Moving docs tree to docs-xml to make room for generated docs in the release tarball.

899 files changed, 239231 insertions, 0 deletions

diff --git a/docs-xml/.bzrignore b/docs-xml/.bzrignore
new file mode 100644
index 00000000000..c3bb0119f0c
--- /dev/null
+++ b/docs-xml/.bzrignore
@@ -0,0 +1,41 @@
+Makefile.settings
+Samba3-Developers-Guide-attributions.xml
+Samba3-HOWTO-attributions.xml
+Samba3-HOWTO.d
+Samba4-HOWTO.d
+Samba4-HOWTO-attributions.xml
+autom4te.cache
+config.log
+config.status
+configure
+test.d
+tmp
+smbdotconf/parameters.all.xml
+smbdotconf/parameters.global.xml
+smbdotconf/parameters.service.xml
+*.d
+output/manpages-3
+Samba3-ByExample.tex
+Samba3-Developers-Guide.tex
+xslt/figures/*.pdf
+output/*.pdf
+*.lof
+*.out
+*.log
+*.aux
+*.ind
+*.ilg
+*.tpt
+*.idx
+*.glo
+*.loe
+*.lot
+*.toc
+Samba3-ByExample.pdf
+Samba3-Developers-Guide.pdf
+Samba3-HOWTO.pdf
+Samba3-HOWTO.tex
+Samba4-HOWTO.pdf
+Samba4-HOWTO.tex
+test.pdf
+test.tex
diff --git a/docs-xml/Makefile b/docs-xml/Makefile
new file mode 100644
index 00000000000..1e4121053d8
--- /dev/null
+++ b/docs-xml/Makefile
@@ -0,0 +1,329 @@
+#################################################################
+# Makefile for Samba Documentation
+# Authors:	
+# 		James Moore <jmoore@php.net>
+# 		Gerald Carter <jerry@samba.org>
+# 		Jelmer Vernooij <jelmer@samba.org>
+include Makefile.settings
+
+# Docs to build
+MAIN_DOCS = $(patsubst %/index.xml,%,$(wildcard */index.xml))
+MANPAGES3 = $(wildcard $(MANPAGEDIR3)/*.?.xml)
+export TEXINPUTS=xslt/latex:.:
+
+# Lists of files to process
+LATEX_FIGURES = xslt/figures/caution.pdf xslt/figures/important.pdf xslt/figures/note.pdf xslt/figures/tip.pdf xslt/figures/warning.pdf
+MANPAGES_PLUCKER = $(patsubst $(MANPAGEDIR3)/%.xml,$(PLUCKERDIR)/%.pdb,$(MANPAGES3))
+
+DATETIME := $(shell date +%Y%m%d%H%M%S)
+
+ifeq ($(PROFILE), Y)
+XSLTPROC += --profile --load-trace --timing
+endif
+
+ifndef OUTPUTDIR
+Makefile.settings: configure
+	@echo Makefile.settings not present, trying to run configure...
+	./configure
+
+configure: configure.ac
+	@echo configure not present, trying to regenerate it...
+	autoreconf
+endif
+
+help: 
+	@echo "Supported make targets:"
+	@echo " release - Build the docs needed for a Samba release"
+	@echo " all - Build all docs that can be build using the utilities found by configure"
+	@echo " everything - Build all of the above"
+	@echo " pdf,tex,dvi,ps,manpages3,txt,pearson,fo,htmlhelp - Build specific output format"
+	@echo " html - Build multi-file HTML versions"
+	@echo " html-single - Build single-file HTML versions"
+	@echo " htmlman3 - Build HTML version of manpages"
+	@echo " undocumented - Output list of undocumented smb.conf options"
+	@echo " samples - Extract examples"
+
+$(DOCBOOKDIR)/Samba3-ByExample.xml: $(filter-out Samba3-ByExample/index.xml,$(wildcard Samba3-ByExample/*.xml))
+$(DOCBOOKDIR)/Samba3-HOWTO.xml: $(filter-out Samba3-HOWTO/index.xml,$(wildcard Samba3-HOWTO/*.xml)) Samba3-HOWTO-attributions.xml
+Samba3-HOWTO/manpages.xml: $(MANPAGEDIR3)/smb.conf.5.xml
+$(DOCBOOKDIR)/Samba3-Developers-Guide.xml: $(filter-out Samba3-Developers-Guide/index.xml,$(wildcard Samba3-Developers-Guide/*.xml)) Samba3-Developers-Guide-attributions.xml
+$(DOCBOOKDIR)/Samba4-HOWTO.xml: $(filter-out Samba4-HOWTO/index.xml,$(wildcard Samba4-HOWTO/*.xml)) Samba4-HOWTO-attributions.xml
+
+# Pseudo targets 
+all: $(TARGETS)
+everything: manpages3 pdf html-single html htmlman3 txt ps fo htmlhelp pearson 
+release: manpages3 htmlman3 html pdf 
+clean:
+	@echo "Cleaning up..." 
+	rm -rf $(OUTPUTDIR)/* $(DOCBOOKDIR)
+	rm -f $(patsubst %.svg,%.png,$(foreach DOC,$(MAIN_DOCS),$($(DOC)-images-latex-dia))) \
+			$(patsubst %.svg,%.pdf,$(foreach DOC,$(MAIN_DOCS),$($(DOC)-images-latex-svg))) \
+			$(patsubst %.svg,%.eps,$(foreach DOC,$(MAIN_DOCS),$($(DOC)-images-latex-svg)))
+	rm -f *.xml *.d *.tpt *.tex *.loc *.toc *.lof *.glo *.idx *.aux
+	rm -f *-images-html*
+	rm -f *-images-latex-* latexfigures
+	rm -f xslt/figures/*pdf
+	rm -f $(SMBDOTCONFDOC)/parameters.*.xml
+	rm -f $(addsuffix .*,$(MAIN_DOCS))
+
+# Output format targets
+pdf: $(patsubst %,$(PDFDIR)/%.pdf,$(MAIN_DOCS))
+dvi: $(patsubst %,$(DVIDIR)/%.dvi,$(MAIN_DOCS))
+ps: $(patsubst %,$(PSDIR)/%.ps,$(MAIN_DOCS))
+txt: $(patsubst %,$(TXTDIR)/%.txt,$(MAIN_DOCS))
+txt-chunks: $(addsuffix -txt-chunks,$(MAIN_DOCS))
+fo: $(patsubst %,$(FODIR)/%.fo,$(MAIN_DOCS))
+fo-pdf: $(patsubst %,$(FOPDFDIR)/%.pdf,$(MAIN_DOCS))
+tex: $(addsuffix .tex,$(MAIN_DOCS))
+texi: $(patsubst %,$(TEXINFODIR)/%.texi,$(MAIN_DOCS))
+texiinfo: $(patsubst %,$(TEXINFODIR)/%.info,$(MAIN_DOCS))
+manpages3: $(patsubst $(MANPAGEDIR3)/%.xml,$(OUTPUTDIR)/manpages-3/%,$(MANPAGES3))
+pearson: $(PEARSONDIR)/Samba3-HOWTO.xml
+pearson-verify: $(PEARSONDIR)/Samba3-HOWTO.report.html
+plucker: $(patsubst %,$(PLUCKERDIR)/%.pdb,$(MAIN_DOCS))
+htmlman3: $(patsubst $(MANPAGEDIR3)/%.xml,$(HTMLDIR)/manpages-3/%.html,$(MANPAGES3)) $(HTMLDIR)/manpages-3/index.html
+html-single: $(patsubst %,$(HTMLDIR)/%.html,$(MAIN_DOCS))
+html: $(patsubst %,$(HTMLDIR)/%/index.html,$(MAIN_DOCS)) $(HTMLDIR)/index.html
+htmlhelp: $(addprefix $(HTMLHELPDIR)/,$(MAIN_DOCS))
+validate: $(addsuffix -validate,$(MAIN_DOCS))
+
+# Intermediate docbook docs
+#
+$(DOCBOOKDIR)/%.xml: %/index.xml xslt/expand-sambadoc.xsl
+	@echo "Converting Samba-specific tags for $*..."
+	@mkdir -p $(@D)
+	$(XSLTPROC) --stringparam latex.imagebasedir "$*/" --stringparam noreference 1 --xinclude --output $@ xslt/expand-sambadoc.xsl $<
+
+$(DOCBOOKDIR)/manpages-3/%.xml: $(MANPAGEDIR3)/%.xml xslt/expand-sambadoc.xsl
+	@mkdir -p $(@D)
+	$(XSLTPROC) --xinclude --stringparam noreference 1 --output $@ xslt/expand-sambadoc.xsl $<
+
+$(DOCBOOKDIR)/manpages-3/index.xml: $(MANPAGES3) xslt/manpage-summary.xsl
+	@mkdir -p $(@D)
+	echo "<article><variablelist>" > $@
+	$(XSLTPROC) xslt/manpage-summary.xsl $(MANPAGES3) >> $@
+	@echo "</variablelist></article>" >> $@
+
+# HTML docs
+
+$(HTMLDIR)/index.html: htmldocs.html
+	@mkdir -p $(@D)
+	cp $< $@
+	
+$(HTMLDIR)/%/index.html: $(DOCBOOKDIR)/%.xml $(HTMLDIR)/%/samba.css xslt/html-chunk.xsl %-images-html-chunks
+	@mkdir -p $(@D)
+	$(XSLTPROC) --stringparam base.dir "$(HTMLDIR)/$*/" xslt/html-chunk.xsl $<
+
+# Single large HTML files
+$(OUTPUTDIR)/%/samba.css: xslt/html/samba.css
+	@mkdir -p $(@D)
+	cp $< $@
+
+$(patsubst %,$(HTMLDIR)/%.html,$(MAIN_DOCS)): $(HTMLDIR)/%.html: %-images-html-single
+
+$(HTMLDIR)/%.html: $(DOCBOOKDIR)/%.xml $(HTMLDIR)/samba.css xslt/html.xsl 
+	$(XSLTPROC) --output $@ xslt/html.xsl $<
+
+# Attributions
+%-attributions.xml: 
+	@echo "Generating attributions file $@ from $*/"
+	@cp -f templates/attributions.xml $@
+	$(XSLTPROC) --xinclude -o $@ xslt/generate-attributions.xsl $*/index.xml 
+
+# Text files
+$(TXTDIR)/%.txt: $(HTMLDIR)/%.html
+	@mkdir -p $(@D)
+	$(HTML2TEXT) -nobs -style pretty -o $@ $<
+
+# Tex files
+%.tex: %/index.xml xslt/latex.xsl
+	@echo "Generating $@..."
+	@mkdir -p $(@D)
+	$(XSLTPROC) $(DB2LATEX_ARGS) --stringparam latex.imagebasedir "$*/" --xinclude --output $@ xslt/latex.xsl $<
+
+latexfigures: $(LATEX_FIGURES)
+
+$(PDFDIR)/%.pdf: %.pdf
+	@mkdir -p $(@D)
+	cp $< $@
+
+%.idx: %.tex latexfigures
+	-$(PDFLATEX) $<
+
+%.ind: %.idx
+	$(MAKEINDEX) $<
+
+# Dependency files
+%.d: $(DOCBOOKDIR)/%.xml xslt/generate-dependencies.xsl
+	@echo "Generating dependency file for $*" 
+	$(XSLTPROC) \
+		--novalid \
+		--stringparam txtbasedir "$(TXTDIR)/$*/" \
+		--stringparam target "$*" \
+		-o $@ xslt/generate-dependencies.xsl $<
+	@echo "$*-images-latex-svg = \$$(wildcard \$$(addsuffix .svg, \$$($*-images-latex)))" >> $@
+	@echo "$*-images-latex-eps: \$$(addsuffix .eps, \$$($*-images-latex))" >> $@
+	@echo "$*-images-latex-pdf: \$$(patsubst %.svg, %.pdf, \$$($*-images-latex-svg))" >> $@
+	@echo "$*-images-latex-png: \$$(filter-out \$$(patsubst %.svg,%.png,\$$($*-images-latex-svg)), \$$(addsuffix .png, \$$($*-images-latex)))" >> $@
+
+	@echo >> $@
+	@echo "\$$(HTMLDIR)/%: $*/%" >> $@
+	@echo "	@mkdir -p \$$(@D)" >> $@
+	@echo "	@cp \$$< \$$@" >> $@
+	@echo >> $@
+	@echo "\$$(HTMLDIR)/$*/%: $*/%" >> $@
+	@echo "	@mkdir -p \$$(@D)" >> $@
+	@echo "	@cp \$$< \$$@" >> $@
+	@echo >> $@
+	@echo "\$$(HTMLHELPDIR)/$*/%: $*/%" >> $@
+	@echo "	@mkdir -p \$$(@D)" >> $@
+	@echo "	@cp \$$< \$$@" >> $@
+	@echo >> $@
+	@echo "$*-images-html-single: \$$(addprefix \$$(HTMLDIR)/, \$$($*-images-html))" >> $@
+	@echo "$*-images-html-chunks: \$$(addprefix \$$(HTMLDIR)/$*/, \$$($*-images-html))" >> $@
+	@echo "$*-images-htmlhelp: \$$(addprefix \$$(HTMLHELPDIR)/$*/, \$$($*-images-html))" >> $@
+
+ifdef OUTPUTDIR 
+ifneq ($(MAKECMDGOALS),clobber)
+-include $(addsuffix .d,$(MAIN_DOCS))
+endif
+endif
+
+# Adobe PDF files
+%.pdf: %.tex %.ind latexfigures %-images-latex-png %-images-latex-pdf
+	-$(PDFLATEX) $<
+	-$(PDFLATEX) $<
+	-$(PDFLATEX) $<
+	-$(PDFLATEX) $<
+	$(THUMBPDF) --quiet $*.pdf
+	-$(PDFLATEX) $<
+
+# DVI files
+$(DVIDIR)/%.dvi: %.dvi
+	@mkdir -p $(@D)
+	cp $< $@
+
+%.dvi: %.tex %.idx %-images-latex-eps
+	-$(LATEX) $< 
+
+%.eps: %.svg
+	$(INKSCAPE) -z -f $< --export-eps=$@
+
+%.png: %.svg
+	$(INKSCAPE) -z -f $< --export-png=$@
+
+#%.pdf: %.svg
+#	$(INKSCAPE) -z -f $< --export-pdf=$@
+
+%.pdf: %.eps
+	$(EPSTOPDF) $<
+
+%.eps: %.png
+	$(PNGTOPNM) $< | $(PNMTOPS) > $@
+
+# PostScript files
+$(PSDIR)/%.ps: $(DVIDIR)/%.dvi
+	@mkdir -p $(@D)
+	$(DVIPS) -o $@ $<
+
+# Fo
+$(FODIR)/%.fo: $(DOCBOOKDIR)/%.xml
+	@mkdir -p $(@D)
+	$(XSLTPROC) --output $@ xslt/fo.xsl $<
+
+# PDF thru Fo
+$(FOPDFDIR)/%.pdf: $(FODIR)/%.fo
+	@mkdir -p $(@D)
+	JAVA_OPTS=-Xmx250m $(FOP) -q -d $< -pdf $@
+
+$(HTMLHELPDIR)/%: $(DOCBOOKDIR)/%.xml %-images-htmlhelp
+	$(XSLTPROC) --stringparam htmlhelp.chm $*.chm \
+				--stringparam manifest.in.base.dir "$@/" \
+				--stringparam base.dir "$@/" \
+	http://docbook.sourceforge.net/release/xsl/current/htmlhelp/htmlhelp.xsl $<
+
+# Plucker docs
+$(PLUCKERDIR)/%.pdb: $(HTMLDIR)/%.html 
+	@mkdir -p $(@D)
+	$(PLUCKERBUILD) -v -V 2 --stayonhost --zlib-compression -f $* -p $(PLUCKERDIR) file:$< 
+
+# Texinfo docs
+$(TEXINFODIR)/%.texi: $(DOCBOOKDIR)/%.xml
+	@mkdir -p $(@D)
+	cd $(@D) && $(DB2TEXI) $(shell pwd)/$<
+
+$(TEXINFODIR)/%.info: $(TEXINFODIR)/%.texi
+	$(MAKEINFO) --no-validate --force -o $@ "$<"
+
+# Manpages
+$(MANPAGEDIR3)/smb.conf.5.xml: $(SMBDOTCONFDOC)/parameters.all.xml $(SMBDOTCONFDOC)/parameters.service.xml $(SMBDOTCONFDOC)/parameters.global.xml
+
+$(SMBDOTCONFDOC)/parameters.all.xml: $(wildcard $(SMBDOTCONFDOC)/*/*.xml) $(SMBDOTCONFDOC)/generate-file-list.sh
+	$(SMBDOTCONFDOC)/generate-file-list.sh $(SMBDOTCONFDOC) > $@
+
+$(SMBDOTCONFDOC)/parameters.global.xml: $(SMBDOTCONFDOC)/parameters.all.xml $(SMBDOTCONFDOC)/generate-context.xsl
+	@echo "Generating list of global smb.conf options" 
+	$(XSLTPROC) --xinclude --param smb.context "'G'" --output $(SMBDOTCONFDOC)/parameters.global.xml $(SMBDOTCONFDOC)/generate-context.xsl $<
+
+$(SMBDOTCONFDOC)/parameters.service.xml: $(SMBDOTCONFDOC)/parameters.all.xml $(SMBDOTCONFDOC)/generate-context.xsl
+	@echo "Generating list of share-mode smb.conf options" 
+	$(XSLTPROC) --xinclude --param smb.context "'S'" --output $(SMBDOTCONFDOC)/parameters.service.xml $(SMBDOTCONFDOC)/generate-context.xsl $<
+
+$(OUTPUTDIR)/%: $(DOCBOOKDIR)/%.xml xslt/man.xsl
+	@mkdir -p $(@D)
+	$(XSLTPROC) --output $@ xslt/man.xsl $<
+
+# Individual smb.conf parameters
+smb.conf-chunks: $(patsubst $(SMBDOTCONFDOC)/%.xml,$(HTMLDIR)/smb.conf/%.html,$(wildcard $(SMBDOTCONFDOC)/*/*.xml))
+	
+$(HTMLDIR)/smb.conf/%.html: $(SMBDOTCONFDOC)/%.xml
+	@mkdir -p $(@D)
+	$(XSLTPROC) --output $@ xslt/smb.conf-html.xsl $<
+
+# Pearson compatible XML
+$(PEARSONDIR)/%.xml: %/index.xml xslt/pearson.xsl
+	@mkdir -p $(@D)
+	$(XSLTPROC) --xinclude --output $@ xslt/sambadoc2pearson.xsl $<
+
+$(PEARSONDIR)/%.report.html: $(PEARSONDIR)/%.xml
+	@mkdir -p $(@D)
+	-$(XMLLINT) --valid --noout $< 2> $@
+
+# Validation verification
+%-validate: %/index.xml
+	cd $(<D) && $(XMLLINT) --xinclude --noent --postvalid --noout $(<F)
+
+# Find undocumented parameters
+undocumented: $(SMBDOTCONFDOC)/parameters.all.xml scripts/find_missing_doc.pl scripts/find_missing_manpages.pl
+	$(PERL) scripts/find_missing_doc.pl $(SRCDIR)
+	$(PERL) scripts/find_missing_manpages.pl $(SRCDIR)
+
+samples: $(DOCBOOKDIR)/Samba3-HOWTO.xml xslt/extract-examples.xsl scripts/indent-smb.conf.pl
+	@mkdir -p $(EXAMPLESDIR)
+	$(XSLTPROC) --xinclude xslt/extract-examples.xsl $< > /dev/null 2> examples/README
+	for I in examples/*.conf; do { ./scripts/indent-smb.conf.pl < $$I > $$I.tmp; mv $$I.tmp $$I; } done
+
+# Archiving
+archive: pdf
+	@mkdir -p $(ARCHIVEDIR)
+	cp $(PDFDIR)/Samba3-HOWTO.pdf $(ARCHIVEDIR)/TOSHARG-$(DATETIME).pdf
+	cp $(PDFDIR)/Samba3-ByExample.pdf $(ARCHIVEDIR)/S3bE-$(DATETIME).pdf
+
+# XSL scripts
+xslt/html.xsl: xslt/html-common.xsl 
+xslt/html-chunk.xsl: xslt/html-common.xsl 
+xslt/latex.xsl: 
+xslt/expand-sambadoc.xsl: 
+xslt/generate-attributions.xsl: 
+xslt/man.xsl:
+xslt/pearson.xsl:
+
+distclean clobber: clean
+	rm Makefile.settings config.status config.log configure
+	rm -rf autom4te.cache
+
+
+# Always keep intermediate files if we can
+.SECONDARY:
+.PHONY: clean clobber archive release everything all $(TARGETS) latexfigures
+
diff --git a/docs-xml/Makefile.settings.in b/docs-xml/Makefile.settings.in
new file mode 100644
index 00000000000..fd7b4d70df0
--- /dev/null
+++ b/docs-xml/Makefile.settings.in
@@ -0,0 +1,50 @@
+# Programs
+XSLTPROC = @XSLTPROC@
+XMLLINT = @XMLLINT@
+DVIPS = @DVIPS@
+PNGTOPNM = @PNGTOPNM@
+EPSTOPNM = @EPSTOPNM@
+PNMTOPNG = @PNMTOPNG@
+DIA = @DIA@
+INKSCAPE = @INKSCAPE@
+PNMTOPS = @PNMTOPS@
+HTML2TEXT = @HTML2TEXT@
+DB2TEXI = @DB2TEXI@
+MAKEINFO = @MAKEINFO@
+PLUCKERBUILD = @PLUCKERBUILD@
+COPY_IMAGES = ./scripts/copy-images.sh
+THUMBPDF = @THUMBPDF@
+PDFLATEX = @PDFLATEX@ --file-line-error-style
+LATEX = @LATEX@ --file-line-error-style
+FOP = @FOP@
+RM = @RM@
+PERL = @PERL@
+ifndef DEBUG_LATEX
+PDFLATEX += --interaction nonstopmode
+LATEX += --interaction nonstopmode
+endif
+
+# Paths
+OUTPUTDIR = output
+ARCHIVEDIR = archive
+TEXINFODIR = $(OUTPUTDIR)/texi
+SRCDIR = @SAMBASOURCEDIR@
+EPSTOPDF = @EPSTOPDF@
+MANPAGEDIR3 = manpages-3
+MAKEINDEX = @MAKEINDEX@
+EXAMPLESDIR = $(OUTPUTDIR)/examples
+SMBDOTCONFDOC = smbdotconf
+DOCBOOKDIR = tmp
+PSDIR = $(OUTPUTDIR)
+FOPDFDIR = $(OUTPUTDIR)/fo-pdf
+PDFDIR = $(OUTPUTDIR)
+DVIDIR = $(OUTPUTDIR)
+FODIR = $(OUTPUTDIR)
+HTMLHELPDIR = $(OUTPUTDIR)/htmlhelp
+PEARSONDIR = $(OUTPUTDIR)/pearson
+TXTDIR = $(OUTPUTDIR)/textdocs
+HTMLDIR=$(OUTPUTDIR)/htmldocs
+PLUCKERDIR=$(OUTPUTDIR)/plucker
+DB2LATEX_ARGS = --stringparam latex.documentclass.book @LATEX_DOCUMENTCLASS_OPTIONS@
+
+TARGETS = @TARGETS@
diff --git a/docs-xml/README b/docs-xml/README
new file mode 100644
index 00000000000..64095ebf390
--- /dev/null
+++ b/docs-xml/README
@@ -0,0 +1,125 @@
+!==
+!== docbook.txt for Samba 3.0
+!==
+!== Author:	David Bannon, D.Bannon@latrobe.edu.au  November, 2000
+!== Updates:	Gerald (Jerry) Carter, jerry@samba.org, Feb. 2001
+!== Updates:	Jelmer Vernooij, jelmer@samba.org,		Aug, 2002
+!== Updates:	Jelmer Vernooij, jelmer@samba.org,		Jun, 2003
+!== Updates: 	Jelmer Vernooij, jelmer@samba.org,		May, 2004
+!== Updates:    Jelmer Vernooij, jelmer@samba.org,              May, 2005
+
+Quick start
+-----------
+
+Run:
+
+make all
+
+What are DocBook documents doing in the Samba Distribution ?
+-----------------------------------------------------------
+
+We have converted all samba docs to XML/DocBook V4.2
+in order to make them easier to maintain and produce a nicer looking
+product.
+
+This short note (strange isn't it how it always starts out as a short note
+and becomes a long one ?) will explain very briefly how and why we have
+done this.
+
+
+The format
+----------
+If you are new to xml, regard an xml file as 'source code'. You don't
+read it directly, but use it to create other formats (like the txt and html
+included in ../txtdocs and ../htmldocs).
+
+Docbook is a particular XML style, particularly suited to producing
+technical manuals. 
+
+For more information on DocBook tags and format, see "DocBook: The 
+Definitive Guide" by Walsh and Muellner, (c) O'Reilly Publishing.
+This book covers DocBook V4.2 and is available on-line
+at http://www.docbook.org/
+
+The Output
+----------
+The current Samba Subversion tree contains the XML/DocBook source files.
+
+A regularly generated version can be found at http://samba.org/samba/docs/.
+
+The Tools
+---------
+
+To generate the docs, you need to have the following packages installed:
+
+ * GNU Make
+ * GNU autoconf
+ * docbook-utils
+ * xsltproc
+ * pngtopnm and pnmtops (from the netpbm utilities)
+ * inkscape
+
+For generating PDF (thru LaTeX):
+ * db2latex (from http://db2latex.sf.net/). Make sure to get CVS version
+   dated 20030622 -- it works best. Versions previous to 20030425 are known
+   to have problems, as well as current (as of 20031210) snapshots.
+ * pdflatex
+ * thumbpdf
+
+For generating PDF (thru FO):
+ * fop (http://xml.apache.org/fop/)
+
+For generating PostScript (thru LaTeX):
+ * db2latex
+ * latex
+ * dvips 
+
+For generating ASCII:
+ * html2text
+
+For generating Palm-viewable docs:
+ * plucker-build
+
+For generating texi files:
+ * docbook2x-texi
+ * makeinfo
+
+For validating:
+ * xmllint
+
+This directory now contains a ./configure script and Makefile to 
+support the automated building of man pages (including HTML versions), and 
+the building of the Samba-HOWTO-Collection and the 
+Samba Developers Guide (HTML,DVI,TeX,PDF,PS,Text versions).
+
+The configure script detects which of the required utilities are installed 
+and builds as much docs as it can using these tools.
+
+Help! Building the docs generates a lot of HTTP traffic...
+-------------
+To be able to build the docs without an internet connection (or faster with 
+a slow internet connection), you need to set up "catalogs".
+
+A catalog contains a list of mappings to locally cached documents. E.g. :
+http://db2latex.sf.net/xsl/ -> /usr/share/sgml/docbook/db2latex/xsl/
+
+Add the following two lines to /etc/xml/catalog for db2latex:
+<rewriteURI uriStartString="http://db2latex.sourceforge.net/xsl/" rewritePrefix="/export/user/me/source/docbook/db2latex/xsl/"/>
+<rewriteURI uriStartString="http://docbook.sourceforge.net/release/xsl/current/" rewritePrefix="/export/user/me/source/docbook/docbook-xsl/"/>
+
+For the Pearson DTD, add something like:
+
+  <public publicId="-//Pearson//DTD Books//DE" uri="file:///home/jelmer/Xml_dtd_1.1/pearson.dtd"/>
+
+For the Samba DTD's, add something like:
+  <rewriteURI uriStartString="http://www.samba.org/samba/DTD" rewritePrefix="file:///home/jelmer/samba-web/DTD"/>
+
+(of course, adapt /export/user/me/source/ to whatever path db2latex is 
+ installed in...)
+
+catalog entries for the other DTD's and XSL scripts should be present on your 
+system already.
+
+Windows Help files
+----------
+http://htmlhelp.berlios.de/howto/mshh4wine.php
diff --git a/docs-xml/Samba-EventLog-HOWTO.txt b/docs-xml/Samba-EventLog-HOWTO.txt
new file mode 100644
index 00000000000..33b3c1ddc47
--- /dev/null
+++ b/docs-xml/Samba-EventLog-HOWTO.txt
@@ -0,0 +1,130 @@
+##
+## Samba-EventLog-HOWTO.txt
+## Brian Moran <bmoran@centeris.com>
+##
+## Feature Introduced in Samba 3.0.21
+##
+
+Samba and Eventlogs
+===================
+
+Samba servers now support event logs -- this means that if 
+Samba is configured correctly, the usual administration tools 
+like event viewer will work against a Samba server. 
+
+To minimally configure Samba to publish event logs, the
+eventlogs to list must be specified in smb.conf, and 
+eventlog entries must be written to those eventlogs. 
+
+Optionally, a message file can be registered for each 
+of the eventlog 'sources' to pretty-print the eventlog 
+messages in the eventlog viewer. 
+
+Configuring smb.conf
+====================
+
+To specify the list of eventlogs the eventlog list 
+command is used. An example which will show four 
+eventlogs is 
+
+	eventlog list = Application System Security  SyslogLinux
+
+When Samba initially starts, it looks to see if the 
+eventlog directory, and a particular log exists; if not, 
+the  directory and file are created under LOCK_DIR 
+
+Writing EventLog Records
+========================
+
+The eventlogadm command is used to write records 
+into a particular eventlog. Eventlogadm expects records 
+to be on STDIN in the following format
+
+	LEN: 0
+	RS1: 1699505740
+	RCN: 0
+	TMG: 1128631322
+	TMW: 1128631322
+	EID: 1000
+	ETP: INFO
+	ECT: 0
+	RS2: 0
+	CRN: 0
+	USL: 0
+	SRC: cron
+	SRN: dmlinux
+	STR: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
+	DAT: 
+
+These fields closely mirror the eventlog structures 
+used by the APIs.  The definitions of the fields are 
+
+- LEN: <integer>  The length field is calculated by the
+  eventlogadm program based on the rest of the information 
+  in the record.  Zero works well here.
+- RS1: 1699505740 A "magic number", the primary purpose of
+  which seems to be to be able to find eventlog records in a 
+  sea of binary data 
+- TMG: <integer>  The time the eventlog record was generated;
+  format is the number of seconds since 00:00:00 January 1, 
+  1970, UTC
+- TMW: <integer>  The time the eventlog record was written;
+  format is the number of seconds since 00:00:00 January 1, 
+  1970, UTC
+- EID: <integer>  The eventlog ID -- used as a index to a
+  message string in a message DLSamba and Eventlogs
+- ETP: <string>   The event type -- one of INFO, ERROR,
+  WARNING, AUDIT SUCCESS, AUDIT FAILURE
+- ECT: <integer>  The event category; this depends on the
+  message file -- primarily used as a means of filtering in 
+  the eventlog viewer
+- RS2: 0 Another reserved field
+- CRN: 0 Yet another reserved field
+- USL: <integer>  Typically would contain the length of the
+  SID of the user object associated with this event. This is 
+  not supported now, so leave this zero.
+- SRC: <string>   The source name associated with the event
+  log, e.g. "cron" or "smbd". If a message file is used with an 
+  event log, there will be a registry entry for associating 
+  this source name with a message file DLL
+- SRN: <string>   The name of the machine on which the
+  eventlog was generated. This is typically the host name
+- STR: <string>   The text associated with the eventlog. Note
+  that there may be more than one strings in a record
+- DAT: <string>   Eventlog records can have binary information
+  associated with them. DAT only supports ASCII strings however
+
+Typically, one would set up a program to gather events, format 
+them into records, and pipe them into eventlogadm for a 
+particular eventlog:
+
+# tail -f /var/log/messages |\
+	my_program_to_parse_into_eventlog_records |\
+	eventlogadm SyslogLinux
+
+Note that individual records are separated on the input by one 
+or more blank lines. In this manner, eventlogadm will just wait 
+for more input, writing to the underlying log files as necessary.
+
+
+Deciphering EventLog entries on the Client
+==========================================
+
+To set up an eventlog source (which is used by the eventlog viewer
+program to pretty-print eventlog records), create a message file 
+DLL,  then use the eventlogadm program to write the appropriate 
+eventlog registry entries:
+
+# eventlogadm -o addsource Application MyApplication \
+	%SystemRoot%/system32/MyApplication.dll
+
+This will add the key
+[HKLM/System/CurrentControlSet/services/Eventlog/Application/MyApplication]
+and to that key add value "MyApplication/EventLogMessageFile" 
+with a string of %SystemRoot%/system32/MyApplication.dll
+
+If there happens to be a share called [C$] on your samba server, 
+and in that share there's a Windows/system32/MyApplication.dll 
+file, it will be read by the eventlog viewer application when 
+displaying eventlog records to pretty-print your eventlog entries.
+
diff --git a/docs-xml/Samba.desktop b/docs-xml/Samba.desktop
new file mode 100644
index 00000000000..2ec24b37791
--- /dev/null
+++ b/docs-xml/Samba.desktop
@@ -0,0 +1,16 @@
+[Desktop Entry]
+Name=Samba
+Name[cz]=Samba
+Name[de]=Samba
+Name[nl]=Samba
+Name[sk]=Samba
+Comment=The file and print service to SMB/ CIFS clients
+Comment[cz]=Souborové a tiskové služby pre klienty SMB/ CIFS
+Comment[de]=SMB/ CIFS Datei- und Druck-Server
+Comment[nl]=SMB/CIFS Bestand en Print-Server
+Comment[pl]=Usługa plików i drukarek dla klientów SMB/CIFS
+Comment[sk]=Súborové a tlačové služby pre klientov SMB/ CIFS
+DocPath=/usr/share/doc/packages/samba/htmldocs/index.html
+X-DOC-SearchMethod=htdig
+X-DOC-SearchEnabledDefault=true
+X-DOC-Weight=-5000
diff --git a/docs-xml/Samba3-ByExample/SBE-2000UserNetwork.xml b/docs-xml/Samba3-ByExample/SBE-2000UserNetwork.xml
new file mode 100644
index 00000000000..c86d9bcb946
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-2000UserNetwork.xml
@@ -0,0 +1,1636 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="2000users">
+  <title>A Distributed 2000-User Network</title>
+
+<para>
+There is something indeed mystical about things that are
+big. Large networks exhibit a certain magnetism and exude a sense of
+importance that obscures reality. You and I know that it is no more
+difficult to secure a large network than it is a small one. We all
+know that over and above a particular number of network clients, the
+rules no longer change; the only real dynamic is the size of the domain
+(much like a kingdom) over which the network ruler (oops, administrator)
+has control. The real dynamic then transforms from the technical to the
+political. Then again, that point is often reached well before the
+kingdom (or queendom) grows large.
+</para>
+
+<para>
+If you have systematically worked your way to this chapter, hopefully you
+have found some gems and techniques that are applicable in your
+world. The network designs you have worked with in this book have their
+strong points as well as weak ones. That is to be expected given that
+they are based on real business environments, the specifics of which are
+molded to serve the purposes of this book.
+</para>
+
+<para>
+This chapter is intent on wrapping up issues that are central to
+implementation and design of progressively larger networks. Are you ready
+for this chapter? Good, it is time to move on.
+</para>
+
+<para>
+In previous chapters, you made the assumption that your network
+administration staff need detailed instruction right down to the
+nuts and bolts of implementing the solution. That is still the case,
+but they have graduated now. You decide to document only those issues,
+methods, and techniques that are new or complex. Routine tasks such as
+implementing a DNS or a DHCP server are under control. Even the basics of
+Samba are largely under control. So in this section you focus on the
+specifics of implementing LDAP changes, Samba changes, and approach and
+design of the solution and its deployment.
+</para>
+
+<sect1>
+<title>Introduction</title>
+
+<para>
+Abmas is a miracle company. Most businesses would have collapsed under
+the weight of rapid expansion that this company has experienced. Samba 
+is flexible, so there is no need to reinstall the whole operating 
+system just because you need to implement a new network design. In fact, 
+you can keep an old server running right up to the moment of cutover 
+and then do a near-live conversion. There is no need to reinstall a 
+Samba server just to change the way your network should function.
+</para>
+
+<para>
+<indexterm><primary>LDAP</primary></indexterm>
+Network growth is common to all organizations. In this exercise,
+your preoccupation is with the mechanics of implementing Samba and
+LDAP so that network users on each network segment can work
+without impediment.
+</para>
+
+	<sect2>
+	<title>Assignment Tasks</title>
+
+	<para>
+	Starting with the configuration files for the server called
+	<constant>MASSIVE</constant> in <link linkend="happy"/>, you now deal with the
+	issues that are particular to large distributed networks. Your task
+	is simple &smbmdash; identify the challenges, consider the 
+	alternatives, and then design and implement a solution.
+	</para>
+
+	<para>
+	<indexterm><primary>VPN</primary></indexterm>
+	Remember, you have users based in London (UK), Los Angeles,
+	Washington. DC, and, three buildings in New York. A significant portion
+	of your workforce have notebook computers and roam all over the
+	world. Some dial into the office, others use VPN connections over the
+	Internet, and others just move between buildings.i
+	</para>
+
+	<para>
+	What do you say to an employee who normally uses a desktop
+	system but must spend six weeks on the road with a notebook computer?
+	She is concerned about email access and how to keep coworkers current
+	with changing documents.
+	</para>
+
+		<para>
+	To top it all off, you have one network support person and one 
+	help desk person based in London, a single person dedicated to all 
+	network operations in Los Angeles, five staff for user administration 
+	and help desk in New York, plus one <emphasis>floater</emphasis> for 
+	Washington.
+	</para>
+
+		<para>
+	You have outsourced all desktop deployment and management to
+	DirectPointe. Your concern is server maintenance and third-level
+	support. Build a plan and show what must be done.
+	</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+<title>Dissection and Discussion</title>
+
+<para>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+In <link linkend="happy"/>, you implemented an LDAP server that provided the
+<parameter>passdb backend</parameter> for the Samba servers. You
+explored ways to accelerate Windows desktop profile handling and you
+took control of network performance.
+</para>
+
+<para>
+<indexterm><primary>ldapsam</primary></indexterm>
+<indexterm><primary>tdbsam</primary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>replicated</primary></indexterm>
+The implementation of an LDAP-based passdb backend (known as
+<emphasis>ldapsam</emphasis> in Samba parlance), or some form of database
+that can be distributed, is essential to permit the deployment of Samba
+Primary and Backup Domain Controllers (PDC/BDCs). You see, the problem
+is that the <emphasis>tdbsam</emphasis>-style passdb backend does not
+lend itself to being replicated. The older plain-text-based
+<emphasis>smbpasswd</emphasis>-style passdb backend can be replicated
+using a tool such as <command>rsync</command>, but
+<emphasis>smbpasswd</emphasis> suffers the drawback that it does not
+support the range of account facilities demanded by modern network
+managers.
+</para>
+
+<para>
+<indexterm><primary>XML</primary></indexterm>
+<indexterm><primary>SQL</primary></indexterm>
+The new <emphasis>tdbsam</emphasis> facility supports functionality
+that is similar to an <emphasis>ldapsam</emphasis>, but the lack of
+distributed infrastructure sorely limits the scope for its
+deployment. This raises the following questions: Why can't I just use
+an XML-based backend, or for that matter, why not use an SQL-based
+backend? Is support for these tools broken? Answers to these
+questions require a bit of background.</para>
+
+<para>
+<indexterm><primary>directory</primary></indexterm>
+<indexterm><primary>database</primary></indexterm>
+<indexterm><primary>transaction processing</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<emphasis>What is a directory?</emphasis> A directory is a
+collection of information regarding objects that can be accessed to
+rapidly find information that is relevant in a particular and
+consistent manner. A directory differs from a database in that it is
+generally more often searched (read) than updated. As a consequence, the
+information is organized to facilitate read access rather than to
+support transaction processing.</para>
+
+<para>
+<indexterm><primary>Lightweight Directory Access Protocol</primary><see>LDAP</see></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>master</primary></indexterm>
+<indexterm><primary>slave</primary></indexterm>
+The Lightweight Directory Access Protocol (LDAP) differs
+considerably from a traditional database. It has a simple search
+facility that uniquely makes a highly preferred mechanism for managing
+user identities. LDAP provides a scalable mechanism for distributing
+the data repository and for keeping all copies (slaves) in sync with
+the master repository.</para>
+
+<para>
+<indexterm><primary>identity management</primary></indexterm>
+<indexterm><primary>Active Directory</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+Samba is a flexible and powerful file and print sharing
+technology. It can use many external authentication sources and can be
+part of a total authentication and identity management
+infrastructure. The two most important external sources for large sites
+are Microsoft Active Directory and LDAP. Sites that specifically wish to
+avoid the proprietary implications of Microsoft Active Directory
+naturally gravitate toward OpenLDAP.</para>
+
+<para>
+<indexterm><primary>network</primary><secondary>routed</secondary></indexterm>
+In <link linkend="happy"/>, you had to deal with a locally routed
+network. All deployment concerns focused around making users happy,
+and that simply means taking control over all network practices and
+usage so that no one user is disadvantaged by any other. The real
+lesson is one of understanding that no matter how much network
+bandwidth you provide, bandwidth remains a precious resource.</para>
+
+<para>In this chapter, you must now consider how the overall network must
+function. In particular, you must be concerned with users who move
+between offices. You must take into account the way users need to
+access information globally. And you must make the network robust
+enough so that it can sustain partial breakdown without causing loss of
+productivity.</para>
+
+	<sect2>
+	<title>Technical Issues</title>
+
+	<para>
+	There are at least three areas that need to be addressed as you
+	approach the challenge of designing a network solution for the newly
+	expanded business:
+	</para>
+
+	<itemizedlist>
+		<listitem><para><indexterm><primary>mobility</primary></indexterm>
+		User needs such as mobility and data access</para></listitem>
+
+		<listitem><para>The nature of Windows networking protocols</para></listitem>
+
+		<listitem><para>Identity management infrastructure needs</para></listitem>
+	</itemizedlist>
+
+	<para>Let's look at each in turn.</para>
+
+	<sect3>
+	  <title>User Needs</title>
+
+	<para>
+	The new company has three divisions. Staff for each division are spread across
+	the company. Some staff are office-bound and some are mobile users. Mobile
+	users travel globally. Some spend considerable periods working in other offices.
+	Everyone wants to be able to work without constraint of productivity.
+	</para> 
+
+	<para>
+	The challenge is not insignificant. In some parts of the world, even dial-up
+	connectivity is poor, while in other regions political encumbrances severely
+	curtail user needs. Parts of the global Internet infrastructure remain shielded
+	off for reasons outside the scope of this discussion.
+	</para>
+
+	<para>
+	<indexterm><primary>synchronize</primary></indexterm>
+	Decisions must be made regarding where data is to be stored, how it will be
+	replicated (if at all), and what the network bandwidth implications are. For
+	example, one decision that can be made is to give each office its own master
+	file storage area that can be synchronized to a central repository in New
+	York. This would permit global data to be backed up from a single location.
+	The synchronization tool could be <command>rsync,</command> run via a cron
+	job. Mobile users may use off-line file storage under Windows XP Professional.
+	This way, they can synchronize all files that have changed since each logon
+	to the network.
+	</para>
+
+	<para>
+	<indexterm><primary>bandwidth</primary><secondary>requirements</secondary></indexterm>
+	<indexterm><primary>roaming profile</primary></indexterm>
+	No matter which way you look at this, the bandwidth requirements
+	for acceptable performance are substantial even if only 10 percent of
+	staff are global data users. A company with 3,500 employees,
+	280 of whom are mobile users who use a similarly distributed
+	network, found they needed at least 2 Mb/sec connectivity
+	between the UK and US offices. Even over 2 Mb/sec bandwidth, this
+	company abandoned any attempt to run roaming profile usage for
+	mobile users. At that time, the average roaming profile took 480
+	KB, while today the minimum Windows XP Professional roaming
+	profile involves a transfer of over 750 KB from the profile
+	server to and from the client.
+	</para>
+
+	<para>
+	<indexterm><primary>wide-area</primary></indexterm>
+	Obviously then, user needs and wide-area practicalities dictate the economic and
+	technical aspects of your network design as well as for standard operating procedures.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	  <title>The Nature of Windows Networking Protocols</title>
+
+	<para>
+	<indexterm><primary>profile</primary><secondary>mandatory</secondary></indexterm>
+	Network logons that include roaming profile handling requires from 140 KB to 2 MB.
+	The inclusion of support for a minimal set of common desktop applications can push
+	the size of a complete profile to over 15 MB. This has substantial implications
+	for location of user profiles. Additionally, it is a significant factor in
+	determining the nature and style of mandatory profiles that may be enforced as
+	part of a total service-level assurance program that might be implemented.
+	</para>
+
+	<para>
+	<indexterm><primary>logon traffic</primary></indexterm>
+	<indexterm><primary>redirected folders</primary></indexterm>
+	One way to reduce the network bandwidth impact of user logon
+	traffic is through folder redirection. In <link linkend="happy"/>, you
+	implemented this in the new Windows XP Professional standard
+	desktop configuration. When desktop folders such as <guimenu>My
+	Documents</guimenu> are redirected to a network drive, they should
+	also be excluded from synchronization to and from the server on
+	logon or logout. Redirected folders are analogous to network drive
+	connections.
+	</para>
+
+	<para><indexterm><primary>application servers</primary></indexterm>
+	Of course, network applications should only be run off
+	local application servers. As a general rule, even with 2 Mb/sec
+	network bandwidth, it would not make sense at all for someone who
+	is working out of the London office to run applications off a
+	server that is located in New York.
+	</para>
+
+	<para>
+	<indexterm><primary>affordability</primary></indexterm>
+	When network bandwidth becomes a precious commodity (that is most
+	of the time), there is a significant demand to understand network
+	processes and to mold the limits of acceptability around the
+	constraints of affordability.
+	</para>
+
+	<para>
+	When a Windows NT4/200x/XP Professional client user logs onto
+	the network, several important things must happen.
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		<indexterm><primary>DHCP</primary></indexterm>
+		The client obtains an IP address via DHCP. (DHCP is
+		necessary so that users can roam between offices.)
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>WINS</primary></indexterm>
+		<indexterm><primary>DNS</primary></indexterm>
+		The client must register itself with the WINS and/or DNS server.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>Domain Controller</primary><secondary>closest</secondary></indexterm>
+		The client must locate the closest domain controller.
+		</para></listitem>
+
+		<listitem><para>
+		The client must log onto a domain controller and obtain as part of
+		that process the location of the user's profile, load it, connect to
+		redirected folders, and establish all network drive and printer connections.
+		</para></listitem>
+
+		<listitem><para>
+		The domain controller must be able to resolve the user's
+		credentials before the logon process is fully implemented.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	Given that this book is about Samba and that it implements the Windows
+	NT4-style domain semantics, it makes little sense to compare Samba with
+	Microsoft Active Directory insofar as 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.20 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
+	IP address. This is immediately followed by registration of its
+	name both by broadcast and Unicast registration that is directed
+	at the WINS server.
+	</para>
+
+	<para>
+	<indexterm><primary>Unicast</primary></indexterm>
+	<indexterm><primary>broadcast</primary><secondary>directed</secondary>
+	</indexterm><indexterm><primary>NetBIOS</primary></indexterm>
+	Given that the client is already a domain member, it then sends
+	a directed (Unicast) request to the WINS server seeking the list of
+	IP addresses for domain controllers (NetBIOS name type 0x1C). The
+	WINS server replies with the information requested.</para>
+
+	<para>
+	<indexterm><primary>broadcast</primary><secondary>mailslot</secondary></indexterm>
+	<indexterm><primary>Unicast</primary></indexterm>
+	<indexterm><primary>WINS</primary></indexterm>
+	The client sends two netlogon mailslot broadcast requests
+	to the local network and to each of the IP addresses returned by
+	the WINS server. Whichever answers this request first appears to
+	be the machine that the Windows XP client attempts to use to
+	process the network logon. The mailslot messages use UDP broadcast
+	to the local network and UDP Unicast directed at each machine that
+	was listed in the WINS server response to a request for the list of
+	domain controllers.
+	</para>
+
+	<para>
+	<indexterm><primary>protocol</primary><secondary>negotiation</secondary></indexterm>
+	<indexterm><primary>logon server</primary></indexterm>
+	<indexterm><primary>fail</primary></indexterm>
+	The logon process begins with negotiation of the SMB/CIFS
+	protocols that are to be used; this is followed by an exchange of
+	information that ultimately includes the client sending the
+	credentials with which the user is attempting to logon. The logon
+	server must now approve the further establishment of the
+	connection, but that is a good point to halt for now. The priority
+	here must center around identification of network infrastructure
+	needs. A secondary fact we need to know is, what happens when
+	local domain controllers fail or break?
+	</para>
+
+	<para>
+	<indexterm><primary>Domain Controller</primary></indexterm>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>netlogon</primary></indexterm>
+	Under most circumstances, the nearest domain controller
+	responds to the netlogon mailslot broadcast. The exception to this
+	norm occurs when the nearest domain controller is too busy or is out
+	of service. Herein lies an important fact. This means it is
+	important that every network segment should have at least two
+	domain controllers. Since there can be only one PDC, all additional
+	domain controllers are by definition BDCs.
+	</para>
+
+	<para>
+	<indexterm><primary>authentication</primary></indexterm>
+	<indexterm><primary>Identity Management</primary></indexterm>
+	The provision of sufficient servers that are BDCs is an
+	important design factor. The second important design factor
+	involves how each of the BDCs obtains user authentication
+	data. That is the subject of the next section, which involves key
+	decisions regarding Identity Management facilities.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Identity Management Needs</title>
+
+	<para>
+	<indexterm><primary>privacy</primary></indexterm>
+	<indexterm><primary>user credentials</primary></indexterm>
+	<indexterm><primary>validated</primary></indexterm>
+	<indexterm><primary>privileges</primary></indexterm>
+	Network managers recognize that in large organizations users
+	generally need to be given resource access based on needs, while
+	being excluded from other resources for reasons of privacy. It is
+	therefore essential that all users identify themselves at the
+	point of network access. The network logon is the principal means
+	by which user credentials are validated and filtered and appropriate
+	rights and privileges are allocated.
+	</para>
+
+	<para>
+	<indexterm><primary>Identity Management</primary></indexterm>
+	<indexterm><primary>Yellow Pages</primary></indexterm>
+	<indexterm><primary>NIS</primary></indexterm>
+	Unfortunately, network resources tend to have their own Identity 
+	Management facilities, the quality and manageability of which varies 
+	from quite poor to exceptionally good. Corporations that use a mixture 
+	of systems soon discover that until recently, few systems were 
+	designed to interoperate. For example, UNIX systems each have an 
+	independent user database. Sun Microsystems developed a facility that 
+	was originally called <constant>Yellow Pages</constant>, and was renamed 
+	when a telephone company objected to the use of its trademark. 
+	What was once called <constant>Yellow Pages</constant> is today known 
+	as <constant>Network Information System</constant> (NIS).
+	</para>
+
+	<para>
+	<indexterm><primary>NIS+</primary></indexterm>
+	NIS gained a strong following throughout the UNIX/VMS space in a short
+	period of time and retained that appeal and use for over a decade.
+	Security concerns and inherent limitations have caused it to enter its
+	twilight. NIS did not gain widespread appeal outside of the UNIX world
+	and was not universally adopted. Sun updated this to a more secure
+	implementation called NIS+, but even it has fallen victim to changing
+	demands as the demand for directory services that can be coupled with
+	other information systems is catching on.
+	</para>
+
+
+	<para>
+	<indexterm><primary>NIS</primary></indexterm>
+	<indexterm><primary>government</primary></indexterm>
+	<indexterm><primary>education</primary></indexterm>
+	Nevertheless, both NIS and NIS+ continue to hold ground in
+	business areas where UNIX still has major sway. Examples of
+	organizations that remain firmly attached to the use of NIS and
+	NIS+ include large government departments, education institutions,
+	and large corporations that have a scientific or engineering
+	focus.
+	</para>
+
+	<para>
+	<indexterm><primary>scalable</primary></indexterm>
+	<indexterm><primary>distributed</primary></indexterm>
+	Today's networking world needs a scalable, distributed Identity 
+	Management infrastructure, commonly called a directory. The most 
+	popular technologies today are Microsoft Active Directory service 
+	and a number of LDAP implementations.
+	</para>
+
+	<para>
+	<indexterm><primary>multiple directories</primary></indexterm>
+	The problem of managing multiple directories has become a focal
+	point over the past decade, creating a large market for
+	metadirectory products and services that allow organizations that
+	have multiple directories and multiple management and control
+	centers to provision information from one directory into
+	another. The attendant benefit to end users is the promise of
+	having to remember and deal with fewer login identities and
+	passwords.</para>
+
+	<para>
+	<indexterm><primary>network</primary><secondary>bandwidth</secondary></indexterm>
+	The challenge of every large network is to find the optimum
+	balance of internal systems and facilities for Identity
+	Management resources. How well the solution is chosen and
+	implemented has potentially significant impact on network bandwidth
+	and systems response needs.</para>
+
+	<para>
+	<indexterm><primary>LDAP server</primary></indexterm>
+	<indexterm><primary>LDAP</primary><secondary>master</secondary></indexterm>
+	<indexterm><primary>LDAP</primary><secondary>slave</secondary></indexterm>
+	In <link linkend="happy"/>, you implemented a single LDAP server for the
+	entire network. This may work for smaller networks, but almost
+	certainly fails to meet the needs of large and complex networks. The
+	following section documents how you may implement a single
+	master LDAP server with multiple slave servers.</para>
+
+	<para>
+	What is the best method for implementing master/slave LDAP
+	servers within the context of a distributed 2,000-user network is a
+	question that remains to be answered.</para>
+
+	<para>
+	<indexterm><primary>distributed domain</primary></indexterm>
+	<indexterm><primary>wide-area</primary></indexterm>
+	One possibility that has great appeal is to create a single,
+	large distributed domain. The practical implications of this
+	design (see <link linkend="chap7net"/>) demands the placement of
+	sufficient BDCs in each location. Additionally, network
+	administrators must make sure that profiles are not transferred
+	over the wide-area links, except as a totally unavoidable
+	measure. Network design must balance the risk of loss of user
+	productivity against the cost of network management and
+	maintenance.
+	</para>
+
+	<para>
+	<indexterm><primary>domain name space</primary></indexterm>
+	The network design in <link linkend="chap7net2"/> takes the approach
+	that management of networks that are too remote to be managed
+	effectively from New York ought to be given a certain degree of
+	autonomy. With this rationale, the Los Angeles and London networks,
+	though fully integrated with those on the East Coast, each have their
+	own domain name space and can be independently managed and controlled.
+	One of the key drawbacks of this design is that it flies in the face of
+	the ability for network users to roam globally without some compromise
+	in how they may access global resources.
+	</para>
+
+	<para>
+	<indexterm><primary>interdomain trusts</primary></indexterm>
+	Desk-bound users need not be negatively affected by this design, since
+	the use of interdomain trusts can be used to satisfy the need for global
+	data sharing.
+	</para>
+
+	<para>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>LDAP</primary><secondary>backend</secondary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	When Samba-3 is configured to use an LDAP backend, it stores the domain
+	account information in a directory entry. This account entry contains the
+	domain SID. An unintended but exploitable side effect is that this makes it
+	possible to operate with more than one PDC on a distributed network.
+	</para>
+
+	<para>
+	<indexterm><primary>WINS</primary></indexterm>
+	<indexterm><primary>wins.dat</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	How might this peculiar feature be exploited? The answer is simple. It is
+	imperative that each network segment have its own WINS server. Major
+	servers on remote network segments can be given a static WINS entry in
+	the <filename>wins.dat</filename> file on each WINS server. This allows
+	all essential data to be visible from all locations. Each location would,
+	however, function as if it is an independent domain, while all sharing the
+	same domain SID. Since all domain account information can be stored in a
+	single LDAP backend, users have unfettered ability to roam.
+	</para>
+
+	<para>
+	<indexterm><primary>NetBIOS name</primary><secondary>aliases</secondary></indexterm>
+	<indexterm><primary>fail-over</primary></indexterm>
+	This concept has not been exhaustively validated, though we can see no reason
+	why this should not work. The important facets are the following: The name of
+	the domain must be identical in all locations. Each network segment must have
+	its own WINS server. The name of the PDC must be the same in all locations; this
+	necessitates the use of NetBIOS name aliases for each PDC so that they can be
+	accessed globally using the alias and not the PDC's primary name. A single master
+	LDAP server can be based in New York, with multiple LDAP slave servers located
+	on every network segment. Finally, the BDCs should each use failover LDAP servers
+	that are in fact slave LDAP servers on the local segments.
+	</para>
+
+	<para>
+	<indexterm><primary>LDAP</primary><secondary>updates</secondary></indexterm>
+	<indexterm><primary>domain tree</primary></indexterm>
+	<indexterm><primary>LDAP</primary><secondary>database</secondary></indexterm>
+	<indexterm><primary>LDAP</primary><secondary>directory</secondary></indexterm>
+	With a single master LDAP server, all network updates are effected on a single
+	server. In the event that this should become excessively fragile or network
+	bandwidth limiting, one could implement a delegated LDAP domain. This is also
+	known as a partitioned (or multiple partition) LDAP database and as a distributed
+	LDAP directory.
+	</para>
+
+	<para>
+	As the LDAP directory grows, it becomes increasingly important
+	that its structure is implemented in a manner that mirrors
+	organizational needs, so as to limit network update and
+	referential traffic. It should be noted that all directory
+	administrators must of necessity follow the same standard
+	procedures for managing the directory, because retroactive correction of
+	inconsistent directory information can be exceedingly difficult.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+
+	<sect2>
+		<title>Political Issues</title>
+
+	<para>
+	As organizations grow, the number of points of control increases
+	also. In a large distributed organization, it is important that the
+	Identity Management system be capable of being updated from
+	many locations, and it is equally important that changes made should
+	become usable in a reasonable period, typically
+	minutes rather than days (the old limitation of highly manual
+	systems).
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Implementation</title>
+
+	<para>
+	<indexterm><primary>winbind</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>UID</primary></indexterm>
+	<indexterm><primary>GID</primary></indexterm>
+	Samba-3 has the ability to use multiple password (authentication and
+	identity resolution) backends. The diagram in <link linkend="chap7idres"/>
+	demonstrates how Samba uses winbind, LDAP, and NIS, the traditional system
+	password database. The diagram only documents the mechanisms for
+	authentication and identity resolution (obtaining a UNIX UID/GID)
+	using the specific systems shown.
+	</para>
+
+	<figure id="chap7idres">
+		<title>Samba and Authentication Backend Search Pathways</title>
+		<imagefile scale="55">chap7-idresol</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>smbpasswd</primary></indexterm>
+	<indexterm><primary>xmlsam</primary></indexterm>
+	<indexterm><primary>SMB passwords</primary></indexterm>
+	<indexterm><primary>tdbsam</primary></indexterm>
+	<indexterm><primary>mysqlsam</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>distributed</primary></indexterm>
+	Samba is capable of using the <constant>smbpasswd</constant>,
+	<constant>tdbsam</constant>, <constant>xmlsam</constant>,
+	and <constant>mysqlsam</constant> authentication databases. The SMB
+	passwords can, of course, also be stored in an LDAP ldapsam
+	backend. LDAP is the preferred passdb backend for distributed network
+	operations.
+	</para>
+
+	<para>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	Additionally, it is possible to use multiple passdb backends
+	concurrently as well as have multiple LDAP backends. As a result, you
+	can specify a failover LDAP backend. The syntax for specifying a
+	single LDAP backend in &smb.conf; is:
+<screen>
+...
+passdb backend = ldapsam:ldap://master.abmas.biz
+...
+</screen>
+	This configuration tells Samba to use a single LDAP server, as shown in <link linkend="ch7singleLDAP"/>.
+	<figure id="ch7singleLDAP">
+		<title>Samba Configuration to Use a Single LDAP Server</title>
+		<imagefile scale="65">ch7-singleLDAP</imagefile>
+	</figure>
+	<indexterm><primary>LDAP</primary><secondary>fail-over</secondary></indexterm>
+	<indexterm><primary>fail-over</primary></indexterm>
+	The addition of a failover LDAP server can simply be done by adding a
+	second entry for the failover server to the single <parameter>ldapsam</parameter>
+	entry, as shown here (note the particular use of the double quotes):
+<screen>
+...
+passdb backend = ldapsam:"ldap://master.abmas.biz \
+	                  ldap://slave.abmas.biz"
+...
+</screen>
+	This configuration tells Samba to use a master LDAP server, with failover to a slave server if necessary,
+	as shown in <link linkend="ch7dualLDAP"/>.
+	<figure id="ch7dualLDAP">
+		<title>Samba Configuration to Use a Dual (Fail-over) LDAP Server</title>
+		<imagefile scale="65">ch7-fail-overLDAP</imagefile>
+	</figure>
+	</para>
+
+	<para>
+	Some folks have tried to implement this without the use of double quotes. This is the type of entry they
+	created:
+<screen>
+...
+passdb backend = ldapsam:ldap://master.abmas.biz \
+                 ldapsam:ldap://slave.abmas.biz
+...
+</screen>
+	<indexterm><primary>contiguous directory</primary></indexterm>
+	The effect of this style of entry is that Samba lists the users
+	that are in both LDAP databases. If both contain the same information,
+	it results in each record being shown twice. This is, of course, not the
+	solution desired for a failover implementation. The net effect of this
+	configuration is shown in <link linkend="ch7dualadd"/>
+	</para>
+
+	<figure id="ch7dualadd">
+		<title>Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!</title>
+		<imagefile scale="55">ch7-dual-additive-LDAP</imagefile>
+	</figure>
+
+	<para>
+	If, however, each LDAP database contains unique information, this may 
+	well be an advantageous way to effectively integrate multiple LDAP databases 
+	into one seemingly contiguous directory. Only the first database will be updated.
+	An example of this configuration is shown in <link linkend="ch7dualok"/>.
+	</para>
+
+	<figure id="ch7dualok">
+		<title>Samba Configuration to Use Two LDAP Databases - The result is additive.</title>
+		<imagefile scale="55">ch7-dual-additive-LDAP-Ok</imagefile>
+	</figure>
+
+	<note><para>
+	When the use of ldapsam is specified twice, as shown here, it is imperative
+	that the two LDAP directories must be disjoint. If the entries are for a
+	master LDAP server as well as its own slave server, updates to the LDAP
+	database may end up being lost or corrupted. You may safely use multiple
+	LDAP backends only if both are entirely separate from each other.
+	</para></note>
+
+    <para>
+	It is assumed that the network you are working with follows in a
+	pattern similar to what was covered in <link linkend="happy"/>. The following steps
+    permit the operation of a master/slave OpenLDAP arrangement.
+	</para>
+
+	<procedure>
+	<title>Implementation Steps for an LDAP Slave Server</title>
+
+		<step><para>
+	    <indexterm><primary>SUSE Linux</primary></indexterm>
+		<indexterm><primary>Red Hat Linux</primary></indexterm>
+		Log onto the master LDAP server as <constant>root</constant>.
+		You are about to change the configuration of the LDAP server, so it
+		makes sense to temporarily halt it. Stop OpenLDAP from running on 
+		SUSE Linux by executing:
+<screen>
+&rootprompt; rcldap stop
+</screen>
+		On Red Hat Linux, you can do this by executing:
+<screen>
+&rootprompt; service ldap stop
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/openldap/slapd.conf</primary></indexterm>
+		Edit the <filename>/etc/openldap/slapd.conf</filename> file so it
+		matches the content of <link linkend="ch7-LDAP-master"/>.
+		</para></step>
+
+		<step><para>
+		Create a file called <filename>admin-accts.ldif</filename> with the following contents:
+<screen>
+dn: cn=updateuser,dc=abmas,dc=biz
+objectClass: person
+cn: updateuser
+sn: updateuser
+userPassword: not24get
+
+dn: cn=sambaadmin,dc=abmas,dc=biz
+objectClass: person
+cn: sambaadmin
+sn: sambaadmin
+userPassword: buttercup
+</screen>
+		</para></step>
+
+		<step><para>
+		Add an account called <quote>updateuser</quote> to the master LDAP server as shown here:
+<screen>
+&rootprompt; slapadd -v -l admin-accts.ldif
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>LDIF</primary></indexterm>
+		<indexterm><primary>LDAP</primary><secondary>preload</secondary></indexterm>
+		Change directory to a suitable place to dump the contents of the
+		LDAP server. The dump file (and LDIF file) is used to preload
+		the slave LDAP server database. You can dump the database by executing:
+<screen>
+&rootprompt; slapcat -v -l LDAP-transfer-LDIF.txt
+</screen>
+		Each record is written to the file.	
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>LDAP-transfer-LDIF.txt</primary></indexterm>
+		Copy the file <filename>LDAP-transfer-LDIF.txt</filename> to the intended
+		slave LDAP server. A good location could be in the directory 
+		<filename>/etc/openldap/preload</filename>.
+		</para></step>
+
+		<step><para>
+		Log onto the slave LDAP server as <constant>root</constant>. You can
+		now configure this server so the <filename>/etc/openldap/slapd.conf</filename>
+		file matches the content of <link linkend="ch7-LDAP-slave"/>.
+		</para></step>
+
+		<step><para>
+		Change directory to the location in which you stored the 
+		<filename>LDAP-transfer-LDIF.txt</filename> file (<filename>/etc/openldap/preload</filename>).
+		While in this directory, execute:
+<screen>
+&rootprompt; slapadd -v -l LDAP-transfer-LDIF.txt
+</screen>
+		If all goes well, the following output confirms that the data is being loaded
+		as intended:
+<screen>
+added: "dc=abmas,dc=biz" (00000001)
+added: "cn=sambaadmin,dc=abmas,dc=biz" (00000002)
+added: "cn=updateuser,dc=abmas,dc=biz" (00000003)
+added: "ou=People,dc=abmas,dc=biz" (00000004)
+added: "ou=Groups,dc=abmas,dc=biz" (00000005)
+added: "ou=Computers,dc=abmas,dc=biz" (00000006)
+added: "uid=Administrator,ou=People,dc=abmas,dc=biz" (00000007)
+added: "uid=nobody,ou=People,dc=abmas,dc=biz" (00000008)
+added: "cn=Domain Admins,ou=Groups,dc=abmas,dc=biz" (00000009)
+added: "cn=Domain Users,ou=Groups,dc=abmas,dc=biz" (0000000a)
+added: "cn=Domain Guests,ou=Groups,dc=abmas,dc=biz" (0000000b)
+added: "uid=bobj,ou=People,dc=abmas,dc=biz" (0000000c)
+added: "sambaDomainName=MEGANET2,dc=abmas,dc=biz" (0000000d)
+added: "uid=stans,ou=People,dc=abmas,dc=biz" (0000000e)
+added: "uid=chrisr,ou=People,dc=abmas,dc=biz" (0000000f)
+added: "uid=maryv,ou=People,dc=abmas,dc=biz" (00000010)
+added: "cn=Accounts,ou=Groups,dc=abmas,dc=biz" (00000011)
+added: "cn=Finances,ou=Groups,dc=abmas,dc=biz" (00000012)
+added: "cn=PIOps,ou=Groups,dc=abmas,dc=biz" (00000013)
+</screen>
+		</para></step>
+
+		<step><para>
+		Now start the LDAP server and set it to run automatically on system reboot by executing:
+<screen>
+&rootprompt; rcldap start
+&rootprompt; chkconfig ldap on
+</screen>
+		On Red Hat Linux, execute the following:
+<screen>
+&rootprompt; service ldap start
+&rootprompt; chkconfig ldap on
+</screen>
+		</para></step>
+
+		<step><para>
+	    <indexterm><primary>chkconfig</primary></indexterm>
+		<indexterm><primary>service</primary></indexterm>
+		<indexterm><primary>rcldap</primary></indexterm>
+		Go back to the master LDAP server. Execute the following to start LDAP as well
+		as <command>slurpd</command>, the synchronization daemon, as shown here:
+<screen>
+&rootprompt; rcldap start
+&rootprompt; chkconfig ldap on
+&rootprompt; rcslurpd start
+&rootprompt; chkconfig slurpd on
+</screen>
+	    <indexterm><primary>slurpd</primary></indexterm>
+		On Red Hat Linux, check the equivalent command to start <command>slurpd</command>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>smbldap-useradd</primary></indexterm>
+		On the master LDAP server you may now add an account to validate that replication
+		is working. Assuming the configuration shown in <link linkend="happy"/>, execute:
+<screen>
+&rootprompt; /var/lib/samba/sbin/smbldap-useradd -a fruitloop
+</screen>
+		</para></step>
+
+		<step><para>
+		On the slave LDAP server, change to the directory <filename>/var/lib/ldap</filename>.
+		There should now be a file called <filename>replogfile</filename>. If replication worked
+		as expected, the content of this file should be:
+<screen>
+time: 1072486403
+dn: uid=fruitloop,ou=People,dc=abmas,dc=biz
+changetype: modify
+replace: sambaProfilePath
+sambaProfilePath: \\MASSIVE\profiles\fruitloop
+-
+replace: sambaHomePath
+sambaHomePath: \\MASSIVE\homes
+-
+replace: entryCSN
+entryCSN: 2003122700:43:38Z#0x0005#0#0000
+-
+replace: modifiersName
+modifiersName: cn=Manager,dc=abmas,dc=biz
+-
+replace: modifyTimestamp
+modifyTimestamp: 20031227004338Z
+-
+</screen>
+		</para></step>
+
+		<step><para>
+		Given that this first slave LDAP server is now working correctly, you may now
+		implement additional slave LDAP servers as required.
+		</para></step>
+
+		<step><para>
+		On each machine (PDC and BDCs) after the respective &smb.conf; files have been created as shown in
+		<link linkend="ch7-massmbconfA">Primary Domain Controller &smb.conf; File &smbmdash; Part A + B + C</link> and
+		on BDCs the <link linkend="ch7-slvsmbocnfA">Backup Domain Controller &smb.conf; File &smbmdash; Part A
+		+ B + C</link> execute the following:
+<screen>
+&rootprompt; smbpasswd -w buttercup
+</screen>
+		This will install in the <filename>secrets.tdb</filename> file the password that Samba will need to
+		manage (write to) the LDAP Master server to perform account updates.
+		</para></step>
+
+	</procedure>
+
+<example id="ch7-LDAP-master">
+<title>LDAP Master Server Configuration File &smbmdash; <filename>/etc/openldap/slapd.conf</filename></title>
+<screen>
+include     /etc/openldap/schema/core.schema
+include     /etc/openldap/schema/cosine.schema
+include     /etc/openldap/schema/inetorgperson.schema
+include     /etc/openldap/schema/nis.schema
+include     /etc/openldap/schema/samba.schema
+
+pidfile     /var/run/slapd/slapd.pid
+argsfile    /var/run/slapd/slapd.args
+
+database    bdb
+suffix      "dc=abmas,dc=biz"
+rootdn      "cn=Manager,dc=abmas,dc=biz"
+
+# rootpw = not24get
+rootpw      {SSHA}86kTavd9Dw3FAz6qzWTrCOKX/c0Qe+UV
+
+replica     host=lapdc.abmas.biz:389
+            suffix="dc=abmas,dc=biz"
+            binddn="cn=updateuser,dc=abmas,dc=biz"
+            bindmethod=simple credentials=not24get
+
+access to attrs=sambaLMPassword,sambaNTPassword
+           by dn="cn=sambaadmin,dc=abmas,dc=biz" write
+           by * none
+
+replogfile  /var/lib/ldap/replogfile
+
+directory   /var/lib/ldap
+
+# Indices to maintain
+index objectClass           eq
+index cn                    pres,sub,eq
+index sn                    pres,sub,eq
+index uid                   pres,sub,eq
+index displayName           pres,sub,eq
+index uidNumber             eq
+index gidNumber             eq
+index memberUID             eq
+index sambaSID              eq
+index sambaPrimaryGroupSID  eq
+index sambaDomainName       eq
+index default               sub
+</screen>
+</example>
+
+<example id="ch7-LDAP-slave">
+<title>LDAP Slave Configuration File &smbmdash; <filename>/etc/openldap/slapd.conf</filename></title>
+<screen>
+include     /etc/openldap/schema/core.schema
+include     /etc/openldap/schema/cosine.schema
+include     /etc/openldap/schema/inetorgperson.schema
+include     /etc/openldap/schema/nis.schema
+include     /etc/openldap/schema/samba.schema
+
+pidfile     /var/run/slapd/slapd.pid
+argsfile    /var/run/slapd/slapd.args
+
+database    bdb
+suffix      "dc=abmas,dc=biz"
+rootdn      "cn=Manager,dc=abmas,dc=biz"
+
+# rootpw = not24get
+rootpw      {SSHA}86kTavd9Dw3FAz6qzWTrCOKX/c0Qe+UV
+
+access to *
+            by dn=cn=updateuser,dc=abmas,dc=biz write
+            by * read
+
+updatedn    cn=updateuser,dc=abmas,dc=biz
+updateref   ldap://massive.abmas.biz
+
+directory   /var/lib/ldap
+
+# Indices to maintain
+index objectClass           eq
+index cn                    pres,sub,eq
+index sn                    pres,sub,eq
+index uid                   pres,sub,eq
+index displayName           pres,sub,eq
+index uidNumber             eq
+index gidNumber             eq
+index memberUID             eq
+index sambaSID              eq
+index sambaPrimaryGroupSID  eq
+index sambaDomainName       eq
+index default               sub
+</screen>
+</example>
+
+<example id="ch7-massmbconfA">
+<title>Primary Domain Controller &smb.conf; File &smbmdash; Part A</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="unix charset">LOCALE</smbconfoption>
+<smbconfoption name="workgroup">MEGANET2</smbconfoption>
+<smbconfoption name="passdb backend">ldapsam:ldap://massive.abmas.biz</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="log level">1</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+<smbconfoption name="max log size">0</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+<smbconfoption name="time server">Yes</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="add user script">/opt/IDEALX/sbin/smbldap-useradd -m '%u'</smbconfoption>
+<smbconfoption name="delete user script">/opt/IDEALX/sbin/smbldap-userdel '%u'</smbconfoption>
+<smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd -p '%g'</smbconfoption>
+<smbconfoption name="delete group script">/opt/IDEALX/sbin/smbldap-groupdel '%g'</smbconfoption>
+<smbconfoption name="add user to group script">/opt/IDEALX/sbin/smbldap-groupmod -m '%g' '%u'</smbconfoption>
+<smbconfoption name="delete user from group script">/opt/IDEALX/sbin/smbldap-groupmod -x '%g' '%u'</smbconfoption>
+<smbconfoption name="set primary group script">/opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'</smbconfoption>
+<smbconfoption name="add machine script">/opt/IDEALX/sbin/smbldap-useradd -w '%u'</smbconfoption>
+<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
+<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
+<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
+<smbconfoption name="logon drive">X:</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="domain master">Yes</smbconfoption>
+<smbconfoption name="wins support">Yes</smbconfoption>
+<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
+<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=sambaadmin,dc=abmas,dc=biz</smbconfoption>
+<smbconfoption name="idmap backend">ldap://massive.abmas.biz</smbconfoption>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+<smbconfoption name="printer admin">root</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch7-massmbconfB">
+<title>Primary Domain Controller &smb.conf; File &smbmdash; Part B</title>
+<smbconfblock>
+<smbconfsection name="[IPC$]"/>
+<smbconfoption name="path">/tmp</smbconfoption>
+
+<smbconfsection name="[accounts]"/>
+<smbconfoption name="comment">Accounting Files</smbconfoption>
+<smbconfoption name="path">/data/accounts</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[service]"/>
+<smbconfoption name="comment">Financial Services Files</smbconfoption>
+<smbconfoption name="path">/data/service</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[pidata]"/>
+<smbconfoption name="comment">Property Insurance Files</smbconfoption>
+<smbconfoption name="path">/data/pidata</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch7-massmbconfC">
+<title>Primary Domain Controller &smb.conf; File &smbmdash; Part C</title>
+<smbconfblock>
+<smbconfsection name="[apps]"/>
+<smbconfoption name="comment">Application Files</smbconfoption>
+<smbconfoption name="path">/apps</smbconfoption>
+<smbconfoption name="admin users">bjones</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">Network Logon Service</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+<smbconfoption name="admin users">root, Administrator</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="locking">No</smbconfoption>
+
+<smbconfsection name="[profiles]"/>
+<smbconfoption name="comment">Profile Share</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="profile acls">Yes</smbconfoption>
+
+<smbconfsection name="[profdata]"/>
+<smbconfoption name="comment">Profile Data Share</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/profdata</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="profile acls">Yes</smbconfoption>
+
+<smbconfsection name="[print$]"/>
+<smbconfoption name="comment">Printer Drivers</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
+<smbconfoption name="write list">root</smbconfoption>
+<smbconfoption name="admin users">root, Administrator</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch7-slvsmbocnfA">
+<title>Backup Domain Controller &smb.conf; File &smbmdash; Part A</title>
+<smbconfblock>
+<smbconfcomment># Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="unix charset">LOCALE</smbconfoption>
+<smbconfoption name="workgroup">MEGANET2</smbconfoption>
+<smbconfoption name="netbios name">BLDG1</smbconfoption>
+<smbconfoption name="passdb backend">ldapsam:ldap://lapdc.abmas.biz</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="log level">1</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+<smbconfoption name="max log size">50</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
+<smbconfoption name="logon drive">X:</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="os level">63</smbconfoption>
+<smbconfoption name="domain master">No</smbconfoption>
+<smbconfoption name="wins server">192.168.2.1</smbconfoption>
+<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
+<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=sambaadmin,dc=abmas,dc=biz</smbconfoption>
+<smbconfoption name="utmp">Yes</smbconfoption>
+<smbconfoption name="idmap backend">ldap://massive.abmas.biz</smbconfoption>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+
+<smbconfsection name="[accounts]"/>
+<smbconfoption name="comment">Accounting Files</smbconfoption>
+<smbconfoption name="path">/data/accounts</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[service]"/>
+<smbconfoption name="comment">Financial Services Files</smbconfoption>
+<smbconfoption name="path">/data/service</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch7-slvsmbocnfB">
+<title>Backup Domain Controller &smb.conf; File &smbmdash; Part B</title>
+<smbconfblock>
+<smbconfsection name="[pidata]"/>
+<smbconfoption name="comment">Property Insurance Files</smbconfoption>
+<smbconfoption name="path">/data/pidata</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[apps]"/>
+<smbconfoption name="comment">Application Files</smbconfoption>
+<smbconfoption name="path">/apps</smbconfoption>
+<smbconfoption name="admin users">bjones</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">Network Logon Service</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="locking">No</smbconfoption>
+
+<smbconfsection name="[profiles]"/>
+<smbconfoption name="comment">Profile Share</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="profile acls">Yes</smbconfoption>
+
+<smbconfsection name="[profdata]"/>
+<smbconfoption name="comment">Profile Data Share</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/profdata</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="profile acls">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+	<sect2>
+		<title>Key Points Learned</title>
+
+		<itemizedlist>
+			<listitem><para>
+			<indexterm><primary>LDAP</primary></indexterm><indexterm><primary>BDC</primary></indexterm>
+			Where Samba-3 is used as a domain controller, the use of LDAP is an 
+			essential component to permit the use of BDCs.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>wide-area</primary></indexterm>
+			Replication of the LDAP master server to create a network of BDCs
+			is an important mechanism for limiting WAN traffic.
+			</para></listitem>
+
+			<listitem><para>
+			Network administration presents many complex challenges, most of which
+			can be satisfied by good design but that also require sound communication
+			and unification of management practices. This can be highly challenging in
+			a large, globally distributed network.
+			</para></listitem>
+
+			<listitem><para>
+			Roaming profiles must be contained to the local network segment. Any
+			departure from this may clog wide-area arteries and slow legitimate network
+			traffic to a crawl.
+			</para></listitem>
+		</itemizedlist>
+
+	</sect2>
+
+	<figure id="chap7net">
+		<title>Network Topology &smbmdash; 2000 User Complex Design A</title>
+		<imagefile scale="80">chap7-net-Ar</imagefile>
+	</figure>
+
+	<figure id="chap7net2">
+		<title>Network Topology &smbmdash; 2000 User Complex Design B</title>
+		<imagefile scale="80">chap7-net2-Br</imagefile>
+	</figure>
+
+</sect1>
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	There is much rumor and misinformation regarding the use of MS Windows networking protocols.
+	These questions are just a few of those frequently asked.
+	</para>
+
+	<qandaset defaultlabel="chap07qa" type="number">
+	<qandaentry>
+	<question>
+
+	    <para>
+		<indexterm><primary>DHCP</primary></indexterm>
+		<indexterm><primary>network</primary><secondary>bandwidth</secondary></indexterm>
+		Is it true that DHCP uses lots of WAN bandwidth?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para>
+		<indexterm><primary>DHCP</primary><secondary>Relay Agent</secondary></indexterm>
+		<indexterm><primary>routers</primary></indexterm>
+		<indexterm><primary>DHCP</primary><secondary>servers</secondary></indexterm>
+		It is a smart practice to localize DHCP servers on each network segment. As a 
+		rule, there should be two DHCP servers per network segment. This means that if
+		one server fails, there is always another to service user needs. DHCP requests use
+		only UDP broadcast protocols. It is possible to run a DHCP Relay Agent on network
+		routers. This makes it possible to run fewer DHCP servers.
+		</para>
+
+	    <para>
+		<indexterm><primary>DHCP</primary><secondary>request</secondary></indexterm>
+		<indexterm><primary>DHCP</primary><secondary>traffic</secondary></indexterm>
+		A DHCP network address request and confirmation usually results in about six UDP packets.
+		The packets are from 60 to 568 bytes in length. Let us consider a site that has 300 DHCP
+		clients and that uses a 24-hour IP address lease. This means that all clients renew
+		their IP address lease every 24 hours. If we assume an average packet length equal to the
+		maximum (just to be on the safe side), and we have a 128 Kb/sec wide-area connection, 
+		how significant would the DHCP traffic be if all of it were to use DHCP Relay?
+		</para>
+
+		<para>
+		I must stress that this is a bad design, but here is the calculation:
+<screen>
+Daily Network Capacity: 128,000 (Kbits/s) / 8 (bits/byte) 
+                             x 3600 (sec/hr) x 24 (hrs/day)= 2288 Mbytes/day.
+
+DHCP traffic:          300 (clients) x 6 (packets) 
+                                       x 512 (bytes/packet) = 0.9 Mbytes/day.
+</screen>
+		From this can be seen that the traffic impact would be minimal.
+		</para>
+
+	    <para>
+		<indexterm><primary>DNS</primary><secondary>Dynamic</secondary></indexterm>
+		<indexterm><primary>DHCP</primary></indexterm>
+		Even when DHCP is configured to do DNS update (dynamic DNS) over a wide-area link,
+		the impact of the update is no more than the DHCP IP address renewal traffic and thus
+		still insignificant for most practical purposes.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para>
+		<indexterm><primary>background communication</primary></indexterm>
+		<indexterm><primary>LDAP</primary><secondary>master/slave</secondary><tertiary>background communication</tertiary></indexterm>
+		How much background communication takes place between a master LDAP server and its slave LDAP servers?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para>
+		<indexterm><primary>slurpd</primary></indexterm>
+		The process that controls the replication of data from the master LDAP server to the slave LDAP
+		servers is called <command>slurpd</command>. The <command>slurpd</command> remains nascent (quiet)
+		until an update must be propagated. The propagation traffic per LDAP slave to update (add/modify/delete)
+		two user accounts requires less than 10KB traffic.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		LDAP has a database. Is LDAP not just a fancy database front end?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para>
+		<indexterm><primary>database</primary></indexterm>
+		<indexterm><primary>LDAP</primary><secondary>database</secondary></indexterm>
+		<indexterm><primary>SQL</primary></indexterm>
+		<indexterm><primary>transactional</primary></indexterm>
+		LDAP does store its data in a database of sorts. In fact, the LDAP backend is an application-specific
+		data storage system. This type of database is indexed so that records can be rapidly located, but the
+		database is not generic and can be used only in particular pre-programmed ways. General external
+		applications do not gain access to the data. This type of database is used also by SQL servers. Both
+		an SQL server and an LDAP server provide ways to access the data. An SQL server has a transactional
+		orientation and typically allows external programs to perform ad hoc queries, even across data tables.
+		An LDAP front end is a purpose-built tool that has a search orientation that is designed around specific
+		simple queries. The term <constant>database</constant> is heavily overloaded and thus much misunderstood.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para>
+		<indexterm><primary>OpenLDAP</primary></indexterm>
+		Can Active Directory obtain account information from an OpenLDAP server?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para>
+		<indexterm><primary>meta-directory</primary></indexterm>
+		No, at least not directly. It is possible to provision Active Directory from and/or to an OpenLDAP
+		database through use of a metadirectory server. Microsoft MMS (now called MIIS) can interface
+		to OpenLDAP using standard LDAP queries and updates. 
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What are the parts of a roaming profile? How large is each part?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>roaming profile</primary>
+	      </indexterm>
+		A roaming profile consists of
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			Desktop folders such as <constant>Desktop</constant>, <constant>My Documents</constant>,
+			<constant>My Pictures</constant>, <constant>My Music</constant>, <constant>Internet Files</constant>,
+			<constant>Cookies</constant>, <constant>Application Data</constant>,
+			<constant>Local Settings,</constant> and more. See <link linkend="happy"/>, <link linkend="XP-screen001"/>.
+			</para>
+
+			<para>
+			<indexterm><primary>folder redirection</primary></indexterm>
+			Each of these can be anywhere from a few bytes to gigabytes in capacity. Fortunately, all
+			such folders can be redirected to network drive resources. See <link linkend="redirfold"/>
+			for more information regarding folder redirection.
+			</para></listitem>
+
+			<listitem><para>
+			A static or rewritable portion that is typically only a few files (2-5 KB of information).
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>NTUSER.DAT</primary></indexterm>
+			<indexterm><primary>HKEY_LOCAL_USER</primary></indexterm>
+			The registry load file that modifies the <constant>HKEY_LOCAL_USER</constant> hive. This is
+			the <filename>NTUSER.DAT</filename> file. It can be from 0.4 to 1.5 MB.
+			</para></listitem>
+		</itemizedlist>
+
+	    <para>
+		<indexterm><primary>Microsoft Outlook</primary><secondary>PST files</secondary></indexterm>
+		Microsoft Outlook PST files may be stored in the <constant>Local Settings\Application Data</constant>
+		folder. It can be up to 2 GB in size per PST file.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Can the <constant>My Documents</constant> folder be stored on a network drive?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para>
+		<indexterm><primary>UNC name</primary></indexterm>
+		<indexterm><primary>Universal Naming Convention</primary><see>UNC name</see></indexterm>
+		Yes. More correctly, such folders can be redirected to network shares. No specific network drive
+		connection is required. Registry settings permit this to be redirected directly to a UNC (Universal
+		Naming Convention) resource, though it is possible to specify a network drive letter instead of a
+		UNC name. See <link linkend="redirfold"/>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para>
+		<indexterm><primary>wide-area</primary></indexterm>
+		<indexterm><primary>network</primary><secondary>bandwidth</secondary></indexterm>
+		<indexterm><primary>WINS</primary></indexterm>
+		How much WAN bandwidth does WINS consume?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para>
+		<indexterm><primary>NetBIOS</primary><secondary>name cache</secondary></indexterm>
+		<indexterm><primary>WINS server</primary></indexterm>
+		<indexterm><primary>domain replication</primary></indexterm>
+		MS Windows clients cache information obtained from WINS lookups in a local NetBIOS name cache.
+		This keeps WINS lookups to a minimum. On a network with 3500 MS Windows clients and a central WINS
+		server, the total bandwidth demand measured at the WINS server, averaged over an 8-hour working day,
+		was less than 30 KB/sec. Analysis of network traffic over a 6-week period showed that the total
+		of all background traffic consumed about 11 percent of available bandwidth over 64 Kb/sec links.
+		Background traffic consisted of domain replication, WINS queries, DNS lookups, and authentication
+		traffic. Each of 11 branch offices had a 64 Kb/sec wide-area link, with a 1.5 Mb/sec main connection
+		that aggregated the branch office connections plus an Internet connection.
+		</para>
+
+		<para>
+		In conclusion, the total load afforded through WINS traffic is again marginal to total operational
+		usage &smbmdash; as it should be.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		How many BDCs should I have? What is the right number of Windows clients per server?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		It is recommended to have at least one BDC per network segment, including the segment served
+		by the PDC. Actual requirements vary depending on the working load on each of the BDCs and the
+		load demand pattern of client usage. I have seen sites that function without problem with 200
+		clients served by one BDC, and yet other sites that had one BDC per 20 clients. In one particular
+		company, there was a drafting office that had 30 CAD/CAM operators served by one server, a print
+		server; and an application server. While all three were BDCs, typically only the print server would
+		service network logon requests after the first 10 users had started to use the network. This was
+		a reflection of the service load placed on both the application server and the data server.
+		</para>
+
+		<para>
+		As unsatisfactory as the answer might sound, it all depends on network and server load
+		characteristics.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para>
+		<indexterm><primary>NIS server</primary></indexterm><indexterm><primary>LDAP</primary></indexterm>
+		I've heard that you can store NIS accounts in LDAP. Is LDAP not just a smarter way to
+		run an NIS server?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The correct answer to both questions is yes. But do understand that an LDAP server has
+		a configurable schema that can store far more information for many more purposes than
+		just NIS.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Can I use NIS in place of LDAP?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para>
+		<indexterm><primary>NIS</primary></indexterm>
+		<indexterm><primary>NIS schema</primary></indexterm>
+		No. The NIS database does not have provision to store Microsoft encrypted passwords and does not deal
+		with the types of data necessary for interoperability with Microsoft Windows networking. The use
+		of LDAP with Samba requires the use of a number of schemas, one of which is the NIS schema, but also
+		a Samba-specific schema extension.
+		</para>
+
+</answer>
+	</qandaentry>
+
+	</qandaset>
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-500UserNetwork.xml b/docs-xml/Samba3-ByExample/SBE-500UserNetwork.xml
new file mode 100644
index 00000000000..776d114257f
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-500UserNetwork.xml
@@ -0,0 +1,2011 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="Big500users">
+  <title>The 500-User Office</title>
+
+	<para>
+	The Samba-3 networking you explored in <link linkend="secure"/> covers the finer points of 
+	configuration of peripheral services such as DHCP and DNS, and WINS. You experienced
+	implementation of a simple configuration of the services that are important adjuncts 
+	to successful deployment of Samba. 
+	</para>
+
+	<para>
+	An analysis of the history of postings to the Samba mailing list easily demonstrates 
+	that the two most prevalent Samba problem areas are
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Defective resolution of a NetBIOS name to its IP address
+		</para></listitem>
+
+		<listitem><para>
+		Printing problems
+		</para></listitem>
+
+	</itemizedlist>
+
+	<para>
+	The exercises
+	so far in this book have focused on implementation of the simplest printing processes
+	involving  no print job processing intelligence. In this chapter, you maintain 
+	that same approach to printing, but <link linkend="happy"/> presents an opportunity 
+	to make printing more complex for the administrator while making it easier for the user.
+	</para>
+
+	<para>
+	<indexterm><primary>WINS server</primary></indexterm>
+	<indexterm><primary>tdbsam</primary></indexterm>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	<link linkend="secure"/> demonstrates operation of a DHCP server and a DNS server 
+	as well as a central WINS server. You validated the operation of these services and
+	saw an effective implementation of a Samba domain controller using the 
+	<parameter>tdbsam</parameter> passdb backend.
+	</para>
+
+	<para>
+	The objective of this chapter is to introduce more complex techniques that can be used to
+	improve manageability of Samba as networking needs grow. In this chapter, you implement
+	a distributed DHCP server environment, a distributed DNS server arrangement, a centralized
+	WINS server, and a centralized Samba domain controller.
+	</para>
+
+	<para>
+	A note of caution is important regarding the Samba configuration that is used in this
+	chapter. The use of a single domain controller on a routed, multisegment network is 
+	a poor design choice that leads to potential network user complaints. 
+	This chapter demonstrates some successful 
+	techniques in deployment and configuration management. This should be viewed as a 
+	foundation chapter for complex Samba deployments.
+	</para>
+
+	<para>
+	As you master the techniques presented here, you may find much better methods to 
+	improve network management and control while reducing human resource overheads.
+	You should take the opportunity to innovate and expand on the methods presented 
+	here and explore them to the fullest.
+	</para>
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>
+	Business continues to go well for Abmas. Mr. Meany is driving your success and the
+	network continues to grow thanks to the hard work Christine has done. You recently
+	hired Stanley Soroka as manager of information systems. Christine recommended Stan
+	to the role. She told you Stan is so good at handling Samba that he can make a cast
+	iron rocking horse that is embedded in concrete kick like a horse at a rodeo. You
+	need skills like his. Christine and Stan get along just fine. Let's see what 
+	you can get out of this pair as they plot the next-generation networks.
+	</para>
+
+	<para>
+	Ten months ago Abmas closed an acquisition of a property insurance business. The
+	founder lost interest in the business and decided to sell it to Mr. Meany.  Because
+	they were former university classmates, the purchase was concluded with mutual assent.
+	The acquired business is located at the other end of town in much larger facilities.
+	The old Abmas building has become too small. Located on the same campus as the newly
+	acquired business are two empty buildings that are ideal to provide Abmas with
+	opportunity for growth.
+	</para>
+
+	<para>
+	Abmas has now completed the purchase of the two empty buildings, and you are
+	to install a new network and relocate staff in nicely furnished new facilities.
+	The new network is to be used to fully integrate company operations. You have
+	decided to locate the new network operations control center in the larger building
+	in which the insurance group is located to take advantage of an ideal floor space
+	and to allow Stan and Christine to fully stage the new network and test it before
+	it is rolled out. Your strategy is to complete the new network so that it
+	is ready for operation when the old office moves into the new premises.
+	</para>
+
+	<sect2>
+		<title>Assignment Tasks</title>
+
+		<para>
+		The acquired business had 280 network users. The old Abmas building housed
+		220 network users in unbelievably cramped conditions. The network that
+		initially served 130 users now handles 220 users quite well.
+		</para>
+
+		<para>
+		The two businesses will be fully merged to create a single campus company.
+		The Property Insurance Group (PIG) houses 300 employees, the new Accounting
+		Services Group (ASG) will be in a small building (BLDG1) that houses 50 
+		employees, and the Financial Services Group (FSG) will be housed in a large
+		building that has capacity for growth (BLDG2). Building 2 houses 150 network
+		users.
+		</para>
+
+		<para>
+		You have decided to connect the building using fiber optic links between new
+		routers. As a backup, the buildings are interconnected using line-of-sight
+		high-speed infrared facilities. The infrared connection provides a
+		secondary route to be used during periods of high demand for network
+		bandwidth.
+		</para>
+
+		<para>
+		The Internet gateway is upgraded to 15 Mb/sec service. Your ISP
+		provides on your premises a fully managed Cisco PIX firewall. You no longer need
+		to worry about firewall facilities on your network.
+		</para>
+
+		<para>
+		Stanley and Christine have purchased new server hardware. Christine wants to
+		roll out a network that has whistles and bells. Stan wants to start off with
+		a simple to manage, not-too-complex network. He believes that network
+		users need to be gradually introduced to new features and capabilities and not
+		rushed into an environment that may cause disorientation and loss of productivity.
+		</para>
+
+		<para>
+		Your intrepid network team has decided to implement a network configuration
+		that closely mirrors the successful system you installed in the old Abmas building.
+		The new network infrastructure is owned by Abmas, but all desktop systems
+		are being procured through a new out-source services and leasing company. Under
+		the terms of a deal with Mr. M. Proper (CEO), DirectPointe, Inc., provides
+		all desktop systems and includes full level-one help desk support for 
+		a flat per-machine monthly fee. The deal allows you to add workstations on demand.
+		This frees Stan and Christine to deal with deeper issues as they emerge and 
+		permits Stan to work on creating new future value-added services.
+		</para>
+
+		<para>
+		DirectPointe Inc. receives from you a new standard desktop configuration
+		every four months. They automatically roll that out to each desktop system.
+		You must keep DirectPointe informed of all changes.
+		</para>
+
+	<para><indexterm>
+	    <primary>PDC</primary>
+	  </indexterm>
+		The new network has a single Samba Primary Domain Controller (PDC) located in the
+		Network Operation Center (NOC). Buildings 1 and 2 each have a local server
+		for local application servicing. It is a domain member. The new system
+		uses the <parameter>tdbsam</parameter> passdb backend.
+		</para>
+
+		<para>
+		Printing is based on raw pass-through facilities just as it has been used so far.
+		All printer drivers are installed on the desktop and notebook computers.
+		</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+	<title>Dissection and Discussion</title>
+
+	<para>
+	<indexterm><primary>network load factors</primary></indexterm>
+	The example you are building in this chapter is of a network design that works, but this
+	does not make it a design that is recommended. As a general rule, there should be at least
+	one Backup Domain Controller (BDC) per 150 Windows network clients. The principle behind
+	this recommendation is that correct operation of MS Windows clients requires rapid
+	network response to all SMB/CIFS requests. The same rule says that if there are more than
+	50 clients per domain controller, they are too busy to service requests. Let's put such
+	rules aside and recognize that network load affects the integrity of domain controller
+	responsiveness. This network will have 500 clients serviced by one central domain
+	controller. This is not a good omen for user satisfaction. You, of course, address this
+	very soon (see <link linkend="happy"/>).
+	</para>
+
+	<sect2>
+		<title>Technical Issues</title>
+
+		<para>
+		Stan has talked you into a horrible compromise, but it is addressed. Just make
+		certain that the performance of this network is well validated before going live.
+		</para>
+
+		<para>
+		Design decisions made in this design include the following:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			<indexterm><primary>PDC</primary></indexterm>
+			<indexterm><primary>LDAP</primary></indexterm>
+			<indexterm><primary>identity management</primary></indexterm>
+			A single PDC is being implemented. This limitation is based on the choice not to
+			use LDAP. Many network administrators fear using LDAP because of the perceived
+			complexity of implementation and management of an LDAP-based backend for all user
+			identity management as well as to store network access credentials.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>BDC</primary></indexterm>
+			<indexterm><primary>machine secret password</primary></indexterm>
+			Because of the refusal to use an LDAP (ldapsam) passdb backend at this time, the
+			only choice that makes sense with 500 users is to use the tdbsam passwd backend. 
+			This type of backend is not receptive to replication to BDCs.  If the tdbsam
+			<filename>passdb.tdb</filename> file is replicated to BDCs using
+			<command>rsync</command>, there are two potential problems: (1) data that is in
+			memory but not yet written to disk will not be replicated, and (2) domain member
+			machines periodically change the secret machine password. When this happens, there
+			is no mechanism to return the changed password to the PDC.
+			</para></listitem>
+
+			<listitem><para>
+			All domain user, group, and machine accounts are managed on the PDC. This makes
+			for a simple mode of operation but has to be balanced with network performance and
+			integrity of operations considerations.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>WINS</primary></indexterm>
+			A single central WINS server is being used. The PDC is also the WINS server.
+			Any attempt to operate a routed network without a WINS server while using NetBIOS
+			over TCP/IP protocols does not work unless on each client the name resolution
+			entries for the PDC are added to the <filename>LMHOSTS</filename>. This file is
+			normally located on the Windows XP Professional client in the 
+			<filename>C:\WINDOWS\SYSTEM32\ETC\DRIVERS</filename> directory.
+			</para></listitem>
+
+			<listitem><para>
+			At this time the Samba WINS database cannot be replicated. That is
+			why a single WINS server is being implemented. This should work without a problem.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>winbindd</primary></indexterm>
+			BDCs make use of <command>winbindd</command> to provide
+			access to domain security credentials for file system access and object storage.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>DHCP</primary><secondary>relay</secondary></indexterm>
+			<indexterm><primary>DHCP</primary><secondary>requests</secondary></indexterm>
+			Configuration of Windows XP Professional clients is achieved using DHCP. Each
+			subnet has its own DHCP server. Backup DHCP serving is provided by one
+			alternate DHCP server. This necessitates enabling of the DHCP Relay agent on
+			all routers. The DHCP Relay agent must be programmed to pass DHCP Requests from the
+			network directed at the backup DHCP server.
+			</para></listitem>
+
+			<listitem><para>
+			All network users are granted the ability to print to any printer that is
+			network-attached. All printers are available from each server. Print jobs that
+			are spooled to a printer that is not on the local network segment are automatically
+			routed to the print spooler that is in control of that printer. The specific details
+			of how this might be done are demonstrated for one example only.
+			</para></listitem>
+
+			<listitem><para>
+			The network address and subnetmask chosen provide 1022 usable IP addresses in
+			each subnet. If in the future more addresses are required, it would make sense
+			to add further subnets rather than change addressing.
+			</para></listitem>
+
+		</itemizedlist>
+
+	</sect2>
+
+
+	<sect2>
+		<title>Political Issues</title>
+
+		<para>
+		This case gets close to the real world. You and I know the right way to implement
+		domain control. Politically, we have to navigate a minefield. In this case, the need is to
+		get the PDC rolled out in compliance with expectations and also to be ready to save the day
+		by having the real solution ready before it is needed. That real solution is presented in
+		<link linkend="happy"/>.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Implementation</title>
+
+	<para>
+	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>
+
+	<figure id="chap05net">
+		<title>Network Topology &smbmdash; 500 User Network Using tdbsam passdb backend.</title>
+		<imagefile scale="50">chap5-net</imagefile>
+	</figure>
+
+	<sect2 id="ch5-dnshcp-setup">
+	<title>Installation of DHCP, DNS, and Samba Control Files</title>
+
+	<para>
+	Carefully install the configuration files into the correct locations as shown in 
+	<link linkend="ch5-filelocations"/>. You should validate that the full file path is
+	correct as shown.
+	</para>
+
+	<para>
+	The abbreviation shown in this table as <constant>{VLN}</constant> refers to
+	the directory location beginning with <filename>/var/lib/named</filename>.
+	</para>
+
+
+	<table id="ch5-filelocations"><title>Domain: <constant>MEGANET</constant>, File Locations for Servers</title>
+		<tgroup cols="5">
+			<colspec colname='c1' align="left"/>
+			<colspec colname='c2' align="left"/>
+			<colspec colname='c3' align="center"/>
+			<colspec colname='c4' align="center"/>
+			<colspec colname='c5' align="center"/>
+			<thead>
+				<row>
+					<entry align="center" namest='c1' nameend='c2'>File Information</entry>
+					<entry align="center" namest="c3" nameend="c5">Server Name</entry>
+				</row>
+				<row>
+					<entry align="center">Source</entry>
+					<entry align="center">Target Location</entry>
+					<entry align="center">MASSIVE</entry>
+					<entry align="center">BLDG1</entry>
+					<entry align="center">BLDG2</entry>
+				</row>
+			</thead>
+			<tbody>
+				<row>
+					<entry><link linkend="ch5-massivesmb"/></entry>
+					<entry><filename>/etc/samba/smb.conf</filename></entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="ch5-dc-common"/></entry>
+					<entry><filename>/etc/samba/dc-common.conf</filename></entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="ch5-commonsmb"/></entry>
+					<entry><filename>/etc/samba/common.conf</filename></entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry><link linkend="ch5-bldg1-smb"/></entry>
+					<entry><filename>/etc/samba/smb.conf</filename></entry>
+					<entry>No</entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="ch5-bldg2-smb"/></entry>
+					<entry><filename>/etc/samba/smb.conf</filename></entry>
+					<entry>No</entry>
+					<entry>No</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry><link linkend="ch5-dommem-smb"/></entry>
+					<entry><filename>/etc/samba/dommem.conf</filename></entry>
+					<entry>No</entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry><link linkend="massive-dhcp"/></entry>
+					<entry><filename>/etc/dhcpd.conf</filename></entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="bldg1dhcp"/></entry>
+					<entry><filename>/etc/dhcpd.conf</filename></entry>
+					<entry>No</entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="bldg2dhcp"/></entry>
+					<entry><filename>/etc/dhcpd.conf</filename></entry>
+					<entry>No</entry>
+					<entry>No</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry><link linkend="massive-nameda"/></entry>
+					<entry><filename>/etc/named.conf (part A)</filename></entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="massive-namedb"/></entry>
+					<entry><filename>/etc/named.conf (part B)</filename></entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="massive-namedc"/></entry>
+					<entry><filename>/etc/named.conf (part C)</filename></entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="abmasbizdns"/></entry>
+					<entry><filename>{VLN}/master/abmas.biz.hosts</filename></entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="abmasusdns"/></entry>
+					<entry><filename>{VLN}/master/abmas.us.hosts</filename></entry>
+					<entry>Yes</entry>
+					<entry>No</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry><link linkend="bldg12nameda"/></entry>
+					<entry><filename>/etc/named.conf (part A)</filename></entry>
+					<entry>No</entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry><link linkend="bldg12namedb"/></entry>
+					<entry><filename>/etc/named.conf (part B)</filename></entry>
+					<entry>No</entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry><link linkend="loopback"/></entry>
+					<entry><filename>{VLN}/localhost.zone</filename></entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry><link linkend="dnsloopy"/></entry>
+					<entry><filename>{VLN}/127.0.0.zone</filename></entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry><link linkend="roothint"/></entry>
+					<entry><filename>{VLN}/root.hint</filename></entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+					<entry>Yes</entry>
+				</row>
+			</tbody>
+		</tgroup>
+	</table>
+
+	</sect2>
+
+	<sect2>
+	<title>Server Preparation: All Servers</title>
+
+	<para>
+	The following steps apply to all servers. Follow each step carefully.
+	</para>
+
+		<procedure>
+		<title>Server Preparation Steps</title>
+
+			<step><para>
+			Using the UNIX/Linux system tools, set the name of the server as shown in the network
+			topology diagram in <link linkend="chap05net"/>. For SUSE Linux products, the tool
+			that permits this is called <command>yast2</command>; for Red Hat Linux products,
+			you can use the <command>netcfg</command> tool.
+			Verify that your hostname is correctly set by running:
+<screen>
+&rootprompt; uname -n
+</screen>
+			An alternate method to verify the hostname is:
+<screen>
+&rootprompt; hostname -f
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>/etc/hosts</primary></indexterm>
+			<indexterm><primary>named</primary></indexterm>
+			Edit your <filename>/etc/hosts</filename> file to include the primary names and addresses
+			of all network interfaces that are on the host server. This is necessary so that during
+			startup the system is able to resolve all its own names to the IP address prior to
+			startup of the DNS server. You should check the startup order of your system. If the 
+			CUPS print server is started before the DNS server (<command>named</command>), you 
+			should also include an entry for the printers in the <filename>/etc/hosts</filename> file.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>/etc/resolv.conf</primary></indexterm>
+			All DNS name resolution should be handled locally. To ensure that the server is configured
+			correctly to handle this, edit <filename>/etc/resolv.conf</filename> so it has the following
+			content:
+<screen>
+search abmas.us abmas.biz
+nameserver 127.0.0.1
+</screen>
+			This instructs the name resolver function (when configured correctly) to ask the DNS server
+			that is running locally to resolve names to addresses.
+			</para></step>
+
+
+			<step><para>
+			<indexterm><primary>administrator</primary></indexterm>
+			<indexterm><primary>smbpasswd</primary></indexterm>
+			Add the <constant>root</constant> user to the password backend:
+<screen>
+&rootprompt; smbpasswd -a root
+New SMB password: XXXXXXXX
+Retype new SMB password: XXXXXXXX
+&rootprompt;
+</screen>
+			The <constant>root</constant> account is the UNIX equivalent of the Windows domain administrator.
+			This account is essential in the regular maintenance of your Samba server. It must never be
+			deleted. If for any reason the account is deleted, you may not be able to recreate this account
+			without considerable trouble.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>username map</primary></indexterm>
+			<indexterm><primary>/etc/samba/smbusers</primary></indexterm>
+			Create the username map file to permit the <constant>root</constant> account to be called
+			<constant>Administrator</constant> from the Windows network environment. To do this, create
+			the file <filename>/etc/samba/smbusers</filename> with the following contents:
+<screen>
+####
+# User mapping file
+####
+# File Format
+# -----------
+# Unix_ID = Windows_ID
+#
+# Examples:
+# root = Administrator
+# janes = "Jane Smith"
+# jimbo = Jim Bones
+#
+# Note: If the name contains a space it must be double quoted.
+#       In the example above the name 'jimbo' will be mapped to Windows
+#       user names 'Jim' and 'Bones' because the space was not quoted.
+#######################################################################
+root = Administrator
+####
+# End of File
+####
+</screen>
+			</para></step>
+
+			<step><para>
+			Configure all network-attached printers to have a fixed IP address.
+			</para></step>
+
+			<step><para>
+			Create an entry in the DNS database on the server <constant>MASSIVE</constant>
+			in both the forward lookup database for the zone <constant>abmas.biz.hosts</constant>
+			and in the reverse lookup database for the network segment that the printer is
+			located in. Example configuration files for similar zones were presented in <link linkend="secure"/>,
+			<link linkend="abmasbiz"/> and <link linkend="eth2zone"/>.
+			</para></step>
+
+			<step><para>
+			Follow the instructions in the printer manufacturer's manuals to permit printing 
+			to port 9100.  Use any other port the manufacturer specifies for direct mode, 
+			raw printing.  This allows the CUPS spooler to print using raw mode protocols.
+			<indexterm><primary>CUPS</primary></indexterm>
+			<indexterm><primary>raw printing</primary></indexterm>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>CUPS</primary><secondary>queue</secondary></indexterm>
+			Only on the server to which the printer is attached configure the CUPS Print 
+			Queues as follows:
+<screen>
+&rootprompt; lpadmin -p <parameter>printque</parameter> -v socket://<parameter>printer-name</parameter>.abmas.biz:9100 -E
+</screen>
+			<indexterm><primary>print filter</primary></indexterm>
+			This step creates the necessary print queue to use no assigned print filter. This
+			is ideal for raw printing, that is, printing without use of filters.
+			The name <parameter>printque</parameter> is the name you have assigned for
+			the particular printer.
+			</para></step>
+
+			<step><para>
+			Print queues may not be enabled at creation. Make certain that the queues
+			you have just created are enabled by executing the following:
+<screen>
+&rootprompt; /usr/bin/enable <parameter>printque</parameter>
+</screen>
+			</para></step>
+
+			<step><para>
+			Even though your print queue may be enabled, it is still possible that it
+			does not accept print jobs. A print queue services incoming printing
+			requests only when configured to do so. Ensure that your print queue is
+			set to accept incoming jobs by executing the following command:
+<screen>
+&rootprompt; /usr/bin/accept <parameter>printque</parameter>
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>mime type</primary></indexterm>
+			<indexterm><primary>/etc/mime.convs</primary></indexterm>
+			<indexterm><primary>application/octet-stream</primary></indexterm>
+			This step, as well as the next one, may be omitted where CUPS version 1.1.18
+			or later is in use.  Although it does no harm to follow it anyway, and may
+			help to avoid time spent later trying to figure out why print jobs may be
+			disappearing without a trace. Look at these two steps as <emphasis>insurance</emphasis>
+			against lost time. Edit file <filename>/etc/cups/mime.convs</filename> to 
+			uncomment the line:
+<screen>
+application/octet-stream     application/vnd.cups-raw      0     -
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>/etc/mime.types</primary></indexterm>
+			Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
+<screen>
+application/octet-stream
+</screen>
+			</para></step>
+
+			<step><para>
+			Refer to the CUPS printing manual for instructions regarding how to configure
+			CUPS so that print queues that reside on CUPS servers on remote networks
+			route print jobs to the print server that owns that queue. The default setting
+			on your CUPS server may automatically discover remotely installed printers and
+			may permit this functionality without requiring specific configuration.
+			</para></step>
+
+			<step><para>
+			As part of the roll-out program, you need to configure the application's
+			server shares. This can be done once on the central server and may then be
+			replicated using a tool such as <command>rsync</command>. Refer to the man
+			page for <command>rsync</command> for details regarding use. The notes in	
+			<link linkend="ch4appscfg"/> may help in your decisions to use an application
+			server facility.
+			</para></step>
+
+		</procedure>
+
+	<note><para>
+	Logon scripts that are run from a domain controller (PDC or BDC) are capable of using semi-intelligent
+	processes to automap Windows client drives to an application server that is nearest to the client. This
+	is considerably more difficult when a single PDC is used on a routed network. It can be done, but not
+	as elegantly as you see in the next chapter.
+	</para></note>
+
+	</sect2>
+
+	<sect2>
+	<title>Server-Specific Preparation</title>
+
+	<para>
+	There are some steps that apply to particular server functionality only. Each step is critical
+	to correct server operation. The following step-by-step installation guidance will assist you 
+	in working through the process of configuring the PDC and then both BDC's.
+	</para>
+
+		<sect3>
+		<title>Configuration for Server: <constant>MASSIVE</constant></title>
+
+		<para>
+		The steps presented here attempt to implement Samba installation in a generic manner. While
+		some steps are clearly specific to Linux, it should not be too difficult to apply them to
+		your platform of choice.
+		</para>
+
+		<procedure>
+		<title>Primary Domain Controller Preparation</title>
+
+			<step><para>
+			<indexterm><primary>/etc/rc.d/boot.local</primary></indexterm>
+			<indexterm><primary>IP forwarding</primary></indexterm>
+			The host server acts as a router between the two internal network segments as well
+			as for all Internet access. This necessitates that IP forwarding be enabled. This can be
+			achieved by adding to the <filename>/etc/rc.d/boot.local</filename> an entry as follows:
+<screen>
+echo 1 > /proc/sys/net/ipv4/ip_forward
+</screen>
+			To ensure that your kernel is capable of IP forwarding during configuration, you may wish to execute
+			that command manually also. This setting permits the Linux system to act as a router.
+			</para></step>
+
+			<step><para>
+			This server is dual hosted (i.e., has two network interfaces) &smbmdash; one goes to the Internet
+			and the other to a local network that has a router that is the gateway to the remote networks.
+			You must therefore configure the server with route table entries so that it can find machines
+			on the remote networks. You can do this using the appropriate system tools for your Linux
+			server or using static entries that you place in one of the system startup files. It is best
+			to always use the tools that the operating system vendor provided. In the case of SUSE Linux, the
+			best tool to do this is YaST (refer to SUSE Administration Manual); in the case of Red Hat,
+			this is best done using the graphical system configuration tools (see the Red Hat documentation).
+			An example of how this may be done manually is as follows:
+<screen>
+&rootprompt; route add net 172.16.4.0 netmask 255.255.252.0 gw 172.16.0.128
+&rootprompt; route add net 172.16.8.0 netmask 255.255.252.0 gw 172.16.0.128
+</screen>
+			If you just execute these commands manually, the route table entries you have created are
+			not persistent across system reboots. You may add these commands directly to the local
+			startup files as follows: (SUSE) <filename>/etc/rc.d/boot.local</filename>, (Red Hat)
+			<filename>/etc/rc.d/init.d/rc.local</filename>.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+			The final step that must be completed is to edit the <filename>/etc/nsswitch.conf</filename> file.
+			This file controls the operation of the various resolver libraries that are part of the Linux
+			Glibc libraries. Edit this file so that it contains the following entries:
+<screen>
+hosts:      files dns wins
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>initGrps.sh</primary></indexterm>
+			Create and map Windows domain groups to UNIX groups. A sample script is provided in
+			<link linkend="ch5-initgrps"/>. Create a file containing this script. You called yours
+			<filename>/etc/samba/initGrps.sh</filename>. Set this file so it can be executed
+			and then execute the script. An example of the execution of this script as well as its
+			validation are shown in Section 4.3.2, Step 5.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>/etc/passwd</primary></indexterm>
+			<indexterm><primary>password</primary><secondary>backend</secondary></indexterm>
+			<indexterm><primary>smbpasswd</primary></indexterm>
+			For each user who needs to be given a Windows domain account, make an entry in the
+			<filename>/etc/passwd</filename> file as well as in the Samba password backend.
+			Use the system tool of your choice to create the UNIX system account, and use the Samba
+			<command>smbpasswd</command> to create a domain user account.
+			</para>
+
+			<para>
+			<indexterm><primary>useradd</primary></indexterm>
+			<indexterm><primary>adduser</primary></indexterm>
+			<indexterm><primary>user</primary><secondary>management</secondary></indexterm>
+			There are a number of tools for user management under UNIX, such as
+			<command>useradd</command>, <command>adduser</command>, as well as a plethora of custom
+			tools. With the tool of your choice, create a home directory for each user.
+			</para></step>
+
+			<step><para>
+			Using the preferred tool for your UNIX system, add each user to the UNIX groups created
+			previously as necessary. File system access control is based on UNIX group membership.
+			</para></step>
+
+			<step><para>
+			Create the directory mount point for the disk subsystem that is to be mounted to provide
+			data storage for company files, in this case, the mount point indicated in the &smb.conf;
+			file is <filename>/data</filename>. Format the file system as required and mount the formatted
+			file system partition using appropriate system tools.
+			</para></step>
+
+			<step><para>
+		<indexterm><primary>file system</primary>
+		  <secondary>permissions</secondary></indexterm>
+			Create the top-level file storage directories for data and applications as follows:
+<screen>
+&rootprompt; mkdir -p /data/{accounts,finsvcs,pidata}
+&rootprompt; mkdir -p /apps
+&rootprompt; chown -R root:root /data
+&rootprompt; chown -R root:root /apps
+&rootprompt; chown -R bjordan:accounts /data/accounts
+&rootprompt; chown -R bjordan:finsvcs /data/finsvcs
+&rootprompt; chown -R bjordan:finsvcs /data/pidata
+&rootprompt; chmod -R ug+rwxs,o-rwx /data
+&rootprompt; chmod -R ug+rwx,o+rx-w /apps
+</screen>
+			Each department is responsible for creating its own directory structure within the departmental
+			share. The directory root of the <command>accounts</command> share is <filename>/data/accounts</filename>.
+			The directory root of the <command>finsvcs</command> share is <filename>/data/finsvcs</filename>.
+			The <filename>/apps</filename> directory is the root of the <constant>apps</constant> share
+			that provides the application server infrastructure.
+			</para></step>
+
+			<step><para>
+			The &smb.conf; file specifies an infrastructure to support roaming profiles and network
+			logon services. You can now create the file system infrastructure to provide the
+			locations on disk that these services require. Adequate planning is essential
+			because desktop profiles can grow to be quite large. For planning purposes, a minimum of
+			200 MB of storage should be allowed per user for profile storage. The following
+			commands create the directory infrastructure needed:
+<screen>
+&rootprompt; mkdir -p /var/spool/samba
+&rootprompt; mkdir -p /var/lib/samba/{netlogon/scripts,profiles}
+&rootprompt; chown -R root:root /var/spool/samba
+&rootprompt; chown -R root:root /var/lib/samba
+&rootprompt; chmod a+rwxt /var/spool/samba
+</screen>
+			For each user account that is created on the system, the following commands should be
+			executed:
+<screen>
+&rootprompt; mkdir /var/lib/samba/profiles/'username'
+&rootprompt; chown 'username':users /var/lib/samba/profiles/'username'
+&rootprompt; chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username'
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>unix2dos</primary></indexterm>
+			<indexterm><primary>dos2unix</primary></indexterm>
+			Create a logon script. It is important that each line is correctly terminated with
+			a carriage return and line-feed combination (i.e., DOS encoding). The following procedure
+			works if the right tools (<constant>unxi2dos</constant> and <constant>dos2unix</constant>) are installed.
+			First, create a file called <filename>/var/lib/samba/netlogon/scripts/logon.bat.unix</filename>
+			with the following contents:
+<screen>
+net time \\massive /set /yes
+net use h: /home
+</screen>
+			Convert the UNIX file to a DOS file:
+<screen>
+&rootprompt; dos2unix &lt; /var/lib/samba/netlogon/scripts/logon.bat.unix \
+        &gt; /var/lib/samba/netlogon/scripts/logon.bat
+</screen>
+			</para></step>
+
+			<step><para>
+			There is one preparatory step without which you cannot have a working Samba network
+			environment. You must add an account for each network user. You can do this by executing
+			the following steps for each user:
+<screen>
+&rootprompt; useradd -m <parameter>username</parameter>
+&rootprompt; passwd <parameter>username</parameter>
+Changing password for <parameter>username</parameter>.
+New password: XXXXXXXX
+Re-enter new password: XXXXXXXX
+Password changed
+&rootprompt; smbpasswd -a <parameter>username</parameter>
+New SMB password: XXXXXXXX
+Retype new SMB password: XXXXXXXX
+Added user <parameter>username</parameter>.
+</screen>
+			You do, of course, use a valid user login ID in place of <parameter>username</parameter>.
+			</para></step>
+
+			<step><para>
+			Follow the processes shown in <link linkend="ch5-procstart"/> to start all services.
+			</para></step>
+
+			<step><para>
+			Your server is ready for validation testing. Do not proceed with the steps in
+			<link linkend="ch5-domsvrspec"/> until after the operation of the server has been
+			validated following the same methods as outlined in <link linkend="secure"/>, <link linkend="ch4valid"/>.
+			</para></step>
+
+		</procedure>
+		
+		</sect3>
+
+		<sect3 id="ch5-domsvrspec">
+		<title>Configuration Specific to Domain Member Servers: <constant>BLDG1, BLDG2</constant></title>
+
+		<para>
+		The following steps will guide you through the nuances of implementing BDCs for the broadcast
+		isolated network segments. Remember that if the target installation platform is not Linux, it may
+		be necessary to adapt some commands to the equivalent on the target platform.
+		</para>
+
+		<procedure>
+		<title>Backup Domain Controller Configuration Steps</title>
+
+			<step><para>
+			<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+			The final step that must be completed is to edit the <filename>/etc/nsswitch.conf</filename> file.
+			This file controls the operation of the various resolver libraries that are part of the Linux
+			Glibc libraries. Edit this file so that it contains the following entries:
+<screen>
+passwd:     files winbind
+group:      files winbind
+hosts:      files dns wins
+</screen>
+                        </para></step>
+
+			<step><para>
+			Follow the steps outlined in <link linkend="ch5-procstart"/> to start all services. Do not
+			start Samba at this time. Samba is controlled by the process called <command>smb</command>.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+			You must now attempt to join the domain member servers to the domain. The following
+			instructions should be executed to effect this:
+<screen>
+&rootprompt; net rpc join 
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>service</primary><secondary>smb</secondary><tertiary>start</tertiary></indexterm>
+			You now start the Samba services by executing:
+<screen>
+&rootprompt; service smb start
+</screen>
+			</para></step>
+
+                        <step><para>
+                        Your server is ready for validation testing. Do not proceed with the steps in
+                        <link linkend="ch5-domsvrspec"/> until after the operation of the server has been
+                        validated following the same methods as outlined in <link linkend="ch4valid"/>.
+                        </para></step>
+
+		</procedure>
+
+		</sect3>
+
+	</sect2>
+
+<!-- One -->
+<example id="ch5-massivesmb">
+<title>Server: MASSIVE (PDC), File: <filename>/etc/samba/smb.conf</filename></title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MEGANET</smbconfoption>
+<smbconfoption name="netbios name">MASSIVE</smbconfoption>
+<smbconfoption name="interfaces">eth1, lo</smbconfoption>
+<smbconfoption name="bind interfaces only">Yes</smbconfoption>
+<smbconfoption name="passdb backend">tdbsam</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="add user script">/usr/sbin/useradd -m '%u'</smbconfoption>
+<smbconfoption name="delete user script">/usr/sbin/userdel -r '%u'</smbconfoption>
+<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
+<smbconfoption name="delete group script">/usr/sbin/groupdel '%g'</smbconfoption>
+<smbconfoption name="add user to group script">/usr/sbin/usermod -G '%g' '%u'</smbconfoption>
+<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</smbconfoption>
+<smbconfoption name="preferred master">Yes</smbconfoption>
+<smbconfoption name="wins support">Yes</smbconfoption>
+<smbconfoption name="include">/etc/samba/dc-common.conf</smbconfoption>
+
+<smbconfsection name="[accounts]"/>
+<smbconfoption name="comment">Accounting Files</smbconfoption>
+<smbconfoption name="path">/data/accounts</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[service]"/>
+<smbconfoption name="comment">Financial Services Files</smbconfoption>
+<smbconfoption name="path">/data/service</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[pidata]"/>
+<smbconfoption name="comment">Property Insurance Files</smbconfoption>
+<smbconfoption name="path">/data/pidata</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+</smbconfblock>
+</example>
+
+<!-- Two -->
+<example id="ch5-dc-common">
+<title>Server: MASSIVE (PDC), File: <filename>/etc/samba/dc-common.conf</filename></title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
+<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
+<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+<smbconfoption name="logon path">\%L\profiles\%U</smbconfoption>
+<smbconfoption name="logon drive">X:</smbconfoption>
+<smbconfoption name="logon home">\%L\%U</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="preferred master">Yes</smbconfoption>
+<smbconfoption name="include">/etc/samba/common.conf</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">Network Logon Service</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="locking">No</smbconfoption>
+
+<smbconfsection name="[profiles]"/>
+<smbconfoption name="comment">Profile Share</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="profile acls">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+<!-- Three -->
+<example id="ch5-commonsmb">
+<title>Common Samba Configuration File: <filename>/etc/samba/common.conf</filename></title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="log level">1</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+<smbconfoption name="max log size">50</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+<smbconfoption name="time server">Yes</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
+<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
+<smbconfoption name="utmp">Yes</smbconfoption>
+<smbconfoption name="map acl inherit">Yes</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+<smbconfoption name="veto files">/*.eml/*.nws/*.{*}/</smbconfoption>
+<smbconfoption name="veto oplock files">/*.doc/*.xls/*.mdb/</smbconfoption>
+<smbconfoption name="include"> </smbconfoption>
+
+<smbconfcomment>Share and Service Definitions are common to all servers</smbconfcomment>
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="default devmode">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[apps]"/>
+<smbconfoption name="comment">Application Files</smbconfoption>
+<smbconfoption name="path">/apps</smbconfoption>
+<smbconfoption name="admin users">bjordan</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+</smbconfblock>
+</example>
+
+<!-- Four -->
+<example id="ch5-bldg1-smb">
+<title>Server: BLDG1 (Member), File: smb.conf</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MEGANET</smbconfoption>
+<smbconfoption name="netbios name">BLDG1</smbconfoption>
+<smbconfoption name="include">/etc/samba/dom-mem.conf</smbconfoption>
+</smbconfblock>
+</example>
+
+<!-- Five -->
+<example id="ch5-bldg2-smb">
+<title>Server: BLDG2 (Member), File: smb.conf</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MEGANET</smbconfoption>
+<smbconfoption name="netbios name">BLDG2</smbconfoption>
+<smbconfoption name="include">/etc/samba/dom-mem.conf</smbconfoption>
+</smbconfblock>
+</example>
+
+<!-- Six -->
+<example id="ch5-dommem-smb">
+<title>Common Domain Member Include File: dom-mem.conf</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
+<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
+<smbconfoption name="preferred master">Yes</smbconfoption>
+<smbconfoption name="wins server">172.16.0.1</smbconfoption>
+<smbconfoption name="idmap uid">15000-20000</smbconfoption>
+<smbconfoption name="idmap gid">15000-20000</smbconfoption>
+<smbconfoption name="include">/etc/samba/common.conf</smbconfoption>
+</smbconfblock>
+</example>
+
+<!-- Seven -->
+<example id="massive-dhcp">
+<title>Server: MASSIVE, File: dhcpd.conf</title>
+<screen>
+# Abmas Accounting Inc.
+
+default-lease-time 86400;
+max-lease-time 172800;
+default-lease-time 86400;
+ddns-updates on;
+ddns-update-style interim;
+
+option ntp-servers 172.16.0.1;
+option domain-name "abmas.biz";
+option domain-name-servers 172.16.0.1, 172.16.4.1;
+option netbios-name-servers 172.16.0.1;
+option netbios-node-type 8;
+
+subnet 172.16.1.0 netmask 255.255.252.0 {
+        range dynamic-bootp 172.16.1.0 172.16.2.255;
+        option subnet-mask 255.255.252.0;
+        option routers 172.16.0.1, 172.16.0.128;
+        allow unknown-clients;
+	}
+subnet 172.16.4.0 netmask 255.255.252.0 {
+        range dynamic-bootp 172.16.7.0 172.16.7.254;
+        option subnet-mask 255.255.252.0;
+        option routers 172.16.4.128;
+        allow unknown-clients;
+	}
+subnet 172.16.8.0 netmask 255.255.252.0 {
+        range dynamic-bootp 172.16.11.0 172.16.11.254;
+        option subnet-mask 255.255.252.0;
+        option routers 172.16.4.128;
+        allow unknown-clients;
+	}
+subnet 127.0.0.0 netmask 255.0.0.0 {
+        }
+subnet 123.45.67.64 netmask 255.255.255.252 {
+        }
+</screen>
+</example>
+
+<!-- Eight -->
+<example id="bldg1dhcp">
+<title>Server: BLDG1, File: dhcpd.conf</title>
+<screen>
+# Abmas Accounting Inc.
+
+default-lease-time 86400;
+max-lease-time 172800;
+default-lease-time 86400;
+ddns-updates on;
+ddns-update-style ad-hoc;
+
+option ntp-servers 172.16.0.1;
+option domain-name "abmas.biz";
+option domain-name-servers 172.16.0.1, 172.16.4.1;
+option netbios-name-servers 172.16.0.1;
+option netbios-node-type 8;
+
+subnet 172.16.1.0 netmask 255.255.252.0 {
+        range dynamic-bootp 172.16.3.0 172.16.3.255;
+        option subnet-mask 255.255.252.0;
+        option routers 172.16.0.1, 172.16.0.128;
+        allow unknown-clients;
+	}
+subnet 172.16.4.0 netmask 255.255.252.0 {
+        range dynamic-bootp 172.16.5.0 172.16.6.255;
+        option subnet-mask 255.255.252.0;
+        option routers 172.16.4.128;
+        allow unknown-clients;
+	}
+subnet 127.0.0.0 netmask 255.0.0.0 {
+        }
+</screen>
+</example>
+
+<!-- Nine -->
+<example id="bldg2dhcp">
+<title>Server: BLDG2, File: dhcpd.conf</title>
+<screen>
+# Abmas Accounting Inc.
+
+default-lease-time 86400;
+max-lease-time 172800;
+default-lease-time 86400;
+ddns-updates on;
+ddns-update-style interim;
+
+option ntp-servers 172.16.0.1;
+option domain-name "abmas.biz";
+option domain-name-servers 172.16.0.1, 172.16.4.1;
+option netbios-name-servers 172.16.0.1;
+option netbios-node-type 8;
+
+subnet 172.16.8.0 netmask 255.255.252.0 {
+        range dynamic-bootp 172.16.9.0 172.16.10.255;
+        option subnet-mask 255.255.252.0;
+        option routers 172.16.8.128;
+        allow unknown-clients;
+	}
+subnet 127.0.0.0 netmask 255.0.0.0 {
+        }
+</screen>
+</example>
+
+<!-- Ten -->
+<example id="massive-nameda">
+<title>Server: MASSIVE, File: named.conf, Part: A</title>
+<screen>
+###
+# Abmas Biz DNS Control File
+###
+# Date: November 15, 2003
+###
+options {
+	directory "/var/lib/named";
+	forwarders {
+		123.45.12.23;
+		123.45.54.32;
+		};
+	forward first;
+	listen-on {
+		mynet;
+		};
+	auth-nxdomain yes;
+	multiple-cnames yes;
+	notify no;
+};
+
+zone "." in {
+	type hint;
+	file "root.hint";
+};
+
+zone "localhost" in {
+	type master;
+	file "localhost.zone";
+};
+
+zone "0.0.127.in-addr.arpa" in {
+	type master;
+	file "127.0.0.zone";
+};
+
+acl mynet {
+	172.16.0.0/24;
+	172.16.4.0/24;
+	172.16.8.0/24;
+	127.0.0.1;
+};
+
+acl seconddns {
+        123.45.54.32;
+};
+</screen>
+</example>
+
+<!-- Eleven -->
+<example id="massive-namedb">
+<title>Server: MASSIVE, File: named.conf, Part: B</title>
+<screen>
+zone "abmas.biz" {
+	type master;
+	file "/var/lib/named/master/abmas.biz.hosts";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+	allow-update {
+		mynet;
+	};
+};
+
+zone "abmas.us" {
+        type master;
+        file "/var/lib/named/master/abmas.us.hosts";
+        allow-query {
+                all;
+        };
+        allow-transfer {
+                seconddns;
+        };
+};
+</screen>
+</example>
+
+<!-- Twelve -->
+<example id="massive-namedc">
+<title>Server: MASSIVE, File: named.conf, Part: C</title>
+<screen>
+zone "0.16.172.in-addr.arpa" {
+	type master;
+	file "/var/lib/named/master/172.16.0.0.rev";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+	allow-update {
+		mynet;
+	};
+};
+
+zone "4.16.172.in-addr.arpa" {
+	type master;
+	file "/var/lib/named/master/172.16.4.0.rev";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+	allow-update {
+		mynet;
+	};
+};
+
+zone "8.16.172.in-addr.arpa" {
+	type master;
+	file "/var/lib/named/master/172.16.8.0.rev";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+	allow-update {
+		mynet;
+	};
+};
+</screen>
+</example>
+
+<!-- Thirteen -->
+<example id="abmasbizdns">
+<title>Forward Zone File: abmas.biz.hosts</title>
+<screen>
+$ORIGIN .
+$TTL 38400	; 10 hours 40 minutes
+abmas.biz	IN SOA	massive.abmas.biz. root.abmas.biz. (
+				2003021833 ; serial
+				10800      ; refresh (3 hours)
+				3600       ; retry (1 hour)
+				604800     ; expire (1 week)
+				38400      ; minimum (10 hours 40 minutes)
+				)
+			NS	massive.abmas.biz.
+			NS	bldg1.abmas.biz.
+			NS	bldg2.abmas.biz.
+			MX	10 massive.abmas.biz.
+$ORIGIN abmas.biz.
+massive			A	172.16.0.1
+router0                 A       172.16.0.128
+bldg1                   A       172.16.4.1
+router4                 A       172.16.4.128
+bldg2                   A       172.16.8.1
+router8                 A       172.16.8.128
+</screen>
+</example>
+
+<!-- Forteen -->
+<example id="abmasusdns">
+<title>Forward Zone File: abmas.biz.hosts</title>
+<screen>
+$ORIGIN .
+$TTL 38400	; 10 hours 40 minutes
+abmas.us	IN SOA	server.abmas.us. root.abmas.us. (
+				2003021833 ; serial
+				10800      ; refresh (3 hours)
+				3600       ; retry (1 hour)
+				604800     ; expire (1 week)
+				38400      ; minimum (10 hours 40 minutes)
+				)
+			NS	dns.abmas.us.
+			NS	dns2.abmas.us.
+			MX	10 mail.abmas.us.
+$ORIGIN abmas.us.
+server			A	123.45.67.66
+dns2			A	123.45.54.32
+gw			A	123.45.67.65
+www			CNAME	server
+mail			CNAME	server
+dns			CNAME	server
+</screen>
+</example>
+
+<!-- Fifteen -->
+<example id="bldg12nameda">
+<title>Servers: BLDG1/BLDG2, File: named.conf, Part: A</title>
+<screen>
+###
+# Abmas Biz DNS Control File
+###
+# Date: November 15, 2003
+###
+options {
+	directory "/var/lib/named";
+	forwarders {
+		172.16.0.1;
+		};
+	forward first;
+	listen-on {
+		mynet;
+		};
+	auth-nxdomain yes;
+	multiple-cnames yes;
+	notify no;
+};
+
+zone "." in {
+	type hint;
+	file "root.hint";
+};
+
+zone "localhost" in {
+	type master;
+	file "localhost.zone";
+};
+
+zone "0.0.127.in-addr.arpa" in {
+	type master;
+	file "127.0.0.zone";
+};
+
+acl mynet {
+	172.16.0.0/24;
+	172.16.4.0/24;
+	172.16.8.0/24;
+	127.0.0.1;
+};
+
+acl seconddns {
+        123.45.54.32;
+};
+</screen>
+</example>
+
+<!-- Sixteen -->
+<example id="bldg12namedb">
+<title>Servers: BLDG1/BLDG2, File: named.conf, Part: B</title>
+<screen>
+zone "abmas.biz" {
+	type slave;
+	file "/var/lib/named/slave/abmas.biz.hosts";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+};
+
+zone "0.16.172.in-addr.arpa" {
+	type slave;
+	file "/var/lib/slave/master/172.16.0.0.rev";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+};
+
+zone "4.16.172.in-addr.arpa" {
+	type slave;
+	file "/var/lib/named/slave/172.16.4.0.rev";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+};
+
+zone "8.16.172.in-addr.arpa" {
+	type slave;
+	file "/var/lib/named/slave/172.16.8.0.rev";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+};
+</screen>
+</example>
+
+
+<!-- Seventeen -->
+<example id="ch5-initgrps">
+<title>Initialize Groups Script, File: /etc/samba/initGrps.sh</title>
+<screen>
+#!/bin/bash
+
+# Create UNIX groups
+groupadd acctsdep
+groupadd finsrvcs
+groupadd piops
+
+# Map Windows Domain Groups to UNIX groups
+net groupmap add ntgroup="Domain Admins"  unixgroup=root type=d
+net groupmap add ntgroup="Domain Users"   unixgroup=users type=d
+net groupmap add ntgroup="Domain Guests"  unixgroup=nobody type=d
+
+# Add Functional Domain Groups
+net groupmap add ntgroup="Accounts Dept"       unixgroup=acctsdep type=d
+net groupmap add ntgroup="Financial Services"  unixgroup=finsrvcs type=d
+net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
+</screen>
+</example>
+
+<!-- End of Examples -->
+
+        <sect2 id="ch5-procstart">
+        <title>Process Startup Configuration</title>
+
+        <para>
+		<indexterm><primary>chkconfig</primary></indexterm>
+		<indexterm><primary>daemon control</primary></indexterm>
+        There are two essential steps to process startup configuration. A process
+        must be configured so that it is automatically restarted each time the server
+        is rebooted. This step involves use of the <command>chkconfig</command> tool that
+        created appropriate symbolic links from the master daemon control file that is
+        located in the <filename>/etc/rc.d</filename> directory to the <filename>/etc/rc'x'.d</filename>
+        directories. Links are created so that when the system run-level is changed, the
+        necessary start or kill script is run.
+        </para>
+
+        <para>
+        <indexterm><primary>/etc/xinetd.d</primary></indexterm>
+        In the event that a service is provided not as a daemon but via the internetworking
+        super daemon (<command>inetd</command> or <command>xinetd</command>), then the <command>chkconfig</command>
+        tool makes the necessary entries in the <filename>/etc/xinetd.d</filename> directory
+        and sends a hang-up (HUP) signal to the super daemon, thus forcing it to
+        re-read its control files.
+        </para>
+
+        <para>
+        Last, each service must be started to permit system validation to proceed. The following steps
+		are for a Red Hat Linux system, please adapt them to suit the target OS platform on which you 
+		are installing Samba.
+        </para>
+
+        <procedure>
+		<title>Process Startup Configuration Steps</title>
+
+                <step><para>
+                Use the standard system tool to configure each service to restart
+                automatically at every system reboot. For example,
+                <indexterm><primary>chkconfig</primary></indexterm>
+<screen>
+&rootprompt; chkconfig dhpc on
+&rootprompt; chkconfig named on
+&rootprompt; chkconfig cups on
+&rootprompt; chkconfig smb on
+&rootprompt; chkconfig swat on
+</screen>
+                </para></step>
+
+                <step><para>
+                <indexterm><primary>starting dhcpd</primary></indexterm>
+                <indexterm><primary>starting samba</primary></indexterm>
+                <indexterm><primary>starting CUPS</primary></indexterm>
+                Now start each service to permit the system to be validated.
+                Execute each of the following in the sequence shown:
+
+<screen>
+&rootprompt; service dhcp restart
+&rootprompt; service named restart
+&rootprompt; service cups restart
+&rootprompt; service smb restart
+&rootprompt; service swat restart
+</screen>
+                </para></step>
+        </procedure>
+
+        </sect2>
+
+	<sect2 id="ch5wincfg">
+	<title>Windows Client Configuration</title>
+
+	<para>
+	The procedure for desktop client configuration for the network in this chapter is similar to
+	that used for the previous one. There are a few subtle changes that should be noted.
+	</para>
+
+	<procedure>
+	<title>Windows Client Configuration Steps</title>
+
+		<step><para>
+		Install MS Windows XP Professional. During installation, configure the client to use DHCP for 
+		TCP/IP protocol configuration.
+		<indexterm><primary>WINS</primary></indexterm>
+		<indexterm><primary>DHCP</primary></indexterm>
+		DHCP configures all Windows clients to use the WINS Server address that has been defined
+		for the local subnet.
+		</para></step>
+
+		<step><para>
+		Join the Windows domain <constant>MEGANET</constant>. Use the domain administrator
+		username <constant>root</constant> and the SMB password you assigned to this account.
+		A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to
+		a Windows domain is given in <link linkend="appendix"/>, <link linkend="domjoin"/>. 
+		Reboot the machine as prompted and then log on using the domain administrator account
+		(<constant>root</constant>).
+		</para></step>
+
+		<step><para>
+		Verify that the server called <constant>MEGANET</constant> is visible in <guimenu>My Network Places</guimenu>, 
+		that it is possible to connect to it and see the shares <guimenuitem>accounts</guimenuitem>,
+		<guimenuitem>apps</guimenuitem>, and <guimenuitem>finsvcs</guimenuitem>,
+		and that it is possible to open each share to reveal its contents.
+		</para></step>
+
+		<step><para>
+		Create a drive mapping to the <constant>apps</constant> share on a server. At this time, it does
+		not particularly matter which application server is used. It is necessary to manually
+		set a persistent drive mapping to the local applications server on each workstation at the time of 
+		installation. This step is avoided by the improvements to the design of the network configuration
+		in the next chapter.
+		</para></step>
+
+		<step><para>
+		Perform an administrative installation of each application to be used. Select the options
+		that you wish to use. Of course, you choose to run applications over the network, correct?
+		</para></step>
+
+		<step><para>
+		Now install all applications to be installed locally. Typical tools include Adobe Acrobat,
+		NTP-based time synchronization software, drivers for specific local devices such as fingerprint
+		scanners, and the like. Probably the most significant application to be locally installed
+		is antivirus software.
+		</para></step>
+
+		<step><para>
+		Now install all four printers onto the staging system. The printers you install
+		include the accounting department HP LaserJet 6 and Minolta QMS Magicolor printers, and you
+		also configure use of the identical printers that are located in the financial services department.
+		Install printers on each machine using the following steps:
+
+			<procedure>
+			<title>Steps to Install Printer Drivers on Windows Clients</title>
+
+				<step><para>
+				Click <menuchoice>
+					<guimenu>Start</guimenu>
+					<guimenuitem>Settings</guimenuitem>
+					<guimenuitem>Printers</guimenuitem>
+					<guiicon>Add Printer</guiicon>
+					<guibutton>Next</guibutton>
+					</menuchoice>. Do not click <guimenuitem>Network printer</guimenuitem>.
+					Ensure that <guimenuitem>Local printer</guimenuitem> is selected.
+				</para></step>
+
+				<step><para>
+				Click <guibutton>Next</guibutton>. In the
+				<guimenuitem>Manufacturer:</guimenuitem> panel, select <constant>HP</constant>.
+				In the <guimenuitem>Printers:</guimenuitem> panel, select the printer called
+				<constant>HP LaserJet 6</constant>. Click <guibutton>Next</guibutton>.
+				</para></step>
+
+				<step><para>
+				In the <guimenuitem>Available ports:</guimenuitem> panel, select
+				<constant>FILE:</constant>. Accept the default printer name by clicking
+				<guibutton>Next</guibutton>. When asked, <quote>Would you like to print a
+				test page?</quote>, click <guimenuitem>No</guimenuitem>. Click
+				<guibutton>Finish</guibutton>.
+				</para></step>
+
+				<step><para>
+				You may be prompted for the name of a file to print to. If so, close the
+				dialog panel. Right-click <menuchoice>
+					<guiicon>HP LaserJet 6</guiicon>
+					<guimenuitem>Properties</guimenuitem>
+					<guimenusub>Details (Tab)</guimenusub>
+					<guimenubutton>Add Port</guimenubutton>
+					</menuchoice>.
+				</para></step>
+
+				<step><para>
+				In the <guimenuitem>Network</guimenuitem> panel, enter the name of
+				the print queue on the Samba server as follows: <constant>\\BLDG1\hplj6a</constant>.
+				Click <menuchoice> 
+					<guibutton>OK</guibutton>
+					<guibutton>OK</guibutton>
+					</menuchoice> to complete the installation.
+				</para></step>
+
+				<step><para>
+				Repeat the printer installation steps above for both HP LaserJet 6 printers
+				as well as for both QMS Magicolor laser printers. Remember to install all
+				printers but to set the destination port for each to the server on the
+				local network. For example, a workstation in the accounting group should
+				have all printers directed at the server <constant>BLDG1</constant>.
+				You may elect to point all desktop workstation configurations at the
+				server called <constant>MASSIVE</constant> and then in your deployment	
+				procedures, it would be wise to document the need to redirect the printer
+				configuration (as well as the applications server drive mapping) to the
+				server on the network segment on which the workstation is to be located.
+				</para></step>
+			</procedure>
+		</para></step>
+
+		<step><para>
+		When you are satisfied that the staging systems are complete, use the appropriate procedure to
+		remove the client from the domain. Reboot the system, and then log on as the local administrator
+		and clean out all temporary files stored on the system. Before shutting down, use the disk
+		defragmentation tool so that the file system is in optimal condition before replication.
+		</para></step>
+
+		<step><para>
+		Boot the workstation using the Norton (Symantec) Ghosting disk (or CD-ROM) and image the
+		machine to a network share on the server.
+		</para></step>
+
+		<step><para>
+		You may now replicate the image using the appropriate Norton Ghost procedure to the target
+		machines. Make sure to use the procedure that ensures each machine has a unique
+		Windows security identifier (SID). When the installation of the disk image is complete, boot the PC. 
+		</para></step>
+
+		<step><para>
+		Log onto the machine as the local Administrator (the only option), and join the machine to
+		the domain following the procedure set out in <link linkend="appendix"/>, <link linkend="domjoin"/>. You must now set the 
+		persistent drive mapping to the applications server that the user is to use. The system is now 
+		ready for the user to log on, provided you have created a network logon account for that 
+		user, of course.
+		</para></step>
+
+		<step><para>
+		Instruct all users to log onto the workstation using their assigned username and password.
+		</para></step>
+	</procedure>
+
+	</sect2>
+
+	<sect2>
+		<title>Key Points Learned</title>
+
+		<para>
+		The network you have just deployed has been a valuable exercise in forced constraint.
+		You have deployed a network that works well, although you may soon start to see
+		performance problems, at which time the modifications demonstrated in <link linkend="happy"/>
+		bring the network to life. The following key learning points were experienced:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			The power of using &smb.conf; include files
+			</para></listitem>
+
+			<listitem><para>
+			Use of a single PDC over a routed network
+			</para></listitem>
+
+			<listitem><para>
+			Joining a Samba-3 domain member server to a Samba-3 domain
+			</para></listitem>
+
+			<listitem><para>
+			Configuration of winbind to use domain users and groups for Samba access
+			to resources on the domain member servers
+			</para></listitem>
+
+			<listitem><para>
+			The introduction of roaming profiles
+			</para></listitem>
+
+		</itemizedlist>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	</para>
+
+	<qandaset defaultlabel="chap01qa" type="number">
+	<qandaentry>
+	<question>
+
+		<para>
+		The example &smb.conf; files in this chapter make use of the <parameter>include</parameter> facility.
+		How may I get to see what the actual working &smb.conf; settings are?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		You may readily see the net compound effect of the included files by running:
+<screen>
+&rootprompt; testparm -s | less
+</screen>
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why does the include file <filename>common.conf</filename> have an empty include statement?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The use of the empty include statement nullifies further includes. For example, let's say you 
+		desire to have just an smb.conf file that is built from the array of include files of which the
+		master control file is called <filename>master.conf</filename>. The following command 
+		produces a compound &smb.conf; file.
+<screen>
+&rootprompt; testparm -s /etc/samba/master.conf > /etc/samba/smb.conf
+</screen>
+		If the include parameter was not in the common.conf file, the final &smb.conf; file leaves
+		the include in place, even though the file it points to has already been included. This is a bug
+		that will be fixed at a future date.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		I accept that the simplest configuration necessary to do the job is the best. The use of <parameter>tdbsam</parameter>
+		passdb backend is much simpler than having to manage an LDAP-based <parameter>ldapsam</parameter> passdb backend.
+		I tried using <command>rsync</command> to replicate the <filename>passdb.tdb</filename>, and it seems to work fine!
+		So what is the problem?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Replication of the <parameter>tdbsam</parameter> database file can result in loss of currency in its
+		contents between the PDC and BDCs. The most notable symptom is that workstations may not be able
+		to log onto the network following a reboot and may have to rejoin the domain to recover network
+		access capability.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		You are using DHCP Relay enabled on the routers as well as a local DHCP server. Will this cause a clash?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		No. It is possible to have as many DHCP servers on a network segment as makes sense. A DHCP server
+		offers an IP address lease, but it is the client that determines which offer is accepted, no matter how many
+		offers are made. Under normal operation, the client accepts the first offer it receives.
+		</para>
+
+		<para>
+		The only exception to this rule is when the client makes a directed request from a specific DHCP server
+		for renewal of the lease it has. This means that under normal circumstances there is no risk of a clash.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		How does the Windows client find the PDC?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The Windows client obtains the WINS server address from the DHCP lease information. It also
+		obtains from the DHCP lease information the parameter that causes it to use directed UDP (UDP Unicast)
+		to register itself with the WINS server and to obtain enumeration of vital network information to 
+		enable it to operate successfully.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why did you enable IP forwarding (routing) only on the server called <constant>MASSIVE</constant>?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The server called <constant>MASSIVE</constant> is acting as a router to the Internet. No other server
+		(BLDG1 or BLDG2) has any need for IP forwarding because they are attached only to their own network.
+		Route table entries are needed to direct MASSIVE to send all traffic intended for the remote network
+		segments to the router that is its gateway to them.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		You did nothing special to implement roaming profiles. Why?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Unless configured to do otherwise, the default behavior with Samba-3 and Windows XP Professional
+		clients is to use roaming profiles.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		On the domain member computers, you configured winbind in the <filename>/etc/nsswitch.conf</filename> file.
+		You did not configure any PAM settings. Is this an omission?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		PAM is needed only for authentication. When Samba is using Microsoft encrypted passwords, it makes only
+		marginal use of PAM. PAM configuration handles only authentication. If you want to log onto the domain
+		member servers using Windows networking usernames and passwords, it is necessary to configure PAM
+		to enable the use of winbind. Samba makes use only of the identity resolution facilities of the name
+		service switch (NSS).
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		You are starting SWAT up on this example but have not discussed that anywhere. Why did you do this?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Oh, I did not think you would notice that. It is there so that it can be used. This is more fully discussed
+		in <emphasis>TOSHARG2</emphasis>, which has a full chapter dedicated to the subject. While we are on the 
+		subject, it should be noted that you should definitely not use SWAT on any system that makes use 
+		of &smb.conf; <parameter>include</parameter> files because SWAT optimizes them out into an aggregated 
+		file but leaves in place a broken reference to the top-layer include file. SWAT was not designed to 
+		handle this functionality gracefully.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		The domain controller has an auto-shutdown script. Isn't that dangerous?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Well done, you spotted that! I guess it is dangerous. It is good to know that you can do this, though.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	</qandaset>
+
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-AddingUNIXClients.xml b/docs-xml/Samba3-ByExample/SBE-AddingUNIXClients.xml
new file mode 100644
index 00000000000..a20703af391
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-AddingUNIXClients.xml
@@ -0,0 +1,2870 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="unixclients">
+  <title>Adding Domain Member Servers and Clients</title>
+
+    <para><indexterm>
+	<primary>Open Magazine</primary>
+      </indexterm><indexterm>
+	<primary>survey</primary>
+      </indexterm>
+	The most frequently discussed Samba subjects over the past 2 years have focused around domain control and printing. 
+	It is well known that Samba is a file and print server. A recent survey conducted by <emphasis>Open Magazine</emphasis> found 
+	that of all respondents, 97 percent use Samba for file and print services, and 68 percent use Samba for Domain Control. See the 
+	<ulink url="http://www.open-mag.com/cgi-bin/opencgi/surveys/survey.cgi?survey_name=samba">Open-Mag</ulink>
+	Web site for current information. The survey results as found on January 14, 2004, are shown in
+	<link linkend="ch09openmag"/>.
+	</para>
+
+	<figure id="ch09openmag">
+		<title>Open Magazine Samba Survey</title>
+		<imagefile scale="60">openmag</imagefile>
+	</figure>
+
+	<para>
+	While domain control is an exciting subject, basic file and print sharing remains the staple bread-and-butter
+	function that Samba provides. Yet this book may give the appearance of having focused too much on more
+	exciting aspects of Samba deployment. This chapter directs your attention to provide important information on
+	the addition of Samba servers into your present Windows network &smbmdash; whatever the controlling technology
+	may be. So let's get back to our good friends at Abmas.
+	</para>
+
+<sect1>
+	<title>Introduction</title>
+
+      <para><indexterm>
+	  <primary>Linux desktop</primary>
+	</indexterm><indexterm>
+	  <primary>Domain Member</primary>
+	  <secondary>server</secondary>
+	</indexterm>
+	Looking back over the achievements of the past year or two, daily events at Abmas are rather straightforward
+	with not too many distractions or problems. Your team is doing well, but a number of employees
+	are asking for Linux desktop systems. Your network has grown and demands additional domain member servers. Let's
+	get on with this; Christine and Stan are ready to go.
+	</para>
+
+      <para><indexterm>
+	  <primary>Domain Member</primary>
+	  <secondary>desktop</secondary>
+	</indexterm>
+	Stan is firmly in control of the department of the future, while Christine is enjoying a stable and
+	predictable network environment. It is time to add more servers and to add Linux desktops. It is
+	time to meet the demands of future growth and endure trial by fire.
+	</para>
+
+	<sect2>
+	<title>Assignment Tasks</title>
+
+	<para><indexterm>
+	    <primary>Active Directory</primary>
+	  </indexterm>
+	You must now add UNIX/Linux domain member servers to your network. You have a friend who has a Windows 2003
+	Active Directory domain network who wants to add a Samba/Linux server and has asked Christine to help him
+	out. Your real objective is to help Christine to see more of the way the Microsoft world lives and use
+	her help to get validation that Samba really does live up to expectations.
+	</para>
+
+	<para>
+	Over the past 6 months, you have hired several new staff who want Linux on their desktops. You must integrate
+	these systems to make sure that Abmas is not building islands of technology. You ask Christine to
+	do likewise at Swodniw Biz NL (your friend's company) to help them to evaluate a Linux desktop. You want to make
+	the right decision, don't you?
+	</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+	<title>Dissection and Discussion</title>
+
+	<para>
+	<indexterm><primary>winbind</primary></indexterm>
+	Recent Samba mailing-list activity is witness to how many sites are using winbind. Some have no trouble
+	at all with it, yet to others the problems seem insurmountable. Periodically there are complaints concerning
+	an inability to achieve identical user and group IDs between Windows and UNIX environments.
+	</para>
+
+	<para>
+	You provide step-by-step implementations of the various tools that can be used for identity
+	resolution. You also provide working examples of solutions for integrated authentication for
+	both UNIX/Linux and Windows environments.
+	</para>
+
+	<sect2>
+		<title>Technical Issues</title>
+
+		<para>
+		One of the great challenges we face when people ask us, <quote>What is the best way to solve
+		this problem?</quote> is to get beyond the facts so we not only can clearly comprehend
+		the immediate technical problem, but also can understand how needs may change.
+		</para>
+
+		<para>
+		<indexterm><primary>integrate</primary></indexterm>
+		There are a few facts we should note when dealing with the question of how best to
+		integrate UNIX/Linux clients and servers into a Windows networking environment:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			<indexterm><primary>Domain Controller</primary></indexterm>
+			<indexterm><primary>authoritative</primary></indexterm>
+			<indexterm><primary>accounts</primary><secondary>authoritative</secondary></indexterm>
+			<indexterm><primary>PDC</primary></indexterm>
+			<indexterm><primary>BDC</primary></indexterm>
+			A domain controller (PDC or BDC) is always authoritative for all accounts in its domain.
+			This means that a BDC must (of necessity) be able to resolve all account UIDs and GIDs
+			to the same values that the PDC resolved them to.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>local accounts</primary></indexterm>
+			<indexterm><primary>Domain Member</primary><secondary>authoritative</secondary><tertiary>local accounts</tertiary></indexterm>
+			<indexterm><primary>Domain accounts</primary></indexterm>
+			<indexterm><primary>winbindd</primary></indexterm>
+			A domain member can be authoritative for local accounts, but is never authoritative for
+			domain accounts. If a user is accessing a domain member server and that user's account
+			is not known locally, the domain member server must resolve the identity of that user
+			from the domain in which that user's account resides. It must then map that ID to a
+			UID/GID pair that it can use locally. This is handled by <command>winbindd</command>.
+			</para></listitem>
+
+			<listitem><para>
+			Samba, when running on a domain member server, can resolve user identities from a
+			number of sources:
+			</para>
+
+			<itemizedlist>
+				<listitem><para>
+				<indexterm><primary>getpwnam</primary></indexterm>
+				<indexterm><primary>getgrnam</primary></indexterm>
+				<indexterm><primary>NSS</primary></indexterm>
+				<indexterm><primary>LDAP</primary></indexterm>
+				<indexterm><primary>NIS</primary></indexterm>
+				By executing a system <command>getpwnam()</command> or <command>getgrnam()</command> call. 
+				On systems that support it, this utilizes the name service switch (NSS) facility to 
+				resolve names according to the configuration of the <filename>/etc/nsswitch.conf</filename> 
+				file. NSS can be configured to use LDAP, winbind, NIS, or local files.
+				</para></listitem>
+
+				<listitem><para>
+				<indexterm><primary>passdb backend</primary></indexterm>
+				<indexterm><primary>PADL</primary></indexterm>
+				<indexterm><primary>nss_ldap</primary></indexterm>
+				Performing, via NSS, a direct LDAP search (where an LDAP passdb backend has been configured).
+				This requires the use of the PADL nss_ldap tool (or equivalent).
+				</para></listitem>
+
+				<listitem><para>
+				<indexterm><primary>winbindd</primary></indexterm>
+				<indexterm><primary>SID</primary></indexterm>
+				<indexterm><primary>winbindd_idmap.tdb</primary></indexterm>
+				<indexterm><primary>winbindd_cache.tdb</primary></indexterm>
+				Directly by querying <command>winbindd</command>. The <command>winbindd</command>
+				contacts a domain controller to attempt to resolve the identity of the user or group. It
+				receives the Windows networking security identifier (SID) for that appropriate
+				account and then allocates a local UID or GID from the range of available IDs and
+				creates an entry in its <filename>winbindd_idmap.tdb</filename> and 
+				<filename>winbindd_cache.tdb</filename> files.
+				</para>
+
+				<para>
+				<indexterm><primary>idmap backend</primary></indexterm>
+				<indexterm><primary>mapping</primary></indexterm>
+				If the parameter <smbconfoption name="idmap backend">ldap:ldap://myserver.domain</smbconfoption>
+				was specified and the LDAP server has been configured with a container in which it may
+				store the IDMAP entries, all domain members may share a common mapping.
+				</para></listitem>
+			</itemizedlist>
+
+			<para>
+			Irrespective of how &smb.conf; is configured, winbind creates and caches a local copy of
+			the ID mapping database. It uses the <filename>winbindd_idmap.tdb</filename> and
+                                <filename>winbindd_cache.tdb</filename> files to do this.
+			</para>
+
+			<para>
+			Which of the resolver methods is chosen is determined by the way that Samba is configured 
+			in the &smb.conf; file. Some of the configuration options are rather less than obvious to the 
+			casual user.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>winbind trusted domains only</primary></indexterm>
+			<indexterm><primary>domain member</primary><secondary>servers</secondary></indexterm>
+			<indexterm><primary>domain controllers</primary></indexterm>
+			If you wish to make use of accounts (users and/or groups) that are local to (i.e., capable
+			of being resolved using) the NSS facility, it is possible to use the 
+			<smbconfoption name="winbind trusted domains only">Yes</smbconfoption>
+			in the &smb.conf; file. This parameter specifically applies to domain controllers, 
+			and to domain member servers.
+			</para></listitem>
+
+		</itemizedlist>
+
+		<para>
+		<indexterm><primary>Posix accounts</primary></indexterm>
+		<indexterm><primary>Samba accounts</primary></indexterm>
+		<indexterm><primary>LDAP</primary></indexterm>
+		For many administrators, it should be plain that the use of an LDAP-based repository for all network
+		accounts (both for POSIX accounts and for Samba accounts) provides the most elegant and
+		controllable facility. You eventually appreciate the decision to use LDAP.
+		</para>
+
+		<para>
+		<indexterm><primary>nss_ldap</primary></indexterm>
+		<indexterm><primary>identifiers</primary></indexterm>
+		<indexterm><primary>resolve</primary></indexterm>
+		If your network account information resides in an LDAP repository, you should use it ahead of any
+		alternative method. This means that if it is humanly possible to use the <command>nss_ldap</command>
+		tools to resolve UNIX account UIDs/GIDs via LDAP, this is the preferred solution, because it provides
+		a more readily controllable method for asserting the exact same user and group identifiers 
+		throughout the network.
+		</para>
+
+		<para>
+		<indexterm><primary>Domain Member</primary><secondary>server</secondary></indexterm>
+		<indexterm><primary>winbind trusted domains only</primary></indexterm>
+		<indexterm><primary>getpwnam</primary></indexterm>
+		<indexterm><primary>smbd</primary></indexterm>
+		<indexterm><primary>Trusted Domains</primary></indexterm>
+		<indexterm><primary>External Domains</primary></indexterm>
+		In the situation where UNIX accounts are held on the domain member server itself, the only effective
+		way to use them involves the &smb.conf; entry 
+		<smbconfoption name="winbind trusted domains only">Yes</smbconfoption>. This forces 
+		Samba (<command>smbd</command>) to perform a <command>getpwnam()</command> system call that can
+		then be controlled via <filename>/etc/nsswitch.conf</filename> file settings. The use of this parameter
+		disables the use of Samba with trusted domains (i.e., external domains).
+		</para>
+
+		<para>
+		<indexterm><primary>appliance mode</primary></indexterm>
+		<indexterm><primary>Domain Member</primary><secondary>server</secondary></indexterm>
+		<indexterm><primary>winbindd</primary></indexterm>
+		<indexterm><primary>automatically allocate</primary></indexterm>
+		Winbind can be used to create an appliance mode domain member server. In this capacity, <command>winbindd</command>
+		is configured to automatically allocate UIDs/GIDs from numeric ranges set in the &smb.conf; file. The allocation
+		is made for all accounts that connect to that domain member server, whether within its own domain or from
+		trusted domains. If not stored in an LDAP backend, each domain member maintains its own unique mapping database.
+		This means that it is almost certain that a given user who accesses two domain member servers does not have the
+		same UID/GID on both servers &smbmdash; however, this is transparent to the Windows network user. This data
+		is stored in the <filename>winbindd_idmap.tdb</filename> and <filename>winbindd_cache.tdb</filename> files.
+		</para>
+	
+		<para>
+		<indexterm><primary>mapping</primary></indexterm>
+		The use of an LDAP backend for the Winbind IDMAP facility permits Windows domain SIDs
+		mappings to UIDs/GIDs to be stored centrally. The result is a consistent mapping across all domain member
+		servers so configured. This solves one of the major headaches for network administrators who need to copy
+		files between or across network file servers.
+		</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Political Issues</title>
+
+		<para>
+		<indexterm><primary>OpenLDAP</primary></indexterm>
+		<indexterm><primary>NIS</primary></indexterm>
+		<indexterm><primary>yellow pages</primary><see>NIS</see></indexterm>
+		<indexterm><primary>identity management</primary></indexterm>
+		One of the most fierce conflicts recently being waged is resistance to the adoption of LDAP, in
+		particular OpenLDAP, as a replacement for UNIX NIS (previously called Yellow Pages). Let's face it, LDAP
+		is different and requires a new approach to the need for a better identity management solution. The more
+		you work with LDAP, the more its power and flexibility emerges from its dark, cavernous chasm.
+		</para>
+
+		<para>
+		LDAP is a most suitable solution for heterogenous environments. If you need crypto, add Kerberos. 
+		The reason these are preferable is because they are heterogenous. Windows solutions of this sort are <emphasis>not</emphasis> 
+		heterogenous by design. This is fundamental &smbmdash; it isn't religious or political. This also doesn't say that 
+		you can't use Windows Active Directory in a heterogenous environment &smbmdash; it can be done, it just requires 
+		commercial integration products. But it's not what Active Directory was designed for.
+		</para>
+
+		<para>
+		<indexterm><primary>directory</primary></indexterm>
+		<indexterm><primary>management</primary></indexterm>
+		A number of long-term UNIX devotees have recently commented in various communications that the Samba Team
+		is the first application group to almost force network administrators to use LDAP. It should be pointed
+		out that we resisted this for as long as we could. It is not out of laziness or malice that LDAP has
+		finally emerged as the preferred identity management backend for Samba. We recommend LDAP for your total
+		organizational directory needs.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Implementation</title>
+
+	<para>
+	<indexterm><primary>Domain Member</primary><secondary>server</secondary></indexterm>
+	<indexterm><primary>Domain Member</primary><secondary>client</secondary></indexterm>
+	<indexterm><primary>Domain Controller</primary></indexterm>
+	The domain member server and the domain member client are at the center of focus in this chapter.
+	Configuration of Samba-3 domain controller is covered in earlier chapters, so if your 
+	interest is in domain controller configuration, you will not find that here. You will find good
+	oil that helps you to add domain member servers and clients.
+	</para>
+
+	<para>
+	<indexterm><primary>Domain Member</primary><secondary>workstations</secondary></indexterm>
+	In practice, domain member servers and domain member workstations are very different entities, but in
+	terms of technology they share similar core infrastructure. A technologist would argue that servers
+	and workstations are identical. Many users would argue otherwise, given that in a well-disciplined
+	environment a workstation (client) is a device from which a user creates documents and files that
+	are located on servers. A workstation is frequently viewed as a disposable (easy to replace) item,
+	but a server is viewed as a core component of the business.
+	</para>
+
+	<para>
+	<indexterm><primary>workstation</primary></indexterm>
+	We can look at this another way. If a workstation breaks down, one user is affected, but if a
+	server breaks down, hundreds of users may not be able to work. The services that a workstation
+	must provide are document- and file-production oriented; a server provides information storage
+	and is distribution oriented.
+	</para>
+
+	<para>
+	<indexterm><primary>authentication process</primary></indexterm>
+	<indexterm><primary>logon process</primary></indexterm>
+	<indexterm><primary>user identities</primary></indexterm>
+	<emphasis>Why is this important?</emphasis> For starters, we must identify what
+	components of the operating system and its environment must be configured. Also, it is necessary
+	to recognize where the interdependencies between the various services to be used are.
+	In particular, it is important to understand the operation of each critical part of the
+	authentication process, the logon process, and how user identities get resolved and applied
+	within the operating system and applications (like Samba) that depend on this and may
+	actually contribute to it.
+	</para>
+
+	<para>
+	So, in this chapter we demonstrate how to implement the technology. It is done within a context of
+	what type of service need must be fulfilled.
+	</para>
+
+	<sect2 id="sdcsdmldap">
+	<title>Samba Domain with Samba Domain Member Server &smbmdash; Using NSS LDAP</title>
+
+	<para>
+	<indexterm><primary>ldapsam</primary></indexterm>
+	<indexterm><primary>ldapsam backend</primary></indexterm>
+	<indexterm><primary>IDMAP</primary></indexterm>
+	<indexterm><primary>mapping</primary><secondary>consistent</secondary></indexterm>
+	<indexterm><primary>winbindd</primary></indexterm>
+	<indexterm><primary>foreign SID</primary></indexterm>
+	In this example, it is assumed that you have Samba PDC/BDC servers. This means you are using
+	an LDAP ldapsam backend. We are adding to the LDAP backend database (directory)
+	containers for use by the IDMAP facility. This makes it possible to have globally consistent
+	mapping of SIDs to and from UIDs and GIDs. This means that it is necessary to run 
+	<command>winbindd</command> as part of your configuration. The primary purpose of running
+	<command>winbindd</command> (within this operational context) is to permit mapping of foreign
+	SIDs (those not originating from the the local Samba server). Foreign SIDs can come from any
+	domain member client or server, or from Windows clients that do not belong to a domain. Another
+	way to explain the necessity to run <command>winbindd</command> is that Samba can locally
+	resolve only accounts that belong to the security context of its own machine SID. Winbind
+	handles all non-local SIDs and maps them to a local UID/GID value. The UID and GID are allocated
+	from the parameter values set in the &smb.conf; file for the <parameter>idmap uid</parameter> and
+	<parameter>idmap gid</parameter> ranges. Where LDAP is used, the mappings can be stored in LDAP
+	so that all domain member servers can use a consistent mapping.
+	</para>
+
+	<para>
+	<indexterm><primary>winbindd</primary></indexterm>
+	<indexterm><primary>getpwnam</primary></indexterm>
+	<indexterm><primary>NSS</primary></indexterm>
+	If your installation is accessed only from clients that are members of your own domain, and all 
+	user accounts are present in a local passdb backend then it is not necessary to run
+	<command>winbindd</command>. The local passdb backend can be in smbpasswd, tdbsam, or in ldapsam.
+	</para>
+
+	<para>
+	It is possible to use a local passdb backend with any convenient means of resolving the POSIX
+	user and group account information. The POSIX information is usually obtained using the
+	<command>getpwnam()</command> system call. On NSS-enabled systems, the actual POSIX account
+	source can be provided from
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		<indexterm><primary>/etc/passwd</primary></indexterm>
+		<indexterm><primary>/etc/group</primary></indexterm>
+		Accounts in <filename>/etc/passwd</filename> or in <filename>/etc/group</filename>.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>NSS</primary></indexterm>
+		<indexterm><primary>compat</primary></indexterm>
+		<indexterm><primary>ldap</primary></indexterm>
+		<indexterm><primary>nis</primary></indexterm>
+		<indexterm><primary>nisplus</primary></indexterm>
+		<indexterm><primary>hesiod</primary></indexterm>
+		<indexterm><primary>ldap</primary></indexterm>
+		<indexterm><primary>nss_ldap</primary></indexterm>
+		<indexterm><primary>PADL Software</primary></indexterm>
+		Resolution via NSS. On NSS-enabled systems, there is usually a facility to resolve IDs
+		via multiple methods. The methods typically include <command>files</command>,
+		<command>compat</command>, <command>db</command>, <command>ldap</command>, 
+		<command>nis</command>, <command>nisplus</command>, <command>hesiod.</command>  When
+		correctly installed, Samba adds to this list the <command>winbindd</command> facility.
+		The ldap facility is frequently the nss_ldap tool provided by PADL Software.
+		</para></listitem>
+	</itemizedlist>
+
+	<note><para>
+	To advoid confusion the use of the term <literal>local passdb backend</literal> means that
+	the user account backend is not shared by any other Samba server &smbmdash; instead, it is
+	used only locally on the Samba domain member server under discussion.
+	</para></note>
+
+	<para>
+	<indexterm><primary>Identity resolution</primary></indexterm>
+	The diagram in <link linkend="ch9-sambadc"/> demonstrates the relationship of Samba and system 
+	components that are involved in the identity resolution process where Samba is used as a domain
+	member server within a Samba domain control network.
+	</para>
+
+<figure id="ch9-sambadc">
+	<title>Samba Domain: Samba Member Server</title>
+	<imagefile scale="60">chap9-SambaDC</imagefile>
+</figure>
+
+	<para>
+	<indexterm><primary>IDMAP</primary></indexterm>
+	<indexterm><primary>foreign</primary></indexterm>
+	In this example configuration, Samba will directly search the LDAP-based passwd backend ldapsam
+	to obtain authentication and user identity information. The IDMAP information is stored in the LDAP
+	backend so that it can be shared by all domain member servers so that every user will have a
+	consistent UID and GID across all of them. The IDMAP facility will be used for all foreign
+	(i.e., not having the same SID as the domain it is a member of) domains. The configuration of 
+	NSS will ensure that all UNIX processes will obtain a consistent UID/GID.
+	</para>
+
+	<para>
+	The instructions given here apply to the Samba environment shown in <link linkend="happy"/> and <link linkend="2000users"/>.
+	If the network does not have an LDAP slave server (i.e., <link linkend="happy"/> configuration), 
+	change the target LDAP server from <constant>lapdc</constant> to <constant>massive.</constant>
+	</para>
+
+	<procedure>
+	<title>Configuration of NSS_LDAP-Based Identity Resolution</title>
+
+		<step><para>
+		Create the &smb.conf; file as shown in <link linkend="ch9-sdmsdc"/>. Locate
+		this file in the directory <filename>/etc/samba</filename>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>ldap.conf</primary></indexterm>
+		Configure the file that will be used by <constant>nss_ldap</constant> to
+		locate and communicate with the LDAP server. This file is called <filename>ldap.conf</filename>.
+		If your implementation of <constant>nss_ldap</constant> is consistent with
+		the defaults suggested by PADL (the authors), it will be located in the
+		<filename>/etc</filename> directory. On some systems, the default location is
+		the <filename>/etc/openldap</filename> directory, however this file is intended
+		for use by the OpenLDAP utilities and should not really be used by the nss_ldap
+		utility since its content and structure serves the specific purpose of enabling
+		the resolution of user and group IDs via NSS.
+		</para>
+
+		<para>
+		Change the parameters inside the file that is located on your OS so it matches
+		<link linkend="ch9-sdmlcnf"/>.  To find the correct location of this file, you
+		can obtain this from the library that will be used by executing the following:
+<screen>
+&rootprompt; strings /lib/libnss_ldap* | grep ldap.conf
+/etc/ldap.conf
+</screen>
+		</para></step>
+
+		<step><para>
+		Configure the NSS control file so it matches the one shown in
+		<link linkend="ch9-sdmnss"/>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Identity resolution</primary></indexterm>
+		<indexterm><primary>getent</primary></indexterm>
+		Before proceeding to configure Samba, validate the operation of the NSS identity 
+		resolution via LDAP by executing:
+<screen>
+&rootprompt; getent passwd
+...
+root:x:0:512:Netbios Domain Administrator:/root:/bin/false
+nobody:x:999:514:nobody:/dev/null:/bin/false
+bobj:x:1000:513:Robert Jordan:/home/bobj:/bin/bash
+stans:x:1001:513:Stanley Soroka:/home/stans:/bin/bash
+chrisr:x:1002:513:Christine Roberson:/home/chrisr:/bin/bash
+maryv:x:1003:513:Mary Vortexis:/home/maryv:/bin/bash
+jht:x:1004:513:John H Terpstra:/home/jht:/bin/bash
+bldg1$:x:1006:553:bldg1$:/dev/null:/bin/false
+temptation$:x:1009:553:temptation$:/dev/null:/bin/false
+vaioboss$:x:1005:553:vaioboss$:/dev/null:/bin/false
+fran$:x:1008:553:fran$:/dev/null:/bin/false
+josephj:x:1007:513:Joseph James:/home/josephj:/bin/bash
+</screen>
+		You should notice the location of the users' home directories. First, make certain that
+		the home directories exist on the domain member server; otherwise, the home directory
+		share is not available. The home directories could be mounted off a domain controller
+		using NFS or by any other suitable means. Second, the absence of the domain name in the
+		home directory path is indicative that identity resolution is not being done via winbind.
+<screen>
+&rootprompt; getent group
+...
+Domain Admins:x:512:root,jht
+Domain Users:x:513:bobj,stans,chrisr,maryv,jht,josephj
+Domain Guests:x:514:
+Accounts:x:1000:
+Finances:x:1001:
+PIOps:x:1002:
+sammy:x:4321:
+</screen>
+		<indexterm><primary>secondary group</primary></indexterm>
+		<indexterm><primary>primary group</primary></indexterm>
+		<indexterm><primary>group membership</primary></indexterm>
+		This shows that all is working as it should be. Notice that in the LDAP database
+		the users' primary and secondary group memberships are identical. It is not
+		necessary to add secondary group memberships (in the group database) if the
+		user is already a member via primary group membership in the password database.
+		When using winbind, it is in fact undesirable to do this because it results in
+		doubling up of group memberships and may cause problems with winbind under certain 
+		conditions. It is intended that these limitations with winbind will be resolved soon
+		after Samba-3.0.20 has been released.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>slapcat</primary></indexterm>
+		The LDAP directory must have a container object for IDMAP data. There are several ways you can
+		check that your LDAP database is able to receive IDMAP information. One of the simplest is to
+		execute:
+<screen>
+&rootprompt; slapcat | grep -i idmap
+dn: ou=Idmap,dc=abmas,dc=biz
+ou: idmap
+</screen>
+		<indexterm><primary>ldapadd</primary></indexterm>
+		If the execution of this command does not return IDMAP entries, you need to create an LDIF
+		template file (see <link linkend="ch9-ldifadd"/>). You can add the required entries using
+		the following command:
+<screen>
+&rootprompt; ldapadd -x -D "cn=Manager,dc=abmas,dc=biz" \
+		-w not24get &lt; /etc/openldap/idmap.LDIF
+</screen>
+		</para></step>
+
+		<step><para>
+		Samba automatically populates the LDAP directory container when it needs to. To permit Samba
+		write access to the LDAP directory it is necessary to set the LDAP administrative password
+		in the <filename>secrets.tdb</filename> file as shown here:
+<screen>
+&rootprompt; smbpasswd -w not24get
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+		<indexterm><primary>Domain join</primary></indexterm>
+		The system is ready to join the domain. Execute the following:
+<screen>
+&rootprompt; net rpc join -U root%not24get
+Joined domain MEGANET2.
+</screen>
+		This indicates that the domain join succeeded.
+		</para>
+
+		<para>
+		Failure to join the domain could be caused by any number of variables. The most common
+		causes of failure to join are:
+		</para>
+
+		<para>
+		<itemizedlist>
+			<listitem><para>Broken resolution of NetBIOS names to the respective IP address.</para></listitem>
+			<listitem><para>Incorrect username and password credentials.</para></listitem>
+			<listitem><para>The NT4 <parameter>restrict anonymous</parameter> is set to exclude anonymous
+				connections.</para></listitem>
+		</itemizedlist> 
+		</para>
+
+		<para>
+		The connection setup can be diagnosed by executing:
+<screen>
+&rootprompt; net rpc join -S 'pdc-name' -U administrator%password -d 5
+</screen>
+		<indexterm><primary>failed</primary></indexterm>
+		<indexterm><primary>failed join</primary></indexterm>
+		<indexterm><primary>rejected</primary></indexterm>
+		<indexterm><primary>restrict anonymous</primary></indexterm>
+		Note: Use "root" for UNIX/Linux and Samba, use "Administrator" for Windows NT4/200X. If the cause of
+		the failure appears to be related to a rejected or failed NT_SESSION_SETUP*  or an error message that
+		says NT_STATUS_ACCESS_DENIED immediately check the Windows registry setting that controls the
+		<constant>restrict anonymous</constant> setting. Set this to the value 0 so that an anonymous connection
+		can be sustained, then try again.
+		</para>
+
+		<para>
+		It is possible (perhaps even recommended) to use the following to validate the ability to connect
+		to an NT4 PDC/BDC:
+<screen>
+&rootprompt; net rpc info -S 'pdc-name' -U Administrator%not24get
+Domain Name: MEGANET2
+Domain SID: S-1-5-21-422319763-4138913805-7168186429
+Sequence number: 1519909596
+Num users: 7003
+Num domain groups: 821
+Num local groups: 8
+
+&rootprompt; net rpc testjoin -S 'pdc-name' -U Administrator%not24get
+Join to 'MEGANET2' is OK
+</screen>
+		If for any reason the following response is obtained to the last command above,it is time to
+		call in the Networking Super-Snooper task force (i.e., start debugging):
+<screen>
+NT_STATUS_ACCESS_DENIED
+Join to 'MEGANET2' failed.
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>wbinfo</primary></indexterm>
+		Just joining the domain is not quite enough; you must now provide a privileged set
+		of credentials through which <command>winbindd</command> can interact with the 
+		domain servers. Execute the following to implant the necessary credentials:
+<screen>
+&rootprompt; wbinfo --set-auth-user=Administrator%not24get
+</screen>
+		The configuration is now ready to obtain the Samba domain user and group information.
+		</para></step>
+
+		<step><para>
+		You may now start Samba in the usual manner, and your Samba domain member server
+		is ready for use. Just add shares as required.
+		</para></step>
+
+	</procedure>
+
+<example id="ch9-sdmsdc">
+<title>Samba Domain Member in Samba Domain Using LDAP &smbmdash; &smb.conf; File</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="unix charset">LOCALE</smbconfoption>
+<smbconfoption name="workgroup">MEGANET2</smbconfoption>
+<smbconfoption name="security">DOMAIN</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="log level">10</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+<smbconfoption name="max log size">50</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="wins server">192.168.2.1</smbconfoption>
+<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
+<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
+<smbconfoption name="idmap backend">ldap:ldap://lapdc.abmas.biz</smbconfoption>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+<smbconfoption name="winbind trusted domains only">Yes</smbconfoption>
+<smbconfoption name="printer admin">root</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[print$]"/>
+<smbconfoption name="comment">Printer Drivers</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
+<smbconfoption name="admin users">root, Administrator</smbconfoption>
+<smbconfoption name="write list">root</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch9-ldifadd">
+<title>LDIF IDMAP Add-On Load File &smbmdash; File: /etc/openldap/idmap.LDIF</title>
+<screen>
+dn: ou=Idmap,dc=abmas,dc=biz
+objectClass: organizationalUnit
+ou: idmap
+structuralObjectClass: organizationalUnit
+</screen>
+</example>
+
+<example id="ch9-sdmlcnf">
+<title>Configuration File for NSS LDAP Support &smbmdash; <filename>/etc/ldap.conf</filename></title>
+<screen>
+URI     ldap://massive.abmas.biz ldap://massive.abmas.biz:636
+host    192.168.2.1
+base    dc=abmas,dc=biz
+binddn  cn=Manager,dc=abmas,dc=biz
+bindpw  not24get
+
+pam_password exop
+
+nss_base_passwd ou=People,dc=abmas,dc=biz?one
+nss_base_shadow ou=People,dc=abmas,dc=biz?one
+nss_base_group  ou=Groups,dc=abmas,dc=biz?one
+ssl     no
+</screen>
+</example>
+
+<example id="ch9-sdmnss">
+<title>NSS using LDAP for Identity Resolution &smbmdash; File: <filename>/etc/nsswitch.conf</filename></title>
+<screen>
+passwd:         files ldap
+shadow:         files ldap
+group:          files ldap
+
+hosts:          files dns wins
+networks:       files dns
+
+services:       files
+protocols:      files
+rpc:            files
+ethers:         files
+netmasks:       files
+netgroup:       files
+publickey:      files
+
+bootparams:     files
+automount:      files
+aliases:        files
+</screen>
+</example>
+
+	</sect2>
+
+	<sect2 id="wdcsdm">
+		<title>NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</title>
+
+	<para>
+	You need to use this method for creating a Samba domain member server if any of the following conditions
+	prevail:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		LDAP support (client) is not installed on the system.
+		</para></listitem>
+
+		<listitem><para>
+		There are mitigating circumstances forcing a decision not to use LDAP.
+		</para></listitem>
+
+		<listitem><para>
+		The Samba domain member server must be part of a Windows NT4 Domain, or a Samba Domain.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	<indexterm><primary>Windows ADS Domain</primary></indexterm>
+	<indexterm><primary>Samba Domain</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	Later in the chapter, you can see how to configure a Samba domain member server for a Windows ADS domain.
+	Right now your objective is to configure a Samba server that can be a member of a Windows NT4-style
+	domain and/or does not use LDAP.
+	</para>
+
+	<note><para>
+	<indexterm><primary>duplicate accounts</primary></indexterm>
+	If you use <command>winbind</command> for identity resolution, make sure that there are no
+	duplicate accounts.
+	</para>
+
+	<para>
+	<indexterm><primary>/etc/passwd</primary></indexterm>
+	For example, do not have more than one account that has UID=0 in the password database. If there 
+	is an account called <constant>root</constant> in the <filename>/etc/passwd</filename> database, 
+	it is okay to have an account called <constant>root</constant> in the LDAP ldapsam or in the 
+	tdbsam. But if there are two accounts in the passdb backend that have the same UID, winbind will 
+	break. This means that the <constant>Administrator</constant> account must be called 
+	<constant>root</constant>.
+	</para>
+
+	<para>
+	<indexterm><primary>/etc/passwd</primary></indexterm>
+	<indexterm><primary>ldapsam</primary></indexterm>
+	<indexterm><primary>tdbsam</primary></indexterm>
+	Winbind will break if there is an account in <filename>/etc/passwd</filename> that has 
+	the same UID as an account that is in LDAP ldapsam (or in tdbsam) but that differs in name only.
+	</para></note>
+
+	<para>
+	<indexterm><primary>credentials</primary></indexterm>
+	<indexterm><primary>traverse</primary></indexterm>
+	<indexterm><primary>wide-area</primary></indexterm>
+	<indexterm><primary>network</primary><secondary>wide-area</secondary></indexterm>
+	<indexterm><primary>tdbdump</primary></indexterm>
+	The following configuration uses CIFS/SMB protocols alone to obtain user and group credentials.
+	The winbind information is locally cached in the <filename>winbindd_cache.tdb winbindd_idmap.tdb</filename>
+	files. This provides considerable performance benefits compared with the LDAP solution, particularly
+	where the LDAP lookups must traverse WAN links. You may examine the contents of these
+	files using the tool <command>tdbdump</command>, though you may have to build this from the Samba
+	source code if it has not been supplied as part of a binary package distribution that you may be using.
+	</para>
+
+	<procedure>
+	<title>Configuration of Winbind-Based Identity Resolution</title>
+
+		<step><para>
+		Using your favorite text editor, create the &smb.conf; file so it has the contents
+		shown in <link linkend="ch0-NT4DSDM"/>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+		Edit the <filename>/etc/nsswitch.conf</filename> so it has the entries shown in
+		<link linkend="ch9-sdmnss"/>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+		The system is ready to join the domain. Execute the following:
+<screen>
+net rpc join -U root%not2g4et
+Joined domain MEGANET2.
+</screen>
+		This indicates that the domain join succeed.
+
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>winbind</primary></indexterm>
+		<indexterm><primary>wbinfo</primary></indexterm>
+		Validate operation of <command>winbind</command> using the <command>wbinfo</command>
+		tool as follows:
+<screen>
+&rootprompt; wbinfo -u
+MEGANET2+root
+MEGANET2+nobody
+MEGANET2+jht
+MEGANET2+maryv
+MEGANET2+billr
+MEGANET2+jelliott
+MEGANET2+dbrady
+MEGANET2+joeg
+MEGANET2+balap
+</screen>
+		This shows that domain users have been listed correctly.
+<screen>
+&rootprompt; wbinfo -g
+MEGANET2+Domain Admins
+MEGANET2+Domain Users
+MEGANET2+Domain Guests
+MEGANET2+Accounts
+MEGANET2+Finances
+MEGANET2+PIOps
+</screen>
+		This shows that domain groups have been correctly obtained also.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>NSS</primary></indexterm>
+		<indexterm><primary>getent</primary></indexterm>
+		<indexterm><primary>winbind</primary></indexterm>
+		The next step verifies that NSS is able to obtain this information
+		correctly from <command>winbind</command> also.
+<screen>
+&rootprompt; getent passwd
+...
+MEGANET2+root:x:10000:10001:NetBIOS Domain Admin:
+                      /home/MEGANET2/root:/bin/bash
+MEGANET2+nobody:x:10001:10001:nobody:
+                      /home/MEGANET2/nobody:/bin/bash
+MEGANET2+jht:x:10002:10001:John H Terpstra:
+                      /home/MEGANET2/jht:/bin/bash
+MEGANET2+maryv:x:10003:10001:Mary Vortexis:
+                      /home/MEGANET2/maryv:/bin/bash
+MEGANET2+billr:x:10004:10001:William Randalph:
+                      /home/MEGANET2/billr:/bin/bash
+MEGANET2+jelliott:x:10005:10001:John G Elliott:
+                      /home/MEGANET2/jelliott:/bin/bash
+MEGANET2+dbrady:x:10006:10001:Darren Brady:
+                      /home/MEGANET2/dbrady:/bin/bash
+MEGANET2+joeg:x:10007:10001:Joe Green:
+                      /home/MEGANET2/joeg:/bin/bash
+MEGANET2+balap:x:10008:10001:Bala Pillay:
+                      /home/MEGANET2/balap:/bin/bash
+</screen>
+		The user account information has been correctly obtained. This information has
+		been merged with the winbind template information configured in the &smb.conf; file.
+<screen>
+&rootprompt;# getent group
+...
+MEGANET2+Domain Admins:x:10000:MEGANET2+root,MEGANET2+jht
+MEGANET2+Domain Users:x:10001:MEGANET2+jht,MEGANET2+maryv,\
+        MEGANET2+billr,MEGANET2+jelliott,MEGANET2+dbrady,\
+        MEGANET2+joeg,MEGANET2+balap
+MEGANET2+Domain Guests:x:10002:MEGANET2+nobody
+MEGANET2+Accounts:x:10003:
+MEGANET2+Finances:x:10004:
+MEGANET2+PIOps:x:10005:
+</screen>
+		</para></step>
+
+		<step><para>
+		The Samba member server of a Windows NT4 domain is ready for use.
+		</para></step>
+
+	</procedure>
+
+<example id="ch0-NT4DSDM">
+<title>Samba Domain Member Server Using Winbind &smb.conf; File for NT4 Domain</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="unix charset">LOCALE</smbconfoption>
+<smbconfoption name="workgroup">MEGANET2</smbconfoption>
+<smbconfoption name="security">DOMAIN</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="log level">1</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+<smbconfoption name="max log size">0</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="wins server">192.168.2.1</smbconfoption>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+<smbconfoption name="template primary group">"Domain Users"</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+<smbconfoption name="winbind separator">+</smbconfoption>
+<smbconfoption name="printer admin">root</smbconfoption>
+<smbconfoption name="hosts allow">192.168.2., 192.168.3., 127.</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[print$]"/>
+<smbconfoption name="comment">Printer Drivers</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
+<smbconfoption name="admin users">root, Administrator</smbconfoption>
+<smbconfoption name="write list">root</smbconfoption>
+</smbconfblock>
+</example>
+
+	</sect2>
+
+	<sect2 id="dcwonss">
+	<title>NT4/Samba Domain with Samba Domain Member Server without NSS Support</title>
+
+	<para>
+	No matter how many UNIX/Linux administrators there may be who believe that a UNIX operating
+	system that does not have NSS and PAM support to be outdated, the fact is there
+	are still many such systems in use today. Samba can be used without NSS support, but this
+	does limit it to the use of local user and group accounts only.
+	</para>
+
+	<para>
+	The following steps may be followed to implement Samba with support for local accounts.
+	In this configuration Samba is made a domain member server. All incoming connections
+	to the Samba server will cause the look-up of the incoming username. If the account
+	is found, it is used. If the account is not found, one will be automatically created
+	on the local machine so that it can then be used for all access controls.
+	</para>
+
+	<procedure>
+	<title>Configuration Using Local Accounts Only</title>
+
+		<step><para>
+		Using your favorite text editor, create the &smb.conf; file so it has the contents
+		shown in <link linkend="ch0-NT4DSCM"/>.
+		</para></step>
+
+		<step>
+		<para><indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+		The system is ready to join the domain. Execute the following:
+<screen>
+net rpc join -U root%not24get
+Joined domain MEGANET2.
+</screen>
+		This indicates that the domain join succeed.
+		</para></step>
+
+		<step><para>
+		Be sure to run all three Samba daemons: <command>smbd</command>, <command>nmbd</command>, <command>winbindd</command>.
+		</para></step>
+
+		<step><para>
+		The Samba member server of a Windows NT4 domain is ready for use.
+		</para></step>
+	</procedure>
+
+<example id="ch0-NT4DSCM">
+<title>Samba Domain Member Server Using Local Accounts &smb.conf; File for NT4 Domain</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="unix charset">LOCALE</smbconfoption>
+<smbconfoption name="workgroup">MEGANET3</smbconfoption>
+<smbconfoption name="netbios name">BSDBOX</smbconfoption>
+<smbconfoption name="security">DOMAIN</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="log level">1</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="add user script">/usr/sbin/useradd -m '%u'</smbconfoption>
+<smbconfoption name="add machine script">/usr/sbin/useradd -M '%u'</smbconfoption>
+<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+<smbconfoption name="max log size">0</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="wins server">192.168.2.1</smbconfoption>
+<smbconfoption name="printer admin">root</smbconfoption>
+<smbconfoption name="hosts allow">192.168.2., 192.168.3., 127.</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[print$]"/>
+<smbconfoption name="comment">Printer Drivers</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
+<smbconfoption name="admin users">root, Administrator</smbconfoption>
+<smbconfoption name="write list">root</smbconfoption>
+</smbconfblock>
+</example>
+	</sect2>
+
+	<sect2 id="adssdm">
+	<title>Active Directory Domain with Samba Domain Member Server</title>
+
+	<para>
+	<indexterm><primary>Active Directory</primary><secondary>join</secondary></indexterm>
+	<indexterm><primary>Kerberos</primary></indexterm>
+	<indexterm><primary>Domain Member</primary><secondary>server</secondary></indexterm>
+	One of the much-sought-after features new to Samba-3 is the ability to join an Active Directory
+	domain using Kerberos protocols. This makes it possible to operate an entire Windows network
+	without the need to run NetBIOS over TCP/IP and permits more secure networking in general. An
+	exhaustively complete discussion of the protocols is not possible in this book; perhaps a
+	later book may explore the intricacies of the NetBIOS-less operation that Samba-3 can participate
+	in. For now, we simply focus on how a Samba-3 server can be made a domain member server.
+	</para>
+
+	<para>
+	<indexterm><primary>Active Directory</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>Identity resolution</primary></indexterm>
+	<indexterm><primary>Kerberos</primary></indexterm>
+	The diagram in <link linkend="ch9-adsdc"/> demonstrates how Samba-3 interfaces with
+	Microsoft Active Directory components. It should be noted that if Microsoft Windows Services
+	for UNIX (SFU) has been installed and correctly configured, it is possible to use client LDAP
+	for identity resolution just as can be done with Samba-3 when using an LDAP passdb backend.
+	The UNIX tool that you need for this, as in the case of LDAP on UNIX/Linux, is the PADL
+	Software nss_ldap tool-set. Compared with use of winbind and Kerberos, the use of 
+	LDAP-based identity resolution is a little less secure. In view of the fact that this solution
+	requires additional software to be installed on the Windows 200x ADS domain controllers,
+	and that means more management overhead, it is likely that most Samba-3 ADS client sites
+	may elect to use winbind.
+	</para>
+
+	<para>
+	Do not attempt to use this procedure if you are not 100 percent certain that the build of Samba-3
+	you are using has been compiled and linked with all the tools necessary for this to work.
+	Given the importance of this step, you must first validate that the Samba-3 message block
+	daemon (<command>smbd</command>) has the necessary features.
+	</para>
+
+	<para>
+	The hypothetical domain you are using in this example assumes that the Abmas London office
+	decided to take its own lead (some would say this is a typical behavior in a global
+	corporate world; besides, a little divergence and conflict makes for an interesting life).
+	The Windows Server 2003 ADS domain is called <constant>london.abmas.biz</constant> and the
+	name of the server is <constant>W2K3S</constant>. In ADS realm terms, the domain controller
+	is known as <constant>w2k3s.london.abmas.biz</constant>. In NetBIOS nomenclature, the
+	domain name is <constant>LONDON</constant> and the server name is <constant>W2K3S</constant>.
+	</para>
+
+	<figure id="ch9-adsdc">
+		<title>Active Directory Domain: Samba Member Server</title>
+		<imagefile scale="60">chap9-ADSDC</imagefile>
+	</figure>
+
+	<procedure>
+	<title>Joining a Samba Server as an ADS Domain Member</title>
+
+		<step><para>
+		<indexterm><primary>smbd</primary></indexterm>
+		Before you try to use Samba-3, you want to know for certain that your executables have
+		support for Kerberos and for LDAP. Execute the following to identify whether or
+		not this build is perhaps suitable for use:
+<screen>
+&rootprompt; cd /usr/sbin
+&rootprompt; smbd -b | grep KRB
+   HAVE_KRB5_H
+   HAVE_ADDR_TYPE_IN_KRB5_ADDRESS
+   HAVE_KRB5
+   HAVE_KRB5_AUTH_CON_SETKEY
+   HAVE_KRB5_GET_DEFAULT_IN_TKT_ETYPES
+   HAVE_KRB5_GET_PW_SALT
+   HAVE_KRB5_KEYBLOCK_KEYVALUE
+   HAVE_KRB5_KEYTAB_ENTRY_KEYBLOCK
+   HAVE_KRB5_MK_REQ_EXTENDED
+   HAVE_KRB5_PRINCIPAL_GET_COMP_STRING
+   HAVE_KRB5_SET_DEFAULT_IN_TKT_ETYPES
+   HAVE_KRB5_STRING_TO_KEY
+   HAVE_KRB5_STRING_TO_KEY_SALT
+   HAVE_LIBKRB5
+</screen>
+		This output was obtained on a SUSE Linux system and shows the output for
+		Samba that has been compiled and linked with the Heimdal Kerberos libraries.
+		The following is a typical output that will be found on a Red Hat Linux system that
+		has been linked with the MIT Kerberos libraries:
+<screen>
+&rootprompt; cd /usr/sbin
+&rootprompt; smbd -b | grep KRB
+   HAVE_KRB5_H
+   HAVE_ADDRTYPE_IN_KRB5_ADDRESS
+   HAVE_KRB5
+   HAVE_KRB5_AUTH_CON_SETUSERUSERKEY
+   HAVE_KRB5_ENCRYPT_DATA
+   HAVE_KRB5_FREE_DATA_CONTENTS
+   HAVE_KRB5_FREE_KTYPES
+   HAVE_KRB5_GET_PERMITTED_ENCTYPES
+   HAVE_KRB5_KEYTAB_ENTRY_KEY
+   HAVE_KRB5_LOCATE_KDC
+   HAVE_KRB5_MK_REQ_EXTENDED
+   HAVE_KRB5_PRINCIPAL2SALT
+   HAVE_KRB5_PRINC_COMPONENT
+   HAVE_KRB5_SET_DEFAULT_TGS_KTYPES
+   HAVE_KRB5_SET_REAL_TIME
+   HAVE_KRB5_STRING_TO_KEY
+   HAVE_KRB5_TKT_ENC_PART2
+   HAVE_KRB5_USE_ENCTYPE
+   HAVE_LIBGSSAPI_KRB5
+   HAVE_LIBKRB5
+</screen>
+		You can validate that Samba has been compiled and linked with LDAP support
+		by executing:
+<screen>
+&rootprompt; smbd -b | grep LDAP
+massive:/usr/sbin # smbd -b | grep LDAP
+   HAVE_LDAP_H
+   HAVE_LDAP
+   HAVE_LDAP_DOMAIN2HOSTLIST
+   HAVE_LDAP_INIT
+   HAVE_LDAP_INITIALIZE
+   HAVE_LDAP_SET_REBIND_PROC
+   HAVE_LIBLDAP
+   LDAP_SET_REBIND_PROC_ARGS
+</screen>
+		This does look promising; <command>smbd</command> has been built with Kerberos and LDAP
+		support. You are relieved to know that it is safe to progress.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Kerberos</primary><secondary>libraries</secondary></indexterm>
+		<indexterm><primary>MIT Kerberos</primary></indexterm>
+		<indexterm><primary>Heimdal Kerberos</primary></indexterm>
+		<indexterm><primary>Kerberos</primary><secondary>MIT</secondary></indexterm>
+		<indexterm><primary>Kerberos</primary><secondary>Heimdal</secondary></indexterm>
+		<indexterm><primary>Red Hat Linux</primary></indexterm>
+		<indexterm><primary>SUSE Linux</primary></indexterm>
+		<indexterm><primary>SerNet</primary></indexterm>
+		<indexterm><primary>validated</primary></indexterm>
+		The next step is to identify which version of the Kerberos libraries have been used.
+		In order to permit Samba-3 to interoperate with Windows 2003 Active Directory, it is
+		essential that it has been linked with either MIT Kerberos version 1.3.1 or later,
+		or that it has been linked with Heimdal Kerberos 0.6 plus specific patches. You may
+		identify what version of the MIT Kerberos libraries are installed on your system by
+		executing (on Red Hat Linux):
+<screen>
+&rootprompt; rpm -q krb5
+</screen>
+		Or on SUSE Linux, execute:
+<screen>
+&rootprompt; rpm -q heimdal
+</screen>
+		Please note that the RPMs provided by the Samba-Team are known to be working and have
+		been validated. Red Hat Linux RPMs may be obtained from the Samba FTP sites. SUSE
+		Linux RPMs may be obtained from <ulink url="ftp://ftp.sernet.de">Sernet</ulink> in
+		Germany.
+		</para>
+
+		<para>
+		From this point on, you are certain that the Samba-3 build you are using has the
+		necessary capabilities. You can now configure Samba-3 and the NSS. 
+		</para></step>
+
+		<step><para>
+		Using you favorite editor, configure the &smb.conf; file that is located in the 
+		<filename>/etc/samba</filename> directory so that it has the contents shown 
+		in <link linkend="ch9-adssdm"/>.
+		</para></step>
+
+		<step><para>
+		Edit or create the NSS control file so it has the contents shown in <link linkend="ch9-sdmnss"/>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/samba/secrets.tdb</primary></indexterm>
+		Delete the file <filename>/etc/samba/secrets.tdb</filename> if it exists. Of course, you
+		do keep a backup, don't you?
+		</para></step>
+
+		<step><para>
+		Delete the tdb files that cache Samba information. You keep a backup of the old
+		files, of course. You also remove all files to ensure that nothing can pollute your
+		nice, new configuration. Execute the following (example is for SUSE Linux):
+<screen>
+&rootprompt; rm /var/lib/samba/*tdb
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>testparm</primary></indexterm>
+		Validate your &smb.conf; file using <command>testparm</command> (as you have
+		done previously). Correct all errors reported before proceeding. The command you
+		execute is:
+<screen>
+&rootprompt; testparm -s | less
+</screen>
+		Now that you are satisfied that your Samba server is ready to join the Windows
+		ADS domain, let's move on.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
+		<indexterm><primary>Kerberos</primary></indexterm>
+		This is a good time to double-check everything and then execute the following
+		command when everything you have done has checked out okay:
+<screen>
+&rootprompt; net ads join -UAdministrator%not24get
+Using short domain name -- LONDON
+Joined 'FRAN' to realm 'LONDON.ABMAS.BIZ'
+</screen>
+		You have successfully made your Samba-3 server a member of the ADS domain
+		using Kerberos protocols.
+		</para>
+
+	    <para>
+		<indexterm><primary>silent return</primary></indexterm>
+		<indexterm><primary>failed join</primary></indexterm>
+		In the event that you receive no output messages, a silent return means that the
+		domain join failed. You should use <command>ethereal</command> to identify what
+		may be failing. Common causes of a failed join include:
+
+		<itemizedlist>
+			<listitem><para>
+			<indexterm><primary>name resolution</primary><secondary>Defective</secondary></indexterm>
+			Defective or misconfigured DNS name resolution.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>Restrictive security</primary></indexterm>
+			Restrictive security settings on the Windows 200x ADS domain controller
+			preventing needed communications protocols. You can check this by searching
+			the Windows Server 200x Event Viewer.
+			</para></listitem>
+
+			<listitem><para>
+			Incorrectly configured &smb.conf; file settings.
+			</para></listitem>
+
+			<listitem><para>
+			Lack of support of necessary Kerberos protocols because the version of MIT
+			Kerberos (or Heimdal) in use is not up to date enough to support the necessary
+			functionality.
+			</para></listitem>
+		</itemizedlist>
+
+		<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+		<indexterm><primary>RPC</primary></indexterm>
+		<indexterm><primary>mixed mode</primary></indexterm>
+		In any case, never execute the <command>net rpc join</command> command in an attempt
+		to join the Samba server to the domain, unless you wish not to use the Kerberos
+		security protocols. Use of the older RPC-based domain join facility requires that
+		Windows Server 200x ADS has been configured appropriately for mixed mode operation.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>tdbdump</primary></indexterm>
+		<indexterm><primary>/etc/samba/secrets.tdb</primary></indexterm>
+		If the <command>tdbdump</command> is installed on your system (not essential),
+		you can look inside the <filename>/etc/samba/secrets.tdb</filename> file. If
+		you wish to do this, execute:
+<screen>
+&rootprompt; tdbdump secrets.tdb
+{
+key = "SECRETS/SID/LONDON"
+data = "\01\04\00\00\00\00\00\05\15\00\00\00\EBw\86\F1\ED\BD\
+   F6{\5C6\E5W\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
+   00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
+   00\00\00\00\00\00\00\00"
+}
+{
+key = "SECRETS/MACHINE_PASSWORD/LONDON"
+data = "le3Q5FPnN5.ueC\00"
+}
+{
+key = "SECRETS/MACHINE_SEC_CHANNEL_TYPE/LONDON"
+data = "\02\00\00\00"
+}
+{
+key = "SECRETS/MACHINE_LAST_CHANGE_TIME/LONDON"
+data = "E\89\F6?"
+}
+</screen>
+		This is given to demonstrate to the skeptics that this process truly does work.
+		</para></step>
+
+		<step><para>
+		It is now time to start Samba in the usual way (as has been done many time before
+		in this book).	
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>wbinfo</primary></indexterm>
+		This is a good time to verify that everything is working. First, check that
+		winbind is able to obtain the list of users and groups from the ADS domain controller.
+		Execute the following:
+<screen>
+&rootprompt; wbinfo -u
+LONDON+Administrator
+LONDON+Guest
+LONDON+SUPPORT_388945a0
+LONDON+krbtgt
+LONDON+jht
+</screen>
+		Good, the list of users was obtained. Now do likewise for group accounts:
+<screen>
+&rootprompt; wbinfo -g
+LONDON+Domain Computers
+LONDON+Domain Controllers
+LONDON+Schema Admins
+LONDON+Enterprise Admins
+LONDON+Domain Admins
+LONDON+Domain Users
+LONDON+Domain Guests
+LONDON+Group Policy Creator Owners
+LONDON+DnsUpdateProxy
+</screen>
+		Excellent. That worked also, as expected.
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>getent</primary>
+	      </indexterm>
+		Now repeat this via NSS to validate that full identity resolution is
+		functional as required. Execute:
+<screen>
+&rootprompt; getent passwd
+...
+LONDON+Administrator:x:10000:10000:Administrator:
+             /home/LONDON/administrator:/bin/bash
+LONDON+Guest:x:10001:10001:Guest:
+             /home/LONDON/guest:/bin/bash
+LONDON+SUPPORT_388945a0:x:10002:10000:SUPPORT_388945a0:
+             /home/LONDON/support_388945a0:/bin/bash
+LONDON+krbtgt:x:10003:10000:krbtgt:
+             /home/LONDON/krbtgt:/bin/bash
+LONDON+jht:x:10004:10000:John H. Terpstra:
+             /home/LONDON/jht:/bin/bash
+</screen>
+		Okay, ADS user accounts are being resolved. Now you try group resolution:
+<screen>
+&rootprompt; getent group
+...
+LONDON+Domain Computers:x:10002:
+LONDON+Domain Controllers:x:10003:
+LONDON+Schema Admins:x:10004:LONDON+Administrator
+LONDON+Enterprise Admins:x:10005:LONDON+Administrator
+LONDON+Domain Admins:x:10006:LONDON+jht,LONDON+Administrator
+LONDON+Domain Users:x:10000:
+LONDON+Domain Guests:x:10001:
+LONDON+Group Policy Creator Owners:x:10007:LONDON+Administrator
+LONDON+DnsUpdateProxy:x:10008:
+</screen>
+		This is very pleasing. Everything works as expected.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>info</tertiary></indexterm>
+		<indexterm><primary>Active Directory</primary><secondary>server</secondary></indexterm>
+		<indexterm><primary>Kerberos</primary></indexterm>
+		You may now perform final verification that communications between Samba-3 winbind and
+		the Active Directory server is using Kerberos protocols. Execute the following:
+<screen>
+&rootprompt; net ads info
+LDAP server: 192.168.2.123
+LDAP server name: w2k3s
+Realm: LONDON.ABMAS.BIZ
+Bind Path: dc=LONDON,dc=ABMAS,dc=BIZ
+LDAP port: 389
+Server time: Sat, 03 Jan 2004 02:44:44 GMT
+KDC server: 192.168.2.123
+Server time offset: 2
+</screen>
+		It should be noted that Kerberos protocols are time-clock critical. You should
+		keep all server time clocks synchronized using the network time protocol (NTP).
+		In any case, the output we obtained confirms that all systems are operational.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>status</tertiary></indexterm>
+		There is one more action you elect to take, just because you are paranoid and disbelieving,
+		so you execute the following command:
+<programlisting>
+&rootprompt; net ads status -UAdministrator%not24get
+objectClass: top
+objectClass: person
+objectClass: organizationalPerson
+objectClass: user
+objectClass: computer
+cn: fran
+distinguishedName: CN=fran,CN=Computers,DC=london,DC=abmas,DC=biz
+instanceType: 4
+whenCreated: 20040103092006.0Z
+whenChanged: 20040103092006.0Z
+uSNCreated: 28713
+uSNChanged: 28717
+name: fran
+objectGUID: 58f89519-c467-49b9-acb0-f099d73696e
+userAccountControl: 69632
+badPwdCount: 0
+codePage: 0
+countryCode: 0
+badPasswordTime: 0
+lastLogoff: 0
+lastLogon: 127175965783327936
+localPolicyFlags: 0
+pwdLastSet: 127175952062598496
+primaryGroupID: 515
+objectSid: S-1-5-21-4052121579-2079768045-1474639452-1109
+accountExpires: 9223372036854775807
+logonCount: 13
+sAMAccountName: fran$
+sAMAccountType: 805306369
+operatingSystem: Samba
+operatingSystemVersion: 3.0.20-SUSE
+dNSHostName: fran
+userPrincipalName: HOST/fran@LONDON.ABMAS.BIZ
+servicePrincipalName: CIFS/fran.london.abmas.biz
+servicePrincipalName: CIFS/fran
+servicePrincipalName: HOST/fran.london.abmas.biz
+servicePrincipalName: HOST/fran
+objectCategory: CN=Computer,CN=Schema,CN=Configuration,
+                              DC=london,DC=abmas,DC=biz
+isCriticalSystemObject: FALSE
+-------------- Security Descriptor (revision: 1, type: 0x8c14)
+owner SID: S-1-5-21-4052121579-2079768045-1474639452-512
+group SID: S-1-5-21-4052121579-2079768045-1474639452-513
+------- (system) ACL (revision: 4, size: 120, number of ACEs: 2)
+------- ACE (type: 0x07, flags: 0x5a, size: 0x38, 
+               mask: 0x20, object flags: 0x3)
+access SID:  S-1-1-0
+access type: AUDIT OBJECT
+Permissions:
+        [Write All Properties]
+------- ACE (type: 0x07, flags: 0x5a, size: 0x38, 
+               mask: 0x20, object flags: 0x3)
+access SID:  S-1-1-0
+access type: AUDIT OBJECT
+Permissions:
+        [Write All Properties]
+------- (user) ACL (revision: 4, size: 1944, number of ACEs: 40)
+------- ACE (type: 0x00, flags: 0x00, size: 0x24, mask: 0xf01ff)
+access SID:  S-1-5-21-4052121579-2079768045-1474639452-512
+access type: ALLOWED
+Permissions: [Full Control]
+------- ACE (type: 0x00, flags: 0x00, size: 0x18, mask: 0xf01ff)
+access SID:  S-1-5-32-548
+...
+------- ACE (type: 0x05, flags: 0x12, size: 0x38, 
+                mask: 0x10, object flags: 0x3)
+access SID:  S-1-5-9
+access type: ALLOWED OBJECT
+Permissions:
+        [Read All Properties]
+-------------- End Of Security Descriptor
+</programlisting>
+		And now you have conclusive proof that your Samba-3 ADS domain member server
+		called <constant>FRAN</constant> is able to communicate fully with the ADS
+		domain controllers.
+		</para></step>
+
+	</procedure>
+
+
+	<para>
+	Your Samba-3 ADS domain member server is ready for use. During training sessions,
+	you may be asked what is inside the <filename>winbindd_cache.tdb and winbindd_idmap.tdb</filename>
+	files. Since curiosity just took hold of you, execute the following:
+<programlisting>
+&rootprompt; tdbdump /var/lib/samba/winbindd_idmap.tdb
+{
+key = "S-1-5-21-4052121579-2079768045-1474639452-501\00"
+data = "UID 10001\00"
+}
+{
+key = "UID 10005\00"
+data = "S-1-5-21-4052121579-2079768045-1474639452-1111\00"
+}
+{
+key = "GID 10004\00"
+data = "S-1-5-21-4052121579-2079768045-1474639452-518\00"
+}
+{
+key = "S-1-5-21-4052121579-2079768045-1474639452-502\00"
+data = "UID 10003\00"
+}
+...
+
+&rootprompt; tdbdump /var/lib/samba/winbindd_cache.tdb
+{
+key = "UL/LONDON"
+data = "\00\00\00\00bp\00\00\06\00\00\00\0DAdministrator\0D
+   Administrator-S-1-5-21-4052121579-2079768045-1474639452-500-
+   S-1-5-21-4052121579-2079768045-1474639452-513\05Guest\05
+   Guest-S-1-5-21-4052121579-2079768045-1474639452-501-
+   S-1-5-21-4052121579-2079768045-1474639452-514\10
+   SUPPORT_388945a0\10SUPPORT_388945a0.
+   S-1-5-21-4052121579-2079768045-1474639452-1001-
+   S-1-5-21-4052121579-2079768045-1474639452-513\06krbtgt\06
+   krbtgt-S-1-5-21-4052121579-2079768045-1474639452-502-
+   S-1-5-21-4052121579-2079768045-1474639452-513\03jht\10
+   John H. Terpstra.S-1-5-21-4052121579-2079768045-1474639452-1110-
+   S-1-5-21-4052121579-2079768045-1474639452-513"
+}
+{
+key = "GM/S-1-5-21-4052121579-2079768045-1474639452-512"
+data = "\00\00\00\00bp\00\00\02\00\00\00.
+   S-1-5-21-4052121579-2079768045-1474639452-1110\03
+   jht\01\00\00\00-S-1-5-21-4052121579-2079768045-1474639452-500\0D
+   Administrator\01\00\00\00"
+}
+{
+key = "SN/S-1-5-21-4052121579-2079768045-1474639452-513"
+data = "\00\00\00\00xp\00\00\02\00\00\00\0CDomain Users"
+}
+{
+key = "GM/S-1-5-21-4052121579-2079768045-1474639452-518"
+data = "\00\00\00\00bp\00\00\01\00\00\00-
+   S-1-5-21-4052121579-2079768045-1474639452-500\0D
+   Administrator\01\00\00\00"
+}
+{
+key = "SEQNUM/LONDON\00"
+data = "xp\00\00C\92\F6?"
+}
+{
+key = "U/S-1-5-21-4052121579-2079768045-1474639452-1110"
+data = "\00\00\00\00xp\00\00\03jht\10John H. Terpstra.
+   S-1-5-21-4052121579-2079768045-1474639452-1110-
+   S-1-5-21-4052121579-2079768045-1474639452-513"
+}
+{
+key = "NS/S-1-5-21-4052121579-2079768045-1474639452-502"
+data = "\00\00\00\00bp\00\00-
+   S-1-5-21-4052121579-2079768045-1474639452-502"
+}
+{
+key = "SN/S-1-5-21-4052121579-2079768045-1474639452-1001"
+data = "\00\00\00\00bp\00\00\01\00\00\00\10SUPPORT_388945a0"
+}
+{
+key = "SN/S-1-5-21-4052121579-2079768045-1474639452-500"
+data = "\00\00\00\00bp\00\00\01\00\00\00\0DAdministrator"
+}
+{
+key = "U/S-1-5-21-4052121579-2079768045-1474639452-502"
+data = "\00\00\00\00bp\00\00\06krbtgt\06krbtgt-
+   S-1-5-21-4052121579-2079768045-1474639452-502-
+   S-1-5-21-4052121579-2079768045-1474639452-513"
+}
+....
+</programlisting>
+	Now all is revealed. Your curiosity, as well as that of your team, has been put at ease.
+	May this server serve well all who happen upon it.
+	</para>
+
+<example id="ch9-adssdm">
+<title>Samba Domain Member &smb.conf; File for Active Directory Membership</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="unix charset">LOCALE</smbconfoption>
+<smbconfoption name="workgroup">LONDON</smbconfoption>
+<smbconfoption name="realm">LONDON.ABMAS.BIZ</smbconfoption>
+<smbconfoption name="server string">Samba 3.0.20</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="log level">1</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+<smbconfoption name="max log size">50</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="ldap ssl">no</smbconfoption>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+<smbconfoption name="template primary group">"Domain Users"</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+<smbconfoption name="winbind separator">+</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[print$]"/>
+<smbconfoption name="comment">Printer Drivers</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
+<smbconfoption name="admin users">root, Administrator</smbconfoption>
+<smbconfoption name="write list">root</smbconfoption>
+</smbconfblock>
+</example>
+
+        <sect3>
+        <title>IDMAP_RID with Winbind</title>
+
+        <para>
+        <indexterm><primary>idmap_rid</primary></indexterm>
+        <indexterm><primary>SID</primary></indexterm>
+        <indexterm><primary>RID</primary></indexterm>
+        <indexterm><primary>IDMAP</primary></indexterm>
+        The <command>idmap_rid</command> facility is a new tool that, unlike native winbind, creates a
+        predictable mapping of MS Windows SIDs to UNIX UIDs and GIDs. The key benefit of this method
+        of implementing the Samba IDMAP facility is that it eliminates the need to store the IDMAP data
+        in a central place. The downside is that it can be used only within a single ADS domain and
+        is not compatible with trusted domain implementations.
+        </para>
+
+        <para>
+        <indexterm><primary>SID</primary></indexterm>
+        <indexterm><primary>allow trusted domains</primary></indexterm>
+        <indexterm><primary>idmap uid</primary></indexterm>
+        <indexterm><primary>idmap gid</primary></indexterm>
+        This alternate method of SID to UID/GID  mapping can be achieved with the idmap_rid
+        plug-in. This plug-in uses the RID of the user SID to derive the UID and GID by adding the
+        RID to a base value specified. This utility requires that the parameter
+        <quote>allow trusted domains = No</quote> must be specified, as it is not compatible
+        with multiple domain environments. The <parameter>idmap uid</parameter> and
+        <parameter>idmap gid</parameter> ranges must be specified.
+        </para>
+
+        <para>
+        <indexterm><primary>idmap_rid</primary></indexterm>
+        <indexterm><primary>realm</primary></indexterm>
+        The idmap_rid facility can be used both for NT4/Samba-style domains as well as with Active Directory.
+        To use this with an NT4 domain, the <parameter>realm</parameter> is not used. Additionally the
+        method used to join the domain uses the <constant>net rpc join</constant> process.
+        </para>
+
+        <para>
+        An example &smb.conf; file for an ADS domain environment is shown in <link linkend="sbe-idmapridex"/>.
+        </para>
+
+<example id="sbe-idmapridex">
+<title>Example &smb.conf; File Using <constant>idmap_rid</constant></title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">KPAK</smbconfoption>
+<smbconfoption name="netbios name">BIGJOE</smbconfoption>
+<smbconfoption name="realm">CORP.KPAK.COM</smbconfoption>
+<smbconfoption name="server string">Office Server</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+<smbconfoption name="allow trusted domains">No</smbconfoption>
+<smbconfoption name="idmap backend">idmap_rid:KPAK=500-100000000</smbconfoption>
+<smbconfoption name="idmap uid">500-100000000</smbconfoption>
+<smbconfoption name="idmap gid">500-100000000</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+<smbconfoption name="winbind use default domain">Yes</smbconfoption>
+<smbconfoption name="winbind enum users">No</smbconfoption>
+<smbconfoption name="winbind enum groups">No</smbconfoption>
+<smbconfoption name="winbind nested groups">Yes</smbconfoption>
+<smbconfoption name="printer admin">"KPAK\Domain Admins"</smbconfoption>
+</smbconfblock>
+</example>
+
+        <para>
+        <indexterm><primary>large domain</primary></indexterm>
+        <indexterm><primary>Active Directory</primary></indexterm>
+        <indexterm><primary>response</primary></indexterm>
+        <indexterm><primary>getent</primary></indexterm>
+        In a large domain with many users, it is imperative to disable enumeration of users and groups.
+        For example, at a site that has 22,000 users in Active Directory the winbind-based user and
+        group resolution is unavailable for nearly 12 minutes following first start-up of
+        <command>winbind</command>. Disabling of such enumeration results in instantaneous response.
+        The disabling of user and group enumeration means that it will not be possible to list users
+        or groups using the <command>getent passwd</command> and <command>getent group</command>
+        commands. It will be possible to perform the lookup for individual users, as shown in the procedure
+        below.
+        </para>
+
+        <para>
+        <indexterm><primary>NSS</primary></indexterm>
+        <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+        The use of this tool requires configuration of NSS as per the native use of winbind. Edit the
+        <filename>/etc/nsswitch.conf</filename> so it has the following parameters:
+<screen>
+...
+passwd: files winbind
+shadow: files winbind
+group:  files winbind
+...
+hosts:  files wins
+...
+</screen>
+        </para>
+
+        <para>
+        The following procedure can be used to utilize the idmap_rid facility:
+        </para>
+
+        <procedure>
+                <step><para>
+                Create or install and &smb.conf; file with the above configuration.
+                </para></step>
+
+                <step><para>
+                Edit the <filename>/etc/nsswitch.conf</filename> file as shown above.
+                </para></step>
+
+                <step><para>
+                Execute:
+<screen>
+&rootprompt; net ads join -UAdministrator%password
+Using short domain name -- KPAK
+Joined 'BIGJOE' to realm 'CORP.KPAK.COM'
+</screen>
+                </para>
+
+                <para>
+                <indexterm><primary>failed join</primary></indexterm>
+                An invalid or failed join can be detected by executing:
+<screen>
+&rootprompt; net ads testjoin
+BIGJOE$@'s password:
+[2004/11/05 16:53:03, 0] utils/net_ads.c:ads_startup(186)
+  ads_connect: No results returned
+Join to domain is not valid
+</screen>
+                The specific error message may differ from the above because it depends on the type of failure that
+                may have occurred. Increase the <parameter>log level</parameter> to 10, repeat the above test,
+                and then examine the log files produced to identify the nature of the failure.
+                </para></step>
+
+                <step><para>
+                Start the <command>nmbd</command>, <command>winbind,</command> and <command>smbd</command> daemons in the order shown.
+                </para></step>
+
+                <step><para>
+                Validate the operation of this configuration by executing:
+                <indexterm><primary></primary></indexterm>
+<screen>
+&rootprompt; getent passwd administrator
+administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash
+</screen>
+                </para></step>
+        </procedure>
+
+        </sect3>
+
+        <sect3>
+        <title>IDMAP Storage in LDAP using Winbind</title>
+
+        <para>
+        <indexterm><primary>ADAM</primary></indexterm>
+        <indexterm><primary>ADS</primary></indexterm>
+        The storage of IDMAP information in LDAP can be used with both NT4/Samba-3-style domains as well as
+        with ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any standards-compliant
+        LDAP server can be used. It is therefore possible to deploy this IDMAP configuration using
+        the Sun iPlanet LDAP server, Novell eDirectory, Microsoft ADS plus ADAM, and so on.
+        </para>
+
+        <para>
+        The example in <link linkend="sbeunxa"/> is for an ADS-style domain.
+        </para>
+
+<example id="sbeunxa">
+<title>Typical ADS Style Domain &smb.conf; File</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">SNOWSHOW</smbconfoption>
+<smbconfoption name="netbios name">GOODELF</smbconfoption>
+<smbconfoption name="realm">SNOWSHOW.COM</smbconfoption>
+<smbconfoption name="server string">Samba Server</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+<smbconfoption name="log level">1 ads:10 auth:10 sam:10 rpc:10</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=Manager,dc=SNOWSHOW,dc=COM</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+<smbconfoption name="ldap suffix">dc=SNOWSHOW,dc=COM</smbconfoption>
+<smbconfoption name="idmap backend">ldap:ldap://ldap.snowshow.com</smbconfoption>
+<smbconfoption name="idmap uid">150000-550000</smbconfoption>
+<smbconfoption name="idmap gid">150000-550000</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+<smbconfoption name="winbind use default domain">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+        <para>
+        <indexterm><primary>realm</primary></indexterm>
+        In the case of an NT4 or Samba-3-style domain the <parameter>realm</parameter> is not used, and the
+        command used to join the domain is <command>net rpc join</command>. The above example also demonstrates
+        advanced error reporting techniques that are documented in the chapter called "Reporting Bugs" in
+	<quote>The Official Samba-3 HOWTO and Reference Guide, Second Edition</quote> (TOSHARG2).
+        </para>
+
+        <para>
+        <indexterm><primary>MIT kerberos</primary></indexterm>
+        <indexterm><primary>Heimdal kerberos</primary></indexterm>
+        <indexterm><primary>/etc/krb5.conf</primary></indexterm>
+        Where MIT kerberos is installed (version 1.3.4 or later), edit the <filename>/etc/krb5.conf</filename>
+        file so it has the following contents:
+<screen>
+[logging]
+ default = FILE:/var/log/krb5libs.log
+ kdc = FILE:/var/log/krb5kdc.log
+ admin_server = FILE:/var/log/kadmind.log
+
+[libdefaults]
+ default_realm = SNOWSHOW.COM
+ dns_lookup_realm = false
+ dns_lookup_kdc = true
+
+[appdefaults]
+ pam = {
+   debug = false
+   ticket_lifetime = 36000
+   renew_lifetime = 36000
+   forwardable = true
+   krb4_convert = false
+ }
+</screen>
+        </para>
+
+        <para>
+        Where Heimdal kerberos is installed, edit the <filename>/etc/krb5.conf</filename>
+        file so it is either empty (i.e., no contents) or it has the following contents:
+<screen>
+[libdefaults]
+        default_realm = SNOWSHOW.COM
+        clockskew = 300
+
+[realms]
+        SNOWSHOW.COM = {
+                kdc = ADSDC.SHOWSHOW.COM
+        }
+
+[domain_realm]
+        .snowshow.com = SNOWSHOW.COM
+</screen>
+        </para>
+
+        <note><para>
+        Samba cannot use the Heimdal libraries if there is no <filename>/etc/krb5.conf</filename> file.
+        So long as there is an empty file, the Heimdal kerberos libraries will be usable. There is no
+        need to specify any settings because Samba, using the Heimdal libraries, can figure this out automatically.
+        </para></note>
+        <para>
+        Edit the NSS control file <filename>/etc/nsswitch.conf</filename> so it has the following entries:
+<screen>
+...
+passwd: files ldap
+shadow: files ldap
+group:  files ldap
+...
+hosts:  files wins
+...
+</screen>
+        </para>
+
+        <para>
+        <indexterm><primary>PADL</primary></indexterm>
+        <indexterm><primary>/etc/ldap.conf</primary></indexterm>
+        You will need the <ulink url="http://www.padl.com">PADL</ulink> <command>nss_ldap</command>
+        tool set for this solution. Configure the <filename>/etc/ldap.conf</filename> file so it has
+        the information needed. The following is an example of a working file:
+<screen>
+host    192.168.2.1
+base    dc=snowshow,dc=com
+binddn  cn=Manager,dc=snowshow,dc=com
+bindpw  not24get
+
+pam_password exop
+
+nss_base_passwd ou=People,dc=snowshow,dc=com?one
+nss_base_shadow ou=People,dc=snowshow,dc=com?one
+nss_base_group  ou=Groups,dc=snowshow,dc=com?one
+ssl     no
+</screen>
+        </para>
+
+        <para>
+        The following procedure may be followed to affect a working configuration:
+        </para>
+        <procedure>
+                <step><para>
+                Configure the &smb.conf; file as shown above.
+                </para></step>
+
+                <step><para>
+                Create the <filename>/etc/krb5.conf</filename> file following the indications above.
+                </para></step>
+
+                <step><para>
+                Configure the <filename>/etc/nsswitch.conf</filename> file as shown above.
+                </para></step>
+
+                <step><para>
+                Download, build, and install the PADL nss_ldap tool set. Configure the
+                <filename>/etc/ldap.conf</filename> file as shown above.
+                </para></step>
+
+                <step><para>
+                Configure an LDAP server and initialize the directory with the top-level entries needed by IDMAP
+                as shown in the following LDIF file:
+<screen>
+dn: dc=snowshow,dc=com
+objectClass: dcObject
+objectClass: organization
+dc: snowshow
+o: The Greatest Snow Show in Singapore.
+description: Posix and Samba LDAP Identity Database
+
+dn: cn=Manager,dc=snowshow,dc=com
+objectClass: organizationalRole
+cn: Manager
+description: Directory Manager
+
+dn: ou=Idmap,dc=snowshow,dc=com
+objectClass: organizationalUnit
+ou: idmap
+</screen>
+                </para></step>
+
+                <step><para>
+                Execute the command to join the Samba domain member server to the ADS domain as shown here:
+<screen>
+&rootprompt; net ads testjoin
+Using short domain name -- SNOWSHOW
+Joined 'GOODELF' to realm 'SNOWSHOW.COM'
+</screen>
+                </para></step>
+
+                <step><para>
+                Store the LDAP server access password in the Samba <filename>secrets.tdb</filename> file as follows:
+<screen>
+&rootprompt; smbpasswd -w not24get
+</screen>
+                </para></step>
+
+                <step><para>
+                Start the <command>nmbd</command>, <command>winbind</command>, and <command>smbd</command> daemons in the order shown.
+                </para></step>
+        </procedure>
+
+
+        <para>
+        <indexterm><primary>diagnostic</primary></indexterm>
+        Follow the diagnostic procedures shown earlier in this chapter to identify success or failure of the join.
+        In many cases a failure is indicated by a silent return to the command prompt with no indication of the
+        reason for failure.
+        </para>
+
+        </sect3>
+
+        <sect3>
+        <title>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</title>
+
+        <para>
+        <indexterm><primary>rfc2307bis</primary></indexterm>
+        <indexterm><primary>schema</primary></indexterm>
+        The use of this method is messy. The information provided in this section is for guidance only
+        and is very definitely not complete. This method does work; it is used in a number of large sites
+        and has an acceptable level of performance.
+        </para>
+
+        <para>
+        An example &smb.conf; file is shown in <link linkend="sbewinbindex"/>.
+        </para>
+
+<example id="sbewinbindex">
+<title>ADS Membership Using RFC2307bis Identity Resolution &smb.conf; File</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">BUBBAH</smbconfoption>
+<smbconfoption name="netbios name">MADMAX</smbconfoption>
+<smbconfoption name="realm">BUBBAH.COM</smbconfoption>
+<smbconfoption name="server string">Samba Server</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+<smbconfoption name="idmap uid">150000-550000</smbconfoption>
+<smbconfoption name="idmap gid">150000-550000</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+<smbconfoption name="winbind use default domain">Yes</smbconfoption>
+<smbconfoption name="winbind trusted domains only">Yes</smbconfoption>
+<smbconfoption name="winbind nested groups">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+        <para>
+        <indexterm><primary>nss_ldap</primary></indexterm>
+        The DMS must be joined to the domain using the usual procedure. Additionally, it is necessary
+        to build and install the PADL nss_ldap tool set. Be sure to build this tool set with the
+        following:
+<screen>
+./configure --enable-rfc2307bis --enable-schema-mapping
+make install
+</screen>
+        </para>
+
+        <para>
+        <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+        The following <filename>/etc/nsswitch.conf</filename> file contents are required:
+<screen>
+...
+passwd: files ldap
+shadow: files ldap
+group:  files ldap
+...
+hosts:  files wins
+...
+</screen>
+        </para>
+
+        <para>
+        <indexterm><primary>/etc/ldap.conf</primary></indexterm>
+        <indexterm><primary>nss_ldap</primary></indexterm>
+        The <filename>/etc/ldap.conf</filename> file must be configured also. Refer to the PADL documentation
+        and source code for nss_ldap instructions.
+        </para>
+
+        <para>
+        The next step involves preparation on the ADS schema. This is briefly discussed in the remaining
+        part of this chapter.
+        </para>
+
+                <sect4>
+                <title>IDMAP, Active Directory, and MS Services for UNIX 3.5</title>
+
+                <para>
+                <indexterm><primary>SFU</primary></indexterm>
+                The Microsoft Windows Service for UNIX version 3.5 is available for free
+                <ulink url="http://www.microsoft.com/windows/sfu/">download</ulink>
+                from the Microsoft Web site. You will need to download this tool and install it following
+                Microsoft instructions.
+                </para>
+
+                </sect4>
+
+                <sect4>
+                <title>IDMAP, Active Directory, and AD4UNIX</title>
+
+                <para>
+                Instructions for obtaining and installing the AD4UNIX tool set can be found from the
+                <ulink url="http://www.geekcomix.com/cgi-bin/classnotes/wiki.pl?LDAP01/An_Alternative_Approach">
+                Geekcomix</ulink> Web site.
+                </para>
+
+                </sect4>
+
+        </sect3>
+
+        </sect2>
+
+
+	<sect2>
+	<title>UNIX/Linux Client Domain Member</title>
+
+	<para><indexterm>
+	    <primary>user credentials</primary>
+	  </indexterm>
+	So far this chapter has been mainly concerned with the provision of file and print
+	services for domain member servers. However, an increasing number of UNIX/Linux
+	workstations are being installed that do not act as file or print servers to anyone
+	other than a single desktop user. The key demand for desktop systems is to be able
+	to log onto any UNIX/Linux or Windows desktop using the same network user credentials.
+	</para>
+
+	<para><indexterm>
+	    <primary>Single Sign-On</primary>
+	    <see>SSO</see>
+	  </indexterm>
+	The ability to use a common set of user credential across a variety of network systems
+	is generally regarded as a single sign-on (SSO) solution. SSO systems are sold by a
+	large number of vendors and include a range of technologies such as:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Proxy sign-on
+		</para></listitem>
+
+		<listitem><para>
+		Federated directory provisioning
+		</para></listitem>
+
+		<listitem><para>
+		Metadirectory server solutions
+		</para></listitem>
+
+		<listitem><para>
+		Replacement authentication systems
+		</para></listitem>
+	</itemizedlist>
+
+	<para><indexterm>
+	    <primary>Identity management</primary>
+	  </indexterm>
+	There are really four solutions that provide integrated authentication and
+	user identity management facilities:
+	</para>
+
+	<itemizedlist>
+                <listitem><para>
+		Samba winbind (free). Samba-3.0.20 introduced a complete replacement for Winbind that now
+		provides a greater level of scalability in large ADS environments.
+                </para></listitem>
+
+                <listitem><para>
+		<ulink url="http://www.padl.com">PADL</ulink> PAM and LDAP tools (free).
+                </para></listitem>
+
+                <listitem><para>
+		<ulink url="http://www.vintela.com">Vintela</ulink> Authentication Services (commercial).
+                </para></listitem>
+
+                <listitem><para>
+		<ulink url="http://www.centrify.com">Centrify</ulink> DirectControl (commercial). 
+		Centrify's commercial product allows UNIX and Linux systems to use Active Directory
+		security, directory and policy services.  Enhancements include a centralized ID mapping that 
+		allows Samba, DirectControl and Active Directory to seamlessly work together.
+                </para></listitem>
+        </itemizedlist>
+
+	<para>
+	The following guidelines are pertinent to the deployment of winbind-based authentication
+	and identity resolution with the express purpose of allowing users to log on to UNIX/Linux desktops
+	using Windows network domain user credentials (username and password).
+	</para>
+
+	<para>
+	You should note that it is possible to use LDAP-based PAM and NSS tools to permit distributed
+	systems logons (SSO), providing user and group accounts are stored in an LDAP directory. This
+	provides logon services for UNIX/Linux users, while Windows users obtain their sign-on
+	support via Samba-3.
+	</para>
+
+	<para>
+	<indexterm><primary>Windows Services for UNIX</primary><see>SUS</see></indexterm>
+	On the other hand, if the authentication and identity resolution backend must be provided by
+	a Windows NT4-style domain or from an Active Directory Domain that does not have the Microsoft
+	Windows Services for UNIX installed, winbind is your best friend. Specific guidance for these
+	situations now follows.
+	</para>
+
+	<para>
+	<indexterm><primary>PAM</primary></indexterm>
+	<indexterm><primary>Identity resolution</primary></indexterm>
+	<indexterm><primary>NSS</primary></indexterm>
+	To permit users to log on to a Linux system using Windows network credentials, you need to
+	configure identity resolution (NSS) and PAM. This means that the basic steps include those
+	outlined above with the addition of PAM configuration. Given that most workstations (desktop/client)
+	usually do not need to provide file and print services to a group of users, the configuration
+	of shares and printers is generally less important. Often this allows the share specifications
+	to be entirely removed from the &smb.conf; file. That is obviously an administrator decision.
+	</para>
+
+		<sect3>
+		<title>NT4 Domain Member</title>
+
+		<para>
+		The following steps provide a Linux system that users can log onto using
+		Windows NT4 (or Samba-3) domain network credentials:
+		</para>
+
+		<procedure>
+			<step><para>
+			Follow the steps outlined in <link linkend="wdcsdm"/> and ensure that
+			all validation tests function as shown.
+			</para></step>
+
+			<step><para>
+			Identify what services users must log on to. On Red Hat Linux, if it is
+			intended that the user shall be given access to all services, it may be
+			most expeditious to simply configure the file 
+			<filename>/etc/pam.d/system-auth</filename>.
+			</para></step>
+
+			<step><para>
+			Carefully make a backup copy of all PAM configuration files before you
+			begin making changes. If you break the PAM configuration, please note
+			that you may need to use an emergency boot process to recover your Linux
+			system. It is possible to break the ability to log into the system if
+			PAM files are incorrectly configured. The entire directory 
+			<filename>/etc/pam.d</filename> should be backed up to a safe location.
+			</para></step>
+
+			<step><para>
+			If you require only console login support, edit the <filename>/etc/pam.d/login</filename>
+			so it matches <link linkend="ch9-pamwnbdlogin"/>.
+			</para></step>
+
+			<step><para>
+			To provide the ability to log onto the graphical desktop interface, you must edit
+			the files <filename>gdm</filename> and <filename>xdm</filename> in the 
+			<filename>/etc/pam.d</filename> directory.
+			</para></step>
+
+			<step><para>
+			Edit only one file at a time. Carefully validate its operation before attempting
+			to reboot the machine.
+			</para></step>
+		</procedure>
+
+		</sect3>
+
+		<sect3>
+		<title>ADS Domain Member</title>
+
+		<para>
+		This procedure should be followed to permit a Linux network client (workstation/desktop)
+		to permit users to log on using Microsoft Active Directory-based user credentials.
+		</para>
+
+		<procedure>
+			<step><para>
+			Follow the steps outlined in <link linkend="adssdm"/> and ensure that
+			all validation tests function as shown.
+			</para></step>
+
+			<step><para>
+			Identify what services users must log on to. On Red Hat Linux, if it is
+			intended that the user shall be given access to all services, it may be
+			most expeditious to simply configure the file 
+			<filename>/etc/pam.d/system-auth</filename> as shown in <link linkend="ch9-rhsysauth"/>.
+			</para></step>
+
+			<step><para>
+			Carefully make a backup copy of all PAM configuration files before you
+			begin making changes. If you break the PAM configuration, please note
+			that you may need to use an emergency boot process to recover your Linux
+			system. It is possible to break the ability to log into the system if
+			PAM files are incorrectly configured. The entire directory 
+			<filename>/etc/pam.d</filename> should be backed up to a safe location.
+			</para></step>
+
+			<step><para>
+			If you require only console login support, edit the <filename>/etc/pam.d/login</filename>
+			so it matches <link linkend="ch9-pamwnbdlogin"/>.
+			</para></step>
+
+			<step><para>
+			To provide the ability to log onto the graphical desktop interface, you must edit
+			the files <filename>gdm</filename> and <filename>xdm</filename> in the 
+			<filename>/etc/pam.d</filename> directory.
+			</para></step>
+
+			<step><para>
+			Edit only one file at a time. Carefully validate its operation before attempting
+			to reboot the machine.
+			</para></step>
+		</procedure>
+
+		</sect3>
+
+<example id="ch9-pamwnbdlogin">
+<title>SUSE: PAM <filename>login</filename> Module Using Winbind</title>
+<screen>
+# /etc/pam.d/login
+
+#%PAM-1.0
+auth sufficient pam_unix2.so    nullok
+auth sufficient pam_winbind.so use_first_pass use_authtok
+auth required   pam_securetty.so
+auth required   pam_nologin.so
+auth required   pam_env.so
+auth required   pam_mail.so
+account sufficient      pam_unix2.so
+account sufficient      pam_winbind.so user_first_pass use_authtok
+password required       pam_pwcheck.so  nullok
+password sufficient     pam_unix2.so    nullok use_first_pass use_authtok
+password sufficient     pam_winbind.so  use_first_pass use_authtok
+session sufficient      pam_unix2.so    none
+session sufficient      pam_winbind.so  use_first_pass use_authtok
+session required        pam_limits.so
+</screen>
+</example>
+
+<example id="ch9-pamwbndxdm">
+<title>SUSE: PAM <filename>xdm</filename> Module Using Winbind</title>
+<screen>
+# /etc/pam.d/gdm (/etc/pam.d/xdm)
+
+#%PAM-1.0
+auth     sufficient     pam_unix2.so     nullok
+auth     sufficient     pam_winbind.so   use_first_pass use_authtok
+account  sufficient     pam_unix2.so
+account  sufficient     pam_winbind.so   use_first_pass use_authtok
+password sufficient     pam_unix2.so
+password sufficient     pam_winbind.so   use_first_pass use_authtok
+session  sufficient     pam_unix2.so
+session  sufficient     pam_winbind.so   use_first_pass use_authtok
+session  required       pam_dev perm.so
+session  required       pam_resmgr.so
+</screen>
+</example>
+
+<example id="ch9-rhsysauth">
+<title>Red Hat 9: PAM System Authentication File: <filename>/etc/pam.d/system-auth</filename> Module Using Winbind</title>
+<screen>
+#%PAM-1.0
+auth        required      /lib/security/$ISA/pam_env.so
+auth        sufficient    /lib/security/$ISA/pam_unix.so likeauth nullok
+auth        sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
+auth        required      /lib/security/$ISA/pam_deny.so
+
+account     required      /lib/security/$ISA/pam_unix.so
+account     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
+
+password    required      /lib/security/$ISA/pam_cracklib.so retry=3 type=
+# Note: The above line is complete. There is nothing following the '='
+password    sufficient    /lib/security/$ISA/pam_unix.so \
+                                             nullok use_authtok md5 shadow
+password    sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
+password    required      /lib/security/$ISA/pam_deny.so
+
+session     required      /lib/security/$ISA/pam_limits.so
+session     sufficient    /lib/security/$ISA/pam_unix.so
+session     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
+</screen>
+</example>
+
+	</sect2>
+
+	<sect2>
+		<title>Key Points Learned</title>
+
+		<para>
+		The addition of UNIX/Linux Samba servers and clients is a common requirement. In this chapter, you
+		learned how to integrate such servers so that the UID/GID mappings they use can be consistent
+		across all domain member servers. You also discovered how to implement the ability to use Samba
+		or Windows domain account credentials to log on to a UNIX/Linux client.
+		</para>
+
+		<para>
+		The following are key points made in this chapter:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			Domain controllers are always authoritative for the domain.
+			</para></listitem>
+
+			<listitem><para>
+			Domain members may have local accounts and must be able to resolve the identity of 
+			domain user accounts. Domain user account identity must map to a local UID/GID. That 
+			local UID/GID can be stored in LDAP. This way, it is possible to share the IDMAP data 
+			across all domain member machines.
+			</para></listitem>
+
+			<listitem><para>
+			Resolution of user and group identities on domain member machines may be implemented 
+			using direct LDAP services or using winbind.
+			</para></listitem>
+
+			<listitem><para>
+			On NSS/PAM enabled UNIX/Linux systems, NSS is responsible for identity management 
+			and PAM is responsible for authentication of logon credentials (username and password).
+			</para></listitem>
+		</itemizedlist>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	The following questions were obtained from the mailing list and also from private discussions
+	with Windows network administrators.
+	</para>
+
+	<qandaset defaultlabel="chap09qa" type="number">
+	<qandaentry>
+	<question>
+
+		<para>
+		We use NIS for all UNIX accounts. Why do we need winbind?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para>
+		<indexterm><primary>NIS</primary></indexterm>
+		<indexterm><primary>encrypted passwords</primary></indexterm>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		<indexterm><primary>tdbsam</primary></indexterm>
+		<indexterm><primary>passdb backend</primary></indexterm>
+		<indexterm><primary>Winbind</primary></indexterm>
+		You can use NIS for your UNIX accounts. NIS does not store the Windows encrypted
+		passwords that need to be stored in one of the acceptable passdb backends.
+		Your choice of backend is limited to <parameter>smbpasswd</parameter> or
+		<parameter>tdbsam</parameter>. Winbind is needed to handle the resolution of
+		SIDs from trusted domains to local UID/GID values.
+		</para>
+
+	    <para>
+		<indexterm><primary>winbind trusted domains only</primary></indexterm>
+		<indexterm><primary>getpwnam()</primary></indexterm>
+		On a domain member server, you effectively map Windows domain users to local users
+		that are in your NIS database by specifying the <parameter>winbind trusted domains
+		only</parameter>. This causes user and group account lookups to be routed via
+		the <command>getpwnam()</command> family of systems calls. On an NIS-enabled client,
+		this pushes the resolution of users and groups out through NIS.
+		</para>
+
+		<para>
+		As a general rule, it is always a good idea to run winbind on all Samba servers.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Our IT management people do not like LDAP but are looking at Microsoft Active Directory. 
+	      Which is better?<indexterm>
+		<primary>Active Directory</primary>
+	      </indexterm>
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>LDAP</primary>
+		<secondary>server</secondary>
+	      </indexterm><indexterm>
+		<primary>Kerberos</primary>
+	      </indexterm><indexterm>
+		<primary>schema</primary>
+	      </indexterm>
+		Microsoft Active Directory is an LDAP server that is intricately tied to a Kerberos
+		infrastructure. Most IT managers who object to LDAP do so because
+		an LDAP server is most often supplied as a raw tool that needs to be configured and
+		for which the administrator must create the schema, create the administration tools, and
+		devise the backup and recovery facilities in a site-dependent manner. LDAP servers
+		in general are seen as a high-energy, high-risk facility.
+		</para>
+
+	    <para><indexterm>
+		<primary>management</primary>
+	      </indexterm>
+		Microsoft Active Directory by comparison is easy to install and configure and
+		is supplied with all tools necessary to implement and manage the directory. For sites
+		that lack a lot of technical competence, Active Directory is a good choice. For sites
+		that have the technical competence to handle Active Directory well, LDAP is a good
+		alternative. The real issue is, What type of solution does
+		the site want? If management wants a choice to use an alternative, they may want to
+		consider the options. On the other hand, if management just wants a solution that works,
+		Microsoft Active Directory is a good solution.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		We want to implement a Samba PDC, four Samba BDCs, and 10 Samba servers. Is it possible 
+		to use NIS in place of LDAP?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>NIS</primary>
+	      </indexterm><indexterm>
+		<primary>LDAP</primary>
+	      </indexterm><indexterm>
+		<primary>encrypted passwords</primary>
+	      </indexterm><indexterm>
+		<primary>synchronized</primary>
+	      </indexterm><indexterm>
+		<primary>secure account password</primary>
+	      </indexterm><indexterm>
+		<primary>PDC</primary>
+	      </indexterm><indexterm>
+		<primary>BDC</primary>
+	      </indexterm>
+		Yes, it is possible to use NIS in place of LDAP, but there may be problems with keeping
+		the Windows (SMB) encrypted passwords database correctly synchronized across the entire
+		network. Workstations (Windows client machines) periodically change their domain
+		membership secure account password. How can you keep changes that are on remote BDCs
+		synchronized on the PDC?
+		</para>
+
+	    <para><indexterm>
+		<primary>centralized storage</primary>
+	      </indexterm><indexterm>
+		<primary>management</primary>
+	      </indexterm><indexterm>
+		<primary>network Identities</primary>
+	      </indexterm>
+		LDAP is a more elegant solution because it permits centralized storage and management
+		of all network identities (user, group, and machine accounts) together with all information
+		Samba needs to provide to network clients and their users.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Are you suggesting that users should not log on to a domain member server? If so, why?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>security</primary>
+	      </indexterm><indexterm>
+		<primary>data</primary>
+		<secondary>integrity</secondary>
+	      </indexterm><indexterm>
+		<primary>mapped drives</primary>
+	      </indexterm>
+		Many UNIX administrators mock the model that the personal computer industry has adopted
+		as normative since the early days of Novell NetWare. The old
+		perception of the necessity to keep users off file and print servers was a result of
+		fears concerning the security and integrity of data. It was a simple and generally
+		effective measure to keep users away from servers, except through mapped drives.
+		</para>
+
+	    <para><indexterm>
+		<primary>user logins</primary>
+	      </indexterm><indexterm>
+		<primary>risk</primary>
+	      </indexterm><indexterm>
+		<primary>user errors</primary>
+	      </indexterm><indexterm>
+		<primary>strategy</primary>
+	      </indexterm><indexterm>
+		<primary>policy</primary>
+	      </indexterm>
+		UNIX administrators are fully correct in asserting that UNIX servers and workstations
+		are identical in terms of the software that is installed. They correctly assert that
+		in a well-secured environment it is safe to store files on a system that has hundreds
+		of users. But all network administrators must factor into the decision to allow or
+		reject general user logins to a UNIX system that is principally a file and print
+		server the risk to operations through simple user errors.
+		Only then can one begin to appraise the best strategy and adopt a site-specific
+		policy that best protects the needs of users and of the organization alike.
+		</para>
+
+	    <para><indexterm>
+		<primary>system level logins</primary>
+	      </indexterm>
+		From experience, it is my recommendation to keep general system-level logins to a
+		practical minimum and to eliminate them if possible. This should not be taken as a
+		hard rule, though. The better question is, what works best for the site?
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>trusted domains</primary>
+	      </indexterm><indexterm>
+		<primary>domain</primary>
+		<secondary>trusted</secondary>
+	      </indexterm><indexterm>
+		<primary>winbind trusted domains only</primary>
+	      </indexterm><indexterm>
+		<primary>domain members</primary>
+	      </indexterm>
+		We want to ensure that only users from our own domain plus from trusted domains can use our
+		Samba servers. In the &smb.conf; file on all servers, we have enabled the <parameter>winbind
+		trusted domains only</parameter> parameter. We now find that users from trusted domains 
+		cannot access our servers, and users from Windows clients that are not domain members
+		can also access our servers. Is this a Samba bug?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>distributed</primary>
+	      </indexterm><indexterm>
+		<primary>NIS</primary>
+	      </indexterm><indexterm>
+		<primary>rsync</primary>
+	      </indexterm><indexterm>
+		<primary>LDAP</primary>
+	      </indexterm><indexterm>
+		<primary>winbindd</primary>
+	      </indexterm><indexterm>
+		<primary>/etc/passwd</primary>
+	      </indexterm>
+		The manual page for this <parameter>winbind trusted domains only</parameter> parameter says,
+		<quote>This parameter is designed to allow Samba servers that are members of a Samba-controlled 
+		domain to use UNIX accounts distributed vi NIS, rsync, or LDAP as the UIDs for winbindd users 
+		in the hosts primary domain. Therefore,  the user <constant>SAMBA\user1</constant> would be 
+		mapped to the account <constant>user1</constant> in <filename>/etc/passwd</filename> instead 
+		of allocating a new UID for him or her.</quote> This clearly suggests that you are trying
+		to use this parameter inappropriately.
+		</para>
+
+	    <para><indexterm>
+		<primary>valid users</primary>
+	      </indexterm>
+		A far better solution is to use the <parameter>valid users</parameter> by specifying
+		precisely the domain users and groups that should be permitted access to the shares. You could, 
+		for example, set the following parameters:
+<screen>
+[demoshare]
+	path = /export/demodata
+	valid users = @"Domain Users", @"OTHERDOMAIN\Domain Users"
+</screen>
+		</para>
+
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What are the benefits of using LDAP for my domain member servers?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>LDAP</primary>
+	      </indexterm><indexterm>
+		<primary>benefit</primary>
+	      </indexterm><indexterm>
+		<primary>UID</primary>
+	      </indexterm><indexterm>
+		<primary>GID</primary>
+	      </indexterm><indexterm>
+		<primary>Domain Controllers</primary>
+	      </indexterm><indexterm>
+		<primary>Domain Member servers</primary>
+	      </indexterm><indexterm>
+		<primary>copy</primary>
+	      </indexterm><indexterm>
+		<primary>replicate</primary>
+	      </indexterm><indexterm>
+		<primary>identity</primary>
+	      </indexterm>
+		The key benefit of using LDAP is that the UID of all users and the GID of all groups
+		are globally consistent on domain controllers as well as on domain member servers.
+		This means that it is possible to copy/replicate files across servers without
+		loss of identity.
+		</para>
+
+	    <para><indexterm>
+		<primary>Identity resolution</primary>
+	      </indexterm><indexterm>
+		<primary>winbind</primary>
+	      </indexterm><indexterm>
+		<primary>IDMAP backend</primary>
+	      </indexterm><indexterm>
+		<primary>LDAP</primary>
+	      </indexterm><indexterm>
+		<primary>Domain Controllers</primary>
+	      </indexterm><indexterm>
+		<primary>Domain Member</primary>
+		<secondary>servers</secondary>
+	      </indexterm><indexterm>
+		<primary>Posix</primary>
+	      </indexterm><indexterm>
+		<primary>account information</primary>
+	      </indexterm>
+		When use is made of account identity resolution via winbind, even when an IDMAP backend
+		is stored in LDAP, the UID/GID on domain member servers is consistent, but differs
+		from the ID that the user/group has on domain controllers. The winbind allocated UID/GID
+		that is stored in LDAP (or locally) will be in the numeric range specified in the <parameter>
+		idmap uid/gid</parameter> in the &smb.conf; file. On domain controllers, the UID/GID is
+		that of the POSIX value assigned in the LDAP directory as part of the POSIX account information.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Is proper DNS operation necessary for Samba-3 plus LDAP? If so, what must I put into
+		my DNS configuration?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>DNS</primary>
+		<secondary>configuration</secondary>
+	      </indexterm><indexterm>
+		<primary>DNS</primary>
+		<secondary>lookup</secondary>
+	      </indexterm><indexterm>
+		<primary>hosts</primary>
+	      </indexterm><indexterm>
+		<primary>/etc/nsswitch.conf</primary>
+	      </indexterm><indexterm>
+		<primary>NSS</primary>
+	      </indexterm><indexterm>
+		<primary>/etc/hosts</primary>
+	      </indexterm><indexterm>
+		<primary>WINS</primary>
+		<secondary>lookup</secondary>
+	      </indexterm>
+		Samba depends on correctly functioning resolution of hostnames to their IP address. Samba
+		makes no direct DNS lookup calls, but rather redirects all name-to-address calls via the
+		<command>getXXXbyXXX()</command> function calls. The configuration of the <constant>hosts</constant>
+		entry in the NSS <filename>/etc/nsswitch.conf</filename> file determines how the underlying
+		resolution process is implemented. If the <constant>hosts</constant> entry in your NSS
+		control file says:
+<screen>
+hosts: files dns wins
+</screen>
+		this means that a hostname lookup first tries the <filename>/etc/hosts</filename>.
+		If this fails to resolve, it attempts a DNS lookup, and if that fails, it tries a
+		WINS lookup.
+		</para>
+
+	    <para><indexterm>
+		<primary>NetBIOS</primary>
+	      </indexterm><indexterm>
+		<primary>TCP/IP</primary>
+	      </indexterm><indexterm>
+		<primary>name resolution</primary>
+	      </indexterm>
+		The addition of the WINS-based name lookup makes sense only if NetBIOS over TCP/IP has
+		been enabled on all Windows clients. Where NetBIOS over TCP/IP has been disabled, DNS
+		is the preferred name resolution technology. This usually makes most sense when Samba
+		is a client of an Active Directory domain, where NetBIOS use has been disabled. In this
+		case, the Windows 200x autoregisters all locator records it needs with its own DNS
+		server or servers.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Our Windows 2003 Server Active Directory domain runs with NetBIOS disabled. Can we
+		use Samba-3 with that configuration?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Yes.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>net</primary>
+		<secondary>ads</secondary>
+		<tertiary>join</tertiary>
+	      </indexterm><indexterm>
+		<primary>net</primary>
+		<secondary>rpc</secondary>
+		<tertiary>join</tertiary>
+	      </indexterm>
+		When I tried to execute net ads join, I got no output. It did not work, so
+		I think that it failed. I then executed net rpc join and that worked fine.
+		That is okay, isn't it?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>Kerberos</primary>
+	      </indexterm><indexterm>
+		<primary>authentication</primary>
+	      </indexterm>
+		No. This is not okay. It means that your Samba-3 client has joined the ADS domain as
+		a Windows NT4 client, and Samba-3 will not be using Kerberos-based authentication.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	</qandaset>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-ByExample/SBE-Appendix1.xml b/docs-xml/Samba3-ByExample/SBE-Appendix1.xml
new file mode 100644
index 00000000000..b78e16a4bd4
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-Appendix1.xml
@@ -0,0 +1,1622 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE appendix PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<chapter id="appendix">
+  <title>A Collection of Useful Tidbits</title>
+
+	<para>
+	<indexterm><primary>material</primary></indexterm>
+	<indexterm><primary>domain</primary><secondary>joining</secondary></indexterm>
+	Information presented here is considered to be either basic or well-known material that is informative
+	yet helpful. Over the years, I have observed an interesting behavior. There is an expectation that
+	the process for joining a Windows client to a Samba-controlled Windows domain may somehow involve steps
+	different from doing so with Windows NT4 or a Windows ADS domain. Be assured that the steps are identical,
+	as shown in the example given below.
+	</para>
+
+<sect1 id="domjoin">
+<title>Joining a Domain: Windows 200x/XP Professional</title>
+
+	<para>
+	<indexterm><primary>joining a domain</primary></indexterm>
+	Microsoft Windows NT/200x/XP Professional platforms can participate in Domain Security.
+	This section steps through the process for making a Windows 200x/XP Professional machine a
+	member of a Domain Security environment. It should be noted that this process is identical
+	when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
+	</para>
+
+	<procedure>
+	<title>Steps to Join a Domain</title>
+
+		<step><para>
+		Click <guimenu>Start</guimenu>.
+		</para></step>
+
+		<step><para>
+		Right-click <guimenu>My Computer</guimenu>, and then select <guimenuitem>Properties</guimenuitem>.
+		</para></step>
+
+		<step><para>
+		The opening panel is the same one that can be reached by clicking <guimenu>System</guimenu> on the Control Panel.
+		See <link linkend="swxpp001"></link>.
+		<figure id="swxpp001"><imagefile>wxpp001</imagefile><title>The General Panel.</title></figure>
+		</para></step>
+
+		<step><para>
+		Click the <guimenu>Computer Name</guimenu> tab.
+		This panel shows the <guimenuitem>Computer Description</guimenuitem>, the <guimenuitem>Full computer name</guimenuitem>,
+		and the <guimenuitem>Workgroup</guimenuitem> or <guimenuitem>Domain name</guimenuitem>.
+		</para>
+
+		<para>
+		Clicking the <guimenu>Network ID</guimenu> button launches the configuration wizard. Do not use this with
+		Samba-3. If you wish to change the computer name, or join or leave the domain, click the <guimenu>Change</guimenu> button.
+		See <link linkend="swxpp004"></link>.
+		<figure id="swxpp004"><imagefile>wxpp004</imagefile><title>The Computer Name Panel.</title></figure>
+		</para></step>
+
+		<step><para>
+		Click on <guimenu>Change</guimenu>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP.
+		We join the domain called MIDEARTH. See <link linkend="swxpp006"></link>.
+		<figure id="swxpp006"><imagefile>wxpp006</imagefile><title>The Computer Name Changes Panel</title></figure>
+		</para></step>
+
+		<step><para>
+		Enter the name <guimenu>MIDEARTH</guimenu> in the field below the Domain radio button.
+		</para>
+
+		<para>
+		This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <link linkend="swxpp007"></link>.
+		<figure id="swxpp007"><imagefile>wxpp007</imagefile><title>The Computer Name Changes Panel &smbmdash; Domain MIDEARTH</title></figure>
+		</para></step>
+
+		<step><para>
+		Now click the <guimenu>OK</guimenu> button. A dialog box should appear to allow you to provide the credentials (username and password)
+		of a domain administrative account that has the rights to add machines to the domain.
+		</para>
+
+		<para>
+		Enter the name <quote>root</quote> and the root password from your Samba-3 server. See <link linkend="swxpp008"></link>.
+		<figure id="swxpp008"><imagefile>wxpp008</imagefile><title>Computer Name Changes &smbmdash; User name and Password Panel</title></figure>
+		</para></step>
+
+		<step><para>
+		Click <guimenu>OK</guimenu>.
+		</para>
+
+		<para>
+		The <quote>Welcome to the MIDEARTH domain</quote> dialog box should appear. At this point, the machine must be rebooted.
+		Joining the domain is now complete.
+		</para></step>
+
+	</procedure>
+
+	<para>
+	<indexterm><primary>Active Directory</primary></indexterm>
+	<indexterm><primary>DNS</primary></indexterm>
+	The screen capture shown in <link linkend="swxpp007"/> has a button labeled <guimenu>More...</guimenu>. This button opens a
+	panel in which you can set (or change) the Primary DNS suffix of the computer. This is a parameter that mainly affects members
+	of Microsoft Active Directory. Active Directory is heavily oriented around the DNS namespace.
+	</para>
+
+	<para>
+	<indexterm><primary>Netlogon</primary></indexterm>
+	<indexterm><primary>DNS</primary><secondary>dynamic</secondary></indexterm>
+	Where NetBIOS technology uses WINS as well as UDP broadcast as key mechanisms for name resolution, Active Directory servers
+	register their services with the Microsoft Dynamic DNS server. Windows clients must be able to query the correct DNS server
+	to find the services (like which machines are domain controllers or which machines have the Netlogon service running).
+	</para>
+
+	<para>
+	<indexterm><primary>DNS</primary><secondary>suffix</secondary></indexterm>
+	The default setting of the Primary DNS suffix is the Active Directory domain name. When you change the Primary DNS suffix,
+	this does not affect domain membership, but it can break network browsing and the ability to resolve your computer name to
+	a valid IP address.
+	</para>
+
+	<para>
+	The Primary DNS suffix parameter principally affects MS Windows clients that are members of an Active Directory domain.
+	Where the client is a member of a Samba domain, it is preferable to leave this field blank.
+	</para>
+
+	<para>
+	<indexterm><primary>Group Policy</primary></indexterm>
+	According to Microsoft documentation, <quote>If this computer belongs to a group with <constant>Group Policy</constant>
+	enabled on <command>Primary DNS suffice of this computer</command>, the string specified in the Group Policy is used
+	as the primary DNS suffix and you might need to restart your computer to view the correct setting. The local setting is
+	used only if Group Policy is disabled or unspecified.</quote>
+	</para>
+
+</sect1>
+
+<sect1>
+	<title>Samba System File Location</title>
+
+      <para><indexterm>
+	  <primary>default installation</primary>
+	</indexterm><indexterm>
+	  <primary>/usr/local/samba</primary>
+	</indexterm><indexterm>
+	  <primary>/usr/local</primary>
+	</indexterm>
+	One of the frustrations expressed by subscribers to the Samba mailing lists revolves around the choice of where the default Samba Team
+	build and installation process locates its Samba files. The location, chosen in the early 1990s, for the default installation is
+	in the <filename>/usr/local/samba</filename> directory. This is a perfectly reasonable location, particularly given all the other
+	Open Source software that installs into the <filename>/usr/local</filename> subdirectories.
+	</para>
+
+	<para>
+	Several UNIX vendors, and Linux vendors in particular, elected to locate the Samba files in a location other than the Samba Team
+	default. 
+	</para>
+
+      <para><indexterm>
+	  <primary>Free Standards Group</primary>
+	  <see>FSG</see>
+	</indexterm><indexterm>
+	  <primary>FSG</primary>
+	</indexterm><indexterm>
+	  <primary>Linux Standards Base</primary>
+	  <see>LSB</see>
+	</indexterm><indexterm>
+	  <primary>LSB</primary>
+	</indexterm><indexterm>
+	  <primary>File Hierarchy System</primary>
+	  <see>FHS</see>
+	</indexterm><indexterm>
+	  <primary>FHS</primary>
+	</indexterm><indexterm>
+	  <primary>file locations</primary>
+	</indexterm><indexterm>
+	  <primary>/etc/samba</primary>
+	</indexterm><indexterm>
+	  <primary>/usr/sbin</primary>
+	</indexterm><indexterm>
+	  <primary>/usr/bin</primary>
+	</indexterm><indexterm>
+	  <primary>/usr/share</primary>
+	</indexterm><indexterm>
+	  <primary>/usr/share/swat</primary>
+	</indexterm><indexterm>
+	  <primary>/usr/lib/samba</primary>
+	</indexterm><indexterm>
+	  <primary>/usr/share/samba/swat</primary>
+	</indexterm><indexterm>
+	  <primary>SWAT</primary>
+	</indexterm><indexterm>
+	  <primary>VFS modules</primary>
+	</indexterm>
+	Linux vendors, working in conjunction with the Free Standards Group (FSG), Linux Standards Base (LSB), and File Hierarchy	
+	System (FHS), have elected to locate the configuration files under the <filename>/etc/samba</filename> directory, common binary
+	files (those used by users) in the <filename>/usr/bin</filename> directory, and the administrative files (daemons) in the
+	<filename>/usr/sbin</filename> directory. Support files for the Samba Web Admin Tool (SWAT) are located under the
+	<filename>/usr/share</filename> directory, either in <filename>/usr/share/samba/swat</filename> or in
+	<filename>/usr/share/swat</filename>. There are additional support files for <command>smbd</command> in the
+	<filename>/usr/lib/samba</filename> directory tree. The files located there include the dynamically loadable modules for the
+	passdb backend as well as for the VFS modules.
+	</para>
+
+      <para><indexterm>
+	  <primary>/var/lib/samba</primary>
+	</indexterm><indexterm>
+	  <primary>/var/log/samba</primary>
+	</indexterm><indexterm>
+	  <primary>run-time control files</primary>
+	</indexterm>
+	Samba creates runtime control files and generates log files. The runtime control files (tdb and dat files) are stored in
+	the <filename>/var/lib/samba</filename> directory. Log files are created in <filename>/var/log/samba.</filename>
+	</para>
+
+	<para>
+	When Samba is built and installed using the default Samba Team process, all files are located under the 
+	<filename>/usr/local/samba</filename> directory tree. This makes it simple to find the files that Samba owns.
+	</para>
+
+      <para><indexterm>
+	  <primary>smbd</primary>
+	  <secondary>location of files</secondary>
+	</indexterm>
+	One way to find the Samba files that are installed on your UNIX/Linux system is to search for the location
+	of all files called <command>smbd</command>. Here is an example:
+<screen>
+&rootprompt; find / -name smbd -print
+</screen>
+	You can find the location of the configuration files by running:
+<screen>
+&rootprompt; /path-to-binary-file/smbd -b | more
+...
+Paths:
+   SBINDIR: /usr/sbin
+   BINDIR: /usr/bin
+   SWATDIR: /usr/share/samba/swat
+   CONFIGFILE: /etc/samba/smb.conf
+   LOGFILEBASE: /var/log/samba
+   LMHOSTSFILE: /etc/samba/lmhosts
+   LIBDIR: /usr/lib/samba
+   SHLIBEXT: so
+   LOCKDIR: /var/lib/samba
+   PIDDIR: /var/run/samba
+   SMB_PASSWD_FILE: /etc/samba/smbpasswd
+   PRIVATE_DIR: /etc/samba
+...
+</screen>
+	If you wish to locate the Samba version, just run:
+<screen>
+&rootprompt; /path-to-binary-file/smbd -V
+Version 3.0.20-SUSE
+</screen>
+	</para>
+
+	<para>
+	Many people have been caught by installation of Samba using the default Samba Team process when it was already installed
+	by the platform vendor's method. If your platform uses RPM format packages, you can check to see if Samba is installed by
+	executing:<indexterm>
+	  <primary>rpm</primary>
+	</indexterm>
+<screen>
+&rootprompt; rpm -qa | grep samba
+samba3-pdb-3.0.20-1
+samba3-vscan-0.3.6-0
+samba3-winbind-3.0.20-1
+samba3-3.0.20-1
+samba3-python-3.0.20-1
+samba3-utils-3.0.20-1
+samba3-doc-3.0.20-1
+samba3-client-3.0.20-1
+samba3-cifsmount-3.0.20-1
+	</screen><indexterm>
+	  <primary>package names</primary>
+	</indexterm>
+	The package names, of course, vary according to how the vendor, or the binary package builder, prepared them.
+	</para>
+
+</sect1>
+
+<sect1>
+	<title>Starting Samba</title>
+
+      <para><indexterm>
+	  <primary>daemon</primary>
+	</indexterm>
+	Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services.
+	An example of a service is the Apache Web server for which the daemon is called <command>httpd</command>. In the case of Samba, there
+	are three daemons, two of which are needed as a minimum.
+	</para>
+
+	<para>
+	The Samba server is made up of the following daemons:
+	</para>
+
+<example id="ch12SL">
+<title>A Useful Samba Control Script for SUSE Linux</title>
+<screen>
+#!/bin/bash
+#
+# Script to start/stop samba
+# Locate this in /sbin as a file called 'samba'
+
+RCD=/etc/rc.d
+
+if [ z$1 == 'z' ]; then
+        echo $0 - No arguments given; must be start or stop.
+        exit
+fi
+
+if [ $1 == 'start' ]; then
+        ${RCD}/nmb start
+        ${RCD}/smb start
+        ${RCD}/winbind start
+
+fi
+if [ $1 == 'stop' ]; then
+        ${RCD}/smb stop
+        ${RCD}/winbind stop
+        ${RCD}/nmb stop
+fi
+if [ $1 == 'restart' ]; then
+        ${RCD}/smb stop
+        ${RCD}/winbind stop
+        ${RCD}/nmb stop
+        sleep 5
+        ${RCD}/nmb start
+        ${RCD}/smb start
+        ${RCD}/winbind start
+fi
+exit 0
+</screen>
+</example>
+
+	<variablelist>
+		<varlistentry><term>nmbd</term>
+			<listitem><para>
+			<indexterm><primary>smbd</primary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
+			This daemon handles all name registration and resolution requests. It is the primary vehicle involved
+			in network browsing. It handles all UDP-based protocols. The <command>nmbd</command> daemon should
+			be the first command started as part of the Samba startup process.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>smbd</term>
+			<listitem><para>
+			<indexterm><primary>nmbd</primary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
+			This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
+			manages local authentication. It should be started immediately following the startup of <command>nmbd</command>.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>winbindd</term>
+			<listitem><para>
+			<indexterm><primary>winbindd</primary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
+			This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when
+			Samba has trust relationships with another domain. The <command>winbindd</command> daemon will check the
+			&smb.conf; file for the presence of the <parameter>idmap uid</parameter> and <parameter>idmap gid</parameter>
+			parameters. If they are not found, <command>winbindd</command> bails out and refuses to start.
+			</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>
+	When Samba has been packaged by an operating system vendor, the startup process is typically a custom feature of its
+	integration into the platform as a whole. Please refer to your operating system platform administration manuals for
+	specific information pertaining to correct management of Samba startup.
+	</para>
+
+<example id="ch12RHscript">
+<title>A Sample Samba Control Script for Red Hat Linux</title>
+<screen>
+#!/bin/sh
+#
+# chkconfig: 345 81 35
+# description: Starts and stops the Samba smbd and nmbd daemons \
+#              used to provide SMB network services.
+
+# Source function library.
+. /etc/rc.d/init.d/functions
+# Source networking configuration.
+. /etc/sysconfig/network
+# Check that networking is up.
+[ ${NETWORKING} = "no" ] &amp;&amp; exit 0
+CONFIG=/etc/samba/smb.conf
+# Check that smb.conf exists.
+[ -f $CONFIG ] || exit 0
+
+# See how we were called.
+case "$1" in
+  start)
+        echo -n "Starting SMB services: "
+        daemon smbd -D; daemon nmbd -D; echo;
+        touch /var/lock/subsys/smb
+        ;;
+  stop)
+        echo -n "Shutting down SMB services: "
+        smbdpids=`ps guax | grep smbd | grep -v grep | awk '{print $2}'`
+        for pid in $smbdpids; do
+                kill -TERM $pid
+        done
+        killproc nmbd -TERM; rm -f /var/lock/subsys/smb
+        echo ""
+        ;;
+  status)
+        status smbd; status nmbd;
+        ;;
+  restart)
+        echo -n "Restarting SMB services: "
+        $0 stop; $0 start;
+        echo "done."
+        ;;
+  *)
+        echo "Usage: smb {start|stop|restart|status}"
+        exit 1
+esac
+</screen>
+</example>
+
+      <para><indexterm>
+	  <primary>samba control script</primary>
+	</indexterm>
+	SUSE Linux implements individual control over each Samba daemon. A Samba control script that can be conveniently
+	executed from the command line is shown in <link linkend="ch12SL"/>. This can be located in the directory
+	<filename>/sbin</filename> in a file called <filename>samba</filename>. This type of control script should be
+	owned by user root and group root, and set so that only root can execute it.
+	</para>
+
+      <para><indexterm>
+	  <primary>startup script</primary>
+	</indexterm>
+	A sample startup script for a Red Hat Linux system is shown in <link linkend="ch12RHscript"/>.
+	This file could be located in the directory <filename>/etc/rc.d</filename> and can be called
+	<filename>samba</filename>. A similar startup script is required to control <command>winbind</command>.
+	If you want to find more information regarding startup scripts please refer to the packaging section of
+	the Samba source code distribution tarball. The packaging files for each platform include a
+	startup control file.
+	</para>
+
+</sect1>
+
+<sect1>
+	<title>DNS Configuration Files</title>
+
+	<para>
+	The following files are common to all DNS server configurations. Rather than repeat them multiple times, they
+	are presented here for general reference.
+	</para>
+
+	<sect2>
+	<title>The Forward Zone File for the Loopback Adaptor</title>
+
+	<para>
+	The forward zone file for the loopback address never changes. An example file is shown
+	in <link linkend="loopback"/>. All traffic destined for an IP address that is hosted on a
+	physical interface on the machine itself is routed to the loopback adaptor. This is
+	a fundamental design feature of the TCP/IP protocol implementation. The loopback adaptor
+	is called <constant>localhost</constant>.
+	</para>
+
+<example id="loopback">
+<title>DNS Localhost Forward Zone File: <filename>/var/lib/named/localhost.zone</filename></title>
+<screen>
+$TTL 1W
+@		IN SOA	@   root (
+				42		; serial
+				2D		; refresh
+				4H		; retry
+				6W		; expiry
+				1W )		; minimum
+
+		IN NS		@
+		IN A		127.0.0.1
+</screen>
+</example>
+
+	</sect2>
+
+	<sect2>
+	<title>The Reverse Zone File for the Loopback Adaptor</title>
+
+	<para>
+	The reverse zone file for the loopback address as shown in <link linkend="dnsloopy"/>
+	is necessary so that references to the address <constant>127.0.0.1</constant> can be
+	resolved to the correct name of the interface. 
+	</para>
+
+<example id="dnsloopy">
+<title>DNS Localhost Reverse Zone File: <filename>/var/lib/named/127.0.0.zone</filename></title>
+<screen>
+$TTL 1W
+@		IN SOA		localhost.   root.localhost. (
+				42		; serial
+				2D		; refresh
+				4H		; retry
+				6W		; expiry
+				1W )		; minimum
+
+		IN NS		localhost.
+1		IN PTR		localhost.
+</screen>
+</example>
+
+<example id="roothint">
+<title>DNS Root Name Server Hint File: <filename>/var/lib/named/root.hint</filename></title>
+<screen>
+; This file is made available by InterNIC under anonymous FTP as
+;       file                /domain/named.root
+;       on server           FTP.INTERNIC.NET
+; last update: Nov 5, 2002. Related version of root zone: 2002110501
+; formerly NS.INTERNIC.NET
+.                        3600000  IN  NS    A.ROOT-SERVERS.NET.
+A.ROOT-SERVERS.NET.      3600000      A     198.41.0.4
+; formerly NS1.ISI.EDU
+.                        3600000      NS    B.ROOT-SERVERS.NET.
+B.ROOT-SERVERS.NET.      3600000      A     128.9.0.107
+; formerly C.PSI.NET
+.                        3600000      NS    C.ROOT-SERVERS.NET.
+C.ROOT-SERVERS.NET.      3600000      A     192.33.4.12
+; formerly TERP.UMD.EDU
+.                        3600000      NS    D.ROOT-SERVERS.NET.
+D.ROOT-SERVERS.NET.      3600000      A     128.8.10.90
+; formerly NS.NASA.GOV
+.                        3600000      NS    E.ROOT-SERVERS.NET.
+E.ROOT-SERVERS.NET.      3600000      A     192.203.230.10
+; formerly NS.ISC.ORG
+.                        3600000      NS    F.ROOT-SERVERS.NET.
+F.ROOT-SERVERS.NET.      3600000      A     192.5.5.241
+; formerly NS.NIC.DDN.MIL
+.                        3600000      NS    G.ROOT-SERVERS.NET.
+G.ROOT-SERVERS.NET.      3600000      A     192.112.36.4
+; formerly AOS.ARL.ARMY.MIL
+.                        3600000      NS    H.ROOT-SERVERS.NET.
+H.ROOT-SERVERS.NET.      3600000      A     128.63.2.53
+; formerly NIC.NORDU.NET
+.                        3600000      NS    I.ROOT-SERVERS.NET.
+I.ROOT-SERVERS.NET.      3600000      A     192.36.148.17
+; operated by VeriSign, Inc. 
+.                        3600000      NS    J.ROOT-SERVERS.NET.
+J.ROOT-SERVERS.NET.      3600000      A     192.58.128.30
+; housed in LINX, operated by RIPE NCC
+.                        3600000      NS    K.ROOT-SERVERS.NET.
+K.ROOT-SERVERS.NET.      3600000      A     193.0.14.129 
+; operated by IANA
+.                        3600000      NS    L.ROOT-SERVERS.NET.
+L.ROOT-SERVERS.NET.      3600000      A     198.32.64.12
+; housed in Japan, operated by WIDE
+.                        3600000      NS    M.ROOT-SERVERS.NET.
+M.ROOT-SERVERS.NET.      3600000      A     202.12.27.33
+; End of File
+</screen>
+</example>
+	</sect2>
+
+	<sect2>
+	<title>DNS Root Server Hint File</title>
+
+	<para>
+	The content of the root hints file as shown in <link linkend="roothint"/>  changes slowly over time. 
+	Periodically this file should be updated from the source shown. Because
+	  of its size, this file is located at the end of this chapter.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1 id="altldapcfg">
+	<title>Alternative LDAP Database Initialization</title>
+
+      <para><indexterm>
+	  <primary>LDAP</primary>
+	  <secondary>database</secondary>
+	</indexterm><indexterm>
+	  <primary>LDAP</primary>
+	  <secondary>initial configuration</secondary>
+	</indexterm>
+	The following procedure may be used as an alternative means of configuring
+	the initial LDAP database. Many administrators prefer to have greater control
+	over how system files get configured.
+	</para>
+
+	<sect2>
+	<title>Initialization of the LDAP Database</title>
+
+	<para><indexterm>
+	    <primary>LDIF</primary>
+	  </indexterm><indexterm>
+	    <primary>Domain Groups</primary>
+	    <secondary>well-known</secondary>
+	  </indexterm><indexterm>
+	    <primary>SID</primary>
+	  </indexterm>
+	The first step to get the LDAP server ready for action is to create the LDIF file from
+	which the LDAP database will be preloaded. This is necessary to create the containers
+	into which the user, group, and other accounts are written. It is also necessary to
+	preload the well-known Windows NT Domain Groups, as they must have the correct SID so
+	that they can be recognized as special NT Groups by the MS Windows clients.
+	</para>
+
+	<procedure id="ldapinit">
+	<title>LDAP Directory Pre-Load Steps</title>
+
+		<step><para>
+		Create a directory in which to store the files you use to generate
+		the LDAP LDIF file for your system. Execute the following:
+<screen>
+&rootprompt; mkdir /etc/openldap/SambaInit
+&rootprompt; chown root:root /etc/openldap/SambaInit
+&rootprompt; chmod 700 /etc/openldap/SambaInit
+</screen>
+		</para></step>
+
+		<step><para>
+		Install the files shown in <link linkend="sbehap-ldapreconfa"/>, <link linkend="sbehap-ldapreconfb"/>,
+		and <link linkend="sbehap-ldapreconfc"/> into the directory 
+		<filename>/etc/openldap/SambaInit/SMBLDAP-ldif-preconfig.sh.</filename> These three files are,
+		respectively, parts A, B, and C of the <filename>SMBLDAP-ldif-preconfig.sh</filename> file.
+		</para></step>
+
+		<step><para>
+		Install the files shown in <link linkend="sbehap-ldifpata"/> and <link linkend="sbehap-ldifpatb"/> into the directory
+		<filename>/etc/openldap/SambaInit/.</filename> These two files are
+                parts A and B, respectively, of the <filename>init-ldif.pat</filename> file.
+		</para></step>
+
+		<step><para>
+		Change to the <filename>/etc/openldap/SambaInit</filename> directory. Execute the following:
+<screen>
+&rootprompt; sh SMBLDAP-ldif-preconfig.sh
+
+How do you wish to refer to your organization?
+Suggestions:
+        Black Tire Company, Inc.
+        Cat With Hat Ltd.
+How would you like your organization name to appear?
+Your organization name is: My Organization
+Enter a new name is this is not what you want, press Enter to Continue.
+Name [My Organization]: Abmas Inc.
+
+Samba Config File Location [/etc/samba/smb.conf]:
+Enter a new full path or press Enter to continue.
+Samba Config File Location [/etc/samba/smb.conf]:
+Domain Name: MEGANET2
+Domain SID: S-1-5-21-3504140859-1010554828-2431957765
+
+The name of your Internet domain is now needed in a special format
+as follows, if your domain name is mydomain.org, what we need is
+the information in the form of:
+        Domain ID: mydomain
+        Top level: org
+If your fully qualified hostname is: snoopy.bazaar.garagesale.net
+where "snoopy" is the name of the machine,
+Then the information needed is:
+        Domain ID: garagesale
+        Top Level: net
+
+Found the following domain name: abmas.biz
+I think the bit we are looking for might be: abmas
+Enter the domain name or press Enter to continue:
+
+The top level organization name I will use is: biz
+Enter the top level org name or press Enter to continue:
+&rootprompt;
+</screen>
+		This creates a file called <filename>MEGANET2.ldif</filename>.
+		</para></step>
+
+		<step><para>
+		It is now time to preload the LDAP database with the following
+		command:
+<screen>
+&rootprompt; slapadd -v -l MEGANET2.ldif
+added: "dc=abmas,dc=biz" (00000001)
+added: "cn=Manager,dc=abmas,dc=biz" (00000002)
+added: "ou=People,dc=abmas,dc=biz" (00000003)
+added: "ou=Computers,dc=abmas,dc=biz" (00000004)
+added: "ou=Groups,dc=abmas,dc=biz" (00000005)
+added: "ou=Domains,dc=abmas,dc=biz" (00000006)
+added: "sambaDomainName=MEGANET2,ou=Domains,dc=abmas,dc=biz" (00000007)
+added: "cn=domadmins,ou=Groups,dc=abmas,dc=biz" (00000008)
+added: "cn=domguests,ou=Groups,dc=abmas,dc=biz" (00000009)
+added: "cn=domusers,ou=Groups,dc=abmas,dc=biz" (0000000a)
+</screen>
+		You should verify that the account information was correctly loaded by executing:
+<screen>
+&rootprompt; slapcat
+dn: dc=abmas,dc=biz
+objectClass: dcObject
+objectClass: organization
+dc: abmas
+o: Abmas Inc.
+description: Posix and Samba LDAP Identity Database
+structuralObjectClass: organization
+entryUUID: af552f8e-c4a1-1027-9002-9421e01bf474
+creatorsName: cn=manager,dc=abmas,dc=biz
+modifiersName: cn=manager,dc=abmas,dc=biz
+createTimestamp: 20031217055747Z
+modifyTimestamp: 20031217055747Z
+entryCSN: 2003121705:57:47Z#0x0001#0#0000
+...
+
+dn: cn=domusers,ou=Groups,dc=abmas,dc=biz
+objectClass: posixGroup
+objectClass: sambaGroupMapping
+gidNumber: 513
+cn: domusers
+sambaSID: S-1-5-21-3504140859-1010554828-2431957765-513
+sambaGroupType: 2
+displayName: Domain Users
+description: Domain Users
+structuralObjectClass: posixGroup
+entryUUID: af7e98ba-c4a1-1027-900b-9421e01bf474
+creatorsName: cn=manager,dc=abmas,dc=biz
+modifiersName: cn=manager,dc=abmas,dc=biz
+createTimestamp: 20031217055747Z
+modifyTimestamp: 20031217055747Z
+entryCSN: 2003121705:57:47Z#0x000a#0#0000
+</screen>
+		</para></step>
+
+		<step><para>
+		Your LDAP database is ready for testing. You can now start the LDAP server
+		using the system tool for your Linux operating system. For SUSE Linux, you can
+		do this as follows:
+<screen>
+&rootprompt; rcldap start
+</screen>
+		</para></step>
+
+		<step><para>
+		It is now a good idea to validate that the LDAP server is running correctly.
+		Execute the following:
+<screen>
+&rootprompt; ldapsearch -x -b "dc=abmas,dc=biz" "(ObjectClass=*)"
+# extended LDIF
+#
+# LDAPv3
+# base &lt;dc=abmas,dc=biz&gt; with scope sub
+# filter: (ObjectClass=*)
+# requesting: ALL
+#
+
+# abmas.biz
+dn: dc=abmas,dc=biz
+objectClass: dcObject
+objectClass: organization
+dc: abmas
+o: Abmas Inc.
+description: Posix and Samba LDAP Identity Database
+...
+# domusers, Groups, abmas.biz
+dn: cn=domusers,ou=Groups,dc=abmas,dc=biz
+objectClass: posixGroup
+objectClass: sambaGroupMapping
+gidNumber: 513
+cn: domusers
+sambaSID: S-1-5-21-3504140859-1010554828-2431957765-513
+sambaGroupType: 2
+displayName: Domain Users
+description: Domain Users
+
+# search result
+search: 2
+result: 0 Success
+
+# numResponses: 11
+# numEntries: 10
+</screen>
+		Your LDAP server is ready for creation of additional accounts.
+		</para></step>
+	</procedure>
+
+	</sect2>
+
+<example id="sbehap-ldapreconfa">
+<title>LDAP Pre-configuration Script: <filename>SMBLDAP-ldif-preconfig.sh</filename> &smbmdash; Part A</title>
+<screen>
+#!/bin/bash
+#
+# This script prepares the ldif LDAP load file only
+#
+
+# Pattern File Name
+file=init-ldif.pat
+
+# The name of my organization
+ORGNAME="My Organization"
+
+# My Internet domain. ie: if my domain is: buckets.org, INETDOMAIN="buckets"
+INETDOMAIN="my-domain"
+
+# In the above case, md domain is: buckets.org, TLDORG="org"
+TLDORG="org"
+
+# This is the Samba Domain/Workgroup Name
+DOMNAME="MYWORKGROUP"
+
+#
+# Here We Go ...
+#
+
+cat &lt;&lt;EOF
+
+How do you wish to refer to your organization?
+
+Suggestions:
+	Black Tire Company, Inc.
+	Cat With Hat Ltd.
+
+How would you like your organization name to appear?
+
+EOF
+
+echo "Your organization name is: $ORGNAME"
+echo
+echo "Enter a new name or, press Enter to Continue."
+echo
+</screen>
+</example>
+
+<example id="sbehap-ldapreconfb">
+<title>LDAP Pre-configuration Script: <filename>SMBLDAP-ldif-preconfig.sh</filename> &smbmdash; Part B</title>
+<screen>
+echo -e -n "Name [$ORGNAME]: "
+	read name
+
+if [ ! -z "$name" ]; then 
+	ORGNAME=${name}
+fi
+echo
+sed "s/ORGNAME/${ORGNAME}/g" &lt; $file &gt; $file.tmp1
+
+# Try to find smb.conf
+
+if [ -e /usr/local/samba/lib/smb.conf ]; then
+	CONF=/usr/local/samba/lib/smb.conf
+elif [ -e /etc/samba/smb.conf ]; then
+	CONF=/etc/samba/smb.conf
+fi
+
+echo "Samba Config File Location [$CONF]: "
+echo
+echo "Enter a new full path or press Enter to continue."
+echo
+echo -n "Samba Config File Location [$CONF]: "
+	read name
+if [ ! -z "$name" ]; then
+	CONF=$name
+fi
+echo
+
+# Find the name of our Domain/Workgroup
+DOMNAME=`grep -i workgroup ${CONF} | sed "s/ //g" | cut -f2 -d=`
+echo Domain Name: $DOMNAME
+echo
+
+sed "s/DOMNAME/${DOMNAME}/g" &lt; $file.tmp1 &gt; $file.tmp2
+
+DOMSID=`net getlocalsid ${DOMNAME} | cut -f2 -d: | sed "s/ //g"`
+echo Domain SID: $DOMSID
+
+sed "s/DOMSID/${DOMSID}/g" &lt; $file.tmp2 &gt; $file.tmp1
+</screen>
+</example>
+
+<example id="sbehap-ldapreconfc">
+<title>LDAP Pre-configuration Script: <filename>SMBLDAP-ldif-preconfig.sh</filename> &smbmdash; Part C</title>
+<screen>
+cat &lt;&lt;EOL
+The name of your Internet domain is now needed in a special format
+as follows, if your domain name is mydomain.org, what we need is
+the information in the form of:
+	Domain ID: mydomain
+	Top level: org
+
+If your fully qualified hostname is: snoopy.bazaar.garagesale.net
+where "snoopy" is the name of the machine,
+Then the information needed is:
+	Domain ID: garagesale
+	Top Level: net
+
+EOL
+INETDOMAIN=`hostname -d | cut -f1 -d.`
+echo Found the following domain name: `hostname -d`
+echo "I think the bit we are looking for might be: $INETDOMAIN"
+echo
+echo -n "Enter the domain name or press Enter to continue: "
+	read domnam
+if [ ! -z $domnam ]; then
+	INETDOMAIN=$domnam
+fi
+echo
+sed "s/INETDOMAIN/${INETDOMAIN}/g" &lt; $file.tmp1 &gt; $file.tmp2
+TLDORG=`hostname -d | sed "s/${INETDOMAIN}.//g"`
+echo "The top level organization name I will use is: ${TLDORG}"
+echo
+echo -n "Enter the top level org name or press Enter to continue: "
+	read domnam
+if [ ! -z $domnam ]; then
+        TLDORG=$domnam
+fi
+sed "s/TLDORG/${TLDORG}/g" &lt; $file.tmp2 &gt; $DOMNAME.ldif
+rm $file.tmp*
+exit 0
+</screen>
+</example>
+
+<example id="sbehap-ldifpata">
+<title>LDIF Pattern File Used to Pre-configure LDAP &smbmdash; Part A</title>
+<screen>
+dn: dc=INETDOMAIN,dc=TLDORG
+objectClass: dcObject
+objectClass: organization
+dc: INETDOMAIN
+o: ORGNAME
+description: Posix and Samba LDAP Identity Database
+
+dn: cn=Manager,dc=INETDOMAIN,dc=TLDORG
+objectClass: organizationalRole
+cn: Manager
+description: Directory Manager
+
+dn: ou=People,dc=INETDOMAIN,dc=TLDORG
+objectClass: top
+objectClass: organizationalUnit
+ou: People
+
+dn: ou=Computers,dc=INETDOMAIN,dc=TLDORG
+objectClass: top
+objectClass: organizationalUnit
+ou: Computers
+
+dn: ou=Groups,dc=INETDOMAIN,dc=TLDORG
+objectClass: top
+objectClass: organizationalUnit
+ou: Groups
+
+dn: ou=Idmap,dc=INETDOMAIN,dc=TLDORG
+objectClass: top
+objectClass: organizationalUnit
+ou: Idmap
+
+dn: ou=Domains,dc=INETDOMAIN,dc=TLDORG
+objectClass: top
+objectClass: organizationalUnit
+ou: Domains
+
+dn: sambaDomainName=DOMNAME,ou=Domains,dc=INETDOMAIN,dc=TLDORG
+objectClass: sambaDomain
+sambaDomainName: DOMNAME
+sambaSID: DOMSID
+sambaAlgorithmicRidBase: 1000
+structuralObjectClass: sambaDomain
+</screen>
+</example>
+
+<example id="sbehap-ldifpatb">
+<title>LDIF Pattern File Used to Pre-configure LDAP &smbmdash; Part B</title>
+<screen>
+dn: cn=domadmins,ou=Groups,dc=INETDOMAIN,dc=TLDORG
+objectClass: posixGroup
+objectClass: sambaGroupMapping
+gidNumber: 512
+cn: domadmins
+sambaSID: DOMSID-512
+sambaGroupType: 2
+displayName: Domain Admins
+description: Domain Administrators
+
+dn: cn=domguests,ou=Groups,dc=INETDOMAIN,dc=TLDORG
+objectClass: posixGroup
+objectClass: sambaGroupMapping
+gidNumber: 514
+cn: domguests
+sambaSID: DOMSID-514
+sambaGroupType: 2
+displayName: Domain Guests
+description: Domain Guests Users
+
+dn: cn=domusers,ou=Groups,dc=INETDOMAIN,dc=TLDORG
+objectClass: posixGroup
+objectClass: sambaGroupMapping
+gidNumber: 513
+cn: domusers
+sambaSID: DOMSID-513
+sambaGroupType: 2
+displayName: Domain Users
+description: Domain Users
+</screen>
+</example>
+
+</sect1>
+
+<sect1>
+<title>The LDAP Account Manager</title>
+
+<para>
+<indexterm><primary>LAM</primary></indexterm>
+<indexterm><primary>LDAP Account Manager</primary><see>LAM</see></indexterm>
+<indexterm><primary>PHP</primary></indexterm>
+<indexterm><primary>unencrypted</primary></indexterm>
+<indexterm><primary>SSL</primary></indexterm>
+<indexterm><primary>Posix</primary></indexterm>
+<indexterm><primary>accounts</primary><secondary>manage</secondary></indexterm>
+The LDAP Account Manager (LAM) is an application suite that has been written in PHP.
+LAM can be used with any Web server that has PHP4 support. It connects to the LDAP
+server either using unencrypted connections or via SSL/TLS. LAM can be used to manage
+Posix accounts as well as SambaSAMAccounts for users, groups, and Windows machines
+(hosts).
+</para>
+
+<para>
+LAM is available from the <ulink url="http://sourceforge.net/projects/lam/">LAM</ulink>
+home page and from its mirror sites. LAM has been released under the GNU GPL version 2.
+The current version of LAM is 0.4.9. Release of version 0.5 is expected in the third quarter
+of 2005.
+</para>
+
+<para>
+<indexterm><primary>PHP4</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>Perl</primary></indexterm>
+Requirements:
+</para>
+
+<itemizedlist>
+	<listitem><para>A web server that will work with PHP4.</para></listitem>
+	<listitem><para>PHP4 (available from the <ulink url="http://www.php.net/">PHP</ulink> home page.)</para></listitem>
+	<listitem><para>OpenLDAP 2.0 or later.</para></listitem>
+	<listitem><para>A Web browser that supports CSS.</para></listitem>
+	<listitem><para>Perl.</para></listitem>
+	<listitem><para>The gettext package.</para></listitem>
+	<listitem><para>mcrypt + mhash (optional).</para></listitem>
+	<listitem><para>It is also a good idea to install SSL support.</para></listitem>
+</itemizedlist>
+
+<para>
+LAM is a useful tool that provides a simple Web-based device that can be used to
+manage the contents of the LDAP directory to:
+<indexterm><primary>organizational units</primary></indexterm>
+<indexterm><primary>operating profiles</primary></indexterm>
+<indexterm><primary>account policies</primary></indexterm>
+</para>
+
+<itemizedlist>
+	<listitem><para>Display user/group/host and Domain entries.</para></listitem>
+	<listitem><para>Manage entries (Add/Delete/Edit).</para></listitem>
+	<listitem><para>Filter and sort entries.</para></listitem>
+	<listitem><para>Store and use multiple operating profiles.</para></listitem>
+	<listitem><para>Edit organizational units (OUs).</para></listitem>
+	<listitem><para>Upload accounts from a file.</para></listitem>
+	<listitem><para>Is compatible with Samba-2.2.x and Samba-3.</para></listitem>
+</itemizedlist>
+
+<para>
+When correctly configured, LAM allows convenient management of UNIX (Posix) and Samba
+user, group, and windows domain member machine accounts.
+</para>
+
+<para>
+<indexterm><primary>default password</primary></indexterm>
+<indexterm><primary>secure connections</primary></indexterm>
+<indexterm><primary>LAM</primary></indexterm>
+<indexterm><primary>SSL</primary></indexterm>
+The default password is <quote>lam.</quote> It is highly recommended that you use only 
+an SSL connection to your Web server for all remote operations involving LAM. If you 
+want secure connections, you must configure your Apache Web server to permit connections 
+to LAM using only SSL.
+</para>
+
+<procedure id="sbehap-laminst">
+<title>Apache Configuration Steps for LAM</title>
+
+	<step><para>
+	Extract the LAM package by untarring it as shown here:
+<screen>
+&rootprompt; tar xzf ldap-account-manager_0.4.9.tar.gz
+</screen>
+	Alternatively, install the LAM DEB for your system using the following command:
+<screen>
+&rootprompt; dpkg -i ldap-account-manager_0.4.9.all.deb
+</screen>
+	</para></step>
+	
+	<step><para>
+	Copy the extracted files to the document root directory of your Web server.
+	For example, on SUSE Linux Enterprise Server 9, copy to the 
+	<filename>/srv/www/htdocs</filename> directory.
+	</para></step>
+
+	<step><para>
+	<indexterm><primary>file permissions</primary></indexterm>
+	Set file permissions using the following commands:
+<screen>
+&rootprompt; chown -R wwwrun:www /srv/www/htdocs/lam
+&rootprompt; chmod 755 /srv/www/htdocs/lam/sess
+&rootprompt; chmod 755 /srv/www/htdocs/lam/tmp
+&rootprompt; chmod 755 /srv/www/htdocs/lam/config
+&rootprompt; chmod 755 /srv/www/htdocs/lam/lib/*pl
+</screen>
+	</para></step>
+
+	<step><para>
+	<indexterm><primary>LAM</primary><secondary>configuration file</secondary></indexterm>
+       Using your favorite editor create the following <filename>config.cfg</filename>
+       LAM configuration file:
+<screen>
+&rootprompt; cd /srv/www/htdocs/lam/config
+&rootprompt; cp config.cfg_sample config.cfg
+&rootprompt; vi config.cfg
+</screen>
+	<indexterm><primary>LAM</primary><secondary>profile</secondary></indexterm>
+	<indexterm><primary>LAM</primary><secondary>wizard</secondary></indexterm>
+	An example file is shown in <link linkend="lamcfg"/>.
+	This is the minimum configuration that must be completed. The LAM profile
+	file can be created using a convenient wizard that is part of the LAM
+	configuration suite.
+	</para></step>
+
+	<step><para>
+	Start your Web server then, using your Web browser, connect to 
+	<ulink url="http://localhost/lam">LAM</ulink> URL. Click on the
+	the <parameter>Configuration Login</parameter> link then click on the
+	Configuration Wizard link to begin creation of the default profile so that 
+	LAM can connect to your LDAP server. Alternately, copy the 
+	<filename>lam.conf_sample</filename> file to a file called 
+	<filename>lam.conf</filename> then, using your favorite editor, 
+	change the settings to match local site needs.
+	</para></step>
+</procedure>
+
+	<para>
+	<indexterm><primary>pitfalls</primary></indexterm>
+	An example of a working file is shown here in <link linkend="lamconf"/>.
+	This file has been stripped of comments to keep the size small. The comments
+	and help information provided in the profile file that the wizard creates
+	is very useful and will help many administrators to avoid pitfalls.
+	Your configuration file obviously reflects the configuration options that
+	are preferred at your site.
+	</para>
+
+	<para>
+	<indexterm><primary>LAM</primary><secondary>login screen</secondary></indexterm>
+	It is important that your LDAP server is running at the time that LAM is 
+	being configured. This permits you to validate correct operation.
+	An example of the LAM login screen is provided in <link linkend="lam-login"/>.
+	</para>
+
+	<figure id="lam-login">
+		<title>The LDAP Account Manager Login Screen</title>
+		<imagefile scale="50">lam-login</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>LAM</primary><secondary>configuration editor</secondary></indexterm>
+	The LAM configuration editor has a number of options that must be managed correctly.
+	An example of use of the LAM configuration editor is shown in <link linkend="lam-config"/>.
+	It is important that you correctly set the minimum and maximum UID/GID values that are
+	permitted for use at your site. The default values may not be compatible with a need to
+	modify initial default account values for well-known Windows network users and groups.
+	The best work-around is to temporarily set the minimum values to zero (0) to permit
+	the initial settings to be made. Do not forget to reset these to sensible values before
+	using LAM to add additional users and groups.
+	</para>
+
+	<figure id="lam-config">
+		<title>The LDAP Account Manager Configuration Screen</title>
+		<imagefile scale="50">lam-config</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>PDF</primary></indexterm>
+	LAM has some nice, but unusual features. For example, one unexpected feature in most application
+	screens permits the generation of a PDF file that lists configuration information. This is a well
+	thought out facility. This option has been edited out of the following screen shots to conserve
+	space.
+	</para>
+
+	<para>
+	<indexterm><primary>LAM</primary><secondary>opening screen</secondary></indexterm>
+	When you log onto LAM the opening screen drops you right into the user manager as shown in
+	<link linkend="lam-user"/>. This is a logical action as it permits the most-needed facility
+	to be used immediately. The editing of an existing user, as with the addition of a new user,
+	is easy to follow and very clear in both layout and intent. It is a simple matter to edit
+	generic settings, UNIX specific parameters, and then Samba account requirements. Each step
+	involves clicking a button that intuitively drives you through the process. When you have
+	finished editing simply press the <guimenu>Final</guimenu> button.
+	</para>
+
+	<figure id="lam-user">
+		<title>The LDAP Account Manager User Edit Screen</title>
+		<imagefile scale="50">lam-users</imagefile>
+	</figure>
+
+	<para>
+	The edit screen for groups is shown in <link linkend="lam-group"/>. As with the edit screen
+	for user accounts, group accounts may be rapidly dealt with. <link linkend="lam-group-mem"/>
+	shows a sub-screen from the group editor that permits users to be assigned secondary group
+	memberships. 
+	</para>
+
+	<figure id="lam-group">
+		<title>The LDAP Account Manager Group Edit Screen</title>
+		<imagefile scale="50">lam-groups</imagefile>
+	</figure>
+
+	<figure id="lam-group-mem">
+		<title>The LDAP Account Manager Group Membership Edit Screen</title>
+		<imagefile scale="50">lam-group-members</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>smbldap-tools</primary></indexterm><indexterm><primary>scripts</primary></indexterm>
+	The final screen presented here is one that you should not normally need to use. Host accounts will
+	be automatically managed using the smbldap-tools scripts. This means that the screen <link linkend="lam-host"/>
+	will, in most cases, not be used.
+	</para>
+
+	<figure id="lam-host">
+		<title>The LDAP Account Manager Host Edit Screen</title>
+		<imagefile scale="50">lam-hosts</imagefile>
+	</figure>
+
+	<para>
+	One aspect of LAM that may annoy some users is the way it forces certain conventions on
+	the administrator. For example, LAM does not permit the creation of Windows user and group
+	accounts that contain spaces even though the underlying UNIX/Linux
+	operating system may exhibit no problems with them. Given the propensity for using upper-case
+	characters and spaces (particularly in the default Windows account names) this may cause
+	some annoyance. For the rest, LAM is a very useful administrative tool.
+	</para>
+	
+	<para>
+	The next major release, LAM 0.5, will have fewer restrictions and support the latest Samba features
+	(e.g., logon hours). The new plugin-based architecture also allows management of much more different
+	account types like plain UNIX accounts. The upload can now handle groups and hosts, too. Another
+	important point is the tree view which allows browsing and editing LDAP objects directly.
+	</para>
+
+<example id="lamcfg">
+<title>Example LAM Configuration File &smbmdash; <filename>config.cfg</filename></title>
+<screen>
+# password to add/delete/rename configuration profiles
+password: not24get
+
+# default profile, without ".conf"
+default: lam
+</screen>
+</example>
+
+<example id="lamconf">
+<title>LAM Profile Control File &smbmdash; <filename>lam.conf</filename></title>
+<screen>
+ServerURL: ldap://massive.abmas.org:389
+Admins: cn=Manager,dc=abmas,dc=biz
+Passwd: not24get
+usersuffix: ou=People,dc=abmas,dc=biz
+groupsuffix: ou=Groups,dc=abmas,dc=biz
+hostsuffix: ou=Computers,dc=abmas,dc=biz
+domainsuffix: ou=Domains,dc=abmas,dc=biz
+MinUID: 0
+MaxUID: 65535
+MinGID: 0
+MaxGID: 65535
+MinMachine: 20000
+MaxMachine: 25000
+userlistAttributes: #uid;#givenName;#sn;#uidNumber;#gidNumber
+grouplistAttributes: #cn;#gidNumber;#memberUID;#description
+hostlistAttributes: #cn;#description;#uidNumber;#gidNumber
+maxlistentries: 30
+defaultLanguage: en_GB:ISO-8859-1:English (Great Britain)
+scriptPath: 
+scriptServer: 
+samba3: yes
+cachetimeout: 5
+pwdhash: SSHA
+</screen>
+</example>
+
+</sect1>
+
+<sect1>
+	<title>IDEALX Management Console</title>
+
+	<para>
+	IMC (the IDEALX Mamagement Console) is a tool that can be used as the basis for a comprehensive
+	web-based management interface for UNIX and Linux systems.
+	</para>
+
+	<para>
+	The Samba toolset is the first console developped for IMC. It offers a simple and ergonomic
+	interface for managing a Samba domain controler. The goal is to give Linux administrators who
+	need to manage production Samba servers an effective, intuitive and consistent management 
+	experience. An IMC screenshot of the user management tool is shown in <link linkend="imcidealx"/>.
+	</para>
+
+	<figure id="imcidealx">
+        <title>The IMC Samba User Account Screen</title>
+        <imagefile scale="40">imc-usermanager2</imagefile>
+    </figure>
+
+	<para>
+	IMC is built on a set of Perl modules. Most modules are standard CPAN modules. Some are bundled with IMC,
+	but will soon to be hosted on the CPAN independently, like Struts4P, a port of Struts to the Perl language.
+	</para>
+
+	<para>
+	For further information regarding IMC refer to the web <ulink url="http://imc.sourceforge.net/">site.</ulink>
+	Prebuilt RPM packages are also <ulink url="http://imc.sourceforge.net/download.html">available.</ulink>
+	</para>
+
+</sect1>
+
+<sect1 id="ch12-SUIDSGID">
+	<title>Effect of Setting File and Directory SUID/SGID Permissions Explained</title>
+
+	<indexterm><primary>SUID</primary></indexterm>
+	<indexterm><primary>SGID</primary></indexterm>
+	<para>
+	The setting of the SUID/SGID bits on the file or directory permissions flag has particular
+	consequences. If the file is executable and the SUID bit is set, it executes with the privilege
+	of (with the UID of) the owner of the file. For example, if you are logged onto a system as
+	a normal user (let's say as the user <constant>bobj</constant>), and you execute a file that is owned
+	by the user <constant>root</constant> (uid = 0), and the file has the SUID bit set, then the file is
+	executed as if you had logged in as the user <constant>root</constant> and then executed the file.
+	The SUID bit effectively gives you (as <constant>bobj</constant>) administrative privilege for the
+	use of that executable file.
+	</para>
+
+	<para>
+	The setting of the SGID bit does precisely the same as the effect of the SUID bit, except that it
+	applies the privilege to the UNIX group setting. In other words, the file executes with the force
+	of capability of the group.
+	</para>
+
+	<para>
+	When the SUID/SGID permissions are set on a directory, all files that are created within that directory
+	are automatically given the ownership of the SUID user and the SGID group, as per the ownership
+	of the directory in which the file is created. This means that the system level <command>create()</command>
+	function executes with the SUID user and/or SGID group of the directory in which the file is
+	created.
+	</para>
+
+	<para>
+	If you want to obtain the SUID behavior, simply execute the following command:
+<screen>
+&rootprompt; chmod u+s file-or-directory
+</screen>
+	To set the SGID properties on a file or a directory, execute this command:
+<screen>
+&rootprompt; chmod g+s file-or-directory
+</screen>
+	And to set both SUID and SGID properties, execute the following:
+<screen>
+&rootprompt; chmod ug+s file-or-directory
+</screen>
+	</para>
+
+	<para>
+	Let's consider the example of a directory <filename>/data/accounts</filename>. The permissions on this
+	directory before setting both SUID and SGID on this directory are:
+<screen>
+&rootprompt; ls -al /data/accounts
+total 1
+drwxr-xr-x   10 root     root          232 Dec 18 17:08 .
+drwxr-xr-x   21 root     root          600 Dec 17 23:15 ..
+drwxrwxrwx    2 bobj     Domain Users  48 Dec 18 17:08 accounts/
+drwx------    2 root     root           48 Jan 26  2002 lost+found
+</screen>
+	In this example, if the user <constant>maryv</constant> creates a file, it is owned by her.
+	If <constant>maryv</constant> has the primary group of <constant>Accounts</constant>, the file is
+	owned by the group <constant>Accounts</constant>, as shown in this listing:
+<screen>
+&rootprompt; ls -al /data/accounts/maryvfile.txt
+drw-rw-r--    2 maryv    Accounts     12346 Dec 18 17:53
+</screen>
+	</para>
+
+	<para>
+	Now you set the SUID and SGID and check the result as follows:
+<screen>
+&rootprompt; chmod ug+s /data/accounts
+&rootprompt; ls -al /data/accounts
+total 1
+drwxr-xr-x   10 root     root          232 Dec 18 17:08 .
+drwxr-xr-x   21 root     root          600 Dec 17 23:15 ..
+drwsrwsr-x    2 bobj     Domain Users  48 Dec 18 17:08 accounts
+drwx------    2 root     root           48 Jan 26  2002 lost+found
+</screen>
+	If <constant>maryv</constant> creates a file in this directory after this change has been made, the
+	file is owned by the user <constant>bobj</constant>, and the group is set to the group
+	<constant>Domain Users</constant>, as shown here:
+<screen>
+&rootprompt; chmod ug+s /data/accounts
+&rootprompt; ls -al /data/accounts/maryvfile.txt
+total 1
+drw-rw-r--    2 bobj     Domain Users  12346 Dec 18 18:11 maryvfile.txt
+</screen>
+	</para>
+
+</sect1>
+
+<sect1 id="ch12dblck">
+	<title>Shared Data Integrity</title>
+
+      <para><indexterm>
+	  <primary>data integrity</primary>
+	</indexterm><indexterm>
+	  <primary>multi-user</primary>
+	  <secondary>data access</secondary>
+	</indexterm>
+	The integrity of shared data is often viewed as a particularly emotional issue, especially where
+	there are concurrent problems with multiuser data access. Contrary to the assertions of some who have
+	experienced problems in either area, the cause has nothing to do with the phases of the moons of Jupiter.
+	</para>
+
+	<para>
+	The solution to concurrent multiuser data access problems must consider three separate areas
+	from which the problem may stem:<indexterm>
+	  <primary>locking</primary>
+	  <secondary>Application level</secondary>
+	</indexterm><indexterm>
+	  <primary>locking</primary>
+	  <secondary>Client side</secondary>
+	</indexterm><indexterm>
+	  <primary>locking</primary>
+	  <secondary>Server side</secondary>
+	</indexterm>
+	</para>
+
+	<itemizedlist>
+		<listitem><para>application-level locking controls</para></listitem>
+		<listitem><para>client-side locking controls</para></listitem>
+		<listitem><para>server-side locking controls</para></listitem>
+	</itemizedlist>
+
+      <para><indexterm>
+	  <primary>database applications</primary>
+	</indexterm><indexterm>
+	  <primary>Microsoft Access</primary>
+	</indexterm>
+	Many database applications use some form of application-level access control. An example of one
+	well-known application that uses application-level locking is Microsoft Access. Detailed guidance
+	is provided here because this is the most common application for which problems have been reported.
+	</para>
+
+      <para><indexterm>
+	  <primary>Microsoft Excel</primary>
+	</indexterm><indexterm>
+	  <primary>Act!</primary>
+	</indexterm>
+	Common applications that are affected by client- and server-side locking controls include MS
+	Excel and Act!. Important locking guidance is provided here.
+	</para>
+
+
+	<sect2>
+	<title>Microsoft Access</title>
+
+	<para>
+	The best advice that can be given is to carefully read the Microsoft knowledgebase articles that
+	cover this area. Examples of relevant documents include:
+	</para>
+
+	<itemizedlist>
+	<listitem><para>http://support.microsoft.com/default.aspx?scid=kb;en-us;208778</para></listitem>
+	<listitem><para>http://support.microsoft.com/default.aspx?scid=kb;en-us;299373</para></listitem>
+	</itemizedlist>
+
+
+	<para><indexterm>
+	    <primary>multi-user</primary>
+	    <secondary>access</secondary>
+	  </indexterm><indexterm>
+	    <primary>exclusive open</primary>
+	  </indexterm>
+	Make sure that your MS Access database file is configured for multiuser access (not set for 
+	exclusive open). Open MS Access on each client workstation, then set the following: <menuchoice>
+	<guimenu>(Menu bar) Tools</guimenu><guimenu>Options</guimenu><guimenu>[tab] General</guimenu>
+	</menuchoice>.  Set network path to Default database folder: <filename>\\server\share\folder</filename>.
+	</para>
+
+	<para>
+        You can configure MS Access file sharing behavior as follows: click <guimenu>[tab] Advanced</guimenu>.
+	  Set:<indexterm>
+	    <primary>record locking</primary>
+	  </indexterm>
+	</para>
+
+	<itemizedlist>
+                <listitem><para>Default open mode: Shared</para></listitem>
+                <listitem><para>Default Record Locking: Edited Record</para></listitem>
+                <listitem><para>Open databases using record_level locking</para></listitem>
+	</itemizedlist>
+
+	<para><indexterm>
+	    <primary>MS Access</primary>
+	    <secondary>validate</secondary>
+	  </indexterm>
+        You must now commit the changes so that they will take effect. To do so, click 
+	<guimenu>Apply</guimenu><guimenu>Ok</guimenu>. At this point, you should exit MS Access, restart 
+	it, and then validate that these settings have not changed.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Act! Database Sharing</title>
+
+	<para><indexterm>
+	    <primary>ACT! database</primary>
+	  </indexterm><indexterm>
+	    <primary>data corruption</primary>
+	  </indexterm>
+	Where the server sharing the ACT! database(s) is running Samba,or Windows NT, 200x, or XP, you 
+	must disable opportunistic locking on the server and all workstations. Failure to do so
+	results in data corruption. This information is available from the Act! Web site
+	knowledgebase articles 
+	<ulink url="http://itdomino.saleslogix.com/act.nsf/docid/1998223162925">1998223162925</ulink>
+	as well as from article
+	<ulink url="http://itdomino.saleslogix.com/act.nsf/docid/200110485036">200110485036</ulink>.
+	</para>
+
+	<para><indexterm>
+	    <primary>opportunistic locking</primary>
+	  </indexterm><indexterm>
+	    <primary>Act!Diag</primary>
+	  </indexterm>
+	These documents clearly state that opportunistic locking must be disabled on both
+	the server (Samba in the case we are interested in here), as well as on every workstation
+	from which the centrally shared Act! database will be accessed. Act! provides
+	a tool called <command>Act!Diag</command> that may be used to disable all workstation
+	registry settings that may otherwise interfere with the operation of Act! 
+	Registered Act! users may download this utility from the Act! Web 
+	<ulink url="http://www.act.com/support/updates/index.cfm">site.</ulink>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Opportunistic Locking Controls</title>
+
+	<para><indexterm>
+	    <primary>file caching</primary>
+	  </indexterm>
+	Third-party Windows applications may not be compatible with the use of opportunistic file
+	and record locking. For applications that are known not to be compatible,<footnote>Refer to
+	the application manufacturer's installation guidelines and knowledge base for specific
+	information regarding compatibility. It is often safe to assume that if the software
+	manufacturer does not specifically mention incompatibilities with opportunistic file
+	and record locking, or with Windows client file caching, the application is probably
+	compatible with Windows (as well as Samba) default settings.</footnote> oplock
+	support may need to be disabled both on the Samba server and on the Windows workstations.
+	</para>
+
+	<para><indexterm>
+	    <primary>cache</primary>
+	  </indexterm><indexterm>
+	    <primary>write lock</primary>
+	  </indexterm><indexterm>
+	    <primary>flush</primary>
+	    <secondary>cache memory</secondary>
+	  </indexterm>
+	Oplocks enable a Windows client to cache parts of a file that are being
+	edited. Another windows client may then request to open the file with the
+	ability to write to it. The server will then ask the original workstation
+	that had the file open with a write lock to release its lock. Before
+	doing so, that workstation must flush the file from cache memory to the
+	disk or network drive.
+	</para>
+
+	<para><indexterm>
+	    <primary>Oplocks</primary>
+	    <secondary>disabled</secondary>
+	  </indexterm>
+	Disabling of Oplocks usage may require server and client changes.
+	Oplocks may be disabled by file, by file pattern, on the share, or on the
+	Samba server.
+	</para>
+
+	<para>
+	The following are examples showing how Oplock support may be managed using
+	Samba &smb.conf; file settings:
+<screen>
+By file:        veto oplock files = myfile.mdb
+
+By Pattern:     veto oplock files = /*.mdb/
+
+On the Share:   oplocks = No
+                level2 oplocks = No
+
+On the server:
+(in [global])   oplocks = No
+                level2 oplocks = No
+</screen>
+	</para>
+
+	<para>
+	The following registry entries on Microsoft Windows XP Professional, 2000 Professional, and Windows NT4
+	workstation clients must be configured as shown here:
+<screen>
+REGEDIT4
+
+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
+            Services\LanmanServer\Parameters]
+      "EnableOplocks"=dword:00000000
+
+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
+            Services\LanmanWorkstation\Parameters]
+      "UseOpportunisticLocking"=dword:00000000
+</screen>
+	</para>
+
+	<para>
+	Comprehensive coverage of file and record-locking controls is provided in TOSHARG2, Chapter 13.
+	The information in that chapter was obtained from a wide variety of sources.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-Appendix2.xml b/docs-xml/Samba3-ByExample/SBE-Appendix2.xml
new file mode 100644
index 00000000000..51d24889f18
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-Appendix2.xml
@@ -0,0 +1,1283 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="primer">
+  <title>Networking Primer</title>
+
+	<para>
+	You are about to use the equivalent of a microscope to look at the information
+	that runs through the veins of a Windows network. We do more to observe the information than
+	to interrogate it. When you are done with this primer, you should have a good understanding
+	of the types of information that flow over the network. Do not worry, this is not
+	a biology lesson. We won't lose you in unnecessary detail. Think to yourself, <quote>This
+	is easy,</quote> then tackle each exercise without fear.
+	</para>
+
+	<para>
+	Samba can be configured with a minimum of complexity. Simplicity should be mastered
+	before you get too deeply into complexities. Let's get moving: we have work to do.
+	</para>
+
+<sect1>
+	<title>Requirements and Notes</title>
+	<para>
+	Successful completion of this primer requires two Microsoft Windows 9x/Me Workstations
+	as well as two Microsoft Windows XP Professional Workstations, each equipped with an Ethernet
+	card connected using a hub. Also required is one additional server (either Windows
+	NT4 Server, Windows 2000 Server, or a Samba-3 on UNIX/Linux server) running a network
+	sniffer and analysis application (Wireshark is a good choice). All work should be undertaken
+	on a quiet network where there is no other traffic. It is best to use a dedicated hub
+	with only the machines under test connected at the time of the exercises.
+	</para>
+
+      <para><indexterm>
+	  <primary>Wireshark</primary>
+	</indexterm>
+	Wireshark (formerly Ethereal) has become the network protocol analyzer of choice for many network administrators.
+	You may find more information regarding this tool from the
+	<ulink url="http://www.wireshark.org">Wireshark</ulink> Web site. Wireshark installation
+	files for Windows may be obtained from the Wireshark Web site. Wireshark is provided with
+	SUSE and Red Hat Linux distributions, as well as with many other Linux distributions. It may
+	not be installed on your system by default. If it is not installed, you may also need
+	to install the <command>libpcap</command> software before you can install or use Wireshark.
+	Please refer to the instructions for your operating system or to the Wireshark Web site
+	for information regarding the installation and operation of Wireshark.
+	</para>
+
+	<para>
+	To obtain <command>Wireshark</command> for your system, please visit the Wireshark
+	<ulink url="http://www.wireshark.org/download.html">download site</ulink>.
+	</para>
+
+	<note><para>
+	The successful completion of this chapter requires that you capture network traffic
+	using <command>Wireshark</command>. It is recommended that you use a hub, not an
+	Ethernet switch. It is necessary for the device used to act as a repeater, not as a
+	filter. Ethernet switches may filter out traffic that is not directed at the machine
+	that is used to monitor traffic; this would not allow you to complete the projects.
+	</para></note>
+
+	<para>
+	<indexterm><primary>network</primary><secondary>captures</secondary></indexterm>
+	Do not worry too much if you do not have access to all this equipment; network captures
+	from the exercises are provided on the enclosed CD-ROM. This makes it possible to dive directly
+	into the analytical part of the exercises if you so desire.
+	</para>
+
+      <para><indexterm>
+	  <primary>network</primary>
+	  <secondary>sniffer</secondary>
+	</indexterm><indexterm>
+	  <primary>protocol analysis</primary>
+	</indexterm>
+	Please do not be alarmed at the use of a high-powered analysis tool (Wireshark) in this
+	primer.  We expose you only to a minimum of detail necessary to complete
+	the exercises. If you choose to use any other network sniffer and protocol
+	analysis tool, be advised that it may not allow you to examine the contents of
+	recently added security protocols used by Windows 200x/XP.
+	</para>
+
+	<para>
+	You could just skim through the exercises and try to absorb the key points made.
+	The exercises provide all the information necessary to convince the die-hard network
+	engineer. You possibly do not require so much convincing and may just want to move on,
+	in which case you should at least read <link linkend="chap01conc"/>.
+	</para>
+
+	<para>
+	<link linkend="chap01qa"/> also provides useful information
+	that may help you to avoid significantly time-consuming networking problems.
+	</para>
+</sect1>
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>
+	The purpose of this chapter is to create familiarity with key aspects of Microsoft Windows
+	network computing. If you want a solid technical grounding, do not gloss over these exercises.
+	The points covered are recurrent issues on the Samba mailing lists.
+	</para>
+
+      <para><indexterm>
+	  <primary>network</primary>
+	  <secondary>broadcast</secondary>
+	</indexterm>
+	You can see from these exercises that Windows networking involves quite a lot of network
+	broadcast traffic. You can look into the contents of some packets, but only to see
+	some particular information that the Windows client sends to a server in the course of
+	establishing a network connection.
+	</para>
+
+	<para>
+	To many people, browsing is everything that happens when one uses Microsoft Internet Explorer.
+	It is only when you start looking at network traffic and noting the protocols
+	and types of information that are used that you can begin to appreciate the complexities of
+	Windows networking and, more importantly, what needs to be configured so that it can work.
+	Detailed information regarding browsing is provided in the recommended
+	preparatory reading.
+	</para>
+
+	<para>
+	Recommended preparatory reading: <emphasis>The Official Samba-3 HOWTO and Reference Guide, Second
+	Edition</emphasis> (TOSHARG2) Chapter 9, <quote>Network Browsing,</quote> and Chapter 3,
+	<quote>Server Types and Security Modes.</quote>
+	</para>
+
+	<sect2>
+	<title>Assignment Tasks</title>
+
+	<para><indexterm>
+	    <primary>browsing</primary>
+	  </indexterm>
+		You are about to witness how Microsoft Windows computer networking functions. The
+		exercises step through identification of how a client machine establishes a
+		connection to a remote Windows server. You observe how Windows machines find
+		each other (i.e., how browsing works) and how the two key types of user identification
+		(share mode security and user mode security) are affected.
+		</para>
+
+	<para><indexterm>
+	    <primary>network</primary>
+	    <secondary>analyzer</secondary>
+	  </indexterm>
+		The networking protocols used by MS Windows networking when working with Samba
+		use TCP/IP as the transport protocol. The protocols that are specific to Windows
+		networking are encapsulated in TCP/IP. The network analyzer we use (Wireshark)
+		is able to show you the contents of the TCP/IP packets (or messages).
+		</para>
+
+		<procedure id="chap01tasks">
+		<title>Diagnostic Tasks</title>
+
+	  <step><para><indexterm>
+		<primary>network</primary>
+		<secondary>trace</secondary>
+	      </indexterm><indexterm>
+		<primary>host announcement</primary>
+	      </indexterm><indexterm>
+		<primary>name resolution</primary>
+	      </indexterm>
+			Examine network traces to witness SMB broadcasts, host announcements,
+			and name resolution processes.
+			</para></step>
+
+			<step><para>
+			Examine network traces to witness how share mode security functions.
+			</para></step>
+
+			<step><para>
+			Examine network traces to witness the use of user mode security.
+			</para></step>
+
+			<step><para>
+			Review traces of network logons for a Windows 9x/Me client as well as
+			a domain logon for a Windows XP Professional client.
+			</para></step>
+		</procedure>
+
+	</sect2>
+</sect1>
+
+<sect1>
+	<title>Exercises</title>
+
+	<para>
+	<indexterm><primary>wireshark</primary></indexterm>
+	You are embarking on a course of discovery. The first part of the exercise requires
+	two MS Windows 9x/Me systems. We called one machine <constant>WINEPRESSME</constant> and the
+	other <constant>MILGATE98</constant>. Each needs an IP address; we used <literal>10.1.1.10</literal>
+	and <literal>10.1.1.11</literal>. The test machines need to be networked via a <emphasis>hub</emphasis>. A UNIX/Linux
+	machine is required to run <command>Wireshark</command> to enable the network activity to be captured.
+	It is important that the machine from which network activity is captured must not interfere with
+	the operation of the Windows workstations. It is helpful for this machine to be passive (does not
+	send broadcast information) to the network.
+	</para>
+
+	<para>
+	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.20 running on a SUSE Enterprise Linux 9</para></listitem>
+	</itemizedlist>
+
+	<para>
+	Choose a workgroup name (MIDEARTH) for each exercise.
+	</para>
+
+	<para>
+	<indexterm><primary>ethereal</primary></indexterm>
+	The network captures provided on the CD-ROM included with this book were captured using <constant>Ethereal</constant>
+	version <literal>0.10.6</literal>. A later version suffices without problems (i.e. you should be using Wireshark), 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 that the value
+	that can be derived from this book really does warrant your taking sufficient time to practice each exercise with
+	care and attention to detail.
+	</para>
+
+	<sect2>
+	<title>Single-Machine Broadcast Activity</title>
+
+	<para>
+	In this section, we start a single Windows 9x/Me machine, then monitor network activity for 30 minutes.
+	</para>
+
+	<procedure>
+	<title>Monitoring Windows 9x Steps</title>
+
+		<step><para>
+		Start the machine from which network activity will be monitored (using <command>Wireshark</command>).
+		Launch <command>Wireshark</command>, click
+			<menuchoice>
+				<guimenu>Capture</guimenu>
+				<guimenuitem>Start</guimenuitem>
+			</menuchoice>.
+		</para>
+
+		<para>
+		Click the following:
+		<orderedlist>
+		<listitem><para>Update list of packets in real time</para></listitem>
+		<listitem><para>Automatic scrolling in live capture</para></listitem>
+		<listitem><para>Enable MAC name resolution</para></listitem>
+		<listitem><para>Enable network name resolution</para></listitem>
+		<listitem><para>Enable transport name resolution</para></listitem>
+		</orderedlist>
+		Click <guibutton>OK</guibutton>.
+		</para></step>
+
+		<step><para>
+		Start the Windows 9x/Me machine to be monitored. Let it run for a full 30 minutes. While monitoring,
+		do not press any keyboard keys, do not click any on-screen icons or menus, and do not answer any dialog boxes.
+		</para></step>
+
+		<step><para>
+		At the conclusion of 30 minutes, stop the capture. Save the capture to a file so you can go back to it later.
+		Leave this machine running in preparation for the task in <link linkend="secondmachine"/>.
+		</para></step>
+
+		<step><para>
+		Analyze the capture. Identify each discrete message type that was captured. Note what transport protocol
+		was used. Identify the timing between messages of identical types.
+		</para></step>
+
+	</procedure>
+
+		<sect3>
+		<title>Findings</title>
+
+		<para>
+		The summary of the first 10 minutes of the packet capture should look like <link linkend="pktcap01"/>.
+		A screenshot of a later stage of the same capture is shown in <link linkend="pktcap02"/>.
+		</para>
+
+		<figure id="pktcap01">
+			<title>Windows Me &smbmdash; Broadcasts &smbmdash; The First 10 Minutes</title>
+			<imagefile scale="40">WINREPRESSME-Capture</imagefile>
+		</figure>
+
+		<figure id="pktcap02">
+			<title>Windows Me &smbmdash; Later Broadcast Sample</title>
+			<imagefile scale="42">WINREPRESSME-Capture2</imagefile>
+		</figure>
+
+	  <para><indexterm>
+	      <primary>Local Master Browser</primary>
+	      <see>LMB</see>
+	    </indexterm><indexterm>
+	      <primary>LMB</primary>
+	    </indexterm>
+		Broadcast messages observed are shown in <link linkend="capsstats01"/>.
+		Actual observations vary a little, but not by much.
+		Early in the startup process, the Windows Me machine broadcasts its name for two reasons:
+		first to ensure that its name would not result in a name clash, and second to establish its
+		presence with the Local Master Browser (LMB).
+		</para>
+
+		<table id="capsstats01">
+			<title>Windows Me &smbmdash; Startup Broadcast Capture Statistics</title>
+			<tgroup cols="4">
+				<colspec align="left" colwidth="3*"/>
+				<colspec align="center"/>
+				<colspec align="center"/>
+				<colspec align="left" colwidth="3*"/>
+				<thead>
+					<row>
+						<entry>Message</entry>
+						<entry>Type</entry>
+						<entry>Num</entry>
+						<entry>Notes</entry>
+					</row>
+				</thead>
+				<tbody>
+					<row>
+						<entry>WINEPRESSME&lt;00&gt;</entry>
+						<entry>Reg</entry>
+						<entry>8</entry>
+						<entry>4 lots of 2, 0.6 sec apart</entry>
+					</row>
+					<row>
+						<entry>WINEPRESSME&lt;03&gt;</entry>
+						<entry>Reg</entry>
+						<entry>8</entry>
+						<entry>4 lots of 2, 0.6 sec apart</entry>
+					</row>
+					<row>
+						<entry>WINEPRESSME&lt;20&gt;</entry>
+						<entry>Reg</entry>
+						<entry>8</entry>
+						<entry>4 lots of 2, 0.75 sec apart</entry>
+					</row>
+					<row>
+						<entry>MIDEARTH&lt;00&gt;</entry>
+						<entry>Reg</entry>
+						<entry>8</entry>
+						<entry>4 lots of 2, 0.75 sec apart</entry>
+					</row>
+					<row>
+						<entry>MIDEARTH&lt;1d&gt;</entry>
+						<entry>Reg</entry>
+						<entry>8</entry>
+						<entry>4 lots of 2, 0.75 sec apart</entry>
+					</row>
+					<row>
+						<entry>MIDEARTH&lt;1e&gt;</entry>
+						<entry>Reg</entry>
+						<entry>8</entry>
+						<entry>4 lots of 2, 0.75 sec apart</entry>
+					</row>
+					<row>
+						<entry>MIDEARTH&lt;1b&gt;</entry>
+						<entry>Qry</entry>
+						<entry>84</entry>
+						<entry>300 sec apart at stable operation</entry>
+					</row>
+					<row>
+						<entry>__MSBROWSE__</entry>
+						<entry>Reg</entry>
+						<entry>8</entry>
+						<entry>Registered after winning election to Browse Master</entry>
+					</row>
+					<row>
+						<entry>JHT&lt;03&gt;</entry>
+						<entry>Reg</entry>
+						<entry>8</entry>
+						<entry>4 x 2. This is the name of the user that logged onto Windows</entry>
+					</row>
+					<row>
+						<entry>Host Announcement WINEPRESSME</entry>
+						<entry>Ann</entry>
+						<entry>2</entry>
+						<entry>Observed at 10 sec</entry>
+					</row>
+					<row>
+						<entry>Domain/Workgroup Announcement MIDEARTH</entry>
+						<entry>Ann</entry>
+						<entry>18</entry>
+						<entry>300 sec apart at stable operation</entry>
+					</row>
+					<row>
+						<entry>Local Master Announcement WINEPRESSME</entry>
+						<entry>Ann</entry>
+						<entry>18</entry>
+						<entry>300 sec apart at stable operation</entry>
+					</row>
+					<row>
+						<entry>Get Backup List Request</entry>
+						<entry>Qry</entry>
+						<entry>12</entry>
+						<entry>6 x 2 early in startup, 0.5 sec apart</entry>
+					</row>
+					<row>
+						<entry>Browser Election Request</entry>
+						<entry>Ann</entry>
+						<entry>10</entry>
+						<entry>5 x 2 early in startup</entry>
+					</row>
+					<row>
+						<entry>Request Announcement WINEPRESSME</entry>
+						<entry>Ann</entry>
+						<entry>4</entry>
+						<entry>Early in startup</entry>
+					</row>
+				</tbody>
+			</tgroup>
+		</table>
+
+	  <para><indexterm>
+	      <primary>election</primary>
+	    </indexterm><indexterm>
+	      <primary>browse master</primary>
+	    </indexterm>
+		From the packet trace, it should be noted that no messages were propagated over TCP/IP;
+		all messages employed UDP/IP.  When steady-state operation has been achieved, there is a cycle
+		of various announcements, re-election of a browse master, and name queries. These create
+		the symphony of announcements by which network browsing is made possible.
+		</para>
+
+	  <para><indexterm>
+	      <primary>CIFS</primary>
+	    </indexterm>
+		For detailed information regarding the precise behavior of the CIFS/SMB protocols,
+		refer to the book <quote>Implementing CIFS: The Common Internet File System,</quote>
+		by Christopher Hertel, (Prentice Hall PTR, ISBN: 013047116X).
+		</para>
+
+		</sect3>
+
+	</sect2>
+
+	<sect2 id="secondmachine">
+	<title>Second Machine Startup Broadcast Interaction</title>
+
+	<para>
+	At this time, the machine you used to capture the single-system startup trace should still be running.
+	The objective of this task is to identify the interaction of two machines in respect to broadcast activity.
+	</para>
+
+	<procedure>
+	<title>Monitoring of Second Machine Activity</title>
+
+		<step><para>
+		On the machine from which network activity will be monitored (using <command>Wireshark</command>),
+		launch <command>Wireshark</command> and click
+			<menuchoice>
+				<guimenu>Capture</guimenu>
+				<guimenuitem>Start</guimenuitem>
+			</menuchoice>.
+		</para>
+
+		<para>
+		Click:
+		<orderedlist>
+			<listitem><para>Update list of packets in real time</para></listitem>
+			<listitem><para>Automatic scrolling in live capture</para></listitem>
+			<listitem><para>Enable MAC name resolution</para></listitem>
+			<listitem><para>Enable network name resolution</para></listitem>
+			<listitem><para>Enable transport name resolution</para></listitem>
+		</orderedlist>
+		Click <guibutton>OK</guibutton>.
+		</para></step>
+
+		<step><para>
+		Start the second Windows 9x/Me machine. Let it run for 15 to 20 minutes. While monitoring, do not press
+		any keyboard keys, do not click any on-screen icons or menus, and do not answer any dialog boxes.
+		</para></step>
+
+		<step><para>
+		At the conclusion of the capture time, stop the capture. Be sure to save the captured data so you
+		can examine the network data capture again at a later date should that be necessary.
+		</para></step>
+
+		<step><para>
+		Analyze the capture trace, taking note of the transport protocols used, the types of messages observed,
+		and what interaction took place between the two machines. Leave both machines running for the next task.
+		</para></step>
+	</procedure>
+
+		<sect3>
+		<title>Findings</title>
+
+		<para>
+		<link linkend="capsstats02"/> summarizes capture statistics observed. As in the previous case,
+		all announcements used UDP/IP broadcasts. Also, as was observed with the last example, the second
+		Windows 9x/Me machine broadcasts its name on startup to ensure that there exists no name clash
+		(i.e., the name is already registered by another machine) on the network segment. Those wishing
+		to explore the inner details of the precise mechanism of how this functions should refer to
+		<quote>Implementing CIFS: The Common Internet File System.</quote>
+		</para>
+
+		<table id="capsstats02">
+                        <title>Second Machine (Windows 98) &smbmdash; Capture Statistics</title>
+                        <tgroup cols="4">
+                                <colspec align="left" colwidth="3*"/>
+                                <colspec align="center"/>
+                                <colspec align="center"/>
+                                <colspec align="left" colwidth="3*"/>
+                                <thead>
+                                        <row>
+                                                <entry>Message</entry>
+                                                <entry>Type</entry>
+                                                <entry>Num</entry>
+                                                <entry>Notes</entry>
+                                        </row>
+                                </thead>
+                                <tbody>
+                                        <row>
+                                                <entry>MILGATE98&lt;00&gt;</entry>
+                                                <entry>Reg</entry>
+                                                <entry>8</entry>
+                                                <entry>4 lots of 2, 0.6 sec apart</entry>
+                                        </row>
+                                        <row>
+                                                <entry>MILGATE98&lt;03&gt;</entry>
+                                                <entry>Reg</entry>
+                                                <entry>8</entry>
+                                                <entry>4 lots of 2, 0.6 sec apart</entry>
+                                        </row>
+                                        <row>
+                                                <entry>MILGATE98&lt;20&gt;</entry>
+                                                <entry>Reg</entry>
+                                                <entry>8</entry>
+                                                <entry>4 lots of 2, 0.75 sec apart</entry>
+                                        </row>
+                                        <row>
+                                                <entry>MIDEARTH&lt;00&gt;</entry>
+                                                <entry>Reg</entry>
+                                                <entry>8</entry>
+                                                <entry>4 lots of 2, 0.75 sec apart</entry>
+                                        </row>
+                                        <row>
+                                                <entry>MIDEARTH&lt;1d&gt;</entry>
+                                                <entry>Reg</entry>
+                                                <entry>8</entry>
+                                                <entry>4 lots of 2, 0.75 sec apart</entry>
+                                        </row>
+                                        <row>
+                                                <entry>MIDEARTH&lt;1e&gt;</entry>
+                                                <entry>Reg</entry>
+                                                <entry>8</entry>
+                                                <entry>4 lots of 2, 0.75 sec apart</entry>
+                                        </row>
+                                        <row>
+                                                <entry>MIDEARTH&lt;1b&gt;</entry>
+                                                <entry>Qry</entry>
+                                                <entry>18</entry>
+                                                <entry>900 sec apart at stable operation</entry>
+                                        </row>
+                                        <row>
+                                                <entry>JHT&lt;03&gt;</entry>
+                                                <entry>Reg</entry>
+                                                <entry>2</entry>
+                                                <entry>This is the name of the user that logged onto Windows</entry>
+                                        </row>
+                                        <row>
+                                                <entry>Host Announcement MILGATE98</entry>
+                                                <entry>Ann</entry>
+                                                <entry>14</entry>
+                                                <entry>Every 120 sec</entry>
+                                        </row>
+                                        <row>
+                                                <entry>Domain/Workgroup Announcement MIDEARTH</entry>
+                                                <entry>Ann</entry>
+                                                <entry>6</entry>
+                                                <entry>900 sec apart at stable operation</entry>
+                                        </row>
+                                        <row>
+                                                <entry>Local Master Announcement WINEPRESSME</entry>
+                                                <entry>Ann</entry>
+                                                <entry>6</entry>
+                                                <entry>Insufficient detail to determine frequency</entry>
+                                        </row>
+				</tbody>
+			</tgroup>
+		</table>
+
+		<para>
+	    	<indexterm><primary>host announcement</primary></indexterm>
+		<indexterm><primary>Local Master Announcement</primary></indexterm>
+		<indexterm><primary>Workgroup Announcement</primary></indexterm>
+		Observation of the contents of Host Announcements, Domain/Workgroup Announcements,
+		and Local Master Announcements is instructive. These messages convey a significant
+		level of detail regarding the nature of each machine that is on the network. An example
+		dissection of a Host Announcement is given in <link linkend="hostannounce"/>.
+		</para>
+
+
+		<figure id="hostannounce">
+			<title>Typical Windows 9x/Me Host Announcement</title>
+			<imagefile scale="41">HostAnnouncment</imagefile>
+		</figure>
+		</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Simple Windows Client Connection Characteristics</title>
+
+	<para>
+	The purpose of this exercise is to discover how Microsoft Windows clients create (establish)
+	connections with remote servers. The methodology involves analysis of a key aspect of how
+	Windows clients access remote servers: the session setup protocol.
+	</para>
+
+	<procedure>
+	<title>Client Connection Exploration Steps</title>
+
+		<step><para>
+		Configure a Windows 9x/Me machine (MILGATE98) with a share called <constant>Stuff</constant>.
+		Create a <parameter>Full Access</parameter> control password on this share.
+		</para></step>
+
+		<step><para>
+		Configure another Windows 9x/Me machine (WINEPRESSME) as a client. Make sure that it exports
+		no shared resources.
+		</para></step>
+
+		<step><para>
+		Start both Windows 9x/Me machines and allow them to stabilize for 10 minutes. Log on to both
+		machines using a user name (JHT) of your choice. Wait approximately 2 minutes before proceeding.
+		</para></step>
+
+		<step><para>
+		Start Wireshark (or the network sniffer of your choice).
+		</para></step>
+
+		<step><para>
+		From the WINEPRESSME machine, right-click <guimenu>Network Neighborhood</guimenu>, select
+		<guimenuitem>Explore</guimenuitem>, select
+		<menuchoice>
+			<guimenuitem>My Network Places</guimenuitem>
+			<guimenuitem>Entire Network</guimenuitem>
+			<guimenuitem>MIDEARTH</guimenuitem>
+			<guimenuitem>MILGATE98</guimenuitem>
+			<guimenuitem>Stuff</guimenuitem>
+		</menuchoice>.
+		Enter the password you set for the <constant>Full Control</constant> mode for the
+		<constant>Stuff</constant> share.
+		</para></step>
+
+		<step><para>
+		When the share called <constant>Stuff</constant> is being displayed, stop the capture.
+		Save the captured data in case it is needed for later analysis.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>session setup</primary></indexterm>
+		From the top of the packets captured, scan down to locate the first packet that has
+		interpreted as <constant>Session Setup AndX, User: anonymous; Tree Connect AndX,
+		Path: \\MILGATE98\IPC$</constant>.
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>Session Setup</primary>
+	      </indexterm><indexterm>
+		<primary>Tree Connect</primary>
+	      </indexterm>
+		In the dissection (analysis) panel, expand the <constant>SMB, Session Setup AndX Request,
+		and Tree Connect AndX Request</constant>. Examine both operations. Identify the name of
+		the user Account and what password was used. The Account name should be empty.
+		This is a <constant>NULL</constant> session setup packet.
+		</para></step>
+
+		<step><para>
+		Return to the packet capture sequence. There will be a number of packets that have been
+		decoded of the type <constant>Session Setup AndX</constant>. Locate the last such packet
+		that was targeted at the <constant>\\MILGATE98\IPC$</constant> service.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>password length</primary></indexterm>
+		<indexterm><primary>User Mode</primary></indexterm>
+		Dissect this packet as per the previous one. This packet should have a password length
+		of 24 (characters) and should have a password field, the contents of which is a
+		long hexadecimal number. Observe the name in the Account field. This is a User Mode
+		session setup packet.
+		</para></step>
+	</procedure>
+
+		<sect3>
+		<title>Findings and Comments</title>
+
+	  	<para>
+		<indexterm><primary>IPC$</primary></indexterm>
+		The <constant>IPC$</constant> share serves a vital purpose<footnote><para>TOSHARG2, Sect 4.5.1</para></footnote>
+		in SMB/CIFS-based networking.  A Windows client connects to this resource to obtain the list of
+		resources that are available on the server. The server responds with the shares and print queues that
+		are available. In most but not all cases, the connection is made with a <constant>NULL</constant>
+		username and a <constant>NULL</constant> password.
+		</para>
+
+	  	<para>
+		<indexterm><primary>account credentials</primary></indexterm>
+		The two packets examined are material evidence of how Windows clients may
+		interoperate with Samba. Samba requires every connection setup to be authenticated using
+		valid UNIX account credentials (UID/GID). This means that even a <constant>NULL</constant>
+		session setup can be established only by automatically mapping it to a valid UNIX
+		account.
+		</para>
+
+		<para>
+	    <indexterm><primary>NULL session</primary></indexterm><indexterm>
+	      <primary>guest account</primary>
+	    </indexterm>
+	    <indexterm><primary>nobody</primary></indexterm>
+		Samba has a special name for the <constant>NULL</constant>, or empty, user account:
+		it calls it the <smbconfoption name="guest account"/>. The
+		default value of this parameter is <constant>nobody</constant>; however, this can be
+		changed to map the function of the guest account to any other UNIX identity. Some
+		UNIX administrators prefer to map this account to the system default anonymous
+		FTP account. A sample NULL Session Setup AndX packet dissection is shown in
+		<link linkend="nullconnect"/>.
+		</para>
+
+		<figure id="nullconnect">
+			<title>Typical Windows 9x/Me NULL SessionSetUp AndX Request</title>
+
+			<imagefile scale="41">NullConnect</imagefile>
+		</figure>
+
+		<para>
+	    	<indexterm><primary>nobody</primary></indexterm>
+		<indexterm><primary>/etc/passwd</primary></indexterm>
+		<indexterm><primary>guest account</primary></indexterm>
+		When a UNIX/Linux system does not have a <constant>nobody</constant> user account
+		(<filename>/etc/passwd</filename>), the operation of the <constant>NULL</constant>
+		account cannot validate and thus connections that utilize the guest account
+		fail. This breaks all ability to browse the Samba server and is a common
+		problem reported on the Samba mailing list. A sample User Mode session setup AndX
+		is shown in <link linkend="userconnect"/>.
+		</para>
+
+		<figure id="userconnect">
+			<title>Typical Windows 9x/Me User SessionSetUp AndX Request</title>
+			<imagefile scale="41">UserConnect</imagefile>
+		</figure>
+
+	 	<para>
+		<indexterm><primary>encrypted</primary></indexterm>
+		The User Mode connection packet contains the account name and the domain name.
+		The password is provided in Microsoft encrypted form, and its length is shown
+		as 24 characters. This is the length of Microsoft encrypted passwords.
+		</para>
+
+		</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Windows 200x/XP Client Interaction with Samba-3</title>
+
+	<para>
+	By now you may be asking, <quote>Why did you choose to work with Windows 9x/Me?</quote>
+	</para>
+
+	<para>
+	First, we want to demonstrate the simple case. This book is not intended to be a detailed treatise
+	on the Windows networking protocols, but rather to provide prescriptive guidance for deployment of Samba.
+	Second, by starting out with the simple protocol, it can be demonstrated that the more complex case mostly
+	follows the same principles.
+	</para>
+
+	<para>
+	The following exercise demonstrates the case that even MS Windows XP Professional with up-to-date service
+	updates also uses the <constant>NULL</constant> account, as well as user accounts. Simply follow the procedure
+	to complete this exercise.
+	</para>
+
+	<para>
+	To complete this exercise, you need a Windows XP Professional client that has been configured as
+	a domain member of either a Samba-controlled domain or a Windows NT4 or 200x Active Directory domain.
+	Here we do not provide details for how to configure this, as full coverage is provided earlier in this book.
+	</para>
+
+	<procedure>
+	<title>Steps to Explore Windows XP Pro Connection Set-up</title>
+
+		<step><para>
+		Start your domain controller. Also, start the Wireshark monitoring machine, launch Wireshark,
+		and then wait for the next step to complete.
+		</para></step>
+
+		<step><para>
+		Start the Windows XP Client and wait 5 minutes before proceeding.
+		</para></step>
+
+		<step><para>
+		On the machine from which network activity will be monitored (using <command>Wireshark</command>),
+                launch <command>Wireshark</command> and click
+                        <menuchoice>
+                                <guimenu>Capture</guimenu>
+                                <guimenuitem>Start</guimenuitem>
+                        </menuchoice>.
+                </para>
+
+                <para>
+                Click:
+                <orderedlist>
+				<listitem><para>Update list of packets in real time</para></listitem>
+				<listitem><para>Automatic scrolling in live capture</para></listitem>
+				<listitem><para>Enable MAC name resolution</para></listitem>
+				<listitem><para>Enable network name resolution</para></listitem>
+				<listitem><para>Enable transport name resolution</para></listitem>
+                </orderedlist>
+                Click <guibutton>OK</guibutton>.
+		</para></step>
+
+		<step><para>
+		On the Windows XP Professional client, press <guimenu>Ctrl-Alt-Delete</guimenu> to bring
+		up the domain logon screen. Log in using valid credentials for a domain user account.
+		</para></step>
+
+		<step><para>
+		Now proceed to connect to the domain controller as follows:
+		<menuchoice>
+			<guimenu>Start</guimenu>
+			<guimenuitem>(right-click) My Network Places</guimenuitem>
+			<guimenuitem>Explore</guimenuitem>
+			<guimenuitem>{Left Panel} [+] Entire Network</guimenuitem>
+			<guimenuitem>{Left Panel} [+] Microsoft Windows Network</guimenuitem>
+			<guimenuitem>{Left Panel} [+] Midearth</guimenuitem>
+			<guimenuitem>{Left Panel} [+] Frodo</guimenuitem>
+			<guimenuitem>{Left Panel} [+] data</guimenuitem>
+		</menuchoice>. Close the explorer window.
+		</para>
+
+		<para>
+		In this step, our domain name is <constant>Midearth</constant>, the domain controller is called
+		<constant>Frodo</constant>, and we have connected to a share called <constant>data</constant>.
+		</para></step>
+
+		<step><para>
+		Stop the capture on the <command>Wireshark</command> monitoring machine. Be sure to save the captured data
+		to a file so that you can refer to it again later.
+		</para></step>
+
+		<step><para>
+		If desired, the Windows XP Professional client and the domain controller are no longer needed for exercises
+		in this chapter.
+		</para></step>
+
+		 <step><para>
+		<indexterm><primary>NTLMSSP_AUTH</primary></indexterm>
+                <indexterm><primary>session setup</primary></indexterm>
+                From the top of the packets captured, scan down to locate the first packet that has
+                interpreted as <constant>Session Setup AndX Request, NTLMSSP_AUTH</constant>.
+                </para></step>
+
+                <step><para>
+		<indexterm><primary>GSS-API</primary></indexterm>
+		<indexterm><primary>SPNEGO</primary></indexterm>
+		<indexterm><primary>NTLMSSP</primary></indexterm>
+                In the dissection (analysis) panel, expand the <constant>SMB, Session Setup AndX Request</constant>.
+		Expand the packet decode information, beginning at the <constant>Security Blob:</constant>
+		entry. Expand the <constant>GSS-API -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP</constant>
+		keys.  This should reveal that this is a <constant>NULL</constant> session setup packet.
+		The <constant>User name: NULL</constant> so indicates. An example decode is shown in
+		<link linkend="XPCap01"/>.
+                </para></step>
+
+                <step><para>
+                Return to the packet capture sequence. There will be a number of packets that have been
+                decoded of the type <constant>Session Setup AndX Request</constant>. Click the last such packet that
+		has been decoded as <constant>Session Setup AndX Request, NTLMSSP_AUTH</constant>.
+                </para></step>
+
+                <step><para>
+		<indexterm><primary>encrypted password</primary></indexterm>
+                In the dissection (analysis) panel, expand the <constant>SMB, Session Setup AndX Request</constant>.
+                Expand the packet decode information, beginning at the <constant>Security Blob:</constant>
+                entry. Expand the <constant>GSS-API -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP</constant>
+                keys.  This should reveal that this is a <constant>User Mode</constant> session setup packet.
+                The <constant>User name: jht</constant> so indicates. An example decode is shown in
+                <link linkend="XPCap02"/>. In this case the user name was <constant>jht</constant>. This packet
+		decode includes the <constant>Lan Manager Response:</constant> and the <constant>NTLM Response:</constant>.
+		The values of these two parameters are the Microsoft encrypted password hashes: respectively, the LanMan
+		password and then the NT (case-preserving) password hash.
+                </para></step>
+
+                <step><para>
+                <indexterm><primary>password length</primary></indexterm>
+                <indexterm><primary>User Mode</primary></indexterm>
+                The passwords are 24-character hexadecimal numbers. This packet confirms that this is a User Mode
+		session setup packet.
+                </para></step>
+
+	</procedure>
+
+	<figure id="XPCap01">
+        <title>Typical Windows XP NULL Session Setup AndX Request</title>
+		<imagefile scale="50">WindowsXP-NullConnection</imagefile>
+	</figure>
+
+	<figure id="XPCap02">
+        <title>Typical Windows XP User Session Setup AndX Request</title>
+		<imagefile scale="50">WindowsXP-UserConnection</imagefile>
+	</figure>
+
+		<sect3>
+		<title>Discussion</title>
+
+	  <para><indexterm>
+	      <primary>NULL-Session</primary>
+	    </indexterm>
+		This exercise demonstrates that, while the specific protocol for the Session Setup AndX is handled
+		in a more sophisticated manner by recent MS Windows clients, the underlying rules or principles
+		remain the same. Thus it is demonstrated  that MS Windows XP Professional clients still use a
+		<constant>NULL-Session</constant> connection to query and locate resources on an advanced network
+		technology server (one using Windows NT4/200x or Samba). It also demonstrates that an authenticated
+		connection must be made before resources can be used.
+		</para>
+
+		</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Conclusions to Exercises</title>
+
+	<para>
+	In summary, the following points have been established in this chapter:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		When NetBIOS over TCP/IP protocols are enabled, MS Windows networking employs broadcast-oriented messaging protocols to provide knowledge of network services.
+		</para></listitem>
+
+		<listitem><para>
+		Network browsing protocols query information stored on browse masters that manage
+		information provided by NetBIOS Name Registrations and by way of ongoing host
+		announcements and workgroup announcements.
+		</para></listitem>
+
+		<listitem><para>
+		All Samba servers must be configured with a mechanism for mapping the <constant>NULL-Session</constant>
+		to a valid but nonprivileged UNIX system account.
+		</para></listitem>
+
+		<listitem><para>
+		The use of Microsoft encrypted passwords is built right into the fabric of Windows
+		networking operations. Such passwords cannot be provided from the UNIX <filename>/etc/passwd</filename>
+		database and thus must be stored elsewhere on the UNIX system in a manner that Samba can
+		use. Samba-2.x permitted such encrypted passwords to be stored in the <constant>smbpasswd</constant>
+		file or in an LDAP database. Samba-3 permits use of multiple <parameter>passdb backend</parameter>
+		databases in concurrent deployment. Refer to <emphasis>TOSHARG2</emphasis>, Chapter 10, <quote>Account Information Databases.</quote>
+		</para></listitem>
+	</itemizedlist>
+
+	</sect2>
+
+</sect1>
+
+<sect1 id="chap01conc">
+	<title>Dissection and Discussion</title>
+
+	<para>
+	<indexterm><primary>guest account</primary></indexterm>
+	The exercises demonstrate the use of the <constant>guest</constant> account, the way that
+	MS Windows clients and servers resolve computer names to a TCP/IP address, and how connections
+	between a client and a server are established.
+	</para>
+
+	<para>
+	Those wishing background information regarding NetBIOS name types should refer to
+	the Microsoft knowledgebase article
+	<ulink url="http://support.microsoft.com/support/kb/articles/Q102/78/8.asp">Q102878.</ulink>
+	</para>
+
+	<sect2>
+		<title>Technical Issues</title>
+
+		<para>
+		<indexterm><primary>guest account</primary></indexterm>
+		Network browsing involves SMB broadcast announcements, SMB enumeration requests,
+		connections to the <constant>IPC$</constant> share, share enumerations, and SMB connection
+		setup processes. The use of anonymous connections to a Samba server involve the use of
+		the <parameter>guest account</parameter> that must map to a valid UNIX UID.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1 id="chap01qa">
+	<title>Questions and Answers</title>
+
+	<para>
+	The questions and answers given in this section are designed to highlight important aspects of Microsoft
+	Windows networking.
+	</para>
+
+	<qandaset defaultlabel="chap01qa" type="number">
+	<qandaentry>
+	<question>
+
+		<para>
+		What is the significance of the MIDEARTH&lt;1b&gt; type query?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		<indexterm><primary>Domain Master Browser</primary><see>DMB</see></indexterm>
+		<indexterm><primary>DMB</primary></indexterm>
+		This is a broadcast announcement by which the Windows machine is attempting to
+		locate a Domain Master Browser (DMB) in the event that it might exist on the network.
+		Refer to <emphasis>TOSHARG2,</emphasis> Chapter 9, Section 9.7, <quote>Technical Overview of Browsing,</quote>
+		for details regarding the function of the DMB and its role in network browsing.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What is the significance of the MIDEARTH&lt;1d&gt; type name registration?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		<indexterm><primary>Local Master Browser</primary><see>LMB</see></indexterm>
+		<indexterm><primary>LMB</primary></indexterm>
+		This name registration records the machine IP addresses of the LMBs.
+		Network clients can query this name type to obtain a list of browser servers from the
+		master browser.
+		</para>
+
+		<para>
+		The LMB is responsible for monitoring all host announcements on the local network and for
+		collating the information contained within them. Using this information, it can provide answers to other Windows
+		network clients that request information such as:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			The list of machines known to the LMB (i.e., the browse list)
+			</para></listitem>
+
+			<listitem><para>
+			The IP addresses of all domain controllers known for the domain
+			</para></listitem>
+
+			<listitem><para>
+			The IP addresses of LMBs
+			</para></listitem>
+
+			<listitem><para>
+			The IP address of the DMB (if one exists)
+			</para></listitem>
+
+			<listitem><para>
+			The IP address of the LMB on the local segment
+			</para></listitem>
+		</itemizedlist>
+
+        </answer>
+        </qandaentry>
+
+        <qandaentry>
+        <question>
+
+                <para>
+		What is the role and significance of the &lt;01&gt;&lt;02&gt;__MSBROWSE__&lt;02&gt;&lt;01&gt;
+		name registration?
+                </para>
+
+        </question>
+        <answer>
+
+                <para>
+		<indexterm><primary>Browse Master</primary></indexterm>
+		This name is registered by the browse master to broadcast and receive domain announcements.
+		Its scope is limited to the local network segment, or subnet. By querying this name type,
+		master browsers on networks that have multiple domains can find the names of master browsers
+		for each domain.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What is the significance of the MIDEARTH&lt;1e&gt; type name registration?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		<indexterm><primary>Browser Election Service</primary></indexterm>
+		This name is registered by all browse masters in a domain or workgroup. The registration
+		name type is known as the Browser Election Service. Master browsers register themselves
+		with this name type so that DMBs can locate them to perform cross-subnet
+		browse list updates. This name type is also used to initiate elections for Master Browsers.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		<indexterm><primary>guest account</primary></indexterm>
+		What is the significance of the <parameter>guest account</parameter> in smb.conf?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		This parameter specifies the default UNIX account to which MS Windows networking
+		NULL session connections are mapped. The default name for the UNIX account used for
+		this mapping is called <constant>nobody</constant>. If the UNIX/Linux system that
+		is hosting Samba does not have a <constant>nobody</constant> account and an alternate
+		mapping has not been specified, network browsing will not work at all.
+		</para>
+
+		<para>
+		It should be noted that the <parameter>guest account</parameter> is essential to
+		Samba operation. Either the operating system must have an account called <constant>nobody</constant>
+		or there must be an entry in the &smb.conf; file with a valid UNIX account, such as
+		<smbconfoption name="guest account">ftp</smbconfoption>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Is it possible to reduce network broadcast activity with Samba-3?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		<indexterm><primary>WINS</primary></indexterm>
+		<indexterm><primary>NetBIOS</primary></indexterm>
+		Yes, there are two ways to do this. The first involves use of WINS (See <emphasis>TOSHARG2</emphasis>, Chapter 9,
+		Section 9.5, <quote>WINS &smbmdash; The Windows Inter-networking Name Server</quote>); the
+		alternate method involves disabling the use of NetBIOS over TCP/IP. This second method requires
+		a correctly configured DNS server (see <emphasis>TOSHARG2</emphasis>, Chapter 9, Section 9.3, <quote>Discussion</quote>).
+		</para>
+
+		<para>
+		<indexterm><primary>broadcast</primary></indexterm>
+		<indexterm><primary>NetBIOS</primary><secondary>Node Type</secondary></indexterm>
+		<indexterm><primary>Hybrid</primary></indexterm>
+		The use of WINS reduces network broadcast traffic. The reduction is greatest when all network
+		clients are configured to operate in <parameter>Hybrid Mode</parameter>. This can be effected through
+		use of DHCP to set the NetBIOS node type to type 8 for all network clients. Additionally, it is
+		beneficial to configure Samba to use <smbconfoption name="name resolve order">wins host cast</smbconfoption>.
+		</para>
+
+		<note><para>
+		Use of SMB without NetBIOS is possible only on Windows 200x/XP Professional clients and servers, as
+		well as with Samba-3.
+		</para></note>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Can I just use plain-text passwords with Samba?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Yes, you can configure Samba to use plain-text passwords, though this does create a few problems.
+		</para>
+
+		<para>
+		First, the use of <filename>/etc/passwd</filename>-based plain-text passwords requires that registry
+		modifications be made on all MS Windows client machines to enable plain-text passwords support. This
+		significantly diminishes the security of MS Windows client operation. Many network administrators
+		are bitterly opposed to doing this.
+		</para>
+
+		<para>
+		Second, Microsoft has not maintained plain-text password support since the default setting was made
+		disabling this. When network connections are dropped by the client, it is not possible to re-establish
+		the connection automatically. Users need to log off and then log on again. Plain-text password support
+		may interfere with recent enhancements that are part of the Microsoft move toward a more secure computing
+		environment.
+		</para>
+
+		<para>
+		Samba-3 supports Microsoft encrypted passwords. Be advised not to reintroduce plain-text password handling.
+		Just create user accounts by running <command>smbpasswd -a 'username'</command>
+		</para>
+
+		<para>
+		It is not possible to add a user to the <parameter>passdb backend</parameter> database unless there is
+		a UNIX system account for that user. On systems that run <command>winbindd</command> to access the Samba
+		PDC/BDC to provide Windows user and group accounts, the <parameter>idmap uid, idmap gid</parameter> ranges
+		set in the &smb.conf; file provide the local UID/GIDs needed for local identity management purposes.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What parameter in the &smb.conf; file is used to enable the use of encrypted passwords?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The parameter in the &smb.conf; file that controls this behavior is known as <parameter>encrypt
+		passwords</parameter>. The default setting for this in Samba-3 is <constant>Yes (Enabled)</constant>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Is it necessary to specify <smbconfoption name="encrypt passwords">Yes</smbconfoption>
+		when Samba-3 is configured as a domain member?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		No. This is the default behavior.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Is it necessary to specify a <parameter>guest account</parameter> when Samba-3 is configured
+		as a domain member server?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Yes. This is a local function on the server. The default setting is to use the UNIX account
+		<constant>nobody</constant>. If this account does not exist on the UNIX server, then it is
+		necessary to provide a <smbconfoption name="guest account">an_account</smbconfoption>,
+		where <constant>an_account</constant> is a valid local UNIX user account.
+		</para>
+
+	</answer>
+	</qandaentry>
+	</qandaset>
+
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-DomainAppsSupport.xml b/docs-xml/Samba3-ByExample/SBE-DomainAppsSupport.xml
new file mode 100644
index 00000000000..6d144ab2e31
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-DomainAppsSupport.xml
@@ -0,0 +1,918 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<chapter id="DomApps">
+<title>Integrating Additional Services</title>
+
+	<para>
+	<indexterm><primary>authentication</primary></indexterm>
+	<indexterm><primary>backends</primary></indexterm>
+	<indexterm><primary>smbpasswd</primary></indexterm>
+	<indexterm><primary>ldapsam</primary></indexterm>
+	<indexterm><primary>Active Directory</primary></indexterm>
+	You've come a long way now. You have pretty much mastered Samba-3 for 
+	most uses it can be put to. Up until now, you have cast Samba-3 in the leading 
+	role, and where authentication was required, you have used one or another of 
+	Samba's many authentication backends (from flat text files with smbpasswd 
+	to LDAP directory integration with ldapsam). Now you can design a 
+	solution for a new Abmas business. This business is running Windows Server 
+	2003 and Active Directory, and these are to stay. It's time to master 
+	implementing Samba and Samba-supported services in a domain controlled by 
+	the latest Windows authentication technologies. Let's get started &smbmdash; this is 
+	leading edge.
+	</para>
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>
+	Abmas has continued its miraculous growth; indeed, nothing seems to be able 
+	to stop its diversification into multiple (and seemingly unrelated) fields. 
+	Its latest acquisition is Abmas Snack Foods, a big player in the snack-food 
+	business.
+	</para>
+
+	<para>
+	With this acquisition comes new challenges for you and your team. Abmas Snack 
+	Foods is a well-developed business with a huge and heterogeneous network. It 
+	already has Windows, NetWare, and Proprietary UNIX, but as yet no Samba or Linux. 
+	The network is mature and well-established, and there is no question of its chosen 
+	user authentication scheme being changed for now. You need to take a wise new 
+	approach.
+	</para>
+
+	<para>
+	You have decided to set the ball rolling by introducing Samba-3 into the network 
+	gradually, taking over key services and easing the way to a full migration and, 
+	therefore, integration into Abmas's existing business later.
+	</para>
+
+	<sect2>
+	<title>Assignment Tasks</title>
+
+		<para>
+		<indexterm><primary>web</primary><secondary>proxying</secondary></indexterm>
+		<indexterm><primary>web</primary><secondary>caching</secondary></indexterm>
+	        You've promised the skeptical Abmas Snack Foods management team 
+		that you can show them how Samba can ease itself and other Open Source 
+		technologies into their existing infrastructure and deliver sound business 
+		advantages. Cost cutting is high on their agenda (a major promise of the 
+		acquisition). You have chosen Web proxying and caching as your proving ground.
+		</para>
+
+		<para>
+		<indexterm><primary>bandwidth</primary></indexterm>
+		<indexterm><primary>Microsoft ISA</primary></indexterm>
+		Abmas Snack Foods has several thousand users housed at its head office 
+		and multiple regional offices, plants, and warehouses. A high proportion of 
+		the business's work is done online, so Internet access for most of these 
+		users is essential. All Internet access, including for all regional offices, 
+		is funneled through the head office and is the job of the (now your) networking 
+		team. The bandwidth requirements were horrific (comparable to a small ISP), and 
+		the team soon discovered proxying and caching. In fact, they became one of 
+		the earliest commercial users of Microsoft ISA.
+		</para>
+
+		<para>
+		<indexterm><primary>Active Directory</primary></indexterm>
+		<indexterm><primary>authenticated</primary></indexterm>
+		<indexterm><primary>proxy</primary></indexterm>
+		The team is not happy with ISA. Because it never lived up to its marketing promises, 
+		it underperformed and had reliability problems. You have pounced on the opportunity 
+		to show what Open Source can do. The one thing they do like, however, is ISA's 
+		integration with Active Directory. They like that their users, once logged on, 
+		are automatically authenticated against the proxy. If your alternative to ISA 
+		can operate completely seamlessly in their Active Directory domain, it will be
+		approved.
+		</para>
+
+		<para>
+		This is a hands-on exercise. You build software applications so
+		that you obtain the functionality Abmas needs.
+		</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+<title>Dissection and Discussion</title>
+
+	<para>
+	The key requirements in this business example are straightforward. You are not required 
+	to do anything new, just to replicate an existing system, not lose any existing features, 
+	and improve performance. The key points are:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Internet access for most employees
+		</para></listitem>
+		<listitem><para>
+		Distributed system to accommodate load and geographical distribution of users
+		</para></listitem>
+		<listitem><para>
+		Seamless and transparent interoperability with the existing Active Directory domain
+		</para></listitem>
+	</itemizedlist>
+
+
+	<sect2>
+		<title>Technical Issues</title>
+
+		<para>
+		<indexterm><primary>browsing</primary></indexterm>
+		<indexterm><primary>Squid proxy</primary></indexterm>
+		<indexterm><primary>proxy</primary></indexterm>
+		<indexterm><primary>authentication</primary></indexterm>
+		<indexterm><primary>Internet Explorer</primary></indexterm>
+		<indexterm><primary>winbind</primary></indexterm>
+		<indexterm><primary>NTLM</primary></indexterm>
+		<indexterm><primary>NTLM authentication daemon</primary></indexterm>
+		<indexterm><primary>authentication</primary></indexterm>
+		<indexterm><primary>daemon</primary></indexterm>
+		<indexterm><primary>Active Directory</primary></indexterm>
+		<indexterm><primary>domain</primary><secondary>Active Directory</secondary></indexterm>
+		<indexterm><primary>Kerberos</primary></indexterm><indexterm><primary>token</primary></indexterm>
+		Functionally, the user's Internet Explorer requests a browsing session with the 
+		Squid proxy, for which it offers its AD authentication token. Squid hands off 
+		the authentication request to the Samba-3 authentication helper application
+		called <command>ntlm_auth</command>. This helper is a hook into winbind, the 
+		Samba-3 NTLM authentication daemon. Winbind enables UNIX services to authenticate 
+		against Microsoft Windows domains, including Active Directory domains. As Active 
+		Directory authentication is a modified Kerberos authentication, winbind is assisted 
+		in this by local Kerberos 5 libraries configured to check passwords with the Active 
+		Directory server. Once the token has been checked, a browsing session is established. 
+		This process is entirely transparent and seamless to the user.
+		</para>
+
+		<para>
+		Enabling this consists of:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			Preparing the necessary environment using preconfigured packages
+			</para></listitem>
+
+			<listitem><para>
+			Setting up raw Kerberos authentication against the Active Directory domain
+			</para></listitem>
+
+			<listitem><para>
+			Configuring, compiling, and then installing the supporting Samba-3 components
+			</para></listitem>
+
+			<listitem><para>
+			Tying it all together
+			</para></listitem>
+		</itemizedlist>
+
+	</sect2>
+
+
+	<sect2>
+		<title>Political Issues</title>
+
+		<para>
+		You are a stranger in a strange land, and all eyes are upon you. Some would even like to see 
+		you fail. For you to gain the trust of your newly acquired IT people, it is essential that your 
+		solution does everything the old one did, but does it better in every way. Only then 
+		will the entrenched positions consider taking up your new way of doing things on a 
+		wider scale.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Implementation</title>
+
+	<para>
+	<indexterm><primary>Squid</primary></indexterm>
+	First, your system needs to be prepared and in a known good state to proceed. This consists 
+	of making sure that everything the system depends on is present and that everything that could 
+	interfere or conflict with the system is removed. You will be configuring the Squid and Samba-3 
+	packages and updating them if necessary. If conflicting packages of these programs are installed, 
+	they must be removed.
+	</para>
+
+	<para>
+	<indexterm><primary>Red Hat Linux</primary></indexterm>
+	The following packages should be available on your Red Hat Linux system:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		<indexterm><primary>krb5</primary></indexterm>
+		<indexterm><primary>Kerberos</primary></indexterm>
+		krb5-libs
+		</para></listitem>
+
+		<listitem><para>
+		krb5-devel
+		</para></listitem>
+
+		<listitem><para>
+		krb5-workstation
+		</para></listitem>
+
+		<listitem><para>
+		krb5-server
+		</para></listitem>
+
+		<listitem><para>
+		pam_krb5
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	<indexterm><primary>SUSE Linux</primary></indexterm>
+	In the case of SUSE Linux, these packages are called:
+	</para>
+
+        <itemizedlist>
+                <listitem><para>
+                heimdal-lib
+                </para></listitem>
+
+                <listitem><para>
+                heimdal-devel
+                </para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>Heimdal</primary></indexterm>
+                heimdal
+                </para></listitem>
+
+                <listitem><para>
+                pam_krb5
+                </para></listitem>
+        </itemizedlist>
+
+	<para>
+	If the required packages are not present on your system, you must install
+	them from the vendor's installation media. Follow the administrative guide
+	for your Linux system to ensure that the packages are correctly updated.
+	</para>
+
+	<note><para>
+	<indexterm><primary>MS Windows Server 2003</primary></indexterm>
+	<indexterm><primary>Kerberos</primary></indexterm>
+	<indexterm><primary>MIT</primary></indexterm>
+	If the requirement is for interoperation with MS Windows Server 2003, it
+	will be necessary to ensure that you are using MIT Kerberos version 1.3.1
+	or later. Red Hat Linux 9 ships with MIT Kerberos 1.2.7 and thus requires
+	updating.
+	</para>
+
+	<para>
+	<indexterm><primary>Heimdal</primary></indexterm>
+	<indexterm><primary>SUSE Enterprise Linux Server</primary></indexterm>
+	Heimdal 0.6 or later is required in the case of SUSE Linux. SUSE Enterprise
+	Linux Server 8 ships with Heimdal 0.4. SUSE 9 ships with the necessary version.
+	</para></note>
+
+	<sect2 id="ch10-one">
+	<title>Removal of Pre-Existing Conflicting RPMs</title>
+
+	<para>
+	<indexterm><primary>Squid</primary></indexterm>
+	If Samba and/or Squid RPMs are installed, they should be updated. You can 
+	build both from source.
+	</para>
+
+	<para>
+	<indexterm><primary>rpm</primary></indexterm>
+	<indexterm><primary>samba</primary></indexterm>
+	<indexterm><primary>squid</primary></indexterm>
+	Locating the packages to be un-installed can be achieved by running:
+<screen>
+&rootprompt; rpm -qa | grep -i samba
+&rootprompt; rpm -qa | grep -i squid
+</screen>
+	The identified packages may be removed using:
+<screen>
+&rootprompt; rpm -e samba-common
+</screen>
+	</para>
+
+	<sect2>
+	<title>Kerberos Configuration</title>
+
+	<para>
+	<indexterm><primary>Kerberos</primary></indexterm>
+	<indexterm><primary>Active Directory</primary><secondary>server</secondary></indexterm>
+	<indexterm><primary>ADS</primary></indexterm>
+	<indexterm><primary>KDC</primary></indexterm>
+	The systems Kerberos installation must be configured to communicate with 
+	your primary Active Directory server (ADS KDC).
+	</para>
+
+	<para>
+	Strictly speaking, MIT Kerberos version 1.3.4 currently gives the best results, 
+	although the current default Red Hat MIT version 1.2.7 gives acceptable results 
+	unless you are using Windows 2003 servers.
+	</para>
+
+	<para>
+	<indexterm><primary>MIT</primary></indexterm>
+	<indexterm><primary>Heimdal</primary></indexterm>
+	<indexterm><primary>Kerberos</primary></indexterm>
+	<indexterm><primary>/etc/krb5.conf</primary></indexterm>
+	<indexterm><primary>DNS</primary><secondary>SRV records</secondary></indexterm>
+	<indexterm><primary>KDC</primary></indexterm>
+	<indexterm><primary>DNS</primary><secondary>lookup</secondary></indexterm>
+	Officially, neither MIT (1.3.4) nor Heimdal (0.63) Kerberos needs an <filename>/etc/krb5.conf</filename> 
+	file in order to work correctly. All ADS domains automatically create SRV records in the 
+	DNS zone <constant>Kerberos.REALM.NAME</constant> for each KDC in the realm. Since both 
+	MIT and Heimdal, KRB5 libraries default to checking for these records, so they 
+	automatically find the KDCs. In addition, <filename>krb5.conf</filename> allows 
+	specifying only a single KDC, even if there is more than one. Using the DNS lookup 
+	allows the KRB5 libraries to use whichever KDCs are available.
+	</para>
+
+	<procedure>
+	<title>Kerberos Configuration Steps</title>
+
+		<step><para>
+		<indexterm><primary>krb5.conf</primary></indexterm>
+		If you find the need to manually configure the <filename>krb5.conf</filename>, you should edit it
+		to have the contents shown in <link linkend="ch10-krb5conf"/>. The final fully qualified path for this file 
+		should be <filename>/etc/krb5.conf</filename>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Kerberos</primary></indexterm>
+		<indexterm><primary>realm</primary></indexterm>
+		<indexterm><primary>case-sensitive</primary></indexterm>
+		<indexterm><primary>KDC</primary></indexterm>
+		<indexterm><primary>synchronization</primary></indexterm>
+		<indexterm><primary>initial credentials</primary></indexterm>
+		<indexterm><primary>Clock skew</primary></indexterm>
+		<indexterm><primary>NTP</primary></indexterm>
+		<indexterm><primary>DNS</primary><secondary>lookup</secondary></indexterm>
+		<indexterm><primary>reverse DNS</primary></indexterm>
+		<indexterm><primary>NetBIOS name </primary></indexterm>
+		<indexterm><primary>/etc/hosts</primary></indexterm>
+		<indexterm><primary>mapping</primary></indexterm>
+		The following gotchas often catch people out. Kerberos is case sensitive. Your realm must
+		be in UPPERCASE, or you will get an error: <quote>Cannot find KDC for requested realm while getting
+		initial credentials</quote>.  Kerberos is picky about time synchronization. The time
+		according to your participating servers must be within 5 minutes or you get an error:
+		<quote>kinit(v5): Clock skew too great while getting initial credentials</quote>.
+		Clock skew limits are, in fact, configurable in the Kerberos protocols (the default is
+		5 minutes). A better solution is to implement NTP throughout your server network.
+		Kerberos needs to be able to do a reverse DNS lookup on the IP address of your KDC.
+		Also, the name that this reverse lookup maps to must either be the NetBIOS name of
+		the KDC (i.e., the hostname with no domain attached) or the
+		NetBIOS name followed by the realm. If all else fails, you can add a
+		<filename>/etc/hosts</filename> entry mapping the IP address of your KDC to its
+		NetBIOS name. If Kerberos cannot do this reverse lookup, you will get a local error
+		when you try to join the realm.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>kinit</primary></indexterm>
+		You are now ready to test your installation by issuing the command:
+<screen>
+&rootprompt; kinit [USERNAME@REALM]
+</screen> 
+		You are asked for your password, which you should enter. The following
+		is a typical console sequence:
+<screen>
+&rootprompt; kinit ADMINISTRATOR@LONDON.ABMAS.BIZ
+Password for ADMINISTRATOR@LONDON.ABMAS.BIZ: 
+</screen>
+		Make sure that your password is accepted by the Active Directory KDC.
+		</para></step>
+	</procedure>
+
+<example id="ch10-krb5conf">
+<title>Kerberos Configuration &smbmdash; File: <filename>/etc/krb5.conf</filename></title>
+<screen>
+[libdefaults]
+	default_realm = LONDON.ABMAS.BIZ
+
+[realms] 
+	LONDON.ABMAS.BIZ = {
+	kdc = w2k3s.london.abmas.biz
+	}
+</screen>
+</example>
+
+	<para><indexterm>
+	    <primary>klist</primary>
+	  </indexterm>
+	The command
+<screen>
+&rootprompt; klist -e 
+</screen>
+	shows the Kerberos tickets cached by the system.
+	</para>
+
+	<sect3>
+	<title>Samba Configuration</title>
+
+	<para>
+	<indexterm><primary>Active Directory</primary></indexterm>
+	Samba must be configured to correctly use Active Directory. Samba-3 must be used, since it 
+	has the necessary components to interface with Active Directory.
+	</para>
+
+	<procedure>
+	<title>Securing Samba-3 With ADS Support Steps</title>
+
+		<step><para>
+		<indexterm><primary>Red Hat Linux</primary></indexterm>
+		<indexterm><primary>Samba Tea</primary></indexterm>
+		<indexterm><primary>Red Hat Fedora Linux</primary></indexterm>
+		<indexterm><primary>MIT KRB5</primary></indexterm>
+		<indexterm><primary>ntlm_auth</primary></indexterm>
+		Download the latest stable Samba-3 for Red Hat Linux from the official Samba Team
+		<ulink url="http://ftp.samba.org">FTP site.</ulink> The official Samba Team
+		RPMs for Red Hat Fedora Linux contain the <command>ntlm_auth</command> tool
+		needed, and are linked against MIT KRB5 version 1.3.1 and therefore are ready for use.
+		</para>
+
+		<para>
+		<indexterm><primary>SerNet</primary></indexterm>
+		<indexterm><primary>RPMs</primary></indexterm>
+		The necessary, validated RPM packages for SUSE Linux may be obtained from
+		the <ulink url="ftp://ftp.sernet.de/pub/samba">SerNet</ulink> FTP site that
+		is located in Germany. All SerNet RPMs are validated, have the necessary
+		<command>ntlm_auth</command> tool, and are statically linked 
+		against suitably patched Heimdal 0.6 libraries.
+		</para></step>
+
+		<step><para>
+		Using your favorite editor, change the <filename>/etc/samba/smb.conf</filename>
+		file so it has contents similar to the example shown in <link linkend="ch10-smbconf"/>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>computer account</primary></indexterm>
+		<indexterm><primary>Active Directory</primary></indexterm>
+		<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>i
+		<indexterm><primary>Kerberos ticket</primary></indexterm>
+		<indexterm><primary>ticket</primary></indexterm>
+		Next you need to create a computer account in the Active Directory. 
+		This sets up the trust relationship needed for other clients to 
+		authenticate to the Samba server with an Active Directory Kerberos ticket. 
+		This is done with the <quote>net ads join -U [Administrator%Password]</quote>
+		command, as follows:
+<screen>
+&rootprompt; net ads join -U administrator%vulcon
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>smbd</primary></indexterm>
+		<indexterm><primary>nmbd</primary></indexterm>
+		<indexterm><primary>winbindd</primary></indexterm>
+		<indexterm><primary>Active Directory</primary></indexterm>
+		<indexterm><primary>Samba</primary></indexterm>
+		Your new Samba binaries must be started in the standard manner as is applicable
+		to the platform you are running on. Alternatively, start your Active Directory-enabled Samba with the following commands:
+<screen>
+&rootprompt; smbd -D
+&rootprompt; nmbd -D
+&rootprompt; winbindd -B
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>winbind</primary></indexterm>
+		<indexterm><primary>Active Directory</primary><secondary>domain</secondary></indexterm>
+		<indexterm><primary>wbinfo</primary></indexterm>
+		<indexterm><primary>enumerating</primary></indexterm>
+		<indexterm><primary>Active Directory</primary><secondary>tree</secondary></indexterm>
+		We now need to test that Samba is communicating with the Active 
+		Directory domain; most specifically, we want to see whether winbind 
+		is enumerating users and groups. Issue the following commands:
+<screen>
+&rootprompt; wbinfo -t
+checking the trust secret via RPC calls succeeded
+</screen>
+		This tests whether we are authenticating against Active Directory:
+<screen>
+&rootprompt; wbinfo -u
+LONDON+Administrator
+LONDON+Guest
+LONDON+SUPPORT_388945a0
+LONDON+krbtgt
+LONDON+jht
+LONDON+xjht
+</screen>
+		This enumerates all the users in your Active Directory tree:
+<screen>
+&rootprompt; wbinfo -g
+LONDON+Domain Computers
+LONDON+Domain Controllers
+LONDON+Schema Admins
+LONDON+Enterprise Admins
+LONDON+Domain Admins
+LONDON+Domain Users
+LONDON+Domain Guests
+LONDON+Group Policy Creator Owners
+LONDON+DnsUpdateProxy
+</screen>
+		This enumerates all the groups in your Active Directory tree.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Squid</primary></indexterm>
+		<indexterm><primary>ntlm_auth</primary></indexterm>
+		Squid uses the <command>ntlm_auth</command> helper build with Samba-3.
+		You may test <command>ntlm_auth</command> with the command:
+<screen>
+&rootprompt; /usr/bin/ntlm_auth --username=jht
+password: XXXXXXXX
+</screen>
+		You are asked for your password, which you should enter. You are rewarded with:
+<screen>
+&rootprompt; NT_STATUS_OK: Success (0x0)
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>ntlm_auth</primary></indexterm>
+		<indexterm><primary>authenticate</primary></indexterm>
+		<indexterm><primary>winbind</primary></indexterm>
+		<indexterm><primary>privileged pipe</primary></indexterm>
+		<indexterm><primary>squid</primary></indexterm>
+		<indexterm><primary>chgrp</primary></indexterm>
+		<indexterm><primary>chmod</primary></indexterm>
+		<indexterm><primary>failure</primary></indexterm>
+		The <command>ntlm_auth</command> helper, when run from a command line as the user 
+		<quote>root</quote>, authenticates against your Active Directory domain (with 
+		the aid of winbind). It manages this by reading from the winbind privileged pipe. 
+		Squid is running with the permissions of user <quote>squid</quote> and group 
+		<quote>squid</quote> and is not able to do this unless we make a vital change. 
+		Squid cannot read from the winbind privilege pipe unless you change the 
+		permissions of its directory. This is the single biggest cause of failure in the 
+		whole process. Remember to issue the following command (for Red Hat Linux):
+<screen>
+&rootprompt; chgrp squid /var/cache/samba/winbindd_privileged
+&rootprompt; chmod 750 /var/cache/samba/winbindd_privileged
+</screen>
+		For SUSE Linux 9, execute the following:
+<screen>
+&rootprompt; chgrp squid /var/lib/samba/winbindd_privileged
+&rootprompt; chmod 750 /var/lib/samba/winbindd_privileged
+</screen>
+		</para></step>
+
+	</procedure>
+	</sect3>
+
+	<sect3>
+	<title>NSS Configuration</title>
+
+	<para>
+	<indexterm><primary>NSS</primary></indexterm>
+	<indexterm><primary>winbind</primary></indexterm>
+	<indexterm><primary>authentication</primary></indexterm>
+	For Squid to benefit from Samba-3, NSS must be updated to allow winbind as a valid route to user authentication.
+	</para>
+
+	<para>
+	Edit your <filename>/etc/nsswitch.conf</filename> file so it has the parameters shown
+	in <link linkend="ch10-etcnsscfg"/>.
+	</para>
+
+<example id="ch10-smbconf">
+<title>Samba Configuration &smbmdash; File: <filename>/etc/samba/smb.conf</filename></title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">LONDON</smbconfoption>
+<smbconfoption name="netbios name">W2K3S</smbconfoption>
+<smbconfoption name="realm">LONDON.ABMAS.BIZ</smbconfoption>
+<smbconfoption name="security">ads</smbconfoption>
+<smbconfoption name="encrypt passwords">yes</smbconfoption>
+<smbconfoption name="password server">w2k3s.london.abmas.biz</smbconfoption>
+
+<smbconfcomment>separate domain and username with '/', like DOMAIN/username</smbconfcomment>
+<smbconfoption name="winbind separator">/</smbconfoption>
+
+<smbconfcomment>use UIDs from 10000 to 20000 for domain users</smbconfcomment>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfcomment>use GIDs from 10000 to 20000 for domain groups</smbconfcomment>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+
+<smbconfcomment>allow enumeration of winbind users and groups</smbconfcomment>
+<smbconfoption name="winbind enum users">yes</smbconfoption>
+<smbconfoption name="winbind enum groups">yes</smbconfoption>
+<smbconfoption name="winbind user default domain">yes</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch10-etcnsscfg">
+<title>NSS Configuration File Extract &smbmdash; File: <filename>/etc/nsswitch.conf</filename></title>
+<screen>
+passwd: files winbind
+shadow: files
+group: files winbind
+</screen>
+</example>
+
+	</sect3>
+
+	<sect3>
+	<title>Squid Configuration</title>
+
+	<para>
+	<indexterm><primary>Squid</primary></indexterm>
+	<indexterm><primary>Active Directory</primary><secondary>authentication</secondary></indexterm>
+	Squid must be configured correctly to interact with the Samba-3 
+	components that handle Active Directory authentication.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Configuration</title></sect2>
+
+	<procedure>
+	<title>Squid Configuration Steps</title>
+
+		<step><para>
+		<indexterm><primary>SUSE Linux</primary></indexterm>
+		<indexterm><primary>Squid</primary> </indexterm>
+		<indexterm><primary>helper agent</primary></indexterm>
+		If your Linux distribution is SUSE Linux 9, the version of Squid 
+		supplied is already enabled to use the winbind helper agent. You
+		can therefore omit the steps that would build the Squid binary
+		programs.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>nobody</primary></indexterm>
+		<indexterm><primary>squid</primary></indexterm>
+		<indexterm><primary>rpms</primary></indexterm>
+		<indexterm><primary>/etc/passwd</primary></indexterm>
+		<indexterm><primary>/etc/group</primary></indexterm>
+		Squid, by default, runs as the user <constant>nobody</constant>. You need to 
+		add a system user <constant>squid</constant> and a system group 
+		<constant>squid</constant> if they are not set up already (if the default 
+		Red Hat squid rpms were installed, they will be).  Set up a 
+		<constant>squid</constant> user in <filename>/etc/passwd</filename> 
+		and a <constant>squid</constant> group in <filename>/etc/group</filename> if these aren't there already.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>permissions</primary></indexterm>
+		<indexterm><primary>chown</primary></indexterm>
+		You now need to change the permissions on Squid's <constant>var</constant>
+		directory.  Enter the following command:
+<screen>
+&rootprompt; chown -R squid /var/cache/squid
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>logging</primary></indexterm>
+		<indexterm><primary>Squid</primary></indexterm>
+		Squid must also have control over its logging. Enter the following commands:
+<screen>
+&rootprompt; chown -R chown squid:squid /var/log/squid
+&rootprompt; chmod 770 /var/log/squid
+</screen>
+		</para></step>
+
+		<step><para>
+		Finally, Squid must be able to write to its disk cache!
+		Enter the following commands:
+<screen>
+&rootprompt; chown -R chown squid:squid /var/cache/squid
+&rootprompt; chmod 770 /var/cache/squid
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/squid/squid.conf</primary></indexterm>
+		The <filename>/etc/squid/squid.conf</filename> file must be edited to include the lines from 
+		<link linkend="etcsquidcfg"/> and <link linkend="etcsquid2"/>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>cache directories</primary></indexterm>
+		You must create Squid's cache directories before it may be run.  Enter the following command: 
+<screen>
+&rootprompt; squid -z
+</screen>
+		</para></step>
+
+		<step><para>
+		Finally, start Squid and enjoy transparent Active Directory authentication.
+		Enter the following command:
+<screen>
+&rootprompt; squid
+</screen>
+		</para></step>
+	</procedure>
+
+<example id="etcsquidcfg">
+<title>Squid Configuration File Extract &smbmdash; <filename>/etc/squid.conf</filename> [ADMINISTRATIVE PARAMETERS Section]</title>
+<screen>
+	cache_effective_user squid
+	cache_effective_group squid
+</screen>
+</example>
+
+<example id="etcsquid2">
+<title>Squid Configuration File extract &smbmdash; File: <filename>/etc/squid.conf</filename> [AUTHENTICATION PARAMETERS Section]</title>
+<screen>
+	auth_param ntlm program /usr/bin/ntlm_auth \
+                                --helper-protocol=squid-2.5-ntlmssp
+	auth_param ntlm children 5
+	auth_param ntlm max_challenge_reuses 0
+	auth_param ntlm max_challenge_lifetime 2 minutes
+	auth_param basic program /usr/bin/ntlm_auth \
+                                --helper-protocol=squid-2.5-basic
+	auth_param basic children 5
+	auth_param basic realm Squid proxy-caching web server
+	auth_param basic credentialsttl 2 hours
+	acl AuthorizedUsers proxy_auth REQUIRED
+	http_access allow all AuthorizedUsers
+</screen>
+</example>
+
+	</sect2>
+
+	<sect2>
+		<title>Key Points Learned</title>
+
+		<para>
+		<indexterm><primary>Web browsers</primary></indexterm>
+		<indexterm><primary>services</primary></indexterm>
+		<indexterm><primary>authentication protocols</primary></indexterm>
+		<indexterm><primary>Web</primary><secondary>proxy</secondary><tertiary>access</tertiary></indexterm>
+		<indexterm><primary>NTLMSSP</primary></indexterm>
+		Microsoft Windows networking protocols permeate the spectrum of technologies that Microsoft
+		Windows clients use, even when accessing traditional services such as Web browsers. Depending 
+		on whom you discuss this with, this is either good or bad. No matter how you might evaluate this,
+		the use of NTLMSSP as the authentication protocol for Web proxy access has some advantages over
+		the cookie-based authentication regime used by all competing browsers. It is Samba's implementation
+		of NTLMSSP that makes it attractive to implement the solution that has been demonstrated in this chapter.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	<indexterm><primary>ntlm_auth</primary></indexterm>
+	<indexterm><primary>SambaXP conference</primary></indexterm>
+	<indexterm><primary>Goettingen</primary></indexterm>
+	<indexterm><primary>Italian</primary></indexterm>
+	The development of the <command>ntlm_auth</command> module was first discussed in many Open Source circles
+	in 2002. At the SambaXP conference in Goettingen, Germany, Mr. Francesco Chemolli demonstrated the use of 
+	<command>ntlm_auth</command> during one of the late developer meetings that took place. Since that time, the 
+	adoption of <command>ntlm_auth</command> has spread considerably.
+	</para>
+
+	<para>
+	The largest report from a site that uses Squid with <command>ntlm_auth</command>-based authentication
+	support uses a dual processor server that has 2 GB of memory. It provides Web and FTP proxy services for 10,000
+	users. Approximately 2,000 of these users make heavy use of the proxy services. According to the source, who
+	wishes to remain anonymous, the sustained transaction load on this server hovers around 140 hits/sec. The following
+	comments were made with respect to questions regarding the performance of this installation:
+	</para>
+
+	<blockquote><para>
+	[In our] EXTREMELY optimized environment . . . [the] performance impact is almost [nothing]. The <quote>almost</quote> 
+	part is due to the brain damage of the ntlm-over-http protocol definition. Suffice to say that its worst-case 
+	scenario triples the number of hits needed to perform the same transactions versus basic or digest auth[entication].
+	</para></blockquote>
+
+	<para>
+	You would be well-advised to recognize that all cache-intensive proxying solutions demand a lot of memory.
+	Make certain that your Squid proxy server is equipped with sufficient memory to permit all proxy operations to run 
+	out of memory without invoking the overheads involved in the use of memory that has to be swapped to disk.
+	</para>
+
+	<qandaset defaultlabel="chap10bqa" type="number">
+	<qandaentry>
+	<question>
+
+		<para>
+		What does Samba have to do with Web proxy serving?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		<indexterm><secondary>transparent inter-operability</secondary></indexterm>
+		<indexterm><primary>Windows clients</primary></indexterm>
+		<indexterm><primary>network</primary><secondary>services</secondary></indexterm>
+		<indexterm><primary>authentication</primary></indexterm>
+		<indexterm><primary>wrapper</primary></indexterm>
+		To provide transparent interoperability between Windows clients and the network services
+		that are used from them, Samba had to develop tools and facilities that deliver that feature. The benefit
+		of Open Source software is that it can readily be reused. The current <command>ntlm_auth</command>
+		module is basically a wrapper around authentication code from the core of the Samba project.
+		</para>
+
+		<para>
+		<indexterm><primary>plain-text</primary></indexterm>
+		<indexterm><primary>authentication</primary><secondary>plain-text</secondary></indexterm>
+		<indexterm><primary>Web</primary><secondary>proxy</secondary></indexterm>
+		<indexterm><primary>FTP</primary><secondary>proxy</secondary></indexterm>
+		<indexterm><primary>NTLMSSP</primary></indexterm>
+		<indexterm><primary>logon credentials</primary></indexterm>
+		<indexterm><primary>Windows explorer</primary></indexterm>
+		<indexterm><primary>Internet Information Server</primary></indexterm>
+		<indexterm><primary>Apache Web server</primary></indexterm>
+		The <command>ntlm_auth</command> module supports basic plain-text authentication and NTLMSSP 
+		protocols. This module makes it possible for Web and FTP proxy requests to be authenticated without
+		the user being interrupted via his or her Windows logon credentials. This facility is available with
+		MS Windows Explorer and is one of the key benefits claimed for Microsoft Internet Information Server.
+		There are a few open source initiatives to provide support for these protocols in the Apache Web server
+		also.
+		</para>
+
+		<para>
+		<indexterm><primary>wrapper</primary></indexterm>
+		The short answer is that by adding a wrapper around key authentication components of Samba, other
+		projects (like Squid) can benefit from the labors expended in meeting user interoperability needs.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What other services does Samba provide?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		<indexterm><primary>winbindd</primary></indexterm>
+		<indexterm><primary>Identity resolver</primary></indexterm>
+		<indexterm><primary>daemon</primary></indexterm>
+		<indexterm><primary>smbd</primary></indexterm>
+		<indexterm><primary>file and print server</primary></indexterm>
+		Samba-3 is a file and print server. The core components that provide this functionality are <command>smbd</command>,
+		<command>nmbd</command>, and the identity resolver daemon, <command>winbindd</command>.
+		</para>
+
+		<para>
+		<indexterm><primary>SMB/CIFS</primary></indexterm>
+		<indexterm><primary>smbclient</primary></indexterm>
+		Samba-3 is an SMB/CIFS client. The core component that provides this is called <command>smbclient</command>.
+		</para>
+
+		<para>
+		<indexterm><primary>modules</primary></indexterm>
+		<indexterm><primary>utilities</primary></indexterm>
+		<indexterm><primary>validation</primary></indexterm>
+		<indexterm><primary>inter-operability</primary></indexterm>
+		<indexterm><primary>authentication</primary></indexterm>
+		Samba-3 includes a number of helper tools, plug-in modules, utilities, and test and validation facilities.
+		Samba-3 includes glue modules that help provide interoperability between MS Windows clients and UNIX/Linux
+		servers and clients. It includes Winbind agents that make it possible to authenticate UNIX/Linux access attempts
+		as well as logins to an SMB/CIFS authentication server backend. Samba-3 includes name service switch (NSS) modules
+		to permit identity resolution via SMB/CIFS servers (Windows NT4/200x, Samba, and a host of other commercial
+		server products).
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Does use of Samba (<command>ntlm_auth</command>) improve the performance of Squid?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Not really. Samba's <command>ntlm_auth</command> module handles only authentication. It requires that
+		Squid make an external call to <command>ntlm_auth</command> and therefore actually incurs a
+		little more overhead. Compared with the benefit obtained, that overhead is well worth enduring. Since
+		Squid is a proxy server, and proxy servers tend to require lots of memory, it is good advice to provide
+		sufficient memory when using Squid. Just add a little more to accommodate <command>ntlm_auth</command>.
+		</para>
+
+	</answer>
+	</qandaentry>
+	</qandaset>
+
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-HighAvailability.xml b/docs-xml/Samba3-ByExample/SBE-HighAvailability.xml
new file mode 100644
index 00000000000..eb203f0a331
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-HighAvailability.xml
@@ -0,0 +1,701 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<chapter id="HA">
+<title>Performance, Reliability, and Availability</title>
+
+	<para>
+	<indexterm><primary>performance</primary></indexterm>
+	<indexterm><primary>reliability</primary></indexterm>
+	<indexterm><primary>availability</primary></indexterm>
+	Well, you have reached one of the last chapters of this book. It is customary to attempt
+	to wrap up the theme and contents of a book in what is generally regarded as the
+	chapter that should draw conclusions. This book is a suspense thriller, and since
+	the plot of the stories told mostly lead you to bigger, better Samba-3 networking
+	solutions, it is perhaps appropriate to close this book with a few pertinent comments
+	regarding some of the things everyone can do to deliver a reliable Samba-3 network.
+	</para>
+
+	<blockquote><attribution>Anonymous</attribution><para>
+	In a world so full of noise, how can the sparrow be heard?
+	</para></blockquote>
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>
+	<indexterm><primary>clustering</primary></indexterm>
+	The sparrow is a small bird whose sounds are drowned out by the noise of the busy
+	world it lives in. Likewise, the simple steps that can be taken to improve the
+	reliability and availability of a Samba network are often drowned out by the volume
+	of discussions about grandiose Samba clustering designs. This is not intended to
+	suggest that clustering is not important, because clearly it is. This chapter does not devote
+	itself to discussion of clustering because each clustering methodology uses its own
+	custom tools and methods. Only passing comments are offered concerning these methods.
+	</para>
+
+	<para>
+	<indexterm><primary>cluster</primary></indexterm>
+	<indexterm><primary>samba cluster</primary></indexterm>
+	<indexterm><primary>scalability</primary></indexterm>
+<ulink url="http://www.google.com/search?hl=en&amp;lr=&amp;ie=ISO-8859-1&amp;q=samba+cluster&amp;btnG=Google+Search">A search</ulink> 
+	for <quote>samba cluster</quote> produced 71,600 hits. And a search for <quote>highly available samba</quote>
+	and <quote>highly available windows</quote> produced an amazing number of references.
+	It is clear from the resources on the Internet that Windows file and print services 
+	availability, reliability, and scalability are of vital interest to corporate network users.
+	</para>
+
+	<para>
+	<indexterm><primary>performance</primary></indexterm>
+	So without further background, you can review a checklist of simple steps that
+	can be taken to ensure acceptable network performance while keeping costs of ownership
+	well under control.
+	</para>
+
+</sect1>
+
+<sect1>
+	<title>Dissection and Discussion</title>
+
+	<para>
+	<indexterm><primary>simple</primary></indexterm>
+	<indexterm><primary>complexities</primary></indexterm>
+	If it is your purpose to get the best mileage out of your Samba servers, there is one rule that
+	must be obeyed. If you want the best, keep your implementation as simple as possible. You may
+	well be forced to introduce some complexities, but you should do so only as a last resort.
+	</para>
+
+	<para>
+	Simple solutions are likely to be easier to get right than are complex ones. They certainly
+	make life easier for your successor. Simple implementations can be more readily audited than can
+	complex ones. 
+	</para>
+
+	<para>
+	<indexterm><primary>broken behavior</primary></indexterm>
+	<indexterm><primary>poor performance</primary></indexterm>
+	Problems reported by users fall into three categories: configurations that do not work, those 
+	that have broken behavior, and poor performance. The term <emphasis>broken behavior</emphasis>
+	means that the function of a particular Samba component appears to work sometimes, but not at
+	others. The resulting intermittent operation is clearly unacceptable. An example of 
+	<emphasis>broken behavior</emphasis> known to many Windows networking users occurs when the
+	list of Windows machines in MS Explorer changes, sometimes listing machines that are running
+	and at other times not listing them even though the machines are in use on the network.
+	</para>
+
+	<para>
+	<indexterm><primary>smbfs</primary></indexterm>
+	<indexterm><primary>smbmnt</primary></indexterm>
+	<indexterm><primary>smbmount</primary></indexterm>
+	<indexterm><primary>smbumnt</primary></indexterm>
+	<indexterm><primary>smbumount</primary></indexterm>
+	<indexterm><primary>front-end</primary></indexterm>
+	A significant number of reports concern problems with the <command>smbfs</command> file system
+	driver that is part of the Linux kernel, not part of Samba. Users continue to interpret that
+	<command>smbfs</command> is part of Samba, simply because Samba includes the front-end tools
+	that are used to manage <command>smbfs</command>-based file service connections. So, just
+	for the record, the tools <command>smbmnt</command>, <command>smbmount</command>,
+	<command>smbumount</command>, and <command>smbumnt</command> are front-end
+	facilities to core drivers that are supplied as part of the Linux kernel. These tools share a
+	common infrastructure with some Samba components, but they are not maintained as part of
+	Samba and are really foreign to it.
+	</para>
+
+	<para>
+	<indexterm><primary>cifsfs</primary></indexterm>
+	The new project, <command>cifsfs</command>, is destined to replace <command>smbfs</command>.
+	It, too, is not part of Samba, even though one of the Samba Team members is a prime mover in
+	this project.
+	</para>
+
+	<para>
+	Table 13.1 lists typical causes of:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>Not Working (NW)</para></listitem>
+		<listitem><para>Broken Behavior (BB)</para></listitem>
+		<listitem><para>Poor Performance (PP)</para></listitem>
+	</itemizedlist>
+
+
+	<table id="ProbList">
+		<title>Effect of Common Problems</title>
+		<tgroup cols="4">
+			<colspec align="left"/>
+			<colspec align="center"/>
+			<colspec align="center"/>
+			<colspec align="center"/>
+			<thead>
+				<row>
+					<entry><para>Problem</para></entry>
+					<entry><para>NW</para></entry>
+					<entry><para>BB</para></entry>
+					<entry><para>PP</para></entry>
+				</row>
+			</thead>
+			<tbody>
+				<row>
+					<entry><para>File locking</para></entry>
+					<entry><para>-</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>-</para></entry>
+				</row>
+				<row>
+					<entry><para>Hardware problems</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+				</row>
+				<row>
+					<entry><para>Incorrect authentication</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>-</para></entry>
+				</row>
+				<row>
+					<entry><para>Incorrect configuration</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+				</row>
+				<row>
+					<entry><para>LDAP problems</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>-</para></entry>
+				</row>
+				<row>
+					<entry><para>Name resolution</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+				</row>
+				<row>
+					<entry><para>Printing problems</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>-</para></entry>
+				</row>
+				<row>
+					<entry><para>Slow file transfer</para></entry>
+					<entry><para>-</para></entry>
+					<entry><para>-</para></entry>
+					<entry><para>X</para></entry>
+				</row>
+				<row>
+					<entry><para>Winbind problems</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>X</para></entry>
+					<entry><para>-</para></entry>
+				</row>
+			</tbody>
+		</tgroup>
+	</table>
+
+	<para>
+	<indexterm><primary>network hygiene</primary></indexterm>
+	It is obvious to all that the first requirement (as a matter of network hygiene) is to eliminate
+	problems that affect basic network operation. This book has provided sufficient working examples
+	to help you to avoid all these problems.
+	</para>
+
+</sect1>
+
+<sect1>
+	<title>Guidelines for Reliable Samba Operation</title>
+
+	<para>
+	<indexterm><primary>resilient</primary></indexterm>
+	<indexterm><primary>extreme demand</primary></indexterm>
+	Your objective is to provide a network that works correctly, can grow at all times, is resilient
+	at times of extreme demand, and can scale to meet future needs. The following subject areas provide
+	pointers that can help you today.
+	</para>
+
+	<sect2>
+	<title>Name Resolution</title>
+
+	<para>
+	There are three basic current problem areas: bad hostnames, routed networks, and network collisions.
+	These are covered in the following discussion.
+	</para>
+
+		<sect3>
+		<title>Bad Hostnames</title>
+
+		<para>
+		<indexterm><primary>DHCP</primary><secondary>client</secondary></indexterm>
+		<indexterm><primary>netbios name</primary></indexterm>
+		<indexterm><primary>localhost</primary></indexterm>
+		<indexterm><primary>/etc/hosts</primary></indexterm>
+		<indexterm><primary>NetBIOS</primary></indexterm>
+		When configured as a DHCP client, a number of Linux distributions set the system hostname
+		to <constant>localhost</constant>. If the parameter <parameter>netbios name</parameter> is not
+		specified to something other than <constant>localhost</constant>, the Samba server appears
+		in the Windows Explorer as <constant>LOCALHOST</constant>. Moreover, the entry in the <filename>/etc/hosts</filename>
+		on the Linux server points to IP address <constant>127.0.0.1</constant>. This means that
+		when the Windows client obtains the IP address of the Samba server called <constant>LOCALHOST</constant>,
+		it obtains the IP address <constant>127.0.0.1</constant> and then proceeds to attempt to
+		set up a NetBIOS over TCP/IP connection to it. This cannot work, because that IP address is
+		the local Windows machine itself. Hostnames must be valid for Windows networking to function
+		correctly.
+		</para>
+
+		<para>
+		<indexterm><primary>digits</primary></indexterm>
+		A few sites have tried to name Windows clients and Samba servers with a name that begins
+		with the digits 1-9. This does not work either because it may result in the client or
+		server attempting to use that name as an IP address.
+		</para>
+
+		<para>
+		<indexterm><primary>DNS</primary><secondary>name lookup</secondary></indexterm>
+		<indexterm><primary>resolve</primary></indexterm>
+		A Samba server called <constant>FRED</constant> in a NetBIOS domain called <constant>COLLISION</constant>
+		in a network environment that is part of the fully-qualified Internet domain namespace known
+		as <constant>parrots.com</constant>, results in DNS name lookups for <constant>fred.parrots.com</constant>
+		and <constant>collision.parrots.com</constant>. It is therefore a mistake to name the domain
+		(workgroup) <constant>collision.parrots.com</constant>, since this results in DNS lookup
+		attempts to resolve <constant>fred.parrots.com.parrots.com</constant>, which most likely
+		fails given that you probably do not have this in your DNS namespace.
+		</para>
+
+		<note><para>
+		<indexterm><primary>Active Directory</primary><secondary>realm</secondary></indexterm>
+		<indexterm><primary>ADS</primary></indexterm>
+		<indexterm><primary>DNS</primary></indexterm>
+		An Active Directory realm called <constant>collision.parrots.com</constant> is perfectly okay,
+		although it too must be capable of being resolved via DNS, something that functions correctly
+		if Windows 200x ADS has been properly installed and configured.
+		</para></note>
+
+		</sect3>
+
+		<sect3>
+		<title>Routed Networks</title>
+
+		<para>
+		<indexterm><primary>NetBIOS</primary></indexterm>
+		<indexterm><primary>UDP</primary><secondary>broadcast</secondary></indexterm>
+		<indexterm><primary>broadcast</primary></indexterm>
+		NetBIOS networks (Windows networking with NetBIOS over TCP/IP enabled) makes extensive use
+		of UDP-based broadcast traffic, as you saw during the exercises in <link linkend="primer"/>.
+		</para>
+
+		<para>
+		<indexterm><primary>routers</primary></indexterm>
+		<indexterm><primary>forwarded</primary></indexterm>
+		<indexterm><primary>multi-subnet</primary></indexterm>
+		UDP broadcast traffic is not forwarded by routers. This means that NetBIOS broadcast-based
+		networking cannot function across routed networks (i.e., multi-subnet networks) unless
+		special provisions are made:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			<indexterm><primary>LMHOSTS</primary></indexterm>
+			<indexterm><primary>remote announce</primary></indexterm>
+			<indexterm><primary>remote browse sync</primary></indexterm>
+			Either install on every Windows client an LMHOSTS file (located in the directory
+			<filename>C:\windows\system32\drivers\etc</filename>). It is also necessary to
+			add to the Samba server &smb.conf; file the parameters <parameter>remote announce</parameter>
+			and <parameter>remote browse sync</parameter>. For more information, refer to the online
+			manual page for the &smb.conf; file.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>WINS</primary><secondary>server</secondary></indexterm>
+			Or configure Samba as a WINS server, and configure all network clients to use that
+			WINS server in their TCP/IP configuration.
+			</para></listitem>
+		</itemizedlist>
+
+		<note><para>
+		<indexterm><primary>WINS</primary><secondary>name resolution</secondary></indexterm>
+		<indexterm><primary>DNS</primary></indexterm>
+		The use of DNS is not an acceptable substitute for WINS. DNS does not store specific
+		information regarding NetBIOS networking particulars that get stored in the WINS
+		name resolution database and that Windows clients require and depend on.
+		</para></note>
+
+		</sect3>
+
+		<sect3>
+		<title>Network Collisions</title>
+
+		<para>
+		<indexterm><primary>network</primary><secondary>collisions</secondary></indexterm>
+		<indexterm><primary>network</primary><secondary>timeouts</secondary></indexterm>
+		<indexterm><primary>collision rates</primary></indexterm>
+		<indexterm><primary>network</primary><secondary>load</secondary></indexterm>
+		Excessive network activity causes NetBIOS network timeouts. Timeouts may result in
+		blue screen of death (BSOD) experiences. High collision rates may be caused by excessive
+		UDP broadcast activity, by defective networking hardware, or through excessive network
+		loads (another way of saying that the network is poorly designed).
+		</para>
+
+		<para>
+		The use of WINS is highly recommended to reduce network broadcast traffic, as outlined
+		in <link linkend="primer"/>.
+		</para>
+
+		<para>
+		<indexterm><primary>netbios forwarding</primary></indexterm>
+		<indexterm><primary>broadcast storms</primary></indexterm>
+		<indexterm><primary>performance</primary></indexterm>
+		Under no circumstances should the facility be supported by many routers, known as <constant>NetBIOS
+		forwarding</constant>, unless you know exactly what you are doing. Inappropriate use of this
+		facility can result in UDP broadcast storms. In one case in 1999, a university network became
+		unusable due to NetBIOS forwarding being enabled on all routers. The problem was discovered during performance
+		testing of a Samba server. The maximum throughput on a 100-Base-T (100 MB/sec) network was
+		less than 15 KB/sec. After the NetBIOS forwarding was turned off, file transfer performance
+		immediately returned to 11 MB/sec.
+		</para>
+
+		</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Samba Configuration</title>
+
+	<para>
+	As a general rule, the contents of the &smb.conf; file should be kept as simple as possible.
+	No parameter should be specified unless you know it is essential to operation.
+	</para>
+
+	<para>
+	<indexterm><primary>document the settings</primary></indexterm>
+	<indexterm><primary>documented</primary></indexterm>
+	<indexterm><primary>optimized</primary></indexterm>
+	Many UNIX administrators like to fully document the settings in the &smb.conf; file. This is a
+	bad idea because it adds content to the file. The &smb.conf; file is re-read by every <command>smbd</command>
+	process every time the file timestamp changes (or, on systems where this does not work, every 20 seconds or so).
+	</para>
+
+	<para>
+	As the size of the &smb.conf; file grows, the risk of introducing parsing errors also increases.
+	It is recommended to keep a fully documented &smb.conf; file on hand, and then to operate Samba only
+	with an optimized file.
+	</para>
+
+	<para><indexterm>
+	    <primary>testparm</primary>
+	  </indexterm>
+	The preferred way to maintain a documented file is to call it something like <filename>smb.conf.master</filename>.
+	You can generate the optimized file by executing:
+<screen>
+&rootprompt; testparm -s smb.conf.master > smb.conf
+</screen>
+	You should carefully observe all warnings issued. It is also a good practice to execute the following
+	command to confirm correct interpretation of the &smb.conf; file contents:
+<screen>
+&rootprompt; testparm
+Load smb config files from /etc/samba/smb.conf
+Can't find include file /etc/samba/machine.
+Processing section "[homes]"
+Processing section "[print$]"
+Processing section "[netlogon]"
+Processing section "[Profiles]"
+Processing section "[printers]"
+Processing section "[media]"
+Processing section "[data]"
+Processing section "[cdr]"
+Processing section "[apps]"
+Loaded services file OK.
+'winbind separator = +' might cause problems with group membership.
+Server role: ROLE_DOMAIN_PDC
+Press enter to see a dump of your service definitions
+</screen>
+	<indexterm><primary>fatal problem</primary></indexterm>
+	You now, of course, press the enter key to complete the command, or else abort it by pressing Ctrl-C.
+	The important thing to note is the noted Server role, as well as warning messages. Noted configuration
+	conflicts must be remedied before proceeding. For example, the following error message represents a
+	common fatal problem:
+<screen>
+ERROR: both 'wins support = true' and 'wins server = &lt;server list&gt;' 
+cannot be set in the smb.conf file. nmbd will abort with this setting.
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>performance degradation</primary></indexterm>
+	<indexterm><primary>socket options</primary></indexterm>
+	<indexterm><primary>socket address</primary></indexterm>
+	There are two parameters that can cause severe network performance degradation: <parameter>socket options</parameter>
+	and <parameter>socket address</parameter>. The <parameter>socket options</parameter> parameter was often necessary
+	when Samba was used with the Linux 2.2.x kernels. Later kernels are largely self-tuning and seldom benefit from
+	this parameter being set. Do not use either parameter unless it has been proven necessary to use them.
+	</para>
+
+	<para>
+	<indexterm><primary>strict sync</primary></indexterm>
+	<indexterm><primary>sync always</primary></indexterm>
+	<indexterm><primary>severely degrade</primary></indexterm>
+	<indexterm><primary>network</primary><secondary>performance</secondary></indexterm>
+	Another &smb.conf; parameter that may cause severe network performance degradation is the 
+	<parameter>strict sync</parameter> parameter. Do not use this at all. There is no good reason
+	to use this with any modern Windows client. The <parameter>strict sync</parameter> is often
+	used with the <parameter>sync always</parameter> parameter. This, too, can severely	
+	degrade network performance, so do not set it; if you must, do so with caution.
+	</para>
+
+	<para>
+	<indexterm><primary>opportunistic locking</primary></indexterm>
+	<indexterm><primary>file caching</primary></indexterm>
+	<indexterm><primary>caching</primary></indexterm>
+	<indexterm><primary>oplocks</primary></indexterm>
+	Finally, many network administrators deliberately disable opportunistic locking support. While this
+	does not degrade Samba performance, it significantly degrades Windows client performance because
+	this disables local file caching on Windows clients and forces every file read and written to
+	invoke a network read or write call. If for any reason you must disable oplocks (opportunistic locking)
+	support, do so only on the share on which it is required. That way, all other shares can provide
+	oplock support for operations that are tolerant of it. See <link linkend="ch12dblck"/> for more
+	information.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Use and Location of BDCs</title>
+
+	<para>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>routed network</primary></indexterm>
+	<indexterm><primary>wide-area network</primary></indexterm>
+	<indexterm><primary>network segment</primary></indexterm>
+	On a network segment where there is a PDC and a BDC, the BDC carries the bulk of the network logon
+	processing. If the BDC is a heavily loaded server, the PDC carries a greater proportion of
+	authentication and logon processing. When a sole BDC on a routed network segment gets heavily
+	loaded, it is possible that network logon requests and authentication requests may be directed
+	to a BDC on a distant network segment. This significantly hinders WAN operations
+	and is undesirable.
+	</para>
+
+	<para>
+	<indexterm><primary>Domain Member</primary></indexterm>
+	<indexterm><primary>Domain Controller</primary></indexterm>
+	As a general guide, instead of adding domain member servers to a network, you would be better advised
+	to add BDCs until there are fewer than 30 Windows clients per BDC. Beyond that ratio, you should add
+	domain member servers. This practice ensures that there are always sufficient domain controllers
+	to handle logon requests and authentication traffic.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Use One Consistent Version of MS Windows Client</title>
+
+	<para>
+	Every network client has its own peculiarities. From a management perspective, it is easier to deal
+	with one version of MS Windows that is maintained to a consistent update level than it is to deal
+	with a mixture of clients.
+	</para>
+
+	<para>
+	On a number of occasions, particular Microsoft service pack updates of a Windows server or client
+	have necessitated special handling from the Samba server end. If you want to remain sane, keep you
+	client workstation configurations consistent.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>For Scalability, Use SAN-Based Storage on Samba Servers</title>
+
+	<para>
+	<indexterm><primary>SAN</primary></indexterm>
+	<indexterm><primary>synchronization</primary></indexterm>
+	Many SAN-based storage systems permit more than one server to share a common data store.
+	Use of a shared SAN data store means that you do not need to use time- and resource-hungry data 
+	synchronization techniques.
+	</para>
+
+	<para>
+	<indexterm><primary>load distribution</primary></indexterm>
+	<indexterm><primary>clustering</primary></indexterm>
+	The use of a collection of relatively low-cost front-end Samba servers that are coupled to
+	a shared backend SAN data store permits load distribution while containing costs below that
+	of installing and managing a complex clustering facility.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Distribute Network Load with MSDFS</title>
+
+	<para>
+	<indexterm><primary>MSDFS</primary></indexterm>
+	<indexterm><primary>distributed</primary></indexterm>
+	Microsoft DFS (distributed file system) technology has been implemented in Samba. MSDFS permits
+	data to be accessed from a single share and yet to actually be distributed across multiple actual
+	servers. Refer to <emphasis>TOSHARG2</emphasis>, Chapter 19, for information regarding
+	implementation of an MSDFS installation.
+	</para>
+
+	<para>
+	<indexterm><primary>front-end</primary><secondary>server</secondary></indexterm>
+	<indexterm><primary>MSDFS</primary></indexterm>
+	The combination of multiple backend servers together with a front-end server and use of MSDFS
+	can achieve almost the same as you would obtain with a clustered Samba server.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</title>
+
+	<para>
+	<indexterm><primary>replicate</primary></indexterm>
+	<indexterm><primary>rsync</primary></indexterm>
+	<indexterm><primary>wide-area network</primary></indexterm>
+	Consider using <command>rsync</command> to replicate data across the WAN during times
+	of low utilization. Users can then access the replicated data store rather than needing to do so
+	across the WAN. This works best for read-only data, but with careful planning can be
+	implemented so that modified files get replicated back to the point of origin. Be careful with your
+	implementation if you choose to permit modification and return replication of the modified file;
+	otherwise, you may inadvertently overwrite important data.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Hardware Problems</title>
+
+	<para>
+	<indexterm><primary>hardware prices</primary></indexterm>
+	<indexterm><primary>hardware problems</primary></indexterm>
+	<indexterm><primary>NICs</primary></indexterm>
+	<indexterm><primary>defective</primary><secondary>HUBs</secondary></indexterm>
+	<indexterm><primary>defective</primary><secondary>switches</secondary></indexterm>
+	<indexterm><primary>defective</primary><secondary>cables</secondary></indexterm>
+	Networking hardware prices have fallen sharply over the past 5 years. A surprising number
+	of Samba networking problems over this time have been traced to defective network interface
+	cards (NICs) or defective HUBs, switches, and cables.
+	</para>
+
+	<para>
+	<indexterm><primary>corrective action</primary></indexterm>
+	Not surprising is the fact that network administrators do not like to be shown to have made
+	a bad decision. Money saved in buying low-cost hardware may result in high costs incurred
+	in corrective action.
+	</para>
+
+	<para>
+	<indexterm><primary>intermittent</primary></indexterm>
+	<indexterm><primary>data corruption</primary></indexterm>
+	<indexterm><primary>slow network</primary></indexterm>
+	<indexterm><primary>low performance</primary></indexterm>
+	<indexterm><primary>data integrity</primary></indexterm>
+	Defective NICs, HUBs, and switches may appear as intermittent network access problems, intermittent
+	or persistent data corruption, slow network throughput, low performance, or even as BSOD
+	problems with MS Windows clients. In one case, a company updated several workstations with newer, faster
+	Windows client machines that triggered problems during logon as well as data integrity problems on
+	an older PC that was unaffected so long as the new machines were kept shut down.
+	</para>
+
+	<para>
+	Defective hardware problems may take patience and persistence before the real cause can be discovered.
+	</para>
+
+	<para>
+	<indexterm><primary>RAID controllers</primary></indexterm>
+	Networking hardware defects can significantly impact perceived Samba performance, but defective
+	RAID controllers as well as SCSI and IDE hard disk controllers have also been known to impair Samba server
+	operations. One business came to this realization only after replacing a Samba installation with MS 
+	Windows Server 2000 running on the same hardware. The root of the problem completely eluded the network
+	administrator until the entire server was replaced. While you may well think that this would never
+	happen to you, experience shows that given the right (unfortunate) circumstances, this can happen to anyone.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Large Directories</title>
+
+	<para>
+	There exist applications that create or manage directories containing many thousands of files. Such
+	applications typically generate many small files (less than 100 KB). At the best of times, under UNIX,
+	listing of the files in a directory that contains many files is slow. By default, Windows NT, 200x, 
+	and XP Pro cause network file system directory lookups on a Samba server to be performed for both 
+	the case preserving file name as well as for the mangled (8.3) file name. This incurs a huge overhead
+	on the Samba server that may slow down the system dramatically.
+	</para>
+
+	<para>
+	In an extreme case, the performance impact was dramatic. File transfer from the Samba server to a Windows
+	XP Professional workstation over 1 Gigabit Ethernet for 250-500 KB files was measured at approximately
+	30 MB/sec. But when tranferring a directory containing 120,000 files, all from 50KB to 60KB in size, the
+	transfer rate to the same workstation was measured at approximately 1.5 KB/sec. The net transfer was
+	on the order of a factor of 20-fold slower.
+	</para>
+
+	<para>
+	The symptoms that will be observed on the Samba server when a large directory is accessed will be that
+	aggregate I/O (typically blocks read) will be relatively low, yet the wait I/O times will be incredibly
+	long while at the same time the read queue is large. Close observation will show that the hard drive
+	that the file system is on will be thrashing wildly.
+	</para>
+
+	<para>
+	Samba-3.0.12 and later, includes new code that radically improves Samba perfomance. The secret to this is
+	really in the <smbconfoption name="case sensitive">True</smbconfoption> line. This tells smbd never to scan
+	for case-insensitive versions of names. So if an application asks for a file called <filename>FOO</filename>,
+	and it can not be found by a simple stat call, then smbd will return "file not found" immediately without
+	scanning the containing directory for a version of a different case.
+	</para>
+
+	<para>
+	Canonicalize all the files in the directory to have one case, upper or lower - either will do. Then set up 
+	a new custom share for the application as follows:
+	<screen>
+	[bigshare]
+			path = /data/xrayfiles/neurosurgeons/
+			read only = no
+			case sensitive = True
+			default case = upper
+			preserve case = no
+			short preserve case = no
+	</screen>
+	</para>
+
+	<para>
+	All files and directories under the <parameter>path</parameter> directory must be in the same case
+	as specified in the &smb.conf; stanza. This means that smbd will not be able to find lower case 
+	filenames with these settings.  Note, this is done on a per-share basis.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Key Points Learned</title>
+
+	<para>
+	This chapter has touched in broad sweeps on a number of simple steps that can be taken
+	to ensure that your Samba network is resilient, scalable, and reliable, and that it
+	performs well.
+	</para>
+
+	<para>
+	Always keep in mind that someone is responsible to maintain and manage your design.
+	In the long term, that may not be you. Spare a thought for your successor and give him or
+	her an even break.
+	</para>
+
+	<para>
+	<indexterm><primary>assumptions</primary></indexterm>
+	Last, but not least, you should not only keep the network design simple, but also be sure it is
+	well documented. This book may serve as your pattern for documenting every
+	aspect of your design, its implementation, and particularly the objects and assumptions
+	that underlie it.
+	</para>
+
+</sect1>
+
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-KerberosFastStart.xml b/docs-xml/Samba3-ByExample/SBE-KerberosFastStart.xml
new file mode 100644
index 00000000000..b593eed4ffe
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-KerberosFastStart.xml
@@ -0,0 +1,2071 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="kerberos">
+  <title>Active Directory, Kerberos, and Security</title>
+
+    <para><indexterm>
+	<primary>experiment</primary>
+      </indexterm>
+	By this point in the book, you have been exposed to many Samba-3 features and capabilities.
+	More importantly, if you have implemented the examples given, you are well on your way to becoming 
+	a Samba-3 networking guru who knows a lot about Microsoft Windows. If you have taken the time to 
+	practice, you likely have thought of improvements and scenarios with which you can experiment. You 
+	are rather well plugged in to the many flexible ways Samba can be used.
+	</para>
+
+    <para><indexterm>
+	<primary>criticism</primary>
+      </indexterm>
+	This is a book about Samba-3. Understandably, its intent is to present it in a positive light. 
+	The casual observer might conclude that this book is one-eyed about Samba. It is &smbmdash; what 
+	would you expect? This chapter exposes some criticisms that have been raised concerning 
+	the use of Samba. For each criticism, there are good answers and appropriate solutions.
+	</para>
+
+	<para>
+	Some criticism always comes from deep inside ranks that one would expect to be supportive of a particular 
+	decision. Criticism can be expected from the outside. Let's see how the interesting dynamic of 
+	criticism develops with respect to Abmas.
+	</para>
+
+    <para><indexterm>
+	<primary>straw-man</primary>
+      </indexterm>
+	This chapter provides a shameless self-promotion of Samba-3. The objections raised were not pulled
+	out of thin air. They were drawn from comments made by Samba users and from criticism during 
+	discussions with Windows network administrators. The tone of the objections reflects as closely 
+	as possible that of the original. The case presented is a straw-man example that is designed to 
+	permit each objection to be answered as it might occur in real life.
+	</para>
+
+<sect1>
+	<title>Introduction</title>
+
+      <para><indexterm>
+	  <primary>acquisitions</primary>
+	</indexterm><indexterm>
+	  <primary>risk</primary>
+	</indexterm><indexterm>
+	  <primary>assessment</primary>
+	</indexterm><indexterm>
+	  <primary>Active Directory</primary>
+	</indexterm><indexterm>
+	  <primary>Windows 2003 Serve</primary>
+	</indexterm>
+	Abmas is continuing its meteoric growth with yet further acquisitions. The investment community took
+	note of the spectacular projection of Abmas onto the global business stage. Abmas is building an
+	interesting portfolio of companies that includes accounting services, financial advice, investment
+	portfolio management, property insurance, risk assessment, and the recent addition of a a video rental
+	business. The pieces do not always appear to fit together, but Mr. Meany is certainly executing an 
+	interesting business growth and development plan. Abmas Video Rentals was recently acquired. 
+	During the time that the acquisition was closing, the Video Rentals business upgraded its Windows 
+	NT4-based network to Windows 2003 Server and Active Directory.
+	</para>
+
+      <para><indexterm>
+	  <primary>Active Directory</primary>
+	</indexterm>
+	You have accepted the fact that Abmas Video Rentals will use Microsoft Active Directory.
+	The IT team, led by Stan Soroka, is committed to Samba-3 and to maintaining a uniform technology platform. 
+	Stan Soroka's team voiced its disapproval over the decision to permit this business to continue to 
+	operate with a solution that is viewed by Christine and her group as <quote>an island of broken 
+	technologies.</quote> This comment was made by one of Christine's staff as they were installing a new 
+	Samba-3 server at the new business.
+	</para>
+
+
+      <para><indexterm>
+	  <primary>consultant</primary>
+	</indexterm><indexterm>
+	  <primary>hypothetical</primary>
+	</indexterm>
+	Abmas Video Rentals' head of IT heard of this criticism. He was offended that a junior engineer
+	should make such a comment. He felt that he had to prepare in case he might be criticized for his 
+	decision to use Active Directory. He decided he would defend his decision by hiring the services 
+	of an outside security systems consultant to report<footnote>This report is entirely fictitious. 
+	Any resemblance to a factual report is purely coincidental.</footnote> on his unit's operations 
+	and to investigate the role of Samba at his site. Here are key extracts from this hypothetical 
+	report:
+	</para>
+
+      <blockquote><para><indexterm>
+	    <primary>vulnerabilities</primary>
+	  </indexterm><indexterm>
+	    <primary>integrity</primary>
+	  </indexterm><indexterm>
+	    <primary>practices</primary>
+	  </indexterm><indexterm>
+	    <primary>Active Directory</primary>
+	  </indexterm>
+	... the implementation of Microsoft Active Directory at the Abmas Video Rentals, Bamingsham site,
+	 has been examined. We find no evidence to support a notion that vulnerabilities exist at your site.  
+	... we took additional steps to validate the integrity of the installation and operation of Active 
+	Directory and are pleased that your staff are following sound practices.
+	</para>
+
+	<para>
+	...
+	</para>
+
+	<para><indexterm>
+	    <primary>accounts</primary>
+	    <secondary>user</secondary>
+	  </indexterm><indexterm>
+	    <primary>accounts</primary>
+	    <secondary>group</secondary>
+	  </indexterm><indexterm>
+	    <primary>Backup</primary>
+	  </indexterm><indexterm>
+	    <primary>disaster recovery</primary>
+	  </indexterm><indexterm>
+	    <primary>validated</primary>
+	  </indexterm><indexterm>
+	    <primary>off-site storage</primary>
+	  </indexterm>
+	User and group accounts, and respective privileges, have been well thought out. File system shares are
+	appropriately secured. Backup and disaster recovery plans are well managed and validated regularly, and
+	effective off-site storage practices are considered to exceed industry norms.
+	</para>
+
+	<para><indexterm>
+	    <primary>compromise</primary>
+	  </indexterm><indexterm>
+	    <primary>secure</primary>
+	  </indexterm><indexterm>
+	    <primary>network</primary>
+	    <secondary>secure</secondary>
+	  </indexterm>
+	Your staff are justifiably concerned that the use of Samba may compromise their good efforts to maintain
+	a secure network. 
+	</para>
+
+	<para><indexterm>
+	    <primary>winbind</primary>
+	  </indexterm><indexterm>
+	    <primary>security</primary>
+	  </indexterm><indexterm>
+	    <primary>secure</primary>
+	  </indexterm><indexterm>
+	    <primary>network</primary>
+	    <secondary>management</secondary>
+	  </indexterm>
+	The recently installed Linux file and application server uses a tool called <command>winbind</command> 
+	that is indiscriminate about security. All user accounts in Active Directory can be used to access data 
+	stored on the Linux system. We are alarmed that secure information is accessible to staff who should 
+	not even be aware that it exists. We share the concerns of your network management staff who have gone 
+	to great lengths to set fine-grained controls that limit information access to those who need access. 
+	It seems incongruous to us that Samba winbind should be permitted to be used considering that it voids this fine work.
+	</para>
+
+	<para><indexterm>
+	    <primary>isolated</primary>
+	  </indexterm><indexterm>
+	    <primary>firewall</primary>
+	  </indexterm><indexterm>
+	    <primary>best practices</primary>
+	  </indexterm>
+	Graham Judd [head of network administration] has locked down the security of all systems and is following 
+	the latest Microsoft guidelines. ... null session connections have been disabled ... the internal network 
+	is isolated from the outside world, the [product name removed] firewall is under current contract 
+	maintenance support from [the manufacturer].  ... our attempts to penetrate security of your systems 
+	failed to find problems common to Windows networking sites. We commend your staff on their attention to 
+	detail and for following Microsoft recommended best practices.
+	</para>
+
+	<para>
+	...
+	</para>
+
+	<para><indexterm>
+	    <primary>security</primary>
+	  </indexterm><indexterm>
+	    <primary>disable</primary>
+	  </indexterm><indexterm>
+	    <primary>essential</primary>
+	  </indexterm><indexterm>
+	    <primary>trusted computing</primary>
+	  </indexterm>
+	Regarding the use of Samba, we offer the following comments: Samba is in use in nearly half of
+	all sites we have surveyed. ... It is our opinion that Samba offers no better security than Microsoft
+	... what worries us regarding Samba is the need to disable essential Windows security features such as
+	secure channel support, digital sign'n'seal on all communication traffic, and running Active Directory in
+	mixed mode so that Samba clients and servers can authenticate all of it. Additionally, we are concerned that
+	Samba is not at the full capabilities of Microsoft Windows NT4 server. Microsoft has moved well beyond that
+	with trusted computing initiatives that the Samba developers do not participate in.
+	</para>
+
+	<para><indexterm>
+	    <primary>integrity</primary>
+	  </indexterm><indexterm>
+	    <primary>hackers</primary>
+	  </indexterm><indexterm>
+	    <primary>accountable</primary>
+	  </indexterm><indexterm>
+	    <primary>flaws</primary>
+	  </indexterm><indexterm>
+	    <primary>updates</primary>
+	  </indexterm><indexterm>
+	    <primary>bug fixes</primary>
+	  </indexterm><indexterm>
+	    <primary>alarm</primary>
+	  </indexterm>
+	One wonders about the integrity of an open source program that is developed by a team of hackers 
+	who cannot be held accountable for the flaws in their code. The sheer number of updates and bug
+	fixes they have released should ring alarm bells in any business.
+	</para>
+
+	<para><indexterm>
+	    <primary>employment</primary>
+	  </indexterm><indexterm>
+	    <primary>jobs</primary>
+	  </indexterm><indexterm>
+	    <primary>risk</primary>
+	  </indexterm>
+	Another factor that should be considered is that buying Microsoft products and services helps to 
+	provide employment in the IT industry. Samba and Open Source software place those jobs at risk.
+	</para></blockquote>
+
+      <para><indexterm>
+	  <primary>Active Directory</primary>
+	</indexterm><indexterm>
+	  <primary>independent expert</primary>
+	</indexterm>
+	This is also a challenge to rise above the trouble spot. You call Stan's team together for a simple 
+	discussion, but it gets further out of hand.  When you return to your office, you find the following 
+	email in your in-box:
+	</para>
+
+	<para>
+	Good afternoon,
+	</para>
+
+	<blockquote><attribution>Stan</attribution><para>
+	I apologize for the leak of internal discussions to the new business. It reflects poorly on our 
+	professionalism and has put you in an unpleasant position. I regret the incident.
+	</para>
+
+	<para>
+	I also wish to advise that two of the recent recruits want to implement Kerberos authentication 
+	across all systems. I concur with the desire to improve security. One of the new guys who is championing
+	the move to Kerberos was responsible for the comment that caused the embarrassment.
+	</para>
+
+	<para><indexterm>
+	    <primary>Kerberos</primary>
+	  </indexterm><indexterm>
+	    <primary>OpenLDAP</primary>
+	  </indexterm><indexterm>
+	    <primary>Active Directory</primary>
+	  </indexterm><indexterm>
+	    <primary>consultant</primary>
+	  </indexterm>
+	I am experiencing difficulty in handling the sharp push for Kerberos. He claims that Kerberos, OpenLDAP, 
+	plus Samba-3 will seamlessly replace Microsoft Active Directory. I am a little out of my depth with respect 
+	to the feasibility of such a move, but have taken steps to pull both of them into line. With your consent, 
+	I would like to hire the services of a well-known Samba consultant to set the record straight.
+	</para>
+
+	<para><indexterm>
+	    <primary>criticism</primary>
+	  </indexterm><indexterm>
+	    <primary>policy</primary>
+	  </indexterm><indexterm>
+	    <primary>Windows Servers</primary>
+	  </indexterm><indexterm>
+	    <primary>Active Directory</primary>
+	  </indexterm><indexterm>
+	    <primary>budgetted</primary>
+	  </indexterm><indexterm>
+	    <primary>financial responsibility</primary>
+	  </indexterm>
+	I intend to use this report to answer the criticism raised and would like to establish a policy that we
+	will approve the use of Microsoft Windows Servers (and Active Directory) subject to all costs being covered 
+	out of the budget of the division that wishes to go its own way. I propose that dissenters will still remain
+	responsible to meet the budgeted contribution to IT operations as a whole. I believe we should not coerce 
+	use of any centrally proposed standards, but make all noncompliance the financial responsibility of the 
+	out-of-step division. Hopefully, this will encourage all divisions to walk with us and not alone.
+	</para></blockquote>
+
+	<sect2>
+		<title>Assignment Tasks</title>
+
+		<para>
+		You agreed with Stan's recommendations and hired a consultant to help defuse the powder
+		keg. The consultant's task is to provide a tractable answer to each of the issues raised. The consultant must be able
+		to support his or her claims, keep emotions to the side, and answer technically.
+		</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+	<title>Dissection and Discussion</title>
+
+      <para><indexterm>
+	  <primary>tool</primary>
+	</indexterm><indexterm>
+	  <primary>benefit</primary>
+	</indexterm><indexterm>
+	  <primary>choice</primary>
+	</indexterm><indexterm>
+	  <primary>consultant</primary>
+	</indexterm><indexterm>
+	  <primary>installation</primary>
+	</indexterm><indexterm>
+	  <primary>income</primary>
+	</indexterm><indexterm>
+	  <primary>employment</primary>
+	</indexterm>
+	Samba-3 is a tool. No one is pounding your door to make you use Samba. That is a choice that you are free to 
+	make or reject. It is likely that your decision to use Samba can greatly benefit your company. 
+	The Samba Team obviously believes that the Samba software is a worthy choice. 
+	If you hire a consultant to assist with the installation and/or deployment of Samba, or if you hire 
+	someone to help manage your Samba installation, you can create income and employment. Alternately, 
+	money saved by not spending in the IT area can be spent elsewhere in the business. All money saved 
+	or spent creates employment.
+	</para>
+
+      <para><indexterm>
+	  <primary>economically sustainable</primary>
+	</indexterm><indexterm>
+	  <primary>inter-operability</primary>
+	</indexterm><indexterm>
+	  <primary>file and print service</primary>
+	</indexterm><indexterm>
+	  <primary>cost</primary>
+	</indexterm><indexterm>
+	  <primary>alternative</primary>
+	</indexterm>
+	In the long term, the use of Samba must be economically sustainable. In some situations, Samba is adopted
+	purely to provide file and print service interoperability on platforms that otherwise cannot provide 
+	access to data and to printers for Microsoft Windows clients. Samba is used by some businesses to
+	effect a reduction in the cost of providing IT services. Obviously, it is also used by some as an 
+	alternative to the use of a Microsoft file and print serving platforms with no consideration of costs.
+	</para>
+
+      <para><indexterm>
+	  <primary>documentation</primary>
+	</indexterm><indexterm>
+	  <primary>responsibility</primary>
+	</indexterm><indexterm>
+	  <primary>fix</primary>
+	</indexterm><indexterm>
+	  <primary>broken</primary>
+	</indexterm>
+	It would be foolish to adopt a technology that might put any data or users at risk. Security affects 
+	everyone. The Samba-Team is fully cognizant of the responsibility they have to their users. 
+	The Samba documentation clearly reveals that full responsibility is accepted to fix anything 
+	that is broken.
+	</para>
+
+      <para><indexterm>
+	  <primary>commercial</primary>
+	</indexterm><indexterm>
+	  <primary>software</primary>
+	</indexterm><indexterm>
+	  <primary>commercial software</primary>
+	</indexterm><indexterm>
+	  <primary>End User License Agreement</primary>
+	  <see>EULA</see>
+	</indexterm><indexterm>
+	  <primary>accountable</primary>
+	</indexterm><indexterm>
+	  <secondary>liability</secondary>
+	</indexterm><indexterm>
+	  <primary>accepts liability</primary>
+	</indexterm><indexterm>
+	  <primary>price paid</primary>
+	</indexterm><indexterm>
+	  <primary>product defects</primary>
+	</indexterm><indexterm>
+	  <primary>reimburse</primary>
+	</indexterm><indexterm>
+	  <primary>extent</primary>
+	</indexterm>
+	There is a mistaken perception in the IT industry that commercial software providers are fully 
+	accountable for the defects in products. Open Source software comes with no warranty, so it is 
+	often assumed that its use confers a higher degree of risk. Everyone should read commercial software 
+	End User License Agreements (EULAs). You should determine what real warranty is offered and the 
+	extent of liability that is accepted. Doing so soon dispels the popular notion that
+	commercial software vendors are willingly accountable for product defects. In many cases, the
+	commercial vendor accepts liability only to reimburse the price paid for the software. 
+	</para>
+
+      <para><indexterm>
+	  <primary>consumer</primary>
+	</indexterm><indexterm>
+	  <primary>EULA</primary>
+	</indexterm><indexterm>
+	  <primary>track record</primary>
+	</indexterm><indexterm>
+	  <primary>commercial software</primary>
+	</indexterm><indexterm>
+	  <primary>support</primary>
+	</indexterm><indexterm>
+	  <primary>vendor</primary>
+	</indexterm>
+	The real issues that a consumer (like you) needs answered are What is the way of escape from technical 
+	problems, and how long will it take? The average problem turnaround time in the Open Source community is 
+	approximately 48 hours. What does the EULA offer? What is the track record in the commercial software 
+	industry? What happens when your commercial vendor decides to cease providing support?
+	</para>
+
+      <para><indexterm>
+	  <primary>source code</primary>
+	</indexterm><indexterm>
+	  <primary>Open Source</primary>
+	</indexterm><indexterm>
+	  <primary>hire</primary>
+	</indexterm><indexterm>
+	  <primary>programmer</primary>
+	</indexterm><indexterm>
+	  <primary>solve</primary>
+	</indexterm><indexterm>
+	  <primary>fix</primary>
+	</indexterm><indexterm>
+	  <secondary>problem</secondary>
+	</indexterm>
+	Open Source software at least puts you in possession of the source code. This means that when
+	all else fails, you can hire a programmer to solve the problem.
+	</para>
+
+	<sect2>
+		<title>Technical Issues</title>
+
+		<para>
+		Each issue is now discussed and, where appropriate, example implementation steps are
+		provided.
+		</para>
+
+	<variablelist>
+		<varlistentry>
+			<term>Winbind and Security</term>
+	    <listitem><para><indexterm>
+		  <primary>Winbind</primary>
+		</indexterm><indexterm>
+		  <primary>Security</primary>
+		</indexterm><indexterm>
+		  <primary>network</primary>
+		  <secondary>administrators</secondary>
+		</indexterm><indexterm>
+		  <primary>Domain users</primary>
+		</indexterm><indexterm>
+		  <secondary>Domain account</secondary>
+		</indexterm><indexterm>
+		  <primary>credentials</primary>
+		</indexterm><indexterm>
+		  <primary>Network Neighborhood</primary>
+		</indexterm><indexterm>
+		  <primary>UNIX/Linux server</primary>
+		</indexterm><indexterm>
+		  <primary>browse</primary>
+		</indexterm><indexterm>
+		  <primary>shares</primary>
+		</indexterm>
+				Windows network administrators may be dismayed to find that <command>winbind</command> 
+				exposes all domain users so that they may use their domain account credentials to 
+				log on to a UNIX/Linux system. The fact that all users in the domain can see the 
+				UNIX/Linux server in their Network Neighborhood and can browse the shares on the 
+				server seems to excite them further.
+				</para>
+
+	      <para><indexterm>
+		  <primary>Domain Member server</primary>
+		</indexterm><indexterm>
+		  <primary>familiar</primary>
+		</indexterm><indexterm>
+		  <primary>fear</primary>
+		</indexterm><indexterm>
+		  <primary>unknown</primary>
+		</indexterm>
+				<command>winbind</command> provides for the UNIX/Linux domain member server or 
+				client, the same as one would obtain by adding a Microsoft Windows server or 
+				client to the domain. The real objection is the fact that Samba is not MS Windows 
+				and therefore requires handling a little differently from the familiar Windows systems.
+				One must recognize fear of the unknown.
+				</para>
+
+	      <para><indexterm>
+		  <primary>network administrators</primary>
+		</indexterm><indexterm>
+		  <primary>recognize</primary>
+		</indexterm><indexterm>
+		  <primary>winbind</primary>
+		</indexterm><indexterm>
+		  <primary>over-ride</primary>
+		</indexterm><indexterm>
+		  <primary>Active Directory</primary>
+		  <secondary>management tools</secondary>
+		</indexterm><indexterm>
+		  <primary>fears</primary>
+		</indexterm>
+				Windows network administrators need to recognize that <command>winbind</command> does
+				not, and cannot, override account controls set using the Active Directory management
+				tools. The control is the same. Have no fear.
+				</para>
+
+	      <para><indexterm>
+		  <primary>ADS Domain</primary>
+		</indexterm><indexterm>
+		  <primary>account</primary>
+		  <secondary>ADS Domain</secondary>
+		</indexterm><indexterm>
+		  <primary>winbind</primary>
+		</indexterm><indexterm>
+		  <primary>browsing</primary>
+		</indexterm><indexterm>
+		  <primary>permits</primary>
+		</indexterm><indexterm>
+		  <primary>access</primary>
+		</indexterm><indexterm>
+		  <primary>drive mapping</primary>
+		</indexterm><indexterm>
+		  <primary>protected</primary>
+		</indexterm><indexterm>
+		  <primary>security controls</primary>
+		</indexterm><indexterm>
+		  <primary>access controls</primary>
+		</indexterm>
+				Where Samba and the ADS domain account information obtained through the use of
+				<command>winbind</command> permits access, by browsing or by the drive mapping to
+				a share, to data that should be better protected. This can only happen when security
+				controls have not been properly implemented. Samba permits access controls to be set
+				on:
+				</para>
+
+				<itemizedlist>
+					<listitem><para>Shares themselves (i.e., the logical share itself)</para></listitem>
+					<listitem><para>The share definition in &smb.conf;</para></listitem>
+					<listitem><para>The shared directories and files using UNIX permissions</para></listitem>
+                                        <listitem><para>Using Windows 2000 ACLs &smbmdash; if the file system is POSIX enabled</para></listitem>
+				</itemizedlist>
+
+				<para>
+				Examples of each are given in <link linkend="ch10expl"/>.
+				</para>
+				</listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>User and Group Controls</term>
+	    <listitem><para><indexterm>
+		  <primary>User and Group Controls</primary>
+		</indexterm><indexterm>
+		  <primary>management</primary>
+		  <secondary>User</secondary>
+		</indexterm><indexterm>
+		  <primary>management</primary>
+		  <secondary>group</secondary>
+		</indexterm><indexterm>
+		  <primary>ADS</primary>
+		</indexterm><indexterm>
+		  <primary>permissions</primary>
+		</indexterm><indexterm>
+		  <primary>privileges</primary>
+		</indexterm><indexterm>
+		  <primary>flexibility</primary>
+		</indexterm><indexterm>
+		  <primary>access controls</primary>
+		</indexterm><indexterm>
+		  <primary>share definition</primary>
+		</indexterm>
+				User and group management facilities as known in the Windows ADS environment may be
+				used to provide equivalent access control constraints or to provide equivalent
+				permissions and privileges on Samba servers. Samba offers greater flexibility in the
+				use of user and group controls because it has additional layers of control compared to
+				Windows 200x/XP. For example, access controls on a Samba server may be set within
+				the share definition in a manner for which Windows has no equivalent.
+				</para>
+
+	      <para><indexterm>
+		  <primary>analysis</primary>
+		</indexterm><indexterm>
+		  <primary>system security</primary>
+		</indexterm><indexterm>
+		  <primary>safe-guards</primary>
+		</indexterm><indexterm>
+		  <primary>permissions</primary>
+		  <secondary>excessive</secondary>
+		</indexterm><indexterm>
+		  <primary>file system</primary>
+		</indexterm><indexterm>
+		  <primary>shared resource</primary>
+		</indexterm><indexterm>
+		  <primary>share definition</primary>
+		</indexterm>
+				In any serious analysis of system security, it is important to examine the safeguards
+				that remain when all other protective measures fail. An administrator may inadvertently
+				set excessive permissions on the file system of a shared resource, or he may set excessive
+				privileges on the share itself. If that were to happen in a Windows 2003 Server environment,
+				the data would indeed be laid bare to abuse. Yet, within a Samba share definition, it is
+				possible to guard against that by enforcing controls on the share definition itself. You
+				see a practical example of this a little later in this chapter.
+				</para>
+
+	      <para><indexterm>
+		  <primary>diligence</primary>
+		</indexterm><indexterm>
+		  <primary>weakness</primary>
+		</indexterm>
+				The report that is critical of Samba really ought to have exercised greater due
+				diligence: the real weakness is on the side of a Microsoft Windows environment.
+				</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>Security Overall</term>
+	    <listitem><para><indexterm>
+		  <primary>defects</primary>
+		</indexterm>
+				Samba is designed in such a manner that weaknesses inherent in the design of
+				Microsoft Windows networking ought not to expose the underlying UNIX/Linux file
+				system in any way. All software has potential defects, and Samba is no exception.
+				What matters more is how defects that are discovered get dealt with.
+				</para>
+
+	      <para><indexterm>
+		  <primary>security</primary>
+		</indexterm><indexterm>
+		  <primary>protection</primary>
+		</indexterm><indexterm>
+		  <primary>compromise</primary>
+		</indexterm><indexterm>
+		  <primary>consequential risk</primary>
+		</indexterm>
+				The Samba Team totally agrees with the necessity to observe and fully implement
+				every security facility to provide a level of protection and security that is necessary
+				and that the end user (or network administrator) needs. Never would the Samba Team
+				recommend a compromise to system security, nor would deliberate defoliation of
+				security be publicly condoned; yet this is the practice by many Windows network
+				administrators just to make happy users who have no notion of consequential risk.
+				</para>
+
+	      <para><indexterm>
+		  <primary>condemns</primary>
+		</indexterm><indexterm>
+		  <primary>security fixes</primary>
+		</indexterm><indexterm>
+		  <primary>updates</primary>
+		</indexterm><indexterm>
+		  <primary>development</primary>
+		</indexterm><indexterm>
+		  <primary>documentation</primary>
+		</indexterm><indexterm>
+		  <primary>security updates</primary>
+		</indexterm><indexterm>
+		  <primary>turn-around time</primary>
+		</indexterm>
+				The report condemns Samba for releasing updates and security fixes, yet Microsoft
+				online updates need to be applied almost weekly. The answer to the criticism 
+				lies in the fact that Samba development is continuing, documentation is improving, 
+				user needs are being increasingly met or exceeded, and security updates are issued 
+				with a short turnaround time.
+				</para>
+
+	      <para><indexterm>
+		  <primary>modularization</primary>
+		</indexterm><indexterm>
+		  <primary>next generation</primary>
+		</indexterm><indexterm>
+		  <primary>responsible</primary>
+		</indexterm><indexterm>
+		  <primary>dependability</primary>
+		</indexterm><indexterm>
+		  <primary>road-map</primary>
+		  <secondary>published</secondary>
+		</indexterm>
+				The release of Samba-4 is expected around late 2004 to early 2005 and involves a near 
+				complete rewrite to permit extensive modularization and to prepare Samba for new 
+				functionality planned for addition during the next-generation series. The Samba Team 
+				is responsible and can be depended upon; the history to date suggests a high 
+				degree of dependability and on charter development consistent with published 
+				roadmap projections.
+				</para>
+
+	      <para><indexterm>
+		  <primary>foundation members</primary>
+		</indexterm><indexterm>
+		  <primary>Common Internet File System</primary>
+		  <see>CIFS</see>
+		</indexterm><indexterm>
+		  <primary>network attached storage</primary>
+		  <see>NAS</see>
+		</indexterm><indexterm>
+		  <primary>conferences</primary>
+		</indexterm><indexterm>
+		  <primary>presence and leadership</primary>
+		</indexterm><indexterm>
+		  <primary>leadership</primary>
+		</indexterm><indexterm>
+		  <primary>inter-operability</primary>
+		</indexterm>
+				Not well published is the fact that Microsoft was a foundation member of
+				the Common Internet File System (CIFS) initiative, together with the participation 
+				of the network attached storage (NAS) industry. Unfortunately, for the past few years,
+				Microsoft has been absent from active involvement at CIFS conferences and has
+				not exercised the leadership expected of a major force in the networking technology
+				space. The Samba Team has maintained consistent presence and leadership at all
+				CIFS conferences and at the interoperability laboratories run concurrently with
+				them.
+				</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>Cryptographic Controls (schannel, sign'n'seal)</term>
+	    <listitem><para><indexterm>
+		  <primary>Cryptographic</primary>
+		</indexterm><indexterm>
+		  <primary>schannel</primary>
+		</indexterm><indexterm>
+		  <primary>digital sign'n'seal</primary>
+		</indexterm>
+				The report correctly mentions that Samba did not support the most recent
+				<constant>schannel</constant> and <constant>digital sign'n'seal</constant> features
+				of Microsoft Windows NT/200x/XPPro products. This is one of the key features 
+				of the Samba-3 release. Market research reports take so long to generate that they are
+				seldom a reflection of current practice, and in many respects reports are like a
+				pathology report &smbmdash; they reflect accurately (at best) status at a snapshot in time.
+				Meanwhile, the world moves on.
+				</para>
+
+	      <para><indexterm>
+		  <primary>public specifications</primary>
+		</indexterm><indexterm>
+		  <primary>protocols</primary>
+		</indexterm><indexterm>
+		  <primary>algorithm</primary>
+		</indexterm><indexterm>
+		  <primary>compatible</primary>
+		</indexterm><indexterm>
+		  <primary>network</primary>
+		  <secondary>traffic</secondary>
+		  <tertiary>observation</tertiary>
+		</indexterm><indexterm>
+		  <primary>defensible standards</primary>
+		</indexterm><indexterm>
+		  <primary>secure networking</primary>
+		</indexterm>
+				It should be pointed out that had clear public specifications for the protocols
+				been published, it would have been much easier to implement these features and would have
+				taken less time to do. The sole mechanism used to find an algorithm that is compatible
+				with the methods used by Microsoft has been based on observation of network traffic
+				and trial-and-error implementation of potential techniques. The real value of public
+				and defensible standards is obvious to all and would have enabled more secure networking
+				for everyone.
+				</para>
+
+	      <para><indexterm>
+		  <primary>Critics</primary>
+		</indexterm><indexterm>
+		  <primary>digital sign'n'seal</primary>
+		</indexterm>
+				Critics of Samba often ignore fundamental problems that may plague (or may have plagued)
+				the users of Microsoft's products also. Those who are first to criticize Samba
+				for not rushing into release of <constant>digital sign'n'seal</constant> support
+				often dismiss the problems that Microsoft has 
+				<ulink url="http://support.microsoft.com/default.aspx?kbid=321733">acknowledged</ulink>
+				and for which a fix was provided. In fact,
+				<ulink url="http://www.tangent-systems.com/support/delayedwrite.html">Tangent Systems</ulink> 
+				have documented a significant problem with delays writes that can be connected with the
+				implementation of sign'n'seal. They provide a work-around that is not trivial for many
+				Windows networking sites. From notes such as this it is clear that there are benefits
+				from not rushing new technology out of the door too soon.
+				</para>
+
+	      <para><indexterm>
+		  <primary>secure networking protocols</primary>
+		</indexterm><indexterm>
+		  <primary>refereed standards</primary>
+		</indexterm><indexterm>
+		  <primary>proprietary</primary>
+		</indexterm><indexterm>
+		  <primary>digital rights</primary>
+		</indexterm><indexterm>
+		  <primary>protection</primary>
+		</indexterm><indexterm>
+		  <primary>networking protocols</primary>
+		</indexterm><indexterm>
+		  <primary>diffusion</primary>
+		</indexterm><indexterm>
+		  <primary>consumer</primary>
+		</indexterm><indexterm>
+		  <primary>choice</primary>
+		</indexterm>
+				One final comment is warranted. If companies want more secure networking protocols,
+				the most effective method by which this can be achieved is by users seeking
+				and working together to help define open and publicly refereed standards. The
+				development of closed source, proprietary methods that are developed in a
+				clandestine framework of secrecy, under claims of digital rights protection, does
+				not favor the diffusion of safe networking protocols and certainly does not
+				help the consumer to make a better choice.
+				</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>Active Directory Replacement with Kerberos, LDAP, and Samba</term>
+	        <indexterm>
+		  <primary>Active Directory</primary>
+		  <secondary>Replacement</secondary>
+		</indexterm><indexterm>
+		  <primary>Kerberos</primary>
+		</indexterm><indexterm>
+		  <primary>LDAP</primary>
+		</indexterm><indexterm>
+		  <primary>remote procedure call</primary>
+		  <see>RPC</see>
+		</indexterm>
+				<listitem><para>
+				<literallayout>    </literallayout>
+				The Microsoft networking protocols extensively make use of remote procedure call (RPC)
+				technology. Active Directory is not a simple mixture of LDAP and Kerberos together
+				with file and print services, but rather is a complex, intertwined implementation
+				of them that uses RPCs that are not supported by any of these component technologies
+				and yet by which they are made to interoperate in ways that the components do not
+				support.
+				</para>
+
+	      <para><indexterm>
+		  <primary>Active Directory</primary>
+		  <secondary>Server</secondary>
+		</indexterm><indexterm>
+		  <primary>OpenLDAP</primary>
+		</indexterm><indexterm>
+		  <primary>Kerberos</primary>
+		</indexterm><indexterm>
+		  <primary>project maintainers</primary>
+		</indexterm><indexterm>
+		  <primary>LDAP</primary>
+		</indexterm>
+				In order to make the popular request for Samba to be an Active Directory Server a
+				reality, it is necessary to add to OpenLDAP, Kerberos, as well as Samba, RPC calls
+				that are not presently supported. The Samba Team has not been able to gain critical
+				overall support for all project maintainers to work together on the complex
+				challenge of developing and integrating the necessary technologies. Therefore, if
+				the Samba Team does not make it a priority to absorb Kerberos and LDAP functionality
+				into the Samba project, this dream request cannot become a reality.
+				</para>
+
+	      <para><indexterm>
+		  <primary>missing RPC's</primary>
+		</indexterm><indexterm>
+		  <primary>road-map</primary>
+		</indexterm><indexterm>
+		  <primary>ADS</primary>
+		  <secondary>server</secondary>
+		</indexterm><indexterm>
+		  <primary>MMC</primary>
+		</indexterm><indexterm>
+		  <primary>managed</primary>
+		</indexterm>
+				At this time, the integration of LDAP, Kerberos, and the missing RPCs is not on the
+				Samba development roadmap. If it is not on the published roadmap, it cannot be delivered
+				anytime soon. Ergo, ADS server support is not a current goal for Samba development.
+				The Samba Team is most committed to permitting Samba to be a full ADS domain member
+				that is increasingly capable of being managed using Microsoft Windows MMC tools.
+				</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<sect3>
+	<title>Kerberos Exposed</title>
+
+	  <para><indexterm>
+	      <primary>kerberos</primary>
+	    </indexterm><indexterm>
+	      <primary>unauthorized activities</primary>
+	    </indexterm><indexterm>
+	      <primary>authorized location</primary>
+	    </indexterm>
+	Kerberos is a network authentication protocol that provides secure authentication for 
+	client-server applications by using secret-key cryptography. Firewalls are an insufficient 
+	barrier mechanism in today's networking world; at best they only restrict incoming network 
+	traffic but cannot prevent network traffic that comes from authorized locations from 
+	performing unauthorized activities.
+	</para>
+
+	  <para><indexterm>
+	      <primary>strong cryptography</primary>
+	    </indexterm><indexterm>
+	      <primary>identity</primary>
+	    </indexterm><indexterm>
+	      <primary>integrity</primary>
+	    </indexterm>
+	Kerberos was created by MIT as a solution to network security problems. The Kerberos protocol uses 
+	strong cryptography so that a client can prove its identity to a server (and vice versa) across an 
+	insecure network connection. After a client and server has used Kerberos to prove their identity, 
+	they can also encrypt all of their communications to assure privacy and data integrity as they go 
+	about their business.
+	</para>
+
+	  <para><indexterm>
+	      <primary>trusted third-party</primary>
+	    </indexterm><indexterm>
+	      <primary>principals</primary>
+	    </indexterm><indexterm>
+	      <primary>trusting</primary>
+	    </indexterm><indexterm>
+	      <primary>kerberos</primary>
+	      <secondary>server</secondary>
+	    </indexterm><indexterm>
+	      <primary>secret</primary>
+	    </indexterm>
+	Kerberos is a trusted third-party service. That means that there is a third party (the kerberos 
+	server) that is trusted by all the entities on the network (users and services, usually called 
+	principals). All principals share a secret password (or key) with the kerberos server and this 
+	enables principals to verify that the messages from the kerberos server are authentic. Therefore, 
+	trusting the kerberos server, users and services can authenticate each other.
+	</para>
+
+	<para>
+	<indexterm><primary>restricted export</primary></indexterm>
+	<indexterm><primary>MIT Kerberos</primary></indexterm>
+	<indexterm><primary>Heimdal Kerberos</primary></indexterm>
+	Kerberos was, until recently, a technology that was restricted from being exported from the United States.
+	For many years that hindered global adoption of more secure networking technologies both within the United States
+	and abroad. A free and unencumbered implementation of MIT Kerberos has been produced in Europe
+	and is available from the <ulink url="http://www.pdc.kth.se/heimdal/">Royal Institute</ulink> of
+	Technology (KTH), Sweden. It is known as the Heimdal Kerberos project.  In recent times the U.S. government
+	has removed sanctions affecting the global distribution of MIT Kerberos.  It is likely that there will be a
+	significant surge forward in the development of Kerberos-enabled applications and in the general deployment
+	and use of Kerberos across the spectrum of the information technology industry.
+	</para>
+
+	<para>
+	<indexterm><primary>Kerberos</primary><secondary>interoperability</secondary></indexterm>
+	A storm has broken out concerning interoperability between MIT Kerberos and Microsofts' implementation
+	of it. For example, a 2002
+	<ulink url="http://www.idg.com.sg/idgwww.nsf/0/5DDA8D153A7505A748256BAB000D992A?OpenDocument">IDG</ulink>
+	report<footnote>Note: This link is no longer active. The same article is still
+	available from <ulink url="http://199.105.191.226/Man/2699/020430msdoj/">ITWorld.com</ulink> (July 5, 2005)</footnote> by
+	states:
+	</para>
+
+	<blockquote><para>
+	A Microsoft Corp. executive testified at the software giant's remedy hearing that the company goes to 
+	great lengths to disclose interfaces and protocols that allow third-party software products to interact 
+	with Windows. But a lawyer with the states suing Microsoft pointed out that when it comes to the company's 
+	use of the Kerberos authentication specification, not everyone agrees.
+	</para>
+
+	<para>
+	<indexterm><primary>Kerberos</primary><secondary>unspecified fields</secondary></indexterm>
+	Robert Short, vice president of Windows core technology at Microsoft, wrote in his direct testimony prepared 
+	before his appearance that non-Microsoft operating systems can disregard the portion of the Kerberos version 
+	5 specification that Windows clients use for proprietary purposes and still achieve interoperability with 
+	the Microsoft OS. Microsoft takes advantage of unspecified fields in the Kerberos specification for storing 
+	Windows-specific authorization data, Short wrote. The designers of Kerberos left these fields undefined so 
+	that software developers could add their own authorization information, he said.
+	</para></blockquote>
+
+	<para>
+	<indexterm><primary>DCE</primary></indexterm>
+	<indexterm><primary>RPC</primary></indexterm>
+	It so happens that Microsoft Windows clients depend on and expect the contents of the <emphasis>unspecified
+	fields</emphasis> in the Kerberos 5 communications data stream for their Windows interoperability,
+	particularly when Samba is expected to emulate a Windows Server 200x domain controller. But the interoperability
+	issue goes far deeper than this. In the domain control protocols that are used by MS Windows XP Professional,
+	there is a tight interdependency between the Kerberos protocols and the Microsoft distributed computing environment
+	(DCE) RPCs that themselves are an integral part of the SMB/CIFS protocols as used by
+	Microsoft.
+	</para>
+
+	<para>
+	Microsoft makes the following comment in a reference in a
+	<ulink url="http://www.microsoft.com/technet/itsolutions/interop/mgmt/kerberos.asp">
+	technet</ulink> article:
+	</para>
+
+	  <blockquote><para><indexterm>
+		<primary>Privilege Attribute Certificates</primary>
+		<see>PAC</see>
+	      </indexterm><indexterm>
+		<primary>access control</primary>
+	      </indexterm>
+	The DCE Security Services are also layered on the Kerberos protocol. DCE authentication services use RPC 
+	representation of Kerberos protocol messages. In addition, DCE uses the authorization data field in Kerberos 
+	tickets to convey Privilege Attribute Certificates (PACs) that define user identity and group membership. 
+	The DCE PAC is used in a similar manner as Windows NT Security IDs for user authorization and access control. 
+	Windows NT services will not be able to translate DCE PACs into Windows NT user and group identifiers. This 
+	is not an issue with Kerberos interoperability, but rather an issue of interoperability between DCE and 
+	Windows NT access control information.
+	</para></blockquote>
+
+	</sect3>
+
+	</sect2>
+
+</sect1>
+
+<sect1 id="ch10expl">
+	<title>Implementation</title>
+
+	<para>
+	The following procedures outline the implementation of the security measures discussed so far.
+	</para>
+
+	<sect2>
+	<title>Share Access Controls</title>
+
+	<para><indexterm>
+	    <primary>Share Access Controls</primary>
+	  </indexterm><indexterm>
+	    <primary>filter</primary>
+	  </indexterm><indexterm>
+	    <primary>connection</primary>
+	  </indexterm>
+	Access control entries placed on the share itself act as a filter at the time a when CIFS/SMB client (such as
+	Windows XP Pro) attempts to make a connection to the Samba server.
+	</para>
+
+	<procedure>
+	<title>Create/Edit/Delete Share ACLs</title>
+	  <step><para><indexterm>
+		<primary>Domain Administrator</primary>
+	      </indexterm><indexterm>
+		<primary>account</primary>
+	      </indexterm>
+		From a Windows 200x/XP Professional workstation, log on to the domain using the Domain Administrator 
+		account (on Samba domains, this is usually the account called <constant>root</constant>).
+		</para></step>
+
+		<step><para>
+		Click 
+		<menuchoice>
+			<guimenu>Start</guimenu>
+			<guimenuitem>Settings</guimenuitem>
+			<guimenuitem>Control Panel</guimenuitem>
+			<guimenuitem>Administrative Tools</guimenuitem>
+			<guimenuitem>Computer Management</guimenuitem>
+		</menuchoice>.
+		</para></step>
+
+		<step><para>
+		In the left panel,
+		<menuchoice>
+			<guimenu>[Right mouse menu item] Computer Management (Local)</guimenu>
+			<guimenuitem>Connect to another computer ...</guimenuitem>
+			<guimenuitem>Browse...</guimenuitem>
+			<guimenuitem>Advanced</guimenuitem>
+			<guimenuitem>Find Now</guimenuitem>
+		</menuchoice>. In the lower panel, click on the name of the server you wish to
+		administer. Click <menuchoice>
+				<guimenu>OK</guimenu>
+				<guimenuitem>OK</guimenuitem>
+				<guimenuitem>OK</guimenuitem>
+	      </menuchoice>.<indexterm>
+		<primary>Computer Management</primary>
+	      </indexterm>
+		In the left panel, the entry <guimenu>Computer Management (Local)</guimenu> should now reflect
+		the change made. For example, if the server you are administering is called <constant>FRODO</constant>,
+		the Computer Management entry should now say <guimenu>Computer Management (FRODO)</guimenu>.
+		</para></step>
+
+		<step><para>
+		In the left panel, click <menuchoice>
+			<guimenu>Computer Management (FRODO)</guimenu>
+			<guimenuitem>[+] Shared Folders</guimenuitem>
+			<guimenuitem>Shares</guimenuitem>
+		</menuchoice>.
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>ACLs</primary>
+	      </indexterm><indexterm>
+		<primary>Share Permissions</primary>
+	      </indexterm>
+		In the right panel, double-click on the share on which you wish to set/edit ACLs. This
+		will bring up the Properties panel. Click the <guimenu>Share Permissions</guimenu> tab.
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>access control settings</primary>
+	      </indexterm><indexterm>
+		<primary>Everyone</primary>
+	      </indexterm><indexterm>
+		<primary>full control</primary>
+	      </indexterm><indexterm>
+		<primary>over-rule</primary>
+	      </indexterm><indexterm>
+		<primary>permissions</primary>
+	      </indexterm><indexterm>
+		<primary>rejected</primary>
+	      </indexterm>
+		You may now edit/add/remove access control settings. Be very careful. Many problems have been
+		created by people who decided that everyone should be rejected but one particular group should
+		have full control. This is a catch-22 situation because members of that particular group also
+		belong to the group <constant>Everyone</constant>, which therefore overrules any permissions
+		set for the permitted group.
+		</para></step>
+
+		<step><para>
+		When you are done with editing, close all panels by clicking through the <guimenu>OK</guimenu>
+		buttons.
+		</para></step>
+	</procedure>
+
+	</sect2>
+
+	<sect2>
+	<title>Share Definition Controls</title>
+
+	<para><indexterm>
+	    <primary>Share Definition</primary>
+	    <secondary>Controls</secondary>
+	  </indexterm><indexterm>
+	    <primary>check-point</primary>
+	  </indexterm><indexterm>
+	    <primary>pile-driver</primary>
+	  </indexterm><indexterm>
+	    <primary>credential</primary>
+	  </indexterm><indexterm>
+	    <primary>powers</primary>
+	  </indexterm><indexterm>
+	    <primary>privileges</primary>
+	  </indexterm>
+	Share-definition-based access controls can be used like a checkpoint or like a pile-driver. Just as a
+	checkpoint can be used to require someone who wants to get through to meet certain requirements, so
+	it is possible to require the user (or group the user belongs to) to meet specified credential-related 
+	objectives. It can be likened to a pile-driver by overriding default controls in that having met the 
+	credential-related objectives, the user can be granted powers and privileges that would not normally be 
+	available under default settings.
+	</para>
+
+	<para><indexterm>
+	    <primary>access controls</primary>
+	  </indexterm><indexterm>
+	    <primary>ACLs</primary>
+	  </indexterm><indexterm>
+	    <primary>share definition controls</primary>
+	  </indexterm><indexterm>
+	    <primary>hierarchy of control</primary>
+	  </indexterm>
+	It must be emphasized that the controls discussed here can act as a filter or give rights of passage
+	that act as a superstructure over normal directory and file access controls. However, share-level
+	ACLs act at a higher level than do share definition controls because the user must filter through the
+	share-level controls to get to the share-definition controls. The proper hierarchy of controls implemented
+	by Samba and Windows networking consists of:
+	</para>
+
+	<orderedlist>
+		<listitem><para>Share-level ACLs</para></listitem>
+		<listitem><para>Share-definition controls</para></listitem>
+		<listitem><para>Directory and file permissions</para></listitem>
+		<listitem><para>Directory and file POSIX ACLs</para></listitem>
+	</orderedlist>
+
+	<sect3>
+	<title>Checkpoint Controls</title>
+
+	  <para><indexterm>
+	      <primary>Checkpoint Controls</primary>
+	    </indexterm>
+	Consider the following extract from a &smb.conf; file defining the share called <constant>Apps</constant>:
+<screen>
+[Apps]
+	comment = Application Share
+	path = /data/apps
+	read only = Yes
+	valid users = @Employees
+</screen>
+	This definition permits only those who are members of the group called <constant>Employees</constant> to 
+	access the share.
+	</para>
+
+	  <note><para><indexterm>
+		<primary>Domain Member</primary>
+		<secondary>servers</secondary>
+	      </indexterm><indexterm>
+		<primary>winbind use default domain</primary>
+	      </indexterm><indexterm>
+		<primary>fully qualified</primary>
+	      </indexterm><indexterm>
+		<primary>valid users</primary>
+	      </indexterm><indexterm>
+		<primary>delimiter</primary>
+	      </indexterm>
+	On domain member servers and clients, even when the <parameter>winbind use default domain</parameter> has
+	been specified, the use of domain accounts in security controls requires fully qualified domain specification,
+	for example, <smbconfoption name="valid users">@"MEGANET\Northern Engineers"</smbconfoption>. 
+	Note the necessity to use the double quotes to avoid having the space in the Windows group name interpreted as a
+	delimiter. 
+	</para></note>
+
+	  <para><indexterm>
+	      <primary>ACL</primary>
+	    </indexterm><indexterm>
+	      <primary>access</primary>
+	    </indexterm><indexterm>
+	      <primary>validate</primary>
+	    </indexterm>
+	If there is an ACL on the share itself to permit read/write access for all <constant>Employees</constant>
+	as well as read/write for the group <constant>Doctors</constant>, both groups are permitted through
+	to the share. However, at the moment an attempt is made to set up a connection to the share, a member of
+	the group <constant>Doctors</constant>, who is not also a member of the group <constant>Employees</constant>,
+	would immediately fail to validate.
+	</para>
+
+	  <para><indexterm>
+	      <primary>share definition controls</primary>
+	    </indexterm>
+	Consider another example. In this case, you want to permit all members of the group <constant>Employees</constant>
+	except the user <constant>patrickj</constant> to access the <constant>Apps</constant> share. This can be
+	easily achieved by setting a share-level ACL permitting only <constant>Employees</constant> to access the share,
+	and then in the share definition controls excluding just <constant>patrickj</constant>. Here is how that might
+	be done:
+<screen>
+[Apps]
+        comment = Application Share
+        path = /data/apps
+        read only = Yes
+        invalid users = patrickj
+</screen>
+	    <indexterm>
+	      <primary>permissions</primary>
+	    </indexterm>
+	Let us assume that you want to permit the user <constant>gbshaw</constant> to manage any file in the
+	UNIX/Linux file system directory <filename>/data/apps</filename>, but you do not want to grant any write
+	permissions beyond that directory tree. Here is one way this can be done:
+<screen>
+[Apps]
+        comment = Application Share
+        path = /data/apps
+        read only = Yes
+        invalid users = patrickj
+        admin users = gbshaw
+</screen>
+	    <indexterm>
+	      <primary>administrative rights</primary>
+	    </indexterm>
+	Now we have a set of controls that permits only <constant>Employees</constant> who are also members of
+	the group <constant>Doctors</constant>, excluding the user <constant>patrickj</constant>, to have 
+	read-only privilege, but the user <constant>gbshaw</constant> is granted administrative rights.
+	The administrative rights conferred upon the user <constant>gbshaw</constant> permit operation as
+	if that user has logged in as the user <constant>root</constant> on the UNIX/Linux system and thus,
+	for access to the directory tree that has been shared (exported), permit the user to override controls
+	that apply to all other users on that resource.
+	</para>
+
+	<para>
+	There are additional checkpoint controls that may be used. For example, if for the same share we now
+	want to provide the user <constant>peters</constant> with the ability to write to one directory to
+	which he has write privilege in the UNIX file system, you can specifically permit that with the
+	following settings:
+<screen>
+[Apps]
+        comment = Application Share
+        path = /data/apps
+        read only = Yes
+        invalid users = patrickj
+        admin users = gbshaw
+        write list = peters
+</screen>
+	    <indexterm>
+	      <primary>check-point controls</primary>
+	    </indexterm>
+	This is a particularly complex example at this point, but it begins to demonstrate the possibilities.
+	You should refer to the online manual page for the &smb.conf; file for more information regarding
+	the checkpoint controls that Samba implements.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Override Controls</title>
+
+	  <para><indexterm>
+	      <primary>over-ride controls</primary>
+	    </indexterm>
+	Override controls implemented by Samba permit actions like the adoption of a different identity 
+	during file system operations, the forced overwriting of normal file and directory permissions,
+	and so on. You should refer to the online manual page for the &smb.conf; file for more information regarding
+        the override controls that Samba implements.
+	</para>
+
+	<para>
+	In the following example, you want to create a Windows networking share that any user can access.
+	However, you want all read and write operations to be performed as if the user <constant>billc</constant>
+	and member of the group <constant>Mentors</constant> read/write the files. Here is one way this
+	can be done:
+<screen>
+[someshare]
+	comment = Some Files Everyone May Overwrite
+	path = /data/somestuff
+	read only = No
+	force user = billc
+	force group = Mentors
+</screen>
+	    <indexterm>
+	      <primary>forced settings</primary>
+	    </indexterm><indexterm>
+	      <primary>overheads</primary>
+	    </indexterm>
+	That is all there is to it. Well, it is almost that simple. The downside of this method is that
+	users are logged onto the Windows client as themselves, and then immediately before accessing the
+	file, Samba makes system calls to change the effective user and group to the forced settings
+	specified, completes the file transaction, and then reverts to the actually logged-on identity.
+	This imposes significant overhead on Samba. The alternative way to effectively achieve the same result
+	(but with lower system CPU overheads) is described next.
+	</para>
+
+	  <para><indexterm>
+	      <primary>force user</primary>
+	    </indexterm><indexterm>
+	      <primary>force group</primary>
+	    </indexterm><indexterm>
+	      <primary>opportunistic</primary>
+	      <secondary>locking</secondary>
+	    </indexterm><indexterm>
+	      <primary>oplock break</primary>
+	    </indexterm><indexterm>
+	      <primary>performance degradation</primary>
+	    </indexterm>
+	The use of the <parameter>force user</parameter> or the <parameter>force group</parameter> may
+	also have a severe impact on system (particularly on Windows client) performance. If opportunistic
+	locking is enabled on the share (the default), it causes an <constant>oplock break</constant> to be
+	sent to the client even if the client has not opened the file. On networks that have high traffic
+	density, or on links that are routed to a remote network segment, <constant>oplock breaks</constant>
+	can be lost. This results in possible retransmission of the request, or the client may time-out while
+	waiting for the file system transaction (read or write) to complete. The result can be a profound
+	apparent performance degradation as the client continually attempts to reconnect to overcome the
+	effect of the lost <constant>oplock break</constant>, or time-out.
+	</para>
+	
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Share Point Directory and File Permissions</title>
+
+	<para><indexterm>
+	    <primary>security</primary>
+	  </indexterm><indexterm>
+	    <primary>privilege controls</primary>
+	  </indexterm><indexterm>
+	    <primary>permission</primary>
+	  </indexterm><indexterm>
+	    <primary>share definition controls</primary>
+	  </indexterm>
+	Samba has been designed and implemented so that it respects as far as is feasible the security and
+	user privilege controls that are built into the UNIX/Linux operating system. Samba does nothing
+	with respect to file system access that violates file system permission settings, unless it is
+	explicitly instructed to do otherwise through share definition controls. Given that Samba obeys
+	UNIX file system controls, this chapter does not document simple information that can be obtained
+	from a basic UNIX training guide. Instead, one common example of a typical problem is used
+	to demonstrate the most effective solution referred to in the immediately preceding paragraph.
+	</para>
+
+	<para><indexterm>
+	    <primary>Microsoft Office</primary>
+	  </indexterm><indexterm>
+	    <primary>Word</primary>
+	  </indexterm><indexterm>
+	    <primary>Excel</primary>
+	  </indexterm>
+	One of the common issues that repeatedly pops up on the Samba mailing lists involves the saving of
+	Microsoft Office files (Word and Excel) to a network drive. Here is the typical sequence:
+	</para>
+
+	<orderedlist>
+		<listitem><para>
+		A user opens a Work document from a network drive. The file was owned by user <constant>janetp</constant>
+		and <group>users</group>, and was set read/write-enabled for everyone.
+		</para></listitem>
+
+		<listitem><para>
+		File changes and edits are made.
+		</para></listitem>
+
+		<listitem><para>
+		The file is saved, and MS Word is closed.
+		</para></listitem>
+
+		<listitem><para>
+		The file is now owned by the user <constant>billc</constant> and group <constant>doctors</constant>,
+		and is set read/write by <constant>billc</constant>, read-only by <constant>doctors</constant>, and
+		no access by everyone.
+		</para></listitem>
+
+		<listitem><para>
+		The original owner cannot now access her own file and is <quote>justifiably</quote> upset.
+		</para></listitem>
+	</orderedlist>
+
+	<para>
+	There have been many postings over the years that report the same basic problem. Frequently Samba users
+	want to know when this <quote>bug</quote> will be fixed. The fact is, this is not a bug in Samba at all.
+	Here is the real sequence of what happens in this case.
+	</para>
+
+	<para><indexterm>
+	    <primary>MS Word</primary>
+	  </indexterm><indexterm>
+	    <primary>ownership</primary>
+	  </indexterm><indexterm>
+	    <primary>permissions</primary>
+	  </indexterm>
+	When the user saves a file, MS Word creates a new (temporary) file. This file is naturally owned
+	by the user who creates the file (<constant>billc</constant>) and has the permissions that follow
+	that user's default settings within the operating system (UNIX/Linux). When MS Word has finished writing
+	the file to disk, it then renames the new (temporary) file to the name of the old one. MS Word does not
+	change the ownership or permissions to what they were on the original file. The file is thus a totally
+	new file, and the old one has been deleted in the process.
+	</para>
+
+	<para>
+	Samba received a request to create a new file, and then to rename the file to a new name. The old file that
+	has the same name is now automatically deleted. Samba has no way of knowing that the new file should
+	perhaps have the same ownership and permissions as the old file. To Samba, these are entirely independent
+	operations.
+	</para>
+
+	<para>
+	The question is, <quote>How can we solve the problem?</quote>
+	</para>
+
+	<para>
+	The solution is simple. Use UNIX file system permissions and controls to your advantage. Follow these
+	simple steps to create a share in which all files will consistently be owned by the same user and the
+	same group:
+	</para>
+
+
+	<procedure>
+	<title>Using Directory Permissions to Force File User and Group Ownership</title>
+		<step><para>
+		Change your share definition so that it matches this pattern:
+<screen>
+[finance]
+        path = /usr/data/finance
+        browseable = Yes
+        read only = No
+</screen>
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>permissions</primary>
+		<secondary>user</secondary>
+	      </indexterm><indexterm>
+		<primary>permissions</primary>
+		<secondary>group</secondary>
+	      </indexterm>
+		Set consistent user and group permissions recursively down the directory tree as shown here:
+<screen>
+&rootprompt; chown -R janetp.users /usr/data/finance
+</screen>
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>accessible</primary>
+	      </indexterm>
+		Set the files and directory permissions to be read/write for owner and group, and not accessible
+		to others (everyone), using the following command:
+<screen>
+&rootprompt; chmod ug+rwx,o-rwx /usr/data/finance
+</screen>
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>SGID</primary>
+	      </indexterm>
+		Set the SGID (supergroup) bit on all directories from the top down. This means all files 
+		can be created with the permissions of the group set on the directory. It means all users 
+		who are members of the group <constant>finance</constant> can read and write all files in 
+		the directory. The directory is not readable or writable by anyone who is not in the 
+		<constant>finance</constant> group. Simply follow this example:
+<screen>
+&rootprompt; find /usr/data/finance -type d -exec chmod ug+s {}\;
+</screen>
+
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>group membership</primary>
+	      </indexterm><indexterm>
+		<primary>primary group</primary>
+	      </indexterm><indexterm>
+		<primary>/etc/passwd</primary>
+	      </indexterm>
+		Make sure all users that must have read/write access to the directory have 
+		<constant>finance</constant> group membership as their primary group, 
+		for example, the group they belong to in <filename>/etc/passwd</filename>.
+		</para></step>
+	</procedure>
+
+	</sect2>
+
+	<sect2>
+	<title>Managing Windows 200x ACLs</title>
+
+	<para><indexterm>
+	    <primary>translate</primary>
+	  </indexterm><indexterm>
+	    <primary>Windows 2000 ACLs</primary>
+	  </indexterm><indexterm>
+	    <primary>Posix ACLs</primary>
+	  </indexterm><indexterm>
+	    <primary>side effects</primary>
+	  </indexterm>
+	Samba must translate Windows 2000 ACLs to UNIX POSIX ACLs. This has some interesting side effects because
+	there is not a one-to-one equivalence between them. The as-close-as-possible ACLs match means
+	that some transactions are not possible from MS Windows clients. One of these is to reset the ownership
+	of directories and files. If you want to reset ownership, this must be done from a UNIX/Linux login.
+	</para>
+
+	<para>
+	There are two possible ways to set ACLs on UNIX/Linux file systems from a Windows network workstation,
+	either via File Manager or via the Microsoft Management Console (MMC) Computer Management interface.
+	</para>
+
+	<sect3>
+	<title>Using the MMC Computer Management Interface</title>
+
+	<procedure>
+		<step><para>
+		From a Windows 200x/XP Professional workstation, log on to the domain using the Domain Administrator 
+		account (on Samba domains, this is usually the account called <constant>root</constant>).
+		</para></step>
+
+		<step><para>
+		Click 
+		<menuchoice>
+			<guimenu>Start</guimenu>
+			<guimenuitem>Settings</guimenuitem>
+			<guimenuitem>Control Panel</guimenuitem>
+			<guimenuitem>Administrative Tools</guimenuitem>
+			<guimenuitem>Computer Management</guimenuitem>
+		</menuchoice>.
+		</para></step>
+
+		<step><para>
+		In the left panel,
+		<menuchoice>
+			<guimenu>[Right mouse menu item] Computer Management (Local)</guimenu>
+			<guimenuitem>Connect to another computer ...</guimenuitem>
+			<guimenuitem>Browse...</guimenuitem>
+			<guimenuitem>Advanced</guimenuitem>
+			<guimenuitem>Find Now</guimenuitem>
+		</menuchoice>. In the lower panel, click on the name of the server you wish to
+		administer. Click <menuchoice>
+				<guimenu>OK</guimenu>
+				<guimenuitem>OK</guimenuitem>
+				<guimenuitem>OK</guimenuitem>
+		</menuchoice>.
+		In the left panel, the entry <guimenu>Computer Management (Local)</guimenu> should now reflect
+		the change made. For example, if the server you are administering is called <constant>FRODO</constant>,
+		the Computer Management entry should now say: <guimenu>Computer Management (FRODO)</guimenu>.
+		</para></step>
+
+		<step><para>
+		In the left panel, click <menuchoice>
+			<guimenu>Computer Management (FRODO)</guimenu>
+			<guimenuitem>[+] Shared Folders</guimenuitem>
+			<guimenuitem>Shares</guimenuitem>
+		</menuchoice>.
+		</para></step>
+
+	    <step><para><indexterm>
+		  <primary>Security</primary>
+		</indexterm><indexterm>
+		  <primary>Properties</primary>
+		</indexterm><indexterm>
+		  <primary>Permissions</primary>
+		</indexterm><indexterm>
+		  <primary>Samba Domain server</primary>
+		</indexterm>
+		In the right panel, double-click on the share on which you wish to set/edit ACLs. This
+		brings up the Properties panel. Click the <guimenu>Security</guimenu> tab. It is best
+		to edit ACLs using the <constant>Advanced</constant> editing features. Click the 
+		<guimenu>Advanced</guimenu> button. This opens a panel that has four tabs. Only the 
+		functionality under the <constant>Permissions</constant> tab can be utilized with respect 
+		to a Samba domain server.
+		</para></step>
+
+	    <step><para><indexterm>
+		  <primary>access control</primary>
+		</indexterm><indexterm>
+		  <primary>permitted group</primary>
+		</indexterm>
+		You may now edit/add/remove access control settings. Be very careful. Many problems have been
+		created by people who decided that everyone should be rejected but one particular group should
+		have full control. This is a catch-22 situation because members of that particular group also
+		belong to the group <constant>Everyone</constant>, which therefore overrules any permissions
+		set for the permitted group.
+		</para></step>
+
+		<step><para>
+		When you are done with editing, close all panels by clicking through the <guimenu>OK</guimenu>
+		buttons until the last panel closes.
+		</para></step>
+	</procedure>
+	
+	</sect3>
+
+	<sect3>
+	<title>Using MS Windows Explorer (File Manager)</title>
+
+	<para>
+	The following alternative method may be used from a Windows workstation. In this example we work
+	with a domain called <constant>MEGANET</constant>, a server called <constant>MASSIVE</constant>, and a
+	share called <constant>Apps</constant>. The underlying UNIX/Linux share point for this share is
+	<filename>/data/apps</filename>.
+	</para>
+
+	<procedure>
+		<step><para>
+		Click <menuchoice>
+			<guimenu>Start</guimenu>
+			<guimenuitem>[right-click] My Computer</guimenuitem>
+			<guimenuitem>Explore</guimenuitem>
+			<guimenuitem>[left panel] [+] My Network Places</guimenuitem>
+			<guimenuitem>[+] Entire Network</guimenuitem>
+			<guimenuitem>[+] Microsoft Windows Network</guimenuitem>
+			<guimenuitem>[+] Meganet</guimenuitem>
+			<guimenuitem>[+] Massive</guimenuitem>
+			<guimenuitem>[right-click] Apps</guimenuitem>
+			<guimenuitem>Properties</guimenuitem>
+			<guimenuitem>Security</guimenuitem>
+			<guimenuitem>Advanced</guimenuitem>
+		</menuchoice>. This opens a panel that has four tabs. Only the functionality under the 
+		<constant>Permissions</constant> tab can be utilized for a Samba domain server.
+		</para></step>
+
+	    <step><para><indexterm>
+		  <primary>full control</primary>
+		</indexterm><indexterm>
+		  <primary>over-rule</primary>
+		</indexterm>
+                You may now edit/add/remove access control settings. Be very careful. Many problems have been
+                created by people who decided that everyone should be rejected but one particular group should
+                have full control. This is a catch-22 situation because members of that particular group also
+                belong to the group <constant>Everyone</constant>, which therefore overrules any permissions
+                set for the permitted group.
+                </para></step>
+
+                <step><para>
+                When you are done with editing, close all panels by clicking through the <guimenu>OK</guimenu>
+                buttons until the last panel closes.
+                </para></step>
+	</procedure>
+
+	</sect3>
+
+	<sect3>
+	<title>Setting Posix ACLs in UNIX/Linux</title>
+
+	  <para><indexterm>
+	      <primary>desired security setting</primary>
+	    </indexterm><indexterm>
+	      <primary>shared resource</primary>
+	    </indexterm>
+	Yet another alternative method for setting desired security settings on the shared resource files and
+	directories can be achieved by logging into UNIX/Linux and setting POSIX ACLs directly using command-line
+	tools. Here is an example session on the same resource as in the immediately preceding example on a SUSE 9
+	Linux system:
+	</para>
+
+	<procedure>
+		<step><para>
+		Log into the Linux system as the user <constant>root</constant>.
+		</para></step>
+
+		<step><para>
+		Change directory to the location of the exported (shared) Windows file share (Apps), which is in
+		the directory <filename>/data</filename>. Execute the following:
+<screen>
+&rootprompt; cd /data
+</screen>
+		Retrieve the existing POSIX ACLs entry by executing:
+<screen>
+&rootprompt; getfacl apps
+# file: apps
+# owner: root
+# group: root
+user::rwx
+group::rwx
+other::r-x
+</screen>
+		</para></step>
+
+	    <step><para><indexterm>
+		  <primary>recursively</primary>
+		</indexterm>
+		You want to add permission for <constant>AppsMgrs</constant> to enable them to
+		manage the applications (apps) share. It is important to set the ACL recursively
+		so that the AppsMgrs have this capability throughout the directory tree that is 
+		being shared. This is done using the <constant>-R</constant> option as shown.
+		Execute the following:
+<screen>
+&rootprompt; setfacl -m -R group:AppsMgrs:rwx /data/apps
+</screen>
+		Because setting an ACL does not provide a response, you immediately validate the command executed
+		as follows:
+<screen>
+&rootprompt; getfacl /data/apps
+# file: apps
+# owner: root
+# group: root
+user::rwx
+group::rwx
+group:AppsMgrs:rwx
+mask::rwx
+other::r-x
+</screen>
+		This confirms that the change of POSIX ACL permissions has been effective.
+		</para></step>
+
+	    <step><para><indexterm>
+		  <primary>setfacl</primary>
+		</indexterm><indexterm>
+		  <primary>getfacl</primary>
+		</indexterm><indexterm>
+		  <primary>directory tree</primary>
+		</indexterm><indexterm>
+		  <primary>Windows ACLs</primary>
+		</indexterm><indexterm>
+		  <primary>inheritance</primary>
+		</indexterm>
+		It is highly recommended that you read the online manual page for the <command>setfacl</command>
+		and <command>getfacl</command> commands. This provides information regarding how to set/read the default
+		ACLs and how that may be propagated through the directory tree. In Windows ACLs terms, this is the equivalent
+		of setting <constant>inheritance</constant> properties.
+		</para></step>
+	</procedure>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+		<title>Key Points Learned</title>
+
+		<para>
+		The mish-mash of issues were thrown together into one chapter because it seemed like a good idea.
+		Looking back, this chapter could be broken into two, but it's too late now. It has been done.
+		The highlights covered are as follows:
+		</para>
+
+		<itemizedlist>
+	  <listitem><para><indexterm>
+		<primary>Winbind</primary>
+	      </indexterm><indexterm>
+		<primary>Active Directory</primary>
+	      </indexterm><indexterm>
+		<primary>password change</primary>
+	      </indexterm><indexterm>
+		<primary>logon hours</primary>
+	      </indexterm>
+			Winbind honors and does not override account controls set in Active Directory.
+			This means that password change, logon hours, and so on, are (or soon will be) enforced
+			by Samba winbind. At this time, an out-of-hours login is denied and password
+			change is enforced. At this time, if logon hours expire, the user is not forcibly
+			logged off. That may be implemented at some later date.
+			</para></listitem>
+
+	  <listitem><para><indexterm>
+		<primary>Sign'n'seal</primary>
+	      </indexterm><indexterm>
+		<primary>schannel</primary>
+	      </indexterm>
+			Sign'n'seal (plus schannel support) has been implemented in Samba-3. Beware of potential
+			problems acknowledged by Microsoft as having been fixed but reported by some as still
+			possibly an open issue.
+			</para></listitem>
+
+	  <listitem><para><indexterm>
+		<primary>Kerberos</primary>
+	      </indexterm><indexterm>
+		<primary>OpenLDAP</primary>
+	      </indexterm><indexterm>
+		<primary>Active Directory</primary>
+	      </indexterm><indexterm>
+		<primary>inter-operability</primary>
+	      </indexterm>
+			The combination of Kerberos 5, plus OpenLDAP, plus Samba, cannot replace Microsoft
+			Active Directory. The possibility to do this is not planned in the current Samba-3
+			roadmap. Samba-3 does aim to provide further improvements in interoperability so that
+			UNIX/Linux systems may be fully integrated into Active Directory domains.
+			</para></listitem>
+
+			<listitem><para>
+			This chapter reviewed mechanisms by which Samba servers may be kept secure. Each of
+			the four key methodologies was reviewed with specific reference to example deployment
+			techniques.
+			</para></listitem>
+		</itemizedlist>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	</para>
+
+	<qandaset defaultlabel="chap10qa" type="number">
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>Sign'n'seal</primary>
+	      </indexterm><indexterm>
+		<primary>registry hacks</primary>
+	      </indexterm>
+		Does Samba-3 require the <constant>Sign'n'seal</constant> registry hacks needed by Samba-2?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>schannel</primary>
+	      </indexterm><indexterm>
+		<primary>Sign'n'seal</primary>
+	      </indexterm><indexterm>
+		<primary>registry change</primary>
+	      </indexterm>
+		No. Samba-3 fully supports <constant>Sign'n'seal</constant> as well as <constant>schannel</constant>
+		operation. The registry change should not be applied when Samba-3 is used as a domain controller.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Does Samba-3 support Active Directory?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>Active Directory</primary>
+	      </indexterm>
+		Yes. Samba-3 can be a fully participating native mode Active Directory client. Samba-3 does not
+		provide Active Directory services. It cannot be used to replace a Microsoft Active Directory
+		server implementation. Samba-3 can function as an Active Directory client (workstation) toolkit,
+		and it can function as an Active Directory domain member server.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>mixed-mode</primary>
+	      </indexterm>
+		When Samba-3 is used with Active Directory, is it necessary to run mixed-mode operation, as was
+		necessary with Samba-2?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>native</primary>
+	      </indexterm>
+		No. Samba-3 can be used with NetBIOS over TCP/IP disabled, just as can be done with Windows 200x
+		Server and 200x/XPPro client products. It is no longer necessary to run mixed-mode operation,
+		because Samba-3 can join a native Windows 2003 Server ADS domain.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>share level access controls</primary>
+	      </indexterm>
+		Is it safe to set share-level access controls in Samba?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Yes. Share-level access controls have been supported since early versions of Samba-2. This is
+		very mature technology. Not enough sites make use of this powerful capability, neither on
+		Windows server or with Samba servers.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>share ACLs</primary>
+	      </indexterm>
+		Is it mandatory to set share ACLs to get a secure Samba-3 server?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>file system security</primary>
+	      </indexterm><indexterm>
+		<primary>Windows 200x ACLs</primary>
+	      </indexterm><indexterm>
+		<primary>share definition controls</primary>
+	      </indexterm><indexterm>
+		<primary>share level ACL</primary>
+	      </indexterm><indexterm>
+		<primary>security</primary>
+	      </indexterm>
+		No. Samba-3 honors UNIX/Linux file system security, supports Windows 200x ACLs, and provides 
+		means of securing shares through share definition controls in the &smb.conf; file. The additional
+		support for share-level ACLs is like frosting on the cake. It adds to security but is not essential
+		to it.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>valid users</primary>
+	      </indexterm>
+		The <parameter>valid users</parameter> did not work on the <smbconfsection name="[homes]"/>.
+		Has this functionality been restored yet?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>meta-service</primary>
+	      </indexterm>
+		Yes. This was fixed in Samba-3.0.2. The use of this parameter is strongly recommended as a safeguard
+		on the <smbconfsection name="[homes]"/> meta-service. The correct way to specify this is:
+		<smbconfoption name="valid users">%S</smbconfoption>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>force user</primary>
+	      </indexterm><indexterm>
+		<primary>force group</primary>
+	      </indexterm><indexterm>
+		<primary>bias</primary>
+	      </indexterm>
+		Is the bias against use of the <parameter>force user</parameter> and <parameter>force group</parameter>
+		really warranted?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>performance</primary>
+	      </indexterm>
+		There is no bias. There is a determination to recommend the right tool for the task at hand.
+		After all, it is better than putting users through performance problems, isn't it?
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		The example given for file and directory access control forces all files to be owned by one
+		particular user. I do not like that. Is there any way I can see who created the file?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>SUID</primary>
+	      </indexterm>
+		Sure. You do not have to set the SUID bit on the directory. Simply execute the following command
+		to permit file ownership to be retained by the user who created it:
+<screen>
+&rootprompt; find /usr/data/finance -type d -exec chmod g+s {}\;
+</screen>
+		Note that this required no more than removing the <constant>u</constant> argument so that the
+		SUID bit is not set for the owner.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>Computer Management</primary>
+	      </indexterm>
+		In the book, <quote>The Official Samba-3 HOWTO and Reference Guide</quote>, you recommended use
+		of the Windows NT4 Server Manager (part of the <filename>SRVTOOLS.EXE</filename>) utility. Why
+		have you mentioned only the use of the Windows 200x/XP MMC Computer Management utility?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>MMC</primary>
+	      </indexterm><indexterm>
+		<primary>SRVTOOLS.EXE</primary>
+	      </indexterm>
+		Either tool can be used with equal effect. There is no benefit of one over the other, except that
+		the MMC utility is present on all Windows 200x/XP systems and does not require additional software
+		to be downloaded and installed. Note that if you want to manage user and group accounts in your
+		Samba-controlled domain, the only tool that permits that is the NT4 Domain User Manager, which
+		is provided as part of the <filename>SRVTOOLS.EXE</filename> utility.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>valid users</primary>
+	      </indexterm><indexterm>
+		<primary>Active Directory</primary>
+	      </indexterm><indexterm>
+		<primary>Domain Member server</primary>
+	      </indexterm>
+		I tried to set <parameter>valid users = @Engineers</parameter>, but it does not work. My Samba
+		server is an Active Directory domain member server. Has this been fixed now?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The use of this parameter has always required the full specification of the domain account, for
+		example, <parameter>valid users = @"MEGANET2\Domain Admins"</parameter>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	</qandaset>
+
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-MakingHappyUsers.xml b/docs-xml/Samba3-ByExample/SBE-MakingHappyUsers.xml
new file mode 100644
index 00000000000..9ea500403b3
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-MakingHappyUsers.xml
@@ -0,0 +1,4518 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="happy">
+  <title>Making Happy Users</title>
+
+	<para>
+	It is said that <quote>a day that is without troubles is not fulfilling.  Rather, give 
+	me a day of troubles well handled so that I can be content with my achievements.</quote>
+	</para>
+
+	<para>
+	In the world of computer networks, problems are as varied as the people who create them
+	or experience them. The design of the network implemented in <link linkend="Big500users"/>
+	may create problems for some network users. The following lists some of the problems that
+	may occur:
+	</para>
+
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>network bandwidth</primary><secondary>utilization</secondary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>user account</primary></indexterm>
+	<indexterm><primary>PDC/BDC ratio</primary></indexterm>
+<caution><para>
+A significant number of network administrators have responded to the guidance given
+here. It should be noted that there are sites that have a single PDC for many hundreds of
+concurrent network clients. Network bandwidth, network bandwidth utilization, and server load
+are among the factors that determine the maximum number of Windows clients that
+can be served by a single domain controller (PDC or BDC) on a network segment. It is possible
+to operate with only a single PDC over a routed network. What is possible is not necessarily
+<emphasis>best practice</emphasis>. When Windows client network logons begin to fail with
+the message that the domain controller cannot be found or that the user account cannot
+be found (when you know it exists), that may be an indication that the domain controller is
+overloaded or network bandwidth is overloaded. The guidance given for PDC/BDC ratio to Windows
+clients is conservative and if followed will minimize problems &smbmdash; but it is not absolute.
+</para></caution>
+
+	<variablelist>
+		<varlistentry>
+		<term>Users experiencing difficulty logging onto the network</term>
+		<listitem><para>
+		<indexterm><primary>network</primary><secondary>logon</secondary></indexterm>
+		<indexterm><primary>multiple domain controllers</primary></indexterm>
+		When a Windows client logs onto the network, many data packets are exchanged
+		between the client and the server that is providing the network logon services.
+		Each request between the client and the server must complete within a specific
+		time limit. This is one of the primary factors that govern the installation of
+		multiple domain controllers (usually called secondary or backup controllers).
+		As a rough rule, there should be one such backup controller for every
+		30 to 150 clients. The actual limits are determined by network operational
+		characteristics. 
+		</para>
+
+		<para>
+		<indexterm><primary>PDC</primary></indexterm>
+		<indexterm><primary>BDC</primary></indexterm>
+		<indexterm><primary>clients per DC</primary></indexterm>
+		If the domain controller provides only network logon services
+		and all file and print activity is handled by domain member servers, one domain	
+		controller per 150 clients on a single network segment may suffice. In any
+		case, it is highly recommended to have a minimum of one domain controller (PDC or BDC)
+		per network segment. It is better to have at least one BDC on the network
+		segment that has a PDC. If the domain controller is also used as a file and
+		print server, the number of clients it can service reliably is reduced,
+		and generally for low powered hardware should not exceed 30 machines (Windows 
+		workstations plus domain member servers) per domain controller. Many sites are
+		able to operate with more clients per domain controller, the number of clients
+		that can be supported is limited by the CPU speed, memory and the workload on
+		the Samba server as well as network bandwidth utilization.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Slow logons and log-offs</term>
+		<listitem><para>
+		<indexterm><primary>slow logon</primary></indexterm>
+		Slow logons and log-offs may be caused by many factors that include:
+
+			<itemizedlist>
+				<listitem><para>
+				<indexterm><primary>NetBIOS</primary><secondary>name resolution</secondary><tertiary>delays</tertiary></indexterm>
+				<indexterm><primary>WINS</primary><secondary>server</secondary></indexterm>
+				Excessive delays in the resolution of a NetBIOS name to its IP
+				address. This may be observed when an overloaded domain controller 
+				is also the WINS server. Another cause may be the failure to use
+				a WINS server (this assumes that there is a single network segment).
+				</para></listitem>
+
+				<listitem><para>
+				<indexterm><primary>traffic collisions</primary></indexterm>
+				<indexterm><primary>HUB</primary></indexterm>
+				<indexterm><primary>ethernet switch</primary></indexterm>
+				Network traffic collisions due to overloading of the network
+				segment. One short-term workaround to this may be to replace
+				network HUBs with Ethernet switches.
+				</para></listitem>
+
+				<listitem><para>
+				<indexterm><primary>networking hardware</primary><secondary>defective</secondary></indexterm>
+				Defective networking hardware. Over the past few years, we have seen
+				on the Samba mailing list a significant increase in the number of
+				problems that were traced to a defective network interface controller,
+				a defective HUB or Ethernet switch, or defective cabling. In most cases,
+				it was the erratic nature of the problem that ultimately pointed to
+				the cause of the problem.
+				</para></listitem>
+
+				<listitem><para>
+				<indexterm><primary>profile</primary><secondary>roaming</secondary></indexterm>
+				<indexterm><primary>MS Outlook</primary><secondary>PST file</secondary></indexterm>
+				Excessively large roaming profiles. This type of problem is typically
+				the result of poor user education as well as poor network management.
+				It can be avoided by users not storing huge quantities of email in
+				MS Outlook PST files as well as by not storing files on the desktop.
+				These are old bad habits that require much discipline and vigilance
+				on the part of network management.
+				</para></listitem>
+
+				<listitem><para>
+				<indexterm><primary>WebClient</primary></indexterm>
+				You should verify that the Windows XP WebClient service is not running.
+				The use of the WebClient service has been implicated in many Windows
+				networking-related problems.
+				</para></listitem>
+			</itemizedlist>
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Loss of access to network drives and printer resources</term>
+		<listitem><para>
+		Loss of access to network resources during client operation may be caused by a number
+		of factors, including:
+		</para>
+
+			<itemizedlist>
+				<listitem><para>
+				<indexterm><primary>network</primary><secondary>overload</secondary></indexterm>
+				Network overload (typically indicated by a high network collision rate)
+				</para></listitem>
+
+				<listitem><para>
+				Server overload
+				</para></listitem>
+
+				<listitem><para>
+				<indexterm><primary>network</primary><secondary>timeout</secondary></indexterm>
+				Timeout causing the client to close a connection that is in use but has
+				been latent (no traffic) for some time (5 minutes or more)
+				</para></listitem>
+
+				<listitem><para>
+				<indexterm><primary>network hardware</primary><secondary>defective</secondary></indexterm>
+				Defective networking hardware
+				</para></listitem>
+			</itemizedlist>
+
+		<para>
+		<indexterm><primary>data</primary><secondary>corruption</secondary></indexterm>
+		No matter what the cause, a sudden loss of access to network resources can
+		result in BSOD (blue screen of death) situations that necessitate rebooting of the client
+		workstation. In the case of a mild problem, retrying to access the network drive of the printer
+		may restore operations, but in any case this is a serious problem that may lead to the next
+		problem, data corruption.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Potential data corruption</term>
+		<listitem><para>
+		<indexterm><primary>data</primary><secondary>corruption</secondary></indexterm>
+		Data corruption is one of the most serious problems. It leads to uncertainty, anger, and 
+		frustration, and generally precipitates immediate corrective demands. Management response
+		to this type of problem may be rational, as well as highly irrational. There have been
+		cases where management has fired network staff for permitting this situation to occur without 
+		immediate correction. There have been situations where perfectly functional hardware was thrown 
+		out and replaced, only to find the problem caused by a low-cost network hardware item. There 
+		have been cases where server operating systems were replaced, or where Samba was updated, 
+		only to later isolate the problem due to defective client software.
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>
+	In this chapter, you can work through a number of measures that significantly arm you to
+	anticipate and combat network performance issues. You can work through complex and thorny
+	methods to improve the reliability of your network environment, but be warned that all such steps
+	demand the price of complexity.
+	</para>
+
+<sect1>
+<title>Regarding LDAP Directories and Windows Computer Accounts</title>
+
+	<para>
+	<indexterm><primary>LDAP</primary><secondary>directory</secondary></indexterm>
+	Computer (machine) accounts can be placed wherever you like in an LDAP directory subject to some 
+	constraints that are described in this section.
+	</para>
+
+	<para>
+	<indexterm><primary>POSIX</primary></indexterm>
+	<indexterm><primary>SambaSAMAccount</primary></indexterm>
+	<indexterm><primary>machine account</primary></indexterm>
+	<indexterm><primary>trust account</primary></indexterm>
+	The POSIX and SambaSAMAccount components of computer (machine) accounts are both used by Samba. 
+	That is, machine  accounts are treated inside Samba in the same way that Windows NT4/200X treats 
+	them. A user account and a machine account are indistinguishable from each other, except that
+	the machine account ends in a $ character, as do trust accounts.
+	</para>
+
+	<para>
+	<indexterm><primary>account</primary></indexterm>
+	<indexterm><primary>UID</primary></indexterm>
+	The need for Windows user, group, machine, trust, and other such accounts to be tied to a valid UNIX UID
+	is a design decision that was made a long way back in the history of Samba development. It is 
+	unlikely that this decision will be reversed or changed during the remaining life of the 
+	Samba-3.x series. 
+	</para>
+
+	<para>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>NSS</primary></indexterm>
+	The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that
+	must refer back to the host operating system on which Samba is running. The name service
+	switch (NSS) is the preferred mechanism that shields applications (like Samba) from the
+	need to know everything about every host OS it runs on.
+	</para>
+
+	<para>
+	Samba asks the host OS to provide a UID via the <quote>passwd</quote>, <quote>shadow</quote>
+	and <quote>group</quote> facilities in the NSS control (configuration) file. The best tool
+	for achieving this is left up to the UNIX administrator to determine. It is not imposed by
+	Samba. Samba provides winbindd together with its support libraries as one method. It is
+	possible to do this via LDAP, and for that Samba provides the appropriate hooks so that
+	all account entities can be located in an LDAP directory.
+	</para>
+
+	<para>
+	<indexterm><primary>nss_ldap</primary></indexterm>
+	For many the weapon of choice is to use the PADL nss_ldap utility. This utility must
+	be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That
+	is fundamentally an LDAP design question.  The information provided on the Samba list and
+	in the documentation is directed at providing working examples only. The design
+	of an LDAP directory is a complex subject that is beyond the scope of this documentation.
+	</para>
+
+</sect1>
+
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>
+	You just opened an email from Christine that reads:
+	</para>
+
+	<para>
+	Good morning,
+	<blockquote><attribution>Christine</attribution><para>
+	A few months ago we sat down to design the network. We discussed the challenges ahead and we all
+	agreed to compromise our design to keep it simple. We knew there would be problems, but anticipated
+	that we would have some time to resolve any issues that might be encountered.
+	</para>
+
+	<para>
+	As you now know, we started off on the wrong foot. We have a lot of unhappy users. One of them
+	resigned yesterday afternoon because she was under duress to complete some critical projects. She
+	suffered a blue screen of death situation just as she was finishing four hours of intensive work, all
+	of which was lost. She has a unique requirement that involves storing large files on her desktop.
+	Mary's desktop profile is nearly 1 GB in size. As a result of her desktop configuration, it
+	takes her nearly 15 minutes just to log onto her workstation. But that is not enough. Because all
+	network logon traffic passes over the network links between our buildings, logging on may take
+	three or four attempts due to blue screen problems associated with network timeouts.
+	</para>
+
+	<para>
+	A few of us worked to help her out of trouble. We convinced her to stay and promised to fully 
+	resolve the difficulties she is facing. We have no choice. We must implement LDAP and set hard 
+	limits on what our users can do with their desktops. Otherwise, we face staff losses 
+	that can surely do harm to our growth as well as to staff morale. I am sure we can better deal 
+	with the consequences of what we know we must do than we can with the unrest we have now.
+	</para>
+
+	<para>
+	Stan and I have discussed the current situation. We are resolved to help our users and protect
+	the well being of Abmas. Please acknowledge this advice with consent to proceed as required to
+	regain control of our vital IT operations.
+	</para></blockquote>
+	</para>
+
+	<para>
+	<indexterm><primary>compromise</primary></indexterm>	
+	<indexterm><primary>network</primary><secondary>multi-segment</secondary></indexterm>
+	Every compromise has consequences. Having a large routed (i.e., multisegment) network with only a
+	single domain controller is a poor design that has obvious operational effects that may
+	frustrate users. Here is your reply:
+	</para>
+
+	<blockquote><attribution>Bob</attribution><para>
+	Christine, Your diligence and attention to detail are much valued. Stan and I fully support your
+	proposals to resolve the issues. I am confident that your plans fully realized will significantly
+	boost staff morale. Please go ahead with your plans. If you have any problems, please let me know.
+	Please let Stan know what the estimated cost will be so I can approve the expense. Do not wait
+	for approval; I appreciate the urgency.
+	</para></blockquote>
+
+	<sect2>
+		<title>Assignment Tasks</title>
+
+		<para>
+		The priority of assigned tasks in this chapter is:
+		</para>
+
+		<orderedlist>
+			<listitem><para>
+			<indexterm><primary>Backup Domain Controller</primary><see>BDC</see></indexterm>
+			<indexterm><primary>BDC</primary></indexterm>
+			<indexterm><primary>tdbsam</primary></indexterm>
+			<indexterm><primary>LDAP</primary></indexterm><indexterm><primary>migration</primary></indexterm>
+			Implement Backup Domain Controllers (BDCs) in each building. This involves
+			a change from a <emphasis>tdbsam</emphasis> backend that was used in the previous
+			chapter to an LDAP-based backend.
+			</para>
+
+			<para>
+			You can implement a single central LDAP server for this purpose.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>logon time</primary></indexterm>
+			<indexterm><primary>network share</primary></indexterm>
+			<indexterm><primary>default profile</primary></indexterm>
+			<indexterm><primary>profile</primary><secondary>default</secondary></indexterm>
+			Rectify the problem of excessive logon times. This involves redirection of
+			folders to network shares as well as modification of all user desktops to
+			exclude the redirected folders from being loaded at login time. You can also
+			create a new default profile that can be used for all new users.
+			</para></listitem>
+		</orderedlist>
+
+		<para>
+		<indexterm><primary>disk image</primary></indexterm>
+		You configure a new MS Windows XP Professional workstation disk image that you roll out
+		to all desktop users. The instructions you have created are followed on a staging machine
+		from which all changes can be carefully tested before inflicting them on your network users.
+		</para>
+
+		<para>
+		<indexterm><primary>CUPS</primary></indexterm>
+		This is the last network example in which specific mention of printing is made. The example
+		again makes use of the CUPS printing system.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Dissection and Discussion</title>
+
+	<para>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>OpenLDAP</primary></indexterm>
+	The implementation of Samba BDCs necessitates the installation and configuration of LDAP.
+	For this site, you use OpenLDAP, the open source software LDAP server platform. Commercial
+	LDAP servers in current use with Samba-3 include:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		<indexterm><primary>eDirectory</primary></indexterm>
+		Novell <ulink url="http://www.novell.com/products/edirectory/">eDirectory</ulink>
+		is being successfully used by some sites. Information on how to use eDirectory can be
+		obtained from the Samba mailing lists or from Novell.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>Tivoli Directory Server</primary></indexterm>
+		IBM <ulink url="http://www-306.ibm.com/software/tivoli/products/directory-server/">Tivoli 
+		Directory Server</ulink> can be used to provide the Samba LDAP backend. Example schema 
+		files are provided in the Samba source code tarball under the directory 
+		<filename>~samba/example/LDAP.</filename>
+		</para></listitem> 
+
+		<listitem><para>
+		<indexterm><primary>Sun ONE Identity Server</primary></indexterm>
+		Sun <ulink url="http://www.sun.com/software/software/products/identity_srvr/home_identity.xml">ONE Identity 
+		Server product suite</ulink> provides an LDAP server that can be used for Samba.
+		Example schema files are provided in the Samba source code tarball under the directory
+		<filename>~samba/example/LDAP.</filename>
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	A word of caution is fully in order. OpenLDAP is purely an LDAP server, and unlike commercial
+	offerings, it requires that you manually edit the server configuration files and manually
+	initialize the LDAP directory database. OpenLDAP itself has only command-line tools to
+	help you to get OpenLDAP and Samba-3 running as required, albeit with some learning curve challenges.
+	</para>
+
+	<para>
+	<indexterm><primary>Active Directory</primary></indexterm>
+	For most sites, the deployment of Microsoft Active Directory from the shrink-wrapped installation is quite
+	adequate. If you are migrating from Microsoft Active Directory, be warned that OpenLDAP does not include
+	GUI-based directory management tools. Even a simple task such as adding users to the OpenLDAP database 
+	requires an understanding of what you are doing, why you are doing it, and the tools that you must use.
+	</para>
+
+	<para>
+	<indexterm><primary>Identity Management</primary></indexterm>
+	<indexterm><primary>high availability</primary></indexterm>
+	<indexterm><primary>directory</primary><secondary>replication</secondary></indexterm>
+	<indexterm><primary>directory</primary><secondary>synchronization</secondary></indexterm>
+	<indexterm><primary>performance</primary></indexterm>
+	<indexterm><primary>directory</primary><secondary>management</secondary></indexterm>
+	<indexterm><primary>directory</primary><secondary>schema</secondary></indexterm>
+	When installed and configured, an OpenLDAP Identity Management backend for Samba functions well. 
+	High availability operation may be obtained through directory replication/synchronization and 
+	master/slave server configurations. OpenLDAP is a mature platform to host the organizational 
+	directory infrastructure that can include all UNIX accounts, directories for electronic mail, and much more. 
+	The price paid through learning how to design an LDAP directory schema in implementation and configuration 
+	of management tools is well rewarded by performance and flexibility and the freedom to manage directory
+	contents with greater ability to back up, restore, and modify the directory than is generally possible
+	with Microsoft Active Directory.
+	</para>
+
+	<para>
+	<indexterm><primary>comparison</primary><secondary>Active Directory &amp; OpenLDAP</secondary></indexterm>
+	<indexterm><primary>ADAM</primary></indexterm>
+	<indexterm><primary>Active Directory</primary></indexterm>
+	<indexterm><primary>OpenLDAP</primary></indexterm>
+	A comparison of OpenLDAP with Microsoft Active Directory does not do justice to either. OpenLDAP is an LDAP directory
+	tool-set. Microsoft Active Directory Server is an implementation of an LDAP server that is largely preconfigured
+	for a specific task orientation. It comes with a set of administrative tools that is entirely customized
+	for the purpose of running MS Windows applications that include file and print services, Microsoft Exchange
+	server, Microsoft SQL server, and more. The complexity of OpenLDAP is highly valued by the UNIX administrator
+	who wants to build a custom directory solution. Microsoft provides an application called 
+	<ulink url="http://www.microsoft.com/windowsserver2003/adam/default.mspx">
+	MS ADAM</ulink> that provides more generic LDAP services, yet it does not have the vanilla-like services
+	of OpenLDAP.
+	</para>
+
+	<para>
+	<indexterm><primary>directory</primary><secondary>schema</secondary></indexterm>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	You may wish to consider outsourcing the development of your OpenLDAP directory to an expert, particularly
+	if you find the challenge of learning about LDAP directories, schemas, configuration, and management
+	tools and the creation of shell and Perl scripts a bit
+	challenging. OpenLDAP can be easily customized, though it includes
+	many ready-to-use schemas. Samba-3 provides an OpenLDAP schema file
+	that is required for use as a passdb backend.
+	</para>
+
+	<para>
+	<indexterm><primary>interoperability</primary></indexterm>
+	For those who are willing to brave the process of installing and configuring LDAP and Samba-3 interoperability,
+	there are a few nice Web-based tools that may help you to manage your users and groups more effectively.
+	The Web-based tools you might like to consider include the
+	<ulink url="http://lam.sourceforge.net/">LDAP Account Manager</ulink> (LAM) and the Webmin-based
+	<ulink url="http://www.webmin.com">Webmin</ulink> Idealx
+	<ulink url="http://webmin.idealx.org/index.en.html">CGI tools</ulink>.
+	</para>
+
+	<para>
+	Some additional LDAP tools should be mentioned. Every so often a Samba user reports using one of 
+	these, so it may be useful to them: 
+	<ulink url="http://biot.com/gq">GQ</ulink>, a GTK-based LDAP browser; 
+	LDAP <ulink url="http://www.iit.edu/~gawojar/ldap/">Browser/Editor</ulink> 
+	<ulink url="http://www.jxplorer.org/">; JXplorer</ulink> (by Computer Associates);
+	and <ulink url="http://phpldapadmin.sourceforge.net/">phpLDAPadmin</ulink>.
+	</para>
+
+	<note><para>
+	The following prescriptive guidance is not an LDAP tutorial. The LDAP implementation expressly uses minimal
+	security controls. No form of secure LDAP communications is attempted. The LDAP configuration information provided
+	is considered to consist of the barest essentials only. You are strongly encouraged to learn more about
+	LDAP before attempting to deploy it in a business-critical environment.
+	</para></note>
+
+	<para>
+	Information to help you get started with OpenLDAP is available from the
+	<ulink url="http://www.openldap.org/pub/">OpenLDAP web site</ulink>. Many people have found the book
+	<ulink url="http://www.oreilly.com/catalog/ldapsa/index.html"><emphasis>LDAP System Administration</emphasis>,</ulink>
+	by Jerry Carter quite useful.
+	</para>
+
+	<para>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>network</primary><secondary>segment</secondary></indexterm>
+	<indexterm><primary>performance</primary></indexterm>
+	<indexterm><primary>network</primary><secondary>wide-area</secondary></indexterm>
+	Mary's problems are due to two factors. First, the absence of a domain controller on the local network is the
+	main cause of the errors that result in blue screen crashes. Second, Mary has a large profile that must
+	be loaded over the WAN connection. The addition of BDCs on each network segment significantly
+	improves overall network performance for most users, but it is not enough. You must gain control over
+	user desktops, and this must be done in a way that wins their support and does not cause further loss of
+	staff morale. The following procedures solve this problem.
+	</para>
+
+	<para>
+	<indexterm><primary>smart printing</primary></indexterm>
+	There is also an opportunity to implement smart printing features. You add this to the Samba configuration
+	so that future printer changes can be managed without need to change desktop configurations.
+	</para>
+
+	<para>
+	You add the ability to automatically download new printer drivers, even if they are not installed 
+	in the default desktop profile. Only one example of printing configuration is given. It is assumed that
+	you can extrapolate the principles and use them to install all printers that may be needed.
+	</para>
+
+	<sect2>
+	<title>Technical Issues</title>
+
+	<para>
+	<indexterm><primary>identity</primary><secondary>management</secondary></indexterm>
+	<indexterm><primary>directory</primary><secondary>server</secondary></indexterm>
+	<indexterm><primary>Posix</primary></indexterm>
+	The solution provided is a minimal approach to getting OpenLDAP running as an identity management directory
+	server for UNIX system accounts as well as for Samba. From the OpenLDAP perspective, UNIX system
+	accounts are stored POSIX schema extensions. Samba provides its own schema to permit storage of account 
+	attributes Samba needs. Samba-3 can use the LDAP backend to store:
+	</para>
+	
+	<itemizedlist>
+		<listitem><para>Windows Networking User Accounts</para></listitem>
+		<listitem><para>Windows NT Group Accounts</para></listitem>
+		<listitem><para>Mapping Information between UNIX Groups and Windows NT Groups</para></listitem>
+		<listitem><para>ID Mappings for SIDs to UIDs (also for foreign Domain SIDs)</para></listitem>
+	</itemizedlist>
+
+	<para>
+	<indexterm><primary>UNIX accounts</primary></indexterm>
+	<indexterm><primary>Windows accounts</primary></indexterm>
+	<indexterm><primary>PADL LDAP tools</primary></indexterm>
+	<indexterm><primary>/etc/group</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>name service switch</primary><see>NSS</see></indexterm>
+	<indexterm><primary>NSS</primary></indexterm>
+	<indexterm><primary>UID</primary></indexterm>
+	<indexterm><primary>nss_ldap</primary></indexterm>
+	The use of LDAP with Samba-3 makes it necessary to store UNIX accounts as well as Windows Networking
+	accounts in the LDAP backend. This implies the need to use the 
+	<ulink url="http://www.padl.com/Contents/OpenSourceSoftware.html">PADL LDAP tools</ulink>. The resolution 
+	of the UNIX group name to its GID must be enabled from either the <filename>/etc/group</filename> 
+	or from the LDAP backend. This requires the use of the PADL <filename>nss_ldap</filename> tool-set
+	that integrates with the NSS. The same requirements exist for resolution
+	of the UNIX username to the UID. The relationships are demonstrated in <link linkend="sbehap-LDAPdiag"/>.
+	</para>
+
+	<figure id="sbehap-LDAPdiag">
+		<title>The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts</title>
+		<imagefile scale="50">UNIX-Samba-and-LDAP</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>security</primary></indexterm>
+	<indexterm><primary>LDAP</primary><secondary>secure</secondary></indexterm>
+	You configure OpenLDAP so that it is operational. Before deploying the OpenLDAP, you really
+	ought to learn how to configure secure communications over LDAP so that site security is not
+	at risk. This is not covered in the following guidance.
+	</para>
+
+	<para>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>LDAP Interchange Format</primary><see>LDIF</see></indexterm>
+	<indexterm><primary>LDIF</primary></indexterm>
+	<indexterm><primary>secrets.tdb</primary></indexterm>
+	When OpenLDAP has been made operative, you configure the PDC called <constant>MASSIVE</constant>.
+	You initialize the Samba <filename>secrets.tdb<subscript></subscript></filename> file. Then you
+	create the LDAP Interchange Format (LDIF) file from which the LDAP database can be initialized.
+	You need to decide how best to create user and group accounts. A few hints are, of course, provided.
+	You can also find on the enclosed CD-ROM, in the <filename>Chap06</filename> directory, a few tools
+	that help to manage user and group configuration.
+	</para>
+
+	<para>
+	<indexterm><primary>folder redirection</primary></indexterm>
+	<indexterm><primary>default profile</primary></indexterm>
+	<indexterm><primary>roaming profile</primary></indexterm>
+	In order to effect folder redirection and to add robustness to the implementation,
+	create a network default profile. All network users workstations are configured to use
+	the new profile. Roaming profiles will automatically be deleted from the workstation
+	when the user logs off.
+	</para>
+
+	<para>
+	<indexterm><primary>mandatory profile</primary></indexterm>
+	The profile is configured so that users cannot change the appearance
+	of their desktop. This is known as a mandatory profile. You make certain that users
+	are able to use their computers efficiently.
+	</para>
+
+	<para>
+	<indexterm><primary>logon script</primary></indexterm>
+	A network logon script is used to deliver flexible but consistent network drive
+	connections.
+	</para>
+
+		<sect3 id="sbehap-ppc">
+		<title>Addition of Machines to the Domain</title>
+
+		<para>
+		<indexterm><primary></primary></indexterm>
+		<indexterm><primary></primary></indexterm>
+		<indexterm><primary></primary></indexterm>
+		<indexterm><primary></primary></indexterm>
+		Samba versions prior to 3.0.11 necessitated the use of a domain administrator account
+		that maps to the UNIX UID=0. The UNIX operating system permits only the <constant>root</constant>
+		user to add user and group accounts. Samba 3.0.11 introduced a new facility known as
+		<constant>Privileges</constant>, which provides five new privileges that
+		can be assigned to users and/or groups; see Table 5.1.
+		</para>
+
+
+		<table id="sbehap-privs">
+			<title>Current Privilege Capabilities</title>
+			<tgroup cols="2">
+				<colspec align="left"/>
+				<colspec align="left"/>
+				<thead>
+					<row>
+						<entry align="left">Privilege</entry>
+						<entry align="left">Description</entry>
+					</row>
+				</thead>
+				<tbody>
+					<row>
+						<entry><para>SeMachineAccountPrivilege</para></entry>
+						<entry><para>Add machines to domain</para></entry>
+					</row>
+					<row>
+						<entry><para>SePrintOperatorPrivilege</para></entry>
+						<entry><para>Manage printers</para></entry>
+					</row>
+					<row>
+						<entry><para>SeAddUsersPrivilege</para></entry>
+						<entry><para>Add users and groups to the domain</para></entry>
+					</row>
+					<row>
+						<entry><para>SeRemoteShutdownPrivilege</para></entry>
+						<entry><para>Force shutdown from a remote system</para></entry>
+					</row>
+					<row>
+						<entry><para>SeDiskOperatorPrivilege</para></entry>
+						<entry><para>Manage disk share</para></entry>
+					</row>
+				</tbody>
+			</tgroup>
+		</table>
+
+		<para>
+		In this network example use is made of one of the supported privileges purely to demonstrate
+		how any user can now be given the ability to add machines to the domain using a normal user account
+		that has been given the appropriate privileges.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Roaming Profile Background</title>
+
+		<para>
+		As XP roaming profiles grow, so does the amount of time it takes to log in and out.
+		</para>
+
+		<para>
+		<indexterm><primary>roaming profile</primary></indexterm>
+		<indexterm><primary>HKEY_CURRENT_USER</primary></indexterm>
+		<indexterm><primary>NTUSER.DAT</primary></indexterm>
+		<indexterm><primary>%USERNAME%</primary></indexterm>
+		An XP roaming profile consists of the <constant>HKEY_CURRENT_USER</constant> hive file
+		<filename>NTUSER.DAT</filename> and a number of folders (My Documents, Application Data,
+		Desktop, Start Menu, Templates, NetHood, Favorites, and so on).  When a user logs onto the 
+		network with the default configuration of MS Windows NT/200x/XPP, all this data is 
+		copied to the local machine under the <filename>C:\Documents and Settings\%USERNAME%</filename>
+		directory. While the user is logged in, any changes made to any of these folders or to the
+		<constant>HKEY_CURRENT_USER</constant> branch of the registry are made to the local copy
+		of the profile.  At logout the profile data is copied back to the server. This behavior
+		can be changed through appropriate registry changes and/or through changes to the default
+		user profile. In the latter case, it updates the registry with the values that are set in the
+		profile <filename>NTUSER.DAT</filename>
+		file.
+		</para>
+
+		<para>
+		The first challenge is to reduce the amount of data that must be transferred to and 
+		from the profile server as roaming profiles are processed.  This includes removing 
+		all the shortcuts in the Recent directory, making sure the cache used by the Web browser 
+		is not being dumped into the <filename>Application Data</filename> folder, removing the 
+		Java plug-ins cache (the .jpi_cache directory in the profile), as well as training the 
+		user to not place large files on the desktop and to use his or her mapped home directory
+		instead of the <filename>My Documents</filename> folder for saving documents.
+		</para>
+
+		<para>
+		<indexterm><primary>My Documents</primary></indexterm>
+		Using a folder other than <filename>My Documents</filename> is a nuisance for 
+		some users, since many applications use it by default.
+		</para>
+
+		<para>
+		<indexterm><primary>roaming profiles</primary></indexterm>
+		<indexterm><primary>Local Group Policy</primary></indexterm>
+		<indexterm><primary>NTUSER.DAT</primary></indexterm>
+		The secret to rapid loading of roaming profiles is to prevent unnecessary data from 
+		being copied back and forth, without losing any functionality. This is not difficult; 
+		it can be done by making changes to the Local Group Policy on each client as well 
+		as changing some paths in each user's <filename>NTUSER.DAT</filename> hive.
+		</para>
+
+		<para>
+		<indexterm><primary>Network Default Profile</primary></indexterm>
+		<indexterm><primary>redirected folders</primary></indexterm>
+		Every user profile has its own <filename>NTUSER.DAT</filename> file. This means
+		you need to edit every user's profile, unless a better method can be
+		followed. Fortunately, with the right preparations, this is not difficult.
+		It is possible to remove the <filename>NTUSER.DAT</filename> file from each
+		user's profile. Then just create a Network Default Profile. Of course, it is
+		necessary to copy all files from redirected folders to the network share to which
+		they are redirected.
+		</para>
+
+		</sect3>
+
+		<sect3 id="sbehap-locgrppol">
+		<title>The Local Group Policy</title>
+
+		<para>
+		<indexterm><primary>Group Policy Objects</primary></indexterm>
+		<indexterm><primary>Active Directory</primary></indexterm>
+		<indexterm><primary>PDC</primary></indexterm>
+		<indexterm><primary>Group Policy editor</primary></indexterm>
+		Without an Active Directory PDC, you cannot take full advantage of Group Policy 
+		Objects. However, you can still make changes to the Local Group Policy by using 
+		the Group Policy editor (<command>gpedit.msc</command>).
+		</para>
+
+		<para>
+		The <emphasis>Exclude directories in roaming profile</emphasis> settings can 
+		be found under 
+		<menuchoice>
+			<guimenu>User Configuration</guimenu>
+			<guimenuitem>Administrative Templates</guimenuitem>
+			<guimenuitem>System</guimenuitem>
+			<guimenuitem>User Profiles</guimenuitem>
+		</menuchoice>. 
+		By default this setting contains
+		<quote>Local Settings; Temporary Internet Files; History; Temp</quote>.
+		</para>
+
+		<para>
+		Simply add the folders you do not wish to be copied back and forth to this 
+		semicolon-separated list. Note that this change must be made on all clients 
+		that are using roaming profiles.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Profile Changes</title>
+
+		<para>
+		<indexterm><primary>NTUSER.DAT</primary></indexterm>
+		<indexterm><primary>%USERNAME%</primary></indexterm>
+		There are two changes that should be done to each user's profile. Move each of 
+		the directories that you have excluded from being copied back and forth out of 
+		the usual profile path. Modify each user's <filename>NTUSER.DAT</filename> file 
+		to point to the new paths that are shared over the network instead of to the default
+		path (<filename>C:\Documents and Settings\%USERNAME%</filename>).
+		</para>
+
+		<para>
+		<indexterm><primary>Default User</primary></indexterm>
+		<indexterm><primary>regedt32</primary></indexterm>
+		The above modifies existing user profiles. So that newly created profiles have 
+		these settings, you need to modify the <filename>NTUSER.DAT</filename> in 
+		the <filename>C:\Documents and Settings\Default User</filename> folder on each 
+		client machine, changing the same registry keys.  You could do this by copying 
+		<filename>NTUSER.DAT</filename> to a Linux box and using <command>regedt32</command>.
+		The basic method is described under <link linkend="redirfold"/>.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Using a Network Default User Profile</title>
+
+		<para>
+		<indexterm><primary>NETLOGON</primary></indexterm>
+		<indexterm><primary>NTUSER.DAT</primary></indexterm>
+		If you are using Samba as your PDC, you should create a file share called 
+		<constant>NETLOGON</constant> and within that create a directory called 
+		<filename>Default User</filename>, which is a copy of the desired default user 
+		configuration (including a copy of <filename>NTUSER.DAT</filename>).
+		If this share exists and the <filename>Default User</filename> folder exists, 
+		the first login from a new account pulls its configuration from it.
+		See also <ulink url="http://isg.ee.ethz.ch/tools/realmen/det/skel.en.html">
+		the Real Men Don't Click</ulink> Web site.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Installation of Printer Driver Auto-Download</title>
+
+		<para>
+		<indexterm><primary>printing</primary><secondary>dumb</secondary></indexterm>
+		<indexterm><primary>dumb printing</primary></indexterm>
+		<indexterm><primary>Raw Print Through</primary></indexterm>
+		The subject of printing is quite topical. Printing problems run second place to name
+		resolution issues today. So far in this book, you have experienced only what is generally
+		known as <quote>dumb</quote> printing. Dumb printing is the arrangement by which all drivers
+		are manually installed on each client and the printing subsystems perform no filtering
+		or intelligent processing. Dumb printing is easily understood. It usually works without
+		many problems, but it has its limitations also. Dumb printing is better known as
+		<command>Raw-Print-Through</command> printing.
+		</para>
+
+		<para>
+		<indexterm><primary>printing</primary><secondary>drag-and-drop</secondary></indexterm>
+		<indexterm><primary>printing</primary><secondary>point-n-click</secondary></indexterm>
+		Samba permits the configuration of <command>smart</command> printing using the Microsoft
+		Windows point-and-click (also called drag-and-drop) printing. What this provides is
+		essentially the ability to print to any printer. If the local client does not yet have a
+		driver installed, the driver is automatically downloaded from the Samba server and
+		installed on the client. Drag-and-drop printing is neat; it means the user never needs
+		to fuss with driver installation, and that is a <trademark>Good Thing,</trademark>
+		isn't it?
+		</para>
+
+		<para>
+		There is a further layer of print job processing that is known as <command>intelligent</command>
+		printing that automatically senses the file format of data submitted for printing and
+		then invokes a suitable print filter to convert the incoming data stream into a format
+		suited to the printer to which the job is dispatched.
+		</para>
+
+		<para>
+		<indexterm><primary>CUPS</primary></indexterm>
+		<indexterm><primary>Easy Software Products</primary></indexterm>
+		<indexterm><primary>Postscript</primary></indexterm>
+		The CUPS printing subsystem is capable of intelligent printing. It has the capacity to
+		detect the data format and apply a print filter. This means that it is feasible to install
+		on all Windows clients a single printer driver for use with all printers that are routed
+		through CUPS. The most sensible driver to use is one for a PostScript printer. Fortunately,
+		<ulink url="http://www.easysw.com">Easy Software Products</ulink>, the authors of CUPS, have
+		released a PostScript printing driver for Windows. It can be installed into the Samba
+		printing backend so that it automatically downloads to the client when needed. 
+		</para>
+
+		<para>
+		This means that so long as there is a CUPS driver for the printer, all printing from Windows 
+		software can use PostScript, no matter what the actual printer language for the physical 
+		device is. It also means that the administrator can swap out a printer with a totally 
+		different type of device without ever needing to change a client workstation driver.
+		</para>
+
+		<para>
+		This book is about Samba-3, so you can confine the printing style to just the smart
+		style of installation. Those interested in further information regarding intelligent
+		printing should review documentation on the Easy Software Products Web site.
+		</para>
+
+		</sect3>
+
+		<sect3 id="sbeavoid">
+		<title>Avoiding Failures: Solving Problems Before They Happen</title>
+
+		<para>
+		It has often been said that there are three types of people in the world: those who
+		have sharp minds and those who forget things. Please do not ask what the third group
+		is like! Well, it seems that many of us have company in the second group. There must
+		be a good explanation why so many network administrators fail to solve apparently
+		simple problems efficiently and effectively.
+		</para>
+
+		<para>
+		Here are some diagnostic guidelines that can be referred to when things go wrong:
+		</para>
+
+		<sect4>
+		<title>Preliminary Advice: Dangers Can Be Avoided</title>
+
+		<para>
+		The best advice regarding how to mend a broken leg is <quote>Never break a leg!</quote>
+		</para>
+
+		<para>
+		<indexterm><primary>LDAP</primary></indexterm>
+		Newcomers to Samba and LDAP seem to struggle a great deal at first.  If you want advice
+		regarding the best way to remedy LDAP and Samba problems: <quote>Avoid them like the plague!</quote>
+		</para>
+
+		<para>
+		If you are now asking yourself how problems can be avoided, the best advice is to start
+		out your learning experience with a <emphasis>known-good configuration.</emphasis> After
+		you have seen a fully working solution, a good way to learn is to make slow and progressive
+		changes that cause things to break, then observe carefully how and why things ceased to work.
+		</para>
+
+		<para>
+		The examples in this chapter (also in the book as a whole) are known to work. That means
+		that they could serve as the kick-off point for your journey through fields of knowledge.
+		Use this resource carefully; we hope it serves you well.
+		</para>
+
+		<warning><para>
+		Do not be lulled into thinking that you can easily adopt the examples in this
+		book and adapt them without first working through the examples provided. A little
+		thing overlooked can cause untold pain and may permanently tarnish your experience.
+		</para></warning>
+
+		</sect4>
+
+		<sect4>
+		<title>The Name Service Caching Daemon</title>
+
+		<para>
+		The name service caching daemon (nscd) is a primary cause of difficulties with name
+		resolution, particularly where <command>winbind</command> is used. Winbind does its
+		own caching, thus nscd causes double caching which can lead to peculiar problems during
+		debugging. As a rule, it is a good idea to turn off the name service caching daemon.
+		</para>
+
+		<para>
+		Operation of the name service caching daemon is controlled by the 
+		<filename>/etc/nscd.conf</filename> file. Typical contents of this file are as follows:
+<screen>
+# /etc/nscd.conf
+# An example Name Service Cache config file.  This file is needed by nscd.
+# Legal entries are:
+#       logfile                 &lt;file&gt;
+#       debug-level             &lt;level&gt;
+#       threads                 &lt;threads to use&gt;
+#       server-user             &lt;user to run server as instead of root&gt;
+#               server-user is ignored if nscd is started with -S parameters
+#       stat-user               &lt;user who is allowed to request statistics&gt;
+#       reload-count            unlimited|&lt;number&gt;
+#
+#       enable-cache            &lt;service&gt; &lt;yes|no&gt;
+#       positive-time-to-live   &lt;service&gt; &lt;time in seconds&gt;
+#       negative-time-to-live   &lt;service&gt; &lt;time in seconds&gt;
+#       suggested-size          &lt;service&gt; &lt;prime number&gt;
+#       check-files             &lt;service&gt; &lt;yes|no&gt;
+#       persistent              &lt;service&gt; &lt;yes|no&gt;
+#       shared                  &lt;service&gt; &lt;yes|no&gt;
+# Currently supported cache names (services): passwd, group, hosts
+#       logfile                 /var/log/nscd.log
+#       threads                 6
+#       server-user             nobody
+#       stat-user               somebody
+        debug-level             0
+#       reload-count            5
+        enable-cache            passwd          yes
+        positive-time-to-live   passwd          600
+        negative-time-to-live   passwd          20
+        suggested-size          passwd          211
+        check-files             passwd          yes
+        persistent              passwd          yes
+        shared                  passwd          yes
+        enable-cache            group           yes
+        positive-time-to-live   group           3600
+        negative-time-to-live   group           60
+        suggested-size          group           211
+        check-files             group           yes
+        persistent              group           yes
+        shared                  group           yes
+# !!!!!WARNING!!!!! Host cache is insecure!!! The mechanism in nscd to
+# cache hosts will cause your local system to not be able to trust
+# forward/reverse lookup checks. DO NOT USE THIS if your system relies on
+# this sort of security mechanism. Use a caching DNS server instead.
+        enable-cache            hosts           no
+        positive-time-to-live   hosts           3600
+        negative-time-to-live   hosts           20
+        suggested-size          hosts           211
+        check-files             hosts           yes
+        persistent              hosts           yes
+        shared                  hosts           yes
+</screen>
+	It is feasible to comment out the <constant>passwd</constant> and <constant>group</constant>
+	entries so they will not be cached. Alternatively, it is often simpler to just disable the
+	<command>nscd</command> service by executing (on Novell SUSE Linux):
+<screen>
+&rootprompt; chkconfig nscd off
+&rootprompt; rcnscd off
+</screen>
+		</para>
+
+		</sect4>
+
+		<sect4>
+		<title>Debugging LDAP</title>
+
+		<para>
+		<indexterm><primary>/etc/openldap/slapd.conf</primary></indexterm>
+		<indexterm><primary>loglevel</primary></indexterm>
+		<indexterm><primary>slapd</primary></indexterm>
+		In the example <filename>/etc/openldap/slapd.conf</filename> control file
+		(see <link linkend="sbehap-dbconf"/>) there is an entry for <constant>loglevel	256</constant>.
+		To enable logging via the syslog infrastructure, it is necessary to uncomment this parameter
+		and restart <command>slapd</command>.
+		</para>
+
+		<para>
+		<indexterm><primary>/etc/syslog.conf</primary></indexterm>
+		<indexterm><primary>/var/log/ldaplogs</primary></indexterm>
+		LDAP log information can be directed into a file that is separate from the normal system
+		log files by changing the <filename>/etc/syslog.conf</filename> file so it has the following
+		contents:
+<screen>
+# Some foreign boot scripts require local7
+#
+local0,local1.*                 -/var/log/localmessages
+local2,local3.*                 -/var/log/localmessages
+local5.*                        -/var/log/localmessages
+local6,local7.*                 -/var/log/localmessages
+local4.*                        -/var/log/ldaplogs
+</screen>
+		In this case, all LDAP-related logs will be directed to the file
+		<filename>/var/log/ldaplogs</filename>. This makes it easy to track LDAP errors.
+		The snippet provides a simple example of usage that can be modified to suit
+		local site needs. The configuration used later in this chapter reflects such
+		customization with the intent that LDAP log files will be stored at a location
+		that meets local site needs and wishes more fully.
+		</para>
+
+		</sect4>
+
+		<sect4>
+		<title>Debugging NSS_LDAP</title>
+
+		<para>
+		The basic mechanism for diagnosing problems with the nss_ldap utility involves adding to the
+		<filename>/etc/ldap.conf</filename> file the following parameters:
+<screen>
+debug 256
+logdir /data/logs
+</screen>
+		Create the log directory as follows:
+<screen>
+&rootprompt; mkdir /data/logs
+</screen>
+		</para>
+
+<?latex \newpage ?>
+
+		<para>
+		The diagnostic process should follow these steps:
+		</para>
+
+		<procedure>
+		<title>NSS_LDAP Diagnostic Steps</title>
+
+			<step><para>
+			Verify the <constant>nss_base_passwd, nss_base_shadow, nss_base_group</constant> entries
+			in the <filename>/etc/ldap.conf</filename> file and compare them closely with the directory
+			tree location that was chosen when the directory was first created.
+			</para>
+
+			<para>
+			One way this can be done is by executing:
+<screen>
+&rootprompt; slapcat | grep Group | grep dn
+dn: ou=Groups,dc=abmas,dc=biz
+dn: cn=Domain Admins,ou=Groups,dc=abmas,dc=biz
+dn: cn=Domain Users,ou=Groups,dc=abmas,dc=biz
+dn: cn=Domain Guests,ou=Groups,dc=abmas,dc=biz
+dn: cn=Domain Computers,ou=Groups,dc=abmas,dc=biz
+dn: cn=Administrators,ou=Groups,dc=abmas,dc=biz
+dn: cn=Print Operators,ou=Groups,dc=abmas,dc=biz
+dn: cn=Backup Operators,ou=Groups,dc=abmas,dc=biz
+dn: cn=Replicators,ou=Groups,dc=abmas,dc=biz
+</screen>
+			The first line is the DIT entry point for the container for POSIX groups. The correct entry
+			for the <filename>/etc/ldap.conf</filename> for the <constant>nss_base_group</constant>
+			parameter therefore is the distinguished name (dn) as applied here:
+<screen>
+nss_base_group ou=Groups,dc=abmas,dc=biz?one
+</screen>
+			The same process may be followed to determine the appropriate dn for user accounts.
+			If the container for computer accounts is not the same as that for users (see the &smb.conf;
+			file entry for <constant>ldap machine suffix</constant>), it may be necessary to set the 
+			following DIT dn in the <filename>/etc/ldap.conf</filename> file:
+<screen>
+nss_base_passwd dc=abmas,dc=biz?sub
+</screen>
+			This instructs LDAP to search for machine as well as user entries from the top of the DIT
+			down. This is inefficient, but at least should work. Note: It is possible to specify multiple
+			<constant>nss_base_passwd</constant> entries in the <filename>/etc/ldap.conf</filename> file; they
+			will be evaluated sequentially. Let us consider an example of use where the following DIT
+			has been implemented:
+			</para>
+
+			<para>
+			<itemizedlist>
+			<listitem><para>User accounts are stored under the DIT: ou=Users, dc=abmas, dc=biz</para></listitem>
+			<listitem><para>User login accounts are under the DIT: ou=People, ou-Users, dc=abmas, dc=biz</para></listitem>
+			<listitem><para>Computer accounts are under the DIT: ou=Computers, ou=Users, dc=abmas, dc=biz</para></listitem>
+			</itemizedlist>
+			</para>
+
+			<para>
+			The appropriate multiple entry for the <constant>nss_base_passwd</constant> directive
+			in the <filename>/etc/ldap.conf</filename> file may be:
+<screen>
+nss_base_passwd ou=People,ou=Users,dc=abmas,dc=org?one
+nss_base_passwd ou=Computers,ou=Users,dc=abmas,dc=org?one
+</screen>
+			</para></step>
+
+			<step><para>
+			Perform lookups such as:
+<screen>
+&rootprompt; getent passwd
+</screen>
+			Each such lookup will create an entry in the <filename>/data/log</filename> directory
+			for each such process executed. The contents of each file created in this directory
+			may provide a hint as to the cause of the a problem that is under investigation. 
+			</para></step>
+
+			<step><para>
+			For additional diagnostic information, check the contents of the <filename>/var/log/messages</filename>
+			to see what error messages are being generated as a result of the LDAP lookups. Here is an example of
+			a successful lookup:
+<screen>
+slapd[12164]: conn=0 fd=10 ACCEPT from IP=127.0.0.1:33539
+(IP=0.0.0.0:389)
+slapd[12164]: conn=0 op=0 BIND dn="" method=128
+slapd[12164]: conn=0 op=0 RESULT tag=97 err=0 text=
+slapd[12164]: conn=0 op=1 SRCH base="" scope=0 deref=0
+filter="(objectClass=*)"
+slapd[12164]: conn=0 op=1 SEARCH RESULT tag=101 err=0
+nentries=1 text=
+slapd[12164]: conn=0 op=2 UNBIND
+slapd[12164]: conn=0 fd=10 closed
+slapd[12164]: conn=1 fd=10 ACCEPT from
+IP=127.0.0.1:33540 (IP=0.0.0.0:389)
+slapd[12164]: conn=1 op=0 BIND
+dn="cn=Manager,dc=abmas,dc=biz" method=128
+slapd[12164]: conn=1 op=0 BIND
+dn="cn=Manager,dc=abmas,dc=biz" mech=SIMPLE ssf=0
+slapd[12164]: conn=1 op=0 RESULT tag=97 err=0 text=
+slapd[12164]: conn=1 op=1 SRCH
+base="ou=People,dc=abmas,dc=biz" scope=1 deref=0
+filter="(objectClass=posixAccount)"
+slapd[12164]: conn=1 op=1 SRCH attr=uid userPassword
+uidNumber gidNumber cn
+homeDirectory loginShell gecos description objectClass
+slapd[12164]: conn=1 op=1 SEARCH RESULT tag=101 err=0
+nentries=2 text=
+slapd[12164]: conn=1 fd=10 closed
+
+</screen>
+			</para></step>
+
+			<step><para>
+			Check that the bindpw entry in the <filename>/etc/ldap.conf</filename> or in the
+			<filename>/etc/ldap.secrets</filename> file is correct, as specified in the
+			<filename>/etc/openldap/slapd.conf</filename> file.
+			</para></step>
+
+		</procedure>
+
+		</sect4>
+
+		<sect4>
+		<title>Debugging Samba</title>
+
+		<para>
+		The following parameters in the &smb.conf; file can be useful in tracking down Samba-related problems:
+<screen>
+[global]
+	...
+	log level = 5
+	log file = /var/log/samba/%m.log
+	max log size = 0
+	...
+</screen>
+		This will result in the creation of a separate log file for every client from which connections
+		are made. The log file will be quite verbose and will grow continually. Do not forget to
+		change these lines to the following when debugging has been completed:
+<screen>
+[global]
+	...
+	log level = 1
+	log file = /var/log/samba/%m.log
+	max log size = 50
+	...
+</screen>
+		</para>
+
+		<para>
+		The log file can be analyzed by executing:
+<screen>
+&rootprompt; cd /var/log/samba
+&rootprompt; grep -v "^\[200" machine_name.log
+</screen>
+		</para>
+
+		<para>
+		Search for hints of what may have failed by looking for the words <emphasis>fail</emphasis>
+		and <emphasis>error</emphasis>.
+		</para>
+
+		</sect4>
+
+		<sect4>
+		<title>Debugging on the Windows Client</title>
+
+		<para>
+		MS Windows 2000 Professional and Windows  XP Professional clients can be configured
+		to create a netlogon.log file that can be very helpful in diagnosing network logon problems. Search
+		the Microsoft knowledge base for detailed instructions. The techniques vary a little with each
+		version of MS Windows.
+		</para>
+
+		</sect4>
+
+		</sect3>
+
+	</sect2>
+
+
+	<sect2>
+		<title>Political Issues</title>
+
+		<para>
+		MS Windows network users are generally very sensitive to limits that may be imposed when 
+		confronted with locked-down workstation configurations. The challenge you face must 
+		be promoted as a choice between reliable, fast network operation and a constant flux 	
+		of problems that result in user irritation.
+		</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Installation Checklist</title>
+
+	<para>
+	You are starting a complex project. Even though you went through the installation of a complex
+	network in <link linkend="Big500users"/>, this network is a bigger challenge because of the
+	large number of complex applications that must be configured before the first few steps
+	can be validated. Take stock of what you are about to undertake, prepare yourself, and
+	frequently review the steps ahead while making at least a mental note of what has already
+	been completed. The following task list may help you to keep track of the task items
+	that are covered:
+	</para>
+
+
+	<itemizedlist>
+		<listitem><para>Samba-3 PDC Server Configuration</para>
+			<orderedlist>
+				<listitem><para>DHCP and DNS servers</para></listitem>
+				<listitem><para>OpenLDAP server</para></listitem>
+				<listitem><para>PAM and NSS client tools</para></listitem>
+				<listitem><para>Samba-3 PDC</para></listitem>
+				<listitem><para>Idealx smbldap scripts</para></listitem>
+				<listitem><para>LDAP initialization</para></listitem>
+				<listitem><para>Create user and group accounts</para></listitem>
+				<listitem><para>Printers</para></listitem>
+				<listitem><para>Share point directory roots</para></listitem>
+				<listitem><para>Profile directories</para></listitem>
+				<listitem><para>Logon scripts</para></listitem>
+				<listitem><para>Configuration of user rights and privileges</para></listitem>
+			</orderedlist>
+		</listitem>
+		<listitem><para>Samba-3 BDC Server Configuration</para>
+			<orderedlist>
+				<listitem><para>DHCP and DNS servers</para></listitem>
+				<listitem><para>PAM and NSS client tools</para></listitem>
+				<listitem><para>Printers</para></listitem>
+				<listitem><para>Share point directory roots</para></listitem>
+				<listitem><para>Profiles directories</para></listitem>
+			</orderedlist>
+		</listitem>
+		<listitem><para>Windows XP Client Configuration</para>
+			<orderedlist>
+				<listitem><para>Default profile folder redirection</para></listitem>
+				<listitem><para>MS Outlook PST file relocation</para></listitem>
+				<listitem><para>Delete roaming profile on logout</para></listitem>
+				<listitem><para>Upload printer drivers to Samba servers</para></listitem>
+				<listitem><para>Install software</para></listitem>
+				<listitem><para>Creation of roll-out images</para></listitem>
+			</orderedlist>
+		</listitem>
+	</itemizedlist>
+
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Samba Server Implementation</title>
+
+	<para>
+	<indexterm><primary>file servers</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	The network design shown in <link linkend="chap6net"/> is not comprehensive. It is assumed
+	that you will install additional file servers and possibly additional BDCs.
+	</para>
+
+	<figure id="chap6net">
+		<title>Network Topology &smbmdash; 500 User Network Using ldapsam passdb backend</title>
+		<imagefile scale="50">chap6-net</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>SUSE Linux</primary></indexterm>
+	<indexterm><primary>Red Hat Linux</primary></indexterm>
+	All configuration files and locations are shown for SUSE Linux 9.2 and are equally valid for SUSE
+	Linux Enterprise Server 9. The file locations for Red Hat Linux are similar. You may need to
+	adjust the locations for your particular Linux system distribution/implementation.
+	</para>
+
+<note><para>
+The following information applies to Samba-3.0.20 when used with the Idealx smbldap-tools
+scripts version 0.9.1. If using a different version of Samba or of the smbldap-tools tarball,
+please verify that the versions you are about to use are matching. The smbldap-tools package
+uses counter-entries in the LDAP directory to avoid duplication of the UIDs and GIDs that are
+issued for POSIX accounts. The LDAP rdn under which this information is stored are called
+<constant>uidNumber</constant> and <constant>gidNumber</constant> respectively. These may be
+located in any convenient part of the directory information tree (DIT). In the examples that
+follow they have been located under <constant>dn=sambaDomainName=MEGANET2,dc=abmas,dc=org</constant>.
+They could just as well be located under the rdn <constant>cn=NextFreeUnixId</constant>.
+</para></note>
+
+	<para>
+	The steps in the process involve changes from the network configuration shown in
+	<link linkend="Big500users"/>.  Before implementing the following steps, you must
+	have completed the network implementation shown in that chapter. If you are starting
+	with newly installed Linux servers, you must complete the steps shown in
+	<link linkend="ch5-dnshcp-setup"/> before commencing at <link linkend="ldapsetup"/>.
+	</para>
+
+	<sect2 id="ldapsetup">
+	<title>OpenLDAP Server Configuration</title>
+
+	<para>
+	<indexterm><primary>nss_ldap</primary></indexterm>
+	<indexterm><primary>pam_ldap</primary></indexterm>
+	<indexterm><primary>openldap</primary></indexterm>
+	Confirm that the packages shown in <link linkend="oldapreq"/> are installed on your system.
+	</para>
+
+	<table id="oldapreq">
+		<title>Required OpenLDAP Linux Packages</title>
+		<tgroup cols="3">
+			<colspec align="left"/>
+			<colspec align="left"/>
+			<colspec align="left"/>
+			<thead>
+				<row>
+					<entry align="center">SUSE Linux 8.x</entry>
+					<entry align="center">SUSE Linux 9.x</entry>
+					<entry align="center">Red Hat Linux</entry>
+				</row>
+			</thead>
+			<tbody>
+				<row>
+					<entry>nss_ldap</entry>
+					<entry>nss_ldap</entry>
+					<entry>nss_ldap</entry>
+				</row>
+				<row>
+					<entry>pam_ldap</entry>
+					<entry>pam_ldap</entry>
+					<entry>pam_ldap</entry>
+				</row>
+				<row>
+					<entry>openldap2</entry>
+					<entry>openldap2</entry>
+					<entry>openldap</entry>
+				</row>
+				<row>
+					<entry>openldap2-client</entry>
+					<entry>openldap2-client</entry>
+					<entry></entry>
+				</row>
+			</tbody>
+		</tgroup>
+	</table>
+
+	<para>
+	Samba-3 and OpenLDAP will have a degree of interdependence that is unavoidable. The method
+	for bootstrapping the LDAP and Samba-3 configuration is relatively straightforward. If you
+	follow these guidelines, the resulting system should work fine.
+	</para>
+
+	<procedure>
+	<title>OpenLDAP Server Configuration Steps</title>
+
+		<step><para>
+		<indexterm><primary>/etc/openldap/slapd.conf</primary></indexterm>
+		Install the file shown in <link linkend="sbehap-slapdconf"/> in the directory
+		<filename>/etc/openldap</filename>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/data/ldap</primary></indexterm>
+		<indexterm><primary>group account</primary></indexterm>
+		<indexterm><primary>user account</primary></indexterm>
+		Remove all files from the directory <filename>/data/ldap</filename>, making certain that
+		the directory exists with permissions:
+<screen>
+&rootprompt; ls -al /data | grep ldap
+drwx------   2 ldap    ldap       48 Dec 15 22:11 ldap
+</screen>
+		This may require you to add a user and a group account for LDAP if they do not exist.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>DB_CONFIG</primary></indexterm>
+		Install the file shown in <link linkend="sbehap-dbconf"/> in the directory
+		<filename>/data/ldap</filename>. In the event that this file is added after <constant>ldap</constant>
+		has been started, it is possible to cause the new settings to take effect by shutting down
+		the <constant>LDAP</constant> server, executing the <command>db_recover</command> command inside the
+		<filename>/data/ldap</filename> directory, and then restarting the <constant>LDAP</constant> server.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>syslog</primary></indexterm>
+		Performance logging can be enabled and should preferably be sent to a file on
+		a file system that is large enough to handle significantly sized logs. To enable
+		the logging at a verbose level to permit detailed analysis, uncomment the entry in
+		the <filename>/etc/openldap/slapd.conf</filename> shown as <quote>loglevel 256</quote>.
+		</para>
+
+		<para>
+		Edit the <filename>/etc/syslog.conf</filename> file to add the following at the end
+		of the file:
+<screen>
+local4.*        -/data/ldap/log/openldap.log
+</screen>
+		Note: The path <filename>/data/ldap/log</filename> should be set at a location
+		that is convenient and that can store a large volume of data.
+		</para></step>
+
+	</procedure>
+
+<example id="sbehap-dbconf">
+<title>LDAP DB_CONFIG File</title>
+<screen>
+set_cachesize           0 150000000 1
+set_lg_regionmax        262144
+set_lg_bsize            2097152
+#set_lg_dir             /var/log/bdb
+set_flags               DB_LOG_AUTOREMOVE
+</screen>
+</example>
+
+<example id="sbehap-slapdconf">
+<title>LDAP Master Configuration File &smbmdash; <filename>/etc/openldap/slapd.conf</filename> Part A</title>
+<screen>
+include		/etc/openldap/schema/core.schema
+include		/etc/openldap/schema/cosine.schema
+include		/etc/openldap/schema/inetorgperson.schema
+include		/etc/openldap/schema/nis.schema
+include		/etc/openldap/schema/samba3.schema
+
+pidfile		/var/run/slapd/slapd.pid
+argsfile	/var/run/slapd/slapd.args
+
+access to dn.base=""
+		by self write
+		by * auth
+
+access to attr=userPassword
+		by self write
+		by * auth
+
+access to attr=shadowLastChange
+		by self write
+		by * read
+
+access to *
+                by * read
+                by anonymous auth
+
+#loglevel	256
+
+schemacheck 	on
+idletimeout	30
+backend		bdb
+database	bdb
+checkpoint      1024 5
+cachesize       10000
+
+suffix		"dc=abmas,dc=biz"
+rootdn		"cn=Manager,dc=abmas,dc=biz"
+
+# rootpw = not24get
+rootpw          {SSHA}86kTavd9Dw3FAz6qzWTrCOKX/c0Qe+UV
+
+directory	/data/ldap
+</screen>
+</example>
+
+<example id="sbehap-slapdconf2">
+<title>LDAP Master Configuration File &smbmdash; <filename>/etc/openldap/slapd.conf</filename> Part B</title>
+<screen>
+# Indices to maintain
+index objectClass           eq
+index cn                    pres,sub,eq
+index sn                    pres,sub,eq
+index uid                   pres,sub,eq
+index displayName           pres,sub,eq
+index uidNumber             eq
+index gidNumber             eq
+index memberUID             eq
+index sambaSID              eq
+index sambaPrimaryGroupSID  eq
+index sambaDomainName       eq
+index default               sub
+</screen>
+</example>
+
+	</sect2>
+
+	<sect2 id="sbehap-PAM-NSS">
+	<title>PAM and NSS Client Configuration</title>
+
+	<para>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>NSS</primary></indexterm>
+	<indexterm><primary>PAM</primary></indexterm>
+	The steps that follow involve configuration of LDAP, NSS LDAP-based resolution of users and
+	groups. Also, so that LDAP-based accounts can log onto the system, the steps ahead configure
+	the Pluggable Authentication Modules (PAM) to permit LDAP-based authentication.
+	</para>
+
+	<para>
+	<indexterm><primary>Pluggable Authentication Modules</primary><see>PAM</see></indexterm>
+	<indexterm><primary>pam_unix2.so</primary></indexterm>
+	Since you have chosen to put UNIX user and group accounts into the LDAP database, it is likely
+	that you may want to use them for UNIX system (Linux) local machine logons. This necessitates
+	correct configuration of PAM. The <command>pam_ldap</command> open source package provides the
+	PAM modules that most people would use. On SUSE Linux systems, the <command>pam_unix2.so</command>
+	module also has the ability to redirect authentication requests through LDAP.
+	</para>
+
+	<para>
+	<indexterm><primary>YaST</primary></indexterm>
+	<indexterm><primary>SUSE Linux</primary></indexterm>
+	<indexterm><primary>Red Hat Linux</primary></indexterm>
+	<indexterm><primary>authconfig</primary></indexterm>
+	You have chosen to configure these services by directly editing the system files, but of course, you
+	know that this configuration can be done using system tools provided by the Linux system vendor.
+	SUSE Linux has a facility in YaST (the system admin tool) through <menuchoice><guimenu>yast</guimenu>
+	<guimenuitem>system</guimenuitem><guimenuitem>ldap-client</guimenuitem></menuchoice> that permits
+	configuration of SUSE Linux as an LDAP client. Red Hat Linux provides the <command>authconfig</command>
+	tool for this.
+	</para>
+
+	<procedure>
+	<title>PAM and NSS Client Configuration Steps</title>
+
+		<step><para>
+		<indexterm><primary>/lib/libnss_ldap.so.2</primary></indexterm>
+		<indexterm><primary>/etc/ldap.conf</primary></indexterm>
+		<indexterm><primary>nss_ldap</primary></indexterm>
+		Execute the following command to find where the <filename>nss_ldap</filename> module
+		expects to find its control file:
+<screen>
+&rootprompt; strings /lib/libnss_ldap.so.2 | grep conf
+</screen>
+		The preferred and usual location is <filename>/etc/ldap.conf</filename>.
+		</para></step>
+
+		<step><para>
+		On the server <constant>MASSIVE</constant>, install the file shown in 
+		<link linkend="sbehap-nss01"/> into the path that was obtained from the step above.
+		On the servers called <constant>BLDG1</constant> and <constant>BLDG2</constant>, install the file shown in
+		<link linkend="sbehap-nss02"/> into the path that was obtained from the step above.
+		</para></step>
+
+<example id="sbehap-nss01">
+<title>Configuration File for NSS LDAP Support &smbmdash; <filename>/etc/ldap.conf</filename></title>
+<screen>
+host 127.0.0.1
+
+base dc=abmas,dc=biz
+
+binddn cn=Manager,dc=abmas,dc=biz
+bindpw not24get
+
+timelimit 50
+bind_timelimit 50
+bind_policy hard
+
+idle_timelimit 3600
+
+pam_password exop
+
+nss_base_passwd ou=People,dc=abmas,dc=biz?one
+nss_base_shadow ou=People,dc=abmas,dc=biz?one
+nss_base_group  ou=Groups,dc=abmas,dc=biz?one
+
+ssl off
+</screen>
+</example>
+
+<example id="sbehap-nss02">
+<title>Configuration File for NSS LDAP Clients Support &smbmdash; <filename>/etc/ldap.conf</filename></title>
+<screen>
+host 172.16.0.1
+
+base dc=abmas,dc=biz
+
+binddn cn=Manager,dc=abmas,dc=biz
+bindpw not24get
+
+timelimit 50
+bind_timelimit 50
+bind_policy hard
+
+idle_timelimit 3600
+
+pam_password exop
+
+nss_base_passwd ou=People,dc=abmas,dc=biz?one
+nss_base_shadow ou=People,dc=abmas,dc=biz?one
+nss_base_group  ou=Groups,dc=abmas,dc=biz?one
+
+ssl off
+</screen>
+</example>
+
+		<step><para>
+		<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+		Edit the NSS control file (<filename>/etc/nsswitch.conf</filename>) so that the lines that
+		control user and group resolution will obtain information from the normal system files as
+		well as from <command>ldap</command>:
+<screen>
+passwd: files ldap
+shadow: files ldap
+group:  files ldap
+hosts:  files dns wins
+</screen>
+		Later, when the LDAP database has been initialized and user and group accounts have been
+		added, you can validate resolution of the LDAP resolver process. The inclusion of 
+		WINS-based hostname resolution is deliberate so that all MS Windows client hostnames can be 
+		resolved to their IP addresses, whether or not they are DHCP clients.
+		</para>
+
+		<note><para>
+		Some Linux systems (Novell SUSE Linux in particular) add entries to the <filename>nsswitch.conf</filename>
+		file that may cause operational problems with the configuration methods adopted in this book. It is
+		advisable to comment out the entries <constant>passwd_compat</constant> and <constant>group_compat</constant>
+		where they are found in this file.
+		</para></note>
+
+		<para>
+		Even at the risk of overstating the issue, incorrect and inappropriate configuration of the
+		<filename>nsswitch.conf</filename> file is a significant cause of operational problems with LDAP.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>pam_unix2.so</primary><secondary>use_ldap</secondary></indexterm>
+		For PAM LDAP configuration on this SUSE Linux 9.0 system, the simplest solution is to edit the following
+		files in the <filename>/etc/pam.d</filename> directory: <command>login</command>, <command>password</command>,
+		<command>samba</command>, <command>sshd</command>.  In each file, locate every entry that has the
+		<command>pam_unix2.so</command> entry and add to the line the entry <command>use_ldap</command> as shown
+		for the <command>login</command> module in this example:
+<screen>
+#%PAM-1.0
+auth      requisite  pam_unix2.so   nullok use_ldap #set_secrpc
+auth      required   pam_securetty.so
+auth      required   pam_nologin.so
+#auth     required   pam_homecheck.so
+auth      required   pam_env.so
+auth      required   pam_mail.so
+account   required   pam_unix2.so   use_ldap
+password  required   pam_pwcheck.s  nullok
+password  required   pam_unix2.so   nullok use_first_pass \
+                                    use_authtok use_ldap
+session   required   pam_unix2.so   none use_ldap # debug or trace
+session   required   pam_limits.so
+</screen>
+		</para>
+
+		<para>
+		<indexterm><primary>pam_ldap.so</primary></indexterm>
+		On other Linux systems that do not have an LDAP-enabled <command>pam_unix2.so</command> module,
+		you must edit these files by adding the <command>pam_ldap.so</command> modules as shown here:
+<screen>
+#%PAM-1.0
+auth     required    pam_securetty.so
+auth     required    pam_nologin.so
+auth     sufficient  pam_ldap.so
+auth     required    pam_unix2.so   nullok try_first_pass #set_secrpc
+account  sufficient  pam_ldap.so
+account  required    pam_unix2.so
+password required    pam_pwcheck.so nullok
+password required    pam_ldap.so    use_first_pass use_authtok
+password required    pam_unix2.so   nullok use_first_pass use_authtok
+session  required    pam_unix2.so   none # debug or trace
+session  required    pam_limits.so
+session  required    pam_env.so
+session  optional    pam_mail.so
+</screen>
+		This example does have the LDAP-enabled <command>pam_unix2.so</command>, but simply
+		demonstrates the use of the <command>pam_ldap.so</command> module. You can use either
+		implementation, but if the <command>pam_unix2.so</command> on your system supports
+		LDAP, you probably want to use it rather than add an additional module.
+		</para></step>
+
+	</procedure>
+
+	</sect2>
+
+	<sect2 id="sbehap-massive">
+	<title>Samba-3 PDC Configuration</title>
+
+	<para>
+	<indexterm><primary>Samba RPM Packages</primary></indexterm>
+	Verify that the Samba-3.0.20 (or later) packages are installed on each SUSE Linux server 
+	before following the steps below. If Samba-3.0.20 (or later) is not installed, you have the
+	choice to either build your own or obtain the packages from a dependable source.
+	Packages for SUSE Linux 8.x, 9.x, and SUSE Linux Enterprise Server 9, as well as for 
+	Red Hat Fedora Core and Red Hat Enterprise Linux Server 3 and 4, are included on the CD-ROM that
+	is included with this book.
+	</para>
+
+	<procedure>
+	<title>Configuration of PDC Called <constant>MASSIVE</constant></title>
+
+		<step><para>
+		Install the files in <link linkend="sbehap-massive-smbconfa"/>, 
+		<link linkend="sbehap-massive-smbconfb"/>, <link linkend="sbehap-shareconfa"/>, 
+		and <link linkend="sbehap-shareconfb"/> into the <filename>/etc/samba/</filename> 
+		directory. The three files should be added together to form the &smb.conf; 
+		master file. It is a good practice to call this file something like
+		<filename>smb.conf.master</filename> and then to perform all file edits
+		on the master file. The operational &smb.conf; is then generated as shown in
+		the next step.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>testparm</primary></indexterm>
+		Create and verify the contents of the &smb.conf; file that is generated by:
+<screen>
+&rootprompt; testparm -s smb.conf.master &gt; smb.conf
+</screen>
+		Immediately follow this with the following:
+<screen>
+&rootprompt; testparm
+</screen>
+		The output that is created should be free from errors, as shown here:
+
+<screen>
+Load smb config files from /etc/samba/smb.conf
+Processing section "[accounts]"
+Processing section "[service]"
+Processing section "[pidata]"
+Processing section "[homes]"
+Processing section "[printers]"
+Processing section "[apps]"
+Processing section "[netlogon]"
+Processing section "[profiles]"
+Processing section "[profdata]"
+Processing section "[print$]"
+Loaded services file OK.
+Server role: ROLE_DOMAIN_PDC
+Press enter to see a dump of your service definitions
+</screen>
+		</para></step>
+		
+		<step><para>
+		Delete all runtime files from prior Samba operation by executing (for SUSE
+		Linux):
+<screen>
+&rootprompt; rm /etc/samba/*tdb
+&rootprompt; rm /var/lib/samba/*tdb
+&rootprompt; rm /var/lib/samba/*dat
+&rootprompt; rm /var/log/samba/*
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>secrets.tdb</primary></indexterm>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		Samba-3 communicates with the LDAP server. The password that it uses to
+		authenticate to the LDAP server must be stored in the <filename>secrets.tdb</filename>
+		file. Execute the following to create the new <filename>secrets.tdb</filename> files
+		and store the password for the LDAP Manager:
+<screen>
+&rootprompt; smbpasswd -w not24get
+</screen>
+		The expected output from this command is:
+<screen>
+Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>smbd</primary></indexterm>
+		<indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
+		Samba-3 generates a Windows Security Identifier (SID) only when <command>smbd</command>
+		has been started. For this reason, you start Samba. After a few seconds delay,
+		execute:
+<screen>
+&rootprompt; smbclient -L localhost -U%
+&rootprompt; net getlocalsid
+</screen>
+		A report such as the following means that the domain SID has not yet
+		been written to the <filename>secrets.tdb</filename> or to the LDAP backend:
+<screen>
+[2005/03/03 23:19:34, 0] lib/smbldap.c:smbldap_connect_system(852)
+  failed to bind to server ldap://massive.abmas.biz
+with dn="cn=Manager,dc=abmas,dc=biz" Error: Can't contact LDAP server
+        (unknown)
+[2005/03/03 23:19:48, 0] lib/smbldap.c:smbldap_search_suffix(1169)
+  smbldap_search_suffix: Problem during the LDAP search:
+        (unknown) (Timed out)
+</screen>
+		The attempt to read the SID will cause and attempted bind to the LDAP server. Because the LDAP server
+		is not running, this operation will fail by way of a timeout, as shown previously. This is
+		normal output; do not worry about this error message.  When the domain has been created and
+		written to the <filename>secrets.tdb</filename> file, the output should look like this:
+<screen>
+SID for domain MASSIVE is: S-1-5-21-3504140859-1010554828-2431957765
+</screen>
+		If, after a short delay (a few seconds), the domain SID has still not been written to 
+		the <filename>secrets.tdb</filename> file, it is necessary to investigate what 
+		may be misconfigured. In this case, carefully check the &smb.conf; file for typographical 
+		errors (the most common problem).  The use of the <command>testparm</command> is highly 
+		recommended to validate the contents of this file.
+		</para></step>
+
+		<step><para>
+		When a positive domain SID has been reported, stop Samba.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>NFS server</primary></indexterm>
+		<indexterm><primary>/etc/exports</primary></indexterm>
+		<indexterm><primary>BDC</primary></indexterm>
+		<indexterm><primary>rsync</primary></indexterm>
+		Configure the NFS server for your Linux system. So you can complete the steps that
+		follow, enter into the <filename>/etc/exports</filename> the following entry:
+<screen>
+/home   *(rw,root_squash,sync)
+</screen>
+		This permits the user home directories to be used on the BDC servers for testing
+		purposes. You, of course, decide what is the best way for your site to distribute
+		data drives, and you create suitable backup and restore procedures for Abmas
+		I'd strongly recommend that for normal operation the BDC is completely independent 
+		of the PDC. rsync is a useful tool here, as it resembles the NT replication service quite 
+		closely. If you do use NFS, do not forget to start the NFS server as follows:
+<screen>
+&rootprompt; rcnfsserver start
+</screen>
+		</para></step>
+	</procedure>
+
+	<para>
+	Your Samba-3 PDC is now ready to communicate with the LDAP password backend. Let's get on with
+	configuration of the LDAP server.
+	</para>
+
+<example id="sbehap-massive-smbconfa">
+<title>LDAP Based &smb.conf; File, Server: MASSIVE &smbmdash; global Section: Part A</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+	<smbconfoption name="unix charset">LOCALE</smbconfoption>
+	<smbconfoption name="workgroup">MEGANET2</smbconfoption>
+	<smbconfoption name="netbios name">MASSIVE</smbconfoption>
+	<smbconfoption name="interfaces">eth1, lo</smbconfoption>
+	<smbconfoption name="bind interfaces only">Yes</smbconfoption>
+	<smbconfoption name="passdb backend">ldapsam:ldap://massive.abmas.biz</smbconfoption>
+	<smbconfoption name="enable privileges">Yes</smbconfoption>
+	<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+	<smbconfoption name="log level">1</smbconfoption>
+	<smbconfoption name="syslog">0</smbconfoption>
+	<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+	<smbconfoption name="max log size">50</smbconfoption>
+	<smbconfoption name="smb ports">139</smbconfoption>
+	<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+	<smbconfoption name="time server">Yes</smbconfoption>
+	<smbconfoption name="printcap name">CUPS</smbconfoption>
+	<smbconfoption name="show add printer wizard">No</smbconfoption>
+	<smbconfoption name="add user script">/opt/IDEALX/sbin/smbldap-useradd -m "%u"</smbconfoption>
+	<smbconfoption name="delete user script">/opt/IDEALX/sbin/smbldap-userdel "%u"</smbconfoption>
+	<smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd -p "%g"</smbconfoption>
+	<smbconfoption name="delete group script">/opt/IDEALX/sbin/smbldap-groupdel "%g"</smbconfoption>
+	<smbconfoption name="add user to group script">/opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"</smbconfoption>
+	<smbconfoption name="delete user from group script">/opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"</smbconfoption>
+	<smbconfoption name="set primary group script">/opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"</smbconfoption>
+	<smbconfoption name="add machine script">/opt/IDEALX/sbin/smbldap-useradd -w "%u"</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="sbehap-massive-smbconfb">
+<title>LDAP Based &smb.conf; File, Server: MASSIVE &smbmdash; global Section: Part B</title>
+<smbconfblock>
+	<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+	<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
+	<smbconfoption name="logon drive">X:</smbconfoption>
+	<smbconfoption name="domain logons">Yes</smbconfoption>
+	<smbconfoption name="preferred master">Yes</smbconfoption>
+	<smbconfoption name="wins support">Yes</smbconfoption>
+	<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
+	<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+	<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+	<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+	<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+	<smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
+	<smbconfoption name="idmap backend">ldap:ldap://massive.abmas.biz</smbconfoption>
+	<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+	<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+	<smbconfoption name="map acl inherit">Yes</smbconfoption>
+	<smbconfoption name="printing">cups</smbconfoption>
+	<smbconfoption name="printer admin">root, chrisr</smbconfoption>
+</smbconfblock>
+</example>
+
+	</sect2>
+
+
+	<sect2 id="sbeidealx">
+	<title>Install and Configure Idealx smbldap-tools Scripts</title>
+
+	<para>
+	<indexterm><primary>Idealx</primary><secondary>smbldap-tools</secondary></indexterm>
+	The Idealx scripts, or equivalent, are necessary to permit Samba-3 to manage accounts
+	on the LDAP server. You have chosen the Idealx scripts because they are the best-known
+	LDAP configuration scripts. The use of these scripts will help avoid the necessity
+	to create custom scripts. It is easy to download them from the Idealx
+	<ulink url="http://samba.idealx.org/index.en.html">Web site</ulink>. The tarball may
+	be directly <ulink url="http://samba.idealx.org/dist/smbldap-tools-0.9.1.tgz">downloaded</ulink>
+	from this site also. Alternatively, you may obtain the 
+	<ulink url="http://samba.idealx.org/dist/smbldap-tools-0.9.1-1.src.rpm">smbldap-tools-0.9.1-1.src.rpm</ulink>
+	file that may be used to build an installable RPM package for your Linux system.
+	</para>
+
+<note><para>
+The smbldap-tools scripts can be installed in any convenient directory of your choice, in which case you must
+change the path to them in your &smb.conf; file on the PDC (<constant>MASSIVE</constant>).
+</para></note>
+
+	<para>
+	The smbldap-tools are located in <filename>/opt/IDEALX/sbin</filename>.
+	The scripts are not needed on BDC machines because all LDAP updates are handled by
+	the PDC alone.
+	</para>
+
+	<sect3>
+	<title>Installation of smbldap-tools from the Tarball</title>
+
+	<para>
+	To perform a manual installation of the smbldap-tools scripts, the following procedure may be used:
+	</para>
+
+	<procedure id="idealxscript">
+	<title>Unpacking and Installation Steps for the <constant>smbldap-tools</constant> Tarball</title>
+
+		<step><para>
+		Create the <filename>/opt/IDEALX/sbin</filename> directory, and set its permissions
+		and ownership as shown here:
+<screen>
+&rootprompt; mkdir -p /opt/IDEALX/sbin
+&rootprompt; chown root:root /opt/IDEALX/sbin
+&rootprompt; chmod 755 /opt/IDEALX/sbin
+&rootprompt; mkdir -p /etc/smbldap-tools
+&rootprompt; chown root:root /etc/smbldap-tools
+&rootprompt; chmod 755 /etc/smbldap-tools
+</screen>
+		</para></step>
+
+		<step><para>
+		If you wish to use the downloaded tarball, unpack the smbldap-tools in a suitable temporary location.
+		Change into either the directory extracted from the tarball or the smbldap-tools
+		directory in your <filename>/usr/share/doc/packages</filename> directory tree.
+		</para></step>
+
+		<step><para>
+		Copy all the <filename>smbldap-*</filename> and the <filename>configure.pl</filename> files into the 
+		<filename>/opt/IDEALX/sbin</filename> directory, as shown here:
+<screen>
+&rootprompt; cd smbldap-tools-0.9.1/
+&rootprompt; cp smbldap-* configure.pl *pm /opt/IDEALX/sbin/
+&rootprompt; cp smbldap*conf /etc/smbldap-tools/
+&rootprompt; chmod 750 /opt/IDEALX/sbin/smbldap-*
+&rootprompt; chmod 750 /opt/IDEALX/sbin/configure.pl
+&rootprompt; chmod 640 /etc/smbldap-tools/smbldap.conf
+&rootprompt; chmod 600 /etc/smbldap-tools/smbldap_bind.conf
+</screen>
+		</para></step>
+
+		<step><para>
+		The smbldap-tools scripts master control file must now be configured.
+		Change to the <filename>/opt/IDEALX/sbin</filename> directory, then edit the
+		<filename>smbldap_tools.pm</filename> to affect the changes
+		shown here:
+<screen>
+...
+# ugly funcs using global variables and spawning openldap clients
+
+my $smbldap_conf="/etc/smbldap-tools/smbldap.conf";
+my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf";
+...
+</screen>
+		</para></step>
+
+		<step><para>
+		To complete the configuration of the smbldap-tools, set the permissions and ownership
+		by executing the following commands:
+<screen>
+&rootprompt; chown root:root /opt/IDEALX/sbin/* 
+&rootprompt; chmod 755 /opt/IDEALX/sbin/smbldap-*
+&rootprompt; chmod 640 /opt/IDEALX/sbin/smb*pm 
+</screen>
+		The smbldap-tools scripts are now ready for the configuration step outlined in
+		<link linkend="smbldap-init"/>.
+		</para></step>
+
+	</procedure>
+
+	</sect3>
+
+	<sect3>
+	<title>Installing smbldap-tools from the RPM Package</title>
+
+	<para>
+	In the event that you have elected to use the RPM package provided by Idealx, download the
+	source RPM <filename>smbldap-tools-0.9.1-1.src.rpm</filename>, then follow this procedure:
+	</para>
+
+	<procedure>
+	<title>Installation Steps for <constant>smbldap-tools</constant> RPM's</title>
+
+		<step><para>
+		Install the source RPM that has been downloaded as follows:
+<screen>
+&rootprompt; rpm -i smbldap-tools-0.9.1-1.src.rpm
+</screen>
+		</para></step>
+
+		<step><para>
+		Change into the directory in which the SPEC files are located. On SUSE Linux:
+<screen>
+&rootprompt; cd /usr/src/packages/SPECS
+</screen>
+		On Red Hat Linux systems:
+<screen>
+&rootprompt; cd /usr/src/redhat/SPECS
+</screen>
+		</para></step>
+
+		<step><para>
+		Edit the <filename>smbldap-tools.spec</filename> file to change the value of the
+		<constant>_sysconfig</constant> macro as shown here:
+<screen>
+%define _prefix /opt/IDEALX
+%define _sysconfdir /etc
+</screen>
+		Note: Any suitable directory can be specified.
+		</para></step>
+
+		<step><para>
+		Build the package by executing:
+<screen>
+&rootprompt; rpmbuild -ba -v smbldap-tools.spec
+</screen>
+		A build process that has completed without error will place the installable binary
+		files in the directory <filename>../RPMS/noarch</filename>.
+		</para></step>
+
+		<step><para>
+		Install the binary package by executing:
+<screen>
+&rootprompt; rpm -Uvh ../RPMS/noarch/smbldap-tools-0.9.1-1.noarch.rpm
+</screen>
+		</para></step>
+
+	</procedure>
+
+	<para>
+	The Idealx scripts should now be ready for configuration using the steps outlined in
+	<link linkend="smbldap-init">Configuration of smbldap-tools</link>.
+	</para>
+
+	</sect3>
+
+	<sect3 id="smbldap-init">
+	<title>Configuration of smbldap-tools</title>
+
+	<para>
+	Prior to use, the smbldap-tools must be configured to match the settings in the &smb.conf; file
+	and to match the settings in the <filename>/etc/openldap/slapd.conf</filename> file. The assumption
+	is made that the &smb.conf; file has correct contents. The following procedure ensures that
+	this is completed correctly:
+	</para>
+
+	<para>
+	The smbldap-tools require that the NetBIOS name (machine name) of the Samba server be included
+	in the &smb.conf; file.
+	</para>
+
+	<procedure>
+	<title>Configuration Steps for <constant>smbldap-tools</constant> to Enable Use</title>
+
+		<step><para>
+		Change into the directory that contains the <filename>configure.pl</filename> script.
+<screen>
+&rootprompt; cd /opt/IDEALX/sbin
+</screen>
+		</para></step>
+
+		<step><para>
+		Execute the <filename>configure.pl</filename> script as follows:
+<screen>
+&rootprompt; ./configure.pl
+</screen>
+		The interactive use of this script for the PDC is demonstrated here:
+<screen>
+&rootprompt; /opt/IDEALX/sbin/configure.pl 
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+       smbldap-tools script configuration
+       -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+Before starting, check
+ . if your samba controller is up and running.
+ . if the domain SID is defined (you can get it with the
+                                                    'net getlocalsid')
+
+ . you can leave the configuration using the Crtl-c key combination
+ . empty value can be set with the "." character
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+Looking for configuration files...
+
+Samba Config File Location [/etc/samba/smb.conf] > 
+smbldap-tools configuration file Location (global parameters)
+                        [/etc/opt/IDEALX/smbldap-tools/smbldap.conf] > 
+smbldap Config file Location (bind parameters) 
+                   [/etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf] > 
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+Let's start configuring the smbldap-tools scripts ...
+
+. workgroup name: name of the domain Samba act as a PDC
+  workgroup name [MEGANET2] > 
+. netbios name: netbios name of the samba controler
+  netbios name [MASSIVE] > 
+. logon drive: local path to which the home directory 
+                    will be connected (for NT Workstations). Ex: 'H:'
+  logon drive [H:] > 
+. logon home: home directory location (for Win95/98 or NT Workstation)
+  (use %U as username) Ex:'\\MASSIVE\%U'
+  logon home (press the "." character if you don't want homeDirectory)
+                                                     [\\MASSIVE\%U] > 
+. logon path: directory where roaming profiles are stored. 
+                                            Ex:'\\MASSIVE\profiles\%U'
+  logon path (press the "." character
+               if you don't want roaming profile) [\\%L\profiles\%U] >
+. home directory prefix (use %U as username)
+                                           [/home/%U] > /data/users/%U
+. default users' homeDirectory mode [700] > 
+. default user netlogon script (use %U as username)
+                                                 [scripts\logon.bat] >
+  default password validation time (time in days) [45] > 900
+. ldap suffix [dc=abmas,dc=biz] > 
+. ldap group suffix [ou=Groups] > 
+. ldap user suffix [ou=People,ou=Users] > 
+. ldap machine suffix [ou=Computers,ou=Users] > 
+. Idmap suffix [ou=Idmap] > 
+. sambaUnixIdPooldn: object where you want to store the next uidNumber
+  and gidNumber available for new users and groups
+  sambaUnixIdPooldn object (relative to ${suffix}) 
+                                          [sambaDomainName=MEGANET2] > 
+. ldap master server: IP adress or DNS name of the master 
+                                                (writable) ldap server
+  ldap master server [massive.abmas.biz] > 
+. ldap master port [389] > 
+. ldap master bind dn [cn=Manager,dc=abmas,dc=biz] > 
+. ldap master bind password [] > 
+. ldap slave server: IP adress or DNS name of the slave ldap server: 
+                                            can also be the master one
+  ldap slave server [massive.abmas.biz] > 
+. ldap slave port [389] > 
+. ldap slave bind dn [cn=Manager,dc=abmas,dc=biz] > 
+. ldap slave bind password [] > 
+. ldap tls support (1/0) [0] > 
+. SID for domain MEGANET2: SID of the domain 
+                      (can be obtained with 'net getlocalsid MASSIVE')
+  SID for domain MEGANET2
+                        [S-1-5-21-3504140859-1010554828-2431957765]] >
+. unix password encryption: encryption used for unix passwords
+  unix password encryption (CRYPT, MD5, SMD5, SSHA, SHA) [SSHA] > MD5
+. default user gidNumber [513] > 
+. default computer gidNumber [515] > 
+. default login shell [/bin/bash] > 
+. default skeleton directory [/etc/skel] > 
+. default domain name to append to mail adress [] > abmas.biz
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+backup old configuration files:
+  /etc/opt/IDEALX/smbldap-tools/smbldap.conf->
+                        /etc/opt/IDEALX/smbldap-tools/smbldap.conf.old
+  /etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf->
+                   /etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf.old
+writing new configuration file:
+  /etc/opt/IDEALX/smbldap-tools/smbldap.conf done.
+  /etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf done.
+</screen>
+		Since a slave LDAP server has not been configured, it is necessary to specify the IP
+		address of the master LDAP server for both the master and the slave configuration
+		prompts.
+		</para></step>
+
+		<step><para>
+		Change to the directory that contains the <filename>smbldap.conf</filename> file,
+		then verify its contents.
+		</para></step>
+
+	</procedure>
+
+	<para>
+	The smbldap-tools are now ready for use.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>LDAP Initialization and Creation of User and Group Accounts</title>
+
+	<para>
+	The LDAP database must be populated with well-known Windows domain user accounts and domain group 
+	accounts before Samba can be used. The following procedures step you through the process.
+	</para>
+
+	<para>
+	At this time, Samba-3 requires that on a PDC all UNIX (POSIX) group accounts that are
+	mapped (linked) to Windows domain group accounts must be in the LDAP database. It does not
+	hurt to have UNIX user and group accounts in both the system files as well as in the LDAP
+	database. From a UNIX system perspective, the NSS resolver checks system files before
+	referring to LDAP. If the UNIX system can resolve (find) an account in the system file, it
+	does not need to ask LDAP.
+	</para>
+
+	<para>
+	Addition of an account to the LDAP backend can be done in two ways:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		<indexterm><primary>NIS</primary></indexterm>
+		<indexterm><primary>/etc/passwd</primary></indexterm>
+		<indexterm><primary>Posix accounts</primary></indexterm>
+		<indexterm><primary>pdbedit</primary></indexterm>
+		<indexterm><primary>SambaSamAccount</primary></indexterm>
+		<indexterm><primary>PosixAccount</primary></indexterm>
+		If you always have a user account in the <filename>/etc/passwd</filename> on every 
+		server or in a NIS(+) backend, it is not necessary to add POSIX accounts for them in 
+		LDAP. In this case, you can add Windows domain user accounts using the 
+		<command>pdbedit</command> utility. Use of this tool from the command line adds the 
+		SambaSamAccount entry for the user, but does not add the PosixAccount entry for the user.
+		</para>
+
+		<para>
+		This is the least desirable method because when LDAP is used as the passwd backend Samba
+		expects the POSIX account to be in LDAP also. It is possible to use the PADL account
+		migration tool to migrate all system accounts from either the <filename>/etc/passwd</filename>
+		files, or from NIS, to LDAP.
+		</para></listitem>
+
+		<listitem><para>
+		If you decide that it is probably a good idea to add both the PosixAccount attributes
+		as well as the SambaSamAccount attributes for each user, then a suitable script is needed.
+		In the example system you are installing in this exercise, you are making use of the
+		Idealx smbldap-tools scripts. A copy of these tools, preconfigured for this system,
+		is included on the enclosed CD-ROM under <filename>Chap06/Tools.</filename>
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	<indexterm><primary>Idealx</primary><secondary>smbldap-tools</secondary></indexterm>
+	If you wish to have more control over how the LDAP database is initialized or 
+	if you don't want to use the Idealx smbldap-tools, you should refer to 
+	<link linkend="appendix"/>, <link linkend="altldapcfg"/>.
+	</para>
+
+	<para>
+	<indexterm><primary>smbldap-populate</primary></indexterm>
+	The following steps initialize the LDAP database, and then you can add user and group
+	accounts that Samba can use. You use the <command>smbldap-populate</command> to
+	seed the LDAP database. You then manually add the accounts shown in <link linkend="sbehap-bigacct"/>. 
+	The list of users does not cover all 500 network users; it provides examples only.
+	</para>
+
+	<note><para>
+	<indexterm><primary>LDAP</primary><secondary>database</secondary></indexterm>
+	<indexterm><primary>directory</primary><secondary>People container</secondary></indexterm>
+	<indexterm><primary>directory</primary><secondary>Computers container</secondary></indexterm>
+	In the following examples, as the LDAP database is initialized, we do create a container
+	for Computer (machine) accounts. In the Samba-3 &smb.conf; files, specific use is made
+	of the People container, not the Computers container, for domain member accounts. This is not a
+	mistake; it is a deliberate action that is necessitated by the fact that the resolution of 
+	a machine (computer) account to a UID is done via NSS. The only way this can be handled is
+	using the NSS (<filename>/etc/nsswitch.conf</filename>) entry for <constant>passwd</constant>,
+	which is resolved using the <filename>nss_ldap</filename> library. The configuration file for
+	the <filename>nss_ldap</filename> library is the file <filename>/etc/ldap.conf</filename> that
+	provides only one possible LDAP search command that is specified by the entry called
+	<constant>nss_base_passwd</constant>. This means that the search path must take into account
+	the directory structure so that the LDAP search will commence at a level that is above
+	both the Computers container and the Users (or People) container. If this is done, it is
+	necessary to use a search that will descend the directory tree so that the machine account
+	can be found. Alternatively, by placing all machine accounts in the People container, we
+	are able to sidestep this limitation. This is the simpler solution that has been adopted
+	in this chapter.
+	</para></note>
+
+
+	<table id="sbehap-bigacct">
+		<title>Abmas Network Users and Groups</title>
+		<tgroup cols="4">
+			<colspec align="left"/>
+			<colspec align="left"/>
+			<colspec align="left"/>
+			<colspec align="left"/>
+			<thead>
+				<row>
+					<entry align="center">Account Name</entry>
+					<entry align="center">Type</entry>
+					<entry align="center">ID</entry>
+					<entry align="center">Password</entry>
+				</row>
+			</thead>
+			<tbody>
+				<row>
+					<entry>Robert Jordan</entry>
+					<entry>User</entry>
+					<entry>bobj</entry>
+					<entry>n3v3r2l8</entry>
+				</row>
+				<row>
+					<entry>Stanley Soroka</entry>
+					<entry>User</entry>
+					<entry>stans</entry>
+					<entry>impl13dst4r</entry>
+				</row>
+				<row>
+					<entry>Christine Roberson</entry>
+					<entry>User</entry>
+					<entry>chrisr</entry>
+					<entry>S9n0nw4ll</entry>
+				</row>
+				<row>
+					<entry>Mary Vortexis</entry>
+					<entry>User</entry>
+					<entry>maryv</entry>
+					<entry>kw13t0n3</entry>
+				</row>
+				<row>
+					<entry>Accounts</entry>
+					<entry>Group</entry>
+					<entry>Accounts</entry>
+					<entry></entry>
+				</row>
+				<row>
+					<entry>Finances</entry>
+					<entry>Group</entry>
+					<entry>Finances</entry>
+					<entry></entry>
+				</row>
+				<row>
+					<entry>Insurance</entry>
+					<entry>Group</entry>
+					<entry>PIOps</entry>
+					<entry></entry>
+				</row>
+			</tbody>
+		</tgroup>
+	</table>
+
+	<procedure id="creatacc">
+	<title>LDAP Directory Initialization Steps</title>
+
+		<step><para>
+		Start the LDAP server by executing:
+<screen>
+&rootprompt; rcldap start
+Starting ldap-server                           done
+</screen>
+		</para></step>
+
+		<step><para>
+		Change to the <filename>/opt/IDEALX/sbin</filename> directory.
+		</para></step>
+
+		<step><para>
+		Execute the script that will populate the LDAP database as shown here:
+<screen>
+&rootprompt; ./smbldap-populate -a root -k 0 -m 0
+</screen>
+		The expected output from this is:
+<screen>
+Using workgroup name from smb.conf: sambaDomainName=MEGANET2
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+=> Warning: you must update smbldap.conf configuration file to :
+=> sambaUnixIdPooldn parameter must be set
+	to "sambaDomainName=MEGANET2,dc=abmas,dc=biz"
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+Using builtin directory structure
+adding new entry: dc=abmas,dc=biz
+adding new entry: ou=People,dc=abmas,dc=biz
+adding new entry: ou=Groups,dc=abmas,dc=biz
+entry ou=People,dc=abmas,dc=biz already exist.
+adding new entry: ou=Idmap,dc=abmas,dc=biz
+adding new entry: sambaDomainName=MEGANET2,dc=abmas,dc=biz
+adding new entry: uid=root,ou=People,dc=abmas,dc=biz
+adding new entry: uid=nobody,ou=People,dc=abmas,dc=biz
+adding new entry: cn=Domain Admins,ou=Groups,dc=abmas,dc=biz
+adding new entry: cn=Domain Users,ou=Groups,dc=abmas,dc=biz
+adding new entry: cn=Domain Guests,ou=Groups,dc=abmas,dc=biz
+adding new entry: cn=Domain Computers,ou=Groups,dc=abmas,dc=biz
+adding new entry: cn=Administrators,ou=Groups,dc=abmas,dc=biz
+adding new entry: cn=Print Operators,ou=Groups,dc=abmas,dc=biz
+adding new entry: cn=Backup Operators,ou=Groups,dc=abmas,dc=biz
+adding new entry: cn=Replicators,ou=Groups,dc=abmas,dc=biz
+</screen>
+		</para></step>
+
+		<step><para>
+		Edit the <filename>/etc/smbldap-tools/smbldap.conf</filename> file so that the following
+		information is changed from:
+<screen>
+# Where to store next uidNumber and gidNumber available
+sambaUnixIdPooldn="cn=NextFreeUnixId,${suffix}"
+</screen>
+		to read, after modification:
+<screen>
+# Where to store next uidNumber and gidNumber available
+#sambaUnixIdPooldn="cn=NextFreeUnixId,${suffix}"
+sambaUnixIdPooldn="sambaDomainName=MEGANET2,dc=abmas,dc=biz"
+</screen>
+		</para></step>
+
+		<step><para>
+		It is necessary to restart the LDAP server as shown here:
+<screen>
+&rootprompt; rcldap restart
+Shutting down ldap-server                            done
+Starting ldap-server                                 done
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>slapcat</primary></indexterm>
+		So that we can use a global IDMAP repository, the LDAP directory must have a container object for IDMAP data. 
+		There are several ways you can check that your LDAP database is able to receive IDMAP information. One of 
+		the simplest is to execute:
+<screen>
+&rootprompt; slapcat | grep -i idmap
+dn: ou=Idmap,dc=abmas,dc=biz
+ou: idmap
+</screen>
+		<indexterm> <primary>ldapadd</primary></indexterm>
+	        If the execution of this command does not return IDMAP entries, you need to create an LDIF
+		template file (see <link linkend="sbehap-ldifadd"/>). You can add the required entries using 
+		the following command:
+<screen>
+&rootprompt; ldapadd -x -D "cn=Manager,dc=abmas,dc=biz" \
+		-w not24get &lt; /etc/openldap/idmap.LDIF
+</screen>
+		Samba automatically populates this LDAP directory container when it needs to.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>slapcat</primary></indexterm>
+		It looks like all has gone well, as expected. Let's confirm that this is the case
+		by running a few tests. First we check the contents of the database directly
+		by running <command>slapcat</command> as follows (the output has been cut down):
+<screen>
+&rootprompt; slapcat
+dn: dc=abmas,dc=biz
+objectClass: dcObject
+objectClass: organization
+dc: abmas
+o: abmas
+structuralObjectClass: organization
+entryUUID: 5ab02bf6-c536-1027-9d29-b1f32350fb43
+creatorsName: cn=Manager,dc=abmas,dc=biz
+createTimestamp: 20031217234200Z
+entryCSN: 2003121723:42:00Z#0x0001#0#0000
+modifiersName: cn=Manager,dc=abmas,dc=biz
+modifyTimestamp: 20031217234200Z
+...
+dn: cn=Domain Computers,ou=Groups,dc=abmas,dc=biz
+objectClass: posixGroup
+objectClass: sambaGroupMapping
+gidNumber: 553
+cn: Domain Computers
+description: Netbios Domain Computers accounts
+sambaSID: S-1-5-21-3504140859-1010554828-2431957765-553
+sambaGroupType: 2
+displayName: Domain Computers
+structuralObjectClass: posixGroup
+entryUUID: 5e0a41d8-c536-1027-9d3b-b1f32350fb43
+creatorsName: cn=Manager,dc=abmas,dc=biz
+createTimestamp: 20031217234206Z
+entryCSN: 2003121723:42:06Z#0x0002#0#0000
+modifiersName: cn=Manager,dc=abmas,dc=biz
+modifyTimestamp: 20031217234206Z
+</screen>
+		This looks good so far.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>ldapsearch</primary></indexterm>
+		The next step is to prove that the LDAP server is running and responds to a
+		search request. Execute the following as shown (output has been cut to save space):
+<screen>
+&rootprompt; ldapsearch -x -b "dc=abmas,dc=biz" "(ObjectClass=*)"
+# extended LDIF
+#
+# LDAPv3
+# base &lt;dc=abmas,dc=biz&gt; with scope sub
+# filter: (ObjectClass=*)
+# requesting: ALL
+#
+
+# abmas.biz
+dn: dc=abmas,dc=biz
+objectClass: dcObject
+objectClass: organization
+dc: abmas
+o: abmas
+
+# People, abmas.biz
+dn: ou=People,dc=abmas,dc=biz
+objectClass: organizationalUnit
+ou: People
+...
+# Domain Computers, Groups, abmas.biz
+dn: cn=Domain Computers,ou=Groups,dc=abmas,dc=biz
+objectClass: posixGroup
+objectClass: sambaGroupMapping
+gidNumber: 553
+cn: Domain Computers
+description: Netbios Domain Computers accounts
+sambaSID: S-1-5-21-3504140859-1010554828-2431957765-553
+sambaGroupType: 2
+displayName: Domain Computers
+
+# search result
+search: 2
+result: 0 Success
+
+# numResponses: 20
+# numEntries: 19
+</screen>
+		Good. It is all working just fine.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>getent</primary></indexterm>
+		You must now make certain that the NSS resolver can interrogate LDAP also.
+		Execute the following commands:
+<screen>
+&rootprompt; getent passwd | grep root
+root:x:998:512:Netbios Domain Administrator:/home:/bin/false
+
+&rootprompt; getent group | grep Domain
+Domain Admins:x:512:root
+Domain Users:x:513:
+Domain Guests:x:514:
+Domain Computers:x:553:
+</screen>
+		<indexterm><primary>nss_ldap</primary></indexterm>
+		This demonstrates that the <command>nss_ldap</command> library is functioning
+		as it should. If these two steps fail to produce this information, refer to
+		<link linkend="sbeavoid"/> for diagnostic procedures that can be followed to
+		isolate the cause of the problem. Proceed to the next step only when the previous steps
+		have been successfully completed.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>smbldap-useradd</primary></indexterm>
+		<indexterm><primary>smbldap-passwd</primary></indexterm>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		Our database is now ready for the addition of network users. For each user for
+		whom an account must be created, execute the following:
+<screen>
+&rootprompt; ./smbldap-useradd -m -a <constant>username</constant>
+&rootprompt; ./smbldap-passwd <constant>username</constant>
+Changing password for <constant>username</constant>
+New password : XXXXXXXX
+Retype new password : XXXXXXXX
+
+&rootprompt; smbpasswd <constant>username</constant>
+New SMB password: XXXXXXXX
+Retype new SMB password: XXXXXXXX
+</screen>
+		where <constant>username</constant> is the login ID for each user.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>getent</primary></indexterm>
+		Now verify that the UNIX (POSIX) accounts can be resolved via NSS by executing the
+		following:
+<screen>
+&rootprompt; getent passwd
+root:x:0:0:root:/root:/bin/bash
+bin:x:1:1:bin:/bin:/bin/bash
+...
+root:x:0:512:Netbios Domain Administrator:/home:/bin/false
+nobody:x:999:514:nobody:/dev/null:/bin/false
+bobj:x:1000:513:System User:/home/bobj:/bin/bash
+stans:x:1001:513:System User:/home/stans:/bin/bash
+chrisr:x:1002:513:System User:/home/chrisr:/bin/bash
+maryv:x:1003:513:System User:/home/maryv:/bin/bash
+</screen>
+		This demonstrates that user account resolution via LDAP is working.
+		</para></step>
+
+		<step><para>
+		This step will determine whether or not identity resolution is working correctly.
+		Do not procede is this step fails, rather find the cause of the failure. The
+		<command>id</command> command may be used to validate your configuration so far,
+		as shown here:
+<screen>
+&rootprompt; id chrisr
+uid=1002(chrisr) gid=513(Domain Users) groups=513(Domain Users)
+</screen>
+		This confirms that the UNIX (POSIX) user account information can be resolved from LDAP
+		by system tools that make a getentpw() system call.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>smbldap-usermod</primary></indexterm>
+		The root account must have UID=0; if not, this means that operations conducted from
+		a Windows client using tools such as the Domain User Manager fails under UNIX because
+		the management of user and group accounts requires that the UID=0. Additionally, it is
+		a good idea to make certain that no matter how root account credentials are resolved,
+		the home directory and shell are valid. You decide to effect this immediately
+		as demonstrated here:
+<screen>
+&rootprompt; cd /opt/IDEALX/sbin
+&rootprompt; ./smbldap-usermod -u 0 -d /root -s /bin/bash root
+</screen>
+		</para></step>
+
+		<step><para>
+		Verify that the changes just made to the <constant>root</constant> account were
+		accepted by executing:
+<screen>
+&rootprompt; getent passwd | grep root
+root:x:0:0:root:/root:/bin/bash
+root:x:0:512:Netbios Domain Administrator:/root:/bin/bash
+</screen>
+		This demonstrates that the changes were accepted.
+		</para></step>
+
+		<step><para>
+		Make certain that a home directory has been created for every user by listing the
+		directories in <filename>/home</filename> as follows:
+<screen>
+&rootprompt; ls -al /home
+drwxr-xr-x   8 root   root         176 Dec 17 18:50 ./
+drwxr-xr-x  21 root   root         560 Dec 15 22:19 ../
+drwx------   7 bobj   Domain Users     568 Dec 17 01:16 bobj/
+drwx------   7 chrisr Domain Users     568 Dec 17 01:19 chrisr/
+drwx------   7 maryv  Domain Users     568 Dec 17 01:27 maryv/
+drwx------   7 stans  Domain Users     568 Dec 17 01:43 stans/
+</screen>
+		This is precisely what we want to see.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>ldapsam</primary></indexterm>
+		<indexterm><primary>pdbedit</primary></indexterm>
+		The final validation step involves making certain that Samba-3 can obtain the user
+		accounts from the LDAP ldapsam passwd backend. Execute the following command as shown:
+<screen>
+&rootprompt; pdbedit -Lv chrisr
+Unix username:        chrisr
+NT username:          chrisr
+Account Flags:        [U          ]
+User SID:             S-1-5-21-3504140859-1010554828-2431957765-3004
+Primary Group SID:    S-1-5-21-3504140859-1010554828-2431957765-513
+Full Name:            System User
+Home Directory:       \\MASSIVE\homes
+HomeDir Drive:        H:
+Logon Script:         scripts\login.cmd
+Profile Path:         \\MASSIVE\profiles\chrisr
+Domain:               MEGANET2
+Account desc:         System User
+Workstations:
+Munged dial:
+Logon time:           0
+Logoff time:          Mon, 18 Jan 2038 20:14:07 GMT
+Kickoff time:         Mon, 18 Jan 2038 20:14:07 GMT
+Password last set:    Wed, 17 Dec 2003 17:17:40 GMT
+Password can change:  Wed, 17 Dec 2003 17:17:40 GMT
+Password must change: Mon, 18 Jan 2038 20:14:07 GMT
+Last bad password   : 0
+Bad password count  : 0
+Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
+</screen>
+		This looks good. Of course, you fully expected that it would all work, didn't you?
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>smbldap-groupadd</primary></indexterm>
+		Now you add the group accounts that are used on the Abmas network. Execute
+		the following exactly as shown:
+<screen>
+&rootprompt; ./smbldap-groupadd -a Accounts
+&rootprompt; ./smbldap-groupadd -a Finances
+&rootprompt; ./smbldap-groupadd -a PIOps
+</screen>
+		The addition of groups does not involve keyboard interaction, so the lack of console
+		output is of no concern.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>getent</primary></indexterm>
+		You really do want to confirm that UNIX group resolution from LDAP is functioning 
+		as it should. Let's do this as shown here:
+<screen>
+&rootprompt; getent group
+...
+Domain Admins:x:512:root
+Domain Users:x:513:bobj,stans,chrisr,maryv
+Domain Guests:x:514:
+...
+Accounts:x:1000:
+Finances:x:1001:
+PIOps:x:1002:
+</screen>
+		The well-known special accounts (Domain Admins, Domain Users, Domain Guests), as well
+		as our own site-specific group accounts, are correctly listed. This is looking good.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>list</tertiary></indexterm>
+		The final step we need to validate is that Samba can see all the Windows domain groups
+		and that they are correctly mapped to the respective UNIX group account. To do this,
+		just execute the following command:
+<screen>
+&rootprompt; net groupmap list
+Domain Admins (S-1-5-21-3504140859-...-2431957765-512) -> Domain Admins
+Domain Users (S-1-5-21-3504140859-...-2431957765-513) -> Domain Users
+Domain Guests (S-1-5-21-3504140859-...-2431957765-514) -> Domain Guests
+...
+Accounts (S-1-5-21-3504140859-1010554828-2431957765-3001) -> Accounts
+Finances (S-1-5-21-3504140859-1010554828-2431957765-3003) -> Finances
+PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps
+</screen>
+		This is looking good. Congratulations &smbmdash; it works! Note that in the above output
+		the lines were shortened by replacing the middle value (1010554828) of the SID with the 
+		ellipsis (...).
+		</para></step>
+
+		<step><para>
+		The server you have so carefully built is now ready for another important step. You 
+		start the Samba-3 server and validate its operation. Execute the following to render all 
+		the processes needed fully operative so that, on system reboot, they are automatically 
+		started:
+<screen>
+&rootprompt; chkconfig named on
+&rootprompt; chkconfig dhcpd on
+&rootprompt; chkconfig ldap on
+&rootprompt; chkconfig nmb on
+&rootprompt; chkconfig smb on
+&rootprompt; chkconfig winbind on
+&rootprompt; rcnmb start
+&rootprompt; rcsmb start
+&rootprompt; rcwinbind start
+</screen>
+		</para></step>
+
+		<step><para>
+		The next step might seem a little odd at this point, but take note that you are about to
+		start <command>winbindd</command>, which must be able to authenticate to the PDC via the
+		localhost interface with the <command>smbd</command> process. This account can be
+		easily created by joining the PDC to the domain by executing the following command:
+<screen>
+&rootprompt; net rpc join -S MASSIVE -U root%not24get
+</screen>
+		Note: Before executing this command on the PDC, both <command>nmbd</command> and
+		<command>smbd</command> must be started so that the <command>net</command> command
+		can communicate with <command>smbd</command>. The expected output is as follows:
+<screen>
+Joined domain MEGANET2.
+</screen>
+		This indicates that the domain security account for the PDC has been correctly created.
+		</para></step>
+
+		<step><para>
+		At this time it is necessary to restart <command>winbindd</command> so that it can
+		correctly authenticate to the PDC. The following command achieves that:
+<screen>
+&rootprompt; rcwinbind restart
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>smbclient</primary></indexterm>
+		You may now check Samba-3 operation as follows:
+<screen>
+&rootprompt; smbclient -L massive -U%
+
+        Sharename      Type      Comment
+        ---------      ----      -------
+        IPC$           IPC       IPC Service (Samba 3.0.20)
+        accounts       Disk      Accounting Files
+        service        Disk      Financial Services Files
+        pidata         Disk      Property Insurance Files
+        apps           Disk      Application Files
+        netlogon       Disk      Network Logon Service
+        profiles       Disk      Profile Share
+        profdata       Disk      Profile Data Share
+        ADMIN$         IPC       IPC Service (Samba 3.0.20)
+
+        Server               Comment
+        ---------            -------
+        MASSIVE              Samba 3.0.20
+
+        Workgroup            Master
+        ---------            -------
+        MEGANET2             MASSIVE
+</screen>
+	This shows that an anonymous connection is working.
+		</para></step>
+
+		<step><para>
+		For your finale, let's try an authenticated connection:
+<screen>
+&rootprompt; smbclient //massive/bobj -Ubobj%n3v3r2l8
+smb: \> dir
+  .                    D        0  Wed Dec 17 01:16:19 2003
+  ..                   D        0  Wed Dec 17 19:04:42 2003
+  bin                  D        0  Tue Sep  2 04:00:57 2003
+  Documents            D        0  Sun Nov 30 07:28:20 2003
+  public_html          D        0  Sun Nov 30 07:28:20 2003
+  .urlview             H      311  Fri Jul  7 06:55:35 2000
+  .dvipsrc             H      208  Fri Nov 17 11:22:02 1995
+
+          57681 blocks of size 524288. 57128 blocks available
+smb: \> q
+</screen>
+		Well done. All is working fine.
+		</para></step>
+	</procedure>
+
+	<para>
+	The server <constant>MASSIVE</constant> is now configured, and it is time to move onto the next task.
+	</para>
+
+	</sect2>
+
+	<sect2 id="sbehap-ptrcfg">
+	<title>Printer Configuration</title>
+
+	<para>
+	<indexterm><primary>CUPS</primary></indexterm>
+	The configuration for Samba-3 to enable CUPS raw-print-through printing has already been
+	taken care of in the &smb.conf; file. The only preparation needed for <constant>smart</constant>
+	printing to be possible involves creation of the directories in which Samba-3 stores
+	Windows printing driver files.
+	</para>
+
+	<procedure>
+	<title>Printer Configuration Steps</title>
+
+                <step><para>
+                Configure all network-attached printers to have a fixed IP address.
+                </para></step>
+
+                <step><para>
+                Create an entry in the DNS database on the server <constant>MASSIVE</constant>
+                in both the forward lookup database for the zone <constant>abmas.biz.hosts</constant>
+                and in the reverse lookup database for the network segment that the printer is to
+                be located in. Example configuration files for similar zones were presented in <link linkend="secure"/>,
+                <link linkend="abmasbiz"/> and in <link linkend="eth2zone"/>.
+                </para></step>
+
+                <step><para>
+                Follow the instructions in the printer manufacturers' manuals to permit printing
+                to port 9100.  Use any other port the manufacturer specifies for direct mode,
+                raw printing.  This allows the CUPS spooler to print using raw mode protocols.
+                <indexterm><primary>CUPS</primary></indexterm>
+                <indexterm><primary>raw printing</primary></indexterm>
+                </para></step>
+
+		<step><para>
+		<indexterm><primary>lpadmin</primary></indexterm>
+                <indexterm><primary>CUPS</primary><secondary>queue</secondary></indexterm>
+                Only on the server to which the printer is attached, configure the CUPS Print
+                Queues as follows:
+<screen>
+&rootprompt; lpadmin -p <parameter>printque</parameter>
+	 -v socket://<parameter>printer-name</parameter>.abmas.biz:9100 -E
+</screen>
+                <indexterm><primary>print filter</primary></indexterm>
+                This step creates the necessary print queue to use no assigned print filter. This
+                is ideal for raw printing, that is, printing without use of filters.
+                The name <parameter>printque</parameter> is the name you have assigned for
+                the particular printer.
+                </para></step>
+
+                <step><para>
+                Print queues may not be enabled at creation. Make certain that the queues
+                you have just created are enabled by executing the following:
+<screen>
+&rootprompt; /usr/bin/enable <parameter>printque</parameter>
+</screen>
+                </para></step>
+
+                <step><para>
+                Even though your print queue may be enabled, it is still possible that it
+                may not accept print jobs. A print queue will service incoming printing
+                requests only when configured to do so. Ensure that your print queue is
+                set to accept incoming jobs by executing the following commands:
+<screen>
+&rootprompt; /usr/bin/accept <parameter>printque</parameter>
+</screen>
+                </para></step>
+
+		<step><para>
+                <indexterm><primary>mime type</primary></indexterm>
+                <indexterm><primary>/etc/mime.convs</primary></indexterm>
+                <indexterm><primary>application/octet-stream</primary></indexterm>
+                Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
+<screen>
+application/octet-stream     application/vnd.cups-raw      0     -
+</screen>
+		</para></step>
+
+		 <step><para>
+		 <indexterm><primary>/etc/mime.types</primary></indexterm>
+		 Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
+<screen>
+application/octet-stream
+</screen>
+	        </para></step>
+
+	        <step><para>
+	        Refer to the CUPS printing manual for instructions regarding how to configure
+	        CUPS so that print queues that reside on CUPS servers on remote networks
+	        route print jobs to the print server that owns that queue. The default setting
+	        on your CUPS server may automatically discover remotely installed printers and
+	        may permit this functionality without requiring specific configuration.
+	        </para></step>
+
+		<step><para>
+		The following action creates the necessary directory subsystem. Follow these 
+		steps to printing heaven:
+<screen>
+&rootprompt; mkdir -p /var/lib/samba/drivers/{W32ALPHA,W32MIPS,W32X86,WIN40}
+&rootprompt; chown -R root:root /var/lib/samba/drivers
+&rootprompt; chmod -R ug=rwx,o=rx /var/lib/samba/drivers
+</screen>
+		</para></step>
+
+	</procedure>
+
+	</sect2>
+
+</sect1>
+
+<sect1 id="sbehap-bldg1">
+	<title>Samba-3 BDC Configuration</title>
+
+	<procedure>
+	<title>Configuration of BDC Called: <constant>BLDG1</constant></title>
+
+		<step><para>
+		Install the files in <link linkend="sbehap-bldg1-smbconf"/>,
+		<link linkend="sbehap-shareconfa"/>, and <link linkend="sbehap-shareconfb"/>
+		into the <filename>/etc/samba/</filename> directory. The three files
+		should be added together to form the &smb.conf; file.
+		</para></step>
+
+		<step><para>
+		Verify the &smb.conf; file as in step 2 of <link
+	      linkend="sbehap-massive"/>.
+		</para></step>
+
+		<step><para>
+		Carefully follow the steps outlined in <link linkend="sbehap-PAM-NSS"/>, taking
+		particular note to install the correct <filename>ldap.conf</filename>.
+		</para></step>
+
+		<step><para>
+		Verify that the NSS resolver is working. You may need to cycle the run level
+		to 1 and back to 5 before the NSS LDAP resolver functions. Follow these
+		commands:
+<screen>
+&rootprompt; init 1
+</screen>
+		After the run level has been achieved, you are prompted to provide the
+		<constant>root</constant> password. Log on, and then execute:
+<screen>
+&rootprompt; init 5
+</screen>
+		When the normal logon prompt appears, log into the system as <constant>root</constant>
+		and then execute these commands:
+<screen>
+&rootprompt; getent passwd
+root:x:0:0:root:/root:/bin/bash
+bin:x:1:1:bin:/bin:/bin/bash
+daemon:x:2:2:Daemon:/sbin:/bin/bash
+lp:x:4:7:Printing daemon:/var/spool/lpd:/bin/bash
+mail:x:8:12:Mailer daemon:/var/spool/clientmqueue:/bin/false
+...
+root:x:0:512:Netbios Domain Administrator:/root:/bin/bash
+nobody:x:999:514:nobody:/dev/null:/bin/false
+bobj:x:1000:513:System User:/home/bobj:/bin/bash
+stans:x:1001:513:System User:/home/stans:/bin/bash
+chrisr:x:1002:513:System User:/home/chrisr:/bin/bash
+maryv:x:1003:513:System User:/home/maryv:/bin/bash
+vaioboss$:x:1005:553:vaioboss$:/dev/null:/bin/false
+bldg1$:x:1006:553:bldg1$:/dev/null:/bin/false
+</screen>
+		This is the correct output. If the accounts that have UIDs above 512 are not shown, there is a problem.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>getent</primary></indexterm>
+		The next step in the verification process involves testing the operation of UNIX group
+		resolution via the NSS LDAP resolver. Execute these commands:
+<screen>
+&rootprompt; getent group
+root:x:0:
+bin:x:1:daemon
+daemon:x:2:
+sys:x:3:
+...
+Domain Admins:x:512:root
+Domain Users:x:513:bobj,stans,chrisr,maryv,jht
+Domain Guests:x:514:
+Administrators:x:544:
+Users:x:545:
+Guests:x:546:nobody
+Power Users:x:547:
+Account Operators:x:548:
+Server Operators:x:549:
+Print Operators:x:550:
+Backup Operators:x:551:
+Replicator:x:552:
+Domain Computers:x:553:
+Accounts:x:1000:
+Finances:x:1001:
+PIOps:x:1002:
+</screen>
+		This is also the correct and desired output, because it demonstrates that the LDAP client
+		is able to communicate correctly with the LDAP server (<constant>MASSIVE</constant>).
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		You must now set the LDAP administrative password into the Samba-3 <filename>secrets.tdb</filename>
+		file by executing this command:
+<screen>
+&rootprompt; smbpasswd -w not24get
+Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb
+</screen>
+		</para></step>
+
+		<step><para>
+		Now you must obtain the domain SID from the PDC and store it into the
+		<filename>secrets.tdb</filename> file also. This step is not necessary with an LDAP
+		passdb backend because Samba-3 obtains the domain SID from the 
+		sambaDomain object it automatically stores in the LDAP backend. It does not hurt to
+		add the SID to the <filename>secrets.tdb</filename>, and if you wish to do so, this 
+		command can achieve that:
+<screen>
+&rootprompt; net rpc getsid MEGANET2
+Storing SID S-1-5-21-3504140859-1010554828-2431957765 \
+                           for Domain MEGANET2 in secrets.tdb
+</screen>
+		When configuring a Samba-3 BDC that has an LDAP backend, there is no need to take
+		any special action to join it to the domain. However, winbind communicates with the
+		domain controller that is running on the localhost and must be able to authenticate,
+		thus requiring that the BDC should be joined to the domain. The process of joining
+		the domain creates the necessary authentication accounts.
+		</para></step>
+
+		<step><para>
+		To join the Samba BDC to the domain, execute the following:
+<screen>
+&rootprompt; net rpc join -U root%not24get
+Joined domain MEGANET2.
+</screen>
+		This indicates that the domain security account for the BDC has been correctly created.
+		</para></step>
+
+		<step><para>
+		<indexterm>
+			<primary>pdbedit</primary>
+		</indexterm>
+		Verify that user and group account resolution works via Samba-3 tools as follows:
+<screen>
+&rootprompt; pdbedit -L
+root:0:root
+nobody:65534:nobody
+bobj:1000:System User
+stans:1001:System User
+chrisr:1002:System User
+maryv:1003:System User
+bldg1$:1006:bldg1$
+
+&rootprompt; net groupmap list
+Domain Admins (S-1-5-21-3504140859-...-2431957765-512) ->
+                                                        Domain Admins
+Domain Users (S-1-5-21-3504140859-...-2431957765-513) -> Domain Users
+Domain Guests (S-1-5-21-3504140859-...-2431957765-514) -> 
+                                                        Domain Guests
+Administrators (S-1-5-21-3504140859-...-2431957765-544) ->
+                                                       Administrators
+...
+Accounts (S-1-5-21-3504140859-1010554828-2431957765-3001) -> Accounts
+Finances (S-1-5-21-3504140859-1010554828-2431957765-3003) -> Finances
+PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps
+</screen>
+		These results show that all things are in order.
+		</para></step>
+
+                <step><para>
+                The server you have so carefully built is now ready for another important step. Now
+                start the Samba-3 server and validate its operation. Execute the following to render all
+                the processes needed fully operative so that, upon system reboot, they are automatically
+                started:
+<screen>
+&rootprompt; chkconfig named on
+&rootprompt; chkconfig dhcpd on
+&rootprompt; chkconfig nmb on
+&rootprompt; chkconfig smb on
+&rootprompt; chkconfig winbind on
+&rootprompt; rcnmb start
+&rootprompt; rcsmb start
+&rootprompt; rcwinbind start
+</screen>
+		Samba-3 should now be running and is ready for a quick test. But not quite yet!
+                </para></step>
+
+		<step><para>
+		Your new <constant>BLDG1, BLDG2</constant> servers do not have home directories for users.
+		To rectify this using the SUSE yast2 utility or by manually editing the <filename>/etc/fstab</filename>
+		file, add a mount entry to mount the <constant>home</constant> directory that has been exported
+		from the <constant>MASSIVE</constant> server. Mount this resource before proceeding. An alternate
+		approach could be to create local home directories for users who are to use these machines.
+		This is a choice that you, as system administrator, must make. The following entry in the
+		<filename>/etc/fstab</filename> file suffices for now:
+<screen>
+massive.abmas.biz:/home  /home  nfs     rw 0 0
+</screen>
+		To mount this resource, execute:
+<screen>
+&rootprompt; mount -a
+</screen>
+		Verify that the home directory has been mounted as follows:
+<screen>
+&rootprompt; df | grep home
+massive:/home         29532988    283388  29249600   1% /home
+</screen>
+		</para></step>
+
+		<step><para>
+		Implement a quick check using one of the users that is in the LDAP database. Here you go:
+<screen>
+&rootprompt; smbclient //bldg1/bobj -Ubobj%n3v3r2l8
+smb: \> dir
+  .                    D        0  Wed Dec 17 01:16:19 2003
+  ..                   D        0  Wed Dec 17 19:04:42 2003
+  bin                  D        0  Tue Sep  2 04:00:57 2003
+  Documents            D        0  Sun Nov 30 07:28:20 2003
+  public_html          D        0  Sun Nov 30 07:28:20 2003
+  .urlview             H      311  Fri Jul  7 06:55:35 2000
+  .dvipsrc             H      208  Fri Nov 17 11:22:02 1995
+
+          57681 blocks of size 524288. 57128 blocks available
+smb: \> q
+</screen>
+		</para></step>
+
+	</procedure>
+
+	<para>
+	Now that the first BDC (<constant>BDLG1</constant>) has been configured it is time to build 
+	and configure the second BDC server (<constant>BLDG2</constant>) as follows:
+	</para>
+
+	<procedure id="sbehap-bldg2">
+	<title>Configuration of BDC Called <constant>BLDG2</constant></title>
+
+		<step><para>
+		Install the files in <link linkend="sbehap-bldg2-smbconf"/>,
+		<link linkend="sbehap-shareconfa"/>, and <link linkend="sbehap-shareconfb"/>
+		into the <filename>/etc/samba/</filename> directory. The three files
+		should be added together to form the &smb.conf; file.
+		</para></step>
+
+		<step><para>
+		Follow carefully the steps shown in <link linkend="sbehap-bldg1"/>, starting at step 2.
+		</para></step>
+
+	</procedure>
+
+<example id="sbehap-bldg1-smbconf">
+<title>LDAP Based &smb.conf; File, Server: BLDG1</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+	<smbconfoption name="unix charset">LOCALE</smbconfoption>
+	<smbconfoption name="workgroup">MEGANET2</smbconfoption>
+	<smbconfoption name="netbios name">BLDG1</smbconfoption>
+	<smbconfoption name="passdb backend">ldapsam:ldap://massive.abmas.biz</smbconfoption>
+	<smbconfoption name="enable privileges">Yes</smbconfoption>
+	<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+	<smbconfoption name="log level">1</smbconfoption>
+	<smbconfoption name="syslog">0</smbconfoption>
+	<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+	<smbconfoption name="max log size">50</smbconfoption>
+	<smbconfoption name="smb ports">139</smbconfoption>
+	<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+	<smbconfoption name="printcap name">CUPS</smbconfoption>
+	<smbconfoption name="show add printer wizard">No</smbconfoption>
+	<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+	<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
+	<smbconfoption name="logon drive">X:</smbconfoption>
+	<smbconfoption name="domain logons">Yes</smbconfoption>
+	<smbconfoption name="domain master">No</smbconfoption>
+	<smbconfoption name="wins server">172.16.0.1</smbconfoption>
+	<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
+	<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+	<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+	<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+	<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+	<smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
+	<smbconfoption name="idmap backend">ldap:ldap://massive.abmas.biz</smbconfoption>
+	<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+	<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+	<smbconfoption name="printing">cups</smbconfoption>
+	<smbconfoption name="printer admin">root, chrisr</smbconfoption>
+</smbconfblock>
+</example>
+
+
+<example id="sbehap-bldg2-smbconf">
+<title>LDAP Based &smb.conf; File, Server: BLDG2</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+	<smbconfoption name="unix charset">LOCALE</smbconfoption>
+	<smbconfoption name="workgroup">MEGANET2</smbconfoption>
+	<smbconfoption name="netbios name">BLDG2</smbconfoption>
+	<smbconfoption name="passdb backend">ldapsam:ldap://massive.abmas.biz</smbconfoption>
+	<smbconfoption name="enable privileges">Yes</smbconfoption>
+	<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+	<smbconfoption name="log level">1</smbconfoption>
+	<smbconfoption name="syslog">0</smbconfoption>
+	<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+	<smbconfoption name="max log size">50</smbconfoption>
+	<smbconfoption name="smb ports">139</smbconfoption>
+	<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+	<smbconfoption name="printcap name">CUPS</smbconfoption>
+	<smbconfoption name="show add printer wizard">No</smbconfoption>
+	<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+	<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
+	<smbconfoption name="logon drive">X:</smbconfoption>
+	<smbconfoption name="domain logons">Yes</smbconfoption>
+	<smbconfoption name="domain master">No</smbconfoption>
+	<smbconfoption name="wins server">172.16.0.1</smbconfoption>
+	<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
+	<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+	<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+	<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+	<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+	<smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
+	<smbconfoption name="idmap backend">ldap:ldap://massive.abmas.biz</smbconfoption>
+	<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+	<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+	<smbconfoption name="printing">cups</smbconfoption>
+	<smbconfoption name="printer admin">root, chrisr</smbconfoption>
+</smbconfblock>
+</example>
+
+
+<example id="sbehap-shareconfa">
+<title>LDAP Based &smb.conf; File, Shares Section &smbmdash; Part A</title>
+<smbconfblock>
+<smbconfsection name="[accounts]"/>
+	<smbconfoption name="comment">Accounting Files</smbconfoption>
+	<smbconfoption name="path">/data/accounts</smbconfoption>
+	<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[service]"/>
+	<smbconfoption name="comment">Financial Services Files</smbconfoption>
+	<smbconfoption name="path">/data/service</smbconfoption>
+	<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[pidata]"/>
+	<smbconfoption name="comment">Property Insurance Files</smbconfoption>
+	<smbconfoption name="path">/data/pidata</smbconfoption>
+	<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+	<smbconfoption name="comment">Home Directories</smbconfoption>
+	<smbconfoption name="valid users">%S</smbconfoption>
+	<smbconfoption name="read only">No</smbconfoption>
+	<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+	<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+	<smbconfoption name="path">/var/spool/samba</smbconfoption>
+	<smbconfoption name="guest ok">Yes</smbconfoption>
+	<smbconfoption name="printable">Yes</smbconfoption>
+	<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="sbehap-shareconfb">
+<title>LDAP Based &smb.conf; File, Shares Section &smbmdash; Part B</title>
+<smbconfblock>
+<smbconfsection name="[apps]"/>
+	<smbconfoption name="comment">Application Files</smbconfoption>
+	<smbconfoption name="path">/apps</smbconfoption>
+	<smbconfoption name="admin users">bjordan</smbconfoption>
+	<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+	<smbconfoption name="comment">Network Logon Service</smbconfoption>
+	<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+	<smbconfoption name="guest ok">Yes</smbconfoption>
+	<smbconfoption name="locking">No</smbconfoption>
+
+<smbconfsection name="[profiles]"/>
+	<smbconfoption name="comment">Profile Share</smbconfoption>
+	<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
+	<smbconfoption name="read only">No</smbconfoption>
+	<smbconfoption name="profile acls">Yes</smbconfoption>
+
+<smbconfsection name="[profdata]"/>
+	<smbconfoption name="comment">Profile Data Share</smbconfoption>
+	<smbconfoption name="path">/var/lib/samba/profdata</smbconfoption>
+	<smbconfoption name="read only">No</smbconfoption>
+	<smbconfoption name="profile acls">Yes</smbconfoption>
+
+<smbconfsection name="[print$]"/>
+	<smbconfoption name="comment">Printer Drivers</smbconfoption>
+	<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
+	<smbconfoption name="browseable">yes</smbconfoption>
+	<smbconfoption name="guest ok">no</smbconfoption>
+	<smbconfoption name="read only">yes</smbconfoption>
+	<smbconfoption name="write list">root, chrisr</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="sbehap-ldifadd">
+<title>LDIF IDMAP Add-On Load File &smbmdash; File: /etc/openldap/idmap.LDIF</title>
+<screen>
+dn: ou=Idmap,dc=abmas,dc=biz
+objectClass: organizationalUnit
+ou: idmap
+structuralObjectClass: organizationalUnit
+</screen>
+</example>
+
+</sect1>
+
+<sect1>
+	<title>Miscellaneous Server Preparation Tasks</title>
+
+	<para>
+	My father would say, <quote>Dinner is not over until the dishes have been done.</quote>
+	The makings of a great network environment take a lot of effort and attention to detail.
+	So far, you have completed most of the complex (and to many administrators, the interesting
+	part of server configuration) steps, but remember to tie it all together. Here are
+	a few more steps that must be completed so that your network runs like a well-rehearsed
+	orchestra.
+	</para>
+
+	<sect2>
+	<title>Configuring Directory Share Point Roots</title>
+
+	<para>
+	In your &smb.conf; file, you have specified Windows shares. Each has a <parameter>path</parameter>
+	parameter. Even though it is obvious to all, one of the common Samba networking problems is
+	caused by forgetting to verify that every such share root directory actually exists and that it
+	has the necessary permissions and ownership.
+	</para>
+
+	<para>
+	Here is an example, but remember to create the directory needed for every share:
+<screen>
+&rootprompt; mkdir -p /data/{accounts,finsvcs,piops}
+&rootprompt; mkdir -p /apps
+&rootprompt; chown -R root:root /data
+&rootprompt; chown -R root:root /apps
+&rootprompt; chown -R bobj:Accounts /data/accounts
+&rootprompt; chown -R bobj:Finances /data/finsvcs
+&rootprompt; chown -R bobj:PIOps /data/piops
+&rootprompt; chmod -R ug+rwxs,o-rwx /data
+&rootprompt; chmod -R ug+rwx,o+rx-w /apps
+</screen>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Configuring Profile Directories</title>
+
+	<para>
+	You made a conscious decision to do everything it would take to improve network client
+	performance. One of your decisions was to implement folder redirection. This means that Windows
+	user desktop profiles are now made up of two components: a dynamically loaded part and a set of file
+	network folders.
+	</para>
+
+	<para>
+	For this arrangement to work, every user needs a directory structure for the network folder
+	portion of his or her profile as shown here:
+<screen>
+&rootprompt; mkdir -p /var/lib/samba/profdata
+&rootprompt; chown root:root /var/lib/samba/profdata
+&rootprompt; chmod 755 /var/lib/samba/profdata
+
+# Per user structure
+&rootprompt; cd /var/lib/samba/profdata
+&rootprompt; mkdir -p <emphasis>username</emphasis>
+&rootprompt; for i in InternetFiles Cookies History AppData \
+                      LocalSettings MyPictures MyDocuments Recent
+&rootprompt; do
+&rootprompt; mkdir <emphasis>username</emphasis>/$i
+&rootprompt; done
+&rootprompt; chown -R <emphasis>username</emphasis>:Domain\ Users <emphasis>username</emphasis>
+&rootprompt; chmod -R 750 <emphasis>username</emphasis>
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>roaming profile</primary></indexterm>
+	<indexterm><primary>mandatory profile</primary></indexterm>
+	You have three options insofar as the dynamically loaded portion of the roaming profile
+	is concerned: 
+	</para>
+
+	<itemizedlist>
+		<listitem><para>You may permit the user to obtain a default profile.</para></listitem>
+		<listitem><para>You can create a mandatory profile.</para></listitem>
+		<listitem><para>You can create a group profile (which is almost always a mandatory profile).</para></listitem>
+	</itemizedlist>
+
+	<para>
+	Mandatory profiles cannot be overwritten by a user. The change from a user profile to a mandatory
+	profile is effected by renaming the <filename>NTUSER.DAT</filename> to <filename>NTUSER.MAN</filename>,
+	that is, just by changing the filename extension.
+	</para>
+
+	<para>
+	<indexterm><primary>SRVTOOLS.EXE</primary></indexterm>
+	<indexterm><primary>Domain User Manager</primary></indexterm>
+	The location of the profile that a user can obtain is set in the user's account in the LDAP passdb backend.
+	You can manage this using the Idealx smbldap-tools or using the 
+	<ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">Windows NT4 Domain User Manager</ulink>.
+	</para>
+
+	<para>
+	It may not be obvious that you must ensure that the root directory for the user's profile exists
+	and has the needed permissions. Use the following commands to create this directory:
+<screen>
+&rootprompt; mkdir -p /var/lib/samba/profiles/<emphasis>username</emphasis>
+&rootprompt; chown <emphasis>username</emphasis>:Domain\ Users
+	    /var/lib/samba/profiles/<emphasis>username</emphasis>
+&rootprompt; chmod 700  /var/lib/samba/profiles/<emphasis>username</emphasis>
+</screen>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Preparation of Logon Scripts</title>
+
+	<para>
+	<indexterm><primary>logon script</primary></indexterm>
+	The use of a logon script with Windows XP Professional is an option that every site should consider.
+	Unless you have locked down the desktop so the user cannot change anything, there is risk that
+	a vital network drive setting may be broken or that printer connections may be lost. Logon scripts
+	can help to restore persistent network folder (drive) and printer connections in a predictable
+	manner. One situation in which such breakage may occur in particular is when a mobile PC (notebook)
+	user attaches to another company's network that forces environment changes that are alien to your
+	network.
+	</para>
+
+	<para>
+	If you decide to use network logon scripts, by reference to the &smb.conf; files for the domain
+	controllers, you see that the path to the share point for the <constant>NETLOGON</constant>
+	share defined is <filename>/var/lib/samba/netlogon</filename>. The path defined for the logon
+	script inside that share is <filename>scripts\logon.bat</filename>. This means that as a Windows
+	NT/200x/XP client logs onto the network, it tries to obtain the file <filename>logon.bat</filename>
+	from the fully qualified path <filename>/var/lib/samba/netlogon/scripts</filename>. This fully
+	qualified path should therefore exist whether you install the <filename>logon.bat</filename>.
+	</para>
+
+	<para>
+	You can, of course, create the fully qualified path by executing:
+<screen>
+&rootprompt; mkdir -p /var/lib/samba/netlogon/scripts
+</screen>
+	</para>
+
+	<para>
+	You should research the options for logon script implementation by referring to <emphasis>TOSHARG2</emphasis>, Chapter 24,
+	Section 24.4. A quick Web search will bring up a host of options. One of the most popular logon
+	facilities in use today is called <ulink url="http://www.kixtart.org">KiXtart</ulink>.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Assigning User Rights and Privileges</title>
+
+	<para>
+	The ability to perform tasks such as joining Windows clients to the domain can be assigned to
+	normal user accounts. By default, only the domain administrator account (<constant>root</constant> on UNIX
+	systems because it has UID=0) can add accounts. New to Samba 3.0.11 is the ability to grant
+	this privilege in a very limited fashion to particular accounts.
+	</para>
+
+	<para>
+	By default, even Samba-3.0.11 does not grant any rights even to the <constant>Domain Admins</constant>
+	group. Here we grant this group all privileges.
+	</para>
+
+	<para>
+	Samba limits privileges on a per-server basis. This is a deliberate limitation so that users who
+	are granted rights can be restricted to particular machines. It is left to the network administrator
+	to determine which rights should be provided and to whom.
+	</para>
+
+	<procedure>
+	<title>Steps for Assignment of User Rights and Privileges</title>
+
+		<step><para>
+		Log onto the PDC as the <constant>root</constant> account.
+		</para></step>
+
+		<step><para>
+		Execute the following command to grant the <constant>Domain Admins</constant> group all
+		rights and privileges:
+<screen>
+&rootprompt; net -S MASSIVE  -U root%not24get rpc rights grant \
+        "MEGANET2\Domain Admins" SeMachineAccountPrivilege \
+	SePrintOperatorPrivilege SeAddUsersPrivilege \
+	SeDiskOperatorPrivilege SeRemoteShutdownPrivilege
+Successfully granted rights.
+</screen>
+		Repeat this step on each domain controller, in each case substituting the name of the server
+		(e.g., BLDG1, BLDG2) in place of the PDC called MASSIVE.
+		</para></step>
+
+		<step><para>
+		In this step the privilege will be granted to Bob Jordan (bobj) to add Windows workstations
+		to the domain. Execute the following only on the PDC. It is not necessary to do this on
+		BDCs or on DMS machines because machine accounts are only ever added by the PDC:
+<screen>
+&rootprompt; net -S MASSIVE  -U root%not24get rpc rights grant \
+             "MEGANET2\bobj" SeMachineAccountPrivilege
+Successfully granted rights.
+</screen>
+		</para></step>
+
+		<step><para>
+		Verify that privilege assignments have been correctly applied by executing:
+<screen>
+net rpc rights list accounts -Uroot%not24get
+MEGANET2\bobj
+SeMachineAccountPrivilege
+
+S-0-0
+No privileges assigned
+
+BUILTIN\Print Operators
+No privileges assigned
+
+BUILTIN\Account Operators
+No privileges assigned
+
+BUILTIN\Backup Operators
+No privileges assigned
+
+BUILTIN\Server Operators
+No privileges assigned
+
+BUILTIN\Administrators
+No privileges assigned
+
+Everyone
+No privileges assigned
+
+MEGANET2\Domain Admins
+SeMachineAccountPrivilege
+SePrintOperatorPrivilege
+SeAddUsersPrivilege
+SeRemoteShutdownPrivilege
+SeDiskOperatorPrivilege
+</screen>
+		</para></step>
+
+	</procedure>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Windows Client Configuration</title>
+
+	<para>
+	<indexterm><primary>NETLOGON</primary></indexterm>
+	In the next few sections, you can configure a new Windows XP Professional disk image on a staging
+	machine. You will configure all software, printer settings, profile and policy handling, and desktop
+	default profile settings on this system. When it is complete, you copy the contents of the
+	<filename>C:\Documents and Settings\Default User</filename> directory to a directory with the same
+	name in the <constant>NETLOGON</constant> share on the domain controllers.
+	</para>
+
+	<para>
+	Much can be learned from the Microsoft Support site regarding how best to set up shared profiles.
+	One knowledge-base article in particular stands out:
+	"<ulink url="http://support.microsoft.com/default.aspx?scid=kb;EN-US;168475">How to Create a 
+	Base Profile for All Users."</ulink>
+
+	</para>
+
+	<sect2 id="redirfold">
+	<title>Configuration of Default Profile with Folder Redirection</title>
+
+	<para>
+	<indexterm><primary>folder redirection</primary></indexterm>
+	Log onto the Windows XP Professional workstation as the local <constant>Administrator</constant>.
+	It is necessary to expose folders that are generally hidden to provide access to the
+	<constant>Default User</constant> folder.
+	</para>
+
+	<procedure>
+	<title>Expose Hidden Folders</title>
+
+		<step><para>
+		Launch the Windows Explorer by clicking
+			<menuchoice>
+                                <guimenu>Start</guimenu>
+                                <guimenuitem>My Computer</guimenuitem>
+                                <guimenuitem>Tools</guimenuitem>
+                                <guimenuitem>Folder Options</guimenuitem>
+                                <guimenuitem>View Tab</guimenuitem>
+                        </menuchoice>.
+		Select <guilabel>Show hidden files and folders</guilabel>,
+		and click <guibutton>OK</guibutton>.  Exit Windows Explorer.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>regedt32</primary></indexterm>
+		Launch the Registry Editor. Click 
+		<menuchoice>
+			<guimenu>Start</guimenu>
+			<guimenuitem>Run</guimenuitem>
+		</menuchoice>. Key in <command>regedt32</command>, and click
+		<guibutton>OK</guibutton>.
+		</para></step>
+
+	</procedure>
+
+	<para>
+	</para>
+
+	<procedure id="sbehap-rdrfldr">
+	<title>Redirect Folders in Default System User Profile</title>
+
+		<step><para>
+		<indexterm><primary>HKEY_LOCAL_MACHINE</primary></indexterm>
+		<indexterm><primary>Default User</primary></indexterm>
+		Give focus to <constant>HKEY_LOCAL_MACHINE</constant> hive entry in the left panel.
+		Click <menuchoice>
+			<guimenu>File</guimenu>
+			<guimenuitem>Load Hive...</guimenuitem>
+			<guimenuitem>Documents and Settings</guimenuitem>
+			<guimenuitem>Default User</guimenuitem>
+			<guimenuitem>NTUSER</guimenuitem>
+			<guimenuitem>Open</guimenuitem>
+		      </menuchoice>. In the dialog box that opens, enter the key name
+		<constant>Default</constant> and click <guibutton>OK</guibutton>.
+		</para></step>
+
+		<step><para>
+		Browse inside the newly loaded Default folder to:
+<screen>
+HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\
+                     CurrentVersion\Explorer\User Shell Folders\
+</screen>
+		The right panel reveals the contents as shown in <link linkend="XP-screen001"/>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>%USERPROFILE%</primary></indexterm>
+		<indexterm><primary>%LOGONSERVER%</primary></indexterm>
+		You edit hive keys. Acceptable values to replace the 
+		<constant>%USERPROFILE%</constant> variable includes:
+
+		<itemizedlist>
+			<listitem><para>A drive letter such as <constant>U:</constant></para></listitem>
+			<listitem><para>A direct network path such as
+				<constant>\\MASSIVE\profdata</constant></para></listitem>
+			<listitem><para>A network redirection (UNC name) that contains a macro such as </para>
+				<para><constant>%LOGONSERVER%\profdata\</constant></para></listitem>
+		</itemizedlist>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>registry keys</primary></indexterm>
+		Set the registry keys as shown in <link linkend="proffold"/>. Your implementation makes the assumption
+		that users have statically located machines. Notebook computers (mobile users) need to be
+		accommodated using local profiles. This is not an uncommon assumption.
+		</para></step>
+
+		<step><para>
+		Click back to the root of the loaded hive <constant>Default</constant>.
+		Click <menuchoice><guimenu>File</guimenu><guimenuitem>Unload Hive...</guimenuitem>
+		<guimenuitem>Yes</guimenuitem></menuchoice>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Registry Editor</primary></indexterm>
+		Click <menuchoice><guimenu>File</guimenu><guimenuitem>Exit</guimenuitem></menuchoice>. This exits the
+		Registry Editor.
+		</para></step>
+
+		<step><para>
+		Now follow the procedure given in <link linkend="sbehap-locgrppol"/>. Make sure that each folder you
+		have redirected is in the exclusion list.
+		</para></step>
+
+		<step><para>
+		You are now ready to copy<footnote><para>
+			There is an alternate method by which a default user profile can be added to the
+			<constant>NETLOGON</constant> share. This facility in the Windows System tool 
+			permits profiles to be exported. The export target may be a particular user or 
+			group profile share point or else the <constant>NETLOGON</constant> share. 
+			In this case, the profile directory must be named <constant>Default User</constant>.
+			</para></footnote> 
+		the Default User profile to the Samba domain controllers. Launch Microsoft Windows Explorer,
+		and use it to copy the full contents of the directory <filename>Default User</filename> that
+		is in the <filename>C:\Documents and Settings</filename> to the root directory of the
+		<constant>NETLOGON</constant> share. If the <constant>NETLOGON</constant> share has the defined
+		UNIX path of <filename>/var/lib/samba/netlogon</filename>, when the copy is complete there must
+		be a directory in there called <filename>Default User</filename>.
+		</para></step>
+
+	</procedure>
+
+	<para>
+	Before punching out new desktop images for the client workstations, it is perhaps a good idea that
+	desktop behavior should be returned to the original Microsoft settings. The following steps achieve
+	that ojective:
+	</para>
+
+	<procedure>
+	<title>Reset Folder Display to Original Behavior</title>
+
+		<step><para>
+		To launch the Windows Explorer, click
+			<menuchoice>
+                                <guimenu>Start</guimenu>
+                                <guimenuitem>My Computer</guimenuitem>
+                                <guimenuitem>Tools</guimenuitem>
+                                <guimenuitem>Folder Options</guimenuitem>
+                                <guimenuitem>View Tab</guimenuitem>
+                        </menuchoice>.
+		Deselect <guilabel>Show hidden files and folders</guilabel>, and click <guibutton>OK</guibutton>.
+		Exit Windows Explorer.
+		</para></step>
+
+	</procedure>
+
+	<figure id="XP-screen001">
+		<title>Windows XP Professional &smbmdash; User Shared Folders</title>
+		<imagefile scale="65">XP-screen001</imagefile>
+	</figure>
+
+<table id="proffold">
+	<title>Default Profile Redirections</title>
+	<tgroup cols="2">
+		<colspec align="left"/>
+		<colspec align="left"/>
+		<thead>
+			<row>
+				<entry>Registry Key</entry>
+				<entry>Redirected Value</entry>
+			</row>
+		</thead>
+		<tbody>
+			<row>
+				<entry>Cache</entry>
+				<entry>%LOGONSERVER%\profdata\%USERNAME%\InternetFiles</entry>
+			</row>
+			<row>
+				<entry>Cookies</entry>
+				<entry>%LOGONSERVER%\profdata\%USERNAME%\Cookies</entry>
+			</row>
+			<row>
+				<entry>History</entry>
+				<entry>%LOGONSERVER%\profdata\%USERNAME%\History</entry>
+			</row>
+			<row>
+				<entry>Local AppData</entry>
+				<entry>%LOGONSERVER%\profdata\%USERNAME%\AppData</entry>
+			</row>
+			<row>
+				<entry>Local Settings</entry>
+				<entry>%LOGONSERVER%\profdata\%USERNAME%\LocalSettings</entry>
+			</row>
+			<row>
+				<entry>My Pictures</entry>
+				<entry>%LOGONSERVER%\profdata\%USERNAME%\MyPictures</entry>
+			</row>
+			<row>
+				<entry>Personal</entry>
+				<entry>%LOGONSERVER%\profdata\%USERNAME%\MyDocuments</entry>
+			</row>
+			<row>
+				<entry>Recent</entry>
+				<entry>%LOGONSERVER%\profdata\%USERNAME%\Recent</entry>
+			</row>
+		</tbody>
+	</tgroup>
+</table>
+
+	</sect2>
+
+	<sect2>
+	<title>Configuration of MS Outlook to Relocate PST File</title>
+
+	<para>
+	<indexterm><primary>Outlook</primary><secondary>PST</secondary></indexterm>
+	<indexterm><primary>MS Outlook</primary><secondary>PST</secondary></indexterm>
+	Microsoft Outlook can store a Personal Storage file, generally known as a PST file.
+	It is the nature of email storage that this file grows, at times quite rapidly.
+	So that users' email is available to them at every workstation they may log onto,
+	it is common practice in well-controlled sites to redirect the PST folder to the
+	users' home directory. Follow these steps for each user who wishes to do this.
+	</para>
+
+	<para>
+	To redirect the Outlook PST file in Outlook 2003 (older versions of Outlook behave
+	slightly differently), follow these steps:
+	</para>
+
+	<procedure>
+	<title>Outlook PST File Relocation</title>
+
+		<step><para>
+		Close Outlook if it is open.
+		</para></step>
+
+		<step><para>
+		From the <guimenu>Control Panel</guimenu>, launch the Mail icon.
+		</para></step>
+
+		<step><para>
+		Click <guimenu>Email Accounts.</guimenu>
+		</para></step>
+
+		<step><para>
+		Make a note of the location of the PST file(s). From this location, move
+		the files to the desired new target location. The most desired new target location 
+		may well be the users' home directory.
+		</para></step>
+
+		<step><para>
+		Add a new data file, selecting the PST file in the new desired target location.
+		Give this entry (not the filename) a new name such as <quote>Personal Mail Folders.</quote>
+		</para>
+
+		<para>
+		Note: If MS Outlook has been configured to use an IMAP account configuration there may be problems
+		following these instructions. Feedback from users suggests that where IMAP is used the PST
+		file is used to store rules and filters. When the PST store is relocated it appears to break
+		MS Outlook's Send/Receive button. If anyone has sucessfully relocated PST files where IMAP is 
+		used please email <literal>jht@samba.org</literal> with useful tips and suggestions so that
+		this warning can be removed or modified.
+		</para></step>
+
+		<step><para>
+		Close the <guimenu>Date Files</guimenu> windows, then click <guimenu>Email Accounts</guimenu>.
+		</para></step>
+
+		<step><para>
+		Select <guimenu>View of Change</guimenu> exiting email accounts, click <guibutton>Next.</guibutton>
+		</para></step>
+
+		<step><para>
+		Change the <guimenu>Mail Delivery Location</guimenu> so as to use the data file in the new
+		target location.
+		</para></step>
+
+		<step><para>
+		Go back to the <guimenu>Data Files</guimenu> window, then delete the old data file entry.
+		</para></step>
+
+	</procedure>
+	
+	<note><para>
+	<indexterm><primary>Outlook Address Book</primary></indexterm>
+	You may have to remove and reinstall the Outlook Address Book (Contacts) entries, otherwise 
+	the user may be not be able to retrieve contacts when addressing a new email message.
+	</para></note>
+
+	<note><para>
+	<indexterm><primary>Outlook Express</primary></indexterm>
+	Outlook Express is not at all like MS OutLook. It stores file very differently also. Outlook
+	Express storage files can not be redirected to network shares. The options panel will not permit
+	this, but they can be moved to folders outside of the user's profile. They can also be excluded
+	from folder synchronization as part of the roaming profile.
+	</para>
+
+	<para>
+	While it is possible to redirect the data stores for Outlook Express data stores by editing the 
+	registry, experience has shown that data corruption and loss of email messages will result.
+	</para>
+
+	<para>
+	<indexterm><primary>Outlook Express</primary></indexterm>
+	<indexterm><primary>MS Outlook</primary></indexterm>
+	In the same vane as MS Outlook, Outlook Express data stores can become very large. When used with
+	roaming profiles this can result in excruciatingly long login and logout behavior will files are
+	synchronized. For this reason, it is highly recommended not to use Outlook Express where roaming
+	profiles are used.
+	</para></note>
+
+	<para>
+	<indexterm><primary>PST file</primary></indexterm>
+	Microsoft does not support storing PST files on network shares, although the practice does appear
+	to be rather popular. Anyone who does relocation the PST file to a network resource should refer
+	the Microsoft <ulink url="http://support.microsoft.com/kb/297019/">reference</ulink> to better
+	understand the issues.
+	</para>
+
+	<para>
+	<indexterm><primary>PST file</primary></indexterm>
+	Apart from manually moving PST files to a network share, it is possible to set the default PST
+	location for new accounts by following the instructions at the WindowsITPro <ulink
+	url="http://www.windowsitpro.com/Windows/Article/ArticleID/48228/48228.html">web</ulink> site.
+	</para>
+
+	<para>
+	<indexterm><primary>PST file</primary></indexterm>
+	User feedback suggests that disabling of oplocks on PST files will significantly improve
+	network performance by reducing locking overheads. One way this can be done is to add to the
+	&smb.conf; file stanza for the share the PST file the following:
+<screen>
+veto oplock files = /*.pdf/*.PST/
+</screen>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Configure Delete Cached Profiles on Logout</title>
+
+	<para>
+	Configure the Windows XP Professional client to auto-delete roaming profiles on logout:
+	</para>
+
+	<para>
+	<indexterm><primary>MMC</primary></indexterm>
+	Click 
+	<menuchoice>
+		<guimenu>Start</guimenu>
+		<guimenuitem>Run</guimenuitem>
+	</menuchoice>. In the dialog box, enter <command>MMC</command> and click <guibutton>OK</guibutton>.
+	</para>
+
+	<para>
+	Follow these steps to set the default behavior of the staging machine so that all roaming
+	profiles are deleted as network users log out of the system. Click
+	<menuchoice>
+		<guimenu>File</guimenu>
+		<guimenuitem>Add/Remove Snap-in</guimenuitem>
+		<guimenuitem>Add</guimenuitem>
+		<guimenuitem>Group Policy</guimenuitem>
+		<guimenuitem>Add</guimenuitem>
+		<guimenuitem>Finish</guimenuitem>
+		<guimenuitem>Close</guimenuitem>
+		<guimenuitem>OK</guimenuitem>
+	</menuchoice>. 
+	</para>
+
+	<para>
+	<indexterm><primary>Microsoft Management Console</primary><see>MMC</see></indexterm>
+	The Microsoft Management Console now shows the <guimenu>Group Policy</guimenu>
+	utility that enables you to set the policies needed. In the left panel, click
+	<menuchoice>
+		<guimenuitem>Local Computer Policy</guimenuitem>
+		<guimenuitem>Administrative Templates</guimenuitem>
+		<guimenuitem>System</guimenuitem>
+		<guimenuitem>User Profiles</guimenuitem>
+	</menuchoice>. In the right panel, set the properties shown here by double-clicking on each
+	item as shown:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>Do not check for user ownership of Roaming Profile Folders = Enabled</para></listitem>
+		<listitem><para>Delete cached copies of roaming profiles = Enabled</para></listitem>
+	</itemizedlist>
+
+	<para>
+	Close the Microsoft Management Console. The settings take immediate effect and persist onto all image copies
+	made of this system to deploy the new standard desktop system.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Uploading Printer Drivers to Samba Servers</title>
+
+	<para>
+	<indexterm><primary>printing</primary><secondary>drag-and-drop</secondary></indexterm>
+	Users want to be able to use network printers. You have a vested interest in making
+	it easy for them to print. You have chosen to install the printer drivers onto the Samba
+	servers and to enable point-and-click (drag-and-drop) printing. This process results in
+	Samba being able to automatically provide the Windows client with the driver necessary to
+	print to the printer chosen. The following procedure must be followed for every network
+	printer:
+	</para>
+
+	<procedure>
+	<title>Steps to Install Printer Drivers on the Samba Servers</title>
+
+		<step><para>
+		Join your Windows XP Professional workstation (the staging machine) to the 
+		<constant>MEGANET2</constant> domain. If you are not sure of the procedure, 
+		follow the guidance given in <link linkend="appendix"/>, <link linkend="domjoin"/>.
+		</para></step>
+
+		<step><para>
+		After the machine has rebooted, log onto the workstation as the domain
+		<constant>root</constant> (this is the Administrator account for the 
+		operating system that is the host platform for this implementation of Samba.
+		</para></step>
+
+		<step><para>
+		Launch MS Windows Explorer. Navigate in the left panel. Click
+		<menuchoice>
+			<guimenu>My Network Places</guimenu>
+			<guimenuitem>Entire Network</guimenuitem>
+			<guimenuitem>Microsoft Windows Network</guimenuitem>
+			<guimenuitem>Meganet2</guimenuitem>
+			<guimenuitem>Massive</guimenuitem>
+		</menuchoice>. Click on <guimenu>Massive</guimenu>
+			<guimenu>Printers and Faxes</guimenu>.
+		</para></step>
+
+		<step><para>
+		Identify a printer that is shown in the right panel. Let us assume the printer is called 
+		<constant>ps01-color</constant>. Right-click on the <guimenu>ps01-color</guimenu> icon
+		and select the <guimenu>Properties</guimenu> entry. This opens a dialog box that indicates
+		that <quote>The printer driver is not installed on this computer. Some printer properties
+		will not be accessible unless you install the printer driver. Do you want to install the
+		driver now?</quote> It is important at this point you answer <guimenu>No</guimenu>.
+		</para></step>
+
+		<step><para>
+		The printer properties panel for the <guimenu>ps01-color</guimenu> printer on the server 
+		<constant>MASSIVE</constant> is displayed. Click the <guimenu>Advanced</guimenu> tab.
+		Note that the box labeled <guimenu>Driver</guimenu> is empty. Click the <guimenu>New Driver</guimenu>
+		button that is next to the <guimenu>Driver</guimenu> box. This launches the <quote>Add Printer Wizard</quote>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Add Printer Wizard</primary><secondary>APW</secondary></indexterm>
+		<indexterm><primary>APW</primary></indexterm>
+		The <quote>Add Printer Driver Wizard on <constant>MASSIVE</constant></quote> panel 
+		is now presented. Click <guimenu>Next</guimenu> to continue. From the left panel, select the 
+		printer manufacturer. In your case, you are adding a driver for a printer manufactured by 
+		Lexmark. In the right panel, select the printer (Lexmark Optra Color 40 PS). Click 
+		<guimenu>Next</guimenu>, and then <guimenu>Finish</guimenu> to commence driver upload. A 
+		progress bar appears and instructs you as each file is being uploaded and that it is being 
+		directed at the network server <constant>\\massive\ps01-color</constant>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>printers</primary><secondary>Advanced</secondary></indexterm>
+		<indexterm><primary>printers</primary><secondary>Properties</secondary></indexterm>
+		<indexterm><primary>printers</primary><secondary>Sharing</secondary></indexterm>
+		<indexterm><primary>printers</primary><secondary>General</secondary></indexterm>
+		<indexterm><primary>printers</primary><secondary>Security</secondary></indexterm>
+		<indexterm><primary>AD printer publishing</primary></indexterm>
+		The driver upload completes in anywhere from a few seconds to a few minutes. When it completes,
+		you are returned to the <guimenu>Advanced</guimenu> tab in the <guimenu>Properties</guimenu> panel. 
+		You can set the Location (under the <guimenu>General</guimenu> tab) and Security settings (under 
+		the <guimenu>Security</guimenu> tab). Under the <guimenu>Sharing</guimenu> tab it is possible to
+		load additional printer drivers; there is also a check-box in this tab called <quote>List in the
+		directory</quote>. When this box is checked, the printer will be published in Active Directory
+		(Applicable to Active Directory use only.)
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>printers</primary><secondary>Default Settings</secondary></indexterm>
+		Click <guimenu>OK</guimenu>. It will take a minute or so to upload the settings to the server. 
+		You are now returned to the <guimenu>Printers and Faxes on Massive</guimenu> monitor.
+		Right-click on the printer, click <menuchoice><guimenu>Properties</guimenu> 
+		<guimenuitem>Device Settings</guimenuitem> </menuchoice>.  Now change the settings to suit 
+		your requirements. BE CERTAIN TO CHANGE AT LEAST ONE SETTING and apply the changes even if 
+		you need to reverse the changes back to their original settings. 
+		</para></step>
+
+		<step><para>
+		This is necessary so that the printer settings are initialized in the Samba printers
+		database. Click <guimenu>Apply</guimenu> to commit your settings. Revert any settings you changed
+		just to initialize the Samba printers database entry for this printer. If you need to revert a setting,
+		click <guimenu>Apply</guimenu> again.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Print Test Page</primary></indexterm>
+		Verify that all printer settings are at the desired configuration. When you are satisfied that they are,
+		click the <guimenu>General</guimenu> tab. Now click the <guimenu>Print Test Page</guimenu> button.
+		A test page should print. Verify that it has printed correctly. Then click <guimenu>OK</guimenu>
+		in the panel that is newly presented. Click <guimenu>OK</guimenu> on the <guimenu>ps01-color on 
+		massive Properties</guimenu> panel.
+		</para></step>
+
+		<step><para>
+		You must repeat this process for all network printers (i.e., for every printer on each server).
+		When you have finished uploading drivers to all printers, close all applications. The next task
+		is to install software your users require to do their work.
+		</para></step>
+
+	</procedure>
+
+	</sect2>
+
+	<sect2>
+	<title>Software Installation</title>
+
+	<para>
+	Your network has both fixed desktop workstations as well as notebook computers. As a general rule, it is
+	a good idea to not tamper with the operating system that is provided by the notebook computer manufacturer.
+	Notebooks require special handling that is beyond the scope of this chapter.
+	</para>
+
+	<para>
+	For desktop systems, the installation of software onto administratively centralized application servers
+	make a lot of sense. This means that you can manage software maintenance from a central
+	perspective and that only minimal application stubware needs to be installed onto the desktop
+	systems. You should proceed with software installation and default configuration as far as is humanly
+	possible and so long as it makes sense to do so. Make certain to thoroughly test and validate every aspect
+	of software operations and configuration.
+	</para>
+
+	<para>
+	When you believe that the overall configuration is complete, be sure to create a shared group profile
+	and migrate that to the Samba server for later reuse when creating custom mandatory profiles, just in
+	case a user may have specific needs you had not anticipated.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Roll-out Image Creation</title>
+
+	<para>
+	The final steps before preparing the distribution Norton Ghost image file you might follow are:
+	</para>
+
+	<blockquote><para>
+	Unjoin the domain &smbmdash; Each workstation requires a unique name and must be independently
+	joined into domain membership.
+	</para></blockquote>
+
+	<blockquote><para>
+	Defragment the hard disk &smbmdash; While not obvious to the uninitiated, defragmentation results
+	in better performance and often significantly reduces the size of the compressed disk image. That
+	also means it will take less time to deploy the image onto 500 workstations.
+	</para></blockquote>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Key Points Learned</title>
+
+	<para>
+	This chapter introduced many new concepts. Is it a sad fact that the example presented deliberately
+	avoided any consideration of security. Security does not just happen; you must design it into your total
+	network. Security begins with a systems design and implementation that anticipates hostile behavior from
+	users both inside and outside the organization. Hostile and malicious intruders do not respect barriers;
+	they accept them as challenges. For that reason, if not simply from a desire to establish safe networking
+	practices, you must not deploy the design presented in this book in an environment where there is risk
+	of compromise.
+	</para>
+
+	<para>
+	<indexterm><primary>Access Control Lists</primary><see>ACLs</see></indexterm>
+	<indexterm><primary>ACLs</primary></indexterm>
+	As a minimum, the LDAP server must be protected by way of Access Control Lists (ACLs), and it must be
+	configured to use secure protocols for all communications over the network. Of course, secure networking
+	does not result just from systems design and implementation but involves constant user education
+	training and, above all, disciplined attention to detail and constant searching for signs of unfriendly
+	or alien activities. Security is itself a topic for a whole book. Please do consult appropriate sources.
+	Jerry Carter's book <ulink url="http://www.booksense.com/product/info.jsp&amp;isbn=1565924916">
+	<emphasis>LDAP System Administration</emphasis></ulink> is a good place to start reading about OpenLDAP
+	as well as security considerations.
+	</para>
+
+	<para>
+	The substance of this chapter that has been deserving of particular attention includes:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Implementation of an OpenLDAP-based passwd backend, necessary to support distributed
+		domain control.
+		</para></listitem>
+
+		<listitem><para>
+		Implementation of Samba primary and secondary domain controllers with a common LDAP backend
+		for user and group accounts that is shared with the UNIX system through the PADL nss_ldap and
+		pam_ldap tool-sets.
+		</para></listitem>
+
+		<listitem><para>
+		Use of the Idealx smbldap-tools scripts for UNIX (POSIX) account management as well as
+		to manage Samba Windows user and group accounts.
+		</para></listitem>
+
+		<listitem><para>
+		The basics of implementation of Group Policy controls for Windows network clients.
+		</para></listitem>
+
+		<listitem><para>
+		Control over roaming profiles, with particular focus on folder redirection to network drives.
+		</para></listitem>
+
+		<listitem><para>
+		Use of the CUPS printing system together with Samba-based printer driver auto-download.
+		</para></listitem>
+	</itemizedlist>
+
+</sect1>
+
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	Well, here we are at the end of this chapter and we have only ten questions to help you to
+	remember so much. There are bound to be some sticky issues here.
+	</para>
+
+	<qandaset defaultlabel="chap06qa" type="number">
+	<qandaentry>
+	<question>
+
+		<para>
+		Why did you not cover secure practices? Isn't it rather irresponsible to instruct
+		network administrators to implement insecure solutions?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Let's get this right. This is a book about Samba, not about OpenLDAP and secure
+		communication protocols for subjects other than Samba. Earlier on, you note,
+		that the dynamic DNS and DHCP solutions also used no protective secure communications
+		protocols. The reason for this is simple: There are so many ways of implementing
+		secure protocols that this book would have been even larger and more complex.
+		</para>
+
+		<para>
+		The solutions presented here all work (at least they did for me). Network administrators
+		have the interest and the need to be better trained and instructed in secure networking
+		practices and ought to implement safe systems. I made the decision, right or wrong,
+		to keep this material as simple as possible. The intent of this book is to demonstrate
+		a working solution and not to discuss too many peripheral issues.
+		</para>
+
+		<para>
+		This book makes little mention of backup techniques. Does that mean that I am recommending
+		that you should implement a network without provision for data recovery and for disaster
+		management? Back to our focus: The deployment of Samba has been clearly demonstrated.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		You have focused much on SUSE Linux and little on the market leader, Red Hat. Do
+		you have a problem with Red Hat Linux? Doesn't that make your guidance irrelevant
+		to the Linux I might be using?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Both Red Hat Linux and SUSE Linux comply with the Linux Standards Base specifications
+		for a standard Linux distribution. The differences are marginal. Surely you know
+		your Linux platform, and you do have access to administration manuals for it. This
+		book is not a Linux tutorial; it is a Samba tutorial. Let's keep the focus on
+		the Samba part of the book; all the other bits are peripheral (but important) to
+		creation of a total network solution. 
+		</para>
+
+		<para>
+		What I find interesting is the attention reviewers give to Linux installation and to
+		the look and feel of the desktop, but does that make for a great server? In this book,
+		I have paid particular attention to the details of creating a whole solution framework.
+		I have not tightened every nut and bolt, but I have touched on all the issues you
+		need to be familiar with. Over the years many people have approached me wanting to
+		know the details of exactly how to implement a DHCP and dynamic DNS server with Samba
+		and WINS. In this chapter, it is plain to see what needs to be configured to provide
+		transparent interoperability. Likewise for CUPS and Samba interoperation. These are
+		key stumbling areas for many people.
+		</para>
+
+		<para>
+		At every critical junction, I have provided comparative guidance for both SUSE and
+		Red Hat Linux. Both manufacturers have done a great job in furthering the cause
+		of open source software. I favor neither and respect both. I like particular
+		features of both products (companies also). No bias in presentation is intended.
+		Oh, before I forget, I particularly like Debian Linux; that is my favorite playground.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		You did not use SWAT to configure Samba. Is there something wrong with it?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		That is a good question. As it is, the &smb.conf; file configurations are presented
+		in as direct a format as possible. Adding SWAT into the equation would have complicated
+		matters. I sought simplicity of implementation. The fact is that I did use SWAT to
+		create the files in the first place.
+		</para>
+
+		<para>
+		There are people in the Linux and open source community who feel that SWAT is dangerous
+		and insecure. Many will not touch it with a barge-pole. By not introducing SWAT, I
+		hope to have brought their interests on board. SWAT is well covered is <emphasis>TOSHARG2</emphasis>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		You have exposed a well-used password <emphasis>not24get</emphasis>. Is that
+		not irresponsible? 
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Well, I had to use a password of some sort. At least this one has been consistently
+		used throughout. I guess you can figure out that in a real deployment it would make 
+		sense to use a more secure and original password.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		The Idealx smbldap-tools create many domain group accounts that are not used. Is that
+		a good thing?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		I took this up with Idealx and found them most willing to change that in the next version.
+		Let's give Idealx some credit for the contribution they have made. I appreciate their work
+		and, besides, it does no harm to create accounts that are not now used &smbmdash; at some time 
+		Samba may well use them.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Can I use LDAP just for Samba accounts and not for UNIX system accounts?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Yes, you can do that for user accounts only. Samba requires there to be a POSIX (UNIX)
+		group account for every Windows domain group account. But if you put your users into
+		the system password account, how do you plan to keep all domain controller system
+		password files in sync? I think that having everything in LDAP makes a lot of sense
+		for the UNIX administrator who is still learning the craft and is migrating from MS Windows.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why are the Windows domain RID portions not the same as the UNIX UID?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Samba uses a well-known public algorithm for assigning RIDs from UIDs and GIDs.
+		This algorithm ought to ensure that there will be no clashes with well-known RIDs.
+		Well-known RIDs have special significance to MS Windows clients. The automatic
+		assignment used the calculation: RID = UID x 2 + 1000. Of course, Samba does
+		permit you to override that to some extent. See the &smb.conf; man page entry
+		for <parameter>algorithmic rid base</parameter>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Printer configuration examples all show printing to the HP port 9100. Does this
+		mean that I must have HP printers for these solutions to work?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		No. You can use any type of printer and must use the interfacing protocol supported
+		by the printer. Many networks use LPR/LPD print servers to which are attached
+		PCL printers, inkjet printers, plotters, and so on. At home I use a USB-attached
+		inkjet printer. Use the appropriate device URI (Universal Resource Interface)
+		argument to the <constant>lpadmin -v</constant> option that is right for your
+		printer.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Is folder redirection dangerous? I've heard that you can lose your data that way.
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The only loss of data I know of that involved folder redirection was caused by
+		manual misuse of the redirection tool. The administrator redirected a folder to
+		a network drive and said he wanted to migrate (move) the data over. Then he 
+		changed his mind, so he moved the folder back to the roaming profile. This time,
+		he declined to move the data because he thought it was still in the local profile
+		folder. That was not the case, so by declining to move the data back, he wiped out
+		the data. You cannot hold the tool responsible for that. Caveat emptor still applies.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Is it really necessary to set a local Group Policy to exclude the redirected
+		folders from the roaming profile?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Yes. If you do not do this, the data will still be copied from the network folder
+		(share) to the local cached copy of the profile.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	</qandaset>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-ByExample/SBE-MigrateNT4Samba3.xml b/docs-xml/Samba3-ByExample/SBE-MigrateNT4Samba3.xml
new file mode 100644
index 00000000000..f7ab1d1c1c1
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-MigrateNT4Samba3.xml
@@ -0,0 +1,1787 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="ntmigration">
+  <title>Migrating NT4 Domain to Samba-3</title>
+
+	<para>
+	Ever since Microsoft announced that it was discontinuing support for Windows
+	NT4, Samba users started to ask for detailed instructions on how to migrate
+	from NT4 to Samba-3. This chapter provides background information that should
+	meet these needs.
+	</para>
+
+	<para>
+	One wonders how many NT4 systems will be left in service by the time you read this
+	book though.
+	</para>
+
+<sect1>
+	<title>Introduction</title>
+
+      <para><indexterm>
+	  <primary>migration</primary>
+	</indexterm>
+	Network administrators who want to migrate off a Windows NT4 environment know
+	one thing with certainty. They feel that NT4 has been abandoned, and they want
+	to update. The desire to get off NT4 and to not adopt Windows 200x and Active
+	Directory is driven by a mixture of concerns over complexity, cost, fear of
+	failure, and much more.
+	</para>
+
+	<para>
+	<indexterm><primary>group policies</primary></indexterm>
+	<indexterm><primary>accounts</primary><secondary>user</secondary></indexterm>
+	<indexterm><primary>accounts</primary><secondary>group</secondary></indexterm>
+	<indexterm><primary>accounts</primary><secondary>machine</secondary></indexterm>
+	The migration from NT4 to Samba-3 can involve a number of factors, including
+	migration of data to another server, migration of network environment controls
+	such as group policies, and migration of the users, groups, and machine
+	accounts.
+	</para>
+
+	<para>
+	<indexterm><primary>accounts</primary><secondary>Domain</secondary></indexterm>
+	It should be pointed out now that it is possible to migrate some systems from
+	a Windows NT4 domain environment to a Samba-3 domain environment. This is certainly
+	not possible in every case. It is possible to just migrate the domain accounts
+	to Samba-3 and then to switch machines, but as a hands-off transition, this is more
+	the exception than the rule. Most systems require some tweaking after
+	migration before an environment that is acceptable for immediate use
+	is obtained.
+	</para>
+
+	<sect2>
+	<title>Assignment Tasks</title>
+
+	<para>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>ldapsam</primary></indexterm>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	You are about to migrate an MS Windows NT4 domain accounts database to
+	a Samba-3 server. The Samba-3 server is using a 
+	<parameter>passdb backend</parameter> based on LDAP. The 
+	<constant>ldapsam</constant> is ideal because an LDAP backend can be distributed
+	for use with BDCs &smbmdash; generally essential for larger networks.
+	</para>
+
+	<para>
+	Your objective is to document the process of migrating user and group accounts
+	from several NT4 domains into a single Samba-3 LDAP backend database.
+	</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+	<title>Dissection and Discussion</title>
+
+	<para>
+	<indexterm><primary>snap-shot</primary></indexterm>
+	<indexterm><primary>NT4 registry</primary></indexterm>
+	<indexterm><primary>registry</primary><secondary>keys</secondary><tertiary>SAM</tertiary></indexterm>
+	<indexterm><primary>registry</primary><secondary>keys</secondary><tertiary>SECURITY</tertiary></indexterm>
+	<indexterm><primary>SAM</primary></indexterm>
+	<indexterm><primary>Security Account Manager</primary><see>SAM</see></indexterm>
+	The migration process takes a snapshot of information that is stored in the
+	Windows NT4 registry-based accounts database. That information resides in
+	the Security Account Manager (SAM) portion of the NT4 registry under keys called
+	<constant>SAM</constant> and <constant>SECURITY</constant>.
+	</para>
+
+	<warning><para>
+	<indexterm><primary>crippled</primary></indexterm>
+	<indexterm><primary>inoperative</primary></indexterm>
+	The Windows NT4 registry keys called <constant>SAM</constant> and <constant>SECURITY</constant>
+	are protected so that you cannot view the contents. If you change the security setting
+	to reveal the contents under these hive keys, your Windows NT4 domain is crippled. Do not
+	do this unless you are willing to render your domain controller inoperative.
+	</para></warning>
+
+	<para>
+	<indexterm><primary>migration</primary><secondary>objectives</secondary></indexterm>
+	<indexterm><primary>disruptive</primary></indexterm>
+	Before commencing an NT4 to Samba-3 migration, you should consider what your objectives are.
+	While in some cases it is possible simply to migrate an NT4 domain to a single Samba-3 server,
+	that may not be a good idea from an administration perspective. Since the process involves going
+	through a certain amount of disruptive activity anyhow, why not take this opportunity to
+	review the structure of the network, how Windows clients are controlled and how they
+	interact with the network environment.
+	</para>
+
+	<para>
+	<indexterm><primary>network</primary><secondary>logon scripts</secondary></indexterm>
+	<indexterm><primary>profiles share</primary></indexterm>
+	<indexterm><primary>security descriptors</primary></indexterm>
+	MS Windows NT4 was introduced some time around 1996. Many environments in which NT4 was deployed
+	have done little to keep the NT4 server environment up to date with more recent Windows releases, 
+	particularly Windows XP Professional. The migration provides opportunity to revise and update 
+	roaming profile deployment as well as folder redirection. Given that you must port the 
+	greater network configuration of this from the old NT4 server to the new Samba-3 server.
+	Do not forget to validate the security descriptors in the profiles share as well as network logon
+	scripts. Feedback from sites that are migrating to Samba-3 suggests that many are using this
+	as a good time to update desktop systems also. In all, the extra effort should constitute no
+	real disruption to users, but rather, with due diligence and care, should make their network experience
+	a much happier one.
+	</para>
+
+	<sect2>
+	<title>Technical Issues</title>
+
+	<para>
+	<indexterm><primary>strategic</primary></indexterm>
+	<indexterm><primary>active directory</primary></indexterm>
+	Migration of an NT4 domain user and group database to Samba-3 involves a certain strategic
+	element. Many sites have asked for instructions regarding merging of multiple NT4
+	domains into one Samba-3 LDAP database. It seems that this is viewed as a significant
+	added value compared with the alternative of migration to Windows Server 200x and Active
+	Directory. The diagram in <link linkend="ch8-migration"/> illustrates the effect of migration
+	from a Windows NT4 domain to a Samba domain.
+	</para>
+
+	<figure id="ch8-migration">
+		<title>Schematic Explaining the <command>net rpc vampire</command> Process</title>
+		<imagefile scale="55">ch8-migration</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>merge</primary></indexterm>
+	<indexterm><primary>passdb.tdb</primary></indexterm>
+	If you want to merge multiple NT4 domain account databases into one Samba domain,
+	you must now dump the contents of the first migration and edit it as appropriate. Now clean
+	out (remove) the tdbsam backend file (<filename>passdb.tdb</filename>) or the LDAP database
+	files. You must start each migration with a new database into which you merge your NT4 
+	domains.
+	</para>
+
+	<para><indexterm>
+	<primary>dump</primary>
+	</indexterm>
+	At this point, you are ready to perform the second migration, following the same steps as
+	for the first. In other words, dump the database, edit it, and then you may merge the
+	dump for the first and second migrations.
+	</para>
+
+	<para><indexterm>
+	<primary>LDAP</primary>
+	</indexterm><indexterm>
+	<primary>migrate</primary>
+	</indexterm><indexterm>
+	<primary>Domain SID</primary>
+	</indexterm>
+	You must be careful. If you choose to migrate to an LDAP backend, your dump file
+	now contains the full account information, including the domain SID. The domain SID for each 
+	of the two NT4 domains will be different. You must choose one and change the domain 
+	portion of the account SIDs so that all are the same.
+	</para>
+
+	<para>
+	<indexterm><primary>passdb.tdb</primary></indexterm>
+	<indexterm><primary>/etc/passwd</primary></indexterm>
+	<indexterm><primary>merged</primary></indexterm>
+	<indexterm><primary>logon script</primary></indexterm>
+	<indexterm><primary>logon hours</primary></indexterm>
+	<indexterm><primary>logon machines</primary></indexterm>
+	<indexterm><primary>profile path</primary></indexterm>
+	<indexterm><primary>smbpasswd</primary></indexterm>
+	<indexterm><primary>tdbsam</primary></indexterm>
+	<indexterm><primary>LDAP backend</primary></indexterm>
+	<indexterm><primary>export</primary></indexterm>
+	<indexterm><primary>import</primary></indexterm>
+	If you choose to use a tdbsam (<filename>passdb.tdb</filename>) backend file, your best choice
+	is to use <command>pdbedit</command> to export the contents of the tdbsam file into an
+	smbpasswd data file. This automatically strips out all domain-specific information,
+	such as logon hours, logon machines, logon script, profile path, as well as the domain SID.
+	The resulting file can be easily merged with other migration attempts (each of which must start
+	with a clean file). It should also be noted that all users who end up in the merged smbpasswd
+	file must have an account in <filename>/etc/passwd</filename>. The resulting smbpasswd file
+	may be exported or imported into either a tdbsam (<filename>passdb.tdb</filename>) or
+	an LDAP backend.
+	</para>
+
+	<figure id="NT4DUM">
+		<title>View of Accounts in NT4 Domain User Manager</title>
+		<imagefile scale="50">UserMgrNT4</imagefile>
+	</figure>
+
+</sect2>
+
+
+<sect2>
+	<title>Political Issues</title>
+
+	<para>
+	The merging of multiple Windows NT4-style domains into a single LDAP-backend-based Samba-3
+	domain may be seen by those who had power over them as a loss of prestige or a loss of
+	power. The imposition of a single domain may even be seen as a threat. So in migrating and
+	merging account databases, be consciously aware of the political fall-out in which you
+	may find yourself entangled when key staff feel a loss of prestige.
+	</para>
+
+	<para>
+	The best advice that can be given to those who set out to merge NT4 domains into a single
+	Samba-3 domain is to promote (sell) the action as one that reduces costs and delivers
+	greater network interoperability and manageability.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Implementation</title>
+
+	<para>
+	From feedback on the Samba mailing lists, it seems that most Windows NT4 migrations
+	to Samba-3 are being performed using a new server or a new installation of a Linux or UNIX
+	server. If you contemplate doing this, please note that the steps that follow in this
+	chapter assume familiarity with the information that has been previously covered in this
+	book. You are particularly encouraged to be familiar with <link linkend="secure"/>,
+	<link linkend="Big500users"/> and <link linkend="happy"/>.
+	</para>
+
+	<para>
+	We present here the steps and example output for two NT4 to Samba-3 domain migrations. The
+	first uses an LDAP-based backend, and the second uses a tdbsam backend. In each case the
+	scripts you specify in the &smb.conf; file for the <parameter>add user script</parameter>
+	collection of parameters are used to effect the addition of accounts into the passdb backend.
+	</para>
+
+	<para>
+	Before proceeding to NT4 migration using either a tdbsam or ldapsam, it is most strongly recommended to
+	review <link linkend="ch5-dnshcp-setup"/> for DNS and DHCP configuration. The importance of correctly
+	functioning name resolution must be recognized. This applies equally for both hostname and NetBIOS names
+	(machine names, computer names, domain names, workgroup names &smbmdash; ALL names!).
+	</para>
+
+	<para>
+	The migration process involves the following steps:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Prepare the target Samba-3 server. This involves configuring Samba-3 for
+		migration to either a tdbsam or an ldapsam backend.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>uppercase</primary></indexterm>
+		<indexterm><primary>Posix</primary></indexterm>
+		<indexterm><primary>lower-case</primary></indexterm>
+		Clean up the source NT4 PDC. Delete all accounts that need not be migrated.
+		Delete all files that should not be migrated. Where possible, change NT group
+		names so there are no spaces or uppercase characters. This is important if
+		the target UNIX host insists on POSIX-compliant all lowercase user and group
+		names.
+		</para></listitem>
+
+		<listitem><para>
+		Step through the migration process.
+		</para></listitem>
+
+		<listitem><para><indexterm><primary>PDC</primary></indexterm>
+		Remove the NT4 PDC from the network.
+		</para></listitem>
+
+		<listitem><para>
+		Upgrade the Samba-3 server from a BDC to a PDC, and validate all account
+		information.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	It may help to use the above outline as a pre-migration checklist.
+	</para>
+
+	<sect2>
+	<title>NT4 Migration Using LDAP Backend</title>
+
+	<para>
+	In this example, the migration is of an NT4 PDC to a Samba-3 PDC with an LDAP backend. The accounts about
+	to be migrated are shown in <link linkend="NT4DUM"/>. In this example use is made of the
+	smbldap-tools scripts to add the accounts that are migrated into the ldapsam passdb backend.
+	Four scripts are essential to the migration process. Other scripts will be required
+	for daily management, but these are not critical to migration. The critical scripts are dependant
+	on which passdb backend is being used. Refer to <link linkend="ch8-vampire"/> to see which scripts
+	must be provided so that the migration process can complete.
+	</para>
+
+	<para>
+	Verify that you have correctly specified in the &smb.conf; file the scripts and arguments 
+	that should be passed to them before attempting to perform the account migration. Note also
+	that the deletion scripts must be commented out during migration. These should be uncommented
+	following successful migration of the NT4 Domain accounts.
+	</para>
+
+	<warning><para>
+	Under absolutely no circumstances should the Samba daemons be started until instructed to do so.
+	Delete the <filename>/etc/samba/secrets.tdb</filename> file and all Samba control tdb files
+	before commencing the following configuration steps.
+	</para></warning>
+
+	<table id="ch8-vampire">
+		<title>Samba &smb.conf; Scripts Essential to Samba Operation</title>
+		<tgroup cols="3">
+			<colspec align="left"/>
+			<colspec align="center"/>
+			<colspec align="center"/>
+			<thead>
+				<row>
+					<entry>Entity</entry>
+					<entry>ldapsam Script</entry>
+					<entry>tdbsam Script</entry>
+				</row>
+			</thead>
+			<tbody>
+				<row>
+					<entry>Add User Accounts</entry>
+					<entry>smbldap-useradd</entry>
+					<entry>useradd</entry>
+				</row>
+				<row>
+					<entry>Delete User Accounts</entry>
+					<entry>smbldap-userdel</entry>
+					<entry>userdel</entry>
+				</row>
+				<row>
+					<entry>Add Group Accounts</entry>
+					<entry>smbldap-groupadd</entry>
+					<entry>groupadd</entry>
+				</row>
+				<row>
+					<entry>Delete Group Accounts</entry>
+					<entry>smbldap-groupdel</entry>
+					<entry>groupdel</entry>
+				</row>
+				<row>
+					<entry>Add User to Group</entry>
+					<entry>smbldap-groupmod</entry>
+					<entry>usermod (See Note)</entry>
+				</row>
+				<row>
+					<entry>Add Machine Accounts</entry>
+					<entry>smbldap-useradd</entry>
+					<entry>useradd</entry>
+				</row>
+			</tbody>
+		</tgroup>
+	</table>
+
+	<note><para>
+	<indexterm><primary>usermod</primary></indexterm>
+	<indexterm><primary>groupmem</primary></indexterm>
+	<indexterm><primary>smbldap-tools</primary></indexterm>
+	The UNIX/Linux <command>usermod</command> utility does not permit simple user addition to (or deletion
+	of users from) groups. This is a feature provided by the smbldap-tools scripts. If you want this
+	capability, you must create your own tool to do this. Alternately, you can search the Web
+	to locate a utility called <command>groupmem</command> (by George Kraft) that provides this functionality.
+	The <command>groupmem</command> utility was contributed to the shadow package but has not surfaced
+	in the formal commands provided by Linux distributions (March 2004).
+	</para></note>
+
+	<note><para>
+	<indexterm><primary>tdbdump</primary></indexterm>
+	The <command>tdbdump</command> utility is a utility that you can build from the Samba source-code tree. Not all Linux binary distributions include this tool. If it is missing from your
+	Linux distribution, you will need to build this yourself or else forgo its use.
+	</para></note>
+
+	<para>
+	<indexterm><primary>User Manager</primary></indexterm>
+	Before starting the migration, all dead accounts were removed from the NT4 domain using the User Manager for Domains.
+	</para>
+
+	<procedure>
+	<title>User Migration Steps</title>
+
+		<step><para>
+		Configure the Samba &smb.conf; file to create a BDC. An example configuration is
+		given in <link linkend="sbent4smb"/>.
+		The delete scripts are commented out so that during the process of migration
+		no account information can be deleted.
+		</para></step>
+
+<example id="sbent4smb">
+<title>NT4 Migration Samba-3 Server <filename>smb.conf</filename> &smbmdash; Part: A</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+        <smbconfoption name="workgroup">DAMNATION</smbconfoption>
+        <smbconfoption name="netbios name">MERLIN</smbconfoption>
+        <smbconfoption name="passdb backend">ldapsam:ldap://localhost</smbconfoption>
+        <smbconfoption name="log level">1</smbconfoption>
+        <smbconfoption name="syslog">0</smbconfoption>
+        <smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+        <smbconfoption name="max log size">0</smbconfoption>
+        <smbconfoption name="smb ports">139 445</smbconfoption>
+        <smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+        <smbconfoption name="add user script">/opt/IDEALX/sbin/smbldap-useradd -m '%u'</smbconfoption>
+        <smbconfoption name="#delete user script">/opt/IDEALX/sbin/smbldap-userdel '%u'</smbconfoption>
+        <smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd '%g'</smbconfoption>
+        <smbconfoption name="#delete group script">/opt/IDEALX/sbin/smbldap-groupdel '%g'</smbconfoption>
+		<smbconfoption name="add user to group script">/opt/IDEALX/sbin/ smbldap-groupmod -m '%u' '%g'</smbconfoption>
+		<smbconfoption name="#delete user from group script">/opt/IDEALX/sbin/smbldap-groupmod -x '%u' '%g'</smbconfoption>
+		<smbconfoption name="set primary group script">/opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'</smbconfoption>
+		<smbconfoption name="add machine script">/opt/IDEALX/sbin/smbldap-useradd -w '%u'</smbconfoption>
+        <smbconfoption name="logon script">scripts\logon.cmd</smbconfoption>
+        <smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
+        <smbconfoption name="logon home">\\%L\%U</smbconfoption>
+        <smbconfoption name="logon drive">X:</smbconfoption>
+        <smbconfoption name="domain logons">Yes</smbconfoption>
+        <smbconfoption name="domain master">No</smbconfoption>
+        <smbconfoption name="#wins support">Yes</smbconfoption>
+        <smbconfoption name="wins server">192.168.123.124</smbconfoption>
+        <smbconfoption name="ldap admin dn">cn=Manager,dc=terpstra-world,dc=org</smbconfoption>
+        <smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+        <smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+        <smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+        <smbconfoption name="ldap passwd sync">Yes</smbconfoption>
+        <smbconfoption name="ldap suffix">dc=terpstra-world,dc=org</smbconfoption>
+        <smbconfoption name="ldap ssl">no</smbconfoption>
+        <smbconfoption name="ldap timeout">20</smbconfoption>
+        <smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+        <smbconfoption name="idmap backend">ldap:ldap://localhost</smbconfoption>
+        <smbconfoption name="idmap uid">15000-20000</smbconfoption>
+        <smbconfoption name="idmap gid">15000-20000</smbconfoption>
+        <smbconfoption name="winbind nested groups">Yes</smbconfoption>
+        <smbconfoption name="ea support">Yes</smbconfoption>
+        <smbconfoption name="map acl inherit">Yes</smbconfoption>
+	</smbconfblock>
+</example>
+
+<example id="sbent4smb2">
+<title>NT4 Migration Samba-3 Server <filename>smb.conf</filename> &smbmdash; Part: B</title>
+<smbconfblock>
+<smbconfsection name="[apps]"/>
+        <smbconfoption name="comment">Application Data</smbconfoption>
+        <smbconfoption name="path">/data/home/apps</smbconfoption>
+		<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+        <smbconfoption name="comment">Home Directories</smbconfoption>
+        <smbconfoption name="path">/home/users/%U/Documents</smbconfoption>
+        <smbconfoption name="valid users">%S</smbconfoption>
+        <smbconfoption name="read only">No</smbconfoption>
+        <smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+        <smbconfoption name="comment">SMB Print Spool</smbconfoption>
+        <smbconfoption name="path">/var/spool/samba</smbconfoption>
+        <smbconfoption name="guest ok">Yes</smbconfoption>
+        <smbconfoption name="printable">Yes</smbconfoption>
+        <smbconfoption name="use client driver">No</smbconfoption>
+        <smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+        <smbconfoption name="comment">Network Logon Service</smbconfoption>
+        <smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+        <smbconfoption name="guest ok">Yes</smbconfoption>
+        <smbconfoption name="locking">No</smbconfoption>
+
+<smbconfsection name="[profiles]"/>
+        <smbconfoption name="comment">Profile Share</smbconfoption>
+        <smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
+        <smbconfoption name="read only">No</smbconfoption>
+        <smbconfoption name="profile acls">Yes</smbconfoption>
+
+<smbconfsection name="[profdata]"/>
+        <smbconfoption name="comment">Profile Data Share</smbconfoption>
+        <smbconfoption name="path">/var/lib/samba/profdata</smbconfoption>
+        <smbconfoption name="read only">No</smbconfoption>
+        <smbconfoption name="profile acls">Yes</smbconfoption>
+
+<smbconfsection name="[print$]"/>
+        <smbconfoption name="comment">Printer Drivers</smbconfoption>
+        <smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
+	</smbconfblock>
+</example>
+
+		<step><para>
+		<indexterm><primary>slapd.conf</primary></indexterm>
+		Configure OpenLDAP in preparation for the migration. An example
+		<filename>sladp.conf</filename> file is shown in <link linkend="sbentslapd"/>.
+		The <constant>rootpw</constant> value is an encrypted password string that can
+		be obtained by executing the <command>slappasswd</command> command.
+		</para></step>
+
+<example id="sbentslapd">
+<title>NT4 Migration LDAP Server Configuration File: <filename>/etc/openldap/slapd.conf</filename> &smbmdash; Part A</title>
+<screen>
+include         /etc/openldap/schema/core.schema
+include         /etc/openldap/schema/cosine.schema
+include         /etc/openldap/schema/inetorgperson.schema
+include         /etc/openldap/schema/nis.schema
+include         /etc/openldap/schema/samba3.schema
+
+pidfile         /var/run/slapd/slapd.pid
+argsfile        /var/run/slapd/slapd.args
+
+access to dn.base=""
+                by self write
+                by * auth
+
+access to attr=userPassword
+                by self write
+                by * auth
+
+access to attr=shadowLastChange
+                by self write
+                by * read
+
+access to *
+                by * read
+                by anonymous auth
+</screen>
+</example>
+
+<example id="sbentslapd2">
+<title>NT4 Migration LDAP Server Configuration File: <filename>/etc/openldap/slapd.conf</filename> &smbmdash; Part B</title>
+<screen>
+#loglevel       256
+
+#schemacheck     on
+idletimeout     30
+#backend         bdb
+database        bdb
+checkpoint      1024 5
+cachesize       10000
+
+suffix          "dc=terpstra-world,dc=org"
+rootdn          "cn=Manager,dc=terpstra-world,dc=org"
+
+# rootpw = not24get
+rootpw          {SSHA}86kTavd9Dw3FAz6qzWTrCOKX/c0Qe+UV
+
+directory       /var/lib/ldap
+
+# Indices to maintain
+index objectClass           eq
+index cn                    pres,sub,eq
+index sn                    pres,sub,eq
+index uid                   pres,sub,eq
+index displayName           pres,sub,eq
+index uidNumber             eq
+index gidNumber             eq
+index memberUID             eq
+index sambaSID              eq
+index sambaPrimaryGroupSID  eq
+index sambaDomainName       eq
+index default               sub
+</screen>
+</example>
+
+		<step><para>
+		<indexterm><primary>nss_ldap</primary></indexterm>
+		<indexterm><primary>/etc/ldap.conf</primary></indexterm>
+		Install the PADL <command>nss_ldap</command> tool set, then configure the <filename>/etc/ldap.conf</filename>
+		as shown in <link linkend="sbrntldapconf"/>.
+		</para></step>
+
+<example id="sbrntldapconf">
+<title>NT4 Migration NSS LDAP File: <filename>/etc/ldap.conf</filename></title>
+<screen>
+host    127.0.0.1
+
+base    dc=terpstra-world,dc=org
+
+ldap_version    3
+
+binddn cn=Manager,dc=terpstra-world,dc=org
+bindpw not24get
+
+pam_password exop
+
+nss_base_passwd         ou=People,dc=terpstra-world,dc=org?one
+nss_base_shadow         ou=People,dc=terpstra-world,dc=org?one
+nss_base_group          ou=Groups,dc=terpstra-world,dc=org?one
+
+ssl off
+</screen>
+</example>
+
+		<step><para>
+		<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+		Edit the <filename>/etc/nsswitch.conf</filename> file so it has the entries shown
+		in <link linkend="sbentnss"/>. Note that the LDAP entries have been commented out.
+		This is deliberate. If these entries are active (not commented out), and the
+		<filename>/etc/ldap.conf</filename> file has been configured, when the LDAP server
+		is started, the process of starting the LDAP server will cause LDAP lookups. This
+		causes the LDAP server <command>slapd</command> to hang because it finds port 389
+		open and therefore cannot gain exclusive control of it. By commenting these entries
+		out, it is possible to avoid this gridlock situation and thus the overall
+		installation and configuration will progress more smoothly.
+		</para></step>
+
+<example id="sbentnss">
+<title>NT4 Migration NSS Control File: <filename>/etc/nsswitch.conf</filename> (Stage:1)</title>
+<screen>
+passwd:         files #ldap
+shadow:         files #ldap
+group:          files #ldap
+
+hosts:          files dns wins
+networks:       files dns
+
+services:       files
+protocols:      files
+rpc:            files
+ethers:         files
+netmasks:       files
+netgroup:       files
+publickey:      files
+
+bootparams:     files
+automount:      files nis
+aliases:        files
+#passwd_compat: ldap       #Not needed.
+#group_compat:  ldap      #Not needed.
+</screen>
+</example>
+
+		<step><para>
+		Validate the the target NT4 PDC name is being correctly resolved to its IP address by
+		executing the following:
+<screen>
+&rootprompt; ping transgression
+PING transgression.terpstra-world.org (192.168.1.5) 56(84) bytes of data.
+64 bytes from (192.168.1.5): icmp_seq=1 ttl=128 time=0.159 ms
+64 bytes from (192.168.1.5): icmp_seq=2 ttl=128 time=0.192 ms
+64 bytes from (192.168.1.5): icmp_seq=3 ttl=128 time=0.141 ms
+
+--- transgression.terpstra-world.org ping statistics ---
+3 packets transmitted, 3 received, 0% packet loss, time 2000ms
+rtt min/avg/max/mdev = 0.141/0.164/0.192/0.021 ms
+</screen>
+		Do not proceed to the next step if this step fails. It is imperative that the name of the PDC
+		can be resolved to its IP address. If this is broken, fix it.
+		</para></step>
+
+		<step><para>
+		Pull the domain SID from the NT4 domain that is being migrated as follows:
+<screen>
+&rootprompt; net rpc getsid -S TRANGRESSION -U Administrator%not24get
+Storing SID S-1-5-21-1385457007-882775198-1210191635 \
+                     for Domain DAMNATION in secrets.tdb
+</screen>
+		</para>
+
+		<para>
+		Another way to obtain the domain SID from the target NT4 domain that is being
+		migrated to Samba-3 is by executing the following:
+<screen>
+&rootprompt; net rpc info -S TRANSGRESSION
+</screen>
+		If this method is used, do not forget to store the SID obtained into the
+		<filename>secrets.tdb</filename> file. This can be done by executing:
+<screen>
+&rootprompt; net setlocalsid S-1-5-21-1385457007-882775198-1210191635
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Idealx</primary></indexterm>
+		<indexterm><primary>configure.pl</primary></indexterm>
+		<indexterm><primary>/opt/IDEALX/sbin</primary></indexterm>
+		<indexterm><primary>smbldap-tools</primary></indexterm>
+		Install the Idealx <command>smbldap-tools</command> software package, following
+		the instructions given in <link linkend="sbeidealx"/>. The resulting perl scripts
+		should be located in the <filename>/opt/IDEALX/sbin</filename> directory.
+		Change into that location, or wherever the scripts have been installed. Execute the
+		<filename>configure.pl</filename> script to configure the Idealx package for use.
+		Note: Use the domain SID obtained from the step above. The following is
+		an example configuration session:
+<screen>
+&rootprompt; ./configure.pl
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+       smbldap-tools script configuration
+       -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+Before starting, check
+ . if your samba controller is up and running.
+ . if the domain SID is defined
+                           (you can get it with the 'net getlocalsid')
+
+ . you can leave the configuration using the Crtl-c key combination
+ . empty value can be set with the "." character
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+Looking for configuration files...
+
+Samba Config File Location [/etc/samba/smb.conf] &gt;
+smbldap Config file Location (global parameters)
+           [/etc/smbldap-tools/smbldap.conf] &gt;
+smbldap Config file Location (bind parameters)
+      [/etc/smbldap-tools/smbldap_bind.conf] &gt;
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+Let's start configuring the smbldap-tools scripts ...
+
+. workgroup name: name of the domain Samba act as a PDC
+  workgroup name [DAMNATION] &gt;
+. netbios name: netbios name of the samba controller
+  netbios name [MERLIN] &gt;
+. logon drive: local path to which the home directory
+         will be connected (for NT Workstations). Ex: 'H:'
+  logon drive [X:] &gt; H:
+. logon home: home directory location (for Win95/98 or NT Workstation)
+  (use %U as username) Ex:'\\MERLIN\home\%U'
+  logon home (leave blank if you don't want homeDirectory)
+                                       [\\MERLIN\home\%U] &gt; \\%L\%U
+. logon path: directory where roaming profiles are stored.
+                                     Ex:'\\MERLIN\profiles\%U'
+  logon path (leave blank if you don't want roaming profile)
+                          [\\MERLIN\profiles\%U] &gt; \\%L\profiles\%U
+. home directory prefix (use %U as username) [/home/%U] >
+                                                        /home/users/%U
+. default user netlogon script (use %U as username) 
+                               [%U.cmd] &gt; scripts\logon.cmd
+  default password validation time (time in days) [45] > 180
+. ldap suffix [dc=terpstra-world,dc=org] &gt;
+. ldap group suffix [ou=Groups] &gt;
+. ldap user suffix [ou=People] &gt;
+. ldap machine suffix [ou=People] &gt;
+. Idmap suffix [ou=Idmap] &gt;
+. sambaUnixIdPooldn: object where you want to store the next uidNumber
+  and gidNumber available for new users and groups
+  sambaUnixIdPooldn object (relative to ${suffix}) 
+                                         [sambaDomainName=DAMNATION] >
+. ldap master server: 
+           IP address or DNS name of the master (writable) ldap server
+  ldap master server [] &gt; 127.0.0.1
+. ldap master port [389] &gt;
+. ldap master bind dn [cn=Manager,dc=terpstra-world,dc=org] &gt;
+. ldap master bind password [] &gt;
+. ldap slave server: IP address or DNS name of the slave ldap server:
+                                         can also be the master one
+  ldap slave server [] &gt; 127.0.0.1
+. ldap slave port [389] &gt;
+. ldap slave bind dn [cn=Manager,dc=terpstra-world,dc=org] &gt;
+. ldap slave bind password [] &gt;
+. ldap tls support (1/0) [0] &gt;
+. SID for domain DAMNATION: SID of the domain 
+                       (can be obtained with 'net getlocalsid MERLIN')
+  SID for domain DAMNATION []
+        &gt; S-1-5-21-1385457007-882775198-1210191635
+. unix password encryption: encryption used for unix passwords
+unix password encryption (CRYPT, MD5, SMD5, SSHA, SHA) [SSHA] &gt; MD5
+. default user gidNumber [513] &gt;
+. default computer gidNumber [515] &gt;
+. default login shell [/bin/bash] &gt;
+. default domain name to append to mail address [] &gt;
+                                                    terpstra-world.org
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+backup old configuration files:
+  /etc/smbldap-tools/smbldap.conf-&gt;
+                              /etc/smbldap-tools/smbldap.conf.old
+  /etc/smbldap-tools/smbldap_bind.conf-&gt;
+                              /etc/smbldap-tools/smbldap_bind.conf.old
+writing new configuration file:
+  /etc/smbldap-tools/smbldap.conf done.
+  /etc/smbldap-tools/smbldap_bind.conf done.
+</screen>
+		<indexterm><primary>sambaDomainName</primary></indexterm>
+		<indexterm><primary>NextFreeUnixId</primary></indexterm>
+		<indexterm><primary>updating smbldap-tools</primary></indexterm>
+		<indexterm><primary>smbldap-tools updating</primary></indexterm>
+		Note that the NT4 domain SID that was previously obtained was entered above. Also,
+		the sambaUnixIdPooldn object was specified as sambaDomainName=DAMNATION. This is
+		the location into which the Idealx smbldap-tools store the next available UID/GID
+		information. It is also where Samba stores domain specific information such as the
+		next RID, the SID, and so on. In older version of the smbldap-tools this information
+		was stored in the sambaUnixIdPooldn DIT location cn=NextFreeUnixId. Where smbldap-tools
+		are being upgraded to version 0.9.1 it is appropriate to update this to the new location
+		only if the directory information is also relocated.
+		</para></step>
+
+		<step><para>
+		Start the LDAP server using the system interface script. On Novell SLES9
+		this is done as shown here:
+<screen>
+&rootprompt; rcldap start
+</screen>
+		</para></step>
+
+		<step><para>
+		Edit the <filename>/etc/nsswitch.conf</filename> file so it has the entries shown in
+		<link linkend="sbentnss2"/>. Note that the LDAP entries have now been uncommented.
+		</para></step>
+
+<example id="sbentnss2">
+<title>NT4 Migration NSS Control File: <filename>/etc/nsswitch.conf</filename> (Stage:2)</title>
+<screen>
+passwd:         files ldap
+shadow:         files ldap
+group:          files ldap
+
+hosts:          files dns wins
+networks:       files dns
+
+services:       files
+protocols:      files
+rpc:            files
+ethers:         files
+netmasks:       files
+netgroup:       files
+publickey:      files
+
+bootparams:     files
+automount:      files nis
+aliases:        files
+#passwd_compat: ldap       #Not needed.
+#group_compat:  ldap      #Not needed.
+</screen>
+</example>
+
+		<step><para>
+		The LDAP management password must be installed into the <filename>secrets.tdb</filename>
+		file as follows:
+<screen>
+&rootprompt; smbpasswd -w not24get
+Setting stored password for 
+            "cn=Manager,dc=terpstra-world,dc=org" in secrets.tdb
+</screen>
+		</para></step>
+
+		<step><para>
+		Populate the LDAP directory as shown here:
+<screen>
+&rootprompt; /opt/IDEALX/sbin/smbldap-populate -a root -k 0 -m 0
+Using workgroup name from sambaUnixIdPooldn (smbldap.conf):
+                          sambaDomainName=DAMNATION
+Using builtin directory structure
+adding new entry: dc=terpstra-world,dc=org
+adding new entry: ou=People,dc=terpstra-world,dc=org
+adding new entry: ou=Groups,dc=terpstra-world,dc=org
+entry ou=People,dc=terpstra-world,dc=org already exist.
+adding new entry: ou=Idmap,dc=terpstra-world,dc=org
+adding new entry: sambaDomainName=DAMNATION,dc=terpstra-world,dc=org
+adding new entry: uid=root,ou=People,dc=terpstra-world,dc=org
+adding new entry: uid=nobody,ou=People,dc=terpstra-world,dc=org
+adding new entry: cn=Domain Admins,ou=Groups,dc=terpstra-world,dc=org
+adding new entry: cn=Domain Users,ou=Groups,dc=terpstra-world,dc=org
+adding new entry: cn=Domain Guests,ou=Groups,dc=terpstra-world,dc=org
+adding new entry: cn=Domain Computers,ou=Groups,dc=terpstra-world,dc=org
+adding new entry: cn=Administrators,ou=Groups,dc=terpstra-world,dc=org
+adding new entry: cn=Print Operators,ou=Groups,dc=terpstra-world,dc=org
+adding new entry: cn=Backup Operators,ou=Groups,dc=terpstra-world,dc=org
+adding new entry: cn=Replicators,ou=Groups,dc=terpstra-world,dc=org
+</screen>
+		The script tries to add the ou=People container twice, hence the error message.
+		This is expected behavior.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Novell SUSE SLES 9</primary></indexterm>
+		Restart the LDAP server following initialization of the LDAP directory. Execute the
+		system control script provided on your system. The following steps can be used on
+		Novell SUSE SLES 9:
+<screen>
+&rootprompt; rcldap restart
+&rootprompt; chkconfig ldap on
+</screen>
+		</para></step>
+
+		<step><para>
+		Verify that the new user accounts that have been added to the LDAP directory can be
+		resolved as follows:
+<screen>
+&rootprompt; getent passwd
+...
+nobody:x:65534:65533:nobody:/var/lib/nobody:/bin/bash
+man:x:13:62:Manual pages viewer:/var/cache/man:/bin/bash
+news:x:9:13:News system:/etc/news:/bin/bash
+uucp:x:10:14:Unix-to-Unix CoPy system:/etc/uucp:/bin/bash
++::0:0:::
+root:x:0:0:Netbios Domain Administrator:/home/users/root:/bin/false
+nobody:x:999:514:nobody:/dev/null:/bin/false
+</screen>
+		Now repeat this for the group accounts as shown here:
+<screen>
+&rootprompt; getent group
+...
+nobody:x:65533:
+nogroup:x:65534:nobody
+users:x:100:
++::0:
+Domain Admins:x:512:root
+Domain Users:x:513:
+Domain Guests:x:514:
+Domain Computers:x:515:
+Administrators:x:544:
+Print Operators:x:550:
+Backup Operators:x:551:
+Replicators:x:552:
+</screen>
+		In both cases the LDAP accounts follow the <quote>+::0:</quote> entry.
+		</para></step>
+
+		<step><para>
+		Now it is time to join the Samba BDC to the target NT4 domain that is being
+		migrated to Samba-3 by executing the following:
+<screen>
+&rootprompt; net rpc join -S TRANSGRESSION -U Administrator%not24get
+merlin:/opt/IDEALX/sbin # net rpc join -S TRANSGRESSION \
+                         -U Administrator%not24get
+Joined domain DAMNATION.
+</screen>
+		</para></step>
+
+		<step><para>
+		Set the new domain administrator (root) password for both UNIX and Windows as shown here:
+<screen>
+&rootprompt; /opt/IDEALX/sbin/smbldap-passwd root
+Changing password for root
+New password : ********
+Retype new password : ********
+</screen>
+		Note: During account migration, the Windows Administrator account will not be migrated
+		to the Samba server.
+		</para></step>
+
+		<step><para>
+		Now validate that these accounts can be resolved using Samba's tools as
+		shown here for user accounts:
+<screen>
+&rootprompt; pdbedit -Lw
+root:0:84B0D8E14D158FF8417EAF50CFAC29C3:
+        AF6DD3FD4E2EA8BDE1695A3F05EFBF52:[U          ]:LCT-425F6467:
+nobody:65534:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:
+        NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:[NU         ]:LCT-00000000:
+</screen>
+		Now complete the following step to validate that group account mappings have
+		been correctly set:
+<screen>
+&rootprompt; net groupmap list
+Domain Admins (S-1-5-21-1385457007-882775198-1210191635-512)
+                                            -&gt; Domain Admins
+Domain Users (S-1-5-21-1385457007-882775198-1210191635-513) 
+                                             -&gt; Domain Users
+Domain Guests (S-1-5-21-1385457007-882775198-1210191635-514) 
+                                            -&gt; Domain Guests
+Domain Computers (S-1-5-21-1385457007-882775198-1210191635-515) 
+                                          -&gt; Domain Computers
+Administrators (S-1-5-32-544) -&gt; Administrators
+Print Operators (S-1-5-32-550) -&gt; Print Operators
+Backup Operators (S-1-5-32-551) -&gt; Backup Operators
+Replicators (S-1-5-32-552) -> Replicators
+</screen>
+		These are the expected results for a correctly configured system.
+		</para></step>
+
+		<step><para>
+		Commence migration as shown here:
+<screen>
+&rootprompt; net rpc vampire -S TRANSGRESSION \
+       -U Administrator%not24get &gt; /tmp/vampire.log 2&gt;1
+</screen>
+		Check the vampire log to confirm that only expected errors have been
+		reported. See <link linkend="sbevam1"/>.
+		</para></step>
+
+		<step><para>
+		The migration of user accounts can be quickly validated as follows:
+<screen>
+&rootprompt; pdbedit -Lw
+root:0:84B0D8E14D158FF8417EAF50CFAC29C3:...
+nobody:65534:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:...
+Administrator:0:84B0D8E14D158FF8417EAF50CFAC29C3:...
+Guest:1:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:...
+TRANSGRESSION$:2:CC044B748CEE294CE76B6B0D1B86C1A8:...
+IUSR_TRANSGRESSION:3:64046AC81B056C375F9537FC409085F8:...
+MIDEARTH$:4:E93186E5819706D2AAD3B435B51404EE:...
+atrickhoffer:5:DC08CFE0C12B2867352502E32A407F23:...
+barryf:6:B829BCDE01FF24376E45D5F10408CFBD:...
+fsellerby:7:6A97CBEBE8F9826B417EAF50CFAC29C3:...
+gdaison:8:48F6A8C8A900024351DA8C2061C5F1D3:...
+hrambotham:9:7330D9EA0964465EAAD3B435B51404EE:...
+jrhapsody:10:ACBA7D207E2BA35D9BD41A26B01626BD:...
+maryk:11:293B5A4CA41F6CA1A7D80430B8342B73:...
+jacko:12:8E8982D86BD037C364BBD09A598E07AD:...
+bridge:13:0D2CA7D2BE67FE2193BE3A377C968336:...
+sharpec:14:8841A75CAC19D2855D8B73B1F4D430F8:...
+jimbo:15:6E8BDC904FD9EC5C17306D272A9441BB:...
+dhenwick:16:D1694A03C33584BDAAD3B435B51404EE:...
+dork:17:69E2D19E69A593D5AAD3B435B51404EE:...
+blue:18:E355EBF9559979FEAAD3B435B51404EE:...
+billw:19:EE35C3481CF7F7DB484448BC86A641A5:...
+rfreshmill:20:7EC033B58661B60CAAD3B435B51404EE:...
+MAGGOT$:21:A3B9334765AD30F7AAD3B435B51404EE:...
+TRENTWARE$:22:1D92C8DD5E7F0DDF93BE3A377C968336:...
+MORTON$:23:89342E69DCA9D3F8AAD3B435B51404EE:...
+NARM$:24:2B93E2D1D25448BDAAD3B435B51404EE:...
+LAPDOG$:25:14AA535885120943AAD3B435B51404EE:...
+SCAVENGER$:26:B6288EB6D147B56F8963805A19B0ED49:...
+merlin$:27:820C50523F368C54AB9D85AE603AD09D:...
+</screen>
+		</para></step>
+
+		<step><para>
+		The mapping of UNIX and Windows groups can be validated as show here:
+<screen>
+&rootprompt; net groupmap list
+Domain Admins (S-1-5-21-1385457007-882775198-1210191635-512)
+                                                     -&gt; Domain Admins
+Domain Users (S-1-5-21-1385457007-882775198-1210191635-513)
+                                                      -&gt; Domain Users
+Domain Guests (S-1-5-21-1385457007-882775198-1210191635-514)
+                                                     -&gt; Domain Guests
+Domain Computers (S-1-5-21-1385457007-882775198-1210191635-515)
+                                                   -&gt; Domain Computers
+Administrators (S-1-5-32-544) -&gt; Administrators
+Print Operators (S-1-5-32-550) -&gt; Print Operators
+Backup Operators (S-1-5-32-551) -&gt; Backup Operators
+Replicator (S-1-5-32-552) -&gt; Replicators
+Engineers (S-1-5-21-1385457007-882775198-1210191635-1020) -&gt; Engineers
+Marketoids (S-1-5-21-1385457007-882775198-1210191635-1022) -&gt; Marketoids
+Gnomes (S-1-5-21-1385457007-882775198-1210191635-1023) -&gt; Gnomes
+Catalyst (S-1-5-21-1385457007-882775198-1210191635-1024) -&gt; Catalyst
+Recieving (S-1-5-21-1385457007-882775198-1210191635-1025) -&gt; Recieving
+Rubberboot (S-1-5-21-1385457007-882775198-1210191635-1026) -&gt; Rubberboot
+Sales (S-1-5-21-1385457007-882775198-1210191635-1027) -&gt; Sales
+Accounting (S-1-5-21-1385457007-882775198-1210191635-1028) -&gt; Accounting
+Shipping (S-1-5-21-1385457007-882775198-1210191635-1029) -&gt; Shipping
+Account Operators (S-1-5-32-548) -&gt; Account Operators
+Guests (S-1-5-32-546) -&gt; Guests
+Server Operators (S-1-5-32-549) -&gt; Server Operators
+Users (S-1-5-32-545) -&gt; Users
+</screen>
+		It is of vital importance that the domain SID portions of all group
+		accounts are identical.
+		</para></step>
+
+		<step><para>
+		The final responsibility in the migration process is to create identical
+		shares and printing resources on the new Samba-3 server, copy all data
+		across, set up privileges, and set share and file/directory access controls.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>domain master</primary></indexterm>
+		<indexterm><primary>PDC</primary></indexterm>
+		Edit the &smb.conf; file to  reset the parameter 
+		<smbconfoption name="domain master">Yes</smbconfoption> so that
+		the Samba server functions as a PDC for the purpose of migration.
+		Also, uncomment the deletion scripts so they will now be fully functional,
+		enable the <parameter>wins support = yes</parameter> parameter and
+		comment out the <parameter>wins server</parameter>. Validate the configuration
+		with the <command>testparm</command> utility as shown here:
+<screen>
+&rootprompt; testparm
+Load smb config files from /etc/samba/smb.conf
+Processing section "[apps]"
+Processing section "[media]"
+Processing section "[homes]"
+Processing section "[printers]"
+Processing section "[netlogon]"
+Processing section "[profiles]"
+Processing section "[profdata]"
+Processing section "[print$]"
+Loaded services file OK.
+Server role: ROLE_DOMAIN_PDC
+Press enter to see a dump of your service definitions
+</screen>
+                </para></step>
+
+		<step><para>
+		Now shut down the old NT4 PDC. Only when the old NT4 PDC and all
+		NT4 BDCs have been shut down can the Samba-3 PDC be started.
+		</para></step>
+
+		<step><para>
+		All workstations should function as they did with the old NT4 PDC. All
+		interdomain trust accounts should remain in place and fully functional.
+		All machine accounts and user logon accounts should also function correctly.
+		</para></step>
+
+		<step><para>
+		The configuration of Samba-3 BDC servers can be accomplished now or at any
+		convenient time in the future. Please refer to the carefully detailed process
+		for doing so is outlined in <link linkend="sbehap-bldg1"/>.
+		</para></step>
+
+	</procedure>
+
+	<sect3 id="sbevam1">
+	<title>Migration Log Validation</title>
+
+	<para>
+	The following <filename>vampire.log</filename> file is typical of a valid migration.
+<screen>
+adding user Administrator to group Domain Admins
+adding user atrickhoffer to group Engineers
+adding user dhenwick to group Engineers
+adding user dork to group Engineers
+adding user rfreshmill to group Marketoids
+adding user jacko to group Gnomes
+adding user jimbo to group Gnomes
+adding user maryk to group Gnomes
+adding user gdaison to group Gnomes
+adding user dhenwick to group Catalyst
+adding user jacko to group Catalyst
+adding user jacko to group Recieving
+adding user blue to group Recieving
+adding user hrambotham to group Rubberboot
+adding user billw to group Sales
+adding user bridge to group Sales
+adding user jrhapsody to group Sales
+adding user maryk to group Sales
+adding user rfreshmill to group Sales
+adding user fsellerby to group Sales
+adding user sharpec to group Sales
+adding user jimbo to group Accounting
+adding user gdaison to group Accounting
+adding user jacko to group Shipping
+adding user blue to group Shipping
+Fetching DOMAIN database
+Creating unix group: 'Engineers'
+Creating unix group: 'Marketoids'
+Creating unix group: 'Gnomes'
+Creating unix group: 'Catalyst'
+Creating unix group: 'Recieving'
+Creating unix group: 'Rubberboot'
+Creating unix group: 'Sales'
+Creating unix group: 'Accounting'
+Creating unix group: 'Shipping'
+Creating account: Administrator
+Creating account: Guest
+Creating account: TRANSGRESSION$
+Creating account: IUSR_TRANSGRESSION
+Creating account: MIDEARTH$
+Creating account: atrickhoffer
+Creating account: barryf
+Creating account: fsellerby
+Creating account: gdaison
+Creating account: hrambotham
+Creating account: jrhapsody
+Creating account: maryk
+Creating account: jacko
+Creating account: bridge
+Creating account: sharpec
+Creating account: jimbo
+Creating account: dhenwick
+Creating account: dork
+Creating account: blue
+Creating account: billw
+Creating account: rfreshmill
+Creating account: MAGGOT$
+Creating account: TRENTWARE$
+Creating account: MORTON$
+Creating account: NARM$
+Creating account: LAPDOG$
+Creating account: SCAVENGER$
+Creating account: merlin$
+Group members of Domain Admins: Administrator,
+Group members of Domain Users: Administrator(primary),
+TRANSGRESSION$(primary),IUSR_TRANSGRESSION(primary),
+MIDEARTH$(primary),atrickhoffer(primary),barryf(primary),
+fsellerby(primary),gdaison(primary),hrambotham(primary),
+jrhapsody(primary),maryk(primary),jacko(primary),bridge(primary),
+sharpec(primary),jimbo(primary),dhenwick(primary),dork(primary),
+blue(primary),billw(primary),rfreshmill(primary),MAGGOT$(primary),
+TRENTWARE$(primary),MORTON$(primary),NARM$(primary),
+LAPDOG$(primary),SCAVENGER$(primary),merlin$(primary),
+Group members of Domain Guests: Guest(primary),
+Group members of Engineers: atrickhoffer,dhenwick,dork,
+Group members of Marketoids: rfreshmill,
+Group members of Gnomes: jacko,jimbo,maryk,gdaison,
+Group members of Catalyst: dhenwick,jacko,
+Group members of Recieving: jacko,blue,
+Group members of Rubberboot: hrambotham,
+Group members of Sales: billw,bridge,jrhapsody,maryk,
+rfreshmill,fsellerby,sharpec,
+Group members of Accounting: jimbo,gdaison,
+Group members of Shipping: jacko,blue,
+Fetching BUILTIN database
+skipping SAM_DOMAIN_INFO delta for 'Builtin' (is not my domain)
+Creating unix group: 'Account Operators'
+Creating unix group: 'Guests'
+Creating unix group: 'Server Operators'
+Creating unix group: 'Users'
+</screen>
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>NT4 Migration Using tdbsam Backend</title>
+
+	<para>
+	In this example, we change the domain name of the NT4 server from
+	<constant>DRUGPREP</constant> to <constant>MEGANET</constant> prior to the use
+	of the vampire (migration) tool. This migration process makes use of Linux system tools
+	(like <command>useradd</command>) to add the accounts that are migrated into the 
+	UNIX/Linux <filename>/etc/passwd</filename> and <filename>/etc/group</filename>
+	databases. These entries must therefore be present, and correct options specified,
+	in your &smb.conf; file, or else the migration does not work as it should.
+	</para>
+
+	<procedure>
+	<title>Migration Steps Using tdbsam</title>
+
+		<step><para>
+		Prepare a Samba-3 server precisely per the instructions shown in <link linkend="Big500users"/>.
+		Set the workgroup name to <constant>MEGANET</constant>.
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>domain master</primary>
+	      </indexterm><indexterm>
+		<primary>BDC</primary>
+	      </indexterm>
+		Edit the &smb.conf; file to temporarily change the parameter 
+		<smbconfoption name="domain master">No</smbconfoption> so
+		the Samba server functions as a BDC for the purpose of migration.
+                </para></step>
+
+		<step><para>
+		Start Samba as you have done previously.
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>net</primary>
+		<secondary>rpc</secondary>
+		<tertiary>join</tertiary>
+	      </indexterm>
+		Join the NT4 Domain as a BDC, as shown here:
+<screen>
+&rootprompt; net rpc join -S oldnt4pdc -W MEGANET -UAdministrator%not24get
+Joined domain MEGANET.
+</screen>
+		</para></step>
+
+		<step><para><indexterm>
+		<primary>net</primary>
+		<secondary>rpc</secondary>
+		<tertiary>vampire</tertiary>
+	      </indexterm>
+		You may vampire the accounts from the NT4 PDC by executing the command, as shown here:
+<screen>
+&rootprompt; net rpc vampire -S oldnt4pdc -U Administrator%not24get
+Fetching DOMAIN database
+SAM_DELTA_DOMAIN_INFO not handled
+Creating unix group: 'Domain Admins'
+Creating unix group: 'Domain Users'
+Creating unix group: 'Domain Guests'
+Creating unix group: 'Engineers'
+Creating unix group: 'Marketoids'
+Creating unix group: 'Account Operators'
+Creating unix group: 'Administrators'
+Creating unix group: 'Backup Operators'
+Creating unix group: 'Guests'
+Creating unix group: 'Print Operators'
+Creating unix group: 'Replicator'
+Creating unix group: 'Server Operators'
+Creating unix group: 'Users'
+Creating account: Administrator
+Creating account: Guest
+Creating account: oldnt4pdc$
+Creating account: jacko
+Creating account: maryk
+Creating account: bridge
+Creating account: sharpec
+Creating account: jimbo
+Creating account: dhenwick
+Creating account: dork
+Creating account: blue
+Creating account: billw
+Creating account: massive$
+Group members of Engineers: Administrator,
+                 sharpec(primary),bridge,billw(primary),dhenwick
+Group members of Marketoids: Administrator,jacko(primary),
+                maryk(primary),jimbo,blue(primary),dork(primary)
+Creating unix group: 'Gnomes'
+Fetching BUILTIN database
+SAM_DELTA_DOMAIN_INFO not handled
+</screen>
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>pdbedit</primary>
+	      </indexterm>
+		At this point, we can validate our migration. Let's look at the accounts
+		in the form in which they are seen in a smbpasswd file. This achieves that:
+<screen>
+&rootprompt; pdbedit -Lw
+Administrator:505:84B0D8E14D158FF8417EAF50CFAC29C3:
+     AF6DD3FD4E2EA8BDE1695A3F05EFBF52:[UX         ]:LCT-3DF7AA9F:
+jimbo:512:6E9A2A51F64A1BD5C187B8085FE1D9DF:
+     CDF7E305E639966E489A0CEFB95EE5E0:[UX         ]:LCT-3E9362BC:
+sharpec:511:E4301A7CD8FDD1EC6BBF9BC19CDF8151:
+     7000255938831D5B948C95C1931534C5:[UX         ]:LCT-3E8B42C4:
+dhenwick:513:DCD8886141E3F892AAD3B435B51404EE:
+     2DB36465949CB938DD98C312EFDC2639:[UX         ]:LCT-3E939F41:
+bridge:510:3FE6873A43101B46417EAF50CFAC29C3:
+     891741F481AF111B4CAA09A94016BD01:[UX         ]:LCT-3E8B4291:
+blue:515:256D41D2559BB3D2AAD3B435B51404EE:
+     9CCADDA4F7D281DD0FAD321478C6F971:[UX         ]:LCT-3E939FDC:
+diamond$:517:6C8E7B64EDCDBC4218B6345447A4454B:
+     3323AC63C666CFAACB60C13F65D54E9A:[S          ]:LCT-00000000:
+oldnt4pdc$:507:3E39430CDCABB5B09ED320D0448AE568:
+     95DBAF885854A919C7C7E671060478B9:[S          ]:LCT-3DF7AA9F:
+Guest:506:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
+     XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[DUX        ]:LCT-3E93A008:
+billw:516:85380CA7C21B6EBE168C8150662AF11B:
+     5D7478508293709937E55FB5FBA14C17:[UX         ]:LCT-3FED7CA1:
+dork:514:78C70DDEC35A35B5AAD3B435B51404EE:
+     0AD886E015AC595EC0AF40E6C9689E1A:[UX         ]:LCT-3E939F9A:
+jacko:508:BC472F3BF9A0A5F63832C92FC614B7D1:
+     0C6822AAF85E86600A40DC73E40D06D5:[UX         ]:LCT-3E8B4242:
+maryk:509:3636AB7E12EBE79AB79AE2610DD89D4C:
+     CF271B744F7A55AFDA277FF88D80C527:[UX         ]:LCT-3E8B4270:
+</screen>
+		</para></step>
+
+		<step><para><indexterm>
+		<primary>pdbedit</primary>
+	      </indexterm>
+		An expanded view of a user account entry shows more of what was
+		obtained from the NT4 PDC:
+<screen>
+sleeth:~ # pdbedit -Lv maryk
+Unix username:        maryk
+NT username:          maryk
+Account Flags:        [UX         ]
+User SID:             S-1-5-21-1988699175-926296742-1295600288-1003
+Primary Group SID:    S-1-5-21-1988699175-926296742-1295600288-1007
+Full Name:            Mary Kathleen
+Home Directory:       \\diamond\maryk
+HomeDir Drive:        X:
+Logon Script:         scripts\logon.bat
+Profile Path:         \\diamond\profiles\maryk
+Domain:               MEGANET
+Account desc:         Peace Maker
+Workstations:
+Munged dial:
+Logon time:           0
+Logoff time:          Mon, 18 Jan 2038 20:14:07 GMT
+Kickoff time:         Mon, 18 Jan 2038 20:14:07 GMT
+Password last set:    Wed, 02 Apr 2003 13:05:04 GMT
+Password can change:  0
+Password must change: Mon, 18 Jan 2038 20:14:07 GMT
+</screen>
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>net</primary>
+		<secondary>group</secondary>
+	      </indexterm>
+		The following command lists the long names of the groups that have been
+		imported (vampired) from the NT4 PDC:
+<screen>
+&rootprompt; net group -l -Uroot%not24get -Smassive
+
+Group name            Comment
+-----------------------------
+Engineers             Snake Oil Engineers
+Marketoids            Untrustworthy Hype Vendors
+Gnomes                Plain Vanilla Garden Gnomes
+Replicator            Supports file replication in a domain
+Guests                Users granted guest access to the computer/domain
+Administrators        Members can fully administer the computer/domain
+Users                 Ordinary users
+</screen>
+		Everything looks well and in order.
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>domain master</primary>
+	      </indexterm><indexterm>
+		<primary>PDC</primary>
+	      </indexterm>
+		Edit the &smb.conf; file to  reset the parameter 
+		<smbconfoption name="domain master">Yes</smbconfoption> so
+		the Samba server functions as a PDC for the purpose of migration.
+                </para></step>
+	</procedure>
+	</sect2>
+
+	<sect2>
+		<title>Key Points Learned</title>
+
+		<para>
+		Migration of an NT4 PDC database to a Samba-3 PDC is possible.
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			An LDAP backend is a suitable vehicle for NT4 migrations.
+			</para></listitem>
+
+			<listitem><para>
+			A tdbsam backend can be used to perform a migration.
+			</para></listitem>
+
+			<listitem><para>
+			Multiple NT4 domains can be merged into a single Samba-3
+			domain.
+			</para></listitem>
+
+			<listitem><para>
+			The net Samba-3 domain most likely requires some
+			administration and updating before going live.
+			</para></listitem>
+		</itemizedlist>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	</para>
+
+	<qandaset defaultlabel="chap08qa" type="number">
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>clean database</primary>
+	      </indexterm>
+		Why must I start each migration with a clean database?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>merge</primary>
+	      </indexterm>
+		This is a recommendation that permits the data from each NT4 domain to
+		be kept separate until you are ready to merge them. Also, if you do not start with a clean database,
+		you may find errors due to users or groups from multiple domains having the
+		same name but different SIDs. It is better to permit each migration to complete
+		without undue errors and then to handle the merging of vampired data under
+		proper supervision.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>Domain SID</primary>
+	      </indexterm>
+		Is it possible to set my domain SID to anything I like?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>auto-generated SID</primary>
+	      </indexterm><indexterm>
+		<primary>SID</primary>
+	      </indexterm><indexterm>
+		<primary>Domain SID</primary>
+	      </indexterm>
+		Yes, so long as the SID you create has the same structure as an autogenerated SID.
+		The typical SID looks like this: S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX, where
+		the XXXXXXXXXX can be any number with from 6 to 10 digits. On the other hand, why
+		would you really want to create your own SID? I cannot think of a good reason.
+		You may want to set the SID to one that is already in use somewhere on your network,
+		but that is a little different from straight out creating your own domain SID.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>/etc/passwd</primary>
+	      </indexterm><indexterm>
+		<primary>/etc/group</primary>
+	      </indexterm><indexterm>
+		<primary>tdbsam</primary>
+	      </indexterm><indexterm>
+		<primary>passdb backend</primary>
+	      </indexterm><indexterm>
+		<primary>accounts</primary>
+		<secondary>user</secondary>
+	      </indexterm><indexterm>
+		<primary>accounts</primary>
+		<secondary>group</secondary>
+	      </indexterm><indexterm>
+		<primary>accounts</primary>
+		<secondary>Domain</secondary>
+	      </indexterm>
+		When using a tdbsam passdb backend, why must I have all domain user and group accounts
+		in <filename>/etc/passwd</filename> and <filename>/etc/group</filename>?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>UID</primary>
+	      </indexterm><indexterm>
+		<primary>GID</primary>
+	      </indexterm><indexterm>
+		<primary>smbpasswd</primary>
+	      </indexterm><indexterm>
+		<primary>/etc/passwd</primary>
+	      </indexterm><indexterm>
+		<primary>Posix</primary>
+	      </indexterm><indexterm>
+		<primary>LDAP database</primary>
+	      </indexterm>
+		Samba-3 must be able to tie all user and group account SIDs to a UNIX UID or GID. Samba
+		does not fabricate the UNIX IDs from thin air, but rather requires them to be located
+		in a suitable place. 
+		</para>
+
+		<para>
+		When migrating a <filename>smbpasswd</filename> file to an LDAP backend, the
+		UID of each account is taken together with the account information in the 
+		<filename>/etc/passwd</filename>, and both sets of data are used to create the account
+		entry in the LDAP database. 
+		</para>
+
+		<para>
+		If you elect to create the POSIX account also, the entire UNIX account is copied to the 
+		LDAP backend. The same occurs with NT groups and UNIX groups. At the conclusion of 
+		migration to the LDAP database, the accounts may be removed from the UNIX database files. 
+		In short then, all UNIX and Windows networking accounts, both in tdbsam as well as in 
+		LDAP, require UIDs/GIDs.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>validate</primary>
+	      </indexterm><indexterm>
+		<primary>connectivity</primary>
+	      </indexterm><indexterm>
+		<primary>migration</primary>
+	      </indexterm>
+		Why did you validate connectivity before attempting migration?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Access validation before attempting to migrate NT4 domain accounts helps to pinpoint
+		potential problems that may otherwise affect or impede account migration. I am always
+		mindful of the 4 P's of migration: Planning Prevents Poor Performance.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		How would you merge 10 tdbsam-based domains into an LDAP database?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>risk</primary>
+	      </indexterm><indexterm>
+		<primary>dump</primary>
+	      </indexterm><indexterm>
+		<primary>tdbsam</primary>
+	      </indexterm><indexterm>
+		<primary>Samba Domain</primary>
+	      </indexterm><indexterm>
+		<primary>UID</primary>
+	      </indexterm><indexterm>
+		<primary>GID</primary>
+	      </indexterm><indexterm>
+		<primary>pdbedit</primary>
+	      </indexterm><indexterm>
+		<primary>transfer</primary>
+	      </indexterm><indexterm>
+		<primary>smbpasswd</primary>
+	      </indexterm><indexterm>
+		<primary>LDAP</primary>
+	      </indexterm><indexterm>
+		<primary>tool</primary>
+	      </indexterm>
+		If you have 10 tdbsam Samba domains, there is considerable risk that there are a number of
+		accounts that have the same UNIX identifier (UID/GID). This means that you almost 
+		certainly have to edit a lot of data. It would be easiest to dump each database in smbpasswd
+		file format and then manually edit all records to ensure that each has a unique UID. Each
+		file can then be imported a number of ways. You can use the <command>pdbedit</command> tool
+		to affect a transfer from the smbpasswd file to LDAP, or you can migrate them en masse to
+		tdbsam and then to LDAP. The final choice is yours. Just remember to verify all accounts that
+		you have migrated before handing over access to a user. After all, too many users with a bad
+		migration experience may threaten your career.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>machine accounts</primary>
+	      </indexterm><indexterm>
+		<primary>accounts</primary>
+		<secondary>machine</secondary>
+	      </indexterm>
+		I want to change my domain name after I migrate all accounts from an NT4 domain to a 
+		Samba-3 domain. Does it make any sense to migrate the machine accounts in that case?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>registry</primary>
+	      </indexterm><indexterm>
+		<primary>un-join</primary>
+	      </indexterm><indexterm>
+		<primary>rejoin</primary>
+	      </indexterm><indexterm>
+		<primary>tattooing</primary>
+	      </indexterm>
+		I would recommend not to migrate the machine account. The machine accounts should still work, but there are registry entries
+		on each Windows NT4 and upward client that have a tattoo of the old domain name. If you
+		unjoin the domain and then rejoin the newly renamed Samba-3 domain, you can be certain to avoid
+		this tattooing effect.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>multiple group mappings</primary>
+	      </indexterm>
+		After merging multiple NT4 domains into a Samba-3 domain, I lost all multiple group mappings. Why?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>/etc/passwd</primary>
+	      </indexterm><indexterm>
+		<primary>/etc/group</primary>
+	      </indexterm>
+		Samba-3 currently does not implement multiple group membership internally. If you use the Windows 
+		NT4 Domain User Manager to manage accounts and you have an LDAP backend, the multiple group
+		membership is stored in the POSIX groups area. If you use either tdbsam or smbpasswd backend,
+		then multiple group membership is handled through the UNIX groups file. When you dump the user
+		accounts, no group account information is provided. When you edit (change) UIDs and GIDs in each
+		file to which you migrated the NT4 Domain data, do not forget to edit the UNIX <filename>/etc/passwd</filename>
+		and <filename>/etc/group</filename> information also. That is where the multiple group information
+		is most closely at your fingertips.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		How can I reset group membership after loading the account information into the LDAP database?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>SRVTOOLS.EXE</primary>
+	      </indexterm>
+		You can use the NT4 Domain User Manager that can be downloaded from the Microsoft Web site. The
+		installation file is called <filename>SRVTOOLS.EXE</filename>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>group names</primary>
+	      </indexterm>
+		What are the limits or constraints that apply to group names?
+		</para>
+
+	</question>
+	<answer>
+
+	    <para><indexterm>
+		<primary>limit</primary>
+	      </indexterm><indexterm>
+		<primary>shadow-utils</primary>
+	      </indexterm><indexterm>
+		<primary>groupadd</primary>
+	      </indexterm><indexterm>
+		<primary>groupdel</primary>
+	      </indexterm><indexterm>
+		<primary>groupmod</primary>
+	      </indexterm><indexterm>
+		<primary>account names</primary>
+	      </indexterm>
+		A Windows 200x group name can be up to 254 characters long, while in Windows NT4 the group
+		name is limited to 20 characters. Most UNIX systems limit this to 32 characters. Windows 
+		groups can contain upper- and lowercase characters, as well as spaces.
+		Many UNIX system do not permit the use of uppercase characters, and some do not permit the
+		space character either. A number of systems (i.e., Linux) work fine with both uppercase
+		and space characters in group names, but the shadow-utils package that provides the group
+		control functions (<command>groupadd</command>, <command>groupmod</command>, <command>groupdel</command>, and so on) do not permit them.
+		Also, a number of UNIX systems management tools enforce their own particular interpretation
+		of the POSIX standards and likewise do not permit uppercase or space characters in group
+		or user account names. You have to experiment with your system to find what its 
+		peculiarities are.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+	    <para><indexterm>
+		<primary>vampire</primary>
+	      </indexterm>
+		My Windows NT4 PDC has 323,000 user accounts. How long will it take to migrate them to a Samba-3
+		LDAP backend system using the vampire process?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		UNIX UIDs and GIDs on most UNIX systems use an unsigned short or an unsigned integer. Recent Linux
+		kernels support at least a much larger number. On systems that have a 16-bit constraint on UID/GIDs,
+		you would not be able to migrate 323,000 accounts because this number cannot fit into a 16-bit unsigned
+		integer. UNIX/Linux systems that have a 32-bit UID/GID can easily handle this number of accounts. 
+		Please check this carefully before you attempt to effect a migration using the vampire process.
+		</para>
+
+	    <para><indexterm>
+		<primary>Migration speed</primary>
+	      </indexterm>
+		Migration speed depends much on the processor speed, the network speed, disk I/O capability, and
+		LDAP update overheads. On a dual processor AMD MP1600+ with 1 GB memory that was mirroring LDAP
+		to a second identical system over 1 Gb Ethernet, I was able to migrate around 180 user accounts
+		per minute. Migration would obviously go much faster if LDAP mirroring were turned off during the migration.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	</qandaset>
+
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-MigrateNW4Samba3.xml b/docs-xml/Samba3-ByExample/SBE-MigrateNW4Samba3.xml
new file mode 100644
index 00000000000..5bf8553e5b0
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-MigrateNW4Samba3.xml
@@ -0,0 +1,1798 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="nw4migration">
+  <title>Migrating NetWare Server to Samba-3</title>
+
+	<para>
+	<indexterm><primary>Novell</primary></indexterm>
+	<indexterm><primary>SUSE</primary></indexterm>
+	Novell is a company any seasoned IT manager has to admire. It has become increasingly
+	Linux-friendly and is emerging out of a deep regression that almost saw the company
+	disappear into obscurity. Novell's SUSE Linux hosts the NetWare server and it is the
+	platform of choice to which many older NetWare servers are being migrated. 
+	It will be interesting to see what becomes of NetWare over time.
+	Meanwhile, there can be no denying that Novell is a Linux company.
+	</para>
+
+	<para>
+	<indexterm><primary>Red Hat</primary></indexterm>
+	<indexterm><primary>Debian</primary></indexterm>
+	<indexterm><primary>Gentoo</primary></indexterm>
+	<indexterm><primary>Mandrake</primary></indexterm>
+	Whatever flavor of Linux is preferred in your environment, whether Red Hat, Debian,
+	Gentoo, Mandrake, or SUSE (Novell), the information in this chapter should be read with
+	the knowledge that file locations may vary a little; even so, the information
+	in this chapter should provide something of value.
+	</para>
+
+	<para>
+	<indexterm><primary>migration</primary></indexterm>
+	Contributions to this chapter were made by Misty Stanley-Jones, a UNIX administrator of many
+	years who surfaced on the Samba mailing list with a barrage of questions and who
+	regularly helps other administrators to solve thorny Samba migration questions.
+	</para>
+
+	<para>
+	<indexterm><primary>NetWare</primary></indexterm>
+	<indexterm><primary>NLM</primary></indexterm>
+	<indexterm><primary>NetWare</primary></indexterm>
+	<indexterm><primary>Mars_NWE</primary></indexterm>
+	One wonders how many NetWare servers remain in active service. Many are being migrated
+	to Samba on Linux. Red Hat Linux, SUSE Linux 9.x, and SUSE Linux Enterprise Server 9 are
+	ideal target platforms to which a NetWare server may be migrated. The migration method
+	of choice is much dependent on the tools that the administrator finds most natural to use.
+	The old-hand NetWare guru will likely want to use tools like the NetWare NLM for
+	<command>rsync</command> to migrate files from the NetWare server to the Samba server.
+	The UNIX administrator might prefer tools that are part of the Mars_NWE (Martin Stovers' NetWare
+	Emulator) open source package. The MS Windows network administrator will likely make use of the
+	NWConv utility that is a part of Windows NT4 Server. Whatever your tool of choice,
+	migration will be filled with joyous and challenging moments &smbmdash; though probably not
+	concurrently.
+	</para>
+
+	<para>
+	The priority that Misty faced was one of migration of the data files off the NetWare 4.11
+	server and onto a Samba-based Windows file and print server. This chapter does not pretend
+	to document all the different methods that could be used to migrate user and group accounts
+	off a NetWare server. Its focus is on migration of data files.
+	</para>
+
+	<para>
+	This chapter tells its own story, so ride along. Maybe the information presented here
+	will help to smooth over a similar migration challenge in your favorite networking environment.
+	</para>
+
+	<para>
+	File paths have been modified to permit use of RPM packages provided by Novell. In the
+	original documentation contributed by Misty, the Courier-IMAP package had been built
+	directly from the original source tarball.
+	</para>
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>
+	<indexterm><primary>Novell</primary></indexterm>
+	Misty Stanley-Jones was recruited by Abmas to administer a network that had
+	not received much attention for some years and was much in need of a makeover.
+	As a brand-new sysadmin to this company, she inherited a very old Novell file server
+	and came with a determination to change things for the better.
+	</para>
+
+	<para>
+	A site survey turned up the following details for the old NetWare server:
+	</para>
+
+	<simplelist>
+		<member><para>200 MHz MMX processor</para></member>
+		<member><para>512K RAM</para></member>
+		<member><para>24 GB disk space in RAID1</para></member>
+		<member><para>Novell 4.11 patched to service pack 7</para></member>
+		<member><para>60+ users</para></member>
+		<member><para>7 network-attached printers</para></member>
+	</simplelist>
+
+	<para>
+	The company had outgrown this server several years before and was dealing with
+	severe growing pains. Some of the problems experienced were:
+	</para>
+		
+	<itemizedlist>
+		<listitem>
+			<para>Very slow performance</para>
+		</listitem>
+		<listitem>
+			<para>Available storage hovering around the 5% range</para>
+			<itemizedlist>
+				<listitem>
+					<para>Extremely slow print spooling.</para>
+				</listitem>
+				<listitem>
+					<para>
+					Users storing information on their local hard
+					drives, causing backup integrity problems
+					</para>
+				</listitem>
+			</itemizedlist>
+		</listitem>
+	  </itemizedlist>
+
+	<para>
+	<indexterm><primary>payroll</primary></indexterm>
+	At one point disk space had filled up to 100 percent, causing the payroll database
+	to become corrupt. This caused the accounting department to be down for over
+	a week and necessitated deployment of another file server. The replacement
+	server was created with very poor security and design considerations from
+	a discarded desktop PC.
+	</para>
+
+	<sect2>
+		<title>Assignment Tasks</title>
+
+	<para>
+	Misty has provided this summary of her migration experience in the hope
+	that it will help someone to avoid the challenges she faced. Perhaps her
+	configuration files and background will accelerate your learning as you
+	grapple with a similar migration challenge. Let there be no confusion,
+	the information presented in this chapter is provided to demonstrate
+	how Misty dealt with a particular NetWare migration requirement, and
+	it provides an overall approach to the implementation of a Samba-3
+	environment that is significantly divergent from that presented in
+	<link linkend="happy"/>.
+	</para>
+
+	<para>
+	The complete removal of all site-specific information in order to produce	
+	a generic migration solution would rob this chapter of its character.
+	It should be recognized, therefore, that the examples given require
+	significant adaptation to suit local needs and thus
+	there are some gaps in the example files. That is not Misty's fault;it
+	is the result of treatment given to her files in an attempt to make
+	the overall information more useful to you.
+	</para>
+
+	<para>
+	<indexterm><primary>cost-benefit</primary></indexterm>
+	After management reviewed a cost-benefit report as well as an estimated
+	time-to-completion, approval was given proceed with the solution proposed.
+	The server was built from purchased components. The total project cost
+	was $3,000. A brief description of the configuration follows:
+	</para>
+
+	<simplelist>
+		<member>
+			<para>3.0 GHz P4 Processor</para>
+		</member>
+		<member>
+			<para>1 GB RAM</para>
+		</member>
+		<member>
+			<para>120 GB SATA operating system drive</para>
+		</member>
+		<member>
+			<para>4 x 80 GB SATA data drives (RAID5 240 GB capacity)</para>
+		</member>
+		<member>
+			<para>2 x 80 GB SATA removable drives for online backup</para>
+		</member>
+		<member>
+			<para>A DLT drive for asynchronous offline backup</para>
+		</member>
+		<member>
+			<para>SUSE Linux Professional 9.1</para>
+		</member>
+	</simplelist>
+
+	<para>
+	The new system has operated for 6 months without problems. Over the past months
+	much attention has been focused on cleaning up desktops and user profiles.
+	</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+	<title>Dissection and Discussion</title>
+
+	<para>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>e-Directory</primary></indexterm>
+	<indexterm><primary>authentication</primary></indexterm>
+	<indexterm><primary>identity management</primary></indexterm>
+	A decision to use LDAP was made even though I knew nothing about LDAP except that
+	I had been reading the book <quote>LDAP System Administration,</quote> by Gerald Carter.
+	LDAP seemed to provide some of the functionality of Novell's e-Directory Services
+	and would provide centralized authentication and identity management.
+	</para>
+
+	<para>
+	<indexterm><primary>database</primary></indexterm>
+	<indexterm><primary>RPM</primary></indexterm>
+	<indexterm><primary>tree</primary></indexterm>
+	Building the LDAP database took a while and a lot of trial and error. Following
+	the guidance I obtained from <quote>LDAP System 
+	Administration,</quote> I installed OpenLDAP (from RPM; later I compiled
+	a more current version from source) and built my initial LDAP tree.
+	</para>
+
+	<sect2>
+	<title>Technical Issues</title>
+
+	<para>
+	<indexterm><primary>white-pages</primary></indexterm>
+	<indexterm><primary>inetOrgPerson</primary></indexterm>
+	<indexterm><primary>OpenLDAP</primary></indexterm>
+	<indexterm><primary>/etc/passwd</primary></indexterm>
+	<indexterm><primary>/etc/shadow</primary></indexterm>
+	<indexterm><primary>LDIF</primary></indexterm>
+	<indexterm><primary>IMAP</primary></indexterm>
+	<indexterm><primary>POP3</primary></indexterm>
+	<indexterm><primary>SMTP</primary></indexterm>
+	The first challenge was to create a company white pages, followed by manually
+	entering everything from the printed company directory. This used only the inetOrgPerson
+	object class from the OpenLDAP schemas. The next step was to write a shell script that
+	would look at the <filename>/etc/passwd</filename> and <filename>/etc/shadow</filename>
+	files on our mail server and create an LDIF file from which the information could be
+	imported into LDAP. This would allow use of LDAP for Linux authentication, IMAP, POP3,
+	and SMTP.
+	</para>
+
+	<para>
+	Because a decision was made to use Courier-IMAP the schema <quote>authldap.schema</quote>
+	from the Courier-IMAP source, tarball is necessary to resolve Courier-specific LDAP directory
+	needs. Where the Courier-IMAP file provided by SUSE is used, this file is named
+	<filename>courier.schema</filename>.
+	</para>
+
+	<para>
+	Looking back, it would have been much easier to populate the LDAP directory using a convenient
+	tool such as <command>phpLDAPAdmin</command> from the outset. An excessive amount of time was
+	spent trying to generate LDIF files that could be parsed using the <command>ldapmodify</command>
+	so that necessary changes could be written to the directory. This was a learning experience!
+	</para>
+
+	<para>
+	An attempt was made to use the PADL POSIX account migration scripts, but I gave up trying to
+	make them work. Instead, even though it is most inelegant, I wrote a simple script that did
+	what I needed. It is enclosed as a simple example to demonstrate that you do not need to be
+	a guru to make light of otherwise painful repetition. This file is listed in <link linkend="sbeamg"/>.
+	</para>
+
+<example id="sbeamg">
+<title>A Rough Tool to Create an LDIF File from the System Account Files</title>
+<screen>
+#!/bin/bash
+
+cat /etc/passwd | while read l; do
+  uid=`echo $l | cut -d : -f 1`
+  uidNumber=`echo $l | cut -d : -f 3`
+  gidNumber=`echo $1 | cut -d : -f 4`
+  gecos=`echo $l | cut -d : -f 5`
+  homeDirectory=`echo $l | cut -d : -f 6`
+  loginShell=`echo $l | cut -d : -f 6`
+  userPassword=`cat /etc/shadow | grep $uid | cut -d : -f 2`
+
+  echo "dn: cn=$gecos,ou=people,dc=mycompany,dc=com"
+  echo "objectClass: account"
+  echo "objectClass: posixAccount"
+  echo "cn: $gecos"
+  echo "uid: $uid"
+  echo "uidNumber: $uidNumber"
+  echo "gidNumber: $gidNumber"
+  echo "homeDirectory: $homeDirectory"
+  echo "loginShell: $loginShell"
+  echo "userPassword: $userPassword"
+done
+</screen>
+</example>
+
+	<note><para>
+	
+	The PADL MigrationTools are recommended for migration of the UNIX account information into
+	the LDAP directory. The tools consist of a set of Perl scripts for migration of users, groups,
+	aliases, hosts, netgroups, networks, protocols, PRCs, and services from the existing ASCII text
+	files (or from a name service such as NIS). This too set can be obtained from the <ulink url=
+	"http://www.padl.com">PADL Web site</ulink>.
+	</para></note>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Implementation</title>
+
+	<para>
+	</para>
+
+	<sect2>
+	<title>NetWare Migration Using LDAP Backend</title>
+
+	<para>
+	The following software must be installed on the SUSE Linux Enterprise Server to perform
+	this migration:
+	</para>
+
+	<simplelist>
+		<member><para>courier-imap</para></member>
+		<member><para>courier-imap-ldap</para></member>
+		<member><para>nss_ldap</para></member>
+		<member><para>openldap2-client</para></member>
+		<member><para>openldap2-devel (only for Samba compilation)</para></member>
+		<member><para>openldap2</para></member>
+		<member><para>pam_ldap</para></member>
+		<member><para>samba-3.0.20 or later</para></member>
+		<member><para>samba-client-3.0.20 or later</para></member>
+		<member><para>samba-winbind-3.0.20 or later</para></member>
+		<member><para>smbldap-tools Version 0.9.1</para></member>
+	</simplelist>
+
+	<para>
+	Each software application must be carefully configured in preparation for migration.
+	The configuration files used at Abmas are provided as a guide and should be modified
+	to meet needs at your site.
+	</para>
+
+	<sect3>
+	<title>LDAP Server Configuration</title>
+
+	<para>
+	The <filename>/etc/openldap/slapd.conf</filename> file Misty used is shown here:
+<programlisting>
+#/etc/openldap/slapd.conf
+#
+# See slapd.conf(5) for details on configuration options.
+# This file should NOT be world readable.
+#
+include   /etc/openldap/schema/core.schema
+include   /etc/openldap/schema/cosine.schema
+include   /etc/openldap/schema/inetorgperson.schema
+include   /etc/openldap/schema/nis.schema
+include   /etc/openldap/schema/samba3.schema
+include   /etc/openldap/schema/dhcp.schema
+include   /etc/openldap/schema/misc.schema
+include   /etc/openldap/schema/idpool.schema
+include   /etc/openldap/schema/eduperson.schema
+include   /etc/openldap/schema/commURI.schema
+include   /etc/openldap/schema/local.schema
+include   /etc/openldap/schema/courier.schema
+
+pidfile   /var/run/slapd/run/slapd.pid
+argsfile  /var/run/slapd/run/slapd.args
+
+replogfile  /data/ldap/log/slapd.replog
+
+# Load dynamic backend modules:
+modulepath  /usr/lib/openldap/modules
+
+#######################################################################
+# Logging parameters
+#######################################################################
+loglevel 256
+
+#######################################################################
+# SASL and TLS options
+#######################################################################
+sasl-host     ldap.corp.abmas.org
+sasl-realm    DIGEST-MD5
+sasl-secprops   none
+TLSCipherSuite HIGH:MEDIUM:+SSLV2
+TLSCertificateFile    /etc/ssl/certs/private/abmas-cert.pem
+TLSCertificateKeyFile /etc/ssl/certs/private/abmas-key.pem
+password-hash   {SSHA}
+defaultsearchbase "dc=abmas,dc=biz"
+
+#######################################################################
+# bdb database definitions
+#######################################################################
+database          bdb
+suffix            "dc=abmas,dc=biz"
+rootdn            "cn=manager,dc=abmas,dc=biz"
+rootpw            {SSHA}gdo/dUvoT4ZJmULz3rUt6A3H/hBEduJ5
+directory         /data/ldap
+mode    0600
+# The following is for BDB to make it flush its data to disk every
+# 500 seconds or 5kb of data
+checkpoint 500 5
+
+## For running slapindex
+#readonly on
+
+## Indexes for often-requested attributes
+index   objectClass             eq
+index   cn                      eq,sub
+index   sn                      eq,sub
+index   uid                     eq,sub
+index   uidNumber               eq
+index   gidNumber               eq
+index   sambaSID                eq
+index   sambaPrimaryGroupSID    eq
+index   sambaDomainName         eq
+index   default                 sub
+cachesize 2000
+
+replica         host=baa.corp.abmas.org:389
+                suffix="dc=abmas,dc=biz"
+                binddn="cn=replica,dc=abmas,dc=biz"
+                credentials=verysecret
+                bindmethod=simple
+                tls=yes
+replica         host=ns.abmas.org:389
+                suffix="dc=abmas,dc=biz"
+                binddn="cn=replica,dc=abmas,dc=biz"
+                credentials=verysecret
+                bindmethod=simple
+                tls=yes
+
+#######################################################################
+# ACL section
+#######################################################################
+## MOST RESTRICTIVE RULES MUST GO FIRST!
+# Admins get access to everything. This way I do not have to rename.
+access to *
+  by group/groupOfUniqueNames/uniqueMember="cn=LDAP
+Administrators,ou=groups,dc=abmas,dc=biz" write
+  by * break
+
+## Users can change their own passwords. 
+access to 
+attrs=userPassword,sambaNTPassword,sambaLMPassword,sambaPwdLastSet,
+sambaPwdMustChange,sambaPwdCanChange
+  by self write
+  by * auth
+
+## Home contact info restricted to the logged-in user and the HR dept
+access to attrs=hometelephoneNumber,homePostalAddress,
+mobileTelephoneNumber,pagerTelephoneNumber
+  by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
+ou=groups,dc=abmas,dc=biz" 
+write
+  by self write
+  by * none
+
+## Everyone can read email aliases
+access to dn.sub="ou=Email Aliases,dc=abmas,dc=biz"
+  by * read
+
+## Only admins can manage email aliases
+## If someone is the role occupant of an alias they can change it -- this
+## is accomplished by the "organizationalRole" objectclass and is
+## pretty cool -- like a groupOfUniqueNames but for individual
+## users.
+access to dn.children="ou=Email Aliases,dc=abmas,dc=biz"
+  by dnattr=roleOccupant write
+  by * read
+
+## Admins and HR can add and delete users
+access to dn.sub="ou=people,dc=abmas,dc=biz"
+  by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
+ou=groups,dc=abmas,dc=biz" 
+write
+  by * read
+
+## Admins and HR can add and delete bizputers
+access to dn.sub="ou=bizputers,dc=abmas,dc=biz"
+  by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
+ou=groups,dc=abmas,dc=biz" 
+write
+  by * read
+
+## Admins and HR can add and delete groups
+access to dn.sub="ou=groups,dc=abmas,dc=biz"
+  by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
+ou=groups,dc=abmas,dc=biz" 
+write
+  by * read
+
+## This is used to quickly deactivate any LDAP object only 
+##  Admins have access.
+access to dn.sub="ou=inactive,dc=abmas,dc=biz"
+  by * none
+
+## This is for programs like Windows Address Book that can 
+## detect the default search base.
+access to attrs=namingcontexts,supportedControl
+  by anonymous =cs
+  by * read
+
+## Default to read-only access
+access to *
+  by dn.base="cn=replica,ou=people,dc=abmas,dc=biz" write
+  by * read
+</programlisting>
+</para>
+
+	<para>
+	<indexterm><primary>/etc/ldap.conf</primary></indexterm>
+	The <filename>/etc/ldap.conf</filename> file used is listed in <link linkend="ch8ldap"/>.
+	</para>
+
+<example id="ch8ldap">
+<title>NSS LDAP Control File &smbmdash; /etc/ldap.conf</title>
+<screen>
+# /etc/ldap.conf
+# This file is present on every *NIX client that authenticates to LDAP.
+# For me, most of the defaults are fine. There is an amazing amount of
+# customization that can be done see the man page for info.
+
+# Your LDAP server. Must be resolvable without using LDAP. The following
+# is for the LDAP server all others use the FQDN of the server
+URI ldap://127.0.0.1
+
+# The distinguished name of the search base.
+base ou=corp,dc=abmas,dc=biz
+
+# The LDAP version to use (defaults to 3 if supported by client library)
+ldap_version 3
+
+# The distinguished name to bind to the server with if the effective
+# user ID is root. Password is stored in /etc/ldap.secret (mode 600)
+rootbinddn cn=Manager,dc=abmas,dc=biz
+
+# Filter to AND with uid=%s
+pam_filter objectclass=posixAccount
+
+# The user ID attribute (defaults to uid)
+pam_login_attribute uid
+
+# Group member attribute
+pam_member_attribute memberUID
+
+# Use the OpenLDAP password change
+# extended operation to update the password.
+pam_password exop
+
+# OpenLDAP SSL mechanism
+# start_tls mechanism uses the normal LDAP port, LDAPS typically 636
+ssl start_tls
+
+tls_cacertfile /etc/ssl/certs/private/abmas-cert.pem
+...
+</screen>
+</example>
+
+	<para>
+	The NSS control file <filename>/etc/nsswitch.conf</filename> has the following contents:
+<screen>
+# /etc/nsswitch.conf
+# This file controls the resolve order for system databases.
+
+# the following two lines obviate the "+" entry in /etc/passwd and /etc/group.
+passwd:   compat ldap
+group:    compat ldap
+# The above are all that I store in LDAP at this point. There are 
+# possibilities to store hosts, services, ethers, and lots of other things.
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>PAM</primary></indexterm>
+	<indexterm><primary>NSS</primary></indexterm>
+	In my setup, users authenticate via PAM and NSS using LDAP-based accounts.
+	The configuration file that controls the behavior of the PAM <command>pam_unix2</command>
+	module is shown in <link linkend="sbepu2"/> file.
+	This works out of the box with the configuration files in this chapter. It
+	enables you to have no local accounts for users (it is highly advisable 
+	to have a local account for the root user).  Traps for the unwary include the following:
+	</para>
+
+<example id="sbepu2">
+<title>The PAM Control File <filename>/etc/security/pam_unix2.conf</filename></title>
+<screen>
+# pam_unix2 config file
+#
+# This file contains options for the pam_unix2.so module.
+# It contains a list of options for every type of management group,
+# which will be used for authentication, account management and
+# password management. Not all options will be used from all types of
+# management groups.
+#
+# At first, pam_unix2 will read this file and then uses the local
+# options. Not all options can be set her global.
+#
+# Allowed options are:
+#
+# debug                 (account, auth, password, session)
+# nullok                (auth)
+# md5                   (password / overwrites /etc/default/passwd)
+# bigcrypt              (password / overwrites /etc/default/passwd)
+# blowfish              (password / overwrites /etc/default/passwd)
+# crypt_rounds=XX
+# none                  (session)
+# trace                 (session)
+# call_modules=x,y,z    (account, auth, password)
+#
+#  Example:
+#  auth:        nullok
+#  account:
+#  password:    nullok blowfish crypt_rounds=8
+#  session:     none
+#
+auth: use_ldap
+account: use_ldap
+password: use_ldap
+session: none
+</screen>
+</example>
+
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>authenticate</primary></indexterm>
+	<indexterm><primary>DNS</primary></indexterm>
+	<itemizedlist>
+		<listitem>
+			<para>
+			If your LDAP database goes down, nobody can authenticate except for root.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para>
+			If failover is configured incorrectly, weird behavior can occur. For example, 
+			DNS can fail to resolve.
+			</para>
+		</listitem>
+	</itemizedlist>
+
+	<para>
+	I do have two LDAP slave servers configured. That subject is beyond the scope
+	of this document, and steps for implementing it are well documented.
+	</para>
+
+	<para>
+	The following services authenticate using LDAP:
+	</para>
+	<indexterm><primary>UNIX</primary></indexterm>
+	<indexterm><primary>Postfix</primary></indexterm>
+	<indexterm><primary>Courier-IMAP</primary></indexterm>
+	<simplelist>
+		<member><para>UNIX login/ssh</para></member>
+		<member><para>Postfix (SMTP)</para></member>
+		<member><para>Courier-IMAP/IMAPS/POP3/POP3S</para></member>
+	</simplelist>
+
+	<para>
+	<indexterm><primary>white-pages</primary></indexterm>
+	<indexterm><primary>Windows Address Book</primary></indexterm>
+	Companywide white pages can be searched using an LDAP client
+	such as the one in the Windows Address Book.
+	</para>
+
+	<para>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>smbldap-tools</primary></indexterm>
+	Having gained a solid understanding of LDAP and a relatively workable LDAP tree
+	thus far, it was time to configure Samba. I compiled the latest stable Samba and
+	also installed the latest <command>smbldap-tools</command> from 
+	<ulink url="http://idealx.com">Idealx</ulink>.
+	</para>
+
+	<para>
+	The Samba &smb.conf; file was configured as shown in <link linkend="ch8smbconf"/>.
+	</para>
+
+<example id="ch8smbconf">
+<title>Samba Configuration File &smbmdash; smb.conf Part A</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MEGANET2</smbconfoption>
+<smbconfoption name="netbios name">MASSIVE</smbconfoption>
+<smbconfoption name="server string">Corp File Server</smbconfoption>
+<smbconfoption name="passdb backend">ldapsam:ldap://localhost</smbconfoption>
+<smbconfoption name="pam password change">Yes</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="log level">1</smbconfoption>
+<smbconfoption name="log file">/data/samba/log/%m.log</smbconfoption>
+<smbconfoption name="name resolve order">wins host bcast</smbconfoption>
+<smbconfoption name="time server">Yes</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="cups options">Raw</smbconfoption>
+<smbconfoption name="add user script">/opt/IDEALX/sbin/smbldap-useradd -m "%u"</smbconfoption>
+<smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd -p "%g"</smbconfoption>
+<smbconfoption name="add user to group script">/opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"</smbconfoption>
+<smbconfoption name="delete user from group script">/opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"</smbconfoption>
+<smbconfoption name="set primary group script">/opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"</smbconfoption>
+<smbconfoption name="add machine script">/usr/local/sbin/smbldap-useradd -w "%m"</smbconfoption>
+<smbconfoption name="logon script">logon.bat</smbconfoption>
+<smbconfoption name="logon path">\\%L\profiles\%U\%a</smbconfoption>
+<smbconfoption name="logon drive">H:</smbconfoption>
+<smbconfoption name="logon home">\\%L\%U</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="wins support">Yes</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
+<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap passwd sync">Yes</smbconfoption>
+<smbconfoption name="ldap suffix">ou=MEGANET2,dc=abmas,dc=biz</smbconfoption>
+<smbconfoption name="ldap ssl">no</smbconfoption>
+<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+<smbconfoption name="admin users">root, "@Domain Admins"</smbconfoption>
+<smbconfoption name="printer admin">"@Domain Admins"</smbconfoption>
+<smbconfoption name="force printername">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch8smbconf2">
+<title>Samba Configuration File &smbmdash; smb.conf Part B</title>
+<smbconfblock>
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">Network logon service</smbconfoption>
+<smbconfoption name="path">/data/samba/netlogon</smbconfoption>
+<smbconfoption name="write list">"@Domain Admins"</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+
+<smbconfsection name="[profiles]"/>
+<smbconfoption name="comment">Roaming Profile Share</smbconfoption>
+<smbconfoption name="path">/data/samba/profiles/</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="profile acls">Yes</smbconfoption>
+<smbconfoption name="veto files">desktop.ini</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="create mask">0770</smbconfoption>
+<smbconfoption name="veto files">desktop.ini</smbconfoption>
+<smbconfoption name="hide files">desktop.ini</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[software]"/>
+<smbconfoption name="comment">Software for %a computers</smbconfoption>
+<smbconfoption name="path">/data/samba/shares/software/%a</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+
+<smbconfsection name="[public]"/>
+<smbconfoption name="comment">Public Files</smbconfoption>
+<smbconfoption name="path">/data/samba/shares/public</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+
+<smbconfsection name="[PDF]"/>
+<smbconfoption name="comment">Location of documents printed to PDFCreator printer</smbconfoption>
+<smbconfoption name="path">/data/samba/shares/pdf</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch8smbconf3">
+<title>Samba Configuration File &smbmdash; smb.conf Part C</title>
+<smbconfblock>
+<smbconfsection name="[EVERYTHING]"/>
+<smbconfoption name="comment">All shares</smbconfoption>
+<smbconfoption name="path">/data/samba</smbconfoption>
+<smbconfoption name="valid users">"@Domain Admins"</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[CDROM]"/>
+<smbconfoption name="comment">CD-ROM on MASSIVE</smbconfoption>
+<smbconfoption name="path">/mnt</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+
+<smbconfsection name="[print$]"/>
+<smbconfoption name="comment">Printer Drivers Share</smbconfoption>
+<smbconfoption name="path">/data/samba/drivers</smbconfoption>
+<smbconfoption name="write list">root</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="path">/data/samba/spool</smbconfoption>
+<smbconfoption name="create mask">0644</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[acct_hp8500]"/>
+<smbconfoption name="comment">"Accounting Color Laser Printer"</smbconfoption>
+<smbconfoption name="path">/data/samba/spool/private</smbconfoption>
+<smbconfoption name="valid users">@acct, @acct_admin, @hr, "@Domain Admins",@Receptionist, dwayne, terri, danae, jerry</smbconfoption>
+<smbconfoption name="create mask">0644</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="copy">printers</smbconfoption>
+
+<smbconfsection name="[plotter]"/>
+<smbconfoption name="comment">Engineering Plotter</smbconfoption>
+<smbconfoption name="path">/data/samba/spool</smbconfoption>
+<smbconfoption name="create mask">0644</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="copy">printers</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch8smbconf4">
+<title>Samba Configuration File &smbmdash; smb.conf Part D</title>
+<smbconfblock>
+<smbconfsection name="[APPS]"/>
+<smbconfoption name="path">/data/samba/shares/Apps</smbconfoption>
+<smbconfoption name="force group">"Domain Users"</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[ACCT]"/>
+<smbconfoption name="path">/data/samba/shares/Accounting</smbconfoption>
+<smbconfoption name="valid users">@acct, "@Domain Admins"</smbconfoption>
+<smbconfoption name="force group">acct</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="create mask">0660</smbconfoption>
+<smbconfoption name="directory mask">0770</smbconfoption>
+
+<smbconfsection name="[ACCT_ADMIN]"/>
+<smbconfoption name="path">/data/samba/shares/Acct_Admin</smbconfoption>
+<smbconfoption name="valid users">@”acct_admin”</smbconfoption>
+<smbconfoption name="force group">acct_admin</smbconfoption>
+
+<smbconfsection name="[HR_PR]"/>
+<smbconfoption name="path">/data/samba/shares/HR_PR</smbconfoption>
+<smbconfoption name="valid users">@hr, @acct_admin</smbconfoption>
+<smbconfoption name="force group">hr</smbconfoption>
+
+<smbconfsection name="[ENGR]"/>
+<smbconfoption name="path">/data/samba/shares/Engr</smbconfoption>
+<smbconfoption name="valid users">@engr, @receptionist, @truss, "@Domain Admins", cheri</smbconfoption>
+<smbconfoption name="force group">engr</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="create mask">0770</smbconfoption>
+
+<smbconfsection name="[DATA]"/>
+<smbconfoption name="path">/data/samba/shares/DATA</smbconfoption>
+<smbconfoption name="valid users">@engr, @receptionist, @truss, "@Domain Admins", cheri</smbconfoption>
+<smbconfoption name="force group">engr</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="create mask">0770</smbconfoption>
+<smbconfoption name="copy">engr</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="ch8smbconf5">
+<title>Samba Configuration File &smbmdash; smb.conf Part E</title>
+<smbconfblock>
+<smbconfsection name="[X]"/>
+<smbconfoption name="path">/data/samba/shares/X</smbconfoption>
+<smbconfoption name="valid users">@engr, @acct</smbconfoption>
+<smbconfoption name="force group">engr</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="create mask">0770</smbconfoption>
+<smbconfoption name="copy">engr</smbconfoption>
+
+<smbconfsection name="[NETWORK]"/>
+<smbconfoption name="path">/data/samba/shares/network</smbconfoption>
+<smbconfoption name="valid users">"@Domain Users"</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="create mask">0770</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+
+<smbconfsection name="[UTILS]"/>
+<smbconfoption name="path">/data/samba/shares/Utils</smbconfoption>
+<smbconfoption name="write list">"@Domain Admins"</smbconfoption>
+
+<smbconfsection name="[SYS]"/>
+<smbconfoption name="path">/data/samba/shares/SYS</smbconfoption>
+<smbconfoption name="valid users">chad</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+	<para>
+	<indexterm><primary>Qbasic</primary></indexterm>
+	<indexterm><primary>Rbase</primary></indexterm>
+	<indexterm><primary>drive letters</primary></indexterm>
+	Most of these shares are only used by one company group, but they are required
+	because of some ancient Qbasic and Rbase applications were that written expecting
+	their own drive letters.
+	</para>
+
+	<para>
+	<indexterm><primary>rsync</primary></indexterm>
+	<indexterm><primary>rsyncd.conf</primary></indexterm>
+	<indexterm><primary>synchronize</primary></indexterm>
+	Note: During the process of building the new server, I kept data files
+	up to date with the Novell server via use of <command>rsync</command>. 
+	On a separate system (my workstation in fact), which could be rebooted
+	whenever necessary, I set up a mount point to the Novell server via
+	<command>ncpmount</command>. I then created a
+	<filename>rsyncd.conf</filename> to share that mount point out to my
+	new server, and synchronized once an hour. The script I used to synchronize
+	is shown in <link linkend="sbersync"/>. The files exclusion list I used
+	is shown in <link linkend="sbexcld"/>.  The reason I had to have the
+	<command>rsync</command> daemon running on a system that could be
+	rebooted frequently is because <constant>ncpfs</constant>
+	(part of the MARS NetWare Emulation package) has a nasty habit of creating stale
+	mount points that cannot be recovered without a reboot. The reason for hourly
+	synchronization is because some part of the chain was very slow and
+	performance-heavy (whether <command>rsync</command> itself, the network,
+	or the Novell server, I am not sure, but it was probably the Novell server).
+	</para>
+
+<example id="sbersync">
+<title>Rsync Script</title>
+<screen>
+#!/bin/bash
+# Part 1 - rsync the Novell directories to the new server
+echo "#############################################"
+echo "New sync operation starting at `date`"
+if ! pgrep -fl '^rsync\&gt; ; then
+        echo "Good, no rsync is running!"
+  echo "Synchronizing oink to BHPRO"
+        rsync -av --exclude-from=/root/excludes.txt 
+baa.corp:/BHPRO/SYS1/ /data/samba/shares/SYS1
+        retval=$?
+        [ ${retval} = 0 ] &amp;&amp; echo "Sync operation completed at `date`"
+        echo "Fixing permissions"
+        # I had a whole lot more permission-fixing stuff here.  It got
+        # pared down as groups got moved over.  The problem
+        # was that the way I was mounting the directory, everything
+        # was owned by the Novell administrator which translated to
+        # Root.  This is also why I could only do one-way sync because
+        # I could not fix the ACLs on the Novell side.
+        find /data/samba/shares/Engr/ -perm +770 -exec chmod 770 {} \;
+        find /data/samba/shares/Engr/ ! -group engr -exec chgrp engr {} \;
+else
+        # This rsync took ages and ages -- I had it set to run every hour but
+        # I needed a way to prevent it running into itself.
+        echo "Oh no, rsync is already running!"
+echo "#############################################"
+fi
+</screen>
+</example>
+
+<example id="sbexcld">
+<title>Rsync Files Exclusion List &smbmdash; <filename>/root/excludes.txt</filename></title>
+<screen>
+/Acct/
+/Apps/
+/DATA/
+/Engr/*.pc3
+/Engr/plotter
+/Engr/APPOLO/
+/Engr/LIBRARY/
+/Home/Accounting/
+/Home/Angie/
+/Home/AngieY/
+/Home/Brandon/
+/Home/Carl/
+</screen>
+</example>
+
+	<para>
+	After Samba was configured, I initialized the LDAP database. The first
+	thing I had to do was store the LDAP password in the Samba configuration by
+	issuing the command (as root):
+<screen>
+&rootprompt; smbpasswd -w verysecret
+</screen>
+	where <quote>verysecret</quote> is replaced by the LDAP bind password.
+	</para>
+
+<note><para>
+The Idealx smbldap-tools package can be configured using a script called 
+<command>configure.pl</command> that is provided as part of the tool. See <link linkend="happy"/>
+for an example of its use. Many administrators, like Misty, choose to do this manually
+so as to maintain greater awareness of how the tool-chain works and possibly to avoid
+undesirable actions from occurring unnoticed.
+</para></note>
+
+	<para>
+	Now Samba was ready for use and it was time to configure the smbldap-tools. There are two
+	relevant files, which are usually put into the directory
+	<filename>/etc/smbldap-tools</filename>. The main file,
+	<filename>smbldap.conf</filename> is shown in <link linkend="ch8ideal"/>.
+	</para>
+
+<example id="ch8ideal">
+<title>Idealx smbldap-tools Control File &smbmdash; Part A</title>
+<screen>
+#########
+#
+# located in /etc/smbldap-tools/smbldap.conf
+#
+######################################################################
+#
+# General Configuration
+#
+######################################################################
+
+# Put your own SID
+# to obtain this number do: net getlocalsid
+SID="S-1-5-21-725326080-1709766072-2910717368"
+
+######################################################################
+#
+# LDAP Configuration
+#
+######################################################################
+
+# Notes: to use to dual ldap servers backend for Samba, you must patch
+# Samba with the dual-head patch from IDEALX. If not using this patch
+# just use the same server for slaveLDAP and masterLDAP.
+# Those two servers declarations can also be used when you have
+# . one master LDAP server where all writing operations must be done
+# . one slave LDAP server where all reading operations must be done
+#   (typically a replication directory)
+
+# Ex: slaveLDAP=127.0.0.1
+slaveLDAP="127.0.0.1"
+slavePort="389"
+
+# Master LDAP : needed for write operations
+# Ex: masterLDAP=127.0.0.1
+masterLDAP="127.0.0.1"
+masterPort="389"
+
+# Use TLS for LDAP
+# If set to 1, this option will use start_tls for connection
+# (you should also used the port 389)
+ldapTLS="0"
+
+# How to verify the server's certificate (none, optional or require)
+# see "man Net::LDAP" in start_tls section for more details
+verify=""
+</screen>
+</example>
+
+<example id="ch8ideal2">
+<title>Idealx smbldap-tools Control File &smbmdash; Part B</title>
+<screen>
+# CA certificate
+# see "man Net::LDAP" in start_tls section for more details
+cafile=""
+ certificate to use to connect to the ldap server
+# see "man Net::LDAP" in start_tls section for more details
+clientcert=""
+
+# key certificate to use to connect to the ldap server
+# see "man Net::LDAP" in start_tls section for more details
+clientkey=""
+
+# LDAP Suffix
+# Ex: suffix=dc=IDEALX,dc=ORG
+suffix="ou=MEGANET2,dc=abmas,dc=biz"
+
+# Where are stored Users
+# Ex: usersdn="ou=Users,dc=IDEALX,dc=ORG"
+usersdn="ou=People,${suffix}"
+
+# Where are stored Computers
+# Ex: computersdn="ou=Computers,dc=IDEALX,dc=ORG"
+computersdn="ou=People,${suffix}"
+
+# Where are stored Groups
+# Ex groupsdn="ou=Groups,dc=IDEALX,dc=ORG"
+groupsdn="ou=Groups,${suffix}"
+
+# Where are stored Idmap entries
+# (used if samba is a domain member server)
+# Ex groupsdn="ou=Idmap,dc=IDEALX,dc=ORG"
+idmapdn="ou=Idmap,${suffix}"
+
+# Where to store next uidNumber and gidNumber available
+sambaUnixIdPooldn="sambaDomainName=MEGANET2,${suffix}"
+
+# Default scope Used
+scope="sub"
+</screen>
+</example>
+
+<example id="ch8ideal3">
+<title>Idealx smbldap-tools Control File &smbmdash; Part C</title>
+<screen>
+# Unix password encryption (CRYPT, MD5, SMD5, SSHA, SHA)
+hash_encrypt="MD5"
+
+# if hash_encrypt is set to CRYPT, you may set a salt format.
+# default is "%s", but many systems will generate MD5 hashed
+# passwords if you use "$1$%.8s". This parameter is optional!
+crypt_salt_format="%s"
+
+######################################################################
+#
+# Unix Accounts Configuration
+#
+######################################################################
+
+# Login defs
+# Default Login Shell
+# Ex: userLoginShell="/bin/bash"
+userLoginShell="/bin/false"
+
+# Home directory
+# Ex: userHome="/home/%U"
+userHome="/home/%U"
+
+# Gecos
+userGecos="Samba User"
+
+# Default User (POSIX and Samba) GID
+defaultUserGid="513"
+
+# Default Computer (Samba) GID
+defaultComputerGid="515"
+
+# Skel dir
+skeletonDir="/etc/skel"
+
+# Default password validation time (time in days) Comment the next
+# line if you don't want password to be enable for
+# defaultMaxPasswordAge days (be careful to the sambaPwdMustChange
+# attribute's value)
+defaultMaxPasswordAge="45"
+</screen>
+</example>
+
+<example id="ch8ideal4">
+<title>Idealx smbldap-tools Control File &smbmdash; Part D</title>
+<screen>
+######################################################################
+#
+# SAMBA Configuration
+#
+######################################################################
+
+# The UNC path to home drives location (%U username substitution)
+# Ex: \\My-PDC-netbios-name\homes\%U
+# Just set it to a null string if you want to use the smb.conf
+# 'logon home' directive and/or disable roaming profiles
+userSmbHome=""
+
+# The UNC path to profiles locations (%U username substitution)
+# Ex: \\My-PDC-netbios-name\profiles\%U
+# Just set it to a null string if you want to use the smb.conf
+# 'logon path' directive and/or disable roaming profiles
+userProfile=""
+
+# The default Home Drive Letter mapping
+# (will be automatically mapped at logon time if home directory exist)
+# Ex: H: for H:
+userHomeDrive=""
+
+# The default user netlogon script name (%U username substitution)
+# if not used, will be automatically username.cmd
+# make sure script file is edited under DOS
+# Ex: %U.cmd
+# userScript="startup.cmd" # make sure script file is edited under DOS
+userScript=""
+
+# Domain appended to the users "mail"-attribute
+# when smbldap-useradd -M is used
+mailDomain="abmas.org"
+
+######################################################################
+#
+# SMBLDAP-TOOLS Configuration (default are ok for a RedHat)
+#
+######################################################################
+# Allows not to use smbpasswd
+# (if with_smbpasswd == 0 in smbldap_conf.pm) but
+# prefer Crypt::SmbHash library
+with_smbpasswd="0"
+smbpasswd="/usr/bin/smbpasswd"
+</screen>
+</example>
+
+	<para>
+	<indexterm><primary>TLS</primary></indexterm>
+	Note: I chose not to take advantage of the TLS capability of this. 
+	Eventually I may go back and tweak it.  Also, I chose not to take advantage
+	of the master/slave configuration as I heard horror stories that it was
+	unstable.  My slave servers are replicas only.
+	</para>
+
+	<para>
+	The <filename>/etc/smbldap-tools/smbldap_bind.conf</filename> file is shown here:
+<screen>
+# smbldap_bind.conf
+#
+# This file simply tells smbldap-tools how to bind to your LDAP server.
+# It has to be a DN with full write access to the Samba portion of
+# the database.
+
+############################
+# Credential Configuration #
+############################
+# Notes: you can specify two different configurations if you use a
+# master ldap for writing access and a slave ldap server for reading access
+# By default, we will use the same DN (so it will work for standard Samba
+# release)
+slaveDN="cn=Manager,dc=abmas,dc=biz"
+slavePw="verysecret"
+masterDN="cn=Manager,dc=abmas,dc=biz"
+masterPw="verysecret"
+</screen>
+	</para>
+
+	<para>
+	The next step was to run the <command>smbldap-populate</command> command, which populates
+	the LDAP tree with the appropriate default users, groups, and UID and GID pools.
+	It creates a user called Administrator with UID=0 and GID=0 matching the
+	Domain Admins group. This is fine because you can still log on as root to a Windows system,
+	but it will break cached credentials if you need to log on as the administrator
+	to a system that is not on the network.
+	</para>
+
+	<para>
+	After the LDAP database has been preloaded, it is prudent to validate that the
+	information needed is in the LDAP directory. This can be done done by restarting
+	the LDAP server, then performing an LDAP search by executing:
+<screen>
+&rootprompt; ldapsearch -W -x -b "dc=abmas,dc=biz"\
+	 -D "cn=Manager,dc=abmas,dc=biz" \
+	"(Objectclass=*)"
+Enter LDAP Password:
+# extended LDIF
+#
+# LDAPv3
+# base &lt;dc=abmas,dc=biz&gt; with scope sub
+# filter: (ObjectClass=*)
+# requesting: ALL
+#
+
+# abmas.biz
+dn: dc=abmas,dc=biz
+objectClass: dcObject
+objectClass: organization
+o: abmas
+dc: abmas
+
+# People, abmas.biz
+dn: ou=People,dc=abmas,dc=biz
+objectClass: organizationalUnit
+ou: People
+
+# Groups, abmas.biz
+dn: ou=Groups,dc=abmas,dc=biz
+objectClass: organizationalUnit
+ou: Groups
+
+# Idmap, abmas.biz
+dn: ou=Idmap,dc=abmas,dc=biz
+objectClass: organizationalUnit
+ou: Idmap
+...
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>Windows</primary></indexterm>
+	<indexterm><primary>POSIX</primary></indexterm>
+	<indexterm><primary>smbldap-groupadd</primary></indexterm>
+	<indexterm><primary>RID</primary></indexterm>
+	<indexterm><primary>sambaGroupMapping</primary></indexterm>
+	With the LDAP directory now initialized, it was time to create the Windows and POSIX
+	(UNIX) group accounts as well as the mappings from Windows groups to UNIX groups.
+	The easiest way to do this was to use <command>smbldap-groupadd</command> command.
+	It creates the group with the posixGroup and sambaGroupMapping attributes, a
+	unique GID, and an automatically determined RID. I learned the hard way not to
+	try to do this by hand.
+	</para>
+
+	<para>
+	<indexterm><primary>group mapping</primary></indexterm>
+	<indexterm><primary>smbldap-groupmod</primary></indexterm>
+	<indexterm><primary>memberUID</primary></indexterm>
+	After I had my group mappings in place, I added users to the groups (the users
+	don't really have to exist yet). I used the <command>smbldap-groupmod</command>
+	command to accomplish this. It can also be done manually by adding memberUID
+	attributes to the group entries in LDAP.
+	</para>
+
+	<para>
+	<indexterm><primary>sambaSamAccount</primary></indexterm>
+	<indexterm><primary>posixAccount</primary></indexterm>
+	<indexterm><primary>smbldap-usermod</primary></indexterm>
+	The most monumental task of all was adding the sambaSamAccount information to each
+	already existent posixAccount entry.  I did it one at a time as I moved people onto
+	the new server, by issuing the command:
+<screen>
+&rootprompt; smbldap-usermod -a -P username
+</screen>
+	<indexterm><primary>NetWare</primary></indexterm>
+	<indexterm><primary>LDIF</primary></indexterm>
+	<indexterm><primary>slapcat</primary></indexterm>
+	I completed that step for every user after asking the person what his or her current
+	NetWare password was. The wiser way to have done it would probably have been to dump the
+	entire database to an LDIF file. This can be done by executing:
+<screen>
+&rootprompt; slapcat &gt; somefile.ldif
+</screen>
+	<indexterm><primary>Perl</primary></indexterm>
+	<indexterm><primary>objectClass</primary></indexterm>
+	Then update the LDIF file created by using a Perl script to parse and add the
+	appropriate attributes and objectClasses to each entry, followed by re-importing
+	the entire database into the LDAP directory. 
+	</para>
+
+	<para>
+	Rebuilding of the LDAP directory can be done as follows:
+<screen>
+&rootprompt; rcldap stop
+&rootprompt; cd /data/ldap
+&rootprompt; rm *bdb _* log*
+&rootprompt; su - ldap -c "slapadd -l somefile.ldif"
+&rootprompt; rcldap start
+</screen>
+	This can be done at any time and for any reason, with no harm to the database.
+	</para>
+
+	<para>
+	I first added a test user, of course. The LDIF for this test user looks like
+	this, to give you an idea:
+<screen>
+# Entry 1: cn=Test User,ou=people,ou=corp,dc=abmas,dc=biz
+dn:cn=Test User,ou=people,ou=corp,dc=abmas,dc=biz
+cn: Test User
+gecos: Test User
+gidNumber: 513
+givenName: Test
+homeDirectory: /home/test.user
+homePhone: 555
+l: Somewhere
+l: ST
+mail: test.user
+o: Corp
+objectClass: top
+objectClass: inetOrgPerson
+objectClass: posixAccount
+objectClass: sambaSamAccount
+postalCode: 12345
+sn: User
+street: 10 Some St.
+uid: test.user
+uidNumber: 1074
+sambaLogonTime: 0
+sambaLogoffTime: 2147483647
+sambaKickoffTime: 2147483647
+sambaPwdCanChange: 0
+displayName: Samba User
+sambaSID: S-1-5-21-725326080-1709766072-2910717368-3148
+sambaLMPassword: 9D29C287C58448F9AAD3B435B51404EE
+sambaAcctFlags: [U]
+sambaNTPassword: D062088E99C95E37D7702287BB35E770
+sambaPwdLastSet: 1102537694
+sambaPwdMustChange: 1106425694
+userPassword: {SSHA}UzFZ2VxRGdwUueLnTGtsTBtnsvMO1oj8
+loginShell: /bin/false
+</screen>
+	</para>
+
+	<para>
+	Then I went over to a spare Windows NT machine and joined it to the MEGANET2 domain.
+	It worked, and the machine's account entry under ou=Computers looks like this:
+<screen>
+dn:uid=w2kengrspare$,ou=Computers,ou=MEGANET2,dc=abmas,dc=biz
+objectClass: top
+objectClass: inetOrgPerson
+objectClass: posixAccount
+objectClass: sambaSamAccount
+cn: w2kengrspare$
+sn: w2kengrspare$
+uid: w2kengrspare$
+uidNumber: 1104
+gidNumber: 515
+homeDirectory: /dev/null
+loginShell: /bin/false
+description: Computer
+gecos: Computer
+sambaSID: S-1-5-21-725326080-1709766072-2910717368-3208
+sambaPrimaryGroupSID: S-1-5-21-725326080-1709766072-2910717368-2031
+displayName: W2KENGRSPARE$
+sambaPwdCanChange: 1103149236
+sambaPwdMustChange: 2147483647
+sambaNTPassword: CA199C45CB6737035DB6D9D9F6CD1834
+sambaPwdLastSet: 1103149236
+sambaAcctFlags: [W          ]
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>netlogon</primary></indexterm>
+	So now I could log on with a test user from the machine w2kengrspare. It was all well and
+	good, but that user was in no groups yet and so had pretty boring access.  I fixed that
+	by writing the login script! To write the login script, I used
+	<ulink url="http://www.kixtart.org">Kixtart</ulink> because it will work
+	with every architecture of Windows, has an active and helpful user base, and was both
+	easier to learn and more powerful than the standard netlogon scripts I have seen.
+	I also did not have to do a logon script per user or per group.
+	</para>
+
+	<para>
+	<indexterm><primary>Kixtart</primary></indexterm>
+	I downloaded Kixtart and put the following files in my netlogon share:
+<screen>
+KIX32.EXE
+KX32.dll
+KX95.dll  &lt;-- Not needed unless you are running Win9x clients.
+kx16.dll  &lt;-- Probably not needed unless you are running DOS clients.
+kxrpc.exe &lt;-- Probably useless as it has to run on the server and can
+          only be run on NT.  It's for Windows 95 to become group-aware.
+          We can get around the need.
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>logon.kix</primary></indexterm>
+	I then wrote the <filename>logon.kix</filename> file that is shown in
+	<link linkend="ch8kix"/>. I chose to keep it all in one file, but it
+	can be split up and linked via include directives.
+	</para>
+
+<example id="ch8kix">
+<title>Kixtart Control File &smbmdash; File: logon.kix</title>
+<screen>
+; This script just calls the other scripts.
+
+; First we want to get things done for everyone.
+
+; Second, we do first-time login stuff.
+
+; Third, we go through the group-oriented scripts one at a time.
+
+
+; We want to check for group membership here to avoid the overhead of running
+; scripts which don't apply.
+call "\\massive\netlogon\scripts\main.kix"
+call "\\massive\netlogon\scripts\setup.kix"
+IF INGROUP("MEGANET2\ACCT")
+  call "scripts\acct.kix"
+ENDIF
+IF INGROUP("MEGANET2\ENGR","MEGANET2\RECEPTIONIST")
+call "\\massive\netlogon\scripts\engr.kix"
+ENDIF
+IF INGROUP("MEGANET2\FURN")
+  call "\\massive\netlogon\scripts\furn.kix"
+ENDIF
+IF INGROUP("MEGANET2\TRUSS")
+  call "\\massive\netlogon\scripts\truss.kix"
+ENDIF
+</screen>
+</example>
+
+<example id="ch8kix2">
+<title>Kixtart Control File &smbmdash; File: main.kix</title>
+<screen>
+break on
+
+; Choose whether to hide the login window or not
+IF INGROUP("MEGANET2\Domain Admins")
+  USE Z: \\massive\everything
+  SETCONSOLE("show")
+ELSE
+  ; Nobody cares about seeing the login script except admins
+  SETCONSOLE("hide")
+ENDIF
+
+; Delete all previously connected shares
+USE * /delete
+
+SETTITLE("Logging on @USERID to @LDOMAIN at @TIME")
+
+; Set the time on the workstation
+$Timeserver = "\\massive"
+Settime $TimeServer
+
+; Map the home directory
+USE H: @HOMESHR ; connect to user's home share
+IF @ERROR = 0
+
+  H:
+  CD @HOMEDIR ; change directory to user's home directory
+ENDIF
+
+; Everyone gets the N drive
+USE N: \\massive\network
+</screen>
+</example>
+
+<example id="ch8kix3">
+<title>Kixtart Control File &smbmdash; File: setup.kix, Part A</title>
+<screen>
+; My setup.kix is where all of the redirection stuff happens.  Note that with 
+; the use of registry keys, this only happens the first time they log in ,or if 
+; I delete the pertinent registry keys which triggers it to happen again:
+
+; Check to see if we have written the abmas sub-key before
+$RETURNCODE = EXISTKEY("HKEY_CURRENT_USER\abmas")
+IF NOT $RETURNCODE = 0
+; Add key for abmas-specific things on the first login
+  ADDKEY("HKEY_CURRENT_USER\abmas")
+  ; The following key gets deleted at the end of the first login
+  ADDKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
+ENDIF
+
+; People with laptops need My Documents to be in their profile.  People with
+; desktops can have My Documents redirected to their home directory to avoid
+; long delays with logging out and out-of-sync files.
+
+; Check to see if this is the first login -- doesn't make sense to do this
+; at the very first login
+
+$RETURNCODE = EXISTKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
+IF NOT $RETURNCODE = 0
+
+; We don't want to do this stuff for people with laptops or people in the FURN
+; group.  (They store their profiles in a different server)
+
+  IF NOT INGROUP("MASSIVE\Laptop","MASSIVE\FURN")
+    $RETURNCODE=EXISTKEY("HKEY_CURRENT_USER\abmas\profile_copied")
+
+; A  crude way to tell what OS our profile is for and copy the "My Documents"
+; to the redirected folder on the server.  It works because the profiles
+; are stored as \\server\profiles\user\architecture
+    IF NOT $RETURNCODE = 0
+      IF EXIST("\\massive\profiles\@userID\WinXP")
+        copy "\\massive\profiles\@userID\WinXP\My Documents\*" 
+"\\massive\@userID\"
+      ENDIF
+      IF EXIST("\\massive\profiles\@userID\Win2K")
+        copy "\\massive\profiles\@userID\Win2K\My Documents\*" 
+"\\massive\@userID\"
+      ENDIF
+      IF EXIST("\\massive\profiles\@userID\WinNT")
+        copy "\\massive\profiles\@userID\WinNT\My Documents\*" 
+"\\massive\@userID\"
+      ENDIF
+</screen>
+</example>
+
+<example id="ch8kix3b">
+<title>Kixtart Control File &smbmdash; File: setup.kix, Part B</title>
+<screen>
+; Now we will write the registry values to redirect the locations of "My 
+Documents"
+; and other folders.
+      ADDKEY("HKEY_CURRENT_USER\abmas\profile_copied")
+      WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
+Windows\CurrentVersion\Explorer\User 
+Shell Folders", "Personal","\\massive\@userID","REG_SZ")
+      WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
+Windows\CurrentVersion\Explorer\User 
+Shell Folders", "My Pictures", "\\massive\@userID\My Pictures", "REG_SZ")
+      IF @PRODUCTTYPE="Windows 2000 Professional" or @PRODUCTTYPE="Windows XP
+Professional"
+      WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
+Windows\CurrentVersion\Explorer\User 
+Shell Folders", "My Videos", "\\massive\@userID\My Videos", "REG_SZ")
+      WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
+Windows\CurrentVersion\Explorer\User 
+Shell Folders", "My Music", "\\massive\@userID\My Music", "REG_SZ")
+      WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
+Windows\CurrentVersion\Explorer\User 
+Shell Folders", "My eBooks", "\\massive\@userID\My eBooks", "REG_SZ")
+      ENDIF
+    ENDIF
+  ENDIF
+
+; Now we will delete the FIRST_LOGIN sub-key that we made before.
+; Note - to run this script again you will want to delete the HKCU\abmas
+; sub-key, log out, and log back in.
+$RETURNVALUE = EXISTKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
+IF $RETURNVALUE = 0
+  DELKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
+ENDIF
+</screen>
+</example>
+
+<example id="ch8kix4">
+<title>Kixtart Control File &smbmdash; File: acct.kix</title>
+<screen>
+; And here is one group-oriented script to show what can be
+; done that way: acct.kix:
+
+IF INGROUP("MASSIVE\Acct_Admin","MASSIVE\HR")
+  USE I: \\MEGANET2\HR_PR
+ENDIF
+
+; Set up printer
+$RETURNVALUE = existkey("HKEY_CURRENT_USER\Printers\,,massive,acct_hp8500")
+IF NOT $RETURNVALUE = 0
+  ADDPRINTERCONNECTION("\\massive\acct_hp8500")
+  SETDEFAULTPRINTER("\\massive\acct_hp8500")
+ENDIF
+; Set up drive mappings
+  USE M: \\massive\ACCT
+  IF INGROUP("MEGANET2\ABRA")
+    USE T: \\trussrv\abra
+  ENDIF
+</screen>
+</example>
+
+	<para>
+	As you can see in the script, I redirected the My Documents to the user's home
+	share if he or she were not in the Laptop group. I also added printers on a
+	group-by-group basis, and if applicable I set the group printer. For this to
+	be effective, the print drivers must be installed on the Samba server in the
+	<filename>[print$]</filename> share. Ample documentation exists about how to
+	do that, so it is not covered here.
+	</para>
+
+	<para>
+	I call this script via the logon.bat script in the [netlogon] directory:
+<screen>
+\\corpsrv\netlogon\kix32 \\corpsrv\netlogon\logon.kix /f
+</screen>
+	I only had to fully qualify the paths for Windows 9x, as Windows NT and
+	greater automatically add [NETLOGON] to the path.
+	</para>
+
+	<para>
+	Also of note for Win9x is that the drive mappings and printer setup will not
+	work because they rely on RPC. You merely have to put the appropriate settings
+	into the <filename>c:\autoexec.bat</filename> file or map the drives manually.
+	One option is to check the OS as part of the Kixtart script, and if it
+	is Win9x and is the first login, copy a premade
+	<filename>autoexec.bat</filename> to the <filename>C:</filename> drive. I
+	have only three such machines, and one is going away in the very near future,
+	so it was easier to do it by hand.
+	</para>
+
+	<para>
+	<indexterm><primary>upgrade</primary></indexterm>
+	At this point I was able to add the users. This is the part that really falls
+	into upgrade. I moved the users over one group at a time, starting with the
+	people who used the least amount of resources on the network. With each group
+	that I moved, I first logged on as a standard user in that group and took
+	careful note of the environment, mainly the printers he or she used, the PATH,
+	and what network resources he or she had access to (most importantly, which ones
+	the user actually needed access to).
+	</para>
+
+	<para>
+	I then added the user's SambaSamAccount information as mentioned earlier,
+	and join the computer to the domain. The very first thing I had to do was to
+	copy the user's profile to the new server. This was very important, and I really
+	struggled with the most effective way to do it.  Here is the method that worked
+	for every one of my users on Windows NT, 2000, and XP:
+	</para>
+
+	<procedure>
+		<step><para>
+			Log in as the user on the domain. This creates the local copy
+			of the user's profile and copies it to the server as he or she logs out.
+		</para></step>
+
+		<step><para>
+			Reboot the computer and log in as the local machine administrator.
+		</para></step>
+
+		<step><para>
+			Right-click My Computer, click Properties, and navigate to the
+			user profiles tab (varies per version of Windows).
+		</para></step>
+
+		<step><para>
+			Select the user's local profile <constant>(COMPUTERNAME\username)</constant>,
+			and click the <command>Copy To</command> button.
+		</para></step>
+
+		<step><para>
+			In the next dialog, copy it directly to the profiles share on the
+			Samba server (in my case \\PDCname\profiles\user\&lt;architecture&gt;.
+			You will have had to make a connection to the share as that
+			user (e.g., Windows Explorer type \\PDCname\profiles\username).
+		</para></step>
+
+		<step><para>
+			When the copy is complete (it can take a while) log out, and log back in
+			as the user. All of his or her settings and all contents of My Documents,
+			Favorites, and the registry should have been copied successfully.
+		</para></step>
+
+		<step><para>
+			If it doesn't look right (the dead giveaway is the desktop background),
+			shut down the computer without logging out (power cycle) and try logging
+			in as the user again. If it still doesn't work, repeat the steps above.
+			I only had to ever repeat it once.
+		</para></step>
+
+	</procedure>
+
+	<para>
+	Words to the Wise:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+			If the user was anything other than a standard user on his or her system
+			before, you will save yourself some headaches by giving him or her identical
+			permissions (on the local machine) as his or her domain account <emphasis>before</emphasis>
+			copying the profile over. Do this through the User Administrator
+			in the Control Panel, after joining the computer to the domain and
+			before logging on as that user for the first time. Otherwise the user will
+			have trouble with permissions on his or her registry keys.
+		</para></listitem>
+
+		<listitem><para>
+			If any application was installed for the user only, rather than for
+			the entire system, it will probably not work without being reinstalled.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	After all these steps are accomplished, only cleanup details are left. Make sure user's
+	shortcuts and Network Places point to the appropriate place on the new server, check
+	the important applications to be sure they work as expected and troubleshoot any problems
+	that might arise, and check to be sure the user's printers are present and working. By the
+	way, if there are any network printers installed as system printers (the Novell way),
+	you will need to log in as a local administrator and delete them.
+	</para>
+
+	<para>
+	For my non-laptop systems, I would then log in and out a couple times as the user
+	to be sure that his or her registry settings were modified, and then I was finished.
+	</para>
+
+	<para>
+	Some compatibility issues that cropped up included the following:
+	</para>
+
+	<para>
+	Blackberry client: It did not like having its registry settings moved around
+	and so had to be reinstalled. Also, it needed write permissions to a portion of
+	the hard drive, and I had to give it those manually on the one system where
+	this was an issue.
+	</para>
+
+	<para>
+	CAMedia: Digital camera software for Canon cameras caused all kinds of trouble
+	with the registry. I had to use the Run as service to open the registry of
+	the local user while logged in as the domain user, and give the domain user
+	the appropriate permissions to some registry keys, then export that portion
+	of the registry to a file. Then, as the domain user, I had to import that file
+	into the registry.
+	</para>
+
+	<para>
+	Crystal Reports version 7: More registry problems that were solved by recopying
+	the user's profile.
+	</para>
+
+	<para>
+	Printing from legacy applications: I found out that Novell sends its jobs to
+	the printer in a raw format. CUPS sends them in PostScript by default. I had
+	to make a second printer definition for one printer and tell CUPS specifically
+	to send raw data to the printer, then assign this printer to the LPT port with
+	Kixtart's version of the net use command.
+	</para>
+
+	<para>
+	These were all eventually solved by elbow grease, queries to the Samba mailing
+	list and others, and diligence. The complete migration took about 5 weeks.
+	My userbase is relatively small but includes multiple versions of Windows,
+	multiple Linux member servers, a mechanized saw, a pen plotter, and legacy
+	applications written in Qbasic and R:Base, just to name a few. I actually
+	ended up making some of these applications work better (or work again, as
+	some of them had stopped functioning on the old server) because as part of
+	the process I had to find out how things were supposed to work.
+	</para>
+
+	<para>
+	The one thing I have not been able to get working is a very old database that
+	we had around for reference purposes; it uses Novell's Btrieve engine.
+	</para>
+
+	<para>
+	As the resources compare, I went from 95 percent disk usage to just around 10 percent.
+	I went from a very high load on the server to an average load of between one
+	and two runnable processes on the server. I have improved the security and
+	robustness of the system. I have also implemented
+	<ulink url="http://www.clamav.net">ClamAV</ulink> antivirus software,
+	which scans the entire Samba server for viruses every 2 hours and
+	quarantines them. I have found it much less problematic than our ancient
+	version of Norton Antivirus Corporate Edition, and much more up-to-date.
+	</para>
+
+	<para>
+	In short, my users are much happier now that the new server is running, and that
+	is what is important to me.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-SecureOfficeServer.xml b/docs-xml/Samba3-ByExample/SBE-SecureOfficeServer.xml
new file mode 100644
index 00000000000..e03c0106b07
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-SecureOfficeServer.xml
@@ -0,0 +1,2693 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="secure">
+  <title>Secure Office Networking</title>
+
+	<para>
+	Congratulations, your Samba networking skills are developing nicely. You started out
+	with three simple networks in <link linkend="simple"/>, and then in <link linkend="small"/>
+	you designed and built a network that provides a high degree of flexibility, integrity,
+	and dependability. It was enough for the basic needs each was designed to fulfill. In
+	this chapter you address a more complex set of needs. The solution you explore 
+	introduces you to basic features that are specific to Samba-3.
+	</para>
+
+	<para>
+	You should note that a working and secure solution could be implemented using Samba-2.2.x. 
+	In the exercises presented here, you are gradually using more Samba-3-specific features,
+	so caution is advised for anyone who tries to use Samba-2.2.x with the guidance here given. 
+	To avoid confusion, this book is all about Samba-3. Let's get the exercises in this 
+	chapter underway.
+	</para>
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>
+	You have made Mr. Meany a very happy man. Recently he paid you a fat bonus for work 
+	well done. It is one year since the last network upgrade. You have been quite busy. 
+	Two months ago Mr. Meany gave approval to hire Christine Roberson, who has taken over 
+	general network management. Soon she will provide primary user support. You have
+	demonstrated that you can delegate responsibility and can plan and execute according
+	to that plan. Above all, you have shown Mr. Meany that you are a responsible person.
+	Today is a big day. Mr. Meany called you to his office at 9 a.m. for news you never 
+	expected: You are going to take charge of business operations. Mr. Meany 
+	is retiring and has entrusted the business to your capable hands. 
+	</para>
+
+	<para>
+	Mr. Meany may be retiring from this company, but not from work. He is taking the
+	opportunity to develop Abmas Accounting into a larger and more substantial company.
+	He says that it took him many years to learn that there is no future in just running
+	a business. He now realizes there is great personal satisfaction in the creation of
+	career opportunities for people in the local community. He wants to do more for others,
+	as he is doing for you. Today he spent a lot of time talking about his grand plan
+	for growth, which you will deal with in the chapters ahead.
+	</para>
+
+	<para>
+	Over the past year, the growth projections were exceeded. The network has grown to
+	meet the needs of 130 users. Along with growth, the demand for improved services
+	and better functionality has also developed. You are about to make an interim
+	improvement and then hand over all Help desk and network maintenance to Christine.
+	Christine has professional certifications in Microsoft Windows as well as in Linux;
+	she is a hard worker and quite likable. Christine does not want to manage the department
+	(although she manages well). She gains job satisfaction when left to sort things out.
+	Occasionally she wants to work with you on a challenging problem. When you told her
+	about your move, she almost resigned, although she was reassured that a new manager would
+	be hired to run Information Technology, and she would be responsible only for operations.
+	</para>
+
+	<sect2>
+		<title>Assignment Tasks</title>
+
+		<para>
+		You promised the staff Internet services including Web browsing, electronic mail, virus
+		protection, and a company Web site.  Christine is eager to help turn the vision into 
+		reality. Let's see how close you can get to the promises made.
+		</para>
+
+		<para>
+		The network you are about to deliver will service 130 users today. Within a year,
+		Abmas will aquire another company. Mr. Meany claims that within 2 years there will be
+		well over 500 users on the network. You have bought into the big picture, so prepare 
+		for growth.  You have purchased a new server and will implement a new network infrastructure. 
+		</para>
+
+		<para>
+		You have decided to not recycle old network components. The only items that will be
+		carried forward are notebook computers. You offered staff new notebooks, but not 
+		one person wanted the disruption for what was perceived as a marginal update. 
+		You decided to give everyone, even the notebook user, a new desktop computer.
+		</para>
+
+		<para>
+		You procured a DSL Internet connection that provides 1.5 Mb/sec (bidirectional)
+		and a 10 Mb/sec ethernet port. You registered the domain
+		<constant>abmas.us</constant>, and the Internet Service Provider (ISP) is supplying
+		secondary DNS. Information furnished by your ISP is shown in <link linkend="chap4netid"/>.
+		</para>
+
+		<para>
+		It is of paramount priority that under no circumstances will Samba offer
+		service access from an Internet connection. You are paying an ISP to
+		give, as part of its value-added services, full firewall protection for your
+		connection to the outside world. The only services allowed in from
+		the Internet side are the following destination ports: <constant>http/https (ports 
+		80 and 443), email (port 25), DNS (port 53)</constant>. All Internet traffic
+		will be allowed out after network address translation (NAT). No internal IP addresses
+		are permitted through the NAT filter because complete privacy of internal network
+		operations must be assured.
+		</para>
+
+		<table id="chap4netid">
+			<title>Abmas.US ISP Information</title>
+			<tgroup cols="2">
+				<colspec align="left"/>
+				<colspec align="center"/>
+				<thead>
+					<row>
+						<entry>Parameter</entry>
+						<entry>Value</entry>
+					</row>
+				</thead>
+				<tbody>
+					<row>
+						<entry>Server IP Address</entry>
+						<entry>123.45.67.66</entry>
+					</row>
+					<row>
+						<entry>DSL Device IP Address</entry>
+						<entry>123.45.67.65</entry>
+					</row>
+					<row>
+						<entry>Network Address</entry>
+						<entry>123.45.67.64/30</entry>
+					</row>
+					<row>
+						<entry>Gateway Address</entry>
+						<entry>123.45.54.65</entry>
+					</row>
+					<row>
+						<entry>Primary DNS Server</entry>
+						<entry>123.45.54.65</entry>
+					</row>
+					<row>
+						<entry>Secondary DNS Server</entry>
+						<entry>123.45.54.32</entry>
+					</row>
+					<row>
+						<entry>Forwarding DNS Server</entry>
+						<entry>123.45.12.23</entry>
+					</row>
+				</tbody>
+			</tgroup>
+		</table>
+
+		<figure id="ch04net">
+			<title>Abmas Network Topology &smbmdash; 130 Users</title>
+			<imagefile scale="65">chap4-net</imagefile>
+		</figure>
+
+		<para>
+		Christine recommended that desktop systems should be installed from a single cloned
+		master system that has a minimum of locally installed software and loads all software
+		off a central application server. The benefit of having the central application server
+		is that it allows single-point maintenance of all business applications, a more
+		efficient way to manage software.  She further recommended installation of antivirus 
+		software on workstations as well as on the Samba server. Christine knows the dangers
+		of potential virus infection and insists on a comprehensive approach to detective
+		as well as corrective action to protect network operations.
+		</para>
+
+		<para>
+		A significant concern is the problem of managing company growth. Recently, a number 
+		of users had to share a PC while waiting for new machines to arrive. This presented 
+		some problems with desktop computers and software installation into the new users' 
+		desktop profiles.
+		</para>
+		
+	</sect2>
+</sect1>
+
+<sect1>
+	<title>Dissection and Discussion</title>
+
+	<para>
+	Many of the conclusions you draw here are obvious. Some requirements are not very clear
+	or may simply be your means of drawing the most out of Samba-3. Much can be done more simply
+	than you will demonstrate here, but keep in mind that the network must scale to at least 500
+	users. This means that some functionality will be overdesigned for the current 130-user
+	environment.
+	</para>
+
+	<sect2>
+		<title>Technical Issues</title>
+
+		<para>
+		In this exercise we use a 24-bit subnet mask for the two local networks. This,
+		of course, limits our network to a maximum of 253 usable IP addresses. The network
+		address range chosen is one assigned by RFC1918 for private networks.
+		When the number of users on the network begins to approach the limit of usable
+		addresses, it is a good idea to switch to a network address specified in RFC1918
+		in the 172.16.0.0/16 range. This is done in subsequent chapters.
+		</para>
+
+		<para>
+		<indexterm><primary>tdbsam</primary></indexterm>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		The high growth rates projected are a good reason to use the <constant>tdbsam</constant>
+		passdb backend. The use of <constant>smbpasswd</constant> for the backend may result in
+		performance problems. The <constant>tdbsam</constant> passdb backend offers features that
+		are not available with the older, flat ASCII-based <constant>smbpasswd</constant> database.
+		</para>
+
+		<para>
+		<indexterm><primary>risk</primary></indexterm>
+		The proposed network design uses a single server to act as an Internet services host for
+		electronic mail, Web serving, remote administrative access via SSH, 
+		Samba-based file and print services. This design is often chosen by sites that feel 	
+		they cannot afford or justify the cost or overhead of having separate servers. It must 
+		be realized that if security of this type of server should ever be violated (compromised), 
+		the whole network and all data is at risk. Many sites continue to choose this type 
+		of solution; therefore, this chapter provides detailed coverage of key implementation 
+		aspects.
+		</para>
+
+		<para>
+		Samba will be configured to specifically not operate on the Ethernet interface that is
+		directly connected to the Internet.
+		</para>
+
+		<para>
+		<indexterm><primary>iptables</primary></indexterm>
+		<indexterm><primary>NAT</primary></indexterm>
+		<indexterm><primary>Network Address Translation</primary><see>NAT</see></indexterm>
+		<indexterm><primary>firewall</primary></indexterm>
+		You know that your ISP is providing full firewall services, but you cannot rely on that.
+		Always assume that human error will occur, so be prepared by using Linux firewall facilities
+		based on <command>iptables</command> to effect NAT. Block all
+		incoming traffic except to permitted well-known ports. You must also allow incoming packets
+		to establish outgoing connections. You will permit all internal outgoing requests.
+		</para>
+
+		<para>
+		The configuration of Web serving, Web proxy services, electronic mail, and the details of
+		generic antivirus handling are beyond the scope of this book and therefore are not
+		covered except insofar as this affects Samba-3.
+		</para>
+
+		<para>
+		<indexterm><primary>login</primary></indexterm>
+		Notebook computers are configured to use a network login when in the office and a
+		local account to log in while away from the office. Users store all work done in
+		transit (away from the office) by using a local share for work files. Standard procedures
+		dictate that on completion of the work that necessitates mobile file access, all
+		work files are moved back to secure storage on the office server. Staff is instructed
+		to not carry on any company notebook computer any files that are not absolutely required.
+		This is a preventative measure to protect client information as well as private business
+		records.
+		</para>
+
+		<para>
+		<indexterm><primary>application server</primary></indexterm>
+		All applications are served from the central server from a share called <constant>apps</constant>.
+		Microsoft Office XP Professional and OpenOffice 1.1.0 will be installed using a network 
+		(or administrative) installation. Accounting and financial management software can also
+		be run only from the central application server. Notebook users are provided with
+		locally installed applications on a need-to-have basis only.
+		</para>
+
+		<para>
+		<indexterm><primary>roaming profiles</primary></indexterm>
+		The introduction of roaming profiles support means that users can move between
+		desktop computer systems without constraint while retaining full access to their data.
+		The desktop travels with them as they move.
+		</para>
+
+		<para>
+		<indexterm><primary>DNS</primary></indexterm>
+		The DNS server implementation must now address both internal and external
+		needs. You forward DNS lookups to your ISP-provided server as well as the 
+		<constant>abmas.us</constant> external secondary DNS server.
+		</para>
+
+		<para>
+		<indexterm><primary>dynamic DNS</primary></indexterm>
+		<indexterm><primary>DDNS</primary><see>dynamic DNS</see></indexterm>
+		<indexterm><primary>DHCP server</primary></indexterm>
+		Compared with the DHCP server configuration in <link linkend="small"/>, <link linkend="dhcp01"/>, the 
+		configuration used in this example has to deal with the presence of an Internet connection.
+		The scope set for it ensures that no DHCP services will be offered on the external
+		connection. All printers are configured as DHCP clients so that the DHCP server assigns
+		the printer a fixed IP address by way of the Ethernet interface (MAC) address. One additional
+		feature of this DHCP server configuration file is the inclusion of parameters to allow dynamic
+		DNS (DDNS) operation.
+		</para>
+
+		<para>
+		This is the first implementation that depends on a correctly functioning DNS server.
+		Comprehensive steps are included to provide for a fully functioning DNS server that also
+		is enabled for DDNS operation. This means that DHCP clients can be autoregistered
+		with the DNS server.
+		</para>
+
+		<para>
+		You are taking the opportunity to manually set the netbios name of the Samba server to
+		a name other than what will be automatically resolved. You are doing this to ensure that
+		the machine has the same NetBIOS name on both network segments.
+		</para>
+
+		<para>
+		As in the previous network configuration, printing in this network configuration uses
+		direct raw printing (i.e., no smart printing and no print driver autodownload to Windows
+		clients). Printer drivers are installed on the Windows client manually. This is not
+		a problem because Christine is to install and configure one single workstation and
+		then clone that configuration, using Norton Ghost, to all workstations. Each machine is
+		identical, so this should pose no problem.
+		</para>
+
+		<sect3>
+		<title>Hardware Requirements</title>
+
+		<para>
+		<indexterm><primary>memory requirements</primary></indexterm>
+		This server runs a considerable number of services. From similarly configured Linux
+		installations, the approximate calculated memory requirements are as shown in
+		<link linkend="ch4memoryest"/>.
+
+<example id="ch4memoryest">
+<title>Estimation of Memory Requirements</title>
+<screen>
+Application  Memory per User    130 Users      500 Users
+   Name        (MBytes)       Total MBytes   Total MBytes
+-----------  ---------------  ------------   ------------
+DHCP              2.5               3              3
+DNS              16.0              16             16
+Samba (nmbd)     16.0              16             16
+Samba (winbind)  16.0              16             16
+Samba (smbd)      4.0             520           2000
+Apache           10.0 (20 User)   200            200
+CUPS              3.5              16             32
+Basic OS        256.0             256            256
+                              -------------- --------------
+    Total:                       1043 MBytes    2539 MBytes
+                              -------------- --------------
+</screen>
+</example>
+		You should add a safety margin of at least 50% to these estimates. The minimum 
+		system memory recommended for initial startup 1 GB, but to permit the system
+		to scale to 500 users, it makes sense to provision the machine with 4 GB memory.
+		An initial configuration with only 1 GB memory would lead to early performance complaints
+		as the system load builds up. Given the low cost of memory, it does not make sense to
+		compromise in this area.
+		</para>
+
+		<para>
+		<indexterm><primary>bandwidth calculations</primary></indexterm>
+		Aggregate input/output loads should be considered for sizing network configuration as 
+		well as disk subsystems. For network bandwidth calculations, one would typically use an
+		estimate of 0.1 MB/sec per user. This suggests that 100-Base-T (approx. 10 MB/sec)
+		would deliver below acceptable capacity for the initial user load. It is therefore a good
+		idea to begin with 1 Gb Ethernet cards for the two internal networks, each attached
+		to a 1 Gb Ethernet switch that provides connectivity to an expandable array of 100-Base-T
+		switched ports.
+		</para>
+
+		<para>
+		<indexterm><primary>network segments</primary></indexterm>
+		<indexterm><primary>RAID</primary></indexterm>
+		Considering the choice of 1 Gb Ethernet interfaces for the two local network segments,
+		the aggregate network I/O capacity will be 2100 Mb/sec (about 230 MB/sec), an I/O
+		demand that would require a fast disk storage I/O capability. Peak disk throughput is 
+		limited by the disk subsystem chosen. It is desirable to provide the maximum 
+		I/O bandwidth affordable. If a low-cost solution must be chosen, 
+		3Ware IDE RAID Controllers are a good choice. These controllers can be fitted into a 
+		64-bit, 66 MHz PCI-X slot. They appear to the operating system as a high-speed SCSI 
+		controller that can operate at the peak of the PCI-X bandwidth (approximately 450 MB/sec).
+		Alternative SCSI-based hardware RAID controllers should also be considered. Alternately,
+		it makes sense to purchase well-known, branded hardware that has appropriate performance
+		specifications. As a minimum, one should attempt to provide a disk subsystem that can
+		deliver I/O rates of at least 100 MB/sec. 
+		</para>
+
+		<para>
+		Disk storage requirements may be calculated as shown in <link linkend="ch4diskest"/>.
+
+<example id="ch4diskest">
+<title>Estimation of Disk Storage Requirements</title>
+<screen>
+Corporate Data: 100 MBytes/user per year
+Email Storage:  500 MBytes/user per year
+Applications:   5000 MBytes
+Safety Buffer:  At least 50%
+
+Given 500 Users and 2 years:
+-----------------------------
+        Corporate Data:  2 x 100 x 500 = 100000 MBytes = 100 GBytes
+        Email Storage:   2 x 500 x 500 = 500000 MBytes = 500 GBytes
+        Applications:                      5000 MBytes =   5 GBytes
+                                       ----------------------------
+                             Total:                      605 GBytes
+             Add 50% buffer                              303 GBytes
+                       Recommended Storage:              908 GBytes
+</screen>
+</example>
+		<indexterm><primary>storage capacity</primary></indexterm>
+		The preferred storage capacity should be approximately 1 Terabyte. Use of RAID level 5
+		with two hot spare drives would require an 8-drive by 200 GB capacity per drive array.
+		</para>
+
+		</sect3>
+
+	</sect2>
+
+
+	<sect2>
+		<title>Political Issues</title>
+
+		<para>
+		Your industry is coming under increasing accountability pressures. Increased paranoia
+		is necessary so you can demonstrate that you have acted with due diligence. You must
+		not trust your Internet connection.
+		</para>
+
+		<para>
+		Apart from permitting more efficient management of business applications through use of
+		an application server, your primary reason for the decision to implement this is that it
+		gives you greater control over software licensing.
+		</para>
+
+		<para>
+		<indexterm><primary>Outlook Express</primary></indexterm>
+		You are well aware that the current configuration results in some performance issues
+		as the size of the desktop profile grows. Given that users use Microsoft Outlook
+		Express, you know that the storage implications of the <constant>.PST</constant> file
+		is something that needs to be addressed later.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Implementation</title>
+
+	<para>
+	<link linkend="ch04net"/> demonstrates the overall design of the network that you will implement.
+	</para>
+
+	<para>
+	The information presented here assumes that you are already familiar with many basic steps.
+	As this stands, the details provided already extend well beyond just the necessities of
+	Samba configuration. This decision is deliberate to ensure that key determinants
+	of a successful installation are not overlooked. This is the last case that documents
+	the finite minutiae of DHCP and DNS server configuration. Beyond the information provided
+	here, there are many other good reference books on these subjects.
+	</para>
+
+	<para>
+	The &smb.conf; file has the following noteworthy features:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		The NetBIOS name of the Samba server is set to <constant>DIAMOND</constant>.
+		</para></listitem>
+
+		<listitem><para>
+		The Domain name is set to <constant>PROMISES</constant>.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>broadcast messages</primary></indexterm>
+		<indexterm><primary>interfaces</primary></indexterm>
+		<indexterm><primary>bind interfaces only</primary></indexterm>
+		Ethernet interface <constant>eth0</constant> is attached to the Internet connection
+		and is externally exposed. This interface is explicitly not available for Samba to use.
+		Samba listens on this interface for broadcast messages but does not broadcast any
+		information on <constant>eth0</constant>, nor does it accept any connections from it.
+		This is achieved by way of the <parameter>interfaces</parameter> parameter and the
+		<parameter>bind interfaces only</parameter> entry.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>passdb backend</primary></indexterm>
+		<indexterm><primary>tdbsam</primary></indexterm>
+		<indexterm><primary>binary database</primary></indexterm>
+		The <parameter>passdb backend</parameter> parameter specifies the creation and use
+		of the <constant>tdbsam</constant> password backend. This is a binary database that
+		has excellent scalability for a large number of user account entries.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>WINS serving</primary></indexterm>
+		<indexterm><primary>wins support</primary></indexterm>
+		<indexterm><primary>name resolve order</primary></indexterm>
+		WINS serving is enabled by the <smbconfoption name="wins support">Yes</smbconfoption>,
+		and name resolution is set to use it by means of the
+		<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption> entry.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>time server</primary></indexterm>
+		The Samba server is configured for use by Windows clients as a time server.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>CUPS</primary></indexterm>
+		<indexterm><primary>printing</primary></indexterm>
+		<indexterm><primary>printcap name</primary></indexterm>
+		Samba is configured to directly interface with CUPS via the direct internal interface
+		that is provided by CUPS libraries. This is achieved with the 
+		<smbconfoption name="printing">CUPS</smbconfoption> as well as the
+		<smbconfoption name="printcap name">CUPS</smbconfoption> entries.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>user management</primary></indexterm>
+		<indexterm><primary>group management</primary></indexterm>
+		<indexterm><primary>SRVTOOLS.EXE</primary></indexterm>
+		External interface scripts are provided to enable Samba to interface smoothly to
+		essential operating system functions for user and group management. This is important
+		to enable workstations to join the Domain and is also important so that you can use
+		the Windows NT4 Domain User Manager as well as the Domain Server Manager. These tools
+		are provided as part of the <filename>SRVTOOLS.EXE</filename> toolkit that can be 
+		downloaded from the Microsoft FTP
+		<ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">site</ulink>.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>User Mode</primary></indexterm>
+		The &smb.conf; file specifies that the Samba server will operate in (default) <parameter>
+		security = user</parameter> mode<footnote><para>See <emphasis>TOSHARG2</emphasis>, Chapter 3.
+		This is necessary so that Samba can act as a Domain Controller (PDC); see
+		<emphasis>TOSHARG2</emphasis>, Chapter 4, for additional information.</para></footnote>
+		(User Mode).
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>logon services</primary></indexterm>
+		<indexterm><primary>logon script</primary></indexterm>
+		Domain logon services as well as a Domain logon script are specified. The logon script
+		will be used to add robustness to the overall network configuration.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>roaming profiles</primary></indexterm>
+		<indexterm><primary>logon path</primary></indexterm>
+		<indexterm><primary>profile share</primary></indexterm>
+		Roaming profiles are enabled through the specification of the parameter,
+		<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>. The value of this parameter translates the
+		<constant>%L</constant> to the name by which the Samba server is called by the client (for this
+		configuration, it translates to the name <constant>DIAMOND</constant>), and the <constant>%U</constant>
+		will translate to the name of the user within the context of the connection made to the profile share.
+		It is the administrator's responsibility to ensure there is a directory in the root of the
+		profile share for each user. This directory must be owned by the user also. An exception to this
+		requirement is when a profile is created for group use.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>virus</primary></indexterm>
+		<indexterm><primary>opportunistic locking</primary></indexterm>
+		Precautionary veto is effected for particular Windows file names that have been targeted by 
+		virus-related activity. Additionally, Microsoft Office files are vetoed from opportunistic locking
+		controls. This should help to prevent lock contention-related file access problems.
+		</para></listitem>
+
+		<listitem><para>
+		Every user has a private home directory on the UNIX/Linux host. This is mapped to
+		a network drive that is the same for all users.
+		</para></listitem>
+
+	</itemizedlist>
+
+	<para>
+	The configuration of the server is the most complex so far. The following steps are used:
+	</para>
+
+	<orderedlist numeration="arabic">
+		<listitem><para>
+		Basic System Configuration
+		</para></listitem>
+
+		<listitem><para>
+		Samba Configuration
+		</para></listitem>
+
+		<listitem><para>
+		DHCP and DNS Server Configuration
+		</para></listitem>
+
+		<listitem><para>
+		Printer Configuration
+		</para></listitem>
+
+		<listitem><para>
+		Process Start-up Configuration
+		</para></listitem>
+
+		<listitem><para>
+		Validation
+		</para></listitem>
+
+		<listitem><para>
+		Application Share Configuration
+		</para></listitem>
+
+		<listitem><para>
+		Windows Client Configuration
+		</para></listitem>
+	</orderedlist>
+
+	<para>
+	The following sections cover each step in logical and defined detail.
+	</para>
+
+	<sect2 id="ch4bsc">
+	<title>Basic System Configuration</title>
+
+	<para>
+	<indexterm><primary>SUSE Enterprise Linux Server</primary></indexterm>
+	The preparation in this section assumes that your SUSE Enterprise Linux Server 8.0 system has been
+	freshly installed. It prepares basic files so that the system is ready for comprehensive
+	operation in line with the network diagram shown in <link linkend="ch04net"/>.
+	</para>
+
+	<procedure>
+	<title>Server Configuration Steps</title>
+
+		<step><para>
+		<indexterm><primary>hostname</primary></indexterm>
+		Using the UNIX/Linux system tools, name the server <constant>server.abmas.us</constant>.
+		Verify that your hostname is correctly set by running:
+<screen>
+&rootprompt; uname -n
+server
+</screen>
+		An alternate method to verify the hostname is:
+<screen>
+&rootprompt; hostname -f
+server.abmas.us
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/hosts</primary></indexterm>
+		<indexterm><primary>localhost</primary></indexterm>
+		Edit your <filename>/etc/hosts</filename> file to include the primary names and addresses
+		of all network interfaces that are on the host server. This is necessary so that during
+		startup the system can resolve all its own names to the IP address prior to
+		startup of the DNS server. An example of entries that should be in the 
+		<filename>/etc/hosts</filename> file is:
+<screen>
+127.0.0.1       localhost
+192.168.1.1     sleeth1.abmas.biz sleeth1 diamond
+192.168.2.1     sleeth2.abmas.biz sleeth2
+123.45.67.66    server.abmas.us server
+</screen>
+		You should check the startup order of your system. If the CUPS print server is started before
+		the DNS server (<command>named</command>), you should also include an entry for the printers
+		in the <filename>/etc/hosts</filename> file, as follows:
+<screen>
+192.168.1.20    qmsa.abmas.biz qmsa
+192.168.1.30    hplj6a.abmas.biz hplj6a
+192.168.2.20    qmsf.abmas.biz qmsf
+192.168.2.30    hplj6f.abmas.biz hplj6f
+</screen>
+		<indexterm><primary>named</primary></indexterm>
+		<indexterm><primary>cupsd</primary></indexterm>
+		<indexterm><primary>daemon</primary></indexterm>
+		The printer entries are not necessary if <command>named</command> is started prior to
+		startup of <command>cupsd</command>, the CUPS daemon.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/rc.d/boot.local</primary></indexterm>
+		<indexterm><primary>IP forwarding</primary></indexterm>
+		<indexterm><primary>/proc/sys/net/ipv4/ip_forward</primary></indexterm>
+		The host server is acting as a router between the two internal network segments as well
+		as for all Internet access. This necessitates that IP forwarding be enabled. This can be
+		achieved by adding to the <filename>/etc/rc.d/boot.local</filename> an entry as follows:
+<screen>
+echo 1 > /proc/sys/net/ipv4/ip_forward
+</screen>
+		To ensure that your kernel is capable of IP forwarding during configuration, you may 
+		wish to execute that command manually also. This setting permits the Linux system to 
+		act as a router.<footnote><para>You may want to do the echo command last and include 
+				"0" in the init scripts, since it opens up your network for a short time.</para></footnote>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>firewall</primary></indexterm>
+		<indexterm><primary>abmas-netfw.sh</primary></indexterm>
+		Installation of a basic firewall and NAT facility is necessary.
+		The following script can be installed in the <filename>/usr/local/sbin</filename>
+		directory. It is executed from the <filename>/etc/rc.d/boot.local</filename> startup
+		script. In your case, this script is called <filename>abmas-netfw.sh</filename>. The
+		script contents are shown in <link linkend="ch4natfw"/>.
+
+<example id="ch4natfw">
+<title>NAT Firewall Configuration Script</title>
+<screen>
+#!/bin/sh
+echo -e "\n\nLoading NAT firewall.\n"
+IPTABLES=/usr/sbin/iptables
+EXTIF="eth0"
+INTIFA="eth1"
+INTIFB="eth2"
+
+/sbin/depmod -a
+/sbin/modprobe ip_tables
+/sbin/modprobe ip_conntrack
+/sbin/modprobe ip_conntrack_ftp
+/sbin/modprobe iptable_nat
+/sbin/modprobe ip_nat_ftp
+$IPTABLES -P INPUT DROP
+$IPTABLES -F INPUT
+$IPTABLES -P OUTPUT ACCEPT
+$IPTABLES -F OUTPUT
+$IPTABLES -P FORWARD DROP
+$IPTABLES -F FORWARD
+
+$IPTABLES -A INPUT -i lo -j ACCEPT
+$IPTABLES -A INPUT -i $INTIFA -j ACCEPT
+$IPTABLES -A INPUT -i $INTIFB -j ACCEPT
+$IPTABLES -A INPUT -i $EXTIF -m state --state ESTABLISHED,RELATED -j ACCEPT
+# Enable incoming traffic for: SSH, SMTP, DNS(tcp), HTTP, HTTPS
+for i in 22 25 53 80 443
+do
+        $IPTABLES -A INPUT -i $EXTIF -p tcp --dport $i  -j ACCEPT
+done
+# Allow DNS(udp)
+$IPTABLES -A INPUT -i $EXTIF -p udp -dport 53  -j ACCEPT
+echo "Allow all connections OUT and only existing and specified ones IN"
+$IPTABLES -A FORWARD -i $EXTIF -o $INTIFA -m state \
+                                  --state ESTABLISHED,RELATED -j ACCEPT
+$IPTABLES -A FORWARD -i $EXTIF -o $INTIFB -m state \
+                                  --state ESTABLISHED,RELATED -j ACCEPT
+$IPTABLES -A FORWARD -i $INTIFA -o $EXTIF -j ACCEPT
+$IPTABLES -A FORWARD -i $INTIFB -o $EXTIF -j ACCEPT
+$IPTABLES -A FORWARD -j LOG
+echo "   Enabling SNAT (MASQUERADE) functionality on $EXTIF"
+$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE
+echo "1" > /proc/sys/net/ipv4/ip_forward
+echo -e "\nNAT firewall done.\n"
+</screen>
+</example>
+		</para></step>
+
+		<step><para>
+		Execute the following to make the script executable:
+<screen>
+&rootprompt; chmod 755 /usr/local/sbin/abmas-natfw.sh
+</screen>
+		You must now edit <filename>/etc/rc.d/boot.local</filename> to add an entry
+		that runs your <command>abmas-natfw.sh</command> script. The following
+		entry works for you:
+<screen>
+#! /bin/sh
+#
+# Copyright (c) 2002 SUSE Linux AG Nuernberg, Germany. 
+# All rights reserved.
+#
+# Author: Werner Fink, 1996
+#         Burchard Steinbild, 1996
+#
+# /etc/init.d/boot.local
+#
+# script with local commands to be executed from init on system startup
+#
+# Here you should add things that should happen directly after booting
+# before we're going to the first run level.
+#
+/usr/local/sbin/abmas-natfw.sh
+</screen>
+		</para></step>
+	</procedure>
+
+	<para>
+	<indexterm><primary>/etc/hosts</primary></indexterm>
+	The server is now ready for Samba configuration. During the validation step, you remove
+	the entry for the Samba server <constant>diamond</constant> from the <filename>/etc/hosts</filename>
+	file. This is done after you are satisfied that DNS-based name resolution is functioning correctly.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Samba Configuration</title>
+
+	<para>
+	When you have completed this section, the Samba server is ready for testing and validation;
+	however, testing and validation have to wait until DHCP, DNS, and printing (CUPS) services have 
+	been configured.
+	</para>
+
+	<procedure>
+	<title>Samba Configuration Steps</title>
+
+		<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.20-1.i386.rpm</filename>, one way to install this
+		file is as follows:
+<screen>
+&rootprompt; rpm -Uvh samba-3.0.20-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,
+		refer to the operating system manufacturer's documentation for guidance.
+		</para></step>
+
+		<step><para>
+		Install the &smb.conf; file shown in <link linkend="promisnet"/>, <link linkend="promisnetsvca"/>,
+		and <link linkend="promisnetsvcb"/>. Concatenate (join) all three files to make a single &smb.conf;
+		file. The final, fully qualified path for this file should be <filename>/etc/samba/smb.conf</filename>.
+
+<example id="promisnet">
+<title>130 User Network with <emphasis>tdbsam</emphasis> &smbmdash; [globals] Section</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">PROMISES</smbconfoption>
+<smbconfoption name="netbios name">DIAMOND</smbconfoption>
+<smbconfoption name="interfaces">eth1, eth2, lo</smbconfoption>
+<smbconfoption name="bind interfaces only">Yes</smbconfoption>
+<smbconfoption name="passdb backend">tdbsam</smbconfoption>
+<smbconfoption name="pam password change">Yes</smbconfoption>
+<smbconfoption name="passwd program">/usr/bin/passwd %u</smbconfoption>
+<smbconfoption name="passwd chat">*New*Password* %n\n *Re-enter*new*password*%n\n *Password*changed*</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="unix password sync">Yes</smbconfoption>
+<smbconfoption name="log level">1</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
+<smbconfoption name="max log size">50</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+<smbconfoption name="time server">Yes</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="add user script">/usr/sbin/useradd -m '%u'</smbconfoption>
+<smbconfoption name="delete user script">/usr/sbin/userdel -r '%u'</smbconfoption>
+<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
+<smbconfoption name="delete group script">/usr/sbin/groupdel '%g'</smbconfoption>
+<smbconfoption name="add user to group script">/usr/sbin/usermod -G '%g' '%u'</smbconfoption>
+<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /tmp '%u'</smbconfoption>
+<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
+<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
+<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
+<smbconfoption name="logon drive">X:</smbconfoption>
+<smbconfoption name="logon home">\\%L\%U</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="preferred master">Yes</smbconfoption>
+<smbconfoption name="wins support">Yes</smbconfoption>
+<smbconfoption name="utmp">Yes</smbconfoption>
+<smbconfoption name="map acl inherit">Yes</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+<smbconfoption name="cups options">Raw</smbconfoption>
+<smbconfoption name="veto files">/*.eml/*.nws/*.{*}/</smbconfoption>
+<smbconfoption name="veto oplock files">/*.doc/*.xls/*.mdb/</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="promisnetsvca">
+<title>130 User Network with <emphasis>tdbsam</emphasis> &smbmdash; Services Section Part A</title>
+<smbconfblock>
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="default devmode">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">Network Logon Service</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="locking">No</smbconfoption>
+
+<smbconfsection name="[profiles]"/>
+<smbconfoption name="comment">Profile Share</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="profile acls">Yes</smbconfoption>
+
+<smbconfsection name="[accounts]"/>
+<smbconfoption name="comment">Accounting Files</smbconfoption>
+<smbconfoption name="path">/data/accounts</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="promisnetsvcb">
+<title>130 User Network with <emphasis>tdbsam</emphasis> &smbmdash; Services Section Part B</title>
+<smbconfblock>
+<smbconfsection name="[service]"/>
+<smbconfoption name="comment">Financial Services Files</smbconfoption>
+<smbconfoption name="path">/data/service</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[pidata]"/>
+<smbconfoption name="comment">Property Insurance Files</smbconfoption>
+<smbconfoption name="path">/data/pidata</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[apps]"/>
+<smbconfoption name="comment">Application Files</smbconfoption>
+<smbconfoption name="path">/apps</smbconfoption>
+<smbconfoption name="read only">Yes</smbconfoption>
+<smbconfoption name="admin users">bjordan</smbconfoption>
+</smbconfblock>
+</example>
+		</para></step>
+
+		<step><para>
+	      <indexterm><primary>administrator</primary></indexterm><indexterm>
+		<primary>smbpasswd</primary>
+	      </indexterm>
+		Add the <constant>root</constant> user to the password backend as follows:
+<screen>
+&rootprompt; smbpasswd -a root
+New SMB password: XXXXXXXX
+Retype new SMB password: XXXXXXXX
+&rootprompt;
+</screen>
+		The <constant>root</constant> account is the UNIX equivalent of the Windows Domain Administrator.
+		This account is essential in the regular maintenance of your Samba server. It must never be
+		deleted. If for any reason the account is deleted, you may not be able to recreate this account
+		without considerable trouble.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>username map</primary></indexterm>
+                Create the username map file to permit the <constant>root</constant> account to be called
+                <constant>Administrator</constant> from the Windows network environment. To do this, create
+                the file <filename>/etc/samba/smbusers</filename> with the following contents:
+<screen>
+####
+# User mapping file
+####
+# File Format
+# -----------
+# Unix_ID = Windows_ID
+#
+# Examples:
+# root = Administrator
+# janes = "Jane Smith"
+# jimbo = Jim Bones
+#
+# Note: If the name contains a space it must be double quoted.
+#       In the example above the name 'jimbo' will be mapped to Windows
+#       user names 'Jim' and 'Bones' because the space was not quoted.
+#######################################################################
+root = Administrator
+####
+# End of File
+####
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>initGrps.sh</primary></indexterm>
+		<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>add</tertiary></indexterm>
+		<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>modify</tertiary></indexterm>
+		<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>list</tertiary></indexterm>
+                Create and map Windows Domain Groups to UNIX groups. A sample script is provided in <link linkend="small"/>,
+                <link linkend="initGrps"/>. Create a file containing this script. We called ours
+                <filename>/etc/samba/initGrps.sh</filename>. Set this file so it can be executed,
+                and then execute the script. Sample output should be as follows:
+
+<example id="ch4initGrps">
+<title>Script to Map Windows NT Groups to UNIX Groups</title>
+<indexterm><primary>initGrps.sh</primary></indexterm>
+<screen>
+#!/bin/bash
+#
+# initGrps.sh
+#
+
+# Create UNIX groups
+groupadd acctsdep
+groupadd finsrvcs
+
+# Map Windows Domain Groups to UNIX groups
+net groupmap add ntgroup="Domain Admins"  unixgroup=root type=d
+net groupmap add ntgroup="Domain Users"   unixgroup=users type=d
+net groupmap add ntgroup="Domain Guests"  unixgroup=nobody type=d
+
+# Add Functional Domain Groups
+net groupmap add ntgroup="Accounts Dept"  unixgroup=acctsdep type=d
+net groupmap add ntgroup="Financial Services" unixgroup=finsrvcs type=d
+net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
+
+# Map Windows NT machine local groups to local UNIX groups
+# Mapping of local groups is not necessary and not functional
+# for this installation.
+</screen>
+</example>
+
+<screen>
+&rootprompt; chmod 755 initGrps.sh
+&rootprompt; /etc/samba # ./initGrps.sh
+Updated mapping entry for Domain Admins
+Updated mapping entry for Domain Users
+Updated mapping entry for Domain Guests
+No rid or sid specified, choosing algorithmic mapping
+Successfully added group Accounts Dept to the mapping db
+No rid or sid specified, choosing algorithmic mapping
+Successfully added group Domain Guests to the mapping db
+
+&rootprompt; /etc/samba # net groupmap list | sort
+Account Operators (S-1-5-32-548) -> -1
+Accounts Dept (S-1-5-21-179504-2437109-488451-2003) -> acctsdep
+Administrators (S-1-5-32-544) -> -1
+Backup Operators (S-1-5-32-551) -> -1
+Domain Admins (S-1-5-21-179504-2437109-488451-512) -> root
+Domain Guests (S-1-5-21-179504-2437109-488451-514) -> nobody
+Domain Users (S-1-5-21-179504-2437109-488451-513) -> users
+Financial Services (S-1-5-21-179504-2437109-488451-2005) -> finsrvcs
+Guests (S-1-5-32-546) -> -1
+Power Users (S-1-5-32-547) -> -1
+Print Operators (S-1-5-32-550) -> -1
+Replicators (S-1-5-32-552) -> -1
+System Operators (S-1-5-32-549) -> -1
+Users (S-1-5-32-545) -> -1
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>useradd</primary></indexterm>
+		<indexterm><primary>adduser</primary></indexterm>
+		<indexterm><primary>passwd</primary></indexterm>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		<indexterm><primary>/etc/passwd</primary></indexterm>
+		<indexterm><primary>password</primary><secondary>backend</secondary></indexterm>
+		<indexterm><primary>user</primary><secondary>management</secondary></indexterm>
+		There is one preparatory step without which you will not have a working Samba 
+		network environment. You must add an account for each network user. 
+                For each user who needs to be given a Windows Domain account, make an entry in the
+                <filename>/etc/passwd</filename> file as well as in the Samba password backend.
+                Use the system tool of your choice to create the UNIX system account, and use the Samba
+                <command>smbpasswd</command> to create a Domain user account.
+                There are a number of tools for user management under UNIX, such as
+                <command>useradd</command>, and <command>adduser</command>, as well as a plethora of custom
+                tools. You also want to create a home directory for each user.
+		You can do this by executing the following steps for each user:
+<screen>
+&rootprompt; useradd -m <parameter>username</parameter>
+&rootprompt; passwd <parameter>username</parameter>
+Changing password for <parameter>username</parameter>.
+New password: XXXXXXXX
+Re-enter new password: XXXXXXXX
+Password changed
+&rootprompt; smbpasswd -a <parameter>username</parameter>
+New SMB password: XXXXXXXX
+Retype new SMB password: XXXXXXXX
+Added user <parameter>username</parameter>.
+</screen>
+		You do of course use a valid user login ID in place of <parameter>username</parameter>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>file system</primary><secondary>access control</secondary></indexterm>
+		<indexterm><primary>file system</primary><secondary>permissions</secondary></indexterm>
+		<indexterm><primary>group membership</primary></indexterm>
+                Using the preferred tool for your UNIX system, add each user to the UNIX groups created
+                previously as necessary. File system access control will be based on UNIX group membership.
+                </para></step>
+
+                <step><para>
+                Create the directory mount point for the disk subsystem that can be mounted to provide
+                data storage for company files. In this case the mount point is indicated in the &smb.conf;
+                file is <filename>/data</filename>. Format the file system as required, and mount the formatted
+                file system partition using appropriate system tools.
+                </para></step>
+
+                <step><para>
+		<indexterm><primary>file system</primary><secondary>permissions</secondary></indexterm>
+                Create the top-level file storage directories for data and applications as follows:
+<screen>
+&rootprompt; mkdir -p /data/{accounts,finsrvcs}
+&rootprompt; mkdir -p /apps
+&rootprompt; chown -R root:root /data
+&rootprompt; chown -R root:root /apps
+&rootprompt; chown -R bjordan:acctsdep /data/accounts
+&rootprompt; chown -R bjordan:finsrvcs /data/finsrvcs
+&rootprompt; chmod -R ug+rwxs,o-rwx /data
+&rootprompt; chmod -R ug+rwx,o+rx-w /apps
+</screen>
+                Each department is responsible for creating its own directory structure within the departmental
+                share. The directory root of the <command>accounts</command> share is <filename>/data/accounts</filename>.
+                The directory root of the <command>finsvcs</command> share is <filename>/data/finsvcs</filename>.
+		The <filename>/apps</filename> directory is the root of the <constant>apps</constant> share
+		that provides the application server infrastructure.
+		</para></step>
+
+		<step><para>
+		The &smb.conf; file specifies an infrastructure to support roaming profiles and network
+		logon services. You can now create the file system infrastructure to provide the
+		locations on disk that these services require. Adequate planning is essential,
+		since desktop profiles can grow to be quite large. For planning purposes, a minimum of
+		200 MB of storage should be allowed per user for profile storage. The following
+		commands create the directory infrastructure needed:
+<screen>
+&rootprompt; mkdir -p /var/spool/samba 
+&rootprompt; mkdir -p /var/lib/samba/{netlogon/scripts,profiles}
+&rootprompt; chown -R root:root /var/spool/samba
+&rootprompt; chown -R root:root /var/lib/samba
+&rootprompt; chmod a+rwxt /var/spool/samba
+&rootprompt; chmod 2775 /var/lib/samba/profiles
+&rootprompt; chgrp users /var/lib/samba/profiles
+</screen>
+		For each user account that is created on the system, the following commands should be
+		executed:
+<screen>
+&rootprompt; mkdir /var/lib/samba/profiles/'username'
+&rootprompt; chown 'username':users /var/lib/samba/profiles/'username'
+&rootprompt; chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username'
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>logon scrip</primary></indexterm>
+		<indexterm><primary>unix2dos</primary></indexterm>
+		<indexterm><primary>dos2unix</primary></indexterm>
+		Create a logon script. It is important that each line is correctly terminated with
+		a carriage return and line-feed combination (i.e., DOS encoding). The following procedure
+		works if the right tools (<constant>unix2dos</constant> and <constant>dos2unix</constant>) are installed.
+		First, create a file called <filename>/var/lib/samba/netlogon/scripts/logon.bat.unix</filename>
+		with the following contents:
+<screen>
+net time \\diamond /set /yes
+net use h: /home
+net use p: \\diamond\apps
+</screen>
+		Convert the UNIX file to a DOS file using the <command>unix2dos</command> as shown here:
+<screen>
+&rootprompt; unix2dos &lt; /var/lib/samba/netlogon/scripts/logon.bat.unix \
+	&gt; /var/lib/samba/netlogon/scripts/logon.bat
+</screen>
+		</para></step>
+	</procedure>
+
+	</sect2>
+
+	<sect2 id="ch4dhcpdns">
+	<title>Configuration of DHCP and DNS Servers</title>
+
+	<para>
+	DHCP services are a basic component of the entire network client installation. DNS operation is
+	foundational to Internet access as well as to trouble-free operation of local networking. When
+	you have completed this section, the server should be ready for solid duty operation.
+	</para>
+
+	<procedure>
+	<title>DHCP and DNS Server Configuration Steps</title>
+
+		<step><para>
+		<indexterm><primary>/etc/dhcpd.conf</primary></indexterm>
+		Create a file called <filename>/etc/dhcpd.conf</filename> with the contents as
+		shown in <link linkend="prom-dhcp"/>.
+
+<example id="prom-dhcp">
+<title>DHCP Server Configuration File &smbmdash; <filename>/etc/dhcpd.conf</filename></title>
+<screen>
+# Abmas Accounting Inc.
+default-lease-time 86400;
+max-lease-time 172800;
+default-lease-time 86400;
+option ntp-servers 192.168.1.1;
+option domain-name "abmas.biz";
+option domain-name-servers 192.168.1.1, 192.168.2.1;
+option netbios-name-servers 192.168.1.1, 192.168.2.1;
+option netbios-node-type 8;       ### Node type = Hybrid ###
+ddns-updates on;                  ### Dynamic DNS enabled ###
+ddns-update-style interim;
+
+subnet 192.168.1.0 netmask 255.255.255.0 {
+        range dynamic-bootp 192.168.1.128 192.168.1.254;
+        option subnet-mask 255.255.255.0;
+        option routers 192.168.1.1;
+        allow unknown-clients;
+        host qmsa {
+                hardware ethernet 08:00:46:7a:35:e4;
+                fixed-address 192.168.1.20;
+                }
+        host hplj6a {
+                hardware ethernet 00:03:47:cb:81:e0;
+                fixed-address 192.168.1.30;
+                }
+        }
+subnet 192.168.2.0 netmask 255.255.255.0 {
+        range dynamic-bootp 192.168.2.128 192.168.2.254;
+        option subnet-mask 255.255.255.0;
+        option routers 192.168.2.1;
+        allow unknown-clients;
+        host qmsf {
+                hardware ethernet 01:04:31:db:e1:c0;
+                fixed-address 192.168.1.20;
+        	}
+        host hplj6f {
+                hardware ethernet 00:03:47:cf:83:e2;
+                fixed-address 192.168.2.30;
+                }
+	}
+subnet 127.0.0.0 netmask 255.0.0.0 {
+        }
+subnet 123.45.67.64 netmask 255.255.255.252 {
+        }
+</screen>
+</example>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/named.conf</primary></indexterm>
+		Create a file called <filename>/etc/named.conf</filename> that has the combined contents
+		of the <link linkend="ch4namedcfg"/>, <link linkend="ch4namedvarfwd"/>, and
+		<link linkend="ch4namedvarrev"/> files that are concatenated (merged) in this
+		specific order.
+		</para></step>
+
+		<step><para>
+		Create the files shown in their respective directories as shown in <link linkend="namedrscfiles">DNS
+		(named) Resource Files</link>.
+
+			<table id="namedrscfiles">
+				<title>DNS (named) Resource Files</title>
+				<tgroup cols="2">
+					<colspec align="left"/>
+					<colspec align="left"/>
+					<thead>
+						<row>
+							<entry>Reference</entry>
+							<entry>File Location</entry>
+						</row>
+					</thead>
+					<tbody>
+						<row>
+							<entry><link linkend="loopback"/></entry>
+							<entry>/var/lib/named/localhost.zone</entry>
+						</row>
+						<row>
+							<entry><link linkend="dnsloopy"/></entry>
+							<entry>/var/lib/named/127.0.0.zone</entry>
+						</row>
+						<row>
+							<entry><link linkend="roothint"/></entry>
+							<entry>/var/lib/named/root.hint</entry>
+						</row>
+						<row>
+							<entry><link linkend="abmasbiz"/></entry>
+							<entry>/var/lib/named/master/abmas.biz.hosts</entry>
+						</row>
+						<row>
+							<entry><link linkend="abmasus"/></entry>
+							<entry>/var/lib/named/abmas.us.hosts</entry>
+						</row>
+						<row>
+							<entry><link linkend="eth1zone"/></entry>
+							<entry>/var/lib/named/192.168.1.0.rev</entry>
+						</row>
+						<row>
+							<entry><link linkend="eth2zone"/></entry>
+							<entry>/var/lib/named/192.168.2.0.rev</entry>
+						</row>
+					</tbody>
+				</tgroup>
+			</table>
+
+<example id="ch4namedcfg">
+<title>DNS Master Configuration File &smbmdash; <filename>/etc/named.conf</filename> Master Section</title>
+<indexterm><primary>/etc/named.conf</primary></indexterm>
+<screen>
+###
+# Abmas Biz DNS Control File
+###
+# Date: November 15, 2003
+###
+options {
+	directory "/var/lib/named";
+	forwarders {
+		123.45.12.23;
+		};
+	forward first;
+	listen-on {
+		mynet;
+		};
+	auth-nxdomain yes;
+	multiple-cnames yes;
+	notify no;
+};
+
+zone "." in {
+	type hint;
+	file "root.hint";
+};
+
+zone "localhost" in {
+	type master;
+	file "localhost.zone";
+};
+
+zone "0.0.127.in-addr.arpa" in {
+	type master;
+	file "127.0.0.zone";
+};
+
+acl mynet {
+	192.168.1.0/24;
+	192.168.2.0/24;
+	127.0.0.1;
+};
+
+acl seconddns {
+	123.45.54.32;
+};
+
+</screen>
+</example>
+
+<example id="ch4namedvarfwd">
+<title>DNS Master Configuration File &smbmdash; <filename>/etc/named.conf</filename> Forward Lookup Definition Section</title>
+<screen>
+zone "abmas.biz" {
+	type master;
+	file "/var/lib/named/master/abmas.biz.hosts";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+	allow-update {
+		mynet;
+	};
+};
+
+zone "abmas.us" {
+	type master;
+	file "/var/lib/named/master/abmas.us.hosts";
+	allow-query {
+		any;
+	};
+	allow-transfer {
+		seconddns;
+	};
+};
+</screen>
+</example>
+
+<example id="ch4namedvarrev">
+<title>DNS Master Configuration File &smbmdash; <filename>/etc/named.conf</filename> Reverse Lookup Definition Section</title>
+<screen>
+zone "1.168.192.in-addr.arpa" {
+	type master;
+	file "/var/lib/named/master/192.168.1.0.rev";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+	allow-update {
+		mynet;
+	};
+};
+
+zone "2.168.192.in-addr.arpa" {
+	type master;
+	file "/var/lib/named/master/192.168.2.0.rev";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+	allow-update {
+		mynet;
+	};
+};
+</screen>
+</example>
+
+<example id="eth1zone">
+<title>DNS 192.168.1 Reverse Zone File</title>
+<screen>
+$ORIGIN .
+$TTL 38400	; 10 hours 40 minutes
+1.168.192.in-addr.arpa	IN SOA	sleeth.abmas.biz. root.abmas.biz. (
+				2003021825 ; serial
+				10800      ; refresh (3 hours)
+				3600       ; retry (1 hour)
+				604800     ; expire (1 week)
+				38400      ; minimum (10 hours 40 minutes)
+				)
+			NS	sleeth1.abmas.biz.
+$ORIGIN 1.168.192.in-addr.arpa.
+1			PTR	sleeth1.abmas.biz.
+20			PTR	qmsa.abmas.biz.
+30			PTR	hplj6a.abmas.biz.
+</screen>
+</example>
+
+<example id="eth2zone">
+<title>DNS 192.168.2 Reverse Zone File</title>
+<screen>
+$ORIGIN .
+$TTL 38400	; 10 hours 40 minutes
+2.168.192.in-addr.arpa	IN SOA	sleeth.abmas.biz. root.abmas.biz. (
+				2003021825 ; serial
+				10800      ; refresh (3 hours)
+				3600       ; retry (1 hour)
+				604800     ; expire (1 week)
+				38400      ; minimum (10 hours 40 minutes)
+				)
+			NS	sleeth2.abmas.biz.
+$ORIGIN 2.168.192.in-addr.arpa.
+1			PTR	sleeth2.abmas.biz.
+20			PTR	qmsf.abmas.biz.
+30			PTR	hplj6f.abmas.biz.
+</screen>
+</example>
+
+<example id="abmasbiz">
+<title>DNS Abmas.biz Forward Zone File</title>
+<screen>
+$ORIGIN .
+$TTL 38400      ; 10 hours 40 minutes
+abmas.biz       IN SOA  sleeth1.abmas.biz. root.abmas.biz. (
+                                2003021833 ; serial
+                                10800      ; refresh (3 hours)
+                                3600       ; retry (1 hour)
+                                604800     ; expire (1 week)
+                                38400      ; minimum (10 hours 40 minutes)
+                                )
+                        NS      dns.abmas.biz.
+                        MX      10 mail.abmas.biz.
+$ORIGIN abmas.biz.
+sleeth1                 A       192.168.1.1
+sleeth2                 A       192.168.2.1
+qmsa                    A       192.168.1.20
+hplj6a                  A       192.168.1.30
+qmsf                    A       192.168.2.20
+hplj6f                  A       192.168.2.30
+dns                     CNAME   sleeth1
+diamond                 CNAME   sleeth1
+mail                    CNAME   sleeth1
+</screen>
+</example>
+
+<example id="abmasus">
+<title>DNS Abmas.us Forward Zone File</title>
+<screen>
+$ORIGIN .
+$TTL 38400      ; 10 hours 40 minutes
+abmas.us        IN SOA  server.abmas.us. root.abmas.us. (
+                                2003021833 ; serial
+                                10800      ; refresh (3 hours)
+                                3600       ; retry (1 hour)
+                                604800     ; expire (1 week)
+                                38400      ; minimum (10 hours 40 minutes)
+                                )
+                        NS      dns.abmas.us.
+                        NS      dns2.abmas.us.
+                        MX      10 mail.abmas.us.
+$ORIGIN abmas.us.
+server                  A       123.45.67.66
+dns2                    A       123.45.54.32
+gw                      A       123.45.67.65
+www                     CNAME   server
+mail                    CNAME   server
+dns                     CNAME   server
+</screen>
+</example>
+
+		</para></step>
+
+		<step><para>
+	      <indexterm><primary>/etc/resolv.conf</primary></indexterm><indexterm>
+		<primary>name resolution</primary>
+	      </indexterm>
+		All DNS name resolution should be handled locally. To ensure that the server is configured
+		correctly to handle this, edit <filename>/etc/resolv.conf</filename> to have the following
+		content:
+<screen>
+search abmas.us abmas.biz
+nameserver 127.0.0.1
+nameserver 123.45.54.23
+</screen>
+	      <indexterm>
+		<primary>DNS server</primary>
+	      </indexterm>
+		This instructs the name resolver function (when configured correctly) to ask the DNS server
+		that is running locally to resolve names to addresses. In the event that the local name server
+		is not available, ask the name server provided by the ISP. The latter, of course, does not resolve
+		purely local names to IP addresses.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+		The final step is to edit the <filename>/etc/nsswitch.conf</filename> file.
+		This file controls the operation of the various resolver libraries that are part of the Linux
+		Glibc libraries. Edit this file so that it contains the following entries:
+<screen>
+hosts:      files dns wins
+</screen>
+		</para></step>
+	</procedure>
+
+	<para>
+	The basic DHCP and DNS services are now ready for validation testing. Before you can proceed,
+	there are a few more steps along the road. First, configure the print spooling and print
+	processing system.  Then you can configure the server so that all services
+	start automatically on reboot. You must also manually start all services prior to validation testing.
+	</para>
+
+	</sect2>
+
+	<sect2 id="ch4ptrcfg">
+	<title>Printer Configuration</title>
+
+	<para>
+	Network administrators who are new to CUPS based-printing typically experience some difficulty mastering
+	its powerful features. The steps outlined in this section are designed to navigate around the distractions
+	of learning CUPS. Instead of implementing smart features and capabilities, our approach is to use it as a
+	transparent print queue that performs no filtering, and only minimal handling of each print job that is
+	submitted to it. In other words, our configuration turns CUPS into a raw-mode print queue. This means that
+	the correct printer driver must be installed on all clients.
+	</para>
+
+	<procedure>
+	<title>Printer Configuration Steps</title>
+
+		<step><para>
+		Configure each printer to be a DHCP client, carefully following the manufacturer's guidelines.
+		</para></step>
+
+                <step><para>
+                Follow the instructions in the printer manufacturer's manuals to permit printing to port 9100.
+		Use any other port the manufacturer specifies for direct-mode raw printing, and adjust the
+		port as necessary in the following example commands.
+                This allows the CUPS spooler to print using raw mode protocols.
+                <indexterm><primary>CUPS</primary></indexterm>
+                <indexterm><primary>raw printing</primary></indexterm>
+                </para></step>
+
+                <step><para>
+	      <indexterm><primary>CUPS</primary><secondary>queue</secondary></indexterm><indexterm>
+		<primary>lpadmin</primary>
+	      </indexterm>
+                Configure the CUPS Print Queues as follows:
+<screen>
+&rootprompt; lpadmin -p qmsa -v socket://qmsa.abmas.biz:9100 -E
+&rootprompt; lpadmin -p hplj6a -v socket://hplj6a.abmas.biz:9100 -E
+&rootprompt; lpadmin -p qmsf -v socket://qmsf.abmas.biz:9100 -E
+&rootprompt; lpadmin -p hplj6f -v socket://hplj6f.abmas.biz:9100 -E
+</screen>
+                <indexterm><primary>print filter</primary></indexterm>
+                This creates the necessary print queues with no assigned print filter.
+                </para></step>
+
+	  <step><para><indexterm>
+		<primary>enable</primary>
+	      </indexterm>
+		Print queues may not be enabled at creation. Use <command>lpc stat</command> to check
+		the status of the print queues and, if necessary, make certain that the queues you have 
+		just created are enabled by executing the following:
+<screen>
+&rootprompt; /usr/bin/enable qmsa
+&rootprompt; /usr/bin/enable hplj6a
+&rootprompt; /usr/bin/enable qmsf
+&rootprompt; /usr/bin/enable hplj6f
+</screen>
+		</para></step>
+
+	  <step><para><indexterm>
+		<primary>accept</primary>
+	      </indexterm>
+		Even though your print queues may be enabled, it is still possible that they
+		are not accepting print jobs. A print queue services incoming printing
+		requests only when configured to do so. Ensure that your print queues are
+		set to accept incoming jobs by executing the following commands:
+<screen>
+&rootprompt; /usr/sbin/accept qmsa
+&rootprompt; /usr/sbin/accept hplj6a
+&rootprompt; /usr/sbin/accept qmsf
+&rootprompt; /usr/sbin/accept hplj6f
+</screen>
+		</para></step>
+
+                <step><para>
+                <indexterm><primary>mime type</primary></indexterm>
+                <indexterm><primary>/etc/mime.convs</primary></indexterm>
+                <indexterm><primary>application/octet-stream</primary></indexterm>
+                Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
+<screen>
+application/octet-stream     application/vnd.cups-raw      0     -
+</screen>
+                </para></step>
+
+                <step><para>
+                <indexterm><primary>/etc/mime.types</primary></indexterm>
+                Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
+<screen>
+application/octet-stream
+</screen>
+                </para></step>
+
+		<step><para>
+		Printing drivers are installed on each network client workstation.
+		</para></step>
+	</procedure>
+
+	<para>
+	Note: If the parameter <parameter>cups options = Raw</parameter> is specified in the &smb.conf; file,
+	the last two steps can be omitted with CUPS version 1.1.18, or later.
+	</para>
+
+	<para>
+	The UNIX system print queues have been configured and are ready for validation testing.
+	</para>
+
+	</sect2>
+
+	<sect2 id="procstart">
+	<title>Process Startup Configuration</title>
+
+	<para>
+	<indexterm><primary>chkconfig</primary></indexterm>
+	There are two essential steps to process startup configuration. First, the process
+	must be configured so that it automatically restarts each time the server
+	is rebooted. This step involves use of the <command>chkconfig</command> tool that
+	creates the appropriate symbolic links from the master daemon control file that is
+	located in the <filename>/etc/rc.d</filename> directory, to the <filename>/etc/rc'x'.d</filename>
+	directories. Links are created so that when the system run level is changed, the
+	necessary start or kill script is run.
+	</para>
+
+	<para>
+	<indexterm><primary>/etc/xinetd.d</primary></indexterm>
+	<indexterm><primary>inetd</primary></indexterm>
+	<indexterm><primary>xinetd</primary></indexterm>
+	<indexterm><primary>chkconfig</primary></indexterm>
+	<indexterm><primary>super daemon</primary></indexterm>
+	In the event that a service is not run as a daemon, but via the internetworking
+	super daemon (<command>inetd</command> or <command>xinetd</command>), then the <command>chkconfig</command>
+	tool makes the necessary entries in the <filename>/etc/xinetd.d</filename> directory
+	and sends a hang-up (HUP) signal to the the super daemon, thus forcing it to
+	re-read its control files.
+	</para>
+
+	<para>
+	Last, each service must be started to permit system validation to proceed.
+	</para>
+
+	<procedure>
+                <step><para>
+                Use the standard system tool to configure each service to restart
+                automatically at every system reboot. For example,
+                <indexterm><primary>chkconfig</primary></indexterm>
+<screen>
+&rootprompt; chkconfig dhpcd on
+&rootprompt; chkconfig named on
+&rootprompt; chkconfig cups on
+&rootprompt; chkconfig smb on
+</screen>
+		</para></step>
+
+		<step><para>
+                <indexterm><primary>starting dhcpd</primary></indexterm>
+                <indexterm><primary>starting samba</primary></indexterm>
+                <indexterm><primary>starting CUPS</primary></indexterm>
+		Now start each service to permit the system to be validated.
+		Execute each of the following in the sequence shown:
+
+<screen>
+&rootprompt; /etc/rc.d/init.d/dhcpd restart
+&rootprompt; /etc/rc.d/init.d/named restart
+&rootprompt; /etc/rc.d/init.d/cups restart
+&rootprompt; /etc/rc.d/init.d/smb restart
+</screen>
+                </para></step>
+	</procedure>
+
+	</sect2>
+
+	<sect2 id="ch4valid">
+	<title>Validation</title>
+
+	<para>
+	<indexterm><primary>validation</primary></indexterm>
+	Complex networking problems are most often caused by simple things that are poorly or incorrectly
+	configured. The validation process adopted here should be followed carefully; it is the result of the
+	experience gained from years of making and correcting the most common mistakes. Shortcuts often lead to basic errors. You should
+	refrain from taking shortcuts, from making basic assumptions, and from not exercising due process
+	and diligence in network validation. By thoroughly testing and validating every step in the process
+	of network installation and configuration, you can save yourself from sleepless nights and restless
+	days. A well debugged network is a foundation for happy network users and network administrators. 
+	Later in this book you learn how to make users happier. For now, it is enough to learn to 
+	validate. Let's get on with it.
+	</para>
+
+		<procedure>
+		<title>Server Validation Steps</title>
+
+			<step><para>
+			<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+			One of the most important facets of Samba configuration is to ensure that
+			name resolution functions correctly. You can check name resolution
+			with a few simple tests. The most basic name resolution is provided from the
+			<filename>/etc/hosts</filename> file. To test its operation, make a
+			temporary edit to the <filename>/etc/nsswitch.conf</filename> file. Using
+			your favorite editor, change the entry for <constant>hosts</constant> to read:
+<screen>
+hosts:     files
+</screen>
+			When you have saved this file, execute the following command:
+<screen>
+&rootprompt; ping diamond
+PING sleeth1.abmas.biz (192.168.1.1) 56(84) bytes of data.
+64 bytes from sleeth1 (192.168.1.1): icmp_seq=1 ttl=64 time=0.131 ms
+64 bytes from sleeth1 (192.168.1.1): icmp_seq=2 ttl=64 time=0.179 ms
+64 bytes from sleeth1 (192.168.1.1): icmp_seq=3 ttl=64 time=0.192 ms
+64 bytes from sleeth1 (192.168.1.1): icmp_seq=4 ttl=64 time=0.191 ms
+
+--- sleeth1.abmas.biz ping statistics ---
+4 packets transmitted, 4 received, 0% packet loss, time 3016ms
+rtt min/avg/max/mdev = 0.131/0.173/0.192/0.026 ms
+</screen>
+			This proves that name resolution via the <filename>/etc/hosts</filename> file
+			is working.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+			So far, your installation is going particularly well. In this step we validate
+			DNS server and name resolution operation. Using your favorite UNIX system editor,
+			change the <filename>/etc/nsswitch.conf</filename> file so that the
+			<constant>hosts</constant> entry reads:
+<screen>
+hosts:        dns
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>named</primary></indexterm>
+			Before you test DNS operation, it is a good idea to verify that the DNS server
+			is running by executing the following:
+<screen>
+&rootprompt; ps ax | grep named
+  437 ?        S      0:00 /sbin/syslogd -a /var/lib/named/dev/log
+  524 ?        S      0:00 /usr/sbin/named -t /var/lib/named -u named
+  525 ?        S      0:00 /usr/sbin/named -t /var/lib/named -u named
+  526 ?        S      0:00 /usr/sbin/named -t /var/lib/named -u named
+  529 ?        S      0:00 /usr/sbin/named -t /var/lib/named -u named
+  540 ?        S      0:00 /usr/sbin/named -t /var/lib/named -u named
+ 2552 pts/2    S      0:00 grep named
+</screen>
+			This means that we are ready to check DNS operation. Do so by executing:
+			<indexterm><primary>ping</primary></indexterm>
+<screen>
+&rootprompt; ping diamond
+PING sleeth1.abmas.biz (192.168.1.1) 56(84) bytes of data.
+64 bytes from sleeth1 (192.168.1.1): icmp_seq=1 ttl=64 time=0.156 ms
+64 bytes from sleeth1 (192.168.1.1): icmp_seq=2 ttl=64 time=0.183 ms
+
+--- sleeth1.abmas.biz ping statistics ---
+2 packets transmitted, 2 received, 0% packet loss, time 999ms
+rtt min/avg/max/mdev = 0.156/0.169/0.183/0.018 ms
+</screen>
+			You should take a few more steps to validate DNS server operation, as follows:
+<screen>
+&rootprompt; host -f diamond.abmas.biz
+sleeth1.abmas.biz has address 192.168.1.1
+</screen>
+			<indexterm><primary>/etc/hosts</primary></indexterm>
+			You may now remove the entry called <constant>diamond</constant> from the
+			<filename>/etc/hosts</filename> file. It does not hurt to leave it there,
+			but its removal reduces the number of administrative steps for this name.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+			WINS is a great way to resolve NetBIOS names to their IP address. You can test
+			the operation of WINS by starting <command>nmbd</command> (manually or by way
+			of the Samba startup method shown in <link linkend="procstart"/>). You must edit
+			the <filename>/etc/nsswitch.conf</filename> file so that the <constant>hosts</constant>
+			entry is as follows:
+<screen>
+hosts:        wins
+</screen>
+			The next step is to make certain that Samba is running using <command>ps ax | grep mbd</command>.
+			The <command>nmbd</command> daemon will provide the WINS name resolution service when the
+			&smb.conf; file <smbconfsection>[global]</smbconfsection> parameter <smbconfoption name="wins
+			support">Yes</smbconfoption> has been specified.  Having validated that Samba is operational,
+			excute the following:
+<screen>
+&rootprompt; ping diamond
+PING diamond (192.168.1.1) 56(84) bytes of data.
+64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.094 ms
+64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.479 ms
+</screen>
+			<indexterm><primary>ping</primary></indexterm>
+			Now that you can relax with the knowledge that all three major forms of name
+			resolution to IP address resolution are working, edit the <filename>/etc/nsswitch.conf</filename>
+			again. This time you add all three forms of name resolution to this file.
+			Your edited entry for <constant>hosts</constant> should now look like this:
+<screen>
+hosts:       files dns wins
+</screen>
+			The system is looking good. Let's move on.
+			</para></step>
+
+			<step><para>
+			It would give you peace of mind to know that the DHCP server is running
+			and available for service. You can validate DHCP services by running:
+
+<screen>
+&rootprompt; ps ax | grep dhcp
+ 2618 ?        S      0:00 /usr/sbin/dhcpd ...
+ 8180 pts/2    S      0:00 grep dhcp
+</screen>
+			This shows that the server is running. The proof of whether or not it is working
+			comes when you try to add the first DHCP client to the network.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>testparm</primary></indexterm>
+			This is a good point at which to start validating Samba operation. You are 
+			content that name resolution is working for basic TCP/IP needs. Let's move on.
+			If your &smb.conf; file has bogus options or parameters, this may cause Samba
+			to refuse to start. The first step should always be to validate the contents
+			of this file by running:
+<screen>
+&rootprompt; testparm -s
+Load smb config files from smb.conf
+Processing section "[homes]"
+Processing section "[printers]"
+Processing section "[netlogon]"
+Processing section "[profiles]"
+Processing section "[accounts]"
+Processing section "[service]"
+Processing section "[apps]"
+Loaded services file OK.
+# Global parameters
+[global]
+    workgroup = PROMISES
+    netbios name = DIAMOND
+    interfaces = eth1, eth2, lo
+    bind interfaces only = Yes
+    passdb backend = tdbsam
+    pam password change = Yes
+    passwd program = /usr/bin/passwd '%u'
+    passwd chat = *New*Password* %n\n \
+             *Re-enter*new*password* %n\n *Password*changed*
+    username map = /etc/samba/smbusers
+    unix password sync = Yes
+    log level = 1
+    syslog = 0
+    log file = /var/log/samba/%m
+    max log size = 50
+    smb ports = 139
+    name resolve order = wins bcast hosts
+    time server = Yes
+    printcap name = CUPS
+    show add printer wizard = No
+    add user script = /usr/sbin/useradd -m '%u'
+    delete user script = /usr/sbin/userdel -r '%u'
+    add group script = /usr/sbin/groupadd '%g'
+    delete group script = /usr/sbin/groupdel '%g'
+    add user to group script = /usr/sbin/usermod -G '%g' '%u'
+    add machine script = /usr/sbin/useradd \
+                              -s /bin/false -d /dev/null '%u'
+    shutdown script = /var/lib/samba/scripts/shutdown.sh
+    abort shutdown script = /sbin/shutdown -c
+    logon script = scripts\logon.bat
+    logon path = \\%L\profiles\%U
+    logon drive = X:
+    logon home = \\%L\%U
+    domain logons = Yes
+    preferred master = Yes
+    wins support = Yes
+    utmp = Yes
+    winbind use default domain = Yes
+    map acl inherit = Yes
+    cups options = Raw
+    veto files = /*.eml/*.nws/*.{*}/
+    veto oplock files = /*.doc/*.xls/*.mdb/
+
+[homes]
+    comment = Home Directories
+    valid users = %S
+    read only = No
+    browseable = No
+...
+### Remainder cut to save space ###
+</screen>
+			Clear away all errors before proceeding.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>check samba daemons</primary></indexterm>
+			<indexterm><primary>smbd</primary></indexterm>
+			<indexterm><primary>nmbd</primary></indexterm>
+			<indexterm><primary>winbindd</primary></indexterm>
+			Check that the Samba server is running:
+<screen>
+&rootprompt; ps ax | grep mbd
+14244 ?        S      0:00 /usr/sbin/nmbd -D
+14245 ?        S      0:00 /usr/sbin/nmbd -D
+14290 ?        S      0:00 /usr/sbin/smbd -D
+
+$rootprompt; ps ax | grep winbind
+14293 ?        S     0:00 /usr/sbin/winbindd -B
+14295 ?        S     0:00 /usr/sbin/winbindd -B
+</screen>
+			The <command>winbindd</command> daemon is running in split mode (normal), so there are also
+			two instances<footnote><para>For more information regarding winbindd, see <emphasis>TOSHARG2</emphasis>, 
+			Chapter 23, Section 23.3. The single instance of <command>smbd</command> is normal. One additional
+			<command>smbd</command> slave process is spawned for each SMB/CIFS client 
+			connection.</para></footnote> of it.
+			</para></step>
+	
+			<step><para>
+			<indexterm><primary>anonymous
+		  connection</primary></indexterm>
+	      <indexterm>
+		<primary>smbclient</primary>
+	      </indexterm>
+			Check that an anonymous connection can be made to the Samba server:
+<screen>
+&rootprompt; smbclient -L localhost -U%
+
+        Sharename      Type      Comment
+        ---------      ----      -------
+        IPC$           IPC       IPC Service (Samba 3.0.20)
+        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.20)
+        hplj6a         Printer   hplj6a
+        hplj6f         Printer   hplj6f
+        qmsa           Printer   qmsa
+        qmsf           Printer   qmsf
+
+        Server               Comment
+        ---------            -------
+        DIAMOND              Samba 3.0.20
+
+        Workgroup            Master
+        ---------            -------
+        PROMISES             DIAMOND
+</screen>
+			This demonstrates that an anonymous listing of shares can be obtained. This is the equivalent
+			of browsing the server from a Windows client to obtain a list of shares on the server.
+			The <constant>-U%</constant> argument means to send a <constant>NULL</constant> username and
+			a <constant>NULL</constant> password.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>dhcp client validation</primary></indexterm>
+			<indexterm><primary>printer validation</primary></indexterm>
+			<indexterm><primary>arp</primary></indexterm>
+			Verify that each printer has the IP address assigned in the DHCP server configuration file.
+			The easiest way to do this is to ping the printer name. Immediately after the ping response
+			has been received, execute <command>arp -a</command> to find the MAC address of the printer
+			that has responded. Now you can compare the IP address and the MAC address of the printer
+			with the configuration information in the <filename>/etc/dhcpd.conf</filename> file. They
+			should, of course, match. For example,
+<screen>
+&rootprompt; ping hplj6
+PING hplj6a (192.168.1.30) 56(84) bytes of data.
+64 bytes from hplj6a (192.168.1.30): icmp_seq=1 ttl=64 time=0.113 ms
+
+&rootprompt; arp -a
+hplj6a (192.168.1.30) at 00:03:47:CB:81:E0 [ether] on eth0
+</screen>
+	      <indexterm>
+		<primary>/etc/dhcpd.conf</primary>
+	      </indexterm>
+			The MAC address <constant>00:03:47:CB:81:E0</constant> matches that specified for the
+			IP address from which the printer has responded and with the entry for it in the
+			<filename>/etc/dhcpd.conf</filename> file. Repeat this for each printer configured.
+			</para></step>
+	
+			<step><para>
+			<indexterm><primary>authenticated connection</primary></indexterm>
+			Make an authenticated connection to the server using the <command>smbclient</command> tool:
+<screen>
+&rootprompt; smbclient //diamond/accounts -U gholmes
+Password: XXXXXXX
+smb: \> dir
+  .                          D        0  Thu Nov 27 15:07:09 2003
+  ..                         D        0  Sat Nov 15 17:40:50 2003
+  zakadmin.exe                   161424  Thu Nov 27 15:06:52 2003
+  zak.exe                       6066384  Thu Nov 27 15:06:52 2003
+  dhcpd.conf                       1256  Thu Nov 27 15:06:52 2003
+  smb.conf                         2131  Thu Nov 27 15:06:52 2003
+  initGrps.sh                A     1089  Thu Nov 27 15:06:52 2003
+  POLICY.EXE                      86542  Thu Nov 27 15:06:52 2003
+
+                55974 blocks of size 65536. 33968 blocks available
+smb: \> q
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>nmap</primary></indexterm>
+			Your new server is connected to an Internet-accessible connection. Before you start
+			your firewall, you should run a port scanner against your system. You should repeat that
+			after the firewall has been started. This helps you understand to what extent the
+			server may be vulnerable to external attack. One way you can do this is by using an
+			external service, such as the <ulink url="http://www.dslreports.com/scan">DSL Reports</ulink> 
+			tools. Alternately, if you can gain root-level access to a remote
+			UNIX/Linux system that has the <command>nmap</command> tool, you can run the following:
+<screen>
+&rootprompt; nmap -v -sT server.abmas.us
+
+Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
+Host server.abmas.us (123.45.67.66) appears to be up ... good.
+Initiating Connect() Scan against server.abmas.us (123.45.67.66)
+Adding open port 6000/tcp
+Adding open port 873/tcp
+Adding open port 445/tcp
+Adding open port 10000/tcp
+Adding open port 901/tcp
+Adding open port 631/tcp
+Adding open port 25/tcp
+Adding open port 111/tcp
+Adding open port 32770/tcp
+Adding open port 3128/tcp
+Adding open port 53/tcp
+Adding open port 80/tcp
+Adding open port 443/tcp
+Adding open port 139/tcp
+Adding open port 22/tcp
+The Connect() Scan took 0 seconds to scan 1601 ports.
+Interesting ports on server.abmas.us (123.45.67.66):
+(The 1587 ports scanned but not shown below are in state: closed)
+Port       State       Service
+22/tcp     open        ssh
+25/tcp     open        smtp
+53/tcp     open        domain
+80/tcp     open        http
+111/tcp    open        sunrpc
+139/tcp    open        netbios-ssn
+443/tcp    open        https
+445/tcp    open        microsoft-ds
+631/tcp    open        ipp
+873/tcp    open        rsync
+901/tcp    open        samba-swat
+3128/tcp   open        squid-http
+6000/tcp   open        X11
+10000/tcp  open        snet-sensor-mgmt
+32770/tcp  open        sometimes-rpc3
+
+Nmap run completed -- 1 IP address (1 host up) scanned in 1 second
+</screen>
+			The above scan was run before the external interface was locked down with the NAT-firewall
+			script you created above. The following results are obtained after the firewall rules
+			have been put into place:
+<screen>
+&rootprompt; nmap -v -sT server.abmas.us
+
+Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
+Host server.abmas.us (123.45.67.66) appears to be up ... good.
+Initiating Connect() Scan against server.abmas.us (123.45.67.66)
+Adding open port 53/tcp
+Adding open port 22/tcp
+The Connect() Scan took 168 seconds to scan 1601 ports.
+Interesting ports on server.abmas.us (123.45.67.66):
+(The 1593 ports scanned but not shown below are in state: filtered)
+Port       State       Service
+22/tcp     open        ssh
+25/tcp     closed      smtp
+53/tcp     open        domain
+80/tcp     closed      http
+443/tcp    closed      https
+
+Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
+</screen>
+			</para></step>
+	
+		</procedure>
+
+	</sect2>
+
+	<sect2 id="ch4appscfg">
+	<title>Application Share Configuration</title>
+
+	<para>
+	<indexterm><primary>application server</primary></indexterm>
+	<indexterm><primary>administrative installation</primary></indexterm>
+	The use of an application server is a key mechanism by which desktop administration overheads
+	can be reduced. Check the application manual for your software to identify how best to
+	create an administrative installation.
+	</para>
+
+	<para>
+	Some Windows software will only run locally on the desktop computer. Such software
+	is typically not suited for administrative installation. Administratively installed software
+	permits one or more of the following installation choices:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Install software fully onto a workstation, storing data files on the same workstation.
+		</para></listitem>
+
+		<listitem><para>
+		Install software fully onto a workstation with central network data file storage.
+		</para></listitem>
+
+		<listitem><para>
+		Install software to run off a central application server with data files stored
+		on the local workstation. This is often called a minimum installation, or a
+		network client installation.
+		</para></listitem>
+
+		<listitem><para>
+		Install software to run off a central application server with data files stored
+		on a central network share. This type of installation often prevents storage
+		of work files on the local workstation.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	<indexterm><primary></primary></indexterm>
+	A common application deployed in this environment is an office suite.
+	Enterprise editions of Microsoft Office XP Professional can be administratively installed
+	by launching the installation from a command shell. The command that achieves this is
+	<command>setup /a</command>. It results in a set of prompts through which various
+	installation choices can be made. Refer to the Microsoft Office Resource SDK and Resource
+	Kit for more information regarding this mode of installation of MS Office XP Professional.
+	The full administrative installation of MS Office XP Professional requires approximately
+	650 MB of disk space.
+	</para>
+
+	<para>
+	When the MS Office XP Professional product has been installed to the administrative network
+	share, the product can be installed onto a workstation by executing the normal setup program.
+	The installation process now provides a choice to either perform a minimum installation
+	or a full local installation. A full local installation takes over 100 MB of disk space.
+	A network workstation (minimum) installation requires typically 10 MB to 15 MB of
+	local disk space. In the latter case, when the applications are used, they load over the network.
+	</para>
+
+	<para>
+	<indexterm><primary>Service Packs</primary></indexterm>
+	<indexterm><primary>Microsoft Office</primary></indexterm>
+	Microsoft Office Service Packs can be unpacked to update an administrative share. This makes
+	it possible to update MS Office XP Professional for all users from a single installation
+	of the service pack and generally circumvents the need to run updates on each network
+	Windows client.
+	</para>	
+
+	<para>
+	The default location for MS Office XP Professional data files can be set through registry
+	editing or by way of configuration options inside each Office XP Professional application.
+	</para>
+
+	<para>
+	<indexterm><primary>OpenOffice</primary></indexterm>
+	OpenOffice.Org OpenOffice Version 1.1.0 can be installed locally. It can also
+	be installed to run off a network share. The latter is a most desirable solution for office-bound 
+	network users and for administrative staff alike. It permits quick and easy updates
+	to be rolled out to all users with a minimum of disruption and with maximum flexibility.
+	</para>
+
+	<para>
+	The process for installation of administrative shared OpenOffice involves download of the
+	distribution ZIP file, followed by extraction of the ZIP file into a temporary disk area.
+	When fully extracted using the unzipping tool of your choosing, change into the Windows
+	installation files directory then execute <command>setup -net</command>. You are
+	prompted on screen for the target installation location. This is the administrative
+	share point. The full administrative OpenOffice share takes approximately 150 MB of disk
+	space.
+	</para>
+
+		<sect3>
+		<title>Comments Regarding Software Terms of Use</title>
+			<para>
+			Many single-user products can be installed into an administrative share, but
+			personal versions of products such as Microsoft Office XP Professional do not permit this. 
+			Many people do not like terms of use typical with commercial products, so a few comments
+			regarding software licensing seem important.
+			</para>
+
+			<para>
+			Please do not use an administrative installation of proprietary and commercially licensed 
+			software products to violate the copyright holders' property. All software is licensed,
+			particularly software that is licensed for use free of charge. All software is the property
+			of the copyright holder unless the author and/or copyright holder has explicitly disavowed
+			ownership and has placed the software into the public domain.
+			</para>
+
+			<para>
+			Software that is under the GNU General Public License, like proprietary software, is 
+			licensed in a way that restricts use. For example, if you modify GPL software and then
+			distribute the binary version of your modifications, you must offer to provide the source
+			code as well. This restriction is designed to maintain the momentum
+			of the diffusion of technology and to protect against the withholding of innovations.
+			</para>
+
+			<para>
+			Commercial and proprietary software generally restrict use to those who have paid the
+			license fees and who comply with the licensee's terms of use. Software that is released
+			under the GNU General Public License is restricted to particular terms and conditions
+			also. Whatever the licensing terms may be, if you do not approve of the terms of use,
+			please do not use the software.
+			</para>
+
+			<para>
+			<indexterm><primary>GPL</primary></indexterm>
+			Samba is provided under the terms of the GNU GPL Version 2, a copy of which is provided
+			with the source code.
+			</para>
+		</sect3>
+
+	</sect2>
+
+	<sect2 id="ch4wincfg">
+	<title>Windows Client Configuration</title>
+
+	<para>
+	Christine needs to roll out 130 new desktop systems. There is no doubt that she also needs
+	to reinstall many of the notebook computers that will be recycled for use with the new network 
+	configuration. The smartest way to handle the challenge of the roll-out program is to build
+	a staged system for each type of target machine, and then use an image replication tool such as Norton
+	Ghost (enterprise edition) to replicate the staged machine to its target desktops. The same can
+	be done with notebook computers as long as they are identical or sufficiently similar.
+	</para>
+
+	<procedure id="sbewinclntprep">
+	<title>Windows Client Configuration Procedure</title>
+
+		<step><para>
+		<indexterm><primary>WINS</primary></indexterm>
+		<indexterm><primary>DHCP</primary></indexterm>
+		Install MS Windows XP Professional. During installation, configure the client to use DHCP for 
+		TCP/IP protocol configuration. DHCP configures all Windows clients to use the WINS Server
+		address that has been defined for the local subnet.
+		</para></step>
+
+		<step><para>
+		Join the Windows Domain <constant>PROMISES</constant>. Use the Domain Administrator
+		username <constant>root</constant> and the SMB password you assigned to this account.
+		A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to
+		a Windows Domain is given in <link linkend="appendix"/>, <link linkend="domjoin"/>. 
+		Reboot the machine as prompted and then log on using the Domain Administrator account
+		(<constant>root</constant>).
+		</para></step>
+
+		<step><para>
+		Verify <constant>DIAMOND</constant> is visible in <guimenu>My Network Places</guimenu>, 
+		that it is possible to connect to it and see the shares <guimenuitem>accounts</guimenuitem>,
+		<guimenuitem>apps</guimenuitem>, and <guimenuitem>finsvcs</guimenuitem>, and that it is
+		possible to open each share to reveal its contents.
+		</para></step>
+
+		<step><para>
+		Create a drive mapping to the <constant>apps</constant> share on the server <constant>DIAMOND</constant>.
+		</para></step>
+
+		<step><para>
+		Perform an administrative installation of each application to be used. Select the options
+		that you wish to use. Of course, you can choose to run applications over the network, correct?
+		</para></step>
+
+		<step><para>
+		Now install all applications to be installed locally. Typical tools include Adobe Acrobat,
+		NTP-based time synchronization software, drivers for specific local devices such as fingerprint
+		scanners, and the like. Probably the most significant application for local installation
+		is antivirus software.
+		</para></step>
+
+		<step><para>
+		Now install all four printers onto the staging system. The printers you install
+		include the accounting department HP LaserJet 6 and Minolta QMS Magicolor printers. You will
+		also configure identical printers that are located in the financial services department.
+		Install printers on each machine following the steps shown in the Windows client printer
+		preparation procedure below.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>defragmentation</primary></indexterm>
+		When you are satisfied that the staging systems are complete, use the appropriate procedure to
+		remove the client from the domain. Reboot the system and then log on as the local administrator
+		and clean out all temporary files stored on the system. Before shutting down, use the disk
+		defragmentation tool so that the file system is in optimal condition before replication.
+		</para></step>
+
+		<step><para>
+		Boot the workstation using the Norton (Symantec) Ghosting diskette (or CD-ROM) and image the
+		machine to a network share on the server.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>Windows security identifier</primary><see>SID</see></indexterm>
+		<indexterm><primary>SID</primary></indexterm>
+		You may now replicate the image to the target machines using the appropriate Norton Ghost 
+		procedure. Make sure to use the procedure that ensures each machine has a unique
+		Windows security identifier (SID). When the installation of the disk image has completed, boot the PC. 
+		</para></step>
+
+		<step><para>
+		Log on to the machine as the local Administrator (the only option), and join the machine to
+		the Domain, following the procedure set out in <link linkend="appendix"/>, <link linkend="domjoin"/>. The system is now 
+		ready for the user to log on, provided you have created a network logon account for that 
+		user, of course.
+		</para></step>
+
+		<step><para>
+		Instruct all users to log on to the workstation using their assigned username and password.
+		</para></step>
+	</procedure>
+
+	<procedure id="sbewinclntptrprep">
+	<title>Windows Client Printer Preparation Procedure</title>
+
+		<step><para>
+		Click <menuchoice>
+			<guimenu>Start</guimenu>
+			<guimenuitem>Settings</guimenuitem>
+			<guimenuitem>Printers</guimenuitem>
+			<guiicon>Add Printer</guiicon>
+			<guibutton>Next</guibutton>
+			</menuchoice>. Do not click <guimenuitem>Network printer</guimenuitem>.
+			Ensure that <guimenuitem>Local printer</guimenuitem> is selected.
+		</para></step>
+
+		<step><para>
+		Click <guibutton>Next</guibutton>. In the
+		<guimenuitem>Manufacturer:</guimenuitem> panel, select <constant>HP</constant>.
+		In the <guimenuitem>Printers:</guimenuitem> panel, select the printer called
+		<constant>HP LaserJet 6</constant>. Click <guibutton>Next</guibutton>.
+		</para></step>
+
+		<step><para>
+		In the <guimenuitem>Available ports:</guimenuitem> panel, select
+		<constant>FILE:</constant>. Accept the default printer name by clicking
+		<guibutton>Next</guibutton>. When asked, <quote>Would you like to print a
+		test page?,</quote> click <guimenuitem>No</guimenuitem>. Click
+		<guibutton>Finish</guibutton>.
+		</para></step>
+
+		<step><para>
+		You may be prompted for the name of a file to print to. If so, close the
+		dialog panel. Right-click <menuchoice>
+			<guiicon>HP LaserJet 6</guiicon>
+			<guimenuitem>Properties</guimenuitem>
+			<guisubmenu>Details (Tab)</guisubmenu>
+			<guimenuitem>Add Port</guimenuitem>
+			</menuchoice>.
+		</para></step>
+
+		<step><para>
+		In the <guimenuitem>Network</guimenuitem> panel, enter the name of
+		the print queue on the Samba server as follows: <constant>\\DIAMOND\hplj6a</constant>.
+		Click <menuchoice> 
+			<guibutton>OK</guibutton>
+			<guibutton>OK</guibutton>
+			</menuchoice> to complete the installation.
+		</para></step>
+
+		<step><para>
+		Repeat the printer installation steps above for both HP LaserJet 6 printers
+		as well as for both QMS Magicolor laser printers.
+		</para></step>
+	</procedure>
+
+	</sect2>
+
+	<sect2>
+	<title>Key Points Learned</title>
+
+		<para>
+		How do you feel? You have built a capable network, a truly ambitious project.
+		Future network updates can be handled by
+		your staff. You must be a satisfied manager. Let's review the achievements.
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			A simple firewall has been configured to protect the server in the event that
+			the ISP firewall service should fail.
+			</para></listitem>
+
+			<listitem><para>
+			The Samba configuration uses measures to ensure that only local network users
+			can connect to SMB/CIFS services.
+			</para></listitem>
+
+			<listitem><para>
+			Samba uses the new <constant>tdbsam</constant> passdb backend facility.
+			Considerable complexity was added to Samba functionality.
+			</para></listitem>
+
+			<listitem><para>
+			A DHCP server was configured to implement dynamic DNS (DDNS) updates to the DNS
+			server.
+			</para></listitem>
+
+			<listitem><para>
+			The DNS server was configured to permit DDNS only for local network clients. This
+			server also provides primary DNS services for the company Internet presence.
+			</para></listitem>
+
+			<listitem><para>
+			You introduced an application server as well as the concept of cloning a Windows
+			client in order to effect improved standardization of desktops and to reduce
+			the costs of network management.
+			</para></listitem>
+		</itemizedlist>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	</para>
+
+	<qandaset defaultlable="missed01" type="number">
+	<qandaentry>
+	<question>
+
+		<para>
+		What is the maximum number of account entries that the <parameter>tdbsam</parameter>
+		passdb backend can handle?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The tdb data structure and support system can handle more entries than the number of
+		accounts that are possible on most UNIX systems. A practical limit would come into
+		play long before a performance boundary would be anticipated. That practical limit
+		is controlled by the nature of Windows networking. There are few Windows file and
+		print servers that can handle more than a few hundred concurrent client connections.
+		The key limiting factors that predicate offloading of services to additional servers
+		are memory capacity, the number of CPUs, network bandwidth, and disk I/O limitations.
+		All of these are readily exhausted by just a few hundred concurrent active users.
+		Such bottlenecks can best be removed by segmentation of the network (distributing
+		network load across multiple networks).
+		</para>
+
+		<para>
+		As the network grows, it becomes necessary to provide additional authentication
+		servers (domain controllers).  The tdbsam is limited to a single machine and cannot
+		be reliably replicated.  This means that practical limits on network design dictate
+		the point at which a distributed passdb backend is required; at this time, there is
+		no real alternative other than ldapsam (LDAP).
+		</para>
+
+		<para>
+		The guideline provided in <emphasis>TOSHARG2</emphasis>, Chapter 10, Section 10.1.2,
+		is to limit the number of accounts in the tdbsam backend to 250. This is the point
+		at which most networks tend to want backup domain controllers (BDCs). Samba-3 does
+		not provide a mechanism for replicating tdbsam data so it can be used by a BDC. The
+		limitation of 250 users per tdbsam is predicated only on the need for replication,
+		not on the limits<footnote><para>Bench tests have shown that tdbsam is a very
+		effective database technology.  There is surprisingly little performance loss even
+		with over 4000 users.</para></footnote> of the tdbsam backend itself. 
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Would Samba operate any better if the OS level is set to a value higher than 35?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		No. MS Windows workstations and servers do not use a value higher than 33. Setting this to a value
+		of 35 already assures Samba of precedence over MS Windows products in browser elections. There is
+		no gain to be had from setting this higher.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why in this example have you provided UNIX group to Windows Group mappings for only Domain Groups?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		At this time, Samba has the capacity to use only Domain Groups mappings. It is possible that at
+		a later date Samba may make use of Windows Local Groups, as well as of the Active Directory special
+		Groups. Proper operation requires Domain Groups to be mapped to valid UNIX groups.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why has a path been specified in the <parameter>IPC$</parameter> share?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		This is done so that in the event that a software bug may permit a client connection to the IPC$ share to
+		obtain access to the file system, it does so at a location that presents least risk. Under normal operation
+		this type of paranoid step should not be necessary. The use of this parameter should not be necessary. 
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why does the &smb.conf; file in this exercise include an entry for <smbconfoption name="smb ports"/>?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The default order by which Samba-3 attempts to communicate with MS Windows clients is via port 445 (the TCP port
+		used by Windows clients when NetBIOS-less SMB over TCP/IP is in use). TCP port 139 is the primary port used for NetBIOS
+		over TCP/IP. In this configuration Windows network operations are predicated around NetBIOS over TCP/IP. By
+		specifying the use of only port 139, the intent is to reduce unsuccessful service connection attempts.
+		The result of this is improved network performance. Where Samba-3 is installed as an Active Directory Domain
+		member, the default behavior is highly beneficial and should not be changed.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What is the difference between a print queue and a printer?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		A printer is a physical device that is connected either directly to the network or to a computer 
+		via a serial, parallel, or USB connection so that print jobs can be submitted to it to create a 
+		hard copy printout. Network-attached printers that use TCP/IP-based printing generally accept a 
+		single print data stream and block all secondary attempts to dispatch jobs concurrently to the 
+		same device. If many clients were to concurrently print directly via TCP/IP to the same printer, 
+		it would result in a huge amount of network traffic through continually failing connection attempts.
+		</para>
+
+		<para>
+		A print server (like CUPS or LPR/LPD) accepts multiple concurrent input streams or
+		print requests. When the data stream has been fully received, the input stream is closed,
+		and the job is then submitted to a sequential print queue where the job is stored until
+		the printer is ready to receive the job.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Can all MS Windows application software be installed onto an application server share?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Much older Windows software is not compatible with installation to and execution from
+		an application server. Enterprise versions of Microsoft Office XP Professional can
+		be installed to an application server. Retail consumer versions of Microsoft Office XP
+		Professional do not permit installation to an application server share and can be installed
+		and used only to/from a local workstation hard disk.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why use dynamic DNS (DDNS)?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		When DDNS records are updated directly from the DHCP server, it is possible for
+		network clients that are not NetBIOS-enabled, and thus cannot use WINS, to locate
+		Windows clients via DNS.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why would you use WINS as well as DNS-based name resolution?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		WINS is to NetBIOS names as DNS is to fully qualified domain names (FQDN). The FQDN is
+		a name like <quote>myhost.mydomain.tld</quote> where <parameter>tld</parameter>
+		means <constant>top-level domain</constant>. A FQDN is a longhand but easy-to-remember
+		expression that may be up to 1024 characters in length and that represents an IP address. 
+		A NetBIOS name is always 16 characters long. The 16<superscript>th</superscript> character
+		is a name type indicator. A specific name type is registered<footnote><para>
+		See <emphasis>TOSHARG2</emphasis>, Chapter 9, for more information.</para></footnote> for each 
+		type of service that is provided by the Windows server or client and that may be registered
+		where a WINS server is in use.
+		</para>
+
+		<para>
+		WINS is a mechanism by which a client may locate the IP Address that corresponds to a
+		NetBIOS name. The WINS server may be queried to obtain the IP Address for a NetBIOS name 
+		that includes a particular registered NetBIOS name type. DNS does not provide a mechanism
+		that permits handling of the NetBIOS name type information.
+		</para>
+
+		<para>
+		DNS provides a mechanism by which TCP/IP clients may locate the IP address of a particular 
+		hostname or service name that has been registered in the DNS database for a particular domain. 
+		A DNS server has limited scope of control and is said to be authoritative for the zone over
+		which it has control.
+		</para>
+
+		<para>
+		Windows 200x Active Directory requires the registration in the DNS zone for the domain it 
+		controls of service locator<footnote><para>See TOSHARG2, Chapter 9, Section 9.3.3.</para></footnote> records 
+		that Windows clients and servers will use to locate Kerberos and LDAP services. ADS also 
+		requires the registration of special records that are called global catalog (GC) entries 
+		and site entries by which domain controllers and other essential ADS servers may be located. 
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What are the major benefits of using an application server?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The use of an application server can significantly reduce application update maintenance.
+		By providing a centralized application share, software updates need be applied to only
+		one location for all major applications used. This results in faster update roll-outs and
+		significantly better application usage control.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	</qandaset>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-ByExample/SBE-SimpleOfficeServer.xml b/docs-xml/Samba3-ByExample/SBE-SimpleOfficeServer.xml
new file mode 100644
index 00000000000..eaa436d6efa
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-SimpleOfficeServer.xml
@@ -0,0 +1,1591 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="simple">
+  <title>No-Frills Samba Servers</title>
+
+	<para>
+	This is the start of the real journey toward the successful deployment of Samba. For some this chapter
+	is the end of the road because their needs will have been adequately met. For others, this chapter is
+	the beginning of a journey that will take them well past the contents of this book. This book provides
+	example configurations of, for the greater part, complete networking solutions. The intent of this book
+	is to help you to get your Samba installation working with the least amount of pain and aggravation.
+	</para>
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>
+	This chapter lays the groundwork for understanding the basics of Samba operation. 
+	Instead of a bland technical discussion, each principle is demonstrated by way of a 
+	real-world scenario for which a working solution<footnote><para>The examples given mirror those documented
+	in The Official Samba-3 HOWTO and Reference Guide, Second Edition (TOSHARG2) Chapter 2, Section 2.3.1. You may gain additional
+	insight from the standalone server configurations covered in TOSHARG2, sections 2.3.1.2 through 2.3.1.4.
+	</para></footnote> is fully described.
+	</para>
+
+	<para>
+	The practical exercises take you on a journey through a drafting office, a charity administration
+	office, and an accounting office. You may choose to apply any or all of these exercises to your own environment.
+	</para>
+
+	<para>
+	Every assignment case can be implemented far more creatively, but remember that the solutions you
+	create are designed to demonstrate a particular solution possibility. With experience, you should
+	find much improved solutions compared with those presented here. By the time you complete this book,
+	you should aim to be a Samba expert, so do attempt to find better solutions and try them as you work your
+	way through the examples.
+	</para>
+
+</sect1>
+<sect1>
+	<title>Assignment Tasks</title>
+
+	<para>
+	Each case presented highlights different aspects of Windows networking for which a simple 
+	Samba-based solution can be provided. Each has subtly different requirements taken from real-world cases.
+	The cases are briefly reviewed to cover important points. Instructions are based
+	on the assumption that the official Samba Team RPM package has been installed.
+	</para>
+
+	<para>
+	This chapter has three assignments built around fictitious companies: 
+	</para>
+
+	<para>
+	<itemizedlist>
+		<listitem><para>A drafting office</para></listitem>
+		<listitem><para>A charity administration office</para></listitem>
+		<listitem><para>An accounting office</para></listitem>
+	</itemizedlist>
+	</para>
+
+	<para>
+	Let's get started.
+	</para>
+
+	<sect2>
+	<title>Drafting Office</title>
+
+	<para>
+	Our fictitious company is called <emphasis>Abmas Design, Inc.</emphasis> This is a three-person
+	computer-aided design (CAD) business that often has more work than can be handled. The 
+	business owner hires contract draftspeople from wherever he can. They bring their own 
+	notebook computers into the office. There are four permanent drafting machines. Abmas has a 
+	collection of over 10 years of plans that must be available for all draftsmen to reference. 
+	Abmas hires the services of an experienced network engineer to update the 
+	plans that are stored on a central server one day per month. She knows how to upload 
+	plans from each machine. The files available from the server must remain read-only. 
+	Anyone should be able to access the plans at any time and without barriers or difficulty.
+	</para>
+
+	<para><indexterm><primary>Red Hat</primary></indexterm>
+		<indexterm><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 Fedora CoreX and
+	have upgraded Samba to version 3.0.20 using the RPM package that is provided from the Samba
+	<ulink url="http://www.samba.org">FTP</ulink> sites. (Note: Fedora CoreX indicates your favorite
+	version.)
+	</para>
+
+	<para><indexterm>
+	    <primary>consultant</primary>
+	  </indexterm>
+	The four permanent drafting machines (Microsoft Windows workstations) have attached printers 
+	and plotters that are shared on a peer-to-peer basis by any and all network users. The intent 
+	is to continue to share printers in this manner. The three permanent staff work together with 
+	all contractors to store all new work on one PC. A daily copy is made of the work storage 
+	area to another PC for safekeeping.  When the network consultant arrives, the weekly work 
+	area is copied to the central server and the files are removed from the main weekly storage 
+	machine. The office works best with this arrangement and does not want to change anything. 
+	Old habits are too ingrained.
+	</para>
+
+		<sect3>
+		<title>Dissection and Discussion</title>
+
+		<para>
+		<indexterm><primary>file server</primary><secondary>read-only</secondary></indexterm>
+		The requirements for this server installation demand simplicity. An anonymous read-only
+		file server adequately meets all needs. The network consultant determines how
+		to upload all files from the weekly storage area to the server. This installation should
+		focus only on critical aspects of the installation.
+		</para>
+
+		<para>
+		It is not necessary to have specific users on the server. The site has a method for storing
+		all design files (plans). Each plan is stored in a directory that is named YYYYWW,<footnote><para>
+		This information is given purely as an example of how data may be stored in such a way that it
+		will be easy to locate records at a later date. The example is not meant to imply any instructions
+		that may be construed as essential to the design of the solution; this is something you will almost
+		certainly want to determine for yourself.</para></footnote> where
+		YYYY is the year, and WW is the week of the year. This arrangement allows work to be stored
+		by week of year to preserve the filing technique the site is familiar with.
+		There is also a customer directory that is alphabetically listed. At the top level are 26
+		directories (A-Z), in each is a second-level of directory for the first plus second letters of the name
+		(A-Z); inside each is a directory by the customers' name. Inside each directory is a symbolic
+		link to each design drawing or plan. This way of storing customer data files permits all
+		plans to be located both by customer name and by the date the work was performed, without
+		demanding the disk space that would be needed if a duplicate file copy were to be stored. 
+		The share containing the plans is called <emphasis>Plans</emphasis>.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Implementation</title>
+
+		<para>
+		It is assumed that the server is fully installed and ready for installation and 
+		configuration of Samba 3.0.20 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 hostname of the server used is <constant>server</constant>.
+		</para>
+
+		<procedure>
+		<title>Samba Server Configuration</title>
+
+			<step><para>
+			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>
+
+			<step><para>
+			<indexterm><primary>RPM</primary><secondary>install</secondary></indexterm>
+			<indexterm><primary>package</primary></indexterm>
+			Install the RPM package using either the Red Hat Linux preferred GUI
+			tool or the <command>rpm</command>:
+<screen>
+&rootprompt; rpm -Uvh samba-3.0.20-1.i386.rpm
+</screen>
+			</para></step>
+
+			<step><para>
+			Create a mount point for the file system that will be used to store all data files.
+			You can create a directory called <filename>/plans</filename>:
+<screen>
+&rootprompt; mkdir /plans
+&rootprompt; chmod 755 /plans
+</screen>
+			The 755 permissions on this directory (mount point) permit the owner to read, write,
+			and execute, and the group and everyone else to read and execute only.
+			</para>
+
+			<para>
+			<indexterm><primary>file system</primary><secondary>Ext3</secondary></indexterm>
+			Use Red Hat Linux system tools (refer to Red Hat instructions)
+			to format the 160GB hard drive with a suitable file system. An Ext3 file system
+			is suitable. Configure this drive to automatically mount using the <filename>/plans</filename>
+			directory as the mount point.
+			</para></step>
+
+			<step><para>
+			Install the &smb.conf; file shown in <link linkend="draft-smbconf"/> in the
+			<filename>/etc/samba</filename> directory.
+
+<example id="draft-smbconf">
+<title>Drafting Office &smb.conf; File</title>
+<smbconfblock>
+<smbconfcomment>Global Parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="security">SHARE</smbconfoption>
+
+<smbconfsection name="[Plans]"/>
+<smbconfoption name="path">/plans</smbconfoption>
+<smbconfoption name="read only">Yes</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+</smbconfblock>
+</example>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>/etc/hosts</primary></indexterm>
+			Verify that the <filename>/etc/hosts</filename> file contains the following entry:
+<screen>
+192.168.1.1	server
+</screen>
+
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>samba</primary><secondary>starting samba</secondary></indexterm>
+			<indexterm><primary>chkconfig</primary></indexterm>
+			<indexterm><primary>starting samba</primary></indexterm>
+			Use the standard system tool to start Samba and to configure it to restart
+			automatically at every system reboot. For example,
+<screen>
+&rootprompt; chkconfig smb on
+&rootprompt; /etc/rc.d/init.d/smb restart
+</screen>
+			</para></step>
+
+		</procedure>
+
+		<procedure>
+		<title>Windows Client Configuration</title>
+
+			<step><para>
+			Make certain that all clients are set to the same network address range as
+			used for the Samba server. For example, one client might have an IP
+			address 192.168.1.10.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>netmask</primary></indexterm>
+			Ensure that the netmask used on the Windows clients matches that used
+			for the Samba server. All clients must have the same netmask, such as
+			255.255.255.0.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>workgroup</primary></indexterm>
+			Set the workgroup name on all clients to <constant>MIDEARTH</constant>.
+			</para></step>
+
+			<step><para>
+			Verify on each client that the machine called <constant>SERVER</constant>
+			is visible in the <guimenu>Network Neighborhood</guimenu>, that it is
+			possible to connect to it and see the share <guimenuitem>Plans</guimenuitem>,
+			and that it is possible to open that share to reveal its contents.
+			</para></step>
+
+		</procedure>
+
+		</sect3>
+
+		<sect3 id="validate1">
+		<title>Validation</title>
+
+		<para>
+		<indexterm><primary>validation</primary></indexterm>
+		The first priority in validating the new Samba configuration should be to check
+		that Samba answers on the loop-back interface. Then it is time to check that Samba
+		answers its own name correctly. Last, check that a client can connect to the Samba
+		server.
+		</para>
+
+		<procedure>
+			<step><para>
+			<indexterm><primary>smbd</primary></indexterm>
+			<indexterm><primary>daemon</primary></indexterm>
+			<indexterm><primary>smbclient</primary></indexterm>
+			To check the ability to access the <command>smbd</command> daemon
+			services, execute the following:
+<screen>
+&rootprompt; smbclient -L localhost -U%
+        Sharename     Type     Comment
+        ---------     ----     -------
+        Plans         Disk
+        IPC$          IPC      IPC Service (Samba 3.0.20)
+        ADMIN$        IPC      IPC Service (Samba 3.0.20)
+
+        Server             Comment
+        ---------          -------
+        SERVER             Samba 3.0.20
+
+        Workgroup          Master
+        ---------          --------
+        MIDEARTH           SERVER 
+</screen>
+			<indexterm><primary>loopback</primary></indexterm>
+			<indexterm><primary>NULL connection</primary></indexterm>
+			This indicates that Samba is able to respond on the loopback interface to
+			a NULL connection. The <parameter>-U%</parameter> means send an empty
+			username and an empty password. This command should be repeated after
+			Samba has been running for 15 minutes.
+			</para></step>
+
+			<step><para>
+			Now verify that Samba correctly handles being passed a username
+			and password, and that it answers its own name. Execute the following:
+<screen>
+&rootprompt; smbclient -L server -Uroot%password
+</screen>
+			The output should be identical to the previous response. Samba has been
+			configured to ignore all usernames given; instead it uses the
+			<parameter>guest account</parameter> for all connections.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>Windows Explorer</primary></indexterm>
+			<indexterm><primary>Network Neighborhood</primary></indexterm>
+			From the Windows 9x/Me client, launch Windows Explorer: 
+			<menuchoice>
+				<guiicon>[Desktop: right-click] Network Neighborhood</guiicon>
+				<guimenu>Explore</guimenu>
+				<guimenuitem>[Left Panel]  [+] Entire Network</guimenuitem>
+				<guimenuitem>[Left Panel] [+] Server</guimenuitem>
+				<guimenuitem>[Left Panel] [+] Plans</guimenuitem>
+			</menuchoice>. In the right panel you should see the files and directories
+			(folders) that are in the <guiicon>Plans</guiicon> share.
+			</para></step>
+		</procedure>
+
+		</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Charity Administration Office</title>
+
+	<para>
+	The fictitious charity organization is called <emphasis>Abmas Vision NL</emphasis>. This office
+	has five networked computers. Staff are all volunteers, staff changes are frequent.
+	Ms. Amy May, the director of operations, wants a no-hassle network. Anyone should be able to
+	use any PC. Only two Windows applications are used: a custom funds tracking and management package
+	that stores all files on the central server and Microsoft Word. The office prepares mail-out
+	letters, invitations, and thank-you notes. All files must be stored in perpetuity.
+	The custom funds tracking and management (FTM) software is configured to use a server named
+	<constant>SERVER</constant>, a share named <constant>FTMFILES</constant>, and a printer queue
+	named <constant>PRINTQ</constant> that uses preprinted stationery, thus demanding a
+	dedicated printer. This printer does not need to be mapped to a local printer on the workstations.
+	</para>
+
+	<para>
+	The FTM software has been in use since the days of Windows 3.11. The software was configured
+	by the vendor who has since gone out of business. The identities of the file
+	server and the printer are hard-coded in a configuration file that was created using a
+	setup tool that the vendor did not provide to Abmas Vision NL or to its predecessors. The
+	company that produced the software is no longer in business. In order to avoid risk of
+	any incompatibilities, the share name and the name of the target print queue must be set
+	precisely as the application expects. In fact, share names and print queue names
+	should be treated as case insensitive (i.e., case does not matter), but Abmas Vision advises
+	that if the share name is not in lowercase, the application claims it cannot find the
+	file share.
+	</para>
+
+	<para>
+	<indexterm><primary>print queue</primary></indexterm>
+	<indexterm><primary>print spooler</primary></indexterm>
+	Printer handling in Samba results in a significant level of confusion. Samba presents to the
+	MS Windows client only a print queue. The Samba <command>smbd</command> process passes a
+	print job sent to it from the Windows client to the native UNIX printing system. The native
+	UNIX printing system (spooler) places the job in a print queue from which it is
+	delivered to the printer. In this book, network diagrams refer to a printer by the name 
+	of the print queue that services that printer. It does not matter what the fully qualified 
+	name (or the hostname) of a network-attached printer is. The UNIX print spooler is configured 
+	to correctly deliver all jobs to the printer.
+	</para>
+
+	<para>
+	This organization has a policy forbidding use of privately owned computers on site as a measure
+	to prevent leakage of confidential information. Only the five PCs owned by Abmas Vision NL are
+	used on this network.
+	</para>
+
+	<para>
+	<indexterm><primary>SUSE Enterprise Linux Server</primary></indexterm>
+	The central server was donated by a local computer store. It is a dual processor Pentium-III
+	server, has 1GB RAM, a 3-Ware IDE RAID Controller that has four 200GB IDE hard drives, and a
+	100-base-T network card. The office has 100-base-T permanent network connections that go to
+	a central hub, and all equipment is new. The five network computers all are equipped with Microsoft
+	Windows Me. Funding is limited, so the server has no operating system on it. You have approval
+	to install Samba on Linux, provided 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 9 and
+	have upgraded Samba to version 3.0.20.
+	</para>
+
+		<sect3>
+		<title>Dissection and Discussion</title>
+
+		<para>
+		<indexterm><primary>force user</primary></indexterm>
+		<indexterm><primary>nt acl support</primary></indexterm>
+		<indexterm><primary>UID</primary></indexterm>
+		<indexterm><primary>Posix</primary></indexterm>
+		This installation demands simplicity. Frequent turnover of volunteer staff indicates that
+		a network environment that requires users to logon might be problematic. It is suggested that the
+		best solution for this office would be one where the user can log onto any PC with any username
+		and password. Samba can accommodate an office like this by using the <parameter>force user</parameter>
+		parameter in share and printer definitions. Using the <parameter>force user</parameter>
+		parameter ensures that all files are owned by same user identifier (UID) and thus that there
+		will never be a problem with file access due to file access permissions. Additionally, you elect
+		to use the <parameter>nt acl support = No</parameter> option to ensure that
+		access control lists (Posix type) cannot be written to any file or directory. This prevents
+		an inadvertent ACL from overriding actual file permissions.
+		</para>
+
+		<para>
+		<indexterm><primary>SUID</primary></indexterm>
+		<indexterm><primary>SGID</primary></indexterm>
+		<indexterm><primary>security</primary><secondary>share mode</secondary></indexterm>
+		This organization is a prime candidate for Share Mode security. The <parameter>force user</parameter>
+		allows all files to be owned by the same user and group. In addition, it would not hurt to
+		set SUID and set SGID shared directories. This means that all new files that are created, no matter
+		who creates it, are owned by the owner or group of the directory in which they are created.
+		For further information regarding the significance of the SUID/SGID settings, see <link
+		linkend="appendix"/>, <link linkend="ch12-SUIDSGID"/>.
+		</para>
+
+		<para>
+		<indexterm><primary>CUPS</primary></indexterm>
+		<indexterm><primary>printing</primary><secondary>raw</secondary></indexterm>
+		<indexterm><primary>Red Hat Linux</primary></indexterm>
+		<indexterm><primary>SUSE Linux</primary></indexterm>
+		All client workstations print to a print queue on the server. This ensures that print jobs
+		continue to print in the event that a user shuts down the workstation immediately after
+		sending a job to the printer. Today, both Red Hat Linux and SUSE Linux use CUPS-based printing. 
+		Older Linux systems offered a choice between the LPRng printing system or CUPS. It appears, however,
+		that CUPS has become the leading UNIX printing technology.
+		</para>
+
+		<para>
+		<indexterm><primary>print queue</primary></indexterm>
+		The print queues are set up as <constant>Raw</constant> devices, which means that CUPS will 
+		not do intelligent print processing, and vendor-supplied drivers must be installed locally on the 
+		Windows clients.
+		</para>
+
+		<para>
+		The hypothetical software, FTM, is representative of 
+		custom-built software that directly uses a NetBIOS interface. Most such software originated in
+		the days of MS/PC DOS. NetBIOS names are uppercase (and functionally are case insensitive), 
+		so some old software applications would permit only uppercase names to be entered.
+		Some such applications were later ported to MS Windows but retain the uppercase network
+		resource naming conventions because customers are familiar with that. We made the decision
+		to name shares and print queues for this application in uppercase for the same reason.
+		Nothing would break if we were to use lowercase names, but that decision might create a need
+		to retrain staff &smbmdash; something well avoided at this time.
+		</para>
+
+		<para>
+		NetBIOS networking does not print directly to a printer. Instead, all printing is done to a
+		print queue. The print spooling system is responsible for communicating with the physical
+		printer. In this example, therefore, the resource called <constant>PRINTQ</constant>
+		really is just a print queue. The name of the print queue is representative of
+		the device to which the print spooler delivers print jobs.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Implementation</title>
+
+		<para>
+		It is assumed that the server is fully installed and ready for configuration of
+		Samba 3.0.20 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 hostname of the server used is <constant>server</constant>.
+		The office network is built as shown in <link linkend="charitynet"/>.
+		</para>
+
+		<figure id="charitynet">
+			<title>Charity Administration Office Network</title>
+			<imagefile scale="80">Charity-Network</imagefile>
+		</figure>
+
+		<procedure>
+		<title>Samba Server Configuration</title>
+
+			<step><para>
+			<indexterm><primary>groupadd</primary></indexterm>
+			Create a group account for office file storage:
+<screen>
+&rootprompt; groupadd office
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>useradd</primary></indexterm>
+			<indexterm><primary>passwd</primary></indexterm>
+			Create a user account for office file storage:
+<screen>
+&rootprompt; useradd -m abmas 
+&rootprompt; passwd abmas 
+Changing password for abmas.
+New password: XXXXXXXX
+Re-enter new password: XXXXXXXX
+Password changed
+</screen>
+			where XXXXXXXX is a secret password.
+			</para></step>
+
+				<step><para>
+				Use the 3-Ware IDE RAID Controller firmware utilities to configure the four 200GB
+				drives as a single RAID level 5 drive, with one drive set aside as the hot spare.
+				(Refer to the 3-Ware RAID Controller Manual for the manufacturer's preferred procedure.)
+				The resulting drive has a capacity of approximately 500GB of usable space.
+				</para></step>
+
+				<step><para>
+				<indexterm><primary>permissions</primary></indexterm>
+				Create a mount point for the file system that can be used to store all data files.
+				Create a directory called <filename>/data</filename>:
+<screen>
+&rootprompt; mkdir /data
+&rootprompt; chmod 755 /data
+</screen>
+				The 755 permissions on this directory (mount point) permit the owner to read, write, and execute,
+				and the group and everyone else to read and execute only.
+				</para></step>
+
+				<step><para>
+				Use SUSE Linux system tools (refer to the SUSE Administrators Guide for correct
+				procedures) to format the partition with a suitable file system. The reiserfs file system
+				is suitable. Configure this drive to automount using the <filename>/data</filename>
+				directory as the mount point. It must be mounted before proceeding.
+				</para></step>
+
+				<step><para>
+				Under the directory called <filename>/data</filename>, create two directories
+				named <filename>ftmfiles</filename> and <filename>officefiles</filename>, and set
+				ownership and permissions:
+<screen>
+&rootprompt; mkdir -p /data/{ftmfiles,officefiles/{letters,invitations,misc}}
+&rootprompt; chown -R abmas:office /data
+&rootprompt; chmod -R ug+rwxs,o-w,o+rx /data
+</screen>
+				These demonstrate compound operations. The <command>mkdir</command> command
+ 				creates in one step these directories:
+<programlisting>
+/data/fmtfiles
+/data/officefiles
+/data/officefiles/letters
+/data/officefiles/invitations
+/data/officefiles/misc
+</programlisting>
+				<indexterm><primary>TOSHARG2</primary></indexterm>
+				The <command>chown</command> operation sets the owner to the user <constant>abmas</constant>
+				and the group to <constant>office</constant> on all directories just created.  It recursively
+				sets the permissions so that the owner and group have SUID/SGID with read, write, and execute
+				permission, and everyone else has read and execute permission. This means that all files and
+				directories are created with the same owner and group as the directory in which they are
+				created. Any new directories created still have the same owner, group, and permissions as the
+				directory they are in. This should eliminate all permissions-based file access problems.  For
+				more information on this subject, refer to TOSHARG2<footnote>The Official Samba-3 HOWTO and
+				Reference Guide, Chapter 15, File, Directory and Share Access Controls.</footnote> or refer
+				to the UNIX man page for the <command>chmod</command> and the <command>chown</command> commands.
+				</para></step>
+
+				<step><para>
+				Install the &smb.conf; file shown in <link linkend="charity-smbconfnew"/> in the
+				<filename>/etc/samba</filename> directory. This newer &smb.conf; file uses user-mode security
+				and is more suited to the mode of operation of Samba-3 than the older share-mode security
+				configuration that was shown in the first edition of this book.
+				</para>
+
+				<para>
+				Note: If you want to use the older-style configuration that uses share-mode security, you
+				can install the file shown in <link linkend="charity-smbconf"/> in the
+				<filename>/etc/samba</filename> directory.
+				</para></step>
+
+				<step><para>
+				<indexterm><primary>smbd</primary></indexterm>
+				We must ensure that the <command>smbd</command> can resolve the name of the Samba
+				server to its IP address. Verify that the <filename>/etc/hosts</filename> file
+				contains the following entry:
+<screen>
+192.168.1.1	server
+</screen>
+				</para></step>
+
+				<step><para>
+				Configure the printers with the IP address as shown in <link linkend="charitynet"/>.
+				Follow the instructions in the manufacturer's manual to permit printing to port 9100
+				so that the CUPS spooler can print using raw mode protocols.
+				</para></step>
+
+				<step><para>
+				<indexterm><primary>lpadmin</primary></indexterm>
+				Configure the CUPS Print Queues:
+<screen>
+&rootprompt; lpadmin -p PRINTQ -v socket://192.168.1.20:9100 -E
+&rootprompt; lpadmin -p hplj5 -v socket://192.168.1.30:9100 -E
+</screen>
+				This creates the necessary print queues with no assigned print filter.
+				</para></step>
+
+				<step><para>
+				<indexterm><primary>mime type</primary></indexterm>
+				<indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
+				<indexterm><primary>application/octet-stream</primary></indexterm>
+				Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
+<screen>
+application/octet-stream     application/vnd.cups-raw      0     -
+</screen>
+				</para></step>
+
+				<step><para>
+				<indexterm><primary>/etc/cups/mime.types</primary></indexterm>
+				Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
+<screen>
+application/octet-stream
+</screen>
+				</para></step>
+
+				<step><para>
+				<indexterm><primary>starting samba</primary></indexterm>
+				Use the standard system tool to start Samba and CUPS to configure them to restart
+				automatically at every system reboot. For example,
+				</para>
+
+				<para>
+				<indexterm><primary>starting samba</primary></indexterm>
+				<indexterm><primary>starting CUPS</primary></indexterm>
+				<indexterm><primary>chkconfig</primary></indexterm>
+<screen>
+&rootprompt; chkconfig smb on
+&rootprompt; chkconfig cups on
+&rootprompt; /etc/rc.d/init.d/smb restart
+&rootprompt; /etc/rc.d/init.d/cups restart
+</screen>
+				</para></step>
+
+			</procedure>
+
+<example id="charity-smbconfnew">
+<title>Charity Administration Office &smb.conf; New-style File</title>
+<smbconfblock>
+<smbconfcomment>Global Parameters - Newer Configuration</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="printing">CUPS</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="map to guest">Bad User</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="wins support">yes</smbconfoption>
+
+<smbconfsection name="[FTMFILES]"/>
+<smbconfoption name="comment">Funds Tracking &amp; Management Files</smbconfoption>
+<smbconfoption name="path">/data/ftmfiles</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="force user">abmas</smbconfoption>
+<smbconfoption name="force group">office</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="nt acl support">No</smbconfoption>
+
+<smbconfsection name="[office]"/>
+<smbconfoption name="comment">General Office Files</smbconfoption>
+<smbconfoption name="path">/data/officefiles</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="force user">abmas</smbconfoption>
+<smbconfoption name="force group">office</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="nt acl support">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">Print Temporary Spool Configuration</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="charity-smbconf">
+<title>Charity Administration Office &smb.conf; Old-style File</title>
+<smbconfblock>
+<smbconfcomment>Global Parameters - Older Style Configuration</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="security">SHARE</smbconfoption>
+<smbconfoption name="printing">CUPS</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="disable spoolss">Yes</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="wins support">yes</smbconfoption>
+
+<smbconfsection name="[FTMFILES]"/>
+<smbconfoption name="comment">Funds Tracking &amp; Management Files</smbconfoption>
+<smbconfoption name="path">/data/ftmfiles</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="force user">abmas</smbconfoption>
+<smbconfoption name="force group">office</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="nt acl support">No</smbconfoption>
+
+<smbconfsection name="[office]"/>
+<smbconfoption name="comment">General Office Files</smbconfoption>
+<smbconfoption name="path">/data/officefiles</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="force user">abmas</smbconfoption>
+<smbconfoption name="force group">office</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="nt acl support">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">Print Temporary Spool Configuration</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+			<procedure>
+			<title>Windows Client Configuration</title>
+
+				<step><para>
+				Configure clients to the network settings shown in <link linkend="charitynet"/>.
+				</para></step>
+
+				<step><para>
+				Ensure that the netmask used on the Windows clients matches that used
+				for the Samba server. All clients must have the same netmask, such as
+				<constant>255.255.255.0</constant>.
+				</para></step>
+
+				<step><para>
+				<indexterm><primary>WINS</primary></indexterm>
+				On all Windows clients, set the WINS Server address to <constant>192.168.1.1</constant>,
+				the IP address of the server.
+				</para></step>
+
+				<step><para>
+				Set the workgroup name on all clients to <constant>MIDEARTH</constant>.
+				</para></step>
+
+				<step><para>
+				<indexterm><secondary>logon</secondary></indexterm>
+				Install the <quote>Client for Microsoft Networks.</quote> Ensure that the only option
+				enabled in its properties is the option <quote>Logon and restore network connections.</quote>
+				</para></step>
+
+				<step><para>
+				Click <guibutton>OK</guibutton> when you are prompted to reboot the system. Reboot the
+				system, then log on using any username and password you choose.
+				</para></step>
+
+				<step><para>
+				<indexterm><primary>My Network Places</primary></indexterm>
+				Verify on each client that the machine called <constant>SERVER</constant>
+				is visible in <guimenu>My Network Places</guimenu>, that it is
+				possible to connect to it and see the share <guimenuitem>office</guimenuitem>,
+				and that it is possible to open that share to reveal its contents.
+				</para></step>
+
+				<step><para>
+				<indexterm><primary>password caching</primary></indexterm>
+				<indexterm><primary>regedit</primary></indexterm>
+				Disable password caching on all Windows 9x/Me machines using the registry change file
+				shown in <link linkend="MEreg"/>. Be sure to remove all files that have the
+				<filename>PWL</filename> extension that are in the <filename>C:\WINDOWS</filename>
+				directory.
+<example id="MEreg">
+<title>Windows Me &smbmdash; Registry Edit File: Disable Password Caching</title>
+<screen>
+REGEDIT4
+
+[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
+	Windows\CurrentVersion\Policies\Network]
+	"DisablePwdCaching"=dword:00000001
+</screen>
+</example>
+				The best way to apply this change is to save the patch in a file called 
+				<filename>ME-dpwc.reg</filename> and then execute:
+<screen>
+C:\WINDOWS: regedit ME-dpwc.reg
+</screen>
+				</para></step>
+
+				<step><para>
+				Instruct all users to log onto the workstation using a name and password of their own
+				choosing. The Samba server has been
+				configured to ignore the username and password given.
+				</para></step>
+
+				<step><para>
+				On each Windows Me workstation, configure a network drive mapping to drive <filename>G:</filename>
+				that redirects to the uniform naming convention (UNC) resource 
+				<filename>\\server\office</filename>. Make this a permanent drive connection:
+				</para>
+					<procedure>
+						<step><para>
+							<menuchoice>
+								Right-click <guimenu>My Network</guimenu>
+								<guimenuitem>Map Network Drive...</guimenuitem>
+							</menuchoice>
+						</para></step>
+
+						<step><para>
+						In the box labeled <quote>Drive:</quote>, type G.
+						</para></step>
+
+						<step><para>
+						In the box labeled <quote>Path:</quote>, enter 
+						<filename>\\server\officefiles</filename>.
+						</para></step>
+
+						<step><para>
+						Click <guimenuitem>Reconnect at logon</guimenuitem>.
+						Click <guibutton>OK</guibutton>.
+						</para></step>
+
+					</procedure>
+				</step>
+
+				<step><para>
+				On each workstation, install the FTM software following the
+				manufacturer's instructions.
+				</para>
+					<procedure>
+					<step><para>
+					During installation, you are prompted for the name of the Windows 98
+					server. Enter the name <constant>SERVER</constant>.
+					</para></step>
+					<step><para>
+					You are prompted for the name of the data share.
+					The prompt defaults to <constant>FTMFILES</constant>. Press enter to accept the default value.
+					</para></step>
+					<step><para>
+					You are now prompted for the print queue name. The default prompt is the name of
+					the server you entered (<constant>SERVER</constant> as follows:
+					<constant>\\SERVER\PRINTQ</constant>). Simply accept the default and press enter to
+					continue. The software now completes the installation.
+					</para></step>
+					</procedure>
+				</step>
+
+				<step><para>
+				Install an office automation software package of the customer's choice. Either Microsoft
+				Office 2003 Standard or OpenOffice 1.1.0 suffices for any functions the office may
+				need to perform. Repeat this on each workstation.
+				</para></step>
+
+				<step><para>
+				Install a printer on each workstation using the following steps:
+				</para>
+
+					<procedure>
+						<step><para>
+						Click <menuchoice>
+							<guimenu>Start</guimenu>
+							<guimenuitem>Settings</guimenuitem>
+							<guimenuitem>Printers</guimenuitem>
+							<guiicon>Add Printer</guiicon>
+							<guibutton>Next</guibutton>
+							</menuchoice>. Do not click <guimenuitem>Network printer</guimenuitem>.
+							Ensure that <guimenuitem>Local printer</guimenuitem> is selected.
+						</para></step>
+
+						<step><para>
+						Click <guibutton>Next</guibutton>. In the Manufacturer: panel, select
+						<constant>HP</constant>. In the Printers: panel, select the printer called
+						<constant>HP LaserJet 5/5M Postscript</constant>. Click <guibutton>Next</guibutton>.
+						</para></step>
+
+						<step><para>
+						In the Available ports: panel, select <constant>FILE:</constant>. Accept the
+						default printer name by clicking <guibutton>Next</guibutton>. When asked,
+						<quote>Would you like to print a test page?</quote>, click
+						<guimenuitem>No</guimenuitem>. Click <guibutton>Finish</guibutton>.
+						</para></step>
+
+						<step><para>
+						You may be prompted for the name of a file to print to. If so, close the
+						dialog panel. Right-click <menuchoice>
+							<guiicon>HP LaserJet 5/5M Postscript</guiicon>
+							<guimenuitem>Properties</guimenuitem>
+							<guisubmenu>Details (Tab)</guisubmenu>
+							<guimenuitem>Add Port</guimenuitem>
+							</menuchoice>.
+						</para></step>
+
+						<step><para>
+						In the Network panel, enter the name of
+						the print queue on the Samba server as follows: <constant>\\SERVER\hplj5</constant>.
+						Click <menuchoice> 
+							<guibutton>OK</guibutton>
+							<guibutton>OK</guibutton>
+							</menuchoice> to complete the installation.
+						</para></step>
+
+						<step><para>
+						It is a good idea to test the functionality of the complete installation before
+						handing the newly configured network over to the Charity Administration Office
+						for production use.
+						</para></step>
+
+					</procedure>
+
+				</step>
+
+			</procedure>
+
+		</sect3>
+
+		<sect3>
+		<title>Validation</title>
+
+		<para>
+		Use the same validation process as was followed in <link linkend="validate1"/>.
+		</para>
+
+		</sect3>
+
+	</sect2>
+
+	<sect2 id="AccountingOffice">
+	<title>Accounting Office</title>
+
+	<para>
+	Abmas Accounting is a 40-year-old family-run business. There are nine permanent
+	computer users. The network clients were upgraded two years ago. All computers run Windows 2000
+	Professional. This year the server will be upgraded from an old Windows NT4 server (actually
+	running Windows NT4 Workstation, which worked fine for fewer than 10 users) that has
+	run in workgroup (standalone) mode, to a new Linux server running Samba.
+	</para>
+
+	<para>
+	The office does not want a Domain Server. Mr. Alan Meany wants to keep the Windows 2000 Professional
+	clients running as workgroup machines so that any staff member can take a machine home and keep 
+	working.  It has worked well so far, and your task is to replace the old server. All users have 
+	their own workstation logon (you configured it that way when the machines were installed). 
+	Mr. Meany wants the new system to operate the same way as the old Windows NT4 server &smbmdash; users 
+	cannot access each others' files, but he can access everyone's files. Each person's work files are 
+	in a separate share on the server. Users log on to their Windows workstation with their username 
+	and enter an assigned password; they do not need to enter a password when accessing their files 
+	on the server.
+	</para>
+
+	<para>
+	<indexterm><primary>Red Hat Linux</primary></indexterm>
+	The new server will run Red Hat Fedora Core2. You should install Samba-3.0.20 and 
+	copy all files from 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
+	replace the server, <quote>but leave everything else alone to avoid staff unrest.</quote>
+	</para>
+
+	<para>
+	You have tried to educate Mr. Meany and found that he has no desire to understand networking.
+	He believes that Windows for Workgroups 3.11 was <quote>the best server Microsoft ever sold
+	</quote> and that Windows NT and 2000 are <quote>too fang-dangled complex!</quote>
+	</para>
+
+		<sect3>
+		<title>Dissection and Discussion</title>
+
+			<para>
+			<indexterm><primary>security</primary><secondary>user mode</secondary></indexterm>
+			The requirements of this network installation are not unusual. The staff are not interested in the
+			details of networking. Passwords are never changed. In this example solution, we demonstrate the use
+			of User Mode security in a simple context. Directories should be set SGID to ensure that members
+			of a common group can access the contents. Each user has his or her own share to which only they
+			can connect. Mr. Meany's share will be a top-level directory above the share point for each employee.
+			Mr. Meany is a member of the same group as his staff and can access their work files.
+			The well-used HP LaserJet 4 is available as a service called <constant>hplj</constant>.
+			</para>
+
+			<para>
+			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>
+
+		<sect3 id="AcctgNet">
+		<title>Implementation</title>
+
+		<para>
+		The workstations have fixed IP addresses. The old server runs Windows NT4 Workstation, so it 
+		cannot be running as a WINS server. It is best that the new configuration preserves the same
+		configuration. The office does not use Internet access, so security really is not an issue.
+		</para>
+
+		<para>
+		The core information regarding the users, their passwords, the directory share point, and the
+		share name is given in <link linkend="acctingnet"/>. The overall network topology is shown in
+		<link linkend="acctingnet2"/>. All machines have been configured as indicated prior to the
+		start of Samba configuration. The following prescriptive steps may now commence.
+		</para>
+
+		<figure id="acctingnet2">
+			<title>Accounting Office Network Topology</title>
+			<imagefile scale="85">AccountingNetwork</imagefile>
+		</figure>
+
+		<table id="acctingnet">
+			<title>Accounting Office Network Information</title>
+			<tgroup cols="6">
+				<colspec align="left"/>
+				<colspec align="left"/>
+				<colspec align="left"/>
+				<colspec align="left"/>
+				<colspec align="left"/>
+				<colspec align="left"/>
+				<thead>
+					<row>
+						<entry>User</entry>
+						<entry>Login-ID</entry>
+						<entry>Password</entry>
+						<entry>Share Name</entry>
+						<entry>Directory</entry>
+						<entry>Wkst</entry>
+					</row>
+				</thead>
+				<tbody>
+					<row>
+						<entry>Alan Meany</entry>
+						<entry>alan</entry>
+						<entry>alm1961</entry>
+						<entry>alan</entry>
+						<entry>/data</entry>
+						<entry>PC1</entry>
+					</row>
+					<row>
+						<entry>James Meany</entry>
+						<entry>james</entry>
+						<entry>jimm1962</entry>
+						<entry>james</entry>
+						<entry>/data/james</entry>
+						<entry>PC2</entry>
+					</row>
+					<row>
+						<entry>Jeannie Meany</entry>
+						<entry>jeannie</entry>
+						<entry>jema1965</entry>
+						<entry>jeannie</entry>
+						<entry>/data/jeannie</entry>
+						<entry>PC3</entry>
+					</row>
+					<row>
+						<entry>Suzy Millicent</entry>
+						<entry>suzy</entry>
+						<entry>suzy1967</entry>
+						<entry>suzy</entry>
+						<entry>/data/suzy</entry>
+						<entry>PC4</entry>
+					</row>
+					<row>
+						<entry>Ursula Jenning</entry>
+						<entry>ujen</entry>
+						<entry>ujen1974</entry>
+						<entry>ursula</entry>
+						<entry>/data/ursula</entry>
+						<entry>PC5</entry>
+					</row>
+					<row>
+						<entry>Peter Pan</entry>
+						<entry>peter</entry>
+						<entry>pete1984</entry>
+						<entry>peter</entry>
+						<entry>/data/peter</entry>
+						<entry>PC6</entry>
+					</row>
+					<row>
+						<entry>Dale Roland</entry>
+						<entry>dale</entry>
+						<entry>dale1986</entry>
+						<entry>dale</entry>
+						<entry>/data/dale</entry>
+						<entry>PC7</entry>
+					</row>
+					<row>
+						<entry>Bertrand E Paoletti</entry>
+						<entry>eric</entry>
+						<entry>eric1993</entry>
+						<entry>eric</entry>
+						<entry>/data/eric</entry>
+						<entry>PC8</entry>
+					</row>
+					<row>
+						<entry>Russell Lewis</entry>
+						<entry>russ</entry>
+						<entry>russ2001</entry>
+						<entry>russell</entry>
+						<entry>/data/russell</entry>
+						<entry>PC9</entry>
+					</row>
+				</tbody>
+			</tgroup>
+		</table>
+
+		<procedure>
+		<title>Migration from Windows NT4 Workstation System to Samba-3</title>
+
+	    <step><para><indexterm>
+		  <primary>migration</primary>
+		</indexterm>
+			Rename the old server from <constant>CASHPOOL</constant> to <constant>STABLE</constant>
+			by logging onto the console as the <constant>Administrator</constant>. Restart the machine
+			following system prompts.
+			</para></step>
+
+			<step><para>
+			Name the new server <constant>CASHPOOL</constant> using the standard configuration method.
+			Restart the machine following system prompts.
+			</para></step>
+
+			<step><para>
+			Install the latest Samba-3 binary Red Hat Linux RPM that is available from the
+			Samba FTP site.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>group account</primary></indexterm>
+			<indexterm><primary>groupadd</primary></indexterm>
+			Add a group account for the office to use. Execute the following:
+<screen>
+&rootprompt; groupadd accts
+</screen>
+			</para></step>
+
+			<step><para>
+			Install the &smb.conf; file shown<footnote><para>This example uses the 
+			<parameter>smbpasswd</parameter> file in an obtuse way, since the use of 
+			the <parameter>passdb backend</parameter> has not been specified in the &smb.conf; 
+			file. This means that you are depending on correct default behavior.</para></footnote> 
+			in <link linkend="acctconf"/>.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>useradd</primary></indexterm>
+			<indexterm><primary>passwd</primary></indexterm>
+			<indexterm><primary>smbpasswd</primary></indexterm>
+			For each user who uses this system (see <link linkend="acctingnet"/>),
+			execute the following:
+<screen>
+&rootprompt; useradd -m -G accts -c "Name of User" "LoginID"
+&rootprompt; passwd "LoginID"
+Changing password for user "LoginID"
+New Password: XXXXXXXXX	&lt;-- the password from the table
+Retype new password: XXXXXXXXX
+&rootprompt; smbpasswd -a "LoginID"
+New SMB password: XXXXXXXXX &lt;-- the password from the table
+Retype new SMB password: XXXXXXXXX
+Added user "LoginID"
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>data storage</primary></indexterm>
+			Create the directory structure for the file shares by executing the following:
+<screen>
+&rootprompt; mkdir -p /data
+&rootprompt; chown alan /data
+&rootprompt; for i in james suzy ujen peter dale eric jeannie russ
+> do
+> 	mkdir -p /data/$i
+> 	chown $i /data/$i
+> done
+&rootprompt; chgrp -R accts /data
+&rootprompt; chmod -R ug+rwxs,o-r+x /data
+</screen>
+			The data storage structure is now prepared for use.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>lpadmin</primary></indexterm>
+			Configure the CUPS Print Queues:
+<screen>
+&rootprompt; lpadmin -p hplj -v parallel:/dev/lp0 -E
+</screen>
+			This creates the necessary print queues with no assigned print filter.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>mime types</primary></indexterm>
+			<indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
+			Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
+<screen>
+application/octet-stream     application/vnd.cups-raw      0     -
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>/etc/cups/mime.types</primary></indexterm>
+			<indexterm><primary>application/octet-stream</primary></indexterm>
+			Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
+<screen>
+application/octet-stream
+</screen>
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>starting samba</primary></indexterm>
+			Use the standard system tool to start Samba and CUPS to configure them to restart
+			automatically at every system reboot. For example,
+			</para>
+
+			<para>
+			<indexterm><primary>starting samba</primary></indexterm>
+			<indexterm><primary>startingCUPS</primary></indexterm>
+			<indexterm><primary>chkconfig</primary></indexterm>
+<screen>
+&rootprompt; chkconfig smb on
+&rootprompt; chkconfig cups on
+&rootprompt; /etc/rc.d/init.d/smb restart
+&rootprompt; /etc/rc.d/init.d/cups restart
+</screen>
+			</para></step>
+
+			<step><para>
+			On Alan's workstation, use Windows Explorer to migrate the files from the old server
+			to the new server. The new server should appear in the <guimenu>Network Neighborhood</guimenu>
+			with the name of the old server (<constant>CASHPOOL</constant>).
+			</para>
+
+				<procedure>
+
+					<step><para>
+					Log on to Alan's workstation as the user <constant>alan</constant>.
+					</para></step>
+
+					<step><para>
+					Launch a second instance of Windows Explorer and navigate to the share called
+					<guiicon>files</guiicon> on the server called <guimenu>STABLE</guimenu>.
+					</para></step>
+
+					<step><para>
+					Click in the right panel, and press <guimenu>Ctrl-A</guimenu> to select all files and
+					directories. Press <guimenu>Ctrl-C</guimenu> to instruct Windows that you wish to
+					copy all selected items.
+					</para></step>
+
+					<step><para>
+					Launch the Windows Explorer, and navigate to the share called <guiicon>files</guiicon>
+					on the server called <guimenu>CASHPOOL</guimenu>. Click in the right panel, and then press
+					<guimenu>Ctrl-V</guimenu> to commence the copying process.
+					</para></step>
+
+				</procedure>
+			</step>
+
+			<step><para>
+			Verify that the files are being copied correctly from the Windows NT4 machine to the Samba-3 server.
+			This is best done on the Samba-3 server. Check the contents of the directory tree under 
+			<filename>/data</filename> by executing the following command:
+<screen>
+&rootprompt; ls -aR /data
+</screen>
+			Make certain to check the ownership and permissions on all files. If in doubt, execute the following:
+<screen>
+&rootprompt; chown alan /data
+&rootprompt; for i in james suzy ujen peter dale eric jeannie russ
+> do
+> 	chown $i /data/$i
+> done
+&rootprompt; chgrp -R accts /data
+&rootprompt; chmod -R ug+rwxs,o-r+x /data
+</screen>
+			</para></step>
+
+			<step><para>
+			The migration of all data should now be complete. It is time to validate the installation.
+			For this, you should make sure all applications, including printing, work before asking the
+			customer to test drive the new network.
+			</para></step>
+
+		</procedure>
+
+<example id="acctconf">
+<title>Accounting Office Network &smb.conf; Old Style Configuration File</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">BILLMORE</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="disable spoolss">Yes</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+
+<smbconfsection name="[files]"/>
+<smbconfoption name="comment">Work area files</smbconfoption>
+<smbconfoption name="path">/data/%U</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[master]"/>
+<smbconfoption name="comment">Master work area files</smbconfoption>
+<smbconfoption name="path">/data</smbconfoption>
+<smbconfoption name="valid users">alan</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">Print Temporary Spool Configuration</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+		</sect3>
+	</sect2>
+</sect1>
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	The following questions and answers draw from the examples in this chapter.
+	Many design decisions are impacted by the configurations chosen. The intent
+	is to expose some of the hidden implications.
+	</para>
+
+	<qandaset defaultlabel="chap02qa" type="number">
+	<qandaentry>
+	<question>
+
+		<para>
+		What makes an anonymous Samba server more simple than a non-anonymous Samba server?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		In the anonymous server, the only account used is the <constant>guest</constant> account.
+		In a non-anonymous configuration, it is necessary to add real user accounts to both the
+		UNIX system and to the Samba configuration. Non-anonymous servers require additional
+		administration.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		How is the operation of the parameter <parameter>force user</parameter> different from
+		setting the root directory of the share SUID?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The parameter <parameter>force user</parameter> causes all operations on the share to assume the UID
+		of the forced user. The new default GID that applies is the primary GID of the forced user.
+		This gives all users of this resource the actual privilege of the forced user.
+		</para>
+
+		<para>
+		When a directory is set SUID, the operating system forces files that are written within it
+		to be owned by the owner of the directory. While this happens, the user who is using the share
+		has only the level of privilege he or she is assigned within the operating system context.
+		</para>
+
+		<para>
+		The parameter <parameter>force user</parameter> has potential security implications that go
+		beyond the actual share root directory. Be careful and wary of using this parameter.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		When would you both use the per share parameter <parameter>force user</parameter> and set
+		the share root directory SUID?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		You would use both parameters when it is necessary to guarantee that all share handling operations
+		are conducted as the forced user, while all file and directory creation are done as the SUID
+		directory owner.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What is better about CUPS printing than LPRng printing?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		CUPS is a print spooling system that has integrated remote management facilities, provides completely
+		automated print processing/preprocessing, and can be configured to automatically
+		apply print preprocessing filters to ensure that a print job submitted is correctly rendered for the
+		target printer. CUPS includes an image file RIP that supports printing of image files to 
+		non-PostScript printers. CUPS has lots of bells and whistles and is more like a supercharged MS Windows
+		NT/200x print monitor and processor. Its complexity can be eliminated or turbocharged to suit
+		any fancy.
+		</para>
+
+		<para>
+		The LPRng software is an enhanced, extended, and portable implementation of the Berkeley LPR print 
+		spooler functionality. It provides the same interface and meets RFC1179 requirements. LPRng can be
+		configured to act like CUPS, but it is in principle a replacement for the old Berkeley lpr/lpd
+		spooler. LPRng is generally preferred by those who are familiar with Berkeley lpr/lpd.
+		</para>
+
+		<para>
+		Which spooling system is better is a matter of personal taste. It depends on what you want to do and how you want to
+		do it and manage it. Most modern Linux systems ship with CUPS as the default print management system.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		When should Windows client IP addresses be hard-coded?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		When there are few MS Windows clients, little client change, no mobile users, and users are not
+		inclined to tamper with network settings, it is a safe and convenient matter to hard-code Windows
+		client TCP/IP settings. Given that it is possible to lock down the Windows desktop and remove
+		user ability to access network configuration controls, fixed configuration eliminates the need
+		for a DHCP server. This reduces maintenance overheads and eliminates a possible point of network
+		failure.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Under what circumstances is it best to use a DHCP server?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		In network configurations where there are mobile users, or where Windows client PCs move around
+		(particularly between offices or between subnets), it makes complete sense to control all Windows
+		client configurations using a DHCP server. Additionally, when users do tamper with the network
+		settings, DHCP can be used to normalize all client settings. 
+		</para>
+
+		<para>
+		One underappreciated benefit of using a DHCP server to assign all network client
+		device TCP/IP settings is that it makes it a pain-free process to change network TCP/IP
+		settings, change network addressing, or enhance the ability of client devices to
+		benefit from new network services.
+		</para>
+
+		<para>
+		Another benefit of modern DHCP servers is their ability to register dynamically
+		assigned IP addresses with the DNS server. The benefits of Dynamic DNS (DDNS) are considerable in 
+		a large Windows network environment.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What is the purpose of setting the parameter <parameter>guest ok</parameter> on a share?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		If this parameter is set to yes for a service, then no password is required to connect to the service.
+		Privileges are those of the guest account.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		When would you set the global parameter <parameter>disable spoolss</parameter>?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Setting this parameter to <constant>Yes</constant> disables Samba's support for the SPOOLSS set of 
+		MS-RPCs and yields behavior identical to Samba 2.0.x. Windows NT/2000 clients can downgrade to 
+		using LanMan style printing commands. Windows 9x/Me are unaffected by the parameter. However, this 
+		disables the ability to upload printer drivers to a Samba server via the Windows NT/200x Add Printer 
+		Wizard or by using the NT printer properties dialog window. It also disables the capability of 
+		Windows NT/200x clients to download print drivers from the Samba host on demand. Be extremely careful about 
+		setting this parameter.
+		</para>
+
+		<para>
+		The alternate parameter <parameter>use client driver</parameter> applies only to Windows NT/200x clients. It has no 
+		effect on Windows 95/98/Me clients. When serving a printer to Windows NT/200x clients without first installing a valid 
+		printer driver on the Samba host, the client is required to install a local printer driver. From this point on, 
+		the client treats the printer as a local printer and not a network printer connection. This is much the same behavior 
+		that occurs when <parameter>disable spoolss = yes</parameter>.
+		</para>
+
+		<para>
+		Under normal circumstances, the NT/200x client attempts to open the network printer using MS-RPC. Because the client 
+		considers the printer to be local, it attempts to issue the <parameter>OpenPrinterEx()</parameter> call requesting
+		access rights associated with the logged on user. If the user possesses local administrator rights but not root
+		privilege on the Samba host (often the case), the <parameter>OpenPrinterEx()</parameter> call fails. The result is
+		that the client now displays an <quote>Access Denied; Unable to connect</quote> message in the printer queue window
+		(even though jobs may be printed successfully). This parameter MUST not be enabled on a print share that has a valid
+		print driver installed on the Samba server.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why would you disable password caching on Windows 9x/Me clients?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Windows 9x/Me workstations that are set at default (password caching enabled) store the username and
+		password in files located in the Windows master directory. Such files can be scavenged (read off a client
+		machine) and decrypted, thus revealing the user's access credentials for all systems the user may have accessed.
+		It is most insecure to allow any Windows 9x/Me client to operate with password caching enabled.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		The example of Abmas Accounting uses User Mode security. How does this provide anonymous access?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The example used does not provide anonymous access. Since the clients are all Windows 2000 Professional,
+		and given that users are logging onto their machines, by default the client attempts to connect to
+		a remote server using currently logged in user credentials. By ensuring that the user's login ID and
+		password are the same as those set on the Samba server, access is transparent and does not require
+		separate user authentication.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	</qandaset>
+
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-Support.xml b/docs-xml/Samba3-ByExample/SBE-Support.xml
new file mode 100644
index 00000000000..b970bc00f04
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-Support.xml
@@ -0,0 +1,163 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<chapter lang="en-US">
+<title>Samba Support</title>
+
+<para>
+<indexterm><primary>support</primary></indexterm>
+One of the most difficult to answer questions in the information technology industry is, <quote>What is
+support?</quote>. That question irritates some folks, as much as common answers may annoy others.
+</para>
+
+<para>
+<indexterm><primary>customers</primary></indexterm>
+The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to
+an Internet service provider who, instead of listening to the problem to find a solution, blandly replies:
+<quote>Oh, Linux? We do not support Linux!</quote>. It has happened to me, and similar situations happen
+through-out the IT industry. Answers like that are designed to inform us that there are some customers
+that a business just does not want to deal with, and well may we feel the anguish of the rejection that 
+is dished out.
+</para>
+
+<para>
+One way to consider support is to view it as consisting of the right answer, in the right place,
+at the right time, no matter the situation. Support is all that it takes to take away pain, disruption,
+inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk.
+</para>
+
+<para>
+<indexterm><primary>provided services</primary></indexterm>
+<indexterm><primary>services provided</primary></indexterm>
+<indexterm><primary>customer expected</primary></indexterm>
+One of the forces that has become a driving force for the adoption of open source software is the fact that
+many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or
+that have been found wanting for other reasons.
+</para>
+
+<para>
+<indexterm><primary>consumer expects</primary></indexterm>
+<indexterm><primary>problem resolution</primary></indexterm>
+In recognition of the need for needs satisfaction as the primary experience an information technology user or
+consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience
+in respect of problem resolution.
+</para>
+
+<para>
+<indexterm><primary>free support</primary></indexterm>
+<indexterm><primary>paid-for support</primary></indexterm>
+<indexterm><primary>commercial support</primary></indexterm>
+In the open source software arena there are two support options: free support and paid-for (commercial)
+support.
+</para>
+
+	<sect1>
+	<title>Free Support</title>
+
+	<para>
+<indexterm><primary>user groups</primary></indexterm>
+<indexterm><primary>mailing lists</primary></indexterm>
+<indexterm><primary>interactive help</primary></indexterm>
+<indexterm><primary>help</primary></indexterm>
+<indexterm><primary>mutual assistance</primary></indexterm>
+<indexterm><primary>assistance</primary></indexterm>
+	Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help
+	facilities. An example of an interactive dacility is the Internet relay chat (IRC) channels that host user
+	supported mutual assistance.
+	</para>
+
+	<para>
+<indexterm><primary>mailing list</primary></indexterm>
+<indexterm><primary>deployment</primary></indexterm>
+<indexterm><primary>subscription</primary></indexterm>
+<indexterm><primary>IRC</primary></indexterm>
+<indexterm><primary>project</primary></indexterm>
+	The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba deployments.
+	Information regarding subscription to the Samba mailing list can be found on the Samba <ulink
+	url="https://lists.samba.org/mailman/">web</ulink> site. The public mailing list that can be used to obtain
+	free, user contributed, support is called the <literal>samba</literal> list. The email address for this list
+	is at <literal>mail:samba@samba.org</literal>.  Information regarding the Samba IRC channels may be found on
+	the Samba <ulink url="http://www.samba.org/samba.irc.html">IRC</ulink> web page.
+	</para>
+
+	<para>
+<indexterm><primary>free support</primary></indexterm>
+<indexterm><primary>qualified problem</primary></indexterm>
+<indexterm><primary>requesting payment</primary></indexterm>
+<indexterm><primary>professional support</primary></indexterm>
+	As a general rule, it is considered poor net behavior to contact a Samba Team member directly
+	for free support. Most active members of the Samba Team work exceptionally long hours to assist
+	users who have demonstrated a qualified problem. Some team members may respond to direct email
+	or telephone contact, with requests for assistance, by requesting payment. A few of the Samba
+	Team members actually provide professional paid-for Samba support and it is therefore wise
+	to show appropriate discretion and reservation in all direct contact.
+	</para>
+
+	<para>
+<indexterm><primary>bug report</primary></indexterm>
+<indexterm><primary>problem report</primary></indexterm>
+<indexterm><primary>code maintainer</primary></indexterm>
+	When you stumble across a Samba bug, often the quickest way to get it resolved is by posting
+	a bug <ulink url="https://bugzilla.samba.org/">report</ulink>. All such reports are mailed to
+	the responsible code maintainer for action. The better the report, and the more serious it is,
+	the sooner it will be dealt with. On the other hand, if the responsible person can not duplicate
+	the reported bug it is likely to be rejected. It is up to you to provide sufficient information
+	that will permit the problem to be reproduced.
+	</para>
+
+	<para>
+<indexterm><primary>purchase support</primary></indexterm>
+	We all recognize that sometimes free support does not provide the answer that is sought within
+	the time-frame required. At other times the problem is elusive and you may lack the experience
+	necessary to isolate the problem and thus to resolve it. This is a situation where is may be
+	prudent to purchase paid-for support.
+	</para>
+
+	</sect1>
+
+	<sect1>
+	<title>Commercial Support</title>
+
+	<para>
+	There are six basic support oriented services that are most commonly sought by Samba sites:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>Assistance with network design</para></listitem>
+		<listitem><para>Staff Training</para></listitem>
+		<listitem><para>Assistance with Samba network deployment and installation</para></listitem>
+		<listitem><para>Priority telephone or email Samba configuration assistance</para></listitem>
+		<listitem><para>Trouble-shooting and diagnostic assistance</para></listitem>
+		<listitem><para>Provision of quality assured ready-to-install Samba binary packages</para></listitem>
+	</itemizedlist>
+
+	<para>
+<indexterm><primary>commercial support</primary></indexterm>
+<indexterm><primary>country of origin</primary></indexterm>
+	Information regarding companies that provide professional Samba support can be obtained by performing a Google
+	search, as well as by reference to the Samba <ulink
+	url="http://www.samba.org/samba/support.html">Support</ulink> web page. Companies who notify the Samba Team
+	that they provide commercial support are given a free listing that is sorted by the country of origin.
+	Multiple listings are permitted, however no guarantee is offered. It is left to you to qualify a support
+	provider and to satisfy yourself that both the company and its staff are able to deliver what is required of
+	them.
+	</para>
+
+	<para>
+<indexterm><primary>commercial support</primary></indexterm>
+	The policy within the Samba Team is to treat all commercial support providers equally and to show no
+	preference. As a result, Samba Team members who provide commercial support are lumped in with everyone else.
+	You are encouraged to obtain the services needed from a company in your local area. The open source movement
+	is pro-community; so do what you can to help a local business to prosper.
+	</para>
+
+	<para>
+<indexterm><primary>unsupported software</primary></indexterm>
+	Open source software support can be found in any quality, at any price and in any place you can
+	to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for
+	suffering in the mistaken belief that Samba is unsupported software &smbmdash; it is supported.
+	</para>
+
+	</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-ByExample/SBE-TheSmallOffice.xml b/docs-xml/Samba3-ByExample/SBE-TheSmallOffice.xml
new file mode 100644
index 00000000000..ca39af30631
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-TheSmallOffice.xml
@@ -0,0 +1,1258 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="small">
+  <title>Small Office Networking</title>
+
+	<para>
+	<link linkend="simple"/> focused on the basics of simple yet effective
+	network solutions. Network administrators who take pride in their work
+	(that's most of us, right?) take care to deliver what our users want,
+	but not too much more. If we make things too complex, we confound our users
+	and increase costs of network ownership. A professional network manager
+	avoids the temptation to put too much pizazz into the way that the network
+	operates. Some creativity is helpful, but keep it under control &smbmdash;
+	good advice that the following two scenarios illustrate.
+	</para>
+
+	<para>
+	<indexterm><primary>Netware</primary></indexterm>
+	In one case the network administrator of a mid-sized company spent three
+	months building a new network to replace an old Netware server. What he
+	delivered had all the bells and whistles he could muster. There were a
+	few teething problems during the changeover, nothing serious but a little
+	disruptive all the same. Users were exposed to many changes at once. The
+	network administrator was asked to resign two months after implementing
+	the new system because so many staff complained they had lost time and
+	were not happy with the new network.  Everything was automated, and he
+	delivered more features than any advanced user could think of. He was
+	just too smart for his own good.
+	</para>
+
+	<para>
+	In the case of the other company, a new network manager was appointed
+	to oversee the replacement of a LanTastic network with an MS Windows
+	NT 4.0 network. He had the replacement installed and operational within
+	two weeks. Before installation and changeover, he called a meeting to
+	explain to all users what was going to happen, how it would affect them,
+	and that he would be available 24 hours a day to help them transition.
+	One week after conversion, he held another meeting asking for cooperation
+	in the introduction of a few new features that would help to make life
+	easier. Network users were thrilled with the help he provided. The network
+	he implemented was nowhere near as complex as in the first example, had fewer
+	features, and yet he had happy users. Months later he was still adding
+	new innovations. He always asked the users if a
+	particular feature was what they wanted. He asked his boss for a raise
+	and got it. He often told me, <quote>Always keep a few new tricks up your
+	sleeves for when you need them.</quote> Was he smart? You decide. Let's
+	get on with our next exercise.
+	</para>
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>
+	Abmas Accounting has grown. Mr. Meany likes you and says he knew you
+	were the right person for the job. That's why he asked you to install the
+	new server. The past few months have been hard work. You advised Mr. Meany
+	that it is time for a change. Abmas now has 52 users, having acquired an
+	investment consulting business recently. The new users were added to the
+	network without any problems.
+	</para>
+
+	<para>
+	Some of the Windows clients are nearly past their use-by date.  You found damaged and unusable software on
+	some of the workstations that came with the acquired business and found some machines in need of both
+	hardware and software maintenance.
+	</para>
+
+	<sect2>
+		<title>Assignment Tasks</title>
+
+		<para>
+		<indexterm><primary>Windows XP</primary></indexterm>
+		Mr. Meany is retiring in 12 months. Before he goes, he wants you to help ensure
+		that the business is running efficiently. Many of the new staff want notebook
+		computers.  They visit customer business premises and need to use local network
+		facilities; these users are technically competent. The company uses a
+		business application that requires Windows XP Professional. In short, a complete
+		client upgrade is about to happen. Mr. Meany told you that he is working
+		on another business acquisition and that by the time he retires there will be
+		80 to 100 users.
+		</para>
+
+		<para>
+		Mr. Meany is not concerned about security. He wants to make it easier for
+		staff to do their work. He has hired you to help him appoint a full-time
+		network manager before he retires. Above all, he says he is investing in
+		the ability to grow. He is determined to live his lifelong dream and
+		hand the business over to a bright and capable executive who can make
+		things happen. This means your network design must cope well with
+		growth.
+		</para>
+
+		<para>
+		In a few months, Abmas will require an Internet connection for email and so
+		that staff can easily obtain software updates. Mr. Meany is warming up to
+		the installation of antivirus software but is not yet ready to approve
+		this expense. He told you to spend the money a virus scanner costs
+		on better quality notebook computers for mobile users.
+		</para>
+
+		<para>
+		One of Mr. Meany's golfing partners convinced him to buy new laser
+		printers, one black only, the other a color laser printer. Staff support
+		the need for a color printer so they can present more attractive proposals
+		and reports.
+		</para>
+
+		<para>
+		Mr. Meany also asked if it would be possible for one of the staff to manage
+		user accounts from the Windows desktop. That person will be responsible for
+		basic operations.
+		</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+	<title>Dissection and Discussion</title>
+
+	<para>
+	What are the key requirements in this business example? A quick review indicates
+	a need for
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Scalability, from 52 to over 100 users in 12 months
+		</para></listitem>
+
+		<listitem><para>
+		Mobile computing capability
+		<indexterm><primary>mobile computing</primary></indexterm>
+		</para></listitem>
+
+		<listitem><para>
+		Improved reliability and usability
+		</para></listitem>
+
+		<listitem><para>
+		Easier administration
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	In this instance the installed Linux system is assumed to be a Red Hat Linux Fedora Core2 server
+	(as in <link linkend="AccountingOffice"/>).
+
+	</para>
+
+
+	<sect2>
+		<title>Technical Issues</title>
+
+		<para>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		<indexterm><primary>DHCP</primary></indexterm>
+		<indexterm><primary>DNS</primary></indexterm>
+		<indexterm><primary>WINS</primary></indexterm>
+		<indexterm><primary>Domain</primary></indexterm>
+		It is time to implement a domain security environment. You will use the <constant>
+		smbpasswd</constant> (default) backend. You should implement a DHCP server. There is no need to
+		run DNS at this time, but the system will use WINS. The domain name will be <constant>
+		BILLMORE</constant>. This time, the name of the server will be <constant>SLEETH</constant>.
+		</para>
+
+                <para>
+		All printers will be configured as DHCP clients. The DHCP server will assign
+		the printer a fixed IP address by way of its Ethernet interface (MAC) address.
+		See <link linkend="dhcp01"/>.
+                </para>
+
+		<note><para>
+		The &smb.conf; file you are creating in this exercise can be used with equal effectiveness
+		with Samba-2.2.x series releases. This is deliberate so that in the next chapter it is
+		possible to start with the installation that you have created here, migrate it
+		to a Samba-3 configuration, and then secure the system further. Configurations following
+		this one utilize features that may not be supported in Samba-2.2.x releases.
+		However, you should note that the examples in each chapter start with the assumption
+		that a fresh new installation is being effected.
+		</para></note>
+
+		<para>
+		Later on, when the Internet connection is implemented, you will add DNS as well as
+		other enhancements. It is important that you plan accordingly.
+		</para>
+
+		<para>
+		<indexterm><primary>Ethernet switch</primary></indexterm>
+		You have split the network into two separate areas. Each has its own Ethernet switch.
+		There are 20 users on the accounting network and 32 users on the financial services
+		network. The server has two network interfaces, one serving each network. The
+		network printers will be located in a central area. You plan to install the new
+		printers and keep the old printer in use also.
+		</para>
+
+		<para>
+		You will provide separate file storage areas for each business entity. The old system
+		will go away, accounting files will be handled under a single directory, and files will
+		be stored under customer name, not under a personal work area. Staff will be made
+		responsible for file location, so the old share point must be maintained.
+		</para>
+
+		<para>
+		Given that DNS will not be used, you will configure WINS name resolution for UNIX
+		hostname name resolution.
+		</para>
+
+		<para>
+		<indexterm><primary>Domain</primary><secondary>groups</secondary></indexterm>
+		<indexterm><primary>UNIX</primary><secondary>groups</secondary></indexterm>
+		It is necessary to map Windows Domain Groups to UNIX groups. It is
+		advisable to also map Windows Local Groups to UNIX groups. Additionally, the two
+		key staff groups in the firm are accounting staff and financial services staff.
+		For these, it is necessary to create UNIX groups as well as Windows Domain Groups.
+		</para>
+
+		<para>
+		In the sample &smb.conf; file, you have configured Samba to call the UNIX
+		<command>groupadd</command> to add group entries. This utility does not permit
+		the addition of group names that contain uppercase characters or spaces. This
+		is considered a bug. The <command>groupadd</command> is part of the
+		<command>shadow-utils</command> open source software package.  A later release
+		of this package may have been patched to resolve this bug.  If your operating
+		platform has this bug, it means that attempts to add a Windows Domain Group that
+		has either a space or uppercase characters in it will fail. See
+		<emphasis>TOSHARG2</emphasis>, Chapter 11, Section 11.3.1, Example 11.1, for
+		more information.
+		</para>
+
+		<para>
+		<indexterm><primary>CUPS</primary></indexterm>
+		Vendor-supplied printer drivers will be installed on each client. The CUPS print
+		spooler on the UNIX host will be operated in <constant>raw</constant> mode.
+		</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Political Issues</title>
+
+		<para>
+		Mr. Meany is an old-school manager. He sets the rules and wants to see compliance.
+		He is willing to spend money on things he believes are of value. You need more
+		time to convince him of real priorities.
+		</para>
+
+		<para>
+		Go ahead, buy better notebooks. Wouldn't it be neat if they happened to be
+		supplied with antivirus software? Above all, demonstrate good purchase value and remember
+		to make your users happy.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Implementation</title>
+
+	<para>
+	<indexterm><primary>migration</primary></indexterm>
+	In this example, the assumption is made that this server is being configured from a clean start.
+	The alternate approach could be to demonstrate the migration of the system that is documented
+	in <link linkend="AcctgNet"/> to meet the new requirements. The decision to treat this case, as with
+	future examples, as a new installation is based on the premise that you can determine
+	the migration steps from the information provided in <link linkend="ntmigration"/>.
+	Additionally, a fresh installation makes the example easier to follow.
+	</para>
+
+	<para>
+	<indexterm><primary>group membership</primary></indexterm>
+	Each user will be given a home directory on the UNIX system, which will be available as a private
+	share. Two additional shares will be created, one for the accounting department and the other for
+	the financial services department. Network users will be given access to these shares by way
+	of group membership.
+	</para>
+
+	<para>
+	<indexterm><primary>UNIX</primary><secondary>groups</secondary></indexterm>
+	UNIX group membership is the primary mechanism by which Windows Domain users will be granted
+	rights and privileges within the Windows environment.
+	</para>
+
+	<para>
+	<indexterm><primary>sticky bit</primary></indexterm>
+	The user <command>alanm</command> will be made the owner of all files. This will be preserved
+	by setting the sticky bit (set UID/GID) on the top-level directories.
+	</para>
+
+	<figure id="acct2net">
+		<title>Abmas Accounting &smbmdash; 52-User Network Topology</title>
+		<imagefile scale="100">acct2net</imagefile>
+	</figure>
+
+	<procedure>
+	<title>Server Installation Steps</title>
+
+		<step><para>
+		Using UNIX/Linux system tools, name the server <constant>sleeth</constant>.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/hosts</primary></indexterm>
+		Place an entry for the machine <constant>sleeth</constant> in the <filename>/etc/hosts</filename>.
+		The printers are network attached, so there should be entries for the
+		network printers also. An example <filename>/etc/hosts</filename> file is shown here:
+<screen>
+192.168.1.1     sleeth sleeth1
+192.168.2.1     sleeth2
+192.168.1.10    hplj6
+192.168.1.11    hplj4
+192.168.2.10    qms
+</screen>
+		</para></step>
+
+		<step><para>
+		Install the Samba-3 binary RPM from the Samba-Team FTP site.
+		</para></step>
+
+		<step><para>
+		Install the ISC DHCP server using the UNIX/Linux system tools available to you.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/rc.d/rc.local</primary></indexterm>
+		<indexterm><primary>IP forwarding</primary></indexterm>
+		<indexterm><primary>router</primary></indexterm>
+		<indexterm><primary>/proc/sys/net/ipv4/ip_forward</primary></indexterm>
+		Because Samba will be operating over two network interfaces and clients on each side
+		may want to be able to reach clients on the other side, it is imperative that IP forwarding
+		is enabled. Use the system tool of your choice to enable IP forwarding. In the
+		absence of such a tool on the Linux system, add to the <filename>/etc/rc.d/rc.local</filename>
+		file an entry as follows:
+<screen>
+echo 1 > /proc/sys/net/ipv4/ip_forward
+</screen>
+		This causes the Linux kernel to forward IP packets so that it acts as a router.
+		</para></step>
+
+		<step><para>
+		Install the &smb.conf; file as shown in <link linkend="acct2conf"/> and
+		<link linkend="acct3conf"/>. Combine these two examples to form a single
+		<filename>/etc/samba/smb.conf</filename> file.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		Add the user <command>root</command> to the Samba password backend:
+<screen>
+&rootprompt; smbpasswd -a root
+New SMB password: XXXXXXX
+Retype new SMB password: XXXXXXX
+&rootprompt;
+</screen>
+		<indexterm><primary>administrator</primary></indexterm>
+		This is the Windows Domain Administrator password. Never delete this account from
+		the password backend after Windows Domain Groups have been initialized. If you delete
+		this account, your system is crippled. You cannot restore this account,
+		and your Samba server can no longer be administered.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>username map</primary></indexterm>
+		Create the username map file to permit the <constant>root</constant> account to be called
+		<constant>Administrator</constant> from the Windows network environment. To do this, create
+		the file <filename>/etc/samba/smbusers</filename> with the following contents:
+<screen>
+####
+# User mapping file
+####
+# File Format
+# -----------
+# Unix_ID = Windows_ID
+#
+# Examples:
+# root = Administrator
+# janes = "Jane Smith"
+# jimbo = Jim Bones
+#
+# Note: If the name contains a space it must be double quoted.
+#       In the example above the name 'jimbo' will be mapped to Windows
+#       user names 'Jim' and 'Bones' because the space was not quoted.
+#######################################################################
+root = Administrator
+####
+# End of File
+####
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>initGrps.sh</primary></indexterm>
+		Create and map Windows Domain Groups to UNIX groups. A sample script is provided in
+		<link linkend="initGrps"/>. Create a file containing this script. We called ours
+		<filename>/etc/samba/initGrps.sh</filename>. Set this file so it can be executed,
+		and then execute the script. Sample output should be as follows:
+
+<example id="initGrps">
+<title>Script to Map Windows NT Groups to UNIX Groups</title>
+<indexterm><primary>initGrps.sh</primary></indexterm>
+<screen>
+#!/bin/bash
+#
+# initGrps.sh
+#
+
+# Create UNIX groups
+groupadd acctsdep
+groupadd finsrvcs
+
+# Map Windows Domain Groups to UNIX groups
+net groupmap add ntgroup="Domain Admins"  unixgroup=root type=d
+net groupmap add ntgroup="Domain Users"   unixgroup=users type=d
+net groupmap add ntgroup="Domain Guests"  unixgroup=nobody type=d
+
+# Add Functional Domain Groups
+net groupmap add ntgroup="Accounts Dept"  unixgroup=acctsdep type=d
+net groupmap add ntgroup="Financial Services" unixgroup=finsrvcs type=d
+</screen>
+</example>
+
+<screen>
+&rootprompt; chmod 755 initGrps.sh
+&rootprompt; cd /etc/samba
+&rootprompt; ./initGrps.sh
+Updated mapping entry for Domain Admins
+Updated mapping entry for Domain Users
+Updated mapping entry for Domain Guests
+No rid or sid specified, choosing algorithmic mapping
+Successfully added group Accounts Dept to the mapping db
+No rid or sid specified, choosing algorithmic mapping
+Successfully added group Domain Guests to the mapping db
+
+&rootprompt; cd /etc/samba
+&rootprompt; net groupmap list | sort
+Account Operators (S-1-5-32-548) -> -1
+Accounts Dept (S-1-5-21-194350-25496802-3394589-2003) -> acctsdep
+Administrators (S-1-5-32-544) -> -1
+Backup Operators (S-1-5-32-551) -> -1
+Domain Admins (S-1-5-21-194350-25496802-3394589-512) -> root
+Domain Guests (S-1-5-21-194350-25496802-3394589-514) -> nobody
+Domain Users (S-1-5-21-194350-25496802-3394589-513) -> users
+Financial Services (S-1-5-21-194350-25496802-3394589-2005) -> finsrvcs
+Guests (S-1-5-32-546) -> -1
+Power Users (S-1-5-32-547) -> -1
+Print Operators (S-1-5-32-550) -> -1
+Replicators (S-1-5-32-552) -> -1
+System Operators (S-1-5-32-549) -> -1
+Users (S-1-5-32-545) -> -1
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/passwd</primary></indexterm>
+		<indexterm><primary>password</primary><secondary>backend</secondary></indexterm>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		For each user who needs to be given a Windows Domain account, make an entry in the
+		<filename>/etc/passwd</filename> file as well as in the Samba password backend.
+		Use the system tool of your choice to create the UNIX system accounts, and use the Samba
+		<command>smbpasswd</command> program to create the Domain user accounts.
+		</para>
+
+		<para>
+		<indexterm><primary>useradd</primary></indexterm>
+		<indexterm><primary>adduser</primary></indexterm>
+		<indexterm><primary>user</primary><secondary>management</secondary></indexterm>
+		There are a number of tools for user management under UNIX, such as
+		<command>useradd</command> and <command>adduser</command>, as well as a plethora of custom
+		tools. With the tool of your choice, create a home directory for each user.
+		</para></step>
+
+		<step><para>
+		Using the preferred tool for your UNIX system, add each user to the UNIX groups created
+		previously, as necessary. File system access control will be based on UNIX group membership.
+		</para></step>
+
+		<step><para>
+		Create the directory mount point for the disk subsystem that is mounted to provide
+		data storage for company files. In this case the mount point is indicated in the &smb.conf;
+		file is <filename>/data</filename>. Format the file system as required, mount the formatted
+		file system partition using <command>mount</command>,
+		and make the appropriate changes in <filename>/etc/fstab</filename>.
+		</para></step>
+
+		<step><para>
+		Create the top-level file storage directories are follows:
+<screen>
+&rootprompt; mkdir -p /data/{accounts,finsvcs}
+&rootprompt; chown -R root:root /data
+&rootprompt; chown -R alanm:accounts /data/accounts
+&rootprompt; chown -R alanm:finsvcs /data/finsvcs
+&rootprompt; chmod -R ug+rwx,o+rx-w /data
+</screen>
+		Each department is responsible for creating its own directory structure within its
+		share. The directory root of the <command>accounts</command> share is <filename>/data/accounts</filename>.
+		The directory root of the <command>finsvcs</command> share is <filename>/data/finsvcs</filename>.
+		</para></step>
+
+		<step><para>
+		Configure the printers with the IP addresses as shown in <link linkend="acct2net"/>.
+		Follow the instructions in the manufacturers' manuals to permit printing to port 9100.
+		This allows the CUPS spooler to print using raw mode protocols.
+		<indexterm><primary>CUPS</primary></indexterm>
+		<indexterm><primary>raw printing</primary></indexterm>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>CUPS</primary><secondary>queue</secondary></indexterm>
+		<indexterm><primary>lpadmin</primary></indexterm>
+		Configure the CUPS Print Queues as follows:
+<screen>
+&rootprompt; lpadmin -p hplj4 -v socket://192.168.1.11:9100 -E
+&rootprompt; lpadmin -p hplj6 -v socket://192.168.1.10:9100 -E
+&rootprompt; lpadmin -p qms -v socket://192.168.2.10:9100 -E
+</screen>
+		<indexterm><primary>print filter</primary></indexterm>
+		This creates the necessary print queues with no assigned print filter.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>mime type</primary></indexterm>
+		<indexterm><primary>/etc/mime.convs</primary></indexterm>
+		<indexterm><primary>application/octet-stream</primary></indexterm>
+		Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
+<screen>
+application/octet-stream     application/vnd.cups-raw      0     -
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>/etc/mime.types</primary></indexterm>
+		Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
+<screen>
+application/octet-stream
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>DHCP Server</primary></indexterm>
+		Using your favorite system editor, create an <filename>/etc/dhcpd.conf</filename> with the
+		contents as shown in <link linkend="dhcp01"/>.
+<example id="dhcp01">
+<title>Abmas Accounting DHCP Server Configuration File &smbmdash; <filename>/etc/dhcpd.conf</filename></title>
+<indexterm><primary>/etc/dhcpd.conf</primary></indexterm>
+<screen>
+default-lease-time 86400;
+max-lease-time 172800;
+default-lease-time 86400;
+
+option ntp-servers 192.168.1.1;
+option domain-name "abmas.biz";
+option domain-name-servers 192.168.1.1, 192.168.2.1;
+option netbios-name-servers 192.168.1.1, 192.168.2.1;
+option netbios-node-type 8;
+### NOTE ###
+# netbios-node-type=8 means set clients to Hybrid Mode
+#   so they will use Unicast communication with the WINS
+#   server and thus reduce the level of UDP broadcast
+#   traffic by up to 90%.
+############
+
+subnet 192.168.1.0 netmask 255.255.255.0 {
+	range dynamic-bootp 192.168.1.128 192.168.1.254;
+	option subnet-mask 255.255.255.0;
+	option routers 192.168.1.1;
+	allow unknown-clients;
+	host hplj4 {
+		hardware ethernet 08:00:46:7a:35:e4;
+		fixed-address 192.168.1.10;
+		}
+	host hplj6 {
+		hardware ethernet 00:03:47:cb:81:e0;
+		fixed-address 192.168.1.11;
+		}
+	}
+subnet 192.168.2.0 netmask 255.255.255.0 {
+	range dynamic-bootp 192.168.2.128 192.168.2.254;
+	option subnet-mask 255.255.255.0;
+	option routers 192.168.2.1;
+	allow unknown-clients;
+	host qms {
+		hardware ethernet 01:04:31:db:e1:c0;
+		fixed-address 192.168.1.10;
+		}
+	}
+subnet 127.0.0.0 netmask 255.0.0.0 {
+	}
+</screen>
+</example>
+		</para></step>
+
+
+		<step><para>
+		Use the standard system tool to start Samba and CUPS and configure them to start
+		automatically at every system reboot. For example,
+		</para>
+
+		<para>
+		<indexterm><primary>chkconfig</primary></indexterm>
+		<indexterm><primary>starting dhcpd</primary></indexterm>
+		<indexterm><primary>starting samba</primary></indexterm>
+		<indexterm><primary>starting CUPS</primary></indexterm>
+		<indexterm><primary>chkconfig</primary></indexterm>
+<screen>
+&rootprompt; chkconfig dhcp on
+&rootprompt; chkconfig smb on
+&rootprompt; chkconfig cups on
+&rootprompt; /etc/rc.d/init.d/dhcp restart
+&rootprompt; /etc/rc.d/init.d/smb restart
+&rootprompt; /etc/rc.d/init.d/cups restart
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>name service switch</primary></indexterm>
+		<indexterm><primary>NSS</primary><see>same service switch</see></indexterm>
+		<indexterm><primary>DNS</primary></indexterm>
+		<indexterm><primary>DNS server</primary></indexterm>
+		<indexterm><primary>WINS</primary></indexterm>
+		<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+		Configure the name service switch (NSS) to handle WINS-based name resolution.
+		Since this system does not use a DNS server, it is safe to remove this option from
+		the NSS configuration. Edit the <filename>/etc/nsswitch.conf</filename> file so that
+		the <constant>hosts:</constant> entry looks like this:
+<screen>
+hosts:	files wins
+</screen>
+		</para></step>
+
+	</procedure>
+
+<example id="acct2conf">
+<title>Accounting Office Network &smb.conf; File &smbmdash; [globals] Section</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">BILLMORE</smbconfoption>
+<smbconfoption name="passwd chat">*New*Password* %n\n*Re-enter*new*password* %n\n *Password*changed*</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="add user script">/usr/sbin/useradd -m -G users '%u'</smbconfoption>
+<smbconfoption name="delete user script">/usr/sbin/userdel -r '%u'</smbconfoption>
+<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
+<smbconfoption name="delete group script">/usr/sbin/groupdel '%g'</smbconfoption>
+<smbconfoption name="add user to group script">/usr/sbin/usermod -A '%g' '%u'</smbconfoption>
+<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</smbconfoption>
+<smbconfoption name="logon script">scripts\login.bat</smbconfoption>
+<smbconfoption name="logon path"> </smbconfoption>
+<smbconfoption name="logon drive">X:</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="preferred master">Yes</smbconfoption>
+<smbconfoption name="wins support">Yes</smbconfoption>
+<smbconfoption name="printing">CUPS</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="acct3conf">
+<title>Accounting Office Network &smb.conf; File &smbmdash; Services and Shares Section</title>
+<smbconfblock>
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">SMB Print Spool</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">Network Logon Service</smbconfoption>
+<smbconfoption name="path">/data/%U</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[accounts]"/>
+<smbconfoption name="comment">Accounting Files</smbconfoption>
+<smbconfoption name="path">/data/accounts</smbconfoption>
+<smbconfoption name="valid users">%G</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[finsvcs]"/>
+<smbconfoption name="comment">Financial Service Files</smbconfoption>
+<smbconfoption name="path">/data/finsvcs</smbconfoption>
+<smbconfoption name="valid users">%G</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+</smbconfblock>
+</example>
+
+		<sect2>
+		<title>Validation</title>
+
+		<para>
+		Does everything function as it ought? That is the key question at this point.
+		Here are some simple steps to validate your Samba server configuration.
+		</para>
+
+		<procedure>
+		<title>Validation Steps</title>
+
+			<step><para>
+			<indexterm><primary>testparm</primary></indexterm>
+			If your &smb.conf; file has bogus options or parameters, this may cause Samba
+			to refuse to start. The first step should always be to validate the contents
+			of this file by running:
+<screen>
+&rootprompt; testparm -s
+Load smb config files from smb.conf
+Processing section "[homes]"
+Processing section "[printers]"
+Processing section "[netlogon]"
+Processing section "[accounts]"
+Processing section "[service]"
+Loaded services file OK.
+# Global parameters
+[global]
+        workgroup = BILLMORE
+        passwd chat = *New*Password* \
+		%n\n *Re-enter*new*password* %n\n *Password*changed*
+        username map = /etc/samba/smbusers
+        syslog = 0
+        name resolve order = wins bcast hosts
+        printcap name = CUPS
+        show add printer wizard = No
+        add user script = /usr/sbin/useradd -m -G users '%u'
+        delete user script = /usr/sbin/userdel -r '%u'
+        add group script = /usr/sbin/groupadd '%g'
+        delete group script = /usr/sbin/groupdel '%g'
+        add user to group script = /usr/sbin/usermod -A '%g' '%u'
+        add machine script = /usr/sbin/useradd
+				-s /bin/false -d /var/lib/nobody '%u'
+        logon script = scripts\logon.bat
+        logon path =
+        logon drive = X:
+        domain logons = Yes
+        preferred master = Yes
+        wins support = Yes
+...
+### Remainder cut to save space ###
+</screen>
+			The inclusion of an invalid parameter (say one called dogbert) would generate an
+			error as follows:
+<screen>
+Unknown parameter encountered: "dogbert"
+Ignoring unknown parameter "dogbert"
+</screen>
+			Clear away all errors before proceeding, and start or restart samba as necessary.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>check samba daemons</primary></indexterm>
+			<indexterm><primary>nmbd</primary></indexterm>
+			<indexterm><primary>smbd</primary></indexterm>
+			<indexterm><primary>winbindd</primary></indexterm>
+			Check that the Samba server is running:
+<screen>
+&rootprompt; ps ax | grep mbd
+14244 ?        S      0:00 /usr/sbin/nmbd -D
+14245 ?        S      0:00 /usr/sbin/nmbd -D
+14290 ?        S      0:00 /usr/sbin/smbd -D
+
+$rootprompt; ps ax | grep winbind
+14293 ?        S     0:00 /usr/sbin/winbindd -B
+14295 ?        S     0:00 /usr/sbin/winbindd -B
+</screen>
+			The <command>winbindd</command> daemon is running in split mode (normal), so there are also
+			two instances of it. For more information regarding <command>winbindd</command>, see
+			<emphasis>TOSHARG2</emphasis>, Chapter 23, Section 23.3. The single instance of
+			<command>smbd</command> is normal.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>anonymous connection</primary></indexterm>
+			Check that an anonymous connection can be made to the Samba server:
+<screen>
+&rootprompt; smbclient -L localhost -U%
+
+        Sharename      Type      Comment
+        ---------      ----      -------
+        netlogon       Disk      Network Logon Service
+        accounts       Disk      Accounting Files
+        finsvcs        Disk      Financial Service Files
+        IPC$           IPC       IPC Service (Samba3)
+        ADMIN$         IPC       IPC Service (Samba3)
+        hplj4          Printer   Hewlett-Packard LaserJet 4
+        hplj6          Printer   Hewlett-Packard LaserJet 6
+        qms            Printer   QMS Magicolor Laser Printer XXXX
+
+        Server               Comment
+        ---------            -------
+        SLEETH               Samba 3.0.20
+
+        Workgroup            Master
+        ---------            -------
+        BILLMORE             SLEETH
+</screen>
+			This demonstrates that an anonymous listing of shares can be obtained. This is the equivalent
+			of browsing the server from a Windows client to obtain a list of shares on the server.
+			The <constant>-U%</constant> argument means to send a <constant>NULL</constant> username and
+			a <constant>NULL</constant> password.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>dhcp client validation</primary></indexterm>
+			<indexterm><primary>printer validation</primary></indexterm>
+			<indexterm><primary>/etc/dhcpd.conf</primary></indexterm>
+			Verify that the printers have the IP addresses assigned in the DHCP server configuration file.
+			The easiest way to do this is to ping the printer name. Immediately after the ping response
+			has been received, execute <command>arp -a</command> to find the MAC address of the printer
+			that has responded. Now you can compare the IP address and the MAC address of the printer
+			with the configuration information in the <filename>/etc/dhcpd.conf</filename> file. They
+			should, of course, match. For example,
+<screen>
+&rootprompt; ping hplj4
+PING hplj4 (192.168.1.11) 56(84) bytes of data.
+64 bytes from hplj4 (192.168.1.11): icmp_seq=1 ttl=64 time=0.113 ms
+
+&rootprompt; arp -a
+hplj4 (192.168.1.11) at 08:00:46:7A:35:E4 [ether] on eth0
+</screen>
+			The MAC address <constant>08:00:46:7A:35:E4</constant> matches that specified for the
+			IP address from which the printer has responded and the entry for it in the
+			<filename>/etc/dhcpd.conf</filename> file.
+			</para></step>
+
+			<step><para>
+			<indexterm><primary>authenticated connection</primary></indexterm>
+			Make an authenticated connection to the server using the <command>smbclient</command> tool:
+<screen>
+&rootprompt; smbclient //sleeth/accounts -U alanm
+Password: XXXXXXX
+smb: \&gt; dir
+  .                          D        0  Sun Nov  9 01:28:34 2003
+  ..                         D        0  Sat Aug 16 17:24:26 2003
+  .mc                       DH        0  Sat Nov  8 21:57:38 2003
+  .qt                       DH        0  Fri Sep  5 00:48:25 2003
+  SMB                        D        0  Sun Oct 19 23:04:30 2003
+  Documents                  D        0  Sat Nov  1 00:31:51 2003
+  xpsp1a_en_x86.exe           131170400  Sun Nov  2 01:25:44 2003
+
+           65387 blocks of size 65536. 28590 blocks available
+smb: \> q
+</screen>
+			</para></step>
+
+		</procedure>
+
+		</sect2>
+
+
+	<procedure>
+	<title>Windows XP Professional Client Configuration</title>
+
+		<step><para>
+		Configure clients to the network settings shown in <link linkend="acct2net"/>.
+		All clients use DHCP for TCP/IP protocol stack configuration.
+		<indexterm><primary>WINS</primary></indexterm>
+		<indexterm><primary>DHCP</primary></indexterm>
+		DHCP configures all Windows clients to use the WINS Server address <constant>192.168.1.1</constant>.
+		</para></step>
+
+		<step><para>
+		Join the Windows Domain called <constant>BILLMORE</constant>. Use the Domain Administrator
+		username <constant>root</constant> and the SMB password you assigned to this account.
+		A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to
+		a Windows Domain is given in <link linkend="appendix"/>, <link linkend="domjoin"/>.
+		Reboot the machine as prompted and then log on using a Domain User account.
+		</para></step>
+
+		<step><para>
+		Verify on each client that the machine called <constant>SLEETH</constant>
+		is visible in <guimenu>My Network Places</guimenu>, that it is
+		possible to connect to it and see the shares <guimenuitem>accounts</guimenuitem>
+		 and <guimenuitem>finsvcs</guimenuitem>,
+		and that it is possible to open that share to reveal its contents.
+		</para></step>
+
+		<step><para>
+		Instruct all users to log onto the workstation using their assigned username and password.
+		</para></step>
+
+		<step><para>
+		Install a printer on each using the following steps:
+		</para>
+
+			<procedure>
+				<step><para>
+				Click <menuchoice>
+					<guimenu>Start</guimenu>
+					<guimenuitem>Settings</guimenuitem>
+					<guimenuitem>Printers</guimenuitem>
+					<guiicon>Add Printer</guiicon>
+					<guibutton>Next</guibutton>
+					</menuchoice>. Do not click <guimenuitem>Network printer</guimenuitem>.
+					Ensure that <guimenuitem>Local printer</guimenuitem> is selected.
+				</para></step>
+
+				<step><para>
+				Click <guibutton>Next</guibutton>. In the
+				<guimenuitem>Manufacturer:</guimenuitem> panel, select <constant>HP</constant>.
+				In the <guimenuitem>Printers:</guimenuitem> panel, select the printer called
+				<constant>HP LaserJet 4</constant>. Click <guibutton>Next</guibutton>.
+				</para></step>
+
+				<step><para>
+				In the <guimenuitem>Available ports:</guimenuitem> panel, select
+				<constant>FILE:</constant>. Accept the default printer name by clicking
+				<guibutton>Next</guibutton>. When asked, <quote>Would you like to print a
+				test page?</quote>, click <guimenuitem>No</guimenuitem>. Click
+				<guibutton>Finish</guibutton>.
+				</para></step>
+
+				<step><para>
+				You may be prompted for the name of a file to print to. If so, close the
+				dialog panel. Right-click <menuchoice>
+					<guiicon>HP LaserJet 4</guiicon>
+					<guimenuitem>Properties</guimenuitem>
+					<guisubmenu>Details (Tab)</guisubmenu>
+					<guimenuitem>Add Port</guimenuitem>
+					</menuchoice>.
+				</para></step>
+
+				<step><para>
+				In the <guimenuitem>Network</guimenuitem> panel, enter the name of
+				the print queue on the Samba server as follows: <constant>\\SERVER\hplj4</constant>.
+				Click <menuchoice>
+					<guibutton>OK</guibutton>
+					<guibutton>OK</guibutton>
+					</menuchoice> to complete the installation.
+				</para></step>
+
+				<step><para>
+				Repeat the printer installation steps above for the HP LaserJet 6 printer
+				as well as for the QMS Magicolor XXXX laser printer.
+				</para></step>
+			</procedure>
+		</step>
+	</procedure>
+
+	<sect2>
+	<title>Notebook Computers: A Special Case</title>
+
+	<para>
+	As a network administrator, you already know how to create local machine accounts for Windows 200x/XP
+	Professional systems. This is the preferred solution to provide continuity of work for notebook users
+	so that absence from the office network environment does not become a barrier to productivity.
+	</para>
+
+	<para>
+	By creating a local machine account that has the same username and password as you create for that
+	user in the Windows Domain environment, the user can log onto the machine locally and still
+	transparently access network resources as if logged onto the domain itself. There are some trade-offs
+	that mean that as the network is more tightly secured, it becomes necessary to modify Windows client
+	configuration somewhat.
+	</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Key Points Learned</title>
+
+		<para>
+		In this network design and implementation exercise, you created a Windows NT4-style Domain
+		Controller using Samba-3.0.20. Following these guidelines, you experienced
+		and implemented several important aspects of Windows networking. In the next chapter,
+		you build on the experience. These are the highlights from this chapter:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			<indexterm><primary>DHCP</primary></indexterm>
+			You implemented a DHCP server, and Microsoft Windows clients were able to obtain all necessary
+			network configuration settings from this server.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>Domain Controller</primary></indexterm>
+			You created a Windows Domain Controller. You were able to use the network logon service
+			and successfully joined Windows 200x/XP Professional clients to the Domain.
+			</para></listitem>
+
+			<listitem><para>
+			<indexterm><primary>CUPS</primary></indexterm>
+			You created raw print queues in the CUPS printing system. You maintained a simple
+			printing system so that all users can share centrally managed printers. You installed
+			native printer drivers on the Windows clients.
+			</para></listitem>
+
+			<listitem><para>
+			You experienced the benefits of centrally managed user accounts on the server.
+			</para></listitem>
+
+			<listitem><para>
+			You offered Mobile notebook users a solution that allows them to continue to work
+			while away from the office and not connected to the corporate network.
+			</para></listitem>
+		</itemizedlist>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Questions and Answers</title>
+
+	<para>
+	Your new Domain Controller is ready to serve you. What does it mean? Here are some questions and answers that
+	may help.
+	</para>
+
+	<qandaset>
+	<qandaentry>
+	<question>
+
+		<para>
+		What is the key benefit of using DHCP to configure Windows client TCP/IP stacks?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		First and foremost, portability. It means that notebook users can move between
+		the Abmas office and client offices (so long as they, too, use DHCP) without having to manually
+		reconfigure their machines. It also means that when they work from their home environments
+		either using DHCP assigned addressing or when using dial-up networking, settings such as
+		default routes and DNS server addresses that apply only to the Abmas office environment do
+		not interfere with remote operations. This is an extremely important feature of DHCP.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Are there any DHCP server configuration parameters in the <filename>/etc/dhcpd.conf</filename>
+		that should be noted in particular?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Yes. The configuration you created automatically provides each client with the IP address
+		of your WINS server. It also configures the client to preferentially register NetBIOS names
+		with the WINS server, and then instructs the client to first query the WINS server when a
+		NetBIOS machine name needs to be resolved to an IP Address. This configuration
+		results in far lower UDP broadcast traffic than would be the case if WINS was not used.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Is it possible to create a Windows Domain account that is specifically called <constant>Administrator</constant>?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		You can surely create a Windows Domain account called <constant>Administrator</constant>. It is also
+		possible to map that account so that it has the effective UNIX UID of 0. This way it isn't
+		necessary to use the <parameter>username map</parameter> facility to map this account to the UNIX
+		account called <constant>root</constant>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why is it necessary to give the Windows Domain <constant>Administrator</constant> a UNIX UID of 0?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The Windows Domain <constant>Administrator</constant> account is the most privileged account that
+		exists on the Windows platform. This user can change any setting, add, delete, or modify user
+		accounts, and completely reconfigure the system. The equivalent to this account in the UNIX
+		environment is the <constant>root</constant> account. If you want to permit the Windows Domain
+		Administrator to manage accounts as well as permissions, privileges, and security
+		settings within the Domain and on the Samba server, equivalent rights must be assigned. This is
+		achieved with the <constant>root</constant> UID equal to 0.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		One of my junior staff needs the ability to add machines to the Domain, but I do not want to give him
+		<constant>root</constant> access. How can we do this?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Users who are members of the <constant>Domain Admins</constant> group can add machines to the
+		Domain. This group is mapped to the UNIX group account called <constant>root</constant>
+		(or the equivalent <constant>wheel</constant> on some UNIX systems) that has a GID of 0.
+		This must be the primary GID of the account of the user who is a member of the Windows <constant>
+		Domain Admins</constant> account.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		Why must I map Windows Domain Groups to UNIX groups?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Samba-3 does not permit a Domain Group to become visible to Domain network clients unless the account
+		has a UNIX group account equivalent. The Domain groups that should be given UNIX equivalents are
+		<guimenu>Domain Guests</guimenu>, <guimenu>Domain Users</guimenu>, and <guimenu>Domain Admins</guimenu>.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		I deleted my <constant>root</constant> account and now I cannot add it back! What can I do?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		This is a nasty problem. Fortunately, there is a solution.
+		</para>
+
+		<procedure>
+			<step><para>
+			Back up your existing configuration files in case you need to restore them.
+			</para></step>
+
+			<step><para>
+			Rename the <filename>group_mapping.tdb</filename> file.
+			</para></step>
+
+			<step><para>
+			Use the <command>smbpasswd</command> to add the root account.
+			</para></step>
+
+			<step><para>
+			Restore the <filename>group_mapping.tdb</filename> file.
+			</para></step>
+		</procedure>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		When I run <command>net groupmap list</command>, it reports a group called <guimenu>Administrators</guimenu>
+		as well as <guimenu>Domain Admins</guimenu>. What is the difference between them?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		The group called <guimenu>Administrators</guimenu> is representative of the same account that would be
+		present as the Local Group account on a Domain Member server or workstation. Samba uses only Domain
+		Groups at this time. A Workstation or Server Local Group has no meaning in a Samba context. This
+		may change at some later date. These accounts are provided only so that security objects are correctly shown.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		What is the effect of changing the name of a Samba server or of changing the Domain name?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		If you elect to change the name of the Samba server, on restarting <command>smbd</command>,
+		Windows security identifiers are changed. In the case of a standalone server or a Domain Member server,
+		the machine SID is changed. This may break Domain membership. In the case of a change of the Domain name
+		(Workgroup name), the Domain SID is changed. This affects all Domain memberships.
+		</para>
+
+		<para>
+		If it becomes necessary to change either the server name or the Domain name, be sure to back up the respective
+		SID before the change is made. You can back up the SID using the <command>net getlocalsid</command> (Samba-3)
+		or the <command>smbpasswd</command> (Samba-2.2.x). To change the SID, you use the same tool. Be sure
+		to check the man page for this command for detailed instructions regarding the steps involved.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	<qandaentry>
+	<question>
+
+		<para>
+		How can I manage user accounts from my Windows XP Professional workstation?
+		</para>
+
+	</question>
+	<answer>
+
+		<para>
+		Samba-3 implements a Windows NT4-style security domain architecture. This type of Domain cannot
+		be managed using tools present on a Windows XP Professional installation. You may download from the
+		Microsoft Web site the SRVTOOLS.EXE package. Extract it into the directory from which you wish to use
+		it. This package extracts the tools: <command>User Manager for Domains</command>, <command>Server Manager</command>, and <command>Event
+		Viewer</command>. You may use the <guimenu>User Manager for Domains</guimenu> to manage your Samba-3
+		Domain user and group accounts. Of course, you do need to be logged on as the <constant>Administrator</constant>
+		for the Samba-3 Domain. It may help to log on as the <constant>root</constant> account.
+		</para>
+
+	</answer>
+	</qandaentry>
+
+	</qandaset>
+
+</sect1>
+
+</chapter>
+
diff --git a/docs-xml/Samba3-ByExample/SBE-UpgradingSamba.xml b/docs-xml/Samba3-ByExample/SBE-UpgradingSamba.xml
new file mode 100644
index 00000000000..f7634aaad79
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-UpgradingSamba.xml
@@ -0,0 +1,1311 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="upgrades">
+<title>Updating Samba-3</title>
+
+<para>
+<indexterm><primary>migrate</primary></indexterm>
+<indexterm><primary>install</primary></indexterm>
+It was a little difficult to select an appropriate title for this chapter.
+From email messages on the Samba mailing lists it is clear that many people
+consider the updating and upgrading of Samba to be a migration matter. Others
+talk about migrating Samba servers when in fact the issue at hand is one of
+installing a new Samba server to replace an older existing Samba server.
+</para>
+
+<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+There has also been much talk about migration of Samba-3 from an smbpasswd
+passdb backend to the use of the tdbsam or ldapsam facilities that are new
+to Samba-3.
+</para>
+
+<para>
+Clearly, there is not a great deal of clarity in the terminology that various
+people apply to these modes by which Samba servers are updated. This is further 
+highlighted by an email posting that included the following neat remark:
+</para>
+
+<blockquote><para>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>vampire</tertiary></indexterm>
+I like the <quote>net rpc vampire</quote> on NT4, but that to my surprise does
+not seem to work against a Samba PDC and, if addressed in the Samba to Samba
+context in either book, I could not find it.
+</para></blockquote>
+
+<para>
+<indexterm><primary>contributions</primary></indexterm>
+So in response to the significant request for these situations to be better 
+documented, this chapter has now been added. User contributions and documentation
+of real-world experiences are a most welcome addition to this chapter.
+</para>
+
+<sect1>
+<title>Introduction</title>
+
+<para>
+<indexterm><primary>update</primary></indexterm>
+<indexterm><primary>upgrade</primary></indexterm>
+<indexterm><primary>frustration</primary></indexterm>
+A Windows network administrator explained in an email what changes he was
+planning to make and followed with the question: <quote>Anyone done this
+before?</quote> Many of us have upgraded and updated Samba without incident.
+Others have experienced much pain and user frustration. So it is to be hoped
+that the notes in this chapter will make a positive difference by assuring
+that someone will be saved a lot of discomfort.
+</para>
+
+<para>
+Before anyone commences an upgrade or an update of Samba, the one cardinal
+rule that must be observed is: Backup all Samba configuration files in
+case it is necessary to revert to the old version. Even if you do not like
+this precautionary step, users will punish an administrator who
+fails to take adequate steps to avoid situations that may inflict lost
+productivity on them.
+</para>
+
+<warning><para>
+<indexterm><primary>configuration files</primary></indexterm>
+<indexterm><primary>down-grade</primary></indexterm>
+Samba makes it possible to upgrade and update configuration files, but it
+is not possible to downgrade the configuration files. Please ensure that
+all configuration and control files are backed up to permit a down-grade
+in the rare event that this may be necessary.
+</para></warning>
+
+
+<para>
+<indexterm><primary>adequate precautions</primary></indexterm>
+<indexterm><primary>precaution</primary></indexterm>
+It is prudent also to backup all data files on the server before attempting
+to perform a major upgrade. Many administrators have experienced the consequences
+of failure to take adequate precautions. So what is adequate? That is simple!
+If data is lost during an upgrade or update and it can not be restored,
+the precautions taken were inadequate. If a backup was not needed, but was available,
+caution was on the side of the victor.
+</para>
+
+	<sect2>
+	<title>Cautions and Notes</title>
+
+	<para>
+	Someone once said, <quote>It is good to be sorry, but better never to need to be!</quote>
+	These are wise words of advice to those contemplating a Samba upgrade or update.
+	</para>
+
+	<para>
+	<indexterm><primary>update</primary></indexterm>
+	<indexterm><primary>upgrade</primary></indexterm>
+	<indexterm><primary>generation</primary></indexterm>
+	This is as good a time as any to define the terms <constant>upgrade</constant> and
+	<constant>update</constant>. The term <constant>upgrade</constant> refers to
+	the installation of a version of Samba that is a whole generation or more ahead of
+	that which is installed. Generations are indicated by the first digit of the version
+	number. So far Samba has been released in generations 1.x, 2.x, 3.x, and currently 4.0
+	is in development.
+	</para>
+
+	<para>
+	<indexterm><primary>generation</primary></indexterm>
+	The term <constant>update</constant> refers to a minor version number installation
+	in place of one of the same generation. For example, updating from Samba 3.0.10 to 3.0.14
+	is an update. The move from Samba 2.0.7 to 3.0.14 is an upgrade.
+	</para>
+
+	<para>
+	<indexterm><primary>functional differences</primary></indexterm>
+	While the use of these terms is an exercise in semantics, what needs to be realized
+	is that there are major functional differences between a Samba 2.x release and a Samba
+	3.0.x release. Such differences may require a significantly different approach to
+	solving the same networking challenge and generally require careful review of the
+	latest documentation to identify precisely how the new installation may need to be
+	modified to preserve prior functionality.
+	</para>
+
+	<para>
+	There is an old axiom that says, <quote>The greater the volume of the documentation,
+	the greater the risk that noone will read it, but where there is no documentation,
+	noone can read it!</quote> While true, some documentation is an evil necessity.
+	It is hoped that this update to the documentation will avoid both extremes.
+	</para>
+
+	<sect3>
+	<title>Security Identifiers (SIDs)</title>
+
+	<para>
+	<indexterm><primary>Windows</primary><secondary>NT</secondary></indexterm>
+	<indexterm><primary>OS/2</primary></indexterm>
+	<indexterm><primary>DOS</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>networking</primary><secondary>client</secondary></indexterm>
+	<indexterm><primary>security</primary><secondary>identifier</secondary></indexterm>
+	Before the days of Windows NT and OS/2, every Windows and DOS networking client
+	that used the SMB protocols was an entirely autonomous entity. There was no concept
+	of a security identifier for a machine or a user outside of the username, the
+	machine name, and the workgroup name. In actual fact, these were not security identifiers
+	in the same context as the way that the SID is used since the development of
+	Windows NT 3.10.
+	</para>
+
+	<para>
+	<indexterm><primary>SessionSetUpAndX</primary></indexterm>
+	<indexterm><primary>SMB</primary></indexterm>
+	<indexterm><primary>CIFS</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>username</primary></indexterm>
+	<indexterm><primary>Windows</primary><secondary>client</secondary></indexterm>
+	Versions of Samba prior to 1.9 did not make use of a SID. Instead they make exclusive use
+	of the username that is embedded in the SessionSetUpAndX component of the connection
+	setup process between a Windows client and an SMB/CIFS server. 
+	</para>
+
+	<para>
+	<indexterm><primary>MACHINE.SID</primary></indexterm>
+	<indexterm><primary>rpc</primary></indexterm>
+	<indexterm><primary>security</primary></indexterm>
+	Around November 1997 support was added to Samba-1.9 to handle the Windows security
+	RPC-based protocols that implemented support for Samba to store a machine SID. This
+	information was stored in a file called <filename>MACHINE.SID.</filename>
+	</para>
+
+	<para>
+	<indexterm><primary>machine</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>secrets.tdb</primary></indexterm>
+	Within the lifetime of the early Samba 2.x series, the machine SID information was
+	relocated into a tdb file called <filename>secrets.tdb</filename>, which is where
+	it is still located in Samba 3.0.x along with other information that pertains to the
+	local machine and its role within a domain security context.
+	</para>
+
+	<para>
+	<indexterm><primary>server</primary><secondary>stand-alone</secondary></indexterm>
+	<indexterm><primary>server</primary><secondary>domain member</secondary></indexterm>
+	<indexterm><primary>DMS</primary></indexterm>
+	<indexterm><primary>SAS</primary></indexterm>
+	There are two types of SID, those pertaining to the machine itself and the domain to
+	which it may belong, and those pertaining to users and groups within the security
+	context of the local machine, in the case of standalone servers (SAS) and domain member
+	servers (DMS).
+	</para>
+
+	<para>
+	<indexterm><primary>smbd</primary></indexterm>
+	<indexterm><primary>workgroup</primary></indexterm>
+	<indexterm><primary>hostname</primary></indexterm>
+	<indexterm><primary>daemon</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>secrets.tdb</primary></indexterm>
+	When the Samba <command>smbd</command> daemon is first started, if the <filename>secrets.tdb</filename>
+	file does not exist, it is created at the first client connection attempt. If this file does
+	exist, <command>smbd</command> checks that there is a machine SID (if it is a domain controller,
+	it searches for the domain SID). If <command>smbd</command> does not find one for the current
+	name of the machine or for the current name of the workgroup, a new SID will be generated and
+	then written to the <filename>secrets.tdb</filename> file. The SID is generated in a nondeterminative
+	manner. This means that each time it is generated for a particular combination of machine name
+	(hostname) and domain name (workgroup), it will be different.
+	</para>
+
+	<para>
+	<indexterm><primary>ACL</primary></indexterm>
+	The SID is the key used by MS Windows networking for all networking operations. This means
+	that when the machine or domain SID changes, all security-encoded objects such as profiles
+	and ACLs may become unusable.
+	</para>
+
+	<note><para>
+	It is of paramount importance that the machine and domain SID be backed up so that in
+	the event of a change of hostname (machine name) or domain name (workgroup) the SID can
+	be restored to its previous value.
+	</para></note>
+
+	<para>
+	<indexterm><primary>domain controller</primary></indexterm>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>domain SID</primary></indexterm>
+	<indexterm><primary>hostname</primary></indexterm>
+	<indexterm><primary>computer name</primary></indexterm>
+	<indexterm><primary>netbios name</primary></indexterm>
+	<indexterm><primary>stand-alone server</primary></indexterm>
+	<indexterm><primary>SAS</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	In Samba-3 on a domain controller (PDC or BDC), the domain name controls the domain
+	SID. On all prior versions the hostname (computer name, or NetBIOS name) controlled
+	the SID. On a standalone server the hostname still controls the SID.
+	</para>
+
+	<para>
+	<indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
+	<indexterm><primary>net</primary><secondary>setlocalsid</secondary></indexterm>
+	The local machine SID can be backed up using this procedure (Samba-3):
+<screen>
+&rootprompt; net getlocalsid > /etc/samba/my-local-SID
+</screen>
+	The contents of the file <filename>/etc/samba/my-local-SID</filename> will be:
+<screen>
+SID for domain FRODO is: S-1-5-21-726309263-4128913605-1168186429
+</screen>
+	This SID can be restored by executing:
+<screen>
+&rootprompt; net setlocalsid S-1-5-21-726309263-4128913605-1168186429
+</screen>
+	</para>
+
+	<para>
+	Samba 1.9.x stored the machine SID in the the file <filename>/etc/MACHINE.SID</filename>
+	from which it could be recovered and stored into the <filename>secrets.tdb</filename> file
+	using the procedure shown above.
+	</para>
+
+	<para>
+	Where the <filename>secrets.tdb</filename> file exists and a version of Samba 2.x or later
+	has been used, there is no specific need to go through this update process. Samba-3 has the
+	ability to read the older tdb file and to perform an in-situ update to the latest tdb format.
+	This is not a reversible process &smbmdash; it is a one-way upgrade.
+	</para>
+
+	<para>
+	<indexterm><primary>smbpasswd</primary></indexterm>
+	In the course of the Samba 2.0.x series the <command>smbpasswd</command> was modified to
+	permit the domain SID to be captured to the <filename>secrets.tdb</filename> file by executing:
+<screen>
+&rootprompt; smbpasswd -S PDC -Uadministrator%password
+</screen>
+	</para>
+
+	<para>
+	The release of the Samba 2.2.x series permitted the SID to be obtained by executing:
+<screen>
+&rootprompt; smbpasswd -S PDC -Uadministrator%password
+</screen>
+	from which the SID could be copied to a file and then written to the Samba-2.2.x
+	<filename>secrets.tdb</filename> file by executing:
+<screen>
+&rootprompt; smbpasswd -W S-1-5-21-726309263-4128913605-1168186429
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>rpcclient</primary></indexterm>
+	<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>info</tertiary></indexterm>
+	Domain security information, which includes the domain SID, can be obtained from Samba-2.2.x
+	systems by executing:
+<screen>
+&rootprompt; rpcclient hostname lsaquery -Uroot%password
+</screen>
+	This can also be done with Samba-3 by executing:
+<screen>
+&rootprompt; net rpc info -Uroot%password
+Domain Name: MIDEARTH
+Domain SID: S-1-5-21-726309263-4128913605-1168186429
+Sequence number: 1113415916
+Num users: 4237
+Num domain groups: 86
+Num local groups: 0
+</screen>
+	It is a very good practice to store this SID information in a safely kept file, just in
+	case it is ever needed at a later date.
+	</para>
+
+	<para>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	Take note that the domain SID is used extensively in Samba. Where LDAP is used for the
+	<parameter>passdb backend</parameter>, all user, group, and trust accounts are encoded
+	with the domain SID. This means that if the domain SID changes for any reason, the entire
+	Samba environment can become broken and require extensive corrective action if the 
+	original SID cannot be restored. Fortunately, it can be recovered from a dump of the
+	LDAP database. A dump of the LDAP directory database can be obtained by executing:
+<screen>
+&rootprompt; slapcat -v -l filename.ldif
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>profiles</primary></indexterm>
+	<indexterm><primary>RPM</primary></indexterm>
+	When the domain SID has changed, roaming profiles cease to be functional. The recovery
+	of roaming profiles necessitates resetting of the domain portion of the user SID
+	that owns the profile. This is encoded in the <filename>NTUser.DAT</filename> and can be
+	updated using the Samba <command>profiles</command> utility. Please be aware that not all
+	Linux distributions of the Samba RPMs include this essential utility. Please do not
+	complain to the Samba Team if this utility is missing; that issue that must be
+	addressed to the creator of the RPM package. The Samba Team do their best to make
+	available all the tools needed to manage a Samba-based Windows networking environment.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Change of hostname</title>
+
+	<para>
+	<indexterm><primary>netbios</primary><secondary>machine  name</secondary></indexterm>
+	<indexterm><primary>netbios name</primary></indexterm>
+	Samba uses two methods by which the primary NetBIOS machine name (also known as a computer
+	name or the hostname) may be determined: If the &smb.conf; file contains a
+	<parameter>netbios name</parameter> entry, its value will be used directly. In the absence
+	of such an entry, the UNIX system hostname will be used.
+	</para>
+
+	<para>
+	Many sites have become victims of lost Samba functionality because the UNIX system
+	hostname was changed for one reason or another. Such a change will cause a new machine
+	SID to be generated. If this happens on a domain controller, it will also change the
+	domain SID. These SIDs can be updated (restored) using the procedure outlined previously.
+	</para>
+
+	<note><para>
+	Do NOT change the hostname or the <parameter>netbios name</parameter>. If this
+	is changed, be sure to reset the machine SID to the original setting. Otherwise
+	there may be serious interoperability and/or operational problems.
+	</para></note>
+
+	</sect3>
+
+	<sect3>
+	<title>Change of Workgroup (Domain) Name</title>
+
+	<para>
+	<indexterm><primary>workgroup</primary></indexterm>
+	The domain name of a Samba server is identical to the workgroup name and is
+	set in the &smb.conf; file using the <parameter>workgroup</parameter> parameter.
+	This has been consistent throughout the history of Samba and across all versions.
+	</para>
+
+	<para>
+	<indexterm><primary>SID</primary></indexterm>
+	Be aware that when the workgroup name is changed, a new SID will be generated.
+	The old domain SID can be reset using the procedure outlined earlier in this chapter.
+	</para>
+
+	</sect3>
+
+	<sect3 id="sbeug1">
+	<title>Location of config files</title>
+
+	<para>
+	The Samba-Team has maintained a constant default location for all Samba control files
+	throughout the life of the project. People who have produced binary packages of Samba
+	have varied the location of the Samba control files. This has led to some confusion
+	for network administrators.
+	</para>
+
+	<para>
+	<indexterm><primary>directory</primary></indexterm>
+	The Samba 1.9.x &smb.conf; file may be found either in the <filename>/etc</filename>
+	directory or in <filename>/usr/local/samba/lib</filename>.
+	</para>
+
+	<para>
+	During the life of the Samba 2.x release, the &smb.conf; file was relocated
+	on Linux systems to the <filename>/etc/samba</filename> directory where it
+	remains located also for Samba 3.0.x installations.
+	</para>
+
+	<para>
+	<indexterm><primary>secrets.tdb</primary></indexterm>
+	Samba 2.x introduced the <filename>secrets.tdb</filename> file that is also stored in the
+	<filename>/etc/samba</filename> directory, or in the <filename>/usr/local/samba/lib</filename>
+	directory subsystem.
+	</para>
+
+	<para>
+	<indexterm><primary>smbd</primary></indexterm>
+	The location at which <command>smbd</command> expects to find all configuration and control
+	files is determined at the time of compilation of Samba. For versions of Samba prior to
+	3.0, one way to find the expected location of these files is to execute:
+<screen>
+&rootprompt; strings /usr/sbin/smbd | grep conf
+&rootprompt; strings /usr/sbin/smbd | grep secret
+&rootprompt; strings /usr/sbin/smbd | grep smbpasswd
+</screen>
+	Note: The <command>smbd</command> executable may be located in the path
+	<filename>/usr/local/samba/sbin</filename>.
+	</para>
+
+	<para>
+	<indexterm><primary>compile-time</primary></indexterm>
+	Samba-3 provides a neat new way to track the location of all control files as well as to
+	find the compile-time options used as the Samba package was built. Here  is how the dark
+	secrets of the internals of the location of control files within Samba executables can
+	be uncovered:
+<screen>
+&rootprompt; smbd -b | less
+Build environment:
+   Built by:    root@frodo
+   Built on:    Mon Apr 11 20:23:27 MDT 2005
+   Built using: gcc
+   Build host:  Linux frodo 2.6...
+   SRCDIR:      /usr/src/packages/BUILD/samba-3.0.20/source
+   BUILDDIR:    /usr/src/packages/BUILD/samba-3.0.20/source
+
+Paths:
+   SBINDIR: /usr/sbin
+   BINDIR: /usr/bin
+   SWATDIR: /usr/share/samba/swat
+   CONFIGFILE: /etc/samba/smb.conf
+   LOGFILEBASE: /var/log/samba
+   LMHOSTSFILE: /etc/samba/lmhosts
+   LIBDIR: /usr/lib/samba
+   SHLIBEXT: so
+   LOCKDIR: /var/lib/samba
+   PIDDIR: /var/run/samba
+   SMB_PASSWD_FILE: /etc/samba/smbpasswd
+   PRIVATE_DIR: /etc/samba
+ ... 
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary></primary></indexterm>
+	It is important that both the &smb.conf; file and the <filename>secrets.tdb</filename>
+	be backed up before attempting any upgrade. The <filename>secrets.tdb</filename> file
+	is version-encoded, and therefore a newer version may not work with an older version
+	of Samba. A backup means that it is always possible to revert a failed or problematic
+	upgrade.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>International Language Support</title>
+
+	<para>
+	<indexterm><primary>unicode</primary></indexterm>
+	<indexterm><primary>character set</primary></indexterm>
+	<indexterm><primary>codepage</primary></indexterm>
+	<indexterm><primary>internationalization</primary></indexterm>
+	Samba-2.x had no support for Unicode; instead, all national language character-set support in file names
+	was done using particular locale codepage mapping techniques. Samba-3 supports Unicode in file names, thus
+	providing true internationalization support.
+	</para>
+
+	<para>
+	<indexterm><primary>8-bit</primary></indexterm>
+	Non-English users whose national language character set has special characters and who upgrade naively will 
+	find that many files that have the special characters in the file name will see them garbled and jumbled up.
+	This typically happens with umlauts and accents because these characters were particular to the codepage
+	that was in use with Samba-2.x using an 8-bit encoding scheme.
+	</para>
+
+	<para>
+	<indexterm><primary>UTF-8</primary></indexterm>
+	Files that are created with Samba-3 will use UTF-8 encoding. Should the file system ever end up with a
+	mix of codepage (unix charset)-encoded file names and UTF-8-encoded file names, the mess will take some
+	effort to set straight.
+	</para>
+
+	<para>
+	<indexterm><primary>convmv</primary></indexterm>
+	A very helpful tool is available from Bjorn Jacke's <ulink url="http://j3e.de/linux/convmv/">convmv</ulink>
+	work. Convmv is a tool that can be used to convert file and directory names from one encoding method to
+	another. The most common use for this tool is to convert locale-encoded files to UTF-8 Unicode encoding.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Updates and Changes in Idealx smbldap-tools</title>
+
+	<para>
+	The smbldap-tools have been maturing rapidly over the past year. With maturation comes change.
+	The location of the <filename>smbldap.conf</filename> and the <filename>smbldap_bind.conf</filename>
+	configuration files have been moved from the directory <filename>/etc/smbldap-tools</filename> to
+	the new location of <filename>/etc/opt/IDEALX/smblda-tools</filename> directory.
+	</para>
+
+	<para>
+	The smbldap-tools maintains an entry in the LDAP directory in which it stores the next
+	values that should be used for UID and GID allocation for POSIX accounts that are created
+	using this tool. The DIT location of these values has changed recently. The original
+	<constant>sambaUnixIdPooldn object</constant> entity was stored in a directory entry (DIT object)
+	called <constant>NextFreeUnixId</constant>, this has been changed to the DIT object
+	<constant>sambaDomainName</constant>. Anyone who updates from an older version to the
+	current release should note that the information stored under <constant>NextFreeUnixId</constant>
+	must now be relocated to the DIT object <constant>sambaDomainName</constant>.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Upgrading from Samba 1.x and 2.x to Samba-3</title>
+
+<para>
+Sites that are being upgraded from Samba-2 (or earlier versions) to Samba-3
+may experience little difficulty or may require a lot of effort, depending
+on the complexity of the configuration. Samba-1.9.x upgrades to Samba-3 will
+generally be simple and straightforward, although no upgrade should be
+attempted without proper planning and preparation.
+</para>
+
+<para>
+There are two basic modes of use of Samba versions prior to Samba-3. The first
+does not use LDAP, the other does. Samba-1.9.x did not provide LDAP support.
+Samba-2.x could be compiled with LDAP support.
+</para>
+
+	<sect2 id="sbeug2">
+	<title>Samba 1.9.x and 2.x Versions Without LDAP</title>
+
+	<para>
+	Where it is necessary to upgrade an old Samba installation to Samba-3,
+	the following procedure can be followed:
+	</para>
+
+	<procedure>
+	<title>Upgrading from a Pre-Samba-3 Version</title>
+
+		<step><para>
+		<indexterm><primary>winbindd</primary></indexterm>
+		<indexterm><primary>smbd</primary></indexterm>
+		<indexterm><primary>nmbd</primary></indexterm>
+		Stop Samba. This can be done using the appropriate system tool
+		that is particular for each operating system or by executing the
+		<command>kill</command> command on <command>smbd</command>,
+		<command>nmbd</command>, and <command>winbindd</command>.
+		</para></step>
+
+		<step><para>
+		Find the location of the Samba &smb.conf; file and back it up to a
+		safe location.
+		</para></step>
+
+		<step><para>
+		Find the location of the <filename>smbpasswd</filename> file and
+		back it up to a safe location.
+		</para></step>
+
+		<step><para>
+		Find the location of the <filename>secrets.tdb</filename> file and
+		back it up to a safe location.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>lock directory</primary></indexterm>
+		<indexterm><primary>/usr/local/samba/var/locks</primary></indexterm>
+		<indexterm><primary>/var/cache/samba</primary></indexterm>
+		<indexterm><primary>/var/lib/samba</primary></indexterm>
+		Find the location of the lock directory. This is the directory
+		in which Samba stores all its tdb control files. The default
+		location used by the Samba Team is in
+		<filename>/usr/local/samba/var/locks</filename> directory,
+		but on Linux systems the old location was under the
+		<filename>/var/cache/samba</filename> directory. However, the
+		Linux Standards Base specified location is now under the
+		<filename>/var/lib/samba</filename> directory. Copy all the
+		tdb files to a safe location.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>RPM</primary></indexterm>
+		It is now safe to upgrade the Samba installation. On Linux systems
+		it is not necessary to remove the Samba RPMs because a simple
+		upgrade installation will automatically remove the old files.
+		</para>
+
+		<para>
+		On systems that do not support a reliable package management system
+		it is advisable either to delete the Samba old installation or to
+		move it out of the way by renaming the directories that contain the
+		Samba binary files.
+		</para></step>
+
+		<step><para>
+		When the Samba upgrade has been installed, the first step that should
+		be completed is to identify the new target locations for the control
+		files. Follow the steps shown in <link linkend="sbeug1"/> to locate
+		the correct directories to which each control file must be moved.
+		</para></step>
+
+		<step><para>
+		Do not change the hostname.
+		</para></step>
+
+		<step><para>
+		Do not change the workgroup name.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>testparm</primary></indexterm>
+		Execute the <command>testparm</command> to validate the &smb.conf; file.
+		This process will flag any parameters that are no longer supported.
+		It will also flag configuration settings that may be in conflict.
+		</para>
+
+		<para>
+		One solution that may be used to clean up and to update the &smb.conf;
+		file involves renaming it to <filename>smb.conf.master</filename> and 
+		then executing the following:
+<screen>
+&rootprompt; cd /etc/samba
+&rootprompt; testparm -s smb.conf.master &gt; smb.conf
+</screen>
+	<indexterm><primary>stripped</primary></indexterm>
+		The resulting &smb.conf; file will be stripped of all comments
+		and of all nonconforming configuration settings.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>winbindd</primary></indexterm>
+		It is now safe to start Samba using the appropriate system tool.
+		Alternately, it is possible to just execute <command>nmbd</command>,
+		<command>smbd</command>, and <command>winbindd</command> for the command
+		line while logged in as the root user.
+		</para></step>
+
+	</procedure>
+
+	</sect2>
+
+	<sect2>
+	<title>Applicable to All Samba 2.x to Samba-3 Upgrades</title>
+
+	<para>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>domain controller</primary></indexterm>
+	<indexterm><primary>inter-domain</primary></indexterm>
+	Samba 2.x servers that were running as a domain controller (PDC)
+	require changes to the configuration of the scripting interface
+	tools that Samba uses to perform OS updates for
+	users, groups, and trust accounts (machines and interdomain).
+	</para>
+
+	<para>
+	<indexterm><primary>parameters</primary></indexterm>
+	The following parameters are new to Samba-3 and should be correctly configured.
+	Please refer to <link linkend="secure"/> through <link linkend="2000users"/>
+	in this book for examples of use of the new parameters shown here:
+	<indexterm><primary>add group script</primary></indexterm>
+	<indexterm><primary>add machine script</primary></indexterm>
+	<indexterm><primary>add user to group script</primary></indexterm>
+	<indexterm><primary>delete group script</primary></indexterm>
+	<indexterm><primary>delete user from group script</primary></indexterm>
+	<indexterm><primary>set primary group script</primary></indexterm>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	</para>
+
+	<para>
+	<simplelist>
+		<member><para>add group script</para></member>
+		<member><para>add machine script</para></member>
+		<member><para>add user to group script</para></member>
+		<member><para>delete group script</para></member>
+		<member><para>delete user from group script</para></member>
+		<member><para>passdb backend</para></member>
+		<member><para>set primary group script</para></member>
+		</simplelist>
+	</para>
+
+	<para>
+	<indexterm><primary>add machine script</primary></indexterm>
+	<indexterm><primary>add user script</primary></indexterm>
+	The <parameter>add machine script</parameter> functionality was previously
+	handled by the <parameter>add user script</parameter>, which in Samba-3 is
+	used exclusively to add user accounts.
+	</para>
+
+	<para>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	<indexterm><primary>smbpasswd</primary></indexterm>
+	<indexterm><primary>tdbsam</primary></indexterm>
+	<indexterm><primary>useradd</primary></indexterm>
+	<indexterm><primary>usermod</primary></indexterm>
+	<indexterm><primary>userdel</primary></indexterm>
+	<indexterm><primary>groupadd</primary></indexterm>
+	<indexterm><primary>groupmod</primary></indexterm>
+	<indexterm><primary>groupdel</primary></indexterm>
+	Where the <parameter>passdb backend</parameter> used is either <constant>smbpasswd</constant>
+	(the default) or the new <constant>tdbsam</constant>, the system interface scripts
+	are typically used. These involve use of OS tools such as <command>useradd</command>,
+	<command>usermod</command>, <command>userdel</command>, <command>groupadd</command>,
+	<command>groupmod</command>, <command>groupdel</command>, and so on.
+	</para>
+
+	<para>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>Idealx</primary></indexterm>
+	Where the <parameter>passdb backend</parameter> makes use of an LDAP directory,
+	it is necessary either to use the <constant>smbldap-tools</constant> provided
+	by Idealx or to use an alternate toolset provided by a third
+	party or else home-crafted to manage the LDAP directory accounts.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Samba-2.x with LDAP Support</title>
+
+	<para>
+	Samba version 2.x could be compiled for use either with or without LDAP.
+	The LDAP control settings in the &smb.conf; file in this old version are
+	completely different (and less complete) than they are with Samba-3. This
+	means that after migrating the control files, it is necessary to reconfigure
+	the LDAP settings entirely.
+	</para>
+
+	<para>
+	Follow the procedure outlined in <link linkend="sbeug2"/> to affect a migration
+	of all files to the correct locations.
+	</para>
+
+	<para>
+	<indexterm><primary>schema</primary></indexterm>
+	<indexterm><primary>WHATSNEW.txt</primary></indexterm>
+	The Samba SAM schema required for Samba-3 is significantly different from that
+	used with Samba 2.x. This means that the LDAP directory must be updated
+	using the procedure outlined in the Samba WHATSNEW.txt file that accompanies
+	all releases of Samba-3. This information is repeated here directly from this
+	file:
+<screen>
+This is an extract from the Samba-3.0.x WHATSNEW.txt file:
+==========================================================
+Changes in Behavior
+-------------------
+
+The following issues are known changes in behavior between Samba 2.2 and
+Samba 3.0 that may affect certain installations of Samba.
+
+  1)  When operating as a member of a Windows domain, Samba 2.2 would
+      map any users authenticated by the remote DC to the 'guest account'
+      if a uid could not be obtained via the getpwnam() call.  Samba 3.0
+      rejects the connection as NT_STATUS_LOGON_FAILURE.  There is no
+      current work around to re-establish the 2.2 behavior.
+
+  2)  When adding machines to a Samba 2.2 controlled domain, the
+      'add user script' was used to create the UNIX identity of the
+      machine trust account.  Samba 3.0 introduces a new 'add machine
+      script' that must be specified for this purpose.  Samba 3.0 will
+      not fall back to using the 'add user script' in the absence of
+      an 'add machine script'
+
+######################################################################
+Passdb Backends and Authentication
+##################################
+
+There have been a few new changes that Samba administrators should be
+aware of when moving to Samba 3.0.
+
+  1) encrypted passwords have been enabled by default in order to
+     inter-operate better with out-of-the-box Windows client
+     installations.  This does mean that either (a) a samba account
+     must be created for each user, or (b) 'encrypt passwords = no'
+     must be explicitly defined in smb.conf.
+
+  2) Inclusion of new 'security = ads' option for integration
+     with an Active Directory domain using the native Windows
+     Kerberos 5 and LDAP protocols.
+
+     MIT kerberos 1.3.1 supports the ARCFOUR-HMAC-MD5 encryption
+     type which is necessary for servers on which the
+     administrator password has not been changed, or kerberos-enabled
+     SMB connections to servers that require Kerberos SMB signing.
+     Besides this one difference, either MIT or Heimdal Kerberos
+     distributions are usable by Samba 3.0.
+
+
+Samba 3.0 also includes the possibility of setting up chains
+of authentication methods (auth methods) and account storage
+backends (passdb backend).  Please refer to the smb.conf(5)
+man page for details.  While both parameters assume sane default
+values, it is likely that you will need to understand what the
+values actually mean in order to ensure Samba operates correctly.
+
+The recommended passdb backends at this time are
+
+  * smbpasswd - 2.2 compatible flat file format
+  * tdbsam - attribute rich database intended as an smbpasswd
+    replacement for stand alone servers
+  * ldapsam - attribute rich account storage and retrieval
+    backend utilizing an LDAP directory.
+  * ldapsam_compat - a 2.2 backward compatible LDAP account
+    backend
+
+Certain functions of the smbpasswd(8) tool have been split between the
+new smbpasswd(8) utility, the net(8) tool, and the new pdbedit(8)
+utility.  See the respective man pages for details.
+
+######################################################################
+LDAP
+####
+
+This section outlines the new features affecting Samba / LDAP
+integration.
+
+New Schema
+----------
+
+A new object class (sambaSamAccount) has been introduced to replace
+the old sambaAccount.  This change aids us in the renaming of
+attributes to prevent clashes with attributes from other vendors.
+There is a conversion script (examples/LDAP/convertSambaAccount) to
+modify and LDIF file to the new schema.
+
+Example:
+
+  $ ldapsearch .... -b "ou=people,dc=..." &gt; sambaAcct.ldif
+  $ convertSambaAccount --sid=&lt;Domain SID&gt; \
+    --input=sambaAcct.ldif --output=sambaSamAcct.ldif \
+    --changetype=[modify|add]
+
+The &lt;DOM SID&gt; can be obtained by running 'net getlocalsid
+&lt;DOMAINNAME&gt;' on the Samba PDC as root.  The changetype determines
+the format of the generated LDIF output--either create new entries
+or modify existing entries.
+
+The old sambaAccount schema may still be used by specifying the
+"ldapsam_compat" passdb backend.  However, the sambaAccount and
+associated attributes have been moved to the historical section of
+the schema file and must be uncommented before use if needed.
+The 2.2 object class declaration for a sambaAccount has not changed
+in the 3.0 samba.schema file.
+
+Other new object classes and their uses include:
+
+  * sambaDomain - domain information used to allocate rids
+    for users and groups as necessary.  The attributes are added
+    in 'ldap suffix' directory entry automatically if
+    an idmap uid/gid range has been set and the 'ldapsam'
+    passdb backend has been selected.
+
+  * sambaGroupMapping - an object representing the
+    relationship between a posixGroup and a Windows
+    group/SID.  These entries are stored in the 'ldap
+    group suffix' and managed by the 'net groupmap' command.
+
+  * sambaUnixIdPool - created in the 'ldap idmap suffix' entry
+    automatically and contains the next available 'idmap uid' and
+    'idmap gid'
+
+  * sambaIdmapEntry - object storing a mapping between a
+    SID and a UNIX uid/gid.  These objects are created by the
+    idmap_ldap module as needed.
+
+  * sambaSidEntry - object representing a SID alone, as a Structural
+    class on which to build the sambaIdmapEntry.
+
+
+New Suffix for Searching
+------------------------
+
+The following new smb.conf parameters have been added to aid in directing
+certain LDAP queries when 'passdb backend = ldapsam://...' has been
+specified.
+
+  * ldap suffix         - used to search for user and computer accounts
+  * ldap user suffix    - used to store user accounts
+  * ldap machine suffix - used to store machine trust accounts
+  * ldap group suffix   - location of posixGroup/sambaGroupMapping entries
+  * ldap idmap suffix   - location of sambaIdmapEntry objects
+
+If an 'ldap suffix' is defined, it will be appended to all of the
+remaining sub-suffix parameters.  In this case, the order of the suffix
+listings in smb.conf is important.  Always place the 'ldap suffix' first
+in the list.
+
+Due to a limitation in Samba's smb.conf parsing, you should not surround
+the DN's with quotation marks.
+</screen>
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Updating a Samba-3 Installation</title>
+
+<para>
+The key concern in this section is to deal with the changes that have been
+affected in Samba-3 between the Samba-3.0.0 release and the current update.
+Network administrators have expressed concerns over the steps that should be
+taken to update Samba-3 versions.
+</para>
+
+<para>
+<indexterm><primary>control files</primary></indexterm>
+The information in <link linkend="sbeug1"/> would not be necessary if every
+person who has ever produced Samba executable (binary) files could agree on
+the preferred location of the &smb.conf; file and other Samba control files.
+Clearly, such agreement is further away than a pipedream.
+</para>
+
+<para>
+<indexterm><primary>vendors</primary></indexterm>
+Vendors and packagers who produce Samba binary installable packages do not,
+as a rule, use the default paths used by the Samba-Team for the location of
+the binary files, the &smb.conf; file, and the Samba control files (tdb's
+as well as files such as <filename>secrets.tdb</filename>). This means that
+the network or UNIX administrator who sets out to build the Samba executable
+files from the Samba tarball must take particular care. Failure to take care
+will result in both the original vendor's version of Samba remaining installed
+and the new version being installed in the default location used
+by the Samba-Team. This can lead to confusion and to much lost time as the
+uninformed administrator deals with apparent failure of the update to take
+effect.
+</para>
+
+<para>
+<indexterm><primary>packages</primary></indexterm>
+The best advice for those lacking in code compilation experience is to use
+only vendor (or Samba-Team) provided binary packages. The Samba packages
+that are provided by the Samba-Team are generally built to use file paths
+that are compatible with the original OS vendor's practices.
+</para>
+
+<para>
+<indexterm><primary>binary package</primary></indexterm>
+<indexterm><primary>binary files</primary></indexterm>
+If you are not sure whether a binary package complies with the OS
+vendor's practices, it is better to ask the package maintainer via
+email than to waste much time dealing with the nuances.
+Alternately, just diagnose the paths specified by the binary files following
+the procedure outlined above.
+</para>
+
+	<sect2>
+	<title>Samba-3 to Samba-3 Updates on the Same Server</title>
+
+	<para>
+	The guidance in this section deals with updates to an existing
+	Samba-3 server installation.
+	</para>
+
+	<sect3>
+	<title>Updating from Samba Versions Earlier than 3.0.5</title>
+
+	<para>
+	With the provision that the binary Samba-3 package has been built
+	with the same path and feature settings as the existing Samba-3
+	package that is being updated, an update of Samba-3 versions 3.0.0
+	through 3.0.4 can be updated to 3.0.5 without loss of functionality
+	and without need to change either the &smb.conf; file or, where
+	used, the LDAP schema.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Updating from Samba Versions between 3.0.6 and 3.0.10</title>
+
+	<para>
+	<indexterm><primary>schema</primary></indexterm>
+	<indexterm><primary>LDAP</primary><secondary>schema</secondary></indexterm>
+	When updating versions of Samba-3 prior to 3.0.6 to 3.0.6 through 3.0.10,
+	it is necessary only to update the LDAP schema (where LDAP is used).
+	Always use the LDAP schema file that is shipped with the latest Samba-3
+	update.
+	</para>
+
+	<para>
+	<indexterm><primary>ldapsam</primary></indexterm>
+	<indexterm><primary>tdbsam</primary></indexterm>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	Samba-3.0.6 introduced the ability to remember the last <emphasis>n</emphasis> number
+	of passwords a user has used. This information will work only with
+	the <constant>tdbsam</constant> and <constant>ldapsam</constant>
+	<parameter>passdb backend</parameter> facilities.
+	</para>
+
+	<para>
+	After updating the LDAP schema, do not forget to re-index the LDAP database.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Updating from Samba Versions after 3.0.6 to a Current Release</title>
+
+	<para>
+	<indexterm><primary>winbindd</primary></indexterm>
+	Samba-3.0.8 introduced changes in how the <parameter>username map</parameter>
+	behaves. It also included a change in behavior of <command>winbindd</command>.
+	Please refer to the man page for &smb.conf; before implementing any update
+	from versions prior to 3.0.8 to a current version.
+	</para>
+
+	<para>
+	<indexterm><primary>privileges</primary></indexterm>
+	In Samba-3.0.11 a new privileges interface was implemented. Please
+	refer to <link linkend="sbehap-ppc"/> for information regarding this new
+	feature. It is not necessary to implement the privileges interface, but it
+	is one that has been requested for several years and thus may be of interest
+	at your site.
+	</para>
+
+	<para>
+	In Samba-3.0.11 there were some functional changes to the <parameter>ldap user
+	suffix</parameter> and to the <parameter>ldap machine suffix</parameter> behaviors.
+	The following information has been extracted from the WHATSNEW.txt file from this
+	release:
+<screen>
+============
+LDAP Changes
+============
+
+If "ldap user suffix" or "ldap machine suffix" are defined in
+smb.conf, all user-accounts must reside below the user suffix,
+and all machine and inter-domain trust-accounts must be located
+below the machine suffix.  Previous Samba releases would fall
+back to searching the 'ldap suffix' in some cases.
+</screen>
+	</para>
+
+	</sect3>
+	</sect2>
+
+	<sect2>
+	<title>Migrating Samba-3 to a New Server</title>
+
+	<para>
+	The two most likely candidates for replacement of a server are
+	domain member servers and domain controllers. Each needs to be
+	handled slightly differently.
+	</para>
+
+	<sect3>
+	<title>Replacing a Domain Member Server</title>
+
+	<para>
+	<indexterm><primary>DMS</primary></indexterm>
+	Replacement of a domain member server should be done
+	using the same procedure as outlined in <link linkend="unixclients"/>.
+	</para>
+
+	<para>
+	Usually the new server will be introduced with a temporary name. After
+	the old server data has been migrated to the new server, it is customary
+	that the new server be renamed to that of the old server. This will
+	change its SID and will necessitate rejoining to the domain.
+	</para>
+
+	<para>
+	<indexterm><primary>smbd</primary></indexterm>
+	<indexterm><primary>nmbd</primary></indexterm>
+	<indexterm><primary>winbindd</primary></indexterm>
+	<indexterm><primary>wins.dat</primary></indexterm>
+	<indexterm><primary>browse.dat</primary></indexterm>
+	<indexterm><primary>resolution</primary></indexterm>
+	Following a change of hostname (NetBIOS name) it is a good idea on all servers
+	to shut down the Samba <command>smbd</command>, <command>nmbd</command>, and
+	<command>winbindd</command> services, delete the <filename>wins.dat</filename>
+	and <filename>browse.dat</filename> files, then restart Samba. This will ensure
+	that the old name and IP address information is no longer able to interfere with
+	name to IP address resolution.  If this is not done, there can be temporary name
+	resolution problems. These problems usually clear within 45 minutes of a name
+	change, but can persist for a longer period of time.
+	</para>
+
+	<para>
+	<indexterm><primary>DMS</primary></indexterm>
+	<indexterm><primary>/etc/passwd</primary></indexterm>
+	<indexterm><primary>/etc/shadow</primary></indexterm>
+	<indexterm><primary>/etc/group</primary></indexterm>
+	If the old domain member server had local accounts, it is necessary to create
+	on the new domain member server the same accounts with the same UID and GID
+	for each account. Where the <parameter>passdb backend</parameter> database
+	is stored in the <constant>smbpasswd</constant> or in the
+	<constant>tdbsam</constant> format, the user and group account information
+	for UNIX accounts that match the Samba accounts will reside in the system
+	<filename>/etc/passwd</filename>, <filename>/etc/shadow</filename>, and
+	<filename>/etc/group</filename> files. In this case, be sure to copy these
+	account entries to the new target server.
+	</para>
+
+	<para>
+	<indexterm><primary>nss_ldap</primary></indexterm>
+	Where the user accounts for both UNIX and Samba are stored in LDAP, the new
+	target server must be configured to use the <command>nss_ldap</command> tool set.
+	This will automatically ensure that the appropriate user entities are
+	available on the new server.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Replacing a Domain Controller</title>
+
+	<para>
+	<indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
+	In the past, people who replaced a Windows NT4 domain controller typically
+	installed a new server, created printers and file shares on it, then migrate across
+	all data that was destined to reside on it. The same can of course be done with
+	Samba.
+	</para>
+
+	<para>
+	From recent mailing list postings it would seem that some administrators
+	have the intent to just replace the old Samba server with a new one with
+	the same name as the old one. In this case, simply follow the same process
+	as for upgrading a Samba 2.x system and do the following:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Where UNIX (POSIX) user and group accounts are stored in the system
+		<filename>/etc/passwd</filename>, <filename>/etc/shadow</filename>, and 
+		<filename>/etc/group</filename> files, be sure to add the same accounts
+		with identical UID and GID values for each user.
+		</para>
+
+		<para>
+		Where LDAP is used, if the new system is intended to be the LDAP server,
+		migrate it across by configuring the LDAP server 
+		(<filename>/etc/openldap/slapd.conf</filename>). The directory can
+		be populated either initially by setting this LDAP server up as a slave or
+		by dumping the data from the old LDAP server using the <command>slapcat</command>
+		command and then reloading the same data into the new LDAP server using the
+		<command>slapadd</command> command. Do not forget to install and configure
+		the <command>nss_ldap</command> tool and the <filename>/etc/nsswitch.conf</filename>
+		(as shown in <link linkend="happy"/>).
+		</para></listitem>
+
+		<listitem><para>
+		Copy the &smb.conf; file from the old server to the new server into the correct
+		location as indicated previously in this chapter.
+		</para></listitem>
+
+		<listitem><para>
+		Copy the <filename>secrets.tdb</filename> file, the <filename>smbpasswd</filename>
+		file (if it is used), the <filename>/etc/samba/passdb.tdb</filename> file (only
+		used by the <constant>tdbsam</constant> backend), and all the tdb control files
+		from the old system to the correct location on the new system.
+		</para></listitem>
+
+		<listitem><para>
+		Before starting the Samba daemons, verify that the hostname of the new server
+		is identical to that of the old one. Note: The IP address can be different
+		from that of the old server.
+		</para></listitem>
+
+		<listitem><para>
+		Copy all files from the old server to the new server, taking precaution to
+		preserve all file ownership and permissions as well as any POSIX ACLs that
+		may have been created on the old server.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	When replacing a Samba domain controller (PDC or BDC) that uses LDAP, the new server
+	need simply be configured to use the LDAP directory, and for the rest it should just
+	work. The domain SID is obtained from the LDAP directory as part of the first connect
+	to the LDAP directory server.
+	</para>
+
+	<para>
+	All Samba servers, other than one that uses LDAP, depend on the tdb files, and
+	particularly on the <filename>secrets.tdb</filename> file. So long as the tdb files are
+	all in place, the &smb.conf; file is preserved, and either the hostname is identical
+	or the <parameter>netbios name</parameter> is set to the original server name, Samba
+	should correctly pick up the original SID and preserve all other settings. It is
+	sound advice to validate this before turning the system over to users.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Migration of Samba Accounts to Active Directory</title>
+
+	<para>
+	Yes, it works. The Windows ADMT tool can be used to migrate Samba accounts
+	to MS Active Directory.  There are a few pitfalls to be aware of:
+	</para>
+
+	<procedure>
+	<title>Migration to Active Directory</title>
+
+		<step><para>
+		Administrator password must be THE SAME on the Samba server,
+		the 2003 ADS, and the local Administrator account on the workstations. 
+		Perhaps this goes without saying, but there needs to be an account
+		called <constant>Administrator</constant> in your Samba domain, with 
+		full administrative (root) rights to that domain.
+		</para></step>
+
+		<step><para>
+		In the Advanced/DNS section of the TCP/IP settings on your Windows 
+		workstations, make sure the <parameter>DNS suffix for this 
+		connection</parameter> field is blank. 
+		</para></step>
+
+		<step><para>
+		Because you are migrating from Samba, user passwords cannot be 
+		migrated. You'll have to reset everyone's passwords. (If you were 
+		migrating from NT4 to ADS, you could migrate passwords as well.)
+		</para>
+
+		<para>
+		To date this has not been attempted with roaming profile support;
+		it has been documented as working with local profiles.
+		</para></step>
+
+		<step><para>
+		Disable the Windows Firewall on all workstations. Otherwise, 
+		workstations won't be migrated to the new domain.
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>ADMT</primary></indexterm>
+		When migrating machines, always test first (using ADMT's test mode) 
+		and satisfy all errors before committing the migration. Note that the 
+		test will always fail, because the machine will not have been actually 
+		migrated. You'll need to interpret the errors to know whether the 
+		failure was due to a problem or simply to the fact that it was just 
+		a test.
+		</para></step>
+
+	</procedure>
+
+
+	<para>
+	<indexterm><primary>ADMT</primary></indexterm>
+	There are some significant benefits of using the ADMT, besides just 
+	migrating user accounts. ADMT can be found on the Windows 2003 CD.
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		You can migrate workstations remotely. You can specify that SIDs 
+		be simply added instead of replaced, giving you the option of joining a 
+		workstation back to the old domain if something goes awry. The 
+		workstations will be joined to the new domain.
+		</para></listitem>
+
+		<listitem><para>
+		Not only are user accounts migrated from the old domain to the new 
+		domain, but ACLs on the workstations are migrated as well. Like SIDs, 
+		ACLs can be added instead of replaced.
+		</para></listitem>
+
+		<listitem><para>
+		Locally stored user profiles on workstations are migrated as well, 
+		presenting almost no disruption to the user. Saved passwords will be 
+		lost, just as when you administratively reset the password in Windows ADS.
+		</para></listitem>
+
+		<listitem><para>
+		The ADMT lets you test all operations before actually performing the 
+		migration. Accounts and workstations can be migrated individually or in 
+		batches. User accounts can be safely migrated all at once (since no 
+		changes are made on the original domain). It is recommended to migrate only one 
+		or two workstations as a test before committing them all.
+		</para></listitem>
+
+	</itemizedlist>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-ByExample/SBE-acknowledgements.xml b/docs-xml/Samba3-ByExample/SBE-acknowledgements.xml
new file mode 100644
index 00000000000..4cbac7fc26e
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-acknowledgements.xml
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<preface lang="en-US">
+<title>Acknowledgments</title>
+
+	<para>
+	<emphasis>Samba-3 by Example</emphasis> would not have been written except
+	as a result of feedback provided by reviewers and readers of the book <emphasis>The
+	Official Samba-3 HOWTO and Reference Guide.</emphasis> This second edition
+	was made possible by generous feedback from Samba users. I hope this book
+	more than answers the challenge and needs of many more networks that are
+	languishing for a better networking solution.
+	</para>
+
+	<para>
+	I am deeply indebted to a large group of diligent people. Space prevents 
+	me from listing all of them, but a few stand out as worthy of mention.
+	Jelmer Vernooij made the notable contribution of building the XML production
+	environment and thereby made possible the typesetting of this book.
+	</para>
+
+	<para>
+	Samba would not have come into existence if Andrew Tridgell had not taken
+	the first steps. He continues to lead the project. Under the shadow of his
+	mantle are some great folks who never give up and are always ready to help.
+	Thank you to: Jeremy Allison, Jerry Carter, Andrew Bartlett, Jelmer Vernooij,
+	Alexander Bokovoy, Volker Lendecke, and other team members who answered my 
+	continuous stream of questions &smbmdash; all of which resulted in improved content 
+	in this book.
+	</para>
+
+	<para>
+	My heartfelt thanks go out also to a small set of reviewers (alphabetically 
+	listed) who gave substantial feedback and significant suggestions for improvement:
+	Tony Earnshaw, William Enestvedt, Eric Hines, Roland Gruber, Gavin Henry, 
+	Steven Henry, Luke Howard, Tarjei Huse, Jon Johnston, Alan Munter, Mike MacIsaac,
+	Scott Mann, Ed Riddle, Geoff Scott, Santos Soler, Misty Stanley-Jones, Mark Taylor,
+	and J�r�me Tournier.
+	</para>
+
+	<para>
+	My appreciation is extended to a team of more than 30 additional reviewers who
+	helped me to find my way around dark corners.
+	</para>
+
+	<para>
+	Particular mention is due to Lyndell, Amos, and Melissa who gave me the 
+	latitude necessary to spend nearly an entire year writing Samba documentation,
+	and then gave more so this second edition could be created.
+	</para>
+
+</preface>
diff --git a/docs-xml/Samba3-ByExample/SBE-foreword.xml b/docs-xml/Samba3-ByExample/SBE-foreword.xml
new file mode 100644
index 00000000000..08c1644df9a
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-foreword.xml
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<preface lang="en-US">
+<title>Foreword</title>
+
+<sect1><title>By John M. Weathersby, Executive Director, OSSI</title>
+<blockquote>
+
+<para>
+The Open Source Software Institute (OSSI) is comprised of representatives from a broad spectrum of business and
+non-business organizations that share a common interest in the promotion of development and implementation
+of open source software solutions globally, and in particular within the United States of America.
+</para>
+
+<para>
+The OSSI has global affiliations with like-minded organizations. Our affiliate in the United Kingdom is the
+Open Source Consortium (OSC). Both the OSSI and the OSC share a common objective to expand the use of open source
+software in federal, state, and municipal government agencies; and in academic institutions. We represent
+businesses that provide professional support services that answer the needs of our target organizational
+information technology consumers in an effective and cost-efficient manner.
+</para>
+
+<para>
+Open source software has matured greatly over the past five years with the result that an increasing number of
+people who hold key decisionmaking positions want to know how the business model works. They
+want to understand how problems get resolved, how questions get answered, and how the development model
+is sustained. Information and communications technology directors in defense organizations, and in other
+government agencies that deal with sensitive information, want to become familiar with development road-maps
+and, in particular, seek to evaluate the track record of the mainstream open source project teams.
+</para>
+
+<para>
+Wherever the OSSI gains entrance to new opportunities we find that Microsoft Windows technologies are the 
+benchmark against which open source software solutions are measured. Two open source software projects
+are key to our ability to present a structured and convincing proposition that there are alternatives
+to the incumbent proprietary means of meeting information technology needs. They are the Apache Web Server
+and Samba.
+</para>
+
+<para>
+Just as the Apache Web Server is the standard in web serving technology, Samba is the definitive standard
+for providing interoperability with UNIX systems and other non-Microsoft operating system platforms. Both
+open source applications have a truly remarkable track record that extends for more than a decade. Both have
+demonstrated the unique capacity to innovate and maintain a level of development that has not only kept
+pace with demands, but, in many areas, each project has also proven to be an industry leader.
+</para>
+
+<para>
+One of the areas in which the Samba project has demonstrated key leadership is in documentation. The OSSI
+was delighted when we saw the Samba Team, and John H. Terpstra in particular, release two amazingly
+well-written books to help Samba software users deploy, maintain, and troubleshoot Windows networking
+installations. We were concerned that, given the large volume of documentation, the challenge to maintain
+it and keep it current might prove difficult.
+</para>
+
+<para>
+This second edition of the book, <emphasis>Samba-3 by Example</emphasis>, barely one year following the release
+of the first edition, has removed all concerns and is proof that open source solutions are a compelling choice.
+The first edition was released shortly following the release of Samba version 3.0 itself, and has become
+the authoritative instrument for training and for guiding deployment.
+</para>
+
+<para>
+I am personally aware of how much effort has gone into this second edition. John Terpstra has worked with
+government bodies and with large organizations that have deployed Samba-3 since it was released. He also
+worked to ensure that this book gained community following. He asked those who have worked at the coalface
+of large and small organizations alike, to contribute their experiences. He has captured that in this book
+and has succeeded yet again. His recipe is persistence, intuition, and a high level of respect for the people
+who use Samba.
+</para>
+
+<para>
+This book is the first source you should turn to before you deploy Samba and as you are mastering its
+deployment. I am proud and excited to be associated in a small way with such a useful tool. This book has
+reached maturity that is demonstrated by reiteration that every step in deployment must be validated.
+This book makes it easy to succeed, and difficult to fail, to gain a stable network environment.
+</para>
+
+<para>
+I recommend this book for use by all IT managers and network administrators.
+</para>
+
+</blockquote>
+
+</sect1>
+
+</preface>
diff --git a/docs-xml/Samba3-ByExample/SBE-front-matter.xml b/docs-xml/Samba3-ByExample/SBE-front-matter.xml
new file mode 100644
index 00000000000..1afd6cd14b4
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-front-matter.xml
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<preface lang="en-US">
+<title>Front Matter</title>
+
+	<para>
+	Just a place holder.
+	</para>
+
+</preface>
diff --git a/docs-xml/Samba3-ByExample/SBE-glossary.xml b/docs-xml/Samba3-ByExample/SBE-glossary.xml
new file mode 100644
index 00000000000..71248cfabbd
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-glossary.xml
@@ -0,0 +1,258 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE glossary PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<glossary>
+	<title>Glossary</title>
+
+	<glossentry>
+		<glossterm>Access Control List</glossterm>
+		<acronym>ACL</acronym>
+		<glossdef><para>
+		A detailed list of permissions granted to users or groups with respect to file and network
+		resource access.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+                <glossterm>Active Directory Service</glossterm>
+		<acronym>ADS</acronym>
+		<glossdef><para>
+		A service unique to Microsoft Windows 200x servers that provides a centrally managed
+		directory for management of user identities and computer objects, as well as the
+		permissions each user or computer may be granted to access distributed network resources.
+		ADS uses Kerberos-based authentication and LDAP over Kerberos for directory access.
+		</para></glossdef>
+        </glossentry>
+
+	<glossentry>
+		<glossterm>Common Internet File System</glossterm>
+		<acronym>CIFS</acronym>
+		<glossdef><para>
+		The new name for SMB. Microsoft renamed the SMB protocol to CIFS during
+		the Internet hype in the 1990s. At about the time that the SMB protocol was renamed
+		to CIFS, an additional dialect of the SMB protocol was in development. The need for the
+		deployment of the NetBIOS layer was also removed, thus paving the way for use of the SMB
+		protocol natively over TCP/IP (known as NetBIOS-less SMB or <quote>naked</quote> TCP
+		transport).
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Common UNIX Printing System</glossterm>
+		<acronym>CUPS</acronym>
+		<glossdef><para>
+		A recent implementation of a high-capability printing system for UNIX developed by
+		<ulink url="http://www.easysw.com/">Easy Software Inc.</ulink>. The design objective
+		of CUPS was to provide a rich print processing system that has built-in intelligence
+		that is capable of correctly rendering (processing) a file that is submitted for
+		printing even if it was formatted for an entirely different printer.
+		</para>
+		</glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Domain Master Browser</glossterm>
+		<acronym>DMB</acronym>
+		<glossdef><para>
+		The Domain Master Browser maintains a list of all the servers that
+		have announced their services within a given workgroup or NT domain.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+                <glossterm>Domain Name Service</glossterm>
+		<acronym>DNS</acronym>
+		<glossdef><para>
+		A protocol by which computer hostnames may be resolved to the matching IP address/es.
+		DNS is implemented by the Berkeley Internet Name Daemon. There exists a recent version
+		of DNS that allows dynamic name registration by network clients or by a DHCP server.
+		This recent protocol is known as dynamic DNS (DDNS).
+		</para></glossdef>
+        </glossentry>
+
+	<glossentry>
+                <glossterm>Dynamic Host Configuration Protocol</glossterm>
+		<acronym>DHCP</acronym>
+		<glossdef><para>
+		A protocol that was based on the BOOTP protocol that may be used to dynamically assign
+		an IP address, from a reserved pool of addresses, to a network client or device.
+		Additionally, DHCP may assign all network configuration settings and may be used to
+		register a computer name and its address with a dynamic DNS server.
+		</para></glossdef>
+        </glossentry>
+
+	<glossentry>
+		<glossterm>Group IDentifier</glossterm>
+		<acronym>GID</acronym>
+		<glossdef><para>
+		The UNIX system group identifier; on older systems, a 32-bit unsigned integer, and on
+		newer systems, an unsigned 64-bit integer. The GID is used in UNIX-like operating systems
+		for all group-level access control.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Key Distribution Center</glossterm>
+		<acronym>KDC</acronym>
+		<glossdef><para>
+		The Kerberos authentication protocol makes use of security keys (also called a ticket)
+		by which access to network resources is controlled. The issuing of Kerberos tickets
+		is effected by a KDC.
+		</para></glossdef>
+	</glossentry>
+
+    <glossentry>
+      <glossterm>Lightweight Directory Access Protocol</glossterm>
+      <acronym>LDAP</acronym>
+      <glossdef>
+	<para>
+	The Lightweight Directory Access Protocol is a technology that
+	  originated from the development of X.500 protocol specifications and
+	  implementations. LDAP was designed as a means of rapidly searching
+	  through X.500 information. Later LDAP was adapted as an engine that
+	  could drive its own directory database. LDAP is not a database per
+	  se; rather it is a technology that enables high-volume search and
+	  locate activity from clients that wish to obtain simply defined
+	  information about a subset of records that are stored in a
+	  database. LDAP does not have a particularly efficient mechanism for
+	  storing records in the database, and it has no concept of transaction
+	  processing nor of mechanisms for preserving data consistency. LDAP is
+	  premised around the notion that the search and read activity far
+	  outweigh any need to add, delete, or modify records. LDAP does
+	  provide a means for replication of the database to keep slave
+	  servers up to date with a master. It also has built-in capability to
+	  handle external references and deferral.
+	</para></glossdef>
+    </glossentry>
+
+	<glossentry>
+		<glossterm>Local Master Browser</glossterm>
+		<acronym>LMB</acronym>
+		<glossdef><para>
+		The Local Master Browser maintains a list of all servers that have announced themselves
+		within a given workgroup or NT domain on a particular broadcast isolated subnet.
+		</para></glossdef>
+	</glossentry>
+
+        <glossentry>
+                <glossterm>Media Access Control</glossterm>
+		<acronym>MAC</acronym>
+                <glossdef><para>
+		The hard-coded address of the physical-layer device that is attached to the network.
+		All network interface controllers must have a hard-coded and unique MAC address. The
+		MAC address is 48 bits long.
+                </para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>NetBIOS Extended User Interface</glossterm>
+		<acronym>NetBEUI</acronym>
+		<glossdef><para>
+		Very simple network protocol invented by IBM and Microsoft. It is used to do NetBIOS
+		over Ethernet with low overhead. NetBEUI is a non-routable protocol.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Network Address Translation</glossterm>
+                <acronym>NAT</acronym>
+                <glossdef><para>
+		Network address translation is a form of IP address masquerading. It ensures that internal
+		private (RFC1918) network addresses from packets inside the network are rewritten so
+		that TCP/IP packets that leave the server over a public connection are seen to come only
+		from the external network address.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Network Basic Input/Output System</glossterm>
+		<acronym>NetBIOS</acronym>
+		<glossdef><para>
+		NetBIOS is a simple application programming interface (API) invented in the 1980s
+		that allows programs to send data to certain network names. NetBIOS is always run over
+		another network protocol such as IPX/SPX, TCP/IP, or Logical Link Control (LLC).
+		NetBIOS run over LLC is best known as NetBEUI (the NetBIOS Extended User Interface
+		&smbmdash; a complete misnomer!).
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>NetBT</glossterm>
+		<acronym>NBT</acronym>
+		<glossdef><para>
+		Protocol for transporting NetBIOS frames over TCP/IP. Uses ports 137, 138, and 139.
+		NetBT is a fully routable protocol.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>NT/LanManager Security Support Provider</glossterm>
+		<acronym>NTLMSSP</acronym>
+		<glossdef><para>
+		The NTLM Security Support Provider (NTLMSSP) service in Windows NT4/200x/XP is responsible for
+		handling all NTLM authentication requests. It is the front end for protocols such as SPNEGO,
+		Schannel, and other technologies. The generic protocol family supported by NTLMSSP is known as
+		GSSAPI, the Generic Security Service Application Program Interface specified in RFC2078.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Server Message Block</glossterm>
+		<acronym>SMB</acronym>
+		<glossdef><para>
+		SMB was the original name of the protocol spoken by Samba. It was invented in the 1980s
+		by IBM and adopted and extended further by Microsoft. Microsoft renamed the protocol to
+		CIFS during the Internet hype in the 1990s.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>The Simple and Protected GSS-API Negotiation</glossterm>
+                <acronym>SPNEGO</acronym>
+                <glossdef><para>
+		The purpose of SPNEGO is to allow a client and server to negotiate a security mechanism for
+		authentication. The protocol is specified in RFC2478 and uses tokens as built via ASN.1 DER.
+		DER refers to Distinguished Encoding Rules. These are a set of common rules for creating
+		binary encodings in a platform-independent manner. Samba has support for SPNEGO.
+                </para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>The Official Samba-3 HOWTO and Reference Guide, Second Edition</glossterm>
+		<acronym>TOSHARG2</acronym>
+		<glossdef><para>
+		This book makes repeated reference to <quote>The Official Samba-3 HOWTO and Reference Guide, Second
+		Edition</quote> by John H. Terpstra and Jelmer R. Vernooij. This publication is available from
+		Amazon.com. Publisher: Prentice Hall PTR (August 2005),
+		ISBN: 013122282.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>User IDentifier</glossterm>
+		<acronym>UID</acronym>
+		<glossdef><para>
+		The UNIX system user identifier; on older systems, a 32-bit unsigned integer, and on newer systems,
+		an unsigned 64-bit integer. The UID is used in UNIX-like operating systems for all user-level access
+		control.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Universal Naming Convention</glossterm>
+		<acronym>UNC</acronym>
+		<glossdef><para>A syntax for specifying the location of network resources (such as file shares).
+		The UNC syntax was developed in the early days of MS DOS 3.x and is used internally by the SMB protocol.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Wireshark</glossterm>
+		<acronym>wireshark</acronym>
+		<glossdef><para>
+		A network analyzer, also known as a network sniffer or a protocol analyzer. Formerly known as Ethereal, Wireshark is
+		freely available for UNIX/Linux and Microsoft Windows systems from
+		<ulink url="http://www.wireshark.org">the Wireshark Web site</ulink>.
+		</para></glossdef>
+	</glossentry>
+
+</glossary>
diff --git a/docs-xml/Samba3-ByExample/SBE-inside-cover.xml b/docs-xml/Samba3-ByExample/SBE-inside-cover.xml
new file mode 100644
index 00000000000..c7608334608
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-inside-cover.xml
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<preface lang="en-US">
+<title>About the Cover Artwork</title>
+
+	<para>
+	The cover artwork of this book continues the freedom theme of the first
+	edition of <quote>Samba-3 by Example</quote>. The history of civilization
+	demonstrates the fragile nature of freedom. It can be lost in a moment,
+	and once lost, the cost of recovering liberty can be incredible. The last
+	edition cover featured Alfred the Great who liberated England from the
+	constant assault of Vikings and Norsemen. Events in England that
+	finally liberated the common people came about in small steps, but
+	the result should not be under-estimated. Today, as always, freedom and
+	liberty are seldom appreciated until they are lost. If we can not quantify
+	what is the value of freedom, we shall be little motivated to protect it.
+	</para>
+
+	<para>
+	<emphasis>Samba-3 by Example Cover Artwork:</emphasis> The British houses
+	of parliament are a symbol of the Westminster system of government. This form
+	of government permits the people to govern themselves at the lowest level, yet
+	it provides for courts of appeal that are designed to protect freedom and to
+	hold back all forces of tyranny. The clock is a pertinent symbol of the
+	importance of time and place.
+	</para>
+
+	<para>
+	The information technology industry is being challenged by the imposition of
+	new laws, hostile litigation, and the imposition of significant constraint 
+	of practice that threatens to remove the freedom to develop and deploy open 
+	source software solutions. Samba is a software solution that epitomizes freedom
+	of choice in network interoperability for Microsoft Windows clients.
+	</para>
+
+	<para>
+	I hope you will take the time needed to deploy it well, and that you may realize
+	the greatest benefits that may be obtained. You are free to use it in ways never
+	considered, but in doing so there may be some obstacles. Every obstacle that is
+	overcome adds to the freedom you can enjoy. Use Samba well, and it will serve
+	you well.
+	</para>
+
+</preface>
diff --git a/docs-xml/Samba3-ByExample/SBE-preface.xml b/docs-xml/Samba3-ByExample/SBE-preface.xml
new file mode 100644
index 00000000000..fe469b83849
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/SBE-preface.xml
@@ -0,0 +1,609 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<preface id="preface">
+  <title>Preface</title>
+
+	<para>
+	Network administrators live busy lives. We face distractions and pressures
+	that drive us to seek proven, working case scenarios that can be easily
+	implemented. Often this approach lands us in trouble. There is a 
+	saying that, geometrically speaking, the shortest distance between two 
+	points is a straight line, but practically we find that the quickest 
+	route to a stable network solution is the long way around.
+	</para>
+
+	<para>
+	This book is your means to the straight path. It provides step-by-step,
+	proven, working examples of Samba deployments.  If you want to deploy
+	Samba-3 with the least effort, or if you want to become an expert at deploying
+	Samba-3 without having to search through lots of documentation, this
+	book is the ticket to your destination.
+	</para>
+
+	<para>
+	Samba is software that can be run on a platform other than Microsoft Windows,
+	for example, UNIX, Linux, IBM System 390, OpenVMS, and other operating systems.
+	Samba uses the TCP/IP protocol that is installed on the host server. When
+	correctly configured, it allows that host to interact with a Microsoft Windows
+	client or server as if it is a Windows file and print server. This book
+	will help you to implement Windows-compatible file and print services.
+	</para>
+
+	<para>
+	The examples presented in this book are typical of various businesses and
+	reflect the problems and challenges they face. Care has been taken to preserve
+	attitudes, perceptions, practices, and demands from real network case studies.
+	The maximum benefit may be obtained from this book by working carefully through
+	each exercise. You may be in a hurry to satisfy a specific need, so feel
+	free to locate the example that most closely matches your need, copy it, and
+	innovate as much as you like. Above all, enjoy the process of learning the
+	secrets of MS Windows networking that is truly liberated by Samba.
+	</para>
+
+	<para>
+	The focus of attention in this book is Samba-3. Specific notes are made in
+	respect of how Samba may be made secure. This book does not attempt to provide
+	detailed information regarding secure operation and configuration of peripheral
+	services and applications such as OpenLDAP, DNS and DHCP, the need for which
+	can be met from other resources that are dedicated to the subject.
+	</para>
+
+  <sect1>
+	<title>Why Is This Book Necessary?</title>
+
+	<para>
+	This book is the result of observations and feedback. The feedback from
+	the Samba-HOWTO-Collection has been positive and complimentary. There
+	have been requests for far more worked examples, a
+	<quote>Samba Cookbook,</quote> and for training materials to
+	help kick-start the process of mastering Samba.
+	</para>
+
+	<para>
+	The Samba mailing lists users have asked for sample configuration files
+	that work. It is natural to question one's own ability to correctly
+	configure a complex tool such as Samba until a minimum necessary
+	knowledge level has been attained.
+	</para>
+
+	<para>
+	The Samba-HOWTO-Collection &smbmdash; as does <emphasis>The Official Samba-3 HOWTO and 
+	Reference Guide</emphasis> &smbmdash; documents Samba features and functionality in
+	a topical context.  This book takes a completely different approach. It
+	walks through Samba network configurations that are working within particular
+	environmental contexts, providing documented step-by-step implementations.
+	All example case configuration files, scripts, and other tools are provided
+	on the CD-ROM. This book is descriptive, provides detailed diagrams, and
+	makes deployment of Samba-3 a breeze.
+	</para>
+
+	<sect2>
+	<title>Samba 3.0.20 Update Edition</title>
+
+	<para>
+	The Samba 3.0.x series has been remarkably popular. At the time this book first
+	went to print samba-3.0.2 was being released. There have been significant modifications
+	and enhancements between samba-3.0.2 and samba-3.0.14 (the current release) that
+	necessitate this documentation update. This update has the specific intent to
+	refocus this book so that its guidance can be followed for samba-3.0.20
+	and beyond. Further changes are expected as Samba-3 matures further and will 
+	be reflected in future updates.
+	</para>
+
+	<para>
+	The changes shown in <link linkend="pref-new"/> are incorporated in this update.
+	</para>
+
+	<table id="pref-new">
+		<title>Samba Changes &smbmdash; 3.0.2 to 3.0.20</title>
+		<tgroup cols="2">
+			<colspec align="left"/>
+			<colspec align="justify"/>
+			<thead>
+				<row>
+					<entry align="left">
+						<para>
+						New Feature
+						</para>
+					</entry>
+					<entry align="left">
+						<para>
+						Description
+						</para>
+					</entry>
+				</row>
+			</thead>
+			<tbody>
+				<row>
+					<entry>
+						<para>
+						Winbind Case Handling
+						</para>
+					</entry>
+					<entry>
+						<para>
+						User and group names returned by <command>winbindd</command> are now converted to lower case
+						for better consistency. Samba implementations that depend on the case of information returned
+						by winbind (such as %u and %U) must now convert the dependency to expecting lower case values.
+						This affects mail spool files, home directories, valid user lines in the &smb.conf; file, etc.
+						</para>
+					</entry>
+				</row>
+				<row>
+					<entry>
+						<para>
+						Schema Changes
+						</para>
+					</entry>
+					<entry>
+						<para>
+						Addition of code to handle password aging, password uniqueness controls, bad
+						password instances at logon time, have made necessary extensions to the SambaSAM
+						schema. This change affects all sites that use LDAP and means that the directory
+						schema must be updated. 
+						</para>
+					</entry>
+				</row>
+				<row>
+					<entry>
+						<para>
+						Username Map Handling
+						</para>
+					</entry>
+					<entry>
+						<para>
+						Samba-3.0.8 redefined the behavior: Local authentication results in a username map file
+						lookup before authenticating the connection. All authentication via an external domain
+						controller will result in the use of the fully qualified name (i.e.: DOMAIN\username)
+						after the user has been successfully authenticated.
+						</para>
+					</entry>
+				</row>
+				<row>
+					<entry>
+						<para>
+						UNIX Extension Handling
+						</para>
+					</entry>
+					<entry>
+						<para>
+						Symbolically linked files and directories on the UNIX host to absolute paths will
+						now be followed. This can be turned off using <quote>wide links = No</quote> in
+						the share stanza in the &smb.conf; file. Turning off <quote>wide links</quote>
+						support will degrade server performance because each path must be checked.
+						</para>
+					</entry>
+				</row>
+				<row>
+					<entry>
+						<para>
+						Privileges Support
+						</para>
+					</entry>
+					<entry>
+						<para>
+						Versions of Samba prior to samba-3.0.11 required the use of the UNIX <constant>root</constant>
+						account from network Windows clients. The new <quote>enable privileges = Yes</quote> capability
+						means that functions such as adding machines to the domain, managing printers, etc. can now
+						be delegated to normal user accounts or to groups of users.
+						</para>
+					</entry>
+				</row>
+			</tbody>
+		</tgroup>
+	</table>
+	</sect2>
+
+  </sect1>
+
+  <sect1>
+  <title>Prerequisites</title>
+
+	<para>
+	This book is not a tutorial on UNIX or Linux administration. UNIX and Linux
+	training is best obtained from books dedicated to the subject. This book
+	assumes that you have at least the basic skill necessary to use these operating
+	systems, and that you can use a basic system editor to edit and configure files.
+	It has been written with the assumption that you have experience with Samba, 
+	have read <emphasis>The Official Samba-3 HOWTO and Reference Guide</emphasis> and
+	the Samba-HOWTO-Collection, or that you have familiarity with Microsoft Windows.
+	</para>
+
+	<para>
+	If you do not have this experience, you can follow the examples in this book but may
+	find yourself at times intimidated by assumptions made. In this situation, you
+	may need to refer to administrative guides or manuals for your operating system
+	platform to find what is the best method to achieve what the text of this book describes.
+	</para>
+
+  </sect1>
+
+  <sect1>
+	<title>Approach</title>
+
+	<para>
+	The first chapter deals with some rather thorny network analysis issues. Do not be
+	put off by this. The information you glean, even without a detailed understanding
+	of network protocol analysis, can help you understand how Windows networking functions.
+	</para>
+
+	<para>
+	Each following chapter of this book opens with the description of a networking solution
+	sought by a hypothetical site. Bob Jordan is a hypothetical decision maker
+	for an imaginary company, <constant>Abmas Biz NL</constant>. We will use the
+	non-existent domain name <constant>abmas.biz</constant>. All <emphasis>facts</emphasis> 
+	presented regarding this company are fictitious and have been drawn from a variety of real 
+	business scenarios over many years. Not one of these reveal the identify of the 
+	real-world company from which the scenario originated.
+	</para>
+
+	<para> 
+	In any case, Mr. Jordan likes to give all his staff nasty little assignments.
+	Stanley Saroka is one of his proteges; Christine Roberson is the network administrator 
+	Bob trusts. Jordan is inclined to treat other departments well because they finance 
+	Abmas IT operations.
+	</para>
+
+	<para>
+	Each chapter presents a summary of the network solution we have chosen to
+	demonstrate together with a rationale to help you to understand the
+	thought process that drove that solution. The chapter then documents in precise
+	detail all configuration files and steps that must be taken to implement the
+	example solution. Anyone wishing to gain serious value from this book will
+	do well to take note of the implications of points made, so watch out for the
+	<emphasis>this means that</emphasis> notations.
+	</para>
+
+	<para>
+	Each chapter has a set of questions and answers to help you to
+	to understand and digest key attributes of the solutions presented.
+	</para>
+
+  </sect1>
+
+  <sect1>
+	<title>Summary of Topics</title>
+
+	<para>
+	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>
+
+	<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 includes 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 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 
+		more complex networking challenge. In the first two cases, Abmas has a small 
+		simple office, and they want to replace a Windows 9x peer-to-peer network. The 
+		third example business uses Windows 2000 Professional. This must be simple, 
+		so let's see how far we can get. If successful, Abmas grows quickly and
+		soon needs to replace all servers and workstations.
+		</para>
+
+        	<para><emphasis>TechInfo</emphasis> &smbmdash; This chapter demands:
+			<itemizedlist>
+				<listitem><para>Case 1: The simplest &smb.conf; file that may
+					reasonably be used. Works with Samba-2.x also. This
+					configuration uses Share Mode security. Encrypted
+					passwords are not used, so there is no 
+					<filename>smbpasswd</filename> file.
+					</para></listitem>
+
+				<listitem><para>Case 2: Another simple &smb.conf; file that adds
+					WINS support and printing support. This case deals with
+					a special requirement that demonstrates how to deal with
+					purpose-built software that has a particular requirement
+					for certain share names and printing demands. This
+					configuration uses Share Mode security and also works with
+					Samba-2.x. Encrypted passwords are not used, so there is no
+					<filename>smbpasswd</filename> file.
+					</para></listitem>
+
+				<listitem><para>Case 3: This &smb.conf; configuration uses User Mode
+					security. The file share configuration demonstrates
+					the ability to provide master access to an administrator
+					while restricting all staff to their own work areas.
+					Encrypted passwords are used, so there is an implicit
+					<filename>smbpasswd</filename> file.
+					</para></listitem>
+			</itemizedlist>
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<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
+		small office and they want better systems to help them to grow. This is
+		your chance to really give advanced users a bit more functionality and usefulness.
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; This &smb.conf; file
+		makes use of encrypted passwords, so there is an <filename>smbpasswd</filename>
+		file. It also demonstrates use of the <parameter>valid users</parameter> and
+		<parameter>valid groups</parameter> to restrict share access. The Windows
+		clients access the server as Domain members. Mobile users log onto
+		the Domain while in the office, but use a local machine account while on the
+		road. The result is an environment that answers mobile computing user needs.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<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
+		to install and the old equipment will be retired. This time they want the
+		new network to scale and grow for at least two years. Start with a sufficient
+		system and allow room for growth. You are now implementing an Internet
+		connection and have a few reservations about user expectations.
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; This &smb.conf; file
+                makes use of encrypted passwords, and you can use a <filename>tdbsam</filename>
+                password backend. Domain logons are introduced. Applications are served from the central
+		server. Roaming profiles are mandated. Access to the server is tightened up
+		so that only domain members can access server resources. Mobile computing
+		needs still are catered to.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<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
+		need to merge a 280-user company they just acquired. It is time to build a serious
+		network. There are now three buildings on one campus and your assignment is 
+		to keep everyone working while a new network is rolled out. Oh, isn't it nice 
+		to roll out brand new clients and servers! Money is no longer tight, you get 
+		to buy and install what you ask for. You will install routers and a firewall.
+		This is exciting!
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; This &smb.conf; file
+                makes use of encrypted passwords, and a <filename>tdbsam</filename>
+		password backend is used. You are not ready to launch into LDAP yet, so you
+		accept the limitation of having one central Domain Controller with a Domain
+		Member server in two buildings on your campus. A number of clever techniques
+		are used to demonstrate some of the smart options built into Samba.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Chapter 5 &smbmdash; Making Happy Users.</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
+		things that need to be fixed. Are you up to the task? Mary says it takes her 20 minutes
+		to log onto the network and it is killing her productivity. Email is a bit <emphasis>
+		unreliable</emphasis> &smbmdash; have you been sleeping on the job? We do not discuss the
+		technology of email but when the use of mail clients breaks because of networking
+		problems, you had better get on top of it. It's time for a change.
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; This &smb.conf; file
+                makes use of encrypted passwords; a distributed <filename>ldapsam</filename>
+                password backend is used. Roaming profiles are enabled. Desktop profile controls
+		are introduced. Check out the techniques that can improve the user experience 
+		of network performance. As a special bonus, this chapter documents how to configure
+		smart downloading of printer drivers for drag-and-drop printing support. And, yes,
+		the secret of configuring CUPS is clearly documented. Go for it; this one will
+		tease you, too.
+                </para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<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.
+		There are three new networks in addition to the original three buildings at the head-office 
+		campus. The head office is in New York and you have branch offices in Washington, Los Angeles, and 
+		London. Your desktop standard is Windows XP Professional. In many ways, everything has changed
+		and yet it must remain the same. Your team is primed for another roll-out. You know there are
+		further challenges ahead.
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; Slave LDAP servers are introduced. Samba is
+		configured to use multiple LDAP backends. This is a brief chapter; it assumes that the
+		technology has been mastered and gets right down to concepts and how to deploy them.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Chapter 7 &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
+		overheads and yet get better control of the network?
+		</para>
+
+		<para>
+		This chapter has been contributed by Mark Taylor <email>mark.taylor@siriusit.co.uk</email>
+		and is based on a live site. For further information regarding this example case, 
+		please contact Mark directly.
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; It is time to consider how to add Samba servers
+		and UNIX and Linux network clients. Users who convert to Linux want to be able to log on
+		using Windows network accounts. You explore nss_ldap, pam_ldap, winbind, and a few neat
+		techniques for taking control. Are you ready for this?
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Chapter 8 &smbmdash; Updating Samba-3.</term><listitem>
+		<para>
+		This chapter is the result of repeated requests for better documentation of the steps
+		that must be followed when updating or upgrading a Samba server. It attempts to cover
+		the entire subject in broad-brush but at the same time provides detailed background
+		information that is not covered elsewhere in the Samba documentation.
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; Samba stores a lot of essential network
+		information in a large and growing collection of files. This chapter documents the
+		essentials of where those files may be located and how to find them. It also provides
+		an insight into inter-related matters that affect a Samba installation.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Chapter 9 &smbmdash; Migrating NT4 Domain to Samba-3.</term><listitem>
+		<para>
+		Another six months have passed. Abmas has acquired yet another company. You will find a
+		way to migrate all users off the old network onto the existing network without loss
+		of passwords and will effect the change-over during one weekend. May the force (and caffeine) be with
+		you, may you keep your back to the wind and may the sun shine on your face.
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; This chapter demonstrates the use of
+		the <command>net rpc migrate</command> facility using an LDAP ldapsam backend, and also
+		using a tdbsam passdb backend. Both are much-asked-for examples of NT4 Domain migration.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Chapter 10 &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.
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; The documentation provided demonstrates
+		how one site migrated from NetWare to Samba. Some alternatives tools are mentioned. These
+		could be used to provide another pathway to a successful migration.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Chapter 11 &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.
+		A network security auditor is hired by the head of the new business and files a damning 
+		report, and you must address the <emphasis>defects</emphasis> reported. You have hired new 
+		network engineers who want to replace Microsoft Active Directory with a pure Kerberos 
+		solution. How will you handle this? 
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; This chapter is your answer. Learn about
+		share access controls, proper use of UNIX/Linux file system access controls, and Windows
+		200x Access Control Lists. Follow these steps to beat the critics.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+                <term>Chapter 12 &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
+		made promises you must keep. IT costs must be reduced, you have new resistance, but you
+		will win again. This time you choose to install the Squid proxy server to validate the
+		fact that Samba is far more than just a file and print server. SPNEGO authentication 
+		support means that your Microsoft Windows clients gain transparent proxy access.
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; Samba provides the <command>ntlm_auth</command>
+		module that makes it possible for MS Windows Internet Explorer to connect via the Squid Web
+		and FTP proxy server. You will configure Samba-3 as well as Squid to deliver authenticated
+		access control using the Active Directory Domain user security credentials.
+                </para>
+                </listitem>
+                </varlistentry>
+
+		<varlistentry>
+		<term>Chapter 13 &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
+		keep the cost under control also? What can go wrong?
+		</para>
+
+		<para><emphasis>TechInfo</emphasis> &smbmdash; Hot tips that put chili into your
+		network. Avoid name resolution problems, identify potential causes of network collisions,
+		avoid Samba configuration options that will weigh the server down. MS distributed file
+		services to make your network fly and much more. This chapter contains a good deal of 
+		<quote>Did I tell you about this...?</quote> type of hints to help keep your name on the top
+		performers list.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Chapter 14 &smbmdash; Samba Support.</term><listitem>
+		<para>
+		This chapter has been added specifically to help those who are seeking professional
+		paid support for Samba. The critics of Open Source Software often assert that
+		there is no support for free software. Some critics argue that free software 
+		undermines the service that proprietary commercial software vendors depend on.
+		This chapter explains what are the support options for Samba and the fact that
+		a growing number of businesses make money by providing commercial paid-for
+		Samba support.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Chapter 15 &smbmdash; A Collection of Useful Tid-bits.</term><listitem>
+		<para>
+		Sometimes it seems that there is not a good place for certain odds and ends that
+		impact Samba deployment. Some readers would argue that everyone can be expected
+		to know this information, or at least be able to find it easily. So to avoid
+		offending a reader's sensitivities, the tid-bits have been placed in this chapter.
+		Do check out the contents, you may find something of value among the loose ends.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Chapter 16 &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>
+
+  <!-- the conventions used in this book -->
+  <xi:include href="conventions.xml" xmlns:xi="http://www.w3.org/2003/XInclude" />
+
+</preface>
+
diff --git a/docs-xml/Samba3-ByExample/conventions.xml b/docs-xml/Samba3-ByExample/conventions.xml
new file mode 100644
index 00000000000..1b3848405c0
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/conventions.xml
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+  <sect1>
+    <title>Conventions Used</title>
+
+    <para>
+    The following notation conventions are used throughout this book:
+    </para>
+
+    <itemizedlist>
+      <listitem>
+	<para>
+	TOSHARG2 is used as an abbreviation for the book, <quote>The Official Samba-3
+	HOWTO and Reference Guide, Second Edition</quote> Editors: John H. Terpstra and Jelmer R. Vernooij,
+	Publisher: Prentice Hall, ISBN: 0131882228.
+	</para>
+      </listitem>
+
+      <listitem>
+	<para>
+	S3bE2 is used as an abbreviation for the book, <quote>Samba-3 by Example, Second Edition</quote> 
+	Editors: John H. Terpstra, Publisher: Prentice Hall, ISBN: 013188221X.
+	</para>
+      </listitem>
+
+      <listitem>
+        <para>
+	Directories and filenames appear in mono-font. For example,
+        <filename>/etc/pam.conf</filename>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+	Executable names are bolded. For example, <command>smbd</command>.
+	</para>
+      </listitem>
+
+      <listitem>
+        <para>
+	Menu items and buttons appear in bold. For example, click <guibutton>Next</guibutton>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+	Selecting a menu item is indicated as:
+	<menuchoice>
+		<guimenu>Start</guimenu>
+		<guimenuitem>Control Panel</guimenuitem>
+		<guimenuitem>Administrative Tools</guimenuitem>
+		<guimenuitem>Active Directory Users and Computers</guimenuitem>
+	</menuchoice>
+       </para>
+      </listitem>
+    </itemizedlist>
+
+  </sect1>
+
diff --git a/docs-xml/Samba3-ByExample/gpl-3.0.xml b/docs-xml/Samba3-ByExample/gpl-3.0.xml
new file mode 100644
index 00000000000..559c89dc4f0
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/gpl-3.0.xml
@@ -0,0 +1,836 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+<appendix>
+  <title>
+    <acronym>GNU</acronym> General Public License version 3
+  </title>
+  <para>
+    Version 3, 29 June 2007
+  </para>
+  <para>
+    Copyright &copy; 2007 Free Software Foundation, Inc.
+    <ulink url="http://fsf.org/">http://fsf.org/</ulink>
+  </para>
+  <para>
+    Everyone is permitted to copy and distribute verbatim copies of this license
+    document, but changing it is not allowed.
+  </para>
+  <bridgehead renderas="sect1">
+    Preamble
+  </bridgehead>
+  <para>
+    The <acronym>GNU</acronym> General Public License is a free, copyleft
+    license for software and other kinds of works.
+  </para>
+  <para>
+    The licenses for most software and other practical works are designed to
+    take away your freedom to share and change the works.  By contrast, the
+    <acronym>GNU</acronym> General Public License is intended to guarantee your
+    freedom to share and change all versions of a program&mdash;to make sure it
+    remains free software for all its users.  We, the Free Software Foundation,
+    use the <acronym>GNU</acronym> General Public License for most of our
+    software; it applies also to any other work released this way by its
+    authors.  You can apply it to your programs, too.
+  </para>
+  <para>
+    When we speak of free software, we are referring to freedom, not price.  Our
+    General Public Licenses are designed to make sure that you have the freedom
+    to distribute copies of free software (and charge for them if you wish),
+    that you receive source code or can get it if you want it, that you can
+    change the software or use pieces of it in new free programs, and that you
+    know you can do these things.
+  </para>
+  <para>
+    To protect your rights, we need to prevent others from denying you these
+    rights or asking you to surrender the rights.  Therefore, you have certain
+    responsibilities if you distribute copies of the software, or if you modify
+    it: responsibilities to respect the freedom of others.
+  </para>
+  <para>
+    For example, if you distribute copies of such a program, whether gratis or
+    for a fee, you must pass on to the recipients the same freedoms that you
+    received.  You must make sure that they, too, receive or can get the source
+    code.  And you must show them these terms so they know their rights.
+  </para>
+  <para>
+    Developers that use the <acronym>GNU</acronym> <acronym>GPL</acronym>
+    protect your rights with two steps: (1) assert copyright on the software,
+    and (2) offer you this License giving you legal permission to copy,
+    distribute and/or modify it.
+  </para>
+  <para>
+    For the developers&rsquo; and authors&rsquo; protection, the
+    <acronym>GPL</acronym> clearly explains that there is no warranty for this
+    free software.  For both users&rsquo; and authors&rsquo; sake, the
+    <acronym>GPL</acronym> requires that modified versions be marked as changed,
+    so that their problems will not be attributed erroneously to authors of
+    previous versions.
+  </para>
+  <para>
+    Some devices are designed to deny users access to install or run modified
+    versions of the software inside them, although the manufacturer can do so.
+    This is fundamentally incompatible with the aim of protecting users&rsquo;
+    freedom to change the software.  The systematic pattern of such abuse occurs
+    in the area of products for individuals to use, which is precisely where it
+    is most unacceptable.  Therefore, we have designed this version of the
+    <acronym>GPL</acronym> to prohibit the practice for those products.  If such
+    problems arise substantially in other domains, we stand ready to extend this
+    provision to those domains in future versions of the <acronym>GPL</acronym>,
+    as needed to protect the freedom of users.
+  </para>
+  <para>
+    Finally, every program is threatened constantly by software patents.  States
+    should not allow patents to restrict development and use of software on
+    general-purpose computers, but in those that do, we wish to avoid the
+    special danger that patents applied to a free program could make it
+    effectively proprietary.  To prevent this, the <acronym>GPL</acronym>
+    assures that patents cannot be used to render the program non-free.
+  </para>
+  <para>
+    The precise terms and conditions for copying, distribution and modification
+    follow.
+  </para>
+  <bridgehead>
+    TERMS AND CONDITIONS
+  </bridgehead>
+  <bridgehead renderas="sect1">
+    0. Definitions.
+  </bridgehead>
+  <para>
+    &ldquo;This License&rdquo; refers to version 3 of the <acronym>GNU</acronym>
+    General Public License.
+  </para>
+  <para>
+    &ldquo;Copyright&rdquo; also means copyright-like laws that apply to other
+    kinds of works, such as semiconductor masks.
+  </para>
+  <para>
+    &ldquo;The Program&rdquo; refers to any copyrightable work licensed under
+    this License.  Each licensee is addressed as &ldquo;you&rdquo;.
+    &ldquo;Licensees&rdquo; and &ldquo;recipients&rdquo; may be individuals or
+    organizations.
+  </para>
+  <para>
+    To &ldquo;modify&rdquo; a work means to copy from or adapt all or part of
+    the work in a fashion requiring copyright permission, other than the making
+    of an exact copy.  The resulting work is called a &ldquo;modified
+    version&rdquo; of the earlier work or a work &ldquo;based on&rdquo; the
+    earlier work.
+  </para>
+  <para>
+    A &ldquo;covered work&rdquo; means either the unmodified Program or a work
+    based on the Program.
+  </para>
+  <para>
+    To &ldquo;propagate&rdquo; a work means to do anything with it that, without
+    permission, would make you directly or secondarily liable for infringement
+    under applicable copyright law, except executing it on a computer or
+    modifying a private copy.  Propagation includes copying, distribution (with
+    or without modification), making available to the public, and in some
+    countries other activities as well.
+  </para>
+  <para>
+    To &ldquo;convey&rdquo; a work means any kind of propagation that enables
+    other parties to make or receive copies.  Mere interaction with a user
+    through a computer network, with no transfer of a copy, is not conveying.
+  </para>
+  <para>
+    An interactive user interface displays &ldquo;Appropriate Legal
+    Notices&rdquo; to the extent that it includes a convenient and prominently
+    visible feature that (1) displays an appropriate copyright notice, and (2)
+    tells the user that there is no warranty for the work (except to the extent
+    that warranties are provided), that licensees may convey the work under this
+    License, and how to view a copy of this License.  If the interface presents
+    a list of user commands or options, such as a menu, a prominent item in the
+    list meets this criterion.
+  </para>
+  <bridgehead renderas="sect1">
+    1. Source Code.
+  </bridgehead>
+  <para>
+    The &ldquo;source code&rdquo; for a work means the preferred form of the
+    work for making modifications to it.  &ldquo;Object code&rdquo; means any
+    non-source form of a work.
+  </para>
+  <para>
+    A &ldquo;Standard Interface&rdquo; means an interface that either is an
+    official standard defined by a recognized standards body, or, in the case of
+    interfaces specified for a particular programming language, one that is
+    widely used among developers working in that language.
+  </para>
+  <para>
+    The &ldquo;System Libraries&rdquo; of an executable work include anything,
+    other than the work as a whole, that (a) is included in the normal form of
+    packaging a Major Component, but which is not part of that Major Component,
+    and (b) serves only to enable use of the work with that Major Component, or
+    to implement a Standard Interface for which an implementation is available
+    to the public in source code form.  A &ldquo;Major Component&rdquo;, in this
+    context, means a major essential component (kernel, window system, and so
+    on) of the specific operating system (if any) on which the executable work
+    runs, or a compiler used to produce the work, or an object code interpreter
+    used to run it.
+  </para>
+  <para>
+    The &ldquo;Corresponding Source&rdquo; for a work in object code form means
+    all the source code needed to generate, install, and (for an executable
+    work) run the object code and to modify the work, including scripts to
+    control those activities.  However, it does not include the work&rsquo;s
+    System Libraries, or general-purpose tools or generally available free
+    programs which are used unmodified in performing those activities but which
+    are not part of the work.  For example, Corresponding Source includes
+    interface definition files associated with source files for the work, and
+    the source code for shared libraries and dynamically linked subprograms that
+    the work is specifically designed to require, such as by intimate data
+    communication or control flow between those subprograms and other parts of
+    the work.
+  </para>
+  <para>
+    The Corresponding Source need not include anything that users can regenerate
+    automatically from other parts of the Corresponding Source.
+  </para>
+  <para>
+    The Corresponding Source for a work in source code form is that same work.
+  </para>
+  <bridgehead renderas="sect1">
+    2. Basic Permissions.
+  </bridgehead>
+  <para>
+    All rights granted under this License are granted for the term of copyright
+    on the Program, and are irrevocable provided the stated conditions are met.
+    This License explicitly affirms your unlimited permission to run the
+    unmodified Program.  The output from running a covered work is covered by
+    this License only if the output, given its content, constitutes a covered
+    work.  This License acknowledges your rights of fair use or other
+    equivalent, as provided by copyright law.
+  </para>
+  <para>
+    You may make, run and propagate covered works that you do not convey,
+    without conditions so long as your license otherwise remains in force.  You
+    may convey covered works to others for the sole purpose of having them make
+    modifications exclusively for you, or provide you with facilities for
+    running those works, provided that you comply with the terms of this License
+    in conveying all material for which you do not control copyright.  Those
+    thus making or running the covered works for you must do so exclusively on
+    your behalf, under your direction and control, on terms that prohibit them
+    from making any copies of your copyrighted material outside their
+    relationship with you.
+  </para>
+  <para>
+    Conveying under any other circumstances is permitted solely under the
+    conditions stated below.  Sublicensing is not allowed; section 10 makes it
+    unnecessary.
+  </para>
+  <bridgehead renderas="sect1">
+    3. Protecting Users&rsquo; Legal Rights From Anti-Circumvention Law.
+  </bridgehead>
+  <para>
+    No covered work shall be deemed part of an effective technological measure
+    under any applicable law fulfilling obligations under article 11 of the WIPO
+    copyright treaty adopted on 20 December 1996, or similar laws prohibiting or
+    restricting circumvention of such measures.
+  </para>
+  <para>
+    When you convey a covered work, you waive any legal power to forbid
+    circumvention of technological measures to the extent such circumvention is
+    effected by exercising rights under this License with respect to the covered
+    work, and you disclaim any intention to limit operation or modification of
+    the work as a means of enforcing, against the work&rsquo;s users, your or
+    third parties&rsquo; legal rights to forbid circumvention of technological
+    measures.
+  </para>
+  <bridgehead renderas="sect1">
+    4. Conveying Verbatim Copies.
+  </bridgehead>
+  <para>
+    You may convey verbatim copies of the Program&rsquo;s source code as you
+    receive it, in any medium, provided that you conspicuously and appropriately
+    publish on each copy an appropriate copyright notice; keep intact all
+    notices stating that this License and any non-permissive terms added in
+    accord with section 7 apply to the code; keep intact all notices of the
+    absence of any warranty; and give all recipients a copy of this License
+    along with the Program.
+  </para>
+  <para>
+    You may charge any price or no price for each copy that you convey, and you
+    may offer support or warranty protection for a fee.
+  </para>
+  <bridgehead renderas="sect1">
+    5. Conveying Modified Source Versions.
+  </bridgehead>
+  <para>
+    You may convey a work based on the Program, or the modifications to produce
+    it from the Program, in the form of source code under the terms of section
+    4, provided that you also meet all of these conditions:
+  </para>
+  <orderedlist numeration="loweralpha">
+    <listitem>
+      <para>
+        The work must carry prominent notices stating that you modified it, and
+        giving a relevant date.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The work must carry prominent notices stating that it is released under
+        this License and any conditions added under section 7.  This requirement
+        modifies the requirement in section 4 to &ldquo;keep intact all
+        notices&rdquo;.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        You must license the entire work, as a whole, under this License to
+        anyone who comes into possession of a copy.  This License will therefore
+        apply, along with any applicable section 7 additional terms, to the
+        whole of the work, and all its parts, regardless of how they are
+        packaged.  This License gives no permission to license the work in any
+        other way, but it does not invalidate such permission if you have
+        separately received it.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        If the work has interactive user interfaces, each must display
+        Appropriate Legal Notices; however, if the Program has interactive
+        interfaces that do not display Appropriate Legal Notices, your work need
+        not make them do so.
+      </para>
+    </listitem>
+  </orderedlist>
+  <para>
+    A compilation of a covered work with other separate and independent works,
+    which are not by their nature extensions of the covered work, and which are
+    not combined with it such as to form a larger program, in or on a volume of
+    a storage or distribution medium, is called an &ldquo;aggregate&rdquo; if
+    the compilation and its resulting copyright are not used to limit the access
+    or legal rights of the compilation&rsquo;s users beyond what the individual works
+    permit.  Inclusion of a covered work in an aggregate does not cause
+    this License to apply to the other parts of the aggregate.
+  </para>
+  <bridgehead renderas="sect1">
+    6. Conveying Non-Source Forms.
+  </bridgehead>
+  <para>
+    You may convey a covered work in object code form under the terms of
+    sections 4 and 5, provided that you also convey the machine-readable
+    Corresponding Source under the terms of this License, in one of these ways:
+  </para>
+  <orderedlist numeration="loweralpha">
+    <listitem>
+      <para>
+        Convey the object code in, or embodied in, a physical product (including
+        a physical distribution medium), accompanied by the Corresponding Source
+        fixed on a durable physical medium customarily used for software
+        interchange.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey the object code in, or embodied in, a physical product (including
+        a physical distribution medium), accompanied by a written offer, valid
+        for at least three years and valid for as long as you offer spare parts
+        or customer support for that product model, to give anyone who possesses
+        the object code either (1) a copy of the Corresponding Source for all
+        the software in the product that is covered by this License, on a
+        durable physical medium customarily used for software interchange, for a
+        price no more than your reasonable cost of physically performing this
+        conveying of source, or (2) access to copy the Corresponding Source from
+        a network server at no charge.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey individual copies of the object code with a copy of the written
+        offer to provide the Corresponding Source.  This alternative is allowed
+        only occasionally and noncommercially, and only if you received the
+        object code with such an offer, in accord with subsection 6b.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey the object code by offering access from a designated place
+        (gratis or for a charge), and offer equivalent access to the
+        Corresponding Source in the same way through the same place at no
+        further charge.  You need not require recipients to copy the
+        Corresponding Source along with the object code.  If the place to copy
+        the object code is a network server, the Corresponding Source may be on
+        a different server (operated by you or a third party) that supports
+        equivalent copying facilities, provided you maintain clear directions
+        next to the object code saying where to find the Corresponding Source.
+        Regardless of what server hosts the Corresponding Source, you remain
+        obligated to ensure that it is available for as long as needed to
+        satisfy these requirements.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey the object code using peer-to-peer transmission, provided you
+        inform other peers where the object code and Corresponding Source of the
+        work are being offered to the general public at no charge under
+        subsection 6d.
+      </para>
+    </listitem>
+  </orderedlist>
+  <para>
+    A separable portion of the object code, whose source code is excluded from
+    the Corresponding Source as a System Library, need not be included in
+    conveying the object code work.
+  </para>
+  <para>
+    A &ldquo;User Product&rdquo; is either (1) a &ldquo;consumer product&rdquo;,
+    which means any tangible personal property which is normally used for
+    personal, family, or household purposes, or (2) anything designed or sold
+    for incorporation into a dwelling.  In determining whether a product is a
+    consumer product, doubtful cases shall be resolved in favor of coverage.
+    For a particular product received by a particular user, &ldquo;normally
+    used&rdquo; refers to a typical or common use of that class of product,
+    regardless of the status of the particular user or of the way in which the
+    particular user actually uses, or expects or is expected to use, the
+    product.  A product is a consumer product regardless of whether the product
+    has substantial commercial, industrial or non-consumer uses, unless such
+    uses represent the only significant mode of use of the product.
+  </para>
+  <para>
+    &ldquo;Installation Information&rdquo; for a User Product means any methods,
+    procedures, authorization keys, or other information required to install and
+    execute modified versions of a covered work in that User Product from a
+    modified version of its Corresponding Source.  The information must suffice
+    to ensure that the continued functioning of the modified object code is in
+    no case prevented or interfered with solely because modification has been
+    made.
+  </para>
+  <para>
+    If you convey an object code work under this section in, or with, or
+    specifically for use in, a User Product, and the conveying occurs as part of
+    a transaction in which the right of possession and use of the User Product
+    is transferred to the recipient in perpetuity or for a fixed term
+    (regardless of how the transaction is characterized), the Corresponding
+    Source conveyed under this section must be accompanied by the Installation
+    Information.  But this requirement does not apply if neither you nor any
+    third party retains the ability to install modified object code on the User
+    Product (for example, the work has been installed in
+    <acronym>ROM</acronym>).
+  </para>
+  <para>
+    The requirement to provide Installation Information does not include a
+    requirement to continue to provide support service, warranty, or updates for
+    a work that has been modified or installed by the recipient, or for the User
+    Product in which it has been modified or installed.  Access to a network may
+    be denied when the modification itself materially and adversely affects the
+    operation of the network or violates the rules and protocols for
+    communication across the network.
+  </para>
+  <para>
+    Corresponding Source conveyed, and Installation Information provided, in
+    accord with this section must be in a format that is publicly documented
+    (and with an implementation available to the public in source code form),
+    and must require no special password or key for unpacking, reading or
+    copying.
+  </para>
+   <bridgehead renderas="sect1">
+     7. Additional Terms.
+   </bridgehead>
+   <para>
+     &ldquo;Additional permissions&rdquo; are terms that supplement the terms of
+     this License by making exceptions from one or more of its conditions.
+     Additional permissions that are applicable to the entire Program shall be
+     treated as though they were included in this License, to the extent that
+     they are valid under applicable law.  If additional permissions apply only
+     to part of the Program, that part may be used separately under those
+     permissions, but the entire Program remains governed by this License
+     without regard to the additional permissions.
+   </para>
+   <para>
+     When you convey a copy of a covered work, you may at your option remove any
+     additional permissions from that copy, or from any part of it.  (Additional
+     permissions may be written to require their own removal in certain cases
+     when you modify the work.)  You may place additional permissions on
+     material, added by you to a covered work, for which you have or can give
+     appropriate copyright permission.
+   </para>
+   <para>
+     Notwithstanding any other provision of this License, for material you add
+     to a covered work, you may (if authorized by the copyright holders of that
+     material) supplement the terms of this License with terms:
+   </para>
+   <orderedlist numeration="loweralpha">
+     <listitem>
+       <para>
+         Disclaiming warranty or limiting liability differently from the terms
+         of sections 15 and 16 of this License; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Requiring preservation of specified reasonable legal notices or author
+         attributions in that material or in the Appropriate Legal Notices
+         displayed by works containing it; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Prohibiting misrepresentation of the origin of that material, or
+         requiring that modified versions of such material be marked in
+         reasonable ways as different from the original version; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Limiting the use for publicity purposes of names of licensors or
+         authors of the material; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Declining to grant rights under trademark law for use of some trade
+         names, trademarks, or service marks; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Requiring indemnification of licensors and authors of that material by
+         anyone who conveys the material (or modified versions of it) with
+         contractual assumptions of liability to the recipient, for any
+         liability that these contractual assumptions directly impose on those
+         licensors and authors.
+       </para>
+     </listitem>
+   </orderedlist>
+   <para>
+     All other non-permissive additional terms are considered &ldquo;further
+     restrictions&rdquo; within the meaning of section 10.  If the Program as
+     you received it, or any part of it, contains a notice stating that it is
+     governed by this License along with a term that is a further restriction,
+     you may remove that term.  If a license document contains a further
+     restriction but permits relicensing or conveying under this License, you
+     may add to a covered work material governed by the terms of that license
+     document, provided that the further restriction does not survive such
+     relicensing or conveying.
+   </para>
+   <para>
+     If you add terms to a covered work in accord with this section, you must
+     place, in the relevant source files, a statement of the additional terms
+     that apply to those files, or a notice indicating where to find the
+     applicable terms.
+   </para>
+   <para>
+     Additional terms, permissive or non-permissive, may be stated in the form
+     of a separately written license, or stated as exceptions; the above
+     requirements apply either way.
+   </para>
+   <bridgehead renderas="sect1">
+     8. Termination.
+   </bridgehead>
+   <para>
+     You may not propagate or modify a covered work except as expressly provided
+     under this License.  Any attempt otherwise to propagate or modify it is
+     void, and will automatically terminate your rights under this License
+     (including any patent licenses granted under the third paragraph of section
+     11).
+   </para>
+   <para>
+     However, if you cease all violation of this License, then your license from
+     a particular copyright holder is reinstated (a) provisionally, unless and
+     until the copyright holder explicitly and finally terminates your license,
+     and (b) permanently, if the copyright holder fails to notify you of the
+     violation by some reasonable means prior to 60 days after the cessation.
+   </para>
+   <para>
+     Moreover, your license from a particular copyright holder is reinstated
+     permanently if the copyright holder notifies you of the violation by some
+     reasonable means, this is the first time you have received notice of
+     violation of this License (for any work) from that copyright holder, and
+     you cure the violation prior to 30 days after your receipt of the notice.
+   </para>
+   <para>
+     Termination of your rights under this section does not terminate the
+     licenses of parties who have received copies or rights from you under this
+     License.  If your rights have been terminated and not permanently
+     reinstated, you do not qualify to receive new licenses for the same
+     material under section 10.
+   </para>
+   <bridgehead renderas="sect1">
+     9. Acceptance Not Required for Having Copies.
+   </bridgehead>
+   <para>
+     You are not required to accept this License in order to receive or run a
+     copy of the Program.  Ancillary propagation of a covered work occurring
+     solely as a consequence of using peer-to-peer transmission to receive a
+     copy likewise does not require acceptance.  However, nothing other than
+     this License grants you permission to propagate or modify any covered work.
+     These actions infringe copyright if you do not accept this License.
+     Therefore, by modifying or propagating a covered work, you indicate your
+     acceptance of this License to do so.
+   </para>
+   <bridgehead renderas="sect1">
+     10. Automatic Licensing of Downstream Recipients.
+   </bridgehead>
+   <para>
+     Each time you convey a covered work, the recipient automatically receives a
+     license from the original licensors, to run, modify and propagate that
+     work, subject to this License.  You are not responsible for enforcing
+     compliance by third parties with this License.
+   </para>
+   <para>
+     An &ldquo;entity transaction&rdquo; is a transaction transferring control
+     of an organization, or substantially all assets of one, or subdividing an
+     organization, or merging organizations.  If propagation of a covered work
+     results from an entity transaction, each party to that transaction who
+     receives a copy of the work also receives whatever licenses to the work the
+     party&rsquo;s predecessor in interest had or could give under the previous
+     paragraph, plus a right to possession of the Corresponding Source of the
+     work from the predecessor in interest, if the predecessor has it or can get
+     it with reasonable efforts.
+   </para>
+   <para>
+     You may not impose any further restrictions on the exercise of the rights
+     granted or affirmed under this License.  For example, you may not impose a
+     license fee, royalty, or other charge for exercise of rights granted under
+     this License, and you may not initiate litigation (including a cross-claim
+     or counterclaim in a lawsuit) alleging that any patent claim is infringed
+     by making, using, selling, offering for sale, or importing the Program or
+     any portion of it.
+   </para>
+  <bridgehead renderas="sect1">
+    11. Patents.
+  </bridgehead>
+  <para>
+    A &ldquo;contributor&rdquo; is a copyright holder who authorizes use under
+    this License of the Program or a work on which the Program is based.  The
+    work thus licensed is called the contributor&rsquo;s &ldquo;contributor
+    version&rdquo;.
+  </para>
+  <para>
+    A contributor&rsquo;s &ldquo;essential patent claims&rdquo; are all patent
+    claims owned or controlled by the contributor, whether already acquired or
+    hereafter acquired, that would be infringed by some manner, permitted by
+    this License, of making, using, or selling its contributor version, but do
+    not include claims that would be infringed only as a consequence of further
+    modification of the contributor version.  For purposes of this definition,
+    &ldquo;control&rdquo; includes the right to grant patent sublicenses in a
+    manner consistent with the requirements of this License.
+  </para>
+  <para>
+    Each contributor grants you a non-exclusive, worldwide, royalty-free patent
+    license under the contributor&rsquo;s essential patent claims, to make, use,
+    sell, offer for sale, import and otherwise run, modify and propagate the
+    contents of its contributor version.
+  </para>
+  <para>
+    In the following three paragraphs, a &ldquo;patent license&rdquo; is any
+    express agreement or commitment, however denominated, not to enforce a
+    patent (such as an express permission to practice a patent or covenant not
+    to sue for patent infringement).  To &ldquo;grant&rdquo; such a patent
+    license to a party means to make such an agreement or commitment not to
+    enforce a patent against the party.
+  </para>
+  <para>
+    If you convey a covered work, knowingly relying on a patent license, and the
+    Corresponding Source of the work is not available for anyone to copy, free
+    of charge and under the terms of this License, through a publicly available
+    network server or other readily accessible means, then you must either (1)
+    cause the Corresponding Source to be so available, or (2) arrange to deprive
+    yourself of the benefit of the patent license for this particular work, or
+    (3) arrange, in a manner consistent with the requirements of this License,
+    to extend the patent license to downstream recipients.  &ldquo;Knowingly
+    relying&rdquo; means you have actual knowledge that, but for the patent
+    license, your conveying the covered work in a country, or your
+    recipient&rsquo;s use of the covered work in a country, would infringe one
+    or more identifiable patents in that country that you have reason to believe
+    are valid.
+  </para>
+  <para>
+    If, pursuant to or in connection with a single transaction or arrangement,
+    you convey, or propagate by procuring conveyance of, a covered work, and
+    grant a patent license to some of the parties receiving the covered work
+    authorizing them to use, propagate, modify or convey a specific copy of the
+    covered work, then the patent license you grant is automatically extended to
+    all recipients of the covered work and works based on it.
+  </para>
+  <para>
+    A patent license is &ldquo;discriminatory&rdquo; if it does not include
+    within the scope of its coverage, prohibits the exercise of, or is
+    conditioned on the non-exercise of one or more of the rights that are
+    specifically granted under this License.  You may not convey a covered work
+    if you are a party to an arrangement with a third party that is in the
+    business of distributing software, under which you make payment to the third
+    party based on the extent of your activity of conveying the work, and under
+    which the third party grants, to any of the parties who would receive the
+    covered work from you, a discriminatory patent license (a) in connection
+    with copies of the covered work conveyed by you (or copies made from those
+    copies), or (b) primarily for and in connection with specific products or
+    compilations that contain the covered work, unless you entered into that
+    arrangement, or that patent license was granted, prior to 28 March 2007.
+  </para>
+  <para>
+    Nothing in this License shall be construed as excluding or limiting any
+    implied license or other defenses to infringement that may otherwise be
+    available to you under applicable patent law.
+  </para>
+  <bridgehead renderas="sect1">
+    12. No Surrender of Others&rsquo; Freedom.
+  </bridgehead>
+  <para>
+    If conditions are imposed on you (whether by court order, agreement or
+    otherwise) that contradict the conditions of this License, they do not
+    excuse you from the conditions of this License.  If you cannot convey a
+    covered work so as to satisfy simultaneously your obligations under this
+    License and any other pertinent obligations, then as a consequence you may
+    not convey it at all.  For example, if you agree to terms that obligate you
+    to collect a royalty for further conveying from those to whom you convey the
+    Program, the only way you could satisfy both those terms and this License
+    would be to refrain entirely from conveying the Program.
+  </para>
+  <bridgehead renderas="sect1">
+    13. Use with the <acronym>GNU</acronym> Affero General Public License.
+  </bridgehead>
+  <para>
+    Notwithstanding any other provision of this License, you have permission to
+    link or combine any covered work with a work licensed under version 3 of the
+    <acronym>GNU</acronym> Affero General Public License into a single combined
+    work, and to convey the resulting work.  The terms of this License will
+    continue to apply to the part which is the covered work, but the special
+    requirements of the <acronym>GNU</acronym> Affero General Public License,
+    section 13, concerning interaction through a network will apply to the
+    combination as such.
+  </para>
+  <bridgehead renderas="sect1">
+    14. Revised Versions of this License.
+  </bridgehead>
+  <para>
+    The Free Software Foundation may publish revised and/or new versions of the
+    <acronym>GNU</acronym> General Public License from time to time.  Such new
+    versions will be similar in spirit to the present version, but may differ in
+    detail to address new problems or concerns.
+  </para>
+  <para>
+    Each version is given a distinguishing version number.  If the Program
+    specifies that a certain numbered version of the <acronym>GNU</acronym>
+    General Public License &ldquo;or any later version&rdquo; applies to it, you
+    have the option of following the terms and conditions either of that
+    numbered version or of any later version published by the Free Software
+    Foundation.  If the Program does not specify a version number of the
+    <acronym>GNU</acronym> General Public License, you may choose any version
+    ever published by the Free Software Foundation.
+  </para>
+  <para>
+    If the Program specifies that a proxy can decide which future versions of
+    the <acronym>GNU</acronym> General Public License can be used, that
+    proxy&rsquo;s public statement of acceptance of a version permanently
+    authorizes you to choose that version for the Program.
+  </para>
+  <para>
+    Later license versions may give you additional or different permissions.
+    However, no additional obligations are imposed on any author or copyright
+    holder as a result of your choosing to follow a later version.
+  </para>
+  <bridgehead renderas="sect1">
+    15. Disclaimer of Warranty.
+  </bridgehead>
+  <para>
+    THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
+    LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+    OTHER PARTIES PROVIDE THE PROGRAM &ldquo;AS IS&rdquo; WITHOUT WARRANTY OF
+    ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+    THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
+    YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
+    NECESSARY SERVICING, REPAIR OR CORRECTION.
+  </para>
+  <bridgehead renderas="sect1">
+    16. Limitation of Liability.
+  </bridgehead>
+  <para>
+    IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
+    ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
+    PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+    GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE
+    OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA
+    OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+    PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+    EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+    SUCH DAMAGES.
+  </para>
+  <bridgehead renderas="sect1">
+    17. Interpretation of Sections 15 and 16.
+  </bridgehead>
+  <para>
+    If the disclaimer of warranty and limitation of liability provided above
+    cannot be given local legal effect according to their terms, reviewing
+    courts shall apply local law that most closely approximates an absolute
+    waiver of all civil liability in connection with the Program, unless a
+    warranty or assumption of liability accompanies a copy of the Program in
+    return for a fee.
+  </para>
+  <bridgehead>
+    END OF TERMS AND CONDITIONS
+  </bridgehead>
+  <bridgehead renderas="sect1">
+    How to Apply These Terms to Your New Programs
+  </bridgehead>
+  <para>
+    If you develop a new program, and you want it to be of the greatest possible
+    use to the public, the best way to achieve this is to make it free software
+    which everyone can redistribute and change under these terms.
+  </para>
+  <para>
+    To do so, attach the following notices to the program.  It is safest to
+    attach them to the start of each source file to most effectively state the
+    exclusion of warranty; and each file should have at least the
+    &ldquo;copyright&rdquo; line and a pointer to where the full notice is
+    found.
+  </para>
+  <screen>
+<replaceable>one line to give the program&rsquo;s name and a brief idea of what it does.</replaceable>
+Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the <acronym>GNU</acronym> General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+<acronym>GNU</acronym> General Public License for more details.
+
+You should have received a copy of the <acronym>GNU</acronym> General Public License
+along with this program.  If not, see <ulink url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
+  </screen>
+  <para>
+    Also add information on how to contact you by electronic and paper mail.
+  </para>
+  <para>
+    If the program does terminal interaction, make it output a short notice like
+    this when it starts in an interactive mode:
+  </para>
+  <screen>
+<replaceable>program</replaceable> Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
+This program comes with ABSOLUTELY NO WARRANTY; for details type &lsquo;<literal>show w</literal>&rsquo;.
+This is free software, and you are welcome to redistribute it
+under certain conditions; type &lsquo;<literal>show c</literal>&rsquo; for details.
+  </screen>
+  <para>
+    The hypothetical commands &lsquo;<literal>show w</literal>&rsquo; and
+    &lsquo;<literal>show c</literal>&rsquo; should show the appropriate parts of
+    the General Public License.  Of course, your program&rsquo;s commands might be
+    different; for a GUI interface, you would use an &ldquo;about box&rdquo;.
+  </para>
+  <para>
+    You should also get your employer (if you work as a programmer) or school,
+    if any, to sign a &ldquo;copyright disclaimer&rdquo; for the program, if
+    necessary.  For more information on this, and how to apply and follow the
+    <acronym>GNU</acronym> <acronym>GPL</acronym>, see <ulink
+    url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
+  </para>
+  <para>
+    The <acronym>GNU</acronym> General Public License does not permit
+    incorporating your program into proprietary programs.  If your program is a
+    subroutine library, you may consider it more useful to permit linking
+    proprietary applications with the library.  If this is what you want to do,
+    use the <acronym>GNU</acronym> Lesser General Public License instead of this
+    License.  But first, please read <ulink
+    url="http://www.gnu.org/philosophy/why-not-lgpl.html">http://www.gnu.org/philosophy/why-not-lgpl.html</ulink>.
+  </para>
+</appendix>
diff --git a/docs-xml/Samba3-ByExample/gpl.xml b/docs-xml/Samba3-ByExample/gpl.xml
new file mode 100644
index 00000000000..8f3b8b40e43
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/gpl.xml
@@ -0,0 +1,425 @@
+<?xml version="1.0"?>
+<!DOCTYPE appendix PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<appendix>
+  <appendixinfo>
+    <title>GNU General Public License</title>
+    <pubdate>Version 2, June 1991</pubdate>
+    <copyright>
+      <year>1989, 1991</year>
+      <holder>Free Software Foundation, Inc.</holder>
+    </copyright>
+    <legalnotice>
+      <para>	
+	<address>Free Software Foundation, Inc. 
+	  <street>59 Temple Place, Suite 330</street>, 
+	  <city>Boston</city>, 
+	  <state>MA</state> 
+	  <postcode>02111-1307</postcode>
+	  <country>USA</country>
+	</address>.
+      </para>
+      <para>	Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+      </para>
+    </legalnotice>
+    <releaseinfo>      Version 2, June 1991</releaseinfo>
+  </appendixinfo>
+  <title>GNU General Public License</title>
+  <sect1>
+    <title>Preamble</title>
+    <para>      The licenses for most software are designed to take away your 
+      freedom to share and change it. By contrast, the GNU General Public License is 
+      intended to guarantee your freedom to share and change 
+      free software - to make sure the software is free for all its users. 
+      This General Public License applies to most of the Free Software 
+      Foundation's software and to any other program whose authors commit 
+      to using it. (Some other Free Software Foundation software is covered 
+      by the GNU Library General Public License instead.) You can apply it 
+      to your programs, too.
+    </para>
+    <para>      When we speak of free software, we are referring to freedom, not price. 
+      Our General Public Licenses are designed to make sure that you have the 
+      freedom to distribute copies of free software (and charge for this 
+      service if you wish), that you receive source code or can get it if you 
+      want it, that you can change the software or use pieces of it in new free 
+      programs; and that you know you can do these things.
+    </para>
+    <para>      To protect your rights, we need to make restrictions that forbid anyone 
+      to deny you these rights or to ask you to surrender the rights. These 
+      restrictions translate to certain responsibilities for you if you distribute 
+      copies of the software, or if you modify it.
+    </para>
+    <para>      For example, if you distribute copies of such a program, whether gratis or 
+      for a fee, you must give the recipients all the rights that you have. You 
+      must make sure that they, too, receive or can get the source code. And you 
+      must show them these terms so they know their rights.
+    </para>
+    <para>      We protect your rights with two steps:
+      <orderedlist>
+	<listitem>
+	  <para>	    copyright the software, and
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>	    offer you this license which gives you legal permission to copy, 
+	    distribute and/or modify the software.
+	  </para>
+	</listitem>
+      </orderedlist>
+    </para>
+    <para>      Also, for each author's protection and ours, we want to make certain that 
+      everyone understands that there is no warranty for this free software. If 
+      the software is modified by someone else and passed on, we want its 
+      recipients to know that what they have is not the original, so that any 
+      problems introduced by others will not reflect on the original authors' 
+      reputations.
+    </para>
+    <para>      Finally, any free program is threatened constantly by software patents. 
+      We wish to avoid the danger that redistributors of a free program will 
+      individually obtain patent licenses, in effect making the program 
+      proprietary. To prevent this, we have made it clear that any patent must be 
+      licensed for everyone's free use or not licensed at all.
+    </para>
+    <para>      The precise terms and conditions for copying, distribution and modification 
+      follow.
+    </para>
+  </sect1>
+  <sect1>
+    <title>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</title>
+    <sect2>
+      <title>Section 0</title>
+      <para>	This License applies to any program or other work which contains a notice 
+	placed by the copyright holder saying it may be distributed under the terms 
+	of this General Public License. The "Program", below, refers to any such 
+	program or work, and a 
+	<quote>work based on the Program
+	</quote> means either 
+	the Program or any derivative work under copyright law: that is to say, a 
+	work containing the Program or a portion of it, either verbatim or with 
+	modifications and/or translated into another language. (Hereinafter, translation 
+	is included without limitation in the term 
+	<quote>modification
+	</quote>.) Each licensee is addressed as <quote>you</quote>.
+      </para>
+      <para>	Activities other than copying, distribution and modification are not covered by 
+	this License; they are outside its scope. The act of running the Program is not 
+	restricted, and the output from the Program is covered only if its contents 
+	constitute a work based on the Program (independent of having been made by running 
+	the Program). Whether that is true depends on what the Program does.
+      </para>
+    </sect2>
+    <sect2 id="sect1">
+      <title>Section 1</title>
+      <para>	You may copy and distribute verbatim copies of the Program's source code as you 
+	receive it, in any medium, provided that you conspicuously and appropriately 
+	publish on each copy an appropriate copyright notice and disclaimer of warranty; 
+	keep intact all the notices that refer to this License and to the absence of any 
+	warranty; and give any other recipients of the Program a copy of this License 
+	along with the Program.
+      </para>
+      <para>	You may charge a fee for the physical act of transferring a copy, and you may at 
+	your option offer warranty protection in exchange for a fee.
+      </para>
+    </sect2>
+    <sect2 id="sect2">
+      <title>Section 2</title>
+      <para>	You may modify your copy or copies of the Program or any portion of it, thus 
+	forming a work based on the Program, and copy and distribute such modifications 
+	or work under the terms of 
+	<link linkend="sect1">Section 1
+	</link> above, provided 
+	that you also meet all of these conditions:
+	<orderedlist>
+	  <listitem>
+	    <para>	      You must cause the modified files to carry prominent notices stating that 
+	      you changed the files and the date of any change.
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>	      You must cause any work that you distribute or publish, that in whole or 
+	      in part contains or is derived from the Program or any part thereof, to be 
+	      licensed as a whole at no charge to all third parties under the terms of 
+	      this License.
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>	      If the modified program normally reads commands interactively when run, you 
+	      must cause it, when started running for such interactive use in the most 
+	      ordinary way, to print or display an announcement including an appropriate 
+	      copyright notice and a notice that there is no warranty (or else, saying 
+	      that you provide a warranty) and that users may redistribute the program 
+	      under these conditions, and telling the user how to view a copy of this 
+	      License. 
+	      <note>
+		<title>Exception:
+		</title>
+		<para>		  If the Program itself is interactive but does not normally print such an 
+		  announcement, your work based on the Program is not required to print an 
+		  announcement.) 
+		</para>
+	      </note>
+	    </para>
+	  </listitem>
+	</orderedlist>
+      </para>
+      <para>	These requirements apply to the modified work as a whole. If identifiable sections 
+	of that work are not derived from the Program, and can be reasonably considered 
+	independent and separate works in themselves, then this License, and its terms, 
+	do not apply to those sections when you distribute them as separate works. But when 
+	you distribute the same sections as part of a whole which is a work based on the 
+	Program, the distribution of the whole must be on the terms of this License, whose 
+	permissions for other licensees extend to the entire whole, and thus to each and 
+	every part regardless of who wrote it.
+      </para>
+      <para>	Thus, it is not the intent of this section to claim rights or contest your rights 
+	to work written entirely by you; rather, the intent is to exercise the right to control 
+	the distribution of derivative or collective works based on the Program.
+      </para>
+      <para>	In addition, mere aggregation of another work not based on the Program with the Program 
+	(or with a work based on the Program) on a volume of a storage or distribution medium 
+	does not bring the other work under the scope of this License.
+      </para>
+    </sect2>
+    <sect2>
+      <title>Section 3
+      </title>
+      <para>	You may copy and distribute the Program (or a work based on it, under 
+	<link linkend="sect2">Section 2
+	</link> in object code or executable form under the terms of 
+	<link linkend="sect1">Sections 1
+	</link> and 
+	<link linkend="sect2">2
+	</link> above provided that you also do one of the following:
+	<orderedlist>
+	  <listitem>
+	    <para>	Accompany it with the complete corresponding machine-readable source code, which 
+	      must be distributed under the terms of Sections 1 and 2 above on a medium 
+	      customarily used for software interchange; or,
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>	      Accompany it with a written offer, valid for at least three years, to give any 
+	      third party, for a charge no more than your cost of physically performing source 
+	      distribution, a complete machine-readable copy of the corresponding source code, 
+	      to be distributed under the terms of Sections 1 and 2 above on a medium customarily 
+	      used for software interchange; or,
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>	      Accompany it with the information you received as to the offer to distribute 
+	      corresponding source code. (This alternative is allowed only for noncommercial 
+	      distribution and only if you received the program in object code or executable form 
+	      with such an offer, in accord with Subsection b above.)
+	    </para>
+	  </listitem>
+	</orderedlist>
+      </para>
+      <para>	The source code for a work means the preferred form of the work for making modifications 
+	to it. For an executable work, complete source code means all the source code for all modules 
+	it contains, plus any associated interface definition files, plus the scripts used to control 
+	compilation and installation of the executable. However, as a special exception, the source 
+	code distributed need not include anything that is normally distributed (in either source or 
+	binary form) with the major components (compiler, kernel, and so on) of the operating system 
+	on which the executable runs, unless that component itself accompanies the executable.
+      </para>
+      <para>	If distribution of executable or object code is made by offering access to copy from a 
+	designated place, then offering equivalent access to copy the source code from the same place 
+	counts as distribution of the source code, even though third parties are not compelled to 
+	copy the source along with the object code.
+      </para>
+    </sect2>
+    <sect2>
+      <title>Section 4
+      </title>
+      <para>	You may not copy, modify, sublicense, or distribute the Program except as expressly provided 
+	under this License. Any attempt otherwise to copy, modify, sublicense or distribute the 
+	Program is void, and will automatically terminate your rights under this License. However, 
+	parties who have received copies, or rights, from you under this License will not have their 
+	licenses terminated so long as such parties remain in full compliance.
+      </para>
+    </sect2>
+    <sect2>
+      <title>Section 5
+      </title>
+      <para>	You are not required to accept this License, since you have not signed it. However, nothing 
+	else grants you permission to modify or distribute the Program or its derivative works. 
+	These actions are prohibited by law if you do not accept this License. Therefore, by modifying 
+	or distributing the Program (or any work based on the Program), you indicate your acceptance 
+	of this License to do so, and all its terms and conditions for copying, distributing or 
+	modifying the Program or works based on it.
+      </para>
+    </sect2>
+    <sect2>
+      <title>Section 6
+      </title>
+      <para>	Each time you redistribute the Program (or any work based on the Program), the recipient 
+	automatically receives a license from the original licensor to copy, distribute or modify 
+	the Program subject to these terms and conditions. You may not impose any further restrictions 
+	on the recipients' exercise of the rights granted herein. You are not responsible for enforcing 
+	compliance by third parties to this License.
+      </para>
+    </sect2>
+    <sect2>
+      <title>Section 7
+      </title>
+      <para>	If, as a consequence of a court judgment or allegation of patent infringement or for any other 
+	reason (not limited to patent issues), conditions are imposed on you (whether by court order, 
+	agreement or otherwise) that contradict the conditions of this License, they do not excuse you 
+	from the conditions of this License. If you cannot distribute so as to satisfy simultaneously 
+	your obligations under this License and any other pertinent obligations, then as a consequence 
+	you may not distribute the Program at all. For example, if a patent license would not permit 
+	royalty-free redistribution of the Program by all those who receive copies directly or 
+	indirectly through you, then the only way you could satisfy both it and this License would be 
+	to refrain entirely from distribution of the Program.
+      </para>
+      <para>	If any portion of this section is held invalid or unenforceable under any particular circumstance, 
+	the balance of the section is intended to apply and the section as a whole is intended to apply 
+	in other circumstances.
+      </para>
+      <para>	It is not the purpose of this section to induce you to infringe any patents or other property 
+	right claims or to contest validity of any such claims; this section has the sole purpose of 
+	protecting the integrity of the free software distribution system, which is implemented by public 
+	license practices. Many people have made generous contributions to the wide range of software 
+	distributed through that system in reliance on consistent application of that system; it is up 
+	to the author/donor to decide if he or she is willing to distribute software through any other 
+	system and a licensee cannot impose that choice.
+      </para>
+      <para>	This section is intended to make thoroughly clear what is believed to be a consequence of the 
+	rest of this License.
+      </para>
+    </sect2>
+    <sect2>
+      <title>Section 8
+      </title>
+      <para>	If the distribution and/or use of the Program is restricted in certain countries either by patents 
+	or by copyrighted interfaces, the original copyright holder who places the Program under this License 
+	may add an explicit geographical distribution limitation excluding those countries, so that 
+	distribution is permitted only in or among countries not thus excluded. In such case, this License 
+	incorporates the limitation as if written in the body of this License.
+      </para>
+    </sect2>
+    <sect2>
+      <title>Section 9
+      </title>
+      <para>	The Free Software Foundation may publish revised and/or new versions of the General Public License 
+	from time to time. Such new versions will be similar in spirit to the present version, but may differ 
+	in detail to address new problems or concerns.
+      </para>
+      <para>	Each version is given a distinguishing version number. If the Program specifies a version number of 
+	this License which applies to it and "any later version", you have the option of following the terms 
+	and conditions either of that version or of any later version published by the Free Software 
+	Foundation. If the Program does not specify a version number of this License, you may choose any 
+	version ever published by the Free Software Foundation.
+      </para>
+    </sect2>
+    <sect2>
+      <title>Section 10
+      </title>
+      <para>	If you wish to incorporate parts of the Program into other free programs whose distribution 
+	conditions are different, write to the author to ask for permission. For software which is copyrighted 
+	by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions 
+	for this. Our decision will be guided by the two goals of preserving the free status of all 
+	derivatives of our free software and of promoting the sharing and reuse of software generally.
+      </para>
+    </sect2>
+    <sect2>
+<title>NO WARRANTY Section 11
+      </title>
+      <para>	BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT 
+	PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR 
+	OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, 
+	INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 
+	PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE 
+	PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+      </para>
+    </sect2>
+    <sect2>
+      <title>Section 12
+      </title>
+      <para>	IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR 
+	ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU 
+	FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 
+	USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED 
+	INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH 
+	ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH 
+	DAMAGES.
+      </para>
+      <para>END OF TERMS AND CONDITIONS
+      </para>
+    </sect2>
+  </sect1>
+  <sect1>
+    <title>How to Apply These Terms to Your New Programs
+    </title>
+    <para>
+      If you develop a new program, and you want it to be of the greatest
+      possible use to the public, the best way to achieve this is to make it
+      free software which everyone can redistribute and change under these terms.
+    </para>
+    <para>
+      To do so, attach the following notices to the program.  It is safest
+      to attach them to the start of each source file to most effectively
+      convey the exclusion of warranty; and each file should have at least
+      the "copyright" line and a pointer to where the full notice is found.
+    </para>
+    <para>
+      &lt;one line to give the program's name and a brief idea of what it does.&gt;
+      Copyright (C) &lt;year&gt;    &lt;name of author&gt;
+    </para>
+    <para>
+      This program is free software; you can redistribute it and/or modify
+      it under the terms of the GNU General Public License as published by
+      the Free Software Foundation; either version 2 of the License, or
+      (at your option) any later version.
+    </para>
+    <para>
+      This program is distributed in the hope that it will be useful,
+      but WITHOUT ANY WARRANTY; without even the implied warranty of
+      MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+      GNU General Public License for more details.
+    </para>
+    <para>
+      You should have received a copy of the GNU General Public License
+      along with this program; if not, write to the Free Software
+      Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+    </para>
+    <para>
+      Also add information on how to contact you by electronic and paper mail.
+    </para>
+    <para>
+      If the program is interactive, make it output a short notice like this
+      when it starts in an interactive mode:
+    </para>
+    <para>
+      Gnomovision version 69, Copyright (C) year name of author
+      Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+      This is free software, and you are welcome to redistribute it
+      under certain conditions; type `show c' for details.
+    </para>
+    <para>
+      The hypothetical commands `show w' and `show c' should show the appropriate
+      parts of the General Public License.  Of course, the commands you use may
+      be called something other than `show w' and `show c'; they could even be
+      mouse-clicks or menu items--whatever suits your program.
+    </para>
+    <para>
+      You should also get your employer (if you work as a programmer) or your
+      school, if any, to sign a "copyright disclaimer" for the program, if
+      necessary.  Here is a sample; alter the names:
+    </para>
+    <para>
+      Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+      `Gnomovision' (which makes passes at compilers) written by James Hacker.
+    </para>
+    <para>
+      &lt;signature of Ty Coon&gt;, 1 April 1989
+      Ty Coon, President of Vice
+    </para>
+    <para>
+      This General Public License does not permit incorporating your program into
+      proprietary programs.  If your program is a subroutine library, you may
+      consider it more useful to permit linking proprietary applications with the
+      library.  If this is what you want to do, use the GNU Library General
+      Public License instead of this License.
+    </para>
+  </sect1>
+  </appendix>
diff --git a/docs-xml/Samba3-ByExample/images/AccountingNetwork.svg b/docs-xml/Samba3-ByExample/images/AccountingNetwork.svg
new file mode 100644
index 00000000000..7cf31f70fe9
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/AccountingNetwork.svg
@@ -0,0 +1,1588 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="12.034cm"
+   height="10.095cm"
+   viewBox="1.1 0.162 13.134 10.258"
+   id="svg2">
+  <defs
+     id="defs439" />
+  <text
+     x="4.2160001"
+     y="1.6"
+     id="text4"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Workgroup: BILLMORE</text>
+  <rect
+     width="1.5"
+     height="3"
+     x="1.15"
+     y="4.6500001"
+     id="rect6"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.5"
+     height="3"
+     x="1.15"
+     y="4.6500001"
+     id="rect8"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.5"
+     height="3"
+     x="1.15"
+     y="4.6500001"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.2"
+     height="1.2"
+     x="1.3"
+     y="4.8000002"
+     id="rect12"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.2"
+     height="1.2"
+     x="1.3"
+     y="4.8000002"
+     id="rect14"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.2"
+     height="1.2"
+     x="1.3"
+     y="4.8000002"
+     id="rect16"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.5"
+     y1="5.0999999"
+     x2="1.3"
+     y2="5.0999999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.3"
+     y1="5.4000001"
+     x2="2.5"
+     y2="5.4000001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line20"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.5"
+     y1="5.625"
+     x2="1.3"
+     y2="5.625"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line22"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.82499999"
+     height="0.44999999"
+     x="1.3"
+     y="6.1500001"
+     id="rect24"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.82499999"
+     height="0.44999999"
+     x="1.3"
+     y="6.1500001"
+     id="rect26"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.82499999"
+     height="0.44999999"
+     x="1.3"
+     y="6.1500001"
+     id="rect28"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.15"
+     y1="6.6750002"
+     x2="2.6500001"
+     y2="6.6750002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line30"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="1.825"
+     y="6.8249998"
+     id="rect32"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="1.825"
+     y="6.8249998"
+     id="rect34"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="1.825"
+     y="6.8249998"
+     id="rect36"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="2.125"
+     y="6.8249998"
+     id="rect38"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="2.125"
+     y="6.8249998"
+     id="rect40"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="2.125"
+     y="6.8249998"
+     id="rect42"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="2.425"
+     y="6.8249998"
+     id="rect44"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="2.425"
+     y="6.8249998"
+     id="rect46"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="2.425"
+     y="6.8249998"
+     id="rect48"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.15000001"
+     height="0.075000003"
+     x="2.3499999"
+     y="6.375"
+     id="rect50"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.15000001"
+     height="0.075000003"
+     x="2.3499999"
+     y="6.375"
+     id="rect52"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.15000001"
+     height="0.075000003"
+     x="2.3499999"
+     y="6.375"
+     id="rect54"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.3"
+     y1="6.375"
+     x2="2.125"
+     y2="6.375"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line56"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.22499999"
+     height="0.22499999"
+     x="1.3"
+     y="6.75"
+     id="rect58"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.22499999"
+     height="0.22499999"
+     x="1.3"
+     y="6.75"
+     id="rect60"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.22499999"
+     height="0.22499999"
+     x="1.3"
+     y="6.75"
+     id="rect62"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.05"
+     height="0.075000003"
+     x="1.375"
+     y="5.6999998"
+     id="rect64"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.05"
+     height="0.075000003"
+     x="1.375"
+     y="5.6999998"
+     id="rect66"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.05"
+     height="0.075000003"
+     x="1.375"
+     y="5.6999998"
+     id="rect68"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.375"
+     y1="6.2249999"
+     x2="2.05"
+     y2="6.2249999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line70"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.05"
+     y1="6.3000002"
+     x2="1.975"
+     y2="6.3000002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.375"
+     y1="6.3000002"
+     x2="1.45"
+     y2="6.3000002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.375"
+     height="0.075000003"
+     x="1.525"
+     y="6.2249999"
+     id="rect76"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.375"
+     height="0.075000003"
+     x="1.525"
+     y="6.2249999"
+     id="rect78"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.375"
+     height="0.075000003"
+     x="1.525"
+     y="6.2249999"
+     id="rect80"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.375"
+     y1="5.8499999"
+     x2="1.45"
+     y2="5.8499999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.525"
+     y1="5.8499999"
+     x2="1.6"
+     y2="5.8499999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line84"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.2750001"
+     y1="5.8499999"
+     x2="2.425"
+     y2="5.8499999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line86"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.575"
+     y1="7.5749998"
+     x2="1.225"
+     y2="7.5749998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line88"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.225"
+     y1="7.5"
+     x2="2.575"
+     y2="7.5"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line90"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.575"
+     y1="7.4250002"
+     x2="1.225"
+     y2="7.4250002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line92"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.225"
+     y1="7.3499999"
+     x2="2.575"
+     y2="7.3499999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line94"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.575"
+     y1="7.2750001"
+     x2="1.225"
+     y2="7.2750001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line96"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.225"
+     y1="7.1999998"
+     x2="2.575"
+     y2="7.1999998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line98"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.575"
+     y1="7.125"
+     x2="1.225"
+     y2="7.125"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line100"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.3329999"
+     height="4"
+     x="3.733"
+     y="3.688"
+     id="rect102"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.3329999"
+     height="4"
+     x="3.733"
+     y="3.688"
+     id="rect104"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.3329999"
+     height="4"
+     x="3.733"
+     y="3.688"
+     id="rect106"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.067"
+     height="1.6"
+     x="3.8670001"
+     y="3.8210001"
+     id="rect108"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.067"
+     height="1.6"
+     x="3.8670001"
+     y="3.8210001"
+     id="rect110"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.067"
+     height="1.6"
+     x="3.8670001"
+     y="3.8210001"
+     id="rect112"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8670001"
+     y1="4.0879998"
+     x2="4.9330001"
+     y2="4.0879998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line114"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.9330001"
+     y1="4.3540001"
+     x2="3.8670001"
+     y2="4.3540001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line116"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8670001"
+     y1="4.6209998"
+     x2="4.9330001"
+     y2="4.6209998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line118"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8670001"
+     y1="4.888"
+     x2="4.9330001"
+     y2="4.888"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line120"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.9330001"
+     y1="5.1539998"
+     x2="3.8670001"
+     y2="5.1539998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line122"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.73299998"
+     height="0.40000001"
+     x="3.8670001"
+     y="5.5539999"
+     id="rect124"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.73299998"
+     height="0.40000001"
+     x="3.8670001"
+     y="5.5539999"
+     id="rect126"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.73299998"
+     height="0.40000001"
+     x="3.8670001"
+     y="5.5539999"
+     id="rect128"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.733"
+     y1="6.2210002"
+     x2="5.0669999"
+     y2="6.2210002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line130"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.067000002"
+     height="0.067000002"
+     x="4.3330002"
+     y="6.3540001"
+     id="rect132"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.067000002"
+     height="0.067000002"
+     x="4.3330002"
+     y="6.3540001"
+     id="rect134"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.067000002"
+     height="0.067000002"
+     x="4.3330002"
+     y="6.3540001"
+     id="rect136"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.067000002"
+     height="0.067000002"
+     x="4.5999999"
+     y="6.3540001"
+     id="rect138"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.067000002"
+     height="0.067000002"
+     x="4.5999999"
+     y="6.3540001"
+     id="rect140"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.067000002"
+     height="0.067000002"
+     x="4.5999999"
+     y="6.3540001"
+     id="rect142"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.067000002"
+     height="0.067000002"
+     x="4.8670001"
+     y="6.3540001"
+     id="rect144"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.067000002"
+     height="0.067000002"
+     x="4.8670001"
+     y="6.3540001"
+     id="rect146"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.067000002"
+     height="0.067000002"
+     x="4.8670001"
+     y="6.3540001"
+     id="rect148"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.133"
+     height="0.133"
+     x="4.8000002"
+     y="5.954"
+     id="rect150"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.133"
+     height="0.133"
+     x="4.8000002"
+     y="5.954"
+     id="rect152"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.133"
+     height="0.133"
+     x="4.8000002"
+     y="5.954"
+     id="rect154"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8670001"
+     y1="5.7540002"
+     x2="4.5999999"
+     y2="5.7540002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line156"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.2"
+     height="0.2"
+     x="3.8670001"
+     y="6.2870002"
+     id="rect158"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.2"
+     height="0.2"
+     x="3.8670001"
+     y="6.2870002"
+     id="rect160"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.2"
+     height="0.2"
+     x="3.8670001"
+     y="6.2870002"
+     id="rect162"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.93300003"
+     height="0.067000002"
+     x="3.9330001"
+     y="5.2210002"
+     id="rect164"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.93300003"
+     height="0.067000002"
+     x="3.9330001"
+     y="5.2210002"
+     id="rect166"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.93300003"
+     height="0.067000002"
+     x="3.9330001"
+     y="5.2210002"
+     id="rect168"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.9330001"
+     y1="5.6209998"
+     x2="4.533"
+     y2="5.6209998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line170"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.533"
+     y1="5.6880002"
+     x2="4.467"
+     y2="5.6880002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line172"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.9330001"
+     y1="5.6880002"
+     x2="4"
+     y2="5.6880002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line174"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.333"
+     height="0.067000002"
+     x="4.0669999"
+     y="5.6209998"
+     id="rect176"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.333"
+     height="0.067000002"
+     x="4.0669999"
+     y="5.6209998"
+     id="rect178"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.333"
+     height="0.067000002"
+     x="4.0669999"
+     y="5.6209998"
+     id="rect180"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.9330001"
+     y1="5.3540001"
+     x2="4"
+     y2="5.3540001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line182"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.0669999"
+     y1="5.3540001"
+     x2="4.1329999"
+     y2="5.3540001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line184"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.7329998"
+     y1="5.3540001"
+     x2="4.8670001"
+     y2="5.3540001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line186"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8"
+     y1="7.6209998"
+     x2="5"
+     y2="7.6209998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line188"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5"
+     y1="7.5539999"
+     x2="3.8"
+     y2="7.5539999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line190"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8"
+     y1="7.487"
+     x2="5"
+     y2="7.487"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line192"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5"
+     y1="7.421"
+     x2="3.8"
+     y2="7.421"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line194"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8"
+     y1="7.3540001"
+     x2="5"
+     y2="7.3540001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line196"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5"
+     y1="7.2870002"
+     x2="3.8"
+     y2="7.2870002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line198"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8"
+     y1="7.2210002"
+     x2="5"
+     y2="7.2210002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line200"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5"
+     y1="7.1539998"
+     x2="3.8"
+     y2="7.1539998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line202"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8"
+     y1="7.0879998"
+     x2="5"
+     y2="7.0879998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line204"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5"
+     y1="7.0209999"
+     x2="3.8"
+     y2="7.0209999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line206"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8"
+     y1="6.954"
+     x2="5"
+     y2="6.954"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line208"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5"
+     y1="6.888"
+     x2="3.8"
+     y2="6.888"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line210"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8"
+     y1="6.8210001"
+     x2="5"
+     y2="6.8210001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line212"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5"
+     y1="6.7540002"
+     x2="3.8"
+     y2="6.7540002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line214"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="4"
+     height="1.3329999"
+     x="5.9749999"
+     y="6.3330002"
+     id="rect216"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="4"
+     height="1.3329999"
+     x="5.9749999"
+     y="6.3330002"
+     id="rect218"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="4"
+     height="1.3329999"
+     x="5.9749999"
+     y="6.3330002"
+     id="rect220"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.524"
+     height="0.76200002"
+     x="8.3559999"
+     y="6.7140002"
+     id="rect222"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.524"
+     height="0.76200002"
+     x="8.3559999"
+     y="6.7140002"
+     id="rect224"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.524"
+     height="0.76200002"
+     x="8.3559999"
+     y="6.7140002"
+     id="rect226"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.8800001"
+     y1="7.0949998"
+     x2="8.3559999"
+     y2="7.0949998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line228"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="1.048"
+     x="7.9749999"
+     y="6.4289999"
+     id="rect230"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="1.048"
+     x="7.9749999"
+     y="6.4289999"
+     id="rect232"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="1.048"
+     x="7.9749999"
+     y="6.4289999"
+     id="rect234"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.094999999"
+     height="0.094999999"
+     x="6.927"
+     y="6.5240002"
+     id="rect236"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.094999999"
+     height="0.094999999"
+     x="6.927"
+     y="6.5240002"
+     id="rect238"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.094999999"
+     height="0.094999999"
+     x="6.927"
+     y="6.5240002"
+     id="rect240"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.094999999"
+     height="0.094999999"
+     x="7.118"
+     y="6.5240002"
+     id="rect242"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.094999999"
+     height="0.094999999"
+     x="7.118"
+     y="6.5240002"
+     id="rect244"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.094999999"
+     height="0.094999999"
+     x="7.118"
+     y="6.5240002"
+     id="rect246"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.094999999"
+     height="0.094999999"
+     x="7.3080001"
+     y="6.5240002"
+     id="rect248"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.094999999"
+     height="0.094999999"
+     x="7.3080001"
+     y="6.5240002"
+     id="rect250"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.094999999"
+     height="0.094999999"
+     x="7.3080001"
+     y="6.5240002"
+     id="rect252"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.19"
+     height="0.19"
+     x="7.5939999"
+     y="6.4289999"
+     id="rect254"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.19"
+     height="0.19"
+     x="7.5939999"
+     y="6.4289999"
+     id="rect256"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.19"
+     height="0.19"
+     x="7.5939999"
+     y="6.4289999"
+     id="rect258"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.28600001"
+     x="6.165"
+     y="6.4289999"
+     id="rect260"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.28600001"
+     x="6.165"
+     y="6.4289999"
+     id="rect262"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.28600001"
+     x="6.165"
+     y="6.4289999"
+     id="rect264"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.3329999"
+     height="0.094999999"
+     x="8.4510002"
+     y="7.1900001"
+     id="rect266"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.3329999"
+     height="0.094999999"
+     x="8.4510002"
+     y="7.1900001"
+     id="rect268"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.3329999"
+     height="0.094999999"
+     x="8.4510002"
+     y="7.1900001"
+     id="rect270"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.0699997"
+     y1="6.5240002"
+     x2="8.0699997"
+     y2="7.381"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line272"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.094999999"
+     height="0.47600001"
+     x="8.0699997"
+     y="6.7140002"
+     id="rect274"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.094999999"
+     height="0.47600001"
+     x="8.0699997"
+     y="6.7140002"
+     id="rect276"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.094999999"
+     height="0.47600001"
+     x="8.0699997"
+     y="6.7140002"
+     id="rect278"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.5939999"
+     y1="7.381"
+     x2="9.7849998"
+     y2="7.381"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line280"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="6.0700002"
+     y1="7"
+     x2="7.7849998"
+     y2="7"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line282"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.7849998"
+     y1="7.0949998"
+     x2="6.0700002"
+     y2="7.0949998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line284"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="6.0700002"
+     y1="7.1900001"
+     x2="7.7849998"
+     y2="7.1900001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line286"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.7849998"
+     y1="7.4759998"
+     x2="6.0700002"
+     y2="7.4759998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line288"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="6.0700002"
+     y1="7.381"
+     x2="7.7849998"
+     y2="7.381"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line290"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.7849998"
+     y1="7.2859998"
+     x2="6.0700002"
+     y2="7.2859998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line292"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.4510002"
+     y1="7.381"
+     x2="8.5459995"
+     y2="7.381"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line294"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.6420002"
+     y1="7.381"
+     x2="8.7370005"
+     y2="7.381"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line296"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.165"
+     y1="7.381"
+     x2="8.165"
+     y2="7.2859998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line298"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.165"
+     y1="6.619"
+     x2="8.165"
+     y2="6.5240002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line300"
+     style="stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="11.127,6.517 11.039,6.554 10.775,7.214 10.775,7.544 10.907,7.654 12.843,7.654 12.975,7.544 12.975,7.214 12.711,6.554 12.623,6.517 11.127,6.517 "
+     id="polygon302"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="11.127,6.517 11.039,6.554 10.775,7.214 10.775,7.544 10.907,7.654 12.843,7.654 12.975,7.544 12.975,7.214 12.711,6.554 12.623,6.517 11.127,6.517 "
+     id="polygon304"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 10.819,7.104 L 10.907,7.141 L 12.843,7.141 L 12.931,7.104"
+     id="path306"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 12.843,7.141 L 12.975,7.214"
+     id="path308"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 10.775,7.214 L 10.907,7.141"
+     id="path310"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="11.391,5.821 11.347,6.701 12.403,6.701 12.359,5.821 11.391,5.821 "
+     id="polygon312"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="11.391,5.821 11.347,6.701 12.403,6.701 12.359,5.821 11.391,5.821 "
+     id="polygon314"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="11.215,6.701 11.127,6.957 12.623,6.957 12.535,6.701 11.215,6.701 "
+     id="polygon316"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="11.215,6.701 11.127,6.957 12.623,6.957 12.535,6.701 11.215,6.701 "
+     id="polygon318"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="11.215"
+     cy="7.2690001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse320"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.215"
+     cy="7.2690001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse322"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.435"
+     cy="7.2690001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse324"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.435"
+     cy="7.2690001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse326"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.655"
+     cy="7.2690001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse328"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.655"
+     cy="7.2690001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse330"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.215"
+     cy="7.3610001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse332"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.215"
+     cy="7.3610001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse334"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.435"
+     cy="7.3610001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse336"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.435"
+     cy="7.3610001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse338"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.655"
+     cy="7.3610001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse340"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.655"
+     cy="7.3610001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse342"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.215"
+     cy="7.4520001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse344"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.215"
+     cy="7.4520001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse346"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.435"
+     cy="7.4520001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse348"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.435"
+     cy="7.4520001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse350"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.655"
+     cy="7.4520001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse352"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.655"
+     cy="7.4520001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse354"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.215"
+     cy="7.5440001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse356"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.215"
+     cy="7.5440001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse358"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.435"
+     cy="7.5440001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse360"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.435"
+     cy="7.5440001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse362"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.655"
+     cy="7.5440001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse364"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="11.655"
+     cy="7.5440001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse366"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="11.875"
+     cy="7.2870002"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse368"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="11.875"
+     cy="7.2870002"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse370"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="12.425"
+     cy="7.2870002"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse372"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="12.425"
+     cy="7.2870002"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse374"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="2"
+     height="1.6670001"
+     x="6.9250002"
+     y="4.237"
+     id="rect376"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2"
+     height="1.6670001"
+     x="6.9250002"
+     y="4.237"
+     id="rect378"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2"
+     height="1.6670001"
+     x="6.9250002"
+     y="4.237"
+     id="rect380"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.778"
+     height="1.3329999"
+     x="7.0359998"
+     y="4.349"
+     id="rect382"
+     style="fill:#a1a1a1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.778"
+     height="1.3329999"
+     x="7.0359998"
+     y="4.349"
+     id="rect384"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.778"
+     height="1.3329999"
+     x="7.0359998"
+     y="4.349"
+     id="rect386"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="7.258,5.904 8.592,5.904 8.258,6.015 7.592,6.015 7.258,5.904 "
+     id="polygon388"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="7.258,5.904 8.592,5.904 8.258,6.015 7.592,6.015 7.258,5.904 "
+     id="polygon390"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="7.258,5.904 8.592,5.904 8.258,6.015 7.592,6.015 7.258,5.904 "
+     id="polygon392"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.667"
+     height="0.111"
+     x="7.592"
+     y="6.0149999"
+     id="rect394"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.667"
+     height="0.111"
+     x="7.592"
+     y="6.0149999"
+     id="rect396"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.667"
+     height="0.111"
+     x="7.592"
+     y="6.0149999"
+     id="rect398"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.3329999"
+     height="0.111"
+     x="7.2579999"
+     y="6.1259999"
+     id="rect400"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.3329999"
+     height="0.111"
+     x="7.2579999"
+     y="6.1259999"
+     id="rect402"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.3329999"
+     height="0.111"
+     x="7.2579999"
+     y="6.1259999"
+     id="rect404"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="1.863,7.675 1.863,9.350 12.012,9.350 12.012,7.662 "
+     id="polyline406"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="4.4000001"
+     y1="7.6880002"
+     x2="4.4120002"
+     y2="9.3380003"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line408"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="7.9749999"
+     y1="7.6669998"
+     x2="7.987"
+     y2="9.3249998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line410"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="5.4250002"
+     y="9.9750004"
+     id="text412"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 192.168.1.0/24</text>
+  <text
+     x="2.165"
+     y="8.2250004"
+     id="text414"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.1</text>
+  <text
+     x="4.6900001"
+     y="8.2290001"
+     id="text416"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.3</text>
+  <text
+     x="12.305"
+     y="8.1660004"
+     id="text418"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.10</text>
+  <text
+     x="8.5109997"
+     y="8.2379999"
+     id="text420"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.100+n</text>
+  <text
+     x="1.3200001"
+     y="2.875"
+     id="text422"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">stable</text>
+  <text
+     x="1.34"
+     y="3.4749999"
+     id="text424"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(NT4)</text>
+  <text
+     x="3.6670001"
+     y="2.8469999"
+     id="text426"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">cashpool</text>
+  <text
+     x="3.6949999"
+     y="3.447"
+     id="text428"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(Samba)</text>
+  <text
+     x="7.5609999"
+     y="2.872"
+     id="text430"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PCn</text>
+  <text
+     x="7.3260002"
+     y="3.4719999"
+     id="text432"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(n=1-9)</text>
+  <text
+     x="11.643"
+     y="4.3119998"
+     id="text434"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj</text>
+  <text
+     x="10.716"
+     y="4.9120002"
+     id="text436"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(HPLaserJet 4)</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/Charity-Network.svg b/docs-xml/Samba3-ByExample/images/Charity-Network.svg
new file mode 100644
index 00000000000..12905c80184
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/Charity-Network.svg
@@ -0,0 +1,1039 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="11.88cm"
+   height="9.4849997cm"
+   viewBox="0.827 -0.889 12.708 8.596"
+   id="svg2">
+  <defs
+     id="defs353" />
+  <rect
+     width="1.077"
+     height="2.5120001"
+     x="1.051"
+     y="0.93599999"
+     id="rect4"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.077"
+     height="2.5120001"
+     x="1.051"
+     y="0.93599999"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="0.861"
+     height="0.287"
+     x="1.158"
+     y="1.087"
+     id="rect8"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.861"
+     height="0.287"
+     x="1.158"
+     y="1.374"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.861"
+     height="0.287"
+     x="1.158"
+     y="1.661"
+     id="rect12"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.861"
+     height="0.287"
+     x="1.158"
+     y="1.948"
+     id="rect14"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.53799999"
+     height="0.17200001"
+     x="1.158"
+     y="2.293"
+     id="rect16"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="1.966"
+     cy="2.322"
+     rx="0.037999999"
+     ry="0.037999999"
+     id="ellipse18"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="1.966"
+     cy="2.322"
+     rx="0.037999999"
+     ry="0.037999999"
+     id="ellipse20"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="1.966"
+     cy="2.4360001"
+     rx="0.037999999"
+     ry="0.037999999"
+     id="ellipse22"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="1.966"
+     cy="2.4360001"
+     rx="0.037999999"
+     ry="0.037999999"
+     id="ellipse24"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.12899999"
+     height="0.115"
+     x="1.751"
+     y="2.3499999"
+     id="rect26"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.12899999"
+     height="0.115"
+     x="1.751"
+     y="2.3499999"
+     id="rect28"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 1.23,2.695 L 1.23,3.323"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 1.41,2.695 L 1.41,3.323"
+     id="path32"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 1.589,2.695 L 1.589,3.323"
+     id="path34"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 1.769,2.695 L 1.769,3.323"
+     id="path36"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 1.948,2.695 L 1.948,3.323"
+     id="path38"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 2.127,2.695 L 2.127,3.323"
+     id="path40"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="0.836,3.664 1.051,3.233 1.051,3.448 2.127,3.448 2.127,3.233 2.414,3.664 0.836,3.664 "
+     id="polygon42"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="0.836,3.664 1.051,3.233 1.051,3.448 2.127,3.448 2.127,3.233 2.414,3.664 0.836,3.664 "
+     id="polygon44"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.587"
+     y1="4.487"
+     x2="11.412"
+     y2="4.4629998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="1.625"
+     y1="3.664"
+     x2="1.624"
+     y2="4.5240002"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line48"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="2.9289999"
+     y="1.6210001"
+     id="rect50"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="2.9289999"
+     y="1.6210001"
+     id="rect52"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.58"
+     height="1.0420001"
+     x="3.148"
+     y="1.839"
+     id="rect54"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="3.202,3.134 4.24,3.134 4.24,3.369 3.257,3.369 3.202,3.134 "
+     id="polygon56"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="3.202,3.134 4.24,3.134 4.24,3.369 3.257,3.369 3.202,3.134 "
+     id="polygon58"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="4.24,3.134 4.673,3.134 4.618,3.369 4.24,3.369 4.24,3.134 "
+     id="polygon60"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="4.24,3.134 4.673,3.134 4.618,3.369 4.24,3.369 4.24,3.134 "
+     id="polygon62"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="4.3109999"
+     y="3.204"
+     id="rect64"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="4.3109999"
+     y="3.204"
+     id="rect66"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="3.736,3.369 4.139,3.369 4.139,3.487 4.341,3.487 4.341,3.604 3.534,3.604 3.534,3.487 3.736,3.487 3.736,3.369 "
+     id="polygon68"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="3.736,3.369 4.139,3.369 4.139,3.487 4.341,3.487 4.341,3.604 3.534,3.604 3.534,3.487 3.736,3.487 3.736,3.369 "
+     id="polygon70"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="5.5040002"
+     y="1.633"
+     id="rect72"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="5.5040002"
+     y="1.633"
+     id="rect74"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.58"
+     height="1.0420001"
+     x="5.723"
+     y="1.852"
+     id="rect76"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="5.777,3.146 6.815,3.146 6.815,3.381 5.832,3.381 5.777,3.146 "
+     id="polygon78"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.777,3.146 6.815,3.146 6.815,3.381 5.832,3.381 5.777,3.146 "
+     id="polygon80"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.815,3.146 7.248,3.146 7.193,3.381 6.815,3.381 6.815,3.146 "
+     id="polygon82"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.815,3.146 7.248,3.146 7.193,3.381 6.815,3.381 6.815,3.146 "
+     id="polygon84"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="6.8860002"
+     y="3.217"
+     id="rect86"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="6.8860002"
+     y="3.217"
+     id="rect88"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.311,3.381 6.714,3.381 6.714,3.499 6.916,3.499 6.916,3.617 6.109,3.617 6.109,3.499 6.311,3.499 6.311,3.381 "
+     id="polygon90"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.311,3.381 6.714,3.381 6.714,3.499 6.916,3.499 6.916,3.617 6.109,3.617 6.109,3.499 6.311,3.499 6.311,3.381 "
+     id="polygon92"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="7.9169998"
+     y="1.658"
+     id="rect94"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="7.9169998"
+     y="1.658"
+     id="rect96"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.58"
+     height="1.0420001"
+     x="8.1350002"
+     y="1.877"
+     id="rect98"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="8.19,3.171 9.228,3.171 9.228,3.406 8.244,3.406 8.19,3.171 "
+     id="polygon100"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.19,3.171 9.228,3.171 9.228,3.406 8.244,3.406 8.19,3.171 "
+     id="polygon102"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="9.228,3.171 9.66,3.171 9.606,3.406 9.228,3.406 9.228,3.171 "
+     id="polygon104"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.228,3.171 9.66,3.171 9.606,3.406 9.228,3.406 9.228,3.171 "
+     id="polygon106"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="9.2980003"
+     y="3.2420001"
+     id="rect108"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="9.2980003"
+     y="3.2420001"
+     id="rect110"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.723,3.406 9.127,3.406 9.127,3.524 9.328,3.524 9.328,3.642 8.522,3.642 8.522,3.524 8.723,3.524 8.723,3.406 "
+     id="polygon112"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.723,3.406 9.127,3.406 9.127,3.524 9.328,3.524 9.328,3.642 8.522,3.642 8.522,3.524 8.723,3.524 8.723,3.406 "
+     id="polygon114"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="10.342"
+     y="1.658"
+     id="rect116"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="10.342"
+     y="1.658"
+     id="rect118"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.58"
+     height="1.0420001"
+     x="10.56"
+     y="1.877"
+     id="rect120"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="10.615,3.171 11.653,3.171 11.653,3.406 10.669,3.406 10.615,3.171 "
+     id="polygon122"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="10.615,3.171 11.653,3.171 11.653,3.406 10.669,3.406 10.615,3.171 "
+     id="polygon124"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="11.653,3.171 12.085,3.171 12.031,3.406 11.653,3.406 11.653,3.171 "
+     id="polygon126"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="11.653,3.171 12.085,3.171 12.031,3.406 11.653,3.406 11.653,3.171 "
+     id="polygon128"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="11.723"
+     y="3.2420001"
+     id="rect130"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="11.723"
+     y="3.2420001"
+     id="rect132"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="11.148,3.406 11.552,3.406 11.552,3.524 11.753,3.524 11.753,3.642 10.947,3.642 10.947,3.524 11.148,3.524 11.148,3.406 "
+     id="polygon134"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="11.148,3.406 11.552,3.406 11.552,3.524 11.753,3.524 11.753,3.642 10.947,3.642 10.947,3.524 11.148,3.524 11.148,3.406 "
+     id="polygon136"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="3.938"
+     y1="3.6040001"
+     x2="3.9389999"
+     y2="5.2309999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.513"
+     y1="3.6170001"
+     x2="6.513"
+     y2="5.237"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line140"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.9250002"
+     y1="3.642"
+     x2="8.9329996"
+     y2="4.5"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line142"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="11.396"
+     y1="3.654"
+     x2="11.4"
+     y2="5.362"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line144"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="10.442"
+     y="5.3460002"
+     id="rect146"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="2.017"
+     height="1.513"
+     x="10.442"
+     y="5.3460002"
+     id="rect148"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.58"
+     height="1.0420001"
+     x="10.66"
+     y="5.5640001"
+     id="rect150"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="10.715,6.859 11.753,6.859 11.753,7.094 10.769,7.094 10.715,6.859 "
+     id="polygon152"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="10.715,6.859 11.753,6.859 11.753,7.094 10.769,7.094 10.715,6.859 "
+     id="polygon154"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="11.753,6.859 12.185,6.859 12.131,7.094 11.753,7.094 11.753,6.859 "
+     id="polygon156"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="11.753,6.859 12.185,6.859 12.131,7.094 11.753,7.094 11.753,6.859 "
+     id="polygon158"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="11.823"
+     y="6.9289999"
+     id="rect160"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.093999997"
+     height="0.093999997"
+     x="11.823"
+     y="6.9289999"
+     id="rect162"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="11.248,7.094 11.652,7.094 11.652,7.212 11.853,7.212 11.853,7.329 11.047,7.329 11.047,7.212 11.248,7.212 11.248,7.094 "
+     id="polygon164"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="11.248,7.094 11.652,7.094 11.652,7.212 11.853,7.212 11.853,7.329 11.047,7.329 11.047,7.212 11.248,7.212 11.248,7.094 "
+     id="polygon166"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="3.171,5.92 3.083,5.956 2.819,6.616 2.819,6.946 2.951,7.056 4.887,7.056 5.019,6.946 5.019,6.616 4.755,5.956 4.667,5.92 3.171,5.92 "
+     id="polygon168"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="3.171,5.92 3.083,5.956 2.819,6.616 2.819,6.946 2.951,7.056 4.887,7.056 5.019,6.946 5.019,6.616 4.755,5.956 4.667,5.92 3.171,5.92 "
+     id="polygon170"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 2.863,6.506 L 2.951,6.543 L 4.887,6.543 L 4.975,6.506"
+     id="path172"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.887,6.543 L 5.019,6.616"
+     id="path174"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 2.819,6.616 L 2.951,6.543"
+     id="path176"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="3.435,5.223 3.391,6.103 4.447,6.103 4.403,5.223 3.435,5.223 "
+     id="polygon178"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="3.435,5.223 3.391,6.103 4.447,6.103 4.403,5.223 3.435,5.223 "
+     id="polygon180"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="3.259,6.103 3.171,6.36 4.667,6.36 4.579,6.103 3.259,6.103 "
+     id="polygon182"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="3.259,6.103 3.171,6.36 4.667,6.36 4.579,6.103 3.259,6.103 "
+     id="polygon184"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="3.2590001"
+     cy="6.671"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse186"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.2590001"
+     cy="6.671"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse188"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.4790001"
+     cy="6.671"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse190"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.4790001"
+     cy="6.671"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse192"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.6989999"
+     cy="6.671"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse194"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.6989999"
+     cy="6.671"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse196"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.2590001"
+     cy="6.763"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse198"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.2590001"
+     cy="6.763"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse200"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.4790001"
+     cy="6.763"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse202"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.4790001"
+     cy="6.763"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse204"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.6989999"
+     cy="6.763"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse206"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.6989999"
+     cy="6.763"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse208"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.2590001"
+     cy="6.855"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse210"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.2590001"
+     cy="6.855"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse212"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.4790001"
+     cy="6.855"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse214"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.4790001"
+     cy="6.855"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse216"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.6989999"
+     cy="6.855"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse218"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.6989999"
+     cy="6.855"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse220"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.2590001"
+     cy="6.9460001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse222"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.2590001"
+     cy="6.9460001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse224"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.4790001"
+     cy="6.9460001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse226"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.4790001"
+     cy="6.9460001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse228"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.6989999"
+     cy="6.9460001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse230"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.6989999"
+     cy="6.9460001"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse232"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.9189999"
+     cy="6.6900001"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse234"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="3.9189999"
+     cy="6.6900001"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse236"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.4689999"
+     cy="6.6900001"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse238"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="4.4689999"
+     cy="6.6900001"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse240"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <polygon
+     points="5.807,5.902 5.719,5.939 5.455,6.599 5.455,6.929 5.587,7.039 7.523,7.039 7.655,6.929 7.655,6.599 7.391,5.939 7.303,5.902 5.807,5.902 "
+     id="polygon242"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="5.807,5.902 5.719,5.939 5.455,6.599 5.455,6.929 5.587,7.039 7.523,7.039 7.655,6.929 7.655,6.599 7.391,5.939 7.303,5.902 5.807,5.902 "
+     id="polygon244"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.499,6.489 L 5.587,6.525 L 7.523,6.525 L 7.611,6.489"
+     id="path246"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.523,6.525 L 7.655,6.599"
+     id="path248"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.455,6.599 L 5.587,6.525"
+     id="path250"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.071,5.205 6.027,6.085 7.083,6.085 7.039,5.205 6.071,5.205 "
+     id="polygon252"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.071,5.205 6.027,6.085 7.083,6.085 7.039,5.205 6.071,5.205 "
+     id="polygon254"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.895,6.085 5.807,6.342 7.303,6.342 7.215,6.085 5.895,6.085 "
+     id="polygon256"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="5.895,6.085 5.807,6.342 7.303,6.342 7.215,6.085 5.895,6.085 "
+     id="polygon258"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="5.895"
+     cy="6.6539998"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse260"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.895"
+     cy="6.6539998"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse262"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1149998"
+     cy="6.6539998"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse264"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1149998"
+     cy="6.6539998"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse266"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.335"
+     cy="6.6539998"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse268"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.335"
+     cy="6.6539998"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse270"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.895"
+     cy="6.7449999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse272"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.895"
+     cy="6.7449999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse274"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1149998"
+     cy="6.7449999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse276"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1149998"
+     cy="6.7449999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse278"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.335"
+     cy="6.7449999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse280"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.335"
+     cy="6.7449999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse282"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.895"
+     cy="6.8369999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse284"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.895"
+     cy="6.8369999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse286"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1149998"
+     cy="6.8369999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse288"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1149998"
+     cy="6.8369999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse290"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.335"
+     cy="6.8369999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse292"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.335"
+     cy="6.8369999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse294"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.895"
+     cy="6.9289999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse296"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.895"
+     cy="6.9289999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse298"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1149998"
+     cy="6.9289999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse300"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1149998"
+     cy="6.9289999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse302"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.335"
+     cy="6.9289999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse304"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.335"
+     cy="6.9289999"
+     rx="0.022"
+     ry="0.022"
+     id="ellipse306"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5549998"
+     cy="6.6719999"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse308"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="6.5549998"
+     cy="6.6719999"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse310"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.105"
+     cy="6.6719999"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse312"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="7.105"
+     cy="6.6719999"
+     rx="0.27500001"
+     ry="0.088"
+     id="ellipse314"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <text
+     x="3.415"
+     y="1.183"
+     id="text316"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk1</text>
+  <text
+     x="5.9000001"
+     y="1.184"
+     id="text318"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk2</text>
+  <text
+     x="8.3559999"
+     y="1.202"
+     id="text320"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk3</text>
+  <text
+     x="10.813"
+     y="1.237"
+     id="text322"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk4</text>
+  <text
+     x="10.92"
+     y="8.0609999"
+     id="text324"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk5</text>
+  <text
+     x="1.138"
+     y="0.44"
+     id="text326"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">server</text>
+  <text
+     x="4.809"
+     y="-0.479"
+     id="text328"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Workgroup: MIDEARTH</text>
+  <text
+     x="3.0309999"
+     y="8.0959997"
+     id="text330"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PRINTQ</text>
+  <text
+     x="6.211"
+     y="8.0249996"
+     id="text332"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj5</text>
+  <text
+     x="1.154"
+     y="4.1560001"
+     id="text334"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.1</text>
+  <text
+     x="3.0799999"
+     y="4.145"
+     id="text336"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.101</text>
+  <text
+     x="5.605"
+     y="4.1430001"
+     id="text338"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.102</text>
+  <text
+     x="8.0349998"
+     y="4.1360002"
+     id="text340"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.103</text>
+  <text
+     x="10.516"
+     y="4.1459999"
+     id="text342"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.104</text>
+  <text
+     x="10.515"
+     y="5.1589999"
+     id="text344"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.105</text>
+  <text
+     x="3.2379999"
+     y="5.0170002"
+     id="text346"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.20</text>
+  <text
+     x="5.8140001"
+     y="5.007"
+     id="text348"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.30</text>
+  <text
+     x="5.5159998"
+     y="0.15899999"
+     id="text350"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 192.168.1.0/24</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/Domain-WorkgroupAnnouncement.png b/docs-xml/Samba3-ByExample/images/Domain-WorkgroupAnnouncement.png
new file mode 100644
index 00000000000..e65882b2cef
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/Domain-WorkgroupAnnouncement.png
diff --git a/docs-xml/Samba3-ByExample/images/HostAnnouncment.png b/docs-xml/Samba3-ByExample/images/HostAnnouncment.png
new file mode 100644
index 00000000000..56f9fb85764
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/HostAnnouncment.png
diff --git a/docs-xml/Samba3-ByExample/images/LocalMasterAnnouncement.png b/docs-xml/Samba3-ByExample/images/LocalMasterAnnouncement.png
new file mode 100644
index 00000000000..8b22bc35c52
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/LocalMasterAnnouncement.png
diff --git a/docs-xml/Samba3-ByExample/images/NullConnect.png b/docs-xml/Samba3-ByExample/images/NullConnect.png
new file mode 100644
index 00000000000..5320fc6db11
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/NullConnect.png
diff --git a/docs-xml/Samba3-ByExample/images/UNIX-Samba-and-LDAP.svg b/docs-xml/Samba3-ByExample/images/UNIX-Samba-and-LDAP.svg
new file mode 100644
index 00000000000..ebd74129611
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/UNIX-Samba-and-LDAP.svg
@@ -0,0 +1,312 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="22.440001cm"
+   height="13.923cm"
+   viewBox="2.2 5.38 24.64 19.302"
+   id="svg2">
+  <defs
+     id="defs95" />
+  <rect
+     width="7.625"
+     height="11.175"
+     x="9.3500004"
+     y="6.2750001"
+     id="rect4"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.162"
+     y1="6.2750001"
+     x2="13.162"
+     y2="17.450001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line6"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.3500004"
+     y1="8.8500004"
+     x2="16.975"
+     y2="8.8500004"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line8"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.3400002"
+     y1="11.68"
+     x2="16.975"
+     y2="11.725"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line10"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.3149996"
+     y1="14.655"
+     x2="16.950001"
+     y2="14.65"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line12"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="10.404"
+     y="5.9749999"
+     id="text14"
+     style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Posix</text>
+  <text
+     x="14.161"
+     y="5.9650002"
+     id="text16"
+     style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
+  <text
+     x="10.277"
+     y="7.7399998"
+     id="text18"
+     style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">People</text>
+  <text
+     x="14.52"
+     y="7.375"
+     id="text20"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">User</text>
+  <text
+     x="14.043"
+     y="8.1750002"
+     id="text22"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounts</text>
+  <text
+     x="10.328"
+     y="16.25"
+     id="text24"
+     style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">uid/gids</text>
+  <text
+     x="14.086"
+     y="13.125"
+     id="text26"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Windows</text>
+  <text
+     x="14.27"
+     y="13.925"
+     id="text28"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Groups</text>
+  <text
+     x="10.306"
+     y="13.334"
+     id="text30"
+     style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Groups</text>
+  <text
+     x="10.285"
+     y="10.459"
+     id="text32"
+     style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">People</text>
+  <text
+     x="14.193"
+     y="9.7340002"
+     id="text34"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain</text>
+  <text
+     x="14.138"
+     y="10.534"
+     id="text36"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member</text>
+  <text
+     x="13.99"
+     y="11.334"
+     id="text38"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Machines</text>
+  <text
+     x="14.257"
+     y="16.284"
+     id="text40"
+     style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">SIDs</text>
+  <rect
+     width="4.3499999"
+     height="1.625"
+     x="2.25"
+     y="9.4499998"
+     id="rect42"
+     style="fill:#c6c6c6;stroke:none;stroke-width:0" />
+  <rect
+     width="4.3499999"
+     height="1.625"
+     x="2.25"
+     y="9.4499998"
+     id="rect44"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.3500004"
+     y1="6.2750001"
+     x2="6.5999999"
+     y2="9.4499998"
+     stroke="#000000"
+     stroke-width="0.050"
+     stroke-dasharray="0.10,0.10"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
+  <line
+     x1="6.5999999"
+     y1="11.075"
+     x2="9.3249998"
+     y2="14.65"
+     stroke="#000000"
+     stroke-width="0.050"
+     stroke-dasharray="0.10,0.10"
+     id="line48"
+     style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
+  <text
+     x="3.313"
+     y="10.5"
+     id="text50"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NSS_LDAP</text>
+  <rect
+     width="5.0999999"
+     height="1.625"
+     x="2.2750001"
+     y="15.225"
+     id="rect52"
+     style="fill:#b9b9b9;stroke:none;stroke-width:0" />
+  <rect
+     width="5.0999999"
+     height="1.625"
+     x="2.2750001"
+     y="15.225"
+     id="rect54"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.415"
+     y="16.247"
+     id="text56"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Winbind (NSS)</text>
+  <line
+     x1="9.3500004"
+     y1="14.725"
+     x2="7.375"
+     y2="15.225"
+     stroke="#000000"
+     stroke-width="0.050"
+     stroke-dasharray="0.10,0.10"
+     id="line58"
+     style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
+  <line
+     x1="7.375"
+     y1="16.85"
+     x2="9.3500004"
+     y2="17.450001"
+     stroke="#000000"
+     stroke-width="0.050"
+     stroke-dasharray="0.10,0.10"
+     id="line60"
+     style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
+  <rect
+     width="5.25"
+     height="2.2249999"
+     x="19.325001"
+     y="9.1499996"
+     id="rect62"
+     style="fill:#adadad;stroke:none;stroke-width:0" />
+  <rect
+     width="5.25"
+     height="2.2249999"
+     x="19.325001"
+     y="9.1499996"
+     id="rect64"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="20.535"
+     y="10.522"
+     id="text66"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd + winbind</text>
+  <line
+     x1="16.975"
+     y1="6.2750001"
+     x2="19.325001"
+     y2="9.1499996"
+     stroke="#000000"
+     stroke-width="0.050"
+     stroke-dasharray="0.10,0.10"
+     id="line68"
+     style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
+  <line
+     x1="19.325001"
+     y1="11.375"
+     x2="16.975"
+     y2="14.675"
+     stroke="#000000"
+     stroke-width="0.050"
+     stroke-dasharray="0.10,0.10"
+     id="line70"
+     style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
+  <rect
+     width="5.25"
+     height="2.1300001"
+     x="19.34"
+     y="14.925"
+     id="rect72"
+     style="fill:#adadad;stroke:none;stroke-width:0" />
+  <rect
+     width="5.25"
+     height="2.1300001"
+     x="19.34"
+     y="14.925"
+     id="rect74"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="21.211"
+     y="15.875"
+     id="text76"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">winbind</text>
+  <text
+     x="21.121"
+     y="16.575001"
+     id="text78"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(IDMAP)</text>
+  <line
+     x1="19.34"
+     y1="14.925"
+     x2="16.975"
+     y2="14.6"
+     stroke="#000000"
+     stroke-width="0.050"
+     stroke-dasharray="0.10,0.10"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
+  <line
+     x1="19.34"
+     y1="17.055"
+     x2="17.049999"
+     y2="17.375"
+     stroke="#000000"
+     stroke-width="0.050"
+     stroke-dasharray="0.10,0.10"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
+  <text
+     x="3.2219999"
+     y="6.375"
+     id="text84"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">UNIX Interface</text>
+  <text
+     x="3.8310001"
+     y="7.0749998"
+     id="text86"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">to LDAP</text>
+  <text
+     x="20.378"
+     y="6.3000002"
+     id="text88"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba Interface</text>
+  <text
+     x="21.156"
+     y="7"
+     id="text90"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">to LDAP</text>
+  <text
+     x="11.024"
+     y="18.74"
+     id="text92"
+     style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP Database</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/UserConnect.png b/docs-xml/Samba3-ByExample/images/UserConnect.png
new file mode 100644
index 00000000000..0b9acce15e3
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/UserConnect.png
diff --git a/docs-xml/Samba3-ByExample/images/UserMgrNT4.png b/docs-xml/Samba3-ByExample/images/UserMgrNT4.png
new file mode 100644
index 00000000000..516c75b4b19
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/UserMgrNT4.png
diff --git a/docs-xml/Samba3-ByExample/images/WINREPRESSME-Capture.png b/docs-xml/Samba3-ByExample/images/WINREPRESSME-Capture.png
new file mode 100644
index 00000000000..3b6dc3ae564
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/WINREPRESSME-Capture.png
diff --git a/docs-xml/Samba3-ByExample/images/WINREPRESSME-Capture2.png b/docs-xml/Samba3-ByExample/images/WINREPRESSME-Capture2.png
new file mode 100644
index 00000000000..b9b82c2287c
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/WINREPRESSME-Capture2.png
diff --git a/docs-xml/Samba3-ByExample/images/Windows-ME-WINEPRESSME-Startup-30min-ProtocolStats.png b/docs-xml/Samba3-ByExample/images/Windows-ME-WINEPRESSME-Startup-30min-ProtocolStats.png
new file mode 100644
index 00000000000..6e23d1632a0
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/Windows-ME-WINEPRESSME-Startup-30min-ProtocolStats.png
diff --git a/docs-xml/Samba3-ByExample/images/Windows-ME-WINEPRESSME-Startup-30min-TraceStats.png b/docs-xml/Samba3-ByExample/images/Windows-ME-WINEPRESSME-Startup-30min-TraceStats.png
new file mode 100644
index 00000000000..f5fd7384759
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/Windows-ME-WINEPRESSME-Startup-30min-TraceStats.png
diff --git a/docs-xml/Samba3-ByExample/images/WindowsXP-NullConnection.png b/docs-xml/Samba3-ByExample/images/WindowsXP-NullConnection.png
new file mode 100644
index 00000000000..76d1ac2c9ad
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/WindowsXP-NullConnection.png
diff --git a/docs-xml/Samba3-ByExample/images/WindowsXP-UserConnection.png b/docs-xml/Samba3-ByExample/images/WindowsXP-UserConnection.png
new file mode 100644
index 00000000000..d60fefc6593
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/WindowsXP-UserConnection.png
diff --git a/docs-xml/Samba3-ByExample/images/XP-screen001.png b/docs-xml/Samba3-ByExample/images/XP-screen001.png
new file mode 100644
index 00000000000..6f0fe58e781
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/XP-screen001.png
diff --git a/docs-xml/Samba3-ByExample/images/acct2net.svg b/docs-xml/Samba3-ByExample/images/acct2net.svg
new file mode 100644
index 00000000000..13153b9a421
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/acct2net.svg
@@ -0,0 +1,1901 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="12.429cm"
+   height="7.289cm"
+   viewBox="0.025 1.145 12.454 8.434"
+   id="svg2">
+  <defs
+     id="defs595" />
+  <rect
+     width="4.4790001"
+     height="5.9099998"
+     x="0.34999999"
+     y="2.1919999"
+     id="rect4"
+     style="fill:#dcdcdc;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.35,2.192 C 0.18431458,2.192 0.05,2.3263146 0.05,2.492"
+     id="path6"
+     style="fill:#dcdcdc;stroke:none" />
+  <path
+     d="M 5.129,2.492 C 5.129,2.3263146 4.9946854,2.192 4.829,2.192"
+     id="path8"
+     style="fill:#dcdcdc;stroke:none" />
+  <rect
+     width="5.079"
+     height="5.3099999"
+     x="0.050000001"
+     y="2.4920001"
+     id="rect10"
+     style="fill:#dcdcdc;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.05,7.802 C 0.05,7.9676854 0.18431458,8.102 0.35,8.102"
+     id="path12"
+     style="fill:#dcdcdc;stroke:none" />
+  <path
+     d="M 4.829,8.102 C 4.9946854,8.102 5.129,7.9676854 5.129,7.802"
+     id="path14"
+     style="fill:#dcdcdc;stroke:none" />
+  <line
+     x1="0.34999999"
+     y1="2.1919999"
+     x2="4.829"
+     y2="2.1919999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.34999999"
+     y1="8.1020002"
+     x2="4.829"
+     y2="8.1020002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.35,2.192 C 0.18431458,2.192 0.05,2.3263146 0.05,2.492"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 5.129,2.492 C 5.129,2.3263146 4.9946854,2.192 4.829,2.192"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.050000001"
+     y1="2.4920001"
+     x2="0.050000001"
+     y2="7.802"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="5.1290002"
+     y1="2.4920001"
+     x2="5.1290002"
+     y2="7.802"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.05,7.802 C 0.05,7.9676854 0.18431458,8.102 0.35,8.102"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 4.829,8.102 C 4.9946854,8.102 5.129,7.9676854 5.129,7.802"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="4.1500001"
+     height="5.9629998"
+     x="7.9790001"
+     y="2.1400001"
+     id="rect32"
+     style="fill:#dcdcdc;stroke:none;stroke-width:0" />
+  <path
+     d="M 7.979,2.14 C 7.8133146,2.14 7.679,2.2743146 7.679,2.44"
+     id="path34"
+     style="fill:#dcdcdc;stroke:none" />
+  <path
+     d="M 12.429,2.44 C 12.429,2.2743146 12.294685,2.14 12.129,2.14"
+     id="path36"
+     style="fill:#dcdcdc;stroke:none" />
+  <rect
+     width="4.75"
+     height="5.3629999"
+     x="7.6789999"
+     y="2.4400001"
+     id="rect38"
+     style="fill:#dcdcdc;stroke:none;stroke-width:0" />
+  <path
+     d="M 7.679,7.802 C 7.679,7.9676854 7.8133146,8.102 7.979,8.102"
+     id="path40"
+     style="fill:#dcdcdc;stroke:none" />
+  <path
+     d="M 12.129,8.102 C 12.294685,8.102 12.429,7.9676854 12.429,7.802"
+     id="path42"
+     style="fill:#dcdcdc;stroke:none" />
+  <line
+     x1="7.9790001"
+     y1="2.1400001"
+     x2="12.129"
+     y2="2.1400001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line44"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="7.9790001"
+     y1="8.1020002"
+     x2="12.129"
+     y2="8.1020002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 7.979,2.14 C 7.8133146,2.14 7.679,2.2743146 7.679,2.44"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.429,2.44 C 12.429,2.2743146 12.294685,2.14 12.129,2.14"
+     id="path50"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="7.6789999"
+     y1="2.4400001"
+     x2="7.6789999"
+     y2="7.802"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.429"
+     y1="2.4400001"
+     x2="12.429"
+     y2="7.802"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line54"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 7.679,7.802 C 7.679,7.9676854 7.8133146,8.102 7.979,8.102"
+     id="path56"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.129,8.102 C 12.294685,8.102 12.429,7.9676854 12.429,7.802"
+     id="path58"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <text
+     x="5.3099999"
+     y="4.9510002"
+     id="text60"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.1</text>
+  <text
+     x="1.069"
+     y="6.0370002"
+     id="text62"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">IP via DHCP</text>
+  <text
+     x="4.098"
+     y="3.1889999"
+     id="text64"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj4</text>
+  <rect
+     width="1.309"
+     height="3.928"
+     x="5.7750001"
+     y="3.1860001"
+     id="rect66"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.309"
+     height="3.928"
+     x="5.7750001"
+     y="3.1860001"
+     id="rect68"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.309"
+     height="3.928"
+     x="5.7750001"
+     y="3.1860001"
+     id="rect70"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.0470001"
+     height="1.571"
+     x="5.9060001"
+     y="3.3169999"
+     id="rect72"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.0470001"
+     height="1.571"
+     x="5.9060001"
+     y="3.3169999"
+     id="rect74"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.0470001"
+     height="1.571"
+     x="5.9060001"
+     y="3.3169999"
+     id="rect76"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.9060001"
+     y1="3.579"
+     x2="6.9530001"
+     y2="3.579"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line78"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="6.9530001"
+     y1="3.8410001"
+     x2="5.9060001"
+     y2="3.8410001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.9060001"
+     y1="4.1030002"
+     x2="6.9530001"
+     y2="4.1030002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.9060001"
+     y1="4.3639998"
+     x2="6.9530001"
+     y2="4.3639998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line84"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="6.9530001"
+     y1="4.6259999"
+     x2="5.9060001"
+     y2="4.6259999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line86"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.72000003"
+     height="0.39300001"
+     x="5.9060001"
+     y="5.0190001"
+     id="rect88"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.72000003"
+     height="0.39300001"
+     x="5.9060001"
+     y="5.0190001"
+     id="rect90"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.72000003"
+     height="0.39300001"
+     x="5.9060001"
+     y="5.0190001"
+     id="rect92"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.7750001"
+     y1="5.6739998"
+     x2="7.0840001"
+     y2="5.6739998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line94"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.064999998"
+     height="0.064999998"
+     x="6.3639998"
+     y="5.8049998"
+     id="rect96"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.064999998"
+     height="0.064999998"
+     x="6.3639998"
+     y="5.8049998"
+     id="rect98"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.064999998"
+     height="0.064999998"
+     x="6.3639998"
+     y="5.8049998"
+     id="rect100"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.064999998"
+     height="0.064999998"
+     x="6.6259999"
+     y="5.8049998"
+     id="rect102"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.064999998"
+     height="0.064999998"
+     x="6.6259999"
+     y="5.8049998"
+     id="rect104"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.064999998"
+     height="0.064999998"
+     x="6.6259999"
+     y="5.8049998"
+     id="rect106"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.064999998"
+     height="0.064999998"
+     x="6.888"
+     y="5.8049998"
+     id="rect108"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.064999998"
+     height="0.064999998"
+     x="6.888"
+     y="5.8049998"
+     id="rect110"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.064999998"
+     height="0.064999998"
+     x="6.888"
+     y="5.8049998"
+     id="rect112"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.131"
+     height="0.131"
+     x="6.822"
+     y="5.4120002"
+     id="rect114"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.131"
+     height="0.131"
+     x="6.822"
+     y="5.4120002"
+     id="rect116"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.131"
+     height="0.131"
+     x="6.822"
+     y="5.4120002"
+     id="rect118"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.9060001"
+     y1="5.2150002"
+     x2="6.6259999"
+     y2="5.2150002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line120"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.19599999"
+     height="0.19599999"
+     x="5.9060001"
+     y="5.7389998"
+     id="rect122"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.19599999"
+     height="0.19599999"
+     x="5.9060001"
+     y="5.7389998"
+     id="rect124"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.19599999"
+     height="0.19599999"
+     x="5.9060001"
+     y="5.7389998"
+     id="rect126"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.917"
+     height="0.064999998"
+     x="5.9710002"
+     y="4.6919999"
+     id="rect128"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.917"
+     height="0.064999998"
+     x="5.9710002"
+     y="4.6919999"
+     id="rect130"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.917"
+     height="0.064999998"
+     x="5.9710002"
+     y="4.6919999"
+     id="rect132"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.9710002"
+     y1="5.085"
+     x2="6.5609999"
+     y2="5.085"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line134"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="6.5609999"
+     y1="5.1500001"
+     x2="6.4949999"
+     y2="5.1500001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.9710002"
+     y1="5.1500001"
+     x2="6.0370002"
+     y2="5.1500001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.32699999"
+     height="0.064999998"
+     x="6.1020002"
+     y="5.085"
+     id="rect140"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.32699999"
+     height="0.064999998"
+     x="6.1020002"
+     y="5.085"
+     id="rect142"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.32699999"
+     height="0.064999998"
+     x="6.1020002"
+     y="5.085"
+     id="rect144"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.9710002"
+     y1="4.823"
+     x2="6.0370002"
+     y2="4.823"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line146"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="6.1020002"
+     y1="4.823"
+     x2="6.1680002"
+     y2="4.823"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line148"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="6.757"
+     y1="4.823"
+     x2="6.888"
+     y2="4.823"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line150"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.8400002"
+     y1="7.0489998"
+     x2="7.0190001"
+     y2="7.0489998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line152"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.0190001"
+     y1="6.9829998"
+     x2="5.8400002"
+     y2="6.9829998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line154"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.8400002"
+     y1="6.9180002"
+     x2="7.0190001"
+     y2="6.9180002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line156"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.0190001"
+     y1="6.8520002"
+     x2="5.8400002"
+     y2="6.8520002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line158"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.8400002"
+     y1="6.7870002"
+     x2="7.0190001"
+     y2="6.7870002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line160"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.0190001"
+     y1="6.7210002"
+     x2="5.8400002"
+     y2="6.7210002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line162"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.8400002"
+     y1="6.6560001"
+     x2="7.0190001"
+     y2="6.6560001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line164"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.0190001"
+     y1="6.5900002"
+     x2="5.8400002"
+     y2="6.5900002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line166"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.8400002"
+     y1="6.5250001"
+     x2="7.0190001"
+     y2="6.5250001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line168"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.0190001"
+     y1="6.4590001"
+     x2="5.8400002"
+     y2="6.4590001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line170"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.8400002"
+     y1="6.3940001"
+     x2="7.0190001"
+     y2="6.3940001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line172"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.0190001"
+     y1="6.3280001"
+     x2="5.8400002"
+     y2="6.3280001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line174"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.8400002"
+     y1="6.263"
+     x2="7.0190001"
+     y2="6.263"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line176"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.0190001"
+     y1="6.197"
+     x2="5.8400002"
+     y2="6.197"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line178"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.0159998"
+     y1="5.1269999"
+     x2="11.562"
+     y2="5.1269999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line180"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="7.6430001"
+     y1="5.1269999"
+     x2="7.6430001"
+     y2="5.125"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line182"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.5790005"
+     y1="5.1269999"
+     x2="8.5790005"
+     y2="4.2020001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line184"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.5790005"
+     y1="5.1269999"
+     x2="8.5790005"
+     y2="6.177"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line186"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.016"
+     y1="5.1269999"
+     x2="10.016"
+     y2="4.2150002"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line188"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.177"
+     y1="5.1269999"
+     x2="10.177"
+     y2="5.1399999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line190"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="11.512"
+     y1="5.1269999"
+     x2="11.512"
+     y2="4.177"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line192"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="0.55599999"
+     y1="5.1669998"
+     x2="5.7789998"
+     y2="5.177"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line194"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="2.244"
+     y1="5.1700001"
+     x2="2.244"
+     y2="5.1599998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line196"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="1.738"
+     y1="5.1690001"
+     x2="1.74"
+     y2="4.1259999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line198"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="4.1370001"
+     y1="5.1739998"
+     x2="4.1389999"
+     y2="4.27"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line200"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="2.7620001"
+     y1="5.171"
+     x2="2.7639999"
+     y2="4.1240001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line202"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="4.1430001"
+     y1="5.1739998"
+     x2="4.1409998"
+     y2="6.165"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line204"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="0.60600001"
+     y1="5.1669998"
+     x2="0.60799998"
+     y2="4.1690001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line206"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.713"
+     height="0.53500003"
+     x="8.2119999"
+     y="3.5190001"
+     id="rect208"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.713"
+     height="0.53500003"
+     x="8.2119999"
+     y="3.5190001"
+     id="rect210"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.55900002"
+     height="0.36899999"
+     x="8.2889996"
+     y="3.596"
+     id="rect212"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="8.308,4.054 8.675,4.054 8.675,4.137 8.328,4.137 8.308,4.054 "
+     id="polygon214"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.308,4.054 8.675,4.054 8.675,4.137 8.328,4.137 8.308,4.054 "
+     id="polygon216"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.675,4.054 8.828,4.054 8.809,4.137 8.675,4.137 8.675,4.054 "
+     id="polygon218"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.675,4.054 8.828,4.054 8.809,4.137 8.675,4.137 8.675,4.054 "
+     id="polygon220"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.033"
+     height="0.033"
+     x="8.6999998"
+     y="4.079"
+     id="rect222"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.033"
+     height="0.033"
+     x="8.6999998"
+     y="4.079"
+     id="rect224"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.497,4.137 8.64,4.137 8.64,4.179 8.711,4.179 8.711,4.22 8.426,4.22 8.426,4.179 8.497,4.179 8.497,4.137 "
+     id="polygon226"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.497,4.137 8.64,4.137 8.64,4.179 8.711,4.179 8.711,4.22 8.426,4.22 8.426,4.179 8.497,4.179 8.497,4.137 "
+     id="polygon228"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.67199999"
+     height="0.50400001"
+     x="1.404"
+     y="3.4649999"
+     id="rect230"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.67199999"
+     height="0.50400001"
+     x="1.404"
+     y="3.4649999"
+     id="rect232"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.52700001"
+     height="0.347"
+     x="1.476"
+     y="3.5380001"
+     id="rect234"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="1.495,3.969 1.841,3.969 1.841,4.048 1.513,4.048 1.495,3.969 "
+     id="polygon236"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="1.495,3.969 1.841,3.969 1.841,4.048 1.513,4.048 1.495,3.969 "
+     id="polygon238"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="1.841,3.969 1.985,3.969 1.967,4.048 1.841,4.048 1.841,3.969 "
+     id="polygon240"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="1.841,3.969 1.985,3.969 1.967,4.048 1.841,4.048 1.841,3.969 "
+     id="polygon242"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.030999999"
+     height="0.030999999"
+     x="1.864"
+     y="3.993"
+     id="rect244"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.030999999"
+     height="0.030999999"
+     x="1.864"
+     y="3.993"
+     id="rect246"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="1.672,4.048 1.807,4.048 1.807,4.087 1.874,4.087 1.874,4.126 1.605,4.126 1.605,4.087 1.672,4.087 1.672,4.048 "
+     id="polygon248"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="1.672,4.048 1.807,4.048 1.807,4.087 1.874,4.087 1.874,4.126 1.605,4.126 1.605,4.087 1.672,4.087 1.672,4.048 "
+     id="polygon250"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.64499998"
+     height="0.484"
+     x="2.441"
+     y="3.49"
+     id="rect252"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.64499998"
+     height="0.484"
+     x="2.441"
+     y="3.49"
+     id="rect254"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.505"
+     height="0.333"
+     x="2.5109999"
+     y="3.5599999"
+     id="rect256"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="2.528,3.974 2.86,3.974 2.86,4.049 2.546,4.049 2.528,3.974 "
+     id="polygon258"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="2.528,3.974 2.86,3.974 2.86,4.049 2.546,4.049 2.528,3.974 "
+     id="polygon260"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="2.86,3.974 2.999,3.974 2.981,4.049 2.86,4.049 2.86,3.974 "
+     id="polygon262"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="2.86,3.974 2.999,3.974 2.981,4.049 2.86,4.049 2.86,3.974 "
+     id="polygon264"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.029999999"
+     height="0.029999999"
+     x="2.8829999"
+     y="3.997"
+     id="rect266"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.029999999"
+     height="0.029999999"
+     x="2.8829999"
+     y="3.997"
+     id="rect268"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="2.699,4.049 2.828,4.049 2.828,4.087 2.893,4.087 2.893,4.124 2.635,4.124 2.635,4.087 2.699,4.087 2.699,4.049 "
+     id="polygon270"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="2.699,4.049 2.828,4.049 2.828,4.087 2.893,4.087 2.893,4.124 2.635,4.124 2.635,4.087 2.699,4.087 2.699,4.049 "
+     id="polygon272"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.65899998"
+     height="0.495"
+     x="0.27900001"
+     y="3.52"
+     id="rect274"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.65899998"
+     height="0.495"
+     x="0.27900001"
+     y="3.52"
+     id="rect276"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.51700002"
+     height="0.34099999"
+     x="0.34999999"
+     y="3.592"
+     id="rect278"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="0.368,4.015 0.707,4.015 0.707,4.092 0.386,4.092 0.368,4.015 "
+     id="polygon280"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="0.368,4.015 0.707,4.015 0.707,4.092 0.386,4.092 0.368,4.015 "
+     id="polygon282"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="0.707,4.015 0.849,4.015 0.831,4.092 0.707,4.092 0.707,4.015 "
+     id="polygon284"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="0.707,4.015 0.849,4.015 0.831,4.092 0.707,4.092 0.707,4.015 "
+     id="polygon286"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.030999999"
+     height="0.030999999"
+     x="0.73000002"
+     y="4.0380001"
+     id="rect288"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.030999999"
+     height="0.030999999"
+     x="0.73000002"
+     y="4.0380001"
+     id="rect290"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="0.542,4.092 0.674,4.092 0.674,4.13 0.74,4.13 0.74,4.169 0.476,4.169 0.476,4.13 0.542,4.13 0.542,4.092 "
+     id="polygon292"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="0.542,4.092 0.674,4.092 0.674,4.13 0.74,4.13 0.74,4.169 0.476,4.169 0.476,4.13 0.542,4.13 0.542,4.092 "
+     id="polygon294"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.65899998"
+     height="0.49399999"
+     x="9.6879997"
+     y="3.527"
+     id="rect296"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.65899998"
+     height="0.49399999"
+     x="9.6879997"
+     y="3.527"
+     id="rect298"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.51599997"
+     height="0.34099999"
+     x="9.7589998"
+     y="3.599"
+     id="rect300"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="9.777,4.022 10.116,4.022 10.116,4.099 9.795,4.099 9.777,4.022 "
+     id="polygon302"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.777,4.022 10.116,4.022 10.116,4.099 9.795,4.099 9.777,4.022 "
+     id="polygon304"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="10.116,4.022 10.258,4.022 10.24,4.099 10.116,4.099 10.116,4.022 "
+     id="polygon306"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="10.116,4.022 10.258,4.022 10.24,4.099 10.116,4.099 10.116,4.022 "
+     id="polygon308"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.030999999"
+     height="0.030999999"
+     x="10.139"
+     y="4.0450001"
+     id="rect310"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.030999999"
+     height="0.030999999"
+     x="10.139"
+     y="4.0450001"
+     id="rect312"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="9.952,4.099 10.083,4.099 10.083,4.137 10.149,4.137 10.149,4.176 9.886,4.176 9.886,4.137 9.952,4.137 9.952,4.099 "
+     id="polygon314"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.952,4.099 10.083,4.099 10.083,4.137 10.149,4.137 10.149,4.176 9.886,4.176 9.886,4.137 9.952,4.137 9.952,4.099 "
+     id="polygon316"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.62300003"
+     height="0.46700001"
+     x="11.2"
+     y="3.5650001"
+     id="rect318"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62300003"
+     height="0.46700001"
+     x="11.2"
+     y="3.5650001"
+     id="rect320"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.48800001"
+     height="0.322"
+     x="11.268"
+     y="3.632"
+     id="rect322"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="11.285,4.032 11.605,4.032 11.605,4.105 11.302,4.105 11.285,4.032 "
+     id="polygon324"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="11.285,4.032 11.605,4.032 11.605,4.105 11.302,4.105 11.285,4.032 "
+     id="polygon326"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="11.605,4.032 11.739,4.032 11.722,4.105 11.605,4.105 11.605,4.032 "
+     id="polygon328"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="11.605,4.032 11.739,4.032 11.722,4.105 11.605,4.105 11.605,4.032 "
+     id="polygon330"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.028999999"
+     height="0.028999999"
+     x="11.627"
+     y="4.0539999"
+     id="rect332"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.028999999"
+     height="0.028999999"
+     x="11.627"
+     y="4.0539999"
+     id="rect334"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="11.449,4.105 11.574,4.105 11.574,4.141 11.636,4.141 11.636,4.177 11.387,4.177 11.387,4.141 11.449,4.141 11.449,4.105 "
+     id="polygon336"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="11.449,4.105 11.574,4.105 11.574,4.141 11.636,4.141 11.636,4.177 11.387,4.177 11.387,4.141 11.449,4.141 11.449,4.105 "
+     id="polygon338"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="3.803,3.759 3.763,3.775 3.645,4.072 3.645,4.22 3.704,4.27 4.574,4.27 4.634,4.22 4.634,4.072 4.515,3.775 4.475,3.759 3.803,3.759 "
+     id="polygon340"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="3.803,3.759 3.763,3.775 3.645,4.072 3.645,4.22 3.704,4.27 4.574,4.27 4.634,4.22 4.634,4.072 4.515,3.775 4.475,3.759 3.803,3.759 "
+     id="polygon342"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 3.665,4.023 L 3.704,4.039 L 4.574,4.039 L 4.614,4.023"
+     id="path344"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.574,4.039 L 4.634,4.072"
+     id="path346"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 3.645,4.072 L 3.704,4.039"
+     id="path348"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="3.922,3.446 3.902,3.841 4.376,3.841 4.357,3.446 3.922,3.446 "
+     id="polygon350"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="3.922,3.446 3.902,3.841 4.376,3.841 4.357,3.446 3.922,3.446 "
+     id="polygon352"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="3.843,3.841 3.803,3.957 4.475,3.957 4.436,3.841 3.843,3.841 "
+     id="polygon354"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="3.843,3.841 3.803,3.957 4.475,3.957 4.436,3.841 3.843,3.841 "
+     id="polygon356"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="3.8429999"
+     cy="4.0970001"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse358"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.8429999"
+     cy="4.0970001"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse360"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.941"
+     cy="4.0970001"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse362"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.941"
+     cy="4.0970001"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse364"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.04"
+     cy="4.0970001"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse366"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.04"
+     cy="4.0970001"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse368"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.8429999"
+     cy="4.138"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse370"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.8429999"
+     cy="4.138"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse372"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.941"
+     cy="4.138"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse374"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.941"
+     cy="4.138"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse376"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.04"
+     cy="4.138"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse378"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.04"
+     cy="4.138"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse380"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.8429999"
+     cy="4.1789999"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse382"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.8429999"
+     cy="4.1789999"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse384"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.941"
+     cy="4.1789999"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse386"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.941"
+     cy="4.1789999"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse388"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.04"
+     cy="4.1789999"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse390"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.04"
+     cy="4.1789999"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse392"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.8429999"
+     cy="4.2199998"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse394"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.8429999"
+     cy="4.2199998"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse396"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.941"
+     cy="4.2199998"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse398"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.941"
+     cy="4.2199998"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse400"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.04"
+     cy="4.2199998"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse402"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.04"
+     cy="4.2199998"
+     rx="0.0099999998"
+     ry="0.0099999998"
+     id="ellipse404"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.1389999"
+     cy="4.105"
+     rx="0.124"
+     ry="0.039999999"
+     id="ellipse406"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="4.1389999"
+     cy="4.105"
+     rx="0.124"
+     ry="0.039999999"
+     id="ellipse408"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.3860002"
+     cy="4.105"
+     rx="0.124"
+     ry="0.039999999"
+     id="ellipse410"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="4.3860002"
+     cy="4.105"
+     rx="0.124"
+     ry="0.039999999"
+     id="ellipse412"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <polygon
+     points="3.741,6.521 3.695,6.54 3.558,6.884 3.558,7.056 3.627,7.114 4.635,7.114 4.704,7.056 4.704,6.884 4.567,6.54 4.521,6.521 3.741,6.521 "
+     id="polygon414"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="3.741,6.521 3.695,6.54 3.558,6.884 3.558,7.056 3.627,7.114 4.635,7.114 4.704,7.056 4.704,6.884 4.567,6.54 4.521,6.521 3.741,6.521 "
+     id="polygon416"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 3.581,6.827 L 3.627,6.846 L 4.635,6.846 L 4.681,6.827"
+     id="path418"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.635,6.846 L 4.704,6.884"
+     id="path420"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 3.558,6.884 L 3.627,6.846"
+     id="path422"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="3.879,6.158 3.856,6.617 4.406,6.617 4.383,6.158 3.879,6.158 "
+     id="polygon424"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="3.879,6.158 3.856,6.617 4.406,6.617 4.383,6.158 3.879,6.158 "
+     id="polygon426"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="3.787,6.617 3.741,6.751 4.521,6.751 4.475,6.617 3.787,6.617 "
+     id="polygon428"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="3.787,6.617 3.741,6.751 4.521,6.751 4.475,6.617 3.787,6.617 "
+     id="polygon430"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="3.7869999"
+     cy="6.9130001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse432"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.7869999"
+     cy="6.9130001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse434"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.902"
+     cy="6.9130001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse436"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.902"
+     cy="6.9130001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse438"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.0159998"
+     cy="6.9130001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse440"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.0159998"
+     cy="6.9130001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse442"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.7869999"
+     cy="6.961"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse444"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.7869999"
+     cy="6.961"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse446"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.902"
+     cy="6.961"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse448"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.902"
+     cy="6.961"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse450"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.0159998"
+     cy="6.961"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse452"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.0159998"
+     cy="6.961"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse454"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.7869999"
+     cy="7.0079999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse456"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.7869999"
+     cy="7.0079999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse458"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.902"
+     cy="7.0079999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse460"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.902"
+     cy="7.0079999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse462"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.0159998"
+     cy="7.0079999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse464"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.0159998"
+     cy="7.0079999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse466"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.7869999"
+     cy="7.0560002"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse468"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.7869999"
+     cy="7.0560002"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse470"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="3.902"
+     cy="7.0560002"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse472"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="3.902"
+     cy="7.0560002"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse474"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.0159998"
+     cy="7.0560002"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse476"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.0159998"
+     cy="7.0560002"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse478"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.131"
+     cy="6.9219999"
+     rx="0.14300001"
+     ry="0.046"
+     id="ellipse480"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="4.131"
+     cy="6.9219999"
+     rx="0.14300001"
+     ry="0.046"
+     id="ellipse482"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.4180002"
+     cy="6.9219999"
+     rx="0.14300001"
+     ry="0.046"
+     id="ellipse484"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="4.4180002"
+     cy="6.9219999"
+     rx="0.14300001"
+     ry="0.046"
+     id="ellipse486"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <polygon
+     points="8.113,6.536 8.063,6.557 7.91,6.938 7.91,7.128 7.987,7.192 9.103,7.192 9.179,7.128 9.179,6.938 9.027,6.557 8.976,6.536 8.113,6.536 "
+     id="polygon488"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="8.113,6.536 8.063,6.557 7.91,6.938 7.91,7.128 7.987,7.192 9.103,7.192 9.179,7.128 9.179,6.938 9.027,6.557 8.976,6.536 8.113,6.536 "
+     id="polygon490"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.936,6.874 L 7.987,6.896 L 9.103,6.896 L 9.154,6.874"
+     id="path492"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 9.103,6.896 L 9.179,6.938"
+     id="path494"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.91,6.938 L 7.987,6.896"
+     id="path496"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="8.266,6.134 8.24,6.642 8.849,6.642 8.824,6.134 8.266,6.134 "
+     id="polygon498"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="8.266,6.134 8.24,6.642 8.849,6.642 8.824,6.134 8.266,6.134 "
+     id="polygon500"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="8.164,6.642 8.113,6.79 8.976,6.79 8.925,6.642 8.164,6.642 "
+     id="polygon502"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="8.164,6.642 8.113,6.79 8.976,6.79 8.925,6.642 8.164,6.642 "
+     id="polygon504"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="8.1639996"
+     cy="6.9699998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse506"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.1639996"
+     cy="6.9699998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse508"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.2910004"
+     cy="6.9699998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse510"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.2910004"
+     cy="6.9699998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse512"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.4180002"
+     cy="6.9699998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse514"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.4180002"
+     cy="6.9699998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse516"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.1639996"
+     cy="7.0229998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse518"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.1639996"
+     cy="7.0229998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse520"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.2910004"
+     cy="7.0229998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse522"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.2910004"
+     cy="7.0229998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse524"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.4180002"
+     cy="7.0229998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse526"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.4180002"
+     cy="7.0229998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse528"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.1639996"
+     cy="7.0749998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse530"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.1639996"
+     cy="7.0749998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse532"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.2910004"
+     cy="7.0749998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse534"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.2910004"
+     cy="7.0749998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse536"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.4180002"
+     cy="7.0749998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse538"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.4180002"
+     cy="7.0749998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse540"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.1639996"
+     cy="7.1279998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse542"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.1639996"
+     cy="7.1279998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse544"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.2910004"
+     cy="7.1279998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse546"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.2910004"
+     cy="7.1279998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse548"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.4180002"
+     cy="7.1279998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse550"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="8.4180002"
+     cy="7.1279998"
+     rx="0.013"
+     ry="0.013"
+     id="ellipse552"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.5450001"
+     cy="6.98"
+     rx="0.15899999"
+     ry="0.050999999"
+     id="ellipse554"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="8.5450001"
+     cy="6.98"
+     rx="0.15899999"
+     ry="0.050999999"
+     id="ellipse556"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="8.8620005"
+     cy="6.98"
+     rx="0.15899999"
+     ry="0.050999999"
+     id="ellipse558"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="8.8620005"
+     cy="6.98"
+     rx="0.15899999"
+     ry="0.050999999"
+     id="ellipse560"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <text
+     x="3.9879999"
+     y="1.613"
+     id="text562"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: BILLMORE</text>
+  <text
+     x="1.056"
+     y="5.6669998"
+     id="text564"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">192.168.1.0/24</text>
+  <text
+     x="9.4580002"
+     y="5.6199999"
+     id="text566"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">192.168.2.0/24</text>
+  <text
+     x="4.4000001"
+     y="5.6009998"
+     id="text568"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.10</text>
+  <text
+     x="4.4390001"
+     y="5.0139999"
+     id="text570"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.11</text>
+  <text
+     x="8.0030003"
+     y="5.5640001"
+     id="text572"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.10</text>
+  <text
+     x="7.2420001"
+     y="4.927"
+     id="text574"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.1</text>
+  <text
+     x="9.7089996"
+     y="6.026"
+     id="text576"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">IP via DHCP</text>
+  <text
+     x="3.9430001"
+     y="7.6009998"
+     id="text578"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj6</text>
+  <text
+     x="8.382"
+     y="7.6389999"
+     id="text580"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">qms</text>
+  <text
+     x="6.0440001"
+     y="2.602"
+     id="text582"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="5.967"
+     y="3.0020001"
+     id="text584"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">SLEETH</text>
+  <text
+     x="0.69599998"
+     y="2.615"
+     id="text586"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounting</text>
+  <text
+     x="9.6929998"
+     y="2.566"
+     id="text588"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Financial Services</text>
+  <text
+     x="0.63999999"
+     y="7.7909999"
+     id="text590"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">20 Users</text>
+  <text
+     x="10.799"
+     y="7.8039999"
+     id="text592"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">32 Users</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/ch7-dual-additive-LDAP-Ok.svg b/docs-xml/Samba3-ByExample/images/ch7-dual-additive-LDAP-Ok.svg
new file mode 100644
index 00000000000..78b735c3614
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/ch7-dual-additive-LDAP-Ok.svg
@@ -0,0 +1,143 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="14.175cm"
+   height="7.1500001cm"
+   viewBox="4.175 2.15 18.35 9.3"
+   id="svg2">
+  <defs
+     id="defs47" />
+  <rect
+     width="4.2249999"
+     height="1.825"
+     x="4.2249999"
+     y="4.4749999"
+     id="rect4"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.2249999"
+     height="1.825"
+     x="4.2249999"
+     y="4.4749999"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="6.1750002"
+     height="2.825"
+     x="12.1"
+     y="2.2"
+     id="rect8"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="6.1750002"
+     height="2.825"
+     x="12.1"
+     y="2.2"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="5.4169998"
+     y="5.5999999"
+     id="text12"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
+  <text
+     x="14.296"
+     y="3.0250001"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master</text>
+  <text
+     x="13.676"
+     y="3.825"
+     id="text16"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
+  <text
+     x="13.84"
+     y="4.625"
+     id="text18"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Directory A</text>
+  <line
+     x1="9"
+     y1="5.3790002"
+     x2="10.9"
+     y2="5.3499999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line20"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="8.996,5.129 8.5,5.387 9.004,5.629 8.996,5.129 "
+     id="polygon22"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <rect
+     width="6.1750002"
+     height="2.605"
+     x="12.125"
+     y="6.52"
+     id="rect24"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="6.1750002"
+     height="2.605"
+     x="12.125"
+     y="6.52"
+     id="rect26"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="14.575"
+     y="7.25"
+     id="text28"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">slave</text>
+  <text
+     x="13.776"
+     y="8.0500002"
+     id="text30"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
+  <text
+     x="13.941"
+     y="8.8500004"
+     id="text32"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Directory B</text>
+  <line
+     x1="11.55"
+     y1="3.618"
+     x2="10.925"
+     y2="3.625"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line34"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="11.553,3.868 12.05,3.613 11.547,3.368 11.553,3.868 "
+     id="polygon36"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="10.95"
+     y1="3.575"
+     x2="10.925"
+     y2="7.8499999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line38"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="11.575"
+     y1="7.8239999"
+     x2="10.95"
+     y2="7.8249998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line40"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="11.576,8.074 12.075,7.823 11.574,7.574 11.576,8.074 "
+     id="polygon42"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="14.331"
+     y="5.9749999"
+     id="text44"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">additive</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/ch7-dual-additive-LDAP.svg b/docs-xml/Samba3-ByExample/images/ch7-dual-additive-LDAP.svg
new file mode 100644
index 00000000000..ad952c29016
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/ch7-dual-additive-LDAP.svg
@@ -0,0 +1,153 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="13.05cm"
+   height="7.987cm"
+   viewBox="4.175 2.9 17.225 10.887"
+   id="svg2">
+  <defs
+     id="defs51" />
+  <rect
+     width="4.2249999"
+     height="1.825"
+     x="4.2249999"
+     y="4.4749999"
+     id="rect4"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.2249999"
+     height="1.825"
+     x="4.2249999"
+     y="4.4749999"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="12"
+     y="2.95"
+     id="rect8"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="12"
+     y="2.95"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="5.4169998"
+     y="5.5500002"
+     id="text12"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
+  <text
+     x="13.846"
+     y="3.7249999"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master</text>
+  <text
+     x="13.226"
+     y="4.5250001"
+     id="text16"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
+  <line
+     x1="9"
+     y1="5.3790002"
+     x2="10.9"
+     y2="5.3499999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="8.996,5.129 8.5,5.387 9.004,5.629 8.996,5.129 "
+     id="polygon20"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="11.998"
+     y="5.9450002"
+     id="rect22"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="11.998"
+     y="5.9450002"
+     id="rect24"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="14.15"
+     y="6.7249999"
+     id="text26"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">slave</text>
+  <text
+     x="13.351"
+     y="7.5250001"
+     id="text28"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
+  <line
+     x1="11.45"
+     y1="3.9119999"
+     x2="10.9"
+     y2="3.925"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line30"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="11.456,4.162 11.95,3.901 11.444,3.663 11.456,4.162 "
+     id="polygon32"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="10.925"
+     y1="3.925"
+     x2="10.95"
+     y2="6.9499998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line34"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="11.448"
+     y1="6.9099998"
+     x2="10.9"
+     y2="6.9250002"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line36"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="11.455,7.16 11.948,6.896 11.441,6.66 11.455,7.16 "
+     id="polygon38"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="13.659"
+     y="5.5749998"
+     id="text40"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">additive</text>
+  <text
+     x="8.6809998"
+     y="8.75"
+     id="text42"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">The LDAP backend consists of a</text>
+  <text
+     x="7.9250002"
+     y="9.3500004"
+     id="text44"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master and a slave for the same database.</text>
+  <text
+     x="8.7819996"
+     y="9.9499998"
+     id="text46"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">This is a broken implementation</text>
+  <text
+     x="9.0249996"
+     y="10.55"
+     id="text48"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">- accounts will be duplicated.</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/ch7-fail-overLDAP.svg b/docs-xml/Samba3-ByExample/images/ch7-fail-overLDAP.svg
new file mode 100644
index 00000000000..58af69ecabb
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/ch7-fail-overLDAP.svg
@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="13.098cm"
+   height="4.9000001cm"
+   viewBox="4.175 2.9 17.273 7.8"
+   id="svg2">
+  <defs
+     id="defs41" />
+  <rect
+     width="4.2249999"
+     height="1.825"
+     x="4.2249999"
+     y="4.4749999"
+     id="rect4"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.2249999"
+     height="1.825"
+     x="4.2249999"
+     y="4.4749999"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="12"
+     y="2.95"
+     id="rect8"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="12"
+     y="2.95"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="5.4169998"
+     y="5.5500002"
+     id="text12"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
+  <text
+     x="13.846"
+     y="3.7249999"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master</text>
+  <text
+     x="13.226"
+     y="4.5250001"
+     id="text16"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
+  <line
+     x1="8.9820004"
+     y1="4.875"
+     x2="11.518"
+     y2="3.813"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="8.886,4.644 8.521,5.068 9.079,5.106 8.886,4.644 "
+     id="polygon20"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="11.614,4.043 11.979,3.619 11.421,3.582 11.614,4.043 "
+     id="polygon22"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="12.047"
+     y="5.7449999"
+     id="rect24"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="12.047"
+     y="5.7449999"
+     id="rect26"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="14.1"
+     y="6.5500002"
+     id="text28"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">slave</text>
+  <text
+     x="13.301"
+     y="7.3499999"
+     id="text30"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
+  <line
+     x1="8.993"
+     y1="5.8610001"
+     x2="11.43"
+     y2="6.7340002"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.10,0.10"
+     id="line32"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <polygon
+     points="9.077,5.625 8.522,5.692 8.908,6.096 9.077,5.625 "
+     id="polygon34"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="11.345,6.97 11.9,6.903 11.514,6.499 11.345,6.97 "
+     id="polygon36"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="10.245"
+     y="6"
+     id="text38"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">fail-over</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/ch7-singleLDAP.svg b/docs-xml/Samba3-ByExample/images/ch7-singleLDAP.svg
new file mode 100644
index 00000000000..7155fd1ffee
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/ch7-singleLDAP.svg
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="12.75cm"
+   height="2.075cm"
+   viewBox="4.175 4.425 16.925 6.5"
+   id="svg2">
+  <defs
+     id="defs25" />
+  <rect
+     width="4.2249999"
+     height="1.825"
+     x="4.2249999"
+     y="4.4749999"
+     id="rect4"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.2249999"
+     height="1.825"
+     x="4.2249999"
+     y="4.4749999"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="11.7"
+     y="4.4749999"
+     id="rect8"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="5.1750002"
+     height="1.9"
+     x="11.7"
+     y="4.4749999"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="5.4169998"
+     y="5.5500002"
+     id="text12"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
+  <text
+     x="13.621"
+     y="5.25"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master</text>
+  <text
+     x="13.001"
+     y="6.0500002"
+     id="text16"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
+  <line
+     x1="9"
+     y1="5.3899999"
+     x2="11.05"
+     y2="5.3979998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="9.001,5.14 8.5,5.388 8.999,5.64 9.001,5.14 "
+     id="polygon20"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="11.049,5.648 11.55,5.4 11.051,5.148 11.049,5.648 "
+     id="polygon22"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/ch8-migration.svg b/docs-xml/Samba3-ByExample/images/ch8-migration.svg
new file mode 100644
index 00000000000..8656885b92b
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/ch8-migration.svg
@@ -0,0 +1,767 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="16.389cm"
+   height="11.635cm"
+   viewBox="3.227 3.533 19.617 15.168"
+   id="svg2">
+  <defs
+     id="defs221" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="4.746,10.964 4.746,12.225 18.667,12.225 18.667,11.050 "
+     id="polyline4"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.0599999"
+     height="4.8070002"
+     x="3.648"
+     y="5.744"
+     id="rect6"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="2.0599999"
+     height="4.8070002"
+     x="3.648"
+     y="5.744"
+     id="rect8"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.648"
+     height="0.54900002"
+     x="3.8540001"
+     y="6.033"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.648"
+     height="0.54900002"
+     x="3.8540001"
+     y="6.5819998"
+     id="rect12"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.648"
+     height="0.54900002"
+     x="3.8540001"
+     y="7.132"
+     id="rect14"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.648"
+     height="0.54900002"
+     x="3.8540001"
+     y="7.6810002"
+     id="rect16"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.03"
+     height="0.33000001"
+     x="3.8540001"
+     y="8.3400002"
+     id="rect18"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="5.3990002"
+     cy="8.3950005"
+     rx="0.071999997"
+     ry="0.071999997"
+     id="ellipse20"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="5.3990002"
+     cy="8.3950005"
+     rx="0.071999997"
+     ry="0.071999997"
+     id="ellipse22"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="5.3990002"
+     cy="8.6149998"
+     rx="0.071999997"
+     ry="0.071999997"
+     id="ellipse24"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="5.3990002"
+     cy="8.6149998"
+     rx="0.071999997"
+     ry="0.071999997"
+     id="ellipse26"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.24699999"
+     height="0.22"
+     x="4.987"
+     y="8.4499998"
+     id="rect28"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.24699999"
+     height="0.22"
+     x="4.987"
+     y="8.4499998"
+     id="rect30"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 3.991,9.109 L 3.991,10.311"
+     id="path32"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 4.334,9.109 L 4.334,10.311"
+     id="path34"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 4.678,9.109 L 4.678,10.311"
+     id="path36"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 5.021,9.109 L 5.021,10.311"
+     id="path38"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 5.364,9.109 L 5.364,10.311"
+     id="path40"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 5.708,9.109 L 5.708,10.311"
+     id="path42"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="3.236,10.964 3.648,10.14 3.648,10.552 5.708,10.552 5.708,10.14 6.257,10.964 3.236,10.964 "
+     id="polygon44"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="3.236,10.964 3.648,10.14 3.648,10.552 5.708,10.552 5.708,10.14 6.257,10.964 3.236,10.964 "
+     id="polygon46"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.8"
+     height="5.4000001"
+     x="17.767"
+     y="5.6500001"
+     id="rect48"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.8"
+     height="5.4000001"
+     x="17.767"
+     y="5.6500001"
+     id="rect50"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.8"
+     height="5.4000001"
+     x="17.767"
+     y="5.6500001"
+     id="rect52"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.4400001"
+     height="2.1600001"
+     x="17.947001"
+     y="5.8299999"
+     id="rect54"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.4400001"
+     height="2.1600001"
+     x="17.947001"
+     y="5.8299999"
+     id="rect56"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.4400001"
+     height="2.1600001"
+     x="17.947001"
+     y="5.8299999"
+     id="rect58"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.947001"
+     y1="6.1900001"
+     x2="19.386999"
+     y2="6.1900001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line60"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.386999"
+     y1="6.5500002"
+     x2="17.947001"
+     y2="6.5500002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line62"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.947001"
+     y1="6.9099998"
+     x2="19.386999"
+     y2="6.9099998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line64"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.947001"
+     y1="7.27"
+     x2="19.386999"
+     y2="7.27"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line66"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.386999"
+     y1="7.6300001"
+     x2="17.947001"
+     y2="7.6300001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line68"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.99000001"
+     height="0.54000002"
+     x="17.947001"
+     y="8.1700001"
+     id="rect70"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.99000001"
+     height="0.54000002"
+     x="17.947001"
+     y="8.1700001"
+     id="rect72"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.99000001"
+     height="0.54000002"
+     x="17.947001"
+     y="8.1700001"
+     id="rect74"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.767"
+     y1="9.0699997"
+     x2="19.566999"
+     y2="9.0699997"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line76"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.090000004"
+     height="0.090000004"
+     x="18.577"
+     y="9.25"
+     id="rect78"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.090000004"
+     height="0.090000004"
+     x="18.577"
+     y="9.25"
+     id="rect80"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.090000004"
+     height="0.090000004"
+     x="18.577"
+     y="9.25"
+     id="rect82"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.090000004"
+     height="0.090000004"
+     x="18.937"
+     y="9.25"
+     id="rect84"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.090000004"
+     height="0.090000004"
+     x="18.937"
+     y="9.25"
+     id="rect86"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.090000004"
+     height="0.090000004"
+     x="18.937"
+     y="9.25"
+     id="rect88"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.090000004"
+     height="0.090000004"
+     x="19.297001"
+     y="9.25"
+     id="rect90"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.090000004"
+     height="0.090000004"
+     x="19.297001"
+     y="9.25"
+     id="rect92"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.090000004"
+     height="0.090000004"
+     x="19.297001"
+     y="9.25"
+     id="rect94"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.18000001"
+     height="0.18000001"
+     x="19.207001"
+     y="8.71"
+     id="rect96"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.18000001"
+     height="0.18000001"
+     x="19.207001"
+     y="8.71"
+     id="rect98"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.18000001"
+     height="0.18000001"
+     x="19.207001"
+     y="8.71"
+     id="rect100"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.947001"
+     y1="8.4399996"
+     x2="18.937"
+     y2="8.4399996"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line102"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.27000001"
+     height="0.27000001"
+     x="17.947001"
+     y="9.1599998"
+     id="rect104"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.27000001"
+     height="0.27000001"
+     x="17.947001"
+     y="9.1599998"
+     id="rect106"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.27000001"
+     height="0.27000001"
+     x="17.947001"
+     y="9.1599998"
+     id="rect108"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.26"
+     height="0.090000004"
+     x="18.037001"
+     y="7.7199998"
+     id="rect110"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.26"
+     height="0.090000004"
+     x="18.037001"
+     y="7.7199998"
+     id="rect112"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.26"
+     height="0.090000004"
+     x="18.037001"
+     y="7.7199998"
+     id="rect114"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="18.037001"
+     y1="8.2600002"
+     x2="18.847"
+     y2="8.2600002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line116"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="18.847"
+     y1="8.3500004"
+     x2="18.757"
+     y2="8.3500004"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line118"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="18.037001"
+     y1="8.3500004"
+     x2="18.127001"
+     y2="8.3500004"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line120"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.44999999"
+     height="0.090000004"
+     x="18.216999"
+     y="8.2600002"
+     id="rect122"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.44999999"
+     height="0.090000004"
+     x="18.216999"
+     y="8.2600002"
+     id="rect124"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.44999999"
+     height="0.090000004"
+     x="18.216999"
+     y="8.2600002"
+     id="rect126"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="18.037001"
+     y1="7.9000001"
+     x2="18.127001"
+     y2="7.9000001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line128"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="18.216999"
+     y1="7.9000001"
+     x2="18.306999"
+     y2="7.9000001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line130"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.117001"
+     y1="7.9000001"
+     x2="19.297001"
+     y2="7.9000001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line132"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.857"
+     y1="10.96"
+     x2="19.476999"
+     y2="10.96"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line134"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.476999"
+     y1="10.87"
+     x2="17.857"
+     y2="10.87"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.857"
+     y1="10.78"
+     x2="19.476999"
+     y2="10.78"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.476999"
+     y1="10.69"
+     x2="17.857"
+     y2="10.69"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line140"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.857"
+     y1="10.6"
+     x2="19.476999"
+     y2="10.6"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line142"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.476999"
+     y1="10.51"
+     x2="17.857"
+     y2="10.51"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line144"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.857"
+     y1="10.42"
+     x2="19.476999"
+     y2="10.42"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line146"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.476999"
+     y1="10.33"
+     x2="17.857"
+     y2="10.33"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line148"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.857"
+     y1="10.24"
+     x2="19.476999"
+     y2="10.24"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line150"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.476999"
+     y1="10.15"
+     x2="17.857"
+     y2="10.15"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line152"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.857"
+     y1="10.06"
+     x2="19.476999"
+     y2="10.06"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line154"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.476999"
+     y1="9.9700003"
+     x2="17.857"
+     y2="9.9700003"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line156"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.857"
+     y1="9.8800001"
+     x2="19.476999"
+     y2="9.8800001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line158"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.476999"
+     y1="9.79"
+     x2="17.857"
+     y2="9.79"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line160"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="2.7190001"
+     height="2.3989999"
+     x="6.5500002"
+     y="6.1869998"
+     id="rect162"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="7.9089999"
+     cy="8.585"
+     rx="1.359"
+     ry="0.40000001"
+     id="ellipse164"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="7.9089999"
+     cy="6.1869998"
+     rx="1.359"
+     ry="0.40000001"
+     id="ellipse166"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="7.9089999"
+     cy="6.1869998"
+     rx="1.359"
+     ry="0.40000001"
+     id="ellipse168"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 9.269,6.187 L 9.269,8.585 C 9.269,8.806 8.66,8.985 7.909,8.985 C 7.159,8.985 6.55,8.806 6.55,8.585 L 6.55,6.187"
+     id="path170"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.7190001"
+     height="2.3989999"
+     x="14.112"
+     y="6.1999998"
+     id="rect172"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="15.472"
+     cy="8.599"
+     rx="1.359"
+     ry="0.40000001"
+     id="ellipse174"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="15.472"
+     cy="6.1999998"
+     rx="1.359"
+     ry="0.40000001"
+     id="ellipse176"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="15.472"
+     cy="6.1999998"
+     rx="1.359"
+     ry="0.40000001"
+     id="ellipse178"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 16.831,6.2 L 16.831,8.599 C 16.831,8.82 16.223,8.999 15.472,8.999 C 14.721,8.999 14.112,8.82 14.112,8.599 L 14.112,6.2"
+     id="path180"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.7249999"
+     y1="7.3499999"
+     x2="6.5250001"
+     y2="7.3499999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line182"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.825001"
+     y1="7.4000001"
+     x2="17.75"
+     y2="7.375"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line184"
+     style="stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 8.65,9.2 C 9.0031969,10.514524 10.174957,11.443114 11.535409,11.486614 C 12.89586,11.530113 14.124549,10.678275 14.561,9.389"
+     id="path186"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="14.713,9.830 14.597,9.283 14.229,9.704 "
+     id="polyline188"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7.02"
+     y="4.9749999"
+     id="text190"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NT4 Registry</text>
+  <text
+     x="7.691"
+     y="5.5749998"
+     id="text192"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">SAM</text>
+  <text
+     x="13.871"
+     y="4.9250002"
+     id="text194"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba SAM</text>
+  <text
+     x="13.221"
+     y="5.5250001"
+     id="text196"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(ldapsam or tdbsam)</text>
+  <text
+     x="4.2259998"
+     y="4.0250001"
+     id="text198"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NT4</text>
+  <text
+     x="4.1719999"
+     y="4.8249998"
+     id="text200"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC</text>
+  <text
+     x="17.992001"
+     y="4"
+     id="text202"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
+  <text
+     x="18.407"
+     y="4.8000002"
+     id="text204"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DC</text>
+  <text
+     x="5.8540001"
+     y="13.625"
+     id="text206"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">net rpc vampire</text>
+  <text
+     x="5.5139999"
+     y="14.325"
+     id="text208"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Migration migrates:</text>
+  <text
+     x="14.664"
+     y="13.375"
+     id="text210"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">User Accounts</text>
+  <text
+     x="14.557"
+     y="14.075"
+     id="text212"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain Groups</text>
+  <text
+     x="14.311"
+     y="14.775"
+     id="text214"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Machine Accounts</text>
+  <line
+     x1="10.725"
+     y1="13.8"
+     x2="12.25"
+     y2="13.818"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line216"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.247,14.068 12.75,13.824 12.253,13.568 12.247,14.068 "
+     id="polygon218"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap4-net.svg b/docs-xml/Samba3-ByExample/images/chap4-net.svg
new file mode 100644
index 00000000000..88d16bd90d3
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap4-net.svg
@@ -0,0 +1,2148 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="21.725cm"
+   height="12.513cm"
+   viewBox="-0.013 1.735 21.712 14.247"
+   id="svg2">
+  <defs
+     id="defs719" />
+  <rect
+     width="7.8249998"
+     height="8.085"
+     x="0.31200001"
+     y="3.6170001"
+     id="rect4"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.312,3.617 C 0.14631458,3.617 0.012,3.7513146 0.012,3.917"
+     id="path6"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 8.437,3.917 C 8.437,3.7513146 8.3026854,3.617 8.137,3.617"
+     id="path8"
+     style="fill:#ededed;stroke:none" />
+  <rect
+     width="8.4250002"
+     height="7.4850001"
+     x="0.012"
+     y="3.9170001"
+     id="rect10"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.012,11.402 C 0.012,11.567685 0.14631458,11.702 0.312,11.702"
+     id="path12"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 8.137,11.702 C 8.3026854,11.702 8.437,11.567685 8.437,11.402"
+     id="path14"
+     style="fill:#ededed;stroke:none" />
+  <line
+     x1="0.31200001"
+     y1="3.6170001"
+     x2="8.1370001"
+     y2="3.6170001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.31200001"
+     y1="11.702"
+     x2="8.1370001"
+     y2="11.702"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.312,3.617 C 0.14631458,3.617 0.012,3.7513146 0.012,3.917"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 8.437,3.917 C 8.437,3.7513146 8.3026854,3.617 8.137,3.617"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.012"
+     y1="3.9170001"
+     x2="0.012"
+     y2="11.402"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="8.4370003"
+     y1="3.9170001"
+     x2="8.4370003"
+     y2="11.402"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.012,11.402 C 0.012,11.567685 0.14631458,11.702 0.312,11.702"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 8.137,11.702 C 8.3026854,11.702 8.437,11.567685 8.437,11.402"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="8.3249998"
+     height="8.1350002"
+     x="13.062"
+     y="3.5420001"
+     id="rect32"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 13.062,3.542 C 12.896315,3.542 12.762,3.6763146 12.762,3.842"
+     id="path34"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 21.688,3.842 C 21.688,3.7622615 21.656256,3.6858034 21.599779,3.6295136 C 21.543301,3.5732239 21.466738,3.5417342 21.387,3.542"
+     id="path36"
+     style="fill:#ededed;stroke:none" />
+  <rect
+     width="8.9250002"
+     height="7.5349998"
+     x="12.762"
+     y="3.842"
+     id="rect38"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.762,11.377 C 12.762,11.542685 12.896315,11.677 13.062,11.677"
+     id="path40"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 21.387,11.677 C 21.466738,11.677266 21.543301,11.645776 21.599779,11.589486 C 21.656256,11.533197 21.688,11.456739 21.688,11.377"
+     id="path42"
+     style="fill:#ededed;stroke:none" />
+  <line
+     x1="13.062"
+     y1="3.5420001"
+     x2="21.386999"
+     y2="3.5420001"
+     stroke="#070707"
+     stroke-width="0.050"
+     id="line44"
+     style="stroke:#070707;stroke-width:0.05" />
+  <line
+     x1="13.062"
+     y1="11.677"
+     x2="21.386999"
+     y2="11.677"
+     stroke="#070707"
+     stroke-width="0.050"
+     id="line46"
+     style="stroke:#070707;stroke-width:0.05" />
+  <path
+     d="M 13.062,3.542 C 12.896315,3.542 12.762,3.6763146 12.762,3.842"
+     id="path48"
+     style="fill:none;stroke:#070707;stroke-width:0.05" />
+  <path
+     d="M 21.688,3.842 C 21.688,3.7622615 21.656256,3.6858034 21.599779,3.6295136 C 21.543301,3.5732239 21.466738,3.5417342 21.387,3.542"
+     id="path50"
+     style="fill:none;stroke:#070707;stroke-width:0.05" />
+  <line
+     x1="12.762"
+     y1="3.842"
+     x2="12.762"
+     y2="11.377"
+     stroke="#070707"
+     stroke-width="0.050"
+     id="line52"
+     style="stroke:#070707;stroke-width:0.05" />
+  <line
+     x1="21.688"
+     y1="3.842"
+     x2="21.688"
+     y2="11.377"
+     stroke="#070707"
+     stroke-width="0.050"
+     id="line54"
+     style="stroke:#070707;stroke-width:0.05" />
+  <path
+     d="M 12.762,11.377 C 12.762,11.542685 12.896315,11.677 13.062,11.677"
+     id="path56"
+     style="fill:none;stroke:#070707;stroke-width:0.05" />
+  <path
+     d="M 21.387,11.677 C 21.466738,11.677266 21.543301,11.645776 21.599779,11.589486 C 21.656256,11.533197 21.688,11.456739 21.688,11.377"
+     id="path58"
+     style="fill:none;stroke:#070707;stroke-width:0.05" />
+  <rect
+     width="1.077"
+     height="2.5120001"
+     x="10.001"
+     y="5.0110002"
+     id="rect60"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.077"
+     height="2.5120001"
+     x="10.001"
+     y="5.0110002"
+     id="rect62"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="0.861"
+     height="0.287"
+     x="10.108"
+     y="5.1620002"
+     id="rect64"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.861"
+     height="0.287"
+     x="10.108"
+     y="5.4489999"
+     id="rect66"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.861"
+     height="0.287"
+     x="10.108"
+     y="5.7360001"
+     id="rect68"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.861"
+     height="0.287"
+     x="10.108"
+     y="6.0229998"
+     id="rect70"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.53799999"
+     height="0.17200001"
+     x="10.108"
+     y="6.368"
+     id="rect72"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="10.916"
+     cy="6.3969998"
+     rx="0.037999999"
+     ry="0.037999999"
+     id="ellipse74"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="10.916"
+     cy="6.3969998"
+     rx="0.037999999"
+     ry="0.037999999"
+     id="ellipse76"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="10.916"
+     cy="6.5110002"
+     rx="0.037999999"
+     ry="0.037999999"
+     id="ellipse78"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="10.916"
+     cy="6.5110002"
+     rx="0.037999999"
+     ry="0.037999999"
+     id="ellipse80"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.12899999"
+     height="0.115"
+     x="10.701"
+     y="6.4250002"
+     id="rect82"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.12899999"
+     height="0.115"
+     x="10.701"
+     y="6.4250002"
+     id="rect84"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.18,6.77 L 10.18,7.398"
+     id="path86"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.36,6.77 L 10.36,7.398"
+     id="path88"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.539,6.77 L 10.539,7.398"
+     id="path90"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.719,6.77 L 10.719,7.398"
+     id="path92"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.898,6.77 L 10.898,7.398"
+     id="path94"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 11.077,6.77 L 11.077,7.398"
+     id="path96"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="9.786,7.739 10.001,7.308 10.001,7.523 11.077,7.523 11.077,7.308 11.364,7.739 9.786,7.739 "
+     id="polygon98"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="9.786,7.739 10.001,7.308 10.001,7.523 11.077,7.523 11.077,7.308 11.364,7.739 9.786,7.739 "
+     id="polygon100"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.423"
+     y1="7.1059999"
+     x2="10.025"
+     y2="7.0999999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line102"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="2.687"
+     y1="7.105"
+     x2="2.688"
+     y2="8.1049995"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line104"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="2.6919999"
+     y1="7.105"
+     x2="2.691"
+     y2="6.0669999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line106"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.1170001"
+     y1="7.1030002"
+     x2="5.1170001"
+     y2="8.1029997"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line108"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.1300001"
+     y1="7.1030002"
+     x2="5.1300001"
+     y2="6.119"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line110"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="7.572"
+     y1="7.1020002"
+     x2="7.572"
+     y2="8.0959997"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line112"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="7.566"
+     y1="7.1020002"
+     x2="7.5650001"
+     y2="6.2249999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line114"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="11.05"
+     y1="7.0749998"
+     x2="20.325001"
+     y2="7.0500002"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line116"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.747"
+     y1="7.0679998"
+     x2="13.75"
+     y2="8.125"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line118"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.74"
+     y1="7.0679998"
+     x2="13.737"
+     y2="6.0840001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line120"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.297001"
+     y1="7.0609999"
+     x2="16.299999"
+     y2="8.0749998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line122"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.306999"
+     y1="7.0609999"
+     x2="16.305"
+     y2="6.1690001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line124"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.896999"
+     y1="7.0539999"
+     x2="18.9"
+     y2="8.0249996"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line126"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.907"
+     y1="7.0539999"
+     x2="18.905001"
+     y2="6.0939999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line128"
+     style="stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 9.39,12.232 C 8.983,12.222 8.194,12.424 8.305,12.856 C 8.416,13.288 8.946,13.384 9.168,13.259 C 9.39,13.134 8.823,13.864 9.907,14.056 C 10.992,14.247 11.547,13.94 11.386,13.72 C 11.226,13.499 12.335,14.238 12.853,13.816 C 13.371,13.393 12.323,12.99 12.545,13.048 C 12.767,13.105 13.445,13.029 13.223,12.309 C 13.001,11.589 11.004,12.145 11.226,12.04 C 11.448,11.934 10.893,11.406 10.203,11.512 C 9.513,11.618 9.464,11.809 9.39,12.231 L 9.39,12.232"
+     id="path130"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 9.39,12.232 C 8.983,12.222 8.194,12.424 8.305,12.856 C 8.416,13.288 8.946,13.384 9.168,13.259 C 9.39,13.134 8.823,13.864 9.907,14.056 C 10.992,14.247 11.547,13.94 11.386,13.72 C 11.226,13.499 12.335,14.238 12.853,13.816 C 13.371,13.393 12.323,12.99 12.545,13.048 C 12.767,13.105 13.445,13.029 13.223,12.309 C 13.001,11.589 11.004,12.145 11.226,12.04 C 11.448,11.934 10.893,11.406 10.203,11.512 C 9.513,11.618 9.464,11.809 9.39,12.231 L 9.39,12.232"
+     id="path132"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="10.353"
+     y="12.927"
+     id="text134"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
+  <line
+     x1="10.562"
+     y1="11.552"
+     x2="10.575"
+     y2="7.7389998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="2.1489999"
+     y="5"
+     id="rect138"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="2.1489999"
+     y="5"
+     id="rect140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="2.266"
+     y="5.118"
+     id="rect142"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="2.296,5.814 2.854,5.814 2.854,5.94 2.325,5.94 2.296,5.814 "
+     id="polygon144"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="2.296,5.814 2.854,5.814 2.854,5.94 2.325,5.94 2.296,5.814 "
+     id="polygon146"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="2.854,5.814 3.087,5.814 3.057,5.94 2.854,5.94 2.854,5.814 "
+     id="polygon148"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="2.854,5.814 3.087,5.814 3.057,5.94 2.854,5.94 2.854,5.814 "
+     id="polygon150"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="2.892"
+     y="5.8520002"
+     id="rect152"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="2.892"
+     y="5.8520002"
+     id="rect154"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="2.583,5.94 2.8,5.94 2.8,6.003 2.908,6.003 2.908,6.067 2.474,6.067 2.474,6.003 2.583,6.003 2.583,5.94 "
+     id="polygon156"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="2.583,5.94 2.8,5.94 2.8,6.003 2.908,6.003 2.908,6.067 2.474,6.067 2.474,6.003 2.583,6.003 2.583,5.94 "
+     id="polygon158"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="18.337"
+     y="8.0270004"
+     id="rect160"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="18.337"
+     y="8.0270004"
+     id="rect162"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="18.455"
+     y="8.1450005"
+     id="rect164"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.484,8.841 19.042,8.841 19.042,8.967 18.514,8.967 18.484,8.841 "
+     id="polygon166"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.484,8.841 19.042,8.841 19.042,8.967 18.514,8.967 18.484,8.841 "
+     id="polygon168"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.042,8.841 19.275,8.841 19.246,8.967 19.042,8.967 19.042,8.841 "
+     id="polygon170"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.042,8.841 19.275,8.841 19.246,8.967 19.042,8.967 19.042,8.841 "
+     id="polygon172"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="19.08"
+     y="8.8789997"
+     id="rect174"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="19.08"
+     y="8.8789997"
+     id="rect176"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.771,8.967 18.988,8.967 18.988,9.031 19.097,9.031 19.097,9.094 18.663,9.094 18.663,9.031 18.771,9.031 18.771,8.967 "
+     id="polygon178"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.771,8.967 18.988,8.967 18.988,9.031 19.097,9.031 19.097,9.094 18.663,9.094 18.663,9.031 18.771,9.031 18.771,8.967 "
+     id="polygon180"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="15.737"
+     y="8.0530005"
+     id="rect182"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="15.737"
+     y="8.0530005"
+     id="rect184"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="15.855"
+     y="8.1700001"
+     id="rect186"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="15.884,8.866 16.442,8.866 16.442,8.992 15.914,8.992 15.884,8.866 "
+     id="polygon188"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.884,8.866 16.442,8.866 16.442,8.992 15.914,8.992 15.884,8.866 "
+     id="polygon190"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.442,8.866 16.675,8.866 16.646,8.992 16.442,8.992 16.442,8.866 "
+     id="polygon192"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.442,8.866 16.675,8.866 16.646,8.992 16.442,8.992 16.442,8.866 "
+     id="polygon194"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="16.48"
+     y="8.9040003"
+     id="rect196"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="16.48"
+     y="8.9040003"
+     id="rect198"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.171,8.992 16.388,8.992 16.388,9.056 16.497,9.056 16.497,9.119 16.063,9.119 16.063,9.056 16.171,9.056 16.171,8.992 "
+     id="polygon200"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.171,8.992 16.388,8.992 16.388,9.056 16.497,9.056 16.497,9.119 16.063,9.119 16.063,9.056 16.171,9.056 16.171,8.992 "
+     id="polygon202"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="18.362"
+     y="5.027"
+     id="rect204"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="18.362"
+     y="5.027"
+     id="rect206"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="18.48"
+     y="5.145"
+     id="rect208"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.509,5.841 19.067,5.841 19.067,5.967 18.539,5.967 18.509,5.841 "
+     id="polygon210"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.509,5.841 19.067,5.841 19.067,5.967 18.539,5.967 18.509,5.841 "
+     id="polygon212"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.067,5.841 19.3,5.841 19.271,5.967 19.067,5.967 19.067,5.841 "
+     id="polygon214"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.067,5.841 19.3,5.841 19.271,5.967 19.067,5.967 19.067,5.841 "
+     id="polygon216"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="19.105"
+     y="5.8790002"
+     id="rect218"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="19.105"
+     y="5.8790002"
+     id="rect220"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.796,5.967 19.013,5.967 19.013,6.031 19.122,6.031 19.122,6.094 18.688,6.094 18.688,6.031 18.796,6.031 18.796,5.967 "
+     id="polygon222"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.796,5.967 19.013,5.967 19.013,6.031 19.122,6.031 19.122,6.094 18.688,6.094 18.688,6.031 18.796,6.031 18.796,5.967 "
+     id="polygon224"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="15.762"
+     y="5.1030002"
+     id="rect226"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="15.762"
+     y="5.1030002"
+     id="rect228"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="15.88"
+     y="5.2199998"
+     id="rect230"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="15.909,5.916 16.467,5.916 16.467,6.042 15.939,6.042 15.909,5.916 "
+     id="polygon232"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.909,5.916 16.467,5.916 16.467,6.042 15.939,6.042 15.909,5.916 "
+     id="polygon234"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.467,5.916 16.7,5.916 16.671,6.042 16.467,6.042 16.467,5.916 "
+     id="polygon236"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.467,5.916 16.7,5.916 16.671,6.042 16.467,6.042 16.467,5.916 "
+     id="polygon238"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="16.504999"
+     y="5.954"
+     id="rect240"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="16.504999"
+     y="5.954"
+     id="rect242"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.196,6.042 16.413,6.042 16.413,6.106 16.522,6.106 16.522,6.169 16.088,6.169 16.088,6.106 16.196,6.106 16.196,6.042 "
+     id="polygon244"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.196,6.042 16.413,6.042 16.413,6.106 16.522,6.106 16.522,6.169 16.088,6.169 16.088,6.106 16.196,6.106 16.196,6.042 "
+     id="polygon246"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="4.5869999"
+     y="5.053"
+     id="rect248"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="4.5869999"
+     y="5.053"
+     id="rect250"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="4.7049999"
+     y="5.1700001"
+     id="rect252"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="4.734,5.866 5.292,5.866 5.292,5.992 4.764,5.992 4.734,5.866 "
+     id="polygon254"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="4.734,5.866 5.292,5.866 5.292,5.992 4.764,5.992 4.734,5.866 "
+     id="polygon256"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="5.292,5.866 5.525,5.866 5.496,5.992 5.292,5.992 5.292,5.866 "
+     id="polygon258"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.292,5.866 5.525,5.866 5.496,5.992 5.292,5.992 5.292,5.866 "
+     id="polygon260"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="5.3299999"
+     y="5.9039998"
+     id="rect262"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="5.3299999"
+     y="5.9039998"
+     id="rect264"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="5.021,5.992 5.238,5.992 5.238,6.056 5.347,6.056 5.347,6.119 4.913,6.119 4.913,6.056 5.021,6.056 5.021,5.992 "
+     id="polygon266"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.021,5.992 5.238,5.992 5.238,6.056 5.347,6.056 5.347,6.119 4.913,6.119 4.913,6.056 5.021,6.056 5.021,5.992 "
+     id="polygon268"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="4.5619998"
+     y="8.0530005"
+     id="rect270"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="4.5619998"
+     y="8.0530005"
+     id="rect272"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="4.6799998"
+     y="8.1700001"
+     id="rect274"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="4.709,8.866 5.267,8.866 5.267,8.992 4.739,8.992 4.709,8.866 "
+     id="polygon276"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="4.709,8.866 5.267,8.866 5.267,8.992 4.739,8.992 4.709,8.866 "
+     id="polygon278"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="5.267,8.866 5.5,8.866 5.471,8.992 5.267,8.992 5.267,8.866 "
+     id="polygon280"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.267,8.866 5.5,8.866 5.471,8.992 5.267,8.992 5.267,8.866 "
+     id="polygon282"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="5.3049998"
+     y="8.9040003"
+     id="rect284"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="5.3049998"
+     y="8.9040003"
+     id="rect286"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="4.996,8.992 5.213,8.992 5.213,9.056 5.322,9.056 5.322,9.119 4.888,9.119 4.888,9.056 4.996,9.056 4.996,8.992 "
+     id="polygon288"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="4.996,8.992 5.213,8.992 5.213,9.056 5.322,9.056 5.322,9.119 4.888,9.119 4.888,9.056 4.996,9.056 4.996,8.992 "
+     id="polygon290"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="2.1619999"
+     y="8.1020002"
+     id="rect292"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="2.1619999"
+     y="8.1020002"
+     id="rect294"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="2.28"
+     y="8.2200003"
+     id="rect296"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="2.309,8.916 2.867,8.916 2.867,9.042 2.339,9.042 2.309,8.916 "
+     id="polygon298"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="2.309,8.916 2.867,8.916 2.867,9.042 2.339,9.042 2.309,8.916 "
+     id="polygon300"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="2.867,8.916 3.1,8.916 3.071,9.042 2.867,9.042 2.867,8.916 "
+     id="polygon302"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="2.867,8.916 3.1,8.916 3.071,9.042 2.867,9.042 2.867,8.916 "
+     id="polygon304"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="2.905"
+     y="8.9540005"
+     id="rect306"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="2.905"
+     y="8.9540005"
+     id="rect308"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="2.596,9.042 2.813,9.042 2.813,9.106 2.922,9.106 2.922,9.169 2.488,9.169 2.488,9.106 2.596,9.106 2.596,9.042 "
+     id="polygon310"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="2.596,9.042 2.813,9.042 2.813,9.106 2.922,9.106 2.922,9.169 2.488,9.169 2.488,9.106 2.596,9.106 2.596,9.042 "
+     id="polygon312"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="20.287001"
+     y="6.5770001"
+     id="rect314"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="20.287001"
+     y="6.5770001"
+     id="rect316"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="20.405001"
+     y="6.6950002"
+     id="rect318"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="20.434,7.391 20.992,7.391 20.992,7.517 20.464,7.517 20.434,7.391 "
+     id="polygon320"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.434,7.391 20.992,7.391 20.992,7.517 20.464,7.517 20.434,7.391 "
+     id="polygon322"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="20.992,7.391 21.225,7.391 21.196,7.517 20.992,7.517 20.992,7.391 "
+     id="polygon324"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.992,7.391 21.225,7.391 21.196,7.517 20.992,7.517 20.992,7.391 "
+     id="polygon326"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="21.030001"
+     y="7.4289999"
+     id="rect328"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="21.030001"
+     y="7.4289999"
+     id="rect330"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="20.721,7.517 20.938,7.517 20.938,7.581 21.047,7.581 21.047,7.644 20.613,7.644 20.613,7.581 20.721,7.581 20.721,7.517 "
+     id="polygon332"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.721,7.517 20.938,7.517 20.938,7.581 21.047,7.581 21.047,7.644 20.613,7.644 20.613,7.581 20.721,7.581 20.721,7.517 "
+     id="polygon334"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="0.31200001"
+     y="6.6030002"
+     id="rect336"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.085"
+     height="0.81300002"
+     x="0.31200001"
+     y="6.6030002"
+     id="rect338"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.85000002"
+     height="0.56"
+     x="0.43000001"
+     y="6.7199998"
+     id="rect340"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="0.459,7.416 1.017,7.416 1.017,7.542 0.489,7.542 0.459,7.416 "
+     id="polygon342"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="0.459,7.416 1.017,7.416 1.017,7.542 0.489,7.542 0.459,7.416 "
+     id="polygon344"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="1.017,7.416 1.25,7.416 1.221,7.542 1.017,7.542 1.017,7.416 "
+     id="polygon346"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="1.017,7.416 1.25,7.416 1.221,7.542 1.017,7.542 1.017,7.416 "
+     id="polygon348"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="1.0549999"
+     y="7.454"
+     id="rect350"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050999999"
+     height="0.050999999"
+     x="1.0549999"
+     y="7.454"
+     id="rect352"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="0.746,7.542 0.963,7.542 0.963,7.606 1.072,7.606 1.072,7.669 0.638,7.669 0.638,7.606 0.746,7.606 0.746,7.542 "
+     id="polygon354"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="0.746,7.542 0.963,7.542 0.963,7.606 1.072,7.606 1.072,7.669 0.638,7.669 0.638,7.606 0.746,7.606 0.746,7.542 "
+     id="polygon356"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="7.201,5.672 7.159,5.69 7.03,6.011 7.03,6.171 7.094,6.225 8.036,6.225 8.1,6.171 8.1,6.011 7.972,5.69 7.929,5.672 7.201,5.672 "
+     id="polygon358"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="7.201,5.672 7.159,5.69 7.03,6.011 7.03,6.171 7.094,6.225 8.036,6.225 8.1,6.171 8.1,6.011 7.972,5.69 7.929,5.672 7.201,5.672 "
+     id="polygon360"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.052,5.957 L 7.094,5.975 L 8.036,5.975 L 8.079,5.957"
+     id="path362"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 8.036,5.975 L 8.1,6.011"
+     id="path364"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.03,6.011 L 7.094,5.975"
+     id="path366"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="7.33,5.333 7.308,5.761 7.822,5.761 7.801,5.333 7.33,5.333 "
+     id="polygon368"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="7.33,5.333 7.308,5.761 7.822,5.761 7.801,5.333 7.33,5.333 "
+     id="polygon370"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="7.244,5.761 7.201,5.886 7.929,5.886 7.886,5.761 7.244,5.761 "
+     id="polygon372"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="7.244,5.761 7.201,5.886 7.929,5.886 7.886,5.761 7.244,5.761 "
+     id="polygon374"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="7.244"
+     cy="6.0380001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse376"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.244"
+     cy="6.0380001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse378"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.3509998"
+     cy="6.0380001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse380"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.3509998"
+     cy="6.0380001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse382"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.4580002"
+     cy="6.0380001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse384"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.4580002"
+     cy="6.0380001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse386"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.244"
+     cy="6.0819998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse388"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.244"
+     cy="6.0819998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse390"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.3509998"
+     cy="6.0819998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse392"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.3509998"
+     cy="6.0819998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse394"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.4580002"
+     cy="6.0819998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse396"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.4580002"
+     cy="6.0819998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse398"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.244"
+     cy="6.1269999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse400"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.244"
+     cy="6.1269999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse402"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.3509998"
+     cy="6.1269999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse404"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.3509998"
+     cy="6.1269999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse406"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.4580002"
+     cy="6.1269999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse408"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.4580002"
+     cy="6.1269999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse410"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.244"
+     cy="6.171"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse412"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.244"
+     cy="6.171"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse414"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.3509998"
+     cy="6.171"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse416"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.3509998"
+     cy="6.171"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse418"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.4580002"
+     cy="6.171"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse420"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.4580002"
+     cy="6.171"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse422"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.5650001"
+     cy="6.0469999"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse424"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="7.5650001"
+     cy="6.0469999"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse426"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.8330002"
+     cy="6.0469999"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse428"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="7.8330002"
+     cy="6.0469999"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse430"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <polygon
+     points="13.374,8.356 13.331,8.374 13.202,8.695 13.202,8.856 13.267,8.909 14.208,8.909 14.272,8.856 14.272,8.695 14.144,8.374 14.101,8.356 13.374,8.356 "
+     id="polygon432"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="13.374,8.356 13.331,8.374 13.202,8.695 13.202,8.856 13.267,8.909 14.208,8.909 14.272,8.856 14.272,8.695 14.144,8.374 14.101,8.356 13.374,8.356 "
+     id="polygon434"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 13.224,8.642 L 13.267,8.659 L 14.208,8.659 L 14.251,8.642"
+     id="path436"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 14.208,8.659 L 14.272,8.695"
+     id="path438"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 13.202,8.695 L 13.267,8.659"
+     id="path440"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="13.502,8.018 13.481,8.445 13.994,8.445 13.973,8.018 13.502,8.018 "
+     id="polygon442"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="13.502,8.018 13.481,8.445 13.994,8.445 13.973,8.018 13.502,8.018 "
+     id="polygon444"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="13.416,8.445 13.374,8.57 14.101,8.57 14.058,8.445 13.416,8.445 "
+     id="polygon446"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="13.416,8.445 13.374,8.57 14.101,8.57 14.058,8.445 13.416,8.445 "
+     id="polygon448"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="13.416"
+     cy="8.7220001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse450"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.416"
+     cy="8.7220001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse452"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.523"
+     cy="8.7220001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse454"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.523"
+     cy="8.7220001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse456"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.63"
+     cy="8.7220001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse458"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.63"
+     cy="8.7220001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse460"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.416"
+     cy="8.7659998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse462"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.416"
+     cy="8.7659998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse464"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.523"
+     cy="8.7659998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse466"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.523"
+     cy="8.7659998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse468"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.63"
+     cy="8.7659998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse470"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.63"
+     cy="8.7659998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse472"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.416"
+     cy="8.8109999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse474"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.416"
+     cy="8.8109999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse476"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.523"
+     cy="8.8109999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse478"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.523"
+     cy="8.8109999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse480"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.63"
+     cy="8.8109999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse482"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.63"
+     cy="8.8109999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse484"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.416"
+     cy="8.8559999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse486"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.416"
+     cy="8.8559999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse488"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.523"
+     cy="8.8559999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse490"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.523"
+     cy="8.8559999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse492"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.63"
+     cy="8.8559999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse494"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.63"
+     cy="8.8559999"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse496"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.737"
+     cy="8.7309999"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse498"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="13.737"
+     cy="8.7309999"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse500"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.005"
+     cy="8.7309999"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse502"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="14.005"
+     cy="8.7309999"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse504"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <polygon
+     points="7.174,8.381 7.131,8.399 7.002,8.72 7.002,8.881 7.067,8.934 8.008,8.934 8.072,8.881 8.072,8.72 7.944,8.399 7.901,8.381 7.174,8.381 "
+     id="polygon506"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="7.174,8.381 7.131,8.399 7.002,8.72 7.002,8.881 7.067,8.934 8.008,8.934 8.072,8.881 8.072,8.72 7.944,8.399 7.901,8.381 7.174,8.381 "
+     id="polygon508"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.024,8.667 L 7.067,8.684 L 8.008,8.684 L 8.051,8.667"
+     id="path510"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 8.008,8.684 L 8.072,8.72"
+     id="path512"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.002,8.72 L 7.067,8.684"
+     id="path514"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="7.302,8.043 7.281,8.47 7.794,8.47 7.773,8.043 7.302,8.043 "
+     id="polygon516"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="7.302,8.043 7.281,8.47 7.794,8.47 7.773,8.043 7.302,8.043 "
+     id="polygon518"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="7.216,8.47 7.174,8.595 7.901,8.595 7.858,8.47 7.216,8.47 "
+     id="polygon520"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="7.216,8.47 7.174,8.595 7.901,8.595 7.858,8.47 7.216,8.47 "
+     id="polygon522"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="7.2160001"
+     cy="8.7469997"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse524"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.2160001"
+     cy="8.7469997"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse526"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.323"
+     cy="8.7469997"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse528"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.323"
+     cy="8.7469997"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse530"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.4299998"
+     cy="8.7469997"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse532"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.4299998"
+     cy="8.7469997"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse534"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.2160001"
+     cy="8.7910004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse536"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.2160001"
+     cy="8.7910004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse538"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.323"
+     cy="8.7910004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse540"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.323"
+     cy="8.7910004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse542"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.4299998"
+     cy="8.7910004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse544"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.4299998"
+     cy="8.7910004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse546"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.2160001"
+     cy="8.8360004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse548"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.2160001"
+     cy="8.8360004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse550"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.323"
+     cy="8.8360004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse552"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.323"
+     cy="8.8360004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse554"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.4299998"
+     cy="8.8360004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse556"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.4299998"
+     cy="8.8360004"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse558"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.2160001"
+     cy="8.8809996"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse560"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.2160001"
+     cy="8.8809996"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse562"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.323"
+     cy="8.8809996"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse564"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.323"
+     cy="8.8809996"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse566"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.4299998"
+     cy="8.8809996"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse568"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="7.4299998"
+     cy="8.8809996"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse570"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.5370002"
+     cy="8.7559996"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse572"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="7.5370002"
+     cy="8.7559996"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse574"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.8049998"
+     cy="8.7559996"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse576"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="7.8049998"
+     cy="8.7559996"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse578"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <polygon
+     points="13.374,5.531 13.331,5.549 13.202,5.87 13.202,6.031 13.267,6.084 14.208,6.084 14.272,6.031 14.272,5.87 14.144,5.549 14.101,5.531 13.374,5.531 "
+     id="polygon580"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="13.374,5.531 13.331,5.549 13.202,5.87 13.202,6.031 13.267,6.084 14.208,6.084 14.272,6.031 14.272,5.87 14.144,5.549 14.101,5.531 13.374,5.531 "
+     id="polygon582"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 13.224,5.817 L 13.267,5.834 L 14.208,5.834 L 14.251,5.817"
+     id="path584"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 14.208,5.834 L 14.272,5.87"
+     id="path586"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 13.202,5.87 L 13.267,5.834"
+     id="path588"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="13.502,5.192 13.481,5.62 13.994,5.62 13.973,5.192 13.502,5.192 "
+     id="polygon590"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="13.502,5.192 13.481,5.62 13.994,5.62 13.973,5.192 13.502,5.192 "
+     id="polygon592"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="13.416,5.62 13.374,5.745 14.101,5.745 14.058,5.62 13.416,5.62 "
+     id="polygon594"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="13.416,5.62 13.374,5.745 14.101,5.745 14.058,5.62 13.416,5.62 "
+     id="polygon596"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="13.416"
+     cy="5.8969998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse598"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.416"
+     cy="5.8969998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse600"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.523"
+     cy="5.8969998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse602"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.523"
+     cy="5.8969998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse604"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.63"
+     cy="5.8969998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse606"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.63"
+     cy="5.8969998"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse608"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.416"
+     cy="5.941"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse610"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.416"
+     cy="5.941"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse612"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.523"
+     cy="5.941"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse614"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.523"
+     cy="5.941"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse616"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.63"
+     cy="5.941"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse618"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.63"
+     cy="5.941"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse620"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.416"
+     cy="5.9860001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse622"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.416"
+     cy="5.9860001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse624"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.523"
+     cy="5.9860001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse626"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.523"
+     cy="5.9860001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse628"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.63"
+     cy="5.9860001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse630"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.63"
+     cy="5.9860001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse632"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.416"
+     cy="6.0310001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse634"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.416"
+     cy="6.0310001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse636"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.523"
+     cy="6.0310001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse638"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.523"
+     cy="6.0310001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse640"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.63"
+     cy="6.0310001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse642"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="13.63"
+     cy="6.0310001"
+     rx="0.011"
+     ry="0.011"
+     id="ellipse644"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="13.737"
+     cy="5.9060001"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse646"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="13.737"
+     cy="5.9060001"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse648"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.005"
+     cy="5.9060001"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse650"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="14.005"
+     cy="5.9060001"
+     rx="0.134"
+     ry="0.043000001"
+     id="ellipse652"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <text
+     x="9.6599998"
+     y="8.3249998"
+     id="text654"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth0</text>
+  <text
+     x="11.456"
+     y="6.7820001"
+     id="text656"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth2</text>
+  <text
+     x="9.0799999"
+     y="6.8319998"
+     id="text658"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth1</text>
+  <text
+     x="7.1090002"
+     y="4.9520001"
+     id="text660"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj6a</text>
+  <text
+     x="13.463"
+     y="4.9569998"
+     id="text662"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj6f</text>
+  <text
+     x="7.1820002"
+     y="9.507"
+     id="text664"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">qmsa</text>
+  <text
+     x="13.327"
+     y="9.507"
+     id="text666"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">qmsf</text>
+  <text
+     x="8.3570004"
+     y="2.2019999"
+     id="text668"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: PROMISES</text>
+  <text
+     x="9.9700003"
+     y="3.55"
+     id="text670"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="9.698"
+     y="4.1500001"
+     id="text672"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIAMOND</text>
+  <text
+     x="2.221"
+     y="9.9250002"
+     id="text674"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="1.8150001"
+     y="10.525"
+     id="text676"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">192.168.1.0/24</text>
+  <text
+     x="15.621"
+     y="9.8520002"
+     id="text678"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="15.185"
+     y="10.452"
+     id="text680"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">192.168.2.0/24</text>
+  <rect
+     width="0.62699997"
+     height="0.55299997"
+     x="8.7729998"
+     y="4.4429998"
+     id="rect682"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="9.0869999"
+     cy="4.9959998"
+     rx="0.31299999"
+     ry="0.092"
+     id="ellipse684"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="9.0869999"
+     cy="4.4429998"
+     rx="0.31299999"
+     ry="0.092"
+     id="ellipse686"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="9.0869999"
+     cy="4.4429998"
+     rx="0.31299999"
+     ry="0.092"
+     id="ellipse688"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 9.4,4.443 L 9.4,4.996 C 9.4,5.047 9.26,5.088 9.087,5.088 C 8.913,5.088 8.773,5.047 8.773,4.996 L 8.773,4.443"
+     id="path690"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.375"
+     y1="4.9000001"
+     x2="10.025"
+     y2="5.3000002"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line692"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62699997"
+     height="0.55299997"
+     x="11.812"
+     y="4.4450002"
+     id="rect694"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="12.126"
+     cy="4.9980001"
+     rx="0.31299999"
+     ry="0.092"
+     id="ellipse696"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.126"
+     cy="4.4450002"
+     rx="0.31299999"
+     ry="0.092"
+     id="ellipse698"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.126"
+     cy="4.4450002"
+     rx="0.31299999"
+     ry="0.092"
+     id="ellipse700"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 12.439,4.445 L 12.439,4.998 C 12.439,5.049 12.299,5.09 12.126,5.09 C 11.953,5.09 11.812,5.049 11.812,4.998 L 11.812,4.445"
+     id="path702"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="11.089"
+     y1="5.2789998"
+     x2="11.825"
+     y2="4.8499999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line704"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="8.7399998"
+     y="5.5819998"
+     id="text706"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
+  <text
+     x="11.799"
+     y="5.6069999"
+     id="text708"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">data</text>
+  <text
+     x="6.5149999"
+     y="11.352"
+     id="text710"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">30 Users</text>
+  <text
+     x="19.365"
+     y="11.267"
+     id="text712"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
+  <text
+     x="1.018"
+     y="4.3790002"
+     id="text714"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounting</text>
+  <text
+     x="16.813"
+     y="4.316"
+     id="text716"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Financial Services</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap5-net.svg b/docs-xml/Samba3-ByExample/images/chap5-net.svg
new file mode 100644
index 00000000000..77df4d1db38
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap5-net.svg
@@ -0,0 +1,3668 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="25.385cm"
+   height="20.027cm"
+   viewBox="-0.789 0.573 24.595 20.6"
+   id="svg2">
+  <defs
+     id="defs1129" />
+  <rect
+     width="11.5"
+     height="7.7259998"
+     x="12.77"
+     y="12.847"
+     id="rect4"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.77,12.847 C 12.604315,12.847 12.47,12.981315 12.47,13.147"
+     id="path6"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 24.57,13.147 C 24.57,12.981315 24.435685,12.847 24.27,12.847"
+     id="path8"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="12.1"
+     height="7.1259999"
+     x="12.47"
+     y="13.147"
+     id="rect10"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.47,20.273 C 12.47,20.438685 12.604315,20.573 12.77,20.573"
+     id="path12"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 24.27,20.573 C 24.435685,20.573 24.57,20.438685 24.57,20.273"
+     id="path14"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="12.77"
+     y1="12.847"
+     x2="24.27"
+     y2="12.847"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.77"
+     y1="20.573"
+     x2="24.27"
+     y2="20.573"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.77,12.847 C 12.604315,12.847 12.47,12.981315 12.47,13.147"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 24.57,13.147 C 24.57,12.981315 24.435685,12.847 24.27,12.847"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.47"
+     y1="13.147"
+     x2="12.47"
+     y2="20.273001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="24.57"
+     y1="13.147"
+     x2="24.57"
+     y2="20.273001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.47,20.273 C 12.47,20.438685 12.604315,20.573 12.77,20.573"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 24.27,20.573 C 24.435685,20.573 24.57,20.438685 24.57,20.273"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="12.01"
+     height="7.7779999"
+     x="-0.46399999"
+     y="12.797"
+     id="rect32"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -0.464,12.797 C -0.62968542,12.797 -0.764,12.931315 -0.764,13.097"
+     id="path34"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.845,13.097 C 11.845,12.931315 11.710685,12.797 11.545,12.797"
+     id="path36"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="12.61"
+     height="7.178"
+     x="-0.764"
+     y="13.097"
+     id="rect38"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -0.764,20.275 C -0.764,20.440685 -0.62968542,20.575 -0.464,20.575"
+     id="path40"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.545,20.575 C 11.710685,20.575 11.845,20.440685 11.845,20.275"
+     id="path42"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="-0.46399999"
+     y1="12.797"
+     x2="11.545"
+     y2="12.797"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line44"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-0.46399999"
+     y1="20.575001"
+     x2="11.545"
+     y2="20.575001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -0.464,12.797 C -0.62968542,12.797 -0.764,12.931315 -0.764,13.097"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.845,13.097 C 11.845,12.931315 11.710685,12.797 11.545,12.797"
+     id="path50"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-0.764"
+     y1="13.097"
+     x2="-0.764"
+     y2="20.275"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.845"
+     y1="13.097"
+     x2="11.845"
+     y2="20.275"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line54"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -0.764,20.275 C -0.764,20.440685 -0.62968542,20.575 -0.464,20.575"
+     id="path56"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.545,20.575 C 11.710685,20.575 11.845,20.440685 11.845,20.275"
+     id="path58"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="15.975"
+     height="9.7749996"
+     x="5.645"
+     y="2.1719999"
+     id="rect60"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 5.645,2.172 C 5.4793146,2.172 5.345,2.3063146 5.345,2.472"
+     id="path62"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 21.92,2.472 C 21.92,2.3063146 21.785685,2.172 21.62,2.172"
+     id="path64"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="16.575001"
+     height="9.1750002"
+     x="5.3449998"
+     y="2.4719999"
+     id="rect66"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 5.345,11.647 C 5.345,11.812685 5.4793146,11.947 5.645,11.947"
+     id="path68"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 21.62,11.947 C 21.785685,11.947 21.92,11.812685 21.92,11.647"
+     id="path70"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="5.645"
+     y1="2.1719999"
+     x2="21.620001"
+     y2="2.1719999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="5.645"
+     y1="11.947"
+     x2="21.620001"
+     y2="11.947"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 5.645,2.172 C 5.4793146,2.172 5.345,2.3063146 5.345,2.472"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 21.92,2.472 C 21.92,2.3063146 21.785685,2.172 21.62,2.172"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="5.3449998"
+     y1="2.4719999"
+     x2="5.3449998"
+     y2="11.647"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="21.92"
+     y1="2.4719999"
+     x2="21.92"
+     y2="11.647"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 5.345,11.647 C 5.345,11.812685 5.4793146,11.947 5.645,11.947"
+     id="path84"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 21.62,11.947 C 21.785685,11.947 21.92,11.812685 21.92,11.647"
+     id="path86"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.263,3.803 C 0.857,3.793 0.068,3.995 0.179,4.427 C 0.29,4.859 0.82,4.955 1.042,4.83 C 1.263,4.705 0.696,5.435 1.781,5.627 C 2.866,5.819 3.42,5.511 3.26,5.291 C 3.1,5.07 4.209,5.809 4.727,5.387 C 5.244,4.964 4.197,4.561 4.418,4.619 C 4.64,4.676 5.318,4.6 5.096,3.88 C 4.874,3.16 2.878,3.717 3.1,3.611 C 3.322,3.505 2.767,2.978 2.077,3.083 C 1.387,3.189 1.338,3.38 1.264,3.803 L 1.263,3.803"
+     id="path88"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 1.263,3.803 C 0.857,3.793 0.068,3.995 0.179,4.427 C 0.29,4.859 0.82,4.955 1.042,4.83 C 1.263,4.705 0.696,5.435 1.781,5.627 C 2.866,5.819 3.42,5.511 3.26,5.291 C 3.1,5.07 4.209,5.809 4.727,5.387 C 5.244,4.964 4.197,4.561 4.418,4.619 C 4.64,4.676 5.318,4.6 5.096,3.88 C 4.874,3.16 2.878,3.717 3.1,3.611 C 3.322,3.505 2.767,2.978 2.077,3.083 C 1.387,3.189 1.338,3.38 1.264,3.803 L 1.263,3.803"
+     id="path90"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.2260001"
+     y="4.4980001"
+     id="text92"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
+  <rect
+     width="1.054"
+     height="2.1070001"
+     x="5.7290001"
+     y="6.2870002"
+     id="rect94"
+     style="fill:#ff0000;stroke:none;stroke-width:0" />
+  <polygon
+     points="5.729,6.287 6.783,6.287 6.915,6.156 5.861,6.156 5.729,6.287 "
+     id="polygon96"
+     style="fill:#ff0000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="6.783,6.287 6.915,6.156 6.915,8.263 6.783,8.394 6.783,6.287 "
+     id="polygon98"
+     style="fill:#ff0000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="6.4980001"
+     x2="6.783"
+     y2="6.4980001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line100"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="6.3660002"
+     x2="6.783"
+     y2="6.4980001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line102"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.0450001"
+     y1="6.2870002"
+     x2="6.0450001"
+     y2="6.4980001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line104"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.0450001"
+     y1="6.2870002"
+     x2="6.177"
+     y2="6.1560001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line106"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="6.9190001"
+     x2="6.783"
+     y2="6.9190001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line108"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="6.7880001"
+     x2="6.783"
+     y2="6.9190001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line110"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.467"
+     y1="6.4980001"
+     x2="6.467"
+     y2="6.9190001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line112"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="7.3410001"
+     x2="6.783"
+     y2="7.3410001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line114"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="7.2090001"
+     x2="6.783"
+     y2="7.3410001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line116"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.0450001"
+     y1="6.9190001"
+     x2="6.0450001"
+     y2="7.3410001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line118"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="7.7620001"
+     x2="6.783"
+     y2="7.7620001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line120"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="7.631"
+     x2="6.783"
+     y2="7.7620001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line122"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.467"
+     y1="7.3410001"
+     x2="6.467"
+     y2="7.7620001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line124"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="8.184"
+     x2="6.783"
+     y2="8.184"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line126"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="8.052"
+     x2="6.783"
+     y2="8.184"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line128"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.0450001"
+     y1="7.7620001"
+     x2="6.0450001"
+     y2="8.184"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line130"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.467"
+     y1="8.184"
+     x2="6.467"
+     y2="8.3940001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line132"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="6.2870002"
+     x2="6.783"
+     y2="6.2870002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line134"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="6.783"
+     y1="8.3940001"
+     x2="6.783"
+     y2="6.2870002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="6.783"
+     y1="6.2870002"
+     x2="6.915"
+     y2="6.1560001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.05" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.050"
+     points="5.729,6.287 5.861,6.156 6.915,6.156 6.915,8.263 6.783,8.394 5.729,8.394 5.729,6.287 "
+     id="polyline140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="2.0050001"
+     height="6.0149999"
+     x="8.4580002"
+     y="4.1360002"
+     id="rect142"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.0050001"
+     height="6.0149999"
+     x="8.4580002"
+     y="4.1360002"
+     id="rect144"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.0050001"
+     height="6.0149999"
+     x="8.4580002"
+     y="4.1360002"
+     id="rect146"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.604"
+     height="2.4059999"
+     x="8.6590004"
+     y="4.3369999"
+     id="rect148"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.604"
+     height="2.4059999"
+     x="8.6590004"
+     y="4.3369999"
+     id="rect150"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.604"
+     height="2.4059999"
+     x="8.6590004"
+     y="4.3369999"
+     id="rect152"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.6590004"
+     y1="4.7379999"
+     x2="10.263"
+     y2="4.7379999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line154"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.263"
+     y1="5.1389999"
+     x2="8.6590004"
+     y2="5.1389999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line156"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.6590004"
+     y1="5.54"
+     x2="10.263"
+     y2="5.54"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line158"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.6590004"
+     y1="5.941"
+     x2="10.263"
+     y2="5.941"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line160"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.263"
+     y1="6.342"
+     x2="8.6590004"
+     y2="6.342"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line162"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.103"
+     height="0.60100001"
+     x="8.6590004"
+     y="6.9429998"
+     id="rect164"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.103"
+     height="0.60100001"
+     x="8.6590004"
+     y="6.9429998"
+     id="rect166"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.103"
+     height="0.60100001"
+     x="8.6590004"
+     y="6.9429998"
+     id="rect168"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.4580002"
+     y1="7.9460001"
+     x2="10.463"
+     y2="7.9460001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line170"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.3610001"
+     y="8.1459999"
+     id="rect172"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.3610001"
+     y="8.1459999"
+     id="rect174"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.3610001"
+     y="8.1459999"
+     id="rect176"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.7620001"
+     y="8.1459999"
+     id="rect178"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.7620001"
+     y="8.1459999"
+     id="rect180"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.7620001"
+     y="8.1459999"
+     id="rect182"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="10.163"
+     y="8.1459999"
+     id="rect184"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="10.163"
+     y="8.1459999"
+     id="rect186"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="10.163"
+     y="8.1459999"
+     id="rect188"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.2"
+     height="0.2"
+     x="10.062"
+     y="7.5450001"
+     id="rect190"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.2"
+     height="0.2"
+     x="10.062"
+     y="7.5450001"
+     id="rect192"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.2"
+     height="0.2"
+     x="10.062"
+     y="7.5450001"
+     id="rect194"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.6590004"
+     y1="7.244"
+     x2="9.7620001"
+     y2="7.244"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line196"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.301"
+     height="0.301"
+     x="8.6590004"
+     y="8.0459995"
+     id="rect198"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.301"
+     height="0.301"
+     x="8.6590004"
+     y="8.0459995"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.301"
+     height="0.301"
+     x="8.6590004"
+     y="8.0459995"
+     id="rect202"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.403"
+     height="0.1"
+     x="8.7589998"
+     y="6.4419999"
+     id="rect204"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.403"
+     height="0.1"
+     x="8.7589998"
+     y="6.4419999"
+     id="rect206"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.403"
+     height="0.1"
+     x="8.7589998"
+     y="6.4419999"
+     id="rect208"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.7589998"
+     y1="7.0430002"
+     x2="9.6610003"
+     y2="7.0430002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line210"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.6610003"
+     y1="7.1440001"
+     x2="9.5609999"
+     y2="7.1440001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line212"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.7589998"
+     y1="7.1440001"
+     x2="8.8590002"
+     y2="7.1440001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line214"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.50099999"
+     height="0.1"
+     x="8.96"
+     y="7.0430002"
+     id="rect216"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.50099999"
+     height="0.1"
+     x="8.96"
+     y="7.0430002"
+     id="rect218"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.50099999"
+     height="0.1"
+     x="8.96"
+     y="7.0430002"
+     id="rect220"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.7589998"
+     y1="6.6420002"
+     x2="8.8590002"
+     y2="6.6420002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line222"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.96"
+     y1="6.6420002"
+     x2="9.0600004"
+     y2="6.6420002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line224"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.9619999"
+     y1="6.6420002"
+     x2="10.163"
+     y2="6.6420002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line226"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="10.051"
+     x2="10.363"
+     y2="10.051"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line228"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.9510002"
+     x2="8.559"
+     y2="9.9510002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line230"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.8500004"
+     x2="10.363"
+     y2="9.8500004"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line232"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.75"
+     x2="8.559"
+     y2="9.75"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line234"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.6499996"
+     x2="10.363"
+     y2="9.6499996"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line236"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.5500002"
+     x2="8.559"
+     y2="9.5500002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line238"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.4490004"
+     x2="10.363"
+     y2="9.4490004"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line240"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.349"
+     x2="8.559"
+     y2="9.349"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line242"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.2489996"
+     x2="10.363"
+     y2="9.2489996"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line244"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.1490002"
+     x2="8.559"
+     y2="9.1490002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line246"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.0480003"
+     x2="10.363"
+     y2="9.0480003"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line248"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="8.948"
+     x2="8.559"
+     y2="8.948"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line250"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="8.8479996"
+     x2="10.363"
+     y2="8.8479996"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line252"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="8.7480001"
+     x2="8.559"
+     y2="8.7480001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line254"
+     style="stroke:#000000;stroke-width:0.01" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="2.424,5.688 2.424,7.250 5.700,7.250 5.700,7.300 "
+     id="polyline256"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.875"
+     y1="7.3000002"
+     x2="8.4250002"
+     y2="7.2750001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line258"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.477"
+     height="1.303"
+     x="11.597"
+     y="4.0450001"
+     id="rect260"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="12.335"
+     cy="5.348"
+     rx="0.73799998"
+     ry="0.21699999"
+     id="ellipse262"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.335"
+     cy="4.0450001"
+     rx="0.73799998"
+     ry="0.21699999"
+     id="ellipse264"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.335"
+     cy="4.0450001"
+     rx="0.73799998"
+     ry="0.21699999"
+     id="ellipse266"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 13.074,4.045 L 13.074,5.348 C 13.074,5.468 12.743,5.565 12.335,5.565 C 11.928,5.565 11.597,5.468 11.597,5.348 L 11.597,4.045"
+     id="path268"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.377"
+     height="1.215"
+     x="11.622"
+     y="5.96"
+     id="rect270"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="12.311"
+     cy="7.1750002"
+     rx="0.68800002"
+     ry="0.20200001"
+     id="ellipse272"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.311"
+     cy="5.96"
+     rx="0.68800002"
+     ry="0.20200001"
+     id="ellipse274"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.311"
+     cy="5.96"
+     rx="0.68800002"
+     ry="0.20200001"
+     id="ellipse276"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 12.999,5.96 L 12.999,7.175 C 12.999,7.287 12.691,7.377 12.311,7.377 C 11.931,7.377 11.622,7.287 11.622,7.175 L 11.622,5.96"
+     id="path278"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.475"
+     y1="4.6750002"
+     x2="11.55"
+     y2="4.6750002"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line280"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.45"
+     y1="6.3499999"
+     x2="11.625"
+     y2="6.3499999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line282"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.45"
+     y1="8.8249998"
+     x2="21"
+     y2="8.8249998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line284"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="20.950001"
+     y1="8.8249998"
+     x2="20.950001"
+     y2="7.9749999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line286"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="14.928"
+     y1="8.8249998"
+     x2="14.928"
+     y2="7.9169998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line288"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="14.946"
+     y1="8.8249998"
+     x2="14.946"
+     y2="9.8249998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line290"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.903"
+     y1="8.8249998"
+     x2="17.903"
+     y2="7.901"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line292"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.910999"
+     y1="8.8249998"
+     x2="17.910999"
+     y2="9.8249998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line294"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="20.950001"
+     y1="8.8249998"
+     x2="20.950001"
+     y2="9.9250002"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line296"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1"
+     height="1"
+     x="11.825"
+     y="10.625"
+     id="rect298"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="1"
+     height="1"
+     x="11.825"
+     y="10.625"
+     id="rect300"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1"
+     height="1"
+     x="11.825"
+     y="10.625"
+     id="rect302"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 12.387,10.787 C 12.387,11.287 12.487,11.187 11.987,11.187"
+     id="path304"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 12.387,10.787 C 12.387,11.287 12.487,11.187 11.987,11.187"
+     id="path306"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="12.435,10.865 12.385,10.765 12.335,10.865 12.435,10.865 "
+     id="polygon308"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.435,10.865 12.385,10.765 12.335,10.865 12.435,10.865 "
+     id="polygon310"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.065,11.135 11.965,11.185 12.065,11.235 12.065,11.135 "
+     id="polygon312"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.065,11.135 11.965,11.185 12.065,11.235 12.065,11.135 "
+     id="polygon314"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 12.684,11.068 C 12.184,11.068 12.284,10.968 12.284,11.468"
+     id="path316"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 12.684,11.068 C 12.184,11.068 12.284,10.968 12.284,11.468"
+     id="path318"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="12.595,11.115 12.695,11.065 12.595,11.015 12.595,11.115 "
+     id="polygon320"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.595,11.115 12.695,11.065 12.595,11.015 12.595,11.115 "
+     id="polygon322"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.225,11.385 12.275,11.485 12.325,11.385 12.225,11.385 "
+     id="polygon324"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.225,11.385 12.275,11.485 12.325,11.385 12.225,11.385 "
+     id="polygon326"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="12.325"
+     y1="8.8249998"
+     x2="12.325"
+     y2="10.625"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line328"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="14.424,10.287 14.365,10.312 14.19,10.75 14.19,10.969 14.278,11.042 15.562,11.042 15.65,10.969 15.65,10.75 15.475,10.312 15.416,10.287 14.424,10.287 "
+     id="polygon330"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="14.424,10.287 14.365,10.312 14.19,10.75 14.19,10.969 14.278,11.042 15.562,11.042 15.65,10.969 15.65,10.75 15.475,10.312 15.416,10.287 14.424,10.287 "
+     id="polygon332"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 14.219,10.677 L 14.278,10.701 L 15.562,10.701 L 15.621,10.677"
+     id="path334"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 15.562,10.701 L 15.65,10.75"
+     id="path336"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 14.19,10.75 L 14.278,10.701"
+     id="path338"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="14.599,9.825 14.57,10.409 15.27,10.409 15.241,9.825 14.599,9.825 "
+     id="polygon340"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="14.599,9.825 14.57,10.409 15.27,10.409 15.241,9.825 14.599,9.825 "
+     id="polygon342"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="14.482,10.409 14.424,10.579 15.416,10.579 15.358,10.409 14.482,10.409 "
+     id="polygon344"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="14.482,10.409 14.424,10.579 15.416,10.579 15.358,10.409 14.482,10.409 "
+     id="polygon346"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="14.482"
+     cy="10.786"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse348"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.482"
+     cy="10.786"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse350"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.628"
+     cy="10.786"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse352"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.628"
+     cy="10.786"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse354"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.774"
+     cy="10.786"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse356"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.774"
+     cy="10.786"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse358"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.482"
+     cy="10.847"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse360"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.482"
+     cy="10.847"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse362"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.628"
+     cy="10.847"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse364"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.628"
+     cy="10.847"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse366"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.774"
+     cy="10.847"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse368"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.774"
+     cy="10.847"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse370"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.482"
+     cy="10.908"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse372"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.482"
+     cy="10.908"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse374"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.628"
+     cy="10.908"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse376"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.628"
+     cy="10.908"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse378"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.774"
+     cy="10.908"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse380"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.774"
+     cy="10.908"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse382"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.482"
+     cy="10.969"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse384"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.482"
+     cy="10.969"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse386"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.628"
+     cy="10.969"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse388"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.628"
+     cy="10.969"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse390"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.774"
+     cy="10.969"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse392"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="14.774"
+     cy="10.969"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse394"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="14.92"
+     cy="10.798"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse396"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="14.92"
+     cy="10.798"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse398"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.285"
+     cy="10.798"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse400"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="15.285"
+     cy="10.798"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse402"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="14.372"
+     y="6.8239999"
+     id="rect404"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="14.372"
+     y="6.8239999"
+     id="rect406"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="14.492"
+     y="6.9439998"
+     id="rect408"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="14.522,7.657 15.094,7.657 15.094,7.787 14.552,7.787 14.522,7.657 "
+     id="polygon410"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="14.522,7.657 15.094,7.657 15.094,7.787 14.552,7.787 14.522,7.657 "
+     id="polygon412"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="15.094,7.657 15.333,7.657 15.303,7.787 15.094,7.787 15.094,7.657 "
+     id="polygon414"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.094,7.657 15.333,7.657 15.303,7.787 15.094,7.787 15.094,7.657 "
+     id="polygon416"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="15.133"
+     y="7.6960001"
+     id="rect418"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="15.133"
+     y="7.6960001"
+     id="rect420"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="14.816,7.787 15.039,7.787 15.039,7.852 15.15,7.852 15.15,7.917 14.705,7.917 14.705,7.852 14.816,7.852 14.816,7.787 "
+     id="polygon422"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="14.816,7.787 15.039,7.787 15.039,7.852 15.15,7.852 15.15,7.917 14.705,7.917 14.705,7.852 14.816,7.852 14.816,7.787 "
+     id="polygon424"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="17.348"
+     y="6.8080001"
+     id="rect426"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="17.348"
+     y="6.8080001"
+     id="rect428"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="17.468"
+     y="6.928"
+     id="rect430"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="17.498,7.641 18.07,7.641 18.07,7.771 17.528,7.771 17.498,7.641 "
+     id="polygon432"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.498,7.641 18.07,7.641 18.07,7.771 17.528,7.771 17.498,7.641 "
+     id="polygon434"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.07,7.641 18.309,7.641 18.279,7.771 18.07,7.771 18.07,7.641 "
+     id="polygon436"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.07,7.641 18.309,7.641 18.279,7.771 18.07,7.771 18.07,7.641 "
+     id="polygon438"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="18.108999"
+     y="7.6799998"
+     id="rect440"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="18.108999"
+     y="7.6799998"
+     id="rect442"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="17.792,7.771 18.014,7.771 18.014,7.836 18.126,7.836 18.126,7.901 17.681,7.901 17.681,7.836 17.792,7.836 17.792,7.771 "
+     id="polygon444"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.792,7.771 18.014,7.771 18.014,7.836 18.126,7.836 18.126,7.901 17.681,7.901 17.681,7.836 17.792,7.836 17.792,7.771 "
+     id="polygon446"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="20.398001"
+     y="6.8319998"
+     id="rect448"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="20.398001"
+     y="6.8319998"
+     id="rect450"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="20.518"
+     y="6.9530001"
+     id="rect452"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="20.548,7.666 21.12,7.666 21.12,7.796 20.578,7.796 20.548,7.666 "
+     id="polygon454"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.548,7.666 21.12,7.666 21.12,7.796 20.578,7.796 20.548,7.666 "
+     id="polygon456"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="21.12,7.666 21.359,7.666 21.329,7.796 21.12,7.796 21.12,7.666 "
+     id="polygon458"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="21.12,7.666 21.359,7.666 21.329,7.796 21.12,7.796 21.12,7.666 "
+     id="polygon460"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="21.159"
+     y="7.7049999"
+     id="rect462"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="21.159"
+     y="7.7049999"
+     id="rect464"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="20.842,7.796 21.064,7.796 21.064,7.861 21.176,7.861 21.176,7.926 20.731,7.926 20.731,7.861 20.842,7.861 20.842,7.796 "
+     id="polygon466"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.842,7.796 21.064,7.796 21.064,7.861 21.176,7.861 21.176,7.926 20.731,7.926 20.731,7.861 20.842,7.861 20.842,7.796 "
+     id="polygon468"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="17.298"
+     y="9.8319998"
+     id="rect470"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="17.298"
+     y="9.8319998"
+     id="rect472"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="17.417999"
+     y="9.9530001"
+     id="rect474"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="17.448,10.666 18.02,10.666 18.02,10.796 17.478,10.796 17.448,10.666 "
+     id="polygon476"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.448,10.666 18.02,10.666 18.02,10.796 17.478,10.796 17.448,10.666 "
+     id="polygon478"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.02,10.666 18.259,10.666 18.229,10.796 18.02,10.796 18.02,10.666 "
+     id="polygon480"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.02,10.666 18.259,10.666 18.229,10.796 18.02,10.796 18.02,10.666 "
+     id="polygon482"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="18.059"
+     y="10.705"
+     id="rect484"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="18.059"
+     y="10.705"
+     id="rect486"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="17.742,10.796 17.964,10.796 17.964,10.861 18.076,10.861 18.076,10.926 17.631,10.926 17.631,10.861 17.742,10.861 17.742,10.796 "
+     id="polygon488"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.742,10.796 17.964,10.796 17.964,10.861 18.076,10.861 18.076,10.926 17.631,10.926 17.631,10.861 17.742,10.861 17.742,10.796 "
+     id="polygon490"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="20.398001"
+     y="9.9320002"
+     id="rect492"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="20.398001"
+     y="9.9320002"
+     id="rect494"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="20.518"
+     y="10.053"
+     id="rect496"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="20.548,10.766 21.12,10.766 21.12,10.896 20.578,10.896 20.548,10.766 "
+     id="polygon498"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.548,10.766 21.12,10.766 21.12,10.896 20.578,10.896 20.548,10.766 "
+     id="polygon500"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="21.12,10.766 21.359,10.766 21.329,10.896 21.12,10.896 21.12,10.766 "
+     id="polygon502"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="21.12,10.766 21.359,10.766 21.329,10.896 21.12,10.896 21.12,10.766 "
+     id="polygon504"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="21.159"
+     y="10.805"
+     id="rect506"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="21.159"
+     y="10.805"
+     id="rect508"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="20.842,10.896 21.064,10.896 21.064,10.961 21.176,10.961 21.176,11.026 20.731,11.026 20.731,10.961 20.842,10.961 20.842,10.896 "
+     id="polygon510"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.842,10.896 21.064,10.896 21.064,10.961 21.176,10.961 21.176,11.026 20.731,11.026 20.731,10.961 20.842,10.961 20.842,10.896 "
+     id="polygon512"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1"
+     height="1"
+     x="3.473"
+     y="13.307"
+     id="rect514"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="1"
+     height="1"
+     x="3.473"
+     y="13.307"
+     id="rect516"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1"
+     height="1"
+     x="3.473"
+     y="13.307"
+     id="rect518"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 4.034,13.469 C 4.034,13.969 4.134,13.869 3.634,13.869"
+     id="path520"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 4.034,13.469 C 4.034,13.969 4.134,13.869 3.634,13.869"
+     id="path522"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.083,13.547 4.033,13.447 3.982,13.547 4.083,13.547 "
+     id="polygon524"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.083,13.547 4.033,13.447 3.982,13.547 4.083,13.547 "
+     id="polygon526"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.713,13.817 3.613,13.867 3.713,13.917 3.713,13.817 "
+     id="polygon528"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.713,13.817 3.613,13.867 3.713,13.917 3.713,13.817 "
+     id="polygon530"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 4.331,13.751 C 3.831,13.751 3.931,13.651 3.931,14.151"
+     id="path532"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 4.331,13.751 C 3.831,13.751 3.931,13.651 3.931,14.151"
+     id="path534"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.242,13.797 4.343,13.747 4.242,13.697 4.242,13.797 "
+     id="polygon536"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.242,13.797 4.343,13.747 4.242,13.697 4.242,13.797 "
+     id="polygon538"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.873,14.067 3.923,14.167 3.973,14.067 3.873,14.067 "
+     id="polygon540"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.873,14.067 3.923,14.167 3.973,14.067 3.873,14.067 "
+     id="polygon542"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="12.025,11.600 12.025,12.422 3.973,12.422 3.973,13.307 "
+     id="polyline544"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="12.625,11.650 12.625,12.422 18.872,12.422 18.872,13.332 "
+     id="polyline546"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="11.971"
+     y="4.928"
+     id="text548"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
+  <text
+     x="11.969"
+     y="6.79"
+     id="text550"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">data</text>
+  <text
+     x="5.848"
+     y="8.9899998"
+     id="text552"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">firewall</text>
+  <text
+     x="10.47"
+     y="11.315"
+     id="text554"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
+  <text
+     x="16.370001"
+     y="6.3779998"
+     id="text556"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.0.0/22</text>
+  <text
+     x="15.487"
+     y="3.3280001"
+     id="text558"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: MEGANET</text>
+  <text
+     x="8.2959995"
+     y="2.983"
+     id="text560"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC Server:</text>
+  <text
+     x="8.5109997"
+     y="3.5829999"
+     id="text562"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">MASSIVE</text>
+  <text
+     x="7.4990001"
+     y="7.092"
+     id="text564"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth0</text>
+  <text
+     x="10.822"
+     y="8.5419998"
+     id="text566"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth1</text>
+  <rect
+     width="1"
+     height="1"
+     x="18.372"
+     y="13.332"
+     id="rect568"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="1"
+     height="1"
+     x="18.372"
+     y="13.332"
+     id="rect570"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1"
+     height="1"
+     x="18.372"
+     y="13.332"
+     id="rect572"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 18.934,13.494 C 18.934,13.994 19.034,13.894 18.534,13.894"
+     id="path574"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 18.934,13.494 C 18.934,13.994 19.034,13.894 18.534,13.894"
+     id="path576"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="18.982,13.572 18.932,13.473 18.883,13.572 18.982,13.572 "
+     id="polygon578"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="18.982,13.572 18.932,13.473 18.883,13.572 18.982,13.572 "
+     id="polygon580"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="18.612,13.842 18.512,13.893 18.612,13.942 18.612,13.842 "
+     id="polygon582"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="18.612,13.842 18.512,13.893 18.612,13.942 18.612,13.842 "
+     id="polygon584"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 19.231,13.776 C 18.731,13.776 18.831,13.676 18.831,14.176"
+     id="path586"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 19.231,13.776 C 18.731,13.776 18.831,13.676 18.831,14.176"
+     id="path588"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="19.142,13.822 19.242,13.772 19.142,13.723 19.142,13.822 "
+     id="polygon590"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.142,13.822 19.242,13.772 19.142,13.723 19.142,13.822 "
+     id="polygon592"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="18.772,14.092 18.822,14.192 18.872,14.092 18.772,14.092 "
+     id="polygon594"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="18.772,14.092 18.822,14.192 18.872,14.092 18.772,14.092 "
+     id="polygon596"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.275"
+     y1="15.225"
+     x2="20.950001"
+     y2="15.225"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line598"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="15.093"
+     y1="15.225"
+     x2="15.093"
+     y2="16.225"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line600"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.325"
+     y1="15.225"
+     x2="13.325"
+     y2="16.225"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line602"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.979"
+     y1="15.225"
+     x2="16.979"
+     y2="16.225"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line604"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.872"
+     y1="15.225"
+     x2="18.872"
+     y2="14.332"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line606"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.864"
+     y1="15.225"
+     x2="18.864"
+     y2="16.225"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line608"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="20.9"
+     y1="15.225"
+     x2="20.9"
+     y2="16.200001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line610"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.5"
+     height="3"
+     x="20.15"
+     y="16.200001"
+     id="rect612"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.5"
+     height="3"
+     x="20.15"
+     y="16.200001"
+     id="rect614"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.5"
+     height="3"
+     x="20.15"
+     y="16.200001"
+     id="rect616"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.2"
+     height="1.2"
+     x="20.299999"
+     y="16.35"
+     id="rect618"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.2"
+     height="1.2"
+     x="20.299999"
+     y="16.35"
+     id="rect620"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.2"
+     height="1.2"
+     x="20.299999"
+     y="16.35"
+     id="rect622"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.5"
+     y1="16.65"
+     x2="20.299999"
+     y2="16.65"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line624"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.299999"
+     y1="16.950001"
+     x2="21.5"
+     y2="16.950001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line626"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.5"
+     y1="17.174999"
+     x2="20.299999"
+     y2="17.174999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line628"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.82499999"
+     height="0.44999999"
+     x="20.299999"
+     y="17.700001"
+     id="rect630"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.82499999"
+     height="0.44999999"
+     x="20.299999"
+     y="17.700001"
+     id="rect632"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.82499999"
+     height="0.44999999"
+     x="20.299999"
+     y="17.700001"
+     id="rect634"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.15"
+     y1="18.225"
+     x2="21.65"
+     y2="18.225"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line636"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="20.825001"
+     y="18.375"
+     id="rect638"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="20.825001"
+     y="18.375"
+     id="rect640"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="20.825001"
+     y="18.375"
+     id="rect642"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.125"
+     y="18.375"
+     id="rect644"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.125"
+     y="18.375"
+     id="rect646"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.125"
+     y="18.375"
+     id="rect648"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.424999"
+     y="18.375"
+     id="rect650"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.424999"
+     y="18.375"
+     id="rect652"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.424999"
+     y="18.375"
+     id="rect654"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.15000001"
+     height="0.075000003"
+     x="21.35"
+     y="17.924999"
+     id="rect656"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.15000001"
+     height="0.075000003"
+     x="21.35"
+     y="17.924999"
+     id="rect658"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.15000001"
+     height="0.075000003"
+     x="21.35"
+     y="17.924999"
+     id="rect660"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.299999"
+     y1="17.924999"
+     x2="21.125"
+     y2="17.924999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line662"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.22499999"
+     height="0.22499999"
+     x="20.299999"
+     y="18.299999"
+     id="rect664"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.22499999"
+     height="0.22499999"
+     x="20.299999"
+     y="18.299999"
+     id="rect666"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.22499999"
+     height="0.22499999"
+     x="20.299999"
+     y="18.299999"
+     id="rect668"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.05"
+     height="0.075000003"
+     x="20.375"
+     y="17.25"
+     id="rect670"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.05"
+     height="0.075000003"
+     x="20.375"
+     y="17.25"
+     id="rect672"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.05"
+     height="0.075000003"
+     x="20.375"
+     y="17.25"
+     id="rect674"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.375"
+     y1="17.775"
+     x2="21.049999"
+     y2="17.775"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line676"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.049999"
+     y1="17.85"
+     x2="20.975"
+     y2="17.85"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line678"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.375"
+     y1="17.85"
+     x2="20.450001"
+     y2="17.85"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line680"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.375"
+     height="0.075000003"
+     x="20.525"
+     y="17.775"
+     id="rect682"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.375"
+     height="0.075000003"
+     x="20.525"
+     y="17.775"
+     id="rect684"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.375"
+     height="0.075000003"
+     x="20.525"
+     y="17.775"
+     id="rect686"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.375"
+     y1="17.4"
+     x2="20.450001"
+     y2="17.4"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line688"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.525"
+     y1="17.4"
+     x2="20.6"
+     y2="17.4"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line690"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.275"
+     y1="17.4"
+     x2="21.424999"
+     y2="17.4"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.575001"
+     y1="19.125"
+     x2="20.225"
+     y2="19.125"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.225"
+     y1="19.049999"
+     x2="21.575001"
+     y2="19.049999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.575001"
+     y1="18.975"
+     x2="20.225"
+     y2="18.975"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line698"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.225"
+     y1="18.9"
+     x2="21.575001"
+     y2="18.9"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line700"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.575001"
+     y1="18.825001"
+     x2="20.225"
+     y2="18.825001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line702"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.225"
+     y1="18.75"
+     x2="21.575001"
+     y2="18.75"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line704"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.575001"
+     y1="18.674999"
+     x2="20.225"
+     y2="18.674999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line706"
+     style="stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="18.371,16.685 18.313,16.709 18.137,17.147 18.137,17.366 18.225,17.439 19.51,17.439 19.598,17.366 19.598,17.147 19.422,16.709 19.364,16.685 18.371,16.685 "
+     id="polygon708"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="18.371,16.685 18.313,16.709 18.137,17.147 18.137,17.366 18.225,17.439 19.51,17.439 19.598,17.366 19.598,17.147 19.422,16.709 19.364,16.685 18.371,16.685 "
+     id="polygon710"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 18.167,17.074 L 18.225,17.099 L 19.51,17.099 L 19.568,17.074"
+     id="path712"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 19.51,17.099 L 19.598,17.147"
+     id="path714"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 18.137,17.147 L 18.225,17.099"
+     id="path716"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="18.546,16.223 18.517,16.807 19.218,16.807 19.189,16.223 18.546,16.223 "
+     id="polygon718"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="18.546,16.223 18.517,16.807 19.218,16.807 19.189,16.223 18.546,16.223 "
+     id="polygon720"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="18.429,16.807 18.371,16.977 19.364,16.977 19.306,16.807 18.429,16.807 "
+     id="polygon722"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="18.429,16.807 18.371,16.977 19.364,16.977 19.306,16.807 18.429,16.807 "
+     id="polygon724"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="18.429001"
+     cy="17.184"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse726"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.429001"
+     cy="17.184"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse728"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.575001"
+     cy="17.184"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse730"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.575001"
+     cy="17.184"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse732"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.721001"
+     cy="17.184"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse734"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.721001"
+     cy="17.184"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse736"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.429001"
+     cy="17.245001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse738"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.429001"
+     cy="17.245001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse740"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.575001"
+     cy="17.245001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse742"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.575001"
+     cy="17.245001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse744"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.721001"
+     cy="17.245001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse746"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.721001"
+     cy="17.245001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse748"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.429001"
+     cy="17.305"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse750"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.429001"
+     cy="17.305"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse752"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.575001"
+     cy="17.305"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse754"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.575001"
+     cy="17.305"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse756"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.721001"
+     cy="17.305"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse758"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.721001"
+     cy="17.305"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse760"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.429001"
+     cy="17.365999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse762"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.429001"
+     cy="17.365999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse764"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.575001"
+     cy="17.365999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse766"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.575001"
+     cy="17.365999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse768"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.721001"
+     cy="17.365999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse770"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.721001"
+     cy="17.365999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse772"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.867001"
+     cy="17.195999"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse774"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="18.867001"
+     cy="17.195999"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse776"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.233"
+     cy="17.195999"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse778"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="19.233"
+     cy="17.195999"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse780"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="16.448"
+     y="16.233"
+     id="rect782"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="16.448"
+     y="16.233"
+     id="rect784"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="16.568001"
+     y="16.353001"
+     id="rect786"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="16.598,17.066 17.17,17.066 17.17,17.196 16.628,17.196 16.598,17.066 "
+     id="polygon788"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.598,17.066 17.17,17.066 17.17,17.196 16.628,17.196 16.598,17.066 "
+     id="polygon790"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.17,17.066 17.409,17.066 17.379,17.196 17.17,17.196 17.17,17.066 "
+     id="polygon792"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.17,17.066 17.409,17.066 17.379,17.196 17.17,17.196 17.17,17.066 "
+     id="polygon794"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="17.209"
+     y="17.105"
+     id="rect796"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="17.209"
+     y="17.105"
+     id="rect798"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.892,17.196 17.114,17.196 17.114,17.261 17.226,17.261 17.226,17.326 16.781,17.326 16.781,17.261 16.892,17.261 16.892,17.196 "
+     id="polygon800"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.892,17.196 17.114,17.196 17.114,17.261 17.226,17.261 17.226,17.326 16.781,17.326 16.781,17.261 16.892,17.261 16.892,17.196 "
+     id="polygon802"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="14.573"
+     y="16.207001"
+     id="rect804"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="14.573"
+     y="16.207001"
+     id="rect806"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="14.693"
+     y="16.327999"
+     id="rect808"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="14.723,17.041 15.295,17.041 15.295,17.171 14.753,17.171 14.723,17.041 "
+     id="polygon810"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="14.723,17.041 15.295,17.041 15.295,17.171 14.753,17.171 14.723,17.041 "
+     id="polygon812"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="15.295,17.041 15.534,17.041 15.504,17.171 15.295,17.171 15.295,17.041 "
+     id="polygon814"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.295,17.041 15.534,17.041 15.504,17.171 15.295,17.171 15.295,17.041 "
+     id="polygon816"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="15.334"
+     y="17.08"
+     id="rect818"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="15.334"
+     y="17.08"
+     id="rect820"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="15.017,17.171 15.239,17.171 15.239,17.236 15.351,17.236 15.351,17.301 14.906,17.301 14.906,17.236 15.017,17.236 15.017,17.171 "
+     id="polygon822"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.017,17.171 15.239,17.171 15.239,17.236 15.351,17.236 15.351,17.301 14.906,17.301 14.906,17.236 15.017,17.236 15.017,17.171 "
+     id="polygon824"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="12.798"
+     y="16.233"
+     id="rect826"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="12.798"
+     y="16.233"
+     id="rect828"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="12.918"
+     y="16.353001"
+     id="rect830"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="12.948,17.066 13.52,17.066 13.52,17.196 12.978,17.196 12.948,17.066 "
+     id="polygon832"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="12.948,17.066 13.52,17.066 13.52,17.196 12.978,17.196 12.948,17.066 "
+     id="polygon834"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="13.52,17.066 13.759,17.066 13.729,17.196 13.52,17.196 13.52,17.066 "
+     id="polygon836"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="13.52,17.066 13.759,17.066 13.729,17.196 13.52,17.196 13.52,17.066 "
+     id="polygon838"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="13.559"
+     y="17.105"
+     id="rect840"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="13.559"
+     y="17.105"
+     id="rect842"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="13.242,17.196 13.464,17.196 13.464,17.261 13.576,17.261 13.576,17.326 13.131,17.326 13.131,17.261 13.242,17.261 13.242,17.196 "
+     id="polygon844"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="13.242,17.196 13.464,17.196 13.464,17.261 13.576,17.261 13.576,17.326 13.131,17.326 13.131,17.261 13.242,17.261 13.242,17.196 "
+     id="polygon846"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.531"
+     height="1.351"
+     x="22.747"
+     y="16.533001"
+     id="rect848"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="23.513"
+     cy="17.884001"
+     rx="0.76599997"
+     ry="0.22499999"
+     id="ellipse850"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="23.513"
+     cy="16.533001"
+     rx="0.76599997"
+     ry="0.22499999"
+     id="ellipse852"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="23.513"
+     cy="16.533001"
+     rx="0.76599997"
+     ry="0.22499999"
+     id="ellipse854"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 24.279,16.533 L 24.279,17.884 C 24.279,18.008 23.936,18.109 23.513,18.109 C 23.09,18.109 22.747,18.008 22.747,17.884 L 22.747,16.533"
+     id="path856"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="21.598"
+     y1="16.933001"
+     x2="22.773001"
+     y2="16.933001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line858"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="23.191"
+     y="17.372"
+     id="text860"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
+  <text
+     x="19.969999"
+     y="13.565"
+     id="text862"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
+  <text
+     x="14.375"
+     y="14.915"
+     id="text864"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.8.0/22</text>
+  <text
+     x="20.979"
+     y="14.872"
+     id="text866"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="21.68"
+     y="15.472"
+     id="text868"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2</text>
+  <line
+     x1="3.924"
+     y1="15.258"
+     x2="11.127"
+     y2="15.25"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line870"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="3.974"
+     y1="15.257"
+     x2="3.9749999"
+     y2="16.25"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line872"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="3.974"
+     y1="15.257"
+     x2="3.973"
+     y2="13.982"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line874"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.5970001"
+     y1="15.255"
+     x2="6.598"
+     y2="16.221001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line876"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.1079998"
+     y1="15.253"
+     x2="8.1079998"
+     y2="15.268"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line878"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.7959995"
+     y1="15.253"
+     x2="8.7980003"
+     y2="16.292999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line880"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="11.077"
+     y1="15.25"
+     x2="11.079"
+     y2="16.25"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line882"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.6670001"
+     height="2.5"
+     x="3.142"
+     y="16.25"
+     id="rect884"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.6670001"
+     height="2.5"
+     x="3.142"
+     y="16.25"
+     id="rect886"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.6670001"
+     height="2.5"
+     x="3.142"
+     y="16.25"
+     id="rect888"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.3329999"
+     height="1"
+     x="3.2249999"
+     y="16.333"
+     id="rect890"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.3329999"
+     height="1"
+     x="3.2249999"
+     y="16.333"
+     id="rect892"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.3329999"
+     height="1"
+     x="3.2249999"
+     y="16.333"
+     id="rect894"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.2249999"
+     y1="16.667"
+     x2="4.5580001"
+     y2="16.667"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line896"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.5580001"
+     y1="17"
+     x2="3.2249999"
+     y2="17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line898"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.917"
+     height="0.5"
+     x="3.392"
+     y="17.417"
+     id="rect900"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.917"
+     height="0.5"
+     x="3.392"
+     y="17.417"
+     id="rect902"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.917"
+     height="0.5"
+     x="3.392"
+     y="17.417"
+     id="rect904"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.142"
+     y1="18.167"
+     x2="4.8080001"
+     y2="18.167"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line906"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.3080001"
+     y="18"
+     id="rect908"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.3080001"
+     y="18"
+     id="rect910"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.3080001"
+     y="18"
+     id="rect912"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.4749999"
+     y="18"
+     id="rect914"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.4749999"
+     y="18"
+     id="rect916"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.4749999"
+     y="18"
+     id="rect918"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.6420002"
+     y="18"
+     id="rect920"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.6420002"
+     y="18"
+     id="rect922"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.6420002"
+     y="18"
+     id="rect924"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="4.5580001"
+     y="17.75"
+     id="rect926"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="4.5580001"
+     y="17.75"
+     id="rect928"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="4.5580001"
+     y="17.75"
+     id="rect930"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.392"
+     y1="17.667"
+     x2="4.3080001"
+     y2="17.667"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line932"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="4.4749999"
+     y="17.417"
+     id="rect934"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="4.4749999"
+     y="17.417"
+     id="rect936"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="4.4749999"
+     y="17.417"
+     id="rect938"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.1670001"
+     height="0.082999997"
+     x="3.3080001"
+     y="17.083"
+     id="rect940"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1670001"
+     height="0.082999997"
+     x="3.3080001"
+     y="17.083"
+     id="rect942"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1670001"
+     height="0.082999997"
+     x="3.3080001"
+     y="17.083"
+     id="rect944"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.4749999"
+     y1="17.5"
+     x2="4.2249999"
+     y2="17.5"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line946"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="3.642"
+     y="17.5"
+     id="rect948"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="3.642"
+     y="17.5"
+     id="rect950"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="3.642"
+     y="17.5"
+     id="rect952"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3080001"
+     y1="17.25"
+     x2="4.4749999"
+     y2="17.25"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line954"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.2249999"
+     y1="18.25"
+     x2="4.7249999"
+     y2="18.25"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line956"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.7249999"
+     y1="18.333"
+     x2="3.2249999"
+     y2="18.333"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line958"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.2249999"
+     y1="18.417"
+     x2="4.7249999"
+     y2="18.417"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line960"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.7249999"
+     y1="18.667"
+     x2="3.2249999"
+     y2="18.667"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line962"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.2249999"
+     y1="18.583"
+     x2="4.7249999"
+     y2="18.583"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line964"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.7249999"
+     y1="18.5"
+     x2="3.2249999"
+     y2="18.5"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line966"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.3080001"
+     y1="17.25"
+     x2="3.392"
+     y2="17.25"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line968"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.4749999"
+     y1="17.25"
+     x2="3.5580001"
+     y2="17.25"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line970"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.4749999"
+     y1="17.583"
+     x2="3.5580001"
+     y2="17.583"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line972"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.1420002"
+     y1="17.583"
+     x2="4.2249999"
+     y2="17.583"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line974"
+     style="stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="6.121,16.635 6.063,16.659 5.887,17.097 5.887,17.316 5.975,17.389 7.26,17.389 7.348,17.316 7.348,17.097 7.172,16.659 7.114,16.635 6.121,16.635 "
+     id="polygon976"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.121,16.635 6.063,16.659 5.887,17.097 5.887,17.316 5.975,17.389 7.26,17.389 7.348,17.316 7.348,17.097 7.172,16.659 7.114,16.635 6.121,16.635 "
+     id="polygon978"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.917,17.024 L 5.975,17.049 L 7.26,17.049 L 7.318,17.024"
+     id="path980"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.26,17.049 L 7.348,17.097"
+     id="path982"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.887,17.097 L 5.975,17.049"
+     id="path984"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.296,16.172 6.267,16.757 6.968,16.757 6.939,16.172 6.296,16.172 "
+     id="polygon986"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.296,16.172 6.267,16.757 6.968,16.757 6.939,16.172 6.296,16.172 "
+     id="polygon988"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.179,16.757 6.121,16.927 7.114,16.927 7.056,16.757 6.179,16.757 "
+     id="polygon990"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.179,16.757 6.121,16.927 7.114,16.927 7.056,16.757 6.179,16.757 "
+     id="polygon992"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="6.1789999"
+     cy="17.134001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse994"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1789999"
+     cy="17.134001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse996"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3249998"
+     cy="17.134001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse998"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3249998"
+     cy="17.134001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1000"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="17.134001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1002"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="17.134001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1004"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1789999"
+     cy="17.195"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1006"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1789999"
+     cy="17.195"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1008"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3249998"
+     cy="17.195"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1010"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3249998"
+     cy="17.195"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1012"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="17.195"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1014"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="17.195"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1016"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1789999"
+     cy="17.254999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1018"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1789999"
+     cy="17.254999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1020"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3249998"
+     cy="17.254999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1022"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3249998"
+     cy="17.254999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1024"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="17.254999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1026"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="17.254999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1028"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1789999"
+     cy="17.316"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1030"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1789999"
+     cy="17.316"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1032"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3249998"
+     cy="17.316"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1034"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3249998"
+     cy="17.316"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1036"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="17.316"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1038"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="17.316"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse1040"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.6170001"
+     cy="17.146"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse1042"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="6.6170001"
+     cy="17.146"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse1044"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.9829998"
+     cy="17.146"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse1046"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="6.9829998"
+     cy="17.146"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse1048"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="10.473"
+     y="16.257999"
+     id="rect1050"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="10.473"
+     y="16.257999"
+     id="rect1052"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="10.593"
+     y="16.378"
+     id="rect1054"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="10.623,17.091 11.195,17.091 11.195,17.221 10.653,17.221 10.623,17.091 "
+     id="polygon1056"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="10.623,17.091 11.195,17.091 11.195,17.221 10.653,17.221 10.623,17.091 "
+     id="polygon1058"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="11.195,17.091 11.434,17.091 11.404,17.221 11.195,17.221 11.195,17.091 "
+     id="polygon1060"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="11.195,17.091 11.434,17.091 11.404,17.221 11.195,17.221 11.195,17.091 "
+     id="polygon1062"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="11.234"
+     y="17.129999"
+     id="rect1064"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="11.234"
+     y="17.129999"
+     id="rect1066"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="10.917,17.221 11.139,17.221 11.139,17.286 11.251,17.286 11.251,17.351 10.806,17.351 10.806,17.286 10.917,17.286 10.917,17.221 "
+     id="polygon1068"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="10.917,17.221 11.139,17.221 11.139,17.286 11.251,17.286 11.251,17.351 10.806,17.351 10.806,17.286 10.917,17.286 10.917,17.221 "
+     id="polygon1070"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="8.2729998"
+     y="16.282"
+     id="rect1072"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="8.2729998"
+     y="16.282"
+     id="rect1074"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="8.3929996"
+     y="16.403"
+     id="rect1076"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="8.423,17.116 8.995,17.116 8.995,17.246 8.453,17.246 8.423,17.116 "
+     id="polygon1078"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.423,17.116 8.995,17.116 8.995,17.246 8.453,17.246 8.423,17.116 "
+     id="polygon1080"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.995,17.116 9.234,17.116 9.204,17.246 8.995,17.246 8.995,17.116 "
+     id="polygon1082"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.995,17.116 9.234,17.116 9.204,17.246 8.995,17.246 8.995,17.116 "
+     id="polygon1084"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="9.0340004"
+     y="17.155001"
+     id="rect1086"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="9.0340004"
+     y="17.155001"
+     id="rect1088"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.717,17.246 8.939,17.246 8.939,17.311 9.051,17.311 9.051,17.376 8.606,17.376 8.606,17.311 8.717,17.311 8.717,17.246 "
+     id="polygon1090"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.717,17.246 8.939,17.246 8.939,17.311 9.051,17.311 9.051,17.376 8.606,17.376 8.606,17.311 8.717,17.311 8.717,17.246 "
+     id="polygon1092"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.53"
+     height="1.35"
+     x="0.51999998"
+     y="16.433001"
+     id="rect1094"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="1.285"
+     cy="17.783001"
+     rx="0.76499999"
+     ry="0.22499999"
+     id="ellipse1096"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.285"
+     cy="16.433001"
+     rx="0.76499999"
+     ry="0.22499999"
+     id="ellipse1098"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.285"
+     cy="16.433001"
+     rx="0.76499999"
+     ry="0.22499999"
+     id="ellipse1100"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 2.051,16.433 L 2.051,17.783 C 2.051,17.907 1.708,18.008 1.285,18.008 C 0.863,18.008 0.52,17.907 0.52,17.783 L 0.52,16.433"
+     id="path1102"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="1.998"
+     y1="16.832001"
+     x2="3.1719999"
+     y2="16.832001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1104"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.97399998"
+     y="17.322001"
+     id="text1106"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
+  <text
+     x="2.102"
+     y="13.872"
+     id="text1108"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
+  <text
+     x="6.6999998"
+     y="14.915"
+     id="text1110"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.4.0/22</text>
+  <text
+     x="0.42899999"
+     y="15.372"
+     id="text1112"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="1.13"
+     y="15.972"
+     id="text1114"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG1</text>
+  <text
+     x="9.4289999"
+     y="20.072001"
+     id="text1116"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
+  <text
+     x="22.027"
+     y="20.183001"
+     id="text1118"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">150 Users</text>
+  <text
+     x="18.612"
+     y="11.758"
+     id="text1120"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">300 Users</text>
+  <text
+     x="0.22499999"
+     y="20.048"
+     id="text1122"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounting</text>
+  <text
+     x="14.062"
+     y="20.108"
+     id="text1124"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Financial Services</text>
+  <text
+     x="15.152"
+     y="4.408"
+     id="text1126"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Property Insurance Group</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap6-net.svg b/docs-xml/Samba3-ByExample/images/chap6-net.svg
new file mode 100644
index 00000000000..6cabfad842b
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap6-net.svg
@@ -0,0 +1,3714 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="25.25cm"
+   height="17.834999cm"
+   viewBox="-0.157 2.112 25.093 19.947"
+   id="svg2">
+  <defs
+     id="defs1143" />
+  <rect
+     width="16.360001"
+     height="9.5100002"
+     x="5.6950002"
+     y="2.1370001"
+     id="rect4"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 5.695,2.137 C 5.5293146,2.137 5.395,2.2713146 5.395,2.437"
+     id="path6"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.355,2.437 C 22.355,2.2713146 22.220685,2.137 22.055,2.137"
+     id="path8"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="16.959999"
+     height="8.9099998"
+     x="5.395"
+     y="2.437"
+     id="rect10"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 5.395,11.347 C 5.395,11.512685 5.5293146,11.647 5.695,11.647"
+     id="path12"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.055,11.647 C 22.220685,11.647 22.355,11.512685 22.355,11.347"
+     id="path14"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="5.6950002"
+     y1="2.1370001"
+     x2="22.055"
+     y2="2.1370001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="5.6950002"
+     y1="11.647"
+     x2="22.055"
+     y2="11.647"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 5.695,2.137 C 5.5293146,2.137 5.395,2.2713146 5.395,2.437"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.355,2.437 C 22.355,2.2713146 22.220685,2.137 22.055,2.137"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="5.395"
+     y1="2.437"
+     x2="5.395"
+     y2="11.347"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="22.355"
+     y1="2.437"
+     x2="22.355"
+     y2="11.347"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 5.395,11.347 C 5.395,11.512685 5.5293146,11.647 5.695,11.647"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.055,11.647 C 22.220685,11.647 22.355,11.512685 22.355,11.347"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="11.6"
+     height="7.875"
+     x="13.168"
+     y="12.047"
+     id="rect32"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 13.168,12.047 C 13.002315,12.047 12.868,12.181315 12.868,12.347"
+     id="path34"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 25.068,12.347 C 25.068,12.181315 24.933685,12.047 24.768,12.047"
+     id="path36"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="12.2"
+     height="7.2750001"
+     x="12.868"
+     y="12.347"
+     id="rect38"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.868,19.622 C 12.868,19.787685 13.002315,19.922 13.168,19.922"
+     id="path40"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 24.768,19.922 C 24.933685,19.922 25.068,19.787685 25.068,19.622"
+     id="path42"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="13.168"
+     y1="12.047"
+     x2="24.768"
+     y2="12.047"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line44"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="13.168"
+     y1="19.922001"
+     x2="24.768"
+     y2="19.922001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 13.168,12.047 C 13.002315,12.047 12.868,12.181315 12.868,12.347"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 25.068,12.347 C 25.068,12.181315 24.933685,12.047 24.768,12.047"
+     id="path50"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.868"
+     y1="12.347"
+     x2="12.868"
+     y2="19.622"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="25.068001"
+     y1="12.347"
+     x2="25.068001"
+     y2="19.622"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line54"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.868,19.622 C 12.868,19.787685 13.002315,19.922 13.168,19.922"
+     id="path56"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 24.768,19.922 C 24.933685,19.922 25.068,19.787685 25.068,19.622"
+     id="path58"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="11.225"
+     height="7.8499999"
+     x="0.168"
+     y="12.047"
+     id="rect60"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.168,12.047 C 0.0023145751,12.047 -0.132,12.181315 -0.132,12.347"
+     id="path62"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.693,12.347 C 11.693,12.181315 11.558685,12.047 11.393,12.047"
+     id="path64"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.825"
+     height="7.25"
+     x="-0.132"
+     y="12.347"
+     id="rect66"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -0.132,19.597 C -0.132,19.762685 0.0023145751,19.897 0.168,19.897"
+     id="path68"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.393,19.897 C 11.558685,19.897 11.693,19.762685 11.693,19.597"
+     id="path70"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="0.168"
+     y1="12.047"
+     x2="11.393"
+     y2="12.047"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.168"
+     y1="19.896999"
+     x2="11.393"
+     y2="19.896999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.168,12.047 C 0.0023145751,12.047 -0.132,12.181315 -0.132,12.347"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.693,12.347 C 11.693,12.181315 11.558685,12.047 11.393,12.047"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-0.132"
+     y1="12.347"
+     x2="-0.132"
+     y2="19.597"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.693"
+     y1="12.347"
+     x2="11.693"
+     y2="19.597"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -0.132,19.597 C -0.132,19.762685 0.0023145751,19.897 0.168,19.897"
+     id="path84"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.393,19.897 C 11.558685,19.897 11.693,19.762685 11.693,19.597"
+     id="path86"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.138,4.153 C 0.732,4.143 -0.057,4.345 0.054,4.777 C 0.165,5.209 0.695,5.305 0.917,5.18 C 1.138,5.055 0.571,5.785 1.656,5.977 C 2.741,6.169 3.295,5.861 3.135,5.641 C 2.975,5.42 4.084,6.159 4.602,5.737 C 5.119,5.314 4.072,4.911 4.293,4.969 C 4.515,5.026 5.193,4.95 4.971,4.23 C 4.749,3.51 2.753,4.067 2.975,3.961 C 3.197,3.855 2.642,3.328 1.952,3.433 C 1.262,3.539 1.213,3.73 1.139,4.153 L 1.138,4.153"
+     id="path88"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 1.138,4.153 C 0.732,4.143 -0.057,4.345 0.054,4.777 C 0.165,5.209 0.695,5.305 0.917,5.18 C 1.138,5.055 0.571,5.785 1.656,5.977 C 2.741,6.169 3.295,5.861 3.135,5.641 C 2.975,5.42 4.084,6.159 4.602,5.737 C 5.119,5.314 4.072,4.911 4.293,4.969 C 4.515,5.026 5.193,4.95 4.971,4.23 C 4.749,3.51 2.753,4.067 2.975,3.961 C 3.197,3.855 2.642,3.328 1.952,3.433 C 1.262,3.539 1.213,3.73 1.139,4.153 L 1.138,4.153"
+     id="path90"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.1010001"
+     y="4.848"
+     id="text92"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
+  <rect
+     width="1.054"
+     height="2.1070001"
+     x="5.7290001"
+     y="6.2870002"
+     id="rect94"
+     style="fill:#ff0000;stroke:none;stroke-width:0" />
+  <polygon
+     points="5.729,6.287 6.783,6.287 6.915,6.156 5.861,6.156 5.729,6.287 "
+     id="polygon96"
+     style="fill:#ff0000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="6.783,6.287 6.915,6.156 6.915,8.263 6.783,8.394 6.783,6.287 "
+     id="polygon98"
+     style="fill:#ff0000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="6.4980001"
+     x2="6.783"
+     y2="6.4980001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line100"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="6.3660002"
+     x2="6.783"
+     y2="6.4980001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line102"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.0450001"
+     y1="6.2870002"
+     x2="6.0450001"
+     y2="6.4980001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line104"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.0450001"
+     y1="6.2870002"
+     x2="6.177"
+     y2="6.1560001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line106"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="6.9190001"
+     x2="6.783"
+     y2="6.9190001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line108"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="6.7880001"
+     x2="6.783"
+     y2="6.9190001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line110"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.467"
+     y1="6.4980001"
+     x2="6.467"
+     y2="6.9190001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line112"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="7.3410001"
+     x2="6.783"
+     y2="7.3410001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line114"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="7.2090001"
+     x2="6.783"
+     y2="7.3410001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line116"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.0450001"
+     y1="6.9190001"
+     x2="6.0450001"
+     y2="7.3410001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line118"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="7.7620001"
+     x2="6.783"
+     y2="7.7620001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line120"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="7.631"
+     x2="6.783"
+     y2="7.7620001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line122"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.467"
+     y1="7.3410001"
+     x2="6.467"
+     y2="7.7620001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line124"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="8.184"
+     x2="6.783"
+     y2="8.184"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line126"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.915"
+     y1="8.052"
+     x2="6.783"
+     y2="8.184"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line128"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.0450001"
+     y1="7.7620001"
+     x2="6.0450001"
+     y2="8.184"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line130"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="6.467"
+     y1="8.184"
+     x2="6.467"
+     y2="8.3940001"
+     stroke="#FFFFFF"
+     stroke-width="0.100"
+     id="line132"
+     style="stroke:#ffffff;stroke-width:0.1" />
+  <line
+     x1="5.7290001"
+     y1="6.2870002"
+     x2="6.783"
+     y2="6.2870002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line134"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="6.783"
+     y1="8.3940001"
+     x2="6.783"
+     y2="6.2870002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="6.783"
+     y1="6.2870002"
+     x2="6.915"
+     y2="6.1560001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.05" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.050"
+     points="5.729,6.287 5.861,6.156 6.915,6.156 6.915,8.263 6.783,8.394 5.729,8.394 5.729,6.287 "
+     id="polyline140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="2.0050001"
+     height="6.0149999"
+     x="8.4580002"
+     y="4.1360002"
+     id="rect142"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.0050001"
+     height="6.0149999"
+     x="8.4580002"
+     y="4.1360002"
+     id="rect144"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.0050001"
+     height="6.0149999"
+     x="8.4580002"
+     y="4.1360002"
+     id="rect146"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.604"
+     height="2.4059999"
+     x="8.6590004"
+     y="4.3369999"
+     id="rect148"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.604"
+     height="2.4059999"
+     x="8.6590004"
+     y="4.3369999"
+     id="rect150"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.604"
+     height="2.4059999"
+     x="8.6590004"
+     y="4.3369999"
+     id="rect152"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.6590004"
+     y1="4.7379999"
+     x2="10.263"
+     y2="4.7379999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line154"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.263"
+     y1="5.1389999"
+     x2="8.6590004"
+     y2="5.1389999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line156"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.6590004"
+     y1="5.54"
+     x2="10.263"
+     y2="5.54"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line158"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.6590004"
+     y1="5.941"
+     x2="10.263"
+     y2="5.941"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line160"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.263"
+     y1="6.342"
+     x2="8.6590004"
+     y2="6.342"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line162"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.103"
+     height="0.60100001"
+     x="8.6590004"
+     y="6.9429998"
+     id="rect164"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.103"
+     height="0.60100001"
+     x="8.6590004"
+     y="6.9429998"
+     id="rect166"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.103"
+     height="0.60100001"
+     x="8.6590004"
+     y="6.9429998"
+     id="rect168"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.4580002"
+     y1="7.9460001"
+     x2="10.463"
+     y2="7.9460001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line170"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.3610001"
+     y="8.1459999"
+     id="rect172"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.3610001"
+     y="8.1459999"
+     id="rect174"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.3610001"
+     y="8.1459999"
+     id="rect176"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.7620001"
+     y="8.1459999"
+     id="rect178"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.7620001"
+     y="8.1459999"
+     id="rect180"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="9.7620001"
+     y="8.1459999"
+     id="rect182"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="10.163"
+     y="8.1459999"
+     id="rect184"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="10.163"
+     y="8.1459999"
+     id="rect186"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.1"
+     height="0.1"
+     x="10.163"
+     y="8.1459999"
+     id="rect188"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.2"
+     height="0.2"
+     x="10.062"
+     y="7.5450001"
+     id="rect190"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.2"
+     height="0.2"
+     x="10.062"
+     y="7.5450001"
+     id="rect192"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.2"
+     height="0.2"
+     x="10.062"
+     y="7.5450001"
+     id="rect194"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.6590004"
+     y1="7.244"
+     x2="9.7620001"
+     y2="7.244"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line196"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.301"
+     height="0.301"
+     x="8.6590004"
+     y="8.0459995"
+     id="rect198"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.301"
+     height="0.301"
+     x="8.6590004"
+     y="8.0459995"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.301"
+     height="0.301"
+     x="8.6590004"
+     y="8.0459995"
+     id="rect202"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.403"
+     height="0.1"
+     x="8.7589998"
+     y="6.4419999"
+     id="rect204"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.403"
+     height="0.1"
+     x="8.7589998"
+     y="6.4419999"
+     id="rect206"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.403"
+     height="0.1"
+     x="8.7589998"
+     y="6.4419999"
+     id="rect208"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.7589998"
+     y1="7.0430002"
+     x2="9.6610003"
+     y2="7.0430002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line210"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.6610003"
+     y1="7.1440001"
+     x2="9.5609999"
+     y2="7.1440001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line212"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.7589998"
+     y1="7.1440001"
+     x2="8.8590002"
+     y2="7.1440001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line214"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.50099999"
+     height="0.1"
+     x="8.96"
+     y="7.0430002"
+     id="rect216"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.50099999"
+     height="0.1"
+     x="8.96"
+     y="7.0430002"
+     id="rect218"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.50099999"
+     height="0.1"
+     x="8.96"
+     y="7.0430002"
+     id="rect220"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.7589998"
+     y1="6.6420002"
+     x2="8.8590002"
+     y2="6.6420002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line222"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.96"
+     y1="6.6420002"
+     x2="9.0600004"
+     y2="6.6420002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line224"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.9619999"
+     y1="6.6420002"
+     x2="10.163"
+     y2="6.6420002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line226"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="10.051"
+     x2="10.363"
+     y2="10.051"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line228"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.9510002"
+     x2="8.559"
+     y2="9.9510002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line230"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.8500004"
+     x2="10.363"
+     y2="9.8500004"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line232"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.75"
+     x2="8.559"
+     y2="9.75"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line234"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.6499996"
+     x2="10.363"
+     y2="9.6499996"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line236"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.5500002"
+     x2="8.559"
+     y2="9.5500002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line238"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.4490004"
+     x2="10.363"
+     y2="9.4490004"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line240"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.349"
+     x2="8.559"
+     y2="9.349"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line242"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.2489996"
+     x2="10.363"
+     y2="9.2489996"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line244"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="9.1490002"
+     x2="8.559"
+     y2="9.1490002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line246"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="9.0480003"
+     x2="10.363"
+     y2="9.0480003"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line248"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="8.948"
+     x2="8.559"
+     y2="8.948"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line250"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.559"
+     y1="8.8479996"
+     x2="10.363"
+     y2="8.8479996"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line252"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.363"
+     y1="8.7480001"
+     x2="8.559"
+     y2="8.7480001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line254"
+     style="stroke:#000000;stroke-width:0.01" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="2.299,6.038 2.299,7.250 5.700,7.250 5.700,7.300 "
+     id="polyline256"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.875"
+     y1="7.3000002"
+     x2="8.4250002"
+     y2="7.2750001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line258"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.454"
+     height="1.283"
+     x="11.484"
+     y="4.0939999"
+     id="rect260"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="12.211"
+     cy="5.3759999"
+     rx="0.727"
+     ry="0.214"
+     id="ellipse262"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.211"
+     cy="4.0939999"
+     rx="0.727"
+     ry="0.214"
+     id="ellipse264"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.211"
+     cy="4.0939999"
+     rx="0.727"
+     ry="0.214"
+     id="ellipse266"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 12.938,4.094 L 12.938,5.376 C 12.938,5.494 12.613,5.59 12.211,5.59 C 11.81,5.59 11.484,5.494 11.484,5.376 L 11.484,4.094"
+     id="path268"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.3329999"
+     height="1.176"
+     x="11.484"
+     y="6.493"
+     id="rect270"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="12.15"
+     cy="7.6690001"
+     rx="0.66600001"
+     ry="0.19599999"
+     id="ellipse272"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.15"
+     cy="6.493"
+     rx="0.66600001"
+     ry="0.19599999"
+     id="ellipse274"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.15"
+     cy="6.493"
+     rx="0.66600001"
+     ry="0.19599999"
+     id="ellipse276"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 12.817,6.493 L 12.817,7.669 C 12.817,7.777 12.518,7.865 12.15,7.865 C 11.782,7.865 11.484,7.777 11.484,7.669 L 11.484,6.493"
+     id="path278"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.475"
+     y1="4.6750002"
+     x2="11.55"
+     y2="4.6750002"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line280"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.45"
+     y1="7.0250001"
+     x2="11.455"
+     y2="6.9970002"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line282"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.4"
+     y1="8.8000002"
+     x2="21.017"
+     y2="8.7969999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line284"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="20.954"
+     y1="8.7969999"
+     x2="20.952999"
+     y2="7.9260001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line286"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="15.678"
+     y1="8.7980003"
+     x2="15.678"
+     y2="7.9169998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line288"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="15.68"
+     y1="8.7980003"
+     x2="15.68"
+     y2="9.8470001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line290"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.254"
+     y1="8.7980003"
+     x2="18.253"
+     y2="7.9260001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line292"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.243"
+     y1="8.7980003"
+     x2="18.243"
+     y2="9.8999996"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line294"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="20.966999"
+     y1="8.7969999"
+     x2="20.966999"
+     y2="9.9189997"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line296"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1"
+     height="1"
+     x="11.825"
+     y="10.625"
+     id="rect298"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="1"
+     height="1"
+     x="11.825"
+     y="10.625"
+     id="rect300"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1"
+     height="1"
+     x="11.825"
+     y="10.625"
+     id="rect302"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 12.387,10.787 C 12.387,11.287 12.487,11.187 11.987,11.187"
+     id="path304"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 12.387,10.787 C 12.387,11.287 12.487,11.187 11.987,11.187"
+     id="path306"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="12.435,10.865 12.385,10.765 12.335,10.865 12.435,10.865 "
+     id="polygon308"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.435,10.865 12.385,10.765 12.335,10.865 12.435,10.865 "
+     id="polygon310"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.065,11.135 11.965,11.185 12.065,11.235 12.065,11.135 "
+     id="polygon312"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.065,11.135 11.965,11.185 12.065,11.235 12.065,11.135 "
+     id="polygon314"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 12.684,11.068 C 12.184,11.068 12.284,10.968 12.284,11.468"
+     id="path316"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 12.684,11.068 C 12.184,11.068 12.284,10.968 12.284,11.468"
+     id="path318"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="12.595,11.115 12.695,11.065 12.595,11.015 12.595,11.115 "
+     id="polygon320"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.595,11.115 12.695,11.065 12.595,11.015 12.595,11.115 "
+     id="polygon322"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.225,11.385 12.275,11.485 12.325,11.385 12.225,11.385 "
+     id="polygon324"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.225,11.385 12.275,11.485 12.325,11.385 12.225,11.385 "
+     id="polygon326"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="12.325"
+     y1="8.8249998"
+     x2="12.325"
+     y2="10.625"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line328"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="15.15,10.178 15.095,10.201 14.93,10.615 14.93,10.823 15.012,10.892 16.228,10.892 16.311,10.823 16.311,10.615 16.145,10.201 16.09,10.178 15.15,10.178 "
+     id="polygon330"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="15.15,10.178 15.095,10.201 14.93,10.615 14.93,10.823 15.012,10.892 16.228,10.892 16.311,10.823 16.311,10.615 16.145,10.201 16.09,10.178 15.15,10.178 "
+     id="polygon332"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 14.957,10.546 L 15.012,10.569 L 16.228,10.569 L 16.283,10.546"
+     id="path334"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.228,10.569 L 16.311,10.615"
+     id="path336"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 14.93,10.615 L 15.012,10.569"
+     id="path338"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="15.316,9.741 15.289,10.293 15.951,10.293 15.924,9.741 15.316,9.741 "
+     id="polygon340"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="15.316,9.741 15.289,10.293 15.951,10.293 15.924,9.741 15.316,9.741 "
+     id="polygon342"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="15.206,10.293 15.15,10.454 16.09,10.454 16.034,10.293 15.206,10.293 "
+     id="polygon344"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="15.206,10.293 15.15,10.454 16.09,10.454 16.034,10.293 15.206,10.293 "
+     id="polygon346"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="15.206"
+     cy="10.65"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse348"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.206"
+     cy="10.65"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse350"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.344"
+     cy="10.65"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse352"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.344"
+     cy="10.65"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse354"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.482"
+     cy="10.65"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse356"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.482"
+     cy="10.65"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse358"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.206"
+     cy="10.708"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse360"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.206"
+     cy="10.708"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse362"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.344"
+     cy="10.708"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse364"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.344"
+     cy="10.708"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse366"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.482"
+     cy="10.708"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse368"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.482"
+     cy="10.708"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse370"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.206"
+     cy="10.765"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse372"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.206"
+     cy="10.765"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse374"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.344"
+     cy="10.765"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse376"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.344"
+     cy="10.765"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse378"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.482"
+     cy="10.765"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse380"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.482"
+     cy="10.765"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse382"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.206"
+     cy="10.823"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse384"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.206"
+     cy="10.823"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse386"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.344"
+     cy="10.823"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse388"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.344"
+     cy="10.823"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse390"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.482"
+     cy="10.823"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse392"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="15.482"
+     cy="10.823"
+     rx="0.014"
+     ry="0.014"
+     id="ellipse394"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.62"
+     cy="10.661"
+     rx="0.17299999"
+     ry="0.055"
+     id="ellipse396"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="15.62"
+     cy="10.661"
+     rx="0.17299999"
+     ry="0.055"
+     id="ellipse398"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="15.965"
+     cy="10.661"
+     rx="0.17299999"
+     ry="0.055"
+     id="ellipse400"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="15.965"
+     cy="10.661"
+     rx="0.17299999"
+     ry="0.055"
+     id="ellipse402"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="15.122"
+     y="6.8239999"
+     id="rect404"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="15.122"
+     y="6.8239999"
+     id="rect406"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="15.242"
+     y="6.9439998"
+     id="rect408"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="15.272,7.657 15.844,7.657 15.844,7.787 15.302,7.787 15.272,7.657 "
+     id="polygon410"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.272,7.657 15.844,7.657 15.844,7.787 15.302,7.787 15.272,7.657 "
+     id="polygon412"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="15.844,7.657 16.083,7.657 16.053,7.787 15.844,7.787 15.844,7.657 "
+     id="polygon414"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.844,7.657 16.083,7.657 16.053,7.787 15.844,7.787 15.844,7.657 "
+     id="polygon416"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="15.883"
+     y="7.6960001"
+     id="rect418"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="15.883"
+     y="7.6960001"
+     id="rect420"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="15.566,7.787 15.789,7.787 15.789,7.852 15.9,7.852 15.9,7.917 15.455,7.917 15.455,7.852 15.566,7.852 15.566,7.787 "
+     id="polygon422"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.566,7.787 15.789,7.787 15.789,7.852 15.9,7.852 15.9,7.917 15.455,7.917 15.455,7.852 15.566,7.852 15.566,7.787 "
+     id="polygon424"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="17.698"
+     y="6.8319998"
+     id="rect426"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="17.698"
+     y="6.8319998"
+     id="rect428"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="17.818001"
+     y="6.9530001"
+     id="rect430"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="17.848,7.666 18.42,7.666 18.42,7.796 17.878,7.796 17.848,7.666 "
+     id="polygon432"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.848,7.666 18.42,7.666 18.42,7.796 17.878,7.796 17.848,7.666 "
+     id="polygon434"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.42,7.666 18.659,7.666 18.629,7.796 18.42,7.796 18.42,7.666 "
+     id="polygon436"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.42,7.666 18.659,7.666 18.629,7.796 18.42,7.796 18.42,7.666 "
+     id="polygon438"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="18.459"
+     y="7.7049999"
+     id="rect440"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="18.459"
+     y="7.7049999"
+     id="rect442"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.142,7.796 18.364,7.796 18.364,7.861 18.476,7.861 18.476,7.926 18.031,7.926 18.031,7.861 18.142,7.861 18.142,7.796 "
+     id="polygon444"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.142,7.796 18.364,7.796 18.364,7.861 18.476,7.861 18.476,7.926 18.031,7.926 18.031,7.861 18.142,7.861 18.142,7.796 "
+     id="polygon446"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="20.398001"
+     y="6.8319998"
+     id="rect448"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="20.398001"
+     y="6.8319998"
+     id="rect450"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="20.518"
+     y="6.9530001"
+     id="rect452"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="20.548,7.666 21.12,7.666 21.12,7.796 20.578,7.796 20.548,7.666 "
+     id="polygon454"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.548,7.666 21.12,7.666 21.12,7.796 20.578,7.796 20.548,7.666 "
+     id="polygon456"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="21.12,7.666 21.359,7.666 21.329,7.796 21.12,7.796 21.12,7.666 "
+     id="polygon458"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="21.12,7.666 21.359,7.666 21.329,7.796 21.12,7.796 21.12,7.666 "
+     id="polygon460"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="21.159"
+     y="7.7049999"
+     id="rect462"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="21.159"
+     y="7.7049999"
+     id="rect464"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="20.842,7.796 21.064,7.796 21.064,7.861 21.176,7.861 21.176,7.926 20.731,7.926 20.731,7.861 20.842,7.861 20.842,7.796 "
+     id="polygon466"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.842,7.796 21.064,7.796 21.064,7.861 21.176,7.861 21.176,7.926 20.731,7.926 20.731,7.861 20.842,7.861 20.842,7.796 "
+     id="polygon468"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="17.673"
+     y="9.9320002"
+     id="rect470"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="17.673"
+     y="9.9320002"
+     id="rect472"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="17.792999"
+     y="10.053"
+     id="rect474"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="17.823,10.766 18.395,10.766 18.395,10.896 17.853,10.896 17.823,10.766 "
+     id="polygon476"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.823,10.766 18.395,10.766 18.395,10.896 17.853,10.896 17.823,10.766 "
+     id="polygon478"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.395,10.766 18.634,10.766 18.604,10.896 18.395,10.896 18.395,10.766 "
+     id="polygon480"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.395,10.766 18.634,10.766 18.604,10.896 18.395,10.896 18.395,10.766 "
+     id="polygon482"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="18.434"
+     y="10.805"
+     id="rect484"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="18.434"
+     y="10.805"
+     id="rect486"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.117,10.896 18.339,10.896 18.339,10.961 18.451,10.961 18.451,11.026 18.006,11.026 18.006,10.961 18.117,10.961 18.117,10.896 "
+     id="polygon488"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.117,10.896 18.339,10.896 18.339,10.961 18.451,10.961 18.451,11.026 18.006,11.026 18.006,10.961 18.117,10.961 18.117,10.896 "
+     id="polygon490"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="20.398001"
+     y="9.8830004"
+     id="rect492"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="20.398001"
+     y="9.8830004"
+     id="rect494"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="20.518"
+     y="10.003"
+     id="rect496"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="20.548,10.716 21.12,10.716 21.12,10.846 20.578,10.846 20.548,10.716 "
+     id="polygon498"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.548,10.716 21.12,10.716 21.12,10.846 20.578,10.846 20.548,10.716 "
+     id="polygon500"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="21.12,10.716 21.359,10.716 21.329,10.846 21.12,10.846 21.12,10.716 "
+     id="polygon502"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="21.12,10.716 21.359,10.716 21.329,10.846 21.12,10.846 21.12,10.716 "
+     id="polygon504"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="21.159"
+     y="10.755"
+     id="rect506"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="21.159"
+     y="10.755"
+     id="rect508"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="20.842,10.846 21.064,10.846 21.064,10.911 21.176,10.911 21.176,10.976 20.731,10.976 20.731,10.911 20.842,10.911 20.842,10.846 "
+     id="polygon510"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.842,10.846 21.064,10.846 21.064,10.911 21.176,10.911 21.176,10.976 20.731,10.976 20.731,10.911 20.842,10.911 20.842,10.846 "
+     id="polygon512"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1"
+     height="1"
+     x="18.872"
+     y="12.033"
+     id="rect514"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="1"
+     height="1"
+     x="18.872"
+     y="12.033"
+     id="rect516"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1"
+     height="1"
+     x="18.872"
+     y="12.033"
+     id="rect518"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 19.434,12.194 C 19.434,12.694 19.534,12.594 19.034,12.594"
+     id="path520"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 19.434,12.194 C 19.434,12.694 19.534,12.594 19.034,12.594"
+     id="path522"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="19.482,12.273 19.432,12.173 19.383,12.273 19.482,12.273 "
+     id="polygon524"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.482,12.273 19.432,12.173 19.383,12.273 19.482,12.273 "
+     id="polygon526"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="19.112,12.543 19.012,12.593 19.112,12.643 19.112,12.543 "
+     id="polygon528"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.112,12.543 19.012,12.593 19.112,12.643 19.112,12.543 "
+     id="polygon530"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 19.731,12.476 C 19.231,12.476 19.331,12.376 19.331,12.876"
+     id="path532"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 19.731,12.476 C 19.231,12.476 19.331,12.376 19.331,12.876"
+     id="path534"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="19.642,12.523 19.742,12.473 19.642,12.423 19.642,12.523 "
+     id="polygon536"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.642,12.523 19.742,12.473 19.642,12.423 19.642,12.523 "
+     id="polygon538"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="19.272,12.793 19.322,12.893 19.372,12.793 19.272,12.793 "
+     id="polygon540"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.272,12.793 19.322,12.893 19.372,12.793 19.272,12.793 "
+     id="polygon542"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1"
+     height="1"
+     x="3.1470001"
+     y="12.082"
+     id="rect544"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="1"
+     height="1"
+     x="3.1470001"
+     y="12.082"
+     id="rect546"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1"
+     height="1"
+     x="3.1470001"
+     y="12.082"
+     id="rect548"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.709,12.244 C 3.709,12.744 3.809,12.644 3.309,12.644"
+     id="path550"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 3.709,12.244 C 3.709,12.744 3.809,12.644 3.309,12.644"
+     id="path552"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="3.757,12.322 3.708,12.223 3.657,12.322 3.757,12.322 "
+     id="polygon554"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.757,12.322 3.708,12.223 3.657,12.322 3.757,12.322 "
+     id="polygon556"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.388,12.592 3.288,12.643 3.388,12.692 3.388,12.592 "
+     id="polygon558"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.388,12.592 3.288,12.643 3.388,12.692 3.388,12.592 "
+     id="polygon560"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 4.006,12.526 C 3.506,12.526 3.606,12.426 3.606,12.926"
+     id="path562"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 4.006,12.526 C 3.506,12.526 3.606,12.426 3.606,12.926"
+     id="path564"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="3.917,12.572 4.018,12.522 3.917,12.473 3.917,12.572 "
+     id="polygon566"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.917,12.572 4.018,12.522 3.917,12.473 3.917,12.572 "
+     id="polygon568"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.547,12.842 3.598,12.942 3.647,12.842 3.547,12.842 "
+     id="polygon570"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.547,12.842 3.598,12.942 3.647,12.842 3.547,12.842 "
+     id="polygon572"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="12.025,11.650 12.025,12.525 4.147,12.525 4.147,12.582 "
+     id="polyline574"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="12.625,11.600 12.625,12.525 18.872,12.525 18.872,12.533 "
+     id="polyline576"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="3.599"
+     y1="14.358"
+     x2="10.802"
+     y2="14.35"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line578"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="3.6489999"
+     y1="14.357"
+     x2="3.6500001"
+     y2="15.35"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line580"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="3.6489999"
+     y1="14.357"
+     x2="3.6470001"
+     y2="13.082"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line582"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.2719998"
+     y1="14.355"
+     x2="6.2729998"
+     y2="15.321"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line584"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="7.783"
+     y1="14.353"
+     x2="7.783"
+     y2="14.368"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line586"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.4709997"
+     y1="14.353"
+     x2="8.4729996"
+     y2="15.393"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line588"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.752"
+     y1="14.35"
+     x2="10.754"
+     y2="15.35"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line590"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.775"
+     y1="14.325"
+     x2="21.35"
+     y2="14.325"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line592"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="15.593"
+     y1="14.325"
+     x2="15.593"
+     y2="15.325"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line594"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.825"
+     y1="14.325"
+     x2="13.825"
+     y2="15.325"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line596"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.479"
+     y1="14.325"
+     x2="17.479"
+     y2="15.325"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line598"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.372"
+     y1="14.325"
+     x2="19.372"
+     y2="13.033"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line600"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.379999"
+     y1="14.325"
+     x2="19.379999"
+     y2="15.322"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line602"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="21.299999"
+     y1="14.325"
+     x2="21.299999"
+     y2="15.375"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line604"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.6670001"
+     height="2.5"
+     x="2.8169999"
+     y="15.35"
+     id="rect606"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.6670001"
+     height="2.5"
+     x="2.8169999"
+     y="15.35"
+     id="rect608"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.6670001"
+     height="2.5"
+     x="2.8169999"
+     y="15.35"
+     id="rect610"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.3329999"
+     height="1"
+     x="2.9000001"
+     y="15.433"
+     id="rect612"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.3329999"
+     height="1"
+     x="2.9000001"
+     y="15.433"
+     id="rect614"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.3329999"
+     height="1"
+     x="2.9000001"
+     y="15.433"
+     id="rect616"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.9000001"
+     y1="15.767"
+     x2="4.2329998"
+     y2="15.767"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line618"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.2329998"
+     y1="16.1"
+     x2="2.9000001"
+     y2="16.1"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line620"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.917"
+     height="0.5"
+     x="3.0669999"
+     y="16.517"
+     id="rect622"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.917"
+     height="0.5"
+     x="3.0669999"
+     y="16.517"
+     id="rect624"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.917"
+     height="0.5"
+     x="3.0669999"
+     y="16.517"
+     id="rect626"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.8169999"
+     y1="17.267"
+     x2="4.4829998"
+     y2="17.267"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line628"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="3.983"
+     y="17.1"
+     id="rect630"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="3.983"
+     y="17.1"
+     id="rect632"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="3.983"
+     y="17.1"
+     id="rect634"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.1500001"
+     y="17.1"
+     id="rect636"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.1500001"
+     y="17.1"
+     id="rect638"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.1500001"
+     y="17.1"
+     id="rect640"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.3169999"
+     y="17.1"
+     id="rect642"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.3169999"
+     y="17.1"
+     id="rect644"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="4.3169999"
+     y="17.1"
+     id="rect646"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="4.2329998"
+     y="16.85"
+     id="rect648"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="4.2329998"
+     y="16.85"
+     id="rect650"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="4.2329998"
+     y="16.85"
+     id="rect652"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.0669999"
+     y1="16.767"
+     x2="3.983"
+     y2="16.767"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line654"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="4.1500001"
+     y="16.517"
+     id="rect656"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="4.1500001"
+     y="16.517"
+     id="rect658"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="4.1500001"
+     y="16.517"
+     id="rect660"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.1670001"
+     height="0.082999997"
+     x="2.983"
+     y="16.183001"
+     id="rect662"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1670001"
+     height="0.082999997"
+     x="2.983"
+     y="16.183001"
+     id="rect664"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1670001"
+     height="0.082999997"
+     x="2.983"
+     y="16.183001"
+     id="rect666"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.1500001"
+     y1="16.6"
+     x2="3.9000001"
+     y2="16.6"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line668"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="3.3169999"
+     y="16.6"
+     id="rect670"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="3.3169999"
+     y="16.6"
+     id="rect672"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="3.3169999"
+     y="16.6"
+     id="rect674"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.983"
+     y1="16.35"
+     x2="4.1500001"
+     y2="16.35"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line676"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.9000001"
+     y1="17.35"
+     x2="4.4000001"
+     y2="17.35"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line678"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.4000001"
+     y1="17.433001"
+     x2="2.9000001"
+     y2="17.433001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line680"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.9000001"
+     y1="17.517"
+     x2="4.4000001"
+     y2="17.517"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line682"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.4000001"
+     y1="17.767"
+     x2="2.9000001"
+     y2="17.767"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line684"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.9000001"
+     y1="17.683001"
+     x2="4.4000001"
+     y2="17.683001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line686"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.4000001"
+     y1="17.6"
+     x2="2.9000001"
+     y2="17.6"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line688"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.983"
+     y1="16.35"
+     x2="3.0669999"
+     y2="16.35"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line690"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.1500001"
+     y1="16.35"
+     x2="3.233"
+     y2="16.35"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.1500001"
+     y1="16.683001"
+     x2="3.233"
+     y2="16.683001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.8169999"
+     y1="16.683001"
+     x2="3.9000001"
+     y2="16.683001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.5"
+     height="3"
+     x="20.549999"
+     y="15.375"
+     id="rect698"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.5"
+     height="3"
+     x="20.549999"
+     y="15.375"
+     id="rect700"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.5"
+     height="3"
+     x="20.549999"
+     y="15.375"
+     id="rect702"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.2"
+     height="1.2"
+     x="20.700001"
+     y="15.525"
+     id="rect704"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.2"
+     height="1.2"
+     x="20.700001"
+     y="15.525"
+     id="rect706"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.2"
+     height="1.2"
+     x="20.700001"
+     y="15.525"
+     id="rect708"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.9"
+     y1="15.825"
+     x2="20.700001"
+     y2="15.825"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line710"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.700001"
+     y1="16.125"
+     x2="21.9"
+     y2="16.125"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line712"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.9"
+     y1="16.35"
+     x2="20.700001"
+     y2="16.35"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line714"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.82499999"
+     height="0.44999999"
+     x="20.700001"
+     y="16.875"
+     id="rect716"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.82499999"
+     height="0.44999999"
+     x="20.700001"
+     y="16.875"
+     id="rect718"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.82499999"
+     height="0.44999999"
+     x="20.700001"
+     y="16.875"
+     id="rect720"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.549999"
+     y1="17.4"
+     x2="22.049999"
+     y2="17.4"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line722"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.225"
+     y="17.549999"
+     id="rect724"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.225"
+     y="17.549999"
+     id="rect726"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.225"
+     y="17.549999"
+     id="rect728"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.525"
+     y="17.549999"
+     id="rect730"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.525"
+     y="17.549999"
+     id="rect732"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.525"
+     y="17.549999"
+     id="rect734"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.825001"
+     y="17.549999"
+     id="rect736"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.825001"
+     y="17.549999"
+     id="rect738"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.075000003"
+     height="0.075000003"
+     x="21.825001"
+     y="17.549999"
+     id="rect740"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.15000001"
+     height="0.075000003"
+     x="21.75"
+     y="17.1"
+     id="rect742"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.15000001"
+     height="0.075000003"
+     x="21.75"
+     y="17.1"
+     id="rect744"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.15000001"
+     height="0.075000003"
+     x="21.75"
+     y="17.1"
+     id="rect746"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.700001"
+     y1="17.1"
+     x2="21.525"
+     y2="17.1"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line748"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.22499999"
+     height="0.22499999"
+     x="20.700001"
+     y="17.475"
+     id="rect750"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.22499999"
+     height="0.22499999"
+     x="20.700001"
+     y="17.475"
+     id="rect752"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.22499999"
+     height="0.22499999"
+     x="20.700001"
+     y="17.475"
+     id="rect754"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.05"
+     height="0.075000003"
+     x="20.775"
+     y="16.424999"
+     id="rect756"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.05"
+     height="0.075000003"
+     x="20.775"
+     y="16.424999"
+     id="rect758"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.05"
+     height="0.075000003"
+     x="20.775"
+     y="16.424999"
+     id="rect760"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.775"
+     y1="16.950001"
+     x2="21.450001"
+     y2="16.950001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line762"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.450001"
+     y1="17.025"
+     x2="21.375"
+     y2="17.025"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line764"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.775"
+     y1="17.025"
+     x2="20.85"
+     y2="17.025"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line766"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.375"
+     height="0.075000003"
+     x="20.924999"
+     y="16.950001"
+     id="rect768"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.375"
+     height="0.075000003"
+     x="20.924999"
+     y="16.950001"
+     id="rect770"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.375"
+     height="0.075000003"
+     x="20.924999"
+     y="16.950001"
+     id="rect772"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.775"
+     y1="16.575001"
+     x2="20.85"
+     y2="16.575001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line774"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.924999"
+     y1="16.575001"
+     x2="21"
+     y2="16.575001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line776"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.674999"
+     y1="16.575001"
+     x2="21.825001"
+     y2="16.575001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line778"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.975"
+     y1="18.299999"
+     x2="20.625"
+     y2="18.299999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line780"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.625"
+     y1="18.225"
+     x2="21.975"
+     y2="18.225"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line782"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.975"
+     y1="18.15"
+     x2="20.625"
+     y2="18.15"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line784"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.625"
+     y1="18.075001"
+     x2="21.975"
+     y2="18.075001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line786"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.975"
+     y1="18"
+     x2="20.625"
+     y2="18"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line788"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.625"
+     y1="17.924999"
+     x2="21.975"
+     y2="17.924999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line790"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.975"
+     y1="17.85"
+     x2="20.625"
+     y2="17.85"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line792"
+     style="stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="5.796,15.735 5.738,15.759 5.562,16.197 5.562,16.416 5.65,16.489 6.935,16.489 7.023,16.416 7.023,16.197 6.847,15.759 6.789,15.735 5.796,15.735 "
+     id="polygon794"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="5.796,15.735 5.738,15.759 5.562,16.197 5.562,16.416 5.65,16.489 6.935,16.489 7.023,16.416 7.023,16.197 6.847,15.759 6.789,15.735 5.796,15.735 "
+     id="polygon796"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.592,16.124 L 5.65,16.149 L 6.935,16.149 L 6.993,16.124"
+     id="path798"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 6.935,16.149 L 7.023,16.197"
+     id="path800"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.562,16.197 L 5.65,16.149"
+     id="path802"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.971,15.273 5.942,15.857 6.643,15.857 6.614,15.273 5.971,15.273 "
+     id="polygon804"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="5.971,15.273 5.942,15.857 6.643,15.857 6.614,15.273 5.971,15.273 "
+     id="polygon806"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.854,15.857 5.796,16.027 6.789,16.027 6.731,15.857 5.854,15.857 "
+     id="polygon808"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="5.854,15.857 5.796,16.027 6.789,16.027 6.731,15.857 5.854,15.857 "
+     id="polygon810"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="5.8540001"
+     cy="16.233999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse812"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.8540001"
+     cy="16.233999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse814"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6"
+     cy="16.233999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse816"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6"
+     cy="16.233999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse818"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1459999"
+     cy="16.233999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse820"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1459999"
+     cy="16.233999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse822"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.8540001"
+     cy="16.295"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse824"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.8540001"
+     cy="16.295"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse826"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6"
+     cy="16.295"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse828"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6"
+     cy="16.295"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse830"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1459999"
+     cy="16.295"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse832"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1459999"
+     cy="16.295"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse834"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.8540001"
+     cy="16.355"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse836"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.8540001"
+     cy="16.355"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse838"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6"
+     cy="16.355"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse840"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6"
+     cy="16.355"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse842"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1459999"
+     cy="16.355"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse844"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1459999"
+     cy="16.355"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse846"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.8540001"
+     cy="16.416"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse848"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.8540001"
+     cy="16.416"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse850"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6"
+     cy="16.416"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse852"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6"
+     cy="16.416"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse854"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.1459999"
+     cy="16.416"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse856"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.1459999"
+     cy="16.416"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse858"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.2919998"
+     cy="16.246"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse860"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="6.2919998"
+     cy="16.246"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse862"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.658"
+     cy="16.246"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse864"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="6.658"
+     cy="16.246"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse866"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <polygon
+     points="18.871,15.81 18.813,15.834 18.637,16.272 18.637,16.491 18.725,16.564 20.01,16.564 20.098,16.491 20.098,16.272 19.922,15.834 19.864,15.81 18.871,15.81 "
+     id="polygon868"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="18.871,15.81 18.813,15.834 18.637,16.272 18.637,16.491 18.725,16.564 20.01,16.564 20.098,16.491 20.098,16.272 19.922,15.834 19.864,15.81 18.871,15.81 "
+     id="polygon870"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 18.667,16.199 L 18.725,16.224 L 20.01,16.224 L 20.068,16.199"
+     id="path872"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 20.01,16.224 L 20.098,16.272"
+     id="path874"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 18.637,16.272 L 18.725,16.224"
+     id="path876"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="19.046,15.348 19.017,15.932 19.718,15.932 19.689,15.348 19.046,15.348 "
+     id="polygon878"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="19.046,15.348 19.017,15.932 19.718,15.932 19.689,15.348 19.046,15.348 "
+     id="polygon880"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="18.929,15.932 18.871,16.102 19.864,16.102 19.806,15.932 18.929,15.932 "
+     id="polygon882"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="18.929,15.932 18.871,16.102 19.864,16.102 19.806,15.932 18.929,15.932 "
+     id="polygon884"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="18.929001"
+     cy="16.309"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse886"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.929001"
+     cy="16.309"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse888"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.075001"
+     cy="16.309"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse890"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="19.075001"
+     cy="16.309"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse892"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.221001"
+     cy="16.309"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse894"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="19.221001"
+     cy="16.309"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse896"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.929001"
+     cy="16.370001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse898"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.929001"
+     cy="16.370001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse900"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.075001"
+     cy="16.370001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse902"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="19.075001"
+     cy="16.370001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse904"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.221001"
+     cy="16.370001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse906"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="19.221001"
+     cy="16.370001"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse908"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.929001"
+     cy="16.43"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse910"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.929001"
+     cy="16.43"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse912"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.075001"
+     cy="16.43"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse914"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="19.075001"
+     cy="16.43"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse916"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.221001"
+     cy="16.43"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse918"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="19.221001"
+     cy="16.43"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse920"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="18.929001"
+     cy="16.490999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse922"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="18.929001"
+     cy="16.490999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse924"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.075001"
+     cy="16.490999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse926"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="19.075001"
+     cy="16.490999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse928"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.221001"
+     cy="16.490999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse930"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="19.221001"
+     cy="16.490999"
+     rx="0.015"
+     ry="0.015"
+     id="ellipse932"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.367001"
+     cy="16.320999"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse934"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="19.367001"
+     cy="16.320999"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse936"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="19.733"
+     cy="16.320999"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse938"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="19.733"
+     cy="16.320999"
+     rx="0.183"
+     ry="0.057999998"
+     id="ellipse940"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="16.948"
+     y="15.332"
+     id="rect942"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="16.948"
+     y="15.332"
+     id="rect944"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="17.068001"
+     y="15.453"
+     id="rect946"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="17.098,16.166 17.67,16.166 17.67,16.296 17.128,16.296 17.098,16.166 "
+     id="polygon948"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.098,16.166 17.67,16.166 17.67,16.296 17.128,16.296 17.098,16.166 "
+     id="polygon950"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.67,16.166 17.909,16.166 17.879,16.296 17.67,16.296 17.67,16.166 "
+     id="polygon952"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.67,16.166 17.909,16.166 17.879,16.296 17.67,16.296 17.67,16.166 "
+     id="polygon954"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="17.709"
+     y="16.205"
+     id="rect956"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="17.709"
+     y="16.205"
+     id="rect958"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="17.392,16.296 17.614,16.296 17.614,16.361 17.726,16.361 17.726,16.426 17.281,16.426 17.281,16.361 17.392,16.361 17.392,16.296 "
+     id="polygon960"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.392,16.296 17.614,16.296 17.614,16.361 17.726,16.361 17.726,16.426 17.281,16.426 17.281,16.361 17.392,16.361 17.392,16.296 "
+     id="polygon962"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="15.073"
+     y="15.307"
+     id="rect964"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="15.073"
+     y="15.307"
+     id="rect966"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="15.193"
+     y="15.428"
+     id="rect968"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="15.223,16.141 15.795,16.141 15.795,16.271 15.253,16.271 15.223,16.141 "
+     id="polygon970"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.223,16.141 15.795,16.141 15.795,16.271 15.253,16.271 15.223,16.141 "
+     id="polygon972"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="15.795,16.141 16.034,16.141 16.004,16.271 15.795,16.271 15.795,16.141 "
+     id="polygon974"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.795,16.141 16.034,16.141 16.004,16.271 15.795,16.271 15.795,16.141 "
+     id="polygon976"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="15.834"
+     y="16.18"
+     id="rect978"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="15.834"
+     y="16.18"
+     id="rect980"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="15.517,16.271 15.739,16.271 15.739,16.336 15.851,16.336 15.851,16.401 15.406,16.401 15.406,16.336 15.517,16.336 15.517,16.271 "
+     id="polygon982"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="15.517,16.271 15.739,16.271 15.739,16.336 15.851,16.336 15.851,16.401 15.406,16.401 15.406,16.336 15.517,16.336 15.517,16.271 "
+     id="polygon984"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="13.298"
+     y="15.332"
+     id="rect986"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="13.298"
+     y="15.332"
+     id="rect988"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="13.418"
+     y="15.453"
+     id="rect990"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="13.448,16.166 14.02,16.166 14.02,16.296 13.478,16.296 13.448,16.166 "
+     id="polygon992"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="13.448,16.166 14.02,16.166 14.02,16.296 13.478,16.296 13.448,16.166 "
+     id="polygon994"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="14.02,16.166 14.259,16.166 14.229,16.296 14.02,16.296 14.02,16.166 "
+     id="polygon996"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="14.02,16.166 14.259,16.166 14.229,16.296 14.02,16.296 14.02,16.166 "
+     id="polygon998"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="14.059"
+     y="16.205"
+     id="rect1000"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="14.059"
+     y="16.205"
+     id="rect1002"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="13.742,16.296 13.964,16.296 13.964,16.361 14.076,16.361 14.076,16.426 13.631,16.426 13.631,16.361 13.742,16.361 13.742,16.296 "
+     id="polygon1004"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="13.742,16.296 13.964,16.296 13.964,16.361 14.076,16.361 14.076,16.426 13.631,16.426 13.631,16.361 13.742,16.361 13.742,16.296 "
+     id="polygon1006"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="10.148"
+     y="15.357"
+     id="rect1008"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="10.148"
+     y="15.357"
+     id="rect1010"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="10.268"
+     y="15.478"
+     id="rect1012"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="10.298,16.191 10.87,16.191 10.87,16.321 10.328,16.321 10.298,16.191 "
+     id="polygon1014"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="10.298,16.191 10.87,16.191 10.87,16.321 10.328,16.321 10.298,16.191 "
+     id="polygon1016"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="10.87,16.191 11.109,16.191 11.079,16.321 10.87,16.321 10.87,16.191 "
+     id="polygon1018"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="10.87,16.191 11.109,16.191 11.079,16.321 10.87,16.321 10.87,16.191 "
+     id="polygon1020"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="10.909"
+     y="16.23"
+     id="rect1022"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="10.909"
+     y="16.23"
+     id="rect1024"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="10.592,16.321 10.814,16.321 10.814,16.386 10.926,16.386 10.926,16.451 10.481,16.451 10.481,16.386 10.592,16.386 10.592,16.321 "
+     id="polygon1026"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="10.592,16.321 10.814,16.321 10.814,16.386 10.926,16.386 10.926,16.451 10.481,16.451 10.481,16.386 10.592,16.386 10.592,16.321 "
+     id="polygon1028"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="7.948"
+     y="15.383"
+     id="rect1030"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.112"
+     height="0.83399999"
+     x="7.948"
+     y="15.383"
+     id="rect1032"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.87099999"
+     height="0.574"
+     x="8.0679998"
+     y="15.503"
+     id="rect1034"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="8.098,16.216 8.67,16.216 8.67,16.346 8.128,16.346 8.098,16.216 "
+     id="polygon1036"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.098,16.216 8.67,16.216 8.67,16.346 8.128,16.346 8.098,16.216 "
+     id="polygon1038"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.67,16.216 8.909,16.216 8.879,16.346 8.67,16.346 8.67,16.216 "
+     id="polygon1040"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.67,16.216 8.909,16.216 8.879,16.346 8.67,16.346 8.67,16.216 "
+     id="polygon1042"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="8.7089996"
+     y="16.254999"
+     id="rect1044"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.052000001"
+     height="0.052000001"
+     x="8.7089996"
+     y="16.254999"
+     id="rect1046"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.392,16.346 8.614,16.346 8.614,16.411 8.726,16.411 8.726,16.476 8.281,16.476 8.281,16.411 8.392,16.411 8.392,16.346 "
+     id="polygon1048"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.392,16.346 8.614,16.346 8.614,16.411 8.726,16.411 8.726,16.476 8.281,16.476 8.281,16.411 8.392,16.411 8.392,16.346 "
+     id="polygon1050"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="1.378"
+     height="1.216"
+     x="0.33899999"
+     y="15.46"
+     id="rect1052"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="1.028"
+     cy="16.676001"
+     rx="0.68900001"
+     ry="0.20299999"
+     id="ellipse1054"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.028"
+     cy="15.46"
+     rx="0.68900001"
+     ry="0.20299999"
+     id="ellipse1056"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.028"
+     cy="15.46"
+     rx="0.68900001"
+     ry="0.20299999"
+     id="ellipse1058"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 1.717,15.46 L 1.717,16.676 C 1.717,16.788 1.408,16.878 1.028,16.878 C 0.647,16.878 0.339,16.788 0.339,16.676 L 0.339,15.46"
+     id="path1060"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="1.673"
+     y1="15.932"
+     x2="2.848"
+     y2="15.932"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1062"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.362"
+     height="1.202"
+     x="23.125999"
+     y="15.633"
+     id="rect1064"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="23.806999"
+     cy="16.834"
+     rx="0.68099999"
+     ry="0.2"
+     id="ellipse1066"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="23.806999"
+     cy="15.633"
+     rx="0.68099999"
+     ry="0.2"
+     id="ellipse1068"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="23.806999"
+     cy="15.633"
+     rx="0.68099999"
+     ry="0.2"
+     id="ellipse1070"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 24.488,15.633 L 24.488,16.834 C 24.488,16.945 24.183,17.035 23.807,17.035 C 23.431,17.035 23.126,16.945 23.126,16.834 L 23.126,15.633"
+     id="path1072"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="22.098"
+     y1="16.082001"
+     x2="23.062"
+     y2="16.047001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1074"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="11.846"
+     y="4.9720001"
+     id="text1076"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
+  <text
+     x="23.485001"
+     y="16.497"
+     id="text1078"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
+  <text
+     x="0.70999998"
+     y="16.322001"
+     id="text1080"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
+  <text
+     x="11.844"
+     y="7.3400002"
+     id="text1082"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">data</text>
+  <text
+     x="5.848"
+     y="8.9899998"
+     id="text1084"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">firewall</text>
+  <text
+     x="1.897"
+     y="12.74"
+     id="text1086"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
+  <text
+     x="20.27"
+     y="12.665"
+     id="text1088"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
+  <text
+     x="10.52"
+     y="11.465"
+     id="text1090"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
+  <text
+     x="17.094999"
+     y="6.4029999"
+     id="text1092"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.0.0/22</text>
+  <text
+     x="6.4499998"
+     y="14.065"
+     id="text1094"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.4.0/22</text>
+  <text
+     x="14.906"
+     y="13.965"
+     id="text1096"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.8.0/24</text>
+  <text
+     x="15.58"
+     y="3.178"
+     id="text1098"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: MEGANET2</text>
+  <text
+     x="8.2959995"
+     y="2.983"
+     id="text1100"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC Server:</text>
+  <text
+     x="8.0710001"
+     y="3.5829999"
+     id="text1102"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">MASSIVE-PDC</text>
+  <text
+     x="1.272"
+     y="14.296"
+     id="text1104"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="0.82099998"
+     y="14.896"
+     id="text1106"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG1-BDC</text>
+  <text
+     x="22.659"
+     y="14.321"
+     id="text1108"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="22.207001"
+     y="14.921"
+     id="text1110"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
+  <text
+     x="7.5240002"
+     y="7.9169998"
+     id="text1112"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth0</text>
+  <text
+     x="10.847"
+     y="9.3170004"
+     id="text1114"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth1</text>
+  <rect
+     width="1.432"
+     height="1.263"
+     x="13.118"
+     y="5.283"
+     id="rect1116"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="13.833"
+     cy="6.5469999"
+     rx="0.71600002"
+     ry="0.211"
+     id="ellipse1118"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.833"
+     cy="5.283"
+     rx="0.71600002"
+     ry="0.211"
+     id="ellipse1120"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.833"
+     cy="5.283"
+     rx="0.71600002"
+     ry="0.211"
+     id="ellipse1122"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 14.549,5.283 L 14.549,6.547 C 14.549,6.663 14.229,6.757 13.833,6.757 C 13.438,6.757 13.118,6.663 13.118,6.547 L 13.118,5.283"
+     id="path1124"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.473"
+     y1="5.9720001"
+     x2="13.098"
+     y2="5.947"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1126"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="13.527"
+     y="6.197"
+     id="text1128"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">ldap</text>
+  <text
+     x="9.408"
+     y="19.547001"
+     id="text1130"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
+  <text
+     x="22.794001"
+     y="19.542"
+     id="text1132"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">150 Users</text>
+  <text
+     x="17.837999"
+     y="5.6919999"
+     id="text1134"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">300 Users</text>
+  <text
+     x="0.83999997"
+     y="19.539"
+     id="text1136"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounting</text>
+  <text
+     x="14.316"
+     y="19.514"
+     id="text1138"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Financial Services</text>
+  <text
+     x="15.63"
+     y="4.5640001"
+     id="text1140"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Property Insurance Group</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap7-idresol.svg b/docs-xml/Samba3-ByExample/images/chap7-idresol.svg
new file mode 100644
index 00000000000..560658f098f
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap7-idresol.svg
@@ -0,0 +1,514 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="17.290001cm"
+   height="13.335cm"
+   viewBox="23.46 19.665 40.75 33"
+   id="svg2">
+  <defs
+     id="defs177" />
+  <rect
+     width="2"
+     height="2"
+     x="29.1"
+     y="23"
+     id="rect4"
+     style="fill:#fff4db;stroke:none;stroke-width:0" />
+  <rect
+     width="2"
+     height="2"
+     x="29.1"
+     y="23"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2"
+     height="2"
+     x="32.035"
+     y="27.59"
+     id="rect8"
+     style="fill:#d8d8d8;stroke:none;stroke-width:0" />
+  <rect
+     width="2"
+     height="2"
+     x="32.035"
+     y="27.59"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2"
+     height="2.04"
+     x="29.184999"
+     y="27.549999"
+     id="rect12"
+     style="fill:#d0d0d0;stroke:none;stroke-width:0" />
+  <rect
+     width="2"
+     height="2.04"
+     x="29.184999"
+     y="27.549999"
+     id="rect14"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.8399999"
+     height="1.735"
+     x="23.51"
+     y="23.139999"
+     id="rect16"
+     style="fill:#a9d8cb;stroke:none;stroke-width:0" />
+  <rect
+     width="2.8399999"
+     height="1.735"
+     x="23.51"
+     y="23.139999"
+     id="rect18"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.825"
+     height="1.885"
+     x="32.674999"
+     y="20.940001"
+     id="rect20"
+     style="fill:#dedede;stroke:none;stroke-width:0" />
+  <rect
+     width="2.825"
+     height="1.885"
+     x="32.674999"
+     y="20.940001"
+     id="rect22"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.6500001"
+     height="2.01"
+     x="37.799999"
+     y="19.715"
+     id="rect24"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.6500001"
+     height="2.01"
+     x="37.799999"
+     y="19.715"
+     id="rect26"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.3"
+     height="2.0150001"
+     x="38.025002"
+     y="22.1"
+     id="rect28"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.3"
+     height="2.0150001"
+     x="38.025002"
+     y="22.1"
+     id="rect30"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.25"
+     height="2.0599999"
+     x="35.150002"
+     y="27.565001"
+     id="rect32"
+     style="fill:#d8d8d8;stroke:none;stroke-width:0" />
+  <rect
+     width="2.25"
+     height="2.0599999"
+     x="35.150002"
+     y="27.565001"
+     id="rect34"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="24.200001"
+     y="23.9"
+     id="text36"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Windows</text>
+  <text
+     x="24.462999"
+     y="24.5"
+     id="text38"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Client</text>
+  <text
+     x="29.659"
+     y="24.15"
+     id="text40"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd</text>
+  <text
+     x="33.388"
+     y="22.051001"
+     id="text42"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">winbindd</text>
+  <text
+     x="29.76"
+     y="28.676001"
+     id="text44"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NSS</text>
+  <text
+     x="32.653999"
+     y="28.775999"
+     id="text46"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PAM</text>
+  <text
+     x="35.763"
+     y="28.700001"
+     id="text48"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="38.696999"
+     y="23"
+     id="text50"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">W2Kx</text>
+  <text
+     x="38.805"
+     y="23.6"
+     id="text52"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">ADS</text>
+  <text
+     x="38.759998"
+     y="20.6"
+     id="text54"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NT4</text>
+  <text
+     x="38.477001"
+     y="21.200001"
+     id="text56"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain</text>
+  <line
+     x1="26.9"
+     y1="24.006001"
+     x2="28.549999"
+     y2="24.000999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line58"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="26.899,23.756 26.4,24.007 26.901,24.256 26.899,23.756 "
+     id="polygon60"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="28.551,24.251 29.05,24 28.549,23.752 28.551,24.251 "
+     id="polygon62"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="29.52"
+     y1="25.575001"
+     x2="29.504999"
+     y2="27"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line64"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="29.77,25.577 29.525,25.075 29.27,25.572 29.77,25.577 "
+     id="polygon66"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="29.255,26.998 29.5,27.5 29.755,27.003 29.255,26.998 "
+     id="polygon68"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="31.393999"
+     y1="25.190001"
+     x2="32.605999"
+     y2="27.110001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line70"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="31.605,25.057 31.127,24.767 31.182,25.324 31.605,25.057 "
+     id="polygon72"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="32.395,27.243 32.873,27.533 32.818,26.976 32.395,27.243 "
+     id="polygon74"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="31.481001"
+     y1="23.128"
+     x2="32.293999"
+     y2="22.278999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line76"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="31.3,22.955 31.135,23.489 31.661,23.301 31.3,22.955 "
+     id="polygon78"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="32.475,22.453 32.64,21.919 32.114,22.106 32.475,22.453 "
+     id="polygon80"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="31.552999"
+     y1="24.312"
+     x2="35.821999"
+     y2="27.253"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="31.695,24.106 31.141,24.028 31.411,24.518 31.695,24.106 "
+     id="polygon84"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="35.68,27.459 36.234,27.537 35.964,27.047 35.68,27.459 "
+     id="polygon86"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="36.066002"
+     y1="21.360001"
+     x2="37.284"
+     y2="20.91"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line88"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="35.979,21.125 35.597,21.533 36.153,21.594 35.979,21.125 "
+     id="polygon90"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="37.371,21.145 37.753,20.737 37.197,20.676 37.371,21.145 "
+     id="polygon92"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="36.013"
+     y1="22.323999"
+     x2="37.512001"
+     y2="22.908001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line94"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="36.103,22.091 35.547,22.143 35.922,22.557 36.103,22.091 "
+     id="polygon96"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="37.422,23.141 37.978,23.089 37.603,22.675 37.422,23.141 "
+     id="polygon98"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <rect
+     width="2.95"
+     height="2.01"
+     x="37.75"
+     y="24.565001"
+     id="rect100"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.95"
+     height="2.01"
+     x="37.75"
+     y="24.565001"
+     id="rect102"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="38.654999"
+     y="25.424999"
+     id="text104"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
+  <text
+     x="38.414001"
+     y="26.025"
+     id="text106"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC/BDC</text>
+  <line
+     x1="34.959"
+     y1="23.228001"
+     x2="37.328999"
+     y2="25.216999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line108"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="35.12,23.037 34.576,22.907 34.798,23.42 35.12,23.037 "
+     id="polygon110"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="37.168,25.408 37.712,25.538 37.489,25.025 37.168,25.408 "
+     id="polygon112"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <rect
+     width="3.915"
+     height="1.76"
+     x="29.01"
+     y="31.190001"
+     id="rect114"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="3.915"
+     height="1.76"
+     x="29.01"
+     y="31.190001"
+     id="rect116"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="30.181999"
+     y1="30.139999"
+     x2="30.177999"
+     y2="30.65"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line118"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="30.432,30.142 30.185,29.64 29.932,30.138 30.432,30.142 "
+     id="polygon120"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="29.928,30.648 30.175,31.15 30.428,30.652 29.928,30.648 "
+     id="polygon122"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="31.402"
+     y1="30.853001"
+     x2="32.599998"
+     y2="29.927"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line124"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="31.249,30.656 31.007,31.159 31.555,31.051 31.249,30.656 "
+     id="polygon126"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="32.753,30.124 32.995,29.621 32.447,29.729 32.753,30.124 "
+     id="polygon128"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="34.584999"
+     y1="28.591999"
+     x2="34.599998"
+     y2="28.593"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line130"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="34.586,28.342 34.085,28.59 34.584,28.842 34.586,28.342 "
+     id="polygon132"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="34.599,28.843 35.1,28.595 34.601,28.343 34.599,28.843 "
+     id="polygon134"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="30.027"
+     y="31.975"
+     id="text136"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">/etc/passwd</text>
+  <text
+     x="30.179001"
+     y="32.575001"
+     id="text138"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">/etc/group</text>
+  <rect
+     width="2.0650001"
+     height="1.76"
+     x="33.535"
+     y="31.190001"
+     id="rect140"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.0650001"
+     height="1.76"
+     x="33.535"
+     y="31.190001"
+     id="rect142"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="34.049"
+     y="32.25"
+     id="text144"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NIS[+]</text>
+  <line
+     x1="34.515999"
+     y1="30.754"
+     x2="33.839001"
+     y2="29.987"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line146"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="34.329,30.919 34.847,31.129 34.704,30.588 34.329,30.919 "
+     id="polygon148"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="34.027,29.822 33.508,29.612 33.652,30.153 34.027,29.822 "
+     id="polygon150"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="33.080002"
+     y1="30.879999"
+     x2="31.639999"
+     y2="29.9"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line152"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="32.94,31.087 33.494,31.162 33.221,30.674 32.94,31.087 "
+     id="polygon154"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="31.78,29.693 31.226,29.618 31.499,30.106 31.78,29.693 "
+     id="polygon156"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 34.773,27.172 C 33.554243,26.096992 31.732941,26.07362 30.487,27.117"
+     id="path158"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="30.268,26.92 30.133,27.462 30.648,27.245 30.268,26.92 "
+     id="polygon160"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="34.609,27.296 35.118,27.526 34.997,26.98 34.609,27.296 "
+     id="polygon162"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="33.568001"
+     y1="27.028999"
+     x2="34.02"
+     y2="23.371"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line164"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="33.319,26.998 33.506,27.525 33.816,27.06 33.319,26.998 "
+     id="polygon166"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="34.268,23.402 34.081,22.875 33.772,23.34 34.268,23.402 "
+     id="polygon168"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="31.264999"
+     y1="27.030001"
+     x2="33.073002"
+     y2="23.292"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line170"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="31.039,26.921 31.047,27.48 31.49,27.139 31.039,26.921 "
+     id="polygon172"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="33.298,23.401 33.291,22.842 32.848,23.183 33.298,23.401 "
+     id="polygon174"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap7-net-A.svg b/docs-xml/Samba3-ByExample/images/chap7-net-A.svg
new file mode 100644
index 00000000000..8337e5c68bd
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap7-net-A.svg
@@ -0,0 +1,9436 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="34.522999cm"
+   height="23.67cm"
+   viewBox="-11.471 -0.456 23.052 23.213"
+   id="svg2">
+  <defs
+     id="defs2855" />
+  <rect
+     width="13.8"
+     height="6.513"
+     x="1.375"
+     y="16.256001"
+     id="rect4"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
+     id="path6"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
+     id="path8"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="14.4"
+     height="5.9130001"
+     x="1.075"
+     y="16.556"
+     id="rect10"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
+     id="path12"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
+     id="path14"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="1.375"
+     y1="16.256001"
+     x2="15.175"
+     y2="16.256001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.375"
+     y1="22.768999"
+     x2="15.175"
+     y2="22.768999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.075"
+     y1="16.556"
+     x2="1.075"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="15.475"
+     y1="16.556"
+     x2="15.475"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.617"
+     height="6.8530002"
+     x="0.495"
+     y="-0.40599999"
+     id="rect32"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
+     id="path34"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
+     id="path36"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.217"
+     height="6.2529998"
+     x="0.19499999"
+     y="-0.106"
+     id="rect38"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
+     id="path40"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
+     id="path42"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="0.495"
+     y1="-0.40599999"
+     x2="11.112"
+     y2="-0.40599999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line44"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.495"
+     y1="6.447"
+     x2="11.112"
+     y2="6.447"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
+     id="path50"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.19499999"
+     y1="-0.106"
+     x2="0.19499999"
+     y2="6.1469998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.412"
+     y1="-0.106"
+     x2="11.412"
+     y2="6.1469998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line54"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
+     id="path56"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
+     id="path58"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.337"
+     height="6.8600001"
+     x="12.35"
+     y="-0.43099999"
+     id="rect60"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
+     id="path62"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
+     id="path64"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="10.937"
+     height="6.2600002"
+     x="12.05"
+     y="-0.131"
+     id="rect66"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
+     id="path68"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
+     id="path70"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="12.35"
+     y1="-0.43099999"
+     x2="22.687"
+     y2="-0.43099999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.35"
+     y1="6.4289999"
+     x2="22.687"
+     y2="6.4289999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.05"
+     y1="-0.131"
+     x2="12.05"
+     y2="6.1290002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="22.987"
+     y1="-0.131"
+     x2="22.987"
+     y2="6.1290002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
+     id="path84"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
+     id="path86"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.821"
+     height="8.375"
+     x="11.905"
+     y="7.244"
+     id="rect88"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
+     id="path90"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
+     id="path92"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.421"
+     height="7.7750001"
+     x="11.605"
+     y="7.5440001"
+     id="rect94"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
+     id="path96"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
+     id="path98"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="11.905"
+     y1="7.244"
+     x2="22.726999"
+     y2="7.244"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line100"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.905"
+     y1="15.619"
+     x2="22.726999"
+     y2="15.619"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line102"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
+     id="path104"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
+     id="path106"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.605"
+     y1="7.5440001"
+     x2="11.605"
+     y2="15.319"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line108"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="23.027"
+     y1="7.5440001"
+     x2="23.027"
+     y2="15.319"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line110"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
+     id="path112"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
+     id="path114"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="15.1"
+     height="8.3719997"
+     x="-11"
+     y="7.1090002"
+     id="rect116"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11,7.109 C -11.165685,7.109 -11.3,7.2433146 -11.3,7.409"
+     id="path118"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 4.4,7.409 C 4.4,7.2433146 4.2656854,7.109 4.1,7.109"
+     id="path120"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="15.7"
+     height="7.7719998"
+     x="-11.3"
+     y="7.4089999"
+     id="rect122"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.3,15.181 C -11.3,15.346685 -11.165685,15.481 -11,15.481"
+     id="path124"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 4.1,15.481 C 4.2656854,15.481 4.4,15.346685 4.4,15.181"
+     id="path126"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="-11"
+     y1="7.1090002"
+     x2="4.0999999"
+     y2="7.1090002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line128"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11"
+     y1="15.481"
+     x2="4.0999999"
+     y2="15.481"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line130"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11,7.109 C -11.165685,7.109 -11.3,7.2433146 -11.3,7.409"
+     id="path132"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 4.4,7.409 C 4.4,7.2433146 4.2656854,7.109 4.1,7.109"
+     id="path134"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.3"
+     y1="7.4089999"
+     x2="-11.3"
+     y2="15.181"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="4.4000001"
+     y1="7.4089999"
+     x2="4.4000001"
+     y2="15.181"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.3,15.181 C -11.3,15.346685 -11.165685,15.481 -11,15.481"
+     id="path140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 4.1,15.481 C 4.2656854,15.481 4.4,15.346685 4.4,15.181"
+     id="path142"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.95"
+     y1="11.168"
+     x2="4.8109999"
+     y2="11.165"
+     stroke="#000000"
+     stroke-width="0.300"
+     id="line144"
+     style="stroke:#000000;stroke-width:0.30000001" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="4.145,2.624 4.145,6.819 5.675,6.819 5.675,9.944 "
+     id="polyline146"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="16.100,2.794 16.100,6.844 8.674,6.844 8.674,9.887 "
+     id="polyline148"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.787"
+     x="-1.723"
+     y="14.284"
+     id="rect150"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.787"
+     height="0.787"
+     x="-1.723"
+     y="14.284"
+     id="rect152"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.787"
+     x="-1.723"
+     y="14.284"
+     id="rect154"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.28,14.411 C -1.28,14.805 -1.201,14.726 -1.595,14.726"
+     id="path156"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.28,14.411 C -1.28,14.805 -1.201,14.726 -1.595,14.726"
+     id="path158"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.242,14.473 -1.282,14.394 -1.321,14.473 -1.242,14.473 "
+     id="polygon160"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.242,14.473 -1.282,14.394 -1.321,14.473 -1.242,14.473 "
+     id="polygon162"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.534,14.685 -1.612,14.725 -1.534,14.764 -1.534,14.685 "
+     id="polygon164"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.534,14.685 -1.612,14.725 -1.534,14.764 -1.534,14.685 "
+     id="polygon166"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.047,14.633 C -1.44,14.633 -1.362,14.554 -1.362,14.948"
+     id="path168"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.047,14.633 C -1.44,14.633 -1.362,14.554 -1.362,14.948"
+     id="path170"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.116,14.67 -1.038,14.63 -1.116,14.591 -1.116,14.67 "
+     id="polygon172"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.116,14.67 -1.038,14.63 -1.116,14.591 -1.116,14.67 "
+     id="polygon174"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.408,14.882 -1.368,14.961 -1.329,14.882 -1.408,14.882 "
+     id="polygon176"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.408,14.882 -1.368,14.961 -1.329,14.882 -1.408,14.882 "
+     id="polygon178"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-1.3"
+     y1="11.069"
+     x2="-1.329"
+     y2="14.284"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line180"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-9.0480003"
+     y="0.86699998"
+     id="text182"
+     style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="1.017"
+     y="13.475"
+     id="text184"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="0.82800001"
+     y="13.975"
+     id="text186"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GNY-PDC</text>
+  <line
+     x1="6.118"
+     y1="13.16"
+     x2="7.7179999"
+     y2="13.135"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.10,0.10"
+     id="line188"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <text
+     x="8.4429998"
+     y="13.325"
+     id="text190"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">= VPN</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="10.645,11.075 10.645,9.069 16.025,9.069 16.025,11.368 "
+     id="polyline192"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-2.9530001"
+     y="15.094"
+     id="text194"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <text
+     x="4.1469998"
+     y="17.031"
+     id="text196"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect198"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect202"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect204"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect206"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect208"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="2.027"
+     x2="3.5869999"
+     y2="2.027"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line210"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.5869999"
+     y1="2.2709999"
+     x2="2.6140001"
+     y2="2.2709999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line212"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect214"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect216"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect218"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.553"
+     y1="3.122"
+     x2="3.77"
+     y2="3.122"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line220"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect222"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect224"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect226"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect228"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect230"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect232"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect234"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect236"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect238"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect240"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect242"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect244"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7360001"
+     y1="2.757"
+     x2="3.405"
+     y2="2.757"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line246"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect248"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect250"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect252"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect254"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect256"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect258"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.6359999"
+     x2="3.3440001"
+     y2="2.6359999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line260"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect262"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect264"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect266"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.405"
+     y1="2.4530001"
+     x2="3.527"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line268"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.1830001"
+     x2="3.7090001"
+     y2="3.1830001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line270"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.244"
+     x2="2.6140001"
+     y2="3.244"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line272"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.3050001"
+     x2="3.7090001"
+     y2="3.3050001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line274"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.487"
+     x2="2.6140001"
+     y2="3.487"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line276"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.427"
+     x2="3.7090001"
+     y2="3.427"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line278"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.3659999"
+     x2="2.6140001"
+     y2="3.3659999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line280"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.675"
+     y1="2.4530001"
+     x2="2.7360001"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line282"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.4530001"
+     x2="2.8570001"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line284"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.697"
+     x2="2.8570001"
+     y2="2.697"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line286"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.283"
+     y1="2.697"
+     x2="3.3440001"
+     y2="2.697"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line288"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.72"
+     y1="2.6359999"
+     x2="8.8620005"
+     y2="2.6229999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line290"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.2069998"
+     y1="2.632"
+     x2="5.2090001"
+     y2="3.5910001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line292"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.21"
+     y1="2.632"
+     x2="5.2080002"
+     y2="1.632"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line294"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.6500001"
+     y1="2.6289999"
+     x2="6.652"
+     y2="3.5339999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line296"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.651"
+     y1="2.6289999"
+     x2="6.6479998"
+     y2="1.6289999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line298"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.092"
+     y1="2.625"
+     x2="8.0950003"
+     y2="3.552"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line300"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.0909996"
+     y1="2.625"
+     x2="8.0889997"
+     y2="1.625"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line302"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.1989999"
+     y="3.559"
+     id="rect304"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.1989999"
+     y="3.559"
+     id="rect306"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.296"
+     y="3.6559999"
+     id="rect308"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
+     id="polygon310"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
+     id="polygon312"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
+     id="polygon314"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
+     id="polygon316"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8130002"
+     y="4.2620001"
+     id="rect318"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8130002"
+     y="4.2620001"
+     id="rect320"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
+     id="polygon322"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
+     id="polygon324"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6420002"
+     y="3.5480001"
+     id="rect326"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6420002"
+     y="3.5480001"
+     id="rect328"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.7389998"
+     y="3.645"
+     id="rect330"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
+     id="polygon332"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
+     id="polygon334"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
+     id="polygon336"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
+     id="polygon338"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2550001"
+     y="4.2509999"
+     id="rect340"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2550001"
+     y="4.2509999"
+     id="rect342"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
+     id="polygon344"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
+     id="polygon346"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="4.7670002"
+     y="1.123"
+     id="rect348"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="4.7670002"
+     y="1.123"
+     id="rect350"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="4.8639998"
+     y="1.22"
+     id="rect352"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
+     id="polygon354"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
+     id="polygon356"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
+     id="polygon358"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
+     id="polygon360"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="5.3800001"
+     y="1.826"
+     id="rect362"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="5.3800001"
+     y="1.826"
+     id="rect364"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
+     id="polygon366"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
+     id="polygon368"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.217"
+     y="1.148"
+     id="rect370"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.217"
+     y="1.148"
+     id="rect372"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.3140001"
+     y="1.245"
+     id="rect374"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
+     id="polygon376"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
+     id="polygon378"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
+     id="polygon380"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
+     id="polygon382"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8299999"
+     y="1.851"
+     id="rect384"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8299999"
+     y="1.851"
+     id="rect386"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
+     id="polygon388"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
+     id="polygon390"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6669998"
+     y="1.123"
+     id="rect392"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6669998"
+     y="1.123"
+     id="rect394"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.7639999"
+     y="1.22"
+     id="rect396"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
+     id="polygon398"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
+     id="polygon400"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
+     id="polygon402"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
+     id="polygon404"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2799997"
+     y="1.826"
+     id="rect406"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2799997"
+     y="1.826"
+     id="rect408"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
+     id="polygon410"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
+     id="polygon412"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
+     id="polygon414"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
+     id="polygon416"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.611,4.115 L 4.659,4.135 L 5.715,4.135 L 5.763,4.115"
+     id="path418"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.715,4.135 L 5.787,4.175"
+     id="path420"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.587,4.175 L 4.659,4.135"
+     id="path422"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
+     id="polygon424"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
+     id="polygon426"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
+     id="polygon428"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
+     id="polygon430"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse432"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse434"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse436"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse438"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse440"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse442"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse444"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse446"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse448"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse450"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse452"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse454"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse456"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse458"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse460"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse462"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse464"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse466"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse468"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse470"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse472"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse474"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse476"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse478"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.1869998"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse480"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="5.1869998"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse482"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.487"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse484"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="5.487"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse486"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect488"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect490"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect492"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect494"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect496"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect498"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.009"
+     y1="1.829"
+     x2="9.0939999"
+     y2="1.829"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line500"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0939999"
+     y1="2.0580001"
+     x2="10.009"
+     y2="2.0580001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line502"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.009"
+     y1="2.2290001"
+     x2="9.0939999"
+     y2="2.2290001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line504"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect506"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect508"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect510"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.9790001"
+     y1="3.03"
+     x2="10.123"
+     y2="3.03"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line512"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect514"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect516"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect518"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect520"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect522"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect524"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect526"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect528"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect530"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect532"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect534"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect536"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0939999"
+     y1="2.8010001"
+     x2="9.7229996"
+     y2="2.8010001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line538"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect540"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect542"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect544"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect546"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect548"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect550"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.687"
+     x2="9.6660004"
+     y2="2.687"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line552"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.6660004"
+     y1="2.744"
+     x2="9.6090002"
+     y2="2.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line554"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.744"
+     x2="9.2080002"
+     y2="2.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line556"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect558"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect560"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect562"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.401"
+     x2="9.2080002"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line564"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.2650003"
+     y1="2.401"
+     x2="9.323"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line566"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.8369999"
+     y1="2.401"
+     x2="9.9519997"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line568"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.7160001"
+     x2="9.0369997"
+     y2="3.7160001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line570"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.6589999"
+     x2="10.066"
+     y2="3.6589999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line572"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.602"
+     x2="9.0369997"
+     y2="3.602"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line574"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.5439999"
+     x2="10.066"
+     y2="3.5439999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line576"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.487"
+     x2="9.0369997"
+     y2="3.487"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line578"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.4300001"
+     x2="10.066"
+     y2="3.4300001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line580"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.3729999"
+     x2="9.0369997"
+     y2="3.3729999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line582"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="6.888"
+     y="5.3340001"
+     id="text584"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="6.4829998"
+     y="5.934"
+     id="text586"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.12.0/22</text>
+  <text
+     x="2.187"
+     y="4.1690001"
+     id="text588"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="2.006"
+     y="4.6690001"
+     id="text590"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-BDC</text>
+  <text
+     x="8.3649998"
+     y="0.375"
+     id="text592"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="8.6969995"
+     y="0.875"
+     id="text594"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-APPS</text>
+  <rect
+     width="1.291"
+     height="1.1390001"
+     x="0.61699998"
+     y="2.0880001"
+     id="rect596"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="1.263"
+     cy="3.227"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse598"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.263"
+     cy="2.0880001"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse600"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.263"
+     cy="2.0880001"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse602"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 1.908,2.088 L 1.908,3.227 C 1.908,3.332 1.619,3.417 1.263,3.417 C 0.906,3.417 0.617,3.332 0.617,3.227 L 0.617,2.088"
+     id="path604"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="1.928"
+     y1="2.523"
+     x2="2.503"
+     y2="2.523"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line606"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.935"
+     y="2.7219999"
+     id="text608"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="0.94999999"
+     y="3.122"
+     id="text610"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect612"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect614"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect616"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect618"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect620"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect622"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="2.1900001"
+     x2="15.431"
+     y2="2.1900001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line624"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="2.4330001"
+     x2="14.458"
+     y2="2.4330001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line626"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect628"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect630"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect632"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.397"
+     y1="3.2850001"
+     x2="15.614"
+     y2="3.2850001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line634"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect636"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect638"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect640"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect642"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect644"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect646"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect648"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect650"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect652"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect654"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect656"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect658"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.58"
+     y1="2.9200001"
+     x2="15.249"
+     y2="2.9200001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line660"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect662"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect664"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect666"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect668"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect670"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect672"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.7980001"
+     x2="15.188"
+     y2="2.7980001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line674"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect676"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect678"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect680"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.249"
+     y1="2.615"
+     x2="15.371"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line682"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.345"
+     x2="15.553"
+     y2="3.345"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line684"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.4059999"
+     x2="14.458"
+     y2="3.4059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line686"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.467"
+     x2="15.553"
+     y2="3.467"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line688"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.6500001"
+     x2="14.458"
+     y2="3.6500001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line690"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.589"
+     x2="15.553"
+     y2="3.589"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.5280001"
+     x2="14.458"
+     y2="3.5280001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="2.615"
+     x2="14.58"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.615"
+     x2="14.701"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line698"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.859"
+     x2="14.701"
+     y2="2.859"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line700"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.127"
+     y1="2.859"
+     x2="15.188"
+     y2="2.859"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line702"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.564"
+     y1="2.7980001"
+     x2="20.705"
+     y2="2.7850001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line704"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.051001"
+     y1="2.7939999"
+     x2="17.052999"
+     y2="3.753"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line706"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.054001"
+     y1="2.7939999"
+     x2="17.052"
+     y2="1.794"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line708"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.493"
+     y1="2.7909999"
+     x2="18.496"
+     y2="3.6960001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line710"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.495001"
+     y1="2.7909999"
+     x2="18.492001"
+     y2="1.791"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line712"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.936001"
+     y1="2.7869999"
+     x2="19.938999"
+     y2="3.714"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line714"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.934999"
+     y1="2.7869999"
+     x2="19.933001"
+     y2="1.7869999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line716"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.042999"
+     y="3.721"
+     id="rect718"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.042999"
+     y="3.721"
+     id="rect720"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.139999"
+     y="3.8180001"
+     id="rect722"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
+     id="polygon724"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
+     id="polygon726"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
+     id="polygon728"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
+     id="polygon730"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.657"
+     y="4.4239998"
+     id="rect732"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.657"
+     y="4.4239998"
+     id="rect734"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
+     id="polygon736"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
+     id="polygon738"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.486"
+     y="3.71"
+     id="rect740"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.486"
+     y="3.71"
+     id="rect742"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.583"
+     y="3.8069999"
+     id="rect744"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
+     id="polygon746"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
+     id="polygon748"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
+     id="polygon750"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
+     id="polygon752"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.099001"
+     y="4.414"
+     id="rect754"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.099001"
+     y="4.414"
+     id="rect756"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
+     id="polygon758"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
+     id="polygon760"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.611"
+     y="1.285"
+     id="rect762"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.611"
+     y="1.285"
+     id="rect764"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="16.708"
+     y="1.382"
+     id="rect766"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
+     id="polygon768"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
+     id="polygon770"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
+     id="polygon772"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
+     id="polygon774"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.224001"
+     y="1.989"
+     id="rect776"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.224001"
+     y="1.989"
+     id="rect778"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
+     id="polygon780"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
+     id="polygon782"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.061001"
+     y="1.3099999"
+     id="rect784"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.061001"
+     y="1.3099999"
+     id="rect786"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.158001"
+     y="1.4069999"
+     id="rect788"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
+     id="polygon790"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
+     id="polygon792"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
+     id="polygon794"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
+     id="polygon796"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.674"
+     y="2.0139999"
+     id="rect798"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.674"
+     y="2.0139999"
+     id="rect800"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
+     id="polygon802"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
+     id="polygon804"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.511"
+     y="1.285"
+     id="rect806"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.511"
+     y="1.285"
+     id="rect808"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.608"
+     y="1.382"
+     id="rect810"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
+     id="polygon812"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
+     id="polygon814"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
+     id="polygon816"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
+     id="polygon818"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.124001"
+     y="1.989"
+     id="rect820"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.124001"
+     y="1.989"
+     id="rect822"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
+     id="polygon824"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
+     id="polygon826"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
+     id="polygon828"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
+     id="polygon830"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.454,4.277 L 16.502,4.297 L 17.558,4.297 L 17.606,4.277"
+     id="path832"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 17.558,4.297 L 17.63,4.337"
+     id="path834"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.43,4.337 L 16.502,4.297"
+     id="path836"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
+     id="polygon838"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
+     id="polygon840"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
+     id="polygon842"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
+     id="polygon844"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="16.67"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse846"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse848"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse850"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse852"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse854"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse856"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse858"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse860"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse862"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse864"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse866"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse868"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse870"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse872"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse874"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse876"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse878"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse880"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse882"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse884"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse886"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse888"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse890"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse892"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.030001"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse894"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.030001"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse896"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.33"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse898"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.33"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse900"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect902"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect904"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect906"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect908"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect910"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect912"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.853001"
+     y1="1.9910001"
+     x2="20.938"
+     y2="1.9910001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line914"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.938"
+     y1="2.22"
+     x2="21.853001"
+     y2="2.22"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line916"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.853001"
+     y1="2.391"
+     x2="20.938"
+     y2="2.391"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line918"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect920"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect922"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect924"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.823"
+     y1="3.1919999"
+     x2="21.966999"
+     y2="3.1919999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line926"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect928"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect930"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect932"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect934"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect936"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect938"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect940"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect942"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect944"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect946"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect948"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect950"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.938"
+     y1="2.9630001"
+     x2="21.566999"
+     y2="2.9630001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line952"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect954"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect956"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect958"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect960"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect962"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect964"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.849"
+     x2="21.51"
+     y2="2.849"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line966"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.51"
+     y1="2.9059999"
+     x2="21.452"
+     y2="2.9059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line968"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.9059999"
+     x2="21.052"
+     y2="2.9059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line970"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect972"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect974"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect976"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.563"
+     x2="21.052"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line978"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.108999"
+     y1="2.563"
+     x2="21.167"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line980"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.681"
+     y1="2.563"
+     x2="21.796"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line982"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.878"
+     x2="20.881001"
+     y2="3.878"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line984"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.8210001"
+     x2="21.91"
+     y2="3.8210001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line986"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.7639999"
+     x2="20.881001"
+     y2="3.7639999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line988"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.707"
+     x2="21.91"
+     y2="3.707"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line990"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.6489999"
+     x2="20.881001"
+     y2="3.6489999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line992"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.592"
+     x2="21.91"
+     y2="3.592"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line994"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.5350001"
+     x2="20.881001"
+     y2="3.5350001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line996"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="18.931999"
+     y="5.4460001"
+     id="text998"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="18.525999"
+     y="6.046"
+     id="text1000"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.16.0/22</text>
+  <text
+     x="14.303"
+     y="4.415"
+     id="text1002"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="14.238"
+     y="4.915"
+     id="text1004"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-BDC</text>
+  <text
+     x="19.816999"
+     y="0.35600001"
+     id="text1006"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="20.266001"
+     y="0.85600001"
+     id="text1008"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-APPS</text>
+  <rect
+     width="1.326"
+     height="1.17"
+     x="12.501"
+     y="2.28"
+     id="rect1010"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="13.164"
+     cy="3.451"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1012"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.164"
+     cy="2.28"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1014"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.164"
+     cy="2.28"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1016"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 13.827,2.28 L 13.827,3.451 C 13.827,3.559 13.53,3.646 13.164,3.646 C 12.798,3.646 12.501,3.559 12.501,3.451 L 12.501,2.28"
+     id="path1018"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.85"
+     y1="2.7939999"
+     x2="14.397"
+     y2="2.7980001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1020"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.809"
+     y="2.9619999"
+     id="text1022"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="12.823"
+     y="3.362"
+     id="text1024"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1026"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1028"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1030"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1032"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1034"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1036"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="10.744"
+     x2="15.309"
+     y2="10.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1038"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.309"
+     y1="10.988"
+     x2="14.336"
+     y2="10.988"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1040"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1042"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1044"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1046"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.275"
+     y1="11.839"
+     x2="15.492"
+     y2="11.839"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1048"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1050"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1052"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1054"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1056"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1058"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1060"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1062"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1064"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1066"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1068"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1070"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1072"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="11.474"
+     x2="15.127"
+     y2="11.474"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1074"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1076"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1078"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1080"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1082"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1084"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1086"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.353"
+     x2="15.066"
+     y2="11.353"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1088"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1090"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1092"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1094"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.127"
+     y1="11.17"
+     x2="15.249"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1096"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="11.9"
+     x2="15.431"
+     y2="11.9"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1098"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="11.961"
+     x2="14.336"
+     y2="11.961"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1100"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="12.022"
+     x2="15.431"
+     y2="12.022"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1102"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="12.204"
+     x2="14.336"
+     y2="12.204"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1104"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="12.143"
+     x2="15.431"
+     y2="12.143"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1106"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="12.083"
+     x2="14.336"
+     y2="12.083"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1108"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.397"
+     y1="11.17"
+     x2="14.458"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1110"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.17"
+     x2="14.579"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1112"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.413"
+     x2="14.579"
+     y2="11.413"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1114"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.005"
+     y1="11.413"
+     x2="15.066"
+     y2="11.413"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1116"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.442"
+     y1="11.353"
+     x2="20.584"
+     y2="11.34"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1118"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.929001"
+     y1="11.349"
+     x2="16.931"
+     y2="12.308"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1120"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.931999"
+     y1="11.349"
+     x2="16.93"
+     y2="10.349"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1122"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.372"
+     y1="11.345"
+     x2="18.374001"
+     y2="12.251"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1124"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.372999"
+     y1="11.345"
+     x2="18.370001"
+     y2="10.345"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1126"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.815001"
+     y1="11.342"
+     x2="19.816999"
+     y2="12.269"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1128"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.813"
+     y1="11.342"
+     x2="19.811001"
+     y2="10.342"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1130"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.921"
+     y="12.276"
+     id="rect1132"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.921"
+     y="12.276"
+     id="rect1134"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.018"
+     y="12.373"
+     id="rect1136"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
+     id="polygon1138"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
+     id="polygon1140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
+     id="polygon1142"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
+     id="polygon1144"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.535"
+     y="12.979"
+     id="rect1146"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.535"
+     y="12.979"
+     id="rect1148"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
+     id="polygon1150"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
+     id="polygon1152"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.364"
+     y="12.265"
+     id="rect1154"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.364"
+     y="12.265"
+     id="rect1156"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.461"
+     y="12.362"
+     id="rect1158"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
+     id="polygon1160"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
+     id="polygon1162"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
+     id="polygon1164"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
+     id="polygon1166"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="19.976999"
+     y="12.968"
+     id="rect1168"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="19.976999"
+     y="12.968"
+     id="rect1170"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
+     id="polygon1172"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
+     id="polygon1174"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.489"
+     y="9.8400002"
+     id="rect1176"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.489"
+     y="9.8400002"
+     id="rect1178"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="16.586"
+     y="9.9370003"
+     id="rect1180"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
+     id="polygon1182"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
+     id="polygon1184"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
+     id="polygon1186"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
+     id="polygon1188"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.101999"
+     y="10.543"
+     id="rect1190"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.101999"
+     y="10.543"
+     id="rect1192"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
+     id="polygon1194"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
+     id="polygon1196"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.938999"
+     y="9.8649998"
+     id="rect1198"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.938999"
+     y="9.8649998"
+     id="rect1200"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.035999"
+     y="9.9619999"
+     id="rect1202"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
+     id="polygon1204"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
+     id="polygon1206"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
+     id="polygon1208"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
+     id="polygon1210"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.552"
+     y="10.568"
+     id="rect1212"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.552"
+     y="10.568"
+     id="rect1214"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
+     id="polygon1216"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
+     id="polygon1218"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.389"
+     y="9.8400002"
+     id="rect1220"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.389"
+     y="9.8400002"
+     id="rect1222"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.486"
+     y="9.9370003"
+     id="rect1224"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
+     id="polygon1226"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
+     id="polygon1228"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
+     id="polygon1230"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
+     id="polygon1232"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.002001"
+     y="10.543"
+     id="rect1234"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.002001"
+     y="10.543"
+     id="rect1236"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
+     id="polygon1238"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
+     id="polygon1240"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
+     id="polygon1242"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
+     id="polygon1244"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.333,12.832 L 16.381,12.852 L 17.437,12.852 L 17.485,12.832"
+     id="path1246"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 17.437,12.852 L 17.509,12.892"
+     id="path1248"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.309,12.892 L 16.381,12.852"
+     id="path1250"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
+     id="polygon1252"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
+     id="polygon1254"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
+     id="polygon1256"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
+     id="polygon1258"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="16.549"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1260"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1262"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1264"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1266"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1268"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1270"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1272"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1274"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1276"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1278"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1280"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1282"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1284"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1286"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1288"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1290"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1292"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1294"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1296"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1298"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1300"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1302"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1304"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1306"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.909"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1308"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="16.909"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1310"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.209"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1312"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.209"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1314"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1316"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1318"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1320"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1322"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1324"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1326"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.731001"
+     y1="10.546"
+     x2="20.816"
+     y2="10.546"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1328"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.816"
+     y1="10.774"
+     x2="21.731001"
+     y2="10.774"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1330"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.731001"
+     y1="10.946"
+     x2="20.816"
+     y2="10.946"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1332"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1334"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1336"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1338"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.701"
+     y1="11.747"
+     x2="21.844999"
+     y2="11.747"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1340"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1342"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1344"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1346"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1348"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1350"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1352"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1354"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1356"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1358"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1360"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1362"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1364"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.816"
+     y1="11.518"
+     x2="21.445"
+     y2="11.518"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1366"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1368"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1370"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1372"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1374"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1376"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1378"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.404"
+     x2="21.388"
+     y2="11.404"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1380"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.388"
+     y1="11.461"
+     x2="21.330999"
+     y2="11.461"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1382"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.461"
+     x2="20.93"
+     y2="11.461"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1384"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1386"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1388"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1390"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.118"
+     x2="20.93"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1392"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.987"
+     y1="11.118"
+     x2="21.045"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1394"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.559"
+     y1="11.118"
+     x2="21.674"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1396"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.433"
+     x2="20.759001"
+     y2="12.433"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1398"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.376"
+     x2="21.788"
+     y2="12.376"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1400"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.319"
+     x2="20.759001"
+     y2="12.319"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1402"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.261"
+     x2="21.788"
+     y2="12.261"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1404"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.204"
+     x2="20.759001"
+     y2="12.204"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1406"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.147"
+     x2="21.788"
+     y2="12.147"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1408"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.09"
+     x2="20.759001"
+     y2="12.09"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1410"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="18.334999"
+     y="14.401"
+     id="text1412"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="17.900999"
+     y="15.001"
+     id="text1414"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.20.0/22</text>
+  <text
+     x="13.937"
+     y="12.893"
+     id="text1416"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="13.608"
+     y="13.393"
+     id="text1418"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WADC-BDC</text>
+  <text
+     x="19.917"
+     y="8.9940004"
+     id="text1420"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="20.101999"
+     y="9.4940004"
+     id="text1422"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WADC-APPS</text>
+  <rect
+     width="1.314"
+     height="1.159"
+     x="12.051"
+     y="10.933"
+     id="rect1424"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="12.708"
+     cy="12.092"
+     rx="0.65700001"
+     ry="0.193"
+     id="ellipse1426"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.708"
+     cy="10.933"
+     rx="0.65700001"
+     ry="0.193"
+     id="ellipse1428"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.708"
+     cy="10.933"
+     rx="0.65700001"
+     ry="0.193"
+     id="ellipse1430"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 13.365,10.933 L 13.365,12.092 C 13.365,12.199 13.071,12.286 12.708,12.286 C 12.345,12.286 12.051,12.199 12.051,12.092 L 12.051,10.933"
+     id="path1432"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="14.275"
+     y1="11.353"
+     x2="13.4"
+     y2="11.368"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1434"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.412"
+     y="11.567"
+     id="text1436"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="12.427"
+     y="11.967"
+     id="text1438"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <path
+     d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
+     id="path1440"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
+     id="path1442"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.7909999"
+     y="11.036"
+     id="text1444"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
+  <path
+     d="M 4.7,11.1 C 5.035363,11.196174 5.3953356,11.076093 5.6057965,10.797841 C 5.8162574,10.51959 5.8338243,10.140524 5.65,9.844"
+     id="path1446"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <path
+     d="M 8.675,9.794 C 7.4940305,10.104758 6.3530779,10.551408 5.275,11.125"
+     id="path1448"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <path
+     d="M 4.7,11.15 C 6.6098972,11.931939 8.7554368,11.904871 10.645,11.075"
+     id="path1450"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1452"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1454"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1456"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1458"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1460"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1462"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.1389999"
+     x2="1.8710001"
+     y2="9.1389999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1464"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.8710001"
+     y1="9.4180002"
+     x2="0.75400001"
+     y2="9.4180002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1466"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.698"
+     x2="1.8710001"
+     y2="9.698"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1468"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.9770002"
+     x2="1.8710001"
+     y2="9.9770002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1470"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.8710001"
+     y1="10.256"
+     x2="0.75400001"
+     y2="10.256"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1472"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1474"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1476"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1478"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.61400002"
+     y1="11.374"
+     x2="2.0109999"
+     y2="11.374"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1480"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1482"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1484"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1486"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1488"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1490"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1492"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1494"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1496"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1498"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1500"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1502"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1504"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="10.885"
+     x2="1.522"
+     y2="10.885"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1506"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1508"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1510"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1512"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1514"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1516"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1518"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.745"
+     x2="1.452"
+     y2="10.745"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1520"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.452"
+     y1="10.815"
+     x2="1.382"
+     y2="10.815"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1522"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.815"
+     x2="0.89300001"
+     y2="10.815"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1524"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1526"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1528"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1530"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.466"
+     x2="0.89300001"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1532"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.963"
+     y1="10.466"
+     x2="1.033"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1534"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.6619999"
+     y1="10.466"
+     x2="1.801"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1536"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.84"
+     x2="1.941"
+     y2="12.84"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1538"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.77"
+     x2="0.68400002"
+     y2="12.77"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1540"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.701"
+     x2="1.941"
+     y2="12.701"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1542"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.631"
+     x2="0.68400002"
+     y2="12.631"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1544"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.561"
+     x2="1.941"
+     y2="12.561"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1546"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.491"
+     x2="0.68400002"
+     y2="12.491"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1548"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.421"
+     x2="1.941"
+     y2="12.421"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1550"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.351"
+     x2="0.68400002"
+     y2="12.351"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1552"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.282"
+     x2="1.941"
+     y2="12.282"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1554"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.212"
+     x2="0.68400002"
+     y2="12.212"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1556"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.142"
+     x2="1.941"
+     y2="12.142"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1558"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.072"
+     x2="0.68400002"
+     y2="12.072"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1560"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.002"
+     x2="1.941"
+     y2="12.002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1562"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="11.932"
+     x2="0.68400002"
+     y2="11.932"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1564"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.3340001"
+     y="11.97"
+     id="rect1566"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.3340001"
+     y="11.97"
+     id="rect1568"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-6.2290001"
+     y="12.076"
+     id="rect1570"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.202,12.699 -5.703,12.699 -5.703,12.812 -6.176,12.812 -6.202,12.699 "
+     id="polygon1572"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.202,12.699 -5.703,12.699 -5.703,12.812 -6.176,12.812 -6.202,12.699 "
+     id="polygon1574"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.703,12.699 -5.494,12.699 -5.521,12.812 -5.703,12.812 -5.703,12.699 "
+     id="polygon1576"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.703,12.699 -5.494,12.699 -5.521,12.812 -5.703,12.812 -5.703,12.699 "
+     id="polygon1578"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.6690001"
+     y="12.733"
+     id="rect1580"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.6690001"
+     y="12.733"
+     id="rect1582"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-5.945,12.812 -5.751,12.812 -5.751,12.869 -5.654,12.869 -5.654,12.925 -6.042,12.925 -6.042,12.869 -5.945,12.869 -5.945,12.812 "
+     id="polygon1584"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.945,12.812 -5.751,12.812 -5.751,12.869 -5.654,12.869 -5.654,12.925 -6.042,12.925 -6.042,12.869 -5.945,12.869 -5.945,12.812 "
+     id="polygon1586"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.62800002"
+     y1="11.055"
+     x2="-9.6000004"
+     y2="11.069"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1588"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-1.312"
+     y1="11.057"
+     x2="-1.314"
+     y2="10.12"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1590"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-3.5769999"
+     y1="11.06"
+     x2="-3.575"
+     y2="12.069"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1592"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-3.573"
+     y1="11.06"
+     x2="-3.5739999"
+     y2="10.399"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1594"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.8520002"
+     y1="11.063"
+     x2="-5.8499999"
+     y2="12.018"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1596"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.8429999"
+     y1="11.063"
+     x2="-5.8439999"
+     y2="10.338"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1598"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-8.0740004"
+     y1="11.066"
+     x2="-8.0749998"
+     y2="10.168"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1600"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.0779999"
+     height="0.80800003"
+     x="-4.079"
+     y="12.008"
+     id="rect1602"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.0779999"
+     height="0.80800003"
+     x="-4.079"
+     y="12.008"
+     id="rect1604"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.84399998"
+     height="0.55699998"
+     x="-3.9619999"
+     y="12.125"
+     id="rect1606"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.933,12.816 -3.378,12.816 -3.378,12.942 -3.903,12.942 -3.933,12.816 "
+     id="polygon1608"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.933,12.816 -3.378,12.816 -3.378,12.942 -3.903,12.942 -3.933,12.816 "
+     id="polygon1610"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-3.378,12.816 -3.147,12.816 -3.176,12.942 -3.378,12.942 -3.378,12.816 "
+     id="polygon1612"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.378,12.816 -3.147,12.816 -3.176,12.942 -3.378,12.942 -3.378,12.816 "
+     id="polygon1614"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050000001"
+     height="0.050000001"
+     x="-3.3399999"
+     y="12.854"
+     id="rect1616"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050000001"
+     height="0.050000001"
+     x="-3.3399999"
+     y="12.854"
+     id="rect1618"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.647,12.942 -3.432,12.942 -3.432,13.005 -3.324,13.005 -3.324,13.068 -3.755,13.068 -3.755,13.005 -3.647,13.005 -3.647,12.942 "
+     id="polygon1620"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.647,12.942 -3.432,12.942 -3.432,13.005 -3.324,13.005 -3.324,13.068 -3.755,13.068 -3.755,13.005 -3.647,13.005 -3.647,12.942 "
+     id="polygon1622"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.329"
+     y="9.3830004"
+     id="rect1624"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.329"
+     y="9.3830004"
+     id="rect1626"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-6.224"
+     y="9.4890003"
+     id="rect1628"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.198,10.112 -5.698,10.112 -5.698,10.225 -6.171,10.225 -6.198,10.112 "
+     id="polygon1630"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.198,10.112 -5.698,10.112 -5.698,10.225 -6.171,10.225 -6.198,10.112 "
+     id="polygon1632"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.698,10.112 -5.49,10.112 -5.516,10.225 -5.698,10.225 -5.698,10.112 "
+     id="polygon1634"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.698,10.112 -5.49,10.112 -5.516,10.225 -5.698,10.225 -5.698,10.112 "
+     id="polygon1636"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.664"
+     y="10.146"
+     id="rect1638"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.664"
+     y="10.146"
+     id="rect1640"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-5.941,10.225 -5.746,10.225 -5.746,10.282 -5.649,10.282 -5.649,10.338 -6.038,10.338 -6.038,10.282 -5.941,10.282 -5.941,10.225 "
+     id="polygon1642"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.941,10.225 -5.746,10.225 -5.746,10.282 -5.649,10.282 -5.649,10.338 -6.038,10.338 -6.038,10.282 -5.941,10.282 -5.941,10.225 "
+     id="polygon1644"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-4.0599999"
+     y="9.4449997"
+     id="rect1646"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-4.0599999"
+     y="9.4449997"
+     id="rect1648"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-3.9549999"
+     y="9.5500002"
+     id="rect1650"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.928,10.173 -3.429,10.173 -3.429,10.286 -3.902,10.286 -3.928,10.173 "
+     id="polygon1652"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.928,10.173 -3.429,10.173 -3.429,10.286 -3.902,10.286 -3.928,10.173 "
+     id="polygon1654"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-3.429,10.173 -3.22,10.173 -3.247,10.286 -3.429,10.286 -3.429,10.173 "
+     id="polygon1656"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.429,10.173 -3.22,10.173 -3.247,10.286 -3.429,10.286 -3.429,10.173 "
+     id="polygon1658"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-3.395"
+     y="10.207"
+     id="rect1660"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-3.395"
+     y="10.207"
+     id="rect1662"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.671,10.286 -3.477,10.286 -3.477,10.343 -3.38,10.343 -3.38,10.399 -3.769,10.399 -3.769,10.343 -3.671,10.343 -3.671,10.286 "
+     id="polygon1664"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.671,10.286 -3.477,10.286 -3.477,10.343 -3.38,10.343 -3.38,10.399 -3.769,10.399 -3.769,10.343 -3.671,10.343 -3.671,10.286 "
+     id="polygon1666"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-10.578"
+     y="10.617"
+     id="rect1668"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-10.578"
+     y="10.617"
+     id="rect1670"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-10.473"
+     y="10.722"
+     id="rect1672"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-10.446,11.345 -9.947,11.345 -9.947,11.458 -10.42,11.458 -10.446,11.345 "
+     id="polygon1674"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-10.446,11.345 -9.947,11.345 -9.947,11.458 -10.42,11.458 -10.446,11.345 "
+     id="polygon1676"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-9.947,11.345 -9.738,11.345 -9.765,11.458 -9.947,11.458 -9.947,11.345 "
+     id="polygon1678"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-9.947,11.345 -9.738,11.345 -9.765,11.458 -9.947,11.458 -9.947,11.345 "
+     id="polygon1680"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-9.9130001"
+     y="11.379"
+     id="rect1682"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-9.9130001"
+     y="11.379"
+     id="rect1684"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-10.19,11.458 -9.995,11.458 -9.995,11.515 -9.898,11.515 -9.898,11.571 -10.287,11.571 -10.287,11.515 -10.19,11.515 -10.19,11.458 "
+     id="polygon1686"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-10.19,11.458 -9.995,11.458 -9.995,11.515 -9.898,11.515 -9.898,11.571 -10.287,11.571 -10.287,11.515 -10.19,11.515 -10.19,11.458 "
+     id="polygon1688"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-1.726,9.492 -1.775,9.513 -1.92,9.877 -1.92,10.059 -1.848,10.12 -0.779,10.12 -0.707,10.059 -0.707,9.877 -0.852,9.513 -0.901,9.492 -1.726,9.492 "
+     id="polygon1690"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.726,9.492 -1.775,9.513 -1.92,9.877 -1.92,10.059 -1.848,10.12 -0.779,10.12 -0.707,10.059 -0.707,9.877 -0.852,9.513 -0.901,9.492 -1.726,9.492 "
+     id="polygon1692"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -1.896,9.816 L -1.848,9.836 L -0.779,9.836 L -0.731,9.816"
+     id="path1694"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -0.779,9.836 L -0.707,9.877"
+     id="path1696"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -1.92,9.877 L -1.848,9.836"
+     id="path1698"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.581,9.108 -1.605,9.593 -1.022,9.593 -1.046,9.108 -1.581,9.108 "
+     id="polygon1700"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.581,9.108 -1.605,9.593 -1.022,9.593 -1.046,9.108 -1.581,9.108 "
+     id="polygon1702"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.678,9.593 -1.726,9.735 -0.901,9.735 -0.949,9.593 -1.678,9.593 "
+     id="polygon1704"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.678,9.593 -1.726,9.735 -0.901,9.735 -0.949,9.593 -1.678,9.593 "
+     id="polygon1706"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="-1.678"
+     cy="9.9069996"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1708"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.678"
+     cy="9.9069996"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1710"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.556"
+     cy="9.9069996"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1712"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.556"
+     cy="9.9069996"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1714"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.4349999"
+     cy="9.9069996"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1716"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.4349999"
+     cy="9.9069996"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1718"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.678"
+     cy="9.9580002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1720"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.678"
+     cy="9.9580002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1722"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.556"
+     cy="9.9580002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1724"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.556"
+     cy="9.9580002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1726"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.4349999"
+     cy="9.9580002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1728"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.4349999"
+     cy="9.9580002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1730"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.678"
+     cy="10.008"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1732"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.678"
+     cy="10.008"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1734"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.556"
+     cy="10.008"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1736"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.556"
+     cy="10.008"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1738"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.4349999"
+     cy="10.008"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1740"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.4349999"
+     cy="10.008"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1742"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.678"
+     cy="10.059"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1744"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.678"
+     cy="10.059"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1746"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.556"
+     cy="10.059"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1748"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.556"
+     cy="10.059"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1750"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.4349999"
+     cy="10.059"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1752"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.4349999"
+     cy="10.059"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1754"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.314"
+     cy="9.9169998"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1756"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-1.314"
+     cy="9.9169998"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1758"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.01"
+     cy="9.9169998"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1760"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-1.01"
+     cy="9.9169998"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1762"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.159"
+     height="2.3180001"
+     x="-8.6300001"
+     y="8.4790001"
+     id="rect1764"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.159"
+     height="2.3180001"
+     x="-8.6300001"
+     y="8.4790001"
+     id="rect1766"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.159"
+     height="2.3180001"
+     x="-8.6300001"
+     y="8.4790001"
+     id="rect1768"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.92699999"
+     height="0.92699999"
+     x="-8.5150003"
+     y="8.5950003"
+     id="rect1770"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.92699999"
+     height="0.92699999"
+     x="-8.5150003"
+     y="8.5950003"
+     id="rect1772"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.92699999"
+     height="0.92699999"
+     x="-8.5150003"
+     y="8.5950003"
+     id="rect1774"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5869999"
+     y1="8.8260002"
+     x2="-8.5150003"
+     y2="8.8260002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1776"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5150003"
+     y1="9.0579996"
+     x2="-7.5869999"
+     y2="9.0579996"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1778"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5869999"
+     y1="9.2320004"
+     x2="-8.5150003"
+     y2="9.2320004"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1780"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.63800001"
+     height="0.34799999"
+     x="-8.5150003"
+     y="9.6379995"
+     id="rect1782"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.63800001"
+     height="0.34799999"
+     x="-8.5150003"
+     y="9.6379995"
+     id="rect1784"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.63800001"
+     height="0.34799999"
+     x="-8.5150003"
+     y="9.6379995"
+     id="rect1786"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6300001"
+     y1="10.044"
+     x2="-7.4710002"
+     y2="10.044"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1788"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-8.1090002"
+     y="10.16"
+     id="rect1790"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-8.1090002"
+     y="10.16"
+     id="rect1792"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-8.1090002"
+     y="10.16"
+     id="rect1794"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.8769999"
+     y="10.16"
+     id="rect1796"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.8769999"
+     y="10.16"
+     id="rect1798"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.8769999"
+     y="10.16"
+     id="rect1800"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.645"
+     y="10.16"
+     id="rect1802"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.645"
+     y="10.16"
+     id="rect1804"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.645"
+     y="10.16"
+     id="rect1806"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.116"
+     height="0.057999998"
+     x="-7.7030001"
+     y="9.8120003"
+     id="rect1808"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.116"
+     height="0.057999998"
+     x="-7.7030001"
+     y="9.8120003"
+     id="rect1810"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.116"
+     height="0.057999998"
+     x="-7.7030001"
+     y="9.8120003"
+     id="rect1812"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5150003"
+     y1="9.8120003"
+     x2="-7.8769999"
+     y2="9.8120003"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1814"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17399999"
+     height="0.17399999"
+     x="-8.5150003"
+     y="10.102"
+     id="rect1816"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17399999"
+     height="0.17399999"
+     x="-8.5150003"
+     y="10.102"
+     id="rect1818"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17399999"
+     height="0.17399999"
+     x="-8.5150003"
+     y="10.102"
+     id="rect1820"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.81099999"
+     height="0.057999998"
+     x="-8.4569998"
+     y="9.29"
+     id="rect1822"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.81099999"
+     height="0.057999998"
+     x="-8.4569998"
+     y="9.29"
+     id="rect1824"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.81099999"
+     height="0.057999998"
+     x="-8.4569998"
+     y="9.29"
+     id="rect1826"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4569998"
+     y1="9.6960001"
+     x2="-7.9349999"
+     y2="9.6960001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1828"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.9349999"
+     y1="9.7539997"
+     x2="-7.993"
+     y2="9.7539997"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1830"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4569998"
+     y1="9.7539997"
+     x2="-8.3990002"
+     y2="9.7539997"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1832"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28999999"
+     height="0.057999998"
+     x="-8.3409996"
+     y="9.6960001"
+     id="rect1834"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28999999"
+     height="0.057999998"
+     x="-8.3409996"
+     y="9.6960001"
+     id="rect1836"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28999999"
+     height="0.057999998"
+     x="-8.3409996"
+     y="9.6960001"
+     id="rect1838"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4569998"
+     y1="9.4060001"
+     x2="-8.3990002"
+     y2="9.4060001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1840"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.3409996"
+     y1="9.4060001"
+     x2="-8.283"
+     y2="9.4060001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1842"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.7610002"
+     y1="9.4060001"
+     x2="-7.645"
+     y2="9.4060001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1844"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5289998"
+     y1="10.739"
+     x2="-8.573"
+     y2="10.739"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1846"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.573"
+     y1="10.681"
+     x2="-7.5289998"
+     y2="10.681"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1848"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5289998"
+     y1="10.623"
+     x2="-8.573"
+     y2="10.623"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1850"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.573"
+     y1="10.565"
+     x2="-7.5289998"
+     y2="10.565"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1852"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5289998"
+     y1="10.507"
+     x2="-8.573"
+     y2="10.507"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1854"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.573"
+     y1="10.449"
+     x2="-7.5289998"
+     y2="10.449"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1856"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5289998"
+     y1="10.391"
+     x2="-8.573"
+     y2="10.391"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1858"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="-5.5710001"
+     y="13.811"
+     id="text1860"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="-5.9060001"
+     y="14.411"
+     id="text1862"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.0.0/22</text>
+  <text
+     x="-10.233"
+     y="7.7189999"
+     id="text1864"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="-9.9090004"
+     y="8.2189999"
+     id="text1866"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GNY-APPS</text>
+  <rect
+     width="1.4450001"
+     height="1.275"
+     x="2.5510001"
+     y="8.6120005"
+     id="rect1868"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="3.273"
+     cy="9.8870001"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1870"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.273"
+     cy="8.6120005"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1872"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.273"
+     cy="8.6120005"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1874"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.996,8.612 L 3.996,9.887 C 3.996,10.005 3.672,10.1 3.273,10.1 C 2.874,10.1 2.551,10.005 2.551,9.887 L 2.551,8.612"
+     id="path1876"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="2.0109999"
+     y1="9.2469997"
+     x2="2.586"
+     y2="9.2469997"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1878"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.983"
+     y="9.3260002"
+     id="text1880"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="2.928"
+     y="9.7259998"
+     id="text1882"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="5.725,19.819 5.725,18.237 5.732,18.237 5.732,17.325 "
+     id="polyline1884"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-10.458"
+     y="15.156"
+     id="text1886"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">1100 Users</text>
+  <text
+     x="1.136"
+     y="6.0770001"
+     id="text1888"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">320 Users</text>
+  <text
+     x="12.943"
+     y="6.0310001"
+     id="text1890"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">180 Users</text>
+  <text
+     x="12.358"
+     y="15.177"
+     id="text1892"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
+  <text
+     x="-4.4629998"
+     y="8.1560001"
+     id="text1894"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York - GNY</text>
+  <text
+     x="13.214"
+     y="0.46399999"
+     id="text1896"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Los Angeles</text>
+  <text
+     x="1.1109999"
+     y="0.46399999"
+     id="text1898"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">London</text>
+  <text
+     x="12.979"
+     y="8.0889997"
+     id="text1900"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Washington, DC</text>
+  <rect
+     width="11.132"
+     height="6.5630002"
+     x="-11.146"
+     y="16.205999"
+     id="rect1902"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
+     id="path1904"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
+     id="path1906"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.732"
+     height="5.9629998"
+     x="-11.446"
+     y="16.506001"
+     id="rect1908"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
+     id="path1910"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
+     id="path1912"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="-11.146"
+     y1="16.205999"
+     x2="-0.014"
+     y2="16.205999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1914"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.146"
+     y1="22.768999"
+     x2="-0.014"
+     y2="22.768999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1916"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
+     id="path1918"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
+     id="path1920"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.446"
+     y1="16.506001"
+     x2="-11.446"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1922"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.28600001"
+     y1="16.506001"
+     x2="0.28600001"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1924"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
+     id="path1926"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
+     id="path1928"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1930"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1932"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1934"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
+     id="path1936"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
+     id="path1938"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
+     id="polygon1940"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
+     id="polygon1942"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
+     id="polygon1944"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
+     id="polygon1946"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
+     id="path1948"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
+     id="path1950"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
+     id="polygon1952"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
+     id="polygon1954"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
+     id="polygon1956"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
+     id="polygon1958"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-5.2220001"
+     y="17.145"
+     id="text1960"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="-5.5609999"
+     y="17.745001"
+     id="text1962"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.4.0/22</text>
+  <text
+     x="-10.001"
+     y="21.07"
+     id="text1964"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="-10.37"
+     y="21.57"
+     id="text1966"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1968"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1970"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1972"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1974"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1976"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1978"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="19.087"
+     x2="-7.6300001"
+     y2="19.087"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1980"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.6300001"
+     y1="19.33"
+     x2="-8.6040001"
+     y2="19.33"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1982"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1984"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1986"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1988"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.665"
+     y1="20.181999"
+     x2="-7.448"
+     y2="20.181999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1990"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1992"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1994"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1996"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect1998"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect2000"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect2002"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2004"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2006"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2008"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2010"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2012"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2014"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4820004"
+     y1="19.816999"
+     x2="-7.8130002"
+     y2="19.816999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2016"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2018"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2020"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2022"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2024"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2026"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2028"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.695"
+     x2="-7.8740001"
+     y2="19.695"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2030"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2032"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2034"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2036"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.8130002"
+     y1="19.511999"
+     x2="-7.691"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2038"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.242001"
+     x2="-7.5089998"
+     y2="20.242001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2040"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.302999"
+     x2="-8.6040001"
+     y2="20.302999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2042"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.364"
+     x2="-7.5089998"
+     y2="20.364"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2044"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.547001"
+     x2="-8.6040001"
+     y2="20.547001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2046"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.486"
+     x2="-7.5089998"
+     y2="20.486"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2048"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.424999"
+     x2="-8.6040001"
+     y2="20.424999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2050"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5430002"
+     y1="19.511999"
+     x2="-8.4820004"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2052"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.511999"
+     x2="-8.3599997"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2054"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.756001"
+     x2="-8.3599997"
+     y2="19.756001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2056"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.9349999"
+     y1="19.756001"
+     x2="-7.8740001"
+     y2="19.756001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2058"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.4980001"
+     y1="19.695"
+     x2="-2.164"
+     y2="19.679001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2060"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.9559999"
+     y1="19.690001"
+     x2="-5.9530001"
+     y2="20.649"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2062"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.9530001"
+     y1="19.690001"
+     x2="-5.9559999"
+     y2="18.690001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2064"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-4.4590001"
+     y1="19.686001"
+     x2="-4.4559999"
+     y2="20.591"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2066"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-4.4569998"
+     y1="19.686001"
+     x2="-4.46"
+     y2="18.686001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2068"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-2.961"
+     y1="19.681"
+     x2="-2.9579999"
+     y2="20.608"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2070"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-2.9619999"
+     y1="19.681"
+     x2="-2.9649999"
+     y2="18.681"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2072"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.9439998"
+     y="20.618"
+     id="rect2074"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.9439998"
+     y="20.618"
+     id="rect2076"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-4.8470001"
+     y="20.715"
+     id="rect2078"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
+     id="polygon2080"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
+     id="polygon2082"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
+     id="polygon2084"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
+     id="polygon2086"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.3299999"
+     y="21.320999"
+     id="rect2088"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.3299999"
+     y="21.320999"
+     id="rect2090"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
+     id="polygon2092"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
+     id="polygon2094"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.4260001"
+     y="20.607"
+     id="rect2096"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.4260001"
+     y="20.607"
+     id="rect2098"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-3.329"
+     y="20.704"
+     id="rect2100"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
+     id="polygon2102"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
+     id="polygon2104"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
+     id="polygon2106"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
+     id="polygon2108"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.813"
+     y="21.311001"
+     id="rect2110"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.813"
+     y="21.311001"
+     id="rect2112"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
+     id="polygon2114"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
+     id="polygon2116"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-6.3759999"
+     y="18.181999"
+     id="rect2118"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-6.3759999"
+     y="18.181999"
+     id="rect2120"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-6.2789998"
+     y="18.278999"
+     id="rect2122"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
+     id="polygon2124"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
+     id="polygon2126"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
+     id="polygon2128"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
+     id="polygon2130"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-5.763"
+     y="18.886"
+     id="rect2132"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-5.763"
+     y="18.886"
+     id="rect2134"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
+     id="polygon2136"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
+     id="polygon2138"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.901"
+     y="18.181999"
+     id="rect2140"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.901"
+     y="18.181999"
+     id="rect2142"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-4.8039999"
+     y="18.278999"
+     id="rect2144"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
+     id="polygon2146"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
+     id="polygon2148"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
+     id="polygon2150"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
+     id="polygon2152"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.2880001"
+     y="18.886"
+     id="rect2154"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.2880001"
+     y="18.886"
+     id="rect2156"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
+     id="polygon2158"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
+     id="polygon2160"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.401"
+     y="18.207001"
+     id="rect2162"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.401"
+     y="18.207001"
+     id="rect2164"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-3.3039999"
+     y="18.304001"
+     id="rect2166"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
+     id="polygon2168"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
+     id="polygon2170"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
+     id="polygon2172"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
+     id="polygon2174"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.7880001"
+     y="18.910999"
+     id="rect2176"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.7880001"
+     y="18.910999"
+     id="rect2178"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
+     id="polygon2180"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
+     id="polygon2182"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
+     id="polygon2184"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
+     id="polygon2186"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -6.607,21.174 L -6.559,21.194 L -5.503,21.194 L -5.455,21.174"
+     id="path2188"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -5.503,21.194 L -5.431,21.234"
+     id="path2190"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -6.631,21.234 L -6.559,21.194"
+     id="path2192"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
+     id="polygon2194"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
+     id="polygon2196"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
+     id="polygon2198"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
+     id="polygon2200"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2202"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2204"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2206"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2208"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2210"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2212"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2214"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2216"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2218"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2220"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2222"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2224"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2226"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2228"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2230"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2232"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2234"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2236"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2238"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2240"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2242"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2244"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2246"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2248"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.0310001"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2250"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-6.0310001"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2252"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-5.7309999"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2254"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-5.7309999"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2256"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.2410001"
+     height="1.095"
+     x="-10.66"
+     y="19.143"
+     id="rect2258"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="-10.04"
+     cy="20.238001"
+     rx="0.62099999"
+     ry="0.183"
+     id="ellipse2260"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="-10.04"
+     cy="19.143"
+     rx="0.62099999"
+     ry="0.183"
+     id="ellipse2262"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="-10.04"
+     cy="19.143"
+     rx="0.62099999"
+     ry="0.183"
+     id="ellipse2264"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -9.419,19.143 L -9.419,20.238 C -9.419,20.338 -9.697,20.42 -10.04,20.42 C -10.382,20.42 -10.66,20.338 -10.66,20.238 L -10.66,19.143"
+     id="path2266"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-9.3959999"
+     y1="19.684"
+     x2="-8.665"
+     y2="19.695"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2268"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-10.328"
+     y="19.759001"
+     id="text2270"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="-10.313"
+     y="20.159"
+     id="text2272"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <text
+     x="-0.91500002"
+     y="19.843"
+     id="text2274"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <text
+     x="-2.1919999"
+     y="22.406"
+     id="text2276"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
+  <text
+     x="-10.31"
+     y="17.143"
+     id="text2278"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
+  <text
+     x="-9.9130001"
+     y="17.944"
+     id="text2280"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg2</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="-1.525,15.094 -1.525,15.906 -1.821,15.906 -1.821,19.285 "
+     id="polyline2282"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2284"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2286"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2288"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
+     id="path2290"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
+     id="path2292"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
+     id="polygon2294"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
+     id="polygon2296"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
+     id="polygon2298"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
+     id="polygon2300"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
+     id="path2302"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
+     id="path2304"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
+     id="polygon2306"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
+     id="polygon2308"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
+     id="polygon2310"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
+     id="polygon2312"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7.5560002"
+     y="17.367001"
+     id="text2314"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="7.2179999"
+     y="17.966999"
+     id="text2316"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.8.0/22</text>
+  <text
+     x="3.204"
+     y="18.118"
+     id="text2318"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="2.835"
+     y="18.618"
+     id="text2320"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-BDC</text>
+  <text
+     x="11.592"
+     y="21.718"
+     id="text2322"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="11.737"
+     y="22.218"
+     id="text2324"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-APPS</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2326"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2328"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2330"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2332"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2334"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2336"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="19.246"
+     x2="5.112"
+     y2="19.246"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2338"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.112"
+     y1="19.49"
+     x2="4.138"
+     y2="19.49"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2340"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2342"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2344"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2346"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.0770001"
+     y1="20.341"
+     x2="5.2940001"
+     y2="20.341"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2348"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2350"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2352"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2354"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2356"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2358"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2360"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2362"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2364"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2366"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2368"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2370"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2372"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.2600002"
+     y1="19.976"
+     x2="4.9289999"
+     y2="19.976"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2374"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2376"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2378"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2380"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2382"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2384"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2386"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.855"
+     x2="4.868"
+     y2="19.855"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2388"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2390"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2392"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2394"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.9289999"
+     y1="19.672001"
+     x2="5.0510001"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2396"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.402"
+     x2="5.2329998"
+     y2="20.402"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2398"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.462999"
+     x2="4.138"
+     y2="20.462999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2400"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.524"
+     x2="5.2329998"
+     y2="20.524"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2402"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.705999"
+     x2="4.138"
+     y2="20.705999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2404"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.645"
+     x2="5.2329998"
+     y2="20.645"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2406"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.584999"
+     x2="4.138"
+     y2="20.584999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2408"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.1989999"
+     y1="19.672001"
+     x2="4.2600002"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2410"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.672001"
+     x2="4.382"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2412"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.915001"
+     x2="4.382"
+     y2="19.915001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2414"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.8070002"
+     y1="19.915001"
+     x2="4.868"
+     y2="19.915001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2416"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.244"
+     y1="19.855"
+     x2="10.386"
+     y2="19.841999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2418"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.7309999"
+     y1="19.851"
+     x2="6.7329998"
+     y2="20.809999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2420"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.7350001"
+     y1="19.851"
+     x2="6.7319999"
+     y2="18.851"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2422"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.1739998"
+     y1="19.847"
+     x2="8.1759996"
+     y2="20.753"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2424"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.1750002"
+     y1="19.847"
+     x2="8.1730003"
+     y2="18.848"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2426"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.6169996"
+     y1="19.844"
+     x2="9.6190004"
+     y2="20.771"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2428"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.6160002"
+     y1="19.844"
+     x2="9.6129999"
+     y2="18.844"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2430"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.723"
+     y="20.778"
+     id="rect2432"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.723"
+     y="20.778"
+     id="rect2434"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.8210001"
+     y="20.875"
+     id="rect2436"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
+     id="polygon2438"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
+     id="polygon2440"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
+     id="polygon2442"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
+     id="polygon2444"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3369999"
+     y="21.481001"
+     id="rect2446"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3369999"
+     y="21.481001"
+     id="rect2448"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
+     id="polygon2450"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
+     id="polygon2452"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.1660004"
+     y="20.767"
+     id="rect2454"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.1660004"
+     y="20.767"
+     id="rect2456"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="9.2629995"
+     y="20.864"
+     id="rect2458"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
+     id="polygon2460"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
+     id="polygon2462"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
+     id="polygon2464"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
+     id="polygon2466"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.7790003"
+     y="21.469999"
+     id="rect2468"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.7790003"
+     y="21.469999"
+     id="rect2470"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
+     id="polygon2472"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
+     id="polygon2474"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.2909999"
+     y="18.341999"
+     id="rect2476"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.2909999"
+     y="18.341999"
+     id="rect2478"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.388"
+     y="18.438999"
+     id="rect2480"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
+     id="polygon2482"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
+     id="polygon2484"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
+     id="polygon2486"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
+     id="polygon2488"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.9039998"
+     y="19.045"
+     id="rect2490"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.9039998"
+     y="19.045"
+     id="rect2492"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
+     id="polygon2494"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
+     id="polygon2496"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.7410002"
+     y="18.367001"
+     id="rect2498"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.7410002"
+     y="18.367001"
+     id="rect2500"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.8379998"
+     y="18.464001"
+     id="rect2502"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
+     id="polygon2504"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
+     id="polygon2506"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
+     id="polygon2508"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
+     id="polygon2510"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3540001"
+     y="19.07"
+     id="rect2512"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3540001"
+     y="19.07"
+     id="rect2514"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
+     id="polygon2516"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
+     id="polygon2518"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.191"
+     y="18.341999"
+     id="rect2520"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.191"
+     y="18.341999"
+     id="rect2522"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="9.2880001"
+     y="18.438999"
+     id="rect2524"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
+     id="polygon2526"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
+     id="polygon2528"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
+     id="polygon2530"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
+     id="polygon2532"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.8039999"
+     y="19.045"
+     id="rect2534"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.8039999"
+     y="19.045"
+     id="rect2536"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
+     id="polygon2538"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
+     id="polygon2540"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
+     id="polygon2542"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
+     id="polygon2544"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 6.135,21.334 L 6.183,21.354 L 7.239,21.354 L 7.287,21.334"
+     id="path2546"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.239,21.354 L 7.311,21.394"
+     id="path2548"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 6.111,21.394 L 6.183,21.354"
+     id="path2550"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
+     id="polygon2552"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
+     id="polygon2554"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
+     id="polygon2556"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
+     id="polygon2558"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2560"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2562"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2564"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2566"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2568"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2570"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2572"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2574"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2576"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2578"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2580"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2582"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2584"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2586"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2588"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2590"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2592"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2594"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2596"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2598"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2600"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2602"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2604"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2606"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.711"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2608"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="6.711"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2610"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.0110002"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2612"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="7.0110002"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2614"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2616"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2618"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2620"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2622"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2624"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2626"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.533"
+     y1="19.048"
+     x2="10.618"
+     y2="19.048"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2628"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.618"
+     y1="19.275999"
+     x2="11.533"
+     y2="19.275999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2630"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.533"
+     y1="19.448"
+     x2="10.618"
+     y2="19.448"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2632"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2634"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2636"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2638"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.504"
+     y1="20.249001"
+     x2="11.647"
+     y2="20.249001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2640"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2642"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2644"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2646"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2648"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2650"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2652"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2654"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2656"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2658"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2660"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2662"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2664"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.618"
+     y1="20.02"
+     x2="11.247"
+     y2="20.02"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2666"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2668"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2670"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2672"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2674"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2676"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2678"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.906"
+     x2="11.19"
+     y2="19.906"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2680"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.19"
+     y1="19.962999"
+     x2="11.133"
+     y2="19.962999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2682"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.962999"
+     x2="10.732"
+     y2="19.962999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2684"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2686"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2688"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2690"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.620001"
+     x2="10.732"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.79"
+     y1="19.620001"
+     x2="10.847"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.362"
+     y1="19.620001"
+     x2="11.476"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.934999"
+     x2="10.561"
+     y2="20.934999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2698"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.878"
+     x2="11.59"
+     y2="20.878"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2700"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.820999"
+     x2="10.561"
+     y2="20.820999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2702"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.763"
+     x2="11.59"
+     y2="20.763"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2704"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.705999"
+     x2="10.561"
+     y2="20.705999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2706"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.649"
+     x2="11.59"
+     y2="20.649"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2708"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.591999"
+     x2="10.561"
+     y2="20.591999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2710"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.4960001"
+     y1="19.819"
+     x2="4.0770001"
+     y2="19.855"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2712"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.183"
+     height="1.044"
+     x="2.302"
+     y="19.268999"
+     id="rect2714"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="2.8940001"
+     cy="20.312"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2716"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="2.8940001"
+     cy="19.268999"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2718"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="2.8940001"
+     cy="19.268999"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2720"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.485,19.269 L 3.485,20.312 C 3.485,20.409 3.221,20.486 2.894,20.486 C 2.567,20.486 2.302,20.409 2.302,20.312 L 2.302,19.269"
+     id="path2722"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.589"
+     y="19.868999"
+     id="text2724"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="2.6040001"
+     y="20.268999"
+     id="text2726"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <text
+     x="2.0469999"
+     y="22.452"
+     id="text2728"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">250 Users</text>
+  <text
+     x="12.072"
+     y="17.239"
+     id="text2730"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
+  <text
+     x="12.468"
+     y="18.039"
+     id="text2732"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg3</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="-1.129,15.125 -1.129,15.903 5.732,15.903 5.732,16.538 "
+     id="polyline2734"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.1"
+     y1="22.393"
+     x2="15.55"
+     y2="23.143"
+     stroke="#F7F7F7"
+     stroke-width="0.100"
+     id="line2736"
+     style="stroke:#f7f7f7;stroke-width:0.1" />
+  <rect
+     width="1.159"
+     height="2.3180001"
+     x="-8.6529999"
+     y="11.306"
+     id="rect2738"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.159"
+     height="2.3180001"
+     x="-8.6529999"
+     y="11.306"
+     id="rect2740"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.159"
+     height="2.3180001"
+     x="-8.6529999"
+     y="11.306"
+     id="rect2742"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.92699999"
+     height="0.92699999"
+     x="-8.5369997"
+     y="11.422"
+     id="rect2744"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.92699999"
+     height="0.92699999"
+     x="-8.5369997"
+     y="11.422"
+     id="rect2746"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.92699999"
+     height="0.92699999"
+     x="-8.5369997"
+     y="11.422"
+     id="rect2748"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.6100001"
+     y1="11.654"
+     x2="-8.5369997"
+     y2="11.654"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2750"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5369997"
+     y1="11.886"
+     x2="-7.6100001"
+     y2="11.886"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2752"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.6100001"
+     y1="12.059"
+     x2="-8.5369997"
+     y2="12.059"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2754"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.63800001"
+     height="0.34799999"
+     x="-8.5369997"
+     y="12.465"
+     id="rect2756"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.63800001"
+     height="0.34799999"
+     x="-8.5369997"
+     y="12.465"
+     id="rect2758"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.63800001"
+     height="0.34799999"
+     x="-8.5369997"
+     y="12.465"
+     id="rect2760"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6529999"
+     y1="12.871"
+     x2="-7.494"
+     y2="12.871"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2762"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-8.1309996"
+     y="12.987"
+     id="rect2764"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-8.1309996"
+     y="12.987"
+     id="rect2766"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-8.1309996"
+     y="12.987"
+     id="rect2768"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.8990002"
+     y="12.987"
+     id="rect2770"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.8990002"
+     y="12.987"
+     id="rect2772"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.8990002"
+     y="12.987"
+     id="rect2774"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.6680002"
+     y="12.987"
+     id="rect2776"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.6680002"
+     y="12.987"
+     id="rect2778"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057999998"
+     height="0.057999998"
+     x="-7.6680002"
+     y="12.987"
+     id="rect2780"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.116"
+     height="0.057999998"
+     x="-7.7259998"
+     y="12.639"
+     id="rect2782"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.116"
+     height="0.057999998"
+     x="-7.7259998"
+     y="12.639"
+     id="rect2784"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.116"
+     height="0.057999998"
+     x="-7.7259998"
+     y="12.639"
+     id="rect2786"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5369997"
+     y1="12.639"
+     x2="-7.8990002"
+     y2="12.639"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2788"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17399999"
+     height="0.17399999"
+     x="-8.5369997"
+     y="12.929"
+     id="rect2790"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17399999"
+     height="0.17399999"
+     x="-8.5369997"
+     y="12.929"
+     id="rect2792"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17399999"
+     height="0.17399999"
+     x="-8.5369997"
+     y="12.929"
+     id="rect2794"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.81099999"
+     height="0.057999998"
+     x="-8.4790001"
+     y="12.117"
+     id="rect2796"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.81099999"
+     height="0.057999998"
+     x="-8.4790001"
+     y="12.117"
+     id="rect2798"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.81099999"
+     height="0.057999998"
+     x="-8.4790001"
+     y="12.117"
+     id="rect2800"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4790001"
+     y1="12.523"
+     x2="-7.9569998"
+     y2="12.523"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2802"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.9569998"
+     y1="12.581"
+     x2="-8.0150003"
+     y2="12.581"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2804"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4790001"
+     y1="12.581"
+     x2="-8.4209995"
+     y2="12.581"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2806"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28999999"
+     height="0.057999998"
+     x="-8.3629999"
+     y="12.523"
+     id="rect2808"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28999999"
+     height="0.057999998"
+     x="-8.3629999"
+     y="12.523"
+     id="rect2810"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28999999"
+     height="0.057999998"
+     x="-8.3629999"
+     y="12.523"
+     id="rect2812"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4790001"
+     y1="12.233"
+     x2="-8.4209995"
+     y2="12.233"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2814"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.3629999"
+     y1="12.233"
+     x2="-8.3050003"
+     y2="12.233"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2816"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.7839999"
+     y1="12.233"
+     x2="-7.6680002"
+     y2="12.233"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2818"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.552"
+     y1="13.566"
+     x2="-8.5950003"
+     y2="13.566"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2820"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5950003"
+     y1="13.508"
+     x2="-7.552"
+     y2="13.508"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2822"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.552"
+     y1="13.45"
+     x2="-8.5950003"
+     y2="13.45"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2824"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5950003"
+     y1="13.393"
+     x2="-7.552"
+     y2="13.393"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2826"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.552"
+     y1="13.335"
+     x2="-8.5950003"
+     y2="13.335"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2828"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5950003"
+     y1="13.277"
+     x2="-7.552"
+     y2="13.277"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2830"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.552"
+     y1="13.219"
+     x2="-8.5950003"
+     y2="13.219"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2832"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.0749998"
+     y1="11.094"
+     x2="-8.1000004"
+     y2="11.344"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2834"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-10.538"
+     y="12.993"
+     id="text2836"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="-10.728"
+     y="13.493"
+     id="text2838"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GNY-DBC</text>
+  <text
+     x="-11.175"
+     y="2.119"
+     id="text2840"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Here there is a single Windows Network|</text>
+  <text
+     x="-11.175"
+     y="2.7190001"
+     id="text2842"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain. There is an LDAP Master in GNY</text>
+  <text
+     x="-11.175"
+     y="3.319"
+     id="text2844"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">with a Slave LDAP server in each remote</text>
+  <text
+     x="-11.175"
+     y="3.9189999"
+     id="text2846"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">office. There is at least one Application</text>
+  <text
+     x="-11.175"
+     y="4.5190001"
+     id="text2848"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">server in each office and at least one BDC</text>
+  <text
+     x="-11.175"
+     y="5.119"
+     id="text2850"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">in every office.</text>
+  <text
+     x="-11.175"
+     y="6.3189998"
+     id="text2852"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">There is 1 BDC per 50 users.</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap7-net-Ar.png b/docs-xml/Samba3-ByExample/images/chap7-net-Ar.png
new file mode 100644
index 00000000000..2f4d80f47b6
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap7-net-Ar.png
diff --git a/docs-xml/Samba3-ByExample/images/chap7-net.svg b/docs-xml/Samba3-ByExample/images/chap7-net.svg
new file mode 100644
index 00000000000..a5ba6905407
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap7-net.svg
@@ -0,0 +1,9010 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="34.602001cm"
+   height="23.67cm"
+   viewBox="-11.55 -0.456 23.052 23.213"
+   id="svg2">
+  <defs
+     id="defs2739" />
+  <rect
+     width="13.8"
+     height="6.513"
+     x="1.375"
+     y="16.256001"
+     id="rect4"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
+     id="path6"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
+     id="path8"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="14.4"
+     height="5.9130001"
+     x="1.075"
+     y="16.556"
+     id="rect10"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
+     id="path12"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
+     id="path14"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="1.375"
+     y1="16.256001"
+     x2="15.175"
+     y2="16.256001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.375"
+     y1="22.768999"
+     x2="15.175"
+     y2="22.768999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.075"
+     y1="16.556"
+     x2="1.075"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="15.475"
+     y1="16.556"
+     x2="15.475"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.617"
+     height="6.8530002"
+     x="0.495"
+     y="-0.40599999"
+     id="rect32"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
+     id="path34"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
+     id="path36"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.217"
+     height="6.2529998"
+     x="0.19499999"
+     y="-0.106"
+     id="rect38"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
+     id="path40"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
+     id="path42"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="0.495"
+     y1="-0.40599999"
+     x2="11.112"
+     y2="-0.40599999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line44"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.495"
+     y1="6.447"
+     x2="11.112"
+     y2="6.447"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
+     id="path50"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.19499999"
+     y1="-0.106"
+     x2="0.19499999"
+     y2="6.1469998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.412"
+     y1="-0.106"
+     x2="11.412"
+     y2="6.1469998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line54"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
+     id="path56"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
+     id="path58"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.337"
+     height="6.8600001"
+     x="12.35"
+     y="-0.43099999"
+     id="rect60"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
+     id="path62"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
+     id="path64"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="10.937"
+     height="6.2600002"
+     x="12.05"
+     y="-0.131"
+     id="rect66"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
+     id="path68"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
+     id="path70"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="12.35"
+     y1="-0.43099999"
+     x2="22.687"
+     y2="-0.43099999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.35"
+     y1="6.4289999"
+     x2="22.687"
+     y2="6.4289999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.05"
+     y1="-0.131"
+     x2="12.05"
+     y2="6.1290002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="22.987"
+     y1="-0.131"
+     x2="22.987"
+     y2="6.1290002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
+     id="path84"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
+     id="path86"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.821"
+     height="8.375"
+     x="11.905"
+     y="7.244"
+     id="rect88"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
+     id="path90"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
+     id="path92"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.421"
+     height="7.7750001"
+     x="11.605"
+     y="7.5440001"
+     id="rect94"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
+     id="path96"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
+     id="path98"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="11.905"
+     y1="7.244"
+     x2="22.726999"
+     y2="7.244"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line100"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.905"
+     y1="15.619"
+     x2="22.726999"
+     y2="15.619"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line102"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
+     id="path104"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
+     id="path106"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.605"
+     y1="7.5440001"
+     x2="11.605"
+     y2="15.319"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line108"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="23.027"
+     y1="7.5440001"
+     x2="23.027"
+     y2="15.319"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line110"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
+     id="path112"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
+     id="path114"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="15.1"
+     height="8.3719997"
+     x="-11.225"
+     y="7.1339998"
+     id="rect116"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
+     id="path118"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 4.175,7.434 C 4.175,7.2683146 4.0406854,7.134 3.875,7.134"
+     id="path120"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="15.7"
+     height="7.7719998"
+     x="-11.525"
+     y="7.434"
+     id="rect122"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
+     id="path124"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 3.875,15.506 C 4.0406854,15.506 4.175,15.371685 4.175,15.206"
+     id="path126"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="-11.225"
+     y1="7.1339998"
+     x2="3.875"
+     y2="7.1339998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line128"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.225"
+     y1="15.506"
+     x2="3.875"
+     y2="15.506"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line130"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
+     id="path132"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 4.175,7.434 C 4.175,7.2683146 4.0406854,7.134 3.875,7.134"
+     id="path134"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.525"
+     y1="7.434"
+     x2="-11.525"
+     y2="15.206"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="4.1750002"
+     y1="7.434"
+     x2="4.1750002"
+     y2="15.206"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
+     id="path140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 3.875,15.506 C 4.0406854,15.506 4.175,15.371685 4.175,15.206"
+     id="path142"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.95"
+     y1="11.168"
+     x2="4.8109999"
+     y2="11.165"
+     stroke="#000000"
+     stroke-width="0.300"
+     id="line144"
+     style="stroke:#000000;stroke-width:0.30000001" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="4.145,2.624 4.145,6.819 5.675,6.819 5.675,9.944 "
+     id="polyline146"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="16.100,2.794 16.100,6.844 8.674,6.844 8.674,9.887 "
+     id="polyline148"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.98000002"
+     height="0.98000002"
+     x="-1.818"
+     y="14.136"
+     id="rect150"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.98000002"
+     height="0.98000002"
+     x="-1.818"
+     y="14.136"
+     id="rect152"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.98000002"
+     height="0.98000002"
+     x="-1.818"
+     y="14.136"
+     id="rect154"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
+     id="path156"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
+     id="path158"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
+     id="polygon160"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
+     id="polygon162"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
+     id="polygon164"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
+     id="polygon166"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
+     id="path168"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
+     id="path170"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
+     id="polygon172"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
+     id="polygon174"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
+     id="polygon176"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
+     id="polygon178"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-1.306"
+     y1="11.165"
+     x2="-1.3279999"
+     y2="14.136"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line180"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-9.1479998"
+     y="1.442"
+     id="text182"
+     style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="0.71700001"
+     y="7.6999998"
+     id="text184"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="0.37799999"
+     y="8.1999998"
+     id="text186"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-PDC</text>
+  <line
+     x1="6.118"
+     y1="13.16"
+     x2="7.7179999"
+     y2="13.135"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.10,0.10"
+     id="line188"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <text
+     x="8.4429998"
+     y="13.325"
+     id="text190"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">= VPN</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="10.645,11.075 10.645,9.069 16.025,9.069 16.025,11.368 "
+     id="polyline192"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-3.0239999"
+     y="14.751"
+     id="text194"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <text
+     x="4.1469998"
+     y="17.031"
+     id="text196"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect198"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect202"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect204"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect206"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect208"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="2.027"
+     x2="3.5869999"
+     y2="2.027"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line210"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.5869999"
+     y1="2.2709999"
+     x2="2.6140001"
+     y2="2.2709999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line212"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect214"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect216"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect218"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.553"
+     y1="3.122"
+     x2="3.77"
+     y2="3.122"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line220"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect222"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect224"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect226"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect228"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect230"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect232"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect234"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect236"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect238"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect240"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect242"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect244"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7360001"
+     y1="2.757"
+     x2="3.405"
+     y2="2.757"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line246"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect248"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect250"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect252"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect254"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect256"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect258"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.6359999"
+     x2="3.3440001"
+     y2="2.6359999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line260"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect262"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect264"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect266"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.405"
+     y1="2.4530001"
+     x2="3.527"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line268"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.1830001"
+     x2="3.7090001"
+     y2="3.1830001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line270"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.244"
+     x2="2.6140001"
+     y2="3.244"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line272"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.3050001"
+     x2="3.7090001"
+     y2="3.3050001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line274"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.487"
+     x2="2.6140001"
+     y2="3.487"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line276"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.427"
+     x2="3.7090001"
+     y2="3.427"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line278"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.3659999"
+     x2="2.6140001"
+     y2="3.3659999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line280"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.675"
+     y1="2.4530001"
+     x2="2.7360001"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line282"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.4530001"
+     x2="2.8570001"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line284"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.697"
+     x2="2.8570001"
+     y2="2.697"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line286"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.283"
+     y1="2.697"
+     x2="3.3440001"
+     y2="2.697"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line288"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.72"
+     y1="2.6359999"
+     x2="8.8620005"
+     y2="2.6229999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line290"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.2069998"
+     y1="2.632"
+     x2="5.2090001"
+     y2="3.5910001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line292"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.21"
+     y1="2.632"
+     x2="5.2080002"
+     y2="1.632"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line294"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.6500001"
+     y1="2.6289999"
+     x2="6.652"
+     y2="3.5339999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line296"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.651"
+     y1="2.6289999"
+     x2="6.6479998"
+     y2="1.6289999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line298"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.092"
+     y1="2.625"
+     x2="8.0950003"
+     y2="3.552"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line300"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.0909996"
+     y1="2.625"
+     x2="8.0889997"
+     y2="1.625"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line302"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.1989999"
+     y="3.559"
+     id="rect304"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.1989999"
+     y="3.559"
+     id="rect306"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.296"
+     y="3.6559999"
+     id="rect308"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
+     id="polygon310"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
+     id="polygon312"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
+     id="polygon314"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
+     id="polygon316"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8130002"
+     y="4.2620001"
+     id="rect318"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8130002"
+     y="4.2620001"
+     id="rect320"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
+     id="polygon322"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
+     id="polygon324"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6420002"
+     y="3.5480001"
+     id="rect326"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6420002"
+     y="3.5480001"
+     id="rect328"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.7389998"
+     y="3.645"
+     id="rect330"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
+     id="polygon332"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
+     id="polygon334"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
+     id="polygon336"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
+     id="polygon338"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2550001"
+     y="4.2509999"
+     id="rect340"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2550001"
+     y="4.2509999"
+     id="rect342"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
+     id="polygon344"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
+     id="polygon346"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="4.7670002"
+     y="1.123"
+     id="rect348"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="4.7670002"
+     y="1.123"
+     id="rect350"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="4.8639998"
+     y="1.22"
+     id="rect352"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
+     id="polygon354"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
+     id="polygon356"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
+     id="polygon358"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
+     id="polygon360"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="5.3800001"
+     y="1.826"
+     id="rect362"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="5.3800001"
+     y="1.826"
+     id="rect364"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
+     id="polygon366"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
+     id="polygon368"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.217"
+     y="1.148"
+     id="rect370"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.217"
+     y="1.148"
+     id="rect372"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.3140001"
+     y="1.245"
+     id="rect374"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
+     id="polygon376"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
+     id="polygon378"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
+     id="polygon380"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
+     id="polygon382"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8299999"
+     y="1.851"
+     id="rect384"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8299999"
+     y="1.851"
+     id="rect386"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
+     id="polygon388"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
+     id="polygon390"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6669998"
+     y="1.123"
+     id="rect392"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6669998"
+     y="1.123"
+     id="rect394"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.7639999"
+     y="1.22"
+     id="rect396"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
+     id="polygon398"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
+     id="polygon400"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
+     id="polygon402"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
+     id="polygon404"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2799997"
+     y="1.826"
+     id="rect406"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2799997"
+     y="1.826"
+     id="rect408"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
+     id="polygon410"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
+     id="polygon412"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
+     id="polygon414"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
+     id="polygon416"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.611,4.115 L 4.659,4.135 L 5.715,4.135 L 5.763,4.115"
+     id="path418"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.715,4.135 L 5.787,4.175"
+     id="path420"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.587,4.175 L 4.659,4.135"
+     id="path422"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
+     id="polygon424"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
+     id="polygon426"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
+     id="polygon428"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
+     id="polygon430"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse432"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse434"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse436"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse438"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse440"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse442"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse444"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse446"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse448"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse450"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse452"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse454"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse456"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse458"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse460"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse462"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse464"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse466"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse468"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse470"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse472"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse474"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse476"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse478"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.1869998"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse480"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="5.1869998"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse482"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.487"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse484"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="5.487"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse486"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect488"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect490"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect492"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect494"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect496"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect498"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.009"
+     y1="1.829"
+     x2="9.0939999"
+     y2="1.829"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line500"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0939999"
+     y1="2.0580001"
+     x2="10.009"
+     y2="2.0580001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line502"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.009"
+     y1="2.2290001"
+     x2="9.0939999"
+     y2="2.2290001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line504"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect506"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect508"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect510"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.9790001"
+     y1="3.03"
+     x2="10.123"
+     y2="3.03"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line512"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect514"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect516"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect518"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect520"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect522"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect524"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect526"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect528"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect530"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect532"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect534"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect536"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0939999"
+     y1="2.8010001"
+     x2="9.7229996"
+     y2="2.8010001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line538"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect540"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect542"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect544"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect546"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect548"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect550"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.687"
+     x2="9.6660004"
+     y2="2.687"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line552"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.6660004"
+     y1="2.744"
+     x2="9.6090002"
+     y2="2.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line554"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.744"
+     x2="9.2080002"
+     y2="2.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line556"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect558"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect560"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect562"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.401"
+     x2="9.2080002"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line564"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.2650003"
+     y1="2.401"
+     x2="9.323"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line566"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.8369999"
+     y1="2.401"
+     x2="9.9519997"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line568"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.7160001"
+     x2="9.0369997"
+     y2="3.7160001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line570"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.6589999"
+     x2="10.066"
+     y2="3.6589999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line572"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.602"
+     x2="9.0369997"
+     y2="3.602"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line574"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.5439999"
+     x2="10.066"
+     y2="3.5439999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line576"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.487"
+     x2="9.0369997"
+     y2="3.487"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line578"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.4300001"
+     x2="10.066"
+     y2="3.4300001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line580"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.3729999"
+     x2="9.0369997"
+     y2="3.3729999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line582"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="5.9629998"
+     y="5.2589998"
+     id="text584"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="5.5580001"
+     y="5.8590002"
+     id="text586"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.12.0/22</text>
+  <text
+     x="1.459"
+     y="4.1030002"
+     id="text588"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="1.239"
+     y="4.6030002"
+     id="text590"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVA-BDC</text>
+  <text
+     x="8.3649998"
+     y="0.375"
+     id="text592"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="8.658"
+     y="0.875"
+     id="text594"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVA-APPS</text>
+  <rect
+     width="1.291"
+     height="1.1390001"
+     x="0.61699998"
+     y="2.0880001"
+     id="rect596"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="1.263"
+     cy="3.227"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse598"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.263"
+     cy="2.0880001"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse600"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.263"
+     cy="2.0880001"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse602"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 1.908,2.088 L 1.908,3.227 C 1.908,3.332 1.619,3.417 1.263,3.417 C 0.906,3.417 0.617,3.332 0.617,3.227 L 0.617,2.088"
+     id="path604"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="1.928"
+     y1="2.523"
+     x2="2.503"
+     y2="2.523"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line606"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.935"
+     y="2.7219999"
+     id="text608"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="0.94999999"
+     y="3.122"
+     id="text610"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect612"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect614"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect616"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect618"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect620"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect622"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="2.1900001"
+     x2="15.431"
+     y2="2.1900001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line624"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="2.4330001"
+     x2="14.458"
+     y2="2.4330001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line626"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect628"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect630"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect632"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.397"
+     y1="3.2850001"
+     x2="15.614"
+     y2="3.2850001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line634"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect636"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect638"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect640"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect642"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect644"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect646"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect648"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect650"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect652"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect654"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect656"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect658"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.58"
+     y1="2.9200001"
+     x2="15.249"
+     y2="2.9200001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line660"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect662"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect664"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect666"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect668"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect670"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect672"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.7980001"
+     x2="15.188"
+     y2="2.7980001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line674"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect676"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect678"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect680"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.249"
+     y1="2.615"
+     x2="15.371"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line682"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.345"
+     x2="15.553"
+     y2="3.345"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line684"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.4059999"
+     x2="14.458"
+     y2="3.4059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line686"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.467"
+     x2="15.553"
+     y2="3.467"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line688"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.6500001"
+     x2="14.458"
+     y2="3.6500001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line690"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.589"
+     x2="15.553"
+     y2="3.589"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.5280001"
+     x2="14.458"
+     y2="3.5280001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="2.615"
+     x2="14.58"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.615"
+     x2="14.701"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line698"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.859"
+     x2="14.701"
+     y2="2.859"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line700"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.127"
+     y1="2.859"
+     x2="15.188"
+     y2="2.859"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line702"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.564"
+     y1="2.7980001"
+     x2="20.705"
+     y2="2.7850001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line704"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.051001"
+     y1="2.7939999"
+     x2="17.052999"
+     y2="3.753"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line706"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.054001"
+     y1="2.7939999"
+     x2="17.052"
+     y2="1.794"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line708"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.493"
+     y1="2.7909999"
+     x2="18.496"
+     y2="3.6960001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line710"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.495001"
+     y1="2.7909999"
+     x2="18.492001"
+     y2="1.791"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line712"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.936001"
+     y1="2.7869999"
+     x2="19.938999"
+     y2="3.714"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line714"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.934999"
+     y1="2.7869999"
+     x2="19.933001"
+     y2="1.7869999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line716"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.042999"
+     y="3.721"
+     id="rect718"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.042999"
+     y="3.721"
+     id="rect720"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.139999"
+     y="3.8180001"
+     id="rect722"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
+     id="polygon724"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
+     id="polygon726"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
+     id="polygon728"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
+     id="polygon730"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.657"
+     y="4.4239998"
+     id="rect732"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.657"
+     y="4.4239998"
+     id="rect734"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
+     id="polygon736"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
+     id="polygon738"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.486"
+     y="3.71"
+     id="rect740"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.486"
+     y="3.71"
+     id="rect742"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.583"
+     y="3.8069999"
+     id="rect744"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
+     id="polygon746"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
+     id="polygon748"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
+     id="polygon750"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
+     id="polygon752"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.099001"
+     y="4.414"
+     id="rect754"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.099001"
+     y="4.414"
+     id="rect756"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
+     id="polygon758"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
+     id="polygon760"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.611"
+     y="1.285"
+     id="rect762"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.611"
+     y="1.285"
+     id="rect764"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="16.708"
+     y="1.382"
+     id="rect766"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
+     id="polygon768"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
+     id="polygon770"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
+     id="polygon772"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
+     id="polygon774"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.224001"
+     y="1.989"
+     id="rect776"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.224001"
+     y="1.989"
+     id="rect778"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
+     id="polygon780"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
+     id="polygon782"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.061001"
+     y="1.3099999"
+     id="rect784"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.061001"
+     y="1.3099999"
+     id="rect786"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.158001"
+     y="1.4069999"
+     id="rect788"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
+     id="polygon790"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
+     id="polygon792"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
+     id="polygon794"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
+     id="polygon796"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.674"
+     y="2.0139999"
+     id="rect798"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.674"
+     y="2.0139999"
+     id="rect800"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
+     id="polygon802"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
+     id="polygon804"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.511"
+     y="1.285"
+     id="rect806"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.511"
+     y="1.285"
+     id="rect808"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.608"
+     y="1.382"
+     id="rect810"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
+     id="polygon812"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
+     id="polygon814"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
+     id="polygon816"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
+     id="polygon818"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.124001"
+     y="1.989"
+     id="rect820"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.124001"
+     y="1.989"
+     id="rect822"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
+     id="polygon824"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
+     id="polygon826"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
+     id="polygon828"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
+     id="polygon830"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.454,4.277 L 16.502,4.297 L 17.558,4.297 L 17.606,4.277"
+     id="path832"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 17.558,4.297 L 17.63,4.337"
+     id="path834"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.43,4.337 L 16.502,4.297"
+     id="path836"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
+     id="polygon838"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
+     id="polygon840"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
+     id="polygon842"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
+     id="polygon844"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="16.67"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse846"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse848"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse850"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse852"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse854"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse856"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse858"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse860"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse862"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse864"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse866"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse868"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse870"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse872"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse874"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse876"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse878"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse880"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse882"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse884"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse886"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse888"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse890"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse892"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.030001"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse894"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.030001"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse896"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.33"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse898"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.33"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse900"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect902"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect904"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect906"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect908"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect910"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect912"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.853001"
+     y1="1.9910001"
+     x2="20.938"
+     y2="1.9910001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line914"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.938"
+     y1="2.22"
+     x2="21.853001"
+     y2="2.22"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line916"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.853001"
+     y1="2.391"
+     x2="20.938"
+     y2="2.391"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line918"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect920"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect922"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect924"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.823"
+     y1="3.1919999"
+     x2="21.966999"
+     y2="3.1919999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line926"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect928"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect930"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect932"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect934"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect936"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect938"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect940"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect942"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect944"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect946"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect948"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect950"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.938"
+     y1="2.9630001"
+     x2="21.566999"
+     y2="2.9630001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line952"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect954"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect956"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect958"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect960"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect962"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect964"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.849"
+     x2="21.51"
+     y2="2.849"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line966"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.51"
+     y1="2.9059999"
+     x2="21.452"
+     y2="2.9059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line968"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.9059999"
+     x2="21.052"
+     y2="2.9059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line970"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect972"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect974"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect976"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.563"
+     x2="21.052"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line978"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.108999"
+     y1="2.563"
+     x2="21.167"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line980"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.681"
+     y1="2.563"
+     x2="21.796"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line982"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.878"
+     x2="20.881001"
+     y2="3.878"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line984"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.8210001"
+     x2="21.91"
+     y2="3.8210001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line986"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.7639999"
+     x2="20.881001"
+     y2="3.7639999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line988"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.707"
+     x2="21.91"
+     y2="3.707"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line990"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.6489999"
+     x2="20.881001"
+     y2="3.6489999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line992"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.592"
+     x2="21.91"
+     y2="3.592"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line994"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.5350001"
+     x2="20.881001"
+     y2="3.5350001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line996"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="18.056999"
+     y="5.3460002"
+     id="text998"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="17.650999"
+     y="5.9460001"
+     id="text1000"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.16.0/22</text>
+  <text
+     x="13.478"
+     y="4.3400002"
+     id="text1002"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="13.248"
+     y="4.8400002"
+     id="text1004"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVB-BDC</text>
+  <text
+     x="19.816999"
+     y="0.35600001"
+     id="text1006"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="20.101"
+     y="0.85600001"
+     id="text1008"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVB-APPS</text>
+  <rect
+     width="1.326"
+     height="1.17"
+     x="12.501"
+     y="2.28"
+     id="rect1010"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="13.164"
+     cy="3.451"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1012"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.164"
+     cy="2.28"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1014"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.164"
+     cy="2.28"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1016"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 13.827,2.28 L 13.827,3.451 C 13.827,3.559 13.53,3.646 13.164,3.646 C 12.798,3.646 12.501,3.559 12.501,3.451 L 12.501,2.28"
+     id="path1018"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.822"
+     y1="2.8599999"
+     x2="14.397"
+     y2="2.7980001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1020"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.809"
+     y="2.9619999"
+     id="text1022"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="12.823"
+     y="3.362"
+     id="text1024"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1026"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1028"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1030"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1032"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1034"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1036"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="10.744"
+     x2="15.309"
+     y2="10.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1038"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.309"
+     y1="10.988"
+     x2="14.336"
+     y2="10.988"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1040"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1042"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1044"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1046"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.275"
+     y1="11.839"
+     x2="15.492"
+     y2="11.839"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1048"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1050"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1052"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1054"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1056"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1058"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1060"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1062"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1064"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1066"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1068"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1070"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1072"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="11.474"
+     x2="15.127"
+     y2="11.474"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1074"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1076"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1078"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1080"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1082"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1084"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1086"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.353"
+     x2="15.066"
+     y2="11.353"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1088"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1090"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1092"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1094"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.127"
+     y1="11.17"
+     x2="15.249"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1096"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="11.9"
+     x2="15.431"
+     y2="11.9"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1098"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="11.961"
+     x2="14.336"
+     y2="11.961"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1100"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="12.022"
+     x2="15.431"
+     y2="12.022"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1102"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="12.204"
+     x2="14.336"
+     y2="12.204"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1104"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="12.143"
+     x2="15.431"
+     y2="12.143"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1106"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="12.083"
+     x2="14.336"
+     y2="12.083"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1108"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.397"
+     y1="11.17"
+     x2="14.458"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1110"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.17"
+     x2="14.579"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1112"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.413"
+     x2="14.579"
+     y2="11.413"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1114"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.005"
+     y1="11.413"
+     x2="15.066"
+     y2="11.413"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1116"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.442"
+     y1="11.353"
+     x2="20.584"
+     y2="11.34"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1118"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.929001"
+     y1="11.349"
+     x2="16.931"
+     y2="12.308"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1120"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.931999"
+     y1="11.349"
+     x2="16.93"
+     y2="10.349"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1122"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.372"
+     y1="11.345"
+     x2="18.374001"
+     y2="12.251"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1124"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.372999"
+     y1="11.345"
+     x2="18.370001"
+     y2="10.345"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1126"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.815001"
+     y1="11.342"
+     x2="19.816999"
+     y2="12.269"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1128"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.813"
+     y1="11.342"
+     x2="19.811001"
+     y2="10.342"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1130"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.921"
+     y="12.276"
+     id="rect1132"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.921"
+     y="12.276"
+     id="rect1134"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.018"
+     y="12.373"
+     id="rect1136"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
+     id="polygon1138"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
+     id="polygon1140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
+     id="polygon1142"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
+     id="polygon1144"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.535"
+     y="12.979"
+     id="rect1146"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.535"
+     y="12.979"
+     id="rect1148"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
+     id="polygon1150"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
+     id="polygon1152"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.364"
+     y="12.265"
+     id="rect1154"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.364"
+     y="12.265"
+     id="rect1156"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.461"
+     y="12.362"
+     id="rect1158"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
+     id="polygon1160"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
+     id="polygon1162"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
+     id="polygon1164"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
+     id="polygon1166"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="19.976999"
+     y="12.968"
+     id="rect1168"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="19.976999"
+     y="12.968"
+     id="rect1170"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
+     id="polygon1172"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
+     id="polygon1174"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.489"
+     y="9.8400002"
+     id="rect1176"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.489"
+     y="9.8400002"
+     id="rect1178"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="16.586"
+     y="9.9370003"
+     id="rect1180"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
+     id="polygon1182"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
+     id="polygon1184"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
+     id="polygon1186"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
+     id="polygon1188"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.101999"
+     y="10.543"
+     id="rect1190"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.101999"
+     y="10.543"
+     id="rect1192"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
+     id="polygon1194"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
+     id="polygon1196"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.938999"
+     y="9.8649998"
+     id="rect1198"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.938999"
+     y="9.8649998"
+     id="rect1200"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.035999"
+     y="9.9619999"
+     id="rect1202"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
+     id="polygon1204"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
+     id="polygon1206"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
+     id="polygon1208"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
+     id="polygon1210"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.552"
+     y="10.568"
+     id="rect1212"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.552"
+     y="10.568"
+     id="rect1214"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
+     id="polygon1216"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
+     id="polygon1218"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.389"
+     y="9.8400002"
+     id="rect1220"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.389"
+     y="9.8400002"
+     id="rect1222"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.486"
+     y="9.9370003"
+     id="rect1224"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
+     id="polygon1226"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
+     id="polygon1228"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
+     id="polygon1230"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
+     id="polygon1232"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.002001"
+     y="10.543"
+     id="rect1234"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.002001"
+     y="10.543"
+     id="rect1236"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
+     id="polygon1238"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
+     id="polygon1240"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
+     id="polygon1242"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
+     id="polygon1244"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.333,12.832 L 16.381,12.852 L 17.437,12.852 L 17.485,12.832"
+     id="path1246"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 17.437,12.852 L 17.509,12.892"
+     id="path1248"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.309,12.892 L 16.381,12.852"
+     id="path1250"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
+     id="polygon1252"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
+     id="polygon1254"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
+     id="polygon1256"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
+     id="polygon1258"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="16.549"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1260"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1262"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1264"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1266"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1268"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1270"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1272"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1274"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1276"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1278"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1280"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1282"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1284"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1286"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1288"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1290"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1292"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1294"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1296"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1298"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1300"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1302"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1304"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1306"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.909"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1308"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="16.909"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1310"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.209"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1312"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.209"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1314"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1316"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1318"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1320"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1322"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1324"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1326"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.731001"
+     y1="10.546"
+     x2="20.816"
+     y2="10.546"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1328"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.816"
+     y1="10.774"
+     x2="21.731001"
+     y2="10.774"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1330"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.731001"
+     y1="10.946"
+     x2="20.816"
+     y2="10.946"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1332"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1334"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1336"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1338"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.701"
+     y1="11.747"
+     x2="21.844999"
+     y2="11.747"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1340"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1342"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1344"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1346"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1348"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1350"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1352"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1354"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1356"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1358"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1360"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1362"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1364"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.816"
+     y1="11.518"
+     x2="21.445"
+     y2="11.518"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1366"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1368"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1370"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1372"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1374"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1376"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1378"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.404"
+     x2="21.388"
+     y2="11.404"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1380"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.388"
+     y1="11.461"
+     x2="21.330999"
+     y2="11.461"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1382"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.461"
+     x2="20.93"
+     y2="11.461"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1384"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1386"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1388"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1390"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.118"
+     x2="20.93"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1392"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.987"
+     y1="11.118"
+     x2="21.045"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1394"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.559"
+     y1="11.118"
+     x2="21.674"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1396"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.433"
+     x2="20.759001"
+     y2="12.433"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1398"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.376"
+     x2="21.788"
+     y2="12.376"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1400"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.319"
+     x2="20.759001"
+     y2="12.319"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1402"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.261"
+     x2="21.788"
+     y2="12.261"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1404"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.204"
+     x2="20.759001"
+     y2="12.204"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1406"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.147"
+     x2="21.788"
+     y2="12.147"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1408"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.09"
+     x2="20.759001"
+     y2="12.09"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1410"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="18.610001"
+     y="9.026"
+     id="text1412"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="18.176001"
+     y="9.6260004"
+     id="text1414"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.20.0/22</text>
+  <text
+     x="13.881"
+     y="12.895"
+     id="text1416"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="13.65"
+     y="13.395"
+     id="text1418"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVC-BDC</text>
+  <text
+     x="19.937"
+     y="14.042"
+     id="text1420"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="20.219"
+     y="14.542"
+     id="text1422"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVC-APPS</text>
+  <rect
+     width="1.3150001"
+     height="1.161"
+     x="12.175"
+     y="9.5089998"
+     id="rect1424"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="12.833"
+     cy="10.669"
+     rx="0.65799999"
+     ry="0.193"
+     id="ellipse1426"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.833"
+     cy="9.5089998"
+     rx="0.65799999"
+     ry="0.193"
+     id="ellipse1428"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.833"
+     cy="9.5089998"
+     rx="0.65799999"
+     ry="0.193"
+     id="ellipse1430"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 13.491,9.509 L 13.491,10.669 C 13.491,10.776 13.196,10.863 12.833,10.863 C 12.47,10.863 12.175,10.776 12.175,10.669 L 12.175,9.509"
+     id="path1432"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="14.219"
+     y1="11.042"
+     x2="13.469"
+     y2="10.167"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1434"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.537"
+     y="10.142"
+     id="text1436"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="12.552"
+     y="10.542"
+     id="text1438"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <path
+     d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
+     id="path1440"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
+     id="path1442"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.7909999"
+     y="11.036"
+     id="text1444"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
+  <path
+     d="M 4.7,11.1 C 5.035363,11.196174 5.3953356,11.076093 5.6057965,10.797841 C 5.8162574,10.51959 5.8338243,10.140524 5.65,9.844"
+     id="path1446"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <path
+     d="M 8.675,9.794 C 7.4940305,10.104758 6.3530779,10.551408 5.275,11.125"
+     id="path1448"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <path
+     d="M 4.7,11.15 C 6.6098972,11.931939 8.7554368,11.904871 10.645,11.075"
+     id="path1450"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1452"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1454"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1456"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1458"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1460"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1462"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.1389999"
+     x2="1.8710001"
+     y2="9.1389999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1464"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.8710001"
+     y1="9.4180002"
+     x2="0.75400001"
+     y2="9.4180002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1466"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.698"
+     x2="1.8710001"
+     y2="9.698"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1468"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.9770002"
+     x2="1.8710001"
+     y2="9.9770002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1470"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.8710001"
+     y1="10.256"
+     x2="0.75400001"
+     y2="10.256"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1472"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1474"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1476"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1478"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.61400002"
+     y1="11.374"
+     x2="2.0109999"
+     y2="11.374"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1480"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1482"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1484"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1486"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1488"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1490"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1492"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1494"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1496"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1498"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1500"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1502"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1504"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="10.885"
+     x2="1.522"
+     y2="10.885"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1506"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1508"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1510"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1512"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1514"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1516"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1518"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.745"
+     x2="1.452"
+     y2="10.745"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1520"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.452"
+     y1="10.815"
+     x2="1.382"
+     y2="10.815"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1522"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.815"
+     x2="0.89300001"
+     y2="10.815"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1524"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1526"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1528"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1530"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.466"
+     x2="0.89300001"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1532"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.963"
+     y1="10.466"
+     x2="1.033"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1534"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.6619999"
+     y1="10.466"
+     x2="1.801"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1536"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.84"
+     x2="1.941"
+     y2="12.84"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1538"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.77"
+     x2="0.68400002"
+     y2="12.77"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1540"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.701"
+     x2="1.941"
+     y2="12.701"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1542"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.631"
+     x2="0.68400002"
+     y2="12.631"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1544"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.561"
+     x2="1.941"
+     y2="12.561"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1546"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.491"
+     x2="0.68400002"
+     y2="12.491"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1548"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.421"
+     x2="1.941"
+     y2="12.421"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1550"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.351"
+     x2="0.68400002"
+     y2="12.351"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1552"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.282"
+     x2="1.941"
+     y2="12.282"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1554"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.212"
+     x2="0.68400002"
+     y2="12.212"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1556"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.142"
+     x2="1.941"
+     y2="12.142"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1558"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.072"
+     x2="0.68400002"
+     y2="12.072"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1560"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.002"
+     x2="1.941"
+     y2="12.002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1562"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="11.932"
+     x2="0.68400002"
+     y2="11.932"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1564"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.559"
+     y="12.296"
+     id="rect1566"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.559"
+     y="12.296"
+     id="rect1568"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-6.454"
+     y="12.401"
+     id="rect1570"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.427,13.024 -5.928,13.024 -5.928,13.137 -6.401,13.137 -6.427,13.024 "
+     id="polygon1572"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.427,13.024 -5.928,13.024 -5.928,13.137 -6.401,13.137 -6.427,13.024 "
+     id="polygon1574"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.928,13.024 -5.719,13.024 -5.746,13.137 -5.928,13.137 -5.928,13.024 "
+     id="polygon1576"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.928,13.024 -5.719,13.024 -5.746,13.137 -5.928,13.137 -5.928,13.024 "
+     id="polygon1578"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.8940001"
+     y="13.058"
+     id="rect1580"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.8940001"
+     y="13.058"
+     id="rect1582"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.17,13.137 -5.976,13.137 -5.976,13.194 -5.879,13.194 -5.879,13.25 -6.267,13.25 -6.267,13.194 -6.17,13.194 -6.17,13.137 "
+     id="polygon1584"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.17,13.137 -5.976,13.137 -5.976,13.194 -5.879,13.194 -5.879,13.25 -6.267,13.25 -6.267,13.194 -6.17,13.194 -6.17,13.137 "
+     id="polygon1586"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.653"
+     y1="11.13"
+     x2="-9.6660004"
+     y2="11.13"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1588"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-1.289"
+     y1="11.13"
+     x2="-1.289"
+     y2="10.145"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1590"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-3.766"
+     y1="11.13"
+     x2="-3.766"
+     y2="12.295"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1592"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-3.7739999"
+     y1="11.13"
+     x2="-3.7739999"
+     y2="10.099"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1594"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-6.0799999"
+     y1="11.13"
+     x2="-6.0799999"
+     y2="12.367"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1596"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-6.0939999"
+     y1="11.13"
+     x2="-6.0939999"
+     y2="10.063"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1598"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-8.4139996"
+     y1="11.13"
+     x2="-8.4139996"
+     y2="9.5740004"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1600"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.069"
+     height="0.80199999"
+     x="-4.289"
+     y="12.216"
+     id="rect1602"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.069"
+     height="0.80199999"
+     x="-4.289"
+     y="12.216"
+     id="rect1604"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.83700001"
+     height="0.55199999"
+     x="-4.1729999"
+     y="12.332"
+     id="rect1606"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.144,13.018 -3.594,13.018 -3.594,13.143 -4.115,13.143 -4.144,13.018 "
+     id="polygon1608"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.144,13.018 -3.594,13.018 -3.594,13.143 -4.115,13.143 -4.144,13.018 "
+     id="polygon1610"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-3.594,13.018 -3.365,13.018 -3.394,13.143 -3.594,13.143 -3.594,13.018 "
+     id="polygon1612"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.594,13.018 -3.365,13.018 -3.394,13.143 -3.594,13.143 -3.594,13.018 "
+     id="polygon1614"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050000001"
+     height="0.050000001"
+     x="-3.5569999"
+     y="13.055"
+     id="rect1616"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050000001"
+     height="0.050000001"
+     x="-3.5569999"
+     y="13.055"
+     id="rect1618"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.861,13.143 -3.648,13.143 -3.648,13.205 -3.541,13.205 -3.541,13.267 -3.968,13.267 -3.968,13.205 -3.861,13.205 -3.861,13.143 "
+     id="polygon1620"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.861,13.143 -3.648,13.143 -3.648,13.205 -3.541,13.205 -3.541,13.267 -3.968,13.267 -3.968,13.205 -3.861,13.205 -3.861,13.143 "
+     id="polygon1622"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.579"
+     y="9.1079998"
+     id="rect1624"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.579"
+     y="9.1079998"
+     id="rect1626"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-6.474"
+     y="9.2139997"
+     id="rect1628"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
+     id="polygon1630"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
+     id="polygon1632"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
+     id="polygon1634"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
+     id="polygon1636"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.914"
+     y="9.8710003"
+     id="rect1638"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.914"
+     y="9.8710003"
+     id="rect1640"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
+     id="polygon1642"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
+     id="polygon1644"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-4.2600002"
+     y="9.1450005"
+     id="rect1646"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-4.2600002"
+     y="9.1450005"
+     id="rect1648"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-4.1550002"
+     y="9.25"
+     id="rect1650"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
+     id="polygon1652"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
+     id="polygon1654"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
+     id="polygon1656"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
+     id="polygon1658"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-3.595"
+     y="9.9069996"
+     id="rect1660"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-3.595"
+     y="9.9069996"
+     id="rect1662"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
+     id="polygon1664"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
+     id="polygon1666"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-8.9029999"
+     y="9.0410004"
+     id="rect1668"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-8.9029999"
+     y="9.0410004"
+     id="rect1670"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-8.7980003"
+     y="9.1470003"
+     id="rect1672"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
+     id="polygon1674"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
+     id="polygon1676"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
+     id="polygon1678"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
+     id="polygon1680"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-8.2379999"
+     y="9.8039999"
+     id="rect1682"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-8.2379999"
+     y="9.8039999"
+     id="rect1684"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
+     id="polygon1686"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
+     id="polygon1688"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
+     id="polygon1690"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
+     id="polygon1692"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -1.871,9.841 L -1.823,9.861 L -0.754,9.861 L -0.706,9.841"
+     id="path1694"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -0.754,9.861 L -0.682,9.902"
+     id="path1696"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -1.895,9.902 L -1.823,9.861"
+     id="path1698"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
+     id="polygon1700"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
+     id="polygon1702"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
+     id="polygon1704"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
+     id="polygon1706"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1708"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1710"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1712"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1714"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1716"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1718"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1720"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1722"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1724"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1726"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1728"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1730"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.653"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1732"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1734"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1736"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1738"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1740"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1742"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.653"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1744"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1746"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1748"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1750"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1752"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1754"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.289"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1756"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-1.289"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1758"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-0.98500001"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1760"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-0.98500001"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1762"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.312"
+     height="2.625"
+     x="-11.059"
+     y="9.7469997"
+     id="rect1764"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.312"
+     height="2.625"
+     x="-11.059"
+     y="9.7469997"
+     id="rect1766"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.312"
+     height="2.625"
+     x="-11.059"
+     y="9.7469997"
+     id="rect1768"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.05"
+     height="1.05"
+     x="-10.928"
+     y="9.8780003"
+     id="rect1770"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.05"
+     height="1.05"
+     x="-10.928"
+     y="9.8780003"
+     id="rect1772"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.05"
+     height="1.05"
+     x="-10.928"
+     y="9.8780003"
+     id="rect1774"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8780003"
+     y1="10.141"
+     x2="-10.928"
+     y2="10.141"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1776"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.928"
+     y1="10.403"
+     x2="-9.8780003"
+     y2="10.403"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1778"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8780003"
+     y1="10.6"
+     x2="-10.928"
+     y2="10.6"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1780"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.722"
+     height="0.39399999"
+     x="-10.928"
+     y="11.06"
+     id="rect1782"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.722"
+     height="0.39399999"
+     x="-10.928"
+     y="11.06"
+     id="rect1784"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.722"
+     height="0.39399999"
+     x="-10.928"
+     y="11.06"
+     id="rect1786"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-11.059"
+     y1="11.519"
+     x2="-9.7460003"
+     y2="11.519"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1788"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.468"
+     y="11.65"
+     id="rect1790"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.468"
+     y="11.65"
+     id="rect1792"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.468"
+     y="11.65"
+     id="rect1794"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.206"
+     y="11.65"
+     id="rect1796"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.206"
+     y="11.65"
+     id="rect1798"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.206"
+     y="11.65"
+     id="rect1800"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-9.9429998"
+     y="11.65"
+     id="rect1802"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-9.9429998"
+     y="11.65"
+     id="rect1804"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-9.9429998"
+     y="11.65"
+     id="rect1806"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.131"
+     height="0.066"
+     x="-10.009"
+     y="11.256"
+     id="rect1808"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.131"
+     height="0.066"
+     x="-10.009"
+     y="11.256"
+     id="rect1810"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.131"
+     height="0.066"
+     x="-10.009"
+     y="11.256"
+     id="rect1812"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.928"
+     y1="11.256"
+     x2="-10.206"
+     y2="11.256"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1814"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.197"
+     height="0.197"
+     x="-10.928"
+     y="11.585"
+     id="rect1816"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.197"
+     height="0.197"
+     x="-10.928"
+     y="11.585"
+     id="rect1818"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.197"
+     height="0.197"
+     x="-10.928"
+     y="11.585"
+     id="rect1820"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91900003"
+     height="0.066"
+     x="-10.862"
+     y="10.666"
+     id="rect1822"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91900003"
+     height="0.066"
+     x="-10.862"
+     y="10.666"
+     id="rect1824"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91900003"
+     height="0.066"
+     x="-10.862"
+     y="10.666"
+     id="rect1826"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.862"
+     y1="11.125"
+     x2="-10.271"
+     y2="11.125"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1828"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.271"
+     y1="11.191"
+     x2="-10.337"
+     y2="11.191"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1830"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.862"
+     y1="11.191"
+     x2="-10.796"
+     y2="11.191"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1832"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.32800001"
+     height="0.066"
+     x="-10.731"
+     y="11.125"
+     id="rect1834"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.32800001"
+     height="0.066"
+     x="-10.731"
+     y="11.125"
+     id="rect1836"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.32800001"
+     height="0.066"
+     x="-10.731"
+     y="11.125"
+     id="rect1838"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.862"
+     y1="10.797"
+     x2="-10.796"
+     y2="10.797"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1840"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.731"
+     y1="10.797"
+     x2="-10.665"
+     y2="10.797"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1842"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.074"
+     y1="10.797"
+     x2="-9.9429998"
+     y2="10.797"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1844"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="12.306"
+     x2="-10.993"
+     y2="12.306"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1846"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.993"
+     y1="12.241"
+     x2="-9.8120003"
+     y2="12.241"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1848"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="12.175"
+     x2="-10.993"
+     y2="12.175"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1850"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.993"
+     y1="12.11"
+     x2="-9.8120003"
+     y2="12.11"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1852"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="12.044"
+     x2="-10.993"
+     y2="12.044"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1854"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.993"
+     y1="11.978"
+     x2="-9.8120003"
+     y2="11.978"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1856"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="11.913"
+     x2="-10.993"
+     y2="11.913"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1858"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="-6.5710001"
+     y="8.3360004"
+     id="text1860"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="-6.9060001"
+     y="8.9359999"
+     id="text1862"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.0.0/22</text>
+  <text
+     x="-10.628"
+     y="13.181"
+     id="text1864"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="-10.454"
+     y="13.681"
+     id="text1866"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-APPS</text>
+  <rect
+     width="1.4450001"
+     height="1.275"
+     x="2.5510001"
+     y="8.6120005"
+     id="rect1868"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="3.273"
+     cy="9.8870001"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1870"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.273"
+     cy="8.6120005"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1872"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.273"
+     cy="8.6120005"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1874"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.996,8.612 L 3.996,9.887 C 3.996,10.005 3.672,10.1 3.273,10.1 C 2.874,10.1 2.551,10.005 2.551,9.887 L 2.551,8.612"
+     id="path1876"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="2.0109999"
+     y1="9.2469997"
+     x2="2.586"
+     y2="9.2469997"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1878"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.983"
+     y="9.3260002"
+     id="text1880"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="2.928"
+     y="9.7259998"
+     id="text1882"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="5.725,19.819 5.725,18.237 5.732,18.237 5.732,17.325 "
+     id="polyline1884"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="1.317"
+     y="15.131"
+     id="text1886"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">1100 Users</text>
+  <text
+     x="1.136"
+     y="6.0770001"
+     id="text1888"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">320 Users</text>
+  <text
+     x="12.943"
+     y="6.0310001"
+     id="text1890"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">180 Users</text>
+  <text
+     x="12.358"
+     y="15.177"
+     id="text1892"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
+  <text
+     x="-9.9619999"
+     y="15.156"
+     id="text1894"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York - Bldg1</text>
+  <text
+     x="13.214"
+     y="0.46399999"
+     id="text1896"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Los Angeles</text>
+  <text
+     x="1.1109999"
+     y="0.46399999"
+     id="text1898"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">London</text>
+  <text
+     x="12.979"
+     y="8.0889997"
+     id="text1900"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Washington, DC</text>
+  <rect
+     width="11.132"
+     height="6.5630002"
+     x="-11.146"
+     y="16.205999"
+     id="rect1902"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
+     id="path1904"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
+     id="path1906"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.732"
+     height="5.9629998"
+     x="-11.446"
+     y="16.506001"
+     id="rect1908"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
+     id="path1910"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
+     id="path1912"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="-11.146"
+     y1="16.205999"
+     x2="-0.014"
+     y2="16.205999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1914"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.146"
+     y1="22.768999"
+     x2="-0.014"
+     y2="22.768999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1916"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
+     id="path1918"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
+     id="path1920"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.446"
+     y1="16.506001"
+     x2="-11.446"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1922"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.28600001"
+     y1="16.506001"
+     x2="0.28600001"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1924"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
+     id="path1926"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
+     id="path1928"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1930"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1932"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1934"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
+     id="path1936"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
+     id="path1938"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
+     id="polygon1940"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
+     id="polygon1942"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
+     id="polygon1944"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
+     id="polygon1946"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
+     id="path1948"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
+     id="path1950"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
+     id="polygon1952"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
+     id="polygon1954"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
+     id="polygon1956"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
+     id="polygon1958"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-5.2220001"
+     y="17.145"
+     id="text1960"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="-5.5609999"
+     y="17.745001"
+     id="text1962"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.4.0/22</text>
+  <text
+     x="-10.001"
+     y="21.07"
+     id="text1964"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="-10.37"
+     y="21.57"
+     id="text1966"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1968"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1970"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1972"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1974"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1976"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1978"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="19.087"
+     x2="-7.6300001"
+     y2="19.087"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1980"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.6300001"
+     y1="19.33"
+     x2="-8.6040001"
+     y2="19.33"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1982"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1984"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1986"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1988"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.665"
+     y1="20.181999"
+     x2="-7.448"
+     y2="20.181999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1990"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1992"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1994"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1996"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect1998"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect2000"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect2002"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2004"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2006"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2008"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2010"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2012"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2014"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4820004"
+     y1="19.816999"
+     x2="-7.8130002"
+     y2="19.816999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2016"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2018"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2020"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2022"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2024"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2026"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2028"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.695"
+     x2="-7.8740001"
+     y2="19.695"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2030"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2032"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2034"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2036"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.8130002"
+     y1="19.511999"
+     x2="-7.691"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2038"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.242001"
+     x2="-7.5089998"
+     y2="20.242001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2040"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.302999"
+     x2="-8.6040001"
+     y2="20.302999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2042"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.364"
+     x2="-7.5089998"
+     y2="20.364"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2044"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.547001"
+     x2="-8.6040001"
+     y2="20.547001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2046"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.486"
+     x2="-7.5089998"
+     y2="20.486"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2048"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.424999"
+     x2="-8.6040001"
+     y2="20.424999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2050"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5430002"
+     y1="19.511999"
+     x2="-8.4820004"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2052"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.511999"
+     x2="-8.3599997"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2054"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.756001"
+     x2="-8.3599997"
+     y2="19.756001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2056"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.9349999"
+     y1="19.756001"
+     x2="-7.8740001"
+     y2="19.756001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2058"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.4980001"
+     y1="19.695"
+     x2="-2.164"
+     y2="19.679001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2060"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.9559999"
+     y1="19.690001"
+     x2="-5.9530001"
+     y2="20.649"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2062"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.9530001"
+     y1="19.690001"
+     x2="-5.9559999"
+     y2="18.690001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2064"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-4.4590001"
+     y1="19.686001"
+     x2="-4.4559999"
+     y2="20.591"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2066"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-4.4569998"
+     y1="19.686001"
+     x2="-4.46"
+     y2="18.686001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2068"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-2.961"
+     y1="19.681"
+     x2="-2.9579999"
+     y2="20.608"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2070"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-2.9619999"
+     y1="19.681"
+     x2="-2.9649999"
+     y2="18.681"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2072"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.9439998"
+     y="20.618"
+     id="rect2074"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.9439998"
+     y="20.618"
+     id="rect2076"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-4.8470001"
+     y="20.715"
+     id="rect2078"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
+     id="polygon2080"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
+     id="polygon2082"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
+     id="polygon2084"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
+     id="polygon2086"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.3299999"
+     y="21.320999"
+     id="rect2088"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.3299999"
+     y="21.320999"
+     id="rect2090"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
+     id="polygon2092"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
+     id="polygon2094"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.4260001"
+     y="20.607"
+     id="rect2096"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.4260001"
+     y="20.607"
+     id="rect2098"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-3.329"
+     y="20.704"
+     id="rect2100"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
+     id="polygon2102"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
+     id="polygon2104"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
+     id="polygon2106"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
+     id="polygon2108"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.813"
+     y="21.311001"
+     id="rect2110"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.813"
+     y="21.311001"
+     id="rect2112"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
+     id="polygon2114"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
+     id="polygon2116"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-6.3759999"
+     y="18.181999"
+     id="rect2118"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-6.3759999"
+     y="18.181999"
+     id="rect2120"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-6.2789998"
+     y="18.278999"
+     id="rect2122"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
+     id="polygon2124"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
+     id="polygon2126"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
+     id="polygon2128"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
+     id="polygon2130"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-5.763"
+     y="18.886"
+     id="rect2132"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-5.763"
+     y="18.886"
+     id="rect2134"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
+     id="polygon2136"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
+     id="polygon2138"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.901"
+     y="18.181999"
+     id="rect2140"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.901"
+     y="18.181999"
+     id="rect2142"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-4.8039999"
+     y="18.278999"
+     id="rect2144"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
+     id="polygon2146"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
+     id="polygon2148"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
+     id="polygon2150"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
+     id="polygon2152"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.2880001"
+     y="18.886"
+     id="rect2154"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.2880001"
+     y="18.886"
+     id="rect2156"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
+     id="polygon2158"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
+     id="polygon2160"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.401"
+     y="18.207001"
+     id="rect2162"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.401"
+     y="18.207001"
+     id="rect2164"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-3.3039999"
+     y="18.304001"
+     id="rect2166"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
+     id="polygon2168"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
+     id="polygon2170"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
+     id="polygon2172"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
+     id="polygon2174"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.7880001"
+     y="18.910999"
+     id="rect2176"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.7880001"
+     y="18.910999"
+     id="rect2178"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
+     id="polygon2180"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
+     id="polygon2182"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
+     id="polygon2184"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
+     id="polygon2186"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -6.607,21.174 L -6.559,21.194 L -5.503,21.194 L -5.455,21.174"
+     id="path2188"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -5.503,21.194 L -5.431,21.234"
+     id="path2190"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -6.631,21.234 L -6.559,21.194"
+     id="path2192"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
+     id="polygon2194"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
+     id="polygon2196"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
+     id="polygon2198"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
+     id="polygon2200"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2202"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2204"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2206"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2208"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2210"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2212"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2214"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2216"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2218"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2220"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2222"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2224"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2226"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2228"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2230"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2232"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2234"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2236"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2238"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2240"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2242"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2244"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2246"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2248"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.0310001"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2250"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-6.0310001"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2252"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-5.7309999"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2254"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-5.7309999"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2256"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.17"
+     height="1.033"
+     x="-10.59"
+     y="19.132"
+     id="rect2258"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="-10.004"
+     cy="20.165001"
+     rx="0.58499998"
+     ry="0.17200001"
+     id="ellipse2260"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="-10.004"
+     cy="19.132"
+     rx="0.58499998"
+     ry="0.17200001"
+     id="ellipse2262"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="-10.004"
+     cy="19.132"
+     rx="0.58499998"
+     ry="0.17200001"
+     id="ellipse2264"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -9.419,19.132 L -9.419,20.165 C -9.419,20.26 -9.681,20.337 -10.004,20.337 C -10.328,20.337 -10.59,20.26 -10.59,20.165 L -10.59,19.132"
+     id="path2266"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-9.3959999"
+     y1="19.684"
+     x2="-8.665"
+     y2="19.695"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2268"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-10.303"
+     y="19.759001"
+     id="text2270"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="-10.288"
+     y="20.159"
+     id="text2272"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <text
+     x="-0.91500002"
+     y="19.843"
+     id="text2274"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <text
+     x="-1.867"
+     y="22.455999"
+     id="text2276"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
+  <text
+     x="-10.478"
+     y="17.114"
+     id="text2278"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
+  <text
+     x="-10.147"
+     y="17.914"
+     id="text2280"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg 2</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="-1.554,15.161 -1.554,15.906 -1.821,15.906 -1.821,19.285 "
+     id="polyline2282"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2284"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2286"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2288"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
+     id="path2290"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
+     id="path2292"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
+     id="polygon2294"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
+     id="polygon2296"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
+     id="polygon2298"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
+     id="polygon2300"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
+     id="path2302"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
+     id="path2304"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
+     id="polygon2306"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
+     id="polygon2308"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
+     id="polygon2310"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
+     id="polygon2312"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7.8559999"
+     y="17.167"
+     id="text2314"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="7.5180001"
+     y="17.767"
+     id="text2316"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.8.0/22</text>
+  <text
+     x="3.204"
+     y="18.118"
+     id="text2318"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="2.835"
+     y="18.618"
+     id="text2320"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-BDC</text>
+  <text
+     x="11.067"
+     y="21.718"
+     id="text2322"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="11.212"
+     y="22.218"
+     id="text2324"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-APPS</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2326"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2328"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2330"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2332"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2334"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2336"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="19.246"
+     x2="5.112"
+     y2="19.246"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2338"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.112"
+     y1="19.49"
+     x2="4.138"
+     y2="19.49"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2340"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2342"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2344"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2346"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.0770001"
+     y1="20.341"
+     x2="5.2940001"
+     y2="20.341"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2348"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2350"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2352"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2354"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2356"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2358"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2360"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2362"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2364"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2366"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2368"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2370"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2372"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.2600002"
+     y1="19.976"
+     x2="4.9289999"
+     y2="19.976"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2374"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2376"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2378"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2380"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2382"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2384"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2386"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.855"
+     x2="4.868"
+     y2="19.855"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2388"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2390"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2392"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2394"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.9289999"
+     y1="19.672001"
+     x2="5.0510001"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2396"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.402"
+     x2="5.2329998"
+     y2="20.402"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2398"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.462999"
+     x2="4.138"
+     y2="20.462999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2400"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.524"
+     x2="5.2329998"
+     y2="20.524"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2402"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.705999"
+     x2="4.138"
+     y2="20.705999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2404"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.645"
+     x2="5.2329998"
+     y2="20.645"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2406"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.584999"
+     x2="4.138"
+     y2="20.584999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2408"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.1989999"
+     y1="19.672001"
+     x2="4.2600002"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2410"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.672001"
+     x2="4.382"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2412"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.915001"
+     x2="4.382"
+     y2="19.915001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2414"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.8070002"
+     y1="19.915001"
+     x2="4.868"
+     y2="19.915001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2416"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.244"
+     y1="19.855"
+     x2="10.386"
+     y2="19.841999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2418"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.7309999"
+     y1="19.851"
+     x2="6.7329998"
+     y2="20.809999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2420"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.7350001"
+     y1="19.851"
+     x2="6.7319999"
+     y2="18.851"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2422"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.1739998"
+     y1="19.847"
+     x2="8.1759996"
+     y2="20.753"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2424"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.1750002"
+     y1="19.847"
+     x2="8.1730003"
+     y2="18.848"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2426"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.6169996"
+     y1="19.844"
+     x2="9.6190004"
+     y2="20.771"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2428"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.6160002"
+     y1="19.844"
+     x2="9.6129999"
+     y2="18.844"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2430"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.723"
+     y="20.778"
+     id="rect2432"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.723"
+     y="20.778"
+     id="rect2434"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.8210001"
+     y="20.875"
+     id="rect2436"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
+     id="polygon2438"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
+     id="polygon2440"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
+     id="polygon2442"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
+     id="polygon2444"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3369999"
+     y="21.481001"
+     id="rect2446"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3369999"
+     y="21.481001"
+     id="rect2448"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
+     id="polygon2450"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
+     id="polygon2452"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.1660004"
+     y="20.767"
+     id="rect2454"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.1660004"
+     y="20.767"
+     id="rect2456"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="9.2629995"
+     y="20.864"
+     id="rect2458"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
+     id="polygon2460"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
+     id="polygon2462"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
+     id="polygon2464"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
+     id="polygon2466"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.7790003"
+     y="21.469999"
+     id="rect2468"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.7790003"
+     y="21.469999"
+     id="rect2470"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
+     id="polygon2472"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
+     id="polygon2474"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.2909999"
+     y="18.341999"
+     id="rect2476"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.2909999"
+     y="18.341999"
+     id="rect2478"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.388"
+     y="18.438999"
+     id="rect2480"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
+     id="polygon2482"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
+     id="polygon2484"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
+     id="polygon2486"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
+     id="polygon2488"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.9039998"
+     y="19.045"
+     id="rect2490"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.9039998"
+     y="19.045"
+     id="rect2492"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
+     id="polygon2494"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
+     id="polygon2496"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.7410002"
+     y="18.367001"
+     id="rect2498"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.7410002"
+     y="18.367001"
+     id="rect2500"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.8379998"
+     y="18.464001"
+     id="rect2502"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
+     id="polygon2504"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
+     id="polygon2506"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
+     id="polygon2508"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
+     id="polygon2510"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3540001"
+     y="19.07"
+     id="rect2512"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3540001"
+     y="19.07"
+     id="rect2514"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
+     id="polygon2516"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
+     id="polygon2518"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.191"
+     y="18.341999"
+     id="rect2520"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.191"
+     y="18.341999"
+     id="rect2522"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="9.2880001"
+     y="18.438999"
+     id="rect2524"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
+     id="polygon2526"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
+     id="polygon2528"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
+     id="polygon2530"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
+     id="polygon2532"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.8039999"
+     y="19.045"
+     id="rect2534"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.8039999"
+     y="19.045"
+     id="rect2536"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
+     id="polygon2538"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
+     id="polygon2540"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
+     id="polygon2542"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
+     id="polygon2544"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 6.135,21.334 L 6.183,21.354 L 7.239,21.354 L 7.287,21.334"
+     id="path2546"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.239,21.354 L 7.311,21.394"
+     id="path2548"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 6.111,21.394 L 6.183,21.354"
+     id="path2550"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
+     id="polygon2552"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
+     id="polygon2554"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
+     id="polygon2556"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
+     id="polygon2558"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2560"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2562"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2564"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2566"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2568"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2570"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2572"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2574"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2576"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2578"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2580"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2582"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2584"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2586"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2588"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2590"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2592"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2594"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2596"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2598"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2600"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2602"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2604"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2606"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.711"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2608"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="6.711"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2610"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.0110002"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2612"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="7.0110002"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2614"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2616"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2618"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2620"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2622"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2624"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2626"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.533"
+     y1="19.048"
+     x2="10.618"
+     y2="19.048"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2628"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.618"
+     y1="19.275999"
+     x2="11.533"
+     y2="19.275999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2630"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.533"
+     y1="19.448"
+     x2="10.618"
+     y2="19.448"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2632"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2634"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2636"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2638"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.504"
+     y1="20.249001"
+     x2="11.647"
+     y2="20.249001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2640"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2642"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2644"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2646"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2648"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2650"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2652"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2654"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2656"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2658"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2660"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2662"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2664"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.618"
+     y1="20.02"
+     x2="11.247"
+     y2="20.02"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2666"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2668"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2670"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2672"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2674"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2676"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2678"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.906"
+     x2="11.19"
+     y2="19.906"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2680"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.19"
+     y1="19.962999"
+     x2="11.133"
+     y2="19.962999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2682"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.962999"
+     x2="10.732"
+     y2="19.962999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2684"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2686"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2688"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2690"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.620001"
+     x2="10.732"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.79"
+     y1="19.620001"
+     x2="10.847"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.362"
+     y1="19.620001"
+     x2="11.476"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.934999"
+     x2="10.561"
+     y2="20.934999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2698"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.878"
+     x2="11.59"
+     y2="20.878"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2700"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.820999"
+     x2="10.561"
+     y2="20.820999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2702"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.763"
+     x2="11.59"
+     y2="20.763"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2704"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.705999"
+     x2="10.561"
+     y2="20.705999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2706"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.649"
+     x2="11.59"
+     y2="20.649"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2708"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.591999"
+     x2="10.561"
+     y2="20.591999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2710"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.4960001"
+     y1="19.819"
+     x2="4.0770001"
+     y2="19.855"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2712"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.183"
+     height="1.044"
+     x="2.302"
+     y="19.268999"
+     id="rect2714"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="2.8940001"
+     cy="20.312"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2716"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="2.8940001"
+     cy="19.268999"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2718"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="2.8940001"
+     cy="19.268999"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2720"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.485,19.269 L 3.485,20.312 C 3.485,20.409 3.221,20.486 2.894,20.486 C 2.567,20.486 2.302,20.409 2.302,20.312 L 2.302,19.269"
+     id="path2722"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.589"
+     y="19.868999"
+     id="text2724"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="2.6040001"
+     y="20.268999"
+     id="text2726"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <text
+     x="2.0469999"
+     y="22.452"
+     id="text2728"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">250 Users</text>
+  <text
+     x="12.072"
+     y="17.239"
+     id="text2730"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
+  <text
+     x="12.402"
+     y="18.039"
+     id="text2732"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg 3</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="-1.129,15.125 -1.129,15.903 5.732,15.903 5.732,16.538 "
+     id="polyline2734"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.1"
+     y1="22.393"
+     x2="15.55"
+     y2="23.143"
+     stroke="#F7F7F7"
+     stroke-width="0.100"
+     id="line2736"
+     style="stroke:#f7f7f7;stroke-width:0.1" />
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap7-net2-B.svg b/docs-xml/Samba3-ByExample/images/chap7-net2-B.svg
new file mode 100644
index 00000000000..8158b3b9eb8
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap7-net2-B.svg
@@ -0,0 +1,9085 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="34.602001cm"
+   height="23.67cm"
+   viewBox="-11.55 -0.456 23.052 23.213"
+   id="svg2">
+  <defs
+     id="defs2769" />
+  <rect
+     width="13.8"
+     height="6.513"
+     x="1.375"
+     y="16.256001"
+     id="rect4"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
+     id="path6"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
+     id="path8"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="14.4"
+     height="5.9130001"
+     x="1.075"
+     y="16.556"
+     id="rect10"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
+     id="path12"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
+     id="path14"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="1.375"
+     y1="16.256001"
+     x2="15.175"
+     y2="16.256001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.375"
+     y1="22.768999"
+     x2="15.175"
+     y2="22.768999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.075"
+     y1="16.556"
+     x2="1.075"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="15.475"
+     y1="16.556"
+     x2="15.475"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.617"
+     height="6.8530002"
+     x="0.495"
+     y="-0.40599999"
+     id="rect32"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
+     id="path34"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
+     id="path36"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.217"
+     height="6.2529998"
+     x="0.19499999"
+     y="-0.106"
+     id="rect38"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
+     id="path40"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
+     id="path42"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="0.495"
+     y1="-0.40599999"
+     x2="11.112"
+     y2="-0.40599999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line44"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.495"
+     y1="6.447"
+     x2="11.112"
+     y2="6.447"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
+     id="path50"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.19499999"
+     y1="-0.106"
+     x2="0.19499999"
+     y2="6.1469998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.412"
+     y1="-0.106"
+     x2="11.412"
+     y2="6.1469998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line54"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
+     id="path56"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
+     id="path58"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.337"
+     height="6.8600001"
+     x="12.35"
+     y="-0.43099999"
+     id="rect60"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
+     id="path62"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
+     id="path64"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="10.937"
+     height="6.2600002"
+     x="12.05"
+     y="-0.131"
+     id="rect66"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
+     id="path68"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
+     id="path70"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="12.35"
+     y1="-0.43099999"
+     x2="22.687"
+     y2="-0.43099999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.35"
+     y1="6.4289999"
+     x2="22.687"
+     y2="6.4289999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.05"
+     y1="-0.131"
+     x2="12.05"
+     y2="6.1290002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="22.987"
+     y1="-0.131"
+     x2="22.987"
+     y2="6.1290002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
+     id="path84"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
+     id="path86"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.821"
+     height="8.375"
+     x="11.905"
+     y="7.244"
+     id="rect88"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
+     id="path90"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
+     id="path92"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.421"
+     height="7.7750001"
+     x="11.605"
+     y="7.5440001"
+     id="rect94"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
+     id="path96"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
+     id="path98"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="11.905"
+     y1="7.244"
+     x2="22.726999"
+     y2="7.244"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line100"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.905"
+     y1="15.619"
+     x2="22.726999"
+     y2="15.619"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line102"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
+     id="path104"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
+     id="path106"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.605"
+     y1="7.5440001"
+     x2="11.605"
+     y2="15.319"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line108"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="23.027"
+     y1="7.5440001"
+     x2="23.027"
+     y2="15.319"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line110"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
+     id="path112"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
+     id="path114"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="15.45"
+     height="8.3719997"
+     x="-11.225"
+     y="7.1339998"
+     id="rect116"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
+     id="path118"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 4.525,7.434 C 4.525,7.2683146 4.3906854,7.134 4.225,7.134"
+     id="path120"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="16.049999"
+     height="7.7719998"
+     x="-11.525"
+     y="7.434"
+     id="rect122"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
+     id="path124"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 4.225,15.506 C 4.3906854,15.506 4.525,15.371685 4.525,15.206"
+     id="path126"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="-11.225"
+     y1="7.1339998"
+     x2="4.2249999"
+     y2="7.1339998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line128"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.225"
+     y1="15.506"
+     x2="4.2249999"
+     y2="15.506"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line130"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
+     id="path132"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 4.525,7.434 C 4.525,7.2683146 4.3906854,7.134 4.225,7.134"
+     id="path134"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.525"
+     y1="7.434"
+     x2="-11.525"
+     y2="15.206"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="4.5250001"
+     y1="7.434"
+     x2="4.5250001"
+     y2="15.206"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
+     id="path140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 4.225,15.506 C 4.3906854,15.506 4.525,15.371685 4.525,15.206"
+     id="path142"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.95"
+     y1="11.168"
+     x2="4.8109999"
+     y2="11.165"
+     stroke="#000000"
+     stroke-width="0.300"
+     id="line144"
+     style="stroke:#000000;stroke-width:0.30000001" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="4.145,2.624 4.145,6.819 5.675,6.819 5.675,9.944 "
+     id="polyline146"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="16.100,2.794 16.100,6.844 8.674,6.844 8.674,9.887 "
+     id="polyline148"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.98000002"
+     height="0.98000002"
+     x="-1.818"
+     y="14.136"
+     id="rect150"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.98000002"
+     height="0.98000002"
+     x="-1.818"
+     y="14.136"
+     id="rect152"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.98000002"
+     height="0.98000002"
+     x="-1.818"
+     y="14.136"
+     id="rect154"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
+     id="path156"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
+     id="path158"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
+     id="polygon160"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
+     id="polygon162"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
+     id="polygon164"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
+     id="polygon166"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
+     id="path168"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
+     id="path170"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
+     id="polygon172"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
+     id="polygon174"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
+     id="polygon176"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
+     id="polygon178"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-1.306"
+     y1="11.165"
+     x2="-1.3279999"
+     y2="14.136"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line180"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.71700001"
+     y="7.6999998"
+     id="text182"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="0.37799999"
+     y="8.1999998"
+     id="text184"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-PDC</text>
+  <line
+     x1="6.118"
+     y1="13.16"
+     x2="7.7179999"
+     y2="13.135"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.10,0.10"
+     id="line186"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <text
+     x="8.4429998"
+     y="13.325"
+     id="text188"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">= VPN</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="10.645,11.075 10.645,9.069 16.025,9.069 16.025,11.368 "
+     id="polyline190"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-3.0239999"
+     y="14.751"
+     id="text192"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <text
+     x="4.1469998"
+     y="17.031"
+     id="text194"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect196"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect198"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect202"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect204"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect206"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="2.027"
+     x2="3.5869999"
+     y2="2.027"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line208"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.5869999"
+     y1="2.2709999"
+     x2="2.6140001"
+     y2="2.2709999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line210"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect212"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect214"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect216"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.553"
+     y1="3.122"
+     x2="3.77"
+     y2="3.122"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line218"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect220"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect222"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect224"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect226"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect228"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect230"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect232"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect234"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect236"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect238"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect240"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect242"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7360001"
+     y1="2.757"
+     x2="3.405"
+     y2="2.757"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line244"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect246"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect248"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect250"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect252"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect254"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect256"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.6359999"
+     x2="3.3440001"
+     y2="2.6359999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line258"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect260"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect262"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect264"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.405"
+     y1="2.4530001"
+     x2="3.527"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line266"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.1830001"
+     x2="3.7090001"
+     y2="3.1830001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line268"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.244"
+     x2="2.6140001"
+     y2="3.244"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line270"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.3050001"
+     x2="3.7090001"
+     y2="3.3050001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line272"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.487"
+     x2="2.6140001"
+     y2="3.487"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line274"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.427"
+     x2="3.7090001"
+     y2="3.427"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line276"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.3659999"
+     x2="2.6140001"
+     y2="3.3659999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line278"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.675"
+     y1="2.4530001"
+     x2="2.7360001"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line280"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.4530001"
+     x2="2.8570001"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line282"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.697"
+     x2="2.8570001"
+     y2="2.697"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line284"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.283"
+     y1="2.697"
+     x2="3.3440001"
+     y2="2.697"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line286"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.72"
+     y1="2.6359999"
+     x2="8.8620005"
+     y2="2.6229999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line288"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.2069998"
+     y1="2.632"
+     x2="5.2090001"
+     y2="3.5910001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line290"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.21"
+     y1="2.632"
+     x2="5.2080002"
+     y2="1.632"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line292"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.6500001"
+     y1="2.6289999"
+     x2="6.652"
+     y2="3.5339999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line294"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.651"
+     y1="2.6289999"
+     x2="6.6479998"
+     y2="1.6289999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line296"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.092"
+     y1="2.625"
+     x2="8.0950003"
+     y2="3.552"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line298"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.0909996"
+     y1="2.625"
+     x2="8.0889997"
+     y2="1.625"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line300"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.1989999"
+     y="3.559"
+     id="rect302"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.1989999"
+     y="3.559"
+     id="rect304"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.296"
+     y="3.6559999"
+     id="rect306"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
+     id="polygon308"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
+     id="polygon310"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
+     id="polygon312"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
+     id="polygon314"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8130002"
+     y="4.2620001"
+     id="rect316"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8130002"
+     y="4.2620001"
+     id="rect318"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
+     id="polygon320"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
+     id="polygon322"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6420002"
+     y="3.5480001"
+     id="rect324"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6420002"
+     y="3.5480001"
+     id="rect326"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.7389998"
+     y="3.645"
+     id="rect328"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
+     id="polygon330"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
+     id="polygon332"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
+     id="polygon334"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
+     id="polygon336"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2550001"
+     y="4.2509999"
+     id="rect338"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2550001"
+     y="4.2509999"
+     id="rect340"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
+     id="polygon342"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
+     id="polygon344"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="4.7670002"
+     y="1.123"
+     id="rect346"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="4.7670002"
+     y="1.123"
+     id="rect348"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="4.8639998"
+     y="1.22"
+     id="rect350"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
+     id="polygon352"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
+     id="polygon354"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
+     id="polygon356"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
+     id="polygon358"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="5.3800001"
+     y="1.826"
+     id="rect360"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="5.3800001"
+     y="1.826"
+     id="rect362"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
+     id="polygon364"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
+     id="polygon366"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.217"
+     y="1.148"
+     id="rect368"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.217"
+     y="1.148"
+     id="rect370"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.3140001"
+     y="1.245"
+     id="rect372"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
+     id="polygon374"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
+     id="polygon376"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
+     id="polygon378"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
+     id="polygon380"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8299999"
+     y="1.851"
+     id="rect382"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8299999"
+     y="1.851"
+     id="rect384"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
+     id="polygon386"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
+     id="polygon388"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6669998"
+     y="1.123"
+     id="rect390"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6669998"
+     y="1.123"
+     id="rect392"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.7639999"
+     y="1.22"
+     id="rect394"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
+     id="polygon396"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
+     id="polygon398"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
+     id="polygon400"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
+     id="polygon402"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2799997"
+     y="1.826"
+     id="rect404"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2799997"
+     y="1.826"
+     id="rect406"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
+     id="polygon408"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
+     id="polygon410"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
+     id="polygon412"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
+     id="polygon414"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.611,4.115 L 4.659,4.135 L 5.715,4.135 L 5.763,4.115"
+     id="path416"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.715,4.135 L 5.787,4.175"
+     id="path418"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.587,4.175 L 4.659,4.135"
+     id="path420"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
+     id="polygon422"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
+     id="polygon424"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
+     id="polygon426"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
+     id="polygon428"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse430"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse432"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse434"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse436"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse438"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse440"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse442"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse444"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse446"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse448"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse450"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse452"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse454"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse456"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse458"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse460"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse462"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse464"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse466"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse468"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse470"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse472"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse474"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse476"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.1869998"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse478"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="5.1869998"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse480"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.487"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse482"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="5.487"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse484"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect486"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect488"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect490"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect492"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect494"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect496"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.009"
+     y1="1.829"
+     x2="9.0939999"
+     y2="1.829"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line498"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0939999"
+     y1="2.0580001"
+     x2="10.009"
+     y2="2.0580001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line500"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.009"
+     y1="2.2290001"
+     x2="9.0939999"
+     y2="2.2290001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line502"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect504"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect506"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect508"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.9790001"
+     y1="3.03"
+     x2="10.123"
+     y2="3.03"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line510"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect512"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect514"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect516"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect518"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect520"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect522"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect524"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect526"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect528"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect530"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect532"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect534"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0939999"
+     y1="2.8010001"
+     x2="9.7229996"
+     y2="2.8010001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line536"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect538"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect540"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect542"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect544"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect546"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect548"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.687"
+     x2="9.6660004"
+     y2="2.687"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line550"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.6660004"
+     y1="2.744"
+     x2="9.6090002"
+     y2="2.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line552"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.744"
+     x2="9.2080002"
+     y2="2.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line554"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect556"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect558"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect560"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.401"
+     x2="9.2080002"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line562"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.2650003"
+     y1="2.401"
+     x2="9.323"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line564"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.8369999"
+     y1="2.401"
+     x2="9.9519997"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line566"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.7160001"
+     x2="9.0369997"
+     y2="3.7160001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line568"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.6589999"
+     x2="10.066"
+     y2="3.6589999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line570"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.602"
+     x2="9.0369997"
+     y2="3.602"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line572"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.5439999"
+     x2="10.066"
+     y2="3.5439999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line574"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.487"
+     x2="9.0369997"
+     y2="3.487"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line576"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.4300001"
+     x2="10.066"
+     y2="3.4300001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line578"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.3729999"
+     x2="9.0369997"
+     y2="3.3729999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line580"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="5.9629998"
+     y="5.2589998"
+     id="text582"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="5.5580001"
+     y="5.8590002"
+     id="text584"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.12.0/22</text>
+  <text
+     x="1.234"
+     y="4.1529999"
+     id="text586"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="1.053"
+     y="4.6529999"
+     id="text588"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-BDC</text>
+  <text
+     x="9.5100002"
+     y="4.4749999"
+     id="text590"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="9.3299999"
+     y="4.9749999"
+     id="text592"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-PDC</text>
+  <rect
+     width="1.291"
+     height="1.1390001"
+     x="0.61699998"
+     y="2.0880001"
+     id="rect594"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="1.263"
+     cy="3.227"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse596"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.263"
+     cy="2.0880001"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse598"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.263"
+     cy="2.0880001"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse600"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 1.908,2.088 L 1.908,3.227 C 1.908,3.332 1.619,3.417 1.263,3.417 C 0.906,3.417 0.617,3.332 0.617,3.227 L 0.617,2.088"
+     id="path602"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="1.928"
+     y1="2.523"
+     x2="2.503"
+     y2="2.523"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line604"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.935"
+     y="2.7219999"
+     id="text606"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="0.94999999"
+     y="3.122"
+     id="text608"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect610"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect612"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect614"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect616"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect618"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect620"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="2.1900001"
+     x2="15.431"
+     y2="2.1900001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line622"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="2.4330001"
+     x2="14.458"
+     y2="2.4330001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line624"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect626"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect628"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect630"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.397"
+     y1="3.2850001"
+     x2="15.614"
+     y2="3.2850001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line632"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect634"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect636"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect638"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect640"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect642"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect644"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect646"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect648"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect650"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect652"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect654"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect656"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.58"
+     y1="2.9200001"
+     x2="15.249"
+     y2="2.9200001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line658"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect660"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect662"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect664"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect666"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect668"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect670"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.7980001"
+     x2="15.188"
+     y2="2.7980001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line672"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect674"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect676"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect678"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.249"
+     y1="2.615"
+     x2="15.371"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line680"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.345"
+     x2="15.553"
+     y2="3.345"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line682"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.4059999"
+     x2="14.458"
+     y2="3.4059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line684"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.467"
+     x2="15.553"
+     y2="3.467"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line686"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.6500001"
+     x2="14.458"
+     y2="3.6500001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line688"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.589"
+     x2="15.553"
+     y2="3.589"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line690"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.5280001"
+     x2="14.458"
+     y2="3.5280001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="2.615"
+     x2="14.58"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.615"
+     x2="14.701"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.859"
+     x2="14.701"
+     y2="2.859"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line698"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.127"
+     y1="2.859"
+     x2="15.188"
+     y2="2.859"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line700"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.564"
+     y1="2.7980001"
+     x2="20.705"
+     y2="2.7850001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line702"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.051001"
+     y1="2.7939999"
+     x2="17.052999"
+     y2="3.753"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line704"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.054001"
+     y1="2.7939999"
+     x2="17.052"
+     y2="1.794"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line706"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.493"
+     y1="2.7909999"
+     x2="18.496"
+     y2="3.6960001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line708"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.495001"
+     y1="2.7909999"
+     x2="18.492001"
+     y2="1.791"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line710"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.936001"
+     y1="2.7869999"
+     x2="19.938999"
+     y2="3.714"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line712"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.934999"
+     y1="2.7869999"
+     x2="19.933001"
+     y2="1.7869999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line714"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.042999"
+     y="3.721"
+     id="rect716"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.042999"
+     y="3.721"
+     id="rect718"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.139999"
+     y="3.8180001"
+     id="rect720"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
+     id="polygon722"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
+     id="polygon724"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
+     id="polygon726"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
+     id="polygon728"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.657"
+     y="4.4239998"
+     id="rect730"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.657"
+     y="4.4239998"
+     id="rect732"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
+     id="polygon734"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
+     id="polygon736"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.486"
+     y="3.71"
+     id="rect738"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.486"
+     y="3.71"
+     id="rect740"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.583"
+     y="3.8069999"
+     id="rect742"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
+     id="polygon744"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
+     id="polygon746"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
+     id="polygon748"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
+     id="polygon750"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.099001"
+     y="4.414"
+     id="rect752"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.099001"
+     y="4.414"
+     id="rect754"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
+     id="polygon756"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
+     id="polygon758"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.611"
+     y="1.285"
+     id="rect760"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.611"
+     y="1.285"
+     id="rect762"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="16.708"
+     y="1.382"
+     id="rect764"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
+     id="polygon766"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
+     id="polygon768"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
+     id="polygon770"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
+     id="polygon772"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.224001"
+     y="1.989"
+     id="rect774"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.224001"
+     y="1.989"
+     id="rect776"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
+     id="polygon778"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
+     id="polygon780"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.061001"
+     y="1.3099999"
+     id="rect782"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.061001"
+     y="1.3099999"
+     id="rect784"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.158001"
+     y="1.4069999"
+     id="rect786"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
+     id="polygon788"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
+     id="polygon790"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
+     id="polygon792"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
+     id="polygon794"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.674"
+     y="2.0139999"
+     id="rect796"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.674"
+     y="2.0139999"
+     id="rect798"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
+     id="polygon800"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
+     id="polygon802"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.511"
+     y="1.285"
+     id="rect804"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.511"
+     y="1.285"
+     id="rect806"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.608"
+     y="1.382"
+     id="rect808"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
+     id="polygon810"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
+     id="polygon812"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
+     id="polygon814"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
+     id="polygon816"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.124001"
+     y="1.989"
+     id="rect818"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.124001"
+     y="1.989"
+     id="rect820"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
+     id="polygon822"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
+     id="polygon824"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
+     id="polygon826"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
+     id="polygon828"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.454,4.277 L 16.502,4.297 L 17.558,4.297 L 17.606,4.277"
+     id="path830"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 17.558,4.297 L 17.63,4.337"
+     id="path832"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.43,4.337 L 16.502,4.297"
+     id="path834"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
+     id="polygon836"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
+     id="polygon838"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
+     id="polygon840"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
+     id="polygon842"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="16.67"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse844"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse846"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse848"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse850"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse852"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse854"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse856"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse858"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse860"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse862"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse864"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse866"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse868"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse870"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse872"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse874"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse876"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse878"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse880"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse882"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse884"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse886"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse888"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse890"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.030001"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse892"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.030001"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse894"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.33"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse896"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.33"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse898"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect900"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect902"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect904"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect906"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect908"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect910"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.853001"
+     y1="1.9910001"
+     x2="20.938"
+     y2="1.9910001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line912"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.938"
+     y1="2.22"
+     x2="21.853001"
+     y2="2.22"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line914"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.853001"
+     y1="2.391"
+     x2="20.938"
+     y2="2.391"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line916"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect918"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect920"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect922"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.823"
+     y1="3.1919999"
+     x2="21.966999"
+     y2="3.1919999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line924"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect926"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect928"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect930"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect932"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect934"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect936"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect938"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect940"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect942"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect944"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect946"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect948"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.938"
+     y1="2.9630001"
+     x2="21.566999"
+     y2="2.9630001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line950"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect952"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect954"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect956"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect958"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect960"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect962"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.849"
+     x2="21.51"
+     y2="2.849"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line964"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.51"
+     y1="2.9059999"
+     x2="21.452"
+     y2="2.9059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line966"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.9059999"
+     x2="21.052"
+     y2="2.9059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line968"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect970"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect972"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect974"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.563"
+     x2="21.052"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line976"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.108999"
+     y1="2.563"
+     x2="21.167"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line978"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.681"
+     y1="2.563"
+     x2="21.796"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line980"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.878"
+     x2="20.881001"
+     y2="3.878"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line982"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.8210001"
+     x2="21.91"
+     y2="3.8210001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line984"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.7639999"
+     x2="20.881001"
+     y2="3.7639999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line986"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.707"
+     x2="21.91"
+     y2="3.707"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line988"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.6489999"
+     x2="20.881001"
+     y2="3.6489999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line990"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.592"
+     x2="21.91"
+     y2="3.592"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line992"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.5350001"
+     x2="20.881001"
+     y2="3.5350001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line994"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="18.056999"
+     y="5.3460002"
+     id="text996"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="17.650999"
+     y="5.9460001"
+     id="text998"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.16.0/22</text>
+  <text
+     x="14.353"
+     y="4.415"
+     id="text1000"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="14.288"
+     y="4.915"
+     id="text1002"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-BDC</text>
+  <text
+     x="21.112"
+     y="4.5809999"
+     id="text1004"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="21.048"
+     y="5.0809999"
+     id="text1006"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-PDC</text>
+  <rect
+     width="1.326"
+     height="1.17"
+     x="12.426"
+     y="2.155"
+     id="rect1008"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="13.089"
+     cy="3.326"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1010"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.089"
+     cy="2.155"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1012"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.089"
+     cy="2.155"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1014"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 13.752,2.155 L 13.752,3.326 C 13.752,3.434 13.455,3.521 13.089,3.521 C 12.723,3.521 12.426,3.434 12.426,3.326 L 12.426,2.155"
+     id="path1016"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.775"
+     y1="2.6440001"
+     x2="14.372"
+     y2="2.648"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1018"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.767"
+     y="2.819"
+     id="text1020"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="12.782"
+     y="3.2190001"
+     id="text1022"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1024"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1026"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1028"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1030"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1032"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1034"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="10.744"
+     x2="15.309"
+     y2="10.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1036"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.309"
+     y1="10.988"
+     x2="14.336"
+     y2="10.988"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1038"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1040"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1042"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1044"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.275"
+     y1="11.839"
+     x2="15.492"
+     y2="11.839"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1046"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1048"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1050"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1052"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1054"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1056"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1058"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1060"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1062"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1064"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1066"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1068"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1070"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="11.474"
+     x2="15.127"
+     y2="11.474"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1072"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1074"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1076"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1078"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1080"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1082"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1084"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.353"
+     x2="15.066"
+     y2="11.353"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1086"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1088"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1090"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1092"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.127"
+     y1="11.17"
+     x2="15.249"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1094"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="11.9"
+     x2="15.431"
+     y2="11.9"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1096"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="11.961"
+     x2="14.336"
+     y2="11.961"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1098"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="12.022"
+     x2="15.431"
+     y2="12.022"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1100"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="12.204"
+     x2="14.336"
+     y2="12.204"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1102"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="12.143"
+     x2="15.431"
+     y2="12.143"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1104"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="12.083"
+     x2="14.336"
+     y2="12.083"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1106"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.397"
+     y1="11.17"
+     x2="14.458"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1108"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.17"
+     x2="14.579"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1110"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.413"
+     x2="14.579"
+     y2="11.413"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1112"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.005"
+     y1="11.413"
+     x2="15.066"
+     y2="11.413"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1114"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.442"
+     y1="11.353"
+     x2="20.584"
+     y2="11.34"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1116"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.929001"
+     y1="11.349"
+     x2="16.931"
+     y2="12.308"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1118"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.931999"
+     y1="11.349"
+     x2="16.93"
+     y2="10.349"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1120"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.372"
+     y1="11.345"
+     x2="18.374001"
+     y2="12.251"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1122"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.372999"
+     y1="11.345"
+     x2="18.370001"
+     y2="10.345"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1124"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.815001"
+     y1="11.342"
+     x2="19.816999"
+     y2="12.269"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1126"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.813"
+     y1="11.342"
+     x2="19.811001"
+     y2="10.342"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1128"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.921"
+     y="12.276"
+     id="rect1130"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.921"
+     y="12.276"
+     id="rect1132"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.018"
+     y="12.373"
+     id="rect1134"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
+     id="polygon1136"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
+     id="polygon1138"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
+     id="polygon1140"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
+     id="polygon1142"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.535"
+     y="12.979"
+     id="rect1144"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.535"
+     y="12.979"
+     id="rect1146"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
+     id="polygon1148"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
+     id="polygon1150"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.364"
+     y="12.265"
+     id="rect1152"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.364"
+     y="12.265"
+     id="rect1154"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.461"
+     y="12.362"
+     id="rect1156"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
+     id="polygon1158"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
+     id="polygon1160"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
+     id="polygon1162"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
+     id="polygon1164"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="19.976999"
+     y="12.968"
+     id="rect1166"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="19.976999"
+     y="12.968"
+     id="rect1168"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
+     id="polygon1170"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
+     id="polygon1172"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.489"
+     y="9.8400002"
+     id="rect1174"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.489"
+     y="9.8400002"
+     id="rect1176"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="16.586"
+     y="9.9370003"
+     id="rect1178"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
+     id="polygon1180"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
+     id="polygon1182"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
+     id="polygon1184"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
+     id="polygon1186"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.101999"
+     y="10.543"
+     id="rect1188"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.101999"
+     y="10.543"
+     id="rect1190"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
+     id="polygon1192"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
+     id="polygon1194"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.938999"
+     y="9.8649998"
+     id="rect1196"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.938999"
+     y="9.8649998"
+     id="rect1198"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.035999"
+     y="9.9619999"
+     id="rect1200"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
+     id="polygon1202"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
+     id="polygon1204"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
+     id="polygon1206"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
+     id="polygon1208"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.552"
+     y="10.568"
+     id="rect1210"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.552"
+     y="10.568"
+     id="rect1212"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
+     id="polygon1214"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
+     id="polygon1216"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.389"
+     y="9.8400002"
+     id="rect1218"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.389"
+     y="9.8400002"
+     id="rect1220"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.486"
+     y="9.9370003"
+     id="rect1222"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
+     id="polygon1224"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
+     id="polygon1226"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
+     id="polygon1228"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
+     id="polygon1230"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.002001"
+     y="10.543"
+     id="rect1232"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.002001"
+     y="10.543"
+     id="rect1234"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
+     id="polygon1236"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
+     id="polygon1238"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
+     id="polygon1240"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
+     id="polygon1242"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.333,12.832 L 16.381,12.852 L 17.437,12.852 L 17.485,12.832"
+     id="path1244"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 17.437,12.852 L 17.509,12.892"
+     id="path1246"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.309,12.892 L 16.381,12.852"
+     id="path1248"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
+     id="polygon1250"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
+     id="polygon1252"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
+     id="polygon1254"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
+     id="polygon1256"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="16.549"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1258"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1260"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1262"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1264"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1266"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1268"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1270"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1272"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1274"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1276"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1278"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1280"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1282"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1284"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1286"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1288"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1290"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1292"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1294"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1296"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1298"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1300"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1302"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1304"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.909"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1306"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="16.909"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1308"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.209"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1310"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.209"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1312"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1314"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1316"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1318"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1320"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1322"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1324"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.731001"
+     y1="10.546"
+     x2="20.816"
+     y2="10.546"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1326"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.816"
+     y1="10.774"
+     x2="21.731001"
+     y2="10.774"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1328"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.731001"
+     y1="10.946"
+     x2="20.816"
+     y2="10.946"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1330"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1332"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1334"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1336"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.701"
+     y1="11.747"
+     x2="21.844999"
+     y2="11.747"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1338"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1340"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1342"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1344"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1346"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1348"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1350"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1352"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1354"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1356"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1358"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1360"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1362"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.816"
+     y1="11.518"
+     x2="21.445"
+     y2="11.518"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1364"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1366"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1368"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1370"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1372"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1374"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1376"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.404"
+     x2="21.388"
+     y2="11.404"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1378"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.388"
+     y1="11.461"
+     x2="21.330999"
+     y2="11.461"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1380"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.461"
+     x2="20.93"
+     y2="11.461"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1382"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1384"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1386"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1388"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.118"
+     x2="20.93"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1390"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.987"
+     y1="11.118"
+     x2="21.045"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1392"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.559"
+     y1="11.118"
+     x2="21.674"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1394"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.433"
+     x2="20.759001"
+     y2="12.433"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1396"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.376"
+     x2="21.788"
+     y2="12.376"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1398"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.319"
+     x2="20.759001"
+     y2="12.319"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1400"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.261"
+     x2="21.788"
+     y2="12.261"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1402"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.204"
+     x2="20.759001"
+     y2="12.204"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1404"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.147"
+     x2="21.788"
+     y2="12.147"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1406"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.09"
+     x2="20.759001"
+     y2="12.09"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1408"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="17.735001"
+     y="9.026"
+     id="text1410"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="17.301001"
+     y="9.6260004"
+     id="text1412"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.20.0/22</text>
+  <text
+     x="14.206"
+     y="12.995"
+     id="text1414"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="13.878"
+     y="13.495"
+     id="text1416"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WADC-BDC</text>
+  <text
+     x="20.712"
+     y="13.518"
+     id="text1418"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="20.302"
+     y="14.018"
+     id="text1420"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WADC-APPS</text>
+  <rect
+     width="1.3150001"
+     height="1.161"
+     x="12"
+     y="10.659"
+     id="rect1422"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="12.658"
+     cy="11.819"
+     rx="0.65799999"
+     ry="0.193"
+     id="ellipse1424"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.658"
+     cy="10.659"
+     rx="0.65799999"
+     ry="0.193"
+     id="ellipse1426"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.658"
+     cy="10.659"
+     rx="0.65799999"
+     ry="0.193"
+     id="ellipse1428"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 13.316,10.659 L 13.316,11.819 C 13.316,11.926 13.021,12.013 12.658,12.013 C 12.295,12.013 12,11.926 12,11.819 L 12,10.659"
+     id="path1430"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="14.275"
+     y1="11.353"
+     x2="13.275"
+     y2="11.344"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1432"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.337"
+     y="11.292"
+     id="text1434"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="12.352"
+     y="11.692"
+     id="text1436"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <path
+     d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
+     id="path1438"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
+     id="path1440"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.7909999"
+     y="11.036"
+     id="text1442"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
+  <path
+     d="M 4.7,11.1 C 5.035363,11.196174 5.3953356,11.076093 5.6057965,10.797841 C 5.8162574,10.51959 5.8338243,10.140524 5.65,9.844"
+     id="path1444"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <path
+     d="M 8.675,9.794 C 7.4940305,10.104758 6.3530779,10.551408 5.275,11.125"
+     id="path1446"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <path
+     d="M 4.7,11.15 C 6.6098972,11.931939 8.7554368,11.904871 10.645,11.075"
+     id="path1448"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1450"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1452"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1454"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1456"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1458"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1460"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.1389999"
+     x2="1.8710001"
+     y2="9.1389999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1462"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.8710001"
+     y1="9.4180002"
+     x2="0.75400001"
+     y2="9.4180002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1464"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.698"
+     x2="1.8710001"
+     y2="9.698"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1466"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.9770002"
+     x2="1.8710001"
+     y2="9.9770002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1468"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.8710001"
+     y1="10.256"
+     x2="0.75400001"
+     y2="10.256"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1470"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1472"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1474"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1476"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.61400002"
+     y1="11.374"
+     x2="2.0109999"
+     y2="11.374"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1478"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1480"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1482"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1484"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1486"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1488"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1490"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1492"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1494"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1496"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1498"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1500"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1502"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="10.885"
+     x2="1.522"
+     y2="10.885"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1504"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1506"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1508"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1510"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1512"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1514"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1516"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.745"
+     x2="1.452"
+     y2="10.745"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1518"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.452"
+     y1="10.815"
+     x2="1.382"
+     y2="10.815"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1520"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.815"
+     x2="0.89300001"
+     y2="10.815"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1522"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1524"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1526"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1528"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.466"
+     x2="0.89300001"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1530"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.963"
+     y1="10.466"
+     x2="1.033"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1532"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.6619999"
+     y1="10.466"
+     x2="1.801"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1534"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.84"
+     x2="1.941"
+     y2="12.84"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1536"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.77"
+     x2="0.68400002"
+     y2="12.77"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1538"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.701"
+     x2="1.941"
+     y2="12.701"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1540"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.631"
+     x2="0.68400002"
+     y2="12.631"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1542"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.561"
+     x2="1.941"
+     y2="12.561"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1544"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.491"
+     x2="0.68400002"
+     y2="12.491"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1546"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.421"
+     x2="1.941"
+     y2="12.421"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1548"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.351"
+     x2="0.68400002"
+     y2="12.351"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1550"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.282"
+     x2="1.941"
+     y2="12.282"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1552"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.212"
+     x2="0.68400002"
+     y2="12.212"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1554"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.142"
+     x2="1.941"
+     y2="12.142"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1556"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.072"
+     x2="0.68400002"
+     y2="12.072"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1558"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.002"
+     x2="1.941"
+     y2="12.002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1560"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="11.932"
+     x2="0.68400002"
+     y2="11.932"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1562"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.6090002"
+     y="11.995"
+     id="rect1564"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.6090002"
+     y="11.995"
+     id="rect1566"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-6.5040002"
+     y="12.101"
+     id="rect1568"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.477,12.724 -5.978,12.724 -5.978,12.837 -6.451,12.837 -6.477,12.724 "
+     id="polygon1570"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.477,12.724 -5.978,12.724 -5.978,12.837 -6.451,12.837 -6.477,12.724 "
+     id="polygon1572"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.978,12.724 -5.769,12.724 -5.796,12.837 -5.978,12.837 -5.978,12.724 "
+     id="polygon1574"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.978,12.724 -5.769,12.724 -5.796,12.837 -5.978,12.837 -5.978,12.724 "
+     id="polygon1576"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.9439998"
+     y="12.758"
+     id="rect1578"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.9439998"
+     y="12.758"
+     id="rect1580"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.22,12.837 -6.026,12.837 -6.026,12.894 -5.929,12.894 -5.929,12.95 -6.317,12.95 -6.317,12.894 -6.22,12.894 -6.22,12.837 "
+     id="polygon1582"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.22,12.837 -6.026,12.837 -6.026,12.894 -5.929,12.894 -5.929,12.95 -6.317,12.95 -6.317,12.894 -6.22,12.894 -6.22,12.837 "
+     id="polygon1584"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.653"
+     y1="11.13"
+     x2="-9.6660004"
+     y2="11.13"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1586"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-1.289"
+     y1="11.13"
+     x2="-1.289"
+     y2="10.145"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1588"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-3.8"
+     y1="11.13"
+     x2="-3.8"
+     y2="12.118"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1590"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-3.7739999"
+     y1="11.13"
+     x2="-3.7739999"
+     y2="10.099"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1592"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-6.0999999"
+     y1="11.13"
+     x2="-6.0999999"
+     y2="11.993"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1594"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-6.0939999"
+     y1="11.13"
+     x2="-6.0939999"
+     y2="10.063"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1596"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-8.4139996"
+     y1="11.13"
+     x2="-8.4139996"
+     y2="9.5740004"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1598"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.069"
+     height="0.80199999"
+     x="-4.3639998"
+     y="11.941"
+     id="rect1600"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.069"
+     height="0.80199999"
+     x="-4.3639998"
+     y="11.941"
+     id="rect1602"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.83700001"
+     height="0.55199999"
+     x="-4.2480001"
+     y="12.057"
+     id="rect1604"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.219,12.743 -3.669,12.743 -3.669,12.868 -4.19,12.868 -4.219,12.743 "
+     id="polygon1606"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.219,12.743 -3.669,12.743 -3.669,12.868 -4.19,12.868 -4.219,12.743 "
+     id="polygon1608"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-3.669,12.743 -3.44,12.743 -3.469,12.868 -3.669,12.868 -3.669,12.743 "
+     id="polygon1610"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.669,12.743 -3.44,12.743 -3.469,12.868 -3.669,12.868 -3.669,12.743 "
+     id="polygon1612"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050000001"
+     height="0.050000001"
+     x="-3.632"
+     y="12.78"
+     id="rect1614"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050000001"
+     height="0.050000001"
+     x="-3.632"
+     y="12.78"
+     id="rect1616"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.936,12.868 -3.723,12.868 -3.723,12.93 -3.616,12.93 -3.616,12.992 -4.043,12.992 -4.043,12.93 -3.936,12.93 -3.936,12.868 "
+     id="polygon1618"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.936,12.868 -3.723,12.868 -3.723,12.93 -3.616,12.93 -3.616,12.992 -4.043,12.992 -4.043,12.93 -3.936,12.93 -3.936,12.868 "
+     id="polygon1620"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.579"
+     y="9.1079998"
+     id="rect1622"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.579"
+     y="9.1079998"
+     id="rect1624"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-6.474"
+     y="9.2139997"
+     id="rect1626"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
+     id="polygon1628"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
+     id="polygon1630"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
+     id="polygon1632"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
+     id="polygon1634"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.914"
+     y="9.8710003"
+     id="rect1636"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.914"
+     y="9.8710003"
+     id="rect1638"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
+     id="polygon1640"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
+     id="polygon1642"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-4.2600002"
+     y="9.1450005"
+     id="rect1644"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-4.2600002"
+     y="9.1450005"
+     id="rect1646"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-4.1550002"
+     y="9.25"
+     id="rect1648"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
+     id="polygon1650"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
+     id="polygon1652"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
+     id="polygon1654"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
+     id="polygon1656"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-3.595"
+     y="9.9069996"
+     id="rect1658"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-3.595"
+     y="9.9069996"
+     id="rect1660"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
+     id="polygon1662"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
+     id="polygon1664"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-8.9029999"
+     y="9.0410004"
+     id="rect1666"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-8.9029999"
+     y="9.0410004"
+     id="rect1668"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-8.7980003"
+     y="9.1470003"
+     id="rect1670"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
+     id="polygon1672"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
+     id="polygon1674"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
+     id="polygon1676"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
+     id="polygon1678"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-8.2379999"
+     y="9.8039999"
+     id="rect1680"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-8.2379999"
+     y="9.8039999"
+     id="rect1682"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
+     id="polygon1684"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
+     id="polygon1686"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
+     id="polygon1688"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
+     id="polygon1690"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -1.871,9.841 L -1.823,9.861 L -0.754,9.861 L -0.706,9.841"
+     id="path1692"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -0.754,9.861 L -0.682,9.902"
+     id="path1694"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -1.895,9.902 L -1.823,9.861"
+     id="path1696"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
+     id="polygon1698"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
+     id="polygon1700"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
+     id="polygon1702"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
+     id="polygon1704"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1706"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1708"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1710"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1712"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1714"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1716"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1718"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1720"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1722"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1724"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1726"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1728"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.653"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1730"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1732"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1734"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1736"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1738"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1740"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.653"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1742"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1744"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1746"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1748"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1750"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1752"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.289"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1754"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-1.289"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1756"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-0.98500001"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1758"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-0.98500001"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1760"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.312"
+     height="2.625"
+     x="-11.059"
+     y="9.7469997"
+     id="rect1762"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.312"
+     height="2.625"
+     x="-11.059"
+     y="9.7469997"
+     id="rect1764"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.312"
+     height="2.625"
+     x="-11.059"
+     y="9.7469997"
+     id="rect1766"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.05"
+     height="1.05"
+     x="-10.928"
+     y="9.8780003"
+     id="rect1768"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.05"
+     height="1.05"
+     x="-10.928"
+     y="9.8780003"
+     id="rect1770"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.05"
+     height="1.05"
+     x="-10.928"
+     y="9.8780003"
+     id="rect1772"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8780003"
+     y1="10.141"
+     x2="-10.928"
+     y2="10.141"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1774"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.928"
+     y1="10.403"
+     x2="-9.8780003"
+     y2="10.403"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1776"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8780003"
+     y1="10.6"
+     x2="-10.928"
+     y2="10.6"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1778"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.722"
+     height="0.39399999"
+     x="-10.928"
+     y="11.06"
+     id="rect1780"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.722"
+     height="0.39399999"
+     x="-10.928"
+     y="11.06"
+     id="rect1782"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.722"
+     height="0.39399999"
+     x="-10.928"
+     y="11.06"
+     id="rect1784"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-11.059"
+     y1="11.519"
+     x2="-9.7460003"
+     y2="11.519"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1786"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.468"
+     y="11.65"
+     id="rect1788"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.468"
+     y="11.65"
+     id="rect1790"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.468"
+     y="11.65"
+     id="rect1792"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.206"
+     y="11.65"
+     id="rect1794"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.206"
+     y="11.65"
+     id="rect1796"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.206"
+     y="11.65"
+     id="rect1798"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-9.9429998"
+     y="11.65"
+     id="rect1800"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-9.9429998"
+     y="11.65"
+     id="rect1802"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-9.9429998"
+     y="11.65"
+     id="rect1804"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.131"
+     height="0.066"
+     x="-10.009"
+     y="11.256"
+     id="rect1806"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.131"
+     height="0.066"
+     x="-10.009"
+     y="11.256"
+     id="rect1808"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.131"
+     height="0.066"
+     x="-10.009"
+     y="11.256"
+     id="rect1810"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.928"
+     y1="11.256"
+     x2="-10.206"
+     y2="11.256"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1812"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.197"
+     height="0.197"
+     x="-10.928"
+     y="11.585"
+     id="rect1814"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.197"
+     height="0.197"
+     x="-10.928"
+     y="11.585"
+     id="rect1816"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.197"
+     height="0.197"
+     x="-10.928"
+     y="11.585"
+     id="rect1818"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91900003"
+     height="0.066"
+     x="-10.862"
+     y="10.666"
+     id="rect1820"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91900003"
+     height="0.066"
+     x="-10.862"
+     y="10.666"
+     id="rect1822"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91900003"
+     height="0.066"
+     x="-10.862"
+     y="10.666"
+     id="rect1824"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.862"
+     y1="11.125"
+     x2="-10.271"
+     y2="11.125"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1826"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.271"
+     y1="11.191"
+     x2="-10.337"
+     y2="11.191"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1828"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.862"
+     y1="11.191"
+     x2="-10.796"
+     y2="11.191"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1830"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.32800001"
+     height="0.066"
+     x="-10.731"
+     y="11.125"
+     id="rect1832"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.32800001"
+     height="0.066"
+     x="-10.731"
+     y="11.125"
+     id="rect1834"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.32800001"
+     height="0.066"
+     x="-10.731"
+     y="11.125"
+     id="rect1836"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.862"
+     y1="10.797"
+     x2="-10.796"
+     y2="10.797"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1838"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.731"
+     y1="10.797"
+     x2="-10.665"
+     y2="10.797"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1840"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.074"
+     y1="10.797"
+     x2="-9.9429998"
+     y2="10.797"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1842"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="12.306"
+     x2="-10.993"
+     y2="12.306"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1844"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.993"
+     y1="12.241"
+     x2="-9.8120003"
+     y2="12.241"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1846"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="12.175"
+     x2="-10.993"
+     y2="12.175"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1848"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.993"
+     y1="12.11"
+     x2="-9.8120003"
+     y2="12.11"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1850"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="12.044"
+     x2="-10.993"
+     y2="12.044"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1852"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.993"
+     y1="11.978"
+     x2="-9.8120003"
+     y2="11.978"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1854"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="11.913"
+     x2="-10.993"
+     y2="11.913"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1856"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="-4.0289998"
+     y="8.2189999"
+     id="text1858"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="-4.3639998"
+     y="8.8190002"
+     id="text1860"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.0.0/22</text>
+  <text
+     x="-10.628"
+     y="13.181"
+     id="text1862"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="-10.454"
+     y="13.681"
+     id="text1864"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-APPS</text>
+  <rect
+     width="1.4450001"
+     height="1.275"
+     x="2.5510001"
+     y="8.6120005"
+     id="rect1866"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="3.273"
+     cy="9.8870001"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1868"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.273"
+     cy="8.6120005"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1870"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.273"
+     cy="8.6120005"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1872"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.996,8.612 L 3.996,9.887 C 3.996,10.005 3.672,10.1 3.273,10.1 C 2.874,10.1 2.551,10.005 2.551,9.887 L 2.551,8.612"
+     id="path1874"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="2.0109999"
+     y1="9.2469997"
+     x2="2.586"
+     y2="9.2469997"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1876"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.983"
+     y="9.3260002"
+     id="text1878"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="2.928"
+     y="9.7259998"
+     id="text1880"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="5.725,19.819 5.725,18.237 5.732,18.237 5.732,17.325 "
+     id="polyline1882"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="1.317"
+     y="15.131"
+     id="text1884"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">1100 Users</text>
+  <text
+     x="1.136"
+     y="6.0770001"
+     id="text1886"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">320 Users</text>
+  <text
+     x="12.943"
+     y="6.0310001"
+     id="text1888"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">180 Users</text>
+  <text
+     x="12.383"
+     y="15.277"
+     id="text1890"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
+  <text
+     x="-9.8629999"
+     y="15.156"
+     id="text1892"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York - GNY</text>
+  <text
+     x="13.189"
+     y="0.46399999"
+     id="text1894"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Los Angeles</text>
+  <text
+     x="1.086"
+     y="0.53899997"
+     id="text1896"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">London</text>
+  <text
+     x="12.979"
+     y="8.0889997"
+     id="text1898"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Washington, DC</text>
+  <rect
+     width="11.132"
+     height="6.5630002"
+     x="-11.146"
+     y="16.205999"
+     id="rect1900"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
+     id="path1902"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
+     id="path1904"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.732"
+     height="5.9629998"
+     x="-11.446"
+     y="16.506001"
+     id="rect1906"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
+     id="path1908"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
+     id="path1910"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="-11.146"
+     y1="16.205999"
+     x2="-0.014"
+     y2="16.205999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1912"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.146"
+     y1="22.768999"
+     x2="-0.014"
+     y2="22.768999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1914"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
+     id="path1916"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
+     id="path1918"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.446"
+     y1="16.506001"
+     x2="-11.446"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1920"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.28600001"
+     y1="16.506001"
+     x2="0.28600001"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1922"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
+     id="path1924"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
+     id="path1926"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1928"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1930"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1932"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
+     id="path1934"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
+     id="path1936"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
+     id="polygon1938"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
+     id="polygon1940"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
+     id="polygon1942"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
+     id="polygon1944"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
+     id="path1946"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
+     id="path1948"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
+     id="polygon1950"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
+     id="polygon1952"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
+     id="polygon1954"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
+     id="polygon1956"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-5.2220001"
+     y="17.145"
+     id="text1958"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="-5.5609999"
+     y="17.745001"
+     id="text1960"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.4.0/22</text>
+  <text
+     x="-10.001"
+     y="21.07"
+     id="text1962"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="-10.37"
+     y="21.57"
+     id="text1964"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1966"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1968"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1970"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1972"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1974"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1976"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="19.087"
+     x2="-7.6300001"
+     y2="19.087"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1978"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.6300001"
+     y1="19.33"
+     x2="-8.6040001"
+     y2="19.33"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1980"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1982"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1984"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1986"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.665"
+     y1="20.181999"
+     x2="-7.448"
+     y2="20.181999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1988"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1990"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1992"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1994"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect1996"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect1998"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect2000"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2002"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2004"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2006"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2008"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2010"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2012"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4820004"
+     y1="19.816999"
+     x2="-7.8130002"
+     y2="19.816999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2014"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2016"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2018"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2020"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2022"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2024"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2026"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.695"
+     x2="-7.8740001"
+     y2="19.695"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2028"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2030"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2032"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2034"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.8130002"
+     y1="19.511999"
+     x2="-7.691"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2036"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.242001"
+     x2="-7.5089998"
+     y2="20.242001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2038"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.302999"
+     x2="-8.6040001"
+     y2="20.302999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2040"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.364"
+     x2="-7.5089998"
+     y2="20.364"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2042"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.547001"
+     x2="-8.6040001"
+     y2="20.547001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2044"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.486"
+     x2="-7.5089998"
+     y2="20.486"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2046"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.424999"
+     x2="-8.6040001"
+     y2="20.424999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2048"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5430002"
+     y1="19.511999"
+     x2="-8.4820004"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2050"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.511999"
+     x2="-8.3599997"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2052"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.756001"
+     x2="-8.3599997"
+     y2="19.756001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2054"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.9349999"
+     y1="19.756001"
+     x2="-7.8740001"
+     y2="19.756001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2056"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.4980001"
+     y1="19.695"
+     x2="-2.164"
+     y2="19.679001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2058"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.9559999"
+     y1="19.690001"
+     x2="-5.9530001"
+     y2="20.649"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2060"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.9530001"
+     y1="19.690001"
+     x2="-5.9559999"
+     y2="18.690001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2062"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-4.4590001"
+     y1="19.686001"
+     x2="-4.4559999"
+     y2="20.591"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2064"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-4.4569998"
+     y1="19.686001"
+     x2="-4.46"
+     y2="18.686001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2066"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-2.961"
+     y1="19.681"
+     x2="-2.9579999"
+     y2="20.608"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2068"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-2.9619999"
+     y1="19.681"
+     x2="-2.9649999"
+     y2="18.681"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2070"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.9439998"
+     y="20.618"
+     id="rect2072"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.9439998"
+     y="20.618"
+     id="rect2074"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-4.8470001"
+     y="20.715"
+     id="rect2076"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
+     id="polygon2078"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
+     id="polygon2080"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
+     id="polygon2082"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
+     id="polygon2084"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.3299999"
+     y="21.320999"
+     id="rect2086"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.3299999"
+     y="21.320999"
+     id="rect2088"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
+     id="polygon2090"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
+     id="polygon2092"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.4260001"
+     y="20.607"
+     id="rect2094"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.4260001"
+     y="20.607"
+     id="rect2096"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-3.329"
+     y="20.704"
+     id="rect2098"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
+     id="polygon2100"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
+     id="polygon2102"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
+     id="polygon2104"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
+     id="polygon2106"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.813"
+     y="21.311001"
+     id="rect2108"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.813"
+     y="21.311001"
+     id="rect2110"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
+     id="polygon2112"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
+     id="polygon2114"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-6.3759999"
+     y="18.181999"
+     id="rect2116"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-6.3759999"
+     y="18.181999"
+     id="rect2118"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-6.2789998"
+     y="18.278999"
+     id="rect2120"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
+     id="polygon2122"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
+     id="polygon2124"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
+     id="polygon2126"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
+     id="polygon2128"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-5.763"
+     y="18.886"
+     id="rect2130"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-5.763"
+     y="18.886"
+     id="rect2132"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
+     id="polygon2134"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
+     id="polygon2136"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.901"
+     y="18.181999"
+     id="rect2138"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.901"
+     y="18.181999"
+     id="rect2140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-4.8039999"
+     y="18.278999"
+     id="rect2142"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
+     id="polygon2144"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
+     id="polygon2146"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
+     id="polygon2148"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
+     id="polygon2150"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.2880001"
+     y="18.886"
+     id="rect2152"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.2880001"
+     y="18.886"
+     id="rect2154"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
+     id="polygon2156"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
+     id="polygon2158"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.401"
+     y="18.207001"
+     id="rect2160"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.401"
+     y="18.207001"
+     id="rect2162"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-3.3039999"
+     y="18.304001"
+     id="rect2164"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
+     id="polygon2166"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
+     id="polygon2168"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
+     id="polygon2170"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
+     id="polygon2172"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.7880001"
+     y="18.910999"
+     id="rect2174"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.7880001"
+     y="18.910999"
+     id="rect2176"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
+     id="polygon2178"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
+     id="polygon2180"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
+     id="polygon2182"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
+     id="polygon2184"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -6.607,21.174 L -6.559,21.194 L -5.503,21.194 L -5.455,21.174"
+     id="path2186"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -5.503,21.194 L -5.431,21.234"
+     id="path2188"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -6.631,21.234 L -6.559,21.194"
+     id="path2190"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
+     id="polygon2192"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
+     id="polygon2194"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
+     id="polygon2196"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
+     id="polygon2198"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2200"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2202"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2204"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2206"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2208"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2210"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2212"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2214"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2216"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2218"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2220"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2222"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2224"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2226"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2228"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2230"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2232"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2234"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2236"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2238"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2240"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2242"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2244"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2246"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.0310001"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2248"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-6.0310001"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2250"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-5.7309999"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2252"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-5.7309999"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2254"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.17"
+     height="1.033"
+     x="-10.59"
+     y="19.132"
+     id="rect2256"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="-10.004"
+     cy="20.165001"
+     rx="0.58499998"
+     ry="0.17200001"
+     id="ellipse2258"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="-10.004"
+     cy="19.132"
+     rx="0.58499998"
+     ry="0.17200001"
+     id="ellipse2260"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="-10.004"
+     cy="19.132"
+     rx="0.58499998"
+     ry="0.17200001"
+     id="ellipse2262"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -9.419,19.132 L -9.419,20.165 C -9.419,20.26 -9.681,20.337 -10.004,20.337 C -10.328,20.337 -10.59,20.26 -10.59,20.165 L -10.59,19.132"
+     id="path2264"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-9.3959999"
+     y1="19.684"
+     x2="-8.665"
+     y2="19.695"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2266"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-10.303"
+     y="19.759001"
+     id="text2268"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="-10.288"
+     y="20.159"
+     id="text2270"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <text
+     x="-0.91500002"
+     y="19.843"
+     id="text2272"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <text
+     x="-1.867"
+     y="22.455999"
+     id="text2274"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
+  <text
+     x="-10.478"
+     y="17.114"
+     id="text2276"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
+  <text
+     x="-10.081"
+     y="17.914"
+     id="text2278"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg2</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="-1.554,15.161 -1.554,15.906 -1.821,15.906 -1.821,19.285 "
+     id="polyline2280"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2282"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2284"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2286"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
+     id="path2288"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
+     id="path2290"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
+     id="polygon2292"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
+     id="polygon2294"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
+     id="polygon2296"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
+     id="polygon2298"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
+     id="path2300"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
+     id="path2302"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
+     id="polygon2304"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
+     id="polygon2306"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
+     id="polygon2308"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
+     id="polygon2310"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7.8559999"
+     y="17.167"
+     id="text2312"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="7.5180001"
+     y="17.767"
+     id="text2314"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.8.0/22</text>
+  <text
+     x="3.204"
+     y="18.118"
+     id="text2316"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="2.835"
+     y="18.618"
+     id="text2318"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-BDC</text>
+  <text
+     x="12.542"
+     y="19.694"
+     id="text2320"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="12.687"
+     y="20.194"
+     id="text2322"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-APPS</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2324"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2326"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2328"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2330"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2332"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2334"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="19.246"
+     x2="5.112"
+     y2="19.246"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2336"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.112"
+     y1="19.49"
+     x2="4.138"
+     y2="19.49"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2338"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2340"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2342"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2344"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.0770001"
+     y1="20.341"
+     x2="5.2940001"
+     y2="20.341"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2346"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2348"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2350"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2352"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2354"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2356"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2358"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2360"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2362"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2364"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2366"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2368"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2370"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.2600002"
+     y1="19.976"
+     x2="4.9289999"
+     y2="19.976"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2372"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2374"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2376"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2378"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2380"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2382"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2384"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.855"
+     x2="4.868"
+     y2="19.855"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2386"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2388"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2390"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2392"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.9289999"
+     y1="19.672001"
+     x2="5.0510001"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2394"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.402"
+     x2="5.2329998"
+     y2="20.402"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2396"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.462999"
+     x2="4.138"
+     y2="20.462999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2398"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.524"
+     x2="5.2329998"
+     y2="20.524"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2400"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.705999"
+     x2="4.138"
+     y2="20.705999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2402"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.645"
+     x2="5.2329998"
+     y2="20.645"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2404"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.584999"
+     x2="4.138"
+     y2="20.584999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2406"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.1989999"
+     y1="19.672001"
+     x2="4.2600002"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2408"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.672001"
+     x2="4.382"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2410"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.915001"
+     x2="4.382"
+     y2="19.915001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2412"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.8070002"
+     y1="19.915001"
+     x2="4.868"
+     y2="19.915001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2414"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.244"
+     y1="19.855"
+     x2="10.386"
+     y2="19.841999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2416"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.7309999"
+     y1="19.851"
+     x2="6.7329998"
+     y2="20.809999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2418"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.7350001"
+     y1="19.851"
+     x2="6.7319999"
+     y2="18.851"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2420"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.1739998"
+     y1="19.847"
+     x2="8.1759996"
+     y2="20.753"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2422"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.1750002"
+     y1="19.847"
+     x2="8.1730003"
+     y2="18.848"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2424"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.6169996"
+     y1="19.844"
+     x2="9.6190004"
+     y2="20.771"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2426"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.6160002"
+     y1="19.844"
+     x2="9.6129999"
+     y2="18.844"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2428"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.723"
+     y="20.778"
+     id="rect2430"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.723"
+     y="20.778"
+     id="rect2432"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.8210001"
+     y="20.875"
+     id="rect2434"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
+     id="polygon2436"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
+     id="polygon2438"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
+     id="polygon2440"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
+     id="polygon2442"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3369999"
+     y="21.481001"
+     id="rect2444"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3369999"
+     y="21.481001"
+     id="rect2446"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
+     id="polygon2448"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
+     id="polygon2450"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.1660004"
+     y="20.767"
+     id="rect2452"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.1660004"
+     y="20.767"
+     id="rect2454"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="9.2629995"
+     y="20.864"
+     id="rect2456"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
+     id="polygon2458"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
+     id="polygon2460"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
+     id="polygon2462"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
+     id="polygon2464"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.7790003"
+     y="21.469999"
+     id="rect2466"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.7790003"
+     y="21.469999"
+     id="rect2468"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
+     id="polygon2470"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
+     id="polygon2472"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.2909999"
+     y="18.341999"
+     id="rect2474"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.2909999"
+     y="18.341999"
+     id="rect2476"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.388"
+     y="18.438999"
+     id="rect2478"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
+     id="polygon2480"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
+     id="polygon2482"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
+     id="polygon2484"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
+     id="polygon2486"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.9039998"
+     y="19.045"
+     id="rect2488"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.9039998"
+     y="19.045"
+     id="rect2490"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
+     id="polygon2492"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
+     id="polygon2494"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.7410002"
+     y="18.367001"
+     id="rect2496"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.7410002"
+     y="18.367001"
+     id="rect2498"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.8379998"
+     y="18.464001"
+     id="rect2500"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
+     id="polygon2502"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
+     id="polygon2504"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
+     id="polygon2506"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
+     id="polygon2508"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3540001"
+     y="19.07"
+     id="rect2510"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3540001"
+     y="19.07"
+     id="rect2512"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
+     id="polygon2514"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
+     id="polygon2516"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.191"
+     y="18.341999"
+     id="rect2518"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.191"
+     y="18.341999"
+     id="rect2520"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="9.2880001"
+     y="18.438999"
+     id="rect2522"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
+     id="polygon2524"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
+     id="polygon2526"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
+     id="polygon2528"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
+     id="polygon2530"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.8039999"
+     y="19.045"
+     id="rect2532"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.8039999"
+     y="19.045"
+     id="rect2534"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
+     id="polygon2536"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
+     id="polygon2538"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
+     id="polygon2540"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
+     id="polygon2542"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 6.135,21.334 L 6.183,21.354 L 7.239,21.354 L 7.287,21.334"
+     id="path2544"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.239,21.354 L 7.311,21.394"
+     id="path2546"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 6.111,21.394 L 6.183,21.354"
+     id="path2548"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
+     id="polygon2550"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
+     id="polygon2552"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
+     id="polygon2554"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
+     id="polygon2556"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2558"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2560"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2562"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2564"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2566"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2568"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2570"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2572"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2574"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2576"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2578"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2580"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2582"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2584"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2586"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2588"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2590"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2592"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2594"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2596"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2598"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2600"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2602"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2604"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.711"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2606"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="6.711"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2608"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.0110002"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2610"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="7.0110002"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2612"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2614"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2616"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2618"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2620"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2622"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2624"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.533"
+     y1="19.048"
+     x2="10.618"
+     y2="19.048"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2626"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.618"
+     y1="19.275999"
+     x2="11.533"
+     y2="19.275999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2628"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.533"
+     y1="19.448"
+     x2="10.618"
+     y2="19.448"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2630"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2632"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2634"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2636"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.504"
+     y1="20.249001"
+     x2="11.647"
+     y2="20.249001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2638"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2640"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2642"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2644"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2646"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2648"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2650"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2652"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2654"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2656"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2658"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2660"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2662"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.618"
+     y1="20.02"
+     x2="11.247"
+     y2="20.02"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2664"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2666"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2668"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2670"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2672"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2674"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2676"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.906"
+     x2="11.19"
+     y2="19.906"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2678"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.19"
+     y1="19.962999"
+     x2="11.133"
+     y2="19.962999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2680"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.962999"
+     x2="10.732"
+     y2="19.962999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2682"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2684"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2686"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2688"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.620001"
+     x2="10.732"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2690"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.79"
+     y1="19.620001"
+     x2="10.847"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.362"
+     y1="19.620001"
+     x2="11.476"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.934999"
+     x2="10.561"
+     y2="20.934999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.878"
+     x2="11.59"
+     y2="20.878"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2698"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.820999"
+     x2="10.561"
+     y2="20.820999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2700"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.763"
+     x2="11.59"
+     y2="20.763"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2702"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.705999"
+     x2="10.561"
+     y2="20.705999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2704"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.649"
+     x2="11.59"
+     y2="20.649"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2706"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.591999"
+     x2="10.561"
+     y2="20.591999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2708"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.4960001"
+     y1="19.819"
+     x2="4.0770001"
+     y2="19.855"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2710"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.183"
+     height="1.044"
+     x="2.302"
+     y="19.268999"
+     id="rect2712"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="2.8940001"
+     cy="20.312"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2714"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="2.8940001"
+     cy="19.268999"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2716"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="2.8940001"
+     cy="19.268999"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2718"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.485,19.269 L 3.485,20.312 C 3.485,20.409 3.221,20.486 2.894,20.486 C 2.567,20.486 2.302,20.409 2.302,20.312 L 2.302,19.269"
+     id="path2720"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.589"
+     y="19.868999"
+     id="text2722"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="2.6040001"
+     y="20.268999"
+     id="text2724"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <text
+     x="12.947"
+     y="22.452"
+     id="text2726"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">250 Users</text>
+  <text
+     x="12.072"
+     y="17.239"
+     id="text2728"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
+  <text
+     x="12.468"
+     y="18.039"
+     id="text2730"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg3</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="-1.129,15.125 -1.129,15.903 5.732,15.903 5.732,16.538 "
+     id="polyline2732"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.1"
+     y1="22.393"
+     x2="15.55"
+     y2="23.143"
+     stroke="#F7F7F7"
+     stroke-width="0.100"
+     id="line2734"
+     style="stroke:#f7f7f7;stroke-width:0.1" />
+  <text
+     x="-10.033"
+     y="7.8769999"
+     id="text2736"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="-10.108"
+     y="22.502001"
+     id="text2738"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="2.5420001"
+     y="22.502001"
+     id="text2740"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="7.355"
+     y="0.40200001"
+     id="text2742"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: UKNET</text>
+  <text
+     x="18.438999"
+     y="0.40200001"
+     id="text2744"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: WESTNET</text>
+  <text
+     x="18.017"
+     y="15.202"
+     id="text2746"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="-10.507"
+     y="0.49399999"
+     id="text2748"
+     style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Notes:</text>
+  <text
+     x="-11.175"
+     y="1.294"
+     id="text2750"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">The decision was made to implement separate</text>
+  <text
+     x="-11.175"
+     y="1.794"
+     id="text2752"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">domains for the West Coast and for UK</text>
+  <text
+     x="-11.175"
+     y="2.2939999"
+     id="text2754"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">operations. Wide-area traffic will be reduced.</text>
+  <text
+     x="-11.175"
+     y="3.2939999"
+     id="text2756"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">This design introduces the concept of deploying</text>
+  <text
+     x="-11.175"
+     y="3.7939999"
+     id="text2758"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">interdomain trusts, thus permitting much needed</text>
+  <text
+     x="-11.175"
+     y="4.2940001"
+     id="text2760"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">network integration and interoperabilty.</text>
+  <text
+     x="-11.175"
+     y="5.2940001"
+     id="text2762"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">There is a single LDAP Master and at least one</text>
+  <text
+     x="-11.175"
+     y="5.7940001"
+     id="text2764"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave LDAP server in each remote office.</text>
+  <text
+     x="-11.175"
+     y="6.2940001"
+     id="text2766"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial" />
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap7-net2-Br.png b/docs-xml/Samba3-ByExample/images/chap7-net2-Br.png
new file mode 100644
index 00000000000..a75a47dc5d0
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap7-net2-Br.png
diff --git a/docs-xml/Samba3-ByExample/images/chap7-net2.svg b/docs-xml/Samba3-ByExample/images/chap7-net2.svg
new file mode 100644
index 00000000000..1466498d62e
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap7-net2.svg
@@ -0,0 +1,9075 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="34.602001cm"
+   height="23.67cm"
+   viewBox="-11.55 -0.456 23.052 23.213"
+   id="svg2">
+  <defs
+     id="defs2765" />
+  <rect
+     width="13.8"
+     height="6.513"
+     x="1.375"
+     y="16.256001"
+     id="rect4"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
+     id="path6"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
+     id="path8"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="14.4"
+     height="5.9130001"
+     x="1.075"
+     y="16.556"
+     id="rect10"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
+     id="path12"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
+     id="path14"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="1.375"
+     y1="16.256001"
+     x2="15.175"
+     y2="16.256001"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.375"
+     y1="22.768999"
+     x2="15.175"
+     y2="22.768999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.075"
+     y1="16.556"
+     x2="1.075"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="15.475"
+     y1="16.556"
+     x2="15.475"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.617"
+     height="6.8530002"
+     x="0.495"
+     y="-0.40599999"
+     id="rect32"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
+     id="path34"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
+     id="path36"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.217"
+     height="6.2529998"
+     x="0.19499999"
+     y="-0.106"
+     id="rect38"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
+     id="path40"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
+     id="path42"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="0.495"
+     y1="-0.40599999"
+     x2="11.112"
+     y2="-0.40599999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line44"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.495"
+     y1="6.447"
+     x2="11.112"
+     y2="6.447"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
+     id="path50"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.19499999"
+     y1="-0.106"
+     x2="0.19499999"
+     y2="6.1469998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.412"
+     y1="-0.106"
+     x2="11.412"
+     y2="6.1469998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line54"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
+     id="path56"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
+     id="path58"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.337"
+     height="6.8600001"
+     x="12.35"
+     y="-0.43099999"
+     id="rect60"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
+     id="path62"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
+     id="path64"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="10.937"
+     height="6.2600002"
+     x="12.05"
+     y="-0.131"
+     id="rect66"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
+     id="path68"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
+     id="path70"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="12.35"
+     y1="-0.43099999"
+     x2="22.687"
+     y2="-0.43099999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.35"
+     y1="6.4289999"
+     x2="22.687"
+     y2="6.4289999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.05"
+     y1="-0.131"
+     x2="12.05"
+     y2="6.1290002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="22.987"
+     y1="-0.131"
+     x2="22.987"
+     y2="6.1290002"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
+     id="path84"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
+     id="path86"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="10.821"
+     height="8.375"
+     x="11.905"
+     y="7.244"
+     id="rect88"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
+     id="path90"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
+     id="path92"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.421"
+     height="7.7750001"
+     x="11.605"
+     y="7.5440001"
+     id="rect94"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
+     id="path96"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
+     id="path98"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="11.905"
+     y1="7.244"
+     x2="22.726999"
+     y2="7.244"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line100"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.905"
+     y1="15.619"
+     x2="22.726999"
+     y2="15.619"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line102"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
+     id="path104"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
+     id="path106"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="11.605"
+     y1="7.5440001"
+     x2="11.605"
+     y2="15.319"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line108"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="23.027"
+     y1="7.5440001"
+     x2="23.027"
+     y2="15.319"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line110"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
+     id="path112"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
+     id="path114"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="15.1"
+     height="8.3719997"
+     x="-11.225"
+     y="7.1339998"
+     id="rect116"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
+     id="path118"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 4.175,7.434 C 4.175,7.2683146 4.0406854,7.134 3.875,7.134"
+     id="path120"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="15.7"
+     height="7.7719998"
+     x="-11.525"
+     y="7.434"
+     id="rect122"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
+     id="path124"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 3.875,15.506 C 4.0406854,15.506 4.175,15.371685 4.175,15.206"
+     id="path126"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="-11.225"
+     y1="7.1339998"
+     x2="3.875"
+     y2="7.1339998"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line128"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.225"
+     y1="15.506"
+     x2="3.875"
+     y2="15.506"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line130"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
+     id="path132"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 4.175,7.434 C 4.175,7.2683146 4.0406854,7.134 3.875,7.134"
+     id="path134"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.525"
+     y1="7.434"
+     x2="-11.525"
+     y2="15.206"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="4.1750002"
+     y1="7.434"
+     x2="4.1750002"
+     y2="15.206"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
+     id="path140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 3.875,15.506 C 4.0406854,15.506 4.175,15.371685 4.175,15.206"
+     id="path142"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="1.95"
+     y1="11.168"
+     x2="4.8109999"
+     y2="11.165"
+     stroke="#000000"
+     stroke-width="0.300"
+     id="line144"
+     style="stroke:#000000;stroke-width:0.30000001" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="4.145,2.624 4.145,6.819 5.675,6.819 5.675,9.944 "
+     id="polyline146"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="16.100,2.794 16.100,6.844 8.674,6.844 8.674,9.887 "
+     id="polyline148"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.98000002"
+     height="0.98000002"
+     x="-1.818"
+     y="14.136"
+     id="rect150"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.98000002"
+     height="0.98000002"
+     x="-1.818"
+     y="14.136"
+     id="rect152"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.98000002"
+     height="0.98000002"
+     x="-1.818"
+     y="14.136"
+     id="rect154"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
+     id="path156"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
+     id="path158"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
+     id="polygon160"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
+     id="polygon162"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
+     id="polygon164"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
+     id="polygon166"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
+     id="path168"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
+     id="path170"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
+     id="polygon172"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
+     id="polygon174"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
+     id="polygon176"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
+     id="polygon178"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-1.306"
+     y1="11.165"
+     x2="-1.3279999"
+     y2="14.136"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line180"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.71700001"
+     y="7.6999998"
+     id="text182"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="0.37799999"
+     y="8.1999998"
+     id="text184"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-PDC</text>
+  <line
+     x1="6.118"
+     y1="13.16"
+     x2="7.7179999"
+     y2="13.135"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.10,0.10"
+     id="line186"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <text
+     x="8.4429998"
+     y="13.325"
+     id="text188"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">= VPN</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="10.645,11.075 10.645,9.069 16.025,9.069 16.025,11.368 "
+     id="polyline190"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-3.0239999"
+     y="14.751"
+     id="text192"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <text
+     x="4.1469998"
+     y="17.031"
+     id="text194"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect196"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect198"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="2.553"
+     y="1.723"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect202"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect204"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="2.6140001"
+     y="1.784"
+     id="rect206"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="2.027"
+     x2="3.5869999"
+     y2="2.027"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line208"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.5869999"
+     y1="2.2709999"
+     x2="2.6140001"
+     y2="2.2709999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line210"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect212"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect214"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="2.7360001"
+     y="2.575"
+     id="rect216"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.553"
+     y1="3.122"
+     x2="3.77"
+     y2="3.122"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line218"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect220"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect222"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.405"
+     y="3.0009999"
+     id="rect224"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect226"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect228"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.527"
+     y="3.0009999"
+     id="rect230"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect232"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect234"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="3.648"
+     y="3.0009999"
+     id="rect236"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect238"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect240"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="3.5869999"
+     y="2.8180001"
+     id="rect242"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7360001"
+     y1="2.757"
+     x2="3.405"
+     y2="2.757"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line244"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect246"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect248"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="3.527"
+     y="2.575"
+     id="rect250"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect252"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect254"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="2.675"
+     y="2.332"
+     id="rect256"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.6359999"
+     x2="3.3440001"
+     y2="2.6359999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line258"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect260"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect262"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="2.918"
+     y="2.6359999"
+     id="rect264"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.405"
+     y1="2.4530001"
+     x2="3.527"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line266"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.1830001"
+     x2="3.7090001"
+     y2="3.1830001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line268"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.244"
+     x2="2.6140001"
+     y2="3.244"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line270"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.3050001"
+     x2="3.7090001"
+     y2="3.3050001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line272"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.487"
+     x2="2.6140001"
+     y2="3.487"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line274"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.6140001"
+     y1="3.427"
+     x2="3.7090001"
+     y2="3.427"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line276"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.7090001"
+     y1="3.3659999"
+     x2="2.6140001"
+     y2="3.3659999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line278"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.675"
+     y1="2.4530001"
+     x2="2.7360001"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line280"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.4530001"
+     x2="2.8570001"
+     y2="2.4530001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line282"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7969999"
+     y1="2.697"
+     x2="2.8570001"
+     y2="2.697"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line284"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.283"
+     y1="2.697"
+     x2="3.3440001"
+     y2="2.697"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line286"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.72"
+     y1="2.6359999"
+     x2="8.8620005"
+     y2="2.6229999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line288"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.2069998"
+     y1="2.632"
+     x2="5.2090001"
+     y2="3.5910001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line290"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="5.21"
+     y1="2.632"
+     x2="5.2080002"
+     y2="1.632"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line292"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.6500001"
+     y1="2.6289999"
+     x2="6.652"
+     y2="3.5339999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line294"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.651"
+     y1="2.6289999"
+     x2="6.6479998"
+     y2="1.6289999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line296"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.092"
+     y1="2.625"
+     x2="8.0950003"
+     y2="3.552"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line298"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.0909996"
+     y1="2.625"
+     x2="8.0889997"
+     y2="1.625"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line300"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.1989999"
+     y="3.559"
+     id="rect302"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.1989999"
+     y="3.559"
+     id="rect304"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.296"
+     y="3.6559999"
+     id="rect306"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
+     id="polygon308"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
+     id="polygon310"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
+     id="polygon312"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
+     id="polygon314"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8130002"
+     y="4.2620001"
+     id="rect316"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8130002"
+     y="4.2620001"
+     id="rect318"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
+     id="polygon320"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
+     id="polygon322"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6420002"
+     y="3.5480001"
+     id="rect324"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6420002"
+     y="3.5480001"
+     id="rect326"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.7389998"
+     y="3.645"
+     id="rect328"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
+     id="polygon330"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
+     id="polygon332"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
+     id="polygon334"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
+     id="polygon336"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2550001"
+     y="4.2509999"
+     id="rect338"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2550001"
+     y="4.2509999"
+     id="rect340"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
+     id="polygon342"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
+     id="polygon344"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="4.7670002"
+     y="1.123"
+     id="rect346"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="4.7670002"
+     y="1.123"
+     id="rect348"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="4.8639998"
+     y="1.22"
+     id="rect350"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
+     id="polygon352"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
+     id="polygon354"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
+     id="polygon356"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
+     id="polygon358"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="5.3800001"
+     y="1.826"
+     id="rect360"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="5.3800001"
+     y="1.826"
+     id="rect362"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
+     id="polygon364"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
+     id="polygon366"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.217"
+     y="1.148"
+     id="rect368"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.217"
+     y="1.148"
+     id="rect370"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.3140001"
+     y="1.245"
+     id="rect372"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
+     id="polygon374"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
+     id="polygon376"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
+     id="polygon378"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
+     id="polygon380"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8299999"
+     y="1.851"
+     id="rect382"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.8299999"
+     y="1.851"
+     id="rect384"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
+     id="polygon386"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
+     id="polygon388"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6669998"
+     y="1.123"
+     id="rect390"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.6669998"
+     y="1.123"
+     id="rect392"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.7639999"
+     y="1.22"
+     id="rect394"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
+     id="polygon396"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
+     id="polygon398"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
+     id="polygon400"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
+     id="polygon402"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2799997"
+     y="1.826"
+     id="rect404"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.2799997"
+     y="1.826"
+     id="rect406"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
+     id="polygon408"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
+     id="polygon410"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
+     id="polygon412"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
+     id="polygon414"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.611,4.115 L 4.659,4.135 L 5.715,4.135 L 5.763,4.115"
+     id="path416"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 5.715,4.135 L 5.787,4.175"
+     id="path418"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 4.587,4.175 L 4.659,4.135"
+     id="path420"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
+     id="polygon422"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
+     id="polygon424"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
+     id="polygon426"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
+     id="polygon428"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse430"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse432"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse434"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse436"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse438"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2049999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse440"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse442"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse444"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse446"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse448"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse450"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.2550001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse452"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse454"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse456"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse458"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse460"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse462"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.3049998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse464"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse466"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.8270001"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse468"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="4.947"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse470"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="4.947"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse472"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse474"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="5.0669999"
+     cy="4.355"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse476"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.1869998"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse478"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="5.1869998"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse480"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="5.487"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse482"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="5.487"
+     cy="4.2150002"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse484"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect486"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect488"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="8.9790001"
+     y="1.4859999"
+     id="rect490"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect492"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect494"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="9.0939999"
+     y="1.6"
+     id="rect496"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.009"
+     y1="1.829"
+     x2="9.0939999"
+     y2="1.829"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line498"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0939999"
+     y1="2.0580001"
+     x2="10.009"
+     y2="2.0580001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line500"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.009"
+     y1="2.2290001"
+     x2="9.0939999"
+     y2="2.2290001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line502"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect504"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect506"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="9.0939999"
+     y="2.6289999"
+     id="rect508"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.9790001"
+     y1="3.03"
+     x2="10.123"
+     y2="3.03"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line510"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect512"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect514"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.4940004"
+     y="3.1440001"
+     id="rect516"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect518"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect520"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.7229996"
+     y="3.1440001"
+     id="rect522"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect524"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect526"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="9.9519997"
+     y="3.1440001"
+     id="rect528"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect530"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect532"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="9.8950005"
+     y="2.8010001"
+     id="rect534"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0939999"
+     y1="2.8010001"
+     x2="9.7229996"
+     y2="2.8010001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line536"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect538"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect540"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="9.0939999"
+     y="3.0869999"
+     id="rect542"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect544"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect546"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="9.151"
+     y="2.286"
+     id="rect548"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.687"
+     x2="9.6660004"
+     y2="2.687"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line550"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.6660004"
+     y1="2.744"
+     x2="9.6090002"
+     y2="2.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line552"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.744"
+     x2="9.2080002"
+     y2="2.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line554"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect556"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect558"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="9.2650003"
+     y="2.687"
+     id="rect560"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.151"
+     y1="2.401"
+     x2="9.2080002"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line562"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.2650003"
+     y1="2.401"
+     x2="9.323"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line564"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.8369999"
+     y1="2.401"
+     x2="9.9519997"
+     y2="2.401"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line566"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.7160001"
+     x2="9.0369997"
+     y2="3.7160001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line568"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.6589999"
+     x2="10.066"
+     y2="3.6589999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line570"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.602"
+     x2="9.0369997"
+     y2="3.602"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line572"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.5439999"
+     x2="10.066"
+     y2="3.5439999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line574"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.487"
+     x2="9.0369997"
+     y2="3.487"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line576"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.0369997"
+     y1="3.4300001"
+     x2="10.066"
+     y2="3.4300001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line578"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.066"
+     y1="3.3729999"
+     x2="9.0369997"
+     y2="3.3729999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line580"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="5.9629998"
+     y="5.2589998"
+     id="text582"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="5.5580001"
+     y="5.8590002"
+     id="text584"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.12.0/22</text>
+  <text
+     x="1.234"
+     y="4.1529999"
+     id="text586"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="1.053"
+     y="4.6529999"
+     id="text588"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-BDC</text>
+  <text
+     x="9.3100004"
+     y="0.375"
+     id="text590"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="9.1300001"
+     y="0.875"
+     id="text592"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-PDC</text>
+  <rect
+     width="1.291"
+     height="1.1390001"
+     x="0.61699998"
+     y="2.0880001"
+     id="rect594"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="1.263"
+     cy="3.227"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse596"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.263"
+     cy="2.0880001"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse598"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="1.263"
+     cy="2.0880001"
+     rx="0.64499998"
+     ry="0.19"
+     id="ellipse600"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 1.908,2.088 L 1.908,3.227 C 1.908,3.332 1.619,3.417 1.263,3.417 C 0.906,3.417 0.617,3.332 0.617,3.227 L 0.617,2.088"
+     id="path602"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="1.928"
+     y1="2.523"
+     x2="2.503"
+     y2="2.523"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line604"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.935"
+     y="2.7219999"
+     id="text606"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="0.94999999"
+     y="3.122"
+     id="text608"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect610"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect612"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.397"
+     y="1.885"
+     id="rect614"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect616"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect618"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.458"
+     y="1.946"
+     id="rect620"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="2.1900001"
+     x2="15.431"
+     y2="2.1900001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line622"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="2.4330001"
+     x2="14.458"
+     y2="2.4330001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line624"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect626"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect628"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.58"
+     y="2.737"
+     id="rect630"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.397"
+     y1="3.2850001"
+     x2="15.614"
+     y2="3.2850001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line632"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect634"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect636"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="3.1630001"
+     id="rect638"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect640"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect642"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.371"
+     y="3.1630001"
+     id="rect644"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect646"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect648"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.492"
+     y="3.1630001"
+     id="rect650"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect652"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect654"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.431"
+     y="2.98"
+     id="rect656"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.58"
+     y1="2.9200001"
+     x2="15.249"
+     y2="2.9200001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line658"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect660"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect662"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.183"
+     x="15.371"
+     y="2.737"
+     id="rect664"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect666"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect668"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.519"
+     y="2.494"
+     id="rect670"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.7980001"
+     x2="15.188"
+     y2="2.7980001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line672"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect674"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect676"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.762"
+     y="2.7980001"
+     id="rect678"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.249"
+     y1="2.615"
+     x2="15.371"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line680"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.345"
+     x2="15.553"
+     y2="3.345"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line682"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.4059999"
+     x2="14.458"
+     y2="3.4059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line684"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.467"
+     x2="15.553"
+     y2="3.467"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line686"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.6500001"
+     x2="14.458"
+     y2="3.6500001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line688"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="3.589"
+     x2="15.553"
+     y2="3.589"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line690"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.553"
+     y1="3.5280001"
+     x2="14.458"
+     y2="3.5280001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="2.615"
+     x2="14.58"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.615"
+     x2="14.701"
+     y2="2.615"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.641"
+     y1="2.859"
+     x2="14.701"
+     y2="2.859"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line698"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.127"
+     y1="2.859"
+     x2="15.188"
+     y2="2.859"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line700"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.564"
+     y1="2.7980001"
+     x2="20.705"
+     y2="2.7850001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line702"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.051001"
+     y1="2.7939999"
+     x2="17.052999"
+     y2="3.753"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line704"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="17.054001"
+     y1="2.7939999"
+     x2="17.052"
+     y2="1.794"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line706"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.493"
+     y1="2.7909999"
+     x2="18.496"
+     y2="3.6960001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line708"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.495001"
+     y1="2.7909999"
+     x2="18.492001"
+     y2="1.791"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line710"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.936001"
+     y1="2.7869999"
+     x2="19.938999"
+     y2="3.714"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line712"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.934999"
+     y1="2.7869999"
+     x2="19.933001"
+     y2="1.7869999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line714"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.042999"
+     y="3.721"
+     id="rect716"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.042999"
+     y="3.721"
+     id="rect718"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.139999"
+     y="3.8180001"
+     id="rect720"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
+     id="polygon722"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
+     id="polygon724"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
+     id="polygon726"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
+     id="polygon728"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.657"
+     y="4.4239998"
+     id="rect730"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.657"
+     y="4.4239998"
+     id="rect732"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
+     id="polygon734"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
+     id="polygon736"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.486"
+     y="3.71"
+     id="rect738"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.486"
+     y="3.71"
+     id="rect740"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.583"
+     y="3.8069999"
+     id="rect742"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
+     id="polygon744"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
+     id="polygon746"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
+     id="polygon748"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
+     id="polygon750"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.099001"
+     y="4.414"
+     id="rect752"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.099001"
+     y="4.414"
+     id="rect754"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
+     id="polygon756"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
+     id="polygon758"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.611"
+     y="1.285"
+     id="rect760"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.611"
+     y="1.285"
+     id="rect762"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="16.708"
+     y="1.382"
+     id="rect764"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
+     id="polygon766"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
+     id="polygon768"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
+     id="polygon770"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
+     id="polygon772"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.224001"
+     y="1.989"
+     id="rect774"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.224001"
+     y="1.989"
+     id="rect776"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
+     id="polygon778"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
+     id="polygon780"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.061001"
+     y="1.3099999"
+     id="rect782"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="18.061001"
+     y="1.3099999"
+     id="rect784"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.158001"
+     y="1.4069999"
+     id="rect786"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
+     id="polygon788"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
+     id="polygon790"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
+     id="polygon792"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
+     id="polygon794"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.674"
+     y="2.0139999"
+     id="rect796"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.674"
+     y="2.0139999"
+     id="rect798"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
+     id="polygon800"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
+     id="polygon802"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.511"
+     y="1.285"
+     id="rect804"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.511"
+     y="1.285"
+     id="rect806"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.608"
+     y="1.382"
+     id="rect808"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
+     id="polygon810"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
+     id="polygon812"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
+     id="polygon814"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
+     id="polygon816"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.124001"
+     y="1.989"
+     id="rect818"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.124001"
+     y="1.989"
+     id="rect820"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
+     id="polygon822"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
+     id="polygon824"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
+     id="polygon826"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
+     id="polygon828"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.454,4.277 L 16.502,4.297 L 17.558,4.297 L 17.606,4.277"
+     id="path830"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 17.558,4.297 L 17.63,4.337"
+     id="path832"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.43,4.337 L 16.502,4.297"
+     id="path834"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
+     id="polygon836"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
+     id="polygon838"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
+     id="polygon840"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
+     id="polygon842"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="16.67"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse844"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse846"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse848"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse850"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse852"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.3670001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse854"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse856"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse858"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse860"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse862"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse864"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.4169998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse866"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse868"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse870"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse872"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse874"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse876"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.467"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse878"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.67"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse880"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.67"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse882"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.790001"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse884"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.790001"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse886"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.91"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse888"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.91"
+     cy="4.5170002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse890"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.030001"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse892"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.030001"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse894"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.33"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse896"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.33"
+     cy="4.3769999"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse898"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect900"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect902"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="20.823"
+     y="1.648"
+     id="rect904"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect906"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect908"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.938"
+     y="1.762"
+     id="rect910"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.853001"
+     y1="1.9910001"
+     x2="20.938"
+     y2="1.9910001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line912"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.938"
+     y1="2.22"
+     x2="21.853001"
+     y2="2.22"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line914"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.853001"
+     y1="2.391"
+     x2="20.938"
+     y2="2.391"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line916"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect918"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect920"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.938"
+     y="2.7920001"
+     id="rect922"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.823"
+     y1="3.1919999"
+     x2="21.966999"
+     y2="3.1919999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line924"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect926"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect928"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.337999"
+     y="3.306"
+     id="rect930"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect932"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect934"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.566999"
+     y="3.306"
+     id="rect936"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect938"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect940"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.796"
+     y="3.306"
+     id="rect942"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect944"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect946"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.738001"
+     y="2.9630001"
+     id="rect948"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.938"
+     y1="2.9630001"
+     x2="21.566999"
+     y2="2.9630001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line950"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect952"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect954"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.938"
+     y="3.2490001"
+     id="rect956"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect958"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect960"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.995001"
+     y="2.448"
+     id="rect962"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.849"
+     x2="21.51"
+     y2="2.849"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line964"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.51"
+     y1="2.9059999"
+     x2="21.452"
+     y2="2.9059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line966"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.9059999"
+     x2="21.052"
+     y2="2.9059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line968"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect970"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect972"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="21.108999"
+     y="2.849"
+     id="rect974"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.995001"
+     y1="2.563"
+     x2="21.052"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line976"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.108999"
+     y1="2.563"
+     x2="21.167"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line978"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.681"
+     y1="2.563"
+     x2="21.796"
+     y2="2.563"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line980"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.878"
+     x2="20.881001"
+     y2="3.878"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line982"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.8210001"
+     x2="21.91"
+     y2="3.8210001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line984"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.7639999"
+     x2="20.881001"
+     y2="3.7639999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line986"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.707"
+     x2="21.91"
+     y2="3.707"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line988"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.6489999"
+     x2="20.881001"
+     y2="3.6489999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line990"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.881001"
+     y1="3.592"
+     x2="21.91"
+     y2="3.592"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line992"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.91"
+     y1="3.5350001"
+     x2="20.881001"
+     y2="3.5350001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line994"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="18.056999"
+     y="5.3460002"
+     id="text996"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="17.650999"
+     y="5.9460001"
+     id="text998"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.16.0/22</text>
+  <text
+     x="14.353"
+     y="4.415"
+     id="text1000"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="14.288"
+     y="4.915"
+     id="text1002"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-BDC</text>
+  <text
+     x="21.162001"
+     y="0.80599999"
+     id="text1004"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="21.098"
+     y="1.306"
+     id="text1006"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-PDC</text>
+  <rect
+     width="1.326"
+     height="1.17"
+     x="12.426"
+     y="2.155"
+     id="rect1008"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="13.089"
+     cy="3.326"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1010"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.089"
+     cy="2.155"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1012"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="13.089"
+     cy="2.155"
+     rx="0.66299999"
+     ry="0.19499999"
+     id="ellipse1014"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 13.752,2.155 L 13.752,3.326 C 13.752,3.434 13.455,3.521 13.089,3.521 C 12.723,3.521 12.426,3.434 12.426,3.326 L 12.426,2.155"
+     id="path1016"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="13.775"
+     y1="2.6440001"
+     x2="14.372"
+     y2="2.648"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1018"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.734"
+     y="2.8369999"
+     id="text1020"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="12.748"
+     y="3.237"
+     id="text1022"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1024"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1026"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="14.275"
+     y="10.44"
+     id="rect1028"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1030"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1032"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="14.336"
+     y="10.501"
+     id="rect1034"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="10.744"
+     x2="15.309"
+     y2="10.744"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1036"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.309"
+     y1="10.988"
+     x2="14.336"
+     y2="10.988"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1038"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1040"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1042"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="14.458"
+     y="11.292"
+     id="rect1044"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.275"
+     y1="11.839"
+     x2="15.492"
+     y2="11.839"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1046"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1048"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1050"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.127"
+     y="11.718"
+     id="rect1052"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1054"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1056"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.249"
+     y="11.718"
+     id="rect1058"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1060"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1062"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="15.37"
+     y="11.718"
+     id="rect1064"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1066"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1068"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="15.309"
+     y="11.535"
+     id="rect1070"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.458"
+     y1="11.474"
+     x2="15.127"
+     y2="11.474"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1072"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1074"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1076"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.183"
+     height="0.182"
+     x="15.249"
+     y="11.292"
+     id="rect1078"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1080"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1082"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="14.397"
+     y="11.048"
+     id="rect1084"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.353"
+     x2="15.066"
+     y2="11.353"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1086"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1088"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1090"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="14.64"
+     y="11.353"
+     id="rect1092"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.127"
+     y1="11.17"
+     x2="15.249"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1094"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="11.9"
+     x2="15.431"
+     y2="11.9"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1096"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="11.961"
+     x2="14.336"
+     y2="11.961"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1098"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="12.022"
+     x2="15.431"
+     y2="12.022"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1100"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="12.204"
+     x2="14.336"
+     y2="12.204"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1102"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.336"
+     y1="12.143"
+     x2="15.431"
+     y2="12.143"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1104"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.431"
+     y1="12.083"
+     x2="14.336"
+     y2="12.083"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1106"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.397"
+     y1="11.17"
+     x2="14.458"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1108"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.17"
+     x2="14.579"
+     y2="11.17"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1110"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.519"
+     y1="11.413"
+     x2="14.579"
+     y2="11.413"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1112"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.005"
+     y1="11.413"
+     x2="15.066"
+     y2="11.413"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1114"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.442"
+     y1="11.353"
+     x2="20.584"
+     y2="11.34"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1116"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.929001"
+     y1="11.349"
+     x2="16.931"
+     y2="12.308"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1118"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.931999"
+     y1="11.349"
+     x2="16.93"
+     y2="10.349"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1120"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.372"
+     y1="11.345"
+     x2="18.374001"
+     y2="12.251"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1122"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.372999"
+     y1="11.345"
+     x2="18.370001"
+     y2="10.345"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1124"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.815001"
+     y1="11.342"
+     x2="19.816999"
+     y2="12.269"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1126"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="19.813"
+     y1="11.342"
+     x2="19.811001"
+     y2="10.342"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1128"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.921"
+     y="12.276"
+     id="rect1130"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.921"
+     y="12.276"
+     id="rect1132"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.018"
+     y="12.373"
+     id="rect1134"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
+     id="polygon1136"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
+     id="polygon1138"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
+     id="polygon1140"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
+     id="polygon1142"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.535"
+     y="12.979"
+     id="rect1144"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.535"
+     y="12.979"
+     id="rect1146"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
+     id="polygon1148"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
+     id="polygon1150"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.364"
+     y="12.265"
+     id="rect1152"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.364"
+     y="12.265"
+     id="rect1154"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.461"
+     y="12.362"
+     id="rect1156"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
+     id="polygon1158"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
+     id="polygon1160"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
+     id="polygon1162"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
+     id="polygon1164"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="19.976999"
+     y="12.968"
+     id="rect1166"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="19.976999"
+     y="12.968"
+     id="rect1168"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
+     id="polygon1170"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
+     id="polygon1172"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.489"
+     y="9.8400002"
+     id="rect1174"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="16.489"
+     y="9.8400002"
+     id="rect1176"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="16.586"
+     y="9.9370003"
+     id="rect1178"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
+     id="polygon1180"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
+     id="polygon1182"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
+     id="polygon1184"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
+     id="polygon1186"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.101999"
+     y="10.543"
+     id="rect1188"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="17.101999"
+     y="10.543"
+     id="rect1190"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
+     id="polygon1192"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
+     id="polygon1194"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.938999"
+     y="9.8649998"
+     id="rect1196"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="17.938999"
+     y="9.8649998"
+     id="rect1198"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="18.035999"
+     y="9.9619999"
+     id="rect1200"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
+     id="polygon1202"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
+     id="polygon1204"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
+     id="polygon1206"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
+     id="polygon1208"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.552"
+     y="10.568"
+     id="rect1210"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="18.552"
+     y="10.568"
+     id="rect1212"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
+     id="polygon1214"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
+     id="polygon1216"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.389"
+     y="9.8400002"
+     id="rect1218"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="19.389"
+     y="9.8400002"
+     id="rect1220"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="19.486"
+     y="9.9370003"
+     id="rect1222"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
+     id="polygon1224"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
+     id="polygon1226"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
+     id="polygon1228"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
+     id="polygon1230"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.002001"
+     y="10.543"
+     id="rect1232"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="20.002001"
+     y="10.543"
+     id="rect1234"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
+     id="polygon1236"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
+     id="polygon1238"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
+     id="polygon1240"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
+     id="polygon1242"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.333,12.832 L 16.381,12.852 L 17.437,12.852 L 17.485,12.832"
+     id="path1244"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 17.437,12.852 L 17.509,12.892"
+     id="path1246"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 16.309,12.892 L 16.381,12.852"
+     id="path1248"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
+     id="polygon1250"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
+     id="polygon1252"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
+     id="polygon1254"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
+     id="polygon1256"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="16.549"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1258"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1260"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1262"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1264"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1266"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="12.922"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1268"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1270"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1272"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1274"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1276"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1278"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="12.972"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1280"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1282"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1284"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1286"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1288"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1290"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="13.022"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1292"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.549"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1294"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.549"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1296"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.669001"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1298"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.669001"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1300"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.789"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1302"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="16.789"
+     cy="13.072"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1304"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="16.909"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1306"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="16.909"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1308"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="17.209"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1310"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="17.209"
+     cy="12.932"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse1312"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1314"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1316"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2869999"
+     x="20.701"
+     y="10.203"
+     id="rect1318"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1320"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1322"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="20.816"
+     y="10.317"
+     id="rect1324"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.731001"
+     y1="10.546"
+     x2="20.816"
+     y2="10.546"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1326"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.816"
+     y1="10.774"
+     x2="21.731001"
+     y2="10.774"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1328"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.731001"
+     y1="10.946"
+     x2="20.816"
+     y2="10.946"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1330"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1332"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1334"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="20.816"
+     y="11.346"
+     id="rect1336"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.701"
+     y1="11.747"
+     x2="21.844999"
+     y2="11.747"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1338"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1340"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1342"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.216"
+     y="11.861"
+     id="rect1344"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1346"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1348"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.445"
+     y="11.861"
+     id="rect1350"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1352"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1354"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="21.674"
+     y="11.861"
+     id="rect1356"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1358"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1360"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="21.615999"
+     y="11.518"
+     id="rect1362"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.816"
+     y1="11.518"
+     x2="21.445"
+     y2="11.518"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1364"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1366"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1368"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="20.816"
+     y="11.804"
+     id="rect1370"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1372"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1374"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="20.872999"
+     y="11.003"
+     id="rect1376"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.404"
+     x2="21.388"
+     y2="11.404"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1378"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.388"
+     y1="11.461"
+     x2="21.330999"
+     y2="11.461"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1380"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.461"
+     x2="20.93"
+     y2="11.461"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1382"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1384"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1386"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="20.987"
+     y="11.404"
+     id="rect1388"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.872999"
+     y1="11.118"
+     x2="20.93"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1390"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.987"
+     y1="11.118"
+     x2="21.045"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1392"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.559"
+     y1="11.118"
+     x2="21.674"
+     y2="11.118"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1394"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.433"
+     x2="20.759001"
+     y2="12.433"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1396"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.376"
+     x2="21.788"
+     y2="12.376"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1398"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.319"
+     x2="20.759001"
+     y2="12.319"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1400"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.261"
+     x2="21.788"
+     y2="12.261"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1402"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.204"
+     x2="20.759001"
+     y2="12.204"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1404"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.759001"
+     y1="12.147"
+     x2="21.788"
+     y2="12.147"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1406"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.788"
+     y1="12.09"
+     x2="20.759001"
+     y2="12.09"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1408"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="17.735001"
+     y="9.026"
+     id="text1410"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="17.301001"
+     y="9.6260004"
+     id="text1412"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.20.0/22</text>
+  <text
+     x="14.206"
+     y="12.995"
+     id="text1414"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="13.885"
+     y="13.495"
+     id="text1416"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WASH-BDC</text>
+  <text
+     x="20.912001"
+     y="13.518"
+     id="text1418"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="20.51"
+     y="14.018"
+     id="text1420"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WASH-APPS</text>
+  <rect
+     width="1.3150001"
+     height="1.161"
+     x="12"
+     y="10.659"
+     id="rect1422"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="12.658"
+     cy="11.819"
+     rx="0.65799999"
+     ry="0.193"
+     id="ellipse1424"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.658"
+     cy="10.659"
+     rx="0.65799999"
+     ry="0.193"
+     id="ellipse1426"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="12.658"
+     cy="10.659"
+     rx="0.65799999"
+     ry="0.193"
+     id="ellipse1428"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 13.316,10.659 L 13.316,11.819 C 13.316,11.926 13.021,12.013 12.658,12.013 C 12.295,12.013 12,11.926 12,11.819 L 12,10.659"
+     id="path1430"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="14.275"
+     y1="11.353"
+     x2="13.275"
+     y2="11.344"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1432"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.337"
+     y="11.292"
+     id="text1434"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="12.352"
+     y="11.692"
+     id="text1436"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <path
+     d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
+     id="path1438"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
+     id="path1440"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.7909999"
+     y="11.036"
+     id="text1442"
+     style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
+  <path
+     d="M 4.7,11.1 C 5.035363,11.196174 5.3953356,11.076093 5.6057965,10.797841 C 5.8162574,10.51959 5.8338243,10.140524 5.65,9.844"
+     id="path1444"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <path
+     d="M 8.675,9.794 C 7.4940305,10.104758 6.3530779,10.551408 5.275,11.125"
+     id="path1446"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <path
+     d="M 4.7,11.15 C 6.6098972,11.931939 8.7554368,11.904871 10.645,11.075"
+     id="path1448"
+     style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1450"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1452"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.397"
+     height="4.1900001"
+     x="0.61400002"
+     y="8.7200003"
+     id="rect1454"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1456"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1458"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.117"
+     height="1.676"
+     x="0.75400001"
+     y="8.8590002"
+     id="rect1460"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.1389999"
+     x2="1.8710001"
+     y2="9.1389999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1462"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.8710001"
+     y1="9.4180002"
+     x2="0.75400001"
+     y2="9.4180002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1464"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.698"
+     x2="1.8710001"
+     y2="9.698"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1466"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="9.9770002"
+     x2="1.8710001"
+     y2="9.9770002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1468"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.8710001"
+     y1="10.256"
+     x2="0.75400001"
+     y2="10.256"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1470"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1472"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1474"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.76800001"
+     height="0.419"
+     x="0.75400001"
+     y="10.675"
+     id="rect1476"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.61400002"
+     y1="11.374"
+     x2="2.0109999"
+     y2="11.374"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1478"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1480"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1482"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.243"
+     y="11.513"
+     id="rect1484"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1486"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1488"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.522"
+     y="11.513"
+     id="rect1490"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1492"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1494"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.07"
+     height="0.07"
+     x="1.801"
+     y="11.513"
+     id="rect1496"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1498"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1500"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.14"
+     height="0.14"
+     x="1.7309999"
+     y="11.094"
+     id="rect1502"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.75400001"
+     y1="10.885"
+     x2="1.522"
+     y2="10.885"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1504"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1506"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1508"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.20999999"
+     height="0.20999999"
+     x="0.75400001"
+     y="11.444"
+     id="rect1510"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1512"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1514"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97799999"
+     height="0.07"
+     x="0.82300001"
+     y="10.326"
+     id="rect1516"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.745"
+     x2="1.452"
+     y2="10.745"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1518"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.452"
+     y1="10.815"
+     x2="1.382"
+     y2="10.815"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1520"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.815"
+     x2="0.89300001"
+     y2="10.815"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1522"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1524"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1526"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.34900001"
+     height="0.07"
+     x="0.963"
+     y="10.745"
+     id="rect1528"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.82300001"
+     y1="10.466"
+     x2="0.89300001"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1530"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.963"
+     y1="10.466"
+     x2="1.033"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1532"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.6619999"
+     y1="10.466"
+     x2="1.801"
+     y2="10.466"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1534"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.84"
+     x2="1.941"
+     y2="12.84"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1536"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.77"
+     x2="0.68400002"
+     y2="12.77"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1538"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.701"
+     x2="1.941"
+     y2="12.701"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1540"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.631"
+     x2="0.68400002"
+     y2="12.631"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1542"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.561"
+     x2="1.941"
+     y2="12.561"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1544"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.491"
+     x2="0.68400002"
+     y2="12.491"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1546"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.421"
+     x2="1.941"
+     y2="12.421"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1548"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.351"
+     x2="0.68400002"
+     y2="12.351"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1550"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.282"
+     x2="1.941"
+     y2="12.282"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1552"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.212"
+     x2="0.68400002"
+     y2="12.212"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1554"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.142"
+     x2="1.941"
+     y2="12.142"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1556"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="12.072"
+     x2="0.68400002"
+     y2="12.072"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1558"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="0.68400002"
+     y1="12.002"
+     x2="1.941"
+     y2="12.002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1560"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.941"
+     y1="11.932"
+     x2="0.68400002"
+     y2="11.932"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1562"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.559"
+     y="12.296"
+     id="rect1564"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.559"
+     y="12.296"
+     id="rect1566"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-6.454"
+     y="12.401"
+     id="rect1568"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.427,13.024 -5.928,13.024 -5.928,13.137 -6.401,13.137 -6.427,13.024 "
+     id="polygon1570"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.427,13.024 -5.928,13.024 -5.928,13.137 -6.401,13.137 -6.427,13.024 "
+     id="polygon1572"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.928,13.024 -5.719,13.024 -5.746,13.137 -5.928,13.137 -5.928,13.024 "
+     id="polygon1574"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.928,13.024 -5.719,13.024 -5.746,13.137 -5.928,13.137 -5.928,13.024 "
+     id="polygon1576"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.8940001"
+     y="13.058"
+     id="rect1578"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.8940001"
+     y="13.058"
+     id="rect1580"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.17,13.137 -5.976,13.137 -5.976,13.194 -5.879,13.194 -5.879,13.25 -6.267,13.25 -6.267,13.194 -6.17,13.194 -6.17,13.137 "
+     id="polygon1582"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.17,13.137 -5.976,13.137 -5.976,13.194 -5.879,13.194 -5.879,13.25 -6.267,13.25 -6.267,13.194 -6.17,13.194 -6.17,13.137 "
+     id="polygon1584"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.653"
+     y1="11.13"
+     x2="-9.6660004"
+     y2="11.13"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1586"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-1.289"
+     y1="11.13"
+     x2="-1.289"
+     y2="10.145"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1588"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-3.766"
+     y1="11.13"
+     x2="-3.766"
+     y2="12.295"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1590"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-3.7739999"
+     y1="11.13"
+     x2="-3.7739999"
+     y2="10.099"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1592"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-6.0799999"
+     y1="11.13"
+     x2="-6.0799999"
+     y2="12.367"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1594"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-6.0939999"
+     y1="11.13"
+     x2="-6.0939999"
+     y2="10.063"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1596"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-8.4139996"
+     y1="11.13"
+     x2="-8.4139996"
+     y2="9.5740004"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1598"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.069"
+     height="0.80199999"
+     x="-4.289"
+     y="12.216"
+     id="rect1600"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.069"
+     height="0.80199999"
+     x="-4.289"
+     y="12.216"
+     id="rect1602"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.83700001"
+     height="0.55199999"
+     x="-4.1729999"
+     y="12.332"
+     id="rect1604"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.144,13.018 -3.594,13.018 -3.594,13.143 -4.115,13.143 -4.144,13.018 "
+     id="polygon1606"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.144,13.018 -3.594,13.018 -3.594,13.143 -4.115,13.143 -4.144,13.018 "
+     id="polygon1608"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-3.594,13.018 -3.365,13.018 -3.394,13.143 -3.594,13.143 -3.594,13.018 "
+     id="polygon1610"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.594,13.018 -3.365,13.018 -3.394,13.143 -3.594,13.143 -3.594,13.018 "
+     id="polygon1612"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.050000001"
+     height="0.050000001"
+     x="-3.5569999"
+     y="13.055"
+     id="rect1614"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.050000001"
+     height="0.050000001"
+     x="-3.5569999"
+     y="13.055"
+     id="rect1616"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.861,13.143 -3.648,13.143 -3.648,13.205 -3.541,13.205 -3.541,13.267 -3.968,13.267 -3.968,13.205 -3.861,13.205 -3.861,13.143 "
+     id="polygon1618"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.861,13.143 -3.648,13.143 -3.648,13.205 -3.541,13.205 -3.541,13.267 -3.968,13.267 -3.968,13.205 -3.861,13.205 -3.861,13.143 "
+     id="polygon1620"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.579"
+     y="9.1079998"
+     id="rect1622"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-6.579"
+     y="9.1079998"
+     id="rect1624"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-6.474"
+     y="9.2139997"
+     id="rect1626"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
+     id="polygon1628"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
+     id="polygon1630"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
+     id="polygon1632"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
+     id="polygon1634"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.914"
+     y="9.8710003"
+     id="rect1636"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-5.914"
+     y="9.8710003"
+     id="rect1638"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
+     id="polygon1640"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
+     id="polygon1642"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-4.2600002"
+     y="9.1450005"
+     id="rect1644"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-4.2600002"
+     y="9.1450005"
+     id="rect1646"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-4.1550002"
+     y="9.25"
+     id="rect1648"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
+     id="polygon1650"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
+     id="polygon1652"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
+     id="polygon1654"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
+     id="polygon1656"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-3.595"
+     y="9.9069996"
+     id="rect1658"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-3.595"
+     y="9.9069996"
+     id="rect1660"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
+     id="polygon1662"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
+     id="polygon1664"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-8.9029999"
+     y="9.0410004"
+     id="rect1666"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97100002"
+     height="0.72799999"
+     x="-8.9029999"
+     y="9.0410004"
+     id="rect1668"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.76099998"
+     height="0.50199997"
+     x="-8.7980003"
+     y="9.1470003"
+     id="rect1670"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
+     id="polygon1672"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
+     id="polygon1674"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
+     id="polygon1676"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
+     id="polygon1678"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-8.2379999"
+     y="9.8039999"
+     id="rect1680"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.045000002"
+     height="0.045000002"
+     x="-8.2379999"
+     y="9.8039999"
+     id="rect1682"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
+     id="polygon1684"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
+     id="polygon1686"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
+     id="polygon1688"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
+     id="polygon1690"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -1.871,9.841 L -1.823,9.861 L -0.754,9.861 L -0.706,9.841"
+     id="path1692"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -0.754,9.861 L -0.682,9.902"
+     id="path1694"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -1.895,9.902 L -1.823,9.861"
+     id="path1696"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
+     id="polygon1698"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
+     id="polygon1700"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
+     id="polygon1702"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
+     id="polygon1704"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1706"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1708"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1710"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1712"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1714"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9320002"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1716"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1718"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1720"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1722"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1724"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1726"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="9.9829998"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1728"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.653"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1730"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1732"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1734"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1736"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1738"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="10.033"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1740"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.653"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1742"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.653"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1744"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.531"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1746"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.531"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1748"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.41"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1750"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-1.41"
+     cy="10.084"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse1752"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-1.289"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1754"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-1.289"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1756"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-0.98500001"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1758"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-0.98500001"
+     cy="9.9420004"
+     rx="0.152"
+     ry="0.048999999"
+     id="ellipse1760"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.312"
+     height="2.625"
+     x="-11.059"
+     y="9.7469997"
+     id="rect1762"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.312"
+     height="2.625"
+     x="-11.059"
+     y="9.7469997"
+     id="rect1764"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.312"
+     height="2.625"
+     x="-11.059"
+     y="9.7469997"
+     id="rect1766"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.05"
+     height="1.05"
+     x="-10.928"
+     y="9.8780003"
+     id="rect1768"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.05"
+     height="1.05"
+     x="-10.928"
+     y="9.8780003"
+     id="rect1770"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.05"
+     height="1.05"
+     x="-10.928"
+     y="9.8780003"
+     id="rect1772"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8780003"
+     y1="10.141"
+     x2="-10.928"
+     y2="10.141"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1774"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.928"
+     y1="10.403"
+     x2="-9.8780003"
+     y2="10.403"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1776"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8780003"
+     y1="10.6"
+     x2="-10.928"
+     y2="10.6"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1778"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.722"
+     height="0.39399999"
+     x="-10.928"
+     y="11.06"
+     id="rect1780"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.722"
+     height="0.39399999"
+     x="-10.928"
+     y="11.06"
+     id="rect1782"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.722"
+     height="0.39399999"
+     x="-10.928"
+     y="11.06"
+     id="rect1784"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-11.059"
+     y1="11.519"
+     x2="-9.7460003"
+     y2="11.519"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1786"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.468"
+     y="11.65"
+     id="rect1788"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.468"
+     y="11.65"
+     id="rect1790"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.468"
+     y="11.65"
+     id="rect1792"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.206"
+     y="11.65"
+     id="rect1794"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.206"
+     y="11.65"
+     id="rect1796"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-10.206"
+     y="11.65"
+     id="rect1798"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-9.9429998"
+     y="11.65"
+     id="rect1800"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-9.9429998"
+     y="11.65"
+     id="rect1802"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.066"
+     height="0.066"
+     x="-9.9429998"
+     y="11.65"
+     id="rect1804"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.131"
+     height="0.066"
+     x="-10.009"
+     y="11.256"
+     id="rect1806"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.131"
+     height="0.066"
+     x="-10.009"
+     y="11.256"
+     id="rect1808"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.131"
+     height="0.066"
+     x="-10.009"
+     y="11.256"
+     id="rect1810"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.928"
+     y1="11.256"
+     x2="-10.206"
+     y2="11.256"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1812"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.197"
+     height="0.197"
+     x="-10.928"
+     y="11.585"
+     id="rect1814"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.197"
+     height="0.197"
+     x="-10.928"
+     y="11.585"
+     id="rect1816"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.197"
+     height="0.197"
+     x="-10.928"
+     y="11.585"
+     id="rect1818"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91900003"
+     height="0.066"
+     x="-10.862"
+     y="10.666"
+     id="rect1820"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91900003"
+     height="0.066"
+     x="-10.862"
+     y="10.666"
+     id="rect1822"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91900003"
+     height="0.066"
+     x="-10.862"
+     y="10.666"
+     id="rect1824"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.862"
+     y1="11.125"
+     x2="-10.271"
+     y2="11.125"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1826"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.271"
+     y1="11.191"
+     x2="-10.337"
+     y2="11.191"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1828"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.862"
+     y1="11.191"
+     x2="-10.796"
+     y2="11.191"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1830"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.32800001"
+     height="0.066"
+     x="-10.731"
+     y="11.125"
+     id="rect1832"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.32800001"
+     height="0.066"
+     x="-10.731"
+     y="11.125"
+     id="rect1834"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.32800001"
+     height="0.066"
+     x="-10.731"
+     y="11.125"
+     id="rect1836"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.862"
+     y1="10.797"
+     x2="-10.796"
+     y2="10.797"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1838"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.731"
+     y1="10.797"
+     x2="-10.665"
+     y2="10.797"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1840"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.074"
+     y1="10.797"
+     x2="-9.9429998"
+     y2="10.797"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1842"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="12.306"
+     x2="-10.993"
+     y2="12.306"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1844"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.993"
+     y1="12.241"
+     x2="-9.8120003"
+     y2="12.241"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1846"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="12.175"
+     x2="-10.993"
+     y2="12.175"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1848"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.993"
+     y1="12.11"
+     x2="-9.8120003"
+     y2="12.11"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1850"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="12.044"
+     x2="-10.993"
+     y2="12.044"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1852"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-10.993"
+     y1="11.978"
+     x2="-9.8120003"
+     y2="11.978"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1854"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-9.8120003"
+     y1="11.913"
+     x2="-10.993"
+     y2="11.913"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1856"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="-4.2459998"
+     y="8.2609997"
+     id="text1858"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="-4.5809999"
+     y="8.8610001"
+     id="text1860"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.0.0/22</text>
+  <text
+     x="-10.628"
+     y="13.181"
+     id="text1862"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="-10.454"
+     y="13.681"
+     id="text1864"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-APPS</text>
+  <rect
+     width="1.4450001"
+     height="1.275"
+     x="2.5510001"
+     y="8.6120005"
+     id="rect1866"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="3.273"
+     cy="9.8870001"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1868"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.273"
+     cy="8.6120005"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1870"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.273"
+     cy="8.6120005"
+     rx="0.72299999"
+     ry="0.213"
+     id="ellipse1872"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.996,8.612 L 3.996,9.887 C 3.996,10.005 3.672,10.1 3.273,10.1 C 2.874,10.1 2.551,10.005 2.551,9.887 L 2.551,8.612"
+     id="path1874"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="2.0109999"
+     y1="9.2469997"
+     x2="2.586"
+     y2="9.2469997"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line1876"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.983"
+     y="9.3260002"
+     id="text1878"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="2.928"
+     y="9.7259998"
+     id="text1880"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="5.725,19.819 5.725,18.237 5.732,18.237 5.732,17.325 "
+     id="polyline1882"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="1.317"
+     y="15.131"
+     id="text1884"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">1100 Users</text>
+  <text
+     x="1.136"
+     y="6.0770001"
+     id="text1886"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">320 Users</text>
+  <text
+     x="12.943"
+     y="6.0310001"
+     id="text1888"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">180 Users</text>
+  <text
+     x="12.383"
+     y="15.277"
+     id="text1890"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
+  <text
+     x="-9.9619999"
+     y="15.156"
+     id="text1892"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York - Bldg1</text>
+  <text
+     x="13.214"
+     y="0.46399999"
+     id="text1894"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Los Angeles</text>
+  <text
+     x="1.1109999"
+     y="0.46399999"
+     id="text1896"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">London</text>
+  <text
+     x="12.979"
+     y="8.0889997"
+     id="text1898"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Washington, DC</text>
+  <rect
+     width="11.132"
+     height="6.5630002"
+     x="-11.146"
+     y="16.205999"
+     id="rect1900"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
+     id="path1902"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
+     id="path1904"
+     style="fill:#ebebeb;stroke:none" />
+  <rect
+     width="11.732"
+     height="5.9629998"
+     x="-11.446"
+     y="16.506001"
+     id="rect1906"
+     style="fill:#ebebeb;stroke:none;stroke-width:0" />
+  <path
+     d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
+     id="path1908"
+     style="fill:#ebebeb;stroke:none" />
+  <path
+     d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
+     id="path1910"
+     style="fill:#ebebeb;stroke:none" />
+  <line
+     x1="-11.146"
+     y1="16.205999"
+     x2="-0.014"
+     y2="16.205999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1912"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.146"
+     y1="22.768999"
+     x2="-0.014"
+     y2="22.768999"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1914"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
+     id="path1916"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
+     id="path1918"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="-11.446"
+     y1="16.506001"
+     x2="-11.446"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1920"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="0.28600001"
+     y1="16.506001"
+     x2="0.28600001"
+     y2="22.469"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line1922"
+     style="stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
+     id="path1924"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <path
+     d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
+     id="path1926"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1928"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1930"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.78799999"
+     height="0.78799999"
+     x="-2.214"
+     y="19.285"
+     id="rect1932"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
+     id="path1934"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
+     id="path1936"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
+     id="polygon1938"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
+     id="polygon1940"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
+     id="polygon1942"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
+     id="polygon1944"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
+     id="path1946"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
+     id="path1948"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
+     id="polygon1950"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
+     id="polygon1952"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
+     id="polygon1954"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
+     id="polygon1956"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-5.2220001"
+     y="17.145"
+     id="text1958"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="-5.5609999"
+     y="17.745001"
+     id="text1960"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.4.0/22</text>
+  <text
+     x="-10.001"
+     y="21.07"
+     id="text1962"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="-10.37"
+     y="21.57"
+     id="text1964"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1966"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1968"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="-8.665"
+     y="18.782"
+     id="rect1970"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1972"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1974"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="-8.6040001"
+     y="18.843"
+     id="rect1976"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="19.087"
+     x2="-7.6300001"
+     y2="19.087"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1978"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.6300001"
+     y1="19.33"
+     x2="-8.6040001"
+     y2="19.33"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1980"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1982"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1984"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="-8.4820004"
+     y="19.634001"
+     id="rect1986"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.665"
+     y1="20.181999"
+     x2="-7.448"
+     y2="20.181999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line1988"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1990"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1992"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.8130002"
+     y="20.059999"
+     id="rect1994"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect1996"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect1998"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.691"
+     y="20.059999"
+     id="rect2000"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2002"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2004"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="-7.5700002"
+     y="20.059999"
+     id="rect2006"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2008"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2010"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="-7.6300001"
+     y="19.877001"
+     id="rect2012"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4820004"
+     y1="19.816999"
+     x2="-7.8130002"
+     y2="19.816999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2014"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2016"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2018"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="-7.691"
+     y="19.634001"
+     id="rect2020"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2022"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2024"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="-8.5430002"
+     y="19.391001"
+     id="rect2026"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.695"
+     x2="-7.8740001"
+     y2="19.695"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2028"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2030"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2032"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="-8.3000002"
+     y="19.695"
+     id="rect2034"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.8130002"
+     y1="19.511999"
+     x2="-7.691"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2036"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.242001"
+     x2="-7.5089998"
+     y2="20.242001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2038"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.302999"
+     x2="-8.6040001"
+     y2="20.302999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2040"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.364"
+     x2="-7.5089998"
+     y2="20.364"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2042"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.547001"
+     x2="-8.6040001"
+     y2="20.547001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2044"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.6040001"
+     y1="20.486"
+     x2="-7.5089998"
+     y2="20.486"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2046"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.5089998"
+     y1="20.424999"
+     x2="-8.6040001"
+     y2="20.424999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2048"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.5430002"
+     y1="19.511999"
+     x2="-8.4820004"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2050"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.511999"
+     x2="-8.3599997"
+     y2="19.511999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2052"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-8.4209995"
+     y1="19.756001"
+     x2="-8.3599997"
+     y2="19.756001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2054"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.9349999"
+     y1="19.756001"
+     x2="-7.8740001"
+     y2="19.756001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2056"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-7.4980001"
+     y1="19.695"
+     x2="-2.164"
+     y2="19.679001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2058"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.9559999"
+     y1="19.690001"
+     x2="-5.9530001"
+     y2="20.649"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2060"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-5.9530001"
+     y1="19.690001"
+     x2="-5.9559999"
+     y2="18.690001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2062"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-4.4590001"
+     y1="19.686001"
+     x2="-4.4559999"
+     y2="20.591"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2064"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-4.4569998"
+     y1="19.686001"
+     x2="-4.46"
+     y2="18.686001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2066"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-2.961"
+     y1="19.681"
+     x2="-2.9579999"
+     y2="20.608"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2068"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-2.9619999"
+     y1="19.681"
+     x2="-2.9649999"
+     y2="18.681"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2070"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.9439998"
+     y="20.618"
+     id="rect2072"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.9439998"
+     y="20.618"
+     id="rect2074"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-4.8470001"
+     y="20.715"
+     id="rect2076"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
+     id="polygon2078"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
+     id="polygon2080"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
+     id="polygon2082"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
+     id="polygon2084"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.3299999"
+     y="21.320999"
+     id="rect2086"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.3299999"
+     y="21.320999"
+     id="rect2088"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
+     id="polygon2090"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
+     id="polygon2092"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.4260001"
+     y="20.607"
+     id="rect2094"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.4260001"
+     y="20.607"
+     id="rect2096"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-3.329"
+     y="20.704"
+     id="rect2098"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
+     id="polygon2100"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
+     id="polygon2102"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
+     id="polygon2104"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
+     id="polygon2106"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.813"
+     y="21.311001"
+     id="rect2108"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.813"
+     y="21.311001"
+     id="rect2110"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
+     id="polygon2112"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
+     id="polygon2114"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-6.3759999"
+     y="18.181999"
+     id="rect2116"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-6.3759999"
+     y="18.181999"
+     id="rect2118"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-6.2789998"
+     y="18.278999"
+     id="rect2120"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
+     id="polygon2122"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
+     id="polygon2124"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
+     id="polygon2126"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
+     id="polygon2128"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-5.763"
+     y="18.886"
+     id="rect2130"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-5.763"
+     y="18.886"
+     id="rect2132"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
+     id="polygon2134"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
+     id="polygon2136"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.901"
+     y="18.181999"
+     id="rect2138"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-4.901"
+     y="18.181999"
+     id="rect2140"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-4.8039999"
+     y="18.278999"
+     id="rect2142"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
+     id="polygon2144"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
+     id="polygon2146"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
+     id="polygon2148"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
+     id="polygon2150"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.2880001"
+     y="18.886"
+     id="rect2152"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-4.2880001"
+     y="18.886"
+     id="rect2154"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
+     id="polygon2156"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
+     id="polygon2158"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.401"
+     y="18.207001"
+     id="rect2160"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="-3.401"
+     y="18.207001"
+     id="rect2162"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="-3.3039999"
+     y="18.304001"
+     id="rect2164"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
+     id="polygon2166"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
+     id="polygon2168"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
+     id="polygon2170"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
+     id="polygon2172"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.7880001"
+     y="18.910999"
+     id="rect2174"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="-2.7880001"
+     y="18.910999"
+     id="rect2176"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
+     id="polygon2178"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
+     id="polygon2180"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
+     id="polygon2182"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
+     id="polygon2184"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -6.607,21.174 L -6.559,21.194 L -5.503,21.194 L -5.455,21.174"
+     id="path2186"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -5.503,21.194 L -5.431,21.234"
+     id="path2188"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M -6.631,21.234 L -6.559,21.194"
+     id="path2190"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
+     id="polygon2192"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
+     id="polygon2194"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
+     id="polygon2196"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
+     id="polygon2198"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2200"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2202"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2204"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2206"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2208"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.264"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2210"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2212"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2214"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2216"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2218"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2220"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.313999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2222"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2224"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2226"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2228"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2230"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2232"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.364"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2234"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2236"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.3909998"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2238"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2240"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.2709999"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2242"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.151"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2244"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="-6.151"
+     cy="21.414"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2246"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-6.0310001"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2248"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-6.0310001"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2250"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="-5.7309999"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2252"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="-5.7309999"
+     cy="21.274"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2254"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.17"
+     height="1.033"
+     x="-10.59"
+     y="19.132"
+     id="rect2256"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="-10.004"
+     cy="20.165001"
+     rx="0.58499998"
+     ry="0.17200001"
+     id="ellipse2258"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="-10.004"
+     cy="19.132"
+     rx="0.58499998"
+     ry="0.17200001"
+     id="ellipse2260"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="-10.004"
+     cy="19.132"
+     rx="0.58499998"
+     ry="0.17200001"
+     id="ellipse2262"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M -9.419,19.132 L -9.419,20.165 C -9.419,20.26 -9.681,20.337 -10.004,20.337 C -10.328,20.337 -10.59,20.26 -10.59,20.165 L -10.59,19.132"
+     id="path2264"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="-9.3959999"
+     y1="19.684"
+     x2="-8.665"
+     y2="19.695"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2266"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-10.303"
+     y="19.759001"
+     id="text2268"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="-10.288"
+     y="20.159"
+     id="text2270"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <text
+     x="-0.91500002"
+     y="19.843"
+     id="text2272"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
+  <text
+     x="-1.867"
+     y="22.455999"
+     id="text2274"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
+  <text
+     x="-10.478"
+     y="17.114"
+     id="text2276"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
+  <text
+     x="-10.147"
+     y="17.914"
+     id="text2278"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg 2</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="-1.554,15.161 -1.554,15.906 -1.821,15.906 -1.821,19.285 "
+     id="polyline2280"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2282"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2284"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.787"
+     height="0.78799999"
+     x="5.3379998"
+     y="16.538"
+     id="rect2286"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
+     id="path2288"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
+     id="path2290"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
+     id="polygon2292"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
+     id="polygon2294"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
+     id="polygon2296"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
+     id="polygon2298"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
+     id="path2300"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
+     id="path2302"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
+     id="polygon2304"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
+     id="polygon2306"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
+     id="polygon2308"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
+     id="polygon2310"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7.8559999"
+     y="17.167"
+     id="text2312"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
+  <text
+     x="7.5180001"
+     y="17.767"
+     id="text2314"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.8.0/22</text>
+  <text
+     x="3.204"
+     y="18.118"
+     id="text2316"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
+  <text
+     x="2.835"
+     y="18.618"
+     id="text2318"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-BDC</text>
+  <text
+     x="12.542"
+     y="19.694"
+     id="text2320"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
+  <text
+     x="12.687"
+     y="20.194"
+     id="text2322"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-APPS</text>
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2324"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2326"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.217"
+     height="1.825"
+     x="4.0770001"
+     y="18.941999"
+     id="rect2328"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2330"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2332"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.97299999"
+     height="0.73000002"
+     x="4.138"
+     y="19.003"
+     id="rect2334"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="19.246"
+     x2="5.112"
+     y2="19.246"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2336"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.112"
+     y1="19.49"
+     x2="4.138"
+     y2="19.49"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2338"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2340"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2342"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.66900003"
+     height="0.36500001"
+     x="4.2600002"
+     y="19.794001"
+     id="rect2344"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.0770001"
+     y1="20.341"
+     x2="5.2940001"
+     y2="20.341"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2346"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2348"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2350"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="4.9289999"
+     y="20.219999"
+     id="rect2352"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2354"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2356"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.0510001"
+     y="20.219999"
+     id="rect2358"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2360"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2362"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.061000001"
+     height="0.061000001"
+     x="5.1719999"
+     y="20.219999"
+     id="rect2364"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2366"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2368"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.122"
+     height="0.122"
+     x="5.112"
+     y="20.037001"
+     id="rect2370"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.2600002"
+     y1="19.976"
+     x2="4.9289999"
+     y2="19.976"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2372"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2374"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2376"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.182"
+     height="0.183"
+     x="5.0510001"
+     y="19.794001"
+     id="rect2378"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2380"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2382"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.852"
+     height="0.061000001"
+     x="4.1989999"
+     y="19.549999"
+     id="rect2384"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.855"
+     x2="4.868"
+     y2="19.855"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2386"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2388"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2390"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.30399999"
+     height="0.061000001"
+     x="4.4419999"
+     y="19.855"
+     id="rect2392"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.9289999"
+     y1="19.672001"
+     x2="5.0510001"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2394"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.402"
+     x2="5.2329998"
+     y2="20.402"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2396"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.462999"
+     x2="4.138"
+     y2="20.462999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2398"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.524"
+     x2="5.2329998"
+     y2="20.524"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2400"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.705999"
+     x2="4.138"
+     y2="20.705999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2402"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.138"
+     y1="20.645"
+     x2="5.2329998"
+     y2="20.645"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2404"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.2329998"
+     y1="20.584999"
+     x2="4.138"
+     y2="20.584999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2406"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.1989999"
+     y1="19.672001"
+     x2="4.2600002"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2408"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.672001"
+     x2="4.382"
+     y2="19.672001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2410"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.3210001"
+     y1="19.915001"
+     x2="4.382"
+     y2="19.915001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2412"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.8070002"
+     y1="19.915001"
+     x2="4.868"
+     y2="19.915001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2414"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="5.244"
+     y1="19.855"
+     x2="10.386"
+     y2="19.841999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2416"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.7309999"
+     y1="19.851"
+     x2="6.7329998"
+     y2="20.809999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2418"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.7350001"
+     y1="19.851"
+     x2="6.7319999"
+     y2="18.851"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2420"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.1739998"
+     y1="19.847"
+     x2="8.1759996"
+     y2="20.753"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2422"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8.1750002"
+     y1="19.847"
+     x2="8.1730003"
+     y2="18.848"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2424"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.6169996"
+     y1="19.844"
+     x2="9.6190004"
+     y2="20.771"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2426"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.6160002"
+     y1="19.844"
+     x2="9.6129999"
+     y2="18.844"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2428"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.723"
+     y="20.778"
+     id="rect2430"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.723"
+     y="20.778"
+     id="rect2432"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.8210001"
+     y="20.875"
+     id="rect2434"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
+     id="polygon2436"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
+     id="polygon2438"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
+     id="polygon2440"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
+     id="polygon2442"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3369999"
+     y="21.481001"
+     id="rect2444"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3369999"
+     y="21.481001"
+     id="rect2446"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
+     id="polygon2448"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
+     id="polygon2450"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.1660004"
+     y="20.767"
+     id="rect2452"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.1660004"
+     y="20.767"
+     id="rect2454"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="9.2629995"
+     y="20.864"
+     id="rect2456"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
+     id="polygon2458"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
+     id="polygon2460"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
+     id="polygon2462"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
+     id="polygon2464"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.7790003"
+     y="21.469999"
+     id="rect2466"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.7790003"
+     y="21.469999"
+     id="rect2468"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
+     id="polygon2470"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
+     id="polygon2472"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.2909999"
+     y="18.341999"
+     id="rect2474"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="6.2909999"
+     y="18.341999"
+     id="rect2476"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="6.388"
+     y="18.438999"
+     id="rect2478"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
+     id="polygon2480"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
+     id="polygon2482"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
+     id="polygon2484"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
+     id="polygon2486"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.9039998"
+     y="19.045"
+     id="rect2488"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="6.9039998"
+     y="19.045"
+     id="rect2490"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
+     id="polygon2492"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
+     id="polygon2494"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.7410002"
+     y="18.367001"
+     id="rect2496"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="7.7410002"
+     y="18.367001"
+     id="rect2498"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="7.8379998"
+     y="18.464001"
+     id="rect2500"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
+     id="polygon2502"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
+     id="polygon2504"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
+     id="polygon2506"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
+     id="polygon2508"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3540001"
+     y="19.07"
+     id="rect2510"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="8.3540001"
+     y="19.07"
+     id="rect2512"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
+     id="polygon2514"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
+     id="polygon2516"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.191"
+     y="18.341999"
+     id="rect2518"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="0.89600003"
+     height="0.67199999"
+     x="9.191"
+     y="18.341999"
+     id="rect2520"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.70200002"
+     height="0.463"
+     x="9.2880001"
+     y="18.438999"
+     id="rect2522"
+     style="fill:#000000;stroke:none;stroke-width:0" />
+  <polygon
+     points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
+     id="polygon2524"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
+     id="polygon2526"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
+     id="polygon2528"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
+     id="polygon2530"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.8039999"
+     y="19.045"
+     id="rect2532"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.041999999"
+     height="0.041999999"
+     x="9.8039999"
+     y="19.045"
+     id="rect2534"
+     style="fill:none;stroke:#000000;stroke-width:0.025" />
+  <polygon
+     points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
+     id="polygon2536"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
+  <polygon
+     points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
+     id="polygon2538"
+     style="fill:none;stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
+     id="polygon2540"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
+     id="polygon2542"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 6.135,21.334 L 6.183,21.354 L 7.239,21.354 L 7.287,21.334"
+     id="path2544"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 7.239,21.354 L 7.311,21.394"
+     id="path2546"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <path
+     d="M 6.111,21.394 L 6.183,21.354"
+     id="path2548"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
+     id="polygon2550"
+     style="fill:#ffffff;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
+     id="polygon2552"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
+     id="polygon2554"
+     style="fill:#000000;stroke:none;stroke-width:0.08" />
+  <polygon
+     points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
+     id="polygon2556"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2558"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2560"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2562"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2564"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2566"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.424"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2568"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2570"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2572"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2574"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2576"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2578"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.474001"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2580"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2582"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2584"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2586"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2588"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2590"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.524"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2592"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2594"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.3509998"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2596"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2598"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.4710002"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2600"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2602"
+     style="fill:#0000ff;stroke:none" />
+  <ellipse
+     cx="6.5910001"
+     cy="21.573999"
+     rx="0.012"
+     ry="0.012"
+     id="ellipse2604"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="6.711"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2606"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="6.711"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2608"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <ellipse
+     cx="7.0110002"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2610"
+     style="fill:#8f8f8f;stroke:none" />
+  <ellipse
+     cx="7.0110002"
+     cy="21.434"
+     rx="0.15000001"
+     ry="0.048"
+     id="ellipse2612"
+     style="fill:none;stroke:#000000;stroke-width:0.02" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2614"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2616"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.1440001"
+     height="2.2880001"
+     x="10.504"
+     y="18.705"
+     id="rect2618"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2620"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2622"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91500002"
+     height="0.91500002"
+     x="10.618"
+     y="18.819"
+     id="rect2624"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.533"
+     y1="19.048"
+     x2="10.618"
+     y2="19.048"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2626"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.618"
+     y1="19.275999"
+     x2="11.533"
+     y2="19.275999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2628"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.533"
+     y1="19.448"
+     x2="10.618"
+     y2="19.448"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2630"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2632"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2634"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.62900001"
+     height="0.34299999"
+     x="10.618"
+     y="19.848"
+     id="rect2636"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.504"
+     y1="20.249001"
+     x2="11.647"
+     y2="20.249001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2638"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2640"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2642"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.018"
+     y="20.363001"
+     id="rect2644"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2646"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2648"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.247"
+     y="20.363001"
+     id="rect2650"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2652"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2654"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.057"
+     height="0.057"
+     x="11.476"
+     y="20.363001"
+     id="rect2656"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2658"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2660"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.114"
+     height="0.057"
+     x="11.419"
+     y="20.02"
+     id="rect2662"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.618"
+     y1="20.02"
+     x2="11.247"
+     y2="20.02"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2664"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2666"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2668"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.17200001"
+     height="0.17200001"
+     x="10.618"
+     y="20.306"
+     id="rect2670"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2672"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2674"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.801"
+     height="0.057"
+     x="10.675"
+     y="19.504999"
+     id="rect2676"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.906"
+     x2="11.19"
+     y2="19.906"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2678"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.19"
+     y1="19.962999"
+     x2="11.133"
+     y2="19.962999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2680"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.962999"
+     x2="10.732"
+     y2="19.962999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2682"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2684"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2686"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.28600001"
+     height="0.057"
+     x="10.79"
+     y="19.906"
+     id="rect2688"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.675"
+     y1="19.620001"
+     x2="10.732"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2690"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.79"
+     y1="19.620001"
+     x2="10.847"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2692"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.362"
+     y1="19.620001"
+     x2="11.476"
+     y2="19.620001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2694"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.934999"
+     x2="10.561"
+     y2="20.934999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2696"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.878"
+     x2="11.59"
+     y2="20.878"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2698"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.820999"
+     x2="10.561"
+     y2="20.820999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2700"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.763"
+     x2="11.59"
+     y2="20.763"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2702"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.705999"
+     x2="10.561"
+     y2="20.705999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2704"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.561"
+     y1="20.649"
+     x2="11.59"
+     y2="20.649"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2706"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="11.59"
+     y1="20.591999"
+     x2="10.561"
+     y2="20.591999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line2708"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.4960001"
+     y1="19.819"
+     x2="4.0770001"
+     y2="19.855"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line2710"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.183"
+     height="1.044"
+     x="2.302"
+     y="19.268999"
+     id="rect2712"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="2.8940001"
+     cy="20.312"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2714"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="2.8940001"
+     cy="19.268999"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2716"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="2.8940001"
+     cy="19.268999"
+     rx="0.59100002"
+     ry="0.17399999"
+     id="ellipse2718"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.485,19.269 L 3.485,20.312 C 3.485,20.409 3.221,20.486 2.894,20.486 C 2.567,20.486 2.302,20.409 2.302,20.312 L 2.302,19.269"
+     id="path2720"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.589"
+     y="19.868999"
+     id="text2722"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="2.6040001"
+     y="20.268999"
+     id="text2724"
+     style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <text
+     x="12.722"
+     y="22.476999"
+     id="text2726"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">250 Users</text>
+  <text
+     x="12.072"
+     y="17.239"
+     id="text2728"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
+  <text
+     x="12.402"
+     y="18.039"
+     id="text2730"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg 3</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="-1.129,15.125 -1.129,15.903 5.732,15.903 5.732,16.538 "
+     id="polyline2732"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="16.1"
+     y1="22.393"
+     x2="15.55"
+     y2="23.143"
+     stroke="#F7F7F7"
+     stroke-width="0.100"
+     id="line2734"
+     style="stroke:#f7f7f7;stroke-width:0.1" />
+  <text
+     x="-10.033"
+     y="7.7020001"
+     id="text2736"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="-10.108"
+     y="22.502001"
+     id="text2738"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="2.5420001"
+     y="22.502001"
+     id="text2740"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="1.905"
+     y="1.027"
+     id="text2742"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: UKNET</text>
+  <text
+     x="13.814"
+     y="1.102"
+     id="text2744"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: WESTNET</text>
+  <text
+     x="18.017"
+     y="15.202"
+     id="text2746"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
+  <text
+     x="-10.507"
+     y="1.794"
+     id="text2748"
+     style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Notes:</text>
+  <text
+     x="-11.075"
+     y="2.5439999"
+     id="text2750"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">The decision was made to implement separate</text>
+  <text
+     x="-11.075"
+     y="3.0439999"
+     id="text2752"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">domains for the West Coast and for UK</text>
+  <text
+     x="-11.075"
+     y="3.5439999"
+     id="text2754"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">operations. Wide-area traffic will be reduced.</text>
+  <text
+     x="-11.075"
+     y="4.0440001"
+     id="text2756"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">This design introduces the concept of deploying</text>
+  <text
+     x="-11.075"
+     y="4.5440001"
+     id="text2758"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">interdomain trusts, thus permitting much needed</text>
+  <text
+     x="-11.075"
+     y="5.0440001"
+     id="text2760"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">network integration and interoperabilty.</text>
+  <text
+     x="-11.075"
+     y="5.5440001"
+     id="text2762"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial" />
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap7-net2r.png b/docs-xml/Samba3-ByExample/images/chap7-net2r.png
new file mode 100644
index 00000000000..194fd3c3503
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap7-net2r.png
diff --git a/docs-xml/Samba3-ByExample/images/chap7-netr.png b/docs-xml/Samba3-ByExample/images/chap7-netr.png
new file mode 100644
index 00000000000..bbbbbf1cc73
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap7-netr.png
diff --git a/docs-xml/Samba3-ByExample/images/chap9-ADSDC.svg b/docs-xml/Samba3-ByExample/images/chap9-ADSDC.svg
new file mode 100644
index 00000000000..a0610367c33
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap9-ADSDC.svg
@@ -0,0 +1,1321 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="19.075001cm"
+   height="15.897cm"
+   viewBox="1.95 0.208 21.025 16.105"
+   id="svg2">
+  <defs
+     id="defs413" />
+  <rect
+     width="10.1"
+     height="13.95"
+     x="2.7750001"
+     y="2.125"
+     id="rect4"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 2.775,2.125 C 2.3884007,2.125 2.075,2.4384007 2.075,2.825"
+     id="path6"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 13.575,2.825 C 13.575,2.4384007 13.261599,2.125 12.875,2.125"
+     id="path8"
+     style="fill:#ededed;stroke:none" />
+  <rect
+     width="11.5"
+     height="12.55"
+     x="2.075"
+     y="2.825"
+     id="rect10"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 2.075,15.375 C 2.075,15.761599 2.3884007,16.075 2.775,16.075"
+     id="path12"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 12.875,16.075 C 13.261599,16.075 13.575,15.761599 13.575,15.375"
+     id="path14"
+     style="fill:#ededed;stroke:none" />
+  <line
+     x1="2.7750001"
+     y1="2.125"
+     x2="12.875"
+     y2="2.125"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7750001"
+     y1="16.075001"
+     x2="12.875"
+     y2="16.075001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 2.775,2.125 C 2.3884007,2.125 2.075,2.4384007 2.075,2.825"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 13.575,2.825 C 13.575,2.4384007 13.261599,2.125 12.875,2.125"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.075"
+     y1="2.825"
+     x2="2.075"
+     y2="15.375"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.575"
+     y1="2.825"
+     x2="13.575"
+     y2="15.375"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 2.075,15.375 C 2.075,15.761599 2.3884007,16.075 2.775,16.075"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 12.875,16.075 C 13.261599,16.075 13.575,15.761599 13.575,15.375"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="5.533"
+     height="13.95"
+     x="14.717"
+     y="2.1500001"
+     id="rect32"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 14.717,2.15 C 14.330791,2.1505517 14.018,2.4637909 14.018,2.85"
+     id="path34"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 20.95,2.85 C 20.95,2.4634007 20.636599,2.15 20.25,2.15"
+     id="path36"
+     style="fill:#ededed;stroke:none" />
+  <rect
+     width="6.9320002"
+     height="12.55"
+     x="14.018"
+     y="2.8499999"
+     id="rect38"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 14.018,15.4 C 14.018,15.786209 14.330791,16.099448 14.717,16.1"
+     id="path40"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 20.25,16.1 C 20.636599,16.1 20.95,15.786599 20.95,15.4"
+     id="path42"
+     style="fill:#ededed;stroke:none" />
+  <line
+     x1="14.717"
+     y1="2.1500001"
+     x2="20.25"
+     y2="2.1500001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line44"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.717"
+     y1="16.1"
+     x2="20.25"
+     y2="16.1"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 14.717,2.15 C 14.330791,2.1505517 14.018,2.4637909 14.018,2.85"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 20.95,2.85 C 20.95,2.4634007 20.636599,2.15 20.25,2.15"
+     id="path50"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.018"
+     y1="2.8499999"
+     x2="14.018"
+     y2="15.4"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.950001"
+     y1="2.8499999"
+     x2="20.950001"
+     y2="15.4"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line54"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 14.018,15.4 C 14.018,15.786209 14.330791,16.099448 14.717,16.1"
+     id="path56"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 20.25,16.1 C 20.636599,16.1 20.95,15.786599 20.95,15.4"
+     id="path58"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="6.125"
+     height="2.75"
+     x="9.9180002"
+     y="12.925"
+     id="rect60"
+     style="fill:#c3c3c3;stroke:none;stroke-width:0" />
+  <path
+     d="M 9.918,12.925 C 9.6418576,12.925 9.418,13.148858 9.418,13.425"
+     id="path62"
+     style="fill:#c3c3c3;stroke:none" />
+  <path
+     d="M 16.543,13.425 C 16.543,13.148858 16.319142,12.925 16.043,12.925"
+     id="path64"
+     style="fill:#c3c3c3;stroke:none" />
+  <rect
+     width="7.125"
+     height="1.75"
+     x="9.4180002"
+     y="13.425"
+     id="rect66"
+     style="fill:#c3c3c3;stroke:none;stroke-width:0" />
+  <path
+     d="M 9.418,15.175 C 9.418,15.451142 9.6418576,15.675 9.918,15.675"
+     id="path68"
+     style="fill:#c3c3c3;stroke:none" />
+  <path
+     d="M 16.043,15.675 C 16.319142,15.675 16.543,15.451142 16.543,15.175"
+     id="path70"
+     style="fill:#c3c3c3;stroke:none" />
+  <line
+     x1="9.9180002"
+     y1="12.925"
+     x2="16.042999"
+     y2="12.925"
+     stroke="#000000"
+     stroke-width="0.001"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.001" />
+  <line
+     x1="9.9180002"
+     y1="15.675"
+     x2="16.042999"
+     y2="15.675"
+     stroke="#000000"
+     stroke-width="0.001"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.001" />
+  <path
+     d="M 9.918,12.925 C 9.6418576,12.925 9.418,13.148858 9.418,13.425"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.001" />
+  <path
+     d="M 16.543,13.425 C 16.543,13.148858 16.319142,12.925 16.043,12.925"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.001" />
+  <line
+     x1="9.4180002"
+     y1="13.425"
+     x2="9.4180002"
+     y2="15.175"
+     stroke="#000000"
+     stroke-width="0.001"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.001" />
+  <line
+     x1="16.542999"
+     y1="13.425"
+     x2="16.542999"
+     y2="15.175"
+     stroke="#000000"
+     stroke-width="0.001"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.001" />
+  <path
+     d="M 9.418,15.175 C 9.418,15.451142 9.6418576,15.675 9.918,15.675"
+     id="path84"
+     style="fill:none;stroke:#000000;stroke-width:0.001" />
+  <path
+     d="M 16.043,15.675 C 16.319142,15.675 16.543,15.451142 16.543,15.175"
+     id="path86"
+     style="fill:none;stroke:#000000;stroke-width:0.001" />
+  <rect
+     width="6.125"
+     height="2.6500001"
+     x="9.75"
+     y="10.05"
+     id="rect88"
+     style="fill:#c3c3c3;stroke:none;stroke-width:0" />
+  <path
+     d="M 9.75,10.05 C 9.4738576,10.05 9.25,10.273858 9.25,10.55"
+     id="path90"
+     style="fill:#c3c3c3;stroke:none" />
+  <path
+     d="M 16.375,10.55 C 16.375,10.273858 16.151142,10.05 15.875,10.05"
+     id="path92"
+     style="fill:#c3c3c3;stroke:none" />
+  <rect
+     width="7.125"
+     height="1.65"
+     x="9.25"
+     y="10.55"
+     id="rect94"
+     style="fill:#c3c3c3;stroke:none;stroke-width:0" />
+  <path
+     d="M 9.25,12.2 C 9.25,12.476142 9.4738576,12.7 9.75,12.7"
+     id="path96"
+     style="fill:#c3c3c3;stroke:none" />
+  <path
+     d="M 15.875,12.7 C 16.151142,12.7 16.375,12.476142 16.375,12.2"
+     id="path98"
+     style="fill:#c3c3c3;stroke:none" />
+  <line
+     x1="9.75"
+     y1="10.05"
+     x2="15.875"
+     y2="10.05"
+     stroke="#000000"
+     stroke-width="0.001"
+     id="line100"
+     style="stroke:#000000;stroke-width:0.001" />
+  <line
+     x1="9.75"
+     y1="12.7"
+     x2="15.875"
+     y2="12.7"
+     stroke="#000000"
+     stroke-width="0.001"
+     id="line102"
+     style="stroke:#000000;stroke-width:0.001" />
+  <path
+     d="M 9.75,10.05 C 9.4738576,10.05 9.25,10.273858 9.25,10.55"
+     id="path104"
+     style="fill:none;stroke:#000000;stroke-width:0.001" />
+  <path
+     d="M 16.375,10.55 C 16.375,10.273858 16.151142,10.05 15.875,10.05"
+     id="path106"
+     style="fill:none;stroke:#000000;stroke-width:0.001" />
+  <line
+     x1="9.25"
+     y1="10.55"
+     x2="9.25"
+     y2="12.2"
+     stroke="#000000"
+     stroke-width="0.001"
+     id="line108"
+     style="stroke:#000000;stroke-width:0.001" />
+  <line
+     x1="16.375"
+     y1="10.55"
+     x2="16.375"
+     y2="12.2"
+     stroke="#000000"
+     stroke-width="0.001"
+     id="line110"
+     style="stroke:#000000;stroke-width:0.001" />
+  <path
+     d="M 9.25,12.2 C 9.25,12.476142 9.4738576,12.7 9.75,12.7"
+     id="path112"
+     style="fill:none;stroke:#000000;stroke-width:0.001" />
+  <path
+     d="M 15.875,12.7 C 16.151142,12.7 16.375,12.476142 16.375,12.2"
+     id="path114"
+     style="fill:none;stroke:#000000;stroke-width:0.001" />
+  <line
+     x1="2.0250001"
+     y1="1.825"
+     x2="20.950001"
+     y2="1.825"
+     stroke="#000000"
+     stroke-width="0.150"
+     id="line116"
+     style="stroke:#000000;stroke-width:0.15000001" />
+  <rect
+     width="1.391"
+     height="3.2460001"
+     x="8.2889996"
+     y="2.836"
+     id="rect118"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.391"
+     height="3.2460001"
+     x="8.2889996"
+     y="2.836"
+     id="rect120"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.113"
+     height="0.37099999"
+     x="8.4280005"
+     y="3.0309999"
+     id="rect122"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.113"
+     height="0.37099999"
+     x="8.4280005"
+     y="3.402"
+     id="rect124"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.113"
+     height="0.37099999"
+     x="8.4280005"
+     y="3.773"
+     id="rect126"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.113"
+     height="0.37099999"
+     x="8.4280005"
+     y="4.1440001"
+     id="rect128"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.69499999"
+     height="0.223"
+     x="8.4280005"
+     y="4.5890002"
+     id="rect130"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="9.4709997"
+     cy="4.6259999"
+     rx="0.048999999"
+     ry="0.048999999"
+     id="ellipse132"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="9.4709997"
+     cy="4.6259999"
+     rx="0.048999999"
+     ry="0.048999999"
+     id="ellipse134"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="9.4709997"
+     cy="4.7740002"
+     rx="0.048999999"
+     ry="0.048999999"
+     id="ellipse136"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="9.4709997"
+     cy="4.7740002"
+     rx="0.048999999"
+     ry="0.048999999"
+     id="ellipse138"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.167"
+     height="0.148"
+     x="9.1929998"
+     y="4.6630001"
+     id="rect140"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.167"
+     height="0.148"
+     x="9.1929998"
+     y="4.6630001"
+     id="rect142"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 8.521,5.108 L 8.521,5.92"
+     id="path144"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 8.752,5.108 L 8.752,5.92"
+     id="path146"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 8.984,5.108 L 8.984,5.92"
+     id="path148"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.216,5.108 L 9.216,5.92"
+     id="path150"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.448,5.108 L 9.448,5.92"
+     id="path152"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.68,5.108 L 9.68,5.92"
+     id="path154"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="8.011,6.36 8.289,5.804 8.289,6.082 9.68,6.082 9.68,5.804 10.051,6.36 8.011,6.36 "
+     id="polygon156"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="8.011,6.36 8.289,5.804 8.289,6.082 9.68,6.082 9.68,5.804 10.051,6.36 8.011,6.36 "
+     id="polygon158"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.67"
+     height="5.0089998"
+     x="16.247"
+     y="3.0339999"
+     id="rect160"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.67"
+     height="5.0089998"
+     x="16.247"
+     y="3.0339999"
+     id="rect162"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.67"
+     height="5.0089998"
+     x="16.247"
+     y="3.0339999"
+     id="rect164"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.336"
+     height="2.003"
+     x="16.414"
+     y="3.201"
+     id="rect166"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.336"
+     height="2.003"
+     x="16.414"
+     y="3.201"
+     id="rect168"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.336"
+     height="2.003"
+     x="16.414"
+     y="3.201"
+     id="rect170"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.414"
+     y1="3.5339999"
+     x2="17.75"
+     y2="3.5339999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line172"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.75"
+     y1="3.868"
+     x2="16.414"
+     y2="3.868"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line174"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.414"
+     y1="4.2020001"
+     x2="17.75"
+     y2="4.2020001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line176"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.414"
+     y1="4.5359998"
+     x2="17.75"
+     y2="4.5359998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line178"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.75"
+     y1="4.8699999"
+     x2="16.414"
+     y2="4.8699999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line180"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91799998"
+     height="0.50099999"
+     x="16.414"
+     y="5.3709998"
+     id="rect182"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91799998"
+     height="0.50099999"
+     x="16.414"
+     y="5.3709998"
+     id="rect184"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91799998"
+     height="0.50099999"
+     x="16.414"
+     y="5.3709998"
+     id="rect186"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.247"
+     y1="6.2059999"
+     x2="17.917"
+     y2="6.2059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line188"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="16.997999"
+     y="6.3730001"
+     id="rect190"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="16.997999"
+     y="6.3730001"
+     id="rect192"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="16.997999"
+     y="6.3730001"
+     id="rect194"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.332001"
+     y="6.3730001"
+     id="rect196"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.332001"
+     y="6.3730001"
+     id="rect198"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.332001"
+     y="6.3730001"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.666"
+     y="6.3730001"
+     id="rect202"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.666"
+     y="6.3730001"
+     id="rect204"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.666"
+     y="6.3730001"
+     id="rect206"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="17.583"
+     y="5.8720002"
+     id="rect208"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="17.583"
+     y="5.8720002"
+     id="rect210"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="17.583"
+     y="5.8720002"
+     id="rect212"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.414"
+     y1="5.6209998"
+     x2="17.332001"
+     y2="5.6209998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line214"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="16.414"
+     y="6.289"
+     id="rect216"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="16.414"
+     y="6.289"
+     id="rect218"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="16.414"
+     y="6.289"
+     id="rect220"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.169"
+     height="0.082999997"
+     x="16.497999"
+     y="4.954"
+     id="rect222"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.169"
+     height="0.082999997"
+     x="16.497999"
+     y="4.954"
+     id="rect224"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.169"
+     height="0.082999997"
+     x="16.497999"
+     y="4.954"
+     id="rect226"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.497999"
+     y1="5.454"
+     x2="17.249001"
+     y2="5.454"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line228"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.249001"
+     y1="5.5380001"
+     x2="17.165001"
+     y2="5.5380001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line230"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.497999"
+     y1="5.5380001"
+     x2="16.580999"
+     y2="5.5380001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line232"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="16.664"
+     y="5.454"
+     id="rect234"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="16.664"
+     y="5.454"
+     id="rect236"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="16.664"
+     y="5.454"
+     id="rect238"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.497999"
+     y1="5.1199999"
+     x2="16.580999"
+     y2="5.1199999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line240"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.664"
+     y1="5.1199999"
+     x2="16.747999"
+     y2="5.1199999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line242"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.499001"
+     y1="5.1199999"
+     x2="17.666"
+     y2="5.1199999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line244"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.9590001"
+     x2="17.833"
+     y2="7.9590001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line246"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.875"
+     x2="16.330999"
+     y2="7.875"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line248"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.7919998"
+     x2="17.833"
+     y2="7.7919998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line250"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.7080002"
+     x2="16.330999"
+     y2="7.7080002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line252"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.625"
+     x2="17.833"
+     y2="7.625"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line254"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.5409999"
+     x2="16.330999"
+     y2="7.5409999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line256"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.4580002"
+     x2="17.833"
+     y2="7.4580002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line258"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.3740001"
+     x2="16.330999"
+     y2="7.3740001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line260"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.2909999"
+     x2="17.833"
+     y2="7.2909999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line262"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.2069998"
+     x2="16.330999"
+     y2="7.2069998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line264"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.1240001"
+     x2="17.833"
+     y2="7.1240001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line266"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.04"
+     x2="16.330999"
+     y2="7.04"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line268"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="6.9569998"
+     x2="17.833"
+     y2="6.9569998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line270"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="6.8730001"
+     x2="16.330999"
+     y2="6.8730001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line272"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.1"
+     y1="1.85"
+     x2="17.1"
+     y2="3.05"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line274"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.0570002"
+     y1="1.823"
+     x2="9.0310001"
+     y2="2.836"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line276"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.85"
+     height="1.632"
+     x="5.7249999"
+     y="3.359"
+     id="rect278"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="6.6500001"
+     cy="4.9910002"
+     rx="0.92500001"
+     ry="0.27200001"
+     id="ellipse280"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="6.6500001"
+     cy="3.359"
+     rx="0.92500001"
+     ry="0.27200001"
+     id="ellipse282"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="6.6500001"
+     cy="3.359"
+     rx="0.92500001"
+     ry="0.27200001"
+     id="ellipse284"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 7.575,3.359 L 7.575,4.991 C 7.575,5.141 7.161,5.263 6.65,5.263 C 6.139,5.263 5.725,5.141 5.725,4.991 L 5.725,3.359"
+     id="path286"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="7.5999999"
+     y1="4.1750002"
+     x2="8.3000002"
+     y2="4.1999998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line288"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.3410001"
+     y="4.3000002"
+     id="text290"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">ADS</text>
+  <text
+     x="5.5120001"
+     y="7.125"
+     id="text292"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Windows Server 2003</text>
+  <text
+     x="6.5840001"
+     y="7.9250002"
+     id="text294"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">ADS Server</text>
+  <text
+     x="5.927"
+     y="8.7250004"
+     id="text296"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain Controller</text>
+  <text
+     x="15.605"
+     y="0.67500001"
+     id="text298"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba Domain</text>
+  <text
+     x="15.598"
+     y="1.475"
+     id="text300"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server</text>
+  <line
+     x1="2.075"
+     y1="8.9750004"
+     x2="20.9"
+     y2="9"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.50,0.50"
+     id="line302"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.5, 0.5" />
+  <text
+     x="6.5079999"
+     y="9.6750002"
+     id="text304"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain Services</text>
+  <text
+     x="5.7870002"
+     y="1.395"
+     id="text306"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network Configuration</text>
+  <rect
+     width="5.3499999"
+     height="1.8"
+     x="4.8249998"
+     y="12.25"
+     id="rect308"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="5.3499999"
+     height="1.8"
+     x="4.8249998"
+     y="12.25"
+     id="rect310"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="4.2750001"
+     height="1.375"
+     x="5.4250002"
+     y="10.6"
+     id="rect312"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.2750001"
+     height="1.375"
+     x="5.4250002"
+     y="10.6"
+     id="rect314"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.4749999"
+     y="11.411"
+     id="text316"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">CIFS Server</text>
+  <text
+     x="16.191999"
+     y="9.6499996"
+     id="text318"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Client Services</text>
+  <rect
+     width="2.575"
+     height="1.125"
+     x="16"
+     y="12.975"
+     id="rect320"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.575"
+     height="1.125"
+     x="16"
+     y="12.975"
+     id="rect322"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="16.599001"
+     y="13.7"
+     id="text324"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Winbind</text>
+  <rect
+     width="2.575"
+     height="1.1"
+     x="15.992"
+     y="10.275"
+     id="rect326"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.575"
+     height="1.1"
+     x="15.992"
+     y="10.275"
+     id="rect328"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.6070001"
+     height="1.1"
+     x="16.566999"
+     y="11.6"
+     id="rect330"
+     style="fill:#c5c5c5;stroke:none;stroke-width:0" />
+  <rect
+     width="2.6070001"
+     height="1.1"
+     x="16.566999"
+     y="11.6"
+     id="rect332"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="16.724001"
+     y="11.086"
+     id="text334"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd</text>
+  <text
+     x="17.357"
+     y="12.361"
+     id="text336"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nmbd</text>
+  <rect
+     width="2.7179999"
+     height="1.1"
+     x="15.95"
+     y="14.35"
+     id="rect338"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.7179999"
+     height="1.1"
+     x="15.95"
+     y="14.35"
+     id="rect340"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="16.579"
+     y="15.075"
+     id="text342"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nss_ldap</text>
+  <path
+     d="M 19.015,13.314 C 19.392106,13.104482 19.629557,12.710441 19.638616,12.279135 C 19.647674,11.84783 19.426976,11.444167 19.059,11.219"
+     id="path344"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="19.151,10.869 18.625,11.056 19.09,11.366 19.151,10.869 "
+     id="polygon346"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.053,13.169 18.575,13.458 19.094,13.667 19.053,13.169 "
+     id="polygon348"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 19.172,14.715 C 19.931775,14.326769 20.402308,13.537936 20.382916,12.684938 C 20.363525,11.83194 19.857632,11.065304 19.081,10.712"
+     id="path350"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="19.154,10.406 18.617,10.559 19.062,10.897 19.154,10.406 "
+     id="polygon352"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.146,14.531 18.716,14.889 19.26,15.018 19.146,14.531 "
+     id="polygon354"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="15.338"
+     y1="14.9"
+     x2="10.912"
+     y2="14.9"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.20,0.20"
+     id="line356"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.2, 0.2" />
+  <polygon
+     points="15.338,15.15 15.838,14.9 15.338,14.65 15.338,15.15 "
+     id="polygon358"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="15.338,15.15 15.838,14.9 15.338,14.65 15.338,15.15 "
+     id="polygon360"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="10.912,14.65 10.412,14.9 10.912,15.15 10.912,14.65 "
+     id="polygon362"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="10.912,14.65 10.412,14.9 10.912,15.15 10.912,14.65 "
+     id="polygon364"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.787"
+     y1="13.328"
+     x2="15.338"
+     y2="13.347"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.20,0.20"
+     id="line366"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.2, 0.2" />
+  <polygon
+     points="10.788,13.078 10.287,13.325 10.786,13.578 10.788,13.078 "
+     id="polygon368"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="10.788,13.078 10.287,13.325 10.786,13.578 10.788,13.078 "
+     id="polygon370"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="15.337,13.597 15.838,13.35 15.339,13.097 15.337,13.597 "
+     id="polygon372"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="15.337,13.597 15.838,13.35 15.339,13.097 15.337,13.597 "
+     id="polygon374"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.594"
+     y="14.05"
+     id="text376"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">UID/GID</text>
+  <text
+     x="12.425"
+     y="14.65"
+     id="text378"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Resolution</text>
+  <rect
+     width="5.4499998"
+     height="1.05"
+     x="4.8249998"
+     y="14.375"
+     id="rect380"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="5.4499998"
+     height="1.05"
+     x="4.8249998"
+     y="14.375"
+     id="rect382"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.2270002"
+     y="13.011"
+     id="text384"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Active Directory</text>
+  <text
+     x="6.0279999"
+     y="13.611"
+     id="text386"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(Kerberos / LDAP)</text>
+  <text
+     x="5.9699998"
+     y="15.136"
+     id="text388"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Services For UNIX</text>
+  <line
+     x1="10.361"
+     y1="10.714"
+     x2="15.314"
+     y2="10.524"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.20,0.20"
+     id="line390"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.2, 0.2" />
+  <polygon
+     points="10.352,10.464 9.862,10.733 10.371,10.964 10.352,10.464 "
+     id="polygon392"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="10.352,10.464 9.862,10.733 10.371,10.964 10.352,10.464 "
+     id="polygon394"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="15.323,10.773 15.813,10.504 15.304,10.274 15.323,10.773 "
+     id="polygon396"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="15.323,10.773 15.813,10.504 15.304,10.274 15.323,10.773 "
+     id="polygon398"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.795"
+     y1="12.333"
+     x2="15.355"
+     y2="11.242"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.20,0.20"
+     id="line400"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.2, 0.2" />
+  <polygon
+     points="10.737,12.09 10.309,12.449 10.853,12.576 10.737,12.09 "
+     id="polygon402"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="10.737,12.09 10.309,12.449 10.853,12.576 10.737,12.09 "
+     id="polygon404"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="15.413,11.485 15.841,11.126 15.297,10.999 15.413,11.485 "
+     id="polygon406"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="15.413,11.485 15.841,11.126 15.297,10.999 15.413,11.485 "
+     id="polygon408"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="11.411"
+     y="11.325"
+     id="text410"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Authentication</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/chap9-SambaDC.svg b/docs-xml/Samba3-ByExample/images/chap9-SambaDC.svg
new file mode 100644
index 00000000000..54d17633940
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/chap9-SambaDC.svg
@@ -0,0 +1,1443 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="19.075001cm"
+   height="15.897cm"
+   viewBox="1.95 0.208 21.025 16.105"
+   id="svg2">
+  <defs
+     id="defs453" />
+  <rect
+     width="10.1"
+     height="13.95"
+     x="2.7750001"
+     y="2.125"
+     id="rect4"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 2.775,2.125 C 2.3884007,2.125 2.075,2.4384007 2.075,2.825"
+     id="path6"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 13.575,2.825 C 13.575,2.4384007 13.261599,2.125 12.875,2.125"
+     id="path8"
+     style="fill:#ededed;stroke:none" />
+  <rect
+     width="11.5"
+     height="12.55"
+     x="2.075"
+     y="2.825"
+     id="rect10"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 2.075,15.375 C 2.075,15.761599 2.3884007,16.075 2.775,16.075"
+     id="path12"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 12.875,16.075 C 13.261599,16.075 13.575,15.761599 13.575,15.375"
+     id="path14"
+     style="fill:#ededed;stroke:none" />
+  <line
+     x1="2.7750001"
+     y1="2.125"
+     x2="12.875"
+     y2="2.125"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.7750001"
+     y1="16.075001"
+     x2="12.875"
+     y2="16.075001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 2.775,2.125 C 2.3884007,2.125 2.075,2.4384007 2.075,2.825"
+     id="path20"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 13.575,2.825 C 13.575,2.4384007 13.261599,2.125 12.875,2.125"
+     id="path22"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.075"
+     y1="2.825"
+     x2="2.075"
+     y2="15.375"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.575"
+     y1="2.825"
+     x2="13.575"
+     y2="15.375"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 2.075,15.375 C 2.075,15.761599 2.3884007,16.075 2.775,16.075"
+     id="path28"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 12.875,16.075 C 13.261599,16.075 13.575,15.761599 13.575,15.375"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="5.533"
+     height="13.95"
+     x="14.717"
+     y="2.1500001"
+     id="rect32"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 14.717,2.15 C 14.330791,2.1505517 14.018,2.4637909 14.018,2.85"
+     id="path34"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 20.95,2.85 C 20.95,2.4634007 20.636599,2.15 20.25,2.15"
+     id="path36"
+     style="fill:#ededed;stroke:none" />
+  <rect
+     width="6.9320002"
+     height="12.55"
+     x="14.018"
+     y="2.8499999"
+     id="rect38"
+     style="fill:#ededed;stroke:none;stroke-width:0" />
+  <path
+     d="M 14.018,15.4 C 14.018,15.786209 14.330791,16.099448 14.717,16.1"
+     id="path40"
+     style="fill:#ededed;stroke:none" />
+  <path
+     d="M 20.25,16.1 C 20.636599,16.1 20.95,15.786599 20.95,15.4"
+     id="path42"
+     style="fill:#ededed;stroke:none" />
+  <line
+     x1="14.717"
+     y1="2.1500001"
+     x2="20.25"
+     y2="2.1500001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line44"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.717"
+     y1="16.1"
+     x2="20.25"
+     y2="16.1"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 14.717,2.15 C 14.330791,2.1505517 14.018,2.4637909 14.018,2.85"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 20.95,2.85 C 20.95,2.4634007 20.636599,2.15 20.25,2.15"
+     id="path50"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.018"
+     y1="2.8499999"
+     x2="14.018"
+     y2="15.4"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.950001"
+     y1="2.8499999"
+     x2="20.950001"
+     y2="15.4"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line54"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 14.018,15.4 C 14.018,15.786209 14.330791,16.099448 14.717,16.1"
+     id="path56"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 20.25,16.1 C 20.636599,16.1 20.95,15.786599 20.95,15.4"
+     id="path58"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="4.9749999"
+     height="4.625"
+     x="10.8"
+     y="10.877"
+     id="rect60"
+     style="fill:#b5b5b5;stroke:none;stroke-width:0" />
+  <path
+     d="M 10.8,10.877 C 10.523858,10.877 10.3,11.100858 10.3,11.377"
+     id="path62"
+     style="fill:#b5b5b5;stroke:none" />
+  <path
+     d="M 16.275,11.377 C 16.275,11.100858 16.051142,10.877 15.775,10.877"
+     id="path64"
+     style="fill:#b5b5b5;stroke:none" />
+  <rect
+     width="5.9749999"
+     height="3.625"
+     x="10.3"
+     y="11.377"
+     id="rect66"
+     style="fill:#b5b5b5;stroke:none;stroke-width:0" />
+  <path
+     d="M 10.3,15.002 C 10.3,15.278142 10.523858,15.502 10.8,15.502"
+     id="path68"
+     style="fill:#b5b5b5;stroke:none" />
+  <path
+     d="M 15.775,15.502 C 16.051142,15.502 16.275,15.278142 16.275,15.002"
+     id="path70"
+     style="fill:#b5b5b5;stroke:none" />
+  <line
+     x1="10.8"
+     y1="10.877"
+     x2="15.775"
+     y2="10.877"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.8"
+     y1="15.502"
+     x2="15.775"
+     y2="15.502"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.8,10.877 C 10.523858,10.877 10.3,11.100858 10.3,11.377"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 16.275,11.377 C 16.275,11.100858 16.051142,10.877 15.775,10.877"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.3"
+     y1="11.377"
+     x2="10.3"
+     y2="15.002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.275"
+     y1="11.377"
+     x2="16.275"
+     y2="15.002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.3,15.002 C 10.3,15.278142 10.523858,15.502 10.8,15.502"
+     id="path84"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 15.775,15.502 C 16.051142,15.502 16.275,15.278142 16.275,15.002"
+     id="path86"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.0250001"
+     y1="1.825"
+     x2="20.950001"
+     y2="1.825"
+     stroke="#000000"
+     stroke-width="0.150"
+     id="line88"
+     style="stroke:#000000;stroke-width:0.15000001" />
+  <rect
+     width="1.391"
+     height="3.2460001"
+     x="5.539"
+     y="3.161"
+     id="rect90"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.391"
+     height="3.2460001"
+     x="5.539"
+     y="3.161"
+     id="rect92"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.113"
+     height="0.37099999"
+     x="5.678"
+     y="3.3559999"
+     id="rect94"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.113"
+     height="0.37099999"
+     x="5.678"
+     y="3.727"
+     id="rect96"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.113"
+     height="0.37099999"
+     x="5.678"
+     y="4.098"
+     id="rect98"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.113"
+     height="0.37099999"
+     x="5.678"
+     y="4.4689999"
+     id="rect100"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.69499999"
+     height="0.223"
+     x="5.678"
+     y="4.914"
+     id="rect102"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="6.7210002"
+     cy="4.9510002"
+     rx="0.048999999"
+     ry="0.048999999"
+     id="ellipse104"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="6.7210002"
+     cy="4.9510002"
+     rx="0.048999999"
+     ry="0.048999999"
+     id="ellipse106"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="6.7210002"
+     cy="5.099"
+     rx="0.048999999"
+     ry="0.048999999"
+     id="ellipse108"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="6.7210002"
+     cy="5.099"
+     rx="0.048999999"
+     ry="0.048999999"
+     id="ellipse110"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.167"
+     height="0.148"
+     x="6.4429998"
+     y="4.9879999"
+     id="rect112"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.167"
+     height="0.148"
+     x="6.4429998"
+     y="4.9879999"
+     id="rect114"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 5.771,5.433 L 5.771,6.245"
+     id="path116"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 6.002,5.433 L 6.002,6.245"
+     id="path118"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 6.234,5.433 L 6.234,6.245"
+     id="path120"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 6.466,5.433 L 6.466,6.245"
+     id="path122"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 6.698,5.433 L 6.698,6.245"
+     id="path124"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 6.93,5.433 L 6.93,6.245"
+     id="path126"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="5.261,6.685 5.539,6.129 5.539,6.407 6.93,6.407 6.93,6.129 7.301,6.685 5.261,6.685 "
+     id="polygon128"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="5.261,6.685 5.539,6.129 5.539,6.407 6.93,6.407 6.93,6.129 7.301,6.685 5.261,6.685 "
+     id="polygon130"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.354"
+     height="3.158"
+     x="8.8369999"
+     y="3.2119999"
+     id="rect132"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.354"
+     height="3.158"
+     x="8.8369999"
+     y="3.2119999"
+     id="rect134"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.0829999"
+     height="0.361"
+     x="8.9720001"
+     y="3.402"
+     id="rect136"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.0829999"
+     height="0.361"
+     x="8.9720001"
+     y="3.763"
+     id="rect138"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.0829999"
+     height="0.361"
+     x="8.9720001"
+     y="4.1240001"
+     id="rect140"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.0829999"
+     height="0.361"
+     x="8.9720001"
+     y="4.4850001"
+     id="rect142"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.67699999"
+     height="0.21699999"
+     x="8.9720001"
+     y="4.9180002"
+     id="rect144"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="9.9879999"
+     cy="4.954"
+     rx="0.046999998"
+     ry="0.046999998"
+     id="ellipse146"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="9.9879999"
+     cy="4.954"
+     rx="0.046999998"
+     ry="0.046999998"
+     id="ellipse148"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="9.9879999"
+     cy="5.099"
+     rx="0.046999998"
+     ry="0.046999998"
+     id="ellipse150"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="9.9879999"
+     cy="5.099"
+     rx="0.046999998"
+     ry="0.046999998"
+     id="ellipse152"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.162"
+     height="0.14399999"
+     x="9.717"
+     y="4.9899998"
+     id="rect154"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.162"
+     height="0.14399999"
+     x="9.717"
+     y="4.9899998"
+     id="rect156"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.063,5.423 L 9.063,6.213"
+     id="path158"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.288,5.423 L 9.288,6.213"
+     id="path160"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.514,5.423 L 9.514,6.213"
+     id="path162"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.739,5.423 L 9.739,6.213"
+     id="path164"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.965,5.423 L 9.965,6.213"
+     id="path166"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.191,5.423 L 10.191,6.213"
+     id="path168"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="8.566,6.642 8.837,6.1 8.837,6.371 10.191,6.371 10.191,6.1 10.552,6.642 8.566,6.642 "
+     id="polygon170"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="8.566,6.642 8.837,6.1 8.837,6.371 10.191,6.371 10.191,6.1 10.552,6.642 8.566,6.642 "
+     id="polygon172"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.67"
+     height="5.0089998"
+     x="16.247"
+     y="3.0339999"
+     id="rect174"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.67"
+     height="5.0089998"
+     x="16.247"
+     y="3.0339999"
+     id="rect176"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.67"
+     height="5.0089998"
+     x="16.247"
+     y="3.0339999"
+     id="rect178"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.336"
+     height="2.003"
+     x="16.414"
+     y="3.201"
+     id="rect180"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.336"
+     height="2.003"
+     x="16.414"
+     y="3.201"
+     id="rect182"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.336"
+     height="2.003"
+     x="16.414"
+     y="3.201"
+     id="rect184"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.414"
+     y1="3.5339999"
+     x2="17.75"
+     y2="3.5339999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line186"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.75"
+     y1="3.868"
+     x2="16.414"
+     y2="3.868"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line188"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.414"
+     y1="4.2020001"
+     x2="17.75"
+     y2="4.2020001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line190"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.414"
+     y1="4.5359998"
+     x2="17.75"
+     y2="4.5359998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line192"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.75"
+     y1="4.8699999"
+     x2="16.414"
+     y2="4.8699999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line194"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.91799998"
+     height="0.50099999"
+     x="16.414"
+     y="5.3709998"
+     id="rect196"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.91799998"
+     height="0.50099999"
+     x="16.414"
+     y="5.3709998"
+     id="rect198"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.91799998"
+     height="0.50099999"
+     x="16.414"
+     y="5.3709998"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.247"
+     y1="6.2059999"
+     x2="17.917"
+     y2="6.2059999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line202"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="16.997999"
+     y="6.3730001"
+     id="rect204"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="16.997999"
+     y="6.3730001"
+     id="rect206"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="16.997999"
+     y="6.3730001"
+     id="rect208"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.332001"
+     y="6.3730001"
+     id="rect210"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.332001"
+     y="6.3730001"
+     id="rect212"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.332001"
+     y="6.3730001"
+     id="rect214"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.666"
+     y="6.3730001"
+     id="rect216"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.666"
+     y="6.3730001"
+     id="rect218"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.082999997"
+     height="0.082999997"
+     x="17.666"
+     y="6.3730001"
+     id="rect220"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="17.583"
+     y="5.8720002"
+     id="rect222"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="17.583"
+     y="5.8720002"
+     id="rect224"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.167"
+     height="0.167"
+     x="17.583"
+     y="5.8720002"
+     id="rect226"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.414"
+     y1="5.6209998"
+     x2="17.332001"
+     y2="5.6209998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line228"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="16.414"
+     y="6.289"
+     id="rect230"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="16.414"
+     y="6.289"
+     id="rect232"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.25"
+     height="0.25"
+     x="16.414"
+     y="6.289"
+     id="rect234"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.169"
+     height="0.082999997"
+     x="16.497999"
+     y="4.954"
+     id="rect236"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.169"
+     height="0.082999997"
+     x="16.497999"
+     y="4.954"
+     id="rect238"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.169"
+     height="0.082999997"
+     x="16.497999"
+     y="4.954"
+     id="rect240"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.497999"
+     y1="5.454"
+     x2="17.249001"
+     y2="5.454"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line242"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.249001"
+     y1="5.5380001"
+     x2="17.165001"
+     y2="5.5380001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line244"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.497999"
+     y1="5.5380001"
+     x2="16.580999"
+     y2="5.5380001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line246"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="16.664"
+     y="5.454"
+     id="rect248"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="16.664"
+     y="5.454"
+     id="rect250"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.417"
+     height="0.082999997"
+     x="16.664"
+     y="5.454"
+     id="rect252"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.497999"
+     y1="5.1199999"
+     x2="16.580999"
+     y2="5.1199999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line254"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.664"
+     y1="5.1199999"
+     x2="16.747999"
+     y2="5.1199999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line256"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.499001"
+     y1="5.1199999"
+     x2="17.666"
+     y2="5.1199999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line258"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.9590001"
+     x2="17.833"
+     y2="7.9590001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line260"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.875"
+     x2="16.330999"
+     y2="7.875"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line262"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.7919998"
+     x2="17.833"
+     y2="7.7919998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line264"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.7080002"
+     x2="16.330999"
+     y2="7.7080002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line266"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.625"
+     x2="17.833"
+     y2="7.625"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line268"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.5409999"
+     x2="16.330999"
+     y2="7.5409999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line270"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.4580002"
+     x2="17.833"
+     y2="7.4580002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line272"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.3740001"
+     x2="16.330999"
+     y2="7.3740001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line274"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.2909999"
+     x2="17.833"
+     y2="7.2909999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line276"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.2069998"
+     x2="16.330999"
+     y2="7.2069998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line278"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="7.1240001"
+     x2="17.833"
+     y2="7.1240001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line280"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="7.04"
+     x2="16.330999"
+     y2="7.04"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line282"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.330999"
+     y1="6.9569998"
+     x2="17.833"
+     y2="6.9569998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line284"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.833"
+     y1="6.8730001"
+     x2="16.330999"
+     y2="6.8730001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line286"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.1"
+     y1="1.85"
+     x2="17.1"
+     y2="3.05"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line288"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.2579999"
+     y1="1.823"
+     x2="6.2810001"
+     y2="3.161"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line290"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="9.5249996"
+     y1="1.85"
+     x2="9.559"
+     y2="3.2119999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line292"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.85"
+     height="1.632"
+     x="2.925"
+     y="3.359"
+     id="rect294"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="3.8499999"
+     cy="4.9910002"
+     rx="0.92500001"
+     ry="0.27200001"
+     id="ellipse296"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.8499999"
+     cy="3.359"
+     rx="0.92500001"
+     ry="0.27200001"
+     id="ellipse298"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="3.8499999"
+     cy="3.359"
+     rx="0.92500001"
+     ry="0.27200001"
+     id="ellipse300"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 4.775,3.359 L 4.775,4.991 C 4.775,5.141 4.361,5.263 3.85,5.263 C 3.339,5.263 2.925,5.141 2.925,4.991 L 2.925,3.359"
+     id="path302"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.85"
+     height="1.632"
+     x="11.008"
+     y="3.3699999"
+     id="rect304"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <ellipse
+     cx="11.932"
+     cy="5.0019999"
+     rx="0.92500001"
+     ry="0.27200001"
+     id="ellipse306"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="11.932"
+     cy="3.3699999"
+     rx="0.92500001"
+     ry="0.27200001"
+     id="ellipse308"
+     style="fill:#ffffff;stroke:none" />
+  <ellipse
+     cx="11.932"
+     cy="3.3699999"
+     rx="0.92500001"
+     ry="0.27200001"
+     id="ellipse310"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 12.857,3.37 L 12.857,5.002 C 12.857,5.152 12.443,5.274 11.932,5.274 C 11.422,5.274 11.008,5.152 11.008,5.002 L 11.008,3.37"
+     id="path312"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="4.8000002"
+     y1="4.1750002"
+     x2="5.5"
+     y2="4.1999998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line314"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.259"
+     y1="4.1490002"
+     x2="10.959"
+     y2="4.1739998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line316"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.4660001"
+     y="4.3000002"
+     id="text318"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="3.3929999"
+     y="4.8000002"
+     id="text320"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
+  <text
+     x="11.541"
+     y="4.3000002"
+     id="text322"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <text
+     x="11.555"
+     y="4.8000002"
+     id="text324"
+     style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
+  <path
+     d="M 10.533,3.038 C 8.7210597,2.042993 6.5088646,2.1244423 4.775,3.25"
+     id="path326"
+     style="fill:none;stroke:#585858;stroke-width:0.1;stroke-dasharray:0.5, 0.15, 0.05, 0.15, 0.05, 0.15" />
+  <polygon
+     points="10.405,3.221 10.959,3.297 10.687,2.808 10.405,3.221 "
+     id="polygon328"
+     style="fill:#585858;stroke:none;stroke-width:0.1" />
+  <text
+     x="3.0420001"
+     y="6.0999999"
+     id="text330"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
+  <text
+     x="3.2969999"
+     y="6.9000001"
+     id="text332"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC</text>
+  <text
+     x="11.317"
+     y="6.0749998"
+     id="text334"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
+  <text
+     x="11.574"
+     y="6.875"
+     id="text336"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BDC</text>
+  <text
+     x="15.605"
+     y="0.67500001"
+     id="text338"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba Domain</text>
+  <text
+     x="15.598"
+     y="1.475"
+     id="text340"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server</text>
+  <line
+     x1="2.075"
+     y1="8.9750004"
+     x2="20.9"
+     y2="9"
+     stroke="#000000"
+     stroke-width="0.100"
+     stroke-dasharray="0.50,0.50"
+     id="line342"
+     style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.5, 0.5" />
+  <text
+     x="7.7189999"
+     y="9.6750002"
+     id="text344"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC/BDC Services</text>
+  <text
+     x="5.7870002"
+     y="1.395"
+     id="text346"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network Configuration</text>
+  <rect
+     width="2.575"
+     height="1.1"
+     x="7.4000001"
+     y="13.025"
+     id="rect348"
+     style="fill:#b9b9b9;stroke:none;stroke-width:0" />
+  <rect
+     width="2.575"
+     height="1.1"
+     x="7.4000001"
+     y="13.025"
+     id="rect350"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="8.0240002"
+     y="13.775"
+     id="text352"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#010101;font-family:arial">Winbind</text>
+  <rect
+     width="2.575"
+     height="1.1"
+     x="8.0679998"
+     y="14.4"
+     id="rect354"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.575"
+     height="1.1"
+     x="8.0679998"
+     y="14.4"
+     id="rect356"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="8.8870001"
+     y="15.1"
+     id="text358"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
+  <rect
+     width="2.575"
+     height="1.1"
+     x="8.0679998"
+     y="10.325"
+     id="rect360"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.575"
+     height="1.1"
+     x="8.0679998"
+     y="10.325"
+     id="rect362"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.6070001"
+     height="1.1"
+     x="7.4180002"
+     y="11.675"
+     id="rect364"
+     style="fill:#c6c6c6;stroke:none;stroke-width:0" />
+  <rect
+     width="2.6070001"
+     height="1.1"
+     x="7.4180002"
+     y="11.675"
+     id="rect366"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="8.7989998"
+     y="11.136"
+     id="text368"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd</text>
+  <text
+     x="8.2069998"
+     y="12.436"
+     id="text370"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nmbd</text>
+  <text
+     x="16.143"
+     y="9.6999998"
+     id="text372"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Client Services</text>
+  <rect
+     width="2.575"
+     height="1.125"
+     x="16"
+     y="12.975"
+     id="rect374"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.575"
+     height="1.125"
+     x="16"
+     y="12.975"
+     id="rect376"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="16.599001"
+     y="13.7"
+     id="text378"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Winbind</text>
+  <rect
+     width="2.575"
+     height="1.1"
+     x="15.992"
+     y="10.275"
+     id="rect380"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.575"
+     height="1.1"
+     x="15.992"
+     y="10.275"
+     id="rect382"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.608"
+     height="1.102"
+     x="16.517"
+     y="11.625"
+     id="rect384"
+     style="fill:#c5c5c5;stroke:none;stroke-width:0" />
+  <rect
+     width="2.608"
+     height="1.102"
+     x="16.517"
+     y="11.625"
+     id="rect386"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="16.724001"
+     y="11.086"
+     id="text388"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd</text>
+  <text
+     x="17.306999"
+     y="12.386"
+     id="text390"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nmbd</text>
+  <rect
+     width="2.7179999"
+     height="1.1"
+     x="15.95"
+     y="14.35"
+     id="rect392"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.7179999"
+     height="1.1"
+     x="15.95"
+     y="14.35"
+     id="rect394"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="16.579"
+     y="15.075"
+     id="text396"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nss_ldap</text>
+  <rect
+     width="2.717"
+     height="1.1"
+     x="4.1680002"
+     y="14.375"
+     id="rect398"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.717"
+     height="1.1"
+     x="4.1680002"
+     y="14.375"
+     id="rect400"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="4.796"
+     y="15.1"
+     id="text402"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nss_ldap</text>
+  <path
+     d="M 7.56,11.075 C 6.4745981,11.601642 5.7241236,12.635796 5.56,13.831"
+     id="path404"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="7.616,11.277 8.02,10.89 7.468,10.799 7.616,11.277 "
+     id="polygon406"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="5.268,13.829 5.526,14.325 5.768,13.821 5.268,13.829 "
+     id="polygon408"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="7.4349999"
+     y1="14.937"
+     x2="7.5180001"
+     y2="14.938"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line410"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="7.44,14.687 6.935,14.926 7.43,15.187 7.44,14.687 "
+     id="polygon412"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="7.512,15.188 8.018,14.949 7.523,14.688 7.512,15.188 "
+     id="polygon414"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 19.015,13.314 C 19.392106,13.104482 19.629557,12.710441 19.638616,12.279135 C 19.647674,11.84783 19.426976,11.444167 19.059,11.219"
+     id="path416"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="19.151,10.869 18.625,11.056 19.09,11.366 19.151,10.869 "
+     id="polygon418"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.053,13.169 18.575,13.458 19.094,13.667 19.053,13.169 "
+     id="polygon420"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 19.172,14.715 C 19.931775,14.326769 20.402308,13.537936 20.382916,12.684938 C 20.363525,11.83194 19.857632,11.065304 19.081,10.712"
+     id="path422"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="19.154,10.406 18.617,10.559 19.062,10.897 19.154,10.406 "
+     id="polygon424"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.146,14.531 18.716,14.889 19.26,15.018 19.146,14.531 "
+     id="polygon426"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="15.338"
+     y1="14.9"
+     x2="11.337"
+     y2="14.9"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line428"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="15.338,15.15 15.838,14.9 15.338,14.65 15.338,15.15 "
+     id="polygon430"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="15.338,15.15 15.838,14.9 15.338,14.65 15.338,15.15 "
+     id="polygon432"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="11.337,14.65 10.837,14.9 11.337,15.15 11.337,14.65 "
+     id="polygon434"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="11.337,14.65 10.837,14.9 11.337,15.15 11.337,14.65 "
+     id="polygon436"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="11.321"
+     y1="11.572"
+     x2="15.379"
+     y2="13.132"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line438"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="11.411,11.338 10.854,11.392 11.231,11.805 11.411,11.338 "
+     id="polygon440"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="11.411,11.338 10.854,11.392 11.231,11.805 11.411,11.338 "
+     id="polygon442"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="15.289,13.366 15.846,13.312 15.469,12.899 15.289,13.366 "
+     id="polygon444"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="15.289,13.366 15.846,13.312 15.469,12.899 15.289,13.366 "
+     id="polygon446"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.719"
+     y="13.45"
+     id="text448"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">UID/GID</text>
+  <text
+     x="12.55"
+     y="14.05"
+     id="text450"
+     style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Resolution</text>
+</svg>
diff --git a/docs-xml/Samba3-ByExample/images/imc-usermanager2.png b/docs-xml/Samba3-ByExample/images/imc-usermanager2.png
new file mode 100644
index 00000000000..3cfcc6a6ec4
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/imc-usermanager2.png
diff --git a/docs-xml/Samba3-ByExample/images/lam-config.png b/docs-xml/Samba3-ByExample/images/lam-config.png
new file mode 100644
index 00000000000..15f989bf374
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/lam-config.png
diff --git a/docs-xml/Samba3-ByExample/images/lam-group-members.png b/docs-xml/Samba3-ByExample/images/lam-group-members.png
new file mode 100644
index 00000000000..cab8e42fc72
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/lam-group-members.png
diff --git a/docs-xml/Samba3-ByExample/images/lam-groups.png b/docs-xml/Samba3-ByExample/images/lam-groups.png
new file mode 100644
index 00000000000..da17b19a776
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/lam-groups.png
diff --git a/docs-xml/Samba3-ByExample/images/lam-hosts.png b/docs-xml/Samba3-ByExample/images/lam-hosts.png
new file mode 100644
index 00000000000..27806eb9abc
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/lam-hosts.png
diff --git a/docs-xml/Samba3-ByExample/images/lam-login.png b/docs-xml/Samba3-ByExample/images/lam-login.png
new file mode 100644
index 00000000000..cce500fc430
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/lam-login.png
diff --git a/docs-xml/Samba3-ByExample/images/lam-users.png b/docs-xml/Samba3-ByExample/images/lam-users.png
new file mode 100644
index 00000000000..0ca4b437ec8
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/lam-users.png
diff --git a/docs-xml/Samba3-ByExample/images/openmag.png b/docs-xml/Samba3-ByExample/images/openmag.png
new file mode 100644
index 00000000000..52eca30c355
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/openmag.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp001.png b/docs-xml/Samba3-ByExample/images/wxpp001.png
new file mode 100644
index 00000000000..2e689a17e25
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp001.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp004.png b/docs-xml/Samba3-ByExample/images/wxpp004.png
new file mode 100644
index 00000000000..656f67942e3
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp004.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp006.png b/docs-xml/Samba3-ByExample/images/wxpp006.png
new file mode 100644
index 00000000000..a20b3ed5836
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp006.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp007.png b/docs-xml/Samba3-ByExample/images/wxpp007.png
new file mode 100644
index 00000000000..cf413522208
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp007.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp008.png b/docs-xml/Samba3-ByExample/images/wxpp008.png
new file mode 100644
index 00000000000..9958c7c873a
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp008.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp010.png b/docs-xml/Samba3-ByExample/images/wxpp010.png
new file mode 100644
index 00000000000..068a0dfc733
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp010.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp011.png b/docs-xml/Samba3-ByExample/images/wxpp011.png
new file mode 100644
index 00000000000..0cf88c04a6c
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp011.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp012.png b/docs-xml/Samba3-ByExample/images/wxpp012.png
new file mode 100644
index 00000000000..d89f3b5d31b
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp012.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp013.png b/docs-xml/Samba3-ByExample/images/wxpp013.png
new file mode 100644
index 00000000000..451240ee383
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp013.png
diff --git a/docs-xml/Samba3-ByExample/images/wxpp015.png b/docs-xml/Samba3-ByExample/images/wxpp015.png
new file mode 100644
index 00000000000..12fe2f31b26
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/images/wxpp015.png
diff --git a/docs-xml/Samba3-ByExample/index.xml b/docs-xml/Samba3-ByExample/index.xml
new file mode 100644
index 00000000000..aaa66a0f409
--- /dev/null
+++ b/docs-xml/Samba3-ByExample/index.xml
@@ -0,0 +1,153 @@
+<?xml version="1.0"?>

+<!DOCTYPE book PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">

+

+<book id="S3bE"

+	xmlns:xi="http://www.w3.org/2003/XInclude">

+	<title>Samba-3 by Example</title>

+	<subtitle>Practical Exercises in Successful Samba Deployment</subtitle>

+	<bookinfo>

+		<authorgroup>

+			<author>&person.jht;</author>

+		</authorgroup>

+		<pubdate>July, 2006</pubdate>

+	</bookinfo>

+

+	<?latex \clearpage ?>

+	<?latex \setcounter{page}{7} ?>

+

+	<xi:include href="SBE-inside-cover.xml"/>

+	<xi:include href="SBE-acknowledgements.xml"/>

+	<?latex \cleardoublepage ?>

+

+	<toc/>

+	<?latex \cleardoublepage ?>

+	<?latex \listofexamples ?>

+	<?latex \cleardoublepage ?>

+	<lot/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-foreword.xml"/>

+	<xi:include href="SBE-preface.xml"/>

+<!-- Chapters -->

+

+<part id="ExNetworks">

+<title>Example Network Configurations</title>

+<partintro>

+<title>Example Network Configurations</title>

+

+<?latex \pagenumbering{arabic} ?>

+

+<para>

+This section of <emphasis>Samba-3 by Example</emphasis> provides example network

+configurations that can be copied, or modified as needed, and deployed as-is.

+The contents have been marginally updated to reflect changes made in Samba=3.0.23.

+</para>

+

+<para>

+Best use can be made of this book by finding in this section the network design and

+layout that best approximates your estimated needs. It is recommended that you will

+implement the design pattern exactly as it appears, then after the installation has

+been proven to work make any changes or modifications needed at your site.

+</para>

+

+<para>

+The examples have been tested with Red Hat Fedora Core 2, Novell SUSE Linux Professional

+9.3 and Novell SUSE Linux Enterprise Server (SLES) 9. The principals of implementation

+apply to all Linux and UNIX systems in general, though some system files and tools will 

+be different and the location of some Samba file locations will be different since these 

+are determined by the person who packages Samba for each platform.

+</para>

+

+<para>

+If you are deploying Samba is a mission-critical environment, or if you simply want

+to save time and get your Samba network operational with minimal fuss, there is the

+option to purchase commercial, professional, Samba support. Information regarding

+commercial support options may be obtained from the commercial

+<ulink url="http://www.samba.org/samba/support/">support</ulink> pages from 

+the Samba web site.

+</para>

+

+</partintro>

+

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-SimpleOfficeServer.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-TheSmallOffice.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-SecureOfficeServer.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-500UserNetwork.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-MakingHappyUsers.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-2000UserNetwork.xml"/>

+	<?latex \cleardoublepage ?>

+

+</part>

+

+<part id="DMSMig">

+<title>Domain Members, Updating Samba and Migration</title>

+<partintro>

+<title>Domain Members, Updating Samba and Migration</title>

+

+<para>

+This section <emphasis>Samba-3 by Example</emphasis> covers two main topics: How to add

+Samba Domain Member Servers and Samba Domain Member Clients to a Samba domain, the other

+subject is that of how to migrate from and NT4 Domain, a NetWare server, or from an earlier

+Samba version to environments that use the most recent Samba-3 release. 

+</para>

+

+<para>

+Those who are making use of the chapter on Adding UNIX clients and servers running Samba

+to a Samba or a Windows networking domain may also benefit by referring to the book

+<emphasis>The Official Samba-3 HOWTO and Reference Guide.</emphasis>

+</para>

+

+</partintro>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-AddingUNIXClients.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-UpgradingSamba.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-MigrateNT4Samba3.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-MigrateNW4Samba3.xml"/>

+	<?latex \cleardoublepage ?>

+</part>

+

+<part id="RefSection">

+<title>Reference Section</title>

+<partintro>

+<title>Reference Section</title>

+

+<para>

+This section <emphasis>Samba-3 by Example</emphasis> provides important reference material

+that may help you to solve network performance issues, to answer some of the critiques

+published regarding Samba, or just to gain a more broad understanding of how Samba can

+play in a Windows networking world.

+</para>

+

+</partintro>

+

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-KerberosFastStart.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-DomainAppsSupport.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-HighAvailability.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-Support.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-Appendix1.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="SBE-Appendix2.xml"/>

+	<?latex \cleardoublepage ?>

+	<xi:include href="gpl-3.0.xml"/>

+	<?latex \cleardoublepage ?>

+

+</part>

+

+	<xi:include href="SBE-glossary.xml"/>

+	<?latex \cleardoublepage ?>

+	<index/>

+

+</book>

diff --git a/docs-xml/Samba3-Developers-Guide/CodingSuggestions.xml b/docs-xml/Samba3-Developers-Guide/CodingSuggestions.xml
new file mode 100644
index 00000000000..caf93d84ad0
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/CodingSuggestions.xml
@@ -0,0 +1,239 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="CodingSuggestions">
+<chapterinfo>
+	<author>
+		<firstname>Steve</firstname><surname>French</surname>
+	</author>
+	<author>
+		<firstname>Simo</firstname><surname>Sorce</surname>
+	</author>
+	<author>
+		<firstname>Andrew</firstname><surname>Bartlett</surname>
+	</author>
+	<author>
+		<firstname>Tim</firstname><surname>Potter</surname>
+	</author>
+	<author>
+		<firstname>Martin</firstname><surname>Pool</surname>
+	</author>
+</chapterinfo>
+
+<title>Coding Suggestions</title>
+
+<para>
+So you want to add code to Samba ...
+</para>
+
+<para>
+One of the daunting tasks facing a programmer attempting to write code for
+Samba is understanding the various coding conventions used by those most
+active in the project.  These conventions were mostly unwritten and helped
+improve either the portability, stability or consistency of the code. This
+document will attempt to document a few of the more important coding
+practices used at this time on the Samba project.  The coding practices are
+expected to change slightly over time, and even to grow as more is learned
+about obscure portability considerations.  Two existing documents
+<filename>samba/source/internals.doc</filename> and 
+<filename>samba/source/architecture.doc</filename> provide
+additional information.
+</para>
+
+<para>
+The loosely related question of coding style is very personal and this
+document does not attempt to address that subject, except to say that I
+have observed that eight character tabs seem to be preferred in Samba
+source.  If you are interested in the topic of coding style, two oft-quoted
+documents are:
+</para>
+
+<para>
+<ulink url="http://lxr.linux.no/source/Documentation/CodingStyle">http://lxr.linux.no/source/Documentation/CodingStyle</ulink>
+</para>
+
+<para>
+<ulink url="http://www.fsf.org/prep/standards_toc.html">http://www.fsf.org/prep/standards_toc.html</ulink>
+</para>
+
+<para>
+But note that coding style in Samba varies due to the many different
+programmers who have contributed.
+</para>
+
+<para>
+Following are some considerations you should use when adding new code to
+Samba.  First and foremost remember that:
+</para>
+
+<para>
+Portability is a primary consideration in adding function, as is network
+compatability with de facto, existing, real world CIFS/SMB implementations.
+There are lots of platforms that Samba builds on so use caution when adding
+a call to a library function that is not invoked in existing Samba code.
+Also note that there are many quite different SMB/CIFS clients that Samba
+tries to support, not all of which follow the SNIA CIFS Technical Reference
+(or the earlier Microsoft reference documents or the X/Open book on the SMB
+Standard) perfectly.
+</para>
+
+<para>
+Here are some other suggestions:
+</para>
+
+<orderedlist>
+
+<listitem><para>
+	use d_printf instead of printf for display text
+	reason: enable auto-substitution of translated language text 
+</para></listitem>
+
+<listitem><para>
+	use SAFE_FREE instead of free
+	reason: reduce traps due to null pointers
+</para></listitem>
+
+<listitem><para>
+	don't use bzero use memset, or ZERO_STRUCT and ZERO_STRUCTP macros
+	reason: not POSIX
+</para></listitem>
+
+<listitem><para>
+	don't use strcpy and strlen (use safe_* equivalents)
+	reason: to avoid traps due to buffer overruns
+</para></listitem>
+
+<listitem><para>
+	don't use getopt_long, use popt functions instead
+	reason: portability
+</para></listitem>
+
+<listitem><para>
+	explicitly add const qualifiers on parm passing in functions where parm
+	is input only (somewhat controversial but const can be #defined away)
+</para></listitem>
+
+<listitem><para>
+	when passing a va_list as an arg, or assigning one to another
+	please use the VA_COPY() macro
+	reason: on some platforms, va_list is a struct that must be 
+	initialized in each function...can SEGV if you don't.
+</para></listitem>
+
+<listitem><para>
+	discourage use of threads
+	reason: portability (also see architecture.doc)
+</para></listitem>
+
+<listitem><para>
+	don't explicitly include new header files in C files - new h files 
+	should be included by adding them once to includes.h
+	reason: consistency
+</para></listitem>
+
+<listitem><para>
+	don't explicitly extern functions (they are autogenerated by 
+	"make proto" into proto.h)
+	reason: consistency
+</para></listitem>
+
+<listitem><para>
+	use endian safe macros when unpacking SMBs (see byteorder.h and
+	internals.doc)
+	reason: not everyone uses Intel
+</para></listitem>
+
+<listitem><para>
+	Note Unicode implications of charset handling (see internals.doc).  See
+	pull_*  and push_* and convert_string functions.
+	reason: Internationalization
+</para></listitem>
+
+<listitem><para>
+	Don't assume English only
+	reason: See above
+</para></listitem>
+
+<listitem><para>
+	Try to avoid using in/out parameters (functions that return data which
+	overwrites input parameters)
+	reason: Can cause stability problems
+</para></listitem>
+
+<listitem><para>
+	Ensure copyright notices are correct, don't append Tridge's name to code
+	that he didn't write.  If you did not write the code, make sure that it
+	can coexist with the rest of the Samba GPLed code.
+</para></listitem>
+
+<listitem><para>
+	Consider usage of DATA_BLOBs for length specified byte-data.
+	reason: stability
+</para></listitem>
+
+<listitem><para>
+	Take advantage of tdbs for database like function
+	reason: consistency
+</para></listitem>
+
+<listitem><para>
+	Don't access the SAM_ACCOUNT structure directly, they should be accessed
+	via pdb_get...() and pdb_set...() functions.
+	reason: stability, consistency
+</para></listitem>
+
+<listitem><para>
+	Don't check a password directly against the passdb, always use the
+	check_password() interface.
+	reason: long term pluggability
+</para></listitem>
+
+<listitem><para>
+	Try to use asprintf rather than pstrings and fstrings where possible
+</para></listitem>
+
+<listitem><para>
+	Use normal C comments / * instead of C++ comments // like
+	this.  Although the C++ comment format is part of the C99
+	standard, some older vendor C compilers do not accept it.
+</para></listitem>
+
+<listitem><para>
+	Try to write documentation for API functions and structures
+	explaining the point of the code, the way it should be used, and
+	any special conditions or results.  Mark these with a double-star
+	comment start / ** so that they can be picked up by Doxygen, as in
+	this file.
+</para></listitem>
+
+<listitem><para>
+	Keep the scope narrow. This means making functions/variables
+	static whenever possible. We don't want our namespace
+	polluted. Each module should have a minimal number of externally
+	visible functions or variables.
+</para></listitem>
+
+<listitem><para>
+	Use function pointers to keep knowledge about particular pieces of
+	code isolated in one place. We don't want a particular piece of
+	functionality to be spread out across lots of places - that makes
+	for fragile, hand to maintain code. Instead, design an interface
+	and use tables containing function pointers to implement specific
+	functionality. This is particularly important for command
+	interpreters. 
+</para></listitem>
+
+<listitem><para>
+	Think carefully about what it will be like for someone else to add
+	to and maintain your code. If it would be hard for someone else to
+	maintain then do it another way. 
+</para></listitem>
+
+</orderedlist>
+
+<para>
+The suggestions above are simply that, suggestions, but the information may
+help in reducing the routine rework done on new code.  The preceeding list
+is expected to change routinely as new support routines and macros are
+added.
+</para>
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/Tracing.xml b/docs-xml/Samba3-Developers-Guide/Tracing.xml
new file mode 100644
index 00000000000..3eaab6373ec
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/Tracing.xml
@@ -0,0 +1,131 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="tracing">
+<chapterinfo>
+	<author>
+		<firstname>Andrew</firstname><surname>Tridgell</surname>
+		<affiliation>
+			<orgname>Samba Team</orgname>
+		</affiliation>
+	</author>
+</chapterinfo>
+
+<title>Tracing samba system calls</title>
+
+<para>
+This file describes how to do a system call trace on Samba to work out
+what its doing wrong. This is not for the faint of heart, but if you
+are reading this then you are probably desperate.
+</para>
+
+<para>
+Actually its not as bad as the the above makes it sound, just don't
+expect the output to be very pretty :-)
+</para>
+
+<para>
+Ok, down to business. One of the big advantages of unix systems is
+that they nearly all come with a system trace utility that allows you
+to monitor all system calls that a program is making. This is
+extremely using for debugging and also helps when trying to work out
+why something is slower than you expect. You can use system tracing
+without any special compilation options. 
+</para>
+
+<para>
+The system trace utility is called different things on different
+systems. On Linux systems its called strace. Under SunOS 4 its called
+trace. Under SVR4 style systems (including solaris) its called
+truss. Under many BSD systems its called ktrace. 
+</para>
+
+<para>
+The first thing you should do is read the man page for your native
+system call tracer. In the discussion below I'll assume its called
+strace as strace is the only portable system tracer (its available for
+free for many unix types) and its also got some of the nicest
+features.
+</para>
+
+<para>
+Next, try using strace on some simple commands. For example, <command>strace
+ls</command> or <command>strace echo hello</command>.
+</para>
+
+<para> 
+You'll notice that it produces a LOT of output. It is showing you the
+arguments to every system call that the program makes and the
+result. Very little happens in a program without a system call so you
+get lots of output. You'll also find that it produces a lot of
+"preamble" stuff showing the loading of shared libraries etc. Ignore
+this (unless its going wrong!)
+</para>
+
+<para>
+For example, the only line that really matters in the <command>strace echo
+hello</command> output is:
+</para>
+
+<para><programlisting>
+write(1, "hello\n", 6)                  = 6
+</programlisting></para>
+
+<para>all the rest is just setting up to run the program.</para>
+
+<para>
+Ok, now you're familiar with strace. To use it on Samba you need to
+strace the running smbd daemon. The way I tend ot use it is to first
+login from my Windows PC to the Samba server, then use smbstatus to
+find which process ID that client is attached to, then as root I do
+<command>strace -p PID</command> to attach to that process. I normally redirect the
+stderr output from this command to a file for later perusal. For
+example, if I'm using a csh style shell:
+</para>
+
+<para><command>strace -f -p 3872 &gt;&amp; strace.out</command></para>
+
+<para>or with a sh style shell:</para>
+
+<para><command>strace -f -p 3872 > strace.out 2&gt;&amp;1</command></para>
+
+<para>
+Note the "-f" option. This is only available on some systems, and
+allows you to trace not just the current process, but any children it
+forks. This is great for finding printing problems caused by the
+"print command" being wrong.
+</para>
+
+<para>
+Once you are attached you then can do whatever it is on the client
+that is causing problems and you will capture all the system calls
+that smbd makes. 
+</para>
+
+<para>
+So how do you interpret the results? Generally I search through the
+output for strings that I know will appear when the problem
+happens. For example, if I am having touble with permissions on a file
+I would search for that files name in the strace output and look at
+the surrounding lines. Another trick is to match up file descriptor
+numbers and "follow" what happens to an open file until it is closed.
+</para>
+
+<para>
+Beyond this you will have to use your initiative. To give you an idea
+of what you are looking for here is a piece of strace output that
+shows that <filename>/dev/null</filename> is not world writeable, which
+causes printing to fail with Samba:
+</para>
+
+<para><programlisting>
+[pid 28268] open("/dev/null", O_RDWR)   = -1 EACCES (Permission denied)
+[pid 28268] open("/dev/null", O_WRONLY) = -1 EACCES (Permission denied)
+</programlisting></para>
+
+<para>
+The process is trying to first open <filename>/dev/null</filename> read-write 
+then read-only. Both fail. This means <filename>/dev/null</filename> has 
+incorrect permissions.
+</para>
+
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/architecture.xml b/docs-xml/Samba3-Developers-Guide/architecture.xml
new file mode 100644
index 00000000000..bb0f29981b4
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/architecture.xml
@@ -0,0 +1,186 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="architecture">
+<chapterinfo>
+	<author>
+		<firstname>Dan</firstname><surname>Shearer</surname>
+	</author>
+	<pubdate> November 1997</pubdate>
+</chapterinfo>
+
+<title>Samba Architecture</title>
+
+<sect1>
+<title>Introduction</title>
+
+<para>
+This document gives a general overview of how Samba works
+internally. The Samba Team has tried to come up with a model which is
+the best possible compromise between elegance, portability, security
+and the constraints imposed by the very messy SMB and CIFS
+protocol. 
+</para>
+
+<para>
+It also tries to answer some of the frequently asked questions such as:
+</para>
+
+<orderedlist>
+<listitem><para>
+	Is Samba secure when running on Unix? The xyz platform?
+	What about the root priveliges issue?
+</para></listitem>
+
+<listitem><para>Pros and cons of multithreading in various parts of Samba</para></listitem>
+
+<listitem><para>Why not have a separate process for name resolution, WINS, and browsing?</para></listitem>
+
+</orderedlist>
+
+</sect1>
+
+<sect1>
+<title>Multithreading and Samba</title>
+
+<para>
+People sometimes tout threads as a uniformly good thing. They are very
+nice in their place but are quite inappropriate for smbd. nmbd is
+another matter, and multi-threading it would be very nice. 
+</para>
+
+<para>
+The short version is that smbd is not multithreaded, and alternative
+servers that take this approach under Unix (such as Syntax, at the
+time of writing) suffer tremendous performance penalties and are less
+robust. nmbd is not threaded either, but this is because it is not
+possible to do it while keeping code consistent and portable across 35
+or more platforms. (This drawback also applies to threading smbd.)
+</para>
+
+<para>
+The longer versions is that there are very good reasons for not making
+smbd multi-threaded.  Multi-threading would actually make Samba much
+slower, less scalable, less portable and much less robust. The fact
+that we use a separate process for each connection is one of Samba's
+biggest advantages.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Threading smbd</title>
+
+<para>
+A few problems that would arise from a threaded smbd are:
+</para>
+
+<orderedlist>
+<listitem><para>
+	It's not only to create threads instead of processes, but you
+	must care about all variables if they have to be thread specific
+	(currently they would be global).
+</para></listitem>
+
+<listitem><para>
+	if one thread dies (eg. a seg fault) then all threads die. We can
+	immediately throw robustness out the window.
+</para></listitem>
+
+<listitem><para>
+	many of the system calls we make are blocking. Non-blocking
+	equivalents of many calls are either not available or are awkward (and
+	slow) to use. So while we block in one thread all clients are
+	waiting. Imagine if one share is a slow NFS filesystem and the others 
+	are fast, we will end up slowing all clients to the speed of NFS.
+</para></listitem>
+
+<listitem><para>
+	you can't run as a different uid in different threads. This means
+	we would have to switch uid/gid on _every_ SMB packet. It would be
+	horrendously slow.
+</para></listitem>
+
+<listitem><para>
+	the per process file descriptor limit would mean that we could only
+	support a limited number of clients.
+</para></listitem>
+
+<listitem><para>
+	we couldn't use the system locking calls as the locking context of
+	fcntl() is a process, not a thread.
+</para></listitem>
+
+</orderedlist>
+
+</sect1>
+
+<sect1>
+<title>Threading nmbd</title>
+
+<para>
+This would be ideal, but gets sunk by portability requirements.
+</para>
+
+<para>
+Andrew tried to write a test threads library for nmbd that used only
+ansi-C constructs (using setjmp and longjmp). Unfortunately some OSes
+defeat this by restricting longjmp to calling addresses that are
+shallower than the current address on the stack (apparently AIX does
+this). This makes a truly portable threads library impossible. So to
+support all our current platforms we would have to code nmbd both with
+and without threads, and as the real aim of threads is to make the
+code clearer we would not have gained anything. (it is a myth that
+threads make things faster. threading is like recursion, it can make
+things clear but the same thing can always be done faster by some
+other method)
+</para>
+
+<para>
+Chris tried to spec out a general design that would abstract threading
+vs separate processes (vs other methods?) and make them accessible
+through some general API. This doesn't work because of the data
+sharing requirements of the protocol (packets in the future depending
+on packets now, etc.) At least, the code would work but would be very
+clumsy, and besides the fork() type model would never work on Unix. (Is there an OS that it would work on, for nmbd?)
+</para>
+
+<para>
+A fork() is cheap, but not nearly cheap enough to do on every UDP
+packet that arrives. Having a pool of processes is possible but is
+nasty to program cleanly due to the enormous amount of shared data (in
+complex structures) between the processes. We can't rely on each
+platform having a shared memory system.
+</para>
+
+</sect1>
+
+<sect1>
+<title>nbmd Design</title>
+
+<para>
+Originally Andrew used recursion to simulate a multi-threaded
+environment, which use the stack enormously and made for really
+confusing debugging sessions. Luke Leighton rewrote it to use a
+queuing system that keeps state information on each packet.  The
+first version used a single structure which was used by all the
+pending states.  As the initialisation of this structure was
+done by adding arguments, as the functionality developed, it got
+pretty messy.  So, it was replaced with a higher-order function
+and a pointer to a user-defined memory block.  This suddenly
+made things much simpler: large numbers of functions could be
+made static, and modularised.  This is the same principle as used
+in NT's kernel, and achieves the same effect as threads, but in
+a single process.
+</para>
+
+<para>
+Then Jeremy rewrote nmbd. The packet data in nmbd isn't what's on the
+wire. It's a nice format that is very amenable to processing but still
+keeps the idea of a distinct packet. See "struct packet_struct" in
+nameserv.h.  It has all the detail but none of the on-the-wire
+mess. This makes it ideal for using in disk or memory-based databases
+for browsing and WINS support. 
+</para>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/cifsntdomain.xml b/docs-xml/Samba3-Developers-Guide/cifsntdomain.xml
new file mode 100644
index 00000000000..2626c8fc13c
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/cifsntdomain.xml
@@ -0,0 +1,2934 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="ntdomain">
+<chapterinfo>
+	<author>
+		<firstname>Luke</firstname><surname>Leighton</surname>
+		<affiliation><address><email>lkcl@switchboard.net</email></address></affiliation>
+	</author>
+	<author>
+		<firstname>Paul</firstname><surname>Ashton</surname>
+		<affiliation><address><email>paul@argo.demon.co.uk</email></address></affiliation>
+	</author>
+	<author>
+		<firstname>Duncan</firstname><surname>Stansfield</surname>
+		<affiliation><address><email>duncans@sco.com</email></address></affiliation>
+	</author>
+
+	<pubdate>01 November 97(version 0.0.24)</pubdate>
+</chapterinfo>
+
+<title>NT Domain RPC's</title>
+
+<sect1>
+<title>Introduction</title>
+
+
+<para>
+This document contains information to provide an NT workstation with login
+services, without the need for an NT server. It is the sgml version of <ulink url="http://mailhost.cb1.com/~lkcl/cifsntdomain.txt">http://mailhost.cb1.com/~lkcl/cifsntdomain.txt</ulink>, controlled by Luke.
+</para>
+
+<para>
+It should be possible to select a domain instead of a workgroup (in the NT
+workstation's TCP/IP settings) and after the obligatory reboot, type in a
+username, password, select a domain and successfully log in.  I would
+appreciate any feedback on your experiences with this process, and any
+comments, corrections and additions to this document.
+</para>
+
+<para>
+The packets described here can be easily derived from (and are probably
+better understood using) Netmon.exe.  You will need to use the version
+of Netmon that matches your system, in order to correctly decode the
+NETLOGON, lsarpc and srvsvc Transact pipes.  This document is derived from
+NT Service Pack 1 and its corresponding version of Netmon.  It is intended
+that an annotated packet trace be produced, which will likely be more
+instructive than this document.
+</para>
+
+<para>
+Also needed, to fully implement NT Domain Login Services, is the 
+document describing the cryptographic part of the NT authentication.
+This document is available from comp.protocols.smb; from the ntsecurity.net
+digest and from the samba digest, amongst other sources.
+</para>
+
+<para>
+A copy is available from:
+</para>
+
+<para><ulink url="http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935">http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935</ulink></para>
+
+<para><ulink url="http://mailhost.cb1.com/~lkcl/crypt.html">http://mailhost.cb1.com/~lkcl/crypt.html</ulink></para>
+
+<para>
+A c-code implementation, provided by <ulink url="mailto:linus@incolumitas.se">Linus Nordberg</ulink>
+of this protocol is available from:
+</para>
+
+<para><ulink url="http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html">http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html</ulink></para>
+<para><ulink url="http://mailhost.cb1.com/~lkcl/crypt.txt">http://mailhost.cb1.com/~lkcl/crypt.txt</ulink></para>
+
+<para>
+Also used to provide debugging information is the Check Build version of
+NT workstation, and enabling full debugging in NETLOGON.  This is
+achieved by setting the following REG_SZ registry key to 0x1ffffff:
+</para>
+
+<para><filename>HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters</filename></para>
+
+<para><emphasis>Incorrect direct editing of the registry can cause your
+machine to fail. Then again, so can incorrect implementation of this 
+protocol. See "Liability:" above.</emphasis></para>
+
+<para>
+Bear in mind that each packet over-the-wire will have its origin in an
+API call.  Therefore, there are likely to be structures, enumerations
+and defines that are usefully documented elsewhere.
+</para>
+
+<para>
+This document is by no means complete or authoritative.  Missing sections
+include, but are not limited to:
+</para>
+
+
+<orderedlist>
+
+<listitem><para>Mappings of RIDs to usernames (and vice-versa).</para></listitem>
+
+<listitem><para>What a User ID is and what a Group ID is.</para></listitem>
+
+<listitem><para>The exact meaning/definition of various magic constants or enumerations.</para></listitem>
+
+<listitem><para>The reply error code and use of that error code when a
+workstation becomes a member of a domain (to be described later).  
+Failure to return this error code will make the workstation report 
+that it is already a member of the domain.</para></listitem>
+
+<listitem><para>the cryptographic side of the NetrServerPasswordSet command, 
+which would allow the workstation to change its password.  This password is
+used to generate the long-term session key.  [It is possible to reject this
+command, and keep the default workstation password].</para></listitem>
+
+</orderedlist>
+
+<sect2>
+<title>Sources</title>
+
+<simplelist>
+<member>cket Traces from Netmonitor (Service Pack 1 and above)</member>
+<member>ul Ashton and Luke Leighton's other "NT Domain" doc.</member>
+<member>FS documentation - cifs6.txt</member>
+<member>FS documentation - cifsrap2.txt</member>
+</simplelist>
+
+</sect2>
+
+<sect2>
+<title>Credits</title>
+
+<simplelist> 
+<member>Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.</member>
+<member>Duncan Stansfield: low-level analysis of MSRPC Pipes.</member>
+<member>Linus Nordberg: producing c-code from Paul's crypto spec.</member>
+<member>Windows Sourcer development team</member>
+</simplelist>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Notes and Structures</title>
+
+<sect2>
+<title>Notes</title>
+
+<orderedlist>
+<listitem><para>
+In the SMB Transact pipes, some "Structures", described here, appear to be
+4-byte aligned with the SMB header, at their start.  Exactly which
+"Structures" need aligning is not precisely known or documented.
+</para></listitem>
+
+<listitem><para>
+In the UDP NTLOGON Mailslots, some "Structures", described here, appear to be
+2-byte aligned with the start of the mailslot, at their start.
+</para></listitem>
+
+<listitem><para>
+Domain SID is of the format S-revision-version-auth1-auth2...authN.
+e.g S-1-5-123-456-789-123-456.  the 5 could be a sub-revision.
+</para></listitem>
+
+<listitem><para>
+any undocumented buffer pointers must be non-zero if the string buffer it
+refers to contains characters.  exactly what value they should be is unknown.
+0x0000 0002 seems to do the trick to indicate that the buffer exists.  a
+NULL buffer pointer indicates that the string buffer is of zero length.
+If the buffer pointer is NULL, then it is suspected that the structure it
+refers to is NOT put into (or taken out of) the SMB data stream.  This is
+empirically derived from, for example, the LSA SAM Logon response packet,
+where if the buffer pointer is NULL, the user information is not inserted
+into the data stream.  Exactly what happens with an array of buffer pointers
+is not known, although an educated guess can be made.
+</para></listitem>
+
+<listitem><para>
+an array of structures (a container) appears to have a count and a pointer.
+if the count is zero, the pointer is also zero.  no further data is put
+into or taken out of the SMB data stream.  if the count is non-zero, then
+the pointer is also non-zero.  immediately following the pointer is the
+count again, followed by an array of container sub-structures.  the count
+appears a third time after the last sub-structure.
+</para></listitem>
+</orderedlist>
+
+</sect2>
+
+<sect2>
+<title>Enumerations</title>
+
+<sect3>
+<title>MSRPC Header type</title>
+<para>command number in the msrpc packet header</para>
+
+<variablelist>
+<varlistentry>
+	<term>MSRPC_Request:</term>
+	<listitem><para>0x00</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>MSRPC_Response:</term>
+	<listitem><para>0x02</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>MSRPC_Bind:</term>
+	<listitem><para>0x0B</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>MSRPC_BindAck:</term>
+	<listitem><para>0x0C</para></listitem>
+</varlistentry>
+</variablelist>
+</sect3>
+
+<sect3>
+<title>MSRPC Packet info</title>
+
+<para>The meaning of these flags is undocumented</para>
+
+<variablelist>
+<varlistentry>
+	<term>FirstFrag:</term>
+	<listitem><para>0x01 </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LastFrag:</term>
+	<listitem><para>0x02 </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NotaFrag:</term>
+	<listitem><para>0x04  </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>RecRespond:</term>
+	<listitem><para>0x08  </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NoMultiplex:</term>
+	<listitem><para>0x10  </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NotForIdemp:</term>
+	<listitem><para>0x20  </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NotforBcast:</term>
+	<listitem><para>0x40  </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NoUuid:</term>
+	<listitem><para>0x80 </para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>Structures</title>
+
+<sect3><title>VOID *</title>
+<para>sizeof VOID* is 32 bits.</para>
+</sect3>
+
+<sect3><title>char</title>
+<para>sizeof char is 8 bits.</para>
+</sect3>
+
+<sect3><title>UTIME</title>
+<para>UTIME is 32 bits, indicating time in seconds since 01jan1970.  documented in cifs6.txt (section 3.5 page, page 30).</para>
+</sect3>
+
+<sect3><title>NTTIME</title>
+<para>NTTIME is 64 bits.  documented in cifs6.txt (section 3.5 page, page 30).</para>
+</sect3>
+
+<sect3>
+<title>DOM_SID (domain SID structure)</title>
+
+<variablelist>
+
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>num of sub-authorities in domain SID</para></listitem>
+</varlistentry>
+
+<varlistentry>
+	<term>UINT8</term>
+	<listitem><para>SID revision number</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT8</term>
+	<listitem><para>num of sub-authorities in domain SID</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT8[6]</term>
+	<listitem><para>6 bytes for domain SID - Identifier Authority.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+	<term>UINT16[n_subauths]</term>
+	<listitem><para>domain SID sub-authorities</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<para><emphasis>Note: the domain SID is documented elsewhere.</emphasis>
+</para>
+
+</sect3>
+
+<sect3>
+<title>STR (string)</title>
+
+<para>STR (string) is a char[] : a null-terminated string of ascii characters.</para>
+
+</sect3>
+
+<sect3>
+<title>UNIHDR (unicode string header) </title>
+
+<variablelist>
+
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>length of unicode string</para></listitem>
+</varlistentry>
+
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>max length of unicode string</para></listitem>
+</varlistentry>
+
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>4 - undocumented.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>UNIHDR2 (unicode string header plus buffer pointer)</title>
+
+<variablelist>
+
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>unicode string header</para></listitem>
+</varlistentry>
+
+
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>UNISTR (unicode string)</title>
+
+<variablelist>
+
+<varlistentry>
+	<term>UINT16[]</term>
+	<listitem><para>null-terminated string of unicode characters.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>NAME (length-indicated unicode string)</title>
+
+<variablelist>
+
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>length of unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16[]</term>
+	<listitem><para>null-terminated string of unicode characters.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>UNISTR2 (aligned unicode string)</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT8[]</term>
+	<listitem><para>padding to get unicode string 4-byte aligned with the start of the SMB header.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>max length of unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - undocumented</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>length of unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16[]</term>
+	<listitem><para>string of uncode characters</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>OBJ_ATTR (object attributes)</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>0x18 - length (in bytes) including the length field.</para></listitem></varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+<listitem><para>0 - root directory (pointer)</para></listitem></varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+<listitem><para>0 - object name (pointer)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>0 - attributes (undocumented)</para></listitem></varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+<listitem><para>0 - security descriptior (pointer)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - security quality of service</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>POL_HND (LSA policy handle)</title>
+
+<variablelist>
+<varlistentry>
+	<term>char[20]</term>
+	<listitem><para>policy handle</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>DOM_SID2 (domain SID structure, SIDS stored in unicode)</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>5 - SID type</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - undocumented</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR2</term>
+	<listitem><para>domain SID unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+	<listitem><para>domain SID unicode string</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para><emphasis>Note:	there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length.  this will need to be resolved.</emphasis></para>
+
+<para><emphasis>Note:	the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.</emphasis></para>
+
+</sect3>
+
+<sect3>
+<title>DOM_RID (domain RID structure)</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>5 - well-known SID.  1 - user SID (see ShowACLs)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>5 - undocumented</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>domain RID </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - domain index out of above reference domains</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>LOG_INFO (server, account, client structure)</title>
+
+<para><emphasis>Note:	logon server name starts with two '\' characters and is upper case.</emphasis></para>
+
+<para><emphasis>Note:	account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.</emphasis></para>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>logon server unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>account name unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>sec_chan - security channel type</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>logon client machine unicode string</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>CLNT_SRV (server, client names structure)</title>
+
+<para><emphasis>Note:	logon server name starts with two '\' characters and is upper case.</emphasis></para>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>logon server unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>logon client machine unicode string</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>CREDS (credentials + time stamp)</title>
+
+<variablelist>
+<varlistentry>
+	<term>char[8]</term>
+	<listitem><para>credentials</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UTIME</term>
+	<listitem><para>time stamp</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>CLNT_INFO2 (server, client structure, client credentials)</title>
+
+<para><emphasis>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks.  the presumed intention is to
+	maintain an authenticated request/response trail.</emphasis></para>
+
+<variablelist>
+<varlistentry>
+	<term>CLNT_SRV</term>
+	<listitem><para>client and server names</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+	<listitem><para>???? padding, for 4-byte alignment with SMB header.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>pointer to client credentials.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>CREDS</term>
+	<listitem><para>client-calculated credentials + client time</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>CLNT_INFO (server, account, client structure, client credentials)</title>
+<para><emphasis>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks.  the presumed intention is to maintain an authenticated request/response trail.</emphasis></para>
+
+<variablelist>
+<varlistentry>
+	<term>LOG_INFO</term>
+	<listitem><para>logon account info</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>CREDS</term>
+	<listitem><para>client-calculated credentials + client time</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>ID_INFO_1 (id info structure, auth level 1)</title>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>ptr_id_info_1</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>domain name unicode header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>param control</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT64</term>
+	<listitem><para>logon ID</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>user name unicode header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>workgroup name unicode header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>char[16]</term>
+	<listitem><para>arc4 LM OWF Password</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>char[16]</term>
+	<listitem><para>arc4 NT OWF Password</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>domain name unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>user name unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>workstation name unicode string</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>SAM_INFO (sam logon/logoff id info structure)</title>
+
+<para><emphasis>Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.</emphasis></para>
+
+<variablelist>
+<varlistentry>
+	<term>CLNT_INFO2</term>
+	<listitem><para>client identification/authentication info</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>pointer to return credentials.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>CRED</term>
+	<listitem><para>return credentials - ignored.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>logon level</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>switch value</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<para><programlisting>
+        switch (switch_value)
+        case 1:
+        {
+            ID_INFO_1     id_info_1;
+        }
+</programlisting></para>
+
+</sect3>
+
+<sect3>
+<title>GID (group id info)</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>group id</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>user attributes (only used by NT 3.1 and 3.51)</para></listitem></varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>DOM_REF (domain reference info)</title>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>num referenced domains?</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented domain name buffer pointer.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>32 - max number of entries</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>4 - num referenced domains?</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR2</term>
+	<listitem><para>domain name unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR2[num_ref_doms-1]</term>
+	<listitem><para>referenced domain unicode string headers</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+	<listitem><para>domain name unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>DOM_SID[num_ref_doms]</term>
+	<listitem><para>referenced domain SIDs</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>DOM_INFO (domain info, levels 3 and 5 are the same))</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT8[]</term>
+	<listitem><para>??? padding to get 4-byte alignment with start of SMB header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>domain name string length * 2</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>domain name string length * 2</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented domain name string buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+<listitem><para>undocumented domain SID string buffer pointer</para></listitem></varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+<listitem><para>domain name (unicode string)</para></listitem></varlistentry>
+<varlistentry>
+	<term>DOM_SID</term>
+	<listitem><para>domain SID</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>USER_INFO (user logon info)</title>
+
+<para><emphasis>Note: it would be nice to know what the 16 byte user session key is for.</emphasis></para>
+
+<variablelist>
+<varlistentry>
+	<term>NTTIME</term>
+	<listitem><para>logon time</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NTTIME</term>
+	<listitem><para>logoff time</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NTTIME</term>
+	<listitem><para>kickoff time</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NTTIME</term>
+	<listitem><para>password last set time</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NTTIME</term>
+	<listitem><para>password can change time</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NTTIME</term>
+	<listitem><para>password must change time</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>username unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>user's full name unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>logon script unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>profile path unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>home directory unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>home directory drive unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>logon count</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>bad password count</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>User ID</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>Group ID</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>num groups</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer to groups.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>user flags</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>char[16]</term>
+	<listitem><para>user session key</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>logon server unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNIHDR</term>
+	<listitem><para>logon domain unicode string header</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented logon domain id pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>char[40]</term>
+	<listitem><para>40 undocumented padding bytes.  future expansion?</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - num_other_sids?</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>NULL - undocumented pointer to other domain SIDs.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>username unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>user's full name unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>logon script unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>profile path unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>home directory unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>home directory drive unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>num groups</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>GID[num_groups]</term>
+	<listitem><para>group info</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>logon server unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>logon domain unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>DOM_SID</term>
+	<listitem><para>domain SID</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>DOM_SID[num_sids]</term>
+	<listitem><para>other domain SIDs?</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>SH_INFO_1_PTR (pointers to level 1 share info strings)</title>
+
+<para><emphasis>Note:	see cifsrap2.txt section5, page 10.</emphasis></para>
+
+<simplelist>
+<member>0 for shi1_type indicates a  Disk.</member>
+<member>1 for shi1_type indicates a  Print Queue.</member>
+<member>2 for shi1_type indicates a  Device.</member>
+<member>3 for shi1_type indicates an IPC pipe.</member>
+<member>0x8000 0000 (top bit set in shi1_type) indicates a hidden share.</member>
+</simplelist>
+
+<variablelist>
+
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>shi1_netname - pointer to net name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>shi1_type    - type of share.  0 - undocumented.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>shi1_remark  - pointer to comment.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>SH_INFO_1_STR (level 1 share info strings)</title>
+
+<variablelist>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>shi1_netname - unicode string of net name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>shi1_remark  - unicode string of comment.</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>SHARE_INFO_1_CTR</title>
+
+<para>share container with 0 entries:</para>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - EntriesRead</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - Buffer</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>share container with > 0 entries:</para>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>EntriesRead</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>non-zero - Buffer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>EntriesRead</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SH_INFO_1_PTR[EntriesRead]</term>
+	<listitem><para>share entry pointers</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SH_INFO_1_STR[EntriesRead]</term>
+	<listitem><para>share entry strings</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+	<listitem><para>padding to get unicode string 4-byte aligned with start of the SMB header.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>EntriesRead</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - padding</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>SERVER_INFO_101</title>
+
+<para><emphasis>Note:	see cifs6.txt section 6.4 - the fields described therein will be of assistance here.  for example, the type listed below is the 	same as fServerType, which is described in 6.4.1. </emphasis></para>
+
+<variablelist>
+<varlistentry>
+	<term>SV_TYPE_WORKSTATION</term>
+	<listitem><para>0x00000001  All workstations</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_SERVER</term>
+	<listitem><para>0x00000002  All servers</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_SQLSERVER</term>
+	<listitem><para>0x00000004  Any server running with SQL server</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_DOMAIN_CTRL</term>
+	<listitem><para>0x00000008  Primary domain controller</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_DOMAIN_BAKCTRL</term>
+	<listitem><para>0x00000010  Backup domain controller</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_TIME_SOURCE</term>
+	<listitem><para>0x00000020  Server running the timesource service</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_AFP</term>
+	<listitem><para>0x00000040  Apple File Protocol servers</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_NOVELL</term>
+	<listitem><para>0x00000080  Novell servers</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_DOMAIN_MEMBER</term>
+	<listitem><para>0x00000100  Domain Member</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_PRINTQ_SERVER</term>
+	<listitem><para>0x00000200  Server sharing print queue</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_DIALIN_SERVER</term>
+	<listitem><para>0x00000400  Server running dialin service.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_XENIX_SERVER</term>
+	<listitem><para>0x00000800  Xenix server</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_NT</term>
+	<listitem><para>0x00001000  NT server</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_WFW</term>
+	<listitem><para>0x00002000  Server running Windows for </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_SERVER_NT</term>
+	<listitem><para>0x00008000  Windows NT non DC server</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_POTENTIAL_BROWSER</term>
+	<listitem><para>0x00010000  Server that can run the browser service</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_BACKUP_BROWSER</term>
+	<listitem><para>0x00020000  Backup browser server</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_MASTER_BROWSER</term>
+	<listitem><para>0x00040000  Master browser server</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_DOMAIN_MASTER</term>
+	<listitem><para>0x00080000  Domain Master Browser server</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_LOCAL_LIST_ONLY</term>
+	<listitem><para>0x40000000  Enumerate only entries marked "local"</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SV_TYPE_DOMAIN_ENUM</term>
+	<listitem><para>0x80000000  Enumerate Domains. The pszServer and pszDomain parameters must be NULL.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>500 - platform_id</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>pointer to name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>5 - major version</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>4 - minor version</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>type (SV_TYPE_... bit field)</para></listitem></varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>pointer to comment</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>sv101_name - unicode string of server name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>sv_101_comment  - unicode string of server comment.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+	<listitem><para>padding to get unicode string 4-byte aligned with start of the SMB header.</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>MSRPC over Transact Named Pipe</title>
+
+<para>For details on the SMB Transact Named Pipe, see cifs6.txt</para>
+
+<sect2>
+<title>MSRPC Pipes</title>
+
+<para>
+The MSRPC is conducted over an SMB Transact Pipe with a name of 
+<filename>\PIPE\</filename>.  You must first obtain a 16 bit file handle, by
+sending a SMBopenX with the pipe name <filename>\PIPE\srvsvc</filename> for
+example.  You can then perform an SMB Trans,
+and must carry out an SMBclose on the file handle once you are finished.
+</para>
+
+<para>
+Trans Requests must be sent with two setup UINT16s, no UINT16 params (none
+known about), and UINT8 data parameters sufficient to contain the MSRPC
+header, and MSRPC data.  The first UINT16 setup parameter must be either
+0x0026 to indicate an RPC, or 0x0001 to indicate Set Named Pipe Handle
+state.  The second UINT16 parameter must be the file handle for the pipe,
+obtained above.
+</para>
+
+<para>
+The Data section for an API Command of 0x0026 (RPC pipe) in the Trans
+Request is the RPC Header, followed by the RPC Data.  The Data section for
+an API Command of 0x0001 (Set Named Pipe Handle state) is two bytes.  The
+only value seen for these two bytes is 0x00 0x43.
+</para>
+
+<para>
+MSRPC Responses are sent as response data inside standard SMB Trans
+responses, with the MSRPC Header, MSRPC Data and MSRPC tail.
+</para>
+
+<para>
+It is suspected that the Trans Requests will need to be at least 2-byte
+aligned (probably 4-byte).  This is standard practice for SMBs.  It is also
+independent of the observed 4-byte alignments with the start of the MSRPC
+header, including the 4-byte alignment between the MSRPC header and the
+MSRPC data.
+</para>
+
+<para>
+First, an SMBtconX connection is made to the IPC$ share.  The connection
+must be made using encrypted passwords, not clear-text.  Then, an SMBopenX
+is made on the pipe.  Then, a Set Named Pipe Handle State must be sent,
+after which the pipe is ready to accept API commands.  Lastly, and SMBclose
+is sent.
+</para>
+
+<para>
+To be resolved:
+</para>
+
+<para>
+lkcl/01nov97 there appear to be two additional bytes after the null-terminated \PIPE\ name for the RPC pipe.  Values seen so far are
+listed below:</para>
+
+<para><programlisting>
+        initial SMBopenX request:         RPC API command 0x26 params:
+        "\\PIPE\\lsarpc"                  0x65 0x63; 0x72 0x70; 0x44 0x65;
+        "\\PIPE\\srvsvc"                  0x73 0x76; 0x4E 0x00; 0x5C 0x43;
+</programlisting></para>
+
+</sect2>
+
+<sect2>
+<title>Header</title>
+
+<para>[section to be rewritten, following receipt of work by Duncan Stansfield]</para>
+
+<para>Interesting note: if you set packed data representation to 0x0100 0000
+then all 4-byte and 2-byte word ordering is turned around!</para>
+
+<para>The start of each of the NTLSA and NETLOGON named pipes begins with:</para>
+
+<segmentedlist>
+<segtitle>offset</segtitle><segtitle>Variable type</segtitle><segtitle>Variable data</segtitle>
+<seglistitem><seg>00</seg><seg>UINT8</seg><seg>5 - RPC major version</seg></seglistitem>
+<seglistitem><seg>01</seg><seg>UINT8</seg><seg>0 - RPC minor version</seg></seglistitem>
+<seglistitem><seg>02</seg><seg>UINT8</seg><seg>2 - RPC response packet</seg></seglistitem>
+<seglistitem><seg>03</seg><seg>UINT8</seg><seg>3 - (FirstFrag bit-wise or with LastFrag)</seg></seglistitem>
+<seglistitem><seg>04</seg><seg>UINT32</seg><seg>0x1000 0000 - packed data representation</seg></seglistitem>
+<seglistitem><seg>08</seg><seg>UINT16</seg><seg>fragment length - data size (bytes) inc header and tail.</seg></seglistitem>
+<seglistitem><seg>0A</seg><seg>UINT16</seg><seg>0 - authentication length </seg></seglistitem>
+<seglistitem><seg>0C</seg><seg>UINT32</seg><seg>call identifier. matches 12th UINT32 of incoming RPC data.</seg></seglistitem>
+<seglistitem><seg>10</seg><seg>UINT32</seg><seg>allocation hint - data size (bytes) minus header and tail.</seg></seglistitem>
+<seglistitem><seg>14</seg><seg>UINT16</seg><seg>0 - presentation context identifier</seg></seglistitem>
+<seglistitem><seg>16</seg><seg>UINT8</seg><seg>0 - cancel count</seg></seglistitem>
+<seglistitem><seg>17</seg><seg>UINT8</seg><seg>in replies: 0 - reserved; in requests: opnum - see #defines.</seg></seglistitem>
+<seglistitem><seg>18</seg><seg>......</seg><seg>start of data (goes on for allocation_hint bytes)</seg></seglistitem>
+</segmentedlist>
+
+<sect3>
+<title>RPC_Packet for request, response, bind and bind acknowledgement</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT8 versionmaj</term>
+<listitem><para>reply same as request (0x05)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8 versionmin</term>
+<listitem><para>reply same as request (0x00)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8 type</term>
+<listitem><para>one of the MSRPC_Type enums</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8 flags</term>
+<listitem><para>reply same as request (0x00 for Bind, 0x03 for Request)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32 representation</term>
+<listitem><para>reply same as request (0x00000010)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 fraglength</term>
+<listitem><para>the length of the data section of the SMB trans packet</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 authlength</term>
+	<listitem><para></para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32 callid</term>
+<listitem><para>call identifier. (e.g. 0x00149594)</para></listitem></varlistentry>
+<varlistentry>
+	<term>* stub USE TvPacket</term>
+<listitem><para>the remainder of the packet depending on the "type"</para></listitem></varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Interface identification</title>
+
+<para>the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc</para>
+
+<para><programlisting>
+abstract (0x4B324FC8, 0x01D31670, 0x475A7812, 0x88E16EBF, 0x00000003)
+transfer (0x8A885D04, 0x11C91CEB, 0x0008E89F, 0x6048102B, 0x00000002)
+</programlisting></para>
+
+</sect3>
+
+<sect3>
+<title>RPC_Iface RW</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT8 byte[16]</term>
+<listitem><para>16 bytes of number</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32 version</term>
+<listitem><para>the interface number</para></listitem></varlistentry>
+</variablelist>
+
+
+</sect3>
+
+<sect3>
+<title>RPC_ReqBind RW</title>
+
+<para>the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck</para>
+
+<variablelist>
+<varlistentry>
+	<term>UINT16 maxtsize</term>
+<listitem><para>maximum transmission fragment size (0x1630)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 maxrsize</term>
+<listitem><para>max receive fragment size (0x1630)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32 assocgid</term>
+<listitem><para>associated group id (0x0)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32 numelements</term>
+<listitem><para>the number of elements (0x1)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 contextid</term>
+<listitem><para>presentation context identifier (0x0)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8 numsyntaxes</term>
+<listitem><para>the number of syntaxes (has always been 1?)(0x1)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+<listitem><para>4-byte alignment padding, against SMB header</para></listitem></varlistentry>
+<varlistentry>
+	<term>* abstractint USE RPC_Iface</term>
+<listitem><para>num and vers. of interface client is using</para></listitem></varlistentry>
+<varlistentry>
+	<term>* transferint USE RPC_Iface</term>
+	<listitem><para>num and vers. of interface to use for replies</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>RPC_Address RW</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT16 length</term>
+<listitem><para>length of the string including null terminator</para></listitem></varlistentry>
+<varlistentry>
+	<term>* port USE string</term>
+<listitem><para>the string above in single byte, null terminated form</para></listitem></varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>RPC_ResBind RW</title>
+
+<para>the response to place after the header in the reply packet</para>
+
+<variablelist>
+<varlistentry>
+	<term>UINT16 maxtsize</term>
+<listitem><para>same as request</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 maxrsize</term>
+<listitem><para>same as request</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32 assocgid</term>
+<listitem><para>zero</para></listitem></varlistentry>
+<varlistentry>
+	<term>* secondaddr USE RPC_Address</term>
+<listitem><para>the address string, as described earlier</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+<listitem><para>4-byte alignment padding, against SMB header</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8 numresults</term>
+<listitem><para>the number of results (0x01)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+<listitem><para>4-byte alignment padding, against SMB header</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 result</term>
+<listitem><para>result (0x00 = accept)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 reason</term>
+<listitem><para>reason (0x00 = no reason specified)</para></listitem></varlistentry>
+<varlistentry>
+	<term>* transfersyntax USE RPC_Iface</term>
+<listitem><para>the transfer syntax from the request</para></listitem></varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>RPC_ReqNorm RW</title>
+
+<para>the remainder of the packet after the header for every other other request</para>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32 allochint</term>
+<listitem><para>the size of the stub data in bytes</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 prescontext</term>
+<listitem><para>presentation context identifier (0x0)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 opnum</term>
+<listitem><para>operation number (0x15)</para></listitem></varlistentry>
+<varlistentry>
+	<term>* stub USE TvPacket</term>
+<listitem><para>a packet dependent on the pipe name (probably the interface) and the op number)</para></listitem></varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>RPC_ResNorm RW</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32 allochint</term>
+<listitem><para># size of the stub data in bytes</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16 prescontext</term>
+<listitem><para># presentation context identifier (same as request)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8 cancelcount</term>
+<listitem><para># cancel count? (0x0)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8 reserved</term>
+<listitem><para># 0 - one byte padding</para></listitem></varlistentry>
+<varlistentry>
+	<term>* stub USE TvPacket</term>
+<listitem><para># the remainder of the reply</para></listitem></varlistentry>
+</variablelist>
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>Tail</title>
+
+<para>The end of each of the NTLSA and NETLOGON named pipes ends with:</para>
+
+<variablelist>
+<varlistentry>
+	<term>......</term>
+	<listitem><para>end of data</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>return code</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect2>
+
+<sect2>
+<title>RPC Bind / Bind Ack</title>
+
+<para>
+RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc)
+with a "transfer syntax" (see RPC_Iface structure).  The purpose for doing
+this is unknown.
+</para>
+
+<para><emphasis>Note: The RPC_ResBind SMB Transact request is sent with two uint16 setup parameters.  The first is 0x0026; the second is the file handle
+	returned by the SMBopenX Transact response.</emphasis></para>
+
+<para><emphasis>Note:	The RPC_ResBind members maxtsize, maxrsize and assocgid are the same in the response as the same members in the RPC_ReqBind.  The
+	RPC_ResBind member transfersyntax is the same in the response as
+	the</emphasis></para>
+
+<para><emphasis>Note:	The RPC_ResBind response member secondaddr contains the name of what is presumed to be the service behind the RPC pipe.  The
+	mapping identified so far is:</emphasis></para>
+
+<variablelist>
+
+<varlistentry>
+	<term>initial SMBopenX request:</term>
+	<listitem><para>RPC_ResBind response:</para></listitem>
+</varlistentry>
+
+<varlistentry>
+	<term>"\\PIPE\\srvsvc"</term>
+	<listitem><para>"\\PIPE\\ntsvcs"</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>"\\PIPE\\samr"</term>
+	<listitem><para>"\\PIPE\\lsass"</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>"\\PIPE\\lsarpc"</term>
+	<listitem><para>"\\PIPE\\lsass"</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>"\\PIPE\\wkssvc"</term>
+	<listitem><para>"\\PIPE\\wksvcs"</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>"\\PIPE\\NETLOGON"</term>
+	<listitem><para>"\\PIPE\\NETLOGON"</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para><emphasis>Note:	The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.</emphasis></para>
+
+<para>Request:</para>
+
+<simplelist>
+<member>RPC_Packet</member>
+<member>RPC_ReqBind</member>
+</simplelist>
+
+<para>Response:</para>
+<simplelist>
+<member>RPC_Packet</member>
+<member>RPC_ResBind</member>
+</simplelist>
+
+</sect2>
+
+<sect2>
+<title>NTLSA Transact Named Pipe</title>
+
+<para>The sequence of actions taken on this pipe are:</para>
+
+<simplelist>
+<member>Establish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</member>
+<member>Open an RPC Pipe with the name "\\PIPE\\lsarpc".  Store the file handle.</member>
+<member>Using the file handle, send a Set Named Pipe Handle state to 0x4300.</member>
+<member>Send an LSA Open Policy request.  Store the Policy Handle.</member>
+<member>Using the Policy Handle, send LSA Query Info Policy requests, etc.</member>
+<member>Using the Policy Handle, send an LSA Close.</member>
+<member>Close the IPC$ share.</member>
+</simplelist>
+
+<para>Defines for this pipe, identifying the query are:</para>
+<variablelist>
+<varlistentry>
+	<term>LSA Open Policy:</term>
+	<listitem><para>0x2c</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA Query Info Policy:</term>
+	<listitem><para>0x07</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA Enumerate Trusted Domains:</term>
+	<listitem><para>0x0d</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA Open Secret:</term>
+	<listitem><para>0xff</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA Lookup SIDs:</term>
+	<listitem><para>0xfe</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA Lookup Names:</term>
+	<listitem><para>0xfd</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA Close:</term>
+	<listitem><para>0x00</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect2>
+
+<sect2>
+<title>LSA Open Policy</title>
+
+<para><emphasis>Note:	The policy handle can be anything you like.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>server name - unicode string starting with two '\'s</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>OBJ_ATTR</term>
+	<listitem><para>object attributes</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>1 - desired access</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+
+<varlistentry>
+	<term>POL_HND</term>
+	<listitem><para>LSA policy handle</para></listitem>
+</varlistentry>
+
+<varlistentry>
+	<term>return</term>
+	<listitem><para>0 - indicates success</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>LSA Query Info Policy</title>
+
+<para><emphasis>Note:	The info class in response must be the same as that in the request.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>POL_HND</term>
+<listitem><para>LSA policy handle</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+<listitem><para>info class (also a policy handle?)</para></listitem></varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>info class (same as info class in request).</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<para><programlisting>
+switch (info class)
+case 3:
+case 5:
+{
+DOM_INFO domain info, levels 3 and 5 (are the same).
+}
+
+return    0 - indicates success
+</programlisting></para>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>LSA Enumerate Trusted Domains</title>
+
+<sect3>
+<title>Request</title>
+
+<para>no extra data</para>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - enumeration context</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - entries read</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - trust information</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>return</term>
+	<listitem><para>0x8000 001a - "no trusted domains" success code</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>LSA Open Secret</title>
+
+<sect3>
+<title>Request</title>
+
+<para>no extra data</para>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - undocumented</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - undocumented</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - undocumented</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - undocumented</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>0 - undocumented</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>return    0x0C00 0034 - "no such secret" success code</para>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>LSA Close</title>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>POL_HND</term>
+	<listitem><para>policy handle to be closed</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>POL_HND</term>
+<listitem><para>0s - closed policy handle (all zeros)</para></listitem></varlistentry>
+</variablelist>
+
+<para>return    0 - indicates success</para>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>LSA Lookup SIDS</title>
+
+<para><emphasis>Note:	num_entries in response must be same as num_entries in request.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>POL_HND</term>
+	<listitem><para>LSA policy handle</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>num_entries</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented domain SID buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented domain name buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*[num_entries] undocumented domain SID pointers to be looked up.
+</term>
+<listitem><para>DOM_SID[num_entries] domain SIDs to be looked up.</para></listitem></varlistentry>
+<varlistentry>
+	<term>char[16]</term>
+	<listitem><para>completely undocumented 16 bytes.</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>DOM_REF</term>
+<listitem><para>domain reference response</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>num_entries (listed above)</para></listitem></varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+<listitem><para>undocumented buffer pointer</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>num_entries (listed above)</para></listitem></varlistentry>
+<varlistentry>
+	<term>DOM_SID2[num_entries]</term>
+<listitem><para>domain SIDs (from Request, listed above).</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>num_entries (listed above)</para></listitem></varlistentry>
+</variablelist>
+
+<para>return                0 - indicates success</para>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>LSA Lookup Names</title>
+
+<para><emphasis>Note:	num_entries in response must be same as num_entries in request.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>POL_HND</term>
+	<listitem><para>LSA policy handle</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>num_entries</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>num_entries</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented domain SID buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented domain name buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>NAME[num_entries]</term>
+	<listitem><para>names to be looked up.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>char[]</term>
+	<listitem><para>undocumented bytes - falsely translated SID structure?</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>DOM_REF</term>
+<listitem><para>domain reference response</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>num_entries (listed above)</para></listitem></varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+<listitem><para>undocumented buffer pointer</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>num_entries (listed above)</para></listitem></varlistentry>
+<varlistentry>
+	<term>DOM_RID[num_entries]</term>
+<listitem><para>domain SIDs (from Request, listed above).</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>num_entries (listed above)</para></listitem></varlistentry>
+</variablelist>
+
+<para>return                0 - indicates success</para>
+
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>NETLOGON rpc Transact Named Pipe</title>
+
+<para>The sequence of actions taken on this pipe are:</para>
+
+<simplelist>
+<member>tablish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</member>
+<member>en an RPC Pipe with the name "\\PIPE\\NETLOGON".  Store the file handle.</member>
+<member>ing the file handle, send a Set Named Pipe Handle state to 0x4300.</member>
+<member>eate Client Challenge. Send LSA Request Challenge.  Store Server Challenge.</member>
+<member>lculate Session Key.  Send an LSA Auth 2 Challenge.  Store Auth2 Challenge.</member>
+<member>lc/Verify Client Creds.  Send LSA Srv PW Set.  Calc/Verify Server Creds.</member>
+<member>lc/Verify Client Creds.  Send LSA SAM Logon .  Calc/Verify Server Creds.</member>
+<member>lc/Verify Client Creds.  Send LSA SAM Logoff.  Calc/Verify Server Creds.</member>
+<member>ose the IPC$ share.</member>
+</simplelist>
+
+<para>Defines for this pipe, identifying the query are</para>
+
+<variablelist>
+<varlistentry>
+	<term>LSA Request Challenge:</term>
+	<listitem><para>0x04</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA Server Password Set:</term>
+	<listitem><para>0x06</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA SAM Logon:</term>
+	<listitem><para>0x02</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA SAM Logoff:</term>
+	<listitem><para>0x03</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA Auth 2:</term>
+	<listitem><para>0x0f</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>LSA Logon Control:</term>
+	<listitem><para>0x0e</para></listitem>
+</varlistentry>
+</variablelist>
+
+<sect2>
+<title>LSA Request Challenge</title>
+
+<para><emphasis>Note:	logon server name starts with two '\' characters and is upper case.</emphasis></para>
+
+<para><emphasis>Note:	logon client is the machine, not the user.</emphasis></para>
+
+<para><emphasis>Note:	the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case).  there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>logon server unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>logon client unicode string</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>char[8]</term>
+	<listitem><para>client challenge</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>char[8]</term>
+	<listitem><para>server challenge</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>return    0 - indicates success</para>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>LSA Authenticate 2</title>
+
+<para><emphasis>Note:	in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</emphasis></para>
+
+<para><emphasis>Note:	neg_flags in the response is the same as that in the request.</emphasis></para>
+
+<para><emphasis>Note:	you must take a copy of the client-calculated credentials received 	here, because they will be used in subsequent authentication packets.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>LOG_INFO</term>
+	<listitem><para>client identification info</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>char[8]</term>
+	<listitem><para>client-calculated credentials</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+<listitem><para>padding to 4-byte align with start of SMB header.</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>neg_flags - negotiated flags (usual value is 0x0000 01ff)</para></listitem></varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>char[8]</term>
+	<listitem><para>server credentials.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>neg_flags - same as neg_flags in request.</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>return    0 - indicates success.  failure value unknown.</para>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>LSA Server Password Set</title>
+
+<para><emphasis>Note: the new password is suspected to be a DES encryption using the old password to generate the key.</emphasis></para>
+
+<para><emphasis>Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</emphasis></para>
+
+<para><emphasis>Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.</emphasis></para>
+
+<para><emphasis>Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>CLNT_INFO</term>
+	<listitem><para>client identification/authentication info</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>char[]</term>
+	<listitem><para>new password - undocumented.</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>CREDS</term>
+	<listitem><para>server credentials.  server time stamp appears to be ignored.</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>return    0 - indicates success; 0xC000 006a indicates failure</para>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>LSA SAM Logon</title>
+
+<para><emphasis>
+Note:	valid_user is True iff the username and password hash are valid for
+	the requested domain.
+</emphasis></para>
+
+<sect3>
+<title>Request</title>
+<variablelist>
+<varlistentry>
+	<term>SAM_INFO</term>
+	<listitem><para>sam_id structure</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>CREDS</term>
+	<listitem><para>server credentials.  server time stamp appears to be ignored.</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para><programlisting>
+if (valid_user)
+{
+	UINT16      3 - switch value indicating USER_INFO structure.
+    VOID*     non-zero - pointer to USER_INFO structure
+    USER_INFO user logon information
+
+    UINT32    1 - Authoritative response; 0 - Non-Auth?
+
+    return    0 - indicates success
+}
+else
+{
+	UINT16    0 - switch value.  value to indicate no user presumed.
+    VOID*     0x0000 0000 - indicates no USER_INFO structure.
+
+    UINT32    1 - Authoritative response; 0 - Non-Auth?
+
+    return    0xC000 0064 - NT_STATUS_NO_SUCH_USER.
+}
+</programlisting></para>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>LSA SAM Logoff</title>
+
+<para><emphasis>
+Note:	presumably, the SAM_INFO structure is validated, and a (currently
+	undocumented) error code returned if the Logoff is invalid.
+</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>SAM_INFO</term>
+	<listitem><para>sam_id structure</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>undocumented buffer pointer</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>CREDS</term>
+	<listitem><para>server credentials.  server time stamp appears to be ignored.</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>return      0 - indicates success.  undocumented failure indication.</para>
+
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>\\MAILSLOT\NET\NTLOGON</title>
+
+<para><emphasis>
+Note:	mailslots will contain a response mailslot, to which the response
+	should be sent.  the target NetBIOS name is REQUEST_NAME&lt;20&gt;, where
+	REQUEST_NAME is the name of the machine that sent the request.
+</emphasis></para>
+
+<sect2>
+<title>Query for PDC</title>
+
+<para><emphasis>Note:	NTversion, LMNTtoken, LM20token in response are the same as those 	given in the request.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>0x0007 - Query for PDC</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>STR</term>
+	<listitem><para>machine name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>STR</term>
+	<listitem><para>response mailslot</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+	<listitem><para>padding to 2-byte align with start of mailslot.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+	<listitem><para>machine name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>NTversion</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>LMNTtoken</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>LM20token</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT16</term>
+<listitem><para>0x000A - Respose to Query for PDC</para></listitem></varlistentry>
+<varlistentry>
+	<term>STR</term>
+<listitem><para>machine name (in uppercase)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+	<listitem><para>padding to 2-byte align with start of mailslot.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+	<listitem><para>machine name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+<listitem><para>domain name</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>NTversion (same as received in request)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+<listitem><para>LMNTtoken (same as received in request)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+<listitem><para>LM20token (same as received in request)</para></listitem></varlistentry>
+</variablelist>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>SAM Logon</title>
+
+<para><emphasis>Note: machine name in response is preceded by two '\' characters.</emphasis></para>
+
+<para><emphasis>Note:	NTversion, LMNTtoken, LM20token in response are the same as those given in the request.</emphasis></para>
+
+<para><emphasis>Note:	user name in the response is presumably the same as that in the request.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>0x0012 - SAM Logon</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>request count</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+	<listitem><para>machine name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+	<listitem><para>user name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>STR</term>
+	<listitem><para>response mailslot</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>alloweable account</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>domain SID size</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>char[sid_size]</term>
+	<listitem><para>domain SID, of sid_size bytes.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+	<listitem><para>???? padding to 4? 2? -byte align with start of mailslot.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>NTversion</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>LMNTtoken</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>LM20token</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>0x0013 - Response to SAM Logon</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+	<listitem><para>machine name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+	<listitem><para>user name - workstation trust account</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UNISTR</term>
+	<listitem><para>domain name </para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>NTversion</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>LMNTtoken</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT16</term>
+	<listitem><para>LM20token</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>SRVSVC Transact Named Pipe</title>
+
+<para>Defines for this pipe, identifying the query are:</para>
+
+<variablelist>
+<varlistentry>
+	<term>Net Share Enum</term>
+	<listitem><para>0x0f</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Net Server Get Info</term>
+	<listitem><para>0x15</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<sect2>
+<title>Net Share Enum</title>
+
+<para><emphasis>Note:	share level and switch value in the response are presumably the same as those in the request.</emphasis></para>
+
+<para><emphasis>Note:	cifsrap2.txt (section 5) may be of limited assistance here.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>VOID*</term>
+<listitem><para>pointer (to server name?)</para></listitem></varlistentry>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>server name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT8[]</term>
+	<listitem><para>padding to get unicode string 4-byte aligned with the start of the SMB header.</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>share level</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>switch value</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>pointer to SHARE_INFO_1_CTR</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SHARE_INFO_1_CTR</term>
+	<listitem><para>share info with 0 entries</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+<listitem><para>preferred maximum length (0xffff ffff)</para></listitem></varlistentry>
+</variablelist>
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>share level</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>switch value</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+<listitem><para>pointer to SHARE_INFO_1_CTR</para></listitem></varlistentry>
+<varlistentry>
+	<term>SHARE_INFO_1_CTR</term>
+<listitem><para>share info (only added if share info ptr is non-zero)</para></listitem></varlistentry>
+</variablelist>
+
+<para>return            0 - indicates success</para>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>Net Server Get Info</title>
+
+<para><emphasis>Note:	level is the same value as in the request.</emphasis></para>
+
+<sect3>
+<title>Request</title>
+
+<variablelist>
+<varlistentry>
+	<term>UNISTR2</term>
+	<listitem><para>server name</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>switch level</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>Response</title>
+
+<variablelist>
+<varlistentry>
+	<term>UINT32</term>
+	<listitem><para>switch level</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>VOID*</term>
+	<listitem><para>pointer to SERVER_INFO_101</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>SERVER_INFO_101</term>
+<listitem><para>server info (only added if server info ptr is non-zero)</para></listitem></varlistentry>
+</variablelist>
+
+<para>return            0 - indicates success</para>
+
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Cryptographic side of NT Domain Authentication</title>
+
+<sect2>
+<title>Definitions</title>
+
+<variablelist>
+<varlistentry>
+<term>Add(A1,A2)</term>
+<listitem><para>Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>E(K,D)</term>
+<listitem><para>DES ECB encryption of 8 byte data D using 7 byte key K</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>lmowf()</term>
+<listitem><para>Lan man hash</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>ntowf()</term>
+<listitem><para>NT hash</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>PW</term>
+<listitem><para>md4(machine_password) == md4(lsadump $machine.acc) ==
+pwdump(machine$) (initially) == md4(lmowf(unicode(machine)))
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>ARC4(K,Lk,D,Ld)</term>
+<listitem><para>ARC4 encryption of data D of length Ld with key K of length Lk</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>v[m..n(,l)]</term>
+<listitem><para>subset of v from bytes m to n, optionally padded with zeroes to length l</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Cred(K,D)</term>
+<listitem><para>E(K[7..7,7],E(K[0..6],D)) computes a credential</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Time()</term>
+<listitem><para>4 byte current time</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Cc,Cs</term>
+<listitem><para>8 byte client and server challenges Rc,Rs: 8 byte client and server credentials</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect2>
+
+<sect2>
+<title>Protocol</title>
+
+<programlisting>
+C-&gt;S ReqChal,Cc
+S-&gt;C Cs
+</programlisting>
+
+<programlisting>
+C &amp; S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))
+</programlisting>
+
+<programlisting>
+C: Rc = Cred(Ks,Cc)
+C-&gt;S Authenticate,Rc
+S: Rs = Cred(Ks,Cs), assert(Rc == Cred(Ks,Cc))
+S-&gt;C Rs
+C: assert(Rs == Cred(Ks,Cs))
+</programlisting>
+
+<para>
+On joining the domain the client will optionally attempt to change its
+password and the domain controller may refuse to update it depending
+on registry settings. This will also occur weekly afterwards.
+</para>
+
+<programlisting>
+C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc)
+C-&gt;S ServerPasswordSet,Rc',Tc,arc4(Ks[0..7,16],lmowf(randompassword())
+C: Rc = Cred(Ks,Rc+Tc+1)
+S: assert(Rc' == Cred(Ks,Rc+Tc)), Ts = Time()
+S: Rs' = Cred(Ks,Rs+Tc+1)
+S-&gt;C Rs',Ts
+C: assert(Rs' == Cred(Ks,Rs+Tc+1))
+S: Rs = Rs'
+</programlisting>
+
+<para>
+User: U with password P wishes to login to the domain (incidental data
+such as workstation and domain omitted)
+</para>
+
+<programlisting>
+C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc)
+C-&gt;S NetLogonSamLogon,Rc',Tc,U,arc4(Ks[0..7,16],16,ntowf(P),16), arc4(Ks[0..7,16],16,lmowf(P),16)
+S: assert(Rc' == Cred(Ks,Rc+Tc)) assert(passwords match those in SAM)
+S: Ts = Time()
+</programlisting>
+
+<programlisting>
+S-&gt;C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc)
+C: assert(Rs == Cred(Ks,Cred(Rc+Tc+1))
+C: Rc = Cred(Ks,Rc+Tc+1)
+</programlisting>
+
+</sect2>
+
+<sect2>
+<title>Comments</title>
+
+<para>
+On first joining the domain the session key could be computed by
+anyone listening in on the network as the machine password has a well
+known value. Until the machine is rebooted it will use this session
+key to encrypt NT and LM one way functions of passwords which are
+password equivalents. Any user who logs in before the machine has been
+rebooted a second time will have their password equivalent exposed. Of
+course the new machine password is exposed at this time anyway.
+</para>
+
+<para>
+None of the returned user info such as logon script, profile path and
+SIDs *appear* to be protected by anything other than the TCP checksum.
+</para>
+
+<para>
+The server time stamps appear to be ignored.
+</para>
+
+<para>
+The client sends a ReturnAuthenticator in the SamLogon request which I
+can't find a use for.  However its time is used as the timestamp
+returned by the server.
+</para>
+
+<para>
+The password OWFs should NOT be sent over the network reversibly
+encrypted. They should be sent using ARC4(Ks,md4(owf)) with the server
+computing the same function using the owf values in the SAM.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>SIDs and RIDs</title>
+
+<para>
+SIDs and RIDs are well documented elsewhere.
+</para>
+
+<para>
+A SID is an NT Security ID (see DOM_SID structure).  They are of the form:
+</para>
+
+<simplelist>
+<member>revision-NN-SubAuth1-SubAuth2-SubAuth3... </member>
+<member>revision-0xNNNNNNNNNNNN-SubAuth1-SubAuth2-SubAuth3...</member>
+</simplelist>
+
+<para>
+currently, the SID revision is 1.
+The Sub-Authorities are known as Relative IDs (RIDs).
+</para>
+
+<sect2>
+<title>Well-known SIDs</title>
+
+<sect3>
+<title>Universal well-known SIDs</title>
+
+<variablelist>
+<varlistentry>
+	<term>Null SID</term>
+	<listitem><para>S-1-0-0</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>World</term>
+	<listitem><para>S-1-1-0</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Local</term>
+	<listitem><para>S-1-2-0</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Creator Owner ID</term>
+	<listitem><para>S-1-3-0</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Creator Group ID</term>
+	<listitem><para>S-1-3-1</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Creator Owner Server ID</term>
+	<listitem><para>S-1-3-2</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Creator Group Server ID</term>
+	<listitem><para>S-1-3-3</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>(Non-unique IDs)</term>
+	<listitem><para>S-1-4</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3>
+<title>NT well-known SIDs</title>
+
+<variablelist>
+<varlistentry>
+	<term>NT Authority</term>
+	<listitem><para>S-1-5</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Dialup</term>
+	<listitem><para>S-1-5-1</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Network</term>
+	<listitem><para>S-1-5-2</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Batch</term>
+	<listitem><para>S-1-5-3</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Interactive</term>
+	<listitem><para>S-1-5-4</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Service</term>
+<listitem><para>S-1-5-6</para></listitem></varlistentry>
+<varlistentry>
+	<term>AnonymousLogon(aka null logon session)</term>
+	<listitem><para>S-1-5-7</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>Proxy</term>
+<listitem><para>S-1-5-8</para></listitem></varlistentry>
+<varlistentry>
+	<term>ServerLogon(aka domain controller account)</term>
+	<listitem><para>S-1-5-8</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>(Logon IDs)</term>
+	<listitem><para>S-1-5-5-X-Y</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>(NT non-unique IDs)</term>
+	<listitem><para>S-1-5-0x15-...</para></listitem>
+</varlistentry>
+<varlistentry>
+	<term>(Built-in domain)</term>
+	<listitem><para>s-1-5-0x20</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>Well-known RIDS</title>
+
+<para>
+A RID is a sub-authority value, as part of either a SID, or in the case
+of Group RIDs, part of the DOM_GID structure, in the USER_INFO_1
+structure, in the LSA SAM Logon response.
+</para>
+
+<sect3>
+<title>Well-known RID users</title>
+
+<segmentedlist>
+<segtitle>Groupname</segtitle>
+<segtitle>????</segtitle>
+<segtitle>RID</segtitle>
+<seglistitem><seg>DOMAIN_USER_RID_ADMIN</seg><seg>0x0000</seg><seg>01F4</seg></seglistitem>
+<seglistitem><seg>DOMAIN_USER_RID_GUEST</seg><seg>0x0000</seg><seg>01F5</seg></seglistitem>
+</segmentedlist>
+
+</sect3>
+
+<sect3>
+<title>Well-known RID groups</title>
+
+<segmentedlist>
+<segtitle>Groupname</segtitle>
+<segtitle>????</segtitle>
+<segtitle>RID</segtitle>
+<seglistitem><seg>	DOMAIN_GROUP_RID_ADMINS</seg><seg>0x0000</seg><seg>0200</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_GROUP_RID_USERS</seg><seg>0x0000</seg><seg>0201</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_GROUP_RID_GUESTS</seg><seg>0x0000</seg><seg>0202</seg></seglistitem>
+</segmentedlist>
+
+</sect3>
+
+<sect3>
+<title>Well-known RID aliases</title>
+
+<segmentedlist>
+<segtitle>Groupname</segtitle>
+<segtitle>????</segtitle>
+<segtitle>RID</segtitle>
+<seglistitem><seg>	DOMAIN_ALIAS_RID_ADMINS</seg><seg>0x0000</seg><seg>0220</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_ALIAS_RID_USERS</seg><seg>0x0000</seg><seg>0221</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_ALIAS_RID_GUESTS</seg><seg>0x0000</seg><seg>0222</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_ALIAS_RID_POWER_USERS</seg><seg>0x0000</seg><seg>0223</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_ALIAS_RID_ACCOUNT_OPS</seg><seg>0x0000</seg><seg>0224</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_ALIAS_RID_SYSTEM_OPS</seg><seg>0x0000</seg><seg>0225</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_ALIAS_RID_PRINT_OPS</seg><seg>0x0000</seg><seg>0226</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_ALIAS_RID_BACKUP_OPS</seg><seg>0x0000</seg><seg>0227</seg></seglistitem>
+<seglistitem><seg>	DOMAIN_ALIAS_RID_REPLICATOR</seg><seg>0x0000</seg><seg>0228</seg></seglistitem>
+</segmentedlist>
+
+</sect3>
+</sect2>
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/contributing.xml b/docs-xml/Samba3-Developers-Guide/contributing.xml
new file mode 100644
index 00000000000..01e6fb28630
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/contributing.xml
@@ -0,0 +1,112 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<chapter id="contributing">
+<chapterinfo>
+	&author.jelmer;
+</chapterinfo>
+
+<title>Contributing code</title>
+
+<para>Here are a few tips and notes that might be useful if you are 
+	interested in modifying samba source code and getting it into 
+	samba's main branch.</para>
+
+<variablelist>
+	<varlistentry>
+		<term>Retrieving the source</term>
+
+		<listitem>
+		<para>In order to contribute code to samba, make sure you have the 
+			latest source. Retrieving the samba source code from CVS is 
+			documented in the appendix of the Samba HOWTO Collection.
+		</para>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Discuss large modifications with team members</term>
+		<listitem>
+		<para>Please discuss large modifications you are going to make 
+		with members of the samba team. Some parts of the samba code 
+		have one or more 'owners' - samba developers who wrote most 
+		of the code and maintain it. 
+		</para>
+
+		<para>This way you can avoid spending your time and effort on 
+		something that is not going to make it into the main samba branch 
+		because someone else was working on the same thing or because your 
+		implementation is not the correct one.
+		</para>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Patch format</term>
+		<listitem>
+		<para>Patches to the samba tree should be in unified diff format, 
+			e.g. files generated by <userinput>diff -u</userinput>. 
+		</para>
+
+		<para>If you are modifying a copy of samba you retrieved from CVS, 
+		you can easily generate a diff file of these changes by running 
+		<userinput>cvs diff -u</userinput>.</para>			
+		</listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Points of attention when modifying samba source code</term>
+		<listitem><para>
+		<itemizedlist>
+		<listitem><para>Don't simply copy code from other places and modify it until it
+		works. Code needs to be clean and logical. Duplicate 
+		code is to be avoided.</para></listitem>
+		<listitem><para>Test your patch. It might take a while before one of us looks 
+		at your patch so it will take longer before your patch when your patch 
+		needs to go thru the review cycle again.</para></listitem>
+		<listitem><para>Don't put separate patches in one large diff file. This makes 
+		it harder to read, understand and test the patch. You might 
+		also risk not getting a good patch committed because you mixed it 
+		with one that had issues. </para></listitem>
+		<listitem><para>Make sure your patch complies to the samba coding style as 
+ 		suggested in the coding-suggestions chapter. </para></listitem>
+			</itemizedlist>
+		</para>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Sending in bugfixes</term>
+		<listitem>
+		<para>Bugfixes to bugs in samba should be submitted to samba's
+		<ulink url="https://bugzilla.samba.org/">bugzilla system</ulink>, 
+		along with a description of the bug.
+		</para>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Sending in feature patches</term>
+		<listitem>
+		<para>Send feature patches along with a description of what the 
+		patch is supposed to do to the 
+		<ulink url="mailto:samba-technical@samba.org">Samba-technical mailinglist</ulink> and possibly to a samba team member who is (one of the) 'owners'
+		of the code you made modifications to. We are all busy people 
+		so everybody tends to 'let one of the others handle it'. If nobody 
+		responded to your patch for a week, try to send it again until you 
+		get a response from one of us.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Feedback on your patch</term>
+		<listitem>
+		<para>One of the team members will look at your patch and either 
+		commit your patch or give comments why he won't apply it. In the 
+		latter case you can fix your patch and re-send it until 
+		your patch is approved.</para>
+		</listitem>
+	</varlistentry>
+</variablelist>
+
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/debug.xml b/docs-xml/Samba3-Developers-Guide/debug.xml
new file mode 100644
index 00000000000..a55facedff4
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/debug.xml
@@ -0,0 +1,323 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="debug">
+<chapterinfo>
+	<author>
+		<firstname>Chris</firstname><surname>Hertel</surname>
+	</author>
+	<pubdate>July 1998</pubdate>
+</chapterinfo>
+
+<title>The samba DEBUG system</title>
+
+<sect1>
+<title>New Output Syntax</title>
+
+<para>
+   The syntax of a debugging log file is represented as:
+</para>
+
+<para><programlisting>
+  &gt;debugfile&lt; :== { &gt;debugmsg&lt; }
+
+  &gt;debugmsg&lt;  :== &gt;debughdr&lt; '\n' &gt;debugtext&lt;
+
+  &gt;debughdr&lt;  :== '[' TIME ',' LEVEL ']' FILE ':' [FUNCTION] '(' LINE ')'
+
+  &gt;debugtext&lt; :== { &gt;debugline&lt; }
+
+  &gt;debugline&lt; :== TEXT '\n'
+</programlisting></para>
+
+<para>
+TEXT is a string of characters excluding the newline character.
+</para>
+
+<para>
+LEVEL is the DEBUG level of the message (an integer in the range
+		0..10).
+</para>
+
+<para>
+TIME is a timestamp.
+</para>
+
+<para>
+FILE is the name of the file from which the debug message was
+generated.
+</para>
+
+<para>
+FUNCTION is the function from which the debug message was generated.
+</para>
+
+<para>
+LINE is the line number of the debug statement that generated the
+message.
+</para>
+
+<para>Basically, what that all means is:</para>
+<orderedlist>
+<listitem><para>
+A debugging log file is made up of debug messages.
+</para></listitem>
+<listitem><para>
+Each debug message is made up of a header and text. The header is
+separated from the text by a newline.
+</para></listitem>
+<listitem><para>
+The header begins with the timestamp and debug level of the
+message enclosed in brackets. The filename, function, and line
+number at which the message was generated follow. The filename is
+terminated by a colon, and the function name is terminated by the
+parenthesis which contain the line number. Depending upon the
+compiler, the function name may be missing (it is generated by the
+__FUNCTION__ macro, which is not universally implemented, dangit).
+</para></listitem>
+<listitem><para>
+The message text is made up of zero or more lines, each terminated
+by a newline.
+</para></listitem>
+</orderedlist>
+
+<para>Here's some example output:</para>
+
+<para><programlisting>
+    [1998/08/03 12:55:25, 1] nmbd.c:(659)
+      Netbios nameserver version 1.9.19-prealpha started.
+      Copyright Andrew Tridgell 1994-1997
+    [1998/08/03 12:55:25, 3] loadparm.c:(763)
+      Initializing global parameters
+</programlisting></para>
+
+<para>
+Note that in the above example the function names are not listed on
+the header line. That's because the example above was generated on an
+SGI Indy, and the SGI compiler doesn't support the __FUNCTION__ macro.
+</para>
+
+</sect1>
+
+<sect1>
+<title>The DEBUG() Macro</title>
+
+<para>
+Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters.
+The first is the message level, the second is the body of a function
+call to the Debug1() function.
+</para>
+
+<para>That's confusing.</para>
+
+<para>Here's an example which may help a bit. If you would write</para>
+
+<para><programlisting>
+printf( "This is a %s message.\n", "debug" );
+</programlisting></para>
+
+<para>
+to send the output to stdout, then you would write
+</para>
+
+<para><programlisting>
+DEBUG( 0, ( "This is a %s message.\n", "debug" ) );
+</programlisting></para>
+
+<para>
+to send the output to the debug file.  All of the normal printf()
+formatting escapes work.
+</para>
+
+<para>
+Note that in the above example the DEBUG message level is set to 0.
+Messages at level 0 always print.  Basically, if the message level is
+less than or equal to the global value DEBUGLEVEL, then the DEBUG
+statement is processed.
+</para>
+
+<para>
+The output of the above example would be something like:
+</para>
+
+<para><programlisting>
+    [1998/07/30 16:00:51, 0] file.c:function(128)
+      This is a debug message.
+</programlisting></para>
+
+<para>
+Each call to DEBUG() creates a new header *unless* the output produced
+by the previous call to DEBUG() did not end with a '\n'. Output to the
+debug file is passed through a formatting buffer which is flushed
+every time a newline is encountered. If the buffer is not empty when
+DEBUG() is called, the new input is simply appended.
+</para>
+
+<para>
+...but that's really just a Kludge. It was put in place because
+DEBUG() has been used to write partial lines. Here's a simple (dumb)
+example of the kind of thing I'm talking about:
+</para>
+
+<para><programlisting>
+    DEBUG( 0, ("The test returned " ) );
+    if( test() )
+      DEBUG(0, ("True") );
+    else
+      DEBUG(0, ("False") );
+    DEBUG(0, (".\n") );
+</programlisting></para>
+
+<para>
+Without the format buffer, the output (assuming test() returned true)
+would look like this:
+</para>
+
+<para><programlisting>
+    [1998/07/30 16:00:51, 0] file.c:function(256)
+      The test returned
+    [1998/07/30 16:00:51, 0] file.c:function(258)
+      True
+    [1998/07/30 16:00:51, 0] file.c:function(261)
+      .
+</programlisting></para>
+
+<para>Which isn't much use. The format buffer kludge fixes this problem.
+</para>
+
+</sect1>
+
+<sect1>
+<title>The DEBUGADD() Macro</title>
+
+<para>
+In addition to the kludgey solution to the broken line problem
+described above, there is a clean solution. The DEBUGADD() macro never
+generates a header. It will append new text to the current debug
+message even if the format buffer is empty. The syntax of the
+DEBUGADD() macro is the same as that of the DEBUG() macro.
+</para>
+
+<para><programlisting>
+    DEBUG( 0, ("This is the first line.\n" ) );
+    DEBUGADD( 0, ("This is the second line.\nThis is the third line.\n" ) );
+</programlisting></para>
+
+<para>Produces</para>
+
+<para><programlisting>
+    [1998/07/30 16:00:51, 0] file.c:function(512)
+      This is the first line.
+      This is the second line.
+      This is the third line.
+</programlisting></para>
+
+</sect1>
+
+<sect1>
+<title>The DEBUGLVL() Macro</title>
+
+<para>
+One of the problems with the DEBUG() macro was that DEBUG() lines
+tended to get a bit long. Consider this example from
+nmbd_sendannounce.c:
+</para>
+
+<para><programlisting>
+  DEBUG(3,("send_local_master_announcement: type %x for name %s on subnet %s for workgroup %s\n",
+            type, global_myname, subrec->subnet_name, work->work_group));
+</programlisting></para>
+
+<para>
+One solution to this is to break it down using DEBUG() and DEBUGADD(),
+as follows:
+</para>
+
+<para><programlisting>
+  DEBUG( 3, ( "send_local_master_announcement: " ) );
+  DEBUGADD( 3, ( "type %x for name %s ", type, global_myname ) );
+  DEBUGADD( 3, ( "on subnet %s ", subrec->subnet_name ) );
+  DEBUGADD( 3, ( "for workgroup %s\n", work->work_group ) );
+</programlisting></para>
+
+<para>
+A similar, but arguably nicer approach is to use the DEBUGLVL() macro.
+This macro returns True if the message level is less than or equal to
+the global DEBUGLEVEL value, so:
+</para>
+
+<para><programlisting>
+  if( DEBUGLVL( 3 ) )
+    {
+    dbgtext( "send_local_master_announcement: " );
+    dbgtext( "type %x for name %s ", type, global_myname );
+    dbgtext( "on subnet %s ", subrec->subnet_name );
+    dbgtext( "for workgroup %s\n", work->work_group );
+    }
+</programlisting></para>
+
+<para>(The dbgtext() function is explained below.)</para>
+
+<para>There are a few advantages to this scheme:</para>
+<orderedlist>
+<listitem><para>
+The test is performed only once.
+</para></listitem>
+<listitem><para>
+You can allocate variables off of the stack that will only be used
+within the DEBUGLVL() block.
+</para></listitem>
+<listitem><para>
+Processing that is only relevant to debug output can be contained
+within the DEBUGLVL() block.
+</para></listitem>
+</orderedlist>
+
+</sect1>
+
+<sect1>
+<title>New Functions</title>
+
+<sect2>
+<title>dbgtext()</title>
+<para>
+This function prints debug message text to the debug file (and
+possibly to syslog) via the format buffer. The function uses a
+variable argument list just like printf() or Debug1(). The
+input is printed into a buffer using the vslprintf() function,
+and then passed to format_debug_text().
+
+If you use DEBUGLVL() you will probably print the body of the
+message using dbgtext(). 
+</para>
+</sect2>
+
+<sect2>
+<title>dbghdr()</title>
+<para>
+This is the function that writes a debug message header.
+Headers are not processed via the format buffer. Also note that
+if the format buffer is not empty, a call to dbghdr() will not
+produce any output. See the comments in dbghdr() for more info.
+</para>
+
+<para>
+It is not likely that this function will be called directly. It
+is used by DEBUG() and DEBUGADD().
+</para>
+</sect2>
+
+<sect2>
+<title>format_debug_text()</title>
+<para>
+This is a static function in debug.c. It stores the output text
+for the body of the message in a buffer until it encounters a
+newline. When the newline character is found, the buffer is
+written to the debug file via the Debug1() function, and the
+buffer is reset. This allows us to add the indentation at the
+beginning of each line of the message body, and also ensures
+that the output is written a line at a time (which cleans up
+syslog output).
+</para>
+</sect2>
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/encryption.xml b/docs-xml/Samba3-Developers-Guide/encryption.xml
new file mode 100644
index 00000000000..be00beba5d7
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/encryption.xml
@@ -0,0 +1,199 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="pwencrypt">
+
+
+<chapterinfo>
+	<author>
+		<firstname>Jeremy</firstname><surname>Allison</surname>
+		<affiliation>
+			<orgname>Samba Team</orgname>
+			<address>
+				<email>samba@samba.org</email>
+			</address>
+		</affiliation>
+	</author>
+
+	<pubdate>19 Apr 1999</pubdate>
+</chapterinfo>
+	
+<title>LanMan and NT Password Encryption</title>
+
+<sect1>
+	<title>Introduction</title>
+	
+	<para>With the development of LanManager and Windows NT 
+	compatible password encryption for Samba, it is now able 
+	to validate user connections in exactly the same way as 
+	a LanManager or Windows NT server.</para>
+
+	<para>This document describes how the SMB password encryption 
+	algorithm works and what issues there are in choosing whether 
+	you want to use it. You should read it carefully, especially 
+	the part about security and the "PROS and CONS" section.</para>
+	
+</sect1>
+
+<sect1>
+	<title>How does it work?</title>
+
+	<para>LanManager encryption is somewhat similar to UNIX 
+	password encryption. The server uses a file containing a 
+	hashed value of a user's password.  This is created by taking 
+	the user's plaintext password, capitalising it, and either 
+	truncating to 14 bytes or padding to 14 bytes with null bytes. 
+	This 14 byte value is used as two 56 bit DES keys to encrypt 
+	a 'magic' eight byte value, forming a 16 byte value which is 
+	stored by the server and client. Let this value be known as 
+	the "hashed password".</para>
+	
+	<para>Windows NT encryption is a higher quality mechanism, 
+	consisting of doing an MD4 hash on a Unicode version of the user's 
+	password. This also produces a 16 byte hash value that is 
+	non-reversible.</para>
+
+	<para>When a client (LanManager, Windows for WorkGroups, Windows 
+	95 or Windows NT) wishes to mount a Samba drive (or use a Samba 
+	resource), it first requests a connection and negotiates the 
+	protocol that the client and server will use. In the reply to this 
+	request the Samba server generates and appends an 8 byte, random 
+	value - this is stored in the Samba server after the reply is sent 
+	and is known as the "challenge".  The challenge is different for 
+	every client connection.</para>
+
+	<para>The client then uses the hashed password (16 byte values 
+	described above), appended with 5 null bytes, as three 56 bit 
+	DES keys, each of which is used to encrypt the challenge 8 byte 
+	value, forming a 24 byte value known as the "response".</para>
+
+	<para>In the SMB call SMBsessionsetupX (when user level security 
+	is selected) or the call SMBtconX (when share level security is 
+	selected), the 24 byte response is returned by the client to the 
+	Samba server.  For Windows NT protocol levels the above calculation 
+	is done on both hashes of the user's password and both responses are 
+	returned in the SMB call, giving two 24 byte values.</para>
+
+	<para>The Samba server then reproduces the above calculation, using 
+	its own stored value of the 16 byte hashed password (read from the 
+	<filename>smbpasswd</filename> file - described later) and the challenge 
+	value that it kept from the negotiate protocol reply. It then checks 
+	to see if the 24 byte value it calculates matches the 24 byte value 
+	returned to it from the client.</para>
+
+	<para>If these values match exactly, then the client knew the 
+	correct password (or the 16 byte hashed value - see security note 
+	below) and is thus allowed access. If not, then the client did not 
+	know the correct password and is denied access.</para>
+
+	<para>Note that the Samba server never knows or stores the cleartext 
+	of the user's password - just the 16 byte hashed values derived from 
+	it. Also note that the cleartext password or 16 byte hashed values 
+	are never transmitted over the network - thus increasing security.</para>
+</sect1>
+
+<sect1>
+	<title>The smbpasswd file</title>
+	<anchor id="SMBPASSWDFILEFORMAT"/>
+	<para>In order for Samba to participate in the above protocol 
+	it must be able to look up the 16 byte hashed values given a user name.
+	Unfortunately, as the UNIX password value is also a one way hash
+	function (ie. it is impossible to retrieve the cleartext of the user's
+	password given the UNIX hash of it), a separate password file
+	containing this 16 byte value must be kept. To minimise problems with
+	these two password files, getting out of sync, the UNIX <filename>
+	/etc/passwd</filename> and the <filename>smbpasswd</filename> file, 
+	a utility, <command>mksmbpasswd.sh</command>, is provided to generate
+	a smbpasswd file from a UNIX <filename>/etc/passwd</filename> file.
+	</para>
+
+
+	<para>To generate the smbpasswd file from your <filename>/etc/passwd
+	</filename> file use the following command:</para>
+	
+	<para><prompt>$ </prompt><userinput>cat /etc/passwd | mksmbpasswd.sh
+	&gt; /usr/local/samba/private/smbpasswd</userinput></para>
+	
+	<para>If you are running on a system that uses NIS, use</para>
+
+	<para><prompt>$ </prompt><userinput>ypcat passwd | mksmbpasswd.sh
+	&gt; /usr/local/samba/private/smbpasswd</userinput></para>
+	
+	<para>The <command>mksmbpasswd.sh</command> program is found in 
+	the Samba source directory. By default, the smbpasswd file is 
+	stored in :</para>
+
+	<para><filename>/usr/local/samba/private/smbpasswd</filename></para>
+
+	<para>The owner of the <filename>/usr/local/samba/private/</filename> 
+	directory should be set to root, and the permissions on it should 
+	be set to 0500 (<command>chmod 500 /usr/local/samba/private</command>).
+	</para>
+
+	<para>Likewise, the smbpasswd file inside the private directory should 
+	be owned by root and the permissions on is should be set to 0600
+	(<command>chmod 600 smbpasswd</command>).</para>
+
+
+	<para>The format of the smbpasswd file is (The line has been 
+	wrapped here. It should appear as one entry per line in 
+	your smbpasswd file.)</para>
+	
+	<para><programlisting>
+username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
+	[Account type]:LCT-&lt;last-change-time&gt;:Long name
+	</programlisting></para>
+	
+	<para>Although only the <replaceable>username</replaceable>, 
+	<replaceable>uid</replaceable>, <replaceable>
+	XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</replaceable>,
+	[<replaceable>Account type</replaceable>] and <replaceable>
+	last-change-time</replaceable> sections are significant 
+	and are looked at in the Samba code.</para>
+
+	<para>It is <emphasis>VITALLY</emphasis> important that there by 32 
+	'X' characters between the two ':' characters in the XXX sections - 
+	the smbpasswd and Samba code will fail to validate any entries that 
+	do not have 32 characters  between ':' characters. The first XXX 
+	section is for the Lanman password hash, the second is for the 
+	Windows NT version.</para>
+
+	<para>When the password file is created all users have password entries
+	consisting of 32 'X' characters. By default this disallows any access
+	as this user. When a user has a password set, the 'X' characters change
+	to 32 ascii hexadecimal digits (0-9, A-F). These are an ascii
+	representation of the 16 byte hashed value of a user's password.</para>
+
+	<para>To set a user to have no password (not recommended), edit the file
+	using vi, and replace the first 11 characters with the ascii text
+	<constant>"NO PASSWORD"</constant> (minus the quotes).</para>
+
+	<para>For example, to clear the password for user bob, his smbpasswd file 
+	entry would look like :</para>
+
+	<para><programlisting>
+bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
+	[U          ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
+	</programlisting></para>
+	
+	<para>If you are allowing users to use the smbpasswd command to set 
+	their own passwords, you may want to give users NO PASSWORD initially 
+	so they do not have to enter a previous password when changing to their 
+	new password (not recommended). In order for you to allow this the
+	<command>smbpasswd</command> program must be able to connect to the 
+	<command>smbd</command> daemon as that user with no password. Enable this 
+	by adding the line :</para>
+
+	<para><command>null passwords = yes</command></para>
+	
+	<para>to the [global] section of the smb.conf file (this is why 
+	the above scenario is not recommended). Preferably, allocate your
+	users a default password to begin with, so you do not have
+	to enable this on your server.</para>
+
+	<para><emphasis>Note : </emphasis>This file should be protected very 
+	carefully. Anyone with access to this file can (with enough knowledge of 
+	the protocols) gain access to your SMB server. The file is thus more 
+	sensitive than a normal unix <filename>/etc/passwd</filename> file.</para>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/gencache.xml b/docs-xml/Samba3-Developers-Guide/gencache.xml
new file mode 100644
index 00000000000..7e8475c192b
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/gencache.xml
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="gencache">
+<chapterinfo>
+	<author>
+		<firstname>Rafal</firstname><surname>Szczesniak</surname>
+	</author>
+	<pubdate>April 2003</pubdate>
+</chapterinfo>
+
+<title>General cache mechanism and API</title>
+
+<sect1>
+<title>Abstract</title>
+<para>
+General cache (gencache) was designed to combine various kinds of caching
+mechanisms into one, defined by a simple API. This way, anyone can use it
+to create their own caching layer on top of gencache. An example of
+such approach is the netbios name cache.
+</para>
+</sect1>
+
+<sect1>
+<title>The mechanism</title>
+<para>
+Gencache utilises <emphasise>tdb</emphasise> database, like many other
+parts of Samba. As its origins are in Berkeley DB implementation, it
+uses key/value pairs stored in binary file. The values gencache
+operates on are string-based, however. This makes very easy to use it
+in command line environment eg. to quickly take a look at what's in
+the cache or set some value.
+</para>
+
+<para>
+All the data is stored in <filename>gencache.tdb</filename>
+file. Records put there are in key/value format as mentioned below,
+but as it's a cache, the timeout plays also important role and has a
+special place in the key/value pair, as well as API.
+</para>
+</sect1>
+
+
+<sect1>
+<title>The data structure</title>
+<para>
+The record stored in <filename>gencache.tdb</filename> file consists
+of the key, the value and the expiration timeout. While the first part
+is stored completely independent from the others, the last two are
+kept together. The form the record has is:
+</para>
+
+<para><programlisting>
+key:     &lt;string&gt;
+value:   &lt;12-digit timeout&gt;/&lt;string&gt;
+</programlisting></para>
+
+<para>The timeout part is the ASCII representation of
+<emphasis>time_t</emphasis> value of the time when the cache entry
+expires. Obviously the API, the programmer is provided with, hides this detail,
+so that you don't have to care about checking it. Simply watch
+carefully the return status of the function.
+</para>
+</sect1>
+
+<sect1>
+<title>The API</title>
+
+<para><programlisting>
+BOOL gencache_init()
+</programlisting></para>
+
+<para>This is used to initialise to whole caching mechanism. It means
+opening the file or creating it if non-existing. If it's already been
+opened earlier, then the routine just does nothing and returns
+<constant>true</constant>. If something goes wrong, say the user
+doesn't have necessary rights, the function returns
+<constant>false</constant>.</para>
+
+<para><programlisting>
+BOOL gencache_shutdown()
+</programlisting></para>
+
+<para>This is the proper way to close the cache file. It simply
+returns <constant>true</constant> after successful closing file and
+<constant>false</constant> upon a failure.</para>
+
+<para><programlisting>
+BOOL gencache_set(const char* keystr, const char* value, time_t timeout)
+</programlisting></para>
+
+<para>This is one of the most basic functions. What it allows you to
+do is to set some particular cache entry. If the entry haven't
+existed yet, the function will act just as it was "gencache_add"
+function. If it's already been in the cache, the entry will be set to
+the new value. In either case, the cache entry will be set with given
+key, value and timeout. Thus it is comfortable way to just set the
+entry and not care about the details.</para>
+
+<para><programlisting>
+BOOL gencache_set_only(const char* keystr, const char* value, time_t timeout)
+</programlisting></para>
+
+<para><programlisting>
+BOOL gencache_del(const char* keystr)
+</programlisting></para>
+
+<para><programlisting>
+BOOL gencache_get(const char* keystr, char** valstr, time_t* timeout)
+</programlisting></para>
+
+<para><programlisting>
+void gencache_iterate(void (*fn)(const char* key, const char *value, time_t timeout, void* dptr),
+                      void* data, const char* keystr_pattern)
+
+</programlisting></para>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/index.xml b/docs-xml/Samba3-Developers-Guide/index.xml
new file mode 100644
index 00000000000..0e5b688874b
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/index.xml
@@ -0,0 +1,99 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE book PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc" [
+<!ATTLIST book 
+	xmlns:xi CDATA #FIXED "http://www.w3.org/2003/XInclude">
+]>
+
+<book id="Samba-Developers-Guide"
+	xmlns:xi="http://www.w3.org/2003/XInclude">
+
+<title>SAMBA Developers Guide</title>
+
+<bookinfo>
+<authorgroup>
+	<editor>&person.jelmer;</editor>
+</authorgroup>
+	
+<abstract>
+<para>
+<emphasis>Last Update</emphasis> : Fri Oct 10 00:59:58 CEST 2003
+</para>
+
+<para>
+This book is a collection of documents that might be useful for 
+people developing samba or those interested in doing so.
+It's nothing more than a collection of documents written by samba developers about 
+the internals of various parts of samba and the SMB protocol. It's still (and will always be) incomplete.
+The most recent version of this document
+can be found at <ulink url="http://devel.samba.org/">http://devel.samba.org/</ulink>.
+</para>
+
+<para>
+This documentation is distributed under the GNU General Public License (GPL) 
+version 2.  A copy of the license is included with the Samba source
+distribution.  A copy can be found on-line at <ulink 
+url="http://www.fsf.org/licenses/gpl.txt">http://www.fsf.org/licenses/gpl.txt</ulink>
+</para>
+
+<warning>
+	<para>This document is incomplete and unmaintained. It is merely a 
+	collection of development-related notes.</para>
+</warning>
+
+</abstract>
+
+</bookinfo>
+
+<xi:include href="../Samba3-Developers-Guide-attributions.xml">
+	<xi:fallback/>
+</xi:include>
+
+<?latex \cleardoublepage ?>
+
+<!-- Contents -->
+<toc/>
+
+<?latex \pagenumbering{arabic} ?>
+<!-- Chapters -->
+<part>
+	<title>The protocol</title>
+
+	<xi:include href="unix-smb.xml"/>
+	<xi:include href="cifsntdomain.xml"/>
+
+</part>
+
+<part>
+	<title>Samba Basics</title>
+
+	<xi:include href="architecture.xml"/>
+	<xi:include href="debug.xml"/>
+	<xi:include href="internals.xml"/>
+	<xi:include href="CodingSuggestions.xml"/>
+	<xi:include href="contributing.xml"/>
+	<xi:include href="modules.xml"/>
+</part>
+
+<part>
+	<title>Samba Subsystems</title>
+	
+	<xi:include href="rpc_plugin.xml"/>
+	<xi:include href="vfs.xml"/>
+	<xi:include href="parsing.xml"/>
+	<xi:include href="wins.xml"/>
+	<xi:include href="encryption.xml"/>
+
+</part>
+
+<part>
+	<title>Debugging and tracing</title>
+
+	<xi:include href="Tracing.xml"/>
+	<xi:include href="printing.xml"/>
+</part>
+
+<part><title>Appendices</title>
+	<xi:include href="packagers.xml"/>
+</part>
+
+</book>
diff --git a/docs-xml/Samba3-Developers-Guide/internals.xml b/docs-xml/Samba3-Developers-Guide/internals.xml
new file mode 100644
index 00000000000..be271217e73
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/internals.xml
@@ -0,0 +1,442 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="internals">
+<chapterinfo>
+	<author>
+		<firstname>David</firstname><surname>Chappell</surname>
+		<affiliation>
+			<address><email>David.Chappell@mail.trincoll.edu</email></address>
+		</affiliation>
+	</author>
+	<pubdate>8 May 1996</pubdate>
+</chapterinfo>
+
+<title>Samba Internals</title>
+
+<sect1>
+<title>Character Handling</title>
+<para>
+This section describes character set handling in Samba, as implemented in
+Samba 3.0 and above
+</para>
+
+<para>
+In the past Samba had very ad-hoc character set handling. Scattered
+throughout the code were numerous calls which converted particular
+strings to/from DOS codepages. The problem is that there was no way of
+telling if a particular char* is in dos codepage or unix
+codepage. This led to a nightmare of code that tried to cope with
+particular cases without handlingt the general case.
+</para>
+</sect1>
+
+<sect1>
+<title>The new functions</title>
+
+<para>
+The new system works like this:
+</para>
+
+<orderedlist>
+<listitem><para>
+	all char* strings inside Samba are "unix" strings. These are
+	multi-byte strings that are in the charset defined by the "unix
+	charset" option in smb.conf. 
+</para></listitem>
+
+<listitem><para>
+	there is no single fixed character set for unix strings, but any
+	character set that is used does need the following properties:
+	</para>
+	<orderedlist>
+	
+	<listitem><para>
+		must not contain NULLs except for termination
+	</para></listitem>
+
+	<listitem><para>
+		must be 7-bit compatible with C strings, so that a constant
+		string or character in C will be byte-for-byte identical to the
+		equivalent string in the chosen character set. 
+	</para></listitem>
+	
+	<listitem><para>
+		when you uppercase or lowercase a string it does not become
+		longer than the original string
+	</para></listitem>
+
+	<listitem><para>
+		must be able to correctly hold all characters that your client
+		will throw at it
+	</para></listitem>
+	</orderedlist>
+	
+	<para>
+	For example, UTF-8 is fine, and most multi-byte asian character sets
+	are fine, but UCS2 could not be used for unix strings as they
+	contain nulls.
+	</para>
+</listitem>
+
+<listitem><para>
+	when you need to put a string into a buffer that will be sent on the
+	wire, or you need a string in a character set format that is
+	compatible with the clients character set then you need to use a
+	pull_ or push_ function. The pull_ functions pull a string from a
+	wire buffer into a (multi-byte) unix string. The push_ functions
+	push a string out to a wire buffer. 
+</para></listitem>
+
+<listitem><para>
+	the two main pull_ and push_ functions you need to understand are
+	pull_string and push_string. These functions take a base pointer
+	that should point at the start of the SMB packet that the string is
+	in. The functions will check the flags field in this packet to
+	automatically determine if the packet is marked as a unicode packet,
+	and they will choose whether to use unicode for this string based on
+	that flag. You may also force this decision using the STR_UNICODE or
+	STR_ASCII flags. For use in smbd/ and libsmb/ there are wrapper
+	functions clistr_ and srvstr_ that call the pull_/push_ functions
+	with the appropriate first argument.
+	</para>
+	
+	<para>
+	You may also call the pull_ascii/pull_ucs2 or push_ascii/push_ucs2
+	functions if you know that a particular string is ascii or
+	unicode. There are also a number of other convenience functions in
+	charcnv.c that call the pull_/push_ functions with particularly
+	common arguments, such as pull_ascii_pstring()
+	</para>
+</listitem>
+
+<listitem><para>
+	The biggest thing to remember is that internal (unix) strings in Samba
+	may now contain multi-byte characters. This means you cannot assume
+	that characters are always 1 byte long. Often this means that you will
+	have to convert strings to ucs2 and back again in order to do some
+	(seemingly) simple task. For examples of how to do this see functions
+	like strchr_m(). I know this is very slow, and we will eventually
+	speed it up but right now we want this stuff correct not fast.
+</para></listitem>
+
+<listitem><para>
+	all lp_ functions now return unix strings. The magic "DOS" flag on
+	parameters is gone.
+</para></listitem>
+
+<listitem><para>
+	all vfs functions take unix strings. Don't convert when passing to them
+</para></listitem>
+
+</orderedlist>
+
+</sect1>
+
+<sect1>
+<title>Macros in byteorder.h</title>
+
+<para>
+This section describes the macros defined in byteorder.h.  These macros 
+are used extensively in the Samba code.
+</para>
+
+<sect2>
+<title>CVAL(buf,pos)</title>
+
+<para>
+returns the byte at offset pos within buffer buf as an unsigned character.
+</para>
+</sect2>
+
+<sect2>
+<title>PVAL(buf,pos)</title>
+<para>returns the value of CVAL(buf,pos) cast to type unsigned integer.</para>
+</sect2>
+
+<sect2>
+<title>SCVAL(buf,pos,val)</title>
+<para>sets the byte at offset pos within buffer buf to value val.</para>
+</sect2>
+
+<sect2>
+<title>SVAL(buf,pos)</title>
+<para>
+	returns the value of the unsigned short (16 bit) little-endian integer at 
+	offset pos within buffer buf.  An integer of this type is sometimes
+	refered to as "USHORT".
+</para>
+</sect2>
+
+<sect2>
+<title>IVAL(buf,pos)</title>
+<para>returns the value of the unsigned 32 bit little-endian integer at offset 
+pos within buffer buf.</para>
+</sect2>
+
+<sect2>
+<title>SVALS(buf,pos)</title>
+<para>returns the value of the signed short (16 bit) little-endian integer at 
+offset pos within buffer buf.</para>
+</sect2>
+
+<sect2>
+<title>IVALS(buf,pos)</title>
+<para>returns the value of the signed 32 bit little-endian integer at offset pos
+within buffer buf.</para>
+</sect2>
+
+<sect2>
+<title>SSVAL(buf,pos,val)</title>
+<para>sets the unsigned short (16 bit) little-endian integer at offset pos within 
+buffer buf to value val.</para>
+</sect2>
+
+<sect2>
+<title>SIVAL(buf,pos,val)</title>
+<para>sets the unsigned 32 bit little-endian integer at offset pos within buffer 
+buf to the value val.</para>
+</sect2>
+
+<sect2>
+<title>SSVALS(buf,pos,val)</title>
+<para>sets the short (16 bit) signed little-endian integer at offset pos within 
+buffer buf to the value val.</para>
+</sect2>
+
+<sect2>
+<title>SIVALS(buf,pos,val)</title>
+<para>sets the signed 32 bit little-endian integer at offset pos withing buffer
+buf to the value val.</para>
+</sect2>
+
+<sect2>
+<title>RSVAL(buf,pos)</title>
+<para>returns the value of the unsigned short (16 bit) big-endian integer at 
+offset pos within buffer buf.</para>
+</sect2>
+
+<sect2>
+<title>RIVAL(buf,pos)</title>
+<para>returns the value of the unsigned 32 bit big-endian integer at offset 
+pos within buffer buf.</para>
+</sect2>
+
+<sect2>
+<title>RSSVAL(buf,pos,val)</title>
+<para>sets the value of the unsigned short (16 bit) big-endian integer at 
+offset pos within buffer buf to value val.
+refered to as "USHORT".</para>
+</sect2>
+
+<sect2>
+<title>RSIVAL(buf,pos,val)</title>
+<para>sets the value of the unsigned 32 bit big-endian integer at offset 
+pos within buffer buf to value val.</para>
+</sect2>
+
+</sect1>
+
+
+<sect1>
+<title>LAN Manager Samba API</title>
+
+<para>
+This section describes the functions need to make a LAN Manager RPC call.
+This information had been obtained by examining the Samba code and the LAN
+Manager 2.0 API documentation.  It should not be considered entirely
+reliable.
+</para>
+
+<para>
+<programlisting>
+call_api(int prcnt, int drcnt, int mprcnt, int mdrcnt, 
+	char *param, char *data, char **rparam, char **rdata);
+</programlisting>
+</para>
+
+<para>
+This function is defined in client.c.  It uses an SMB transaction to call a
+remote api.
+</para>
+
+<sect2>
+<title>Parameters</title>
+
+<para>The parameters are as follows:</para>
+
+<orderedlist>
+<listitem><para>
+	prcnt: the number of bytes of parameters begin sent.
+</para></listitem>
+<listitem><para>
+	drcnt:   the number of bytes of data begin sent.
+</para></listitem>
+<listitem><para>
+	mprcnt:  the maximum number of bytes of parameters which should be returned
+</para></listitem>
+<listitem><para>
+	mdrcnt:  the maximum number of bytes of data which should be returned
+</para></listitem>
+<listitem><para>
+	param:   a pointer to the parameters to be sent.
+</para></listitem>
+<listitem><para>
+	data:    a pointer to the data to be sent.
+</para></listitem>
+<listitem><para>
+	rparam:  a pointer to a pointer which will be set to point to the returned
+	parameters.  The caller of call_api() must deallocate this memory.
+</para></listitem>
+<listitem><para>
+	rdata:   a pointer to a pointer which will be set to point to the returned 
+	data.  The caller of call_api() must deallocate this memory.
+</para></listitem>
+</orderedlist>
+
+<para>
+These are the parameters which you ought to send, in the order of their
+appearance in the parameter block:
+</para>
+
+<orderedlist>
+
+<listitem><para>
+An unsigned 16 bit integer API number.  You should set this value with
+SSVAL().  I do not know where these numbers are described.
+</para></listitem>
+
+<listitem><para>
+An ASCIIZ string describing the parameters to the API function as defined
+in the LAN Manager documentation.  The first parameter, which is the server
+name, is ommited.  This string is based uppon the API function as described
+in the manual, not the data which is actually passed.
+</para></listitem>
+
+<listitem><para>
+An ASCIIZ string describing the data structure which ought to be returned.
+</para></listitem>
+
+<listitem><para>
+Any parameters which appear in the function call, as defined in the LAN
+Manager API documentation, after the "Server" and up to and including the
+"uLevel" parameters.
+</para></listitem>
+
+<listitem><para>
+An unsigned 16 bit integer which gives the size in bytes of the buffer we
+will use to receive the returned array of data structures.  Presumably this
+should be the same as mdrcnt.  This value should be set with SSVAL().
+</para></listitem>
+
+<listitem><para>
+An ASCIIZ string describing substructures which should be returned.  If no 
+substructures apply, this string is of zero length.
+</para></listitem>
+
+</orderedlist>
+
+<para>
+The code in client.c always calls call_api() with no data.  It is unclear
+when a non-zero length data buffer would be sent.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Return value</title>
+
+<para>
+The returned parameters (pointed to by rparam), in their order of appearance
+are:</para>
+
+<orderedlist>
+
+<listitem><para>
+An unsigned 16 bit integer which contains the API function's return code. 
+This value should be read with SVAL().
+</para></listitem>
+
+<listitem><para>
+An adjustment which tells the amount by which pointers in the returned
+data should be adjusted.  This value should be read with SVAL().  Basically, 
+the address of the start of the returned data buffer should have the returned
+pointer value added to it and then have this value subtracted from it in
+order to obtain the currect offset into the returned data buffer.
+</para></listitem>
+
+<listitem><para>
+A count of the number of elements in the array of structures returned. 
+It is also possible that this may sometimes be the number of bytes returned.
+</para></listitem>
+</orderedlist>
+
+<para>
+When call_api() returns, rparam points to the returned parameters.  The
+first if these is the result code.  It will be zero if the API call
+suceeded.  This value by be read with "SVAL(rparam,0)".
+</para>
+
+<para>
+The second parameter may be read as "SVAL(rparam,2)".  It is a 16 bit offset
+which indicates what the base address of the returned data buffer was when
+it was built on the server.  It should be used to correct pointer before
+use.
+</para>
+
+<para>
+The returned data buffer contains the array of returned data structures. 
+Note that all pointers must be adjusted before use.  The function
+fix_char_ptr() in client.c can be used for this purpose.
+</para>
+
+<para>
+The third parameter (which may be read as "SVAL(rparam,4)") has something to
+do with indicating the amount of data returned or possibly the amount of
+data which can be returned if enough buffer space is allowed.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Code character table</title>
+<para>
+Certain data structures are described by means of ASCIIz strings containing
+code characters.  These are the code characters:
+</para>
+
+<orderedlist>
+<listitem><para>
+W	a type byte little-endian unsigned integer
+</para></listitem>
+<listitem><para>
+N	a count of substructures which follow
+</para></listitem>
+<listitem><para>
+D	a four byte little-endian unsigned integer
+</para></listitem>
+<listitem><para>
+B	a byte (with optional count expressed as trailing ASCII digits)
+</para></listitem>
+<listitem><para>
+z	a four byte offset to a NULL terminated string
+</para></listitem>
+<listitem><para>
+l	a four byte offset to non-string user data
+</para></listitem>
+<listitem><para>
+b	an offset to data (with count expressed as trailing ASCII digits)
+</para></listitem>
+<listitem><para>
+r	pointer to returned data buffer???
+</para></listitem>
+<listitem><para>
+L	length in bytes of returned data buffer???
+</para></listitem>
+<listitem><para>
+h	number of bytes of information available???
+</para></listitem>
+</orderedlist>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/modules.xml b/docs-xml/Samba3-Developers-Guide/modules.xml
new file mode 100644
index 00000000000..a74c1768443
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/modules.xml
@@ -0,0 +1,166 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="modules">
+<chapterinfo>
+	<author>
+		<firstname>Jelmer</firstname><surname>Vernooij</surname>
+		<affiliation>
+			<orgname>Samba Team</orgname>
+			<address><email>jelmer@samba.org</email></address>
+		</affiliation>
+	</author>
+	<pubdate> 19 March 2003 </pubdate>
+</chapterinfo>
+
+<title>Modules</title>
+
+<sect1>
+<title>Advantages</title>
+
+<para>
+The new modules system has the following advantages:
+</para>
+
+<simplelist>
+<member>Transparent loading of static and shared modules (no need 
+for a subsystem to know about modules)</member>
+<member>Simple selection between shared and static modules at configure time</member>
+<member>"preload modules" option for increasing performance for stable modules</member>
+<member>No nasty #define stuff anymore</member>
+<member>All backends are available as plugin now (including pdb_ldap and pdb_tdb)</member>
+</simplelist>
+</sect1>
+
+<sect1>
+<title>Loading modules</title>
+
+<para>
+Some subsystems in samba use different backends. These backends can be 
+either statically linked in to samba or available as a plugin. A subsystem 
+should have a function that allows a module to register itself. For example, 
+the passdb subsystem has: 
+</para>
+
+<para><programlisting>
+NTSTATUS smb_register_passdb(int version, const char *name, pdb_init_function init);
+</programlisting></para>
+
+<para>
+This function will be called by the initialisation function of the module to 
+register itself. 
+</para>
+
+<sect2>
+<title>Static modules</title>
+
+<para>
+The modules system compiles a list of initialisation functions for the 
+static modules of each subsystem. This is a define. For example, 
+it is here currently (from <filename>include/config.h</filename>): 
+</para>
+
+<para><programlisting>
+/* Static init functions */
+#define static_init_pdb { pdb_mysql_init(); pdb_ldap_init(); pdb_smbpasswd_init(); pdb_tdbsam_init(); pdb_guest_init();}
+</programlisting></para>
+
+<para>
+These functions should be called before the subsystem is used. That 
+should be done when the subsystem is initialised or first used. 
+</para>
+
+</sect2>
+
+<sect2>
+<title>Shared modules</title>
+
+<para>
+If a subsystem needs a certain backend, it should check if it has 
+already been registered. If the backend hasn't been registered already, 
+the subsystem should call smb_probe_module(char *subsystem, char *backend).
+This function tries to load the correct module from a certain path
+($LIBDIR/subsystem/backend.so). If the first character in 'backend' 
+is a slash, smb_probe_module() tries to load the module from the 
+absolute path specified in 'backend'.
+</para>
+
+<para>After smb_probe_module() has been executed, the subsystem 
+should check again if the module has been registered. 
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Writing modules</title>
+
+<para>
+Each module has an initialisation function. For modules that are 
+included with samba this name is '<replaceable>subsystem</replaceable>_<replaceable>backend</replaceable>_init'. For external modules (that will never be built-in, but only available as a module) this name is always 'init_module'. (In the case of modules included with samba, the configure system will add a #define subsystem_backend_init() init_module()).
+The prototype for these functions is:
+</para>
+
+<para><programlisting>
+NTSTATUS init_module(void);
+</programlisting></para>
+
+<para>This function should call one or more 
+registration functions. The function should return NT_STATUS_OK on success and  
+NT_STATUS_UNSUCCESSFUL or a more useful nt error code on failure.</para>
+
+<para>For example, pdb_ldap_init() contains: </para>
+
+<para><programlisting>
+NTSTATUS pdb_ldap_init(void)
+{
+smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam", pdb_init_ldapsam);
+smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam_nua", pdb_init_ldapsam_nua);
+	return NT_STATUS_OK;
+}
+</programlisting></para>
+
+<sect2>
+<title>Static/Shared selection in configure.in</title>
+
+<para>
+Some macros in configure.in generate the various defines and substs that 
+are necessary for the system to work correct. All modules that should 
+be built by default have to be added to the variable 'default_modules'. 
+For example, if ldap is found, pdb_ldap is added to this variable.
+</para>
+
+<para>
+On the bottom of configure.in, SMB_MODULE() should be called 
+for each module and SMB_SUBSYSTEM() for each subsystem.
+</para>
+
+<para>Syntax:</para>
+
+<para><programlisting>
+SMB_MODULE(<replaceable>subsystem</replaceable>_<replaceable>backend</replaceable>, <replaceable>object files</replaceable>, <replaceable>plugin name</replaceable>, <replaceable>subsystem name</replaceable>, <replaceable>static_action</replaceable>, <replaceable>shared_action</replaceable>)
+SMB_SUBSYSTEM(<replaceable>subsystem</replaceable>,<replaceable>depfile</replaceable>)
+</programlisting></para>
+
+<para>The depfile for a certain subsystem is the file that calls the 
+initialisation functions for the statically built in modules.</para>
+
+<para>
+<replaceable>@SUBSYSTEM_MODULES@</replaceable> in Makefile.in will 
+be replaced with the names of the plugins to build.
+</para>
+
+<para>You must make sure all .c files that contain defines that can 
+be changed by ./configure are rebuilded in the 'modules_clean' make target. 
+Practically, this means all c files that contain <command>static_init_subsystem;</command> calls need to be rebuilded.
+</para>
+
+<note>
+<para>
+There currently also is a configure.in command called SMB_MODULE_PROVIVES().
+This is used for modules that register multiple things. It should not 
+be used as probing will most likely disappear in the future.</para>
+</note>
+
+</sect2>
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/packagers.xml b/docs-xml/Samba3-Developers-Guide/packagers.xml
new file mode 100644
index 00000000000..8b8eccacc76
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/packagers.xml
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="Packaging">
+<chapterinfo>
+	<author>
+		<firstname>Jelmer</firstname><surname>Vernooij</surname>
+	</author>
+</chapterinfo>
+
+<title>Notes to packagers</title>
+
+<sect1>
+<title>Versioning</title>
+
+<para>
+Please, please update the version number in <filename>source/include/version.h</filename> to include the
+versioning of your package. This makes it easier to distinguish standard samba builds from custom-build samba
+builds (distributions often patch packages). For example, a good version would be:
+</para>
+
+<para><programlisting>
+Version 2.999+3.0.alpha21-5 for Debian
+</programlisting></para>
+
+</sect1>
+
+<sect1>
+<title>Modules</title>
+
+<para>
+Samba3 has support for building parts of samba as plugins. This makes it possible to, for example,
+put ldap or mysql support in a separate package, thus making it possible to have a normal samba package not
+depending on ldap or mysql. To build as much parts of samba as a plugin, run:
+</para>
+
+<para>
+The option <literal>--with-shared-modules</literal> is maintained to support specific modules such as
+idmap_XXX and vfs_XXX. For example, <literal>--with-shared-modules=idmap_ad</literal>. Use of this parameter
+to the <command>configure</command> command as not been supported in official releases.
+</para>
+
+<para>
+<programlisting>
+./configure --with-shared-modules=rpc,vfs,auth,pdb,charset
+</programlisting>
+</para>
+
+</sect1>
+
+
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/parsing.xml b/docs-xml/Samba3-Developers-Guide/parsing.xml
new file mode 100644
index 00000000000..d695f9313cf
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/parsing.xml
@@ -0,0 +1,241 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="parsing">
+<chapterinfo>
+	<author>
+		<firstname>Chris</firstname><surname>Hertel</surname>
+	</author>
+	<pubdate>November 1997</pubdate>
+</chapterinfo>
+
+<title>The smb.conf file</title>
+
+<sect1>
+<title>Lexical Analysis</title>
+
+<para>
+Basically, the file is processed on a line by line basis.  There are
+four types of lines that are recognized by the lexical analyzer
+(params.c):
+</para>
+
+<orderedlist>
+<listitem><para>
+Blank lines - Lines containing only whitespace.
+</para></listitem>
+<listitem><para>
+Comment lines - Lines beginning with either a semi-colon or a
+pound sign (';' or '#').
+</para></listitem>
+<listitem><para>
+Section header lines - Lines beginning with an open square bracket ('[').
+</para></listitem>
+<listitem><para>
+Parameter lines - Lines beginning with any other character.
+(The default line type.)
+</para></listitem>
+</orderedlist>
+
+<para>
+The first two are handled exclusively by the lexical analyzer, which
+ignores them.  The latter two line types are scanned for
+</para>
+
+<orderedlist>
+<listitem><para>
+  - Section names
+</para></listitem>
+<listitem><para>
+  - Parameter names
+</para></listitem>
+<listitem><para>
+  - Parameter values
+</para></listitem>
+</orderedlist>
+
+<para>
+These are the only tokens passed to the parameter loader
+(loadparm.c).  Parameter names and values are divided from one
+another by an equal sign: '='.
+</para>
+
+<sect2>
+<title>Handling of Whitespace</title>
+
+<para>
+Whitespace is defined as all characters recognized by the isspace()
+function (see ctype(3C)) except for the newline character ('\n')
+The newline is excluded because it identifies the end of the line.
+</para>
+
+<orderedlist>
+<listitem><para>
+The lexical analyzer scans past white space at the beginning of a line.
+</para></listitem>
+
+<listitem><para>
+Section and parameter names may contain internal white space.  All
+whitespace within a name is compressed to a single space character. 
+</para></listitem>
+
+<listitem><para>
+Internal whitespace within a parameter value is kept verbatim with 
+the exception of carriage return characters ('\r'), all of which
+are removed.
+</para></listitem>
+
+<listitem><para>
+Leading and trailing whitespace is removed from names and values.
+</para></listitem>
+
+</orderedlist>
+
+</sect2>
+
+<sect2>
+<title>Handling of Line Continuation</title>
+
+<para>
+Long section header and parameter lines may be extended across
+multiple lines by use of the backslash character ('\\').  Line
+continuation is ignored for blank and comment lines.
+</para>
+
+<para>
+If the last (non-whitespace) character within a section header or on
+a parameter line is a backslash, then the next line will be
+(logically) concatonated with the current line by the lexical
+analyzer.  For example:
+</para>
+
+<para><programlisting>
+	param name = parameter value string \
+	with line continuation.
+</programlisting></para>
+
+<para>Would be read as</para>
+
+<para><programlisting>
+    param name = parameter value string     with line continuation.
+</programlisting></para>
+
+<para>
+Note that there are five spaces following the word 'string',
+representing the one space between 'string' and '\\' in the top
+line, plus the four preceeding the word 'with' in the second line.
+(Yes, I'm counting the indentation.)
+</para>
+
+<para>
+Line continuation characters are ignored on blank lines and at the end
+of comments.  They are *only* recognized within section and parameter
+lines.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Line Continuation Quirks</title>
+
+<para>Note the following example:</para>
+
+<para><programlisting>
+	param name = parameter value string \
+    \
+    with line continuation.
+</programlisting></para>
+
+<para>
+The middle line is *not* parsed as a blank line because it is first
+concatonated with the top line.  The result is
+</para>
+
+<para><programlisting>
+param name = parameter value string         with line continuation.
+</programlisting></para>
+
+<para>The same is true for comment lines.</para>
+
+<para><programlisting>
+	param name = parameter value string \
+	; comment \
+    with a comment.
+</programlisting></para>
+
+<para>This becomes:</para>
+
+<para><programlisting>
+param name = parameter value string     ; comment     with a comment.
+</programlisting></para>
+
+<para>
+On a section header line, the closing bracket (']') is considered a
+terminating character, and the rest of the line is ignored.  The lines
+</para>
+
+<para><programlisting>
+	[ section   name ] garbage \
+    param  name  = value
+</programlisting></para>
+
+<para>are read as</para>
+
+<para><programlisting>
+	[section name]
+    param name = value
+</programlisting></para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Syntax</title>
+
+<para>The syntax of the smb.conf file is as follows:</para>
+
+<para><programlisting>
+  &lt;file&gt;            :==  { &lt;section&gt; } EOF
+  &lt;section&gt;         :==  &lt;section header&gt; { &lt;parameter line&gt; }
+  &lt;section header&gt;  :==  '[' NAME ']'
+  &lt;parameter line&gt;  :==  NAME '=' VALUE NL
+</programlisting></para>
+
+<para>Basically, this means that</para>
+
+<orderedlist>
+<listitem><para>
+	a file is made up of zero or more sections, and is terminated by
+	an EOF (we knew that).
+</para></listitem>
+
+<listitem><para>
+	A section is made up of a section header followed by zero or more
+	parameter lines.
+</para></listitem>
+
+<listitem><para>
+	A section header is identified by an opening bracket and
+	terminated by the closing bracket.  The enclosed NAME identifies
+	the section.
+</para></listitem>
+
+<listitem><para>
+	A parameter line is divided into a NAME and a VALUE.  The *first*
+	equal sign on the line separates the NAME from the VALUE.  The
+	VALUE is terminated by a newline character (NL = '\n').
+</para></listitem>
+
+</orderedlist>
+
+<sect2>
+<title>About params.c</title>
+
+<para>
+The parsing of the config file is a bit unusual if you are used to
+lex, yacc, bison, etc.  Both lexical analysis (scanning) and parsing
+are performed by params.c.  Values are loaded via callbacks to
+loadparm.c.
+</para>
+</sect2>
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/printing.xml b/docs-xml/Samba3-Developers-Guide/printing.xml
new file mode 100644
index 00000000000..bbdbb85ef70
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/printing.xml
@@ -0,0 +1,395 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="devprinting">
+<chapterinfo>
+	<author>
+		<firstname>Gerald</firstname><surname>Carter</surname>
+	</author>
+	<pubdate>October 2002</pubdate>
+</chapterinfo>
+
+
+<title>Samba Printing Internals</title>
+
+
+<sect1>
+<title>Abstract</title>
+<para>
+The purpose of this document is to provide some insight into
+Samba's printing functionality and also to describe the semantics
+of certain features of Windows client printing.
+</para>
+</sect1>
+
+
+
+<sect1>
+<title>
+Printing Interface to Various Back ends
+</title>
+
+<para>
+Samba uses a table of function pointers to seven functions.  The
+function prototypes are defined in the <varname>printif</varname> structure declared
+in <filename>printing.h</filename>.
+</para>
+
+<itemizedlist>
+	<listitem><para>retrieve the contents of a print queue</para></listitem>
+	<listitem><para>pause the print queue</para></listitem>
+	<listitem><para>resume a paused print queue</para></listitem>
+	<listitem><para>delete a job from the queue</para></listitem>
+	<listitem><para>pause a job in the print queue</para></listitem>
+	<listitem><para>result a paused print job in the queue</para></listitem>
+	<listitem><para>submit a job to the print queue</para></listitem>
+</itemizedlist>
+
+<para>
+Currently there are only two printing back end implementations
+defined.
+</para>
+
+<itemizedlist>
+	<listitem><para>a generic set of functions for working with standard UNIX
+	printing subsystems</para></listitem>
+
+	<listitem><para>a set of CUPS specific functions (this is only enabled if
+	the CUPS libraries were located at compile time).</para></listitem>
+</itemizedlist>
+
+</sect1>
+
+
+
+
+<sect1>
+<title>
+Print Queue TDB's
+</title>
+
+
+<para>
+Samba provides periodic caching of the output from the "lpq command"
+for performance reasons.  This cache time is configurable in seconds.
+Obviously the longer the cache time the less often smbd will be
+required to exec a copy of lpq.  However, the accuracy of the print
+queue contents displayed to clients will be diminished as well.
+</para>
+
+<para>
+The list of currently opened print queue TDB's can be found
+be examining the list of tdb_print_db structures ( see print_db_head
+in printing.c ). A queue TDB is opened using the wrapper function
+printing.c:get_print_db_byname().  The function ensures that smbd
+does not open more than MAX_PRINT_DBS_OPEN in an effort to prevent
+a large print server from exhausting all available file descriptors.
+If the number of open queue TDB's exceeds the MAX_PRINT_DBS_OPEN
+limit, smbd falls back to a most recently used algorithm for maintaining
+a list of open TDB's.
+</para>
+
+<para>
+There are two ways in which a a print job can be entered into
+a print queue's TDB.  The first is to submit the job from a Windows
+client which will insert the job information directly into the TDB.
+The second method is to have the print job picked up by executing the
+"lpq command".
+</para>
+
+<para><programlisting>
+/* included from printing.h */
+struct printjob {
+	pid_t pid; /* which process launched the job */
+	int sysjob; /* the system (lp) job number */
+	int fd; /* file descriptor of open file if open */
+	time_t starttime; /* when the job started spooling */
+	int status; /* the status of this job */
+	size_t size; /* the size of the job so far */
+	int page_count;	/* then number of pages so far */
+	BOOL spooled; /* has it been sent to the spooler yet? */
+	BOOL smbjob; /* set if the job is a SMB job */
+	fstring filename; /* the filename used to spool the file */
+	fstring jobname; /* the job name given to us by the client */
+	fstring user; /* the user who started the job */
+	fstring queuename; /* service number of printer for this job */
+	NT_DEVICEMODE *nt_devmode;
+};
+</programlisting></para>
+
+<para>
+The current manifestation of the printjob structure contains a field
+for the UNIX job id returned from the "lpq command" and a Windows job
+ID (32-bit bounded by PRINT_MAX_JOBID).  When a print job is returned
+by the "lpq command" that does not match an existing job in the queue's
+TDB, a 32-bit job ID above the &lt;*vance doesn't know what word is missing here*&gt; is generating by adding UNIX_JOB_START to
+the id reported by lpq.
+</para>
+
+<para>
+In order to match a 32-bit Windows jobid onto a 16-bit lanman print job
+id, smbd uses an in memory TDB to match the former to a number appropriate
+for old lanman clients.
+</para>
+
+<para>
+When updating a print queue, smbd will perform the following
+steps ( refer to <filename>print.c:print_queue_update()</filename> ):
+</para>
+
+<orderedlist>
+	<listitem><para>Check to see if another smbd is currently in 
+	the process of updating the queue contents by checking the pid 
+	stored in <constant>LOCK/<replaceable>printer_name</replaceable></constant>.  
+	If so, then do not update the TDB.</para></listitem>
+	
+	<listitem><para>Lock the mutex entry in the TDB and store our own pid.
+	Check that this succeeded, else fail.</para></listitem>
+
+	<listitem><para>Store the updated time stamp for the new cache
+	listing</para></listitem>
+
+	<listitem><para>Retrieve the queue listing via "lpq command"</para></listitem>
+
+	<listitem><para><programlisting>
+	foreach job in the queue
+     	{
+		if the job is a UNIX job, create a new entry;
+		if the job has a Windows based jobid, then
+		{
+			Lookup the record by the jobid;
+			if the lookup failed, then
+				treat it as a UNIX job;
+			else
+				update the job status only
+		}
+	}</programlisting></para></listitem>
+
+	<listitem><para>Delete any jobs in the TDB that are not
+	in the in the lpq listing</para></listitem>
+
+	<listitem><para>Store the print queue status in the TDB</para></listitem>
+	
+	<listitem><para>update the cache time stamp again</para></listitem>
+	
+</orderedlist>
+
+<para>
+Note that it is the contents of this TDB that is returned to Windows
+clients and not the actual listing from the "lpq command".
+</para>
+
+<para>
+The NT_DEVICEMODE stored as part of the printjob structure is used to
+store a pointer to a non-default DeviceMode associated with the print
+job.  The pointer will be non-null when the client included a Device
+Mode in the OpenPrinterEx() call and subsequently submitted a job for
+printing on that same handle.  If the client did not include a Device
+Mode in the OpenPrinterEx() request, the nt_devmode field is NULL
+and the job has the printer's device mode associated with it by default.
+</para>
+
+<para>
+Only non-default Device Mode are stored with print jobs in the print
+queue TDB.  Otherwise, the Device Mode is obtained from the printer
+object when the client issues a GetJob(level == 2) request.
+</para>
+
+</sect1>
+
+
+
+
+<sect1>
+<title>
+ChangeID and Client Caching of Printer Information
+</title>
+
+<para>
+[To be filled in later]
+</para>
+</sect1>
+
+
+
+<sect1>
+<title>
+Windows NT/2K Printer Change Notify
+</title>
+
+<para>
+When working with Windows NT+ clients, it is possible for a
+print server to use RPC to send asynchronous change notification
+events to clients for certain printer and print job attributes.
+This can be useful when the client needs to know that a new
+job has been added to the queue for a given printer or that the
+driver for a printer has been changed.  Note that this is done
+entirely orthogonal to cache updates based on a new ChangeID for
+a printer object.
+</para>
+
+<para>
+The basic set of RPC's used to implement change notification are
+</para>
+
+<itemizedlist>
+	<listitem><para>RemoteFindFirstPrinterChangeNotifyEx ( RFFPCN )</para></listitem>
+	<listitem><para>RemoteFindNextPrinterChangeNotifyEx ( RFNPCN )</para></listitem>
+	<listitem><para>FindClosePrinterChangeNotify( FCPCN )</para></listitem>
+	<listitem><para>ReplyOpenPrinter</para></listitem>
+	<listitem><para>ReplyClosePrinter</para></listitem>
+	<listitem><para>RouteRefreshPrinterChangeNotify ( RRPCN )</para></listitem>
+</itemizedlist>
+
+<para>
+One additional RPC is available to a server, but is never used by the
+Windows spooler service:
+</para>
+
+<itemizedlist>
+	<listitem><para>RouteReplyPrinter()</para></listitem>
+</itemizedlist>
+
+<para>
+The opnum for all of these RPC's are defined in include/rpc_spoolss.h
+</para>
+
+<para>
+Windows NT print servers use a bizarre method of sending print
+notification event to clients.  The process of registering a new change
+notification handle is as follows.  The 'C' is for client and the
+'S' is for server.  All error conditions have been eliminated.
+</para>
+
+<para><programlisting>
+C:	Obtain handle to printer or to the printer
+	server via the standard OpenPrinterEx() call.
+S:	Respond with a valid handle to object
+
+C:	Send a RFFPCN request with the previously obtained
+	handle with either (a) set of flags for change events
+	to monitor, or (b) a PRINTER_NOTIFY_OPTIONS structure
+	containing the event information to monitor.  The windows
+	spooler has only been observed to use (b).
+S:	The &lt;* another missing word*&gt; opens a new TCP session to the client (thus requiring
+	all print clients to be CIFS servers as well) and sends
+	a ReplyOpenPrinter() request to the client.
+C:	The client responds with a printer handle that can be used to
+	send event notification messages.
+S:	The server replies success to the RFFPCN request.
+
+C:	The windows spooler follows the RFFPCN with a RFNPCN
+	request to fetch the current values of all monitored
+	attributes.
+S:	The server replies with an array SPOOL_NOTIFY_INFO_DATA
+	structures (contained in a SPOOL_NOTIFY_INFO structure).
+
+C:	If the change notification handle is ever released by the
+	client via a FCPCN request, the server sends a ReplyClosePrinter()
+	request back to the client first.  However a request of this
+	nature from the client is often an indication that the previous
+	notification event was not marshalled correctly by the server
+	or a piece of data was wrong.
+S:	The server closes the internal change notification handle
+	(POLICY_HND) and does not send any further change notification
+	events to the client for that printer or job.
+</programlisting></para>
+
+<para>
+The current list of notification events supported by Samba can be
+found by examining the internal tables in srv_spoolss_nt.c
+</para>
+
+<itemizedlist>
+	<listitem><para>printer_notify_table[]</para></listitem>
+	<listitem><para>job_notify_table[]</para></listitem>
+</itemizedlist>
+
+<para>
+When an event occurs that could be monitored, smbd sends a message
+to itself about the change.  The list of events to be transmitted
+are queued by the smbd process sending the message to prevent an
+overload of TDB usage and the internal message is sent during smbd's
+idle loop (refer to printing/notify.c and the functions
+send_spoolss_notify2_msg() and print_notify_send_messages() ).
+</para>
+
+<para>
+The decision of whether or not the change is to be sent to connected
+clients is made by the routine which actually sends the notification.
+( refer to srv_spoolss_nt.c:recieve_notify2_message() ).
+</para>
+
+<para>
+Because it possible to receive a listing of multiple changes for
+multiple printers, the notification events must be split into
+categories by the printer name.  This makes it possible to group
+multiple change events to be sent in a single RPC according to the
+printer handle obtained via a ReplyOpenPrinter().
+</para>
+
+<para>
+The actual change notification is performed using the RRPCN request
+RPC.  This packet contains
+</para>
+
+
+<itemizedlist>
+	
+<listitem><para>the printer handle registered with the
+client's spooler on which the change occurred</para></listitem>
+
+<listitem><para>The change_low value which was sent as part
+of the last RFNPCN request from the client</para></listitem>
+
+<listitem><para>The SPOOL_NOTIFY_INFO container with the event
+information</para></listitem>
+
+</itemizedlist>
+
+<para>
+A <varname>SPOOL_NOTIFY_INFO</varname> contains:
+</para>
+
+<itemizedlist>
+
+<listitem><para>the version and flags field are predefined
+and should not be changed</para></listitem>
+
+<listitem><para>The count field is the number of entries
+in the SPOOL_NOTIFY_INFO_DATA array</para></listitem>
+
+</itemizedlist>
+
+<para>
+The <varname>SPOOL_NOTIFY_INFO_DATA</varname> entries contain:
+</para>
+
+<itemizedlist>
+
+<listitem><para>The type defines whether or not this event
+is for a printer or a print job</para></listitem>
+
+<listitem><para>The field is the flag identifying the event</para></listitem>
+
+<listitem><para>the notify_data union contains the new valuie of the
+attribute</para></listitem>
+
+<listitem><para>The enc_type defines the size of the structure for marshalling
+and unmarshalling</para></listitem>
+
+<listitem><para>(a) the id must be 0 for a printer event on a printer handle.
+(b) the id must be the job id for an event on a printer job
+(c) the id must be the matching number of the printer index used
+in the response packet to the RFNPCN when using a print server
+handle for notification.  Samba currently uses the snum of
+the printer for this which can break if the list of services
+has been modified since the notification handle was registered.</para></listitem>
+
+<listitem><para>The size is either (a) the string length in UNICODE for strings,
+(b) the size in bytes of the security descriptor, or (c) 0 for
+data values.</para></listitem>
+
+</itemizedlist>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/rpc_plugin.xml b/docs-xml/Samba3-Developers-Guide/rpc_plugin.xml
new file mode 100644
index 00000000000..cc263ffc3e6
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/rpc_plugin.xml
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="rpc-plugin">
+<chapterinfo>
+	<author>
+		<firstname>Anthony</firstname><surname>Liguori</surname>
+		<affiliation>
+			<orgname>IBM</orgname>
+			<address><email>aliguor@us.ibm.com</email></address>
+		</affiliation>
+	</author>
+	<author>
+		<firstname>Jelmer</firstname><surname>Vernooij</surname>
+		<affiliation>
+			<orgname>Samba Team</orgname>
+			<address><email>jelmer@samba.org</email></address>
+		</affiliation>
+	</author>
+	<pubdate>January 2003</pubdate>
+</chapterinfo>
+
+<title>RPC Pluggable Modules</title>
+
+<sect1>
+<title>About</title>
+
+<para>
+This document describes how to make use the new RPC Pluggable Modules features
+of Samba 3.0.  This architecture was added to increase the maintainability of
+Samba allowing RPC Pipes to be worked on separately from the main CVS branch.
+The RPM architecture will also allow third-party vendors to add functionality
+to Samba through plug-ins.
+</para>
+
+</sect1>
+
+<sect1>
+<title>General Overview</title>
+
+<para>
+When an RPC call is sent to smbd, smbd tries to load a shared library by the
+name <filename>librpc_&lt;pipename&gt;.so</filename> to handle the call if
+it doesn't know how to handle the call internally.  For instance, LSA calls
+are handled by <filename>librpc_lsass.so</filename>..
+These shared libraries should be located in the <filename>&lt;sambaroot&gt;/lib/rpc</filename>.  smbd then attempts to call the init_module function within
+the shared library. Check the chapter on modules for more information.
+</para>
+
+<para>
+In the init_module function, the library should call 
+rpc_pipe_register_commands().  This function takes the following arguments:
+</para>
+
+<para><programlisting>
+NTSTATUS rpc_pipe_register_commands(int version, const char *clnt, const char *srv,
+                               const struct api_struct *cmds, int size);
+</programlisting></para>
+
+<variablelist>
+
+<varlistentry><term>version</term>
+<listitem><para>Version number of the RPC interface. Use the define <emphasis>SMB_RPC_INTERFACE_VERSION</emphasis> for this 
+argument.</para></listitem>
+</varlistentry>
+		
+<varlistentry><term>clnt</term>
+<listitem><para>the Client name of the named pipe</para></listitem>
+</varlistentry>
+
+<varlistentry><term>srv</term>
+<listitem><para>the Server name of the named pipe</para></listitem>
+</varlistentry>
+
+<varlistentry><term>cmds</term>
+<listitem><para>a list of api_structs that map RPC ordinal numbers to function calls</para></listitem>
+</varlistentry>
+
+<varlistentry><term>size</term>
+<listitem><para>the number of api_structs contained in cmds</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<para>
+See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of
+how to use this library.
+</para>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/unix-smb.xml b/docs-xml/Samba3-Developers-Guide/unix-smb.xml
new file mode 100644
index 00000000000..b700dfc9dc4
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/unix-smb.xml
@@ -0,0 +1,318 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="unix-smb">
+<chapterinfo>
+	<author>
+		<firstname>Andrew</firstname><surname>Tridgell</surname>
+	</author>
+	<pubdate>April 1995</pubdate>
+</chapterinfo>
+
+<title>NetBIOS in a Unix World</title>
+
+<sect1>
+<title>Introduction</title>
+<para>
+This is a short document that describes some of the issues that
+confront a SMB implementation on unix, and how Samba copes with
+them. They may help people who are looking at unix&lt;-&gt;PC
+interoperability.
+</para>
+
+<para>
+It was written to help out a person who was writing a paper on unix to
+PC connectivity.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Usernames</title>
+<para>
+The SMB protocol has only a loose username concept. Early SMB
+protocols (such as CORE and COREPLUS) have no username concept at
+all. Even in later protocols clients often attempt operations
+(particularly printer operations) without first validating a username
+on the server.
+</para>
+
+<para>
+Unix security is based around username/password pairs. A unix box
+should not allow clients to do any substantive operation without some
+sort of validation. 
+</para>
+
+<para>
+The problem mostly manifests itself when the unix server is in "share
+level" security mode. This is the default mode as the alternative
+"user level" security mode usually forces a client to connect to the
+server as the same user for each connected share, which is
+inconvenient in many sites.
+</para>
+
+<para>
+In "share level" security the client normally gives a username in the
+"session setup" protocol, but does not supply an accompanying
+password. The client then connects to resources using the "tree
+connect" protocol, and supplies a password. The problem is that the
+user on the PC types the username and the password in different
+contexts, unaware that they need to go together to give access to the
+server. The username is normally the one the user typed in when they
+"logged onto" the PC (this assumes Windows for Workgroups). The
+password is the one they chose when connecting to the disk or printer.
+</para>
+
+<para>
+The user often chooses a totally different username for their login as
+for the drive connection. Often they also want to access different
+drives as different usernames. The unix server needs some way of
+divining the correct username to combine with each password.
+</para>
+
+<para>
+Samba tries to avoid this problem using several methods. These succeed
+in the vast majority of cases. The methods include username maps, the
+service%user syntax, the saving of session setup usernames for later
+validation and the derivation of the username from the service name
+(either directly or via the user= option).
+</para>
+
+</sect1>
+
+<sect1>
+<title>File Ownership</title>
+
+<para>
+The commonly used SMB protocols have no way of saying "you can't do
+that because you don't own the file". They have, in fact, no concept
+of file ownership at all.
+</para>
+
+<para>
+This brings up all sorts of interesting problems. For example, when
+you copy a file to a unix drive, and the file is world writeable but
+owned by another user the file will transfer correctly but will
+receive the wrong date. This is because the utime() call under unix
+only succeeds for the owner of the file, or root, even if the file is
+world writeable. For security reasons Samba does all file operations
+as the validated user, not root, so the utime() fails. This can stuff
+up shared development diectories as programs like "make" will not get
+file time comparisons right.
+</para>
+
+<para>
+There are several possible solutions to this problem, including
+username mapping, and forcing a specific username for particular
+shares.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Passwords</title>
+
+<para>
+Many SMB clients uppercase passwords before sending them. I have no
+idea why they do this. Interestingly WfWg uppercases the password only
+if the server is running a protocol greater than COREPLUS, so
+obviously it isn't just the data entry routines that are to blame.
+</para>
+
+<para>
+Unix passwords are case sensitive. So if users use mixed case
+passwords they are in trouble.
+</para>
+
+<para>
+Samba can try to cope with this by either using the "password level"
+option which causes Samba to try the offered password with up to the
+specified number of case changes, or by using the "password server"
+option which allows Samba to do its validation via another machine
+(typically a WinNT server).
+</para>
+
+<para>
+Samba supports the password encryption method used by SMB
+clients. Note that the use of password encryption in Microsoft
+networking leads to password hashes that are "plain text equivalent".
+This means that it is *VERY* important to ensure that the Samba
+smbpasswd file containing these password hashes is only readable
+by the root user. See the documentation ENCRYPTION.txt for more
+details.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Locking</title>
+<para>
+Since samba 2.2, samba supports other types of locking as well. This 
+section is outdated.
+</para>
+
+<para>
+The locking calls available under a DOS/Windows environment are much
+richer than those available in unix. This means a unix server (like
+Samba) choosing to use the standard fcntl() based unix locking calls
+to implement SMB locking has to improvise a bit.
+</para>
+
+<para>
+One major problem is that dos locks can be in a 32 bit (unsigned)
+range. Unix locking calls are 32 bits, but are signed, giving only a 31
+bit range. Unfortunately OLE2 clients use the top bit to select a
+locking range used for OLE semaphores.
+</para>
+
+<para>
+To work around this problem Samba compresses the 32 bit range into 31
+bits by appropriate bit shifting. This seems to work but is not
+ideal. In a future version a separate SMB lockd may be added to cope
+with the problem.
+</para>
+
+<para>
+It also doesn't help that many unix lockd daemons are very buggy and
+crash at the slightest provocation. They normally go mostly unused in
+a unix environment because few unix programs use byte range
+locking. The stress of huge numbers of lock requests from dos/windows
+clients can kill the daemon on some systems.
+</para>
+
+<para>
+The second major problem is the "opportunistic locking" requested by
+some clients. If a client requests opportunistic locking then it is
+asking the server to notify it if anyone else tries to do something on
+the same file, at which time the client will say if it is willing to
+give up its lock. Unix has no simple way of implementing
+opportunistic locking, and currently Samba has no support for it.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Deny Modes</title>
+
+<para>
+When a SMB client opens a file it asks for a particular "deny mode" to
+be placed on the file. These modes (DENY_NONE, DENY_READ, DENY_WRITE,
+DENY_ALL, DENY_FCB and DENY_DOS) specify what actions should be
+allowed by anyone else who tries to use the file at the same time. If
+DENY_READ is placed on the file, for example, then any attempt to open
+the file for reading should fail.
+</para>
+
+<para>
+Unix has no equivalent notion. To implement this Samba uses either lock
+files based on the files inode and placed in a separate lock
+directory or a shared memory implementation. The lock file method 
+is clumsy and consumes processing and file resources,
+the shared memory implementation is vastly prefered and is turned on
+by default for those systems that support it.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Trapdoor UIDs</title>
+<para>
+A SMB session can run with several uids on the one socket. This
+happens when a user connects to two shares with different
+usernames. To cope with this the unix server needs to switch uids
+within the one process. On some unixes (such as SCO) this is not
+possible. This means that on those unixes the client is restricted to
+a single uid.
+</para>
+
+<para>
+Note that you can also get the "trapdoor uid" message for other
+reasons. Please see the FAQ for details.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Port numbers</title>
+<para>
+There is a convention that clients on sockets use high "unprivileged"
+port numbers (>1000) and connect to servers on low "privilegedg" port
+numbers. This is enforced in Unix as non-root users can't open a
+socket for listening on port numbers less than 1000.
+</para>
+
+<para>
+Most PC based SMB clients (such as WfWg and WinNT) don't follow this
+convention completely. The main culprit is the netbios nameserving on
+udp port 137. Name query requests come from a source port of 137. This
+is a problem when you combine it with the common firewalling technique
+of not allowing incoming packets on low port numbers. This means that
+these clients can't query a netbios nameserver on the other side of a
+low port based firewall.
+</para>
+
+<para>
+The problem is more severe with netbios node status queries. I've
+found that WfWg, Win95 and WinNT3.5 all respond to netbios node status
+queries on port 137 no matter what the source port was in the
+request. This works between machines that are both using port 137, but
+it means it's not possible for a unix user to do a node status request
+to any of these OSes unless they are running as root. The answer comes
+back, but it goes to port 137 which the unix user can't listen
+on. Interestingly WinNT3.1 got this right - it sends node status
+responses back to the source port in the request.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Protocol Complexity</title>
+<para>
+There are many "protocol levels" in the SMB protocol. It seems that
+each time new functionality was added to a Microsoft operating system,
+they added the equivalent functions in a new protocol level of the SMB
+protocol to "externalise" the new capabilities.
+</para>
+
+<para>
+This means the protocol is very "rich", offering many ways of doing
+each file operation. This means SMB servers need to be complex and
+large. It also means it is very difficult to make them bug free. It is
+not just Samba that suffers from this problem, other servers such as
+WinNT don't support every variation of every call and it has almost
+certainly been a headache for MS developers to support the myriad of
+SMB calls that are available.
+</para>
+
+<para>
+There are about 65 "top level" operations in the SMB protocol (things
+like SMBread and SMBwrite). Some of these include hundreds of
+sub-functions (SMBtrans has at least 120 sub-functions, like
+DosPrintQAdd and NetSessionEnum). All of them take several options
+that can change the way they work. Many take dozens of possible
+"information levels" that change the structures that need to be
+returned. Samba supports all but 2 of the "top level" functions. It
+supports only 8 (so far) of the SMBtrans sub-functions. Even NT
+doesn't support them all.
+</para>
+
+<para>
+Samba currently supports up to the "NT LM 0.12" protocol, which is the
+one preferred by Win95 and WinNT3.5. Luckily this protocol level has a
+"capabilities" field which specifies which super-duper new-fangled
+options the server suports. This helps to make the implementation of
+this protocol level much easier.
+</para>
+
+<para>
+There is also a problem with the SMB specications. SMB is a X/Open
+spec, but the X/Open book is far from ideal, and fails to cover many
+important issues, leaving much to the imagination. Microsoft recently
+renamed the SMB protocol CIFS (Common Internet File System) and have 
+published new specifications. These are far superior to the old 
+X/Open documents but there are still undocumented calls and features. 
+This specification is actively being worked on by a CIFS developers 
+mailing list hosted by Microsft.
+</para>
+</sect1>
+</chapter>
+
diff --git a/docs-xml/Samba3-Developers-Guide/vfs.xml b/docs-xml/Samba3-Developers-Guide/vfs.xml
new file mode 100644
index 00000000000..44e0bd68636
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/vfs.xml
@@ -0,0 +1,924 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="vfs">
+<chapterinfo>
+	<author>
+		<firstname>Alexander</firstname><surname>Bokovoy</surname>
+		<affiliation>
+			<address><email>ab@samba.org</email></address>
+		</affiliation>
+	</author>
+	<author>
+		<firstname>Stefan</firstname><surname>Metzmacher</surname>
+		<affiliation>
+			<address><email>metze@samba.org</email></address>
+		</affiliation>
+	</author>
+	<pubdate> 27 May 2003 </pubdate>
+</chapterinfo>
+
+<title>VFS Modules</title>
+
+<sect1>
+<title>The Samba (Posix) VFS layer</title>
+
+<para>While most of Samba deployments are done using POSIX-compatible
+operating systems, there is clearly more to a file system than what is
+required by POSIX when it comes to adopting semantics of NT file
+system. Since Samba 2.2 all file-system related operations go through
+an abstraction layer for virtual file system (VFS) that is modelled
+after both POSIX and additional functions needed to transform NTFS
+semantics.
+</para>
+
+<para>
+This abstraction layer now provides more features than a regular POSIX
+file system could fill in. It is not required that all of them should
+be implemented by your particular file system.  However, when those
+features are available, Samba would advertize them to a CIFS client
+and they might be used by an application and in case of Windows client
+that might mean a client expects even more additional functionality
+when it encounters those features. There is a practical reason to
+allow handling of this snowfall without modifying the Samba core and
+it is fulfilled by providing an infrastructure to dynamically load VFS
+modules at run time.
+</para>
+
+<para>Each VFS module could implement a number of VFS operations. The
+way it does it is irrelevant, only two things actually matter: whether
+specific implementation wants to cooperate with other modules'
+implementations or not, and whether module needs to store additional
+information that is specific to a context it is operating in. Multiple
+VFS modules could be loaded at the same time and it is even possible
+to load several instances of the same VFS module with different
+parameters.
+</para>
+
+<sect2>
+<title>The general interface</title>
+
+<para>A VFS module has three major components:
+<itemizedlist>
+<listitem><emphasis>An initialization function</emphasis> that is
+called during the module load to register implemented
+operations.</listitem>
+<listitem><emphasis>An operations table</emphasis> representing a
+mapping between statically defined module functions and VFS layer
+operations.</listitem>
+<listitem><emphasis>Module functions</emphasis> that do actual
+work.</listitem>
+</itemizedlist>
+</para>
+
+<para>While this structure has been first applied to the VFS
+subsystem, it is now commonly used across all Samba 3 subsystems that
+support loadable modules. In fact, one module could provide a number
+of interfaces to different subsystems by exposing different
+<emphasis>operation tables</emphasis> through separate
+<emphasis>initialization functions</emphasis>.</para>
+
+<para><emphasis>An initialization function</emphasis> is used to
+register module with Samba run-time. As Samba internal structures and
+API are changed over lifetime, each released version has a VFS
+interface version that is increased as VFS development progresses or
+any of underlying Samba structures are changed in binary-incompatible
+way. When VFS module is compiled in, VFS interface version of that
+Samba environment is embedded into the module's binary object and is
+checked by the Samba core upon module load. If VFS interface number
+reported by the module isn't the same Samba core knows about, version
+conflict is detected and module dropped to avoid any potential memory
+corruption when accessing (changed) Samba structures.
+</para>
+
+<para>Therefore, initialization function passes three parameters to the
+VFS registration function, <literal>smb_register_vfs()</literal>
+<itemizedlist>
+  <listitem><emphasis>interface version number</emphasis>, as constant
+  <literal>SMB_VFS_INTERFACE_VERSION</literal>, </listitem>
+  <listitem><emphasis>module name</emphasis>, under which Samba core
+  will know it, and</listitem>
+  <listitem><emphasis>an operations' table</emphasis>.</listitem>
+</itemizedlist>
+</para>
+
+<para>The <emphasis>operations' table</emphasis> defines which
+functions in the module would correspond to specific VFS operations
+and how those functions would co-operate with the rest of VFS
+subsystem. Each operation could perform in a following ways:
+<itemizedlist>
+  <listitem><emphasis>transparent</emphasis>, meaning that while
+  operation is overriden, the module will still call a previous
+  implementation, before or after its own action. This mode is
+  indicated by the constant
+  <literal>SMB_VFS_LAYER_TRANSPARENT</literal>;
+  </listitem>
+  <listitem><emphasis>opaque</emphasis>, for the implementations that
+  are terminating sequence of actions. For example, it is used to
+  implement POSIX operation on top of non-POSIX file system or even
+  not a file system at all, like a database for a personal audio
+  collection. Use constant <literal>SMB_VFS_LAYER_OPAQUE</literal> for
+  this mode;</listitem>
+  <listitem><emphasis>splitter</emphasis>, a way when some file system
+  activity is done in addition to the transparently calling previous
+  implentation. This usually involves mangling the result of that call
+  before returning it back to the caller. This mode is selected by
+  <literal>SMB_VFS_LAYER_SPLITTER</literal> constant;</listitem>
+  <listitem><emphasis>logger</emphasis> does not change anything or
+  performs any additional VFS operations. When
+  <emphasis>logger</emphasis> module acts, information about
+  operations is logged somewhere using an external facility (or
+  Samba's own debugging tools) but not the VFS layer. In order to
+  describe this type of activity use constant
+  <literal>SMB_VFS_LAYER_LOGGER</literal>;
+  </listitem>
+  <listitem>On contrary, <emphasis>scanner</emphasis> module does call
+  other VFS operations while processing the data that goes through the
+  system. This type of operation is indicated by the
+  <literal>SMB_VFS_LAYER_SCANNER</literal> constant.</listitem>
+</itemizedlist>
+</para>
+
+<para>Fundamentally, there are three types:
+<emphasis>transparent</emphasis>, <emphasis>opaque</emphasis>, and
+<emphasis>logger</emphasis>. <emphasis>Splitter</emphasis> and
+<emphasis>scanner</emphasis> may confuse developers (and indeed they
+are confused as our experience has shown) but this separation is to
+better expose the nature of a module's actions. Most of modules
+developed so far are either one of those three fundamental types with
+transparent and opaque being prevalent.
+</para>
+
+<para>
+Each VFS operation has a vfs_op_type, a function pointer and a handle
+pointer in the struct vfs_ops and tree macros to make it easier to
+call the operations.  (Take a look at
+<filename>include/vfs.h</filename> and
+<filename>include/vfs_macros.h</filename>.)
+</para>
+
+<para><programlisting>
+typedef enum _vfs_op_type {
+	SMB_VFS_OP_NOOP = -1,
+
+	...
+
+	/* File operations */
+
+	SMB_VFS_OP_OPEN,
+	SMB_VFS_OP_CLOSE,
+	SMB_VFS_OP_READ,
+	SMB_VFS_OP_WRITE,
+	SMB_VFS_OP_LSEEK,
+	SMB_VFS_OP_SENDFILE,
+
+	...
+
+	SMB_VFS_OP_LAST
+} vfs_op_type;
+</programlisting></para>
+
+<para>This struct contains the function and handle pointers for all operations.<programlisting>
+struct vfs_ops {
+	struct vfs_fn_pointers {
+		...
+		
+		/* File operations */
+		
+		int (*open)(struct vfs_handle_struct *handle,
+			struct connection_struct *conn,
+			const char *fname, int flags, mode_t mode);
+		int (*close)(struct vfs_handle_struct *handle,
+			struct files_struct *fsp, int fd);
+		ssize_t (*read)(struct vfs_handle_struct *handle, 
+			struct files_struct *fsp, int fd, void *data, size_t n);
+		ssize_t (*write)(struct vfs_handle_struct *handle, 
+			struct files_struct *fsp, int fd, 
+			const void *data, size_t n);
+		SMB_OFF_T (*lseek)(struct vfs_handle_struct *handle, 
+			struct files_struct *fsp, int fd, 
+			SMB_OFF_T offset, int whence);
+		ssize_t (*sendfile)(struct vfs_handle_struct *handle, 
+			int tofd, files_struct *fsp, int fromfd, 
+			const DATA_BLOB *header, SMB_OFF_T offset, size_t count);
+
+		...
+	} ops;
+	
+	struct vfs_handles_pointers {
+		...
+		
+		/* File operations */
+		
+		struct vfs_handle_struct *open;
+		struct vfs_handle_struct *close;
+		struct vfs_handle_struct *read;
+		struct vfs_handle_struct *write;
+		struct vfs_handle_struct *lseek;
+		struct vfs_handle_struct *sendfile;
+		
+		...
+	} handles;
+};
+</programlisting></para>
+
+<para>
+This macros SHOULD be used to call any vfs operation.
+DO NOT ACCESS conn-&gt;vfs.ops.* directly !!!
+<programlisting>
+...
+	
+/* File operations */
+#define SMB_VFS_OPEN(conn, fname, flags, mode) \
+	((conn)-&gt;vfs.ops.open((conn)-&gt;vfs.handles.open,\
+	 (conn), (fname), (flags), (mode)))
+#define SMB_VFS_CLOSE(fsp, fd) \
+	((fsp)-&gt;conn-&gt;vfs.ops.close(\
+	(fsp)-&gt;conn-&gt;vfs.handles.close, (fsp), (fd)))
+#define SMB_VFS_READ(fsp, fd, data, n) \
+	((fsp)-&gt;conn-&gt;vfs.ops.read(\
+	(fsp)-&gt;conn-&gt;vfs.handles.read,\
+	 (fsp), (fd), (data), (n)))
+#define SMB_VFS_WRITE(fsp, fd, data, n) \
+	((fsp)-&gt;conn-&gt;vfs.ops.write(\
+	(fsp)-&gt;conn-&gt;vfs.handles.write,\
+	 (fsp), (fd), (data), (n)))
+#define SMB_VFS_LSEEK(fsp, fd, offset, whence) \
+	((fsp)-&gt;conn-&gt;vfs.ops.lseek(\
+	(fsp)-&gt;conn-&gt;vfs.handles.lseek,\
+	 (fsp), (fd), (offset), (whence)))
+#define SMB_VFS_SENDFILE(tofd, fsp, fromfd, header, offset, count) \
+	((fsp)-&gt;conn-&gt;vfs.ops.sendfile(\
+	(fsp)-&gt;conn-&gt;vfs.handles.sendfile,\
+	 (tofd), (fsp), (fromfd), (header), (offset), (count)))
+
+...
+</programlisting></para>
+
+</sect2>
+
+<sect2>
+<title>Possible VFS operation layers</title>
+
+<para>
+These values are used by the VFS subsystem when building the conn-&gt;vfs 
+and conn-&gt;vfs_opaque structs for a connection with multiple VFS modules. 
+Internally, Samba differentiates only opaque and transparent layers at this process.
+Other types are used for providing better diagnosing facilities.
+</para>
+
+<para>
+Most modules will provide transparent layers. Opaque layer is for modules
+which implement actual file system calls (like DB-based VFS). For example,
+default POSIX VFS which is built in into Samba is an opaque VFS module.
+</para>
+
+<para>    
+Other layer types (logger, splitter, scanner) were designed to provide different 
+degree of transparency and for diagnosing VFS module behaviour.
+</para>
+
+<para>
+Each module can implement several layers at the same time provided that only
+one layer is used per each operation.
+</para>
+
+<para><programlisting>
+typedef enum _vfs_op_layer {
+	SMB_VFS_LAYER_NOOP = -1,	/* - For using in VFS module to indicate end of array */
+					/*   of operations description */
+	SMB_VFS_LAYER_OPAQUE = 0,	/* - Final level, does not call anything beyond itself */
+	SMB_VFS_LAYER_TRANSPARENT,	/* - Normal operation, calls underlying layer after */
+					/*   possibly changing passed data */
+	SMB_VFS_LAYER_LOGGER,		/* - Logs data, calls underlying layer, logging may not */
+					/*   use Samba VFS */
+	SMB_VFS_LAYER_SPLITTER,		/* - Splits operation, calls underlying layer _and_ own facility, */
+					/*   then combines result */
+	SMB_VFS_LAYER_SCANNER		/* - Checks data and possibly initiates additional */
+					/*   file activity like logging to files _inside_ samba VFS */
+} vfs_op_layer;
+</programlisting></para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>The Interaction between the Samba VFS subsystem and the modules</title>
+
+<sect2>
+<title>Initialization and registration</title>
+
+<para>
+As each Samba module a VFS module should have a 
+<programlisting>NTSTATUS vfs_example_init(void);</programlisting> function if it's staticly linked to samba or
+<programlisting>NTSTATUS init_module(void);</programlisting> function if it's a shared module.
+</para>
+
+<para>
+This should be the only non static function inside the module.
+Global variables should also be static!
+</para>
+
+<para>
+The module should register its functions via the
+<programlisting>
+NTSTATUS smb_register_vfs(int version, const char *name, vfs_op_tuple *vfs_op_tuples);
+</programlisting> function.
+</para>
+
+<variablelist>
+
+<varlistentry><term>version</term>
+<listitem><para>should be filled with SMB_VFS_INTERFACE_VERSION</para></listitem>
+</varlistentry>
+
+<varlistentry><term>name</term>
+<listitem><para>this is the name witch can be listed in the 
+<command>vfs objects</command> parameter to use this module.</para></listitem>
+</varlistentry>
+
+<varlistentry><term>vfs_op_tuples</term>
+<listitem><para>
+this is an array of vfs_op_tuple's.
+(vfs_op_tuples is descripted in details below.)
+</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<para>
+For each operation the module wants to provide it has a entry in the 
+vfs_op_tuple array.
+</para>
+
+<programlisting>
+typedef struct _vfs_op_tuple {
+	void* op;
+	vfs_op_type type;
+	vfs_op_layer layer;
+} vfs_op_tuple;
+</programlisting>
+
+<variablelist>
+
+<varlistentry><term>op</term>
+<listitem><para>the function pointer to the specified function.</para></listitem>
+</varlistentry>
+
+<varlistentry><term>type</term>
+<listitem><para>the vfs_op_type of the function to specified witch operation the function provides.</para></listitem>
+</varlistentry>
+
+<varlistentry><term>layer</term>
+<listitem><para>the vfs_op_layer in whitch the function operates.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<para>A simple example:</para>
+
+<programlisting>
+static vfs_op_tuple example_op_tuples[] = {	
+	{SMB_VFS_OP(example_connect),	SMB_VFS_OP_CONNECT,	SMB_VFS_LAYER_TRANSPARENT},
+	{SMB_VFS_OP(example_disconnect),	SMB_VFS_OP_DISCONNECT,	SMB_VFS_LAYER_TRANSPARENT},
+
+	{SMB_VFS_OP(example_rename),	SMB_VFS_OP_RENAME,	SMB_VFS_LAYER_OPAQUE},
+
+	/* This indicates the end of the array */
+	{SMB_VFS_OP(NULL),				SMB_VFS_OP_NOOP,	SMB_VFS_LAYER_NOOP}
+};
+
+NTSTATUS init_module(void)
+{
+	return smb_register_vfs(SMB_VFS_INTERFACE_VERSION, &quot;example&quot;, example_op_tuples);
+}
+</programlisting>
+
+</sect2>
+
+<sect2>
+<title>How the Modules handle per connection data</title>
+
+<para>Each VFS function has as first parameter a pointer to the modules vfs_handle_struct.
+</para>
+
+<programlisting>
+typedef struct vfs_handle_struct {
+	struct vfs_handle_struct  *next, *prev;
+	const char *param;
+	struct vfs_ops vfs_next;
+	struct connection_struct *conn;
+	void *data;
+	void (*free_data)(void **data);
+} vfs_handle_struct;
+</programlisting>
+
+<variablelist>
+
+<varlistentry><term>param</term>
+<listitem><para>this is the module parameter specified in the <command>vfs objects</command> parameter.</para>
+<para>e.g. for 'vfs objects = example:test' param would be &quot;test&quot;.</para></listitem>
+</varlistentry>
+
+<varlistentry><term>vfs_next</term>
+<listitem><para>This vfs_ops struct contains the information for calling the next module operations.
+Use the SMB_VFS_NEXT_* macros to call a next module operations and
+don't access handle-&gt;vfs_next.ops.* directly!</para></listitem>
+</varlistentry>
+
+<varlistentry><term>conn</term>
+<listitem><para>This is a pointer back to the connection_struct to witch the handle belongs.</para></listitem>
+</varlistentry>
+
+<varlistentry><term>data</term>
+<listitem><para>This is a pointer for holding module private data.
+You can alloc data with connection life time on the handle-&gt;conn-&gt;mem_ctx TALLOC_CTX.
+But you can also manage the memory allocation yourself.</para></listitem>
+</varlistentry>
+
+<varlistentry><term>free_data</term>
+<listitem><para>This is a function pointer to a function that free's the module private data.
+If you talloc your private data on the TALLOC_CTX handle-&gt;conn-&gt;mem_ctx,
+you can set this function pointer to NULL.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<para>Some useful MACROS for handle private data.
+</para>
+
+<programlisting>
+#define SMB_VFS_HANDLE_GET_DATA(handle, datap, type, ret) { \
+	if (!(handle)||((datap=(type *)(handle)-&gt;data)==NULL)) { \
+		DEBUG(0,(&quot;%s() failed to get vfs_handle-&gt;data!\n&quot;,FUNCTION_MACRO)); \
+		ret; \
+	} \
+}
+
+#define SMB_VFS_HANDLE_SET_DATA(handle, datap, free_fn, type, ret) { \
+	if (!(handle)) { \
+		DEBUG(0,(&quot;%s() failed to set handle-&gt;data!\n&quot;,FUNCTION_MACRO)); \
+		ret; \
+	} else { \
+		if ((handle)-&gt;free_data) { \
+			(handle)-&gt;free_data(&amp;(handle)-&gt;data); \
+		} \
+		(handle)-&gt;data = (void *)datap; \
+		(handle)-&gt;free_data = free_fn; \
+	} \
+}
+
+#define SMB_VFS_HANDLE_FREE_DATA(handle) { \
+	if ((handle) &amp;&amp; (handle)-&gt;free_data) { \
+		(handle)-&gt;free_data(&amp;(handle)-&gt;data); \
+	} \
+}
+</programlisting>
+
+<para>How SMB_VFS_LAYER_TRANSPARENT functions can call the SMB_VFS_LAYER_OPAQUE functions.</para>
+
+<para>The easiest way to do this is to use the SMB_VFS_OPAQUE_* macros.
+</para>
+
+<programlisting>
+...
+/* File operations */
+#define SMB_VFS_OPAQUE_OPEN(conn, fname, flags, mode) \
+	((conn)-&gt;vfs_opaque.ops.open(\
+	(conn)-&gt;vfs_opaque.handles.open,\
+	 (conn), (fname), (flags), (mode)))
+#define SMB_VFS_OPAQUE_CLOSE(fsp, fd) \
+	((fsp)-&gt;conn-&gt;vfs_opaque.ops.close(\
+	(fsp)-&gt;conn-&gt;vfs_opaque.handles.close,\
+	 (fsp), (fd)))
+#define SMB_VFS_OPAQUE_READ(fsp, fd, data, n) \
+	((fsp)-&gt;conn-&gt;vfs_opaque.ops.read(\
+	(fsp)-&gt;conn-&gt;vfs_opaque.handles.read,\
+	 (fsp), (fd), (data), (n)))
+#define SMB_VFS_OPAQUE_WRITE(fsp, fd, data, n) \
+	((fsp)-&gt;conn-&gt;vfs_opaque.ops.write(\
+	(fsp)-&gt;conn-&gt;vfs_opaque.handles.write,\
+	 (fsp), (fd), (data), (n)))
+#define SMB_VFS_OPAQUE_LSEEK(fsp, fd, offset, whence) \
+	((fsp)-&gt;conn-&gt;vfs_opaque.ops.lseek(\
+	(fsp)-&gt;conn-&gt;vfs_opaque.handles.lseek,\
+	 (fsp), (fd), (offset), (whence)))
+#define SMB_VFS_OPAQUE_SENDFILE(tofd, fsp, fromfd, header, offset, count) \
+	((fsp)-&gt;conn-&gt;vfs_opaque.ops.sendfile(\
+	(fsp)-&gt;conn-&gt;vfs_opaque.handles.sendfile,\
+	 (tofd), (fsp), (fromfd), (header), (offset), (count)))
+...
+</programlisting>
+
+<para>How SMB_VFS_LAYER_TRANSPARENT functions can call the next modules functions.</para>
+
+<para>The easiest way to do this is to use the SMB_VFS_NEXT_* macros.
+</para>
+
+<programlisting>
+...
+/* File operations */
+#define SMB_VFS_NEXT_OPEN(handle, conn, fname, flags, mode) \
+	((handle)-&gt;vfs_next.ops.open(\
+	(handle)-&gt;vfs_next.handles.open,\
+	 (conn), (fname), (flags), (mode)))
+#define SMB_VFS_NEXT_CLOSE(handle, fsp, fd) \
+	((handle)-&gt;vfs_next.ops.close(\
+	(handle)-&gt;vfs_next.handles.close,\
+	 (fsp), (fd)))
+#define SMB_VFS_NEXT_READ(handle, fsp, fd, data, n) \
+	((handle)-&gt;vfs_next.ops.read(\
+	(handle)-&gt;vfs_next.handles.read,\
+	 (fsp), (fd), (data), (n)))
+#define SMB_VFS_NEXT_WRITE(handle, fsp, fd, data, n) \
+	((handle)-&gt;vfs_next.ops.write(\
+	(handle)-&gt;vfs_next.handles.write,\
+	 (fsp), (fd), (data), (n)))
+#define SMB_VFS_NEXT_LSEEK(handle, fsp, fd, offset, whence) \
+	((handle)-&gt;vfs_next.ops.lseek(\
+	(handle)-&gt;vfs_next.handles.lseek,\
+	 (fsp), (fd), (offset), (whence)))
+#define SMB_VFS_NEXT_SENDFILE(handle, tofd, fsp, fromfd, header, offset, count) \
+	((handle)-&gt;vfs_next.ops.sendfile(\
+	(handle)-&gt;vfs_next.handles.sendfile,\
+	 (tofd), (fsp), (fromfd), (header), (offset), (count)))
+...
+</programlisting>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Upgrading to the New VFS Interface</title>
+
+<sect2>
+<title>Upgrading from 2.2.* and 3.0aplha modules</title>
+
+<orderedlist>
+<listitem><para>
+Add &quot;vfs_handle_struct *handle, &quot; as first parameter to all vfs operation functions.
+e.g. example_connect(connection_struct *conn, const char *service, const char *user);
+-&gt;   example_connect(vfs_handle_struct *handle, connection_struct *conn, const char *service, const char *user);
+</para></listitem>
+
+<listitem><para>
+Replace &quot;default_vfs_ops.&quot; with &quot;smb_vfs_next_&quot;.
+e.g. default_vfs_ops.connect(conn, service, user);
+-&gt;   smb_vfs_next_connect(conn, service, user);
+</para></listitem>
+
+<listitem><para>
+Uppercase all &quot;smb_vfs_next_*&quot; functions.
+e.g. smb_vfs_next_connect(conn, service, user);
+-&gt;   SMB_VFS_NEXT_CONNECT(conn, service, user);
+</para></listitem>
+
+<listitem><para>
+Add &quot;handle, &quot; as first parameter to all SMB_VFS_NEXT_*() calls.
+e.g. SMB_VFS_NEXT_CONNECT(conn, service, user);
+-&gt;   SMB_VFS_NEXT_CONNECT(handle, conn, service, user);
+</para></listitem>
+
+<listitem><para>
+(Only for 2.2.* modules) 
+Convert the old struct vfs_ops example_ops to 
+a vfs_op_tuple example_op_tuples[] array.
+e.g.
+<programlisting>
+struct vfs_ops example_ops = {
+	/* Disk operations */
+	example_connect,		/* connect */
+	example_disconnect,		/* disconnect */
+	NULL,				/* disk free *
+	/* Directory operations */
+	NULL,				/* opendir */
+	NULL,				/* readdir */
+	NULL,				/* mkdir */
+	NULL,				/* rmdir */
+	NULL,				/* closedir */
+	/* File operations */
+	NULL,				/* open */
+	NULL,				/* close */
+	NULL,				/* read  */
+	NULL,				/* write */
+	NULL,				/* lseek */
+	NULL,				/* sendfile */
+	NULL,				/* rename */
+	NULL,				/* fsync */
+	example_stat,			/* stat  */
+	example_fstat,			/* fstat */
+	example_lstat,			/* lstat */
+	NULL,				/* unlink */
+	NULL,				/* chmod */
+	NULL,				/* fchmod */
+	NULL,				/* chown */
+	NULL,				/* fchown */
+	NULL,				/* chdir */
+	NULL,				/* getwd */
+	NULL,				/* utime */
+	NULL,				/* ftruncate */
+	NULL,				/* lock */
+	NULL,				/* symlink */
+	NULL,				/* readlink */
+	NULL,				/* link */
+	NULL,				/* mknod */
+	NULL,				/* realpath */
+	NULL,				/* fget_nt_acl */
+	NULL,				/* get_nt_acl */
+	NULL,				/* fset_nt_acl */
+	NULL,				/* set_nt_acl */
+
+	NULL,				/* chmod_acl */
+	NULL,				/* fchmod_acl */
+
+	NULL,				/* sys_acl_get_entry */
+	NULL,				/* sys_acl_get_tag_type */
+	NULL,				/* sys_acl_get_permset */
+	NULL,				/* sys_acl_get_qualifier */
+	NULL,				/* sys_acl_get_file */
+	NULL,				/* sys_acl_get_fd */
+	NULL,				/* sys_acl_clear_perms */
+	NULL,				/* sys_acl_add_perm */
+	NULL,				/* sys_acl_to_text */
+	NULL,				/* sys_acl_init */
+	NULL,				/* sys_acl_create_entry */
+	NULL,				/* sys_acl_set_tag_type */
+	NULL,				/* sys_acl_set_qualifier */
+	NULL,				/* sys_acl_set_permset */
+	NULL,				/* sys_acl_valid */
+	NULL,				/* sys_acl_set_file */
+	NULL,				/* sys_acl_set_fd */
+	NULL,				/* sys_acl_delete_def_file */
+	NULL,				/* sys_acl_get_perm */
+	NULL,				/* sys_acl_free_text */
+	NULL,				/* sys_acl_free_acl */
+	NULL				/* sys_acl_free_qualifier */
+};
+</programlisting>
+-&gt;
+<programlisting> 
+static vfs_op_tuple example_op_tuples[] = {
+	{SMB_VFS_OP(example_connect),	SMB_VFS_OP_CONNECT,	SMB_VFS_LAYER_TRANSPARENT},
+	{SMB_VFS_OP(example_disconnect),	SMB_VFS_OP_DISCONNECT,	SMB_VFS_LAYER_TRANSPARENT},
+	
+	{SMB_VFS_OP(example_fstat), 	SMB_VFS_OP_FSTAT,	SMB_VFS_LAYER_TRANSPARENT},
+	{SMB_VFS_OP(example_stat),		SMB_VFS_OP_STAT,	SMB_VFS_LAYER_TRANSPARENT},
+	{SMB_VFS_OP(example_lstat), 	SMB_VFS_OP_LSTAT,	SMB_VFS_LAYER_TRANSPARENT},
+
+	{SMB_VFS_OP(NULL),				SMB_VFS_OP_NOOP,	SMB_VFS_LAYER_NOOP}
+};
+</programlisting>
+</para></listitem>
+
+<listitem><para>
+Move the example_op_tuples[] array to the end of the file. 
+</para></listitem>
+
+<listitem><para>
+Add the init_module() function at the end of the file.
+e.g.
+<programlisting>
+NTSTATUS init_module(void)
+{
+	return smb_register_vfs(SMB_VFS_INTERFACE_VERSION,&quot;example&quot;,example_op_tuples);
+}
+</programlisting>
+</para></listitem>
+
+<listitem><para>
+Check if your vfs_init() function does more then just prepare the vfs_ops structs or
+remember the struct smb_vfs_handle_struct.
+<simplelist>
+<member>If NOT you can remove the vfs_init() function.</member>
+<member>If YES decide if you want to move the code to the example_connect() operation or to the init_module(). And then remove vfs_init().
+  e.g. a debug class registration should go into init_module() and the allocation of private data should go to example_connect().</member>
+</simplelist>
+</para></listitem>
+
+<listitem><para>
+(Only for 3.0alpha* modules) 
+Check if your vfs_done() function contains needed code.
+<simplelist>
+<member>If NOT you can remove the vfs_done() function.</member>
+<member>If YES decide if you can move the code to the example_disconnect() operation. Otherwise register a SMB_EXIT_EVENT with smb_register_exit_event(); (Described in the <link linkend="modules">modules section</link>) And then remove vfs_done(). e.g. the freeing of private data should go to example_disconnect().
+</member>
+</simplelist>
+</para></listitem>
+
+<listitem><para>
+Check if you have any global variables left.
+Decide if it wouldn't be better to have this data on a connection basis.
+<simplelist>
+  <member>If NOT leave them as they are. (e.g. this could be the variable for the private debug class.)</member>
+  <member>If YES pack all this data into a struct. You can use handle-&gt;data to point to such a struct on a per connection basis.</member>
+</simplelist>
+
+  e.g. if you have such a struct:
+<programlisting>    
+struct example_privates {
+	char *some_string;
+	int db_connection;
+};
+</programlisting>	
+first way of doing it:
+<programlisting>
+static int example_connect(vfs_handle_struct *handle,
+	connection_struct *conn, const char *service, 
+	const char* user)
+{
+	struct example_privates *data = NULL;
+
+	/* alloc our private data */
+	data = (struct example_privates *)talloc_zero(conn-&gt;mem_ctx, sizeof(struct example_privates));
+	if (!data) {
+		DEBUG(0,(&quot;talloc_zero() failed\n&quot;));
+		return -1;
+	}
+
+	/* init out private data */
+	data-&gt;some_string = talloc_strdup(conn-&gt;mem_ctx,&quot;test&quot;);
+	if (!data-&gt;some_string) {
+		DEBUG(0,(&quot;talloc_strdup() failed\n&quot;));
+		return -1;
+	}
+
+	data-&gt;db_connection = open_db_conn();
+
+	/* and now store the private data pointer in handle-&gt;data
+	 * we don't need to specify a free_function here because
+	 * we use the connection TALLOC context.
+	 * (return -1 if something failed.)
+	 */
+	VFS_HANDLE_SET_DATA(handle, data, NULL, struct example_privates, return -1);
+
+	return SMB_VFS_NEXT_CONNECT(handle,conn,service,user);
+}
+
+static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd)
+{
+	struct example_privates *data = NULL;
+	
+	/* get the pointer to our private data
+	 * return -1 if something failed
+	 */
+	SMB_VFS_HANDLE_GET_DATA(handle, data, struct example_privates, return -1);
+	
+	/* do something here...*/
+	DEBUG(0,(&quot;some_string: %s\n&quot;,data-&gt;some_string));
+	
+	return SMB_VFS_NEXT_CLOSE(handle, fsp, fd);
+}
+</programlisting>
+second way of doing it:
+<programlisting>
+static void free_example_privates(void **datap)
+{
+	struct example_privates *data = (struct example_privates *)*datap;
+	
+	SAFE_FREE(data-&gt;some_string);
+	SAFE_FREE(data);
+	
+	*datap = NULL;
+	
+	return;
+}
+
+static int example_connect(vfs_handle_struct *handle, 
+	connection_struct *conn, const char *service, 
+	const char* user)
+{
+	struct example_privates *data = NULL;
+
+	/* alloc our private data */
+	data = (struct example_privates *)malloc(sizeof(struct example_privates));
+	if (!data) {
+		DEBUG(0,(&quot;malloc() failed\n&quot;));
+		return -1;
+	}
+
+	/* init out private data */
+	data-&gt;some_string = strdup(&quot;test&quot;);
+	if (!data-&gt;some_string) {
+		DEBUG(0,(&quot;strdup() failed\n&quot;));
+		return -1;
+	}
+
+	data-&gt;db_connection = open_db_conn();
+
+	/* and now store the private data pointer in handle-&gt;data
+	 * we need to specify a free_function because we used malloc() and strdup().
+	 * (return -1 if something failed.)
+	 */
+	SMB_VFS_HANDLE_SET_DATA(handle, data, free_example_privates, struct example_privates, return -1);
+
+	return SMB_VFS_NEXT_CONNECT(handle,conn,service,user);
+}
+
+static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd)
+{
+	struct example_privates *data = NULL;
+	
+	/* get the pointer to our private data
+	 * return -1 if something failed
+	 */
+	SMB_VFS_HANDLE_GET_DATA(handle, data, struct example_privates, return -1);
+	
+	/* do something here...*/
+	DEBUG(0,(&quot;some_string: %s\n&quot;,data-&gt;some_string));
+	
+	return SMB_VFS_NEXT_CLOSE(handle, fsp, fd);
+}
+</programlisting>
+</para></listitem>
+
+<listitem><para>
+To make it easy to build 3rd party modules it would be usefull to provide
+configure.in, (configure), install.sh and Makefile.in with the module.
+(Take a look at the example in <filename>examples/VFS</filename>.)
+</para>
+
+<para>
+The configure script accepts <option>--with-samba-source</option> to specify 
+the path to the samba source tree.
+It also accept <option>--enable-developer</option> which lets the compiler 
+give you more warnings.  
+</para>
+
+<para>
+The idea is that you can extend this 
+<filename>configure.in</filename> and <filename>Makefile.in</filename> scripts
+for your module.
+</para></listitem>
+
+<listitem><para>
+Compiling &amp; Testing...
+<simplelist>
+<member><userinput>./configure <option>--enable-developer</option></userinput> ...</member>
+<member><userinput>make</userinput></member>
+<member>Try to fix all compiler warnings</member>
+<member><userinput>make</userinput></member>
+<member>Testing, Testing, Testing ...</member>
+</simplelist>
+</para></listitem>
+</orderedlist>
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Some Notes</title>
+
+<sect2>
+<title>Implement TRANSPARENT functions</title>
+
+<para>
+Avoid writing functions like this:
+
+<programlisting>
+static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd)
+{
+	return SMB_VFS_NEXT_CLOSE(handle, fsp, fd);
+}
+</programlisting>
+
+Overload only the functions you really need to!
+</para>
+
+</sect2>
+
+<sect2>
+<title>Implement OPAQUE functions</title>
+
+<para>
+If you want to just implement a better version of a 
+default samba opaque function
+(e.g. like a disk_free() function for a special filesystem) 
+it's ok to just overload that specific function.
+</para>
+
+<para>
+If you want to implement a database filesystem or
+something different from a posix filesystem.
+Make sure that you overload every vfs operation!!!
+</para>
+<para>
+Functions your FS does not support should be overloaded by something like this:
+e.g. for a readonly filesystem.
+</para>
+
+<programlisting>
+static int example_rename(vfs_handle_struct *handle, connection_struct *conn,
+			char *oldname, char *newname)
+{
+	DEBUG(10,(&quot;function rename() not allowed on vfs 'example'\n&quot;));
+	errno = ENOSYS;
+	return -1;
+}
+</programlisting>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-Developers-Guide/wins.xml b/docs-xml/Samba3-Developers-Guide/wins.xml
new file mode 100644
index 00000000000..df29627bfdf
--- /dev/null
+++ b/docs-xml/Samba3-Developers-Guide/wins.xml
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="wins">
+<chapterinfo>
+	<author>
+		<firstname>Gerald</firstname><surname>Carter</surname>
+	</author>
+	<pubdate>October 2002</pubdate>
+</chapterinfo>
+
+
+<title>Samba WINS Internals</title>
+
+
+<sect1>
+<title>WINS Failover</title>
+
+
+<para>
+The current Samba codebase possesses the capability to use groups of WINS
+servers that share a common namespace for NetBIOS name registration and 
+resolution.  The formal parameter syntax is
+</para>
+
+<para><programlisting>
+	WINS_SERVER_PARAM 	= SERVER [ SEPARATOR SERVER_LIST ]
+	WINS_SERVER_PARAM 	= &quot;wins server&quot;
+	SERVER 			= ADDR[:TAG]
+	ADDR 			= ip_addr | fqdn
+	TAG 			= string
+	SEPARATOR		= comma | \s+
+	SERVER_LIST		= SERVER [ SEPARATOR SERVER_LIST ]
+</programlisting></para>
+
+<para>
+A simple example of a valid wins server setting is
+</para>
+
+<para><programlisting>
+[global]
+	wins server = 192.168.1.2 192.168.1.3
+</programlisting></para>
+
+<para>
+In the event that no TAG is defined in for a SERVER in the list, smbd assigns a default
+TAG of &quot;*&quot;.  A TAG is used to group servers of a shared NetBIOS namespace together.  Upon
+startup, nmbd will attempt to register the netbios name value with one server in each
+tagged group.
+</para>
+
+<para>
+An example using tags to group WINS servers together is show here.  Note that the use of
+interface names in the tags is only by convention and is not a technical requirement.
+</para>
+
+
+<para><programlisting>
+[global]
+	wins server = 192.168.1.2:eth0 192.168.1.3:eth0 192.168.2.2:eth1
+</programlisting></para>
+
+<para>
+Using this configuration, nmbd would attempt to register the server's NetBIOS name 
+with one WINS server in each group.  Because the &quot;eth0&quot; group has two servers, the 
+second server would only be used when a registration (or resolution) request to 
+the first server in that group timed out.
+</para>
+
+<para>
+NetBIOS name resolution follows a similar pattern as name registration.  When resolving 
+a NetBIOS name via WINS, smbd and other Samba programs will attempt to query a single WINS 
+server in a tagged group until either a positive response is obtained at least once or 
+until a server from every tagged group has responded negatively to the name query request.
+If a timeout occurs when querying a specific WINS server, that server is marked as down to 
+prevent further timeouts and the next server in the WINS group is contacted.  Once marked as 
+dead, Samba will not attempt to contact that server for name registration/resolution queries 
+for a period of 10 minutes.
+</para>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml b/docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml
new file mode 100644
index 00000000000..48f439deadc
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml
@@ -0,0 +1,1710 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<chapter id="AccessControls">
+<chapterinfo>
+	&author.jht;
+	&author.jeremy;
+	<author>&person.jelmer;<contrib>drawing</contrib></author>
+	<pubdate>May 10, 2003</pubdate>
+</chapterinfo>
+<title>File, Directory, and Share Access Controls</title>
+
+<para>
+<indexterm><primary>ACLs</primary></indexterm>
+<indexterm><primary>share</primary></indexterm>
+<indexterm><primary>network access controls</primary></indexterm>
+<indexterm><primary>unauthorized access</primary></indexterm>
+Advanced MS Windows users are frequently perplexed when file, directory, and share manipulation of
+resources shared via Samba do not behave in the manner they might expect. MS Windows network
+administrators are often confused regarding network access controls and how to
+provide users with the access they need while protecting resources from unauthorized access.
+</para>
+
+<para>
+<indexterm><primary>file access permissions</primary></indexterm>
+<indexterm><primary>directory access permissions</primary></indexterm>
+Many UNIX administrators are unfamiliar with the MS Windows environment and in particular
+have difficulty in visualizing what the MS Windows user wishes to achieve in attempts to set file
+and directory access permissions. 
+</para>
+
+<para>
+<indexterm><primary>bridge</primary></indexterm>
+<indexterm><primary>directory controls</primary></indexterm>
+<indexterm><primary>directory permissions</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+The problem lies in the differences in how file and directory permissions and controls work
+between the two environments. This difference is one that Samba cannot completely hide, even
+though it does try to bridge the chasm to a degree.
+</para>
+
+<para>
+<indexterm><primary>Extended Attributes</primary></indexterm>
+<indexterm><primary>ACLs</primary><secondary>POSIX</secondary></indexterm>
+<indexterm><primary>Access Control List</primary></indexterm>
+<indexterm><primary>commercial Linux products</primary></indexterm>
+POSIX Access Control List technology has been available (along with extended attributes)
+for UNIX for many years, yet there is little evidence today of any significant use. This
+explains to some extent the slow adoption of ACLs into commercial Linux products. MS Windows
+administrators are astounded at this, given that ACLs were a foundational capability of the now
+decade-old MS Windows NT operating system.
+</para>
+
+<para>
+<indexterm><primary>network administrator</primary></indexterm>
+The purpose of this chapter is to present each of the points of control that are possible with
+Samba-3 in the hope that this will help the network administrator to find the optimum method
+for delivering the best environment for MS Windows desktop users.
+</para>
+
+<para>
+<indexterm><primary>interoperability</primary></indexterm>
+<indexterm><primary>data interchange</primary></indexterm>
+This is an opportune point to mention that Samba was created to provide a means of interoperability
+and interchange of data between differing operating environments. Samba has no intent to change
+UNIX/Linux into a platform like MS Windows. Instead the purpose was and is to provide a sufficient
+level of exchange of data between the two environments. What is available today extends well
+beyond early plans and expectations, yet the gap continues to shrink.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+	<para>
+	Samba offers much flexibility in file system access management. These are the key access control
+	facilities present in Samba today:
+	</para>
+
+	<itemizedlist>
+	<title>Samba Access Control Facilities</title>
+		<listitem><para>
+		<indexterm><primary>permissions</primary><secondary>UNIX file and directory</secondary></indexterm>
+		<emphasis>UNIX File and Directory Permissions</emphasis>
+		</para>
+
+			<para>
+<indexterm><primary>UNIX file system access controls</primary></indexterm>
+<indexterm><primary>access controls</primary></indexterm>
+<indexterm><primary>permissions and controls</primary></indexterm>
+			Samba honors and implements UNIX file system access controls. Users
+			who access a Samba server will do so as a particular MS Windows user.
+			This information is passed to the Samba server as part of the logon or
+			connection setup process. Samba uses this user identity to validate
+			whether or not the user should be given access to file system resources
+			(files and directories). This chapter provides an overview for those
+			to whom the UNIX permissions and controls are a little strange or unknown.
+			</para>
+		</listitem>
+
+		<listitem><para>
+		<emphasis>Samba Share Definitions</emphasis>
+		</para>
+
+			<para>
+<indexterm><primary>share settings</primary></indexterm>
+			In configuring share settings and controls in the &smb.conf; file,
+			the network administrator can exercise overrides to native file
+			system permissions and behaviors. This can be handy and convenient
+			to effect behavior that is more like what MS Windows NT users expect,
+			but it is seldom the <emphasis>best</emphasis> way to achieve this.
+			The basic options and techniques are described herein.
+			</para>
+		</listitem>
+
+		<listitem><para>
+		<emphasis>Samba Share ACLs</emphasis>
+		<indexterm><primary>ACLs</primary><secondary>share</secondary></indexterm>
+		</para>
+
+			<para>
+<indexterm><primary>ACLs on shares</primary></indexterm>
+			Just as it is possible in MS Windows NT to set ACLs on shares
+			themselves, so it is possible to do in Samba.
+			Few people make use of this facility, yet it remains one of the
+			easiest ways to affect access controls (restrictions) and can often
+			do so with minimum invasiveness compared with other methods.
+			</para>
+		</listitem>
+
+		<listitem><para>
+				<indexterm><primary>ACLs</primary><secondary>POSIX</secondary></indexterm>
+				<indexterm><primary>ACLs</primary><secondary>Windows</secondary></indexterm>
+		<emphasis>MS Windows ACLs through UNIX POSIX ACLs</emphasis>
+		</para>
+
+			<para>
+<indexterm><primary>native ACLs</primary></indexterm>
+			The use of POSIX ACLs on UNIX/Linux is possible only if the underlying
+			operating system supports them. If not, then this option will not be
+			available to you. Current UNIX technology platforms have native support
+			for POSIX ACLs. There are patches for the Linux kernel that also provide
+			this support. Sadly, few Linux platforms ship today with native ACLs and
+			extended attributes enabled. This chapter has pertinent information
+			for users of platforms that support them.
+			</para>
+		</listitem>
+	</itemizedlist>
+
+</sect1>
+
+<sect1>
+<title>File System Access Controls</title>
+
+<para>
+Perhaps the most important recognition to be made is the simple fact that MS Windows NT4/200x/XP
+implement a totally divergent file system technology from what is provided in the UNIX operating system
+environment. First we consider what the most significant differences are, then we look
+at how Samba helps to bridge the differences.
+</para>
+
+	<sect2>
+	<title>MS Windows NTFS Comparison with UNIX File Systems</title>
+
+	<para>
+	<indexterm><primary>NTFS</primary></indexterm>
+	<indexterm><primary>File System</primary></indexterm>
+	<indexterm><primary>File System</primary><secondary>UNIX</secondary></indexterm>
+	<indexterm><primary>File System</primary><secondary>Windows</secondary></indexterm>
+	Samba operates on top of the UNIX file system. This means it is subject to UNIX file system conventions
+	and permissions. It also means that if the MS Windows networking environment requires file system
+	behavior, that differs from UNIX file system behavior then somehow Samba is responsible for emulating
+	that in a transparent and consistent manner.
+	</para>
+
+	<para>
+	It is good news that Samba does this to a large extent, and on top of that, provides a high degree
+	of optional configuration to override the default behavior. We look at some of these overrides,
+	but for the greater part we stay within the bounds of default behavior. Those wishing to explore
+	the depths of control ability should review the &smb.conf; man page.
+	</para>
+
+	<para>The following compares file system features for UNIX with those of MS Windows NT/200x:
+	<indexterm><primary>File System</primary><secondary>feature comparison</secondary></indexterm>
+	
+	</para>
+
+	<variablelist>
+		<varlistentry>
+			<term>Name Space</term>
+			<listitem>
+		<para>
+		MS Windows NT4/200x/XP file names may be up to 254 characters long, and UNIX file names
+		may be 1023 characters long. In MS Windows, file extensions indicate particular file types;
+		in UNIX this is not so rigorously observed because all names are considered arbitrary. 
+		</para>
+		<para>
+		What MS Windows calls a folder, UNIX calls a directory.
+		</para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>Case Sensitivity</term>
+			<listitem>
+		<para>
+		<indexterm><primary>8.3 file names</primary></indexterm>
+		<indexterm><primary>File System</primary><secondary>case sensitivity</secondary></indexterm>
+		MS Windows file names are generally uppercase if made up of 8.3 (8-character file name
+		and 3 character extension. File names that are longer than 8.3 are case preserving and case
+		insensitive.
+		</para>
+
+		<para>
+		UNIX file and directory names are case sensitive and case preserving. Samba implements the
+		MS Windows file name behavior, but it does so as a user application. The UNIX file system
+		provides no mechanism to perform case-insensitive file name lookups. MS Windows does this
+		by default. This means that Samba has to carry the processing overhead to provide features
+		that are not native to the UNIX operating system environment.
+		</para>
+
+		<para>
+		Consider the following. All are unique UNIX names but one single MS Windows file name:
+		<screen>
+				MYFILE.TXT
+				MyFile.txt
+				myfile.txt
+		</screen></para>
+
+		<para>
+		So clearly, in an MS Windows file namespace these three files cannot co-exist, but in UNIX
+		they can.
+		</para>
+
+		<para>
+		So what should Samba do if all three are present? That which is lexically first will be
+		accessible to MS Windows users; the others are invisible and unaccessible &smbmdash; any
+		other solution would be suicidal. The Windows client will ask for a case-insensitive file
+		lookup, and that is the reason for which Samba must offer a consistent selection in the
+		event that the UNIX directory contains multiple files that would match a case insensitive
+		file listing.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Directory Separators</term>
+		<listitem><para>
+		<indexterm><primary>Directory Separators</primary></indexterm>
+		MS Windows and DOS use the backslash <constant>\</constant> as a directory delimiter, and UNIX uses
+		the forward-slash <constant>/</constant> as its directory delimiter. This is handled transparently by Samba.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Drive Identification</term>
+		<listitem><para>
+		<indexterm><primary>Drive Identification</primary></indexterm>
+		MS Windows products support a notion of drive letters, like <command>C:</command>, to represent
+		disk partitions. UNIX has no concept of separate identifiers for file partitions; each
+		such file system is mounted to become part of the overall directory tree.
+		The UNIX directory tree begins at <constant>/</constant> just as the root of a DOS drive is specified as
+		<constant>C:\</constant>.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>File Naming Conventions</term>
+		<listitem><para>
+		<indexterm><primary>File Naming Conventions</primary></indexterm>
+		MS Windows generally never experiences file names that begin with a dot (<constant>.</constant>), while in UNIX these
+		are commonly found in a user's home directory. Files that begin with a dot (<constant>.</constant>) are typically
+		startup files for various UNIX applications, or they may be files that contain
+		startup configuration data.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>Links and Short-Cuts</term>
+		<listitem><para>
+		<indexterm><primary>Links</primary><secondary>hard</secondary></indexterm>
+		<indexterm><primary>Links</primary><secondary>soft</secondary></indexterm>
+		<indexterm><primary>Shortcuts</primary></indexterm>
+		MS Windows make use of <emphasis>links and shortcuts</emphasis> that are actually special types of files that will
+		redirect an attempt to execute the file to the real location of the file. UNIX knows of file and directory
+		links, but they are entirely different from what MS Windows users are used to.
+		</para>
+
+		<para>
+		Symbolic links are files in UNIX that contain the actual location of the data (file or directory). An
+		operation (like read or write) will operate directly on the file referenced. Symbolic links are also
+		referred to as <quote>soft links.</quote> A hard link is something that MS Windows is not familiar with. It allows
+		one physical file to be known simultaneously by more than one file name.
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>
+	There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort
+	in the process of becoming familiar with UNIX/Linux. These are best left for a text that is dedicated to the
+	purpose of UNIX/Linux training and education.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Managing Directories</title>
+
+	<para>
+<indexterm><primary>create</primary></indexterm>
+<indexterm><primary>delete</primary></indexterm>
+<indexterm><primary>rename</primary></indexterm>
+	There are three basic operations for managing directories: <command>create</command>, <command>delete</command>,
+	<command>rename</command>. <link linkend="TOSH-Accesstbl">Managing Directories with UNIX and
+	Windows</link> compares the commands in Windows and UNIX that implement these operations.
+	</para>
+
+	<table frame="all" id="TOSH-Accesstbl">
+		<title>Managing Directories with UNIX and Windows</title>
+		<tgroup align="center" cols="3">
+		<thead>
+		<row><entry>Action</entry><entry>MS Windows Command</entry><entry>UNIX Command</entry></row>
+		</thead>
+	
+		<tbody>
+			<row><entry>create</entry><entry>md folder</entry><entry>mkdir folder</entry></row>
+			<row><entry>delete</entry><entry>rd folder</entry><entry>rmdir folder</entry></row>
+			<row><entry>rename</entry><entry>rename oldname newname</entry><entry>mv oldname newname</entry></row>
+		</tbody>
+	</tgroup>
+	</table>
+
+	</sect2>
+
+	<sect2>
+	<title>File and Directory Access Control</title>
+
+	<para>
+	<indexterm><primary>ACLs</primary><secondary>File System</secondary></indexterm>
+<indexterm><primary>POSIX ACLs</primary></indexterm>
+<indexterm><primary>EAs</primary></indexterm>
+	The network administrator is strongly advised to read basic UNIX training manuals and reference materials
+	regarding file and directory permissions maintenance. Much can be achieved with the basic UNIX permissions
+	without having to resort to more complex facilities like POSIX ACLs or extended attributes (EAs).
+	</para>
+
+	<para>
+	UNIX/Linux file and directory access permissions involves setting three primary sets of data and one control set.
+	A UNIX file listing looks as follows:
+<screen>
+&prompt;<userinput>ls -la</userinput>
+total 632
+drwxr-xr-x   13 maryo   gnomes      816 2003-05-12 22:56 .
+drwxrwxr-x   37 maryo   gnomes     3800 2003-05-12 22:29 ..
+dr-xr-xr-x    2 maryo   gnomes       48 2003-05-12 22:29 muchado02
+drwxrwxrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado03
+drw-rw-rw-    2 maryo   gnomes       48 2003-05-12 22:29 muchado04
+d-w--w--w-    2 maryo   gnomes       48 2003-05-12 22:29 muchado05
+dr--r--r--    2 maryo   gnomes       48 2003-05-12 22:29 muchado06
+drwsrwsrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado08
+----------    1 maryo   gnomes     1242 2003-05-12 22:31 mydata00.lst
+--w--w--w-    1 maryo   gnomes     7754 2003-05-12 22:33 mydata02.lst
+-r--r--r--    1 maryo   gnomes    21017 2003-05-12 22:32 mydata04.lst
+-rw-rw-rw-    1 maryo   gnomes    41105 2003-05-12 22:32 mydata06.lst
+&prompt;
+</screen>
+	</para>
+
+	<para>
+	The columns represent (from left to right) permissions, number of hard links to file, owner, group, size
+	(bytes), access date, time of last modification, and file name.
+	</para>
+
+	<para>
+	An overview of the permissions field is shown in <link linkend="access1">Overview of UNIX permissions
+	field</link>.
+	</para>
+
+	<figure id="access1">
+		<title>Overview of UNIX permissions field.</title>
+		<imagefile scale="40">access1</imagefile>
+	</figure>
+
+	<para>
+		Any bit flag may be unset. An unset bit flag is the equivalent of "cannot" and is represented
+		as a <quote>-</quote> character (see <link linkend="access2"/>)
+<indexterm><primary>read</primary></indexterm>
+<indexterm><primary>write</primary></indexterm>
+<indexterm><primary>execute</primary></indexterm>
+<indexterm><primary>user</primary></indexterm>
+<indexterm><primary>group</primary></indexterm>
+<indexterm><primary>other</primary></indexterm>
+	</para>
+
+<example id="access2">
+<title>Example File</title>
+<programlisting>
+-rwxr-x---   Means: 
+ ^^^                The owner (user) can read, write, execute
+    ^^^             the group can read and execute
+       ^^^          everyone else cannot do anything with it.
+</programlisting>
+</example>
+
+
+	<para>
+<indexterm><primary>character device</primary></indexterm>
+<indexterm><primary>block device</primary></indexterm>
+<indexterm><primary>pipe device</primary></indexterm>
+<indexterm><primary>UNIX Domain Socket</primary></indexterm>
+	Additional possibilities in the [type] field are c = character device, b = block device, p = pipe device,
+	s = UNIX Domain Socket.
+	</para>
+
+	<para>
+<indexterm><primary>read</primary></indexterm>
+<indexterm><primary>write</primary></indexterm>
+<indexterm><primary>execute</primary></indexterm>
+<indexterm><primary>SGID</primary></indexterm>
+<indexterm><primary>SUID</primary></indexterm>
+	The letters <constant>rwxXst</constant> set permissions for the user, group, and others as read (r), write (w),
+	execute (or access for directories) (x), execute  only  if  the  file  is a directory or already has execute
+	permission for some user (X), set user (SUID) or group ID (SGID) on execution (s), sticky (t).
+	</para>
+
+	<para>
+<indexterm><primary>sticky bit</primary></indexterm>
+<indexterm><primary>unlinked</primary></indexterm>
+<indexterm><primary>/tmp</primary></indexterm>
+<indexterm><primary>world-writable</primary></indexterm>
+	When the sticky bit is set on a directory, files in that directory may be unlinked (deleted) or renamed only by root or their owner. 
+	Without the sticky  bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on
+	directories, such as <filename>/tmp</filename>, that are world-writable.
+	</para>
+
+	<para>
+<indexterm><primary>write</primary></indexterm>
+<indexterm><primary>read</primary></indexterm>
+<indexterm><primary>setting up directories</primary></indexterm>
+<indexterm><primary>set user id</primary><see>SUID</see></indexterm>
+<indexterm><primary>set group id</primary><see>SGID</see></indexterm>
+	When the set user or group ID bit (s) is set on a directory, then all files created within it will be owned by the user and/or
+	group whose `set user or group' bit is set. This can be helpful in setting up directories for which it is desired that
+	all users who are in a group should be able to write to and read from a file, particularly when it is undesirable for that file
+	to be exclusively owned by a user whose primary group is not the group that all such users belong to.
+	</para>
+
+	<para>
+	When a directory is set <constant>d-wx--x---</constant>, the owner can read and create (write) files in it, but because
+	the (r) read flags are not set, files cannot be listed (seen) in the directory by anyone. The group can read files in the
+	directory but cannot create new files. If files in the directory are set to be readable and writable for the group, then
+	group members will be able to write to (or delete) them.
+	</para>
+
+	<sect3>
+	<title>Protecting Directories and Files from Deletion</title>
+
+	<para>
+<indexterm><primary>protect files</primary></indexterm>
+<indexterm><primary>protect directories</primary></indexterm>
+<indexterm><primary>access controls</primary></indexterm>
+<indexterm><primary>capability to delete</primary></indexterm>
+	People have asked on the Samba mailing list how is it possible to protect files or directories from deletion by users.
+	For example, Windows NT/2K/XP provides the capacity to set access controls on a directory into which people can
+	write files but not delete them. It is possible to set an ACL on a Windows file that permits the file to be written to
+	but not deleted. Such concepts are foreign to the UNIX operating system file space. Within the UNIX file system
+	anyone who has the ability to create a file can write to it. Anyone who has write permission on the
+	directory that contains a file and has write permission for it has the capability to delete it.
+	</para>
+
+	<para>
+<indexterm><primary>directory permissions</primary></indexterm>
+<indexterm><primary>delete a file</primary></indexterm>
+<indexterm><primary>write access</primary></indexterm>
+	For the record, in the UNIX environment the ability to delete a file is controlled by the permissions on
+	the directory that the file is in. In other words, a user can delete a file in a directory to which that
+	user has write access, even if that user does not own the file.
+	</para>
+	
+	<para>
+<indexterm><primary>file system capabilities</primary></indexterm>
+<indexterm><primary>inheritance</primary></indexterm>
+<indexterm><primary>POSIX ACLs</primary></indexterm>
+<indexterm><primary>extended attributes</primary></indexterm>
+	Of necessity, Samba is subject to the file system semantics of the host operating system. Samba is therefore
+	limited in the file system capabilities that can be made available through Windows ACLs, and therefore performs
+	a "best fit" translation to POSIX ACLs. Some UNIX file systems do, however support, a feature known
+	as extended attributes. Only the Windows concept of <emphasis>inheritance</emphasis> is implemented by Samba through
+	the appropriate extended attribute.
+	</para>	
+
+	<para>
+<indexterm><primary>extended attributes</primary></indexterm>
+<indexterm><primary>immutible</primary></indexterm>
+<indexterm><primary>chattr</primary></indexterm>
+<indexterm><primary>CAP_LINUX_IMMUTABLE</primary></indexterm>
+	The specific semantics of the extended attributes are not consistent across UNIX and UNIX-like systems such as Linux.
+	For example, it is possible on some implementations of the extended attributes to set a flag that prevents the directory
+	or file from being deleted. The extended attribute that may achieve this is called the <constant>immutible</constant> bit.
+	Unfortunately, the implementation of the immutible flag is NOT consistent with published documentation. For example, the
+	man page for the <command>chattr</command> on SUSE Linux 9.2 says:
+<screen>
+A file with the i attribute cannot be modified: it cannot be deleted
+or renamed, no link can be created to this file and no data can be
+written to the file. Only the superuser or a process possessing the
+CAP_LINUX_IMMUTABLE capability can set or clear this attribute.
+</screen>
+	A simple test can be done to check if the immutible flag is supported on files in the file system of the Samba host
+	server.
+	</para>
+
+	<procedure>
+	<title>Test for File Immutibility Support</title>
+
+	<step><para>
+	Create a file called <filename>filename</filename>.
+	</para></step>
+
+	<step><para>
+	Login as the <constant>root</constant> user, then set the immutibile flag on a test file as follows:
+<screen>
+&rootprompt; chattr +i `filename'
+</screen>
+	</para></step>
+
+	<step><para>
+	Login as the user who owns the file (not root) and attempt to remove the file as follows:
+<screen>
+mystic:/home/hannibal > rm filename
+</screen>
+	It will not be possible to delete the file if the immutible flag is correctly honored.
+	</para></step>
+	</procedure>
+
+	<para>
+	On operating systems and file system types that support the immutible bit, it is possible to create directories
+	that cannot be deleted. Check the man page on your particular host system to determine whether or not
+	immutable directories are writable. If they are not, then the entire directory and its contents will effectively
+	be protected from writing (file creation also) and deletion.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Share Definition Access Controls</title>
+
+
+	<para>
+	<indexterm><primary>permissions</primary><secondary>share</secondary></indexterm>
+	The following parameters in the &smb.conf; file sections define a share control or affect access controls.
+	Before using any of the following options, please refer to the man page for &smb.conf;.
+	</para>
+
+	<sect2>
+	<title>User- and Group-Based Controls</title>
+
+	<para>
+	User- and group-based controls can prove quite useful. In some situations it is distinctly desirable to
+	force all file system operations as if a single user were doing so. The use of the
+	<smbconfoption name="force user"/> and <smbconfoption name="force group"/> behavior will achieve this.
+	In other situations it may be necessary to use a paranoia level of control to ensure that only particular
+	authorized persons will be able to access a share or its contents. Here the use of the
+	<smbconfoption name="valid users"/> or the <smbconfoption name="invalid users"/> parameter may be useful.
+	</para>
+
+	<para>
+	As always, it is highly advisable to use the easiest to maintain and the least ambiguous method for
+	controlling access. Remember, when you leave the scene, someone else will need to provide assistance, and
+	if he or she finds too great a mess or does not understand what you have done, there is risk of
+	Samba being removed and an alternative solution being adopted.
+	</para>
+
+	<para>
+	<link linkend="ugbc">User and Group Based Controls</link> enumerates these controls.
+	</para>
+
+	<table frame='all' pgwide='0' id="ugbc"><title>User- and Group-Based Controls</title>
+	<tgroup cols='2'>
+		<colspec align="left"/>
+		<colspec align="justify" colwidth="1*"/>
+		<thead>
+		<row>
+			<entry align="center">Control Parameter</entry>
+			<entry align="center">Description, Action, Notes</entry>
+		</row>
+		</thead>
+		<tbody>
+		<row>
+			<entry><smbconfoption name="admin users"/></entry>
+			<entry><para>
+			List of users who will be granted administrative privileges on the share.
+			They will do all file operations as the superuser (root). 
+			Users in this list will be able to do anything they like on the share,
+			irrespective of file permissions.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="force group"/></entry>
+			<entry><para>
+			Specifies a UNIX group name that will be assigned as the default primary group
+			for all users connecting to this service.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="force user"/></entry>
+			<entry><para>
+			Specifies a UNIX username that will be assigned as the default user for all users connecting to this service.
+			This is useful for sharing files. Incorrect use can cause security problems.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="guest ok"/></entry>
+			<entry><para>
+			If this parameter is set for a service, then no password is required to connect to the service. Privileges will be 
+			those of the  guest account.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="invalid users"/></entry>
+			<entry><para>
+			List of users that should not be allowed to login to this service.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="only user"/></entry>
+			<entry><para>
+			Controls whether connections with usernames not in the user list will be allowed.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="read list"/></entry>
+			<entry><para>
+			List of users that are given read-only access to a service. Users in this list
+			will not be given write access, no matter what the  read-only  option is set to. 
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="username"/></entry>
+			<entry><para>
+			Refer to the &smb.conf; man page for more information; this is a complex and potentially misused parameter.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="valid users"/></entry>
+			<entry><para>
+			List of users that should be allowed to login to this service.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="write list"/></entry>
+			<entry><para>
+			List of users that are given read-write access to a service.
+			</para></entry>
+		</row>
+		</tbody>
+	</tgroup>
+	</table>
+
+	</sect2>
+
+	<sect2>
+	<title>File and Directory Permissions-Based Controls</title>
+
+	<para>
+	Directory permission-based controls, if misused, can result in considerable difficulty in diagnosing the causes of 
+	misconfiguration. Use them sparingly and carefully. By gradually introducing each, one at a time, undesirable side 
+	effects may be detected. In the event of a problem, always comment all of them out and then gradually reintroduce 
+	them in a controlled way.
+	</para>
+
+	<para>
+	Refer to <link linkend="fdpbc">File and Directory Permission Based Controls</link> for information 
+	regarding the parameters that may be used to set file and directory permission-based access controls.
+	</para>
+
+	<table frame='all' id="fdpbc"><title>File and Directory Permission-Based Controls</title>
+		<tgroup cols='2'>
+			<colspec align="left"/>
+			<colspec align="justify" colwidth="1*"/>
+		<thead>
+		<row>
+			<entry align="center">Control Parameter</entry>
+			<entry align="center">Description, Action, Notes</entry>
+		</row>
+		</thead>
+		<tbody>
+		<row>
+			<entry><smbconfoption name="create mask"/></entry>
+			<entry><para>
+			Refer to the &smb.conf; man page.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="directory mask"/></entry>
+			<entry><para>
+			The octal modes used when converting DOS modes to UNIX modes when creating UNIX directories.
+			See also directory security mask.
+			</para></entry></row>
+		<row>
+			<entry><smbconfoption name="dos filemode"/></entry>
+			<entry><para>
+			Enabling this parameter allows a user who has write access to the file to modify the permissions on it.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="force create mode"/></entry>
+			<entry><para>
+			This parameter specifies a set of UNIX-mode bit permissions that will always be set on a file created by Samba.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="force directory mode"/></entry>
+			<entry><para>
+			This parameter specifies a set of UNIX-mode bit permissions that will always be set on a directory created by Samba.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="force directory security mode"/></entry>
+			<entry><para>
+			Controls UNIX permission bits modified when a Windows NT client is manipulating UNIX permissions on a directory.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="force security mode"/></entry>
+			<entry><para>
+			Controls UNIX permission bits modified when a Windows NT client manipulates UNIX permissions.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="hide unreadable"/></entry>
+			<entry><para>
+			Prevents clients from seeing the existence of files that cannot be read.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="hide unwriteable files"/></entry>
+			<entry><para>
+			Prevents clients from seeing the existence of files that cannot be written to. Unwritable directories are shown as usual. 
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="nt acl support"/></entry>
+			<entry><para>
+			This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT ACLs.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="security mask"/></entry>
+			<entry><para>
+			Controls UNIX permission bits modified when a Windows NT client is manipulating the UNIX permissions on a file.
+			</para></entry>
+		</row>
+		</tbody>
+	</tgroup>
+	</table>
+
+	</sect2>
+
+	<sect2>
+	<title>Miscellaneous Controls</title>
+
+	<para>
+	The parameter documented in <link linkend="mcoc">Other Controls</link> are often used by administrators 
+	in ways that create inadvertent barriers to file access. Such are the consequences of not understanding the 
+	full implications of &smb.conf; file settings.
+	</para>
+
+	<table frame='all' id="mcoc"><title>Other Controls</title>
+	<tgroup cols='2'>
+		<colspec align="justify" colwidth="1*"/>
+		<colspec align="justify" colwidth="1*"/>
+		<thead>
+		<row>
+			<entry align="center">Control Parameter</entry>
+			<entry align="center">Description, Action, Notes</entry>
+		</row>
+		</thead>
+		<tbody>
+		<row>
+			<entry>
+			<smbconfoption name="case sensitive"/>,
+			<smbconfoption name="default case"/>,
+			<smbconfoption name="short preserve case"/>
+			</entry>
+			<entry><para>
+			This means that all file name lookup will be done in a case-sensitive manner. 
+			Files will be created with the precise file name Samba received from the MS Windows client.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="csc policy"/></entry>
+			<entry><para>
+			Client-side caching policy parallels MS Windows client-side file caching capabilities.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="dont descend"/></entry>
+			<entry><para>
+			Allows specifying a comma-delimited list of directories that the server should always show as empty.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="dos filetime resolution"/></entry>
+			<entry><para>
+			This option is mainly used as a compatibility option for Visual C++ when used against Samba shares.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="dos filetimes"/></entry>
+			<entry><para>
+			DOS and Windows allow users to change file timestamps if they can write to the file. POSIX semantics prevent this.
+			This option allows DOS and Windows behavior.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="fake oplocks"/></entry>
+			<entry><para>
+			Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an
+			oplock, the client is free to assume that it is the only one accessing the file, and it will aggressively cache file data.
+			</para></entry>
+		</row>
+		<row>
+			<entry>
+			<smbconfoption name="hide dot files"/>,
+			<smbconfoption name="hide files"/>,
+			<smbconfoption name="veto files"/>
+			</entry>
+			<entry><para>
+			Note: MS Windows Explorer allows override of files marked as hidden so they will still be visible.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="read only"/></entry>
+			<entry><para>
+			If this parameter is yes, then users of a service may not create or modify files in the service's directory.
+			</para></entry>
+		</row>
+		<row>
+			<entry><smbconfoption name="veto files"/></entry>
+			<entry><para>
+			List of files and directories that are neither visible nor accessible.
+			</para></entry>
+		</row>
+		</tbody>
+	</tgroup>
+	</table>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Access Controls on Shares</title>
+
+
+	<para>
+<indexterm><primary>per-share access control</primary></indexterm>
+<indexterm><primary>Everyone - Full Control</primary></indexterm>
+<indexterm><primary>specific restrictions</primary></indexterm>
+<indexterm><primary>share access</primary></indexterm>
+	<indexterm><primary>permissions</primary><secondary>share ACLs</secondary></indexterm>
+	This section deals with how to configure Samba per-share access control restrictions.
+	By default, Samba sets no restrictions on the share itself. Restrictions on the share itself
+	can be set on MS Windows NT4/200x/XP shares. This can be an effective way to limit who can
+	connect to a share. In the absence of specific restrictions, the default setting is to allow
+	the global user <constant>Everyone - Full Control</constant> (full control, change and read).
+	</para>
+
+	<para>
+<indexterm><primary>access control</primary></indexterm>
+<indexterm><primary>MMC</primary></indexterm>
+<indexterm><primary>Computer Management</primary></indexterm>
+	At this time Samba does not provide a tool for configuring access control settings on the share
+	itself the only way to create those settings is to use either the NT4 Server Manager or the Windows 200x
+	Microsoft Management Console (MMC) for Computer Management. There are currently no plans to provide
+	this capability in the Samba command-line tool set.
+	</para>
+
+	<para>
+<indexterm><primary>share_info.tdb</primary></indexterm>
+<indexterm><primary>/usr/local/samba/var</primary></indexterm>
+<indexterm><primary>tdbdump</primary></indexterm>
+<indexterm><primary>tdb files</primary></indexterm>
+	Samba stores the per-share access control settings in a file called <filename>share_info.tdb</filename>.
+	The location of this file on your system will depend on how Samba was compiled. The default location
+	for Samba's tdb files is under <filename>/usr/local/samba/var</filename>. If the <filename>tdbdump</filename>
+	utility has been compiled and installed on your system, then you can examine the contents of this file
+	by executing <command>tdbdump share_info.tdb</command> in the directory containing the tdb files.
+	</para>
+
+	<sect2>
+	<title>Share Permissions Management</title>
+
+		<para>
+		The best tool for share permissions management is platform-dependent. Choose the best tool for your environment.
+		</para>
+
+			<sect3>
+			<title>Windows NT4 Workstation/Server</title>
+			<para>
+<indexterm><primary>manage share permissions</primary></indexterm>
+<indexterm><primary>share permissions</primary></indexterm>
+<indexterm><primary>NT Server Manager</primary></indexterm>
+<indexterm><primary>Windows NT4</primary></indexterm>
+			The tool you need to manage share permissions on a Samba server from a Windows NT4 Workstation or Server
+			is the NT Server Manager.  Server Manager is shipped with Windows NT4 Server products but not with Windows
+			NT4 Workstation.  You can obtain the NT Server Manager for MS Windows NT4 Workstation from the Microsoft
+			web site <ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673">support</ulink> section.
+			</para>
+
+			<procedure>
+			<title>Instructions</title>
+
+			<step><para>
+			Launch the <application>NT4 Server Manager</application> and click on the Samba server you want to
+			administer. From the menu select <guimenu>Computer</guimenu>, then click on
+			<guimenuitem>Shared Directories</guimenuitem>.
+			</para></step>
+
+			<step><para>
+			Click on the share that you wish to manage and click the <guilabel>Properties</guilabel> tab, then click
+			the <guilabel>Permissions</guilabel> tab. Now you can add or change access control settings as you wish.
+			</para></step>
+			</procedure>
+
+			</sect3>
+
+			<sect3>
+			<title>Windows 200x/XP</title>
+
+			<para>
+<indexterm><primary>Windows NT4/200x/XP</primary></indexterm>
+<indexterm><primary>ACLs on share</primary></indexterm>
+<indexterm><primary>Sharing</primary></indexterm>
+<indexterm><primary>Permissions</primary></indexterm>
+			On <application>MS Windows NT4/200x/XP</application> system, ACLs on the share itself are set using native
+			tools, usually from File Manager. For example, in Windows 200x, right-click on the shared folder,
+			then select <guimenuitem>Sharing</guimenuitem>, then click on <guilabel>Permissions</guilabel>. The default 
+			Windows NT4/200x permission allows "Everyone" full control on the share.
+			</para>
+
+			<para>
+<indexterm><primary>Computer Management</primary></indexterm>
+<indexterm><primary>MMC</primary></indexterm>
+<indexterm><primary>tool</primary></indexterm>
+			MS Windows 200x and later versions come with a tool called the <application>Computer Management</application>
+			snap-in for the MMC. This tool is located by clicking on <guimenu>Control Panel ->
+			Administrative Tools -> Computer Management</guimenu>.
+			</para>
+
+			<procedure>
+			<title>Instructions</title>
+			<step><para>
+			After launching the MMC with the Computer Management snap-in, click the menu item <guimenuitem>Action</guimenuitem>
+			and select <guilabel>Connect to another computer</guilabel>. If you are not logged onto a domain you will be prompted
+			to enter a domain login user identifier and a password. This will authenticate you to the domain.
+			If you are already logged in with administrative privilege, this step is not offered.
+			</para></step>
+
+			<step><para>
+			If the Samba server is not shown in the <guilabel>Select Computer</guilabel> box, type in the name of the target
+			Samba server in the field <guilabel>Name:</guilabel>. Now click the on <guibutton>[+]</guibutton> next to 
+			<guilabel>System Tools</guilabel>, then on the <guibutton>[+]</guibutton> next to
+			<guilabel>Shared Folders</guilabel> in the left panel.
+			</para></step>
+
+			<step><para>
+<indexterm><primary>Share Permissions</primary></indexterm>
+			In the right panel, double-click on the share on which you wish to set access control permissions.
+			Then click the tab <guilabel>Share Permissions</guilabel>. It is now possible to add access control entities
+			to the shared folder. Remember to set what type of access (full control, change, read) you
+			wish to assign for each entry.
+			</para></step>
+			</procedure>
+
+			<warning>
+			<para>
+			Be careful. If you take away all permissions from the <constant>Everyone</constant> user without removing
+			this user, effectively no user will be able to access the share. This is a result of what is known as
+			ACL precedence. Everyone with <emphasis>no access</emphasis> means that <constant>MaryK</constant> who is
+			part of the group <constant>Everyone</constant> will have no access even if she is given explicit full
+			control access.
+			</para>
+			</warning>
+
+			</sect3>
+		</sect2>
+
+</sect1>
+
+<sect1>
+<title>MS Windows Access Control Lists and UNIX Interoperability</title>
+
+	<sect2>
+		<title>Managing UNIX Permissions Using NT Security Dialogs</title>
+
+
+		<para>
+		<indexterm><primary>permissions</primary><secondary>file/directory ACLs</secondary></indexterm>
+		Windows NT clients can use their native security settings dialog box to view and modify the
+		underlying UNIX permissions.
+		</para>
+
+		<para>
+		This ability is careful not to compromise the security of the UNIX host on which Samba is running and 
+		still obeys all the file permission rules that a Samba administrator can set.
+		</para>
+
+		<para>
+		Samba does not attempt to go beyond POSIX ACLs, so the various finer-grained access control
+		options provided in Windows are actually ignored.
+		</para> 
+
+		<note>
+		<para>
+		All access to UNIX/Linux system files via Samba is controlled by the operating system file access controls.
+		When trying to figure out file access problems, it is vitally important to find the identity of the Windows
+		user as it is presented by Samba at the point of file access. This can best be determined from the
+		Samba log files.
+		</para>
+		</note>
+	</sect2>
+
+	<sect2>
+		<title>Viewing File Security on a Samba Share</title>
+
+		<para>
+		From an NT4/2000/XP client, right-click on any file or directory in a Samba-mounted drive letter
+		or UNC path. When the menu pops up, click on the <guilabel>Properties</guilabel> entry at the bottom
+		of the menu. This brings up the file <constant>Properties</constant> dialog box. Click on the 
+		<guilabel>Security</guilabel> tab and you will see three buttons: <guibutton>Permissions</guibutton>,
+		<guibutton>Auditing</guibutton>, and <guibutton>Ownership</guibutton>. The <guibutton>Auditing</guibutton>
+		button will cause either an error message <errorname>"A requested privilege is not held by the client"</errorname>
+		to appear if the user is not the NT administrator, or a dialog intended to allow an administrator
+		to add auditing requirements to a file if the user is logged on as the NT administrator. This dialog is
+		nonfunctional with a Samba share at this time, because the only useful button, the <guibutton>Add</guibutton>
+		button, will not currently allow a list of users to be seen.
+		</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Viewing File Ownership</title>
+
+		<para>
+		Clicking on the <guibutton>Ownership</guibutton> button brings up a dialog box telling you who owns
+		the given file. The owner name will be displayed like this:
+		<screen>
+		<constant>SERVER\user (Long name)</constant>
+		</screen>
+		<replaceable>SERVER</replaceable> is the NetBIOS name of the Samba server, <replaceable>user</replaceable>
+		is the username of the UNIX user who owns the file, and <replaceable>(Long name)</replaceable> is the
+		descriptive string identifying the user (normally found in the GECOS field of the UNIX password database).
+		Click on the <guibutton>Close</guibutton> button to remove this dialog.
+		</para>
+
+		<para>
+		If the parameter <smbconfoption name="nt acl support"/> is set to <constant>false</constant>,
+		the file owner will be shown as the NT user <emphasis>Everyone</emphasis>.
+		</para>
+
+		<para>
+<indexterm><primary>Take Ownership</primary></indexterm>
+		The <guibutton>Take Ownership</guibutton> button will not allow you to change the ownership of this file to
+		yourself (clicking it will display a dialog box complaining that the user as whom you are currently logged onto
+		the NT client cannot be found). The reason for this is that changing the ownership of a file is a privileged
+		operation in UNIX, available only to the <emphasis>root</emphasis> user. Because clicking on this button causes
+		NT to attempt to change the ownership of a file to the current user logged into the NT client, this will
+		not work with Samba at this time.
+		</para>
+
+		<para>
+<indexterm><primary>chown</primary></indexterm>
+<indexterm><primary>ownership</primary></indexterm>
+<indexterm><primary>Seclib</primary></indexterm>
+		There is an NT <command>chown</command> command that will work with Samba and allow a user with administrator
+		privilege connected to a Samba server as root to change the ownership of files on both a local NTFS file system
+		or remote mounted NTFS or Samba drive. This is available as part of the <application>Seclib</application> NT
+		security library written by Jeremy Allison of the Samba Team and is downloadable from the main Samba FTP site.
+		</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Viewing File or Directory Permissions</title>
+
+		<para>
+		The third button is the <guibutton>Permissions</guibutton> button. Clicking on it brings up a dialog box
+		that shows both the permissions and the UNIX owner of the file or directory. The owner is displayed like this:
+		</para>
+
+		<para><command><replaceable>SERVER</replaceable>\
+				<replaceable>user</replaceable> 
+				<replaceable>(Long name)</replaceable></command></para>
+
+		<para><replaceable>SERVER</replaceable> is the NetBIOS name of the Samba server,
+		<replaceable>user</replaceable> is the username of the UNIX user who owns the file, and
+		<replaceable>(Long name)</replaceable> is the descriptive string identifying the user (normally found in the
+		GECOS field of the UNIX password database).</para>
+
+		<para>
+		If the parameter <smbconfoption name="nt acl support"/> is set to <constant>false</constant>,
+		the file owner will be shown as the NT user <constant>Everyone</constant>, and the permissions will be
+		shown as NT <emphasis>Full Control</emphasis>.
+		</para>
+
+
+		<para>
+		The permissions field is displayed differently for files and directories. Both are discussed next.
+		</para>
+
+		<sect3>
+		<title>File Permissions</title>
+
+		<para>
+		The standard UNIX user/group/world triplet and the corresponding <constant>read, write,
+		execute</constant> permissions triplets are mapped by Samba into a three-element NT ACL with the
+		<quote>r</quote>, <quote>w</quote>, and <quote>x</quote> bits mapped into the corresponding NT
+		permissions. The UNIX world permissions are mapped into the global NT group <constant>Everyone</constant>, followed 
+		by the list of permissions allowed for the UNIX world. The UNIX owner and group permissions are displayed as an NT 
+		<guiicon>user</guiicon> icon and an NT <guiicon>local group</guiicon> icon, respectively, followed by the list 
+		of permissions allowed for the UNIX user and group.
+		</para>
+
+		<para>
+		Because many UNIX permission sets do not map into common NT names such as <constant>read</constant>,
+		<constant>change</constant>, or <constant>full control</constant>, usually the permissions will be prefixed
+		by the words <constant>Special Access</constant> in the NT display list.
+		</para>
+
+		<para>
+		But what happens if the file has no permissions allowed for a particular UNIX user group or world component?
+		In order to  allow <emphasis>no permissions</emphasis> to be seen and modified, Samba then overloads the NT
+		<constant>Take Ownership</constant> ACL attribute (which has no meaning in UNIX) and reports a component with
+		no permissions as having the NT <command>O</command> bit set.  This was chosen, of course, to make it look
+		like a zero, meaning zero permissions. More details on the decision behind this action are given below.
+		</para>
+
+		</sect3>
+		
+		<sect3>
+		<title>Directory Permissions</title>
+
+		<para>
+		Directories on an NT NTFS file system have two different sets of permissions. The first set is the ACL set on the
+		directory itself, which is usually displayed in the first set of parentheses in the normal <constant>RW</constant> 
+		NT style. This first set of permissions is created by Samba in exactly the same way as normal file permissions are, described 
+		above, and is displayed in the same way.
+		</para>
+
+		<para>
+		The second set of directory permissions has no real meaning in the UNIX permissions world and represents the <constant>
+		inherited</constant> permissions that any file created within this directory would inherit.
+		</para>
+
+		<para>
+		Samba synthesizes these inherited permissions for NT by returning as an NT ACL the UNIX permission mode that a new file 
+		created by Samba on this share would receive.
+		</para>
+
+		</sect3>
+
+	</sect2>
+		
+	<sect2>
+	<title>Modifying File or Directory Permissions</title>
+
+	<para>
+	Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box
+	and clicking on <guibutton>OK</guibutton>. However, there are limitations that a user needs to be aware of,
+	and also interactions with the standard Samba permission masks and mapping of DOS attributes that also need to
+	be taken into account.
+	</para>
+
+	<para>
+	If the parameter <smbconfoption name="nt acl support"/> is set to <constant>false</constant>, any attempt to
+	set security permissions will fail with an <errorname>"Access Denied" </errorname> message.
+	</para>
+
+	<para>
+	The first thing to note is that the <guibutton>Add</guibutton> button will not return a list of users in Samba
+	(it will give an error message saying <errorname>"The remote procedure call failed and did not
+	execute"</errorname>). This means that you can only manipulate the current user/group/world permissions listed
+	in the dialog box. This actually works quite well because these are the only permissions that UNIX actually
+	has.
+	</para>
+
+	<para>
+	If a permission triplet (either user, group, or world) is removed from the list of permissions in the NT
+	dialog box, then when the <guibutton>OK</guibutton> button is pressed, it will be applied as <emphasis>no
+	permissions</emphasis> on the UNIX side. If you view the permissions again, the <emphasis>no
+	permissions</emphasis> entry will appear as the NT <command>O</command> flag, as described above. This allows
+	you to add permissions back to a file or directory once you have removed them from a triplet component.
+	</para>
+
+	<para>
+	Because UNIX supports only the <quote>r</quote>, <quote>w</quote>, and <quote>x</quote> bits of an NT ACL, if
+	other NT security attributes such as <constant>Delete Access</constant> are selected, they will be ignored
+	when applied on the Samba server.
+	</para>
+
+	<para>
+	When setting permissions on a directory, the second set of permissions (in the second set of parentheses) is
+	by default applied to all files within that directory. If this is not what you want, you must uncheck the
+	<guilabel>Replace permissions on existing files</guilabel> checkbox in the NT dialog before clicking on
+	<guibutton>OK</guibutton>.
+	</para>
+
+	<para>
+	If you wish to remove all permissions from a user/group/world  component, you may either highlight the
+	component and click on the <guibutton>Remove</guibutton> button or set the component to only have the special
+	<constant>Take Ownership</constant> permission (displayed as <command>O</command>) highlighted.
+	</para>
+
+	</sect2>
+
+<?latex \newpage ?>
+	<sect2>
+	<title>Interaction with the Standard Samba <quote>create mask</quote> Parameters</title>
+
+	<para>There are four parameters that control interaction with the standard Samba <parameter>create mask</parameter> parameters:
+	
+
+	<itemizedlist>
+		<listitem><para><smbconfoption name="security mask"/></para></listitem>
+		<listitem><para><smbconfoption name="force security mode"/></para></listitem>
+		<listitem><para><smbconfoption name="directory security mask"/></para></listitem>
+		<listitem><para><smbconfoption name="force directory security mode"/></para></listitem>
+	</itemizedlist>
+
+	</para>
+
+	<para>
+	When a user clicks on <guibutton>OK</guibutton> to apply the 
+	permissions, Samba maps the given permissions into a user/group/world 
+	r/w/x triplet set, and then checks the changed permissions for a 
+	file against the bits set in the  
+	<smbconfoption name="security mask"/> parameter. Any bits that 
+	were changed that are not set to <emphasis>1</emphasis> in this parameter are left alone 
+	in the file permissions.</para>
+
+	<para>
+	Essentially, zero bits in the <smbconfoption name="security mask"/>
+	may be treated as a set of bits the user is <emphasis>not</emphasis> 
+	allowed to change, and one bits are those the user is allowed to change.
+	</para>
+
+	<para>
+	If not explicitly set, this parameter defaults to the same value as 
+	the <smbconfoption name="create mask"/> parameter. To allow a user to modify all the
+	user/group/world permissions on a file, set this parameter to 0777.
+	</para>
+
+	<para>
+	Next Samba checks the changed permissions for a file against the bits set in the 
+	<smbconfoption name="force security mode"/> parameter. Any bits 
+	that were changed that correspond to bits set to <emphasis>1</emphasis> in this parameter 
+	are forced to be set.</para>
+
+	<para>
+	Essentially, bits set in the <parameter>force security mode</parameter> parameter
+	may be treated as a set of bits that, when modifying security on a file, the user 
+	has always set to be <emphasis>on</emphasis>.</para>
+
+	<para>
+	If not explicitly set, this parameter defaults to the same value 
+	as the <smbconfoption name="force create mode"/> parameter.
+	To allow a user to modify all the user/group/world permissions on a file
+	with no restrictions, set this parameter to 000. The
+	<smbconfoption name="security mask"/> and <parameter>force 
+	security mode</parameter> parameters are applied to the change 
+	request in that order.</para>
+
+	<para>
+	For a directory, Samba performs the same operations as 
+	described above for a file except it uses the parameter <parameter>
+	directory security mask</parameter> instead of <parameter>security 
+	mask</parameter>, and <parameter>force directory security mode
+	</parameter> parameter instead of <parameter>force security mode
+	</parameter>.</para>
+
+	<para>
+	The <smbconfoption name="directory security mask"/> parameter 
+	by default is set to the same value as the <parameter>directory mask
+	</parameter> parameter and the <parameter>force directory security 
+	mode</parameter> parameter by default is set to the same value as 
+	the <smbconfoption name="force directory mode"/> parameter.
+	In this way Samba enforces the permission restrictions that 
+	an administrator can set on a Samba share, while still allowing users 
+	to modify the permission bits within that restriction.</para>
+
+	<para>
+	If you want to set up a share that allows users full control
+	in modifying the permission bits on their files and directories and
+	does not force any particular bits to be set <emphasis>on</emphasis>,
+	then set the following parameters in the &smb.conf; file in that
+	share-specific section:
+	</para>
+
+<?latex \newpage ?>
+	<smbconfblock>
+		<smbconfoption name="security mask">0777</smbconfoption>
+		<smbconfoption name="force security mode">0</smbconfoption>
+		<smbconfoption name="directory security mask">0777</smbconfoption>
+		<smbconfoption name="force directory security mode">0</smbconfoption>
+	</smbconfblock>
+
+</sect2>
+
+<sect2>
+	<title>Interaction with the Standard Samba File Attribute Mapping</title>
+
+	<note>
+	<para>
+	Samba maps some of the DOS attribute bits (such as <quote>read-only</quote>)
+	into the UNIX permissions of a file. This means there can 
+	be a conflict between the permission bits set via the security 
+	dialog and the permission bits set by the file attribute mapping.
+	</para>
+	</note>
+
+	<para>
+	If a file has no UNIX read access for the owner, it will show up
+	as <quote>read-only</quote> in the standard file attributes tabbed dialog.
+	Unfortunately, this dialog is the same one that contains the security information
+	in another tab.
+	</para>
+
+	<para>
+	What this can mean is that if the owner changes the permissions
+	to allow himself or herself read access using the security dialog, clicks on
+	<guibutton>OK</guibutton> to get back to the standard attributes tab 
+	dialog, and clicks on <guibutton>OK</guibutton> on that dialog, then 
+	NT will set the file permissions back to read-only (as that is what 
+	the attributes still say in the dialog). This means that after setting 
+	permissions and clicking on <guibutton>OK</guibutton> to get back to the 
+	attributes dialog, you should always press <guibutton>Cancel</guibutton> 
+	rather than <guibutton>OK</guibutton> to ensure that your changes 
+	are not overridden.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Windows NT/200X ACLs and POSIX ACLs Limitations</title>
+
+	<para>
+	Windows administrators are familiar with simple ACL controls, and they typically
+	consider that UNIX user/group/other (ugo) permissions are inadequate and not
+	sufficiently fine-grained.
+	</para>
+
+	<para>
+	Competing SMB implementations differ in how they handle Windows ACLs. Samba handles
+	Windows ACLs from the perspective of UNIX file system administration and thus adopts
+	the limitations of POSIX ACLs. Therefore, where POSIX ACLs lack a capability of the
+	Windows NT/200X ACLs, the POSIX semantics and limitations are imposed on the Windows
+	administrator.
+	</para>
+
+	<para>
+	POSIX ACLs present an interesting challenge to the UNIX administrator and therefore
+	force a compromise to be applied to Windows ACLs administration. POSIX ACLs are not
+	covered by an official standard; rather, the latest standard is a draft standard
+	1003.1e revision 17. This is the POSIX document on which the Samba implementation has
+	been implemented.
+	</para>
+
+	<para>
+	UNIX vendors differ in the manner in which POSIX ACLs are implemented. There are a
+	number of Linux file systems that support ACLs. Samba has to provide a way to make
+	transparent all the differences between the various implementations of POSIX ACLs.
+	The pressure for ACLs support in Samba has noticeably increased the pressure to
+	standardize ACLs support in the UNIX world.
+	</para>
+
+	<para>
+	Samba has to deal with the complicated matter of handling the challenge of the Windows
+	ACL that implements <emphasis>inheritance</emphasis>, a concept not anticipated by POSIX
+	ACLs as implemented in UNIX file systems. Samba provides support for <emphasis>masks</emphasis>
+	that permit normal ugo and ACLs functionality to be overrided. This further complicates
+	the way in which Windows ACLs must be implemented.
+	</para>
+
+	<sect3>
+	<title>UNIX POSIX ACL Overview</title>
+
+	<para>
+	In examining POSIX ACLs we must consider the manner in which they operate for 
+	both files and directories. File ACLs have the following significance:
+<screen>
+# file: testfile      &lt;- the file name
+# owner: jeremy       &lt;-- the file owner
+# group: users        &lt;-- the POSIX group owner
+user::rwx             &lt;-- perms for the file owner (user)
+user:tpot:r-x         &lt;-- perms for the additional user `tpot'
+group::r--            &lt;-- perms for the file group owner (group)
+group:engrs:r--       &lt;-- perms for the additonal group `engineers'
+mask:rwx              &lt;-- the mask that is `ANDed' with groups
+other::---            &lt;-- perms applied to everyone else (other)
+</screen>
+	Directory ACLs have the following signficance:
+<screen>
+# file: testdir       &lt;-- the directory name
+# owner: jeremy       &lt;-- the directory owner
+# group: jeremy       &lt;-- the POSIX group owner
+user::rwx             &lt;-- directory perms for owner (user)
+group::rwx            &lt;-- directory perms for owning group (group)
+mask::rwx             &lt;-- the mask that is `ANDed' with group perms
+other:r-x             &lt;-- perms applied to everyone else (other)
+default:user::rwx     &lt;-- inherited owner perms
+default:user:tpot:rwx &lt;-- inherited extra perms for user `tpot'
+default:group::r-x    &lt;-- inherited group perms
+default:mask:rwx      &lt;-- inherited default mask
+default:other:---     &lt;-- inherited permissions for everyone (other)
+</screen>
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Mapping of Windows File ACLs to UNIX POSIX ACLs</title>
+
+	<para>
+	Microsoft Windows NT4/200X ACLs must of necessity be mapped to POSIX ACLs.
+	The mappings for file permissions are shown in <link linkend="fdsacls">How
+	Windows File ACLs Map to UNIX POSIX File ACLs</link>.
+	The # character means this flag is set only when the Windows administrator
+	sets the <constant>Full Control</constant> flag on the file.
+	</para>
+
+	<table frame='all' pgwide='0' id="fdsacls"><title>How Windows File ACLs Map to UNIX POSIX File ACLs</title>
+	<tgroup cols='2'>
+		<colspec align="left"/>
+		<colspec align="center"/>
+		<thead>
+		<row>
+			<entry align="left">Windows ACE</entry>
+			<entry align="center">File Attribute Flag</entry>
+		</row>
+		</thead>
+		<tbody>
+		<row>
+			<entry><para>Full Control</para></entry>
+			<entry><para>#</para></entry>
+		</row>
+		<row>
+			<entry><para>Traverse Folder/Execute File</para></entry>
+			<entry><para>x</para></entry>
+		</row>
+		<row>
+			<entry><para>List Folder/Read Data</para></entry>
+			<entry><para>r</para></entry>
+		</row>
+		<row>
+			<entry><para>Read Attributes</para></entry>
+			<entry><para>r</para></entry>
+		</row>
+		<row>
+			<entry><para>Read Extended Attribures</para></entry>
+			<entry><para>r</para></entry>
+		</row>
+		<row>
+			<entry><para>Create Files/Write Data</para></entry>
+			<entry><para>w</para></entry>
+		</row>
+		<row>
+			<entry><para>Create Folders/Append Data</para></entry>
+			<entry><para>w</para></entry>
+		</row>
+		<row>
+			<entry><para>Write Attributes</para></entry>
+			<entry><para>w</para></entry>
+		</row>
+		<row>
+			<entry><para>Write Extended Attributes</para></entry>
+			<entry><para>w</para></entry>
+		</row>
+		<row>
+			<entry><para>Delete Subfolders and Files</para></entry>
+			<entry><para>w</para></entry>
+		</row>
+		<row>
+			<entry><para>Delete</para></entry>
+			<entry><para>#</para></entry>
+		</row>
+		<row>
+			<entry><para>Read Permissions</para></entry>
+			<entry><para>all</para></entry>
+		</row>
+		<row>
+			<entry><para>Change Permissions</para></entry>
+			<entry><para>#</para></entry>
+		</row>
+		<row>
+			<entry><para>Take Ownership</para></entry>
+			<entry><para>#</para></entry>
+		</row>
+		</tbody>
+	</tgroup>
+	</table>
+
+	<para>
+	As can be seen from the mapping table, there is no one-to-one mapping capability, and therefore
+	Samba must make a logical mapping that will permit Windows to operate more-or-less the way
+	that is intended by the administrator.
+	</para>
+
+	<para>
+	In general the mapping of UNIX POSIX user/group/other permissions will be mapped to
+	Windows ACLs. This has precedence over the creation of POSIX ACLs. POSIX ACLs are necessary
+	to establish access controls for users and groups other than the user and group that
+	own the file or directory.
+	</para>
+
+	<para>
+	The UNIX administrator can set any directory permission from within the UNIX environment.
+	The Windows administrator is more restricted in that it is not possible from within 
+	Windows Explorer to remove read permission for the file owner.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Mapping of Windows Directory ACLs to UNIX POSIX ACLs</title>
+
+	<para>
+	Interesting things happen in the mapping of UNIX POSIX directory permissions and
+	UNIX POSIX ACLs to Windows ACEs (Access Control Entries, the discrete components of
+	an ACL) are mapped to Windows directory ACLs.
+	</para>
+
+	<para>
+	Directory permissions function in much the same way as shown for file permissions, but
+	there are some notable exceptions and a few peculiarities that the astute administrator
+	will want to take into account in the setting up of directory permissions.
+	</para>
+
+	</sect3>
+
+	</sect2>
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+File, directory, and share access problems are common topics on the mailing list. The following
+are examples recently taken from the mailing list.
+</para>
+
+
+	<sect2>
+	<title>Users Cannot Write to a Public Share</title>
+
+	<para>
+	The following complaint has frequently been voiced on the Samba mailing list: 
+	<quote>
+	We are facing some troubles with file/directory permissions. I can log on the domain as admin user (root),
+	and there's a public share on which everyone needs to have permission to create/modify files, but only
+	root can change the file, no one else can. We need to constantly go to the server to
+	<userinput>chgrp -R users *</userinput> and <userinput>chown -R nobody *</userinput> to allow
+	other users to change the file.
+	</quote>
+	</para>
+
+	<para>
+	Here is one way the problem can be solved:
+	</para>
+
+	<procedure>
+		<step>
+			<para>
+			Go to the top of the directory that is shared.
+			</para>
+		</step>
+
+		<step>
+			<para>
+			Set the ownership to whatever public user and group you want
+<screen>
+&prompt;find `directory_name' -type d -exec chown user:group {}\;
+&prompt;find `directory_name' -type d -exec chmod 2775 {}\;
+&prompt;find `directory_name' -type f -exec chmod 0775 {}\;
+&prompt;find `directory_name' -type f -exec chown user:group {}\;
+</screen>
+			</para>
+
+			<note><para>
+			The above will set the <constant>SGID bit</constant> on all directories. Read your
+			UNIX/Linux man page on what that does. This ensures that all files and directories
+			that are created in the directory tree will be owned by the current user and will
+			be owned by the group that owns the directory in which it is created.
+			</para></note>
+		</step>
+		<step>
+			<para>
+			Directory is <replaceable>/foodbar</replaceable>:
+<screen>
+&prompt;<userinput>chown jack:engr /foodbar</userinput>
+</screen>
+			</para>
+
+			<note>
+			<para>This is the same as doing:</para>
+<screen>
+&prompt;<userinput>chown jack /foodbar</userinput>
+&prompt;<userinput>chgrp engr /foodbar</userinput>
+</screen>
+			</note>
+		</step>
+		<step>
+			<para>Now type: 
+
+<screen>
+&prompt;<userinput>chmod 2775 /foodbar</userinput>
+&prompt;<userinput>ls -al /foodbar/..</userinput>
+</screen>
+			</para>
+		
+			<para>You should see:
+<screen>
+drwxrwsr-x  2 jack  engr    48 2003-02-04 09:55 foodbar
+</screen>
+			</para>
+		</step>
+		<step>
+
+		<para>Now type:
+<screen>
+&prompt;<userinput>su - jill</userinput>
+&prompt;<userinput>cd /foodbar</userinput>
+&prompt;<userinput>touch Afile</userinput>
+&prompt;<userinput>ls -al</userinput>
+</screen>
+		</para>
+
+		<para>
+		You should see that the file <filename>Afile</filename> created by Jill will have ownership
+		and permissions of Jack, as follows:
+<screen>
+-rw-r--r--  1 jill  engr     0 2007-01-18 19:41 Afile
+</screen>
+		</para>
+		</step>
+
+		<step>
+		<para>
+		If the user that must have write permission in the directory is not a member of the group
+		<emphasis>engr</emphasis> set in the &smb.conf; entry for the share:
+		<smbconfblock>
+<smbconfoption name="force group">engr</smbconfoption>
+		</smbconfblock>
+		</para>
+	</step>
+	</procedure>
+	</sect2>
+
+
+	<sect2>
+		<title>File Operations Done as <emphasis>root</emphasis> with <emphasis>force user</emphasis> Set</title>
+
+		<para>
+		When you have a user in <smbconfoption name="admin users"/>, Samba will always do file operations for
+		this user as <emphasis>root</emphasis>, even if <smbconfoption name="force user"/> has been set.
+		</para>
+	</sect2>
+	
+	<sect2>
+		<title>MS Word with Samba Changes Owner of File</title>
+
+		<para>
+		<emphasis>Question:</emphasis> <quote>When user B saves a word document that is owned by user A,
+		the updated file is now owned by user B.  Why is Samba doing this? How do I fix this?</quote>
+		</para>
+
+		<para>
+		<emphasis>Answer:</emphasis> Word does the following when you modify/change a Word document: MS Word creates a new document with
+		a temporary name. Word then closes the old document and deletes it, then renames the new document to the original document name.
+		There is no mechanism by which Samba can in any way know that the new document really should be owned by the owners
+		of the original file. Samba has no way of knowing that the file will be renamed by MS Word. As far as Samba is able
+		to tell, the file that gets created is a new file, not one that the application (Word) is updating.
+		</para>
+
+		<para>
+		There is a workaround to solve the permissions problem. It involves understanding how you can manage file
+		system behavior from within the &smb.conf; file, as well as understanding how UNIX file systems work. Set on the directory
+		in which you are changing Word documents: <command>chmod g+s `directory_name'.</command> This ensures that all files will
+		be created with the group that owns the directory. In &smb.conf; share declaration section set:
+		</para>
+
+		<para>
+		<smbconfblock>
+                <smbconfoption name="force create mode">0660</smbconfoption>
+                <smbconfoption name="force directory mode">0770</smbconfoption>
+		</smbconfblock>
+		</para>
+
+		<para>
+		These two settings will ensure that all directories and files that get created in the share will be readable/writable by the
+		owner and group set on the directory itself.
+		</para>
+		
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-AdvancedNetworkAdmin.xml b/docs-xml/Samba3-HOWTO/TOSHARG-AdvancedNetworkAdmin.xml
new file mode 100644
index 00000000000..2ecfa4b1c3e
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-AdvancedNetworkAdmin.xml
@@ -0,0 +1,485 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="AdvancedNetworkManagement">
+<chapterinfo>
+	&author.jht;
+    <pubdate>June 15 2005</pubdate>
+</chapterinfo>
+
+<title>Advanced Network Management</title>
+
+<para>
+<indexterm><primary>access control</primary></indexterm>
+This section documents peripheral issues that are of great importance to network
+administrators who want to improve network resource access control, to automate the user
+environment, and to make their lives a little easier.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+Often the difference between a working network environment and a well-appreciated one can
+best be measured by the <emphasis>little things</emphasis> that make everything work more
+harmoniously. A key part of every network environment solution is the ability to remotely
+manage MS Windows workstations, remotely access the Samba server, provide customized
+logon scripts, as well as other housekeeping activities that help to sustain more reliable
+network operations.
+</para>
+
+<para>
+This chapter presents information on each of these areas. They are placed here, and not in
+other chapters, for ease of reference.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Remote Server Administration</title>
+
+
+<para><quote>How do I get User Manager and Server Manager?</quote></para>
+
+<para>
+<indexterm><primary>User Manager</primary></indexterm>
+<indexterm><primary>Server Manager</primary></indexterm>
+<indexterm><primary>Event Viewer</primary></indexterm>
+Since I do not need to buy an <application>NT4 server</application>, how do I get the User Manager for Domains
+and the Server Manager?
+</para>
+
+<para>
+<indexterm><primary>Nexus.exe</primary></indexterm>
+<indexterm><primary>Windows 9x/Me</primary></indexterm>
+Microsoft distributes a version of these tools called <filename>Nexus.exe</filename> for installation 
+on <application>Windows 9x/Me</application> systems. The tools set includes:
+</para>
+
+<itemizedlist>
+	<listitem><para>Server Manager</para></listitem>
+	<listitem><para>User Manager for Domains</para></listitem>
+	<listitem><para>Event Viewer</para></listitem>
+</itemizedlist>
+
+<para>
+Download the archived file at the Microsoft <ulink noescape="1"
+url="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE">Nexus</ulink> link.
+</para>
+
+<para>
+<indexterm><primary>SRVTOOLS.EXE</primary></indexterm>
+<indexterm><primary>User Manager for Domains</primary></indexterm>
+<indexterm><primary>Server Manager</primary></indexterm>
+The <application>Windows NT 4.0</application> version of the User Manager for 
+Domains and Server Manager are available from Microsoft
+<ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">via ftp</ulink>.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Remote Desktop Management</title>
+
+<para>
+<indexterm><primary>remote desktop management</primary></indexterm>
+<indexterm><primary>network environment</primary></indexterm>
+There are a number of possible remote desktop management solutions that range from free
+through costly. Do not let that put you off. Sometimes the most costly solution is the
+most cost effective. In any case, you will need to draw your own conclusions as to which
+is the best tool in your network environment.
+</para>
+
+	<sect2>
+	<title>Remote Management from NoMachine.Com</title>
+
+	<para>
+	<indexterm><primary>NoMachine.Com</primary></indexterm>
+	The following information was posted to the Samba mailing list at Apr 3 23:33:50 GMT 2003.
+	It is presented in slightly edited form (with author details omitted for privacy reasons).
+	The entire answer is reproduced below with some comments removed.
+	</para>
+
+		<para><quote>
+<indexterm><primary>remote desktop capabilities</primary></indexterm>
+		I have a wonderful Linux/Samba server running as PDC for a network. Now I would like to add remote
+		desktop capabilities so users outside could login to the system and get their desktop up from home or
+		another country.
+		</quote></para>
+
+		<para><quote>
+<indexterm><primary>Windows Terminal server</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>remote login</primary></indexterm>
+		Is there a way to accomplish this? Do I need a Windows Terminal server?  Do I need to configure it so
+		it is a member of the domain or a BDC or PDC? Are there any hacks for MS Windows XP to enable remote login
+		even if the computer is in a domain?
+		</quote></para>
+
+		<para>
+		Answer provided: Check out the new offer of <quote>NX</quote> software from
+		<ulink noescape="1" url="http://www.nomachine.com/">NoMachine</ulink>.
+		</para>
+
+	<para>
+<indexterm><primary>Remote X protocol</primary></indexterm>
+<indexterm><primary>VNC/RFB</primary></indexterm>
+<indexterm><primary>rdesktop/RDP</primary></indexterm>
+	It implements an easy-to-use interface to the Remote X protocol as
+	well as incorporating VNC/RFB and rdesktop/RDP into it, but at a speed
+	performance much better than anything you may have ever seen.
+	</para>
+
+	<para>
+<indexterm><primary>modem/ISDN</primary></indexterm>
+	Remote X is not new at all, but what they did achieve successfully is
+	a new way of compression and caching technologies that makes the thing
+	fast enough to run even over slow modem/ISDN connections.
+	</para>
+
+	<para>
+<indexterm><primary>KDE konqueror</primary></indexterm>
+<indexterm><primary>mouse-over</primary></indexterm>
+<indexterm><primary>rdesktop</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+	I test drove their (public) Red Hat machine in Italy, over a loaded
+	Internet connection, with enabled thumbnail previews in KDE konqueror,
+	which popped up immediately on <quote>mouse-over</quote>. From inside that (remote X)
+	session I started a rdesktop session on another, a Windows XP machine.
+	To test the performance, I played Pinball. I am proud to announce
+	that my score was 631,750 points at first try.
+	</para>
+
+	<para>
+<indexterm><primary>NX</primary></indexterm>
+<indexterm><primary>TightVNC</primary></indexterm>
+<indexterm><primary>rdesktop</primary></indexterm>
+<indexterm><primary>Remote X</primary></indexterm>
+	NX performs better on my local LAN than any of the other <quote>pure</quote>
+	connection methods I use from time to time: TightVNC, rdesktop or
+	Remote X. It is even faster than a direct crosslink connection between
+	two nodes.
+	</para>
+
+	<para>
+<indexterm><primary>Remote X</primary></indexterm>
+<indexterm><primary>KDE session</primary></indexterm>
+<indexterm><primary>copy'n'paste</primary></indexterm>
+	I even got sound playing from the Remote X app to my local boxes, and
+	had a working <quote>copy'n'paste</quote> from an NX  window (running a KDE session
+	in Italy) to my Mozilla mailing agent. These guys are certainly doing
+	something right!
+	</para>
+
+	<para>
+	I recommend test driving NX to anybody with a only a passing interest in remote computing
+	the <ulink noescape="1" url="http://www.nomachine.com/testdrive.php">NX</ulink> utility.
+	</para>
+
+	<para>
+	Just download the free-of-charge client software (available for Red Hat,
+	SuSE, Debian and Windows) and be up and running within 5 minutes (they
+	need to send you your account data, though, because you are assigned
+	a real UNIX account on their testdrive.nomachine.com box).
+	</para>
+
+	<para>
+	They plan to get to the point were you can have NX application servers
+	running as a cluster of nodes, and users simply start an NX session locally
+	and can select applications to run transparently (apps may even run on
+	another NX node, but pretend to be on the same as used for initial login,
+	because it displays in the same window. You also can run it
+	full-screen, and after a short time you forget that it is a remote session
+	at all).
+	</para>
+
+	<para>
+<indexterm><primary>GPL</primary></indexterm>
+	Now the best thing for last: All the core compression and caching
+	technologies are released under the GPL and available as source code
+	to anybody who wants to build on it! These technologies are working,
+	albeit started from the command line only (and very inconvenient to
+	use in order to get a fully running remote X session up and running).
+	</para>
+
+	<para>
+	To answer your questions:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		You do not need to install a terminal server; XP has RDP support built in.
+		</para></listitem>
+
+		<listitem><para>
+		NX is much cheaper than Citrix &smbmdash; and comparable in performance, probably faster.
+		</para></listitem>
+
+		<listitem><para>
+		You do not need to hack XP &smbmdash; it just works.
+		</para></listitem>
+
+		<listitem><para>
+		You log into the XP box from remote transparently (and I think there is no
+		need to change anything to get a connection, even if authentication is against a domain).
+		</para></listitem>
+
+		<listitem><para>
+		The NX core technologies are all Open Source and released under the GPL &smbmdash;
+		you can now use a (very inconvenient) command line at no cost,
+		but you can buy a comfortable (proprietary) NX GUI front end for money.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>OSS/Free Software</primary></indexterm>
+<indexterm><primary>LTSP</primary></indexterm>
+<indexterm><primary>KDE</primary></indexterm>
+<indexterm><primary>GNOME</primary></indexterm>
+<indexterm><primary>NoMachine</primary></indexterm>
+		NoMachine is encouraging and offering help to OSS/Free Software implementations
+		for such a front-end too, even if it means competition to them (they have written
+		to this effect even to the LTSP, KDE, and GNOME developer mailing lists).
+		</para></listitem>
+	</itemizedlist>
+
+	</sect2>
+	<sect2>
+	<title>Remote Management with ThinLinc</title>
+	<para>
+	Another alternative for remote access is <emphasis>ThinLinc</emphasis> from Cendio.
+	</para>
+
+	<para>
+<indexterm><primary>ThinLinc</primary></indexterm>
+<indexterm><primary>terminal server</primary></indexterm>
+<indexterm><primary>Linux</primary></indexterm>
+<indexterm><primary>Solaris</primary></indexterm>
+<indexterm><primary>TightVNC</primary></indexterm>
+<indexterm><primary>SSH</primary></indexterm>
+<indexterm><primary>NFS</primary></indexterm>
+<indexterm><primary>PulseAudio</primary></indexterm>
+	ThinLinc is a terminal server solution that is available for Linux and Solaris based on standard
+	protocols such as SSH, TightVNC, NFS and PulseAudio.
+	</para>
+
+	<para>
+<indexterm><primary>LAN</primary></indexterm>
+<indexterm><primary>thin client</primary></indexterm>
+	ThinLinc an be used both in the LAN environment to implement a Thin Client strategy for an organization, and as
+	secure remote access solution for people working from remote locations, even over smallband connections.
+	ThinLinc is free to use for a single concurrent user.
+	</para>
+
+	<para>
+<indexterm><primary>Citrix</primary></indexterm>
+<indexterm><primary>Windows Terminal Server</primary></indexterm>
+<indexterm><primary>Java</primary></indexterm>
+	The product can also be used as a frontend to access Windows Terminal Server or Citrix farms, or even Windows
+	XP machines, securing the connection via the ssh protocol. The client is available both for Linux (supporting
+	all Linux distributions as well as numerous thin terminals) and for Windows. A Java-based Web client is also
+	available.
+	</para>
+
+	<para>
+	ThinLinc may be evaluated by connecting to Cendio's demo system, see
+	<ulink noescape="1" url="http://www.cendio.com">Cendio's</ulink> web site
+	<ulink noescape="1" url="http://www.cendio.com/testdrive">testdrive</ulink> center.
+	</para>
+
+	<para>
+	Cendio is a major contributor to several open source projects including
+	<ulink noescape="1" url="http://www.tightvnc.com">TightVNC</ulink>,
+	<ulink noescape="1" url="http://pulseaudio.org">PulseAudio</ulink> , unfsd,
+	<ulink noescape="1" url="http://www.python.org">Python</ulink> and
+	<ulink noescape="1" url="http://www.rdesktop.org">rdesktop</ulink>.
+	</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+<title>Network Logon Script Magic</title>
+
+<para>
+There are several opportunities for creating a custom network startup configuration environment.
+</para>
+
+<itemizedlist>
+	<listitem><para>No Logon Script.</para></listitem>
+	<listitem><para>Simple universal Logon Script that applies to all users.</para></listitem>
+	<listitem><para>Use of a conditional Logon Script that applies per-user or per-group attributes.</para></listitem>
+	<listitem><para>Use of Samba's preexec and postexec functions on access to the NETLOGON share to create
+		a custom logon script and then execute it.</para></listitem>
+	<listitem><para>User of a tool such as KixStart.</para></listitem>
+</itemizedlist>
+
+<para>
+The Samba source code tree includes two logon script generation/execution tools.
+See <filename>examples</filename> directory <filename>genlogon</filename> and
+<filename>ntlogon</filename> subdirectories.
+</para>
+
+<para>
+The following listings are from the genlogon directory.
+</para>
+
+
+<para>
+<indexterm><primary>genlogon.pl</primary></indexterm>
+This is the <filename>genlogon.pl</filename> file:
+
+<programlisting>
+	#!/usr/bin/perl
+	#
+	# genlogon.pl
+	#
+	# Perl script to generate user logon scripts on the fly, when users
+	# connect from a Windows client. This script should be called from 
+	# smb.conf with the %U, %G and %L parameters. I.e:
+	#
+	#       root preexec = genlogon.pl %U %G %L
+	#
+	# The script generated will perform
+	# the following:
+	#
+	# 1. Log the user connection to /var/log/samba/netlogon.log
+	# 2. Set the PC's time to the Linux server time (which is maintained
+	#    daily to the National Institute of Standards Atomic clock on the
+	#    internet.
+	# 3. Connect the user's home drive to H: (H for Home).
+	# 4. Connect common drives that everyone uses.
+	# 5. Connect group-specific drives for certain user groups.
+	# 6. Connect user-specific drives for certain users.
+	# 7. Connect network printers.
+
+	# Log client connection
+	#($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
+	($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
+	open LOG, ">>/var/log/samba/netlogon.log";
+	print LOG "$mon/$mday/$year $hour:$min:$sec";
+	print LOG " - User $ARGV[0] logged into $ARGV[1]\n";
+	close LOG;
+
+	# Start generating logon script
+	open LOGON, ">/shared/netlogon/$ARGV[0].bat";
+	print LOGON "\@ECHO OFF\r\n";
+
+	# Connect shares just use by Software Development group
+	if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev")
+	{
+		print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n";
+	}
+
+	# Connect shares just use by Technical Support staff
+	if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support")
+	{
+		print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n";
+	}
+
+	# Connect shares just used by Administration staff
+	If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin")
+	{
+		print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n";
+		print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n";
+	}
+
+	# Now connect Printers. We handle just two or three users a little
+	# differently, because they are the exceptions that have desktop
+	# printers on LPT1: - all other user's go to the LaserJet on the
+	# server.
+	if ($ARGV[0] eq 'jim'
+	    || $ARGV[0] eq 'yvonne')
+	{
+		print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n";
+		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
+	}
+	else
+	{
+		print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n";
+		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
+	}
+
+	# All done! Close the output file.
+	close LOGON;
+</programlisting>
+</para>
+
+<para>
+Those wishing to use a more elaborate or capable logon processing system should check out these sites:
+</para>
+
+<itemizedlist>
+	<listitem><para><ulink noescape="1" url="http://www.craigelachie.org/rhacer/ntlogon">http://www.craigelachie.org/rhacer/ntlogon</ulink></para></listitem>
+	<listitem><para><ulink noescape="1" url="http://www.kixtart.org">http://www.kixtart.org</ulink></para></listitem>
+</itemizedlist>
+
+<sect2>
+<title>Adding Printers without User Intervention</title>
+
+
+<para>
+<indexterm><primary>rundll32</primary></indexterm>
+Printers may be added automatically during logon script processing through the use of:
+<screen>
+&dosprompt;<userinput>rundll32 printui.dll,PrintUIEntry /?</userinput>
+</screen>
+
+See the documentation in the <ulink url="http://support.microsoft.com/default.asp?scid=kb;en-us;189105">Microsoft Knowledge Base article 189105</ulink>.
+</para>
+</sect2>
+
+<sect2>
+	<title>Limiting Logon Connections</title>
+
+	<para>
+		Sometimes it is necessary to limit the number of concurrent connections to a
+		Samba shared resource. For example, a site may wish to permit only one network
+		logon per user.
+	</para>
+
+	<para>
+		The Samba <parameter>preexec script</parameter> parameter can be used to permit only one
+		connection per user. Though this method is not foolproof and may have side effects,
+		the following contributed method may inspire someone to provide a better solution.
+	</para>
+
+	<para>
+		This is not a perfect solution because Windows clients can drop idle connections
+		with an auto-reconnect capability that could result in the appearance that a share
+		is no longer in use, while actually it is. Even so, it demonstrates the principle
+		of use of the <parameter>preexec script</parameter> parameter.
+	</para>
+
+	<para>
+		The following share configuration demonstrates use of the script shown in <link linkend="Tpees"/>.
+<programlisting>
+[myshare]
+	...
+	preexec script = /sbin/PermitSingleLogon.sh
+	preexec close = Yes
+	...
+</programlisting>
+	</para>
+
+<example id="Tpees">
+<title>Script to Enforce Single Resource Logon</title>
+<screen>
+#!/bin/bash
+
+IFS="-"
+RESULT=$(smbstatus -S -u $1 2> /dev/null | awk 'NF \
+        > 6 {print $1}' | sort | uniq -d)
+
+if [ "X${RESULT}" == X  ]; then
+  exit 0
+else
+  exit 1
+fi
+</screen>
+</example>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-BDC.xml b/docs-xml/Samba3-HOWTO/TOSHARG-BDC.xml
new file mode 100644
index 00000000000..35fdd9ee572
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-BDC.xml
@@ -0,0 +1,862 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="samba-bdc">
+
+<chapterinfo>
+	&author.jht;
+	&author.vl;
+	<author>&person.gd;<contrib>LDAP updates</contrib></author>
+</chapterinfo>
+
+<title>Backup Domain Control</title>
+
+<para>
+Before you continue reading this section, please make sure that you are comfortable
+with configuring a Samba domain controller as described in <link linkend="samba-pdc">Domain Control</link>.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+This is one of the most difficult chapters to summarize. It does not matter what we say here, for someone will
+still draw conclusions and/or approach the Samba Team with expectations that are either not yet capable of
+being delivered or that can be achieved far more effectively using a totally different approach. In the event
+that you should have a persistent concern that is not addressed in this book, please email <ulink
+url="mailto:jht@samba.org">John H. Terpstra</ulink> clearly setting out your requirements and/or question, and
+we will do our best to provide a solution.
+</para>
+
+<para>
+<indexterm><primary>SAM backend</primary><secondary>LDAP</secondary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>LDAP</primary><secondary>slave</secondary></indexterm>
+<indexterm><primary>scalability</primary></indexterm>
+Samba-3 can act as a Backup Domain Controller (BDC) to another Samba Primary Domain Controller (PDC). A
+Samba-3 PDC can operate with an LDAP account backend. The LDAP backend can be either a common master LDAP
+server or a slave server. The use of a slave LDAP server has the benefit that when the master is down, clients
+may still be able to log onto the network.  This effectively gives Samba a high degree of scalability and is
+an effective solution for large organizations. If you use an LDAP slave server for a PDC, you will need to
+ensure the master's continued availability &smbmdash; if the slave finds its master down at the wrong time,
+you will have stability and operational problems.
+</para>
+
+<para>
+<indexterm><primary>two-way</primary><secondary>propagation</secondary></indexterm>
+<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
+<indexterm><primary>non-LDAP</primary><secondary>backend</secondary></indexterm>
+<indexterm><primary>propagate</primary></indexterm>
+While it is possible to run a Samba-3 BDC with a non-LDAP backend, that backend must allow some form of
+"two-way" propagation of changes from the BDC to the master.  At this time only LDAP delivers the capability
+to propagate identity database changes from the BDC to the PDC. The BDC can use a slave LDAP server, while it
+is preferable for the PDC to use as its primary an LDAP master server.
+</para>
+
+<para>
+<indexterm><primary>non-LDAP</primary><secondary>backend</secondary></indexterm>
+<indexterm><primary>SAM backend</primary><secondary>non-LDAP</secondary></indexterm>
+<indexterm><primary>domain</primary><secondary>member</secondary><tertiary>server</tertiary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>trust account password</primary></indexterm>
+<indexterm><primary>domain trust</primary></indexterm>
+The use of a non-LDAP backend SAM database is particularly problematic because domain member
+servers and workstations periodically change the Machine Trust Account password. The new
+password is then stored only locally. This means that in the absence of a centrally stored
+accounts database (such as that provided with an LDAP-based solution) if Samba-3 is running
+as a BDC, the BDC instance of the domain member trust account password will not reach the
+PDC (master) copy of the SAM. If the PDC SAM is then replicated to BDCs, this results in 
+overwriting the SAM that contains the updated (changed) trust account password with resulting
+breakage of the domain trust.
+</para>
+
+<para>
+<indexterm><primary>net</primary><secondary>rpc</secondary></indexterm>
+<indexterm><primary>SAM backend</primary><secondary>ldapsam</secondary></indexterm>
+<indexterm><primary>SAM backend</primary><secondary>tdbsam</secondary></indexterm>
+<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
+Considering the number of comments and questions raised concerning how to configure a BDC,
+let's consider each possible option and look at the pros and cons for each possible solution.
+<link linkend="pdc-bdc-table">The Domain Backend Account Distribution Options table below</link> lists 
+possible design configurations for a PDC/BDC infrastructure.
+</para>
+
+<table frame="all" id="pdc-bdc-table"><title>Domain Backend Account Distribution Options</title>
+<tgroup cols="3">
+        <colspec align="center" colwidth="1*"/>
+        <colspec align="center" colwidth="1*"/>
+        <colspec align="left" colwidth="3*"/>
+
+        <thead>
+        <row><entry>PDC Backend</entry><entry>BDC Backend</entry><entry>Notes/Discussion</entry></row>
+        </thead>
+        <tbody>
+        <row>
+        <entry><para>Master LDAP Server</para></entry>
+        <entry><para>Slave LDAP Server</para></entry>
+        <entry><para>The optimal solution that provides high integrity. The SAM will be
+		replicated to a common master LDAP server.</para></entry>
+        </row>
+        <row>
+        <entry><para>Single Central LDAP Server</para></entry>
+        <entry><para>Single Central LDAP Server</para></entry>
+	<entry><para>
+	A workable solution without failover ability. This is a usable solution, but not optimal. 
+	</para></entry>
+        </row>
+        <row>
+        <entry><para>tdbsam</para></entry>
+        <entry><para>tdbsam + <command>net rpc vampire</command></para></entry>
+        <entry><para>
+	Does not work with Samba-3.0; Samba does not implement the
+        server-side protocols required.
+	</para></entry>
+        </row>
+        <row>
+        <entry><para>tdbsam</para></entry>
+        <entry><para>tdbsam + <command>rsync</command></para></entry>
+        <entry><para>
+	Do not use this configuration.
+	Does not work because the TDB files are live and data may not
+        have been flushed to disk.  Furthermore, this will cause
+        domain trust breakdown.
+	</para></entry>
+        </row>
+        <row>
+        <entry><para>smbpasswd file</para></entry>
+        <entry><para>smbpasswd file</para></entry>
+        <entry><para>
+	Do not use this configuration.
+	Not an elegant solution due to the delays in synchronization
+        and also suffers
+        from the issue of domain trust breakdown.
+	</para></entry>
+        </row>
+        </tbody>
+</tgroup>
+</table>
+
+</sect1>
+
+<sect1>
+<title>Essential Background Information</title>
+
+<para>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>logon requests</primary></indexterm>
+<indexterm><primary>LanMan</primary></indexterm>
+<indexterm><primary>Netlogon</primary></indexterm>
+A domain controller is a machine that is able to answer logon requests from network
+workstations. Microsoft LanManager and IBM LanServer were two early products that
+provided this capability. The technology has become known as the LanMan Netlogon service.
+</para>
+
+<para>
+<indexterm>network<primary></primary><secondary>logon</secondary><tertiary>service</tertiary></indexterm>
+<indexterm><primary>Windows NT3.10</primary></indexterm>
+When MS Windows NT3.10 was first released, it supported a new style of Domain Control
+and with it a new form of the network logon service that has extended functionality.
+This service became known as the NT NetLogon Service. The nature of this service has
+changed with the evolution of MS Windows NT and today provides a complex array of
+services that are implemented over an intricate spectrum of technologies.
+</para>
+
+<sect2>
+<title>MS Windows NT4-style Domain Control</title>
+
+<para>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>authentication server</primary></indexterm>
+<indexterm><primary>username</primary></indexterm>
+<indexterm><primary>password</primary></indexterm>
+<indexterm><primary>SAM</primary></indexterm>
+<indexterm><primary>Security Account Manager</primary><see>SAM</see></indexterm>
+<indexterm><primary>domain control database</primary><see>SAM</see></indexterm>
+Whenever a user logs into a Windows NT4/200x/XP Professional workstation,
+the workstation connects to a domain controller (authentication server) to validate that
+the username and password the user entered are valid. If the information entered
+does not match account information that has been stored in the domain
+control database (the SAM, or Security Account Manager database), a set of error
+codes is returned to the workstation that has made the authentication request.
+</para>
+
+<para>
+<indexterm><primary>account information</primary></indexterm>
+<indexterm><primary>machine accounts database</primary></indexterm>
+<indexterm><primary>profile</primary></indexterm>
+<indexterm><primary>network access profile</primary></indexterm>
+<indexterm><primary>desktop profile</primary></indexterm>
+When the username/password pair has been validated, the domain controller
+(authentication server) will respond with full enumeration of the account information
+that has been stored regarding that user in the user and machine accounts database
+for that domain. This information contains a complete network access profile for
+the user but excludes any information that is particular to the user's desktop profile,
+or for that matter it excludes all desktop profiles for groups that the user may
+belong to. It does include password time limits, password uniqueness controls,
+network access time limits, account validity information, machine names from which the
+user may access the network, and much more. All this information was stored in the SAM
+in all versions of MS Windows NT (3.10, 3.50, 3.51, 4.0).
+</para>
+
+<para>
+<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
+<indexterm><primary>%SystemRoot%\System32\config</primary></indexterm>
+<indexterm><primary>C:\WinNT\System32\config</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>SAM</primary></indexterm>
+The account information (user and machine) on domain controllers is stored in two files,
+one containing the security information and the other the SAM. These are stored in files
+by the same name in the <filename>%SystemRoot%\System32\config</filename> directory. 
+This normally translates to the path <filename>C:\WinNT\System32\config</filename>. These
+are the files that are involved in replication of the SAM database where BDCs are present
+on the network.
+</para>
+
+<para>
+There are two situations in which it is desirable to install BDCs:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	On the local network that the PDC is on, if there are many
+	workstations and/or where the PDC is generally very busy. In this case the BDCs
+	will pick up network logon requests and help to add robustness to network services.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>network</primary><secondary>wide-area</secondary></indexterm>
+	At each remote site, to reduce wide-area network traffic and to add stability to
+	remote network operations. The design of the network, and the strategic placement of
+	BDCs, together with an implementation that localizes as much of network to client
+	interchange as possible, will help to minimize wide-area network bandwidth needs
+	(and thus costs).
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>SAM</primary></indexterm>
+<indexterm><primary>user account database</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>trigger</primary></indexterm>
+The interoperation of a PDC and its BDCs in a true Windows NT4 environment is worth
+mentioning here. The PDC contains the master copy of the SAM. In the event that an
+administrator makes a change to the user account database while physically present
+on the local network that has the PDC, the change will likely be made directly to
+the PDC instance of the master copy of the SAM. In the event that this update may
+be performed in a branch office, the change will likely be stored in a delta file
+on the local BDC. The BDC will then send a trigger to the PDC to commence the process
+of SAM synchronization. The PDC will then request the delta from the BDC and apply
+it to the master SAM. The PDC will then contact all the BDCs in the domain and
+trigger them to obtain the update and then apply that to their own copy of the SAM.
+</para>
+
+<para>
+<indexterm><primary>SAM</primary><secondary>replication</secondary></indexterm>
+<indexterm><primary>SAM</primary><secondary>delta file</secondary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+Samba-3 cannot participate in true SAM replication and is therefore not able to
+employ precisely the same protocols used by MS Windows NT4. A Samba-3 BDC will
+not create SAM update delta files. It will not interoperate with a PDC (NT4 or Samba)
+to synchronize the SAM from delta files that are held by BDCs.
+</para>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+Samba-3 cannot function as a BDC to an MS Windows NT4 PDC, and Samba-3 cannot
+function correctly as a PDC to an MS Windows NT4 BDC. Both Samba-3 and MS Windows
+NT4 can function as a BDC to its own type of PDC.
+</para>
+
+<para>
+<indexterm><primary>SAM</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>domain security</primary></indexterm>
+The BDC is said to hold a <emphasis>read-only</emphasis> of the SAM from which
+it is able to process network logon requests and authenticate users. The BDC can
+continue to provide this service, particularly while, for example, the wide-area
+network link to the PDC is down. A BDC plays a very important role in both the
+maintenance of domain security as well as in network integrity.
+</para>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>promoted</primary></indexterm>
+<indexterm><primary>demoted</primary></indexterm>
+<indexterm><primary>reconfiguration</primary></indexterm>
+In the event that the NT4 PDC should need to be taken out of service, or if it dies, one of the NT4 BDCs can
+be promoted to a PDC. If this happens while the original NT4 PDC is online, it is automatically demoted to an
+NT4 BDC. This is an important aspect of domain controller management. The tool that is used to effect a
+promotion or a demotion is the Server Manager for Domains. It should be noted that Samba-3 BDCs cannot be
+promoted in this manner because reconfiguration of Samba requires changes to the &smb.conf; file. It is easy
+enough to manuall change the &smb.conf; file and then restart relevant Samba network services.
+</para>
+
+<sect3>
+<title>Example PDC Configuration</title>
+
+<para>
+<indexterm><primary>domain logon</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+Beginning with Version 2.2, Samba officially supports domain logons for all current Windows clients, including
+Windows NT4, 2003, and XP Professional. For Samba to be enabled as a PDC, some parameters in the
+<smbconfsection name="[global]"/> section of the &smb.conf; have to be set.  Refer to <link
+linkend="minimalPDC">the Minimal smb.conf for a PDC in Use with a BDC &smbmdash; LDAP Server on PDC
+section</link> for an example of the minimum required settings.
+</para>
+
+<example id="minimalPDC">
+<title>Minimal smb.conf for a PDC in Use with a BDC &smbmdash; LDAP Server on PDC</title>
+<smbconfblock>
+<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
+<smbconfoption name="passdb backend">ldapsam://localhost:389</smbconfoption>
+<smbconfoption name="domain master">yes</smbconfoption>
+<smbconfoption name="domain logons">yes</smbconfoption>
+<smbconfoption name="ldap suffix">dc=quenya,dc=org</smbconfoption>
+<smbconfoption name="ldap user suffix">ou=Users</smbconfoption>
+<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+<smbconfoption name="ldap machine suffix">ou=Computers</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=sambadmin,dc=quenya,dc=org</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>profile path</primary></indexterm>
+<indexterm><primary>home drive</primary></indexterm>
+Several other things like a <smbconfsection name="[homes]"/> and a <smbconfsection name="[netlogon]"/> share
+also need to be set along with settings for the profile path, the user's home drive, and so on. This is not
+covered in this chapter; for more information please refer to <link linkend="samba-pdc">Domain Control</link>.
+Refer to <link linkend="samba-pdc">the Domain Control chapter</link> for specific recommendations for PDC
+configuration. Alternately, fully documented working example network configurations using OpenLDAP and Samba
+as available in the <ulink url="http://www.samba.org/samba/docs/Samba3-ByExample">book</ulink> <quote>Samba-3
+by Example</quote> that may be obtained from local and on-line book stores.
+</para>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>LDAP Configuration Notes</title>
+
+<para>
+<indexterm><primary>LDAP</primary><secondary>master</secondary></indexterm>
+<indexterm><primary>LDAP</primary><secondary>slave</secondary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+When configuring a master and a slave LDAP server, it is advisable to use the master LDAP server
+for the PDC and slave LDAP servers for the BDCs. It is not essential to use slave LDAP servers; however,
+many administrators will want to do so in order to provide redundant services. Of course, one or more BDCs
+may use any slave LDAP server. Then again, it is entirely possible to use a single LDAP server for the
+entire network.
+</para>
+
+<para>
+<indexterm><primary>LDAP</primary><secondary>master</secondary></indexterm>
+<indexterm><primary>LDAP</primary><secondary>server</secondary></indexterm>
+<indexterm><primary>CN</primary></indexterm>
+<indexterm><primary>DN</primary></indexterm>
+<indexterm><primary>RFC2830</primary></indexterm>
+When configuring a master LDAP server that will have slave LDAP servers, do not forget to configure this in
+the <filename>/etc/openldap/slapd.conf</filename> file. It must be noted that the DN of a server certificate
+must use the CN attribute to name the server, and the CN must carry the servers' fully qualified domain name.
+Additional alias names and wildcards may be present in the subjectAltName certificate extension. More details
+on server certificate names are in RFC2830.
+</para>
+
+<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>transport layer security</primary><see>TLS</see></indexterm>
+<indexterm><primary>/etc/ssl/certs/slapd.pem</primary></indexterm>
+<indexterm><primary>slapd.pem</primary></indexterm>
+<indexterm><primary>Red Hat Linux</primary></indexterm>
+It does not really fit within the scope of this document, but a working LDAP installation is basic to
+LDAP-enabled Samba operation. When using an OpenLDAP server with Transport Layer Security (TLS), the machine
+name in <filename>/etc/ssl/certs/slapd.pem</filename> must be the same as in
+<filename>/etc/openldap/sldap.conf</filename>. The Red Hat Linux startup script creates the
+<filename>slapd.pem</filename> file with hostname <quote>localhost.localdomain.</quote> It is impossible to
+access this LDAP server from a slave LDAP server (i.e., a Samba BDC) unless the certificate is re-created with
+a correct hostname.
+</para>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>machine account</primary></indexterm>
+<indexterm><primary>credentials</primary></indexterm>
+<indexterm><primary>replication</primary></indexterm>
+<indexterm><primary>duplicate</primary></indexterm>
+Do not install a Samba PDC so that is uses an LDAP slave server. Joining client machines to the domain
+will fail in this configuration because the change to the machine account in the LDAP tree must take place on
+the master LDAP server. This is not replicated rapidly enough to the slave server that the PDC queries. It
+therefore gives an error message on the client machine about not being able to set up account credentials. The
+machine account is created on the LDAP server, but the password fields will be empty.  Unfortunately, some
+sites are unable to avoid such configurations, and these sites should review the <smbconfoption name="ldap
+replication sleep"/> parameter, intended to slow down Samba sufficiently for the replication to catch up.
+This is a kludge, and one that the administrator must manually duplicate in any scripts (such as the
+<smbconfoption name="add machine script"/>) that they use.
+</para>
+
+<para>
+Possible PDC/BDC plus LDAP configurations include:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	PDC+BDC -> One Central LDAP Server.
+	</para></listitem>
+	<listitem><para>
+	PDC -> LDAP master server, BDC -> LDAP slave server.
+	</para></listitem>
+	<listitem><para>
+	PDC -> LDAP master, with secondary slave LDAP server.
+	</para><para>
+	BDC -> LDAP master, with secondary slave LDAP server.
+	</para></listitem>
+	<listitem><para>
+	PDC -> LDAP master, with secondary slave LDAP server.
+	</para><para>
+	BDC -> LDAP slave server, with secondary master LDAP server.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+In order to have a fallback configuration (secondary) LDAP server, you would specify
+the secondary LDAP server in the &smb.conf; file as shown in <link linkend="mulitldapcfg">the Multiple LDAP
+Servers in &smb.conf; example</link>.
+</para>
+
+<example id="mulitldapcfg">
+<title>Multiple LDAP Servers in &smb.conf;</title>
+<smbconfblock>
+<smbconfoption name="passdb backend">ldapsam:"ldap://master.quenya.org ldap://slave.quenya.org"</smbconfoption>
+</smbconfblock>
+</example>
+
+</sect2>
+
+<sect2>
+<title>Active Directory Domain Control</title>
+
+<para>
+<indexterm><primary>MS Windows 2000</primary></indexterm>
+<indexterm><primary>Active Directory</primary></indexterm>
+<indexterm><primary>directory</primary></indexterm>
+<indexterm><primary>replicated</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+As of the release of MS Windows 2000 and Active Directory, this information is now stored
+in a directory that can be replicated and for which partial or full administrative control
+can be delegated. Samba-3 is not able to be a domain controller within an Active Directory
+tree, and it cannot be an Active Directory server. This means that Samba-3 also cannot
+act as a BDC to an Active Directory domain controller.
+</para>
+
+</sect2>
+
+<sect2>
+<title>What Qualifies a Domain Controller on the Network?</title>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>NetBIOS</primary></indexterm>
+Every machine that is a domain controller for the domain MIDEARTH has to register the NetBIOS
+group name MIDEARTH&lt;1C&gt; with the WINS server and/or by broadcast on the local network.
+The PDC also registers the unique NetBIOS name MIDEARTH&lt;1B&gt; with the WINS server.
+The name type &lt;1B&gt; name is normally reserved for the Domain Master Browser (DMB), a role
+that has nothing to do with anything related to authentication, but the Microsoft domain
+implementation requires the DMB to be on the same machine as the PDC.
+</para>
+
+<para>
+<indexterm><primary>broadcast</primary></indexterm>
+<indexterm><primary>name registration</primary></indexterm>
+<indexterm><primary>SMB/CIFS</primary></indexterm>
+Where a WINS server is not used, broadcast name registrations alone must suffice. Refer to
+<link linkend="NetworkBrowsing">Network Browsing</link>,<link linkend="netdiscuss">Discussion</link>
+for more information regarding TCP/IP network protocols and how SMB/CIFS names are handled.
+</para>
+
+</sect2>
+
+<sect2>
+<title>How Does a Workstation find its Domain Controller?</title>
+
+<para>
+<indexterm><primary>locate domain controller</primary></indexterm>
+<indexterm><primary>NetBIOS</primary></indexterm>
+There are two different mechanisms to locate a domain controller: one method is used when
+NetBIOS over TCP/IP is enabled and the other when it has been disabled in the TCP/IP
+network configuration.
+</para>
+
+<para>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>broadcast messaging</primary></indexterm>
+Where NetBIOS over TCP/IP is disabled, all name resolution involves the use of DNS, broadcast
+messaging over UDP, as well as Active Directory communication technologies. In this type of
+environment all machines require appropriate DNS entries. More information may be found in
+<link linkend="adsdnstech">DNS and Active Directory</link>.
+</para>
+
+<sect3>
+<title>NetBIOS Over TCP/IP Enabled</title>
+<para>
+<indexterm><primary>Windows NT4/200x/XP</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>logon requests</primary></indexterm>
+<indexterm><primary>credentials validation</primary></indexterm>
+An MS Windows NT4/200x/XP Professional workstation in the domain MIDEARTH that wants a
+local user to be authenticated has to find the domain controller for MIDEARTH. It does this
+by doing a NetBIOS name query for the group name MIDEARTH&lt;1C&gt;. It assumes that each
+of the machines it gets back from the queries is a domain controller and can answer logon
+requests. To not open security holes, both the workstation and the selected domain controller
+authenticate each other. After that the workstation sends the user's credentials (name and
+password) to the local domain controller for validation.
+</para>
+
+</sect3>
+
+<sect3>
+<title>NetBIOS Over TCP/IP Disabled</title>
+
+<para>
+<indexterm><primary>realm</primary></indexterm>
+<indexterm><primary>logon authentication</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>_ldap._tcp.pdc._msdcs.quenya.org</primary></indexterm>
+An MS Windows NT4/200x/XP Professional workstation in the realm <constant>quenya.org</constant>
+that has a need to affect user logon authentication will locate the domain controller by 
+re-querying DNS servers for the <constant>_ldap._tcp.pdc._msdcs.quenya.org</constant> record.
+More information regarding this subject may be found in <link linkend="adsdnstech">DNS and Active Directory</link>.
+</para>
+
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Backup Domain Controller Configuration</title>
+
+<para>
+<indexterm><primary>BDC</primary></indexterm>
+The creation of a BDC requires some steps to prepare the Samba server before
+&smbd; is executed for the first time. These steps are as follows:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>private/secrets.tdb</primary></indexterm>
+	<indexterm><primary>private/MACHINE.SID</primary></indexterm>
+	<indexterm><primary>domain SID</primary></indexterm>
+	The domain SID has to be the same on the PDC and the BDC. In Samba versions pre-2.2.5, the domain SID was
+	stored in the file <filename>private/MACHINE.SID</filename>.  For all versions of Samba released since 2.2.5
+	the domain SID is stored in the file <filename>private/secrets.tdb</filename>. This file is unique to each
+	server and cannot be copied from a PDC to a BDC; the BDC will generate a new SID at startup. It will overwrite
+	the PDC domain SID with the newly created BDC SID.  There is a procedure that will allow the BDC to aquire the
+	domain SID. This is described here.
+	</para>
+
+	<para>
+	<indexterm><primary>domain SID</primary></indexterm>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>secrets.tdb</primary></indexterm>
+	<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>getsid</tertiary></indexterm>
+	To retrieve the domain SID from the PDC or an existing BDC and store it in the
+	<filename>secrets.tdb</filename>, execute:
+	</para>
+<screen>
+&rootprompt;<userinput>net rpc getsid</userinput>
+</screen>
+	</listitem>
+
+	<listitem><para>
+	<indexterm><primary>secrets.tdb</primary></indexterm>
+	<indexterm><primary>smbpasswd</primary></indexterm>
+	<indexterm><primary>LDAP administration password</primary></indexterm>
+	Specification of the <smbconfoption name="ldap admin dn"/> is obligatory.
+	This also requires the LDAP administration password to be set in the <filename>secrets.tdb</filename>
+	using the <command>smbpasswd -w <replaceable>mysecret</replaceable></command>.
+	</para></listitem>
+
+	<listitem><para>
+	The <smbconfoption name="ldap suffix"/> parameter and the <smbconfoption name="ldap idmap suffix"/>
+	parameter must be specified in the &smb.conf; file.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
+	<indexterm><primary>user database</primary></indexterm>
+	<indexterm><primary>synchronized</primary></indexterm>
+	<indexterm><primary>NIS</primary></indexterm>
+	The UNIX user database has to be synchronized from the PDC to the
+	BDC. This means that both the <filename>/etc/passwd</filename> and
+	<filename>/etc/group</filename> have to be replicated from the PDC
+	to the BDC. This can be done manually whenever changes are made. 
+	Alternately, the PDC is set up as an NIS master server and the BDC as an NIS slave
+	server. To set up the BDC as a mere NIS client would not be enough,
+	as the BDC would not be able to access its user database in case of
+	a PDC failure. NIS is by no means the only method to synchronize
+	passwords. An LDAP solution would also work.
+	</para>
+	</listitem>
+
+	<listitem><para>
+	<indexterm><primary>password database</primary></indexterm>
+	<indexterm><primary>replicated</primary></indexterm>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>smbpasswd</primary></indexterm>
+	<indexterm><primary>rsync</primary></indexterm>
+	<indexterm><primary>ssh</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	The Samba password database must be replicated from the PDC to the BDC.
+	Although it is possible to synchronize the <filename>smbpasswd</filename>
+	file with <command>rsync</command> and <command>ssh</command>, this method
+	is broken and flawed, and is therefore not recommended. A better solution
+	is to set up slave LDAP servers for each BDC and a master LDAP server for the PDC.
+	The use of rsync is inherently flawed by the fact that the data will be replicated
+	at timed intervals. There is no guarantee that the BDC will be operating at all
+	times with correct and current machine and user account information. This means that
+	this method runs the risk of users being inconvenienced by discontinuity of access
+	to network services due to inconsistent security data. It must be born in mind that
+	Windows workstations update (change) the machine trust account password at regular
+	intervals &smbmdash; administrators are not normally aware that this is happening
+	or when it takes place.
+	</para>
+
+	<para>
+	<indexterm><primary>POSIX</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>SambaSAMAccount</primary></indexterm>
+	<indexterm><primary>synchronize</primary></indexterm>
+	The use of LDAP for both the POSIX (UNIX user and group) accounts and for the
+	SambaSAMAccount data automatically ensures that all account change information
+	will be written to the shared directory. This eliminates the need for any special
+	action to synchronize account information because LDAP will meet that requirement.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>netlogon share</primary></indexterm>
+	<indexterm><primary>replicate</primary></indexterm>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>cron</primary></indexterm>
+	<indexterm><primary>rsync</primary></indexterm>
+	The netlogon share has to be replicated from the PDC to the BDC. This can be done manually whenever login
+	scripts are changed, or it can be done automatically using a <command>cron</command> job that will replicate
+	the directory structure in this share using a tool like <command>rsync</command>. The use of
+	<command>rsync</command> for replication of the netlogon data is not critical to network security and is one
+	that can be manually managed given that the administrator will make all changes to the netlogon share as part
+	of a conscious move.
+	</para></listitem>
+
+</itemizedlist>
+
+<sect2>
+<title>Example Configuration</title>
+
+<para>
+Finally, the BDC has to be capable of being found by the workstations. This can be done by configuring the
+Samba &smb.conf; file <smbconfsection name="[global]"/> section as shown in <link linkend="minim-bdc">Minimal
+Setup for Being a BDC</link>.
+</para>
+
+<example id="minim-bdc">
+<title>Minimal Setup for Being a BDC</title>
+<smbconfblock>
+<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
+<smbconfoption name="passdb backend">ldapsam:ldap://slave-ldap.quenya.org</smbconfoption>
+<smbconfoption name="domain master">no</smbconfoption>
+<smbconfoption name="domain logons">yes</smbconfoption>
+<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
+<smbconfoption name="ldap user suffix">ou=Users</smbconfoption>
+<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+<smbconfoption name="ldap machine suffix">ou=Computers</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=sambadmin,dc=quenya,dc=org</smbconfoption>
+<smbconfoption name="idmap backend">ldap:ldap://master-ldap.quenya.org</smbconfoption>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+Fully documented working example network configurations using OpenLDAP and Samba
+as available in the <ulink url="http://www.samba.org/samba/docs/Samba3-ByExample">book</ulink> <quote>Samba-3
+by Example</quote> that may be obtained from local and on-line book stores.
+</para>
+
+<para>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>NetBIOS</primary></indexterm>
+<indexterm><primary>group</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+This configuration causes the BDC to register only the name MIDEARTH&lt;1C&gt; with the WINS server. This is
+not a problem, as the name MIDEARTH&lt;1C&gt; is a NetBIOS group name that is meant to be registered by more
+than one machine. The parameter <smbconfoption name="domain master">no</smbconfoption> forces the BDC not to
+register MIDEARTH&lt;1B&gt;, which is a unique NetBIOS name that is reserved for the PDC.
+</para>
+
+<para>
+<indexterm><primary>idmap backend</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>redirect</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>LDAP database</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>nss_ldap</primary></indexterm>
+The <parameter>idmap backend</parameter> will redirect the <command>winbindd</command> utility to use the LDAP
+database to store all mappings for Windows SIDs to  UIDs and GIDs for UNIX accounts in a repository that is
+shared. The BDC will however depend on local resolution of UIDs and GIDs via NSS and the
+<command>nss_ldap</command> utility.
+</para>
+
+<note><para>
+<indexterm><primary>Server Type</primary><secondary>Domain Member</secondary></indexterm>
+<indexterm><primary>ID mapping</primary></indexterm>
+<indexterm><primary>domain member server</primary></indexterm>
+<indexterm><primary>idmap backend</primary></indexterm>
+Samba-3 has introduced a new ID mapping facility. One of the features of this facility is that it
+allows greater flexibility in how user and group IDs are handled in respect to NT domain user and group
+SIDs. One of the new facilities provides for explicitly ensuring that UNIX/Linux UID and GID values
+will be consistent on the PDC, all BDCs, and all domain member servers. The parameter that controls this
+is called <parameter>idmap backend</parameter>. Please refer to the man page for &smb.conf; for more information
+regarding its behavior.
+</para></note>
+
+<para>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>domain member servers</primary></indexterm>
+The use of the <smbconfoption name="idmap backend">ldap:ldap://master.quenya.org</smbconfoption>
+option on a BDC only makes sense where ldapsam is used on a PDC. The purpose of an LDAP-based idmap backend is
+also to allow a domain member (without its own passdb backend) to use winbindd to resolve Windows network users
+and groups to common UID/GIDs. In other words, this option is generally intended for use on BDCs and on domain
+member servers.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+<indexterm><primary>domain control</primary></indexterm>
+Domain control was a new area for Samba, but there are now many examples that we may refer to.
+Updated information will be published as they become available and may be found in later Samba releases or
+from the Samba Web <ulink url="http://samba.org">site</ulink>; refer in particular to the
+<filename>WHATSNEW.txt</filename> in the Samba release tarball. The book, <quote>Samba-3 by Example</quote>
+documents well tested and proven configuration examples. You can obtain a copy of this
+<ulink url="http://www.samba.org/samba/docs/Samba3-ByExample.pdf">book</ulink> for the Samba web site.
+</para>
+
+<sect2>
+<title>Machine Accounts Keep Expiring</title>
+
+<para>
+<indexterm><primary>Machine Trust Accounts</primary></indexterm>
+<indexterm><primary>passdb</primary></indexterm>
+<indexterm><primary>SAM</primary></indexterm>
+<indexterm><primary>Local Machine Trust Account</primary></indexterm>
+This problem will occur when the passdb (SAM) files are copied  from a central
+server but the local BDC is acting as a PDC. This results in the application of
+Local Machine Trust Account password updates to the local SAM. Such updates 
+are not copied back to the central server. The newer machine account password is then
+overwritten when the SAM is recopied from the PDC. The result is that the domain member machine
+on startup will find that its passwords do not match the one now in the database, and
+since the startup security check will now fail, this machine will not allow logon attempts
+to proceed and the account expiry error will be reported.
+</para>
+
+<para>
+The solution is to use a more robust passdb backend, such as the ldapsam backend, setting up
+a slave LDAP server for each BDC and a master LDAP server for the PDC.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Can Samba Be a Backup Domain Controller to an NT4 PDC?</title>
+
+<para>
+<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
+<indexterm><primary>SAM</primary></indexterm>
+No. The native NT4 SAM replication protocols have not yet been fully implemented.
+</para>
+
+<para>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>logon requests</primary></indexterm>
+Can I get the benefits of a BDC with Samba?  Yes, but only to a Samba PDC.The
+main reason for implementing a BDC is availability. If the PDC is a Samba
+machine, a second Samba machine can be set up to service logon requests whenever
+the PDC is down.
+</para>
+
+</sect2>
+
+<sect2>
+<title>How Do I Replicate the smbpasswd File?</title>
+
+<para>
+<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>SAM</primary></indexterm>
+Replication of the smbpasswd file is sensitive. It has to be done whenever changes
+to the SAM are made. Every user's password change is done in the smbpasswd file and
+has to be replicated to the BDC. So replicating the smbpasswd file very often is necessary.
+</para>
+
+<para>
+<indexterm><primary>plaintext password</primary></indexterm>
+<indexterm><primary>ssh</primary></indexterm>
+<indexterm><primary>rsync</primary></indexterm>
+As the smbpasswd file contains plaintext password equivalents, it must not be
+sent unencrypted over the wire. The best way to set up smbpasswd replication from
+the PDC to the BDC is to use the utility rsync. rsync can use ssh as a transport.
+<command>ssh</command> itself can be set up to accept <emphasis>only</emphasis>
+<command>rsync</command> transfer without requiring the user to type a password.
+</para>
+
+<para>
+<indexterm><primary>machine trust accounts</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+As said a few times before, use of this method is broken and flawed. Machine trust 
+accounts will go out of sync, resulting in a broken domain. This method is
+<emphasis>not</emphasis> recommended. Try using LDAP instead.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Can I Do This All with LDAP?</title>
+
+<para>
+<indexterm><primary>pdb_ldap</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+The simple answer is yes. Samba's pdb_ldap code supports binding to a replica
+LDAP server and will also follow referrals and rebind to the master if it ever
+needs to make a modification to the database. (Normally BDCs are read-only, so
+this will not occur often).
+</para>
+
+</sect2>
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Backup.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Backup.xml
new file mode 100644
index 00000000000..ede68229bc6
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Backup.xml
@@ -0,0 +1,241 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="Backup">
+<chapterinfo>
+	&author.jht;
+</chapterinfo>
+
+<title>Backup Techniques</title>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>backup</primary></indexterm>
+<indexterm><primary>UNIX system files</primary></indexterm>
+<indexterm><primary>system tools</primary></indexterm>
+<indexterm><primary>Samba mailing lists</primary></indexterm>
+The Samba project is over 10 years old. During the early history
+of Samba, UNIX administrators were its key implementors. UNIX administrators
+use UNIX system tools to backup UNIX system files. Over the past
+4 years, an increasing number of Microsoft network administrators have
+taken an interest in Samba. This is reflected in the questions about backup
+in general on the Samba mailing lists.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Discussion of Backup Solutions</title>
+
+<para>
+<indexterm><primary>Meccano set</primary></indexterm>
+<indexterm><primary>training course</primary></indexterm>
+During discussions at a Microsoft Windows training course, one of
+the pro-UNIX delegates stunned the class when he pointed out that Windows
+NT4 is limiting compared with UNIX. He likened UNIX to a Meccano set
+that has an unlimited number of tools that are simple, efficient,
+and, in combination, capable of achieving any desired outcome.
+</para>
+
+<para>
+<indexterm><primary>networking advocates</primary></indexterm>
+<indexterm><primary>clear purpose preferred</primary></indexterm>
+One of the Windows networking advocates retorted that if she wanted a
+Meccano set, she would buy one. She made it clear that a complex single
+tool that does more than is needed but does it with a clear purpose and
+intent is preferred by some like her.
+</para>
+
+<para>
+<indexterm><primary>due diligence</primary></indexterm>
+<indexterm><primary>research</primary></indexterm>
+<indexterm><primary>backup solution</primary></indexterm>
+Please note that all information here is provided as is and without recommendation
+of fitness or suitability. The network administrator is strongly encouraged to
+perform due diligence research before implementing any backup solution, whether free
+software or commercial.
+</para>
+
+<para>
+A useful Web site I recently stumbled across that you might like to refer to
+is located at <ulink noescape="1" url="http://www.allmerchants.com/Software/Backup_Software/">
+www.allmerchants.com</ulink>.
+</para>
+
+<para>
+The following three free software projects might also merit consideration.
+</para>
+
+	<sect2>
+	<title>BackupPC</title>
+
+
+	<para>
+	<indexterm><primary>BackupPC</primary></indexterm>
+<indexterm><primary>rsync</primary></indexterm>
+<indexterm><primary>rsyncd</primary></indexterm>
+	BackupPC version 2.0.0 has been released on <ulink url="http://backuppc.sourceforge.net">SourceForge</ulink>.
+	 New features include support for <command>rsync/rsyncd</command> and internationalization of the CGI interface
+	(including English, French, Spanish, and German).
+	</para>
+
+	<para>
+<indexterm><primary>BackupPC</primary></indexterm>
+<indexterm><primary>laptops</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>smbclient</primary></indexterm>
+<indexterm><primary>tar</primary></indexterm>
+<indexterm><primary>rsh</primary></indexterm>
+<indexterm><primary>ssh</primary></indexterm>
+<indexterm><primary>rsync</primary></indexterm>
+	BackupPC is a high-performance Perl-based package for backing up Linux,
+	UNIX, and Windows PCs and laptops to a server's disk. BackupPC is highly
+	configurable and easy to install and maintain. SMB (via smbclient),
+	<command>tar</command> over <command>rsh/ssh</command>, or <command>rsync/rsyncd</command>
+	 are used to extract client data.
+	</para>
+
+	<para>
+<indexterm><primary>RAID</primary></indexterm>
+<indexterm><primary>local disk</primary></indexterm>
+<indexterm><primary>network storage</primary></indexterm>
+	Given the ever-decreasing cost of disks and RAID systems, it is now
+	practical and cost effective to backup a large number of machines onto
+	a server's local disk or network storage. This is what BackupPC does.
+	</para>
+
+	<para>
+	Key features are pooling of identical files (big savings in server disk
+	space), compression, and a comprehensive CGI interface that allows users
+	to browse backups and restore files.
+	</para>
+
+	<para>
+<indexterm><primary>GNU GPL</primary></indexterm>
+	BackupPC is free software distributed under a GNU GPL license.
+	BackupPC runs on Linux/UNIX/freenix servers and has been tested
+	on Linux, UNIX, Windows 9x/Me, Windows 98, Windows 200x, Windows XP, and Mac OSX clients.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Rsync</title>
+
+	<para>
+<indexterm><primary>rsync</primary></indexterm>
+<indexterm><primary>ftp</primary></indexterm>
+<indexterm><primary>http</primary></indexterm>
+<indexterm><primary>scp</primary></indexterm>
+<indexterm><primary>rcp</primary></indexterm>
+<indexterm><primary>checksum-search</primary></indexterm>
+	<command>rsync</command> is a flexible program for efficiently copying files or
+		directory trees.</para>
+
+	<para><command>rsync</command> has many options to select which files will be copied
+	  and how they are to be transferred. It may be used as an
+	  alternative to <command>ftp, http, scp</command>, or <command>rcp</command>.</para>
+
+	<para>
+<indexterm><primary>remote-update protocol</primary></indexterm>
+<indexterm><primary>transfer differences</primary></indexterm>
+<indexterm><primary>differences</primary></indexterm>
+	The rsync remote-update protocol allows rsync to transfer just
+	  the differences between two sets of files across the network link,
+	  using an efficient checksum-search algorithm described in the
+	  technical report that accompanies the rsync package.</para>
+
+	<para>Some of the additional features of rsync are:</para>
+
+	<itemizedlist>
+
+		<listitem>
+		  <para>
+		    Support for copying links, devices, owners, groups, and permissions.
+		  </para>
+		</listitem>
+
+		<listitem>
+		  <para>
+		    Exclude and exclude-from options are similar to GNU tar.
+		  </para>
+		</listitem>
+
+		<listitem>
+		  <para>
+		    A CVS exclude mode for ignoring the same files that CVS would ignore.
+		  </para>
+		</listitem>
+
+		<listitem>
+		  <para>
+		    Can use any transparent remote shell, including rsh or ssh.
+		  </para>
+		</listitem>
+
+		<listitem>
+		  <para>
+		    Does not require root privileges.
+		  </para>
+		</listitem>
+
+		<listitem>
+		  <para>
+		    Pipelining of file transfers to minimize latency costs.
+		  </para>
+		</listitem>
+
+		<listitem>
+		  <para>
+		    Support for anonymous or authenticated rsync servers (ideal for
+		    mirroring).
+		  </para>
+		</listitem>
+	</itemizedlist>
+
+	</sect2>
+
+	<sect2>
+	<title>Amanda</title>
+
+
+	<para>
+	<indexterm><primary>Amanda</primary></indexterm>
+<indexterm><primary>native dump</primary></indexterm>
+<indexterm><primary>GNU tar</primary></indexterm>
+	Amanda, the Advanced Maryland Automatic Network Disk Archiver, is a backup system that
+	allows the administrator of a LAN to set up a single master backup server to back up
+	multiple hosts to a single large capacity tape drive. Amanda uses native dump and/or
+	GNU tar facilities and can back up a large number of workstations running multiple
+	versions of UNIX. Recent versions can also use Samba to back up Microsoft Windows hosts.
+	</para>
+
+	<para>
+	For more information regarding Amanda, please check the <ulink url="http://www.amanda.org/">
+	www.amanda.org/ site</ulink>.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>BOBS: Browseable Online Backup System</title>
+
+	
+	<para>
+	<indexterm><primary>BOBS</primary></indexterm>
+	Browseable Online Backup System (BOBS) is a complete online backup system. Uses large
+	disks for storing backups and lets users browse the files using a Web browser. Handles
+	some special files like AppleDouble and icon files.
+	</para>
+
+	<para>
+	The home page for BOBS is located at <ulink url="http://bobs.sourceforge.net/">
+	bobs.sourceforge.net</ulink>.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Bugs.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Bugs.xml
new file mode 100644
index 00000000000..0ef2c5cc76b
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Bugs.xml
@@ -0,0 +1,287 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="bugreport">
+
+<chapterinfo>
+	&author.jht;
+	&author.jelmer;
+	&author.tridge;
+	<pubdate> 27 June 1997 </pubdate>
+</chapterinfo>
+
+<title>Reporting Bugs</title>
+
+<sect1>
+<title>Introduction</title>
+
+<para>
+<indexterm><primary>Bugzilla</primary></indexterm>
+<indexterm><primary>bug reports</primary></indexterm>
+Please report bugs using Samba's <ulink url="https://bugzilla.samba.org/">Bugzilla</ulink> facilities and take
+the time to read this file before you submit a bug report. Also, check to see if it has changed between
+releases, as we may be changing the bug reporting mechanism at some point.
+</para>
+
+<para>
+Please do as much as you can yourself to help track down the
+bug. Samba is maintained by a dedicated group of people who volunteer
+their time, skills, and efforts. We receive far more mail than
+we can possibly answer, so you have a much higher chance of a response
+and a fix if you send us a <quote>developer-friendly</quote> bug report that lets
+us fix it fast. 
+</para>
+
+<para>
+<indexterm><primary>comp.protocols.smb</primary></indexterm>
+<indexterm><primary>newsgroup</primary></indexterm>
+<indexterm><primary>configuration problem</primary></indexterm>
+If you post the bug to the comp.protocols.smb
+newsgroup or the mailing list, do not assume that we will read it. If you suspect that your 
+problem is not a bug but a configuration problem, it is better to send 
+it to the Samba mailing list, as there are thousands of other users on
+that list who may be able to help you.
+</para>
+
+<para>
+You may also like to look though the recent mailing list archives,
+which are conveniently accessible on the Samba Web pages
+at <ulink noescape="1" url="http://samba.org/samba/">http://samba.org/samba/</ulink>.
+</para>
+
+</sect1>
+
+<sect1>
+<title>General Information</title>
+
+<para>
+Before submitting a bug report, check your config for silly
+errors. Look in your log files for obvious messages that tell
+you've misconfigured something. Run testparm to check your config
+file for correct syntax.
+</para>
+
+<para>
+Have you looked through <link linkend="diagnosis">The Samba Checklist</link>? This is extremely important.
+</para>
+
+<para>
+If you include part of a log file with your bug report, then be sure to
+annotate it with exactly what you were doing on the client at the
+time and exactly what the results were.
+</para>
+
+</sect1>
+
+<sect1 id="dbglvl">
+<title>Debug Levels</title>
+
+<para>
+If the bug has anything to do with Samba behaving incorrectly as a
+server (like refusing to open a file), then the log files will probably
+be quite useful. Depending on the problem, a log level of between 3 and
+10 showing the problem may be appropriate. A higher level gives more
+detail but may use too much disk space.
+</para>
+
+<para>
+<indexterm><primary>debug level</primary></indexterm>
+<indexterm><primary>log level</primary></indexterm>
+To set the debug level, use the <smbconfoption name="log level"/> in your 
+&smb.conf;. You may also find it useful to set the log 
+level higher for just one machine and keep separate logs for each machine. 
+To do this, add the following lines to your main &smb.conf; file:
+</para>
+
+<smbconfblock>
+<smbconfoption name="log level">10</smbconfoption>
+<smbconfoption name="log file">/usr/local/samba/lib/log.%m</smbconfoption>
+<smbconfoption name="include">/usr/local/samba/lib/smb.conf.%m</smbconfoption>
+</smbconfblock>
+
+<para>
+and create a file <filename>/usr/local/samba/lib/smb.conf.<replaceable>machine</replaceable></filename> where
+<replaceable>machine</replaceable> is the name of the client you wish to debug. In that file put any
+&smb.conf; commands you want; for example, <smbconfoption name="log level"/> may be useful. This also allows
+you to experiment with different security systems, protocol levels, and so on, on just one machine.
+</para>
+
+<para>
+The &smb.conf; entry <smbconfoption name="log level"/> is synonymous with the parameter <smbconfoption
+name="debuglevel"/> that has been used in older versions of Samba and is being retained for backward
+compatibility of &smb.conf; files.
+</para>
+
+<para>
+As the <smbconfoption name="log level"/> value is increased, you will record a significantly greater level of
+debugging information. For most debugging operations, you may not need a setting higher than
+<constant>3</constant>. Nearly all bugs can be tracked at a setting of <constant>10</constant>, but be
+prepared for a large volume of log data.
+</para>
+
+	<sect2>
+	<title>Debugging-Specific Operations</title>
+
+	<para>
+<indexterm><primary>debugging</primary></indexterm>
+<indexterm><primary>logging</primary></indexterm>
+<indexterm><primary>functional components</primary></indexterm>
+<indexterm><primary>cluttering</primary></indexterm>
+	Samba-3.x permits debugging (logging) of specific functional components without unnecessarily
+	cluttering the log files with detailed logs for all operations. An example configuration to 
+	achieve this is shown in:
+	</para>
+
+<para>
+<smbconfblock>
+<smbconfoption name="log level">0 tdb:3 passdb:5 auth:4 vfs:2</smbconfoption>
+<smbconfoption name="max log size">0</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%U.%m.log</smbconfoption>
+</smbconfblock>
+</para>
+
+	<para>
+	This will cause the level of detail to be expanded to the debug class (log level) passed to
+	each functional area per the value shown above. The first value passed to the <parameter>log level</parameter>
+	of <constant>0</constant> means turn off all unnecessary debugging except the debug classes set for
+	the functional areas as specified. The table shown in <link linkend="dbgclass">Debuggable Functions</link>
+	may be used to attain very precise analysis of each SMB operation Samba is conducting.
+	</para>
+
+	<table frame="all" id="dbgclass">
+		<title>Debuggable Functions</title>
+	<tgroup cols="2" align="center">
+		<thead>
+		<row><entry>Function Name</entry><entry>Function Name</entry></row>
+		</thead>
+		<tbody>
+		<row><entry>all</entry><entry>passdb</entry></row>
+		<row><entry>tdb</entry><entry>sam</entry></row>
+		<row><entry>printdrivers</entry><entry>auth</entry></row>
+		<row><entry>lanman</entry><entry>winbind</entry></row>
+		<row><entry>smb</entry><entry>vfs</entry></row>
+		<row><entry>rpc_parse</entry><entry>idmap</entry></row>
+		<row><entry>rpc_srv</entry><entry>quota</entry></row>
+		<row><entry>rpc_cli</entry><entry>acls</entry></row>
+		</tbody>
+	</tgroup>
+	</table>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Internal Errors</title>
+
+<para>
+If you get the message <quote><errorname>INTERNAL ERROR</errorname></quote> in your log files, 
+it means that Samba got an unexpected signal while running. It is probably a
+segmentation fault and almost certainly means a bug in Samba (unless
+you have faulty hardware or system software).
+</para>
+
+<para>
+If the message came from smbd, it will probably be accompanied by
+a message that details the last SMB message received by smbd. This
+information is often useful in tracking down the problem, so please
+include it in your bug report.
+</para>
+
+<para>
+You should also detail how to reproduce the problem, if
+possible. Please make this reasonably detailed.
+</para>
+
+
+<para>
+<indexterm><primary>core files</primary></indexterm>
+You may also find that a core file appeared in a <filename>corefiles</filename>
+subdirectory of the directory where you keep your Samba log
+files. This file is the most useful tool for tracking down the bug. To
+use it, you do this:
+<indexterm><primary>gdb</primary></indexterm>
+<indexterm><primary>debug</primary></indexterm>
+<screen>
+&prompt;<userinput>gdb smbd core</userinput>
+</screen>
+</para>
+
+<para>
+<indexterm><primary>dbx</primary></indexterm>
+<indexterm><primary>stack trace</primary></indexterm>
+adding appropriate paths to smbd and core so gdb can find them. If you
+do not have gdb, try <userinput>dbx</userinput>. Then within the debugger,
+use the command <command>where</command> to give a stack trace of where the
+problem occurred. Include this in your report.
+</para>
+
+<para>
+<indexterm><primary>disass</primary></indexterm>
+If you know any assembly language, do a <command>disass</command> of the routine
+where the problem occurred (if it's in a library routine, then
+disassemble the routine that called it) and try to work out exactly
+where the problem is by looking at the surrounding code. Even if you
+do not know assembly, including this information in the bug report can be
+useful. 
+</para>
+</sect1>
+
+<sect1>
+<title>Attaching to a Running Process</title>
+
+<para>
+<indexterm><primary>PID</primary></indexterm>
+<indexterm><primary>gdb</primary></indexterm>
+<indexterm><primary>smbstatus</primary></indexterm>
+Unfortunately, some UNIXes (in particular some recent Linux kernels)
+refuse to dump a core file if the task has changed UID (which smbd
+does often). To debug with this sort of system, you could try to attach
+to the running process using
+<userinput>gdb smbd <replaceable>PID</replaceable></userinput>, where you get
+<replaceable>PID</replaceable> from <application>smbstatus</application>.
+Then use <command>c</command> to continue and try to cause the core dump
+using the client. The debugger should catch the fault and tell you
+where it occurred.
+</para>
+
+<para>
+Sometimes it is necessary to build Samba binary files that have debugging
+symbols so as to make it possible to capture enough information from a crashed
+operation to permit the Samba Team to fix the problem.
+</para>
+
+<para>
+Compile with <constant>-g</constant> to ensure you have symbols in place. 
+Add the following line to the &smb.conf; file global section:
+<screen>
+panic action = "/bin/sleep 90000"
+</screen>
+to catch any panics. If <command>smbd</command> seems to be frozen, look for any sleep
+processes. If it is not, and appears to be spinning, find the PID
+of the spinning process and type:
+<screen>
+&rootprompt; gdb /usr/local/samba/sbin/smbd
+</screen>
+<indexterm><primary>spinning process</primary></indexterm>
+then <quote>attach `pid'</quote> (of the spinning process), then type <quote>bt</quote> to
+get a backtrace to see where the smbd is in the call path.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Patches</title>
+
+
+<para>
+<indexterm><primary>diff</primary></indexterm>
+<indexterm><primary>patch</primary></indexterm>
+The best sort of bug report is one that includes a fix! If you send us
+patches, please use <userinput>diff -u</userinput> format if your version of 
+diff supports it; otherwise, use <userinput>diff -c4</userinput>. Make sure 
+you do the diff against a clean version of the source and let me know 
+exactly what version you used. 
+</para>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-CUPS-printing.xml b/docs-xml/Samba3-HOWTO/TOSHARG-CUPS-printing.xml
new file mode 100644
index 00000000000..9b12e4cac59
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-CUPS-printing.xml
@@ -0,0 +1,5237 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="CUPS-printing">
+
+<chapterinfo>
+
+	<author>
+		<firstname>Kurt</firstname><surname>Pfeifle</surname>
+		<affiliation>
+			<orgname>Danka Deutschland GmbH </orgname>
+                        <address><email>kpfeifle@danka.de</email></address>
+		</affiliation>
+	</author>
+	<author>
+		<firstname>Ciprian</firstname><surname>Vizitiu</surname>
+		<affiliation>
+			<address><email>CVizitiu@gbif.org</email></address>
+		</affiliation>
+		<contrib>drawings</contrib>
+	</author>
+
+	<author>&person.jelmer;<contrib>drawings</contrib></author>
+
+	<pubdate> (27 Jan 2004) </pubdate>
+</chapterinfo>
+
+<title>CUPS Printing Support</title>
+
+<sect1>
+
+	<title>Introduction</title>
+
+	<sect2>
+		<title>Features and Benefits</title>
+
+		<para>
+<indexterm><primary>default printing</primary></indexterm>
+		The Common UNIX Print System (<ulink url="http://www.cups.org/">CUPS</ulink>)
+		has become quite popular. All major Linux distributions now ship it as their default printing
+		system. To many, it is still a mystical tool. Mostly, it just works.  People tend to regard
+		it as a <quote>black box</quote> that they do not want to look into as long as it works. But once
+		there is a little problem, they have trouble finding out where to start debugging it. Refer to
+		<link linkend="classicalprinting">Classical Printing</link>, which contains much information
+		that is also relevant to CUPS.
+		</para>
+
+		<para>
+<indexterm><primary>CUPS</primary></indexterm>
+		CUPS sports quite a few unique and powerful features. While its basic functions may be grasped quite
+		easily, they are also new. Because it is different from other, more traditional printing systems, it is best
+		not to try to apply any prior knowledge about printing to this new system. Rather, try to understand CUPS from
+		the beginning. This documentation will lead you to a complete understanding of CUPS. Let's start with the most
+		basic things first.
+		</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Overview</title>
+
+	<para>
+<indexterm><primary>print spooling system</primary></indexterm>
+<indexterm><primary>CUPS</primary></indexterm>
+<indexterm><primary>printer management system</primary></indexterm>
+<indexterm><primary>IETF</primary></indexterm>
+<indexterm><primary>Internet Printing Protocol</primary><see>IPP</see></indexterm>
+<indexterm><primary>Internet Engineering Task Force</primary><see>IETF</see></indexterm>
+<indexterm><primary>GUI</primary></indexterm>
+<indexterm><primary>KDEPrint</primary></indexterm>
+	CUPS is more than just a print spooling system. It is a complete printer management system that
+	complies with the new Internet Printing Protocol (IPP). IPP is an industry and Internet Engineering Task Force
+	(IETF) standard for network printing. Many of its functions can be managed remotely (or locally) via a Web
+	browser (giving you platform-independent access to the CUPS print server). Additionally, it has the
+	traditional command line and several more modern GUI interfaces (GUI interfaces developed by third parties,
+	like KDE's overwhelming <ulink url="http://printing.kde.org/">KDEPrint</ulink>).
+	</para>
+
+	<para>
+<indexterm><primary>raw printers</primary></indexterm>
+<indexterm><primary>smart printers</primary></indexterm>
+	CUPS allows creation of <emphasis>raw</emphasis> printers (i.e., no print file format translation) as
+	well as <emphasis>smart</emphasis> printers (i.e., CUPS does file format conversion as required for the
+	printer). In many ways, this gives CUPS capabilities similar to the MS Windows print monitoring system. Of
+	course, if you are a CUPS advocate, you would argue that CUPS is better! In any case, let us now explore how
+	to configure CUPS for interfacing with MS Windows print clients via Samba.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Basic CUPS Support Configuration</title>
+
+	<para>
+<indexterm><primary>CUPS</primary></indexterm>
+<indexterm><primary>cupsd.conf</primary></indexterm>
+<indexterm><primary>/etc/printcap</primary></indexterm>
+<indexterm><primary>Printcap</primary></indexterm>
+<indexterm><primary>PrintcapFormat</primary></indexterm>
+Printing with CUPS in the most basic &smb.conf; setup in Samba-3.0 (as was true for 2.2.x) requires just two
+parameters: <smbconfoption name="printing">cups</smbconfoption> and <smbconfoption
+name="printcap">cups</smbconfoption>. CUPS does not need a printcap file.  However, the
+<filename>cupsd.conf</filename> configuration file knows of two related directives that control how such a
+file will be automatically created and maintained by CUPS for the convenience of third-party applications
+(example: <parameter>Printcap /etc/printcap</parameter> and <parameter>PrintcapFormat BSD</parameter>).
+Legacy programs often require the existence of a printcap file containing printer names or they will refuse to
+print. Make sure CUPS is set to generate and maintain a printcap file. For details, see <command>man
+cupsd.conf</command> and other CUPS-related documentation, like the wealth of documents regarding the CUPS
+server itself available from the <ulink noescape="1"
+url="http://localhost:631/documentation.html">CUPS</ulink> web site.
+	</para>
+
+	<sect2>
+	<title>Linking smbd with libcups.so</title>
+
+	<para>
+<indexterm><primary>libcups.so</primary></indexterm>
+	Samba has a special relationship to CUPS. Samba can be compiled with CUPS library support.
+	Most recent installations have this support enabled. By default, CUPS linking is compiled
+	into smbd and other Samba binaries. Of course, you can use CUPS even
+	if Samba is not linked against <filename>libcups.so</filename> &smbmdash; but
+	there are some differences in required or supported configuration.
+	</para>
+
+	<para>
+<indexterm><primary>libcups</primary></indexterm>
+<indexterm><primary>ldd</primary></indexterm>
+	When Samba is compiled and linked with <filename>libcups</filename>, <smbconfoption name="printcap">cups</smbconfoption>
+	uses the CUPS API to list printers, submit jobs, query queues, and so on. Otherwise it maps to the System V
+	commands with an additional <command>-oraw</command> option for printing. On a Linux
+	system, you can use the <command>ldd</command> utility to find out if smbd has been linked with the
+	libcups library (<command>ldd</command> may not be present on other OS platforms, or its function may be embodied
+	by a different command):
+<screen>
+&rootprompt;<userinput>ldd `which smbd`</userinput>
+libssl.so.0.9.6 =&gt; /usr/lib/libssl.so.0.9.6 (0x4002d000)
+libcrypto.so.0.9.6 =&gt; /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
+libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
+[....]
+</screen>
+	</para>
+
+	<para>
+<indexterm><primary>libcups.so.2</primary></indexterm>
+	The line <computeroutput>libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)</computeroutput> shows
+	there is CUPS support compiled into this version of Samba. If this is the case, and printing = cups
+	is set, then <emphasis>any otherwise manually set print command in &smb.conf; is ignored</emphasis>.
+	This is an important point to remember!
+	</para>
+
+	<tip><para> Should it be necessary, for any reason, to set your own print commands, you can do this by setting
+	<smbconfoption name="printing">sysv</smbconfoption>. However, you will lose all the benefits
+	of tight CUPS-Samba integration. When you do this, you must manually configure the printing system commands
+	(most important: 
+	<smbconfoption name="print command"/>; other commands are
+	<smbconfoption name="lppause command"/>,
+	<smbconfoption name="lpresume command"/>,
+	<smbconfoption name="lpq command"/>,
+	<smbconfoption name="lprm command"/>,
+	<smbconfoption name="queuepause command"/> and
+	<smbconfoption name="queue resume command"/>).
+	</para></tip>
+
+	</sect2>
+
+	<sect2>
+	<title>Simple &smb.conf; Settings for CUPS</title>
+
+	<para>
+	To summarize, <link linkend="cups-exam-simple">the Simplest Printing-Related 
+	&smb.conf; file</link> shows the simplest printing-related setup for &smb.conf; to 
+	enable basic CUPS support:
+	</para>
+
+	<example id="cups-exam-simple">
+	<title>Simplest Printing-Related smb.conf</title>
+	<smbconfblock>
+	<smbconfsection name="[global]"/>
+	<smbconfoption name="load printers">yes</smbconfoption>
+	<smbconfoption name="printing">cups</smbconfoption>
+	<smbconfoption name="printcap name">cups</smbconfoption>
+
+	<smbconfsection name="[printers]"/>
+	<smbconfoption name="comment">All Printers</smbconfoption>
+	<smbconfoption name="path">/var/spool/samba</smbconfoption>
+	<smbconfoption name="browseable">no</smbconfoption>
+	<smbconfoption name="public">yes</smbconfoption>
+	<smbconfoption name="guest ok">yes</smbconfoption>
+	<smbconfoption name="writable">no</smbconfoption>
+	<smbconfoption name="printable">yes</smbconfoption>
+	<smbconfoption name="printer admin">root, @ntadmins</smbconfoption>
+	</smbconfblock>
+	</example>
+
+	<para>
+<indexterm><primary>PDF</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>printer driver</primary></indexterm>
+	This is all you need for basic printing setup for CUPS. It will print all graphic, text, PDF, and PostScript
+	files submitted from Windows clients. However, most of your Windows users would not know how to send these
+	kinds of files to print without opening a GUI application. Windows clients tend to have local printer drivers
+	installed, and the GUI application's print buttons start a printer driver. Your users also rarely send files
+	from the command line. Unlike UNIX clients, they rarely submit graphic, text, or PDF formatted files directly
+	to the spooler. They nearly exclusively print from GUI applications with a <quote>printer driver</quote>
+	hooked between the application's native format and the print data stream. If the backend printer is not a
+	PostScript device, the print data stream is <quote>binary,</quote> sensible only for the target printer. Read
+	on to learn what problem this may cause and how to avoid it.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>More Complex CUPS &smb.conf; Settings</title>
+
+	<para>
+	<link linkend="overridesettings">The Overriding Global CUPS Settings for One Printer example</link> 
+	is a slightly more complex printing-related setup for &smb.conf;. It enables general CUPS printing
+	support for all printers, but defines one printer share, which is set up differently. 
+	</para>
+
+	<example id="overridesettings">
+	<title>Overriding Global CUPS Settings for One Printer</title>
+	<smbconfblock>
+	<smbconfsection name="[global]"/>
+	<smbconfoption name="printing">cups</smbconfoption>
+	<smbconfoption name="printcap name">cups</smbconfoption>
+	<smbconfoption name="load printers">yes</smbconfoption>
+
+	<smbconfsection name="[printers]"/>
+	<smbconfoption name="comment">All Printers</smbconfoption>
+	<smbconfoption name="path">/var/spool/samba</smbconfoption>
+	<smbconfoption name="public">yes</smbconfoption>
+	<smbconfoption name="guest ok">yes</smbconfoption>
+	<smbconfoption name="writable">no</smbconfoption>
+	<smbconfoption name="printable">yes</smbconfoption>
+	<smbconfoption name="printer admin">root, @ntadmins</smbconfoption>
+
+	<smbconfsection name="[special_printer]"/>
+	<smbconfoption name="comment">A special printer with his own settings</smbconfoption>
+	<smbconfoption name="path">/var/spool/samba-special</smbconfoption>
+	<smbconfoption name="printing">sysv</smbconfoption>
+	<smbconfoption name="printcap">lpstat</smbconfoption>
+	<smbconfoption name="print command">echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; echo "     `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; echo "     `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log ; rm %f </smbconfoption>
+	<smbconfoption name="public">no</smbconfoption>
+	<smbconfoption name="guest ok">no</smbconfoption>
+	<smbconfoption name="writable">no</smbconfoption>
+	<smbconfoption name="printable">yes</smbconfoption>
+	<smbconfoption name="printer admin">kurt</smbconfoption>
+	<smbconfoption name="hosts deny">0.0.0.0</smbconfoption>
+	<smbconfoption name="hosts allow">turbo_xp, 10.160.50.23, 10.160.51.60</smbconfoption>
+	</smbconfblock>
+	</example>
+
+	<para>
+	This special share is only for testing purposes. It does not write the print job to a file. It just logs the job parameters
+	known to Samba into the <filename>/tmp/smbprn.log</filename> file and deletes the job-file. Moreover, the
+	<smbconfoption name="printer admin"/> of this share is <quote>kurt</quote> (not the <quote>@ntadmins</quote> group),
+	guest access is not allowed, the share isn't published to the Network Neighborhood (so you need to know it is there), and it
+	allows access from only three hosts. To prevent CUPS from kicking in and taking over the print jobs for that share, we need to set
+	<smbconfoption name="printing">sysv</smbconfoption> and <smbconfoption name="printcap">lpstat</smbconfoption>.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Advanced Configuration</title>
+
+	<para>
+	Before we delve into all the configuration options, let us clarify a few points. <emphasis>Network printing
+	needs to be organized and set up correctly</emphasis>. This frequently doesn't happen. Legacy systems or small
+	business LAN environments often lack design and good housekeeping.
+	</para>
+
+
+	<sect2>
+	<title>Central Spooling vs. <quote>Peer-to-Peer</quote> Printing</title>
+
+
+	<para>
+<indexterm><primary>spooling</primary></indexterm>
+	<indexterm><primary>spooling</primary><secondary>central</secondary></indexterm>
+	<indexterm><primary>spooling</primary><secondary>peer-to-peer</secondary></indexterm>
+	Many small office or home networks, as well as badly organized larger environments, allow each client a direct
+	access to available network printers. This is generally a bad idea. It often blocks one client's access to the
+	printer when another client's job is printing. It might freeze the first client's application while it is
+	waiting to get rid of the job. Also, there are frequent complaints about various jobs being printed with their
+	pages mixed with each other. A better concept is the use of a print server: it routes all jobs through one
+	central system, which responds immediately, takes jobs from multiple concurrent clients, and transfers them to
+	the printer(s) in the correct order.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Raw Print Serving: Vendor Drivers on Windows Clients</title>
+
+	<para>
+	<indexterm><primary>spooling-only</primary></indexterm>
+	<indexterm><primary>raw printing</primary></indexterm>
+	Most traditionally configured UNIX print servers acting on behalf of
+	Samba's Windows clients represented a really simple setup. Their only
+	task was to manage the <quote>raw</quote> spooling of all jobs handed to them by
+	Samba. This approach meant that the Windows clients were expected to
+	prepare the print job file that is ready to be sent to the printing
+	device. In this case, a native (vendor-supplied) Windows printer driver needs to
+	be installed on each and every client for the target device.
+	</para>
+
+	<para>
+<indexterm><primary>render</primary></indexterm>
+<indexterm><primary>vendor-provided drivers</primary></indexterm>
+	It is possible to configure CUPS, Samba, and your Windows clients in the
+	same traditional and simple way. When CUPS printers are configured
+	for raw print-through mode operation, it is the responsibility of the
+	Samba client to fully render the print job (file). The file must be
+	sent in a format that is suitable for direct delivery to the
+	printer. Clients need to run the vendor-provided drivers to do
+	this. In this case, CUPS will not do any print file format conversion
+	work.
+	</para>
+
+	<para>
+	The easiest printing configuration possible is raw print-through.
+	This is achieved by installation of the printer as if it were physically
+	attached to the Windows client. You then redirect output to a raw network
+	print queue. This procedure may be followed to achieve this:
+	</para>
+
+	<procedure>
+	<title>Configuration Steps for Raw CUPS Printing Support</title>
+
+		<step><para>
+<indexterm><primary>/etc/cups/mime.types</primary></indexterm>
+		Edit <filename>/etc/cups/mime.types</filename> to uncomment the line
+		near the end of the file that has:
+<screen>
+#application/octet-...
+</screen>
+		</para></step>
+
+		<step><para>
+<indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
+		Do the same for the file <filename>/etc/cups/mime.convs</filename>.
+		</para></step>
+
+		<step><para>
+		Add a raw printer using the Web interface. Point your browser at
+		<constant>http://localhost:631</constant>. Enter Administration, and add
+		the printer following the prompts. Do not install any drivers for it.
+		Choose Raw. Choose queue name <constant>Raw Queue</constant>.
+		</para></step>
+
+		<step><para>
+		In the &smb.conf; file <constant>[printers]</constant> section add
+		<smbconfoption name="use client driver">Yes</smbconfoption>,
+		and in the <constant>[global]</constant> section add
+		<smbconfoption name="printing">CUPS</smbconfoption>, plus
+		<smbconfoption name="printcap">CUPS</smbconfoption>.
+		</para></step>
+
+		<step><para>
+		Install the printer as if it is a local printer, that is, Printing to <constant>LPT1:</constant>.
+		</para></step>
+
+		<step><para>
+		Edit the configuration under the <guimenu>Detail</guimenu> tab and create a
+		<constant>local port</constant> that points to the raw printer queue that
+		you have configured above. Example: <constant>\\server\raw_q</constant>.
+		Here, the name <constant>raw_q</constant> is the name you gave the print
+		queue in the CUPS environment.
+		</para></step>
+	</procedure>
+
+	</sect2>
+
+	<sect2>
+	<title>Installation of Windows Client Drivers</title>
+
+	<para>
+	The printer drivers on the Windows clients may be installed
+	in two functionally different ways:
+	</para>
+
+	<itemizedlist>
+	<listitem><para>Manually install the drivers locally on each client,
+	one by one; this yields the old LanMan style
+	printing and uses a <filename>\\sambaserver\printershare</filename>
+	type of connection.</para></listitem>
+
+
+	<listitem><para>
+	<indexterm><primary>point 'n' print</primary></indexterm>
+			Deposit and prepare the drivers (for later download) on
+			the print server (Samba); this enables the clients to use
+	<quote>Point'n'Print</quote> to get drivers semi-automatically installed the
+	first time they access the printer; with this method NT/200x/XP
+	clients use the <emphasis>SPOOLSS/MS-RPC</emphasis>
+	type printing calls.</para></listitem>
+	</itemizedlist>
+
+	<para>
+	The second method is recommended for use over the first.
+	</para>
+	</sect2>
+
+	<sect2 id="cups-raw">
+	<title>Explicitly Enable <quote>raw</quote> Printing for <emphasis>application/octet-stream</emphasis></title>
+
+
+	<para>
+	<indexterm><primary>application/octet-stream</primary></indexterm>
+	<indexterm><primary>raw printing</primary></indexterm>
+	<indexterm><primary>MIME</primary><secondary>raw</secondary></indexterm>
+	If you use the first option (drivers are installed on the client
+	side), there is one setting to take care of: CUPS needs to be told
+	that it should allow <quote>raw</quote> printing of deliberate (binary) file
+	formats. The CUPS files that need to be correctly set for raw mode
+	printers to work are:
+	</para>
+
+	<itemizedlist>
+		<listitem><para><filename>/etc/cups/mime.types</filename></para></listitem>
+		<listitem><para><filename>/etc/cups/mime.convs</filename></para></listitem>
+	</itemizedlist>
+
+	<para>
+	Both contain entries (at the end of the respective files) that must be uncommented to allow RAW mode
+	operation.  In <filename>/etc/cups/mime.types</filename>, make sure this line is present:
+<programlisting>
+application/octet-stream
+</programlisting>
+	<indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
+	<indexterm><primary>/etc/cups/mime.types</primary></indexterm>
+	In <filename>/etc/cups/mime.convs</filename>, have this line:
+	<indexterm><primary>application/vnd.cups-raw</primary></indexterm>
+<programlisting>
+application/octet-stream   application/vnd.cups-raw   0   - 
+</programlisting>
+	If these two files are not set up correctly for raw Windows client
+	printing, you may encounter the dreaded <computeroutput>Unable to
+	convert file 0</computeroutput> in your CUPS <filename>error_log</filename> file. 
+	</para>
+
+	<note><para>
+	Editing the <filename>mime.convs</filename> and the <filename>mime.types</filename> file does
+	not <emphasis>enforce</emphasis> <quote>raw</quote> printing, it only <emphasis>allows</emphasis> it.
+	</para></note>
+
+	<formalpara><title>Background</title>
+
+	<para>
+	<indexterm><primary>application/octet-stream</primary></indexterm>
+<indexterm><primary>MIME type</primary></indexterm>
+	That CUPS is a more security-aware printing system than traditional ones does not by default allow a user to
+	send deliberate (possibly binary) data to printing devices. This could be easily abused to launch a
+	<quote>Denial of Service</quote> attack on your printer(s), causing at least the loss of a lot of paper and
+	ink. <quote>Unknown</quote> data are tagged by CUPS as <parameter>MIME type: application/octet-stream</parameter>
+	and not allowed to go to the printer. By default, you can only send other (known) MIME types <quote>raw.</quote>
+	Sending data <quote>raw</quote> means that CUPS does not try to convert them and passes them to the printer
+	untouched.
+	</para>
+	</formalpara>
+
+	<para>
+	This is all you need to know to get the CUPS/Samba combo printing
+	<quote>raw</quote> files prepared by Windows clients, which have vendor drivers
+	locally installed. If you are not interested in background information about
+	more advanced CUPS/Samba printing, simply skip the remaining sections
+	of this chapter.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Driver Upload Methods</title>
+
+	<para>
+	This section describes three familiar methods, plus one new one, by which
+	printer drivers may be uploaded.
+	</para>
+
+	<para>
+	<indexterm><primary>point'n'print</primary></indexterm>
+	If you want to use the MS-RPC-type printing, you must upload the
+	drivers onto the Samba server first (<smbconfsection name="[print$]"/>
+	share). For a discussion on how to deposit printer drivers on the
+	Samba host (so the Windows clients can download and use them via
+	<quote>Point'n'Print</quote>), please refer to the <link linkend="classicalprinting">Classical Printing
+	chapter</link> of this book. There you will find a description or reference to
+	three methods of preparing the client drivers on the Samba server:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		<indexterm><primary>add printer wizard</primary></indexterm>
+		The GUI, <quote>Add Printer Wizard</quote> <emphasis>upload-from-a-Windows-client</emphasis> method.
+		</para></listitem>
+
+		<listitem><para>
+		The command line, <quote>smbclient/rpcclient</quote> upload-from-a-UNIX-workstation method.
+		</para></listitem>
+
+		<listitem><para>
+		<indexterm><primary>imprints</primary></indexterm>
+		The Imprints tool set method.
+		</para></listitem>
+	</itemizedlist>
+
+	<para> 
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+	These three methods apply to CUPS all the same. The <command>cupsaddsmb</command> utility is a new and more
+	convenient way to load the Windows drivers into Samba and is provided if you use CUPS.
+	</para>
+
+	<para>
+	<command>cupsaddsmb</command> is discussed in much detail later in this chapter. But we first
+	explore the CUPS filtering system and compare the Windows and UNIX printing architectures.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Advanced Intelligent Printing with PostScript Driver Download</title>
+
+	<para>
+	<indexterm><primary>PostScript</primary><seealso>Ghostscript</seealso></indexterm>
+	We now know how to set up a <quote>dump</quote> print server, that is, a server that spools
+	print jobs <quote>raw</quote>, leaving the print data untouched.
+	</para>
+
+	<para>
+	You might need to set up CUPS in a smarter way. The reasons could be manifold:
+	</para>
+
+<indexterm><primary>print statistics</primary></indexterm>
+<indexterm><primary>average print run</primary></indexterm>
+<indexterm><primary>print quota</primary></indexterm>
+	<itemizedlist>
+	<listitem><para>Maybe your boss wants to get monthly statistics: Which
+	printer did how many pages? What was the average data size of a job?
+	What was the average print run per day? What are the typical hourly
+	peaks in printing? Which department prints how much?</para></listitem>
+
+	<listitem><para>Maybe you are asked to set up a print quota system:
+	Users should not be able to print more jobs once they have surpassed
+	a given limit per period.</para></listitem>
+
+	<listitem><para>Maybe your previous network printing setup is a mess
+	and must be re-organized from a clean beginning.</para></listitem>
+
+	<listitem><para>Maybe you are experiencing too many <quote>blue screens</quote>
+	originating from poorly debugged printer drivers running in NT <quote>kernel mode</quote>?</para></listitem>
+	</itemizedlist>
+
+	<para>
+	These goals cannot be achieved by a raw print server. To build a
+	server meeting these requirements, you'll first need to learn
+	how CUPS works and how you can enable its features.
+	</para>
+
+	<para>
+	What follows is the comparison of some fundamental concepts for
+	Windows and UNIX printing, then a description of the
+	CUPS filtering system, how it works, and how you can tweak it.
+	</para>
+
+	<sect2 id="gdipost">
+	<title>GDI on Windows, PostScript on UNIX</title>
+
+	<para>
+	<indexterm><primary>GDI</primary></indexterm>
+	<indexterm><primary>PostScript</primary></indexterm>
+	Network printing is one of the most complicated and error-prone
+	day-to-day tasks any user or administrator may encounter. This is
+	true for all OS platforms, and there are reasons it is so.
+	</para>
+
+
+	<para>
+	<indexterm><primary>PCL</primary></indexterm>
+	<indexterm><primary>PDL</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>Adobe</primary></indexterm>
+<indexterm><primary>page description languages</primary><see>PDL</see></indexterm>
+	You can't expect to throw just any file format at a printer and have it get printed. A file format conversion
+	must take place. The problem is that there is no common standard for print file formats across all
+	manufacturers and printer types. While PostScript (trademark held by Adobe) and, to an extent, PCL (trademark
+	held by Hewlett-Packard) have developed into semi-official <quote>standards</quote> by being the most widely
+	used page description languages (PDLs), there are still many manufacturers who <quote>roll their own</quote>
+	(their reasons may be unacceptable license fees for using printer-embedded PostScript interpreters, and so on).
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Windows Drivers, GDI, and EMF</title>
+
+	<para>
+	<indexterm><primary>GDI</primary></indexterm>
+	<indexterm><primary>EMF</primary></indexterm>
+	<indexterm><primary>WYSIWYG</primary></indexterm>
+<indexterm><primary>Enhanced MetaFile</primary><see>EMF</see></indexterm>
+	In Windows OS, the format conversion job is done by the printer drivers. On MS Windows OS platforms all
+	application programmers have at their disposal a built-in API, the graphical device interface (GDI), as part
+	and parcel of the OS itself to base themselves on. This GDI core is used as one common unified ground for all
+	Windows programs to draw pictures, fonts, and documents <emphasis>on screen</emphasis> as well as <emphasis>on
+	paper</emphasis> (print). Therefore, printer driver developers can standardize on a well-defined GDI output
+	for their own driver input. Achieving WYSIWYG (What You See Is What You Get) is relatively easy, because the
+	on-screen graphic primitives, as well as the on-paper drawn objects, come from one common source. This source,
+	the GDI, often produces a file format called Enhanced MetaFile (EMF). The EMF is processed by the printer
+	driver and converted to the printer-specific file format.
+	</para>
+
+	<note><para>
+	<indexterm><primary>PDF</primary></indexterm>
+<indexterm><primary>Xprint</primary></indexterm>
+<indexterm><primary>core graphic engine</primary></indexterm>
+	To the GDI foundation in MS Windows, Apple has chosen to put paper and screen output on a common foundation
+	for its (BSD-UNIX-based, did you know?) Mac OS X and Darwin operating <indexterm><primary>X Window
+	System</primary></indexterm> <indexterm><primary>PostScript</primary></indexterm>
+	<indexterm><primary>PCL</primary></indexterm> <indexterm><primary>Xprint</primary></indexterm> systems.
+	Apple's <emphasis>core graphic engine</emphasis> uses a <emphasis>PDF</emphasis> derivative for all display work.
+	</para></note>
+
+	<para>
+	The example in <link linkend="1small">Windows Printing to a Local Printer</link> illustrates local Windows
+	printing.
+	</para>
+
+	<figure id="1small">
+		<title>Windows Printing to a Local Printer.</title>
+		<imagefile>1small</imagefile>
+	</figure>
+
+	</sect2>
+
+	<sect2>
+	<title>UNIX Printfile Conversion and GUI Basics</title>
+
+	<para>
+	<indexterm><primary>X Window System</primary></indexterm>
+	<indexterm><primary>PostScript</primary></indexterm>
+	<indexterm><primary>PCL</primary></indexterm>
+	<indexterm><primary>Xprint</primary></indexterm>
+	In UNIX and Linux, there is no comparable layer built into the OS kernel(s) or the X (screen display) server.
+	Every application is responsible for itself to create its print output. Fortunately, most use PostScript and
+	that at least gives some common ground. Unfortunately, there are many different levels of quality for this
+	PostScript. And worse, there is a huge difference (and no common root) in the way the same document is
+	displayed on screen and how it is presented on paper. WYSIWYG is more difficult to achieve. This goes back to
+	the time, decades ago, when the predecessors of X.org, designing the UNIX foundations and protocols for
+	graphical user interfaces, refused to take responsibility for <quote>paper output</quote>, as some had
+	demanded at the time, and restricted itself to <quote>on-screen only.</quote> (For some years now, the
+	<quote>Xprint</quote> project has been under development, attempting to build printing support into the X
+	framework, including a PostScript and a PCL driver, but it is not yet ready for prime time.) You can see this
+	unfavorable inheritance up to the present day by looking into the various <quote>font</quote> directories on
+	your system; there are separate ones for fonts used for X display and fonts to be used on paper.
+	</para>
+
+	<formalpara>
+	<title>Background</title>
+
+	<para>
+	<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>color</primary></indexterm>
+<indexterm><primary>linewidth</primary></indexterm>
+<indexterm><primary>scale</primary></indexterm>
+<indexterm><primary>distort</primary></indexterm>
+<indexterm><primary>rotate</primary></indexterm>
+<indexterm><primary>shift</primary></indexterm>
+<indexterm><primary>raster images</primary></indexterm>
+<indexterm><primary>display PostScript</primary></indexterm>
+<indexterm><primary>graphical objects</primary></indexterm>
+	The PostScript programming language is an <quote>invention</quote> by Adobe, but its specifications have been
+	published extensively. Its strength lies in its powerful abilities to describe graphical objects (fonts,
+	shapes, patterns, lines, curves, and dots), their attributes (color, linewidth), and the way to manipulate
+	(scale, distort, rotate, shift) them. Because of its open specification, anybody with the skill can start
+	writing his or her own implementation of a PostScript interpreter and use it to display PostScript files on
+	screen or on paper. Most graphical output devices are based on the concept of <quote>raster images</quote> or
+	<quote>pixels</quote> (one notable exception is pen plotters). Of course, you can look at a PostScript file in
+	its textual form and you will be reading its PostScript code, the language instructions that need to be
+	interpreted by a rasterizer. Rasterizers produce pixel images, which may be displayed on screen by a viewer
+	program or on paper by a printer.
+	</para>
+	</formalpara>
+	</sect2>
+
+	<sect2 id="post-and-ghost">
+	<title>PostScript and Ghostscript</title>
+
+	<para>
+	<indexterm><primary>PostScript</primary></indexterm>
+	<indexterm><primary>GhostScript</primary><seealso>PostScript</seealso></indexterm>
+	<indexterm><primary>PostScript</primary><secondary>RIP</secondary></indexterm>
+<indexterm><primary>PostScript interpreter</primary></indexterm>
+<indexterm><primary>raster image processor</primary><see>RIP</see></indexterm>
+	So UNIX is lacking a common ground for printing on paper and displaying on screen. Despite this unfavorable
+	legacy for UNIX, basic printing is fairly easy if you have PostScript printers at your disposal. The reason is
+	that these devices have a built-in PostScript language <quote>interpreter,</quote> also called a raster image
+	processor (RIP), (which makes them more expensive than other types of printers; throw PostScript toward them,
+	and they will spit out your printed pages. The RIP does all the hard work of converting the PostScript drawing
+	commands into a bitmap picture as you see it on paper, in a resolution as done by your printer. This is no
+	different than PostScript printing a file from a Windows origin.
+	</para>
+
+	<note><para>
+	<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>PPD-aware</primary></indexterm>
+<indexterm><primary>PostScript Printer Description</primary><see>PPD</see></indexterm>
+	Traditional UNIX programs and printing systems &smbmdash; while using PostScript &smbmdash; are largely not
+	PPD-aware. PPDs are <quote>PostScript Printer Description</quote> files. They enable you to specify and
+	control all options a printer supports: duplexing, stapling, and punching. Therefore, UNIX users for a long
+	time couldn't choose many of the supported device and job options, unlike Windows or Apple users. But now
+	there is CUPS. as illustrated in <link linkend="2small">Printing to a PostScript Printer</link>.
+	</para>
+	</note>
+
+	<figure id="2small">
+		<title>Printing to a PostScript Printer.</title>
+		<imagefile>2small</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>PDL</primary></indexterm>
+	However, there are other types of printers out there. These do not know how to print PostScript. They use
+	their own PDL, often proprietary. To print to them is much more demanding. Since your UNIX applications mostly
+	produce PostScript, and since these devices do not understand PostScript, you need to convert the print files
+	to a format suitable for your printer on the host before you can send it away.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Ghostscript: The Software RIP for Non-PostScript Printers</title>
+
+	<para>
+	<indexterm><primary>GhostScript</primary></indexterm>
+	Here is where Ghostscript kicks in. Ghostscript is the traditional (and quite powerful) PostScript interpreter
+	used on UNIX platforms. It is a RIP in software, capable of doing a <emphasis>lot</emphasis> of file format
+	conversions for a very broad spectrum of hardware devices as well as software file formats.  Ghostscript
+	technology and drivers are what enable PostScript printing to non-PostScript hardware. This is shown in
+	<link linkend="3small">Ghostscript as a RIP for Non-PostScript Printers</link>.
+	</para>
+
+	<figure id="3small">
+		<title>Ghostscript as a RIP for Non-PostScript Printers.</title>
+		<imagefile>3small</imagefile>
+	</figure>
+
+	<tip><para>
+<indexterm><primary>PNG</primary></indexterm>
+<indexterm><primary>AFPL</primary></indexterm>
+<indexterm><primary>ESP</primary></indexterm>
+	Use the <quote>gs -h</quote> command to check for all built-in <quote>devices</quote> on your Ghostscript
+	version. If you specify a parameter of <parameter>-sDEVICE=png256</parameter> on your Ghostscript command
+	line, you are asking Ghostscript to convert the input into a PNG file. Naming a <quote>device</quote> on the
+	command line is the most important single parameter to tell Ghostscript exactly how it should render the
+	input. New Ghostscript versions are released at fairly regular intervals, now by artofcode LLC. They are
+	initially put under the <quote>AFPL</quote> license, but re-released under the GNU GPL as soon as the next
+	AFPL version appears. GNU Ghostscript is probably the version installed on most Samba systems. But it has some
+	deficiencies.  <indexterm><primary>Ghostscript</primary><secondary>ESP</secondary><see>ESP
+	GhostScript</see></indexterm> Therefore, ESP Ghostscript was developed as an enhancement over GNU Ghostscript,
+	with lots of bug-fixes, additional devices, and improvements. It is jointly maintained by developers from
+	CUPS, Gimp-Print, MandrakeSoft, SuSE, Red Hat, and Debian. It includes the <quote>cups</quote> device
+	(essential to print to non-PS printers from CUPS).
+	</para></tip>
+
+	</sect2>
+
+	<sect2>
+	<title>PostScript Printer Description (PPD) Specification</title>
+
+	<para>
+	<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>PDL</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+	While PostScript in essence is a PDL to represent the page layout in a device-independent way, real-world
+	print jobs are always ending up being output on hardware with device-specific features. To take care of all
+	the differences in hardware and to allow for innovations, Adobe has specified a syntax and file format for
+	PostScript Printer Description (PPD) files. Every PostScript printer ships with one of these files.
+	</para>
+
+	<para>
+	PPDs contain all the information about general and special features of the
+	given printer model: Which different resolutions can it handle? Does
+	it have a duplexing unit? How many paper trays are there? What media
+	types and sizes does it take? For each item, it also names the special
+	command string to be sent to the printer (mostly inside the PostScript
+	file) in order to enable it.
+	</para>
+
+	<para>
+	Information from these PPDs is meant to be taken into account by the
+	printer drivers. Therefore, installed as part of the Windows
+	PostScript driver for a given printer is the printer's PPD. Where it
+	makes sense, the PPD features are presented in the drivers' UI dialogs
+	to display to the user a choice of print options. In the end, the
+	user selections are somehow written (in the form of special
+	PostScript, PJL, JCL, or vendor-dependent commands) into the PostScript
+	file created by the driver.
+	</para>
+
+	<warning><para>
+	<indexterm><primary>PDF</primary></indexterm>
+<indexterm><primary>PDF distilling</primary></indexterm>
+	A PostScript file that was created to contain device-specific commands
+	for achieving a certain print job output (e.g., duplexed, stapled, and
+	punched) on a specific target machine may not print as expected, or
+	may not be printable at all on other models; it also may not be fit
+	for further processing by software (e.g., by a PDF distilling program).
+	</para></warning>
+	</sect2>
+
+	<sect2>
+	<title>Using Windows-Formatted Vendor PPDs</title>
+
+	<para>
+<indexterm><primary>CUPS</primary></indexterm>
+<indexterm><primary>PPDs</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+	CUPS can handle all spec-compliant PPDs as supplied by the manufacturers for their PostScript models. Even if
+	a vendor does not mention our favorite OS in his or her manuals and brochures, you can safely trust this:
+	<emphasis>If you get the Windows NT version of the PPD, you can use it unchanged in CUPS</emphasis> and thus
+	access the full power of your printer just like a Windows NT user could!
+	</para>
+
+	<tip><para>
+	To check the spec compliance of any PPD online, go to <ulink noescape="1"
+	url="http://www.cups.org/testppd.php">http://www.cups.org/testppd.php</ulink> and upload your PPD. You will
+	see the results displayed immediately. CUPS in all versions after 1.1.19 has a much stricter internal PPD
+	parsing and checking code enabled; in case of printing trouble, this online resource should be one of your
+	first pit stops.
+	</para></tip>
+
+	<warning><para>
+	<indexterm><primary>foomatic</primary></indexterm>
+	<indexterm><primary>cupsomatic</primary></indexterm>
+	For real PostScript printers, <emphasis>do not</emphasis> use the <emphasis>Foomatic</emphasis> or
+	<emphasis>cupsomatic</emphasis> PPDs from Linuxprinting.org. With these devices, the original vendor-provided
+	PPDs are always the first choice.
+	</para></warning>
+
+	<tip><para>
+<indexterm><primary>W32X86/2</primary></indexterm>
+	If you are looking for an original vendor-provided PPD of a specific device, and you know that an NT4 box (or
+	any other Windows box) on your LAN has the PostScript driver installed, just use <command>smbclient
+	//NT4-box/print\$ -U username</command> to access the Windows directory where all printer driver files are
+	stored. First look in the <filename>W32X86/2</filename> subdirectory for the PPD you are seeking.
+	</para></tip>
+	</sect2>
+
+	<sect2>
+	<title>CUPS Also Uses PPDs for Non-PostScript Printers</title>
+
+	<para>
+<indexterm><primary>non-PostScript</primary></indexterm>
+<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>CUPS filtering</primary></indexterm>
+	CUPS also uses specially crafted PPDs to handle non-PostScript printers. These PPDs are usually not available
+	from the vendors (and no, you can't just take the PPD of a PostScript printer with the same model name and
+	hope it works for the non-PostScript version too). To understand how these PPDs work for non-PS printers, we
+	first need to dive deeply into the CUPS filtering and file format conversion architecture. Stay tuned.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>The CUPS Filtering Architecture</title>
+
+<para>
+<indexterm><primary>CUPS filtering</primary></indexterm>
+<indexterm><primary>Ghostscript</primary></indexterm>
+<indexterm><primary>MIME type</primary></indexterm>
+<indexterm><primary>MIME recognition</primary></indexterm>
+<indexterm><primary>MIME conversion rules</primary></indexterm>
+The core of the CUPS filtering system is based on Ghostscript. In addition to Ghostscript, CUPS uses some
+other filters of its own. You (or your OS vendor) may have plugged in even more filters. CUPS handles all data
+file formats under the label of various MIME types. Every incoming print file is subjected to an initial
+autotyping. The autotyping determines its given MIME type. A given MIME type implies zero or more possible
+filtering chains relevant to the selected target printer. This section discusses how MIME types recognition
+and conversion rules interact. They are used by CUPS to automatically set up a working filtering chain for any
+given input data format.
+</para>
+
+<para>
+If CUPS rasterizes a PostScript file natively to a bitmap, this is done in two stages:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+<indexterm><primary>generic raster format</primary></indexterm>
+<indexterm><primary>CUPS raster</primary></indexterm>
+	The first stage uses a Ghostscript device named <quote>cups</quote>
+	(this is since version 1.1.15) and produces a generic raster format
+	called <quote>CUPS raster</quote>.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>raster driver</primary></indexterm>
+	The second stage uses a <quote>raster driver</quote> that converts
+	the generic CUPS raster to a device-specific raster.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>Ghostscript</primary></indexterm>
+<indexterm><primary>GNU Ghostscript</primary></indexterm>
+<indexterm><primary>ESP Ghostscript</primary></indexterm>
+Make sure your Ghostscript version has the <quote>cups</quote> device compiled in (check with <command>gs -h |
+grep cups</command>). Otherwise you may encounter the dreaded <computeroutput>Unable to convert file
+0</computeroutput> in your CUPS error_log file. To have <quote>cups</quote> as a device in your Ghostscript,
+you either need to patch GNU Ghostscript and recompile or use
+<indexterm><primary>ESP</primary><secondary>Ghostscript</secondary></indexterm><ulink
+url="http://www.cups.org/ghostscript.php">ESP Ghostscript</ulink>. The superior alternative is ESP
+Ghostscript. It supports not just CUPS, but 300 other devices (while GNU Ghostscript supports only about 180).
+Because of this broad output device support, ESP Ghostscript is the first choice for non-CUPS spoolers, too.
+It is now recommended by Linuxprinting.org for all spoolers.
+</para>
+
+<para>
+<indexterm><primary>cupsomatic</primary></indexterm>
+<indexterm><primary>foomatic</primary></indexterm>
+<indexterm><primary>foomatic-rip</primary></indexterm>
+<indexterm><primary>ESP Ghostscript</primary></indexterm>
+CUPS printers may be set up to use external rendering paths. One of the most common is provided by the
+Foomatic/cupsomatic concept from <ulink url="http://www.linuxprinting.org/">Linuxprinting.org</ulink>. This
+uses the classical Ghostscript approach, doing everything in one step.  It does not use the
+<quote>cups</quote> device, but one of the many others. However, even for Foomatic/cupsomatic usage, best
+results and <indexterm><primary>ESP</primary><secondary>Ghostscript</secondary></indexterm> broadest printer
+model support is provided by ESP Ghostscript (more about Foomatic/cupsomatic, particularly the new version
+called now <emphasis>foomatic-rip</emphasis>, follows).
+</para>
+
+	<sect2>
+	<title>MIME Types and CUPS Filters</title>
+
+
+	<para>
+	<indexterm><primary>MIME</primary><secondary>filters</secondary></indexterm>
+	<indexterm><primary>MIME</primary></indexterm>
+<indexterm><primary>mime.types</primary></indexterm>
+<indexterm><primary>application/pdf</primary></indexterm>
+<indexterm><primary>autotyping</primary></indexterm>
+	CUPS reads the file <filename>/etc/cups/mime.types</filename> (and all other files carrying a
+	<filename>*.types</filename> suffix in the same directory) upon startup. These files contain the MIME type
+	recognition rules that are applied when CUPS runs its autotyping routines. The rule syntax is explained in the
+	man page for <filename>mime.types</filename> and in the comments section of the
+	<filename>mime.types</filename> file itself. A simple rule reads like this:
+	<indexterm><primary>application/pdf</primary></indexterm>
+<programlisting>
+application/pdf         pdf string(0,%PDF)
+</programlisting>
+<indexterm><primary>%PDF</primary></indexterm>
+<indexterm><primary>.pdf</primary></indexterm>
+	This means if a filename has a <filename>.pdf</filename> suffix or if the magic string
+	<emphasis>%PDF</emphasis> is right at the beginning of the file itself (offset 0 from the start), then it is a
+	PDF file (<parameter>application/pdf</parameter>).  Another rule is this:
+<programlisting>
+application/postscript  ai eps ps string(0,%!) string(0,&lt;04&gt;%!)
+</programlisting>
+<indexterm><primary>suffixes</primary></indexterm>
+<indexterm><primary>.ai</primary></indexterm>
+<indexterm><primary>.eps</primary></indexterm>
+<indexterm><primary>.ps</primary></indexterm>
+<indexterm><primary>generic PostScript</primary></indexterm>
+<indexterm><primary>application/postscript</primary></indexterm>
+	If the filename has one of the suffixes <filename>.ai</filename>, <filename>.eps</filename>,
+	<filename>.ps</filename>, or if the file itself starts with one of the strings <emphasis>%!</emphasis> or
+	<emphasis><![CDATA[<04>%!]]></emphasis>, it is a generic PostScript file
+	(<parameter>application/postscript</parameter>).
+	</para>
+
+	<warning><para>
+<indexterm><primary>/etc/cups/</primary></indexterm>
+	Don't confuse the other mime.types files your system might be using
+	with the one in the <filename>/etc/cups/</filename> directory.
+	</para></warning>
+
+	<note><para>
+<indexterm><primary>application/postscript</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>filter</primary></indexterm>
+<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>transformation</primary></indexterm>
+	There is an important difference between two similar MIME types in CUPS: one is
+	<parameter>application/postscript</parameter>, the other is
+	<parameter>application/vnd.cups-postscript</parameter>. While <parameter>application/postscript</parameter> is
+	meant to be device-independent, job options for the file are still outside the PS file content, embedded in
+	command-line or environment variables by CUPS, <parameter>application/vnd.cups-postscript</parameter> may have
+	the job options inserted into the PostScript data itself (where applicable). The transformation of the generic
+	PostScript (<parameter>application/postscript</parameter>) to the device-specific version
+	(<parameter>application/vnd.cups-postscript</parameter>) is the responsibility of the CUPS
+	<parameter>pstops</parameter> filter. pstops uses information contained in the PPD to do the transformation.
+	</para></note>
+
+	<para>
+<indexterm><primary>ASCII</primary></indexterm>
+<indexterm><primary>HP-GL</primary></indexterm>
+<indexterm><primary>PDF</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>DVI</primary></indexterm>
+<indexterm><primary>GIF</primary></indexterm>
+<indexterm><primary>PNG</primary></indexterm>
+<indexterm><primary>TIFF</primary></indexterm>
+<indexterm><primary>JPEG</primary></indexterm>
+<indexterm><primary>Photo-CD</primary></indexterm>
+<indexterm><primary>SUN-Raster</primary></indexterm>
+<indexterm><primary>PNM</primary></indexterm>
+<indexterm><primary>PBM</primary></indexterm>
+<indexterm><primary>SGI-RGB</primary></indexterm>
+<indexterm><primary>MIME</primary></indexterm>
+<indexterm><primary>filters</primary></indexterm>
+	CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI, and
+	many image formats (GIF, PNG, TIFF, JPEG, Photo-CD, SUN-Raster,
+	PNM, PBM, SGI-RGB, and more) and their associated MIME types
+	with its filters.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>MIME Type Conversion Rules</title>
+
+
+	<para>
+	<indexterm><primary>MIME</primary></indexterm>
+	<indexterm><primary>application/pdf</primary></indexterm>
+<indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
+<indexterm><primary>application/pdf</primary></indexterm>
+<indexterm><primary>application/postscript</primary></indexterm>
+	CUPS reads the file <filename>/etc/cups/mime.convs</filename>
+	(and all other files named with a <filename>*.convs</filename>
+	suffix in the same directory) upon startup. These files contain
+	lines naming an input MIME type, an output MIME type, a format
+	conversion filter that can produce the output from the input type,
+	and virtual costs associated with this conversion. One example line
+	reads like this:
+<programlisting>
+application/pdf         application/postscript   33   pdftops
+</programlisting>
+<indexterm><primary>pdftops</primary></indexterm>
+	This means that the <parameter>pdftops</parameter> filter will take
+	<parameter>application/pdf</parameter> as input and produce
+	<parameter>application/postscript</parameter> as output; the virtual
+	cost of this operation is 33 CUPS-$. The next filter is more
+	expensive, costing 66 CUPS-$:
+	<indexterm><primary>pdf</primary></indexterm>
+<programlisting>
+application/vnd.hp-HPGL application/postscript   66   hpgltops
+</programlisting>
+<indexterm><primary>hpgltops</primary></indexterm>
+	This is the <parameter>hpgltops</parameter>, which processes HP-GL
+	plotter files to PostScript.
+	<indexterm><primary>application/octet-stream</primary></indexterm>
+<programlisting>
+application/octet-stream
+</programlisting>
+	Here are two more examples: 
+	<indexterm><primary>text/plain</primary></indexterm>
+<indexterm><primary>application/x-shell</primary></indexterm>
+<indexterm><primary>text/plain</primary></indexterm>
+<indexterm><primary>texttops</primary></indexterm>
+<programlisting>
+application/x-shell     application/postscript   33    texttops
+text/plain              application/postscript   33    texttops
+</programlisting>
+<indexterm><primary>application/x-shell</primary></indexterm>
+	The last two examples name the <parameter>texttops</parameter> filter to work on
+	<parameter>text/plain</parameter> as well as on <parameter>application/x-shell</parameter>. (Hint: This
+	differentiation is needed for the syntax highlighting feature of <parameter>texttops</parameter>).
+	</para>
+	</sect2>
+
+	<sect2>
+	<title>Filtering  Overview</title>
+
+	<para>
+	<indexterm><primary>MIME</primary></indexterm>
+	There are many more combinations named in <filename>mime.convs</filename>. However, you are not limited to use
+	the ones predefined there. You can plug in any filter you like to the CUPS framework. It must meet, or must be
+	made to meet, some minimal requirements. If you find (or write) a cool conversion filter of some kind, make
+	sure it complies with what CUPS needs and put in the right lines in <filename>mime.types</filename> and
+	<filename>mime.convs</filename>; then it will work seamlessly inside CUPS.
+	</para>
+
+	<sect3>
+	<title>Filter Requirements</title>
+
+	<para>
+	The <quote>CUPS requirements</quote> for filters are simple. Take filenames or <filename>stdin</filename> as
+	input and write to <filename>stdout</filename>. They should take these arguments:
+	</para>
+
+	<variablelist>
+		<varlistentry><term>printer</term>
+			<listitem><para>
+			The name of the printer queue (normally this is the name of the filter being run).
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>job</term>
+			<listitem><para>
+			The numeric job ID for the job being printed.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>user</term>
+			<listitem><para>
+			The string from the originating-user-name attribute.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>title</term>
+			<listitem><para>
+			The string from the job-name attribute.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>copies</term>
+			<listitem><para>
+			The numeric value from the number-copies attribute.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>options</term>
+			<listitem><para>
+			The job options.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>filename</term>
+			<listitem><para>
+			(optionally) The print request file (if missing, filters expected data
+			fed through <filename>stdin</filename>). In most cases, it is easy to
+			write a simple wrapper script around existing filters to make them work with CUPS.
+			</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Prefilters</title>
+
+	<para>
+	<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>non-PostScript printers</primary></indexterm>
+<indexterm><primary>raster</primary></indexterm>
+	As previously stated, PostScript is the central file format to any UNIX-based
+	printing system. From PostScript, CUPS generates raster data to feed
+	non-PostScript printers.
+	</para>
+
+	<para>
+<indexterm><primary>prefilters</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>ASCII text</primary></indexterm>
+<indexterm><primary>PDF</primary></indexterm>
+<indexterm><primary>DVI</primary></indexterm>
+<indexterm><primary>HP-GL.</primary></indexterm>
+<indexterm><primary>MIME type</primary></indexterm>
+<indexterm><primary>application/postscript</primary></indexterm>
+<indexterm><primary>pstops</primary></indexterm>
+<indexterm><primary>application/vnd.cups-postscript</primary></indexterm>
+	But what happens if you send one of the supported non-PS formats to print? Then CUPS runs
+	<quote>prefilters</quote> on these input formats to generate PostScript first. There are prefilters to create
+	PostScript from ASCII text, PDF, DVI, or HP-GL. The outcome of these filters is always of MIME type
+	<parameter>application/postscript</parameter> (meaning that any device-specific print options are not yet
+	embedded into the PostScript by CUPS and that the next filter to be called is pstops). Another prefilter is
+	running on all supported image formats, the <parameter>imagetops</parameter> filter. Its outcome is always of
+	MIME type <parameter>application/vnd.cups-postscript</parameter> (not application/postscript), meaning it has
+	the print options already embedded into the file. This is shown in <link linkend="4small">Prefiltering in
+	CUPS to Form PostScript</link>.
+	</para>
+
+	<figure id="4small">
+		<title>Prefiltering in CUPS to Form PostScript.</title>
+		<imagefile scale="25">4small</imagefile>
+	</figure>
+
+	</sect2>
+
+	<sect2>
+	<title>pstops</title>
+
+	<para>
+<indexterm><primary>pstops</primary></indexterm>
+<indexterm><primary>application/postscript</primary></indexterm>
+<indexterm><primary>application/vnd.cups-postscript</primary></indexterm>
+<indexterm><primary>output duplexing</primary></indexterm>
+<indexterm><primary>stapling</primary></indexterm>
+<indexterm><primary>punching</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+	<emphasis>pstops</emphasis> is a filter that is used to convert <parameter>application/postscript</parameter> to
+	<parameter>application/vnd.cups-postscript</parameter>. As stated earlier, this filter inserts all
+	device-specific print options (commands to the printer to ask for the duplexing of output, or stapling and
+	punching it, and so on) into the PostScript file. An example is illustrated in <link
+	linkend="5small">Adding Device-Specific Print Options</link>.
+	</para>
+
+	<figure id="5small">
+		<title>Adding Device-Specific Print Options.</title>
+		<imagefile scale="25">5small</imagefile>
+	</figure>
+
+	<para>
+	This is not all. Other tasks performed by it are:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Selecting the range of pages to be printed (e.g., you can choose to
+		print only pages <quote>3, 6, 8-11, 16, and 19-21</quote>, or only odd-numbered
+		pages).
+		</para></listitem>
+
+		<listitem><para>
+		Putting two or more logical pages on one sheet of paper (the
+		so-called <quote>number-up</quote> function).
+		</para></listitem>
+
+		<listitem><para>Counting the pages of the job to insert the accounting
+		information into the <filename>/var/log/cups/page_log</filename>.
+		</para></listitem>
+	</itemizedlist>
+	</sect2>
+
+	<sect2>
+	<title>pstoraster</title>
+
+	<para>
+<indexterm><primary>pstoraster</primary></indexterm>
+<indexterm><primary>rasterization</primary></indexterm>
+<indexterm><primary>raster drivers</primary></indexterm>
+	<parameter>pstoraster</parameter> is at the core of the CUPS filtering system. It is responsible for the first
+	stage of the rasterization process. Its input is of MIME type application/vnd.cups-postscript; its output is
+	application/vnd.cups-raster. This output format is not yet meant to be printable. Its aim is to serve as a
+	general-purpose input format for more specialized <emphasis>raster drivers</emphasis> that are able to
+	generate device-specific printer data. This is shown in <link linkend="cups-raster">the PostScript to
+	Intermediate Raster Format diagram</link>.
+	</para>
+
+	<figure id="cups-raster">
+		<title>PostScript to Intermediate Raster Format.</title>
+		<imagefile scale="25">6small</imagefile>
+	</figure>
+
+	<para>
+<indexterm><primary>CUPS raster</primary></indexterm>
+<indexterm><primary>generic raster</primary></indexterm>
+<indexterm><primary>IANA</primary></indexterm>
+<indexterm><primary>raster drivers</primary></indexterm>
+	CUPS raster is a generic raster format with powerful features. It is able to include per-page information,
+	color profiles, and more, to be used by the downstream raster drivers. Its MIME type is registered with IANA
+	and its specification is, of course, completely open. It is designed to make it quite easy and inexpensive for
+	manufacturers to develop Linux and UNIX raster drivers for their printer models should they choose to do so.
+	CUPS always takes care of the first stage of rasterization so these vendors do not need to care about
+	Ghostscript complications (in fact, there are currently more than one vendor financing the development of CUPS
+	raster drivers). This is illustrated in <link linkend="cups-raster2">the CUPS-Raster Production Using
+	Ghostscript illustration</link>.
+	</para>
+
+	<figure id="cups-raster2">
+		<title>CUPS-Raster Production Using Ghostscript.</title>
+		<imagefile>7small</imagefile>
+	</figure>
+
+	<para>
+<indexterm><primary>pstoraster</primary></indexterm>
+<indexterm><primary>GNU Ghostscript</primary></indexterm>
+<indexterm><primary>AFPL Ghostscript</primary></indexterm>
+<indexterm><primary>standalone filter</primary></indexterm>
+	CUPS versions before version 1.1.15 shipped a binary (or source code) standalone filter, named
+	<parameter>pstoraster</parameter>. <parameter>pstoraster</parameter>, which was derived from GNU Ghostscript
+	5.50 and could be installed instead of and in addition to any GNU or AFPL Ghostscript package without
+	conflicting.
+	</para>
+
+	<para>
+	Since version 1.1.15, this feature has changed. The functions for this filter have been integrated back
+	into Ghostscript (now based on GNU Ghostscript version 7.05). The <parameter>pstoraster</parameter> filter is
+	now a simple shell script calling <command>gs</command> with the <command>-sDEVICE=cups</command> parameter.
+	If your Ghostscript fails when this command is executed: <command>gs -h |grep cups</command>, you might not 
+	be able to print, update your Ghostscript.
+	</para>
+	</sect2>
+
+	<sect2>
+	<title>imagetops and imagetoraster</title>
+
+	<para>
+<indexterm><primary>prefilter</primary></indexterm>
+<indexterm><primary>imagetoraster</primary></indexterm>
+	In the section about prefilters, we mentioned the prefilter
+	that generates PostScript from image formats. The <parameter>imagetoraster</parameter>
+	filter is used to convert directly from image to raster, without the
+	intermediate PostScript stage. It is used more often than the previously
+	mentioned prefilters. We summarize in a flowchart the image file
+	filtering in <link linkend="small8">the Image Format to CUPS-Raster Format Conversion illustration</link>.
+	</para>
+
+	<figure id="small8">
+		<title>Image Format to CUPS-Raster Format Conversion.</title>
+		<imagefile>8small</imagefile>
+	</figure>
+
+	</sect2>
+
+	<sect2>
+	<title>rasterto [printers specific]</title>
+
+	<para>
+<indexterm><primary>rastertoalps</primary></indexterm>
+<indexterm><primary>rastertobj</primary></indexterm>
+<indexterm><primary>rastertoepson</primary></indexterm>
+<indexterm><primary>rastertoescp</primary></indexterm>
+<indexterm><primary>rastertopcl</primary></indexterm>
+<indexterm><primary>rastertoturboprint</primary></indexterm>
+<indexterm><primary>rastertoescp</primary></indexterm>
+<indexterm><primary>rastertohp</primary></indexterm>
+<indexterm><primary>rastertoprinter</primary></indexterm>
+<indexterm><primary>rastertoprinter</primary></indexterm>
+<indexterm><primary>Gimp-Print</primary></indexterm>
+	CUPS ships with quite a variety of raster drivers for processing CUPS raster. On my system, I find in
+	/usr/lib/cups/filter/ the following: <parameter>rastertoalps</parameter>, <parameter>rastertobj</parameter>,
+	<parameter>rastertoepson</parameter>, <parameter>rastertoescp</parameter>, <parameter>rastertopcl</parameter>,
+	<parameter>rastertoturboprint</parameter>, <parameter>rastertoapdk</parameter>,
+	<parameter>rastertodymo</parameter>, <parameter>rastertoescp</parameter>, <parameter>rastertohp</parameter>,
+	and <parameter>rastertoprinter</parameter>. Don't worry if you have fewer drivers than this; some of these are
+	installed by commercial add-ons to CUPS (like <parameter>rastertoturboprint</parameter>), and others (like
+	<parameter>rastertoprinter</parameter>) by third-party driver development projects (such as Gimp-Print)
+	wanting to cooperate as closely as possible with CUPS. See <link linkend="small9">the Raster to
+	Printer-Specific Formats illustration</link>.
+	</para>
+
+		<figure id="small9">
+			<title>Raster to Printer-Specific Formats.</title>
+			<imagefile>9small</imagefile>
+		</figure>
+	</sect2>
+
+	<sect2>
+	<title>CUPS Backends</title>
+
+	<para>
+<indexterm><primary>CUPS filtering chain</primary></indexterm>
+<indexterm><primary>print queue</primary></indexterm>
+	The last part of any CUPS filtering chain is a backend. Backends
+	are special programs that send the print-ready file to the final
+	device. There is a separate backend program for any transfer
+	protocol for sending print jobs over the network, and one for every local
+	interface. Every CUPS print queue needs to have a CUPS <quote>device-URI</quote>
+	associated with it. The device URI is the way to encode the backend
+	used to send the job to its destination. Network device-URIs use
+	two slashes in their syntax, local device URIs only one, as you can
+	see from the following list. Keep in mind that local interface names
+	may vary greatly from my examples, if your OS is not Linux:
+	</para>
+
+	<variablelist>
+		<varlistentry><term>usb</term>
+		<listitem><para>
+		This backend sends print files to USB-connected printers. An
+		example for the CUPS device-URI to use is
+		<filename>usb:/dev/usb/lp0</filename>.
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>serial</term>
+		<listitem><para>
+		This backend sends print files to serially connected printers.
+		An example for the CUPS device-URI to use is
+		<filename>serial:/dev/ttyS0?baud=11500</filename>.
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>parallel</term>
+		<listitem><para>
+		This backend sends print files to printers connected to the
+		parallel port. An example for the CUPS device-URI to use is
+		<filename>parallel:/dev/lp0</filename>.
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>SCSI</term>
+		<listitem><para>
+		This backend sends print files to printers attached to the
+		SCSI interface. An example for the CUPS device-URI to use is
+		<filename>scsi:/dev/sr1</filename>.
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>lpd</term>
+		<listitem><para>
+		This backend sends print files to LPR/LPD-connected network
+		printers. An example for the CUPS device-URI to use is
+		<filename>lpd://remote_host_name/remote_queue_name</filename>.
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>AppSocket/HP JetDirect</term>
+		<listitem><para>
+		This backend sends print files to AppSocket (a.k.a., HP
+		JetDirect) connected network printers. An example for the CUPS
+		device-URI to use is
+		<filename>socket://10.11.12.13:9100</filename>.
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>ipp</term>
+		<listitem><para>
+		This backend sends print files to IPP-connected network
+		printers (or to other CUPS servers). Examples for CUPS device-URIs
+		to use are
+		<filename>ipp:://192.193.194.195/ipp</filename>
+		(for many HP printers) and
+		<filename>ipp://remote_cups_server/printers/remote_printer_name</filename>.
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>http</term>
+		<listitem><para>
+		This backend sends print files to HTTP-connected printers.
+		(The http:// CUPS backend is only a symlink to the ipp:// backend.)
+		Examples for the CUPS device-URIs to use are
+		<filename>http:://192.193.194.195:631/ipp</filename>
+		(for many HP printers) and
+		<filename>http://remote_cups_server:631/printers/remote_printer_name</filename>.
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>smb</term>
+		<listitem><para>
+		This backend sends print files to printers shared by a Windows
+		host. Examples of CUPS device-URIs that may be used includes:
+		</para>
+
+		<para>
+		<simplelist>
+		<member><filename>smb://workgroup/server/printersharename</filename></member>
+		<member><filename>smb://server/printersharename</filename></member>
+		<member><filename>smb://username:password@workgroup/server/printersharename</filename></member>
+		<member><filename>smb://username:password@server/printersharename</filename></member>
+		</simplelist>
+		</para>
+
+		<para>
+		The smb:// backend is a symlink to the Samba utility
+		<parameter>smbspool</parameter> (does not ship with CUPS). If the
+		symlink is not present in your CUPS backend directory, have your
+		root user create it: <command>ln -s `which smbspool'
+		/usr/lib/cups/backend/smb</command>.
+		</para></listitem></varlistentry>
+	</variablelist>
+
+	<para>
+	It is easy to write your own backends as shell or Perl scripts if you
+	need any modification or extension to the CUPS print system. One
+	reason could be that you want to create <quote>special</quote> printers that send
+	the print jobs as email (through a <quote>mailto:/</quote> backend), convert them to
+	PDF (through a <quote>pdfgen:/</quote> backend) or dump them to <quote>/dev/null</quote>. (In
+	fact, I have the systemwide default printer set up to be connected to
+	a devnull:/ backend: there are just too many people sending jobs
+	without specifying a printer, and scripts and programs that do not name
+	a printer. The systemwide default deletes the job and sends a polite
+	email back to the $USER asking him or her to always specify the correct
+	printer name.)
+	</para>
+
+	<para>
+<indexterm><primary>lpinfo</primary></indexterm>
+<indexterm><primary>CUPS backends</primary></indexterm>
+	Not all of the mentioned backends may be present on your system or
+	usable (depending on your hardware configuration). One test for all
+	available CUPS backends is provided by the <emphasis>lpinfo</emphasis>
+	utility. Used with the <option>-v</option> parameter, it lists
+	all available backends:
+	</para>
+
+	<para><screen>
+	&prompt;<userinput>lpinfo -v</userinput>
+	</screen></para>
+	</sect2>
+
+	<sect2>
+	<title>The Role of <parameter>cupsomatic/foomatic</parameter></title>
+
+	<para>
+	<indexterm><primary>cupsomatic</primary></indexterm>
+	<indexterm><primary>foomatic</primary></indexterm>
+<indexterm><primary>PPDs</primary></indexterm>
+<indexterm><primary>Foomatic Printer</primary></indexterm>
+<indexterm><primary>Linuxprinting.org</primary></indexterm>
+	<parameter>cupsomatic</parameter> filters may be the most widely used on CUPS
+	installations. You must be clear that these were not
+	developed by the CUPS people. They are a third-party add-on to
+	CUPS. They utilize the traditional Ghostscript devices to render jobs
+	for CUPS. When troubleshooting, you should know about the
+	difference. Here the whole rendering process is done in one stage,
+	inside Ghostscript, using an appropriate device for the target
+	printer. <parameter>cupsomatic</parameter> uses PPDs that are generated from the Foomatic
+	Printer &amp; Driver Database at Linuxprinting.org.
+	</para>
+
+	<para>
+	You can recognize these PPDs from the line calling the
+	<parameter>cupsomatic</parameter> filter:
+<programlisting>
+*cupsFilter: "application/vnd.cups-postscript  0  cupsomatic"
+</programlisting>
+	You may find this line among the first 40 or so lines of the PPD
+	file. If you have such a PPD installed, the printer shows up in the
+	CUPS Web interface with a <parameter>foomatic</parameter> namepart for
+	the driver description. <parameter>cupsomatic</parameter> is a Perl script that runs
+	Ghostscript with all the complicated command-line options
+	autoconstructed from the selected PPD and command line options give to
+	the print job.
+	</para>
+
+	<para>
+	<indexterm><primary>point'n'print</primary></indexterm>
+<indexterm><primary>foomatic-rip</primary></indexterm>
+<indexterm><primary>Adobe specifications</primary></indexterm>
+<indexterm><primary>hi-res photo</primary></indexterm>
+<indexterm><primary>normal color</primary></indexterm>
+<indexterm><primary>grayscale</primary></indexterm>
+<indexterm><primary>draft</primary></indexterm>
+<indexterm><primary>media type</primary></indexterm>
+<indexterm><primary>resolution</primary></indexterm>
+<indexterm><primary>inktype</primary></indexterm>
+<indexterm><primary>dithering algorithm</primary></indexterm>
+	However, <parameter>cupsomatic</parameter> is now deprecated. Its PPDs (especially the first
+	generation of them, still in heavy use out there) are not meeting the
+	Adobe specifications. You might also suffer difficulties when you try
+	to download them with <quote>Point'n'Print</quote> to Windows clients. A better
+	and more powerful successor is now in a stable beta-version: it is called <parameter>foomatic-rip</parameter>. To use
+	<parameter>foomatic-rip</parameter> as a filter with CUPS, you need the new type of PPDs, which
+	have a similar but different line:
+<programlisting>
+*cupsFilter: "application/vnd.cups-postscript  0  foomatic-rip"
+</programlisting>
+	The PPD-generating engine at Linuxprinting.org has been revamped.
+	The new PPDs comply with the Adobe spec. They also provide a
+	new way to specify different quality levels (hi-res photo, normal
+	color, grayscale, and draft) with a single click, whereas before you
+	could have required five or more different selections (media type,
+	resolution, inktype, and dithering algorithm). There is support for
+	custom-size media built in. There is support to switch
+	print options from page to page in the middle of a job. And the
+	best thing is that the new <constant>foomatic-rip</constant> works seamlessly with all
+	legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR, and so on), providing
+	for them access to use PPDs for their printing.
+	</para>
+	</sect2>
+
+	<sect2>
+	<title>The Complete Picture</title>
+
+	<para>
+	If you want to see an overview of all the filters and how they
+	relate to each other, the complete picture of the puzzle is at the end
+	of this chapter.
+	</para>
+	</sect2>
+
+	<sect2>
+	<title><filename>mime.convs</filename></title>
+
+	<para>
+	CUPS autoconstructs all possible filtering chain paths for any given
+	MIME type and every printer installed. But how does it decide in
+	favor of or against a specific alternative?  (There may be cases
+	where there is a choice of two or more possible filtering chains for
+	the same target printer.) Simple. You may have noticed the figures in
+	the third column of the mime.convs file. They represent virtual costs
+	assigned to this filter. Every possible filtering chain will sum up to
+	a total <quote>filter cost.</quote> CUPS decides for the most <quote>inexpensive</quote> route.
+	</para>
+
+	<tip><para>
+<indexterm><primary>cupsd.conf</primary></indexterm>
+<indexterm><primary>FilterLimit</primary></indexterm>
+	Setting <parameter>FilterLimit 1000</parameter> in
+	<filename>cupsd.conf</filename> will not allow more filters to
+	run concurrently than will consume a total of 1000 virtual filter
+	cost. This is an efficient way to limit the load of any CUPS
+	server by setting an appropriate <quote>FilterLimit</quote> value. A FilterLimit of
+	200 allows roughly one job at a time, while a FilterLimit of 1000 allows
+	approximately five jobs maximum at a time.
+	</para></tip>
+	</sect2>
+
+	<sect2>
+	<title><quote>Raw</quote> Printing</title>
+
+	<para>
+<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>lpadmin</primary></indexterm>
+<indexterm><primary>rawprinter</primary></indexterm>
+	You can tell CUPS to print (nearly) any file <quote>raw</quote>. <quote>Raw</quote> means it will not be
+	filtered. CUPS will send the file to the printer <quote>as is</quote> without bothering if the printer is able
+	to digest it. Users need to take care themselves that they send sensible data formats only. Raw printing can
+	happen on any queue if the <quote><parameter>-o raw</parameter></quote> option is specified on the command
+	line. You can also set up raw-only queues by simply not associating any PPD with it. This command:
+<screen>
+&prompt;<userinput>lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E</userinput>
+</screen>
+	sets up a queue named <quote>rawprinter</quote>, connected via the <quote>socket</quote> protocol (a.k.a.
+	<quote>HP JetDirect</quote>) to the device at IP address 11.12.1.3.14, using port 9100. (If you had added a
+	PPD with <command>-P /path/to/PPD</command> to this command line, you would have installed a
+	<quote>normal</quote> print queue.)
+	</para>
+
+	<para>
+	CUPS will automatically treat each job sent to a queue as a <quote>raw</quote> one
+	if it can't find a PPD associated with the queue. However, CUPS will
+	only send known MIME types (as defined in its own mime.types file) and
+	refuse others.
+	</para>
+	</sect2>
+
+	<sect2>
+	<title>application/octet-stream Printing</title>
+
+	<para>
+<indexterm><primary>/etc/cups/mime.types</primary></indexterm>
+<indexterm><primary>application/octet-stream</primary></indexterm>
+	Any MIME type with no rule in the <filename>/etc/cups/mime.types</filename> file is regarded as unknown
+	or <parameter>application/octet-stream</parameter> and will not be
+	sent. Because CUPS refuses to print unknown MIME types by default,
+	you will probably have experienced that print jobs originating
+	from Windows clients were not printed. You may have found an error
+	message in your CUPS logs like:
+	</para>
+
+	<para><computeroutput>
+	 Unable to convert file 0 to printable format for job
+	</computeroutput></para>
+
+	<para>
+	To enable the printing of <parameter>application/octet-stream</parameter> files, edit
+	these two files:
+	</para>
+
+	<itemizedlist>
+		<listitem><para><filename>/etc/cups/mime.convs</filename></para></listitem>
+
+		<listitem><para><filename>/etc/cups/mime.types</filename></para></listitem>
+	</itemizedlist>
+
+	<para>
+<indexterm><primary>raw mode</primary></indexterm>
+	Both contain entries (at the end of the respective files) that must be uncommented to allow raw mode
+	operation for <parameter>application/octet-stream</parameter>. In <filename>/etc/cups/mime.types</filename>
+	make sure this line is present:
+	<indexterm><primary>application/octet-stream</primary></indexterm>
+<programlisting>
+application/octet-stream
+</programlisting>
+	This line (with no specific autotyping rule set) makes all files
+	not otherwise auto-typed a member of <parameter>application/octet-stream</parameter>. In
+	<filename>/etc/cups/mime.convs</filename>, have this
+	line: 
+<programlisting>
+application/octet-stream   application/vnd.cups-raw   0   -
+</programlisting>
+	<indexterm><primary>MIME</primary></indexterm>
+	This line tells CUPS to use the <emphasis>Null Filter</emphasis>
+	(denoted as <quote>-</quote>, doing nothing at all) on
+	<parameter>application/octet-stream</parameter>, and tag the result as
+	<parameter>application/vnd.cups-raw</parameter>. This last one is
+	always a green light to the CUPS scheduler to now hand the file over
+	to the backend connecting to the printer and sending it over.
+	</para>
+
+	<note><para>
+	Editing the <filename>mime.convs</filename> and the <filename>mime.types</filename> file does not
+	<emphasis>enforce</emphasis> <quote>raw</quote> printing, it only <emphasis>allows</emphasis> it.
+	</para></note>
+
+	<formalpara>
+	<title>Background</title>
+
+	<para>
+<indexterm><primary>security-aware</primary></indexterm>
+<indexterm><primary>MIME type</primary></indexterm>
+<indexterm><primary>/etc/cups/mime.types</primary></indexterm>
+<indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
+	That CUPS is a more security-aware printing system than traditional ones
+	does not by default allow one to send deliberate (possibly binary)
+	data to printing devices. (This could be easily abused to launch a
+	Denial of Service attack on your printer(s), causing at least the loss
+	of a lot of paper and ink.) <quote>Unknown</quote> data are regarded by CUPS
+	as <emphasis>MIME type</emphasis> <emphasis>application/octet-stream</emphasis>. While you
+	<emphasis>can</emphasis> send data <quote>raw</quote>, the MIME type for these must
+	be one that is known to CUPS and allowed by it. The file
+	<filename>/etc/cups/mime.types</filename> defines the <quote>rules</quote> of how CUPS
+	recognizes MIME types. The file <filename>/etc/cups/mime.convs</filename> decides which file
+	conversion filter(s) may be applied to which MIME types.
+	</para>
+	</formalpara>
+	</sect2>
+
+	<sect2>
+	<title>PostScript Printer Descriptions for Non-PostScript Printers</title>
+
+	<para>
+	<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>non-PostScript</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>RIP</primary></indexterm>
+<indexterm><primary>Ghostscript</primary></indexterm>
+<indexterm><primary>device-specific commands</primary></indexterm>
+	Originally PPDs were meant to be used for PostScript printers
+	only. Here, they help to send device-specific commands and settings
+	to the RIP, which processes the job file. CUPS has extended this
+	scope for PPDs to cover non-PostScript printers too. This was not
+	difficult, because it is a standardized file format. In a way
+	it was logical too: CUPS handles PostScript and uses a PostScript
+	RIP (Ghostscript) to process the job files. The only difference is that
+	a PostScript printer has the RIP built-in, for other types of
+	printers the Ghostscript RIP runs on the host computer.
+	</para>
+
+	<para>
+	PPDs for a non-PostScript printer have a few lines that are unique to
+	CUPS. The most important one looks similar to this:
+	<indexterm><primary>application/vnd.cups-raster</primary></indexterm>
+<programlisting>
+*cupsFilter: application/vnd.cups-raster  66   rastertoprinter
+</programlisting>
+	It is the last piece in the CUPS filtering puzzle. This line tells the
+	CUPS daemon to use as a last filter <parameter>rastertoprinter</parameter>. This filter
+	should be served as input an <parameter>application/vnd.cups-raster</parameter> MIME type
+	file. Therefore, CUPS should autoconstruct a filtering chain, which
+	delivers as its last output the specified MIME type. This is then
+	taken as input to the specified <parameter>rastertoprinter</parameter> filter. After
+	the last filter has done its work (<parameter>rastertoprinter</parameter> is a Gimp-Print
+	filter), the file should go to the backend, which sends it to the
+	output device.
+	</para>
+
+	<para>
+	CUPS by default ships only a few generic PPDs, but they are good for
+	several hundred printer models. You may not be able to control
+	different paper trays, or you may get larger margins than your
+	specific model supports. See Table 21.1<link linkend="cups-ppds"></link> for summary information.
+	</para>
+
+	<table frame="all" id="cups-ppds">
+		<title>PPDs Shipped with CUPS</title>
+		<tgroup cols="2" align="left">
+			<colspec align="left"/>
+			<colspec align="justify" colwidth="1*"/>
+			<thead><row><entry>PPD file</entry><entry>Printer type</entry></row></thead>
+			<tbody>
+			<row><entry>deskjet.ppd</entry><entry>older HP inkjet printers and compatible</entry></row>
+
+			<row><entry>deskjet2.ppd</entry> <entry>newer HP inkjet printers and compatible </entry> </row>
+
+			<row><entry>dymo.ppd</entry> <entry>label printers </entry> </row>
+
+			<row><entry>epson9.ppd</entry> <entry>Epson 24-pin impact printers and compatible </entry> </row>
+
+			<row><entry>epson24.ppd</entry> <entry>Epson 24-pin impact printers and compatible </entry> </row>
+
+			<row><entry>okidata9.ppd</entry> <entry>Okidata 9-pin impact printers and compatible </entry> </row>
+
+			<row><entry>okidat24.ppd</entry> <entry>Okidata 24-pin impact printers and compatible </entry> </row>
+
+			<row><entry>stcolor.ppd</entry> <entry>older Epson Stylus Color printers </entry> </row>
+
+			<row><entry>stcolor2.ppd</entry> <entry>newer Epson Stylus Color printers </entry> </row>
+
+			<row><entry>stphoto.ppd</entry> <entry>older Epson Stylus Photo printers </entry> </row>
+
+			<row><entry>stphoto2.ppd</entry> <entry>newer Epson Stylus Photo printers </entry> </row>
+
+			<row><entry>laserjet.ppd</entry> <entry>all PCL printers </entry> </row>
+
+			</tbody>
+		</tgroup>
+	</table>
+
+	</sect2>
+
+	<sect2>
+	<title><emphasis>cupsomatic/foomatic-rip</emphasis> Versus <emphasis>Native CUPS</emphasis> Printing</title>
+
+	<para>
+	<indexterm><primary>cupsomatic</primary></indexterm>
+	<indexterm><primary>foomatic-rip</primary></indexterm>
+	Native CUPS rasterization works in two steps:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+<indexterm><primary>pstoraster</primary></indexterm>
+		First is the <parameter>pstoraster</parameter> step. It uses the special CUPS
+		<indexterm><primary>ESP</primary><secondary>Ghostscript</secondary></indexterm>
+		device from ESP Ghostscript 7.05.x as its tool.
+		</para></listitem>
+
+		<listitem><para>
+		Second is the <parameter>rasterdriver</parameter> step. It uses various
+		device-specific filters; there are several vendors who provide good
+		quality filters for this step. Some are free software, some are
+		shareware, and some are proprietary.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	Often this produces better quality (and has several more advantages) than other methods.
+	This is shown in <link linkend="cupsomatic-dia"> the cupsomatic/foomatic Processing Versus Native CUPS
+	illustration</link>.
+	</para>
+
+	<figure id="cupsomatic-dia">
+		<title>cupsomatic/foomatic Processing Versus Native CUPS.</title>
+		<imagefile>10small</imagefile>
+	</figure>
+
+	<para>
+	One other method is the <parameter>cupsomatic/foomatic-rip</parameter>
+	way. Note that <parameter>cupsomatic</parameter> is <emphasis>not</emphasis> made by the CUPS
+	developers. It is an independent contribution to printing development,
+	made by people from Linuxprinting.org.<footnote><para>See also <ulink
+	noescape="1" url="http://www.cups.org/cups-help.html">http://www.cups.org/cups-help.html</ulink></para></footnote>
+	<parameter>cupsomatic</parameter> is no longer developed, maintained, or supported. It now been
+	replaced by <parameter>foomatic-rip</parameter>. <parameter>foomatic-rip</parameter> is a complete rewrite
+	of the old <parameter>cupsomatic</parameter> idea, but very much improved and generalized to
+	other (non-CUPS) spoolers. An upgrade to <parameter>foomatic-rip</parameter> is strongly
+	advised, especially if you are upgrading to a recent version of CUPS,
+	too.
+	</para>
+
+	<para>
+	<indexterm><primary>cupsomatic</primary></indexterm>
+	<indexterm><primary>foomatic</primary></indexterm>
+	Like the old <parameter>cupsomatic</parameter> method, the <parameter>foomatic-rip</parameter> (new) method
+	from Linuxprinting.org uses the traditional Ghostscript print file processing, doing everything in a single
+	step. It therefore relies on all the other devices built into Ghostscript. The quality is as good (or bad) as
+	Ghostscript rendering is in other spoolers. The advantage is that this method supports many printer models not
+	supported (yet) by the more modern CUPS method.
+	</para>
+
+	<para>
+	Of course, you can use both methods side by side on one system (and even for one printer, if you set up
+	different queues) and find out which works best for you.
+	</para>
+
+	<para>
+<indexterm><primary>cupsomatic</primary></indexterm>
+<indexterm><primary>pstoraster</primary></indexterm>
+<indexterm><primary>rastertosomething</primary></indexterm>
+<indexterm><primary>rasterization</primary></indexterm>
+<indexterm><primary>Foomatic/cupsomatic</primary></indexterm>
+<indexterm><primary>rendering</primary></indexterm>
+	<parameter>cupsomatic</parameter> kidnaps the print file after the
+	<parameter>application/vnd.cups-postscript</parameter> stage and deviates it through the CUPS-external,
+	systemwide Ghostscript installation. Therefore, the print file bypasses the <parameter>pstoraster</parameter>
+	filter (and also bypasses the CUPS raster drivers <parameter>rastertosomething</parameter>). After Ghostscript
+	finished its rasterization, <parameter>cupsomatic</parameter> hands the rendered file directly to the CUPS
+	backend. <link linkend="cupsomatic-dia">cupsomatic/foomatic Processing Versus Native
+	CUPS</link>, illustrates the difference between native CUPS rendering and the
+	<parameter>Foomatic/cupsomatic</parameter> method.
+	</para>
+	</sect2>
+
+	<sect2>
+	<title>Examples for Filtering Chains</title>
+
+	<para>
+	Here are a few examples of commonly occurring filtering chains to
+	illustrate the workings of CUPS.
+	</para>
+
+	<para>
+<indexterm><primary>HP JetDirect</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>two-up</primary></indexterm>
+<indexterm><primary>duplex</primary></indexterm>
+	Assume you want to print a PDF file to an HP JetDirect-connected
+	PostScript printer, but you want to print pages 3-5, 7, and 11-13
+	only, and you want to print them <quote>two-up</quote> and <quote>duplex</quote>:
+	</para>
+
+	<itemizedlist>
+	<listitem><para>Your print options (page selection as required, two-up,
+	duplex) are passed to CUPS on the command line.</para></listitem>
+
+	<listitem><para>The (complete) PDF file is sent to CUPS and autotyped as
+	<parameter>application/pdf</parameter>.</para></listitem>
+
+	<listitem><para>The file therefore must first pass the
+	<parameter>pdftops</parameter> prefilter, which produces PostScript
+	MIME type <parameter>application/postscript</parameter> (a preview here
+	would still show all pages of the original PDF).</para></listitem>
+
+	<listitem><para>The file then passes the <parameter>pstops</parameter>
+	filter that applies the command-line options: it selects pages
+	2-5, 7, and 11-13, creates the imposed layout <quote>two pages on one sheet</quote>, and
+	inserts the correct <quote>duplex</quote> command (as defined in the printer's
+	PPD) into the new PostScript file; the file is now of PostScript MIME
+	type
+	<parameter>application/vnd.cups-postscript</parameter>.</para></listitem>
+
+	<listitem><para>The file goes to the <parameter>socket</parameter>
+	backend, which transfers the job to the printers.</para></listitem>
+	</itemizedlist>
+
+	<para>
+	The resulting filter chain, therefore, is as shown in <link linkend="pdftosocket">the PDF to socket chain
+	illustration</link>.
+	</para>
+
+<indexterm><primary>pdftosocket</primary></indexterm>
+	<figure id="pdftosocket">
+		<title>PDF to Socket Chain.</title>
+		<imagefile>pdftosocket</imagefile>
+	</figure>
+
+	<para>
+<indexterm><primary>USB</primary></indexterm>
+<indexterm><primary>Epson Stylus</primary></indexterm>
+<indexterm><primary>stphoto2.ppd</primary></indexterm>
+	Assume you want to print the same filter to an USB-connected Epson Stylus Photo Printer installed with the CUPS
+	<filename>stphoto2.ppd</filename>. The first few filtering stages are nearly the same:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Your print options (page selection as required, two-up,
+		duplex) are passed to CUPS on the command line.
+		</para></listitem>
+
+		<listitem><para>
+		The (complete) PDF file is sent to CUPS and autotyped as
+		<parameter>application/pdf</parameter>.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>pdftops</primary></indexterm>
+<indexterm><primary>PDF</primary></indexterm>
+		The file must first pass the <parameter>pdftops</parameter> prefilter, which produces PostScript
+		MIME type <parameter>application/postscript</parameter> (a preview here would still show all
+		pages of the original PDF).
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>pstops</primary></indexterm>
+<indexterm><primary>duplex printing</primary></indexterm>
+		The file then passes the <quote>pstops</quote> filter that applies
+		the command-line options: it selects the pages 2-5, 7, and 11-13,
+		creates the imposed layout <quote>two pages on one sheet,</quote> and inserts the
+		correct <quote>duplex</quote> command (oops &smbmdash; this printer and PPD
+		do not support duplex printing at all, so this option will
+		be ignored) into the new PostScript file; the file is now of PostScript
+		MIME type <parameter>application/vnd.cups-postscript</parameter>.
+		</para></listitem>
+
+		<listitem><para>
+		The file then passes the <parameter>pstoraster</parameter> stage and becomes MIME type
+		<parameter>application/cups-raster</parameter>.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>rastertoepson</primary></indexterm>
+		Finally, the <parameter>rastertoepson</parameter> filter
+		does its work (as indicated in the printer's PPD), creating the
+		printer-specific raster data and embedding any user-selected
+		print options into the print data stream.
+		</para></listitem>
+
+		<listitem><para>
+		The file goes to the <parameter>usb</parameter> backend, which transfers the job to the printers.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	The resulting filter chain therefore is as shown in <link linkend="pdftoepsonusb">the PDF to USB Chain
+	illustration</link>.
+	</para>
+
+	<figure id="pdftoepsonusb">
+		<title>PDF to USB Chain.</title>
+		<imagefile>pdftoepsonusb</imagefile>
+	</figure>
+	</sect2>
+
+	<sect2>
+	<title>Sources of CUPS Drivers/PPDs</title>
+
+	<para>
+	On the Internet you can now find many thousands of CUPS-PPD files
+	(with their companion filters), in many national languages
+	supporting more than 1,000 non-PostScript models.
+	</para>
+
+	<itemizedlist>
+		<indexterm><primary>ESP</primary><secondary>Print Pro</secondary></indexterm>
+		<indexterm><primary>PrintPro</primary><see>ESP Print Pro</see></indexterm>
+		<listitem><para>
+		<ulink url="http://www.easysw.com/printpro/">ESP PrintPro</ulink>
+		(commercial, non-free) is packaged with more than 3,000 PPDs, ready for
+		successful use <quote>out of the box</quote> on Linux, Mac OS X, IBM-AIX,
+		HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital UNIX, and
+		other commercial Unices (it is written by the CUPS developers
+		themselves and its sales help finance the further development of
+		CUPS, as they feed their creators).
+		</para></listitem>
+
+		<listitem><para>
+		The <ulink url="http://gimp-print.sourceforge.net/">Gimp-Print Project</ulink>
+		(GPL, free software) provides around 140 PPDs (supporting nearly 400 printers, many driven
+		to photo quality output), to be used alongside the Gimp-Print CUPS filters.
+		</para></listitem>
+
+		<listitem><para>
+		<ulink url="http://www.turboprint.de/english.html/">TurboPrint </ulink> (shareware, non-free) supports
+		roughly the same number of printers in excellent quality.
+		</para></listitem>
+
+		<listitem><para>
+		<ulink url="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/">OMNI </ulink>
+		(LPGL, free) is a package made by IBM, now containing support for more
+		than 400 printers, stemming from the inheritance of IBM OS/2 know-how
+		ported over to Linux (CUPS support is in a beta stage at present).
+		</para></listitem>
+
+		<listitem><para>
+		<ulink url="http://hpinkjet.sourceforge.net/">HPIJS </ulink> (BSD-style licenses, free)
+		supports approximately 150 of HP's own printers and also provides
+		excellent print quality now (currently available only via the Foomatic path).
+		</para></listitem>
+
+		<listitem><para>
+		<ulink url="http://www.linuxprinting.org/">Foomatic/cupsomatic </ulink>
+		(LPGL, free) from Linuxprinting.org provide PPDs for practically every Ghostscript
+		filter known to the world (including Omni, Gimp-Print, and HPIJS).
+		</para></listitem>
+	</itemizedlist>
+
+	</sect2>
+
+	<sect2>
+	<title>Printing with Interface Scripts</title>
+
+	<para>
+<indexterm><primary>PCL</primary></indexterm>
+<indexterm><primary>lpadmin</primary></indexterm>
+	CUPS also supports the use of <quote>interface scripts</quote> as known from
+	System V AT&amp;T printing systems. These are often used for PCL
+	printers, from applications that generate PCL print jobs. Interface
+	scripts are specific to printer models. They have a role similar to
+	PPDs for PostScript printers. Interface scripts may inject the Escape
+	sequences as required into the print data stream if the user, for example, selects
+	a certain paper tray, or changes paper orientation, or uses A3
+	paper. Interface scripts are practically unknown in the Linux
+	realm. On HP-UX platforms they are more often used. You can use any
+	working interface script on CUPS too. Just install the printer with
+	the <command>-i</command> option:
+<screen>
+&rootprompt;<userinput>lpadmin -p pclprinter -v socket://11.12.13.14:9100 \
+          -i /path/to/interface-script</userinput>
+</screen></para>
+
+	<para>
+	Interface scripts might be the <quote>unknown animal</quote> to many. However,
+	with CUPS they provide the easiest way to plug in your own custom-written filtering
+	script or program into one specific print queue (some information about the traditional
+	use of interface scripts is found at
+	<ulink noescape="1" url="http://playground.sun.com/printing/documentation/interface.html">
+	http://playground.sun.com/printing/documentation/interface.html</ulink>).
+	</para>
+	</sect2>
+</sect1>
+
+<sect1>
+<title>Network Printing (Purely Windows)</title>
+
+<para>
+Network printing covers a lot of ground. To understand what exactly
+goes on with Samba when it is printing on behalf of its Windows
+clients, let's first look at a <quote>purely Windows</quote> setup: Windows clients
+with a Windows NT print server.
+</para>
+
+<sect2>
+<title>From Windows Clients to an NT Print Server</title>
+
+<para>
+Windows clients printing to an NT-based print server have two
+options. They may:
+<indexterm><primary>GDI</primary></indexterm>
+<indexterm><primary>EMF</primary></indexterm>
+</para>
+
+
+<itemizedlist>
+	<listitem><para>Execute the driver locally and render the GDI output
+			(EMF) into the printer-specific format on their own.
+	</para></listitem>
+
+	<listitem><para>Send the GDI output (EMF) to the server, where the
+	driver is executed to render the printer-specific output.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+Both print paths are shown in the flowcharts in <link linkend="small11">
+Print Driver Execution on the Client</link>, and
+<link linkend="small12">Print Driver Execution on the Server</link>.
+</para>
+</sect2>
+
+<sect2>
+<title>Driver Execution on the Client</title>
+
+<para>
+In the first case, the print server must spool the file as raw, meaning it shouldn't touch the job file and try
+to convert it in any way. This is what a traditional UNIX-based print server can do too, and at a better
+performance and more reliably than an NT print server. This is what most Samba administrators probably are
+familiar with. One advantage of this setup is that this <quote>spooling-only</quote> print server may be used
+even if no driver(s) for UNIX is available. It is sufficient to have the Windows client drivers available and
+installed on the clients. This is illustrated in <link linkend="small11">the Print Driver Execution on the
+Client diagram</link>.
+</para>
+
+<figure id="small11">
+	<title>Print Driver Execution on the Client.</title>
+	<imagefile>11small</imagefile>
+</figure>
+
+</sect2>
+
+<sect2>
+<title>Driver Execution on the Server</title>
+
+
+<para>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>PCL</primary></indexterm>
+<indexterm><primary>ESC/P</primary></indexterm>
+<indexterm><primary>EMF</primary></indexterm>
+<indexterm><primary>GDI</primary></indexterm>
+The other path executes the printer driver on the server. The client transfers print files in EMF format to
+the server. The server uses the PostScript, PCL, ESC/P, or other driver to convert the EMF file into the
+printer-specific language. It is not possible for UNIX to do the same. Currently, there is no program or
+method to convert a Windows client's GDI output on a UNIX server into something a printer could understand.
+This is illustrated in <link linkend="small12">the Print Driver Execution on the Server diagram</link>.
+</para>
+
+	<figure id="small12">
+		<title>Print Driver Execution on the Server.</title>
+		<imagefile>12small</imagefile>
+	</figure>
+
+<para>
+However, something similar is possible with CUPS, so read on.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Network Printing (Windows Clients and UNIX/Samba Print
+Servers)</title>
+
+<para>
+Since UNIX print servers <emphasis>cannot</emphasis> execute the Win32
+program code on their platform, the picture is somewhat
+different. However, this does not limit your options all that
+much. On the contrary, you may have a way here to implement printing
+features that are not possible otherwise.
+</para>
+
+<sect2>
+<title>From Windows Clients to a CUPS/Samba Print Server</title>
+
+<para>
+Here is a simple recipe showing how you can take advantage of CUPS's
+powerful features for the benefit of your Windows network printing
+clients:
+</para>
+
+<itemizedlist>
+	<listitem><para>Let the Windows clients send PostScript to the CUPS
+	server.</para></listitem>
+
+	<listitem><para>Let the CUPS server render the PostScript into device-specific raster format.</para></listitem>
+</itemizedlist>
+
+<para>
+This requires the clients to use a PostScript driver (even if the
+printer is a non-PostScript model. It also requires that you have a
+driver on the CUPS server.
+</para>
+
+<para>
+First, to enable CUPS-based printing through Samba, the following options should be set in your &smb.conf;
+file <parameter>[global]</parameter> section:
+</para>
+
+<smbconfblock>
+<smbconfoption name="printing">cups</smbconfoption>
+<smbconfoption name="printcap">cups</smbconfoption>
+</smbconfblock>
+
+<para>
+When these parameters are specified, all manually set print directives (like <smbconfoption name="print
+command"/> or <smbconfoption name="lppause command"/>) in &smb.conf; (as well as in Samba itself) will be
+ignored. Instead, Samba will directly interface with CUPS through its application program interface (API), as
+long as Samba has been compiled with CUPS library (libcups) support. If Samba has not been compiled with CUPS
+support, and if no other print commands are set up, then printing will use the <emphasis>System V</emphasis>
+AT&amp;T command set, with the -oraw option automatically passing through (if you want your own defined print
+commands to work with a Samba server that has CUPS support compiled in, simply use <smbconfoption
+name="classicalprinting">sysv</smbconfoption>). This is illustrated in <link linkend="13small">the Printing via
+CUPS/Samba Server diagram</link>.
+</para>
+
+	<figure id="13small">
+		<title>Printing via CUPS/Samba Server.</title>
+		<imagefile>13small</imagefile>
+	</figure>
+</sect2>
+
+<sect2>
+<title>Samba Receiving Job-Files and Passing Them to CUPS</title>
+
+<para>
+Samba <emphasis>must</emphasis> use its own spool directory (it is set by a line similar to <smbconfoption
+name="path">/var/spool/samba</smbconfoption>, in the <smbconfsection name="[printers]"/> or <smbconfsection
+name="[printername]"/> section of &smb.conf;). Samba receives the job in its own spool space and passes it
+into the spool directory of CUPS (the CUPS spool directory is set by the <parameter>RequestRoot</parameter>
+directive in a line that defaults to <parameter>RequestRoot /var/spool/cups</parameter>). CUPS checks the
+access rights of its spool directory and resets it to healthy values with every restart. We have seen quite a
+few people who used a common spooling space for Samba and CUPS, and struggled for weeks with this
+<quote>problem.</quote>
+</para>
+
+<para>
+A Windows user authenticates only to Samba (by whatever means is
+configured). If Samba runs on the same host as CUPS, you only need to
+allow <quote>localhost</quote> to print. If it runs on different machines, you
+need to make sure the Samba host gets access to printing on CUPS.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Network PostScript RIP</title>
+
+<para>
+This section discusses the use of CUPS filters on the server &smbmdash; configuration where
+clients make use of a PostScript driver with CUPS-PPDs.
+</para>
+
+
+<para>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>PCL</primary></indexterm>
+<indexterm><primary>PJL</primary></indexterm>
+PPDs can control all print device options. They are usually provided by the manufacturer &smbmdash; if you own
+a PostScript printer, that is. PPD files are always a component of PostScript printer drivers on MS Windows or
+Apple Mac OS systems. They are ASCII files containing user-selectable print options, mapped to appropriate
+PostScript, PCL, or PJL commands for the target printer. Printer driver GUI dialogs translate these options
+<quote>on the fly</quote> into buttons and drop-down lists for the user to select.
+</para>
+
+<para>
+CUPS can load, without any conversions, the PPD file from any Windows (NT is recommended) PostScript driver
+and handle the options. There is a Web browser interface to the print options (select <ulink noescape="1"
+url="http://localhost:631/printers/">http://localhost:631/printers/</ulink> and click on one
+<guibutton>Configure Printer</guibutton> button to see it) or a command-line interface (see <command>man
+lpoptions</command> or see if you have <command>lphelp</command> on your system). There are also some
+different GUI front-ends on Linux/UNIX, which can present PPD options to users. PPD options are normally meant
+to be evaluated by the PostScript RIP on the real PostScript printer.
+</para>
+
+<sect2>
+<title>PPDs for Non-PS Printers on UNIX</title>
+
+
+<para>
+<indexterm><primary>PPD</primary></indexterm>
+CUPS does not limit itself to <quote>real</quote> PostScript printers in its use of PPDs. The CUPS developers
+have extended the scope of the PPD concept to also describe available device and driver options for
+non-PostScript printers through CUPS-PPDs.
+</para>
+
+<para>
+This is logical, because CUPS includes a fully featured PostScript interpreter (RIP). This RIP is based on
+Ghostscript. It can process all received PostScript (and additionally many other file formats) from clients.
+All CUPS-PPDs geared to non-PostScript printers contain an additional line, starting with the keyword
+<parameter>*cupsFilter</parameter>. This line tells the CUPS print system which printer-specific filter to use
+for the interpretation of the supplied PostScript. Thus CUPS lets all its printers appear as PostScript
+devices to its clients, because it can act as a PostScript RIP for those printers, processing the received
+PostScript code into a proper raster print format.
+</para>
+</sect2>
+
+<sect2>
+<title>PPDs for Non-PS Printers on Windows</title>
+
+<para>
+<indexterm><primary>PPD</primary></indexterm>
+CUPS-PPDs can also be used on Windows clients, on top of a <quote>core</quote> PostScript driver (now
+recommended is the CUPS PostScript Driver for Windows NT/200x/XP; you can also use the Adobe one, with
+limitations). This feature enables CUPS to do a few tricks no other spooler can do:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Act as a networked PostScript RIP handling print files from all client platforms in a uniform way.
+	</para></listitem>
+
+	<listitem><para>
+	Act as a central accounting and billing server, since all files are passed through the pstops filter and are therefore
+	logged in the CUPS <filename>page_log</filename> file.  <emphasis>Note:</emphasis> this cannot happen with
+	<quote>raw</quote> print jobs, which always remain unfiltered per definition.
+	</para></listitem>
+
+	<listitem><para>
+	Enable clients to consolidate on a single PostScript driver, even for many different target printers.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+Using CUPS PPDs on Windows clients enables them to control all print job settings just as a UNIX client can do.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Windows Terminal Servers (WTS) as CUPS Clients</title>
+
+<para>
+This setup may be of special interest to people experiencing major problems in WTS environments. WTS often
+need a multitude of non-PostScript drivers installed to run their clients' variety of different printer
+models. This often imposes the price of much increased instability.
+</para>
+
+<sect2>
+<title>Printer Drivers Running in <quote>Kernel Mode</quote> Cause Many
+Problems</title>
+
+<para>
+Windows NT printer drivers, which run in <quote>kernel mode</quote>, introduce a high risk for the stability
+of the system if the driver is not really stable and well-tested. And there are a lot of bad drivers out
+there! Especially notorious is the example of the PCL printer driver that had an additional sound module
+running to notify users via soundcard of their finished jobs. Do I need to say that this one was also reliably
+causing <quote>blue screens of death</quote> on a regular basis?
+</para>
+
+<para>
+PostScript drivers are generally well-tested. They are not known to cause any problems, even though they also
+run in kernel mode. This might be because until now there have been only two different PostScript drivers: the
+one from Adobe and the one from Microsoft. Both are well-tested and are as stable as you can imagine on
+Windows. The CUPS driver is derived from the Microsoft one.
+</para>
+</sect2>
+
+<sect2>
+<title>Workarounds Impose Heavy Limitations</title>
+
+<para>
+In an attempt to work around problems, site administrators have resorted to restricting the
+allowed drivers installed on their WTS to one generic PCL and one PostScript driver. This, however, restricts
+the number of printer options available for clients to use. Often they can't get out more than simplex
+prints from one standard paper tray, while their devices could do much better if driven by a different driver!
+</para>
+</sect2>
+
+<sect2>
+<title>CUPS: A <quote>Magical Stone</quote>?</title>
+
+<para>
+<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very elegant way to overcome all these
+shortcomings. There are, depending on the version of Windows OS you use, up to three different PostScript
+drivers now available: Adobe, Microsoft, and CUPS PostScript drivers. None of them is known to cause major
+stability problems on WTS (even if used with many different PPDs). The clients will be able to (again) choose
+paper trays, duplex printing, and other settings. However, there is a certain price for this too: a CUPS
+server acting as a PostScript RIP for its clients requires more CPU and RAM than when just acting as a
+<quote>raw spooling</quote> device. Plus, this setup is not yet widely tested, although the first feedbacks
+look very promising.
+</para>
+</sect2>
+
+<sect2>
+<title>PostScript Drivers with No Major Problems, Even in Kernel
+Mode</title>
+
+<para>
+<indexterm><primary>DDK</primary></indexterm>
+<indexterm><primary>W32X86</primary></indexterm>
+<indexterm><primary>PostScript</primary></indexterm>
+<indexterm><primary>Visual Studio</primary></indexterm>
+<indexterm><primary>Microsoft driver</primary></indexterm>
+<indexterm><primary>Adobe</primary></indexterm>
+More recent printer drivers on W200x and XP no longer run in kernel mode (unlike Windows NT). However, both
+operating systems can still use the NT drivers, running in kernel mode (you can roughly tell which is which as
+the drivers in subdirectory <quote>2</quote> of <quote>W32X86</quote> are <quote>old</quote> ones). As was
+said before, the Adobe as well as the Microsoft PostScript drivers are not known to cause any stability
+problems. The CUPS driver is derived from the Microsoft one. There is a simple reason for this: the MS DDK
+(Device Development Kit) for Windows NT (which used to be available at no cost to licensees of Visual Studio)
+includes the source code of the Microsoft driver, and licensees of Visual Studio are allowed to use and modify
+it for their own driver development efforts. This is what the CUPS people have done. The license does not
+allow them to publish the whole of the source code.  However, they have released the <quote>diff</quote> under
+the GPL, and if you are the owner of an <quote>MS DDK for Windows NT,</quote> you can check the driver
+yourself.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Configuring CUPS for Driver Download</title>
+
+<para>
+As we have said before, all previously known methods to prepare client printer drivers on the Samba server for
+download and Point'n'Print convenience of Windows workstations are working with CUPS, too. These methods were
+described in <link linkend="classicalprinting">Classical Printing</link>. In reality, this is a pure Samba
+business and relates only to the Samba-Windows client relationship.
+</para>
+
+<sect2>
+<title><emphasis>cupsaddsmb</emphasis>: The Unknown Utility</title>
+
+
+<para>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+The <parameter>cupsaddsmb</parameter> utility (shipped with all current CUPS versions) is an alternative
+method to transfer printer drivers into the Samba <smbconfsection name="[print$]"/> share. Remember, this
+share is where clients expect drivers deposited and set up for download and installation. It makes the sharing
+of any (or all) installed CUPS printers quite easy. <command>cupsaddsmb</command> can use the Adobe PostScript
+driver as well as the newly developed CUPS PostScript driver for Windows NT/200x/XP.
+<parameter>cupsaddsmb</parameter> does <emphasis>not</emphasis> work with arbitrary vendor printer drivers,
+but only with the <emphasis>exact</emphasis> driver files that are named in its man page.
+</para>
+
+<para>
+The CUPS printer driver is available from the CUPS download site. Its package name is
+<filename>cups-samba-[version].tar.gz</filename>. It is preferred over the Adobe drivers because it has a
+number of advantages:
+</para>
+
+<itemizedlist>
+	<listitem><para>It supports a much more accurate page accounting.</para></listitem>
+
+	<listitem><para>It supports banner pages and page labels on all printers.</para></listitem>
+
+	<listitem><para>It supports the setting of a number of job IPP attributes
+	(such as job priority, page label, and job billing).</para></listitem>
+</itemizedlist>
+
+<para>
+However, currently only Windows NT, 2000, and XP are supported by the
+CUPS drivers. You will also need to get the respective part of the Adobe driver
+if you need to support Windows 95, 98, and Me clients.
+</para>
+</sect2>
+
+<sect2>
+<title>Prepare Your &smb.conf; for <command>cupsaddsmb</command></title>
+
+<para>
+Prior to running <command>cupsaddsmb</command>, you need the settings in
+&smb.conf; as shown in <link linkend="cupsadd-ex">the &smb.conf; for cupsaddsmb Usage</link>.
+</para>
+
+<example id="cupsadd-ex">
+<title>smb.conf for cupsaddsmb Usage</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="load printers">yes</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="browseable">no</smbconfoption>
+<smbconfoption name="public">yes</smbconfoption>
+<smbconfcomment>setting depends on your requirements</smbconfcomment>
+<smbconfoption name="guest ok">yes</smbconfoption>
+<smbconfoption name="writable">no</smbconfoption>
+<smbconfoption name="printable">yes</smbconfoption>
+<smbconfoption name="printer admin">root</smbconfoption>
+ <smbconfsection name="[print$]"/>
+<smbconfoption name="comment">Printer Drivers</smbconfoption>
+<smbconfoption name="path">/etc/samba/drivers</smbconfoption>
+<smbconfoption name="browseable">yes</smbconfoption>
+<smbconfoption name="guest ok">no</smbconfoption>
+<smbconfoption name="read only">yes</smbconfoption>
+<smbconfoption name="write list">root</smbconfoption>
+</smbconfblock>
+</example>
+</sect2>
+
+<sect2>
+<title>CUPS <quote>PostScript Driver for Windows NT/200x/XP</quote></title>
+
+<para>
+<indexterm><primary>PostScript</primary></indexterm>
+CUPS users may get the exact same package from <ulink noescape="1"
+url="http://www.cups.org/software.html">http://www.cups.org/software.html</ulink>.  It is a separate package
+from the CUPS-based software files, tagged as CUPS 1.1.x Windows NT/200x/XP Printer Driver for Samba (tar.gz,
+192k). The filename to download is <filename>cups-samba-1.1.x.tar.gz</filename>. Upon untar and unzipping, it
+will reveal these files:
+<screen>
+&rootprompt;<userinput>tar xvzf cups-samba-1.1.19.tar.gz</userinput>
+cups-samba.install
+cups-samba.license
+cups-samba.readme
+cups-samba.remove
+cups-samba.ss
+</screen></para>
+
+<para>
+<indexterm><primary>ESP</primary><secondary>meta packager</secondary></indexterm>
+<indexterm><primary>EPM</primary><see>ESP meta packager</see></indexterm>
+These have been packaged with the ESP meta-packager software EPM. The <filename>*.install</filename> and
+<filename>*.remove</filename> files are simple shell scripts, which untar the <filename>*.ss</filename> (the
+<filename>*.ss</filename> is nothing else but a tar archive, which can be untarred by <quote>tar</quote> too).
+Then it puts the content into <filename>/usr/share/cups/drivers/</filename>. This content includes three
+files:
+<screen>
+&rootprompt;<userinput>tar tv cups-samba.ss</userinput>
+cupsdrvr.dll
+cupsui.dll
+cups.hlp  
+</screen></para>
+
+<para>
+The <parameter>cups-samba.install</parameter> shell scripts are easy to
+handle:
+<screen>
+&rootprompt;<userinput>./cups-samba.install</userinput>
+[....]
+Installing software...
+Updating file permissions...
+Running post-install commands...
+Installation is complete.       
+</screen></para>
+
+<para>
+The script should automatically put the driver files into the
+<filename>/usr/share/cups/drivers/</filename> directory:
+<screen>
+&rootprompt;<userinput>cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/</userinput>
+</screen></para>
+
+<warning><para>
+Due to a bug, one recent CUPS release puts the <filename>cups.hlp</filename> driver file
+into<filename>/usr/share/drivers/</filename> instead of <filename>/usr/share/cups/drivers/</filename>. To work
+around this, copy/move the file (after running the <command>./cups-samba.install</command> script) manually to
+the correct place.
+</para></warning>
+
+<para>
+<indexterm><primary>DDK</primary></indexterm>
+This new CUPS PostScript driver is currently binary only, but free of charge. No complete source code is
+provided (yet). The reason is that it has been developed with the help of the Microsoft DDK and compiled with
+Microsoft Visual Studio 6. Driver developers are not allowed to distribute the whole of the source code as
+free software. However, CUPS developers released the <quote>diff</quote> in source code under the GPL, so
+anybody with a license for Visual Studio and a DDK will be able to compile for himself or herself.
+</para>
+</sect2>
+
+<sect2>
+<title>Recognizing Different Driver Files</title>
+
+<para>
+The CUPS drivers do not support the older Windows 95/98/Me, but only the Windows NT/2000/XP client.
+</para>
+
+<para>Windows NT, 2000, and XP are supported by:</para>
+
+<itemizedlist>
+	<listitem><para>cups.hlp</para></listitem>
+	<listitem><para>cupsdrvr.dll</para></listitem>
+	<listitem><para>cupsui.dll</para></listitem>
+</itemizedlist>
+
+<para>
+Adobe drivers are available for the older Windows 95/98/Me as well as
+for Windows NT/2000/XP clients. The set of files is different from the
+different platforms.
+</para>
+
+<para>Windows 95, 98, and ME are supported by:</para>
+
+<itemizedlist>
+	<listitem><para>ADFONTS.MFM</para></listitem>
+	<listitem><para>ADOBEPS4.DRV</para></listitem>
+	<listitem><para>ADOBEPS4.HLP</para></listitem>
+	<listitem><para>DEFPRTR2.PPD</para></listitem>
+	<listitem><para>ICONLIB.DLL</para></listitem>
+	<listitem><para>PSMON.DLL</para></listitem>
+</itemizedlist>
+
+<para>Windows NT, 2000, and XP are supported by:</para>
+
+<itemizedlist>
+	<listitem><para>ADOBEPS5.DLL</para></listitem>
+	<listitem><para>ADOBEPSU.DLL</para></listitem>
+	<listitem><para>ADOBEPSU.HLP</para></listitem>
+</itemizedlist>
+
+<note><para>
+<indexterm><primary>Adobe driver files</primary></indexterm>
+If both the Adobe driver files and the CUPS driver files for the support of Windows NT/200x/XP are presently
+installed on the server, the Adobe files will be ignored and the CUPS files will be used. If you prefer
+&smbmdash; for whatever reason &smbmdash; to use Adobe-only drivers, move away the three CUPS driver files.
+The Windows 9x/Me clients use the Adobe drivers in any case.
+</para></note>
+</sect2>
+
+<sect2>
+<title>Acquiring the Adobe Driver Files</title>
+
+<para>
+Acquiring the Adobe driver files seems to be unexpectedly difficult for many users. They are not available on
+the Adobe Web site as single files, and the self-extracting and/or self-installing Windows-.exe is not easy to
+locate either. You probably need to use the included native installer and run the installation process on one
+client once. This will install the drivers (and one generic PostScript printer) locally on the client. When
+they are installed, share the generic PostScript printer. After this, the client's <smbconfsection
+name="[print$]"/> share holds the Adobe files, which you can get with smbclient from the CUPS host.
+</para>
+</sect2>
+
+<sect2>
+<title>ESP Print Pro PostScript Driver for Windows NT/200x/XP</title>
+
+<para>
+<indexterm><primary>ESP</primary><secondary>Print Pro</secondary></indexterm>
+Users of the ESP Print Pro software are able to install the ESP print drivers package as an alternative to the
+Adobe PostScript drivers.  To do so, retrieve the driver files from the normal download area of the ESP Print
+Pro software at <ulink noescape="1" url="http://www.easysw.com/software.html">Easy Software</ulink> web site.
+You need to locate the link labeled <quote>SAMBA</quote> among the <guilabel>Download Printer Drivers for ESP
+Print Pro 4.x</guilabel> area and download the package. Once installed, you can prepare any driver by simply
+highlighting the printer in the Printer Manager GUI and selecting <guilabel>Export Driver...</guilabel> from
+the menu. Of course, you need to have prepared Samba beforehand to handle the driver files; that is, set up
+the <smbconfsection name="[print$]"/> share, and so on. The ESP Print Pro package includes the CUPS driver
+files as well as a (licensed) set of Adobe drivers for the Windows 95/98/Me client family.
+</para>
+</sect2>
+
+<sect2>
+<title>Caveats to Be Considered</title>
+
+
+<para>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+<indexterm><primary>cups.hlp</primary></indexterm>
+<indexterm><primary>WIN40</primary></indexterm>
+<indexterm><primary>W32X86</primary></indexterm>
+Once you have run the install script (and possibly manually moved the <filename>cups.hlp</filename> file to
+<filename>/usr/share/cups/drivers/</filename>), the driver is ready to be put into Samba's <smbconfsection
+name="[print$]"/> share (which often maps to <filename>/etc/samba/drivers/</filename> and contains a
+subdirectory tree with <emphasis>WIN40</emphasis> and <emphasis>W32X86</emphasis> branches). You do this by
+running <command>cupsaddsmb</command> (see also <command>man cupsaddsmb</command> for CUPS since release
+1.1.16).
+</para>
+
+<tip><para>
+<indexterm><primary>Single Sign-On</primary></indexterm>
+<indexterm><primary>Domain Controller</primary></indexterm>
+You may need to put root into the smbpasswd file by running <command>smbpasswd</command>; this is especially
+important if you should run this whole procedure for the first time and are not working in an environment
+where everything is configured for <emphasis>single sign-on</emphasis> to a Windows Domain Controller.
+</para></tip>
+
+<para>
+Once the driver files are in the <smbconfsection name="[print$]"/> share and are initialized, they are ready
+to be downloaded and installed by the Windows NT/200x/XP clients.
+</para>
+
+<note><para>
+Win 9x/Me clients will not work with the CUPS PostScript driver. For these you still need to use the
+<filename>ADOBE*.*</filename> drivers, as previously stated.
+</para></note>
+
+<note>
+<para>
+It is not harmful if you still have the <filename>ADOBE*.*</filename> driver files from previous installations
+in the <filename>/usr/share/cups/drivers/</filename> directory. The new <command>cupsaddsmb</command> (from
+1.1.16) will automatically prefer its own drivers if it finds both.
+</para></note>
+
+<note><para>
+<indexterm><primary>"Printers" folder</primary></indexterm>
+<indexterm><primary>Adobe PostScript</primary></indexterm>
+Should your Windows clients have had the old <filename>ADOBE*.*</filename> files for the Adobe PostScript
+driver installed, the download and installation of the new CUPS PostScript driver for Windows NT/200x/XP will
+fail at first. You need to wipe the old driver from the clients first. It is not enough to
+<quote>delete</quote> the printer, because the driver files will still be kept by the clients and re-used if
+you try to re-install the printer. To really get rid of the Adobe driver files on the clients, open the
+<guilabel>Printers</guilabel> folder (possibly via <guilabel>Start -> Settings -> Control Panel ->
+Printers</guilabel>), right-click on the folder background, and select <guimenuitem>Server
+Properties</guimenuitem>. When the new dialog opens, select the <guilabel>Drivers</guilabel> tab. On the list
+select the driver you want to delete and click the <guilabel>Delete</guilabel> button. This will only work if
+there is not one single printer left that uses that particular driver. You need to <quote>delete</quote> all
+printers using this driver in the <guilabel>Printers</guilabel> folder first. You will need Administrator
+privileges to do this.
+</para></note>
+
+<note><para>
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+<indexterm><primary>CUPS PostScript</primary></indexterm>
+Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all
+printers to this one by proceeding as described in <link linkend="classicalprinting">Classical Printing
+Support</link>. Either change a driver for an existing printer by running the <guilabel>Printer
+Properties</guilabel> dialog, or use <command>rpcclient</command> with the <command>setdriver</command>
+subcommand.
+</para></note>
+</sect2>
+
+<sect2>
+<title>Windows CUPS PostScript Driver Versus Adobe Driver</title>
+
+<para>
+Are you interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes, these
+are the most important items that weigh in favor of CUPS:
+</para>
+
+<itemizedlist>
+	<listitem><para>No hassle with the Adobe EULA.</para></listitem>
+
+	<listitem><para>No hassle with the question, <quote>Where do I
+	get the ADOBE*.* driver files?</quote></para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>PJL</primary></indexterm>
+	The Adobe drivers (on request of the printer PPD associated with them) often put a PJL header in front of the
+	main PostScript part of the print file. Thus, the print file starts with <parameter>&lt;1B
+	&gt;%-12345X</parameter> or <parameter>&lt;escape&gt;%-12345X</parameter> instead of
+	<parameter>%!PS</parameter>. This leads to the CUPS daemon autotyping the incoming file as a print-ready file,
+	not initiating a pass through the <parameter>pstops</parameter> filter (to speak more technically, it is not
+	regarded as the generic MIME-type <indexterm><primary>application/postscript</primary></indexterm>
+	<parameter>application/postscript</parameter>, but as the more special MIME type
+	<indexterm><primary>application/cups.vnd-postscript</primary></indexterm>
+	<parameter>application/cups.vnd-postscript</parameter>), which therefore also leads to the page accounting in
+	<parameter>/var/log/cups/page_log</parameter> not receiving the exact number of pages; instead the dummy page
+	number of <quote>1</quote> is logged in a standard setup).
+	</para></listitem>
+
+	<listitem><para>The Adobe driver has more options to misconfigure the
+<indexterm><primary>Adobe driver</primary></indexterm>
+	PostScript generated by it (like setting it inadvertently to
+	<guilabel>Optimize for Speed</guilabel> instead of
+	<guilabel>Optimize for Portability</guilabel>, which
+	could lead to CUPS being unable to process it).</para></listitem>
+
+	<listitem><para>The CUPS PostScript driver output sent by Windows
+<indexterm><primary>CUPS PostScript driver</primary></indexterm>
+	clients to the CUPS server is guaranteed to autotype 
+	as the generic MIME type <parameter>application/postscript</parameter>,
+	thus passing through the CUPS <parameter>pstops</parameter> filter and logging the
+	correct number of pages in the <filename>page_log</filename> for
+	accounting and quota purposes.</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>banner pages</primary></indexterm>
+	The CUPS PostScript driver supports the sending of additional standard (IPP) print options by Windows
+	NT/200x/XP clients. Such additional print options are naming the CUPS standard <emphasis>banner
+	pages</emphasis> (or the custom ones, should they be installed at the time of driver download), using the CUPS
+	page-label option, setting a job priority, and setting the scheduled time of printing (with the option to
+	support additional useful IPP job attributes in the future).
+	</para></listitem>
+
+	<listitem><para>The CUPS PostScript driver supports the inclusion of
+	the new <parameter>*cupsJobTicket</parameter> comments at the
+	beginning of the PostScript file (which could be used in the future
+	for all sorts of beneficial extensions on the CUPS side, but which will
+	not disturb any other applications because they will regard it as a comment
+	and simply ignore it).</para></listitem>
+
+	<listitem><para>The CUPS PostScript driver will be the heart of the
+	fully fledged CUPS IPP client for Windows NT/200x/XP to be released soon
+	(probably alongside the first beta release for CUPS 1.2).</para></listitem>
+</itemizedlist>
+
+</sect2>
+
+<sect2>
+<title>Run cupsaddsmb (Quiet Mode)</title>
+
+
+<para>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+<indexterm><primary>point 'n' print</primary></indexterm>
+The <command>cupsaddsmb</command> command copies the needed files into your <smbconfsection name="[print$]"/>
+share. Additionally, the PPD associated with this printer is copied from <filename>/etc/cups/ppd/</filename>
+to <smbconfsection name="[print$]"/>. There the files wait for convenient Windows client installations via
+Point'n'Print. Before we can run the command successfully, we need to be sure that we can authenticate toward
+Samba. If you have a small network, you are probably using user-level security (<smbconfoption
+name="security">user</smbconfoption>).
+</para>
+
+<para>
+Here is an example of a successfully run <command>cupsaddsmb</command> command: 
+<indexterm><primary>banner pages</primary></indexterm>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+<screen>
+&rootprompt;<userinput>cupsaddsmb -U root infotec_IS2027</userinput>
+Password for root required to access localhost via Samba: <userinput>['secret']</userinput>
+</screen></para>
+
+<para>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+To share <emphasis>all</emphasis> printers and drivers, use the
+<option>-a</option> parameter instead of a printer name. Since
+<command>cupsaddsmb</command> <quote>exports</quote> the printer drivers to Samba, it should be
+obvious that it only works for queues with a CUPS driver associated.
+</para>
+</sect2>
+
+<sect2>
+<title>Run cupsaddsmb with Verbose Output</title>
+
+
+<para>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+Probably you want to see what's going on. Use the
+<option>-v</option> parameter to get a more verbose output. The
+output below was edited for better readability: all <quote>\</quote> at the end of
+a line indicate that I inserted an artificial line break plus some
+indentation here:
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>cupsaddsmb -U root -v infotec_2105</userinput>
+Password for root required to access localhost via &example.server.samba;:
+Running command: smbclient //localhost/print\$ -N -U'root%secret' \
+    -c 'mkdir W32X86; \
+    put /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd; \
+	put /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll; \
+    put /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll; \
+    put /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
+added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
+putting file /var/spool/cups/tmp/3e98bf2d333b5 as \W32X86/infotec_2105.ppd
+putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll
+putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll
+putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp
+  
+Running command: rpcclient localhost -N -U'root%secret' 
+   -c 'adddriver "Windows NT x86"   \
+   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL: \
+    RAW:NULL"'
+cmd = adddriver "Windows NT x86" \
+   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL: \
+	RAW:NULL"
+Printer Driver infotec_2105 successfully installed.
+  
+Running command: smbclient //localhost/print\$ -N -U'root%secret' \
+-c 'mkdir WIN40; \
+    put /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; \
+	put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;   \
+    put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV; \
+    put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP; \
+    put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD; \
+	put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL; \
+	put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
+  added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+  Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+  NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
+  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \WIN40/infotec_2105.PPD
+  putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM
+  putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV
+  putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP
+  putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD
+  putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL
+  putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL
+  
+  Running command: rpcclient localhost -N -U'root%secret' \
+   -c 'adddriver "Windows 4.0"      \
+   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
+   PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL, \
+    ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+	cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:\
+	infotec_2105.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,\
+	infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,\
+	ICONLIB.DLL"
+  Printer Driver infotec_2105 successfully installed.
+  
+  Running command: rpcclient localhost -N -U'root%secret'  \
+   -c 'setdriver infotec_2105 infotec_2105'
+  cmd = setdriver infotec_2105 infotec_2105
+  Successfully set infotec_2105 to driver infotec_2105.
+</screen></para>
+
+<warning><para>
+You will see the root password for the Samba account printed on screen. 
+</para></warning>
+
+<para>
+If you look closely, you'll discover your root password was transferred unencrypted over the wire, so beware!
+Also, if you look further, you may discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in the output.
+This will occur when the directories WIN40 and W32X86 already existed in the <smbconfsection name="[print$]"/>
+driver download share (from a previous driver installation). These are harmless warning messages.
+</para>
+</sect2>
+
+<sect2>
+<title>Understanding cupsaddsmb</title>
+
+<para>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+What has happened? What did <command>cupsaddsmb</command> do? There are five stages of the procedure:
+</para>
+
+<orderedlist>
+	<listitem><para>
+	<indexterm><primary>IPP</primary></indexterm>
+	Call the CUPS server via IPP and request the driver files and the PPD file for the named printer.</para></listitem>
+
+	<listitem><para>Store the files temporarily in the local TEMPDIR (as defined in <filename>cupsd.conf</filename>).</para></listitem>
+
+	<listitem><para>Connect via smbclient to the Samba server's <smbconfsection name="[print$]"/> share and put the files into the
+	 share's WIN40 (for Windows 9x/Me) and W32X86 (for Windows NT/200x/XP) subdirectories.</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+	Connect via rpcclient to the Samba server and execute the <command>adddriver</command> command with the correct parameters.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+	Connect via rpcclient to the Samba server a second time and execute the <command>setdriver</command> command.</para></listitem>
+</orderedlist>
+
+<note>
+<para>
+You can run the <command>cupsaddsmb</command> utility with parameters to specify one remote host as Samba host
+and a second remote host as CUPS host. Especially if you want to get a deeper understanding, it is a good idea
+to try it and see more clearly what is going on (though in real life most people will have their CUPS and
+Samba servers run on the same host):
+<screen>
+&rootprompt;<userinput>cupsaddsmb -H sambaserver -h cupsserver -v printer</userinput>
+</screen>
+</para></note>
+
+</sect2>
+
+<sect2>
+<title>How to Recognize If cupsaddsmb Completed Successfully</title>
+
+<para>
+You <emphasis>must</emphasis> always check if the utility completed
+successfully in all fields. You need at minimum these three messages
+among the output:
+</para>
+
+<orderedlist>
+	<listitem><para><emphasis>Printer Driver infotec_2105 successfully
+	installed.</emphasis> # (for the W32X86 == Windows NT/200x/XP
+	architecture).</para></listitem>
+
+	<listitem><para><emphasis>Printer Driver infotec_2105 successfully
+	installed.</emphasis> # (for the WIN40 == Windows 9x/Me
+	architecture).</para></listitem>
+
+	<listitem><para><emphasis>Successfully set [printerXPZ] to driver
+	[printerXYZ].</emphasis></para></listitem>
+</orderedlist>
+
+<para>
+These messages are probably not easily recognized in the general
+output. If you run <command>cupsaddsmb</command> with the <option>-a</option>
+parameter (which tries to prepare <emphasis>all</emphasis> active CUPS
+printer drivers for download), you might miss if individual printer
+drivers had problems installing properly. A redirection of the
+output will help you analyze the results in retrospective.
+</para>
+
+<para>
+If you get:
+<screen>
+SetPrinter call failed!
+result was WERR_ACCESS_DENIED
+</screen>
+it means that you might have set <smbconfoption name="use client driver">yes</smbconfoption> for this printer. 
+Setting it to <quote>no</quote> will solve the problem. Refer to the &smb.conf; man page for explanation of 
+the <parameter>use client driver</parameter>.
+</para>
+
+<note><para>
+It is impossible to see any diagnostic output if you do not run <command>cupsaddsmb</command> in verbose mode.
+Therefore, we strongly recommend against use of the default quiet mode. It will hide any problems from you that
+might occur.
+</para></note>
+</sect2>
+
+<sect2>
+<title>cupsaddsmb with a Samba PDC</title>
+
+<para>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+Can't get the standard <command>cupsaddsmb</command> command to run on a Samba PDC?  Are you asked for the
+password credential again and again, and the command just will not take off at all? Try one of these
+variations:
+</para>
+
+<para><screen>
+&rootprompt;<userinput>cupsaddsmb -U &example.workgroup;\\root -v printername</userinput>
+&rootprompt;<userinput>cupsaddsmb -H &example.pdc.samba; -U &example.workgroup;\\root -v printername</userinput>
+&rootprompt;<userinput>cupsaddsmb -H &example.pdc.samba; -U &example.workgroup;\\root -h cups-server -v printername</userinput>
+</screen></para>
+
+<para>
+(Note the two backslashes: the first one is required to <quote>escape</quote> the second one).
+</para>
+</sect2>
+
+<sect2>
+<title>cupsaddsmb Flowchart</title>
+
+<para>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+<indexterm><primary>raw print</primary></indexterm>
+<link linkend="small14">The cupsaddsmb Flowchart</link> shows a chart about the procedures, command flows, and
+data flows of the <command>cupaddsmb</command> command. Note again: cupsaddsmb is
+not intended to, and does not work with, raw print queues!
+</para>
+
+	<figure id="small14">
+		<title>cupsaddsmb Flowchart.</title>
+		<imagefile>14small</imagefile></figure>
+</sect2>
+
+<sect2>
+<title>Installing the PostScript Driver on a Client</title>
+
+<para>
+<indexterm><primary>point'n'print</primary></indexterm>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+After <command>cupsaddsmb</command> is completed, your driver is prepared for the clients to use. Here are the
+steps you must perform to download and install it via Point'n'Print. From a Windows client, browse to the
+CUPS/Samba server:
+</para>
+
+<itemizedlist>
+
+	<listitem><para>
+	<indexterm><primary>"Printers" folder</primary></indexterm>
+	Open the <guilabel>Printers</guilabel> share of Samba in Network Neighborhood.</para></listitem>
+
+	<listitem><para>Right-click on the printer in question.</para></listitem>
+
+	<listitem><para>From the opening context menu select
+	<guimenuitem>Install...</guimenuitem> or 
+	<guimenuitem>Connect...</guimenuitem> (depending on the Windows version you use).</para></listitem>
+</itemizedlist>
+
+<para>
+After a few seconds, there should be a new printer in your client's <emphasis>local</emphasis>
+<guilabel>Printers</guilabel> folder. On Windows XP it will follow a naming convention of
+<emphasis>PrinterName on SambaServer</emphasis>. (In my current case it is infotec_2105 on kde-bitshop). If
+you want to test it and send your first job from an application like Winword, the new printer appears in a
+<filename>\\SambaServer\PrinterName</filename> entry in the drop-down list of available printers.
+</para>
+
+<para>
+<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>Adobe PostScript driver</primary></indexterm>
+<indexterm><primary>net use lpt1:</primary></indexterm>
+<command>cupsaddsmb</command> will only reliably work with CUPS version 1.1.15 or higher and with Samba
+version 2.2.4, or later. If it does not work, or if the automatic printer driver download to the clients does
+not succeed, you can still manually install the CUPS printer PPD on top of the Adobe PostScript driver on
+clients. Then point the client's printer queue to the Samba printer share for a UNC type of connection:
+<screen>
+&dosprompt;<userinput>net use lpt1: \\sambaserver\printershare /user:ntadmin</userinput>
+</screen>
+should you desire to use the CUPS networked PostScript RIP functions. (Note that user <quote>ntadmin</quote>
+needs to be a valid Samba user with the required privileges to access the printershare.) This sets up the
+printer connection in the traditional LanMan way (not using MS-RPC).
+</para>
+</sect2>
+
+<sect2 id="cups-avoidps1">
+<title>Avoiding Critical PostScript Driver Settings on the Client</title>
+
+<para>
+Printing works, but there are still problems. Most jobs print well, some do not print at all. Some jobs have
+problems with fonts, which do not look very good. Some jobs print fast and some are dead-slow. Many of these
+problems can be greatly reduced or even completely eliminated if you follow a few guidelines. Remember, if
+your print device is not PostScript-enabled, you are treating your Ghostscript installation on your CUPS host
+with the output your client driver settings produce. Treat it well:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Avoid the PostScript Output Option: Optimize for Speed setting. Use the Optimize for Portability instead
+	(Adobe PostScript driver).</para></listitem>
+
+	<listitem><para>
+	Don't use the Page Independence: NO setting. Instead, use Page Independence: YES (CUPS PostScript Driver).
+	</para></listitem>
+
+	<listitem><para>
+	Recommended is the True Type Font Downloading Option: Native True Type over Automatic and Outline; 
+	you should by all means avoid Bitmap (Adobe PostScript Driver).</para></listitem>
+
+	<listitem><para>
+	Choose True Type Font: Download as Softfont into Printer over the default Replace by Device
+	Font (for exotic fonts, you may need to change it back to get a printout at all; Adobe).</para></listitem>
+
+	<listitem><para>
+	Sometimes you can choose PostScript Language Level: in case of problems try 2
+	instead of 3 (the latest ESP Ghostscript package handles Level 3 PostScript very well; Adobe).
+	</para></listitem>
+
+	<listitem><para>
+	Say Yes to PostScript Error Handler (Adobe).</para></listitem>
+</itemizedlist>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Installing PostScript Driver Files Manually Using rpcclient</title>
+
+<para>
+Of course, you can run all the commands that are embedded into the
+cupsaddsmb convenience utility yourself, one by one, and upload
+and prepare the driver files for future client downloads.
+</para>
+
+<orderedlist>
+	<listitem><para>Prepare Samba (a CUPS print queue with the name of the
+	printer should be there. We are providing the driver now).</para></listitem>
+
+	<listitem><para>Copy all files to <smbconfsection name="[print$]"/>.</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+	Run <command>rpcclient adddriver</command>
+	(for each client architecture you want to support).</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+	Run <command>rpcclient setdriver.</command></para></listitem>
+</orderedlist>
+
+<para>
+<indexterm><primary>rpcclient</primary><secondary>enumports</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>enumdrivers</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+We are going to do this now. First, read the man page on <parameter>rpcclient</parameter> to get a first idea.
+Look at all the printing-related subcommands: <command>enumprinters</command>, <command>enumdrivers</command>,
+<command>enumports</command>, <command>adddriver</command>, and <command>setdriver</command> are among the
+most interesting ones. <parameter>rpcclient</parameter> implements an important part of the MS-RPC protocol.
+You can use it to query (and command) a Windows NT (or 200x/XP) PC, too. MS-RPC is used by Windows clients,
+among other things, to benefit from the Point'n'Print features. Samba can now mimic this as well.
+</para>
+
+<sect2>
+<title>A Check of the rpcclient man Page</title>
+
+<para>
+First let's check the <parameter>rpcclient</parameter> man page. Here are two relevant passages:
+</para>
+
+<para>
+<indexterm><primary>adddriver</primary></indexterm>
+<indexterm><primary>AddPrinterDriver()</primary></indexterm>
+<indexterm><primary>getdriverdir</primary></indexterm>
+<command>adddriver &lt;arch&gt; &lt;config&gt;</command> Execute an <command>AddPrinterDriver()</command> RPC
+to install the printer driver information on the server. The driver files should already exist in the
+directory returned by <command>getdriverdir</command>. Possible values for <parameter>arch</parameter> are the
+same as those for the <command>getdriverdir</command> command. The <parameter>config</parameter> parameter is
+defined as follows:
+<screen>
+Long Printer Name:\
+Driver File Name:\
+Data File Name:\
+Config File Name:\
+Help File Name:\
+Language Monitor Name:\
+Default Data Type:\
+Comma Separated list of Files
+</screen></para>
+
+<para>
+Any empty fields should be entered as the string <quote>NULL</quote>. 
+</para>
+
+<para>
+Samba does not need to support the concept of print monitors, since these only apply to local printers whose
+drivers can use a bidirectional link for communication. This field should be <quote>NULL</quote>.  On a remote
+NT print server, the print monitor for a driver must already be installed before adding the driver or else the
+RPC will fail.
+</para>
+
+<para>
+<indexterm><primary>setdriver</primary></indexterm>
+<indexterm><primary>SetPrinter()</primary></indexterm>
+<command>setdriver &lt;printername&gt; &lt;drivername&gt;</command> Execute a <command>SetPrinter()</command>
+command to update the printer driver associated with an installed printer. The printer driver must already be
+correctly installed on the print server.
+</para>
+
+<para>
+<indexterm><primary>enumprinters</primary></indexterm>
+<indexterm><primary>enumdrivers</primary></indexterm>
+See also the <command>enumprinters</command> and <command>enumdrivers</command> commands to
+obtain a list of installed printers and drivers.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Understanding the rpcclient man Page</title>
+
+<para>
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+The <emphasis>exact</emphasis> format isn't made too clear by the man page, since you have to deal with some
+parameters containing spaces. Here is a better description for it. We have line-broken the command and
+indicated the breaks with <quote>\</quote>. Usually you would type the command in one line without the line
+breaks:
+<screen>
+adddriver "Architecture" \
+   "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
+   LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
+</screen></para>
+
+<para>
+What the man pages denote as a simple <parameter>&lt;config&gt;</parameter> keyword in reality consists of
+eight colon-separated fields. The last field may take multiple (in some very insane cases, even 20 different
+additional) files. This might sound confusing at first.  What the man pages call the
+<quote>LongPrinterName</quote> in reality should be called the <quote>Driver Name</quote>. You can name it
+anything you want, as long as you use this name later in the <command>rpcclient ... setdriver</command>
+command. For practical reasons, many name the driver the same as the printer.
+</para>
+
+<para>
+It isn't simple at all. I hear you asking: <quote>How do I know which files are Driver File</quote>,
+<quote>Data File</quote>, <quote>Config File</quote>, <quote>Help File</quote> and <quote>Language Monitor
+File in each case?</quote> For an answer, you may want to have a look at how a Windows NT box with a shared
+printer presents the files to us. Remember that this whole procedure has to be developed by the Samba Team by
+listening to the traffic caused by Windows computers on the wire. We may as well turn to a Windows box now and
+access it from a UNIX workstation. We will query it with <command>rpcclient</command> to see what it tells us
+and try to understand the man page more clearly.
+</para>
+</sect2>
+
+<sect2>
+<title>Producing an Example by Querying a Windows Box</title>
+
+<para>
+<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
+We could run <command>rpcclient</command> with a <command>getdriver</command> or a
+<command>getprinter</command> subcommand (in level 3 verbosity) against it. Just sit down at a UNIX or Linux
+workstation with the Samba utilities installed, then type the following command:
+<screen>
+&rootprompt;<userinput>rpcclient -U'user%secret' NT-SERVER -c 'getdriver printername 3'</userinput>
+</screen></para>
+
+<para>
+From the result it should become clear which is which. Here is an example from my installation:
+<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>rpcclient -U'Danka%xxxx' W200xSERVER \
+    -c'getdriver "DANKA InfoStream Virtual Printer" 3'</userinput>
+    cmd = getdriver "DANKA InfoStream Virtual Printer" 3
+
+ [Windows NT x86]
+ Printer Driver Info 3:
+         Version: [2]
+         Driver Name: [DANKA InfoStream]
+         Architecture: [Windows NT x86]
+         Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRIPT.DLL]
+         Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\INFOSTRM.PPD]
+         Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRPTUI.DLL]
+         Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRIPT.HLP]
+ 
+         Dependentfiles: []
+         Dependentfiles: []
+         Dependentfiles: []
+         Dependentfiles: []
+         Dependentfiles: []
+         Dependentfiles: []
+         Dependentfiles: []
+ 
+         Monitorname: []
+         Defaultdatatype: []
+</screen></para>
+
+<para>
+Some printer drivers list additional files under the label <parameter>Dependentfiles</parameter>, and these
+would go into the last field <parameter>ListOfFiles,Comma-separated</parameter>. For the CUPS PostScript
+drivers, we do not need any (nor would we for the Adobe PostScript driver); therefore, the field will get a
+<quote>NULL</quote> entry.
+</para>
+</sect2>
+
+<sect2>
+<title>Requirements for adddriver and setdriver to Succeed</title>
+
+<para>
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+<indexterm><primary>cupsaddsmb</primary></indexterm>
+<indexterm><primary>setdriver</primary></indexterm>
+From the man page (and from the quoted output of <command>cupsaddsmb</command> above) it becomes clear that
+you need to have certain conditions in order to make the manual uploading and initializing of the driver files
+succeed. The two <command>rpcclient</command> subcommands (<command>adddriver</command> and
+<command>setdriver</command>) need to encounter the following preconditions to complete successfully:
+</para>
+
+<itemizedlist>
+	<listitem><para>You are connected as <smbconfoption name="printer admin"/> or root (this is
+	<emphasis>not</emphasis> the <quote>Printer Operators</quote> group in NT, but the <emphasis>printer
+	admin</emphasis> group as defined in the <smbconfsection name="[global]"/> section of &smb.conf;).
+	</para></listitem>
+
+	<listitem><para>Copy all required driver files to <filename>\\SAMBA\print$\w32x86</filename> and
+	<filename>\\SAMBA\print$\win40</filename> as appropriate. They will end up in the <quote>0</quote> respective
+	<quote>2</quote> subdirectories later. For now, <emphasis>do not</emphasis> put them there; they'll be
+	automatically used by the <command>adddriver</command> subcommand. (If you use <command>smbclient</command> to
+	put the driver files into the share, note that you need to escape the <quote>$</quote>: <command>smbclient
+	//sambaserver/print\$ -U root.</command>)</para></listitem>
+
+	<listitem><para>The user you're connecting as must be able to write to
+	the <smbconfsection name="[print$]"/> share and create
+	subdirectories.</para></listitem>
+
+	<listitem><para>The printer you are going to set up for the Windows
+	clients needs to be installed in CUPS already.</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+	<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
+	The CUPS printer must be known to Samba; otherwise the <command>setdriver</command> subcommand fails with an
+	NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by Samba, you may use the
+	<command>enumprinters</command> subcommand to <command>rpcclient</command>. A long-standing bug prevented a
+	proper update of the printer list until every smbd process had received a SIGHUP or was restarted. Remember
+	this in case you've created the CUPS printer just recently and encounter problems: try restarting Samba.
+	</para></listitem>
+</itemizedlist>
+</sect2>
+
+<sect2>
+<title>Manual Driver Installation in 15 Steps</title>
+
+<para>
+We are going to install a printer driver now by manually executing all
+required commands. Because this may seem a rather complicated process at
+first, we go through the procedure step by step, explaining every
+single action item as it comes up.
+</para>
+
+<procedure>
+<title>Manual Driver Installation</title>
+
+	<step>
+	<title>Install the printer on CUPS.</title>
+
+	<para><screen>
+	&rootprompt;<userinput>lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E \
+				-P canonIR85.ppd</userinput>
+	</screen></para>
+
+	<para>
+	This installs a printer with the name <parameter>mysmbtstprn</parameter>
+	to the CUPS system. The printer is accessed via a socket
+	(a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
+	for this step.
+	</para>
+	</step>
+
+	<step>
+	<title>(Optional.) Check if the printer is recognized by Samba.</title>
+
+	<para>
+	<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'enumprinters' localhost \
+  | grep -C2 mysmbtstprn</userinput>
+flags:[0x800000]
+name:[\\kde-bitshop\mysmbtstprn]
+description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
+comment:[mysmbtstprn]
+</screen>
+	</para>
+
+	<para>
+	This should show the printer in the list. If not, stop and restart the Samba daemon (smbd) or send a HUP signal: 
+<screen>
+&rootprompt;<userinput>kill -HUP `pidof smbd`</userinput>
+</screen>
+	Check again. Troubleshoot and repeat until successful. Note the <quote>empty</quote> field between the two
+	commas in the <quote>description</quote> line. The driver name would appear here if there was one already. You
+	need to know root's Samba password (as set by the <command>smbpasswd</command> command) for this step and most
+	of the following steps. Alternatively, you can authenticate as one of the users from the <quote>write
+	list</quote> as defined in &smb.conf; for <smbconfsection name="[print$]"/>.
+	</para>
+	</step>
+
+	<step>
+	<title>(Optional.) Check if Samba knows a driver for the printer.</title>
+
+	<para>
+	<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
+	<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2'\
+ localhost | grep driver </userinput>
+
+drivername:[]
+
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' \
+ localhost | grep -C4 driv</userinput>
+
+servername:[\\kde-bitshop]
+printername:[\\kde-bitshop\mysmbtstprn]
+sharename:[mysmbtstprn]
+portname:[Samba Printer Port]
+drivername:[]
+comment:[mysmbtstprn]
+location:[]
+sepfile:[]
+printprocessor:[winprint]
+ 
+&rootprompt;<userinput>rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost</userinput>
+ result was WERR_UNKNOWN_PRINTER_DRIVER
+</screen></para>
+
+<para>
+None of the three commands shown above should show a driver.
+This step was done for the purpose of demonstrating this condition. An
+attempt to connect to the printer at this stage will prompt a
+message along the lines of, <quote>The server does not have the required printer
+driver installed.</quote>
+</para>
+</step>
+
+<step>
+<title>Put all required driver files into Samba's
+[print$].</title>
+
+<para><screen>
+&rootprompt;<userinput>smbclient //localhost/print\$ -U 'root%xxxx' \
+	-c 'cd W32X86; \
+	put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD; \ 
+	put /usr/share/cups/drivers/cupsui.dll cupsui.dll; \
+	put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
+	put /usr/share/cups/drivers/cups.hlp cups.hlp'</userinput>
+</screen></para>
+
+<para>
+(This command should be entered in one long single line. Line breaks and the line ends indicated by
+<quote>\</quote> have been inserted for readability reasons.) This step is <emphasis>required</emphasis> for
+the next one to succeed. It makes the driver files physically present in the <smbconfsection name="[print$]"/>
+share. However, clients would still not be able to install them, because Samba does not yet treat them as
+driver files. A client asking for the driver would still be presented with a <quote>not installed here</quote>
+message.
+</para>
+</step>
+
+<step>
+<title>Verify where the driver files are now.</title>
+
+<para><screen>
+&rootprompt;<userinput>ls -l /etc/samba/drivers/W32X86/</userinput>
+total 669
+drwxr-sr-x    2 root     ntadmin       532 May 25 23:08 2
+drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
+-rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
+-rwxr--r--    1 root     ntadmin    278380 May 25 23:21 cupsdrvr.dll
+-rwxr--r--    1 root     ntadmin    215848 May 25 23:21 cupsui.dll
+-rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
+</screen></para>
+
+<para>
+The driver files now are in the W32X86 architecture <quote>root</quote> of
+<smbconfsection name="[print$]"/>.
+</para>
+</step>
+
+<step>
+<title>Tell Samba that these are driver files (<command>adddriver</command>).</title>
+
+<para>
+<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
+	"mydrivername:cupsdrvr.dll:mysmbtstprn.PPD: \
+  cupsui.dll:cups.hlp:NULL:RAW:NULL"' \
+  localhost</userinput>
+Printer Driver mydrivername successfully installed.
+</screen></para>
+
+<para>
+You cannot repeat this step if it fails. It could fail even as a result of a simple typo. It will most likely
+have moved a part of the driver files into the <quote>2</quote> subdirectory. If this step fails, you need to
+go back to the fourth step and repeat it before you can try this one again. In this step, you need to choose a
+name for your driver. It is normally a good idea to use the same name as is used for the printer name;
+however, in big installations you may use this driver for a number of printers that obviously have different
+names, so the name of the driver is not fixed.
+</para>
+</step>
+
+<step>
+<title>Verify where the driver files are now.</title>
+
+<para><screen>
+&rootprompt;<userinput>ls -l /etc/samba/drivers/W32X86/</userinput>
+total 1
+drwxr-sr-x    2 root     ntadmin       532 May 25 23:22 2
+drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
+
+&rootprompt;<userinput>ls -l /etc/samba/drivers/W32X86/2</userinput>
+total 5039
+[....]
+-rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
+-rwxr--r--    1 root     ntadmin    278380 May 13 13:53 cupsdrvr.dll
+-rwxr--r--    1 root     ntadmin    215848 May 13 13:53 cupsui.dll
+-rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
+</screen></para>
+
+<para>
+Notice how step 6 also moved the driver files to the appropriate
+subdirectory. Compare this with the situation after step 5.
+</para>
+</step>
+
+<step>
+<title>(Optional.) Verify if Samba now recognizes the driver.</title>
+
+<para>
+<indexterm><primary>rpcclient</primary><secondary>enumdrivers</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'enumdrivers 3' \
+	localhost | grep -B2 -A5 mydrivername</userinput>
+Printer Driver Info 3:
+Version: [2]
+Driver Name: [mydrivername]
+Architecture: [Windows NT x86]
+Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
+Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
+Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
+Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
+</screen></para>
+
+<para>
+Remember, this command greps for the name you chose for the
+driver in step 6. This command must succeed before you can proceed.
+</para>
+</step>
+
+<step>
+<para><title>Tell Samba which printer should use these driver files (<command>setdriver</command>).</title></para>
+
+<para>
+<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' \
+	localhost</userinput>
+Successfully set mysmbtstprn to driver mydrivername
+</screen></para>
+
+<para>
+Since you can bind any printer name (print queue) to any driver, this is a convenient way to set up many
+queues that use the same driver. You do not need to repeat all the previous steps for the setdriver command to
+succeed. The only preconditions are that <command>enumdrivers</command> must find the driver and
+<command>enumprinters</command> must find the printer.
+</para>
+</step>
+
+<step>
+<title>(Optional) Verify if Samba has recognized this association.</title>
+
+<para>
+<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
+<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+  | grep driver</userinput>
+drivername:[mydrivername]
+ 
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+  | grep -C4 driv</userinput>
+servername:[\\kde-bitshop]
+printername:[\\kde-bitshop\mysmbtstprn]
+sharename:[mysmbtstprn]
+portname:[Done]
+drivername:[mydrivername]
+comment:[mysmbtstprn]
+location:[]
+sepfile:[]
+printprocessor:[winprint]
+ 
+&rootprompt;<userinput>rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost</userinput>
+[Windows NT x86]
+Printer Driver Info 3:
+     Version: [2]
+     Driver Name: [mydrivername]
+     Architecture: [Windows NT x86]
+     Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
+     Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
+     Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
+     Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
+     Monitorname: []
+     Defaultdatatype: [RAW]
+     Monitorname: []
+     Defaultdatatype: [RAW]
+ 
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'enumprinters' localhost \
+	| grep mysmbtstprn</userinput>
+     name:[\\kde-bitshop\mysmbtstprn]
+     description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
+     comment:[mysmbtstprn]
+
+</screen></para>
+
+<para>
+<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
+Compare these results with the ones from steps 2 and 3. Every one of these commands show the driver is installed. Even
+the <command>enumprinters</command> command now lists the driver
+on the <quote>description</quote> line.
+</para>
+</step>
+
+<step>
+<title>(Optional.) Tickle the driver into a correct
+device mode.</title>
+
+<para>
+<indexterm><primary>"Printers" folder</primary></indexterm>
+You certainly know how to install the driver on the client. In case
+you are not particularly familiar with Windows, here is a short
+recipe: Browse the Network Neighborhood, go to the Samba server, and look
+for the shares. You should see all shared Samba printers.
+Double-click on the one in question. The driver should get
+installed and the network connection set up. Another way is to
+open the <guilabel>Printers (and Faxes)</guilabel> folder, right-click on the printer in
+question, and select <guilabel>Connect</guilabel> or <guilabel>Install</guilabel>. As a result, a new printer
+should appear in your client's local <guilabel>Printers (and Faxes)</guilabel>
+folder, named something like <guilabel>printersharename on Sambahostname</guilabel>.
+</para>
+
+<para>
+It is important that you execute this step as a Samba printer admin
+(as defined in &smb.conf;). Here is another method
+to do this on Windows XP. It uses a command line, which you may type
+into the <quote>DOS box</quote> (type root's smbpassword when prompted):
+</para>
+
+<para><screen>
+&dosprompt;<userinput>runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry \
+	/in /n \\sambaserver\mysmbtstprn"</userinput>
+</screen></para>
+
+<para>
+Change any printer setting once (like changing <emphasis><guilabel>portrait</guilabel> to
+<guilabel>landscape</guilabel></emphasis>), click on <guibutton>Apply</guibutton>, and change the setting back.
+</para>
+</step>
+
+<step>
+<title>Install the printer on a client (Point'n'Print).</title>
+
+<para>
+<indexterm significance="preferred"><primary>point 'n' print</primary></indexterm>
+<screen>
+&dosprompt;<userinput>rundll32 printui.dll,PrintUIEntry /in /n &quot;\\sambaserver\mysmbtstprn&quot;</userinput>
+</screen>
+If it does not work, it could be a permissions problem with the <smbconfsection name="[print$]"/> share.
+</para>
+</step>
+
+<step>
+<title>(Optional) Print a test page.</title>
+
+<indexterm><primary>rundll32</primary></indexterm>
+<para><screen>
+&dosprompt;<userinput>rundll32 printui.dll,PrintUIEntry /p /n "\\sambaserver\mysmbtstprn"</userinput>
+</screen></para>
+
+<para>
+Then hit [TAB] five times, [ENTER] twice, [TAB] once, and [ENTER] again, and march to the printer.
+</para>
+</step>
+
+<step>
+<title>(Recommended.) Study the test page.</title>
+
+<para>
+Hmmm. Just kidding! By now you know everything about printer installations and you do not need to read a word.
+Just put it in a frame and bolt it to the wall with the heading "MY FIRST RPCCLIENT-INSTALLED PRINTER"
+&smbmdash; why not just throw it away!
+</para>
+</step>
+
+<step>
+<title>(Obligatory.) Enjoy. Jump. Celebrate your success.</title>
+
+<para><screen>
+&rootprompt;<userinput>echo "Cheeeeerioooooo! Success..." &gt;&gt; /var/log/samba/log.smbd</userinput>
+</screen></para>
+</step>
+</procedure>
+</sect2>
+
+<sect2>
+<title>Troubleshooting Revisited</title>
+
+<para>
+<indexterm><primary>adddriver</primary></indexterm>
+The setdriver command will fail if in Samba's mind the queue is not
+already there. A successful installation displys the promising message that the:
+<screen>
+Printer Driver ABC successfully installed.
+</screen>
+following the <command>adddriver</command> parts of the procedure.  But you may also see
+a disappointing message like this one:
+<computeroutput>
+result was NT_STATUS_UNSUCCESSFUL
+</computeroutput></para>
+
+<para>
+<indexterm><primary>lpstat</primary></indexterm>
+<indexterm><primary>rpcclient</primary></indexterm>
+It is not good enough that you can see the queue in CUPS, using the <command>lpstat -p ir85wm</command>
+command. A bug in most recent versions of Samba prevents the proper update of the queue list. The recognition
+of newly installed CUPS printers fails unless you restart Samba or send a HUP to all smbd processes. To verify
+if this is the reason why Samba does not execute the <command>setdriver</command> command successfully, check
+if Samba <quote>sees</quote> the printer:
+<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>rpcclient transmeta -N -U'root%xxxx' -c 'enumprinters 0'|grep ir85wm</userinput>
+        printername:[ir85wm]
+</screen></para>
+
+<para>
+An alternate command could be this: 
+<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' </userinput>
+        cmd = getprinter ir85wm
+        flags:[0x800000]
+        name:[\\transmeta\ir85wm]
+        description:[\\transmeta\ir85wm,ir85wm,DPD]
+        comment:[CUPS PostScript-Treiber for Windows NT/200x/XP]
+</screen></para>
+
+<para>
+By the way, you can use these commands, plus a few more, of course, to install drivers on remote Windows NT print servers too!
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>The Printing <filename>*.tdb</filename> Files</title>
+
+<para>
+<indexterm><primary>TDB</primary></indexterm>
+<indexterm><primary>connections.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>printing.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>share_info.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>ntdrivers.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>unexpected.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>brlock.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>locking.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>ntforms.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>messages.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>ntprinters.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>sessionid.tdb</primary><seealso>TDB</seealso></indexterm>
+<indexterm><primary>secrets.tdb</primary><seealso>TDB</seealso></indexterm>
+Some mystery is associated with the series of files with a tdb suffix appearing in every Samba installation.
+They are <filename>connections.tdb</filename>, <filename>printing.tdb</filename>,
+<filename>share_info.tdb</filename>, <filename>ntdrivers.tdb</filename>, <filename>unexpected.tdb</filename>,
+<filename>brlock.tdb</filename>, <filename>locking.tdb</filename>, <filename>ntforms.tdb</filename>,
+<filename>messages.tdb</filename> , <filename>ntprinters.tdb</filename>, <filename>sessionid.tdb</filename>,
+and <filename>secrets.tdb</filename>. What is their purpose?
+</para>
+
+<sect2>
+<title>Trivial Database Files</title>
+
+<para>
+<indexterm><primary>TDB</primary></indexterm>
+A Windows NT (print) server keeps track of all information needed to serve its duty toward its clients by
+storing entries in the Windows registry. Client queries are answered by reading from the registry,
+Administrator or user configuration settings that are saved by writing into the registry. Samba and UNIX
+obviously do not have such a Registry. Samba instead keeps track of all client-related information in a series
+of <filename>*.tdb</filename> files. (TDB stands for trivial data base). These are often located in
+<filename>/var/lib/samba/</filename> or <filename>/var/lock/samba/</filename>. The printing-related files are
+<filename>ntprinters.tdb</filename>, <filename>printing.tdb</filename>,<filename>ntforms.tdb</filename>, and
+<filename>ntdrivers.tdb</filename>.
+</para>
+</sect2>
+
+<sect2>
+<title>Binary Format</title>
+
+<para>
+<filename>*.tdb</filename> files are not human readable. They are written in a binary format. <quote>Why not
+ASCII?</quote>, you may ask. <quote>After all, ASCII configuration files are a good and proven tradition on
+UNIX.</quote> The reason for this design decision by the Samba Team is mainly performance. Samba needs to be
+fast; it runs a separate <command>smbd</command> process for each client connection, in some environments many
+thousands of them. Some of these <command>smbds</command> might need to write-access the same
+<filename>*.tdb</filename> file <emphasis>at the same time</emphasis>. The file format of Samba's
+<filename>*.tdb</filename> files allows for this provision. Many smbd processes may write to the same
+<filename>*.tdb</filename> file at the same time. This wouldn't be possible with pure ASCII files.
+</para>
+</sect2>
+
+<sect2>
+<title>Losing <filename>*.tdb</filename> Files</title>
+
+<para>
+It is very important that all <filename>*.tdb</filename> files remain consistent over all write and read
+accesses. However, it may happen that these files <emphasis>do</emphasis> get corrupted. (A <command>kill -9
+`pidof smbd'</command> while a write access is in progress could do the damage, as could a power interruption,
+etc.). In cases of trouble, a deletion of the old printing-related <filename>*.tdb</filename> files may be the
+only option. After that, you need to re-create all print-related setups unless you have made a backup of the
+<filename>*.tdb</filename> files in time.
+</para>
+</sect2>
+
+<sect2>
+<title>Using <command>tdbbackup</command></title>
+
+<para>
+<indexterm><primary>TDB</primary><secondary>backing up</secondary><see>tdbbackup</see></indexterm>
+<indexterm><primary>tdbbackup</primary></indexterm>
+Samba ships with a little utility that helps the root user of your system to backup your
+<filename>*.tdb</filename> files. If you run it with no argument, it prints a usage message:
+<screen>
+&rootprompt;<userinput>tdbbackup</userinput>
+ Usage: tdbbackup [options] &lt;fname...&gt;
+ 
+ Version:3.0a
+   -h            this help message
+   -s suffix     set the backup suffix
+   -v            verify mode (restore if corrupt)
+</screen></para>
+
+<para>
+Here is how I backed up my <filename>printing.tdb</filename> file:
+</para>
+
+<para><screen>
+&rootprompt;<userinput>ls</userinput>
+.              browse.dat     locking.tdb     ntdrivers.tdb printing.tdb
+..             share_info.tdb connections.tdb messages.tdb  ntforms.tdb
+printing.tdbkp unexpected.tdb brlock.tdb      gmon.out      namelist.debug  
+ntprinters.tdb sessionid.tdb
+ 
+&rootprompt;<userinput>tdbbackup -s .bak printing.tdb</userinput>
+ printing.tdb : 135 records
+ 
+&rootprompt;<userinput>ls -l printing.tdb*</userinput>
+ -rw-------    1 root     root        40960 May  2 03:44 printing.tdb
+ -rw-------    1 root     root        40960 May  2 03:44 printing.tdb.bak
+
+</screen></para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>CUPS Print Drivers from Linuxprinting.org</title>
+
+<para>
+<indexterm><primary>Linuxprinting.org</primary></indexterm>
+CUPS ships with good support for HP LaserJet-type printers. You can install the generic driver as follows:
+<indexterm><primary>lpadmin</primary></indexterm>
+<screen>
+&rootprompt;<userinput>lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd</userinput>
+</screen></para>
+
+<para>
+The <option>-m</option> switch will retrieve the <filename>laserjet.ppd</filename> from the standard
+repository for not-yet-installed PPDs, which CUPS typically stores in
+<filename>/usr/share/cups/model</filename>. Alternatively, you may use <option>-P /path/to/your.ppd</option>.
+</para>
+
+<para>
+The generic <filename>laserjet.ppd,</filename> however, does not support every special option for every
+LaserJet-compatible model. It constitutes a sort of <quote>least common denominator</quote> of all the models.
+If for some reason you must pay for the commercially available ESP Print Pro drivers, your first move should
+be to consult the database on the <ulink noescape="1"
+url="http://www.linuxprinting.org/printer_list.cgi">Linuxprinting</ulink> Web site.  Linuxprinting.org has
+excellent recommendations about which driver is best used for each printer. Its database is kept current by
+the tireless work of Till Kamppeter from Mandrakesoft, who is also the principal author of the
+<command>foomatic-rip</command> utility.
+</para>
+
+<note><para>
+<indexterm><primary>foomatic-rip</primary></indexterm>
+<indexterm><primary>cupsomatic</primary></indexterm>
+<indexterm><primary>Adobe PPD</primary></indexterm>
+The former <command>cupsomatic</command> concept is now being replaced by the new successor, a much more
+powerful <command>foomatic-rip</command>.  <command>cupsomatic</command> is no longer maintained. Here is the
+new URL to the <ulink noescape="1" url="http://www.linuxprinting.org/driver_list.cgi">Foomatic-3.0</ulink>
+database.  If you upgrade to <command>foomatic-rip</command>, remember to also upgrade to the new-style PPDs
+for your Foomatic-driven printers. foomatic-rip will not work with PPDs generated for the old
+<command>cupsomatic</command>. The new-style PPDs are 100% compliant with the Adobe PPD specification. They
+are also intended to be used by Samba and the cupsaddsmb utility, to provide the driver files for the Windows
+clients!
+</para></note>
+
+<sect2>
+<title>foomatic-rip and Foomatic Explained</title>
+
+
+<para>
+<indexterm significance="preferred"><primary>foomatic</primary></indexterm>
+<indexterm significance="preferred"><primary>foomatic-rip</primary></indexterm>
+Nowadays, most Linux distributions rely on the utilities from the <ulink
+url="http://www.linuxprinting.org/">Linuxprinting.org</ulink> to create their printing-related software
+(which, by the way, works on all UNIXes and on Mac OS X and Darwin, too).  The utilities from this sire have a
+very end-user-friendly interface that allows for an easy update of drivers and PPDs for all supported models,
+all spoolers, all operating systems, and all package formats (because there is none). Its history goes back a
+few years.
+</para>
+
+<para>
+Recently, Foomatic has achieved the astonishing milestone of <ulink
+url="http://www.linuxprinting.org/printer_list.cgi?make=Anyone">1,000 listed</ulink> printer models.
+Linuxprinting.org keeps all the important facts about printer drivers, supported models, and which options are
+available for the various driver/printer combinations in its <ulink
+url="http://www.linuxprinting.org/foomatic.html">Foomatic</ulink> database. Currently there are <ulink
+url="http://www.linuxprinting.org/driver_list.cgi">245 drivers</ulink> in the database. Many drivers support
+various models, and many models may be driven by different drivers &smbmdash; its your choice!
+</para>
+
+<sect3>
+<title>690 <quote>Perfect</quote> Printers</title>
+
+<para>
+<indexterm><primary>Windows PPD</primary></indexterm>
+At present, there are 690 devices dubbed as working perfectly: 181 are <emphasis>mostly</emphasis> perfect, 96
+are <emphasis>partially</emphasis> perfect, and 46 are paperweights. Keeping in mind that most of these are
+non-PostScript models (PostScript printers are automatically supported by CUPS to perfection by using their
+own manufacturer-provided Windows PPD), and that a multifunctional device never qualifies as working perfectly
+if it does not also scan and copy and fax under GNU/Linux &smbmdash; then this is a truly astonishing
+achievement! Three years ago the number was not more than 500, and Linux or UNIX printing at the time wasn't
+anywhere near the quality it is today.
+</para>
+</sect3>
+
+<sect3>
+<title>How the Printing HOWTO Started It All</title>
+
+<para>
+A few years ago <ulink url="http://www2.picante.com/">Grant Taylor</ulink> started it all. The
+roots of today's Linuxprinting.org are in the first <ulink
+url="http://www.linuxprinting.org/foomatic2.9/howto/">Linux Printing HOWTO</ulink> that he authored. As a
+side-project to this document, which served many Linux users and admins to guide their first steps in this
+complicated and delicate setup (to a scientist, printing is <quote>applying a structured deposition of
+distinct patterns of ink or toner particles on paper substrates</quote>), he started to build in a little
+Postgres database with information about the hardware and driver zoo that made up Linux printing of the time.
+This database became the core component of today's Foomatic collection of tools and data. In the meantime, it
+has moved to an XML representation of the data.
+</para>
+</sect3>
+
+<sect3>
+<title>Foomatic's Strange Name</title>
+
+
+<para>
+<indexterm><primary>foomatic</primary></indexterm>
+<quote>Why the funny name?</quote> you ask. When it really took off, around spring 2000, CUPS was far less
+popular than today, and most systems used LPD, LPRng, or even PDQ to print. CUPS shipped with a few generic
+drivers (good for a few hundred different printer models). These didn't support many device-specific options.
+CUPS also shipped with its own built-in rasterization filter (<parameter>pstoraster</parameter>, derived from
+Ghostscript). On the other hand, CUPS provided brilliant support for <emphasis>controlling</emphasis> all
+printer options through standardized and well-defined PPD files.  Plus, CUPS was designed to be easily
+extensible.
+</para>
+
+<para>
+Taylor already had in his database a respectable compilation of facts about many more printers and the
+Ghostscript <quote>drivers</quote> they run with. His idea, to generate PPDs from the database information and
+use them to make standard Ghostscript filters work within CUPS, proved to work very well. It also killed
+several birds with one stone:
+</para>
+
+<itemizedlist>
+	<listitem><para>It made all current and future Ghostscript filter
+	developments available for CUPS.</para></listitem>
+
+	<listitem><para>It made available a lot of additional printer models
+	to CUPS users (because often the traditional Ghostscript way of
+	printing was the only one available).</para></listitem>
+
+	<listitem><para>It gave all the advanced CUPS options (Web interface,
+	GUI driver configurations) to users wanting (or needing) to use
+	Ghostscript filters.</para></listitem>
+</itemizedlist>
+</sect3>
+
+<sect3>
+<title>cupsomatic, pdqomatic, lpdomatic, directomatic</title>
+
+<para>
+<indexterm><primary>cupsomatic</primary></indexterm>
+<indexterm><primary>CUPS-PPD</primary></indexterm>
+<indexterm><primary>PPD</primary><secondary>CUPS</secondary><see>CUPS-PPD</see></indexterm>
+CUPS worked through a quickly hacked-up filter script named <ulink
+url="http://www.linuxprinting.org/download.cgi?filename=cupsomatic&amp;show=0">cupsomatic</ulink>.  cupsomatic
+ran the printfile through Ghostscript, constructing automatically the rather complicated command line needed.
+It just needed to be copied into the CUPS system to make it work. To configure the way cupsomatic controls the
+Ghostscript rendering process, it needs a CUPS-PPD. This PPD is generated directly from the contents of the
+database. For CUPS and the respective printer/filter combo, another Perl script named CUPS-O-Matic did the PPD
+generation. After that was working, Taylor implemented within a few days a similar thing for two other
+spoolers. Names chosen for the config-generator scripts were <ulink
+url="http://www.linuxprinting.org/download.cgi?filename=lpdomatic&amp;show=0">PDQ-O-Matic</ulink> (for PDQ)
+and <ulink url="http://www.linuxprinting.org/download.cgi?filename=lpdomatic&amp;show=0">LPD-O-Matic</ulink>
+(for &smbmdash; you guessed it &smbmdash; LPD); the configuration here didn't use PPDs but other
+spooler-specific files.
+</para>
+
+<para>
+From late summer of that year, <ulink url="http://www.linuxprinting.org/till/">Till Kamppeter</ulink> started
+to put work into the database. Kamppeter had been newly employed by <ulink
+url="http://www.mandrakesoft.com/">Mandrakesoft</ulink> to convert its printing system over to CUPS, after
+they had seen his <ulink url="http://www.fltk.org/">FLTK</ulink>-based <ulink
+url="http://cups.sourceforge.net/xpp/">XPP</ulink> (a GUI front-end to the CUPS lp-command). He added a huge
+amount of new information and new printers. He also developed the support for other spoolers, like <ulink
+url="http://ppr.sourceforge.net/">PPR</ulink> (via ppromatic), <ulink
+url="http://sourceforge.net/projects/lpr/">GNUlpr</ulink>, and <ulink
+url="http://www.lprng.org/">LPRng</ulink> (both via an extended lpdomatic) and spooler-less printing (<ulink
+url="http://www.linuxprinting.org/download.cgi?filename=directomatic&amp;show=0">directomatic</ulink>).
+</para>
+
+<para>
+So, to answer your question, <quote>Foomatic</quote> is the general name for all the overlapping code and data
+behind the <quote>*omatic</quote> scripts.  Foomatic, up to versions 2.0.x, required (ugly) Perl data
+structures attached to Linuxprinting.org PPDs for CUPS. It had a different <quote>*omatic</quote> script for
+every spooler, as well as different printer configuration files.
+</para>
+</sect3>
+
+<sect3>
+<title>The <emphasis>Grand Unification</emphasis> Achieved</title>
+
+<para>
+<indexterm><primary>foomatic-rip</primary></indexterm>
+This has all changed in Foomatic versions 2.9 (beta) and released as <quote>stable</quote> 3.0. It has now
+achieved the convergence of all *omatic scripts and is called the <ulink
+url="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&amp;show=0">foomatic-rip</ulink>.
+This single script is the unification of the previously different spooler-specific *omatic scripts.
+foomatic-rip is used by all the different spoolers alike, and because it can read PPDs (both the original
+PostScript printer PPDs and the Linuxprinting.org-generated ones), all of a sudden all supported spoolers can
+have the power of PPDs at their disposal. Users only need to plug foomatic-rip into their system. For users
+there is improved media type and source support &smbmdash; paper sizes and trays are easier to configure.
+</para>
+
+<para>
+<indexterm><primary>PPDs</primary></indexterm>
+<indexterm><primary>Foomatic tutorial</primary></indexterm>
+<indexterm><primary>LinuxKongress2002</primary></indexterm>
+Also, the new generation of Linuxprinting.org PPDs no longer contains Perl data structures. If you are a
+distro maintainer and have used the previous version of Foomatic, you may want to give the new one a spin, but
+remember to generate a new-version set of PPDs via the new <ulink
+url="http://www.linuxprinting.org/download/foomatic/foomatic-db-engine-3.0.0beta1.tar.gz">foomatic-db-engine!</ulink>.
+Individual users just need to generate a single new PPD specific to their model by <ulink
+url="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/II.Foomatic-User/II.tutorial-handout-foomatic-user.html">following
+the steps</ulink> outlined in the Foomatic tutorial or in this chapter. This new development is truly amazing.
+</para>
+
+<para>
+<indexterm><primary>foomatic-rip</primary></indexterm>
+<indexterm><primary>Adobe</primary></indexterm>
+<indexterm><primary>printer drivers</primary></indexterm>
+foomatic-rip is a very clever wrapper around the need to run Ghostscript with a different syntax, options,
+device selections, and/or filters for each different printer or spooler. At the same time, it can read the PPD
+associated with a print queue and modify the print job according to the user selections. Together with this
+comes the 100% compliance of the new Foomatic PPDs with the Adobe spec. Some innovative features of the
+Foomatic concept may surprise users. It will support custom paper sizes for many printers and will support
+printing on media drawn from different paper trays within the same job (in both cases, even where there is no
+support for this from Windows-based vendor printer drivers).
+</para>
+</sect3>
+
+<sect3>
+<title>Driver Development Outside</title>
+
+<para>
+<indexterm><primary>Linuxprinting.org</primary></indexterm>
+Most driver development itself does not happen within Linuxprinting.org. Drivers are written by independent
+maintainers.  Linuxprinting.org just pools all the information and stores it in its database. In addition, it
+also provides the Foomatic glue to integrate the many drivers into any modern (or legacy) printing system
+known to the world.
+</para>
+
+<para>
+Speaking of the different driver development groups, most of the work is currently done in three projects:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+<indexterm><primary>Omni</primary></indexterm>
+	<ulink url="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/">Omni</ulink>
+	&smbmdash; a free software project by IBM that tries to convert its printer
+	driver knowledge from good-ol' OS/2 times into a modern, modular,
+	universal driver architecture for Linux/UNIX (still beta). This
+	currently supports 437 models.</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>HPIJS</primary></indexterm>
+	<ulink url="http://hpinkjet.sf.net/">HPIJS</ulink> &smbmdash;
+	a free software project by HP to provide the support for its own
+	range of models (very mature, printing in most cases is perfect and
+	provides true photo quality). This currently supports 369
+	models.</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>Gimp-Print</primary></indexterm>
+	<ulink url="http://gimp-print.sf.net/">Gimp-Print</ulink> &smbmdash; a free software
+	effort, started by Michael Sweet (also lead developer for CUPS), now
+	directed by Robert Krawitz, which has achieved an amazing level of
+	photo print quality (many Epson users swear that its quality is
+	better than the vendor drivers provided by Epson for the Microsoft
+	platforms). This currently supports 522 models.</para></listitem>
+</itemizedlist>
+</sect3>
+
+<sect3>
+<title>Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</title>
+
+<para>
+Linuxprinting.org today is the one-stop shop to download printer drivers. Look for printer information and
+<ulink url="http://www.linuxprinting.org//kpfeifle/LinuxKongress2002/Tutorial/">tutorials</ulink> or solve
+printing problems in its popular <ulink url="http://www.linuxprinting.org/newsportal/">forums</ulink>. This
+forum is not just for GNU/Linux users, but admins of <ulink url="http://www.linuxprinting.org/macosx/">
+commercial UNIX systems</ulink> are also going there, and the relatively new
+<ulink url="http://www.linuxprinting.org/newsportal/thread.php3?name=linuxprinting.macosx.general">Mac OS X
+forum</ulink> has turned out to be one of the most frequented forums after only a few weeks.
+</para>
+
+<para>
+<indexterm><primary>Mandriva</primary></indexterm>
+<indexterm><primary>Mandrake</primary></indexterm>
+<indexterm><primary>Conectiva</primary></indexterm>
+Linuxprinting.org and the Foomatic driver wrappers around Ghostscript are now a standard tool-chain for
+printing on all the important distros. Most of them also have CUPS underneath. While in recent years most
+printer data had been added by Kamppeter, many additional contributions came from engineers with SuSE, Red
+Hat, Conectiva, Debian, and others. Vendor-neutrality is an important goal of the Foomatic project. Mandrake
+and Conectiva have merged and are now called Mandriva.
+</para>
+
+<note><para>
+Till Kamppeter from Mandrakesoft is doing an excellent job in his spare time to maintain Linuxprinting.org and
+Foomatic. So if you use it often, please send him a note showing your appreciation.
+</para></note>
+</sect3>
+
+<sect3>
+<title>Foomatic Database-Generated PPDs</title>
+
+<para>
+<indexterm><primary>Foomatic database</primary></indexterm>
+<indexterm><primary>XML-based datasets</primary></indexterm>
+<indexterm><primary>kprinter</primary></indexterm>
+<indexterm><primary>gtklp</primary></indexterm>
+<indexterm><primary>xpp</primary></indexterm>
+<indexterm><primary>HP Photosmart</primary></indexterm>
+<indexterm><primary>Epson Stylus inkjet</primary></indexterm>
+<indexterm><primary>non-PostScript printers</primary></indexterm>
+<indexterm><primary>raster</primary></indexterm>
+The Foomatic database is an amazing piece of ingenuity in itself. Not only does it keep the printer and driver
+information, but it is organized in a way that it can generate PPD files on the fly from its internal
+XML-based datasets. While these PPDs are modeled to the Adobe specification of PPDs, the
+Linuxprinting.org/Foomatic-PPDs do not normally drive PostScript printers. They are used to describe all the
+bells and whistles you could ring or blow on an Epson Stylus inkjet, or an HP Photosmart, or what-have-you.
+The main trick is one little additional line, not envisaged by the PPD specification, starting with the
+<parameter>*cupsFilter</parameter> keyword. It tells the CUPS daemon how to proceed with the PostScript print
+file (old-style Foomatic-PPDs named the cupsomatic filter script, while the new-style PPDs are now call
+foomatic-rip). This filter script calls Ghostscript on the host system (the recommended variant is ESP
+Ghostscript) to do the rendering work. foomatic-rip knows which filter or internal device setting it should
+ask from Ghostscript to convert the PostScript print job into a raster format ready for the target device.
+This usage of PPDs to describe the options of non-PostScript printers was the invention of the CUPS
+developers. The rest is easy.  GUI tools (like KDE's marvelous <ulink
+url="http://printing.kde.org/overview/kprinter.phtml">kprinter</ulink> or the GNOME <ulink
+url="http://gtklp.sourceforge.net/">gtklp</ulink> xpp and the CUPS Web interface) read the PPD as well and use
+this information to present the available settings to the user as an intuitive menu selection.
+</para>
+</sect3>
+</sect2>
+
+<sect2>
+<title>foomatic-rip and Foomatic PPD Download and Installation</title>
+
+<para>
+Here are the steps to install a foomatic-rip-driven LaserJet 4 Plus-compatible
+printer in CUPS (note that recent distributions of SuSE, UnitedLinux and
+Mandrake may ship with a complete package of Foomatic-PPDs plus the
+<command>foomatic-rip</command> utility. Going directly to
+Linuxprinting.org ensures that you get the latest driver/PPD files).
+</para>
+
+<itemizedlist>
+	<listitem><para>Open your browser at the Linuxprinting.org printer list <ulink url="http://www.linuxprinting.org/printer_list.cgi">page.</ulink>
+	</para></listitem>
+
+	<listitem><para>Check the complete list of printers in the 
+	<ulink url="http://www.linuxprinting.org/printer_list.cgi?make=Anyone">database.</ulink>.
+	</para></listitem>
+
+	<listitem><para>Select your model and click on the link.
+	</para></listitem>
+
+	<listitem><para>You'll arrive at a page listing all drivers working with this
+	model (for all printers, there will always be <emphasis>one</emphasis>
+	recommended driver. Try this one first).
+	</para></listitem>
+
+	<listitem><para>In our case (HP LaserJet 4 Plus), we'll arrive at the default driver for the
+	<ulink url="http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus">HP-LaserJet 4 Plus.</ulink>
+	</para></listitem>
+
+	<listitem><para>The recommended driver is ljet4.</para></listitem>
+
+	<listitem><para>Several links are provided here. You should visit them all if you
+	are not familiar with the Linuxprinting.org database.
+	</para></listitem>
+
+	<listitem><para>There is a link to the database page for the
+	<ulink url="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4">ljet4</ulink>.
+	On the driver's page, you'll find important and detailed information
+	about how to use that driver within the various available
+	spoolers.</para></listitem>
+
+	<listitem><para>Another link may lead you to the home page of the
+	author of the driver.</para></listitem>
+
+	<listitem><para>Important links are the ones that provide hints with
+	setup instructions for <ulink noescape="1" url="http://www.linuxprinting.org/cups-doc.html">CUPS</ulink>;
+	<ulink url="http://www.linuxprinting.org/pdq-doc.html">PDQ</ulink>;
+	<ulink url="http://www.linuxprinting.org/lpd-doc.html">LPD, LPRng, and GNUlpr</ulink>);
+	as well as <ulink url="http://www.linuxprinting.org/ppr-doc.html">PPR</ulink>
+	or <quote>spoolerless</quote> <ulink url="http://www.linuxprinting.org/direct-doc.html">printing</ulink>.
+	</para></listitem>
+
+	<listitem><para>You can view the PPD in your browser through this link:
+	<ulink noescape="1" url="http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&amp;printer=HP-LaserJet_4_Plus&amp;show=1">http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&amp;printer=HP-LaserJet_4_Plus&amp;show=1</ulink>
+	</para></listitem> <listitem><para>Most importantly, you can also generate and download
+	the <ulink url="http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&amp;printer=HP-LaserJet_4_Plus&amp;show=0">PPD</ulink>.
+	</para></listitem>
+
+	<listitem><para>The PPD contains all the information needed to use our
+	model and the driver; once installed, this works transparently
+	for the user. Later you'll only need to choose resolution, paper size,
+	and so on, from the Web-based menu, or from the print dialog GUI, or from
+	the command line.</para></listitem>
+
+	<listitem><para>If you ended up on the drivers
+	<ulink url="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4">page</ulink>,
+	you can choose to use the <quote>PPD-O-Matic</quote> online PPD generator
+	program.</para></listitem>
+
+	<listitem><para>Select the exact model and check either <guilabel>Download</guilabel> or
+	<guilabel>Display PPD file</guilabel> and click <guilabel>Generate PPD file</guilabel>.</para></listitem>
+
+	<listitem><para>If you save the PPD file from the browser view, please
+	do not use cut and paste (since it could possibly damage line endings
+	and tabs, which makes the PPD likely to fail its duty), but use <guimenuitem>Save
+	as...</guimenuitem> in your browser's menu. (It is best to use the <guilabel>Download</guilabel> option
+	directly from the Web page.)</para></listitem>
+
+	<listitem><para>Another interesting part on each driver page is
+	the <guimenuitem>Show execution details</guimenuitem> button. If you
+	select your printer model and click on that button,
+	a complete Ghostscript command line will be displayed, enumerating all options
+	available for that combination of driver and printer model. This is a great way to
+	<quote>learn Ghostscript by doing</quote>. It is also an excellent cheat sheet
+	for all experienced users who need to reconstruct a good command line
+	for that darned printing script, but can't remember the exact
+	syntax. </para></listitem>
+
+	<listitem><para>Sometime during your visit to Linuxprinting.org, save
+	the PPD to a suitable place on your hard disk, say
+	<filename>/path/to/my-printer.ppd</filename> (if you prefer to install
+	your printers with the help of the CUPS Web interface, save the PPD to
+	the <filename>/usr/share/cups/model/</filename> path and restart
+	cupsd).</para></listitem>
+
+	<listitem><para>Then install the printer with a suitable command line,
+	like this: 
+	</para>
+
+	<para><screen>
+	&rootprompt;<userinput>lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
+		-P path/to/my-printer.ppd</userinput>
+	</screen></para></listitem>
+
+	<listitem><para>For all the new-style <quote>Foomatic-PPDs</quote>
+	from Linuxprinting.org, you also need a special CUPS filter named
+	foomatic-rip. 
+	</para></listitem>
+
+	<listitem><para>The foomatic-rip Perl script itself also makes some
+	interesting <ulink url="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&amp;show=1">reading</ulink>
+	because it is well documented by Kamppeter's in-line comments (even
+	non-Perl hackers will learn quite a bit about printing by reading
+	it).</para></listitem>
+
+	<listitem><para>Save foomatic-rip either directly in
+	<filename>/usr/lib/cups/filter/foomatic-rip</filename> or somewhere in
+	your $PATH (and remember to make it world-executable). Again,
+	do not save by copy and paste but use the appropriate link or the
+	<guimenuitem>Save as...</guimenuitem>  menu item in your browser.</para></listitem>
+
+	<listitem><para>If you save foomatic-rip in your $PATH, create a symlink:
+	<screen>
+	&rootprompt;<userinput>cd /usr/lib/cups/filter/ ; ln -s `which foomatic-rip'</userinput>
+	</screen>
+	</para>
+
+	<para>
+	CUPS will discover this new available filter at startup after restarting
+	cupsd.</para></listitem>
+</itemizedlist>
+
+<para>
+Once you print to a print queue set up with the Foomatic PPD, CUPS will insert the appropriate commands and
+comments into the resulting PostScript job file. foomatic-rip is able to read and act upon these and uses some
+specially encoded Foomatic comments embedded in the job file. These in turn are used to construct
+(transparently for you, the user) the complicated Ghostscript command line telling the printer driver exactly
+how the resulting raster data should look and which printer commands to embed into the data stream. You need:
+</para>
+
+<itemizedlist>
+	<listitem><para>A <quote>foomatic+something</quote> PPD &smbmdash; but this is not enough
+	to print with CUPS (it is only <emphasis>one</emphasis> important
+	component).</para></listitem>
+
+	<listitem><para>The <parameter>foomatic-rip</parameter> filter script (Perl) in
+	<filename>/usr/lib/cups/filters/</filename>.</para></listitem>
+
+	<listitem><para>Perl to make foomatic-rip run.</para></listitem>
+
+	<listitem><para>Ghostscript (because it is doing the main work,
+	controlled by the PPD/foomatic-rip combo) to produce the raster data
+	fit for your printer model's consumption.</para></listitem>
+
+	<listitem><para>Ghostscript <emphasis>must</emphasis> (depending on
+	the driver/model) contain support for a certain device representing
+	the selected driver for your model (as shown by <command>gs -h</command>).</para></listitem>
+
+	<listitem><para>foomatic-rip needs a new version of PPDs (PPD versions
+	produced for cupsomatic do not work with foomatic-rip).</para></listitem>
+</itemizedlist>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Page Accounting with CUPS</title>
+
+
+<para>
+<indexterm><primary>CUPS</primary><secondary>Page Accounting</secondary></indexterm>
+Often there are questions regarding print quotas where Samba users (that is, Windows clients) should not be
+able to print beyond a certain number of pages or data volume per day, week, or month. This feature is
+dependent on the real print subsystem you're using.  Samba's part is always to receive the job files from the
+clients (filtered <emphasis>or</emphasis> unfiltered) and hand them over to this printing subsystem.
+</para>
+
+<para>
+Of course one could hack things with one's own scripts. But then there is CUPS. CUPS supports quotas that can
+be based on the size of jobs or on the number of pages or both, and can span any time period you want.
+</para>
+
+<sect2>
+<title>Setting Up Quotas</title>
+
+<para>
+<indexterm><primary>CUPS</primary><secondary>quotas</secondary></indexterm>
+This is an example command of how root would set a print quota in CUPS, assuming an existing printer named
+<quote>quotaprinter</quote>:
+<indexterm><primary>lpadmin</primary></indexterm>
+<screen>
+&rootprompt;<userinput>lpadmin -p quotaprinter -o job-quota-period=604800 \
+	-o job-k-limit=1024 -o job-page-limit=100</userinput>
+</screen></para>
+
+<para>
+This would limit every single user to print no more than 100 pages or 1024 KB of
+data (whichever comes first) within the last 604,800 seconds ( = 1 week).
+</para>
+</sect2>
+
+<sect2>
+<title>Correct and Incorrect Accounting</title>
+
+<para>
+For CUPS to count correctly, the printfile needs to pass the CUPS pstops filter; otherwise it uses a dummy
+count of <quote>one</quote>. Some print files do not pass it (e.g., image files), but then those are mostly
+one-page jobs anyway. This also means that proprietary drivers for the target printer running on the client
+computers and CUPS/Samba, which then spool these files as <quote>raw</quote> (i.e., leaving them untouched,
+not filtering them), will be counted as one-pagers too!
+</para>
+
+<para>
+You need to send PostScript from the clients (i.e., run a PostScript driver there) to have the chance to get
+accounting done. If the printer is a non-PostScript model, you need to let CUPS do the job to convert the file
+to a print-ready format for the target printer. This is currently working for about a thousand different
+printer models.  Linuxprinting.org has a driver <ulink url="http://www.linuxprinting.org/printer_list.cgi">list</ulink>.
+</para>
+</sect2>
+
+<sect2>
+<title>Adobe and CUPS PostScript Drivers for Windows Clients</title>
+
+<para>
+<indexterm><primary>Adobe PostScript</primary></indexterm>
+<indexterm><primary>pstops</primary></indexterm>
+<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>pstoraster</primary></indexterm>
+<indexterm><primary>PJL-header</primary></indexterm>
+Before CUPS 1.1.16, your only option was to use the Adobe PostScript driver on the Windows clients. The output
+of this driver was not always passed through the <command>pstops</command> filter on the CUPS/Samba side, and
+therefore was not counted correctly (the reason is that it often, depending on the PPD being used, wrote a
+PJL-header in front of the real PostScript, which caused CUPS to skip <command>pstops</command> and go
+directly to the <command>pstoraster</command> stage).
+</para>
+
+<para>
+From CUPS 1.1.16 and later releases, you can use the CUPS PostScript driver for Windows NT/200x/XP
+clients (which is tagged in the download area of <filename>http://www.cups.org/</filename> as the
+<filename>cups-samba-1.1.16.tar.gz</filename> package). It does <emphasis>not</emphasis> work for Windows
+9x/Me clients, but it guarantees:
+</para>
+
+<itemizedlist>
+	<listitem><para> <indexterm><primary>PJL</primary></indexterm> To not write a PJL-header.</para></listitem>
+
+	<listitem><para>To still read and support all PJL-options named in the
+	driver PPD with its own means.</para></listitem>
+
+	<listitem><para>That the file will pass through the <command>pstops</command> filter
+	on the CUPS/Samba server.</para></listitem>
+
+	<listitem><para>To page-count correctly the print file.</para></listitem>
+</itemizedlist>
+
+<para>
+You can read more about the setup of this combination in the man page for <command>cupsaddsmb</command> (which
+is only present with CUPS installed, and only current from CUPS 1.1.16).
+</para>
+</sect2>
+
+<sect2>
+<title>The page_log File Syntax</title>
+
+<para>
+<indexterm><primary>page_log</primary></indexterm>
+These are the items CUPS logs in the <filename>page_log</filename> for every page of a job:
+</para>
+
+<itemizedlist>
+	<listitem><para>Printer name</para></listitem>
+
+	<listitem><para>User name</para></listitem>
+
+	<listitem><para>Job ID</para></listitem>
+
+	<listitem><para>Time of printing</para></listitem>
+
+	<listitem><para>Page number</para></listitem>
+
+	<listitem><para>Number of copies</para></listitem>
+
+	<listitem><para>A billing information string (optional)</para></listitem>
+
+	<listitem><para>The host that sent the job (included since version 1.1.19)</para></listitem>
+</itemizedlist>
+
+<para>
+Here is an extract of my CUPS server's <filename>page_log</filename> file to illustrate the
+format and included items:
+</para>
+
+<para><screen>
+tec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 1 3 #marketing 10.160.50.13
+tec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 2 3 #marketing 10.160.50.13
+tec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 3 3 #marketing 10.160.50.13
+tec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 4 3 #marketing 10.160.50.13
+Dig9110 boss 402 [22/Apr/2003:10:33:22 +0100] 1 440 finance-dep 10.160.51.33
+</screen></para>
+
+<para>
+This was job ID <parameter>401</parameter>, printed on <parameter>tec_IS2027</parameter>
+by user <parameter>kurt</parameter>, a 64-page job printed in three copies, billed to
+<parameter>#marketing</parameter>, and sent from IP address <constant>10.160.50.13.</constant>
+ The next job had ID <parameter>402</parameter>, was sent by user <parameter>boss</parameter>
+from IP address <constant>10.160.51.33</constant>, printed from one page 440 copies, and
+is set to be billed to <parameter>finance-dep</parameter>.
+</para>
+</sect2>
+
+<sect2>
+<title>Possible Shortcomings</title>
+
+<para>
+What flaws or shortcomings are there with this quota system?
+</para>
+
+<itemizedlist>
+	<listitem><para>The ones named above (wrongly logged job in case of
+	printer hardware failure, and so on).</para></listitem>
+
+	<listitem><para>In reality, CUPS counts the job pages that are being
+	processed in <emphasis>software</emphasis> (that is, going through the
+	RIP) rather than the physical sheets successfully leaving the
+	printing device. Thus, if there is a jam while printing the fifth sheet out
+	of 1,000 and the job is aborted by the printer, the page count will
+	still show the figure of 1,000 for that job.</para></listitem>
+
+	<listitem><para>All quotas are the same for all users (no flexibility
+	to give the boss a higher quota than the clerk) and no support for
+	groups.</para></listitem>
+
+	<listitem><para>No means to read out the current balance or the
+	<quote>used-up</quote> number of current quota.</para></listitem>
+
+	<listitem><para>A user having used up 99 sheets of a 100 quota will
+	still be able to send and print a 1,000 sheet job.</para></listitem>
+
+	<listitem><para>A user being denied a job because of a filled-up quota
+	does not get a meaningful error message from CUPS other than
+	<quote>client-error-not-possible</quote>.</para></listitem>
+</itemizedlist>
+</sect2>
+
+<sect2>
+<title>Future Developments</title>
+
+<para>
+This is the best system currently available, and there are huge
+improvements under development for CUPS 1.2:
+</para>
+
+<itemizedlist>
+	<listitem><para>Page counting will go into the backends (these talk
+	directly to the printer and will increase the count in sync with the
+	actual printing process; thus, a jam at the fifth sheet will lead to a
+	stop in the counting).</para></listitem>
+
+	<listitem><para>Quotas will be handled more flexibly.</para></listitem>
+
+	<listitem><para>Probably there will be support for users to inquire
+	about their accounts in advance.</para></listitem>
+
+	<listitem><para>Probably there will be support for some other tools
+	around this topic.</para></listitem>
+</itemizedlist>
+</sect2>
+
+<sect2>
+<title>Other Accounting Tools</title>
+
+<para>
+Other accounting tools that can be used includes: PrintAnalyzer, pyKota, printbill, LogReport.
+For more information regarding these tools you can try a Google search.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Additional Material</title>
+
+<para>
+A printer queue with <emphasis>no</emphasis> PPD associated to it is a
+<quote>raw</quote> printer, and all files will go directly there as received by the
+spooler. The exceptions are file types <parameter>application/octet-stream</parameter>
+that need the pass-through feature enabled. <quote>Raw</quote> queues do not do any
+filtering at all; they hand the file directly to the CUPS backend.
+This backend is responsible for sending the data to the device
+(as in the <quote>device URI</quote> notation: <filename>lpd://, socket://,
+smb://, ipp://, http://, parallel:/, serial:/, usb:/</filename>, and so on).
+</para>
+
+<para>
+cupsomatic/Foomatic are <emphasis>not</emphasis> native CUPS drivers
+and they do not ship with CUPS. They are a third-party add-on
+developed at Linuxprinting.org. As such, they are a brilliant hack to
+make all models (driven by Ghostscript drivers/filters in traditional
+spoolers) also work via CUPS, with the same (good or bad!) quality as
+in these other spoolers. <parameter>cupsomatic</parameter> is only a vehicle to execute a
+Ghostscript command line at that stage in the CUPS filtering chain
+where normally the native CUPS <parameter>pstoraster</parameter> filter would kick
+in. <parameter>cupsomatic</parameter> bypasses <parameter>pstoraster</parameter>, kidnaps the print file from CUPS,
+and redirects it to go through Ghostscript. CUPS accepts this
+because the associated cupsomatic/foomatic-PPD specifies:
+
+<programlisting>
+*cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
+</programlisting>
+
+This line persuades CUPS to hand the file to <parameter>cupsomatic</parameter> once it has
+successfully converted it to the MIME type
+<parameter>application/vnd.cups-postscript</parameter>. This conversion will not happen for
+jobs arriving from Windows that are autotyped
+<parameter>application/octet-stream</parameter>, with the according changes in
+<filename>/etc/cups/mime.types</filename> in place.
+</para>
+
+<para>
+CUPS is widely configurable and flexible, even regarding its filtering
+mechanism. Another workaround in some situations would be to have in
+<filename>/etc/cups/mime.types</filename> entries as follows:
+
+<programlisting>
+application/postscript           application/vnd.cups-raw  0  -
+application/vnd.cups-postscript  application/vnd.cups-raw  0  -
+</programlisting>
+
+This would prevent all PostScript files from being filtered (rather,
+they will through the virtual <emphasis>nullfilter</emphasis>
+denoted with <quote>-</quote>). This could only be useful for PostScript printers. If you
+want to print PostScript code on non-PostScript printers (provided they support ASCII
+text printing), an entry as follows could be useful:
+
+<programlisting>
+*/*           application/vnd.cups-raw  0  -
+</programlisting>
+
+and would effectively send <emphasis>all</emphasis> files to the
+backend without further processing.
+</para>
+
+<para>
+You could have the following entry:
+
+<programlisting>
+application/vnd.cups-postscript application/vnd.cups-raw 0 \
+	my_PJL_stripping_filter
+</programlisting>
+
+You will need to write a <parameter>my_PJL_stripping_filter</parameter>
+(which could be a shell script) that parses the PostScript and removes the
+unwanted PJL. This needs to conform to CUPS filter design
+(mainly, receive and pass the parameters printername, job-id,
+username, jobtitle, copies, print options, and possibly the
+filename). It is installed as world executable into
+<filename>/usr/lib/cups/filters/</filename> and is called by CUPS
+if it encounters a MIME type <parameter>application/vnd.cups-postscript</parameter>.
+</para>
+
+<para>
+CUPS can handle <parameter>-o job-hold-until=indefinite</parameter>.
+This keeps the job in the queue on hold. It will only be printed
+upon manual release by the printer operator. This is a requirement in
+many central reproduction departments, where a few operators manage
+the jobs of hundreds of users on some big machine, where no user is
+allowed to have direct access (such as when the operators often need
+to load the proper paper type before running the 10,000 page job
+requested by marketing for the mailing, and so on).
+</para>
+</sect1>
+
+<sect1>
+<title>Autodeletion or Preservation of CUPS Spool Files</title>
+
+<para>
+<indexterm><primary>/var/spool/samba</primary></indexterm>
+<indexterm><primary>/var/spool/cups/</primary></indexterm>
+<indexterm><primary>cupsd.conf</primary></indexterm>
+Samba print files pass through two spool directories. One is the incoming directory managed by Samba (set in
+the <smbconfoption name="path">/var/spool/samba</smbconfoption> directive in the <smbconfsection
+name="[printers]"/> section of &smb.conf;). The other is the spool directory of your UNIX print subsystem. For
+CUPS it is normally <filename>/var/spool/cups/</filename>, as set by the <filename>cupsd.conf</filename>
+directive <filename>RequestRoot /var/spool/cups</filename>.
+</para>
+
+<sect2>
+<title>CUPS Configuration Settings Explained</title>
+
+<para>
+Some important parameter settings in the CUPS configuration file
+<filename>cupsd.conf</filename> are:
+</para>
+
+<variablelist>
+
+	<varlistentry><term>PreserveJobHistory Yes</term>
+	<listitem><para>
+	This keeps some details of jobs in cupsd's mind (well, it keeps the
+	c12345, c12346, and so on, files in the CUPS spool directory, which does a
+	similar job as the old-fashioned BSD-LPD control files). This is set
+	to <quote>Yes</quote> as a default.
+	</para></listitem></varlistentry>
+
+	<varlistentry><term>PreserveJobFiles Yes</term>
+	<listitem><para>
+	This keeps the job files themselves in cupsd's mind
+	(it keeps the d12345, d12346, etc., files in the CUPS spool
+	directory). This is set to <quote>No</quote> as the CUPS
+	default.
+	</para></listitem></varlistentry>
+
+	<varlistentry><term><quote>MaxJobs 500</quote></term>
+	<listitem><para>
+	This directive controls the maximum number of jobs
+	that are kept in memory. Once the number of jobs reaches the limit,
+	the oldest completed job is automatically purged from the system to
+	make room for the new one. If all of the known jobs are still
+	pending or active, then the new job will be rejected. Setting the
+	maximum to 0 disables this functionality. The default setting is
+	0.
+	</para></listitem></varlistentry>
+</variablelist>
+
+<para>
+(There are also additional settings for <parameter>MaxJobsPerUser</parameter> and
+<parameter>MaxJobsPerPrinter</parameter>.)
+</para>
+</sect2>
+
+<sect2>
+<title>Preconditions</title>
+
+<para>
+For everything to work as it should, you need to have three things:
+</para>
+
+<itemizedlist>
+	<listitem><para>A Samba smbd that is compiled against <filename>libcups</filename> (check
+	on Linux by running <userinput>ldd `which smbd'</userinput>).</para></listitem>
+
+	<listitem><para>A Samba-&smb.conf; setting of
+			<smbconfoption name="printing">cups</smbconfoption>.</para></listitem>
+
+	<listitem><para>Another Samba &smb.conf; setting of
+			<smbconfoption name="printcap">cups</smbconfoption>.</para></listitem>
+</itemizedlist>
+
+<note><para>
+In this case, all other manually set printing-related commands (like
+<smbconfoption name="print command"/>, 
+<smbconfoption name="lpq command"/>, 
+<smbconfoption name="lprm command"/>, 
+<smbconfoption name="lppause command"/>, and
+<smbconfoption name="lpresume command"/>) are ignored, and they should normally have no
+influence whatsoever on your printing.
+</para></note>
+</sect2>
+
+<sect2>
+<title>Manual Configuration</title>
+
+<para>
+If you want to do things manually, replace the <smbconfoption name="printing">cups</smbconfoption>
+by <smbconfoption name="printing">bsd</smbconfoption>. Then your manually set commands may work
+(I haven't tested this), and a <smbconfoption name="print command">lp -d %P %s; rm %s</smbconfoption>
+may do what you need.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Printing from CUPS to Windows-Attached Printers</title>
+
+<para>
+<indexterm><primary>smbspool</primary></indexterm>
+<indexterm><primary>backends</primary></indexterm>
+From time to time the question arises, how can you print <emphasis>to</emphasis> a Windows-attached printer
+<emphasis>from</emphasis> Samba? Normally the local connection from Windows host to printer would be done by
+USB or parallel cable, but this does not matter to Samba. From here only an SMB connection needs to be opened
+to the Windows host. Of course, this printer must be shared first. As you have learned by now, CUPS uses
+<emphasis>backends</emphasis> to talk to printers and other servers. To talk to Windows shared printers, you
+need to use the <filename>smb</filename> (surprise, surprise!) backend. Check if this is in the CUPS backend
+directory. This usually resides in <filename>/usr/lib/cups/backend/</filename>. You need to find an
+<filename>smb</filename> file there. It should be a symlink to <filename>smbspool</filename>, and the file
+must exist and be executable:
+<screen>
+&rootprompt;<userinput>ls -l /usr/lib/cups/backend/</userinput>
+total 253
+drwxr-xr-x    3 root   root     720 Apr 30 19:04 .
+drwxr-xr-x    6 root   root     125 Dec 19 17:13 ..
+-rwxr-xr-x    1 root   root   10692 Feb 16 21:29 canon
+-rwxr-xr-x    1 root   root   10692 Feb 16 21:29 epson
+lrwxrwxrwx    1 root   root       3 Apr 17 22:50 http -&gt; ipp
+-rwxr-xr-x    1 root   root   17316 Apr 17 22:50 ipp
+-rwxr-xr-x    1 root   root   15420 Apr 20 17:01 lpd
+-rwxr-xr-x    1 root   root    8656 Apr 20 17:01 parallel
+-rwxr-xr-x    1 root   root    2162 Mar 31 23:15 pdfdistiller
+lrwxrwxrwx    1 root   root      25 Apr 30 19:04 ptal -&gt; /usr/sbin/ptal-cups
+-rwxr-xr-x    1 root   root    6284 Apr 20 17:01 scsi
+lrwxrwxrwx    1 root   root      17 Apr  2 03:11 smb -&gt; /usr/bin/smbspool
+-rwxr-xr-x    1 root   root    7912 Apr 20 17:01 socket
+-rwxr-xr-x    1 root   root    9012 Apr 20 17:01 usb
+
+&rootprompt;<userinput>ls -l `which smbspool`</userinput>
+-rwxr-xr-x    1 root   root  563245 Dec 28 14:49 /usr/bin/smbspool
+</screen></para>
+
+<para>
+If this symlink does not exist, create it:
+<screen>
+&rootprompt;<userinput>ln -s `which smbspool` /usr/lib/cups/backend/smb</userinput>
+</screen></para>
+
+<para>
+<indexterm><primary>smbspool</primary></indexterm>
+<indexterm><primary>troubleshooting</primary></indexterm>
+<command>smbspool</command> was written by Mike Sweet from the CUPS folks. It is included and ships with
+Samba. It may also be used with print subsystems other than CUPS, to spool jobs to Windows printer shares. To
+set up printer <replaceable>winprinter</replaceable> on CUPS, you need to have a driver for it. Essentially
+this means to convert the print data on the CUPS/Samba host to a format that the printer can digest (the
+Windows host is unable to convert any files you may send). This also means you should be able to print to the
+printer if it were hooked directly at your Samba/CUPS host. For troubleshooting purposes, this is what you
+should do to determine if that part of the process chain is in order. Then proceed to fix the network
+connection/authentication to the Windows host, and so on.
+</para>
+
+<para>
+To install a printer with the <parameter>smb</parameter> backend on CUPS, use this command:
+</para>
+
+<para><screen>
+&rootprompt;<userinput>lpadmin -p winprinter -v smb://WINDOWSNETBIOSNAME/printersharename \
+  -P /path/to/PPD</userinput>
+</screen></para>
+
+<para>
+<indexterm><primary>PostScript printers</primary></indexterm>
+<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>Windows NT PostScript driver</primary></indexterm>
+The PPD must be able to direct CUPS to generate the print data for the target model. For PostScript printers,
+just use the PPD that would be used with the Windows NT PostScript driver. But what can you do if the printer
+is only accessible with a password? Or if the printer's host is part of another workgroup? This is provided
+for: You can include the required parameters as part of the <filename>smb://</filename> device-URI like this:
+</para>
+
+<itemizedlist>
+	<listitem><para><filename>smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename</filename></para></listitem>
+	<listitem><para><filename>smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename</filename></para></listitem>
+	<listitem><para><filename>smb://username:password@WINDOWSNETBIOSNAME/printersharename</filename></para></listitem>
+</itemizedlist>
+
+<para>
+Note that the device URI will be visible in the process list of the Samba server (e.g., when someone uses the
+<command>ps -aux</command> command on Linux), even if the username and passwords are sanitized before they get
+written into the log files. This is an inherently insecure option; however, it is the only one. Don't use it
+if you want to protect your passwords. Better share the printer in a way that does not require a password!
+Printing will only work if you have a working NetBIOS name resolution up and running. Note that this is a
+feature of CUPS and you do not necessarily need to have smbd running.
+
+</para>
+</sect1>
+
+<sect1>
+<title>More CUPS Filtering Chains</title>
+
+<para>
+The diagrams in <link linkend="cups1">Filtering Chain 1</link> and <link linkend="cups2">Filtering Chain with
+cupsomatic</link> show how CUPS handles print jobs.
+</para>
+
+<figure id="cups1">
+	<title>Filtering Chain 1.</title>
+	<imagefile>cups1</imagefile>
+</figure>
+
+<!-- JJJ -->
+<figure id="cups2">
+	<title>Filtering Chain with cupsomatic</title>
+	<imagefile scale="45">cups2</imagefile>
+</figure>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+	<sect2>
+	<title>Windows 9x/Me Client Can't Install Driver</title>
+
+	<para>For Windows 9x/Me, clients require the printer names to be eight
+	characters (or <quote>8 plus 3 chars suffix</quote>) max; otherwise, the driver files
+	will not get transferred when you want to download them from Samba.</para>
+
+	</sect2>
+
+	<sect2 id="root-ask-loop">
+	<title><quote>cupsaddsmb</quote> Keeps Asking for Root Password in Never-ending Loop</title>
+
+	<para>Have you set <smbconfoption name="security">user</smbconfoption>? Have
+	you used <command>smbpasswd</command> to give root a Samba account?
+	You can do two things: open another terminal and execute
+	<command>smbpasswd -a root</command> to create the account and
+	continue entering the password into the first terminal. Or, break
+	out of the loop by pressing Enter twice (without trying to type a
+	password).</para>
+
+	<para>
+	If the error is <quote>Tree connect failed: NT_STATUS_BAD_NETWORK_NAME</quote>, 
+	you may have forgotten to create the <filename>/etc/samba/drivers</filename> directory.
+	</para>
+	</sect2>
+
+	<sect2>
+	<title><quote>cupsaddsmb</quote> or <quote>rpcclient addriver</quote> Emit Error</title>
+
+	<para>
+	If <command>cupsaddsmb</command>, or <command>rpcclient addriver</command> emit the error message
+	WERR_BAD_PASSWORD, refer to <link linkend="root-ask-loop">the previous common error</link>.
+	</para>
+	
+	</sect2>
+
+	<sect2>
+	<title><quote>cupsaddsmb</quote> Errors</title>
+
+	<para>
+	The use of <quote>cupsaddsmb</quote> gives <quote>No PPD file for printer...</quote> 
+	message while PPD file is present.  What might the problem be?
+	</para>
+
+	<para>
+	Have you enabled printer sharing on CUPS? This means, do you have a <literal>&lt;Location
+	/printers&gt;....&lt;/Location&gt;</literal> section in CUPS server's <filename>cupsd.conf</filename> that
+	does not deny access to the host you run <quote>cupsaddsmb</quote> from?  It <emphasis>could</emphasis> be an
+	issue if you use cupsaddsmb remotely, or if you use it with a <option>-h</option> parameter:
+	<userinput>cupsaddsmb -H sambaserver -h cupsserver -v printername</userinput>.
+	</para>
+
+	<para>Is your <parameter>TempDir</parameter> directive in
+	<filename>cupsd.conf</filename> set to a valid value, and is it writable?
+	</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Client Can't Connect to Samba Printer</title>
+
+	<para>Use <command>smbstatus</command> to check which user
+	you are from Samba's point of view. Do you have the privileges to
+	write into the <smbconfsection name="[print$]"/>
+	share?</para>
+
+	</sect2>
+
+	<sect2>
+	<title>New Account Reconnection from Windows 200x/XP Troubles</title>
+
+<para>
+Once you are connected as the wrong user (for example, as <constant>nobody</constant>, which often occurs if
+you have <smbconfoption name="map to guest">bad user</smbconfoption>), Windows Explorer will not accept an
+attempt to connect again as a different user. There will not be any bytes transferred on the wire to Samba,
+but still you'll see a stupid error message that makes you think Samba has denied access. Use
+<command>smbstatus</command> to check for active connections. Kill the PIDs. You still can't re-connect, and
+you get the dreaded <computeroutput>You can't connect with a second account from the same
+machine</computeroutput> message as soon as you try. And you do not see a single byte arriving at Samba (see
+logs; use <quote>ethereal</quote>) indicating a renewed connection attempt. Shut all Explorer Windows.  This
+makes Windows forget what it has cached in its memory as established connections. Then reconnect as the right
+user. The best method is to use a DOS terminal window and <emphasis>first</emphasis> do <userinput>net use z:
+\\&example.server.samba;\print$ /user:root</userinput>. Check with <command>smbstatus</command> that you are
+connected under a different account. Now open the <guilabel>Printers</guilabel> folder (on the Samba server in
+the <guilabel>Network Neighborhood</guilabel>), right-click on the printer in question, and select
+<guibutton>Connect....</guibutton>.
+</para>
+</sect2>
+
+<sect2>
+<title>Avoid Being Connected to the Samba Server as the Wrong User</title>
+	
+<para>
+<indexterm><primary>smbstatus</primary></indexterm>
+You see per <command>smbstatus</command> that you are connected as user nobody, but you want to be root or
+printer admin. This is probably due to <smbconfoption name="map to guest">bad user</smbconfoption>, which
+silently connected you under the guest account when you gave (maybe by accident) an incorrect username. Remove
+<smbconfoption name="map to guest"/> if you want to prevent this.
+</para>
+</sect2>
+
+<sect2>
+<title>Upgrading to CUPS Drivers from Adobe Drivers</title>
+
+<para>
+This information came from a mailing list posting regarding problems experienced when
+upgrading from Adobe drivers to CUPS drivers on Microsoft Windows NT/200x/XP clients.
+</para>
+
+<para>First delete all old Adobe-using printers. Then delete all old Adobe drivers. (On Windows 200x/XP, right-click in
+the background of <guilabel>Printers</guilabel> folder, select <guimenuitem>Server Properties...</guimenuitem>, select
+tab <guilabel>Drivers</guilabel>, and delete here).</para>
+</sect2>
+
+<sect2>
+<title>Can't Use <quote>cupsaddsmb</quote> on Samba Server, Which Is a PDC</title>
+
+<para>Do you use the <quote>naked</quote> root user name? Try to do it
+this way: <userinput>cupsaddsmb -U <replaceable>DOMAINNAME</replaceable>\\root -v
+<replaceable>printername</replaceable></userinput>> (note the two backslashes: the first one is
+required to <quote>escape</quote> the second one).</para>
+
+</sect2>
+
+<sect2>
+<title>Deleted Windows 200x Printer Driver Is Still Shown</title>
+
+<para>Deleting a printer on the client will not delete the
+driver too (to verify, right-click on the white background of the
+<guilabel>Printers</guilabel> folder, select <guimenuitem>Server Properties</guimenuitem> and click on the
+<guilabel>Drivers</guilabel> tab). These same old drivers will be re-used when you try to
+install a printer with the same name. If you want to update to a new
+driver, delete the old ones first. Deletion is only possible if no
+other printer uses the same driver.</para>
+</sect2>
+
+<sect2>
+<title>Windows 200x/XP Local Security Policies</title>
+
+<indexterm><primary>Local security policies</primary></indexterm>
+<indexterm><primary>unsigned drivers</primary></indexterm>
+<para>Local security policies may not allow the installation of unsigned drivers &smbmdash; <quote>local
+security policies</quote> may not allow the installation of printer drivers at all.</para>
+
+</sect2>
+
+<sect2>
+<title>Administrator Cannot Install Printers for All Local Users</title>
+
+<para>
+<indexterm><primary>SMB printers</primary></indexterm>
+<indexterm><primary>IPP client</primary></indexterm>
+Windows XP handles SMB printers on a <quote>per-user</quote> basis.
+This means every user needs to install the printer himself or herself. To have a printer available for
+everybody, you might want to use the built-in IPP client capabilities of Win XP. Add a printer with the print
+path of <parameter>http://cupsserver:631/printers/printername</parameter>.  We're still looking into this one.
+Maybe a logon script could automatically install printers for all users.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Print Change, Notify Functions on NT Clients</title>
+
+<para>For print change, notify functions on NT++ clients.  These need to run the <command>Server</command>
+service first (renamed to <command>File &amp; Print Sharing for MS Networks</command> in XP).</para>
+
+</sect2>
+
+<sect2>
+<title>Win XP-SP1</title>
+
+<para>Win XP-SP1 introduced a Point and Print Restriction Policy (this restriction does not apply to
+<quote>Administrator</quote> or <quote>Power User</quote> groups of users). In Group Policy Object Editor, go
+to <guimenu>User Configuration -> Administrative Templates -> Control Panel -> Printers</guimenu>. The policy
+is automatically set to <constant>Enabled</constant> and the <constant>Users can only Point and Print to
+machines in their Forest</constant> . You probably need to change it to <constant>Disabled</constant> or
+<constant>Users can only Point and Print to these servers</constant> to make driver downloads from Samba
+possible.
+</para>
+</sect2>
+
+<sect2>
+<title>Print Options for All Users Can't Be Set on Windows 200x/XP</title>
+
+<para>How are you doing it? I bet the wrong way (it is not easy to find out, though). There are three
+different ways to bring you to a dialog that <emphasis>seems</emphasis> to set everything. All three dialogs
+<emphasis>look</emphasis> the same, yet only one of them does what you intend. You need to be Administrator or
+Print Administrator to do this for all users. Here is how I do in on XP:
+</para>
+
+<orderedlist numeration="upperalpha">
+
+	<listitem><para>The first wrong way:
+
+		<orderedlist>
+		<listitem><para>Open the <guilabel>Printers</guilabel>
+		folder.</para></listitem>
+
+		<listitem><para>Right-click on the printer
+		(<guilabel>remoteprinter on cupshost</guilabel>) and
+		select in context menu <guimenuitem>Printing
+		Preferences...</guimenuitem></para></listitem>.
+
+		<listitem><para>Look at this dialog closely and remember what it looks like.</para></listitem>
+		</orderedlist>
+	</para></listitem>
+
+	<listitem><para>The second wrong way:
+	<orderedlist>
+		<listitem><para>Open the <guilabel>Printers</guilabel> folder.</para></listitem>
+
+		<listitem><para>Right-click on the printer (<guilabel>remoteprinter on
+		cupshost</guilabel>) and select the context menu
+		<guimenuitem>Properties</guimenuitem>.</para></listitem>
+
+		<listitem><para>Click on the <guilabel>General</guilabel> tab.</para></listitem>
+
+		<listitem><para>Click on the button <guibutton>Printing
+		Preferences...</guibutton></para></listitem>.
+
+		<listitem><para>A new dialog opens. Keep this dialog open and go back
+		to the parent dialog.</para></listitem>
+	</orderedlist>
+	</para></listitem>
+
+	<listitem><para>The third and correct way: 
+	<orderedlist>
+		<listitem><para>Open the <guilabel>Printers</guilabel> folder.</para></listitem>
+
+		<listitem><para>Right-click on the printer (<guilabel>remoteprinter on
+		cupshost</guilabel>) and select the context menu
+		<guimenuitem>Properties</guimenuitem>.</para></listitem>
+
+		<listitem><para>Click on the <guilabel>Advanced</guilabel>
+		tab. (If everything is <quote>grayed out,</quote> then you are not logged
+		in as a user with enough privileges).</para></listitem>
+
+		<listitem><para>Click on the <guibutton>Printing
+		Defaults...</guibutton> button.</para></listitem>
+
+		<listitem><para>On any of the two new tabs, click on the
+		<guibutton>Advanced...</guibutton> button.</para></listitem>
+
+		<listitem><para>A new dialog opens. Compare this one to the other
+		identical-looking one from step <quote>B.5</quote> or A.3".</para></listitem>
+	</orderedlist>
+	</para></listitem>
+</orderedlist>
+
+<para>
+Do you see any difference? I don't either. However, only the last one, which you arrived at with steps
+<quote>C.1. to C.6.</quote>, will save any settings permanently and be the defaults for new users. If you want
+all clients to get the same defaults, you need to conduct these steps <emphasis>as Administrator</emphasis>
+(<smbconfoption name="printer admin"/> in &smb.conf;) <emphasis>before</emphasis> a client downloads the
+driver (the clients can later set their own <emphasis>per-user defaults</emphasis> by following the procedures
+<emphasis>A</emphasis> or <emphasis>B</emphasis>).
+</para>
+
+</sect2>
+
+<sect2>
+<title>Most Common Blunders in Driver Settings on Windows Clients</title>
+
+<para>
+Don't use <parameter>Optimize for Speed</parameter>, but use <parameter>Optimize for Portability</parameter>
+instead (Adobe PS Driver). Don't use <parameter>Page Independence: No</parameter>. Always settle with
+<parameter>Page Independence: Yes</parameter> (Microsoft PS Driver and CUPS PS Driver for Windows NT/200x/XP).
+If there are problems with fonts, use <parameter>Download as Softfont into printer</parameter> (Adobe PS
+Driver). For <guilabel>TrueType Download Options</guilabel> choose <constant>Outline</constant>. Use
+PostScript Level 2 if you are having trouble with a non-PS printer and if there is a choice.
+</para>
+
+</sect2>
+
+<sect2>
+<title><command>cupsaddsmb</command> Does Not Work with Newly Installed Printer</title>
+
+<para>
+Symptom: The last command of <command>cupsaddsmb</command> does not complete successfully. If the <command>cmd
+= setdriver printername printername</command> result was NT_STATUS_UNSUCCESSFUL, then possibly the printer was
+not yet recognized by Samba. Did it show up in Network Neighborhood? Did it show up in <command>rpcclient
+hostname -c `enumprinters'</command>? Restart smbd (or send a <command>kill -HUP</command> to all processes
+listed by <command>smbstatus</command>, and try again.
+</para></sect2>
+
+<sect2>
+<title>Permissions on <filename>/var/spool/samba/</filename> Get Reset After Each Reboot</title>
+
+<para>
+Have you ever by accident set the CUPS spool directory to the same location (<parameter>RequestRoot
+/var/spool/samba/</parameter> in <filename>cupsd.conf</filename> or the other way round:
+<filename>/var/spool/cups/</filename> is set as <smbconfoption name="path"/>> in the <smbconfsection
+name="[printers]"/> section)? These <parameter>must</parameter> be different. Set <parameter>RequestRoot
+/var/spool/cups/</parameter> in <filename>cupsd.conf</filename> and <smbconfoption name="path">
+/var/spool/samba</smbconfoption> in the <smbconfsection name="[printers]"/> section of &smb.conf;. Otherwise,
+cupsd will sanitize permissions to its spool directory with each restart and printing will not work reliably.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Print Queue Called <quote>lp</quote> Mishandles Print Jobs</title>
+
+<para>
+In this case a print queue called <quote>lp</quote> intermittently swallows jobs and
+spits out completely different ones from what was sent.
+</para>
+
+<para>
+<indexterm><primary>lp</primary></indexterm>
+<indexterm><primary>Implicit Classes</primary></indexterm>
+<indexterm><primary>BrowseShortNames</primary></indexterm>
+It is a bad idea to name any printer <quote>lp</quote>. This is the traditional UNIX name for the default
+printer. CUPS may be set up to do an automatic creation of Implicit Classes. This means, to group all printers
+with the same name to a pool of devices and load-balance the jobs across them in a round-robin fashion.
+Chances are high that someone else has a printer named <quote>lp</quote> too. You may receive that person's
+jobs and send your own to his or her device unwittingly. To have tight control over the printer names, set
+<parameter>BrowseShortNames No</parameter>. It will present any printer as
+<replaceable>printername@cupshost</replaceable>, which gives you better control over what may happen in a
+large networked environment.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Location of Adobe PostScript Driver Files for <quote>cupsaddsmb</quote></title>
+
+<para>
+Use <command>smbclient</command> to connect to any Windows box with a shared PostScript printer:
+<command>smbclient //windowsbox/print\$ -U guest</command>. You can navigate to the
+<filename>W32X86/2</filename> subdir to <command>mget ADOBE*</command> and other files or to
+<filename>WIN40/0</filename> to do the same.  Another option is to download the <filename>*.exe</filename>
+packaged files from the Adobe Web site.
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Overview of the CUPS Printing Processes</title>
+
+<para>
+A complete overview of the CUPS printing processes can be found in <link linkend="a_small">the CUPS
+Printing Overview diagram</link>.
+</para>
+
+<figure id="a_small">
+	<title>CUPS Printing Overview.</title>
+	<imagefile scale="45">a_small</imagefile>
+</figure>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-ChangeNotes.xml b/docs-xml/Samba3-HOWTO/TOSHARG-ChangeNotes.xml
new file mode 100644
index 00000000000..6c2af32a754
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-ChangeNotes.xml
@@ -0,0 +1,244 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="ChangeNotes">
+<chapterinfo>
+	&author.jht;
+	&author.jerry;
+</chapterinfo>
+
+<title>Important and Critical Change Notes for the Samba 3.x Series</title>
+<para>
+Please read this chapter carefully before update or upgrading Samba.  You should expect to find only critical
+or very important information here. Comprehensive change notes and guidance information can be found in the
+section <link linkend="upgrading-to-3.0">Updating and Upgrading Samba</link>.
+</para>
+
+<sect1>
+
+<title>Important Samba-3.2.x Change Notes</title>
+<para>
+!!!!!!!!!!!!Add all critical update notes here!!!!!!!!!!!!!
+</para>
+
+</sect1>
+
+<sect1>
+
+<title>Important Samba-3.0.x Change Notes</title>
+<para>
+These following notes pertain in particular to Samba 3.0.23 through Samba 3.0.25c (or more recent 3.0.25
+update).  Samba is a fluid and ever changing project. Changes throughout the 3.0.x series release are
+documented in this documention - See <link linkend="oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</link>.
+</para>
+
+<para>
+Sometimes it is difficult to figure out which part, or parts, of the HOWTO documentation should be updated to
+reflect the impact of new or modified features. At other times it becomes clear that the documentation is in
+need of being restructured.
+</para>
+
+<para>
+In recent times a group of Samba users has joined the thrust to create a new <ulink
+url="http://wiki.samba.org/">Samba Wiki</ulink> that is slated to become the all-singing and all-dancing
+new face of Samba documentation. Hopefully, the Wiki will benefit from greater community input and
+thus may be kept more up to date. Until that golden dream materializes and matures it is necessary to
+continue to maintain the HOWTO. This chapter will document major departures from earlier behavior until
+such time as the body of this HOWTO is restructured or modified.
+</para>
+
+<para>
+This chapter is new to the release of the HOWTO for Samba 3.0.23. It includes much of the notes provided
+in the <filename>WHATSNEW.txt</filename> file that is included with the Samba source code release tarball.
+</para>
+
+<sect2>
+<title>User and Group Changes</title>
+
+<para>
+The change documented here affects unmapped user and group accounts only.
+</para>
+
+<para>
+<indexterm><primary>user</primary></indexterm>
+<indexterm><primary>group</primary></indexterm>
+<indexterm><primary>Relative Identifiers</primary><see>RID</see></indexterm>
+<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>vampire</tertiary></indexterm>
+The user and group internal management routines have been rewritten to prevent overlaps of
+assigned Relative Identifiers (RIDs).  In the past the has been a potential problem when
+either manually mapping Unix groups with the <command>net groupmap</command> command or
+when migrating a Windows domain to a Samba domain by executing:
+<command>net rpc vampire</command>.
+</para>
+
+<para>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>SAM</primary></indexterm>
+<indexterm><primary>RID</primary></indexterm>
+<indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
+Unmapped users are now assigned a SID in the <literal>S-1-22-1</literal> domain and unmapped
+groups are assigned a SID in the <literal>S-1-22-2</literal> domain.  Previously they were
+assigned a RID within the SAM on the Samba server.  For a domain controller this would have been under the
+authority of the domain SID where as on a member server or standalone server, this would have
+been under the authority of the local SAM (see the man page for <command>net getlocalsid</command>).
+</para>
+
+<para>
+<indexterm><primary>unmapped users</primary></indexterm>
+<indexterm><primary>unmapped groups</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>NTFS</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+The result is that any unmapped users or groups on an upgraded Samba domain controller may
+be assigned a new SID.  Because the SID rather than a name is stored in Windows security
+descriptors, this can cause a user to no longer have access to a resource for example if a
+file was copied from a Samba file server to a local Windows client NTFS partition.  Any files
+stored on the Samba server itself will continue to be accessible because UNIX stores the UNIX
+GID and not the SID for authorization checks.
+</para>
+
+<para>
+An example helps to illustrate the change:
+</para>
+
+<para>
+<indexterm><primary>group mapping</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>ACL</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+Assume that a group named <emphasis>developers</emphasis> exists with a UNIX GID of 782. In this
+case this user does not exist in Samba's group mapping table. It would be perfectly normal for
+this group to be appear in an ACL editor.  Prior to Samba-3.0.23, the group SID might appear as
+<literal>S-1-5-21-647511796-4126122067-3123570092-2565</literal>.
+</para>
+
+<para>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>NTFS</primary></indexterm>
+<indexterm><primary>access</primary></indexterm>
+<indexterm><primary>group permissions</primary></indexterm>
+With the release of Samba-3.0.23, the group SID would be reported as <literal>S-1-22-2-782</literal>.  Any
+security descriptors associated with files stored on a Windows NTFS disk partition will not allow access based
+on the group permissions if the user was not a member of the
+<literal>S-1-5-21-647511796-4126122067-3123570092-2565</literal>  group.  Because this group SID is
+<literal>S-1-22-2-782</literal> and not reported in a user's token, Windows would fail the authorization check
+even though both SIDs in some respect refer to the same UNIX group.
+</para>
+
+<para>
+<indexterm><primary>group mapping</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+The workaround for versions of Samba prior to 3.0.23, is to create a manual domain group mapping
+entry for the group <emphasis>developers</emphasis> to point at the
+<literal>S-1-5-21-647511796-4126122067-3123570092-2565</literal> SID. With the release of Samba-3.0.23 this
+workaround is no longer needed.
+</para>
+</sect2>
+
+<sect2>
+<title>Essential Group Mappings</title>
+<para>
+Samba 3.0.x series  releases before 3.0.23 automatically created group mappings for the essential Windows
+domain groups <literal>Domain Admins, Domain Users, Domain Guests</literal>. Commencing with Samba 3.0.23
+these mappings need to be created by the Samba administrator. Failure to do this may result in a failure to
+correctly authenticate and recoognize valid domain users. When this happens users will not be able to log onto
+the Windows client.
+</para>
+
+<note><para>
+Group mappings are essentail only if the Samba servers is running as a PDC/BDC. Stand-alone servers do not
+require these group mappings.
+</para></note>
+
+<para>
+The following mappings are required:
+</para>
+
+<table frame="all" id="TOSH-domgroups">
+	<title>Essential Domain Group Mappings</title>
+	<tgroup align="center" cols="3">
+	<thead>
+		<row><entry>Domain Group</entry><entry>RID</entry><entry>Example UNIX Group</entry></row>
+	</thead>
+	<tbody>
+		<row><entry>Domain Admins</entry><entry>512</entry><entry>root</entry></row>
+		<row><entry>Domain Users</entry><entry>513</entry><entry>users</entry></row>
+		<row><entry>Domain Guests</entry><entry>514</entry><entry>nobody</entry></row>
+	</tbody>
+	</tgroup>
+</table>
+
+<para>
+When the POSIX (UNIX) groups are stored in LDAP, it may be desirable to call these <literal>domadmins, domusers,
+domguests</literal> respectively.
+</para>
+
+<para>
+For further information regarding group mappings see <link linkend="groupmapping">Group Mapping: MS Windows
+and UNIX</link>.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Passdb Changes</title>
+
+<para>
+<indexterm><primary>backends</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>SQL</primary></indexterm>
+<indexterm><primary>XML</primary></indexterm>
+The <smbconfoption name="passdb backend"/> parameter no long accepts multiple passdb backends in a
+chained configuration.  Also be aware that the SQL and XML based passdb modules have been
+removed in the Samba-3.0.23 release.  More information regarding external support for a SQL
+passdb module can be found on the  <ulink url="http://pdbsql.sourceforge.net/">pdbsql</ulink> web site.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Group Mapping Changes in Samba-3.0.23</title>
+
+<para>
+<indexterm><primary>default mapping</primary></indexterm>
+<indexterm><primary>Domain Admins</primary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>tdbsam</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>group mappings</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>IDMAP</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>domain groups</primary></indexterm>
+The default mapping entries for groups such as <literal>Domain Admins</literal> are no longer
+created when using an <literal>smbpasswd</literal> file or a <literal>tdbsam</literal> passdb
+backend.  This means that it is necessary to explicitly execute the <command>net groupmap add</command>
+to create group mappings, rather than use the <command>net groupmap modify</command> method to create the
+Windows group SID to UNIX GID mappings.  This change has no effect on winbindd's IDMAP functionality
+for domain groups.
+</para>
+
+</sect2>
+
+<sect2>
+<title>LDAP Changes in Samba-3.0.23</title>
+
+<para>
+<indexterm><primary>LDAP schema</primary></indexterm>
+<indexterm><primary>sambaSID</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>slapindex</primary></indexterm>
+<indexterm><primary>slapd.conf</primary></indexterm>
+There has been a minor update the Samba LDAP schema file. A substring matching rule has been
+added to the <literal>sambaSID</literal> attribute definition.  For OpenLDAP servers, this
+will require the addition of <literal>index sambaSID sub</literal> to the
+<filename>slapd.conf</filename> configuration file.  It will be necessary to execute the
+<command>slapindex</command> command after making this change. There has been no change to the
+actual data storage schema.
+</para>
+
+</sect2>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml
new file mode 100644
index 00000000000..130da819e8d
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml
@@ -0,0 +1,590 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="compiling">
+<chapterinfo>
+	&author.jelmer;
+	&author.jht;
+	&author.tridge;
+	
+	<pubdate> 22 May 2001 </pubdate>
+	<pubdate> 18 March 2003 </pubdate>
+	<pubdate> June 2005 </pubdate>
+</chapterinfo>
+
+<title>How to Compile Samba</title>
+
+<para>
+You can obtain the Samba source file from the
+<ulink url="http://samba.org/">Samba Web site</ulink>. To obtain a development version, 
+you can download Samba from Subversion or using <command>rsync</command>.
+</para>
+
+<sect1>
+<title>Access Samba Source Code via Subversion</title>
+
+
+<sect2>
+<title>Introduction</title>
+
+<para>
+<indexterm><primary>Subversion</primary></indexterm>
+Samba is developed in an open environment. Developers use a
+Subversion to <quote>checkin</quote> (also known as 
+<quote>commit</quote>) new source code. Samba's various Subversion branches can
+be accessed via anonymous Subversion using the instructions
+detailed in this chapter.
+</para>
+
+<para>
+This chapter is a modified version of the instructions found at the
+<ulink noescape="1" url="http://samba.org/samba/subversion.html">Samba</ulink> Web site.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Subversion Access to samba.org</title>
+
+<para>
+The machine samba.org runs a publicly accessible Subversion
+repository for access to the source code of several packages, 
+including Samba, rsync, distcc, ccache, and jitterbug. There are two main ways
+of accessing the Subversion server on this host.
+</para>
+
+<sect3>
+<title>Access via ViewCVS</title>
+
+
+<para>
+<indexterm><primary>SVN</primary><secondary>web</secondary></indexterm>
+You can access the source code via your favorite WWW browser. This allows you to access
+the contents of individual files in the repository and also to look at the revision 
+history and commit logs of individual files. You can also ask for a diff 
+listing between any two versions on the repository.
+</para>
+
+<para>
+Use the URL
+<ulink noescape="1" url="http://viewcvs.samba.org/">http://viewcvs.samba.org/</ulink>.
+</para>
+</sect3>
+
+<sect3>
+<title>Access via Subversion</title>
+
+<para>
+<indexterm><primary>Subversion</primary></indexterm>
+You can also access the source code via a normal Subversion client. This gives you much more control over what
+you can do with the repository and allows you to check out whole source trees and keep them up to date via
+normal Subversion commands. This is the preferred method of access if you are a developer and not just a
+casual browser.
+</para>
+
+<para>In order to be able to download the Samba sources off Subversion, you need 
+a Subversion client. Your distribution might include one, or you can download the 
+sources from <ulink noescape="1" url="http://subversion.tigris.org/">http://subversion.tigris.org/</ulink>.
+</para>
+
+<para>
+To gain access via anonymous Subversion, use the following steps. 
+</para>
+
+<procedure>
+	<title>Retrieving Samba using Subversion</title>
+
+	<step>
+	<para>
+	Install a recent copy of Subversion. All you really need is a 
+	copy of the Subversion client binary. 
+	</para>
+	</step>
+
+	<step>
+	<para>
+	Run the command 
+	<screen>
+	<userinput>svn co svn://svnanon.samba.org/samba/trunk samba</userinput>.
+	</screen>
+	</para>
+	
+	<para>
+	This will create a directory called <filename>samba</filename> containing the 
+	latest Samba source code (usually the branch that is going to be the next major release). This 
+	currently corresponds to the 3.1 development tree. 
+	</para>
+	
+	<para>
+	Subversion branches other then trunk can be obtained by adding branches/BRANCH_NAME to the URL you check
+	out. A list of branch names can be found on the <quote>Development</quote> page of the Samba Web site. A
+	common request is to obtain the latest 3.0 release code. This could be done by using the following command:
+	<screen>
+	<userinput>svn co svn://svnanon.samba.org/samba/branches/SAMBA_3_0 samba_3</userinput>.
+	</screen>
+	</para>
+	</step>
+
+	<step>
+	<para>
+	Whenever you want to merge in the latest code changes, use the following command from within the Samba
+	directory:
+	<screen>
+	<userinput>svn update</userinput>
+	</screen>
+	</para>
+	</step>
+</procedure>
+	
+</sect3>
+</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Accessing the Samba Sources via rsync and ftp</title>
+
+
+	<para>
+	<indexterm><primary>rsync</primary></indexterm>
+	<indexterm><primary>ftp</primary></indexterm>
+	<parameter>pserver.samba.org</parameter> also exports unpacked copies of most parts of the Subversion tree
+	at the Samba <ulink noescape="1" url="ftp://pserver.samba.org/pub/unpacked">pserver</ulink> location and also
+	via anonymous rsync at the Samba <ulink noescape="1"
+	url="rsync://pserver.samba.org/ftp/unpacked/">rsync</ulink> server location.  I recommend using rsync rather
+	than ftp, because rsync is capable of compressing data streams, but it is also more useful than FTP because
+	during a partial update it will transfer only the data that is missing plus a small overhead.  See <ulink
+	noescape="1" url="http://rsync.samba.org/">the rsync home page</ulink> for more info on rsync.
+	</para>
+
+	<para>
+	The disadvantage of the unpacked trees is that they do not support automatic
+	merging of local changes as Subversion does. <command>rsync</command> access is most convenient 
+	for an initial install.                      
+	</para>
+</sect1>
+
+<sect1>
+<title>Verifying Samba's PGP Signature</title>
+
+<para>
+<indexterm><primary>GPG</primary></indexterm>
+<indexterm><primary>PGP</primary></indexterm>
+It is strongly recommended that you verify the PGP signature for any source file before
+installing it. Even if you're not downloading from a mirror site, verifying PGP signatures
+should be a standard reflex. Many people today use the GNU GPG tool set in place of PGP.
+GPG can substitute for PGP.
+</para>
+
+
+<para>
+With that said, go ahead and download the following files:
+</para>
+
+<para><screen>
+&prompt;<userinput>wget http://us1.samba.org/samba/ftp/samba-3.0.20.tar.asc</userinput>
+&prompt;<userinput>wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</userinput>
+</screen></para>
+
+
+<para>
+<indexterm><primary>PGP</primary></indexterm>
+The first file is the PGP signature for the Samba source file; the other is the Samba public
+PGP key itself. Import the public PGP key with:
+<screen>
+&prompt;<userinput>gpg --import samba-pubkey.asc</userinput>
+</screen>
+and verify the Samba source code integrity with:
+<screen>
+&prompt;<userinput>gzip -d samba-3.0.20.tar.gz</userinput>
+&prompt;<userinput>gpg --verify samba-3.0.20.tar.asc</userinput>
+</screen>
+</para>
+
+<para>
+If you receive a message like, <quote>Good signature from Samba Distribution Verification Key...,</quote>
+then all is well. The warnings about trust relationships can be ignored. An
+example of what you would not want to see would be:
+<screen>
+gpg: BAD signature from <quote>Samba Distribution Verification Key</quote>
+</screen>
+</para>
+
+</sect1>
+
+<sect1>
+	<title>Building the Binaries</title>
+	
+	<para>
+	<indexterm><primary>autogen.sh</primary></indexterm>
+<indexterm><primary>configure</primary></indexterm>
+	After the source tarball has been unpacked, the next step involves
+	configuration to match Samba to your operating system platform.
+	If your source directory does not contain the <command>configure</command> script,
+	it is necessary to build it before you can continue. Building of
+	the configure script requires the correct version of the autoconf
+	tool kit. Where the necessary version of autoconf is present,
+	the configure script can be generated by executing the following:
+<screen>
+&rootprompt; cd samba-3.0.20/source
+&rootprompt; ./autogen.sh
+</screen>
+	</para>
+	
+
+	<para>
+	<indexterm><primary>configure</primary></indexterm>
+	To build the binaries, run the program <userinput>./configure
+	</userinput> in the source directory. This should automatically 
+	configure Samba for your operating system. If you have unusual 
+	needs, then you may wish to first run:
+<screen>
+&rootprompt;<userinput>./configure --help</userinput>
+</screen>
+</para>
+	
+	<para>
+	This will help you to see what special options can be enabled. Now execute
+	<userinput>./configure</userinput> with any arguments it might need:
+<screen>
+&rootprompt;<userinput>./configure <replaceable>[... arguments ...]</replaceable></userinput>
+</screen>
+	</para>
+	
+	<para>
+	<indexterm><primary>make</primary></indexterm>
+	Execute the following create the binaries:
+<screen>
+&rootprompt; <userinput>make</userinput>
+</screen>
+	Once it is successfully compiled, you can execute the command shown here to
+	install the binaries and manual pages:
+<screen>
+&rootprompt; <userinput>make install</userinput>
+</screen>
+	</para>
+	
+	<para>
+	Some people prefer to install binary files and man pages separately. If this is
+	your wish, the binary files can be installed by executing:
+<screen>
+&rootprompt; <userinput>make installbin</userinput>
+</screen>
+	The man pages can be installed using this command:
+<screen>
+&rootprompt; <userinput>make installman</userinput>
+</screen>
+	</para>
+
+	<para>
+	Note that if you are upgrading from a previous version of Samba the old
+	versions of the binaries will be renamed with an <quote>.old</quote> extension.
+	You can go back to the previous version by executing:
+<screen>
+&rootprompt; <userinput>make revert</userinput>
+</screen>
+	As you can see from this, building and installing Samba does not need to
+	result in disaster!
+	</para>
+	
+
+	<sect2>
+	<title>Compiling Samba with Active Directory Support</title>
+	
+	<para>
+	In order to compile Samba with ADS support, you need to have installed
+	on your system:
+	</para>
+
+	<itemizedlist>
+	
+	    <listitem><para>
+		The MIT or Heimdal Kerberos development libraries
+	    (either install from the sources or use a package).
+		</para></listitem>
+	
+	    <listitem><para>
+		The OpenLDAP development libraries.
+		</para></listitem>
+	    
+	</itemizedlist>
+
+	<para>
+	If your Kerberos libraries are in a nonstandard location, then
+	remember to add the configure option
+	<option>--with-krb5=<replaceable>DIR</replaceable></option>.
+	</para>
+
+	<para>
+	After you run configure, make sure that the 
+	<filename>include/config.h</filename> it generates contain lines like this:
+<programlisting>
+#define HAVE_KRB5 1
+#define HAVE_LDAP 1
+</programlisting>
+	</para>
+
+	<para>
+	If it does not, configure did not find your KRB5 libraries or
+	your LDAP libraries. Look in <filename>config.log</filename> to figure
+	out why and fix it.
+	</para>
+
+	<sect3>
+	<title>Installing the Required Packages for Debian</title>
+
+	<para>On Debian, you need to install the following packages:</para>
+	<para>
+		<itemizedlist>
+			<listitem><para>libkrb5-dev</para></listitem>
+			<listitem><para>krb5-user</para></listitem>
+		</itemizedlist>
+	</para>
+	</sect3>
+
+	<sect3>
+	<title>Installing the Required Packages for Red Hat Linux</title>
+
+	<para>On Red Hat Linux, this means you should have at least: </para>
+	<para>
+		<itemizedlist>
+			<listitem><para>krb5-workstation (for kinit)</para></listitem>
+			<listitem><para>krb5-libs (for linking with)</para></listitem>
+			<listitem><para>krb5-devel (because you are compiling from source)</para></listitem>
+		</itemizedlist>
+	</para>
+
+	<para>in addition to the standard development environment.</para>
+
+	<para>If these files are not installed on your system, you should check the installation
+	CDs to find which has them and install the files using your tool of choice. If in doubt
+	about what tool to use, refer to the Red Hat Linux documentation.</para>
+
+	</sect3>
+
+	<sect3>
+	<title>SuSE Linux Package Requirements</title>
+
+	<para>
+	SuSE Linux installs Heimdal packages that may be required to allow you to build
+	binary packages. You should verify that the development libraries have been installed on
+	your system.
+	</para>
+
+	<para>
+	SuSE Linux Samba RPMs support Kerberos. Please refer to the documentation for
+	your SuSE Linux system for information regarding SuSE Linux specific configuration.
+	Additionally, SuSE is very active in the maintenance of Samba packages that provide
+	the maximum capabilities that are available. You should consider using SuSE-provided
+	packages where they are available.
+	</para>
+
+	</sect3>
+	
+	</sect2>
+			  
+</sect1>
+
+<sect1 id="startingSamba">
+	<title>Starting the &smbd; &nmbd; and &winbindd;</title>
+
+
+	<para>
+	<indexterm><primary>inetd</primary></indexterm>
+	You must choose to start &smbd;, &winbindd;  and &nmbd; either as daemons or from
+	<application>inetd</application>. Don't try to do both!  Either you can put
+	them in <filename> inetd.conf</filename> and have them started on demand by
+	<application>inetd</application> or <application>xinetd</application>, or you
+	can start them as daemons either from the command-line or in
+	<filename>/etc/rc.local</filename>. See the man pages for details on the
+	command line options. Take particular care to read the bit about what user
+	you need to have to start Samba. In many cases, you must be root.
+	</para>
+
+	<para>
+	The main advantage of starting &smbd; and &nmbd; using the recommended daemon method
+	is that they will respond slightly more quickly to an initial connection request.
+	</para>
+
+	<sect2>
+	<title>Starting from inetd.conf</title>
+
+	<indexterm><primary>inetd</primary></indexterm>
+	
+	<note>
+	<para>The following will be different if 
+	you use NIS, NIS+, or LDAP to distribute services maps.</para>
+	</note>
+	
+	<para>Look at your <filename>/etc/services</filename>. 
+	What is defined at port 139/tcp? If nothing is defined, 
+	then add a line like this:</para>
+
+	<para><programlisting>netbios-ssn     139/tcp</programlisting></para>
+
+	<para>Similarly for 137/udp, you should have an entry like:</para>
+
+	<para><programlisting>netbios-ns	137/udp</programlisting></para>
+
+	<para>
+	Next, edit your <filename>/etc/inetd.conf</filename> and add two lines like this:
+<programlisting>
+netbios-ssn stream tcp nowait root /usr/local/samba/sbin/smbd smbd 
+netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd 
+</programlisting>
+	</para>
+
+<indexterm><primary>/etc/inetd.conf</primary></indexterm>
+	<para>
+	The exact syntax of <filename>/etc/inetd.conf</filename> 
+	varies between UNIXes. Look at the other entries in inetd.conf 
+	for a guide.
+	</para>
+
+	<para>
+	<indexterm><primary>xinetd</primary></indexterm>
+	Some distributions use xinetd instead of inetd. Consult the 
+	xinetd manual for configuration information.
+	</para>
+
+	<note><para>Some UNIXes already have entries like netbios_ns 
+	(note the underscore) in <filename>/etc/services</filename>. 
+	You must edit <filename>/etc/services</filename> or
+	<filename>/etc/inetd.conf</filename> to make them consistent.
+	</para></note>
+
+	<note><para>
+	<indexterm><primary>ifconfig</primary></indexterm>
+	On many systems you may need to use the
+	<smbconfoption name="interfaces"/> option in &smb.conf; to specify
+	the IP address and netmask of your interfaces. Run 
+	<application>ifconfig</application> as root if you do
+	not know what the broadcast is for your net. &nmbd; tries
+	to determine it at runtime, but fails on some UNIXes. 
+	</para></note>
+
+	<warning><para>
+	Many UNIXes only accept around five parameters on the command
+	line in <filename>inetd.conf</filename>.  This means you shouldn't
+	use spaces between the options and arguments, or you should use
+	a script and start the script from <command>inetd</command>.
+	</para></warning>
+
+	<para>
+	Restart <application>inetd</application>, perhaps just send it a HUP,
+	like this:
+<indexterm><primary>killall</primary></indexterm>
+<screen>
+&rootprompt;<userinput>killall -HUP inetd</userinput>
+</screen>
+	</para>
+		
+	</sect2>
+	
+	<sect2>
+	<title>Alternative: Starting &smbd; as a Daemon</title>
+		
+	<para>
+	<indexterm><primary>daemon</primary></indexterm>
+<indexterm><primary>startsmb</primary></indexterm>
+	To start the server as a daemon, you should create a script something
+	like this one, perhaps calling it <filename>startsmb</filename>.
+	</para>
+
+<para><programlisting>
+#!/bin/sh
+/usr/local/samba/sbin/smbd -D 
+/usr/local/samba/sbin/winbindd -B
+/usr/local/samba/sbin/nmbd -D 
+</programlisting></para>
+
+	<para>
+	Make it executable with <command>chmod +x startsmb</command>.
+	</para>
+
+	<para>
+	You can then run <command>startsmb</command> by hand or execute
+	it from <filename>/etc/rc.local</filename>.
+	</para>
+
+	<para>
+	To kill it, send a kill signal to the processes &nmbd; and &smbd;.
+	</para>
+
+	<note><para>
+	If you use the SVR4-style init system, you may like to look at the
+	<filename>examples/svr4-startup</filename> script to make Samba fit
+	into that system.
+	</para></note>
+
+	<sect3>
+	<title>Starting Samba for Red Hat Linux</title>
+
+	<para>
+	Red Hat Linux has not always included all Samba components in the standard installation.
+	So versions of Red Hat Linux do not install the winbind utility, even though it is present
+	on the installation CDROM media. Check to see if the <command>winbindd</command> is present
+	on the system:
+<screen>
+&rootprompt; ls /usr/sbin/winbindd
+/usr/sbin/winbindd
+</screen>
+	This means that the appropriate RPM package was installed. The following response means
+	that it is not installed:
+<screen>
+/bin/ls: /usr/sbin/winbind: No such file or directory
+</screen>
+	In this case, it should be installed if you intend to use <command>winbindd</command>. Search
+	the CDROM installation media for the samba-winbind RPM and install it following Red Hat
+	guidelines.
+	</para>
+
+	<para>
+	The process for starting Samba will now be outlined. Be sure to configure Samba's &smb.conf;
+	file before starting Samba. When configured, start Samba by executing:
+<screen>
+&rootprompt; service smb start
+&rootprompt; service winbind start
+</screen>
+	These steps will start &nmbd;, &smbd; and &winbindd;.
+	</para>
+
+	<para>
+	To ensure that these services will be automatically restarted when the system is rebooted
+	execute:
+<screen>
+&rootprompt; chkconfig smb on
+&rootprompt; chkconfig winbind on
+</screen>
+	Samba will be started automatically at every system reboot.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Starting Samba for Novell SUSE Linux</title>
+
+	<para>
+	Novell SUSE Linux products automatically install all essential Samba components in a default installation.
+	Configure your &smb.conf; file, then execute the following to start Samba:
+<screen>
+&rootprompt; rcnmb start
+&rootprompt; rcsmb start
+&rootprompt; rcwinbind start
+</screen>
+	Now execute these commands so that Samba will be started automatically following a system
+	reboot:
+<screen>
+&rootprompt; chkconfig nmb on
+&rootprompt; chkconfig smb on
+&rootprompt; chkconfig winbind on
+</screen>
+	The Samba services will now be started automatically following a system reboot.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-ConfigSmarts.xml b/docs-xml/Samba3-HOWTO/TOSHARG-ConfigSmarts.xml
new file mode 100644
index 00000000000..f46cc8e1811
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-ConfigSmarts.xml
@@ -0,0 +1,392 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="cfgsmarts">
+<chapterinfo>
+	&author.jht;
+	<pubdate>June 30, 2005</pubdate>
+</chapterinfo>
+<title>Advanced Configuration Techniques</title>
+
+<para>
+<indexterm><primary>configuration techniques</primary></indexterm>
+<indexterm><primary>include</primary></indexterm>
+Since the release of the first edition of this book there have been repeated requests to better document
+configuration techniques that may help a network administrator to get more out of Samba. Some users have asked
+for documentation regarding the use of the <smbconfoption name="include">file-name</smbconfoption> parameter.
+</para>
+
+<para>
+<indexterm><primary>multiple servers</primary></indexterm>
+<indexterm><primary>multiple server personalities</primary></indexterm>
+Commencing around mid-2004 there has been increasing interest in the ability to host multiple Samba servers on
+one machine. There has also been an interest in the hosting of multiple Samba server personalities on one
+server.
+</para>
+
+<para>
+<indexterm><primary>technical reviewers</primary></indexterm>
+<indexterm><primary>reviewers</primary></indexterm>
+Feedback from technical reviewers made the inclusion of this chapter a necessity. So, here is an 
+answer the questions that have to date not been adequately addressed. Additional user input is welcome as
+it will help this chapter to mature. What is presented here is just a small beginning.
+</para>
+
+<para>
+<indexterm><primary>multiple servers</primary></indexterm>
+<indexterm><primary>multiple hosting</primary></indexterm>
+<indexterm><primary>domain controllers</primary></indexterm>
+There are a number of ways in which multiple servers can be hosted on a single Samba server. Multiple server
+hosting makes it possible to host multiple domain controllers on one machine. Each such machine is
+independent, and each can be stopped or started without affecting another.
+</para>
+
+<para>
+<indexterm><primary>multiple servers</primary></indexterm>
+<indexterm><primary>DMS</primary></indexterm>
+<indexterm><primary>anonymous server</primary></indexterm>
+Sometimes it is desirable to host multiple servers, each with its own security mode. For example, a single
+UNIX/Linux host may be a domain member server (DMS) as well as a generic anonymous print server. In this case,
+only domain member machines and domain users can access the DMS, but even guest users can access the generic
+print server. Another example of a situation where it may be beneficial to host a generic (anonymous) server
+is to host a CDROM server.
+</para>
+
+<para>
+<indexterm><primary>separate servers</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+Some environments dictate the need to have separate servers, each with their own resources, each of which are
+accessible only by certain users or groups. This is one of the simple, but highly effective, ways that Samba
+can replace many physical Windows servers in one Samba installation.
+</para>
+
+<sect1>
+<title>Implementation</title>
+
+<para>
+</para>
+
+<sect2>
+<title>Multiple Server Hosting</title>
+
+<para>
+<indexterm><primary>multiple server hosting</primary></indexterm>
+<indexterm><primary>separate instances</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>recompiling</primary></indexterm>
+<indexterm><primary>TDB</primary></indexterm>
+The use of multiple server hosting involves running multiple separate instances of Samba, each with it's own
+configuration file. This method is complicated by the fact that each instance of &nmbd;, &smbd; and &winbindd;
+must have write access to entirely separate TDB files. The ability to keep separate the TDB files used by
+&nmbd;, &smbd; and &winbindd; can be enabled either by recompiling Samba for each server hosted so each has its
+own default TDB directories, or by configuring these in the &smb.conf; file, in which case each instance of
+&nmbd;, &smbd; and &winbindd; must be told to start up with its own &smb.conf; configuration file.
+</para>
+
+<para>
+<indexterm><primary>independent</primary></indexterm>
+<indexterm><primary>listen own socket</primary></indexterm>
+<indexterm><primary>socket</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+Each instance should operate on its own IP address (that independent IP address can be an IP Alias).
+Each instance of &nmbd;, &smbd; and &winbindd; should listen only on its own IP socket. This can be secured
+using the <smbconfoption name="socket address"/> parameter. Each instance of the Samba server will have its
+own SID also, this means that the servers are discrete and independent of each other.
+</para>
+
+<para>
+<indexterm><primary>multiple server hosting</primary></indexterm>
+<indexterm><primary>private dir</primary></indexterm>
+<indexterm><primary>pid directory</primary></indexterm>
+<indexterm><primary>lock directory</primary></indexterm>
+<indexterm><primary>interfaces</primary></indexterm>
+<indexterm><primary>bind interfaces only</primary></indexterm>
+<indexterm><primary>netbios name</primary></indexterm>
+<indexterm><primary>workgroup</primary></indexterm>
+<indexterm><primary>socket address</primary></indexterm>
+The user of multiple server hosting is non-trivial, and requires careful configuration of each aspect of
+process management and start up. The &smb.conf; parameters that must be carefully configured includes:
+<smbconfoption name="private dir"/>, <smbconfoption name="pid directory"/>,<smbconfoption name="lock
+directory"/>, <smbconfoption name="interfaces"/>, <smbconfoption name="bind interfaces only"/>, <smbconfoption
+name="netbios name"/>, <smbconfoption name="workgroup"/>, <smbconfoption name="socket address"/>.
+</para>
+
+<para>
+<indexterm><primary>multiple servers</primary></indexterm>
+<indexterm><primary>contribute</primary></indexterm>
+<indexterm><primary>comprehensive documentation</primary></indexterm>
+Those who elect to create multiple Samba servers should have the ability to read and follow
+the Samba source code, and to modify it as needed. This mode of deployment is considered beyond the scope of
+this book. However, if someone will contribute more comprehensive documentation we will gladly review it, and
+if it is suitable extend this section of this chapter. Until such documentation becomes available the hosting
+of multiple samba servers on a single host is considered not supported for Samba-3 by the Samba Team.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Multiple Virtual Server Personalities</title>
+
+<para>
+<indexterm><primary>multiple virtual servers</primary></indexterm>
+<indexterm><primary>netbios alias</primary></indexterm>
+<indexterm><primary>meta-services</primary></indexterm>
+Samba has the ability to host multiple virtual servers, each of which have their own personality.  This is
+achieved by configuring an &smb.conf; file that is common to all personalities hosted.  Each server
+personality is hosted using its own <smbconfoption name="netbios alias"/> name, and each has its own distinct
+<smbconfoption name="[global]"/> section. Each server may have its own stanzas for services and meta-services.
+</para>
+
+<para>
+<indexterm><primary>workgroup</primary></indexterm>
+<indexterm><primary>security</primary></indexterm>
+<indexterm><primary>netbios aliases</primary></indexterm>
+When hosting multiple virtual servers, each with their own personality, each can be in a different workgroup.
+Only the primary server can be a domain member or a domain controller. The personality is defined by the
+combination of the <smbconfoption name="security"/> mode it is operating in, the <smbconfoption name="netbios
+aliases"/> it has, and the <smbconfoption name="workgroup"/> that is defined for it.
+</para>
+
+<para>
+<indexterm><primary>NetBIOS name</primary></indexterm>
+<indexterm><primary>NetBIOS-less SMB</primary></indexterm>
+<indexterm><primary>smb ports</primary></indexterm>
+<indexterm><primary>TCP port 139</primary></indexterm>
+<indexterm><primary>TCP port 445</primary></indexterm>
+<indexterm><primary>%L</primary></indexterm>
+This configuration style can be used either with NetBIOS names, or using NetBIOS-less SMB over TCP services.
+If run using NetBIOS mode (the most common method) it is important that the parameter <smbconfoption name="smb
+ports">139</smbconfoption> should be specified in the primary &smb.conf; file. Failure to do this will result
+in Samba operating over TCP port 445 and problematic operation at best, and at worst only being able to obtain
+the functionality that is specified in the primary &smb.conf; file. The use of NetBIOS over TCP/IP using only
+TCP port 139 means that the use of the <literal>%L</literal> macro is fully enabled. If the <smbconfoption
+name="smb ports">139</smbconfoption> is not specified (the default is <parameter>445 139</parameter>, or if
+the value of this parameter is set at <parameter>139 445</parameter> then the <literal>%L</literal> macro
+is not serviceable.
+</para>
+
+<para>
+<indexterm><primary>host multiple servers</primary></indexterm>
+<indexterm><primary>multiple personality</primary></indexterm>
+<indexterm><primary>NetBIOS-less</primary></indexterm>
+<indexterm><primary>%i macro</primary></indexterm>
+It is possible to host multiple servers, each with their own personality, using port 445 (the NetBIOS-less SMB
+port), in which case the <literal>%i</literal> macro can be used to provide separate server identities (by
+IP Address). Each can have its own <smbconfoption name="security"/> mode. It will be necessary to use the
+<smbconfoption name="interfaces"/>, <smbconfoption name="bind interfaces only"/> and IP aliases in addition to
+the <smbconfoption name="netbios name"/> parameters to create the virtual servers. This method is considerably
+more complex than that using NetBIOS names only using TCP port 139.
+</para>
+
+<para>
+<indexterm><primary>anonymous file server</primary></indexterm>
+Consider an example environment that consists of a standalone, user-mode security Samba server and a read-only
+Windows 95 file server that has to be replaced. Instead of replacing the Windows 95 machine with a new PC, it
+is possible to add this server as a read-only anonymous file server that is hosted on the Samba server. Here
+are some parameters:
+</para>
+
+<para>
+The Samba server is called <literal>ELASTIC</literal>, its workgroup name is <literal>ROBINSNEST</literal>.
+The CDROM server is called <literal>CDSERVER</literal> and its workgroup is <literal>ARTSDEPT</literal>. A
+possible implementation is shown here:
+</para>
+
+<para>
+<indexterm><primary>/etc/samba</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>smb.conf</primary></indexterm>
+The &smb.conf; file for the master server is shown in <link linkend="elastic">Elastic smb.conf File</link>.
+This file is placed in the <filename>/etc/samba</filename> directory. Only the &nmbd; and the &smbd; daemons
+are needed. When started the server will appear in Windows Network Neighborhood as the machine
+<literal>ELASTIC</literal> under the workgroup <literal>ROBINSNEST</literal>. It is helpful if the Windows
+clients that must access this server are also in the workgroup <literal>ROBINSNEST</literal> as this will make
+browsing much more reliable.
+</para>
+
+<example id="elastic">
+<title>Elastic smb.conf File</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">ROBINSNEST</smbconfoption>
+<smbconfoption name="netbios name">ELASTIC</smbconfoption>
+<smbconfoption name="netbios aliases">CDSERVER</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+<smbconfoption name="disable spoolss">Yes</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+<smbconfoption name="include">/etc/samba/smb-%L.conf</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[office]"/>
+<smbconfoption name="comment">Data</smbconfoption>
+<smbconfoption name="path">/data</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="create mask">0600</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>smb-cdserver.conf</primary></indexterm>
+The configuration file for the CDROM server is listed in <link linkend="cdserver">CDROM Server
+smb-cdserver.conf file</link>. This file is called <filename>smb-cdserver.conf</filename> and it should be
+located in the <filename>/etc/samba</filename> directory. Machines that are in the workgroup
+<literal>ARTSDEPT</literal> will be able to browse this server freely.
+</para>
+
+<example id="cdserver">
+<title>CDROM Server smb-cdserver.conf file</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">ARTSDEPT</smbconfoption>
+<smbconfoption name="netbios name">CDSERVER</smbconfoption>
+<smbconfoption name="map to guest">Bad User</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+
+<smbconfsection name="[carousel]"/>
+<smbconfoption name="comment">CDROM Share</smbconfoption>
+<smbconfoption name="path">/export/cddata</smbconfoption>
+<smbconfoption name="read only">Yes</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>different resources</primary></indexterm>
+<indexterm><primary>separate workgroups</primary></indexterm>
+<indexterm><primary>read-only access</primary></indexterm>
+<indexterm><primary>nobody account</primary></indexterm>
+The two servers have different resources and are in separate workgroups. The server <literal>ELASTIC</literal>
+can only be accessed by uses who have an appropriate account on the host server. All users will be able to
+access the CDROM data that is stored in the <filename>/export/cddata</filename> directory. File system
+permissions should set so that the <literal>others</literal> user has read-only access to the directory and its
+contents. The files can be owned by root (any user other than the nobody account).
+</para>
+
+</sect2>
+
+<sect2>
+<title>Multiple Virtual Server Hosting</title>
+
+<para>
+<indexterm><primary>primary domain controller</primary></indexterm>
+<indexterm><primary>extra machine</primary></indexterm>
+<indexterm><primary>same domain/workgroup</primary></indexterm>
+In this example, the requirement is for a primary domain controller for the domain called
+<literal>MIDEARTH</literal>. The PDC will be called <literal>MERLIN</literal>. An extra machine called
+<literal>SAURON</literal> is required. Each machine will have only its own shares. Both machines belong to the
+same domain/workgroup.
+</para>
+
+<para>
+<indexterm><primary>master smb.conf</primary></indexterm>
+<indexterm><primary>/etc/samba</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+The master &smb.conf; file is shown in <link linkend="mastersmbc">the Master smb.conf File Global Section</link>.
+The two files that specify the share information for each server are shown in <link linkend="merlinsmbc">the
+smb-merlin.conf File Share Section</link>, and <link linkend="sauronsmbc">the smb-sauron.conf File Share
+Section</link>. All three files are locate in the <filename>/etc/samba</filename> directory.
+</para>
+
+<example id="mastersmbc">
+<title>Master smb.conf File Global Section</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">MERLIN</smbconfoption>
+<smbconfoption name="netbios aliases">SAURON</smbconfoption>
+<smbconfoption name="passdb backend">tdbsam</smbconfoption>
+<smbconfoption name="smb ports">139</smbconfoption>
+<smbconfoption name="syslog">0</smbconfoption>
+<smbconfoption name="printcap name">CUPS</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="add user script">/usr/sbin/useradd -m '%u'</smbconfoption>
+<smbconfoption name="delete user script">/usr/sbin/userdel -r '%u'</smbconfoption>
+<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
+<smbconfoption name="delete group script">/usr/sbin/groupdel '%g'</smbconfoption>
+<smbconfoption name="add user to group script">/usr/sbin/usermod -G '%g' '%u'</smbconfoption>
+<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</smbconfoption>
+<smbconfoption name="logon script">scripts\login.bat</smbconfoption>
+<smbconfoption name="logon path"> </smbconfoption>
+<smbconfoption name="logon drive">X:</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="preferred master">Yes</smbconfoption>
+<smbconfoption name="wins support">Yes</smbconfoption>
+<smbconfoption name="printing">CUPS</smbconfoption>
+<smbconfoption name="include">/etc/samba/smb-%L.conf</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="merlinsmbc">
+<title>MERLIN smb-merlin.conf File Share Section</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">MERLIN</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[office]"/>
+<smbconfoption name="comment">Data</smbconfoption>
+<smbconfoption name="path">/data</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">NETLOGON</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+<smbconfoption name="read only">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="sauronsmbc">
+<title>SAURON smb-sauron.conf File Share Section</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">SAURON</smbconfoption>
+
+<smbconfsection name="[www]"/>
+<smbconfoption name="comment">Web Pages</smbconfoption>
+<smbconfoption name="path">/srv/www/htdocs</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+</smbconfblock>
+</example>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-DNS-DHCP-Configuration.xml b/docs-xml/Samba3-HOWTO/TOSHARG-DNS-DHCP-Configuration.xml
new file mode 100644
index 00000000000..f64a677159c
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-DNS-DHCP-Configuration.xml
@@ -0,0 +1,346 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="DNSDHCP">
+<chapterinfo>
+	&author.jht;
+</chapterinfo>
+
+<title>DNS and DHCP Configuration Guide</title>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>Dynamic Host Configuration Protocol</primary><see>DHCP</see></indexterm>
+<indexterm><primary>Domain Name System</primary><see>DNS</see></indexterm>
+There are few subjects in the UNIX world that might raise as much contention as
+Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP).
+Not all opinions held for or against particular implementations of DNS and DHCP
+are valid.
+</para>
+
+<para>
+We live in a modern age where many information technology users demand mobility
+and freedom. Microsoft Windows users in particular expect to be able to plug their
+notebook computer into a network port and have things <quote>just work.</quote>
+</para>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+UNIX administrators have a point. Many of the normative practices in the Microsoft
+Windows world at best border on bad practice from a security perspective.
+Microsoft Windows networking protocols allow workstations to arbitrarily register
+themselves on a network. Windows 2000 Active Directory registers entries in the DNS namespace
+that are equally perplexing to UNIX administrators. Welcome to the new world!
+</para>
+
+
+<para>
+<indexterm><primary>ISC</primary><secondary>DNS</secondary></indexterm>
+<indexterm><primary>ISC</primary><secondary>DHCP</secondary></indexterm>
+<indexterm><primary>Dynamic DNS</primary><see>DDNS</see></indexterm>
+The purpose of this chapter is to demonstrate the configuration of the Internet
+Software Consortium (ISC) DNS and DHCP servers to provide dynamic services that are
+compatible with their equivalents in the Microsoft Windows 2000 Server products.
+</para>
+
+<para>
+This chapter provides no more than a working example of configuration files for both DNS and DHCP servers. The
+examples used match configuration examples used elsewhere in this document.
+</para>
+
+<para>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>DHCP</primary></indexterm>
+<indexterm><primary>BIND9.NET</primary></indexterm>
+This chapter explicitly does not provide a tutorial, nor does it pretend to be a reference guide on DNS and
+DHCP, as this is well beyond the scope and intent of this document as a whole. Anyone who wants more detailed
+reference materials on DNS or DHCP should visit the ISC Web site at <ulink noescape="1"
+url="http://www.isc.org"> http://www.isc.org</ulink>.  Those wanting a written text might also be interested
+in the O'Reilly publications on DNS, see the <ulink
+url="http://www.oreilly.com/catalog/dns/index.htm">O'Reilly</ulink> web site, and the <ulink
+url="http://www.bind9.net/books-dhcp">BIND9.NET</ulink> web site for details.
+The books are:
+</para>
+
+<orderedlist>
+	<listitem><para>DNS and BIND, By Cricket Liu, Paul Albitz, ISBN: 1-56592-010-4</para></listitem>
+	<listitem><para>DNS &amp; Bind Cookbook, By Cricket Liu, ISBN: 0-596-00410-9</para></listitem>
+	<listitem><para>The DHCP Handbook (2nd Edition), By: Ralph Droms, Ted Lemon, ISBN 0-672-32327-3</para></listitem>
+</orderedlist>
+
+</sect1>
+
+<sect1>
+<title>Example Configuration</title>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+The DNS is to the Internet what water is to life. Nearly all information resources (host names) are resolved
+to their Internet protocol (IP) addresses through DNS.  Windows networking tried hard to avoid the
+complexities of DNS, but alas, DNS won.  <indexterm><primary>WINS</primary></indexterm> The alternative to
+DNS, the Windows Internet Name Service (WINS) &smbmdash; an artifact of NetBIOS networking over the TCP/IP
+protocols &smbmdash; has demonstrated scalability problems as well as a flat, nonhierarchical namespace that
+became unmanageable as the size and complexity of information technology networks grew.
+</para>
+
+<para>
+<indexterm><primary>RFC 1001</primary></indexterm>
+<indexterm><primary>RFC 1002</primary></indexterm>
+WINS is a Microsoft implementation of the RFC1001/1002 NetBIOS Name Service (NBNS).
+It allows NetBIOS clients (like Microsoft Windows machines) to register an arbitrary
+machine name that the administrator or user has chosen together with the IP
+address that the machine has been given. Through the use of WINS, network client machines
+could resolve machine names to their IP address.
+</para>
+
+<para>
+The demand for an alternative to the limitations of NetBIOS networking finally drove
+Microsoft to use DNS and Active Directory. Microsoft's new implementation attempts
+to use DNS in a manner similar to the way that WINS is used for NetBIOS networking.
+Both WINS and Microsoft DNS rely on dynamic name registration.
+</para> 
+
+<para>
+Microsoft Windows clients can perform dynamic name registration to the DNS server
+on startup. Alternatively, where DHCP is used to assign workstation IP addresses,
+it is possible to register hostnames and their IP address by the DHCP server as
+soon as a client acknowledges an IP address lease. Finally, Microsoft DNS can resolve
+hostnames via Microsoft WINS.
+</para>
+
+<para>
+The following configurations demonstrate a simple, insecure dynamic DNS server and
+a simple DHCP server that matches the DNS configuration.
+</para>
+
+	<sect2>
+	<title>Dynamic DNS</title>
+
+	<para>
+	<indexterm><primary>DNS</primary><secondary>Dynamic</secondary></indexterm>
+	The example DNS configuration is for a private network in the IP address
+	space for network 192.168.1.0/24. The private class network address space
+	is set forth in RFC1918.
+	</para>
+
+
+	<para>
+	<indexterm><primary>BIND</primary></indexterm>
+	It is assumed that this network will be situated behind a secure firewall.
+	The files that follow work with ISC BIND version 9. BIND is the Berkeley
+	Internet Name Daemon.
+	</para>
+
+	<para>
+	The master configuration file <filename>/etc/named.conf</filename>
+	determines the location of all further configuration files used.
+	The location and name of this file is specified in the startup script
+	that is part of the operating system.
+<programlisting>
+# Quenya.Org configuration file
+
+acl mynet {
+	192.168.1.0/24;
+	127.0.0.1;
+};
+
+options {
+
+	directory "/var/named";
+	listen-on-v6 { any; };
+	notify no;
+	forward first;
+	forwarders {
+		192.168.1.1;
+		};
+	auth-nxdomain yes;
+	multiple-cnames yes;
+	listen-on {
+		mynet;
+		};
+};
+
+# The following three zone definitions do not need any modification.
+# The first one defines localhost while the second defines the
+# reverse lookup for localhost. The last zone "." is the
+# definition of the root name servers.
+
+zone "localhost" in {
+	type master;
+	file "localhost.zone";
+};
+
+zone "0.0.127.in-addr.arpa" in {
+	type master;
+	file "127.0.0.zone";
+};
+
+zone "." in {
+	type hint;
+	file "root.hint";
+};
+
+# You can insert further zone records for your own domains below.
+
+zone "quenya.org" {
+	type master;
+	file "/var/named/quenya.org.hosts";
+	allow-query {
+		mynet;
+		};
+	allow-transfer {
+		mynet;
+		};
+	allow-update {
+		mynet;
+		};
+	};
+
+zone "1.168.192.in-addr.arpa" {
+	type master;
+	file "/var/named/192.168.1.0.rev";
+	allow-query {
+		mynet;
+	};
+	allow-transfer {
+		mynet;
+	};
+	allow-update {
+		mynet;
+	};
+};
+</programlisting>
+	</para>
+
+	<para>
+	The following files are all located in the directory <filename>/var/named</filename>.
+	This is the <filename>/var/named/localhost.zone</filename> file:
+<programlisting>
+$TTL 1W
+@               IN SOA  @   root (
+				42              ; serial (d. adams)
+				2D              ; refresh
+				4H              ; retry
+				6W              ; expiry
+				1W )            ; minimum
+
+		IN NS           @
+		IN A            127.0.0.1
+	</programlisting>
+	</para>
+
+	<para>
+	The <filename>/var/named/127.0.0.zone</filename> file:
+<programlisting>
+$TTL 1W
+@               IN SOA          localhost.  root.localhost. (
+				42              ; serial (d. adams)
+				2D              ; refresh
+				4H              ; retry
+				6W              ; expiry
+				1W )            ; minimum
+
+				IN NS           localhost.
+1               IN PTR          localhost.
+</programlisting>
+	</para>
+
+	<para>
+		The <filename>/var/named/quenya.org.host</filename> file:
+<programlisting>
+$ORIGIN .
+$TTL 38400      ; 10 hours 40 minutes
+quenya.org      IN SOA  marvel.quenya.org. root.quenya.org. (
+				2003021832 ; serial
+				10800      ; refresh (3 hours)
+				3600       ; retry (1 hour)
+				604800     ; expire (1 week)
+				38400      ; minimum (10 hours 40 minutes)
+				)
+			NS      marvel.quenya.org.
+			MX      10 mail.quenya.org.
+$ORIGIN quenya.org.
+frodo                   A       192.168.1.1
+marvel                  A       192.168.1.2
+;
+mail                    CNAME   marvel
+www                     CNAME   marvel
+</programlisting>
+</para>
+
+<para>
+	The <filename>/var/named/192.168.1.0.rev</filename> file:
+<programlisting>
+$ORIGIN .
+$TTL 38400      ; 10 hours 40 minutes
+1.168.192.in-addr.arpa  IN SOA  marvel.quenya.org. root.quenya.org. (
+				2003021824 ; serial
+				10800      ; refresh (3 hours)
+				3600       ; retry (1 hour)
+				604800     ; expire (1 week)
+				38400      ; minimum (10 hours 40 minutes)
+				)
+			NS      marvel.quenya.org.
+$ORIGIN 1.168.192.in-addr.arpa.
+1                       PTR     frodo.quenya.org.
+2                       PTR     marvel.quenya.org.
+</programlisting>
+	</para>
+
+	<para>
+<indexterm><primary>BIND</primary></indexterm>
+<indexterm><primary>dynamic registration files</primary></indexterm>
+	The configuration files shown here were copied from a fully working system. All dynamically registered
+	entries have been removed. In addition to these files, BIND version 9 will
+	create for each of the dynamic registration files a file that has a 
+	<filename>.jnl</filename> extension. Do not edit or tamper with the configuration
+	files or with the <filename>.jnl</filename> files that are created.
+	</para>
+
+	</sect2>
+
+	<sect2 id="DHCP">
+	<title>DHCP Server</title>
+
+	<para>
+	The following file is used with the ISC DHCP Server version 3.
+	The file is located in <filename>/etc/dhcpd.conf</filename>:
+	</para>
+
+	<para>
+	<programlisting>
+ddns-updates on;
+ddns-domainname "quenya.org";
+option ntp-servers 192.168.1.2;
+ddns-update-style ad-hoc;
+allow unknown-clients;
+default-lease-time 86400;
+max-lease-time 172800;
+
+option domain-name "quenya.org";
+option domain-name-servers 192.168.1.2;
+option netbios-name-servers 192.168.1.2;
+option netbios-dd-server 192.168.1.2;
+option netbios-node-type 8;
+
+subnet 192.168.1.0 netmask 255.255.255.0 {
+	range dynamic-bootp 192.168.1.60 192.168.1.254;
+	option subnet-mask 255.255.255.0;
+	option routers 192.168.1.2;
+	allow unknown-clients;
+}
+</programlisting>
+	</para>
+
+	<para>
+	In this example, IP addresses between 192.168.1.1 and 192.168.1.59 are
+	reserved for fixed-address (commonly called <constant>hard-wired</constant>) IP addresses. The
+	addresses between 192.168.1.60 and 192.168.1.254 are allocated for dynamic use.
+	</para>
+
+	</sect2>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml
new file mode 100644
index 00000000000..951c879b497
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml
@@ -0,0 +1,603 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="diagnosis">
+<chapterinfo>
+	&author.tridge;
+	&author.jelmer;
+	&author.danshearer;
+	<pubdate>Wed Jan 15</pubdate>
+</chapterinfo>
+
+<title>The Samba Checklist</title>
+
+<sect1>
+<title>Introduction</title>
+
+<para>
+<indexterm><primary>validate</primary></indexterm>
+This file contains a list of tests you can perform to validate your
+Samba server. It also tells you what the likely cause of the problem
+is if it fails any one of these steps. If it passes all these tests,
+then it is probably working fine.
+</para>
+
+<para>
+You should do all the tests in the order shown. We have tried to
+carefully choose them so later tests only use capabilities verified in
+the earlier tests. However, do not stop at the first error: there
+have been some instances when continuing with the tests has helped
+to solve a problem.
+</para>
+
+<para>
+If you send one of the Samba mailing lists  an email saying, <quote>It does not work,</quote>
+and you have not followed this test procedure, you should not be surprised
+if your email is ignored.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Assumptions</title>
+
+<para>
+In all of the tests, it is assumed you have a Samba server called 
+BIGSERVER and a PC called ACLIENT, both in workgroup TESTGROUP.
+</para>
+
+<para>
+The procedure is similar for other types of clients.
+</para>
+
+<para>
+It is also assumed you know the name of an available share in your
+&smb.conf;. I for our examples this share is called <smbconfsection name="tmp"/>.
+You can add a <smbconfsection name="tmp"/> share like this by adding the
+lines shown in <link linkend="tmpshare">the next example</link>.
+</para>
+
+<example id="tmpshare">
+<title>smb.conf with [tmp] Share</title>
+<smbconfblock>
+<smbconfsection name="[tmp]"/>
+<smbconfoption name="comment">temporary files </smbconfoption>
+<smbconfoption name="path">/tmp</smbconfoption>
+<smbconfoption name="read only">yes</smbconfoption>
+</smbconfblock>
+</example>
+
+<note><para>
+These tests assume version 3.0.0 or later of the Samba suite.
+Some commands shown did not exist in earlier versions. 
+</para></note>
+
+<para>
+<indexterm><primary>error messages</primary></indexterm>
+<indexterm><primary>name resolution</primary></indexterm>
+<indexterm><primary>/etc/resolv.conf</primary></indexterm>
+Please pay attention to the error messages you receive. If any error message
+reports that your server is being unfriendly, you should first check that your
+IP name resolution is correctly set up. Make sure your <filename>/etc/resolv.conf</filename>
+file points to name servers that really do exist.
+</para>
+
+<para>
+<indexterm><primary>DNS server access</primary></indexterm>
+<indexterm><primary>name resolution</primary></indexterm>
+<indexterm><primary>dns proxy</primary></indexterm>
+<indexterm><primary>testparm</primary></indexterm>
+Also, if you do not have DNS server access for name resolution, please check
+that the settings for your &smb.conf; file results in <parameter>dns proxy = no</parameter>. The
+best way to check this is with <command>testparm smb.conf</command>.
+</para>
+
+
+<para>
+<indexterm><primary>log files</primary></indexterm>
+<indexterm><primary>tail</primary></indexterm>
+<indexterm><primary>/usr/local/samba/var</primary></indexterm>
+<indexterm><primary>/var/log/samba</primary></indexterm>
+<indexterm><primary>log files</primary><secondary>monitoring</secondary></indexterm>
+It is helpful to monitor the log files during testing by using the
+<command>tail -F log_file_name</command> in a separate
+terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X). 
+Relevant log files can be found (for default installations) in
+<filename>/usr/local/samba/var</filename>. Also, connection logs from
+machines can be found here or possibly in <filename>/var/log/samba</filename>,
+depending on how or if you specified logging in your &smb.conf; file.
+</para>
+
+<para>
+If you make changes to your &smb.conf; file while going through these test,
+remember to restart &smbd; and &nmbd;.
+</para>
+
+</sect1>
+
+<sect1>
+<title>The Tests</title>
+<procedure>
+<title>Diagnosing Your Samba Server</title>
+
+
+<step performance="required">
+<para>
+<indexterm><primary>testparm</primary></indexterm>
+In the directory in which you store your &smb.conf; file, run the command
+<command>testparm smb.conf</command>. If it reports any errors, then your &smb.conf;
+configuration file is faulty.
+</para>
+
+<note><para>
+<indexterm><primary>/etc/samba</primary></indexterm>
+<indexterm><primary>/usr/local/samba/lib</primary></indexterm>
+Your &smb.conf; file may be located in <filename>/etc/samba</filename>
+or in <filename>/usr/local/samba/lib</filename>.
+</para></note>
+</step>
+
+<step performance="required">
+<para>
+<indexterm><primary>ping</primary></indexterm>
+Run the command <command>ping BIGSERVER</command> from the PC and
+<command>ping ACLIENT</command> from the UNIX box. If you do not get a valid response,
+then your TCP/IP software is not correctly installed. 
+</para>
+
+<para>
+You will need to start a <quote>DOS prompt</quote> window on the PC to run ping.
+</para>
+
+<para>
+<indexterm><primary>/etc/hosts</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>/etc/resolv.conf</primary></indexterm>
+If you get a message saying <quote><errorname>host not found</errorname></quote> or a similar message, then
+your DNS software or <filename>/etc/hosts</filename> file is not correctly set up.  If using DNS, check that
+the <filename>/etc/resolv.conf</filename> has correct, current, entries in it. It is possible to run
+Samba without DNS entries for the server and client, but it is assumed you do have correct entries for the
+remainder of these tests.
+</para>
+
+<para>
+<indexterm><primary>firewall</primary></indexterm>
+<indexterm><primary>iptables</primary></indexterm>
+<indexterm><primary>ipchains</primary></indexterm>
+Another reason why ping might fail is if your host is running firewall 
+software. You will need to relax the rules to let in the workstation
+in question, perhaps by allowing access from another subnet (on Linux
+this is done via the appropriate firewall maintenance commands <command>ipchains</command>
+or <command>iptables</command>).
+</para>
+
+<note>
+<para>
+Modern Linux distributions install ipchains/iptables by default. 
+This is a common problem that is often overlooked.
+</para>
+</note>
+
+<para>
+<indexterm><primary>iptables</primary></indexterm>
+<indexterm><primary>ipchains</primary></indexterm>
+If you wish to check what firewall rules may be present in a system under test, simply run
+<command>iptables -L -v</command>, or if <parameter>ipchains</parameter>-based firewall rules are in use,
+<command>ipchains -L -v</command>.
+</para>
+
+<para>
+Here is a sample listing from a system that has an external Ethernet interface (eth1) on which Samba
+is not active and an internal (private network) interface (eth0) on which Samba is active:
+<screen>
+frodo:~ # iptables -L -v
+Chain INPUT (policy DROP 98496 packets, 12M bytes)
+ pkts bytes target     prot opt in     out     source     destination
+ 187K  109M ACCEPT     all  --  lo     any     anywhere   anywhere
+ 892K  125M ACCEPT     all  --  eth0   any     anywhere   anywhere
+1399K 1380M ACCEPT     all  --  eth1   any     anywhere   anywhere  \
+					state RELATED,ESTABLISHED
+
+Chain FORWARD (policy DROP 0 packets, 0 bytes)
+ pkts bytes target     prot opt in     out     source     destination
+ 978K 1177M ACCEPT     all  --  eth1   eth0    anywhere   anywhere \
+					state RELATED,ESTABLISHED
+ 658K   40M ACCEPT     all  --  eth0   eth1    anywhere   anywhere
+    0     0 LOG        all  --  any    any     anywhere   anywhere \
+					LOG level warning
+
+Chain OUTPUT (policy ACCEPT 2875K packets, 1508M bytes)
+ pkts bytes target     prot opt in     out     source     destination
+
+Chain reject_func (0 references)
+ pkts bytes target     prot opt in     out     source     destination
+</screen>
+</para>
+
+</step>
+
+<step performance="required">
+<para>
+Run the command <command>smbclient -L BIGSERVER</command>
+on the UNIX box. You should get back a list of available shares. 
+</para>
+
+<para>
+<indexterm><primary>bad password</primary></indexterm>
+<indexterm><primary>hosts allow</primary></indexterm>
+<indexterm><primary>hosts deny</primary></indexterm>
+<indexterm><primary>valid users</primary></indexterm>
+<indexterm><primary>guest account</primary></indexterm>
+<indexterm><primary>invalid users</primary></indexterm>
+If you get an error message containing the string <quote>bad password</quote>, then
+you probably have either an incorrect <parameter>hosts allow</parameter>, 
+<parameter>hosts deny</parameter>, or <parameter>valid users</parameter> line in your 
+&smb.conf;, or your guest account is not valid. Check what your guest account is using &testparm; and
+temporarily remove any <parameter>hosts allow</parameter>, <parameter>hosts deny</parameter>,
+<parameter>valid users</parameter>, or <parameter>invalid users</parameter> lines.
+</para>
+
+<para>
+<indexterm><primary>inetd.conf</primary></indexterm>
+If you get a message <literal>connection refused</literal> response, then the <command>smbd</command> server may
+not be running. If you installed it in <filename>inetd.conf</filename>, then you probably edited
+that file incorrectly. If you installed it as a daemon, then check that
+it is running and check that the netbios-ssn port is in a LISTEN
+state using <command>netstat -a</command>.
+</para>
+
+<note><para>
+<indexterm><primary>inetd</primary></indexterm>
+<indexterm><primary>xinetd</primary><see>inetd</see></indexterm>
+Some UNIX/Linux systems use <command>xinetd</command> in place of
+<command>inetd</command>. Check your system documentation for the location
+of the control files for your particular system implementation of
+the network super daemon.
+</para></note>
+
+<para>
+If you get a message saying <literal>session request failed,</literal> the server refused the
+connection. If it says <quote>Your server software is being unfriendly,</quote> then
+it's probably because you have invalid command line parameters to &smbd;,
+or a similar fatal problem with the initial startup of &smbd;. Also
+check your config file (&smb.conf;) for syntax errors with &testparm;
+and that the various directories where Samba keeps its log and lock
+files exist.
+</para>
+
+<para>
+There are a number of reasons for which smbd may refuse or decline
+a session request. The most common of these involve one or more of
+the &smb.conf; file entries as shown in <link linkend="modif1">the next example</link>.
+</para>
+
+
+<example id="modif1">
+<title>Configuration for Allowing Connections Only from a Certain Subnet</title>
+<smbconfblock>
+<smbconfsection name="[globals]"/>
+<smbconfoption name="hosts deny">ALL</smbconfoption>
+<smbconfoption name="hosts allow">xxx.xxx.xxx.xxx/yy</smbconfoption>
+<smbconfoption name="interfaces">eth0</smbconfoption>
+<smbconfoption name="bind interfaces only">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>loopback adapter</primary></indexterm>
+In <link linkend="modif1">Configuration for Allowing Connections Only from a Certain Subnet</link>, no
+allowance has been made for any session requests that will automatically translate to the loopback adapter
+address 127.0.0.1.  To solve this problem, change these lines as shown in <link linkend="modif2">the following
+example</link>.
+</para>
+
+<example id="modif2">
+<title>Configuration for Allowing Connections from a Certain Subnet and localhost</title>
+<smbconfblock>
+<smbconfsection name="[globals]"/>
+<smbconfoption name="hosts deny">ALL</smbconfoption>
+<smbconfoption name="hosts allow">xxx.xxx.xxx.xxx/yy 127.</smbconfoption>
+<smbconfoption name="interfaces">eth0 lo</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>inetd</primary></indexterm>
+<indexterm><primary>smbclient</primary></indexterm>
+Another common cause of these two errors is having something already running on port <constant>139</constant>,
+such as Samba (&smbd; is running from <application>inetd</application> already) or Digital's Pathworks. Check
+your <filename>inetd.conf</filename> file before trying to start &smbd; as a daemon &smbmdash; it can avoid a
+lot of frustration!
+</para>
+
+<para>
+<indexterm><primary>subnet mask</primary></indexterm>
+<indexterm><primary>broadcast address</primary></indexterm>
+<indexterm><primary>log.nmbd</primary></indexterm>
+<indexterm><primary>network interface</primary></indexterm>
+<indexterm><primary>IP address</primary></indexterm>
+And yet another possible cause for failure of this test is when the subnet mask and/or broadcast address
+settings are incorrect. Please check that the network interface IP address/broadcast address/subnet mask
+settings are correct and that Samba has correctly noted these in the <filename>log.nmbd</filename> file.
+</para>
+
+</step>
+
+<step performance="required">
+
+<para>
+<indexterm><primary>nmblookup</primary></indexterm>
+Run the command <command>nmblookup -B BIGSERVER __SAMBA__</command>.
+You should get back the IP address of your Samba server.
+</para>
+
+<para>
+<indexterm><primary>inetd.conf</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>port 137</primary></indexterm>
+If you do not, then &nmbd; is incorrectly installed. Check your <filename>inetd.conf</filename>
+if you run it from there, or that the daemon is running and listening to UDP port 137.
+</para>
+
+<para>
+One common problem is that many inetd implementations can't take many
+parameters on the command line. If this is the case, then create a
+one-line script that contains the right parameters and run that from
+inetd.
+</para>
+
+</step>
+
+<step performance="required">
+
+<para>
+<indexterm><primary>nmblookup</primary></indexterm>
+Run the command <command>nmblookup -B ACLIENT `*'</command>.
+</para>
+
+<para>
+You should get the PC's IP address back. If you do not, then the client
+software on the PC isn't installed correctly, or isn't started, or you
+got the name of the PC wrong. 
+</para>
+
+<para>
+If ACLIENT does not resolve via DNS, then use the IP address of the
+client in the above test.
+</para>
+
+</step>
+
+<step performance="required">
+
+<para>
+Run the command <command>nmblookup -d 2 `*'</command>.
+</para>
+
+<para>
+This time we are trying the same as the previous test but are trying
+it via a broadcast to the default broadcast address. A number of
+NetBIOS/TCP/IP hosts on the network should respond, although Samba may
+not catch all of the responses in the short time it listens. You
+should see the <literal>got a positive name query response</literal>
+messages from several hosts.
+</para>
+
+<para>
+<indexterm><primary>nmblookup</primary></indexterm>
+If this does not give a result similar to the previous test, then nmblookup isn't correctly getting your
+broadcast address through its automatic mechanism. In this case you should experiment with the <smbconfoption
+name="interfaces"/> option in &smb.conf; to manually configure your IP address, broadcast, and netmask.
+</para>
+
+<para>
+If your PC and server aren't on the same subnet, then you will need to use the
+<option>-B</option> option to set the broadcast address to that of the PC's subnet.
+</para>
+
+<para>
+This test will probably fail if your subnet mask and broadcast address are
+not correct. (Refer to test 3 notes above).
+</para>
+
+</step>
+
+<step performance="required">
+
+
+<para>
+<indexterm><primary>smbclient</primary></indexterm>
+Run the command <command>smbclient //BIGSERVER/TMP</command>. You should 
+then be prompted for a password. You should use the password of the account
+with which you are logged into the UNIX box. If you want to test with
+another account, then add the <option>-U accountname</option> option to the end of
+the command line &smbmdash; for example, <command>smbclient //bigserver/tmp -Ujohndoe</command>.
+</para>
+
+<note><para>
+It is possible to specify the password along with the username as follows:
+<command>smbclient //bigserver/tmp -Ujohndoe%secret</command>.
+</para></note>
+
+<para>
+Once you enter the password, you should get the <prompt>smb></prompt> prompt. If you
+do not, then look at the error message. If it says <quote><errorname>invalid network
+name,</errorname></quote> then the service <smbconfsection name="tmp"/> is not correctly set up in your &smb.conf;.
+</para>
+
+<para>
+If it says <quote><errorname>bad password,</errorname></quote> then the likely causes are:
+</para>
+
+<orderedlist>
+<listitem>
+	<para>
+	You have shadow passwords (or some other password system) but didn't
+	compile in support for them in &smbd;.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	Your <smbconfoption name="valid users"/> configuration is incorrect.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	You have a mixed-case password and you haven't enabled the <smbconfoption name="password level"/> option at a high enough level.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	The <smbconfoption name="path"/> line in &smb.conf; is incorrect. Check it with &testparm;.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	You enabled password encryption but didn't map UNIX to Samba users. Run
+	<command>smbpasswd -a username</command>
+	</para>
+</listitem>
+</orderedlist>
+
+<para>
+<indexterm><primary>dir</primary></indexterm>
+<indexterm><primary>get</primary></indexterm>
+<indexterm><primary>put</primary></indexterm>
+<indexterm><primary>help command</primary></indexterm>
+Once connected, you should be able to use the commands <command>dir</command>, <command>get</command>,
+<command>put</command>, and so on. Type <command>help command</command> for instructions. You should
+especially check that the amount of free disk space shown is correct when you type <command>dir</command>.
+</para>
+
+</step>
+
+<step performance="required">
+
+<para>
+<indexterm><primary>net view</primary></indexterm>
+On the PC, type the command <command>net view \\BIGSERVER</command>. You will 
+need to do this from within a DOS prompt window. You should get back a 
+list of shares available on the server.
+</para>
+
+<para>
+<indexterm><primary>nmbd</primary></indexterm>
+If you get a message <literal>network name not found</literal> or similar error, then NetBIOS
+name resolution is not working. This is usually caused by a problem in <command>nmbd</command>.
+To overcome it, you could do one of the following (you only need to choose one of them):
+</para>
+
+<orderedlist>
+<listitem><para>
+	Fix the &nmbd; installation.
+</para></listitem>
+
+<listitem><para>
+	Add the IP address of BIGSERVER to the <command>wins server</command> box in the
+	advanced TCP/IP setup on the PC.
+</para></listitem>
+
+<listitem><para>
+	Enable Windows name resolution via DNS in the advanced section of the TCP/IP setup.
+</para></listitem>
+
+<listitem><para>
+	Add BIGSERVER to your lmhosts file on the PC.
+</para></listitem>
+</orderedlist>
+
+<para>
+If you get a message <quote><errorname>invalid network name</errorname></quote> or 
+<quote><errorname>bad password error,</errorname></quote> then apply the
+same fixes as for the <command>smbclient -L</command> test. In
+particular, make sure your <command>hosts allow</command> line is correct (see the man pages).
+</para>
+
+<para>
+Also, do not overlook that fact that when the workstation requests the
+connection to the Samba server, it will attempt to connect using the 
+name with which you logged onto your Windows machine. You need to make
+sure that an account exists on your Samba server with that exact same
+name and password.
+</para>
+
+<para>
+If you get a message <quote><errorname>specified computer is not receiving requests</errorname></quote> or similar error,
+it probably means that the host is not contactable via TCP services.
+Check to see if the host is running TCP wrappers, and if so, add an entry in
+the <filename>hosts.allow</filename> file for your client (or subnet, and so on.)
+</para>
+
+</step>
+
+<step performance="required">
+
+<para>
+Run the command <command>net use x: \\BIGSERVER\TMP</command>. You should 
+be prompted for a password, then you should get a <computeroutput>command completed 
+successfully</computeroutput> message. If not, then your PC software is incorrectly 
+installed or your &smb.conf; is incorrect. Make sure your <parameter>hosts allow</parameter>
+and other config lines in &smb.conf; are correct.
+</para>
+
+<para>
+It's also possible that the server can't work out what username to connect you as.
+To see if this is the problem, add the line
+<smbconfoption name="user">username</smbconfoption> to the
+<smbconfsection name="[tmp]"/> section of 
+&smb.conf; where <parameter>username</parameter> is the
+username corresponding to the password you typed. If you find this
+fixes things, you may need the username mapping option. 
+</para>
+
+<para>
+It might also be the case that your client only sends encrypted passwords 
+and you have <smbconfoption name="encrypt passwords">no</smbconfoption> in &smb.conf;.
+Change this setting to `yes' to fix this.
+</para>
+
+</step>
+
+<step performance="required">
+
+<para>
+Run the command <command>nmblookup -M <parameter>testgroup</parameter></command> where 
+<parameter>testgroup</parameter> is the name of the workgroup that your Samba server and 
+Windows PCs belong to. You should get back the IP address of the 
+master browser for that workgroup.
+</para>
+
+<para>
+If you do not, then the election process has failed. Wait a minute to
+see if it is just being slow, then try again. If it still fails after
+that, then look at the browsing options you have set in &smb.conf;. Make
+sure you have <smbconfoption name="preferred master">yes</smbconfoption> to ensure that 
+an election is held at startup.
+</para>
+
+</step>
+
+<step performance="required">
+
+<para>
+From file manager, try to browse the server. Your Samba server should
+appear in the browse list of your local workgroup (or the one you
+specified in &smb.conf;). You should be able to double-click on the name
+of the server and get a list of shares. If you get the error message <quote>invalid password,</quote>
+ you are probably running Windows NT and it
+is refusing to browse a server that has no encrypted password
+capability and is in user-level security mode. In this case, either set
+<smbconfoption name="security">server</smbconfoption> and 
+<smbconfoption name="password server">Windows_NT_Machine</smbconfoption> in your
+&smb.conf; file or make sure <smbconfoption name="encrypt passwords"/> is
+set to <quote>yes</quote>.
+</para>
+
+</step>
+</procedure>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml b/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
new file mode 100644
index 00000000000..c0f43ff1306
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
@@ -0,0 +1,1419 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="domain-member">
+
+<chapterinfo>
+	&author.jht;
+	&author.jeremy;
+	&author.jerry;
+	&author.tridge;
+	&author.jelmer;
+	<author>&person.gd;<contrib>LDAP updates</contrib></author>
+</chapterinfo>
+
+<title>Domain Membership</title>
+
+<para>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>machine trust account</primary></indexterm>
+<indexterm><primary>domain security</primary></indexterm>
+Domain membership is a subject of vital concern. Samba must be able to
+participate as a member server in a Microsoft domain security context, and
+Samba must be capable of providing domain machine member trust accounts;
+otherwise it would not be able to offer a viable option for many users.
+</para>
+
+<para>
+<indexterm><primary>domain membership</primary></indexterm>
+<indexterm><primary>misinformation</primary></indexterm>
+This chapter covers background information pertaining to domain membership,
+the Samba configuration for it, and MS Windows client procedures for joining a
+domain. Why is this necessary? Because both are areas in which there exists
+within the current MS Windows networking world, and particularly in the
+UNIX/Linux networking and administration world, a considerable level of
+misinformation, incorrect understanding, and lack of knowledge. Hopefully
+this chapter will fill the voids.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>domain security</primary></indexterm>
+<indexterm><primary>single sign-on</primary></indexterm>
+<indexterm><primary>SSO</primary></indexterm>
+MS Windows workstations and servers that want to participate in domain security need to
+be made domain members. Participating in domain security is often called 
+<emphasis>single sign-on</emphasis>, or <acronym>SSO</acronym> for short. This
+chapter describes the process that must be followed to make a workstation
+(or another server &smbmdash; be it an <application>MS Windows NT4/200x</application>
+server) or a Samba server a member of an MS Windows domain security context.
+</para>
+
+<para>
+<indexterm><primary>native member</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>domain control</primary></indexterm>
+<indexterm><primary>Server Type</primary><secondary>Domain Member</secondary></indexterm>
+Samba-3 can join an MS Windows NT4-style domain as a native member server, an 
+MS Windows Active Directory domain as a native member server, or a Samba domain
+control network. Domain membership has many advantages:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<indexterm><primary>SAM</primary></indexterm>
+	MS Windows workstation users get the benefit of SSO.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>access rights</primary></indexterm>
+	<indexterm><primary>file ownership</primary></indexterm>
+	<indexterm><primary>access controls</primary></indexterm>
+	<indexterm><primary>SAM</primary></indexterm>
+	Domain user access rights and file ownership/access controls can be set
+	from the single Domain Security Account Manager (SAM) database 
+	(works with domain member servers as well as with MS Windows workstations
+	that are domain members).
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>domain members</primary></indexterm>
+	<indexterm><primary>network logon</primary></indexterm>
+	Only <application>MS Windows NT4/200x/XP Professional</application>
+	workstations that are domain members can use network logon facilities.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>domain member</primary></indexterm>
+	<indexterm><primary>policy files</primary></indexterm>
+	<indexterm><primary>NTConfig.POL</primary></indexterm>
+	<indexterm><primary>desktop profiles</primary></indexterm>
+	Domain member workstations can be better controlled through the use of
+	policy files (<filename>NTConfig.POL</filename>) and desktop profiles.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>logon script</primary></indexterm>
+	<indexterm><primary>transparent access</primary></indexterm>
+	<indexterm><primary>application servers</primary></indexterm>
+	Through the use of logon scripts, users can be given transparent access to network
+	applications that run off application servers.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>user access management</primary></indexterm>
+	<indexterm><primary>SAM</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>ADS</primary></indexterm>
+	Network administrators gain better application and user access management
+	abilities because there is no need to maintain user accounts on any network
+	client or server other than the central domain database 
+	(either NT4/Samba SAM-style domain, NT4 domain that is backend-ed with an
+	LDAP directory, or via an Active Directory infrastructure).
+	</para></listitem>
+</itemizedlist>
+
+</sect1>
+
+<sect1 id="machine-trust-accounts">
+<title>MS Windows Workstation/Server Machine Trust Accounts</title>
+
+<para>
+<indexterm><primary>Machine Trust Accounts</primary></indexterm>
+<indexterm><primary>authenticate</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>rogue user</primary></indexterm>
+A Machine Trust Account is an account that is used to authenticate a client machine (rather than a user) to
+the domain controller server. In Windows terminology, this is known as a <quote>computer account.</quote> The
+purpose of the machine trust account is to prevent a rogue user and domain controller from colluding to gain
+access to a domain member workstation.
+</para>
+
+<para>
+<indexterm><primary>machine trust account</primary><secondary>password</secondary></indexterm>
+<indexterm><primary>shared secret</primary></indexterm>
+<indexterm><primary>unauthorized</primary></indexterm>
+<indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
+<indexterm><primary>Windows 9x/Me/XP Home</primary></indexterm>
+The password of a Machine Trust Account acts as the shared secret for secure communication with the domain
+controller. This is a security feature to prevent an unauthorized machine with the same NetBIOS name from
+joining the domain, participating in domain security operations, and gaining access to domain user/group
+accounts. Windows NT/200x/XP Professional clients use machine trust accounts, but Windows 9x/Me/XP Home
+clients do not. Hence, a Windows 9x/Me/XP Home client is never a true member of a domain because it does not
+possess a Machine Trust Account, and, thus, has no shared secret with the domain controller.
+</para>
+
+<para>
+<indexterm><primary>Windows Registry</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>Machine Trust Account</primary></indexterm>
+A Windows NT4 PDC stores each Machine Trust Account in the Windows Registry.
+The introduction of MS Windows 2000 saw the introduction of Active Directory,
+the new repository for Machine Trust Accounts. A Samba PDC, however, stores
+each Machine Trust Account in two parts,
+as follows:
+
+<itemizedlist>
+	<listitem><para>
+	<indexterm><primary>domain security account</primary></indexterm>
+	<indexterm><primary>account information</primary></indexterm>
+	<indexterm><primary>backend database</primary></indexterm>
+	A domain security account (stored in the <smbconfoption name="passdb backend"/>) that has been configured in
+	the &smb.conf; file. The precise nature of the account information that is stored depends on the type of
+	backend database that has been chosen.
+	</para>
+
+	<para>
+	<indexterm><primary>smbpasswd</primary></indexterm>
+	<indexterm><primary>UNIX login ID</primary></indexterm>
+	<indexterm><primary>UID</primary></indexterm>
+	<indexterm><primary>LanMan</primary></indexterm>
+	<indexterm><primary>NT-encrypted password</primary></indexterm>
+	<indexterm><primary>UNIX user identifier</primary><see>UID</see></indexterm>
+	The older format of this data is the <filename>smbpasswd</filename> database
+	that contains the UNIX login ID, the UNIX user identifier (UID), and the
+	LanMan and NT-encrypted passwords. There is also some other information in
+	this file that we do not need to concern ourselves with here.
+	</para>
+
+	<para>
+	<indexterm><primary>database</primary></indexterm>
+	<indexterm><primary>ldapsam</primary></indexterm>
+	<indexterm><primary>smbpasswd</primary></indexterm>
+	<indexterm><primary>account controls</primary></indexterm>
+	The two newer database types are called ldapsam and tdbsam. Both store considerably more data than the older
+	<filename>smbpasswd</filename> file did. The extra information enables new user account controls to be
+	implemented.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>UNIX account</primary></indexterm>
+	<indexterm><primary>/etc/passwd</primary></indexterm>
+	A corresponding UNIX account, typically stored in <filename>/etc/passwd</filename>. Work is in progress to
+	allow a simplified mode of operation that does not require UNIX user accounts, but this has not been a feature
+	of the early releases of Samba-3, and is not currently planned for release either.
+	</para></listitem>
+</itemizedlist>
+</para>
+
+<?latex \newpage ?>
+<para>
+<indexterm><primary>Machine Trust Accounts</primary><secondary>creating</secondary></indexterm>
+There are three ways to create Machine Trust Accounts:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<indexterm><primary>manual UNIX account creation</primary></indexterm>
+	Manual creation from the UNIX/Linux command line. Here, both the Samba and
+	corresponding UNIX account are created by hand.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>Server Manager</primary></indexterm>
+	<indexterm><primary>Nexus toolkit</primary></indexterm>
+	Using the MS Windows NT4 Server Manager, either from an NT4 domain member
+	server or using the Nexus toolkit available from the Microsoft Web site.
+	This tool can be run from any MS Windows machine as long as the user is
+	logged on as the administrator account.
+	</para></listitem>
+	
+	<listitem><para>
+	<indexterm><primary>Machine Trust Account</primary></indexterm>
+	<indexterm><primary>joined client</primary></indexterm>
+	<quote>On-the-fly</quote> creation. The Samba Machine Trust Account is automatically
+	created by Samba at the time the client is joined to the domain.
+	(For security, this is the recommended method.) The corresponding UNIX
+	account may be created automatically or manually. 
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>enforcing</primary></indexterm>
+<indexterm><primary>machine trust account</primary><secondary>creation</secondary></indexterm>
+Neither MS Windows NT4/200x/XP Professional, nor Samba, provide any method for enforcing the method of machine
+trust account creation. This is a matter of the administrator's choice.
+</para>
+
+<sect2>
+<title>Manual Creation of Machine Trust Accounts</title>
+
+<para>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+<indexterm><primary>useradd</primary></indexterm>
+<indexterm><primary>vipw</primary></indexterm>
+The first step in manually creating a Machine Trust Account is to manually
+create the corresponding UNIX account in <filename>/etc/passwd</filename>. 
+This can be done using <command>vipw</command> or another <quote>adduser</quote> command
+that is normally used to create new UNIX accounts. The following is an example for
+a Linux-based Samba server:
+<screen>
+&rootprompt;<userinput>/usr/sbin/useradd -g machines -d /var/lib/nobody \
+   -c <replaceable>"machine nickname"</replaceable> \
+   -s /bin/false <replaceable>machine_name</replaceable>$ </userinput>
+
+&rootprompt;<userinput>passwd -l <replaceable>machine_name</replaceable>$</userinput>
+</screen>
+</para>
+
+<para>
+<indexterm><primary>primary group</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>machine accounts</primary></indexterm>
+In the example above there is an existing system group <quote>machines</quote> which is used
+as the primary group for all machine accounts. In the following examples the <quote>machines</quote> group
+numeric GID is 100.
+</para>
+
+<para>
+<indexterm><primary>chpass</primary></indexterm>
+<indexterm><primary>BSD</primary></indexterm>
+On *BSD systems, this can be done using the <command>chpass</command> utility:
+<screen>
+&rootprompt;<userinput>chpass -a \
+'<replaceable>machine_name</replaceable>$:*:101:100::0:0:Windows <replaceable>machine_name</replaceable>:/dev/null:/sbin/nologin'</userinput>
+</screen>
+</para>
+
+<para>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>$</primary></indexterm>
+<indexterm><primary>null shell</primary></indexterm>
+<indexterm><primary>home directory</primary></indexterm>
+The <filename>/etc/passwd</filename> entry will list the machine name 
+with a <quote>$</quote> appended, and will not have a password, will have a null shell and no 
+home directory. For example, a machine named <quote>doppy</quote> would have an 
+<filename>/etc/passwd</filename> entry like this:
+<programlisting>
+doppy$:x:505:100:<replaceable>machine_nickname</replaceable>:/dev/null:/bin/false
+</programlisting>
+</para>
+
+<para>
+<indexterm><primary>machine_nickname</primary></indexterm>
+<indexterm><primary>machine_name</primary></indexterm>
+<indexterm><primary>Machine Trust Account</primary></indexterm>
+in which <replaceable>machine_nickname</replaceable> can be any
+descriptive name for the client, such as BasementComputer.
+<replaceable>machine_name</replaceable> absolutely must be the NetBIOS
+name of the client to be joined to the domain. The <quote>$</quote> must be
+appended to the NetBIOS name of the client or Samba will not recognize
+this as a Machine Trust Account.
+</para>
+
+<para>
+<indexterm><primary>UNIX account</primary></indexterm>
+<indexterm><primary>Samba account</primary></indexterm>
+<indexterm><primary>Machine Trust Account</primary><secondary>password</secondary></indexterm>
+Now that the corresponding UNIX account has been created, the next step is to create 
+the Samba account for the client containing the well-known initial 
+Machine Trust Account password. This can be done using the 
+<command>smbpasswd</command> command 
+as shown here:
+<screen>
+&rootprompt;<userinput>smbpasswd -a -m <replaceable>machine_name</replaceable></userinput>
+</screen>
+</para>
+
+<para>
+<indexterm><primary>machine_name</primary></indexterm>
+<indexterm><primary>NetBIOS name</primary></indexterm>
+<indexterm><primary>RID</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+where <replaceable>machine_name</replaceable> is the machine's NetBIOS
+name. The RID of the new machine account is generated from the UID of 
+the corresponding UNIX account.
+</para>
+
+<warning>
+<title>Join the client to the domain immediately</title>
+
+<para>
+<indexterm><primary>Machine Trust Account</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>Server Manager</primary></indexterm>
+<indexterm><primary>changes password</primary></indexterm>
+<indexterm><primary>NetBIOS name</primary></indexterm>
+Manually creating a Machine Trust Account using this method is the 
+equivalent of creating a Machine Trust Account on a Windows NT PDC using 
+<indexterm><primary>Server Manager</primary></indexterm>
+the <application>Server Manager</application>. From the time at which the 
+account is created to the time the client joins the domain and 
+changes the password, your domain is vulnerable to an intruder joining 
+your domain using a machine with the same NetBIOS name. A PDC inherently 
+trusts members of the domain and will serve out a large degree of user 
+information to such clients. You have been warned!
+</para>
+</warning>
+</sect2>
+
+<sect2>
+<title>Managing Domain Machine Accounts using NT4 Server Manager</title>
+
+<para>
+<indexterm><primary>machine trust accounts</primary></indexterm>
+<indexterm><primary>automatic account creation</primary></indexterm>
+<indexterm><primary>Server Manager</primary></indexterm>
+A working <smbconfoption name="add machine script"/> is essential
+for machine trust accounts to be automatically created. This applies no matter whether
+you use automatic account creation or the NT4 Domain Server Manager.
+</para>
+
+<para>
+<indexterm><primary>SRVTOOLS.EXE</primary></indexterm>
+<indexterm><primary>SrvMgr.exe</primary></indexterm>
+<indexterm><primary>UsrMgr.exe</primary></indexterm>
+<indexterm><primary>domain management tools</primary></indexterm>
+If the machine from which you are trying to manage the domain is an 
+<application>MS Windows NT4 workstation or MS Windows 200x/XP Professional</application>,
+the tool of choice is the package called <command>SRVTOOLS.EXE</command>. 
+When executed in the target directory it will unpack <command>SrvMgr.exe</command>
+and <command>UsrMgr.exe</command> (both are domain management tools for MS Windows NT4 workstation).
+</para>
+
+<para>
+<indexterm><primary>Nexus.exe</primary></indexterm>
+<indexterm><primary>Microsoft Windows 9x/Me</primary></indexterm>
+If your workstation is a <application>Microsoft Windows 9x/Me</application> family product,
+ you should download the <command>Nexus.exe</command> package from the Microsoft Web site.
+When executed from the target directory, it will unpack the same tools but for use on 
+this platform.
+</para>
+
+<para>
+Further information about these tools may be obtained from Knowledge Base articles
+<ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673">173673</ulink>, and
+<ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540">172540</ulink>
+</para>
+
+<para>
+<indexterm><primary>srvmgr.exe</primary></indexterm>
+<indexterm><primary>Server Manager for Domains</primary></indexterm>
+Launch the <command>srvmgr.exe</command> (Server Manager for Domains) and follow these steps:
+</para>
+
+<procedure>
+<title>Server Manager Account Machine Account Management</title>
+	<step><para>
+	From the menu select <guimenu>Computer</guimenu>.
+	</para></step>
+
+	<step><para>
+	Click <guimenuitem>Select Domain</guimenuitem>.
+	</para></step>
+
+	<step><para>
+	Click the name of the domain you wish to administer in the
+	<guilabel>Select Domain</guilabel> panel and then click 
+	<guibutton>OK</guibutton>.
+	</para></step>
+
+	<step><para>
+	Again from the menu select <guimenu>Computer</guimenu>.
+	</para></step>
+
+	<step><para>
+	Select <guimenuitem>Add to Domain</guimenuitem>.
+	</para></step>
+
+	<step><para>
+	In the dialog box, click the radio button to 
+	<guilabel>Add NT Workstation of Server</guilabel>, then
+	enter the machine name in the field provided, and click the 
+	<guibutton>Add</guibutton> button.
+	</para></step>
+</procedure>
+
+</sect2>
+
+<sect2>
+<title>On-the-Fly Creation of Machine Trust Accounts</title>
+
+<para>
+<indexterm><primary>Machine Trust Account</primary><secondary>creation</secondary></indexterm>
+The third (and recommended) way of creating Machine Trust Accounts is simply to allow the Samba server to
+create them as needed when the client is joined to the domain.
+</para>
+
+<para>
+<indexterm><primary>Machine Trust Account</primary><secondary>UNIX account</secondary></indexterm>
+<indexterm><primary>UNIX account</primary></indexterm>
+<indexterm><primary>add machine script</primary></indexterm>
+Since each Samba Machine Trust Account requires a corresponding UNIX account, a method
+for automatically creating the UNIX account is usually supplied; this requires configuration of the
+add machine script option in &smb.conf;. This method is not required; however, corresponding UNIX
+accounts may also be created manually.
+</para>
+
+
+<para>
+<indexterm><primary>useradd</primary></indexterm>
+<indexterm><primary>Red Hat Linux</primary></indexterm>
+Here is an example for a Red Hat Linux system:
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="add machine script">/usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u</smbconfoption>
+</smbconfblock>
+</para>
+
+</sect2>
+
+<sect2><title>Making an MS Windows Workstation or Server a Domain Member</title>
+
+<para>
+The procedure for making an MS Windows workstation or server a member of the domain varies
+with the version of Windows.
+</para>
+
+<sect3>
+	<title>Windows 200x/XP Professional Client</title>
+
+	<para>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>machine trust account</primary><secondary>create privilege</secondary></indexterm>
+<indexterm><primary>privileges</primary></indexterm>
+<indexterm><primary>root</primary></indexterm>
+	When the user elects to make the client a domain member, Windows 200x prompts for
+	an account and password that has privileges to create  machine accounts in the domain.
+	A Samba administrator account (i.e., a Samba account that has <constant>root</constant> privileges on the
+	Samba server) must be entered here; the operation will fail if an ordinary user
+	account is given. 
+	</para>
+
+	<para>
+<indexterm><primary>administrator account</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+	For security reasons, the password for this administrator account should be set
+	to a password that is other than that used for the root user in <filename>/etc/passwd</filename>.
+	</para>
+
+	<para>
+<indexterm><primary>account</primary></indexterm>
+<indexterm><primary>create domain member</primary></indexterm>
+<indexterm><primary>root</primary></indexterm>
+<indexterm><primary>map</primary></indexterm>
+	The name of the account that is used to create domain member machine trust accounts can be
+	anything the network administrator may choose. If it is other than <constant>root</constant>,
+	then this is easily mapped to <constant>root</constant> in the file named in the &smb.conf; parameter
+	<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>.
+	</para>
+
+	<para>
+<indexterm><primary>administrator account</primary></indexterm>
+<indexterm><primary>encryption key</primary></indexterm>
+<indexterm><primary>machine trust account</primary></indexterm>
+	The session key of the Samba administrator account acts as an encryption key for setting the password of the machine trust
+	account. The Machine Trust Account will be created on-the-fly, or updated if it already exists.
+	</para>
+</sect3>
+
+<sect3>
+	<title>Windows NT4 Client</title>
+
+	<para>
+<indexterm><primary>Machine Trust Account</primary></indexterm>
+<indexterm><primary>Create a Computer Account</primary></indexterm>
+<indexterm><primary>join the machine</primary></indexterm>
+	If the Machine Trust Account was created manually, on the
+	Identification Changes menu enter the domain name, but do not
+	check the box <guilabel>Create a Computer Account in the Domain</guilabel>.
+	In this case, the existing Machine Trust Account is used to join the machine 
+	to the domain.
+	</para>
+
+	<para>
+<indexterm><primary>Machine Trust Account</primary></indexterm>
+<indexterm><primary>on the fly</primary></indexterm>
+<indexterm><primary>Computer Account</primary></indexterm>
+<indexterm><primary>administrator account</primary></indexterm>
+	If the Machine Trust Account is to be created on the fly, on the Identification Changes menu enter the domain
+	name and check the box <guilabel>Create a Computer Account in the Domain</guilabel>. In this case, joining
+	the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrator account when
+	prompted).
+	</para>
+</sect3>
+
+<sect3>
+	<title>Samba Client</title>
+
+	<para>
+<indexterm><primary></primary></indexterm>
+	Joining a Samba client to a domain is documented in <link linkend="domain-member-server">the next section</link>.
+	</para>
+</sect3>
+
+</sect2>
+</sect1>
+
+<sect1 id="domain-member-server">
+<title>Domain Member Server</title>
+
+<para>
+<indexterm><primary>domain security</primary></indexterm>
+<indexterm><primary>security context</primary></indexterm>
+<indexterm><primary>authentication regime</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+This mode of server operation involves the Samba machine being made a member
+of a domain security context. This means by definition that all user
+authentication will be done from a centrally defined authentication regime. 
+The authentication regime may come from an NT3/4-style (old domain technology)
+server, or it may be provided from an Active Directory server (ADS) running on
+MS Windows 2000 or later.
+</para>
+
+<para>
+<emphasis>
+<indexterm><primary>authentication</primary><secondary>backend</secondary></indexterm>
+<indexterm><primary>distributed directory</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>iPlanet</primary></indexterm>
+<indexterm><primary>Sun</primary></indexterm>
+<indexterm><primary>Novell</primary></indexterm>
+<indexterm><primary>e-Directory</primary></indexterm>
+Of course it should be clear that the authentication backend itself could be
+from any distributed directory architecture server that is supported by Samba.
+This can be LDAP (from OpenLDAP), or Sun's iPlanet, or Novell e-Directory
+Server, and so on.
+</emphasis>
+</para>
+
+<note><para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>identity management</primary></indexterm>
+<indexterm><primary>machine authentication</primary></indexterm>
+When Samba is configured to use an LDAP or other identity management and/or
+directory service, it is Samba that continues to perform user and machine
+authentication. It should be noted that the LDAP server does not perform
+authentication handling in place of what Samba is designed to do.
+</para></note>
+
+<para>
+<indexterm><primary>create a domain machine account</primary></indexterm>
+<indexterm><primary>domain member server</primary></indexterm>
+<indexterm><primary>join the domain</primary></indexterm>
+Please refer to <link linkend="samba-pdc">Domain Control</link>, for more information regarding
+how to create a domain machine account for a domain member server as well as for
+information on how to enable the Samba domain member machine to join the domain
+and be fully trusted by it.
+</para>
+
+<sect2>
+<title>Joining an NT4-type Domain with Samba-3</title>
+
+<para><link linkend="assumptions">Assumptions</link> lists names that are used in the remainder of this chapter.</para>
+
+<table frame="all" id="assumptions"><title>Assumptions</title>
+	<tgroup cols="2">
+		<colspec align="right"/>
+		<colspec align="left"/>
+	<tbody>
+			<row>
+				<entry>Samba DMS NetBIOS name:</entry><entry>SERV1</entry>
+			</row>
+			<row>
+				<entry>Windows 200x/NT domain name:</entry><entry>&example.workgroup;</entry>
+			</row>
+			<row>
+				<entry>Domain's PDC NetBIOS name:</entry><entry>DOMPDC</entry>
+			</row>
+			<row>
+				<entry>Domain's BDC NetBIOS names:</entry><entry>DOMBDC1 and DOMBDC2</entry>
+			</row>
+	</tbody>
+	</tgroup>
+</table>
+
+<para>
+<indexterm><primary></primary></indexterm>
+First, you must edit your &smb.conf; file to tell Samba it should now use domain security.
+</para>
+
+<para>
+<indexterm><primary>security = user</primary></indexterm>
+<indexterm><primary>standalone server</primary></indexterm>
+<indexterm><primary>domain member server</primary></indexterm>
+<indexterm><primary>domain security</primary></indexterm>
+Change (or add) your <smbconfoption name="security"/> line in the [global] section 
+of your &smb.conf; to read:
+<smbconfblock>
+<smbconfoption name="security">domain</smbconfoption>
+</smbconfblock>
+Note that if the parameter <parameter>security = user</parameter> is used, this machine would function as a
+standalone server and not as a domain member server. Domain security mode causes Samba to work within the
+domain security context.
+</para>
+
+<para>
+Next change the <smbconfoption name="workgroup"/> line in the <smbconfsection name="[global]"/>
+section to read: 
+<smbconfblock>
+<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
+</smbconfblock>
+This is the name of the domain we are joining.
+</para>
+
+<para>
+<indexterm><primary>authenticate</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+You must also have the parameter <smbconfoption name="encrypt passwords"/>
+set to <constant>yes</constant> in order for your users to authenticate to the NT PDC.
+This is the default setting if this parameter is not specified. There is no need to specify this
+parameter, but if it is specified in the &smb.conf; file, it must be set to <constant>Yes</constant>.
+</para>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>authenticate users</primary></indexterm>
+<indexterm><primary>domain controllers</primary></indexterm>
+Finally, add (or modify) a <smbconfoption name="password server"/> line in the [global]
+section to read: 
+<smbconfblock>
+<smbconfoption name="password server">DOMPDC DOMBDC1 DOMBDC2</smbconfoption>
+</smbconfblock>
+These are the PDC and BDCs Samba 
+will attempt to contact in order to authenticate users. Samba will 
+try to contact each of these servers in order, so you may want to 
+rearrange this list in order to spread out the authentication load 
+among Domain Controllers.
+</para>
+
+<para>
+<indexterm><primary>list of domain controllers</primary></indexterm>
+<indexterm><primary>mechanism</primary></indexterm>
+<indexterm><primary>broadcast-based name resolution</primary></indexterm>
+<indexterm><primary>DNS name resolution</primary></indexterm>
+Alternatively, if you want smbd to determine automatically the list of domain controllers to use for
+authentication, you may set this line to be:
+<smbconfblock>
+<smbconfoption name="password server">*</smbconfoption>
+</smbconfblock>
+<indexterm><primary>WINS</primary></indexterm>
+This method allows Samba to use exactly the same mechanism that NT does. The 
+method either uses broadcast-based name resolution, performs a WINS database
+lookup in order to find a domain controller against which to authenticate,
+or locates the domain controller using DNS name resolution.
+</para>
+
+<para>
+To join the domain, run this command:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+<screen>
+&rootprompt;<userinput>net rpc join -S DOMPDC -U<replaceable>Administrator%password</replaceable></userinput>
+</screen>
+</para>
+
+<para>
+<indexterm><primary>NetBIOS name</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>WINS lookup</primary></indexterm>
+<indexterm><primary>NetBIOS broadcast</primary></indexterm>
+If the <option>-S DOMPDC</option> argument is not given, the domain name will be obtained from &smb.conf; and
+the NetBIOS name of the PDC will be obtained either using a WINS lookup or via NetBIOS broadcast based name
+look up.
+</para>
+
+<para>
+<indexterm><primary>joining the domain</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>Administrator%password</primary></indexterm>
+<indexterm><primary>Joined domain</primary></indexterm>
+The machine is joining the domain DOM, and the PDC for that domain (the only machine
+that has write access to the domain SAM database) is DOMPDC; therefore, use the <option>-S</option>
+option. The <replaceable>Administrator%password</replaceable> is the login name and
+password for an account that has the necessary privilege to add machines to the
+domain. If this is successful, you will see the following message in your terminal window.
+Where the older NT4-style domain architecture is used:
+<screen>
+<computeroutput>Joined domain DOM.</computeroutput>
+</screen>
+</para>
+
+<para>
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>join the ADS domain</primary></indexterm>
+Where Active Directory is used, the command used to join the ADS domain is:
+<screen>
+&rootprompt; net ads join -U<replaceable>Administrator%password</replaceable>
+</screen>
+And the following output is indicative of a successful outcome:
+<screen>
+<computeroutput>Joined SERV1 to realm MYREALM.</computeroutput>
+</screen>
+</para>
+
+<para>
+Refer to the <command>net</command> man page and to <link linkend="NetCommand">the chapter on remote
+administration</link> for further information.
+</para>
+
+<para>
+<indexterm><primary>join the domain</primary></indexterm>
+<indexterm><primary>create machine trust account</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+This process joins the server to the domain without separately having to create the machine
+trust account on the PDC beforehand.
+</para>
+
+<para>
+<indexterm><primary>machine account password</primary><secondary>change protocol</secondary></indexterm>
+<indexterm><primary>random machine account password</primary></indexterm>
+<indexterm><primary>/usr/local/samba/private/secrets.tdb</primary></indexterm>
+<indexterm><primary>/etc/samba/secrets.tdb</primary></indexterm>
+This command goes through the machine account password change protocol, then writes the new (random) machine
+account password for this Samba server into a file in the same directory in which a smbpasswd file would be
+normally stored. The trust account information that is needed by the DMS is written into the file
+<filename>/usr/local/samba/private/secrets.tdb</filename> or <filename>/etc/samba/secrets.tdb</filename>.
+</para>
+
+<para>
+<indexterm><primary>domain-level security</primary></indexterm>
+<indexterm><primary>shadow password file</primary></indexterm>
+This file is created and owned by root and is not readable by any other user. It is
+the key to the domain-level security for your system and should be treated as carefully 
+as a shadow password file.
+</para>
+
+<para>
+<indexterm><primary>Samba daemons</primary></indexterm>
+<indexterm><primary>distribution</primary></indexterm>
+<indexterm><primary>/etc/init.d/samba</primary></indexterm>
+Finally, restart your Samba daemons and get ready for clients to begin using domain
+security. The way you can restart your Samba daemons depends on your distribution,
+but in most cases the following will suffice:
+<screen>
+&rootprompt;/etc/init.d/samba restart
+</screen>
+</para>
+
+</sect2>
+
+<sect2>
+<title>Why Is This Better Than <parameter>security = server</parameter>?</title>
+
+<para>
+<indexterm><primary>domain security</primary></indexterm>
+<indexterm><primary>UNIX users</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+Currently, domain security in Samba does not free you from having to create local UNIX users to represent the
+users attaching to your server. This means that if domain user <constant>DOM\fred</constant> attaches to your
+domain security Samba server, there needs to be a local UNIX user fred to represent that user in the UNIX file
+system. This is similar to the older Samba security mode <smbconfoption
+name="security">server</smbconfoption>, where Samba would pass through the authentication request to a Windows
+NT server in the same way as a Windows 95 or Windows 98 server would.
+</para>
+
+<para>
+<indexterm><primary>winbind</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+Please refer to <link linkend="winbind">Winbind: Use of Domain Accounts</link>, for information on a system
+to automatically assign UNIX UIDs and GIDs to Windows NT domain users and groups.
+</para>
+
+<para>
+<indexterm><primary>domain-level</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+<indexterm><primary>RPC</primary></indexterm>
+The advantage of domain-level security is that the authentication in domain-level security is passed down the
+authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now
+participate in domain trust relationships in exactly the same way NT servers do (i.e., you can add Samba
+servers into a resource domain and have the authentication passed on from a resource domain PDC to an account
+domain PDC).
+</para>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>connection resources</primary></indexterm>
+In addition, with <smbconfoption name="security">server</smbconfoption>, every Samba daemon on a server has to
+keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the
+connection resources on a Microsoft NT server and cause it to run out of available connections. With
+<smbconfoption name="security">domain</smbconfoption>, however, the Samba daemons connect to the PDC or BDC
+only for as long as is necessary to authenticate the user and then drop the connection, thus conserving PDC
+connection resources.
+</para>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>authentication reply</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>NT groups</primary></indexterm>
+Finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the
+authentication reply, the Samba server gets the user identification information such as the user SID, the list
+of NT groups the user belongs to, and so on.
+</para>
+
+<note>
+<para>
+Much of the text of this document was first published in the Web magazine 
+<ulink url="http://www.linuxworld.com"><emphasis>LinuxWorld</emphasis></ulink> as the article <ulink
+url="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html"/>
+<emphasis>Doing the NIS/NT Samba</emphasis>.
+</para>
+</note>
+
+</sect2>
+</sect1>
+
+<sect1 id="ads-member">
+<title>Samba ADS Domain Membership</title>
+
+<para>
+<indexterm significance="preferred"><primary>Active Directory</primary></indexterm>
+<indexterm significance="preferred"><primary>ADS</primary><see>Active Directory</see></indexterm>
+<indexterm><primary>KDC</primary></indexterm>
+<indexterm><primary>Kerberos</primary></indexterm>
+This is a rough guide to setting up Samba-3 with Kerberos authentication against a
+Windows 200x KDC. A familiarity with Kerberos is assumed.
+</para> 
+
+<sect2>
+<title>Configure &smb.conf;</title>
+
+<para>
+You must use at least the following three options in &smb.conf;:
+</para>
+
+<smbconfblock>
+<smbconfoption name="realm">your.kerberos.REALM</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+<smbconfcomment>The following parameter need only be specified if present.</smbconfcomment>
+<smbconfcomment>The default setting if not present is Yes.</smbconfcomment>
+<smbconfoption name="encrypt passwords">yes</smbconfoption>
+</smbconfblock>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>realm</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>ADS DC</primary></indexterm>
+<indexterm><primary>password server</primary></indexterm>
+In case samba cannot correctly identify the appropriate ADS server using the realm name, use the 
+<smbconfoption name="password server"/> option in &smb.conf;:
+<smbconfblock>
+<smbconfoption name="password server">your.kerberos.server</smbconfoption>
+</smbconfblock>
+The most common reason for which Samba may not be able to locate the ADS domain controller is a consequence of
+sites maintaining some DNS servers on UNIX systems without regard for the DNS requirements of the ADS
+infrastructure. There is no harm in specifying a preferred ADS domain controller using the <parameter>password
+server</parameter>.
+</para>
+
+<note><para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>authenticated</primary></indexterm>
+You do <emphasis>not</emphasis> need an smbpasswd file, and older clients will be authenticated as 
+if <smbconfoption name="security">domain</smbconfoption>, although it will not do any harm and 
+allows you to have local users not in the domain.
+</para></note>
+
+</sect2>
+  
+<sect2>
+<title>Configure <filename>/etc/krb5.conf</filename></title>
+
+<para>
+<indexterm><primary>/etc/krb5.conf</primary></indexterm>
+<indexterm><primary>Kerberos</primary><secondary>/etc/krb5.conf</secondary></indexterm>
+<indexterm><primary>MIT</primary></indexterm>
+<indexterm><primary>Heimdal</primary></indexterm>
+With both MIT and Heimdal Kerberos, it is unnecessary to configure the <filename>/etc/krb5.conf</filename>,
+and it may be detrimental.
+</para>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>SRV records</primary></indexterm>
+<indexterm><primary>DNS zon</primary></indexterm>
+<indexterm><primary>KDC</primary></indexterm>
+<indexterm><primary>_kerberos.REALM.NAME</primary></indexterm>
+Microsoft ADS automatically create SRV records in the DNS zone 
+<parameter>_kerberos._tcp.REALM.NAME</parameter> for each KDC in the realm. This is part
+of the installation and configuration process used to create an Active Directory domain.
+A KDC is a Kerberos Key Distribution Center and forms an integral part of the Microsoft
+active directory infrastructure.
+</para>
+
+<para>
+<indexterm><primary>kinit</primary></indexterm>
+<indexterm><primary>DES-CBC-MD5</primary></indexterm>
+<indexterm><primary>DES-CBC-CRC</primary></indexterm>
+<indexterm><primary>encryption types</primary></indexterm>
+<indexterm><primary>kerberos</primary></indexterm>
+<indexterm><primary>Windows 2000</primary></indexterm>
+UNIX systems can use kinit and the DES-CBC-MD5 or DES-CBC-CRC encryption types to authenticate to the Windows
+2000 KDC. For further information regarding Windows 2000 ADS kerberos interoperability please refer to the
+Microsoft Windows 2000 Kerberos <ulink
+url="http://www.microsoft.com/windows2000/techinfo/planning/security/kerbsteps.asp">Interoperability</ulink>
+guide. Another very useful document that may be referred to for general information regarding Kerberos
+interoperability is <ulink url="http://www.ietf.org/rfc/rfc1510.txt?number=1510">RFC1510</ulink>. This RFC
+explains much of the magic behind the operation of Kerberos.
+</para>
+
+<para>
+<indexterm><primary>MIT</primary></indexterm>
+<indexterm><primary>KRB5</primary></indexterm>
+<indexterm><primary>SRV records</primary></indexterm>
+<indexterm><primary>krb5.conf</primary></indexterm>
+<indexterm><primary>DNS lookup</primary></indexterm>
+<indexterm><primary>libraries</primary></indexterm>
+MIT's, as well as Heimdal's, recent KRB5 libraries default to checking for SRV records, so they will 
+automatically find the KDCs. In addition, <filename>krb5.conf</filename> only allows specifying 
+a single KDC, even there if there may be more than one. Using the DNS lookup allows the KRB5 
+libraries to use whichever KDCs are available.
+</para>
+
+<para>
+<indexterm><primary>krb5.conf</primary></indexterm>
+When manually configuring <filename>krb5.conf</filename>, the minimal configuration is:
+<screen>
+[libdefaults]
+	default_realm = YOUR.KERBEROS.REALM
+
+[realms]
+	YOUR.KERBEROS.REALM = {
+	kdc = your.kerberos.server
+	}
+
+[domain_realms]
+	.kerberos.server = YOUR.KERBEROS.REALM
+</screen>
+</para>
+
+<para>
+<indexterm><primary>Heimdal</primary></indexterm>
+When using Heimdal versions before 0.6, use the following configuration settings:
+<screen>
+[libdefaults]
+	default_realm      = YOUR.KERBEROS.REALM
+	default_etypes     = des-cbc-crc des-cbc-md5
+	default_etypes_des = des-cbc-crc des-cbc-md5
+
+[realms]
+        YOUR.KERBEROS.REALM = {
+        kdc = your.kerberos.server
+	}
+
+[domain_realms]
+        .kerberos.server = YOUR.KERBEROS.REALM
+</screen>
+</para>
+
+<para>
+<indexterm><primary>KDC</primary></indexterm>
+<indexterm><primary>kinit</primary></indexterm>
+Test your config by doing a <userinput>kinit
+<replaceable>USERNAME</replaceable>@<replaceable>REALM</replaceable></userinput> and
+making sure that your password is accepted by the Win2000 KDC.
+</para>
+
+<para>
+<indexterm><primary>Heimdal</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>KDC</primary></indexterm>
+<indexterm><primary>Windows 2003</primary></indexterm>
+With Heimdal versions earlier than 0.6.x you can use only newly created accounts
+in ADS or accounts that have had the password changed once after migration, or
+in case of <constant>Administrator</constant> after installation. At the
+moment, a Windows 2003 KDC can only be used with Heimdal releases later than 0.6
+(and no default etypes in krb5.conf). Unfortunately, this whole area is still
+in a state of flux.
+</para>
+
+<note><para>
+<indexterm><primary>realm</primary></indexterm>
+<indexterm><primary>uppercase</primary></indexterm>
+<indexterm><primary>KDC</primary></indexterm>
+The realm must be in uppercase or you will get a <quote><errorname>Cannot find KDC for
+requested realm while getting initial credentials</errorname></quote> error (Kerberos
+is case-sensitive!).
+</para></note>
+
+<note><para>
+<indexterm><primary>synchronize</primary></indexterm>
+<indexterm><primary>credentials</primary></indexterm>
+<indexterm><primary>time difference</primary></indexterm>
+<indexterm><primary>clock skew</primary></indexterm>
+Time between the two servers must be synchronized. You will get a <quote><errorname>kinit(v5): Clock skew too
+great while getting initial credentials</errorname></quote> if the time difference (clock skew) is more than five minutes.
+</para></note>
+
+<para>
+<indexterm><primary>clock skew</primary></indexterm>
+<indexterm><primary>Kerberos</primary></indexterm>
+Clock skew limits are configurable in the Kerberos protocols. The default setting is five minutes.
+</para>
+
+<para>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>KDC</primary></indexterm>
+<indexterm><primary>hostname</primary></indexterm>
+<indexterm><primary>realm</primary></indexterm>
+You also must ensure that you can do a reverse DNS lookup on the IP address of your KDC. Also, the name that
+this reverse lookup maps to must either be the NetBIOS name of the KDC (i.e., the hostname with no domain
+attached) or it can be the NetBIOS name followed by the realm.
+</para>
+
+<para>
+<indexterm><primary>/etc/hosts</primary></indexterm>
+<indexterm><primary>KDC</primary></indexterm>
+<indexterm><primary>realm</primary></indexterm>
+The easiest way to ensure you get this right is to add a <filename>/etc/hosts</filename> entry mapping the IP
+address of your KDC to its NetBIOS name. If you do not get this correct, then you will get a <errorname>local
+error</errorname> when you try to join the realm.
+</para>
+
+<para>
+<indexterm><primary>Kerberos</primary></indexterm>
+<indexterm><primary>Create the Computer Account</primary></indexterm>
+<indexterm><primary>Testing Server Setup</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+If all you want is Kerberos support in &smbclient;, then you can skip directly to <link
+linkend="ads-test-smbclient">Testing with &smbclient;</link> now.  <link
+linkend="ads-create-machine-account">Create the Computer Account</link> and <link
+linkend="ads-test-server">Testing Server Setup</link> are needed only if you want Kerberos support for &smbd;
+and &winbindd;.
+</para>
+
+</sect2>
+
+<sect2 id="ads-create-machine-account">
+<title>Create the Computer Account</title>
+
+<para>
+<indexterm><primary>write permission</primary></indexterm>
+<indexterm><primary>Samba private directory</primary></indexterm>
+<indexterm><primary>Administrator account</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+As a user who has write permission on the Samba private directory (usually root), run:
+<screen>
+&rootprompt; <userinput>net ads join -U Administrator%password</userinput>
+</screen>
+The Administrator account can be any account that has been designated in the ADS domain security settings with
+permission to add machines to the ADS domain. It is, of course, a good idea to use an account other than Administrator.
+On the UNIX/Linux system, this command must be executed by an account that has UID=0 (root).
+</para>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>machine trust account</primary></indexterm>
+<indexterm><primary>organizational unit</primary></indexterm>
+<indexterm><primary>ADS manager</primary></indexterm>
+<indexterm><primary>kinit</primary></indexterm>
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
+When making a Windows client a member of an ADS domain within a complex organization, you
+may want to create the machine trust account within a particular organizational unit. Samba-3 permits
+this to be done using the following syntax:
+<screen>
+&rootprompt; <userinput>kinit Administrator@your.kerberos.REALM</userinput>
+&rootprompt; <userinput>net ads join createcomputer="organizational_unit"</userinput>
+</screen>
+Your ADS manager will be able to advise what should be specified for the "organizational_unit" parameter.
+</para>
+
+<para>
+<indexterm><primary>organizational directory</primary></indexterm>
+<indexterm><primary>machine trust account</primary></indexterm>
+<indexterm><primary>container</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+For example, you may want to create the machine trust account in a container called <quote>Servers</quote>
+under the organizational directory <quote>Computers/BusinessUnit/Department,</quote> like this:
+<screen>
+&rootprompt; <userinput>net ads join "Computers/BusinessUnit/Department/Servers"</userinput>
+</screen>
+This command will place the Samba server machine trust account in the container
+<literal>Computers/BusinessUnit/Department/Servers</literal>. The container should exist in the ADS directory
+before executing this command.  Please note that forward slashes must be used, because backslashes are both
+valid characters in an OU name and used as escapes for other characters.  If you need a backslash in an OU 
+name, it may need to be quadrupled to pass through the shell escape and ldap escape.
+</para>
+
+<sect3>
+<title>Possible Errors</title>
+
+<para>
+<variablelist>
+	<varlistentry><term><errorname>ADS support not compiled in</errorname></term>
+	<listitem><para>
+	<indexterm><primary>config.cache</primary></indexterm>
+	<indexterm><primary>Kerberos</primary></indexterm>
+	<indexterm><primary>headers files</primary></indexterm>
+	Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the
+	Kerberos libraries and headers files are installed.
+	</para></listitem></varlistentry>
+
+	<varlistentry><term><errorname>net ads join prompts for user name</errorname></term>
+	<listitem><para>
+	<indexterm><primary>kinit</primary></indexterm>
+	<indexterm><primary>rights</primary></indexterm>
+	You need to log in to the domain using <userinput>kinit
+	<replaceable>USERNAME</replaceable>@<replaceable>REALM</replaceable></userinput>.
+	<replaceable>USERNAME</replaceable> must be a user who has rights to add a machine to the domain.
+	</para></listitem></varlistentry>
+
+	<varlistentry><term>Unsupported encryption/or checksum types</term>
+	<listitem><para>
+	<indexterm><primary>/etc/krb5.conf</primary></indexterm>
+	<indexterm><primary>unsupported encryption</primary></indexterm>
+	<indexterm><primary>Kerberos</primary></indexterm>
+	Make sure that the <filename>/etc/krb5.conf</filename> is correctly configured
+	for the type and version of Kerberos installed on the system.
+	</para></listitem></varlistentry>
+</variablelist>
+</para>
+
+</sect3>
+
+</sect2>
+
+<sect2 id="ads-test-server">
+<title>Testing Server Setup</title>
+
+<para>
+<indexterm><primary>successful join</primary></indexterm>
+<indexterm><primary>computer account</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+If the join was successful, you will see a new computer account with the
+NetBIOS name of your Samba server in Active Directory (in the <quote>Computers</quote>
+folder under Users and Computers.
+</para>
+
+<para>
+<indexterm><primary>Windows 2000</primary></indexterm>
+<indexterm><primary>net</primary><secondary>use</secondary></indexterm>
+<indexterm><primary>DES-CBC-MD5</primary></indexterm>
+On a Windows 2000 client, try <userinput>net use * \\server\share</userinput>. You should
+be logged in with Kerberos without needing to know a password. If this fails, then run
+<userinput>klist tickets</userinput>. Did you get a ticket for the server? Does it have
+an encryption type of DES-CBC-MD5? 
+</para>
+
+<note><para>
+<indexterm><primary>DES-CBC-MD5</primary></indexterm>
+<indexterm><primary>ARCFOUR-HMAC-MD5</primary></indexterm>
+<indexterm><primary>encoding</primary></indexterm>
+Samba can use both DES-CBC-MD5 encryption as well as ARCFOUR-HMAC-MD5 encoding.
+</para></note>
+
+</sect2>
+
+<sect2 id="ads-test-smbclient">
+<title>Testing with &smbclient;</title>
+
+<para>
+<indexterm><primary>smbclient</primary></indexterm>
+<indexterm><primary>Kerberos</primary></indexterm>
+<indexterm><primary>Kerberos authentication</primary></indexterm>
+On your Samba server try to log in to a Windows 2000 server or your Samba
+server using &smbclient; and Kerberos. Use &smbclient; as usual, but
+specify the <option>-k</option> option to choose Kerberos authentication.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Notes</title>
+
+<para>
+<indexterm><primary>administrator password</primary></indexterm>
+<indexterm><primary>change password</primary></indexterm>
+<indexterm><primary>encryption types</primary></indexterm>
+You must change the administrator password at least once after installing a domain controller, 
+to create the right encryption types.
+</para>
+
+<para>
+<indexterm><primary>_kerberos._udp</primary></indexterm>
+<indexterm><primary>_ldap._tcp</primary></indexterm>
+<indexterm><primary>default DNS setup</primary></indexterm>
+Windows 200x does not seem to create the <parameter>_kerberos._udp</parameter> and
+<parameter>_ldap._tcp</parameter> in the default DNS setup. Perhaps this will be fixed later in service packs.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Sharing User ID Mappings between Samba Domain Members</title>
+
+<para>
+<indexterm><primary>maps UNIX users and groups</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+Samba maps UNIX users and groups (identified by UIDs and GIDs) to Windows users and groups (identified by SIDs).
+These mappings are done by the <parameter>idmap</parameter> subsystem of Samba.
+</para>
+
+<para>
+<indexterm><primary>mappings</primary></indexterm>
+<indexterm><primary>CIFS</primary></indexterm>
+<indexterm><primary>NFS</primary></indexterm>
+In some cases it is useful to share these mappings between Samba domain members,
+so <emphasis>name->id</emphasis> mapping is identical on all machines.
+This may be needed in particular when sharing files over both CIFS and NFS.
+</para>
+
+<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>ldap idmap suffix</primary></indexterm>
+To use the <emphasis>LDAP</emphasis> <parameter>ldap idmap suffix</parameter>, set:
+</para>
+
+<smbconfblock>
+<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+</smbconfblock>
+
+<para>
+See the &smb.conf; man page entry for the <smbconfoption name="ldap idmap suffix"></smbconfoption>
+parameter for further information.
+</para>
+
+<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>LDAP administrative password</primary></indexterm>
+<indexterm><primary>secrets.tdb</primary></indexterm>
+Do not forget to specify also the <smbconfoption name="ldap admin dn"/>
+and to make certain to set the LDAP administrative password into the <filename>secrets.tdb</filename> using:
+<screen>
+&rootprompt; smbpasswd -w ldap-admin-password
+</screen>
+In place of <literal>ldap-admin-password</literal>, substitute the LDAP administration password for your
+system.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>machine trust accounts</primary></indexterm>
+In the process of adding/deleting/re-adding domain member machine trust accounts, there are
+many traps for the unwary player and many <quote>little</quote> things that can go wrong.
+It is particularly interesting how often subscribers on the Samba mailing list have concluded
+after repeated failed attempts to add a machine account that it is necessary to <quote>reinstall</quote>
+MS Windows on the machine. In truth, it is seldom necessary to reinstall because of this type
+of problem. The real solution is often quite simple, and with an understanding of how MS Windows
+networking functions, it is easy to overcome.
+</para>
+
+<sect2>
+<title>Cannot Add Machine Back to Domain</title>
+
+<para>
+<indexterm><primary>machine trust account</primary></indexterm>
+<indexterm><primary>already exists</primary></indexterm>
+<quote>A Windows workstation was reinstalled. The original domain machine trust
+account was deleted and added immediately. The workstation will not join the domain if I use 
+the same machine name. Attempts to add the machine fail with a message that the machine already
+exists on the network &smbmdash; I know it does not. Why is this failing?</quote>
+</para>
+
+<para>
+<indexterm><primary>NetBIOS name cache</primary></indexterm>
+<indexterm><primary>nbtstat</primary></indexterm>
+The original name is still in the NetBIOS name cache and must expire after machine account
+deletion before adding that same name as a domain member again. The best advice is to delete
+the old account and then add the machine with a new name. Alternately, the name cache can be flushed and
+reloaded with current data using the <command>nbtstat</command> command on the Windows client:
+<screen>
+&dosprompt; nbtstat -R
+</screen>
+</para>
+
+</sect2>
+
+<sect2>
+<title>Adding Machine to Domain Fails</title>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>fails</primary></indexterm>
+<quote>Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a
+message that says, <errorname>"The machine could not be added at this time, there is a network problem.
+Please try again later."</errorname> Why?</quote>
+</para>
+
+<para>
+<indexterm><primary>check logs</primary></indexterm>
+You should check that there is an <smbconfoption name="add machine script"/> in your &smb.conf;
+file. If there is not, please add one that is appropriate for your OS platform. If a script
+has been defined, you will need to debug its operation. Increase the <smbconfoption name="log level"></smbconfoption>
+in the &smb.conf; file to level 10, then try to rejoin the domain. Check the logs to see which
+operation is failing.
+</para>
+
+<para>
+Possible causes include:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+<indexterm><primary>script</primary></indexterm>
+<indexterm><primary>path specified</primary></indexterm>
+	The script does not actually exist, or could not be located in the path specified.
+	</para>
+
+	<para>
+<indexterm><primary>UNIX system account</primary></indexterm>
+<indexterm><primary>Samba SAM account</primary></indexterm>
+	<emphasis>Corrective action:</emphasis> Fix it. Make sure when run manually
+	that the script will add both the UNIX system account and the Samba SAM account.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>UNIX system account</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+	The machine could not be added to the UNIX system accounts file <filename>/etc/passwd</filename>.
+	</para>
+
+	<para>
+<indexterm><primary>legal UNIX system account name</primary></indexterm>
+<indexterm><primary>uppercase</primary></indexterm>
+	<emphasis>Corrective action:</emphasis> Check that the machine name is a legal UNIX
+	system account name. If the UNIX utility <command>useradd</command> is called,
+	then make sure that the machine name you are trying to add can be added using this
+	tool. <command>Useradd</command> on some systems will not allow any uppercase characters
+	nor will it allow spaces in the name.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>backend database</primary></indexterm>
+<indexterm><primary>UNIX system account</primary></indexterm>
+<indexterm><primary>Samba backend database</primary></indexterm>
+The <smbconfoption name="add machine script"/> does not create the
+machine account in the Samba backend database; it is there only to create a UNIX system
+account to which the Samba backend database account can be mapped.
+</para>
+
+</sect2>
+
+<sect2>
+	<title>I Can't Join a Windows 2003 PDC</title>
+
+	<para>
+<indexterm><primary>SMB signing</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>Windows 2003</primary></indexterm>
+<indexterm><primary>SMB/CIFS</primary></indexterm>
+	Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0.
+	Set <smbconfoption name="client use spnego">yes</smbconfoption> when communicating 
+	with a Windows 2003 server. This will not interfere with other Windows clients that do not
+	support the more advanced security features of Windows 2003 because the client will simply
+	negotiate a protocol that both it and the server suppport. This is a well-known fall-back facility
+	that is built into the SMB/CIFS protocols.
+	</para>
+
+</sect2>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-FastStart.xml b/docs-xml/Samba3-HOWTO/TOSHARG-FastStart.xml
new file mode 100644
index 00000000000..ff2552515b1
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-FastStart.xml
@@ -0,0 +1,1306 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="FastStart">
+<chapterinfo>
+	&author.jht;
+</chapterinfo>
+
+<title>Fast Start: Cure for Impatience</title>
+
+<para>
+When we first asked for suggestions for inclusion in the Samba HOWTO documentation,
+someone wrote asking for example configurations &smbmdash; and lots of them. That is remarkably
+difficult to do without losing a lot of value that can be derived from presenting
+many extracts from working systems. That is what the rest of this document does.
+It does so with extensive descriptions of the configuration possibilities within the
+context of the chapter that covers it. We hope that this chapter is the medicine 
+that has been requested.
+</para>
+
+<para>
+The information in this chapter is very sparse compared with the book <quote>Samba-3 by Example</quote>
+that was written after the original version of this book was nearly complete. <quote>Samba-3 by Example</quote>
+was the result of feedback from reviewers during the final copy editing of the first edition. It
+was interesting to see that reader feedback mirrored that given by the original reviewers.
+In any case, a month and a half was spent in doing basic research to better understand what
+new as well as experienced network administrators would best benefit from. The book <quote>Samba-3 by Example</quote>
+is the result of that research. What is presented in the few pages of this book is covered
+far more comprehensively in the second edition of <quote>Samba-3 by Example</quote>. The second edition
+of both books will be released at the same time.
+</para>
+
+<para>
+So in summary, the book <quote>The Official Samba-3 HOWTO &amp; Reference Guide</quote> is intended
+as the equivalent of an auto mechanic's repair guide. The book <quote>Samba-3 by Example</quote> is the
+equivalent of the driver's guide that explains how to drive the car. If you want complete network
+configuration examples, go to <ulink url="http://www.samba.org/samba/docs/Samba3-ByExample.pdf">Samba-3 by
+Example</ulink>.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+Samba needs very little configuration to create a basic working system.
+In this chapter we progress from the simple to the complex, for each providing
+all steps and configuration file changes needed to make each work. Please note
+that a comprehensively configured system will likely employ additional smart
+features. These additional features are covered in the remainder of this document.
+</para>
+
+<para>
+The examples used here have been obtained from a number of people who made
+requests for example configurations. All identities have been obscured to protect
+the guilty, and any resemblance to unreal nonexistent sites is deliberate.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Description of Example Sites</title>
+
+<para>
+In the first set of configuration examples we consider the case of exceptionally simple system requirements.
+There is a real temptation to make something that should require little effort much too complex.
+</para>
+
+<para>
+<link linkend="anon-ro"></link> documents the type of server that might be sufficient to serve CD-ROM images,
+or reference document files for network client use. This configuration is also discussed in <link
+linkend="StandAloneServer"></link>, <link linkend="RefDocServer"></link>.  The purpose for this configuration
+is to provide a shared volume that is read-only that anyone, even guests, can access.
+</para>
+
+<para>
+The second example shows a minimal configuration for a print server that anyone can print to as long as they
+have the correct printer drivers installed on their computer. This is a mirror of the system described in
+<link linkend="StandAloneServer"></link>, <link linkend="SimplePrintServer"></link>.
+</para>
+
+<para>
+The next example is of a secure office file and print server that will be accessible only to users who have an
+account on the system. This server is meant to closely resemble a workgroup file and print server, but has to
+be more secure than an anonymous access machine.  This type of system will typically suit the needs of a small
+office. The server provides no network logon facilities, offers no domain control; instead it is just a
+network-attached storage (NAS) device and a print server.
+</para>
+
+<para>
+The later example consider more complex systems that will either integrate into existing MS Windows networks
+or replace them entirely. These cover domain member servers as well as Samba domain control (PDC/BDC) and
+finally describes in detail a large distributed network with branch offices in remote locations.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Worked Examples</title>
+
+<para>
+The configuration examples are designed to cover everything necessary to get Samba 
+running. They do not cover basic operating system platform configuration, which is
+clearly beyond the scope of this text.
+</para>
+
+<para>
+It is also assumed that Samba has been correctly installed, either by way of installation
+of the packages that are provided by the operating system vendor or through other means.
+</para>
+
+	<sect2>
+	<title>Standalone Server</title>
+
+	<para>
+	<indexterm><primary>Server Type</primary><secondary>Stand-alone</secondary></indexterm>
+	A standalone server implies no more than the fact that it is not a domain controller
+	and it does not participate in domain control. It can be a simple, workgroup-like
+	server, or it can be a complex server that is a member of a domain security context.
+	</para>
+
+	<para>
+	As the examples are developed, every attempt is made to progress the system toward greater capability, just as
+	one might expect would happen in a real business office as that office grows in size and its needs change.
+	</para>
+
+		<sect3 id="anon-ro">
+		<title>Anonymous Read-Only Document Server</title>
+
+		<para>
+		<indexterm><primary>read only</primary><secondary>server</secondary></indexterm>
+		The purpose of this type of server is to make available to any user
+		any documents or files that are placed on the shared resource. The
+		shared resource could be a CD-ROM drive, a CD-ROM image, or a file
+		storage area.
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			The file system share point will be <filename>/export</filename>.
+			</para></listitem>
+
+			<listitem><para>
+			All files will be owned by a user called Jack Baumbach.
+			Jack's login name will be <emphasis>jackb</emphasis>. His password will be
+			<emphasis>m0r3pa1n</emphasis> &smbmdash; of course, that's just the example we are
+			using; do not use this in a production environment because
+			all readers of this document will know it.
+			</para></listitem>
+		</itemizedlist>
+
+		<procedure>
+		<title>Installation Procedure: Read-Only Server</title>
+			<step><para>
+			Add user to system (with creation of the user's home directory):
+<screen>
+&rootprompt;<userinput>useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb</userinput>
+</screen>
+			</para></step>
+
+			<step><para>
+			Create directory, and set permissions and ownership:
+<screen>
+&rootprompt;<userinput>mkdir /export</userinput>
+&rootprompt;<userinput>chmod u+rwx,g+rx,o+rx /export</userinput>
+&rootprompt;<userinput>chown jackb.users /export</userinput>
+</screen>
+			</para></step>
+
+			<step><para>
+			Copy the files that should be shared to the <filename>/export</filename>
+			directory.
+			</para></step>
+
+			<step><para>
+			Install the Samba configuration file (<filename>/etc/samba/smb.conf</filename>)
+			as shown in <link linkend="anon-example">Anonymous Read-Only Server Configuration</link>.
+			</para></step>
+
+<example id="anon-example">
+<title>Anonymous Read-Only Server Configuration</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">HOBBIT</smbconfoption>
+<smbconfoption name="security">share</smbconfoption>
+
+<smbconfsection name="[data]"/>
+<smbconfoption name="comment">Data</smbconfoption>
+<smbconfoption name="path">/export</smbconfoption>
+<smbconfoption name="read only">Yes</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+			<step><para>
+			Test the configuration file by executing the following command:
+<screen>
+&rootprompt;<userinput>testparm</userinput>
+</screen>
+			Alternatively, where you are operating from a master configuration file called
+			<filename>smb.conf.master</filename>, the following sequence of commands might prove
+			more appropriate:
+<screen>
+&rootprompt; cd /etc/samba
+&rootprompt; testparm -s smb.conf.master > smb.conf
+&rootprompt; testparm
+</screen>
+			Note any error messages that might be produced. Proceed only if error-free output has been
+			obtained. An example of typical output that should be generated from the above configuration
+			file is shown here:
+<screen>
+Load smb config files from /etc/samba/smb.conf
+Processing section "[data]"
+Loaded services file OK.
+Server role: ROLE_STANDALONE
+Press enter to see a dump of your service definitions
+<userinput>[Press enter]</userinput>
+
+# Global parameters
+[global]
+	workgroup = MIDEARTH
+	netbios name = HOBBIT
+	security = share
+
+[data]
+	comment = Data
+	path = /export
+	read only = Yes
+	guest only = Yes
+</screen>
+			</para></step>
+
+			<step><para>
+			Start Samba using the method applicable to your operating system platform. The method that
+			should be used is platform dependent. Refer to <link linkend="startingSamba">Starting Samba</link>
+			for further information regarding the starting of Samba.
+			</para></step>
+
+			<step><para>
+			Configure your MS Windows client for workgroup <emphasis>MIDEARTH</emphasis>,
+			set the machine name to ROBBINS, reboot, wait a few (2 - 5) minutes,
+			then open Windows Explorer and visit the Network Neighborhood.
+			The machine HOBBIT should be visible. When you click this machine
+			icon, it should open up to reveal the <emphasis>data</emphasis> share. After
+			you click the share, it should open up to reveal the files previously
+			placed in the <filename>/export</filename> directory.
+			</para></step>
+		</procedure>
+
+		<para>
+		The information above (following # Global parameters) provides the complete
+		contents of the <filename>/etc/samba/smb.conf</filename> file.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Anonymous Read-Write Document Server</title>
+
+		<para>
+		<indexterm><primary>anonymous</primary><secondary>read-write server</secondary></indexterm>
+		We should view this configuration as a progression from the previous example.
+		The difference is that shared access is now forced to the user identity of jackb
+		and to the primary group jackb belongs to. One other refinement we can make is to
+		add the user <emphasis>jackb</emphasis> to the <filename>smbpasswd</filename> file.
+		To do this, execute:
+<screen>
+&rootprompt;<userinput>smbpasswd -a jackb</userinput>
+New SMB password: <userinput>m0r3pa1n</userinput>
+Retype new SMB password: <userinput>m0r3pa1n</userinput>
+Added user jackb.
+</screen>
+		Addition of this user to the <filename>smbpasswd</filename> file allows all files
+		to be displayed in the Explorer Properties boxes as belonging to <emphasis>jackb</emphasis>
+		instead of to <emphasis>User Unknown</emphasis>.
+		</para>
+
+		<para>
+		The complete, modified &smb.conf; file is as shown in <link linkend="anon-rw"/>.
+		</para>
+
+<example id="anon-rw">
+<title>Modified Anonymous Read-Write smb.conf</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">HOBBIT</smbconfoption>
+<smbconfoption name="security">SHARE</smbconfoption>
+
+<smbconfsection name="[data]"/>
+<smbconfoption name="comment">Data</smbconfoption>
+<smbconfoption name="path">/export</smbconfoption>
+<smbconfoption name="force user">jackb</smbconfoption>
+<smbconfoption name="force group">users</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+		</sect3>
+
+		<sect3>
+		<title>Anonymous Print Server</title>
+
+		<para>
+		<indexterm><primary>anonymous</primary><secondary>print server</secondary></indexterm>
+		An anonymous print server serves two purposes:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			It allows printing to all printers from a single location.
+			</para></listitem>
+
+			<listitem><para>
+			It reduces network traffic congestion due to many users trying
+			to access a limited number of printers.
+			</para></listitem>
+		</itemizedlist>
+
+		<para>
+		In the simplest of anonymous print servers, it is common to require the installation
+		of the correct printer drivers on the Windows workstation. In this case the print
+		server will be designed to just pass print jobs through to the spooler, and the spooler
+		should be configured to do raw pass-through to the printer. In other words, the print
+		spooler should not filter or process the data stream being passed to the printer.
+		</para>
+
+		<para>
+		In this configuration, it is undesirable to present the Add Printer Wizard, and we do
+		not want to have automatic driver download, so we disable it in the following
+		configuration. <link linkend="anon-print"></link> is the resulting &smb.conf; file.
+		</para>
+
+<example id="anon-print">
+<title>Anonymous Print Server smb.conf</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">LUTHIEN</smbconfoption>
+<smbconfoption name="security">share</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+<smbconfoption name="disable spoolss">Yes</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+		<para>
+		The above configuration is not ideal. It uses no smart features, and it deliberately
+		presents a less than elegant solution. But it is basic, and it does print. Samba makes
+		use of the direct printing application program interface that is provided by CUPS.
+		When Samba has been compiled and linked with the CUPS libraries, the default printing
+		system will be CUPS. By specifying that the printcap name is CUPS, Samba will use
+		the CUPS library API to communicate directly with CUPS for all printer functions.
+		It is possible to force the use of external printing commands by setting the value
+		of the <parameter>printing</parameter> to either SYSV or BSD, and thus the value of
+		the parameter <parameter>printcap name</parameter> must be set to something other than
+		CUPS. In such case, it could be set to the name of any file that contains a list
+		of printers that should be made available to Windows clients.
+		</para>
+
+		<note><para>
+		Windows users will need to install a local printer and then change the print
+		to device after installation of the drivers. The print to device can then be set to
+		the network printer on this machine.
+		</para></note>
+
+		<para>
+		Make sure that the directory <filename>/var/spool/samba</filename> is capable of being used
+		as intended. The following steps must be taken to achieve this:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			The directory must be owned by the superuser (root) user and group:
+<screen>
+&rootprompt;<userinput>chown root.root /var/spool/samba</userinput>
+</screen>
+			</para></listitem>
+
+			<listitem><para>
+			Directory permissions should be set for public read-write with the
+			sticky bit set as shown:
+<screen>
+&rootprompt;<userinput>chmod a+twrx /var/spool/samba</userinput>
+</screen>
+		The purpose of setting the sticky bit is to prevent who does not own the temporary print file
+		from being able to take control of it with the potential for devious misuse.
+			</para></listitem>
+		</itemizedlist>
+
+
+		<note><para>
+		<indexterm><primary>MIME</primary><secondary>raw</secondary></indexterm>
+		<indexterm><primary>raw printing</primary></indexterm>
+		On CUPS-enabled systems there is a facility to pass raw data directly to the printer without
+		intermediate processing via CUPS print filters. Where use of this mode of operation is desired,
+		it is necessary to configure a raw printing device. It is also necessary to enable the raw mime
+		handler in the <filename>/etc/mime.conv</filename> and <filename>/etc/mime.types</filename>
+		files. Refer to <link linkend="cups-raw"></link>.
+		</para></note>
+
+		</sect3>
+
+		<sect3>
+
+		<title>Secure Read-Write File and Print Server</title>
+
+		<para>
+		We progress now from simple systems to a server that is slightly more complex.
+		</para>
+
+		<para>
+		Our new server will require a public data storage area in which only authenticated
+		users (i.e., those with a local account) can store files, as well as a home directory.
+		There will be one printer that should be available for everyone to use.
+		</para>
+
+		<para>
+		In this hypothetical environment (no espionage was conducted to obtain this data),
+		the site is demanding a simple environment that is <emphasis>secure enough</emphasis>
+		but not too difficult to use. 
+		</para>
+
+		<para>
+		Site users will be Jack Baumbach, Mary Orville, and Amed Sehkah. Each will have
+		a password (not shown in further examples). Mary will be the printer administrator and will
+		own all files in the public share.
+		</para>
+
+		<para>
+		This configuration will be based on <emphasis>user-level security</emphasis> that
+		is the default, and for which the default is to store Microsoft Windows-compatible
+		encrypted passwords in a file called <filename>/etc/samba/smbpasswd</filename>.
+		The default &smb.conf; entry that makes this happen is
+		<smbconfoption name="passdb backend">smbpasswd, guest</smbconfoption>. Since this is the default,
+		it is not necessary to enter it into the configuration file. Note that the guest backend is
+		added to the list of active passdb backends no matter whether it specified directly in Samba configuration
+		file or not.
+		</para>
+
+
+		<procedure>
+		<title>Installing the Secure Office Server</title>
+			<step><para>
+		<indexterm><primary>office server</primary></indexterm>
+			Add all users to the operating system:
+<screen>
+&rootprompt;<userinput>useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb</userinput>
+&rootprompt;<userinput>useradd -c "Mary Orville" -m -g users -p secret maryo</userinput>
+&rootprompt;<userinput>useradd -c "Amed Sehkah" -m -g users -p secret ameds</userinput>
+</screen>
+			</para></step>
+
+			<step><para>
+			Configure the Samba &smb.conf; file as shown in <link linkend="OfficeServer"/>.
+			</para></step>
+
+<example id="OfficeServer">
+<title>Secure Office Server smb.conf</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">OLORIN</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+<smbconfoption name="disable spoolss">Yes</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[public]"/>
+<smbconfoption name="comment">Data</smbconfoption>
+<smbconfoption name="path">/export</smbconfoption>
+<smbconfoption name="force user">maryo</smbconfoption>
+<smbconfoption name="force group">users</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printer admin">root, maryo</smbconfoption>
+<smbconfoption name="create mask">0600</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+			<step><para>
+			Initialize the Microsoft Windows password database with the new users:
+<screen>
+&rootprompt;<userinput>smbpasswd -a root</userinput>
+New SMB password: <userinput>bigsecret</userinput>
+Reenter smb password: <userinput>bigsecret</userinput>
+Added user root.
+
+&rootprompt;<userinput>smbpasswd -a jackb</userinput>
+New SMB password: <userinput>m0r3pa1n</userinput>
+Retype new SMB password: <userinput>m0r3pa1n</userinput>
+Added user jackb.
+
+&rootprompt;<userinput>smbpasswd -a maryo</userinput>
+New SMB password: <userinput>secret</userinput>
+Reenter smb password: <userinput>secret</userinput>
+Added user maryo.
+
+&rootprompt;<userinput>smbpasswd -a ameds</userinput>
+New SMB password: <userinput>mysecret</userinput>
+Reenter smb password: <userinput>mysecret</userinput>
+Added user ameds.
+</screen>
+			</para></step>
+
+			<step><para>
+			Install printer using the CUPS Web interface. Make certain that all
+			printers that will be shared with Microsoft Windows clients are installed
+			as raw printing devices.
+			</para></step>
+
+			<step><para>
+			Start Samba using the operating system administrative interface.
+			Alternately, this can be done manually by executing:
+			<indexterm><primary>smbd</primary></indexterm>
+			<indexterm><primary>nmbd</primary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
+<screen>
+&rootprompt;<userinput> nmbd; smbd;</userinput>
+</screen>
+			Both applications automatically execute as daemons. Those who are paranoid about
+			maintaining control can add the <constant>-D</constant> flag to coerce them to start
+			up in daemon mode.
+			</para></step>
+
+			<step><para>
+			Configure the <filename>/export</filename> directory:
+<screen>
+&rootprompt;<userinput>mkdir /export</userinput>
+&rootprompt;<userinput>chown maryo.users /export</userinput>
+&rootprompt;<userinput>chmod u=rwx,g=rwx,o-rwx /export</userinput>
+</screen>
+			</para></step>
+
+			<step><para>
+			Check that Samba is running correctly:
+<screen>
+&rootprompt;<userinput>smbclient -L localhost -U%</userinput>
+Domain=[MIDEARTH] OS=[UNIX] Server=[Samba-3.0.20]
+
+Sharename      Type      Comment
+---------      ----      -------
+public         Disk      Data
+IPC$           IPC       IPC Service (Samba-3.0.20)
+ADMIN$         IPC       IPC Service (Samba-3.0.20)
+hplj4          Printer   hplj4
+
+Server               Comment
+---------            -------
+OLORIN               Samba-3.0.20
+
+Workgroup            Master
+---------            -------
+MIDEARTH             OLORIN
+</screen>
+			The following error message indicates that Samba was not running:
+<screen>
+&rootprompt; smbclient -L olorin -U%
+Error connecting to 192.168.1.40 (Connection refused)
+Connection to olorin failed
+</screen>
+			</para></step>
+
+			<step><para>
+			Connect to OLORIN as maryo:
+<screen>
+&rootprompt;<userinput>smbclient //olorin/maryo -Umaryo%secret</userinput>
+OS=[UNIX] Server=[Samba-3.0.20]
+smb: \> <userinput>dir</userinput>
+.                              D        0  Sat Jun 21 10:58:16 2003
+..                             D        0  Sat Jun 21 10:54:32 2003
+Documents                      D        0  Fri Apr 25 13:23:58 2003
+DOCWORK                        D        0  Sat Jun 14 15:40:34 2003
+OpenOffice.org                 D        0  Fri Apr 25 13:55:16 2003
+.bashrc                        H     1286  Fri Apr 25 13:23:58 2003
+.netscape6                    DH        0  Fri Apr 25 13:55:13 2003
+.mozilla                      DH        0  Wed Mar  5 11:50:50 2003
+.kermrc                        H      164  Fri Apr 25 13:23:58 2003
+.acrobat                      DH        0  Fri Apr 25 15:41:02 2003
+
+		55817 blocks of size 524288. 34725 blocks available
+smb: \> <userinput>q</userinput>
+</screen>
+			</para></step>
+		</procedure>
+
+			<para>
+			By now you should be getting the hang of configuration basics. Clearly, it is time to
+			explore slightly more complex examples. For the remainder of this chapter we abbreviate
+			instructions, since there are previous examples.
+			</para>
+
+		</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Domain Member Server</title>
+
+	<para>
+	<indexterm><primary>Server Type</primary><secondary>Domain Member</secondary></indexterm>
+	In this instance we consider the simplest server configuration we can get away with
+	to make an accounting department happy. Let's be warned, the users are accountants and they
+	do have some nasty demands. There is a budget for only one server for this department.
+	</para>
+
+	<para>
+	The network is managed by an internal Information Services Group (ISG), to which we belong.
+	Internal politics are typical of a medium-sized organization; Human Resources is of the
+	opinion that they run the ISG because they are always adding and disabling users. Also,
+	departmental managers have to fight tooth and nail to gain basic network resources access for
+	their staff. Accounting is different, though, they get exactly what they want. So this should
+	set the scene.
+	</para>
+
+	<para>
+	We use the users from the last example. The accounting department
+	has a general printer that all departmental users may use. There is also a check printer
+	that may be used only by the person who has authority to print checks. The chief financial
+	officer (CFO) wants that printer to be completely restricted and for it to be located in the
+	private storage area in her office. It therefore must be a network printer.
+	</para>
+
+	<para>
+	The accounting department uses an accounting application called <emphasis>SpytFull</emphasis>
+	that must be run from a central application server. The software is licensed to run only off
+	one server, there are no workstation components, and it is run off a mapped share. The data
+	store is in a UNIX-based SQL backend. The UNIX gurus look after that, so this is not our
+	problem.
+	</para>
+
+	<para>
+	The accounting department manager (maryo) wants a general filing system as well as a separate
+	file storage area for form letters (nastygrams). The form letter area should be read-only to
+	all accounting staff except the manager. The general filing system has to have a structured
+	layout with a general area for all staff to store general documents as well as a separate
+	file area for each member of her team that is private to that person, but she wants full
+	access to all areas. Users must have a private home share for personal work-related files
+	and for materials not related to departmental operations.
+	</para>
+	
+		<sect3>
+		<title>Example Configuration</title>
+		
+		<para>
+		The server <emphasis>valinor</emphasis> will be a member server of the company domain.
+		Accounting will have only a local server. User accounts will be on the domain controllers,
+		as will desktop profiles and all network policy files.
+		</para>
+
+		<procedure>
+			<step><para>
+			Do not add users to the UNIX/Linux server; all of this will run off the
+			central domain.
+			</para></step>
+
+			<step><para>
+			Configure &smb.conf; according to <link linkend="fast-member-server">Member server smb.conf
+			(globals)</link> and <link linkend="fast-memberserver-shares">Member server smb.conf (shares
+			and services)</link>.
+			</para></step>
+
+<example id="fast-member-server">
+<title>Member Server smb.conf (Globals)</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">VALINOR</smbconfoption>
+<smbconfoption name="security">DOMAIN</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+<smbconfoption name="disable spoolss">Yes</smbconfoption>
+<smbconfoption name="show add printer wizard">No</smbconfoption>
+<smbconfoption name="idmap uid">15000-20000</smbconfoption>
+<smbconfoption name="idmap gid">15000-20000</smbconfoption>
+<smbconfoption name="winbind use default domain">Yes</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="fast-memberserver-shares">
+<title>Member Server smb.conf (Shares and Services)</title>
+<smbconfblock>
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[spytfull]"/>
+<smbconfoption name="comment">Accounting Application Only</smbconfoption>
+<smbconfoption name="path">/export/spytfull</smbconfoption>
+<smbconfoption name="valid users">@Accounts</smbconfoption>
+<smbconfoption name="admin users">maryo</smbconfoption>
+<smbconfoption name="read only">Yes</smbconfoption>
+
+<smbconfsection name="[public]"/>
+<smbconfoption name="comment">Data</smbconfoption>
+<smbconfoption name="path">/export/public</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printer admin">root, maryo</smbconfoption>
+<smbconfoption name="create mask">0600</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+			<step><para>
+			<indexterm><primary>net</primary><secondary>rpc</secondary></indexterm>
+			Join the domain. Note: Do not start Samba until this step has been completed!
+<screen>
+&rootprompt;<userinput>net rpc join -Uroot%'bigsecret'</userinput>
+Joined domain MIDEARTH.
+</screen>
+			</para></step>
+
+			<step><para>
+			Make absolutely certain that you disable (shut down) the <command>nscd</command>
+			daemon on any system on which <command>winbind</command> is configured to run.
+			</para></step>
+
+			<step><para>
+			Start Samba following the normal method for your operating system platform.
+			If you wish to do this manually, execute as root:
+			<indexterm><primary>smbd</primary></indexterm>
+			<indexterm><primary>nmbd</primary></indexterm>
+			<indexterm><primary>winbindd</primary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
+<screen>
+&rootprompt;<userinput>nmbd; smbd; winbindd;</userinput>
+</screen>
+			</para></step>
+
+			<step><para>
+			Configure the name service switch (NSS) control file on your system to resolve user and group names
+			via winbind. Edit the following lines in <filename>/etc/nsswitch.conf</filename>:
+<programlisting>
+passwd: files winbind
+group:  files winbind
+hosts:  files dns winbind
+</programlisting>
+			</para></step>
+
+			<step><para>
+			Set the password for <command>wbinfo</command> to use:
+<screen>
+&rootprompt;<userinput>wbinfo --set-auth-user=root%'bigsecret'</userinput>
+</screen>
+			</para></step>
+
+			<step><para>
+			Validate that domain user and group credentials can be correctly resolved by executing:
+<screen>
+&rootprompt;<userinput>wbinfo -u</userinput>
+MIDEARTH\maryo
+MIDEARTH\jackb
+MIDEARTH\ameds
+...
+MIDEARTH\root
+
+&rootprompt;<userinput>wbinfo -g</userinput>
+MIDEARTH\Domain Users
+MIDEARTH\Domain Admins
+MIDEARTH\Domain Guests
+...
+MIDEARTH\Accounts
+</screen>
+			</para></step>
+
+			<step><para>
+			Check that <command>winbind</command> is working. The following demonstrates correct
+			username resolution via the <command>getent</command> system utility:
+<screen>
+&rootprompt;<userinput>getent passwd maryo</userinput>
+maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
+</screen>
+			</para></step>
+
+			<step><para>
+			A final test that we have this under control might be reassuring:
+<screen>
+&rootprompt;<userinput>touch /export/a_file</userinput>
+&rootprompt;<userinput>chown maryo /export/a_file</userinput>
+&rootprompt;<userinput>ls -al /export/a_file</userinput>
+...
+-rw-r--r--    1 maryo    users       11234 Jun 21 15:32 a_file
+...
+
+&rootprompt;<userinput>rm /export/a_file</userinput>
+</screen>
+			</para></step>
+
+			<step><para>
+			Configuration is now mostly complete, so this is an opportune time
+			to configure the directory structure for this site:
+<screen>
+&rootprompt;<userinput>mkdir -p /export/{spytfull,public}</userinput>
+&rootprompt;<userinput>chmod ug=rwxS,o=x /export/{spytfull,public}</userinput>
+&rootprompt;<userinput>chown maryo.Accounts /export/{spytfull,public}</userinput>
+</screen>
+			</para></step>
+		</procedure>
+
+		</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Domain Controller</title>
+
+
+	<para>
+	<indexterm><primary>Server Type</primary><secondary>Domain Controller</secondary></indexterm>
+	For the remainder of this chapter the focus is on the configuration of domain control.
+	The examples that follow are for two implementation strategies. Remember, our objective is
+	to create a simple but working solution. The remainder of this book should help to highlight
+	opportunity for greater functionality and the complexity that goes with it.
+	</para>
+
+	<para>
+	A domain controller configuration can be achieved with a simple configuration using the new
+	tdbsam password backend. This type of configuration is good for small
+	offices, but has limited scalability (cannot be replicated), and performance can be expected
+	to fall as the size and complexity of the domain increases.
+	</para>
+
+	<para>
+	The use of tdbsam is best limited to sites that do not need
+	more than a Primary Domain Controller (PDC). As the size of a domain grows the need
+	for additional domain controllers becomes apparent. Do not attempt to under-resource
+	a Microsoft Windows network environment; domain controllers provide essential
+	authentication services. The following are symptoms of an under-resourced domain control
+	environment:
+	</para>
+
+	<itemizedlist>	
+		<listitem><para>
+		 Domain logons intermittently fail.
+		</para></listitem>
+
+		<listitem><para>
+		File access on a domain member server intermittently fails, giving a permission denied
+		error message.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	A more scalable domain control authentication backend option might use
+	Microsoft Active Directory or an LDAP-based backend. Samba-3 provides
+	for both options as a domain member server. As a PDC, Samba-3 is not able to provide
+	an exact alternative to the functionality that is available with Active Directory.
+	Samba-3 can provide a scalable LDAP-based PDC/BDC solution.
+	</para>
+
+	<para>
+	The tdbsam authentication backend provides no facility to replicate
+	the contents of the database, except by external means (i.e., there is no self-contained protocol
+	in Samba-3 for Security Account Manager database [SAM] replication).
+	</para>
+
+	<note><para>
+	If you need more than one domain controller, do not use a tdbsam authentication backend.
+	</para></note>
+
+		<sect3>
+		<title>Example: Engineering Office</title>
+
+		<para>
+		The engineering office network server we present here is designed to demonstrate use
+		of the new tdbsam password backend. The tdbsam
+		facility is new to Samba-3. It is designed to provide many user and machine account controls
+		that are possible with Microsoft Windows NT4. It is safe to use this in smaller networks.
+		</para>
+
+		<procedure>
+			<step><para>
+			A working PDC configuration using the tdbsam
+			password backend can be found in <link linkend="fast-engoffice-global">Engineering Office smb.conf
+			(globals)</link> together with <link linkend="fast-engoffice-shares">Engineering Office smb.conf
+			(shares and services)</link>:
+			<indexterm><primary>pdbedit</primary></indexterm>
+			</para></step>
+
+<example id="fast-engoffice-global">
+<title>Engineering Office smb.conf (globals)</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">FRODO</smbconfoption>
+<smbconfoption name="passdb backend">tdbsam</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+<smbconfoption name="add user script">/usr/sbin/useradd -m %u</smbconfoption>
+<smbconfoption name="delete user script">/usr/sbin/userdel -r %u</smbconfoption>
+<smbconfoption name="add group script">/usr/sbin/groupadd %g</smbconfoption>
+<smbconfoption name="delete group script">/usr/sbin/groupdel %g</smbconfoption>
+<smbconfoption name="add user to group script">/usr/sbin/groupmod -A %u %g</smbconfoption>
+<smbconfoption name="delete user from group script">/usr/sbin/groupmod -R %u %g</smbconfoption>
+<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /var/lib/nobody %u</smbconfoption>
+<smbconfcomment>Note: The following specifies the default logon script.</smbconfcomment>
+<smbconfcomment>Per user logon scripts can be specified in the user account using pdbedit </smbconfcomment>
+<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+<smbconfcomment>This sets the default profile path. Set per user paths with pdbedit</smbconfcomment>
+<smbconfoption name="logon path">\\%L\Profiles\%U</smbconfoption>
+<smbconfoption name="logon drive">H:</smbconfoption>
+<smbconfoption name="logon home">\\%L\%U</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="os level">35</smbconfoption>
+<smbconfoption name="preferred master">Yes</smbconfoption>
+<smbconfoption name="domain master">Yes</smbconfoption>
+<smbconfoption name="idmap uid">15000-20000</smbconfoption>
+<smbconfoption name="idmap gid">15000-20000</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+</smbconfblock>
+</example>
+
+<example id="fast-engoffice-shares">
+<title>Engineering Office smb.conf (shares and services)</title>
+<smbconfblock>
+<smbconfsection name="[homes]"/>
+<smbconfoption name="comment">Home Directories</smbconfoption>
+<smbconfoption name="valid users">%S</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfcomment>Printing auto-share (makes printers available thru CUPS)</smbconfcomment>
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printer admin">root, maryo</smbconfoption>
+<smbconfoption name="create mask">0600</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfsection name="[print$]"/>
+<smbconfoption name="comment">Printer Drivers Share</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
+<smbconfoption name="write list">maryo, root</smbconfoption>
+<smbconfoption name="printer admin">maryo, root</smbconfoption>
+
+<smbconfcomment>Needed to support domain logons</smbconfcomment>
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">Network Logon Service</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+<smbconfoption name="admin users">root, maryo</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+
+<smbconfcomment>For profiles to work, create a user directory under the path</smbconfcomment>
+<smbconfcomment> shown. i.e., mkdir -p /var/lib/samba/profiles/maryo</smbconfcomment>
+<smbconfsection name="[Profiles]"/>
+<smbconfoption name="comment">Roaming Profile Share</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
+<smbconfoption name="read only">No</smbconfoption>
+<smbconfoption name="profile acls">Yes</smbconfoption>
+
+<smbconfcomment>Other resource (share/printer) definitions would follow below.</smbconfcomment>
+</smbconfblock>
+</example>
+
+			<step><para>
+			Create UNIX group accounts as needed using a suitable operating system tool:
+<screen>
+&rootprompt;<userinput>groupadd ntadmins</userinput>
+&rootprompt;<userinput>groupadd designers</userinput>
+&rootprompt;<userinput>groupadd engineers</userinput>
+&rootprompt;<userinput>groupadd qateam</userinput>
+</screen>
+			</para></step>
+
+			<step><para>
+			Create user accounts on the system using the appropriate tool
+			provided with the operating system. Make sure all user home directories
+			are created also. Add users to groups as required for access control
+			on files, directories, printers, and as required for use in the Samba
+			environment.
+			</para></step>
+
+
+			<step><para>
+			<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
+			<indexterm><primary>initGroups.sh</primary></indexterm>
+			Assign each of the UNIX groups to NT groups by executing this shell script
+			(You could name the script <filename>initGroups.sh</filename>):
+<screen>
+#!/bin/bash
+#### Keep this as a shell script for future re-use
+			
+# First assign well known groups
+net groupmap add ntgroup="Domain Admins" unixgroup=ntadmins rid=512 type=d
+net groupmap add ntgroup="Domain Users"  unixgroup=users rid=513 type=
+net groupmap add ntgroup="Domain Guests" unixgroup=nobody rid=514 type=d
+
+# Now for our added Domain Groups
+net groupmap add ntgroup="Designers" unixgroup=designers type=d
+net groupmap add ntgroup="Engineers" unixgroup=engineers type=d
+net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d
+</screen>
+			</para></step>
+
+			<step><para>
+			Create the <filename>scripts</filename> directory for use in the 
+			<smbconfsection name="[NETLOGON]"/> share:
+<screen>
+&rootprompt;<userinput>mkdir -p /var/lib/samba/netlogon/scripts</userinput>
+</screen>
+			Place the logon scripts that will be used (batch or cmd scripts)
+			in this directory.
+			</para></step>
+		</procedure>
+
+		<para>
+		The above configuration provides a functional PDC
+		system to which must be added file shares and printers as required.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>A Big Organization</title>
+
+		<para>
+		In this section we finally get to review in brief a Samba-3 configuration that
+		uses a Lightweight Directory Access (LDAP)-based authentication backend. The
+		main reasons for this choice are to provide the ability to host primary
+		and Backup Domain Control (BDC), as well as to enable a higher degree of
+		scalability to meet the needs of a very distributed environment.
+		</para>
+
+			<sect4>
+			<title>The Primary Domain Controller</title>
+
+			<para>
+			This is an example of a minimal configuration to run a Samba-3 PDC
+			using an LDAP authentication backend. It is assumed that the operating system
+			has been correctly configured.
+			</para>
+
+			<para>
+			The Idealx scripts (or equivalent) are needed to manage LDAP-based POSIX and/or
+			SambaSamAccounts. The Idealx scripts may be downloaded from the <ulink url="http://www.idealx.org">
+			Idealx</ulink> Web site. They may also be obtained from the Samba tarball. Linux
+			distributions tend to install the Idealx scripts in the 
+			<filename>/usr/share/doc/packages/sambaXXXXXX/examples/LDAP/smbldap-tools</filename> directory.
+			Idealx scripts version <constant>smbldap-tools-0.9.1</constant> are known to work well.
+			</para>
+
+			<procedure>
+				<step><para>
+				Obtain from the Samba sources <filename>~/examples/LDAP/samba.schema</filename>
+				and copy it to the <filename>/etc/openldap/schema/</filename> directory.
+				</para></step>
+
+				<step><para>
+				Set up the LDAP server. This example is suitable for OpenLDAP 2.1.x.
+				The <filename>/etc/openldap/slapd.conf</filename> file.
+				<indexterm><primary>/etc/openldap/slapd.conf</primary></indexterm>
+<title>Example slapd.conf File</title>
+<screen>
+# Note commented out lines have been removed
+include         /etc/openldap/schema/core.schema
+include         /etc/openldap/schema/cosine.schema
+include         /etc/openldap/schema/inetorgperson.schema
+include         /etc/openldap/schema/nis.schema
+include         /etc/openldap/schema/samba.schema
+
+pidfile         /var/run/slapd/slapd.pid
+argsfile        /var/run/slapd/slapd.args
+
+database        bdb
+suffix          "dc=quenya,dc=org"
+rootdn          "cn=Manager,dc=quenya,dc=org"
+rootpw          {SSHA}06qDkonA8hk6W6SSnRzWj0/pBcU3m0/P
+# The password for the above is 'nastyon3'
+
+directory     /var/lib/ldap
+
+index   objectClass     eq
+index cn                      pres,sub,eq
+index sn                      pres,sub,eq
+index uid                     pres,sub,eq
+index displayName             pres,sub,eq
+index uidNumber               eq
+index gidNumber               eq
+index memberUid               eq
+index   sambaSID              eq
+index   sambaPrimaryGroupSID  eq
+index   sambaDomainName       eq
+index   default               sub
+</screen>
+				</para></step>
+
+				<step><para>
+				Create the following file <filename>initdb.ldif</filename>:
+				<indexterm><primary>initdb.ldif</primary></indexterm>
+<programlisting>
+# Organization for SambaXP Demo
+dn: dc=quenya,dc=org
+objectclass: dcObject
+objectclass: organization
+dc: quenya
+o: SambaXP Demo
+description: The SambaXP Demo LDAP Tree
+
+# Organizational Role for Directory Management
+dn: cn=Manager,dc=quenya,dc=org
+objectclass: organizationalRole
+cn: Manager
+description: Directory Manager
+
+# Setting up the container for users
+dn: ou=People, dc=quenya, dc=org
+objectclass: top
+objectclass: organizationalUnit
+ou: People
+
+# Set up an admin handle for People OU
+dn: cn=admin, ou=People, dc=quenya, dc=org
+cn: admin
+objectclass: top
+objectclass: organizationalRole
+objectclass: simpleSecurityObject
+userPassword: {SSHA}0jBHgQ1vp4EDX2rEMMfIudvRMJoGwjVb
+# The password for above is 'mordonL8'
+</programlisting>
+				</para></step>
+
+				<step><para>
+				Load the initial data above into the LDAP database:
+<screen>
+&rootprompt;<userinput>slapadd -v -l initdb.ldif</userinput>
+</screen>
+				</para></step>
+
+				<step><para>
+				Start the LDAP server using the appropriate tool or method for
+				the operating system platform on which it is installed.
+				</para></step>
+
+				<step><para>
+				Install the Idealx script files in the <filename>/usr/local/sbin</filename> directory,
+				then configure the smbldap_conf.pm file to match your system configuration.
+				</para></step>
+
+				<step><para>
+				The &smb.conf; file that drives this backend can be found in example <link
+				linkend="fast-ldap">LDAP backend smb.conf for PDC</link>. Add additional stanzas
+				as required.
+				</para></step>
+
+<example id="fast-ldap">
+<title>LDAP backend smb.conf for PDC</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">FRODO</smbconfoption>
+<smbconfoption name="passdb backend">ldapsam:ldap://localhost</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+<smbconfoption name="add user script">/usr/local/sbin/smbldap-useradd -m '%u'</smbconfoption>
+<smbconfoption name="delete user script">/usr/local/sbin/smbldap-userdel %u</smbconfoption>
+<smbconfoption name="add group script">/usr/local/sbin/smbldap-groupadd -p '%g'</smbconfoption>
+<smbconfoption name="delete group script">/usr/local/sbin/smbldap-groupdel '%g'</smbconfoption>
+<smbconfoption name="add user to group script">/usr/local/sbin/smbldap-groupmod -m '%u' '%g'</smbconfoption>
+<smbconfoption name="delete user from group script">/usr/local/sbin/smbldap-groupmod -x '%u' '%g'</smbconfoption>
+<smbconfoption name="set primary group script">/usr/local/sbin/smbldap-usermod -g '%g' '%u'</smbconfoption>
+<smbconfoption name="add machine script">/usr/local/sbin/smbldap-useradd -w '%u'</smbconfoption>
+<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+<smbconfoption name="logon path">\\%L\Profiles\%U</smbconfoption>
+<smbconfoption name="logon drive">H:</smbconfoption>
+<smbconfoption name="logon home">\\%L\%U</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="os level">35</smbconfoption>
+<smbconfoption name="preferred master">Yes</smbconfoption>
+<smbconfoption name="domain master">Yes</smbconfoption>
+<smbconfoption name="ldap suffix">dc=quenya,dc=org</smbconfoption>
+<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap group suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=Manager</smbconfoption>
+<smbconfoption name="ldap ssl">no</smbconfoption>
+<smbconfoption name="ldap passwd sync">Yes</smbconfoption>
+<smbconfoption name="idmap uid">15000-20000</smbconfoption>
+<smbconfoption name="idmap gid">15000-20000</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+</smbconfblock>
+</example>
+
+				<step><para>
+				Add the LDAP password to the <filename>secrets.tdb</filename> file so Samba can update
+				the LDAP database:
+<screen>
+&rootprompt;<userinput>smbpasswd -w mordonL8</userinput>
+</screen>
+				</para></step>
+
+				<step><para>
+				Add users and groups as required. Users and groups added using Samba tools
+				will automatically be added to both the LDAP backend and the operating
+				system as required.
+				</para></step>
+
+			</procedure>
+
+			</sect4>
+
+			<sect4>
+			<title>Backup Domain Controller</title>
+
+			<para>
+			<link linkend="fast-bdc"/> shows the example configuration for the BDC. Note that
+			the &smb.conf; file does not specify the smbldap-tools scripts &smbmdash; they are
+			not needed on a BDC. Add additional stanzas for shares and printers as required.
+			</para>
+
+			<procedure>
+				<step><para>
+				Decide if the BDC should have its own LDAP server or not. If the BDC is to be
+				the LDAP server, change the following &smb.conf; as indicated. The default
+				configuration in <link linkend="fast-bdc">Remote LDAP BDC smb.conf</link>
+				uses a central LDAP server.
+				</para></step>
+
+<example id="fast-bdc">
+<title>Remote LDAP BDC smb.conf</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
+<smbconfoption name="netbios name">GANDALF</smbconfoption>
+<smbconfoption name="passdb backend">ldapsam:ldap://frodo.quenya.org</smbconfoption>
+<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
+<smbconfoption name="logon path">\\%L\Profiles\%U</smbconfoption>
+<smbconfoption name="logon drive">H:</smbconfoption>
+<smbconfoption name="logon home">\\%L\%U</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="os level">33</smbconfoption>
+<smbconfoption name="preferred master">Yes</smbconfoption>
+<smbconfoption name="domain master">No</smbconfoption>
+<smbconfoption name="ldap suffix">dc=quenya,dc=org</smbconfoption>
+<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap group suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=Manager</smbconfoption>
+<smbconfoption name="ldap ssl">no</smbconfoption>
+<smbconfoption name="ldap passwd sync">Yes</smbconfoption>
+<smbconfoption name="idmap uid">15000-20000</smbconfoption>
+<smbconfoption name="idmap gid">15000-20000</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+</smbconfblock>
+</example>
+
+				<step><para>
+				Configure the NETLOGON and PROFILES directory as for the PDC in <link linkend="fast-bdc"/>.
+				</para></step>
+			</procedure>
+
+			</sect4>
+
+		</sect3>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Further-Resources.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Further-Resources.xml
new file mode 100644
index 00000000000..0a9d7d1cd53
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Further-Resources.xml
@@ -0,0 +1,174 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="Further-Resources">
+<chapterinfo>
+	&author.jelmer;
+	<pubdate>May 1, 2003</pubdate>
+</chapterinfo>
+
+<title>Further Resources</title>
+
+<sect1>
+	<title>Web sites</title>
+
+<itemizedlist>
+
+	<listitem><para>
+	<ulink url="http://hr.uoregon.edu/davidrl/cifs.txt">
+	<emphasis>CIFS: Common Insecurities Fail Scrutiny</emphasis> by <quote>Hobbit</quote></ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://afr.com/it/2002/10/01/FFXDF43AP6D.html">
+	<emphasis>Doing the Samba on Windows</emphasis> by Financial Review
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://ubiqx.org/cifs/">
+	<emphasis>Implementing CIFS</emphasis> by Christopher R. Hertel
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://samba.anu.edu.au/cifs/docs/what-is-smb.html">
+	<emphasis>Just What Is SMB?</emphasis> by Richard Sharpe
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://www.linux-mag.com/1999-05/samba_01.html">
+	<emphasis>Opening Windows Everywhere</emphasis> by Mike Warfield
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://www.tldp.org/HOWTO/SMB-HOWTO.html">
+	<emphasis>SMB HOWTO</emphasis> by David Wood
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://www.phrack.org/phrack/60/p60-0x0b.txt">
+	<emphasis>SMB/CIFS by The Root</emphasis> by <quote>ledin</quote>
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://www.linux-mag.com/1999-09/samba_01.html">
+	<emphasis>The Story of Samba</emphasis> by Christopher R. Hertel
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://hr.uoregon.edu/davidrl/samba/">
+	<emphasis>The Unofficial Samba HOWTO</emphasis> by David Lechnyr
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://www.linux-mag.com/2001-05/smb_01.html">
+	<emphasis>Understanding the Network Neighborhood</emphasis> by Christopher R. Hertel
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://www.linux-mag.com/2002-02/samba_01.html">
+	<emphasis>Using Samba as a PDC</emphasis> by Andrew Bartlett
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://ru.samba.org/samba/ftp/docs/Samba24Hc13.pdf">
+	<emphasis>PDF version of the Troubleshooting Techniques chapter</emphasis>
+	from the second edition of Sam's Teach Yourself Samba in 24 Hours
+	(publishing date of Dec. 12, 2001)</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://ru.samba.org/samba/ftp/slides/">
+	<emphasis>Slide presentations</emphasis> by Samba Team members
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html">
+	<emphasis>Introduction to Samba-3.0</emphasis> by Motonobu Takahashi 
+	(written in Japanese). </ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://www.linux-mag.com/2001-05/smb_01.html">
+	<emphasis>Understanding the Network Neighborhood</emphasis>, by team member
+	Chris Hertel. This article appeared in the May 2001 issue of 
+	Linux Magazine. 
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="ftp://ftp.stratus.com/pub/vos/customers/samba/">
+	<emphasis>Samba 2.0.x Troubleshooting guide</emphasis> from Paul Green
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://samba.org/samba/docs/10years.html">
+	<emphasis>Ten Years of Samba</emphasis>
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://tldp.org/HOWTO/Samba-Authenticated-Gateway-HOWTO.html">
+		<emphasis>Samba Authenticated Gateway HOWTO</emphasis>
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://samba.org/samba/docs/SambaIntro.html">
+		<emphasis>An Introduction to Samba</emphasis>
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://www.samba.org/cifs/">
+		<emphasis>What is CIFS?</emphasis>
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://support.microsoft.com/support/kb/articles/q92/5/88.asp">
+		<emphasis>WFWG: Password Caching and How It Affects LAN Manager
+			Security</emphasis> at Microsoft Knowledge Base
+	</ulink>
+	</para></listitem>
+
+</itemizedlist>
+
+</sect1>
+
+<sect1>
+	<title>Related updates from Microsoft</title>
+
+<itemizedlist>
+	<listitem><para>
+	<ulink url="http://support.microsoft.com/support/kb/articles/q92/5/88.asp">
+		<emphasis>Enhanced Encryption for Windows 95 Password Cache</emphasis> 
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://support.microsoft.com/support/kb/articles/q136/4/18.asp">
+		<emphasis>Windows '95 File Sharing Updates</emphasis>
+	</ulink>
+	</para></listitem>
+
+	<listitem><para>
+	<ulink url="http://support.microsoft.com/support/kb/articles/q136/4/18.asp">
+		<emphasis>Windows for Workgroups Sharing Updates</emphasis>
+	</ulink>
+	</para></listitem>
+
+</itemizedlist>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Group-Mapping.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Group-Mapping.xml
new file mode 100644
index 00000000000..337ae3d794b
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Group-Mapping.xml
@@ -0,0 +1,920 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="groupmapping">
+<chapterinfo>
+	&author.jht;
+	<author>
+		<firstname>Jean Fran�ois</firstname><surname>Micouleau</surname>
+	</author>
+	&author.jerry;
+</chapterinfo>
+<title>Group Mapping: MS Windows and UNIX</title>
+
+
+	<para>
+<indexterm significance="preferred"><primary>groups</primary><secondary>mapping</secondary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>associations</primary></indexterm>
+<indexterm><primary>UNIX groups</primary></indexterm>
+<indexterm><primary>groupmap</primary></indexterm>
+<indexterm><primary>net</primary></indexterm>
+	Starting with Samba-3, new group mapping functionality is available to create associations
+	between Windows group SIDs and UNIX group GIDs. The <command>groupmap</command> subcommand
+	included with the &net; tool can be used to manage these associations.
+	</para>
+
+	<para>
+<indexterm><primary>group mapping</primary></indexterm>
+<indexterm><primary>domain groups</primary></indexterm>
+	The new facility for mapping NT groups to UNIX system groups allows the administrator to decide
+	which NT domain groups are to be exposed to MS Windows clients. Only those NT groups that map
+	to a UNIX group that has a value other than the default (<constant>-1</constant>) will be exposed
+	in group selection lists in tools that access domain users and groups.
+	</para>
+
+	<warning>
+	<para>
+	<indexterm><primary>domain admin group</primary></indexterm>
+<indexterm><primary>Windows group</primary></indexterm>
+	The <parameter>domain admin group</parameter> parameter has been removed in Samba-3 and should no longer
+	be specified in &smb.conf;. In Samba-2.2.x, this parameter was used to give the listed users membership in the
+	<constant>Domain Admins</constant> Windows group, which gave local admin rights on their workstations
+	(in default configurations).
+	</para>
+	</warning>
+
+<sect1>
+<title>Features and Benefits</title>
+
+	<para>
+	Samba allows the administrator to create MS Windows NT4/200x group accounts and to
+	arbitrarily associate them with UNIX/Linux group accounts.
+	</para>
+
+	<para>
+	<indexterm><primary>UID</primary></indexterm>
+	<indexterm><primary>GID</primary></indexterm>
+	<indexterm><primary>idmap uid</primary></indexterm>
+<indexterm><primary>MMC</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>ID range</primary></indexterm>
+<indexterm><primary>group accounts</primary></indexterm>
+	Group accounts can be managed using the MS Windows NT4 or MS Windows 200x/XP Professional MMC tools.
+	Appropriate interface scripts should be provided in &smb.conf; if it is desired that UNIX/Linux system
+	accounts should be automatically created when these tools are used. In the absence of these scripts, and
+	so long as <command>winbindd</command> is running, Samba group accounts that are created using these
+	tools will be allocated UNIX UIDs and GIDs from the ID range specified by the
+	<smbconfoption name="idmap uid"/>/<smbconfoption name="idmap gid"/>
+	parameters in the &smb.conf; file.
+	</para>
+
+	<figure id="idmap-sid2gid">
+		<title>IDMAP: Group SID-to-GID Resolution.</title>
+		<imagefile scale="50">idmap-sid2gid</imagefile>
+	</figure>
+
+	<figure id="idmap-gid2sid">
+		<title>IDMAP: GID Resolution to Matching SID.</title>
+	<imagefile scale="50">idmap-gid2sid</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>IDMAP</primary></indexterm>
+<indexterm><primary>SID-to-GID</primary></indexterm>
+<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
+<indexterm><primary>group mappings</primary></indexterm>
+	In both cases, when winbindd is not running, only locally resolvable groups can be recognized. Please refer to
+	<link linkend="idmap-sid2gid">IDMAP: Group SID-to-GID Resolution</link> and <link
+	linkend="idmap-gid2sid">IDMAP: GID Resolution to Matching SID</link>.  The <command>net groupmap</command> is
+	used to establish UNIX group to NT SID mappings as shown in <link linkend="idmap-store-gid2sid">IDMAP: storing
+	group mappings</link>.
+	</para>
+
+	<figure id="idmap-store-gid2sid">
+		<title>IDMAP Storing Group Mappings.</title>
+		<imagefile scale="50">idmap-store-gid2sid</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>groupadd</primary></indexterm>
+	<indexterm><primary>groupdel</primary></indexterm>
+<indexterm><primary>shadow utilities</primary></indexterm>
+<indexterm><primary>groupmod</primary></indexterm>
+	Administrators should be aware that where &smb.conf; group interface scripts make
+	direct calls to the UNIX/Linux system tools (the shadow utilities, <command>groupadd</command>,
+	<command>groupdel</command>, and <command>groupmod</command>), the resulting UNIX/Linux group names will be subject
+	to any limits imposed by these tools. If the tool does not allow uppercase characters
+	or space characters, then the creation of an MS Windows NT4/200x-style group of
+	<literal>Engineering Managers</literal> will attempt to create an identically named
+	UNIX/Linux group, an attempt that will of course fail.
+	</para>
+
+	<para>
+	<indexterm><primary>GID</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	There are several possible workarounds for the operating system tools limitation. One
+	method is to use a script that generates a name for the UNIX/Linux system group that
+	fits the operating system limits and that then just passes the UNIX/Linux group ID (GID)
+	back to the calling Samba interface. This will provide a dynamic workaround solution.
+	</para>
+
+	<para>
+<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
+	Another workaround is to manually create a UNIX/Linux group, then manually create the
+	MS Windows NT4/200x group on the Samba server, and then use the <command>net groupmap</command>
+	tool to connect the two to each other.
+	</para>
+
+</sect1>
+
+<sect1>
+<title>Discussion</title>
+
+	<para>
+<indexterm><primary>Windows NT4/200x</primary></indexterm>
+<indexterm><primary>group privileges</primary></indexterm>
+	When you install <application>MS Windows NT4/200x</application> on a computer, the installation
+	program creates default users and groups, notably the <constant>Administrators</constant> group,
+	and gives that group privileges necessary to perform essential system tasks,
+	such as the ability to change the date and time or to kill (or close) any process running on the
+	local machine.
+	</para>
+	
+	<para>
+	<indexterm><primary>Administrator</primary></indexterm>
+	The <constant>Administrator</constant> user is a member of the <constant>Administrators</constant> group, and thus inherits
+	<constant>Administrators</constant> group privileges. If a <constant>joe</constant> user is created to be a member of the
+	<constant>Administrators</constant> group, <constant>joe</constant> has exactly the same rights as the user
+	<constant>Administrator</constant>.
+	</para>
+
+	<para>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>Domain Admins</primary></indexterm>
+<indexterm><primary>inherits rights</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+	When an MS Windows NT4/200x/XP machine is made a domain member, the <quote>Domain Admins</quote> group of the
+	PDC is added to the local <constant>Administrators</constant> group of the workstation. Every member of the
+	<constant>Domain Admins</constant> group inherits the rights of the local <constant>Administrators</constant> group when
+	logging on the workstation.
+	</para>
+
+	<para>
+<indexterm><primary>Domain Admins</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+	The following steps describe how to make Samba PDC users members of the <constant>Domain Admins</constant> group.
+	</para>
+
+	<orderedlist>
+		<listitem><para>
+		Create a UNIX group (usually in <filename>/etc/group</filename>); let's call it <constant>domadm</constant>.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>/etc/group</primary></indexterm>
+		Add to this group the users that must be <quote>Administrators</quote>. For example,
+		if you want <constant>joe, john</constant>, and <constant>mary</constant> to be administrators,
+		your entry in <filename>/etc/group</filename> will look like this:
+		</para>
+
+		<para><programlisting>
+		domadm:x:502:joe,john,mary
+		</programlisting>
+		</para></listitem>
+
+		<listitem><para>
+		Map this domadm group to the <quote>Domain Admins</quote> group by executing the command:
+		</para>
+
+		<para>
+<screen>
+&rootprompt;<userinput>net groupmap add ntgroup="Domain Admins" unixgroup=domadm rid=512 type=d</userinput>
+</screen>
+		</para>
+		
+		<para>
+		<indexterm><primary>Domain Admins group</primary></indexterm>
+		The quotes around <quote>Domain Admins</quote> are necessary due to the space in the group name.
+		Also make sure to leave no white space surrounding the equal character (=).
+		</para></listitem>
+	</orderedlist>
+
+	<para>
+	Now <constant>joe, john</constant>, and <constant>mary</constant> are domain administrators.
+	</para>
+
+	<para>
+	<indexterm><primary>groups</primary><secondary>domain</secondary></indexterm>
+	It is possible to map any arbitrary UNIX group to any Windows NT4/200x group as well as
+	to make any UNIX group a Windows domain group. For example, if you wanted to include a
+	UNIX group (e.g., acct) in an ACL on a local file or printer on a Domain Member machine,
+	you would flag that group as a domain group by running the following on the Samba PDC:
+	</para>
+
+	<para>
+<screen>
+&rootprompt;<userinput>net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct type=d</userinput>
+</screen>
+	The <literal>ntgroup</literal> value must be in quotes if it contains space characters to prevent
+	the space from being interpreted as a command delimiter.
+	</para>
+
+	<para>
+<indexterm><primary>RID</primary></indexterm>
+<indexterm><primary>assigned RID</primary></indexterm>
+	Be aware that the RID parameter is an unsigned 32-bit integer that should
+	normally start at 1000. However, this RID must not overlap with any RID assigned
+	to a user. Verification for this is done differently depending on the passdb backend
+	you are using. Future versions of the tools may perform the verification automatically,
+	but for now the burden is on you.
+	</para>
+
+	<sect2>
+	<title>Warning: User Private Group Problems</title>
+
+	<para>
+<indexterm><primary>group accounts</primary></indexterm>
+<indexterm><primary>Red Hat Linux</primary></indexterm>
+<indexterm><primary>private groups</primary></indexterm>
+	Windows does not permit user and group accounts to have the same name.
+	This has serious implications for all sites that use private group accounts.
+	A private group account is an administrative practice whereby users are each
+	given their own group account. Red Hat Linux, as well as several free distributions
+	of Linux, by default create private groups.
+	</para>
+
+	<para>
+<indexterm><primary>UNIX/Linux group</primary></indexterm>
+<indexterm><primary>Windows group</primary></indexterm>
+	When mapping a UNIX/Linux group to a Windows group account, all conflict can
+	be avoided by assuring that the Windows domain group name does not overlap
+	with any user account name.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Nested Groups: Adding Windows Domain Groups to Windows Local Groups</title>
+
+	<indexterm><primary>groups</primary><secondary>nested</secondary></indexterm>
+
+	<para>
+<indexterm><primary>nested groups</primary></indexterm>
+	This functionality is known as <constant>nested groups</constant> and was first added to
+	Samba-3.0.3.
+	</para>
+
+	<para>
+<indexterm><primary>nested groups</primary></indexterm>
+	All MS Windows products since the release of Windows NT 3.10 support the use of nested groups.
+	Many Windows network administrators depend on this capability because it greatly simplifies security
+	administration.
+	</para>
+
+	<para>
+<indexterm><primary>nested group</primary></indexterm>
+<indexterm><primary>group membership</primary></indexterm>
+<indexterm><primary>domain security</primary></indexterm>
+<indexterm><primary>domain member server</primary></indexterm>
+<indexterm><primary>local groups</primary></indexterm>
+<indexterm><primary>domain global groups</primary></indexterm>
+<indexterm><primary>domain global users</primary></indexterm>
+	The nested group architecture was designed with the premise that day-to-day user and group membership
+	management should be performed on the domain security database. The application of group security
+	should be implemented on domain member servers using only local groups. On the domain member server,
+	all file system security controls are then limited to use of the local groups, which will contain
+	domain global groups and domain global users.
+	</para>
+
+	<para>
+<indexterm><primary>individual domain user</primary></indexterm>
+<indexterm><primary>domain group settings</primary></indexterm>
+<indexterm><primary>Account Unknown</primary></indexterm>
+	You may ask, What are the benefits of this arrangement? The answer is obvious to those who have plumbed
+	the dark depths of Windows networking architecture. Consider for a moment a server on which are stored
+	200,000 files, each with individual domain user and domain group settings. The company that owns the
+	file server is bought by another company, resulting in the server being moved to another location, and then
+	it is made a member of a different domain. Who would you think now owns all the files and directories?
+	Answer: Account Unknown.
+	</para>
+
+	<para>
+<indexterm><primary>directory access control</primary></indexterm>
+<indexterm><primary>local groups</primary></indexterm>
+<indexterm><primary>ACL</primary></indexterm>
+<indexterm><primary>Account Unknown</primary></indexterm>
+	Unraveling the file ownership mess is an unenviable administrative task that can be avoided simply
+	by using local groups to control all file and directory access control. In this case, only the members
+	of the local groups will have been lost. The files and directories in the storage subsystem will still
+	be owned by the local groups. The same goes for all ACLs on them. It is administratively much simpler
+	to delete the <constant>Account Unknown</constant> membership entries inside local groups with appropriate
+	entries for domain global groups in the new domain that the server has been made a member of.
+	</para>
+
+	<para>
+<indexterm><primary>nested groups</primary></indexterm>
+<indexterm><primary>administrative privileges</primary></indexterm>
+<indexterm><primary>domain member workstations</primary></indexterm>
+<indexterm><primary>domain member servers</primary></indexterm>
+<indexterm><primary>member machine</primary></indexterm>
+<indexterm><primary>full rights</primary></indexterm>
+<indexterm><primary>Domain Admins</primary></indexterm>
+<indexterm><primary>local administrative privileges</primary></indexterm>
+	Another prominent example of the use of nested groups involves implementation of administrative privileges
+	on domain member workstations and servers. Administrative privileges are given to all members of the
+	built-in local group <constant>Administrators</constant> on each domain member machine. To ensure that all domain
+	administrators have full rights on the member server or workstation, on joining the domain, the
+	<constant>Domain Admins</constant> group is added to the local Administrators group. Thus everyone who is
+	logged into the domain as a member of the Domain Admins group is also granted local administrative
+	privileges on each domain member.
+	</para>
+
+	<para>
+<indexterm><primary>nested groups</primary></indexterm>
+<indexterm><primary>auxiliary members</primary></indexterm>
+<indexterm><primary>/etc/group</primary></indexterm>
+<indexterm><primary>winbind</primary></indexterm>
+	UNIX/Linux has no concept of support for nested groups, and thus Samba has for a long time not supported
+	them either. The problem is that you would have to enter UNIX groups as auxiliary members of a group in
+	<filename>/etc/group</filename>. This does not work because it was not a design requirement at the time
+	the UNIX file system security model was implemented. Since Samba-2.2, the winbind daemon can provide
+	<filename>/etc/group</filename> entries on demand by obtaining user and group information from the domain
+	controller that the Samba server is a member of.
+	</para>
+
+	<para>
+<indexterm><primary>/etc/group</primary></indexterm>
+<indexterm><primary>libnss_winbind</primary></indexterm>
+<indexterm><primary>local groups</primary></indexterm>
+<indexterm><primary>Domain Users</primary></indexterm>
+<indexterm><primary>alias group</primary></indexterm>
+	In effect, Samba supplements the <filename>/etc/group</filename> data via the dynamic
+	<command>libnss_winbind</command> mechanism. Beginning with Samba-3.0.3, this facility is used to provide
+	local groups in the same manner as Windows. It works by expanding the local groups on the
+	fly as they are accessed. For example, the <constant>Domain Users</constant> group of the domain is made
+	a member of the local group <constant>demo</constant>. Whenever Samba needs to resolve membership of the
+	<constant>demo</constant> local (alias) group, winbind asks the domain controller for demo members of the Domain Users
+	group. By definition, it can only contain user objects, which can then be faked to be member of the
+	UNIX/Linux group <constant>demo</constant>.
+	</para>
+
+	<para>
+<indexterm><primary>nested groups</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>winbind</primary></indexterm>
+<indexterm><primary>local groups</primary></indexterm>
+<indexterm><primary>Domain User Manager</primary></indexterm>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group</tertiary></indexterm>
+	To enable the use of nested groups, <command>winbindd</command> must be used with NSS winbind.
+	Creation and administration of the local groups is done best via the Windows Domain User Manager or its
+	Samba equivalent, the utility <command>net rpc group</command>. Creating the local group
+	<constant>demo</constant> is achieved by executing:
+	<screen>
+	&rootprompt; net rpc group add demo -L -Uroot%not24get
+	</screen>
+<indexterm><primary>addmem</primary></indexterm>
+<indexterm><primary>delmem</primary></indexterm>
+	Here the -L switch means that you want to create a local group. It may be necessary to add -S and -U
+	switches for accessing the correct host with appropriate user or root privileges. Adding and removing
+	group members can be done via the <constant>addmem</constant> and <constant>delmem</constant> subcommands of
+	<command>net rpc group</command> command. For example, addition of <quote>DOM\Domain Users</quote> to the
+	local group <constant>demo</constant> is done by executing:
+	<screen>
+	net rpc group addmem demo "DOM\Domain Users"
+	</screen>
+<indexterm><primary>getent group demo</primary></indexterm>
+<indexterm><primary>trusted domain</primary></indexterm>
+<indexterm><primary>foreign domain</primary></indexterm>
+<indexterm><primary>local access permissions</primary></indexterm>
+	Having completed these two steps, the execution of <command>getent group demo</command> will show demo
+	members of the global <constant>Domain Users</constant> group as members of  the group
+	<constant>demo</constant>.  This also works with any local or domain user. In case the domain DOM trusts
+	another domain, it is also possible to add global users and groups of the trusted domain as members of
+	<constant>demo</constant>. The users from the foreign domain who are members of the group that has been
+	added to the <constant>demo</constant> group now have the same local access permissions as local domain
+	users have. 
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Important Administrative Information</title>
+
+	<para>
+	Administrative rights are necessary in two specific forms:
+	</para>
+
+	<orderedlist>
+		<listitem><para>For Samba-3 domain controllers and domain member servers/clients.</para></listitem>
+		<listitem><para>To manage domain member Windows workstations.</para></listitem>
+	</orderedlist>
+
+	<para>
+<indexterm><primary>rights and privileges</primary></indexterm>
+<indexterm><primary>domain member client</primary></indexterm>
+<indexterm><primary>group account</primary></indexterm>
+	Versions of Samba up to and including 3.0.10 do not provide a means for assigning rights and privileges
+	that are necessary for system administration tasks from a Windows domain member client machine, so
+	domain administration tasks such as adding, deleting, and changing user and group account information, and
+	managing workstation domain membership accounts, can be handled by any account other than root.
+	</para>
+
+	<para>
+<indexterm><primary>privilege management</primary></indexterm>
+<indexterm><primary>delegated</primary></indexterm>
+<indexterm><primary>Administrator</primary></indexterm>
+	Samba-3.0.11 introduced a new privilege management interface (see <link linkend="rights">User Rights and Privileges</link>)
+	that permits these tasks to be delegated to non-root (i.e., accounts other than the equivalent of the
+	MS Windows Administrator) accounts.
+	</para>
+
+	<para>
+<indexterm><primary>mapped</primary></indexterm>
+<indexterm><primary>Domain Admins</primary></indexterm>
+	Administrative tasks on a Windows domain member workstation can be done by anyone who is a member of the
+	<constant>Domain Admins</constant> group. This group can be mapped to any convenient UNIX group.
+	</para>
+
+	<sect3>
+	<title>Applicable Only to Versions Earlier than 3.0.11</title>
+
+	<para>
+<indexterm><primary>privilege</primary></indexterm>
+	Administrative tasks on UNIX/Linux systems, such as adding users or groups, requires
+	<constant>root</constant>-level privilege. The addition of a Windows client to a Samba domain involves the
+	addition of a user account for the Windows client.
+	</para>
+
+	<para>
+<indexterm><primary>system security</primary></indexterm>
+<indexterm><primary>privileges</primary></indexterm>
+	Many UNIX administrators continue to request that the Samba Team make it possible to add Windows workstations, or 
+	the ability to add, delete, or modify user accounts, without requiring <constant>root</constant> privileges. 
+	Such a request violates every understanding of basic UNIX system security.
+	</para>
+
+	<para>
+<indexterm><primary>privileges</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>Domain Server Manager</primary></indexterm>
+<indexterm><primary>Domain User Manager</primary></indexterm>
+<indexterm><primary>manage share-level ACL</primary></indexterm>
+<indexterm><primary>share-level ACLs</primary></indexterm>
+	There is no safe way to provide access on a UNIX/Linux system without providing
+	<constant>root</constant>-level privileges. Provision of <constant>root</constant> privileges can be done
+	either by logging on to the Domain as the user <constant>root</constant> or by permitting particular users to
+	use a UNIX account that has a UID=0 in the <filename>/etc/passwd</filename> database. Users of such accounts
+	can use tools like the NT4 Domain User Manager and the NT4 Domain Server Manager to manage user and group
+	accounts as well as domain member server and client accounts. This level of privilege is also needed to manage
+	share-level ACLs.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Default Users, Groups, and Relative Identifiers</title>
+
+	<para>
+	<indexterm><primary>Relative Identifier</primary><see>RID</see></indexterm>
+	<indexterm><primary>RID</primary></indexterm>
+<indexterm><primary>Windows NT4/200x/XP</primary></indexterm>
+<indexterm><primary>well-known RID</primary></indexterm>
+<indexterm><primary>domain groups</primary></indexterm>
+<indexterm><primary>tdbsam</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>NT groups</primary></indexterm>
+	When first installed, Windows NT4/200x/XP are preconfigured with certain user, group, and
+	alias entities. Each has a well-known RID. These must be preserved for continued
+	integrity of operation. Samba must be provisioned with certain essential domain groups that require
+	the appropriate RID value. When Samba-3 is configured to use <constant>tdbsam</constant>, the essential
+	domain groups are automatically created. It is the LDAP administrator's responsibility to create
+	(provision) the default NT groups.
+	</para>
+
+	<para>
+<indexterm><primary>default users</primary></indexterm>
+<indexterm><primary>default groups</primary></indexterm>
+<indexterm><primary>default aliases</primary></indexterm>
+<indexterm><primary>RID</primary></indexterm>
+	Each essential domain group must be assigned its respective well-known RID. The default users, groups,
+	aliases, and RIDs are shown in <link linkend="WKURIDS">Well-Known User Default RIDs</link>.
+	</para>
+
+	<note><para>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>ldapsam</primary></indexterm>
+<indexterm><primary>domain groups</primary></indexterm>
+<indexterm><primary>RID</primary></indexterm>
+	It is the administrator's responsibility to create the essential domain groups and to assign each
+	its default RID.
+	</para></note>
+
+	<para>
+<indexterm><primary>domain groups</primary></indexterm>
+<indexterm><primary>RID</primary></indexterm>
+	It is permissible to create any domain group that may be necessary; just make certain that the essential
+	domain groups (well known) have been created and assigned their default RIDs. Other groups you create may
+	be assigned any arbitrary RID you care to use.
+	</para>
+
+	<para>
+	Be sure to map each domain group to a UNIX system group. That is the only way to ensure that the group
+	will be available for use as an NT domain group.
+	</para>
+
+	<para>
+	<table frame="all" id="WKURIDS">
+	<title>Well-Known User Default RIDs</title>
+		<tgroup cols="4" align="left">
+			<colspec align="left"/>
+			<colspec align="left"/>
+			<colspec align="left"/>
+			<colspec align="center"/>
+			<thead>
+				<row>
+					<entry>Well-Known Entity</entry>
+					<entry>RID</entry>
+					<entry>Type</entry>
+					<entry>Essential</entry>
+				</row>
+			</thead>
+			<tbody>
+				<row>
+					<entry>Domain Administrator</entry>
+					<entry>500</entry>
+					<entry>User</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Domain Guest</entry>
+					<entry>501</entry>
+					<entry>User</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Domain KRBTGT</entry>
+					<entry>502</entry>
+					<entry>User</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Domain Admins</entry>
+					<entry>512</entry>
+					<entry>Group</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry>Domain Users</entry>
+					<entry>513</entry>
+					<entry>Group</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry>Domain Guests</entry>
+					<entry>514</entry>
+					<entry>Group</entry>
+					<entry>Yes</entry>
+				</row>
+				<row>
+					<entry>Domain Computers</entry>
+					<entry>515</entry>
+					<entry>Group</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Domain Controllers</entry>
+					<entry>516</entry>
+					<entry>Group</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Domain Certificate Admins</entry>
+					<entry>517</entry>
+					<entry>Group</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Domain Schema Admins</entry>
+					<entry>518</entry>
+					<entry>Group</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Domain Enterprise Admins</entry>
+					<entry>519</entry>
+					<entry>Group</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Domain Policy Admins</entry>
+					<entry>520</entry>
+					<entry>Group</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin Admins</entry>
+					<entry>544</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin users</entry>
+					<entry>545</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin Guests</entry>
+					<entry>546</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin Power Users</entry>
+					<entry>547</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin Account Operators</entry>
+					<entry>548</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin System Operators</entry>
+					<entry>549</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin Print Operators</entry>
+					<entry>550</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin Backup Operators</entry>
+					<entry>551</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin Replicator</entry>
+					<entry>552</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+				<row>
+					<entry>Builtin RAS Servers</entry>
+					<entry>553</entry>
+					<entry>Alias</entry>
+					<entry>No</entry>
+				</row>
+			</tbody>
+		</tgroup>
+	</table>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Example Configuration</title>
+
+		<para>
+<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>list</tertiary></indexterm>
+		You can list the various groups in the mapping database by executing
+		<command>net groupmap list</command>. Here is an example:
+		</para>
+
+		<para>
+<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
+<screen>
+&rootprompt; <userinput>net groupmap list</userinput>
+Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
+Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
+Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
+</screen>
+		</para>
+
+		<para>
+		For complete details on <command>net groupmap</command>, refer to the net(8) man page.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Configuration Scripts</title>
+
+	<para>
+	Everyone needs tools. Some of us like to create our own, others prefer to use canned tools
+	(i.e., prepared by someone else for general use). 
+	</para>
+
+	<sect2>
+	<title>Sample &smb.conf; Add Group Script</title>
+
+		<para>
+		<indexterm><primary>smbgrpadd.sh</primary></indexterm>
+		<indexterm><primary>groupadd limitations</primary></indexterm>
+		<indexterm><primary>smbgrpadd.sh</primary></indexterm>
+<indexterm><primary>/etc/group</primary></indexterm>
+<indexterm><primary>groupadd</primary></indexterm>
+		A script to create complying group names for use by the Samba group interfaces
+		is provided in <link linkend="smbgrpadd.sh">smbgrpadd.sh</link>. This script
+		adds a temporary entry in the <filename>/etc/group</filename> file and then renames
+		it to the desired name. This is an example of a method to get around operating
+		system maintenance tool limitations such as those present in some version of the
+		<command>groupadd</command> tool.
+<example id="smbgrpadd.sh">
+<title>smbgrpadd.sh</title>
+<programlisting>
+#!/bin/bash
+
+# Add the group using normal system groupadd tool.
+groupadd smbtmpgrp00
+
+thegid=`cat /etc/group | grep ^smbtmpgrp00 | cut -d ":" -f3`
+
+# Now change the name to what we want for the MS Windows networking end
+cp /etc/group /etc/group.bak
+cat /etc/group.bak | sed "s/^smbtmpgrp00/$1/g" > /etc/group
+rm /etc/group.bak
+
+# Now return the GID as would normally happen.
+echo $thegid
+exit 0
+</programlisting>
+</example>
+</para>
+
+		<para>
+		The &smb.conf; entry for the above script shown in <link linkend="smbgrpadd">the configuration of
+		&smb.conf; for the add group Script</link> demonstrates how it may be used.
+
+<example id="smbgrpadd">
+<title>Configuration of &smb.conf; for the add group Script</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="add group script">/path_to_tool/smbgrpadd.sh &quot;%g&quot;</smbconfoption>
+</smbconfblock>
+</example>
+		</para>
+
+	</sect2>
+	
+	<sect2>
+	<title>Script to Configure Group Mapping</title>
+
+	<para>
+<indexterm><primary>initGroups.sh</primary></indexterm>
+	In our example we have created a UNIX/Linux group called <literal>ntadmin</literal>.
+	Our script will create the additional groups <literal>Orks</literal>, <literal>Elves</literal>, and <literal>Gnomes</literal>.
+	It is a good idea to save this shell script for later use just in case you ever need to rebuild your mapping database.
+	For the sake of convenience we elect to save this script as a file called <filename>initGroups.sh</filename>.
+	This script is given in <link linkend="set-group-map">intGroups.sh</link>.
+<indexterm><primary>initGroups.sh</primary></indexterm>
+<example id="set-group-map">
+<title>Script to Set Group Mapping</title>
+<programlisting>
+#!/bin/bash
+
+net groupmap add ntgroup="Domain Admins" unixgroup=ntadmin rid=512 type=d
+net groupmap add ntgroup="Domain Users" unixgroup=users rid=513 type=d
+net groupmap add ntgroup="Domain Guests" unixgroup=nobody rid=514 type=d
+
+groupadd Orks
+groupadd Elves
+groupadd Gnomes
+
+net groupmap add ntgroup="Orks"   unixgroup=Orks   type=d
+net groupmap add ntgroup="Elves"  unixgroup=Elves  type=d
+net groupmap add ntgroup="Gnomes" unixgroup=Gnomes type=d
+</programlisting>
+</example>
+	</para>
+
+	<para>
+	Of course it is expected that the administrator will modify this to suit local needs.
+	For information regarding the use of the <command>net groupmap</command> tool please
+	refer to the man page.
+	</para>
+
+	<note><para>
+	Versions of Samba-3 prior to 3.0.23 automatically create default group mapping for the
+	<literal>Domain Admins, Domain Users</literal> and <literal>Domain Guests</literal> Windows
+	groups, but do not map them to UNIX GIDs. This was a cause of administrative confusion and 
+	trouble. Commencing with Samba-3.0.23 this annomaly has been fixed - thus all Windows groups
+	must now be manually and explicitly created and mapped to a valid UNIX GID by the Samba 
+	administrator.
+	</para></note>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+At this time there are many little surprises for the unwary administrator. In a real sense
+it is imperative that every step of automated control scripts be carefully tested
+manually before putting it into active service.
+</para>
+
+	<sect2>
+	<title>Adding Groups Fails</title>
+
+		<para>
+<indexterm><primary>groupadd</primary></indexterm>
+		This is a common problem when the <command>groupadd</command> is called directly
+		by the Samba interface script for the <smbconfoption name="add group script"/> in
+		the &smb.conf; file.
+		</para>
+
+		<para>
+<indexterm><primary>uppercase character</primary></indexterm>
+<indexterm><primary>space character</primary></indexterm>
+		The most common cause of failure is an attempt to add an MS Windows group account
+		that has an uppercase character and/or a space character in it.
+		</para>
+
+		<para>
+<indexterm><primary>groupadd</primary></indexterm>
+		There are three possible workarounds. First, use only group names that comply
+		with the limitations of the UNIX/Linux <command>groupadd</command> system tool.
+		Second, it involves the use of the script mentioned earlier in this chapter, and
+		third is the option is to manually create a UNIX/Linux group account that can substitute
+		for the MS Windows group name, then use the procedure listed above to map that group
+		to the MS Windows group.
+		</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Adding Domain Users to the Workstation Power Users Group</title>
+
+		<para><quote>
+		What must I do to add domain users to the Power Users group?
+		</quote></para>
+
+		<para>
+<indexterm><primary>Domain Users group</primary></indexterm>
+		The Power Users group is a group that is local to each Windows 200x/XP Professional workstation.
+		You cannot add the Domain Users group to the Power Users group automatically, it must be done on
+		each workstation by logging in as the local workstation <emphasis>administrator</emphasis> and
+		then using the following procedure:
+		</para>
+
+		<procedure>
+			<step><para>
+			Click <guimenu>Start -> Control Panel -> Users and Passwords</guimenu>.
+			</para></step>
+
+			<step><para>
+			Click the <guimenuitem>Advanced</guimenuitem> tab.
+			</para></step>
+
+			<step><para>
+			Click the <guibutton>Advanced</guibutton> button.
+			</para></step>
+
+			<step><para>
+			Click <constant>Groups</constant>.
+			</para></step>
+
+			<step><para>
+			Double-click <constant>Power Users</constant>. This will launch the panel to add users or groups
+			to the local machine <constant>Power Users</constant> group.
+			</para></step>
+
+			<step><para>
+			Click the <guibutton>Add</guibutton> button.
+			</para></step>
+
+			<step><para>
+			Select the domain from which the <constant>Domain Users</constant> group is to be added.
+			</para></step>
+
+			<step><para>
+			Double-click the <constant>Domain Users</constant> group.
+			</para></step>
+
+			<step><para>
+			Click the <guibutton>OK</guibutton> button. If a logon box is presented during this process, 
+			please remember to enter the connect as <constant>DOMAIN\UserName</constant>, that is, for the
+			domain <constant>MIDEARTH</constant> and the user <constant>root</constant> enter
+			<constant>MIDEARTH\root</constant>.
+			</para></step>
+		</procedure>
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml b/docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml
new file mode 100644
index 00000000000..1ce81d404e2
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml
@@ -0,0 +1,500 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="SambaHA">
+<chapterinfo>
+	&author.jht;
+	&author.jeremy;
+</chapterinfo>
+
+<title>High Availability</title>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>availability</primary></indexterm>
+<indexterm><primary>intolerance</primary></indexterm>
+<indexterm><primary>vital task</primary></indexterm>
+Network administrators are often concerned about the availability of file and print
+services. Network users are inclined toward intolerance of the services they depend
+on to perform vital task responsibilities.
+</para>
+
+<para>
+A sign in a computer room served to remind staff of their responsibilities. It read:
+</para>
+
+<blockquote>
+<para>
+<indexterm><primary>fail</primary></indexterm>
+<indexterm><primary>managed by humans</primary></indexterm>
+<indexterm><primary>economically wise</primary></indexterm>
+<indexterm><primary>anticipate failure</primary></indexterm>
+All humans fail, in both great and small ways we fail continually. Machines fail too.
+Computers are machines that are managed by humans, the fallout from failure
+can be spectacular. Your responsibility is to deal with failure, to anticipate it
+and to eliminate it as far as is humanly and economically wise to achieve.
+Are your actions part of the problem or part of the solution?
+</para>
+</blockquote>
+
+<para>
+If we are to deal with failure in a planned and productive manner, then first we must
+understand the problem. That is the purpose of this chapter.
+</para>
+
+<para>
+<indexterm><primary>high availability</primary></indexterm>
+<indexterm><primary>CIFS/SMB</primary></indexterm>
+<indexterm><primary>state of knowledge</primary></indexterm>
+Parenthetically, in the following discussion there are seeds of information on how to
+provision a network infrastructure against failure. Our purpose here is not to provide
+a lengthy dissertation on the subject of high availability. Additionally, we have made
+a conscious decision to not provide detailed working examples of high availability
+solutions; instead we present an overview of the issues in the hope that someone will
+rise to the challenge of providing a detailed document that is focused purely on
+presentation of the current state of knowledge and practice in high availability as it
+applies to the deployment of Samba and other CIFS/SMB technologies.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Technical Discussion</title>
+
+<para>
+<indexterm><primary>SambaXP conference</primary></indexterm>
+<indexterm><primary>Germany</primary></indexterm>
+<indexterm><primary>inspired structure</primary></indexterm>
+The following summary was part of a presentation by Jeremy Allison at the SambaXP 2003
+conference that was held at Goettingen, Germany, in April 2003. Material has been added
+from other sources, but it was Jeremy who inspired the structure that follows.
+</para>
+
+	<sect2>
+	<title>The Ultimate Goal</title>
+
+	<para>
+<indexterm><primary>clustering technologies</primary></indexterm>
+<indexterm><primary>affordable power</primary></indexterm>
+<indexterm><primary>unstoppable services</primary></indexterm>
+	All clustering technologies aim to achieve one or more of the following:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>Obtain the maximum affordable computational power.</para></listitem>
+		<listitem><para>Obtain faster program execution.</para></listitem>
+		<listitem><para>Deliver unstoppable services.</para></listitem>
+		<listitem><para>Avert points of failure.</para></listitem>
+		<listitem><para>Exact most effective utilization of resources.</para></listitem>
+	</itemizedlist>
+
+	<para>
+	A clustered file server ideally has the following properties:
+<indexterm><primary>clustered file server</primary></indexterm>
+<indexterm><primary>connect transparently</primary></indexterm>
+<indexterm><primary>transparently reconnected</primary></indexterm>
+<indexterm><primary>distributed file system</primary></indexterm>
+	</para>
+
+	<itemizedlist>
+		<listitem><para>All clients can connect transparently to any server.</para></listitem>
+		<listitem><para>A server can fail and clients are transparently reconnected to another server.</para></listitem>
+		<listitem><para>All servers serve out the same set of files.</para></listitem>
+		<listitem><para>All file changes are immediately seen on all servers.</para>
+			<itemizedlist><listitem><para>Requires a distributed file system.</para></listitem></itemizedlist></listitem>
+		<listitem><para>Infinite ability to scale by adding more servers or disks.</para></listitem>
+	</itemizedlist>
+
+	</sect2>
+
+	<sect2>
+	<title>Why Is This So Hard?</title>
+
+	<para>
+	In short, the problem is one of <emphasis>state</emphasis>.
+	</para>
+
+	<itemizedlist>
+		<listitem>
+			<para>
+<indexterm><primary>state information</primary></indexterm>
+			All TCP/IP connections are dependent on state information.
+			</para>
+			<para>
+<indexterm><primary>TCP failover</primary></indexterm>
+			The TCP connection involves a packet sequence number. This
+			sequence number would need to be dynamically updated on all
+			machines in the cluster to effect seamless TCP failover.
+			</para>
+		</listitem>
+		<listitem>
+			<para>
+<indexterm><primary>CIFS/SMB</primary></indexterm>
+<indexterm><primary>TCP</primary></indexterm>
+			CIFS/SMB (the Windows networking protocols) uses TCP connections.
+			</para>
+			<para>
+			This means that from a basic design perspective, failover is not
+			seriously considered.
+			<itemizedlist>
+				<listitem><para>
+				All current SMB clusters are failover solutions
+				&smbmdash; they rely on the clients to reconnect. They provide server
+				failover, but clients can lose information due to a server failure.
+<indexterm><primary>server failure</primary></indexterm>
+				</para></listitem>
+			</itemizedlist>
+			</para>
+		</listitem>
+		<listitem>
+			<para>
+			Servers keep state information about client connections.
+			<itemizedlist>
+<indexterm><primary>state</primary></indexterm>
+				<listitem><para>CIFS/SMB involves a lot of state.</para></listitem>
+				<listitem><para>Every file open must be compared with other open files
+						to check share modes.</para></listitem>
+			</itemizedlist>
+			</para>
+		</listitem>
+	</itemizedlist>
+
+		<sect3>
+		<title>The Front-End Challenge</title>
+
+		<para>
+<indexterm><primary>cluster servers</primary></indexterm>
+<indexterm><primary>single server</primary></indexterm>
+<indexterm><primary>TCP data streams</primary></indexterm>
+<indexterm><primary>front-end virtual server</primary></indexterm>
+<indexterm><primary>virtual server</primary></indexterm>
+<indexterm><primary>de-multiplex</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+		To make it possible for a cluster of file servers to appear as a single server that has one
+		name and one IP address, the incoming TCP data streams from clients must be processed by the
+		front-end virtual server. This server must de-multiplex the incoming packets at the SMB protocol
+		layer level and then feed the SMB packet to different servers in the cluster.
+		</para>
+
+		<para>
+<indexterm><primary>IPC$ connections</primary></indexterm>
+<indexterm><primary>RPC calls</primary></indexterm>
+		One could split all IPC$ connections and RPC calls to one server to handle printing and user
+		lookup requirements. RPC printing handles are shared between different IPC4 sessions &smbmdash; it is
+		hard to split this across clustered servers!
+		</para>
+
+		<para>
+		Conceptually speaking, all other servers would then provide only file services. This is a simpler
+		problem to concentrate on.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Demultiplexing SMB Requests</title>
+
+		<para>
+<indexterm><primary>SMB requests</primary></indexterm>
+<indexterm><primary>SMB state information</primary></indexterm>
+<indexterm><primary>front-end virtual server</primary></indexterm>
+<indexterm><primary>complicated problem</primary></indexterm>
+		De-multiplexing of SMB requests requires knowledge of SMB state information,
+		all of which must be held by the front-end <emphasis>virtual</emphasis> server.
+		This is a perplexing and complicated problem to solve.
+		</para>
+
+		<para>
+<indexterm><primary>vuid</primary></indexterm>
+<indexterm><primary>tid</primary></indexterm>
+<indexterm><primary>fid</primary></indexterm>
+		Windows XP and later have changed semantics so state information (vuid, tid, fid)
+		must match for a successful operation. This makes things simpler than before and is a
+		positive step forward.
+		</para>
+
+		<para>
+<indexterm><primary>SMB requests</primary></indexterm>
+<indexterm><primary>Terminal Server</primary></indexterm>
+		SMB requests are sent by vuid to their associated server. No code exists today to
+		effect this solution. This problem is conceptually similar to the problem of
+		correctly handling requests from multiple requests from Windows 2000
+		Terminal Server in Samba.
+		</para>
+
+		<para>
+<indexterm><primary>de-multiplexing</primary></indexterm>
+		One possibility is to start by exposing the server pool to clients directly.
+		This could eliminate the de-multiplexing step.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>The Distributed File System Challenge</title>
+
+		<para>
+<indexterm><primary>Distributed File Systems</primary></indexterm>
+		There exists many distributed file systems for UNIX and Linux.
+		</para>
+
+		<para>
+<indexterm><primary>backend</primary></indexterm>
+<indexterm><primary>SMB semantics</primary></indexterm>
+<indexterm><primary>share modes</primary></indexterm>
+<indexterm><primary>locking</primary></indexterm>
+<indexterm><primary>oplock</primary></indexterm>
+<indexterm><primary>distributed file systems</primary></indexterm>
+		Many could be adopted to backend our cluster, so long as awareness of SMB
+		semantics is kept in mind (share modes, locking, and oplock issues in particular).
+		Common free distributed file systems include:
+<indexterm><primary>NFS</primary></indexterm>
+<indexterm><primary>AFS</primary></indexterm>
+<indexterm><primary>OpenGFS</primary></indexterm>
+<indexterm><primary>Lustre</primary></indexterm>
+		</para>
+
+		<itemizedlist>
+			<listitem><para>NFS</para></listitem>
+			<listitem><para>AFS</para></listitem>
+			<listitem><para>OpenGFS</para></listitem>
+			<listitem><para>Lustre</para></listitem>
+		</itemizedlist>
+
+		<para>
+<indexterm><primary>server pool</primary></indexterm>
+		The server pool (cluster) can use any distributed file system backend if all SMB
+		semantics are performed within this pool.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Restrictive Constraints on Distributed File Systems</title>
+
+		<para>
+<indexterm><primary>SMB services</primary></indexterm>
+<indexterm><primary>oplock handling</primary></indexterm>
+<indexterm><primary>server pool</primary></indexterm>
+<indexterm><primary>backend file system pool</primary></indexterm>
+		Where a clustered server provides purely SMB services, oplock handling
+		may be done within the server pool without imposing a need for this to
+		be passed to the backend file system pool.
+		</para>
+
+		<para>
+<indexterm><primary>NFS</primary></indexterm>
+<indexterm><primary>interoperability</primary></indexterm>
+		On the other hand, where the server pool also provides NFS or other file services,
+		it will be essential that the implementation be oplock-aware so it can
+		interoperate with SMB services. This is a significant challenge today. A failure
+		to provide this interoperability will result in a significant loss of performance that will be
+		sorely noted by users of Microsoft Windows clients.
+		</para>
+
+		<para>
+		Last, all state information must be shared across the server pool.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Server Pool Communications</title>
+
+		<para>
+<indexterm><primary>POSIX semantics</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>POSIX locks</primary></indexterm>
+<indexterm><primary>SMB locks</primary></indexterm>
+		Most backend file systems support POSIX file semantics. This makes it difficult
+		to push SMB semantics back into the file system. POSIX locks have different properties
+		and semantics from SMB locks.
+		</para>
+
+		<para>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>tdb</primary></indexterm>
+<indexterm><primary>Clustered smbds</primary></indexterm>
+		All <command>smbd</command> processes in the server pool must of necessity communicate
+		very quickly. For this, the current <parameter>tdb</parameter> file structure that Samba
+		uses is not suitable for use across a network. Clustered <command>smbd</command>s must use something else.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Server Pool Communications Demands</title>
+
+		<para>
+		High-speed interserver communications in the server pool is a design prerequisite
+		for a fully functional system. Possibilities for this include:
+		</para>
+
+		<itemizedlist>
+<indexterm><primary>Myrinet</primary></indexterm>
+<indexterm><primary>scalable coherent interface</primary><see>SCI</see></indexterm>
+			<listitem><para>
+			Proprietary shared memory bus (example: Myrinet or SCI [scalable coherent interface]).
+			These are high-cost items.
+			</para></listitem>
+		
+			<listitem><para>
+			Gigabit Ethernet (now quite affordable).
+			</para></listitem>
+		
+			<listitem><para>
+			Raw Ethernet framing (to bypass TCP and UDP overheads).
+			</para></listitem>
+		</itemizedlist>
+
+		<para>
+		We have yet to identify metrics for  performance demands to enable this to happen
+		effectively.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Required Modifications to Samba</title>
+
+		<para>
+		Samba needs to be significantly modified to work with a high-speed server interconnect
+		system to permit transparent failover clustering.
+		</para>
+
+		<para>
+		Particular functions inside Samba that will be affected include:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			The locking database, oplock notifications,
+			and the share mode database.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>failure semantics</primary></indexterm>
+<indexterm><primary>oplock messages</primary></indexterm>
+			Failure semantics need to be defined. Samba behaves the same way as Windows.
+			When oplock messages fail, a file open request is allowed, but this is 
+			potentially dangerous in a clustered environment. So how should interserver
+			pool failure semantics function, and how should such functionality be implemented?
+			</para></listitem>
+
+			<listitem><para>
+			Should this be implemented using a point-to-point lock manager, or can this
+			be done using multicast techniques?
+			</para></listitem>
+
+		</itemizedlist>
+
+		</sect3>
+	</sect2>
+
+	<sect2>
+	<title>A Simple Solution</title>
+
+	<para>
+<indexterm><primary>failover servers</primary></indexterm>
+<indexterm><primary>exported file system</primary></indexterm>
+<indexterm><primary>distributed locking protocol</primary></indexterm>
+	Allowing failover servers to handle different functions within the exported file system
+	removes the problem of requiring a distributed locking protocol.
+	</para>
+
+	<para>
+<indexterm><primary>high-speed server interconnect</primary></indexterm>
+<indexterm><primary>complex file name space</primary></indexterm>
+	If only one server is active in a pair, the need for high-speed server interconnect is avoided.
+	This allows the use of existing high-availability solutions, instead of inventing a new one.
+	This simpler solution comes at a price &smbmdash; the cost of which is the need to manage a more
+	complex file name space. Since there is now not a single file system, administrators
+	must remember where all services are located &smbmdash; a complexity not easily dealt with.
+	</para>
+
+	<para>
+<indexterm><primary>virtual server</primary></indexterm>
+	The <emphasis>virtual server</emphasis> is still needed to redirect requests to backend
+	servers. Backend file space integrity is the responsibility of the administrator.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>High-Availability Server Products</title>
+
+	<para>
+<indexterm><primary>resource failover</primary></indexterm>
+<indexterm><primary>high-availability services</primary></indexterm>
+<indexterm><primary>dedicated heartbeat</primary></indexterm>
+<indexterm><primary>LAN</primary></indexterm>
+<indexterm><primary>failover process</primary></indexterm>
+	Failover servers must communicate in order to handle resource failover. This is essential
+	for high-availability services. The use of a dedicated heartbeat is a common technique to
+	introduce some intelligence into the failover process. This is often done over a dedicated
+	link (LAN or serial).
+	</para>
+
+	<para>
+<indexterm><primary>SCSI</primary></indexterm>
+<indexterm><primary>Red Hat Cluster Manager</primary></indexterm>
+<indexterm><primary>Microsoft Wolfpack</primary></indexterm>
+<indexterm><primary>Fiber Channel</primary></indexterm>
+<indexterm><primary>failover communication</primary></indexterm>
+	Many failover solutions (like Red Hat Cluster Manager and Microsoft Wolfpack)
+	can use a shared SCSI of Fiber Channel disk storage array for failover communication.
+	Information regarding Red Hat high availability solutions for Samba may be obtained from
+	<ulink url="http://www.redhat.com/docs/manuals/enterprise/RHEL-AS-2.1-Manual/cluster-manager/s1-service-samba.html">www.redhat.com</ulink>.
+	</para>
+
+	<para>
+<indexterm><primary>Linux High Availability project</primary></indexterm>
+	The Linux High Availability project is a resource worthy of consultation if your desire is
+	to build a highly available Samba file server solution. Please consult the home page at
+	<ulink url="http://www.linux-ha.org/">www.linux-ha.org/</ulink>.
+	</para>
+
+	<para>
+<indexterm><primary>backend failures</primary></indexterm>
+<indexterm><primary>continuity of service</primary></indexterm>
+	Front-end server complexity remains a challenge for high availability because it must deal
+	gracefully with backend failures, while at the same time providing continuity of service
+	to all network clients.
+	</para>
+	
+	</sect2>
+
+	<sect2>
+	<title>MS-DFS: The Poor Man's Cluster</title>
+
+	<para>
+<indexterm><primary>MS-DFS</primary></indexterm>
+<indexterm><primary>DFS</primary><see>MS-DFS, Distributed File Systems</see></indexterm>
+	MS-DFS links can be used to redirect clients to disparate backend servers. This pushes
+	complexity back to the network client, something already included by Microsoft.
+	MS-DFS creates the illusion of a simple, continuous file system name space that works even
+	at the file level.
+	</para>
+
+	<para>
+	Above all, at the cost of complexity of management, a distributed system (pseudo-cluster) can
+	be created using existing Samba functionality.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Conclusions</title>
+
+	<itemizedlist>
+		<listitem><para>Transparent SMB clustering is hard to do!</para></listitem>
+		<listitem><para>Client failover is the best we can do today.</para></listitem>
+		<listitem><para>Much more work is needed before a practical and manageable high-availability transparent cluster solution will be possible.</para></listitem>
+		<listitem><para>MS-DFS can be used to create the illusion of a single transparent cluster.</para></listitem>
+	</itemizedlist>
+
+	</sect2>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml b/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml
new file mode 100644
index 00000000000..2ff794939c8
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml
@@ -0,0 +1,1124 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="idmapper">
+<chapterinfo>
+	&author.jht;
+</chapterinfo>
+
+<title>Identity Mapping (IDMAP)</title>
+
+<para>
+<indexterm><primary>Windows</primary></indexterm>
+<indexterm><primary>interoperability</primary></indexterm>
+<indexterm><primary>IDMAP</primary></indexterm>
+<indexterm><primary>Windows Security Identifiers</primary><see>SID</see></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+The Microsoft Windows operating system has a number of features that impose specific challenges
+to interoperability with the operating systems on which Samba is implemented. This chapter deals
+explicitly with the mechanisms Samba-3 (version 3.0.8 and later) uses to overcome one of the
+key challenges in the integration of Samba servers into an MS Windows networking environment.
+This chapter deals with identity mapping (IDMAP) of Windows security identifiers (SIDs)
+to UNIX UIDs and GIDs.
+</para>
+
+<para>
+To ensure sufficient coverage, each possible Samba deployment type is discussed.
+This is followed by an overview of how the IDMAP facility may be implemented.
+</para>
+
+<para>
+<indexterm><primary>network client</primary></indexterm>
+<indexterm><primary>IDMAP</primary></indexterm>
+<indexterm><primary>IDMAP infrastructure</primary></indexterm>
+<indexterm><primary>default behavior</primary></indexterm>
+The IDMAP facility is of concern where more than one Samba server (or Samba network client)
+is installed in a domain. Where there is a single Samba server, do not be too concerned regarding
+the IDMAP infrastructure &smbmdash; the default behavior of Samba is nearly always sufficient.
+Where mulitple Samba servers are used it is often necessary to move data off one server and onto
+another, and that is where the fun begins!
+</para>
+
+<para>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>nss_ldap</primary></indexterm>
+<indexterm><primary>NT4 domain members</primary></indexterm>
+<indexterm><primary>ADS domain members</primary></indexterm>
+<indexterm><primary>security name-space</primary></indexterm>
+Where user and group account information is stored in an LDAP directory every server can have the same
+consistent UID and GID for users and groups. This is achieved using NSS and the nss_ldap tool. Samba
+can be configured to use only local accounts, in which case the scope of the IDMAP problem is somewhat
+reduced. This works reasonably well if the servers belong to a single domain, and interdomain trusts
+are not needed. On the other hand, if the Samba servers are NT4 domain members, or ADS  domain members,
+or if there is a need to keep the security name-space separate (i.e., the user
+<literal>DOMINICUS\FJones</literal> must not be given access to the account resources of the user 
+<literal>FRANCISCUS\FJones</literal><footnote>Samba local account mode results in both
+<literal>DOMINICUS\FJones</literal> and <literal>FRANCISCUS\FJones</literal> mapping to the UNIX user
+<literal>FJones</literal>.</footnote> free from inadvertent cross-over, close attention should be given
+to the way that the IDMAP facility is configured.
+</para>
+
+<para>
+<indexterm><primary>IDMAP</primary></indexterm>
+<indexterm><primary>domain access</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>one domain</primary></indexterm>
+The use of IDMAP is important where the Samba server will be accessed by workstations or servers from
+more than one domain, in which case it is important to run winbind so it can handle the resolution (ID mapping)
+of foreign SIDs to local UNIX UIDs and GIDs.
+</para>
+
+<para>
+<indexterm><primary>winbindd</primary></indexterm>
+The use of the IDMAP facility requires the execution of the <command>winbindd</command> upon Samba startup.
+</para>
+
+<sect1>
+<title>Samba Server Deployment Types and IDMAP</title>
+
+<para>
+<indexterm><primary>Server Types</primary></indexterm>
+There are four basic server deployment types, as documented in <link linkend="ServerType">the chapter
+on Server Types and Security Modes</link>.
+</para>
+
+	<sect2>
+	<title>Standalone Samba Server</title>
+
+	<para>
+	<indexterm><primary>stand-alone server</primary></indexterm>
+	<indexterm><primary>Active Directory</primary></indexterm>
+	<indexterm><primary>NT4 Domain</primary></indexterm>
+	A standalone Samba server is an implementation that is not a member of a Windows NT4 domain,
+	a Windows 200X Active Directory domain, or a Samba domain.
+	</para>
+
+	<para>
+	<indexterm><primary>IDMAP</primary></indexterm>
+	<indexterm><primary>identity</primary></indexterm>
+	<indexterm><primary>local user</primary></indexterm>
+	By definition, this means that users and groups will be created and controlled locally, and
+	the identity of a network user must match a local UNIX/Linux user login. The IDMAP facility
+	is therefore of little to no interest, winbind will not be necessary, and the IDMAP facility
+	will not be relevant or of interest.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Domain Member Server or Domain Member Client</title>
+
+	<para>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>NT4</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>Active Directory</primary></indexterm>
+	Samba-3 can act as a Windows NT4 PDC or BDC, thereby providing domain control protocols that
+	are compatible with Windows NT4. Samba-3 file and print sharing protocols are compatible with
+	all versions of MS Windows products. Windows NT4, as with MS Active Directory,
+	extensively makes use of Windows SIDs.
+	</para>
+
+	<para>
+	<indexterm><primary>MS Windows SID</primary></indexterm>
+	<indexterm><primary>UID</primary></indexterm>
+	<indexterm><primary>GID</primary></indexterm>
+	Samba-3 domain member servers and clients must interact correctly with MS Windows SIDs. Incoming
+	Windows SIDs must be translated to local UNIX UIDs and GIDs. Outgoing information from the Samba
+	server must provide to MS Windows clients and servers appropriate SIDs.
+	</para>
+
+	<para>
+	<indexterm><primary>ADS</primary></indexterm>
+	<indexterm><primary>winbind</primary></indexterm>
+	A Samba member of a Windows networking domain (NT4-style or ADS) can be configured to handle 
+	identity mapping in a variety of ways. The mechanism it uses depends on whether or not
+	the <command>winbindd</command> daemon is used and how the winbind functionality is configured.
+	The configuration options are briefly described here:
+	</para>
+
+	<variablelist>
+		<varlistentry><term>Winbind is not used; users and groups are local: </term>
+			<listitem>
+				<para>
+				<indexterm><primary>winbindd</primary></indexterm>
+				<indexterm><primary>smbd</primary></indexterm>
+				<indexterm><primary>network traffic</primary></indexterm>
+				<indexterm><primary>LoginID</primary></indexterm>
+				<indexterm><primary>account name</primary></indexterm>
+				<indexterm><primary>getpwnam</primary></indexterm>
+				<indexterm><primary>NSS</primary></indexterm>
+				<indexterm><primary>local users</primary></indexterm>
+				<indexterm><primary>local groups</primary></indexterm>
+				<indexterm><primary>/etc/passwd</primary></indexterm>
+				<indexterm><primary>/etc/group</primary></indexterm>
+				Where <command>winbindd</command> is not used Samba (<command>smbd</command>)
+				uses the underlying UNIX/Linux mechanisms to resolve the identity of incoming
+				network traffic. This is done using the LoginID (account name) in the
+				session setup request and passing it to the getpwnam() system function call.
+				This call is implemented using the name service switch (NSS) mechanism on
+				modern UNIX/Linux systems. By saying "users and groups are local,"
+				we are implying that they are stored only on the local system, in the
+				<filename>/etc/passwd</filename> and <filename>/etc/group</filename> respectively.
+				</para>
+
+				<para>
+				<indexterm><primary>SessionSetupAndX</primary></indexterm>
+				<indexterm><primary>/etc/passwd</primary></indexterm>
+				For example, when the user <literal>BERYLIUM\WambatW</literal> tries to open a
+				connection to a Samba server the incoming SessionSetupAndX request will make a 
+				system call to look up the user <literal>WambatW</literal> in the
+				<filename>/etc/passwd</filename> file.
+				</para>
+
+				<para>
+				<indexterm><primary>standalone</primary></indexterm>
+				<indexterm><primary>domain member server</primary></indexterm>
+				<indexterm><primary>NT4</primary></indexterm>
+				<indexterm><primary>ADS</primary></indexterm>
+				<indexterm><primary>PDC</primary></indexterm>
+				<indexterm><primary>smbpasswd</primary></indexterm>
+				<indexterm><primary>tdbsam</primary></indexterm>
+				<indexterm><primary>passdb backend</primary></indexterm>
+				This configuration may be used with standalone Samba servers, domain member
+				servers (NT4 or ADS), and for a PDC that uses either an smbpasswd
+				or a tdbsam-based Samba passdb backend.
+				</para>
+			</listitem>
+		</varlistentry>
+	
+		<varlistentry><term>Winbind is not used; users and groups resolved via NSS: </term>
+			<listitem>
+				<para>
+				<indexterm><primary>user accounts</primary></indexterm>
+				<indexterm><primary>group accounts</primary></indexterm>
+				<indexterm><primary>local accounts</primary></indexterm>
+				<indexterm><primary>repository</primary></indexterm>
+				<indexterm><primary>NIS</primary></indexterm>
+				<indexterm><primary>LDAP</primary></indexterm>
+				In this situation user and group accounts are treated as if they are local
+				accounts. The only way in which this differs from having local accounts is
+				that the accounts are stored in a repository that can be shared. In practice
+				this means that they will reside in either an NIS-type database or else in LDAP.
+				</para>
+
+				<para>
+				<indexterm><primary>standalone</primary></indexterm>
+				<indexterm><primary>domain member server</primary></indexterm>
+				<indexterm><primary>NT4</primary></indexterm>
+				<indexterm><primary>ADS</primary></indexterm>
+				<indexterm><primary>PDC</primary></indexterm>
+				<indexterm><primary>smbpasswd</primary></indexterm>
+				<indexterm><primary>tdbsam</primary></indexterm>
+				This configuration may be used with standalone Samba servers, domain member
+				servers (NT4 or ADS), and for a PDC that uses either an smbpasswd
+				or a tdbsam-based Samba passdb backend.
+				</para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry><term>Winbind/NSS with the default local IDMAP table: </term>
+			<listitem>
+				<para>
+				<indexterm><primary>NT4 domain</primary></indexterm>
+				<indexterm><primary>ADS domain</primary></indexterm>
+				<indexterm><primary>winbind</primary></indexterm>
+				<indexterm><primary>domain control</primary></indexterm>
+				There are many sites that require only a simple Samba server or a single Samba
+				server that is a member of a Windows NT4 domain or an ADS domain. A typical example
+				is an appliance like file server on which no local accounts are configured and
+				winbind is used to obtain account credentials from the domain controllers for the
+				domain. The domain control can be provided by Samba-3, MS Windows NT4, or MS Windows
+				Active Directory.
+				</para>
+
+				<para>
+				<indexterm><primary>UID numbers</primary></indexterm>
+				<indexterm><primary>GID numbers</primary></indexterm>
+				<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+				<indexterm><primary>winbind</primary></indexterm>
+				<indexterm><primary>SID</primary></indexterm>
+				Winbind is a great convenience in this situation. All that is needed is a range of
+				UID numbers and GID numbers that can be defined in the &smb.conf; file. The
+				<filename>/etc/nsswitch.conf</filename> file is configured to use <command>winbind</command>,
+				which does all the difficult work of mapping incoming SIDs to appropriate UIDs and GIDs.
+				The SIDs are allocated a UID/GID in the order in which winbind receives them.
+				</para>
+
+				<para>
+				<indexterm><primary>UID</primary></indexterm>
+				<indexterm><primary>GID</primary></indexterm>
+				<indexterm><primary>IDMAP</primary></indexterm>
+				<indexterm><primary>corrupted file</primary></indexterm>
+				This configuration is not convenient or practical in sites that have more than one
+				Samba server and that require the same UID or GID for the same user or group across
+				all servers. One of the hazards of this method is that in the event that the winbind
+				IDMAP file becomes corrupted or lost, the repaired or rebuilt IDMAP file may allocate
+				UIDs and GIDs to different users and groups from what was there previously with the
+				result that MS Windows files that are stored on the Samba server may now not belong to
+				the rightful owners.
+				</para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry><term>Winbind/NSS uses RID based IDMAP: </term>
+			<listitem>
+				<para>
+				<indexterm><primary>RID</primary></indexterm>
+				<indexterm><primary>idmap_rid</primary></indexterm>
+				<indexterm><primary>ADS</primary></indexterm>
+				<indexterm><primary>LDAP</primary></indexterm>
+				The IDMAP_RID facility is new to Samba version 3.0.8. It was added to make life easier
+				for a number of sites that are committed to use of MS ADS, that do not apply
+				an ADS schema extension, and that do not have an installed an LDAP directory server just for
+				the purpose of maintaining an IDMAP table. If you have a single ADS domain (not a forest of
+				domains, and not multiple domain trees) and you want a simple cookie-cutter solution to the
+				IDMAP table problem, then IDMAP_RID is an obvious choice.
+				</para>
+
+				<para>
+				<indexterm><primary>idmap_rid</primary></indexterm>
+				<indexterm><primary>idmap uid</primary></indexterm>
+				<indexterm><primary>idmap gid</primary></indexterm>
+				<indexterm><primary>RID</primary></indexterm>
+				<indexterm><primary>SID</primary></indexterm>
+				<indexterm><primary>UID</primary></indexterm>
+				<indexterm><primary>idmap backend</primary></indexterm>
+				<indexterm><primary>automatic mapping</primary></indexterm>
+				This facility requires the allocation of the <parameter>idmap uid</parameter> and the
+				<parameter>idmap gid</parameter> ranges, and within the <parameter>idmap uid</parameter>
+				it is possible to allocate a subset of this range for automatic mapping of the relative
+				identifier (RID) portion of the SID directly to the base of the UID plus the RID value.
+				For example, if the <parameter>idmap uid</parameter> range is <constant>1000-100000000</constant>
+				and the <parameter>idmap backend = idmap_rid:DOMAIN_NAME=1000-50000000</parameter>, and
+				a SID is encountered that has the value <constant>S-1-5-21-34567898-12529001-32973135-1234</constant>,
+				the resulting UID will be <constant>1000 + 1234 = 2234</constant>.
+				</para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry><term>Winbind with an NSS/LDAP backend-based IDMAP facility: </term>
+			<listitem>
+				<para>
+				<indexterm><primary>Domain Member</primary></indexterm>
+				<indexterm><primary>winbind</primary></indexterm>
+				<indexterm><primary>SID</primary></indexterm>
+				<indexterm><primary>UID</primary></indexterm>
+				<indexterm><primary>GID</primary></indexterm>
+				<indexterm><primary>idmap gid</primary></indexterm>
+				<indexterm><primary>idmap uid</primary></indexterm>
+				<indexterm><primary>LDAP</primary></indexterm>
+				In this configuration <command>winbind</command> resolved SIDs to UIDs and GIDs from
+				the <parameter>idmap uid</parameter> and <parameter>idmap gid</parameter> ranges specified
+				in the &smb.conf; file, but instead of using a local winbind IDMAP table, it is stored
+				in an LDAP directory so that all domain member machines (clients and servers) can share
+				a common IDMAP table.
+				</para>
+
+				<para>
+				<indexterm><primary>idmap backend</primary></indexterm>
+				<indexterm><primary>LDAP server</primary></indexterm>
+				<indexterm><primary>LDAP redirects</primary></indexterm>
+				It is important that all LDAP IDMAP clients use only the master LDAP server because the
+				<parameter>idmap backend</parameter> facility in the &smb.conf; file does not correctly
+				handle LDAP redirects.
+				</para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry><term>Winbind with NSS to resolve UNIX/Linux user and group IDs: </term>
+			<listitem>
+				<para>
+				The use of LDAP as the passdb backend is a smart solution for PDC, BDC, and
+				domain member servers. It is a neat method for assuring that UIDs, GIDs, and the matching
+				SIDs are consistent across all servers.
+				</para>
+
+				<para>
+				<indexterm><primary>LDAP</primary></indexterm>
+				<indexterm><primary>PADL</primary></indexterm>
+				The use of the LDAP-based passdb backend requires use of the PADL nss_ldap utility or
+				an equivalent. In this situation winbind is used to handle foreign SIDs, that is, SIDs from
+				standalone Windows clients (i.e., not a member of our domain) as well as SIDs from 
+				another domain. The foreign UID/GID is mapped from allocated ranges (idmap uid and idmap gid)
+				in precisely the same manner as when using winbind with a local IDMAP table.
+				</para>
+
+				<para>
+				<indexterm><primary>nss_ldap</primary></indexterm>
+				<indexterm><primary>AD4UNIX</primary></indexterm>
+				<indexterm><primary>MMC</primary></indexterm>
+				The nss_ldap tool set can be used to access UIDs and GIDs via LDAP as well as via Active
+				Directory. In order to use Active Directory, it is necessary to modify the ADS schema by
+				installing either the AD4UNIX schema extension or using the Microsoft Services for UNIX
+				version 3.5 or later to extend the ADS schema so it maintains UNIX account credentials.
+				Where the ADS schema is extended, a Microsoft Management Console (MMC) snap-in is also
+				installed to permit the UNIX credentials to be set and managed from the ADS User and Computer
+				Management tool. Each account must be separately UNIX-enabled before the UID and GID data can
+				be used by Samba.
+				</para>
+			</listitem>
+		</varlistentry>
+
+	</variablelist>
+
+	</sect2>
+
+	<sect2>
+	<title>Primary Domain Controller</title>
+
+	<para>
+	<indexterm><primary>domain security</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>RID</primary></indexterm>
+	<indexterm><primary>algorithmic mapping</primary></indexterm>
+	Microsoft Windows domain security systems generate the user and group SID as part
+	of the process of creation of an account. Windows does not have a concept of the UNIX UID or a GID; rather,
+	it has its own type of security descriptor. When Samba is used as a domain controller, it provides a method
+	of producing a unique SID for each user and group. Samba generates a machine and a domain SID to which it
+	adds an RID that is calculated algorithmically from a base value that can be specified
+	in the &smb.conf; file, plus twice (2x) the UID or GID. This method is called <quote>algorithmic mapping</quote>.
+	</para>
+
+	<para>
+	<indexterm><primary>RID base</primary></indexterm>
+	For example, if a user has a UID of 4321, and the algorithmic RID base has a value of 1000, the RID will
+	be <literal>1000 + (2 x 4321) = 9642</literal>. Thus, if the domain SID is
+	<literal>S-1-5-21-89238497-92787123-12341112</literal>, the resulting SID is
+	<literal>S-1-5-21-89238497-92787123-12341112-9642</literal>.
+	</para>
+
+	<para>
+	<indexterm><primary>on-the-fly</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	<indexterm><primary>ldapsam</primary></indexterm>
+	The foregoing type of SID is produced by Samba as an automatic function and is either produced on the fly
+	(as is the case when using a <parameter>passdb backend = [tdbsam | smbpasswd]</parameter>), or may be stored
+	as a permanent part of an account in an LDAP-based ldapsam.
+	</para>
+
+	<para>
+	<indexterm><primary>SFU 3.5</primary></indexterm>
+	<indexterm><primary>ADS</primary></indexterm>
+	<indexterm><primary>directory schema</primary></indexterm>
+	<indexterm><primary>account attributes</primary></indexterm>
+	<indexterm><primary>UID</primary></indexterm>
+	<indexterm><primary>GID</primary></indexterm>
+	<indexterm><primary>ADS schema</primary></indexterm>
+	<indexterm><primary>account management</primary></indexterm>
+	<indexterm><primary>MMC</primary></indexterm>
+	ADS uses a directory schema that can be extended to accommodate additional
+	account attributes such as UIDs and GIDs. The installation of Microsoft Service for UNIX 3.5 will expand
+	the normal ADS schema to include UNIX account attributes. These must of course be managed separately
+	through a snap-in module to the normal ADS account management MMC interface.
+	</para>
+
+	<para>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>passdb backend</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>LDAP backend</primary></indexterm>
+	Security identifiers used within a domain must be managed to avoid conflict and to preserve itegrity.
+	In an NT4 domain context, the PDC manages the distribution of all security credentials to the backup
+	domain controllers (BDCs). At this time the only passdb backend for a Samba domain controller that is suitable
+	for such information is an LDAP backend.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Backup Domain Controller</title>
+
+	<para>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>read-only access</primary></indexterm>
+	<indexterm><primary>security credentials</primary></indexterm>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>group account</primary></indexterm>
+	<indexterm><primary>write changes</primary></indexterm>
+	<indexterm><primary>directory</primary></indexterm>
+	BDCs have read-only access to security credentials that are stored in LDAP.
+	Changes in user or group account information are passed by the BDC to the PDC. Only the PDC can write
+	changes to the directory.
+	</para>
+
+	<para>
+	IDMAP information can be written directly to the LDAP server so long as all domain controllers
+	have access to the master (writable) LDAP server. Samba-3 at this time does not handle LDAP redirects
+	in the IDMAP backend. This means that it is is unsafe to use a slave (replicate) LDAP server with
+	the IDMAP facility.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Examples of IDMAP Backend Usage</title>
+
+<para>
+<indexterm><primary>Domain Member Server</primary><see>DMS</see></indexterm>
+<indexterm><primary>Domain Member Client</primary><see>DMC</see></indexterm>
+<indexterm><primary>DMS</primary></indexterm>
+<indexterm><primary>DMC</primary></indexterm>
+<indexterm><primary>winbind</primary></indexterm>
+Anyone who wishes to use <command>winbind</command> will find the following example configurations helpful.
+Remember that in the majority of cases <command>winbind</command> is of primary interest for use with
+domain member servers (DMSs) and domain member clients (DMCs).
+</para>
+
+	<sect2>
+	<title>Default Winbind TDB</title>
+
+	<para>
+	Two common configurations are used:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Networks that have an NT4 PDC (with or without BDCs) or a Samba PDC (with or without BDCs).
+		</para></listitem>
+
+		<listitem><para>
+		Networks that use MS Windows 200x ADS.
+		</para></listitem>
+	</itemizedlist>
+
+	<sect3>
+	<title>NT4-Style Domains (Includes Samba Domains)</title>
+
+	<para>
+	<link linkend="idmapnt4dms">NT4 Domain Member Server smb.con</link> is a simple example of an NT4 DMS
+	&smb.conf; file that shows only the global section.
+	</para>
+
+<example id="idmapnt4dms">
+<title>NT4 Domain Member Server smb.conf</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">MEGANET2</smbconfoption>
+<smbconfoption name="security">DOMAIN</smbconfoption>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+<smbconfoption name="template primary group">"Domain Users"</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+</smbconfblock>
+</example>
+
+	<para>
+	<indexterm><primary>winbind</primary></indexterm>
+	<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+	The use of <command>winbind</command> requires configuration of NSS. Edit the <filename>/etc/nsswitch.conf</filename>
+	so it includes the following entries:
+<screen>
+...
+passwd: files winbind
+shadow: files winbind
+group:  files winbind
+...
+hosts:  files [dns] wins
+...
+</screen>
+	The use of DNS in the hosts entry should be made only if DNS is used on site.
+	</para>
+
+	<para>
+	The creation of the DMS requires the following steps:
+	</para>
+
+	<procedure>
+		<step><para>
+		Create or install an &smb.conf; file with the above configuration.
+		</para></step>
+
+		<step><para>
+		Execute:
+<screen>
+&rootprompt; net rpc join -UAdministrator%password
+Joined domain MEGANET2.
+</screen>
+	<indexterm><primary>join</primary></indexterm>
+	The success of the join can be confirmed with the following command:
+<screen>
+&rootprompt; net rpc testjoin
+Join to 'MIDEARTH' is OK
+</screen>
+		A failed join would report an error message like the following:
+		<indexterm><primary>failed join</primary></indexterm>
+<screen>
+&rootprompt; net rpc testjoin
+[2004/11/05 16:34:12, 0] utils/net_rpc_join.c:net_rpc_join_ok(66)
+Join to domain 'MEGANET2' is not valid
+</screen>
+		</para></step>
+
+		<step><para>
+		<indexterm><primary>nmbd</primary></indexterm>
+		<indexterm><primary>winbind</primary></indexterm>
+		<indexterm><primary>smbd</primary></indexterm>
+		Start the <command>nmbd, winbind,</command> and <command>smbd</command> daemons in the order shown.
+		</para></step>
+	</procedure>
+
+	</sect3>
+
+	<sect3>
+	<title>ADS Domains</title>
+
+	<para>
+	<indexterm><primary>domain join</primary></indexterm>
+	<indexterm><primary>ADS domain</primary></indexterm>
+	The procedure for joining an ADS domain is similar to the NT4 domain join, except the &smb.conf; file
+	will have the contents shown in <link linkend="idmapadsdms">ADS Domain Member Server smb.conf</link>
+	</para>
+
+<example id="idmapadsdms">
+<title>ADS Domain Member Server smb.conf</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">BUTTERNET</smbconfoption>
+<smbconfoption name="netbios name">GARGOYLE</smbconfoption>
+<smbconfoption name="realm">BUTTERNET.BIZ</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+<smbconfoption name="idmap uid">500-10000000</smbconfoption>
+<smbconfoption name="idmap gid">500-10000000</smbconfoption>
+<smbconfoption name="winbind use default domain">Yes</smbconfoption>
+<smbconfoption name="winbind nested groups">Yes</smbconfoption>
+<smbconfoption name="printer admin">"BUTTERNET\Domain Admins"</smbconfoption>
+</smbconfblock>
+</example>
+
+	<para>
+	<indexterm><primary>KRB</primary></indexterm>
+	<indexterm><primary>kerberos</primary></indexterm>
+	<indexterm><primary>/etc/krb5.conf</primary></indexterm>
+	<indexterm><primary>MIT</primary></indexterm>
+	<indexterm><primary>MIT kerberos</primary></indexterm>
+	<indexterm><primary>Heimdal</primary></indexterm>
+	<indexterm><primary>Heimdal kerberos</primary></indexterm>
+	ADS DMS operation requires use of kerberos (KRB). For this to work, the <filename>krb5.conf</filename>
+	must be configured. The exact requirements depends on which version of MIT or Heimdal Kerberos is being
+	used. It is sound advice to use only the latest version, which at this time are MIT Kerberos version
+	1.3.5 and Heimdal 0.61.
+	</para>
+
+	<para>
+	The creation of the DMS requires the following steps:
+	</para>
+
+	<procedure>
+		<step><para>
+		Create or install an &smb.conf; file with the above configuration.
+		</para></step>
+
+		<step><para>
+		Edit the <filename>/etc/nsswitch.conf</filename> file as shown above.
+		</para></step>
+
+		<step><para>
+		Execute:
+		<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
+<screen>
+&rootprompt; net ads join -UAdministrator%password
+Joined domain BUTTERNET.
+</screen>
+	The success or failure of the join can be confirmed with the following command:
+<screen>
+&rootprompt; net ads testjoin
+Using short domain name -- BUTTERNET
+Joined 'GARGOYLE' to realm 'BUTTERNET.BIZ'
+</screen>
+	</para>
+
+	<para>
+	An invalid or failed join can be detected by executing:
+<screen>
+&rootprompt; net ads testjoin
+GARGOYLE$@'s password:
+[2004/11/05 16:53:03, 0] utils/net_ads.c:ads_startup(186)
+  ads_connect: No results returned
+Join to domain is not valid
+</screen>
+		<indexterm><primary>error message</primary></indexterm>
+		<indexterm><primary>failure</primary></indexterm>
+		<indexterm><primary>log level</primary></indexterm>
+		<indexterm><primary>identify</primary></indexterm>
+		The specific error message may differ from the above because it depends on the type of failure that
+		may have occurred. Increase the <parameter>log level</parameter> to 10, repeat the test,
+		and then examine the log files produced to identify the nature of the failure.
+		</para></step>
+
+		<step><para>
+		Start the <command>nmbd</command>, <command>winbind</command>, and <command>smbd</command> daemons in the order shown.
+		</para></step>
+
+	</procedure>
+
+	</sect3>
+	</sect2>
+
+	<sect2>
+	<title>IDMAP_RID with Winbind</title>
+
+	<para>
+	<indexterm><primary>idmap_rid</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>RID</primary></indexterm>
+	<indexterm><primary>IDMAP</primary></indexterm>
+	The <command>idmap_rid</command> facility is a new tool that, unlike native winbind, creates a
+	predictable mapping of MS Windows SIDs to UNIX UIDs and GIDs. The key benefit of this method
+	of implementing the Samba IDMAP facility is that it eliminates the need to store the IDMAP data
+	in a central place. The downside is that it can be used only within a single ADS domain and
+	is not compatible with trusted domain implementations.
+	</para>
+
+	<para>
+	<indexterm><primary>SID</primary></indexterm>
+	<indexterm><primary>allow trusted domains</primary></indexterm>
+	<indexterm><primary>idmap uid</primary></indexterm>
+	<indexterm><primary>idmap gid</primary></indexterm>
+	This alternate method of SID to UID/GID  mapping can be achieved using the idmap_rid
+        plug-in. This plug-in uses the RID of the user SID to derive the UID and GID by adding the
+        RID to a base value specified. This utility requires that the parameter
+        <quote>allow trusted domains = No</quote> be specified, as it is not compatible
+        with multiple domain environments. The <parameter>idmap uid</parameter> and 
+	<parameter>idmap gid</parameter> ranges must be specified.
+	</para>
+
+	<para>
+	<indexterm><primary>idmap_rid</primary></indexterm>
+	<indexterm><primary>realm</primary></indexterm>
+	The idmap_rid facility can be used both for NT4/Samba-style domains and Active Directory.
+	To use this with an NT4 domain, do not include the <parameter>realm</parameter> parameter; additionally, the
+	method used to join the domain uses the <constant>net rpc join</constant> process.
+	</para>
+
+	<para>
+	An example &smb.conf; file for and ADS domain environment is shown in <link linkend="idmapadsridDMS">ADS
+	Domain Member smb.conf using idmap_rid</link>.
+	</para>
+
+<example id="idmapadsridDMS">
+<title>ADS Domain Member smb.conf using idmap_rid</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">KPAK</smbconfoption>
+<smbconfoption name="netbios name">BIGJOE</smbconfoption>
+<smbconfoption name="realm">CORP.KPAK.COM</smbconfoption>
+<smbconfoption name="server string">Office Server</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+<smbconfoption name="allow trusted domains">No</smbconfoption>
+<smbconfoption name="idmap backend">idmap_rid:KPAK=500-100000000</smbconfoption>
+<smbconfoption name="idmap uid">500-100000000</smbconfoption>
+<smbconfoption name="idmap gid">500-100000000</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+<smbconfoption name="winbind use default domain">Yes</smbconfoption>
+<smbconfoption name="winbind enum users">No</smbconfoption>
+<smbconfoption name="winbind enum groups">No</smbconfoption>
+<smbconfoption name="winbind nested groups">Yes</smbconfoption>
+<smbconfoption name="printer admin">"Domain Admins"</smbconfoption>
+</smbconfblock>
+</example>
+
+	<para>
+	<indexterm><primary>large domain</primary></indexterm>
+	<indexterm><primary>Active Directory</primary></indexterm>
+	<indexterm><primary>response</primary></indexterm>
+	<indexterm><primary>getent</primary></indexterm>
+	In a large domain with many users it is imperative to disable enumeration of users and groups.
+	For example, at a site that has 22,000 users in Active Directory the winbind-based user and
+	group resolution is unavailable for nearly 12 minutes following first startup of 
+	<command>winbind</command>. Disabling enumeration resulted in instantaneous response.
+	The disabling of user and group enumeration means that it will not be possible to list users
+	or groups using the <command>getent passwd</command> and <command>getent group</command>
+	commands. It will be possible to perform the lookup for individual users, as shown in the following procedure.
+	</para>
+
+	<para>
+	<indexterm><primary>NSS</primary></indexterm>
+	<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+	The use of this tool requires configuration of NSS as per the native use of winbind. Edit the
+	<filename>/etc/nsswitch.conf</filename> so it has the following parameters:
+<screen>
+...
+passwd: files winbind
+shadow: files winbind
+group:  files winbind
+...
+hosts:  files wins
+...
+</screen>
+	</para>
+
+	<para>
+	The following procedure can use the idmap_rid facility:
+	</para>
+
+	<procedure>
+		<step><para>
+		Create or install an &smb.conf; file with the above configuration.
+		</para></step>
+
+		<step><para>
+		Edit the <filename>/etc/nsswitch.conf</filename> file as shown above.
+		</para></step>
+
+		<step><para>
+		Execute:
+<screen>
+&rootprompt; net ads join -UAdministrator%password
+Using short domain name -- KPAK
+Joined 'BIGJOE' to realm 'CORP.KPAK.COM'
+</screen>
+		</para>
+
+		<para>
+		<indexterm><primary>failed join</primary></indexterm>
+		An invalid or failed join can be detected by executing:
+<screen>
+&rootprompt; net ads testjoin
+BIGJOE$@'s password:
+[2004/11/05 16:53:03, 0] utils/net_ads.c:ads_startup(186)
+  ads_connect: No results returned
+Join to domain is not valid
+</screen>
+		The specific error message may differ from the above because it depends on the type of failure that
+		may have occurred. Increase the <parameter>log level</parameter> to 10, repeat the test,
+		and then examine the log files produced to identify the nature of the failure.
+		</para></step>
+
+		<step><para>
+		Start the <command>nmbd</command>, <command>winbind</command>, and <command>smbd</command> daemons in the order shown.
+		</para></step>
+
+		<step><para>
+		Validate the operation of this configuration by executing:
+		<indexterm><primary></primary></indexterm>
+<screen>
+&rootprompt; getent passwd administrator
+administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash
+</screen>
+		</para></step>
+	</procedure>
+
+	</sect2>
+
+	<sect2>
+	<title>IDMAP Storage in LDAP Using Winbind</title>
+
+	<para>
+	<indexterm><primary>ADAM</primary></indexterm>
+	<indexterm><primary>ADS</primary></indexterm>
+	The storage of IDMAP information in LDAP can be used with both NT4/Samba-3-style domains and
+	ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any
+	standards-complying LDAP server can be used. It is therefore possible to deploy this IDMAP
+	configuration using the Sun iPlanet LDAP server, Novell eDirectory, Microsoft ADS plus ADAM,
+	and so on.
+	</para>
+
+	<para>
+	An example is for an ADS domain is shown in <link linkend="idmapldapDMS">ADS Domain Member Server using
+	LDAP</link>.
+	</para>
+
+<example id="idmapldapDMS">
+<title>ADS Domain Member Server using LDAP</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">SNOWSHOW</smbconfoption>
+<smbconfoption name="netbios name">GOODELF</smbconfoption>
+<smbconfoption name="realm">SNOWSHOW.COM</smbconfoption>
+<smbconfoption name="server string">Samba Server</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+<smbconfoption name="log level">1 ads:10 auth:10 sam:10 rpc:10</smbconfoption>
+<smbconfoption name="ldap admin dn">cn=Manager,dc=SNOWSHOW,dc=COM</smbconfoption>
+<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+<smbconfoption name="ldap suffix">dc=SNOWSHOW,dc=COM</smbconfoption>
+<smbconfoption name="idmap backend">ldap:ldap://ldap.snowshow.com</smbconfoption>
+<smbconfoption name="idmap uid">150000-550000</smbconfoption>
+<smbconfoption name="idmap gid">150000-550000</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+<smbconfoption name="winbind use default domain">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+	<para>
+	<indexterm><primary>realm</primary></indexterm>
+	In the case of an NT4 or Samba-3-style domain the <parameter>realm</parameter> is not used, and the
+	command used to join the domain is <command>net rpc join</command>. The above example also demonstrates
+	advanced error-reporting techniques that are documented in <link linkend="dbglvl">Reporting Bugs</link>.
+	</para>
+
+	<para>
+	<indexterm><primary>MIT kerberos</primary></indexterm>
+	<indexterm><primary>Heimdal kerberos</primary></indexterm>
+	<indexterm><primary>/etc/krb5.conf</primary></indexterm>
+	Where MIT kerberos is installed (version 1.3.4 or later), edit the <filename>/etc/krb5.conf</filename> 
+	file so it has the following contents:
+<screen>
+[logging]
+ default = FILE:/var/log/krb5libs.log
+ kdc = FILE:/var/log/krb5kdc.log
+ admin_server = FILE:/var/log/kadmind.log
+
+[libdefaults]
+ default_realm = SNOWSHOW.COM
+ dns_lookup_realm = false
+ dns_lookup_kdc = true
+
+[appdefaults]
+ pam = {
+   debug = false
+   ticket_lifetime = 36000
+   renew_lifetime = 36000
+   forwardable = true
+   krb4_convert = false
+ }
+</screen>
+	</para>
+
+	<para>
+	Where Heimdal kerberos is installed, edit the <filename>/etc/krb5.conf</filename>
+        file so it is either empty (i.e., no contents) or it has the following contents:
+<screen>
+[libdefaults]
+        default_realm = SNOWSHOW.COM
+        clockskew = 300
+
+[realms]
+        SNOWSHOW.COM = {
+                kdc = ADSDC.SHOWSHOW.COM
+        }
+        
+[domain_realm]
+        .snowshow.com = SNOWSHOW.COM
+</screen>
+	</para>
+
+	<note><para>
+	Samba cannot use the Heimdal libraries if there is no <filename>/etc/krb5.conf</filename> file.
+	So long as there is an empty file, the Heimdal kerberos libraries will be usable. There is no
+	need to specify any settings because Samba, using the Heimdal libraries, can figure this out automatically.
+	</para></note>
+
+	<para>
+	Edit the NSS control file <filename>/etc/nsswitch.conf</filename> so it has the following entries:
+<screen>
+...
+passwd: files ldap
+shadow: files ldap
+group:  files ldap
+...
+hosts:  files wins
+...
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>PADL</primary></indexterm>
+	<indexterm><primary>/etc/ldap.conf</primary></indexterm>
+	You will need the <ulink url="http://www.padl.com">PADL</ulink> <command>nss_ldap</command> 
+	tool set for this solution. Configure the <filename>/etc/ldap.conf</filename> file so it has 
+	the information needed. The following is an example of a working file:
+<screen>
+host    192.168.2.1
+base    dc=snowshow,dc=com
+binddn  cn=Manager,dc=snowshow,dc=com
+bindpw  not24get
+
+pam_password exop
+
+nss_base_passwd ou=People,dc=snowshow,dc=com?one
+nss_base_shadow ou=People,dc=snowshow,dc=com?one
+nss_base_group  ou=Groups,dc=snowshow,dc=com?one
+ssl     no
+</screen>
+	</para>
+
+	<para>
+	The following procedure may be followed to effect a working configuration:
+	</para>
+
+	<procedure>
+		<step><para>
+		Configure the &smb.conf; file as shown above.
+		</para></step>
+
+		<step><para>
+		Create the <filename>/etc/krb5.conf</filename> file as shown above.
+		</para></step>
+
+		<step><para>
+		Configure the <filename>/etc/nsswitch.conf</filename> file as shown above.
+		</para></step>
+
+		<step><para>
+		Download, build, and install the PADL nss_ldap tool set. Configure the 
+		<filename>/etc/ldap.conf</filename> file as shown above.
+		</para></step>
+
+		<step><para>
+		Configure an LDAP server and initialize the directory with the top-level entries needed by IDMAP,
+		shown in the following LDIF file:
+<screen>
+dn: dc=snowshow,dc=com
+objectClass: dcObject
+objectClass: organization
+dc: snowshow
+o: The Greatest Snow Show in Singapore.
+description: Posix and Samba LDAP Identity Database
+
+dn: cn=Manager,dc=snowshow,dc=com
+objectClass: organizationalRole
+cn: Manager
+description: Directory Manager
+
+dn: ou=Idmap,dc=snowshow,dc=com
+objectClass: organizationalUnit
+ou: idmap
+</screen>
+		</para></step>
+
+		<step><para>
+		Execute the command to join the Samba DMS to the ADS domain as shown here:
+<screen>
+&rootprompt; net ads testjoin
+Using short domain name -- SNOWSHOW
+Joined 'GOODELF' to realm 'SNOWSHOW.COM'
+</screen>
+		</para></step>
+
+		<step><para>
+		Store the LDAP server access password in the Samba <filename>secrets.tdb</filename> file as follows:
+<screen>
+&rootprompt; smbpasswd -w not24get
+</screen>
+		</para></step>
+
+		<step><para>
+		Start the <command>nmbd</command>, <command>winbind</command>, and <command>smbd</command> daemons in the order shown.
+		</para></step>
+	</procedure>
+
+	<para>
+	<indexterm><primary>diagnostic</primary></indexterm>
+	Follow the diagnositic procedures shown earlier in this chapter to identify success or failure of the join.
+	In many cases a failure is indicated by a silent return to the command prompt with no indication of the
+	reason for failure.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</title>
+
+	<para>
+	<indexterm><primary>rfc2307bis</primary></indexterm>
+	<indexterm><primary>schema</primary></indexterm>
+	The use of this method is messy. The information provided in the following is for guidance only
+	and is very definitely not complete. This method does work; it is used in a number of large sites
+	and has an acceptable level of performance.
+	</para>
+
+	<para>
+	An example &smb.conf; file is shown in <link linkend="idmaprfc2307">ADS Domain Member Server using
+RFC2307bis Schema Extension Date via NSS</link>.
+	</para>
+
+<example id="idmaprfc2307">
+<title>ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS</title>
+<smbconfblock>
+<smbconfcomment>Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">BOBBY</smbconfoption>
+<smbconfoption name="realm">BOBBY.COM</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+<smbconfoption name="idmap uid">150000-550000</smbconfoption>
+<smbconfoption name="idmap gid">150000-550000</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+<smbconfoption name="winbind cache time">5</smbconfoption>
+<smbconfoption name="winbind use default domain">Yes</smbconfoption>
+<smbconfoption name="winbind trusted domains only">Yes</smbconfoption>
+<smbconfoption name="winbind nested groups">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+	<para>
+	<indexterm><primary>nss_ldap</primary></indexterm>
+	The DMS must be joined to the domain using the usual procedure. Additionally, it is necessary
+	to build and install the PADL nss_ldap tool set. Be sure to build this tool set with the
+	following:
+<screen>
+./configure --enable-rfc2307bis --enable-schema-mapping
+make install
+</screen> 
+	</para>
+
+	<para>
+	<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+	The following <filename>/etc/nsswitch.conf</filename> file contents are required:
+<screen>
+...
+passwd: files ldap
+shadow: files ldap
+group:  files ldap
+...
+hosts:  files wins
+...
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>/etc/ldap.conf</primary></indexterm>
+	<indexterm><primary>nss_ldap</primary></indexterm>
+	The <filename>/etc/ldap.conf</filename> file must be configured also. Refer to the PADL documentation
+	and source code for nss_ldap to specific instructions.
+	</para>
+
+	<para>
+	The next step involves preparation of the ADS schema. This is briefly discussed in the remaining
+	part of this chapter.
+	</para>
+
+		<sect3>
+		<title>IDMAP, Active Directory, and MS Services for UNIX 3.5</title>
+
+		<para>
+		<indexterm><primary>SFU</primary></indexterm>
+		The Microsoft Windows Service for UNIX (SFU) version 3.5 is available for free 
+		<ulink url="http://www.microsoft.com/windows/sfu/">download</ulink>
+		from the Microsoft Web site. You will need to download this tool and install it following
+		Microsoft instructions.
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>IDMAP, Active Directory and AD4UNIX</title>
+
+		<para>
+		Instructions for obtaining and installing the AD4UNIX tool set can be found from the
+		<ulink url="http://www.geekcomix.com/cgi-bin/classnotes/wiki.pl?LDAP01/An_Alternative_Approach">
+		Geekcomix</ulink> Web site.
+		</para>
+
+		</sect3>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Install.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Install.xml
new file mode 100644
index 00000000000..9894ed2854c
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Install.xml
@@ -0,0 +1,702 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="install">
+<chapterinfo>
+	&author.tridge;
+	&author.jelmer;
+	&author.jht;
+	&author.kauer;
+	&author.danshearer;
+	<!-- Isn't some of this written by others as well? -->
+
+</chapterinfo>
+
+<title>How to Install and Test SAMBA</title>
+
+<sect1>
+	<title>Obtaining and Installing Samba</title>
+
+	<para>
+	<indexterm><primary>packages</primary></indexterm>
+	Binary packages of Samba are included in almost any Linux or UNIX distribution. There are also some
+	packages available at <ulink url="http://samba.org/">the Samba home page</ulink>. Refer to the manual of your
+	operating system for details on installing packages for your specific operating system.
+	</para>
+
+	<para>
+	<indexterm><primary>compile</primary></indexterm>
+	If you need to compile Samba from source, check <link linkend="compiling">How to Compile Samba</link>.
+	</para>
+
+</sect1>
+
+<sect1>
+	<title>Configuring Samba (smb.conf)</title>
+
+	<para>
+	<indexterm><primary>/etc/samba/smb.conf</primary></indexterm>
+	<indexterm><primary>SWAT</primary></indexterm>
+	Samba's configuration is stored in the &smb.conf; file, which usually resides in
+	<filename>/etc/samba/smb.conf</filename> or <filename>/usr/local/samba/lib/smb.conf</filename>. You can either
+	edit this file yourself or do it using one of the many graphical tools that are available, such as the
+	Web-based interface SWAT, that is included with Samba.
+	</para>
+
+	<sect2>
+	<title>Configuration File Syntax</title>
+
+	<para>
+	<indexterm><primary>section name</primary></indexterm>
+	The &smb.conf; file uses the same syntax as the various old <filename>.ini</filename> files in Windows
+	3.1: Each file consists of various sections, which are started by putting the section name between brackets
+	(<literal>[]</literal>) on a new line. Each contains zero or more key/value pairs separated by an equality
+	sign (<literal>=</literal>). The file is just a plaintext file, so you can open and edit it with your favorite
+	editing tool.
+	</para>
+
+	<para>
+	<indexterm><primary>meta-service</primary></indexterm>
+	<indexterm><primary>print</primary><secondary>queue</secondary></indexterm>
+	<indexterm><primary>share</primary></indexterm>
+	<indexterm><primary>spooler.</primary></indexterm>
+	<indexterm><primary>print</primary><secondary>spooler</secondary></indexterm>
+	<indexterm><primary>spool</primary><secondary>directory</secondary></indexterm>
+	Each section in the &smb.conf; file represents either a share or a meta-service on the Samba server. The
+	section <literal>[global]</literal> is special, since it contains settings that apply to the whole Samba
+	server.  Samba supports a number of meta-services, each of which serves its own purpose. For example, the
+	<literal>[homes]</literal> share is a meta-service that causes Samba to provide a personal home share for
+	each user. The <literal>[printers]</literal> share is a meta-service that establishes print queue support
+	and that specifies the location of the intermediate spool directory into which print jobs are received
+	from Windows clients prior to being dispatched to the UNIX/Linux print spooler.
+	</para>
+
+	<para>
+<indexterm><primary>printers</primary></indexterm>
+<indexterm><primary>meta-service</primary></indexterm>
+<indexterm><primary>printcap</primary></indexterm>
+<indexterm><primary>lpstat</primary></indexterm>
+<indexterm><primary>CUPS API</primary></indexterm>
+<indexterm><primary>browseable</primary></indexterm>
+	The <literal>printers</literal> meta-service will cause every printer that is either specified in a
+	<literal>printcap</literal> file, via the <command>lpstat</command>,  or via the CUPS API, to be
+	published as a shared print queue. The <literal>printers</literal> stanza in the &smb.conf; file can
+	be set as not browseable. If it is set to be browseable, then it will be visible as if it is a share.
+	That makes no sense given that this meta-service is responsible only for making UNIX system printers
+	available as Windows print queues. If a <literal>comment</literal> parameter is specified, the value
+	of it will be displayed as part of the printer name in Windows Explorer browse lists.
+	</para>
+
+	<para>
+	<indexterm><primary>stanza</primary></indexterm>
+	Each section of the &smb.conf; file that specifies a share, or a meta-service, is called a stanza.
+	The <literal>global</literal> stanza specifies settings that affect all the other stanzas in the
+	&smb.conf; file. Configuration parameters are documented in the &smb.conf; man page. Some parameters
+	can be used only in the <literal>global</literal> stanza, some only in share or meta-service stanzas,
+	and some can be used globally or just within a share or meta-service stanza.
+	</para>
+
+	<para>
+	<indexterm><primary>minimal</primary><secondary>configuration</secondary></indexterm>
+	<link linkend="smbconfminimal">A minimal smb.conf</link> contains a very minimal &smb.conf;.
+	<indexterm><primary>minimal configuration</primary></indexterm>
+	</para>
+
+	<example id="smbconfminimal">
+		<title>A minimal smb.conf</title>
+		<smbconfblock>
+
+		<smbconfsection name="[global]"/>
+		<smbconfoption name="workgroup">WKG</smbconfoption>
+		<smbconfoption name="netbios name">MYNAME</smbconfoption>
+		<smbconfsection name="[share1]"/>
+		<smbconfoption name="path">/tmp</smbconfoption>
+
+		<smbconfsection name="[share2]"/>
+		<smbconfoption name="path">/my_shared_folder</smbconfoption>
+		<smbconfoption name="comment">Some random files</smbconfoption>
+	</smbconfblock>
+	</example>
+
+</sect2>
+
+<sect2 id="tdbdocs">
+	<title>TDB Database File Information</title>
+
+	<para>
+	This section contains brief descriptions of the databases that are used by Samba-3.
+	</para>
+
+	<para>
+<indexterm><primary>tdb file locations</primary></indexterm>
+	The directory in which Samba stores the tdb files is determined by compile-time directives. Samba-3 stores
+	tdb files in two locations. The best way to determine these locations is to execute the following
+	command:
+<screen>
+&rootprompt; smbd -b | grep PRIVATE_DIR
+   PRIVATE_DIR: /etc/samba/private
+</screen>
+	This means that the confidential tdb files are stored in the <filename>/etc/samba/private</filename>
+	directory. Samba-3 also uses a number of tdb files that contain more mundane data. The location of
+	these files can be found by executing:
+<screen>
+&rootprompt; smbd -b | grep LOCKDIR
+   LOCKDIR: /var/lib/samba
+</screen>
+	Therefore the remaining control files will, in the example shown, be stored in the
+	<filename>/var/lib/samba</filename> directory.
+	</para>
+
+	<para>
+<indexterm><primary>tdb file descriptions</primary></indexterm>
+	The persistent tdb files are described in <link linkend="tdbpermfiledesc">the Persistent TDB File
+	Descriptions table</link>. All persistent tdb files should be regularly backed up. Use the
+	<command>tdbbackup</command> utility to backup the tdb files. All persistent tdb files must be
+	preserved during machine migrations, updates and upgrades.
+	</para>
+
+	<para>
+	The temporary tdb files do not need to be backed up, nor do they need to be preseved across machine
+	migrations, updates or upgrades. The temporary tdb files are described in <link linkend="tdbtempfiledesc">
+	the Temporary TDB File Descriptions</link>.
+	</para>
+
+        <table frame='all' id="tdbpermfiledesc"><title>Persistent TDB File Descriptions</title>
+        <tgroup cols='2'>
+			<colspec align="left"/>
+			<colspec align="justify" colwidth="1*"/>
+			<colspec align="left"/>
+                <thead>
+                <row>
+                        <entry align="left">Name</entry>
+                        <entry align="justify">Description</entry>
+                </row>
+                </thead>
+                <tbody>
+		<row>
+			<entry>account_policy</entry>
+			<entry><para>Samba/NT account policy settings, includes password expiration settings.</para></entry>
+		</row>
+		<row>
+			<entry>group_mapping</entry>
+			<entry><para>Mapping table from Windows groups/SID to UNIX groups.</para></entry>
+		</row>
+		<row>
+			<entry>ntdrivers</entry>
+			<entry><para>Stores per-printer installed driver information.</para></entry>
+		</row>
+		<row>
+			<entry>ntforms</entry>
+			<entry><para>Stores per-printer installed forms information.</para></entry>
+		</row>
+		<row>
+			<entry>ntprinters</entry>
+			<entry><para>Stores the per-printer devmode configuration settings.</para></entry>
+		</row>
+		<row>
+			<entry>passdb</entry>
+			<entry><para>
+				Exists only when the tdbsam passwd backend is used. This file stores the
+				SambaSAMAccount information. Note: This file requires that user POSIX account information is
+				availble from either the /etc/passwd file, or from an alternative system source.
+			</para></entry>
+		</row>
+		<row>
+			<entry>registry</entry>
+			<entry><para>
+				Read-only Samba database of a Windows registry skeleton that provides support for exporting 
+				various database tables via the winreg RPCs.
+			</para></entry>
+		</row>
+		<row>
+			<entry>secrets</entry>
+			<entry><para>
+				This file stores the Workgroup/Domain/Machine SID, the LDAP directory update password, and
+				a further collection of critical environmental data that is necessary for Samba to operate
+				correctly. This file contains very sensitive information that must be protected. It is stored
+				in the PRIVATE_DIR directory.
+			</para></entry>
+		</row>
+		<row>
+			<entry>share_info</entry>
+			<entry><para>Stores per-share ACL information.</para></entry>
+		</row>
+		<row>
+			<entry>winbindd_idmap</entry>
+			<entry><para>Winbindd's local IDMAP database.</para></entry>
+		</row>
+		</tbody>
+	</tgroup>
+	</table>
+
+        <table frame='all' id="tdbtempfiledesc"><title>Temporary TDB File Descriptions</title>
+        <tgroup cols='3'>
+			<colspec align="left"/>
+			<colspec align="justify" colwidth="1*"/>
+			<colspec align="left"/>
+                <thead>
+                <row>
+                        <entry align="left">Name</entry>
+                        <entry align="justify">Description</entry>
+                        <entry align="center">Backup</entry>
+                </row>
+                </thead>
+                <tbody>
+		<row>
+			<entry>brlock</entry>
+			<entry><para>Byte-range locking information.</para></entry>
+			<entry>No</entry>
+		</row>
+		<row>
+			<entry>connections</entry>
+			<entry><para>A temporary cache for current connection information used to enforce max connections.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>eventlog/*tdb</entry>
+			<entry><para>Records of eventlog entries. In most circumstances this is just a cache of system logs.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>gencache</entry>
+			<entry><para>Generic caching database for dead WINS servers and trusted domain data.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>login_cache</entry>
+			<entry><para>A temporary cache for login information, in particular bad password attempts.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>messages</entry>
+			<entry><para>Temporary storage of messages being processed by smbd.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>netsamlogon_cache</entry>
+			<entry><para>Caches user net_info_3 structure data from net_samlogon requests (as a domain member).</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>perfmon/*.tdb</entry>
+			<entry><para>Performance counter information.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>printing/*.tdb</entry>
+			<entry><para>Cached output from lpq command created on a per-print-service basis.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>schannel_store</entry>
+			<entry><para>
+				A confidential file, stored in the PRIVATE_DIR, containing crytographic connection
+				information so that clients that have temporarily disconnected can reconnect without
+				needing to renegotiate the connection setup process.
+			</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>sessionid</entry>
+			<entry><para>Temporary cache for miscellaneous session information and for utmp handling.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>unexpected</entry>
+			<entry><para>Stores packets received for which no process is actively listening.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>winbindd_cache</entry>
+			<entry><para>Cache of Identity information received from an NT4 domain or from ADS. Includes user
+				lists, etc.</para></entry>
+			<entry>yes</entry>
+		</row>
+		</tbody>
+	</tgroup>
+	</table>
+
+</sect2>
+
+<sect2>
+	<title>Starting Samba</title>
+
+	<para>
+	<indexterm><primary>daemon</primary></indexterm>
+	Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services.
+	An example of a service is the Apache Web server for which the daemon is called <command>httpd</command>. In the case of Samba there
+	are three daemons, two of which are needed as a minimum.
+	</para>
+
+	<para>
+	The Samba server is made up of the following daemons:
+	</para>
+
+	<variablelist>
+		<varlistentry><term>nmbd</term>
+			<listitem><para>
+			<indexterm><primary>smbd</primary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
+			This daemon handles all name registration and resolution requests. It is the primary vehicle involved
+			in network browsing. It handles all UDP-based protocols. The <command>nmbd</command> daemon should
+			be the first command started as part of the Samba startup process.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>smbd</term>
+			<listitem><para>
+			<indexterm><primary>nmbd</primary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
+			This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
+			manages local authentication. It should be started immediately following the startup of <command>nmbd</command>.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>winbindd</term>
+			<listitem><para>
+			<indexterm><primary>winbindd</primary></indexterm>
+			<indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
+			This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when
+			Samba has trust relationships with another domain. The <command>winbindd</command> daemon will check the
+			&smb.conf; file for the presence of the <parameter>idmap uid</parameter> and <parameter>idmap gid</parameter>
+			parameters. If they are are found, <command>winbindd</command> will use the values specified for
+			for UID and GID allocation. If these parameters are not specified, <command>winbindd</command>
+			will start but it will not be able to allocate UIDs or GIDs.
+			</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>
+	<indexterm><primary>startup</primary><secondary>process</secondary></indexterm>
+	When Samba has been packaged by an operating system vendor, the startup process is typically a custom feature of its
+	integration into the platform as a whole. Please refer to your operating system platform administration manuals for
+	specific information pertaining to correct management of Samba startup.
+	</para>
+
+</sect2>
+	
+<sect2>
+	<title>Example Configuration</title>
+	
+	<para>
+	<indexterm><primary>examples</primary></indexterm>
+	<indexterm><primary>source code</primary></indexterm>
+	<indexterm><primary>distribution</primary></indexterm>
+	<indexterm><primary>tarball</primary></indexterm>
+	<indexterm><primary>package</primary></indexterm>
+	There are sample configuration files in the examples subdirectory in the source code distribution tarball
+	package. It is suggested you read them carefully so you can see how the options go together in practice. See
+	the man page for all the options.  It might be worthwhile to start out with the
+	<filename>smb.conf.default</filename> configuration file and adapt it to your needs. It contains plenty of comments.
+	</para>
+
+	<para>
+	<indexterm><primary>simplest</primary><secondary>configuration</secondary></indexterm>
+	The simplest useful configuration file would contain something like that shown in
+	<link linkend="simple-example">Another simple smb.conf File</link>.
+	<indexterm><primary>simple configuration</primary></indexterm>
+	</para>
+
+<example id="simple-example">
+<title>Another simple smb.conf File</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
+
+<smbconfsection name="[homes]"/>
+<smbconfoption name="guest ok">no</smbconfoption>
+<smbconfoption name="read only">no</smbconfoption>
+</smbconfblock>
+</example>
+	
+	<para>
+	<indexterm><primary>connections</primary></indexterm>
+	<indexterm><primary>account</primary></indexterm>
+	<indexterm><primary>login name</primary></indexterm>
+	<indexterm><primary>service name</primary></indexterm>
+	This will allow connections by anyone with an account on the server, using either
+	their login name or <smbconfsection name="homes"/> as the service name.
+	(Note: The workgroup that Samba should appear in must also be set. The default
+	workgroup name is WORKGROUP.)
+	</para>
+	
+	<para>
+	<indexterm><primary>smbd</primary></indexterm>
+	Make sure you put the &smb.conf; file in the correct place. Note, the correct location of this file
+	depends on how the binary files were built. You can discover the correct location by executing from
+	the directory that contains the <command>smbd</command> command file:
+<screen>
+&rootprompt; smbd -b | grep smb.conf
+</screen>
+	</para>
+
+	<para>
+	<indexterm><primary>security</primary><secondary>settings</secondary></indexterm>
+	For more information about security settings for the <smbconfsection name="[homes]"/> share, please refer to 
+	<link linkend="securing-samba">Securing Samba</link>.
+	</para>
+
+<sect3>
+	<title>Test Your Config File with <command>testparm</command></title>
+
+	<para>
+	<indexterm><primary>validate</primary></indexterm>
+	<indexterm><primary>testparm</primary></indexterm>
+	<indexterm><primary>misconfigurations</primary></indexterm>
+	It's important to validate the contents of the &smb.conf; file using the &testparm; program.
+	If testparm runs correctly, it will list the loaded services. If not, it will give an error message.
+	Make sure it runs correctly and that the services look reasonable before proceeding. Enter the command: 
+	<screen>
+	&rootprompt; testparm /etc/samba/smb.conf
+	</screen>
+	Testparm will parse your configuration file and report any unknown parameters or incorrect syntax.
+	It also performs a check for common misconfigurations and will issue a warning if one is found.
+	</para>
+
+	<para>
+	Always run testparm again whenever the &smb.conf; file is changed!
+	</para>
+
+	<para>
+	<indexterm><primary>smbd</primary></indexterm>
+	<indexterm><primary>nmbd</primary></indexterm>
+	<indexterm><primary>winbindd</primary></indexterm>
+	<indexterm><primary>configuration</primary><secondary>documentation</secondary></indexterm>
+	The &smb.conf; file is constantly checked by the Samba daemons <command>smbd</command> and every instance of
+	itself that it spawns, <command>nmbd</command> and <command>winbindd</command>. It is good practice to
+	keep this file as small as possible. Many administrators prefer to document Samba configuration settings
+	and thus the need to keep this file small goes against good documentation wisdom. One solution that may
+	be adopted is to do all documentation and configuration in a file that has another name, such as
+	<filename>smb.conf.master</filename>. The <command>testparm</command> utility can be used to generate a
+	fully optimized &smb.conf; file from this master configuration and documtenation file as shown here:
+<screen>
+&rootprompt; testparm -s smb.conf.master > smb.conf
+</screen>
+	This administrative method makes it possible to maintain detailed configuration change records while at
+	the same time keeping the working &smb.conf; file size to the minimum necessary.
+	</para>
+
+</sect3>
+</sect2>
+
+<sect2>
+	<title>SWAT</title>
+
+	<para>
+	<indexterm><primary>swat</primary></indexterm>
+	SWAT is a Web-based interface that can be used to facilitate the configuration of Samba.  SWAT might not
+	be available in the Samba package that shipped with your platform, but in a separate package. If it is
+	necesaary to built SWAT please read the SWAT man page regarding compilation, installation, and
+	configuration of SWAT from the source code.
+	</para>
+
+	<para>
+	To launch SWAT, just run your favorite Web browser and point it to
+	<ulink url="http://localhost:901/" noescape="1">http://localhost:901/</ulink>.
+	Replace <replaceable>localhost</replaceable> with the name of the computer on which
+	Samba is running if that is a different computer than your browser.
+	</para>
+
+	<para>
+	SWAT can be used from a browser on any IP-connected machine, but be aware that connecting from a remote
+	machine leaves your connection open to password sniffing because passwords will be sent over the wire in the clear. 
+	</para>
+
+	<para>
+	More information about SWAT can be found in <link linkend="SWAT">The Samba Web Administration Tool</link>.
+	</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+	<title>List Shares Available on the Server</title>
+
+	<para>
+	To list shares that are available from the configured Samba server, execute the
+	following command:
+	</para>
+
+<para><screen>
+&prompt;<userinput>smbclient -L <replaceable>yourhostname</replaceable></userinput>
+</screen></para>
+
+	<para>
+	You should see a list of shares available on your server. If you do not, then
+	something is incorrectly configured. This method can also be used to see what shares 
+	are available on other SMB servers, such as Windows 2000.
+	</para>
+
+	<para>
+	If you choose user-level security, you may find that Samba requests a password
+	before it will list the shares. See the <command>smbclient</command> man page for details.
+	You can force it to list the shares without a password by adding the option
+	<option>-N</option> to the command line. 
+	</para>
+</sect1>
+
+<sect1>
+	<title>Connect with a UNIX Client</title>
+	
+	<para>
+	Enter the following command:
+<screen>
+&prompt;<userinput>smbclient <replaceable> //yourhostname/aservice</replaceable></userinput>
+</screen></para>
+	
+	<para>Typically <replaceable>yourhostname</replaceable> is the name of the host on which &smbd;
+	has been installed. The <replaceable>aservice</replaceable> is any service that has been defined in the &smb.conf;
+	file. Try your username if you just have a <smbconfsection name="[homes]"/> section in the &smb.conf; file.</para>
+
+	<para>Example: If the UNIX host is called <replaceable>bambi</replaceable> and a valid login name
+	is <replaceable>fred</replaceable>, you would type:</para>
+
+<para><screen>
+&prompt;<userinput>smbclient //<replaceable>bambi</replaceable>/<replaceable>fred</replaceable></userinput>
+</screen></para>
+</sect1>
+
+<sect1>
+	<title>Connect from a Remote SMB Client</title>
+
+	<para>
+	Now that Samba is working correctly locally, you can try to access it from other clients. Within a few
+	minutes, the Samba host should be listed in the Network Neighborhood on all Windows clients of its subnet.
+	Try browsing the server from another client or "mounting" it.
+	</para>
+
+	<para>
+	Mounting disks from a DOS, Windows, or OS/2 client can be done by running a command such as:
+<screen>
+&dosprompt;<userinput>net use m: \\servername\service</userinput>
+</screen>
+	Where the drive letter m: is any available drive letter. It is important to double-check that the
+	service (share) name that you used does actually exist.
+	</para>
+
+	<para>
+	Try printing, for example,
+<screen>
+&dosprompt;<userinput>net use lpt1:	\\servername\spoolservice</userinput>
+</screen>
+	The <literal>spoolservice</literal> is the name of the printer (actually the print queue) on the target
+	server. This will permit all print jobs that are captured by the lpt1: port on the Windows client to
+	be sent to the printer that owns the spoolservice that has been specified.
+	</para>
+
+<para>
+<screen>&dosprompt;<userinput>print filename</userinput>
+</screen></para>
+
+	<sect2>
+	<title>What If Things Don't Work?</title>
+	
+	<para>
+	You might want to read <link linkend="diagnosis">The Samba Checklist</link>.  If you are still
+	stuck, refer to <link linkend="problems">Analyzing and Solving Samba Problems</link>.  Samba has
+	been successfully installed at thousands of sites worldwide.  It is unlikely that your particular problem is
+	unique, so it might be productive to perform an Internet search to see if someone else has encountered your
+	problem and has found a way to overcome it.
+	</para>
+
+	<para>
+	If you are new to Samba, and particularly if you are new to Windows networking, or to UNIX/Linux,
+	the book <quote>Samba-3 by Example</quote> will help you to create a validated network environment.
+	Simply choose from the first five chapters the network design that most closely matches site needs,
+	then follow the simple step-by-step procedure to deploy it. Later, when you have a working network
+	you may well want to refer back to this book for further insight into opportunities for improvement.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Still Stuck?</title>
+
+	<para>
+	The best advice under the stress of abject frustration is to cool down! That may be challenging
+	of itself, but while you are angry or annoyed your ability to seek out a solution is somewhat
+	undermined. A cool head clears the way to finding the answer you are looking for. Just remember,
+	every problem has a solution &smbmdash; there is a good chance that someone else has found it
+	even though you can't right now. That will change with time, patience and learning.
+	</para>
+
+	<para>
+	Now that you have cooled down a bit, please refer to <link linkend="diagnosis">the Samba Checklist</link>
+	for a process that can be followed to identify the cause of your problem.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+The following questions and issues are raised repeatedly on the Samba mailing list.
+</para>
+
+<sect2>
+	<title>Large Number of smbd Processes</title>
+
+	<para>
+	Samba consists of three core programs: &nmbd;, &smbd;, and &winbindd;. &nmbd; is the name server message daemon,
+	&smbd; is the server message daemon, and &winbindd; is the daemon that handles communication with domain controllers.
+	</para>
+
+	<para>
+	If Samba is <emphasis>not</emphasis> running as a WINS server, then there will be one single instance of
+	 &nmbd; running on your system. If it is running as a WINS server, then there will be
+	two instances &smbmdash; one to handle the WINS requests.
+	</para>
+
+	<para>
+	&smbd; handles all connection requests. It spawns a new process for each client
+	connection made. That is why you may see so many of them, one per client connection.
+	</para>
+
+	<para>
+	&winbindd; will run as one or two daemons, depending on whether or not it is being
+	run in <emphasis>split mode</emphasis> (in which case there will be two instances).
+	</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Error Message: open_oplock_ipc</title>
+
+	<para>
+	An error message is observed in the log files when &smbd; is started: <quote>open_oplock_ipc: Failed to
+	get local UDP socket for address 100007f. Error was Cannot assign requested.</quote>
+	</para>
+
+	<para>
+	Your loopback device isn't working correctly. Make sure it is configured correctly. The loopback
+	device is an internal (virtual) network device with the IP address <emphasis>127.0.0.1</emphasis>.
+	Read your OS documentation for details on how to configure the loopback on your system.
+	</para>
+
+	</sect2>
+
+	<sect2>
+		<title><quote><errorname>The network name cannot be found</errorname></quote></title>
+
+		<para>
+		This error can be caused by one of these misconfigurations:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>You specified a nonexisting path
+			for the share in &smb.conf;.</para></listitem>
+
+			<listitem><para>The user you are trying to access the share with does not 
+			have sufficient permissions to access the path for
+			the share. Both read (r) and access (x) should be possible.</para></listitem>
+
+			<listitem><para>The share you are trying to access does not exist.</para></listitem>
+	</itemizedlist>
+
+	</sect2>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Integrating-with-Windows.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Integrating-with-Windows.xml
new file mode 100644
index 00000000000..68b9d49b69b
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Integrating-with-Windows.xml
@@ -0,0 +1,745 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="integrate-ms-networks">
+ 
+<chapterinfo>
+	&author.jht;
+        <pubdate> (Jan 01 2001) </pubdate>
+</chapterinfo>
+ 
+<title>Integrating MS Windows Networks with Samba</title>
+ 
+<para>
+<indexterm><primary>NetBIOS</primary></indexterm>
+This chapter deals with NetBIOS over TCP/IP name to IP address resolution. If
+your MS Windows clients are not configured to use NetBIOS over TCP/IP, then this
+section does not apply to your installation. If your installation involves the use of
+NetBIOS over TCP/IP, then this chapter may help you to resolve networking problems.
+</para>
+
+<note>
+<para>
+<indexterm><primary>NetBEUI</primary></indexterm>
+<indexterm><primary>LLC</primary></indexterm>
+NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS
+over Logical Link Control (LLC). On modern networks it is highly advised
+to not run NetBEUI at all. Note also that there is no such thing as
+NetBEUI over TCP/IP &smbmdash; the existence of such a protocol is a complete
+and utter misapprehension.
+</para>
+</note>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+Many MS Windows network administrators have never been exposed to basic TCP/IP
+networking as it is implemented in a UNIX/Linux operating system. Likewise, many UNIX and
+Linux administrators have not been exposed to the intricacies of MS Windows TCP/IP-based
+networking (and may have no desire to be, either).
+</para>
+
+<para>
+This chapter gives a short introduction to the basics of how a name can be resolved to 
+its IP address for each operating system environment.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Background Information</title>
+
+<para>
+<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
+<indexterm><primary>UDP port 137</primary></indexterm>
+<indexterm><primary>TCP port 139</primary></indexterm>
+<indexterm><primary>TCP port 445</primary></indexterm>
+<indexterm><primary>UDP port 137</primary></indexterm>
+Since the introduction of MS Windows 2000, it is possible to run MS Windows networking
+without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS
+name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over
+TCP/IP is disabled on MS Windows 2000 and later clients, then only the TCP port 445 is
+used, and the UDP port 137 and TCP port 139 are not.
+</para>
+
+<note>
+<para>
+When using Windows 2000 or later clients, if NetBIOS over TCP/IP is not disabled, then
+the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet
+Name Service, or WINS), TCP port 139, and TCP port 445 (for actual file and print traffic).
+</para>
+</note>
+
+<para>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>DDNS</primary></indexterm>
+<indexterm><primary>SRV RR</primary></indexterm>
+<indexterm><primary>IXFR</primary></indexterm>
+<indexterm><primary>DHCP</primary></indexterm>
+When NetBIOS over TCP/IP is disabled, the use of DNS is essential. Most installations that disable NetBIOS
+over TCP/IP today use MS Active Directory Service (ADS). ADS requires
+<indexterm><primary>DNS</primary><secondary>Dynamic</secondary></indexterm> dynamic DNS with Service Resource
+Records (SRV RR) and with Incremental Zone Transfers (IXFR).  <indexterm><primary>DHCP</primary></indexterm>
+Use of DHCP with ADS is recommended as a further means of maintaining central control over the client
+workstation network configuration.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Name Resolution in a Pure UNIX/Linux World</title>
+
+<para>
+The key configuration files covered in this section are:
+</para>
+
+<indexterm><primary>/etc/hosts</primary></indexterm>
+<indexterm><primary>/etc/resolv.conf</primary></indexterm>
+<indexterm><primary>/etc/host.conf</primary></indexterm>
+<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+
+<itemizedlist>
+	<listitem><para><filename>/etc/hosts</filename></para></listitem>
+	<listitem><para><filename>/etc/resolv.conf</filename></para></listitem>
+	<listitem><para><filename>/etc/host.conf</filename></para></listitem>
+	<listitem><para><filename>/etc/nsswitch.conf</filename></para></listitem>
+</itemizedlist>
+
+<sect2>
+<title><filename>/etc/hosts</filename></title>
+
+<para>
+This file contains a static list of IP addresses and names.
+<programlisting>
+127.0.0.1	localhost localhost.localdomain
+192.168.1.1	bigbox.quenya.org	bigbox	alias4box
+</programlisting>
+</para>
+
+<para>
+<indexterm><primary>/etc/hosts></primary></indexterm>
+<indexterm><primary>name resolution</primary></indexterm>
+The purpose of <filename>/etc/hosts</filename> is to provide a 
+name resolution mechanism so users do not need to remember 
+IP addresses.
+</para>
+
+<para>
+<indexterm><primary>IP addresses</primary></indexterm>
+<indexterm><primary>MAC address</primary></indexterm>
+<indexterm><primary>physical network transport layer</primary></indexterm>
+Network packets that are sent over the physical network transport 
+layer communicate not via IP addresses but rather using the Media 
+Access Control address, or MAC address. IP addresses are currently 
+32 bits in length and are typically presented as four decimal 
+numbers that are separated by a dot (or period) &smbmdash; for example, 168.192.1.1.
+</para>
+
+<para>
+<indexterm><primary>MAC Addresses</primary></indexterm>
+MAC addresses use 48 bits (or 6 bytes) and are typically represented 
+as two-digit hexadecimal numbers separated by colons: 40:8e:0a:12:34:56.
+</para>
+
+<para>
+Every network interface must have a MAC address. Associated with a MAC address may be one or more IP
+addresses. There is no relationship between an IP address and a MAC address; all such assignments are
+arbitrary or discretionary in nature. At the most basic level, all network communications take place using MAC
+addressing. Since MAC addresses must be globally unique and generally remain fixed for any particular
+interface, the assignment of an IP address makes sense from a network management perspective. More than one IP
+address can be assigned per MAC address. One address must be the primary IP address &smbmdash; this is the
+address that will be returned in the Address Resolution Protocol (ARP) reply.
+</para>
+
+<para>
+<indexterm><primary>machine name</primary></indexterm>
+When a user or a process wants to communicate with another machine, 
+the protocol implementation ensures that the <quote>machine name</quote> or <quote>host 
+name</quote> is resolved to an IP address in a manner that is controlled 
+by the TCP/IP configuration control files. The file 
+<filename>/etc/hosts</filename> is one such file.
+</para>
+
+<para>
+<indexterm><primary>ARP/RARP</primary></indexterm>
+When the IP address of the destination interface has been determined, a protocol called ARP/RARP is used to
+identify the MAC address of the target interface. ARP is a broadcast-oriented method that uses User Datagram
+Protocol (UDP) to send a request to all interfaces on the local network segment using the all 1s MAC address.
+Network interfaces are programmed to respond to two MAC addresses only; their own unique address and the
+address ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will contain the MAC address and the primary
+IP address for each interface.
+</para>
+
+<para>
+<indexterm><primary>/etc/hosts</primary></indexterm>
+The <filename>/etc/hosts</filename> file is foundational to all 
+UNIX/Linux TCP/IP installations and as a minimum will contain 
+the localhost and local network interface IP addresses and the 
+primary names by which they are known within the local machine. 
+This file helps to prime the pump so a basic level of name 
+resolution can exist before any other method of name resolution 
+becomes available.
+</para>
+
+</sect2>
+
+
+<sect2>
+<title><filename>/etc/resolv.conf</filename></title>
+
+<para>
+This file tells the name resolution libraries:
+</para>
+
+<itemizedlist>
+	<listitem><para>The name of the domain to which the machine 
+	belongs.
+	</para></listitem>
+	
+	<listitem><para>The name(s) of any domains that should be 
+	automatically searched when trying to resolve unqualified 
+	host names to their IP address.
+	</para></listitem>
+	
+	<listitem><para>The name or IP address of available domain 
+	name servers that may be asked to perform name-to-address 
+	translation lookups.
+	</para></listitem>
+</itemizedlist>
+
+</sect2>
+
+
+<sect2>
+<title><filename>/etc/host.conf</filename></title>
+
+
+<para>
+<indexterm><primary>/etc/host.conf</primary></indexterm>
+<filename>/etc/host.conf</filename> is the primary means by which the setting in
+<filename>/etc/resolv.conf</filename> may be effected. It is a critical configuration file. This file controls
+the order by which name resolution may proceed. The typical structure is:
+<programlisting>
+order hosts,bind
+multi on
+</programlisting></para>
+
+<para>Both addresses should be returned. Please refer to the 
+man page for <filename>host.conf</filename> for further details.
+</para>
+
+</sect2>
+
+
+<sect2>
+<title><filename>/etc/nsswitch.conf</filename></title>
+
+<para>
+<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+This file controls the actual name resolution targets. The 
+file typically has resolver object specifications as follows:
+<programlisting>
+# /etc/nsswitch.conf
+#
+# Name Service Switch configuration file.
+#
+
+passwd:		compat
+# Alternative entries for password authentication are:
+# passwd:	compat files nis ldap winbind
+shadow:		compat
+group:		compat
+
+hosts:		files nis dns
+# Alternative entries for host name resolution are:
+# hosts:	files dns nis nis+ hesiod db compat ldap wins
+networks:	nis files dns
+
+ethers:		nis files
+protocols:	nis files
+rpc:		nis files
+services:	nis files
+</programlisting></para>
+
+<para>
+Of course, each of these mechanisms requires that the appropriate 
+facilities and/or services are correctly configured.
+</para>
+
+<para>
+It should be noted that unless a network request/message must be 
+sent, TCP/IP networks are silent. All TCP/IP communications assume a 
+principal of speaking only when necessary.
+</para>
+
+
+<para>
+<indexterm><primary>libnss_wins.so</primary></indexterm>
+<indexterm><primary>NetBIOS names</primary></indexterm>
+<indexterm><primary>make</primary></indexterm>
+<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+<indexterm><primary>wins</primary></indexterm>
+Starting with version 2.2.0, Samba has Linux support for extensions to 
+the name service switch infrastructure so Linux clients will 
+be able to obtain resolution of MS Windows NetBIOS names to IP 
+addresses. To gain this functionality, Samba needs to be compiled 
+with appropriate arguments to the make command (i.e., <userinput>make 
+nsswitch/libnss_wins.so</userinput>). The resulting library should 
+then be installed in the <filename>/lib</filename> directory, and 
+the <parameter>wins</parameter> parameter needs to be added to the <quote>hosts:</quote> line in 
+the <filename>/etc/nsswitch.conf</filename> file. At this point, it 
+will be possible to ping any MS Windows machine by its NetBIOS 
+machine name, as long as that machine is within the workgroup to 
+which both the Samba machine and the MS Windows machine belong.
+</para>
+
+</sect2>
+</sect1>
+
+
+<sect1>
+<title>Name Resolution as Used within MS Windows Networking</title>
+
+<para>
+<indexterm><primary>computer name</primary></indexterm>
+<indexterm><primary>machine name</primary></indexterm>
+<indexterm><primary>NetBIOS name</primary></indexterm>
+<indexterm><primary>SMB name</primary></indexterm>
+MS Windows networking is predicated on the name each machine is given. This name is known variously (and
+inconsistently) as the <quote>computer name,</quote> <quote>machine name,</quote> <quote>networking
+name,</quote> <quote>NetBIOS name,</quote> or <quote>SMB name.</quote> All terms mean the same thing with the
+exception of <quote>NetBIOS name,</quote> which can also apply to the name of the workgroup or the domain
+name. The terms <quote>workgroup</quote> and <quote>domain</quote> are really just a simple name with which
+the machine is associated. All NetBIOS names are exactly 16 characters in length. The
+16<superscript>th</superscript> character is reserved.  It is used to store a 1-byte value that indicates
+service level information for the NetBIOS name that is registered. A NetBIOS machine name is therefore
+registered for each service type that is provided by the client/server.
+</para>
+
+<para>
+<link linkend="uniqnetbiosnames">Unique NetBIOS names</link> and <link linkend="netbiosnamesgrp">group names</link> tables 
+list typical NetBIOS name/service type registrations.
+</para>
+
+<table frame="all" id="uniqnetbiosnames">
+<title>Unique NetBIOS Names</title>
+<tgroup cols="2">
+<colspec align="left"/>
+<colspec align="justify"/>
+<tbody>
+<row><entry>MACHINENAME&lt;00&gt;</entry><entry>Server Service is running on MACHINENAME</entry></row>
+<row><entry>MACHINENAME&lt;03&gt;</entry><entry>Generic machine name (NetBIOS name)</entry></row>
+<row><entry>MACHINENAME&lt;20&gt;</entry><entry>LanMan server service is running on MACHINENAME</entry></row>
+<row><entry>WORKGROUP&lt;1b&gt;</entry><entry>Domain master browser</entry></row>
+</tbody>
+</tgroup>
+</table>
+
+<table frame="all" id="netbiosnamesgrp">
+<title>Group Names</title>
+<tgroup cols="2">
+<colspec align="left"/>
+<colspec align="justify"/>
+<tbody>
+<row><entry>WORKGROUP&lt;03&gt;</entry><entry>Generic name registered by all members of WORKGROUP</entry></row>
+<row><entry>WORKGROUP&lt;1c&gt;</entry><entry>Domain cntrollers/netlogon servers</entry></row>
+<row><entry>WORKGROUP&lt;1d&gt;</entry><entry>Local master browsers</entry></row>
+<row><entry>WORKGROUP&lt;1e&gt;</entry><entry>Browser election service</entry></row>
+</tbody>
+</tgroup>
+</table>
+
+<para>
+<indexterm><primary>NetBIOS</primary></indexterm>
+It should be noted that all NetBIOS machines register their own 
+names as per <link linkend="uniqnetbiosnames">Unique NetBIOS names</link> and <link
+linkend="netbiosnamesgrp">group names</link>. This is in vast contrast to TCP/IP 
+installations where the system administrator traditionally 
+determines in the <filename>/etc/hosts</filename> or in the DNS database what names 
+are associated with each IP address.
+</para>
+
+<para>
+<indexterm><primary>NetBIOS</primary></indexterm>
+<indexterm><primary>/etc/hosts</primary></indexterm>
+<indexterm><primary>NetBIOS name</primary></indexterm>
+One further point of clarification should be noted. The <filename>/etc/hosts</filename> 
+file and the DNS records do not provide the NetBIOS name information 
+that MS Windows clients depend on to locate the type of service that may 
+be needed. An example of this is what happens when an MS Windows client 
+wants to locate a domain logon server. It finds this service and the IP 
+address of a server that provides it by performing a lookup (via a 
+NetBIOS broadcast) for enumeration of all machines that have 
+registered the name type *&lt;1C&gt;. A logon request is then sent to each 
+IP address that is returned in the enumerated list of IP addresses.
+Whichever machine first replies, it then ends up providing the logon services.
+</para>
+
+<para>
+<indexterm><primary>domain</primary></indexterm>
+<indexterm><primary>workgroup</primary></indexterm>
+The name <quote>workgroup</quote> or <quote>domain</quote> really can be confusing, since these 
+have the added significance of indicating what is the security 
+architecture of the MS Windows network. The term <quote>workgroup</quote> indicates 
+that the primary nature of the network environment is that of a 
+peer-to-peer design. In a workgroup, all machines are responsible for 
+their own security, and generally such security is limited to the use of 
+just a password (known as share-level security). In most situations 
+with peer-to-peer networking, the users who control their own machines 
+will simply opt to have no security at all. It is possible to have 
+user-level security in a workgroup environment, thus requiring the use 
+of a username and a matching password.
+</para>
+
+<para>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>Network Basic Input/Output System</primary><see>NetBIOS</see></indexterm>
+<indexterm><primary>Logical Link Control</primary><see>LLC</see></indexterm>
+<indexterm><primary>Network Basic Extended User Interface</primary><see>NetBEUI</see></indexterm>
+<indexterm><primary>Internetworking Packet Exchange</primary><see>IPX</see></indexterm>
+<indexterm><primary>NetWare</primary></indexterm>
+<indexterm><primary>NetBT</primary></indexterm>
+<indexterm><primary>NBT</primary></indexterm>
+MS Windows networking is thus predetermined to use machine names 
+for all local and remote machine message passing. The protocol used is 
+called Server Message Block (SMB), and this is implemented using 
+the NetBIOS protocol (Network Basic Input/Output System). NetBIOS can 
+be encapsulated using LLC (Logical Link Control) protocol &smbmdash; in which case 
+the resulting protocol is called NetBEUI (Network Basic Extended User 
+Interface). NetBIOS can also be run over IPX (Internetworking Packet 
+Exchange) protocol as used by Novell NetWare, and it can be run 
+over TCP/IP protocols &smbmdash; in which case the resulting protocol is called 
+NBT or NetBT, the NetBIOS over TCP/IP.
+</para>
+
+<para>
+MS Windows machines use a complex array of name resolution mechanisms. 
+Since we are primarily concerned with TCP/IP, this demonstration is 
+limited to this area.
+</para>
+
+<sect2>
+<title>The NetBIOS Name Cache</title>
+
+<para>
+<indexterm><primary>n-memory buffer</primary></indexterm>
+<indexterm><primary>local cache</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+All MS Windows machines employ an in-memory buffer in which is 
+stored the NetBIOS names and IP addresses for all external 
+machines that machine has communicated with over the 
+past 10 to 15 minutes. It is more efficient to obtain an IP address 
+for a machine from the local cache than it is to go through all the 
+configured name resolution mechanisms.
+</para>
+
+<para>
+<indexterm><primary>name lookup</primary></indexterm>
+If a machine whose name is in the local name cache is shut 
+down before the name is expired and flushed from the cache, then 
+an attempt to exchange a message with that machine will be subject 
+to timeout delays. Its name is in the cache, so a name resolution 
+lookup will succeed, but the machine cannot respond. This can be 
+frustrating for users but is a characteristic of the protocol.
+</para>
+
+<para>
+<indexterm><primary>nbtstat</primary></indexterm>
+<indexterm><primary>nmblookup</primary></indexterm>
+<indexterm><primary>NetBIOS</primary></indexterm>
+The MS Windows utility that allows examination of the NetBIOS 
+name cache is called <quote>nbtstat.</quote> The Samba equivalent
+is called <command>nmblookup</command>.
+</para>
+
+</sect2>
+
+<sect2>
+<title>The LMHOSTS File</title>
+
+<para>
+<indexterm><primary>LMHOSTS</primary></indexterm>
+This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in the directory
+<filename>%SystemRoot%\SYSTEM32\DRIVERS\ETC</filename> and contains the IP address
+and the machine name in matched pairs. The <filename>LMHOSTS</filename> file
+performs NetBIOS name to IP address mapping.
+</para>
+
+<para>
+It typically looks like this:
+</para>
+
+<para><programlisting>
+# Copyright (c) 1998 Microsoft Corp.
+#
+# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
+# over TCP/IP) stack for Windows98
+#
+# This file contains the mappings of IP addresses to NT computer names
+# (NetBIOS) names. Each entry should be kept on an individual line.
+# The IP address should be placed in the first column followed by the
+# corresponding computer name. The address and the computer name
+# should be separated by at least one space or tab. The "#" character
+# is generally used to denote the start of a comment (see the exceptions
+# below).
+#
+# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
+# files and offers the following extensions:
+#
+#      #PRE
+#      #DOM:&lt;domain&gt;
+#      #INCLUDE &lt;filename&gt;
+#      #BEGIN_ALTERNATE
+#      #END_ALTERNATE
+#      \0xnn (non-printing character support)
+#
+# Following any entry in the file with the characters "#PRE" will cause
+# the entry to be preloaded into the name cache. By default, entries are
+# not preloaded, but are parsed only after dynamic name resolution fails.
+#
+# Following an entry with the "#DOM:&lt;domain&gt;" tag will associate the
+# entry with the domain specified by &lt;domain&gt;. This effects how the
+# browser and logon services behave in TCP/IP environments. To preload
+# the host name associated with #DOM entry, it is necessary to also add a
+# #PRE to the line. The &lt;domain&gt; is always pre-loaded although it will not
+# be shown when the name cache is viewed.
+#
+# Specifying "#INCLUDE &lt;filename&gt;" will force the RFC NetBIOS (NBT)
+# software to seek the specified &lt;filename&gt; and parse it as if it were
+# local. &lt;filename&gt; is generally a UNC-based name, allowing a
+# centralized lmhosts file to be maintained on a server.
+# It is ALWAYS necessary to provide a mapping for the IP address of the
+# server prior to the #INCLUDE. This mapping must use the #PRE directive.
+# In addition the share "public" in the example below must be in the
+# LanMan Server list of "NullSessionShares" in order for client machines to
+# be able to read the lmhosts file successfully. This key is under
+# \machine\system\currentcontrolset\services\lanmanserver\
+# parameters\nullsessionshares
+# in the registry. Simply add "public" to the list found there.
+#
+# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
+# statements to be grouped together. Any single successful include
+# will cause the group to succeed.
+#
+# Finally, non-printing characters can be embedded in mappings by
+# first surrounding the NetBIOS name in quotations, then using the
+# \0xnn notation to specify a hex value for a non-printing character.
+#
+# The following example illustrates all of these extensions:
+#
+# 102.54.94.97     rhino     #PRE #DOM:networking  #net group's DC
+# 102.54.94.102    "appname  \0x14"       #special app server
+# 102.54.94.123    popular   #PRE         #source server
+# 102.54.94.117    localsrv  #PRE         #needed for the include
+#
+# #BEGIN_ALTERNATE
+# #INCLUDE \\localsrv\public\lmhosts
+# #INCLUDE \\rhino\public\lmhosts
+# #END_ALTERNATE
+#
+# In the above example, the "appname" server contains a special
+# character in its name, the "popular" and "localsrv" server names are
+# pre-loaded, and the "rhino" server name is specified so it can be used
+# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
+# system is unavailable.
+#
+# Note that the whole file is parsed including comments on each lookup,
+# so keeping the number of comments to a minimum will improve performance.
+# Therefore it is not advisable to simply add lmhosts file entries onto the
+# end of this file.
+</programlisting></para>
+
+</sect2>
+
+<sect2>
+<title>HOSTS File</title>
+
+<para>
+This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in 
+the directory <filename>%SystemRoot%\SYSTEM32\DRIVERS\ETC</filename> and contains 
+the IP address and the IP hostname in matched pairs. It can be 
+used by the name resolution infrastructure in MS Windows, depending 
+on how the TCP/IP environment is configured. This file is in 
+every way the equivalent of the UNIX/Linux <filename>/etc/hosts</filename> file.
+</para>
+</sect2>
+
+
+<sect2>
+<title>DNS Lookup</title>
+
+
+<para>
+<indexterm><primary>DNS</primary></indexterm>
+This capability is configured in the TCP/IP setup area in the network 
+configuration facility. If enabled, an elaborate name resolution sequence 
+is followed, the precise nature of which is dependent on how the NetBIOS 
+Node Type parameter is configured. A Node Type of 0 means that
+NetBIOS broadcast (over UDP broadcast) is used if the name 
+that is the subject of a name lookup is not found in the NetBIOS name 
+cache. If that fails, then DNS, HOSTS, and LMHOSTS are checked. If set to 
+Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the 
+WINS server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast 
+lookup is used.
+</para>
+
+</sect2>
+
+<sect2>
+<title>WINS Lookup</title>
+
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>Windows Internet Name Server</primary><see>WINS</see></indexterm>
+<indexterm><primary>NetBIOS Name Server</primary><see>NBNS</see></indexterm>
+A WINS (Windows Internet Name Server) service is the equivalent of the 
+rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores 
+the names and IP addresses that are registered by a Windows client 
+if the TCP/IP setup has been given at least one WINS server IP address.
+</para>
+
+<para>
+To configure Samba to be a WINS server, the following parameter needs 
+to be added to the &smb.conf; file:
+</para>
+
+<para><smbconfblock>
+<smbconfoption name="wins support">Yes</smbconfoption>
+</smbconfblock></para>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+To configure Samba to use a WINS server, the following parameters are 
+needed in the &smb.conf; file:
+</para>
+
+<para><smbconfblock>
+<smbconfoption name="wins support">No</smbconfoption>
+<smbconfoption name="wins server">xxx.xxx.xxx.xxx</smbconfoption>
+</smbconfblock></para>
+
+<para>
+where <replaceable>xxx.xxx.xxx.xxx</replaceable> is the IP address 
+of the WINS server.
+</para>
+
+<para>For information about setting up Samba as a WINS server, read 
+<link linkend="NetworkBrowsing">Network Browsing</link>.</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+TCP/IP network configuration problems find every network administrator sooner or later.
+The cause can be anything from keyboard mishaps to forgetfulness to simple mistakes to
+carelessness. Of course, no one is ever deliberately careless!
+</para>
+
+	<sect2>
+		<title>Pinging Works Only One Way</title>
+
+	<para>
+	<quote>I can ping my Samba server from Windows, but I cannot ping my Windows
+	machine from the Samba server.</quote>
+	</para>
+
+	<para>
+	The Windows machine was at IP address 192.168.1.2 with netmask 255.255.255.0, the
+	Samba server (Linux) was at IP address 192.168.1.130 with netmask 255.255.255.128.
+	The machines were on a local network with no external connections.
+	</para>
+
+	<para>
+	Due to inconsistent netmasks, the Windows machine was on network 192.168.1.0/24, while
+	the Samba server was on network 192.168.1.128/25 &smbmdash; logically a different network.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Very Slow Network Connections</title>
+
+	<para>
+	A common cause of slow network response includes:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>Client is configured to use DNS and the DNS server is down.</para></listitem>
+		<listitem><para>Client is configured to use remote DNS server, but the
+		remote connection is down.</para></listitem>
+		<listitem><para>Client is configured to use a WINS server, but there is no WINS server.</para></listitem>
+		<listitem><para>Client is not configured to use a WINS server, but there is a WINS server.</para></listitem>
+		<listitem><para>Firewall is filtering out DNS or WINS traffic.</para></listitem>
+	</itemizedlist>
+
+	</sect2>
+
+	<sect2>
+	<title>Samba Server Name-Change Problem</title>
+
+	<para>
+	<quote>The name of the Samba server was changed, Samba was restarted, and now the Samba server cannot be
+	pinged by its new name from an MS Windows NT4 workstation, but it does still respond to pinging using
+	the old name. Why?</quote>
+	</para>
+
+	<para>
+	From this description, three things are obvious:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>WINS is not in use; only broadcast-based name resolution is used.</para></listitem>
+		<listitem><para>The Samba server was renamed and restarted within the last 10 or 15 minutes.</para></listitem>
+		<listitem><para>The old Samba server name is still in the NetBIOS name cache on the MS Windows NT4 workstation.</para></listitem>
+	</itemizedlist>
+
+	<para>
+	To find what names are present in the NetBIOS name cache on the MS Windows NT4 machine,
+	open a <command>cmd</command> shell and then:
+	</para>
+
+	<para>
+<screen>
+&dosprompt;<userinput>nbtstat -n</userinput>
+
+              NetBIOS Local Name Table
+
+   Name                 Type          Status
+------------------------------------------------
+&example.workstation.windows;            &lt;03&gt;  UNIQUE      Registered
+ADMINISTRATOR     &lt;03&gt;  UNIQUE      Registered
+&example.workstation.windows;            &lt;00&gt;  UNIQUE      Registered
+SARDON           &lt;00&gt;  GROUP       Registered
+&example.workstation.windows;            &lt;20&gt;  UNIQUE      Registered
+&example.workstation.windows;            &lt;1F&gt;  UNIQUE      Registered
+
+
+&dosprompt;nbtstat -c
+
+             NetBIOS Remote Cache Name Table
+
+   Name                 Type       Host Address     Life [sec]
+--------------------------------------------------------------
+&example.server.samba;	&lt;20&gt;  UNIQUE      192.168.1.1          240
+
+&dosprompt;
+</screen>
+	</para>
+
+	<para>
+	In this example, &example.server.samba; is the Samba server and &example.workstation.windows; is the MS Windows NT4 workstation.
+	The first listing shows the contents of the Local Name Table (i.e., identity information on
+	the MS Windows workstation), and the second shows the NetBIOS name in the NetBIOS name cache.
+	The name cache contains the remote machines known to this workstation.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-InterdomainTrusts.xml b/docs-xml/Samba3-HOWTO/TOSHARG-InterdomainTrusts.xml
new file mode 100644
index 00000000000..3ea527ba5e1
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-InterdomainTrusts.xml
@@ -0,0 +1,602 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="InterdomainTrusts">
+<chapterinfo>
+	&author.jht;
+	&author.mimir;
+	<author>&person.jelmer;<contrib>drawing</contrib></author>
+        <author>
+                <firstname>Stephen</firstname><surname>Langasek</surname>
+                <affiliation>
+                        <address><email>vorlon@netexpress.net</email></address>
+                </affiliation>
+        </author>
+	<pubdate>April 3, 2003</pubdate>
+</chapterinfo>
+
+<title>Interdomain Trust Relationships</title>
+
+
+<para>
+<indexterm><primary>Interdomain Trusts</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>trusts</primary></indexterm>
+<indexterm><primary>samba-to-samba trusts</primary></indexterm>
+<indexterm><primary>Active Directory</primary></indexterm>
+<indexterm><primary>NT4-style domain</primary></indexterm>
+<indexterm><primary>trust relationships</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>LDAP-based</primary></indexterm>
+Samba-3 supports NT4-style domain trust relationships. This is a feature that many sites
+will want to use if they migrate to Samba-3 from an NT4-style domain and do not want to
+adopt Active Directory or an LDAP-based authentication backend. This chapter explains
+some background information regarding trust relationships and how to create them. It is now
+possible for Samba-3 to trust NT4 (and vice versa), as well as to create Samba-to-Samba 
+trusts.
+</para>
+
+<para>
+<indexterm><primary>winbind</primary></indexterm>
+<indexterm><primary>UID range</primary></indexterm>
+<indexterm><primary>GID range</primary></indexterm>
+<indexterm><primary>daemon</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+The use of interdomain trusts requires use of <command>winbind</command>, so the
+<command>winbindd</command> daemon must be running. Winbind operation in this mode is
+dependent on the specification of a valid UID range and a valid GID range in the &smb.conf; file.
+These are specified respectively using:
+<smbconfblock>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+</smbconfblock>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>POSIX user accounts</primary></indexterm>
+<indexterm><primary>maximum value</primary></indexterm>
+<indexterm><primary>4294967295</primary></indexterm>
+The range of values specified must not overlap values used by the host operating system and must
+not overlap values used in the passdb backend for POSIX user accounts. The maximum value is
+limited by the upper-most value permitted by the host operating system. This is a UNIX kernel
+limited parameter. Linux kernel 2.6-based systems support a maximum value of 4294967295 
+(32-bit unsigned variable).
+</para>
+
+<note><para>
+<indexterm><primary>winbind</primary></indexterm>
+<indexterm><primary>trusting domain</primary></indexterm>
+<indexterm><primary>trusted domain</primary></indexterm>
+The use of winbind is necessary only when Samba is the trusting domain, not when it is the
+trusted domain.
+</para></note>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>scalability</primary></indexterm>
+<indexterm><primary>trust relationships</primary></indexterm>
+Samba-3 can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4-style
+trust relationships. This imparts to Samba scalability similar to that with MS Windows NT4.
+</para>
+
+<para>
+<indexterm><primary>scalable backend</primary></indexterm>
+<indexterm><primary>authentication database</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>interdomain trusts</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+Given that Samba-3 can function with a scalable backend authentication database such as LDAP, and given its
+ability to run in primary as well as backup domain control modes, the administrator would be well-advised to
+consider alternatives to the use of interdomain trusts simply because, by the very nature of how trusts
+function, this system is fragile.  That was, after all, a key reason for the development and adoption of
+Microsoft Active Directory.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Trust Relationship Background</title>
+
+<para>
+<indexterm><primary>security domains</primary></indexterm>
+<indexterm><primary>nonhierarchical</primary></indexterm>
+<indexterm><primary>security structure</primary></indexterm>
+<indexterm><primary>large organizations</primary></indexterm>
+<indexterm><primary>delegation</primary></indexterm>
+<indexterm><primary>administrative responsibilities</primary></indexterm>
+MS Windows NT3/4-type security domains employ a nonhierarchical security structure.
+The limitations of this architecture as it effects the scalability of MS Windows networking
+in large organizations is well known. Additionally, the flat namespace that results from
+this design significantly impacts the delegation of administrative responsibilities in
+large and diverse organizations.
+</para>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>Kerberos</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>limitations</primary></indexterm>
+<indexterm><primary>domain security</primary></indexterm>
+Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
+of circumventing the limitations of the older technologies. Not every organization is ready
+or willing to embrace ADS. For small companies the older NT4-style domain security paradigm
+is quite adequate, and so there remains an entrenched user base for whom there is no direct
+desire to go through a disruptive change to adopt ADS.
+</para>
+
+<para>
+<indexterm><primary>security domains</primary></indexterm>
+<indexterm><primary>access rights</primary></indexterm>
+<indexterm><primary>privileges</primary></indexterm>
+<indexterm><primary>trusts</primary></indexterm>
+<indexterm><primary>trusted domain</primary></indexterm>
+<indexterm><primary>trusting domain</primary></indexterm>
+<indexterm><primary>one direction</primary></indexterm>
+With Windows NT, Microsoft introduced the ability to allow different security domains
+to effect a mechanism so users from one domain may be given access rights and privileges
+in another domain. The language that describes this capability is couched in terms of
+<emphasis>trusts</emphasis>. Specifically, one domain will <emphasis>trust</emphasis> the users
+from another domain. The domain from which users can access another security domain is
+said to be a trusted domain. The domain in which those users have assigned rights and privileges
+is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only,
+so if users in both domains are to have privileges and rights in each others' domain, then it is
+necessary to establish two relationships, one in each direction.
+</para>
+
+<para>
+<indexterm><primary>security domain</primary></indexterm>
+<indexterm><primary>nontransitive</primary></indexterm>
+<indexterm><primary>trust relationship</primary></indexterm>
+<indexterm><primary>transitive</primary></indexterm>
+<indexterm><primary>explicit trust</primary></indexterm>
+Further, in an NT4-style MS security domain, all trusts are nontransitive. This means that if there are three
+domains (let's call them red, white, and blue), where red and white have a trust relationship, and white and
+blue have a trust relationship, then it holds that there is no implied trust between the red and blue domains.
+Relationships are explicit and not transitive.
+</para>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>security contexts</primary></indexterm>
+<indexterm><primary>trust relationships</primary></indexterm>
+<indexterm><primary>two-way trust</primary></indexterm>
+<indexterm><primary>Windows 2000</primary></indexterm>
+<indexterm><primary>security domains</primary></indexterm>
+<indexterm><primary>NT4-style domains</primary></indexterm>
+New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way by default.
+Also, all inter-ADS domain trusts are transitive. In the case of the red, white, and blue domains, with
+Windows 2000 and ADS, the red and blue domains can trust each other. This is an inherent feature of ADS
+domains. Samba-3 implements MS Windows NT4-style interdomain trusts and interoperates with MS Windows 200x ADS
+security domains in similar manner to MS Windows NT4-style domains.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Native MS Windows NT4 Trusts Configuration</title>
+
+<para>
+<indexterm><primary>Interdomain Trusts</primary><secondary>creating</secondary></indexterm>
+<indexterm><primary>two-way trust</primary></indexterm>
+<indexterm><primary>security credentials</primary></indexterm>
+There are two steps to creating an interdomain trust relationship. To effect a two-way trust
+relationship, it is necessary for each domain administrator to create a trust account for the 
+other domain to use in verifying security credentials.
+</para>
+
+
+<sect2>
+<title>Creating an NT4 Domain Trust</title>
+
+<para>
+<indexterm><primary>domain trust</primary></indexterm>
+<indexterm><primary>trust relationships</primary></indexterm>
+<indexterm><primary>>Domain User Manager</primary></indexterm>
+<indexterm><primary>remote domain</primary></indexterm>
+<indexterm><primary>standard confirmation</primary></indexterm>
+For MS Windows NT4, all domain trust relationships are configured using the 
+<application>Domain User Manager</application>. This is done from the Domain User Manager Policies
+entry on the menu bar. From the <guimenu>Policy</guimenu> menu, select
+<guimenuitem>Trust Relationships</guimenuitem>. Next to the lower box labeled
+<guilabel>Permitted to Trust this Domain</guilabel> are two buttons, <guibutton>Add</guibutton>
+and <guibutton>Remove</guibutton>. The <guibutton>Add</guibutton> button will open a panel in which
+to enter the name of the remote domain that will be able to assign access rights to users in 
+your domain. You will also need to enter a password for this trust relationship, which the 
+trusting domain will use when authenticating users from the trusted domain.
+The password needs to be typed twice (for standard confirmation).
+</para>
+
+</sect2>
+
+
+<sect2>
+<title>Completing an NT4 Domain Trust</title>
+
+<para>
+<indexterm><primary>trust relationship</primary></indexterm>
+<indexterm><primary>trusting domain</primary></indexterm>
+<indexterm><primary>trusted domain</primary></indexterm>
+<indexterm><primary>remote domain</primary></indexterm>
+<indexterm><primary>password assigned</primary></indexterm>
+<indexterm><primary>Interdomain Trusts</primary><secondary>Completing</secondary></indexterm>
+A trust relationship will work only when the other (trusting) domain makes the appropriate connections
+with the trusted domain. To consummate the trust relationship, the administrator launches the
+Domain User Manager from the menu selects <guilabel>Policies</guilabel>, then select
+<guilabel>Trust Relationships</guilabel>, and clicks on the <guibutton>Add</guibutton> button
+next to the box that is labeled <guilabel>Trusted Domains</guilabel>. A panel opens in which
+must be entered the name of the remote domain as well as the password assigned to that trust.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Interdomain Trust Facilities</title>
+
+
+<para>
+<indexterm><primary>two-way trust</primary></indexterm>
+<indexterm><primary>trust relationship</primary></indexterm>
+<indexterm><primary>trust established</primary></indexterm>
+<indexterm><primary>one-way trust</primary></indexterm>
+<indexterm><primary>Windows NT4 domains</primary></indexterm>
+<indexterm><primary>Interdomain Trusts</primary><secondary>Facilities</secondary></indexterm>
+A two-way trust relationship is created when two one-way trusts are created, one in each direction.
+Where a one-way trust has been established between two MS Windows NT4 domains (let's call them
+DomA and DomB), the following facilities are created:
+</para>
+
+<figure id="trusts1">
+	<title>Trusts overview.</title>
+	<imagefile>trusts1</imagefile>
+</figure>
+
+<itemizedlist>
+	<listitem><para>
+	DomA (completes the trust connection) <parameter>Trusts</parameter> DomB.
+	</para></listitem>
+
+	<listitem><para>
+	DomA is the <parameter>Trusting</parameter> domain.
+	</para></listitem>
+
+	<listitem><para>
+	DomB is the <parameter>Trusted</parameter> domain (originates the trust account).
+	</para></listitem>
+
+	<listitem><para>
+	Users in DomB can access resources in DomA.
+	</para></listitem>
+
+	<listitem><para>
+	Users in DomA cannot access resources in DomB.
+	</para></listitem>
+
+	<listitem><para>
+	Global groups from DomB can be used in DomA.
+	</para></listitem>
+
+	<listitem><para>
+	Global groups from DomA cannot be used in DomB.
+	</para></listitem>
+
+	<listitem><para>
+	DomB does appear in the logon dialog box on client workstations in DomA.
+	</para></listitem>
+
+	<listitem><para>
+	DomA does not appear in the logon dialog box on client workstations in DomB.
+	</para></listitem>
+</itemizedlist>
+
+<itemizedlist>
+	<listitem><para>
+	Users and groups in a trusting domain cannot be granted rights, permissions, or access
+	to a trusted domain.
+	</para></listitem>
+
+	<listitem><para>
+	The trusting domain can access and use accounts (users/global groups) in the
+	trusted domain.
+	</para></listitem>
+
+	<listitem><para>
+	Administrators of the trusted domain can be granted administrative rights in the 
+	trusting domain.
+	</para></listitem>
+
+	<listitem><para>
+	Users in a trusted domain can be given rights and privileges in the trusting
+	domain.
+	</para></listitem>
+
+	<listitem><para>
+	Trusted domain global groups can be given rights and permissions in the trusting
+	domain.
+	</para></listitem>
+
+	<listitem><para>
+	Global groups from the trusted domain can be made members in local groups on
+	MS Windows domain member machines.
+	</para></listitem>
+</itemizedlist>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Configuring Samba NT-Style Domain Trusts</title>
+
+<para>
+<indexterm><primary>interdomain trust</primary></indexterm>
+This description is meant to be a fairly short introduction about how to set up a Samba server so
+that it can participate in interdomain trust relationships. Trust relationship support in Samba
+is at an early stage, so do not be surprised if something does not function as it should.
+</para>
+
+<para>
+<indexterm><primary>peer domain</primary></indexterm>
+<indexterm><primary>trust relationship</primary></indexterm>
+<indexterm><primary>Windows NT4 Server</primary></indexterm>
+<indexterm><primary>between domains</primary></indexterm>
+Each of the procedures described next assumes the peer domain in the trust relationship is controlled by a
+Windows NT4 server. However, the remote end could just as well be another Samba-3  domain. It can be clearly
+seen, after reading this document, that combining Samba-specific parts of what's written in the following
+sections leads to trust between domains in a purely Samba environment.
+</para>
+
+<sect2 id="samba-trusted-domain">
+<title>Samba as the Trusted Domain</title>
+
+<para>
+<indexterm><primary>trusted party</primary></indexterm>
+<indexterm><primary>special account</primary></indexterm>
+<indexterm><primary>trusting party</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+In order to set the Samba PDC to be the trusted party of the relationship, you first need
+to create a special account for the domain that will be the trusting party. To do that,
+you can use the <command>smbpasswd</command> utility. Creating the trusted domain account is 
+similar to creating a trusted machine account. Suppose, your domain is
+called SAMBA, and the remote domain is called RUMBA. The first step
+will be to issue this command from your favorite shell:
+</para>
+
+<para>
+<screen>
+&rootprompt; <userinput>smbpasswd -a -i rumba</userinput>
+New SMB password: <userinput>XXXXXXXX</userinput>
+Retype SMB password: <userinput>XXXXXXXX</userinput>
+Added user rumba$
+</screen>
+
+where <option>-a</option> means to add a new account into the
+passdb database and <option>-i</option> means to <quote>create this
+account with the Interdomain trust flag</quote>.
+</para>
+
+<para>
+<indexterm><primary>account name</primary></indexterm>
+<indexterm><primary>remote domain</primary></indexterm>
+<indexterm><primary>password database</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+The account name will be <quote>rumba$</quote> (the name of the remote domain).
+If this fails, you should check that the trust account has been added to the system
+password database (<filename>/etc/passwd</filename>). If it has not been added, you
+can add it manually and then repeat the previous step.
+</para>
+
+<para>
+<indexterm><primary>password</primary></indexterm>
+<indexterm><primary>new account</primary></indexterm>
+<indexterm><primary>confirm the trust</primary></indexterm>
+<indexterm><primary>Windows NT Server</primary></indexterm>
+After issuing this command, you will be asked to enter the password for the account. You can use any password
+you want, but be aware that Windows NT will not change this password until 7 days following account creation.
+After the command returns successfully, you can look at the entry for the new account (in the standard way as
+appropriate for your configuration) and see that the account's name is really RUMBA$ and it has the
+<quote>I</quote> flag set in the flags field. Now you are ready to confirm the trust by establishing it from
+Windows NT Server.
+</para>
+
+
+<para>
+<indexterm><primary>User Manager</primary></indexterm>
+<indexterm><primary>trusted domain name</primary></indexterm>
+<indexterm><primary>relationship password</primary></indexterm>
+<indexterm><primary>remote domain</primary></indexterm>
+<indexterm><primary>established</primary></indexterm>
+Open <application>User Manager for Domains</application> and from the <guimenu>Policies</guimenu> menu, select
+<guimenuitem>Trust Relationships...</guimenuitem>.  Beside the <guilabel>Trusted domains</guilabel> list box,
+click the <guimenu>Add...</guimenu> button. You will be prompted for the trusted domain name and the
+relationship password. Type in SAMBA, as this is the name of the remote domain and the password used at the
+time of account creation.  Click on <guibutton>OK</guibutton> and, if everything went without incident, you
+will see the <computeroutput>Trusted domain relationship successfully established</computeroutput> message.
+</para>
+
+</sect2>
+<sect2>
+<title>Samba as the Trusting Domain</title>
+
+<para>
+<indexterm><primary>NT-controlled domain</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+This time activities are somewhat reversed. Again, we'll assume that your domain
+controlled by the Samba PDC is called SAMBA and the NT-controlled domain is called RUMBA.
+</para>
+
+<para>
+The very first step is to add an account for the SAMBA domain on RUMBA's PDC.
+</para>
+
+
+<para>
+<indexterm><primary>User Manager</primary></indexterm>
+<indexterm><primary>trusted domain</primary></indexterm>
+<indexterm><primary>password</primary></indexterm>
+Launch the <application>Domain User Manager</application>, then from the menu select
+<guimenu>Policies</guimenu>, <guimenuitem>Trust Relationships</guimenuitem>.
+Now, next to the <guilabel>Trusting Domains</guilabel> box, press the <guibutton>Add</guibutton>
+button and type in the name of the trusted domain (SAMBA) and the password to use in securing
+the relationship.
+</para>
+
+<para>
+<indexterm><primary>password</primary></indexterm>
+<indexterm><primary>confirm the password</primary></indexterm>
+The password can be arbitrarily chosen. It is easy to change the password from the Samba server whenever you
+want. After you confirm the password, your account is ready for use. Now its Samba's turn.
+</para>
+
+<para>
+Using your favorite shell while logged in as root, issue this command:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom establish</tertiary></indexterm>
+</para>
+
+<para>
+&rootprompt;<userinput>net rpc trustdom establish rumba</userinput>
+</para>
+
+<para>
+<indexterm><primary>password</primary></indexterm>
+<indexterm><primary>interdomain connection</primary></indexterm>
+<indexterm><primary>ordinary connection</primary></indexterm>
+You will be prompted for the password you just typed on your Windows NT4 Server box.
+An error message, <literal>"NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT,"</literal>
+that may be reported periodically is of no concern and may safely be ignored.
+It means the password you gave is correct and the NT4 server says the account is ready for
+interdomain connection and not for ordinary connection.  After that, be patient;
+it can take a while (especially in large networks), but eventually you should see
+the <literal>Success</literal> message. Congratulations! Your trust
+relationship has just been established.
+</para>
+
+<note><para>
+You have to run this command as root because you must have write access to
+the <filename>secrets.tdb</filename> file.
+</para></note>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>NT4-Style Domain Trusts with Windows 2000</title>
+
+<para>
+<indexterm><primary>trust relationship</primary></indexterm>
+<indexterm><primary>Windows 2000 server</primary></indexterm>
+<indexterm><primary>NT4-style</primary></indexterm>
+<indexterm><primary>mixed mode</primary></indexterm>
+Although <application>Domain User Manager</application> is not present in Windows 2000, it is 
+also possible to establish an NT4-style trust relationship with a Windows 2000 domain 
+controller running in mixed mode as the trusting server. It should also be possible for 
+Samba to trust a Windows 2000 server; however, more testing is still needed in this area.
+</para>
+
+<para>
+<indexterm><primary>interdomain trust</primary></indexterm>
+<indexterm><primary>trust account</primary></indexterm>
+<indexterm><primary>not transitive</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+After <link linkend="samba-trusted-domain">creating the interdomain trust account on the Samba server</link>
+as described previously, open <application>Active Directory Domains and Trusts</application> on the AD
+controller of the domain whose resources you wish Samba users to have access to. Remember that since NT4-style
+trusts are not transitive, if you want your users to have access to multiple mixed-mode domains in your AD
+forest, you will need to repeat this process for each of those domains. With <application>Active Directory
+domains and trusts</application> open, right-click on the name of the Active Directory domain that will trust
+our Samba domain and choose <guimenuitem>Properties</guimenuitem>, then click on the
+<guilabel>Trusts</guilabel> tab. In the upper part of the panel, you will see a list box labeled
+<guilabel>Domains trusted by this domain:</guilabel> and an <guilabel>Add...</guilabel> button next to it.
+Press this button and, just as with NT4, you will be prompted for the trusted domain name and the relationship
+password. Press <emphasis>OK</emphasis> and after a moment, Active Directory will respond with
+<computeroutput>The trusted domain has been added and the trust has been verified.</computeroutput> Your
+Samba users can now be granted access to resources in the AD domain.
+</para>
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+Interdomain trust relationships should not be attempted on networks that are unstable
+or that suffer regular outages. Network stability and integrity are key concerns with
+distributed trusted domains.
+</para>
+
+<sect2>
+<title>Browsing of Trusted Domain Fails</title>
+
+<para>
+<emphasis>Browsing from a machine in a trusted Windows 200x domain to a Windows 200x member of
+a trusting Samba domain, I get the following error:</emphasis>
+<screen>
+The system detected a possible attempt to compromise security. Please
+ensure that you can contact the server that authenticated you.
+</screen>
+</para>
+
+<para>
+<emphasis>The event logs on the box I'm trying to connect to have entries regarding group
+policy not being applied because it is a member of a down-level domain.</emphasis>
+</para>
+
+<para>If there is a computer account in the Windows
+200x domain for the machine in question, and it is disabled, this problem can
+occur.  If there is no computer account (removed or never existed), or if that 
+account is still intact (i.e., you just joined it to another domain), everything 
+seems to be fine. By default, when you unjoin a domain (the Windows 200x 
+domain), the computer tries to automatically disable the computer account in 
+the domain.  If you are running as an account that has privileges to do this 
+when you unjoin the machine, it is done; otherwise it is not done.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Problems with LDAP ldapsam and Older Versions of smbldap-tools</title>
+
+<para>
+If you use the <command>smbldap-useradd</command> script to create a trust
+account to set up interdomain trusts, the process of setting up the trust will
+fail. The account that was created in the LDAP database will have an account
+flags field that has <literal>[W          ]</literal>, when it must have
+<literal>[I          ]</literal> for interdomain trusts to work.
+</para>
+
+<para>Here is a simple solution.
+Create a machine account as follows:
+<screen>
+&rootprompt; smbldap-useradd -w domain_name
+</screen>
+Then set the desired trust account password as shown here:
+<screen>
+&rootprompt; smbldap-passwd domain_name\$
+</screen>
+Using a text editor, create the following file:
+<screen>
+dn: uid=domain_name$,ou=People,dc={your-domain},dc={your-top-level-domain}
+changetype: modify
+sambaAcctFlags: [I         ]
+</screen>
+Then apply the text file to the LDAP database as follows:
+<screen>
+&rootprompt; ldapmodify -x -h localhost \
+ -D "cn=Manager,dc={your-domain},dc={your-top-level-domain}" \
+ -W -f /path-to/foobar
+</screen>
+Create a single-sided trust under the NT4 Domain User Manager, then execute:
+<screen>
+&rootprompt; net rpc trustdom establish domain_name
+</screen>
+</para>
+
+<para>
+It works with Samba-3  and NT4 domains, and also with Samba-3 and Windows 200x ADS in mixed mode.
+Both domain controllers, Samba and NT must have the same WINS server; otherwise,
+the trust will never work. 
+</para>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-IntroSMB.xml b/docs-xml/Samba3-HOWTO/TOSHARG-IntroSMB.xml
new file mode 100644
index 00000000000..dec4638e5b0
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-IntroSMB.xml
@@ -0,0 +1,224 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<preface id="IntroSMB">
+<prefaceinfo>
+	&author.jht;
+	<pubdate>June 29, 2003</pubdate>
+</prefaceinfo>
+
+<title>Introduction</title>
+
+<para><quote>
+A man's gift makes room for him before great men. Gifts are like hooks that can catch
+hold of the mind taking it beyond the reach of forces that otherwise might constrain it.
+</quote> --- Anon.
+</para>
+
+
+<para>
+This is a book about Samba. It is a tool, a derived work of the labors
+of many and of the diligence and goodwill of more than a few.
+This book contains material that has been contributed in a persistent belief
+that each of us can add value to our neighbors as well as to those who will
+follow us.
+</para>
+
+<para>
+This book is designed to meet the needs of the Microsoft network administrator.
+UNIX administrators will benefit from this book also, though they may complain
+that it is hard to find the information they think they need. So if you are a
+Microsoft certified specialist, this book should meet your needs rather well.
+If you are a UNIX or Linux administrator, there is no need to feel badly &smbmdash; you
+should have no difficulty finding answers to your current concerns also.
+</para>
+
+<sect1>
+<title>What Is Samba?</title>
+
+	<para>
+	Samba is a big, complex project. The Samba project is ambitious and exciting.
+	The team behind Samba is a group of some thirty individuals who are spread
+	the world over and come from an interesting range of backgrounds. This team
+	includes scientists, engineers, programmers, business people, and students.
+	</para>
+
+	<para>
+	Team members were drawn into active participation through the desire to help
+	deliver an exciting level of transparent interoperability between Microsoft
+	Windows and the non-Microsoft information
+	technology world. 
+	</para>
+
+	<para>
+	The slogan that unites the efforts behind the Samba project says:
+	<emphasis>Samba, Opening Windows to a Wider World!</emphasis> The goal
+	behind the project is one of removing barriers to interoperability.
+	</para>
+
+	<para>
+	Samba provides file and print services for Microsoft Windows clients. These
+	services may be hosted off any TCP/IP-enabled platform. The original deployment
+	platforms were UNIX and Linux, though today it is in common use across
+	a broad variety of systems.
+	</para>
+
+	<para>
+	The Samba project includes not only an impressive feature set in file and print
+	serving capabilities, but has been extended to include client functionality,
+	utilities to ease migration to Samba, tools to aid interoperability with
+	Microsoft Windows, and administration tools.
+	</para>
+
+	<para>
+	The real people behind Samba are users like you. You have inspired the
+	developers (the Samba Team) to do more than any of them imagined could or should
+	be done. User feedback drives Samba development. Samba-3 in particular incorporates
+	a huge amount of work done as a result of user requests, suggestions and direct
+	code contributions.
+	</para>
+
+</sect1>
+
+<sect1>
+<title>Why This Book?</title>
+
+	<para>
+	There is admittedly a large number of Samba books on the market today and
+	each book has its place. Despite the apparent plethora of books, Samba
+	as a project continues to receive much criticism for failing to provide
+	sufficient documentation. Samba is also criticized for being too complex
+	and too difficult to configure. In many ways this is evidence of the
+	success of Samba as there would be no complaints if it was not successful.
+	</para>
+
+	<para>
+	The Samba Team members work predominantly with UNIX and Linux, so
+	it is hardly surprising that existing Samba documentation should reflect
+	that orientation. The original HOWTO text documents were intended to provide
+	some tips, a few golden nuggets, and if they helped anyone then that was
+	just wonderful. But the HOWTO documents lacked structure and context. They were
+	isolated snapshots of information that were written to pass information
+	on to someone else who might benefit. They reflected a need to transmit
+	more information that could be conveniently put into manual pages.
+	</para>
+
+	<para>
+	The original HOWTO documents were written by different authors. Most HOWTO
+	documents are the result of feedback and contributions from numerous
+	authors. In this book we took care to preserve as much original content as
+	possible. As you read this book you will note that chapters were written by
+	multiple authors, each of whom has his own style. This demonstrates
+	the nature of the Open Source software development process.
+	</para>
+
+	<para>
+	Out of the original HOWTO documents sprang a collection of unofficial
+	HOWTO documents that are spread over the Internet. It is sincerely intended
+	that this work will <emphasis>not</emphasis> replace the valuable unofficial 
+	HOWTO work that continues to flourish. If you are involved in unofficial 
+	HOWTO production then please continue your work!
+	</para>
+
+	<para>
+	Those of you who have dedicated your labors to the production of unofficial
+	HOWTOs, to Web page information regarding Samba, or to answering questions
+	on the mailing lists or elsewhere, may be aware that this is a labor
+	of love. We would like to know about your contribution and willingly receive
+	the precious pearls of wisdom you have collected. Please email your contribution to
+	<ulink noescape="1" url="mailto:jht@samba.org">John H. Terpstra (jht@samba.org)</ulink>.
+	As a service to other users we will gladly adopt material that is technically accurate.
+	</para>
+
+	<para>
+	Existing Samba books are largely addressed to the UNIX administrator.
+	From the perspective of this target group the existing books serve
+	an adequate purpose, with one exception &smbmdash; now that Samba-3 is out
+	they need to be updated!
+	</para>
+
+	<para>
+	This book, the <emphasis>Official Samba-3 HOWTO and Reference Guide</emphasis>,
+	includes the Samba-HOWTO-Collection.pdf that ships with Samba.
+	These documents have been written with a new design intent and purpose.
+	</para>
+
+	<para>
+	Over the past two years many Microsoft network administrators have adopted
+	Samba and have become interested in its deployment. Their information needs
+	are very different from that of the UNIX administrator. This book has been
+	arranged and the information presented from the perspective of someone with previous
+	Microsoft Windows network administrative training and experience.
+	</para>
+
+</sect1>
+
+<sect1>
+<title>Book Structure and Layout</title>
+
+	<para>
+	This book is presented in six parts:
+	</para>
+
+	<variablelist>
+		<varlistentry><term>General Installation</term>
+			<listitem><para>
+			Designed to help you get Samba-3 running quickly.
+			The Fast Start chapter is a direct response to requests from
+			Microsoft network administrators for some sample configurations
+			that <emphasis>just work</emphasis>.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>Server Configuration Basics</term>
+			<listitem><para>
+			The purpose of this section is to aid the transition from existing
+			Microsoft Windows network knowledge to Samba terminology and norms.
+			The chapters in this part each cover the installation of one type of 
+			Samba server.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>Advanced Configuration</term>
+			<listitem><para>
+			The mechanics of network browsing have long been the Achilles heel of
+			all Microsoft Windows users. Samba-3 introduces new user and machine
+			account management facilities, a new way to map UNIX groups and Windows
+			groups, Interdomain trusts, new loadable file system drivers (VFS), and
+			more. New with this document is expanded printing documentation, as well
+			as a wealth of information regarding desktop and user policy handling,
+			use of desktop profiles, and techniques for enhanced network integration.
+			This section makes up the core of the book. Read and enjoy.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>Migration and Updating</term>
+			<listitem><para>
+			A much requested addition to the book is information on how to migrate
+			from Microsoft Windows NT4 to Samba-3, as well as an overview of what the
+			issues are when moving from Samba-2.x to Samba-3.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>Troubleshooting</term>
+			<listitem><para>
+			This short section should help you when all else fails.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>Reference Section</term>
+			<listitem><para>
+			Here you will find a collection of things that are either too peripheral
+			for most users, or are a little left of field to be included in the
+			main body of information.
+			</para></listitem>
+		</varlistentry>
+	</variablelist>
+		
+<para>
+Welcome to Samba-3 and the first published document to help you and your users to enjoy a whole
+new world of interoperability between Microsoft Windows and the rest of the world.
+</para>
+
+</sect1>
+
+</preface>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-LargeFile.xml b/docs-xml/Samba3-HOWTO/TOSHARG-LargeFile.xml
new file mode 100644
index 00000000000..5fdbe7a2434
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-LargeFile.xml
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="largefile">
+<chapterinfo>
+	&author.jeremy;
+	&author.jht;
+	<pubdate>March 5, 2005</pubdate>
+</chapterinfo>
+<title>Handling Large Directories</title>
+
+<para>
+<indexterm><primary>performance degradation</primary></indexterm>
+<indexterm><primary>large numbers of files</primary></indexterm>
+<indexterm><primary>large directory</primary></indexterm>
+Samba-3.0.12 and later implements a solution for sites that have experienced performance degradation due to the
+problem of using Samba-3 with applications that need large numbers of files (100,000 or more) per directory.
+</para>
+
+<para>
+<indexterm><primary>read directory into memory</primary></indexterm>
+<indexterm><primary>strange delete semantics</primary></indexterm>
+The key was fixing the directory handling to read only the current list requested instead of the old
+(up to samba-3.0.11) behavior of reading the entire directory into memory before doling out names.
+Normally this would have broken OS/2 applications, which have very strange delete semantics, but by
+stealing logic from Samba4 (thanks, Tridge), the current code in 3.0.12 handles this correctly.
+</para>
+
+<para>
+<indexterm><primary>large directory</primary></indexterm>
+<indexterm><primary>performance</primary></indexterm>
+To set up an application that needs large numbers of files per directory in a way that does not
+damage performance unduly, follow these steps:
+</para>
+
+<para>
+<indexterm><primary>canonicalize files</primary></indexterm>
+First, you need to canonicalize all the files in the directory to have one case, upper or lower &smbmdash; take your
+pick (I chose upper because all my files were already uppercase names). Then set up a new custom share for the
+application as follows:
+<smbconfblock>
+<smbconfsection name="[bigshare]"/>
+<smbconfoption name="path">/data/manyfilesdir</smbconfoption>
+<smbconfoption name="read only">no</smbconfoption>
+<smbconfoption name="case sensitive">True</smbconfoption>
+<smbconfoption name="default case">upper</smbconfoption>
+<smbconfoption name="preserve case">no</smbconfoption>
+<smbconfoption name="short preserve case">no</smbconfoption>
+</smbconfblock>
+</para>
+
+<para>
+<indexterm><primary>case options</primary></indexterm>
+<indexterm><primary>match case</primary></indexterm>
+<indexterm><primary>uppercase</primary></indexterm>
+Of course, use your own path and settings, but set the case options to match the case of all the files in your
+directory. The path should point at the large directory needed for the application &smbmdash; any new files created in
+there and in any paths under it will be forced by smbd into uppercase, but smbd will no longer have to scan
+the directory for names: it knows that if a file does not exist in uppercase, then it doesn't exist at all.
+</para>
+
+<para>
+<indexterm><primary>case-insensitive</primary></indexterm>
+<indexterm><primary>consistent case</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+The secret to this is really in the <smbconfoption name="case sensitive">True</smbconfoption>
+line. This tells smbd never to scan for case-insensitive versions of names. So if an application asks for a file
+called <filename>FOO</filename>, and it cannot be found by a simple stat call, then smbd will return file not
+found immediately without scanning the containing directory for a version of a different case. The other
+<filename>xxx case xxx</filename> lines make this work by forcing a consistent case on all files created by
+&smbd;.
+</para>
+
+<para>
+<indexterm><primary>uppercase</primary></indexterm>
+<indexterm><primary>stanza</primary></indexterm>
+<indexterm><primary>lowercase filenames</primary></indexterm>
+Remember, all files and directories under the <parameter>path</parameter> directory must be in uppercase
+with this &smb.conf; stanza because &smbd; will not be able to find lowercase filenames with these settings. Also
+note that this is done on a per-share basis, allowing this parameter to be set only for a share servicing an application with
+this problematic behavior (using large numbers of entries in a directory) &smbmdash; the rest of your &smbd; shares
+don't need to be affected.
+</para>
+
+<para>
+This makes smbd much faster when dealing with large directories.  My test case has over 100,000 files, and
+smbd now deals with this very efficiently.
+</para>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-NT4Migration.xml b/docs-xml/Samba3-HOWTO/TOSHARG-NT4Migration.xml
new file mode 100644
index 00000000000..2688e060ac6
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-NT4Migration.xml
@@ -0,0 +1,631 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="NT4Migration">
+<chapterinfo>
+	&author.jht;
+	<pubdate>April 3, 2003</pubdate>
+</chapterinfo>
+
+<title>Migration from NT4 PDC to Samba-3 PDC</title>
+
+<para>
+<indexterm><primary>migrate</primary></indexterm>
+<indexterm><primary>domain control</primary></indexterm>
+This is a rough guide to assist those wishing to migrate from NT4 domain control to
+Samba-3-based domain control.
+</para>
+
+<sect1>
+<title>Planning and Getting Started</title>
+
+<para>
+<indexterm><primary>show-stopper-type</primary></indexterm>
+In the IT world there is often a saying that all problems are encountered because of
+poor planning. The corollary to this saying is that not all problems can be anticipated
+and planned for. Then again, good planning will anticipate most show-stopper-type situations.
+</para>
+
+<para>
+<indexterm><primary>migration plan</primary></indexterm>
+Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control
+environment would do well to develop a detailed migration plan. So here are a few pointers to
+help migration get underway.
+</para>
+
+<sect2>
+<title>Objectives</title>
+
+<para>
+<indexterm><primary>migration process</primary></indexterm>
+The key objective for most organizations is to make the migration from MS Windows NT4 
+to Samba-3 domain control as painless as possible. One of the challenges you may experience
+in your migration process may well be convincing management that the new environment
+should remain in place. Many who have introduced open source technologies have experienced
+pressure to return to a Microsoft-based platform solution at the first sign of trouble. 
+</para>
+
+<para>
+<indexterm><primary>change motivations</primary></indexterm>
+Before attempting a migration to a Samba-3-controlled network, make every possible effort to
+gain all-round commitment to the change. Know precisely <emphasis>why</emphasis> the change
+is important for the organization. Possible motivations to make a change include:
+</para>
+
+<indexterm><primary>manageability</primary></indexterm>
+<indexterm><primary>functionality</primary></indexterm>
+<indexterm><primary>operating costs</primary></indexterm>
+<indexterm><primary>support exposure</primary></indexterm>
+<indexterm><primary>licensing</primary></indexterm>
+
+<itemizedlist>
+    <listitem><para>Improve network manageability.</para></listitem>
+    <listitem><para>Obtain better user-level functionality.</para></listitem>
+    <listitem><para>Reduce network operating costs.</para></listitem>
+    <listitem><para>Reduce exposure caused by Microsoft withdrawal of NT4 support.</para></listitem>
+    <listitem><para>Avoid MS License 6 implications.</para></listitem>
+    <listitem><para>Reduce organization's dependency on Microsoft.</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>alternative solution</primary></indexterm>
+<indexterm><primary>advantages</primary></indexterm>
+<indexterm><primary>core values</primary></indexterm>
+<indexterm><primary>migration</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>without ADS</primary></indexterm>
+Make sure everyone knows that Samba-3 is not MS Windows NT4. Samba-3 offers
+an alternative solution that is both different from MS Windows NT4 and offers 
+advantages compared with it. Gain recognition that Samba-3 lacks many of the
+features that Microsoft has promoted as core values in migration from MS Windows NT4 to 
+MS Windows 2000 and beyond (with or without Active Directory services).
+</para>
+
+<para>
+What are the features that Samba-3 cannot provide?
+</para>
+
+<indexterm><primary>Active Directory Server</primary></indexterm>
+<indexterm><primary>Group Policy Objects</primary></indexterm>
+<indexterm><primary>Machine Policy Objects</primary></indexterm>
+<indexterm><primary>Logon Scripts</primary></indexterm>
+<indexterm><primary>Access Controls</primary></indexterm>
+
+<itemizedlist>
+	<listitem><para>Active Directory Server.</para></listitem>
+	<listitem><para>Group Policy Objects (in Active Directory).</para></listitem>
+	<listitem><para>Machine Policy Objects.</para></listitem>
+	<listitem><para>Logon Scripts in Active Directory.</para></listitem>
+	<listitem><para>Software Application and Access Controls in Active Directory.</para></listitem>
+</itemizedlist>
+
+<para>
+The features that Samba-3 does provide and that may be of compelling interest to your site
+include:
+</para>
+
+<indexterm><primary>ownership cost</primary></indexterm>
+<indexterm><primary>Global support</primary></indexterm>
+<indexterm><primary>Dynamic SMB servers</primary></indexterm>
+<indexterm><primary>on-the-fly logon scripts</primary></indexterm>
+<indexterm><primary>on-the-fly policy files</primary></indexterm>
+<indexterm><primary>stability</primary></indexterm>
+<indexterm><primary>reliability</primary></indexterm>
+<indexterm><primary>performance</primary></indexterm>
+<indexterm><primary>availability</primary></indexterm>
+<indexterm><primary>Manageability</primary></indexterm>
+<indexterm><primary>backend authentication</primary></indexterm>
+<indexterm><primary>tdbsam</primary></indexterm>
+<indexterm><primary>ldapsam</primary></indexterm>
+<indexterm><primary>single-sign-on</primary></indexterm>
+<indexterm><primary>distribute authentication systems</primary></indexterm>
+
+<itemizedlist>
+	<listitem><para>Lower cost of ownership.</para></listitem>
+	<listitem><para>Global availability of support with no strings attached.</para></listitem>
+	<listitem><para>Dynamic SMB servers (can run more than one SMB/CIFS server per UNIX/Linux system).</para></listitem>
+	<listitem><para>Creation of on-the-fly logon scripts.</para></listitem>
+	<listitem><para>Creation of on-the-fly policy files.</para></listitem>
+	<listitem><para>Greater stability, reliability, performance, and availability.</para></listitem>
+	<listitem><para>Manageability via an SSH connection.</para></listitem>
+	<listitem><para>Flexible choices of backend authentication technologies (tdbsam, ldapsam).</para></listitem>
+	<listitem><para>Ability to implement a full single-sign-on architecture.</para></listitem>
+	<listitem><para>Ability to distribute authentication systems for absolute minimum wide-area network bandwidth demand.</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>successful migration</primary></indexterm>
+Before migrating a network from MS Windows NT4 to Samba-3, consider all necessary factors. Users
+should be educated about changes they may experience so the change will be a welcome one
+and not become an obstacle to the work they need to do. The following sections explain factors that will 
+help ensure a successful migration.
+</para>
+
+<sect3>
+<title>Domain Layout</title>
+
+<para>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>backup domain controller</primary></indexterm>
+<indexterm><primary>secondary controller</primary></indexterm>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>standalone server</primary></indexterm>
+<indexterm><primary>network security</primary></indexterm>
+<indexterm><primary>domain context</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDCs</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>authentication backend</primary></indexterm>
+<indexterm><primary>complex organization</primary></indexterm>
+<indexterm><primary>LDAP database</primary></indexterm>
+<indexterm><primary>master server</primary></indexterm>
+<indexterm><primary>slave servers</primary></indexterm>
+<indexterm><primary>multiple domains</primary></indexterm>
+Samba-3 can be configured as a domain controller, a backup domain controller (probably best called
+a secondary controller), a domain member, or a standalone server. The Windows network security
+domain context should be sized and scoped before implementation. Particular attention needs to be
+paid to the location of the Primary Domain Controller (PDC) as well as backup controllers (BDCs).
+One way in which Samba-3 differs from Microsoft technology is that if one chooses to use an LDAP
+authentication backend, then the same database can be used by several different domains. In a
+complex organization, there can be a single LDAP database, which itself can be distributed (have
+a master server and multiple slave servers) that can simultaneously serve multiple domains.
+</para>
+
+<para>
+<indexterm><primary>network bandwidth</primary></indexterm>
+From a design perspective, the number of users per server as well as the number of servers per
+domain should be scaled taking into consideration server capacity and network bandwidth.
+</para>
+
+<para>
+<indexterm><primary>network segment</primary></indexterm>
+<indexterm><primary>multiple network segments</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>ping</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>remote segment</primary></indexterm>
+A physical network segment may house several domains. Each may span multiple network segments.
+Where domains span routed network segments, consider and test the performance implications of
+the design and layout of a network. A centrally located domain controller that is designed to
+serve multiple routed network segments may result in severe performance problems. Check the
+response time (ping timing) between the remote segment and the PDC. If it's long (more than 100 ms),
+locate a BDC on the remote segment to serve as the local authentication and access control server.
+</para>
+</sect3>
+
+<sect3>
+<title>Server Share and Directory Layout</title>
+
+<para>
+<indexterm><primary>Simplicity is king</primary></indexterm>
+<indexterm><primary>well-controlled network</primary></indexterm>
+There are cardinal rules to effective network design that cannot be broken with impunity.
+The most important rule: Simplicity is king in every well-controlled network. Every part of
+the infrastructure must be managed; the more complex it is, the greater will be the demand
+of keeping systems secure and functional.
+</para>
+
+<para>
+<indexterm><primary>disk space</primary></indexterm>
+<indexterm><primary>backed up</primary></indexterm>
+<indexterm><primary>tape</primary></indexterm>
+<indexterm><primary>backup</primary></indexterm>
+<indexterm><primary>validate every backup</primary></indexterm>
+<indexterm><primary>disaster recovery</primary></indexterm>
+Keep in mind the nature of how data must be shared. Physical disk space layout should be considered
+carefully. Some data must be backed up. The simpler the disk layout, the easier it will be to
+keep track of backup needs. Identify what backup media will meet your needs; consider backup to tape,
+CD-ROM or DVD-ROM, or other offline storage medium. Plan and implement for minimum
+maintenance. Leave nothing to chance in your design; above all, do not leave backups to chance:
+backup, test, and validate every backup; create a disaster recovery plan and prove that it works.
+</para>
+
+<para>
+<indexterm><primary>access control needs</primary></indexterm>
+<indexterm><primary>group permissions</primary></indexterm>
+<indexterm><primary>sticky bit</primary></indexterm>
+Users should be grouped according to data access control needs. File and directory access 
+is best controlled via group permissions, and the use of the <quote>sticky bit</quote> on group-controlled
+directories may substantially avoid file access complaints from Samba share users.
+</para>
+
+<para>
+<indexterm><primary>network administrators</primary></indexterm>
+<indexterm><primary>document design</primary></indexterm>
+<indexterm><primary>simple access controls</primary></indexterm>
+<indexterm><primary>obtuse complexity</primary></indexterm>
+<indexterm><primary>document design</primary></indexterm>
+Inexperienced  network administrators often attempt elaborate techniques to set access
+controls on files, directories, shares, as well as in share definitions.
+Keep your design and implementation simple and document your design extensively. Have others
+audit your documentation. Do not create a complex mess that your successor will not understand.
+Remember, job security through complex design and implementation may cause loss of operations
+and downtime to users as the new administrator learns to untangle your knots. Keep access
+controls simple and effective, and make sure that users will never be interrupted by obtuse
+complexity.
+</para>
+</sect3>
+
+<sect3>
+<title>Logon Scripts</title>
+
+<para>
+<indexterm><primary>Logon scripts</primary></indexterm>
+Logon scripts can help to ensure that all users gain the share and printer connections they need.
+</para>
+
+<para>
+Logon scripts can be created on the fly so all commands executed are specific to the
+rights and privileges granted to the user. The preferred controls should be effected through
+group membership so group information can be used to create a custom logon script using
+the <smbconfoption name="root preexec"/> parameters to the <smbconfsection name="NETLOGON"/> share.
+</para>
+
+<para>
+<indexterm><primary>kixstart</primary></indexterm>
+Some sites prefer to use a tool such as <command>kixstart</command> to establish a controlled
+user environment. In any case, you may wish to do a Google search for logon script process controls.
+In particular, you may wish to explore the use of the Microsoft Knowledge Base article KB189105 that
+deals with how to add printers without user intervention via the logon script process.
+</para>
+</sect3>
+
+<sect3>
+<title>Profile Migration/Creation</title>
+
+<para>
+User and group profiles may be migrated using the tools described in the section titled Desktop Profile
+Management.
+</para>
+
+
+<para>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>NTuser.DAT</primary></indexterm>
+Profiles may also be managed using the Samba-3 tool <command>profiles</command>. This tool allows the MS
+Windows NT-style security identifiers (SIDs) that are stored inside the profile
+<filename>NTuser.DAT</filename> file to be changed to the SID of the Samba-3 domain.
+</para>
+</sect3>
+
+<sect3>
+<title>User and Group Accounts</title>
+
+<para>
+<indexterm><primary>migrate account settings</primary></indexterm>
+<indexterm><primary>migrate user</primary></indexterm>
+<indexterm><primary>migrate group</primary></indexterm>
+<indexterm><primary>map</primary></indexterm>
+It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before
+attempting to migrate user and group accounts, you are STRONGLY advised to create in Samba-3 the
+groups that are present on the MS Windows NT4 domain <emphasis>AND</emphasis> to map them to
+suitable UNIX/Linux groups. By following this simple advice, all user and group attributes
+should migrate painlessly.
+</para>
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>Steps in Migration Process</title>
+
+<para>
+The approximate migration process is described below.
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	You have an NT4 PDC that has the users, groups, policies, and profiles to be migrated.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>netlogon share</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+	Samba-3 is set up as a domain controller with netlogon share, profile share, and so on. Configure the &smb.conf; file
+	to function as a BDC: <parameter>domain master = No</parameter>.
+	</para></listitem>
+</itemizedlist>
+
+<procedure>
+<title>The Account Migration Process</title>
+
+	<step><para>
+	<indexterm><primary>pdbedit</primary></indexterm>
+	Create a BDC account in the old NT4 domain for the Samba server using NT Server Manager.
+	<emphasis>Samba must not be running.</emphasis>
+	</para></step>
+
+	<step><para>
+	<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+	<userinput>net rpc join -S <replaceable>NT4PDC</replaceable> -w <replaceable>DOMNAME</replaceable> -U
+	Administrator%<replaceable>passwd</replaceable></userinput>
+	</para></step>
+
+	<step><para>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>vampire</tertiary></indexterm>
+	<userinput>net rpc vampire -S <replaceable>NT4PDC</replaceable> -U 
+	administrator%<replaceable>passwd</replaceable></userinput>
+	</para></step>
+
+<indexterm><primary>pdbedit</primary></indexterm>
+	<step><para><userinput>pdbedit -L</userinput></para>
+		<para>Note: Did the users migrate?</para>
+	</step>
+
+	<step><para>
+	<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
+	<indexterm><primary>initGroups.sh</primary></indexterm>
+	Now assign each of the UNIX groups to NT groups:
+	(It may be useful to copy this text to a script called <filename>initGroups.sh</filename>)
+	<programlisting>
+#!/bin/bash
+#### Keep this as a shell script for future re-use
+			
+# First assign well known domain global groups
+net groupmap add ntgroup="Domain Admins" unixgroup=root rid=512 type=d
+net groupmap add ntgroup="Domain Users"  unixgroup=users rid=513 type=d
+net groupmap add ntgroup="Domain Guests" unixgroup=nobody rid=514 type=d
+
+# Now for our added domain global groups
+net groupmap add ntgroup="Designers" unixgroup=designers type=d
+net groupmap add ntgroup="Engineers" unixgroup=engineers type=d
+net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d
+</programlisting>
+	</para></step>
+
+	<step><para><userinput>net groupmap list</userinput></para>
+		<para>Check that all groups are recognized.
+	</para></step>
+</procedure>
+
+<para>
+Migrate all the profiles, then migrate all policy files.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Migration Options</title>
+
+<para>
+Sites that wish to migrate from MS Windows NT4 domain control to a Samba-based solution
+generally fit into three basic categories. <link linkend="majtypes">Following table</link> shows the possibilities.
+</para>
+
+<table frame="all" id="majtypes"><title>The Three Major Site Types</title>
+<tgroup cols="2">
+	<colspec align="left"/>
+	<colspec align="justify"/> 
+	<thead>
+	<row><entry>Number of Users</entry><entry>Description</entry></row>
+	</thead>
+	<tbody>
+	<row><entry>&lt; 50</entry><entry><para>Want simple conversion with no pain.</para></entry></row>
+	<row><entry>50 - 250</entry><entry><para>Want new features; can manage some inhouse complexity.</para></entry></row>
+	<row><entry>&gt; 250</entry><entry><para>Solution/implementation must scale well; complex needs.
+		Cross-departmental decision process. Local expertise in most areas.</para></entry></row>
+	</tbody>
+</tgroup>
+</table>
+
+<sect2>
+<title>Planning for Success</title>
+
+<para>
+There are three basic choices for sites that intend to migrate from MS Windows NT4
+to Samba-3:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Simple conversion (total replacement).
+	</para></listitem>
+
+	<listitem><para>
+	Upgraded conversion (could be one of integration).
+	</para></listitem>
+
+	<listitem><para>
+	Complete redesign (completely new solution).
+	</para></listitem>
+</itemizedlist>
+
+<para>
+Minimize downstream problems by:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Taking sufficient time.
+	</para></listitem>
+
+	<listitem><para>
+	Avoiding panic.
+	</para></listitem>
+
+	<listitem><para>
+	Testing all assumptions.
+	</para></listitem>
+
+	<listitem><para>
+	Testing the full roll-out program, including workstation deployment.
+	</para></listitem>
+</itemizedlist>
+
+<para><link linkend="natconchoices">Following table</link> lists the conversion choices given the type of migration
+being contemplated.
+</para>
+
+<table frame="all" id="natconchoices"><title>Nature of the Conversion Choices</title>
+<tgroup cols="3">
+	<colspec align="justify" colwidth="1*"/>
+	<colspec align="justify" colwidth="1*"/>
+	<colspec align="justify" colwidth="1*"/>
+	<thead>
+	<row><entry>Simple Install</entry><entry>Upgrade Decisions</entry><entry>Redesign Decisions</entry></row>
+	</thead>
+	<tbody>
+	<row>
+	<entry><para>Make use of minimal OS-specific features</para></entry>
+	<entry><para>Translate NT4 features to new host OS features</para></entry>
+	<entry><para>Improve on NT4 functionality, enhance management capabilities</para></entry>
+	</row>
+	<row>
+	<entry><para>Move all accounts from NT4 into Samba-3</para></entry>
+	<entry><para>Copy and improve</para></entry>
+	<entry><para>Authentication regime (database location and access)</para></entry>
+	</row>
+	<row>
+	<entry><para>Make least number of operational changes</para></entry>
+	<entry><para>Make progressive improvements</para></entry>
+	<entry><para>Desktop management methods</para></entry>
+	</row>
+	<row>
+	<entry><para>Take least amount of time to migrate</para></entry>
+	<entry><para>Minimize user impact</para></entry>
+	<entry><para>Better control of Desktops/Users</para></entry>
+	</row>
+	<row>
+	<entry><para>Live versus isolated conversion</para></entry>
+	<entry><para>Maximize functionality</para></entry>
+	<entry><para>Identify Needs for: <emphasis>Manageability, Scalability, Security, Availability</emphasis></para></entry>
+	</row>
+	<row>
+	<entry><para>Integrate Samba-3, then migrate while users are active, then change of control (swap out)</para></entry>
+	<entry><para>Take advantage of lower maintenance opportunity</para></entry>
+	<entry><para></para></entry>
+	</row>
+	</tbody>
+</tgroup>
+</table>
+</sect2>
+
+<sect2>
+<title>Samba-3 Implementation Choices</title>
+
+<variablelist>
+		<varlistentry><term>Authentication Database/Backend</term><listitem>
+		<para>
+		Samba-3 can use an external authentication backend:
+		</para>
+
+		<para>
+		<itemizedlist>
+			<listitem><para>Winbind (external Samba or NT4/200x server).</para></listitem>
+			<listitem><para>External server could use Active Directory or NT4 domain.</para></listitem>
+			<listitem><para>Can use pam_mkhomedir.so to autocreate home directories.</para></listitem>
+			<listitem><para> Samba-3 can use a local authentication backend: <parameter>smbpasswd</parameter>,
+				<parameter>tdbsam</parameter>, <parameter>ldapsam</parameter>
+			</para></listitem>
+		</itemizedlist></para></listitem>
+		</varlistentry>
+
+        <varlistentry><term>Access Control Points</term><listitem>
+		<para>
+		Samba permits Access Control points to be set:
+		</para>
+
+<indexterm><primary>share ACLs</primary></indexterm>
+<indexterm><primary>UNIX permissions</primary></indexterm>
+<indexterm><primary>POSIX ACLS</primary></indexterm>
+<indexterm><primary>share stanza controls</primary></indexterm>
+
+		<itemizedlist>
+			<listitem><para>On the share itself &smbmdash; using share ACLs.</para></listitem>
+			<listitem><para>On the file system &smbmdash; using UNIX permissions on files and directories.</para>
+			<para>Note: Can enable Posix ACLs in file system also.</para></listitem>
+			<listitem><para>Through Samba share parameters &smbmdash; not recommended except as last resort.</para></listitem>
+		</itemizedlist></listitem>
+        </varlistentry>
+
+        <varlistentry><term>Policies (migrate or create new ones)</term><listitem>
+		<para>
+<indexterm><primary>policies</primary></indexterm>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+		Exercise great caution when making registry changes; use the right tool and be aware
+		that changes made through NT4-style <filename>NTConfig.POL</filename> files can leave
+		permanent changes.
+<indexterm><primary>Group Policy Editor</primary></indexterm>
+<indexterm><primary>tattoo effect</primary></indexterm>
+<indexterm><primary>permanent changes</primary></indexterm>
+		</para>
+                <itemizedlist>
+                        <listitem><para>Using Group Policy Editor (NT4).</para></listitem>
+                        <listitem><para>Watch out for tattoo effect.</para></listitem>
+		</itemizedlist>
+                </listitem>
+        </varlistentry>
+
+        <varlistentry><term>User and Group Profiles</term><listitem>
+		<para>
+<indexterm><primary>NTUser.DAT</primary></indexterm>
+<indexterm><primary>SIDs</primary></indexterm>
+		Platform-specific, so use platform tool to change from a local to a roaming profile.
+		Can use new profiles tool to change SIDs (<filename>NTUser.DAT</filename>).
+		</para>
+                </listitem>
+        </varlistentry>
+
+        <varlistentry><term>Logon Scripts</term><listitem>
+                <para>
+		Know how they work.
+		</para>
+                </listitem>
+        </varlistentry>
+
+
+        <varlistentry><term>User and Group Mapping to UNIX/Linux</term><listitem>
+		<para>
+		<indexterm><primary>pdbedit</primary></indexterm>
+		User and group mapping code is new. Many problems have been experienced as network administrators
+		who are familiar with Samba-2.2.x migrate to Samba-3. Carefully study the chapters that document
+		the new password backend behavior and the new group mapping functionality.
+		</para>
+			<itemizedlist>
+				<listitem><para>The <parameter>username map</parameter> facility may be needed.</para></listitem>
+				<listitem><para>Use <command>net groupmap</command> to connect NT4 groups to UNIX groups.</para></listitem>
+				<listitem><para>
+					Use <command>pdbedit</command> to set/change user configuration.
+					</para>
+
+					<para>
+					When migrating to LDAP backend, it may be easier to dump the initial
+					LDAP database to LDIF, edit, then reload into LDAP.
+					</para></listitem>
+			</itemizedlist></listitem>
+        </varlistentry>
+
+        <varlistentry><term>OS-Specific Scripts/Programs May be Needed</term><listitem>
+		<para>
+		Every operating system has its peculiarities. These are the result of engineering decisions
+		that were based on the experience of the designer and may have side effects that were not
+		anticipated. Limitations that may bite the Windows network administrator include:
+		</para>
+                <itemizedlist>
+                        <listitem><para>Add/Delete Users: Note OS limits on size of name
+				(Linux 8 chars, NT4 up to 254 chars).</para></listitem>
+                        <listitem><para>Add/Delete Machines: Applied only to domain members
+				(Note: machine names may be limited to 16 characters).</para></listitem>
+                        <listitem><para>Use <command>net groupmap</command> to connect NT4 groups to UNIX groups.</para></listitem>
+                        <listitem><para>Add/Delete Groups: Note OS limits on size and nature.
+				Linux limit is 16 char, no spaces, and no uppercase chars (<command>groupadd</command>).</para></listitem>
+		</itemizedlist></listitem>
+        </varlistentry>
+
+        <varlistentry><term>Migration Tools</term><listitem>
+                <para>
+				<indexterm><primary>pdbedit</primary></indexterm>
+				Domain Control (NT4-Style) Profiles, Policies, Access Controls, Security
+				<itemizedlist>
+					 <listitem><para>Samba: <command>net, rpcclient, smbpasswd, pdbedit, profiles</command></para></listitem>
+					 <listitem><para>Windows: <command>NT4 Domain User Manager, Server Manager (NEXUS)</command></para></listitem>
+				</itemizedlist></para></listitem>
+        </varlistentry>
+</variablelist>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml b/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml
new file mode 100644
index 00000000000..3c86438c2f8
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml
@@ -0,0 +1,2218 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="NetworkBrowsing">
+<chapterinfo>
+	&author.jht;
+	&author.jelmer;
+	<author>
+		<firstname>Jonathan</firstname><surname>Johnson</surname>
+		<affiliation>
+			<orgname>Sutinen Consulting, Inc.</orgname>
+                        <address><email>jon@sutinen.com</email></address>
+		</affiliation>
+	</author>
+	<pubdate>July 5, 1998</pubdate>
+	<pubdate>Updated: September 20, 2006</pubdate>
+</chapterinfo>
+
+<title>Network Browsing</title>
+
+<para>
+<indexterm><primary>browsing across subnets</primary></indexterm>
+<indexterm><primary>resolution of NetBIOS names</primary></indexterm>
+<indexterm><primary>browse list handling</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+This chapter contains detailed information as well as a fast-track guide to
+implementing browsing across subnets and/or across workgroups (or domains).
+WINS is the best tool for resolution of NetBIOS names to IP addresses; however, WINS is
+not involved in browse list handling except by way of name-to-address resolution.
+</para>
+
+<note><para>
+<indexterm><primary>WINS</primary></indexterm>
+What is WINS?
+</para>
+<para>
+WINS is a facility that provides resolution of a NetBIOS name to its IP address. WINS is like a
+Dynamic-DNS service for NetBIOS networking names.
+</para></note>
+
+<note><para>
+<indexterm><primary>Windows 2000</primary></indexterm>
+<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+MS Windows 2000 and later versions can be configured to operate with no NetBIOS
+over TCP/IP. Samba-3 and later versions also support this mode of operation.
+When the use of NetBIOS over TCP/IP has been disabled, the primary
+means for resolution of MS Windows machine names is via DNS and Active Directory.
+The following information assumes that your site is running NetBIOS over TCP/IP.
+</para></note>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+Charles Dickens once referred to the past in these words: <quote><emphasis>It was the best of times,
+it was the worst of times.</emphasis></quote> The more we look back, the more we long for what was and
+hope it never returns.
+</para>
+
+
+<para>
+<indexterm><primary>NetBIOS</primary></indexterm>
+<indexterm><primary>NetBIOS networking</primary></indexterm>
+<indexterm><primary>fickle</primary></indexterm>
+For many MS Windows network administrators, that statement sums up their feelings about
+NetBIOS networking precisely. For those who mastered NetBIOS networking, its fickle
+nature was just par for the course. For those who never quite managed to tame its
+lusty features, NetBIOS is like Paterson's Curse.
+</para>
+
+<para>
+For those not familiar with botanical problems in Australia, Paterson's Curse,
+<emphasis>Echium plantagineum</emphasis>, was introduced to Australia from Europe during the mid-19th
+century. Since then it has spread rapidly. The high seed production, with densities of
+thousands of seeds per square meter, a seed longevity of more than 7 years, and an
+ability to germinate at any time of year, given the right conditions, are some of the
+features that make it such a persistent weed.
+</para>
+
+<para>
+<indexterm><primary>Network Basic Input/Output System</primary><see>NetBIOS</see></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>NetBIOS</primary></indexterm>
+<indexterm><primary>TCP/IP</primary></indexterm>
+<indexterm><primary>Windows network clients</primary></indexterm>
+In this chapter we explore vital aspects of Server Message Block (SMB) networking with
+a particular focus on SMB as implemented through running NetBIOS (Network Basic
+Input/Output System) over TCP/IP. Since Samba does not implement SMB or NetBIOS over
+any other protocols, we need to know how to configure our network environment and simply
+remember to use nothing but TCP/IP on all our MS Windows network clients.
+</para>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>MS WINS</primary></indexterm>
+Samba provides the ability to implement a WINS (Windows Internetworking Name Server)
+and implements extensions to Microsoft's implementation of WINS. These extensions
+help Samba to effect stable WINS operations beyond the normal scope of MS WINS.
+</para>
+
+<para>
+<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
+<indexterm><primary>NetBIOS disabled</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+WINS is exclusively a service that applies only to those systems
+that run NetBIOS over TCP/IP. MS Windows 200x/XP have the capacity to operate with
+support for NetBIOS disabled, in which case WINS is of no relevance. Samba supports this also.
+</para>
+
+<para>
+<indexterm><primary>NetBIOS disabled</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+For those networks on which NetBIOS has been disabled (i.e., WINS is not required),
+the use of DNS is necessary for hostname resolution.
+</para>
+
+</sect1>
+
+<sect1>
+<title>What Is Browsing?</title>
+
+<para>
+<indexterm><primary>browsing</primary></indexterm>
+<indexterm><primary>Network Neighborhood</primary></indexterm>
+<indexterm><primary>shares</primary></indexterm>
+<indexterm><primary>printers available</primary></indexterm>
+To most people, browsing means they can see the MS Windows and Samba servers
+in the Network Neighborhood, and when the computer icon for a particular server is
+clicked, it opens up and shows the shares and printers available on the target server.
+</para>
+
+<para>
+What seems so simple is in fact a complex interaction of different technologies.
+The technologies (or methods) employed in making all of this work include:
+</para>
+
+<itemizedlist>
+	<listitem><para>MS Windows machines register their presence to the network.</para></listitem>
+	<listitem><para>Machines announce themselves to other machines on the network.</para></listitem>
+	<listitem><para>One or more machines on the network collate the local announcements.</para></listitem>
+	<listitem><para>The client machine finds the machine that has the collated list of machines.</para></listitem>
+	<listitem><para>The client machine is able to resolve the machine names to IP addresses.</para></listitem>
+	<listitem><para>The client machine is able to connect to a target machine.</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>browse list management</primary></indexterm>
+<indexterm><primary>name resolution</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+The Samba application that controls browse list management and name resolution is
+called <filename>nmbd</filename>. The configuration parameters involved in nmbd's operation are:
+</para>
+
+<para>
+Browsing options:
+</para>
+<itemizedlist>
+	<listitem><smbconfoption name="os level"/></listitem>
+	<listitem><smbconfoption name="lm announce"/></listitem>
+	<listitem><smbconfoption name="lm interval"/></listitem>
+	<listitem><smbconfoption name="preferred master"/>(*)</listitem>
+	<listitem><smbconfoption name="local master"/>(*)</listitem>
+	<listitem><smbconfoption name="domain master"/>(*)</listitem>
+	<listitem><smbconfoption name="browse list"/></listitem>
+	<listitem><smbconfoption name="enhanced browsing"/></listitem>
+</itemizedlist>
+
+<para>
+Name Resolution Method:
+</para>
+<itemizedlist>
+	<listitem><smbconfoption name="name resolve order"/>(*)</listitem>
+</itemizedlist>
+
+<para>
+WINS options:
+</para>
+<itemizedlist>
+	<listitem><smbconfoption name="dns proxy"/></listitem>
+	<listitem><smbconfoption name="wins proxy"/></listitem>
+	<listitem><smbconfoption name="wins server"/>(*)</listitem>
+	<listitem><smbconfoption name="wins support"/>(*)</listitem>
+	<listitem><smbconfoption name="wins hook"/></listitem>
+</itemizedlist>
+
+<para>
+Those marked with an (*) are the only options that commonly may need to be modified. Even if none of these
+parameters is set, <filename>nmbd</filename> will still do its job.
+</para>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>WINS Server</primary></indexterm>
+<indexterm><primary>WINS Support</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>mutually exclusive options</primary></indexterm>
+For Samba, the WINS Server and WINS Support are mutually exclusive options. When <command>nmbd</command> is
+started it will fail to execute if both options are set in the &smb.conf; file. The <command>nmbd</command>
+understands that when it spawns an instance of itself to run as a WINS server that it has to use its own WINS
+server also.
+</para>
+
+</sect1>
+
+<sect1 id="netdiscuss">
+<title>Discussion</title>
+
+<para>
+<indexterm><primary>SMB-based messaging</primary></indexterm>
+<indexterm><primary>NetBIOS</primary></indexterm>
+<indexterm><primary>NetBIOS</primary></indexterm>
+<indexterm><primary>phasing out NetBIOS</primary></indexterm>
+All MS Windows networking uses SMB-based messaging.  SMB messaging may be implemented with or without NetBIOS.
+MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft appears intent on phasing
+out NetBIOS support.
+</para>
+
+<sect2>
+<title>NetBIOS over TCP/IP</title>
+
+<para>
+<indexterm><primary>encapsulating</primary></indexterm>
+<indexterm><primary>broadcast</primary></indexterm>
+<indexterm><primary>unicast</primary></indexterm>
+<indexterm><primary>UDP</primary></indexterm>
+Samba implements NetBIOS, as does MS Windows NT/200x/XP, by encapsulating it over TCP/IP.
+NetBIOS-based networking uses broadcast messaging to effect browse list management. When running NetBIOS over
+TCP/IP, this uses UDP-based messaging.  UDP messages can be broadcast or unicast.
+</para>
+
+<para>
+<indexterm><primary>UDP</primary></indexterm>
+Normally, only unicast UDP messaging can be forwarded by routers. The <smbconfoption name="remote announce"/>
+parameter to smb.conf helps to project browse announcements to remote network segments via unicast UDP.
+Similarly, the <smbconfoption name="remote browse sync"/> parameter of &smb.conf; implements browse list
+collation using unicast UDP.
+</para>
+
+<para>
+The methods used by MS Windows to perform name lookup requests (name resolution) is determined by a
+configuration parameter called the NetBIOS node-type. There are four basic NetBIOS node types:
+</para>
+
+<indexterm><primary>b-node</primary></indexterm>
+<indexterm><primary>p-node</primary></indexterm>
+<indexterm><primary>m-node</primary></indexterm>
+<indexterm><primary>h-node</primary></indexterm>
+<indexterm><primary>node-type</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>broadcast</primary></indexterm>
+<indexterm><primary>unicast</primary></indexterm>
+<itemizedlist>
+	<listitem><para><emphasis>b-node (type 0x01):</emphasis> The Windows client will use only
+	NetBIOS broadcast requests using UDP broadcast.</para></listitem>
+	<listitem><para><emphasis>p-node (type 0x02):</emphasis> The Windows client will use point-to-point
+	(NetBIOS unicast) requests using UDP unicast directed to a WINS server.</para></listitem>
+	<listitem><para><emphasis>m-node (type 0x04):</emphasis> The Windows client will first use
+	NetBIOS broadcast requests using UDP broadcast, then it will use (NetBIOS unicast)
+	requests using UDP unicast directed to a WINS server.</para></listitem>
+	<listitem><para><emphasis>h-node (type 0x08):</emphasis> The Windows client will use
+	(NetBIOS unicast) requests using UDP unicast directed to a WINS server, then it will use
+	NetBIOS broadcast requests using UDP broadcast.</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>h-node</primary></indexterm>
+<indexterm><primary>hybrid</primary></indexterm>
+<indexterm><primary>enables NetBIOS over TCP/IP</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>broadcast-based</primary></indexterm>
+<indexterm><primary>name resolution</primary></indexterm>
+The default Windows network client (or server) network configuration enables NetBIOS over TCP/IP
+and b-node configuration. The use of WINS makes most sense with h-node (hybrid mode) operation so that
+in the event of a WINS breakdown or non-availability, the client can use broadcast-based name resolution.
+</para>
+
+<para>
+<indexterm><primary>LMB</primary><see>Local Master Browser</see></indexterm>
+<indexterm><primary>Local Master Browser</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>cross-segment browsing</primary></indexterm>
+<indexterm><primary>network segment</primary></indexterm>
+In those networks where Samba is the only SMB server technology, wherever possible <filename>nmbd</filename>
+should be configured on one machine as the WINS server. This makes it easy to manage the browsing environment.
+If each network segment is configured with its own Samba WINS server, then the only way to get cross-segment
+browsing to work is by using the <smbconfoption name="remote announce"/> and the <smbconfoption name="remote
+browse sync"/> parameters to your &smb.conf; file.
+</para>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+If only one WINS server is used for an entire multisegment network, then
+the use of the <smbconfoption name="remote announce"/> and the
+<smbconfoption name="remote browse sync"/> parameters should not be necessary.
+</para>
+
+<para>
+<indexterm><primary>replication</primary><secondary>WINS</secondary></indexterm>
+As of Samba-3, WINS replication is being worked on. The bulk of the code has been committed, but it still
+needs maturation. This is not a supported feature of the Samba-3.0.20 release. Hopefully, this will become a
+supported feature of one of the Samba-3 release series. The delay is caused by the fact that this feature has
+not been of sufficient significance to inspire someone to pay a developer to complete it.
+</para>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>MS-WINS replication</primary></indexterm>
+<indexterm><primary>redundancy</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>NetBIOSless SMB over TCP/IP</primary></indexterm>
+<indexterm><primary>local names</primary></indexterm>
+<indexterm><primary>subnets</primary></indexterm>
+<indexterm><primary>multiple WINS servers</primary></indexterm>
+Right now Samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS
+server, there must only be one <filename>nmbd</filename> configured as a WINS server on the network. Some
+sites have used multiple Samba WINS servers for redundancy (one server per subnet) and then used
+<smbconfoption name="remote browse sync"/> and <smbconfoption name="remote announce"/> to effect browse list
+collation across all segments. Note that this means clients will only resolve local names and must be
+configured to use DNS to resolve names on other subnets in order to resolve the IP addresses of the servers
+they can see on other subnets. This setup is not recommended but is mentioned as a practical consideration
+(i.e., an <quote>if all else fails</quote> scenario). NetBIOS over TCP/IP is an ugly and difficult to manage
+protocol. Its replacement, NetBIOSless SMB over TCP/IP is not without its own manageability concerns. NetBIOS
+based networking is a life of compromise and trade-offs. WINS stores information that cannot be stored in
+DNS; consequently, DNS is a poor substitute for WINS given that when NetBIOS over TCP/IP is used, Windows
+clients are designed to use WINS.
+</para>
+
+<para>
+<indexterm><primary>broadcast messages</primary></indexterm>
+<indexterm><primary>repeated intervals</primary></indexterm>
+<indexterm><primary>across network segments</primary></indexterm>
+Lastly, take note that browse lists are a collection of unreliable broadcast
+messages that are repeated at intervals of not more than 15 minutes. This means
+that it will take time to establish a browse list, and it can take up to 45
+minutes to stabilize, particularly across network segments.
+</para>
+
+<para>
+<indexterm><primary>Windows 200x/XP</primary></indexterm>
+When an MS Windows 200x/XP system attempts to resolve a host name to an IP address, it follows a defined path:
+</para>
+
+<orderedlist>
+	<listitem><para>
+	Checks the <filename>hosts</filename> file. It is located in <filename>%SystemRoot%\System32\Drivers\etc</filename>.
+	</para></listitem>
+
+	<listitem><para>
+	Does a DNS lookup.
+	</para></listitem>
+
+	<listitem><para>
+	Checks the NetBIOS name cache.
+	</para></listitem>
+
+	<listitem><para>
+	Queries the WINS server.
+	</para></listitem>
+
+	<listitem><para>
+	Does a broadcast name lookup over UDP.
+	</para></listitem>
+
+	<listitem><para>
+	Looks up entries in LMHOSTS, located in <filename>%SystemRoot%\System32\Drivers\etc</filename>.
+	</para></listitem>
+</orderedlist>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
+<indexterm><primary>name lookups</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+Given the nature of how the NetBIOS over TCP/IP protocol is implemented, only WINS is capable of resolving
+with any reliability name lookups for service-oriented names such as TEMPTATION&lt;1C&gt; &smbmdash; a NetBIOS
+name query that seeks to find network logon servers. DNS has no concept of service-oriented names such as
+this. In fact, the Microsoft ADS implementation specifically manages a whole range of extended
+service-oriented DNS entries. This type of facility is not implemented and is not supported for the NetBIOS
+over TCP/IP protocol namespace.
+</para>
+
+</sect2>
+
+<sect2>
+<title>TCP/IP without NetBIOS</title>
+
+<para>
+<indexterm><primary>NetBIOS</primary></indexterm>
+<indexterm><primary>NetBIOS-less</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+All TCP/IP-enabled systems use various forms of hostname resolution. The primary
+methods for TCP/IP hostname resolution involve either a static file (<filename>/etc/hosts</filename>)
+or the Domain Name System (DNS). DNS is the technology that makes
+the Internet usable. DNS-based hostname resolution is supported by nearly all
+TCP/IP-enabled systems. Only a few embedded TCP/IP systems do not support DNS.
+</para>
+
+<para>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>DDNS</primary></indexterm>
+<indexterm><primary>ipconfig</primary></indexterm>
+<indexterm><primary>Dynamic DNS</primary><see>DDNS</see></indexterm>
+Windows 200x/XP can register its hostname with a Dynamic DNS server (DDNS). It is possible to force register with a
+dynamic DNS server in Windows 200x/XP using <command>ipconfig /registerdns</command>.
+</para>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>severely impaired</primary></indexterm>
+With Active Directory, a correctly functioning DNS server is absolutely essential. In the absence of a working
+DNS server that has been correctly configured, MS Windows clients and servers will be unable to locate each
+other, so network services consequently will be severely impaired.
+</para>
+
+<para>
+<indexterm><primary>raw SMB over TCP/IP</primary></indexterm>
+<indexterm><primary>No NetBIOS layer</primary></indexterm>
+<indexterm><primary>NetBIOS</primary></indexterm>
+<indexterm><primary>domain member server</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+Use of raw SMB over TCP/IP (No NetBIOS layer) can be done only with Active Directory domains. Samba is not an
+Active Directory domain controller: ergo, it is not possible to run Samba as a domain controller and at the same
+time <emphasis>not</emphasis> use NetBIOS. Where Samba is used as an Active Directory domain member server
+(DMS) it is possible to configure Samba to not use NetBIOS over TCP/IP. A Samba DMS can integrate fully into
+an Active Directory domain, however, if NetBIOS over TCP/IP is disabled, it is necessary to manually create
+appropriate DNS entries for the Samba DMS because they will not be automatically generated either by Samba, or
+by the ADS environment.
+</para>
+
+</sect2>
+
+<sect2 id="adsdnstech">
+<title>DNS and Active Directory</title>
+
+<para>
+<indexterm><primary>DNS</primary><secondary>Active Directory</secondary></indexterm>
+<indexterm><primary>DDNS</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>SRV records</primary></indexterm>
+<indexterm><primary>DNS</primary><secondary>SRV records</secondary></indexterm>
+Occasionally we hear from UNIX network administrators who want to use a UNIX-based DDNS server in place
+of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is
+autoconfigured to work with Active Directory. It is possible to use BIND version 8 or 9, but it will almost
+certainly be necessary to create service records (SRV records) so MS Active Directory clients can resolve
+hostnames to locate essential network services.  The following are some of the default service records that
+Active Directory requires:
+</para>
+
+<para>
+<indexterm><primary>DDNS</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>BIND9</primary></indexterm>
+The use of DDNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for
+its ability to adequately support the SRV (service) records that are needed for Active Directory. Of course,
+when running ADS, it makes sense to use Microsoft's own DDNS server because of the natural affinity between ADS
+and MS DNS.
+</para>
+
+<variablelist>
+<varlistentry>
+	<term>_ldap._tcp.pdc._msdcs.<emphasis>Domain</emphasis></term>
+	<listitem>
+	<para>
+	This provides the address of the Windows NT PDC for the domain.
+	</para>
+	</listitem>
+</varlistentry>
+<varlistentry>
+	<term>_ldap._tcp.pdc._msdcs.<emphasis>DomainTree</emphasis></term>
+	<listitem>
+        <para>
+	Resolves the addresses of global catalog servers in the domain.
+        </para>
+	</listitem>
+</varlistentry>
+<varlistentry>
+        <term>_ldap._tcp.<emphasis>site</emphasis>.sites.writable._msdcs.<emphasis>Domain</emphasis></term>
+	<listitem>
+        <para>
+	Provides list of domain controllers based on sites.
+        </para>
+	</listitem>
+</varlistentry>
+<varlistentry>
+        <term>_ldap._tcp.writable._msdcs.<emphasis>Domain</emphasis></term>
+	<listitem>
+        <para>
+	Enumerates list of domain controllers that have the writable copies of the Active Directory data store.
+        </para>
+	</listitem>
+</varlistentry>
+<varlistentry>
+	<term>_ldap._tcp.<emphasis>GUID</emphasis>.domains._msdcs.<emphasis>DomainTree</emphasis></term>
+	<listitem>
+	<para>
+	Entry used by MS Windows clients to locate machines using the global unique identifier.
+	</para>
+	</listitem>
+</varlistentry>
+<varlistentry>
+	<term>_ldap._tcp.<emphasis>Site</emphasis>.gc._msdcs.<emphasis>DomainTree</emphasis></term>
+	<listitem>
+	<para>
+	Used by Microsoft Windows clients to locate the site configuration-dependent global catalog server.
+	</para>
+	</listitem>
+</varlistentry>
+</variablelist>
+
+	<para>
+	Specific entries used by Microsoft clients to locate essential services for an example domain
+	called <constant>quenya.org</constant> include:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		_kerberos._udp.quenya.org &smbmdash; Used to contact the KDC server via UDP.
+		This entry must list port 88 for each KDC.
+		</para></listitem>
+
+		<listitem><para>
+		_kpasswd._udp.quenya.org &smbmdash; Used to locate the <constant>kpasswd</constant> server
+		when a user password change must be processed. This record must list port 464 on the
+		master KDC.
+		</para></listitem>
+
+		<listitem><para>
+		_kerberos._tcp.quenya.org &smbmdash; Used to locate the KDC server via TCP.
+		This entry must list port 88 for each KDC.
+		</para></listitem>
+
+		<listitem><para>
+		_ldap._tcp.quenya.org &smbmdash; Used to locate the LDAP service on the PDC.
+		This record must list port 389 for the PDC.
+		</para></listitem>
+
+		<listitem><para>
+		_kpasswd._tcp.quenya.org &smbmdash; Used to locate the <constant>kpasswd</constant> server
+		to permit user password changes to be processed. This must list port 464.
+		</para></listitem>
+
+		<listitem><para>
+		_gc._tcp.quenya.org &smbmdash; Used to locate the global catalog server  for the
+		top of the domain. This must list port 3268.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	The following records are also used by the Windows domain member client to locate vital
+	services on the Windows ADS domain controllers.
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		_ldap._tcp.pdc._msdcs.quenya.org
+		</para></listitem>
+
+		<listitem><para>
+		_ldap.gc._msdcs.quenya.org
+		</para></listitem>
+
+		<listitem><para>
+		_ldap.default-first-site-name._sites.gc._msdcs.quenya.org
+		</para></listitem>
+
+		<listitem><para>
+		_ldap.{SecID}.domains._msdcs.quenya.org
+		</para></listitem>
+
+		<listitem><para>
+		_ldap._tcp.dc._msdcs.quenya.org
+		</para></listitem>
+
+		<listitem><para>
+		_kerberos._tcp.dc._msdcs.quenya.org
+		</para></listitem>
+
+		<listitem><para>
+		_ldap.default-first-site-name._sites.dc._msdcs.quenya.org
+		</para></listitem>
+
+		<listitem><para>
+		_kerberos.default-first-site-name._sites.dc._msdcs.queyna.org
+		</para></listitem>
+
+		<listitem><para>
+		SecID._msdcs.quenya.org
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	Presence of the correct DNS entries can be validated by executing:
+<screen>
+&rootprompt; dig @frodo -t any _ldap._tcp.dc._msdcs.quenya.org
+
+; &lt;lt;&gt;&gt; DiG 9.2.2 &lt;lt;&gt;&gt; @frodo -t any _ldap._tcp.dc._msdcs.quenya.org
+;; global options:  printcmd
+;; Got answer:
+;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 3072
+;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
+
+
+;; QUESTION SECTION:
+;_ldap._tcp.dc._msdcs.quenya.org. IN        ANY
+
+
+;; ANSWER SECTION:
+_ldap._tcp.dc._msdcs.quenya.org. 600 IN SRV 0 100 389 frodo.quenya.org.
+_ldap._tcp.dc._msdcs.quenya.org. 600 IN SRV 0 100 389 noldor.quenya.org.
+
+
+;; ADDITIONAL SECTION:
+frodo.quenya.org.  3600  IN      A       10.1.1.16
+noldor.quenya.org. 1200  IN      A       10.1.1.17
+
+
+;; Query time: 0 msec
+;; SERVER: frodo#53(10.1.1.16)
+;; WHEN: Wed Oct  7 14:39:31 2004
+;; MSG SIZE  rcvd: 171
+</screen>
+	</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>How Browsing Functions</title>
+
+<para>
+<indexterm><primary>register NetBIOS names</primary></indexterm>
+<indexterm><primary>LMHOSTS</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>WINS server address</primary></indexterm>
+MS Windows machines register their NetBIOS names (i.e., the machine name for each service type in operation)
+on startup.  The exact method by which this name registration takes place is determined by whether or not the
+MS Windows client/server has been given a WINS server address, whether or not LMHOSTS lookup is enabled,
+whether or not DNS for NetBIOS name resolution is enabled, and so on.
+</para>
+
+<para>
+<indexterm><primary>WINS server</primary></indexterm>
+<indexterm><primary>name lookups</primary></indexterm>
+<indexterm><primary>UDP</primary></indexterm>
+In the case where there is no WINS server, all name registrations as well as name lookups are done by UDP
+broadcast. This isolates name resolution to the local subnet, unless LMHOSTS is used to list all names and IP
+addresses. In such situations, Samba provides a means by which the Samba server name may be forcibly injected
+into the browse list of a remote MS Windows network (using the <smbconfoption name="remote announce"/>
+parameter).
+</para>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>UDP unicast</primary></indexterm>
+<indexterm><primary>name resolution across routed networks</primary></indexterm>
+Where a WINS server is used, the MS Windows client will use UDP unicast to register with the WINS server. Such
+packets can be routed, and thus WINS allows name resolution to function across routed networks.
+</para>
+
+<para>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>local master browser</primary><see>LMB</see></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>LMHOSTS</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>browse list</primary></indexterm>
+<indexterm><primary>election</primary></indexterm>
+<indexterm><primary>election criteria</primary></indexterm>
+During the startup process, an election takes place to create a local master browser (LMB) if one does not
+already exist. On each NetBIOS network one machine will be elected to function as the domain master browser
+(DMB). This domain browsing has nothing to do with MS security Domain Control.  Instead, the DMB serves the
+role of contacting each LMB (found by asking WINS or from LMHOSTS) and exchanging browse list contents. This
+way every master browser will eventually obtain a complete list of all machines that are on the network. Every
+11 to 15 minutes an election is held to determine which machine will be the master browser. By the nature of
+the election criteria used, the machine with the highest uptime, or the most senior protocol version or other
+criteria, will win the election as DMB.
+</para>
+
+<para>
+<indexterm><primary>WINS server</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>NetBIOS name type</primary></indexterm>
+<indexterm><primary>n security context</primary></indexterm>
+<indexterm><primary>network segment</primary></indexterm>
+<indexterm><primary>authoritive</primary></indexterm>
+<indexterm><primary>browse list maintainers</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+Where a WINS server is used, the DMB registers its IP address with the WINS server using the name of the
+domain and the NetBIOS name type 1B (e.g., DOMAIN&lt;1B&gt;). All LMBs register their IP addresses with the WINS
+server, also with the name of the domain and the NetBIOS name type of 1D. The 1B name is unique to one
+server within the domain security context, and only one 1D name is registered for each network segment.
+Machines that have registered the 1D name will be authoritive browse list maintainers for the network segment
+they are on. The DMB is responsible for synchronizing the browse lists it obtains from the LMBs.
+</para>
+
+<para>
+<indexterm><primary>name resolution</primary></indexterm>
+Clients wishing to browse the network make use of this list but also depend on the availability of correct
+name resolution to the respective IP address or addresses.
+</para>
+
+<para>
+<indexterm><primary>browsing intrinsics</primary></indexterm>
+Any configuration that breaks name resolution and/or browsing intrinsics will annoy users because they will
+have to put up with protracted inability to use the network services.
+</para>
+
+<para>
+<indexterm><primary>forced synchronization</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>bridges networks</primary></indexterm>
+<indexterm><primary>cross-subnet browsing</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>/etc/hosts</primary></indexterm>
+Samba supports a feature that allows forced synchronization of browse lists across routed networks using the
+<smbconfoption name="remote browse sync"/> parameter in the &smb.conf; file. This causes Samba to contact the
+LMB on a remote network and to request browse list synchronization. This effectively bridges two networks that
+are separated by routers. The two remote networks may use either broadcast-based name resolution or WINS-based
+name resolution, but it should be noted that the <smbconfoption name="remote browse sync"/> parameter provides
+browse list synchronization &smbmdash; and that is distinct from name-to-address resolution. In other words,
+for cross-subnet browsing to function correctly, it is essential that a name-to-address resolution mechanism
+be provided. This mechanism could be via DNS, <filename>/etc/hosts</filename>, and so on.
+</para>
+
+<sect2 id="DMB">
+<title>Configuring Workgroup Browsing</title>
+
+<para>
+<indexterm><primary>cross-subnet browsing</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>isolated workgroup</primary></indexterm>
+<indexterm><primary>workgroup</primary></indexterm>
+To configure cross-subnet browsing on a network containing machines in a workgroup, not an NT domain, you need
+to set up one Samba server to be the DMB (note that this is not the same as a Primary Domain Controller,
+although in an NT domain the same machine plays both roles). The role of a DMB is to collate the browse lists
+from LMB on all the subnets that have a machine participating in the workgroup. Without one machine configured
+as a DMB, each subnet would be an isolated workgroup unable to see any machines on another subnet. It is the
+presence of a DMB that makes cross-subnet browsing possible for a workgroup.
+</para>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+In a workgroup environment the DMB must be a Samba server, and there must only be one DMB per workgroup name.
+To set up a Samba server as a DMB, set the following option in the <smbconfsection name="[global]"/> section
+of the &smb.conf; file:
+</para>
+
+<para>
+<smbconfblock>
+<smbconfoption name="domain master">yes</smbconfoption>
+</smbconfblock>
+</para>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+The DMB should preferably be the LMB for its own subnet. In order to achieve this, set the following options
+in the <smbconfsection name="[global]"/> section of the &smb.conf; file as shown in <link
+linkend="dmbexample">Domain Master Browser smb.conf</link>
+</para>
+
+<example id="dmbexample">
+<title>Domain Master Browser smb.conf</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="domain master">yes</smbconfoption>
+<smbconfoption name="local master">yes</smbconfoption>
+<smbconfoption name="preferred master">yes</smbconfoption>
+<smbconfoption name="os level">65</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>WINS server</primary></indexterm>
+The DMB may be the same machine as the WINS server, if necessary.
+</para>
+
+<para>
+<indexterm><primary>subnets</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>rebooted</primary></indexterm>
+Next, you should ensure that each of the subnets contains a machine that can act as an LMB for the workgroup.
+Any MS Windows NT/200x/XP machine should be able to do this, as will Windows 9x/Me machines (although these
+tend to get rebooted more often, so it is not such a good idea to use them). To make a Samba server an LMB,
+set the following options in the <smbconfsection name="[global]"/> section of the &smb.conf; file as shown in
+<link linkend="lmbexample">Local master browser smb.conf</link>
+</para>
+
+<example id="lmbexample">
+<title>Local master browser smb.conf</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="domain master">no</smbconfoption>
+<smbconfoption name="local master">yes</smbconfoption>
+<smbconfoption name="preferred master">yes</smbconfoption>
+<smbconfoption name="os level">65</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>LMB</primary></indexterm>
+Do not do this for more than one Samba server on each subnet, or they will war with
+each other over which is to be the LMB.
+</para>
+
+<para>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>browser election</primary></indexterm>
+The <smbconfoption name="local master"/> parameter allows Samba to act as a
+LMB. The <smbconfoption name="preferred master"/> causes <command>nmbd</command>
+to force a browser election on startup and the <smbconfoption name="os level"/>
+parameter sets Samba high enough so it should win any browser elections.
+</para>
+
+<para>
+<indexterm><primary>disable LMB</primary></indexterm>
+If you have an NT machine on the subnet that you wish to be the LMB, you can disable Samba from
+becoming an LMB by setting the following options in the <smbconfsection name="[global]"/> section of the
+&smb.conf; file as shown in <link linkend="nombexample">smb.conf for Not Being a Master Browser</link>.
+</para>
+
+<para>
+<example id="nombexample">
+<title>smb.conf for Not Being a Master Browser</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="domain master">no</smbconfoption>
+<smbconfoption name="local master">no</smbconfoption>
+<smbconfoption name="preferred master">no</smbconfoption>
+<smbconfoption name="os level">0</smbconfoption>
+</smbconfblock>
+</example>
+</para>
+
+</sect2>
+
+<sect2>
+<title>Domain Browsing Configuration</title>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>registers</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+If you are adding Samba servers to a Windows NT domain, then you must not set up a Samba server as a DMB.  By
+default, a Windows NT PDC for a domain is also the DMB for that domain. Network browsing may break if a Samba
+server other than the PDC registers the DMB NetBIOS name (<replaceable>DOMAIN</replaceable>&lt;1B&gt;) with
+WINS.
+</para>
+
+<para>
+<indexterm><primary>Local Master Browser</primary></indexterm>
+For subnets other than the one containing the Windows NT PDC, you may set up Samba servers as LMBs as
+described. To make a Samba server a Local Master Browser, set the following options in the <smbconfsection
+name="[global]"/> section of the &smb.conf; file as shown in <link linkend="remsmb">Local Master Browser
+smb.conf</link>
+</para>
+
+<example id="remsmb">
+<title>Local Master Browser smb.conf</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="domain master">no</smbconfoption>
+<smbconfoption name="local master">yes</smbconfoption>
+<smbconfoption name="preferred master">yes</smbconfoption>
+<smbconfoption name="os level">65</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>election</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+If you wish to have a Samba server fight the election with machines on the same subnet, you may set the
+<smbconfoption name="os level"/> parameter to lower levels.  By doing this you can tune the order of machines
+that will become LMBs if they are running. For more details on this, refer to <link
+linkend="browse-force-master">Forcing Samba to Be the Master</link>.
+</para>
+
+<para>
+<indexterm><primary>domain members</primary></indexterm>
+<indexterm><primary>browser elections</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+If you have Windows NT machines that are members of the domain on all subnets and you are sure they will
+always be running, you can disable Samba from taking part in browser elections and ever becoming an LMB by
+setting the following options in the <smbconfsection name="[global]"/> section of the &smb.conf; file as shown
+in <link linkend="xremmb">&smb.conf; for Not Being a master browser</link>
+</para>
+
+<para>
+<example id="xremmb">
+<title>&smb.conf; for Not Being a master browser</title>
+<smbconfsection name="[global]"/>
+<smbconfoption name="domain master">no</smbconfoption>
+<smbconfoption name="local master">no</smbconfoption>
+<smbconfoption name="preferred master">no</smbconfoption>
+<smbconfoption name="os level">0</smbconfoption>
+</example>
+</para>
+
+</sect2>
+
+<sect2 id="browse-force-master">
+<title>Forcing Samba to Be the Master</title>
+
+<para>
+<indexterm><primary>master browser</primary></indexterm>
+<indexterm><primary>election process</primary></indexterm>
+<indexterm><primary>broadcasts</primary></indexterm>
+<indexterm><primary>election packet</primary></indexterm>
+<indexterm><primary>bias</primary></indexterm>
+<indexterm><primary>election</primary></indexterm>
+<indexterm><primary>precedence</primary></indexterm>
+Who becomes the master browser is determined by an election process using broadcasts. Each election packet
+contains a number of parameters that determine what precedence (bias) a host should have in the election. By
+default Samba uses a low precedence and thus loses elections to just about every Windows network server or
+client.
+</para>
+
+<para>
+If you want Samba to win elections, set the <smbconfoption name="os level"/> global option in &smb.conf; to a
+higher number. It defaults to 20. Using 34 would make it win all elections over every other system (except
+other Samba systems).
+</para>
+
+<para>
+An <smbconfoption name="os level"/> of two would make it beat Windows for Workgroups and Windows 9x/Me, but
+not MS Windows NT/200x Server. An MS Windows NT/200x Server domain controller uses level 32. The maximum os
+level is 255.
+</para>
+
+<para>
+<indexterm><primary>force an election</primary></indexterm>
+<indexterm><primary>potential master browsers</primary></indexterm>
+<indexterm><primary>local subnet</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+If you want Samba to force an election on startup, set the <smbconfoption name="preferred master"/> global
+option in &smb.conf; to <constant>yes</constant>.  Samba will then have a slight advantage over other
+potential master browsers that are not preferred master browsers.  Use this parameter with care, because if
+you have two hosts (whether they are Windows 9x/Me or NT/200x/XP or Samba) on the same local subnet both set
+with <smbconfoption name="preferred master"/> to <constant>yes</constant>, then periodically and continually
+they will force an election in order to become the LMB.
+</para>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>LAN</primary></indexterm>
+<indexterm><primary>WAN</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>broadcast isolated subnet</primary></indexterm>
+If you want Samba to be a <emphasis>DMB</emphasis>, then it is recommended that you also set <smbconfoption
+name="preferred master"/> to <constant>yes</constant>, because Samba will not become a DMB for the whole of
+your LAN or WAN if it is not also a LMB on its own broadcast isolated subnet.
+</para>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>automatic redundancy</primary></indexterm>
+<indexterm><primary>UDP</primary></indexterm>
+<indexterm><primary>network bandwidth</primary></indexterm>
+<indexterm><primary>browser elections</primary></indexterm>
+It is possible to configure two Samba servers to attempt to become the DMB for a domain. The first server that
+comes up will be the DMB. All other Samba servers will attempt to become the DMB every 5 minutes. They will
+find that another Samba server is already the DMB and will fail. This provides automatic redundancy should the
+current DMB fail. The network bandwidth overhead of browser elections is relatively small, requiring
+approximately four UDP packets per machine per election. The maximum size of a UDP packet is 576 bytes.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Making Samba the Domain Master</title>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>collating</primary></indexterm>
+<indexterm><primary>browse lists</primary></indexterm>
+<indexterm><primary>browsing</primary></indexterm>
+The domain master browser is responsible for collating the browse lists of multiple subnets so browsing can
+occur between subnets. You can make Samba act as the domain master browser by setting <smbconfoption name="domain
+master">yes</smbconfoption> in &smb.conf;. By default it will not be a domain master browser.
+</para>
+
+<para>
+<indexterm><primary>workgroup</primary></indexterm>
+<indexterm><primary>network browsing problems</primary></indexterm>
+Do not set Samba to be the domain master for a workgroup that has the same name as an NT/200x domain.  If
+Samba is configured to be the domain master for a workgroup that is present on the same network as a Windows
+NT/200x domain that has the same name, network browsing problems will certainly be experienced.
+</para>
+
+<para>
+When Samba is the domain master and the master browser, it will listen for master announcements (made roughly
+every 12 minutes) from LMBs on other subnets and then contact them to synchronize browse lists.
+</para>
+
+<para>
+<indexterm><primary>win election</primary></indexterm>
+<indexterm><primary>force election</primary></indexterm>
+If you want Samba to be the domain master, you should also set the <smbconfoption name="os level"/> high
+enough to make sure it wins elections, and set <smbconfoption name="preferred master"/> to
+<constant>yes</constant>, to get Samba to force an election on startup.
+</para>
+
+<para>
+<indexterm><primary>WINS server</primary></indexterm>
+<indexterm><primary>resolve NetBIOS names</primary></indexterm>
+All servers (including Samba) and clients should be using a WINS server to resolve NetBIOS names. If your
+clients are only using broadcasting to resolve NetBIOS names, then two things will occur:
+</para>
+
+<orderedlist>
+<listitem>
+	<para>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+	LMBs will be unable to find a DMB because they will be looking only on the local subnet.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+<indexterm><primary>domain-wide browse list</primary></indexterm>
+	If a client happens to get hold of a domain-wide browse list and a user attempts to access a
+	host in that list, it will be unable to resolve the NetBIOS name of that host.
+	</para>
+</listitem>
+</orderedlist>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+If, however, both Samba and your clients are using a WINS server, then:
+</para>
+
+<orderedlist>
+<listitem>
+	<para>
+	LMBs will contact the WINS server and, as long as Samba has registered that it is a DMB with the WINS
+	server, the LMB will receive Samba's IP address as its DMB.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	When a client receives a domain-wide browse list and a user attempts to access a host in that list, it will
+	contact the WINS server to resolve the NetBIOS name of that host. As long as that host has registered its
+	NetBIOS name with the same WINS server, the user will be able to see that host..
+	</para>
+</listitem>
+</orderedlist>
+
+</sect2>
+
+<sect2>
+<title>Note about Broadcast Addresses</title>
+
+<para>
+<indexterm><primary>zero-based broadcast</primary></indexterm>
+If your network uses a zero-based broadcast address (for example, if it ends in a 0), then you will strike
+problems. Windows for Workgroups does not seem to support a zeros broadcast, and you will probably find that
+browsing and name lookups will not work.
+</para>
+</sect2>
+
+<sect2>
+<title>Multiple Interfaces</title>
+
+<para>
+<indexterm><primary>multiple network interfaces</primary></indexterm>
+Samba supports machines with multiple network interfaces. If you have multiple interfaces, you will
+need to use the <smbconfoption name="interfaces"/> option in &smb.conf; to configure them. For example, the
+machine you are working with has 4 network interfaces; <literal>eth0</literal>, <literal>eth1</literal>,
+<literal>eth2</literal>, <literal>eth3</literal> and only interfaces <literal>eth1</literal> and
+<literal>eth4</literal> should be used by Samba. In this case, the following &smb.conf; file entries would
+permit that intent:
+<smbconfblock>
+<smbconfoption name="interfaces">eth1, eth4</smbconfoption>
+<smbconfoption name="bind interfaces only">Yes</smbconfoption>
+</smbconfblock>
+<indexterm><primary>port 135</primary></indexterm>
+<indexterm><primary>port 137</primary></indexterm>
+<indexterm><primary>port 138</primary></indexterm>
+<indexterm><primary>port 139</primary></indexterm>
+<indexterm><primary>port 445</primary></indexterm>
+<indexterm><primary>UDP</primary></indexterm>
+<indexterm><primary>TCP</primary></indexterm>
+The <smbconfoption name="bind interfaces only">Yes</smbconfoption> is necessary to exclude TCP/IP session
+services (ports 135, 139, and 445) over the interfaces that are not specified. Please be aware that
+<command>nmbd</command> will listen for incoming UDP port 137 packets on the unlisted interfaces, but it will
+not answer them. It will, however, send its broadcast packets over the unlisted interfaces. Total isolation of
+ethernet interface requires the use of a firewall to block ports 137 and 138 (UDP), and ports 135, 139, and
+445 (TCP) on all network interfaces that must not be able to access the Samba server.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Use of the Remote Announce Parameter</title>
+<para>
+The <smbconfoption name="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.  The syntax of the <smbconfoption
+name="remote announce"/> parameter is:
+<smbconfblock>
+<smbconfoption name="remote announce">192.168.12.23 [172.16.21.255] ...</smbconfoption>
+</smbconfblock>
+<emphasis>or</emphasis>
+<smbconfblock>
+<smbconfoption name="remote announce">192.168.12.23/MIDEARTH [172.16.21.255/ELVINDORF] ...</smbconfoption>
+</smbconfblock>
+
+where:
+<variablelist>
+	<varlistentry><term><replaceable>192.168.12.23</replaceable> and <replaceable>172.16.21.255</replaceable></term>
+		<listitem><para>
+<indexterm><primary>LMB</primary><see>Local Master Browser</see></indexterm>
+<indexterm><primary>Local Master Browser</primary></indexterm>
+		is either the LMB IP address or the broadcast address of the remote network.
+		That is, the LMB is at 192.168.1.23, or the address could be given as 172.16.21.255 where the netmask
+		is assumed to be 24 bits (255.255.255.0). When the remote announcement is made to the broadcast
+		address of the remote network, every host will receive our announcements. This is noisy and therefore
+		undesirable but may be necessary if we do not know the IP address of the remote LMB.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term><replaceable>WORKGROUP</replaceable></term>
+		<listitem><para>is optional and can be either our own workgroup or that of the remote network. If you use the
+		workgroup name of the remote network, our NetBIOS machine names will end up looking like
+		they belong to that workgroup. This may cause name resolution problems and should be avoided.
+		</para></listitem>
+	</varlistentry>
+</variablelist>
+</para>
+
+</sect2>
+
+<sect2>
+<title>Use of the Remote Browse Sync Parameter</title>
+
+<para>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>synchronize</primary></indexterm>
+The <smbconfoption name="remote browse sync"/> parameter of &smb.conf; is used to announce to another LMB that
+it must synchronize its NetBIOS name list with our Samba LMB. This works only if the Samba server that has
+this option is simultaneously the LMB on its network segment.
+</para>
+
+<para>
+The syntax of the <smbconfoption name="remote browse sync"/> parameter is:
+
+<smbconfblock>
+<smbconfoption name="remote browse sync"><replaceable>192.168.10.40</replaceable></smbconfoption>
+</smbconfblock>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>remote segment</primary></indexterm>
+where <replaceable>192.168.10.40</replaceable> is either the IP address of the
+remote LMB or the network broadcast address of the remote segment.
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>WINS: The Windows Internetworking Name Server</title>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>name_type</primary></indexterm>
+<indexterm><primary>LanManager-compatible</primary></indexterm>
+Use of WINS (either Samba WINS or MS Windows NT Server WINS) is highly
+recommended. Every NetBIOS machine registers its name together with a
+name_type value for each of several types of service it has available.
+It registers its name directly as a unique (the type 0x03) name.
+It also registers its name if it is running the LanManager-compatible
+server service (used to make shares and printers available to other users)
+by registering the server (the type 0x20) name.
+</para>
+
+<para>
+<indexterm><primary>NetBIOS name length</primary></indexterm>
+<indexterm><primary>name_type</primary></indexterm>
+All NetBIOS names are up to 15 characters in length. The name_type variable
+is added to the end of the name, thus creating a 16 character name. Any
+name that is shorter than 15 characters is padded with spaces to the 15th
+character. Thus, all NetBIOS names are 16 characters long (including the
+name_type information).
+</para>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>registered</primary></indexterm>
+<indexterm><primary>NetLogon service</primary></indexterm>
+<indexterm><primary>lmhosts</primary></indexterm>
+WINS can store these 16-character names as they get registered. A client
+that wants to log onto the network can ask the WINS server for a list
+of all names that have registered the NetLogon service name_type. This saves
+broadcast traffic and greatly expedites logon processing. Since broadcast
+name resolution cannot be used across network segments, this type of
+information can only be provided via WINS or via a statically configured
+<filename>lmhosts</filename> file that must reside on all clients in the
+absence of WINS.
+</para>
+
+<para>
+<indexterm><primary>synchronization</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>browse list</primary></indexterm>
+WINS also forces browse list synchronization by all LMBs. LMBs must synchronize their browse list with the
+DMB, and WINS helps the LMB to identify its DMB. By definition this will work only within a single workgroup.
+Note that the DMB has nothing to do with what is referred to as an MS Windows NT domain. The latter is a
+reference to a security environment, while the DMB refers to the master controller for browse list information
+only.
+</para>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>TCP/IP protocol stack</primary></indexterm>
+<indexterm><primary>WINS servers</primary></indexterm>
+<indexterm><primary>name-to-address</primary></indexterm>
+WINS will work correctly only if every client TCP/IP protocol stack
+is configured to use the WINS servers. Any client that is not
+configured to use the WINS server will continue to use only broadcast-based
+name registration, so WINS may never get to know about it. In any case,
+machines that have not registered with a WINS server will fail name-to-address
+lookup attempts by other clients and will therefore cause workstation access
+errors.
+</para>
+
+<para>
+To configure Samba as a WINS server, just add
+<smbconfoption name="wins support">yes</smbconfoption> to the &smb.conf;
+file [global] section.
+</para>
+
+<para>
+To configure Samba to register with a WINS server, just add <smbconfoption name="wins
+server">10.0.0.18</smbconfoption> to your &smb.conf; file <smbconfsection name="[global]"/> section.
+</para>
+
+<important><para>
+Never use <smbconfoption name="wins support">yes</smbconfoption> together with <smbconfoption name="wins
+server">10.0.0.18</smbconfoption> particularly not using its own IP address. Specifying both will cause &nmbd;
+to refuse to start!
+</para></important>
+
+<sect2>
+<title>WINS Server Configuration</title>
+
+<para>
+<indexterm><primary>WINS</primary></indexterm>
+Either a Samba server or a Windows NT server machine may be set up
+as a WINS server. To configure a Samba server to be a WINS server, you must
+add to the &smb.conf; file on the selected Server the following line to
+the <smbconfsection name="[global]"/> section:
+</para>
+
+<para>
+<smbconfblock>
+<smbconfoption name="wins support">yes</smbconfoption>
+</smbconfblock>
+</para>
+
+<para>
+<indexterm><primary>Samba 1.9.17</primary></indexterm>
+Versions of Samba prior to 1.9.17 had this parameter default to
+yes. If you have any older versions of Samba on your network, it is
+strongly suggested you upgrade to a recent version, or at the very
+least set the parameter to <quote>no</quote> on all these machines.
+</para>
+
+<para>
+Machines configured with <smbconfoption name="wins support">yes</smbconfoption> will keep a list of
+all NetBIOS names registered with them, acting as a DNS for NetBIOS names.
+</para>
+
+<para>
+<indexterm><primary>only one WINS server</primary></indexterm>
+It is strongly recommended to set up only one WINS server. Do not set the <smbconfoption name="wins
+support">yes</smbconfoption> option on more than one Samba server on a network.
+</para>
+
+<para>
+<indexterm><primary>replication</primary><secondary>WINS</secondary></indexterm>
+<indexterm><primary>Windows NT/200x</primary></indexterm>
+<indexterm><primary>WINS service</primary></indexterm>
+<indexterm><primary>replication protocols</primary></indexterm>
+<indexterm><primary>WINS server</primary></indexterm>
+To configure Windows NT/200x Server as a WINS server, install and configure the WINS service. See the Windows
+NT/200x documentation for details.  Windows NT/200x WINS servers can replicate to each other, allowing more
+than one to be set up in a complex subnet environment. Because Microsoft refuses to document the replication
+protocols, Samba cannot currently participate in these replications. It is possible that a Samba-to-Samba WINS
+replication protocol may be defined in the future, in which case more than one Samba machine could be set up
+as a WINS server.  Currently only one Samba server should have the <smbconfoption name="wins
+support">yes</smbconfoption> parameter set.
+</para>
+
+<para>
+<indexterm><primary>WINS server</primary></indexterm>
+<indexterm><primary>Primary WINS Server</primary></indexterm>
+After the WINS server has been configured, you must ensure that all machines participating on the network are
+configured with the address of this WINS server. If your WINS server is a Samba machine, fill in the Samba
+machine IP address in the <guilabel>Primary WINS Server</guilabel> field of the <guilabel>Control
+Panel->Network->Protocols->TCP->WINS Server</guilabel> dialogs in Windows 9x/Me or Windows NT/200x. To tell a
+Samba server the IP address of the WINS server, add the following line to the <smbconfsection
+name="[global]"/> section of all &smb.conf; files:
+<smbconfblock>
+<smbconfoption name="wins server">&lt;name or IP address&gt;</smbconfoption>
+</smbconfblock>
+where &lt;name or IP address&gt; is either the DNS name of the WINS server
+machine or its IP address.
+</para>
+
+<para>
+This line must not be set in the &smb.conf; file of the Samba
+server acting as the WINS server itself. If you set both the
+<smbconfoption name="wins support">yes</smbconfoption> option and the
+<smbconfoption name="wins server">&lt;name&gt;</smbconfoption> option then
+<command>nmbd</command> will fail to start.
+</para>
+
+<para>
+<indexterm><primary>cross-subnet browsing</primary></indexterm>
+<indexterm><primary>Windows 9x/Me</primary></indexterm>
+<indexterm><primary>Windows NT/200x</primary></indexterm>
+<indexterm><primary>not part of domain</primary></indexterm>
+There are two possible scenarios for setting up cross-subnet browsing.
+The first details setting up cross-subnet browsing on a network containing
+Windows 9x/Me, Samba, and Windows NT/200x machines that are not configured as
+part of a Windows NT domain. The second details setting up cross-subnet
+browsing on networks that contain NT domains.
+</para>
+
+</sect2>
+
+<sect2>
+<title>WINS Replication</title>
+
+<para>
+<indexterm><primary>replication</primary><secondary>WINS</secondary></indexterm>
+<indexterm><primary>WINS replication</primary></indexterm>
+Samba-3 does not support native WINS replication. There was an approach to implement it, called
+<filename>wrepld</filename>, but it was never ready for action and the development is now discontinued.
+</para>
+<para>
+Meanwhile, there is a project named <filename>samba4WINS</filename>, which makes it possible to
+run the Samba-4 WINS server parallel to Samba-3 since version 3.0.21. More information about
+<filename>samba4WINS</filename> are available at http://ftp.sernet.de/pub/samba4WINS.
+
+</para>
+
+</sect2>
+<sect2>
+<title>Static WINS Entries</title>
+
+<para>
+<indexterm><primary>static WINS entries</primary></indexterm>
+<indexterm><primary>wins.dat</primary></indexterm>
+<indexterm><primary>/usr/local/samba/var/locks</primary></indexterm>
+<indexterm><primary>/var/run/samba</primary></indexterm>
+Adding static entries to your Samba WINS server is actually fairly easy.  All you have to do is add a line to
+<filename>wins.dat</filename>, typically located in <filename
+class="directory">/usr/local/samba/var/locks</filename> or <filename>/var/run/samba</filename>.
+</para>
+
+<para>
+Entries in <filename>wins.dat</filename> take the form of:
+<programlisting>
+"NAME#TYPE" TTL ADDRESS+ FLAGS
+</programlisting>
+<indexterm><primary>TTL</primary></indexterm>
+<indexterm><primary>time-to-live</primary><see>TTL</see></indexterm>
+where NAME is the NetBIOS name, TYPE is the NetBIOS type, TTL is the time-to-live as an absolute time in
+seconds, ADDRESS+ is one or more addresses corresponding to the registration, and FLAGS are the NetBIOS flags
+for the registration.
+</para>
+
+<note><para>
+A change that has been made to the <filename>wins.dat</filename> will not take effect until &nmbd; has been
+restarted. It should be noted that since the <filename>wins.dat</filename> file changes dynamically, &nmbd;
+should be stopped before editting this file. Do not forget to restart &nmbd; when this file has been editted.
+</para></note>
+
+<para>
+A typical dynamic entry looks like this:
+<programlisting>
+"MADMAN#03" 1155298378 192.168.1.2 66R
+</programlisting>
+To make a NetBIOS name static (permanent), simply set the TTL to 0, like this:
+<programlisting>
+"MADMAN#03" 0 192.168.1.2 66R
+</programlisting>
+</para>
+
+<para>
+<indexterm><primary>NetBIOS flags</primary></indexterm>
+<indexterm><primary>Broadcast node</primary></indexterm>
+<indexterm><primary>Peer node</primary></indexterm>
+<indexterm><primary>Meta node</primary></indexterm>
+<indexterm><primary>Hybrid node</primary></indexterm>
+<indexterm><primary>Permanent name</primary></indexterm>
+<indexterm><primary>nameserv.h</primary></indexterm>
+The NetBIOS flags may be interpreted as additive hexadecimal values: 00 - Broadcast node registration, 20 -
+Peer node registration, 40 - Meta node registration, 60 - Hybrid node registration, 02 - Permanent name, 04 -
+Active name, 80 - Group name. The 'R' indicates this is a registration record. Thus 66R means: Hybrid node
+active and permanent NetBIOS name. These values may be found in the <filename>nameserv.h</filename> header
+file from the Samba source code repository. These are the values for the NB flags.
+</para>
+
+<para>
+<indexterm><primary>WINS replication</primary></indexterm>
+Though this method works with early Samba-3 versions, there is a possibility that it may change in future
+versions if WINS replication is added.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Helpful Hints</title>
+
+<para>
+The following hints should be carefully considered because they are stumbling points
+for many new network administrators.
+</para>
+
+<sect2>
+<title>Windows Networking Protocols</title>
+
+<para>
+<indexterm><primary>browsing problems</primary></indexterm>
+<indexterm><primary>more than one protocol</primary></indexterm>
+A common cause of browsing problems results from the installation of more than one protocol on an MS Windows
+machine.
+</para>
+
+<warning><para>
+Do not use more than one protocol on MS Windows clients.
+</para></warning>
+
+<para>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
+every 15 minutes. A set of election criteria is used to determine the order
+of precedence for winning this election process. A machine running Samba or
+Windows NT will be biased, so the most suitable machine will predictably
+win and thus retain its role.
+</para>
+
+<para>
+<indexterm><primary>NetBIOS network interface</primary></indexterm>
+<indexterm><primary>TCP/IP</primary></indexterm>
+<indexterm><primary>IPX</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>Windows 9x/Me</primary></indexterm>
+<indexterm><primary>TCP/IP-only</primary></indexterm>
+The election process is <emphasis>fought out, so to speak</emphasis> over every NetBIOS network interface. In
+the case of a Windows 9x/Me machine that has both TCP/IP and IPX installed and has NetBIOS enabled over both
+protocols, the election will be decided over both protocols. As often happens, if the Windows 9x/Me machine is
+the only one with both protocols, then the LMB may be won on the NetBIOS interface over the IPX protocol.
+Samba will then lose the LMB role because Windows 9x/Me will insist it knows who the LMB is. Samba will then
+cease to function as an LMB, and browse list operation on all TCP/IP-only machines will therefore fail.
+</para>
+
+<para>
+<indexterm><primary>Windows 9x/Me</primary></indexterm>
+<indexterm><primary>extended protocol</primary></indexterm>
+Windows 95, 98, 98se, and Me are referred to generically as Windows 9x/Me.  The Windows NT4, 200x, and XP use
+common protocols. These are roughly referred to as the Windows NT family, but it should be recognized that
+2000 and XP/2003 introduce new protocol extensions that cause them to behave differently from MS Windows NT4.
+Generally, where a server does not support the newer or extended protocol, these will fall back to the NT4
+protocols.
+</para>
+
+<para>
+The safest rule of all to follow is: Use only one protocol!
+</para>
+
+</sect2>
+
+<sect2>
+<title>Name Resolution Order</title>
+
+<para>
+<indexterm><primary>NetBIOS names</primary></indexterm>
+<indexterm><primary>name_type</primary></indexterm>
+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
+are:
+</para>
+
+<itemizedlist>
+	<listitem><para>WINS &smbmdash; the best tool.</para></listitem>
+	<listitem><para>LMHOSTS &smbmdash; static and hard to maintain.</para></listitem>
+	<listitem><para>Broadcast &smbmdash; uses UDP and cannot resolve names across remote segments.</para></listitem>
+</itemizedlist>
+
+<para>
+Alternative means of name resolution include:
+</para>
+<itemizedlist>
+<listitem><para>Static <filename>/etc/hosts</filename> &smbmdash;  hard to maintain and lacks name_type info.</para></listitem>
+<listitem><para>DNS &smbmdash; is a good choice but lacks essential NetBIOS name_type information.</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>restrict DNS</primary></indexterm>
+<indexterm><primary>name resolve order</primary></indexterm>
+Many sites want to restrict DNS lookups and avoid broadcast name
+resolution traffic. The <parameter>name resolve order</parameter> parameter is of great help here.
+The syntax of the <parameter>name resolve order</parameter> parameter is:
+<smbconfblock>
+<smbconfoption name="name resolve order">wins lmhosts bcast host</smbconfoption>
+</smbconfblock>
+<emphasis>or</emphasis>
+<smbconfblock>
+<smbconfoption name="name resolve order">wins lmhosts  	(eliminates bcast and host)</smbconfoption>
+</smbconfblock>
+The default is:
+<smbconfblock>
+<smbconfoption name="name resolve order">host lmhost wins bcast</smbconfoption>,
+</smbconfblock>
+<indexterm><primary>gethostbyname() function call</primary></indexterm>
+where <quote>host</quote> refers to the native methods used by the UNIX system to implement the
+gethostbyname() function call. This is normally controlled by <filename>/etc/host.conf</filename>,
+<filename>/etc/nsswitch.conf</filename> and <filename>/etc/resolv.conf</filename>.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Technical Overview of Browsing</title>
+
+<para>
+<indexterm><primary>SMB</primary></indexterm>
+SMB networking provides a mechanism by which clients can access a list
+of machines in a network called <smbconfoption name="browse list"/>. This list
+contains machines that are ready to offer file and/or print services
+to other machines within the network. It therefore does not include
+machines that aren't currently able to do server tasks. The browse
+list is heavily used by all SMB clients. Configuration of SMB
+browsing has been problematic for some Samba users, hence this
+document.
+</para>
+
+<para>
+<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
+<indexterm><primary>DNS/LDAP/ADS</primary></indexterm>
+<indexterm><primary>name resolution</primary></indexterm>
+MS Windows 2000 and later versions, as with Samba-3 and later versions, can be
+configured to not use NetBIOS over TCP/IP. When configured this way,
+it is imperative that name resolution (using DNS/LDAP/ADS) be correctly
+configured and operative. Browsing will not work if name resolution
+from SMB machine names to IP addresses does not function correctly.
+</para>
+
+<para>
+<indexterm><primary>NetBIOS</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+Where NetBIOS over TCP/IP is enabled, use of a WINS server is highly
+recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
+WINS allows remote segment clients to obtain NetBIOS name_type information
+that cannot be provided by any other means of name resolution.
+</para>
+
+<sect2>
+<title>Browsing Support in Samba</title>
+
+<para>
+<indexterm><primary>browsing</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>domain logons</primary></indexterm>
+<indexterm><primary>scripts</primary></indexterm>
+Samba facilitates browsing. The browsing is supported by &nmbd;
+and is also controlled by options in the &smb.conf; file.
+Samba can act as an LMB for a workgroup, and the ability
+to support domain logons and scripts is now available.
+</para>
+
+<para>
+<indexterm><primary>DMB for a workgroup</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+Samba can also act as a DMB for a workgroup. This
+means that it will collate lists from LMBs into a
+wide-area network server list. In order for browse clients to
+resolve the names they may find in this list, it is recommended that
+both Samba and your clients use a WINS server.
+</para>
+
+<para>
+<indexterm><primary>domain master</primary></indexterm>
+Do not set Samba to be the domain master for a workgroup that has the same
+name as an NT Domain. On each wide-area network, you must only ever have one
+DMB per workgroup, regardless of whether it is NT, Samba,
+or any other type of domain master that is providing this service.
+</para>
+
+<note><para>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>WINS server</primary></indexterm>
+<command>nmbd</command> can be configured as a WINS server, but it is not
+necessary to specifically use Samba as your WINS server. MS Windows
+NT4, Server or Advanced Server 200x can be configured as
+your WINS server. In a mixed NT/200x server and Samba environment on
+a WAN, it is recommended that you use the Microsoft
+WINS server capabilities. In a Samba-only environment, it is
+recommended that you use one and only one Samba server as the WINS server.
+</para></note>
+
+<para>
+<indexterm><primary>nmbd</primary></indexterm>
+To get browsing to work, you need to run <command>nmbd</command> as usual, but must
+use the <smbconfoption name="workgroup"/> option in &smb.conf;
+to control what workgroup Samba becomes a part of.
+</para>
+
+<para>
+<indexterm><primary>browsing another subnet</primary></indexterm>
+Samba also has a useful option for a Samba server to offer itself for browsing on another subnet. It is
+recommended that this option is used only for <quote>unusual</quote> purposes: announcements over the
+Internet, for example. See <smbconfoption name="remote announce"/> in the &smb.conf; man page.
+</para>
+</sect2>
+
+<sect2>
+<title>Problem Resolution</title>
+
+<para>
+<indexterm><primary>log.nmbd</primary></indexterm>
+<indexterm><primary>browse.dat</primary></indexterm>
+If something does not work, the <filename>log.nmbd</filename> file will help
+to track down the problem. Try a <smbconfoption name="log level"></smbconfoption> of 2 or 3 for finding
+problems. Also note that the current browse list usually gets stored
+in text form in a file called <filename>browse.dat</filename>.
+</para>
+
+<para>
+<indexterm><primary>\\SERVER</primary></indexterm>
+<indexterm><primary>filemanager</primary></indexterm>
+If it does not work, you should still be able to
+type the server name as <filename>\\SERVER</filename> in <command>filemanager</command>, then
+press enter, and <command>filemanager</command> should display the list of available shares.
+</para>
+
+<para>
+<indexterm><primary>IPC$</primary></indexterm>
+<indexterm><primary>guest account</primary></indexterm>
+Some people find browsing fails because they do not have the global
+<smbconfoption name="guest account"/> set to a valid account. Remember that the
+IPC$ connection that lists the shares is done as guest and so you must have a valid guest account.
+</para>
+
+<note><para>
+<indexterm><primary>IPC$</primary></indexterm>
+<indexterm><primary>Windows Explorer</primary></indexterm>
+<indexterm><primary>browse resources</primary></indexterm>
+<indexterm><primary>Network Neighborhood</primary></indexterm>
+<indexterm><primary>My Network Places</primary></indexterm>
+The <literal>IPC$</literal> share is used by all SMB/CIFS clients to obtain the list of resources that is
+available on the server. This is the source of the list of shares and printers when browsing an SMB/CIFS
+server (also Windows machines) using the Windows Explorer to browse resources through the Windows Network
+Neighborhood (also called My Network Places) through to a Windows server. At this point, the client has opened
+a connection to the <literal>\\server\IPC4</literal> resource.  Clicking on a share will then open up a
+connection to the <literal>\\server\share</literal>.
+</para></note>
+
+<para>
+<indexterm><primary>guest account</primary></indexterm>
+<indexterm><primary>anonymous access</primary></indexterm>
+<indexterm><primary>IPC$</primary></indexterm>
+<indexterm><primary>browse server resources</primary></indexterm>
+MS Windows 2000 and later (as with Samba) can be configured to disallow
+anonymous (i.e., guest account) access to the IPC$ share. In that case, the
+MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the
+name of the currently logged-in user to query the IPC$ share. MS Windows
+9x/Me clients are not able to do this and thus will not be able to browse
+server resources.
+</para>
+
+<para>
+<indexterm><primary>broadcast address</primary></indexterm>
+The other big problem people have is that their broadcast address,
+netmask, or IP address is wrong (specified with the <smbconfoption name="interfaces"></smbconfoption> option
+in &smb.conf;)
+</para>
+</sect2>
+
+<sect2>
+<title>Cross-Subnet Browsing</title>
+
+<para>
+<indexterm><primary>replication</primary><secondary>browse lists</secondary></indexterm>
+<indexterm><primary>browse across subnet</primary></indexterm>
+Since the release of Samba 1.9.17 (alpha1), Samba has supported the replication of browse lists across subnet
+boundaries. This section describes how to set this feature up in different settings.
+</para>
+
+<para>
+<indexterm><primary>browse lists</primary></indexterm>
+<indexterm><primary>broadcast traffic</primary></indexterm>
+<indexterm><primary>UDP</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>remote announce</primary></indexterm>
+<indexterm><primary>remote browse sync</primary></indexterm>
+To see browse lists that span TCP/IP subnets (i.e., networks separated by routers that do not pass broadcast
+traffic), you must set up at least one WINS server. The WINS server acts as a DNS for NetBIOS names. This will
+allow NetBIOS name-to-IP address translation to be completed by a direct query of the WINS server. This is
+done via a directed UDP packet on port 137 to the WINS server machine. The WINS server avoids the necessity of
+default NetBIOS name-to-IP address translation, which is done using UDP broadcasts from the querying machine.
+This means that machines on one subnet will not be able to resolve the names of machines on another subnet
+without using a WINS server. The Samba hacks, <parameter>remote browse sync</parameter>, and <parameter>remote
+announce</parameter> are designed to get around the natural limitations that prevent UDP broadcast
+propagation. The hacks are not a universal solution and they should not be used in place of WINS, they are
+considered last resort methods.
+</para>
+
+<para>
+<indexterm><primary>DHCP</primary></indexterm>
+<indexterm><primary>browsing across subnets</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>Network settings</primary></indexterm>
+Remember, for browsing across subnets to work correctly, all machines, be they Windows 95, Windows NT, or
+Samba servers, must have the IP address of a WINS server given to them by a DHCP server or by manual
+configuration: for Windows 9x/Me and Windows NT/200x/XP, this is in the TCP/IP Properties, under Network
+settings; for Samba, this is in the &smb.conf; file.
+</para>
+
+<para>
+<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+It is possible to operate Samba-3 without NetBIOS over TCP/IP. If you do this, be warned that if used outside
+of MS ADS, this will forgo network browsing support. ADS permits network browsing support through DNS,
+providing appropriate DNS records are inserted for all Samba servers.
+</para>
+
+<sect3>
+<title>Behavior of Cross-Subnet Browsing</title>
+
+<para>
+<indexterm><primary>cross-subnet browsing</primary></indexterm>
+<indexterm><primary>complicated</primary></indexterm>
+Cross-subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several
+years to get the code that correctly achieves this, and Samba lags behind in some areas.  Samba is capable of
+cross-subnet browsing when configured correctly.
+</para>
+
+<para>
+Consider a network set up as in <link linkend="browsing1">Cross-Subnet Browsing Example</link>.
+</para>
+
+<figure id="browsing1">
+	<title>Cross-Subnet Browsing Example.</title>
+	<imagefile scale="40">browsing1</imagefile>
+</figure>
+
+<para>
+<indexterm><primary>broadcasts</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+This consists of three subnets (1, 2, 3) connected by two routers (R1, R2), which do not pass broadcasts.
+Subnet 1 has five machines on it, subnet 2 has four machines, and subnet 3 has four machines. Assume for the
+moment that all machines are configured to be in the same workgroup (for simplicity's sake). Machine N1_C on
+subnet 1 is configured as the DMB (i.e., it will collate the browse lists for the workgroup). Machine N2_D is
+configured as a WINS server, and all the other machines are configured to register their NetBIOS names with
+it.
+</para>
+
+<para>
+<indexterm><primary>master browsers</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+As these machines are booted up, elections for master browsers
+take place on each of the three subnets. Assume that machine
+N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on
+subnet 3. These machines are known as LMBs for
+their particular subnet. N1_C has an advantage in winning as the
+LMB on subnet 1 because it is set up as DMB.
+</para>
+
+<para>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>browse list</primary></indexterm>
+On each of the three networks, machines that are configured to offer sharing services will broadcast that they
+are offering these services. The LMB on each subnet will receive these broadcasts and keep a record of the
+fact that the machine is offering a service. This list of records is the basis of the browse list. For this
+case, assume that all the machines are configured to offer services, so all machines will be on the browse
+list.
+</para>
+
+<para>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>authoritative</primary></indexterm>
+<indexterm><primary>verifiable</primary></indexterm>
+<indexterm><primary>trusted</primary></indexterm>
+<indexterm><primary>non-authoritative</primary></indexterm>
+For each network, the LMB on that network is
+considered <emphasis>authoritative</emphasis> for all the names it receives via
+local broadcast. This is because a machine seen by the LMB
+via a local broadcast must be on the same network as the
+Local Master Browser and thus is a <emphasis>trusted</emphasis>
+and <emphasis>verifiable</emphasis> resource. Machines on other networks that
+the LMBs learn about when collating their
+browse lists have not been directly seen. These records are
+called <emphasis>non-authoritative.</emphasis>
+</para>
+
+<para>
+<indexterm><primary>network neighborhood</primary></indexterm>
+At this point the browse lists appear as shown in <link linkend="browsubnet">Browse Subnet Example 1</link>
+(these are the machines you would see in your network neighborhood if you looked in it on a particular network
+right now).
+</para>
+
+<para>
+<table frame="all" id="browsubnet">
+	<title>Browse Subnet Example 1</title>
+	<tgroup align="left" cols="3">
+	<thead>
+		<row><entry>Subnet</entry><entry>Browse Master</entry><entry>List</entry></row>
+	</thead>
+
+	<tbody>
+		<row><entry>Subnet1</entry><entry>N1_C</entry><entry>N1_A, N1_B, N1_C, N1_D, N1_E</entry></row>
+		<row><entry>Subnet2</entry><entry>N2_B</entry><entry>N2_A, N2_B, N2_C, N2_D</entry></row>
+		<row><entry>Subnet3</entry><entry>N3_D</entry><entry>N3_A, N3_B, N3_C, N3_D</entry></row>
+	</tbody>
+	</tgroup>
+</table>
+</para>
+
+<para>
+At this point all the subnets are separate, and no machine is seen across any of the subnets.
+</para>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>synchronize</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+Now examine subnet 2 in <link linkend="brsbex">Browse Subnet Example 2</link>.  As soon as N2_B has become the
+LMB, it looks for a DMB with which to synchronize its browse list. It does this by querying the WINS server
+(N2_D) for the IP address associated with the NetBIOS name WORKGROUP&lt;1B&gt;. This name was registered by
+the DMB (N1_C) with the WINS server as soon as it was started.
+</para>
+
+<para>
+<indexterm><primary>MasterAnnouncement</primary></indexterm>
+<indexterm><primary>NetServerEnum2</primary></indexterm>
+<indexterm><primary>synchronization</primary></indexterm>
+<indexterm><primary>browse lists</primary></indexterm>
+Once N2_B knows the address of the DMB, it tells it that is the LMB for subnet 2 by sending a
+<emphasis>MasterAnnouncement</emphasis> packet as a UDP port 138 packet.  It then synchronizes with it by
+doing a <emphasis>NetServerEnum2</emphasis> call. This tells the DMB to send it all the server names it knows
+about. Once the DMB receives the <emphasis>MasterAnnouncement</emphasis> packet, it schedules a
+synchronization request to the sender of that packet. After both synchronizations are complete, the browse
+lists look like those in <link linkend="brsbex">Browse Subnet Example 2</link>
+</para>
+
+<table frame="all" id="brsbex">
+	<title>Browse Subnet Example 2</title>
+	<tgroup	cols="3">
+		<colspec align="left"/>
+		<colspec align="left"/>
+		<colspec align="justify" colwidth="1*"/>
+	<thead>
+		<row><entry>Subnet</entry><entry>Browse Master</entry><entry>List</entry></row>
+	</thead>
+
+	<tbody>
+		<row><entry>Subnet1</entry><entry>N1_C</entry><entry>N1_A, N1_B, N1_C, N1_D, N1_E,
+N2_A(*), N2_B(*), N2_C(*), N2_D(*)</entry></row>
+		<row><entry>Subnet2</entry><entry>N2_B</entry><entry>N2_A, N2_B, N2_C, N2_D, N1_A(*),
+N1_B(*), N1_C(*), N1_D(*), N1_E(*)</entry></row>
+		<row><entry>Subnet3</entry><entry>N3_D</entry><entry>N3_A, N3_B, N3_C, N3_D</entry></row>
+	</tbody>
+	</tgroup>
+</table>
+
+<para>
+<indexterm><primary>non-authoritative</primary></indexterm>
+Servers with an (*) after them are non-authoritative names.
+</para>
+
+<para>
+<indexterm><primary>Network Neighborhood</primary></indexterm>
+At this point users looking in their Network Neighborhood on subnets 1 or 2 will see all the servers on both;
+users on subnet 3 will still see only the servers on their own subnet.
+</para>
+
+<para>
+<indexterm><primary>DMB</primary></indexterm>
+The same sequence of events that occurred for N2_B now occurs for the LMB on subnet 3 (N3_D). When it
+synchronizes browse lists with the DMB (N1_A) it gets both the server entries on subnet 1 and those on subnet
+2. After N3_D has synchronized with N1_C and vica versa, the browse lists will appear as shown in <link
+linkend="brsex2">Browse Subnet Example 3</link>
+</para>
+
+<table frame="all" id="brsex2">
+	<title>Browse Subnet Example 3</title>		
+	<tgroup cols="3" align="left">
+		<colspec align="left"/>
+		<colspec align="left"/>
+		<colspec align="justify" colwidth="1*"/>
+
+	<thead>
+		<row><entry>Subnet</entry><entry>Browse Master</entry><entry>List</entry></row>
+	</thead>
+
+	<tbody>
+		<row><entry>Subnet1</entry><entry>N1_C</entry><entry>N1_A, N1_B, N1_C, N1_D, N1_E,
+N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</entry></row>
+		<row><entry>Subnet2</entry><entry>N2_B</entry><entry>N2_A, N2_B, N2_C, N2_D, N1_A(*),
+N1_B(*), N1_C(*), N1_D(*), N1_E(*)</entry></row>
+		<row><entry>Subnet3</entry><entry>N3_D</entry><entry>N3_A, N3_B, N3_C, N3_D, N1_A(*),
+N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)</entry></row>
+	</tbody>
+	</tgroup>
+</table>
+
+<para>
+Servers with an (*) after them are non-authoritative names.
+</para>
+
+<para>
+At this point, users looking in their Network Neighborhood on
+subnets 1 or 3 will see all the servers on all subnets, while users on
+subnet 2 will still see only the servers on subnets 1 and 2, but not 3.
+</para>
+
+<para>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>browse lists</primary></indexterm>
+Finally, the LMB for subnet 2 (N2_B) will sync again
+with the DMB (N1_C) and will receive the missing
+server entries. Finally, as when a steady state (if no machines
+are removed or shut off) has been achieved, the browse lists will appear
+as shown in <link linkend="brsex3">Browse Subnet Example 4</link>.
+</para>
+
+<table frame="all" id="brsex3">
+	<title>Browse Subnet Example 4</title>
+	<tgroup cols="3" align="left">
+		<colspec align="left"/>
+		<colspec align="left"/>
+		<colspec align="justify" colwidth="1*"/>
+
+	<thead>
+		<row><entry>Subnet</entry><entry>Browse Master</entry><entry>List</entry></row>
+	</thead>
+
+	<tbody>
+		<row><entry>Subnet1</entry><entry>N1_C</entry><entry>N1_A, N1_B, N1_C, N1_D, N1_E,
+N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*),
+N3_C(*), N3_D(*)</entry></row>
+		<row><entry>Subnet2</entry><entry>N2_B</entry><entry>N2_A, N2_B, N2_C, N2_D, N1_A(*),
+N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*),
+N3_C(*), N3_D(*)</entry></row>
+		<row><entry>Subnet3</entry><entry>N3_D</entry><entry>N3_A, N3_B, N3_C, N3_D, N1_A(*),
+N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*),
+N2_C(*), N2_D(*)</entry></row>
+	</tbody>
+	</tgroup>
+</table>
+
+<para>
+Servers with an (*) after them are non-authoritative names.
+</para>
+
+<para>
+Synchronizations between the DMB and LMBs
+will continue to occur, but this should remain a
+steady-state operation.
+</para>
+
+<para>
+If either router R1 or R2 fails, the following will occur:
+</para>
+
+<orderedlist>
+<listitem>
+	<para>
+<indexterm><primary>Network Neighborhood</primary></indexterm>
+	Names of computers on each side of the inaccessible network fragments
+	will be maintained for as long as 36 minutes in the Network Neighborhood
+	lists.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	Attempts to connect to these inaccessible computers will fail, but the
+	names will not be removed from the Network Neighborhood lists.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>NetBIOS name resolution</primary></indexterm>
+<indexterm><primary>DNS server</primary></indexterm>
+	If one of the fragments is cut off from the WINS server, it will only
+	be able to access servers on its local subnet using subnet-isolated
+	broadcast NetBIOS name resolution. The effect is similar to that of
+	losing access to a DNS server.
+	</para>
+</listitem>
+</orderedlist>
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+<indexterm><primary>browsing problems</primary></indexterm>
+<indexterm><primary>name resolution</primary></indexterm>
+Many questions are asked on the mailing lists regarding browsing. The majority of browsing
+problems originate from incorrect configuration of NetBIOS name resolution. Some are of
+particular note.
+</para>
+
+<sect2>
+<title>Flushing the Samba NetBIOS Name Cache</title>
+
+<para>
+How Can One Flush the Samba NetBIOS Name Cache without Restarting Samba?
+</para>
+
+<para>
+<indexterm><primary>flush name cache</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>NetBIOS name cache</primary></indexterm>
+<indexterm><primary>rogue machine</primary></indexterm>
+Samba's <command>nmbd</command> process controls all browse list handling. Under normal circumstances it is
+safe to restart <command>nmbd</command>. This will effectively flush the Samba NetBIOS name cache and cause it
+to be rebuilt. This does not make certain that a rogue machine name will not reappear
+in the browse list. When <command>nmbd</command> is taken out of service, another machine on the network will
+become the browse master. This new list may still have the rogue entry in it. If you really
+want to clear a rogue machine from the list, every machine on the network must be
+shut down and restarted after all machines are down. Failing a complete restart, the only
+other thing you can do is wait until the entry times out and is then flushed from the list.
+This may take a long time on some networks (perhaps months).
+</para>
+
+</sect2>
+
+<sect2>
+	<title>Server Resources Cannot Be Listed</title>
+
+<para><quote>My Client Reports "<quote>This server is not configured to list shared resources."</quote></quote></para>
+
+
+<para>
+Your guest account is probably invalid for some reason. Samba uses the
+guest account for browsing in <command>smbd</command>. Check that your guest account is
+valid.
+</para>
+
+<para>Also see <smbconfoption name="guest account"/> in the &smb.conf; man page.</para>
+
+</sect2>
+
+<sect2>
+	<title>I Get an "<errorname>Unable to browse the network</errorname>" Error</title>
+
+	<para>This error can have multiple causes:
+<indexterm><primary>browsing problems</primary></indexterm>
+	</para>
+
+	<itemizedlist>
+		<listitem><para>There is no LMB. Configure &nmbd;
+			or any other machine to serve as LMB.</para></listitem>
+		<listitem><para>You cannot log onto the machine that is the LMB.
+			Can you log on to it as a guest user? </para></listitem>
+		<listitem><para>There is no IP connectivity to the LMB.
+			Can you reach it by broadcast?</para></listitem>
+</itemizedlist>
+</sect2>
+
+<sect2>
+<title>Browsing of Shares and Directories is Very Slow</title>
+
+<para><quote>
+<indexterm><primary>slow browsing</primary></indexterm>
+There are only two machines on a test network. One is a Samba server, the other a Windows XP machine.
+Authentication and logons work perfectly, but when I try to explore shares on the Samba server, the
+Windows XP client becomes unresponsive. Sometimes it does not respond for some minutes. Eventually,
+Windows Explorer will respond and displays files and directories without problem.
+</quote>
+</para>
+
+<para><quote>
+<indexterm><primary>cmd</primary></indexterm>
+But, the share is immediately available from a command shell (<command>cmd</command>, followed by
+exploration with DOS command. Is this a Samba problem, or is it a Windows problem? How can I solve this?
+</quote></para>
+
+<para>
+Here are a few possibilities:
+</para>
+
+<variablelist>
+	<varlistentry>
+		<term>Bad Networking Hardware</term>
+		<listitem><para>
+<indexterm><primary>bad hardware</primary></indexterm>
+<indexterm><primary>WebClient</primary></indexterm>
+<indexterm><primary>defective hardware</primary></indexterm>
+<indexterm><primary>Bad networking hardware</primary></indexterm>
+<indexterm><primary>data corruption</primary></indexterm>
+		Most common defective hardware problems center around low cost or defective hubs, routers,
+		network interface controllers (NICs), and bad wiring. If one piece of hardware is defective,
+		the whole network may suffer. Bad networking hardware can cause data corruption. Most bad
+		networking hardware problems are accompanied by an increase in apparent network traffic,
+		but not all.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>The Windows XP WebClient</term>
+		<listitem><para>
+<indexterm><primary>network browsing problems</primary></indexterm>
+		A number of sites have reported similar slow network browsing problems and found that when
+		the WebClient service is turned off, the problem disappears. This is certainly something
+		that should be explored because it is a simple solution &smbmdash; if it works.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Inconsistent WINS Configuration</term>
+		<listitem><para>
+<indexterm><primary>WINS Configuration</primary></indexterm>
+<indexterm><primary>WINS server</primary></indexterm>
+		This type of problem is common when one client is configured to use a WINS server (that is
+		a TCP/IP configuration setting) and there is no WINS server on the network. Alternatively,
+		this will happen if there is a WINS server and Samba is not configured to use it. The use of
+		WINS is highly recommended if the network is using NetBIOS over TCP/IP protocols. If use
+		of NetBIOS over TCP/IP is disabled on all clients, Samba should not be configured as a WINS
+		server, nor should it be configured to use one.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Incorrect DNS Configuration</term>
+		<listitem><para>
+<indexterm><primary>DNS Configuration</primary></indexterm>
+<indexterm><primary>NetBIOS over TCP/IP disabled</primary></indexterm>
+		If use of NetBIOS over TCP/IP is disabled, Active Directory is in use and the DNS server
+		has been incorrectly configured. For further information refer to
+		<link linkend="adsdnstech">DNS and Active Directory</link>.
+		</para></listitem>
+	</varlistentry>
+</variablelist>
+
+</sect2>
+<sect2>
+<title>Invalid Cached Share References Affects Network Browsing</title>
+<para>
+<indexterm><primary>cached references</primary></indexterm>
+<indexterm><primary>stale network links</primary></indexterm>
+Cached references on your MS Windows client (workstation or server) to shares or servers that no longer exist
+can cause MS Windows Explorer to appear unresponsive as it tries to connect to these shares. After a delay
+(can take a long time) it times out and browsing will appear to be mostly normal again.
+</para>
+
+<para>
+To eliminate the problem the stale cached references should be removed. This does not happen automatically and
+requires manual intervention. This is a design feature of MS Windows and not anything that Samba can change.
+To remove the stale shortcuts found in <emphasis>My Network Places</emphasis> which refer to what are now
+invalid shares or servers it is necessary to edit the Windows Registry under
+<literal>HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\</literal>. Edit the entry
+<literal>MountPoints2</literal> (on Windows XP and later, or <literal>MountPoints</literal> on Windows 2000
+and earlier). Remove all keys named <literal>\\server\share</literal> (where 'server' and 'share' refer to a
+non-existent server or share).
+</para>
+
+<note><para>
+Removal of stale network links needs to be done on a per-user basis. Alternately, you can delete the
+shortcuts from the MS Windows Explorer in <literal>My Network Places</literal> just by right-clicking them and
+selecting <emphasis>Delete.</emphasis>
+</para></note>
+
+<para>
+<indexterm><primary>slow network browsing</primary></indexterm>
+Samba users have reported that these stale references negatively affect network browsing with Windows, Samba,
+and Novell servers. It is suspected to be a universal problem not directly related to the Samba
+server. Samba users may experience this more often due to Samba being somewhat viewed as an experimenter's
+toolkit. This results from the fact that a user might go through several reconfigurations and incarnations of
+their Samba server, by different names, with different shares, increasing the chances for having stale
+(invalid) cached share references. Windows clients do not expire these references thus necessitating manual
+removal.
+</para>
+
+<para>
+It is common for <emphasis>Open</emphasis> dialog boxes (for example; in Word and Excel) to respond very
+slowly, as they attempt to locate all of the cached references, even if they are not in the current directory
+being accessed.
+</para>
+</sect2>
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Other-Clients.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Other-Clients.xml
new file mode 100644
index 00000000000..94c3fcc81a4
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Other-Clients.xml
@@ -0,0 +1,351 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="Other-Clients">
+<chapterinfo>
+	&author.jelmer;
+	&author.jht;
+	&author.danshearer;
+	<author>&person.jmcd;<contrib>OS/2</contrib></author>
+	<pubdate>5 Mar 2001</pubdate>
+</chapterinfo>
+
+<title>Samba and Other CIFS Clients</title>
+
+<para>This chapter contains client-specific information.</para>
+
+<sect1>
+<title>Macintosh Clients</title>
+
+<para>
+<indexterm><primary>DAVE</primary></indexterm>
+Yes. <ulink url="http://www.thursby.com/">Thursby</ulink> has a CIFS client/server called <ulink
+url="http://www.thursby.com/products/dave.html">DAVE</ulink>.  They test it against Windows 95, Windows
+NT/200x/XP, and Samba for compatibility issues. At the time of this writing, DAVE was at version 5.1. Please
+refer to Thursby's Web site for more information regarding this product.
+</para>
+
+<para> 
+<indexterm><primary>Netatalk</primary></indexterm>
+<indexterm><primary>CAP</primary></indexterm>
+Alternatives include two free implementations of AppleTalk for several kinds of UNIX machines and several more
+commercial ones.  These products allow you to run file services and print services natively to Macintosh
+users, with no additional support required on the Macintosh. The two free implementations are <ulink
+url="http://www.umich.edu/~rsug/netatalk/">Netatalk</ulink> and <ulink
+url="http://www.cs.mu.oz.au/appletalk/atalk.html">CAP</ulink>.  What Samba offers MS Windows users, these
+packages offer to Macs.  For more info on these packages, Samba, and Linux (and other UNIX-based systems), see
+<ulink noescape="1" url="http://www.eats.com/linux_mac_win.html">http://www.eats.com/linux_mac_win.html.</ulink>
+</para>
+
+<para>Newer versions of the Macintosh (Mac OS X) include Samba.</para>
+
+</sect1>
+
+<sect1>
+<title>OS2 Client</title>
+
+	<sect2>
+		<title>Configuring OS/2 Warp Connect or OS/2 Warp 4</title>
+
+		<para>Basically, you need three components:</para>
+		
+		<itemizedlist>
+			<listitem><para>The File and Print Client (IBM peer)</para></listitem>
+			<listitem><para>TCP/IP (Internet support) </para></listitem>
+			<listitem><para>The <quote>NetBIOS over TCP/IP</quote> driver (TCPBEUI)</para></listitem>
+		</itemizedlist>
+		
+		<para>Installing the first two together with the base operating 
+		system on a blank system is explained in the Warp manual. If Warp 
+		has already been installed, but you now want to install the 
+		networking support, use the <quote>Selective Install for Networking</quote> 
+		object in the <quote>System Setup</quote> folder.</para>
+
+		<para>Adding the <quote>NetBIOS over TCP/IP</quote> driver is not described 
+		in the manual and just barely in the online documentation. Start 
+		<command>MPTS.EXE</command>, click on <guiicon>OK</guiicon>, click on <guimenu>Configure LAPS</guimenu>, and click 
+		on <guimenu>IBM OS/2 NETBIOS OVER TCP/IP</guimenu> in  <guilabel>Protocols</guilabel>. This line 
+		is then moved to <guilabel>Current Configuration</guilabel>. Select that line, 
+		click on <guimenuitem>Change number</guimenuitem>, and increase it from 0 to 1. Save this
+		configuration.</para>
+
+		<para>If the Samba server is not on your local subnet, you 
+		can optionally add IP names and addresses of these servers 
+		to the <guimenu>Names List</guimenu> or specify a  WINS server (NetBIOS 
+		Nameserver in IBM and RFC terminology). For Warp Connect, you 
+		may need to download an update for <constant>IBM Peer</constant> to bring it on 
+		the same level as Warp 4. See the IBM OS/2 Warp Web page</para>
+	</sect2>
+	
+	<sect2>
+		<title>Configuring Other Versions of OS/2</title>
+	
+		<para>This sections deals with configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x.</para>
+		
+		<para>You can use the free Microsoft LAN Manager 2.2c Client for OS/2 that is
+		available from 
+		<ulink noescape="1" url="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/">
+		ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</ulink>. In a nutshell, edit
+	the file <filename>\OS2VER</filename> in the root directory of the OS/2 boot partition and add the lines:</para>
+		
+		<para><programlisting>
+		20=setup.exe
+		20=netwksta.sys
+		20=netvdd.sys
+		</programlisting></para>
+		
+		<para>before you install the client. Also, do not use the included NE2000 driver because it is buggy.
+		Try the NE2000 or NS2000 driver from <ulink noescape="1" url="ftp://ftp.cdrom.com/pub/os2/network/ndis/">
+ 		ftp://ftp.cdrom.com/pub/os2/network/ndis/</ulink> instead.
+		</para>
+	</sect2>
+	
+	<sect2>
+		<title>Printer Driver Download for OS/2 Clients</title>
+
+		<para>Create a share called <smbconfsection name="[PRINTDRV]"/> that is 
+		world-readable. Copy your OS/2 driver files there. The <filename>.EA_</filename>
+		files must still be separate, so you will need to use the original install files
+		and not copy an installed driver from an OS/2 system.</para>
+		
+		<para>Install the NT driver first for that printer. Then, add to your &smb.conf; a parameter,
+		<smbconfoption name="os2 driver map"><replaceable>filename</replaceable></smbconfoption>. 
+		Next, in the file specified by <replaceable>filename</replaceable>, map the 
+		name of the NT driver name to the OS/2 driver name as follows:</para>
+		
+		<para><parameter><replaceable>nt driver name</replaceable> = <replaceable>os2 driver name</replaceable>.<replaceable>device name</replaceable></parameter>, e.g.,</para>
+
+		<para><parameter>
+		HP LaserJet 5L = LASERJET.HP LaserJet 5L</parameter></para>
+
+		<para>You can have multiple drivers mapped in this file.</para>
+	
+		<para>If you only specify the OS/2 driver name, and not the 
+		device name, the first attempt to download the driver will 
+		actually download the files, but the OS/2 client will tell 
+		you the driver is not available. On the second attempt, it 
+		will work. This is fixed simply by adding the device name
+  		 to the mapping, after which it will work on the first attempt.
+		</para>
+	</sect2>
+</sect1>
+
+<sect1>
+<title>Windows for Workgroups</title>
+
+<sect2>
+<title>Latest TCP/IP Stack from Microsoft</title>
+
+<para>Use the latest TCP/IP stack from Microsoft if you use Windows
+for Workgroups. The early TCP/IP stacks had lots of bugs.</para>
+
+<para> 
+Microsoft has released an incremental upgrade to its TCP/IP 32-bit VxD drivers. The latest release can be
+found at ftp.microsoft.com, located in <filename>/Softlib/MSLFILES/TCP32B.EXE</filename>.  There is an
+update.txt file there that describes the problems that were fixed. New files include
+<filename>WINSOCK.DLL</filename>, <filename>TELNET.EXE</filename>, <filename>WSOCK.386</filename>,
+<filename>VNBT.386</filename>, <filename>WSTCP.386</filename>, <filename>TRACERT.EXE</filename>,
+<filename>NETSTAT.EXE</filename>, and <filename>NBTSTAT.EXE</filename>.
+</para>
+
+<para>
+More information about this patch is available in <ulink
+url="http://support.microsoft.com/kb/q99891/">Knowledge Base article 99891</ulink>.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Delete .pwl Files After Password Change</title>
+
+<para>
+Windows for Workgroups does a lousy job with passwords. When you change passwords on either
+the UNIX box or the PC, the safest thing to do is delete the .pwl files in the Windows
+directory. The PC will complain about not finding the files, but will soon get over it,
+allowing you to enter the new password.
+</para>
+
+<para> 
+If you do not do this, you may find that Windows for Workgroups remembers and uses the old
+password, even if you told it a new one.
+</para>
+
+<para> 
+Often Windows for Workgroups will totally ignore a password you give it in a dialog box.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Configuring Windows for Workgroups Password Handling</title>
+
+<para>
+<indexterm><primary>admincfg.exe</primary></indexterm>
+There is a program call <filename>admincfg.exe</filename> on the last disk (disk 8) of the WFW 3.11 disk set.
+To install it, type <userinput>EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE</userinput>.  Then add an icon
+for it via the <application>Program Manager</application> <guimenu>New</guimenu> menu.  This program allows
+you to control how WFW handles passwords, Disable Password Caching and so on, for use with <smbconfoption
+name="security">user</smbconfoption>.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Password Case Sensitivity</title>
+
+<para>Windows for Workgroups uppercases the password before sending it to the server.
+UNIX passwords can be case-sensitive though. Check the &smb.conf; information on
+<smbconfoption name="password level"/> to specify what characters
+Samba should try to uppercase when checking.</para>
+
+</sect2>
+
+<sect2>
+<title>Use TCP/IP as Default Protocol</title>
+
+<para>To support print queue reporting, you may find
+that you have to use TCP/IP as the default protocol under
+Windows for Workgroups. For some reason, if you leave NetBEUI as the default,
+it may break the print queue reporting on some systems.
+It is presumably a Windows for Workgroups bug.</para>
+
+</sect2>
+
+<sect2 id="speedimpr">
+<title>Speed Improvement</title>
+
+<para>
+Note that some people have found that setting <parameter>DefaultRcvWindow</parameter> in
+the <smbconfsection name="[MSTCP]"/> section of the 
+<filename>SYSTEM.INI</filename> file under Windows for Workgroups to 3072 gives a
+big improvement.
+</para>
+
+<para>
+My own experience with DefaultRcvWindow is that I get a much better
+performance with a large value (16384 or larger). Other people have
+reported that anything over 3072 slows things down enormously. One
+person even reported a speed drop of a factor of 30 when he went from
+3072 to 8192.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Windows 95/98</title>
+
+<para>
+When using Windows 95 OEM SR2, the following updates are recommended where Samba
+is being used. Please note that the changes documented in 
+<link linkend="speedimpr">Speed Improvement</link> will affect you once these
+updates  have been installed.
+</para>
+
+<para> 
+There are more updates than the ones mentioned here. Refer to the
+Microsoft Web site for all currently available updates to your specific version
+of Windows 95.
+</para>
+
+<simplelist>
+<member>Kernel Update: KRNLUPD.EXE</member>
+<member>Ping Fix: PINGUPD.EXE</member>
+<member>RPC Update: RPCRTUPD.EXE</member>
+<member>TCP/IP Update: VIPUPD.EXE</member>
+<member>Redirector Update: VRDRUPD.EXE</member>
+</simplelist>
+
+<para>
+Also, if using <application>MS Outlook,</application> it is desirable to 
+install the <command>OLEUPD.EXE</command> fix. This
+fix may stop your machine from hanging for an extended period when exiting
+Outlook, and you may notice a significant speedup when accessing network
+neighborhood services.
+</para>
+
+<sect2>
+<title>Speed Improvement</title>
+
+<para>
+Configure the Windows 95 TCP/IP registry settings to give better
+performance. I use a program called <command>MTUSPEED.exe</command> that I got off the
+Internet. There are various other utilities of this type freely available.
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Windows 2000 Service Pack 2</title>
+
+<para> 
+There are several annoyances with Windows 2000 SP2, one of which
+only appears when using a Samba server to host user profiles
+to Windows 2000 SP2 clients in a Windows domain. This assumes
+that Samba is a member of the domain, but the problem will
+most likely occur if it is not.
+</para>
+
+<para> 
+In order to serve profiles successfully to Windows 2000 SP2 
+clients (when not operating as a PDC), Samba must have 
+<smbconfoption name="nt acl support">no</smbconfoption>
+added to the file share that houses the roaming profiles.
+If this is not done, then the Windows 2000 SP2 client will
+complain about not being able to access the profile (Access 
+Denied) and create multiple copies of it on disk (DOMAIN.user.001,
+DOMAIN.user.002, and so on). See the &smb.conf; man page
+for more details on this option. Also note that the 
+<smbconfoption name="nt acl support"/> parameter was formally a global parameter in
+releases prior to Samba 2.2.2.
+</para>
+
+<para> 
+<link linkend="minimalprofile">Following example</link> provides a minimal profile share.
+</para>
+
+<example id="minimalprofile">
+<title>Minimal Profile Share</title>
+<smbconfblock>
+<smbconfsection name="[profile]"/>
+<smbconfoption name="path">/export/profile</smbconfoption>
+<smbconfoption name="create mask">0600</smbconfoption>
+<smbconfoption name="directory mask">0700</smbconfoption>
+<smbconfoption name="nt acl support">no</smbconfoption>
+<smbconfoption name="read only">no</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+The reason for this bug is that the Windows 200x SP2 client copies
+the security descriptor for the profile that contains
+the Samba server's SID, and not the domain SID. The client
+compares the SID for SAMBA\user and realizes it is
+different from the one assigned to DOMAIN\user; hence,
+<errorname>access denied</errorname> message.
+</para>
+
+<para>
+When the <smbconfoption name="nt acl support"/> parameter is disabled, Samba will send
+the Windows 200x client a response to the QuerySecurityDescriptor trans2 call, which causes the client
+to set a default ACL for the profile. This default ACL includes:
+</para>
+
+<para><emphasis>DOMAIN\user 	<quote>Full Control</quote></emphasis>></para>
+
+<note><para>This bug does not occur when using Winbind to
+create accounts on the Samba host for Domain users.</para></note>
+
+</sect1>
+
+<sect1>
+<title>Windows NT 3.1</title>
+
+<para>If you have problems communicating across routers with Windows 
+NT 3.1 workstations, read <ulink url="http://support.microsoft.com/default.aspx?scid=kb;Q103765">this Microsoft Knowledge Base article:</ulink>.
+
+</para>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-PAM.xml b/docs-xml/Samba3-HOWTO/TOSHARG-PAM.xml
new file mode 100644
index 00000000000..072e88a5bab
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-PAM.xml
@@ -0,0 +1,1013 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="pam">
+<chapterinfo>
+	&author.jht;
+	<author>
+		<firstname>Stephen</firstname><surname>Langasek</surname>
+		<affiliation>
+			<address><email>vorlon@netexpress.net</email></address>
+		</affiliation>
+	</author>
+    <pubdate>May 31, 2003</pubdate>
+</chapterinfo>
+ 
+<title>PAM-Based Distributed Authentication</title>
+
+<para>
+<indexterm><primary>PAM-enabled</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>Winbind-based authentication</primary></indexterm>
+This chapter should help you to deploy Winbind-based authentication on any PAM-enabled
+UNIX/Linux system. Winbind can be used to enable user-level application access authentication
+from any MS Windows NT domain, MS Windows 200x Active Directory-based
+domain, or any Samba-based domain environment. It will also help you to configure PAM-based local host access
+controls that are appropriate to your Samba configuration.
+</para>
+
+<para>
+<indexterm><primary>PAM management</primary></indexterm>
+<indexterm><primary>pam_smbpass.so</primary></indexterm>
+In addition to knowing how to configure Winbind into PAM, you will learn generic PAM management
+possibilities and in particular how to deploy tools like <filename>pam_smbpass.so</filename> to your advantage.
+</para>
+
+<note><para>
+The use of Winbind requires more than PAM configuration alone.
+Please refer to <link linkend="winbind">Winbind: Use of Domain Accounts</link>, for further information regarding Winbind.
+</para></note>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>Sun Solaris</primary></indexterm>
+<indexterm><primary>xxxxBSD</primary></indexterm>
+<indexterm><primary>Linux</primary></indexterm>
+<indexterm><primary>Pluggable Authentication Modules</primary><see>PAM</see></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>login</primary></indexterm>
+<indexterm><primary>passwd</primary></indexterm>
+<indexterm><primary>chown</primary></indexterm>
+A number of UNIX systems (e.g., Sun Solaris), as well as the xxxxBSD family and Linux,
+now utilize the Pluggable Authentication Modules (PAM) facility to provide all authentication, 
+authorization, and resource control services. Prior to the introduction of PAM, a decision
+to use an alternative to the system password database (<filename>/etc/passwd</filename>) 
+would require the provision of alternatives for all programs that provide security services.
+Such a choice would involve provision of alternatives to programs such as <command>login</command>, 
+<command>passwd</command>, <command>chown</command>, and so on.
+</para>
+
+<para>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>/etc/pam.conf</primary></indexterm>
+<indexterm><primary>Solaris</primary></indexterm>
+<indexterm><primary>/etc/pam.d</primary></indexterm>
+PAM provides a mechanism that disconnects these security programs from the underlying
+authentication/authorization infrastructure. PAM is configured by making appropriate modifications to one file,
+<filename>/etc/pam.conf</filename> (Solaris), or by editing individual control files that are
+located in <filename>/etc/pam.d</filename>.
+</para>
+
+<para>
+<indexterm><primary>PAM-enabled</primary></indexterm>
+<indexterm><primary>dynamically loadable library modules</primary></indexterm>
+On PAM-enabled UNIX/Linux systems, it is an easy matter to configure the system to use any
+authentication backend so long as the appropriate dynamically loadable library modules
+are available for it. The backend may be local to the system or may be centralized on a
+remote server.
+</para>
+
+<para>
+PAM support modules are available for:
+</para>
+
+<variablelist>
+	<varlistentry><term><filename>/etc/passwd</filename></term><listitem>
+		<para>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>PAM modules</primary></indexterm>
+<indexterm><primary>pam_unix.so</primary></indexterm>
+<indexterm><primary>pam_unix2.so</primary></indexterm>
+<indexterm><primary>pam_pwdb.so</primary></indexterm>
+<indexterm><primary>pam_userdb.so</primary></indexterm>
+		There are several PAM modules that interact with this standard UNIX user database. The most common are called
+		<filename>pam_unix.so</filename>, <filename>pam_unix2.so</filename>, <filename>pam_pwdb.so</filename> and
+		<filename>pam_userdb.so</filename>.
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term>Kerberos</term><listitem>
+		<para>
+<indexterm><primary>pam_krb5.so</primary></indexterm>
+<indexterm><primary>Kerberos</primary></indexterm>
+<indexterm><primary>Heimdal</primary></indexterm>
+<indexterm><primary>MIT Kerberos</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+		The <filename>pam_krb5.so</filename> module allows the use of any Kerberos-compliant server.
+		This tool is used to access MIT Kerberos, Heimdal Kerberos, and potentially
+		Microsoft Active Directory (if enabled).
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term>LDAP</term><listitem>
+		<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>pam_ldap.so</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>Sun ONE iDentity server</primary></indexterm>
+<indexterm><primary>Novell eDirectory server</primary></indexterm>
+<indexterm><primary>Microsoft Active Directory</primary></indexterm>
+		The <filename>pam_ldap.so</filename> module allows the use of any LDAP v2- or v3-compatible backend
+		server. Commonly used LDAP backend servers include OpenLDAP v2.0 and v2.1,
+		Sun ONE iDentity server, Novell eDirectory server, and Microsoft Active Directory.
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term>NetWare Bindery</term><listitem>
+		<para>
+<indexterm><primary>NetWare Bindery</primary></indexterm>
+<indexterm><primary>pam_ncp_auth.so</primary></indexterm>
+<indexterm><primary>bindery-enabled</primary></indexterm>
+<indexterm><primary>NetWare Core Protocol-based server</primary></indexterm>
+		The <filename>pam_ncp_auth.so</filename> module allows authentication off any bindery-enabled
+		NetWare Core Protocol-based server.
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term>SMB Password</term><listitem>
+		<para>
+<indexterm><primary>SMB Password</primary></indexterm>
+<indexterm><primary>pam_smbpass.so</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+		This module, called <filename>pam_smbpass.so</filename>, allows user authentication of
+		the passdb backend that is configured in the Samba &smb.conf; file.
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term>SMB Server</term><listitem>
+		<para>
+<indexterm><primary>SMB Server</primary></indexterm>
+<indexterm><primary>pam_smb_auth.so</primary></indexterm>
+		The <filename>pam_smb_auth.so</filename> module is the original MS Windows networking authentication
+		tool. This module has been somewhat outdated by the Winbind module.
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term>Winbind</term><listitem>
+		<para>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>pam_winbind.so</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+		The <filename>pam_winbind.so</filename> module allows Samba to obtain authentication from any
+		MS Windows domain controller. It can just as easily be used to authenticate
+		users for access to any PAM-enabled application.
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term>RADIUS</term><listitem>
+		<para>
+<indexterm><primary>Remote Access Dial-In User Service</primary><see>RADIUS</see></indexterm>
+		There is a PAM RADIUS (Remote Access Dial-In User Service) authentication
+		module. In most cases, administrators need to locate the source code
+		for this tool and compile and install it themselves. RADIUS protocols are
+		used by many routers and terminal servers.
+		</para>
+	</listitem></varlistentry>
+</variablelist>
+
+<para>
+<indexterm><primary>pam_smbpasswd.so</primary></indexterm>
+<indexterm><primary>pam_winbind.so</primary></indexterm>
+Of the modules listed, Samba provides the <filename>pam_smbpasswd.so</filename> and the
+<filename>pam_winbind.so</filename> modules alone.
+</para>
+
+<para>
+<indexterm><primary>wide-area network bandwidth</primary></indexterm>
+<indexterm><primary>efficient authentication</primary></indexterm>
+<indexterm><primary>PAM-capable</primary></indexterm>
+<indexterm><primary>centrally managed</primary></indexterm>
+Once configured, these permit a remarkable level of flexibility in the location and use
+of distributed Samba domain controllers that can provide wide-area network bandwidth,
+efficient authentication services for PAM-capable systems. In effect, this allows the
+deployment of centrally managed and maintained distributed authentication from a
+single-user account database.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Technical Discussion</title>
+
+<para>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>privilege-granting applications</primary></indexterm>
+<indexterm><primary>/etc/pam.conf</primary></indexterm>
+<indexterm><primary>/etc/pam.d/</primary></indexterm>
+PAM is designed to provide system administrators with a great deal of flexibility in
+configuration of the privilege-granting applications of their system. The local
+configuration of system security controlled by PAM is contained in one of two places:
+either the single system file <filename>/etc/pam.conf</filename> or the
+<filename>/etc/pam.d/</filename> directory.
+</para>
+
+<sect2>
+<title>PAM Configuration Syntax</title>
+
+<para>
+<indexterm><primary>PAM-specific tokens</primary></indexterm>
+<indexterm><primary>case sensitivity</primary></indexterm>
+In this section we discuss the correct syntax of and generic options respected by entries to these files.
+PAM-specific tokens in the configuration file are case insensitive. The module paths, however, are case
+sensitive, since they indicate a file's name and reflect the case dependence of typical file systems.  The
+case sensitivity of the arguments to any given module is defined for each module in turn.
+</para>
+
+<para>
+In addition to the lines described below, there are two special characters provided for the convenience
+of the system administrator: comments are preceded by a <quote>#</quote> and extend to the next end-of-line; also,
+module specification lines may be extended with a <quote>\</quote>-escaped newline. 
+</para>
+
+<para>
+<indexterm><primary>PAM authentication module</primary></indexterm>
+<indexterm><primary>/lib/security</primary></indexterm>
+If the PAM authentication module (loadable link library file) is located in the
+default location, then it is not necessary to specify the path. In the case of
+Linux, the default location is <filename>/lib/security</filename>. If the module
+is located outside the default, then the path must be specified as:
+<programlisting>
+auth  required  /other_path/pam_strange_module.so
+</programlisting>
+</para>
+
+<sect3>
+<title>Anatomy of <filename>/etc/pam.d</filename> Entries</title>
+
+<para>
+The remaining information in this subsection was taken from the documentation of the Linux-PAM
+project. For more information on PAM, see 
+<ulink url="http://ftp.kernel.org/pub/linux/libs/pam/">the Official Linux-PAM home page</ulink>.
+</para>
+
+<para>
+<indexterm><primary>/etc/pam.conf</primary></indexterm>
+A general configuration line of the <filename>/etc/pam.conf</filename> file has the following form:
+<programlisting>
+service-name   module-type   control-flag   module-path   args
+</programlisting>
+</para>
+
+<para>
+We explain the meaning of each of these tokens. The second (and more recently adopted)
+way of configuring Linux-PAM is via the contents of the <filename>/etc/pam.d/</filename> directory.
+Once we have explained the meaning of the tokens, we describe this method.
+</para>
+
+<variablelist>
+	<varlistentry><term>service-name</term><listitem>
+		<para>
+<indexterm><primary>ftpd</primary></indexterm>
+<indexterm><primary>rlogind</primary></indexterm>
+<indexterm><primary>su</primary></indexterm>
+		The name of the service associated with this entry. Frequently, the service-name is the conventional
+		name of the given application &smbmdash; for example, <command>ftpd</command>, <command>rlogind</command> and
+		<command>su</command>, and so on.
+		</para>
+
+		<para>
+		There is a special service-name reserved for defining a default authentication mechanism. It has
+		the name <parameter>OTHER</parameter> and may be specified in either lower- or uppercase characters.
+		Note, when there is a module specified for a named service, the <parameter>OTHER</parameter>
+		entries are ignored.
+		</para>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry><term>module-type</term><listitem>
+                <para>
+		One of (currently) four types of module. The four types are as follows:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+<indexterm><primary>auth</primary></indexterm>
+<indexterm><primary>/etc/groups</primary></indexterm>
+			<parameter>auth:</parameter> This module type provides two aspects of authenticating the user.
+			It establishes that the user is who he or she claims to be by instructing the application
+			to prompt the user for a password or other means of identification. Second, the module can
+			grant group membership (independently of the <filename>/etc/groups</filename> file)
+			or other privileges through its credential-granting properties.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>account</primary></indexterm>
+<indexterm><primary>non-authentication-based account management</primary></indexterm>
+			<parameter>account:</parameter> This module performs non-authentication-based account management.
+			It is typically used to restrict/permit access to a service based on the time of day, currently
+		 	available system resources (maximum number of users), or perhaps the location of the user 
+			login. For example, the <quote>root</quote> login may be permitted only on the console.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>session</primary></indexterm>
+			<parameter>session:</parameter> Primarily, this module is associated with doing things that need
+			to be done for the user before and after he or she can be given service. Such things include logging
+			information concerning the opening and closing of some data exchange with a user, mounting
+			directories, and so on.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>password</primary></indexterm>
+			<parameter>password:</parameter> This last module type is required for updating the authentication
+			token associated with the user. Typically, there is one module for each
+			<quote>challenge/response</quote> authentication <parameter>(auth)</parameter> module type.
+			</para></listitem>
+		</itemizedlist>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry><term>control-flag</term><listitem>
+		<para>
+		The control-flag is used to indicate how the PAM library will react to the success or failure of the
+		module it is associated with. Since modules can be stacked (modules of the same type execute in series,
+		one after another), the control-flags determine the relative importance of each module. The application
+		is not made aware of the individual success or failure of modules listed in the
+		<filename>/etc/pam.conf</filename> file. Instead, it receives a summary success or fail response from
+		the Linux-PAM library. The order of execution of these modules is that of the entries in the
+		<filename>/etc/pam.conf</filename> file; earlier entries are executed before later ones.
+		As of Linux-PAM v0.60, this control-flag can be defined with one of two syntaxes.
+		</para>
+
+		<para>
+<indexterm><primary>required</primary></indexterm>
+<indexterm><primary>requisite</primary></indexterm>
+<indexterm><primary>sufficient</primary></indexterm>
+<indexterm><primary>optional</primary></indexterm>
+		The simpler (and historical) syntax for the control-flag is a single keyword defined to indicate the
+		severity of concern associated with the success or failure of a specific module. There are four such
+		keywords: <parameter>required</parameter>, <parameter>requisite</parameter>,
+		<parameter>sufficient</parameter>, and <parameter>optional</parameter>.
+		</para>
+
+		<para>
+		The Linux-PAM library interprets these keywords in the following manner:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			<parameter>required:</parameter> This indicates that the success of the module is required for the
+			module-type facility to succeed. Failure of this module will not be apparent to the user until all
+			of the remaining modules (of the same module-type) have been executed.
+			</para></listitem>
+
+			<listitem><para>
+			<parameter>requisite:</parameter> Like required, except that if such a module returns a
+			failure, control is directly returned to the application. The return value is that associated with
+			the first required or requisite module to fail. This flag can be used to protect against the
+			possibility of a user getting the opportunity to enter a password over an unsafe medium. It is
+			conceivable that such behavior might inform an attacker of valid accounts on a system. This
+			possibility should be weighed against the not insignificant concerns of exposing a sensitive
+			password in a hostile environment.
+			</para></listitem>
+
+			<listitem><para>
+			<parameter>sufficient:</parameter> The success of this module is deemed <parameter>sufficient</parameter> to satisfy
+			the Linux-PAM library that this module-type has succeeded in its purpose. In the event that no
+			previous required module has failed, no more <quote>stacked</quote> modules of this type are invoked.
+			(In this case, subsequent required modules are not invoked). A failure of this module is not deemed
+			as fatal to satisfying the application that this module-type has succeeded.
+			</para></listitem>
+
+            <listitem><para>
+            <parameter>optional:</parameter> As its name suggests, this control-flag marks the module as not
+			being critical to the success or failure of the user's application for service. In general,
+			Linux-PAM ignores such a module when determining if the module stack will succeed or fail.
+			However, in the absence of any definite successes or failures of previous or subsequent stacked
+			modules, this module will determine the nature of the response to the application. One example of
+			this latter case is when the other modules return something like PAM_IGNORE.
+			</para></listitem>
+		</itemizedlist>
+
+		<para>
+		The more elaborate (newer) syntax is much more specific and gives the administrator a great deal of control
+		over how the user is authenticated. This form of the control-flag is delimited with square brackets and
+		consists of a series of <parameter>value=action</parameter> tokens:
+		</para>
+
+<para><programlisting>
+[value1=action1 value2=action2 ...]
+</programlisting></para>
+
+		<para>
+		Here, <parameter>value1</parameter> is one of the following return values:
+<screen>
+<parameter>success; open_err; symbol_err; service_err; system_err; buf_err;</parameter>
+<parameter>perm_denied; auth_err; cred_insufficient; authinfo_unavail;</parameter>
+<parameter>user_unknown; maxtries; new_authtok_reqd; acct_expired; session_err;</parameter>
+<parameter>cred_unavail; cred_expired; cred_err; no_module_data; conv_err;</parameter>
+<parameter>authtok_err; authtok_recover_err; authtok_lock_busy;</parameter>
+<parameter>authtok_disable_aging; try_again; ignore; abort; authtok_expired;</parameter>
+<parameter>module_unknown; bad_item;</parameter> and <parameter>default</parameter>.
+</screen>
+</para>
+
+		<para>
+		The last of these (<parameter>default</parameter>) can be used to set the action for those return values that are not explicitly defined.
+		</para>
+
+		<para>
+		The <parameter>action1</parameter> can be a positive integer or one of the following tokens: 
+		<parameter>ignore</parameter>; <parameter>ok</parameter>; <parameter>done</parameter>;
+		<parameter>bad</parameter>; <parameter>die</parameter>; and <parameter>reset</parameter>.
+		A positive integer, J, when specified as the action, can be used to indicate that the next J modules of the
+		current module-type will be skipped. In this way, the administrator can develop a moderately sophisticated
+		stack of modules with a number of different paths of execution. Which path is taken can be determined by the
+		reactions of individual modules.
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+			<parameter>ignore:</parameter> When used with a stack of modules, the module's return status will not
+			contribute to the return code the application obtains.
+			</para></listitem>
+
+			<listitem><para>
+            <parameter>bad:</parameter> This action indicates that the return code should be thought of as indicative
+			of the module failing. If this module is the first in the stack to fail, its status value will be used
+			for that of the whole stack.
+			</para></listitem>
+
+            <listitem><para>
+            <parameter>die:</parameter> Equivalent to bad with the side effect of terminating the module stack and
+			PAM immediately returning to the application.
+			</para></listitem>
+
+           <listitem><para>
+           <parameter>ok:</parameter> This tells PAM that the administrator thinks this return code should
+			contribute directly to the return code of the full stack of modules. In other words, if the former
+			state of the stack would lead to a return of PAM_SUCCESS, the module's return code will override
+			this value. Note, if the former state of the stack holds some value that is indicative of a module's
+			failure, this <parameter>ok</parameter> value will not be used to override that value.
+			</para></listitem>
+
+            <listitem><para>
+            <parameter>done:</parameter> Equivalent to <parameter>ok</parameter> with the side effect of terminating the module stack and
+			PAM immediately returning to the application.
+                        </para></listitem>
+
+           <listitem><para>
+           <parameter>reset:</parameter> Clears all memory of the state of the module stack and starts again with
+			the next stacked module.
+			</para></listitem>
+		</itemizedlist>
+
+		<para>
+		Each of the four keywords, <parameter>required</parameter>; <parameter>requisite</parameter>;
+		<parameter>sufficient</parameter>; and <parameter>optional</parameter>, have an equivalent expression in terms
+		of the [...] syntax. They are as follows:
+		</para>
+
+		<para>
+		<itemizedlist>
+			<listitem><para>
+			<parameter>required</parameter> is equivalent to <parameter>[success=ok new_authtok_reqd=ok ignore=ignore default=bad]</parameter>.
+			</para></listitem>
+
+			<listitem><para>
+			<parameter>requisite</parameter> is equivalent to <parameter>[success=ok new_authtok_reqd=ok ignore=ignore default=die]</parameter>.
+			</para></listitem>
+
+			<listitem><para>
+			<parameter>sufficient</parameter> is equivalent to <parameter>[success=done  new_authtok_reqd=done  default=ignore]</parameter>.
+			</para></listitem>
+
+			<listitem><para>
+			<parameter>optional</parameter> is equivalent to <parameter>[success=ok new_authtok_reqd=ok default=ignore]</parameter>.
+			</para></listitem>
+		</itemizedlist>
+		</para>
+
+		<para>
+		Just to get a feel for the power of this new syntax, here is a taste of what you can do with it. With Linux-PAM-0.63,
+		the notion of client plug-in agents was introduced. This makes it possible for PAM to support
+		machine-machine authentication using the transport protocol inherent to the client/server application. With the
+		<parameter>[ ... value=action ... ]</parameter> control syntax, it is possible for an application to be configured
+		to support binary prompts with compliant clients, but to gracefully fail over into an alternative authentication
+		mode for legacy applications.
+		</para>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry><term>module-path</term><listitem>
+		<para>
+		The pathname of the dynamically loadable object file; the pluggable module itself. If the first character of the
+		module path is <quote>/</quote>, it is assumed to be a complete path. If this is not the case, the given module path is appended
+		to the default module path: <filename>/lib/security</filename> (but see the previous notes).
+		</para>
+
+		<para>
+		The arguments are a list of tokens that are passed to the module when it is invoked, much like arguments to a typical
+		Linux shell command. Generally, valid arguments are optional and are specific to any given module. Invalid arguments
+		are ignored by a module; however, when encountering an invalid argument, the module is required to write an error
+		to syslog(3). For a list of generic options, see the next section.
+		</para>
+
+		<para>
+		If you wish to include spaces in an argument, you should surround that argument with square brackets. For example:
+		</para>
+
+<para><programlisting>
+squid auth required pam_mysql.so user=passwd_query passwd=mada \
+db=eminence [query=select user_name from internet_service where \
+user_name=<quote>%u</quote> and password=PASSWORD(<quote>%p</quote>) and service=<quote>web_proxy</quote>]
+</programlisting></para>
+
+		<para>
+		When using this convention, you can include <quote>[</quote> characters inside the string, and if you wish to have a <quote>]</quote>
+		character inside the string that will survive the argument parsing, you should use <quote>\[</quote>. In other words,
+		</para>
+
+<para><programlisting>
+[..[..\]..]    -->   ..[..]..
+</programlisting></para>
+
+		<para>
+		Any line in one of the configuration files that is not formatted correctly will generally tend (erring on the
+		side of caution) to make the authentication process fail. A corresponding error is written to the system log files
+		with a call to syslog(3). 
+		</para>
+		</listitem>
+	</varlistentry>
+</variablelist>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>Example System Configurations</title>
+
+<para>
+The following is an example <filename>/etc/pam.d/login</filename> configuration file. 
+This example had all options uncommented and is probably not usable 
+because it stacks many conditions before allowing successful completion 
+of the login process. Essentially, all conditions can be disabled 
+by commenting them out, except the calls to <filename>pam_pwdb.so</filename>.
+</para>
+
+<sect3>
+<title>PAM: Original Login Config</title>
+
+<para>
+	<programlisting>
+#%PAM-1.0
+# The PAM configuration file for the <quote>login</quote> service
+#
+auth         required    pam_securetty.so
+auth         required    pam_nologin.so
+# auth       required    pam_dialup.so
+# auth       optional    pam_mail.so
+auth         required    pam_pwdb.so shadow md5
+# account    requisite   pam_time.so
+account      required    pam_pwdb.so
+session      required    pam_pwdb.so
+# session    optional    pam_lastlog.so
+# password   required    pam_cracklib.so retry=3
+password     required    pam_pwdb.so shadow md5
+</programlisting>
+</para>
+
+</sect3>
+
+<sect3>
+<title>PAM: Login Using <filename>pam_smbpass</filename></title>
+
+<para>
+PAM allows use of replaceable modules. Those available on a sample system include:
+</para>
+
+<para><prompt>$</prompt><userinput>/bin/ls /lib/security</userinput>
+<programlisting>
+pam_access.so    pam_ftp.so          pam_limits.so     
+pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so     
+pam_cracklib.so  pam_group.so        pam_listfile.so   
+pam_nologin.so   pam_rootok.so       pam_tally.so      
+pam_deny.so      pam_issue.so        pam_mail.so       
+pam_permit.so    pam_securetty.so    pam_time.so       
+pam_dialup.so    pam_lastlog.so      pam_mkhomedir.so  
+pam_pwdb.so      pam_shells.so       pam_unix.so       
+pam_env.so       pam_ldap.so         pam_motd.so       
+pam_radius.so    pam_smbpass.so      pam_unix_acct.so  
+pam_wheel.so     pam_unix_auth.so    pam_unix_passwd.so
+pam_userdb.so    pam_warn.so         pam_unix_session.so
+</programlisting></para>
+
+<para>
+The following example for the login program replaces the use of 
+the <filename>pam_pwdb.so</filename> module that uses the system 
+password database (<filename>/etc/passwd</filename>,
+<filename>/etc/shadow</filename>, <filename>/etc/group</filename>) with 
+the module <filename>pam_smbpass.so</filename>, which uses the Samba 
+database containing the Microsoft MD4 encrypted password 
+hashes. This database is stored either in 
+<filename>/usr/local/samba/private/smbpasswd</filename>, 
+<filename>/etc/samba/smbpasswd</filename> or in 
+<filename>/etc/samba.d/smbpasswd</filename>, depending on the 
+Samba implementation for your UNIX/Linux system. The 
+<filename>pam_smbpass.so</filename> module is provided by 
+Samba version 2.2.1 or later. It can be compiled by specifying the 
+<option>--with-pam_smbpass</option> options when running Samba's
+<command>configure</command> script. For more information
+on the <filename>pam_smbpass</filename> module, see the documentation
+in the <filename>source/pam_smbpass</filename> directory of the Samba 
+source distribution.
+</para>
+
+<para>
+	<programlisting>
+#%PAM-1.0
+# The PAM configuration file for the <quote>login</quote> service
+#
+auth        required    pam_smbpass.so nodelay
+account     required    pam_smbpass.so nodelay
+session     required    pam_smbpass.so nodelay
+password    required    pam_smbpass.so nodelay
+</programlisting></para>
+
+<para>
+The following is the PAM configuration file for a particular 
+Linux system. The default condition uses <filename>pam_pwdb.so</filename>.
+</para>
+
+<para>
+	<programlisting>
+#%PAM-1.0
+# The PAM configuration file for the <quote>samba</quote> service
+#
+auth       required     pam_pwdb.so nullok nodelay shadow audit
+account    required     pam_pwdb.so audit nodelay
+session    required     pam_pwdb.so nodelay
+password   required     pam_pwdb.so shadow md5
+</programlisting></para>
+
+<para>
+In the following example, the decision has been made to use the 
+<command>smbpasswd</command> database even for basic Samba authentication. Such a 
+decision could also be made for the <command>passwd</command> program and would 
+thus allow the <command>smbpasswd</command> passwords to be changed using the
+<command>passwd</command> program:
+</para>
+
+<para>
+		<programlisting>
+#%PAM-1.0
+# The PAM configuration file for the <quote>samba</quote> service
+#
+auth       required     pam_smbpass.so nodelay
+account    required     pam_pwdb.so audit nodelay
+session    required     pam_pwdb.so nodelay
+password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
+</programlisting>
+</para>
+
+<note><para>PAM allows stacking of authentication mechanisms. It is 
+also possible to pass information obtained within one PAM module through 
+to the next module in the PAM stack. Please refer to the documentation for 
+your particular system implementation for details regarding the specific 
+capabilities of PAM in this environment. Some Linux implementations also 
+provide the <filename>pam_stack.so</filename> module that allows all 
+authentication to be configured in a single central file. The 
+<filename>pam_stack.so</filename> method has some devoted followers 
+on the basis that it allows for easier administration. As with all issues in 
+life, though, every decision has trade-offs, so you may want to examine the 
+PAM documentation for further helpful information.
+</para></note>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>&smb.conf; PAM Configuration</title>
+
+<para>
+There is an option in &smb.conf; called <smbconfoption name="obey pam restrictions"/>.
+The following is from the online help for this option in SWAT:
+</para>
+
+<blockquote>
+<para>
+When Samba is configured to enable PAM support (i.e., <option>--with-pam</option>), this parameter will 
+control whether or not Samba should obey PAM's account and session management directives. The default behavior 
+is to use PAM for clear-text authentication only and to ignore any account or session management. Samba always 
+ignores PAM for authentication in the case of <smbconfoption name="encrypt passwords">yes</smbconfoption>. 
+The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB 
+password encryption. 
+</para>
+
+<para>Default: <smbconfoption name="obey pam restrictions">no</smbconfoption></para>
+</blockquote>
+
+</sect2>
+
+<sect2>
+<title>Remote CIFS Authentication Using <filename>winbindd.so</filename></title>
+
+<para>
+All operating systems depend on the provision of user credentials acceptable to the platform.
+UNIX requires the provision of a user identifier (UID) as well as a group identifier (GID).
+These are both simple integer numbers that are obtained from a password backend such
+as <filename>/etc/passwd</filename>.
+</para>
+
+<para>
+Users and groups on a Windows NT server are assigned a relative ID (RID) which is unique for
+the domain when the user or group is created. To convert the Windows NT user or group into
+a  UNIX user or group, a mapping between RIDs and UNIX user and group IDs is required. This
+is one of the jobs that winbind performs.
+</para>
+
+<para>
+As winbind users and groups are resolved from a server, user and group IDs are allocated
+from a specified range. This is done on a first come, first served basis, although all
+existing users and groups will be mapped as soon as a client performs a user or  group 
+enumeration command. The allocated UNIX IDs are stored in a database file under the Samba
+lock directory and will be remembered.
+</para>
+
+<para>
+The astute administrator will realize from this that the combination of <filename>pam_smbpass.so</filename>, 
+<command>winbindd</command>, and a distributed <smbconfoption name="passdb backend"></smbconfoption>
+such as <parameter>ldap</parameter> will allow the establishment of a centrally managed, distributed user/password
+database that can also be used by all PAM-aware (e.g., Linux) programs and applications. This arrangement can have
+particularly potent advantages compared with the use of Microsoft Active Directory Service (ADS) insofar as
+the reduction of wide-area network authentication traffic.
+</para>
+
+<warning><para>
+The RID to UNIX ID database is the only location where the user and group  mappings are 
+stored by <command>winbindd</command>. If this file is deleted or corrupted, there is no way for <command>winbindd</command>
+to determine which user and group IDs correspond to Windows NT user and group RIDs.
+</para></warning>
+
+</sect2>
+
+<sect2>
+<title>Password Synchronization Using <filename>pam_smbpass.so</filename></title>
+
+<para>
+<filename>pam_smbpass</filename> is a PAM module that can be used on conforming systems to
+keep the <filename>smbpasswd</filename> (Samba password) database in sync with the UNIX
+password file. PAM is an API supported
+under some UNIX operating systems, such as Solaris, HPUX, and Linux, that provides a
+generic interface to authentication mechanisms.
+</para>
+
+<para>
+This module authenticates a local <filename>smbpasswd</filename> user database. If you require
+support for authenticating against a remote SMB server, or if you are
+concerned about the presence of SUID root binaries on your system, it is
+recommended that you use <filename>pam_winbind</filename> instead.
+</para>
+
+<para>
+Options recognized by this module are shown in <link linkend="smbpassoptions">next table</link>.
+<table frame="all" id="smbpassoptions">
+	<title>Options recognized by <parameter>pam_smbpass</parameter></title>
+	<tgroup cols="2" align="left">
+		<colspec align="left"/>
+		<colspec align="justify" colwidth="1*"/>
+	<tbody>
+		<row><entry>debug</entry><entry>Log more debugging info.</entry></row>
+		<row><entry>audit</entry><entry>Like debug, but also logs unknown usernames.</entry></row>
+		<row><entry>use_first_pass</entry><entry>Do not prompt the user for passwords; take them from PAM_ items instead.</entry></row>
+		<row><entry>try_first_pass</entry><entry>Try to get the password from a previous PAM module; fall back to prompting the user.</entry></row>
+		<row><entry>use_authtok</entry>
+			<entry>Like try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set (intended for stacking password modules only).</entry></row>
+		<row><entry>not_set_pass</entry><entry>Do not make passwords used by this module available to other modules.</entry></row>
+		<row><entry>nodelay</entry><entry>dDo not insert ~1-second delays on authentication failure.</entry></row>
+		<row><entry>nullok</entry><entry>Null passwords are allowed.</entry></row>
+		<row><entry>nonull</entry><entry>Null passwords are not allowed. Used to override the Samba configuration.</entry></row>
+		<row><entry>migrate</entry><entry>Only meaningful in an <quote>auth</quote> context; used to update smbpasswd file with a password used for successful authentication.</entry></row>
+		<row><entry>smbconf=<replaceable>file</replaceable></entry><entry>Specify an alternate path to the &smb.conf; file.</entry></row>
+	</tbody>
+</tgroup>
+</table>
+</para>
+
+<para>
+The following are examples of the use of <filename>pam_smbpass.so</filename> in the format of the Linux
+<filename>/etc/pam.d/</filename> files structure. Those wishing to implement this
+tool on other platforms will need to adapt this appropriately.
+</para>
+
+<sect3>
+<title>Password Synchronization Configuration</title>
+
+<para>
+The following is a sample PAM configuration that shows the use of pam_smbpass to make
+sure <filename>private/smbpasswd</filename> is kept in sync when <filename>/etc/passwd (/etc/shadow)</filename>
+is changed. It is useful when an expired password might be changed by an
+application (such as <command>ssh</command>).
+</para>
+
+<para>
+	<programlisting>
+#%PAM-1.0
+# password-sync
+#
+auth       requisite    pam_nologin.so
+auth       required     pam_unix.so
+account    required     pam_unix.so
+password   requisite    pam_cracklib.so retry=3
+password   requisite    pam_unix.so shadow md5 use_authtok try_first_pass
+password   required     pam_smbpass.so nullok use_authtok try_first_pass
+session    required     pam_unix.so
+</programlisting></para>
+</sect3>
+
+<sect3>
+<title>Password Migration Configuration</title>
+
+<para>
+The following PAM configuration shows the use of <filename>pam_smbpass</filename> to migrate
+from plaintext to encrypted passwords for Samba. Unlike other methods,
+this can be used for users who have never connected to Samba shares:
+password migration takes place when users <command>ftp</command> in, login using <command>ssh</command>, pop
+their mail, and so on.
+</para>
+
+<para>
+	<programlisting>
+#%PAM-1.0
+# password-migration
+#
+auth       requisite   pam_nologin.so
+# pam_smbpass is called IF pam_unix succeeds.
+auth       requisite   pam_unix.so
+auth       optional    pam_smbpass.so migrate
+account    required    pam_unix.so
+password   requisite   pam_cracklib.so retry=3
+password   requisite   pam_unix.so shadow md5 use_authtok try_first_pass
+password   optional    pam_smbpass.so nullok use_authtok try_first_pass
+session    required    pam_unix.so
+</programlisting></para>
+</sect3>
+
+<sect3>
+<title>Mature Password Configuration</title>
+
+<para>
+The following is a sample PAM configuration for a mature <filename>smbpasswd</filename> installation.
+<filename>private/smbpasswd</filename> is fully populated, and we consider it an error if
+the SMB password does not exist or does not match the UNIX password.
+</para>
+
+<para>
+<programlisting>
+#%PAM-1.0
+# password-mature
+#
+auth       requisite    pam_nologin.so
+auth       required     pam_unix.so
+account    required     pam_unix.so
+password   requisite    pam_cracklib.so retry=3
+password   requisite    pam_unix.so shadow md5 use_authtok try_first_pass
+password   required     pam_smbpass.so use_authtok use_first_pass
+session    required     pam_unix.so
+</programlisting></para>
+</sect3>
+
+<sect3>
+<title>Kerberos Password Integration Configuration</title>
+
+<para>
+The following is a sample PAM configuration that shows <parameter>pam_smbpass</parameter> used together with
+<parameter>pam_krb5</parameter>. This could be useful on a Samba PDC that is also a member of
+a Kerberos realm.
+</para>
+
+<para>
+		<programlisting>
+#%PAM-1.0
+# kdc-pdc
+#
+auth       requisite   pam_nologin.so
+auth       requisite   pam_krb5.so
+auth       optional    pam_smbpass.so migrate
+account    required    pam_krb5.so
+password   requisite   pam_cracklib.so retry=3
+password   optional    pam_smbpass.so nullok use_authtok try_first_pass
+password   required    pam_krb5.so use_authtok try_first_pass
+session    required    pam_krb5.so
+</programlisting></para>
+
+</sect3>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+PAM can be fickle and sensitive to configuration glitches. Here we look at a few cases from
+the Samba mailing list.
+</para>
+
+	<sect2>
+	<title>pam_winbind Problem</title>
+
+	<para>
+	A user reported, <emphasis>I have the following PAM configuration</emphasis>:
+	</para>
+
+<para>
+<programlisting>
+auth required /lib/security/pam_securetty.so
+auth sufficient /lib/security/pam_winbind.so
+auth sufficient /lib/security/pam_unix.so use_first_pass nullok
+auth required /lib/security/pam_stack.so service=system-auth
+auth required /lib/security/pam_nologin.so
+account required /lib/security/pam_stack.so service=system-auth
+account required /lib/security/pam_winbind.so
+password required /lib/security/pam_stack.so service=system-auth
+</programlisting>
+</para>
+
+	<para>
+	<emphasis>When I open a new console with [ctrl][alt][F1], I can't log in with my user <quote>pitie.</quote>
+	I have tried with user <quote>scienceu\pitie</quote> also.</emphasis>
+	</para>
+
+	<para>
+	The problem may lie with the inclusion of <parameter>pam_stack.so
+	service=system-auth</parameter>. That file often contains a lot of stuff that may
+	duplicate what you are already doing. Try commenting out the <parameter>pam_stack</parameter> lines
+	for <parameter>auth</parameter> and <parameter>account</parameter> and see if things work. If they do, look at
+	<filename>/etc/pam.d/system-auth</filename> and copy only what you need from it into your
+	<filename>/etc/pam.d/login</filename> file. Alternatively, if you want all services to use
+	Winbind, you can put the Winbind-specific stuff in <filename>/etc/pam.d/system-auth</filename>.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Winbind Is Not Resolving Users and Groups</title>
+
+	<para>
+	<quote>
+	My &smb.conf; file is correctly configured. I have specified 
+	<smbconfoption name="idmap uid">12000</smbconfoption> 
+	and <smbconfoption name="idmap gid">3000-3500,</smbconfoption>
+	and <command>winbind</command> is running. When I do the following it all works fine.
+	</quote>
+	</para>
+
+<para><screen>
+&rootprompt;<userinput>wbinfo -u</userinput>
+MIDEARTH\maryo
+MIDEARTH\jackb
+MIDEARTH\ameds
+...
+MIDEARTH\root
+
+&rootprompt;<userinput>wbinfo -g</userinput>
+MIDEARTH\Domain Users
+MIDEARTH\Domain Admins
+MIDEARTH\Domain Guests
+...
+MIDEARTH\Accounts
+
+&rootprompt;<userinput>getent passwd</userinput>
+root:x:0:0:root:/root:/bin/bash
+bin:x:1:1:bin:/bin:/bin/bash
+...
+maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
+</screen></para>
+
+	<para>
+	<quote>
+	But this command fails:
+	</quote>
+<screen>
+&rootprompt;<userinput>chown maryo a_file</userinput>
+chown: 'maryo': invalid user
+</screen>
+	<quote>This is driving me nuts! What can be wrong?</quote>
+	</para>
+
+	<para>
+	Your system is likely running <command>nscd</command>, the name service
+	caching daemon. Shut it down, do not restart it! You will find your problem resolved.
+	</para>
+
+	</sect2>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml b/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml
new file mode 100644
index 00000000000..d37edbe17fa
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml
@@ -0,0 +1,1409 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="samba-pdc">
+
+<chapterinfo>
+	&author.jht;
+	&author.jerry;
+	&author.dbannon;
+	<author>&person.gd; <contrib>LDAP updates</contrib></author>
+</chapterinfo>
+
+<title>Domain Control</title>
+
+<para>
+There are many who approach MS Windows networking with incredible misconceptions.
+That's okay, because it gives the rest of us plenty of opportunity to be of assistance.
+Those who really want help are well advised to become familiar with information
+that is already available.
+</para>
+
+<para>
+<indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
+You are advised not to tackle this section without having first understood
+and mastered some basics. MS Windows networking is not particularly forgiving of
+misconfiguration. Users of MS Windows networking are likely to complain 
+of persistent niggles that may be caused by a broken network configuration.
+To a great many people, however, MS Windows networking starts with a domain controller
+that in some magical way is expected to solve all network operational ills.
+</para>
+
+<para>
+<link linkend="domain-example">The Example Domain Illustration</link> shows a typical MS Windows domain security
+network environment. Workstations A, B, and C are representative of many physical MS Windows
+network clients.
+</para>
+
+<figure id="domain-example">
+	<title>An Example Domain.</title>
+	<imagefile scale="40">domain</imagefile>
+</figure>
+
+<para>
+From the Samba mailing list we can readily identify many common networking issues.
+If you are not clear on the following subjects, then it will do much good to read the 
+sections of this HOWTO that deal with it. These are the most common causes of MS Windows
+networking problems:
+</para>
+
+<itemizedlist>
+	<listitem><para>Basic TCP/IP configuration.</para></listitem>
+	<listitem><para>NetBIOS name resolution.</para></listitem>
+	<listitem><para>Authentication configuration.</para></listitem>
+	<listitem><para>User and group configuration.</para></listitem>
+	<listitem><para>Basic file and directory permission control in UNIX/Linux.</para></listitem>
+	<listitem><para>Understanding how MS Windows clients interoperate in a network environment.</para></listitem>
+</itemizedlist>
+
+<para>
+Do not be put off; on the surface of it MS Windows networking seems so simple that anyone 
+can do it. In fact, it is not a good idea to set up an MS Windows network with
+inadequate training and preparation. But let's get our first indelible principle out of the
+way: <emphasis>It is perfectly okay to make mistakes!</emphasis> In the right place and at
+the right time, mistakes are the essence of learning. It is very much not okay to make
+mistakes that cause loss of productivity and impose an avoidable financial burden on an
+organization.
+</para>
+
+<para>
+Where is the right place to make mistakes? Only out of harms way. If you are going to
+make mistakes, then please do it on a test network, away from users, and in such a way as
+to not inflict pain on others. Do your learning on a test network.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>domain security</primary></indexterm>
+<emphasis>What is the key benefit of Microsoft Domain Security?</emphasis>
+</para>
+
+<para>
+<indexterm>single sign-on<primary></primary><see>SSO</see></indexterm>
+<indexterm><primary>trust</primary></indexterm>
+<indexterm><primary>account</primary></indexterm>
+<indexterm><primary>domain</primary><secondary>security</secondary><tertiary>protocols</tertiary></indexterm>
+In a word, <emphasis>single sign-on</emphasis>, or SSO for short. To many, this is the Holy Grail of MS
+Windows NT and beyond networking. SSO allows users in a well-designed network to log onto any workstation that
+is a member of the domain that contains their user account (or in a domain that has an appropriate trust
+relationship with the domain they are visiting) and they will be able to log onto the network and access
+resources (shares, files, and printers) as if they are sitting at their home (personal) workstation. This is a
+feature of the domain security protocols.
+</para>
+
+<para>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>RID</primary></indexterm>
+<indexterm><primary>relative identifier</primary><see>RID</see></indexterm>
+<indexterm><primary>security identifier</primary><see>SID</see></indexterm>
+<indexterm><primary>access control</primary></indexterm>
+The benefits of domain security are available to those sites that deploy a Samba PDC.  A domain provides a
+unique network security identifier (SID). Domain user and group security identifiers are comprised of the
+network SID plus a relative identifier (RID) that is unique to the account. User and group SIDs (the network
+SID plus the RID) can be used to create access control lists (ACLs) attached to network resources to provide
+organizational access control. UNIX systems recognize only local security identifiers.
+</para>
+
+<para>
+<indexterm><primary>SID</primary></indexterm>
+A SID represents a security context. For example, every Windows machine has local accounts within the security
+context of the local machine which has a unique SID. Every domain (NT4, ADS, Samba) contains accounts that
+exist within the domain security context which is defined by the domain SID.
+</para>
+
+<para>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>RID</primary></indexterm>
+A domain member server will have a SID that differs from the domain SID.  The domain member server can be
+configured to regard all domain users as local users. It can also be configured to recognize domain users and
+groups as non-local. SIDs are persistent. A typical domain of user SID looks like this:
+<screen>
+S-1-5-21-726309263-4128913605-1168186429
+</screen>
+Every account (user, group, machine, trust, etc.) is assigned a RID. This is done automatically as an account
+is created. Samba produces the RID algorithmically. The UNIX operating system uses a separate name space for
+user and group identifiers (the UID and GID) but Windows allocates the RID from a single name space. A Windows
+user and a Windows group can not have the same RID. Just as the UNIX user <literal>root</literal> has the
+UID=0, the Windows Administrator has the well-known RID=500. The RID is catenated to the Windows domain SID,
+so Administrator account for a domain that has the above SID will have the user SID
+<screen>
+S-1-5-21-726309263-4128913605-1168186429-500
+</screen>
+The result is that every account in the Windows networking world has a globally unique security identifier.
+</para>
+
+<note><para>
+<indexterm><primary>domain</primary><secondary>member</secondary></indexterm>
+<indexterm><primary>machine account</primary></indexterm>
+<indexterm><primary>domain</primary><secondary>trust account</secondary></indexterm>
+Network clients of an MS Windows domain security environment must be domain members to be able to gain access
+to the advanced features provided. Domain membership involves more than just setting the workgroup name to the
+domain name. It requires the creation of a domain trust account for the workstation (called a machine
+account). Refer to <link linkend="domain-member">Domain Membership</link> for more information.
+</para></note>
+
+<para>
+The following functionalities are new to the Samba-3 release:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<indexterm><primary>account</primary><secondary>backend</secondary></indexterm>
+	Samba-3 supports the use of a choice of backends that may be used in which user, group and machine
+	accounts may be stored. Multiple passwd backends can be used in combination, either as additive backend
+	data sets, or as fail-over data sets.
+	</para>
+
+	<para>
+	<indexterm><primary>LDAP</primary></indexterm>
+	<indexterm><primary>replicated</primary></indexterm>
+	<indexterm><primary>distributed</primary></indexterm>
+	<indexterm><primary>scalability</primary></indexterm>
+	<indexterm><primary>reliability</primary></indexterm>
+	An LDAP passdb backend confers the benefit that the account backend can be distributed and replicated,
+	which is of great value because it confers scalability and provides a high degree of reliability. 
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>interdomain</primary><secondary>trust</secondary><tertiary>account</tertiary></indexterm>
+	<indexterm><primary>trust account</primary><secondary>interdomain</secondary></indexterm>
+	<indexterm><primary>interoperability</primary></indexterm>
+	Windows NT4 domain trusts. Samba-3 supports workstation and server (machine) trust accounts. It also
+	supports Windows NT4 style interdomain trust accounts, which further assists in network scalability
+	and interoperability.
+	</para></listitem>
+	
+	<listitem><para>
+	<indexterm><primary>NetBIOS</primary></indexterm>
+	<indexterm><primary>raw SMB</primary></indexterm>
+	<indexterm><primary>active directory</primary></indexterm>
+	<indexterm><primary>domain</primary><secondary>member server</secondary></indexterm>
+	<indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
+	<indexterm><primary>network</primary><secondary>browsing</secondary></indexterm>
+	Operation without NetBIOS over TCP/IP, rather using the raw SMB over TCP/IP. Note, this is feasible
+	only when operating as a Microsoft active directory domain member server. When acting as a Samba domain
+	controller the use of NetBIOS is necessary to provide network browsing support.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>WINS</primary></indexterm>
+	<indexterm><primary>TCP port</primary></indexterm>
+	<indexterm><primary>session services</primary></indexterm>
+	Samba-3 provides NetBIOS name services (WINS), NetBIOS over TCP/IP (TCP port 139) session services, SMB over
+	TCP/IP (TCP port 445) session services, and Microsoft compatible ONC DCE RPC services (TCP port 135)
+	services.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>Nexus.exe</primary></indexterm>
+	Management of users and groups via the User Manager for Domains. This can be done on any MS Windows client
+	using the <filename>Nexus.exe</filename> toolkit for Windows 9x/Me, or using the SRVTOOLS.EXE package for MS
+	Windows NT4/200x/XP platforms. These packages are available from Microsoft's Web site.
+	</para></listitem>
+
+	<listitem><para>
+	Implements full Unicode support. This simplifies cross-locale internationalization support. It also opens up
+	the use of protocols that Samba-2.2.x had but could not use due to the need to fully support Unicode.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+The following functionalities are not provided by Samba-3:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<indexterm><primary>SAM</primary></indexterm>
+	<indexterm><primary>replication</primary></indexterm>
+	SAM replication with Windows NT4 domain controllers (i.e., a Samba PDC and a Windows NT BDC, or vice versa).
+	This means Samba cannot operate as a BDC when the PDC is Microsoft-based Windows NT PDC. Samba-3 can not
+	participate in replication of account data to Windows PDCs and BDCs.
+	</para></listitem>
+	
+	<listitem><para>
+	<indexterm><primary>kerberos</primary></indexterm>
+	<indexterm><primary>active directory</primary></indexterm>
+	Acting as a Windows 2000 active directory domain controller (i.e., Kerberos and Active Directory). In point of
+	fact, Samba-3 does have some Active Directory domain control ability that is at this time purely experimental.
+	Active directory domain control is one of the features that is being developed in Samba-4, the next
+	generation Samba release. At this time there are no plans to enable active directory domain control
+	support during the Samba-3 series life-cycle.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>MMC</primary></indexterm>
+	<indexterm><primary>SVRTOOLS.EXE</primary></indexterm>
+	<indexterm><primary>Microsoft management console</primary><see>MMC</see></indexterm>
+	The Windows 200x/XP Microsoft Management Console (MMC) cannot be used to manage a Samba-3 server. For this you
+	can use only the MS Windows NT4 Domain Server Manager and the MS Windows NT4 Domain User Manager. Both are
+	part of the SVRTOOLS.EXE package mentioned later.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>Windows XP Home edition</primary></indexterm>
+<indexterm><primary>LanMan</primary></indexterm>
+Windows 9x/Me/XP Home clients are not true members of a domain for reasons outlined in this chapter. The
+protocol for support of Windows 9x/Me-style network (domain) logons is completely different from NT4/Windows
+200x-type domain logons and has been officially supported for some time. These clients use the old LanMan
+network logon facilities that are supported in Samba since approximately the Samba-1.9.15 series.
+</para>
+
+<para>
+<indexterm><primary>group</primary><secondary>mapping</secondary></indexterm>
+Samba-3 implements group mapping between Windows NT groups and UNIX groups (this is really quite complicated
+to explain in a short space). This is discussed more fully in <link linkend="groupmapping">Group Mapping: MS
+Windows and UNIX</link>.
+</para>
+
+<para>
+<indexterm><primary>machine trust account</primary></indexterm>
+<indexterm><primary>trust account</primary><secondary>machine</secondary></indexterm>
+<indexterm><primary>machine account</primary></indexterm>
+Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store user and Machine Trust
+Account information in a suitable backend data-store.  Refer to <link linkend="machine-trust-accounts">MS
+Windows Workstation/Server Machine Trust Accounts</link>. With Samba-3 there can be multiple backends for
+this. A complete discussion of account database backends can be found in <link linkend="passdb">Account
+Information Databases</link>.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Single Sign-On and Domain Security</title>
+
+<para>
+<indexterm><primary>single sign-on</primary><see>SSO</see></indexterm>
+<indexterm><primary>SSO</primary></indexterm>
+<indexterm><primary>active directory</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+<indexterm><primary>validation</primary></indexterm>
+<indexterm><primary>password uniqueness</primary></indexterm>
+<indexterm><primary>password history</primary></indexterm>
+When network administrators  are asked to describe the benefits of Windows NT4 and active directory networking
+the most often mentioned feature is that of single sign-on (SSO). Many companies have implemented SSO
+solutions. The mode of implementation of a single sign-on solution is an important factor in the practice of
+networking in general, and is critical in respect of Windows networking. A company may have a wide variety of
+information systems, each of which requires a form of user authentication and validation, thus it is not
+uncommon that users may need to remember more than ten login IDs and passwords. This problem is compounded
+when the password for each system must be changed at regular intervals, and particularly so where password
+uniqueness and history limits are applied.
+</para>
+
+<para>
+<indexterm><primary>management overheads</primary></indexterm>
+There is a broadly held perception that SSO is the answer to the problem of users having to deal with too many
+information system access credentials (username/password pairs). Many elaborate schemes have been devised to
+make it possible to deliver a user-friendly SSO solution. The trouble is that if this implementation is not
+done correctly, the site may end up paying dearly by way of complexity and management overheads. Simply put,
+many SSO solutions are an administrative nightmare.
+</para>
+
+<para>
+<indexterm><primary>identity management</primary></indexterm>
+<indexterm><primary>authentication system</primary></indexterm>
+<indexterm><primary>SSO</primary></indexterm>
+SSO implementations utilize centralization of all user account information. Depending on environmental
+complexity and the age of the systems over which a SSO solution is implemented, it may not be possible to
+change the solution architecture so as to accomodate a new identity management and user authentication system.
+Many SSO solutions involving legacy systems consist of a new super-structure that handles authentication on
+behalf of the user. The software that gets layered over the old system may simply implement a proxy
+authentication system. This means that the addition of SSO increases over-all information systems complexity.
+Ideally, the implementation of SSO should reduce complexity and reduce administative overheads.
+</para>
+
+<para>
+<indexterm><primary>centralized identity management</primary></indexterm>
+<indexterm><primary>identity management</primary><secondary>centralized</secondary></indexterm>
+<indexterm><primary>centralized</primary><secondary>authentication</secondary></indexterm>
+<indexterm><primary>legacy systems</primary></indexterm>
+<indexterm><primary>access control</primary></indexterm>
+The initial goal of many network administrators is often to create and use a centralized identity management
+system. It is often assumed that such a centralized system will use a single authentication infrastructure
+that can be used by all information systems. The Microsoft Windows NT4 security domain architecture and the
+Micrsoft active directory service are often put forward as the ideal foundation for such a system. It is
+conceptually simple to install an external authentication agent on each of the disparate infromation systems
+that can then use the Microsoft (NT4 domain or ads service) for user authentication and access control. The
+wonderful dream of a single centralized authentication service is commonly broken when realities are realized.
+The problem with legacy systems is often the inability to externalize the authentication and access control
+system it uses because its implementation will be excessively invasive from a re-engineering perspective, or
+because application software has built-in dependencies on particular elements of the way user authentication
+and access control were designed and built.
+</para>
+
+<para>
+<indexterm><primary>meta-directory</primary></indexterm>
+<indexterm><primary>credentials</primary></indexterm>
+<indexterm><primary>disparate information systems</primary></indexterm>
+<indexterm><primary>management procedures</primary></indexterm>
+<indexterm><primary>work-flow protocol</primary></indexterm>
+<indexterm><primary>rights</primary></indexterm>
+<indexterm><primary>privileges</primary></indexterm>
+<indexterm><primary>provisioned</primary></indexterm>
+Over the past decade an industry has been developed around the various methods that have been built to get
+around the key limitations of legacy information technology systems. One approach that is often used involves
+the use of a meta-directory. The meta-directory stores user credentials for all disparate information systems
+in the format that is particular to each system. An elaborate set of management procedures is coupled with a
+rigidly enforced work-flow protocol for managing user rights and privileges within the maze of systems that
+are provisioned by the new infrastructure makes possible user access to all systems using a single set of user
+credentials.
+</para>
+
+<para>
+<indexterm><primary>Organization for the Advancement of Structured Information Standards</primary><see>OASIS</see></indexterm>
+<indexterm><primary>Security Assertion Markup Language</primary><see>SAML</see></indexterm>
+<indexterm><primary>Federated Identity Management</primary><see>FIM</see></indexterm>
+<indexterm><primary>secure access</primary></indexterm>
+The Organization for the Advancement of Structured Information Standards (OASIS) has developed the Security
+Assertion Markup Language (SAML), a structured method for communication of authentication information. The
+over-all umbrella name for the technologies and methods that deploy SAML is called Federated Identity
+Management (FIM). FIM depends on each system in the complex maze of disparate information systems to
+authenticate their respective users and vouch for secure access to the services each provides.
+</para>
+
+<para>
+<indexterm><primary>Simple Object Access Protocol</primary><see>SOAP</see></indexterm>
+<indexterm><primary>federated organizations</primary></indexterm>
+<indexterm><primary>Liberty Alliance</primary></indexterm>
+<indexterm><primary>federated-identity</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+<indexterm><primary></primary></indexterm>
+SAML documents can be wrapped in a Simple Object Access Protocol (SOAP) message for the computer-to-computer
+communications needed for Web services. Or they may be passed between Web servers of federated organizations
+that share live services. The Liberty Alliance, an industry group formed to promote federated-identity
+standards, has adopted SAML 1.1 as part of its application framework. Microsoft and IBM have proposed an
+alternative specification called WS-Security. Some believe that the competing technologies and methods may
+converge when the SAML 2.0 standard is introduced. A few Web access-management products support SAML today,
+but implemention of the technology mostly requires customization to integrate applications and develop user
+interfaces. In a nust-shell, that is why FIM is a big and growing industry.
+</para>
+
+<para>
+<indexterm><primary>interoperability</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>GSSAPI</primary></indexterm>
+<indexterm><primary>general security service application programming interface</primary><see>GSSAPI</see></indexterm>
+Ignoring the bigger picture, which is beyond the scope of this book, the migration of all user and group
+management to a centralized system is a step in the right direction. It is essential for interoperability
+reasons to locate the identity management system data in a directory such as Microsoft Active Directory
+Service (ADS), or any proprietary or open source system that provides a standard protocol for information
+access (such as LDAP) and that can be coupled with a flexible array of authentication mechanisms (such as
+kerberos) that use the protocols that are defined by the various general security service application
+programming interface (GSSAPI) services.
+</para>
+
+<para>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>authentication agents</primary></indexterm>
+A growing number of companies provide authentication agents for disparate legacy platforms to permit the use
+of LDAP systems. Thus the use of OpenLDAP, the dominant open source software implementation of the light
+weight directory access protocol standard. This fact, means that by providing support in Samba for the use of
+LDAP and Microsoft ADS make Samba a highly scalable and forward reaching organizational networking technology.
+</para>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>authentication architecture</primary></indexterm>
+<indexterm><primary>ntlm_auth</primary></indexterm>
+<indexterm><primary>SQUID</primary></indexterm>
+<indexterm><primary>FIM</primary></indexterm>
+Microsoft ADS provides purely proprietary services that, with limitation, can be extended to provide a
+centralized authentication infrastructure. Samba plus LDAP provides a similar opportunity for extension of a
+centralized authentication architecture, but it is the fact that the Samba Team are pro-active in introducing
+the extension of authentication services, using LDAP or otherwise, to applications such as SQUID (the open
+source proxy server) through tools such as the <command>ntlm_auth</command> utility, that does much to create
+sustainable choice and competition in the FIM market place.
+</para>
+
+<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>identity information</primary></indexterm>
+Primary domain control, if it is to be scalable to meet the needs of large sites, must therefore be capable of
+using LDAP. The rapid adoption of OpenLDAP, and Samba configurations that use it, is ample proof that the era
+of the directory has started. Samba-3 does not demand the use of LDAP, but the demand for a mechanism by which
+user and group identity information can be distributed makes it an an unavoidable option.
+</para>
+
+<para>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>e-Directory</primary></indexterm>
+At this time, the use of Samba based BDCs, necessitates the use of LDAP. The most commonly used LDAP
+implementation used by Samba sites is OpenLDAP. It is possible to use any standards compliant LDAP server.
+Those known to work includes those manufactured by: IBM, CA, Novell (e-Directory), and others.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Basics of Domain Control</title>
+
+<para>
+<indexterm><primary>domain control</primary></indexterm>
+Over the years, public perceptions of what domain control really is has taken on an almost mystical nature.
+Before we branch into a brief overview of domain control, there are three basic types of domain controllers.
+</para>
+
+<sect2>
+<title>Domain Controller Types</title>
+
+<itemizedlist>
+	<listitem><para>NT4 style Primary Domain Controller</para></listitem>
+	<listitem><para>NT4 style Backup Domain Controller</para></listitem>
+	<listitem><para>ADS Domain Controller</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>powerful</primary></indexterm>
+<indexterm><primary>network</primary><secondary>performance</secondary></indexterm>
+<indexterm><primary>domain</primary><secondary>member</secondary><secondary>server</secondary></indexterm>
+The <emphasis>Primary Domain Controller</emphasis> or PDC plays an important role in MS Windows NT4. In
+Windows 200x domain control architecture, this role is held by domain controllers.  Folklore dictates that
+because of its role in the MS Windows network, the domain controller should be the most powerful and most
+capable machine in the network.  As strange as it may seem to say this here, good overall network performance
+dictates that the entire infrastructure needs to be balanced. It is advisable to invest more in standalone
+(domain member) servers than in the domain controllers.
+</para>
+
+<para>
+<indexterm><primary>SAM</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>authenticatior</primary></indexterm>
+<indexterm><primary>synchronization</primary></indexterm>
+<indexterm><primary>Security Account Manager</primary><see>SAM</see></indexterm>
+In the case of MS Windows NT4-style domains, it is the PDC that initiates a new domain control database.
+This forms a part of the Windows registry called the Security Account Manager (SAM). It plays a key
+part in NT4-type domain user authentication and in synchronization of the domain authentication
+database with BDCs. 
+</para>
+
+<para>
+<indexterm><primary>domain</primary><secondary>controller</secondary><tertiary>hierarchy</tertiary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm>account<primary></primary><secondary>backend</secondary></indexterm>
+<indexterm><primary>machine account</primary></indexterm>
+With MS Windows 200x Server-based Active Directory domains, one domain controller initiates a potential
+hierarchy of domain controllers, each with its own area of delegated control. The master domain
+controller has the ability to override any downstream controller, but a downline controller has
+control only over its downline. With Samba-3, this functionality can be implemented using an
+LDAP-based user and machine account backend.
+</para>
+
+<para>
+<indexterm><primary>backend database</primary></indexterm>
+<indexterm><primary>registry</primary></indexterm>
+New to Samba-3 is the ability to use a backend database that holds the same type of data as the NT4-style SAM
+database (one of the registry files)<footnote><para>See also <link linkend="passdb">Account Information
+Databases</link>.</para>.</footnote>
+</para>
+
+<para>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+<indexterm><primary>netlogon</primary></indexterm>
+<indexterm><primary>name lookup</primary></indexterm>
+The <emphasis>Backup Domain Controller</emphasis> or BDC plays a key role in servicing network authentication
+requests. The BDC is biased to answer logon requests in preference to the PDC.  On a network segment that has
+a BDC and a PDC, the BDC will most likely service network logon requests. The PDC will answer network logon
+requests when the BDC is too busy (high load). When a user logs onto a Windows domain member client the
+workstation will query the network to locate the nearest network logon server. Where a WINS server is used,
+this is done via a query to the WINS server. If a netlogon server can not be found from the WINS query, or in
+the absence of a WINS server, the workstation will perform a NetBIOS name lookup via a mailslot broadcast over
+the UDP broadcast protocol. This means that the netlogon server that the windows client will use is influenced
+by a number of variables, thus there is no simple determinant of whether a PDC or a BDC will serve a
+particular logon authentication request.
+</para>
+
+<para>
+<indexterm><primary>promote</primary></indexterm>
+<indexterm><primary>demote</primary></indexterm>
+A Windows NT4 BDC can be promoted to a PDC. If the PDC is online at the time that a BDC is promoted to PDC,
+the previous PDC is automatically demoted to a BDC. With Samba-3, this is not an automatic operation; the PDC
+and BDC must be manually configured, and other appropriate changes also need to be made.
+</para>
+
+<para>
+<indexterm><primary>domain</primary><secondary>controller</secondary><tertiary>convert</tertiary></indexterm>
+With MS Windows NT4, a decision is made at installation to determine what type of machine the server will be.
+It is possible to promote a BDC to a PDC, and vice versa. The only method Microsoft provide to convert a
+Windows NT4 domain controller to a domain member server or a standalone server is to reinstall it. The install
+time choices offered are:
+</para>
+
+<itemizedlist>
+	<listitem><para><emphasis>Primary Domain Controller</emphasis> &smbmdash; the one that seeds the domain SAM.</para></listitem>
+	<listitem><para><emphasis>Backup Domain Controller</emphasis> &smbmdash; one that obtains a copy of the domain SAM.</para></listitem>
+	<listitem><para><emphasis>Domain Member Server</emphasis> &smbmdash; one that has no copy of the domain SAM; rather
+		it obtains authentication from a domain controller for all access controls.</para></listitem>
+	<listitem><para><emphasis>Standalone Server</emphasis> &smbmdash; one that plays no part in SAM synchronization,
+		has its own authentication database, and plays no role in domain security.</para></listitem>
+</itemizedlist>
+
+<note><para>
+<indexterm><primary>promote</primary></indexterm>
+Algin Technology LLC provide a commercial tool that makes it possible to promote a Windows NT4 standalone
+server to a PDC or a BDC, and also permits this process to be reversed. Refer to the <ulink
+url="http://utools.com/UPromote.asp">Algin</ulink> web site for further information.
+</para></note>
+
+<para>
+<indexterm><primary>domain</primary><secondary>control</secondary><tertiary>role</tertiary></indexterm>
+<indexterm><primary>native member</primary></indexterm>
+Samba-3 servers can readily be converted to and from domain controller roles through simple changes to the
+&smb.conf; file. Samba-3 is capable of acting fully as a native member of a Windows 200x server Active
+Directory domain.
+</para>
+
+<para>
+<indexterm><primary>convert</primary><secondary>domain member server</secondary></indexterm>
+For the sake of providing a complete picture, MS Windows 2000 domain control configuration is done after the server has been
+installed. Please refer to Microsoft documentation for the procedures that should be followed to convert a
+domain member server to or from a domain control, and to install or remove active directory service support.
+</para>
+
+<para>
+<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
+<indexterm><primary>SAM</primary><secondary>replication</secondary></indexterm>
+New to Samba-3 is the ability to function fully as an MS Windows NT4-style domain controller,
+excluding the SAM replication components. However, please be aware that Samba-3 also supports the
+MS Windows 200x domain control protocols.
+</para>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+At this time any appearance that Samba-3 is capable of acting as a <emphasis>domain controller</emphasis> in
+native ADS mode is limited and experimental in nature.  This functionality should not be used until the Samba
+Team offers formal support for it.  At such a time, the documentation will be revised to duly reflect all
+configuration and management requirements. Samba can act as a NT4-style domain controller in a Windows 2000/XP
+environment. However, there are certain compromises:
+</para>
+
+<itemizedlist>
+	<listitem><para>No machine policy files.</para></listitem>
+	<listitem><para>No Group Policy Objects.</para></listitem>
+	<listitem><para>No synchronously executed Active Directory logon scripts.</para></listitem>
+	<listitem><para>Can't use Active Directory management tools to manage users and machines.</para></listitem>
+	<listitem><para>Registry changes tattoo the main registry, while with Active Directory they do not leave
+		permanent changes in effect.</para></listitem>
+	<listitem><para>Without Active Directory you cannot perform the function of exporting specific
+		applications to specific users or groups.</para></listitem>
+</itemizedlist>
+
+</sect2>
+
+<sect2>
+<title>Preparing for Domain Control</title>
+
+<para>
+<indexterm><primary>standalone</primary></indexterm>
+<indexterm><primary>workgroup</primary></indexterm>
+<indexterm><primary>member</primary></indexterm>
+<indexterm><primary>security</primary></indexterm>
+There are two ways that MS Windows machines may interact with each other, with other servers,
+and with domain controllers: either as <emphasis>standalone</emphasis> systems, more commonly
+called <emphasis>workgroup</emphasis> members, or as full participants in a security system,
+more commonly called <emphasis>domain</emphasis> members.
+</para>
+
+<para>
+<indexterm><primary>workgroup</primary></indexterm>
+<indexterm><primary>workgroup</primary><secondary>membership</secondary></indexterm>
+<indexterm><primary>machine trust account</primary></indexterm>
+It should be noted that workgroup membership involves no special configuration other than the machine being
+configured so the network configuration has a commonly used name for its workgroup entry. It is not uncommon
+for the name WORKGROUP to be used for this. With this mode of configuration, there are no Machine Trust
+Accounts, and any concept of membership as such is limited to the fact that all machines appear in the network
+neighborhood to be logically grouped together. Again, just to be clear: <emphasis>workgroup mode does not
+involve security machine accounts</emphasis>.
+</para>
+
+<para>
+<indexterm><primary>domain membership</primary></indexterm>
+<indexterm><primary>machine trust account</primary><secondary>password</secondary></indexterm>
+<indexterm><primary>trigger</primary></indexterm>
+Domain member machines have a machine trust account in the domain accounts database. A special procedure
+must be followed on each machine to effect domain membership. This procedure, which can be done
+only by the local machine Administrator account, creates the domain machine account (if it does
+not exist), and then initializes that account. When the client first logs onto the
+domain, a machine trust account password change will be automatically triggered.
+</para>
+
+<note><para>
+<indexterm><primary>domain member</primary></indexterm>
+When Samba is configured as a domain controller, secure network operation demands that
+all MS Windows NT4/200x/XP Professional clients should be configured as domain members.
+If a machine is not made a member of the domain, then it will operate like a workgroup
+(standalone) machine. Please refer to <link linkend="domain-member">Domain Membership</link>, for
+information regarding domain membership.
+</para></note>
+
+<para>
+The following are necessary for configuring Samba-3 as an MS Windows NT4-style PDC for MS Windows
+NT4/200x/XP clients:
+</para>
+
+<itemizedlist>
+	<listitem><para>Configuration of basic TCP/IP and MS Windows networking.</para></listitem>
+	<listitem><para>Correct designation of the server role (<smbconfoption name="security">user</smbconfoption>).</para></listitem>
+	<listitem><para>Consistent configuration of name resolution.<footnote><para>See <link linkend="NetworkBrowsing">Network Browsing</link>, and 
+		<link linkend="integrate-ms-networks">Integrating MS Windows Networks with Samba</link>.</para></footnote></para></listitem>
+	<listitem><para>Domain logons for Windows NT4/200x/XP Professional clients.</para></listitem>
+	<listitem><para>Configuration of roaming profiles or explicit configuration to force local profile usage.</para></listitem>
+	<listitem><para>Configuration of network/system policies.</para></listitem>
+	<listitem><para>Adding and managing domain user accounts.</para></listitem>
+	<listitem><para>Configuring MS Windows NT4/2000 Professional and Windows XP Professional client machines to become domain members.</para></listitem>
+</itemizedlist>
+
+<para>
+The following provisions are required to serve MS Windows 9x/Me clients:
+</para>
+
+<itemizedlist>
+	<listitem><para>Configuration of basic TCP/IP and MS Windows networking.</para></listitem>
+	<listitem><para>Correct designation of the server role (<smbconfoption name="security">user</smbconfoption>).</para></listitem>
+	<listitem><para>Network logon configuration (since Windows 9x/Me/XP Home are not technically domain
+	members, they do not really participate in  the security aspects of Domain logons as such).</para></listitem>
+	<listitem><para>Roaming profile configuration.</para></listitem>
+	<listitem><para>Configuration of system policy handling.</para></listitem>
+	<listitem><para>Installation of the network driver <quote>Client for MS Windows Networks</quote> and configuration
+	to log onto the domain.</para></listitem>
+	<listitem><para>Placing Windows 9x/Me clients in user-level security &smbmdash; if it is desired to allow
+	all client-share access to be controlled according to domain user/group identities.</para></listitem>
+	<listitem><para>Adding and managing domain user accounts.</para></listitem>
+</itemizedlist>
+
+<note><para>
+<indexterm><primary>roaming profiles</primary></indexterm>
+<indexterm><primary>account policies</primary></indexterm>
+Roaming profiles and system/network policies are advanced network administration topics
+that are covered in <link linkend="ProfileMgmt">Desktop Profile Management</link> and
+<link linkend="PolicyMgmt">System and Account Policies</link> of this document. However, these are not
+necessarily specific to a Samba PDC as much as they are related to Windows NT networking concepts.
+</para></note>
+
+<para>
+A domain controller is an SMB/CIFS server that:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<indexterm><primary>NetBIOS</primary><secondary>brooadcast</secondary></indexterm>
+	<indexterm><primary>WINS</primary></indexterm>
+	<indexterm><primary>UDP</primary></indexterm>
+	<indexterm><primary>DNS</primary></indexterm>
+	<indexterm><primary>active directory</primary></indexterm>
+	Registers and advertises itself as a domain controller (through NetBIOS broadcasts
+	as well as by way of name registrations either by Mailslot Broadcasts over UDP broadcast,
+	to a WINS server over UDP unicast, or via DNS and Active Directory).
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>NETLOGON</primary></indexterm>
+	<indexterm><primary>LanMan logon service</primary></indexterm>
+	Provides the NETLOGON service. (This is actually a collection of services that runs over
+	multiple protocols. These include the LanMan logon service, the Netlogon service,
+	the Local Security Account service, and variations of them.)
+	</para></listitem>
+
+	<listitem><para>
+	Provides a share called NETLOGON.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>domain</primary><secondary>master</secondary><tertiary>browser</tertiary></indexterm>
+<indexterm><primary>local</primary><secondary>master</secondary><tertiary>browser</tertiary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>LMB</primary></indexterm>
+<indexterm><primary>browse list</primary></indexterm>
+It is rather easy to configure Samba to provide these. Each Samba domain controller must provide the NETLOGON
+service that Samba calls the <smbconfoption name="domain logons"/> functionality (after the name of the
+parameter in the &smb.conf; file). Additionally, one server in a Samba-3 domain must advertise itself as the
+domain master browser.<footnote><para>See <link linkend="NetworkBrowsing">Network
+Browsing</link>.</para></footnote> This causes the PDC to claim a domain-specific NetBIOS name that identifies
+it as a DMB for its given domain or workgroup. Local master browsers (LMBs) in the same domain or workgroup on
+broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide-area network.
+Browser clients then contact their LMB, and will receive the domain-wide browse list instead of just the list
+for their broadcast-isolated subnet.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Domain Control: Example Configuration</title>
+
+<para>
+The first step in creating a working Samba PDC is to understand the parameters necessary
+in &smb.conf;. An example &smb.conf; for acting as a PDC can be found in <link linkend="pdc-example">the
+smb.conf file for an example PDC</link>. 
+</para>
+
+<example id="pdc-example">
+<title>smb.conf for being a PDC</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="netbios name"><replaceable>BELERIAND</replaceable></smbconfoption>
+<smbconfoption name="workgroup"><replaceable>&example.workgroup;</replaceable></smbconfoption>
+<smbconfoption name="passdb backend">tdbsam</smbconfoption>
+<smbconfoption name="os level">33</smbconfoption>
+<smbconfoption name="preferred master">auto</smbconfoption>
+<smbconfoption name="domain master">yes</smbconfoption>
+<smbconfoption name="local master">yes</smbconfoption>
+<smbconfoption name="security">user</smbconfoption>
+<smbconfoption name="domain logons">yes</smbconfoption>
+<smbconfoption name="logon path">\\%N\profiles\%U</smbconfoption>
+<smbconfoption name="logon drive">H:</smbconfoption>
+<smbconfoption name="logon home">\\homeserver\%U\winprofile</smbconfoption>
+<smbconfoption name="logon script">logon.cmd</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+<smbconfoption name="read only">yes</smbconfoption>
+<smbconfoption name="write list"><replaceable>ntadmin</replaceable></smbconfoption>
+
+<smbconfsection name="[profiles]"/>
+<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
+<smbconfoption name="read only">no</smbconfoption>
+<smbconfoption name="create mask">0600</smbconfoption>
+<smbconfoption name="directory mask">0700</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+The basic options shown in <link linkend="pdc-example">this example</link> are explained as follows:
+</para>
+
+<variablelist>
+	<varlistentry><term>passdb backend </term>
+		<listitem><para>
+		<indexterm><primary>group</primary><secondary>account</secondary></indexterm>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		<indexterm><primary>tdbsam</primary></indexterm>
+		<indexterm><primary>ldapsam</primary></indexterm>
+		<indexterm><primary>guest</primary></indexterm>
+		<indexterm><primary>default accounts</primary></indexterm>
+		This contains all the user and group account information. Acceptable values for a PDC
+		are: <emphasis>smbpasswd, tdbsam, and ldapsam</emphasis>. The <quote>guest</quote> entry provides
+		default accounts and is included by default; there is no need to add it explicitly.
+		</para>
+
+		<para>
+		<indexterm><primary>passdb backend</primary></indexterm>
+		<indexterm><primary>distributed</primary></indexterm>
+		<indexterm><primary>smbpasswd</primary></indexterm>
+		<indexterm><primary>tdbsam</primary></indexterm>
+		Where use of BDCs is intended, the only logical choice is
+		to use LDAP so the passdb backend can be distributed. The tdbsam and smbpasswd files
+		cannot effectively be distributed and therefore should not be used.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>Domain Control Parameters </term>
+		<listitem><para>
+		<indexterm><primary>os level</primary></indexterm>
+		<indexterm><primary>preferred master</primary></indexterm>
+		<indexterm><primary>domain master</primary></indexterm>
+		<indexterm><primary>network</primary><secondary>logon</secondary></indexterm>
+		The parameters <emphasis>os level, preferred master, domain master, security, 
+		encrypt passwords</emphasis>, and <emphasis>domain logons</emphasis> play a central role in assuring domain
+		control and network logon support.
+		</para>
+
+		<para>
+		<indexterm><primary>DMB</primary></indexterm>
+		<indexterm><primary>encryped password</primary></indexterm>
+		The <emphasis>os level</emphasis> must be set at or above a value of 32. A domain controller
+		must be the DMB, must be set in <emphasis>user</emphasis> mode security,
+		must support Microsoft-compatible encrypted passwords, and must provide the network logon
+		service (domain logons). Encrypted passwords must be enabled. For more details on how 
+		to do this, refer to <link linkend="passdb">Account Information Databases</link>.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>Environment Parameters </term>
+		<listitem><para>
+		<indexterm><primary>logon path</primary></indexterm>
+		<indexterm><primary>logon home</primary></indexterm>
+		<indexterm><primary>logon drive</primary></indexterm>
+		<indexterm><primary>logon script</primary></indexterm>
+		The parameters <emphasis>logon path, logon home, logon drive</emphasis>, and <emphasis>logon script</emphasis> are
+		environment support settings that help to facilitate client logon operations and that help
+		to provide automated control facilities to ease network management overheads. Please refer
+		to the man page information for these parameters.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>NETLOGON Share </term>
+		<listitem><para>
+		<indexterm><primary>NETLOGON</primary></indexterm>
+		<indexterm><primary>logon processing</primary></indexterm>
+		<indexterm><primary>domain logon</primary></indexterm>
+		<indexterm><primary>domain membership</primary></indexterm>
+		<indexterm><primary>group policy</primary></indexterm>
+		<indexterm><primary>NTConfig.POL</primary></indexterm>
+		The NETLOGON share plays a central role in domain logon and domain membership support.
+		This share is provided on all Microsoft domain controllers. It is used to provide logon
+		scripts, to store group policy files (NTConfig.POL), as well as to locate other common
+		tools that may be needed for logon processing. This is an essential share on a domain controller.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>PROFILE Share </term>
+		<listitem><para>
+		<indexterm><primary>desktop profile</primary></indexterm>
+		<indexterm><primary>VFS</primary></indexterm>
+		<indexterm><primary>fake_permissions</primary></indexterm>
+		<indexterm><primary>profile</primary></indexterm>
+		<indexterm><primary></primary></indexterm>
+		This share is used to store user desktop profiles. Each user must have a directory at the root
+		of this share. This directory must be write-enabled for the user and must be globally read-enabled.
+		Samba-3 has a VFS module called <quote>fake_permissions</quote> that may be installed on this share. This will
+		allow a Samba administrator to make the directory read-only to everyone. Of course this is useful
+		only after the profile has been properly created.
+		</para></listitem>
+	</varlistentry>
+</variablelist>
+
+<note><para>
+The above parameters make for a full set of functionality that may define the server's mode
+of operation. The following &smb.conf; parameters are the essentials alone:
+</para>
+
+<para>
+<smbconfblock>
+<smbconfoption name="netbios name">BELERIAND</smbconfoption>
+<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="domain master">Yes</smbconfoption>
+<smbconfoption name="security">User</smbconfoption>
+</smbconfblock>
+</para>
+
+<para>
+The additional parameters shown in the longer listing in this section just make for
+a more complete explanation.
+</para></note>
+
+</sect1>
+
+<sect1>
+<title>Samba ADS Domain Control</title>
+
+<para>
+<indexterm><primary>active directory</primary></indexterm>
+Samba-3 is not, and cannot act as, an Active Directory server. It cannot truly function as an Active Directory
+PDC. The protocols for some of the functionality of Active Directory domain controllers has been partially
+implemented on an experimental only basis. Please do not expect Samba-3 to support these protocols. Do not
+depend on any such functionality either now or in the future. The Samba Team may remove these experimental
+features or may change their behavior. This is mentioned for the benefit of those who have discovered secret
+capabilities in Samba-3 and who have asked when this functionality will be completed. The answer is maybe
+someday or maybe never!
+</para>
+
+<para>
+<indexterm><primary>domain controllers</primary></indexterm>
+<indexterm><primary>active directory</primary></indexterm>
+To be sure, Samba-3 is designed to provide most of the functionality that Microsoft Windows NT4-style
+domain controllers have. Samba-3 does not have all the capabilities of Windows NT4, but it does have
+a number of features that Windows NT4 domain controllers do not have. In short, Samba-3 is not NT4 and it
+is not Windows Server 200x: it is not an Active Directory server. We hope this is plain and simple
+enough for all to understand.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Domain and Network Logon Configuration</title>
+
+<para>
+<indexterm><primary>domain logon</primary></indexterm>
+The subject of network or domain logons is discussed here because it forms
+an integral part of the essential functionality that is provided by a domain controller.
+</para>
+
+<sect2>
+<title>Domain Network Logon Service</title>
+
+<para>
+<indexterm><primary>domain logon</primary></indexterm>
+All domain controllers must run the netlogon service (<emphasis>domain logons</emphasis>
+in Samba). One domain controller must be configured with <smbconfoption name="domain master">Yes</smbconfoption>
+(the PDC); on all BDCs set the parameter <smbconfoption name="domain master">No</smbconfoption>.
+</para>
+
+<sect3>
+<title>Example Configuration</title>
+
+<example id="PDC-config">
+<title>smb.conf for being a PDC</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+<smbconfoption name="domain master">(Yes on PDC, No on BDCs)</smbconfoption>
+
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">Network Logon Service</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+</sect3>
+<sect3>
+<title>The Special Case of MS Windows XP Home Edition</title>
+
+<para>
+<indexterm><primary>Windows XP Home edition</primary></indexterm>
+To be completely clear: If you want MS Windows XP Home Edition to integrate with your
+MS Windows NT4 or Active Directory domain security, understand it cannot be done.
+The only option is to purchase the upgrade from MS Windows XP Home Edition to
+MS Windows XP Professional.
+</para>
+
+<note><para>
+MS Windows XP Home Edition does not have the ability to join any type of domain
+security facility. Unlike MS Windows 9x/Me, MS Windows XP Home Edition also completely
+lacks the ability to log onto a network.
+</para></note>
+
+<para>
+Now that this has been said, please do not ask the mailing list or email any of the
+Samba Team members with your questions asking how to make this work. It can't be done.
+If it can be done, then to do so would violate your software license agreement with
+Microsoft, and we recommend that you do not do that.
+</para>
+
+</sect3>
+
+<sect3>
+<title>The Special Case of Windows 9x/Me</title>
+
+<para>
+<indexterm><primary>domain</primary></indexterm>
+<indexterm><primary>workgroup</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+<indexterm><primary>browsing</primary></indexterm>
+<indexterm><primary>rights</primary></indexterm>
+A domain and a workgroup are exactly the same in terms of network
+browsing. The difference is that a distributable authentication
+database is associated with a domain, for secure login access to a
+network. Also, different access rights can be granted to users if they
+successfully authenticate against a domain logon server. Samba-3 does this
+now in the same way as MS Windows NT/200x.
+</para>
+
+<para>
+<indexterm><primary>browsing</primary></indexterm>
+The SMB client logging on to a domain has an expectation that every other
+server in the domain should accept the same authentication information.
+Network browsing functionality of domains and workgroups is identical and
+is explained in this documentation under the browsing discussions.
+It should be noted that browsing is totally orthogonal to logon support.
+</para>
+
+<para>
+<indexterm><primary>single-logon</primary></indexterm>
+<indexterm><primary>domain logons</primary></indexterm>
+<indexterm><primary>network logon</primary></indexterm>
+Issues related to the single-logon network model are discussed in this
+section. Samba supports domain logons, network logon scripts, and user
+profiles for MS Windows for Workgroups and MS Windows 9x/Me clients,
+which are the focus of this section.
+</para>
+
+<para>
+<indexterm><primary>broadcast request</primary></indexterm>
+When an SMB client in a domain wishes to log on, it broadcasts requests for a logon server. The first one to
+reply gets the job and validates its password using whatever mechanism the Samba administrator has installed.
+It is possible (but ill advised) to create a domain where the user database is not shared between servers;
+that is, they are effectively workgroup servers advertising themselves as participating in a domain. This
+demonstrates how authentication is quite different from but closely involved with domains.
+</para>
+
+<para>
+Using these features, you can make your clients verify their logon via
+the Samba server, make clients run a batch file when they log on to
+the network and download their preferences, desktop, and start menu.
+</para>
+
+<para><emphasis>
+MS Windows XP Home edition is not able to join a domain and does not permit the use of domain logons.
+</emphasis></para>
+
+<para>
+Before launching into the configuration instructions, it is worthwhile to look at how a Windows 9x/Me client
+performs a logon:
+</para>
+
+<orderedlist>
+<listitem>
+	<para>
+	<indexterm><primary>DOMAIN&lt;1C&gt;</primary></indexterm>
+	<indexterm><primary>logon server</primary></indexterm>
+	The client broadcasts (to the IP broadcast address of the subnet it is in)
+	a NetLogon request. This is sent to the NetBIOS name DOMAIN&lt;1C&gt; at the
+	NetBIOS layer. The client chooses the first response it receives, which
+	contains the NetBIOS name of the logon server to use in the format of 
+	<filename>\\SERVER</filename>. The <literal>1C</literal> name is the name
+	type that is registered by domain controllers (SMB/CIFS servers that provide
+	the netlogon service).
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	<indexterm><primary>IPC$</primary></indexterm>
+	<indexterm><primary>SMBsessetupX</primary></indexterm>
+	<indexterm><primary>SMBtconX</primary></indexterm>
+	The client connects to that server, logs on (does an SMBsessetupX) and
+	then connects to the IPC$ share (using an SMBtconX).
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	<indexterm><primary>NetWkstaUserLogon</primary></indexterm>
+	The client does a NetWkstaUserLogon request, which retrieves the name
+	of the user's logon script. 
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	The client then connects to the NetLogon share and searches for said script.	
+	If it is found and can be read, it is retrieved and executed by the client.
+	After this, the client disconnects from the NetLogon share.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	<indexterm><primary>NetUserGetInfo</primary></indexterm>
+	<indexterm><primary>profile</primary></indexterm>
+	The client sends a NetUserGetInfo request to the server to retrieve
+	the user's home share, which is used to search for profiles. Since the
+	response to the NetUserGetInfo request does not contain much more than	
+	the user's home share, profiles for Windows 9x clients must reside in the user
+	home directory.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	<indexterm><primary>profiles</primary></indexterm>
+	The client connects to the user's home share and searches for the 
+	user's profile. As it turns out, you can specify the user's home share as
+	a share name and path. For example, <filename>\\server\fred\.winprofile</filename>.
+	If the profiles are found, they are implemented.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	<indexterm><primary>CONFIG.POL</primary></indexterm>
+	The client then disconnects from the user's home share and reconnects to
+	the NetLogon share and looks for <filename>CONFIG.POL</filename>, the policies file. If this is
+	found, it is read and implemented.
+	</para>
+</listitem>
+</orderedlist>
+
+<para>
+The main difference between a PDC and a Windows 9x/Me logon server configuration is:
+</para>
+
+<itemizedlist>
+<listitem><para>
+	<indexterm><primary>password</primary><secondary>plaintext</secondary></indexterm>
+	<indexterm><primary>plaintext password</primary></indexterm>
+	Password encryption is not required for a Windows 9x/Me logon server. But note
+	that beginning with MS Windows 98 the default setting is that plaintext
+	password support is disabled. It can be re-enabled with the registry
+	changes that are documented in <link linkend="PolicyMgmt">System and Account Policies</link>.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>machine trust account</primary></indexterm>
+	Windows 9x/Me clients do not require and do not use Machine Trust Accounts.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>network logon services</primary></indexterm>
+A Samba PDC will act as a Windows 9x/Me logon server; after all, it does provide the
+network logon services that MS Windows 9x/Me expect to find.
+</para>
+
+<note><para>
+<indexterm><primary>sniffer</primary></indexterm>
+Use of plaintext passwords is strongly discouraged. Where used they are easily detected
+using a sniffer tool to examine network traffic.
+</para></note>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>Security Mode and Master Browsers</title>
+
+<para>
+<indexterm><primary>security mode</primary></indexterm>
+<indexterm><primary>user-mode security</primary></indexterm>
+<indexterm><primary>share-mode security</primary></indexterm>
+There are a few comments to make in order to tie up some loose ends. There has been much debate over the issue
+of whether it is okay to configure Samba as a domain controller that operates with security mode other than
+user-mode. The only security mode that will not work due to technical reasons is share-mode security. Domain
+and server mode security are really just a variation on SMB user-level security.
+</para>
+
+<para>
+<indexterm><primary>DOMAIN&lt;1C&gt;</primary></indexterm>
+<indexterm><primary>DOMAIN&lt;1B&gt;</primary></indexterm>
+<indexterm><primary>DMB</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>NetBIOS name</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>election</primary></indexterm>
+Actually, this issue is also closely tied to the debate on whether Samba must be the DMB for its workgroup
+when operating as a domain controller.  In a pure Microsoft Windows NT domain, the PDC wins the election to be
+the DMB, and then registers the DOMAIN&lt;1B&gt; NetBIOS name. This is not the name used by Windows clients
+to locate the domain controller, all domain controllers register the DOMAIN&lt;1C&gt; name and Windows clients
+locate a network logon server by seraching for the DOMAIN&lt;1C&gt; name.  A DMB is a Domain Master Browser
+&smbmdash; see <link linkend="NetworkBrowsing">The Network Browsing Chapter</link>, <link
+linkend="DMB">Configuring WORKGROUP Browsing</link>; Microsoft PDCs expect to win the election to become the
+DMB, if it loses that election it will report a continuous and rapid sequence of warning messages to its
+Windows event logger complaining that it has lost the election to become a DMB.  For this reason, in networks
+where a Samba server is the PDC it is wise to configure the Samba domain controller as the DMB.
+</para>
+
+<note><para>
+<indexterm><primary>DOMAIN&lt;1D&gt;</primary></indexterm>
+<indexterm><primary>synchronization</primary></indexterm>
+<indexterm><primary>domain control</primary></indexterm>
+<indexterm><primary>browse list management</primary></indexterm>
+<indexterm><primary>network</primary><secondary>logon</secondary><tertiary>service</tertiary></indexterm>
+SMB/CIFS servers that register the DOMAIN&lt;1C&gt; name do so because they provide the network logon
+service. Server that register the DOMAIN&lt;1B&gt; name are DMBs &smbmdash; meaning that they are responsible
+for browse list synchronization across all machines that have registered the DOMAIN&lt;1D&gt; name. The later
+are LMBs that have the responsibility to listen to all NetBIOS name registrations that occur locally to their
+own network segment. The network logon service (NETLOGON) is germane to domain control and has nothing to do
+with network browsing and browse list management. The 1C and 1B/1D name services are orthogonal to each
+other.
+</para></note>
+
+<para>
+Now back to the issue of configuring a Samba domain controller to use a mode other than <smbconfoption
+name="security">user</smbconfoption>. If a Samba host is configured to use another SMB server or domain
+controller in order to validate user connection requests, it is a fact that some other machine on the network
+(the <smbconfoption name="password server"/>) knows more about the user than the Samba host. About 99 percent
+of the time, this other host is a domain controller. Now to operate in domain mode security, the
+<smbconfoption name="workgroup"/> parameter must be set to the name of the Windows NT domain (which already
+has a domain controller).  If the domain does not already have a domain controller, you do not yet have a
+domain.
+</para>
+
+<para>
+Configuring a Samba box as a domain controller for a domain that already by definition has a
+PDC is asking for trouble. Therefore, you should always configure the Samba domain controller
+to be the DMB for its domain and set <smbconfoption name="security">user</smbconfoption>.
+This is the only officially supported mode of operation.
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<sect2>
+<title><quote>$</quote> Cannot Be Included in Machine Name</title>
+
+<para>
+<indexterm><primary>BSD</primary></indexterm>
+<indexterm><primary>FreeBSD</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+A machine account, typically stored in <filename>/etc/passwd</filename>, takes the form of the machine
+name with a <quote>$</quote> appended. Some BSD systems will not create a user with a <quote>$</quote> in the name.
+Recent versions of FreeBSD have removed this limitation, but older releases are still in common use.
+</para>
+
+<para>
+<indexterm><primary>vipw</primary></indexterm>
+The problem is only in the program used to make the entry. Once made, it works perfectly.  Create a user
+without the <quote>$</quote>. Then use <command>vipw</command> to edit the entry, adding the <quote>$</quote>.
+Or create the whole entry with vipw if you like; make sure you use a unique user login ID.
+</para>
+
+<note><para>The machine account must have the exact name that the workstation has.</para></note>
+
+<note><para>
+The UNIX tool <command>vipw</command> is a common tool for directly editing the <filename>/etc/passwd</filename> file.
+The use of vipw will ensure that shadow files (where used) will remain current with the passwd file. This is
+important for security reasons.
+</para></note>
+
+</sect2>
+
+<sect2>
+<title>Joining Domain Fails Because of Existing Machine Account</title>
+		
+<para>
+<indexterm><primary>join domain</primary></indexterm>
+<quote>I get told, `You already have a connection to the Domain....' or `Cannot join domain, the
+credentials supplied conflict with an existing set...' when creating a Machine Trust Account.</quote>
+</para>
+
+<para>
+This happens if you try to create a Machine Trust Account from the machine itself and already have a
+connection (e.g., mapped drive) to a share (or IPC$) on the Samba PDC. The following command will remove all
+network drive connections:
+<screen>
+&dosprompt;<userinput>net use * /d</userinput>
+</screen>
+This will break all network connections.
+</para>
+
+<para>
+Further, if the machine is already a <quote>member of a workgroup</quote> that is the same name as the domain
+you are joining (bad idea), you will get this message. Change the workgroup name to something else &smbmdash;
+it does not matter what &smbmdash; reboot, and try again.
+</para>
+
+</sect2>
+
+<sect2>
+<title>The System Cannot Log You On (C000019B)</title>
+
+<para><quote>
+I joined the domain successfully but after upgrading to a newer version of the Samba code I get the message,
+<errorname>`The system cannot log you on (C000019B). Please try again or consult your system
+administrator</errorname> when attempting to logon.'</quote>
+</para>
+
+<para>
+<indexterm><primary>SID</primary></indexterm>
+This occurs when the domain SID stored in the secrets.tdb database is changed. The most common cause of a
+change in domain SID is when the domain name and/or the server name (NetBIOS name) is changed.  The only way
+to correct the problem is to restore the original domain SID or remove the domain client from the domain and
+rejoin. The domain SID may be reset using either the net or rpcclient utilities.
+</para>
+
+<para>
+To reset or change the domain SID you can use the net command as follows:
+
+<screen>
+&rootprompt;<userinput>net getlocalsid 'OLDNAME'</userinput>
+&rootprompt;<userinput>net setlocalsid 'SID'</userinput>
+</screen>
+</para>
+
+<para>
+Workstation Machine Trust Accounts work only with the domain (or network) SID. If this SID changes,
+domain members (workstations) will not be able to log onto the domain. The original domain SID
+can be recovered from the secrets.tdb file. The alternative is to visit each workstation to rejoin
+it to the domain.
+</para>
+
+</sect2>
+
+<sect2>
+<title>The Machine Trust Account Is Not Accessible</title>
+
+<para>
+<quote>When I try to join the domain I get the message, <errorname>"The machine account 
+for this computer either does not exist or is not accessible</errorname>." What's wrong?</quote>
+</para>
+
+<para>
+This problem is caused by the PDC not having a suitable Machine Trust Account.  If you are using the
+<smbconfoption name="add machine script"/> method to create accounts, then this would indicate that it has not
+worked. Ensure the domain admin user system is working.
+</para>
+
+<para>
+Alternately, if you are creating account entries manually, then they have not been created correctly. Make
+sure that you have the entry correct for the Machine Trust Account in <filename>smbpasswd</filename> file on
+the Samba PDC.  If you added the account using an editor rather than using the smbpasswd utility, make sure
+that the account name is the machine NetBIOS name with a <quote>$</quote> appended to it (i.e.,
+computer_name$). There must be an entry in both the POSIX UNIX system account backend as well as in the
+SambaSAMAccount backend. The default backend for Samba-3 (i.e., the parameter <parameter>passdb
+backend</parameter> is not specified in the &smb.conf; file, or if specified is set to
+<literal>smbpasswd</literal>, are respectively the <filename>/etc/passwd</filename> and
+<filename>/etc/samba/smbpasswd</filename> (or <filename>/usr/local/samba/lib/private/smbpasswd</filename> if
+compiled using Samba Team default settings). The use of the <filename>/etc/passwd</filename> can be overridden
+by alternative settings in the NSS <filename>/etc/nsswitch.conf</filename> file.
+</para>
+
+<para>
+Some people have also reported that inconsistent subnet masks between the Samba server and the NT 
+client can cause this problem.  Make sure that these are consistent for both client and server.
+</para>
+</sect2>
+
+<sect2>
+<title>Account Disabled</title>
+
+<para><quote>When I attempt to log in to a Samba domain from a NT4/W200x workstation,
+I get a message about my account being disabled.</quote></para>
+
+<para>
+Enable the user accounts with <userinput>smbpasswd -e <replaceable>username</replaceable>
+</userinput>. This is normally done as an account is created.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Domain Controller Unavailable</title>
+		
+<para><quote>Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'</quote></para>
+
+<para>
+A domain controller has to announce its role on the network. This usually takes a while. Be patient for up to 15 minutes,
+then try again.
+</para>
+</sect2>
+
+<sect2>
+<title>Cannot Log onto Domain Member Workstation After Joining Domain</title>
+
+<para>
+<indexterm><primary>schannel</primary></indexterm>
+<indexterm><primary>signing</primary></indexterm>
+After successfully joining the domain, user logons fail with one of two messages: one to the
+effect that the domain controller cannot be found; the other claims that the account does not
+exist in the domain or that the password is incorrect. This may be due to incompatible
+settings between the Windows client and the Samba-3 server for <emphasis>schannel</emphasis>
+(secure channel) settings or <emphasis>smb signing</emphasis> settings. Check your Samba
+settings for <emphasis>client schannel</emphasis>, <emphasis>server schannel</emphasis>,
+<emphasis>client signing</emphasis>, <emphasis>server signing</emphasis> by executing:
+<screen>
+<command>testparm -v | grep channel</command> and looking for the value of these parameters.
+</screen>
+</para>
+
+<para>
+Also use the MMC &smbmdash; Local Security Settings. This tool is available from the
+Control Panel. The Policy settings are found in the Local Policies/Security Options area and are prefixed by
+<emphasis>Secure Channel:..., and Digitally sign...</emphasis>.
+</para>
+
+<para>
+It is important that these be set consistently with the Samba-3 server settings.
+</para>
+
+</sect2>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml
new file mode 100644
index 00000000000..957abbfdadb
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml
@@ -0,0 +1,2675 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="passdb">
+<chapterinfo>
+	&author.jelmer;
+	&author.jht;
+	&author.jerry;
+	&author.jeremy;
+	<author>&person.gd;<contrib>LDAP updates</contrib></author>
+	<author>
+		<firstname>Olivier (lem)</firstname><surname>Lemaire</surname>
+		<affiliation>
+			<orgname>IDEALX</orgname>
+			<address><email>olem@IDEALX.org</email></address>
+		</affiliation>
+	</author>
+
+	<pubdate>May 24, 2003</pubdate>
+</chapterinfo>
+<title>Account Information Databases</title>
+
+<para>
+<indexterm><primary>account backends</primary></indexterm>
+<indexterm><primary>password backends</primary></indexterm>
+<indexterm><primary>scalability</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+Early releases of Samba-3 implemented new capability to work concurrently with multiple account backends. This
+capability was removed beginning with release of Samba 3.0.23. Commencing with Samba 3.0.23 it is possible to
+work with only one specified passwd backend.
+</para>
+
+<para>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>tdbsam</primary></indexterm>
+<indexterm><primary>ldapsam</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>single repository</primary></indexterm>
+The three passdb backends that are fully maintained (actively supported) by the Samba Team are:
+<literal>smbpasswd</literal> (being obsoleted), <literal>tdbsam</literal> (a tdb-based binary file format),
+and <literal>ldapsam</literal> (LDAP directory).  Of these, only the <literal>ldapsam</literal> backend
+stores both POSIX (UNIX) and Samba user and group account information in a single repository. The
+<literal>smbpasswd</literal> and <literal>tdbsam</literal> backends store only Samba user accounts.
+</para>
+
+<para>
+In a strict sense, there are three supported account storage and access systems. One of these is considered
+obsolete (smbpasswd). It is recommended to use the <literal>tdbsam</literal> method for all simple systems. Use
+<literal>ldapsam</literal> for larger and more complex networks.
+</para>
+
+<para>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>account storage mechanisms</primary></indexterm>
+<indexterm><primary>account storage system</primary></indexterm>
+<indexterm><primary>user and trust accounts</primary></indexterm>
+<indexterm><primary>machine trust accounts</primary></indexterm>
+<indexterm><primary>computer accounts</primary></indexterm>
+<indexterm><primary>interdomain trust accounts</primary></indexterm>
+In a strict and literal sense, the passdb backends are account storage mechanisms (or methods) alone. The choice
+of terminology can be misleading, however we are stuck with this choice of wording. This chapter documents the
+nature of the account storage system with a focus on user and trust accounts. Trust accounts have two forms,
+machine trust accounts (computer accounts) and interdomain trust accounts. These are all treated as user-like
+entities.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+Samba-3 provides for complete backward compatibility with Samba-2.2.x functionality
+as follows:
+<indexterm><primary>SAM backend</primary><secondary>smbpasswd</secondary></indexterm>
+<indexterm><primary>SAM backend</primary><secondary>ldapsam_compat</secondary></indexterm>
+<indexterm><primary>encrypted passwords</primary></indexterm>
+</para>
+
+<sect2>
+	<title>Backward Compatibility Account Storage Systems</title>
+
+<variablelist>
+	<varlistentry><term>Plaintext</term>
+		<listitem>
+			<para>
+<indexterm><primary>plaintext</primary></indexterm>
+<indexterm><primary>plaintext authentication</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>/etc/shadow</primary></indexterm>
+<indexterm><primary>PAM</primary></indexterm>
+			This isn't really a backend at all, but is listed here for simplicity.  Samba can be configured to pass
+			plaintext authentication requests to the traditional UNIX/Linux <filename>/etc/passwd</filename> and
+			<filename>/etc/shadow</filename>-style subsystems.  On systems that have Pluggable Authentication Modules
+			(PAM) support, all PAM modules are supported. The behavior is just as it was with Samba-2.2.x, and the
+			protocol limitations imposed by MS Windows clients apply likewise. Please refer to <link
+			linkend="passdbtech">Technical Information</link>, for more information regarding the limitations of plaintext
+			password usage.
+			</para>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry><term>smbpasswd</term>
+		<listitem>
+			<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>LanMan passwords</primary></indexterm>
+<indexterm><primary>NT-encrypted passwords</primary></indexterm>
+<indexterm><primary>SAM</primary></indexterm>
+			This option allows continued use of the <filename>smbpasswd</filename>
+			file that maintains a plain ASCII (text) layout that includes the MS Windows
+			LanMan and NT-encrypted passwords as well as a field that stores some
+			account information. This form of password backend does not store any of
+			the MS Windows NT/200x SAM (Security Account Manager) information required to
+			provide the extended controls that are needed for more comprehensive
+			interoperation with MS Windows NT4/200x servers.
+			</para>
+
+			<para>
+			This backend should be used only for backward compatibility with older
+			versions of Samba. It may be deprecated in future releases.
+			</para>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry><term>ldapsam_compat (Samba-2.2 LDAP Compatibility)</term>
+		<listitem>
+			<para>
+<indexterm><primary>ldapsam_compat</primary></indexterm>
+<indexterm><primary>Samba-2.2.x LDAP schema</primary></indexterm>
+<indexterm><primary>OpenLDAP backend</primary></indexterm>
+			There is a password backend option that allows continued operation with
+			an existing OpenLDAP backend that uses the Samba-2.2.x LDAP schema extension.
+			This option is provided primarily as a migration tool, although there is
+			no reason to force migration at this time. This tool will eventually
+			be deprecated.
+			</para>
+		</listitem>
+	</varlistentry>
+</variablelist>
+
+</sect2>
+
+<sect2>
+<title>New Account Storage Systems</title>
+
+<para>
+Samba-3 introduces a number of new password backend capabilities.
+<indexterm><primary>SAM backend</primary><secondary>tdbsam</secondary></indexterm>
+<indexterm><primary>SAM backend</primary><secondary>ldapsam</secondary></indexterm>
+</para>
+
+<variablelist>
+	<varlistentry><term>tdbsam</term>
+		<listitem>
+			<para>
+<indexterm><primary>rich database backend</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+			This backend provides a rich database backend for local servers. This
+			backend is not suitable for multiple domain controllers (i.e., PDC + one
+			or more BDC) installations.
+			</para>
+
+			<para>
+<indexterm><primary>extended SAM</primary></indexterm>
+<indexterm><primary>TDB</primary></indexterm>
+<indexterm><primary>binary format TDB</primary></indexterm>
+<indexterm><primary>trivial database</primary></indexterm>
+<indexterm><primary>system access controls</primary></indexterm>
+<indexterm><primary>MS Windows NT4/200x</primary></indexterm>
+			The <emphasis>tdbsam</emphasis> password backend stores the old <emphasis>
+			smbpasswd</emphasis> information plus the extended MS Windows NT/200x
+			SAM information into a binary format TDB (trivial database) file.
+			The inclusion of the extended information makes it possible for Samba-3
+			to implement the same account and system access controls that are possible
+			with MS Windows NT4/200x-based systems.
+			</para>
+
+			<para>
+<indexterm><primary>simple operation</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+			The inclusion of the <emphasis>tdbsam</emphasis> capability is a direct
+			response to user requests to allow simple site operation without the overhead
+			of the complexities of running OpenLDAP. It is recommended to use this only
+			for sites that have fewer than 250 users. For larger sites or implementations,
+			the use of OpenLDAP or of Active Directory integration is strongly recommended.
+			</para>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry><term>ldapsam</term>
+		<listitem>
+			<para>
+<indexterm><primary>rich directory backend</primary></indexterm>
+<indexterm><primary>distributed account</primary></indexterm>
+			This provides a rich directory backend for distributed account installation.
+			</para>
+
+			<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>Samba schema</primary></indexterm>
+<indexterm><primary>schema file</primary></indexterm>
+<indexterm><primary>examples/LDAP</primary></indexterm>
+			Samba-3 has a new and extended LDAP implementation that requires configuration
+			of OpenLDAP with a new format Samba schema. The new format schema file is
+			included in the <filename class="directory">examples/LDAP</filename> directory of the Samba distribution.
+			</para>
+
+			<para>
+<indexterm><primary>expands control abilities</primary></indexterm>
+<indexterm><primary>profile</primary></indexterm>
+<indexterm><primary>home directories</primary></indexterm>
+<indexterm><primary>account access controls</primary></indexterm>
+<indexterm><primary>greater scalability</primary></indexterm>
+			The new LDAP implementation significantly expands the control abilities that
+			were possible with prior versions of Samba. It is now possible to specify
+			<quote>per-user</quote> profile settings, home directories, account access controls, and
+			much more. Corporate sites will see that the Samba Team has listened to their
+			requests both for capability and greater scalability.
+			</para>
+		</listitem>
+	</varlistentry>
+
+</variablelist>
+
+</sect2>
+
+</sect1>
+
+<sect1 id="passdbtech">
+	<title>Technical Information</title>
+
+	<para>
+<indexterm><primary>plaintext passwords</primary></indexterm>
+<indexterm><primary>encrypted passwords</primary></indexterm>
+	Old Windows clients send plaintext passwords over the wire. Samba can check these
+	passwords by encrypting them and comparing them to the hash stored in the UNIX user database.
+	</para>
+
+	<para>
+<indexterm><primary>encrypted passwords</primary></indexterm>
+<indexterm><primary>LanMan</primary></indexterm>
+<indexterm><primary>plaintext passwords</primary></indexterm>
+<indexterm><primary>registry</primary></indexterm>
+	Newer Windows clients send encrypted passwords (LanMan and NT hashes) instead of plaintext passwords over
+	the wire. The newest clients will send only encrypted passwords and refuse to send plaintext passwords unless
+	their registry is tweaked.
+	</para>
+
+	<para>
+<indexterm><primary>UNIX-style encrypted passwords</primary></indexterm>
+<indexterm><primary>converted</primary></indexterm>
+	Many people ask why Samba cannot simply use the UNIX password database. Windows requires
+	passwords that are encrypted in its own format.  The UNIX passwords can't be converted to
+	UNIX-style encrypted passwords. Because of that, you can't use the standard UNIX user
+	database, and you have to store the LanMan and NT hashes somewhere else.
+	</para>
+
+	<para>
+<indexterm><primary>differently encrypted passwords</primary></indexterm>
+<indexterm><primary>profile</primary></indexterm>
+<indexterm><primary>workstations</primary></indexterm>
+<indexterm><primary>tdbsam</primary></indexterm>
+	In addition to differently encrypted passwords, Windows also stores certain data for each
+	user that is not stored in a UNIX user database: for example, workstations the user may logon from,
+	the location where the user's profile is stored, and so on. Samba retrieves and stores this
+	information using a <smbconfoption name="passdb backend"/>. Commonly available backends are LDAP,
+	tdbsam, and plain text file. For more information, see the man page for &smb.conf; regarding the
+	<smbconfoption name="passdb backend"/> parameter.
+	</para>
+
+
+	<figure id="idmap-sid2uid">
+		<title>IDMAP: Resolution of SIDs to UIDs.</title>
+		<imagefile scale="40">idmap-sid2uid</imagefile>
+	</figure>
+
+	<para>
+	<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+	The resolution of SIDs to UIDs is fundamental to correct operation of Samba. In both cases shown, if winbindd
+	is not running or cannot be contacted, then only local SID/UID resolution is possible. See <link
+	linkend="idmap-sid2uid">resolution of SIDs to UIDs</link> and <link linkend="idmap-uid2sid">resolution of UIDs
+	to SIDs</link> diagrams.
+	</para>
+
+	<figure id="idmap-uid2sid">
+		<title>IDMAP: Resolution of UIDs to SIDs.</title>
+		<imagefile scale="50">idmap-uid2sid</imagefile>
+	</figure>
+
+	<sect2>
+	<title>Important Notes About Security</title>
+
+		<para>
+<indexterm><primary>SMB password encryption</primary></indexterm>
+<indexterm><primary>clear-text passwords</primary></indexterm>
+<indexterm><primary>hashed password equivalent</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>secret</primary></indexterm>
+		The UNIX and SMB password encryption techniques seem similar on the surface. This
+		similarity is, however, only skin deep. The UNIX scheme typically sends clear-text
+		passwords over the network when logging in. This is bad. The SMB encryption scheme
+		never sends the clear-text password over the network, but it does store the 16-byte
+		hashed values on disk. This is also bad. Why? Because the 16 byte hashed values
+		are a <quote>password equivalent.</quote> You cannot derive the user's password from them, but
+		they could potentially be used in a modified client to gain access to a server.
+		This would require considerable technical knowledge on behalf of the attacker but
+		is perfectly possible. You should therefore treat the data stored in whatever passdb
+		backend you use (smbpasswd file, LDAP) as though it contained the clear-text
+		passwords of all your users. Its contents must be kept secret, and the file should
+		be protected accordingly.
+		</para>
+
+		<para>
+<indexterm><primary>password scheme</primary></indexterm>
+<indexterm><primary>plaintext passwords</primary></indexterm>
+<indexterm><primary>compatible</primary></indexterm>
+		Ideally, we would like a password scheme that involves neither plaintext passwords
+		on the network nor plaintext passwords on disk. Unfortunately, this is not available because Samba is stuck with
+		having to be compatible with other SMB systems (Windows NT, Windows for Workgroups, Windows 9x/Me).
+		</para>
+
+		<para>
+<indexterm><primary>encrypted passwords</primary></indexterm>
+<indexterm><primary>plaintext passwords</primary></indexterm>
+		Windows NT 4.0 Service Pack 3 changed the default setting so plaintext passwords
+		are disabled from being sent over the wire. This mandates either the use of encrypted
+		password support or editing the Windows NT registry to re-enable plaintext passwords.
+		</para>
+
+		<para>
+<indexterm><primary>domain security</primary></indexterm>
+<indexterm><primary>domain environment</primary></indexterm>
+		The following versions of Microsoft Windows do not support full domain security protocols,
+		although they may log onto a domain environment:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>MS DOS Network client 3.0 with the basic network redirector installed.</para></listitem>
+			<listitem><para>Windows 95 with the network redirector update installed.</para></listitem>
+			<listitem><para>Windows 98 [Second Edition].</para></listitem>
+			<listitem><para>Windows Me.</para></listitem>
+		</itemizedlist>
+
+		<note>
+		<para>
+<indexterm><primary>Windows XP Home</primary></indexterm>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>domain logons</primary></indexterm>
+ 		MS Windows XP Home does not have facilities to become a domain member, and it cannot participate in domain logons.
+		</para>
+		</note>
+
+		<para>
+		The following versions of MS Windows fully support domain security protocols.
+		</para>
+
+		<itemizedlist>
+			<listitem><para>Windows NT 3.5x.</para></listitem>
+			<listitem><para>Windows NT 4.0.</para></listitem>
+			<listitem><para>Windows 2000 Professional.</para></listitem>
+			<listitem><para>Windows 200x Server/Advanced Server.</para></listitem>
+			<listitem><para>Windows XP Professional.</para></listitem>
+		</itemizedlist>
+
+		<para>
+<indexterm><primary>SMB/CIFS</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+<indexterm><primary>challenge/response mechanis</primary></indexterm>
+<indexterm><primary>clear-text</primary></indexterm>
+<indexterm><primary>encrypted</primary></indexterm>
+<indexterm><primary>negotiate</primary></indexterm>
+		All current releases of Microsoft SMB/CIFS clients support authentication via the
+		SMB challenge/response mechanism described here. Enabling clear-text authentication
+		does not disable the ability of the client to participate in encrypted authentication.
+		Instead, it allows the client to negotiate either plaintext or encrypted password
+		handling.
+		</para>
+
+		<para>
+<indexterm><primary>cached encrypted password</primary></indexterm>
+<indexterm><primary>plaintext passwords</primary></indexterm>
+<indexterm><primary>registry change</primary></indexterm>
+<indexterm><primary>auto-reconnect</primary></indexterm>
+<indexterm><primary>encrypted passwords</primary></indexterm>
+		MS Windows clients will cache the encrypted password alone. Where plaintext passwords
+		are re-enabled through the appropriate registry change, the plaintext password is never
+		cached. This means that in the event that a network connections should become disconnected
+		(broken), only the cached (encrypted) password will be sent to the resource server to
+		effect an auto-reconnect. If the resource server does not support encrypted passwords, the
+		auto-reconnect will fail. Use of encrypted passwords is strongly advised.
+		</para>
+
+		<sect3>
+		<title>Advantages of Encrypted Passwords</title>
+
+			<itemizedlist>
+				<listitem><para>
+<indexterm><primary>passed across the network</primary></indexterm>
+<indexterm><primary>network sniffer</primary></indexterm>
+<indexterm><primary>SMB server</primary></indexterm>
+				Plaintext passwords are not passed across the network. Someone using a network sniffer
+				cannot just record passwords going to the SMB server.
+				</para></listitem>
+
+				<listitem><para>
+<indexterm><primary>not stored anywhere</primary></indexterm>
+<indexterm><primary>memory</primary></indexterm>
+<indexterm><primary>disk</primary></indexterm>
+				Plaintext passwords are not stored anywhere in memory or on disk.
+				</para></listitem>
+ 
+				<listitem><para>
+<indexterm><primary>encrypted passwords</primary></indexterm>
+<indexterm><primary>user-level security</primary></indexterm>
+<indexterm><primary>password prompt</primary></indexterm>
+<indexterm><primary>SMB encryption</primary></indexterm>
+				Windows NT does not like talking to a server that does not support encrypted passwords. It will refuse to
+				browse the server if the server is also in user-level security mode. It will insist on prompting the user for
+				the password on each connection, which is very annoying. The only thing you can do to stop this is to use SMB
+				encryption.
+				</para></listitem>
+
+				<listitem><para>
+<indexterm><primary>encrypted password</primary></indexterm>
+<indexterm><primary>automatic reconnects</primary></indexterm>
+				Encrypted password support allows automatic share (resource) reconnects.
+				</para></listitem>
+
+				<listitem><para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+				Encrypted passwords are essential for PDC/BDC operation.
+				</para></listitem>
+			</itemizedlist>
+		</sect3>
+
+
+		<sect3>
+		<title>Advantages of Non-Encrypted Passwords</title>
+
+			<itemizedlist>
+				<listitem><para>
+<indexterm><primary>cached in memory</primary></indexterm>
+				Plaintext passwords are not kept on disk and are not cached in memory.
+				</para></listitem>
+
+				<listitem><para>
+<indexterm><primary>Login</primary></indexterm>
+<indexterm><primary>FTP</primary></indexterm>
+				Plaintext passwords use the same password file as other UNIX services, such as Login and FTP.
+				</para></listitem>
+
+				<listitem><para>
+<indexterm><primary>Telnet</primary></indexterm>
+<indexterm><primary>FTP</primary></indexterm>
+				Use of other services (such as Telnet and FTP) that send plaintext passwords over
+				the network makes sending them for SMB not such a big deal.
+				</para></listitem>
+			</itemizedlist>
+		</sect3>
+	</sect2>
+
+	<sect2>
+	<title>Mapping User Identifiers between MS Windows and UNIX</title>
+
+	<para>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>mapping</primary></indexterm>
+	Every operation in UNIX/Linux requires a user identifier (UID), just as in
+	MS Windows NT4/200x this requires a security identifier (SID). Samba provides
+	two means for mapping an MS Windows user to a UNIX/Linux UID.
+	</para>
+
+	<para>
+<indexterm><primary>Samba SAM</primary></indexterm>
+<indexterm><primary>SAM</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>account information database</primary></indexterm>
+<indexterm><primary>local user account</primary></indexterm>
+	First, all Samba SAM database accounts require a UNIX/Linux UID that the account will map to. As users are
+	added to the account information database, Samba will call the <smbconfoption name="add user script"/>
+	interface to add the account to the Samba host OS. In essence all accounts in the local SAM require a local
+	user account.
+	</para>
+
+	<para>
+	<indexterm><primary>idmap uid</primary></indexterm>
+	<indexterm><primary>idmap gid</primary></indexterm>
+	<indexterm><primary>UID</primary></indexterm>
+	<indexterm><primary>SAM</primary></indexterm>
+	<indexterm><primary>foreign domain</primary></indexterm>
+	<indexterm><primary>non-member Windows client</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	The second way to map Windows SID to UNIX UID is via the <emphasis>idmap uid</emphasis> and
+	<emphasis>idmap gid</emphasis> parameters in &smb.conf;.  Please refer to the man page for information about
+	these parameters.  These parameters are essential when mapping users from a remote (non-member Windows client
+	or a member of a foreign domain) SAM server.
+	</para>
+
+	</sect2>
+
+	<sect2 id="idmapbackend">
+	<title>Mapping Common UIDs/GIDs on Distributed Machines</title>
+
+	<para>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>domain member servers</primary></indexterm>
+<indexterm><primary>NFS</primary></indexterm>
+<indexterm><primary>rsync</primary></indexterm>
+	Samba-3 has a special facility that makes it possible to maintain identical UIDs and GIDs
+	on all servers in a distributed network. A distributed network is one where there exists
+	a PDC, one or more BDCs, and/or one or more domain member servers. Why is this important?
+	This is important if files are being shared over more than one protocol (e.g., NFS) and where
+	users are copying files across UNIX/Linux systems using tools such as <command>rsync</command>.
+	</para>
+
+	<para>
+<indexterm><primary>LDAP-based</primary></indexterm>
+<indexterm><primary>idmap backend</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>SAM backend</primary></indexterm>
+<indexterm><primary>LDAP idmap Backend</primary></indexterm>
+	<indexterm><primary>idmap backend</primary></indexterm>
+	The special facility is enabled using a parameter called <parameter>idmap backend</parameter>.
+	The default setting for this parameter is an empty string. Technically it is possible to use
+	an LDAP-based idmap backend for UIDs and GIDs, but it makes most sense when this is done for
+	network configurations that also use LDAP for the SAM backend.
+	<link linkend="idmapbackendexample">Example Configuration with the LDAP idmap Backend</link>
+	shows that configuration.
+	</para>
+
+<indexterm><primary>SAM backend</primary><secondary>ldapsam</secondary></indexterm>
+<example id="idmapbackendexample">
+<title>Example Configuration with the LDAP idmap Backend</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="idmap backend">ldap:ldap://ldap-server.quenya.org:636</smbconfoption>
+<smbconfcomment>Alternatively, this could be specified as:</smbconfcomment>
+<smbconfoption name="idmap backend">ldap:ldaps://ldap-server.quenya.org</smbconfoption>
+</smbconfblock>
+</example>
+
+	<para>
+<indexterm><primary>LDAP backends</primary></indexterm>
+<indexterm><primary>PADL Software</primary></indexterm>
+	A network administrator who wants to make significant use of LDAP backends will sooner or later be
+	exposed to the excellent work done by PADL Software. PADL <ulink url="http://www.padl.com"/> have
+	produced and released to open source an array of tools that might be of interest. These tools include:
+	</para>
+
+	<itemizedlist>
+		<listitem>
+		<para>
+<indexterm><primary>nss_ldap</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>AIX</primary></indexterm>
+<indexterm><primary>Linux</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>Solaris</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+		<emphasis>nss_ldap:</emphasis> An LDAP name service switch (NSS) module to provide native
+		name service support for AIX, Linux, Solaris, and other operating systems. This tool
+		can be used for centralized storage and retrieval of UIDs and GIDs.
+		</para>
+		</listitem>
+
+		<listitem>
+		<para>
+<indexterm><primary>pam_ldap</primary></indexterm>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>access authentication</primary></indexterm>
+		<emphasis>pam_ldap:</emphasis> A PAM module that provides LDAP integration for UNIX/Linux
+		system access authentication.
+		</para>
+		</listitem>
+
+		<listitem>
+		<para>
+<indexterm><primary>idmap_ad</primary></indexterm>
+<indexterm><primary>IDMAP backend</primary></indexterm>
+<indexterm><primary>RFC 2307</primary></indexterm>
+<indexterm><primary>PADL</primary></indexterm>
+		<emphasis>idmap_ad:</emphasis> An IDMAP backend that supports the Microsoft Services for
+		UNIX RFC 2307 schema available from the PADL Web
+		<ulink url="http://www.padl.com/download/xad_oss_plugins.tar.gz">site</ulink>.
+		</para>
+		</listitem>
+	</itemizedlist>
+
+	</sect2>
+
+	<sect2>
+	<title>Comments Regarding LDAP</title>
+
+	<para>
+<indexterm><primary>LDAP</primary><secondary>directories</secondary></indexterm>
+<indexterm><primary>architecture</primary></indexterm>
+<indexterm><primary>FIM</primary></indexterm>
+<indexterm><primary>SSO</primary></indexterm>
+	There is much excitement and interest in LDAP directories in the information technology world
+	today. The LDAP architecture was designed to be highly scalable. It was also designed for
+	use across a huge number of potential areas of application encompassing a wide range of operating
+	systems and platforms. LDAP technologies are at the heart of the current generations of Federated
+	Identity Management (FIM) solutions that can underlie a corporate Single Sign-On (SSO) environment.
+	</para>
+
+	<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>eDirectory</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+	LDAP implementations have been built across a wide variety of platforms. It lies at the core of Microsoft
+	Windows Active Directory services (ADS), Novell's eDirectory, as well as many others. Implementation of the
+	directory services LDAP involves interaction with legacy as well as new generation applications, all of which
+	depend on some form of authentication services.
+	</para>
+
+	<para>
+<indexterm><primary>LDAP directory</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+<indexterm><primary>access controls</primary></indexterm>
+<indexterm><primary>intermediate tools</primary></indexterm>
+<indexterm><primary>middle-ware</primary></indexterm>
+<indexterm><primary>central environment</primary></indexterm>
+<indexterm><primary>infrastructure</primary></indexterm>
+<indexterm><primary>login shells</primary></indexterm>
+<indexterm><primary>mail</primary></indexterm>
+<indexterm><primary>messaging systems</primary></indexterm>
+<indexterm><primary>quota controls</primary></indexterm>
+<indexterm><primary>printing systems</primary></indexterm>
+<indexterm><primary>DNS servers</primary></indexterm>
+<indexterm><primary>DHCP servers</primary></indexterm>
+	UNIX services can utilize LDAP directory information for authentication and access controls
+	through intermediate tools and utilities. The total environment that consists of the LDAP directory
+	and the middle-ware tools and utilities makes it possible for all user access to the UNIX platform
+	to be managed from a central environment and yet distributed to wherever the point of need may
+	be physically located. Applications that benefit from this infrastructure include: UNIX login
+	shells, mail and messaging systems, quota controls, printing systems, DNS servers, DHCP servers,
+	and also Samba.
+	</para>
+
+	<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>scalable</primary></indexterm>
+<indexterm><primary>SAM backend</primary></indexterm>
+<indexterm><primary>LDAP directory</primary></indexterm>
+<indexterm><primary>management costs</primary></indexterm>
+	Many sites are installing LDAP for the first time in order to provide a scalable passdb backend
+	for Samba. Others are faced with the need to adapt an existing LDAP directory to new uses such
+	as for the Samba SAM backend. Whatever your particular need and attraction to Samba may be,
+	decisions made in respect of the design of the LDAP directory structure and its implementation
+	are of a durable nature for the site. These have far-reaching implications that affect long-term
+	information systems management costs.
+	</para>
+
+	<para>
+<indexterm><primary>LDAP deployment</primary></indexterm>
+<indexterm><primary>Directory Information Tree</primary><see>DIT</see></indexterm>
+	Do not rush into an LDAP deployment. Take the time to understand how the design of the Directory
+	Information Tree (DIT) may impact current and future site needs, as well as the ability to meet
+	them. The way that Samba SAM information should be stored within the DIT varies from site to site
+	and with each implementation new experience is gained. It is well understood by LDAP veterans that
+	first implementations create awakening, second implementations of LDAP create fear, and
+	third-generation deployments bring peace and tranquility.
+	</para>
+
+	<sect3>
+	<title>Caution Regarding LDAP and Samba</title>
+
+	<para>
+<indexterm><primary>POSIX identity</primary></indexterm>
+<indexterm><primary>networking environment</primary></indexterm>
+<indexterm><primary>user accounts</primary></indexterm>
+<indexterm><primary>group accounts</primary></indexterm>
+<indexterm><primary>machine trust accounts</primary></indexterm>
+<indexterm><primary>interdomain trust accounts</primary></indexterm>
+<indexterm><primary>intermediate information</primary></indexterm>
+	Samba requires UNIX POSIX identity information as well as a place to store information that is
+	specific to Samba and the Windows networking environment. The most used information that must
+	be dealt with includes: user accounts, group accounts, machine trust accounts, interdomain
+	trust accounts, and intermediate information specific to Samba internals.
+	</para>
+
+	<para>
+<indexterm><primary>deployment guidelines</primary></indexterm>
+<indexterm><primary>HOWTO documents</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+	The example deployment guidelines in this book, as well as other books and HOWTO documents
+	available from the internet may not fit with established directory designs and implementations.
+	The existing DIT may not be able to accommodate the simple information layout proposed in common
+	sources. Additionally, you may find that the common scripts and tools that are used to provision
+	the LDAP directory for use with Samba may not suit your needs.
+	</para>
+
+	<para>
+<indexterm><primary>existing LDAP DIT</primary></indexterm>
+	It is not uncommon, for sites that have existing LDAP DITs to find necessity to generate a
+	set of site-specific scripts and utilities to make it possible to deploy Samba within the
+	scope of site operations. The way that user and group accounts are distributed throughout
+	the DIT may make this a challenging matter. The solution will, of course, be rewarding, but
+	the journey to it may be challenging. Take time to understand site needs and do not rush
+	into deployment.
+	</para>
+
+	<para>
+<indexterm><primary>scripts</primary></indexterm>
+<indexterm><primary>tools</primary></indexterm>
+	Above all, do not blindly use scripts and tools that are not suitable for your site. Check
+	and validate all scripts before you execute them to make sure that the existing infrastructure
+	will not be damaged by inadvertent use of an inappropriate tool.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>LDAP Directories and Windows Computer Accounts</title>
+
+		<para>
+<indexterm><primary>turnkey solution</primary></indexterm>
+<indexterm><primary>LDAP.</primary></indexterm>
+<indexterm><primary>frustrating experience</primary></indexterm>
+		Samba doesn't provide a turnkey solution to LDAP. It is best to deal with the design and
+		configuration of an LDAP directory prior to integration with Samba. A working knowledge
+		of LDAP makes Samba integration easy, and the lack of a working knowledge of LDAP can make
+		it a frustrating experience.
+		</para>
+
+		<para>
+<indexterm><primary>computer accounts</primary></indexterm>
+<indexterm><primary>machine accounts</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+		Computer (machine) accounts can be placed wherever you like in an LDAP directory subject
+		to some constraints that are described in this chapter.
+		</para>
+
+		<para>
+<indexterm><primary>POSIX</primary></indexterm>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+<indexterm><primary>computer accounts</primary></indexterm>
+<indexterm><primary>machine accounts</primary></indexterm>
+<indexterm><primary>Windows NT4/200X</primary></indexterm>
+<indexterm><primary>user account</primary></indexterm>
+<indexterm><primary>trust accounts</primary></indexterm>
+		The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba.
+		Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats
+		them. A user account and a machine account are indistinquishable from each other, except that
+		the machine account ends in a $ character, as do trust accounts.
+		</para>
+
+		<para>
+<indexterm><primary>user</primary></indexterm>
+<indexterm><primary>group</primary></indexterm>
+<indexterm><primary>machine</primary></indexterm>
+<indexterm><primary>trust</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+		The need for Windows user, group, machine, trust, and other accounts to be tied to a valid UNIX
+		UID is a design decision that was made a long way back in the history of Samba development. It
+		is unlikely that this decision will be reversed or changed during the remaining life of the
+		Samba-3.x series.
+		</para>
+
+		<para>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+		The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that
+		must refer back to the host operating system on which Samba is running. The NSS is the preferred
+		mechanism that shields applications (like Samba) from the need to know everything about every
+		host OS it runs on.
+		</para>
+
+		<para>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>passwd</primary></indexterm>
+<indexterm><primary>shadow</primary></indexterm>
+<indexterm><primary>group</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+		Samba asks the host OS to provide a UID via the <quote>passwd</quote>, <quote>shadow</quote>,
+		and <quote>group</quote> facilities in the NSS control (configuration) file. The best tool
+		for achieving this is left up to the UNIX administrator to determine. It is not imposed by
+		Samba. Samba provides winbindd with its support libraries as one method. It is
+		possible to do this via LDAP, and for that Samba provides the appropriate hooks so that
+		all account entities can be located in an LDAP directory.
+		</para>
+
+		<para>
+<indexterm><primary>PADL</primary></indexterm>
+<indexterm><primary>nss_ldap</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>documentation</primary></indexterm>
+		For many the weapon of choice is to use the PADL nss_ldap utility. This utility must
+		be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That
+		is fundamentally an LDAP design question.  The information provided on the Samba list and
+		in the documentation is directed at providing working examples only. The design
+		of an LDAP directory is a complex subject that is beyond the scope of this documentation.
+		</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1 id="acctmgmttools">
+<title>Account Management Tools</title>
+
+<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>machine accounts</primary></indexterm>
+<indexterm><primary>management tools</primary></indexterm>
+Samba provides two tools for management of user and machine accounts:
+<command>smbpasswd</command> and <command>pdbedit</command>.
+</para>
+
+<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>password aging</primary></indexterm>
+<indexterm><primary>failed logins</primary></indexterm>
+The <command>pdbedit</command> can be used to manage account policies in addition to
+Samba user account information. The policy management capability is used to administer
+domain default settings for password aging and management controls to handle failed login
+attempts.
+</para>
+
+<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>storage mechanism</primary></indexterm>
+<indexterm><primary>SambaSAMAccount</primary></indexterm>
+<indexterm><primary>net</primary></indexterm>
+Some people are confused when reference is made to <literal>smbpasswd</literal> because the
+name refers to a storage mechanism for SambaSAMAccount information, but it is also the name
+of a utility tool. That tool is destined to eventually be replaced by new functionality that
+is being added to the <command>net</command> toolset (see <link linkend="NetCommand">the Net Command</link>.
+</para>
+
+	<sect2>
+	<title>The <command>smbpasswd</command> Tool</title>
+
+		<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>passwd</primary></indexterm>
+<indexterm><primary>yppasswd</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>storage methods</primary></indexterm>
+		The <command>smbpasswd</command> utility is similar to the <command>passwd</command>
+		and <command>yppasswd</command> programs. It maintains the two 32 byte password
+		fields in the passdb backend. This utility operates independently of the actual
+		account and password storage methods used (as specified by the <parameter>passdb
+		backend</parameter> in the &smb.conf; file.
+		</para>
+
+		<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>client-server mode</primary></indexterm>
+		<command>smbpasswd</command> works in a client-server mode where it contacts the
+		local smbd to change the user's password on its behalf. This has enormous benefits.
+		</para>
+
+		<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>change passwords</primary></indexterm>
+		<command>smbpasswd</command> has the capability to change passwords on Windows NT
+		servers (this only works when the request is sent to the NT PDC if changing an NT
+		domain user's password).
+		</para>
+
+		<para>
+		<indexterm><primary>user management</primary></indexterm>
+		<indexterm><primary>user account</primary><secondary>Adding/Deleting</secondary></indexterm>
+		<command>smbpasswd</command> can be used to:
+		</para>
+
+		<itemizedlist>
+			<listitem><para><emphasis>add</emphasis> user or machine accounts.</para></listitem>
+			<listitem><para><emphasis>delete</emphasis> user or machine accounts.</para></listitem>
+			<listitem><para><emphasis>enable</emphasis> user or machine accounts.</para></listitem>
+			<listitem><para><emphasis>disable</emphasis> user or machine accounts.</para></listitem>
+			<listitem><para><emphasis>set to NULL</emphasis> user passwords.</para></listitem>
+			<listitem><para><emphasis>manage</emphasis> interdomain trust accounts.</para></listitem>
+		</itemizedlist>
+
+		<para>
+		To run smbpasswd as a normal user, just type:
+		</para>
+
+		<para>
+<screen>
+&prompt;<userinput>smbpasswd</userinput>
+<prompt>Old SMB password: </prompt><userinput><replaceable>secret</replaceable></userinput>
+</screen>
+		For <replaceable>secret</replaceable>, type the old value here or press return if
+		there is no old password.
+<screen>
+<prompt>New SMB Password: </prompt><userinput><replaceable>new secret</replaceable></userinput>
+<prompt>Repeat New SMB Password: </prompt><userinput><replaceable>new secret</replaceable></userinput>
+</screen>
+		</para>
+
+		<para>
+		If the old value does not match the current value stored for that user, or the two
+		new values do not match each other, then the password will not be changed.
+		</para>
+
+		<para>
+<indexterm><primary>SMB password</primary></indexterm>
+		When invoked by an ordinary user, the command will allow only the user to change his or her own
+		SMB password.
+		</para>
+
+		<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>SMB password</primary></indexterm>
+		When run by root, <command>smbpasswd</command> may take an optional argument specifying
+		the username whose SMB password you wish to change. When run as root, <command>smbpasswd</command>
+		does not prompt for or check the old password value, thus allowing root to set passwords
+		for users who have forgotten their passwords.
+		</para>
+
+		<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>passwd</primary></indexterm>
+<indexterm><primary>yppasswd</primary></indexterm>
+<indexterm><primary>change capabilities</primary></indexterm>
+		<command>smbpasswd</command> is designed to work in the way familiar to UNIX
+		users who use the <command>passwd</command> or <command>yppasswd</command> commands.
+		While designed for administrative use, this tool provides essential user-level
+		password change capabilities.
+		</para>
+
+		<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+		For more details on using <command>smbpasswd</command>, refer to the man page (the
+		definitive reference).
+		</para>
+	</sect2>
+
+	<sect2 id="pdbeditthing">
+	<title>The <command>pdbedit</command> Tool</title>
+
+		<para>
+		<indexterm><primary>pdbedit</primary></indexterm>
+		<indexterm><primary>User Management</primary></indexterm>
+		<indexterm><primary>account policy</primary></indexterm>
+		<indexterm><primary>User Accounts</primary><secondary>Adding/Deleting</secondary></indexterm>
+		<command>pdbedit</command> is a tool that can be used only by root. It is used to
+		manage the passdb backend, as well as domain-wide account policy settings. <command>pdbedit</command>
+		can be used to:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>add, remove, or modify user accounts.</para></listitem>
+			<listitem><para>list user accounts.</para></listitem>
+			<listitem><para>migrate user accounts.</para></listitem>
+			<listitem><para>migrate group accounts.</para></listitem>
+			<listitem><para>manage account policies.</para></listitem>
+			<listitem><para>manage domain access policy settings.</para></listitem>
+		</itemizedlist>
+
+		<para>
+		<indexterm><primary>Sarbanes-Oxley</primary></indexterm>
+		Under the terms of the Sarbanes-Oxley Act of 2002, American businesses and organizations are mandated to
+		implement a series of <literal>internal controls</literal> and procedures to communicate, store,
+		and protect financial data. The Sarbanes-Oxley Act has far reaching implications in respect of:
+		</para>
+
+		<orderedlist>
+			<listitem><para>Who has access to information systems that store financial data.</para></listitem>
+			<listitem><para>How personal and financial information is treated among employees and business
+				partners.</para></listitem>
+			<listitem><para>How security vulnerabilities are managed.</para></listitem>
+			<listitem><para>Security and patch level maintenance for all information systems.</para></listitem>
+			<listitem><para>How information systems changes are documented and tracked.</para></listitem>
+			<listitem><para>How information access controls are implemented and managed.</para></listitem>
+			<listitem><para>Auditability of all information systems in respect of change and security.</para></listitem>
+			<listitem><para>Disciplinary procedures and controls to ensure privacy.</para></listitem>
+		</orderedlist>
+
+		<para>
+		<indexterm><primary>accountability</primary></indexterm>
+		<indexterm><primary>compliance</primary></indexterm>
+		In short, the Sarbanes-Oxley Act of 2002 is an instrument that enforces accountability in respect of
+		business related information systems so as to ensure the compliance of all information systems that
+		are used to store personal information and particularly for financial records processing. Similar
+		accountabilities are being demanded around the world.
+		</para>
+
+		<para>
+		<indexterm><primary>laws</primary></indexterm>
+		<indexterm><primary>regulations</primary></indexterm>
+		<indexterm><primary>pdbedit</primary></indexterm>
+		<indexterm><primary>access controls</primary></indexterm>
+		<indexterm><primary>manage accounts</primary></indexterm>
+		The need to be familiar with the Samba tools and facilities that permit information systems operation
+		in compliance with government laws and regulations is clear to all. The <command>pdbedit</command> is
+		currently the only Samba tool that provides the capacity to manage account and systems access controls
+		and policies. During the remaining life-cycle of the Samba-3 series it is possible the new tools may
+		be implemented to aid in this important area.
+		</para>
+
+		<para>
+		Domain global policy controls available in Windows NT4 compared with Samba
+		is shown in <link linkend="policycontrols">NT4 Domain v's Samba Policy Controls</link>.
+		</para>
+
+		<table id="policycontrols">
+		<title>NT4 Domain v's Samba Policy Controls</title>
+            <tgroup cols="5">
+                <colspec align="left" colwidth="2*"/>
+                <colspec align="left" colwidth="2*"/>
+                <colspec align="center" colwidth="1*"/>
+                <colspec align="center" colwidth="1*"/>
+                <colspec align="center" colwidth="1*"/>
+                <thead>
+                    <row>
+                        <entry><para>NT4 policy Name</para></entry>
+                        <entry><para>Samba Policy Name</para></entry>
+                        <entry><para>NT4 Range</para></entry>
+                        <entry><para>Samba Range</para></entry>
+                        <entry><para>Samba Default</para></entry>
+                    </row>
+                </thead>
+                <tbody>
+                    <row>
+					<entry><para>Maximum Password Age</para></entry>
+					<entry><para>maximum password age</para></entry>
+					<entry><para>0 - 999 (days)</para></entry>
+					<entry><para>0 - 4294967295 (sec)</para></entry>
+					<entry><para>4294967295</para></entry>
+                    </row>
+                    <row>
+					<entry><para>Minimum Password Age</para></entry>
+					<entry><para>minimum password age</para></entry>
+					<entry><para>0 - 999 (days)</para></entry>
+					<entry><para>0 - 4294967295 (sec)</para></entry>
+					<entry><para>0</para></entry>
+                    </row>
+                    <row>
+					<entry><para>Mimimum Password Length</para></entry>
+					<entry><para>min password length</para></entry>
+					<entry><para>1 - 14 (Chars)</para></entry>
+					<entry><para>0 - 4294967295 (Chars)</para></entry>
+					<entry><para>5</para></entry>
+                    </row>
+                    <row>
+					<entry><para>Password Uniqueness</para></entry>
+					<entry><para>password history</para></entry>
+					<entry><para>0 - 23 (#)</para></entry>
+					<entry><para>0 - 4294967295 (#)</para></entry>
+					<entry><para>0</para></entry>
+                    </row>
+                    <row>
+					<entry><para>Account Lockout - Reset count after</para></entry>
+					<entry><para>reset count minutes</para></entry>
+					<entry><para>1 - 99998 (min)</para></entry>
+					<entry><para>0 - 4294967295 (min)</para></entry>
+					<entry><para>30</para></entry>
+                    </row>
+                    <row>
+					<entry><para>Lockout after bad logon attempts</para></entry>
+					<entry><para>bad lockout attempt</para></entry>
+					<entry><para>0 - 998 (#)</para></entry>
+					<entry><para>0 - 4294967295 (#)</para></entry>
+					<entry><para>0</para></entry>
+                    </row>
+                    <row>
+					<entry><para>*** Not Known ***</para></entry>
+					<entry><para>disconnect time</para></entry>
+					<entry><para>TBA</para></entry>
+					<entry><para>0 - 4294967295</para></entry>
+					<entry><para>0</para></entry>
+                    </row>
+                    <row>
+					<entry><para>Lockout Duration</para></entry>
+					<entry><para>lockout duration</para></entry>
+					<entry><para>1 - 99998 (min)</para></entry>
+					<entry><para>0 - 4294967295 (min)</para></entry>
+					<entry><para>30</para></entry>
+                    </row>
+                    <row>
+					<entry><para>Users must log on in order to change password</para></entry>
+					<entry><para>user must logon to change password</para></entry>
+					<entry><para>0/1</para></entry>
+					<entry><para>0 - 4294967295</para></entry>
+					<entry><para>0</para></entry>
+                    </row>
+                    <row>
+					<entry><para>*** Registry Setting ***</para></entry>
+					<entry><para>refuse machine password change</para></entry>
+					<entry><para>0/1</para></entry>
+					<entry><para>0 - 4294967295</para></entry>
+					<entry><para>0</para></entry>
+                    </row>
+				</tbody>
+			</tgroup>
+		</table>
+
+		<para>
+		<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>policy settings</primary></indexterm>
+<indexterm><primary>account security</primary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+		The <command>pdbedit</command> tool is the only one that can manage the account
+		security and policy settings. It is capable of all operations that smbpasswd can
+		do as well as a superset of them.
+		</para>
+
+		<para>
+		<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>account import/export</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+		One particularly important purpose of the <command>pdbedit</command> is to allow
+		the import/export of account information from one passdb backend to another.
+		</para>
+
+		<sect3>
+		<title>User Account Management</title>
+
+		<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>system accounts</primary></indexterm>
+<indexterm><primary>user account</primary></indexterm>
+<indexterm><primary>domain user manager</primary></indexterm>
+<indexterm><primary>add user script</primary></indexterm>
+<indexterm><primary>interface scripts</primary></indexterm>
+		The <command>pdbedit</command> tool, like the <command>smbpasswd</command> tool, requires
+		that a POSIX user account already exists in the UNIX/Linux system accounts database (backend).
+		Neither tool will call out to the operating system to create a user account because this is
+		considered to be the responsibility of the system administrator. When the Windows NT4 domain
+		user manager is used to add an account, Samba will implement the <literal>add user script</literal>
+		(as well as the other interface scripts) to ensure that user, group and machine accounts are
+		correctly created and changed. The use of the <command>pdbedit</command> tool does not
+		make use of these interface scripts.
+		</para>
+
+		<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>POSIX account</primary></indexterm>
+		Before attempting to use the <command>pdbedit</command> tool to manage user and machine
+		accounts, make certain that a system (POSIX) account has already been created.
+		</para>
+
+		<sect4>
+		<title>Listing User and Machine Accounts</title>
+
+		<para>
+<indexterm><primary>tdbsam</primary></indexterm>
+<indexterm><primary>password backend</primary></indexterm>
+		The following is an example of the user account information that is stored in
+		a tdbsam password backend. This listing was produced by running:
+<screen>
+&prompt;<userinput>pdbedit -Lv met</userinput>
+UNIX username:        met
+NT username:          met
+Account Flags:        [U          ]
+User SID:             S-1-5-21-1449123459-1407424037-3116680435-2004
+Primary Group SID:    S-1-5-21-1449123459-1407424037-3116680435-1201
+Full Name:            Melissa E Terpstra
+Home Directory:       \\frodo\met\Win9Profile
+HomeDir Drive:        H:
+Logon Script:         scripts\logon.bat
+Profile Path:         \\frodo\Profiles\met
+Domain:               &example.workgroup;
+Account desc:
+Workstations:         melbelle
+Munged dial:
+Logon time:           0
+Logoff time:          Mon, 18 Jan 2038 20:14:07 GMT
+Kickoff time:         Mon, 18 Jan 2038 20:14:07 GMT
+Password last set:    Sat, 14 Dec 2002 14:37:03 GMT
+Password can change:  Sat, 14 Dec 2002 14:37:03 GMT
+Password must change: Mon, 18 Jan 2038 20:14:07 GMT
+</screen>
+		</para>
+
+		<para>
+<indexterm><primary>smbpasswd format</primary></indexterm>
+		Accounts can also be listed in the older <literal>smbpasswd</literal> format:
+<screen>
+&rootprompt;<userinput>pdbedit -Lw</userinput>
+root:0:84B0D8E14D158FF8417EAF50CFAC29C3:
+     AF6DD3FD4E2EA8BDE1695A3F05EFBF52:[U          ]:LCT-42681AB8:
+jht:1000:6BBC4159020A52741486235A2333E4D2:
+     CC099521AD554A3C3CF2556274DBCFBC:[U          ]:LCT-40D75B5B:
+rcg:1002:E95D4331A6F23AF8AAD3B435B51404EE:
+     BB0F2C39B04CA6100F0E535DF8314B43:[U          ]:LCT-40D7C5A3:
+afw:1003:1AAFA7F9F6DC1DEAAAD3B435B51404EE:
+     CE92C2F9471594CDC4E7860CA6BC62DB:[T          ]:LCT-40DA501F:
+met:1004:A2848CB7E076B435AAD3B435B51404EE:
+     F25F5D3405085C555236B80B7B22C0D2:[U          ]:LCT-4244FAB8:
+aurora$:1005:060DE593EA638B8ACC4A19F14D2FF2BB:
+     060DE593EA638B8ACC4A19F14D2FF2BB:[W          ]:LCT-4173E5CC:
+temptation$:1006:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
+     A96703C014E404E33D4049F706C45EE9:[W          ]:LCT-42BF0C57:
+vaioboss$:1001:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
+     88A30A095160072784C88F811E89F98A:[W          ]:LCT-41C3878D:
+frodo$:1008:15891DC6B843ECA41249940C814E316B:
+     B68EADCCD18E17503D3DAD3E6B0B9A75:[W          ]:LCT-42B7979F:
+marvel$:1011:BF709959C3C94E0B3958B7B84A3BB6F3:
+     C610EFE9A385A3E8AA46ADFD576E6881:[W          ]:LCT-40F07A4
+</screen>
+<indexterm><primary>login id</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>LanManger password</primary></indexterm>
+<indexterm><primary>NT password</primary></indexterm>
+<indexterm><primary>Account Flags</primary></indexterm>
+<indexterm><primary>LCT</primary><see>last change time</see></indexterm>
+		The account information that was returned by this command in order from left to right
+		consists of the following colon separated data:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>Login ID.</para></listitem>
+			<listitem><para>UNIX UID.</para></listitem>
+			<listitem>
+				<para>Microsoft LanManager password hash (password converted to upper-case then hashed.</para>
+			</listitem>
+			<listitem><para>Microsoft NT password hash (hash of the case-preserved password).</para></listitem>
+			<listitem><para>Samba SAM Account Flags.</para></listitem>
+			<listitem><para>The LCT data (password last change time).</para></listitem>
+		</itemizedlist>
+
+		<para>
+<indexterm><primary>Account Flags</primary></indexterm>
+<indexterm><primary>pdbedit</primary></indexterm>
+		The Account Flags parameters are documented in the <command>pdbedit</command> man page, and are
+		briefly documented in <link linkend="TOSHARG-acctflags">the Account Flags Management section</link>.
+		</para>
+
+		<para>
+<indexterm><primary>last change time</primary></indexterm>
+		The LCT data consists of 8 hexadecimal characters representing the time since January 1, 1970, of
+		the time when the password was last changed.
+		</para>
+
+		</sect4>
+
+		<sect4>
+		<title>Adding User Accounts</title>
+
+		<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>add a user account</primary></indexterm>
+<indexterm><primary>standalone server</primary></indexterm>
+<indexterm><primary>domain</primary></indexterm>
+<indexterm><primary>SambaSAMAccount</primary></indexterm>
+		The <command>pdbedit</command> can be used to add a user account to a standalone server
+		or to a domain. In the example shown here the account for the user <literal>vlaan</literal>
+		has been created before attempting to add the SambaSAMAccount.
+<screen>
+&rootprompt; pdbedit -a vlaan
+new password: secretpw
+retype new password: secretpw
+Unix username:        vlaan
+NT username:          vlaan
+Account Flags:        [U          ]
+User SID:             S-1-5-21-726309263-4128913605-1168186429-3014
+Primary Group SID:    S-1-5-21-726309263-4128913605-1168186429-513
+Full Name:            Victor Laan
+Home Directory:       \\frodo\vlaan
+HomeDir Drive:        H:
+Logon Script:         scripts\logon.bat
+Profile Path:         \\frodo\profiles\vlaan
+Domain:               &example.workgroup;
+Account desc:         Guest User
+Workstations:
+Munged dial:
+Logon time:           0
+Logoff time:          Mon, 18 Jan 2038 20:14:07 GMT
+Kickoff time:         Mon, 18 Jan 2038 20:14:07 GMT
+Password last set:    Wed, 29 Jun 2005 19:35:12 GMT
+Password can change:  Wed, 29 Jun 2005 19:35:12 GMT
+Password must change: Mon, 18 Jan 2038 20:14:07 GMT
+Last bad password   : 0
+Bad password count  : 0
+Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
+</screen>
+		</para>
+
+		</sect4>
+
+		<sect4>
+		<title>Deleting Accounts</title>
+
+		<para>
+<indexterm><primary>account deleted</primary></indexterm>
+<indexterm><primary>SambaSAMAccount</primary></indexterm>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+		An account can be deleted from the SambaSAMAccount database
+<screen>
+&rootprompt; pdbedit -x vlaan
+</screen>
+		The account is removed without further screen output. The account is removed only from the
+		SambaSAMAccount (passdb backend) database, it is not removed from the UNIX account backend.
+		</para>
+
+		<para>
+<indexterm><primary>delete user script</primary></indexterm>
+<indexterm><primary>pdbedit</primary></indexterm>
+		The use of the NT4 domain user manager to delete an account will trigger the <parameter>delete user
+		script</parameter>, but not the <command>pdbedit</command> tool.
+		</para>
+
+		</sect4>
+
+		<sect4>
+		<title>Changing User Accounts</title>
+
+		<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+		Refer to the <command>pdbedit</command> man page for a full synopsis of all operations
+		that are available with this tool.
+		</para>
+
+		<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+		An example of a simple change in the user account information is the change of the full name
+		information shown here:
+<screen>
+&rootprompt; pdbedit -r --fullname="Victor Aluicious Laan" vlaan
+...
+Primary Group SID:    S-1-5-21-726309263-4128913605-1168186429-513
+Full Name:            Victor Aluicious Laan
+Home Directory:       \\frodo\vlaan
+...
+</screen>
+		</para>
+
+		<para>
+<indexterm><primary>grace time</primary></indexterm>
+<indexterm><primary>password expired</primary></indexterm>
+<indexterm><primary>expired password</primary></indexterm>
+		Let us assume for a moment that a user's password has expired and the user is unable to
+		change the password at this time. It may be necessary to give the user additional grace time
+		so that it is possible to continue to work with the account and the original password. This
+		demonstrates how the password expiration settings may be updated
+<screen>
+&rootprompt; pdbedit -Lv vlaan
+...
+Password last set:    Sun, 09 Sep 2001 22:21:40 GMT
+Password can change:  Thu, 03 Jan 2002 15:08:35 GMT
+Password must change: Thu, 03 Jan 2002 15:08:35 GMT
+Last bad password   : Thu, 03 Jan 2002 15:08:35 GMT
+Bad password count  : 2
+...
+</screen>
+<indexterm><primary>bad logon attempts</primary></indexterm>
+<indexterm><primary>lock the account</primary></indexterm>
+		The user has recorded 2 bad logon attempts and the next will lock the account, but the
+		password is also expired. Here is how this account can be reset:
+<screen>
+&rootprompt; pdbedit -z vlaan
+...
+Password last set:    Sun, 09 Sep 2001 22:21:40 GMT
+Password can change:  Thu, 03 Jan 2002 15:08:35 GMT
+Password must change: Thu, 03 Jan 2002 15:08:35 GMT
+Last bad password   : 0
+Bad password count  : 0
+...
+</screen>
+		The <literal>Password must change:</literal> parameter can be reset like this:
+<screen>
+&rootprompt; pdbedit --pwd-must-change-time=1200000000 vlaan
+...
+Password last set:    Sun, 09 Sep 2001 22:21:40 GMT
+Password can change:  Thu, 03 Jan 2002 15:08:35 GMT
+Password must change: Thu, 10 Jan 2008 14:20:00 GMT
+...
+</screen>
+		Another way to use this tools is to set the date like this:
+<screen>
+&rootprompt; pdbedit --pwd-must-change-time="2010-01-01" \
+              --time-format="%Y-%m-%d" vlaan
+...
+Password last set:    Sun, 09 Sep 2001 22:21:40 GMT
+Password can change:  Thu, 03 Jan 2002 15:08:35 GMT
+Password must change: Fri, 01 Jan 2010 00:00:00 GMT
+...
+</screen>
+<indexterm><primary>strptime</primary></indexterm>
+<indexterm><primary>time format</primary></indexterm>
+		Refer to the strptime man page for specific time format information.
+		</para>
+
+		<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>SambaSAMAccount</primary></indexterm>
+		Please refer to the pdbedit man page for further information relating to SambaSAMAccount
+		management.
+		</para>
+
+		<sect5 id="TOSHARG-acctflags">
+		<title>Account Flags Management</title>
+
+		<para>
+<indexterm><primary>Samba SAM account flags</primary></indexterm>
+<indexterm><primary>account control block</primary><see>ACB</see></indexterm>
+<indexterm><primary>account encode_bits</primary></indexterm>
+<indexterm><primary>account control flags</primary></indexterm>
+		The Samba SAM account flags are properly called the ACB (account control block) within
+		the Samba source code. In some parts of the Samba source code they are referred to as the
+		account encode_bits, and also as the account control flags.
+		</para>
+
+		<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>user account</primary></indexterm>
+<indexterm><primary>machine account</primary></indexterm>
+<indexterm><primary>trust account</primary></indexterm>
+<indexterm><primary>damaged data</primary></indexterm>
+		The manual adjustment of user, machine (workstation or server) or an inter-domain trust
+		account account flgas should not be necessary under normal conditions of use of Samba. On the other hand,
+		where this information becomes corrupted for some reason, the ability to correct the damaged data is certainly
+		useful. The tool of choice by which such correction can be affected is the <command>pdbedit</command> utility.
+		</para>
+
+		<para>
+<indexterm><primary>account flags</primary></indexterm>
+<indexterm><primary>LDAP directory</primary></indexterm>
+		There have been a few requests for information regarding the account flags from developers
+		who are creating their own Samba management tools. An example of a need for information regarding
+		the proper management of the account flags is evident when developing scripts that will be used
+		to manage an LDAP directory.
+		</para>
+
+		<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>account flag order</primary></indexterm>
+		The account flag field can contain up to 16 characters. Presently, only 11 are in use.
+		These are listed in <link linkend="accountflags">Samba SAM Account Control Block Flags</link>.
+		The order in which the flags are specified to the <command>pdbedit</command> command is not important.
+		In fact, they can be set without problem in any order in the SambaAcctFlags record in the LDAP directory.
+		</para>
+
+		<table frame="all" id="accountflags">
+		<title>Samba SAM Account Control Block Flags</title>
+        <tgroup cols="2" align="center">
+            <thead>
+            <row><entry align="center">Flag</entry><entry>Description</entry></row>
+            </thead>
+            <tbody>
+            <row>
+				<entry align="center">D</entry>
+				<entry align="left">Account is disabled.</entry>
+			</row>
+            <row>
+				<entry align="center">H</entry>
+				<entry align="left">A home directory is required.</entry>
+			</row>
+            <row>
+				<entry align="center">I</entry>
+				<entry align="left">An inter-domain trust account.</entry>
+			</row>
+            <row>
+				<entry align="center">L</entry>
+				<entry align="left">Account has been auto-locked.</entry>
+			</row>
+            <row>
+				<entry align="center">M</entry>
+				<entry align="left">An MNS (Microsoft network service) logon account.</entry>
+			</row>
+            <row>
+				<entry align="center">N</entry>
+				<entry align="left">Password not required.</entry>
+			</row>
+            <row>
+				<entry align="center">S</entry>
+				<entry align="left">A server trust account.</entry>
+			</row>
+            <row>
+				<entry align="center">T</entry>
+				<entry align="left">Temporary duplicate account entry.</entry>
+			</row>
+            <row>
+				<entry align="center">U</entry>
+				<entry align="left">A normal user account.</entry>
+			</row>
+            <row>
+				<entry align="center">W</entry>
+				<entry align="left">A workstation trust account.</entry>
+			</row>
+            <row>
+				<entry align="center">X</entry>
+				<entry align="left">Password does not expire.</entry>
+			</row>
+            </tbody>
+        </tgroup>
+        </table>
+
+		<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>account control flags</primary></indexterm>
+		An example of use of the <command>pdbedit</command> utility to set the account control flags
+		is shown here:
+<screen>
+&rootprompt; pdbedit -r -c "[DLX]" jht
+Unix username:        jht
+NT username:          jht
+Account Flags:        [DHULX      ]
+User SID:             S-1-5-21-729263-4123605-1186429-3000
+Primary Group SID:    S-1-5-21-729263-4123605-1186429-513
+Full Name:            John H Terpstra,Utah Office
+Home Directory:       \\aurora\jht
+HomeDir Drive:        H:
+Logon Script:         scripts\logon.bat
+Profile Path:         \\aurora\profiles\jht
+Domain:               MIDEARTH
+Account desc:         BluntObject
+Workstations:
+Logon time:           0
+Logoff time:          Mon, 18 Jan 2038 20:14:07 GMT
+Kickoff time:         0
+Password last set:    Sun, 03 Jul 2005 23:19:18 GMT
+Password can change:  Sun, 03 Jul 2005 23:19:18 GMT
+Password must change: Mon, 18 Jan 2038 20:14:07 GMT
+Last bad password   : 0
+Bad password count  : 0
+Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
+</screen>
+<indexterm><primary>default settings</primary></indexterm>
+	The flags can be reset to the default settings by executing:
+<screen>
+&rootprompt; pdbedit -r -c "[]" jht
+Unix username:        jht
+NT username:          jht
+Account Flags:        [U          ]
+User SID:             S-1-5-21-729263-4123605-1186429-3000
+Primary Group SID:    S-1-5-21-729263-4123605-1186429-513
+Full Name:            John H Terpstra,Utah Office
+Home Directory:       \\aurora\jht
+HomeDir Drive:        H:
+Logon Script:         scripts\logon.bat
+Profile Path:         \\aurora\profiles\jht
+Domain:               MIDEARTH
+Account desc:         BluntObject
+Workstations:
+Logon time:           0
+Logoff time:          Mon, 18 Jan 2038 20:14:07 GMT
+Kickoff time:         0
+Password last set:    Sun, 03 Jul 2005 23:19:18 GMT
+Password can change:  Sun, 03 Jul 2005 23:19:18 GMT
+Password must change: Mon, 18 Jan 2038 20:14:07 GMT
+Last bad password   : 0
+Bad password count  : 0
+Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
+</screen>
+		</para>
+
+		</sect5>
+
+		</sect4>
+
+		<sect4>
+		<title>Domain Account Policy Managment</title>
+
+		<para>
+<indexterm><primary>domain account access policies</primary></indexterm>
+<indexterm><primary>access policies</primary></indexterm>
+		To view the domain account access policies that may be configured execute:
+<screen>
+&rootprompt; pdbedit -P ?
+No account policy by that name
+Account policy names are :
+min password length
+password history
+user must logon to change password
+maximum password age
+minimum password age
+lockout duration
+reset count minutes
+bad lockout attempt
+disconnect time
+refuse machine password change
+</screen>
+		</para>
+
+		<para>
+		Commands will be executed to establish controls for our domain as follows:
+		</para>
+
+		<orderedlist>
+			<listitem><para>min password length = 8 characters.</para></listitem>
+			<listitem><para>password history = last 4 passwords.</para></listitem>
+			<listitem><para>maximum password age = 90 days.</para></listitem>
+			<listitem><para>minimum password age = 7 days.</para></listitem>
+			<listitem><para>bad lockout attempt = 8 bad logon attempts.</para></listitem>
+			<listitem><para>lockout duration = forever, account must be manually reenabled.</para></listitem>
+		</orderedlist>
+
+		<para>
+		The following command execution will achieve these settings:
+<screen>
+&rootprompt; pdbedit -P "min password length" -C 8
+account policy value for min password length was 5
+account policy value for min password length is now 8
+&rootprompt; pdbedit -P "password history" -C 4
+account policy value for password history was 0
+account policy value for password history is now 4
+&rootprompt; pdbedit -P "maximum password age" -C 7776000
+account policy value for maximum password age was 4294967295
+account policy value for maximum password age is now 7776000
+&rootprompt; pdbedit -P "minimum password age" -C 7
+account policy value for minimum password age was 0
+account policy value for minimum password age is now 7
+&rootprompt; pdbedit -P "bad lockout attempt" -C 8
+account policy value for bad lockout attempt was 0
+account policy value for bad lockout attempt is now 8
+&rootprompt; pdbedit -P "lockout duration" -C -1
+account policy value for lockout duration was 30
+account policy value for lockout duration is now 4294967295
+</screen>
+		</para>
+
+<note><para>
+To set the maximum (infinite) lockout time use the value of -1.
+</para></note>
+
+<warning><para>
+Account policies must be set individually on each PDC and BDC. At this time (Samba 3.0.11 to Samba 3.0.14a)
+account policies are not replicated automatically. This may be fixed before Samba 3.0.20 ships or some
+time there after. Please check the WHATSNEW.txt file in the Samba-3 tarball for specific update notiations
+regarding this facility.
+</para></warning>
+
+		</sect4>
+
+		</sect3>
+
+		<sect3>
+		<title>Account Import/Export</title>
+
+		<para>
+		<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>account import/export</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+		The <command>pdbedit</command> tool allows import/export of authentication (account)
+		databases from one backend to another. For example, to import/export accounts from an
+		old <filename>smbpasswd</filename> database to a <parameter>tdbsam</parameter>
+		backend:
+		</para>
+
+		<procedure>
+			<step><para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<screen>
+&rootprompt;<userinput>pdbedit -i smbpasswd -e tdbsam</userinput>
+</screen>
+			</para></step>
+
+			<step><para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+			Replace the <parameter>smbpasswd</parameter> with <parameter>tdbsam</parameter> in the
+			<parameter>passdb backend</parameter> configuration in &smb.conf;.
+			</para></step>
+		</procedure>
+
+	</sect3>
+	</sect2>
+</sect1>
+
+<sect1>
+<title>Password Backends</title>
+
+<para>
+<indexterm><primary>account database</primary></indexterm>
+<indexterm><primary>SMB/CIFS server</primary></indexterm>
+Samba offers flexibility in backend account database design. The flexibility is immediately obvious as one
+begins to explore this capability. Recent changes to Samba (since 3.0.23) have removed the mulitple backend
+feature in order to simplify problems that broke some installations. This removal has made the internal
+operation of Samba-3 more consistent and predictable.
+</para>
+
+<para>
+<indexterm><primary>multiple backends</primary></indexterm>
+<indexterm><primary>tdbsam databases</primary></indexterm>
+Beginning with Samba 3.0.23 it is no longer possible to specify use of mulitple passdb backends. Earlier
+versions of Samba-3 made it possible to specify multiple password backends, and even multiple
+backends of the same type. The multiple passdb backend capability caused many problems with name to SID and
+SID to name ID resolution.  The Samba team wrestled with the challenges and decided that this feature needed
+to be removed.
+</para>
+
+	<sect2>
+	<title>Plaintext</title>
+
+		<para>
+<indexterm><primary>user database</primary></indexterm>
+<indexterm><primary>/etc/samba/smbpasswd</primary></indexterm>
+<indexterm><primary>/etc/smbpasswd</primary></indexterm>
+<indexterm><primary>password encryption</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>PAM</primary></indexterm>
+		Older versions of Samba retrieved user information from the UNIX user database
+		and eventually some other fields from the file <filename>/etc/samba/smbpasswd</filename>
+		or <filename>/etc/smbpasswd</filename>. When password encryption is disabled, no
+		SMB-specific data is stored at all. Instead, all operations are conducted via the way
+		that the Samba host OS will access its <filename>/etc/passwd</filename> database.
+		On most Linux systems, for example, all user and group resolution is done via PAM.
+		</para>
+
+	</sect2>
+
+	<sect2>
+	<title>smbpasswd: Encrypted Password Database</title>
+
+		<para>
+		<indexterm><primary>SAM backend</primary><secondary>smbpasswd</secondary></indexterm>
+<indexterm><primary>user account</primary></indexterm>
+<indexterm><primary>LM/NT password hashes</primary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+		Traditionally, when configuring <smbconfoption name="encrypt passwords">yes</smbconfoption>
+		in Samba's &smb.conf; file, user account information such as username, LM/NT password hashes,
+		password change times, and account flags have been stored in the <filename>smbpasswd(5)</filename>
+		file. There are several disadvantages to this approach for sites with large numbers of users
+		(counted in the thousands).
+		</para>
+
+		<itemizedlist>
+		<listitem><para>
+<indexterm><primary>lookups</primary></indexterm>
+		The first problem is that all lookups must be performed sequentially. Given that
+		there are approximately two lookups per domain logon (one during intial logon validation
+		and one for a session connection setup, such as when mapping a network drive or printer), this
+		is a performance bottleneck for large sites. What is needed is an indexed approach
+		such as that used in databases.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>replicate</primary></indexterm>
+<indexterm><primary>rsync</primary></indexterm>
+<indexterm><primary>ssh</primary></indexterm>
+<indexterm><primary>custom scripts</primary></indexterm>
+		The second problem is that administrators who desire to replicate an smbpasswd file
+		to more than one Samba server are left to use external tools such as
+		<command>rsync(1)</command> and <command>ssh(1)</command> and write custom,
+		in-house scripts.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>home directory</primary></indexterm>
+<indexterm><primary>password expiration</primary></indexterm>
+<indexterm><primary>relative identifier</primary></indexterm>
+<indexterm><primary>relative identifier</primary><see>RID</see></indexterm>
+		Finally, the amount of information that is stored in an smbpasswd entry leaves
+		no room for additional attributes such as a home directory, password expiration time,
+		or even a relative identifier (RID).
+		</para></listitem>
+		</itemizedlist>
+
+		<para>
+<indexterm><primary>user attributes</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>API</primary></indexterm>
+<indexterm><primary>samdb interface</primary></indexterm>
+		As a result of these deficiencies, a more robust means of storing user attributes
+		used by smbd was developed. The API that defines access to user accounts
+		is commonly referred to as the samdb interface (previously, this was called the passdb
+		API and is still so named in the Samba source code trees).
+		</para>
+
+		<para>
+<indexterm><primary>passdb backends</primary></indexterm>
+<indexterm><primary>smbpasswd plaintext database</primary></indexterm>
+<indexterm><primary>tdbsam</primary></indexterm>
+<indexterm><primary>ldapsam</primary></indexterm>
+<indexterm><primary>enterprise</primary></indexterm>
+		Samba provides an enhanced set of passdb backends that overcome the deficiencies
+		of the smbpasswd plaintext database. These are tdbsam and ldapsam.
+		Of these, ldapsam will be of most interest to large corporate or enterprise sites.
+		</para>
+
+	</sect2>
+
+	<sect2>
+	<title>tdbsam</title>
+
+		<para>
+		<indexterm><primary>SAM backend</primary><secondary>tdbsam</secondary></indexterm>
+<indexterm><primary>trivial database</primary><see>TDB</see></indexterm>
+<indexterm><primary>machine account</primary></indexterm>
+		Samba can store user and machine account data in a <quote>TDB</quote> (trivial database).
+		Using this backend does not require any additional configuration. This backend is
+		recommended for new installations that do not require LDAP.
+		</para>
+
+		<para>
+<indexterm><primary>tdbsam</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>scalability</primary></indexterm>
+		As a general guide, the Samba Team does not recommend using the tdbsam backend for sites
+		that have 250 or more users. Additionally, tdbsam is not capable of scaling for use
+		in sites that require PDB/BDC implementations that require replication of the account
+		database. Clearly, for reason of scalability, the use of ldapsam should be encouraged.
+		</para>
+
+		<para>
+<indexterm><primary>250-user limit</primary></indexterm>
+<indexterm><primary>performance-based</primary></indexterm>
+<indexterm><primary>tdbsam</primary></indexterm>
+		The recommendation of a 250-user limit is purely based on the notion that this
+		would generally involve a site that has routed networks, possibly spread across
+		more than one physical location. The Samba Team has not at this time established
+		the performance-based scalability limits of the tdbsam architecture.
+		</para>
+
+		<para>
+<indexterm><primary>4,500 user accounts</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>tdbsam</primary></indexterm>
+<indexterm><primary>SambaSAMAccount</primary></indexterm>
+		There are sites that have thousands of users and yet require only one server.
+		One site recently reported having 4,500 user accounts on one UNIX system and
+		reported excellent performance with the <literal>tdbsam</literal> passdb backend.
+		The limitation of where the <literal>tdbsam</literal> passdb backend can be used
+		is not one pertaining to a limitation in the TDB storage system, it is based
+		only on the need for a reliable distribution mechanism for the SambaSAMAccount
+		backend.
+		</para>
+
+	</sect2>
+
+	<sect2>
+	<title>ldapsam</title>
+
+		<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>ldapsam</primary></indexterm>
+		<indexterm><primary>SAM backend</primary><secondary>ldapsam</secondary></indexterm>
+		There are a few points to stress that the ldapsam does not provide. The LDAP
+		support referred to in this documentation does not include:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>A means of retrieving user account information from
+			a Windows 200x Active Directory server.</para></listitem>
+			<listitem><para>A means of replacing /etc/passwd.</para></listitem>
+		</itemizedlist>
+
+		<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>LGPL</primary></indexterm>
+		The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be
+		obtained from <ulink url="http://www.padl.com/">PADL Software</ulink>.  More information about the
+		configuration of these packages may be found in <ulink url="http://safari.oreilly.com/?XmlId=1-56592-491-6">
+		<emphasis>LDAP, System Administration</emphasis> by Gerald Carter, Chapter 6, Replacing NIS"</ulink>.
+		</para>
+
+		<para>
+<indexterm><primary>LDAP directory</primary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>directory server</primary></indexterm>
+		This document describes how to use an LDAP directory for storing Samba user
+		account information traditionally stored in the smbpasswd(5) file. It is
+		assumed that the reader already has a basic understanding of LDAP concepts
+		and has a working directory server already installed. For more information
+		on LDAP architectures and directories, please refer to the following sites:
+		</para>
+
+		<itemizedlist>
+			<listitem><para><ulink url="http://www.openldap.org/">OpenLDAP</ulink></para></listitem>
+			<listitem><para><ulink url="http://www.sun.com/software/products/directory_srvr_ee/index.xml">
+				Sun One Directory Server</ulink></para></listitem>
+			<listitem><para><ulink url="http://www.novell.com/products/edirectory/">Novell eDirectory</ulink></para></listitem>
+			<listitem><para><ulink url="http://www-306.ibm.com/software/tivoli/products/directory-server/">IBM
+				Tivoli Directory Server</ulink></para></listitem>
+			<listitem><para><ulink url="http://www.redhat.com/software/rha/directory/">Red Hat Directory
+				Server</ulink></para></listitem>
+			<listitem><para><ulink url="http://www.linuxsecurity.com/content/view/119229">Fedora Directory
+				Server</ulink></para></listitem>
+		</itemizedlist>
+
+		<para>
+		Two additional Samba resources that may prove to be helpful are:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+<indexterm><primary>Samba-PDC-LDAP-HOWTO</primary></indexterm>
+			The <ulink url="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html">Samba-PDC-LDAP-HOWTO</ulink>
+			maintained by Ignacio Coupeau.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>IDEALX</primary></indexterm>
+<indexterm><primary>NT migration scripts</primary></indexterm>
+<indexterm><primary>smbldap-tools</primary></indexterm>
+			The NT migration scripts from <ulink url="http://samba.idealx.org/">IDEALX</ulink> that are
+			geared to manage users and groups in such a Samba-LDAP domain controller configuration.
+			Idealx also produced the smbldap-tools and the Interactive Console Management tool.
+			</para></listitem>
+		</itemizedlist>
+
+		<sect3>
+		<title>Supported LDAP Servers</title>
+
+			<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>ldapsam</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>Netscape's Directory Server</primary></indexterm>
+			The LDAP ldapsam code was developed and tested using the OpenLDAP 2.x server and
+			client libraries. The same code should work with Netscape's Directory Server and client SDK.
+			However, there are bound to be compile errors and bugs. These should not be hard to fix.
+			Please submit fixes via the process outlined in <link linkend="bugreport">Reporting Bugs</link>.
+			</para>
+
+			<para>
+			Samba is capable of working with any standards-compliant LDAP server.
+			</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Schema and Relationship to the RFC 2307 posixAccount</title>
+
+
+			<para>
+			Samba-3.0 includes the necessary schema file for OpenLDAP 2.x in the
+			<filename>examples/LDAP/samba.schema</filename> directory of the source code distribution
+			tarball. The schema entry for the sambaSamAccount ObjectClass is shown here:
+<programlisting>
+ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
+    DESC 'Samba-3.0 Auxiliary SAM Account'
+    MUST ( uid $ sambaSID )
+    MAY  ( cn $ sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $
+          sambaLogonTime $ sambaLogoffTime $ sambaKickoffTime $
+          sambaPwdCanChange $ sambaPwdMustChange $ sambaAcctFlags $
+          displayName $ sambaHomePath $ sambaHomeDrive $ sambaLogonScript $
+          sambaProfilePath $ description $ sambaUserWorkstations $
+          sambaPrimaryGroupSID $ sambaDomainName ))
+</programlisting>
+			</para>
+
+			<para>
+<indexterm><primary>samba.schema</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>OID</primary></indexterm>
+			The <filename>samba.schema</filename> file has been formatted for OpenLDAP 2.0/2.1.
+			The Samba Team owns the OID space used by the above schema and recommends its use.
+			If you translate the schema to be used with Netscape DS, please submit the modified
+			schema file as a patch to <ulink url="mailto:jerry@samba.org">jerry@samba.org</ulink>.
+			</para>
+
+			<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+<indexterm><primary>AUXILIARY</primary></indexterm>
+<indexterm><primary>ObjectClass</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>RFC 2307.</primary></indexterm>
+			Just as the smbpasswd file is meant to store information that provides information
+			additional to  a user's <filename>/etc/passwd</filename> entry, so is the sambaSamAccount
+			object meant to supplement the UNIX user account information. A sambaSamAccount is an
+			<constant>AUXILIARY</constant> ObjectClass, so it can be used to augment existing
+			user account information in the LDAP directory, thus providing information needed
+			for Samba account handling. However, there are several fields (e.g., uid) that overlap
+			with the posixAccount ObjectClass outlined in RFC 2307. This is by design.
+			</para>
+
+			<para>
+<indexterm><primary>account information</primary></indexterm>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+<indexterm><primary>posixAccount</primary></indexterm>
+<indexterm><primary>ObjectClasses</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>getpwnam</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>NIS</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+			In order to store all user account information (UNIX and Samba) in the directory,
+			it is necessary to use the sambaSamAccount and posixAccount ObjectClasses in
+			combination. However, <command>smbd</command> will still obtain the user's UNIX account
+			information via the standard C library calls, such as getpwnam().
+			This means that the Samba server must also have the LDAP NSS library installed
+			and functioning correctly. This division of information makes it possible to
+			store all Samba account information in LDAP, but still maintain UNIX account
+			information in NIS while the network is transitioning to a full LDAP infrastructure.
+			</para>
+		</sect3>
+
+		<sect3>
+		<title>OpenLDAP Configuration</title>
+
+		<para>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+<indexterm><primary>OpenLDAP</primary></indexterm>
+<indexterm><primary>slapd</primary></indexterm>
+<indexterm><primary>samba.schema</primary></indexterm>
+		To include support for the sambaSamAccount object in an OpenLDAP directory
+		server, first copy the samba.schema file to slapd's configuration directory.
+		The samba.schema file can be found in the directory <filename>examples/LDAP</filename>
+		in the Samba source distribution.
+<screen>
+&rootprompt;<userinput>cp samba.schema /etc/openldap/schema/</userinput>
+</screen>
+		</para>
+
+		<para>
+<indexterm><primary>samba.schema</primary></indexterm>
+<indexterm><primary>slapd.conf</primary></indexterm>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+<indexterm><primary>cosine.schema</primary></indexterm>
+<indexterm><primary>uid</primary></indexterm>
+<indexterm><primary>inetorgperson.schema</primary></indexterm>
+<indexterm><primary>displayName</primary></indexterm>
+<indexterm><primary>attribute</primary></indexterm>
+		Next, include the <filename>samba.schema</filename> file in <filename>slapd.conf</filename>.
+		The sambaSamAccount object contains two attributes that depend on other schema
+		files. The <parameter>uid</parameter> attribute is defined in <filename>cosine.schema</filename> and
+		the <parameter>displayName</parameter> attribute is defined in the <filename>inetorgperson.schema</filename>
+		file. Both of these must be included before the <filename>samba.schema</filename> file.
+<programlisting>
+## /etc/openldap/slapd.conf
+
+## schema files (core.schema is required by default)
+include	           /etc/openldap/schema/core.schema
+
+## needed for sambaSamAccount
+include            /etc/openldap/schema/cosine.schema
+include            /etc/openldap/schema/inetorgperson.schema
+include            /etc/openldap/schema/nis.schema
+include            /etc/openldap/schema/samba.schema
+....
+</programlisting>
+		</para>
+
+		<para>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+<indexterm><primary>posixAccount</primary></indexterm>
+<indexterm><primary>posixGroup</primary></indexterm>
+<indexterm><primary>ObjectClasses</primary></indexterm>
+		It is recommended that you maintain some indices on some of the most useful attributes,
+		as in the following example, to speed up searches made on sambaSamAccount ObjectClasses
+		(and possibly posixAccount and posixGroup as well):
+		</para>
+
+<para>
+<programlisting>
+# Indices to maintain
+## required by OpenLDAP
+index objectclass             eq
+
+index cn                      pres,sub,eq
+index sn                      pres,sub,eq
+## required to support pdb_getsampwnam
+index uid                     pres,sub,eq
+## required to support pdb_getsambapwrid()
+index displayName             pres,sub,eq
+
+## uncomment these if you are storing posixAccount and
+## posixGroup entries in the directory as well
+##index uidNumber               eq
+##index gidNumber               eq
+##index memberUid               eq
+
+index   sambaSID              eq
+index   sambaPrimaryGroupSID  eq
+index   sambaDomainName       eq
+index   default               sub
+</programlisting>
+</para>
+
+		<para>
+		Create the new index by executing:
+<screen>
+&rootprompt;./sbin/slapindex -f slapd.conf
+</screen>
+		</para>
+
+		<para>
+		Remember to restart slapd after making these changes:
+<screen>
+&rootprompt;<userinput>/etc/init.d/slapd restart</userinput>
+</screen>
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Initialize the LDAP Database</title>
+
+		<para>
+<indexterm><primary>LDAP database</primary></indexterm>
+<indexterm><primary>account containers</primary></indexterm>
+<indexterm><primary>LDIF file</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+		Before you can add accounts to the LDAP database, you must create the account containers
+		that they will be stored in. The following LDIF file should be modified to match your
+		needs (DNS entries, and so on):
+<programlisting>
+# Organization for Samba Base
+dn: dc=quenya,dc=org
+objectclass: dcObject
+objectclass: organization
+dc: quenya
+o: Quenya Org Network
+description: The Samba-3 Network LDAP Example
+
+# Organizational Role for Directory Management
+dn: cn=Manager,dc=quenya,dc=org
+objectclass: organizationalRole
+cn: Manager
+description: Directory Manager
+
+# Setting up container for Users OU
+dn: ou=People,dc=quenya,dc=org
+objectclass: top
+objectclass: organizationalUnit
+ou: People
+
+# Setting up admin handle for People OU
+dn: cn=admin,ou=People,dc=quenya,dc=org
+cn: admin
+objectclass: top
+objectclass: organizationalRole
+objectclass: simpleSecurityObject
+userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
+
+# Setting up container for groups
+dn: ou=Groups,dc=quenya,dc=org
+objectclass: top
+objectclass: organizationalUnit
+ou: Groups
+
+# Setting up admin handle for Groups OU
+dn: cn=admin,ou=Groups,dc=quenya,dc=org
+cn: admin
+objectclass: top
+objectclass: organizationalRole
+objectclass: simpleSecurityObject
+userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
+
+# Setting up container for computers
+dn: ou=Computers,dc=quenya,dc=org
+objectclass: top
+objectclass: organizationalUnit
+ou: Computers
+
+# Setting up admin handle for Computers OU
+dn: cn=admin,ou=Computers,dc=quenya,dc=org
+cn: admin
+objectclass: top
+objectclass: organizationalRole
+objectclass: simpleSecurityObject
+userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
+</programlisting>
+		</para>
+
+		<para>
+<indexterm><primary>userPassword</primary></indexterm>
+<indexterm><primary>slappasswd</primary></indexterm>
+		The userPassword shown above should be generated using <command>slappasswd</command>.
+		</para>
+
+		<para>
+<indexterm><primary>LDIF</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+		The following command will then load the contents of the LDIF file into the LDAP
+		database.
+<indexterm><primary>slapadd</primary></indexterm>
+<screen>
+&prompt;<userinput>slapadd -v -l initldap.dif</userinput>
+</screen>
+		</para>
+
+		<para>
+		Do not forget to secure your LDAP server with an adequate access control list
+		as well as an admin password.
+		</para>
+
+		<note><para>
+<indexterm><primary>secrets.tdb</primary></indexterm>
+		Before Samba can access the LDAP server, you need to store the LDAP admin password
+		in the Samba-3 <filename>secrets.tdb</filename> database by:
+<indexterm><primary>smbpasswd</primary></indexterm>
+<screen>
+&rootprompt;<userinput>smbpasswd -w <replaceable>secret</replaceable></userinput>
+</screen>
+		</para></note>
+
+		</sect3>
+
+		<sect3>
+		<title>Configuring Samba</title>
+
+			<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+			The following parameters are available in &smb.conf; only if your version of Samba was built with
+			LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. The
+			best method to verify that Samba was built with LDAP support is:
+<screen>
+&rootprompt; smbd -b | grep LDAP
+   HAVE_LDAP_H
+   HAVE_LDAP
+   HAVE_LDAP_DOMAIN2HOSTLIST
+   HAVE_LDAP_INIT
+   HAVE_LDAP_INITIALIZE
+   HAVE_LDAP_SET_REBIND_PROC
+   HAVE_LIBLDAP
+   LDAP_SET_REBIND_PROC_ARGS
+</screen>
+			If the build of the <command>smbd</command> command you are using does not produce output
+			that includes <literal>HAVE_LDAP_H</literal> it is necessary to discover why the LDAP headers
+			and libraries were not found during compilation.
+			</para>
+
+			<para>LDAP-related smb.conf options include these:
+			<smbconfblock>
+			<smbconfoption name="passdb backend">ldapsam:url</smbconfoption>
+			<smbconfoption name="ldap admin dn"/>
+			<smbconfoption name="ldap delete dn"/>
+			<smbconfoption name="ldap filter"/>
+			<smbconfoption name="ldap group suffix"/>
+			<smbconfoption name="ldap idmap suffix"/>
+			<smbconfoption name="ldap machine suffix"/>
+			<smbconfoption name="ldap passwd sync"/>
+			<smbconfoption name="ldap ssl"/>
+			<smbconfoption name="ldap suffix"/>
+			<smbconfoption name="ldap user suffix"/>
+			<smbconfoption name="ldap replication sleep"/>
+			<smbconfoption name="ldap timeout"/>
+			<smbconfoption name="ldap page size"/>
+			</smbconfblock>
+			</para>
+
+			<para>
+			These are described in the &smb.conf; man page and so are not repeated here. However, an example
+			for use with an LDAP directory is shown in <link linkend="confldapex">the Configuration with LDAP.</link>
+			</para>
+
+<example id="confldapex">
+<title>Configuration with LDAP</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="security">user</smbconfoption>
+<smbconfoption name="encrypt passwords">yes</smbconfoption>
+<smbconfoption name="netbios name">MORIA</smbconfoption>
+<smbconfoption name="workgroup">NOLDOR</smbconfoption>
+
+<smbconfcomment>LDAP related parameters:</smbconfcomment>
+
+<smbconfcomment>Define the DN used when binding to the LDAP servers.</smbconfcomment>
+<smbconfcomment>The password for this DN is not stored in smb.conf</smbconfcomment>
+<smbconfcomment>Set it using 'smbpasswd -w secret' to store the</smbconfcomment>
+<smbconfcomment>passphrase in the secrets.tdb file.</smbconfcomment>
+<smbconfcomment>If the "ldap admin dn" value changes, it must be reset.</smbconfcomment>
+<smbconfoption name="ldap admin dn">"cn=Manager,dc=quenya,dc=org"</smbconfoption>
+
+<smbconfcomment>SSL directory connections can be configured by:</smbconfcomment>
+<smbconfcomment>('off', 'start tls', or 'on' (default))</smbconfcomment>
+<smbconfoption name="ldap ssl">start tls</smbconfoption>
+
+<smbconfcomment>syntax: passdb backend = ldapsam:ldap://server-name[:port]</smbconfcomment>
+<smbconfoption name="passdb backend">ldapsam:ldap://frodo.quenya.org</smbconfoption>
+
+<smbconfcomment>smbpasswd -x delete the entire dn-entry</smbconfcomment>
+<smbconfoption name="ldap delete dn">no</smbconfoption>
+
+<smbconfcomment>The machine and user suffix are added to the base suffix</smbconfcomment>
+<smbconfcomment>wrote WITHOUT quotes. NULL suffixes by default</smbconfcomment>
+<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
+<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
+<smbconfoption name="ldap machine suffix">ou=Computers</smbconfoption>
+
+<smbconfcomment>Trust UNIX account information in LDAP</smbconfcomment>
+<smbconfcomment> (see the smb.conf man page for details)</smbconfcomment>
+
+<smbconfcomment>Specify the base DN to use when searching the directory</smbconfcomment>
+<smbconfoption name="ldap suffix">dc=quenya,dc=org</smbconfoption>
+</smbconfblock>
+</example>
+
+		</sect3>
+
+		<sect3>
+		<title>Accounts and Groups Management</title>
+
+			<para>
+			<indexterm><primary>User Management</primary></indexterm>
+			<indexterm><primary>User Accounts</primary><secondary>Adding/Deleting</secondary></indexterm>
+			Because user accounts are managed through the sambaSamAccount ObjectClass, you should
+			modify your existing administration tools to deal with sambaSamAccount attributes.
+			</para>
+
+			<para>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+<indexterm><primary>/etc/openldap/sldap.conf</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+			Machine accounts are managed with the sambaSamAccount ObjectClass, just
+			like user accounts. However, it is up to you to store those accounts
+			in a different tree of your LDAP namespace. You should use
+			<quote>ou=Groups,dc=quenya,dc=org</quote> to store groups and
+			<quote>ou=People,dc=quenya,dc=org</quote> to store users. Just configure your
+			NSS and PAM accordingly (usually, in the <filename>/etc/openldap/sldap.conf</filename>
+			configuration file).
+			</para>
+
+			<para>
+<indexterm><primary>POSIX</primary></indexterm>
+<indexterm><primary>posixGroup</primary></indexterm>
+<indexterm><primary>Domain Groups</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+			In Samba-3, the group management system is based on POSIX
+			groups. This means that Samba makes use of the posixGroup ObjectClass.
+			For now, there is no NT-like group system management (global and local
+			groups). Samba-3 knows only about <constant>Domain Groups</constant>
+			and, unlike MS Windows 2000 and Active Directory, Samba-3 does not
+			support nested groups.
+			</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Security and sambaSamAccount</title>
+
+
+			<para>
+<indexterm><primary>sambaSAMAccount</primary></indexterm>
+			There are two important points to remember when discussing the security
+			of sambaSAMAccount entries in the directory.
+			</para>
+
+			<itemizedlist>
+				<listitem><para><emphasis>Never</emphasis> retrieve the SambaLMPassword or
+<indexterm><primary>SambaNTPassword</primary></indexterm>
+				SambaNTPassword attribute values over an unencrypted LDAP session.</para></listitem>
+				<listitem><para><emphasis>Never</emphasis> allow non-admin users to
+				view the SambaLMPassword or SambaNTPassword attribute values.</para></listitem>
+			</itemizedlist>
+
+			<para>
+<indexterm><primary>clear-text</primary></indexterm>
+<indexterm><primary>impersonate</primary></indexterm>
+<indexterm><primary>LM/NT password hashes</primary></indexterm>
+			These password hashes are clear-text equivalents and can be used to impersonate
+			the user without deriving the original clear-text strings. For more information
+			on the details of LM/NT password hashes, refer to <link linkend="passdb">the
+			Account Information Database section</link>.
+			</para>
+
+			<para>
+<indexterm><primary>encrypted session</primary></indexterm>
+<indexterm><primary>StartTLS</primary></indexterm>
+<indexterm><primary>LDAPS</primary></indexterm>
+<indexterm><primary>secure communications</primary></indexterm>
+			To remedy the first security issue, the <smbconfoption name="ldap ssl"/> &smb.conf;
+			parameter defaults to require an encrypted session (<smbconfoption name="ldap
+			ssl">on</smbconfoption>) using the default port of <constant>636</constant> when
+			contacting the directory server. When using an OpenLDAP server, it
+			is possible to use the StartTLS LDAP extended operation in the place of LDAPS.
+			In either case, you are strongly encouraged to use secure communications protocols
+			(so do not set <smbconfoption name="ldap ssl">off</smbconfoption>).
+			</para>
+
+			<para>
+<indexterm><primary>LDAPS</primary></indexterm>
+<indexterm><primary>StartTLS</primary></indexterm>
+<indexterm><primary>LDAPv3</primary></indexterm>
+			Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS
+			extended operation. However, the OpenLDAP library still provides support for
+			the older method of securing communication between clients and servers.
+			</para>
+
+			<para>
+<indexterm><primary>harvesting password hashes</primary></indexterm>
+<indexterm><primary>ACL</primary></indexterm>
+<indexterm><primary>slapd.conf</primary></indexterm>
+			The second security precaution is to prevent non-administrative users from
+			harvesting password hashes from the directory. This can be done using the
+			following ACL in <filename>slapd.conf</filename>:
+			</para>
+
+<para>
+<programlisting>
+## allow the "ldap admin dn" access, but deny everyone else
+access to attrs=SambaLMPassword,SambaNTPassword
+     by dn="cn=Samba Admin,ou=People,dc=quenya,dc=org" write
+     by * none
+</programlisting>
+</para>
+
+		</sect3>
+
+		<sect3>
+		<title>LDAP Special Attributes for sambaSamAccounts</title>
+
+			<para> The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: <link
+			linkend="attribobjclPartA">Part A</link>, and <link linkend="attribobjclPartB">Part B</link>.
+			</para>
+
+			<table frame="all" id="attribobjclPartA">
+				<title>Attributes in the sambaSamAccount ObjectClass (LDAP), Part A</title>
+			<tgroup cols="2" align="justify">
+					<colspec align="left"/>
+					<colspec align="justify" colwidth="1*"/>
+			<tbody>
+				<row><entry><constant>sambaLMPassword</constant></entry><entry>The LanMan password 16-byte hash stored as a character
+						representation of a hexadecimal string.</entry></row>
+				<row><entry><constant>sambaNTPassword</constant></entry><entry>The NT password 16-byte hash stored as a character
+						representation of a hexadecimal string.</entry></row>
+				<row><entry><constant>sambaPwdLastSet</constant></entry><entry>The integer time in seconds since 1970 when the
+						<constant>sambaLMPassword</constant> and <constant>sambaNTPassword</constant> attributes were last set.
+				</entry></row>
+
+				<row><entry><constant>sambaAcctFlags</constant></entry><entry>String of 11 characters surrounded by square brackets [ ]
+						representing account flags such as U (user), W (workstation), X (no password expiration),
+						I (domain trust account), H (home dir required), S (server trust account),
+						and D (disabled).</entry></row>
+
+				<row><entry><constant>sambaLogonTime</constant></entry><entry>Integer value currently unused.</entry></row>
+
+				<row><entry><constant>sambaLogoffTime</constant></entry><entry>Integer value currently unused.</entry></row>
+
+				<row><entry><constant>sambaKickoffTime</constant></entry><entry>Specifies the time (UNIX time format) when the user
+				will be locked down and cannot login any longer. If this attribute is omitted, then the account will never expire.
+				Using this attribute together with shadowExpire of the shadowAccount ObjectClass will enable accounts to
+				expire completely on an exact date.</entry></row>
+
+				<row><entry><constant>sambaPwdCanChange</constant></entry><entry>Specifies the time (UNIX time format)
+				after which the user is allowed to change his password. If this attribute is not set, the user will be free
+				to change his password whenever he wants.</entry></row>
+
+				<row><entry><constant>sambaPwdMustChange</constant></entry><entry>Specifies the time (UNIX time format) when the user is
+				forced to change his password. If this value is set to 0, the user will have to change his password at first login.
+				If this attribute is not set, then the password will never expire.</entry></row>
+
+				<row><entry><constant>sambaHomeDrive</constant></entry><entry>Specifies the drive letter to which to map the
+				UNC path specified by sambaHomePath. The drive letter must be specified in the form <quote>X:</quote>
+				where X is the letter of the drive to map. Refer to the <quote>logon drive</quote> parameter in the
+				smb.conf(5) man page for more information.</entry></row>
+
+				<row><entry><constant>sambaLogonScript</constant></entry><entry>The sambaLogonScript property specifies the path of
+				the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path
+				is relative to the netlogon share. Refer to the <smbconfoption name="logon script"/> parameter in the
+				&smb.conf; man page for more information.</entry></row>
+
+				<row><entry><constant>sambaProfilePath</constant></entry><entry>Specifies a path to the user's profile.
+				This value can be a null string, a local absolute path, or a UNC path. Refer to the
+				<smbconfoption name="logon path"/> parameter in the &smb.conf; man page for more information.</entry></row>
+
+				<row><entry><constant>sambaHomePath</constant></entry><entry>The sambaHomePath property specifies the path of
+				the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies
+				a drive letter, sambaHomePath should be a UNC path. The path must be a network
+				UNC path of the form <filename>\\server\share\directory</filename>. This value can be a null string.
+				Refer to the <command>logon home</command> parameter in the &smb.conf; man page for more information.
+				</entry></row>
+			</tbody>
+			</tgroup></table>
+
+
+			<table frame="all" id="attribobjclPartB">
+				<title>Attributes in the sambaSamAccount ObjectClass (LDAP), Part B</title>
+			<tgroup cols="2" align="justify">
+					<colspec align="left"/>
+					<colspec align="justify" colwidth="1*"/>
+			<tbody>
+				<row><entry><constant>sambaUserWorkstations</constant></entry><entry>Here you can give a comma-separated list of machines
+				on which the user is allowed to login. You may observe problems when you try to connect to a Samba domain member.
+				Because domain members are not in this list, the domain controllers will reject them. Where this attribute is omitted,
+				the default implies no restrictions.
+				</entry></row>
+
+				<row><entry><constant>sambaSID</constant></entry><entry>The security identifier(SID) of the user.
+				The Windows equivalent of UNIX UIDs.</entry></row>
+
+				<row><entry><constant>sambaPrimaryGroupSID</constant></entry><entry>The security identifier (SID) of the primary group
+				of the user.</entry></row>
+
+				<row><entry><constant>sambaDomainName</constant></entry><entry>Domain the user is part of.</entry></row>
+			</tbody>
+			</tgroup></table>
+
+
+			<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+			The majority of these parameters are only used when Samba is acting as a PDC of
+			a domain (refer to <link linkend="samba-pdc">Domain Control</link>, for details on
+			how to configure Samba as a PDC). The following four attributes
+			are only stored with the sambaSamAccount entry if the values are non-default values:
+			</para>
+
+			<itemizedlist>
+<indexterm><primary>sambaHomePath</primary></indexterm>
+<indexterm><primary>sambaLogonScript</primary></indexterm>
+<indexterm><primary>sambaProfilePath</primary></indexterm>
+<indexterm><primary>sambaHomeDrive</primary></indexterm>
+				<listitem><para>sambaHomePath</para></listitem>
+				<listitem><para>sambaLogonScript</para></listitem>
+				<listitem><para>sambaProfilePath</para></listitem>
+				<listitem><para>sambaHomeDrive</para></listitem>
+			</itemizedlist>
+
+			<para>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>smbHome</primary></indexterm>
+			These attributes are only stored with the sambaSamAccount entry if
+			the values are non-default values. For example, assume MORIA has now been
+			configured as a PDC and that <smbconfoption name="logon home">\\%L\%u</smbconfoption> was defined in
+			its &smb.conf; file. When a user named <quote>becky</quote> logs on to the domain,
+			the <smbconfoption name="logon home"/> string is expanded to \\MORIA\becky.
+			If the smbHome attribute exists in the entry <quote>uid=becky,ou=People,dc=samba,dc=org</quote>,
+			this value is used. However, if this attribute does not exist, then the value
+			of the <smbconfoption name="logon home"/> parameter is used in its place. Samba
+			will only write the attribute value to the directory entry if the value is
+			something other than the default (e.g., <filename>\\MOBY\becky</filename>).
+			</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Example LDIF Entries for a sambaSamAccount</title>
+
+			<para>
+			The following is a working LDIF that demonstrates the use of the SambaSamAccount ObjectClass:
+<programlisting>
+dn: uid=guest2, ou=People,dc=quenya,dc=org
+sambaLMPassword: 878D8014606CDA29677A44EFA1353FC7
+sambaPwdMustChange: 2147483647
+sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-513
+sambaNTPassword: 552902031BEDE9EFAAD3B435B51404EE
+sambaPwdLastSet: 1010179124
+sambaLogonTime: 0
+objectClass: sambaSamAccount
+uid: guest2
+sambaKickoffTime: 2147483647
+sambaAcctFlags: [UX         ]
+sambaLogoffTime: 2147483647
+sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5006
+sambaPwdCanChange: 0
+</programlisting>
+			</para>
+
+			<para>
+			The following is an LDIF entry for using both the sambaSamAccount and
+			posixAccount ObjectClasses:
+<programlisting>
+dn: uid=gcarter, ou=People,dc=quenya,dc=org
+sambaLogonTime: 0
+displayName: Gerald Carter
+sambaLMPassword: 552902031BEDE9EFAAD3B435B51404EE
+sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-1201
+objectClass: posixAccount
+objectClass: sambaSamAccount
+sambaAcctFlags: [UX         ]
+userPassword: {crypt}BpM2ej8Rkzogo
+uid: gcarter
+uidNumber: 9000
+cn: Gerald Carter
+loginShell: /bin/bash
+logoffTime: 2147483647
+gidNumber: 100
+sambaKickoffTime: 2147483647
+sambaPwdLastSet: 1010179230
+sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5004
+homeDirectory: /home/moria/gcarter
+sambaPwdCanChange: 0
+sambaPwdMustChange: 2147483647
+sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7
+</programlisting>
+		</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Password Synchronization</title>
+
+		<para>
+		Samba-3 and later can update the non-Samba (LDAP) password stored with an account. When
+		using pam_ldap, this allows changing both UNIX and Windows passwords at once.
+		</para>
+
+		<para>The <smbconfoption name="ldap passwd sync"/> options can have the  values shown in
+		<link linkend="ldappwsync">Possible <emphasis>ldap passwd sync</emphasis> Values</link>.</para>
+
+		<table frame="all" id="ldappwsync">
+		<title>Possible <parameter>ldap passwd sync</parameter> Values</title>
+		<tgroup cols="2">
+			<colspec align="left" colwidth="1*"/>
+			<colspec align="justify" colwidth="4*"/>
+		<thead>
+			<row><entry align="left">Value</entry><entry align="center">Description</entry></row>
+		</thead>
+		<tbody>
+		<row><entry>yes</entry><entry><para>When the user changes his password, update
+			       <constant>SambaNTPassword</constant>, <constant>SambaLMPassword</constant>,
+			       and the <constant>password</constant> fields.</para></entry></row>
+
+		<row><entry>no</entry><entry><para>Only update <constant>SambaNTPassword</constant> and
+					<constant>SambaLMPassword</constant>.</para></entry></row>
+
+		<row><entry>only</entry><entry><para>Only update the LDAP password and let the LDAP server
+			worry about the other fields.  This option is only available on some LDAP servers and
+			only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</para></entry></row>
+		</tbody>
+		</tgroup>
+		</table>
+
+
+		<para>More information can be found in the &smb.conf; man page.</para>
+
+		</sect3>
+
+		<sect3>
+		<title>Using OpenLDAP Overlay for Password Syncronization</title>
+
+		<para>
+		Howard Chu has written a special overlay called <command>smbk5pwd</command>. This tool  modifies the
+		<literal>SambaNTPassword</literal>, <literal>SambaLMPassword</literal> and <literal>Heimdal</literal>
+		hashes in an OpenLDAP entry when an LDAP_EXOP_X_MODIFY_PASSWD operation is performed.
+		</para>
+
+		<para>
+		The overlay is shipped with OpenLDAP-2.3 and can be found in the
+		<filename>contrib/slapd-modules/smbk5pwd</filename> subdirectory. This module can also be used with
+		OpenLDAP-2.2.
+		</para>
+
+		</sect3>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+	<sect2>
+		<title>Users Cannot Logon</title>
+
+		<para><quote>I've installed Samba, but now I can't log on with my UNIX account! </quote></para>
+
+		<para>Make sure your user has been added to the current Samba <smbconfoption name="passdb backend"/>.
+		Read the <link linkend="acctmgmttools">Account Management Tools,</link> for details.</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Configuration of <parameter>auth methods</parameter></title>
+
+	<para>
+	When explicitly setting an <smbconfoption name="auth methods"/> parameter,
+	<parameter>guest</parameter> must be specified as the first entry on the line &smbmdash;
+	for example, <smbconfoption name="auth methods">guest sam</smbconfoption>.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-PolicyMgmt.xml b/docs-xml/Samba3-HOWTO/TOSHARG-PolicyMgmt.xml
new file mode 100644
index 00000000000..0e8b1ef229e
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-PolicyMgmt.xml
@@ -0,0 +1,607 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="PolicyMgmt">
+<chapterinfo>
+	&author.jht;
+    <pubdate>April 3 2003</pubdate>
+</chapterinfo>
+
+<title>System and Account Policies</title>
+
+<para>
+<indexterm><primary>validation</primary></indexterm>
+This chapter summarizes the current state of knowledge derived from personal
+practice and knowledge from Samba mailing list subscribers. Before reproduction
+of posted information, every effort has been made to validate the information given.
+Where additional information was uncovered through this validation, it is provided
+also.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>Group Policies</primary></indexterm>
+<indexterm><primary>users</primary></indexterm>
+<indexterm><primary>groups</primary></indexterm>
+When MS Windows NT 3.5 was introduced, the hot new topic was the ability to implement
+Group Policies for users and groups. Then along came MS Windows NT4 and a few sites
+started to adopt this capability. How do we know that? By the number of <quote>boo-boos</quote>
+(or mistakes) administrators made and then requested help to resolve.
+</para>
+
+<para>
+<indexterm><primary>group policies</primary></indexterm>
+<indexterm><primary>Group Policy Objects</primary><see>GPO</see></indexterm>
+<indexterm><primary>GPOs</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>group policy objects</primary><see>GPOs</see></indexterm>
+By the time that MS Windows 2000 and Active Directory was released, administrators
+got the message: Group Policies are a good thing! They can help reduce administrative
+costs and actually make happier users. But adoption of the true
+potential of MS Windows 200x Active Directory and Group Policy Objects (GPOs) for users
+and machines were picked up on rather slowly. This was obvious from the Samba
+mailing list back in 2000 and 2001 when there were few postings regarding GPOs and
+how to replicate them in a Samba environment.
+</para>
+
+<para>
+<indexterm><primary>exploit opportunities</primary></indexterm>
+Judging by the traffic volume since mid 2002, GPOs have become a standard part of
+the deployment in many sites. This chapter reviews techniques and methods that can
+be used to exploit opportunities for automation of control over user desktops and
+network client workstations.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Creating and Managing System Policies</title>
+
+<para>
+<indexterm><primary>NETLOGON</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>registry</primary></indexterm>
+<indexterm><primary>affect users</primary></indexterm>
+Under MS Windows platforms, particularly those following the release of MS Windows
+NT4 and MS Windows 95, it is possible to create a type of file that would be placed
+in the NETLOGON share of a domain controller. As the client logs onto the network,
+this file is read and the contents initiate changes to the registry of the client
+machine. This file allows changes to be made to those parts of the registry that
+affect users, groups of users, or machines.
+</para>
+
+<para>
+<indexterm><primary>Config.POL</primary></indexterm>
+<indexterm><primary>poledit.exe</primary></indexterm>
+<indexterm><primary>policy editor</primary></indexterm>
+For MS Windows 9x/Me, this file must be called <filename>Config.POL</filename> and may
+be generated using a tool called <filename>poledit.exe</filename>, better known as the
+Policy Editor. The policy editor was provided on the Windows 98 installation CD-ROM, but
+disappeared again with the introduction of MS Windows Me. From
+comments of MS Windows network administrators, it would appear that this tool became
+a part of the MS Windows Me Resource Kit.
+</para>
+
+<para>
+<indexterm><primary>System Policy Editor</primary></indexterm>
+MS Windows NT4 server products include the <emphasis>System Policy Editor</emphasis>
+under <guimenu>Start -> Programs -> Administrative Tools</guimenu>.
+For MS Windows NT4 and later clients, this file must be called <filename>NTConfig.POL</filename>.
+</para>
+
+<para>
+<indexterm><primary>MMC</primary></indexterm>
+New with the introduction of MS Windows 2000 was the Microsoft Management Console
+or MMC. This tool is the new wave in the ever-changing landscape of Microsoft
+methods for management of network access and security. Every new Microsoft product
+or technology seems to make the old rules obsolete and introduces newer and more
+complex tools and methods. To Microsoft's credit, the MMC does appear to
+be a step forward, but improved functionality comes at a great price.
+</para>
+
+<para>
+<indexterm><primary>network policies</primary></indexterm>
+<indexterm><primary>system policies</primary></indexterm>
+<indexterm><primary>Profiles</primary></indexterm>
+<indexterm><primary>Policies</primary></indexterm>
+Before embarking on the configuration of network and system policies, it is highly
+advisable to read the documentation available from Microsoft's Web site regarding
+<ulink url="http://www.microsoft.com/ntserver/techresources/management/prof_policies.asp">
+Implementing Profiles and Policies in Windows NT 4.0</ulink>.
+There are a large number of documents in addition to this old one that should also
+be read and understood. Try searching on the Microsoft Web site for <quote>Group Policies</quote>.
+</para>
+
+<para>
+What follows is a brief discussion with some helpful notes. The information provided
+here is incomplete &smbmdash; you are warned.
+</para>
+
+	<sect2>
+	<title>Windows 9x/ME Policies</title>
+
+	<para>
+<indexterm><primary>Group Policy Editor</primary></indexterm>
+<indexterm><primary>tools\reskit\netadmin\poledit</primary></indexterm>
+	You need the Windows 98 Group Policy Editor to set up Group Profiles under Windows 9x/Me.
+	It can be found on the original full-product Windows 98 installation CD-ROM under
+	<filename>tools\reskit\netadmin\poledit</filename>. Install this using the
+	Add/Remove Programs facility, and then click on <guiicon>Have Disk</guiicon>.
+	</para>
+
+
+	<para>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+<indexterm><primary>Config.POL</primary></indexterm>
+	Use the Group Policy Editor to create a policy file that specifies the location of
+	user profiles and/or <filename>My Documents</filename>, and so on. Then save these
+	settings in a file called <filename>Config.POL</filename> that needs to be placed in the
+	root of the <smbconfsection name="[NETLOGON]"/> share. If Windows 98 is configured to log onto
+	the Samba domain, it will automatically read this file and update the Windows 9x/Me registry
+	of the machine as it logs on.
+	</para>
+
+	<para>
+	Further details are covered in the Windows 98 Resource Kit documentation.
+	</para>
+
+	<para>
+<indexterm><primary>registry</primary></indexterm>
+	If you do not take the correct steps, then every so often Windows 9x/Me will check the
+	integrity of the registry and restore its settings from the backup
+	copy of the registry it stores on each Windows 9x/Me machine. So, you will
+	occasionally notice things changing back to the original settings.
+	</para>
+
+	<para>
+<indexterm><primary>grouppol.inf</primary></indexterm>
+<indexterm><primary>Group Policy</primary></indexterm>
+	Install the Group Policy handler for Windows 9x/Me to pick up Group Policies. Look on the
+	Windows 98 CD-ROM in <filename>\tools\reskit\netadmin\poledit</filename>.
+	Install Group Policies on a Windows 9x/Me client by double-clicking on
+	<filename>grouppol.inf</filename>. Log off and on again a couple of times and see
+	if Windows 98 picks up Group Policies. Unfortunately, this needs to be done on every
+	Windows 9x/Me machine that uses Group Policies.
+	</para>
+
+	</sect2>
+	<sect2>
+	<title>Windows NT4-Style Policy Files</title>
+
+	<para>
+<indexterm><primary>ntconfig.pol</primary></indexterm>
+<indexterm><primary>poledit.exe</primary></indexterm>
+<indexterm><primary>Policy Editor</primary></indexterm>
+<indexterm><primary>domain policies</primary></indexterm>
+	To create or edit <filename>ntconfig.pol</filename>, you must use the NT Server
+	Policy Editor, <command>poledit.exe</command>, which is included with NT4 Server
+	but not with NT workstation. There is a Policy Editor on an NT4
+	Workstation but it is not suitable for creating domain policies.
+	Furthermore, although the Windows 95 Policy Editor can be installed on an NT4
+	workstation/server, it will not work with NT clients. However, the files from
+	the NT Server will run happily enough on an NT4 workstation.
+	</para>
+
+	<para>
+<indexterm><primary>poledit.exe</primary></indexterm>
+<indexterm><primary>common.adm</primary></indexterm>
+<indexterm><primary>winnt.adm</primary></indexterm>
+<indexterm><primary>c:\winnt\inf</primary></indexterm>
+	You need <filename>poledit.exe</filename>, <filename>common.adm</filename>, and <filename>winnt.adm</filename>.
+	It is convenient to put the two <filename>*.adm</filename> files in  the <filename>c:\winnt\inf</filename> 
+	directory, which is where the binary will look for them unless told otherwise. This
+	directory is normally <quote>hidden.</quote>
+	</para>
+
+	<para>
+<indexterm><primary>Policy Editor</primary></indexterm>
+<indexterm><primary>Nt4sp6ai.exe</primary></indexterm>
+<indexterm><primary>poledit.exe</primary></indexterm>
+<indexterm><primary>Zero Administration Kit</primary></indexterm>
+	The Windows NT Policy Editor is also included with the Service Pack 3 (and
+	later) for Windows NT 4.0. Extract the files using <command>servicepackname /x</command>
+	&smbmdash; that's <command>Nt4sp6ai.exe /x</command> for Service Pack 6a. The Policy Editor,
+	<command>poledit.exe</command>, and the associated template files (*.adm) should
+	be extracted as well. It is also possible to download the policy template
+	files for Office97 and get a copy of the Policy Editor. Another possible
+	location is with the Zero Administration Kit available for download from Microsoft.
+	</para>
+
+		<sect3>
+		<title>Registry Spoiling</title>
+
+			<para>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+<indexterm><primary>HKEY_LOCAL_MACHINE</primary></indexterm>
+			With NT4-style registry-based policy changes, a large number of settings are not
+			automatically reversed as the user logs off. The settings that were in the
+			<filename>NTConfig.POL</filename> file were applied to the client machine registry and apply to the
+			hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known
+			as tattooing. It can have serious consequences downstream, and the administrator must
+			be extremely careful not to lock out the ability to manage the machine at a later date.
+			</para>
+
+		</sect3>
+	</sect2>
+	<sect2>
+	<title>MS Windows 200x/XP Professional Policies</title>
+
+	<para>
+<indexterm><primary>registry</primary></indexterm>
+	Windows NT4 system policies allow the setting of registry parameters specific to
+	users, groups, and computers (client workstations) that are members of the NT4-style
+	domain. Such policy files will work with MS Windows 200x/XP clients also.
+	</para>
+
+	<para>
+	New to MS Windows 2000, Microsoft recently introduced a style of Group Policy that confers
+	a superset of capabilities compared with NT4-style policies. Obviously, the tool used
+	to create them is different, and the mechanism for implementing them is much improved.
+	</para>
+
+	<para>
+	<indexterm><primary>GPOs</primary></indexterm>
+<indexterm><primary>Administrative Templates</primary></indexterm>
+	The older NT4-style registry-based policies are known as <emphasis>Administrative Templates</emphasis>
+	in MS Windows 2000/XP GPOs. The latter includes the ability to set various security
+	configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
+	users desktop (including the location of <filename>My Documents</filename> files, as
+	well as intrinsics of where menu items will appear in the Start menu). An additional new
+	feature is the ability to make available particular software Windows applications to particular
+	users and/or groups.
+	</para>
+
+	<para>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+<indexterm><primary>NETLOGON</primary></indexterm>
+<indexterm><primary>local registry values</primary></indexterm>
+	Remember, NT4 policy files are named <filename>NTConfig.POL</filename> and are stored in the root
+	of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username and password
+	and selects the domain name to which the logon will attempt to take place. During the logon process,
+	the client machine reads the <filename>NTConfig.POL</filename> file from the NETLOGON share on
+	the authenticating server and modifies the local registry values according to the settings in this file.
+	</para>
+
+	<para>
+<indexterm><primary>SYSVOL</primary></indexterm>
+<indexterm><primary>NETLOGON</primary></indexterm>
+<indexterm><primary>replicated</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>domain controllers</primary></indexterm>
+<indexterm><primary>Group Policy Container</primary><see>GPC</see></indexterm>
+<indexterm><primary>Group Policy Template</primary><see>GPT</see></indexterm>
+<indexterm><primary>replicated SYSVOL</primary></indexterm>
+	Windows 200x GPOs are feature-rich. They are not stored in the NETLOGON share, but rather part of
+	a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
+	in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
+	Directory domain controllers. The part that is stored in the Active Directory itself is called the
+	Group Policy Container (GPC), and the part that is stored in the replicated share called SYSVOL is
+	known as the Group Policy Template (GPT).
+	</para>
+
+	<para>
+<indexterm><primary>GPOs</primary></indexterm>
+	With NT4 clients, the policy file is read and executed only as each user logs onto the network.
+	MS Windows 200x policies are much more complex &smbmdash; GPOs are processed and applied at client machine
+	startup (machine specific part), and when the user logs onto the network, the user-specific part
+	is applied. In MS Windows 200x-style policy management, each machine and/or user may be subject
+	to any number of concurrently applicable (and applied) policy sets (GPOs). Active Directory allows
+	the administrator to also set filters over the policy settings. No such equivalent capability
+	exists with NT4-style policy files.
+	</para>
+
+		<sect3>
+		<title>Administration of Windows 200x/XP Policies</title>
+
+		<para>
+		<indexterm><primary>GPOs</primary></indexterm>
+		<indexterm><primary>System Policy Editor</primary></indexterm>
+<indexterm><primary>poledit.exe</primary></indexterm>
+<indexterm><primary>MMC snap-in</primary></indexterm>
+<indexterm><primary>Poledit</primary></indexterm>
+		Instead of using the tool called <application>the System Policy Editor</application>, commonly called Poledit (from the
+		executable name <command>poledit.exe</command>), <acronym>GPOs</acronym> are created and managed using a 
+		<application>Microsoft Management Console</application> <acronym>(MMC)</acronym> snap-in as follows:</para>
+		<procedure>
+			<step><para>
+			Go to the Windows 200x/XP menu <guimenu>Start->Programs->Administrative Tools</guimenu>
+			and select the MMC snap-in called <guimenuitem>Active Directory Users and Computers</guimenuitem>
+			</para></step>
+
+			<step><para>
+<indexterm><primary>organizational unit</primary><see>OU</see></indexterm>
+			Select the domain or organizational unit (OU) that you wish to manage, then right-click
+			to open the context menu for that object, and select the <guibutton>Properties</guibutton>.
+			</para></step>
+
+			<step><para>
+			Left-click on the <guilabel>Group Policy</guilabel> tab, then
+			left-click on the New tab. Type a name
+			for the new policy you will create.
+			</para></step>
+
+			<step><para>
+			 Left-click on the <guilabel>Edit</guilabel> tab to commence the steps needed to create the GPO.
+			</para></step>
+		</procedure>
+
+		<para>
+		All policy configuration options are controlled through the use of policy administrative
+		templates. These files have an .adm extension, both in NT4 as well as in Windows 200x/XP.
+		Beware, however, the .adm files are not interchangeable across NT4 and Windows 200x.
+		The latter introduces many new features as well as extended definition capabilities. It is
+		well beyond the scope of this documentation to explain how to program .adm files; for that,
+		refer to the Microsoft Windows Resource Kit for your particular
+		version of MS Windows.
+		</para>
+
+		<note>
+		<para>
+<indexterm><primary>gpolmig.exe</primary></indexterm>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+<indexterm><primary>resource kit</primary></indexterm>
+		The MS Windows 2000 Resource Kit contains a tool called <command>gpolmig.exe</command>. This tool can be used
+		to migrate an NT4 <filename>NTConfig.POL</filename> file into a Windows 200x style GPO. Be VERY careful how you
+		use this powerful tool. Please refer to the resource kit manuals for specific usage information.
+		</para>
+		</note>
+
+		</sect3>
+
+		<sect3>
+		<title>Custom System Policy Templates</title>
+
+		<para>
+		Over the past year, there has been a bit of talk regarding the creation of customized
+		templates for the Windows Sytem Policy Editor. A recent announcement on the Samba mailing
+		list is worthy of mention.
+		</para>
+
+		<para>
+		Mike Petersen has announced the availability of a template file he has created. This custom System Policy
+		Editor Template will allow you to successfully control Microsoft Windows workstations from an SMB server, such
+		as Samba. This template has been tested on a few networks, although if you find any problems with any of these
+		policies, or have any ideas for additional policies, let me know at mailto:mgpeter@pcc-services.com.  This
+		Template includes many policies for Windows XP to allow it to behave better in a professional environment.
+		</para>
+
+		<para>
+		For further information please see the <ulink
+		url="http://www.pcc-services.com/custom_poledit.html">Petersen</ulink> Computer Consulting web site. There is
+		a download link for the template file.
+		</para>
+
+		</sect3>
+	</sect2>
+</sect1>
+
+<sect1>
+<title>Managing Account/User Policies</title>
+
+<para>
+<indexterm><primary>Policies</primary></indexterm>
+<indexterm><primary>policy file </primary></indexterm>
+<indexterm><primary>registry settings</primary></indexterm>
+Policies can define a specific user's settings or the settings for a group of users. The resulting
+policy file contains the registry settings for all users, groups, and computers that will be using
+the policy file. Separate policy files for each user, group, or computer are not necessary.
+</para>
+
+<para>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+If you create a policy that will be automatically downloaded from validating domain controllers,
+you should name the file <filename>NTConfig.POL</filename>. As system administrator, you have the option of renaming the
+policy file and, by modifying the Windows NT-based workstation, directing the computer to update
+the policy from a manual path. You can do this by either manually changing the registry or by using
+the System Policy Editor. This can even be a local path such that each machine has its own policy file,
+but if a change is necessary to all machines, it must be made individually to each workstation.
+</para>
+
+<para>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+<indexterm><primary>NETLOGON</primary></indexterm>
+When a Windows NT4/200x/XP machine logs onto the network, the client looks in the NETLOGON share on
+the authenticating domain controller for the presence of the <filename>NTConfig.POL</filename> file. If one exists, it is 
+downloaded, parsed, and then applied to the user's part of the registry.
+</para>
+
+<para>
+<indexterm><primary>GPOs</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+<indexterm><primary>NT4 style policy updates</primary></indexterm>
+MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally
+acquire policy settings through GPOs that are defined and stored in Active Directory
+itself. The key benefit of using AD GPOs is that they impose no registry <emphasis>spoiling</emphasis> effect.
+This has considerable advantage compared with the use of <filename>NTConfig.POL</filename> (NT4) style policy updates.
+</para>
+
+<para>
+<indexterm><primary>account restrictions</primary></indexterm>
+<indexterm><primary>Common restrictions</primary></indexterm>
+In addition to user access controls that may be imposed or applied via system and/or group policies
+in a manner that works in conjunction with user profiles, the user management environment under
+MS Windows NT4/200x/XP allows per-domain as well as per-user account restrictions to be applied.
+Common restrictions that are frequently used include:
+</para>
+
+<para>
+<indexterm><primary>Account Controls</primary></indexterm>
+<itemizedlist>
+	<listitem><para>Logon hours</para></listitem>
+	<listitem><para>Password aging</para></listitem>
+	<listitem><para>Permitted logon from certain machines only</para></listitem>
+	<listitem><para>Account type (local or global)</para></listitem>
+	<listitem><para>User rights</para></listitem>
+</itemizedlist>
+</para>
+
+<para>
+<indexterm><primary>Domain User Manager</primary></indexterm>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+Samba-3.0.20 does not yet implement all account controls that are common to MS Windows NT4/200x/XP.
+While it is possible to set many controls using the Domain User Manager for MS Windows NT4, only password
+expiry is functional today. Most of the remaining controls at this time have only stub routines
+that may eventually be completed to provide actual control. Do not be misled by the fact that a
+parameter can be set using the NT4 Domain User Manager or in the <filename>NTConfig.POL</filename>.
+</para>
+
+</sect1>
+<sect1>
+<title>Management Tools</title>
+
+<para>
+Anyone who wishes to create or manage Group Policies will need to be familiar with a number of tools.
+The following sections describe a few key tools that will help you to create a low-maintenance user
+environment.
+</para>
+
+	<sect2>
+	<title>Samba Editreg Toolset</title>
+
+	<para>
+	<indexterm><primary>editreg</primary></indexterm>
+	<indexterm><primary>NTUser.DAT</primary></indexterm>
+	<indexterm><primary>NTConfig.POL</primary></indexterm>
+	A new tool called <command>editreg</command> is under development. This tool can be used
+	to edit registry files (called <filename>NTUser.DAT</filename>) that are stored in user
+	and group profiles. <filename>NTConfig.POL</filename> files have the same structure as the
+	<filename>NTUser.DAT</filename> file and can be edited using this tool. <command>editreg</command>
+	is being built with the intent to enable <filename>NTConfig.POL</filename> files to be saved in text format and to
+	permit the building of new <filename>NTConfig.POL</filename> files with extended capabilities. It is proving difficult
+	to realize this capability, so do not be surprised if this feature does not materialize. Formal
+	capabilities will be announced at the time that this tool is released for production use.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Windows NT4/200x</title>
+
+	<para>
+<indexterm><primary>regedt32.exe</primary></indexterm>
+<indexterm><primary>Group Policy Editor</primary></indexterm>
+<indexterm><primary>MMC</primary></indexterm>
+	The tools that may be used to configure these types of controls from the MS Windows environment are
+	the NT4 User Manager for Domains, the NT4 System and Group Policy Editor, and the Registry Editor (regedt32.exe).
+	Under MS Windows 200x/XP, this is done using the MMC with appropriate
+	<quote>snap-ins,</quote> the registry editor, and potentially also the NT4 System and Group Policy Editor.
+	</para>
+	</sect2>
+
+	<sect2>
+	<title>Samba PDC</title>
+
+	<para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>NET</primary></indexterm>
+<indexterm><primary>rpcclient</primary></indexterm>
+	With a Samba domain controller, the new tools for managing user account and policy information include:
+	<command>smbpasswd</command>, <command>pdbedit</command>, <command>net</command>, and <command>rpcclient</command>. 
+	The administrator should read the man pages for these tools and become familiar with their use.
+	</para>
+
+	</sect2>
+</sect1>
+
+<sect1>
+<title>System Startup and Logon Processing Overview</title>
+
+<para>
+The following attempts to document the order of processing the system and user policies following a system
+reboot and as part of the user logon:
+</para>
+
+<orderedlist>
+	<listitem><para>
+<indexterm><primary>Remote Procedure Call System Service</primary><see>RPCSS</see></indexterm>
+<indexterm><primary>multiple universal naming convention provider</primary><see>MUP</see></indexterm>
+	Network starts, then Remote Procedure Call System Service (RPCSS) and multiple universal naming
+	convention provider (MUP) start.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>GPOs</primary></indexterm>
+	Where Active Directory is involved, an ordered list of GPOs is downloaded
+	and applied. The list may include GPOs that:
+<itemizedlist>
+	<listitem><para>Apply to the location of machines in a directory.</para></listitem>
+	<listitem><para>Apply only when settings have changed.</para></listitem>
+	<listitem><para>Depend on configuration of the scope of applicability: local,
+	site, domain, organizational unit, and so on.</para></listitem>
+</itemizedlist>
+	No desktop user interface is presented until the above have been processed.
+	</para></listitem>
+
+	<listitem><para>
+	Execution of startup scripts (hidden and synchronous by default).
+	</para></listitem>
+
+	<listitem><para>
+	A keyboard action to effect start of logon (Ctrl-Alt-Del).
+	</para></listitem>
+
+	<listitem><para>
+	User credentials are validated, user profile is loaded (depends on policy settings).
+	</para></listitem>
+
+	<listitem><para>
+	An ordered list of user GPOs is obtained. The list contents depends on what is configured in respect of:
+
+<itemizedlist>
+	<listitem><para>Is the user a domain member, thus subject to particular policies?</para></listitem>
+	<listitem><para>Loopback enablement, and the state of the loopback policy (merge or replace).</para></listitem>
+	<listitem><para>Location of the Active Directory itself.</para></listitem>
+	<listitem><para>Has the list of GPOs changed? No processing is needed if not changed.</para></listitem>
+</itemizedlist>
+	</para></listitem>
+
+	<listitem><para>
+	User policies are applied from Active Directory. Note: There are several types.
+	</para></listitem>
+
+	<listitem><para>
+	Logon scripts are run. New to Windows 200x and Active Directory, logon scripts may be obtained based on GPOs
+	(hidden and executed synchronously). NT4-style logon scripts are then run in a normal
+	window.
+	</para></listitem>
+
+	<listitem><para>
+	The user interface as determined from the GPOs is presented. Note: In a Samba domain (like an NT4
+	domain), machine (system) policies are applied at startup; user policies are applied at logon.
+	</para></listitem>
+</orderedlist>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+Policy-related problems can be quite difficult to diagnose and even more difficult to rectify. The following
+collection demonstrates only basic issues.
+</para>
+
+<sect2>
+<title>Policy Does Not Work</title>
+
+<para>
+<quote>We have created the <filename>Config.POL</filename> file and put it in the <emphasis>NETLOGON</emphasis> share.
+It has made no difference to our Win XP Pro machines, they just do not see it. It worked fine with Win 98 but does not
+work any longer since we upgraded to Win XP Pro. Any hints?</quote>
+</para>
+
+<para>
+Policy files are not portable between Windows 9x/Me and MS Windows NT4/200x/XP-based platforms. You need to
+use the NT4 Group Policy Editor to create a file called <filename>NTConfig.POL</filename> so it is in the
+correct format for your MS Windows XP Pro clients.
+</para>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Portability.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Portability.xml
new file mode 100644
index 00000000000..533ad5c9bb8
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Portability.xml
@@ -0,0 +1,270 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="Portability">
+<chapterinfo>
+	&author.jelmer;
+	&author.jht;
+	<!-- Some other people as well, but there were no author names in the text files this file is based on-->
+</chapterinfo>
+
+<title>Portability</title>
+
+<para>
+<indexterm><primary>platforms</primary></indexterm>
+<indexterm><primary>compatible</primary></indexterm>
+Samba works on a wide range of platforms, but the interface all the 
+platforms provide is not always compatible. This chapter contains 
+platform-specific information about compiling and using Samba.</para>
+
+<sect1>
+<title>HPUX</title>
+
+<para>
+<indexterm><primary>/etc/logingroup</primary></indexterm>
+<indexterm><primary>/etc/group</primary></indexterm>
+Hewlett-Packard's implementation of supplementary groups is nonstandard (for
+historical reasons). There are two group files, <filename>/etc/group</filename> and
+<filename>/etc/logingroup</filename>; the system maps UIDs to numbers using the former, but
+initgroups() reads the latter. Most system admins who know the ropes
+symlink <filename>/etc/group</filename> to <filename>/etc/logingroup</filename>
+(hard-link does not work for reasons too obtuse to go into here). initgroups() will complain if one of the
+groups you're in, in <filename>/etc/logingroup</filename>, has what it considers to be an invalid
+ID, which means outside the range <constant>[0..UID_MAX]</constant>, where <constant>UID_MAX</constant> is
+60000 currently on HP-UX. This precludes -2 and 65534, the usual <constant>nobody</constant>
+GIDs.
+</para>
+
+<para>
+If you encounter this problem, make sure the programs that are failing 
+to initgroups() are run as users, not in any groups with GIDs outside the 
+allowed range.
+</para>
+
+<para>
+This is documented in the HP manual pages under setgroups(2) and passwd(4).
+</para>
+
+<para>
+<indexterm><primary>gcc</primary></indexterm>
+<indexterm><primary>ANSI compiler</primary></indexterm>
+On HP-UX you must use gcc or the HP ANSI compiler. The free compiler
+that comes with HP-UX is not ANSI compliant and cannot compile Samba.
+</para>
+
+</sect1>
+
+<sect1>
+<title>SCO UNIX</title>
+
+<para> 
+If you run an old version of SCO UNIX, you may need to get important 
+TCP/IP patches for Samba to work correctly. Without the patch, you may 
+encounter corrupt data transfers using Samba.
+</para>
+
+<para>
+The patch you need is UOD385 Connection Drivers SLS. It is available from
+SCO <ulink noescape="1" url="ftp://ftp.sco.com/">ftp.sco.com</ulink>, directory SLS,
+files uod385a.Z and uod385a.ltr.Z).
+</para>
+
+<para>
+The information provided here refers to an old version of SCO UNIX. If you require
+binaries for more recent SCO UNIX products, please contact SCO to obtain packages that are
+ready to install. You should also verify with SCO that your platform is up to date for the
+binary packages you will install. This is important if you wish to avoid data corruption
+problems with your installation. To build Samba for SCO UNIX products  may
+require significant patching of Samba source code. It is much easier to obtain binary
+packages directly from SCO.
+</para>
+
+</sect1>
+
+<sect1>
+<title>DNIX</title>
+
+<para>
+DNIX has a problem with seteuid() and setegid(). These routines are
+needed for Samba to work correctly, but they were left out of the DNIX
+C library for some reason.
+</para>
+
+<para>
+For this reason Samba by default defines the macro NO_EID in the DNIX
+section of includes.h. This works around the problem in a limited way,
+but it is far from ideal, and some things still will not work right.
+</para>
+
+<para> 
+To fix the problem properly, you need to assemble the following two
+functions and then either add them to your C library or link them into
+Samba. Put the following in the file <filename>setegid.s</filename>:
+</para>
+
+<para><programlisting>
+        .globl  _setegid
+_setegid:
+        moveq   #47,d0
+        movl    #100,a0
+        moveq   #1,d1
+        movl    4(sp),a1
+        trap    #9
+        bccs    1$
+        jmp     cerror
+1$:
+        clrl    d0
+        rts
+</programlisting></para>
+
+<para>
+Put this in the file <filename>seteuid.s</filename>:
+</para>
+
+<para><programlisting>
+        .globl  _seteuid
+_seteuid:
+        moveq   #47,d0
+        movl    #100,a0
+        moveq   #0,d1
+        movl    4(sp),a1
+        trap    #9
+        bccs    1$
+        jmp     cerror
+1$:
+        clrl    d0
+        rts
+</programlisting></para>
+
+<para>
+After creating the files, you then assemble them using
+</para>
+
+<screen>
+&prompt;<userinput>as seteuid.s</userinput>
+&prompt;<userinput>as setegid.s</userinput>
+</screen>
+
+<para>
+which should produce the files <filename>seteuid.o</filename> and
+<filename>setegid.o</filename>.
+</para>
+
+<para>
+Next you need to add these to the LIBSM line in the DNIX section of
+the Samba Makefile. Your LIBSM line will look something like this:
+</para>
+
+<para><programlisting>
+LIBSM = setegid.o seteuid.o -ln
+</programlisting></para>
+
+<para>
+You should then remove the line:
+</para>
+
+<para><programlisting>
+#define NO_EID
+</programlisting></para>
+
+<para>from the DNIX section of <filename>includes.h</filename>.</para>
+
+</sect1>
+
+<sect1>
+<title>Red Hat Linux</title>
+
+<para>
+By default during installation, some versions of Red Hat Linux add an
+entry to <filename>/etc/hosts</filename> as follows:
+<programlisting>
+127.0.0.1 loopback "hostname"."domainname"
+</programlisting>
+</para>
+
+<para>
+<indexterm><primary>loopback interface</primary></indexterm>
+This causes Samba to loop back onto the loopback interface.
+The result is that Samba fails to communicate correctly with
+the world and therefore may fail to correctly negotiate who
+is the master browse list holder and who is the master browser.
+</para>
+
+<para>
+Corrective action: Delete the entry after the word "loopback"
+in the line starting 127.0.0.1.
+</para>
+</sect1>
+
+<sect1>
+<title>AIX: Sequential Read Ahead</title>
+<!-- From an email by William Jojo <jojowil@hvcc.edu> -->
+<para>
+Disabling sequential read ahead can improve Samba performance significantly
+when there is a relatively high level of multiprogramming (many smbd processes
+or mixed with another workload), not an abundance of physical memory or slower
+disk technology. These can cause AIX to have a higher WAIT values. Disabling
+sequential read-ahead can also have an adverse affect on other workloads in the
+system so you will need to evaluate other applications for impact.
+</para>
+
+<para>
+It is recommended to use the defaults provided by IBM, but if you experience a
+high amount of wait time, try disabling read-ahead with the following commands:
+</para>
+
+<para>
+For AIX 5.1 and earlier: <userinput>vmtune -r 0</userinput>
+</para>
+
+<para>
+For AIX 5.2 and later jfs filesystems: <userinput>ioo -o minpgahead=0</userinput>
+</para>
+
+<para>
+For AIX 5.2 and later jfs2 filesystems: <userinput>ioo -o j2_minPageReadAhead=0</userinput>
+</para>
+
+<para>
+If you have a mix of jfs and jfs2 filesystems on the same host, simply use both
+ioo commands.
+</para>
+</sect1>
+
+<sect1>
+<title>Solaris</title>
+
+<sect2>
+<title>Locking Improvements</title>
+
+<para>Some people have been experiencing problems with F_SETLKW64/fcntl 
+when running Samba on Solaris. The built-in file-locking mechanism was
+not scalable. Performance would degrade to the point where processes would
+get into loops of trying to lock a file. It would try a lock, then fail,
+then try again. The lock attempt was failing before the grant was
+occurring. The visible manifestation of this was a handful of
+processes stealing all of the CPU, and when they were trussed, they would
+be stuck in F_SETLKW64 loops.
+</para>
+
+<para>
+Please check with Sun support for current patches needed to fix this bug.
+The patch revision for 2.6 is 105181-34, for 8 is 108528-19, and for 9 is 112233-04.
+After the installation of these patches, it is recommended to reconfigure
+and rebuild Samba.
+</para>
+
+<para>Thanks to Joe Meslovich for reporting this.</para>
+
+</sect2>
+
+<sect2 id="winbind-solaris9">
+<title>Winbind on Solaris 9</title>
+<para>
+Nsswitch on Solaris 9 refuses to use the Winbind NSS module. This behavior
+is fixed by Sun in patch <ulink
+url="http://sunsolve.sun.com/search/advsearch.do?collection=PATCH&amp;type=collections&amp;max=50&amp;language=en&amp;queryKey5=112960;rev=14&amp;toDocument=yes">112960-14</ulink>.
+</para>
+</sect2>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Printing.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Printing.xml
new file mode 100644
index 00000000000..1cf35fb7c4f
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Printing.xml
@@ -0,0 +1,3273 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="classicalprinting">
+
+<chapterinfo>
+	<author>
+		<firstname>Kurt</firstname><surname>Pfeifle</surname>
+		<affiliation>
+			<orgname>Danka Deutschland GmbH</orgname>
+			<address><email>kpfeifle@danka.de</email></address>
+		</affiliation>
+	</author>
+	&author.jerry;
+	&author.jht;
+	<pubdate>May 31, 2003</pubdate>
+</chapterinfo>
+
+<title>Classical Printing Support</title>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>mission-critical</primary></indexterm>
+Printing is often a mission-critical service for the users. Samba can provide this service reliably and
+seamlessly for a client network consisting of Windows workstations.
+</para>
+
+<para>
+<indexterm><primary>print service</primary></indexterm>
+<indexterm><primary>domain member server</primary></indexterm>
+<indexterm><primary>standalone server</primary></indexterm>
+<indexterm><primary>file serving</primary></indexterm>
+<indexterm><primary>dedicated print server</primary></indexterm>
+<indexterm><primary>print server</primary></indexterm>
+<indexterm><primary>printing support</primary></indexterm>
+<indexterm><primary>Point'n'Print</primary></indexterm>
+<indexterm><primary>Add Printer Wizard</primary></indexterm>
+<indexterm><primary>upload drivers</primary></indexterm>
+<indexterm><primary>manage drivers</primary></indexterm>
+<indexterm><primary>install drivers</primary></indexterm>
+<indexterm><primary>print accounting</primary></indexterm>
+<indexterm><primary>Common UNIX Printing System</primary><see>CUPS</see></indexterm>
+A Samba print service may be run on a standalone or domain member server, side by side with file serving
+functions, or on a dedicated print server.  It can be made as tightly or as loosely secured as needs dictate.
+Configurations may be simple or complex. Available authentication schemes are essentially the same as
+described for file services in previous chapters. Overall, Samba's printing support is now able to replace an
+NT or Windows 2000 print server full-square, with additional benefits in many cases. Clients may download and
+install drivers and printers through their familiar <literal>Point'n'Print</literal> mechanism. Printer
+installations executed by <literal>Logon Scripts</literal> are no problem. Administrators can upload and manage
+drivers to be used by clients through the familiar <literal>Add Printer Wizard</literal>. As an additional
+benefit, driver and printer management may be run from the command line or through scripts, making it more
+efficient in case of large numbers of printers. If a central accounting of print jobs (tracking every single
+page and supplying the raw data for all sorts of statistical reports) is required, this function is best
+supported by the newer Common UNIX Printing System (CUPS) as the print subsystem underneath the Samba hood.
+</para>
+
+<para>
+<indexterm><primary>BSD</primary></indexterm>
+<indexterm><primary>CUPS</primary></indexterm>
+This chapter outlines the fundamentals of Samba printing as implemented by the more traditional UNIX
+BSD- and System V-style printing systems. Much of the information in this chapter applies also to CUPS.  If
+you use CUPS, you may be tempted to jump to the next chapter, but you will certainly miss a few things if you
+do. For further information refer to <link linkend="CUPS-printing">CUPS Printing Support</link>.
+</para>
+
+<note>
+<para>
+<indexterm><primary>Windows XP Professional</primary></indexterm>
+<indexterm><primary>Windows 200x/XP</primary></indexterm>
+<indexterm><primary>Windows NT4</primary></indexterm>
+Most of the following examples have been verified on Windows XP Professional clients. Where this document
+describes the responses to commands given, bear in mind that Windows 200x/XP clients are quite similar but may
+differ in minor details. Windows NT4 is somewhat different again.
+</para>
+</note>
+
+</sect1>
+
+<sect1>
+<title>Technical Introduction</title>
+
+<para>
+<indexterm><primary>printing support</primary></indexterm>
+<indexterm><primary>print subsystem</primary></indexterm>
+<indexterm><primary>printing system</primary></indexterm>
+Samba's printing support always relies on the installed print subsystem of the UNIX OS it runs on. Samba is a
+<literal>middleman.</literal> It takes print files from Windows (or other SMB) clients and passes them to the real
+printing system for further processing; therefore, it needs to communicate with both sides: the Windows print
+clients and the UNIX printing system. Hence, we must differentiate between the various client OS types, each
+of which behave differently, as well as the various UNIX print subsystems, which themselves have different
+features and are accessed differently.
+</para>
+
+<para>
+<indexterm><primary>UNIX printing</primary></indexterm>
+<indexterm><primary>CUPS</primary></indexterm>
+This chapter deals with the traditional way of UNIX printing. The next chapter covers in great detail the more
+modern CUPS.
+</para>
+
+<important><para>
+<indexterm><primary>CUPS</primary></indexterm>
+CUPS users, be warned: do not just jump on to the next chapter. You might miss important information only found here!
+</para></important>
+
+<para>
+<indexterm><primary>print configuration</primary></indexterm>
+<indexterm><primary>problematic print</primary></indexterm>
+<indexterm><primary>print processing</primary></indexterm>
+<indexterm><primary>print filtering</primary></indexterm>
+It is apparent from postings on the Samba mailing list that print configuration is one of the most problematic
+aspects of Samba administration today. Many new Samba administrators have the impression that Samba performs
+some sort of print processing. Rest assured, Samba does not perform any type of print processing. It does not
+do any form of print filtering.
+</para>
+
+<para>
+<indexterm><primary>data stream</primary></indexterm>
+<indexterm><primary>local spool area</primary></indexterm>
+<indexterm><primary>spooled file</primary></indexterm>
+<indexterm><primary>local system printing</primary></indexterm>
+Samba obtains from its clients a data stream (print job) that it spools to a local spool area. When the entire
+print job has been received, Samba invokes a local UNIX/Linux print command and passes the spooled file to it.
+It is up to the local system printing subsystems to correctly process the print job and to submit it to the
+printer.
+</para>
+
+<sect2>
+<title>Client to Samba Print Job Processing</title>
+
+<para>
+Successful printing from a Windows client via a Samba print server to a UNIX
+printer involves six (potentially seven) stages:
+</para>
+
+<orderedlist>
+	<listitem><para>Windows opens a connection to the printer share.</para></listitem>
+
+	<listitem><para>Samba must authenticate the user.</para></listitem>
+
+	<listitem><para>Windows sends a copy of the print file over the network
+	into Samba's spooling area.</para></listitem>
+
+	<listitem><para>Windows closes the connection.</para></listitem>
+
+	<listitem><para>Samba invokes the print command to hand the file over
+	to the UNIX print subsystem's spooling area.</para></listitem>
+
+	<listitem><para>The UNIX print subsystem processes the print job.</para></listitem>
+
+	<listitem><para>The print file may need to be explicitly deleted
+	from the Samba spooling area. This item depends on your print spooler
+	configuration settings.</para></listitem>
+</orderedlist>
+</sect2>
+
+<sect2>
+<title>Printing-Related Configuration Parameters</title>
+
+<para>
+<indexterm><primary>global-level</primary></indexterm>
+<indexterm><primary>service-level</primary></indexterm>
+<indexterm><primary>printing behavior</primary></indexterm>
+There are a number of configuration parameters to control Samba's printing behavior. Please refer to the man
+page for &smb.conf; for an overview of these. As with other parameters, there are global-level (tagged with a
+<emphasis>G</emphasis> in the listings) and service-level (<emphasis>S</emphasis>) parameters.
+</para>
+
+<variablelist>
+	<varlistentry><term>Global Parameters</term>
+		<listitem><para> These <emphasis>may not</emphasis> go into
+		individual share definitions. If they go in by error,
+		the <command>testparm</command> utility can discover this
+		(if you run it) and tell you so.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>Service-Level Parameters</term>
+		<listitem><para> These may be specified in the
+		<smbconfsection name="[global]"/> section of &smb.conf;.
+		In this case they define the default behavior of all individual
+		or service-level shares (provided they do not have a different
+		setting defined for the same parameter, thus overriding the
+		global default).
+		</para></listitem>
+	</varlistentry>
+</variablelist>
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Simple Print Configuration</title>
+
+<para>
+<indexterm><primary>BSD Printing</primary></indexterm>
+<indexterm><primary>simple printing</primary></indexterm>
+<indexterm><primary>enables clients to print</primary></indexterm>
+<indexterm><primary>print environment</primary></indexterm>
+<link linkend="simpleprc">Simple Configuration with BSD Printing</link> shows a simple printing configuration.
+If you compare this with your own, you may find additional parameters that have been preconfigured by your OS
+vendor. Following is a discussion and explanation of the parameters. This example does not use many
+parameters.  However, in many environments these are enough to provide a valid &smb.conf; file that enables
+all clients to print.
+</para>
+
+<example id="simpleprc">
+<title>Simple Configuration with BSD Printing</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="printing">bsd</smbconfoption>
+<smbconfoption name="load printers">yes</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printable">yes</smbconfoption>
+<smbconfoption name="public">yes</smbconfoption>
+<smbconfoption name="writable">no</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>testparm</primary></indexterm>
+<indexterm><primary>misconfigured settings</primary></indexterm>
+<indexterm><primary>pager program</primary></indexterm>
+This is only an example configuration. Samba assigns default values to all configuration parameters. The
+defaults are conservative and sensible. When a parameter is specified in the &smb.conf; file, this overwrites
+the default value. The <command>testparm</command> utility when run as root is capable of reporting all
+settings, both default as well as &smb.conf; file settings. <command>Testparm</command> gives warnings for all
+misconfigured settings. The complete output is easily 360 lines and more, so you may want to pipe it through a
+pager program.
+</para>
+
+<para>  
+<indexterm><primary>configuration syntax</primary></indexterm>
+<indexterm><primary>syntax tolerates spelling errors</primary></indexterm>
+<indexterm><primary>case-insensitive</primary></indexterm>
+The syntax for the configuration file is easy to grasp. You should know that  is not very picky about its
+syntax. As has been explained elsewhere in this book, Samba tolerates some spelling errors (such as
+<smbconfoption name="browseable"/> instead of <smbconfoption name="browsable"/>), and spelling is
+case-insensitive. It is permissible to use <parameter>Yes/No</parameter> or <parameter>True/False</parameter>
+for Boolean settings. Lists of names may be separated by commas, spaces, or tabs.
+</para>
+
+<sect2>
+<title>Verifying Configuration with <command>testparm</command></title>
+
+<para>
+<indexterm><primary>printing-related settings</primary></indexterm>
+<indexterm><primary>lp</primary></indexterm>
+<indexterm><primary>print</primary></indexterm>
+<indexterm><primary>spool</primary></indexterm>
+<indexterm><primary>driver</primary></indexterm>
+<indexterm><primary>ports</primary></indexterm>
+<indexterm><primary>testparm</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>print configuration</primary></indexterm>
+<indexterm><primary>printer shares </primary></indexterm>
+<indexterm><primary>spooling path</primary></indexterm>
+To see all (or at least most) printing-related settings in Samba, including the implicitly used ones, try the
+command outlined below. This command greps for all occurrences of <constant>lp</constant>,
+<constant>print</constant>, <constant>spool</constant>, <constant>driver</constant>,
+<constant>ports</constant>, and <constant>[</constant> in <command>testparm</command>'s output. This provides
+a convenient overview of the running <command>smbd</command> print configuration. This command does not show
+individually created printer shares or the spooling paths they may use. Here is the output of my Samba setup,
+with settings shown in <link linkend="simpleprc">the example above</link>:
+<screen>
+&rootprompt;<userinput>testparm -s -v | egrep "(lp|print|spool|driver|ports|\[)"</userinput>
+ Load smb config files from /etc/samba/smb.conf
+ Processing section "[homes]"
+ Processing section "[printers]"
+ 
+ [global]
+        smb ports = 139 445
+        lpq cache time = 10
+        load printers = Yes
+        printcap name = /etc/printcap
+        disable spoolss = No
+        enumports command =
+        addprinter command = 
+        deleteprinter command = 
+        show add printer wizard = Yes
+        os2 driver map =
+        printer admin =
+        min print space = 0
+        max print jobs = 1000
+        printable = No
+        printing = bsd
+        print command = lpr -r -P'%p' %s
+        lpq command = lpq -P'%p'
+        lprm command = lprm -P'%p' %j
+        lppause command =
+        lpresume command =
+        printer name =
+        use client driver = No
+
+ [homes]
+
+ [printers]
+        path = /var/spool/samba
+        printable = Yes
+</screen>
+</para>
+
+<para>
+You can easily verify which settings were implicitly added by Samba's default behavior. <emphasis>Remember: it
+may be important in your future dealings with Samba.</emphasis>
+</para>
+
+<note><para>
+The <command>testparm</command> in Samba-3 behaves differently from that in 2.2.x: used without the
+<quote>-v</quote> switch, it only shows you the settings actually written into! To see the complete
+configuration used, add the <quote>-v</quote> parameter to testparm.
+</para></note>
+
+</sect2>
+
+<sect2>
+<title>Rapid Configuration Validation</title>
+
+<para> 
+<indexterm><primary>troubleshoot</primary></indexterm>
+<indexterm><primary>testparm</primary></indexterm>
+<indexterm><primary>parameters</primary></indexterm>
+<indexterm><primary>verify</primary></indexterm>
+Should you need to troubleshoot at any stage, please always come back to this point first and verify if
+<command>testparm</command> shows the parameters you expect. To give you a warning from personal experience,
+try to just comment out the <smbconfoption name="load printers"/> parameter. If your 2.2.x system behaves like
+mine, you'll see this:
+</para>
+
+<para><screen>
+&rootprompt;grep "load printers" /etc/samba/smb.conf
+        #  load printers = Yes
+        # This setting is commented out!!
+ 
+&rootprompt;testparm -v /etc/samba/smb.conf | egrep "(load printers)"
+        load printers = Yes
+</screen></para>
+
+<para>
+<indexterm><primary>commenting out setting</primary></indexterm>
+<indexterm><primary>publishing printers</primary></indexterm>
+I assumed that commenting out of this setting should prevent Samba from
+publishing my printers, but it still did. It took some time to figure out
+the reason. But I am no longer fooled ... at least not by this.
+<screen>
+&rootprompt;<userinput>grep -A1 "load printers" /etc/samba/smb.conf</userinput>
+        load printers = No
+        # The above setting is what I want!
+        #  load printers = Yes
+        # This setting is commented out!
+
+&rootprompt;<userinput>testparm -s -v smb.conf.simpleprinting | egrep "(load printers)"</userinput>
+        load printers = No
+</screen></para>
+
+<para>
+<indexterm><primary>explicitly set</primary></indexterm>
+Only when the parameter is explicitly set to <smbconfoption name="load printers">No</smbconfoption> would
+Samba conform with my intentions. So, my strong advice is:
+</para>
+
+<itemizedlist>
+	<listitem><para>Never rely on commented-out parameters.</para></listitem>
+
+	<listitem><para>Always set parameters explicitly as you intend them to
+	behave.</para></listitem>
+
+	<listitem><para>Use <command>testparm</command> to uncover hidden
+	settings that might not reflect your intentions.</para></listitem>
+</itemizedlist>
+
+<para>
+The following is the most minimal configuration file:
+<screen>
+&rootprompt;<userinput>cat /etc/samba/smb.conf-minimal</userinput>
+        [printers]
+</screen></para>
+
+<para>
+<indexterm><primary>testparm</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+This example should show that you can use <command>testparm</command> to test any Samba configuration file.
+Actually, we encourage you <emphasis>not</emphasis> to change your working system (unless you know exactly
+what you are doing). Don't rely on the assumption that changes will only take effect after you restart smbd!
+This is not the case. Samba rereads it every 60 seconds and on each new client connection. You might have to
+face changes for your production clients that you didn't intend to apply. You will now note a few more
+interesting things; <command>testparm</command> is useful to identify what the Samba print configuration would
+be if you used this minimalistic configuration. Here is what you can expect to find:
+<screen>
+&rootprompt;<userinput>testparm -v smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"</userinput>
+ Processing section "[printers]"
+ WARNING: [printers] service MUST be printable!
+ No path in service printers - using /tmp
+
+        lpq cache time = 10
+        load printers = Yes
+        printcap name = /etc/printcap
+        disable spoolss = No
+        enumports command =
+        addprinter command =
+        deleteprinter command =
+        show add printer wizard = Yes
+        os2 driver map =
+        printer admin =
+        min print space = 0
+        max print jobs = 1000
+        printable = No
+        printing = bsd
+        print command = lpr -r -P%p %s
+        lpq command = lpq -P%p
+        printer name =
+        use client driver = No
+
+ [printers]
+        printable = Yes
+</screen></para>
+
+<para>
+<command>testparm</command> issued two warnings:
+</para>
+
+<itemizedlist>
+	<listitem><para>We did not specify the <smbconfsection name="[printers]"/> section as printable.</para></listitem>
+	<listitem><para>We did not tell Samba which spool directory to use.</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>compile-time options</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+<indexterm><primary></primary></indexterm>
+<indexterm><primary></primary></indexterm>
+However, this was not fatal, and Samba will default to values that will work. Please, do not rely on this and
+do not use this example. This was included to encourage you to be careful to design and specify your setup to
+do precisely what you require. The outcome on your system may vary for some parameters given, since Samba may
+have been built with  different compile-time options. <emphasis>Warning:</emphasis> do not put a comment sign
+<emphasis>at the end</emphasis> of a valid line. It will cause the parameter to be ignored (just as if you had
+put the comment sign at the front). At first I regarded this as a bug in my Samba versions. But the man page
+clearly says: <literal>Internal whitespace in a parameter value is retained verbatim.</literal> This means
+that a line consisting of, for example,
+<smbconfblock>
+<smbconfcomment>This defines LPRng as the printing system</smbconfcomment>
+<smbconfoption name="printing"> lprng</smbconfoption>
+</smbconfblock>
+</para>
+
+<para>
+will regard the whole of the string after the <literal>=</literal> sign as the value you want to define. This
+is an invalid value that will be ignored, and a default value will be used in its place.
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Extended Printing Configuration</title>
+
+<para>
+<indexterm><primary>Extended BSD Printing</primary></indexterm>
+<indexterm><primary>BSD-style printing</primary></indexterm>
+<indexterm><primary>CUPS</primary></indexterm>
+<indexterm><primary>testparm</primary></indexterm>
+<link linkend="extbsdpr">Extended BSD Printing Configuration</link> shows a more verbose configuration for
+print-related settings in a BSD-style printing environment. What follows is a discussion and explanation of
+the various parameters. We chose to use BSD-style printing here because it is still the most commonly used
+system on legacy UNIX/Linux installations. New installations predominantly use CUPS, which is discussed in a
+separate chapter. The example explicitly names many parameters that do not need to be specified because they
+are set by default. You could use a much leaner &smb.conf; file, or you can use <command>testparm</command> or
+<command>SWAT</command> to optimize the &smb.conf; file to remove all parameters that are set at default.
+</para>
+
+<example id="extbsdpr">
+<title>Extended BSD Printing Configuration</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="printing">bsd</smbconfoption>
+<smbconfoption name="load printers">yes</smbconfoption>
+<smbconfoption name="show add printer wizard">yes</smbconfoption>
+<smbconfoption name="printcap name">/etc/printcap</smbconfoption>
+<smbconfoption name="printer admin">@ntadmin, root</smbconfoption>
+<smbconfoption name="max print jobs">100</smbconfoption>
+<smbconfoption name="lpq cache time">20</smbconfoption>
+<smbconfoption name="use client driver">no</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="printable">yes</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="browseable">no</smbconfoption>
+<smbconfoption name="guest ok">yes</smbconfoption>
+<smbconfoption name="public">yes</smbconfoption>
+<smbconfoption name="read only">yes</smbconfoption>
+<smbconfoption name="writable">no       </smbconfoption>
+
+<smbconfsection name="[my_printer_name]"/>
+<smbconfoption name="comment">Printer with Restricted Access</smbconfoption>
+<smbconfoption name="path">/var/spool/samba_my_printer</smbconfoption>
+<smbconfoption name="printer admin">kurt</smbconfoption>
+<smbconfoption name="browseable">yes</smbconfoption>
+<smbconfoption name="printable">yes</smbconfoption>
+<smbconfoption name="writable">no</smbconfoption>
+<smbconfoption name="hosts allow">0.0.0.0</smbconfoption>
+<smbconfoption name="hosts deny">turbo_xp, 10.160.50.23, 10.160.51.60</smbconfoption>
+<smbconfoption name="guest ok">no</smbconfoption>
+</smbconfblock></example>
+
+<para>
+<indexterm><primary></primary></indexterm>
+<indexterm><primary></primary></indexterm>
+<indexterm><primary></primary></indexterm>
+This is an example configuration. You may not find all the settings that are in the configuration file that
+was provided by the OS vendor. Samba configuration parameters, if not explicitly set, default to a sensible
+value.  To see all settings, as <constant>root</constant> use the <command>testparm</command> utility.
+<command>testparm</command> gives warnings for misconfigured settings.
+</para>
+
+<sect2>
+<title>Detailed Explanation Settings</title>
+
+<para>
+The following is a discussion of the settings from <link linkend="extbsdpr">Extended BSD Printing
+Configuration</link> <link linkend="extbsdpr">Extended BSD Printing Configuration</link>.
+</para>
+
+<sect3>
+<title>The [global] Section</title>
+
+<para>
+<indexterm><primary>global section</primary></indexterm>
+<indexterm><primary>special sections</primary></indexterm>
+<indexterm><primary>individual section</primary></indexterm>
+<indexterm><primary>share</primary></indexterm>
+The <smbconfsection name="[global]"/> section is one of four special sections (along with <smbconfsection
+name="[homes]"/>, <smbconfsection name="[printers]"/>, and <smbconfsection name="[print$]"/>). The
+<smbconfsection name="[global]"/> contains all parameters that apply to the server as a whole. It is the place
+for parameters that have only a global meaning. It may also contain service-level parameters that define
+default settings for all other sections and shares. This way you can simplify the configuration and avoid
+setting the same value repeatedly. (Within each individual section or share, you may, however, override these
+globally set share settings and specify other values).
+</para>
+
+<variablelist>
+	<varlistentry><term><smbconfoption name="printing">bsd </smbconfoption></term>
+		<listitem><para>
+<indexterm><primary>default print commands</primary></indexterm>
+<indexterm><primary>RFC 1179</primary></indexterm>
+<indexterm><primary>printing</primary></indexterm>
+<indexterm><primary>CUPS</primary></indexterm>
+<indexterm><primary>LPD</primary></indexterm>
+<indexterm><primary>LPRNG</primary></indexterm>
+<indexterm><primary>SYSV</primary></indexterm>
+<indexterm><primary>HPUX</primary></indexterm>
+<indexterm><primary>AIX</primary></indexterm>
+<indexterm><primary>QNX</primary></indexterm>
+<indexterm><primary>PLP</primary></indexterm>
+<indexterm><primary>queue control</primary></indexterm>
+		Causes Samba to use default print commands applicable for the BSD (also known as RFC 1179 style or LPR/LPD)
+		printing system. In general, the <parameter>printing</parameter> parameter informs Samba about the print
+		subsystem it should expect. Samba supports CUPS, LPD, LPRNG, SYSV, HPUX, AIX, QNX, and PLP. Each of these
+		systems defaults to a different <smbconfoption name="print command"/> (and other queue control commands).
+		</para>
+
+		<caution><para>
+<indexterm><primary>service-level</primary></indexterm>
+<indexterm><primary>SOFTQ printing system</primary></indexterm>
+		The <smbconfoption name="printing"/> parameter is normally a service-level parameter. Since it is included
+		here in the <smbconfsection name="[global]"/> section, it will take effect for all printer shares that are not
+		defined differently. Samba-3 no longer supports the SOFTQ printing system.
+		</para></caution>
+	</listitem></varlistentry>
+
+	<varlistentry><term><smbconfoption name="load printers">yes </smbconfoption></term>
+		<listitem><para>
+<indexterm><primary>printer shares</primary></indexterm>
+<indexterm><primary>printcap</primary></indexterm>
+<indexterm><primary>separate shares</primary></indexterm>
+<indexterm><primary>UNIX printer</primary></indexterm>
+		Tells Samba to create automatically all available printer shares. Available printer shares are discovered by
+		scanning the printcap file. All created printer shares are also loaded for browsing. If you use this
+		parameter, you do not need to specify separate shares for each printer. Each automatically created printer
+		share will clone the configuration options found in the <smbconfsection name="[printers]"/> section. (The
+		<parameter>load printers = no</parameter> setting will allow you to specify each UNIX printer you want to
+		share separately, leaving out some you do not want to be publicly visible and available).
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term><smbconfoption name="show add printer wizard">yes </smbconfoption></term>
+		<listitem><para>
+<indexterm><primary>Add Printer Wizard</primary></indexterm>
+<indexterm><primary>Printers</primary></indexterm>
+<indexterm><primary>Network Neighborhood</primary></indexterm>
+<indexterm><primary>net view</primary></indexterm>
+<indexterm><primary>uploaded driver</primary></indexterm>
+		Setting is normally enabled by default (even if the parameter is not specified in &smb.conf;).  It causes the
+		<guiicon>Add Printer Wizard</guiicon> icon to appear in the <guiicon>Printers</guiicon> folder of the Samba
+		host's share listing (as shown in <guiicon>Network Neighborhood</guiicon> or by the <command>net
+		view</command> command). To disable it, you need to explicitly set it to <constant>no</constant> (commenting
+		it out will not suffice). The <parameter>Add Printer Wizard</parameter> lets you upload a printer driver to
+		the <smbconfsection name="[print$]"/> share and associate it with a printer (if the respective queue exists
+		before the action), or exchange a printer's driver for any other previously uploaded driver.
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term><smbconfoption name="max print jobs">100 </smbconfoption></term>
+		<listitem><para>
+<indexterm><primary>print jobs</primary></indexterm>
+		Sets the upper limit to 100 print jobs being active on the Samba server at any one time. Should a client
+		submit a job that exceeds this number, a "no more space available on server" type of error message will be
+		returned by Samba to the client. A setting of zero (the default) means there is <emphasis>no</emphasis> limit
+		at all.
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term><smbconfoption name="printcap name">/etc/printcap </smbconfoption></term>
+		<listitem><para>
+<indexterm><primary>CUPS</primary></indexterm>
+<indexterm><primary>available printerd</primary></indexterm>
+<indexterm><primary>printcap</primary></indexterm>
+		Tells Samba where to look for a list of available printer names. Where CUPS is used, make sure that a printcap
+		file is written. This is controlled by the <constant>Printcap</constant> directive in the
+		<filename>cupsd.conf</filename> file.
+	</para></listitem></varlistentry>
+
+	<varlistentry><term><smbconfoption name="printer admin">@ntadmin </smbconfoption></term>
+		<listitem><para>
+<indexterm><primary>add drivers</primary></indexterm>
+<indexterm><primary>/etc/group</primary></indexterm>
+<indexterm><primary>printer share</primary></indexterm>
+<indexterm><primary>set printer properties</primary></indexterm>
+		Members of the ntadmin group should be able to add drivers and set printer properties
+		(<constant>ntadmin</constant> is only an example name; it needs to be a valid UNIX group name); root is
+		implicitly always a <smbconfoption name="printer admin"/>. The <literal>@</literal> sign precedes group names
+		in the <filename>/etc/group</filename>. A printer admin can do anything to printers via the remote
+		administration interfaces offered by MS-RPC (see <link linkend="cups-msrpc">Printing Developments Since
+		Samba-2.2</link>).  In larger installations, the <smbconfoption name="printer admin"/> parameter is normally a
+		per-share parameter. This permits different groups to administer each printer share.
+	</para></listitem></varlistentry>
+
+	<varlistentry><term><smbconfoption name="lpq cache time">20 </smbconfoption></term>
+		<listitem><para>
+<indexterm><primary>lpq command</primary></indexterm>
+<indexterm><primary>lpq cache time</primary></indexterm>
+		Controls the cache time for the results of the lpq command. It prevents the lpq command being called too often
+		and reduces the load on a heavily used print server.
+	</para></listitem></varlistentry>
+
+	<varlistentry><term><smbconfoption name="use client driver">no </smbconfoption></term>
+		<listitem><para>
+<indexterm><primary>Windows NT/200x/XP</primary></indexterm>
+		If set to <constant>yes</constant>, only takes effect for Windows NT/200x/XP clients (and not for Win
+		95/98/ME). Its default value is <constant>No</constant> (or <constant>False</constant>).  It must
+		<emphasis>not</emphasis> be enabled on print shares (with a <constant>yes</constant> or
+		<constant>true</constant> setting) that have valid drivers installed on the Samba server. For more detailed
+		explanations, see the &smb.conf; man page.
+	</para></listitem></varlistentry>
+</variablelist>
+
+</sect3>
+
+<sect3 id="ptrsect">
+<title>The [printers] Section</title>
+
+<para>
+<indexterm><primary>printers section</primary></indexterm>
+<indexterm><primary>printcap</primary></indexterm>
+The printers section is the second special section. If a section with this name appears in the &smb.conf;,
+users are able to connect to any printer specified in the Samba host's printcap file, because Samba on startup
+then creates a printer share for every printer name it finds in the printcap file. You could regard this
+section as a convenient shortcut to share all printers with minimal configuration. It is also a container for
+settings that should apply as default to all printers. (For more details, see the &smb.conf; man page.)
+Settings inside this container must be share-level parameters.
+</para>
+
+<variablelist>
+	<varlistentry><term><smbconfoption name="comment">All printers </smbconfoption></term>
+		<listitem><para>
+		The <smbconfoption name="comment"/> is shown next to the share if
+		a client queries the server, either via <guiicon>Network Neighborhood</guiicon> or with
+		the <command>net view</command> command, to list available shares.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="printable">yes </smbconfoption></term>
+		<listitem><para>
+		The <smbconfsection name="[printers]"/> service <emphasis>must</emphasis>
+		be declared as printable. If you specify otherwise, smbd will refuse to load  at
+		startup. This parameter allows connected clients to open, write to, and submit spool files
+		into the directory specified with the <smbconfoption name="path"/>
+		parameter for this service. It is used by Samba to differentiate printer shares from
+		file shares. 
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="path">/var/spool/samba </smbconfoption></term>
+		<listitem><para>
+		Must point to a directory used by Samba to spool incoming print files. <emphasis>It
+		must not be the same as the spool directory specified in the configuration of your UNIX
+		print subsystem!</emphasis> The path typically points to a directory that is world
+		writable, with the <emphasis>sticky</emphasis> bit set to it.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="browseable">no </smbconfoption></term>
+		<listitem><para>
+		Is always set to <constant>no</constant> if
+		<smbconfoption name="printable">yes</smbconfoption>. It makes
+		the <smbconfsection name="[printer]"/> share itself invisible in the list of
+		available shares in a <command>net view</command> command or in the Explorer browse
+		list. (You will of course see the individual printers.)
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="guest ok">yes </smbconfoption></term>
+		<listitem><para>
+		If this parameter is set to <constant>yes</constant>, no password is required to
+		connect to the printer's service. Access will be granted with the privileges of the
+		<smbconfoption name="guest account"/>. On many systems the guest
+		account will map to a user named "nobody." This user will usually be found
+		in the UNIX passwd file with an empty password, but with no valid UNIX login. On some
+		systems the guest account might not have the privilege to be able to print. Test this
+		by logging in as your guest user using <command>su - guest</command> and run a system
+		print command like:
+		</para>
+	
+		<para>
+		<userinput>lpr -P printername /etc/motd</userinput>
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="public">yes </smbconfoption></term>
+		<listitem><para>
+		Is a synonym for <smbconfoption name="guest ok">yes</smbconfoption>.
+		Since we have <smbconfoption name="guest ok">yes</smbconfoption>, it
+		really does not need to be here. (This leads to the interesting question, <quote>What if I
+		by accident have two contradictory settings for the same share?</quote> The answer is that the
+		last one encountered by Samba wins. <command>testparm</command> does not complain about different settings
+		of the same parameter for the same share. You can test this by setting up multiple
+		lines for the <parameter>guest account</parameter> parameter with different usernames,
+		and then run testparm to see which one is actually used by Samba.)
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="read only">yes </smbconfoption></term>
+		<listitem><para>
+		Normally (for other types of shares) prevents users from creating or modifying files
+		in the service's directory. However, in a <emphasis>printable</emphasis> service, it is
+		<emphasis>always</emphasis> allowed to write to the directory (if user privileges allow the
+		connection), but only via print spooling operations. Normal write operations are not permitted.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="writable">no </smbconfoption></term>
+		<listitem><para>
+		Is a synonym for <smbconfoption name="read only">yes</smbconfoption>.
+		</para></listitem>
+	</varlistentry>
+</variablelist>
+</sect3>
+
+<sect3>
+<title>Any [my_printer_name] Section</title>
+
+<para>
+<indexterm><primary>loading printer drivers</primary></indexterm>
+<indexterm><primary>name conflict</primary></indexterm>
+If a <parameter>[my_printer_name]</parameter> section appears in the &smb.conf; file, which includes the
+parameter <smbconfoption name="printable">yes</smbconfoption> Samba will configure it as a printer share.
+Windows 9x/Me clients may have problems with connecting or loading printer drivers if the share name has more
+than eight characters. Do not name a printer share with a name that may conflict with an existing user or file
+share name. On client connection requests, Samba always tries to find file shares with that name first. If it
+finds one, it will connect to this and will not connect to a printer with the same name!
+</para>
+
+<?latex \newpage ?>
+<variablelist>
+	<varlistentry><term><smbconfoption name="comment">Printer with Restricted Access </smbconfoption></term>
+		<listitem><para>
+		The comment says it all.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="path">/var/spool/samba_my_printer </smbconfoption></term>
+		<listitem><para>
+		Sets the spooling area for this printer to a directory other than the default. It is not
+		necessary to set it differently, but the option is available.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="printer admin">kurt </smbconfoption></term>
+		<listitem><para>
+		The printer admin definition is different for this explicitly defined printer share from the general
+		<smbconfsection name="[printers]"/> share. It is not a requirement; we did it to show that it is possible.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="browseable">yes </smbconfoption></term>
+		<listitem><para>
+		This makes the printer browseable so the clients may conveniently find it when browsing the
+		<guiicon>Network Neighborhood</guiicon>.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="printable">yes </smbconfoption></term>
+		<listitem><para>
+		See <link linkend="ptrsect">Section 20.4.1.2</link>.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="writable">no </smbconfoption></term>
+		<listitem><para>
+		See <link linkend="ptrsect">Section 20.4.1.2</link>.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="hosts allow">10.160.50.,10.160.51. </smbconfoption></term>
+		<listitem><para>
+		Here we exercise a certain degree of access control by using the <smbconfoption name="hosts allow"/>
+		and <smbconfoption name="hosts deny"/> parameters. This is not by any means a safe bet. It is not a
+		way to secure your printers. This line accepts all clients from a certain subnet in a first evaluation of
+		access control.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="hosts deny">turbo_xp,10.160.50.23,10.160.51.60 </smbconfoption></term>
+		<listitem><para>
+		All listed hosts are not allowed here (even if they belong to the allowed subnets). As
+		you can see, you could name IP addresses as well as NetBIOS hostnames here.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="guest ok">no </smbconfoption></term>
+		<listitem><para>
+		This printer is not open for the guest account.
+		</para></listitem>
+	</varlistentry>
+</variablelist>
+</sect3>
+
+<sect3>
+<title>Print Commands</title>
+
+<para>
+<indexterm><primary>print command</primary></indexterm>
+<indexterm><primary>print subsystem</primary></indexterm>
+<indexterm><primary>temporary location</primary></indexterm>
+<indexterm><primary>shell scripts</primary></indexterm>
+In each section defining a printer (or in the <smbconfsection name="[printers]"/> section),
+a <parameter>print command</parameter> parameter may be defined. It sets a command to process the files
+that have been placed into the Samba print spool directory for that printer. (That spool directory was,
+if you remember, set up with the <smbconfoption name="path"/> parameter). Typically,
+this command will submit the spool file to the Samba host's print subsystem, using the suitable system
+print command. But there is no requirement that this needs to be the case. For debugging or
+some other reason, you may want to do something completely different than print the file. An example is a
+command that just copies the print file to a temporary location for further investigation when you need
+to debug printing. If you craft your own print commands (or even develop print command shell scripts),
+make sure you pay attention to the need to remove the files from the Samba spool directory. Otherwise,
+your hard disk may soon suffer from shortage of free space.
+</para>
+</sect3>
+
+<sect3>
+<title>Default UNIX System Printing Commands</title>
+
+<para>
+<indexterm><primary>default print command</primary></indexterm>
+You learned earlier that Samba, in most cases, uses its built-in settings for many parameters if it cannot
+find an explicitly stated one in its configuration file. The same is true for the <smbconfoption name="print
+command"/>. The default print command varies depending on the <smbconfoption name="printing"/> parameter
+setting. In the commands listed in <link linkend="printOptions">Default Printing Settings</link> , you will
+notice some parameters of the form <emphasis>%X</emphasis> where <emphasis>X</emphasis> is <emphasis>p, s,
+J</emphasis>, and so on. These letters stand for printer name, spool file, and job ID, respectively.  They are
+explained in more detail in <link linkend="printOptions">Default Printing Settings</link> presents an overview
+of key printing options but excludes the special case of CUPS, is discussed in <link
+linkend="CUPS-printing">CUPS Printing Support</link>.
+</para>
+
+<table frame='all' id="printOptions">
+	<title>Default Printing Settings</title>
+	<tgroup cols='2' align='left' colsep='1' rowsep='1'>
+		<colspec align="left"/>
+		<colspec align="left"/>
+	<thead>
+		<row>
+		<entry>Setting</entry>
+		<entry>Default Printing Commands</entry>
+		</row>
+	</thead>
+	<tbody>
+		<row>
+		<entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
+		<entry>print command is <command>lpr -r -P%p %s</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
+		<entry>print command is <command>lp -c -P%p %s; rm %s</command></entry>
+		</row>
+		<row>
+		<entry> <smbconfoption name="printing">qnx</smbconfoption></entry>
+		<entry>print command is <command>lp -r -P%p -s %s</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
+		<entry>lpq command is <command>lpq -P%p</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
+		<entry>lpq command is <command>lpstat -o%p</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">qnx</smbconfoption></entry>
+		<entry>lpq command is <command>lpq -P%p</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
+		<entry>lprm command is <command>lprm -P%p %j</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
+		<entry>lprm command is <command>cancel %p-%j</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">qnx</smbconfoption></entry>
+		<entry>lprm command is <command>cancel %p-%j</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
+		<entry>lppause command is <command>lp -i %p-%j -H hold</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
+		<entry>lppause command   (...is empty)</entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">qnx</smbconfoption></entry>
+		<entry>lppause command   (...is empty)</entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
+		<entry>lpresume command is <command>lp -i %p-%j -H resume</command></entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
+		<entry>lpresume command   (...is empty)</entry>
+		</row>
+		<row>
+		<entry><smbconfoption name="printing">qnx</smbconfoption></entry>
+		<entry>lpresume command   (...is empty)</entry>
+		</row>
+	</tbody>
+	</tgroup>
+</table>
+
+<para>
+<indexterm><primary>CUPS API</primary></indexterm>
+<indexterm><primary>cupsd.conf</primary></indexterm>
+<indexterm><primary>autogenerated printcap</primary></indexterm>
+<indexterm><primary>libcups</primary></indexterm>
+For <parameter>printing = CUPS</parameter>, if Samba is compiled against libcups, it uses the CUPS API to
+submit jobs. (It is a good idea also to set <smbconfoption name="printcap">cups</smbconfoption> in case your
+<filename>cupsd.conf</filename> is set to write its autogenerated printcap file to an unusual place).
+Otherwise, Samba maps to the System V printing commands with the -oraw option for printing; that is, it uses
+<command>lp -c -d%p -oraw; rm %s</command>. With <parameter>printing = cups</parameter>, and if Samba is
+compiled against libcups, any manually set print command will be ignored!
+</para>
+
+</sect3>
+
+<sect3>
+<title>Custom Print Commands</title>
+
+<para>
+<indexterm><primary>print job</primary></indexterm>
+<indexterm><primary>spooling</primary></indexterm>
+After a print job has finished spooling to a service, the <smbconfoption name="print command"/> will be used
+by Samba via a system() call to process the spool file. Usually the command specified will submit the spool
+file to the host's printing subsystem. But there is no requirement at all that this must be the case. The
+print subsystem may not remove the spool file on its own, so whatever command you specify, you should ensure
+that the spool file is deleted after it has been processed.
+</para>
+
+<para>
+<indexterm><primary>traditional printing</primary></indexterm>
+<indexterm><primary>customized print commands</primary></indexterm>
+<indexterm><primary>built-in commands</primary></indexterm>
+<indexterm><primary>macros</primary></indexterm>
+There is no difficulty with using your own customized print commands with the traditional printing systems.
+However, if you do not wish to roll your own, you should be well informed about the default built-in commands
+that Samba uses for each printing subsystem (see <link linkend="printOptions">Default Printing
+Settings</link>). In all the commands listed in the last paragraphs, you see parameters of the form
+<emphasis>%X</emphasis>. These are <emphasis>macros</emphasis>, or shortcuts, used as placeholders for the
+names of real objects. At the time of running a command with such a placeholder, Samba will insert the
+appropriate value automatically. Print commands can handle all Samba macro substitutions. In regard to
+printing, the following ones do have special relevance:
+</para>
+
+<itemizedlist>
+	<listitem><para><parameter>%s, %f</parameter> &smbmdash; the path to the spool file name.</para></listitem>
+	<listitem><para><parameter>%p</parameter> &smbmdash; the appropriate printer name.</para></listitem>
+	<listitem><para><parameter>%J</parameter> &smbmdash; the job name as transmitted by the client.</para></listitem>
+	<listitem><para><parameter>%c</parameter> &smbmdash; the number of printed pages of the spooled job (if known).</para></listitem>
+	<listitem><para><parameter>%z</parameter> &smbmdash; the size of the spooled print job (in bytes).</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>default printer</primary></indexterm>
+The print command must contain at least one occurrence of <parameter>%s</parameter> or
+<parameter>%f</parameter>. The <parameter>%p</parameter> is optional. If no printer name is supplied,
+the <parameter>%p</parameter> will be silently removed from the print command. In this case, the job is
+sent to the default printer.
+</para>
+
+<para>
+<indexterm><primary>global print command</primary></indexterm>
+<indexterm><primary>spool files</primary></indexterm>
+If specified in the <smbconfsection name="[global]"/> section, the print command given will be
+used for any printable service that does not have its own print command specified. If there is neither a
+specified print command for a printable service nor a global print command, spool files will be created
+but not processed! Most importantly, print files will not be removed, so they will consume disk space.
+</para>
+
+<para>
+<indexterm><primary>nobody account</primary></indexterm>
+<indexterm><primary>guest account</primary></indexterm>
+Printing may fail on some UNIX systems when using the <emphasis>nobody</emphasis> account. If this happens, create an
+alternative guest account and give it the privilege to print. Set up this guest account in the
+<smbconfsection name="[global]"/> section with the <parameter>guest account</parameter> parameter.
+</para>
+
+<para>
+<indexterm><primary>environment variables</primary></indexterm>
+<indexterm><primary>print commands</primary></indexterm>
+<indexterm><primary>print job</primary></indexterm>
+You can form quite complex print commands. You need to realize that print commands are just
+passed to a UNIX shell. The shell is able to expand the included environment variables as
+usual. (The syntax to include a UNIX environment variable <parameter>$variable</parameter>
+in the Samba print command is <parameter>%$variable</parameter>.) To give you a working
+<smbconfoption name="print command"/> example, the following will log a print job
+to <filename>/tmp/print.log</filename>, print the file, then remove it. The semicolon (<quote>;</quote>
+is the usual separator for commands in shell scripts:
+</para>
+
+<para><smbconfblock>
+	<smbconfoption name="print command">echo Printing %s &gt;&gt; /tmp/print.log; lpr -P %p %s; rm %s</smbconfoption>
+</smbconfblock></para>
+
+<para>
+You may have to vary your own command considerably from this example depending on how you normally print
+files on your system. The default for the <smbconfoption name="print command"/>
+parameter varies depending on the setting of the <smbconfoption name="printing"/>
+parameter. Another example is:
+</para>
+
+<para><smbconfblock>
+<smbconfoption name="print command">/usr/local/samba/bin/myprintscript %p %s</smbconfoption>
+</smbconfblock></para>
+</sect3>
+</sect2>
+</sect1>
+
+<sect1 id="cups-msrpc">
+<title>Printing Developments Since Samba-2.2</title>
+
+<para>
+<indexterm><primary>LanMan</primary></indexterm>
+<indexterm><primary>MS-RPC</primary></indexterm>
+<indexterm><primary>SPOOLSS</primary></indexterm>
+Prior to Samba-2.2.x, print server support for Windows clients was limited to <emphasis>LanMan</emphasis>
+printing calls. This is the same protocol level as Windows 9x/Me PCs offer when they share printers.
+Beginning with the 2.2.0 release, Samba started to support the native Windows NT printing mechanisms. These
+are implemented via <emphasis>MS-RPC</emphasis> (Remote Procedure Calls).
+MS-RPCs use the <emphasis>SPOOLSS</emphasis> named pipe for all printing.
+</para>
+
+<para>
+The additional functionality provided by the new SPOOLSS support includes:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+<indexterm><primary>Point'n'Print</primary></indexterm>
+	Support for downloading printer driver files to Windows 95/98/NT/2000 clients upon
+	demand (<emphasis>Point'n'Print</emphasis>).
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>Add Printer Wizard</primary></indexterm>
+	Uploading of printer drivers via the Windows NT <emphasis>Add Printer Wizard</emphasis> (APW)
+	or the <ulink url="http://imprints.sourceforge.net/">Imprints</ulink> tool set.
+	</para></listitem>
+
+	<listitem><para>	
+<indexterm><primary>MS-RPC</primary></indexterm>
+<indexterm><primary>printing calls</primary></indexterm>
+<indexterm><primary>StartDocPrinter</primary></indexterm>
+<indexterm><primary>EnumJobs()</primary></indexterm>
+<indexterm><primary>Win32 printing API</primary></indexterm>
+	Support for the native MS-RPC printing calls such as StartDocPrinter, EnumJobs(), and so on. (See the
+	<ulink url="http://msdn.microsoft.com/">MSDN documentation</ulink> for more information on the
+	Win32 printing API).
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>ACL</primary></indexterm>
+<indexterm><primary>printer objects</primary></indexterm>
+	Support for NT Access Control Lists (ACL) on printer objects.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>printer queue</primary></indexterm>
+	Improved support for printer queue manipulation through the use of internal databases for spooled
+	job information (implemented by various <filename>*.tdb</filename> files).
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+A benefit of updating is that Samba-3 is able to publish its printers to Active Directory (or LDAP).
+</para>
+
+<para>
+<indexterm><primary>publish printers</primary></indexterm>
+A fundamental difference exists between MS Windows NT print servers and Samba operation. Windows NT
+permits the installation of local printers that are not shared. This is an artifact of the fact that
+any Windows NT machine (server or client) may be used by a user as a workstation. Samba will publish all
+printers that are made available, either by default or by specific declaration via printer-specific shares.
+</para>
+
+<para>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>MS-RPC</primary></indexterm>
+<indexterm><primary>Everyone group</primary></indexterm>
+<indexterm><primary>privileges</primary></indexterm>
+<indexterm><primary>printer default permissions</primary></indexterm>
+Windows NT/200x/XP Professional clients do not have to use the standard SMB printer share; they can
+print directly to any printer on another Windows NT host using MS-RPC. This, of course, assumes that
+the client has the necessary privileges on the remote host that serves the printer resource. The
+default permissions assigned by Windows NT to a printer gives the print permissions to the well-known
+<emphasis>Everyone</emphasis> group. (The older clients of type Windows 9x/Me can only print to shared
+printers.)
+</para>
+
+<sect2>
+<title>Point'n'Print Client Drivers on Samba Servers</title>
+
+<para>
+<indexterm><primary>printer drivers</primary></indexterm>
+There is much confusion about what all this means. The question is often asked, <quote>Is it or is
+it not necessary for printer drivers to be installed on a Samba host in order to support printing from
+Windows clients?</quote> The answer to this is no, it is not necessary.
+</para>
+
+<para>
+<indexterm><primary>install drivers</primary></indexterm>
+<indexterm><primary>print queue</primary></indexterm>
+Windows NT/2000 clients can, of course, also run their APW to install drivers <emphasis>locally</emphasis>
+(which then connect to a Samba-served print queue). This is the same method used by Windows 9x/Me
+clients. (However, a bug existed in Samba 2.2.0 that made Windows NT/2000 clients
+require that the Samba server possess a valid driver for the printer. This was fixed in Samba 2.2.1).
+</para>
+
+<para>
+<indexterm><primary>printer drivers</primary></indexterm>
+<indexterm><primary>uploading</primary></indexterm>
+But it is a new capability to install the printer drivers into the <smbconfsection name="[print$]"/>
+share of the Samba server, and a big convenience, too. Then <emphasis>all</emphasis> clients
+(including 95/98/ME) get the driver installed when they first connect to this printer share. The
+<emphasis>uploading</emphasis> or <emphasis>depositing</emphasis> of the driver into this
+<smbconfsection name="[print$]"/> share and the following binding of this driver to an existing
+Samba printer share can be achieved by different means:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Running the <emphasis>APW</emphasis> on an NT/200x/XP Professional client (this does not work from 95/98/ME clients).
+	</para></listitem>
+
+	<listitem><para>
+	Using the <emphasis>Imprints</emphasis> toolset.
+	</para></listitem>
+
+	<listitem><para>
+	Using the <emphasis>smbclient</emphasis> and <emphasis>rpcclient</emphasis> command-line tools.
+	</para></listitem>
+
+	<listitem><para>
+	Using <emphasis>cupsaddsmb</emphasis> (only works for the CUPS printing system, not for LPR/LPD, LPRng, and so on).
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>uploaded drivers</primary></indexterm>
+<indexterm><primary>Point'n'Print</primary></indexterm>
+Samba does not use these uploaded drivers in any way to process spooled files. These drivers are utilized
+entirely by the clients who download and install them via the <quote>Point'n'Print</quote> mechanism
+supported by Samba. The clients use these drivers to generate print files in the format the printer
+(or the UNIX print system) requires. Print files received by Samba are handed over to the UNIX printing
+system, which is responsible for all further processing, as needed.
+</para>
+</sect2>
+
+<sect2>
+<title>The Obsoleted [printer$] Section</title>
+
+	<para>
+<indexterm><primary>printer$ share</primary></indexterm>
+<indexterm><primary>printer driver</primary></indexterm>
+	Versions of Samba prior to 2.2 made it possible to use a share named <parameter>[printer$]</parameter>. This
+	name was taken from the same named service created by Windows 9x/Me clients when a printer was shared by them.
+	Windows 9x/Me printer servers always have a <smbconfsection name="[printer$]"/> service that provides
+	read-only access (with no password required) to support printer driver downloads. However, Samba's initial
+	implementation allowed for a parameter named <parameter>printer driver location</parameter> to be used on a
+	per-share basis. This specified the location of the driver files associated with that printer. Another
+	parameter named <parameter>printer driver</parameter> provided a means of defining the printer driver name to
+	be sent to the client.
+	</para>
+
+	<para>
+<indexterm><primary>printer driver file</primary></indexterm>
+<indexterm><primary>read-write access</primary></indexterm>
+<indexterm><primary>ACLs</primary></indexterm>
+	These parameters, including the <parameter>printer driver file</parameter> parameter,
+	are now removed and cannot be used in installations of Samba-3. The share name
+	<smbconfsection name="[print$]"/> is now used for the location of downloadable printer
+	drivers. It is taken from the <smbconfsection name="[print$]"/> service created
+	by Windows NT PCs when a printer is shared by them. Windows NT print servers always have a
+	<smbconfsection name="[print$]"/> service that provides read-write access (in the context
+	of its ACLs) to support printer driver downloads and uploads. This does not mean Windows
+	9x/Me clients are now thrown aside. They can use Samba's <smbconfsection name="[print$]"/>
+	share support just fine.
+	</para>
+</sect2>
+
+<sect2>
+<title>Creating the [print$] Share</title>
+
+<para>
+<indexterm><primary>printer driver</primary></indexterm>
+In order to support the uploading and downloading of printer driver files, you must first configure a
+file share named <smbconfsection name="[print$]"/>. The public name of this share is hard coded
+in the MS Windows clients. It cannot be renamed, since Windows clients are programmed to search for a
+service of exactly this name if they want to retrieve printer driver files.
+</para>
+
+<para>
+You should modify the server's file to add the global parameters and create the
+<smbconfsection name="[print$]"/> file share (of course, some of the parameter values, such
+as <smbconfoption name="path"/>, are arbitrary and should be replaced with appropriate values for your
+site). See <link linkend="prtdollar">[print\$] Example</link>.
+</para>
+
+<example id="prtdollar">
+<title>[print$] Example</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfcomment>members of the ntadmin group should be able to add drivers and set</smbconfcomment>
+<smbconfcomment>printer properties. root is implicitly always a 'printer admin'.</smbconfcomment>
+<smbconfoption name="printer admin">@ntadmin</smbconfoption>
+<smbconfcomment>...</smbconfcomment>
+
+<smbconfsection name="[printers]"/>
+<smbconfcomment>...</smbconfcomment>
+
+<smbconfsection name="[print$]"/>
+<smbconfoption name="comment">Printer Driver Download Area</smbconfoption>
+<smbconfoption name="path">/etc/samba/drivers</smbconfoption>
+<smbconfoption name="browseable">yes</smbconfoption>
+<smbconfoption name="guest ok">yes</smbconfoption>
+<smbconfoption name="read only">yes</smbconfoption>
+<smbconfoption name="write list">@ntadmin, root</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+Of course, you also need to ensure that the directory named by the
+<smbconfoption name="path"/> parameter exists on the UNIX file system.
+</para>
+
+</sect2>
+
+<sect2>
+<title>[print$] Stanza Parameters</title>
+
+<para>
+<indexterm><primary>special section</primary></indexterm>
+<indexterm><primary>special stanza</primary></indexterm>
+<indexterm><primary>potential printer</primary></indexterm>
+<indexterm><primary>driver download</primary></indexterm>
+<indexterm><primary>local print driver</primary></indexterm>
+The <smbconfsection name="[print$]"/> is a special section in &smb.conf;. It contains settings relevant to
+potential printer driver download and is used by Windows clients for local print driver installation.
+The following parameters are frequently needed in this share section:
+</para>
+
+<variablelist>
+	<varlistentry><term><smbconfoption name="comment">Printer Driver Download Area </smbconfoption></term>
+		<listitem><para>
+		The comment appears next to the share name if it is listed in a share list (usually Windows
+		clients will not see it, but it will also appear up in a <command>smbclient -L sambaserver
+		</command> output).
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="path">/etc/samba/printers </smbconfoption></term>
+		<listitem><para>
+		The path to the location of the Windows driver file deposit from the UNIX point of view.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="browseable">no </smbconfoption></term>
+		<listitem><para>
+		Makes the <smbconfsection name="[print$]"/> share invisible to clients from the
+		<guimenu>Network Neighborhood</guimenu>. By excuting from a <command>cmd</command> shell:
+<screen>
+&dosprompt; <command>net use g:\\sambaserver\print$</command>
+</screen>
+		 you can still mount it from any client. This can also be done from the
+		<guimenu>Connect network drive menu></guimenu> from Windows Explorer.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="guest ok">yes </smbconfoption></term>
+		<listitem><para>
+		Gives read-only access to this share for all guest users. Access may be granted to
+		download and install printer drivers on clients. The requirement for <parameter>guest ok
+		= yes</parameter> depends on how your site is configured. If users will be guaranteed
+		to have an account on the Samba host, then this is a non-issue.
+		</para>
+
+		<note><para> 
+		If all your Windows NT users are guaranteed to be authenticated by the Samba server
+		(for example, if Samba authenticates via an NT domain server and the user has already been
+		validated by the domain controller in order to log on to the Windows NT session), then guest
+		access is not necessary. Of course, in a workgroup environment where you just want
+		to print without worrying about silly accounts and security, then configure the share for
+		guest access. You should consider adding <smbconfoption name="map to guest">Bad	User</smbconfoption>
+		in the <smbconfsection name="[global]"/> section as well. Make sure you understand what this
+		parameter does before using it.
+		</para></note>
+		</listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="read only">yes </smbconfoption></term>
+		<listitem><para>
+		Because we do not want everybody to upload driver files (or even change driver settings),
+		we tagged this share as not writable.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term><smbconfoption name="write list">@ntadmin, root </smbconfoption></term>
+		<listitem><para>
+		The <smbconfsection name="[print$]"/> was made read-only by the previous
+		setting so we should create a <parameter>write list</parameter> entry also. UNIX
+		groups are denoted with a leading <quote>@</quote> character. Users listed here are allowed
+		write-access (as an exception to the general public's read-only access), which they need to
+		update files on the share. Normally, you will want to name only administrative-level user
+		account in this setting. Check the file system permissions to make sure these accounts
+		can copy files to the share. If this is a non-root account, then the account should also
+		be mentioned in the global <smbconfoption name="printer admin"/>
+		parameter. See the &smb.conf; man page for more information on configuring file shares.
+		</para></listitem>
+	</varlistentry>
+</variablelist>
+
+</sect2>
+
+<sect2>
+<title>The [print$] Share Directory</title>
+
+<para>
+In order for a Windows NT print server to support the downloading of driver files by multiple client
+architectures, you must create several subdirectories within the <smbconfsection name="[print$]"/>
+service (i.e., the UNIX directory named by the <smbconfoption name="path"/>
+parameter). These correspond to each of the supported client architectures. Samba follows this model as
+well. Just like the name of the <smbconfsection name="[print$]"/> share itself, the subdirectories
+must be exactly the names listed below (you may leave out the subdirectories of architectures you do
+not need to support).
+</para>
+
+<para>
+Therefore, create a directory tree below the
+<smbconfsection name="[print$]"/> share for each architecture you wish
+to support like this:
+<programlisting>
+[print$]--+
+          |--W32X86           # serves drivers to Windows NT x86
+          |--WIN40            # serves drivers to Windows 95/98
+          |--W32ALPHA         # serves drivers to Windows NT Alpha_AXP
+          |--W32MIPS          # serves drivers to Windows NT R4000
+          |--W32PPC           # serves drivers to Windows NT PowerPC
+</programlisting>
+</para>
+
+<important><title>Required Permissions</title>
+	<para>
+	In order to add a new driver to your Samba host, one of two conditions must hold true:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		The account used to connect to the Samba host must have a UID of 0 (i.e., a root account).
+		</para></listitem>
+
+		<listitem><para>
+		The account used to connect to the Samba host must be named in the <emphasis>printer admin</emphasis> list.
+		</para></listitem>
+	</itemizedlist>
+
+	<para>
+	Of course, the connected account must still have write access to add files to the subdirectories beneath
+	<smbconfsection name="[print$]"/>. Remember that all file shares are set to <quote>read-only</quote> by default.
+	</para>
+</important>
+
+<para>
+Once you have created the required <smbconfsection name="[print$]"/> service and
+associated subdirectories, go to a Windows NT 4.0/200x/XP client workstation. Open <guiicon>Network
+Neighborhood</guiicon> or <guiicon>My Network Places</guiicon> and browse for the Samba host. Once you
+have located the server, navigate to its <guiicon>Printers and Faxes</guiicon> folder. You should see
+an initial listing of printers that matches the printer shares defined on your Samba host.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Installing Drivers into [print$]</title>
+
+<para>
+Have you successfully created the <smbconfsection name="[print$]"/> share in &smb.conf;, and have you forced
+Samba to reread its &smb.conf; file? Good. But you are not yet ready to use the new facility. The client
+driver files need to be installed into this share. So far, it is still an empty share. Unfortunately, it is
+not enough to just copy the driver files over. They need to be correctly installed so that appropriate records
+for each driver will exist in the Samba internal databases so it can provide the correct drivers as they are
+requested from MS Windows clients. And that is a bit tricky, to say the least. We now discuss two alternative
+ways to install the drivers into <smbconfsection name="[print$]"/>:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Using the Samba command-line utility <command>rpcclient</command> with its various subcommands (here,
+	<command>adddriver</command> and <command>setdriver</command>) from any UNIX workstation.
+	</para></listitem>
+
+	<listitem><para>
+	Running a GUI (<guiicon>Printer Properties</guiicon> and <guiicon>Add Printer Wizard</guiicon>)
+	from any Windows NT/200x/XP client workstation.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+The latter option is probably the easier one (even if the process may seem a little bit weird at first).
+</para>
+
+<sect2>
+<title>Add Printer Wizard Driver Installation</title>
+
+<para>
+The printers initially listed in the Samba host's <guiicon>Printers</guiicon> folder accessed from a
+client's Explorer will have no real printer driver assigned to them. By default this driver name is set
+to a null string. This must be changed now. The local <guiicon>Add Printer Wizard</guiicon> (APW), run from
+NT/2000/XP clients, will help us in this task.
+</para>
+
+<para>
+Installation of a valid printer driver is not straightforward. You must attempt to view the printer properties
+for the printer to which you want the driver assigned. Open Windows Explorer, open <guiicon>Network
+Neighborhood</guiicon>, browse to the Samba host, open Samba's <guiicon>Printers</guiicon> folder, right-click
+on the printer icon, and select <guimenu>Properties...</guimenu>. You are now trying to view printer and
+driver properties for a queue that has this default <constant>NULL</constant> driver assigned. This will
+result in the following error message: <quote> Device settings cannot be displayed. The driver for the
+specified printer is not installed, only spooler properties will be displayed. Do you want to install the
+driver now?</quote>
+</para>
+
+<para>
+Do <emphasis>not</emphasis> click on <guibutton>Yes</guibutton>!  Instead, click on <guibutton>No</guibutton>
+in the error dialog.  Now you will be presented with the printer properties window. From here, the way to
+assign a driver to a printer is open. You now have the choice of:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Select a driver from the pop-up list of installed drivers. Initially this list will be empty.
+	</para></listitem>
+
+	<listitem><para>
+	Click on <guibutton>New Driver</guibutton> to install a new printer driver (which will
+	start up the APW).
+	</para></listitem>
+</itemizedlist>
+
+<para>
+Once the APW is started, the procedure is exactly the same as the one you are familiar with in Windows (we
+assume here that you are familiar with the printer driver installations procedure on Windows NT). Make sure
+your connection is, in fact, set up as a user with <smbconfoption name="printer admin"/>
+privileges (if in doubt, use <command>smbstatus</command> to check for this). If you wish to install
+printer drivers for client operating systems other than <application>Windows NT x86</application>,
+you will need to use the <guilabel>Sharing</guilabel> tab of the printer properties dialog.
+</para>
+
+<para>
+Assuming you have connected with an administrative (or root) account (as named by the
+<smbconfoption name="printer admin"/> parameter), you will also be able to modify
+other printer properties such as ACLs and default device settings using this dialog. For the default
+device settings, please consider the advice given further in <link linkend="inst-rpc">Installing
+Print Drivers Using <command>rpcclient</command></link>.
+</para>
+</sect2>
+
+<sect2 id="inst-rpc">
+<title>Installing Print Drivers Using <command>rpcclient</command></title>
+
+<para>
+The second way to install printer drivers into <smbconfsection name="[print$]"/> and set them
+up in a valid way is to do it from the UNIX command line. This involves four distinct steps:
+</para>
+
+<orderedlist>
+	<listitem><para>
+	Gather information about required driver files and collect the files.
+	</para></listitem>
+
+	<listitem><para>
+	Deposit the driver files into the <smbconfsection name="[print$]"/> share's correct subdirectories
+	(possibly by using <command>smbclient</command>).
+	</para></listitem>
+
+	<listitem><para>
+	Run the <command>rpcclient</command> command-line utility once with the <command>adddriver</command>
+	subcommand.
+	</para></listitem>
+
+	<listitem><para>
+	Run <command>rpcclient</command> a second time with the <command>setdriver</command> subcommand.
+	</para></listitem>
+</orderedlist>
+
+<para>
+We provide detailed hints for each of these steps in the paragraphs that follow.
+</para>
+
+<sect3>
+<title>Identifying Driver Files</title>
+
+<para>
+<indexterm><primary>driver files</primary></indexterm>
+<indexterm><primary>driver CDROM</primary></indexterm>
+<indexterm><primary>inf file</primary></indexterm>
+To find out about the driver files, you have two options. You can check the contents of the driver
+CDROM that came with your printer. Study the <filename>*.inf</filename> files located on the CD-ROM. This
+may not be possible, since the <filename>*.inf</filename> file might be missing. Unfortunately, vendors have now started
+to use their own installation programs. These installations packages are often in some Windows platform
+archive format. Additionally, the files may be re-named during the installation process. This makes it
+extremely difficult to identify the driver files required.
+</para>
+
+<para>
+<indexterm><primary>W32X86</primary></indexterm>
+Then you have the second option. Install the driver locally on a Windows client and
+investigate which filenames and paths it uses after they are installed. (You need to repeat
+this procedure for every client platform you want to support. We show it here for the
+<application>W32X86</application> platform only, a name used by Microsoft for all Windows NT/200x/XP
+clients.)
+</para>
+
+<para>
+<indexterm><primary>driver files</primary></indexterm>
+A good method to recognize the driver files is to print the test page from the driver's
+<guilabel>Properties</guilabel> dialog (<guilabel>General</guilabel> tab). Then look at the list of
+driver files named on the printout. You'll need to recognize what Windows (and Samba) are calling the
+<guilabel>Driver File</guilabel>, <guilabel>Data File</guilabel>, <guilabel>Config File</guilabel>,
+<guilabel>Help File</guilabel>, and (optionally) <guilabel>Dependent Driver Files</guilabel>
+(this may vary slightly for Windows NT). You need to note all filenames for the next steps.
+</para>
+
+<para>
+<indexterm><primary>rpcclient</primary></indexterm>
+<indexterm><primary>enumdrivers</primary></indexterm>
+<indexterm><primary>getdriver</primary></indexterm>
+Another method to quickly test the driver filenames and related paths is provided by the
+<command>rpcclient</command> utility. Run it with <command>enumdrivers</command> or with the
+<command>getdriver</command> subcommand, each at the <filename>3</filename> info level. In the following example,
+<emphasis>TURBO_XP</emphasis> is the name of the Windows PC (in this case it was a Windows XP Professional
+laptop). I installed the driver locally to TURBO_XP from a Samba server called <constant>KDE-BITSHOP</constant>.
+We could run an interactive <command>rpcclient</command> session; then we would get an
+<command>rpcclient /></command> prompt and would type the subcommands at this prompt. This is left as
+a good exercise for you. For now, we use <command>rpcclient</command> with the <option>-c</option>
+parameter to execute a single subcommand line and exit again. This is the method you use if you
+want to create scripts to automate the procedure for a large number of printers and drivers. Note the
+different quotation marks used to overcome the different spaces between words:
+</para>
+
+<para><screen>
+&rootprompt;<userinput>rpcclient -U'Danka%xxxx' -c \
+	'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP</userinput>
+cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3
+
+[Windows NT x86]
+Printer Driver Info 3:
+  Version: [2]
+  Driver Name: [Heidelberg Digimaster 9110 (PS)]
+  Architecture: [Windows NT x86]
+  Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.DLL]
+  Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.ppd]
+  Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.DLL]
+  Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.HLP]
+  
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.DLL]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.INI]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.dat]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.cat]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.def]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hre]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.vnd]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hlp]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01Aux.dll]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.NTF]
+  
+  Monitorname: []
+  Defaultdatatype: []
+</screen></para>
+
+<para>
+<indexterm><primary>Driver File</primary></indexterm>
+<indexterm><primary>Driver Path</primary></indexterm>
+<indexterm><primary>WIN40</primary></indexterm>
+<indexterm><primary>W32X86</primary></indexterm>
+You may notice that this driver has quite a large number of <guilabel>Dependent files</guilabel>
+(there are worse cases, however). Also, strangely, the
+<guilabel>Driver File</guilabel> is tagged here
+<guilabel>Driver Path</guilabel>. We do not yet have support for the so-called
+<application>WIN40</application> architecture installed. This name is used by Microsoft for the Windows
+9x/Me platforms. If we want to support these, we need to install the Windows 9x/Me driver files in
+addition to those for <application>W32X86</application> (i.e., the Windows NT 2000/XP clients) onto a
+Windows PC. This PC can also host the Windows 9x/Me drivers, even if it runs on Windows NT, 2000, or XP.
+</para>
+
+<para>
+<indexterm><primary>UNC notation</primary></indexterm>
+<indexterm><primary>Windows Explorer</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+Since the <smbconfsection name="[print$]"/> share is usually accessible through the <guiicon>Network
+Neighborhood</guiicon>, you can also use the UNC notation from Windows Explorer to poke at it. The Windows
+9x/Me driver files will end up in subdirectory <filename>0</filename> of the <filename>WIN40</filename>
+directory. The full path to access them is <filename>\\WINDOWSHOST\print$\WIN40\0\</filename>.
+</para>
+
+<note><para>
+More recent drivers on Windows 2000 and Windows XP are installed into the <quote>3</quote> subdirectory
+instead of the <quote>2</quote>. The version 2 of drivers, as used in Windows NT, were running in kernel
+mode. Windows 2000 changed this. While it still can use the kernel mode drivers (if this is enabled by
+the Admin), its native mode for printer drivers is user mode execution. This requires drivers designed
+for this purpose. These types of drivers install into the <quote>3</quote> subdirectory.
+</para></note>
+</sect3>
+
+<sect3>
+<title>Obtaining Driver Files from Windows Client [print$] Shares</title>
+
+<para>
+Now we need to collect all the driver files we identified in our previous step. Where do we get them
+from? Well, why not retrieve them from the very PC and the same <smbconfsection name="[print$]"/>
+share that we investigated in our last step to identify the files? We can use <command>smbclient</command>
+to do this. We will use the paths and names that were leaked to us by <command>getdriver</command>. The
+listing is edited to include line breaks for readability:
+<screen>
+&rootprompt;<userinput>smbclient //TURBO_XP/print\$ -U'Danka%xxxx' \ 
+   -c 'cd W32X86/2;mget HD*_de.* hd*ppd Hd*_de.* Hddm*dll HDN*Aux.DLL'</userinput>
+
+added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+Got a positive name query response from 10.160.50.8 ( 10.160.50.8 )
+Domain=[DEVELOPMENT] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
+<prompt>Get file Hddm91c1_de.ABD? </prompt><userinput>n</userinput>
+<prompt>Get file Hddm91c1_de.def? </prompt><userinput>y</userinput>
+getting file \W32X86\2\Hddm91c1_de.def of size 428 as Hddm91c1_de.def
+<prompt>Get file Hddm91c1_de.DLL? </prompt><userinput>y</userinput>
+getting file \W32X86\2\Hddm91c1_de.DLL of size 876544 as Hddm91c1_de.DLL
+[...]
+</screen></para>
+
+<para>
+After this command is complete, the files are in our current local directory. You probably have noticed
+that this time we passed several commands to the <option>-c</option> parameter, separated by semicolons.
+This ensures that all commands are executed in sequence on the remote Windows server before
+<command>smbclient</command> exits again.
+</para>
+
+<para>
+<indexterm><primary>WIN40</primary></indexterm>
+Remember to repeat the procedure for the <application>WIN40</application> architecture should you need to
+support Windows 9x/Me/XP clients. Remember too, the files for these architectures are in the
+<filename>WIN40/0/</filename> subdirectory. Once this is complete, we can run <command>smbclient. .
+.put</command> to store the collected files on the Samba server's <smbconfsection name="[print$]"/> share.
+</para>
+</sect3>
+
+<sect3>
+<title>Installing Driver Files into [print$]</title>
+
+<para>
+We are now going to locate the driver files into the <smbconfsection name="[print$]"/> share. Remember, the
+UNIX path to this share has been defined previously in your &smb.conf; file. You also have created
+subdirectories for the different Windows client types you want to support. If, for example, your
+<smbconfsection name="[print$]"/> share maps to the UNIX path <filename>/etc/samba/drivers/</filename>, your
+driver files should now go here:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	For all Windows NT, 2000, and XP clients, <filename>/etc/samba/drivers/W32X86/</filename> but
+	not (yet) into the <filename>2</filename> subdirectory.
+	</para></listitem>
+
+	<listitem><para>
+	For all Windows 95, 98, and Me clients, <filename>/etc/samba/drivers/WIN40/</filename> but not
+	(yet) into the <filename>0</filename> subdirectory.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>smbclient</primary></indexterm>
+<indexterm><primary>getdriver</primary></indexterm>
+We again use smbclient to transfer the driver files across the network. We specify the same files
+and paths as were leaked to us by running <command>getdriver</command> against the original
+<emphasis>Windows</emphasis> install. However, now we are going to store the files into a
+<emphasis>Samba/UNIX</emphasis> print server's <smbconfsection name="[print$]"/> share.
+<screen>
+&rootprompt;<userinput>smbclient //SAMBA-CUPS/print\$ -U'root%xxxx' -c \
+  'cd W32X86; put HDNIS01_de.DLL; \
+  put Hddm91c1_de.ppd; put HDNIS01U_de.DLL;        \
+  put HDNIS01U_de.HLP; put Hddm91c1_de.DLL;        \
+  put Hddm91c1_de.INI; put Hddm91c1KMMin.DLL;      \
+  put Hddm91c1_de.dat; put Hddm91c1_de.dat;        \
+  put Hddm91c1_de.def; put Hddm91c1_de.hre;        \
+  put Hddm91c1_de.vnd; put Hddm91c1_de.hlp;        \
+  put Hddm91c1_de_reg.HLP; put HDNIS01Aux.dll;     \
+  put HDNIS01_de.NTF'</userinput>
+
+added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+putting file HDNIS01_de.DLL as \W32X86\HDNIS01_de.DLL
+putting file Hddm91c1_de.ppd as \W32X86\Hddm91c1_de.ppd
+putting file HDNIS01U_de.DLL as \W32X86\HDNIS01U_de.DLL
+putting file HDNIS01U_de.HLP as \W32X86\HDNIS01U_de.HLP
+putting file Hddm91c1_de.DLL as \W32X86\Hddm91c1_de.DLL
+putting file Hddm91c1_de.INI as \W32X86\Hddm91c1_de.INI
+putting file Hddm91c1KMMin.DLL as \W32X86\Hddm91c1KMMin.DLL
+putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
+putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
+putting file Hddm91c1_de.def as \W32X86\Hddm91c1_de.def
+putting file Hddm91c1_de.hre as \W32X86\Hddm91c1_de.hre
+putting file Hddm91c1_de.vnd as \W32X86\Hddm91c1_de.vnd
+putting file Hddm91c1_de.hlp as \W32X86\Hddm91c1_de.hlp
+putting file Hddm91c1_de_reg.HLP as \W32X86\Hddm91c1_de_reg.HLP
+putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll
+putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF
+</screen>
+<indexterm><primary>PPD</primary></indexterm>
+<indexterm><primary>PostScript driver</primary></indexterm>
+<indexterm><primary>adddriver</primary></indexterm>
+Whew &smbmdash; that was a lot of typing! Most drivers are a lot smaller &smbmdash; many have only three generic
+PostScript driver files plus one PPD. While we did retrieve the files from the <filename>2</filename>
+subdirectory of the <filename>W32X86</filename> directory from the Windows box, we do not put them
+(for now) in this same subdirectory of the Samba box. This relocation will automatically be done by the
+<command>adddriver</command> command, which we will run shortly (and do not forget to also put the files
+for the Windows 9x/Me architecture into the <filename>WIN40/</filename> subdirectory should you need them).
+</para>
+
+</sect3>
+
+<sect3>
+<title><command>smbclient</command> to Confirm Driver Installation</title>
+
+<para>
+<indexterm><primary>smbclient</primary></indexterm>
+<indexterm><primary>SSH</primary></indexterm>
+For now we verify that our files are there. This can be done with <command>smbclient</command>, too
+(but, of course, you can log in via SSH also and do this through a standard UNIX shell access):
+</para>
+
+<para><screen>
+&rootprompt;<userinput>smbclient //SAMBA-CUPS/print\$ -U 'root%xxxx' \
+	-c 'cd W32X86; pwd; dir; cd 2; pwd; dir'</userinput>
+ added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.8a]
+
+Current directory is \\SAMBA-CUPS\print$\W32X86\
+.                                  D        0  Sun May  4 03:56:35 2003
+..                                 D        0  Thu Apr 10 23:47:40 2003
+2                                   D        0  Sun May  4 03:56:18 2003
+HDNIS01Aux.dll                      A    15356  Sun May  4 03:58:59 2003
+Hddm91c1KMMin.DLL                   A    46966  Sun May  4 03:58:59 2003
+HDNIS01_de.DLL                      A   434400  Sun May  4 03:58:59 2003
+HDNIS01_de.NTF                      A   790404  Sun May  4 03:56:35 2003
+Hddm91c1_de.DLL                     A   876544  Sun May  4 03:58:59 2003
+Hddm91c1_de.INI                     A      101  Sun May  4 03:58:59 2003
+Hddm91c1_de.dat                     A     5044  Sun May  4 03:58:59 2003
+Hddm91c1_de.def                     A      428  Sun May  4 03:58:59 2003
+Hddm91c1_de.hlp                     A    37699  Sun May  4 03:58:59 2003
+Hddm91c1_de.hre                     A   323584  Sun May  4 03:58:59 2003
+Hddm91c1_de.ppd                     A    26373  Sun May  4 03:58:59 2003
+Hddm91c1_de.vnd                     A    45056  Sun May  4 03:58:59 2003
+HDNIS01U_de.DLL                     A   165888  Sun May  4 03:58:59 2003
+HDNIS01U_de.HLP                     A    19770  Sun May  4 03:58:59 2003
+Hddm91c1_de_reg.HLP                 A   228417  Sun May  4 03:58:59 2003
+              40976 blocks of size 262144. 709 blocks available
+
+Current directory is \\SAMBA-CUPS\print$\W32X86\2\
+.                                  D        0  Sun May  4 03:56:18 2003
+..                                 D        0  Sun May  4 03:56:35 2003
+ADOBEPS5.DLL                        A   434400  Sat May  3 23:18:45 2003
+laserjet4.ppd                       A     9639  Thu Apr 24 01:05:32 2003
+ADOBEPSU.DLL                        A   109568  Sat May  3 23:18:45 2003
+ADOBEPSU.HLP                        A    18082  Sat May  3 23:18:45 2003
+PDFcreator2.PPD                     A    15746  Sun Apr 20 22:24:07 2003
+              40976 blocks of size 262144. 709 blocks available
+</screen></para>
+
+<para>
+<indexterm><primary>Point'n'Print</primary></indexterm>
+<indexterm><primary>printer driver files</primary></indexterm>
+<indexterm><primary>print queue</primary></indexterm>
+Notice that there are already driver files present in the <filename>2</filename> subdirectory (probably from a
+previous installation). Once the files for the new driver are there too, you are still a few steps away from
+being able to use them on the clients. The only thing you could do now is retrieve them from a client just
+like you retrieve ordinary files from a file share, by opening print$ in Windows Explorer. But that wouldn't
+install them per Point'n'Print. The reason is that Samba does not yet know that these files are something
+special, namely <emphasis>printer driver files</emphasis>, and it does not know to which print queue(s) these
+driver files belong.
+</para>
+</sect3>
+
+<sect3>
+<title>Running <command>rpcclient</command> with <command>adddriver</command></title>
+
+<para>
+<indexterm><primary>adddriver</primary></indexterm>
+<indexterm><primary>register driver files</primary></indexterm>
+<indexterm><primary>TDB database</primary></indexterm>
+Next, you must tell Samba about the special category of the files you just uploaded into the
+<smbconfsection name="[print$]"/> share. This is done by the <command>adddriver</command>
+command. It will prompt Samba to register the driver files into its internal TDB database files. The
+following command and its output has been edited for readability:
+<screen>
+&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
+  "dm9110:HDNIS01_de.DLL: \
+  Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
+  NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
+  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
+  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
+  HDNIS01Aux.dll,HDNIS01_de.NTF,                     \
+  Hddm91c1_de_reg.HLP' SAMBA-CUPS</userinput>
+
+cmd = adddriver "Windows NT x86" \
+  "dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:   \
+  HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
+  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,          \
+  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL,        \
+  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
+
+Printer Driver dm9110 successfully installed.
+</screen></para>
+
+<para>
+<indexterm><primary>NT_STATUS_UNSUCCESSFUL</primary></indexterm>
+<indexterm><primary>error message</primary></indexterm>
+<indexterm><primary>adddriver</primary></indexterm>
+After this step, the driver should be recognized by Samba on the print server. You need to be very
+careful when typing the command. Don't exchange the order of the fields. Some changes would lead to
+an <computeroutput>NT_STATUS_UNSUCCESSFUL</computeroutput> error message. These become obvious. Other
+changes might install the driver files successfully but render the driver unworkable. So take care!
+Hints about the syntax of the adddriver command are in the man page. 
+provides a more detailed description, should you need it.
+</para>
+</sect3>
+
+<sect3>
+<title>Checking <command>adddriver</command> Completion</title>
+
+<para>
+One indication for Samba's recognition of the files as driver files is the <computeroutput>successfully
+installed</computeroutput> message. Another one is the fact that our files have been moved by the
+<command>adddriver</command> command into the <filename>2</filename> subdirectory. You can check this
+again with <command>smbclient</command>:
+<screen>
+&rootprompt;<userinput>smbclient //SAMBA-CUPS/print\$ -Uroot%xx \
+	-c 'cd W32X86;dir;pwd;cd 2;dir;pwd'</userinput>
+ added interface ip=10.160.51.162 bcast=10.160.51.255 nmask=255.255.252.0
+ Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+
+  Current directory is \\SAMBA-CUPS\print$\W32X86\
+  .                                  D        0  Sun May  4 04:32:48 2003
+  ..                                 D        0  Thu Apr 10 23:47:40 2003
+  2                                   D        0  Sun May  4 04:32:48 2003
+                40976 blocks of size 262144. 731 blocks available 
+
+  Current directory is \\SAMBA-CUPS\print$\W32X86\2\
+  .                                  D        0  Sun May  4 04:32:48 2003
+  ..                                 D        0  Sun May  4 04:32:48 2003
+  DigiMaster.PPD                      A   148336  Thu Apr 24 01:07:00 2003
+  ADOBEPS5.DLL                        A   434400  Sat May  3 23:18:45 2003
+  laserjet4.ppd                       A     9639  Thu Apr 24 01:05:32 2003
+  ADOBEPSU.DLL                        A   109568  Sat May  3 23:18:45 2003
+  ADOBEPSU.HLP                        A    18082  Sat May  3 23:18:45 2003
+  PDFcreator2.PPD                     A    15746  Sun Apr 20 22:24:07 2003
+  HDNIS01Aux.dll                      A    15356  Sun May  4 04:32:18 2003
+  Hddm91c1KMMin.DLL                   A    46966  Sun May  4 04:32:18 2003
+  HDNIS01_de.DLL                      A   434400  Sun May  4 04:32:18 2003
+  HDNIS01_de.NTF                      A   790404  Sun May  4 04:32:18 2003
+  Hddm91c1_de.DLL                     A   876544  Sun May  4 04:32:18 2003
+  Hddm91c1_de.INI                     A      101  Sun May  4 04:32:18 2003
+  Hddm91c1_de.dat                     A     5044  Sun May  4 04:32:18 2003
+  Hddm91c1_de.def                     A      428  Sun May  4 04:32:18 2003
+  Hddm91c1_de.hlp                     A    37699  Sun May  4 04:32:18 2003
+  Hddm91c1_de.hre                     A   323584  Sun May  4 04:32:18 2003
+  Hddm91c1_de.ppd                     A    26373  Sun May  4 04:32:18 2003
+  Hddm91c1_de.vnd                     A    45056  Sun May  4 04:32:18 2003
+  HDNIS01U_de.DLL                     A   165888  Sun May  4 04:32:18 2003
+  HDNIS01U_de.HLP                     A    19770  Sun May  4 04:32:18 2003
+  Hddm91c1_de_reg.HLP                 A   228417  Sun May  4 04:32:18 2003
+                40976 blocks of size 262144. 731 blocks available
+</screen></para>
+
+<para>
+Another verification is that the timestamp of the printing TDB files is now updated
+(and possibly their file size has increased).
+</para>
+</sect3>
+
+<sect3>
+<title>Check Samba for Driver Recognition</title>
+
+<para>
+<indexterm><primary>registered</primary></indexterm>
+Now the driver should be registered with Samba. We can easily verify this and will do so in a
+moment. However, this driver is not yet associated with a particular printer. We may check the driver
+status of the files by at least three methods:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+<indexterm><primary>Network Neighborhood</primary></indexterm>
+<indexterm><primary>Printers and Faxes</primary></indexterm>
+<indexterm><primary>printer icon</primary></indexterm>
+<indexterm><primary>Windows95/98/ME</primary></indexterm>
+<indexterm><primary>Windows NT/2000/XP</primary></indexterm>
+	From any Windows client browse Network Neighborhood, find the Samba host, and open the Samba
+	<guiicon>Printers and Faxes</guiicon> folder. Select any printer icon, right-click and select
+	the printer <guimenuitem>Properties</guimenuitem>. Click the <guilabel>Advanced</guilabel>
+	tab. Here is a field indicating the driver for that printer. A drop-down menu allows you to
+	change that driver (be careful not to do this unwittingly). You can use this list to view
+	all drivers known to Samba. Your new one should be among them. (Each type of client will
+	see only its own architecture's list. If you do not have every driver installed for each platform,
+	the list will differ if you look at it from Windows95/98/ME or Windows NT/2000/XP.)
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>Network Neighborhood</primary></indexterm>
+	From a Windows 200x/XP client (not Windows NT) browse <guiicon>Network Neighborhood</guiicon>,
+	search for the Samba server, open the server's <guiicon>Printers</guiicon> folder,
+	and right-click on the white background (with no printer highlighted). Select <guimenuitem>Server
+	Properties</guimenuitem>. On the <guilabel>Drivers</guilabel> tab you will see the new driver
+	listed. This view enables you to also inspect the list of files belonging to that driver
+	(this does not work on Windows NT, but only on Windows 2000 and Windows XP; Windows NT does not
+	provide the <guimenuitem>Drivers</guimenuitem> tab). An alternative and much quicker method for
+	Windows 2000/XP to start this dialog is by typing into a DOS box (you must of course adapt the
+	name to your Samba server instead of <replaceable>SAMBA-CUPS</replaceable>):
+	<screen>
+	<userinput>rundll32 printui.dll,PrintUIEntry /s /t2 /n\\<replaceable>SAMBA-CUPS</replaceable></userinput>
+	</screen>
+	</para>
+	</listitem>
+
+	<listitem><para>
+	From a UNIX prompt, run this command (or a variant thereof), where
+	<replaceable>SAMBA-CUPS</replaceable> is the name of the Samba host and xxxx represents the
+	actual Samba password assigned to root:
+	<screen>
+	<userinput>rpcclient -U'root%xxxx' -c 'enumdrivers' <replaceable>SAMBA-CUPS</replaceable></userinput>
+	</screen>
+	</para>
+
+	<para>
+	You will see a listing of all drivers Samba knows about. Your new one should be among
+	them. But it is only listed under the <parameter>[Windows NT x86]</parameter> heading, not under
+	<smbconfsection name="[Windows 4.0]"/>, since you didn't install that part. Or did you?
+	In our example it is named <constant>dm9110</constant>. Note that the third column shows the other
+	installed drivers twice, one time for each supported architecture. Our new driver only shows up
+	for <application>Windows NT 4.0 or 2000</application>. To have it present for <application>Windows
+	95, 98, and Me</application>, you'll have to repeat the whole procedure with the WIN40 architecture
+	and subdirectory.
+	</para></listitem>
+</itemizedlist>
+</sect3>
+
+<sect3>
+<title>Specific Driver Name Flexibility</title>
+
+<para>
+<indexterm><primary>adddriver</primary></indexterm>
+You can name the driver as you like. If you repeat the <command>adddriver</command> step with the same
+files as before but with a different driver name, it will work the same:
+<screen>
+&rootprompt;<userinput>rpcclient -Uroot%xxxx         \
+  -c 'adddriver "Windows NT x86"                     \
+  "mydrivername:HDNIS01_de.DLL:              \
+  Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
+  NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
+  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
+  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
+  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS
+  </userinput>
+
+cmd = adddriver "Windows NT x86" \
+ "mydrivername:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:\
+  HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,           \
+  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,                    \
+  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL,                  \
+  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
+
+Printer Driver mydrivername successfully installed.
+</screen></para>
+
+<para>
+<indexterm><primary>print queue</primary></indexterm>
+<indexterm><primary>rpcclient</primary></indexterm>
+<indexterm><primary>adddriver</primary></indexterm>
+You will be able to bind that driver to any print queue (however, you are responsible that
+you associate drivers to queues that make sense with respect to target printers). You cannot run the
+<command>rpcclient</command> <command>adddriver</command> command repeatedly. Each run consumes the
+files you had put into the <smbconfsection name="[print$]"/> share by moving them into the
+respective subdirectories, so you must execute an <command>smbclient ... put</command> command before
+each <command>rpcclient ... adddriver</command> command.
+</para>
+</sect3>
+
+<sect3>
+<title>Running <command>rpcclient</command> with <command>setdriver</command></title>
+
+<para> 
+<indexterm><primary>mapping printer driver</primary></indexterm>
+<indexterm><primary>TDB</primary></indexterm>
+Samba needs to know which printer owns which driver. Create a mapping of the driver to a printer, and
+store this information in Samba's memory, the TDB files. The <command>rpcclient setdriver</command> command
+achieves exactly this:
+<screen>
+&rootprompt;<userinput>rpcclient -U'root%xxxx' -c 'setdriver dm9110 mydrivername' <replaceable>SAMBA-CUPS</replaceable></userinput>
+ cmd = setdriver dm9110 mydrivername
+
+Successfully set dm9110 to driver mydrivername.
+</screen></para>
+
+<para>
+Ah, no, I did not want to do that. Repeat, this time with the name I intended: 
+<screen>
+&rootprompt;<userinput>rpcclient -U'root%xxxx' -c 'setdriver dm9110 dm9110' <replaceable>SAMBA-CUPS</replaceable></userinput>
+ cmd = setdriver dm9110 dm9110
+Successfully set dm9110 to driver dm9110.
+</screen></para>
+
+<para>
+The syntax of the command is:
+<screen>
+<userinput>rpcclient -U'root%<replaceable>sambapassword</replaceable>' -c 'setdriver <replaceable>printername</replaceable> \
+ <replaceable>drivername</replaceable>' <replaceable>SAMBA-Hostname</replaceable></userinput>. 
+</screen>
+Now we have done most of the work, but not all of it.
+</para>
+
+<note><para>
+The <command>setdriver</command> command will only succeed if the printer is already known to Samba. A
+bug in 2.2.x prevented Samba from recognizing freshly installed printers. You had to restart Samba,
+or at least send an HUP signal to all running smbd processes to work around this: <userinput>kill -HUP
+`pidof smbd`</userinput>.
+</para></note>
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Client Driver Installation Procedure</title>
+
+<para>
+As Don Quixote said, <quote>The proof of the pudding is in the eating.</quote> The proof
+for our setup lies in the printing. So let's install the printer driver onto the client PCs. This is
+not as straightforward as it may seem. Read on.
+</para>
+
+<sect2>
+<title>First Client Driver Installation</title>
+
+<para>
+Especially important is the installation onto the first client PC (for each architectural platform
+separately). Once this is done correctly, all further clients are easy to set up and shouldn't need further
+attention. What follows is a description for the recommended first procedure. You now work from a client
+workstation. You should check that your connection is not unwittingly mapped to <emphasis>bad
+user</emphasis> nobody. In a DOS box type:
+</para>
+
+<para><userinput>net use \\<replaceable>SAMBA-SERVER</replaceable>\print$ /user:root</userinput></para>
+
+<para>
+Replace root, if needed, by another valid <smbconfoption name="printer admin"/> user as given in
+the definition. Should you already be connected as a different user, you will get an error message. There
+is no easy way to get rid of that connection, because Windows does not seem to know a concept of logging
+off from a share connection (do not confuse this with logging off from the local workstation; that is
+a different matter).  On Windows NT/200x, you can force a logoff from all smb/cifs connections by restarting the 
+<emphasis>workstation</emphasis> service. You can try to close all Windows file explorers and Internet Explorer for 
+Windows. As a last resort, you may have to reboot. Make sure there is no automatic reconnection set up. It may be
+easier to go to a different workstation and try from there. After you have made sure you are connected
+as a printer admin user (you can check this with the <command>smbstatus</command> command on Samba),
+do this from the Windows workstation:
+</para>
+
+<procedure>
+	<step><para>
+	Open <guiicon>Network Neighborhood</guiicon>.
+	</para></step>
+
+	<step><para>
+	Browse to Samba server.
+	</para></step>
+
+	<step><para>
+	Open its <guiicon>Printers and Faxes</guiicon> folder.
+	</para></step>
+
+	<step><para>
+	Highlight and right-click on the printer.
+	</para></step>
+
+	<step><para>
+	Select <guimenuitem>Connect</guimenuitem> (for Windows NT4/200x
+	it is possibly <guimenuitem>Install</guimenuitem>).
+	</para></step>
+</procedure>
+
+<para>
+A new printer (named <replaceable>printername</replaceable> on Samba server) should now have
+appeared in your <emphasis>local</emphasis> Printer folder (check <guimenu>Start</guimenu> ->
+<guimenuitem>Settings</guimenuitem> -> <guimenuitem>Control Panel</guimenuitem> -> <guiicon>Printers
+and Faxes</guiicon>).
+</para>
+
+<para>
+<indexterm><primary>print test page</primary></indexterm>
+Most likely you are tempted to try to print a test page. After all, you now can open the printer
+properties, and on the <guimenu>General</guimenu> tab there is a button offering to do just that. But
+chances are that you get an error message saying "<literal>Unable to print Test Page</literal>." The
+reason might be that there is not yet a valid device mode set for the driver or that the <quote>printer
+driver data</quote> set is still incomplete.
+</para>
+
+<para>
+You must make sure that a valid <parameter>device mode</parameter> is set for the
+driver. We now explain what that means.
+</para>
+</sect2>
+
+<sect2 id="prt-modeset">
+<title>Setting Device Modes on New Printers</title>
+
+<para>
+For a printer to be truly usable by a Windows NT/200x/XP client, it must possess:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+<indexterm><primary>device mode</primary></indexterm>
+	A valid <emphasis>device mode</emphasis> generated by the driver for the printer (defining things
+	like paper size, orientation and duplex settings).
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>printer driver data</primary></indexterm>
+	A complete set of <emphasis>printer driver data</emphasis> generated by the driver.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>ntprinters.tdb</primary></indexterm>
+<indexterm><primary>ntdrivers.tdb</primary></indexterm>
+<indexterm><primary>printing.tdb</primary></indexterm>
+<indexterm><primary>ntforms.tdb</primary></indexterm>
+<indexterm><primary>TDB database files</primary></indexterm>
+If either of these is incomplete, the clients can produce less than optimal output at best. In the
+worst cases, unreadable garbage or nothing at all comes from the printer, or it produces a harvest of
+error messages when attempting to print. Samba stores the named values and all printing-related information in
+its internal TDB database files <filename>(ntprinters.tdb</filename>, <filename>ntdrivers.tdb</filename>,
+<filename>printing.tdb</filename>, and <filename>ntforms.tdb</filename>).
+</para>
+
+<para>
+The device mode and the set of printer driver data are basically collections
+of settings for all print queue properties, initialized in a sensible way. Device modes and
+printer driver data should initially be set on the print server (the Samba host) to healthy
+values so the clients can start to use them immediately. How do we set these initial healthy values?
+This can be achieved by accessing the drivers remotely from an NT (or 200x/XP) client, as discussed
+in the following paragraphs.
+</para>
+
+<para>
+Be aware that a valid device mode can only be initiated by a <smbconfoption name="printer admin"/> or root
+(the reason should be obvious). Device modes can be correctly set only by executing the printer driver program
+itself. Since Samba cannot execute this Win32 platform driver code, it sets this field initially to NULL
+(which is not a valid setting for clients to use). Fortunately, most drivers automatically generate the
+printer driver data that is needed when they are uploaded to the <smbconfsection name="[print$]"/> share with
+the help of the APW or rpcclient.
+</para>
+
+<para>
+The generation and setting of a first valid device mode, however, requires some tickling from a client
+to set it on the Samba server. The easiest means of doing so is to simply change the page orientation on
+the server's printer. This executes enough of the printer driver program on the client for the desired
+effect to happen and feeds back the new device mode to our Samba server. You can use the native Windows
+NT/200x/XP printer properties page from a Window client for this:
+</para>
+
+<procedure>
+<title>Procedure to Initialize the Printer Driver Settings</title>
+	<step><para>
+	Browse the <guiicon>Network Neighborhood</guiicon>.
+	</para></step>
+
+	<step><para>
+	Find the Samba server.
+	</para></step>
+
+	<step><para>
+	Open the Samba server's <guiicon>Printers and Faxes</guiicon> folder.
+	</para></step>
+
+	<step><para>
+	Highlight the shared printer in question.
+	</para></step>
+
+	<step><para>
+	Right-click on the printer (you may already be here if you followed the last section's description).
+	</para></step>
+
+	<step><para>
+	At the bottom of the context menu select <guimenu>Properties</guimenu> (if the menu still offers the 
+	<guimenuitem>Connect</guimenuitem> entry further above, you
+	need to click on that one first to achieve the driver
+	installation, as shown in the last section).
+	</para></step>
+
+	<step><para>
+	Go to the <guilabel>Advanced</guilabel> tab; click on <guibutton>Printing Defaults</guibutton>.
+	</para></step>
+
+	<step><para>
+	Change the <guimenuitem>Portrait</guimenuitem> page setting to <guimenuitem>Landscape</guimenuitem> (and back).
+	</para></step>
+
+	<step><para>
+	Make sure to apply changes between swapping the page orientation to cause the change to actually take effect.
+	</para></step>
+
+	<step><para>
+	While you are at it, you may also want to set the desired printing defaults here, which then apply to all future
+	client driver installations.
+	</para></step>
+</procedure>
+
+<para>
+This procedure executes the printer driver program on the client platform and feeds back the correct
+device mode to Samba, which now stores it in its TDB files. Once the driver is installed on the client,
+you can follow the analogous steps by accessing the <emphasis>local</emphasis> <guiicon>Printers</guiicon>
+folder, too, if you are a Samba printer admin user. From now on, printing should work as expected.
+</para>
+
+<para>
+<indexterm><primary>default devmode</primary></indexterm>
+Samba includes a service-level parameter name <parameter>default devmode</parameter> for generating a default
+device mode for a printer. Some drivers function well with Samba's default set of properties. Others
+may crash the client's spooler service. So use this parameter with caution. It is always better to have
+the client generate a valid device mode for the printer and store it on the server for you.
+</para>
+</sect2>
+
+<sect2>
+<title>Additional Client Driver Installation</title>
+
+<para>
+<indexterm><primary>additional driver</primary></indexterm>
+Every additional driver may be installed in the same way as just described.  Browse <command>Network
+Neighborhood</command>, open the <guiicon>Printers</guiicon> folder on Samba server, right-click on
+<guiicon>Printer</guiicon>, and choose <guimenuitem>Connect...</guimenuitem>. Once this completes (should be
+not more than a few seconds, but could also take a minute, depending on network conditions), you should find
+the new printer in your client workstation local <guiicon>Printers and Faxes</guiicon> folder.
+</para>
+
+<para>
+You can also open your local <guiicon>Printers and Faxes</guiicon> folder by
+using this command on Windows 200x/XP Professional workstations:
+<screen>
+<userinput>rundll32 shell32.dll,SHHelpShortcuts_RunDLL PrintersFolder</userinput>
+</screen>
+or this command on Windows NT 4.0 workstations:
+<indexterm><primary>rundll32</primary></indexterm>
+<screen>
+<userinput>rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2</userinput>
+</screen>
+</para>
+
+<para>
+You can enter the commands either inside a <guilabel>DOS box</guilabel> window or in the <guimenuitem>Run
+command...</guimenuitem> field from the <guimenu>Start</guimenu> menu.
+</para>
+</sect2>
+
+<sect2>
+<title>Always Make First Client Connection as root or <quote>printer admin</quote></title>
+
+<para>
+After you installed the driver on the Samba server (in its <smbconfsection name="[print$]"/> share), you
+should always make sure that your first client installation completes correctly. Make it a habit for yourself
+to build the very first connection from a client as <smbconfoption name="printer admin"/>. This is to make
+sure that:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	A first valid <emphasis>device mode</emphasis> is really initialized (see above <link
+	linkend="prt-modeset">Setting Device Modes on New Printers</link>) for more explanation details).
+	</para></listitem>
+
+	<listitem><para>	
+	The default print settings of your printer for all further client installations are as you want them.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+Do this by changing the orientation to landscape, click on <guiicon>Apply</guiicon>, and then change it
+back again. Next, modify the other settings (for example, you do not want the default media size set to
+<guiicon>Letter</guiicon> when you are all using <guiicon>A4</guiicon>, right? You may want to set the
+printer for <guiicon>duplex</guiicon> as the default, and so on).
+</para>
+
+<para>
+<indexterm><primary>runas</primary></indexterm>
+To connect as root to a Samba printer, try this command from a Windows 200x/XP DOS box command prompt:
+<screen>
+&dosprompt;<userinput>runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n 
+	\\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printername</replaceable>"</userinput>
+</screen>
+</para>
+
+<para>
+You will be prompted for <constant>root</constant>'s Samba password; type it, wait a few seconds, click on
+<guibutton>Printing Defaults</guibutton>, and proceed to set the job options that should be used as defaults
+by all clients. Alternatively, instead of root you can name one other member of the <smbconfoption
+name="printer admin"/> from the setting.
+</para>
+
+<para>
+Now all the other users downloading and installing the driver the same way (using
+<literal>Point'n'Print</literal>) will have the same defaults set for them. If you miss this step, you'll get a
+lot of help desk calls from your users, but maybe you like to talk to people.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Other Gotchas</title>
+
+<para>
+Your driver is installed. It is now ready for Point'n'Print installation by the clients. You may have tried to
+download and use it on your first client machine, but wait. Let's make sure you are acquainted first with a
+few tips and tricks you may find useful. For example, suppose you did not set the defaults on the printer, as
+advised in the preceding paragraphs. Your users complain about various issues (such as, <quote>We need to set
+the paper size for each job from Letter to A4 and it will not store it</quote>).
+</para>
+
+<sect2>
+<title>Setting Default Print Options for Client Drivers</title>
+
+<para>
+The last sentence might be viewed with mixed feelings by some users and Admins. They have struggled for hours
+and could not arrive at a point where their settings seemed to be saved. It is not their fault. The confusing
+thing is that in the multitabbed dialog that pops up when you right-click on the printer name and select
+<guimenuitem>Properties</guimenuitem>, you can arrive at two dialogs that appear identical, each claiming that
+they help you to set printer options in three different ways. Here is the definitive answer to the Samba
+default driver setting FAQ:
+</para>
+
+<formalpara><title><quote>I can not set and save default print options
+for all users on Windows 200x/XP. Why not?</quote></title>
+
+<para>
+How are you doing it? I bet the wrong way. (It is not easy to find out, though.) There are three different
+ways to bring you to a dialog that seems to set everything. All three dialogs look the same, but only one of
+them does what you intend. You need to be Administrator or Print Administrator to do this for all users. Here
+is how I reproduce it in an XP Professional:
+</para>
+
+<orderedlist numeration="upperalpha">
+	<listitem><para>The first <quote>wrong</quote> way:
+	<orderedlist numeration="arabic">
+		<listitem><para>Open the <guiicon>Printers</guiicon> folder.</para></listitem>
+
+		<listitem><para>Right-click on the printer (<emphasis>remoteprinter on cupshost</emphasis>) and
+		select in context menu <guimenu>Printing Preferences...</guimenu>.</para></listitem>
+
+		<listitem><para>Look at this dialog closely and remember what it looks like.</para></listitem>
+	</orderedlist></para></listitem>
+
+	<listitem><para>The second <quote>wrong</quote> way:
+		<orderedlist numeration="arabic">
+			<listitem><para>Open the <guimenu>Printers</guimenu> folder.</para></listitem>
+
+			<listitem><para>Right-click on the printer (<emphasis>remoteprinter on
+			cupshost</emphasis>) and select in the context menu
+			<guimenuitem>Properties</guimenuitem></para></listitem>.
+
+			<listitem><para>Click on the <guilabel>General</guilabel>
+			tab.</para></listitem>
+
+			<listitem><para>Click on the <guibutton>Printing
+			Preferences...</guibutton> button.</para></listitem>
+
+			<listitem><para>A new dialog opens. Keep this dialog open and go back
+			to the parent dialog.</para></listitem>
+		</orderedlist>
+	</para></listitem>
+
+	<listitem><para>
+	The third and correct way (should you do this from the beginning, just carry out steps 1
+	and 2 from the second method above):
+	</para>
+
+		<orderedlist numeration="arabic">
+			<listitem><para>Click on the <guilabel>Advanced</guilabel>
+			tab. (If everything is <quote>grayed out,</quote> then you are not logged
+			in as a user with enough privileges.)</para></listitem>
+
+			<listitem><para>Click on the <guibutton>Printing
+			Defaults</guibutton> button.</para></listitem>
+
+			<listitem><para>On any of the two new tabs,
+			click on the
+			<guilabel>Advanced</guilabel> button.</para></listitem>
+
+			<listitem><para>A new dialog opens. Compare
+			this one to the other. Are they
+			identical when you compare one from
+			<quote>B.5</quote> and one from A.3?</para></listitem>
+		</orderedlist>
+	</listitem>
+</orderedlist>
+
+<para>
+Do you see any difference in the two settings dialogs? I do not either. However, only the last one, which you
+arrived at with steps C.1 through C.6 will permanently save any settings which will then become the defaults
+for new users. If you want all clients to have the same defaults, you need to conduct these steps as
+administrator (<smbconfoption name="printer admin"/>) before a client downloads the driver (the clients can
+later set their own per-user defaults by following procedures A or B above). Windows 200x/XP allow per-user
+default settings and the ones the administrator gives them before they set up their own. The parents of the
+identical-looking dialogs have a slight difference in their window names; one is called
+<computeroutput>Default Print Values for Printer Foo on Server Bar</computeroutput> (which is the one you
+need) and the other is called <quote><computeroutput>Print Settings for Printer Foo on Server
+Bar</computeroutput></quote>. The last one is the one you arrive at when you right-click on the printer and
+select <guimenuitem>Print Settings...</guimenuitem>. This is the one that you were taught to use back in the
+days of Windows NT, so it is only natural to try the same way with Windows 200x/XP. You would not dream that
+there is now a different path to arrive at an identical-looking, but functionally different, dialog to set
+defaults for all users.
+</para></formalpara>
+
+<tip><para>Try (on Windows 200x/XP) to run this command (as a user with the right privileges):
+<indexterm><primary>rundll32</primary></indexterm>
+</para>
+
+<para><userinput>
+rundll32 printui.dll,PrintUIEntry /p /t3 /n\\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printersharename</replaceable>
+</userinput></para>
+
+<para>
+To see the tab with the <guilabel>Printing Defaults</guilabel> button (the one you need), also run this command:
+</para>
+
+<para><userinput>
+rundll32 printui.dll,PrintUIEntry /p /t0 /n\\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printersharename</replaceable>
+</userinput></para>
+
+<para>
+To see the tab with the <guilabel>Printing Preferences</guilabel>
+button (the one that does not set systemwide defaults), you can
+start the commands from inside a DOS box or from <guimenu>Start</guimenu> -> <guimenuitem>Run</guimenuitem>.
+</para>
+</tip>
+
+</sect2>
+
+<sect2>
+<title>Supporting Large Numbers of Printers</title>
+
+<para>
+One issue that has arisen during the recent development phase of Samba is the need to support driver
+downloads for hundreds of printers. Using Windows NT APW for this task is somewhat awkward (to say the least). If
+you do not want to acquire RSS pains from the printer installation clicking orgy alone, you need
+to think about a non-interactive script.
+</para>
+
+<para>
+If more than one printer is using the same driver, the <command>rpcclient setdriver</command>
+command can be used to set the driver associated with an installed queue. If the driver is uploaded to
+<smbconfsection name="[print$]"/> once and registered with the printing TDBs, it can be used by
+multiple print queues. In this case, you just need to repeat the <command>setprinter</command> subcommand of
+<command>rpcclient</command> for every queue (without the need to conduct the <command>adddriver</command>
+repeatedly). The following is an example of how this can be accomplished:
+</para>
+
+<para><screen>
+&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumdrivers'</userinput>
+ cmd = enumdrivers
+ 
+ [Windows NT x86]
+ Printer Driver Info 1:
+   Driver Name: [infotec  IS 2075 PCL 6]
+ 
+ Printer Driver Info 1:
+   Driver Name: [DANKA InfoStream]
+ 
+ Printer Driver Info 1:
+   Driver Name: [Heidelberg Digimaster 9110 (PS)]
+ 
+ Printer Driver Info 1:
+   Driver Name: [dm9110]
+
+ Printer Driver Info 1:
+   Driver Name: [mydrivername]
+
+ [....]
+</screen>
+
+<screen>
+&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumprinters'</userinput>
+ cmd = enumprinters
+   flags:[0x800000]
+   name:[\\SAMBA-CUPS\dm9110]
+   description:[\\SAMBA-CUPS\dm9110,,110ppm HiVolume DANKA Stuttgart]
+   comment:[110 ppm HiVolume DANKA Stuttgart]
+ [....]
+</screen>
+
+<screen>
+&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c \
+  'setdriver <replaceable>dm9110</replaceable> "<replaceable>Heidelberg Digimaster 9110 (PS)</replaceable>"'</userinput>
+ cmd = setdriver dm9110 Heidelberg Digimaster 9110 (PPD)
+ Successfully set dm9110 to driver Heidelberg Digimaster 9110 (PS).
+</screen>
+
+<screen>
+&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumprinters'</userinput>
+ cmd = enumprinters
+   flags:[0x800000]
+   name:[\\SAMBA-CUPS\dm9110]
+   description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),\
+     110ppm HiVolume DANKA Stuttgart]
+   comment:[110ppm HiVolume DANKA Stuttgart]
+ [....]
+</screen>
+
+<screen>
+&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'setdriver <replaceable>dm9110</replaceable> <replaceable>mydrivername</replaceable>'</userinput>
+ cmd = setdriver dm9110 mydrivername
+ Successfully set dm9110 to mydrivername.
+</screen>
+
+<screen>
+&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumprinters'</userinput>
+ cmd = enumprinters
+   flags:[0x800000]
+   name:[\\SAMBA-CUPS\dm9110]
+   description:[\\SAMBA-CUPS\dm9110,mydrivername,\
+     110ppm HiVolume DANKA Stuttgart]
+   comment:[110ppm HiVolume DANKA Stuttgart]
+ [....]
+</screen></para>
+
+<para>
+It may not be easy to recognize that the first call to <command>enumprinters</command> showed the
+<quote>dm9110</quote> printer with an empty string where the driver should have been listed (between
+the two commas in the description field). After the <command>setdriver</command> command
+succeeds, all is well.
+</para>
+</sect2>
+
+<sect2>
+<title>Adding New Printers with the Windows NT APW</title>
+
+<para>
+By default, Samba exhibits all printer shares defined in &smb.conf; in the <guiicon>Printers</guiicon>
+folder. Also located in this folder is the Windows NT Add Printer Wizard icon. The APW will be shown only if:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	The connected user is able to successfully execute an <command>OpenPrinterEx(\\server)</command> with
+	administrative privileges (i.e., root or <smbconfoption name="printer admin"/>).
+	</para>
+
+	<tip><para> Try this from a Windows 200x/XP DOS box command prompt:
+	</para>
+
+	<para><userinput>
+	runas /netonly /user:root rundll32 printui.dll,PrintUIEntry /p /t0 /n \\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printersharename</replaceable>
+	</userinput></para>
+
+	<para>
+	Click on <guibutton>Printing Preferences</guibutton>.
+	</para></tip></listitem>
+
+	<listitem><para>... contains the setting
+	<smbconfoption name="show add printer wizard">yes</smbconfoption> (the
+	default).</para></listitem>
+</itemizedlist>
+
+<para>
+The APW can do various things:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Upload a new driver to the Samba <smbconfsection name="[print$]"/> share.
+	</para></listitem>
+
+	<listitem><para>
+	Associate an uploaded driver with an existing (but still driverless) print queue.
+	</para></listitem>
+
+	<listitem><para>
+	Exchange the currently used driver for an existing print queue with one that has been uploaded before.
+	</para></listitem>
+
+	<listitem><para>
+	Add an entirely new printer to the Samba host (only in conjunction with a working
+	<smbconfoption name="add printer command"/>. A corresponding
+	<smbconfoption name="delete printer command"/> for removing entries from the
+	<guiicon>Printers</guiicon> folder may also be provided).
+	</para></listitem>
+</itemizedlist>
+
+<para>
+The last one (add a new printer) requires more effort than the previous ones. To use the APW to successfully
+add a printer to a Samba server, the <smbconfoption name="add printer command"/> must have a defined value.
+The program hook must successfully add the printer to the UNIX print system (i.e., to
+<filename>/etc/printcap</filename>, <filename>/etc/cups/printers.conf</filename> or other appropriate files)
+and to &smb.conf; if necessary.
+</para>
+
+<para>
+When using the APW from a client, if the named printer share does not exist, smbd will execute the
+<smbconfoption name="add printer command"/> and reparse to attempt to locate the new printer share. If the
+share is still not defined, an error of "<errorname>Access Denied"</errorname> is returned to the client. The
+<smbconfoption name="add printer command"/> is executed under the context of the connected user, not
+necessarily a root account. A <smbconfoption name="map to guest">bad user</smbconfoption> may have connected
+you unwittingly under the wrong privilege. You should check it by using the <command>smbstatus</command>
+command.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Error Message: <quote>Cannot connect under a different Name</quote></title>
+
+<para>
+Once you are connected with the wrong credentials, there is no means to reverse the situation other than
+to close all Explorer windows, and perhaps reboot.
+</para>
+
+<itemizedlist>
+	<listitem><para>
+<indexterm><primary>net use</primary></indexterm>
+	The <command>net use \\SAMBA-SERVER\sharename /user:root</command> gives you an error message:
+	<quote>Multiple connections to a server or a shared resource by the same user utilizing
+	several user names are not allowed. Disconnect all previous connections to the server,
+	esp. the shared resource, and try again.</quote>
+	</para></listitem>
+
+	<listitem><para>
+	Every attempt to <quote>connect a network drive</quote> to <filename>\\SAMBASERVER\\print$</filename>
+	to <constant>z:</constant> is countered by the pertinacious message: <quote>This
+	network folder is currently connected under different credentials (username and password).
+	Disconnect first any existing connection to this network share in order to connect again under
+	a different username and password</quote>.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+So you close all connections. You try again. You get the same message. You check from the Samba side, using
+<command>smbstatus</command>. Yes, there are more connections. You kill them all. The client still gives you
+the same error message. You watch the smbd.log file on a high debug level and try reconnect. Same error
+message, but not a single line in the log. You start to wonder if there was a connection attempt at all. You
+run ethereal and tcpdump while you try to connect. Result: not a single byte goes on the wire. Windows still
+gives the error message. You close all Explorer windows and start it again. You try to connect &smbmdash; and
+this times it works!  Windows seems to cache connection information somewhere and does not keep it up to date
+(if you are unlucky, you might need to reboot to get rid of the error message).
+</para>
+
+<para>
+The easiest way to forcefully terminate all connections from your client to a server is by executing:
+<screen>
+&dosprompt; net use * /delete
+</screen>
+This will also disconnect all mapped drives and will allow you create fresh connection as required.
+</para>
+</sect2>
+
+<sect2>
+<title>Take Care When Assembling Driver Files</title>
+
+<para>
+You need to be extremely careful when you take notes about the files belonging to a particular
+driver. Don't confuse the files for driver version <quote>0</quote> (for Windows 9x/Me, going into
+<filename>[print$]/WIN/0/</filename>), driver version <filename>2</filename> (kernel mode driver for Windows NT,
+going into <filename>[print$]/W32X86/2/</filename>; may be used on Windows 200x/XP also), and
+driver version <quote>3</quote> (non-kernel mode driver going into <filename>[print$]/W32X86/3/</filename>;
+cannot be used on Windows NT). Quite often these different driver versions contain
+files that have the same name but actually are very different. If you look at them from
+the Windows Explorer (they reside in <filename>%WINDOWS%\system32\spool\drivers\W32X86\</filename>),
+you will probably see names in capital letters, while an <command>enumdrivers</command> command from Samba
+would show mixed or lowercase letters, so it is easy to confuse them. If you install them manually using
+<command>rpcclient</command> and subcommands, you may even succeed without an error message. Only later,
+when you try install on a client, you will encounter error messages like <computeroutput>This server
+has no appropriate driver for the printer</computeroutput>.
+</para>
+
+<para>
+Here is an example. You are invited to look closely at the various files, compare their names and
+their spelling, and discover the differences in the composition of the version 2 and 3 sets. Note: the
+version 0 set contained 40 <parameter>Dependentfiles</parameter>, so I left it out for space reasons:
+</para>
+
+<para><screen>
+&rootprompt;<userinput>rpcclient -U 'Administrator%<replaceable>secret</replaceable>' -c 'enumdrivers 3' 10.160.50.8 </userinput>
+
+ Printer Driver Info 3:
+         Version: [3]
+         Driver Name: [Canon iR8500 PS3]
+         Architecture: [Windows NT x86]
+         Driver Path: [\\10.160.50.8\print$\W32X86\3\cns3g.dll]
+         Datafile: [\\10.160.50.8\print$\W32X86\3\iR8500sg.xpd]
+         Configfile: [\\10.160.50.8\print$\W32X86\3\cns3gui.dll]
+         Helpfile: [\\10.160.50.8\print$\W32X86\3\cns3g.hlp]
+ 
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aucplmNT.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\ucs32p.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\tnl32.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussdrv.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cnspdc.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussapi.dat]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3407.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\CnS3G.cnt]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBAPI.DLL]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBIPC.DLL]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcview.exe]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcdspl.exe]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcedit.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm.exe]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcspl.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cfine32.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcr407.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\Cpcqm407.hlp]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm407.cnt]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3ggr.dll]
+ 
+         Monitorname: []
+         Defaultdatatype: []
+
+ Printer Driver Info 3:
+         Version: [2]
+         Driver Name: [Canon iR5000-6000 PS3]
+         Architecture: [Windows NT x86]
+         Driver Path: [\\10.160.50.8\print$\W32X86\2\cns3g.dll]
+         Datafile: [\\10.160.50.8\print$\W32X86\2\IR5000sg.xpd]
+         Configfile: [\\10.160.50.8\print$\W32X86\2\cns3gui.dll]
+         Helpfile: [\\10.160.50.8\print$\W32X86\2\cns3g.hlp]
+ 
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\2\AUCPLMNT.DLL]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussdrv.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cnspdc.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussapi.dat]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3407.dll]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\2\CnS3G.cnt]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBAPI.DLL]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBIPC.DLL]
+         Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3gum.dll]
+ 
+         Monitorname: [CPCA Language Monitor2]
+         Defaultdatatype: []
+
+</screen></para>
+
+<para>
+If we write the <quote>version 2</quote> files and the <quote>version 3</quote> files
+into different text files and compare the result, we see this
+picture:
+</para>
+
+<para><screen>
+&rootprompt;<userinput>sdiff 2-files 3-files</userinput>
+
+<![CDATA[
+ cns3g.dll                     cns3g.dll
+ iR8500sg.xpd                  iR8500sg.xpd
+ cns3gui.dll                   cns3gui.dll
+ cns3g.hlp                     cns3g.hlp
+ AUCPLMNT.DLL                | aucplmNT.dll
+                             > ucs32p.dll
+                             > tnl32.dll
+ aussdrv.dll                   aussdrv.dll
+ cnspdc.dll                    cnspdc.dll
+ aussapi.dat                   aussapi.dat
+ cns3407.dll                   cns3407.dll
+ CnS3G.cnt                     CnS3G.cnt
+ NBAPI.DLL                     NBAPI.DLL
+ NBIPC.DLL                     NBIPC.DLL
+ cns3gum.dll                 | cpcview.exe
+                             > cpcdspl.exe 
+                             > cpcqm.exe
+                             > cpcspl.dll
+                             > cfine32.dll
+                             > cpcr407.dll
+                             > Cpcqm407.hlp
+                             > cpcqm407.cnt
+                             > cns3ggr.dll
+]]>
+</screen>
+
+Do not be fooled! Driver files for each version with identical
+names may be different in their content, as you can see from this size
+comparison:
+</para>
+
+<para><screen>
+&rootprompt;<userinput>for i in cns3g.hlp cns3gui.dll cns3g.dll; do                  \
+           smbclient //10.160.50.8/print\$ -U 'Administrator%xxxx' \
+           -c "cd W32X86/3; dir $i; cd .. ; cd 2; dir $i";      \
+		   done</userinput>
+
+  CNS3G.HLP               A   122981  Thu May 30 02:31:00 2002
+  CNS3G.HLP               A    99948  Thu May 30 02:31:00 2002
+
+  CNS3GUI.DLL             A  1805824  Thu May 30 02:31:00 2002
+  CNS3GUI.DLL             A  1785344  Thu May 30 02:31:00 2002
+
+  CNS3G.DLL               A  1145088  Thu May 30 02:31:00 2002
+  CNS3G.DLL               A    15872  Thu May 30 02:31:00 2002
+</screen></para>
+
+<para>
+In my example were even more differences than shown here. Conclusion: you must be careful to select the
+correct driver files for each driver version. Don't rely on the names alone, and don't interchange files
+belonging to different driver versions.
+</para>
+</sect2>
+
+<sect2>
+<title>Samba and Printer Ports</title>
+
+<para>
+<indexterm><primary>LPT1:</primary></indexterm>
+<indexterm><primary>COM1:</primary></indexterm>
+<indexterm><primary>FILE:</primary></indexterm>
+<indexterm><primary>available port</primary></indexterm>
+Windows NT/2000 print servers associate a port with each printer. These normally take the form of
+<filename>LPT1:</filename>, <filename>COM1:</filename>, <filename>FILE:</filename>, and so on. Samba must also
+support the concept of ports associated with a printer. By default, only one printer port, named <quote>Samba
+Printer Port</quote>, exists on a system. Samba does not really need such a <quote>port</quote> in order to
+print; rather it is a requirement of Windows clients. They insist on being told about an available port when
+they request this information; otherwise, they throw an error message at you. So Samba fakes the port
+information to keep the Windows clients happy.
+</para>
+
+<para>
+<indexterm><primary>Printer Pooling</primary></indexterm>
+Samba does not support the concept of <constant>Printer Pooling</constant> internally either. Printer
+pooling assigns a logical printer to multiple ports as a form of load balancing or failover.
+</para>
+
+<para>
+If you require multiple ports to be defined for some reason or another (my users and my boss should not know
+that they are working with Samba), configure the <smbconfoption name="enumports command"/>,
+which can be used to define an external program that generates a listing of ports on a system.
+</para>
+</sect2>
+
+<sect2>
+<title>Avoiding Common Client Driver Misconfiguration</title>
+
+<para>
+So now the printing works, but there are still problems. Most jobs print well, some do not print at
+all. Some jobs have problems with fonts, which do not look good. Some jobs print fast and some
+are dead-slow. We cannot cover it all, but we want to encourage you to read the brief paragraph about
+<quote>Avoiding the Wrong PostScript Driver Settings</quote> in <link linkend="CUPS-printing">CUPS Printing
+Chapter</link>, <link linkend="cups-avoidps1">Avoiding Critical PostScript Driver Settings on the
+Client</link>.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>The Imprints Toolset</title>
+
+<para>
+<indexterm><primary>Imprints</primary></indexterm>
+The Imprints tool set provides a UNIX equivalent of the Windows NT APW.  For complete information, please
+refer to the <ulink url="http://imprints.sourceforge.net/">Imprints</ulink> Web site as well as the
+documentation included with the Imprints source distribution. This section provides only a brief introduction
+to the features of Imprints.
+</para>
+
+<para>
+Unfortunately, the Imprints toolset is no longer maintained. As of December 2000, the project is in
+need of a new maintainer. The most important skill to have is Perl coding and an interest in MS-RPC-based
+printing used in Samba. If you wish to volunteer, please coordinate your efforts on the Samba technical
+mailing list. The toolset is still in usable form, but only for a series of older printer models where
+there are prepared packages to use. Packages for more up-to-date print devices are needed if Imprints
+should have a future. Information regarding the Imprints toolset can be obtained from the <ulink
+url="http://imprints.sourceforge.net/">Imprints</ulink> home page.
+</para>
+
+<sect2>
+<title>What Is Imprints?</title>
+
+<para>
+Imprints is a collection of tools for supporting these goals:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Providing a central repository of information regarding Windows NT and 95/98 printer driver packages.
+	</para></listitem>
+
+	<listitem><para>
+	Providing the tools necessary for creating the Imprints printer driver packages.
+	</para></listitem>
+
+	<listitem><para>
+	Providing an installation client that will obtain printer drivers from a central Internet (or intranet) Imprints Server
+	repository and install them on remote Samba and Windows NT4 print servers.
+	</para></listitem>
+</itemizedlist>
+</sect2>
+
+<sect2>
+<title>Creating Printer Driver Packages</title>
+
+<para>
+The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt,
+included with the Samba distribution for more information). In short, an Imprints driver package
+is a gzipped tarball containing the driver files, related INF files, and a control file needed by the
+installation client.
+</para>
+</sect2>
+
+<sect2>
+<title>The Imprints Server</title>
+
+<para>
+The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each
+printer entry in the database has an associated URL for the actual downloading of the package. Each
+package is digitally signed via GnuPG, which can be used to verify that
+the package downloaded is actually
+the one referred in the Imprints database. It is strongly recommended that this security check
+not be disabled.
+</para>
+</sect2>
+
+<sect2>
+<title>The Installation Client</title>
+
+<para>
+More information regarding the Imprints installation client is available from the documentation file
+<filename>Imprints-Client-HOWTO.ps</filename> that is included with the Imprints source package. The Imprints
+installation client comes in two forms:
+</para>
+
+<itemizedlist>
+	<listitem><para>A set of command-line Perl scripts.</para></listitem>
+	<listitem><para>A GTK+-based graphical interface to the command-line Perl scripts.</para></listitem>
+</itemizedlist>
+
+<para>
+The installation client (in both forms) provides a means of querying the Imprints database server for
+a matching list of known printer model names as well as a means to download and install the drivers on
+remote Samba and Windows NT print servers.
+</para>
+
+<para>
+The basic installation process is in four steps, and Perl code is wrapped around smbclient and rpcclient.
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	For each supported architecture for a given driver:
+	<orderedlist>
+		<listitem><para>rpcclient: Get the appropriate upload directory on the remote server.</para></listitem>
+		<listitem><para>smbclient: Upload the driver files.</para></listitem>
+		<listitem><para>rpcclient: Issues an AddPrinterDriver() MS-RPC.</para></listitem>
+	</orderedlist>
+	</para></listitem>
+
+	<listitem><para>rpcclient: Issues an AddPrinterEx() MS-RPC to actually create the printer.</para></listitem>
+</itemizedlist>
+
+<para>
+One of the problems encountered when implementing the Imprints tool set was the namespace issues between
+various supported client architectures. For example, Windows NT includes a driver named <quote>Apple LaserWriter
+II NTX v51.8</quote>, and Windows 95 calls its version of this driver <quote>Apple LaserWriter II NTX</quote>.
+</para>
+
+<para>
+The problem is how to know what client drivers have been uploaded for a printer. An astute reader will
+remember that the Windows NT Printer Properties dialog only includes space for one printer driver name. A
+quick look in the Windows NT 4.0 system registry at:
+</para>
+
+<para><filename>
+ HKLM\System\CurrentControlSet\Control\Print\Environment
+</filename></para>
+
+<para>
+will reveal that Windows NT always uses the NT driver name. This is okay because Windows NT always requires
+that at least the Windows NT version of the printer driver is present. Samba does not have the
+requirement internally; therefore, <quote>How can you use the NT driver name if it has not already been installed?</quote>
+</para>
+
+<para>
+The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and
+95/98 printer drivers and that the NT driver is installed first.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Adding Network Printers without User Interaction</title>
+
+<para>
+The following MS Knowledge Base article may be of some help if you need to handle Windows 2000 clients:
+<emphasis>How to Add Printers with No User Interaction in Windows 2000,</emphasis> (<ulink
+url="http://support.microsoft.com/default.aspx?scid=kb;en-us;189105">Microsoft KB 189105</ulink>).  It also
+applies to Windows XP Professional clients.  The ideas sketched out in this section are inspired by this
+article, which describes a command-line method that can be applied to install network and local printers and
+their drivers. This is most useful if integrated in Logon Scripts. You can see what options are available by
+typing in the command prompt (<command>DOS box</command>):
+</para>
+
+<para><userinput>rundll32 printui.dll,PrintUIEntry /?</userinput></para>
+
+<para>
+A window pops up that shows you all of the command-line switches available. An extensive list of examples
+is also provided. This is only for Windows 200x/XP; it does not work on Windows NT. Windows NT probably has
+some other tools in the respective Resource Kit. Here is a suggestion about what a client logon script
+might contain, with a short explanation of what the lines actually do (it works if 200x/XP Windows
+clients access printers via Samba, and works for Windows-based print servers too):
+</para>
+
+<para><screen>
+<userinput>rundll32 printui.dll,PrintUIEntry /dn /n "\\cupsserver\infotec2105-IPDS" /q</userinput>
+<userinput>rundll32 printui.dll,PrintUIEntry /in /n "\\cupsserver\infotec2105-PS"</userinput>
+<userinput>rundll32 printui.dll,PrintUIEntry /y /n "\\cupsserver\infotec2105-PS"</userinput>
+</screen></para>
+
+<para>
+Here is a list of the used command-line parameters: 
+</para>
+
+<variablelist>
+	<varlistentry><term>/dn</term>
+		<listitem><para>deletes a network printer.</para></listitem>
+	</varlistentry>
+	<varlistentry><term>/q</term>
+		<listitem><para>quiet modus.</para></listitem>
+	</varlistentry>
+	<varlistentry><term>/n</term>
+		<listitem><para>names a printer.</para></listitem>
+	</varlistentry>
+	<varlistentry><term>/in</term>
+		<listitem><para>adds a network printer connection.</para></listitem>
+	</varlistentry>
+	<varlistentry><term>/y</term>
+		<listitem><para>sets printer as default printer.</para></listitem>
+	</varlistentry>
+</variablelist>
+
+<itemizedlist>
+	<listitem><para>
+	Line 1 deletes a possibly existing previous network printer <emphasis>infotec2105-IPDS</emphasis>
+	(which had used native Windows drivers with LPRng that were removed from the server that was
+	converted to CUPS). The <command>/q</command> at the end prevents confirm
+	or error dialog boxes from popping up. They should not be presented to the user logging on.
+	</para></listitem>
+
+	<listitem><para>	
+	Line 2 adds the new printer
+	<emphasis>infotec2105-PS</emphasis> (which actually is the same
+	physical device but is now run by the new CUPS printing system and associated with the
+	CUPS/Adobe PS drivers). The printer and its driver must have been added to Samba prior to
+	the user logging in (e.g., by a procedure as discussed earlier in this chapter or by running
+	<command>cupsaddsmb</command>). The driver is now autodownloaded to the client PC where the
+	user is about to log in.
+	</para></listitem>
+
+	<listitem><para>
+	Line 3 sets the default printer to this new network printer (there might be several other
+	printers installed with this same method, and some may be local as well, so we decide for a
+	default printer). The default printer selection may, of course, be different for different users.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+The second line only works if the printer <emphasis>infotec2105-PS</emphasis> has an already working
+print queue on the <constant>cupsserver</constant> and if the
+printer drivers have been successfully uploaded
+(via the <command>APW</command>, <command>smbclient/rpcclient</command>, or <command>cupsaddsmb</command>)
+into the <smbconfsection name="[print$]"/> driver repository of Samba. Some Samba versions
+prior to version 3.0 required a restart of smbd after the printer install and the driver upload;
+otherwise the script (or any other client driver download) would fail.
+</para>
+
+<para>
+Since there is no easy way to test for the existence of an installed network printer from the logon script,
+do not bother checking. Just allow the de-installation/re-installation to occur every time a user logs in;
+it's really quick anyway (1 to 2 seconds).
+</para>
+
+<para>
+The additional benefits for this are:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	It puts in place any printer default setup changes automatically at every user logon.
+	</para></listitem>
+
+	<listitem><para>
+	It allows for <quote>roaming</quote> users' login to the domain from different workstations.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+Since network printers are installed per user, this much simplifies the process of keeping the installation
+up to date. The few extra seconds at logon time will not really be noticeable. Printers can be centrally
+added, changed, and deleted at will on the server with no user intervention required from the clients
+(you just need to keep the logon scripts up to date).
+</para>
+</sect1>
+
+<sect1>
+<title>The <command>addprinter</command> Command</title>
+
+<para>
+The <command>addprinter</command> command can be configured to be a shell script or program executed by
+Samba. It is triggered by running the APW from a client against the Samba print server. The APW asks
+the user to fill in several fields (such as printer name, driver to be used, comment, port monitor,
+and so on). These parameters are passed on to Samba by the APW. If the addprinter command is designed in a
+way that it can create a new printer (through writing correct printcap entries on legacy systems or
+by executing the <command>lpadmin</command> command on more modern systems) and create the associated share,
+then the APW will in effect really create a new printer on Samba and the UNIX print subsystem!
+</para>
+</sect1>
+
+<sect1>
+<title>Migration of Classical Printing to Samba</title>
+
+<para>
+The basic NT-style printer driver management has not changed considerably in 3.0 over the 2.2.x releases
+(apart from many small improvements). Here migration should be quite easy, especially if you followed
+previous advice to stop using deprecated parameters in your setup. For migrations from an existing 2.0.x
+setup, or if you continued Windows 9x/Me-style printing in your Samba 2.2 installations, it is more of
+an effort. Please read the appropriate release notes and the HOWTO Collection for Samba-2.2.x. You can
+follow several paths. Here are possible scenarios for migration:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	You need to study and apply the new Windows NT printer and driver support. Previously used
+	parameters <parameter>printer driver file</parameter>, <parameter>printer driver</parameter>,
+	and <parameter>printer driver location</parameter> are no longer supported.
+	</para></listitem>
+
+	<listitem><para>
+	If you want to take advantage of Windows NT printer driver support, you also need to migrate the
+	Windows 9x/Me drivers to the new setup.
+	</para></listitem>
+
+	<listitem><para>
+	An existing <filename>printers.def</filename> file (the one specified in the now removed parameter
+	<parameter>printer driver file</parameter>) will no longer work with Samba-3. In 3.0, smbd attempts
+	to locate Windows 9x/Me driver files for the printer in <smbconfsection name="[print$]"/>
+	and additional settings in the TDB and only there; if it fails, it will <emphasis>not</emphasis>
+	(as 2.2.x used to do) drop down to using a <filename>printers.def</filename> (and all associated
+	parameters). The make_printerdef tool is removed and there is no backward compatibility for this.
+	</para></listitem>
+
+	<listitem><para>You need to install a Windows 9x/Me driver into the
+	<smbconfsection name="[print$]"/> share for a printer on your Samba
+	host. The driver files will be stored in the <quote>WIN40/0</quote> subdirectory of
+	<smbconfsection name="[print$]"/>, and some other settings and information go
+	into the printing-related TDBs.</para></listitem>
+
+	<listitem><para>
+	If you want to migrate an existing <filename>printers.def</filename> file into the new setup, the only current
+	solution is to use the Windows NT APW to install the NT drivers and the 9x/Me drivers. This can be scripted
+	using smbclient and rpcclient. See the Imprints installation client on the <ulink noescape="1"
+	url="http://imprints.sourceforge.net/">Imprints</ulink> web site for example. See also the discussion of
+	rpcclient usage in <link linkend="CUPS-printing">CUPS Printing</link>.
+	</para></listitem>
+</itemizedlist>
+</sect1>
+
+<sect1>
+<title>Publishing Printer Information in Active Directory or LDAP</title>
+
+<para>
+This topic has also been addressed in <link linkend="NetCommand">Remote and Local Management &smbmdash; The
+Net Command</link>. If you wish to volunteer your services to help document this further, please contact 
+<ulink url="mail://jht@samba.org">John H. Terpstra</ulink>.
+</para>
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<sect2>
+<title>I Give My Root Password but I Do Not Get Access</title>
+
+<para>
+Do not confuse the root password, which is valid for the UNIX system (and in most cases stored in the
+form of a one-way hash in a file named <filename>/etc/shadow</filename>), with the password used to
+authenticate against Samba. Samba does not know the UNIX password. Root access to Samba resources
+requires that a Samba account for root must first be created. This is done with the <command>smbpasswd</command>
+command as follows:
+<screen>
+&rootprompt; smbpasswd -a root
+New SMB password: secret
+Retype new SMB password: secret
+</screen>
+</para>
+
+</sect2>
+
+<sect2>
+<title>My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</title>
+
+<para>
+Do not use the existing UNIX print system spool directory for the Samba spool directory. It may seem
+convenient and a savings of space, but it only leads to problems. The two must be separate. The UNIX/Linux
+system print spool directory (e.g., <filename>/var/spool/cups</filename>) is typically owned by a
+non-privileged user such as <literal>cups</literal> or <literal>lp</literal>. Additionally. the permissions on
+the spool directory are typically restrictive to the owner and/or group. On the other hand, the Samba
+spool directory must be world writable, and should have the 't' bit set to ensure that only a temporary
+spool file owner can change or delete the file.
+</para>
+
+<para>
+Depending on the type of print spooling system in use on the UNIX/Linux host, files that the spool
+management application finds and that are not currently part of job queue that it is managing can be deleted.
+This may explain the observation that jobs are spooled (by Samba) into this directory and just disappear.
+</para>
+
+</sect2>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Problems.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Problems.xml
new file mode 100644
index 00000000000..8f1d3c1849e
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Problems.xml
@@ -0,0 +1,329 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="problems">
+
+<chapterinfo>
+	&author.jerry;
+	&author.jelmer;
+	&author.dbannon;
+	&author.danshearer;
+	<pubdate>8 Apr 2003</pubdate>
+</chapterinfo>
+
+<title>Analyzing and Solving Samba Problems</title>
+
+<para>
+<indexterm><primary>RFCs</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>documentation</primary></indexterm>
+There are many sources of information available in the form of mailing lists, RFCs, and documentation. The
+documentation that comes with the Samba distribution contains good explanations of general SMB topics such as
+browsing.
+</para> 
+	
+<sect1>
+<title>Diagnostics Tools</title>
+
+<para>
+<indexterm><primary>sniffer</primary></indexterm>
+<indexterm><primary>LAN</primary></indexterm>
+<indexterm><primary>analyzes data</primary></indexterm>
+<indexterm><primary>SMB networking</primary></indexterm>
+<indexterm><primary>network analyzer</primary></indexterm>
+With SMB networking, it is often not immediately clear what the cause is of a certain problem. Samba itself
+provides rather useful information, but in some cases you might have to fall back to using a
+<emphasis>sniffer</emphasis>. A sniffer is a program that listens on your LAN, analyzes the data sent on it,
+and displays it on the screen.
+</para>
+
+<sect2>
+<title>Debugging with Samba Itself</title>
+
+<para>
+<indexterm><primary>diagnostic tools</primary></indexterm>
+<indexterm><primary>debugging problems</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>debugging passwords</primary></indexterm>
+<indexterm><primary>debug level</primary></indexterm>
+<indexterm><primary>log level</primary></indexterm>
+One of the best diagnostic tools for debugging problems is Samba itself.  You can use the <option>-d
+option</option> for both &smbd; and &nmbd; to specify the <smbconfoption name="debug level"/> at which to run.
+See the man pages for <command>smbd, nmbd</command>, and &smb.conf; for more information regarding debugging
+options. The debug level (log level) can range from 1 (the default) to 10 (100 for debugging passwords).
+</para>
+	
+<para>
+<indexterm><primary>debugging</primary></indexterm>
+<indexterm><primary>gcc</primary></indexterm>
+<indexterm><primary>gdb</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>LsaEnumTrustedDomains</primary></indexterm>
+<indexterm><primary>attach gdb</primary></indexterm>
+Another helpful method of debugging is to compile Samba using the <command>gcc -g </command> flag. This will
+include debug information in the binaries and allow you to attach <command>gdb</command> to the running
+<command>smbd/nmbd</command> process.  To attach <command>gdb</command> to an <command>smbd</command> process
+for an NT workstation, first get the workstation to make the connection. Pressing ctrl-alt-delete and going
+down to the domain box is sufficient (at least, the first time you join the domain) to generate a
+<parameter>LsaEnumTrustedDomains</parameter>. Thereafter, the workstation maintains an open connection and
+there will be an smbd process running (assuming that you haven't set a really short smbd idle timeout). So, in
+between pressing <command>ctrl-alt-delete</command> and actually typing in your password, you can attach
+<command>gdb</command> and continue.
+</para>
+
+<para>
+Some useful Samba commands worth investigating are:
+<indexterm><primary>testparm</primary></indexterm>
+<indexterm><primary>smbclient</primary></indexterm>
+<screen>
+&prompt;<userinput>testparm | more</userinput>
+&prompt;<userinput>smbclient -L //{netbios name of server}</userinput>
+</screen>
+</para>
+
+</sect2>
+
+<sect2>
+	<title>Tcpdump</title>
+  
+<para>
+<indexterm><primary>tcpdump</primary></indexterm>
+<indexterm><primary>tethereal</primary></indexterm>
+<indexterm><primary>ethereal</primary></indexterm>
+<ulink url="http://www.tcpdump.org/">Tcpdump</ulink> was the first 
+UNIX sniffer with SMB support. It is a command-line utility and 
+now, its SMB support is somewhat lagging that of <command>ethereal</command> 
+and <command>tethereal</command>.
+</para>
+
+</sect2>
+
+<sect2>
+	<title>Ethereal</title>
+
+<para>
+<indexterm><primary>ethereal</primary></indexterm>
+<ulink url="http://www.ethereal.com/">Ethereal</ulink> is a graphical sniffer, available for both UNIX (Gtk)
+and Windows. Ethereal's SMB support is quite good. For details on the use of <command>ethereal</command>, read
+the well-written Ethereal User Guide.
+</para>
+
+<figure id="ethereal1"><title>Starting a Capture.</title><imagefile>ethereal1</imagefile></figure>
+
+<para>
+<indexterm><primary>ports</primary></indexterm>
+Listen for data on ports 137, 138, 139, and 445. For example, use the filter <userinput>port 137, port 138,
+port 139, or port 445</userinput> as seen in <link linkend="ethereal1">Starting a Capture</link> snapshot.
+</para>
+
+<para>
+A console version of ethereal is available as well and is called <command>tethereal</command>.
+</para>
+
+<figure id="ethereal2"><title>Main Ethereal Data Window.</title><imagefile>ethereal2</imagefile></figure>
+
+</sect2>
+
+<sect2>
+<title>The Windows Network Monitor</title>
+	
+<para>
+<indexterm><primary>Network Monitor</primary></indexterm>
+<indexterm><primary>Netmon</primary></indexterm>
+<indexterm><primary>Microsoft Developer Network CDs</primary></indexterm>
+<indexterm><primary>SMS</primary></indexterm>
+<indexterm><primary>promiscuous mode</primary></indexterm>
+<indexterm><primary>ethereal</primary></indexterm>
+For tracing things on Microsoft Windows NT, Network Monitor (aka Netmon) is available on Microsoft Developer
+Network CDs, the Windows NT Server install CD, and the SMS CDs. The version of Netmon that ships with SMS
+allows for dumping packets between any two computers (i.e., placing the network interface in promiscuous
+mode).  The version on the NT Server install CD will only allow monitoring of network traffic directed to the
+local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write Netmon formatted
+files.
+</para>
+
+<sect3>
+<title>Installing Network Monitor on an NT Workstation</title>
+
+<para>
+<indexterm><primary>Netmon.</primary></indexterm>
+Installing Netmon on an NT workstation requires a couple of steps. The following are instructions for
+installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
+Workstation 4.0. The process should be similar for other versions of Windows NT version of Netmon. You will
+need both the Microsoft Windows NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
+</para> 
+
+<para>
+<indexterm><primary>Network Monitor Tools and Agent</primary></indexterm>
+Initially you will need to install <application>Network Monitor Tools and Agent</application>
+on the NT Server to do this: 
+</para>
+
+<itemizedlist>
+	<listitem><para>Go to <guibutton>Start</guibutton> -> <guibutton>Settings</guibutton> -> <guibutton>Control Panel</guibutton> -> 
+	<guibutton>Network</guibutton> -> <guibutton>Services</guibutton> -> <guibutton>Add</guibutton>.</para></listitem>
+	
+	<listitem><para>Select the <guilabel>Network Monitor Tools and Agent</guilabel> and click on <guibutton>OK</guibutton>.</para></listitem> 
+	
+	<listitem><para>Click on <guibutton>OK</guibutton> on the Network Control Panel.</para></listitem> 
+	
+	<listitem><para>Insert the Windows NT Server 4.0 install CD when prompted.</para></listitem> 
+</itemizedlist>
+
+<para>
+At this point, the Netmon files should exist in <filename>%SYSTEMROOT%\System32\netmon\*.*</filename>.   
+Two subdirectories exist as well: <filename>parsers\</filename>, which contains the necessary DLLs
+for parsing the Netmon packet dump, and <filename>captures\</filename>.
+</para>
+
+<para>
+To install the Netmon tools on an NT Workstation, you will first need to install the 
+Network  Monitor Agent from the Workstation install CD.
+</para>
+
+<itemizedlist>
+	<listitem><para>Go to <guibutton>Start</guibutton> -> <guibutton>Settings</guibutton> ->
+		<guibutton>Control Panel</guibutton> -> <guibutton>Network</guibutton> ->
+		<guibutton>Services</guibutton> -> <guibutton>Add</guibutton>.</para></listitem> 
+
+	<listitem><para>Select the <guilabel>Network Monitor Agent</guilabel>, click on
+		<guibutton>OK</guibutton>.</para></listitem> 
+	
+	<listitem><para>Click on <guibutton>OK</guibutton> in the Network Control Panel.
+	</para></listitem> 
+	
+	<listitem><para>Insert the Windows NT Workstation 4.0 install CD when prompted.</para></listitem> 
+</itemizedlist>
+
+<para>
+Now copy the files from the NT Server in <filename>%SYSTEMROOT%\System32\netmon</filename>
+to <filename>%SYSTEMROOT%\System32\netmon</filename> on the workstation and set permissions
+as you deem appropriate for your site. You will need administrative rights on the NT box to run Netmon.
+</para>
+
+</sect3>
+<sect3>
+<title>Installing Network Monitor on Windows 9x/Me</title>
+<para>
+To install Netmon on Windows 9x/Me, install the Network Monitor Agent 
+from the Windows 9x/Me CD (<filename>\admin\nettools\netmon</filename>). 
+There is a readme file included with the Netmon driver files on the CD if you need 
+information on how to do this. Copy the files from a working Netmon installation.
+</para>
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Useful URLs</title>
+<itemizedlist>
+
+<listitem><para>See how Scott Merrill simulates a BDC behavior at 
+       <ulink noescape="1" url="http://www.skippy.net/linux/smb-howto.html">
+       http://www.skippy.net/linux/smb-howto.html</ulink>. </para></listitem>
+
+<listitem><para>FTP site for older SMB specs, 
+       <ulink noescape="1" url="ftp://ftp.microsoft.com/developr/drg/CIFS/">
+       ftp://ftp.microsoft.com/developr/drg/CIFS/</ulink></para></listitem>.
+
+</itemizedlist>
+
+</sect1>
+
+<sect1>
+<title>Getting Mailing List Help</title>
+
+<para>
+There are a number of Samba-related mailing lists. Go to <ulink 
+noescape="1" url="http://samba.org">http://samba.org</ulink>, click on your nearest mirror,
+and then click on <command>Support</command>. Next, click on <command>
+Samba-related mailing lists</command>.
+</para>
+
+<para>
+For questions relating to Samba TNG, go to
+<ulink noescape="1" url="http://www.samba-tng.org/">http://www.samba-tng.org/</ulink>. 
+It has been requested that you do not post questions about Samba-TNG to the
+mainstream Samba lists.</para>
+
+<para>
+If you do post a message to one of the lists, please observe the following guidelines:
+</para>
+
+<itemizedlist>
+
+	<listitem><para>
+<indexterm><primary>volunteers</primary></indexterm>
+	Always remember that the developers are volunteers; they are
+	not paid and they never guarantee to produce a particular feature at 
+	a particular time. Any timelines are <quote>best guess,</quote> and nothing more.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>PDC</primary></indexterm>
+	Always mention what version of Samba you are using and what 
+	operating system it's running under. You should list the relevant sections of
+	your &smb.conf; file, at least the options in <smbconfsection name="[global]"/>
+	that affect PDC support.
+	</para></listitem>
+
+	<listitem><para>In addition to the version, if you obtained Samba via
+	CVS, mention the date when you last checked it out.</para></listitem>
+
+	<listitem><para> Try to make your questions clear and brief. Lots of long, 
+	convoluted questions get deleted before	they are completely read!
+	Do not post HTML-encoded messages. Most people on mailing lists simply delete
+	them.
+	</para></listitem>
+
+	<listitem><para> If you run one of those nifty <quote>I'm on holiday</quote> things when
+	you are away, make sure its configured to not answer mailing list traffic. Autoresponses
+	to mailing lists really irritate the thousands of people who end up having to deal
+	with such bad netiquet bahavior.
+	</para></listitem> 
+
+	<listitem><para>
+<indexterm><primary>cross post</primary></indexterm>
+	Don't cross post. Work out which is the best list to post to 
+	and see what happens. Do not post to both samba-ntdom and samba-technical.
+	Many people active on the lists subscribe to more 
+	than one list and get annoyed to see the same message two or more times.
+	Often someone who thinks a message would be better dealt 
+	with on another list will forward it on for you.</para></listitem>
+
+	<listitem><para>You might include <emphasis>partial</emphasis>
+	log files written at a log level set to as much as 20. 
+	Please do not send the entire log but just enough to give the context of the
+	error messages.</para></listitem>
+
+	<listitem><para>If you have a complete Netmon trace (from the opening of
+	the pipe to the error), you can send the *.CAP file as well.</para></listitem> 
+	    
+	<listitem><para>Please think carefully before attaching a document to an email.
+	Consider pasting the relevant parts into the body of the message. The Samba
+	mailing lists go to a huge number of people. Do they all need a copy of your 
+	&smb.conf; in their attach directory?</para></listitem>
+
+</itemizedlist>
+
+</sect1>
+
+<sect1>
+<title>How to Get Off the Mailing Lists</title>
+
+<para>To have your name removed from a Samba mailing list, go to the same
+place where you went to
+subscribe to it, go to <ulink noescape="1" url="http://lists.samba.org/">http://lists.samba.org</ulink>, 
+click on your nearest mirror, click on <command>Support</command>, and 
+then click on <command>Samba-related mailing lists</command>. 
+</para>
+
+<para>
+Please do not post messages to the list asking to be removed. You will only
+be referred to the above address (unless that process failed in some way).
+</para>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-ProfileMgmt.xml b/docs-xml/Samba3-HOWTO/TOSHARG-ProfileMgmt.xml
new file mode 100644
index 00000000000..571ca323ce6
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-ProfileMgmt.xml
@@ -0,0 +1,1320 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="ProfileMgmt">
+<chapterinfo>
+	&author.jht;
+    <pubdate>April 3 2003</pubdate>
+</chapterinfo>
+
+<title>Desktop Profile Management</title>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>roaming profiles</primary></indexterm>
+Roaming profiles are feared by some, hated by a few, loved by many, and a godsend for
+some administrators.
+</para>
+
+<para>
+<indexterm><primary>manage roaming profiles</primary></indexterm>
+Roaming profiles allow an administrator to make available a consistent user desktop
+as the user moves from one machine to another. This chapter provides much information
+regarding how to configure and manage roaming profiles.
+</para>
+
+<para>
+<indexterm><primary>local profiles</primary></indexterm>
+While roaming profiles might sound like nirvana to some, they are a real and tangible
+problem to others. In particular, users of mobile computing tools, where often there may not
+be a sustained network connection, are often better served by purely local profiles.
+This chapter provides information to help the Samba administrator deal with those
+situations.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Roaming Profiles</title>
+
+<warning>
+<para>
+Roaming profiles support is different for Windows 9x/Me and Windows NT4/200x.
+</para>
+</warning>
+
+<para>
+Before discussing how to configure roaming profiles, it is useful to see how
+Windows 9x/Me and Windows NT4/200x clients implement these features.
+</para>
+
+<para>
+<indexterm><primary>NetUserGetInfo</primary></indexterm>
+Windows 9x/Me clients send a NetUserGetInfo request to the server to get the user's
+profiles location. However, the response does not have room for a separate
+profiles location field, only the user's home share. This means that Windows 9x/Me
+profiles are restricted to being stored in the user's home directory.
+</para>
+
+
+<para>
+<indexterm><primary>NetSAMLogon</primary></indexterm>
+<indexterm><primary>RPC</primary></indexterm>
+Windows NT4/200x  clients send a NetSAMLogon RPC request, which contains many fields
+including a separate field for the location of the user's profiles.
+</para>
+
+<sect2>
+<title>Samba Configuration for Profile Handling</title>
+
+<para>
+This section documents how to configure Samba for MS Windows client profile support.
+</para>
+
+<sect3>
+<title>NT4/200x User Profiles</title>
+
+<para>
+For example, to support Windows NT4/200x clients, set the following in the [global] section of the &smb.conf; file:
+</para>
+
+<smbconfblock>
+	<smbconfoption name="logon path"> \\profileserver\profileshare\profilepath\%U\moreprofilepath</smbconfoption>
+</smbconfblock>
+
+<para>
+This is typically implemented like:
+<smbconfblock>
+<smbconfoption name="logon path">\\%L\Profiles\%U</smbconfoption>
+</smbconfblock>
+where <quote>%L</quote> translates to the name of the Samba server and <quote>%U</quote> translates to the username.
+</para>
+
+<para>
+The default for this option is <filename>\\%N\%U\profile</filename>, namely, <filename>\\sambaserver\username\profile</filename>. 
+The <filename>\\%N\%U</filename> service is created automatically by the [homes] service. If you are using
+a Samba server for the profiles, you must make the share that is specified in the logon path
+browseable. Please refer to the man page for &smb.conf; regarding the different
+semantics of <quote>%L</quote> and <quote>%N</quote>, as well as <quote>%U</quote> and <quote>%u</quote>.
+</para>
+
+<note><para>
+<indexterm><primary>logons</primary></indexterm>
+<indexterm><primary>disconnect a connection</primary></indexterm>
+MS Windows NT/200x clients at times do not disconnect a connection to a server between logons. It is recommended
+to not use the <smbconfsection name="homes"/> metaservice name as part of the profile share path.
+</para></note>
+</sect3>
+
+<sect3>
+<title>Windows 9x/Me User Profiles</title>
+
+<para>
+<indexterm><primary>net use /home</primary></indexterm>
+<indexterm><primary>logon home</primary></indexterm>
+To support Windows 9x/Me clients, you must use the <smbconfoption name="logon home"/>
+parameter. Samba has been fixed so <userinput>net use /home</userinput> now works as well and it, too, relies
+on the <parameter>logon home</parameter> parameter.
+</para>
+
+<para>
+<indexterm><primary>logon home</primary></indexterm>
+<indexterm><primary>\\%L\%U\.profiles</primary></indexterm>
+<indexterm><primary>.profiles</primary></indexterm>
+By using the <parameter>logon home</parameter> parameter, you are restricted to putting Windows 9x/Me profiles
+in the user's home directory.  But wait! There is a trick you can use. If you set the following in the
+<smbconfsection name="[global]"/> section of your &smb.conf; file:
+<smbconfblock>
+<smbconfoption name="logon home">\\%L\%U\.profiles</smbconfoption>
+</smbconfblock>
+then your Windows 9x/Me clients will dutifully put their clients in a subdirectory
+of your home directory called <filename>.profiles</filename> (making them hidden).
+</para>
+
+<para>
+<indexterm><primary>net use /home</primary></indexterm>
+Not only that, but <userinput>net use /home</userinput> will also work because of a feature in
+Windows 9x/Me. It removes any directory stuff off the end of the home directory area
+and only uses the server and share portion. That is, it looks like you
+specified <filename>\\%L\%U</filename> for <smbconfoption name="logon home"/>.
+</para>
+</sect3>
+
+<sect3>
+<title>Mixed Windows Windows 9x/Me and NT4/200x User Profiles</title>
+
+<para>
+You can support profiles for Windows 9x and Windows NT clients by setting both the
+<smbconfoption name="logon home"/> and <smbconfoption name="logon path"/> parameters. For example,
+</para>
+
+<para><smbconfblock>
+<smbconfoption name="logon home">\\%L\%U\.profiles</smbconfoption>
+<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
+</smbconfblock></para>
+
+<para>
+<indexterm><primary>mixed profile</primary></indexterm>
+Windows 9x/Me and NT4 and later profiles should not be stored in the same location because
+Windows NT4 and later will experience problems with mixed profile environments.
+</para>
+
+</sect3>
+<sect3>
+<title>Disabling Roaming Profile Support</title>
+
+<para>
+<indexterm><primary>disable roaming profiles</primary></indexterm>
+The question often asked is, <quote>How may I enforce use of local profiles?</quote> or
+<quote>How do I disable roaming profiles?</quote>
+</para>
+
+<para>
+<indexterm><primary>roaming profiles</primary></indexterm>
+There are three ways of doing this:
+</para>
+
+<indexterm><primary>windows registry settings</primary><secondary>roaming profiles</secondary></indexterm>
+
+<variablelist>
+	<varlistentry>
+		<term>In &smb.conf;</term>:
+		<listitem><para>
+		Affect the following settings and ALL clients will be forced to use a local profile:
+		<smbconfoption name="logon home"> </smbconfoption> and <smbconfoption name="logon path"> </smbconfoption>
+		</para>
+
+		<para>
+		The arguments to these parameters must be left blank. It is necessary to include the <constant>=</constant> sign
+		to specifically assign the empty value.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>MS Windows Registry:</term>
+		<listitem><para>
+<indexterm><primary>MMC</primary></indexterm>
+<indexterm><primary>local profile</primary></indexterm>
+		Use the Microsoft Management Console (MMC) <command>gpedit.msc</command> to instruct your MS Windows XP
+		machine to use only a local profile. This, of course, modifies registry settings. The full
+		path to the option is:
+<screen>
+Local Computer Policy\
+	Computer Configuration\
+		Administrative Templates\
+			System\
+				User Profiles\
+
+Disable: Only Allow Local User Profiles 
+Disable: Prevent Roaming Profile Change from Propagating to the Server
+</screen>
+	</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Change of Profile Type:</term>
+<indexterm><primary>Profile Type</primary></indexterm>
+		<listitem><para>From the start menu right-click on the <guiicon>My Computer</guiicon> icon,
+		select <guimenuitem>Properties</guimenuitem>, click on the <guilabel>User Profiles</guilabel>
+		tab, select the profile you wish to change from
+		<guimenu>Roaming</guimenu> type to <guimenu>Local</guimenu>, and click on
+		<guibutton>Change Type</guibutton>.
+		</para></listitem>
+	</varlistentry>
+</variablelist>
+
+<para>
+Consult the MS Windows registry guide for your particular MS Windows version for more information
+about which registry keys to change to enforce use of only local user profiles.
+</para>
+
+<note><para>
+<indexterm><primary>Windows Resource Kit</primary></indexterm>
+The specifics of how to convert a local profile to a roaming profile, or a roaming profile
+to a local one, vary according to the version of MS Windows you are running. Consult the Microsoft MS
+Windows Resource Kit for your version of Windows for specific information.
+</para></note>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>Windows Client Profile Configuration Information</title>
+
+<sect3>
+<title>Windows 9x/Me Profile Setup</title>
+
+<para>
+When a user first logs in on Windows 9x, the file user.DAT is created, as are folders <filename>Start
+Menu</filename>, <filename>Desktop</filename>, <filename>Programs</filename>, and
+<filename>Nethood</filename>. These directories and their contents will be merged with the local versions
+stored in <filename>c:\windows\profiles\username</filename> on subsequent logins, taking the most recent from
+each.	You will need to use the <smbconfsection name="[global]"/> options <smbconfoption name="preserve
+case">yes</smbconfoption>, <smbconfoption name="short preserve case">yes</smbconfoption>, and <smbconfoption
+name="case sensitive">no</smbconfoption> in order to maintain capital letters in shortcuts in any of the
+profile folders.
+</para>
+
+<para>
+<indexterm><primary>user.DAT</primary></indexterm>
+<indexterm><primary>user.MAN</primary></indexterm>
+The <filename>user.DAT</filename> file contains all the user's preferences. If you wish to enforce a set of preferences,
+rename their <filename>user.DAT</filename> file to <filename>user.MAN</filename>, and deny them write access to this file.
+</para>
+
+<orderedlist>
+	<listitem> <para>
+	On the Windows 9x/Me machine, go to <guimenu>Control Panel</guimenu> ->
+	<guimenuitem>Passwords</guimenuitem> and select the <guilabel>User Profiles</guilabel> tab.
+	Select the required level of roaming preferences. Press <guibutton>OK</guibutton>, but do not
+	allow the computer to reboot.
+	</para> </listitem>
+
+	<listitem> <para>
+	On the Windows 9x/Me machine, go to <guimenu>Control Panel</guimenu> ->
+	<guimenuitem>Network</guimenuitem> -> <guimenuitem>Client for Microsoft Networks</guimenuitem>
+	-> <guilabel>Preferences</guilabel>. Select <guilabel>Log on to NT Domain</guilabel>.	Then,
+	ensure that the Primary Logon is <guilabel>Client for Microsoft Networks</guilabel>. Press
+	<guibutton>OK</guibutton>, and this time allow the computer to reboot.
+	</para> </listitem>
+</orderedlist>
+
+<para>
+<indexterm><primary>Primary Logon</primary></indexterm>
+<indexterm><primary>Client for Novell Networks</primary></indexterm>
+<indexterm><primary>Novell</primary></indexterm>
+<indexterm><primary>Windows Logon</primary></indexterm>
+Under Windows 9x/Me, profiles are downloaded from the Primary Logon. If you have the Primary Logon
+as <quote>Client for Novell Networks</quote>, then the profiles and logon script will be downloaded from
+your Novell server. If you have the Primary Logon as <quote>Windows Logon</quote>, then the profiles will
+be loaded from the local machine &smbmdash; a bit against the concept of roaming profiles, it would seem! 
+</para>
+
+<para>
+<indexterm><primary>domain logon server</primary></indexterm>
+You will now find that the Microsoft Networks Login box contains <constant>[user, password, domain]</constant> instead
+of just <constant>[user, password]</constant>. Type in the Samba server's domain name (or any other domain known to exist,
+but bear in mind that the user will be authenticated against this domain and profiles downloaded from it
+if that domain logon server supports it), user name and user's password. 
+</para>
+
+<para>
+Once the user has been successfully validated, the Windows 9x/Me machine informs you that
+<computeroutput>The user has not logged on before</computeroutput> and asks <computeroutput>Do you
+wish to save the user's preferences?</computeroutput> Select <guibutton>Yes</guibutton>.
+</para>
+
+<para>
+Once the Windows 9x/Me client comes up with the desktop, you should be able to examine the
+contents of the directory specified in the <smbconfoption name="logon path"/> on
+the Samba server and verify that the <filename>Desktop</filename>, <filename>Start Menu</filename>,
+<filename>Programs</filename>, and <filename>Nethood</filename> folders have been created.
+</para>
+
+<para>
+<indexterm><primary>cached locally</primary></indexterm>
+<indexterm><primary>shortcuts</primary></indexterm>
+<indexterm><primary>profile directory</primary></indexterm>
+These folders will be cached locally on the client and updated when the user logs off (if
+you haven't made them read-only by then). You will find that if the user creates further folders or
+shortcuts, the client will merge the profile contents downloaded with the contents of the profile
+directory already on the local client, taking the newest folders and shortcut from each set.
+</para>
+
+<para>
+<indexterm><primary>local profile</primary></indexterm>
+<indexterm><primary>remote profile</primary></indexterm>
+<indexterm><primary>ownership rights</primary></indexterm>
+<indexterm><primary>profile directory</primary></indexterm>
+If you have made the folders/files read-only on the Samba server, then you will get errors from
+the Windows 9x/Me machine on logon and logout as it attempts to merge the local and remote profile.
+Basically, if you have any errors reported by the Windows 9x/Me machine, check the UNIX file permissions
+and ownership rights on the profile directory contents, on the Samba server.
+</para>
+
+<para>
+<indexterm><primary>windows registry settings</primary></indexterm>
+<indexterm><primary>profile path</primary></indexterm>
+<indexterm><primary>user profiles</primary></indexterm>
+<indexterm><primary>desktop cache</primary></indexterm>
+<indexterm><primary>windows registry settings</primary><secondary>profile path</secondary></indexterm>
+If you have problems creating user profiles, you can reset the user's local desktop cache, as shown below.
+When this user next logs in, the user will be told that he/she is logging in <quote>for the first
+time</quote>.
+</para>
+
+
+<orderedlist>
+	<listitem><para>
+	Instead of logging in under the [user, password, domain] dialog, press <guibutton>escape</guibutton>.
+	</para> </listitem>
+
+	<listitem><para>
+	Run the <command>regedit.exe</command> program, and look in:
+	</para>
+
+	<para>
+	<filename>HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList</filename>
+	</para>
+
+	<para>
+	You will find an entry for each user of ProfilePath. Note the contents of this key
+	(likely to be <filename>c:\windows\profiles\username</filename>), then delete the key
+	<parameter>ProfilePath</parameter> for the required user.
+	</para></listitem>
+
+	<listitem><para>
+	Exit the registry editor.
+	</para></listitem>
+
+	<listitem><para>
+	Search for the user's .PWL password-caching file in the <filename>c:\windows</filename> directory, and delete it.
+	</para></listitem>
+
+	<listitem><para>
+	Log off the Windows 9x/Me client.
+	</para></listitem>
+
+	<listitem><para>
+	Check the contents of the profile path (see <smbconfoption name="logon path"/>
+	described above) and delete the <filename>user.DAT</filename> or <filename>user.MAN</filename>
+	file for the user, making a backup if required. 
+	</para></listitem>
+</orderedlist>
+
+<warning><para>
+<indexterm><primary>ProfilePath</primary></indexterm>
+Before deleting the contents of the directory listed in the <parameter>ProfilePath</parameter>
+(this is likely to be <filename>c:\windows\profiles\username)</filename>, ask whether the owner has
+any important files stored on his or her desktop or start menu. Delete the contents of the
+directory <parameter>ProfilePath</parameter> (making a backup if any of the files are needed).
+</para>
+
+<para>
+This will have the effect of removing the local (read-only hidden system file) <filename>user.DAT</filename>
+in their profile directory, as well as the local <quote>desktop,</quote> <quote>nethood,</quote>
+<quote>start menu,</quote> and <quote>programs</quote> folders.
+</para></warning>
+
+<para>
+<indexterm><primary>log level</primary></indexterm>
+<indexterm><primary>packet sniffer</primary></indexterm>
+<indexterm><primary>ethereal</primary></indexterm>
+<indexterm><primary>netmon.exe</primary></indexterm>
+If all else fails, increase Samba's debug log levels to between 3 and 10, and/or run a packet
+sniffer program such as ethereal or <command>netmon.exe</command>, and look for error messages.
+</para>
+
+<para>
+<indexterm><primary>roaming profiles</primary></indexterm>
+<indexterm><primary>packet trace</primary></indexterm>
+If you have access to an Windows NT4/200x server, then first set up roaming profiles and/or
+netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces
+provided with Windows NT4/200x server, and see what the differences are with the equivalent Samba trace.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Windows NT4 Workstation</title>
+
+<para>
+When a user first logs in to a Windows NT workstation, the profile NTuser.DAT is created. The profile
+location can be now specified through the <smbconfoption name="logon path"/> parameter.
+</para>
+
+<para>
+There is a parameter that is now available for use with NT Profiles: <smbconfoption name="logon drive"/>. 
+This should be set to <filename>H:</filename> or any other drive, and should be used in conjunction with
+the new <smbconfoption name="logon home"/> parameter.
+</para>
+
+<para>
+<indexterm><primary>.PDS extension</primary></indexterm>
+<indexterm><primary>profile path</primary></indexterm>
+The entry for the NT4 profile is a directory, not a file. The NT help on profiles mentions that a
+directory is also created with a .PDS extension. The user, while logging in, must have write permission
+to create the full profile path (and the folder with the .PDS extension for those situations where it
+might be created). 
+</para>
+
+<para>
+<indexterm><primary>NTuser.DAT</primary></indexterm>
+In the profile directory, Windows NT4 creates more folders than Windows 9x/Me. It creates
+<filename>Application Data</filename> and others, as well as <filename>Desktop</filename>,
+<filename>Nethood</filename>, <filename>Start Menu,</filename> and <filename>Programs</filename>.
+The profile itself is stored in a file <filename>NTuser.DAT</filename>. Nothing appears to be stored
+in the .PDS directory, and its purpose is currently unknown.
+</para>
+
+<para>
+<indexterm><primary>NTuser.DAT</primary></indexterm>
+<indexterm><primary>NTuser.MAN</primary></indexterm>
+You can use the <application>System Control Panel</application> to copy a local profile onto
+a Samba server (see NT help on profiles; it is also capable of firing up the correct location in the
+<application>System Control Panel</application> for you). The NT help file also mentions that renaming
+<filename>NTuser.DAT</filename> to <filename>NTuser.MAN</filename> turns a profile into a mandatory one.
+</para>
+
+<para>
+The case of the profile is significant.	The file must be called <filename>NTuser.DAT</filename>
+or, for a mandatory profile, <filename>NTuser.MAN</filename>.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Windows 2000/XP Professional</title>
+
+<para>
+You must first convert the profile from a local profile to a domain profile on the MS Windows
+workstation as follows: </para>
+
+<procedure>
+	<step><para> Log on as the <emphasis>local</emphasis> workstation administrator. </para></step>
+
+	<step><para> Right-click on the <guiicon>My Computer</guiicon> icon, and select
+	<guimenuitem>Properties</guimenuitem>.</para></step>
+
+	<step><para> Click on the <guilabel>User Profiles</guilabel> tab.</para></step>
+
+	<step><para> Select the profile you wish to convert (click it once).</para></step>
+
+	<step><para> Click on the <guibutton>Copy To</guibutton> button.</para></step>
+
+	<step><para> In the <guilabel>Permitted to use</guilabel> box, click on the
+	<guibutton>Change</guibutton> button. </para></step>
+
+	<step><para> Click on the <guilabel>Look in</guilabel> area that lists the machine name. When you click here, it will
+	open up a selection box. Click on the domain to which the profile must be accessible. </para>
+
+	<note><para>You will need to log on if a logon box opens up. 
+	For example, connect as <replaceable>DOMAIN</replaceable>\root, password:
+	<replaceable>mypassword</replaceable>.</para></note> </step>
+
+	<step><para> To make the profile capable of being used by anyone, select <quote>Everyone</quote>. </para></step>
+
+	<step><para> Click on <guibutton>OK</guibutton> and the Selection box will close. </para></step>
+
+	<step><para> Now click on <guibutton>OK</guibutton> to create the profile in the path
+	you nominated.	</para></step>
+</procedure>
+
+<para>
+Done. You now have a profile that can be edited using the Samba <command>profiles</command> tool.
+</para>
+
+<note><para>
+Under Windows NT/200x, the use of mandatory profiles forces the use of MS Exchange storage of mail
+data and keeps it out of the desktop profile. That keeps desktop profiles from becoming unusable.
+</para></note>
+
+<sect4>
+<title>Windows XP Service Pack 1</title>
+	<para>
+	There is a security check new to Windows XP (or maybe only Windows XP service pack 1).
+	It can be disabled via a group policy in the Active Directory. The policy is called:
+<screen>
+Computer Configuration\Administrative Templates\System\User Profiles\
+          Do not check for user ownership of Roaming Profile Folders
+</screen>
+	</para>
+
+	<para>
+	This should be set to <constant>Enabled</constant>.
+	</para>
+
+	<para>
+	Does the new version of Samba have an Active Directory analogue?  If so, then you may be able to set the policy through this.
+	</para>
+
+	<para>If you cannot set group policies in Samba, then you may be able to set the policy locally on
+	each machine. If you want to try this, then do the following:
+	</para>
+
+
+<procedure>
+	<step><para>On the XP workstation, log in with an administrative account.</para></step>
+
+	<step><para>Click on <guimenu>Start</guimenu> -> <guimenuitem>Run</guimenuitem>.</para></step>
+	<step><para>Type <command>mmc</command>.</para></step>
+	<step><para>Click on <guibutton>OK</guibutton>.</para></step>
+	<step><para>A Microsoft Management Console should appear.</para></step>
+	<step><para>Click on <guimenu>File</guimenu> -> <guimenuitem>Add/Remove Snap-in</guimenuitem> -> <guimenuitem>Add</guimenuitem>.</para></step> 
+	<step><para>Double-click on <guiicon>Group Policy</guiicon>.</para></step> 
+	<step><para>Click on <guibutton>Finish</guibutton> -> <guibutton>Close</guibutton>.</para></step> 
+	<step><para>Click on <guibutton>OK</guibutton>.</para></step>
+	<step><para>In the <quote>Console Root</quote> window expand <guiicon>Local Computer Policy</guiicon> ->
+		<guiicon>Computer Configuration</guiicon> -> <guiicon>Administrative Templates</guiicon> -> 
+		<guiicon>System</guiicon> -> <guiicon>User Profiles</guiicon>.</para></step>
+	<step><para>Double-click on <guilabel>Do not check for user ownership of Roaming Profile Folders</guilabel>.</para></step>
+	<step><para>Select <guilabel>Enabled</guilabel>.</para></step>
+	<step><para>Click on <guibutton>OK</guibutton>.</para></step>
+	<step><para>Close the whole console. You do not need to save the settings (this refers to the
+	console settings rather than the policies you have changed).</para></step>
+	<step><para>Reboot.</para></step>
+</procedure>
+</sect4>
+</sect3>
+</sect2>
+
+<sect2>
+<title>User Profile Hive Cleanup Service</title>
+
+<para>
+There are certain situations that cause a cached local copy of roaming profile not to be deleted on exit, even if
+the policy to force such deletion is set. To deal with that situation, a special service was created. The application 
+<command>UPHClean</command> (User Profile Hive Cleanup) can be installed as a service on Windows NT4/2000/XP Professional
+and Windows 2003.
+</para>
+
+<para>
+The UPHClean software package can be downloaded from the User Profile Hive Cleanup
+Service<footnote>http://www.microsoft.com/downloads/details.aspx?FamilyID=1B286E6D-8912-4E18-B570-42470E2F3582&amp;displaylang=en</footnote>
+web site.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</title>
+
+<para>
+<indexterm><primary>profile sharing</primary></indexterm>
+<indexterm><primary>profile contents</primary></indexterm>
+Sharing of desktop profiles between Windows versions is not recommended. Desktop profiles are an
+evolving phenomenon, and profiles for later versions of MS Windows clients add features that may interfere
+with earlier versions of MS Windows clients. Probably the more salient reason to not mix profiles is
+that when logging off an earlier version of MS Windows, the older format of profile contents may overwrite
+information that belongs to the newer version, resulting in loss of profile information content when that
+user logs on again with the newer version of MS Windows.
+</para>
+
+<para>
+If you then want to share the same Start Menu and Desktop with Windows 9x/Me, you must specify a common
+location for the profiles. The &smb.conf; parameters that need to be common are 
+<smbconfoption name="logon path"/> and <smbconfoption name="logon home"/>.
+</para>
+
+<para>
+<indexterm><primary>user.DAT</primary></indexterm>
+<indexterm><primary>NTuser.DAT</primary></indexterm>
+If you have this set up correctly, you will find separate <filename>user.DAT</filename> and
+<filename>NTuser.DAT</filename> files in the same profile directory.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Profile Migration from Windows NT4/200x Server to Samba</title>
+
+<para>
+<indexterm><primary>encrypted passwords</primary></indexterm>
+There is nothing to stop you from specifying any path that you like for the location of users' profiles.
+Therefore, you could specify that the profile be stored on a Samba server or any other SMB server,
+as long as that SMB server supports encrypted passwords.
+</para>
+
+<sect3 id="profilemigrn">
+<title>Windows NT4 Profile Management Tools</title>
+
+<para>
+<indexterm><primary>resource kit</primary></indexterm>
+Unfortunately, the resource kit information is specific to the version of MS Windows NT4/200x. The
+correct resource kit is required for each platform.
+</para>
+
+<para>Here is a quick guide:</para>
+
+<procedure>
+<title>Profile Migration Procedure</title>
+
+	<step><para> On your NT4 domain controller, right-click on <guiicon>My Computer</guiicon>, then select 
+	<guilabel>Properties</guilabel>, then the tab labeled <guilabel>User Profiles</guilabel>. </para></step>
+
+	<step><para> Select a user profile you want to migrate and click on it. </para>
+
+	<note><para>I am using the term <quote>migrate</quote> loosely. You can copy a profile to create a group
+	profile. You can give the user <parameter>Everyone</parameter> rights to the profile you copy this to. That
+	is what you need to do, since your Samba domain is not a member of a trust relationship with your NT4
+	PDC.</para></note></step>
+
+	<step><para>Click on the <guibutton>Copy To</guibutton> button.</para></step>
+
+	<step><para>In the box labeled <guilabel>Copy Profile to</guilabel> add your new path, such as,
+	<filename>c:\temp\foobar</filename></para></step>
+
+	<step><para>Click on <guibutton>Change</guibutton> in the <guilabel>Permitted to use</guilabel> box.</para></step>
+
+	<step><para>Click on the group <quote>Everyone</quote>, click on <guibutton>OK</guibutton>. This
+	closes the <quote>choose user</quote> box.</para></step>
+
+	<step><para>Now click on <guibutton>OK</guibutton>.</para></step>
+</procedure>
+
+<para>
+Follow these steps for every profile you need to migrate.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Side Bar Notes</title>
+
+
+<para>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>info</tertiary></indexterm>
+You should obtain the SID of your NT4 domain. You can use the <command>net rpc info</command> to do this.
+See <link linkend="NetCommand">The Net Command Chapter</link>, <link linkend="netmisc1">Other Miscellaneous Operations</link> for more information.
+</para>
+
+</sect3>
+
+<sect3>
+<title>moveuser.exe</title>
+
+<para>
+<indexterm><primary>moveuser.exe</primary></indexterm>
+The Windows 200x professional resource kit has <command>moveuser.exe</command>.
+<command>moveuser.exe</command> changes the security of a profile from one user to another. This allows the
+account domain to change and/or the username to change.
+</para>
+
+<para>
+This command is like the Samba <command>profiles</command> tool.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Get SID</title>
+
+<para>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>GetSID.exe</primary></indexterm>
+You can identify the SID by using <command>GetSID.exe</command> from the Windows NT Server 4.0 Resource Kit.
+</para>
+
+<para>
+Windows NT 4.0 stores the local profile information in the registry under the following key:
+<filename>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</filename>
+</para>
+
+<para>
+Under the ProfileList key, there will be subkeys named with the SIDs of the users who have logged
+on to this computer. (To find the profile information for the user whose locally cached profile you want
+to move, find the SID for the user with the <command>GetSID.exe</command> utility.) Inside the appropriate user's subkey,
+you will see a string value named <parameter>ProfileImagePath</parameter>.
+</para>
+
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Mandatory Profiles</title>
+
+<para>
+<indexterm><primary>mandatory profiles</primary></indexterm>
+A mandatory profile is a profile that the user does not have the ability to overwrite. During the
+user's session, it may be possible to change the desktop environment; however, as the user logs out, all changes
+made will be lost. If it is desired to not allow the user any ability to change the desktop environment,
+then this must be done through policy settings. See <link linkend="PolicyMgmt">System and Account
+Policies</link>.
+</para>
+
+<note><para> 
+<indexterm><primary>fake-permissions module</primary></indexterm>
+<indexterm><primary>VFS module</primary></indexterm>
+<indexterm><primary>fake_perms</primary></indexterm>
+Under NO circumstances should the profile directory (or its contents) be made read-only because this may
+render the profile unusable.  Where it is essential to make a profile read-only within the UNIX file system,
+this can be done, but then you absolutely must use the <command>fake-permissions</command> VFS module to
+instruct MS Windows NT/200x/XP clients that the Profile has write permission for the user.  See <link
+linkend="fakeperms">fake_perms VFS module</link>.
+</para></note>
+
+<para>
+<indexterm><primary>NTUser.MAN</primary></indexterm>
+<indexterm><primary>NTUser.DAT</primary></indexterm>
+For MS Windows NT4/200x/XP, the procedure shown in <link linkend="profilemigrn">Profile Migration from Windows
+NT4/200x Server to Samba</link> can also be used to create mandatory profiles. To convert a group profile into
+a mandatory profile, simply locate the <filename>NTUser.DAT</filename> file in the copied profile and rename
+it to <filename>NTUser.MAN</filename>.
+</para>
+
+<para>
+<indexterm><primary>User.MAN</primary></indexterm>
+For MS Windows 9x/Me, it is the <filename>User.DAT</filename> file that must be renamed to
+<filename>User.MAN</filename> to effect a mandatory profile.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Creating and Managing Group Profiles</title>
+
+<para>
+<indexterm><primary>group profiles</primary></indexterm>
+<indexterm><primary>template</primary></indexterm>
+<indexterm><primary>profile migration tool</primary></indexterm>
+<indexterm><primary>profile access rights</primary></indexterm>
+Most organizations are arranged into departments. There is a nice benefit in this fact, since usually
+most users in a department require the same desktop applications and the same desktop layout. MS
+Windows NT4/200x/XP will allow the use of group profiles. A group profile is a profile that is created
+first using a template (example) user. Then using the profile migration tool (see above), the profile is
+assigned access rights for the user group that needs to be given access to the group profile.
+</para>
+
+<para>
+<indexterm><primary>User Manager</primary></indexterm>
+The next step is rather important. Instead of assigning a group profile to users (Using User Manager)
+on a <quote>per-user</quote> basis, the group itself is assigned the now modified profile.
+</para>
+
+<note><para>
+Be careful with group profiles. If the user who is a member of a group also has a personal
+profile, then the result will be a fusion (merge) of the two.
+</para></note>
+
+</sect1>
+
+<sect1>
+<title>Default Profile for Windows Users</title>
+
+<para>
+<indexterm><primary>default profile</primary></indexterm>
+<indexterm><primary>registry keys</primary></indexterm>
+MS Windows 9x/Me and NT4/200x/XP will use a default profile for any user for whom a profile
+does not already exist. Armed with a knowledge of where the default profile is located on the Windows
+workstation, and knowing which registry keys affect the path from which the default profile is created,
+it is possible to modify the default profile to one that has been optimized for the site. This has
+significant administrative advantages.
+</para>
+
+<sect2>
+<title>MS Windows 9x/Me</title>
+
+<para>
+<indexterm><primary>System Policy Editor</primary></indexterm>
+<indexterm><primary>registry</primary></indexterm>
+To enable default per-use profiles in Windows 9x/Me, you can either use the <application>Windows
+98 System Policy Editor</application> or change the registry directly.
+</para>
+
+<para>
+To enable default per-user profiles in Windows 9x/Me, launch the <application>System Policy
+Editor</application>, then select <guimenu>File</guimenu> -> <guimenuitem>Open Registry</guimenuitem>.
+Next click on the <guiicon>Local Computer</guiicon> icon, click on <guilabel>Windows 98 System</guilabel>,
+select <guilabel>User Profiles</guilabel>, and click on the enable box. Remember to save the registry
+changes.
+</para>
+
+<para>
+<indexterm><primary>regedit.exe</primary></indexterm>
+To modify the registry directly, launch the <application>Registry Editor</application>
+(<command>regedit.exe</command>) and select the hive <filename>HKEY_LOCAL_MACHINE\Network\Logon</filename>.
+Now add a DWORD type key with the name <quote>User Profiles.</quote> To enable user profiles to set the value
+to 1; to disable user profiles set it to 0.
+</para>
+
+<sect3>
+<title>User Profile Handling with Windows 9x/Me</title>
+
+<para>
+When a user logs on to a Windows 9x/Me machine, the local profile path,
+<filename>HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</filename>, is checked
+for an existing entry for that user.
+</para>
+
+<para>
+If the user has an entry in this registry location, Windows 9x/Me checks for a locally cached
+version of the user profile. Windows 9x/Me also checks the user's home directory (or other specified
+directory if the location has been modified) on the server for the user profile. If a profile exists
+in both locations, the newer of the two is used. If the user profile exists on the server but does not
+exist on the local machine, the profile on the server is downloaded and used. If the user profile only
+exists on the local machine, that copy is used.
+</para>
+
+<para>
+If a user profile is not found in either location, the default user profile from the Windows
+9x/Me machine is used and copied to a newly created folder for the logged on user. At log off, any
+changes that the user made are written to the user's local profile. If the user has a roaming profile,
+the changes are written to the user's profile on the server.
+</para>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>MS Windows NT4 Workstation</title>
+
+<para>
+On MS Windows NT4, the default user profile is obtained from the location
+<filename>%SystemRoot%\Profiles</filename>, which in a default installation will translate to
+<filename>C:\Windows NT\Profiles</filename>. Under this directory on a clean install, there will be three
+directories: <filename>Administrator</filename>, <filename>All
+Users,</filename> and <filename>Default
+User</filename>.
+</para>
+
+<para>
+The <filename>All Users</filename> directory contains menu settings that are common across all
+system users. The <filename>Default User</filename> directory contains menu entries that are customizable
+per user depending on the profile settings chosen/created.
+</para>
+
+<para>
+When a new user first logs onto an MS Windows NT4 machine, a new profile is created from:
+</para>
+
+<itemizedlist>
+	<listitem><para>All Users settings.</para></listitem>
+	<listitem><para>Default User settings (contains the default <filename>NTUser.DAT</filename> file).</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+When a user logs on to an MS Windows NT4 machine that is a member of a Microsoft security domain,
+the following steps are followed for profile handling: 
+</para>
+
+<procedure>
+	<step> <para> The user's account information that is obtained during the logon process
+	contains the location of the user's desktop profile. The profile path may be local to
+	the machine or it may be located on a network share. If there exists a profile at the
+	location of the path from the user account, then this profile is copied to the location
+	<filename>%SystemRoot%\Profiles\%USERNAME%</filename>. This profile then inherits the settings
+	in the <filename>All Users</filename> profile in the <filename>%SystemRoot%\Profiles</filename>
+	location. </para> </step>
+
+	<step> <para> If the user account has a profile path, but at its location a profile does not
+	exist, then a new profile is created in the <filename>%SystemRoot%\Profiles\%USERNAME%</filename>
+	directory from reading the <filename>Default User</filename> profile. </para> </step>
+
+	<step> <para>
+<indexterm><primary>NTConfig.POL</primary></indexterm>
+<indexterm><primary>NETLOGON</primary></indexterm>
+<indexterm><primary>authenticating server</primary></indexterm>
+<indexterm><primary>logon server</primary></indexterm>
+<indexterm><primary>HKEY_CURRENT_USER</primary></indexterm>
+	If the NETLOGON share on the authenticating server (logon server) contains
+	a policy file (<filename>NTConfig.POL</filename>), then its contents are applied to the
+	<filename>NTUser.DAT</filename>, which is applied to the <filename>HKEY_CURRENT_USER</filename>
+	part of the registry. 
+	</para> </step>
+
+	<step> <para> When the user logs out, if the profile is set to be a roaming profile, it will be
+	written out to the location of the profile. The <filename>NTuser.DAT</filename> file is then
+	re-created from the contents of the <filename>HKEY_CURRENT_USER</filename> contents. Thus,
+	should there not exist in the NETLOGON share an <filename>NTConfig.POL</filename> at the next
+	logon, the effect of the previous <filename>NTConfig.POL</filename> will still be held in the
+	profile. The effect of this is known as tattooing.
+	</para> </step>
+</procedure>
+
+<para>
+MS Windows NT4 profiles may be <emphasis>local</emphasis> or <emphasis>roaming</emphasis>. A local
+profile is stored in the <filename>%SystemRoot%\Profiles\%USERNAME%</filename> location. A roaming
+profile will also remain stored in the same way, unless the following registry key is created:
+<screen>
+HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
+winlogon\"DeleteRoamingCache"=dword:0000000
+</screen>
+In this case, the local copy (in <filename>%SystemRoot%\Profiles\%USERNAME%</filename>) will be deleted
+on logout.
+</para>
+
+<para>
+<indexterm><primary>regedt32</primary></indexterm>
+Under MS Windows NT4, default locations for common resources like <filename>My Documents</filename>
+may be redirected to a network share by modifying the following registry keys. These changes may be
+made via use of the System Policy Editor. To do so may require that you create your own template
+extension for the Policy Editor to allow this to be done through the GUI. Another way to do this is by
+first creating a default user profile, then while logged in as that user, running <command>regedt32</command> to edit
+the key settings.
+</para>
+
+<para>
+The Registry Hive key that affects the behavior of folders that are part of the default user
+profile are controlled by entries on Windows NT4 is:
+<screen>
+HKEY_CURRENT_USER
+	\Software
+		\Microsoft
+			\Windows
+				\CurrentVersion
+					\Explorer
+						\User Shell Folders
+</screen>
+<indexterm><primary>windows registry settings</primary><secondary>default profile locations</secondary></indexterm>
+</para>
+
+<para>  The above hive key contains a list of automatically managed
+folders. The default entries are shown in <link linkend="ProfileLocs">the next table</link>.
+</para>
+
+<table frame="all" id="ProfileLocs">
+	<title>User Shell Folder Registry Keys Default Values</title>
+	<tgroup cols="2">
+		<colspec align="left"/>
+		<colspec align="left"/>
+	<thead>
+		<row><entry>Name</entry><entry>Default Value</entry></row>
+	</thead>
+	<tbody>
+		<row><entry>AppData</entry><entry>%USERPROFILE%\Application Data</entry></row>
+		<row><entry>Desktop</entry><entry>%USERPROFILE%\Desktop</entry></row>
+		<row><entry>Favorites</entry><entry>%USERPROFILE%\Favorites</entry></row>
+		<row><entry>NetHood</entry><entry>%USERPROFILE%\NetHood</entry></row>
+		<row><entry>PrintHood</entry><entry>%USERPROFILE%\PrintHood</entry></row>
+		<row><entry>Programs</entry><entry>%USERPROFILE%\Start Menu\Programs</entry></row>
+		<row><entry>Recent</entry><entry>%USERPROFILE%\Recent</entry></row>
+		<row><entry>SendTo</entry><entry>%USERPROFILE%\SendTo</entry></row>
+		<row><entry>Start Menu </entry><entry>%USERPROFILE%\Start Menu</entry></row>
+		<row><entry>Startup</entry><entry>%USERPROFILE%\Start Menu\Programs\Startup</entry></row>
+	</tbody>
+	</tgroup>
+</table>
+
+<para> The registry key that contains the location of the default profile settings is:
+<screen>
+HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\
+User Shell Folders
+</screen>
+</para>
+
+<para>
+The default entries are shown in <link linkend="regkeys">Defaults of Profile Settings Registry Keys</link>.
+</para>
+
+<table frame="all" id="regkeys">
+	<title>Defaults of Profile Settings Registry Keys</title>
+	<tgroup cols="2">
+		<colspec align="left"/>
+		<colspec align="left"/>
+	<tbody>
+		<row><entry>Common Desktop</entry><entry>%SystemRoot%\Profiles\All Users\Desktop</entry></row>
+		<row><entry>Common Programs</entry><entry>%SystemRoot%\Profiles\All Users\Programs</entry></row>
+		<row><entry>Common Start Menu</entry><entry>%SystemRoot%\Profiles\All Users\Start Menu</entry></row>
+		<row><entry>Common Startup</entry><entry>%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup</entry></row>
+	</tbody>
+	</tgroup>
+</table>
+
+</sect2>
+
+<sect2>
+<title>MS Windows 200x/XP</title>
+
+<note><para>
+<indexterm><primary>GPOs</primary></indexterm>
+<indexterm><primary>Windows XP Home Edition</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>domain security</primary></indexterm>
+MS Windows XP Home Edition does use default per-user profiles, but cannot participate
+in domain security, cannot log onto an NT/ADS-style domain, and thus can obtain the profile only
+from itself. While there are benefits in doing this, the beauty of those MS Windows clients that
+can participate in domain logon processes is that they allow the administrator to create a global default
+profile and enforce it through the use of Group Policy Objects (GPOs).
+</para></note>
+
+<para>
+<indexterm><primary>Default User</primary></indexterm>
+When a new user first logs onto an MS Windows 200x/XP machine, the default profile is obtained from
+<filename>C:\Documents and Settings\Default User</filename>. The administrator can modify or change the
+contents of this location, and MS Windows 200x/XP will gladly use it. This is far from the optimum arrangement,
+since it will involve copying a new default profile to every MS Windows 200x/XP client workstation.
+</para>
+
+<para>
+<indexterm><primary>NETLOGON</primary></indexterm>
+When MS Windows 200x/XP participates in a domain security context, and if the default user profile is not
+found, then the client will search for a default profile in the NETLOGON share of the authenticating server.
+In MS Windows parlance, it is <filename>%LOGONSERVER%\NETLOGON\Default User,</filename>
+and if one exists there, it will copy this to the workstation in the <filename>C:\Documents and
+Settings\</filename> under the Windows login name of the use.
+</para>
+
+<note> <para> This path translates, in Samba parlance, to the &smb.conf;
+<smbconfsection name="[NETLOGON]"/> share. The directory should be created at the root
+of this share and must be called <filename>Default User</filename>.
+</para> </note>
+
+<para> If a default profile does not exist in this location, then MS Windows 200x/XP will use the local
+default profile. </para>
+
+<para> On logging out, the user's desktop profile is stored to the location specified in the registry
+settings that pertain to the user. If no specific policies have been created or passed to the client
+during the login process (as Samba does automatically), then the user's profile is written to the
+local machine only under the path <filename>C:\Documents and Settings\%USERNAME%</filename>. </para>
+
+<para> Those wishing to modify the default behavior can do so through these three methods: </para>
+
+<itemizedlist>
+	<listitem> <para> Modify the registry keys on the local machine manually and place the new
+	default profile in the NETLOGON share root. This is not recommended because it is maintenance intensive.
+	</para> </listitem>
+
+	<listitem> <para> Create an NT4-style NTConfig.POL file that specifies this behavior and locate
+	this file in the root of the NETLOGON share along with the new default profile. </para> </listitem>
+
+	<listitem> <para> Create a GPO that enforces this through Active Directory, and place the new
+	default profile in the NETLOGON share.	</para> </listitem>
+</itemizedlist>
+
+<para>The registry hive key that affects the behavior of folders that are part of the default user
+profile are controlled by entries on Windows 200x/XP is: </para>
+
+<para> <filename>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell
+Folders\</filename> </para>
+
+<para>
+This hive key contains a list of automatically managed folders. The default entries are shown
+in <link linkend="defregpthkeys">the next table</link>
+<indexterm><primary>windows registry settings</primary><secondary>default profile locations</secondary></indexterm>
+</para>
+
+
+<table frame="all" id="defregpthkeys">
+	<title>Defaults of Default User Profile Paths Registry Keys</title>
+	<tgroup cols="2">
+		<colspec align="left"/>
+		<colspec align="left"/>
+	<thead>
+		<row><entry>Name</entry><entry>Default Value</entry></row>
+	</thead>
+	<tbody>
+		<row><entry>AppData</entry><entry>%USERPROFILE%\Application Data</entry></row>
+		<row><entry>Cache</entry><entry>%USERPROFILE%\Local Settings\Temporary Internet Files</entry></row>
+		<row><entry>Cookies</entry><entry>%USERPROFILE%\Cookies</entry></row>
+		<row><entry>Desktop</entry><entry>%USERPROFILE%\Desktop</entry></row>
+		<row><entry>Favorites</entry><entry>%USERPROFILE%\Favorites</entry></row>
+		<row><entry>History</entry><entry>%USERPROFILE%\Local Settings\History</entry></row>
+		<row><entry>Local AppData</entry><entry>%USERPROFILE%\Local Settings\Application Data</entry></row>
+		<row><entry>Local Settings</entry><entry>%USERPROFILE%\Local Settings</entry></row>
+		<row><entry>My Pictures</entry><entry>%USERPROFILE%\My Documents\My Pictures</entry></row>
+		<row><entry>NetHood</entry><entry>%USERPROFILE%\NetHood</entry></row>
+		<row><entry>Personal</entry><entry>%USERPROFILE%\My Documents</entry></row>
+		<row><entry>PrintHood</entry><entry>%USERPROFILE%\PrintHood</entry></row>
+		<row><entry>Programs</entry><entry>%USERPROFILE%\Start Menu\Programs</entry></row>
+		<row><entry>Recent</entry><entry>%USERPROFILE%\Recent</entry></row>
+		<row><entry>SendTo</entry><entry>%USERPROFILE%\SendTo</entry></row>
+		<row><entry>Start Menu</entry><entry>%USERPROFILE%\Start Menu</entry></row>
+		<row><entry>Startup</entry><entry>%USERPROFILE%\Start Menu\Programs\Startup</entry></row>
+		<row><entry>Templates</entry><entry>%USERPROFILE%\Templates</entry></row>
+	</tbody>
+	</tgroup>
+</table>
+
+<para> There is also an entry called <quote>Default</quote> that has no value set. The default entry is
+of type <constant>REG_SZ</constant>; all the others are of type <constant>REG_EXPAND_SZ</constant>. </para>
+
+<para> It makes a huge difference to the speed of handling roaming user profiles if all the folders are
+stored on a dedicated location on a network server. This means that it will not be necessary to write
+the Outlook PST file over the network for every login and logout. </para>
+
+<para>
+To set this to a network location, you could use the following examples:
+<screen>
+%LOGONSERVER%\%USERNAME%\Default Folders
+</screen>
+This stores the folders in the user's home directory under a directory called <filename>Default
+Folders</filename>. You could also use:
+<screen>
+\\<replaceable>SambaServer</replaceable>\<replaceable>FolderShare</replaceable>\%USERNAME%
+</screen>
+</para>
+
+<para>
+in which case the default folders are stored in the server named <replaceable>SambaServer</replaceable>
+in the share called <replaceable>FolderShare</replaceable> under a directory that has the name of the
+MS Windows user as seen by the Linux/UNIX file system.	</para>
+
+<para> Please note that once you have created a default profile share, you <emphasis>must</emphasis> migrate a user's profile
+(default or custom) to it. </para>
+
+<para> MS Windows 200x/XP profiles may be <emphasis>local</emphasis> or <emphasis>roaming</emphasis>.
+	A roaming profile is cached locally unless the following registry key is created: 
+
+<indexterm><primary>delete roaming profiles</primary></indexterm>
+</para>
+
+
+<para> <programlisting> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
+	winlogon\"DeleteRoamingCache"=dword:00000001</programlisting></para>
+
+<para>
+In this case, the local cache copy is deleted on logout.
+</para> 
+</sect2> 
+</sect1>
+
+<sect1> <title>Common Errors</title>
+
+<para>
+The following are some typical errors, problems, and questions that have been asked on the Samba mailing lists.
+</para>
+
+<sect2>
+<title>Configuring Roaming Profiles for a Few Users or Groups</title>
+
+<para>
+With Samba-2.2.x, the choice you have is to enable or disable roaming profiles support. It is a
+global-only setting. The default is to have roaming profiles, and the default path will locate them in
+the user's home directory.
+</para>
+
+<para>
+If disabled globally, then no one will have roaming profile ability. If enabled and you want it
+to apply only to certain machines, then on those machines on which roaming profile support is not wanted,
+it is necessary to disable roaming profile handling in the registry of each such machine.
+</para>
+
+<para>
+With Samba-3, you can have a global profile setting in &smb.conf;, and you can override this by
+per-user settings using the Domain User Manager (as with MS Windows NT4/200x). </para>
+
+<para> In any case, you can configure only one profile per user. That profile can be either: </para>
+
+<itemizedlist>
+	<listitem><para>A profile unique to that user.</para></listitem>
+	<listitem><para>A mandatory profile (one the user cannot change).</para></listitem>
+	<listitem><para>A group profile (really should be mandatory &smbmdash; that is, unchangable).</para></listitem>
+</itemizedlist>
+
+</sect2>
+
+<sect2> <title>Cannot Use Roaming Profiles</title>
+
+<para> A user requested the following: <quote> I do not want roaming profiles to be implemented. I want
+to give users a local profile alone. I am totally lost with this error. For the past
+two days I tried everything, I googled around but found no useful pointers. Please help me. </quote></para>
+
+<para> The choices are: </para>
+
+<variablelist>
+	<varlistentry>
+		<term>Local profiles</term> <listitem><para> I know of no registry keys that will allow
+		autodeletion of LOCAL profiles on log out.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Roaming profiles</term> <listitem><para> As a user logs onto the network, a centrally
+		stored profile is copied to the workstation to form a local profile. This local profile
+		will persist (remain on the workstation disk) unless a registry key is changed that will
+		cause this profile to be automatically deleted on logout. </para></listitem>
+	</varlistentry>
+</variablelist>
+
+<para>The roaming profile choices are: </para>
+
+<variablelist>
+	<varlistentry>
+		<term>Personal roaming profiles</term> <listitem><para> These are typically stored in
+		a profile share on a central (or conveniently located local) server. </para>
+
+		<para> Workstations cache (store) a local copy of the profile. This cached
+		copy is used when the profile cannot be downloaded at next logon. </para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Group profiles</term> <listitem><para>These are loaded from a central profile
+		server.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>Mandatory profiles</term> <listitem><para> Mandatory profiles can be created for
+		a user as well as for any group that a user is a member of. Mandatory profiles cannot be
+		changed by ordinary users. Only the administrator can change or reconfigure a mandatory
+		profile. </para></listitem>
+	</varlistentry>
+</variablelist>
+
+<para> A Windows NT4/200x/XP profile can vary in size from 130KB to very large. Outlook PST files are
+most often part of the profile and can be many gigabytes in size. On average (in a well controlled environment),
+roaming profile size of 2MB is a good rule of thumb to use for planning purposes. In an undisciplined
+environment, I have seen up to 2GB profiles. Users tend to complain when it takes an hour to log onto a
+workstation, but they harvest the fruits of folly (and ignorance). </para>
+
+<para> The point of this discussion is to show that roaming profiles and good controls of how they can be
+changed as well as good discipline make for a problem-free site. </para>
+
+<para> Microsoft's answer to the PST problem is to store all email in an MS Exchange Server backend. This
+removes the need for a PST file. </para>
+
+<para>Local profiles mean: </para>
+
+<itemizedlist>
+	<listitem><para>If each machine is used by many users, then much local disk storage is needed
+	for local profiles.</para></listitem> <listitem><para>Every workstation the user logs into has
+	its own profile; these can be very different from machine to machine.</para></listitem>
+</itemizedlist>
+
+<para> On the other hand, use of roaming profiles means: </para>
+
+<itemizedlist>
+	<listitem><para>The network administrator can control the desktop environment of all users.</para></listitem>
+	<listitem><para>Use of mandatory profiles drastically reduces network management overheads.</para></listitem>
+	<listitem><para>In the long run, users will experience fewer problems.</para></listitem>
+</itemizedlist>
+
+</sect2>
+
+<sect2>
+<title>Changing the Default Profile</title>
+
+<para><quote>When the client logs onto the domain controller, it searches
+for a profile to download. Where do I put this default profile?</quote></para>
+
+<para>
+<indexterm><primary>default profile</primary></indexterm>
+First, the Samba server needs to be configured as a domain controller. This can be done by
+setting in &smb.conf;: </para>
+
+<smbconfblock>
+<smbconfoption name="security">user</smbconfoption>
+<smbconfoption name="os level">32 (or more)</smbconfoption>
+<smbconfoption name="domain logons">Yes</smbconfoption>
+</smbconfblock>
+
+<para> There must be a <smbconfsection name="[netlogon]"/> share that is world readable. It is
+a good idea to add a logon script to preset printer and drive connections. There is also a facility
+for automatically synchronizing the workstation time clock with that of the logon server (another good
+thing to do). </para>
+
+<note><para> To invoke autodeletion of roaming profiles from the local workstation cache (disk storage), use
+the <application>Group Policy Editor</application> to create a file called <filename>NTConfig.POL</filename>
+with the appropriate entries. This file needs to be located in the <smbconfsection name="netlogon"/>
+share root directory.</para></note>
+
+<para> Windows clients need to be members of the domain. Workgroup machines do not use network logons,
+so they do not interoperate with domain profiles. </para>
+
+<para> For roaming profiles, add to &smb.conf;: </para>
+
+<smbconfblock>
+<smbconfoption name="logon path">\\%N\profiles\%U</smbconfoption>
+<smbconfcomment>Default logon drive is Z:</smbconfcomment>
+<smbconfoption name="logon drive">H:</smbconfoption>
+<smbconfcomment>This requires a PROFILES share that is world writable.</smbconfcomment>
+</smbconfblock>
+
+</sect2>
+
+<sect2>
+<title>Debugging Roaming Profiles and NT4-style Domain Policies</title>
+
+<para>
+Roaming profiles and domain policies are implemented via <command>USERENV.DLL</command>. 
+Microsoft Knowledge Base articles <ulink
+url="http://support.microsoft.com/default.aspx?scid=kb;en-us;221833">221833</ulink> and 
+<ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;154120">154120</ulink>
+ describe how to instruct that DLL to debug the login process.
+</para>
+
+</sect2>
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-RightsAndPriviliges.xml b/docs-xml/Samba3-HOWTO/TOSHARG-RightsAndPriviliges.xml
new file mode 100644
index 00000000000..5ce64ddffdf
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-RightsAndPriviliges.xml
@@ -0,0 +1,600 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="rights">
+<chapterinfo>
+        &author.jerry;
+        &author.jht;
+</chapterinfo>
+
+<title>User Rights and Privileges</title>
+
+<para>
+<indexterm><primary>Windows user</primary></indexterm>
+<indexterm><primary>Windows group</primary></indexterm>
+<indexterm><primary>machine accounts</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+The administration of Windows user, group, and machine accounts in the Samba
+domain-controlled network necessitates interfacing between the MS Windows
+networking environment and the UNIX operating system environment. The right
+(permission) to add machines to the Windows security domain can be assigned
+(set) to non-administrative users both in Windows NT4 domains and
+Active Directory domains.
+</para>
+
+<para>
+<indexterm><primary>Windows NT4/2kX/XPPro</primary></indexterm>
+<indexterm><primary>machine account</primary></indexterm>
+<indexterm><primary>trusted</primary></indexterm>
+<indexterm><primary>user logons</primary></indexterm>
+The addition of Windows NT4/2kX/XPPro machines to the domain necessitates the
+creation of a machine account for each machine added. The machine account is
+a necessity that is used to validate that the machine can be trusted to permit
+user logons.
+</para>
+
+<para>
+<indexterm><primary>user accounts</primary></indexterm>
+<indexterm><primary>special account</primary></indexterm>
+<indexterm><primary>account name</primary></indexterm>
+<indexterm><primary>/bin/false</primary></indexterm>
+<indexterm><primary>/dev/null</primary></indexterm>
+<indexterm><primary>man-in-the-middle</primary></indexterm>
+Machine accounts are analogous to user accounts, and thus in implementing them on a UNIX machine that is
+hosting Samba (i.e., on which Samba is running), it is necessary to create a special type of user account.
+Machine accounts differ from  normal user accounts in that the account name (login ID) is terminated with a
+<literal>$</literal> sign. An additional difference is that this type of account should not ever be able to
+log into the UNIX environment as a system user and therefore is set to have a shell of
+<command>/bin/false</command> and a home directory of <command>/dev/null.</command> The machine
+account is used only to authenticate domain member machines during start-up. This security measure
+is designed to block man-in-the-middle attempts to violate network integrity.
+</para>
+
+<note><para>
+<indexterm><primary>computer accounts</primary></indexterm>
+<indexterm><primary>domain member servers</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>credentials</primary></indexterm>
+<indexterm><primary>secure authentication</primary></indexterm>
+Machine (computer) accounts are used in the Windows NT OS family to store security
+credentials for domain member servers and workstations. When the domain member
+starts up, it goes through a validation process that includes an exchange of
+credentials with a domain controller. If the domain member fails to authenticate
+using the credentials known for it by domain controllers, the machine will be refused
+all access by domain users. The computer account is essential to the way that MS 
+Windows secures authentication.
+</para></note>
+
+<para>
+<indexterm><primary>UNIX system accounts</primary></indexterm>
+<indexterm><primary>system administrator</primary></indexterm>
+<indexterm><primary>root</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+The creation of UNIX system accounts has traditionally been the sole right of
+the system administrator, better known as the <constant>root</constant> account.
+It is possible in the UNIX environment to create multiple users who have the
+same UID. Any UNIX user who has a UID=0 is inherently the same as the
+<constant>root</constant> account user.
+</para>
+
+<para>
+<indexterm><primary>system interface scripts</primary></indexterm>
+<indexterm><primary>CIFS function calls</primary></indexterm>
+<indexterm><primary>root account</primary></indexterm>
+<indexterm><primary>UNIX host system</primary></indexterm>
+All versions of Samba call system interface scripts that permit CIFS function
+calls that are used to manage users, groups, and machine accounts
+in the UNIX environment. All versions of Samba up to and including version 3.0.10
+required the use of a Windows administrator account that unambiguously maps to
+the UNIX <constant>root</constant> account to permit the execution of these
+interface scripts. The requirement to do this has understandably met with some
+disdain and consternation among Samba administrators, particularly where it became
+necessary to permit people who should not possess <constant>root</constant>-level
+access to the UNIX host system.
+</para>
+
+<sect1>
+<title>Rights Management Capabilities</title>
+
+<para>
+<indexterm><primary>Windows privilege model</primary></indexterm>
+<indexterm><primary>privilege model</primary></indexterm>
+<indexterm><primary>rights assigned</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+Samba 3.0.11 introduced support for the Windows privilege model.  This model
+allows certain rights to be assigned to a user or group SID.  In order to enable
+this feature, <smbconfoption name="enable privileges">yes</smbconfoption>
+must be defined in the <smbconfsection name="global"/> section of the &smb.conf; file.
+</para>
+
+<para>
+<indexterm><primary>rights</primary></indexterm>
+<indexterm><primary>privileges</primary></indexterm>
+<indexterm><primary>manage privileges</primary></indexterm>
+Currently, the rights supported in Samba-3 are listed in <link linkend="rp-privs"/>.
+The remainder of this chapter explains how to manage and use these privileges on Samba servers.
+</para>
+
+<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
+<indexterm><primary>SePrintOperatorPrivilege</primary></indexterm>
+<indexterm><primary>SeAddUsersPrivilege</primary></indexterm>
+<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
+<indexterm><primary>SeDiskOperatorPrivilege</primary></indexterm>
+<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
+<table id="rp-privs">
+        <title>Current Privilege Capabilities</title>
+        <tgroup cols="2">
+                <colspec align="right"/>
+                <colspec align="left"/>
+                <thead>
+                        <row>
+                                <entry align="left">Privilege</entry>
+                                <entry align="left">Description</entry>
+                        </row>
+                </thead>
+                <tbody>
+                        <row>
+                                <entry><para>SeMachineAccountPrivilege</para></entry>
+                                <entry><para>Add machines to domain</para></entry>
+                        </row>
+                        <row>
+                                <entry><para>SePrintOperatorPrivilege</para></entry>
+                                <entry><para>Manage printers</para></entry>
+                        </row>
+                        <row>
+                                <entry><para>SeAddUsersPrivilege</para></entry>
+                                <entry><para>Add users and groups to the domain</para></entry>
+                        </row>
+                        <row>
+                                <entry><para>SeRemoteShutdownPrivilege</para></entry>
+                                <entry><para>Force shutdown from a remote system</para></entry>
+                        </row>
+                        <row>
+                                <entry><para>SeDiskOperatorPrivilege</para></entry>
+                                <entry><para>Manage disk share</para></entry>
+                        </row>
+<!-- These are not used at this time - so void them from the docs.
+                        <row>
+                                <entry><para>SeBackupPrivilege</para></entry>
+                                <entry><para>Back up files and directories</para></entry>
+                        </row>
+                        <row>
+                                <entry><para>SeRestorePrivilege</para></entry>
+                                <entry><para>Restore files and directories</para></entry>
+                        </row>
+**** End of commented out section **** -->    
+                        <row>
+                                <entry><para>SeTakeOwnershipPrivilege</para></entry>
+                                <entry><para>Take ownership of files or other objects</para></entry>
+                        </row>
+            </tbody>
+        </tgroup>
+</table>
+
+<sect2>
+<title>Using the <quote>net rpc rights</quote> Utility</title>
+
+<para>
+<indexterm><primary>managing rights</primary></indexterm>
+<indexterm><primary>rights assigned</primary></indexterm>
+<indexterm><primary>NT4 User Manager for Domains</primary></indexterm>
+<indexterm><primary>command-line utility</primary></indexterm>
+<indexterm><primary>administrative actions</primary></indexterm>
+There are two primary means of managing the rights assigned to users and groups
+on a Samba server.  The <command>NT4 User Manager for Domains</command> may be
+used from any Windows NT4, 2000, or XP Professional domain member client to
+connect to a Samba domain controller and view/modify the rights assignments.
+This application, however, appears to have bugs when run on a client running
+Windows 2000 or later; therefore, Samba provides a command-line utility for
+performing the necessary administrative actions.
+</para>
+
+<para>
+The <command>net rpc rights</command> utility in Samba 3.0.11 has three new subcommands:
+</para>
+
+<variablelist>
+	<varlistentry><term>list [name|accounts]</term>
+		<listitem><para>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>list</tertiary></indexterm>
+<indexterm><primary>available rights</primary></indexterm>
+<indexterm><primary>privileges assigned</primary></indexterm>
+<indexterm><primary>privileged accounts</primary></indexterm>
+		When called with no arguments, <command>net rpc list</command>
+		simply lists the available rights on the server.  When passed
+		a specific user or group name, the tool lists the privileges
+		currently assigned to the specified account.  When invoked using
+		the special string <constant>accounts</constant>,
+		<command>net rpc rights list</command> returns a list of all
+		privileged accounts on the server and the assigned rights.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>grant &lt;user&gt; &lt;right [right ...]&gt;</term>
+		<listitem><para>
+<indexterm><primary>assign rights</primary></indexterm>
+<indexterm><primary>grant rights</primary></indexterm>
+<indexterm><primary>add client machines</primary></indexterm>
+<indexterm><primary>user or group</primary></indexterm>
+		When called with no arguments, this function is used to assign
+		a list of rights to a specified user or group.  For example,
+		to grant the members of the Domain Admins group on a Samba domain controller,
+		the capability to add client machines to the domain, one would run:
+<screen>
+&rootprompt; net -S server -U domadmin rpc rights grant \
+	 'DOMAIN\Domain Admins' SeMachineAccountPrivilege
+</screen>
+		The following syntax has the same result:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>rights grant</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc rights grant 'DOMAIN\Domain Admins' \
+     SeMachineAccountPrivilege -S server -U domadmin
+</screen>
+		More than one privilege can be assigned by specifying a
+		list of rights separated by spaces. The parameter 'Domain\Domain Admins'
+		must be quoted with single ticks or using double-quotes to prevent
+		the backslash and the space from being interpreted by the system shell.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>revoke &lt;user&gt; &lt;right [right ...]&gt;</term>
+		<listitem><para>
+		This command is similar in format to <command>net rpc rights grant</command>.  Its
+		effect is to remove an assigned right (or list of rights) from a user or group.
+		</para></listitem>
+	</varlistentry>
+
+</variablelist>
+
+<note><para>
+<indexterm><primary>member</primary></indexterm>
+<indexterm><primary>Domain Admins</primary></indexterm>
+<indexterm><primary>revoke privileges</primary></indexterm>
+You must be connected as a member of the Domain Admins group to be able to grant or revoke privileges assigned
+to an account.  This capability is inherent to the Domain Admins group and is not configurable. There are no
+default rights and privileges, except the ability for a member of the Domain Admins group to assign them.
+This means that all administrative rights and privileges (other than the ability to assign them) must be 
+explicitly assigned, even for the Domain Admins group.
+</para></note>
+
+<para>
+<indexterm><primary>performed as root</primary></indexterm>
+<indexterm><primary>necessary rights</primary></indexterm>
+<indexterm><primary>add machine script</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+By default, no privileges are initially assigned to any account because certain actions will be performed as
+root once smbd determines that a user has the necessary rights.  For example, when joining a client to a
+Windows domain, <parameter>add machine script</parameter> must be executed with superuser rights in most 
+cases.  For this reason, you should be very careful about handing out privileges to accounts.
+</para>
+
+<para>
+<indexterm><primary>Access</primary></indexterm>
+<indexterm><primary>root user</primary></indexterm>
+<indexterm><primary>bypasses privilege</primary></indexterm>
+Access as the root user (UID=0) bypasses all privilege checks.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Description of Privileges</title>
+
+<para>
+<indexterm><primary>privileges</primary></indexterm>
+<indexterm><primary>additional privileges</primary></indexterm>
+<indexterm><primary>house-keeping</primary></indexterm>
+The privileges that have been implemented in Samba-3.0.11 are shown below.  It is possible, and likely, that
+additional privileges may be implemented in later releases of Samba. It is also likely that any privileges
+currently implemented but not used may be removed from future releases as a housekeeping matter, so it is
+important that the successful as well as unsuccessful use of these facilities should be reported on the Samba
+mailing lists.
+</para>
+
+<variablelist>
+	<varlistentry><term>SeAddUsersPrivilege</term>
+		<listitem><para>
+<indexterm><primary>SeAddUsersPrivilege</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>net rpc user add</primary></indexterm>
+		This right determines whether or not smbd will allow the
+		user to create new user or group accounts via such tools
+		as <command>net rpc user add</command> or 
+		<command>NT4 User Manager for Domains.</command>
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>SeDiskOperatorPrivilege</term>
+		<listitem><para>
+<indexterm><primary>SeDiskOperatorPrivilege</primary></indexterm>
+<indexterm><primary>add/delete/change share</primary></indexterm>
+<indexterm><primary>ACL</primary></indexterm>
+		Accounts that possess this right will be able to execute
+		scripts defined by the <command>add/delete/change</command>
+		share command in &smb.conf; file as root.  Such users will
+		also be able to modify the ACL associated with file shares
+		on the Samba server.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>SeMachineAccountPrivilege</term>
+		<listitem><para>
+<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
+<indexterm><primary>right to join domain</primary></indexterm>
+<indexterm><primary>join client</primary></indexterm>
+		This right controls whether or not the user can join client
+		machines to a Samba-controlled domain.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>SePrintOperatorPrivilege</term>
+		<listitem><para>
+<indexterm><primary>SePrintOperatorPrivilege</primary></indexterm>
+<indexterm><primary>privilege</primary></indexterm>
+<indexterm><primary>global right</primary></indexterm>
+<indexterm><primary>administrative rights</primary></indexterm>
+<indexterm><primary>printers admin</primary></indexterm>
+		This privilege operates identically to the <smbconfoption name="printer admin"/>
+		option in the &smb.conf; file (see section 5 man page for &smb.conf;)
+		except that it is a global right (not on a per-printer basis). 
+		Eventually the smb.conf option will be deprecated and administrative
+		rights to printers will be controlled exclusively by this right and
+		the security descriptor associated with the printer object in the
+		<filename>ntprinters.tdb</filename> file.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>SeRemoteShutdownPrivilege</term>
+		<listitem><para>
+<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
+<indexterm><primary>rebooting server</primary></indexterm>
+<indexterm><primary>aborting shutdown</primary></indexterm>
+		Samba provides two hooks for shutting down or rebooting
+		the server and for aborting a previously issued shutdown
+		command.  Since this is an operation normally limited by
+		the operating system to the root user, an account must possess this
+		right to be able to execute either of these hooks.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>SeTakeOwnershipPrivilege</term>
+		<listitem><para>
+<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
+<indexterm><primary>take ownership</primary></indexterm>
+		This right permits users to take ownership of files and directories.
+		</para></listitem>
+	</varlistentry>
+
+</variablelist>
+
+</sect2>
+
+<sect2>
+<title>Privileges Suppored by Windows 2000 Domain Controllers</title>
+
+<para>
+    For reference purposes, a Windows NT4 Primary Domain Controller reports support for the following
+	privileges:
+<indexterm><primary>SeCreateTokenPrivilege</primary></indexterm>
+<indexterm><primary>SeAssignPrimaryTokenPrivilege</primary></indexterm>
+<indexterm><primary>SeLockMemoryPrivilege</primary></indexterm>
+<indexterm><primary>SeIncreaseQuotaPrivilege</primary></indexterm>
+<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
+<indexterm><primary>SeTcbPrivilege</primary></indexterm>
+<indexterm><primary>SeSecurityPrivilege</primary></indexterm>
+<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
+<indexterm><primary>SeLoadDriverPrivilege</primary></indexterm>
+<indexterm><primary>SeSystemProfilePrivilege</primary></indexterm>
+<indexterm><primary>SeSystemtimePrivilege</primary></indexterm>
+<indexterm><primary>SeProfileSingleProcessPrivilege</primary></indexterm>
+<indexterm><primary>SeIncreaseBasePriorityPrivilege</primary></indexterm>
+<indexterm><primary>SeCreatePagefilePrivilege</primary></indexterm>
+<indexterm><primary>SeCreatePermanentPrivilege</primary></indexterm>
+<indexterm><primary>SeBackupPrivilege</primary></indexterm>
+<indexterm><primary>SeRestorePrivilege</primary></indexterm>
+<indexterm><primary>SeShutdownPrivilege</primary></indexterm>
+<indexterm><primary>SeDebugPrivilege</primary></indexterm>
+<indexterm><primary>SeAuditPrivilege</primary></indexterm>
+<indexterm><primary>SeSystemEnvironmentPrivilege</primary></indexterm>
+<indexterm><primary>SeChangeNotifyPrivilege</primary></indexterm>
+<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
+<screen>
+         SeCreateTokenPrivilege  Create a token object
+  SeAssignPrimaryTokenPrivilege  Replace a process level token
+          SeLockMemoryPrivilege  Lock pages in memory
+       SeIncreaseQuotaPrivilege  Increase quotas
+      SeMachineAccountPrivilege  Add workstations to domain
+                 SeTcbPrivilege  Act as part of the operating system
+            SeSecurityPrivilege  Manage auditing and security log
+       SeTakeOwnershipPrivilege  Take ownership of files or other objects
+          SeLoadDriverPrivilege  Load and unload device drivers
+       SeSystemProfilePrivilege  Profile system performance
+          SeSystemtimePrivilege  Change the system time
+SeProfileSingleProcessPrivilege  Profile single process
+SeIncreaseBasePriorityPrivilege  Increase scheduling priority
+      SeCreatePagefilePrivilege  Create a pagefile
+     SeCreatePermanentPrivilege  Create permanent shared objects
+              SeBackupPrivilege  Back up files and directories
+             SeRestorePrivilege  Restore files and directories
+            SeShutdownPrivilege  Shut down the system
+               SeDebugPrivilege  Debug programs
+               SeAuditPrivilege  Generate security audits
+   SeSystemEnvironmentPrivilege  Modify firmware environment values
+        SeChangeNotifyPrivilege  Bypass traverse checking
+      SeRemoteShutdownPrivilege  Force shutdown from a remote system
+</screen>
+	And Windows 200x/XP Domain Controllers and workstations reports to support the following privileges:
+<indexterm><primary>SeCreateTokenPrivilege</primary></indexterm>
+<indexterm><primary>SeAssignPrimaryTokenPrivilege</primary></indexterm>
+<indexterm><primary>SeLockMemoryPrivilege</primary></indexterm>
+<indexterm><primary>SeIncreaseQuotaPrivilege</primary></indexterm>
+<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
+<indexterm><primary>SeTcbPrivilege</primary></indexterm>
+<indexterm><primary>SeSecurityPrivilege</primary></indexterm>
+<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
+<indexterm><primary>SeLoadDriverPrivilege</primary></indexterm>
+<indexterm><primary>SeSystemProfilePrivilege</primary></indexterm>
+<indexterm><primary>SeSystemtimePrivilege</primary></indexterm>
+<indexterm><primary>SeProfileSingleProcessPrivilege</primary></indexterm>
+<indexterm><primary>SeIncreaseBasePriorityPrivilege</primary></indexterm>
+<indexterm><primary>SeCreatePagefilePrivilege</primary></indexterm>
+<indexterm><primary>SeCreatePermanentPrivilege</primary></indexterm>
+<indexterm><primary>SeBackupPrivilege</primary></indexterm>
+<indexterm><primary>SeRestorePrivilege</primary></indexterm>
+<indexterm><primary>SeShutdownPrivilege</primary></indexterm>
+<indexterm><primary>SeDebugPrivilege</primary></indexterm>
+<indexterm><primary>SeAuditPrivilege</primary></indexterm>
+<indexterm><primary>SeSystemEnvironmentPrivilege</primary></indexterm>
+<indexterm><primary>SeChangeNotifyPrivilege</primary></indexterm>
+<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
+<indexterm><primary>SeUndockPrivilege</primary></indexterm>
+<indexterm><primary>SeSyncAgentPrivilege</primary></indexterm>
+<indexterm><primary>SeEnableDelegationPrivilege</primary></indexterm>
+<indexterm><primary>SeManageVolumePrivilege</primary></indexterm>
+<indexterm><primary>SeImpersonatePrivilege</primary></indexterm>
+<indexterm><primary>SeCreateGlobalPrivilege</primary></indexterm>
+<screen>
+         SeCreateTokenPrivilege  Create a token object
+  SeAssignPrimaryTokenPrivilege  Replace a process level token
+          SeLockMemoryPrivilege  Lock pages in memory
+       SeIncreaseQuotaPrivilege  Increase quotas
+      SeMachineAccountPrivilege  Add workstations to domain
+                 SeTcbPrivilege  Act as part of the operating system
+            SeSecurityPrivilege  Manage auditing and security log
+       SeTakeOwnershipPrivilege  Take ownership of files or other objects
+          SeLoadDriverPrivilege  Load and unload device drivers
+       SeSystemProfilePrivilege  Profile system performance
+          SeSystemtimePrivilege  Change the system time
+SeProfileSingleProcessPrivilege  Profile single process
+SeIncreaseBasePriorityPrivilege  Increase scheduling priority
+      SeCreatePagefilePrivilege  Create a pagefile
+     SeCreatePermanentPrivilege  Create permanent shared objects
+              SeBackupPrivilege  Back up files and directories
+             SeRestorePrivilege  Restore files and directories
+            SeShutdownPrivilege  Shut down the system
+               SeDebugPrivilege  Debug programs
+               SeAuditPrivilege  Generate security audits
+   SeSystemEnvironmentPrivilege  Modify firmware environment values
+        SeChangeNotifyPrivilege  Bypass traverse checking
+      SeRemoteShutdownPrivilege  Force shutdown from a remote system
+              SeUndockPrivilege  Remove computer from docking station
+           SeSyncAgentPrivilege  Synchronize directory service data
+    SeEnableDelegationPrivilege  Enable computer and user accounts to
+                                 be trusted for delegation
+        SeManageVolumePrivilege  Perform volume maintenance tasks
+         SeImpersonatePrivilege  Impersonate a client after authentication
+        SeCreateGlobalPrivilege  Create global objects
+</screen>
+<indexterm><primary>equivalence</primary></indexterm>
+    The Samba Team is implementing only those privileges that are logical and useful in the UNIX/Linux
+    environment. Many of the Windows 200X/XP privileges have no direct equivalence in UNIX.
+    </para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>The Administrator Domain SID</title>
+
+<para>
+<indexterm><primary>domain Administrator</primary></indexterm>
+<indexterm><primary>User Rights and Privileges</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>net getlocalsid</primary></indexterm>
+Please note that every Windows NT4 and later server requires a domain Administrator account. Samba versions
+commencing with 3.0.11 permit Administrative duties to be performed via assigned rights and privileges
+(see <link linkend="rights">User Rights and Privileges</link>).  An account in the server's passdb backend can
+be set to the well-known RID of the default administrator account.  To obtain the domain SID on a Samba domain
+controller, run the following command:
+<screen>
+&rootprompt; net getlocalsid
+SID for domain FOO is: S-1-5-21-4294955119-3368514841-2087710299
+</screen>
+<indexterm><primary>RID</primary></indexterm>
+You may assign the domain administrator RID to an account using the <command>pdbedit</command>
+command as shown here:
+<indexterm><primary>pdbedit</primary></indexterm>
+<screen>
+&rootprompt; pdbedit -U S-1-5-21-4294955119-3368514841-2087710299-500 -u root -r
+</screen>
+</para>
+
+<note><para>
+<indexterm><primary>RID 500</primary></indexterm>
+<indexterm><primary>well known RID</primary></indexterm>
+<indexterm><primary>rights and privileges</primary></indexterm>
+<indexterm><primary>root account</primary></indexterm>
+The RID 500 is the well known standard value of the default Administrator account. It is the RID
+that confers the rights and privileges that the Administrator account has on a Windows machine
+or domain. Under UNIX/Linux the equivalent is UID=0 (the root account).
+</para></note>
+
+<para>
+<indexterm><primary>without Administrator account</primary></indexterm>
+<indexterm><primary>equivalent rights and privileges</primary></indexterm>
+<indexterm><primary>Windows group account</primary></indexterm>
+<indexterm><primary>3.0.11</primary></indexterm>
+Releases of Samba version 3.0.11 and later make it possible to operate without an Administrator account
+provided equivalent rights and privileges have been established for a Windows user or a Windows
+group account. 
+</para>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+	<sect2>
+	<title>What Rights and Privileges Will Permit Windows Client Administration?</title>
+
+	<para>
+<indexterm><primary>domain global</primary></indexterm>
+<indexterm><primary>local group</primary></indexterm>
+<indexterm><primary>administrative rights</primary></indexterm>
+<indexterm><primary>Windows client</primary></indexterm>
+	When a Windows NT4 (or later) client joins a domain, the domain global <literal>Domain Admins</literal> group
+	is added to the membership of the local <literal>Administrators</literal> group on the client. Any user who is
+	a member of the domain global <literal>Domain Admins</literal> group will have administrative rights on the
+	Windows client.
+	</para>
+
+	<para>
+<indexterm><primary>desirable solution</primary></indexterm>
+<indexterm><primary>administrative rights and privileges</primary></indexterm>
+<indexterm><primary>Power Users</primary></indexterm>
+<indexterm><primary>domain global user</primary></indexterm>
+<indexterm><primary>domain global group</primary></indexterm>
+	This is often not the most desirable solution because it means that the user will have administrative
+	rights and privileges on domain servers also. The <literal>Power Users</literal> group on Windows client
+	workstations permits local administration of the workstation alone. Any domain global user or domain global
+	group can be added to the membership of the local workstation group <literal>Power Users</literal>.
+	</para>
+
+	<para>
+<indexterm><primary>Nested Group Support</primary></indexterm>
+<indexterm><primary>add domain users and groups to a local group</primary></indexterm>
+<indexterm><primary>net</primary></indexterm>
+<indexterm><primary>Windows workstation.</primary></indexterm>
+	See <link linkend="nestedgrpmgmgt">Nested Group Support</link> for an example of how to add domain users
+	and groups to a local group that is on a Windows workstation. The use of the <command>net</command>
+	command permits this to be done from the Samba server.
+	</para>
+
+	<para>
+<indexterm><primary>cmd</primary></indexterm>
+<indexterm><primary>cmd shell</primary></indexterm>
+<indexterm><primary>net</primary><secondary>localgroup</secondary></indexterm>
+	Another way this can be done is to log onto the Windows workstation as the user
+	<literal>Administrator</literal>, then open a <command>cmd</command> shell, then execute:
+<screen>
+&dosprompt; net localgroup administrators /add <userinput>domain_name\entity</userinput>
+</screen>
+	where <literal>entity</literal> is either a domain user or a domain group account name.
+	</para>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-SWAT.xml b/docs-xml/Samba3-HOWTO/TOSHARG-SWAT.xml
new file mode 100644
index 00000000000..73b092f7f06
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-SWAT.xml
@@ -0,0 +1,640 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="SWAT">
+<chapterinfo>
+	&author.jht;
+	<pubdate>April 21, 2003</pubdate>
+</chapterinfo>
+
+<title>SWAT: The Samba Web Administration Tool</title>
+
+<para>
+<indexterm><primary>configuration tool</primary></indexterm>
+<indexterm><primary>SWAT</primary></indexterm>
+<indexterm><primary>Web-based configuration</primary></indexterm>
+There are many and varied opinions regarding the usefulness of SWAT.  No matter how hard one tries to produce
+the perfect configuration tool, it remains an object of personal taste. SWAT is a tool that allows Web-based
+configuration of Samba. It has a wizard that may help to get Samba configured quickly, it has
+context-sensitive help on each &smb.conf; parameter, it provides for monitoring of current state of connection
+information, and it allows networkwide MS Windows network password management.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>internetworking super daemon</primary></indexterm>
+SWAT is a facility that is part of the Samba suite. The main executable is called
+<command>swat</command> and is invoked by the internetworking super daemon.
+See <link linkend="xinetd">appropriate section</link> for details.
+</para>
+
+<para>
+<indexterm><primary>man</primary></indexterm>
+SWAT uses integral Samba components to locate parameters supported by the particular
+version of Samba. Unlike tools and utilities that are external to Samba, SWAT is always
+up to date as known Samba parameters change. SWAT provides context-sensitive help for each
+configuration parameter, directly from <command>man</command> page entries.
+</para>
+
+<para>
+<indexterm><primary>documentation</primary></indexterm>
+<indexterm><primary>configuration files</primary></indexterm>
+<indexterm><primary>internal ordering</primary></indexterm>
+Some network administrators believe that it is a good idea to write systems
+documentation inside configuration files, and for them SWAT will always be a nasty tool. SWAT
+does not store the configuration file in any intermediate form; rather, it stores only the
+parameter settings, so when SWAT writes the &smb.conf; file to disk, it writes only
+those parameters that are at other than the default settings. The result is that all comments,
+as well as parameters that are no longer supported, will be lost from the &smb.conf; file.
+Additionally, the parameters will be written back in internal ordering.
+</para>
+
+<note><para>
+<indexterm><primary>stripped of comments</primary></indexterm>
+Before using SWAT, please be warned &smbmdash; SWAT will completely replace your &smb.conf; with
+a fully optimized file that has been stripped of all comments you might have placed there
+and only nondefault settings will be written to the file.
+</para></note>
+
+</sect1>
+
+<sect1>
+<title>Guidelines and Technical Tips</title>
+
+<para>
+<indexterm><primary>internationalization support</primary></indexterm>
+This section aims to unlock the dark secrets behind how SWAT may be made to work,
+how it can be made more secure, and how to solve internationalization support problems.
+</para>
+
+<sect2>
+<title>Validate SWAT Installation</title>
+
+<para>
+<indexterm><primary>SWAT binary support</primary></indexterm>
+The very first step that should be taken before attempting to configure a host
+system for SWAT operation is to check that it is installed. This may seem a trivial
+point to some, but several Linux distributions do not install SWAT by default,
+even though they do ship an installable binary support package containing SWAT
+on the distribution media.
+</para>
+
+<para>
+<indexterm><primary>swat</primary></indexterm>
+When you have confirmed that SWAT is installed, it is necessary to validate
+that the installation includes the binary <command>swat</command> file as well
+as all the supporting text and Web files. A number of operating system distributions
+in the past have failed to include the necessary support files, even though the
+<command>swat</command> binary executable file was installed. 
+</para>
+
+<para>
+<indexterm><primary>inetd</primary></indexterm>
+<indexterm><primary>xinetd</primary></indexterm>
+Finally, when you are sure that SWAT has been fully installed, please check that SWAT
+is enabled in the control file for the internetworking super-daemon (inetd or xinetd)
+that is used on your operating system platform. 
+</para>
+
+<sect3>
+<title>Locating the <command>SWAT</command> File</title>
+
+<para>
+<indexterm><primary>/usr/local/samba/bin</primary></indexterm>
+<indexterm><primary>/usr/sbin</primary></indexterm>
+<indexterm><primary>/opt/samba/bin</primary></indexterm>
+To validate that SWAT is installed, first locate the <command>swat</command> binary
+file on the system. It may be found under the following directories:</para>
+<para><simplelist>
+	<member><filename>/usr/local/samba/bin</filename> &smbmdash; the default Samba location</member>
+	<member><filename>/usr/sbin</filename> &smbmdash; the default location on most Linux systems</member>
+	<member><filename>/opt/samba/bin</filename></member>
+</simplelist>
+</para>
+
+<para>
+The actual location is much dependent on the choice of the operating system vendor or as determined
+by the administrator who compiled and installed Samba.
+</para>
+
+<para>
+There are a number of methods that may be used to locate the <command>swat</command> binary file.
+The following methods may be helpful.
+</para>
+
+<para>
+<indexterm><primary>swat</primary></indexterm>
+<indexterm><primary>operating system search path</primary></indexterm>
+<indexterm><primary>swat command-line options</primary></indexterm>
+If <command>swat</command> is in your current operating system search path, it will be easy to 
+find it. You can ask what are the command-line options for <command>swat</command> as shown here:
+<screen>
+frodo:~ # swat -?
+Usage: swat [OPTION...]
+  -a, --disable-authentication         Disable authentication (demo mode)
+
+Help options:
+  -?, --help                           Show this help message
+  --usage                              Display brief usage message
+
+Common samba options:
+  -d, --debuglevel=DEBUGLEVEL          Set debug level
+  -s, --configfile=CONFIGFILE          Use alternative configuration file
+  -l, --log-basename=LOGFILEBASE       Basename for log/debug files
+  -V, --version                        Print version
+</screen>
+</para>
+
+</sect3>
+
+<sect3>
+<title>Locating the SWAT Support Files</title>
+
+<para>
+Now that you have found that <command>swat</command> is in the search path, it is easy
+to identify where the file is located. Here is another simple way this may be done:
+<screen>
+frodo:~ # whereis swat
+swat: /usr/sbin/swat /usr/share/man/man8/swat.8.gz
+</screen>
+</para>
+
+<para>
+If the above measures fail to locate the <command>swat</command> binary, another approach
+is needed. The following may be used:
+<screen>
+frodo:/ # find / -name swat -print
+/etc/xinetd.d/swat
+/usr/sbin/swat
+/usr/share/samba/swat
+frodo:/ #
+</screen>
+</para>
+
+<para>
+This list shows that there is a control file for <command>xinetd</command>, the internetwork
+super-daemon that is installed on this server. The location of the SWAT binary file is
+<filename>/usr/sbin/swat</filename>, and the support files for it are located under the
+directory <filename>/usr/share/samba/swat</filename>.
+</para>
+
+<para>
+We must now check where <command>swat</command> expects to find its support files. This can
+be done as follows:
+<screen>
+frodo:/ # strings /usr/sbin/swat | grep "/swat"
+/swat/
+...
+/usr/share/samba/swat
+frodo:/ #
+</screen>
+</para>
+
+<para>
+The <filename>/usr/share/samba/swat/</filename> entry shown in this listing is the location of the
+support files. You should verify that the support files exist under this directory. A sample
+list is as shown:
+<screen>
+jht@frodo:/> find /usr/share/samba/swat -print
+/usr/share/samba/swat
+/usr/share/samba/swat/help
+/usr/share/samba/swat/lang
+/usr/share/samba/swat/lang/ja
+/usr/share/samba/swat/lang/ja/help
+/usr/share/samba/swat/lang/ja/help/welcome.html
+/usr/share/samba/swat/lang/ja/images
+/usr/share/samba/swat/lang/ja/images/home.gif
+...
+/usr/share/samba/swat/lang/ja/include
+/usr/share/samba/swat/lang/ja/include/header.nocss.html
+...
+/usr/share/samba/swat/lang/tr
+/usr/share/samba/swat/lang/tr/help
+/usr/share/samba/swat/lang/tr/help/welcome.html
+/usr/share/samba/swat/lang/tr/images
+/usr/share/samba/swat/lang/tr/images/home.gif
+...
+/usr/share/samba/swat/lang/tr/include
+/usr/share/samba/swat/lang/tr/include/header.html
+/usr/share/samba/swat/using_samba
+...
+/usr/share/samba/swat/images
+/usr/share/samba/swat/images/home.gif
+...
+/usr/share/samba/swat/include
+/usr/share/samba/swat/include/footer.html
+/usr/share/samba/swat/include/header.html
+jht@frodo:/>
+</screen>
+</para>
+
+<para>
+If the files needed are not available, it is necessary to obtain and install them
+before SWAT can be used.
+</para>
+
+</sect3>
+</sect2>
+
+<sect2 id="xinetd">
+<title>Enabling SWAT for Use</title>
+
+<para>
+SWAT should be installed to run via the network super-daemon. Depending on which system
+your UNIX/Linux system has, you will have either an <command>inetd</command>- or
+<command>xinetd</command>-based system.
+</para>
+
+<para>
+The nature and location of the network super-daemon varies with the operating system
+implementation. The control file (or files) can be located in the file 
+<filename>/etc/inetd.conf</filename> or in the directory <filename>/etc/[x]inet[d].d</filename>
+or in a similar location.
+</para>
+
+<para>
+The control entry for the older style file might be:
+<indexterm><primary>swat</primary><secondary>enable</secondary></indexterm>
+</para>
+
+
+<para><programlisting>
+	# swat is the Samba Web Administration Tool
+	swat stream tcp nowait.400 root /usr/sbin/swat swat
+</programlisting></para>
+
+<para>
+A control file for the newer style xinetd could be:
+</para>
+
+<para>
+<programlisting>
+# default: off
+# description: SWAT is the Samba Web Admin Tool. Use swat \
+#              to configure your Samba server. To use SWAT, \
+#              connect to port 901 with your favorite web browser.
+service swat
+{
+	port    = 901
+	socket_type     = stream
+	wait    = no
+	only_from = localhost
+	user    = root
+	server  = /usr/sbin/swat
+	log_on_failure  += USERID
+	disable = no
+}
+</programlisting>
+In the above, the default setting for <parameter>disable</parameter> is <constant>yes</constant>.
+This means that SWAT is disabled. To enable use of SWAT, set this parameter to <constant>no</constant>
+as shown.
+</para>
+
+<para>
+<indexterm><primary>swat</primary></indexterm>
+<indexterm><primary>/usr/sbin</primary></indexterm>
+<indexterm><primary>/usr/share/samba/swat</primary></indexterm>
+<indexterm><primary>/usr/local/samba/swat</primary></indexterm>
+Both of the previous examples assume that the <command>swat</command> binary has been
+located in the <filename>/usr/sbin</filename> directory. In addition to the above,
+SWAT will use a directory access point from which it will load its Help files
+as well as other control information. The default location for this on most Linux
+systems is in the directory <filename>/usr/share/samba/swat</filename>. The default
+location using Samba defaults will be <filename>/usr/local/samba/swat</filename>.
+</para>
+
+<para>
+<indexterm><primary>SWAT permission allowed</primary></indexterm>
+<indexterm><primary>password change facility</primary></indexterm>
+Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user,
+the only permission allowed is to view certain aspects of configuration as well as
+access to the password change facility. The buttons that will be exposed to the non-root
+user are <guibutton>HOME</guibutton>, <guibutton>STATUS</guibutton>, <guibutton>VIEW</guibutton>, and 
+<guibutton>PASSWORD</guibutton>. The only page that allows
+change capability in this case is <guibutton>PASSWORD</guibutton>.
+</para>
+
+<para>
+As long as you log onto SWAT as the user <emphasis>root</emphasis>, you should obtain
+full change and commit ability. The buttons that will be exposed include
+<guibutton>HOME</guibutton>, <guibutton>GLOBALS</guibutton>, <guibutton>SHARES</guibutton>, <guibutton>PRINTERS</guibutton>, 
+<guibutton>WIZARD</guibutton>, <guibutton>STATUS</guibutton>, <guibutton>VIEW</guibutton>, and <guibutton>PASSWORD</guibutton>.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Securing SWAT through SSL</title>
+
+
+<para>
+<indexterm><primary>SSL</primary></indexterm>
+<indexterm><primary>swat</primary><secondary>security</secondary></indexterm>
+Many people have asked about how to set up SWAT with SSL to allow for secure remote
+administration of Samba. Here is a method that works, courtesy of Markus Krieger.
+</para>
+
+<para>
+Modifications to the SWAT setup are as follows: 
+</para>
+
+<procedure>
+	<step><para>
+<indexterm><primary>OpenSSL</primary></indexterm>
+	Install OpenSSL.
+	</para></step>
+
+	<step><para>
+<indexterm><primary>certificate</primary></indexterm>
+<indexterm><primary>private key</primary></indexterm>
+	Generate certificate and private key.
+<indexterm><primary>/usr/bin/openssl</primary></indexterm>
+<screen>
+&rootprompt;<userinput>/usr/bin/openssl req -new -x509 -days 365 -nodes -config \
+	/usr/share/doc/packages/stunnel/stunnel.cnf \
+	-out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem</userinput>
+</screen></para></step>
+
+	<step><para>
+	Remove SWAT entry from [x]inetd.
+	</para></step>
+
+	<step><para>
+<indexterm><primary>stunnel</primary></indexterm>
+	Start <command>stunnel</command>.
+
+<screen>
+&rootprompt;<userinput>stunnel -p /etc/stunnel/stunnel.pem -d 901 \
+	 -l /usr/local/samba/bin/swat swat </userinput>
+</screen></para></step>
+</procedure>
+
+<para>
+Afterward, simply connect to SWAT by using the URL <ulink noescape="1"
+url="https://myhost:901">https://myhost:901</ulink>, accept the certificate, and the SSL connection is up.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Enabling SWAT Internationalization Support</title>
+
+<para>
+SWAT can be configured to display its messages to match the settings of
+the language configurations of your Web browser. It will be passed to SWAT 
+in the Accept-Language header of the HTTP request.
+</para>
+
+<para>
+To enable this feature:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Install  the proper <command>msg</command> files from the Samba
+	<filename>source/po</filename> directory into $LIBDIR.
+	</para></listitem>
+
+	<listitem><para>
+	Set your browsers language setting.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>msg file</primary></indexterm>
+<indexterm><primary>Japanese</primary></indexterm>
+<indexterm><primary>French</primary></indexterm>
+<indexterm><primary>English</primary></indexterm>
+The name of the <command>msg</command> file is the same as the language ID sent by the browser. For
+example, <emphasis>en</emphasis> means English, <emphasis>ja</emphasis> means Japanese, <emphasis>fr</emphasis> means French.
+</para>
+
+<para>
+<indexterm><primary>locale</primary></indexterm>
+If you do not like some of messages, or there are no <command>msg</command> files for
+your locale, you can create them simply by copying the <command>en.msg</command> files
+to the directory for <quote>your language ID.msg</quote> and filling in proper strings
+to each <quote>msgstr</quote>. For example, in <filename>it.msg</filename>, the
+<command>msg</command> file for the Italian locale, just set:
+<screen>
+msgid "Set Default"
+msgstr "Imposta Default"
+</screen>
+<indexterm><primary>msg</primary></indexterm>
+and so on. If you find a mistake or create a new <command>msg</command> file, please email it
+to us so we will consider it in the next release of Samba. The <command>msg</command> file should be encoded in UTF-8.
+</para>
+
+<para>
+<indexterm><primary>UTF-8 encoding</primary></indexterm>
+Note that if you enable this feature and the <smbconfoption name="display charset"/> is not
+matched to your browser's setting, the SWAT display may be corrupted.  In a future version of
+Samba, SWAT will always display messages with UTF-8 encoding. You will then not need to set
+this &smb.conf; file parameter.
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Overview and Quick Tour</title>
+
+<para>
+SWAT is a tool that may be used to configure Samba or just to obtain useful links
+to important reference materials such as the contents of this book as well as other
+documents that have been found useful for solving Windows networking problems.
+</para>
+
+<sect2>
+<title>The SWAT Home Page</title>
+
+<para>
+The SWAT title page provides access to the latest Samba documentation. The manual page for
+each Samba component is accessible from this page, as are the Samba3-HOWTO (this 
+document) as well as the O'Reilly book <quote>Using Samba.</quote>
+</para>
+
+<para>
+Administrators who wish to validate their Samba configuration may obtain useful information
+from the man pages for the diagnostic utilities. These are available from the SWAT home page
+also. One diagnostic tool that is not mentioned on this page but that is particularly
+useful is <ulink url="http://www.ethereal.com/"><command>ethereal</command></ulink>.
+</para>
+
+<warning><para>
+SWAT can be configured to run in <emphasis>demo</emphasis> mode. This is not recommended
+because it runs SWAT without authentication and with full administrative ability. It allows
+changes to &smb.conf; as well as general operation with root privileges. The option that
+creates this ability is the <option>-a</option> flag to SWAT. <emphasis>Do not use this in a
+production environment.</emphasis>
+</para></warning>
+
+</sect2>
+
+<sect2>
+<title>Global Settings</title>
+
+<para>
+The <guibutton>GLOBALS</guibutton> button exposes a page that allows configuration of the global parameters
+in &smb.conf;. There are two levels of exposure of the parameters:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<guibutton>Basic</guibutton> &smbmdash; exposes common configuration options.
+	</para></listitem>
+
+	<listitem><para>
+	<guibutton>Advanced</guibutton> &smbmdash; exposes configuration options needed in more 
+	complex environments.
+	</para></listitem>
+</itemizedlist>
+
+<para>
+To switch to other than <guibutton>Basic</guibutton> editing ability, click on <guibutton>Advanced</guibutton>.
+You may also do this by clicking on the radio button, then click on the <guibutton>Commit Changes</guibutton> button.
+</para>
+
+<para>
+After making any changes to configuration parameters, make sure that
+you click on the 
+<guibutton>Commit Changes</guibutton> button before moving to another area; otherwise,
+your changes will be lost.
+</para>
+
+<note><para>
+SWAT has context-sensitive help. To find out what each parameter is
+for, simply click on the
+<guibutton>Help</guibutton> link to the left of the configuration parameter.
+</para></note>
+
+</sect2>
+
+<sect2>
+<title>Share Settings</title>
+
+<para>
+To affect a currently configured share, simply click on the pull-down button between the
+<guibutton>Choose Share</guibutton> and the <guibutton>Delete Share</guibutton> buttons and
+select the share you wish to operate on. To edit the settings,
+click on the
+<guibutton>Choose Share</guibutton> button. To delete the share, simply press the
+<guibutton>Delete Share</guibutton> button.
+</para>
+
+<para>
+To create a new share, next to the button labeled <guibutton>Create Share</guibutton>, enter
+into the text field the name of the share to be created, then click on the 
+<guibutton>Create Share</guibutton> button.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Printers Settings</title>
+
+<para>
+To affect a currently configured printer, simply click on the pull-down button between the
+<guibutton>Choose Printer</guibutton> and the <guibutton>Delete Printer</guibutton> buttons and
+select the printer you wish to operate on. To edit the settings,
+click on the
+<guibutton>Choose Printer</guibutton> button. To delete the share, simply press the
+<guibutton>Delete Printer</guibutton> button.
+</para>
+
+<para>
+To create a new printer, next to the button labeled <guibutton>Create Printer</guibutton>, enter
+into the text field the name of the share to be created, then click on the 
+<guibutton>Create Printer</guibutton> button.
+</para>
+
+</sect2>
+
+<sect2>
+<title>The SWAT Wizard</title>
+
+<para>
+The purpose of the SWAT Wizard is to help the Microsoft-knowledgeable network administrator
+to configure Samba with a minimum of effort.
+</para>
+
+<para>
+The Wizard page provides a tool for rewriting the &smb.conf; file in fully optimized format.
+This will also happen if you press the <guibutton>Commit</guibutton> button. The two differ
+because the <guibutton>Rewrite</guibutton> button ignores any changes that may have been made,
+while the <guibutton>Commit</guibutton> button causes all changes to be affected.
+</para>
+
+<para>
+The <guibutton>Edit</guibutton> button permits the editing (setting) of the minimal set of
+options that may be necessary to create a working Samba server.
+</para>
+
+<para>
+Finally, there are a limited set of options that determine what type of server Samba
+will be configured for, whether it will be a WINS server, participate as a WINS client, or
+operate with no WINS support. By clicking one button, you can elect to expose (or not) user
+home directories.
+</para>
+
+</sect2>
+
+<sect2>
+<title>The Status Page</title>
+
+<para>
+The status page serves a limited purpose. First, it allows control of the Samba daemons.
+The key daemons that create the Samba server environment are &smbd;, &nmbd;, and &winbindd;.
+</para>
+
+<para>
+The daemons may be controlled individually or as a total group. Additionally, you may set
+an automatic screen refresh timing. As MS Windows clients interact with Samba, new smbd processes
+are continually spawned. The auto-refresh facility allows you to track the changing
+conditions with minimal effort.
+</para>
+
+<para>
+Finally, the status page may be used to terminate specific smbd client connections in order to
+free files that may be locked.
+</para>
+
+</sect2>
+
+<sect2>
+<title>The View Page</title>
+
+<para>
+The view page allows you to view the optimized &smb.conf; file and, if you are
+particularly masochistic, permits you also to see all possible global configuration
+parameters and their settings.
+</para>
+
+</sect2>
+
+<sect2>
+<title>The Password Change Page</title>
+
+<para>
+The password change page is a popular tool that allows the creation, deletion, deactivation,
+and reactivation of MS Windows networking users on the local machine. You can also use
+this tool to change a local password for a user account.
+</para>
+
+<para>
+When logged in as a non-root account, the user must provide the old password as well as
+the new password (twice). When logged in as <emphasis>root</emphasis>, only the new password is
+required.
+</para>
+
+<para>
+One popular use for this tool is to change user passwords across a range of remote MS Windows
+servers.
+</para>
+
+</sect2>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-SecureLDAP.xml b/docs-xml/Samba3-HOWTO/TOSHARG-SecureLDAP.xml
new file mode 100644
index 00000000000..4d79895985f
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-SecureLDAP.xml
@@ -0,0 +1,405 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="ch-ldap-tls">
+<chapterinfo>
+        &author.ghenry;
+        <pubdate>July 8, 2005</pubdate>
+</chapterinfo>
+<title>LDAP and Transport Layer Security</title>
+
+<sect1 id="s1-intro-ldap-tls">
+<title>Introduction</title>
+
+	<para>
+	<indexterm><primary>Transport Layer Seccurity, TLS</primary><secondary>Introduction</secondary></indexterm>
+<indexterm><primary>ACL</primary></indexterm>
+	Up until now, we have discussed the straightforward configuration of <trademark>OpenLDAP</trademark>,
+	with some advanced features such as ACLs. This does not however, deal with the fact that the network
+	transmissions are still in plain text. This is where <firstterm>Transport Layer Security (TLS)</firstterm>
+	comes in.
+	</para> 
+
+	<para>
+<indexterm><primary>RFC 2830</primary></indexterm>
+	<trademark>OpenLDAP</trademark> clients and servers are capable of using the Transport Layer Security (TLS)
+	framework to provide integrity and confidentiality protections in accordance with <ulink
+	url="http://rfc.net/rfc2830.html">RFC 2830</ulink>; <emphasis>Lightweight Directory Access Protocol (v3):
+	Extension for Transport Layer Security.</emphasis>
+	</para>
+
+	<para>
+<indexterm><primary>X.509 certificates</primary></indexterm>
+	TLS uses X.509 certificates. All servers are required to have valid certificates, whereas client certificates
+	are optional. We will only be discussing server certificates.
+	</para>
+
+	<tip><para>
+<indexterm><primary>DN</primary></indexterm>
+<indexterm><primary>CN</primary></indexterm>
+<indexterm><primary>FQDN</primary></indexterm>
+	The DN of a server certificate must use the CN attribute to name the server, and the CN must carry the
+	server's fully qualified domain name (FQDN). Additional alias names and wildcards may be present in the
+	<option>subjectAltName</option> certificate extension. More details on server certificate names are in <ulink
+	url="http://rfc.net/rfc2830.html">RFC2830</ulink>.
+	</para></tip>
+
+	<para>
+	We will discuss this more in the next sections.
+	</para>
+
+	</sect1>
+
+	<sect1 id="s1-config-ldap-tls">
+	<title>Configuring</title>
+
+	<para>
+	<indexterm><primary>Transport Layer Seccurity, TLS</primary><secondary>Configuring</secondary></indexterm>
+	Now on to the good bit.
+	</para>
+
+	<sect2 id="s1-config-ldap-tls-certs">
+	<title>Generating the Certificate Authority</title>
+
+	<para>
+<indexterm><primary>Certificate Authority</primary><see>CA</see></indexterm>
+	In order to create the relevant certificates, we need to become our own Certificate Authority (CA).
+	<footnote><para>We could however, get our generated server certificate signed by proper CAs, like <ulink
+	url="http://www.thawte.com/">Thawte</ulink> and <ulink url="http://www.verisign.com/">VeriSign</ulink>, which
+	you pay for, or the free ones, via <ulink url="http://www.cacert.org/">CAcert</ulink>
+	</para></footnote> This is necessary, so we can sign the server certificate.
+	</para>
+
+	<para>
+<indexterm><primary>OpenSSL</primary></indexterm>
+	We will be using the <ulink url="http://www.openssl.org">OpenSSL</ulink> <footnote><para>The downside to
+	making our own CA, is that the certificate is not automatically recognized by clients, like the commercial
+	ones are.</para></footnote> software for this, which is included with every great <trademark
+	class="registered">Linux</trademark> distribution.
+	</para>
+
+	<para>
+	TLS is used for many types of servers, but the instructions<footnote><para>For information straight from the
+	horse's mouth, please visit <ulink
+	url="http://www.openssl.org/docs/HOWTO/">http://www.openssl.org/docs/HOWTO/</ulink>; the main OpenSSL
+	site.</para></footnote> presented here, are tailored for &OL;.
+	</para>
+
+	<note><para>
+	The <emphasis>Common Name (CN)</emphasis>, in the following example, <emphasis>MUST</emphasis> be
+	the fully qualified domain name (FQDN) of your ldap server.
+	</para></note>
+
+	<para>
+	First we need to generate the CA:
+<screen width="90">
+<computeroutput>
+&rootprompt; mkdir myCA
+</computeroutput>
+</screen>
+	Move into that directory:
+<screen width="90">
+<computeroutput>
+&rootprompt; cd myCA
+</computeroutput>
+</screen>
+	Now generate the CA:<footnote><para>Your <filename>CA.pl</filename> or <filename>CA.sh</filename> might not be
+	in the same location as mine is, you can find it by using the <command>locate</command> command, i.e.,
+	<command>locate CA.pl</command>.  If the command complains about the database being too old, run
+	<command>updatedb</command> as <emphasis>root</emphasis> to update it.</para></footnote>
+<screen width="90">
+<computeroutput>
+&rootprompt; /usr/share/ssl/misc/CA.pl -newca
+CA certificate filename (or enter to create)
+  
+Making CA certificate ...
+Generating a 1024 bit RSA private key
+.......................++++++
+.............................++++++
+writing new private key to './demoCA/private/cakey.pem'
+Enter PEM pass phrase:
+Verifying - Enter PEM pass phrase:
+-----
+You are about to be asked to enter information that will be incorporated
+into your certificate request.
+What you are about to enter is what is called a Distinguished Name or a DN.
+There are quite a few fields but you can leave some blank
+For some fields there will be a default value,
+If you enter '.', the field will be left blank.
+-----
+Country Name (2 letter code) [AU]:AU
+State or Province Name (full name) [Some-State]:NSW
+Locality Name (eg, city) []:Sydney
+Organization Name (eg, company) [Internet Widgits Pty Ltd]:Abmas
+Organizational Unit Name (eg, section) []:IT
+Common Name (eg, YOUR name) []:ldap.abmas.biz
+Email Address []:support@abmas.biz
+</computeroutput>
+</screen>
+	</para>
+
+	<para>
+	There are some things to note here. 
+	</para>
+
+	<orderedlist>
+		<listitem>
+			<para>
+			You <emphasis>MUST</emphasis> remember the password, as we will need
+			it to sign the server certificate..
+			</para>
+		</listitem>
+
+		<listitem>
+			<para>
+			The <emphasis>Common Name (CN)</emphasis>, <emphasis>MUST</emphasis> be the
+			fully qualified domain name (FQDN) of your ldap server.
+			</para>
+		</listitem>
+	</orderedlist>
+
+	</sect2>
+
+	<sect2 id="s1-config-ldap-tls-server">
+	<title>Generating the Server Certificate</title>
+
+	<para>
+	Now we need to generate the server certificate:
+<screen width="90">
+<computeroutput>
+&rootprompt; openssl req -new -nodes -keyout newreq.pem -out newreq.pem
+Generating a 1024 bit RSA private key
+.............++++++
+........................................................++++++
+writing new private key to 'newreq.pem'
+-----
+You are about to be asked to enter information that will be incorporated
+into your certificate request.
+What you are about to enter is what is called a Distinguished Name or a DN.
+There are quite a few fields but you can leave some blank
+For some fields there will be a default value,
+If you enter '.', the field will be left blank.
+-----
+Country Name (2 letter code) [AU]:AU
+State or Province Name (full name) [Some-State]:NSW
+Locality Name (eg, city) []:Sydney
+Organization Name (eg, company) [Internet Widgits Pty Ltd]:Abmas
+Organizational Unit Name (eg, section) []:IT
+Common Name (eg, YOUR name) []:ldap.abmas.biz
+Email Address []:support@abmas.biz
+  
+Please enter the following 'extra' attributes
+to be sent with your certificate request
+A challenge password []:
+An optional company name []:
+</computeroutput>
+</screen>
+	</para>	
+
+	<para>
+	Again, there are some things to note here. 
+	</para>		
+
+	<orderedlist>
+		<listitem>
+			<para>
+			You should <emphasis>NOT</emphasis> enter a password.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para>
+			The <emphasis>Common Name (CN)</emphasis>, <emphasis>MUST</emphasis> be
+			the fully qualified domain name (FQDN) of your ldap server.
+			</para>
+		</listitem>
+	</orderedlist>
+
+	<para>
+	Now we sign the certificate with the new CA:
+<screen width="90">
+<computeroutput>
+&rootprompt; /usr/share/ssl/misc/CA.pl -sign
+Using configuration from /etc/ssl/openssl.cnf
+Enter pass phrase for ./demoCA/private/cakey.pem:
+Check that the request matches the signature
+Signature ok
+Certificate Details:
+Serial Number: 1 (0x1)
+Validity
+	Not Before: Mar  6 18:22:26 2005 EDT
+	Not After : Mar  6 18:22:26 2006 EDT
+Subject:
+	countryName               = AU
+	stateOrProvinceName       = NSW
+	localityName              = Sydney
+	organizationName          = Abmas
+	organizationalUnitName    = IT
+	commonName                = ldap.abmas.biz
+	emailAddress              = support@abmas.biz
+X509v3 extensions:
+	X509v3 Basic Constraints:
+	    CA:FALSE
+	Netscape Comment:
+	    OpenSSL Generated Certificate
+	X509v3 Subject Key Identifier:
+	    F7:84:87:25:C4:E8:46:6D:0F:47:27:91:F0:16:E0:86:6A:EE:A3:CE
+	X509v3 Authority Key Identifier:
+	    keyid:27:44:63:3A:CB:09:DC:B1:FF:32:CC:93:23:A4:F1:B4:D5:F0:7E:CC
+	    DirName:/C=AU/ST=NSW/L=Sydney/O=Abmas/OU=IT/
+						CN=ldap.abmas.biz/emailAddress=support@abmas.biz
+	    serial:00
+
+Certificate is to be certified until Mar  6 18:22:26 2006 EDT (365 days)
+Sign the certificate? [y/n]:y
+
+
+1 out of 1 certificate requests certified, commit? [y/n]y
+Write out database with 1 new entries
+Data Base Updated
+Signed certificate is in newcert.pem
+</computeroutput>
+</screen>
+	</para>
+
+	<para>
+	That completes the server certificate generation. 
+	</para>
+
+	</sect2>
+
+	<sect2 id="s1-config-ldap-tls-install">
+	<title>Installing the Certificates</title>
+
+	<para>
+	Now we need to copy the certificates to the right configuration directories,
+	rename them at the same time (for convenience), change the ownership and
+	finally the permissions:
+<screen width="90">
+<computeroutput>
+&rootprompt; cp demoCA/cacert.pem /etc/openldap/
+&rootprompt; cp newcert.pem /etc/openldap/servercrt.pem
+&rootprompt; cp newreq.pem /etc/openldap/serverkey.pem
+&rootprompt; chown ldap.ldap /etc/openldap/*.pem
+&rootprompt; chmod 640 /etc/openldap/cacert.pem;
+&rootprompt; chmod 600 /etc/openldap/serverkey.pem
+</computeroutput>
+</screen>
+	</para>
+
+	<para>
+	Now we just need to add these locations to <filename>slapd.conf</filename>,
+	anywhere before the <option>database</option> declaration as shown here:
+<screen width="90">
+<computeroutput>
+TLSCertificateFile /etc/openldap/servercrt.pem
+TLSCertificateKeyFile /etc/openldap/serverkey.pem
+TLSCACertificateFile /etc/openldap/cacert.pem
+</computeroutput>
+</screen>
+	</para>
+
+	<para>
+	Here is the declaration and <filename>ldap.conf</filename>:
+<filename>ldap.conf</filename>
+<screen width="90">
+<computeroutput>
+TLS_CACERT /etc/openldap/cacert.pem
+</computeroutput>
+</screen>
+	</para>
+
+	<para>
+	That's all there is to it. Now on to <xref linkend="s1-test-ldap-tls"></xref>
+	</para>
+
+	</sect2>
+
+</sect1>
+
+<sect1 id="s1-test-ldap-tls">
+<title>Testing</title>
+
+<para>
+<indexterm><primary>Transport Layer Security, TLS</primary><secondary>Testing</secondary></indexterm>
+This is the easy part. Restart the server:
+<screen width="90">
+<computeroutput>
+&rootprompt; /etc/init.d/ldap restart
+Stopping slapd:                                            [  OK  ]
+Checking configuration files for slapd: config file testing succeeded
+Starting slapd:                                            [  OK  ]
+</computeroutput>
+</screen>
+	Then, using <command>ldapsearch</command>, test an anonymous search with the
+	<option>-ZZ</option><footnote><para>See <command>man ldapsearch</command></para></footnote> option:
+<screen width="90">
+<computeroutput>
+&rootprompt; ldapsearch -x -b "dc=ldap,dc=abmas,dc=biz" \
+        -H 'ldap://ldap.abmas.biz:389' -ZZ
+</computeroutput>
+</screen>
+	Your results should be the same as before you restarted the server, for example:
+<screen width="90">
+<computeroutput>
+&rootprompt; ldapsearch -x -b "dc=ldap,dc=abmas,dc=biz" \
+    -H 'ldap://ldap.abmas.biz:389' -ZZ
+
+# extended LDIF
+#
+# LDAPv3
+# base &lt;&gt; with scope sub
+# filter: (objectclass=*)
+# requesting: ALL
+#
+
+# abmas.biz
+dn: dc=ldap,dc=abmas,dc=biz
+objectClass: dcObject
+objectClass: organization
+o: Abmas
+dc: abmas
+
+# Manager, ldap.abmas.biz
+dn: cn=Manager,dc=ldap,dc=abmas,dc=biz
+objectClass: organizationalRole
+cn: Manager
+
+# ABMAS, abmas.biz
+dn: sambaDomainName=ABMAS,dc=ldap,dc=abmas,dc=biz
+sambaDomainName: ABMAS
+sambaSID: S-1-5-21-238355452-1056757430-1592208922
+sambaAlgorithmicRidBase: 1000
+objectClass: sambaDomain
+sambaNextUserRid: 67109862
+sambaNextGroupRid: 67109863
+</computeroutput>
+</screen>
+	If you have any problems, please read <xref linkend="s1-int-ldap-tls"></xref>
+</para>
+
+</sect1>
+
+<sect1 id="s1-int-ldap-tls">
+<title>Troubleshooting</title>
+
+<para>
+<indexterm><primary>Transport Layer Security, TLS</primary><secondary>Troubleshooting</secondary></indexterm>
+The most common error when configuring TLS, as I have already mentioned numerous times, is that the
+<emphasis>Common Name (CN)</emphasis> you entered in <xref linkend="s1-config-ldap-tls-server"></xref> is
+<emphasis>NOT</emphasis> the Fully Qualified Domain Name (FQDN) of your ldap server.
+</para>
+
+<para>
+Other errors could be that you have a typo somewhere in your <command>ldapsearch</command> command, or that
+your have the wrong permissions on the <filename>servercrt.pem</filename> and <filename>cacert.pem</filename>
+files. They should be set with <command>chmod 640</command>, as per <xref
+linkend="s1-config-ldap-tls-install"></xref>.
+</para>
+
+<para>
+For anything else, it's best to read through your ldap logfile or join the &OL; mailing list.
+</para>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Securing.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Securing.xml
new file mode 100644
index 00000000000..21218ea9da4
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Securing.xml
@@ -0,0 +1,448 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="securing-samba">
+
+<chapterinfo>
+	&author.tridge;
+	&author.jht;
+	<pubdate>May 26, 2003</pubdate>
+</chapterinfo>
+
+<title>Securing Samba</title>
+
+<sect1>
+<title>Introduction</title>
+
+<para>
+<indexterm><primary>security</primary></indexterm>
+<indexterm><primary>direct internet access</primary></indexterm>
+<indexterm><primary>firewall</primary></indexterm>
+<indexterm><primary>private network</primary></indexterm>
+<indexterm><primary>barriers</primary></indexterm>
+<indexterm><primary>deterents</primary></indexterm>
+<indexterm><primary>secured networks</primary></indexterm>
+The information contained in this chapter applies in general to all Samba installations. Security is
+everyone's concern in the information technology world. A surprising number of Samba servers are being
+installed on machines that have direct internet access, thus security is made more critical than it would have been had the
+server been located behind a firewall and on a private network. Paranoia regarding server security is causing
+some  network administrators to insist on the installation of robust firewalls even on servers that are located
+inside secured networks. This chapter provides information to assist the administrator who understands
+how to create the needed barriers and deterents against <quote>the enemy</quote>, no matter where [s]he may
+come from.
+</para>
+
+<blockquote>
+<para>
+A new apprentice reported for duty to the chief engineer of a boiler house. He said, <quote>Here I am,
+if you will show me the boiler I'll start working on it.</quote> Then engineer replied, <quote>You're leaning
+on it!</quote>
+</para>
+</blockquote>
+
+<para>
+Security concerns are just like that. You need to know a little about the subject to appreciate
+how obvious most of it really is. The challenge for most of us is to discover that first morsel
+of knowledge with which we may unlock the secrets of the masters.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>moderately secure</primary></indexterm>
+<indexterm><primary>perimeter firewall</primary></indexterm>
+<indexterm><primary>host security</primary></indexterm>
+<indexterm><primary>Samba security</primary></indexterm>
+There are three levels at which security principles must be observed in order to render a site
+at least moderately secure. They are the perimeter firewall, the configuration of the host
+server that is running Samba, and Samba itself.
+</para>
+
+<para>
+Samba permits a most flexible approach to network security. As far as possible Samba implements
+the latest protocols to permit more secure MS Windows file and print operations.
+</para>
+
+<para>
+<indexterm><primary>host-based protection</primary></indexterm>
+<indexterm><primary>interface-based exclusion</primary></indexterm>
+<indexterm><primary>resource-based exclusion</primary></indexterm>
+Samba can be secured from connections that originate from outside the local network. This can be done using
+<emphasis>host-based protection</emphasis>, using Samba's implementation of a technology known as
+<quote>tcpwrappers,</quote> or it may be done be using <emphasis>interface-based exclusion</emphasis> so
+&smbd; will bind only to specifically permitted interfaces. It is also possible to set specific share- or
+resource-based exclusions, for example, on the <smbconfsection name="[IPC$]"/> autoshare. The <smbconfsection
+name="[IPC$]"/> share is used for browsing purposes as well as to establish TCP/IP connections.
+</para>
+
+<para>
+<indexterm><primary>Access Control Entries</primary><see>ACE</see></indexterm>
+<indexterm><primary>ACL</primary></indexterm>
+<indexterm>controls<primary></primary></indexterm>
+Another method by which Samba may be secured is by setting Access Control Entries (ACEs) in an Access 
+Control List (ACL) on the shares themselves. This is discussed in
+<link linkend="AccessControls">File, Directory, and Share Access Controls</link>.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Technical Discussion of Protective Measures and Issues</title>
+
+<para>
+The key challenge of security is that protective measures suffice at best
+only to close the door on known exploits and breach techniques. Never assume that
+because you have followed these few measures, the Samba server is now an impenetrable
+fortress! Given the history of information systems so far, it is only a matter of time
+before someone will find yet another vulnerability.
+</para>
+
+	<sect2>
+	<title>Using Host-Based Protection</title>
+
+	<para>
+<indexterm><primary>outside threat</primary></indexterm>
+<indexterm><primary>insecure</primary></indexterm>
+<indexterm><primary>Internet</primary></indexterm>
+	In many installations of Samba, the greatest threat comes from outside
+	your immediate network. By default, Samba accepts connections from
+	any host, which means that if you run an insecure version of Samba on
+	a host that is directly connected to the Internet, you can be
+	especially vulnerable.
+	</para>
+
+	<para>
+<indexterm><primary>allow access</primary></indexterm>
+<indexterm><primary>range of hosts</primary></indexterm>
+	One of the simplest fixes in this case is to use the <smbconfoption name="hosts allow"/> and
+	<smbconfoption name="hosts deny"/> options in the Samba &smb.conf; configuration file to
+	allow access to your server only from a specific range of hosts. An example might be:
+	<smbconfblock>
+	<smbconfoption name="hosts allow">127.0.0.1 192.168.2.0/24 192.168.3.0/24</smbconfoption>
+	<smbconfoption name="hosts deny">0.0.0.0/0</smbconfoption>
+	</smbconfblock>
+	</para>
+
+	<para>
+<indexterm><primary>localhost</primary></indexterm>
+<indexterm><primary>private networks</primary></indexterm>
+<indexterm><primary>called name</primary></indexterm>
+	The above will allow SMB connections only from <constant>localhost</constant> (your own
+	computer) and from the two private networks 192.168.2 and 192.168.3. All other
+	connections will be refused as soon as the client sends its first packet. The refusal
+	will be marked as <literal>not listening on called name</literal> error.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>User-Based Protection</title>
+
+	<para>
+	If you want to restrict access to your server to valid users only, then the following
+	method may be of use. In the &smb.conf; <smbconfsection name="[global]"/> section put:
+	<smbconfblock>
+	<smbconfoption name="valid users">@smbusers, jacko</smbconfoption>
+	</smbconfblock>
+	</para>
+
+	<para>
+<indexterm><primary>smbusers</primary></indexterm>
+	This restricts all server access either to the user <emphasis>jacko</emphasis>
+	or to members of the system group <emphasis>smbusers</emphasis>.
+	</para>
+
+	</sect2>
+
+	<sect2>
+
+	<title>Using Interface Protection</title>
+
+	<para>
+<indexterm><primary>network interface</primary></indexterm>
+<indexterm><primary>accept connections</primary></indexterm>
+<indexterm><primary>Internet</primary></indexterm>
+	By default, Samba accepts connections on any network interface that
+	it finds on your system. That means if you have an ISDN line or a PPP
+	connection to the Internet then Samba will accept connections on those
+	links. This may not be what you want.
+	</para>
+
+	<para>
+	You can change this behavior using options like this:
+	<smbconfblock>
+	<smbconfoption name="interfaces">eth* lo</smbconfoption>
+	<smbconfoption name="bind interfaces only">yes</smbconfoption>
+	</smbconfblock>
+	</para>
+
+	<para>
+<indexterm><primary>interfaces</primary></indexterm>
+<indexterm><primary>loopback interface</primary></indexterm>
+<indexterm><primary>Ethernet adapters</primary></indexterm>
+<indexterm><primary>listen for connections</primary></indexterm>
+	This tells Samba to listen for connections only on interfaces with a name starting with
+	<constant>eth</constant> such as <constant>eth0</constant> or <constant>eth1</constant>, plus on the loopback interface called
+	<constant>lo</constant>. The name you will need to use depends on what OS you are using. In the above, I used
+	the common name for Ethernet adapters on Linux.
+	</para>
+
+	<para>
+<indexterm><primary>PPP</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>cracker</primary></indexterm>
+<indexterm><primary>confirm address</primary></indexterm>
+	If you use the above and someone tries to make an SMB connection to your host over a PPP interface called
+	<constant>ppp0</constant>, then [s]he will get a TCP connection refused reply. In that case, no Samba code
+	is run at all, because the operating system has been told not to pass connections from that interface to any
+	Samba process. However, the refusal helps a would-be cracker by confirming that the IP address provides
+	valid active services.
+	</para>
+
+	<para>
+<indexterm><primary>ignore connection</primary></indexterm>
+<indexterm><primary>refusing connection</primary></indexterm>
+<indexterm><primary>exploitation</primary></indexterm>
+<indexterm><primary>denial of service</primary></indexterm>
+<indexterm><primary>firewall</primary></indexterm>
+	A better response would be to ignore the connection (from, for example, ppp0) altogether. The
+	advantage of ignoring the connection attempt, as compared with refusing it, is that it foils those who
+	probe an interface with the sole intention of finding valid IP addresses for later use in exploitation
+	or denial of service attacks. This method of dealing with potential malicious activity demands the
+	use of appropriate firewall mechanisms.
+	</para>
+
+	</sect2>
+
+	<sect2 id="firewallports">
+	<title>Using a Firewall</title>
+
+	<para>
+<indexterm><primary>deny access</primary></indexterm>
+<indexterm><primary>exposed</primary></indexterm>
+<indexterm><primary>firewall active</primary></indexterm>
+	Many people use a firewall to deny access to services they do not want exposed outside their network. This can
+	be a good idea, although I recommend using it in conjunction with the above methods so you are protected even
+	if your firewall is not active for some reason.
+	</para>
+
+	<para>
+	If you are setting up a firewall, you need to know what TCP and UDP ports to allow and block. Samba uses
+	the following:
+<indexterm><primary>Port 135/TCP</primary></indexterm>
+<indexterm><primary>Port 137/UDP</primary></indexterm>
+<indexterm><primary>Port 138/UDP</primary></indexterm>
+<indexterm><primary>Port 139/TCP</primary></indexterm>
+<indexterm><primary>Port 445/TCP</primary></indexterm>
+	</para>
+
+	<simplelist>
+		<member>Port 135/TCP - used by smbd</member>
+		<member>Port 137/UDP - used by nmbd</member>
+		<member>Port 138/UDP - used by nmbd</member>
+		<member>Port 139/TCP - used by smbd</member>
+		<member>Port 445/TCP - used by smbd</member>
+	</simplelist>
+
+	<para>
+<indexterm><primary>firewall setups</primary></indexterm>
+	The last one is important because many older firewall setups may not be aware of it, given that this port
+	was only added to the protocol in recent years.
+	</para>
+
+	<para>
+<indexterm><primary>configuring a firewall</primary></indexterm>
+<indexterm><primary>high order ports</primary></indexterm>
+<indexterm><primary>block incoming packets</primary></indexterm>
+	When configuring a firewall, the high order ports (1024-65535) are often used for outgoing connections and
+	therefore should be permitted through the firewall. It is prudent to block incoming packets on the high order
+	ports except for established connections.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Using IPC$ Share-Based Denials </title>
+
+	<para>
+<indexterm><primary>IPC$</primary></indexterm>
+<indexterm><primary>deny</primary></indexterm>
+<indexterm><primary>security hole</primary></indexterm>
+	If the above methods are not suitable, then you could also place a more specific deny on the IPC$ share that
+	is used in the recently discovered security hole. This allows you to offer access to other shares while
+	denying access to IPC$ from potentially untrustworthy hosts.
+	</para>
+
+	<para>
+	To do this you could use:
+	<smbconfblock>
+	<smbconfsection name="[IPC$]"/>
+	<smbconfoption name="hosts allow">192.168.115.0/24 127.0.0.1</smbconfoption>
+	<smbconfoption name="hosts deny">0.0.0.0/0</smbconfoption>
+	</smbconfblock>
+	</para>
+
+	<para>
+<indexterm><primary>IPC$</primary></indexterm>
+<indexterm><primary>protection against attackers</primary></indexterm>
+<indexterm><primary>valid username/password</primary></indexterm>
+	This instructs Samba that IPC$ connections are not allowed from anywhere except the two listed network
+	addresses (localhost and the 192.168.115 subnet). Connections to other shares are still allowed. Because the
+	IPC$ share is the only share that is always accessible anonymously, this provides some level of protection
+	against attackers who do not know a valid username/password for your host.
+	</para>
+
+	<para>
+<indexterm><primary>access denied</primary></indexterm>
+<indexterm><primary>IPC$</primary></indexterm>
+<indexterm><primary>browse shares</primary></indexterm>
+	If you use this method, then clients will be given an <literal>`access denied'</literal> reply when they try
+	to access the IPC$ share. Those clients will not be able to browse shares and may also be unable to access
+	some other resources.  This is not recommended unless for some reason you cannot use one of the other methods
+	just discussed.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>NTLMv2 Security</title>
+
+	<para>
+<indexterm><primary>NTLMv2</primary></indexterm>
+	To configure NTLMv2 authentication, the following registry keys are worth knowing about:
+	</para>
+
+	<para>
+		<screen>
+		[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
+		"lmcompatibilitylevel"=dword:00000003
+		</screen>
+	</para>
+
+	<para>
+	The value 0x00000003 means to send NTLMv2 response only. Clients will use NTLMv2 authentication;
+	use NTLMv2 session security if the server supports it. Domain controllers accept LM,
+	NTLM, and NTLMv2 authentication.
+	</para>
+
+	<para>
+		<screen>
+		[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
+		"NtlmMinClientSec"=dword:00080000
+		</screen>
+	</para>
+
+	<para>
+	The value 0x00080000 means permit only NTLMv2 session security. If either NtlmMinClientSec or
+	NtlmMinServerSec is set to 0x00080000, the connection will fail if NTLMv2
+	session security is negotiated.
+	</para>
+	</sect2>
+</sect1>
+
+<sect1>
+<title>Upgrading Samba</title>
+
+<para>
+<indexterm><primary>updates</primary></indexterm>
+<indexterm><primary>important announcements</primary></indexterm>
+<indexterm><primary>security vulnerability</primary></indexterm>
+Please check regularly on <ulink noescape="1" url="http://www.samba.org/">http://www.samba.org/</ulink> for
+updates and important announcements. Occasionally security releases are made, and it is highly recommended to
+upgrade Samba promptly when a security vulnerability is discovered. Check with your OS vendor for OS-specific
+upgrades.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+If all Samba and host platform configurations were really as intuitive as one might like them to be, this
+chapter would not be necessary. Security issues are often vexing for a support person to resolve, not because
+of the complexity of the problem, but because most administrators who post what turns out to be a security
+problem request are totally convinced that the problem is with Samba.
+</para>
+
+	<sect2>
+	<title>Smbclient Works on Localhost, but the Network Is Dead</title>
+
+	<para>
+	This is a common problem. Linux vendors tend to install a default firewall.
+	With the default firewall in place, only traffic on the loopback adapter (IP address 127.0.0.1)
+	is allowed through the firewall.
+	</para>
+
+	<para>
+	The solution is either to remove the firewall (stop it) or modify the firewall script to
+	allow SMB networking traffic through. See <link linkend="firewallports">the Using a 
+	Firewall</link> section.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Why Can Users Access Other Users' Home Directories?</title>
+
+	<para>
+	<quote>
+<indexterm><primary>mapping home directory</primary></indexterm>
+<indexterm><primary>own home directory</primary></indexterm>
+	We are unable to keep individual users from mapping to any other user's home directory once they have
+	supplied a valid password! They only need to enter their own password. I have not found any method to
+	configure Samba so that users may map only their own home directory.
+	</quote>
+	</para>
+
+	<para><quote>
+	User xyzzy can map his home directory. Once mapped, user xyzzy can also map anyone else's home directory.
+	</quote></para>
+
+	<para>
+<indexterm><primary>security flaw</primary></indexterm>
+<indexterm><primary>defined shares</primary></indexterm>
+	This is not a security flaw, it is by design. Samba allows users to have exactly the same access to the UNIX
+	file system as when they were logged on to the UNIX box, except that it only allows such views onto the file
+	system as are allowed by the defined shares.
+	</para>
+
+	<para>
+<indexterm><primary>UNIX home directories</primary></indexterm>
+<indexterm><primary>permissions</primary></indexterm>
+	If your UNIX home directories are set up so that one user can happily <command>cd</command>
+	into another user's directory and execute <command>ls</command>, the UNIX security solution is to change file
+	permissions on the user's home directories so that the <command>cd</command> and <command>ls</command> are denied.
+	</para>
+
+	<para>
+<indexterm><primary>security policies</primary></indexterm>
+<indexterm><primary>permissions</primary></indexterm>
+	Samba tries very hard not to second guess the UNIX administrator's security policies and
+	trusts the UNIX admin to set the policies and permissions he or she desires.
+	</para>
+
+	<para>
+	Samba allows the behavior you require. Simply put the <smbconfoption name="only user">%S</smbconfoption>
+	option in the <smbconfsection name="[homes]"/> share definition.
+	</para>
+
+	<para>
+	The <smbconfoption name="only user"></smbconfoption> works in conjunction with the <smbconfoption name="users">list</smbconfoption>,
+	so to get the behavior you require, add the line:
+	<smbconfblock>
+	<smbconfoption name="users">%S</smbconfoption>
+	</smbconfblock>
+	This is equivalent to adding
+	<smbconfblock>
+	<smbconfoption name="valid users">%S</smbconfoption>
+	</smbconfblock>
+	to the definition of the <smbconfsection name="[homes]"/> share, as recommended in
+	the &smb.conf; man page.
+	</para>
+	</sect2>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml b/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml
new file mode 100644
index 00000000000..8aea1775e35
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml
@@ -0,0 +1,833 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="ServerType">
+<chapterinfo>
+	&author.tridge;
+	&author.jelmer;
+	&author.jht;
+</chapterinfo>
+
+<title>Server Types and Security Modes</title>
+
+<para>
+<indexterm><primary>migrate</primary></indexterm>
+<indexterm><primary>security mode</primary></indexterm>
+This chapter provides information regarding the types of server that Samba may be configured to be. A
+Microsoft network administrator who wishes to migrate to or use Samba will want to know the meaning, within a
+Samba context, of terms familiar to the MS Windows administrator. This means that it is essential also to
+define how critical security modes function before we get into the details of how to configure the server
+itself.
+</para>
+
+<para>
+This chapter provides an overview of the security modes of which Samba is capable and how they relate to MS
+Windows servers and clients.
+</para>
+
+<para>
+A question often asked is, <quote>Why would I want to use Samba?</quote> Most chapters contain a section that
+highlights features and benefits. We hope that the information provided will help to answer this question. Be
+warned though, we want to be fair and reasonable, so not all features are positive toward Samba. The benefit
+may be on the side of our competition.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+Two men were walking down a dusty road, when one suddenly kicked up a small red stone. It
+hurt his toe and lodged in his sandal. He took the stone out and cursed it with a passion
+and fury befitting his anguish. The other looked at the stone and said, <quote>This is a garnet.
+I can turn that into a precious gem and some day it will make a princess very happy!</quote>
+</para>
+
+<para>
+The moral of this tale: Two men, two very different perspectives regarding the same stone.
+Like it or not, Samba is like that stone. Treat it the right way and it can bring great
+pleasure, but if you are forced to use it and have no time for its secrets, then it can be
+a source of discomfort.
+</para>
+
+<para>
+<indexterm><primary>UNIX</primary><secondary>server</secondary></indexterm>
+<indexterm><primary>interoperability</primary></indexterm>
+Samba started out as a project that sought to provide interoperability for MS Windows 3.x
+clients with a UNIX server. It has grown up a lot since its humble beginnings and now provides
+features and functionality fit for large-scale deployment. It also has some warts. In sections
+like this one, we tell of both.
+</para>
+
+<para>
+So, what are the benefits of the features mentioned in this chapter?
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
+	Samba-3 can replace an MS Windows NT4 domain controller.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>active directory</primary></indexterm>
+	Samba-3 offers excellent interoperability with MS Windows NT4-style
+	domains as well as natively with Microsoft Active Directory domains.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>interdomain</primary><secondary>trustrs</secondary></indexterm>
+	Samba-3 permits full NT4-style interdomain trusts.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>authentication</primary></indexterm>
+	<indexterm><primary>security</primary><secondary>modes</secondary></indexterm>
+	Samba has security modes that permit more flexible authentication
+	than is possible with MS Windows NT4 domain controllers.
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>account</primary><secondary>database</secondary><tertiary>backends</tertiary></indexterm>
+	<indexterm><primary>encrypted</primary></indexterm>
+	Samba-3 permits use of multiple concurrent account database backends.
+	(Encrypted passwords that are stored in the account database are in
+	formats that are unique to Windows networking).
+	</para></listitem>
+
+	<listitem><para>
+	<indexterm><primary>replicated</primary></indexterm>
+	The account database backends can be distributed
+	and replicated using multiple methods. This gives Samba-3
+	greater flexibility than MS Windows NT4 and in many cases a
+	significantly higher utility than Active Directory domains
+	with MS Windows 200x.
+	</para></listitem>
+</itemizedlist>
+
+</sect1>
+
+<sect1>
+<title>Server Types</title>
+
+
+<para>
+<indexterm><primary>Server Type</primary></indexterm>
+Administrators of Microsoft networks often refer to three different types of servers:
+</para>
+
+<itemizedlist>
+	<listitem><para>Domain Controller</para>
+		<itemizedlist>
+			<listitem><para>Primary Domain Controller (PDC)</para></listitem>
+			<listitem><para>Backup Domain Controller (BDC)</para></listitem>
+			<listitem><para>ADS Domain Controller</para></listitem>
+		</itemizedlist>
+	</listitem>
+	<listitem><para>Domain Member Server</para>
+		<itemizedlist>
+			<listitem><para>Active Directory Domain Server</para></listitem>
+			<listitem><para>NT4 Style Domain Domain Server</para></listitem>
+		</itemizedlist>
+	</listitem>
+	<listitem><para>Standalone Server</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>domain</primary><secondary>control</secondary></indexterm>
+<indexterm><primary>domain</primary><secondary>member</secondary></indexterm>
+<indexterm><primary>domain control</primary><secondary>primary</secondary></indexterm>
+<indexterm><primary>domain control</primary><secondary>backup</secondary></indexterm>
+The chapters covering domain control (<link linkend="samba-pdc">Domain Control</link>), 
+backup domain control (<link linkend="samba-bdc">Backup Domain Control</link>), and 
+domain membership (<link linkend="domain-member">Domain Membership</link>) provide
+pertinent information regarding Samba configuration for each of these server roles.
+You are strongly encouraged to become intimately familiar with these chapters because
+they lay the foundation for deployment of Samba domain security.
+</para>
+
+<para>
+<indexterm><primary>standalone</primary></indexterm>
+A Standalone server is autonomous in respect of the source of its account backend.
+Refer to <link linkend="StandAloneServer">Standalone Servers</link> to gain a wider appreciation
+of what is meant by a server being configured as a <emphasis>standalone</emphasis> server.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Samba Security Modes</title>
+
+
+<para>
+<indexterm><primary>Security Mode</primary></indexterm>
+<indexterm><primary>security</primary></indexterm>
+In this section, the function and purpose of Samba's security modes are described. An accurate understanding of
+how Samba implements each security mode as well as how to configure MS Windows clients for each mode will
+significantly reduce user complaints and administrator heartache.
+</para>
+
+<para>
+<indexterm><primary>Server Message Block</primary><see>SMB</see></indexterm>
+<indexterm><primary>Common Internet Filesystem</primary><see>CIFS</see></indexterm>
+Microsoft Windows networking uses a protocol that was originally called the Server Message Block (SMB)
+protocol. Since some time around 1996 the protocol has been better known as the Common Internet Filesystem
+(CIFS) protocol.
+</para>
+
+<para>
+<indexterm><primary>security levels</primary></indexterm>
+<indexterm><primary>security modes</primary></indexterm>
+<indexterm><primary>user-level</primary></indexterm>
+<indexterm><primary>share-level</primary></indexterm>
+In the SMB/CIFS networking world, there are only two types of security: <emphasis>user-level</emphasis> and
+<emphasis>share level</emphasis>. We refer to these collectively as <emphasis>security levels</emphasis>.  In
+implementing these two security levels, Samba provides flexibilities that are not available with MS Windows
+NT4/200x servers. In fact, Samba implements <emphasis>share-level</emphasis> security only one way, but has
+four ways of implementing <emphasis>user-level</emphasis> security. Collectively, we call the Samba
+implementations of the security levels <emphasis>security modes</emphasis>. They are known as
+<emphasis>share</emphasis>, <emphasis>user</emphasis>, <emphasis>domain</emphasis>, <emphasis>ADS</emphasis>,
+and <emphasis>server</emphasis> modes.  They are documented in this chapter.
+</para>
+
+<para>
+An SMB server informs the client, at the time of a session setup, the security level the server is running.
+There are two options: share-level and user-level. Which of these two the client receives affects the way the
+client then tries to authenticate itself. It does not directly affect (to any great extent) the way the Samba
+server does security. This may sound strange, but it fits in with the client/server approach of SMB.  In SMB
+everything is initiated and controlled by the client, and the server can only tell the client what is
+available and whether an action is allowed.
+</para>
+
+<para>
+The term <literal>client</literal> refers to all agents whether it is a Windows workstation, a Windows server,
+another Samba server, or any vanilla SMB or CIFS client application (e.g., <command>smbclient</command>) that
+make use of services provided by an SMB/CIFS server.
+</para>
+
+<sect2>
+<title>User Level Security</title>
+
+<para>
+<indexterm><primary>user-level</primary></indexterm>
+We describe user-level security first because its simpler.  In user-level security, the client sends a session
+setup request directly following protocol negotiation.  This request provides a username and password. The
+server can either accept or reject that username/password combination. At this stage the server has no idea
+what share the client will eventually try to connect to, so it can't base the
+<emphasis>accept/reject</emphasis> on anything other than:
+</para>
+
+<orderedlist>
+<listitem><para>the username/password.</para></listitem>
+<listitem><para>the name of the client machine.</para></listitem>
+</orderedlist>
+
+<para>
+<indexterm><primary>credentials</primary></indexterm>
+If the server accepts the username/password credentials, the client expects to be able to mount shares (using
+a <emphasis>tree connection</emphasis>) without further specifying a password. It expects that all access
+rights will be as the username/password credentials set that was specified in the initial <emphasis>session
+setup</emphasis>.
+</para>
+
+<para>
+<indexterm><primary>session setup</primary></indexterm>
+It is also possible for a client to send multiple <emphasis>session setup</emphasis>
+requests. When the server responds, it gives the client a <emphasis>uid</emphasis> to use
+as an authentication tag for that username/password. The client can maintain multiple
+authentication contexts in this way (WinDD is an example of an application that does this).
+</para>
+
+<para>
+<indexterm><primary>LanManager</primary></indexterm>
+<indexterm><primary>case-preserving</primary></indexterm>
+<indexterm><primary>case-insensitive</primary></indexterm>
+<indexterm><primary>upper-case</primary></indexterm>
+<indexterm><primary>lower-case</primary></indexterm>
+Windows networking user account names are case-insensitive, meaning that upper-case and lower-case characters
+in the account name are considered equivalent. They are said to be case-preserving, but not case significant.
+Windows and LanManager systems previous to Windows NT version 3.10 have case-insensitive passwords that were
+not necessarilty case-preserving. All Windows NT family systems treat passwords as case-preserving and
+case-sensitive.
+</para>
+
+<sect3>
+<title>Example Configuration</title>
+
+<para>
+The &smb.conf; parameter that sets user-level security is:
+</para>
+
+<para><smbconfblock>
+<smbconfoption name="security">user</smbconfoption>
+</smbconfblock></para>
+
+<para>
+This is the default setting since Samba-2.2.x.
+</para>
+
+</sect3>
+
+</sect2>
+<sect2>
+<title>Share-Level Security</title>
+
+<para>
+<indexterm><primary>share-level</primary></indexterm>
+<indexterm><primary>mount</primary></indexterm>
+In share-level security, the client authenticates itself separately for each share. It sends a password along
+with each tree connection request (share mount), but it does not explicitly send a username with this
+operation. The client expects a password to be associated with each share, independent of the user. This means
+that Samba has to work out what username the client probably wants to use, the SMB server is not explicitly
+sent the username.  Some commercial SMB servers such as NT actually associate passwords directly with shares
+in share-level security, but Samba always uses the UNIX authentication scheme where it is a username/password
+pair that is authenticated, not a share/password pair.
+</para>
+
+<para>
+To understand the MS Windows networking parallels, think in terms of MS Windows 9x/Me where you can create a
+shared folder that provides read-only or full access, with or without a password.
+</para>
+
+<para>
+Many clients send a session setup request even if the server is in share-level security. They normally send a valid
+username but no password. Samba records this username in a list of possible usernames. When the client then
+issues a tree connection request, it also adds to this list the name of the share they try to connect to (useful for
+home directories) and any users listed in the <smbconfoption name="user"/> parameter in the &smb.conf; file.
+The password is then checked in turn against these possible usernames. If a match is found, then the client is
+authenticated as that user.
+</para>
+
+<para>
+<indexterm><primary>name service switch</primary><see>NSS</see></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>nsswitch.conf</primary></indexterm>
+Where the list of possible user names is not provided, Samba makes a UNIX system call to find the user
+account that has a password that matches the one provided from the standard account database. On a system that
+has no name service switch (NSS) facility, such lookups will be from the <filename>/etc/passwd</filename>
+database. On NSS enabled systems, the lookup will go to the libraries that have been specified in the
+<filename>nsswitch.conf</filename> file. The entries in that file in which the libraries are specified are:
+<screen>
+passwd: files nis ldap
+shadow: files nis ldap
+group: files nis ldap
+</screen>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>/etc/group</primary></indexterm>
+<indexterm><primary>NIS</primary></indexterm>
+In the example shown here (not likely to be used in practice) the lookup will check
+<filename>/etc/passwd</filename> and <filename>/etc/group</filename>, if not found it will check NIS, then
+LDAP.
+</para>
+
+<sect3>
+<title>Example Configuration</title>
+
+<para>
+The &smb.conf; parameter that sets share-level security is:
+</para>
+
+<para><smbconfblock>
+<smbconfoption name="security">share</smbconfoption>
+</smbconfblock></para>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>Domain Security Mode (User-Level Security)</title>
+
+<para>
+<indexterm><primary>domain</primary><secondary>controllers</secondary></indexterm>
+<indexterm><primary>security</primary><secondary>controllers</secondary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>logon</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+Domain security provides a mechanism for storing all user and group accounts in a central, shared, account
+repository. The centralized account repository is shared between domain (security) controllers. Servers that
+act as domain controllers provide authentication and validation services to all machines that participate in
+the security context for the domain. A primary domain controller (PDC) is a server that is responsible for
+maintaining the integrity of the security account database. Backup domain controllers (BDCs) provide only domain
+logon and authentication services. Usually, BDCs will answer network logon requests more responsively than
+will a PDC.
+</para>
+
+<para>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>trust account</primary></indexterm>
+<indexterm><primary>trust</primary><secondary>account</secondary></indexterm>
+<indexterm><primary>domain</primary><secondary>security</secondary></indexterm>
+<indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
+When Samba is operating in <smbconfoption name="security">domain</smbconfoption> mode, the Samba server has a
+domain security trust account (a machine account) and causes all authentication requests to be passed through
+to the domain controllers.  In other words, this configuration makes the Samba server a domain member server,
+even when it is in fact acting as a domain controller. All machines that participate in domain security must
+have a machine account in the security database.
+</para>
+
+<para>
+<indexterm><primary>account</primary><secondary>database</secondary></indexterm>
+<indexterm><primary>machine</primary><secondary>account</secondary></indexterm>
+<indexterm><primary>NetBIOS</primary><secondary>name</secondary></indexterm>
+<indexterm><primary>NetBIOS</primary></indexterm>
+Within the domain security environment, the underlying security architecture uses user-level security. Even
+machines that are domain members must authenticate on startup. The machine account consists of an account
+entry in the accounts database, the name of which is the NetBIOS name of the machine and of which the password
+is randomly generated and known to both the domain controllers and the member machine. If the machine account
+cannot be validated during startup, users will not be able to log on to the domain using this machine because
+it cannot be trusted. The machine account is referred to as a machine trust account.
+</para>
+
+<para>
+There are three possible domain member configurations:
+</para>
+
+<orderedlist>
+	<listitem><para>Primary domain controller (PDC) - of which there is one per domain.</para></listitem>
+	<listitem><para>Backup domain controller (BDC) - of which there can be any number per domain.</para></listitem>
+	<listitem><para>Domain member server (DMS) - of which there can be any number per domain.</para></listitem>
+</orderedlist>
+
+<para>
+<indexterm><primary>DMS</primary></indexterm>
+We will discuss each of these in separate chapters. For now, we are most interested in basic DMS
+configuration.
+</para>
+
+<sect3>
+<title>Example Configuration</title>
+<para><emphasis>
+Samba as a Domain Member Server
+</emphasis></para>
+
+
+<para>
+<indexterm><primary>server type</primary><secondary>domain member</secondary></indexterm>
+This method involves addition of the following parameters in the &smb.conf; file:
+<smbconfblock>
+<smbconfoption name="security">domain</smbconfoption>
+<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
+</smbconfblock>
+</para>
+
+<para>
+In order for this method to work, the Samba server needs to join the MS Windows NT
+security domain. This is done as follows:
+<indexterm><primary>net</primary><secondary>rpc</secondary></indexterm>
+<indexterm><primary>Domain Member</primary><secondary>joining</secondary></indexterm>
+</para>
+
+
+<procedure>
+        <step><para>On the MS Windows NT domain controller, using
+        the Server Manager, add a machine account for the Samba server.
+        </para></step>
+
+        <step><para>On the UNIX/Linux system execute:</para>
+	
+			<para><screen>&rootprompt;<userinput>net rpc join -U administrator%password</userinput></screen></para>
+		</step>
+</procedure>
+
+<note><para>
+<indexterm><primary>smbpasswd</primary></indexterm>
+Samba-2.2.4 and later Samba 2.2.x series releases can autojoin a Windows NT4-style domain just by executing:
+<screen>
+&rootprompt;<userinput>smbpasswd -j <replaceable>DOMAIN_NAME</replaceable> -r <replaceable>PDC_NAME</replaceable> \
+	 -U Administrator%<replaceable>password</replaceable></userinput>
+</screen>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+Samba-3 can do the same by executing:
+<screen>
+&rootprompt;<userinput>net rpc join -U Administrator%<replaceable>password</replaceable></userinput>
+</screen>
+It is not necessary with Samba-3 to specify the <replaceable>DOMAIN_NAME</replaceable> or the
+<replaceable>PDC_NAME</replaceable>, as it figures this out from the &smb.conf; file settings.
+</para></note>
+
+<para>
+<indexterm><primary>invalid shell</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>/bin/false</primary></indexterm>
+Use of this mode of authentication requires there to be a standard UNIX account for each user in order to
+assign a UID once the account has been authenticated by the Windows domain controller. This account can be
+blocked to prevent logons by clients other than MS Windows through means such as setting an invalid shell in
+the <filename>/etc/passwd</filename> entry. The best way to allocate an invalid shell to a user account is to
+set the shell to the file <filename>/bin/false</filename>.
+</para>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+Domain controllers can be located anywhere that is convenient. The best advice is to have a BDC on every
+physical network segment, and if the PDC is on a remote network segment the use of WINS (see <link
+linkend="NetworkBrowsing">Network Browsing</link> for more information) is almost essential.
+</para>
+
+<para>
+An alternative to assigning UIDs to Windows users on a Samba member server is presented in <link
+linkend="winbind">Winbind</link>, <link linkend="winbind">Winbind: Use of Domain Accounts</link>.
+</para>
+
+<para>
+For more information regarding domain membership, <link linkend="domain-member">Domain Membership</link>.
+</para>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>ADS Security Mode (User-Level Security)</title>
+
+<para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>native mode</primary></indexterm>
+Both Samba-2.2, and Samba-3 can join an Active Directory domain using NT4 style RPC based security.  This is
+possible if the domain is run in native mode. Active Directory in native mode perfectly allows NT4-style
+domain members. This is contrary to popular belief.
+</para>
+
+<para>
+If you are using Active Directory, starting with Samba-3 you can join as a native AD member. Why would you
+want to do that?  Your security policy might prohibit the use of NT-compatible authentication protocols. All
+your machines are running Windows 2000 and above and all use Kerberos. In this case, Samba, as an NT4-style
+domain, would still require NT-compatible authentication data. Samba in AD-member mode can accept Kerberos
+tickets.
+</para>
+
+<para>
+<indexterm><primary>realm</primary></indexterm>
+<indexterm><primary>mixed mode</primary></indexterm>
+Sites that use Microsoft Windows active directory services (ADS) should be aware of the significance of the
+terms: <literal>native mode</literal> and <literal>mixed mode</literal> ADS operation. The term
+<literal>realm</literal> is used to describe a Kerberos-based security architecture (such as is used by
+Microsoft ADS).
+</para>
+
+<sect3>
+<title>Example Configuration</title>
+
+<para><smbconfblock>
+<smbconfoption name="realm">your.kerberos.REALM</smbconfoption>
+<smbconfoption name="security">ADS</smbconfoption>
+</smbconfblock></para>
+
+<para>
+The following parameter may be required:
+</para>
+
+<para><smbconfblock>
+<smbconfoption name="password server">your.kerberos.server</smbconfoption>
+</smbconfblock></para>
+
+<para>
+Please refer to <link linkend="domain-member">Domain Membership</link>, and <link linkend="ads-member">Samba
+ADS Domain Membership</link> for more information regarding this configuration option.
+</para>
+
+</sect3>
+</sect2>
+
+<sect2>
+<title>Server Security (User Level Security)</title>
+
+<para>
+Server security mode is left over from the time when Samba was not capable of acting
+as a domain member server. It is highly recommended not to use this feature. Server
+security mode has many drawbacks that include:
+</para>
+
+<itemizedlist>
+	<listitem><para>Potential account lockout on MS Windows NT4/200x password servers.</para></listitem>
+	<listitem><para>Lack of assurance that the password server is the one specified.</para></listitem>
+	<listitem><para>Does not work with Winbind, which is particularly needed when storing profiles remotely.</para></listitem>
+	<listitem><para>This mode may open connections to the password server and keep them open for extended periods.</para></listitem>
+	<listitem><para>Security on the Samba server breaks badly when the remote password server suddenly shuts down.</para></listitem>
+	<listitem><para>With this mode there is NO security account in the domain that the password server belongs to for the Samba server.</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>session setup</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+In server security mode the Samba server reports to the client that it is in user-level security. The client
+then does a session setup as described earlier.  The Samba server takes the username/password that the client
+sends and attempts to log into the <smbconfoption name="password server"/> by sending exactly the same
+username/password that it got from the client. If that server is in user-level security and accepts the
+password, then Samba accepts the client's connection. This parameter allows the Samba server to use another
+SMB server as the <smbconfoption name="password server"/>.
+</para>
+
+<para>
+<indexterm><primary>security level</primary></indexterm>
+<indexterm><primary>encryption</primary></indexterm>
+You should also note that at the start of all this, when the server tells the client
+what security level it is in, it also tells the client if it supports encryption. If it
+does, it supplies the client with a random cryptkey. The client will then send all
+passwords in encrypted form. Samba supports this type of encryption by default.
+</para>
+
+<para>
+The parameter <smbconfoption name="security">server</smbconfoption> means that Samba reports to clients that
+it is running in <emphasis>user mode</emphasis> but actually passes off all authentication requests to another
+user mode server. This requires an additional parameter <smbconfoption name="password server"/> that points to
+the real authentication server.  The real authentication server can be another Samba server, or it can be a
+Windows NT server, the latter being natively capable of encrypted password support.
+</para>
+
+<note><para>
+<indexterm><primary>password server</primary></indexterm>
+<indexterm><primary>workgroup</primary></indexterm>
+When Samba is running in <emphasis>server security mode</emphasis>, it is essential that the parameter
+<emphasis>password server</emphasis> is set to the precise NetBIOS machine name of the target authentication
+server. Samba cannot determine this from NetBIOS name lookups because the choice of the target authentication
+server is arbitrary and cannot be determined from a domain name. In essence, a Samba server that is in
+<emphasis>server security mode</emphasis> is operating in what used to be known as workgroup mode.
+</para></note>
+
+<sect3>
+<title>Example Configuration</title>
+<para><emphasis>
+Using MS Windows NT as an Authentication Server
+</emphasis></para>
+
+<para>
+This method involves the additions of the following parameters in the &smb.conf; file:
+</para>
+
+<para><smbconfblock>
+<smbconfoption name="encrypt passwords">Yes</smbconfoption>
+<smbconfoption name="security">server</smbconfoption>
+<smbconfoption name="password server">"NetBIOS_name_of_a_DC"</smbconfoption>
+</smbconfblock></para>
+
+
+<para>
+There are two ways of identifying whether or not a username and password pair is valid.
+One uses the reply information provided as part of the authentication messaging
+process, the other uses just an error code.
+</para>
+
+<para>
+<indexterm><primary>bogus</primary></indexterm>
+<indexterm><primary>lockout</primary></indexterm>
+The downside of this mode of configuration is that for security reasons Samba
+will send the password server a bogus username and a bogus password, and if the remote
+server fails to reject the bogus username and password pair, then an alternative mode of
+identification or validation is used. Where a site uses password lockout, after a
+certain number of failed authentication attempts, this will result in user lockouts.
+</para>
+
+<para>
+Use of this mode of authentication requires a standard UNIX account for the user.
+This account can be blocked to prevent logons by non-SMB/CIFS clients.
+</para>
+
+</sect3>
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Password Checking</title>
+
+<para>
+MS Windows clients may use encrypted passwords as part of a challenge/response
+authentication model (a.k.a. NTLMv1 and NTLMv2) or alone, or clear-text strings for simple
+password-based authentication. It should be realized that with the SMB protocol,
+the password is passed over the network either in plaintext or encrypted, but
+not both in the same authentication request.
+</para>
+
+<para>
+<indexterm><primary>encrypted passwords</primary></indexterm>
+<indexterm><primary>encrypted</primary></indexterm>
+When encrypted passwords are used, a password that has been entered by the user
+is encrypted in two ways:
+</para>
+
+<itemizedlist>
+        <listitem><para>An MD4 hash of the unicode of the password
+        string. This is known as the NT hash.
+        </para></listitem>
+
+        <listitem><para>The password is converted to uppercase,
+        and then padded or truncated to 14 bytes. This string is
+        then appended with 5 bytes of NULL characters and split to
+        form two 56-bit DES keys to encrypt a "magic" 8-byte value.
+        The resulting 16 bytes form the LanMan hash.
+        </para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>plain-text</primary><secondary>passwords</secondary></indexterm>
+MS Windows 95 pre-service pack 1 and MS Windows NT versions 3.x and version 4.0 pre-service pack 3 will use
+either mode of password authentication. All versions of MS Windows that follow these versions no longer
+support plain-text passwords by default.
+</para>
+
+<para>
+<indexterm><primary>cached</primary><secondary>password</secondary></indexterm>
+MS Windows clients have a habit of dropping network mappings that have been idle
+for 10 minutes or longer. When the user attempts to use the mapped drive
+connection that has been dropped, the client re-establishes the connection using
+a cached copy of the password.
+</para>
+
+<para>
+When Microsoft changed the default password mode, support was dropped for caching
+of the plaintext password. This means that when the registry parameter is changed
+to re-enable use of plaintext passwords, it appears to work, but when a dropped
+service connection mapping attempts to revalidate, this will fail if the remote
+authentication server does not support encrypted passwords. It is definitely not
+a good idea to re-enable plaintext password support in such clients.
+</para>
+
+<para>
+The following parameters can be used to work around the issue of Windows 9x/Me clients
+uppercasing usernames and passwords before transmitting them to the SMB server
+when using clear-text authentication:
+</para>
+
+
+<?latex \newpage ?>
+<smbconfblock>
+<smbconfoption name="password level"><replaceable>integer</replaceable></smbconfoption>
+<smbconfoption name="username level"><replaceable>integer</replaceable></smbconfoption>
+</smbconfblock>
+
+<para>
+By default Samba will convert to lowercase the username before attempting to lookup the user
+in the database of local system accounts. Because UNIX usernames conventionally
+only contain lowercase characters, the <smbconfoption name="username-level"/> parameter
+is rarely needed.
+</para>
+
+<para>
+<indexterm><primary>clear-text</primary></indexterm>
+However, passwords on UNIX systems often make use of mixed-case characters.  This means that in order for a
+user on a Windows 9x/Me client to connect to a Samba server using clear-text authentication, the
+<smbconfoption name="password level"/> must be set to the maximum number of uppercase letters that
+<emphasis>could</emphasis> appear in a password. Note that if the Server OS uses the traditional DES version
+of crypt(), a <smbconfoption name="password level"/> of 8 will result in case-insensitive passwords as seen
+from Windows users. This will also result in longer login times because Samba has to compute the permutations
+of the password string and try them one by one until a match is located (or all combinations fail).
+</para>
+
+<para>
+The best option to adopt is to enable support for encrypted passwords wherever
+Samba is used. Most attempts to apply the registry change to re-enable plaintext
+passwords will eventually lead to user complaints and unhappiness.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+We all make mistakes. It is okay to make mistakes, as long as they are made in the right places
+and at the right time. A mistake that causes lost productivity is seldom tolerated; however, a mistake
+made in a developmental test lab is expected.
+</para>
+
+<para>
+Here we look at common mistakes and misapprehensions that have been the subject of discussions
+on the Samba mailing lists. Many of these are avoidable by doing your homework before attempting
+a Samba implementation. Some are the result of a misunderstanding of the English language,
+which has many phrases that are potentially vague and may be highly confusing
+to those for whom English is not their native tongue.
+</para>
+
+<sect2>
+<title>What Makes Samba a Server?</title>
+
+<para>
+To some, the nature of the Samba security mode is obvious, but entirely
+wrong all the same. It is assumed that <smbconfoption name="security">server</smbconfoption> means that Samba
+will act as a server. Not so! This setting means that Samba will <emphasis>try</emphasis>
+to use another SMB server as its source for user authentication alone.
+</para>
+
+<para>
+Samba is a server regardless of which security mode is chosen. When Samba is used outside of a domain security
+context, it is best to leave the security mode at the default setting. By default Samba-3 uses user-mode
+security.
+</para>
+
+</sect2>
+
+<sect2>
+<title>What Makes Samba a Domain Controller?</title>
+
+<para>
+<indexterm><primary>server-mode</primary></indexterm>
+The &smb.conf; parameter <smbconfoption name="security">domain</smbconfoption> does not really make Samba behave
+as a domain controller. This setting means we want Samba to be a domain member. See <link
+linkend="samba-pdc">Samba as a PDC</link> for more information.
+</para>
+
+</sect2>
+
+<sect2>
+<title>What Makes Samba a Domain Member?</title>
+
+<para>
+Guess! So many others do. But whatever you do, do not think that <smbconfoption name="security">user</smbconfoption>
+makes Samba act as a domain member. Read the manufacturer's manual before the warranty expires. See 
+<link linkend="domain-member">Domain Membership</link>, for more information.
+</para>
+
+</sect2>
+
+
+<sect2>
+<title>Constantly Losing Connections to Password Server</title>
+
+<para><quote>
+Why does server_validate() simply give up rather than re-establish its connection to the
+password server?  Though I am not fluent in the SMB protocol, perhaps the cluster server
+process passes along to its client workstation the session key it receives from the password
+server, which means the password hashes submitted by the client would not work on a subsequent
+connection whose session key would be different. So server_validate() must give up.
+</quote></para>
+
+<para>
+Indeed. That's why <smbconfoption name="security">server</smbconfoption>
+is at best a nasty hack. Please use <smbconfoption name="security">domain</smbconfoption>;
+<smbconfoption name="security">server</smbconfoption> mode is also known as pass-through authentication.
+</para>
+
+</sect2>
+
+<sect2>
+<title>Stand-alone Server is converted to Domain Controller &smbmdash; Now User accounts don't work</title>
+
+<para><quote>
+When I try to log in to the DOMAIN, the eventlog shows <emphasis>tried credentials DOMAIN/username; effective
+credentials SERVER/username</emphasis>
+</quote></para>
+
+<para>
+Usually this is due to a user or machine account being created before the Samba server is configured to be a
+domain controller. Accounts created before the server becomes a domain controller will be
+<emphasis>local</emphasis> accounts and authenticated as what looks like a member in the SERVER domain, much
+like local user accounts in Windows 2000 and later.  Accounts created after the Samba server becomes a domain
+controller will be <emphasis>domain</emphasis> accounts and will be authenticated as a member of the DOMAIN
+domain.
+</para>
+
+<para>
+This can be verified by issuing the command <command>pdbedit -L -v username</command>.  If this reports DOMAIN
+then the account is a domain account, if it reports SERVER then the account is a local account.
+</para>
+
+<para>
+The easiest way to resolve this is to remove and recreate the account; however this may cause problems with
+established user profiles. You can also use <command>pdbedit -u username -I DOMAIN</command>. You may also
+need to change the User SID and Primary Group SID to match the domain.
+</para>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml
new file mode 100644
index 00000000000..18a15ae092c
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml
@@ -0,0 +1,327 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="speed">
+
+<chapterinfo>
+	<author>
+		<firstname>Paul</firstname><surname>Cochrane</surname>
+		<affiliation>
+			<orgname>Dundee Limb Fitting Centre</orgname>
+			<address><email>paulc@dth.scot.nhs.uk</email></address>
+		</affiliation>
+	</author>
+	&author.jelmer;
+	&author.jht;
+</chapterinfo>
+
+<title>Samba Performance Tuning</title>
+
+<sect1>
+<title>Comparisons</title>
+
+<para>
+The Samba server uses TCP to talk to the client, so if you are
+trying to see if it performs well, you should really compare it to
+programs that use the same protocol. The most readily available
+programs for file transfer that use TCP are ftp or another TCP-based
+SMB server.
+</para>
+
+<para>
+If you want to test against something like an NT or Windows for Workgroups server, then
+you will have to disable all but TCP on either the client or
+server. Otherwise, you may well be using a totally different protocol
+(such as NetBEUI) and comparisons may not be valid.
+</para>
+
+<para>
+Generally, you should find that Samba performs similarly to ftp at raw
+transfer speed. It should perform quite a bit faster than NFS,
+although this depends on your system.
+</para>
+
+<para>
+Several people have done comparisons between Samba and Novell, NFS, or
+Windows NT. In some cases Samba performed the best, in others the worst. I
+suspect the biggest factor is not Samba versus some other system, but the
+hardware and drivers used on the various systems. Given similar
+hardware, Samba should certainly be competitive in speed with other
+systems.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Socket Options</title>
+
+<para>
+There are a number of socket options that can greatly affect the
+performance of a TCP-based server like Samba.
+</para>
+
+<para>
+The socket options that Samba uses are settable both on the command
+line with the <option>-O</option> option and in the &smb.conf; file.
+</para>
+
+<para>
+The <smbconfoption name="socket options"/> section of the &smb.conf; manual page describes how
+to set these and gives recommendations.
+</para>
+
+<para>
+Getting the socket options correct can make a big difference to your
+performance, but getting them wrong can degrade it by just as
+much. The correct settings are very dependent on your local network.
+</para>
+
+<para>
+The socket option TCP_NODELAY is the one that seems to make the biggest single difference
+for most networks. Many people report that adding
+<smbconfoption name="socket options">TCP_NODELAY</smbconfoption>
+doubles the read performance of a Samba drive. The best explanation I have seen for
+this is that the Microsoft TCP/IP stack is slow in sending TCP ACKs.
+</para>
+
+<para>
+There have been reports that setting <parameter>socket options = SO_RCVBUF=8192</parameter> in smb.conf
+can seriously degrade Samba performance on the loopback adaptor (IP Address 127.0.0.1). It is strongly
+recommended that before specifying any settings for <parameter>socket options</parameter>, the effect
+first be quantitatively measured on the server being configured.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Read Size</title>
+
+<para>
+The option <smbconfoption name="read size"/> affects the overlap of disk
+reads/writes with network reads/writes. If the amount of data being
+transferred in several of the SMB commands (currently SMBwrite, SMBwriteX, and
+SMBreadbraw) is larger than this value, then the server begins writing
+the data before it has received the whole packet from the network, or
+in the case of SMBreadbraw, it begins writing to the network before
+all the data has been read from disk.
+</para>
+
+<para>
+This overlapping works best when the speeds of disk and network access
+are similar, having little effect when the speed of one is much
+greater than the other.
+</para>
+
+<para>
+The default value is 16384, but little experimentation has been
+done as yet to determine the optimal value, and it is likely that the best
+value will vary greatly between systems anyway. A value over 65536 is
+pointless and will cause you to allocate memory unnecessarily.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Max Xmit</title>
+
+<para>
+	At startup the client and server negotiate a <parameter>maximum transmit</parameter> size,
+which limits the size of nearly all SMB commands. You can set the
+maximum size that Samba will negotiate using the <smbconfoption name="max xmit"/> option
+in &smb.conf;. Note that this is the maximum size of SMB requests that 
+Samba will accept, but not the maximum size that the client will accept.
+The client maximum receive size is sent to Samba by the client, and Samba
+honors this limit.
+</para>
+
+<para>
+It defaults to 65536 bytes (the maximum), but it is possible that some
+clients may perform better with a smaller transmit unit. Trying values
+of less than 2048 is likely to cause severe problems.
+In most cases the default is the best option.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Log Level</title>
+
+<para>
+If you set the log level (also known as <smbconfoption name="debug level"/>) higher than 2,
+then you may suffer a large drop in performance. This is because the
+server flushes the log file after each operation, which can be quite
+expensive. 
+</para>
+</sect1>
+
+<sect1>
+<title>Read Raw</title>
+
+<para>
+The <smbconfoption name="read raw"/> operation is designed to be an optimized, low-latency
+file read operation. A server may choose to not support it,
+however, and Samba makes support for <smbconfoption name="read raw"/> optional, with it
+being enabled by default.
+</para>
+
+<para>
+In some cases clients do not handle <smbconfoption name="read raw"/> very well and actually
+get lower performance using it than they get using the conventional
+read operations, so you might like to try <smbconfoption name="read raw">no</smbconfoption> and see what happens on your
+network. It might lower, raise, or not affect your performance. Only
+testing can really tell.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Write Raw</title>
+
+<para>
+The <smbconfoption name="write raw"/> operation is designed to be an optimized, low-latency
+file write operation. A server may choose to not support it, however, and Samba makes support for
+<smbconfoption name="write raw"/> optional, with it being enabled by default.
+</para>
+
+<para>
+Some machines may find <smbconfoption name="write raw"/> slower than normal write, in which
+case you may wish to change this option.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Slow Logins</title>
+
+<para>
+Slow logins are almost always due to the password checking time. Using
+the lowest practical <smbconfoption name="password level"/> will improve things. 
+</para>
+
+</sect1>
+
+<sect1>
+<title>Client Tuning</title>
+
+<para>
+Often a speed problem can be traced to the client. The client (for
+example Windows for Workgroups) can often be tuned for better TCP
+performance. Check the sections on the various clients in 
+<link linkend="Other-Clients">Samba and Other CIFS Clients</link>.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Samba Performance Problem Due to Changing Linux Kernel</title>
+
+<para>
+A user wrote the following to the mailing list:
+</para>
+
+<blockquote>
+<para>
+<indexterm><primary>Gentoo</primary></indexterm>
+<indexterm><primary>slow network</primary></indexterm>
+I am running Gentoo on my server and Samba 2.2.8a. Recently I changed kernel versions from
+<filename>linux-2.4.19-gentoo-r10</filename> to <filename>linux-2.4.20-wolk4.0s</filename>. Now I have a
+performance issue with Samba.  Many of you will probably say,  <quote>Move to vanilla sources!</quote> Well, I
+tried that and it didn't work. I have a 100MB LAN and two computers (Linux and Windows 2000). The Linux server
+shares directories with DivX files, the client (Windows 2000) plays them via LAN. Before, when I was running
+the 2.4.19 kernel, everything was fine, but now movies freeze and stop. I tried moving files between the
+server and Windows, and it is terribly slow.
+</para>
+</blockquote>
+
+<para>
+The answer he was given is:
+</para>
+
+<blockquote>
+<para>
+<indexterm><primary>ifconfig</primary></indexterm>
+<indexterm><primary>framing error</primary></indexterm>
+<indexterm><primary>collisions</primary></indexterm>
+Grab the mii-tool and check the duplex settings on the NIC.  My guess is that it is a link layer issue, not an
+application layer problem. Also run ifconfig and verify that the framing error, collisions, and so on, look
+normal for ethernet.
+</para>
+</blockquote>
+
+</sect1>
+
+<sect1>
+<title>Corrupt tdb Files</title>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>mbd kept spawning</primary></indexterm>
+<indexterm><primary>/var/locks/*.tdb</primary></indexterm>
+Our Samba PDC server has been hosting three TB of data to our 500+ users [Windows NT/XP]  for the last three
+years using Samba without a problem.  Today all shares went very slow. Also, the main smbd kept spawning new
+processes, so we had 1600+ running SMDB's (normally we average 250).  It crashed the SUN E3500 cluster twice.
+After a lot of searching, I decided to <command>rm /var/locks/*.tdb</command>. Happy again.
+</para>
+
+<para>
+<emphasis>Question:</emphasis> Is there any method of keeping the *.tdb files in top condition, or
+how can I detect early corruption?
+</para>
+
+<para>
+<indexterm><primary>tdbbackup</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<emphasis>Answer:</emphasis> Yes, run <command>tdbbackup</command> each time after stopping nmbd and before starting nmbd.
+</para>
+
+<para>
+<emphasis>Question:</emphasis> What I also would like to mention is that the service latency seems
+a lot lower than before the locks cleanup. Any ideas on keeping it top notch?
+</para>
+
+<para>
+<emphasis>Answer:</emphasis> Yes. Same answer as for previous question!
+</para>
+
+</sect1>
+
+<sect1>
+<title>Samba Performance is Very Slow</title>
+
+<para>
+<indexterm><primary>slow performance</primary></indexterm>
+A site reported experiencing very baffling symptoms with MYOB Premier opening and
+accessing its data files. Some  operations on the file would take between 40 and
+45 seconds.
+</para>
+
+<para>
+<indexterm><primary>printer monitor</primary></indexterm>
+<indexterm><primary>pauses</primary></indexterm>
+It turned out that the printer monitor program running on the Windows
+clients was causing the problems. From the logs, we saw activity coming
+through with pauses of about 1 second.
+</para>
+
+<para>
+<indexterm><primary>networks access</primary></indexterm>
+<indexterm><primary>printing now</primary></indexterm>
+Stopping the monitor software resulted in the networks access at normal
+(quick) speed. Restarting the program caused the speed to slow down
+again. The printer was a Canon LBP-810 and the relevant task was
+something like CAPON (not sure on spelling). The monitor software
+displayed a "printing now" dialog on the client during printing.
+</para>
+
+<para>
+We discovered this by starting with a clean install of Windows and
+trying the application at every step of the installation of other software
+process (we had to do this many times).
+</para>
+
+<para>
+Moral of the story: Check everything (other software included)!
+</para>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-StandAloneServer.xml b/docs-xml/Samba3-HOWTO/TOSHARG-StandAloneServer.xml
new file mode 100644
index 00000000000..895544ed226
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-StandAloneServer.xml
@@ -0,0 +1,341 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="StandAloneServer">
+<chapterinfo>
+	&author.jht;
+</chapterinfo>
+<title>Standalone Servers</title>
+
+<para>
+<indexterm><primary>standalone server</primary></indexterm>
+<indexterm><primary>not domain members</primary></indexterm>
+<indexterm><primary>minimum security control</primary></indexterm>
+Standalone servers are independent of domain controllers on the network.
+They are not domain members and function more like workgroup servers. In many
+cases a standalone server is configured with a minimum of security control
+with the intent that all data served will be readily accessible to all users.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>secure</primary></indexterm>
+<indexterm><primary>insecure</primary></indexterm>
+Standalone servers can be as secure or as insecure as needs dictate. They can
+have simple or complex configurations. Above all, despite the hoopla about
+domain security, they remain a common installation.
+</para>
+
+<para>
+<indexterm><primary>read-only files</primary></indexterm>
+<indexterm><primary>share-mode</primary></indexterm>
+<indexterm><primary>read-only</primary></indexterm>
+<indexterm><primary>standalone server</primary></indexterm>
+If all that is needed is a server for read-only files, or for
+printers alone, it may not make sense to effect a complex installation.
+For example, a drafting office needs to store old drawings and reference
+standards. Noone can write files to the server because it is legislatively
+important that all documents remain unaltered. A share-mode read-only standalone
+server is an ideal solution.
+</para>
+
+<para>
+<indexterm><primary>simplicity</primary></indexterm>
+<indexterm><primary>printers</primary></indexterm>
+<indexterm><primary>share-mode server</primary></indexterm>
+Another situation that warrants simplicity is an office that has many printers
+that are queued off a single central server. Everyone needs to be able to print
+to the printers, there is no need to effect any access controls, and no files will
+be served from the print server. Again, a share-mode standalone server makes
+a great solution.
+</para>
+</sect1>
+
+<sect1>
+<title>Background</title>
+
+<para>
+<indexterm><primary>standalone server</primary></indexterm>
+<indexterm><primary>local authentication</primary></indexterm>
+<indexterm><primary>access control</primary></indexterm>
+The term <emphasis>standalone server</emphasis> means that it will provide local authentication and access
+control for all resources that are available from it. In general this means that there will be a local user
+database. In more technical terms, it means resources on the machine will be made available in either
+<emphasis>share</emphasis> mode or in <emphasis>user</emphasis> mode.
+</para>
+
+<para>
+<indexterm><primary>create user accounts</primary></indexterm>
+<indexterm><primary>no network logon service</primary></indexterm>
+<indexterm><primary>independent</primary></indexterm>
+No special action is needed other than to create user accounts. Standalone
+servers do not provide network logon services. This means that machines that
+use this server do not perform a domain logon to it. Whatever logon facility
+the workstations are subject to is independent of this machine. It is, however,
+necessary to accommodate any network user so the logon name he or she uses will
+be translated (mapped) locally on the standalone server to a locally known
+user name. There are several ways this can be done.
+</para>
+
+<para>
+<indexterm><primary>local authentication database</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>not domain member</primary></indexterm>
+Samba tends to blur the distinction a little in defining
+a standalone server. This is because the authentication database may be
+local or on a remote server, even if from the SMB protocol perspective
+the Samba server is not a member of a domain security context.
+</para>
+
+<para>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>UNIX-user database</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>/etc/shadow</primary></indexterm>
+<indexterm><primary>local smbpasswd file</primary></indexterm>
+<indexterm><primary>LDAP backend</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+Through the use of Pluggable Authentication Modules (PAM) (see <link linkend="pam">the chapter on PAM</link>)
+and the name service switcher (NSS), which maintains the UNIX-user database, the source of authentication may
+reside on another server. We would be inclined to call this the authentication server.  This means that the
+Samba server may use the local UNIX/Linux system password database (<filename>/etc/passwd</filename> or
+<filename>/etc/shadow</filename>), may use a local smbpasswd file, or may use an LDAP backend, or even via PAM
+and Winbind another CIFS/SMB server for authentication.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Example Configuration</title>
+
+<para>
+<indexterm><primary>inspire simplicity</primary></indexterm>
+<indexterm><primary>complexity</primary></indexterm>
+<link linkend="simplynice">The example Reference Documentation Server</link> and <link
+linkend="SimplePrintServer">Central Print Serving</link> are designed to inspire simplicity. It is too easy to
+attempt a high level of creativity and to introduce too much complexity in server and network design.
+</para>
+
+<sect2 id="RefDocServer">
+<title>Reference Documentation Server</title>
+
+<para>
+<indexterm><primary>read-only</primary></indexterm>
+<indexterm><primary>reference documents</primary></indexterm>
+<indexterm><primary>/export</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+Configuration of a read-only data server that everyone can access is very simple. By default, all shares are
+read-only, unless set otherwise in the &smb.conf; file. <link linkend="simplynice">The example - Reference
+Documentation Server</link> is the &smb.conf; file that will do this. Assume that all the reference documents
+are stored in the directory <filename>/export</filename>, and the documents are owned by a user other than
+nobody. No home directories are shared, and there are no users in the <filename>/etc/passwd</filename> UNIX
+system database. This is a simple system to administer.
+</para>
+
+<example id="simplynice">
+<title>smb.conf for Reference Documentation Server</title>
+<smbconfblock>
+<smbconfcomment> Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
+<smbconfoption name="netbios name">&example.server.samba;</smbconfoption>
+<smbconfoption name="security">SHARE</smbconfoption>
+<smbconfoption name="passdb backend">guest</smbconfoption>
+<smbconfoption name="wins server">192.168.1.1</smbconfoption>
+<smbconfsection name="[data]"/>
+<smbconfoption name="comment">Data</smbconfoption>
+<smbconfoption name="path">/export</smbconfoption>
+<smbconfoption name="guest only">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+<blockquote>
+<attribution>Mark Twain</attribution>
+<para>
+I would have spoken more briefly, if I'd had more time to prepare.
+</para>
+</blockquote>
+
+<para>
+<indexterm><primary>password backend</primary></indexterm>
+<indexterm><primary>guest</primary></indexterm>
+<indexterm><primary>unprivileged account names</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+In <link linkend="simplynice">this example</link>, the machine name is set to &example.server.samba;, and the
+workgroup is set to the name of the local workgroup (&example.workgroup;) so the machine will appear together
+with systems with which users are familiar. The only password backend required is the <quote>guest</quote>
+backend to allow default unprivileged account names to be used. As there is a WINS server on this network, we
+of course make use of it.
+</para>
+
+<para>
+A US Air Force Colonel was renowned for saying: <quote>Better is the enemy of good enough!</quote> There are often
+sound reasons for avoiding complexity as well as for avoiding a technically perfect solution. Unfortunately,
+many network administrators still need to learn the art of doing just enough to keep out of trouble.
+</para>
+
+</sect2>
+
+<sect2 id="SimplePrintServer">
+<title>Central Print Serving</title>
+
+<para>
+<indexterm><primary>simple print server</primary></indexterm>
+<indexterm><primary>tools</primary></indexterm>
+Configuration of a simple print server is easy if you have all the right tools on your system.
+</para>
+
+<orderedlist>
+<title> Assumptions</title>
+	<listitem><para>
+	The print server must require no administration.
+	</para></listitem>
+
+	<listitem><para>
+	The print spooling and processing system on our print server will be CUPS.
+	(Please refer to <link linkend="CUPS-printing">CUPS Printing Support</link>, for more information).
+	</para></listitem>
+
+	<listitem><para>
+	The print server will service only network printers. The network administrator
+	will correctly configure the CUPS environment to support the printers.
+	</para></listitem>
+
+	<listitem><para>
+	All workstations will use only PostScript drivers. The printer driver
+	of choice is the one shipped with the Windows OS for the Apple Color LaserWriter.
+	</para></listitem>
+</orderedlist>
+
+<para>
+<indexterm><primary>print server</primary></indexterm>
+<indexterm><primary>/var/spool/samba</primary></indexterm>
+<indexterm><primary>anonymous</primary></indexterm>
+In this example our print server will spool all incoming print jobs to
+<filename>/var/spool/samba</filename> until the job is ready to be submitted by
+Samba to the CUPS print processor. Since all incoming connections will be as
+the anonymous (guest) user, two things will be required to enable anonymous printing.
+</para>
+
+<itemizedlist>
+<title>Enabling Anonymous Printing</title>
+	<listitem><para>
+<indexterm><primary>guest account</primary></indexterm>
+<indexterm><primary>nobody</primary></indexterm>
+<indexterm><primary>testparm</primary></indexterm>
+	The UNIX/Linux system must have a <command>guest</command> account.
+	The default for this is usually the account <command>nobody</command>.
+	To find the correct name to use for your version of Samba, do the 
+	following:
+<screen>
+&prompt;<userinput>testparm -s -v | grep "guest account"</userinput>
+</screen>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+	Make sure that this account exists in your system password
+	database (<filename>/etc/passwd</filename>).
+	</para>
+
+	<para>
+<indexterm><primary>set a password</primary></indexterm>
+<indexterm><primary>lock password</primary></indexterm>
+<indexterm><primary>passwd</primary></indexterm>
+	It is a good idea either to set a password on this account, or else to lock it
+	from UNIX use. Assuming that the guest account is called <literal>pcguest</literal>,
+	it can be locked by executing:
+<screen>
+&rootprompt; passwd -l pcguest
+</screen>
+	The exact command may vary depending on your UNIX/Linux distribution.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>directory</primary></indexterm>
+<indexterm><primary>guest account</primary></indexterm>
+<indexterm><primary>available</primary></indexterm>
+<indexterm><primary>mkdir</primary></indexterm>
+<indexterm><primary>chown</primary></indexterm>
+<indexterm><primary>chmod</primary></indexterm>
+	The directory into which Samba will spool the file must have write
+	access for the guest account. The following commands will ensure that
+	this directory is available for use:
+<screen>
+&rootprompt;<userinput>mkdir /var/spool/samba</userinput>
+&rootprompt;<userinput>chown nobody.nobody /var/spool/samba</userinput>
+&rootprompt;<userinput>chmod a+rwt /var/spool/samba</userinput>
+</screen>
+	</para></listitem>
+</itemizedlist>
+
+<para>
+The contents of the &smb.conf; file is shown in <link linkend="AnonPtrSvr">the Anonymous Printing example</link>.
+</para>
+
+<example id="AnonPtrSvr">
+<title>&smb.conf; for Anonymous Printing</title>
+<smbconfblock>
+<smbconfcomment> Global parameters</smbconfcomment>
+<smbconfsection name="[global]"/>
+<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
+<smbconfoption name="netbios name">&example.server.samba;</smbconfoption>
+<smbconfoption name="security">SHARE</smbconfoption>
+<smbconfoption name="passdb backend">guest</smbconfoption>
+<smbconfoption name="printing">cups</smbconfoption>
+<smbconfoption name="printcap name">cups</smbconfoption>
+
+<smbconfsection name="[printers]"/>
+<smbconfoption name="comment">All Printers</smbconfoption>
+<smbconfoption name="path">/var/spool/samba</smbconfoption>
+<smbconfoption name="printer admin">root</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+<smbconfoption name="printable">Yes</smbconfoption>
+<smbconfoption name="use client driver">Yes</smbconfoption>
+<smbconfoption name="browseable">No</smbconfoption>
+</smbconfblock>
+</example>
+
+
+<note><para>
+<indexterm><primary>MIME</primary><secondary>raw</secondary></indexterm>
+<indexterm><primary>raw printing</primary></indexterm>
+<indexterm><primary>/etc/mime.conv</primary></indexterm>
+<indexterm><primary>/etc/mime.types</primary></indexterm>
+<indexterm><primary>CUPS print filters</primary></indexterm>
+On CUPS-enabled systems there is a facility to pass raw data directly to the printer without intermediate
+processing via CUPS print filters. Where use of this mode of operation is desired, it is necessary to
+configure a raw printing device. It is also necessary to enable the raw mime handler in the
+<filename>/etc/mime.conv</filename> and <filename>/etc/mime.types</filename> files. Refer to <link
+linkend="CUPS-printing">CUPS Printing Support</link>, <link linkend="cups-raw">Explicitly Enable raw Printing
+for application/octet-stream</link>.
+</para></note>
+
+<para>
+<indexterm><primary>CUPS libarary API</primary></indexterm>
+<indexterm><primary>no printcap file</primary></indexterm>
+<indexterm><primary>PDF filter</primary></indexterm>
+<indexterm><primary>printcap name</primary></indexterm>
+The example in <link linkend="AnonPtrSvr">the Anonymous Printing example</link> uses CUPS for direct printing
+via the CUPS libarary API. This means that all printers will be exposed to Windows users without need to
+configure a printcap file. If there is necessity to expose only a sub-set of printers, or to define a special
+type of printer (for example, a PDF filter) the <parameter>printcap name = cups</parameter> can be replaced
+with the entry <parameter>printcap name = /etc/samba/myprintcap</parameter>. In this case the file specified
+should contain a list of the printer names that should be exposed to Windows network users.
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+<indexterm><primary>greatest mistake</primary></indexterm>
+<indexterm><primary>configuration too complex</primary></indexterm>
+The greatest mistake so often made is to make a network configuration too complex.
+It pays to use the simplest solution that will meet the needs of the moment.
+</para>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Support.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Support.xml
new file mode 100644
index 00000000000..b970bc00f04
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Support.xml
@@ -0,0 +1,163 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<chapter lang="en-US">
+<title>Samba Support</title>
+
+<para>
+<indexterm><primary>support</primary></indexterm>
+One of the most difficult to answer questions in the information technology industry is, <quote>What is
+support?</quote>. That question irritates some folks, as much as common answers may annoy others.
+</para>
+
+<para>
+<indexterm><primary>customers</primary></indexterm>
+The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to
+an Internet service provider who, instead of listening to the problem to find a solution, blandly replies:
+<quote>Oh, Linux? We do not support Linux!</quote>. It has happened to me, and similar situations happen
+through-out the IT industry. Answers like that are designed to inform us that there are some customers
+that a business just does not want to deal with, and well may we feel the anguish of the rejection that 
+is dished out.
+</para>
+
+<para>
+One way to consider support is to view it as consisting of the right answer, in the right place,
+at the right time, no matter the situation. Support is all that it takes to take away pain, disruption,
+inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk.
+</para>
+
+<para>
+<indexterm><primary>provided services</primary></indexterm>
+<indexterm><primary>services provided</primary></indexterm>
+<indexterm><primary>customer expected</primary></indexterm>
+One of the forces that has become a driving force for the adoption of open source software is the fact that
+many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or
+that have been found wanting for other reasons.
+</para>
+
+<para>
+<indexterm><primary>consumer expects</primary></indexterm>
+<indexterm><primary>problem resolution</primary></indexterm>
+In recognition of the need for needs satisfaction as the primary experience an information technology user or
+consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience
+in respect of problem resolution.
+</para>
+
+<para>
+<indexterm><primary>free support</primary></indexterm>
+<indexterm><primary>paid-for support</primary></indexterm>
+<indexterm><primary>commercial support</primary></indexterm>
+In the open source software arena there are two support options: free support and paid-for (commercial)
+support.
+</para>
+
+	<sect1>
+	<title>Free Support</title>
+
+	<para>
+<indexterm><primary>user groups</primary></indexterm>
+<indexterm><primary>mailing lists</primary></indexterm>
+<indexterm><primary>interactive help</primary></indexterm>
+<indexterm><primary>help</primary></indexterm>
+<indexterm><primary>mutual assistance</primary></indexterm>
+<indexterm><primary>assistance</primary></indexterm>
+	Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help
+	facilities. An example of an interactive dacility is the Internet relay chat (IRC) channels that host user
+	supported mutual assistance.
+	</para>
+
+	<para>
+<indexterm><primary>mailing list</primary></indexterm>
+<indexterm><primary>deployment</primary></indexterm>
+<indexterm><primary>subscription</primary></indexterm>
+<indexterm><primary>IRC</primary></indexterm>
+<indexterm><primary>project</primary></indexterm>
+	The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba deployments.
+	Information regarding subscription to the Samba mailing list can be found on the Samba <ulink
+	url="https://lists.samba.org/mailman/">web</ulink> site. The public mailing list that can be used to obtain
+	free, user contributed, support is called the <literal>samba</literal> list. The email address for this list
+	is at <literal>mail:samba@samba.org</literal>.  Information regarding the Samba IRC channels may be found on
+	the Samba <ulink url="http://www.samba.org/samba.irc.html">IRC</ulink> web page.
+	</para>
+
+	<para>
+<indexterm><primary>free support</primary></indexterm>
+<indexterm><primary>qualified problem</primary></indexterm>
+<indexterm><primary>requesting payment</primary></indexterm>
+<indexterm><primary>professional support</primary></indexterm>
+	As a general rule, it is considered poor net behavior to contact a Samba Team member directly
+	for free support. Most active members of the Samba Team work exceptionally long hours to assist
+	users who have demonstrated a qualified problem. Some team members may respond to direct email
+	or telephone contact, with requests for assistance, by requesting payment. A few of the Samba
+	Team members actually provide professional paid-for Samba support and it is therefore wise
+	to show appropriate discretion and reservation in all direct contact.
+	</para>
+
+	<para>
+<indexterm><primary>bug report</primary></indexterm>
+<indexterm><primary>problem report</primary></indexterm>
+<indexterm><primary>code maintainer</primary></indexterm>
+	When you stumble across a Samba bug, often the quickest way to get it resolved is by posting
+	a bug <ulink url="https://bugzilla.samba.org/">report</ulink>. All such reports are mailed to
+	the responsible code maintainer for action. The better the report, and the more serious it is,
+	the sooner it will be dealt with. On the other hand, if the responsible person can not duplicate
+	the reported bug it is likely to be rejected. It is up to you to provide sufficient information
+	that will permit the problem to be reproduced.
+	</para>
+
+	<para>
+<indexterm><primary>purchase support</primary></indexterm>
+	We all recognize that sometimes free support does not provide the answer that is sought within
+	the time-frame required. At other times the problem is elusive and you may lack the experience
+	necessary to isolate the problem and thus to resolve it. This is a situation where is may be
+	prudent to purchase paid-for support.
+	</para>
+
+	</sect1>
+
+	<sect1>
+	<title>Commercial Support</title>
+
+	<para>
+	There are six basic support oriented services that are most commonly sought by Samba sites:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>Assistance with network design</para></listitem>
+		<listitem><para>Staff Training</para></listitem>
+		<listitem><para>Assistance with Samba network deployment and installation</para></listitem>
+		<listitem><para>Priority telephone or email Samba configuration assistance</para></listitem>
+		<listitem><para>Trouble-shooting and diagnostic assistance</para></listitem>
+		<listitem><para>Provision of quality assured ready-to-install Samba binary packages</para></listitem>
+	</itemizedlist>
+
+	<para>
+<indexterm><primary>commercial support</primary></indexterm>
+<indexterm><primary>country of origin</primary></indexterm>
+	Information regarding companies that provide professional Samba support can be obtained by performing a Google
+	search, as well as by reference to the Samba <ulink
+	url="http://www.samba.org/samba/support.html">Support</ulink> web page. Companies who notify the Samba Team
+	that they provide commercial support are given a free listing that is sorted by the country of origin.
+	Multiple listings are permitted, however no guarantee is offered. It is left to you to qualify a support
+	provider and to satisfy yourself that both the company and its staff are able to deliver what is required of
+	them.
+	</para>
+
+	<para>
+<indexterm><primary>commercial support</primary></indexterm>
+	The policy within the Samba Team is to treat all commercial support providers equally and to show no
+	preference. As a result, Samba Team members who provide commercial support are lumped in with everyone else.
+	You are encouraged to obtain the services needed from a company in your local area. The open source movement
+	is pro-community; so do what you can to help a local business to prosper.
+	</para>
+
+	<para>
+<indexterm><primary>unsupported software</primary></indexterm>
+	Open source software support can be found in any quality, at any price and in any place you can
+	to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for
+	suffering in the mistaken belief that Samba is unsupported software &smbmdash; it is supported.
+	</para>
+
+	</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml b/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml
new file mode 100644
index 00000000000..b2b3ebd5b15
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml
@@ -0,0 +1,1916 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<chapter id="NetCommand">
+<chapterinfo>
+	&author.jht;
+	&author.vl;
+	&author.gd;
+	<pubdate>May 9, 2005</pubdate>
+</chapterinfo>
+
+<title>Remote and Local Management: The Net Command</title>
+
+<para>
+<indexterm><primary>net</primary></indexterm>
+<indexterm><primary>remote management</primary></indexterm>
+<indexterm><primary>command-line</primary></indexterm>
+<indexterm><primary>scripted control</primary></indexterm>
+The <command>net</command> command is one of the new features of Samba-3 and is an attempt to provide a useful
+tool for the majority of remote management operations necessary for common tasks. The <command>net</command>
+tool is flexible by design and is intended for command-line use as well as for scripted control application.
+</para>
+
+<para>
+<indexterm><primary>net</primary></indexterm>
+<indexterm><primary>network administrator's toolbox</primary></indexterm>
+<indexterm><primary>smbgroupedit</primary></indexterm>
+<indexterm><primary>rpcclient</primary></indexterm>
+Originally introduced with the intent to mimic the Microsoft Windows command that has the same name, the
+<command>net</command> command has morphed into a very powerful instrument that has become an essential part
+of the Samba network administrator's toolbox. The Samba Team has introduced tools, such as
+<command>smbgroupedit</command> and <command>rpcclient</command>, from which really useful capabilities have
+been integrated into the <command>net</command>. The <command>smbgroupedit</command> command was absorbed
+entirely into the <command>net</command>, while only some features of the <command>rpcclient</command> command
+have been ported to it. Anyone who finds older references to these utilities and to the functionality they
+provided should look at the <command>net</command> command before searching elsewhere.
+</para>
+
+<para>
+A Samba-3 administrator cannot afford to gloss over this chapter because to do so will almost certainly cause
+the infliction of self-induced pain, agony, and desperation. Be warned: this is an important chapter.
+</para>
+
+	<sect1>
+	<title>Overview</title>
+
+	<para>
+<indexterm><primary>standalone</primary></indexterm>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>DMS</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+	The tasks that follow the installation of a Samba-3 server, whether standalone or domain member, of a
+	domain controller (PDC or BDC) begins with the need to create administrative rights. Of course, the
+	creation of user and group accounts is essential for both a standalone server and a PDC.
+	In the case of a BDC or a Domain Member server (DMS), domain user and group accounts are obtained from
+	the central domain authentication backend.
+	</para>
+
+	<para>
+<indexterm><primary>server type</primary></indexterm>
+<indexterm><primary>local UNIX groups</primary></indexterm>
+<indexterm><primary>mapped</primary></indexterm>
+<indexterm><primary>domain global group</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>access rights</primary></indexterm>
+<indexterm><primary>net</primary></indexterm>
+	Regardless of the type of server being installed, local UNIX groups must be mapped to the Windows
+	networking domain global group accounts. Do you ask why? Because Samba always limits its access to
+	the resources of the host server by way of traditional UNIX UID and GID controls. This means that local
+	groups must be mapped to domain global groups so that domain users who are members of the domain
+	global groups can be given access rights based on UIDs and GIDs local to the server that is hosting
+	Samba. Such mappings are implemented using the <command>net</command> command.
+	</para>
+
+	<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+<indexterm><primary>DMS</primary></indexterm>
+<indexterm><primary>security account</primary></indexterm>
+<indexterm><primary>domain authentication</primary></indexterm>
+<indexterm><primary>trust accounts</primary></indexterm>
+<indexterm><primary>net</primary></indexterm>
+	UNIX systems that are hosting a Samba-3 server that is running as a member (PDC, BDC, or DMS) must have
+	a machine security account in the domain authentication database (or directory). The creation of such
+	security (or trust) accounts is also handled using the <command>net</command> command.
+	</para>
+
+	<para>
+<indexterm><primary>interdomain trusts</primary></indexterm>
+<indexterm><primary>net</primary></indexterm>
+<indexterm><primary>administrative duties</primary></indexterm>
+<indexterm><primary>user management</primary></indexterm>
+<indexterm><primary>group management</primary></indexterm>
+<indexterm><primary>share management</primary></indexterm>
+<indexterm><primary>printer management</primary></indexterm>
+<indexterm><primary>printer migration</primary></indexterm>
+<indexterm><primary>SID management</primary></indexterm>
+	The establishment of interdomain trusts is achieved using the <command>net</command> command also, as
+	may a plethora of typical administrative duties such as user management, group management, share and
+	printer management, file and printer migration, security identifier management, and so on.
+	</para>
+
+	<para>
+<indexterm><primary>net</primary></indexterm>
+<indexterm><primary>man pages</primary></indexterm>
+	The overall picture should be clear now: the <command>net</command> command plays a central role
+	on the Samba-3 stage. This role will continue to be developed. The inclusion of this chapter is
+	evidence of its importance, one that has grown in complexity to the point that it is no longer considered
+	prudent to cover its use fully in the online UNIX man pages.
+	</para>
+
+	</sect1>
+	
+	<sect1>
+	<title>Administrative Tasks and Methods</title>
+
+	<para>
+<indexterm><primary>net</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>Distributed Computing Environment</primary><see>DCE</see></indexterm>
+<indexterm><primary>Remote Procedure Call</primary><see>RPC</see></indexterm>
+	The basic operations of the <command>net</command> command are documented here. This documentation is not
+	exhaustive, and thus it is incomplete. Since the primary focus is on migration from Windows servers to a Samba
+	server, the emphasis is on the use of the Distributed Computing Environment Remote Procedure Call (DCE RPC)
+	mode of operation. When used against a server that is a member of an Active Directory domain, it is preferable
+	(and often necessary) to use ADS mode operations. The <command>net</command> command supports both, but not
+	for every operation. For most operations, if the mode is not specified, <command>net</command> will
+	automatically fall back via the <constant>ads</constant>, <constant>rpc</constant>, and
+	<constant>rap</constant> modes.  Please refer to the man page for a more comprehensive overview of the
+	capabilities of this utility.
+	</para>
+
+	</sect1>
+
+	<sect1>
+	<title>UNIX and Windows Group Management</title>
+
+	<para>
+<indexterm><primary>Active Directory</primary></indexterm>
+<indexterm><primary>net</primary><secondary>rpc</secondary></indexterm>
+<indexterm><primary>net</primary><secondary>ads</secondary></indexterm>
+<indexterm><primary>net</primary><secondary>rap</secondary></indexterm>
+<indexterm><primary>RAP</primary></indexterm>
+	As stated, the focus in most of this chapter is on use of the <command>net rpc</command> family of
+	operations that are supported by Samba. Most of them are supported by the <command>net ads</command>
+	mode when used in connection with Active Directory. The <command>net rap</command> operating mode is
+	also supported for some of these operations. RAP protocols are used by IBM OS/2 and by several
+	earlier SMB servers.
+	</para>
+
+	<para>
+<indexterm><primary>net</primary></indexterm>
+<indexterm><primary>user management</primary></indexterm>
+<indexterm><primary>group management</primary></indexterm>
+	Samba's <command>net</command> tool implements sufficient capability to permit all common administrative
+	tasks to be completed from the command line. In this section each of the essential user and group management
+	facilities are explored.
+	</para>
+
+	<para>
+<indexterm><primary>groups</primary></indexterm>
+<indexterm><primary>domain</primary><secondary>groups</secondary></indexterm>
+<indexterm><primary>local</primary><secondary>groups</secondary></indexterm>
+<indexterm><primary>domain user accounts</primary></indexterm>
+	Samba-3 recognizes two types of groups: <emphasis>domain groups</emphasis> and <emphasis>local
+	groups</emphasis>. Domain groups can contain (have as members) only domain user accounts. Local groups
+	can contain local users, domain users, and domain groups as members.
+	</para>
+
+	<para>
+	The purpose of a local group is to permit file permission to be set for a group account that, like the
+	usual UNIX/Linux group, is persistent across redeployment of a Windows file server.
+	</para>
+
+	<sect2>
+	<title>Adding, Renaming, or Deletion of Group Accounts</title>
+
+	<para>
+	Samba provides file and print services to Windows clients. The file system resources it makes available
+	to the Windows environment must, of necessity, be provided in a manner that is compatible with the
+	Windows networking environment. UNIX groups are created and deleted as required to serve operational
+	needs in the UNIX operating system and its file systems.
+	</para>
+
+	<para>
+	In order to make available to the Windows environment, Samba has a facility by which UNIX groups can
+	be mapped to a logical entity, called a Windows (or domain) group. Samba supports two types of Windows
+	groups, local and global. Global groups can contain as members, global users. This membership is
+	affected in the normal UNIX manner, but adding UNIX users to UNIX groups. Windows user accounts consist
+	of a mapping between a user SambaSAMAccount (logical entity) and a UNIX user account. Therefore, 
+	a UNIX user is mapped to a Windows user (i.e., is given a Windows user account and password) and the
+	UNIX groups to which that user belongs, is mapped to a Windows group account. The result is that in
+	the Windows account environment that user is also a member of the Windows group account by virtue
+	of UNIX group memberships.
+	</para>
+
+	<para>
+	The following sub-sections that deal with management of Windows groups demonstrates the relationship
+	between the UNIX group account and its members to the respective Windows group accounts. It goes on to
+	show how UNIX group members automatically pass-through to Windows group membership as soon as a logical
+	mapping has been created.
+	</para>
+
+	<sect3>
+	<title>Adding or Creating a New Group</title>
+
+	<para>
+	Before attempting to add a Windows group account, the currently available groups can be listed as shown
+	here:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group</tertiary></indexterm>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group list</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc group list -Uroot%not24get
+Password:
+Domain Admins
+Domain Users
+Domain Guests
+Print Operators
+Backup Operators
+Replicator
+Domain Computers
+Engineers
+</screen>
+	</para>
+
+<?latex \newpage ?>
+	<para>
+	A Windows group account called <quote>SupportEngrs</quote> can be added by executing the following
+command:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group add</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc group add "SupportEngrs" -Uroot%not24get
+</screen>
+	The addition will result in immediate availability of the new group account as validated by executing
+this command:
+<screen>
+&rootprompt; net rpc group list -Uroot%not24get
+Password:
+Domain Admins
+Domain Users
+Domain Guests
+Print Operators
+Backup Operators
+Replicator
+Domain Computers
+Engineers
+SupportEngrs
+</screen>
+	</para>
+
+	<para>
+<indexterm><primary>POSIX</primary></indexterm>
+<indexterm><primary>smbldap-groupadd</primary></indexterm>
+<indexterm><primary>getent</primary></indexterm>
+	The following demonstrates that the POSIX (UNIX/Linux system account) group has been created by calling
+	the <smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd -p "%g"</smbconfoption> interface
+	script:
+<screen>
+&rootprompt; getent group
+...
+Domain Admins:x:512:root
+Domain Users:x:513:jht,lct,ajt,met
+Domain Guests:x:514:
+Print Operators:x:550:
+Backup Operators:x:551:
+Replicator:x:552:
+Domain Computers:x:553:
+Engineers:x:1002:jht
+SupportEngrs:x:1003:
+</screen>
+	The following demonstrates that the use of the <command>net</command> command to add a group account
+results in immediate mapping of the POSIX group that has been created to the Windows group account as shown
+here:
+<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>list</tertiary></indexterm>
+<screen>
+&rootprompt; net groupmap list
+Domain Admins (S-1-5-21-72630-4128915-11681869-512) -> Domain Admins
+Domain Users (S-1-5-21-72630-4128915-11681869-513) -> Domain Users
+Domain Guests (S-1-5-21-72630-4128915-11681869-514) -> Domain Guests
+Print Operators (S-1-5-21-72630-4128915-11681869-550) -> Print Operators
+Backup Operators (S-1-5-21-72630-4128915-11681869-551) -> Backup Operators
+Replicator (S-1-5-21-72630-4128915-11681869-552) -> Replicator
+Domain Computers (S-1-5-21-72630-4128915-11681869-553) -> Domain Computers
+Engineers (S-1-5-21-72630-4128915-11681869-3005) -> Engineers
+SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -> SupportEngrs
+</screen>
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Mapping Windows Groups to UNIX Groups</title>
+
+	<para>
+<indexterm><primary>mapped</primary></indexterm>
+<indexterm><primary>Windows groups</primary></indexterm>
+<indexterm><primary>system groups</primary></indexterm>
+<indexterm><primary>access controls</primary></indexterm>
+	Windows groups must be mapped to UNIX system (POSIX) groups so that file system access controls
+	can be asserted in a manner that is consistent with the methods appropriate to the operating
+	system that is hosting the Samba server.
+	</para>
+
+	<para>
+<indexterm><primary>access controls</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>locally known UID</primary></indexterm>
+	All file system (file and directory) access controls, within the file system of a UNIX/Linux server that is
+	hosting a Samba server, are implemented using a UID/GID identity tuple. Samba does not in any way override
+	or replace UNIX file system semantics. Thus it is necessary that all Windows networking operations that
+	access the file system provide a mechanism that maps a Windows user to a particular UNIX/Linux group
+	account. The user account must also map to a locally known UID. Note that the <command>net</command>
+	command does not call any RPC-functions here but directly accesses the passdb.
+	</para>
+
+	<para>
+<indexterm><primary>default mappings</primary></indexterm>
+<indexterm><primary>Domain Admins</primary></indexterm>
+<indexterm><primary>Domain Users</primary></indexterm>
+<indexterm><primary>Domain Guests</primary></indexterm>
+<indexterm><primary>Windows group</primary></indexterm>
+<indexterm><primary>UNIX group</primary></indexterm>
+<indexterm><primary>mapping</primary></indexterm>
+	Samba depends on default mappings for the <constant>Domain Admins, Domain Users</constant>, and
+	<constant>Domain Guests</constant> global groups. Additional groups may be added as shown in the
+	examples just given. There are times when it is necessary to map an existing UNIX group account
+	to a Windows group. This operation, in effect, creates a Windows group account as a consequence
+	of creation of the mapping.
+	</para>
+
+	<para>
+<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>modify</tertiary></indexterm>
+<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>add</tertiary></indexterm>
+<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>delete</tertiary></indexterm>
+	The operations that are permitted include: <constant>add</constant>, <constant>modify</constant>,
+	and <constant>delete</constant>. An example of each operation is shown here.
+	</para>
+
+	<note><para>
+	Commencing with Samba-3.0.23 Windows Domain Groups must be explicitly created. By default, all
+	UNIX groups are exposed to Windows networking as Windows local groups.
+	</para></note>
+
+	<para>
+	An existing UNIX group may be mapped to an existing Windows group by this example:
+<screen>
+&rootprompt; net groupmap modify ntgroup="Domain Users" unixgroup=users
+</screen>
+	An existing UNIX group may be mapped to a new Windows group as shown here:
+<screen>
+&rootprompt; net groupmap add ntgroup="EliteEngrs" unixgroup=Engineers type=d
+</screen>
+	Supported mapping types are 'd' (domain global) and 'l' (domain local).
+	A Windows group may be deleted, and then a new Windows group can be mapped to the UNIX group by
+	executing these commands:
+<screen>
+&rootprompt; net groupmap delete ntgroup=Engineers
+&rootprompt; net groupmap add ntgroup=EngineDrivers unixgroup=Engineers type=d
+</screen>
+	The deletion and addition operations affected only the logical entities known as Windows groups, or domain
+	groups. These operations are inert to UNIX system groups, meaning that they neither delete nor create UNIX
+	system groups. The mapping of a UNIX group to a Windows group makes the UNIX group available as Windows
+	groups so that files and folders on domain member clients (workstations and servers) can be given
+	domain-wide access controls for domain users and groups.
+	</para>
+
+	<para>
+	Two types of Windows groups can be created: <constant>domain (global)</constant> and <constant>local</constant>.
+	In the previous examples the Windows groups created were of type <constant>domain</constant> or global. The
+	following command will create a Windows group of type <constant>local</constant>.
+<screen>
+&rootprompt; net groupmap add ntgroup=Pixies unixgroup=pixies type=l
+</screen>
+	Supported mapping types are 'd' (domain global) and 'l' (domain local), a domain local group in Samba is
+	treated as local to the individual Samba server. Local groups can be used with Samba to enable multiple
+	nested group support.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Deleting a Group Account</title>
+
+	<para>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group delete</tertiary></indexterm>
+	A group account may be deleted by executing the following command:
+<screen>
+&rootprompt; net rpc group delete SupportEngineers -Uroot%not24get
+</screen>
+	</para>
+
+	<para>
+	Validation of the deletion is advisable. The same commands may be executed as shown above.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>Rename Group Accounts</title>
+
+	<note><para>
+	This command is not documented in the man pages; it is implemented in the source code, but it does not
+	work at this time. The example given documents, from the source code, how it should work. Watch the
+	release notes of a future release to see when this may have been fixed.
+	</para></note>
+
+	<para>
+	Sometimes it is necessary to rename a group account. Good administrators know how painful some managers'
+	demands can be if this simple request is ignored. The following command demonstrates how the Windows group
+	<quote>SupportEngrs</quote> can be renamed to <quote>CustomerSupport</quote>:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group rename</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc group rename SupportEngrs \
+    CustomerSupport -Uroot%not24get
+</screen>
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2 id="grpmemshipchg">
+	<title>Manipulating Group Memberships</title>
+
+	<para>
+	Three operations can be performed regarding group membership. It is possible to (1) add Windows users
+	to a Windows group, to (2) delete Windows users from Windows groups, and to (3) list the Windows users that are
+	members of a Windows group.
+	</para>
+
+	<para>
+	To avoid confusion, it makes sense to check group membership before attempting to make any changes.
+	The <command>getent group</command> will list UNIX/Linux group membership. UNIX/Linux group members are
+	seen also as members of a Windows group that has been mapped using the <command>net groupmap</command>
+	command (see <link linkend="groupmapping"/>). The following list of UNIX/Linux group membership shows
+	that the user <constant>ajt</constant> is a member of the UNIX/Linux group <constant>Engineers</constant>.
+<screen>
+&rootprompt; getent group
+...
+Domain Admins:x:512:root
+Domain Users:x:513:jht,lct,ajt,met,vlendecke
+Domain Guests:x:514:
+Print Operators:x:550:
+Backup Operators:x:551:
+Replicator:x:552:
+Domain Computers:x:553:
+Engineers:x:1000:jht,ajt
+</screen>
+	The UNIX/Linux groups have been mapped to Windows groups, as is shown here:
+<screen>
+&rootprompt; net groupmap list
+Domain Admins (S-1-5-21-72630-412605-116429-512) -> Domain Admins
+Domain Users (S-1-5-21-72630-412605-116429-513) -> Domain Users
+Domain Guests (S-1-5-21-72630-412605-116429-514) -> Domain Guests
+Print Operators (S-1-5-21-72630-412605-116429-550) -> Print Operators
+Backup Operators (S-1-5-21-72630-412605-116429-551) -> Backup Operators
+Replicator (S-1-5-21-72630-412605-116429-552) -> Replicator
+Domain Computers (S-1-5-21-72630-412605-116429-553) -> Domain Computers
+Engineers (S-1-5-21-72630-412605-116429-3001) -> Engineers
+</screen>
+	</para>
+
+	<para>
+	Given that the user <constant>ajt</constant> is already a member of the UNIX/Linux group and, via the
+	group mapping, a member of the Windows group, an attempt to add this account again should fail. This is
+	demonstrated here:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group addmem</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc group addmem "MIDEARTH\Engineers" ajt -Uroot%not24get
+Could not add ajt to MIDEARTH\Engineers: NT_STATUS_MEMBER_IN_GROUP
+</screen>
+	This shows that the group mapping between UNIX/Linux groups and Windows groups is effective and
+	transparent.
+	</para>
+
+	<para>
+	To permit the user <constant>ajt</constant> to be added using the <command>net rpc group</command> utility,
+	this account must first be removed. The removal and confirmation of its effect is shown here:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group delmem</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc group delmem "MIDEARTH\Engineers" ajt -Uroot%not24get
+&rootprompt; getent group Engineers
+Engineers:x:1000:jht
+&rootprompt; net rpc group members Engineers -Uroot%not24get
+MIDEARTH\jht
+</screen>
+	In this example both at the UNIX/Linux system level, the group no longer has the <constant>ajt</constant>
+	as a member. The above also shows this to be the case for Windows group membership.
+	</para>
+
+	<para>
+	The account is now added again, using the <command>net rpc group</command> utility:
+<screen>
+&rootprompt; net rpc group addmem "MIDEARTH\Engineers" ajt -Uroot%not24get
+&rootprompt; getent group Engineers
+Engineers:x:1000:jht,ajt
+&rootprompt; net rpc group members Engineers -Uroot%not24get
+MIDEARTH\jht
+MIDEARTH\ajt
+</screen>
+	</para>
+
+	<para>
+	In this example the members of the Windows <constant>Domain Users</constant> account are validated using
+	the <command>net rpc group</command> utility. Note the this contents of the UNIX/Linux group was shown
+	four paragraphs earlier. The Windows (domain) group membership is shown here:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group members</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc group members "Domain Users" -Uroot%not24get
+MIDEARTH\jht
+MIDEARTH\lct
+MIDEARTH\ajt
+MIDEARTH\met
+MIDEARTH\vlendecke
+</screen>
+	This express example shows that Windows group names are treated by Samba (as with
+	MS Windows) in a case-insensitive manner:
+<screen>
+&rootprompt; net rpc group members "DomAiN USerS" -Uroot%not24get
+MIDEARTH\jht
+MIDEARTH\lct
+MIDEARTH\ajt
+MIDEARTH\met
+MIDEARTH\vlendecke
+</screen>
+	</para>
+
+	<note><para>
+	An attempt to specify the group name as <constant>MIDEARTH\Domain Users</constant> in place of
+	just simply <constant>Domain Users</constant> will fail. The default behavior of the net rpc group
+	is to direct the command at the local machine. The Windows group is treated as being local to the machine.
+	If it is necessary to query another machine, its name can be specified using the <constant>-S
+	servername</constant> parameter to the <command>net</command> command.
+	</para></note>
+
+	</sect2>
+
+	<sect2 id="nestedgrpmgmgt">
+	<title>Nested Group Support</title>
+
+	<para>
+	It is possible in Windows (and now in Samba also) to create a local group that has members (contains),
+	domain users, and domain global groups.  Creation of the local group <constant>demo</constant> is
+	achieved by executing:
+<screen>
+&rootprompt; net rpc group add demo -L -S MORDON -Uroot%not24get
+</screen>
+	The -L switch means create a local group. Use the -S argument to direct the operation to a particular
+	server. The parameters to the -U argument should be for a user who has appropriate administrative right
+	and privileges on the machine.
+	</para>
+
+	<para>
+	Addition and removal of group members can be achieved using the <constant>addmem</constant> and
+	<constant>delmem</constant> subcommands of <command>net rpc group</command> command. For example,
+	addition of <quote>DOM\Domain Users</quote> to the local group <constant>demo</constant> would be
+	done by executing:
+<screen>
+&rootprompt; net rpc group addmem demo "DOM\Domain Users" -Uroot%not24get
+</screen>
+	</para>
+
+	<para>
+	The members of a nested group can be listed by executing the following:
+<screen>
+&rootprompt; net rpc group members demo -Uroot%not24get
+DOM\Domain Users
+DOM\Engineers
+DOM\jamesf
+DOM\jht
+</screen>
+	</para>
+
+	<para>
+	Nested group members can be removed (deleted) as shown here:
+<screen>
+&rootprompt; net rpc group delmem demo "DOM\jht" -Uroot%not24get
+</screen>
+	</para>
+
+	<sect3>
+	<title>Managing Nest Groups on Workstations from the Samba Server</title>
+
+	<para>
+	Windows network administrators often ask on the Samba mailing list how it is possible to grant everyone
+	administrative rights on their own workstation. This is of course a very bad practice, but commonly done
+	to avoid user complaints. Here is how it can be done remotely from a Samba PDC or BDC:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group addmem</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc group addmem "Administrators" "Domain Users" \
+    -S WINPC032 -Uadministrator%secret
+</screen>
+	</para>
+
+	<para>
+	This can be scripted, and can therefore be performed as a user logs onto the domain from a Windows
+	workstation. Here is a simple example that shows how this can be done.
+	</para>
+
+	<procedure>
+	<title>Automating User Addition to the Workstation Power Users Group</title>
+
+		<step><para>
+		Create the script shown in <link linkend="autopoweruserscript"></link> and locate it in
+		the directory <filename>/etc/samba/scripts</filename>, named as <filename>autopoweruser.sh</filename>.
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group addmem</tertiary></indexterm>
+<indexterm><primary>autopoweruser.sh</primary></indexterm>
+<indexterm><primary>/etc/samba/scripts</primary></indexterm>
+		</para></step>
+
+<example id="autopoweruserscript">
+<title>Script to Auto-add Domain Users to Workstation Power Users Group</title>
+<screen>
+#!/bin/bash
+
+/usr/bin/net rpc group addmem "Power Users" "DOMAIN_NAME\$1" \
+                   -UAdministrator%secret -S $2
+
+exit 0
+</screen>
+</example>
+
+		<step><para>
+		Set the permissions on this script to permit it to be executed as part of the logon process:
+<screen>
+&rootprompt; chown root:root /etc/samba/autopoweruser.sh
+&rootprompt; chmod 755 /etc/samba/autopoweruser.sh
+</screen>
+		</para></step>
+
+		<step><para>
+		Modify the &smb.conf; file so the <literal>NETLOGON</literal> stanza contains the parameters
+		shown in <link linkend="magicnetlogon">the Netlogon Example smb.conf file</link>.
+		</para></step>
+
+<example id="magicnetlogon">
+<title>A Magic Netlogon Share</title>
+<smbconfblock>
+<smbconfsection name="[netlogon]"/>
+<smbconfoption name="comment">Netlogon Share</smbconfoption>
+<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
+<smbconfoption name="root preexec">/etc/samba/scripts/autopoweruser.sh %U %m</smbconfoption>
+<smbconfoption name="read only">Yes</smbconfoption>
+<smbconfoption name="guest ok">Yes</smbconfoption>
+</smbconfblock>
+</example>
+
+		<step><para>
+		Ensure that every Windows workstation Administrator account has the same password that you
+		have used in the script shown in <link linkend="magicnetlogon">the Netlogon Example smb.conf
+		file</link>
+		</para></step>
+
+</procedure>
+
+	<para>
+	This script will be executed every time a user logs on to the network. Therefore every user will
+	have local Windows workstation management rights. This could of course be assigned using a group,
+	in which case there is little justification for the use of this procedure. The key justification
+	for the use of this method is that it will guarantee that all users have appropriate rights on
+	the workstation.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+	</sect1>
+
+	<sect1>
+	<title>UNIX and Windows User Management</title>
+
+	<para>
+<indexterm><primary>user account</primary></indexterm>
+<indexterm><primary>UNIX/Linux user account</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>POSIX account</primary></indexterm>
+<indexterm><primary>range</primary></indexterm>
+<indexterm><primary>Windows user accounts</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>account information</primary></indexterm>
+	Every Windows network user account must be translated to a UNIX/Linux user account. In actual fact,
+	the only account information the UNIX/Linux Samba server needs is a UID.  The UID is available either
+	from a system (POSIX) account or from a pool (range) of UID numbers that is set aside for the purpose
+	of being allocated for use by Windows user accounts. In the case of the UID pool, the UID for a
+	particular user will be allocated by <command>winbindd</command>.
+	</para>
+
+	<para>
+	Although this is not the appropriate place to discuss the <smbconfoption name="username map"/> facility,
+	this interface is an important method of mapping a Windows user account to a UNIX account that has a
+	different name. Refer to the man page for the &smb.conf; file for more information regarding this
+	facility. User name mappings cannot be managed using the <command>net</command> utility.
+	</para>
+
+	<sect2 id="sbeuseraddn">
+	<title>Adding User Accounts</title>
+
+	<para>
+	The syntax for adding a user account via the <command>net</command> (according to the man page) is shown
+	here:
+<screen>
+net [&lt;method&gt;] user ADD &lt;name&gt; [-c container] [-F user flags] \
+    [misc. options] [targets]
+</screen>
+	The user account password may be set using this syntax:
+<screen>
+net rpc password &lt;username&gt; [&lt;password&gt;] -Uadmin_username%admin_pass
+</screen>
+	</para>
+
+	<para>
+	The following demonstrates the addition of an account to the server <constant>FRODO</constant>:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user add</tertiary></indexterm>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user password</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc user add jacko -S FRODO -Uroot%not24get
+Added user jacko
+</screen>
+	The account password can be set with the following methods (all show the same operation):
+<screen>
+&rootprompt; net rpc password jacko f4sth0rse -S FRODO -Uroot%not24get
+&rootprompt; net rpc user password jacko f4sth0rse \
+    -S FRODO -Uroot%not24get
+</screen>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Deletion of User Accounts</title>
+
+	<para>
+	Deletion of a user account can be done using the following syntax:
+<screen>
+net [&lt;method&gt;] user DELETE &lt;name&gt; [misc. options] [targets]
+</screen>
+	The following command will delete the user account <constant>jacko</constant>:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user delete</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc user delete jacko -Uroot%not24get
+Deleted user account
+</screen>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Managing User Accounts</title>
+
+	<para>
+	Two basic user account operations are routinely used: change of password and querying which groups a user
+	is a member of. The change of password operation is shown in <link linkend="sbeuseraddn"/>.
+	</para>
+
+	<para>
+	The ability to query Windows group membership can be essential. Here is how a remote server may be
+	interrogated to find which groups a user is a member of:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user info</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc user info jacko -S SAURON -Uroot%not24get
+net rpc user info jacko -S SAURON -Uroot%not24get
+Domain Users
+Domain Admins
+Engineers
+TorridGroup
+BOP Shop
+Emergency Services
+</screen>
+	</para>
+
+	<para>
+	It is also possible to rename user accounts:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user rename</tertiary></indexterm>oldusername newusername
+	Note that this operation does not yet work against Samba Servers. It is, however, possible to rename useraccounts on
+	Windows Servers.
+
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>User Mapping</title>
+
+	<para>
+<indexterm><primary>logon name</primary></indexterm>
+<indexterm><primary>/etc/samba/smbusers</primary></indexterm>
+<indexterm><primary>username map</primary></indexterm>
+	In some situations it is unavoidable that a user's Windows logon name will differ from the login ID
+	that user has on the Samba server. It is possible to create a special file on the Samba server that
+	will permit the Windows user name to be mapped to a different UNIX/Linux user name. The &smb.conf;
+	file must also be amended so that the <constant>[global]</constant> stanza contains the parameter:
+<screen>
+username map = /etc/samba/smbusers
+</screen>
+	The content of the <filename>/etc/samba/smbusers</filename> file is shown here:
+<screen>
+parsonsw: "William Parsons"
+marygee: geeringm
+</screen>
+	In this example the Windows user account <quote>William Parsons</quote> will be mapped to the UNIX user
+	<constant>parsonsw</constant>, and the Windows user account <quote>geeringm</quote> will be mapped to the
+	UNIX user <constant>marygee</constant>.
+	</para>
+
+	</sect2>
+
+	</sect1>
+
+	<sect1>
+	<title>Administering User Rights and Privileges</title>
+
+	<para>
+<indexterm><primary>credentials</primary></indexterm>
+<indexterm><primary>manage printers</primary></indexterm>
+<indexterm><primary>manage shares</primary></indexterm>
+<indexterm><primary>manage groups</primary></indexterm>
+<indexterm><primary>manage users</primary></indexterm>
+	With all versions of Samba earlier than 3.0.11 the only account on a Samba server that could
+	manage users, groups, shares, printers, and such was the <constant>root</constant> account. This caused
+	problems for some users and was a frequent source of scorn over the necessity to hand out the
+	credentials for the most security-sensitive account on a UNIX/Linux system.
+	</para>
+
+	<para>
+<indexterm><primary>delegate administrative privileges</primary></indexterm>
+<indexterm><primary>normal user</primary></indexterm>
+<indexterm><primary>rights and privilege</primary></indexterm>
+<indexterm><primary>privilege management</primary></indexterm>
+<indexterm><primary>groups of users</primary></indexterm>
+	New to Samba version 3.0.11 is the ability to delegate administrative privileges as necessary to either
+	a normal user or to groups of users. The significance of the administrative privileges is documented
+	in <link linkend="rights"/>. Examples of use of the <command>net</command> for user rights and privilege
+	management is appropriate to this chapter.
+	</para>
+
+	<note><para>
+	When user rights and privileges are correctly set, there is no longer a need for a Windows
+	network account for the <constant>root</constant> user (nor for any synonym of it) with a UNIX UID=0.
+	Initial user rights and privileges can be assigned by any account that is a member of the <constant>
+	Domain Admins</constant> group. Rights can be assigned to user as well as group accounts.
+	</para></note>
+
+	<para>
+	By default, no privileges and rights are assigned. This is demonstrated by executing the command
+	shown here:
+<screen>
+&rootprompt; net rpc rights list accounts -U root%not24get
+BUILTIN\Print Operators
+No privileges assigned
+
+BUILTIN\Account Operators
+No privileges assigned
+
+BUILTIN\Backup Operators
+No privileges assigned
+
+BUILTIN\Server Operators
+No privileges assigned
+
+BUILTIN\Administrators
+No privileges assigned
+
+Everyone
+No privileges assigned
+</screen>
+	</para>
+
+	<para>
+	The <command>net</command> command can be used to obtain the currently supported capabilities for rights
+	and privileges using this method:
+<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
+<indexterm><primary>SePrintOperatorPrivilege</primary></indexterm>
+<indexterm><primary>SeAddUsersPrivilege</primary></indexterm>
+<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
+<indexterm><primary>SeDiskOperatorPrivilege</primary></indexterm>
+<indexterm><primary>SeBackupPrivilege</primary></indexterm>
+<indexterm><primary>SeRestorePrivilege</primary></indexterm>
+<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>rights list</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc rights list -U root%not24get
+     SeMachineAccountPrivilege  Add machines to domain
+      SePrintOperatorPrivilege  Manage printers
+           SeAddUsersPrivilege  Add users and groups to the domain
+     SeRemoteShutdownPrivilege  Force shutdown from a remote system
+       SeDiskOperatorPrivilege  Manage disk shares
+             SeBackupPrivilege  Back up files and directories
+            SeRestorePrivilege  Restore files and directories
+      SeTakeOwnershipPrivilege  Take ownership of files or other objects
+</screen>
+	Machine account privilege is necessary to permit a Windows NT4 or later network client to be added to the
+	domain. The disk operator privilege is necessary to permit the user to manage share ACLs and file and
+	directory ACLs for objects not owned by the user.
+	</para>
+
+	<para>
+	In this example, all rights are assigned to the <constant>Domain Admins</constant> group. This is a good
+	idea since members of this group are generally expected to be all-powerful. This assignment makes that
+	the reality:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>rights grant</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc rights grant "MIDEARTH\Domain Admins" \
+    SeMachineAccountPrivilege SePrintOperatorPrivilege \
+    SeAddUsersPrivilege SeRemoteShutdownPrivilege \
+    SeDiskOperatorPrivilege  -U root%not24get
+Successfully granted rights.
+</screen>
+	Next, the domain user <constant>jht</constant> is given the privileges needed for day-to-day
+	administration:
+<screen>
+&rootprompt; net rpc rights grant "MIDEARTH\jht" \
+    SeMachineAccountPrivilege SePrintOperatorPrivilege \
+    SeAddUsersPrivilege SeDiskOperatorPrivilege \
+    -U root%not24get
+Successfully granted rights.
+</screen>
+	</para>
+
+	<para>
+	The following step permits validation of the changes just made:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>rights list accounts</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc rights list accounts -U root%not24get
+MIDEARTH\jht
+SeMachineAccountPrivilege
+SePrintOperatorPrivilege
+SeAddUsersPrivilege
+SeDiskOperatorPrivilege
+
+BUILTIN\Print Operators
+No privileges assigned
+
+BUILTIN\Account Operators
+No privileges assigned
+
+BUILTIN\Backup Operators
+No privileges assigned
+
+BUILTIN\Server Operators
+No privileges assigned
+
+BUILTIN\Administrators
+No privileges assigned
+
+Everyone
+No privileges assigned
+
+MIDEARTH\Domain Admins
+SeMachineAccountPrivilege
+SePrintOperatorPrivilege
+SeAddUsersPrivilege
+SeRemoteShutdownPrivilege
+SeDiskOperatorPrivilege
+</screen>
+	</para>
+
+	</sect1>
+
+	<sect1>
+	<title>Managing Trust Relationships</title>
+
+	<para>
+	There are essentially two types of trust relationships: the first is between domain controllers and domain
+	member machines (network clients), the second is between domains (called interdomain trusts). All
+	Samba servers that participate in domain security require a domain membership trust account, as do like
+	Windows NT/200x/XP workstations.
+	</para>
+
+	<sect2>
+	<title>Machine Trust Accounts</title>
+
+	<para>
+	The net command looks in the &smb.conf; file to obtain its own configuration settings. Thus, the following
+	command 'knows' which domain to join from the &smb.conf; file.
+	</para>
+
+	<para>
+	A Samba server domain trust account can be validated as shown in this example:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>testjoin</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc testjoin
+Join to 'MIDEARTH' is OK
+</screen>
+	Where there is no domain membership account, or when the account credentials are not valid, the following
+	results will be observed:
+<screen>
+net rpc testjoin -S DOLPHIN
+Join to domain 'WORLDOCEAN' is not valid
+</screen>
+	</para>
+
+	<para>
+	The equivalent command for joining a Samba server to a Windows ADS domain is shown here:
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>testjoin</tertiary></indexterm>
+<screen>
+&rootprompt; net ads testjoin
+Using short domain name -- TAKEAWAY
+Joined 'LEMONADE' to realm 'TAKEAWAY.BIZ'
+</screen>
+	In the event that the ADS trust was not established, or is broken for one reason or another, the following
+	error message may be obtained:
+<screen>
+&rootprompt; net ads testjoin -UAdministrator%secret
+Join to domain is not valid
+</screen>
+	</para>
+
+	<para>
+	The following demonstrates the process of creating a machine trust account in the target domain for the
+	Samba server from which the command is executed:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc join -S FRODO -Uroot%not24get
+Joined domain MIDEARTH.
+</screen>
+	The joining of a Samba server to a Samba domain results in the creation of a machine account. An example
+	of this is shown here:
+<screen>
+&rootprompt; pdbedit -Lw merlin\$
+merlin$:1009:9B4489D6B90461FD6A3EC3AB96147E16:\
+176D8C554E99914BDF3407DEA2231D80:[S          ]:LCT-42891919:
+</screen>
+	The S in the square brackets means this is a server (PDC/BDC) account. The domain join can be cast to join
+	purely as a workstation, in which case the S is replaced with a W (indicating a workstation account). The
+	following command can be used to affect this:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join member</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc join member -S FRODO -Uroot%not24get
+Joined domain MIDEARTH.
+</screen>
+	Note that the command-line parameter <constant>member</constant> makes this join specific. By default
+	the type is deduced from the &smb.conf; file configuration. To specifically join as a PDC or BDC, the
+	command-line parameter will be <constant>[PDC | BDC]</constant>. For example:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join bdc</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc join bdc -S FRODO -Uroot%not24get
+Joined domain MIDEARTH.
+</screen>
+	It is best to let Samba figure out the domain join type from the settings in the &smb.conf; file.
+	</para>
+
+	<para>
+	The command to join a Samba server to a Windows ADS domain is shown here:
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
+<screen>
+&rootprompt; net ads join -UAdministrator%not24get
+Using short domain name -- GDANSK
+Joined 'FRANDIMITZ' to realm 'GDANSK.ABMAS.BIZ'
+</screen>
+	</para>
+
+	<para>
+	There is no specific option to remove a machine account from an NT4 domain. When a domain member that is a
+	Windows machine is withdrawn from the domain, the domain membership account is not automatically removed
+	either. Inactive domain member accounts can be removed using any convenient tool. If necessary, the
+	machine account can be removed using the following <command>net</command> command:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user delete</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc user delete HERRING\$ -Uroot%not24get
+Deleted user account.
+</screen>
+	The removal is made possible because machine accounts are just like user accounts with a trailing $
+	character. The account management operations treat user and machine accounts in like manner.
+	</para>
+
+	<para>
+	A Samba-3 server that is a Windows ADS domain member can execute the following command to detach from the
+	domain:
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>leave</tertiary></indexterm>
+<screen>
+&rootprompt; net ads leave
+</screen>
+	</para>
+
+	<para>
+	Detailed information regarding an ADS domain can be obtained by a Samba DMS machine by executing the
+	following:
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>status</tertiary></indexterm>
+<screen>
+&rootprompt; net ads status
+</screen>
+	The volume of information is extensive. Please refer to the book <quote>Samba-3 by Example</quote>,
+	Chapter 7 for more information regarding its use. This book may be obtained either in print or online from
+	the <ulink url="http://www.samba.org/samba/docs/Samba3-ByExample.pdf">Samba-3 by Example</ulink>.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Interdomain Trusts</title>
+
+	<para>
+	Interdomain trust relationships form the primary mechanism by which users from one domain can be granted
+	access rights and privileges in another domain. 
+	</para>
+
+	<para>
+	To discover what trust relationships are in effect, execute this command:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom list</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc trustdom list -Uroot%not24get
+Trusted domains list:
+
+none
+
+Trusting domains list:
+
+none
+</screen>
+	There are no interdomain trusts at this time; the following steps will create them.
+	</para>
+
+	<para>
+	It is necessary to create a trust account in the local domain. A domain controller in a second domain can
+	create a trusted connection with this account. That means that the foreign domain is being trusted
+	to access resources in the local domain. This command creates the local trust account:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom add</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc trustdom add DAMNATION f00db4r -Uroot%not24get
+</screen>
+	The account can be revealed by using the <command>pdbedit</command> as shown here:
+<screen>
+&rootprompt; pdbedit -Lw DAMNATION\$
+DAMNATION$:1016:9AC1F121DF897688AAD3B435B51404EE: \
+7F845808B91BB9F7FEF44B247D9DC9A6:[I         ]:LCT-428934B1:
+</screen>
+	A trust account will always have an I in the field within the square brackets.
+	</para>
+
+	<para>
+	If the trusting domain is not capable of being reached, the following command will fail:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom list</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc trustdom list -Uroot%not24get
+Trusted domains list:
+
+none
+
+Trusting domains list:
+
+DAMNATION           S-1-5-21-1385457007-882775198-1210191635
+</screen>
+	The above command executed successfully; a failure is indicated when the following response is obtained:
+<screen>
+net rpc trustdom list -Uroot%not24get
+Trusted domains list:
+
+DAMNATION           S-1-5-21-1385457007-882775198-1210191635
+
+Trusting domains list:
+
+DAMNATION           domain controller is not responding
+</screen>
+	</para>
+
+	<para>
+	Where a trust account has been created on a foreign domain, Samba is able to establish the trust (connect with)
+	the foreign account. In the process it creates a one-way trust to the resources on the remote domain. This
+	command achieves the objective of joining the trust relationship:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom establish</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc trustdom establish DAMNATION
+Password: xxxxxxx	== f00db4r
+Could not connect to server TRANSGRESSION
+Trust to domain DAMNATION established
+</screen>
+	Validation of the two-way trust now established is possible as shown here:
+<screen>
+&rootprompt; net rpc trustdom list -Uroot%not24get
+Trusted domains list:
+
+DAMNATION           S-1-5-21-1385457007-882775198-1210191635
+
+Trusting domains list:
+
+DAMNATION           S-1-5-21-1385457007-882775198-1210191635
+</screen>
+	</para>
+
+	<para>
+	Sometimes it is necessary to remove the ability for local users to access a foreign domain. The trusting
+	connection can be revoked as shown here:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom revoke</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc trustdom revoke DAMNATION -Uroot%not24get
+</screen>
+	At other times it becomes necessary to remove the ability for users from a foreign domain to be able to
+	access resources in the local domain. The command shown here will do that:
+<screen>
+&rootprompt; net rpc trustdom del DAMNATION -Uroot%not24get
+</screen>
+
+	</para>
+
+	</sect2>
+
+	</sect1>
+
+	<sect1>
+	<title>Managing Security Identifiers (SIDS)</title>
+
+	<para>
+<indexterm><primary>security identifier</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>desktop profiles</primary></indexterm>
+<indexterm><primary>user encoded</primary></indexterm>
+<indexterm><primary>group SID</primary></indexterm>
+	The basic security identifier that is used by all Windows networking operations is the Windows security
+	identifier (SID). All Windows network machines (servers and workstations), users, and groups are
+	identified by their respective SID. All desktop profiles are also encoded with user and group SIDs that
+	are specific to the SID of the domain to which the user belongs.
+	</para>
+
+	<para>
+<indexterm><primary>machine SID</primary></indexterm>
+<indexterm><primary>domain SID</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>rejoin</primary></indexterm>
+	It is truly prudent to store the machine and/or domain SID in a file for safekeeping. Why? Because 
+	a change in hostname or in the domain (workgroup) name may result in a change in the SID. When you
+	have the SID on hand, it is a simple matter to restore it. The alternative is to suffer the pain of
+	having to recover user desktop profiles and perhaps rejoin all member machines to the domain.
+	</para>
+
+	<para>
+	First, do not forget to store the local SID in a file. It is a good idea to put this in the directory
+	in which the &smb.conf; file is also stored. Here is a simple action to achieve this:
+<indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
+<screen>
+&rootprompt; net getlocalsid > /etc/samba/my-sid
+</screen>
+	Good, there is now a safe copy of the local machine SID. On a PDC/BDC this is the domain SID also.
+	</para>
+
+	<para>
+	The following command reveals what the former one should have placed into the file called
+	<filename>my-sid</filename>:
+<screen>
+&rootprompt; net getlocalsid
+SID for domain MERLIN is: S-1-5-21-726309263-4128913605-1168186429
+</screen>
+	</para>
+
+	<para>
+	If ever it becomes necessary to restore the SID that has been stored in the <filename>my-sid</filename>
+	file, simply copy the SID (the string of characters that begins with <constant>S-1-5-21</constant>) to
+	the command line shown here:
+<indexterm><primary>net</primary><secondary>setlocalsid</secondary></indexterm>
+<screen>
+&rootprompt; net setlocalsid S-1-5-21-1385457007-882775198-1210191635
+</screen>
+	Restoration of a machine SID is a simple operation, but the absence of a backup copy can be very
+	problematic.
+	</para>
+
+	<para>
+	The following operation is useful only for machines that are being configured as a PDC or a BDC.
+	DMS and workstation clients should have their own machine SID to avoid
+	any potential namespace collision. Here is the way that the BDC SID can be synchronized to that
+	of the PDC (this is the default NT4 domain practice also):
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>getsid</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc getsid -S FRODO -Uroot%not24get
+Storing SID S-1-5-21-726309263-4128913605-1168186429 \
+    for Domain MIDEARTH in secrets.tdb
+</screen>
+	Usually it is not necessary to specify the target server (-S FRODO) or the administrator account
+	credentials (-Uroot%not24get).
+	</para>
+
+	</sect1>
+	
+	<sect1>
+	<title>Share Management</title>
+
+	<para>
+	Share management is central to all file serving operations. Typical share operations include:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>Creation/change/deletion of shares</para></listitem>
+		<listitem><para>Setting/changing ACLs on shares</para></listitem>
+		<listitem><para>Moving shares from one server to another</para></listitem>
+		<listitem><para>Change of permissions of share contents</para></listitem>
+	</itemizedlist>
+
+	<para>
+	Each of these are dealt with here insofar as they involve the use of the <command>net</command>
+	command. Operations outside of this command are covered elsewhere in this document.
+	</para>
+
+	<sect2>
+	<title>Creating, Editing, and Removing Shares</title>
+
+	<para>
+	A share can be added using the <command>net rpc share</command> command capabilities.
+	The target machine may be local or remote and is specified by the -S option. It must be noted
+	that the addition and deletion of shares using this tool depends on the availability of a suitable
+	interface script. The interface scripts Sambas <command>smbd</command> uses are called
+	<smbconfoption name="add share command"/>, <smbconfoption name="delete share command"/> and
+	<smbconfoption name="change share command"/> A set of example scripts are provided in the Samba source
+	code tarball in the directory <filename>~samba/examples/scripts</filename>.
+	</para>
+
+	<para>
+	The following steps demonstrate the use of the share management capabilities of the <command>net</command>
+	utility. In the first step a share called <constant>Bulge</constant> is added. The sharepoint within the
+	file system is the directory <filename>/data</filename>. The command that can be executed to perform the
+	addition of this share is shown here:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share add</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc share add Bulge=/data -S MERLIN -Uroot%not24get
+</screen>
+	Validation is an important process, and by executing the command <command>net rpc share</command>
+	with no other operators it is possible to obtain a listing of available shares, as shown here:
+<screen>
+&rootprompt; net rpc share -S MERLIN -Uroot%not24get
+profdata
+archive
+Bulge   &lt;--- This one was added
+print$
+netlogon
+profiles
+IPC$
+kyocera
+ADMIN$
+</screen>
+	</para>
+
+	<para>
+	Often it is desirable also to permit a share to be removed using a command-line tool.
+	The following step permits the share that was previously added to be removed:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share delete</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc share delete Bulge -S MERLIN -Uroot%not24get
+</screen>
+	A simple validation shown here demonstrates that the share has been removed:
+<screen>
+&rootprompt; net rpc share -S MERLIN -Uroot%not24get
+profdata
+archive
+print$
+netlogon
+profiles
+IPC$
+ADMIN$
+kyocera
+</screen>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Creating and Changing Share ACLs</title>
+
+	<para>
+	At this time the <command>net</command> tool cannot be used to manage ACLs on Samba shares. In MS Windows 
+	language this is called Share Permissions.
+	</para>
+
+	<para>
+	It is possible to set ACLs on Samba shares using either the SRVTOOLS NT4 Domain Server Manager
+	or using the Computer Management MMC snap-in. Neither is covered here,
+	but see <link linkend="AccessControls"/>.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Share, Directory, and File Migration</title>
+
+	<para>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>vampire</tertiary></indexterm>
+	Shares and files can be migrated in the same manner as user, machine, and group accounts.
+	It is possible to preserve access control settings (ACLs) as well as security settings
+	throughout the migration process. The <command>net rpc vampire</command> facility is used
+	to migrate accounts from a Windows NT4 (or later) domain to a Samba server. This process
+	preserves passwords and account security settings and is a precursor to the migration
+	of shares and files.
+	</para>
+
+	<para>
+	The <command>net rpc share</command> command may be used to migrate shares, directories,
+	files, and all relevant data from a Windows server to a Samba server.
+	</para>
+
+	<para>
+	A set of command-line switches permit the creation of almost direct clones of Windows file
+	servers. For example, when migrating a fileserver, file ACLs and DOS file attributes from
+	the Windows server can be included in the migration process and will reappear, almost identically,
+	on the Samba server when the migration has been completed.
+	</para>
+
+	<para>
+	The migration process can be completed only with the Samba server already being fully operational.
+	The user and group accounts must be migrated before attempting to migrate data
+	share, files, and printers. The migration of files and printer configurations involves the use
+	of both SMB and MS DCE RPC services. The benefit of the manner in which the migration process has
+	been implemented is that the possibility now exists to use a Samba server as a man-in-middle migration
+	service that affects a transfer of data from one server to another. For example, if the Samba
+	server is called MESSER, the source Windows NT4 server is called PEPPY, and the target Samba
+	server is called GONZALES, the machine MESSER can be used to effect the migration of all data
+	(files and shares) from PEPPY to GONZALES. If the target machine is not specified, the local
+	server is assumed by default - as net's general rule of thumb .
+	</para>
+
+	<para>
+	The success of server migration requires a firm understanding of the structure of the source
+	server (or domain) as well as  the processes on which the migration is critically dependant.
+	</para>
+
+	<para>
+	There are two known limitations to the migration process:
+	</para>
+
+	<orderedlist>
+		<listitem><para>
+		The <command>net</command> command requires that the user credentials provided exist on both
+		the migration source and the migration target.
+		</para></listitem>
+
+		<listitem><para>
+		Printer settings may not be fully or may be incorrectly migrated. This might in particular happen
+		when migrating a Windows 2003 print server to Samba.
+		</para></listitem>
+	</orderedlist>
+
+	<sect3>
+	<title>Share Migration</title>
+
+	<para>
+	The <command>net rpc share migrate</command> command operation permits the migration of plain
+	share stanzas. A stanza contains the parameters within which a file or print share are defined.
+	The use of this migration method will create share stanzas that have as parameters the file
+	system directory path, an optional description, and simple security settings that permit write
+	access to files. One of the first steps necessary following migration is to review the share
+	stanzas to ensure that the settings are suitable for use.
+	</para>
+
+	<para>
+	The shares are created on the fly as part of the migration process. The <command>smbd</command>
+	application does this by calling on the operating system to execute the script specified by the 
+	&smb.conf; parameter <parameter>add share command</parameter>.
+	</para>
+
+	<para>
+	There is a suitable example script for the <parameter>add share command</parameter> in the
+	<filename>$SAMBA_SOURCES/examples/scripts</filename> directory. It should be noted that
+	the account that is used to drive the migration must, of necessity, have appropriate file system
+	access privileges and have the right to create shares and to set ACLs on them. Such rights are
+	conferred by these rights: <parameter>SeAddUsersPrivilege</parameter> and <parameter>SeDiskOperatorPrivilege</parameter>.
+	For more information regarding rights and privileges please refer to <link linkend="rights"/>.
+	</para>
+
+	<para>
+	The syntax of the share migration command is shown here:
+<screen>
+net rpc share MIGRATE SHARES &lt;share-name&gt; -S &lt;source&gt;
+        [--destination=localhost] [--exclude=share1,share2] [-v]
+</screen>
+	When the parameter &lt;share-name&gt; is omitted, all shares will be migrated. The potentially
+	large list of available shares on the system that is being migrated can be limited using the
+	<parameter>--exclude</parameter> switch. For example:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share migrate</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc share migrate shares myshare\
+         -S win2k -U administrator%secret"
+</screen>
+	This will migrate the share <constant>myshare</constant> from the server <constant>win2k</constant>
+	to the Samba Server using the permissions that are tied to the account <constant>administrator</constant> 
+	with the password <constant>secret</constant>. The account that is used must be the same on both the
+	migration source server and the target Samba server. The use of the <command>net rpc
+	vampire</command>, prior to attempting the migration of shares, will ensure that accounts will be
+	identical on both systems. One precaution worth taking before commencement of migration of shares is
+	to validate that the migrated accounts (on the Samba server) have the needed rights and privileges.
+	This can be done as shown here:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>right list accounts</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc right list accounts -Uroot%not24get
+</screen>
+	The steps taken so far perform only the migration of shares. Directories and directory contents
+	are not migrated by the steps covered up to this point.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>File and Directory Migration</title>
+
+	<para>
+	Everything covered to this point has been done in preparation for the migration of file and directory
+	data. For many people preparation is potentially boring and the real excitement only begins when file
+	data can be used. The next steps demonstrate the techniques that can be used to transfer (migrate)
+	data files using the <command>net</command> command.
+	</para>
+
+	<para>
+	Transfer of files from one server to another has always been a challenge for MS Windows
+	administrators because Windows NT and 200X servers do not always include the tools needed. The
+	<command>xcopy</command> from Windows NT is not capable of preserving file and directory ACLs, 
+	it does so only with Windows 200x. Microsoft does provide a
+	utility that can copy ACLs (security settings) called <command>scopy</command>, but it is provided only
+	as part of the Windows NT or 200X Server Resource Kit.
+	</para>
+
+	<para>
+	There are several tools, both commercial and freeware, that can be used from a Windows server to copy files
+	and directories with full preservation of security settings. One of the best known of the free tools is
+	called <command>robocopy</command>.
+	</para>
+
+	<para>
+	The <command>net</command> utility can be used to copy files and directories with full preservation of
+	ACLs as well as DOS file attributes. Note that including ACLs makes sense only where the destination
+	system will operate within the same security context as the source system. This applies both to a
+	DMS and to domain controllers that result from a vampired domain.
+	Before file and directory migration, all shares must already exist.
+	</para>
+
+	<para>
+	The syntax for the migration commands is shown here:
+<screen>
+net rpc share MIGRATE FILES &lt;share-name&gt; -S &lt;source&gt;
+    [--destination=localhost] [--exclude=share1,share2]
+    [--acls] [--attrs] [--timestamps] [-v]
+</screen>
+	If the &lt;share-name&gt; parameter is omitted, all shares will be migrated. The potentially large
+	list of shares on the source system can be restricted using the <parameter>--exclude</parameter> command
+	switch.
+	</para>
+
+	<para>
+	Where it is necessary to preserve all file ACLs, the <parameter>--acls</parameter> switch should be added
+	to the above command line. Original file timestamps can be preserved by specifying the
+	<parameter>--timestamps</parameter> switch, and the DOS file attributes (i.e., hidden, archive, etc.) can
+	be preserved by specifying the <parameter>--attrs</parameter> switch.
+	</para>
+
+	<note><para>
+	The ability to preserve ACLs depends on appropriate support for ACLs as well as the general file system
+	semantics of the host operating system on the target server. A migration from one Windows file server to
+	another will perfectly preserve all file attributes. Because of the difficulty of mapping Windows ACLs
+	onto a POSIX ACLs-supporting system, there can be no perfect migration of Windows ACLs to a Samba server.
+	</para></note>
+
+	<para>
+	The ACLs that result on a Samba server will most probably not match the originating ACLs. Windows supports
+	the possibility of files that are owned only by a group. Group-alone file ownership is not possible under
+	UNIX/Linux. Errors in migrating group-owned files can be avoided by using the &smb.conf; file
+	<smbconfoption name="force unknown acl user">yes</smbconfoption> parameter. This facility will
+	automatically convert group-owned files into correctly user-owned files on the Samba server.
+	</para>
+
+	<para>
+	An example for migration of files from a machine called <constant>nt4box</constant> to the Samba server
+	from which the process will be handled is shown here:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share migrate files</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc share migrate files -S nt4box --acls \
+    --attrs -U administrator%secret
+</screen>
+	</para>
+
+	<para>
+	This command  will migrate all files and directories from all file shares on the Windows server called
+	<constant>nt4box</constant> to the Samba server from which migration is initiated. Files that are group-owned
+	will be owned by the user account <constant>administrator</constant>.
+	</para>
+
+	</sect3>
+	
+	<sect3>
+	<title>Share-ACL Migration</title>
+	<para>
+	It is possible to have share-ACLs (security descriptors) that won't allow you, even as Administrator, to
+	copy any files or directories into it. Therefor the migration of the share-ACLs has been put into a separate
+	function:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share migrate security</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc share migrate security -S nt4box -U administrator%secret
+</screen>
+	</para>
+
+	<para>
+	This command will only copy the share-ACL of each share on nt4box to your local samba-system.
+	</para>
+	</sect3>
+
+	<sect3>
+	<title>Simultaneous Share and File Migration</title>
+
+	<para>
+	The operating mode shown here is just a combination of the previous three. It first migrates
+	share definitions and then all shared files and directories and finally migrates the share-ACLs:
+<screen>
+net rpc share MIGRATE ALL &lt;share-name&gt; -S &lt;source&gt;
+    [--exclude=share1, share2] [--acls] [--attrs] [--timestamps] [-v]
+</screen>
+	</para>
+
+	<para>
+	An example of simultaneous migration is shown here:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share migrate all</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc share migrate all -S w2k3server -U administrator%secret
+</screen>
+	This will generate a complete server clone of the <parameter>w2k3server</parameter> server.
+	</para>
+
+	</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Printer Migration</title>
+
+	<para>
+	The installation of a new server, as with the migration to a new network environment, often is similar to
+	building a house; progress is very rapid from the laying of foundations up to the stage at which
+	the house can be locked up, but the finishing off appears to take longer and longer as building
+	approaches completion.
+	</para>
+
+	<para>
+	Printing needs vary greatly depending on the network environment and may be very simple or complex. If
+	the need is very simple, the best solution to the implementation of printing support may well be to
+	re-install everything from a clean slate instead of migrating older configurations. On the other hand,
+	a complex network that is integrated with many international offices and a multiplexity of local branch
+	offices, each of which form an inter-twined maze of printing possibilities, the ability to migrate all
+	printer configurations is decidedly beneficial. To manually re-establish a complex printing network
+	will take much time and frustration. Often it will not be possible to find driver files that are
+	currently in use, necessitating the installation of newer drivers. Newer drivers often implement
+	printing features that will necessitate a change in the printer usage. Additionally, with very complex
+	printer configurations it becomes almost impossible to re-create the same environment &smbmdash; no matter
+	how extensively it has been documented.
+	</para>
+
+	<para>
+	The migration of an existing printing architecture involves the following:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>Establishment of print queues.</para></listitem>
+
+		<listitem><para>Installation of printer drivers (both for the print server and for Windows clients.</para></listitem>
+
+		<listitem><para>Configuration of printing forms.</para></listitem>
+
+		<listitem><para>Implementation of security settings.</para></listitem>
+
+		<listitem><para>Configuration of printer settings.</para></listitem>
+	</itemizedlist>
+
+	<para>
+	The Samba <command>net</command> utility permits printer migration from one Windows print server
+	to another. When this tool is used to migrate printers to a Samba server <command>smbd</command>,
+	the application that receives the network requests to create the necessary services must call out
+	to the operating system in order to create the underlying printers. The call-out is implemented
+	by way of an interface script that can be specified by the &smb.conf; file parameter
+	<smbconfoption id="add printer script"/>. This script is essential to the migration process.
+	A suitable example script may be obtained from the <filename>$SAMBA_SOURCES/examples/scripts</filename>
+	directory. Take note that this script must be customized to suit the operating system environment
+	and may use its tools to create a print queue.
+	</para>
+
+	<para>
+	Each of the components listed above can be completed separately, or they can be completed as part of an
+	automated operation. Many network administrators prefer to deal with migration issues in a manner that
+	gives them the most control, particularly when things go wrong. The syntax for each operation is now
+	briefly described.
+	</para>
+
+	<para>
+	Printer migration from a Windows print server (NT4 or 200x) is shown. This instruction causes the
+	printer share to be created together with the underlying print queue:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate printers</tertiary></indexterm>
+<screen>
+net rpc printer MIGRATE PRINTERS [printer] [misc. options] [targets]
+</screen>
+	Printer drivers can be migrated from the Windows print server to the Samba server using this
+	command-line instruction:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate drivers</tertiary></indexterm>
+<screen>
+net rpc printer MIGRATE DRIVERS [printer] [misc. options] [targets]
+</screen>
+	Printer forms can be migrated with the following operation:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate forms</tertiary></indexterm>
+<screen>
+net rpc printer MIGRATE FORMS [printer] [misc. options] [targets]
+</screen>
+	Printer security settings (ACLs) can be migrated from the Windows server to the Samba server using this command:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate security</tertiary></indexterm>
+<screen>
+net rpc printer MIGRATE SECURITY [printer] [misc. options] [targets]
+</screen>
+	Printer configuration settings include factors such as paper size and default paper orientation.
+	These can be migrated from the Windows print server to the Samba server with this command:
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate settings</tertiary></indexterm>
+<screen>
+net rpc printer MIGRATE SETTINGS [printer] [misc. options] [targets]
+</screen>
+	</para>
+
+	<para>
+	Migration of printers including the above-mentioned sets of information may be completed
+	with a single command using this syntax:
+<screen>
+net rpc printer MIGRATE ALL [printer] [misc. options] [targets]
+</screen>
+	</para>
+
+	</sect2>
+
+	</sect1>
+
+	<sect1>
+	<title>Controlling Open Files</title>
+
+	<para>
+	The man page documents the <command>net file</command> function suite, which provides the tools to
+	close open files using either RAP or RPC function calls. Please refer to the man page for specific
+	usage information.
+	</para>
+
+	</sect1>
+
+	<sect1>
+	<title>Session and Connection Management</title>
+
+	<para>
+	The session management interface of the <command>net session</command> command uses the old RAP
+	method to obtain the list of connections to the Samba server, as shown here:
+<indexterm><primary>net</primary><secondary>rap</secondary><tertiary>session</tertiary></indexterm>
+<screen>
+&rootprompt; net rap session -S MERLIN -Uroot%not24get
+Computer             User name            Client Type        Opens Idle time
+------------------------------------------------------------------------------
+\\merlin             root                 Unknown Client         0 00:00:00
+\\marvel             jht                  Unknown Client         0 00:00:00
+\\maggot             jht                  Unknown Client         0 00:00:00
+\\marvel             jht                  Unknown Client         0 00:00:00
+</screen>
+	</para>
+
+	<para>
+	A session can be closed by executing a command as shown here:
+<screen>
+&rootprompt; net rap session close marvel -Uroot%not24get
+</screen>
+	</para>
+
+	</sect1>
+
+	<sect1>
+	<title>Printers and ADS</title>
+
+	<para>
+	When Samba-3 is used within an MS Windows ADS environment, printers shared via Samba will not be browseable
+	until they have been published to the ADS domain. Information regarding published printers may be obtained
+	from the ADS server by executing the <command>net ads print info</command> command following this syntax:
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>printer info</tertiary></indexterm>
+<screen>
+net ads printer info &lt;printer_name&gt; &lt;server_name&gt; -Uadministrator%secret
+</screen>
+	If the asterisk (*) is used in place of the printer_name argument, a list of all printers will be
+	returned.
+	</para>
+
+	<para>
+	To publish (make available) a printer to ADS, execute the following command:
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>printer publish</tertiary></indexterm>
+<screen>
+net ads printer publish &lt;printer_name&gt; -Uadministrator%secret
+</screen>
+	This publishes a printer from the local Samba server to ADS.
+	</para>
+
+	<para>
+	Removal of a Samba printer from ADS is achieved by executing this command:
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>printer remove</tertiary></indexterm>
+<screen>
+net ads printer remove &lt;printer_name&gt; -Uadministrator%secret
+</screen>
+	</para>
+
+	<para>
+	A generic search (query) can also be made to locate a printer across the entire ADS domain by executing:
+<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>printer search</tertiary></indexterm>
+<screen>
+net ads printer search &lt;printer_name&gt; -Uadministrator%secret
+</screen>
+	</para>
+
+	</sect1>
+
+	<sect1>
+	<title>Manipulating the Samba Cache</title>
+
+	<para>
+	Please refer to the <command>net</command> command man page for information regarding cache management.
+	</para>
+
+	</sect1>
+
+	<sect1>
+	<title>Managing IDMAP UID/SID Mappings</title>
+
+	<para>
+	The IDMAP UID to SID, and SID to UID, mappings that are created by <command>winbindd</command> can be
+	backed up to a text file. The text file can be manually edited, although it is highly recommended that
+	you attempt this only if you know precisely what you are doing.
+	</para>
+
+	<para>
+	An IDMAP text dump file can be restored (or reloaded). There are two situations that may necessitate
+	this action: a) The existing IDMAP file is corrupt, b) It is necessary to install an editted version
+	of the mapping information.
+	</para>
+
+	<para>
+	Winbind must be shut down to dump the IDMAP file. Before restoring a dump file, shut down
+	<command>winbindd</command> and delete the old <filename>winbindd_idmap.tdb</filename> file.
+	</para>
+
+	<sect2>
+	<title>Creating an IDMAP Database Dump File</title>
+
+	<para>
+	The IDMAP database can be dumped to a text file as shown here:
+<screen>
+net idmap dump &lt;full_path_and_tdb_filename&gt; &gt; dumpfile.txt
+</screen>
+	Where a particular build of Samba the run-time tdb files are stored in the
+	<filename>/var/lib/samba</filename> directory the following commands to create the dump file will suffice:
+<screen>
+net idmap dump /var/lib/samba/winbindd_idmap.tdb &gt; idmap_dump.txt
+</screen>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Restoring the IDMAP Database Dump File</title>
+
+	<para>
+	The IDMAP dump file can be restored using the following command:
+<screen>
+net idmap restore &lt;full_path_and_tdb_filename&gt; &lt; dumpfile.txt
+</screen>
+	Where the Samba run-time tdb files are stored in the <filename>/var/lib/samba</filename> directory
+    the following command can be used to restore the data to the tdb file:
+<screen>
+net idmap restore /var/lib/samba/winbindd_idmap.tdb &lt; idmap_dump.txt
+</screen>
+	</para>
+
+	</sect2>
+
+	</sect1>
+
+	<sect1 id="netmisc1">
+	<title>Other Miscellaneous Operations</title>
+
+	<para>
+	The following command is useful for obtaining basic statistics regarding a Samba domain. This command does
+	not work with current Windows XP Professional clients.
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>info</tertiary></indexterm>
+<screen>
+&rootprompt; net rpc info
+Domain Name: RAPIDFLY
+Domain SID: S-1-5-21-399034208-633907489-3292421255
+Sequence number: 1116312355
+Num users: 720
+Num domain groups: 27
+Num local groups: 6
+</screen>
+	</para>
+
+	<para>
+	Another useful tool is the <command>net time</command> tool set. This tool may be used to query the
+	current time on the target server as shown here:
+<indexterm><primary>net</primary><secondary>time</secondary></indexterm>
+<screen>
+&rootprompt; net time -S SAURON
+Tue May 17 00:50:43 2005
+</screen>
+	In the event that it is the intent to pass the time information obtained to the UNIX
+	<command>/bin/time</command>, it is a good idea to obtain the time from the target server in a format
+	that is ready to be passed through. This may be done by executing:
+<indexterm><primary>net</primary><secondary>time</secondary><tertiary>system</tertiary></indexterm>
+<screen>
+&rootprompt; net time system -S FRODO
+051700532005.16
+</screen>
+	The time can be set on a target server by executing:
+<indexterm><primary>net</primary><secondary>time</secondary><tertiary>set</tertiary></indexterm>
+<screen>
+&rootprompt; net time set -S MAGGOT -U Administrator%not24get
+Tue May 17 00:55:30 MDT 2005
+</screen>
+	It is possible to obtain the time zone of a server by executing the following command against it:
+<indexterm><primary>net</primary><secondary>time</secondary><tertiary>zone</tertiary></indexterm>
+<screen>
+&rootprompt; net time zone -S SAURON
+-0600
+</screen>
+	</para>
+
+	</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Unicode.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Unicode.xml
new file mode 100644
index 00000000000..d4318995a1c
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Unicode.xml
@@ -0,0 +1,571 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="unicode">
+<chapterinfo>
+	&author.jelmer;
+	&author.jht;
+	<author>
+		<firstname>TAKAHASHI</firstname><surname>Motonobu</surname>
+		<affiliation>
+		<address><email>monyo@home.monyo.com</email></address>
+		</affiliation>
+		<contrib>Japanese character support</contrib>
+	</author>
+	<pubdate>25 March 2003</pubdate>
+</chapterinfo>
+
+<title>Unicode/Charsets</title>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>use computer anywhere</primary></indexterm>
+Every industry eventually matures. One of the great areas of maturation is in
+the focus that has been given over the past decade to make it possible for anyone
+anywhere to use a computer. It has not always been that way. In fact, not so long
+ago, it was common for software to be written for exclusive use in the country of
+origin.
+</para>
+
+<para>
+Of all the effort that has been brought to bear on providing native
+language support for all computer users, the efforts of the
+<ulink url="http://www.openi18n.org/">Openi18n organization</ulink>
+is deserving of special mention.
+</para>
+
+<para>
+<indexterm><primary>codepages</primary></indexterm>
+Samba-2.x supported a single locale through a mechanism called 
+<emphasis>codepages</emphasis>. Samba-3 is destined to become a truly transglobal
+file- and printer-sharing platform.
+</para>
+
+</sect1>
+
+<sect1>
+<title>What Are Charsets and Unicode?</title>
+
+<para>
+<indexterm><primary>character set</primary></indexterm>
+Computers communicate in numbers. In texts, each number is 
+translated to a corresponding letter. The meaning that will be assigned 
+to a certain number depends on the <emphasis>character set (charset)
+</emphasis> that is used. 
+</para>
+
+<para>
+<indexterm><primary>charset</primary></indexterm>
+<indexterm><primary>ASCII</primary></indexterm>
+A charset can be seen as a table that is used to translate numbers to 
+letters. Not all computers use the same charset (there are charsets 
+with German umlauts, Japanese characters, and so on). The American Standard Code
+for Information Interchange (ASCII) encoding system has been the normative character
+encoding scheme used by computers to date. This employs a charset that contains 
+256 characters. Using this mode of encoding, each character takes exactly one byte.
+</para>
+
+<para>
+<indexterm><primary>multibyte charsets</primary></indexterm>
+<indexterm><primary>extended characters</primary></indexterm>
+There are also charsets that support extended characters, but those need at least
+twice as much storage space as does ASCII encoding. Such charsets can contain
+<command>256 * 256 = 65536</command> characters, which is more than all possible
+characters one could think of. They are called multibyte charsets because they use
+more then one byte to store one character. 
+</para>
+
+<para>
+<indexterm><primary>unicode</primary></indexterm>
+One standardized multibyte charset encoding scheme is known as
+<ulink url="http://www.unicode.org/">unicode</ulink>.  A big advantage of using a
+multibyte charset is that you only need one. There is no need to make sure two
+computers use the same charset when they are communicating.
+</para>
+
+<para>
+<indexterm><primary>single-byte charsets</primary></indexterm>
+<indexterm><primary>SMB/CIFS</primary></indexterm>
+<indexterm><primary>negotiating the charset</primary></indexterm>
+Old Windows clients use single-byte charsets, named 
+<parameter>codepages</parameter>, by Microsoft. However, there is no support for 
+negotiating the charset to be used in the SMB/CIFS protocol. Thus, you 
+have to make sure you are using the same charset when talking to an older client.
+Newer clients (Windows NT, 200x, XP) talk Unicode over the wire.
+</para>
+</sect1>
+
+<sect1>
+<title>Samba and Charsets</title>
+
+<para>
+<indexterm><primary>Unicode</primary></indexterm>
+<indexterm><primary>character sets</primary></indexterm>
+As of Samba-3, Samba can (and will) talk Unicode over the wire. Internally, 
+Samba knows of three kinds of character sets: 
+</para>
+
+<variablelist>
+	<varlistentry>
+		<term><smbconfoption name="unix charset"/></term>
+		<listitem><para>
+<indexterm><primary>UTF-8</primary></indexterm>
+<indexterm><primary>CP850</primary></indexterm>
+		This is the charset used internally by your operating system. 
+		The default is <constant>UTF-8</constant>, which is fine for most 
+		systems and covers all characters in all languages. The default
+		in previous Samba releases was to save filenames in the encoding of the 
+		clients &smbmdash; for example, CP850 for Western European countries.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term><smbconfoption name="display charset"/></term>
+		<listitem><para>This is the charset Samba uses to print messages
+		on your screen. It should generally be the same as the <parameter>unix charset</parameter>.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term><smbconfoption name="dos charset"/></term>
+		<listitem><para>This is the charset Samba uses when communicating with 
+		DOS and Windows 9x/Me clients. It will talk Unicode to all newer clients.
+		The default depends on the charsets you have installed on your system.
+		Run <command>testparm -v | grep &quot;dos charset&quot;</command> to see 
+		what the default is on your system. 
+		</para></listitem>
+	</varlistentry>
+</variablelist>
+
+</sect1>
+
+<sect1>
+<title>Conversion from Old Names</title>
+
+<para>
+<indexterm><primary>charset conversion</primary></indexterm>
+Because previous Samba versions did not do any charset conversion, 
+characters in filenames are usually not correct in the UNIX charset but only 
+for the local charset used by the DOS/Windows clients.
+</para>
+
+<para>Bjoern Jacke has written a utility named <ulink url="http://j3e.de/linux/convmv/">convmv</ulink>
+that can convert whole directory structures to different charsets with one single command. 
+</para>
+
+</sect1>
+
+<sect1>
+<title>Japanese Charsets</title>
+
+<para>
+Setting up Japanese charsets is quite difficult. This is mainly because:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+<indexterm><primary>JIS X 0208</primary></indexterm>
+		The Windows character set is extended from the original legacy Japanese
+		standard (JIS X 0208) and is not standardized. This means that the strictly
+		standardized implementation cannot support the full Windows character set.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>Shift_JIS</primary></indexterm>
+<indexterm><primary>EUC-JP</primary></indexterm>
+<indexterm><primary>CAP</primary></indexterm>
+<indexterm><primary>HEX</primary></indexterm>
+<indexterm><primary>Japanese</primary></indexterm>
+		Mainly for historical reasons, there are several encoding methods in
+		Japanese, which are not fully compatible with each other. There are
+		two major encoding methods. One is the Shift_JIS series used in Windows
+		and some UNIXes. The other is the EUC-JP series used in most UNIXes
+		and Linux. Moreover, Samba previously also offered several unique encoding
+		methods, named CAP and HEX, to keep interoperability with CAP/NetAtalk and
+		UNIXes that can't use Japanese filenames.  Some implementations of the
+		EUC-JP series can't support the full Windows character set.
+	</para></listitem>
+
+	<listitem><para>There are some code conversion tables between Unicode and legacy
+		Japanese character sets. One is compatible with Windows, another one
+		is based on the reference of the Unicode consortium, and others are 
+		a mixed implementation. The Unicode consortium does not officially
+		define any conversion tables between Unicode and legacy character
+		sets, so there cannot be standard one.
+	</para></listitem>
+
+	<listitem><para>The character set and conversion tables available in iconv() depend
+		on the iconv library that is available. Next to that, the Japanese locale 
+		names may be different on different systems.  This means that the value of 
+		the charset parameters depends on the implementation of iconv() you are using.
+		</para>
+
+		<para>
+<indexterm><primary>UCS-2</primary></indexterm>
+<indexterm><primary>Shift_JIS</primary></indexterm>
+<indexterm><primary>ASCII</primary></indexterm>
+<indexterm><primary>English</primary></indexterm>
+		Though 2-byte fixed UCS-2 encoding is used in Windows internally,
+		Shift_JIS series encoding is usually used in Japanese environments
+		as ASCII encoding is in English environments.
+	</para></listitem>
+</itemizedlist>
+
+<sect2><title>Basic Parameter Setting</title>
+
+	<para>
+<indexterm><primary>CP932</primary></indexterm>
+	The <smbconfoption name="dos charset"/> and 
+	<smbconfoption name="display charset"/>
+	should be set to the locale compatible with the character set 
+	and encoding method used on Windows. This is usually CP932
+	but sometimes has a different name.
+	</para>
+
+	<para>
+<indexterm><primary>Shift_JIS</primary></indexterm>
+<indexterm><primary>UTF-8</primary></indexterm>
+<indexterm><primary>EUC-JP</primary></indexterm>
+	The <smbconfoption name="unix charset"/> can be either Shift_JIS series,
+	EUC-JP series, or UTF-8. UTF-8 is always available, but the availability of other locales
+	and the name itself depends on the system.
+	</para>
+
+	<para>
+	Additionally, you can consider using the Shift_JIS series as the
+	value of the <smbconfoption name="unix charset"/>
+	parameter by using the vfs_cap module, which does the same thing as
+	setting <quote>coding system = CAP</quote> in the Samba 2.2 series.
+	</para>
+
+	<para>
+	Where to set <smbconfoption name="unix charset"/>
+	to is a difficult question. Here is a list of details, advantages, and
+	disadvantages of using a certain value.
+	</para>
+
+	<variablelist>
+		<varlistentry><term>Shift_JIS series</term>
+			<listitem><para>
+			Shift_JIS series means a locale that is equivalent to <constant>Shift_JIS</constant>,
+			used as a standard on Japanese Windows. In the case of <constant>Shift_JIS</constant>,
+			for example, if a Japanese filename consists of 0x8ba4 and 0x974c
+			(a 4-bytes Japanese character string meaning <quote>share</quote>) and <quote>.txt</quote>
+			is written from Windows on Samba, the filename on UNIX becomes
+			0x8ba4, 0x974c, <quote>.txt</quote> (an 8-byte BINARY string), same as Windows.
+			</para>
+
+			<para>Since Shift_JIS series is usually used on some commercial-based
+			UNIXes; hp-ux and AIX as the Japanese locale (however, it is also possible
+			to use the EUC-JP locale series). To use Shift_JIS series on these platforms,
+			Japanese filenames created from Windows can be referred to also on
+			UNIX.</para>
+
+			<para>
+			If your UNIX is already working with Shift_JIS and there is a user 
+			who needs to use Japanese filenames written from Windows, the
+			Shift_JIS series is the best choice.  However, broken filenames
+			may be displayed, and some commands that cannot handle non-ASCII
+			filenames may be aborted during parsing filenames. Especially, there
+			may be <quote>\ (0x5c)</quote> in filenames, which need to be handled carefully.
+			It is best to not touch filenames written from Windows on UNIX.
+			</para>
+
+			<para>
+			Note that most Japanized free software actually works with EUC-JP
+			only. It is good practice to verify that the Japanized free software can work
+			with Shift_JIS.
+			</para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry><term>EUC-JP series</term>
+			<listitem><para>
+<indexterm><primary>EUC-JP</primary></indexterm>
+<indexterm><primary>Japanese UNIX</primary></indexterm>
+			EUC-JP series means a locale that is equivalent to the industry
+			standard called EUC-JP, widely used in Japanese UNIX (although EUC
+			contains specifications for languages other than Japanese, such as
+			EUC-KR). In the case of EUC-JP series, for example, if a Japanese
+			filename consists of 0x8ba4 and 0x974c and <quote>.txt</quote> is written from
+			Windows on Samba, the filename on UNIX becomes 0xb6a6, 0xcdad,
+			<quote>.txt</quote> (an 8-byte BINARY string). 
+			</para>
+
+			<para>
+<indexterm><primary>EUC-JP</primary></indexterm>
+<indexterm><primary>UNIX</primary></indexterm>
+<indexterm><primary>Linux</primary></indexterm>
+<indexterm><primary>FreeBSD</primary></indexterm>
+<indexterm><primary>Solaris</primary></indexterm>
+<indexterm><primary>IRIX</primary></indexterm>
+<indexterm><primary>Tru64 UNIX</primary></indexterm>
+<indexterm><primary>Japanese locale</primary></indexterm>
+<indexterm><primary>Shift_JIS</primary></indexterm>
+<indexterm><primary>UTF-8</primary></indexterm>
+			Since EUC-JP is usually used on open source UNIX, Linux, and FreeBSD, and on commercial-based UNIX, Solaris,
+			IRIX, and Tru64 UNIX as Japanese locale (however, it is also possible on Solaris to use Shift_JIS and UTF-8,
+			and on Tru64 UNIX it is possible to use Shift_JIS). To use EUC-JP series, most Japanese filenames created from
+			Windows can be referred to also on UNIX. Also, most Japanized free software works mainly with EUC-JP only.
+			</para>
+
+			<para>
+			It is recommended to choose EUC-JP series when using Japanese filenames on UNIX.
+			</para>
+
+			<para>
+			Although there is no character that needs to be carefully treated
+			like <quote>\ (0x5c)</quote>, broken filenames may be displayed and some
+			commands that cannot handle non-ASCII filenames may be aborted
+			during parsing filenames.
+			</para>
+
+			<para>
+<indexterm><primary>eucJP-ms locale</primary></indexterm>
+			Moreover, if you built Samba using differently installed libiconv,
+			the eucJP-ms locale included in libiconv and EUC-JP series locale
+			included in the operating system may not be compatible. In this case, you may need to
+			avoid using incompatible characters for filenames.
+			</para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry><term>UTF-8</term>
+			<listitem><para>
+			UTF-8 means a locale equivalent to UTF-8, the international standard defined by the Unicode consortium. In
+			UTF-8, a <parameter>character</parameter> is expressed using 1 to 3 bytes. In case of the Japanese language,
+			most characters are expressed using 3 bytes. Since on Windows Shift_JIS, where a character is expressed with 1
+			or 2 bytes is used to express Japanese, basically a byte length of a UTF-8 string the length of the UTF-8
+			string is 1.5 times that of the original Shift_JIS string. In the case of UTF-8, for example, if a Japanese
+			filename consists of 0x8ba4 and 0x974c, and <quote>.txt</quote> is written from Windows on Samba, the filename
+			on UNIX becomes 0xe585, 0xb1e6, 0x9c89, <quote>.txt</quote> (a 10-byte BINARY string).
+			</para>
+
+			<para>
+			For systems where iconv() is not available or where iconv()'s locales
+			are not compatible with Windows, UTF-8 is the only locale available.
+			</para>
+
+			<para> 
+			There are no systems that use UTF-8 as the default locale for Japanese.
+			</para>
+
+			<para>
+			Some broken filenames may be displayed, and some commands that
+			cannot handle non-ASCII filenames may be aborted during parsing
+			filenames. Especially, there may be <quote>\ (0x5c)</quote> in filenames, which
+			must be handled carefully, so you had better not touch filenames
+			written from Windows on UNIX.
+			</para>
+
+			<para>
+<indexterm><primary>Windows</primary></indexterm>
+<indexterm><primary>Java</primary></indexterm>
+<indexterm><primary>Unicode UTF-8</primary></indexterm>
+			In addition, although it is not directly concerned with Samba, since
+			there is a delicate difference between the iconv() function, which is
+			generally used on UNIX, and the functions used on other platforms,
+			such as Windows and Java, so far is concerens the conversion between
+			Shift_JIS and Unicode UTF-8 must be done with care and recognition
+			of the limitations involved in the process.
+			</para>
+
+			<para>
+<indexterm><primary>Mac OS X </primary></indexterm>
+			Although Mac OS X uses UTF-8 as its encoding method for filenames,
+			it uses an extended UTF-8 specification that Samba cannot handle, so
+			UTF-8 locale is not available for Mac OS X.
+			</para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry><term>Shift_JIS series + vfs_cap (CAP encoding)</term>
+			<listitem><para>
+<indexterm><primary>CAP</primary></indexterm>
+<indexterm><primary>NetAtalk</primary></indexterm>
+<indexterm><primary>Macintosh</primary></indexterm>
+			CAP encoding means a specification used in CAP and NetAtalk, file
+			server software for Macintosh. In the case of CAP encoding, for
+			example, if a Japanese filename consists of 0x8ba4 and 0x974c, and
+			<quote>.txt</quote> is written from Windows on Samba, the filename on UNIX
+			becomes <quote>:8b:a4:97L.txt</quote> (a 14 bytes ASCII string). 
+			</para>
+
+			<para>
+			For CAP encoding, a byte that cannot be expressed as an ASCII
+			character (0x80 or above) is encoded in an <quote>:xx</quote> form. You need to take
+			care of containing a <quote>\(0x5c)</quote> in a filename, but filenames are not
+			broken in a system that cannot handle non-ASCII filenames.
+			</para>
+
+			<para>
+			The greatest merit of CAP encoding is the compatibility of encoding
+			filenames with CAP or NetAtalk. These are respectively the Columbia Appletalk
+			Protocol, and the NetAtalk Open Source software project.
+			Since these software applications write a file name on UNIX with CAP encoding, if a
+			directory is shared with both Samba and NetAtalk, you need to use
+			CAP encoding to avoid non-ASCII filenames from being broken.
+			</para>
+
+			<para>
+			However, recently, NetAtalk has been
+			patched on some systems to write filenames with EUC-JP (e.g., Japanese original Vine Linux).
+			In this case, you need to choose EUC-JP series instead of CAP encoding.
+			</para>
+
+			<para>
+			vfs_cap itself is available for non-Shift_JIS series locales for
+			systems that cannot handle non-ASCII characters or systems that
+			share files with NetAtalk.
+			</para>
+
+			<para>
+			To use CAP encoding on Samba-3, you should use the unix charset parameter and VFS 
+			as in <link linkend="vfscap-intl">the VFS CAP smb.conf file</link>.
+			</para>
+
+<example id="vfscap-intl">
+<title>VFS CAP</title>
+	<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfcomment>the locale name "CP932" may be different</smbconfcomment>
+<smbconfoption name="dos charset">CP932</smbconfoption>
+<smbconfoption name="unix charset">CP932</smbconfoption>
+
+<smbconfsection name="[cap-share]"/>
+<smbconfoption name="vfs option">cap</smbconfoption>
+</smbconfblock>
+</example>
+
+			<para>
+<indexterm><primary>CP932</primary></indexterm>
+<indexterm><primary>libiconv</primary></indexterm>
+<indexterm><primary>unix charset</primary></indexterm>
+<indexterm><primary>cap-share</primary></indexterm>
+			You should set CP932 if using GNU libiconv for unix charset. With this setting,
+			filenames in the <quote>cap-share</quote> share are written with CAP encoding.
+			</para>
+			</listitem>
+		</varlistentry>
+	</variablelist>
+
+</sect2>
+
+<sect2><title>Individual Implementations</title>
+
+<para>
+Here is some additional information regarding individual implementations:
+</para>
+
+	<variablelist>
+		<varlistentry><term>GNU libiconv</term>
+			<listitem><para>
+			To handle Japanese correctly, you should apply the patch
+			<ulink url="http://www2d.biglobe.ne.jp/~msyk/software/libiconv-patch.html">libiconv-1.8-cp932-patch.diff.gz</ulink>
+			to libiconv-1.8.
+			</para>
+			
+			<para>
+			Using the patched libiconv-1.8, these settings are available:
+			</para>
+
+<programlisting>
+dos charset = CP932
+unix charset = CP932 / eucJP-ms / UTF-8
+		|       |
+		|       +-- EUC-JP series
+		+-- Shift_JIS series
+display charset = CP932
+</programlisting>
+
+			<para>
+			Other Japanese locales (for example, Shift_JIS and EUC-JP) should not
+			be used because of the lack of the compatibility with Windows.
+			</para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry><term>GNU glibc</term>
+			<listitem><para>
+			To handle Japanese correctly, you should apply a <ulink url="http://www2d.biglobe.ne.jp/~msyk/software/glibc/">patch</ulink>
+			to glibc-2.2.5/2.3.1/2.3.2 or should use the patch-merged versions, glibc-2.3.3 or later.
+			</para>
+
+			<para>
+			Using the above glibc, these setting are available:
+			<smbconfblock>
+			<smbconfoption name="dos charset">CP932</smbconfoption>
+			<smbconfoption name="unix charset">CP932 / eucJP-ms / UTF-8</smbconfoption>
+			<smbconfoption name="display charset">CP932</smbconfoption>
+			</smbconfblock>
+			</para>
+
+			<para>
+			Other Japanese locales (for example, Shift_JIS and EUC-JP) should not
+			be used because of the lack of the compatibility with Windows.
+			</para>
+			</listitem>
+		</varlistentry>
+	</variablelist>
+
+</sect2>
+
+<sect2>
+	<title>Migration from Samba-2.2 Series</title>
+
+<para> 
+Prior to Samba-2.2 series, the <quote>coding system</quote> parameter was used. The default codepage in Samba
+2.x was code page 850. In the Samba-3 series this has been replaced with the <smbconfoption name="unix
+charset"/> parameter.  <link linkend="japancharsets">Japanese Character Sets in Samba-2.2 and Samba-3</link>
+shows the mapping table when migrating from the Samba-2.2 series to Samba-3.
+</para>
+
+	<table frame="all" id="japancharsets">
+		<title>Japanese Character Sets in Samba-2.2 and Samba-3</title>
+
+		<tgroup cols="2" align="center">
+			<colspec align="center"/>
+			<colspec align="center"/>
+			<thead>
+				<row><entry>Samba-2.2 Coding System</entry><entry>Samba-3 unix charset</entry></row>
+			</thead>
+			<tbody>
+				<row><entry>SJIS</entry><entry>Shift_JIS series</entry></row>
+				<row><entry>EUC</entry><entry>EUC-JP series</entry></row>
+				<row><entry>EUC3<footnote><para>Only exists in Japanese Samba version</para></footnote></entry><entry>EUC-JP series</entry></row>
+				<row><entry>CAP</entry><entry>Shift_JIS series + VFS</entry></row>
+				<row><entry>HEX</entry><entry>currently none</entry></row>
+				<row><entry>UTF8</entry><entry>UTF-8</entry></row>
+				<row><entry>UTF8-Mac<footnote><para>Only exists in Japanese Samba version</para></footnote></entry><entry>currently none</entry></row>
+				<row><entry>others</entry><entry>none</entry></row>
+			</tbody>
+		</tgroup>
+	</table>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+	<title>Common Errors</title>
+
+	<sect2>
+		<title>CP850.so Can't Be Found</title>
+
+		<para><quote>Samba is complaining about a missing <filename>CP850.so</filename> file.</quote></para>
+
+		<para>
+		CP850 is the default <smbconfoption name="dos charset"/>.
+		The <smbconfoption name="dos charset"/> is used to convert data to the codepage used by your DOS clients.
+		If you do not have any DOS clients, you can safely ignore this message. </para>
+
+		<para>
+		CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed.
+		If you compiled Samba from source, make sure that the configure process found iconv. This can be
+		confirmed by checking the <filename>config.log</filename> file that is generated when
+		<command>configure</command> is executed.</para> 
+	</sect2>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-VFS.xml b/docs-xml/Samba3-HOWTO/TOSHARG-VFS.xml
new file mode 100644
index 00000000000..b8bd3277a63
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-VFS.xml
@@ -0,0 +1,949 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="VFS">
+<chapterinfo>
+	&author.jelmer;
+	&author.jht;
+	&author.tpot;
+	<author><firstname>Simo</firstname><surname>Sorce</surname><contrib>original vfs_skel README</contrib></author>
+	<author><firstname>Alexander</firstname><surname>Bokovoy</surname><contrib>original vfs_netatalk docs</contrib></author>
+	<author><firstname>Stefan</firstname><surname>Metzmacher</surname><contrib>Update for multiple modules</contrib></author>
+	<author><firstname>Ed</firstname><surname>Riddle</surname><contrib>original shadow_copy docs</contrib></author>
+</chapterinfo>
+<title>Stackable VFS modules</title>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>Virtual File System</primary><see>VFS</see></indexterm>
+<indexterm><primary>modules</primary></indexterm>
+<indexterm><primary>loaded modules</primary></indexterm>
+Stackable VFS (Virtual File System) modules support was new to Samba-3 and has proven quite popular. Samba
+passes each request to access the UNIX file system through the loaded VFS modules. This chapter covers the
+modules that come with the Samba source and provides references to some external modules.
+</para>
+
+
+</sect1>
+
+<sect1>
+<title>Discussion</title>
+
+<para>
+<indexterm><primary>IRIX</primary></indexterm>
+<indexterm><primary>GNU/Linux</primary></indexterm>
+If not supplied with your platform distribution binary Samba package, you may have problems compiling these
+modules, as shared libraries are compiled and linked in different ways on different systems. They currently
+have been tested against GNU/Linux and IRIX.
+</para>
+
+<para>
+<indexterm><primary>VFS modules</primary></indexterm>
+<indexterm><primary>modules</primary></indexterm>
+<indexterm><primary>recycle bin</primary></indexterm>
+To use the VFS modules, create a share similar to the one below. The important parameter is the <smbconfoption
+name="vfs objects"/> parameter where you can list one or more VFS modules by name. For example, to log all
+access to files and put deleted files in a recycle bin, see <link linkend="vfsrecyc">the smb.conf with VFS
+modules example</link>:
+</para>
+
+<example id="vfsrecyc">
+<title>smb.conf with VFS modules</title>
+<smbconfblock>
+<smbconfsection name="[audit]"/>
+<smbconfoption name="comment">Audited /data directory</smbconfoption>
+<smbconfoption name="path">/data</smbconfoption>
+<smbconfoption name="vfs objects">audit recycle</smbconfoption>
+<smbconfoption name="writeable">yes</smbconfoption>
+<smbconfoption name="browseable">yes</smbconfoption>
+</smbconfblock>
+</example>
+
+<para>
+<indexterm><primary>virus scanner</primary></indexterm>
+<indexterm><primary>scanner module</primary></indexterm>
+<indexterm><primary>recycle bin</primary></indexterm>
+The modules are used in the order in which they are specified.  Let's say that you want to both have a virus
+scanner module and a recycle bin module. It is wise to put the virus scanner module as the first one so that
+it is the first to get run and may detect a virus immediately, before any action is performed on that file.
+<smbconfoption name="vfs objects">vscan-clamav recycle</smbconfoption>
+</para>
+
+<para>
+<indexterm><primary>/usr/local/samba/lib/vfs</primary></indexterm>
+<indexterm><primary>/usr/lib/samba/vfs</primary></indexterm>
+Samba will attempt to load modules from the <filename>/lib</filename> directory in the root directory of the
+Samba installation (usually <filename>/usr/lib/samba/vfs</filename> or
+<filename>/usr/local/samba/lib/vfs</filename>).
+</para>
+
+<para>
+<indexterm><primary>modules</primary></indexterm>
+<indexterm><primary>VFS</primary></indexterm>
+<indexterm><primary>multiple modules</primary></indexterm>
+<indexterm><primary>multiple VFS</primary></indexterm>
+Some modules can be used twice for the same share.  This can be done using a configuration similar to the one
+shown in <link linkend="multimodule">the smb.conf with multiple VFS modules</link>.
+
+<example id="multimodule">
+<title>smb.conf with multiple VFS modules</title>
+<smbconfblock>
+<smbconfsection name="[test]"/>
+<smbconfoption name="comment">VFS TEST</smbconfoption>
+<smbconfoption name="path">/data</smbconfoption>
+<smbconfoption name="writeable">yes</smbconfoption>
+<smbconfoption name="browseable">yes</smbconfoption>
+<smbconfoption name="vfs objects">example:example1 example example:test</smbconfoption>
+<smbconfoption name="example1: parameter">1</smbconfoption>
+<smbconfoption name="example:  parameter">5</smbconfoption>
+<smbconfoption name="test:     parameter">7</smbconfoption>
+</smbconfblock>
+</example>
+</para>
+
+</sect1>
+
+<sect1>
+<title>Included Modules</title>
+
+	<sect2>
+	<title>audit</title>
+
+		<para>
+<indexterm><primary>audit file access</primary></indexterm>
+		A simple module to audit file access to the syslog facility. The following operations are logged:
+		<itemizedlist>
+			<listitem><para>share</para></listitem>
+			<listitem><para>connect/disconnect</para></listitem>
+			<listitem><para>directory opens/create/remove</para></listitem>
+			<listitem><para>file open/close/rename/unlink/chmod</para></listitem>
+		</itemizedlist>
+		</para>
+
+	</sect2>
+
+	<sect2>
+	<title>default_quota</title>
+
+	<para>
+	This module allows the default quota values, in the windows explorer GUI, to be stored on a Samba-3 server.
+	The challenge is that linux filesystems only store quotas for users and groups, but no default quotas.
+	</para>
+
+	<para>
+	Samba returns NO_LIMIT as the default quotas by default and refuses to update them. With this module you 
+	can store the default quotas that are reported to a windows client, in the quota record of a user. By
+	default the root user is taken because quota limits for root are typically not enforced.
+	</para>
+
+	<para>
+	This module takes 2 parametric entries in the &smb.conf; file.  The default prefix for each is the
+	<quote>default_quota</quote>. This can be overwrittem when you load the module in the <emphasis>vfs
+	modules</emphasis> parameter like this:
+<screen>
+vfs objects = default_quota:myprefix
+</screen>
+	</para>
+
+	<para>
+	The parametric entries that may be specified for the default_quotas module are:
+	</para>
+
+	<variablelist>
+		<varlistentry>
+            <term>myprefix:uid</term>
+			<listitem><para>
+			This parameter takes a integer argument that specifies the uid of the quota record that will be 
+			used for storing the default user quotas.
+			</para>
+
+			<para>
+			The default value is 0 (for root user). An example of use is:
+<screen>
+vfs objects = default_quota
+default_quota:	uid = 65534
+</screen>
+			The above demonstrates the case where the <constant>myprefix</constant> was omitted, thus the
+			default prefix is the name of the module. When a <constant>myprefix</constant> parameter is
+			specified the above can be re-written like this:
+<screen>
+vfs objects = default_quota:myprefix
+myprefix:	uid = 65534
+</screen>
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+            <term>myprefix:uid nolimit</term>
+			<listitem><para>
+			This parameter takes a boolean argument that specifies if the stored default quota values also be
+			reported for the user record, or if the value <constant>NO_LIMIT</constant> should be reported to 
+			the windows client for the user specified by the <parameter>prefix:uid</parameter> parameter.
+			</para>
+
+			<para>
+			The default value is <constant>yes</constant> (which means to report NO_LIMIT). An example of use
+			is shown here:
+<screen>
+vfs objects = default_quota:myprefix
+myprefix:	uid nolimit = no
+</screen>
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>myprefix:gid</term>
+			<listitem><para>
+			This parameter takes an integer argument, it's just like the <parameter>prefix>:uid</parameter> but 
+			for group quotas.  NOTE: group quotas are not supported from the windows explorer.
+			</para>
+
+			<para>
+			The default value is 0 (for root group). An example of use is shown here:
+<screen>
+vfs objects = default_quota
+default_quota:	gid = 65534
+</screen>
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>myprefix:gid nolimit</term>
+			<listitem><para>
+			This parameter takes a boolean argument, just like the <parameter>prefix>:uid nolimit</parameter> 
+			but for group quotas.  NOTE: group quotas are not supported from the windows explorer.
+			</para>
+
+			<para>
+			The default value is <constant>yes</constant> (which means to report NO_LIMIT). An example of use
+			is shown here:
+<screen>
+vfs objects = default_quota
+default_quota:	uid nolimit = no
+</screen>
+			</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>
+	An example of use of multiple parametric specifications is shown here:
+<screen>
+...
+vfs objects = default_quota:quotasettings
+quotasettings:	uid nolimit = no
+quotasettings:	gid = 65534
+quotasettings:	gid nolimit = no
+...
+</screen>
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>extd_audit</title>
+
+		<para>
+<indexterm><primary>audit module</primary></indexterm>
+<indexterm><primary>extd_audit module</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+		This module is identical with the <command>audit</command> module above except
+		that it sends audit logs to both syslog as well as the <command>smbd</command> log files. The 
+		<smbconfoption name="log level"/> for this module is set in the &smb.conf; file. 
+		</para>
+
+		<para>
+		Valid settings and the information that will be recorded are shown in <link linkend="xtdaudit">the next table</link>.
+		</para>
+
+		<table frame="all" id="xtdaudit">
+			<title>Extended Auditing Log Information</title>
+		<tgroup cols="2" align="center">
+			<thead>
+			<row><entry align="center">Log Level</entry><entry>Log Details - File and Directory Operations</entry></row>
+			</thead>
+			<tbody>
+			<row><entry align="center">0</entry><entry align="left">Make Directory, Remove Directory, Unlink</entry></row>
+			<row><entry align="center">1</entry><entry align="left">Open Directory, Rename File, Change Permissions/ACLs</entry></row>
+			<row><entry align="center">2</entry><entry align="left">Open &amp; Close File</entry></row>
+			<row><entry align="center">10</entry><entry align="left">Maximum Debug Level</entry></row>
+			</tbody>
+		</tgroup>
+		</table>
+
+		<sect3>
+		<title>Configuration of Auditing</title>
+
+		<para>
+<indexterm><primary>logging</primary></indexterm>
+		This auditing tool is more felxible than most people readily will recognize. There are a number of ways
+		by which useful logging information can be recorded.
+		</para>
+
+		<itemizedlist>
+			<listitem><para>Syslog can be used to record all transaction. This can be disabled by setting
+					in the &smb.conf; file <parameter>syslog = 0</parameter>.</para></listitem>
+			<listitem><para>Logging can take place to the default log file (<filename>log.smbd</filename>)
+					for all loaded VFS modules just by setting in the &smb.conf; file
+					<parameter>log level = 0 vfs:x</parameter>, where x is the log level.
+					This will disable general logging while activating all logging of VFS
+					module activity at the log level specified.</para></listitem>
+			<listitem><para>Detailed logging can be obtained per user, per client machine, etc.
+					This requires the above together with the creative use of the
+					<parameter>log file</parameter> settings.</para>
+					<para>An example of detailed per-user and per-machine logging can
+					be obtained by setting 
+					<smbconfoption name="log file">/var/log/samba/%U.%m.log</smbconfoption>.
+					</para></listitem>
+		</itemizedlist>
+
+		<para>
+		Auditing information often must be preserved for a long time. So that the log files do not get rotated
+		it is essential that the <smbconfoption name="max log size">0</smbconfoption> be set
+		in the &smb.conf; file.
+		</para>
+
+		</sect3>
+
+	</sect2>
+
+	<sect2 id="fakeperms">
+	<title>fake_perms</title>
+
+		<para>
+<indexterm><primary>fake_perms</primary></indexterm>
+<indexterm><primary>Roaming Profile</primary></indexterm>
+<indexterm><primary>writeable</primary></indexterm>
+<indexterm><primary>read only</primary></indexterm>
+		This module was created to allow Roaming Profile files and directories to be set (on the Samba server
+		under UNIX) as read only. This module will, if installed on the Profiles share, report to the client
+		that the Profile files and directories are writeable. This satisfies the client even though the files
+		will never be overwritten as the client logs out or shuts down.
+		</para>
+
+	</sect2>
+
+	<sect2>
+	<title>recycle</title>
+
+		<para>
+<indexterm><primary>recycle</primary></indexterm>
+<indexterm><primary>unlink calls</primary></indexterm>
+<indexterm><primary>recycle directory</primary></indexterm>
+		A Recycle Bin-like module. Where used, unlink calls will be intercepted and files moved
+		to the recycle directory instead of being deleted. This gives the same effect as the
+		<guiicon>Recycle Bin</guiicon> on Windows computers.
+		</para>
+
+		<para>
+<indexterm><primary>recycle</primary></indexterm>
+<indexterm><primary>.recycle</primary></indexterm>
+<indexterm><primary>recycle:keeptree</primary></indexterm>
+<indexterm><primary>deleted files</primary></indexterm>
+		The <guiicon>Recycle Bin</guiicon> will not appear in
+		<application>Windows Explorer</application> views of the network
+		file system (share) nor on any mapped drive. Instead, a directory
+		called <filename>.recycle</filename> will be automatically created
+		when the first file is deleted and <parameter>recycle:repository</parameter>
+		is not configured.
+		If <parameter>recycle:repository</parameter> is configured, the name
+		of the created directory depends on <parameter>recycle:repository</parameter>.
+		Users can recover files from the recycle bin. If the
+		<parameter>recycle:keeptree</parameter> has been specified,	deleted
+		files will be found in a path identical with that from which the
+		file was deleted.
+		</para>
+		
+		<para>Supported options for the <command>recycle</command> module are as follow:
+		<variablelist>
+			<varlistentry>
+			<term>recycle:repository</term>
+				<listitem><para>
+<indexterm><primary>recycle:repository</primary></indexterm>
+				Path of the directory where deleted files should be moved.
+				</para></listitem>
+			</varlistentry>
+
+			<varlistentry>
+			<term>recycle:directory_mode</term>
+				<listitem><para>
+<indexterm><primary>directory_mode</primary></indexterm>
+				Set it to the octal mode you want for the recycle directory. With
+				this mode the recycle directory	will be created if it not
+				exists and the first file is deleted.
+				If <parameter>recycle:subdir_mode</parameter> is not set, these
+				mode also apply to sub directories.
+				If <parameter>directory_mode</parameter> not exists, the default
+				mode 0700 is used.
+				</para></listitem>
+			</varlistentry>
+
+			<varlistentry>
+			<term>recycle:subdir_mode</term>
+				<listitem><para>
+<indexterm><primary>recycle:subdir_mode</primary></indexterm>
+				Set it to the octal mode you want for the sub directories of
+				the recycle directory. With this mode	the sub directories will
+				be created.
+				If <parameter>recycle:subdir_mode</parameter> is not set, the
+				sub directories will be created with the mode from
+				<parameter>directory_mode</parameter>.
+				</para></listitem>
+			</varlistentry>
+
+			<varlistentry>
+			<term>recycle:keeptree</term>
+				<listitem><para>
+<indexterm><primary>recycle:keeptree</primary></indexterm>
+				Specifies whether the directory structure should be kept or if the files in the directory that is being 
+				deleted should be kept separately in the recycle bin.
+				</para></listitem>
+			</varlistentry>
+			
+			<varlistentry>
+			<term>recycle:versions</term>
+				<listitem><para>
+<indexterm><primary>recycle:versions</primary></indexterm>
+				If this option is set, two files 
+				with the same name that are deleted will both 
+				be kept in the recycle bin. Newer deleted versions 
+				of a file will be called <quote>Copy #x of <replaceable>filename</replaceable></quote>.
+				</para></listitem>
+			</varlistentry>
+
+			<varlistentry>
+			<term>recycle:touch</term>
+				<listitem><para>
+<indexterm><primary>recycle:touch</primary></indexterm>
+				Specifies whether a file's access date should be touched when the file is moved to the recycle bin.
+				</para></listitem>
+			</varlistentry>
+
+			<varlistentry>
+			<term>recycle:touch_mtime</term>
+				<listitem><para>
+<indexterm><primary>recycle:touch</primary></indexterm>
+				Specifies whether a file's last modify date date should be touched when the file is moved to the recycle bin.
+				</para></listitem>
+			</varlistentry>
+
+			<varlistentry>
+			<term>recycle:maxsize</term>
+				<listitem><para>
+<indexterm><primary>recycle:maxsize</primary></indexterm>
+				Files that are larger than the number of bytes specified by this parameter will not be put into the recycle bin.
+				</para></listitem>
+			</varlistentry>
+
+			<varlistentry>
+			<term>recycle:exclude</term>
+				<listitem><para>
+<indexterm><primary>recycle:exclude</primary></indexterm>
+				List of files that should not be put into the recycle bin when deleted, but deleted in the regular way.
+				</para></listitem>
+			</varlistentry>
+
+			<varlistentry>
+			<term>recycle:exclude_dir</term>
+				<listitem><para>
+<indexterm><primary>recycle:exclude_dir</primary></indexterm>
+				Contains a list of directories. When files from these directories are
+				deleted, they are not put into the
+				recycle bin but are deleted in the
+				regular way.
+				</para></listitem>
+			</varlistentry>
+
+			<varlistentry>
+			<term>recycle:noversions</term>
+				<listitem><para>
+<indexterm><primary>recycle:noversions</primary></indexterm>
+				Specifies a list of paths (wildcards such as * and ? are supported) for which no versioning
+				should be used. Only useful when <emphasis>recycle:versions</emphasis> is enabled.
+				</para></listitem>
+			</varlistentry>
+		</variablelist>
+		</para>
+
+	</sect2>
+
+	<sect2>
+	<title>netatalk</title>
+
+		<para>
+<indexterm><primary>netatalk</primary></indexterm>
+		A netatalk module will ease co-existence of Samba and netatalk file sharing services.
+		</para>
+
+		<para>Advantages compared to the old netatalk module:
+		<itemizedlist>
+<indexterm><primary>.AppleDouble</primary></indexterm>
+			<listitem><para>Does not care about creating .AppleDouble forks, just keeps them in sync.</para></listitem>
+			<listitem><para>If a share in &smb.conf; does not contain .AppleDouble item in hide or veto list, it will be added automatically.</para></listitem>
+		</itemizedlist>
+		</para>
+
+	</sect2>
+
+    <sect2>
+      <title>shadow_copy</title>
+
+	<warning><para>
+<indexterm><primary>shadow_copy</primary></indexterm>
+	<emphasis>THIS IS NOT A BACKUP, ARCHIVAL, OR VERSION CONTROL SOLUTION!</emphasis>
+	</para>
+
+	<para>
+<indexterm><primary>version control</primary></indexterm>
+	With Samba or Windows servers, shadow_copy is designed to be an end-user tool only.  It does not replace or
+	enhance your backup and archival solutions and should in no way be considered as such.  Additionally, if you
+	need version control, implement a version control system.  You have been warned.
+	</para></warning>
+
+
+	<para>
+	The shadow_copy module allows you to setup functionality that is similar to MS shadow copy services.  When
+	setup properly, this module allows Microsoft shadow copy clients to browse "shadow copies" on Samba shares.
+	You will need to install the shadow copy client.  You can get the MS shadow copy client <ulink noescape="1"
+	url="http://www.microsoft.com/windowsserver2003/downloads/shadowcopyclient.mspx">here.</ulink>.  Note the
+	additional requirements for pre-Windows XP clients.  I did not test this functionality with any pre-Windows XP
+	clients.  You should be able to get more information about MS Shadow Copy <ulink noescape="1"
+	url="http://www.microsoft.com/windowsserver2003/techinfo/overview/scr.mspx">from the Microsoft's site</ulink>.
+	</para>
+
+	<para>
+<indexterm><primary>shadow_copy</primary></indexterm>
+<indexterm><primary>VFS module</primary></indexterm>
+<indexterm><primary>shadow_copy module</primary></indexterm>
+<indexterm><primary>LVM</primary></indexterm>
+<indexterm><primary>EVMS</primary></indexterm>
+<indexterm><primary>Logical Volume Manager</primary><see>LVM</see></indexterm>
+	The shadow_copy VFS module requires some underlying file system setup with some sort of Logical Volume Manager
+	(LVM) such as LVM1, LVM2, or EVMS.  Setting up LVM is beyond the scope of this document; however, we will
+	outline the steps we took to test this functionality for <emphasis>example purposes only.</emphasis> You need
+	to make sure the LVM implementation you choose to deploy is ready for production.  Make sure you do plenty of
+	tests.
+	</para>
+
+	<para>
+	Here are some common resources for LVM and EVMS:
+	</para>
+
+	<itemizedlist>
+	  <listitem>
+	    <para><ulink noescape="1"
+	    url="http://www.sistina.com/products_lvm_download.htm">Sistina's
+	    LVM1 and LVM2</ulink></para>
+	  </listitem>
+	  <listitem>
+	    <para><ulink url="http://evms.sourceforge.net/">Enterprise Volume Management System (EVMS)</ulink></para>
+	  </listitem>
+	  <listitem>
+	    <para><ulink url="http://tldp.org/HOWTO/LVM-HOWTO/">The LVM HOWTO</ulink></para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      See <ulink url="http://www-106.ibm.com/developerworks/linux/library/l-lvm/">Learning
+	      Linux LVM, Part 1</ulink> and <ulink url="http://www-106.ibm.com/developerworks/library/l-lvm2.html">Learning
+	      Linux LWM, Part 2</ulink> for Daniel Robbins' well-written, two part tutorial on Linux and LVM using LVM
+	      source code and reiserfs.</para>
+	  </listitem>
+	</itemizedlist>
+
+	<sect3>
+	<title>Shadow Copy Setup</title>
+	<para>
+<indexterm><primary>XFS file system</primary></indexterm>
+<indexterm><primary>Debian Sarge</primary></indexterm>
+	At the time of this writing, not much testing has been done.  I tested the shadow copy VFS module with a
+	specific scenario which was not deployed in a production environment, but more as a proof of concept.  The
+	scenario involved a Samba-3 file server on Debian Sarge with an XFS file system and LVM1.  I do NOT recommend
+	you use this as a solution without doing your own due diligence with regard to all the components presented
+	here.  That said, following is an basic outline of how I got things going.
+	</para>
+
+	<orderedlist>
+	  <listitem>
+	    <formalpara><title>Installed Operating System </title> 
+	    <para>
+		In my tests, I used <ulink url="http://www.debian.org/devel/debian-installer/">Debian
+		Sarge</ulink> (i.e., testing) on an XFS file system.  Setting up the OS is a bit beyond the scope of this
+		document.  It is assumed that you have a working OS capable of running Samba.
+		</para></formalpara>
+	  </listitem>
+
+	  <listitem>
+	    <formalpara><title>Install &amp; Configure Samba</title>
+		<para>
+		See the <link linkend="introduction">installation section</link> of this HOWTO for more detail on this.
+		It doesn't matter if it is a Domain Controller or Member File Server, but it is assumed that you have a
+		working Samba 3.0.3 or later server running.
+		</para></formalpara>
+	  </listitem>
+
+	  <listitem>
+	    <formalpara><title>Install &amp; Configure LVM</title>
+		<para>
+<indexterm><primary>shadow copies</primary></indexterm>
+<indexterm><primary>Snapshots</primary></indexterm>
+		Before you can make shadow copies available to the client, you have to create the shadow copies.  This is
+		done by taking some sort of file system snapshot.  Snapshots are a typical feature of Logical Volume
+		Managers such as LVM, so we first need to have that setup.
+		</para></formalpara>
+
+	    <itemizedlist>
+		<para>
+		The following is provided as an example and will be most helpful for Debian users.  Again, this was tested
+		using the "testing" or "Sarge" distribution.
+		</para>
+
+			<listitem>
+			<para>
+<indexterm><primary>lvm10 package</primary></indexterm>
+<indexterm><primary>devfsd package</primary></indexterm>
+<indexterm><primary>Debian</primary></indexterm>
+<indexterm><primary>xfsprogs</primary></indexterm>
+<indexterm><primary>apt-get</primary></indexterm>
+			Install lvm10 and devfsd packages if you have not done so already.  On Debian systems, you are warned of the
+			interaction of devfs and lvm1 which requires the use of devfs filenames.  Running <command>apt-get update
+			&amp;&amp; apt-get install lvm10 devfsd xfsprogs</command> should do the trick for this example.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>create volume</primary></indexterm>
+<indexterm><primary>create partition</primary></indexterm>
+<indexterm><primary>fdisk</primary></indexterm>
+<indexterm><primary>cfdisk</primary></indexterm>
+<indexterm><primary>Linux LVM</primary></indexterm>
+			Now you need to create a volume.  You will need to create a partition (or partitions) to add to your volume.
+			Use your favorite partitioning tool (e.g., Linux fdisk, cfdisk, etc.).  The partition type should be set to
+			0x8e for "Linux LVM."  In this example, we will use /dev/hdb1.
+			</para>
+
+			<para>
+<indexterm><primary>Linux LVM partition</primary></indexterm>
+<indexterm><primary>LVM volume</primary></indexterm>
+<indexterm><primary>modprobe</primary></indexterm>
+			Once you have the Linux LVM partition (type 0x8e), you can run a series of commands to create the LVM volume.
+			You can use several disks and/or partitions, but we will use only one in this example.  You may also need to
+			load the kernel module with something like <command>modprobe lvm-mod</command> and set your system up to load
+			it on reboot by adding it to (<filename>/etc/modules</filename>).
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>pvcreate</primary></indexterm>
+			Create the physical volume with <command>pvcreate /dev/hdb1</command>
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>vgcreate</primary></indexterm>
+<indexterm><primary>volume group</primary></indexterm>
+			Create the volume group and add /dev/hda1 to it with <command>vgcreate shadowvol /dev/hdb1</command>
+			</para>
+
+			<para>
+<indexterm><primary>vgdisplay</primary></indexterm>
+			You can use <command>vgdisplay</command> to review information about the volume group.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>lvcreate</primary></indexterm>
+			Now you can create the logical volume with something like <command>lvcreate -L400M -nsh_test shadowvol</command>
+			</para>
+
+			<para>
+<indexterm><primary>/dev/shadowvol</primary></indexterm>
+			This creates the logical volume of 400 MBs named "sh_test" in the volume group we created called shadowvol.
+			If everything is working so far, you should see them in <filename>/dev/shadowvol</filename>.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>mkfs.xfs</primary></indexterm>
+			Now we should be ready to format the logical volume we named sh_test with <command>mkfs.xfs
+			/dev/shadowvol/sh_test</command>
+			</para>
+
+			<para>
+<indexterm><primary>logical volume</primary></indexterm>
+<indexterm><primary>LVM</primary></indexterm>
+<indexterm><primary>freezing</primary></indexterm>
+<indexterm><primary>resizing</primary></indexterm>
+<indexterm><primary>growing</primary></indexterm>
+			You can format the logical volume with any file system you choose, but make sure to use one that allows you to
+			take advantage of the additional features of LVM such as freezing, resizing, and growing your file systems.
+			</para>
+
+			<para>
+<indexterm><primary>LVM volume</primary></indexterm>
+<indexterm><primary>shadow_copy</primary></indexterm>
+<indexterm><primary>module</primary></indexterm>
+			Now we have an LVM volume where we can play with the shadow_copy VFS module.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>mkdir</primary></indexterm>
+<indexterm><primary>permissions</primary></indexterm>
+<indexterm><primary>chmod</primary></indexterm>
+			Now we need to prepare the directory with something like
+<screen>
+&rootprompt; mkdir -p /data/shadow_share
+</screen>
+			or whatever you want to name your shadow copy-enabled Samba share.  Make sure you set the permissions so that
+			you can use it.  If in doubt, use <command>chmod 777 /data/shadow_share</command> and tighten the permissions
+			once you get things working.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>mount</primary></indexterm>
+			Mount the LVM volume using something like <command>mount /dev/shadowvol/sh_test /data/shadow_share</command>
+			</para>
+
+			<para>
+<indexterm><primary>/etc/fstab</primary></indexterm>
+			You may also want to edit your <filename>/etc/fstab</filename> so that this partition mounts during the system boot.
+			</para></listitem>
+		</itemizedlist>
+
+		</listitem>
+
+	  <listitem>
+	    <formalpara><title>Install &amp; Configure the shadow_copy VFS Module</title>
+		<para>
+		Finally we get to the actual shadow_copy VFS module.  The shadow_copy VFS module should be available in Samba
+		3.0.3 and higher.  The smb.conf configuration is pretty standard.  Here is our example of a share configured
+		with the shadow_copy VFS module:
+		</para></formalpara>
+
+		<example id="vfsshadow">
+		<title>Share With shadow_copy VFS</title>
+		<smbconfblock>
+		<smbconfsection name="[shadow_share]"/>
+		<smbconfoption name="comment">Shadow Copy Enabled Share</smbconfoption>
+		<smbconfoption name="path">/data/shadow_share</smbconfoption>
+		<smbconfoption name="vfs objects">shadow_copy</smbconfoption>
+		<smbconfoption name="writeable">yes</smbconfoption>
+		<smbconfoption name="browseable">yes</smbconfoption>
+		</smbconfblock>
+		</example>
+
+		</listitem>
+
+		<listitem>
+	    <formalpara><title>Create Snapshots and Make Them Available to shadow_copy.so</title> 
+		<para>
+<indexterm><primary>shadow_copy</primary></indexterm>
+<indexterm><primary>LVM snapshots</primary></indexterm>
+<indexterm><primary>module</primary></indexterm>
+		Before you can browse the shadow copies, you must create them and mount them.  This will most likely be done
+		with a script that runs as a cron job.  With this particular solution, the shadow_copy VFS module is used to
+		browse LVM snapshots.  Those snapshots are not created by the module.  They are not made available by the
+		module either.  This module allows the shadow copy-enabled client to browse the snapshots you take and make
+		available.
+		</para></formalpara>
+
+	    <para>
+		Here is a simple script used to create and mount the snapshots:
+<screen>
+#!/bin/bash
+# This is a test, this is only a test
+SNAPNAME=`date +%Y.%m.%d-%H.%M.%S`
+xfs_freeze -f /data/shadow_share/
+lvcreate -L10M -s -n $SNAPNAME /dev/shadowvol/sh_test
+xfs_freeze -u /data/shadow_share/
+mkdir /data/shadow_share/@GMT-$SNAPNAME
+mount /dev/shadowvol/$SNAPNAME \
+       /data/shadow_share/@GMT-$SNAPNAME -onouuid,ro
+</screen>
+		Note that the script does not handle other things like remounting snapshots on reboot.
+	    </para></listitem>
+
+		<listitem>
+	    <formalpara><title>Test From Client</title>
+		<para>
+		To test, you will need to install the shadow copy client which you can obtain from the <ulink
+		url="http://www.microsoft.com/windowsserver2003/downloads/shadowcopyclient.mspx">Microsoft web site.</ulink> I
+		only tested this with an XP client so your results may vary with other pre-XP clients.  Once installed, with
+		your XP client you can right-click on specific files or in the empty space of the shadow_share and view the
+		"properties."  If anything has changed, then you will see it on the "Previous Versions" tab of the properties
+		window.
+		</para></formalpara>
+	  </listitem>
+	</orderedlist>
+
+	</sect3>
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>VFS Modules Available Elsewhere</title>
+
+<para>
+<indexterm><primary>VFS modules</primary></indexterm>
+This section contains a listing of various other VFS modules that have been posted but do not currently reside
+in the Samba CVS tree for one reason or another (e.g., it is easy for the maintainer to have his or her own
+CVS tree).
+</para>
+
+<para>
+No statements about the stability or functionality of any module should be implied due to its presence here.
+</para>
+
+<sect2>
+<title>DatabaseFS</title>
+
+<para>
+<indexterm><primary>DatabaseFS</primary></indexterm>
+URL: <ulink noescape="1" url="http://www.css.tayloru.edu/~elorimer/databasefs/index.php">
+Taylors University DatabaeFS</ulink>
+</para>
+
+<para>By <ulink url="mailto:elorimer@css.tayloru.edu">Eric Lorimer.</ulink></para>
+
+<para>
+I have created a VFS module that implements a fairly complete read-only filesystem. It presents information
+from a database as a filesystem in a modular and generic way to allow different databases to be used.
+(Originally designed for organizing MP3s under directories such as <quote>Artists,</quote> <quote>Song
+Keywords,</quote> and so on. I have since easily applied it to a student roster database.) The directory
+structure is stored in the database itself and the module makes no assumptions about the database structure
+beyond the table it requires to run.
+</para>
+
+<para>
+Any feedback would be appreciated: comments, suggestions, patches, and so on. If nothing else, it
+might prove useful for someone else who wishes to create a virtual filesystem.
+</para>
+
+</sect2>
+
+<sect2>
+<title>vscan</title>
+
+<indexterm><primary>vscan</primary></indexterm>
+<para>URL: <ulink noescape="1" url="http://www.openantivirus.org/projects.php#samba-vscan">
+Open Anti-Virus vscan</ulink>
+</para>
+
+<para>
+<indexterm><primary>samba-vscan</primary></indexterm>
+samba-vscan is a proof-of-concept module for Samba, which provides on-access anti-virus support for files
+shared using Samba.  samba-vscan supports various virus scanners and is maintained by Rainer Link.
+</para>
+
+</sect2>
+
+<sect2>
+<title>vscan-clamav</title>
+<para>
+Samba users have been using the RPMS from SerNet without a problem.
+OpenSUSE Linux users have also used the vscan scanner for quite some time
+with excellent results. It does impact overall write performance though.
+</para>
+
+<para>
+The following share stanza is a good guide for those wanting to configure vscan-clamav:
+</para>
+
+<screen>
+[share]
+vfs objects = vscan-clamav
+vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
+</screen>
+
+<para>
+The following example of the <filename>vscan-clamav.conf</filename> file may help to get this
+fully operational:
+</para>
+
+<screen>
+<title>VFS: Vscan ClamAV Control File</title>
+#
+# /etc/samba/vscan-clamav.conf
+#
+
+[samba-vscan]
+; run-time configuration for vscan-samba using
+; clamd
+; all options are set to default values
+
+; do not scan files larger than X bytes. If set to 0 (default),
+; this feature is disable (i.e. all files are scanned)
+max file size = 10485760
+
+; log all file access (yes/no). If set to yes, every access will
+; be logged. If set to no (default), only access to infected files
+; will be logged
+verbose file logging = no
+
+; if set to yes (default), a file will be scanned while opening
+scan on open = yes
+; if set to yes, a file will be scanned while closing (default is yes)
+scan on close = yes
+
+; if communication to clamd fails, should access to file denied?
+; (default: yes)
+deny access on error = no
+
+; if daemon failes with a minor error (corruption, etc.),
+; should access to file denied?
+; (default: yes)
+deny access on minor error = no
+
+; send a warning message via Windows Messenger service
+; when virus is found?
+; (default: yes)
+send warning message = yes
+
+; what to do with an infected file
+; quarantine: try to move to quantine directory
+; delete:     delete infected file
+; nothing:    do nothing (default)
+infected file action = quarantine
+
+; where to put infected files - you really want to change this!
+quarantine directory  = /opt/clamav/quarantine
+; prefix for files in quarantine
+quarantine prefix = vir-
+
+; as Windows tries to open a file multiple time in a (very) short time
+; of period, samba-vscan use a last recently used file mechanism to avoid
+; multiple scans of a file. This setting specified the maximum number of
+; elements of the last recently used file list. (default: 100)
+max lru files entries = 100
+
+; an entry is invalidad after lru file entry lifetime (in seconds).
+; (Default: 5)
+lru file entry lifetime = 5
+
+; exclude files from being scanned based on the MIME-type! Semi-colon
+; seperated list (default: empty list). Use this with care!
+exclude file types =
+
+; socket name of clamd (default: /var/run/clamd). Setting will be ignored if
+; libclamav is used
+clamd socket name = /tmp/clamd
+
+; limits, if vscan-clamav was build for using the clamav library (libclamav)
+; instead of clamd
+
+; maximum number of files in archive (default: 1000)
+libclamav max files in archive = 1000
+
+; maximum archived file size, in bytes (default: 10 MB)
+libclamav max archived file size = 5242880
+
+; maximum recursion level (default: 5)
+libclamav max recursion level = 5
+</screen>
+
+<para>
+Obviously, a running clam daemon is necessary for this to work. This is a working example for me using ClamAV.
+The ClamAV documentation should provide additional configuration examples. On your system these may be located
+under the <filename>/usr/share/doc/</filename> directory. Some examples may also target other virus scanners,
+any of which can be used.
+</para>
+
+</sect2>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml
new file mode 100644
index 00000000000..7731e4e2064
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml
@@ -0,0 +1,1479 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="winbind">
+
+<chapterinfo>
+	<author>
+		<firstname>Tim</firstname><surname>Potter</surname>
+		<affiliation>
+			<orgname>Samba Team</orgname>
+			<address><email>tpot@linuxcare.com.au</email></address>
+		</affiliation>
+	</author>
+	&author.tridge;
+	<author>
+		<firstname>Naag</firstname><surname>Mummaneni</surname>
+		<affiliation>
+			<address><email>getnag@rediffmail.com</email></address>
+		</affiliation>
+		<contrib>Notes for Solaris</contrib>
+	</author>
+	<author>
+		<firstname>John</firstname><surname>Trostel</surname>
+		<affiliation>
+			<orgname>SNAP</orgname>
+			<address><email>jtrostel@snapserver.com</email></address>
+		</affiliation>
+	</author>
+	&author.jelmer;
+	&author.jht;
+	<pubdate>June 15, 2005</pubdate>
+</chapterinfo>
+
+<title>Winbind: Use of Domain Accounts</title>
+
+<sect1>
+	<title>Features and Benefits</title>
+
+	<para>
+<indexterm><primary>holy grail</primary></indexterm>
+<indexterm><primary>heterogeneous computing</primary></indexterm>
+	Integration of UNIX and Microsoft Windows NT through a unified logon has
+	been considered a <quote>holy grail</quote> in heterogeneous computing environments for
+	a long time.
+	</para>
+
+	<para>
+<indexterm><primary>interoperability</primary></indexterm>
+<indexterm><primary>domain user</primary></indexterm>
+<indexterm><primary>domain group</primary></indexterm>
+<indexterm><primary>group ownership</primary></indexterm>
+	There is one other facility without which UNIX and Microsoft Windows network
+	interoperability would suffer greatly. It is imperative that there be a
+	mechanism for sharing files across UNIX systems and to be able to assign
+	domain user and group ownerships with integrity.
+	</para>
+
+	<para>
+<indexterm><primary>Pluggable Authentication Modules</primary><see>PAM</see></indexterm>
+<indexterm><primary>winbind</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>RPC</primary></indexterm>
+	<emphasis>winbind</emphasis> is a component of the Samba suite of programs that
+	solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft
+	RPC calls, Pluggable Authentication Modules (PAMs), and the name service switch (NSS) to
+	allow Windows NT domain users to appear and operate as UNIX users on a UNIX
+	machine. This chapter describes the Winbind system, the functionality
+	it provides, how it is configured, and how it works internally.
+	</para>
+
+	<para>
+	Winbind provides three separate functions:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>NT4 domain</primary></indexterm>
+		Authentication of user credentials (via PAM). This makes it possible to
+		log onto a UNIX/Linux system using user and group accounts from a Windows
+		NT4 (including a Samba domain) or an Active Directory domain.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>identity resolution</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+		Identity resolution (via NSS). This is the default when winbind is not used.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+<indexterm><primary>idmap uid</primary></indexterm>
+<indexterm><primary>idmap gid</primary></indexterm>
+<indexterm><primary>idmap backend</primary></indexterm>
+<indexterm><primary></primary>LDAP</indexterm>
+		Winbind maintains a database called winbind_idmap.tdb in which it stores
+		mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only
+		for users and groups that do not have a local UID/GID. It stores the UID/GID
+		allocated from the idmap uid/gid range that it has mapped to the NT SID.
+		If <parameter>idmap backend</parameter> has been specified as <constant>ldap:ldap://hostname[:389]</constant>,
+		then instead of using a local mapping, Winbind will obtain this information
+		from the LDAP database.
+		</para></listitem>
+	</itemizedlist>
+
+	<note><para>
+	<indexterm><primary>winbindd</primary></indexterm>
+	<indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>/etc/group</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+	If <command>winbindd</command> is not running, smbd (which calls <command>winbindd</command>) will fall back to
+	using purely local information from <filename>/etc/passwd</filename> and <filename>/etc/group</filename> and no dynamic
+	mapping will be used. On an operating system that has been enabled with the NSS,
+	the resolution of user and group information will be accomplished via NSS.
+	</para></note>
+
+
+	<figure id="winbind_idmap">
+	<title>Winbind Idmap</title>
+	<imagefile scale="45">idmap_winbind_no_loop</imagefile>
+	</figure>
+
+</sect1>
+
+
+<sect1>
+	<title>Introduction</title>
+
+	<para>It is well known that UNIX and Microsoft Windows NT have
+	different models for representing user and group information and
+	use different technologies for implementing them. This fact has
+	made it difficult to integrate the two systems in a satisfactory
+	manner.</para>
+
+	<para>
+<indexterm><primary>synchronization problems</primary></indexterm>
+<indexterm><primary>passwords</primary></indexterm>
+	One common solution in use today has been to create
+	identically named user accounts on both the UNIX and Windows systems
+	and use the Samba suite of programs to provide file and print services
+	between the two. This solution is far from perfect, however, because
+	adding and deleting users on both sets of machines becomes a chore,
+	and two sets of passwords are required &smbmdash; both of which
+	can lead to synchronization problems between the UNIX and Windows
+	systems and confusion for users.</para>
+
+	<para>We divide the unified logon problem for UNIX machines into
+	three smaller problems:</para>
+
+	<itemizedlist>
+		<listitem><para>Obtaining Windows NT user and group information.
+		</para></listitem>
+
+		<listitem><para>Authenticating Windows NT users.
+		</para></listitem>
+
+		<listitem><para>Password changing for Windows NT users.
+		</para></listitem>
+	</itemizedlist>
+
+
+	<para>
+<indexterm><primary>unified logon</primary></indexterm>
+<indexterm><primary>duplication of information</primary></indexterm>
+	Ideally, a prospective solution to the unified logon problem
+	would satisfy all the above components without duplication of
+	information on the UNIX machines and without creating additional
+	tasks for the system administrator when maintaining users and
+	groups on either system. The Winbind system provides a simple
+	and elegant solution to all three components of the unified logon
+	problem.</para>
+</sect1>
+
+
+<sect1>
+	<title>What Winbind Provides</title>
+
+	<para>
+<indexterm><primary>Windows account management</primary></indexterm>
+<indexterm><primary>UNIX users</primary></indexterm>
+<indexterm><primary>UNIX groups</primary></indexterm>
+<indexterm><primary>NT domain</primary></indexterm>
+	Winbind unifies UNIX and Windows NT account management by
+	allowing a UNIX box to become a full member of an NT domain. Once
+	this is done, the UNIX box will see NT users and groups as if
+	they were <quote>native</quote> UNIX users and groups, allowing the NT domain
+	to be used in much the same manner that NIS+ is used within
+	UNIX-only environments.</para>
+
+	<para>
+<indexterm><primary>Winbind hooks</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>redirection</primary></indexterm>
+	The end result is that whenever a
+	program on the UNIX machine asks the operating system to look up
+	a user or group name, the query will be resolved by asking the
+	NT domain controller for the specified domain to do the lookup.
+	Because Winbind hooks into the operating system at a low level
+	(via the NSS name resolution modules in the C library), this
+	redirection to the NT domain controller is completely
+	transparent.</para>
+
+	<para>
+<indexterm><primary>user and group</primary></indexterm>
+<indexterm><primary>domain user</primary></indexterm>
+	Users on the UNIX machine can then use NT user and group
+	names as they would <quote>native</quote> UNIX names. They can chown files
+	so they are owned by NT domain users or even login to the
+	UNIX machine and run a UNIX X-Window session as a domain user.</para>
+
+	<para>
+<indexterm><primary>domain controller</primary></indexterm>
+	The only obvious indication that Winbind is being used is
+	that user and group names take the form <constant>DOMAIN\user</constant> and
+	<constant>DOMAIN\group</constant>. This is necessary because it allows Winbind to determine
+	that redirection to a domain controller is wanted for a particular
+	lookup and which trusted domain is being referenced.</para>
+
+	<para>
+<indexterm><primary>PAM-enabled</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+	Additionally, Winbind provides an authentication service that hooks into the PAM system
+	to provide authentication via an NT domain to any PAM-enabled
+	applications. This capability solves the problem of synchronizing
+	passwords between systems, since all passwords are stored in a single
+	location (on the domain controller).</para>
+
+	<sect2>
+		<title>Target Uses</title>
+
+		<para>
+<indexterm><primary>infrastructure</primary></indexterm>
+		Winbind is targeted at organizations that have an
+		existing NT-based domain infrastructure into which they wish
+		to put UNIX workstations or servers. Winbind will allow these
+		organizations to deploy UNIX workstations without having to
+		maintain a separate account infrastructure. This greatly
+		simplifies the administrative overhead of deploying UNIX
+		workstations into an NT-based organization.</para>
+
+		<para>
+<indexterm><primary>Appliances</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+		Another interesting way in which we expect Winbind to
+		be used is as a central part of UNIX-based appliances. Appliances
+		that provide file and print services to Microsoft-based networks
+		will be able to use Winbind to provide seamless integration of
+		the appliance into the domain.</para>
+	</sect2>
+
+	<sect2>
+	<title>Handling of Foreign SIDs</title>
+
+	<para>
+<indexterm><primary>foreign SID</primary></indexterm>
+	The term <emphasis>foreign SID</emphasis> is often met with the reaction that it
+	is not relevant to a particular environment. The following documents an interchange
+	that took place on the Samba mailing list. It is a good example of the confusion
+	often expressed regarding the use of winbind.
+	</para>
+
+	<para>
+<indexterm><primary>local domain</primary></indexterm>
+	Fact: Winbind is needed to handle users who use workstations that are NOT part
+	of the local domain.
+	</para>
+
+	<para>
+<indexterm><primary>PDC</primary></indexterm>
+	Response: <quote>Why? I've used Samba with workstations that are not part of my domains
+	lots of times without using winbind. I thought winbind was for using Samba as a member server
+	in a domain controlled by another Samba/Windows PDC.</quote>
+	</para>
+
+	<para>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>foreign user</primary></indexterm>
+	If the Samba server will be accessed from a domain other than the local Samba domain, or
+	if there will be access from machines that are not local domain members, winbind will
+	permit the allocation of UIDs and GIDs from the assigned pool that will keep the identity
+	of the foreign user separate from users that are members of the Samba domain.
+	</para>
+
+	<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>domain non-member</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+	This means that winbind is eminently useful in cases where a single
+	Samba PDC on a local network is combined with both domain member and domain non-member workstations.
+	If winbind is not used, the user george on a Windows workstation that is not a domain
+	member will be able to access the files of a user called george in the account database
+	of the Samba server that is acting as a PDC. When winbind is used, the default condition
+	is that the local user george will be treated as the account DOMAIN\george and the
+	foreign (non-member of the domain) account will be treated as MACHINE\george because
+	each has a different SID.
+	</para>
+
+	</sect2>
+</sect1>
+
+
+
+<sect1>
+	<title>How Winbind Works</title>
+
+	<para>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>UNIX domain socket</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>PAM</primary></indexterm>
+	The Winbind system is designed around a client/server
+	architecture. A long-running <command>winbindd</command> daemon
+	listens on a UNIX domain socket waiting for requests
+	to arrive. These requests are generated by the NSS and PAM
+	clients and are processed sequentially.</para>
+
+	<para>The technologies used to implement Winbind are described
+	in detail below.</para>
+
+	<sect2>
+		<title>Microsoft Remote Procedure Calls</title>
+
+		<para>
+<indexterm><primary>Microsoft Remote Procedure Call</primary><see>MSRPC</see></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>remote management</primary></indexterm>
+<indexterm><primary>user authentication</primary></indexterm>
+<indexterm><primary>print spooling</primary></indexterm>
+		Over the last few years, efforts have been underway by various Samba Team members to implement various aspects of
+		the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network-related operations
+		between Windows NT machines, including remote management, user authentication, and print spooling. Although
+		initially this work was done to aid the implementation of Primary Domain Controller (PDC) functionality in
+		Samba, it has also yielded a body of code that can be used for other purposes.
+		</para>
+
+		<para>
+<indexterm><primary>MSRPC</primary></indexterm>
+<indexterm><primary>enumerate domain users</primary></indexterm>
+<indexterm><primary>enumerate domain groups</primary></indexterm>
+		Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about
+		individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user
+		passwords. By directly querying a Windows PDC for user and group information, Winbind maps the NT account
+		information onto UNIX user and group names.
+		</para>
+	</sect2>
+
+	<sect2>
+		<title>Microsoft Active Directory Services</title>
+
+		<para>
+<indexterm><primary>LDAP</primary></indexterm>
+<indexterm><primary>Kerberos</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>native mode</primary></indexterm>
+		Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its <quote>native
+		mode</quote> protocols rather than the NT4 RPC services.  Using LDAP and Kerberos, a domain member running
+		Winbind can enumerate users and groups in exactly the same way as a Windows 200x client would, and in so doing
+		provide a much more efficient and effective Winbind implementation.
+		</para>
+	</sect2>
+
+	<sect2>
+		<title>Name Service Switch</title>
+
+		<para>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>networked workstation</primary></indexterm>
+<indexterm><primary>NIS</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+		The NSS is a feature that is present in many UNIX operating systems. It allows system
+		information such as hostnames, mail aliases, and user information
+		to be resolved from different sources. For example, a standalone
+		UNIX workstation may resolve system information from a series of
+		flat files stored on the local file system. A networked workstation
+		may first attempt to resolve system information from local files,
+		and then consult an NIS database for user information or a DNS server
+		for hostname information.</para>
+
+		<para>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>MSRPC</primary></indexterm>
+<indexterm><primary>trusted domain</primary></indexterm>
+<indexterm><primary>local users</primary></indexterm>
+<indexterm><primary>local groups</primary></indexterm>
+		The NSS application programming interface allows Winbind to present itself as a source of system
+		information when resolving UNIX usernames and groups. Winbind uses this interface and information obtained
+		from a Windows NT server using MSRPC calls to provide a new source of account enumeration. Using standard UNIX
+		library calls, you can enumerate the users and groups on a UNIX machine running Winbind and see all users and
+		groups in an NT domain plus any trusted domain as though they were local users and groups.
+		</para>
+
+		<para>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+<indexterm><primary>passwd</primary></indexterm>
+		The primary control file for NSS is <filename>/etc/nsswitch.conf</filename>.  When a UNIX application
+		makes a request to do a lookup, the C library looks in <filename>/etc/nsswitch.conf</filename> for a line that
+		matches the service type being requested; for example, the <quote>passwd</quote> service type is used when
+		user or group names are looked up. This config line specifies which implementations of that service should be
+		tried and in what order. If the passwd config line is:
+<screen>
+passwd: files example
+</screen>
+<indexterm><primary>/lib/libnss_files.so</primary></indexterm>
+<indexterm><primary>/lib/libnss_example.so</primary></indexterm>
+<indexterm><primary>resolver functions</primary></indexterm>
+		then the C library will first load a module called <filename>/lib/libnss_files.so</filename> followed
+		by the module <filename>/lib/libnss_example.so</filename>. The C library will dynamically load each of these
+		modules in turn and call resolver functions within the modules to try to resolve the request. Once the request
+		is resolved, the C library returns the result to the application.
+		</para>
+
+		<para>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>libnss_winbind.so</primary></indexterm>
+<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+		This NSS interface provides an easy way for Winbind to hook into the operating system. All that needs
+		to be done is to put <filename>libnss_winbind.so</filename> in <filename>/lib/</filename> then add
+		<quote>winbind</quote> into <filename>/etc/nsswitch.conf</filename> at the appropriate place. The C library
+		will then call Winbind to resolve user and group names.
+		</para>
+	</sect2>
+
+	<sect2>
+		<title>Pluggable Authentication Modules</title>
+
+		<para>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>authentication methods</primary></indexterm>
+<indexterm><primary>authorization</primary></indexterm>
+<indexterm><primary>NIS database</primary></indexterm>
+		PAMs provide a system for abstracting authentication and authorization technologies. With a PAM
+		module, it is possible to specify different authentication methods for different system applications without
+		having to recompile these applications. PAM is also useful for implementing a particular policy for
+		authorization. For example, a system administrator may only allow console logins from users stored in the
+		local password file but only allow users resolved from an NIS database to log in over the network.
+		</para>
+
+		<para>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>authentication management</primary></indexterm>
+<indexterm><primary>password management</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+		Winbind uses the authentication management and password management PAM interface to integrate Windows
+		NT users into a UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated
+		against a suitable PDC.  These users can also change their passwords and have this change take effect directly
+		on the PDC.
+		</para>
+
+		<para>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>/etc/pam.d/</primary></indexterm>
+<indexterm><primary>pam_winbind.so</primary></indexterm>
+<indexterm><primary>/lib/security/</primary></indexterm>
+		PAM is configured by providing control files in the directory <filename>/etc/pam.d/</filename> for
+		each of the services that require authentication. When an authentication request is made by an application,
+		the PAM code in the C library looks up this control file to determine what modules to load to do the
+		authentication check and in what order. This interface makes adding a new authentication service for Winbind
+		very easy: simply copy the <filename>pam_winbind.so</filename> module to <filename>/lib/security/</filename>,
+		and the PAM control files for relevant services are updated to allow authentication via Winbind. See the PAM
+		documentation in <link linkend="pam">PAM-Based Distributed Authentication</link>, for more information.
+		</para>
+	</sect2>
+
+	<sect2>
+		<title>User and Group ID Allocation</title>
+
+		<para>
+<indexterm><primary>RID</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>UNIX ID</primary></indexterm>
+		When a user or group is created under Windows NT/200x, it is allocated a numerical relative identifier
+		(RID). This is slightly different from UNIX, which has a range of numbers that are used to identify users and
+		the same range used to identify groups. It is Winbind's job to convert RIDs to UNIX ID numbers and vice versa.
+		When Winbind is configured, it is given part of the UNIX user ID space and a part of the UNIX group ID space
+		in which to store Windows NT users and groups. If a Windows NT user is resolved for the first time, it is
+		allocated the next UNIX ID from the range. The same process applies for Windows NT groups. Over time, Winbind
+		will have mapped all Windows NT users and groups to UNIX user IDs and group IDs.
+		</para>
+
+		<para>
+<indexterm><primary>ID mapping database</primary></indexterm>
+<indexterm><primary>tdb</primary></indexterm>
+<indexterm><primary>UNIX ID</primary></indexterm>
+<indexterm><primary>RID</primary></indexterm>
+		The results of this mapping are stored persistently in an ID mapping database held in a tdb database.
+		This ensures that RIDs are mapped to UNIX IDs in a consistent way.
+		</para>
+	</sect2>
+
+	<sect2>
+		<title>Result Caching</title>
+
+		<para>
+<indexterm><primary>SAM</primary></indexterm>
+<indexterm><primary>caching scheme</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+		An active directory system can generate a lot of user and group name lookups. To reduce the network
+		cost of these lookups, Winbind uses a caching scheme based on the SAM sequence number supplied by NT domain
+		controllers. User or group information returned by a PDC is cached by Winbind along with a sequence number
+		also returned by the PDC. This sequence number is incremented by Windows NT whenever any user or group
+		information is modified. If a cached entry has expired, the sequence number is requested from the PDC and
+		compared against the sequence number of the cached entry.  If the sequence numbers do not match, then the
+		cached information is discarded and up-to-date information is requested directly from the PDC.
+		</para>
+	</sect2>
+</sect1>
+
+
+<sect1>
+	<title>Installation and Configuration</title>
+
+<sect2>
+<title>Introduction</title>
+
+<para>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>authentication control</primary></indexterm>
+This section describes the procedures used to get Winbind up and running. Winbind is capable of providing
+access and authentication control for Windows Domain users through an NT or Windows 200x PDC for regular
+services, such as telnet and ftp, as well for Samba services.
+</para>
+
+<itemizedlist>
+<listitem>
+	<para>
+	<emphasis>Why should I do this?</emphasis>
+	</para>
+
+	<para>
+<indexterm><primary>Samba administrator</primary></indexterm>
+<indexterm><primary>authentication mechanisms</primary></indexterm>
+<indexterm><primary>domain members</primary></indexterm>
+<indexterm><primary>accounts</primary></indexterm>
+This allows the Samba administrator to rely on the authentication mechanisms on the Windows NT/200x PDC
+for the authentication of domain members. Windows NT/200x users no longer need to have separate accounts on
+the Samba server.
+	</para>
+</listitem>
+
+<listitem>
+	<para>
+	<emphasis>Who should be reading this document?</emphasis>
+	</para>
+
+	<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>Windows NT/200x</primary></indexterm>
+This document is designed for system administrators. If you are implementing Samba on a file server and wish
+to (fairly easily) integrate existing Windows NT/200x users from your PDC onto the Samba server, this document
+is for you.
+	</para>
+</listitem>
+</itemizedlist>
+</sect2>
+
+
+<sect2>
+<title>Requirements</title>
+
+<para>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>back up</primary></indexterm>
+<indexterm><primary>boot disk`</primary></indexterm>
+If you have a Samba configuration file that you are currently using, <emphasis>BACK IT UP!</emphasis>
+If your system already uses PAM, <emphasis>back up the <filename>/etc/pam.d</filename> directory
+contents!</emphasis> If you haven't already made a boot disk, <emphasis>MAKE ONE NOW!</emphasis>
+</para>
+
+<para>
+<indexterm><primary>PAM configuration</primary></indexterm>
+<indexterm><primary>/etc/pam.d</primary></indexterm>
+<indexterm><primary>single-user mode</primary></indexterm>
+Messing with the PAM configuration files can make it nearly impossible to log in to your machine. That's
+why you want to be able to boot back into your machine in single-user mode and restore your
+<filename>/etc/pam.d</filename> to the original state it was in if you get frustrated with the
+way things are going.
+</para>
+
+<para>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>daemon</primary></indexterm>
+The latest version of Samba-3 includes a functioning winbindd daemon. Please refer to the <ulink
+url="http://samba.org/">main Samba Web page</ulink>, or better yet, your closest Samba mirror site for
+instructions on downloading the source code.
+</para>
+
+<para>
+<indexterm><primary>domain users</primary></indexterm>
+<indexterm><primary>shares and files</primary></indexterm>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>development libraries</primary></indexterm>
+To allow domain users the ability to access Samba shares and files, as well as potentially other services
+provided by your Samba machine, PAM must be set up properly on your
+machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed
+on your system. Please refer to the PAM Web site <ulink url="http://www.kernel.org/pub/linux/libs/pam/"/>.
+</para>
+</sect2>
+
+<sect2>
+<title>Testing Things Out</title>
+
+<para>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>/etc/pam.d</primary></indexterm>
+<indexterm><primary>PAM</primary></indexterm>
+Before starting, it is probably best to kill off all the Samba-related daemons running on your server.
+Kill off all &smbd;, &nmbd;, and &winbindd; processes that may be running. To use PAM,
+make sure that you have the standard PAM package that supplies the <filename>/etc/pam.d</filename>
+directory structure, including the PAM modules that are used by PAM-aware services, several PAM libraries,
+and the <filename>/usr/doc</filename> and <filename>/usr/man</filename> entries for PAM. Winbind is built
+better in Samba if the pam-devel package is also installed. This package includes the header files
+needed to compile PAM-aware applications.
+</para>
+
+<sect3>
+<title>Configure <filename>nsswitch.conf</filename> and the Winbind Libraries on Linux and Solaris</title>
+
+<para>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>pam-devel</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+PAM is a standard component of most current generation UNIX/Linux systems. Unfortunately, few systems install
+the <filename>pam-devel</filename> libraries that are needed to build PAM-enabled Samba. Additionally, Samba-3
+may auto-install the Winbind files into their correct locations on your system, so before you get too far down
+the track, be sure to check if the following configuration is really
+necessary. You may only need to configure
+<filename>/etc/nsswitch.conf</filename>.
+</para>
+
+<para>
+The libraries needed to run the &winbindd; daemon through nsswitch need to be copied to their proper locations:
+</para>
+
+<para>
+<indexterm><primary>libnss_winbind.so</primary></indexterm>
+<screen>
+&rootprompt;<userinput>cp ../samba/source/nsswitch/libnss_winbind.so /lib</userinput>
+</screen>
+</para>
+
+<para>
+I also found it necessary to make the following symbolic link:
+</para>
+
+<para>
+&rootprompt; <userinput>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</userinput>
+</para>
+
+<para>And, in the case of Sun Solaris:
+<indexterm><primary>nss_winbind.so.1</primary></indexterm>
+<screen>
+&rootprompt;<userinput>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</userinput>
+&rootprompt;<userinput>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</userinput>
+&rootprompt;<userinput>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</userinput>
+</screen>
+</para>
+
+<para>
+<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
+As root, edit <filename>/etc/nsswitch.conf</filename> to allow user and group entries to be visible from the
+&winbindd; daemon. My <filename>/etc/nsswitch.conf</filename> file looked like this after editing:
+<programlisting>
+passwd:     files winbind
+shadow:     files
+group:      files winbind
+</programlisting></para>
+
+<para>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>ldconfig</primary></indexterm>
+<indexterm><primary>libnss_winbind</primary></indexterm>
+<indexterm><primary>grep</primary></indexterm>
+<indexterm><primary>dynamic link loader</primary></indexterm>
+The libraries needed by the <command>winbindd</command> daemon will be automatically
+entered into the <command>ldconfig</command> cache the next time
+your system reboots, but it is faster (and you do not need to reboot) if you do it manually:
+<screen>
+&rootprompt;<userinput>/sbin/ldconfig -v | grep winbind</userinput>
+</screen>
+This makes <filename>libnss_winbind</filename> available to winbindd and reports the current
+search path that is used by the dynamic link loader. The use of the <command>grep</command>
+filters the output of the <command>ldconfig</command> command so that we may see proof that
+this library is indeed recognized by the dynamic link loader.
+</para>
+
+<para>
+<indexterm><primary>dynamic link loader</primary></indexterm>
+<indexterm><primary>crle</primary></indexterm>
+<indexterm><primary>/usr/local/lib</primary></indexterm>
+<indexterm><primary>link loader configuration</primary></indexterm>
+<indexterm><primary>object module dependencies</primary></indexterm>
+The Sun Solaris dynamic link loader management tool is called <command>crle</command>. The
+use of this tool is necessary to instruct the dynamic link loader to search directories that
+contain library files that were not supplied as part of the original operating system platform.
+The following example shows how to use this tool to add the directory <filename>/usr/local/lib</filename>
+to the dynamic link loader's search path:
+<screen>
+&rootprompt; crle -u -l /usr/lib:/usr/local/lib
+</screen>
+When executed without arguments, <command>crle</command> reports the current dynamic
+link loader configuration. This is demonstrated here:
+<screen>
+&rootprompt; crle
+
+Configuration file [version 4]: /var/ld/ld.config
+  Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
+  Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system default)
+
+Command line:
+  crle -c /var/ld/ld.config -l /lib:/usr/lib:/usr/local/lib
+</screen>
+From this it is apparent that the <filename>/usr/local/lib</filename> directory is included
+in the search dynamic link libraries in order to satisfy object module dependencies.
+</para>
+
+</sect3>
+
+<sect3>
+<title>NSS Winbind on AIX</title>
+
+<para>(This section is only for those running AIX.)</para>
+
+<para>
+<indexterm><primary>AIX</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>/usr/lib/security</primary></indexterm>
+<indexterm><primary>authentication module API</primary></indexterm>
+<indexterm><primary>/usr/lib/security/methods.cfg</primary></indexterm>
+<indexterm><primary>PAM module</primary></indexterm>
+The Winbind AIX identification module gets built as <filename>libnss_winbind.so</filename> in the
+nsswitch directory of the Samba source. This file can be copied to <filename>/usr/lib/security</filename>,
+and the AIX naming convention would indicate that it should be named WINBIND. A stanza like the following:
+<programlisting>
+WINBIND:
+        program = /usr/lib/security/WINBIND
+        options = authonly
+</programlisting>
+can then be added to <filename>/usr/lib/security/methods.cfg</filename>. This module only supports
+identification, but there have been reports of success using the standard Winbind PAM module for
+authentication. Use caution configuring loadable authentication modules, since misconfiguration can make
+it impossible to log on to the system.  Information regarding the AIX authentication module API can
+be found in the <quote>Kernel Extensions and Device Support Programming Concepts for AIX</quote> document that
+describes the <ulink url="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixprggd/kernextc/sec_load_mod.htm">
+Loadable Authentication Module Programming Interface</ulink> for AIX. Further information on administering the modules
+can be found in the <ulink url="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/baseadmn/iandaadmin.htm">System
+Management Guide: Operating System and Devices.</ulink>
+</para>
+</sect3>
+
+<sect3>
+<title>Configure smb.conf</title>
+
+<para>
+<indexterm><primary>winbind</primary></indexterm>
+<indexterm><primary>man page</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+Several parameters are needed in the &smb.conf; file to control the behavior of &winbindd;. These
+are described in more detail in the <citerefentry><refentrytitle>winbindd</refentrytitle>
+<manvolnum>8</manvolnum></citerefentry> man page. My &smb.conf; file, as shown in <link
+linkend="winbindcfg">the smb.conf for Winbind Setup</link>, was modified to include the necessary entries in the [global] section.
+</para>
+
+<example id="winbindcfg">
+<title>smb.conf for Winbind Setup</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfcomment> separate domain and username with '\', like DOMAIN\username</smbconfcomment>
+<smbconfoption name="winbind separator">\</smbconfoption>
+<smbconfcomment> use uids from 10000 to 20000 for domain users</smbconfcomment>
+<smbconfoption name="idmap uid">10000-20000</smbconfoption>
+<smbconfcomment> use gids from 10000 to 20000 for domain groups</smbconfcomment>
+<smbconfoption name="idmap gid">10000-20000</smbconfoption>
+<smbconfcomment> allow enumeration of winbind users and groups</smbconfcomment>
+<smbconfoption name="winbind enum users">yes</smbconfoption>
+<smbconfoption name="winbind enum groups">yes</smbconfoption>
+<smbconfcomment> give winbind users a real shell (only needed if they have telnet access)</smbconfcomment>
+<smbconfoption name="template homedir">/home/winnt/%D/%U</smbconfoption>
+<smbconfoption name="template shell">/bin/bash</smbconfoption>
+</smbconfblock>
+</example>
+
+</sect3>
+
+
+<sect3>
+<title>Join the Samba Server to the PDC Domain</title>
+
+<para>
+<indexterm><primary>domain security</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>BDC</primary></indexterm>
+All machines that will participate in domain security should be members of
+the domain. This applies also to the PDC and all BDCs.
+</para>
+
+<para>
+<indexterm><primary>joining domain</primary></indexterm>
+<indexterm><primary>domain join</primary></indexterm>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>MS DCE RPC</primary></indexterm>
+<indexterm><primary>DCE RPC</primary></indexterm>
+<indexterm><primary>RPC</primary></indexterm>
+The process of joining a domain requires the use of the <command>net rpc join</command>
+command. This process communicates with the domain controller it will register with
+(usually the PDC) via MS DCE RPC. This means, of course, that the <command>smbd</command>
+process must be running on the target domain controller. It is therefore necessary to temporarily
+start Samba on a PDC so that it can join its own domain.
+</para>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>administrative privileges</primary></indexterm>
+<indexterm><primary>Administrator</primary></indexterm>
+Enter the following command to make the Samba server join the domain, where <replaceable>PDC</replaceable> is
+the name of your PDC and <replaceable>Administrator</replaceable> is a domain user who has administrative
+privileges in the domain.
+</para>
+
+<note><para>
+<indexterm><primary>domain controller</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>tcp ports</primary></indexterm>
+<indexterm><primary>udp ports</primary></indexterm>
+Before attempting to join a machine to the domain, verify that Samba is running
+on the target domain controller (usually PDC) and that it is capable of being reached via ports
+137/udp, 135/tcp, 139/tcp, and 445/tcp (if Samba or Windows Server 2Kx).
+</para></note>
+
+<para>
+<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
+The use of the <command>net rpc join</command> facility is shown here:
+<screen>
+&rootprompt;<userinput>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</userinput>
+</screen>
+The proper response to the command should be <quote>Joined the domain
+<replaceable>DOMAIN</replaceable></quote> where <replaceable>DOMAIN</replaceable>
+is your domain name.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Starting and Testing the <command>winbindd</command> Daemon</title>
+
+<para>
+<indexterm><primary>startup script</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>Winbind services</primary></indexterm>
+Eventually, you will want to modify your Samba startup script to automatically invoke the winbindd daemon when
+the other parts of Samba start, but it is possible to test out just the Winbind portion first. To start up
+Winbind services, enter the following command as root:
+<screen>
+&rootprompt;<userinput>/usr/local/samba/sbin/winbindd</userinput>
+</screen>
+Use the appropriate path to the location of the <command>winbindd</command> executable file.
+</para>
+
+<note><para>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>/usr/local/samba</primary></indexterm>
+The command to start up Winbind services assumes that Samba has been installed in the
+<filename>/usr/local/samba</filename> directory tree. You may need to search for the location of Samba files
+if this is not the location of <command>winbindd</command> on your system.
+</para></note>
+
+<para>
+<indexterm><primary>paranoid</primary></indexterm>
+<indexterm><primary>daemon running</primary></indexterm>
+I'm always paranoid and like to make sure the daemon is really running.
+<screen>
+&rootprompt;<userinput>ps -ae | grep winbindd</userinput>
+</screen>
+</para>
+
+<para>
+<indexterm><primary>winbindd</primary></indexterm>
+This command should produce output like the following if the daemon is running.
+<screen>
+3025 ?        00:00:00 winbindd
+</screen>
+</para>
+
+<para>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>wbinfo</primary></indexterm>
+Now, for the real test, try to get some information about the users on your PDC:
+<screen>
+&rootprompt;<userinput>/usr/local/samba/bin/wbinfo -u</userinput>
+</screen>
+This should echo back a list of users on your Windows users on your PDC. For example, I get the following
+response:
+<screen>
+CEO\Administrator
+CEO\burdell
+CEO\Guest
+CEO\jt-ad
+CEO\krbtgt
+CEO\TsInternetUser
+</screen>
+Obviously, I have named my domain <quote>CEO</quote> and my <smbconfoption name="winbind separator"/> is
+<quote>\</quote>.
+</para>
+
+<para>
+<indexterm><primary>wbinfo</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+You can do the same sort of thing to get group information from the PDC:
+<screen>
+&rootprompt;<userinput>/usr/local/samba/bin/wbinfo -g</userinput>
+CEO\Domain Admins
+CEO\Domain Users
+CEO\Domain Guests
+CEO\Domain Computers
+CEO\Domain Controllers
+CEO\Cert Publishers
+CEO\Schema Admins
+CEO\Enterprise Admins
+CEO\Group Policy Creator Owners
+</screen></para>
+
+<para>
+<indexterm><primary>getent</primary></indexterm>
+<indexterm><primary>PDC</primary></indexterm>
+<indexterm><primary>/etc/passwd</primary></indexterm>
+<indexterm><primary>UID</primary></indexterm>
+<indexterm><primary>GID</primary></indexterm>
+<indexterm><primary>home directories</primary></indexterm>
+<indexterm><primary>default shells</primary></indexterm>
+The function <command>getent</command> can now be used to get unified lists of both local and PDC users and
+groups. Try the following command:
+<screen>
+&rootprompt;<userinput>getent passwd</userinput>
+</screen>
+You should get a list that looks like your <filename>/etc/passwd</filename>
+list followed by the domain users with their new UIDs, GIDs, home
+directories, and default shells.
+</para>
+
+<para>
+The same thing can be done for groups with the command:
+<screen>
+&rootprompt;<userinput>getent group</userinput>
+</screen>
+</para>
+
+</sect3>
+
+
+<sect3>
+<title>Fix the init.d Startup Scripts</title>
+
+<sect4>
+<title>Linux</title>
+
+<para>
+<indexterm><primary>winbindd daemon</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>/etc/init.d/smb</primary></indexterm>
+<indexterm><primary>/etc/init.d/samba</primary></indexterm>
+<indexterm><primary>/usr/local/samba/bin</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+<indexterm><primary></primary></indexterm>
+<indexterm><primary></primary></indexterm>
+The &winbindd; daemon needs to start up after the &smbd; and &nmbd; daemons are running.  To accomplish this
+task, you need to modify the startup scripts of your system.  They are located at
+<filename>/etc/init.d/smb</filename> in Red Hat Linux and in <filename>/etc/init.d/samba</filename> in Debian
+Linux. Edit your script to add commands to invoke this daemon in the proper sequence. My startup script starts
+up &smbd;, &nmbd;, and &winbindd; from the <filename>/usr/local/samba/bin</filename> directory directly. The
+<command>start</command> function in the script looks like this:
+<programlisting>
+start() {
+        KIND="SMB"
+        echo -n $"Starting $KIND services: "
+        daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
+        RETVAL=$?
+        echo
+        KIND="NMB"
+        echo -n $"Starting $KIND services: "
+        daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
+        RETVAL2=$?
+        echo
+        KIND="Winbind"
+        echo -n $"Starting $KIND services: "
+        daemon /usr/local/samba/sbin/winbindd
+        RETVAL3=$?
+        echo
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &amp;&amp; \
+		touch /var/lock/subsys/smb || RETVAL=1
+        return $RETVAL
+}
+</programlisting></para>
+
+<para>If you would like to run winbindd in dual daemon mode, replace the line:
+<programlisting>
+        daemon /usr/local/samba/sbin/winbindd
+</programlisting>
+
+in the example above with:
+
+<programlisting>
+        daemon /usr/local/samba/sbin/winbindd -B
+</programlisting>.
+</para>
+
+<para>
+The <command>stop</command> function has a corresponding entry to shut down the services and looks like this:
+</para>
+
+<para><programlisting>
+stop() {
+        KIND="SMB"
+        echo -n $"Shutting down $KIND services: "
+        killproc smbd
+        RETVAL=$?
+        echo
+        KIND="NMB"
+        echo -n $"Shutting down $KIND services: "
+        killproc nmbd
+        RETVAL2=$?
+        echo
+        KIND="Winbind"
+        echo -n $"Shutting down $KIND services: "
+        killproc winbindd
+        RETVAL3=$?
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &amp;&amp; \
+		 rm -f /var/lock/subsys/smb
+        echo ""
+        return $RETVAL
+}
+</programlisting></para>
+</sect4>
+
+<sect4>
+<title>Solaris</title>
+
+<para>
+Winbind does not work on Solaris 9; see <link linkend="winbind-solaris9">Winbind on Solaris 9 section</link>
+for details.
+</para>
+
+<para>
+<indexterm><primary>Solaris 9</primary></indexterm>
+<indexterm><primary>/etc/init.d/samba.server</primary></indexterm>
+<indexterm><primary>/usr/local/samba/bin</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+On Solaris, you need to modify the <filename>/etc/init.d/samba.server</filename> startup script. It
+usually only starts smbd and nmbd but should now start winbindd, too. If you have Samba installed in
+<filename>/usr/local/samba/bin</filename>, the file could contains something like this:
+</para>
+
+<para>
+	<programlisting>
+	##
+	## samba.server
+	##
+
+	if [ ! -d /usr/bin ]
+	then                    # /usr not mounted
+		exit
+	fi
+
+	killproc() {            # kill the named process(es)
+		pid=`/usr/bin/ps -e |
+		     /usr/bin/grep -w $1 |
+		     /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
+		[ "$pid" != "" ] &amp;&amp; kill $pid
+	}
+
+	# Start/stop processes required for Samba server
+
+	case "$1" in
+
+	'start')
+	#
+	# Edit these lines to suit your installation (paths, workgroup, host)
+	#
+	echo Starting SMBD
+	   /usr/local/samba/bin/smbd -D -s \
+		/usr/local/samba/smb.conf
+
+	echo Starting NMBD
+	   /usr/local/samba/bin/nmbd -D -l \
+		/usr/local/samba/var/log -s /usr/local/samba/smb.conf
+
+	echo Starting Winbind Daemon
+	   /usr/local/samba/sbin/winbindd
+	   ;;
+
+	'stop')
+	   killproc nmbd
+	   killproc smbd
+	   killproc winbindd
+	   ;;
+
+	*)
+	   echo "Usage: /etc/init.d/samba.server { start | stop }"
+	   ;;
+	esac
+</programlisting></para>
+
+<para>
+Again, if you would like to run Samba in dual daemon mode, replace:
+<programlisting>
+/usr/local/samba/sbin/winbindd
+</programlisting>
+in the script above with:
+<programlisting>
+/usr/local/samba/sbin/winbindd -B
+</programlisting>
+</para>
+
+</sect4>
+
+<sect4>
+<title>Restarting</title>
+<para>
+<indexterm><primary>daemons</primary></indexterm>
+<indexterm><primary>local user</primary></indexterm>
+If you restart the &smbd;, &nmbd;, and &winbindd; daemons at this point, you
+should be able to connect to the Samba server as a domain member just as
+if you were a local user.
+</para>
+</sect4>
+</sect3>
+
+<sect3>
+<title>Configure Winbind and PAM</title>
+
+<para>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>authentication</primary></indexterm>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>/etc/pam.d</primary></indexterm>
+If you have made it this far, you know that <command>winbindd</command> and Samba are working together. If you
+want to use Winbind to provide authentication for other services, keep reading. The PAM configuration files
+need to be altered in this step. (Did you remember to make backups of your original
+<filename>/etc/pam.d</filename> files? If not, do it now.)
+</para>
+
+<para>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>../source/nsswitch</primary></indexterm>
+<indexterm><primary>pam_winbind.so</primary></indexterm>
+<indexterm><primary>/lib/security</primary></indexterm>
+<indexterm><primary>Solaris</primary></indexterm>
+<indexterm><primary>/usr/lib/security</primary></indexterm>
+You will need a PAM module to use winbindd with these other services. This module will be compiled in the
+<filename>../source/nsswitch</filename> directory by invoking the command:
+<screen>
+&rootprompt;<userinput>make nsswitch/pam_winbind.so</userinput>
+</screen>
+from the <filename>../source</filename> directory. The <filename>pam_winbind.so</filename> file should be
+copied to the location of your other PAM security modules. On my Red Hat system, this was the
+<filename>/lib/security</filename> directory. On Solaris, the PAM security modules reside in
+<filename>/usr/lib/security</filename>.
+<screen>
+&rootprompt;<userinput>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</userinput>
+</screen>
+</para>
+
+<sect4>
+<title>Linux/FreeBSD-Specific PAM Configuration</title>
+
+<para>
+<indexterm><primary>/etc/pam.d/samba</primary></indexterm>
+The <filename>/etc/pam.d/samba</filename> file does not need to be changed. I just left this file as it was:
+<programlisting>
+auth    required  /lib/security/pam_stack.so service=system-auth
+account required  /lib/security/pam_stack.so service=system-auth
+</programlisting></para>
+
+<para>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>authentication service</primary></indexterm>
+<indexterm><primary>login</primary></indexterm>
+<indexterm><primary>console</primary></indexterm>
+<indexterm><primary>telnet logins</primary></indexterm>
+<indexterm><primary>ftp service</primary></indexterm>
+<indexterm><primary>/etc/xinetd.d</primary></indexterm>
+<indexterm><primary>/etc/inetd.conf</primary></indexterm>
+<indexterm><primary>/etc/xinetd.d/telnet</primary></indexterm>
+The other services that I modified to allow the use of Winbind as an authentication service were the normal
+login on the console (or a terminal session), telnet logins, and ftp service. In order to enable these
+services, you may first need to change the entries in <filename>/etc/xinetd.d</filename> (or
+<filename>/etc/inetd.conf</filename>).  Red Hat Linux 7.1 and later uses the new xinetd.d structure, in this
+case you need to change the lines in <filename>/etc/xinetd.d/telnet</filename> and
+<filename>/etc/xinetd.d/wu-ftp</filename> from:
+<programlisting>
+	enable = no
+</programlisting>
+to
+<programlisting>
+	enable = yes
+</programlisting></para>
+
+<para>
+<indexterm><primary>ftp services</primary></indexterm>
+<indexterm><primary>home directory template</primary></indexterm>
+<indexterm><primary>domain users</primary></indexterm>
+For ftp services to work properly, you will also need to either have individual directories for the domain
+users already present on the server or change the home directory template to a general directory for all
+domain users. These can be easily set using the &smb.conf; global entry <smbconfoption name="template
+homedir"/>.
+</para>
+
+<note><para>
+<indexterm><primary>pam_mkhomedir</primary></indexterm>
+The directory in <smbconfoption name="template homedir"/> is not created automatically! Use pam_mkhomedir or
+pre-create the directories of users to make sure users can log in on UNIX with their own home directory.
+</para></note>
+
+<para>
+<indexterm><primary>/etc/pam.d/ftp</primary></indexterm>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>ftp access</primary></indexterm>
+The <filename>/etc/pam.d/ftp</filename> file can be changed to allow Winbind ftp access in a manner similar to
+the samba file. My <filename>/etc/pam.d/ftp</filename> file was changed to look like this:
+<programlisting>
+auth       required     /lib/security/pam_listfile.so item=user sense=deny \
+	 file=/etc/ftpusers onerr=succeed
+auth       sufficient   /lib/security/pam_winbind.so
+auth       required     /lib/security/pam_stack.so service=system-auth
+auth       required     /lib/security/pam_shells.so
+account    sufficient   /lib/security/pam_winbind.so
+account    required     /lib/security/pam_stack.so service=system-auth
+session    required     /lib/security/pam_stack.so service=system-auth
+</programlisting></para>
+
+<para>
+<indexterm><primary>/etc/pam.d/login</primary></indexterm>
+The <filename>/etc/pam.d/login</filename> file can be changed in nearly the same way. It now looks like this:
+<programlisting>
+auth       required     /lib/security/pam_securetty.so
+auth       sufficient   /lib/security/pam_winbind.so
+auth       sufficient   /lib/security/pam_unix.so use_first_pass
+auth       required     /lib/security/pam_stack.so service=system-auth
+auth       required     /lib/security/pam_nologin.so
+account    sufficient   /lib/security/pam_winbind.so
+account    required     /lib/security/pam_stack.so service=system-auth
+password   required     /lib/security/pam_stack.so service=system-auth
+session    required     /lib/security/pam_stack.so service=system-auth
+session    optional     /lib/security/pam_console.so
+</programlisting>
+<indexterm><primary>pam_winbind.so</primary></indexterm>
+<indexterm><primary>pam_securetty.so</primary></indexterm>
+<indexterm><primary>pam_unix.so</primary></indexterm>
+In this case, I added the <programlisting>auth sufficient /lib/security/pam_winbind.so</programlisting> lines
+as before, but also added the <programlisting>required pam_securetty.so</programlisting> above it to disallow
+root logins over the network. I also added a <programlisting>sufficient /lib/security/pam_unix.so
+use_first_pass</programlisting> line after the <command>winbind.so</command> line to get rid of annoying
+double prompts for passwords.
+</para>
+
+</sect4>
+
+<sect4>
+<title>Solaris-Specific Configuration</title>
+
+<para>
+<indexterm><primary>/etc/pam.conf</primary></indexterm>
+<indexterm><primary></primary></indexterm>
+The <filename>/etc/pam.conf</filename> needs to be changed. I changed this file so my Domain
+users can log on both locally as well as with telnet. The following are the changes
+that I made. You can customize the <filename>pam.conf</filename> file as per your requirements, but
+be sure of those changes because in the worst case it will leave your system
+nearly impossible to boot.
+<programlisting>
+#
+#ident "@(#)pam.conf 1.14 99/09/16 SMI"
+#
+# Copyright (c) 1996-1999, Sun Microsystems, Inc.
+# All Rights Reserved.
+#
+# PAM configuration
+#
+# Authentication management
+#
+login   auth required   /usr/lib/security/pam_winbind.so
+login auth required  /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+login auth required  /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass
+#
+rlogin  auth sufficient /usr/lib/security/pam_winbind.so
+rlogin  auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
+rlogin auth required  /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+dtlogin auth sufficient /usr/lib/security/pam_winbind.so
+dtlogin auth required  /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1
+other   auth sufficient /usr/lib/security/pam_winbind.so
+other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+# Account management
+#
+login   account sufficient      /usr/lib/security/pam_winbind.so
+login account requisite /usr/lib/security/$ISA/pam_roles.so.1
+login account required /usr/lib/security/$ISA/pam_unix.so.1
+#
+dtlogin account sufficient      /usr/lib/security/pam_winbind.so
+dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1
+dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1
+#
+other   account sufficient      /usr/lib/security/pam_winbind.so
+other account requisite /usr/lib/security/$ISA/pam_roles.so.1
+other account required /usr/lib/security/$ISA/pam_unix.so.1
+#
+# Session management
+#
+other session required /usr/lib/security/$ISA/pam_unix.so.1
+#
+# Password management
+#
+#other   password sufficient     /usr/lib/security/pam_winbind.so
+other password required /usr/lib/security/$ISA/pam_unix.so.1
+dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1
+#
+# Support for Kerberos V5 authentication (uncomment to use Kerberos)
+#
+#rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other account optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other session optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+</programlisting></para>
+
+<para>
+<indexterm><primary>winbind.so</primary></indexterm>
+I also added a <parameter>try_first_pass</parameter> line after the <filename>winbind.so</filename>
+line to get rid of annoying double prompts for passwords.
+</para>
+
+<para>
+Now restart your Samba and try connecting through your application that you
+configured in the pam.conf.
+</para>
+
+</sect4>
+
+</sect3>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Conclusion</title>
+
+<para>
+<indexterm><primary>Winbind</primary></indexterm>
+<indexterm><primary>NSS</primary></indexterm>
+<indexterm><primary>PAM</primary></indexterm>
+<indexterm><primary>RPC calls</primary></indexterm>
+<indexterm><primary>domain users</primary></indexterm>
+The Winbind system, through the use of the NSS, PAMs, and appropriate Microsoft RPC calls, have allowed us to
+provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great
+reduction in the administrative cost of running a mixed UNIX and NT network.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+	<para>
+	Winbind has a number of limitations in its current released version that we hope to overcome in future releases:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		Winbind is currently only available for the Linux, Solaris, AIX, and IRIX operating systems, although
+		ports to other operating systems are certainly possible. For such ports to be feasible, we require the C
+		library of the target operating system to support the NSS and PAM systems. This is becoming more common as NSS
+		and PAM gain support among UNIX vendors.
+		</para></listitem>
+
+		<listitem><para>
+		The mappings of Windows NT RIDs to UNIX IDs is not made algorithmically and depends on the order in
+		which unmapped users or groups are seen by Winbind. It may be difficult to recover the mappings of RID to UNIX
+		ID if the file containing this information is corrupted or destroyed.
+		</para></listitem>
+
+		<listitem><para>
+		Currently the Winbind PAM module does not take into account possible workstation and logon time
+		restrictions that may be set for Windows NT users; this is instead up to the PDC to enforce.
+		</para></listitem>
+	</itemizedlist>
+
+	<sect2>
+	<title>NSCD Problem Warning</title>
+
+	<warning><para>
+	Do not under any circumstances run <command>nscd</command> on any system
+	on which <command>winbindd</command> is running.
+	</para></warning>
+
+	<para>
+	If <command>nscd</command> is running on the UNIX/Linux system, then
+	even though NSSWITCH is correctly configured, it will not be possible to resolve
+	domain users and groups for file and directory controls.
+	</para>
+
+	</sect2>
+
+	<sect2>
+	<title>Winbind Is Not Resolving Users and Groups</title>
+
+	<para><quote>
+	My &smb.conf; file is correctly configured. I have specified <smbconfoption name="idmap uid">12000</smbconfoption>,
+	and <smbconfoption name="idmap gid">3000-3500</smbconfoption> and <command>winbind</command> is running.
+	When I do the following, it all works fine.
+	</quote></para>
+
+<para><screen>
+&rootprompt;<userinput>wbinfo -u</userinput>
+MIDEARTH\maryo
+MIDEARTH\jackb
+MIDEARTH\ameds
+...
+MIDEARTH\root
+
+&rootprompt;<userinput>wbinfo -g</userinput>
+MIDEARTH\Domain Users
+MIDEARTH\Domain Admins
+MIDEARTH\Domain Guests
+...
+MIDEARTH\Accounts
+
+&rootprompt;<userinput>getent passwd</userinput>
+root:x:0:0:root:/root:/bin/bash
+bin:x:1:1:bin:/bin:/bin/bash
+...
+maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
+</screen></para>
+
+<para><quote>
+But the following command just fails:
+</quote>
+<screen>
+&rootprompt;<userinput>chown maryo a_file</userinput>
+chown: `maryo': invalid user
+</screen>
+<quote>
+This is driving me nuts! What can be wrong?
+</quote></para>
+
+<para>
+Same problem as the one above.
+Your system is likely running <command>nscd</command>, the name service
+caching daemon. Shut it down, do not restart it! You will find your problem resolved.
+Alternately, fix the operation of nscd to resolve the problem.
+</para>
+
+</sect2>
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml b/docs-xml/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml
new file mode 100644
index 00000000000..50ee1c63e0a
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml
@@ -0,0 +1,599 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="ClientConfig">
+<chapterinfo>
+	&author.jht;
+</chapterinfo>
+
+<title>MS Windows Network Configuration Guide</title>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>network difficulty</primary></indexterm>
+<indexterm><primary>network client</primary></indexterm>
+<indexterm><primary>client client instructions</primary></indexterm>
+Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate
+correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way
+to configure an MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x
+servers. Yet there is repetitious need to provide detailed Windows client configuration instructions.
+</para>
+
+<para>
+<indexterm><primary>graphically illustrated client configuration</primary></indexterm>
+<indexterm><primary>critical aspects of configuration</primary></indexterm>
+The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common
+critical aspects of such configuration. An experienced network administrator will not be interested in the
+details of this chapter.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Technical Details</title>
+
+<para>
+<indexterm><primary>TCP/IP protocol configuration</primary></indexterm>
+<indexterm><primary>network membership</primary></indexterm>
+This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms
+that are in common use today. These are:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Microsoft Windows XP Professional
+	</para></listitem>
+	<listitem><para>
+	Windows 2000 Professional
+	</para></listitem>
+	<listitem><para>
+	Windows Millennium edition (Me)
+	</para></listitem>
+</itemizedlist>
+
+	<sect2>
+	<title>TCP/IP Configuration</title>
+
+	<para>
+<indexterm><primary>network configuration problems</primary></indexterm>
+<indexterm><primary>plague network users</primary></indexterm>
+	The builder of a house must ensure that all construction takes place on a firm foundation.
+	The same is true for the builder of a TCP/IP-based networking system. Fundamental network configuration problems
+	will plague all network users until they are resolved. 
+	</para>
+
+	<para>
+<indexterm><primary>fixed IP addresses</primary></indexterm>
+<indexterm><primary>DHCP</primary></indexterm>
+	MS Windows workstations and servers can be configured either with fixed
+	IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP
+	and make only passing reference to those situations where fixed IP configuration
+	settings can be effected.
+	</para>
+
+	<para>
+<indexterm><primary>shortcuts</primary></indexterm>
+<indexterm><primary>abbreviated keystrokes</primary></indexterm>
+	It is possible to use shortcuts or abbreviated keystrokes to arrive at a
+	particular configuration screen. The decision was made to base all examples in this
+	chapter on use of the <guibutton>Start</guibutton> button.
+	</para>
+
+		<sect3>
+		<title>MS Windows XP Professional</title>
+
+		<para>
+<indexterm><primary>Windows XP TCP/IP</primary></indexterm>
+		There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer:
+		</para>
+
+		<para>
+		Click <guimenu>Start -> Control Panel -> Network Connections</guimenu>.
+		</para>
+
+		<para>
+		<emphasis>Alternately,</emphasis> click <guimenu>Start -></guimenu>, and right-click <guimenu>My Network Places</guimenu>
+		then select <guimenuitem>Properties</guimenuitem>.
+		</para>
+
+		<para>
+<indexterm><primary>Windows XP Professional</primary></indexterm>
+		The following procedure steps through the Windows XP Professional TCP/IP configuration process:
+		</para>
+
+		<procedure>
+			<step><para>
+<indexterm><primary>Local Area Connection</primary></indexterm>
+<indexterm><primary>Network Bridge</primary></indexterm>
+<indexterm><primary>interface</primary></indexterm>
+			On some installations the interface will be called <guimenu>Local Area Connection</guimenu> and
+			on others it will be called <guimenu>Network Bridge</guimenu>. On our system it is called <guimenu>Network Bridge</guimenu>.
+			Right-click on <guimenu>Network Bridge -> Properties</guimenu>. See <link linkend="WXPP002"/>.
+			<figure id="WXPP002"><title>Network Bridge Configuration.</title><imagefile>WXPP002</imagefile></figure>
+			</para>
+			</step>
+
+			<step><para>
+<indexterm><primary>TCP/IP protocol settings</primary></indexterm>
+<indexterm><primary>Network Bridge Configuration</primary></indexterm>
+			The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings.
+			In <guimenuitem>This connection uses the following items:</guimenuitem> box,
+			click on <guimenu>Internet Protocol (TCP/IP)</guimenu>, then click on <guibutton>Properties</guibutton>.
+			</para>
+
+			<para>
+<indexterm><primary>DHCP-enabled operation</primary></indexterm>
+<indexterm><primary>IP address automatically</primary></indexterm>
+			The default setting is DHCP-enabled operation
+			(i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="WXPP003"/>.
+			<figure id="WXPP003">
+				<title>Internet Protocol (TCP/IP) Properties.</title>
+				<imagefile>WXPP003</imagefile>
+			</figure>
+			</para>
+
+			<para>
+<indexterm><primary>DHCP</primary></indexterm>
+<indexterm><primary>TCP/IP</primary></indexterm>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>ISC DHCP server</primary></indexterm>
+			Many network administrators will want to use DHCP to configure all client TCP/IP
+			protocol stack settings. (For information on how to configure the ISC DHCP server
+			for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>,
+			<link linkend="DHCP">DHCP Server</link>.
+			</para>
+
+			<para>
+<indexterm><primary>fixed IP address</primary></indexterm>
+<indexterm><primary>subnet mask</primary></indexterm>
+<indexterm><primary>gateway address</primary></indexterm>
+			If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and enter the
+			IP Address, the subnet mask, and the default gateway address in the boxes provided.
+			</para></step>
+
+			<step><para>
+<indexterm><primary>Advanced TCP/IP configuration</primary></indexterm>
+<indexterm><primary>TCP/IP configuration</primary></indexterm>
+<indexterm><primary>IP aliases</primary></indexterm>
+<indexterm><primary>default gateways</primary></indexterm>
+			Click the <guibutton>Advanced</guibutton> button to proceed with TCP/IP configuration.
+			This opens a panel in which it is possible to create additional IP addresses for this interface.
+			The technical name for the additional addresses is <emphasis>IP aliases</emphasis>, and additionally this
+			panel permits the setting of more default gateways (routers). In most cases where DHCP is used, it will not be
+			necessary to create additional settings. See <link linkend="WXPP005"></link> to see the appearance of this panel.
+			<figure id="WXPP005"><title>Advanced Network Settings</title><imagefile>WXPP005</imagefile></figure>
+			</para>
+
+			<para>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>DHCP</primary></indexterm>
+			Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
+			</para></step>
+
+			<step><para>
+<indexterm><primary>DNS server settings</primary></indexterm>
+<indexterm><primary>manually configured DNS settings</primary></indexterm>
+			Click the <guimenu>DNS</guimenu> tab to add DNS server settings. 
+			The example system uses manually configured DNS settings. When finished making changes, click the
+			<guibutton>OK</guibutton> to commit the settings. See <link linkend="WXPP014"/>.
+			<figure id="WXPP014"> <title>DNS Configuration.</title> <imagefile>WXPP014</imagefile> </figure>
+			</para></step>
+
+			<step><para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>manual WINS server entries</primary></indexterm>
+			Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries. 
+			This step demonstrates an example system that uses manually configured WINS settings. 
+			When finished making changes, click <guibutton>OK</guibutton> to commit
+                        the settings. See <link linkend="WXPP009"></link>.
+			<figure id="WXPP009"><title>WINS Configuration</title><imagefile>WXPP009</imagefile></figure>
+			</para></step>
+		</procedure>
+
+		</sect3>
+
+		<sect3>
+		<title>MS Windows 2000</title>
+
+		<para>
+<indexterm><primary>Windows 2000 Professional TCP/IP</primary></indexterm>
+<indexterm><primary>TCP/IP configuration panel</primary></indexterm>
+		There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer:
+		</para>
+
+		<para>
+		Click <guimenu>Start -> Control Panel -> Network and Dial-up Connections</guimenu>.
+		</para>
+
+		<para>
+		<emphasis>Alternatively,</emphasis> click <guimenu>Start</guimenu>, then right-click <guimenu>My Network Places</guimenu>, and
+		select <guimenuitem>Properties</guimenuitem>.
+		</para>
+
+		<para>
+<indexterm><primary>Windows XP Professional TCP/IP</primary></indexterm>
+		The following procedure steps through the Windows XP Professional TCP/IP configuration process:
+		</para>
+
+		<procedure>
+			<step><para>
+			Right-click on <guimenu>Local Area Connection</guimenu>, then click
+			<guimenuitem>Properties</guimenuitem>. See <link linkend="w2kp001"></link>.
+			<figure id="w2kp001"><title>Local Area Connection Properties.</title><imagefile>w2kp001</imagefile></figure>
+			</para></step>
+
+			<step><para>
+<indexterm><primary>Local Area Connection Properties</primary></indexterm>
+<indexterm><primary>TCP/IP protocol settings</primary></indexterm>
+			The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on
+			<guimenu>Internet Protocol (TCP/IP)</guimenu> in the <guimenuitem>Components checked are used by this
+			connection:</guimenuitem> box, then click the <guibutton>Properties</guibutton> button.
+			</para></step>
+
+			<step><para>
+<indexterm><primary>DHCP-enabled</primary></indexterm>
+<indexterm><primary>IP address automatically</primary></indexterm>
+			The default setting is DHCP-enabled operation
+			(i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="w2kp002"/>.
+			<figure id="w2kp002"><title>Internet Protocol (TCP/IP) Properties.</title><imagefile>w2kp002</imagefile></figure>
+			</para>
+
+			<para>
+<indexterm><primary>DHCP</primary></indexterm>
+<indexterm><primary>protocol stack settings</primary></indexterm>
+			Many network administrators will want to use DHCP to configure all client TCP/IP
+			protocol stack settings. (For information on how to configure the ISC DHCP server
+			for Windows client support, see, <link linkend="DHCP"></link>.
+			</para>
+
+			<para>
+<indexterm><primary>fixed IP address</primary></indexterm>
+<indexterm><primary>network clients</primary></indexterm>
+			If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and enter the
+			IP Address, the subnet mask, and the default gateway address in the boxes provided.
+			For this example we are assuming that all network clients will be configured using DHCP.
+			</para></step>
+
+			<step><para>
+			Click the <guimenu>Advanced</guimenu> button to proceed with TCP/IP configuration.
+			Refer to <link linkend="w2kp003"></link>.
+			<figure id="w2kp003"><title>Advanced Network Settings.</title><imagefile>w2kp003</imagefile></figure>
+			</para>
+
+			<para>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>DHCP</primary></indexterm>
+			Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
+			</para></step>
+
+			<step><para>
+<indexterm><primary>DNS server settings</primary></indexterm>
+<indexterm><primary>commit the settings</primary></indexterm>
+			Click the <guimenu>DNS</guimenu> tab to add DNS server settings. 
+			The example system uses manually configured DNS settings. When finished making changes,
+			click <guibutton>OK</guibutton> to commit the settings. See <link linkend="w2kp004"></link>.
+			<figure id="w2kp004"><title>DNS Configuration.</title><imagefile>w2kp004</imagefile></figure>
+			</para></step>
+
+			<step><para>
+<indexterm><primary>manual WINS server entries</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+			Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries. 
+			This step demonstrates an example system that uses manually configured WINS settings. 
+			When finished making changes, click <guibutton>OK</guibutton> to commit the settings.
+			See <link linkend="w2kp005"></link>.
+			<figure id="w2kp005">
+				<title>WINS Configuration.</title><imagefile>w2kp005</imagefile>
+			</figure>
+			</para></step>
+
+		</procedure>
+
+		</sect3>
+
+		<sect3>
+		<title>MS Windows Me</title>
+
+		<para>
+<indexterm><primary>Windows Millennium edition (Me) TCP/IP</primary></indexterm>
+<indexterm><primary>Windows Millennium</primary></indexterm>
+<indexterm><primary>TCP/IP configuration</primary></indexterm>
+		There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer:
+		</para>
+
+		<para>
+		Click <guimenu>Start -> Control Panel -> Network Connections</guimenu>.
+		</para>
+
+		<para>
+<indexterm><primary>My Network Places</primary></indexterm>
+<indexterm><primary>Properties</primary></indexterm>
+		<emphasis>Alternatively,</emphasis> click on <guimenu>Start -></guimenu>, and right click on <guimenu>My Network Places</guimenu>
+		then select <guimenuitem>Properties</guimenuitem>.
+		</para>
+
+		<para>
+<indexterm><primary>Windows Me TCP/IP</primary></indexterm>
+		The following procedure steps through the Windows Me TCP/IP configuration process:
+		</para>
+
+		<procedure>
+			<step><para>
+<indexterm><primary>Internet Protocol TCP/IP</primary></indexterm>
+			In the box labeled <guimenuitem>The following network components are installed:</guimenuitem>,
+			click on <guimenu>Internet Protocol TCP/IP</guimenu>, then click on the <guibutton>Properties</guibutton> button.
+			See <link linkend="WME001"></link>.
+			<figure id="WME001">
+				<title>The Windows Me Network Configuration Panel.</title>
+				<imagefile>WME001</imagefile>
+			</figure>
+			</para></step>
+
+			<step><para>
+<indexterm><primary>DHCP</primary></indexterm>
+<indexterm><primary>TCP/IP</primary></indexterm>
+<indexterm><primary>ISC DHCP server</primary></indexterm>
+			Many network administrators will want to use DHCP to configure all client TCP/IP
+			protocol stack settings. (For information on how to configure the ISC DHCP server
+			for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>,
+			<link linkend="DHCP">DHCP Server</link>. The default setting on Windows Me workstations is for DHCP-enabled operation
+			(i.e., <guimenu>Obtain IP address automatically</guimenu> is enabled). See <link linkend="WME002"></link>.
+			<figure id="WME002"><title>IP Address.</title><imagefile>WME002</imagefile></figure>
+			</para>
+
+			<para>
+<indexterm><primary>Specify an IP address</primary></indexterm>
+<indexterm><primary>subnet mask</primary></indexterm>
+<indexterm><primary>DHCP</primary></indexterm>
+			If it is necessary to provide a fixed IP address, click on <guimenuitem>Specify an IP address</guimenuitem> and enter the
+			IP Address and the subnet mask in the boxes provided. For this example we are assuming that all
+			network clients will be configured using DHCP.
+			</para></step>
+
+			<step><para>
+<indexterm><primary>DNS</primary></indexterm>
+<indexterm><primary>WINS</primary></indexterm>
+			Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
+			</para></step>
+
+			<step><para>
+<indexterm><primary>WINS server settings</primary></indexterm>
+			If necessary, click the <guimenu>DNS Configuration</guimenu> tab to add DNS server settings. 
+			Click the <guibutton>WINS Configuration</guibutton> tab to add WINS server settings. 
+			The <guimenu>Gateway</guimenu> tab allows additional gateways (router addresses) to be added to the network
+			interface settings. In most cases where DHCP is used, it will not be necessary to
+			create these manual settings.
+			</para></step>
+
+			<step><para>
+<indexterm><primary>WINS</primary></indexterm>
+<indexterm><primary>manually configured</primary></indexterm>
+			The following example uses manually configured WINS settings. See <link linkend="WME005"></link>.
+			When finished making changes, click <guibutton>OK</guibutton> to commit the settings.
+			<figure id="WME005"><title>DNS Configuration.</title><imagefile>WME005</imagefile></figure>
+			</para>
+
+			<para>
+<indexterm><primary>single DHCP server</primary></indexterm>
+<indexterm><primary>multiple Windows workgroups or domains</primary></indexterm>
+			This is an example of a system that uses manually configured WINS settings. One situation where
+			this might apply is on a network that has a single DHCP server that provides settings for multiple
+			Windows workgroups or domains. See <link linkend="WME003"></link>.
+			<figure id="WME003"><title>WINS Configuration.</title><imagefile>WME003</imagefile></figure>
+			</para></step>
+		</procedure>
+
+
+		</sect3>
+
+	</sect2>
+
+	<sect2>
+	<title>Joining a Domain: Windows 2000/XP Professional</title>
+
+	<para>
+<indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
+<indexterm><primary>domain security</primary></indexterm>
+<indexterm><primary>domain member</primary></indexterm>
+<indexterm><primary>domain joining</primary></indexterm>
+	Microsoft Windows NT/200x/XP Professional platforms can participate in domain security.
+	This section steps through the process for making a Windows 200x/XP Professional machine a
+	member of a domain security environment. It should be noted that this process is identical
+	when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
+	</para>
+
+	<procedure>
+		<step><para>
+		Click <guimenu>Start</guimenu>.
+		</para></step>
+
+		<step><para>
+		Right-click <guimenu>My Computer</guimenu>, then select <guimenuitem>Properties</guimenuitem>.
+		</para></step>
+
+		<step><para>
+<indexterm><primary>Control Panel</primary></indexterm>
+		The opening panel is the same one that can be reached by clicking <guimenu>System</guimenu> on the Control Panel.
+		See <link linkend="wxpp001"></link>.
+		<figure id="wxpp001"><title>The General Panel.</title><imagefile>wxpp001</imagefile></figure>
+		</para></step>
+
+		<step><para>
+<indexterm><primary>Computer Name</primary></indexterm>
+		Click the <guimenu>Computer Name</guimenu> tab.
+		This panel shows the <guimenuitem>Computer Description</guimenuitem>, the <guimenuitem>Full computer name</guimenuitem>,
+		and the <guimenuitem>Workgroup</guimenuitem> or <guimenuitem>Domain name</guimenuitem>.
+		</para>
+
+		<para>
+<indexterm><primary>Network ID</primary></indexterm>
+<indexterm><primary>configuration wizard</primary></indexterm>
+		Clicking the <guimenu>Network ID</guimenu> button will launch the configuration wizard. Do not use this with
+		Samba-3. If you wish to change the computer name or join or leave the domain, click the <guimenu>Change</guimenu> button.
+		See <link linkend="wxpp004"></link>.
+		<figure id="wxpp004"><title>The Computer Name Panel.</title><imagefile>wxpp004</imagefile></figure>
+		</para></step>
+
+		<step><para>
+		Click on <guimenu>Change</guimenu>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP.
+		We will join the domain called MIDEARTH. See <link linkend="wxpp006"></link>.
+		<figure id="wxpp006"><title>The Computer Name Changes Panel.</title><imagefile>wxpp006</imagefile></figure>
+        </para></step>
+
+		<step><para>
+<indexterm><primary>domain radio button</primary></indexterm>
+		Enter the name <guimenu>MIDEARTH</guimenu> in the field below the domain radio button.
+		</para>
+
+        <para>
+		This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <link linkend="wxpp007"></link>.
+		<figure id="wxpp007"><title>The Computer Name Changes Panel &smbmdash; Domain MIDEARTH.</title><imagefile>wxpp007</imagefile></figure>
+        </para></step>
+
+		<step><para>
+<indexterm><primary>credentials</primary></indexterm>
+<indexterm><primary>username and password</primary></indexterm>
+		Now click the <guimenu>OK</guimenu> button. A dialog box should appear to allow you to provide the
+		credentials (username and password) of a domain administrative account that has the rights to add machines to
+		the domain.
+		</para>
+
+        <para>
+<indexterm><primary>root</primary></indexterm>
+		Enter the name <quote>root</quote> and the root password from your Samba-3 server. See <link linkend="wxpp008"></link>.
+		<figure id="wxpp008">
+			<title>Computer Name Changes &smbmdash; Username and Password Panel.</title><imagefile>wxpp008</imagefile>
+		</figure>
+        </para></step>
+
+		<step><para>
+		Click on <guimenu>OK</guimenu>.
+        </para>
+
+		<para>
+<indexterm><primary>Welcome</primary></indexterm>
+<indexterm><primary>rebooted</primary></indexterm>
+		The <quote>Welcome to the MIDEARTH domain.</quote> dialog box should appear. At this point the machine must be rebooted.
+		Joining the domain is now complete.
+        </para></step>
+
+	</procedure>
+
+	</sect2>
+
+	<sect2>
+	<title>Domain Logon Configuration: Windows 9x/Me</title>
+
+	<para>
+<indexterm><primary>Windows 9x/Me</primary></indexterm>
+<indexterm><primary>domain logon</primary></indexterm>
+<indexterm><primary>LanManager</primary></indexterm>
+	We follow the convention used by most in saying that Windows 9x/Me machines can participate in domain logons. The truth is
+	that these platforms can use only the LanManager network logon protocols.
+	</para>
+
+	<note><para>
+<indexterm><primary>Windows XP Home edition</primary></indexterm>
+<indexterm><primary>LanManager</primary></indexterm>
+<indexterm><primary>network logon</primary></indexterm>
+	Windows XP Home edition cannot participate in domain or LanManager network logons.
+	</para></note>
+
+	<procedure>
+		<step><para>
+		Right-click on the <guimenu>Network Neighborhood</guimenu> icon.
+		</para></step>
+
+		<step><para>
+		The Network Configuration Panel allows all common network settings to be changed.
+                See <link linkend="WME009"></link>.
+		<figure id="WME009"><title>The Network Panel.</title><imagefile>WME009</imagefile></figure>
+                </para>
+
+		<para>
+<indexterm><primary>Client for Microsoft Networks</primary></indexterm>
+<indexterm><primary>Properties</primary></indexterm>
+		Make sure that the <guimenu>Client for Microsoft Networks</guimenu> driver is installed as shown.
+		Click on the <guimenu>Client for Microsoft Networks</guimenu> entry in <guimenu>The following network
+		components are installed:</guimenu> box. Then click the <guibutton>Properties</guibutton> button.
+		</para></step>
+
+		<step><para>
+<indexterm><primary>Networks Properties</primary></indexterm>
+<indexterm><primary>network logon</primary></indexterm>
+		The Client for Microsoft Networks Properties panel is the correct location to configure network logon
+		settings. See <link linkend="WME010"></link>.
+		<figure id="WME010"><title>Client for Microsoft Networks Properties Panel.</title><imagefile>WME010</imagefile></figure>
+                </para>
+
+		<para>
+<indexterm><primary>Windows NT domain name</primary></indexterm>
+<indexterm><primary>domain name</primary></indexterm>
+		Enter the Windows NT domain name, check the <guimenu>Log on to Windows NT domain</guimenu> box,
+		and click <guimenu>OK</guimenu>.
+		</para></step>
+
+		<step><para>
+<indexterm><primary>Identification</primary></indexterm>
+<indexterm><primary>workgroup</primary></indexterm>
+<indexterm><primary>computer name</primary></indexterm>
+		Click on the <guimenu>Identification</guimenu> button. This is the location at which the workgroup
+		(domain) name and the machine name (computer name) need to be set. See <link linkend="WME013"></link>.
+		<figure id="WME013"><title>Identification Panel.</title><imagefile>WME013</imagefile></figure>
+                </para></step>
+
+		<step><para>
+<indexterm><primary>Access Control</primary></indexterm>
+<indexterm><primary>group accounts</primary></indexterm>
+<indexterm><primary>domain user</primary></indexterm>
+<indexterm><primary>User-level access control</primary></indexterm>
+		Now click the <guimenu>Access Control</guimenu> button. If you want to be able to assign share access
+		permissions using domain user and group accounts, it is necessary to enable
+		<guimenu>User-level access control</guimenu> as shown in this panel.  See <link linkend="WME014"></link>.
+		<figure id="WME014"><title>Access Control Panel.</title><imagefile>WME014</imagefile></figure>
+                </para></step>
+
+	</procedure>
+
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+<indexterm><primary>networking systems</primary></indexterm>
+<indexterm><primary>errors that can afflict</primary></indexterm>
+The most common errors that can afflict Windows networking systems include:
+</para>
+
+<itemizedlist>
+	<listitem><para>Incorrect IP address.</para></listitem>
+	<listitem><para>Incorrect or inconsistent netmasks.</para></listitem>
+	<listitem><para>Incorrect router address.</para></listitem>
+	<listitem><para>Incorrect DNS server address.</para></listitem>
+	<listitem><para>Incorrect WINS server address.</para></listitem>
+	<listitem><para>Use of a Network Scope setting &smbmdash; watch out for this one!</para></listitem>
+</itemizedlist>
+
+<para>
+<indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
+<indexterm><primary>cannot join domain</primary></indexterm>
+The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are:
+</para>
+
+<itemizedlist>
+	<listitem><para>&smb.conf; does not have correct <smbconfoption name="add machine script"/> settings.</para></listitem>
+	<listitem><para><quote>root</quote> account is not in password backend database.</para></listitem>
+	<listitem><para>Attempt to use a user account instead of the <quote>root</quote> account to join a machine to the domain.</para></listitem>
+	<listitem><para>Open connections from the workstation to the server.</para></listitem>
+	<listitem><para>Firewall or filter configurations in place on either the client or the Samba server.</para></listitem>
+</itemizedlist>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml b/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml
new file mode 100644
index 00000000000..6331d2fd4e3
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml
@@ -0,0 +1,79 @@
+<?xml version='1.0'?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<preface>
+<title>Foreword</title>
+
+<para>
+When John first asked me to write an introductory piece for his latest book, I was somewhat mystified as to
+why he chose me. A conversation with John provided some of the rationale, and he left it to me to fill in the
+<emphasis>rest</emphasis> of the story. So, if you are willing to endure a little bit of background, I will
+provide the part of the story that John wouldn't provide.
+</para>
+
+<para>
+I am the Director of Corporate Standards at Sun Microsystems, and manage Sun's standards portfolio. Before
+that, I was the Director of Standards at Netscape, which was when I met John. Before Sun, there was Digital
+Equipment Corporation, also standards. I've written several books on standards, and tend to observe (and
+occasionally help) the technical and business trends that drive standardization as a discipline. I tend to see
+standardization as a management tool, not as a technical discipline and this is part of the rationale that
+John provided.
+</para>
+
+<para>
+The book that you have before you focuses on a particular standardized way of doing something hence, it is a
+book about a standard. The most important thing to keep in mind about a standard is the rationale for its
+creation. Standards are created not for technical reasons, not for business reasons, but for a deeper and much
+more compelling reason. Standards are created and used to allow people to communicate in a meaningful way.
+Every standard, if it is a true standard, has as its entire (and only) goal set the increasing of relevant
+communication between people.
+</para>
+
+<para>
+This primary goal cannot be met however, unless the standard is documented. I have been involved in too many
+standardization efforts when it became apparent that <emphasis>everybody knows</emphasis> was the dominant
+emotion of those providing documentation. <emphasis>They</emphasis> of the ever present <emphasis>they
+say</emphasis> and <emphasis>they know</emphasis> are the bane of good standards. If <emphasis>they
+know</emphasis>, why are you doing a standard?
+</para>
+
+<para>
+A <emphasis>good standard</emphasis> survives because people know how to use it. People know how to use a
+standard when it is so transparent, so obvious, and so easy that it become invisible. And a standard becomes
+invisible only when the documentation describing how to deploy it is clear, unambiguous, and correct. These
+three elements must be present for a standard to be useful, allowing communication and interaction between two
+separate and distinct entities to occur without obvious effort. As you read this book, look for the evidence
+of these three characteristics and notice how they are seamlessly woven into John's text. Clarity and
+unambiguity without <emphasis>correctness</emphasis> provide a technical nightmare. Correctness and clarity
+with ambiguity create <emphasis>maybe bits,</emphasis> and correctness and unambiguity without clarity provide
+a <emphasis>muddle through</emphasis> scenario.
+</para>
+
+<para>
+And this is <emphasis>the rest of the story</emphasis> that John couldn't (or wouldn't) bring himself to
+state. This book provides a clear, concise, unambiguous, and technically valid presentation of Samba to make
+it useful to a user to someone who wants to use the standard to increase communication and the capability
+for communication between two or more entities whether person-machine, machine-machine, or person-person.
+The intent of this book is not to convince anyone of any agenda political, technical, or social. The intent
+is to provide documentation for users who need to know about Samba, how to use it, and how to get on with
+their primary responsibilities. While there is pride on John's part because of the tremendous success of
+the Samba documentation, he writes for the person who needs a tool to accomplish a particular job, and who has
+selected Samba to be that tool.
+</para>
+
+<para>
+The book is a monument to John's perseverance and dedication to Samba and in my opinion to the goal of
+standardization. By writing this book, John has provided the users of Samba those that want to deploy it to
+make things better a clear, easy, and ultimately valuable resource. Additionally, he has increased the
+understanding and utility of a highly useful standard, and for this, as much as for the documentation, he is
+owed a debt of gratitude by those of us who rely on standards to make our lives more manageable.
+</para>
+
+<para>
+<simplelist>
+	<member>Carl Cargill, Senior Director</member>
+	<member>Corporate Standardization, The Office of the CTO</member>
+	<member>Sun Microsystems</member>
+</simplelist>
+</para>
+	
+</preface>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-foreword-tridge.xml b/docs-xml/Samba3-HOWTO/TOSHARG-foreword-tridge.xml
new file mode 100644
index 00000000000..34bc37314d7
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-foreword-tridge.xml
@@ -0,0 +1,48 @@
+<?xml version='1.0'?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<preface>
+<title>Foreword</title>
+
+<para>
+Over the last few years, the Samba project has undergone a major
+transformation. From a small project used only by people who dream in
+machine code, Samba has grown to be an integral part of the IT
+infrastructure of many businesses. Along with the growth in the
+popularity of Samba there has been a corresponding growth in the ways
+that it can be used, and a similar growth in the number of
+configuration options and the interactions between them.
+</para>
+
+<para>
+To address this increasing complexity a wealth of documentation has
+been written on Samba, including numerous HOWTOs, diagnostic tips,
+manual pages, and explanations of important pieces of technology that
+Samba relies on. While it has been gratifying to see so much
+documentation being written, the sheer volume of different types of
+documentation has proved difficult to navigate, thus reducing its
+value to system administrators trying to cope with the complexity.
+</para>
+
+<para>
+This book gathers together that wealth of information into a much more
+accessible form, to allow system administrators to quickly find what
+they need. The breadth of technical information provided ensures that
+even the most demanding administrators will find something helpful.
+</para>
+
+<para>
+I am delighted that the Samba documentation has now developed to the
+extent that it can be presented usefully as a book, and I am grateful
+for the efforts of the many people who have contributed so much
+toward this result. Enjoy!
+</para>
+
+<para>
+<simplelist>
+	<member>Andrew Tridgell</member>
+	<member><emphasis>President, Samba Team</emphasis></member>
+	<member><emphasis>July 2003</emphasis></member>
+</simplelist>
+</para>
+	
+</preface>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-glossary.xml b/docs-xml/Samba3-HOWTO/TOSHARG-glossary.xml
new file mode 100644
index 00000000000..6410e3e0f78
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-glossary.xml
@@ -0,0 +1,254 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE glossary PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<glossary>
+	<title>Glossary</title>
+
+	<glossentry>
+		<glossterm>Access Control List</glossterm>
+		<acronym>ACL</acronym>
+		<glossdef><para>
+		A detailed list of permissions granted to users or groups with respect to file and network resource access.
+		 See <link linkend="AccessControls"/>, 
+		for details.</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Active Directory Service</glossterm>
+		<acronym>ADS</acronym>
+		<glossdef><para>
+		A service unique to Microsoft Windows 200x servers that provides a centrally managed
+		directory for management of user identities and computer objects, as well as the permissions
+		each user or computer may be granted to access
+		distributed network resources. ADS uses Kerberos-based
+		authentication and LDAP over Kerberos for directory access.
+		</para></glossdef>
+        </glossentry>
+
+	<glossentry>
+		<glossterm>Common Internet File System</glossterm>
+		<acronym>CIFS</acronym>
+		<glossdef><para>The new name for SMB. Microsoft renamed the 
+		SMB protocol to CIFS during the Internet hype in the nineties.
+		At about the time that the SMB protocol was renamed to CIFS, an
+		additional dialect of the SMB protocol was in development.
+		The need for the deployment of the NetBIOS layer was also
+		removed, thus paving the way for use of the SMB protocol natively
+		over TCP/IP (known as NetBIOS-less SMB or <quote>naked</quote>  TCP transport).
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Common UNIX Printing System</glossterm>
+		<acronym>CUPS</acronym>
+		<glossdef><para>
+		A recent implementation of a high capability printing system for UNIX developed by
+		<ulink url="http://www.easysw.com/"></ulink>. The design objective of CUPS was to provide
+		a rich print processing system that has built-in intelligence capable of correctly rendering (processing)
+		a file that is submitted for printing even if it was formatted for an entirely different printer.
+		</para>
+		</glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Domain Master Browser</glossterm>
+		<acronym>DMB</acronym>
+		<glossdef><para>The domain master browser maintains a list of all the servers that 
+		have announced their services within a given workgroup or NT domain. See <link linkend="DMB"/> for details.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+                <glossterm>Domain Name Service</glossterm>
+		<acronym>DNS</acronym>
+		<glossdef><para>
+		A protocol by which computer hostnames may be resolved to the matching IP address/es. DNS is implemented
+		by the Berkeley Internet Name Daemon. There exists a recent version of DNS that allows dynamic name registration
+		by network clients or by a DHCP server. This recent protocol is known as dynamic DNS (DDNS).
+		</para></glossdef>
+        </glossentry>
+
+	<glossentry>
+                <glossterm>Dynamic Host Configuration Protocol</glossterm>
+		<acronym>DHCP</acronym>
+		<glossdef><para>
+		A protocol that was based on the BOOTP protocol that may be used to dynamically assign an IP address,
+		from a reserved pool of addresses, to a network client or device. Additionally, DHCP may assign all
+		network configuration settings and may be used to register a computer name and its address with a
+		dynamic DNS server.
+		</para></glossdef>
+        </glossentry>
+	<glossentry>
+		<glossterm>Extended Meta-file Format</glossterm>
+		<acronym>EMF</acronym>
+		<glossdef>
+			<para>
+			An intermediate file format used by Microsoft Windows-based servers and clients. EMF files may be
+			rendered into a page description language by a print processor.
+		</para>
+		</glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Graphical Device Interface</glossterm>
+		<acronym>GDI</acronym>
+		<glossdef><para>
+		Device-independent format for printing used by Microsoft Windows. 
+		It is quite similar to what PostScript is for UNIX. Printing jobs are first generated in GDI and
+		then converted to a device-specific format. See <link linkend="gdipost"/> for details.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Group IDentifier</glossterm>
+		<acronym>GID</acronym>
+		<glossdef><para>
+		The UNIX system group identifier; on older systems, a 32-bit unsigned integer, and on newer systems
+		an unsigned 64-bit integer. The GID is used in UNIX-like operating systems for all group-level access
+		control.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Internet Print Protocol</glossterm>
+		<acronym>IPP</acronym>
+		<glossdef><para>An IETF standard for network printing. CUPS
+		implements IPP.</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Key Distribution Center</glossterm>
+		<acronym>KDC</acronym>
+		<glossdef><para>The Kerberos authentication protocol makes use of security keys (also called a ticket)
+		by which access to network resources is controlled. The issuing of Kerberos tickets is effected by
+		a KDC.</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>NetBIOS Extended User Interface</glossterm>
+		<acronym>NetBEUI</acronym>
+		<glossdef><para>
+		Very simple network protocol invented by IBM and Microsoft. It is used 
+		to do NetBIOS over Ethernet with low overhead. NetBEUI is a nonroutable
+		protocol.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Network Basic Input/Output System</glossterm>
+		<acronym>NetBIOS</acronym>
+		<glossdef><para>
+		NetBIOS is a simple application programming interface (API) invented in the 1980s 
+		that allows programs to send data to certain network names. 
+		NetBIOS is always run over another network protocol such 
+		as IPX/SPX, TCP/IP, or Logical Link Control (LLC). NetBIOS run over LLC
+		is best known as NetBEUI (NetBIOS Extended User Interface &smbmdash; a complete misnomer!).
+		</para></glossdef>
+	</glossentry>
+
+
+	<glossentry>
+		<glossterm>NetBT</glossterm>
+		<acronym>NBT</acronym>
+		<glossdef><para>Protocol for transporting NetBIOS frames over TCP/IP. Uses ports 137, 138, and 139. 
+		NetBT is a fully routable protocol.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Local Master Browser</glossterm>
+		<acronym>LMB</acronym>
+		<glossdef><para>The local master browser maintains a list 
+		of all servers that have announced themselves within a given workgroup or NT domain on a particular
+		broadcast-isolated subnet. See <link linkend="DMB"/> for details.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Printer Command Language</glossterm>
+		<acronym>PCL</acronym>
+		<glossdef><para>
+		A printer page description language that was developed by Hewlett-Packard
+		and is in common use today.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Portable Document Format</glossterm>
+		<acronym>PDF</acronym>
+		<glossdef>
+		<para>
+		A highly compressed document format, based on PostScript, used as a document distribution format
+		that is supported by Web browsers as well as many applications. Adobe also distributes an application
+		called <quote>Acrobat,</quote> which is a PDF reader.
+		</para>
+		</glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Page Description Language</glossterm>
+		<acronym>PDL</acronym>
+		<glossdef><para>A language for describing the layout and contents of a printed page.
+		The best-known PDLs are Adobe PostScript and Hewlett-Packard PCL (Printer Control Language),
+		both of which are used to control laser printers.</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>PostScript Printer Description</glossterm>
+		<acronym>PPD</acronym>
+		<glossdef><para>
+		PPDs specify and control options supported by PostScript printers, such as duplexing, stapling, 
+		and DPI. See also <link linkend="post-and-ghost"/>. PPD files can be read by printing applications
+		to enable correct PostScript page layout for a particular PostScript printer.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+        <glossterm>Remote Procedure Call</glossterm>
+        <acronym>RPC</acronym>
+        <glossdef><para>
+		RPCs are a means for executing network operations. The RPC protocol is independent of transport protocols. RPC
+		does not try to implement any kind of reliability and the application that uses RPCs must be aware of the type
+		of transport protocol underneath RPC. An RPC is like a programmatic jump subroutine over a network. RPCs used
+		in the UNIX environment are specified in RFC 1050. RPC is a powerful technique for constructing distributed,
+		client-server based applications. It is based on extending the notion of conventional, or local procedure
+		calling, so that the called procedure need not exist in the same address space as the calling procedure. The
+		two processes may be on the same system, or they may be on different systems with a network connecting them.
+		By using RPC, programmers of distributed applications avoid the details of the interface with the network. The
+		transport independence of RPC isolates the application from the physical and logical elements of the data
+		communications mechanism and allows the application to use a variety of transports.
+        </para></glossdef>
+    </glossentry>
+
+	<glossentry>
+		<glossterm>Server Message Block</glossterm>
+		<acronym>SMB</acronym>
+		<glossdef><para>
+		SMB was the original name of the protocol `spoken' by 
+		Samba. It was invented in the 1980s by IBM and adopted 
+		and extended further by Microsoft. Microsoft 
+		renamed the protocol to CIFS during the Internet hype in the 
+		1990s.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>User IDentifier</glossterm>
+		<acronym>UID</acronym>
+		<glossdef><para>
+		The UNIX system user identifier; on older systems a 32-bit unsigned integer, and on newer systems,
+		an unsigned 64-bit integer. The UID is used in UNIX-like operating systems for all user-level access
+		control.
+		</para></glossdef>
+	</glossentry>
+
+	<glossentry>
+		<glossterm>Universal Naming Convention</glossterm>
+		<acronym>UNC</acronym>
+		<glossdef><para>A syntax for specifying the location of network resources (such as file shares).
+		The UNC syntax was developed in the early days of MS DOS 3.x and is used internally by the SMB protocol.
+		</para></glossdef>
+	</glossentry>
+
+	
+
+</glossary>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-inside-cover.xml b/docs-xml/Samba3-HOWTO/TOSHARG-inside-cover.xml
new file mode 100644
index 00000000000..f1b1990d4c8
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-inside-cover.xml
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<preface lang="en-US">
+<title>About the Cover Artwork</title>
+
+	<para>
+	The cover artwork of this book continues the freedom theme of the first edition of <quote>The Official Samba-3
+	HOWTO and Reference Guide</quote>.  We may look back upon the past to question the motives of those who have
+	gone before us. Seldom do we realise that the past owes us no answer, and despite what we may think of the
+	actions of those who have travelled lifes' road before us, we must feel a sense of pride and gratitude for
+	those who, in the past, have protected our liberties.
+	</para>
+
+	<para>
+	Developments in information technology continue to move at an alarming pace. Human nature causes us
+	to adopt and embrace new developments that appear to answer the needs of the moment, but that can entrap
+	us at a future date. There are many examples in the short history of information technology. MS-DOS was
+	seen as a tool that liberated users from the tyrany of large computer system operating costs, and that
+	made possible the rapid progres we are beneficiaries of today. Yet today we are inclined to look back with
+	disdain on MS-DOS as an obsolete and constraining technology that belongs are an era that is best
+	forgotten.
+	</para>
+
+	<para>
+	The embrace of Windows networking, Windows NT4, and MS Active Directory in more recent times, may seem
+	modern and progressive today, but sooner or later something better will replace them. The current
+	preoccupation with extended identity management solutions and with directories is not unexpected.
+	The day will come that these too will be evaluated, and what may seem refreshing and powerful may
+	be better recogized as the chilly winds of the night. To argue against progress is unthinkable,
+	no matter what may lie ahead.
+	</para>
+
+	<para>
+	The development of Samba is moving forwards. The changes since Samba 3.0.0 are amazing, yet many
+	users would like to see more and faster progress. The benefits of recent developments can be realized
+	quickly, but documentation is necessary to unlock the pandoras' box. It is our hope that this book
+	will help the network administrator to rapidly deploy the new features with minimum effort. As you
+	deploy and gain mileage from the new enablement, take the time to think through what may lie ahead.
+	Above all, take stock of the freedom of choice that Samba provides in your world, and enjoy the new 
+	potential for seamless interoperability.
+	</para>
+
+</preface>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-locking.xml b/docs-xml/Samba3-HOWTO/TOSHARG-locking.xml
new file mode 100644
index 00000000000..ee48f8c90d6
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-locking.xml
@@ -0,0 +1,1140 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="locking">
+<chapterinfo>
+	&author.jeremy;
+	&author.jelmer;
+	&author.jht;
+	&author.eroseme;
+</chapterinfo>
+<title>File and Record Locking</title>
+
+<para>
+<indexterm><primary>locking</primary></indexterm>
+One area that causes trouble for many network administrators is locking.
+The extent of the problem is readily evident from searches over the Internet.
+</para>
+
+<sect1>
+<title>Features and Benefits</title>
+
+<para>
+<indexterm><primary>locking semantics</primary></indexterm>
+Samba provides all the same locking semantics that MS Windows clients expect
+and that MS Windows NT4/200x servers also provide.
+</para>
+
+<para>
+<indexterm><primary>locking</primary></indexterm>
+The term <emphasis>locking</emphasis> has exceptionally broad meaning and covers
+a range of functions that are all categorized under this one term.
+</para>
+
+<para>
+<indexterm><primary>opportunistic locking</primary></indexterm>
+<indexterm><primary>locking protocol</primary></indexterm>
+<indexterm><primary>performance advantage</primary></indexterm>
+Opportunistic locking is a desirable feature when it can enhance the
+perceived performance of applications on a networked client. However, the
+opportunistic locking protocol is not robust and therefore can
+encounter problems when invoked beyond a simplistic configuration or
+on extended slow or faulty networks. In these cases, operating
+system management of opportunistic locking and/or recovering from
+repetitive errors can offset the perceived performance advantage that
+it is intended to provide.
+</para>
+
+<para>
+<indexterm><primary>registry</primary></indexterm>
+The MS Windows network administrator needs to be aware that file and record
+locking semantics (behavior) can be controlled either in Samba or by way of registry
+settings on the MS Windows client.
+</para>
+
+<note>
+<para>
+<indexterm><primary>disable locking</primary></indexterm>
+Sometimes it is necessary to disable locking control settings on the Samba
+server as well as on each MS Windows client!
+</para>
+</note>
+
+</sect1>
+
+<sect1>
+<title>Discussion</title>
+
+<para>
+<indexterm><primary>record locking</primary></indexterm>
+<indexterm><primary>deny modes</primary></indexterm>
+There are two types of locking that need to be performed by an SMB server.
+The first is <emphasis>record locking</emphasis> that allows a client to lock
+a range of bytes in an open file. The second is the <emphasis>deny modes</emphasis>
+that are specified when a file is open.
+</para>
+
+<para>
+<indexterm><primary>locking semantics</primary></indexterm>
+<indexterm><primary>record locking</primary></indexterm>
+<indexterm><primary>locking</primary></indexterm>
+<indexterm><primary>byte ranges</primary></indexterm>
+<indexterm><primary>UNIX locking</primary></indexterm>
+Record locking semantics under UNIX are very different from record locking under
+Windows. Versions of Samba before 2.2 have tried to use the native fcntl() UNIX
+system call to implement proper record locking between different Samba clients.
+This cannot be fully correct for several reasons. The simplest is
+that a Windows client is allowed to lock a byte range up to 2^32 or 2^64,
+depending on the client OS. The UNIX locking only supports byte ranges up to 2^31.
+So it is not possible to correctly satisfy a lock request above 2^31. There are
+many more differences, too many to be listed here.
+</para>
+
+<para>
+<indexterm><primary>record locking</primary></indexterm>
+<indexterm><primary>byte-range lock</primary></indexterm>
+Samba 2.2 and above implement record locking completely independently of the
+underlying UNIX system. If a byte-range lock that the client requests happens
+to fall into the range of 0 to 2^31, Samba hands this request down to the UNIX system.
+No other locks can be seen by UNIX, anyway.
+</para>
+
+<para>
+<indexterm><primary>check for locks</primary></indexterm>
+<indexterm><primary>rpc.lockd</primary></indexterm>
+Strictly speaking, an SMB server should check for locks before every read and write call on
+a file. Unfortunately, with the way fcntl() works, this can be slow and may overstress
+the <command>rpc.lockd</command>. This is almost always unnecessary because clients are 
+independently supposed to make locking calls before reads and writes if locking is
+important to them. By default, Samba only makes locking calls when explicitly asked
+to by a client, but if you set <smbconfoption name="strict locking">yes</smbconfoption>, it
+will make lock checking calls on <emphasis>every</emphasis> read and write call.
+</para>
+
+<para>
+<indexterm><primary>byte-range locking</primary></indexterm>
+You can also disable byte-range locking completely by using
+<smbconfoption name="locking">no</smbconfoption>.
+This is useful for those shares that do not support locking or do not need it
+(such as CD-ROMs). In this case, Samba fakes the return codes of locking calls to
+tell clients that everything is okay.
+</para>
+
+<para>
+<indexterm><primary>deny modes</primary></indexterm>
+<indexterm><primary>DENY_NONE</primary></indexterm>
+<indexterm><primary>DENY_READ</primary></indexterm>
+<indexterm><primary>DENY_WRITE</primary></indexterm>
+<indexterm><primary>DENY_ALL</primary></indexterm>
+<indexterm><primary>DENY_FCB</primary></indexterm>
+<indexterm><primary>DENY_DOS</primary></indexterm>
+The second class of locking is the <emphasis>deny modes</emphasis>. These 
+are set by an application when it opens a file to determine what types of
+access should be allowed simultaneously with its open. A client may ask for
+<constant>DENY_NONE</constant>, <constant>DENY_READ</constant>, 
+<constant>DENY_WRITE</constant>, or <constant>DENY_ALL</constant>. There are also special compatibility
+modes called <constant>DENY_FCB</constant> and <constant>DENY_DOS</constant>.
+</para>
+
+<sect2>
+<title>Opportunistic Locking Overview</title>
+
+<para>
+<indexterm><primary>opportunistic locking</primary></indexterm>
+<indexterm><primary>oplocks</primary></indexterm>
+<indexterm><primary>caching</primary></indexterm>
+Opportunistic locking (oplocks) is invoked by the Windows file system
+(as opposed to an API) via registry entries (on the server and the client)
+for the purpose of enhancing network performance when accessing a file
+residing on a server. Performance is enhanced by caching the file
+locally on the client that allows the following:
+</para>
+
+<variablelist>
+	<varlistentry><term>Read-ahead:</term>
+		<listitem><para>
+<indexterm><primary>Read-ahead</primary></indexterm>
+		The client reads the local copy of the file, eliminating network latency.
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>Write caching:</term>
+		<listitem><para>
+<indexterm><primary>Write caching</primary></indexterm>
+		The client writes to the local copy of the file, eliminating network latency.
+		</para></listitem>
+	</varlistentry>
+
+        <varlistentry><term>Lock caching:</term>
+        <listitem><para>
+<indexterm><primary>Lock caching</primary></indexterm>
+		The client caches application locks locally, eliminating network latency.
+		</para></listitem>
+        </varlistentry>
+</variablelist>
+
+<para>
+<indexterm><primary>performance enhancement</primary></indexterm>
+<indexterm><primary>oplocks</primary></indexterm>
+<indexterm><primary>deny-none</primary></indexterm>
+The performance enhancement of oplocks is due to the opportunity of
+exclusive access to the file &smbmdash; even if it is opened with deny-none &smbmdash;
+because Windows monitors the file's status for concurrent access from
+other processes.
+</para>
+
+<variablelist>
+<title>Windows Defines Four Kinds of Oplocks:</title>
+
+		<varlistentry><term>Level1 Oplock</term>
+			<listitem><para>
+<indexterm><primary>Level1 Oplock</primary></indexterm>
+<indexterm><primary>redirector</primary></indexterm>
+<indexterm><primary>concurrent access</primary></indexterm>
+<indexterm><primary>cached local file</primary></indexterm>
+			The redirector sees that the file was opened with deny
+			none (allowing concurrent access), verifies that no
+			other process is accessing the file, checks that
+			oplocks are enabled, then grants deny-all/read-write/exclusive
+			access to the file. The client now performs
+			operations on the cached local file.
+			</para>
+
+			<para>
+<indexterm><primary>oplock break</primary></indexterm>
+<indexterm><primary>flush local locks</primary></indexterm>
+<indexterm><primary>deferred open</primary></indexterm>
+<indexterm><primary>byte-range locking</primary></indexterm>
+			If a second process attempts to open the file, the open
+			is deferred while the redirector "breaks" the original
+			oplock. The oplock break signals the caching client to
+			write the local file back to the server, flush the
+			local locks, and discard read-ahead data. The break is
+			then complete, the deferred open is granted, and the
+			multiple processes can enjoy concurrent file access as
+			dictated by mandatory or byte-range locking options.
+			However, if the original opening process opened the
+			file with a share mode other than deny-none, then the
+			second process is granted limited or no access, despite
+			the oplock break.
+			</para></listitem>
+        </varlistentry>
+
+        <varlistentry><term>Level2 Oplock</term>
+                <listitem><para>
+<indexterm><primary>Level2 Oplock</primary></indexterm>
+<indexterm><primary>Level1 oplock</primary></indexterm>
+<indexterm><primary>caching</primary></indexterm>
+				Performs like a Level1 oplock, except caching is only
+                operative for reads. All other operations are performed
+                on the server disk copy of the file.
+                </para></listitem>
+        </varlistentry>
+
+        <varlistentry><term>Filter Oplock</term>
+                <listitem><para>
+<indexterm><primary>Filter Oplock</primary></indexterm>
+				Does not allow write or delete file access.
+                </para></listitem>
+        </varlistentry>
+
+        <varlistentry><term>Batch Oplock</term>
+                <listitem><para>
+<indexterm><primary>Batch Oplock</primary></indexterm>
+				Manipulates file openings and closings and allows caching
+                of file attributes.
+                </para></listitem>
+        </varlistentry>
+</variablelist>
+
+<para>
+<indexterm><primary>oplocks</primary></indexterm>
+An important detail is that oplocks are invoked by the file system, not
+an application API. Therefore, an application can close an oplocked
+file, but the file system does not relinquish the oplock. When the
+oplock break is issued, the file system then simply closes the file in
+preparation for the subsequent open by the second process.
+</para>
+
+<para>
+<indexterm><primary>Opportunistic locking</primary></indexterm>
+<indexterm><primary>client-side data caching</primary></indexterm>
+<indexterm><primary>data caching</primary></indexterm>
+<indexterm><primary>oplock break</primary></indexterm>
+<emphasis>Opportunistic locking</emphasis> is actually an improper name for this feature.
+The true benefit of this feature is client-side data caching, and
+oplocks is merely a notification mechanism for writing data back to the
+networked storage disk. The limitation of oplocks is the
+reliability of the mechanism to process an oplock break (notification)
+between the server and the caching client. If this exchange is faulty
+(usually due to timing out for any number of reasons), then the
+client-side caching benefit is negated.
+</para>
+
+<para>
+<indexterm><primary>client-side caching</primary></indexterm>
+The actual decision that a user or administrator should consider is
+whether it is sensible to share among multiple users data that will
+be cached locally on a client. In many cases the answer is no.
+Deciding when to cache or not cache data is the real question, and thus
+oplocks should be treated as a toggle for client-side
+caching. Turn it <quote>on</quote> when client-side caching is desirable and
+reliable. Turn it <quote>off</quote> when client-side caching is redundant,
+unreliable, or counterproductive.
+</para>
+
+<para>
+<indexterm><primary>oplocks</primary></indexterm>
+Oplocks is by default set to <quote>on</quote> by Samba on all
+configured shares, so careful attention should be given to each case to
+determine if the potential benefit is worth the potential for delays.
+The following recommendations will help to characterize the environment
+where oplocks may be effectively configured.
+</para>
+
+<para>
+<indexterm><primary>oplocks</primary></indexterm>
+<indexterm><primary>high-availability</primary></indexterm>
+Windows oplocks is a lightweight performance-enhancing
+feature. It is not a robust and reliable protocol. Every
+implementation of oplocks should be evaluated as a
+trade-off between perceived performance and reliability. Reliability
+decreases as each successive rule above is not enforced. Consider a
+share with oplocks enabled, over a wide-area network, to a client on a
+South Pacific atoll, on a high-availability server, serving a
+mission-critical multiuser corporate database during a tropical
+storm. This configuration will likely encounter problems with oplocks.
+</para>
+
+<para>
+<indexterm><primary>mission-critical</primary></indexterm>
+Oplocks can be beneficial to perceived client performance when treated
+as a configuration toggle for client-side data caching. If the data
+caching is likely to be interrupted, then oplock usage should be
+reviewed. Samba enables oplocks by default on all
+shares. Careful attention should be given to the client usage of
+shared data on the server, the server network reliability, and the
+oplocks configuration of each share.
+In mission-critical, high-availability environments, data integrity is
+often a priority. Complex and expensive configurations are implemented
+to ensure that if a client loses connectivity with a file server, a
+failover replacement will be available immediately to provide
+continuous data availability.
+</para>
+
+<para>
+<indexterm><primary>Windows client failover</primary></indexterm>
+<indexterm><primary>transport connection loss</primary></indexterm>
+Windows client failover behavior is more at risk of application
+interruption than other platforms because it is dependent upon an
+established TCP transport connection. If the connection is interrupted
+&smbmdash; as in a file server failover &smbmdash; a new session must be established.
+It is rare for Windows client applications to be coded to recover
+correctly from a transport connection loss; therefore, most applications
+will experience some sort of interruption &smbmdash; at worst, abort and
+require restarting.
+</para>
+
+<para>
+<indexterm><primary>caching writes</primary></indexterm>
+<indexterm><primary>caching reads</primary></indexterm>
+<indexterm><primary>oplock break</primary></indexterm>
+If a client session has been caching writes and reads locally due to
+oplocks, it is likely that the data will be lost when the
+application restarts or recovers from the TCP interrupt. When the TCP
+connection drops, the client state is lost. When the file server
+recovers, an oplock break is not sent to the client. In this case, the
+work from the prior session is lost. Observing this scenario with
+oplocks disabled and with the client writing data to the file server
+real-time,  the failover will provide the data on disk as it
+existed at the time of the disconnect.
+</para>
+
+<para>
+In mission-critical, high-availability environments, careful attention
+should be given to oplocks. Ideally, comprehensive
+testing should be done with all affected applications with oplocks
+enabled and disabled.
+</para>
+
+<sect3>
+<title>Exclusively Accessed Shares</title>
+
+<para>
+Oplocks is most effective when it is confined to shares
+that are exclusively accessed by a single user, or by only one user at
+a time. Because the true value of oplocks is the local
+client caching of data, any operation that interrupts the caching
+mechanism will cause a delay.
+</para>
+
+<para>
+Home directories are the most obvious examples of where the performance
+benefit of oplocks can be safely realized.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Multiple-Accessed Shares or Files</title>
+
+<para>
+As each additional user accesses a file in a share with oplocks
+enabled, the potential for delays and resulting perceived poor
+performance increases. When multiple users are accessing a file on a
+share that has oplocks enabled, the management impact of sending and
+receiving oplock breaks and the resulting latency while other clients
+wait for the caching client to flush data offset the performance gains
+of the caching user.
+</para>
+
+<para>
+As each additional client attempts to access a file with oplocks set,
+the potential performance improvement is negated and eventually results
+in a performance bottleneck.
+</para>
+
+</sect3>
+
+<sect3>
+<title>UNIX or NFS Client-Accessed Files</title>
+
+<para>
+<indexterm><primary>NFS clients</primary></indexterm>
+<indexterm><primary>data corruption</primary></indexterm>
+Local UNIX and NFS clients access files without a mandatory
+file-locking mechanism. Thus, these client platforms are incapable of
+initiating an oplock break request from the server to a Windows client
+that has a file cached. Local UNIX or NFS file access can therefore
+write to a file that has been cached by a Windows client, which
+exposes the file to likely data corruption.
+</para>
+
+<para>
+If files are shared between Windows clients and either local UNIX 
+or NFS users, turn oplocks off.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Slow and/or Unreliable Networks</title>
+
+<para>
+<indexterm><primary>performance improvement</primary></indexterm>
+<indexterm><primary>WAN</primary></indexterm>
+<indexterm><primary>latency</primary></indexterm>
+The biggest potential performance improvement for oplocks
+occurs when the client-side caching of reads and writes delivers the
+most differential over sending those reads and writes over the wire.
+This is most likely to occur when the network is extremely slow,
+congested, or distributed (as in a WAN). However, network latency also
+has a high impact on the reliability of the oplock break
+mechanism, and thus increases the likelihood of encountering oplock
+problems that more than offset the potential perceived performance
+gain. Of course, if an oplock break never has to be sent, then this is
+the most advantageous scenario in which to utilize oplocks.
+</para>
+
+<para>
+If the network is slow, unreliable, or a WAN, then do not configure
+oplocks if there is any chance of multiple users
+regularly opening the same file.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Multiuser Databases</title>
+
+<para>
+<indexterm><primary>Multiuser databases</primary></indexterm>
+<indexterm><primary>management bottleneck</primary></indexterm>
+<indexterm><primary>oplocks disabled</primary></indexterm>
+Multiuser databases clearly pose a risk due to their very nature &smbmdash; they are typically heavily
+accessed by numerous users at random intervals. Placing a multiuser database on a share with oplocks enabled
+will likely result in a locking management bottleneck on the Samba server. Whether the database application is
+developed in-house or a commercially available product, ensure that the share has oplocks disabled.
+</para>
+
+</sect3>
+
+<sect3>
+<title>PDM Data Shares</title>
+
+<para>
+<indexterm><primary>PDM</primary></indexterm>
+<indexterm><primary>Process data management</primary></indexterm>
+<indexterm><primary>client-side data caching</primary></indexterm>
+<indexterm><primary>oplocks management</primary></indexterm>
+<indexterm><primary>disabling oplocks</primary></indexterm>
+Process data management (PDM) applications such as IMAN, Enovia, and Clearcase are increasing in usage with
+Windows client platforms and therefore with SMB datastores. PDM applications manage multiuser environments for
+critical data security and access. The typical PDM environment is usually associated with sophisticated client
+design applications that will load data locally as demanded. In addition, the PDM application will usually
+monitor the data state of each client.  In this case, client-side data caching is best left to the local
+application and PDM server to negotiate and maintain. It is appropriate to eliminate the client OS from any
+caching tasks, and the server from any oplocks management, by disabling oplocks on the share.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Beware of Force User</title>
+
+<para>
+<indexterm><primary>oplock break</primary></indexterm>
+Samba includes an &smb.conf; parameter called <smbconfoption name="force user"/> that changes the user
+accessing a share from the incoming user to whatever user is defined by the &smb.conf; variable. If oplocks is
+enabled on a share, the change in user access causes an oplock break to be sent to the client, even if the
+user has not explicitly loaded a file. In cases where the network is slow or unreliable, an oplock break can
+become lost without the user even accessing a file. This can cause apparent performance degradation as the
+client continually reconnects to overcome the lost oplock break.
+</para>
+
+<para>
+Avoid the combination of the following: 
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	<smbconfoption name="force user"/> in the &smb.conf; share configuration.
+	</para></listitem>
+
+	<listitem><para>
+	Slow or unreliable networks.
+	</para></listitem>
+
+	<listitem><para>
+	Oplocks enabled.
+	</para></listitem>
+</itemizedlist>
+
+</sect3>
+
+<sect3>
+<title>Advanced Samba Oplocks Parameters</title>
+
+<para>
+<indexterm><primary>oplock parameters</primary></indexterm>
+<indexterm><primary>oplock mechanism</primary></indexterm>
+<indexterm><primary>implementing oplocks</primary></indexterm>
+Samba provides oplock parameters that allow the
+administrator to adjust various properties of the oplock mechanism to
+account for timing and usage levels. These parameters provide good
+versatility for implementing oplocks in environments where they would
+likely cause problems. The parameters are 
+<smbconfoption name="oplock break wait time"/>, and
+<smbconfoption name="oplock contention limit"/>.
+</para>
+
+<para>
+<indexterm><primary>turn oplocks off</primary></indexterm>
+For most users, administrators, and environments, if these parameters
+are required, then the better option is simply to turn oplocks off.
+The Samba SWAT help text for both parameters reads: <quote>Do not change
+this parameter unless you have read and understood the Samba oplock code.</quote>
+This is good advice.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Mission-Critical, High-Availability</title>
+
+<para>
+In mission-critical, high-availability environments, data integrity is
+often a priority. Complex and expensive configurations are implemented
+to ensure that if a client loses connectivity with a file server, a
+failover replacement will be available immediately to provide
+continuous data availability.
+</para>
+
+<para>
+Windows client failover behavior is more at risk of application
+interruption than other platforms because it is dependent upon an
+established TCP transport connection. If the connection is interrupted
+&smbmdash; as in a file server failover &smbmdash; a new session must be established.
+It is rare for Windows client applications to be coded to recover
+correctly from a transport connection loss; therefore, most applications
+will experience some sort of interruption &smbmdash; at worst, abort and
+require restarting.
+</para>
+
+<para>
+If a client session has been caching writes and reads locally due to
+oplocks, it is likely that the data will be lost when the
+application restarts or recovers from the TCP interrupt. When the TCP
+connection drops, the client state is lost. When the file server
+recovers, an oplock break is not sent to the client. In this case, the
+work from the prior session is lost. Observing this scenario with
+oplocks disabled, if the client was writing data to the file server
+real-time, then the failover will provide the data on disk as it
+existed at the time of the disconnect.
+</para>
+
+<para>
+In mission-critical, high-availability environments, careful attention
+should be given to oplocks. Ideally, comprehensive
+testing should be done with all affected applications with oplocks
+enabled and disabled.
+</para>
+
+</sect3>
+</sect2>
+</sect1>
+
+<sect1>
+<title>Samba Oplocks Control</title>
+
+<para>
+Oplocks is a unique Windows file locking feature. It is
+not really file locking, but is included in most discussions of Windows
+file locking, so is considered a de facto locking feature.
+Oplocks is actually part of the Windows client file
+caching mechanism. It is not a particularly robust or reliable feature
+when implemented on the variety of customized networks that exist in
+enterprise computing.
+</para>
+
+<para>
+Like Windows, Samba implements oplocks as a server-side
+component of the client caching mechanism. Because of the lightweight
+nature of the Windows feature design, effective configuration of
+oplocks requires a good understanding of its limitations,
+and then applying that understanding when configuring data access for
+each particular customized network and client usage state.
+</para>
+
+<para>
+Oplocks essentially means that the client is allowed to download and cache
+a file on its hard drive while making changes; if a second client wants to access the
+file, the first client receives a break and must synchronize the file back to the server.
+This can give significant performance gains in some cases; some programs insist on
+synchronizing the contents of the entire file back to the server for a single change.
+</para>
+
+<para>
+Level1 Oplocks (also known as just plain <quote>oplocks</quote>) is another term for opportunistic locking.
+</para>
+
+<para>
+Level2 Oplocks provides opportunistic locking for a file that will be treated as
+<emphasis>read only</emphasis>. Typically this is used on files that are read-only or
+on files that the client has no initial intention to write to at time of opening the file.
+</para>
+
+<para>
+Kernel Oplocks are essentially a method that allows the Linux kernel to co-exist with
+Samba's oplocked files, although this has provided better integration of MS Windows network
+file locking with the underlying OS. SGI IRIX and Linux are the only two OSs that are
+oplock-aware at this time.
+</para>
+
+<para>
+Unless your system supports kernel oplocks, you should disable oplocks if you are
+accessing the same files from both UNIX/Linux and SMB clients. Regardless, oplocks should
+always be disabled if you are sharing a database file (e.g., Microsoft Access) between
+multiple clients, because any break the first client receives will affect synchronization of
+the entire file (not just the single record), which will result in a noticeable performance
+impairment and, more likely, problems accessing the database in the first place. Notably,
+Microsoft Outlook's personal folders (*.pst) react quite badly to oplocks. If in doubt,
+disable oplocks and tune your system from that point.
+</para>
+
+<para>
+If client-side caching is desirable and reliable on your network, you will benefit from
+turning on oplocks. If your network is slow and/or unreliable, or you are sharing your
+files among other file sharing mechanisms (e.g., NFS) or across a WAN, or multiple people
+will be accessing the same files frequently, you probably will not benefit from the overhead
+of your client sending oplock breaks and will instead want to disable oplocks for the share.
+</para>
+
+<para>
+Another factor to consider is the perceived performance of file access. If oplocks provide no
+measurable speed benefit on your network, it might not be worth the hassle of dealing with them.
+</para>
+
+<sect2>
+<title>Example Configuration</title>
+
+<para>
+In the following section we examine two distinct aspects of Samba locking controls.
+</para>
+
+<sect3>
+<title>Disabling Oplocks</title>
+
+<para>
+You can disable oplocks on a per-share basis with the following:
+</para>
+
+<para>
+<smbconfblock>
+<smbconfsection name="[acctdata]"/>
+<smbconfoption name="oplocks">False</smbconfoption>
+<smbconfoption name="level2 oplocks">False</smbconfoption>
+</smbconfblock>
+</para>
+
+<para>
+The default oplock type is Level1. Level2 oplocks are enabled on a per-share basis
+in the &smb.conf; file.
+</para>
+
+<para>
+Alternately, you could disable oplocks on a per-file basis within the share:
+</para>
+
+<para>
+	<smbconfblock>
+<smbconfoption name="veto oplock files">/*.mdb/*.MDB/*.dbf/*.DBF/</smbconfoption>
+</smbconfblock>
+</para>
+
+<para>
+If you are experiencing problems with oplocks, as apparent from Samba's log entries,
+you may want to play it safe and disable oplocks and Level2 oplocks.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Disabling Kernel Oplocks</title>
+
+<para>
+Kernel oplocks is an &smb.conf; parameter that notifies Samba (if
+the UNIX kernel has the capability to send a Windows client an oplock
+break) when a UNIX process is attempting to open the file that is
+cached. This parameter addresses sharing files between UNIX and
+Windows with oplocks enabled on the Samba server: the UNIX process
+can open the file that is Oplocked (cached) by the Windows client and
+the smbd process will not send an oplock break, which exposes the file
+to the risk of data corruption. If the UNIX kernel has the ability to
+send an oplock break, then the kernel oplocks parameter enables Samba
+to send the oplock break. Kernel oplocks are enabled on a per-server
+basis in the &smb.conf; file.
+</para>
+
+<para>
+<smbconfblock>
+<smbconfoption name="kernel oplocks">yes</smbconfoption>
+</smbconfblock>
+The default is no.
+</para>
+
+<para>
+<emphasis>Veto oplocks</emphasis> is an &smb.conf; parameter that identifies specific files for
+which oplocks are disabled. When a Windows client opens a file that
+has been configured for veto oplocks, the client will not be granted
+the oplock, and all operations will be executed on the original file on
+disk instead of a client-cached file copy. By explicitly identifying
+files that are shared with UNIX processes and disabling oplocks for
+those files, the server-wide oplock configuration can be enabled to
+allow Windows clients to utilize the performance benefit of file
+caching without the risk of data corruption. Veto oplocks can be
+enabled on a per-share basis, or globally for the entire server, in the
+&smb.conf; file as shown in <link linkend="far1"/>.
+</para>
+
+<para>
+<example id="far1">
+<title>Share with Some Files Oplocked</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="veto oplock files">/filename.htm/*.txt/</smbconfoption>
+
+<smbconfsection name="[share_name]"/>
+<smbconfoption name="veto oplock files">/*.exe/filename.ext/</smbconfoption>
+</smbconfblock>
+</example>
+</para>
+
+<para>
+<smbconfoption name="oplock break wait time"/> is an &smb.conf; parameter
+that adjusts the time interval for Samba to reply to an oplock break request. Samba recommends:
+<quote>Do not change this parameter unless you have read and understood the Samba oplock code.</quote>
+Oplock break wait time can only be configured globally in the &smb.conf; file as shown:
+</para>
+
+<para>
+	<smbconfblock>
+<smbconfoption name="oplock break wait time"> 0 (default)</smbconfoption>
+</smbconfblock>
+</para>
+
+<para>
+<emphasis>Oplock break contention limit</emphasis> is an &smb.conf; parameter that limits the
+response of the Samba server to grant an oplock if the configured
+number of contending clients reaches the limit specified by the parameter. Samba recommends
+<quote>Do not change this parameter unless you have read and understood the Samba oplock code.</quote>
+Oplock break contention limit can be enabled on a per-share basis, or globally for
+the entire server, in the &smb.conf; file as shown in <link linkend="far3"/>.
+</para>
+
+<para>
+<example id="far3">
+<title>Configuration with Oplock Break Contention Limit</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="oplock break contention limit"> 2 (default)</smbconfoption>
+
+<smbconfsection name="[share_name]"/>
+<smbconfoption name="oplock break contention limit"> 2 (default)</smbconfoption>
+</smbconfblock>
+</example>
+</para>
+
+</sect3>
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>MS Windows Oplocks and Caching Controls</title>
+
+<para>
+There is a known issue when running applications (like Norton Antivirus) on a Windows 2000/ XP
+workstation computer that can affect any application attempting to access shared database files
+across a network. This is a result of a default setting configured in the Windows 2000/XP
+operating system. When a workstation
+attempts to access shared data files located on another Windows 2000/XP computer,
+the Windows 2000/XP operating system will attempt to increase performance by locking the
+files and caching information locally. When this occurs, the application is unable to
+properly function, which results in an <quote>Access Denied</quote>
+ error message being displayed during network operations.
+</para>
+
+<para>
+All Windows operating systems in the NT family that act as database servers for data files
+(meaning that data files are stored there and accessed by other Windows PCs) may need to
+have oplocks disabled in order to minimize the risk of data file corruption.
+This includes Windows 9x/Me, Windows NT, Windows 200x, and Windows XP.
+<footnote><para>Microsoft has documented this in Knowledge Base article 300216.</para></footnote>
+</para>
+
+<para>
+If you are using a Windows NT family workstation in place of a server, you must also
+disable oplocks on that workstation. For example, if you use a
+PC with the Windows NT Workstation operating system instead of Windows NT Server, and you
+have data files located on it that are accessed from other Windows PCs, you may need to
+disable oplocks on that system.
+</para>
+
+<para>
+The major difference is the location in the Windows registry where the values for disabling
+oplocks are entered. Instead of the LanManServer location, the LanManWorkstation location
+may be used.
+</para>
+
+<para>
+You can verify (change or add, if necessary) this registry value using the Windows
+Registry Editor. When you change this registry value, you will have to reboot the PC
+to ensure that the new setting goes into effect.
+</para>
+
+<para>
+The location of the client registry entry for oplocks has changed in
+Windows 2000 from the earlier location in Microsoft Windows NT.
+</para>
+
+<note><para>
+Windows 2000 will still respect the EnableOplocks registry value used to disable oplocks
+in earlier versions of Windows.
+</para></note>
+
+<para>
+You can also deny the granting of oplocks by changing the following registry entries:
+</para>
+
+<para>
+<programlisting>
+	HKEY_LOCAL_MACHINE\System\
+		CurrentControlSet\Services\MRXSmb\Parameters\
+
+		OplocksDisabled REG_DWORD 0 or 1
+		Default: 0 (not disabled)
+</programlisting>
+</para>
+
+<note><para>
+The OplocksDisabled registry value configures Windows clients to either request or not
+request oplocks on a remote file. To disable oplocks, the value of
+ OplocksDisabled must be set to 1.
+</para></note>
+
+<para>
+<programlisting>
+	HKEY_LOCAL_MACHINE\System\
+		CurrentControlSet\Services\LanmanServer\Parameters
+
+		EnableOplocks REG_DWORD 0 or 1
+		Default: 1 (Enabled by Default)
+
+		EnableOpLockForceClose REG_DWORD 0 or 1
+		Default: 0 (Disabled by Default)
+</programlisting>
+</para>
+
+<note><para>
+The EnableOplocks value configures Windows-based servers (including Workstations sharing
+files) to allow or deny oplocks on local files.
+</para></note>
+
+<para>
+To force closure of open oplocks on close or program exit, EnableOpLockForceClose must be set to 1.
+</para>
+
+<para>
+An illustration of how Level2 oplocks work follows:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Station 1 opens the file requesting oplock.
+	</para></listitem>
+	<listitem><para>
+	Since no other station has the file open, the server grants station 1 exclusive oplock.
+	</para></listitem>
+	<listitem><para>
+	Station 2 opens the file requesting oplock.
+	</para></listitem>
+	<listitem><para>
+	Since station 1 has not yet written to the file, the server asks station 1 to break
+	to Level2 oplock.
+	</para></listitem>
+	<listitem><para>
+	Station 1 complies by flushing locally buffered lock information to the server.
+	</para></listitem>
+	<listitem><para>
+	Station 1 informs the server that it has broken to level2 Oplock (alternately,
+	station 1 could have closed the file).
+	</para></listitem>
+	<listitem><para>
+	The server responds to station 2's open request, granting it Level2 oplock.
+	Other stations can likewise open the file and obtain Level2 oplock.
+	</para></listitem>
+	<listitem><para>
+	Station 2 (or any station that has the file open) sends a write request SMB.
+	The server returns the write response.
+	</para></listitem>
+	<listitem><para>
+	The server asks all stations that have the file open to break to none, meaning no
+	station holds any oplock on the file. Because the workstations can have no cached
+	writes or locks at this point, they need not respond to the break-to-none advisory;
+	all they need do is invalidate locally cashed read-ahead data.
+	</para></listitem>
+</itemizedlist>
+
+<sect2>
+<title>Workstation Service Entries</title>
+
+<para><programlisting>
+	\HKEY_LOCAL_MACHINE\System\
+		CurrentControlSet\Services\LanmanWorkstation\Parameters
+
+	UseOpportunisticLocking   REG_DWORD   0 or 1
+	Default: 1 (true)
+</programlisting></para>
+
+<para>
+This indicates whether the redirector should use oplocks performance
+enhancement. This parameter should be disabled only to isolate problems.
+</para>
+
+</sect2>
+<sect2>
+<title>Server Service Entries</title>
+
+<para><programlisting>
+	\HKEY_LOCAL_MACHINE\System\
+		CurrentControlSet\Services\LanmanServer\Parameters
+
+	EnableOplocks   REG_DWORD   0 or 1
+	Default: 1 (true)
+</programlisting></para>
+
+<para>
+This specifies whether the server allows clients to use oplocks on files. Oplocks are a
+significant performance enhancement, but have the potential to cause lost cached
+data on some networks, particularly WANs.
+</para>
+
+<para><programlisting>
+	MinLinkThroughput   REG_DWORD   0 to infinite bytes per second
+	Default: 0
+</programlisting></para>
+
+<para>
+This specifies the minimum link throughput allowed by the server before it disables
+raw I/O and oplocks for this connection.
+</para>
+
+<para><programlisting>
+	MaxLinkDelay   REG_DWORD   0 to 100,000 seconds
+	Default: 60
+</programlisting></para>
+
+<para>
+This specifies the maximum time allowed for a link delay. If delays exceed this number,
+the server disables raw I/O and oplocks for this connection.
+</para>
+
+<para><programlisting>
+	OplockBreakWait   REG_DWORD   10 to 180 seconds
+	Default: 35
+</programlisting></para>
+
+<para>
+This specifies the time that the server waits for a client to respond to an oplock break
+request. Smaller values can allow detection of crashed clients more quickly but can
+potentially cause loss of cached data.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>Persistent Data Corruption</title>
+
+<para>
+If you have applied all of the settings discussed in this chapter but data corruption problems
+and other symptoms persist, here are some additional things to check out.
+</para>
+
+<para>
+We have credible reports from developers that faulty network hardware, such as a single
+faulty network card, can cause symptoms similar to read caching and data corruption.
+If you see persistent data corruption even after repeated re-indexing, you may have to
+rebuild the data files in question. This involves creating a new data file with the
+same definition as the file to be rebuilt and transferring the data from the old file
+to the new one. There are several known methods for doing this that can be found in
+our knowledge base.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+
+<para>
+In some sites locking problems surface as soon as a server is installed; in other sites
+locking problems may not surface for a long time. Almost without exception, when a locking
+problem does surface, it will cause embarrassment and potential data corruption.
+</para>
+
+<para>
+Over the past few years there have been a number of complaints on the Samba mailing lists
+that have claimed that Samba caused data corruption. Three causes have been identified
+so far:
+</para>
+
+<itemizedlist>
+	<listitem><para>
+	Incorrect configuration of oplocks (incompatible with the application
+	being used). This is a common problem even where MS Windows NT4 or MS Windows
+	200x-based servers were in use. It is imperative that the software application vendors'
+	instructions for configuration of file locking should be followed. If in doubt,
+	disable oplocks on both the server and the client. Disabling of all forms of file
+	caching on the MS Windows client may be necessary also.
+	</para></listitem>
+
+	<listitem><para>
+	Defective network cards, cables, or hubs/switches. This is generally a more
+	prevalent factor with low-cost networking hardware, although occasionally there
+	have also been problems with incompatibilities in more up-market hardware.
+	</para></listitem>
+
+	<listitem><para>
+	There have been some random reports of Samba log files being written over data
+	files. This has been reported by very few sites (about five in the past 3 years)
+	and all attempts to reproduce the problem have failed. The Samba Team has been
+	unable to catch this happening and thus unable to isolate any particular
+	cause. Considering the millions of systems that use Samba, for the sites that have
+	been affected by this as well as for the Samba Team, this is a frustrating and
+	vexing challenge. If you see this type of thing happening, please create a bug
+	report on Samba <ulink url="https://bugzilla.samba.org">Bugzilla</ulink> without delay.
+	Make sure that you give as much information as you possibly can to help isolate the
+	cause and to allow replication of the problem (an essential step in problem isolation and correction).
+	</para></listitem>
+</itemizedlist>
+
+	<sect2>
+	<title>locking.tdb Error Messages</title>
+
+	<para>
+		<quote>
+			We are seeing lots of errors in the Samba logs, like:
+		</quote>
+<programlisting>
+tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic
+ 0x4d6f4b61 at offset=36116
+</programlisting>
+
+		<quote>
+			What do these mean?
+		</quote>
+	</para>
+
+	<para>
+	This error indicates a corrupted tdb. Stop all instances of smbd, delete locking.tdb, and restart smbd.
+	</para>
+
+	</sect2>
+
+	<sect2>
+		<title>Problems Saving Files in MS Office on Windows XP</title>
+
+<indexterm><primary>KB 812937</primary></indexterm>
+		<para>This is a bug in Windows XP. More information can be 
+		found in <ulink url="http://support.microsoft.com/?id=812937">Microsoft Knowledge Base article 812937</ulink></para>.
+
+	</sect2>
+
+	<sect2>
+
+		<title>Long Delays Deleting Files over Network with XP SP1</title>
+		
+		<para><quote>It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied.</quote></para>
+
+<indexterm><primary>KB 811492</primary></indexterm>
+		<para>This is a bug in Windows XP. More information can be found in <ulink url="http://support.microsoft.com/?id=811492">
+				Microsoft Knowledge Base article 811492</ulink></para>.
+	</sect2>
+
+</sect1>
+
+<sect1>
+<title>Additional Reading</title>
+
+<para>
+You may want to check for an updated documentation regarding file and record locking issues on the Microsoft
+<ulink url="http://support.microsoft.com/">Support</ulink> web site. Additionally, search for the word
+<literal>locking</literal> on the Samba <ulink url="http://www.samba.org/">web</ulink> site.
+</para>
+
+<para>
+Section of the Microsoft MSDN Library on opportunistic locking: 
+</para>
+
+<para>
+<indexterm><primary>KB 224992</primary></indexterm>
+Microsoft Knowledge Base, <quote>Maintaining Transactional Integrity with OPLOCKS</quote>,
+Microsoft Corporation, April 1999, <ulink noescape="1" url="http://support.microsoft.com/?id=224992">Microsoft
+KB Article 224992</ulink>.
+</para>
+
+<para>
+<indexterm><primary>KB 296264</primary></indexterm>
+Microsoft Knowledge Base, <quote>Configuring Opportunistic Locking in Windows 2000</quote>,
+Microsoft Corporation, April 2001 <ulink noescape="1" url="http://support.microsoft.com/?id=296264">Microsoft KB Article 296264</ulink>.
+</para>
+
+<para>
+<indexterm><primary>KB 129202</primary></indexterm>
+Microsoft Knowledge Base, <quote>PC Ext: Explanation of Opportunistic Locking on Windows NT</quote>,
+Microsoft Corporation, April 1995 <ulink noescape="1" url="http://support.microsoft.com/?id=129202">Microsoft
+KB Article 129202</ulink>.
+</para>
+
+</sect1>
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-msdfs.xml b/docs-xml/Samba3-HOWTO/TOSHARG-msdfs.xml
new file mode 100644
index 00000000000..528f41d8cb6
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-msdfs.xml
@@ -0,0 +1,176 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="msdfs">
+
+<chapterinfo>
+	<author>
+		<firstname>Shirish</firstname><surname>Kalele</surname>
+		<affiliation>
+			<orgname>Samba Team &amp; Veritas Software</orgname>
+			<address>
+				<email>samba@samba.org</email>
+			</address>
+		</affiliation>
+	</author>
+	&author.jht;
+	
+	<pubdate>12 Jul 2000</pubdate>
+</chapterinfo>
+
+<title>Hosting a Microsoft Distributed File System Tree</title>
+
+<sect1>
+<title>Features and Benefits</title>
+
+	<para>
+<indexterm><primary>distributed file system</primary><see>DFS</see></indexterm>
+<indexterm><primary>physical locations</primary></indexterm>
+<indexterm><primary>higher availability</primary></indexterm>
+<indexterm><primary>load balancing</primary></indexterm>
+<indexterm><primary>logical directories</primary></indexterm>
+	The distributed file system (DFS) provides a means of separating the logical
+	view of files and directories that users see from the actual physical locations
+	of these resources on the network. It allows for higher availability, smoother
+	storage expansion, load balancing, and so on.
+	</para>
+
+	<para>
+<indexterm><primary>DFS</primary></indexterm>
+<indexterm><primary>DFS tree</primary></indexterm>
+<indexterm><primary>DFS-aware</primary></indexterm>
+	For information about DFS, refer to the <ulink
+	url="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp">Microsoft
+	documentation</ulink>.  This document explains how to host a DFS tree on a UNIX machine (for DFS-aware clients
+	to browse) using Samba.
+	</para>
+
+	<para>
+<indexterm><primary>DFS server</primary></indexterm>
+<indexterm><primary>share-level</primary></indexterm>
+<indexterm><primary>DFS junction</primary></indexterm>
+<indexterm><primary>DFS-aware</primary></indexterm>
+	A Samba server can be made a DFS server by setting the global Boolean <smbconfoption name="host msdfs"/>
+	parameter in the &smb.conf; file. You designate a share as a DFS root using the share-level Boolean
+	<smbconfoption name="msdfs root"/> parameter. A DFS root directory on Samba hosts DFS links in the form of
+	symbolic links that point to other servers. For example, a symbolic link
+	<filename>junction-&gt;msdfs:storage1\share1</filename> in the share directory acts as the DFS junction. When
+	DFS-aware clients attempt to access the junction link, they are redirected to the storage location (in this
+	case, <parameter>\\storage1\share1</parameter>).
+	</para>
+
+	<para>
+<indexterm><primary>DFS-aware</primary></indexterm>
+<indexterm><primary>DFS tree</primary></indexterm>
+<indexterm><primary>DFS links</primary></indexterm>
+<indexterm><primary>DFS</primary></indexterm>
+	DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x.
+	<link linkend="dfscfg">The following sample configuration</link> shows how to setup a DFS tree on a Samba server.
+	In the <filename>/export/dfsroot</filename> directory, you set up your DFS links to 
+	other servers on the network.
+<screen>
+&rootprompt;<userinput>cd /export/dfsroot</userinput>
+&rootprompt;<userinput>chown root /export/dfsroot</userinput>
+&rootprompt;<userinput>chmod 755 /export/dfsroot</userinput>
+&rootprompt;<userinput>ln -s msdfs:storageA\\shareA linka</userinput>
+&rootprompt;<userinput>ln -s msdfs:serverB\\share,serverC\\share linkb</userinput>
+</screen>
+</para>
+
+<example id="dfscfg">
+<title>smb.conf with DFS Configured</title>
+<smbconfblock>
+<smbconfsection name="[global]"/>
+<smbconfoption name="netbios name">&example.server.samba;</smbconfoption>
+<smbconfoption name="host msdfs  ">yes</smbconfoption>
+
+<smbconfsection name="[dfs]"/>
+<smbconfoption name="path">/export/dfsroot</smbconfoption>
+<smbconfoption name="msdfs root">yes</smbconfoption>
+</smbconfblock>
+</example>
+
+	<para>
+<indexterm><primary>DFS root</primary></indexterm>
+<indexterm><primary>msdfs links</primary></indexterm>
+<indexterm><primary>symbolic links</primary></indexterm>
+	You should set up the permissions and ownership of the directory acting as the DFS root so that only
+	designated users can create, delete, or modify the msdfs links. Also note that symlink names should be all
+	lowercase. This limitation exists to have Samba avoid trying all the case combinations to get at the link
+	name. Finally, set up the symbolic links to point to the network shares you want and start Samba.
+	</para>
+
+	<para>
+<indexterm><primary>DFS-aware clients</primary></indexterm>
+<indexterm><primary>DFS tree</primary></indexterm>
+	Users on DFS-aware clients can now browse the DFS tree on the Samba server at
+	<constant>\\samba\dfs</constant>. Accessing links linka or linkb (which appear as directories to the client)
+	takes users directly to the appropriate shares on the network.
+	</para>
+
+</sect1>
+
+<sect1>
+<title>Common Errors</title>
+	<itemizedlist>
+		<listitem><para>Windows clients need to be rebooted 
+		if a previously mounted non-DFS share is made a DFS 
+		root, or vice versa. A better way is to introduce a 
+		new share and make it the DFS root.</para>
+		</listitem>
+		
+		<listitem><para>Currently, there's a restriction that msdfs 
+		symlink names should all be lowercase.</para>
+		</listitem>
+		
+		<listitem><para>For security purposes, the directory 
+		acting as the root of the DFS tree should have ownership 
+		and permissions set so only designated users can 
+		modify the symbolic links in the directory.</para>
+		</listitem>
+	</itemizedlist>
+
+	<sect2>
+		<title>MSDFS UNIX Path Is Case-Critical</title>
+
+		<para>
+		A network administrator sent advice to the Samba mailing list
+		after long sessions trying to determine why DFS was not working.
+		His advice is worth noting.
+		</para>
+
+		<para><quote>
+		I spent some time trying to figure out why my particular
+		DFS root wasn't working. I noted in the documentation that
+		the symlink should be in all lowercase. It should be
+		amended that the entire path to the symlink should all be
+		in lowercase as well.
+		</quote></para>
+
+		<para>
+		<quote>For example, I had a share defined as such:</quote>
+		<smbconfblock>
+		<smbconfsection name="[pub]"/>
+		<smbconfoption name="path">/export/home/Shares/public_share</smbconfoption>
+		<smbconfoption name="msdfs root">yes</smbconfoption>
+		</smbconfblock>
+		<quote>and I could not make my Windows 9x/Me (with the dfs client installed) follow this symlink:</quote>
+		<screen>
+		damage1 -> msdfs:damage\test-share
+		</screen>
+		</para>
+
+		<para>
+		<quote>Running a debug level of 10 reveals:</quote>
+		<programlisting>
+		[2003/08/20 11:40:33, 5] msdfs/msdfs.c:is_msdfs_link(176)
+		  is_msdfs_link: /export/home/shares/public_share/* does not exist.
+		</programlisting>
+		<quote>Curious. So I changed the directory name from <constant>.../Shares/...</constant> to
+		<constant>.../shares/...</constant> (along with my service definition) and it worked!</quote>
+		</para>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-preface.xml b/docs-xml/Samba3-HOWTO/TOSHARG-preface.xml
new file mode 100644
index 00000000000..43df53e5232
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-preface.xml
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE book PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<preface id="TOSHpreface">
+<title>Preface</title>
+
+<para>
+The editors wish to thank you for your decision to purchase this book.
+The Official Samba-3 HOWTO and Reference Guide is the result of many years
+of accumulation of information, feedback, tips, hints, and happy solutions.
+</para>
+
+<para>
+Please note that this book is a living document, the contents of which are
+constantly being updated. We encourage you to contribute your tips, techniques,
+helpful hints, and your special insight into the Windows networking world to
+help make the next generation of this book even more valuable to Samba users.
+</para>
+
+<para>
+We have made a concerted effort to document more comprehensively than has been
+done previously the information that may help you to better deploy Samba and to
+gain more contented network users.
+</para>
+
+<para>
+This book provides example configurations, it documents key aspects of Microsoft
+Windows networking, provides in-depth insight into the important configuration of
+Samba-3, and helps to put all of these into a useful framework.
+</para>
+
+<para>
+The most recent electronic versions of this document can be found at
+<ulink noescape="1" url="http://www.samba.org/">http://www.samba.org/</ulink>
+on the <quote>Documentation</quote> page.
+</para>
+
+<para>
+Updates, patches and corrections are most welcome. Please email your contributions
+to any one of the following:
+</para>
+
+<para>
+<simplelist>
+<member><ulink noescape="1" url="mailto:jelmer@samba.org">Jelmer Vernooij (jelmer@samba.org)</ulink></member>
+<member><ulink noescape="1" url="mailto:jht@samba.org">John H. Terpstra (jht@samba.org)</ulink></member>
+<member><ulink noescape="1" url="mailto:jerry@samba.org">Gerald (Jerry) Carter (jerry@samba.org)</ulink></member>
+</simplelist>
+</para>
+
+<para>
+We wish to advise that only original and unencumbered material can be published. Please do not submit
+content that is not your own work unless proof of consent from the copyright holder accompanies your
+submission.
+</para>
+
+  <!-- the conventions used in this book -->
+  <xi:include href="conventions.xml" xmlns:xi="http://www.w3.org/2003/XInclude" />
+
+
+</preface>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml b/docs-xml/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml
new file mode 100644
index 00000000000..aa879aeb0a0
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml
@@ -0,0 +1,871 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<chapter id="upgrading-to-3.0">
+<chapterinfo>
+	&author.jelmer;
+	&author.jht;
+	&author.jerry;
+	<pubdate>August 16, 2007</pubdate>
+</chapterinfo>
+
+<title>Updating and Upgrading Samba</title>
+<para>
+This chapter provides a detailed record of changes made during the 3.x series releases. At this time this
+series consists of the 3.0.x series that is under the GNU GPL version 2 license, and the Samba 3.2.x series
+that is being released under the terms of the GNU GPL version 3 license.
+</para>
+
+<sect1>
+<title>Key Update Requirements</title>
+<para>
+Samba is a fluid product in which there may be significant changes between releases. Some of these changes are
+brought about as a result of changes in the protocols that are used by Microsoft Windows network clients as a
+result of security or functionality updates through official Microsoft patches and updates. Samba must track
+such changes, particularly where they affect the internal operation of Samba itself.
+</para>
+
+<para>
+Please refer to any notes below that make explicit mention of the version of Samba you are using. In general,
+all changes that apply to a new release will apply to follow-on releases also. For example, changes to Samba
+3.0.23 affect all releases up to an including 3.0.25 and later.  Samba 3.2.x was originaly cut from Samba
+3.0.25 before 3.2.0-specific changes were applied. Unless a 3.0.x series feature is specifically revoked, the
+behavior of the 3.2.x series can be expected to follow the earlier pattern.
+</para>
+
+<sect2>
+<title>Upgrading from Samba-3.0.x to Samba-3.2.0</title>
+<para>
+</para>
+</sect2>
+
+<sect2 id="oldupdatenotes">
+<title>Upgrading from Samba-2.x to Samba-3.0.25</title>
+<para>
+<indexterm><primary>Samba differences</primary></indexterm>
+<indexterm><primary>changed parameters</primary></indexterm>
+<indexterm><primary>simple guide</primary></indexterm>
+This chapter deals exclusively with the differences between Samba-3.0.25 and Samba-2.2.8a.
+It points out where configuration parameters have changed, and provides a simple guide for
+the move from 2.2.x to 3.0.25.
+</para>
+</sect2>
+
+<sect2>
+<title>Quick Migration Guide</title>
+
+<para>
+Samba-3.0.25 default behavior should be approximately the same as Samba-2.2.x.
+The default behavior when the new parameter <smbconfoption name="passdb backend"/>
+is not defined in the &smb.conf; file provides the same default behavior as Samba-2.2.x
+with <smbconfoption name="encrypt passwords">Yes</smbconfoption> and
+will use the <filename>smbpasswd</filename> database.
+</para>
+
+<para>
+<indexterm><primary>behavior approximately same</primary></indexterm>
+<indexterm><primary>differing protocol</primary></indexterm>
+So why say that <emphasis>behavior should be approximately the same as Samba-2.2.x</emphasis>? Because
+Samba-3.0.25 can negotiate new protocols, such as support for native Unicode, that may result in
+differing protocol code paths being taken. The new behavior under such circumstances is not
+exactly the same as the old one. The good news is that the domain and machine SIDs will be
+preserved across the upgrade.
+</para>
+
+<para>
+<indexterm><primary>LDAP backend</primary></indexterm>
+<indexterm><primary>database</primary></indexterm>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>Samba-3-compatible LDAP backend</primary></indexterm>
+If the Samba-2.2.x system is using an LDAP backend, and there is no time to update the LDAP
+database, then make sure that <smbconfoption name="passdb backend">ldapsam_compat</smbconfoption>
+is specified in the &smb.conf; file. For the rest, behavior should remain more or less the same.
+At a later date, when there is time to implement a new Samba-3-compatible LDAP backend, it is possible
+to migrate the old LDAP database to the new one through use of the <command>pdbedit</command>.
+See <link linkend="pdbeditthing">The <emphasis>pdbedit</emphasis> Command</link>.
+</para>
+
+</sect2>
+</sect1>
+
+<sect1>
+<title>New Featuers in Samba-3.x Series</title>
+<para>
+</para>
+
+<sect2>
+<title>New Features in Samba-3.2.x Series</title>
+<para>
+</para>
+</sect2>
+
+<sect2>
+<title>New Features in Samba-3.0.x</title>
+
+<para>
+The major new features are:
+</para>
+
+<orderedlist numeration="arabic">
+	<listitem><para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>LDAP/Kerberos</primary></indexterm>
+	Active Directory support. This release is able to join an ADS realm
+	as a member server and authenticate users using LDAP/Kerberos.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>Unicode</primary></indexterm>
+<indexterm><primary>multibyte character sets</primary></indexterm>
+	Unicode support. Samba will now negotiate Unicode on the wire, and
+	internally there is a much better infrastructure for multibyte
+	and Unicode character sets.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>authentication system</primary></indexterm>
+	New authentication system. The internal authentication system has
+	been almost completely rewritten. Most of the changes are internal,
+	but the new authoring system is also very configurable.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>filename mangling</primary></indexterm>
+	New filename mangling system. The filename mangling system has been
+	completely rewritten. An internal database now stores mangling maps
+	persistently.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>net command</primary></indexterm>
+	New <quote>net</quote> command. A new <quote>net</quote> command has been added. It is
+	somewhat similar to the <quote>net</quote> command in Windows. Eventually, we
+	plan to replace a bunch of other utilities (such as smbpasswd)
+	with subcommands in <quote>net</quote>.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>status32 codes</primary></indexterm>
+	Samba now negotiates NT-style status32 codes on the wire. This
+	considerably improves error handling.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>printer attributes publishing</primary></indexterm>
+	Better Windows 200x/XP printing support, including publishing
+	printer attributes in Active Directory.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>RPC modules</primary></indexterm>
+<indexterm><primary>passdb backends</primary></indexterm>
+<indexterm><primary>character sets</primary></indexterm>
+	New loadable RPC modules for passdb backends and character sets.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>dual-daemon winbindd</primary></indexterm>
+	New default dual-daemon winbindd support for better performance.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>migrating</primary></indexterm>
+<indexterm><primary>maintaining ids</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
+	Support for migrating from a Windows NT 4.0 domain to a Samba
+	domain and maintaining user, group, and domain SIDs.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>trust relationships</primary></indexterm>
+<indexterm><primary>domain controllers</primary></indexterm>
+	Support for establishing trust relationships with Windows NT 4.0
+	domain controllers.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>Winbind architecture</primary></indexterm>
+<indexterm><primary>LDAP directory</primary></indexterm>
+<indexterm><primary>ID mapping</primary></indexterm>
+	Initial support for a distributed Winbind architecture using
+	an LDAP directory for storing SID to UID/GID mappings.
+	</para></listitem>
+
+	<listitem><para>
+	Major updates to the Samba documentation tree.
+	</para></listitem>
+
+	<listitem><para>
+<indexterm><primary>SMB signing</primary></indexterm>
+<indexterm><primary>security settings</primary></indexterm>
+	Full support for client and server SMB signing to ensure
+	compatibility with default Windows 2003 security settings.
+	</para></listitem>
+</orderedlist>
+
+<para>
+Plus lots of other improvements!
+</para>
+
+
+<sect3>
+<title>Configuration Parameter Changes</title>
+
+<para>
+This section contains a brief listing of changes to &smb.conf; options since the Samba-2.2.x series up to and
+including Samba-3.0.25.
+</para>
+
+<para>
+Please refer to the smb.conf(5) man page for complete descriptions of new or modified
+parameters.
+</para>
+
+<para>
+Whenever a Samba update or upgrade is performed it is highly recommended to read the file called
+<emphasis>WHATSNEW.txt</emphasis> that is part of the Samba distribution tarball. This file may also
+be obtain on-line from the Samba <ulink url="http://www.samba.org/samba/">web site</ulink>, in
+the right column, under Current Stable Release, by clicking on <emphasis>Release Notes</emphasis>.
+</para>
+
+</sect3>
+
+<sect3>
+<title>Removed Parameters</title>
+
+<indexterm><primary>deleted parameters</primary></indexterm>
+<para>
+In alphabetical order, these are the parameters eliminated from Samba-2.2.x through 3.0.25.
+</para>
+
+<itemizedlist>
+	<listitem><para>admin log</para></listitem>
+	<listitem><para>alternate permissions</para></listitem>
+	<listitem><para>character set</para></listitem>
+	<listitem><para>client codepage</para></listitem>
+	<listitem><para>code page directory</para></listitem>
+	<listitem><para>coding system</para></listitem>
+	<listitem><para>domain admin group</para></listitem>
+	<listitem><para>domain guest group</para></listitem>
+	<listitem><para>enable rid algorithm</para></listitem>
+	<listitem><para>enable svcctl</para></listitem>
+	<listitem><para>force unknown acl user</para></listitem>
+	<listitem><para>hosts equiv</para></listitem>
+	<listitem><para>ldap filter</para></listitem>
+	<listitem><para>min password length</para></listitem>
+	<listitem><para>nt smb support</para></listitem>
+	<listitem><para>post script</para></listitem>
+	<listitem><para>printer admin</para></listitem>
+	<listitem><para>printer driver</para></listitem>
+	<listitem><para>printer driver file</para></listitem>
+	<listitem><para>printer driver location</para></listitem>
+	<listitem><para>read size</para></listitem>
+	<listitem><para>source environment</para></listitem>
+	<listitem><para>status </para></listitem>
+	<listitem><para>strip dot </para></listitem>
+	<listitem><para>total print jobs</para></listitem>
+	<listitem><para>unicode</para></listitem>
+	<listitem><para>use rhosts</para></listitem>
+	<listitem><para>valid chars</para></listitem>
+	<listitem><para>vfs options</para></listitem>
+	<listitem><para>winbind enable local accounts</para></listitem>
+	<listitem><para>winbind max idle children</para></listitem>
+	<listitem><para>wins partners</para></listitem>
+</itemizedlist>
+
+</sect3>
+
+<sect3>
+<title>New Parameters</title>
+
+<para>The following new parameters have been released up to and including Samba 3.0.25 (grouped by function:)</para>
+
+<para>Remote Management</para>
+
+<indexterm><primary>new parameters</primary></indexterm>
+
+<itemizedlist>
+	<listitem><para>abort shutdown script</para></listitem>
+	<listitem><para>shutdown script</para></listitem>
+</itemizedlist>
+
+<para>User and Group Account Management</para>
+
+<itemizedlist>
+	<listitem><para>add group script</para></listitem>
+	<listitem><para>add machine script</para></listitem>
+	<listitem><para>add user to group script</para></listitem>
+	<listitem><para>algorithmic rid base</para></listitem>
+	<listitem><para>delete group script</para></listitem>
+	<listitem><para>delete user from group script</para></listitem>
+	<listitem><para>passdb backend</para></listitem>
+	<listitem><para>rename user script</para></listitem>
+	<listitem><para>set primary group script</para></listitem>
+	<listitem><para>username map script</para></listitem>
+</itemizedlist>
+
+<para>Authentication</para>
+
+<itemizedlist>
+	<listitem><para>auth methods</para></listitem>
+	<listitem><para>ldap password sync</para></listitem>
+	<listitem><para>passdb expand explicit</para></listitem>
+	<listitem><para>realm</para></listitem>
+</itemizedlist>
+
+<para>Protocol Options</para>
+
+<itemizedlist>
+	<listitem><para>add port command</para></listitem>
+	<listitem><para>afs token lifetime</para></listitem>
+	<listitem><para>client lanman auth</para></listitem>
+	<listitem><para>client NTLMv2 auth</para></listitem>
+	<listitem><para>client schannel</para></listitem>
+	<listitem><para>client signing</para></listitem>
+	<listitem><para>client use spnego</para></listitem>
+	<listitem><para>defer sharing violations</para></listitem>
+	<listitem><para>disable netbios</para></listitem>
+	<listitem><para>dmapi support</para></listitem>
+	<listitem><para>enable privileges</para></listitem>
+	<listitem><para>use kerberos keytab</para></listitem>
+	<listitem><para>log nt token command</para></listitem>
+	<listitem><para>ntlm auth</para></listitem>
+	<listitem><para>paranoid server security </para></listitem>
+	<listitem><para>sendfile</para></listitem>
+	<listitem><para>server schannel</para></listitem>
+	<listitem><para>server signing</para></listitem>
+	<listitem><para>smb ports</para></listitem>
+	<listitem><para>svcctl list</para></listitem>
+	<listitem><para>use spnego</para></listitem>
+</itemizedlist>
+
+<para>File Service</para>
+
+<itemizedlist>
+	<listitem><para>allocation roundup size</para></listitem>
+	<listitem><para>acl check permissions</para></listitem>
+	<listitem><para>acl group control</para></listitem>
+	<listitem><para>acl map full control</para></listitem>
+	<listitem><para>aio read size</para></listitem>
+	<listitem><para>aio write size</para></listitem>
+	<listitem><para>dfree cache time</para></listitem>
+	<listitem><para>dfree command</para></listitem>
+	<listitem><para>ea support</para></listitem>
+	<listitem><para>enable asu support</para></listitem>
+	<listitem><para>fam change notify</para></listitem>
+	<listitem><para>force unknown acl user</para></listitem>
+	<listitem><para>get quota command</para></listitem>
+	<listitem><para>hide special files</para></listitem>
+	<listitem><para>hide unwriteable files</para></listitem>
+	<listitem><para>inherit owner</para></listitem>
+	<listitem><para>hostname lookups</para></listitem>
+	<listitem><para>kernel change notify</para></listitem>
+	<listitem><para>mangle prefix</para></listitem>
+	<listitem><para>map acl inherit</para></listitem>
+	<listitem><para>map read only</para></listitem>
+	<listitem><para>max stat cache size</para></listitem>
+	<listitem><para>msdfs proxy</para></listitem>
+	<listitem><para>open files database hash size</para></listitem>
+	<listitem><para>set quota command</para></listitem>
+	<listitem><para>store dos attributes</para></listitem>
+	<listitem><para>use sendfile</para></listitem>
+	<listitem><para>usershare allow guests</para></listitem>
+	<listitem><para>usershare max shares</para></listitem>
+	<listitem><para>usershare owner only</para></listitem>
+	<listitem><para>usershare path</para></listitem>
+	<listitem><para>usershare prefix allow list</para></listitem>
+	<listitem><para>usershare prefix deny list</para></listitem>
+	<listitem><para>usershare template share</para></listitem>
+	<listitem><para>vfs objects</para></listitem>
+</itemizedlist>
+
+<para>Printing</para>
+
+<itemizedlist>
+	<listitem><para>cups options</para></listitem>
+	<listitem><para>cups server</para></listitem>
+	<listitem><para>force printername</para></listitem>
+	<listitem><para>iprint server</para></listitem>
+	<listitem><para>max reported print jobs</para></listitem>
+	<listitem><para>printcap cache time</para></listitem>
+</itemizedlist> 
+
+
+<para>Unicode and Character Sets</para>
+
+<itemizedlist>
+	<listitem><para>display charset</para></listitem>
+	<listitem><para>dos charset</para></listitem>
+	<listitem><para>UNIX charset</para></listitem>
+</itemizedlist>
+
+<para>SID to UID/GID Mappings</para>
+
+<itemizedlist>
+	<listitem><para>idmap backend</para></listitem>
+	<listitem><para>idmap gid</para></listitem>
+	<listitem><para>idmap uid</para></listitem>
+	<listitem><para>username map script</para></listitem>
+	<listitem><para>winbind nss info</para></listitem>
+	<listitem><para>winbind offline logon</para></listitem>
+	<listitem><para>winbind refresh tickets</para></listitem>
+	<listitem><para>winbind trusted domains only</para></listitem>
+	<listitem><para>template primary group</para></listitem>
+</itemizedlist>
+
+<para>LDAP</para>
+
+<itemizedlist>
+	<listitem><para>ldap delete dn</para></listitem>
+	<listitem><para>ldap group suffix</para></listitem>
+	<listitem><para>ldap idmap suffix</para></listitem>
+	<listitem><para>ldap machine suffix</para></listitem>
+	<listitem><para>ldap passwd sync</para></listitem>
+	<listitem><para>ldap replication sleep</para></listitem>
+	<listitem><para>ldap timeout</para></listitem>
+	<listitem><para>ldap user suffix</para></listitem>
+</itemizedlist>
+
+<para>General Configuration</para>
+
+<itemizedlist>
+	<listitem><para>eventlog list</para></listitem>
+	<listitem><para>preload modules</para></listitem>
+	<listitem><para>reset on zero vc</para></listitem>
+	<listitem><para>privatedir</para></listitem>
+</itemizedlist>
+
+</sect3>
+
+<sect3>
+<title>Modified Parameters (Changes in Behavior)</title>
+
+<itemizedlist>
+	<listitem><para>acl group control (new default is No, deprecated parameter)</para></listitem>
+	<listitem><para>change notify timeout (scope changed)</para></listitem>
+	<listitem><para>dos filemode (disabled by default)</para></listitem>
+	<listitem><para>dos filetimes (enabled by default)</para></listitem>
+	<listitem><para>enable asu support (disabled by default)</para></listitem>
+	<listitem><para>enable privileges (enabled by default)</para></listitem>
+	<listitem><para>encrypt passwords (enabled by default) </para></listitem>
+	<listitem><para>host msdfs (enabled by default)</para></listitem>
+	<listitem><para>mangling method (set to hash2 by default) </para></listitem>
+	<listitem><para>map to guest</para></listitem>
+	<listitem><para>only user (deprecated)</para></listitem>
+	<listitem><para>passwd chat</para></listitem>
+	<listitem><para>passwd program</para></listitem>
+	<listitem><para>password server</para></listitem>
+	<listitem><para>restrict anonymous (integer value)</para></listitem>
+	<listitem><para>security (new ads value)</para></listitem>
+	<listitem><para>strict locking (auto by default)</para></listitem>
+	<listitem><para>winbind cache time (increased to 5 minutes)</para></listitem>
+	<listitem><para>winbind enum groups (disabled by default)</para></listitem>
+	<listitem><para>winbind enum users (disabled by default)</para></listitem>
+	<listitem><para>winbind nested groups (enabled by default)</para></listitem>
+	<listitem><para>winbind uid (deprecated in favor of idmap uid)</para></listitem>
+	<listitem><para>winbind gid (deprecated in favor of idmap gid)</para></listitem>
+	<listitem><para>winbindd nss info</para></listitem>
+	<listitem><para>write cache (deprecated)</para></listitem>
+</itemizedlist>
+
+</sect3>
+
+</sect2>
+
+<sect2>
+<title>New Functionality</title>
+
+	<para>
+<indexterm><primary>major changes</primary></indexterm>
+	The major changes in behavior since that Samba-2.2.x series are documented in this section.
+	Please refer to the <filename>WHATSNEW.txt</filename> file that ships with every release of
+	Samba to obtain detailed information regarding the changes that have been made during the
+	life of the current Samba release.
+	</para>
+
+	<sect3>
+	<title>TDB Data Files</title>
+
+<indexterm><primary>tdb data files</primary></indexterm>
+	<para>
+	Refer to <link linkend="install">Installation, Chapter 1</link>, <link linkend="tdbdocs">Chapter 1</link>
+	for information pertaining to the Samba-3 data files, their location and the information that must be
+	preserved across server migrations, updates and upgrades.
+	</para>
+
+	<para>
+<indexterm><primary>tdb file backup</primary></indexterm>
+	Please remember to back up your existing ${lock directory}/*tdb before upgrading to Samba-3. If necessary,
+	Samba will upgrade databases as they are opened. Downgrading from Samba-3 to 2.2, or reversion to an earlier
+	version of Samba-3 from a later release, is an unsupported path.
+	</para>
+
+	<para>
+<indexterm><primary>tdb file descriptions</primary></indexterm>
+	The old Samba-2.2.x tdb files are described in <link linkend="oldtdbfiledesc">the next table</link>.
+	</para>
+
+
+        <table frame='all' id="oldtdbfiledesc"><title>Samba-2.2.x TDB File Descriptions</title>
+        <tgroup cols='3'>
+			<colspec align="left"/>
+			<colspec align="justify" colwidth="1*"/>
+			<colspec align="left"/>
+                <thead>
+                <row>
+                        <entry align="left">Name</entry>
+                        <entry align="justify">Description</entry>
+                        <entry align="center">Backup?</entry>
+                </row>
+                </thead>
+                <tbody>
+                <row>
+                        <entry>account_policy</entry>
+			<entry>User policy settings</entry>
+			<entry>yes</entry>
+		</row>
+		<row>
+			<entry>brlock</entry>
+			<entry>Byte-range file locking information.</entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>connections</entry>
+			<entry><para>Client connection information</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>locking</entry>
+			<entry>Temporary file locking data.</entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>messages</entry>
+			<entry><para>Temporary storage of messages being processed by smbd.</para></entry>
+			<entry>no</entry>
+		</row>
+       <row>
+            <entry>ntdrivers</entry>
+            <entry><para>Stores per-printer driver information.</para></entry>
+			<entry>yes</entry>
+        </row>
+        <row>
+            <entry>ntforms</entry>
+            <entry><para>Stores per-printer forms information.</para></entry>
+			<entry>yes</entry>
+        </row>
+        <row>
+            <entry>ntprinters</entry>
+            <entry><para>Stores the per-printer devmode configuration settings.</para></entry>
+			<entry>yes</entry>
+        </row>
+		<row>
+			<entry>printing/*.tdb</entry>
+			<entry><para>Cached output from lpq command created on a per-print-service basis.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+
+			<entry>registry</entry>
+			<entry><para>Read-only Samba registry skeleton that provides support for
+				exporting various database tables via the winreg RPCs.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>sessionid</entry>
+			<entry><para>Temporary cache for miscellaneous session information.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>share_info</entry>
+			<entry>Share ACL settings.</entry>
+			<entry>yes</entry>
+		</row>
+		<row>
+
+			<entry>unexpected</entry>
+			<entry><para>Packets received for which no process was listening.</para></entry>
+			<entry>no</entry>
+		</row>
+		<row>
+			<entry>winbindd_cache</entry>
+			<entry><para>Cache of identity information received from an NT4 or an ADS domain.</para></entry>
+			<entry>yes</entry>
+		</row>
+		<row>
+			<entry>winbindd_idmap</entry>
+			<entry><para>New ID map table from SIDS to UNIX UIDs/GIDs.</para></entry>
+			<entry>yes</entry>
+		</row>
+		</tbody>
+	</tgroup>
+	</table>
+
+	</sect3>
+
+	<sect3>
+	<title>Changes in Behavior</title>
+
+	<para>
+	The following issues are known changes in behavior between Samba-2.2 and
+	Samba-3 that may affect certain installations of Samba.
+	</para>
+
+	<orderedlist>
+		<listitem><para>
+<indexterm><primary>Windows domain</primary></indexterm>
+<indexterm><primary>getpwnam() call</primary></indexterm>
+<indexterm><primary>NT_STATUS_LOGON_FAILURE</primary></indexterm>
+		When operating as a member of a Windows domain, Samba-2.2 would map any users authenticated by the remote DC
+		to the <quote>guest account</quote> if a UID could not be obtained via the getpwnam() call. Samba-3 rejects
+		the connection with the error message <quote>NT_STATUS_LOGON_FAILURE.</quote> There is no current workaround
+		to re-establish the Samba-2.2 behavior.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>add user script</primary></indexterm>
+<indexterm><primary>add machine script</primary></indexterm>
+		When adding machines to a Samba-2.2 controlled domain, the
+		<quote>add user script</quote> was used to create the UNIX identity of the
+		machine trust account. Samba-3 introduces a new <quote>add machine
+		script</quote> that must be specified for this purpose. Samba-3 will
+		not fall back to using the <quote>add user script</quote> in the absence of
+		an <quote>add machine script</quote>.
+		</para></listitem>
+	</orderedlist>
+
+	</sect3>
+
+	<sect3>
+	<title>Passdb Backends and Authentication</title>
+
+	<para>
+	There have been a few new changes that Samba administrators should be
+	aware of when moving to Samba-3.
+	</para>
+
+	<orderedlist>
+		<listitem><para>
+<indexterm><primary>encrypted passwords</primary></indexterm>
+		Encrypted passwords have been enabled by default in order to
+		interoperate better with out-of-the-box Windows client
+		installations. This does mean that either (a) a Samba account
+		must be created for each user, or (b) <quote>encrypt passwords = no</quote>
+		must be explicitly defined in &smb.conf;.
+		</para></listitem>
+
+		<listitem><para>
+<indexterm><primary>ADS</primary></indexterm>
+<indexterm><primary>Kerberos</primary></indexterm>
+<indexterm><primary>LDAP</primary></indexterm>
+		Inclusion of new <smbconfoption name="security">ads</smbconfoption> option for integration
+		with an Active Directory domain using the native Windows Kerberos 5 and LDAP protocols.
+		</para></listitem>
+	</orderedlist>
+
+	<para>
+<indexterm><primary>account storage backends</primary></indexterm>
+	Samba-3 also includes the possibility of setting up chains of authentication methods (<smbconfoption
+	name="auth methods"/>) and account storage backends (<smbconfoption name="passdb backend"/>).  Please refer to
+	the &smb.conf; man page and <link linkend="passdb">Account Information Databases</link>, for
+	details. While both parameters assume sane default values, it is likely that you will need to understand what
+	the values actually mean in order to ensure Samba operates correctly.
+	</para>
+
+	<para>
+<indexterm><primary>pdbedit</primary></indexterm>
+<indexterm><primary>smbpasswd</primary></indexterm>
+<indexterm><primary>net tool</primary></indexterm>
+	Certain functions of the <command>smbpasswd</command> tool have been split between the
+	new <command>smbpasswd</command> utility, the <command>net</command> tool, and the new <command>pdbedit</command>
+	utility. See the respective man pages for details.
+	</para>
+
+	</sect3>
+
+	<sect3>
+	<title>LDAP</title>
+
+	<para>
+	This section outlines the new features effecting Samba/LDAP integration.
+	</para>
+
+		<sect4>
+		<title>New Schema</title>
+
+		<para>
+<indexterm><primary>object class</primary></indexterm>
+<indexterm><primary>sambaSamAccount</primary></indexterm>
+<indexterm><primary>LDIF</primary></indexterm>
+<indexterm><primary>attributes</primary></indexterm>
+		A new object class (sambaSamAccount) has been introduced to replace
+		the old sambaAccount. This change aids in the renaming of attributes
+		to prevent clashes with attributes from other vendors. There is a
+		conversion script (examples/LDAP/convertSambaAccount) to modify an LDIF
+		file to the new schema.
+		</para>
+
+		<para>
+		Example:
+<indexterm><primary>ldapsearch</primary></indexterm>
+		</para>
+		<para><screen>
+		&prompt;ldapsearch .... -LLL -b "ou=people,dc=..." &gt; old.ldif
+		&prompt;convertSambaAccount --sid &lt;DOM SID&gt; --input old.ldif --output new.ldif
+		</screen></para>
+
+		<para>
+<indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
+		The &lt;DOM SID&gt; can be obtained by running
+<screen>
+&prompt;<userinput>net getlocalsid &lt;DOMAINNAME&gt;</userinput>
+</screen>
+<indexterm><primary>PDC</primary></indexterm>
+		on the Samba PDC as root.
+		</para>
+
+		<para>
+		Under Samba-2.x the domain SID can be obtained by executing:
+<indexterm><primary>smbpasswd</primary></indexterm>
+<screen>
+&prompt;<userinput>smbpasswd -S &lt;DOMAINNAME&gt;</userinput>
+</screen>
+		</para>
+
+		<para>
+<indexterm><primary>old sambaAccount</primary></indexterm>
+<indexterm><primary>ldapsam_compat</primary></indexterm>
+<indexterm><primary>object class declaration</primary></indexterm>
+<indexterm><primary>samba.schema</primary></indexterm>
+		The old <literal>sambaAccount</literal> schema may still be used by specifying the
+		<parameter>ldapsam_compat</parameter> passdb backend. However, the sambaAccount and
+		associated attributes have been moved to the historical section of
+		the schema file and must be uncommented before use if needed.
+		The Samba-2.2 object class declaration for a <literal>sambaAccount</literal> has not changed
+		in the Samba-3 <filename>samba.schema</filename> file.
+		</para>
+
+		<para>
+		Other new object classes and their uses include:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>
+<indexterm><primary>sambaDomain</primary></indexterm>
+<indexterm><primary>domain information</primary></indexterm>
+<indexterm><primary>RID</primary></indexterm>
+<indexterm><primary>ldap suffix</primary></indexterm>
+<indexterm><primary>ldapsam</primary></indexterm>
+<indexterm><primary>idmap</primary></indexterm>
+			<literal>sambaDomain</literal> &smbmdash; domain information used to allocate RIDs
+			for users and groups as necessary. The attributes are added
+			in <quote>ldap suffix</quote> directory entry automatically if
+			an idmap UID/GID range has been set and the <quote>ldapsam</quote>
+			passdb backend has been selected.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>sambaGroupMapping</primary></indexterm>
+<indexterm><primary>ldap group suffix</primary></indexterm>
+<indexterm><primary>net groupmap</primary></indexterm>
+			sambaGroupMapping &smbmdash; an object representing the
+			relationship between a posixGroup and a Windows
+			group/SID. These entries are stored in the <quote>ldap
+			group suffix</quote> and managed by the <quote>net groupmap</quote> command.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>sambaUNIXIdPool</primary></indexterm>
+<indexterm><primary>ldap idmap suffix</primary></indexterm>
+<indexterm><primary>idmap UID</primary></indexterm>
+<indexterm><primary>idmap GID</primary></indexterm>
+			<literal>sambaUNIXIdPool</literal> &smbmdash; created in the <quote>ldap idmap suffix</quote> entry
+			automatically and contains the next available <quote>idmap UID</quote> and
+			<quote>idmap GID</quote>.
+			</para></listitem>
+
+			<listitem><para>
+<indexterm><primary>sambaIdmapEntry</primary></indexterm>
+<indexterm><primary>idmap_ldap module</primary></indexterm>
+			<literal>sambaIdmapEntry</literal> &smbmdash; object storing a mapping between a
+			SID and a UNIX UID/GID. These objects are created by the
+			idmap_ldap module as needed.
+			</para></listitem>
+		</itemizedlist>
+
+		</sect4>
+
+		<sect4>
+		<title>New Suffix for Searching</title>
+
+		<para>
+<indexterm><primary>LDAP queries</primary></indexterm>
+<indexterm><primary>passdb backend</primary></indexterm>
+<indexterm><primary>ldap suffix</primary></indexterm>
+<indexterm><primary>ldap user suffix</primary></indexterm>
+<indexterm><primary>ldap machine suffix</primary></indexterm>
+<indexterm><primary>ldap group suffix</primary></indexterm>
+<indexterm><primary>ldap idmap suffix</primary></indexterm>
+		The following new &smb.conf; parameters have been added to aid in directing
+		certain LDAP queries when <parameter>passdb backend = ldapsam://...</parameter> has been
+		specified.
+		</para>
+
+		<itemizedlist>
+			<listitem><para>ldap suffix         &smbmdash; used to search for user and computer accounts.</para></listitem>
+			<listitem><para>ldap user suffix    &smbmdash; used to store user accounts.</para></listitem>
+			<listitem><para>ldap machine suffix &smbmdash; used to store machine trust accounts.</para></listitem>
+			<listitem><para>ldap group suffix   &smbmdash; location of posixGroup/sambaGroupMapping entries.</para></listitem>
+			<listitem><para>ldap idmap suffix   &smbmdash; location of sambaIdmapEntry objects.</para></listitem>
+		</itemizedlist>
+
+		<para>
+<indexterm><primary>ldap suffix</primary></indexterm>
+<indexterm><primary>subsuffix parameters</primary></indexterm>
+		If an <parameter>ldap suffix</parameter> is defined, it will be appended to all of the
+		remaining subsuffix parameters. In this case, the order of the suffix
+		listings in &smb.conf; is important. Always place the <parameter>ldap suffix</parameter> first
+		in the list.
+		</para>
+
+		<para>
+		Due to a limitation in Samba's &smb.conf; parsing, you should not surround
+		the domain names with quotation marks.
+		</para>
+
+		</sect4>
+
+		<sect4>
+		<title>IdMap LDAP Support</title>
+
+		<para>
+<indexterm><primary>idmap backend</primary></indexterm>
+		Samba-3 supports an LDAP backend for the idmap subsystem. The
+		following options inform Samba that the idmap table should be
+		stored on the directory server <emphasis>onterose</emphasis> in the ou=Idmap,dc=quenya,dc=org partition.
+		</para>
+
+		<smbconfblock>
+		<smbconfsection name="[global]"/>
+		<member>...</member>
+		<smbconfoption name="idmap backend">ldap:ldap://onterose/</smbconfoption>
+		<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
+		<smbconfoption name="idmap uid">40000-50000</smbconfoption>
+		<smbconfoption name="idmap gid">40000-50000</smbconfoption>
+		</smbconfblock>
+
+		<para>
+<indexterm><primary>NFS</primary></indexterm>
+		This configuration allows Winbind installations on multiple servers to
+		share a UID/GID number space, thus avoiding the interoperability problems
+		with NFS that were present in Samba-2.2.
+		</para>
+
+		</sect4>
+
+		</sect3>
+
+	</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba3-HOWTO/conventions.xml b/docs-xml/Samba3-HOWTO/conventions.xml
new file mode 100644
index 00000000000..1b3848405c0
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/conventions.xml
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+  <sect1>
+    <title>Conventions Used</title>
+
+    <para>
+    The following notation conventions are used throughout this book:
+    </para>
+
+    <itemizedlist>
+      <listitem>
+	<para>
+	TOSHARG2 is used as an abbreviation for the book, <quote>The Official Samba-3
+	HOWTO and Reference Guide, Second Edition</quote> Editors: John H. Terpstra and Jelmer R. Vernooij,
+	Publisher: Prentice Hall, ISBN: 0131882228.
+	</para>
+      </listitem>
+
+      <listitem>
+	<para>
+	S3bE2 is used as an abbreviation for the book, <quote>Samba-3 by Example, Second Edition</quote> 
+	Editors: John H. Terpstra, Publisher: Prentice Hall, ISBN: 013188221X.
+	</para>
+      </listitem>
+
+      <listitem>
+        <para>
+	Directories and filenames appear in mono-font. For example,
+        <filename>/etc/pam.conf</filename>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+	Executable names are bolded. For example, <command>smbd</command>.
+	</para>
+      </listitem>
+
+      <listitem>
+        <para>
+	Menu items and buttons appear in bold. For example, click <guibutton>Next</guibutton>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+	Selecting a menu item is indicated as:
+	<menuchoice>
+		<guimenu>Start</guimenu>
+		<guimenuitem>Control Panel</guimenuitem>
+		<guimenuitem>Administrative Tools</guimenuitem>
+		<guimenuitem>Active Directory Users and Computers</guimenuitem>
+	</menuchoice>
+       </para>
+      </listitem>
+    </itemizedlist>
+
+  </sect1>
+
diff --git a/docs-xml/Samba3-HOWTO/gpl-3.0.xml b/docs-xml/Samba3-HOWTO/gpl-3.0.xml
new file mode 100644
index 00000000000..559c89dc4f0
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/gpl-3.0.xml
@@ -0,0 +1,836 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+<appendix>
+  <title>
+    <acronym>GNU</acronym> General Public License version 3
+  </title>
+  <para>
+    Version 3, 29 June 2007
+  </para>
+  <para>
+    Copyright &copy; 2007 Free Software Foundation, Inc.
+    <ulink url="http://fsf.org/">http://fsf.org/</ulink>
+  </para>
+  <para>
+    Everyone is permitted to copy and distribute verbatim copies of this license
+    document, but changing it is not allowed.
+  </para>
+  <bridgehead renderas="sect1">
+    Preamble
+  </bridgehead>
+  <para>
+    The <acronym>GNU</acronym> General Public License is a free, copyleft
+    license for software and other kinds of works.
+  </para>
+  <para>
+    The licenses for most software and other practical works are designed to
+    take away your freedom to share and change the works.  By contrast, the
+    <acronym>GNU</acronym> General Public License is intended to guarantee your
+    freedom to share and change all versions of a program&mdash;to make sure it
+    remains free software for all its users.  We, the Free Software Foundation,
+    use the <acronym>GNU</acronym> General Public License for most of our
+    software; it applies also to any other work released this way by its
+    authors.  You can apply it to your programs, too.
+  </para>
+  <para>
+    When we speak of free software, we are referring to freedom, not price.  Our
+    General Public Licenses are designed to make sure that you have the freedom
+    to distribute copies of free software (and charge for them if you wish),
+    that you receive source code or can get it if you want it, that you can
+    change the software or use pieces of it in new free programs, and that you
+    know you can do these things.
+  </para>
+  <para>
+    To protect your rights, we need to prevent others from denying you these
+    rights or asking you to surrender the rights.  Therefore, you have certain
+    responsibilities if you distribute copies of the software, or if you modify
+    it: responsibilities to respect the freedom of others.
+  </para>
+  <para>
+    For example, if you distribute copies of such a program, whether gratis or
+    for a fee, you must pass on to the recipients the same freedoms that you
+    received.  You must make sure that they, too, receive or can get the source
+    code.  And you must show them these terms so they know their rights.
+  </para>
+  <para>
+    Developers that use the <acronym>GNU</acronym> <acronym>GPL</acronym>
+    protect your rights with two steps: (1) assert copyright on the software,
+    and (2) offer you this License giving you legal permission to copy,
+    distribute and/or modify it.
+  </para>
+  <para>
+    For the developers&rsquo; and authors&rsquo; protection, the
+    <acronym>GPL</acronym> clearly explains that there is no warranty for this
+    free software.  For both users&rsquo; and authors&rsquo; sake, the
+    <acronym>GPL</acronym> requires that modified versions be marked as changed,
+    so that their problems will not be attributed erroneously to authors of
+    previous versions.
+  </para>
+  <para>
+    Some devices are designed to deny users access to install or run modified
+    versions of the software inside them, although the manufacturer can do so.
+    This is fundamentally incompatible with the aim of protecting users&rsquo;
+    freedom to change the software.  The systematic pattern of such abuse occurs
+    in the area of products for individuals to use, which is precisely where it
+    is most unacceptable.  Therefore, we have designed this version of the
+    <acronym>GPL</acronym> to prohibit the practice for those products.  If such
+    problems arise substantially in other domains, we stand ready to extend this
+    provision to those domains in future versions of the <acronym>GPL</acronym>,
+    as needed to protect the freedom of users.
+  </para>
+  <para>
+    Finally, every program is threatened constantly by software patents.  States
+    should not allow patents to restrict development and use of software on
+    general-purpose computers, but in those that do, we wish to avoid the
+    special danger that patents applied to a free program could make it
+    effectively proprietary.  To prevent this, the <acronym>GPL</acronym>
+    assures that patents cannot be used to render the program non-free.
+  </para>
+  <para>
+    The precise terms and conditions for copying, distribution and modification
+    follow.
+  </para>
+  <bridgehead>
+    TERMS AND CONDITIONS
+  </bridgehead>
+  <bridgehead renderas="sect1">
+    0. Definitions.
+  </bridgehead>
+  <para>
+    &ldquo;This License&rdquo; refers to version 3 of the <acronym>GNU</acronym>
+    General Public License.
+  </para>
+  <para>
+    &ldquo;Copyright&rdquo; also means copyright-like laws that apply to other
+    kinds of works, such as semiconductor masks.
+  </para>
+  <para>
+    &ldquo;The Program&rdquo; refers to any copyrightable work licensed under
+    this License.  Each licensee is addressed as &ldquo;you&rdquo;.
+    &ldquo;Licensees&rdquo; and &ldquo;recipients&rdquo; may be individuals or
+    organizations.
+  </para>
+  <para>
+    To &ldquo;modify&rdquo; a work means to copy from or adapt all or part of
+    the work in a fashion requiring copyright permission, other than the making
+    of an exact copy.  The resulting work is called a &ldquo;modified
+    version&rdquo; of the earlier work or a work &ldquo;based on&rdquo; the
+    earlier work.
+  </para>
+  <para>
+    A &ldquo;covered work&rdquo; means either the unmodified Program or a work
+    based on the Program.
+  </para>
+  <para>
+    To &ldquo;propagate&rdquo; a work means to do anything with it that, without
+    permission, would make you directly or secondarily liable for infringement
+    under applicable copyright law, except executing it on a computer or
+    modifying a private copy.  Propagation includes copying, distribution (with
+    or without modification), making available to the public, and in some
+    countries other activities as well.
+  </para>
+  <para>
+    To &ldquo;convey&rdquo; a work means any kind of propagation that enables
+    other parties to make or receive copies.  Mere interaction with a user
+    through a computer network, with no transfer of a copy, is not conveying.
+  </para>
+  <para>
+    An interactive user interface displays &ldquo;Appropriate Legal
+    Notices&rdquo; to the extent that it includes a convenient and prominently
+    visible feature that (1) displays an appropriate copyright notice, and (2)
+    tells the user that there is no warranty for the work (except to the extent
+    that warranties are provided), that licensees may convey the work under this
+    License, and how to view a copy of this License.  If the interface presents
+    a list of user commands or options, such as a menu, a prominent item in the
+    list meets this criterion.
+  </para>
+  <bridgehead renderas="sect1">
+    1. Source Code.
+  </bridgehead>
+  <para>
+    The &ldquo;source code&rdquo; for a work means the preferred form of the
+    work for making modifications to it.  &ldquo;Object code&rdquo; means any
+    non-source form of a work.
+  </para>
+  <para>
+    A &ldquo;Standard Interface&rdquo; means an interface that either is an
+    official standard defined by a recognized standards body, or, in the case of
+    interfaces specified for a particular programming language, one that is
+    widely used among developers working in that language.
+  </para>
+  <para>
+    The &ldquo;System Libraries&rdquo; of an executable work include anything,
+    other than the work as a whole, that (a) is included in the normal form of
+    packaging a Major Component, but which is not part of that Major Component,
+    and (b) serves only to enable use of the work with that Major Component, or
+    to implement a Standard Interface for which an implementation is available
+    to the public in source code form.  A &ldquo;Major Component&rdquo;, in this
+    context, means a major essential component (kernel, window system, and so
+    on) of the specific operating system (if any) on which the executable work
+    runs, or a compiler used to produce the work, or an object code interpreter
+    used to run it.
+  </para>
+  <para>
+    The &ldquo;Corresponding Source&rdquo; for a work in object code form means
+    all the source code needed to generate, install, and (for an executable
+    work) run the object code and to modify the work, including scripts to
+    control those activities.  However, it does not include the work&rsquo;s
+    System Libraries, or general-purpose tools or generally available free
+    programs which are used unmodified in performing those activities but which
+    are not part of the work.  For example, Corresponding Source includes
+    interface definition files associated with source files for the work, and
+    the source code for shared libraries and dynamically linked subprograms that
+    the work is specifically designed to require, such as by intimate data
+    communication or control flow between those subprograms and other parts of
+    the work.
+  </para>
+  <para>
+    The Corresponding Source need not include anything that users can regenerate
+    automatically from other parts of the Corresponding Source.
+  </para>
+  <para>
+    The Corresponding Source for a work in source code form is that same work.
+  </para>
+  <bridgehead renderas="sect1">
+    2. Basic Permissions.
+  </bridgehead>
+  <para>
+    All rights granted under this License are granted for the term of copyright
+    on the Program, and are irrevocable provided the stated conditions are met.
+    This License explicitly affirms your unlimited permission to run the
+    unmodified Program.  The output from running a covered work is covered by
+    this License only if the output, given its content, constitutes a covered
+    work.  This License acknowledges your rights of fair use or other
+    equivalent, as provided by copyright law.
+  </para>
+  <para>
+    You may make, run and propagate covered works that you do not convey,
+    without conditions so long as your license otherwise remains in force.  You
+    may convey covered works to others for the sole purpose of having them make
+    modifications exclusively for you, or provide you with facilities for
+    running those works, provided that you comply with the terms of this License
+    in conveying all material for which you do not control copyright.  Those
+    thus making or running the covered works for you must do so exclusively on
+    your behalf, under your direction and control, on terms that prohibit them
+    from making any copies of your copyrighted material outside their
+    relationship with you.
+  </para>
+  <para>
+    Conveying under any other circumstances is permitted solely under the
+    conditions stated below.  Sublicensing is not allowed; section 10 makes it
+    unnecessary.
+  </para>
+  <bridgehead renderas="sect1">
+    3. Protecting Users&rsquo; Legal Rights From Anti-Circumvention Law.
+  </bridgehead>
+  <para>
+    No covered work shall be deemed part of an effective technological measure
+    under any applicable law fulfilling obligations under article 11 of the WIPO
+    copyright treaty adopted on 20 December 1996, or similar laws prohibiting or
+    restricting circumvention of such measures.
+  </para>
+  <para>
+    When you convey a covered work, you waive any legal power to forbid
+    circumvention of technological measures to the extent such circumvention is
+    effected by exercising rights under this License with respect to the covered
+    work, and you disclaim any intention to limit operation or modification of
+    the work as a means of enforcing, against the work&rsquo;s users, your or
+    third parties&rsquo; legal rights to forbid circumvention of technological
+    measures.
+  </para>
+  <bridgehead renderas="sect1">
+    4. Conveying Verbatim Copies.
+  </bridgehead>
+  <para>
+    You may convey verbatim copies of the Program&rsquo;s source code as you
+    receive it, in any medium, provided that you conspicuously and appropriately
+    publish on each copy an appropriate copyright notice; keep intact all
+    notices stating that this License and any non-permissive terms added in
+    accord with section 7 apply to the code; keep intact all notices of the
+    absence of any warranty; and give all recipients a copy of this License
+    along with the Program.
+  </para>
+  <para>
+    You may charge any price or no price for each copy that you convey, and you
+    may offer support or warranty protection for a fee.
+  </para>
+  <bridgehead renderas="sect1">
+    5. Conveying Modified Source Versions.
+  </bridgehead>
+  <para>
+    You may convey a work based on the Program, or the modifications to produce
+    it from the Program, in the form of source code under the terms of section
+    4, provided that you also meet all of these conditions:
+  </para>
+  <orderedlist numeration="loweralpha">
+    <listitem>
+      <para>
+        The work must carry prominent notices stating that you modified it, and
+        giving a relevant date.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The work must carry prominent notices stating that it is released under
+        this License and any conditions added under section 7.  This requirement
+        modifies the requirement in section 4 to &ldquo;keep intact all
+        notices&rdquo;.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        You must license the entire work, as a whole, under this License to
+        anyone who comes into possession of a copy.  This License will therefore
+        apply, along with any applicable section 7 additional terms, to the
+        whole of the work, and all its parts, regardless of how they are
+        packaged.  This License gives no permission to license the work in any
+        other way, but it does not invalidate such permission if you have
+        separately received it.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        If the work has interactive user interfaces, each must display
+        Appropriate Legal Notices; however, if the Program has interactive
+        interfaces that do not display Appropriate Legal Notices, your work need
+        not make them do so.
+      </para>
+    </listitem>
+  </orderedlist>
+  <para>
+    A compilation of a covered work with other separate and independent works,
+    which are not by their nature extensions of the covered work, and which are
+    not combined with it such as to form a larger program, in or on a volume of
+    a storage or distribution medium, is called an &ldquo;aggregate&rdquo; if
+    the compilation and its resulting copyright are not used to limit the access
+    or legal rights of the compilation&rsquo;s users beyond what the individual works
+    permit.  Inclusion of a covered work in an aggregate does not cause
+    this License to apply to the other parts of the aggregate.
+  </para>
+  <bridgehead renderas="sect1">
+    6. Conveying Non-Source Forms.
+  </bridgehead>
+  <para>
+    You may convey a covered work in object code form under the terms of
+    sections 4 and 5, provided that you also convey the machine-readable
+    Corresponding Source under the terms of this License, in one of these ways:
+  </para>
+  <orderedlist numeration="loweralpha">
+    <listitem>
+      <para>
+        Convey the object code in, or embodied in, a physical product (including
+        a physical distribution medium), accompanied by the Corresponding Source
+        fixed on a durable physical medium customarily used for software
+        interchange.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey the object code in, or embodied in, a physical product (including
+        a physical distribution medium), accompanied by a written offer, valid
+        for at least three years and valid for as long as you offer spare parts
+        or customer support for that product model, to give anyone who possesses
+        the object code either (1) a copy of the Corresponding Source for all
+        the software in the product that is covered by this License, on a
+        durable physical medium customarily used for software interchange, for a
+        price no more than your reasonable cost of physically performing this
+        conveying of source, or (2) access to copy the Corresponding Source from
+        a network server at no charge.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey individual copies of the object code with a copy of the written
+        offer to provide the Corresponding Source.  This alternative is allowed
+        only occasionally and noncommercially, and only if you received the
+        object code with such an offer, in accord with subsection 6b.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey the object code by offering access from a designated place
+        (gratis or for a charge), and offer equivalent access to the
+        Corresponding Source in the same way through the same place at no
+        further charge.  You need not require recipients to copy the
+        Corresponding Source along with the object code.  If the place to copy
+        the object code is a network server, the Corresponding Source may be on
+        a different server (operated by you or a third party) that supports
+        equivalent copying facilities, provided you maintain clear directions
+        next to the object code saying where to find the Corresponding Source.
+        Regardless of what server hosts the Corresponding Source, you remain
+        obligated to ensure that it is available for as long as needed to
+        satisfy these requirements.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey the object code using peer-to-peer transmission, provided you
+        inform other peers where the object code and Corresponding Source of the
+        work are being offered to the general public at no charge under
+        subsection 6d.
+      </para>
+    </listitem>
+  </orderedlist>
+  <para>
+    A separable portion of the object code, whose source code is excluded from
+    the Corresponding Source as a System Library, need not be included in
+    conveying the object code work.
+  </para>
+  <para>
+    A &ldquo;User Product&rdquo; is either (1) a &ldquo;consumer product&rdquo;,
+    which means any tangible personal property which is normally used for
+    personal, family, or household purposes, or (2) anything designed or sold
+    for incorporation into a dwelling.  In determining whether a product is a
+    consumer product, doubtful cases shall be resolved in favor of coverage.
+    For a particular product received by a particular user, &ldquo;normally
+    used&rdquo; refers to a typical or common use of that class of product,
+    regardless of the status of the particular user or of the way in which the
+    particular user actually uses, or expects or is expected to use, the
+    product.  A product is a consumer product regardless of whether the product
+    has substantial commercial, industrial or non-consumer uses, unless such
+    uses represent the only significant mode of use of the product.
+  </para>
+  <para>
+    &ldquo;Installation Information&rdquo; for a User Product means any methods,
+    procedures, authorization keys, or other information required to install and
+    execute modified versions of a covered work in that User Product from a
+    modified version of its Corresponding Source.  The information must suffice
+    to ensure that the continued functioning of the modified object code is in
+    no case prevented or interfered with solely because modification has been
+    made.
+  </para>
+  <para>
+    If you convey an object code work under this section in, or with, or
+    specifically for use in, a User Product, and the conveying occurs as part of
+    a transaction in which the right of possession and use of the User Product
+    is transferred to the recipient in perpetuity or for a fixed term
+    (regardless of how the transaction is characterized), the Corresponding
+    Source conveyed under this section must be accompanied by the Installation
+    Information.  But this requirement does not apply if neither you nor any
+    third party retains the ability to install modified object code on the User
+    Product (for example, the work has been installed in
+    <acronym>ROM</acronym>).
+  </para>
+  <para>
+    The requirement to provide Installation Information does not include a
+    requirement to continue to provide support service, warranty, or updates for
+    a work that has been modified or installed by the recipient, or for the User
+    Product in which it has been modified or installed.  Access to a network may
+    be denied when the modification itself materially and adversely affects the
+    operation of the network or violates the rules and protocols for
+    communication across the network.
+  </para>
+  <para>
+    Corresponding Source conveyed, and Installation Information provided, in
+    accord with this section must be in a format that is publicly documented
+    (and with an implementation available to the public in source code form),
+    and must require no special password or key for unpacking, reading or
+    copying.
+  </para>
+   <bridgehead renderas="sect1">
+     7. Additional Terms.
+   </bridgehead>
+   <para>
+     &ldquo;Additional permissions&rdquo; are terms that supplement the terms of
+     this License by making exceptions from one or more of its conditions.
+     Additional permissions that are applicable to the entire Program shall be
+     treated as though they were included in this License, to the extent that
+     they are valid under applicable law.  If additional permissions apply only
+     to part of the Program, that part may be used separately under those
+     permissions, but the entire Program remains governed by this License
+     without regard to the additional permissions.
+   </para>
+   <para>
+     When you convey a copy of a covered work, you may at your option remove any
+     additional permissions from that copy, or from any part of it.  (Additional
+     permissions may be written to require their own removal in certain cases
+     when you modify the work.)  You may place additional permissions on
+     material, added by you to a covered work, for which you have or can give
+     appropriate copyright permission.
+   </para>
+   <para>
+     Notwithstanding any other provision of this License, for material you add
+     to a covered work, you may (if authorized by the copyright holders of that
+     material) supplement the terms of this License with terms:
+   </para>
+   <orderedlist numeration="loweralpha">
+     <listitem>
+       <para>
+         Disclaiming warranty or limiting liability differently from the terms
+         of sections 15 and 16 of this License; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Requiring preservation of specified reasonable legal notices or author
+         attributions in that material or in the Appropriate Legal Notices
+         displayed by works containing it; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Prohibiting misrepresentation of the origin of that material, or
+         requiring that modified versions of such material be marked in
+         reasonable ways as different from the original version; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Limiting the use for publicity purposes of names of licensors or
+         authors of the material; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Declining to grant rights under trademark law for use of some trade
+         names, trademarks, or service marks; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Requiring indemnification of licensors and authors of that material by
+         anyone who conveys the material (or modified versions of it) with
+         contractual assumptions of liability to the recipient, for any
+         liability that these contractual assumptions directly impose on those
+         licensors and authors.
+       </para>
+     </listitem>
+   </orderedlist>
+   <para>
+     All other non-permissive additional terms are considered &ldquo;further
+     restrictions&rdquo; within the meaning of section 10.  If the Program as
+     you received it, or any part of it, contains a notice stating that it is
+     governed by this License along with a term that is a further restriction,
+     you may remove that term.  If a license document contains a further
+     restriction but permits relicensing or conveying under this License, you
+     may add to a covered work material governed by the terms of that license
+     document, provided that the further restriction does not survive such
+     relicensing or conveying.
+   </para>
+   <para>
+     If you add terms to a covered work in accord with this section, you must
+     place, in the relevant source files, a statement of the additional terms
+     that apply to those files, or a notice indicating where to find the
+     applicable terms.
+   </para>
+   <para>
+     Additional terms, permissive or non-permissive, may be stated in the form
+     of a separately written license, or stated as exceptions; the above
+     requirements apply either way.
+   </para>
+   <bridgehead renderas="sect1">
+     8. Termination.
+   </bridgehead>
+   <para>
+     You may not propagate or modify a covered work except as expressly provided
+     under this License.  Any attempt otherwise to propagate or modify it is
+     void, and will automatically terminate your rights under this License
+     (including any patent licenses granted under the third paragraph of section
+     11).
+   </para>
+   <para>
+     However, if you cease all violation of this License, then your license from
+     a particular copyright holder is reinstated (a) provisionally, unless and
+     until the copyright holder explicitly and finally terminates your license,
+     and (b) permanently, if the copyright holder fails to notify you of the
+     violation by some reasonable means prior to 60 days after the cessation.
+   </para>
+   <para>
+     Moreover, your license from a particular copyright holder is reinstated
+     permanently if the copyright holder notifies you of the violation by some
+     reasonable means, this is the first time you have received notice of
+     violation of this License (for any work) from that copyright holder, and
+     you cure the violation prior to 30 days after your receipt of the notice.
+   </para>
+   <para>
+     Termination of your rights under this section does not terminate the
+     licenses of parties who have received copies or rights from you under this
+     License.  If your rights have been terminated and not permanently
+     reinstated, you do not qualify to receive new licenses for the same
+     material under section 10.
+   </para>
+   <bridgehead renderas="sect1">
+     9. Acceptance Not Required for Having Copies.
+   </bridgehead>
+   <para>
+     You are not required to accept this License in order to receive or run a
+     copy of the Program.  Ancillary propagation of a covered work occurring
+     solely as a consequence of using peer-to-peer transmission to receive a
+     copy likewise does not require acceptance.  However, nothing other than
+     this License grants you permission to propagate or modify any covered work.
+     These actions infringe copyright if you do not accept this License.
+     Therefore, by modifying or propagating a covered work, you indicate your
+     acceptance of this License to do so.
+   </para>
+   <bridgehead renderas="sect1">
+     10. Automatic Licensing of Downstream Recipients.
+   </bridgehead>
+   <para>
+     Each time you convey a covered work, the recipient automatically receives a
+     license from the original licensors, to run, modify and propagate that
+     work, subject to this License.  You are not responsible for enforcing
+     compliance by third parties with this License.
+   </para>
+   <para>
+     An &ldquo;entity transaction&rdquo; is a transaction transferring control
+     of an organization, or substantially all assets of one, or subdividing an
+     organization, or merging organizations.  If propagation of a covered work
+     results from an entity transaction, each party to that transaction who
+     receives a copy of the work also receives whatever licenses to the work the
+     party&rsquo;s predecessor in interest had or could give under the previous
+     paragraph, plus a right to possession of the Corresponding Source of the
+     work from the predecessor in interest, if the predecessor has it or can get
+     it with reasonable efforts.
+   </para>
+   <para>
+     You may not impose any further restrictions on the exercise of the rights
+     granted or affirmed under this License.  For example, you may not impose a
+     license fee, royalty, or other charge for exercise of rights granted under
+     this License, and you may not initiate litigation (including a cross-claim
+     or counterclaim in a lawsuit) alleging that any patent claim is infringed
+     by making, using, selling, offering for sale, or importing the Program or
+     any portion of it.
+   </para>
+  <bridgehead renderas="sect1">
+    11. Patents.
+  </bridgehead>
+  <para>
+    A &ldquo;contributor&rdquo; is a copyright holder who authorizes use under
+    this License of the Program or a work on which the Program is based.  The
+    work thus licensed is called the contributor&rsquo;s &ldquo;contributor
+    version&rdquo;.
+  </para>
+  <para>
+    A contributor&rsquo;s &ldquo;essential patent claims&rdquo; are all patent
+    claims owned or controlled by the contributor, whether already acquired or
+    hereafter acquired, that would be infringed by some manner, permitted by
+    this License, of making, using, or selling its contributor version, but do
+    not include claims that would be infringed only as a consequence of further
+    modification of the contributor version.  For purposes of this definition,
+    &ldquo;control&rdquo; includes the right to grant patent sublicenses in a
+    manner consistent with the requirements of this License.
+  </para>
+  <para>
+    Each contributor grants you a non-exclusive, worldwide, royalty-free patent
+    license under the contributor&rsquo;s essential patent claims, to make, use,
+    sell, offer for sale, import and otherwise run, modify and propagate the
+    contents of its contributor version.
+  </para>
+  <para>
+    In the following three paragraphs, a &ldquo;patent license&rdquo; is any
+    express agreement or commitment, however denominated, not to enforce a
+    patent (such as an express permission to practice a patent or covenant not
+    to sue for patent infringement).  To &ldquo;grant&rdquo; such a patent
+    license to a party means to make such an agreement or commitment not to
+    enforce a patent against the party.
+  </para>
+  <para>
+    If you convey a covered work, knowingly relying on a patent license, and the
+    Corresponding Source of the work is not available for anyone to copy, free
+    of charge and under the terms of this License, through a publicly available
+    network server or other readily accessible means, then you must either (1)
+    cause the Corresponding Source to be so available, or (2) arrange to deprive
+    yourself of the benefit of the patent license for this particular work, or
+    (3) arrange, in a manner consistent with the requirements of this License,
+    to extend the patent license to downstream recipients.  &ldquo;Knowingly
+    relying&rdquo; means you have actual knowledge that, but for the patent
+    license, your conveying the covered work in a country, or your
+    recipient&rsquo;s use of the covered work in a country, would infringe one
+    or more identifiable patents in that country that you have reason to believe
+    are valid.
+  </para>
+  <para>
+    If, pursuant to or in connection with a single transaction or arrangement,
+    you convey, or propagate by procuring conveyance of, a covered work, and
+    grant a patent license to some of the parties receiving the covered work
+    authorizing them to use, propagate, modify or convey a specific copy of the
+    covered work, then the patent license you grant is automatically extended to
+    all recipients of the covered work and works based on it.
+  </para>
+  <para>
+    A patent license is &ldquo;discriminatory&rdquo; if it does not include
+    within the scope of its coverage, prohibits the exercise of, or is
+    conditioned on the non-exercise of one or more of the rights that are
+    specifically granted under this License.  You may not convey a covered work
+    if you are a party to an arrangement with a third party that is in the
+    business of distributing software, under which you make payment to the third
+    party based on the extent of your activity of conveying the work, and under
+    which the third party grants, to any of the parties who would receive the
+    covered work from you, a discriminatory patent license (a) in connection
+    with copies of the covered work conveyed by you (or copies made from those
+    copies), or (b) primarily for and in connection with specific products or
+    compilations that contain the covered work, unless you entered into that
+    arrangement, or that patent license was granted, prior to 28 March 2007.
+  </para>
+  <para>
+    Nothing in this License shall be construed as excluding or limiting any
+    implied license or other defenses to infringement that may otherwise be
+    available to you under applicable patent law.
+  </para>
+  <bridgehead renderas="sect1">
+    12. No Surrender of Others&rsquo; Freedom.
+  </bridgehead>
+  <para>
+    If conditions are imposed on you (whether by court order, agreement or
+    otherwise) that contradict the conditions of this License, they do not
+    excuse you from the conditions of this License.  If you cannot convey a
+    covered work so as to satisfy simultaneously your obligations under this
+    License and any other pertinent obligations, then as a consequence you may
+    not convey it at all.  For example, if you agree to terms that obligate you
+    to collect a royalty for further conveying from those to whom you convey the
+    Program, the only way you could satisfy both those terms and this License
+    would be to refrain entirely from conveying the Program.
+  </para>
+  <bridgehead renderas="sect1">
+    13. Use with the <acronym>GNU</acronym> Affero General Public License.
+  </bridgehead>
+  <para>
+    Notwithstanding any other provision of this License, you have permission to
+    link or combine any covered work with a work licensed under version 3 of the
+    <acronym>GNU</acronym> Affero General Public License into a single combined
+    work, and to convey the resulting work.  The terms of this License will
+    continue to apply to the part which is the covered work, but the special
+    requirements of the <acronym>GNU</acronym> Affero General Public License,
+    section 13, concerning interaction through a network will apply to the
+    combination as such.
+  </para>
+  <bridgehead renderas="sect1">
+    14. Revised Versions of this License.
+  </bridgehead>
+  <para>
+    The Free Software Foundation may publish revised and/or new versions of the
+    <acronym>GNU</acronym> General Public License from time to time.  Such new
+    versions will be similar in spirit to the present version, but may differ in
+    detail to address new problems or concerns.
+  </para>
+  <para>
+    Each version is given a distinguishing version number.  If the Program
+    specifies that a certain numbered version of the <acronym>GNU</acronym>
+    General Public License &ldquo;or any later version&rdquo; applies to it, you
+    have the option of following the terms and conditions either of that
+    numbered version or of any later version published by the Free Software
+    Foundation.  If the Program does not specify a version number of the
+    <acronym>GNU</acronym> General Public License, you may choose any version
+    ever published by the Free Software Foundation.
+  </para>
+  <para>
+    If the Program specifies that a proxy can decide which future versions of
+    the <acronym>GNU</acronym> General Public License can be used, that
+    proxy&rsquo;s public statement of acceptance of a version permanently
+    authorizes you to choose that version for the Program.
+  </para>
+  <para>
+    Later license versions may give you additional or different permissions.
+    However, no additional obligations are imposed on any author or copyright
+    holder as a result of your choosing to follow a later version.
+  </para>
+  <bridgehead renderas="sect1">
+    15. Disclaimer of Warranty.
+  </bridgehead>
+  <para>
+    THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
+    LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+    OTHER PARTIES PROVIDE THE PROGRAM &ldquo;AS IS&rdquo; WITHOUT WARRANTY OF
+    ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+    THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
+    YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
+    NECESSARY SERVICING, REPAIR OR CORRECTION.
+  </para>
+  <bridgehead renderas="sect1">
+    16. Limitation of Liability.
+  </bridgehead>
+  <para>
+    IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
+    ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
+    PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+    GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE
+    OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA
+    OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+    PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+    EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+    SUCH DAMAGES.
+  </para>
+  <bridgehead renderas="sect1">
+    17. Interpretation of Sections 15 and 16.
+  </bridgehead>
+  <para>
+    If the disclaimer of warranty and limitation of liability provided above
+    cannot be given local legal effect according to their terms, reviewing
+    courts shall apply local law that most closely approximates an absolute
+    waiver of all civil liability in connection with the Program, unless a
+    warranty or assumption of liability accompanies a copy of the Program in
+    return for a fee.
+  </para>
+  <bridgehead>
+    END OF TERMS AND CONDITIONS
+  </bridgehead>
+  <bridgehead renderas="sect1">
+    How to Apply These Terms to Your New Programs
+  </bridgehead>
+  <para>
+    If you develop a new program, and you want it to be of the greatest possible
+    use to the public, the best way to achieve this is to make it free software
+    which everyone can redistribute and change under these terms.
+  </para>
+  <para>
+    To do so, attach the following notices to the program.  It is safest to
+    attach them to the start of each source file to most effectively state the
+    exclusion of warranty; and each file should have at least the
+    &ldquo;copyright&rdquo; line and a pointer to where the full notice is
+    found.
+  </para>
+  <screen>
+<replaceable>one line to give the program&rsquo;s name and a brief idea of what it does.</replaceable>
+Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the <acronym>GNU</acronym> General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+<acronym>GNU</acronym> General Public License for more details.
+
+You should have received a copy of the <acronym>GNU</acronym> General Public License
+along with this program.  If not, see <ulink url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
+  </screen>
+  <para>
+    Also add information on how to contact you by electronic and paper mail.
+  </para>
+  <para>
+    If the program does terminal interaction, make it output a short notice like
+    this when it starts in an interactive mode:
+  </para>
+  <screen>
+<replaceable>program</replaceable> Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
+This program comes with ABSOLUTELY NO WARRANTY; for details type &lsquo;<literal>show w</literal>&rsquo;.
+This is free software, and you are welcome to redistribute it
+under certain conditions; type &lsquo;<literal>show c</literal>&rsquo; for details.
+  </screen>
+  <para>
+    The hypothetical commands &lsquo;<literal>show w</literal>&rsquo; and
+    &lsquo;<literal>show c</literal>&rsquo; should show the appropriate parts of
+    the General Public License.  Of course, your program&rsquo;s commands might be
+    different; for a GUI interface, you would use an &ldquo;about box&rdquo;.
+  </para>
+  <para>
+    You should also get your employer (if you work as a programmer) or school,
+    if any, to sign a &ldquo;copyright disclaimer&rdquo; for the program, if
+    necessary.  For more information on this, and how to apply and follow the
+    <acronym>GNU</acronym> <acronym>GPL</acronym>, see <ulink
+    url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
+  </para>
+  <para>
+    The <acronym>GNU</acronym> General Public License does not permit
+    incorporating your program into proprietary programs.  If your program is a
+    subroutine library, you may consider it more useful to permit linking
+    proprietary applications with the library.  If this is what you want to do,
+    use the <acronym>GNU</acronym> Lesser General Public License instead of this
+    License.  But first, please read <ulink
+    url="http://www.gnu.org/philosophy/why-not-lgpl.html">http://www.gnu.org/philosophy/why-not-lgpl.html</ulink>.
+  </para>
+</appendix>
diff --git a/docs-xml/Samba3-HOWTO/hitlist-content b/docs-xml/Samba3-HOWTO/hitlist-content
new file mode 100644
index 00000000000..66f3b1a603c
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/hitlist-content
@@ -0,0 +1,14 @@
+- Broadcast messaging
+- Profile Recovery
+- smbfs/cifsfs
+- Anti-Virus
+- Krb5 TGT usage
+- Static WINS entries
+- Disabling Roaming Profiles
+- BAD SID issues
+- VPN
+- incorporation in apache and squid (ntlm_auth)
+- smbldap-tools
+- kinit issues (you need to have kerberos updated in order to run win2k3, etc)
+- pam_smb and why not to use it
+- quotas
diff --git a/docs-xml/Samba3-HOWTO/images/10small.png b/docs-xml/Samba3-HOWTO/images/10small.png
new file mode 100644
index 00000000000..56a9b0cd67a
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/10small.png
diff --git a/docs-xml/Samba3-HOWTO/images/11small.png b/docs-xml/Samba3-HOWTO/images/11small.png
new file mode 100644
index 00000000000..18f5d9e4dd7
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/11small.png
diff --git a/docs-xml/Samba3-HOWTO/images/12small.png b/docs-xml/Samba3-HOWTO/images/12small.png
new file mode 100644
index 00000000000..5bdf809c1b4
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/12small.png
diff --git a/docs-xml/Samba3-HOWTO/images/13small.png b/docs-xml/Samba3-HOWTO/images/13small.png
new file mode 100644
index 00000000000..536b2fc2c2c
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/13small.png
diff --git a/docs-xml/Samba3-HOWTO/images/14small.png b/docs-xml/Samba3-HOWTO/images/14small.png
new file mode 100644
index 00000000000..89054249c00
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/14small.png
diff --git a/docs-xml/Samba3-HOWTO/images/1small.png b/docs-xml/Samba3-HOWTO/images/1small.png
new file mode 100644
index 00000000000..c4905163c94
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/1small.png
diff --git a/docs-xml/Samba3-HOWTO/images/2small.png b/docs-xml/Samba3-HOWTO/images/2small.png
new file mode 100644
index 00000000000..5fd9071349f
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/2small.png
diff --git a/docs-xml/Samba3-HOWTO/images/3small.png b/docs-xml/Samba3-HOWTO/images/3small.png
new file mode 100644
index 00000000000..22a39bae52e
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/3small.png
diff --git a/docs-xml/Samba3-HOWTO/images/4small.png b/docs-xml/Samba3-HOWTO/images/4small.png
new file mode 100644
index 00000000000..6b7f1b1fd40
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/4small.png
diff --git a/docs-xml/Samba3-HOWTO/images/5small.png b/docs-xml/Samba3-HOWTO/images/5small.png
new file mode 100644
index 00000000000..b23e1fc2c71
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/5small.png
diff --git a/docs-xml/Samba3-HOWTO/images/6small.png b/docs-xml/Samba3-HOWTO/images/6small.png
new file mode 100644
index 00000000000..35a646d8269
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/6small.png
diff --git a/docs-xml/Samba3-HOWTO/images/7small.png b/docs-xml/Samba3-HOWTO/images/7small.png
new file mode 100644
index 00000000000..d182677510a
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/7small.png
diff --git a/docs-xml/Samba3-HOWTO/images/8small.png b/docs-xml/Samba3-HOWTO/images/8small.png
new file mode 100644
index 00000000000..08aca66386b
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/8small.png
diff --git a/docs-xml/Samba3-HOWTO/images/9small.png b/docs-xml/Samba3-HOWTO/images/9small.png
new file mode 100644
index 00000000000..90c2cde3273
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/9small.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME001.png b/docs-xml/Samba3-HOWTO/images/WME001.png
new file mode 100644
index 00000000000..c5db7570bc5
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME001.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME002.png b/docs-xml/Samba3-HOWTO/images/WME002.png
new file mode 100644
index 00000000000..641f2179a0d
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME002.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME003.png b/docs-xml/Samba3-HOWTO/images/WME003.png
new file mode 100644
index 00000000000..073c58eddd4
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME003.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME004.png b/docs-xml/Samba3-HOWTO/images/WME004.png
new file mode 100644
index 00000000000..5053adeeeca
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME004.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME005.png b/docs-xml/Samba3-HOWTO/images/WME005.png
new file mode 100644
index 00000000000..5e4e72e498f
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME005.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME006.png b/docs-xml/Samba3-HOWTO/images/WME006.png
new file mode 100644
index 00000000000..cbd31836962
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME006.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME007.png b/docs-xml/Samba3-HOWTO/images/WME007.png
new file mode 100644
index 00000000000..e0a113b0804
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME007.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME008.png b/docs-xml/Samba3-HOWTO/images/WME008.png
new file mode 100644
index 00000000000..b03a7853b42
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME008.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME009.png b/docs-xml/Samba3-HOWTO/images/WME009.png
new file mode 100644
index 00000000000..f851876ceee
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME009.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME010.png b/docs-xml/Samba3-HOWTO/images/WME010.png
new file mode 100644
index 00000000000..589be02b224
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME010.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME011.png b/docs-xml/Samba3-HOWTO/images/WME011.png
new file mode 100644
index 00000000000..f15399b4a25
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME011.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME012.png b/docs-xml/Samba3-HOWTO/images/WME012.png
new file mode 100644
index 00000000000..d2e46212f62
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME012.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME013.png b/docs-xml/Samba3-HOWTO/images/WME013.png
new file mode 100644
index 00000000000..0f0a70d0624
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME013.png
diff --git a/docs-xml/Samba3-HOWTO/images/WME014.png b/docs-xml/Samba3-HOWTO/images/WME014.png
new file mode 100644
index 00000000000..73f1dde37c0
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WME014.png
diff --git a/docs-xml/Samba3-HOWTO/images/WXPP002.png b/docs-xml/Samba3-HOWTO/images/WXPP002.png
new file mode 100644
index 00000000000..b87001bca41
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WXPP002.png
diff --git a/docs-xml/Samba3-HOWTO/images/WXPP003.png b/docs-xml/Samba3-HOWTO/images/WXPP003.png
new file mode 100644
index 00000000000..a60d6c413a2
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WXPP003.png
diff --git a/docs-xml/Samba3-HOWTO/images/WXPP005.png b/docs-xml/Samba3-HOWTO/images/WXPP005.png
new file mode 100644
index 00000000000..4aa091767bf
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WXPP005.png
diff --git a/docs-xml/Samba3-HOWTO/images/WXPP009.png b/docs-xml/Samba3-HOWTO/images/WXPP009.png
new file mode 100644
index 00000000000..b540e238b80
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WXPP009.png
diff --git a/docs-xml/Samba3-HOWTO/images/WXPP014.png b/docs-xml/Samba3-HOWTO/images/WXPP014.png
new file mode 100644
index 00000000000..f1e02d3ce32
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/WXPP014.png
diff --git a/docs-xml/Samba3-HOWTO/images/a_small.png b/docs-xml/Samba3-HOWTO/images/a_small.png
new file mode 100644
index 00000000000..a6622ef6cf7
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/a_small.png
diff --git a/docs-xml/Samba3-HOWTO/images/access1.svg b/docs-xml/Samba3-HOWTO/images/access1.svg
new file mode 100644
index 00000000000..486686f780f
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/access1.svg
@@ -0,0 +1,308 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="30.1cm"
+   height="13.348cm"
+   viewBox="1.35 1.15 31.45 14.498"
+   id="svg2">
+  <defs
+     id="defs99" />
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="1.4"
+     y="1.2"
+     id="rect4"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="1.4"
+     y="1.2"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3"
+     y="2"
+     id="text8"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">type</text>
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="6.5"
+     y="1.2"
+     id="rect10"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="6.5"
+     y="1.2"
+     id="rect12"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7.8000002"
+     y="2"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">users</text>
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="11.5"
+     y="1.2"
+     id="rect16"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="11.5"
+     y="1.2"
+     id="rect18"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="12.6"
+     y="2"
+     id="text20"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">group</text>
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="16.5"
+     y="1.2"
+     id="rect22"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="16.5"
+     y="1.2"
+     id="rect24"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="17.700001"
+     y="2"
+     id="text26"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">others</text>
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="1.4"
+     y="2.7"
+     id="rect28"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="1.4"
+     y="2.7"
+     id="rect30"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.2"
+     y="3.5"
+     id="text32"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">d l</text>
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="6.5"
+     y="2.7"
+     id="rect34"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="6.5"
+     y="2.7"
+     id="rect36"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7.9000001"
+     y="3.5"
+     id="text38"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">r w x</text>
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="11.5"
+     y="2.7"
+     id="rect40"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="11.5"
+     y="2.7"
+     id="rect42"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="13"
+     y="3.5"
+     id="text44"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">r w x</text>
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="16.5"
+     y="2.7"
+     id="rect46"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4000001"
+     height="1.1"
+     x="16.5"
+     y="2.7"
+     id="rect48"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="17.9"
+     y="3.5"
+     id="text50"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">r w x</text>
+  <text
+     x="22.700001"
+     y="6.0999999"
+     id="text52"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Execute, List files</text>
+  <text
+     x="22.700001"
+     y="6.9000001"
+     id="text54"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Write, Create files</text>
+  <text
+     x="22.700001"
+     y="7.6999998"
+     id="text56"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Read, Read files</text>
+  <text
+     x="22.700001"
+     y="8.5"
+     id="text58"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Execute, List files</text>
+  <text
+     x="22.700001"
+     y="9.3000002"
+     id="text60"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Write, Create files</text>
+  <text
+     x="22.700001"
+     y="10.1"
+     id="text62"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Read, Read files</text>
+  <text
+     x="22.700001"
+     y="10.9"
+     id="text64"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Execute, List files</text>
+  <text
+     x="22.700001"
+     y="11.7"
+     id="text66"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Write, Create files</text>
+  <text
+     x="22.700001"
+     y="12.5"
+     id="text68"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Read, Read files</text>
+  <text
+     x="22.700001"
+     y="13.3"
+     id="text70"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Is a symbolic link</text>
+  <text
+     x="22.700001"
+     y="14.1"
+     id="text72"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Is a directory</text>
+  <line
+     x1="18.700001"
+     y1="3.8"
+     x2="18.700001"
+     y2="6.6999998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="18.700001"
+     y1="6.6999998"
+     x2="22.1"
+     y2="6.6999998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line76"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="18.000,3.800 18.000,3.800 18.000,7.500 22.100,7.500 "
+     id="polyline78"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="14.400,3.700 14.400,3.700 14.400,8.300 22.100,8.300 "
+     id="polyline80"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="13.700,3.800 13.700,3.800 13.700,9.100 22.100,9.100 "
+     id="polyline82"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="13.100,3.800 13.000,3.800 13.000,9.900 22.100,9.900 "
+     id="polyline84"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="9.200,3.800 9.300,3.800 9.300,10.700 22.100,10.700 "
+     id="polyline86"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="8.700,3.800 8.800,3.800 8.800,11.500 22.100,11.500 "
+     id="polyline88"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="8.000,3.800 8.100,3.800 8.100,12.300 22.100,12.300 "
+     id="polyline90"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="3.900,3.800 3.900,3.800 3.900,13.100 22.100,13.100 "
+     id="polyline92"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="3.300,3.800 3.300,3.800 3.300,13.900 22.100,13.900 "
+     id="polyline94"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="19.200,3.800 19.200,3.800 19.200,5.900 22.100,5.900 "
+     id="polyline96"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/browsing1.svg b/docs-xml/Samba3-HOWTO/images/browsing1.svg
new file mode 100644
index 00000000000..181ea218715
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/browsing1.svg
@@ -0,0 +1,2025 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="29.107cm"
+   height="18.84cm"
+   viewBox="-2.808 0.758 26.299 19.598"
+   id="svg2">
+  <defs
+     id="defs689" />
+  <rect
+     width="1.534"
+     height="3.5799999"
+     x="2.007"
+     y="2.0139999"
+     id="rect4"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.534"
+     height="3.5799999"
+     x="2.007"
+     y="2.0139999"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.227"
+     height="0.40900001"
+     x="2.1600001"
+     y="2.2279999"
+     id="rect8"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.227"
+     height="0.40900001"
+     x="2.1600001"
+     y="2.638"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.227"
+     height="0.40900001"
+     x="2.1600001"
+     y="3.0469999"
+     id="rect12"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.227"
+     height="0.40900001"
+     x="2.1600001"
+     y="3.4560001"
+     id="rect14"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76700002"
+     height="0.245"
+     x="2.1600001"
+     y="3.947"
+     id="rect16"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="3.3110001"
+     cy="3.9879999"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse18"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="3.3110001"
+     cy="3.9879999"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse20"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="3.3110001"
+     cy="4.151"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse22"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="3.3110001"
+     cy="4.151"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse24"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="3.0039999"
+     y="4.0279999"
+     id="rect26"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="3.0039999"
+     y="4.0279999"
+     id="rect28"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 2.263,4.519 L 2.263,5.414"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 2.518,4.519 L 2.518,5.414"
+     id="path32"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 2.774,4.519 L 2.774,5.414"
+     id="path34"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 3.03,4.519 L 3.03,5.414"
+     id="path36"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 3.285,4.519 L 3.285,5.414"
+     id="path38"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 3.541,4.519 L 3.541,5.414"
+     id="path40"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="1.7,5.9 2.007,5.286 2.007,5.593 3.541,5.593 3.541,5.286 3.95,5.9 1.7,5.9 "
+     id="polygon42"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="1.7,5.9 2.007,5.286 2.007,5.593 3.541,5.593 3.541,5.286 3.95,5.9 1.7,5.9 "
+     id="polygon44"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.595"
+     height="3.7219999"
+     x="6.119"
+     y="2"
+     id="rect46"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.595"
+     height="3.7219999"
+     x="6.119"
+     y="2"
+     id="rect48"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.276"
+     height="0.42500001"
+     x="6.2789998"
+     y="2.223"
+     id="rect50"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.276"
+     height="0.42500001"
+     x="6.2789998"
+     y="2.6489999"
+     id="rect52"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.276"
+     height="0.42500001"
+     x="6.2789998"
+     y="3.0739999"
+     id="rect54"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.276"
+     height="0.42500001"
+     x="6.2789998"
+     y="3.4990001"
+     id="rect56"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.79799998"
+     height="0.255"
+     x="6.2789998"
+     y="4.0100002"
+     id="rect58"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="7.4749999"
+     cy="4.052"
+     rx="0.056000002"
+     ry="0.056000002"
+     id="ellipse60"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="7.4749999"
+     cy="4.052"
+     rx="0.056000002"
+     ry="0.056000002"
+     id="ellipse62"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="7.4749999"
+     cy="4.223"
+     rx="0.056000002"
+     ry="0.056000002"
+     id="ellipse64"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="7.4749999"
+     cy="4.223"
+     rx="0.056000002"
+     ry="0.056000002"
+     id="ellipse66"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.191"
+     height="0.17"
+     x="7.1560001"
+     y="4.0949998"
+     id="rect68"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.191"
+     height="0.17"
+     x="7.1560001"
+     y="4.0949998"
+     id="rect70"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 6.385,4.605 L 6.385,5.536"
+     id="path72"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 6.651,4.605 L 6.651,5.536"
+     id="path74"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 6.917,4.605 L 6.917,5.536"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 7.182,4.605 L 7.182,5.536"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 7.448,4.605 L 7.448,5.536"
+     id="path80"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 7.714,4.605 L 7.714,5.536"
+     id="path82"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="5.8,6.041 6.119,5.403 6.119,5.722 7.714,5.722 7.714,5.403 8.139,6.041 5.8,6.041 "
+     id="polygon84"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="5.8,6.041 6.119,5.403 6.119,5.722 7.714,5.722 7.714,5.403 8.139,6.041 5.8,6.041 "
+     id="polygon86"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.618"
+     height="3.776"
+     x="10.124"
+     y="1.9"
+     id="rect88"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.618"
+     height="3.776"
+     x="10.124"
+     y="1.9"
+     id="rect90"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.295"
+     height="0.43200001"
+     x="10.286"
+     y="2.1270001"
+     id="rect92"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.295"
+     height="0.43200001"
+     x="10.286"
+     y="2.5580001"
+     id="rect94"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.295"
+     height="0.43200001"
+     x="10.286"
+     y="2.99"
+     id="rect96"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.295"
+     height="0.43200001"
+     x="10.286"
+     y="3.421"
+     id="rect98"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.80900002"
+     height="0.259"
+     x="10.286"
+     y="3.9389999"
+     id="rect100"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="11.499"
+     cy="3.9820001"
+     rx="0.057"
+     ry="0.057"
+     id="ellipse102"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="11.499"
+     cy="3.9820001"
+     rx="0.057"
+     ry="0.057"
+     id="ellipse104"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="11.499"
+     cy="4.1550002"
+     rx="0.057"
+     ry="0.057"
+     id="ellipse106"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="11.499"
+     cy="4.1550002"
+     rx="0.057"
+     ry="0.057"
+     id="ellipse108"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.19400001"
+     height="0.17299999"
+     x="11.176"
+     y="4.026"
+     id="rect110"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.19400001"
+     height="0.17299999"
+     x="11.176"
+     y="4.026"
+     id="rect112"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.393,4.543 L 10.393,5.487"
+     id="path114"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.663,4.543 L 10.663,5.487"
+     id="path116"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.933,4.543 L 10.933,5.487"
+     id="path118"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 11.203,4.543 L 11.203,5.487"
+     id="path120"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 11.472,4.543 L 11.472,5.487"
+     id="path122"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 11.742,4.543 L 11.742,5.487"
+     id="path124"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="9.8,6 10.124,5.353 10.124,5.676 11.742,5.676 11.742,5.353 12.174,6 9.8,6 "
+     id="polygon126"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="9.8,6 10.124,5.353 10.124,5.676 11.742,5.676 11.742,5.353 12.174,6 9.8,6 "
+     id="polygon128"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="2.2"
+     y="1.4"
+     id="text130"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_A</text>
+  <text
+     x="6.1999998"
+     y="1.4"
+     id="text132"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_B</text>
+  <text
+     x="10.1"
+     y="1.3"
+     id="text134"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_C (DMB)</text>
+  <rect
+     width="1.631"
+     height="3.806"
+     x="14.726"
+     y="1.8"
+     id="rect136"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.631"
+     height="3.806"
+     x="14.726"
+     y="1.8"
+     id="rect138"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.3049999"
+     height="0.435"
+     x="14.889"
+     y="2.0280001"
+     id="rect140"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.3049999"
+     height="0.435"
+     x="14.889"
+     y="2.4630001"
+     id="rect142"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.3049999"
+     height="0.435"
+     x="14.889"
+     y="2.898"
+     id="rect144"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.3049999"
+     height="0.435"
+     x="14.889"
+     y="3.3329999"
+     id="rect146"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.815"
+     height="0.26100001"
+     x="14.889"
+     y="3.855"
+     id="rect148"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="16.113001"
+     cy="3.8989999"
+     rx="0.057"
+     ry="0.057"
+     id="ellipse150"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="16.113001"
+     cy="3.8989999"
+     rx="0.057"
+     ry="0.057"
+     id="ellipse152"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="16.113001"
+     cy="4.073"
+     rx="0.057"
+     ry="0.057"
+     id="ellipse154"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="16.113001"
+     cy="4.073"
+     rx="0.057"
+     ry="0.057"
+     id="ellipse156"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.19599999"
+     height="0.17399999"
+     x="15.786"
+     y="3.9419999"
+     id="rect158"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.19599999"
+     height="0.17399999"
+     x="15.786"
+     y="3.9419999"
+     id="rect160"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 14.998,4.464 L 14.998,5.415"
+     id="path162"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 15.27,4.464 L 15.27,5.415"
+     id="path164"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 15.542,4.464 L 15.542,5.415"
+     id="path166"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 15.814,4.464 L 15.814,5.415"
+     id="path168"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 16.085,4.464 L 16.085,5.415"
+     id="path170"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 16.357,4.464 L 16.357,5.415"
+     id="path172"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="14.4,5.932 14.726,5.279 14.726,5.606 16.357,5.606 16.357,5.279 16.792,5.932 14.4,5.932 "
+     id="polygon174"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="14.4,5.932 14.726,5.279 14.726,5.606 16.357,5.606 16.357,5.279 16.792,5.932 14.4,5.932 "
+     id="polygon176"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.9"
+     y1="7.0999999"
+     x2="2.5999999"
+     y2="7.0999999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line178"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="2.825"
+     y1="5.9000001"
+     x2="2.8"
+     y2="7"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line180"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="6.9699998"
+     y1="6.0409999"
+     x2="6.9000001"
+     y2="7"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line182"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="10.987"
+     y1="6"
+     x2="11"
+     y2="7.0999999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line184"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="15.596"
+     y1="5.9320002"
+     x2="15.6"
+     y2="7.0999999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line186"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.645"
+     height="3.839"
+     x="18.929001"
+     y="1.85"
+     id="rect188"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.645"
+     height="3.839"
+     x="18.929001"
+     y="1.85"
+     id="rect190"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.316"
+     height="0.43900001"
+     x="19.094"
+     y="2.0799999"
+     id="rect192"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.316"
+     height="0.43900001"
+     x="19.094"
+     y="2.5190001"
+     id="rect194"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.316"
+     height="0.43900001"
+     x="19.094"
+     y="2.9579999"
+     id="rect196"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.316"
+     height="0.43900001"
+     x="19.094"
+     y="3.3970001"
+     id="rect198"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.82300001"
+     height="0.26300001"
+     x="19.094"
+     y="3.9230001"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="20.327999"
+     cy="3.967"
+     rx="0.057999998"
+     ry="0.057999998"
+     id="ellipse202"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="20.327999"
+     cy="3.967"
+     rx="0.057999998"
+     ry="0.057999998"
+     id="ellipse204"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="20.327999"
+     cy="4.1420002"
+     rx="0.057999998"
+     ry="0.057999998"
+     id="ellipse206"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="20.327999"
+     cy="4.1420002"
+     rx="0.057999998"
+     ry="0.057999998"
+     id="ellipse208"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.197"
+     height="0.176"
+     x="19.999001"
+     y="4.0110002"
+     id="rect210"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.197"
+     height="0.176"
+     x="19.999001"
+     y="4.0110002"
+     id="rect212"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 19.203,4.537 L 19.203,5.497"
+     id="path214"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 19.478,4.537 L 19.478,5.497"
+     id="path216"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 19.752,4.537 L 19.752,5.497"
+     id="path218"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 20.026,4.537 L 20.026,5.497"
+     id="path220"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 20.3,4.537 L 20.3,5.497"
+     id="path222"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 20.574,4.537 L 20.574,5.497"
+     id="path224"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="18.6,6.018 18.929,5.36 18.929,5.689 20.574,5.689 20.574,5.36 21.013,6.018 18.6,6.018 "
+     id="polygon226"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="18.6,6.018 18.929,5.36 18.929,5.689 20.574,5.689 20.574,5.36 21.013,6.018 18.6,6.018 "
+     id="polygon228"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.799999"
+     y1="7.0999999"
+     x2="19.806999"
+     y2="6.0180001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line230"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="14.6"
+     y="1.3"
+     id="text232"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_D</text>
+  <text
+     x="18.9"
+     y="1.3"
+     id="text234"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_E</text>
+  <line
+     x1="2.5999999"
+     y1="7"
+     x2="2.5999999"
+     y2="8.6000004"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line236"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.3499999"
+     height="2.3499999"
+     x="1.4"
+     y="8.6000004"
+     id="rect238"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="2.3499999"
+     height="2.3499999"
+     x="1.4"
+     y="8.6000004"
+     id="rect240"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.3499999"
+     height="2.3499999"
+     x="1.4"
+     y="8.6000004"
+     id="rect242"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 2.72,8.98 C 2.72,10.155 2.955,9.92 1.78,9.92"
+     id="path244"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 2.72,8.98 C 2.72,10.155 2.955,9.92 1.78,9.92"
+     id="path246"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="2.833,9.164 2.716,8.929 2.599,9.164 2.833,9.164 "
+     id="polygon248"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="2.833,9.164 2.716,8.929 2.599,9.164 2.833,9.164 "
+     id="polygon250"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="1.964,9.798 1.729,9.916 1.964,10.034 1.964,9.798 "
+     id="polygon252"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="1.964,9.798 1.729,9.916 1.964,10.034 1.964,9.798 "
+     id="polygon254"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 3.418,9.641 C 2.243,9.641 2.478,9.406 2.478,10.581"
+     id="path256"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 3.418,9.641 C 2.243,9.641 2.478,9.406 2.478,10.581"
+     id="path258"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="3.21,9.752 3.445,9.634 3.21,9.516 3.21,9.752 "
+     id="polygon260"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.21,9.752 3.445,9.634 3.21,9.516 3.21,9.752 "
+     id="polygon262"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="2.34,10.386 2.458,10.621 2.575,10.386 2.34,10.386 "
+     id="polygon264"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="2.34,10.386 2.458,10.621 2.575,10.386 2.34,10.386 "
+     id="polygon266"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="4.5"
+     y="10.1"
+     id="text268"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Router 1</text>
+  <text
+     x="9.8999996"
+     y="8.1000004"
+     id="text270"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Subnet 1</text>
+  <line
+     x1="19.9"
+     y1="7"
+     x2="19.9"
+     y2="8.6999998"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line272"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.4000001"
+     height="2.4000001"
+     x="18.700001"
+     y="8.6999998"
+     id="rect274"
+     style="fill:#9f9f9f;stroke:none;stroke-width:0" />
+  <rect
+     width="2.4000001"
+     height="2.4000001"
+     x="18.700001"
+     y="8.6999998"
+     id="rect276"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.4000001"
+     height="2.4000001"
+     x="18.700001"
+     y="8.6999998"
+     id="rect278"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 20.048,9.088 C 20.048,10.288 20.288,10.048 19.088,10.048"
+     id="path280"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 20.048,9.088 C 20.048,10.288 20.288,10.048 19.088,10.048"
+     id="path282"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="20.164,9.276 20.044,9.036 19.924,9.276 20.164,9.276 "
+     id="polygon284"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="20.164,9.276 20.044,9.036 19.924,9.276 20.164,9.276 "
+     id="polygon286"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="19.276,9.924 19.036,10.044 19.276,10.164 19.276,9.924 "
+     id="polygon288"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.276,9.924 19.036,10.044 19.276,10.164 19.276,9.924 "
+     id="polygon290"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <path
+     d="M 20.761,9.764 C 19.561,9.764 19.801,9.524 19.801,10.724"
+     id="path292"
+     style="fill:none;stroke:#ffffff;stroke-width:0.13" />
+  <path
+     d="M 20.761,9.764 C 19.561,9.764 19.801,9.524 19.801,10.724"
+     id="path294"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <polygon
+     points="20.548,9.876 20.788,9.756 20.548,9.636 20.548,9.876 "
+     id="polygon296"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="20.548,9.876 20.788,9.756 20.548,9.636 20.548,9.876 "
+     id="polygon298"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="19.66,10.524 19.78,10.764 19.9,10.524 19.66,10.524 "
+     id="polygon300"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.66,10.524 19.78,10.764 19.9,10.524 19.66,10.524 "
+     id="polygon302"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="15.5"
+     y="10.1"
+     id="text304"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Router 2</text>
+  <line
+     x1="2.575"
+     y1="10.95"
+     x2="2.5999999"
+     y2="12.4"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line306"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="8"
+     y1="12.4"
+     x2="-1.7"
+     y2="12.4"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line308"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.4000001"
+     y="12"
+     id="text310"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Subnet 2</text>
+  <rect
+     width="1.493"
+     height="3.483"
+     x="7.099"
+     y="13.5"
+     id="rect312"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.493"
+     height="3.483"
+     x="7.099"
+     y="13.5"
+     id="rect314"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.194"
+     height="0.398"
+     x="7.2480001"
+     y="13.709"
+     id="rect316"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.194"
+     height="0.398"
+     x="7.2480001"
+     y="14.107"
+     id="rect318"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.194"
+     height="0.398"
+     x="7.2480001"
+     y="14.505"
+     id="rect320"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.194"
+     height="0.398"
+     x="7.2480001"
+     y="14.903"
+     id="rect322"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.74599999"
+     height="0.23899999"
+     x="7.2480001"
+     y="15.381"
+     id="rect324"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="8.3669996"
+     cy="15.421"
+     rx="0.052000001"
+     ry="0.052000001"
+     id="ellipse326"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="8.3669996"
+     cy="15.421"
+     rx="0.052000001"
+     ry="0.052000001"
+     id="ellipse328"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="8.3669996"
+     cy="15.58"
+     rx="0.052000001"
+     ry="0.052000001"
+     id="ellipse330"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="8.3669996"
+     cy="15.58"
+     rx="0.052000001"
+     ry="0.052000001"
+     id="ellipse332"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17900001"
+     height="0.15899999"
+     x="8.0690002"
+     y="15.461"
+     id="rect334"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17900001"
+     height="0.15899999"
+     x="8.0690002"
+     y="15.461"
+     id="rect336"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 7.347,15.938 L 7.347,16.809"
+     id="path338"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 7.596,15.938 L 7.596,16.809"
+     id="path340"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 7.845,15.938 L 7.845,16.809"
+     id="path342"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 8.094,15.938 L 8.094,16.809"
+     id="path344"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 8.343,15.938 L 8.343,16.809"
+     id="path346"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 8.591,15.938 L 8.591,16.809"
+     id="path348"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="6.8,17.282 7.099,16.685 7.099,16.983 8.591,16.983 8.591,16.685 8.989,17.282 6.8,17.282 "
+     id="polygon350"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="6.8,17.282 7.099,16.685 7.099,16.983 8.591,16.983 8.591,16.685 8.989,17.282 6.8,17.282 "
+     id="polygon352"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="7.895"
+     y1="13.5"
+     x2="7.9000001"
+     y2="12.3"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line354"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.535"
+     height="3.582"
+     x="3.707"
+     y="13.489"
+     id="rect356"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.535"
+     height="3.582"
+     x="3.707"
+     y="13.489"
+     id="rect358"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="3.8599999"
+     y="13.703"
+     id="rect360"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="3.8599999"
+     y="14.113"
+     id="rect362"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="3.8599999"
+     y="14.522"
+     id="rect364"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="3.8599999"
+     y="14.931"
+     id="rect366"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76700002"
+     height="0.24600001"
+     x="3.8599999"
+     y="15.423"
+     id="rect368"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="5.0120001"
+     cy="15.464"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse370"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="5.0120001"
+     cy="15.464"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse372"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="5.0120001"
+     cy="15.627"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse374"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="5.0120001"
+     cy="15.627"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse376"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="4.7049999"
+     y="15.505"
+     id="rect378"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="4.7049999"
+     y="15.505"
+     id="rect380"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 3.963,15.996 L 3.963,16.891"
+     id="path382"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 4.219,15.996 L 4.219,16.891"
+     id="path384"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 4.474,15.996 L 4.474,16.891"
+     id="path386"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 4.73,15.996 L 4.73,16.891"
+     id="path388"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 4.986,15.996 L 4.986,16.891"
+     id="path390"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 5.242,15.996 L 5.242,16.891"
+     id="path392"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="3.4,17.377 3.707,16.763 3.707,17.07 5.242,17.07 5.242,16.763 5.651,17.377 3.4,17.377 "
+     id="polygon394"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="3.4,17.377 3.707,16.763 3.707,17.07 5.242,17.07 5.242,16.763 5.651,17.377 3.4,17.377 "
+     id="polygon396"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.526"
+     y1="13.489"
+     x2="4.5999999"
+     y2="12.4"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line398"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7"
+     y="18.4"
+     id="text400"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N2_D</text>
+  <text
+     x="7"
+     y="19.200001"
+     id="text402"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(WINS)</text>
+  <text
+     x="3.9000001"
+     y="18.4"
+     id="text404"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N2_C</text>
+  <rect
+     width="1.535"
+     height="3.582"
+     x="0.60699999"
+     y="13.5"
+     id="rect406"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.535"
+     height="3.582"
+     x="0.60699999"
+     y="13.5"
+     id="rect408"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="0.75999999"
+     y="13.715"
+     id="rect410"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="0.75999999"
+     y="14.124"
+     id="rect412"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="0.75999999"
+     y="14.534"
+     id="rect414"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="0.75999999"
+     y="14.943"
+     id="rect416"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76700002"
+     height="0.24600001"
+     x="0.75999999"
+     y="15.434"
+     id="rect418"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="1.9119999"
+     cy="15.475"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse420"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="1.9119999"
+     cy="15.475"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse422"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="1.9119999"
+     cy="15.639"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse424"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="1.9119999"
+     cy="15.639"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse426"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="1.605"
+     y="15.516"
+     id="rect428"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="1.605"
+     y="15.516"
+     id="rect430"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 0.863,16.007 L 0.863,16.903"
+     id="path432"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 1.119,16.007 L 1.119,16.903"
+     id="path434"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 1.374,16.007 L 1.374,16.903"
+     id="path436"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 1.63,16.007 L 1.63,16.903"
+     id="path438"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 1.886,16.007 L 1.886,16.903"
+     id="path440"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 2.142,16.007 L 2.142,16.903"
+     id="path442"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="0.3,17.389 0.607,16.775 0.607,17.082 2.142,17.082 2.142,16.775 2.551,17.389 0.3,17.389 "
+     id="polygon444"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="0.3,17.389 0.607,16.775 0.607,17.082 2.142,17.082 2.142,16.775 2.551,17.389 0.3,17.389 "
+     id="polygon446"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.426"
+     y1="13.5"
+     x2="1.5"
+     y2="12.411"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line448"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.80000001"
+     y="18.410999"
+     id="text450"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N2_B</text>
+  <rect
+     width="1.535"
+     height="3.582"
+     x="-2.493"
+     y="13.5"
+     id="rect452"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.535"
+     height="3.582"
+     x="-2.493"
+     y="13.5"
+     id="rect454"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="-2.3399999"
+     y="13.715"
+     id="rect456"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="-2.3399999"
+     y="14.124"
+     id="rect458"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="-2.3399999"
+     y="14.534"
+     id="rect460"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="-2.3399999"
+     y="14.943"
+     id="rect462"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76700002"
+     height="0.24600001"
+     x="-2.3399999"
+     y="15.434"
+     id="rect464"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="-1.188"
+     cy="15.475"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse466"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="-1.188"
+     cy="15.475"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse468"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="-1.188"
+     cy="15.639"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse470"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="-1.188"
+     cy="15.639"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse472"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="-1.495"
+     y="15.516"
+     id="rect474"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="-1.495"
+     y="15.516"
+     id="rect476"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M -2.237,16.007 L -2.237,16.903"
+     id="path478"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M -1.981,16.007 L -1.981,16.903"
+     id="path480"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M -1.726,16.007 L -1.726,16.903"
+     id="path482"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M -1.47,16.007 L -1.47,16.903"
+     id="path484"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M -1.214,16.007 L -1.214,16.903"
+     id="path486"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M -0.958,16.007 L -0.958,16.903"
+     id="path488"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="-2.8,17.389 -2.493,16.775 -2.493,17.082 -0.958,17.082 -0.958,16.775 -0.549,17.389 -2.8,17.389 "
+     id="polygon490"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="-2.8,17.389 -2.493,16.775 -2.493,17.082 -0.958,17.082 -0.958,16.775 -0.549,17.389 -2.8,17.389 "
+     id="polygon492"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="-1.674"
+     y1="13.5"
+     x2="-1.6"
+     y2="12.411"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line494"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="-2.4000001"
+     y="18.4"
+     id="text496"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N2_A</text>
+  <line
+     x1="19.9"
+     y1="11.1"
+     x2="19.9"
+     y2="12.6"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line498"
+     style="stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="25.299999"
+     y1="12.6"
+     x2="15.6"
+     y2="12.6"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line500"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="20.700001"
+     y="12.2"
+     id="text502"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Subnet 3</text>
+  <rect
+     width="1.493"
+     height="3.483"
+     x="24.399"
+     y="13.7"
+     id="rect504"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.493"
+     height="3.483"
+     x="24.399"
+     y="13.7"
+     id="rect506"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.194"
+     height="0.398"
+     x="24.548"
+     y="13.909"
+     id="rect508"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.194"
+     height="0.398"
+     x="24.548"
+     y="14.307"
+     id="rect510"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.194"
+     height="0.398"
+     x="24.548"
+     y="14.705"
+     id="rect512"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.194"
+     height="0.398"
+     x="24.548"
+     y="15.103"
+     id="rect514"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.74599999"
+     height="0.23899999"
+     x="24.548"
+     y="15.581"
+     id="rect516"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="25.667"
+     cy="15.621"
+     rx="0.052000001"
+     ry="0.052000001"
+     id="ellipse518"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="25.667"
+     cy="15.621"
+     rx="0.052000001"
+     ry="0.052000001"
+     id="ellipse520"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="25.667"
+     cy="15.78"
+     rx="0.052000001"
+     ry="0.052000001"
+     id="ellipse522"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="25.667"
+     cy="15.78"
+     rx="0.052000001"
+     ry="0.052000001"
+     id="ellipse524"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.17900001"
+     height="0.15899999"
+     x="25.368999"
+     y="15.661"
+     id="rect526"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.17900001"
+     height="0.15899999"
+     x="25.368999"
+     y="15.661"
+     id="rect528"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 24.647,16.138 L 24.647,17.009"
+     id="path530"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 24.896,16.138 L 24.896,17.009"
+     id="path532"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 25.145,16.138 L 25.145,17.009"
+     id="path534"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 25.394,16.138 L 25.394,17.009"
+     id="path536"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 25.643,16.138 L 25.643,17.009"
+     id="path538"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 25.891,16.138 L 25.891,17.009"
+     id="path540"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="24.1,17.482 24.399,16.885 24.399,17.183 25.891,17.183 25.891,16.885 26.289,17.482 24.1,17.482 "
+     id="polygon542"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="24.1,17.482 24.399,16.885 24.399,17.183 25.891,17.183 25.891,16.885 26.289,17.482 24.1,17.482 "
+     id="polygon544"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="25.195"
+     y1="13.7"
+     x2="25.200001"
+     y2="12.5"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line546"
+     style="stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.535"
+     height="3.582"
+     x="21.007"
+     y="13.689"
+     id="rect548"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.535"
+     height="3.582"
+     x="21.007"
+     y="13.689"
+     id="rect550"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="21.16"
+     y="13.903"
+     id="rect552"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="21.16"
+     y="14.313"
+     id="rect554"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="21.16"
+     y="14.722"
+     id="rect556"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="21.16"
+     y="15.131"
+     id="rect558"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76700002"
+     height="0.24600001"
+     x="21.16"
+     y="15.623"
+     id="rect560"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="22.312"
+     cy="15.664"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse562"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="22.312"
+     cy="15.664"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse564"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="22.312"
+     cy="15.827"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse566"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="22.312"
+     cy="15.827"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse568"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="22.004999"
+     y="15.705"
+     id="rect570"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="22.004999"
+     y="15.705"
+     id="rect572"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 21.263,16.196 L 21.263,17.091"
+     id="path574"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 21.519,16.196 L 21.519,17.091"
+     id="path576"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 21.774,16.196 L 21.774,17.091"
+     id="path578"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 22.03,16.196 L 22.03,17.091"
+     id="path580"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 22.286,16.196 L 22.286,17.091"
+     id="path582"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 22.542,16.196 L 22.542,17.091"
+     id="path584"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="20.7,17.577 21.007,16.963 21.007,17.27 22.542,17.27 22.542,16.963 22.951,17.577 20.7,17.577 "
+     id="polygon586"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="20.7,17.577 21.007,16.963 21.007,17.27 22.542,17.27 22.542,16.963 22.951,17.577 20.7,17.577 "
+     id="polygon588"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.826"
+     y1="13.689"
+     x2="21.9"
+     y2="12.6"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line590"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="24.299999"
+     y="18.6"
+     id="text592"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N3_D</text>
+  <text
+     x="21.200001"
+     y="18.6"
+     id="text594"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N3_C</text>
+  <rect
+     width="1.535"
+     height="3.582"
+     x="17.907"
+     y="13.7"
+     id="rect596"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.535"
+     height="3.582"
+     x="17.907"
+     y="13.7"
+     id="rect598"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="18.059999"
+     y="13.915"
+     id="rect600"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="18.059999"
+     y="14.324"
+     id="rect602"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="18.059999"
+     y="14.734"
+     id="rect604"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="18.059999"
+     y="15.143"
+     id="rect606"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76700002"
+     height="0.24600001"
+     x="18.059999"
+     y="15.634"
+     id="rect608"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="19.212"
+     cy="15.675"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse610"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="19.212"
+     cy="15.675"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse612"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="19.212"
+     cy="15.839"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse614"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="19.212"
+     cy="15.839"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse616"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="18.905001"
+     y="15.716"
+     id="rect618"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="18.905001"
+     y="15.716"
+     id="rect620"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 18.163,16.207 L 18.163,17.103"
+     id="path622"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 18.419,16.207 L 18.419,17.103"
+     id="path624"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 18.674,16.207 L 18.674,17.103"
+     id="path626"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 18.93,16.207 L 18.93,17.103"
+     id="path628"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 19.186,16.207 L 19.186,17.103"
+     id="path630"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 19.442,16.207 L 19.442,17.103"
+     id="path632"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="17.6,17.589 17.907,16.975 17.907,17.282 19.442,17.282 19.442,16.975 19.851,17.589 17.6,17.589 "
+     id="polygon634"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="17.6,17.589 17.907,16.975 17.907,17.282 19.442,17.282 19.442,16.975 19.851,17.589 17.6,17.589 "
+     id="polygon636"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="18.726"
+     y1="13.7"
+     x2="18.799999"
+     y2="12.611"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line638"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="18.1"
+     y="18.611"
+     id="text640"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N3_B</text>
+  <rect
+     width="1.535"
+     height="3.582"
+     x="14.807"
+     y="13.7"
+     id="rect642"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.535"
+     height="3.582"
+     x="14.807"
+     y="13.7"
+     id="rect644"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="14.96"
+     y="13.915"
+     id="rect646"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="14.96"
+     y="14.324"
+     id="rect648"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="14.96"
+     y="14.734"
+     id="rect650"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.228"
+     height="0.40900001"
+     x="14.96"
+     y="15.143"
+     id="rect652"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.76700002"
+     height="0.24600001"
+     x="14.96"
+     y="15.634"
+     id="rect654"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="16.112"
+     cy="15.675"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse656"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="16.112"
+     cy="15.675"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse658"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="16.112"
+     cy="15.839"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse660"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="16.112"
+     cy="15.839"
+     rx="0.054000001"
+     ry="0.054000001"
+     id="ellipse662"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="15.805"
+     y="15.716"
+     id="rect664"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.184"
+     height="0.164"
+     x="15.805"
+     y="15.716"
+     id="rect666"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 15.063,16.207 L 15.063,17.103"
+     id="path668"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 15.319,16.207 L 15.319,17.103"
+     id="path670"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 15.574,16.207 L 15.574,17.103"
+     id="path672"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 15.83,16.207 L 15.83,17.103"
+     id="path674"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 16.086,16.207 L 16.086,17.103"
+     id="path676"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 16.342,16.207 L 16.342,17.103"
+     id="path678"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="14.5,17.589 14.807,16.975 14.807,17.282 16.342,17.282 16.342,16.975 16.751,17.589 14.5,17.589 "
+     id="polygon680"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="14.5,17.589 14.807,16.975 14.807,17.282 16.342,17.282 16.342,16.975 16.751,17.589 14.5,17.589 "
+     id="polygon682"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.626"
+     y1="13.7"
+     x2="15.7"
+     y2="12.611"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line684"
+     style="stroke:#000000;stroke-width:0.1" />
+  <text
+     x="14.9"
+     y="18.6"
+     id="text686"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N3_A</text>
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/cups1.svg b/docs-xml/Samba3-HOWTO/images/cups1.svg
new file mode 100644
index 00000000000..18b7e4f2a6a
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/cups1.svg
@@ -0,0 +1,274 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="27.950001cm"
+   height="23.34cm"
+   viewBox="0.8 0.857 28.75 24.198"
+   id="svg2">
+  <defs
+     id="defs117" />
+  <text
+     x="0.80000001"
+     y="1.4"
+     id="text4"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">CUPS in and of itself has this (general) filter chain (italic letters</text>
+  <text
+     x="0.80000001"
+     y="2.2"
+     id="text6"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">are file-formats or MIME types, other are filters (this is</text>
+  <text
+     x="0.80000001"
+     y="3"
+     id="text8"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):</text>
+  <text
+     x="2.0999999"
+     y="4.9000001"
+     id="text10"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">something-fileformat</text>
+  <polygon
+     points="4.625,5.6 4.625,6.45 4.2,6.45 5.05,7.3 5.9,6.45 5.475,6.45 5.475,5.6 4.625,5.6 "
+     id="polygon12"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.625,5.6 4.625,6.45 4.2,6.45 5.05,7.3 5.9,6.45 5.475,6.45 5.475,5.6 4.625,5.6 "
+     id="polygon14"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.625,5.6 4.625,6.45 4.2,6.45 5.05,7.3 5.9,6.45 5.475,6.45 5.475,5.6 4.625,5.6 "
+     id="polygon16"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="2.0999999"
+     y="11.9"
+     id="text18"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/postscript</text>
+  <polygon
+     points="4.725,12.6 4.725,13.45 4.3,13.45 5.15,14.3 6,13.45 5.575,13.45 5.575,12.6 4.725,12.6 "
+     id="polygon20"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.725,12.6 4.725,13.45 4.3,13.45 5.15,14.3 6,13.45 5.575,13.45 5.575,12.6 4.725,12.6 "
+     id="polygon22"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.725,12.6 4.725,13.45 4.3,13.45 5.15,14.3 6,13.45 5.575,13.45 5.575,12.6 4.725,12.6 "
+     id="polygon24"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="4.625,9 4.625,9.85 4.2,9.85 5.05,10.7 5.9,9.85 5.475,9.85 5.475,9 4.625,9 "
+     id="polygon26"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.625,9 4.625,9.85 4.2,9.85 5.05,10.7 5.9,9.85 5.475,9.85 5.475,9 4.625,9 "
+     id="polygon28"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.625,9 4.625,9.85 4.2,9.85 5.05,10.7 5.9,9.85 5.475,9.85 5.475,9 4.625,9 "
+     id="polygon30"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="2.8"
+     y="8.3000002"
+     id="text32"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">somethingtops</text>
+  <text
+     x="4.0999999"
+     y="15.3"
+     id="text34"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstops</text>
+  <polygon
+     points="4.725,15.8 4.725,16.65 4.3,16.65 5.15,17.5 6,16.65 5.575,16.65 5.575,15.8 4.725,15.8 "
+     id="polygon36"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.725,15.8 4.725,16.65 4.3,16.65 5.15,17.5 6,16.65 5.575,16.65 5.575,15.8 4.725,15.8 "
+     id="polygon38"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.725,15.8 4.725,16.65 4.3,16.65 5.15,17.5 6,16.65 5.575,16.65 5.575,15.8 4.725,15.8 "
+     id="polygon40"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="1.2"
+     y="18.4"
+     id="text42"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-postscript</text>
+  <text
+     x="14.8"
+     y="18.4"
+     id="text44"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstoraster</text>
+  <text
+     x="13.4"
+     y="14.8"
+     id="text46"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-raster</text>
+  <text
+     x="14.2"
+     y="11.2"
+     id="text48"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">rastertosomething</text>
+  <text
+     x="13.3"
+     y="7.6999998"
+     id="text50"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">something-device-specific</text>
+  <text
+     x="25.6"
+     y="7.6999998"
+     id="text52"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">backend</text>
+  <polygon
+     points="11.2,17.625 12.5,17.625 12.5,17.2 13.8,18.05 12.5,18.9 12.5,18.475 11.2,18.475 11.2,17.625 "
+     id="polygon54"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="11.2,17.625 12.5,17.625 12.5,17.2 13.8,18.05 12.5,18.9 12.5,18.475 11.2,18.475 11.2,17.625 "
+     id="polygon56"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="11.2,17.625 12.5,17.625 12.5,17.2 13.8,18.05 12.5,18.9 12.5,18.475 11.2,18.475 11.2,17.625 "
+     id="polygon58"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="16.35,17.5 16.35,16.35 15.9,16.35 16.8,15.2 17.7,16.35 17.25,16.35 17.25,17.5 16.35,17.5 "
+     id="polygon60"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="16.35,17.5 16.35,16.35 15.9,16.35 16.8,15.2 17.7,16.35 17.25,16.35 17.25,17.5 16.35,17.5 "
+     id="polygon62"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="16.35,17.5 16.35,16.35 15.9,16.35 16.8,15.2 17.7,16.35 17.25,16.35 17.25,17.5 16.35,17.5 "
+     id="polygon64"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="16.35,14 16.35,12.85 15.9,12.85 16.8,11.7 17.7,12.85 17.25,12.85 17.25,14 16.35,14 "
+     id="polygon66"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="16.35,14 16.35,12.85 15.9,12.85 16.8,11.7 17.7,12.85 17.25,12.85 17.25,14 16.35,14 "
+     id="polygon68"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="16.35,14 16.35,12.85 15.9,12.85 16.8,11.7 17.7,12.85 17.25,12.85 17.25,14 16.35,14 "
+     id="polygon70"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="16.35,10.3 16.35,9.15 15.9,9.15 16.8,8 17.7,9.15 17.25,9.15 17.25,10.3 16.35,10.3 "
+     id="polygon72"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="16.35,10.3 16.35,9.15 15.9,9.15 16.8,8 17.7,9.15 17.25,9.15 17.25,10.3 16.35,10.3 "
+     id="polygon74"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="16.35,10.3 16.35,9.15 15.9,9.15 16.8,8 17.7,9.15 17.25,9.15 17.25,10.3 16.35,10.3 "
+     id="polygon76"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="21.9,7.025 23.2,7.025 23.2,6.6 24.5,7.45 23.2,8.3 23.2,7.875 21.9,7.875 21.9,7.025 "
+     id="polygon78"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="21.9,7.025 23.2,7.025 23.2,6.6 24.5,7.45 23.2,8.3 23.2,7.875 21.9,7.875 21.9,7.025 "
+     id="polygon80"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="21.9,7.025 23.2,7.025 23.2,6.6 24.5,7.45 23.2,8.3 23.2,7.875 21.9,7.875 21.9,7.025 "
+     id="polygon82"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="8.1000004"
+     height="2.7"
+     x="20.200001"
+     y="10"
+     id="rect84"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="8.1000004"
+     height="2.7"
+     x="20.200001"
+     y="10"
+     id="rect86"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="20.5"
+     y="10.7"
+     id="text88"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">e.g. Gimp-Print filters</text>
+  <text
+     x="20.5"
+     y="11.5"
+     id="text90"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">may be plugged in here</text>
+  <text
+     x="20.5"
+     y="12.3"
+     id="text92"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(= &quot;raster driver&quot;)</text>
+  <text
+     x="1.5"
+     y="20.700001"
+     id="text94"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">ESP PrintPro has some enhanced &quot;rastertosomething&quot; filters as compared to</text>
+  <text
+     x="1.5"
+     y="21.5"
+     id="text96"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">CUPS, and also a somewhat improved &quot;pstoraster&quot; filter.</text>
+  <text
+     x="1.6"
+     y="23"
+     id="text98"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to</text>
+  <text
+     x="1.6"
+     y="23.799999"
+     id="text100"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">CUPS and ESP PrintPro plug-in where rastertosomething is noted.</text>
+  <rect
+     width="10.1"
+     height="4.4000001"
+     x="18.6"
+     y="15.5"
+     id="rect102"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="10.1"
+     height="4.4000001"
+     x="18.6"
+     y="15.5"
+     id="rect104"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="19"
+     y="16.4"
+     id="text106"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">as shipped with CUPS,</text>
+  <text
+     x="19"
+     y="17.200001"
+     id="text108"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">independent from any</text>
+  <text
+     x="19"
+     y="18"
+     id="text110"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">GhostScript installation on the</text>
+  <text
+     x="19"
+     y="18.799999"
+     id="text112"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">system</text>
+  <text
+     x="19"
+     y="19.6"
+     id="text114"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(= &quot;postscript interpreter&quot;)</text>
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/cups2.svg b/docs-xml/Samba3-HOWTO/images/cups2.svg
new file mode 100644
index 00000000000..8cddd339c01
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/cups2.svg
@@ -0,0 +1,320 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="24.681999cm"
+   height="42.34cm"
+   viewBox="0.268 0.758 24.95 43.098"
+   id="svg2">
+  <defs
+     id="defs139" />
+  <text
+     x="1"
+     y="1.3"
+     id="text4"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">something-fileformat</text>
+  <polygon
+     points="3.163,1.9 3.163,2.825 2.7,2.825 3.625,3.75 4.55,2.825 4.088,2.825 4.088,1.9 3.163,1.9 "
+     id="polygon6"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.163,1.9 3.163,2.825 2.7,2.825 3.625,3.75 4.55,2.825 4.088,2.825 4.088,1.9 3.163,1.9 "
+     id="polygon8"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.163,1.9 3.163,2.825 2.7,2.825 3.625,3.75 4.55,2.825 4.088,2.825 4.088,1.9 3.163,1.9 "
+     id="polygon10"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="1.7"
+     y="4.8000002"
+     id="text12"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">somethingtops</text>
+  <text
+     x="1.4"
+     y="8.3000002"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/postscript</text>
+  <polygon
+     points="3.262,5.4 3.262,6.325 2.8,6.325 3.725,7.25 4.65,6.325 4.188,6.325 4.188,5.4 3.262,5.4 "
+     id="polygon16"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.262,5.4 3.262,6.325 2.8,6.325 3.725,7.25 4.65,6.325 4.188,6.325 4.188,5.4 3.262,5.4 "
+     id="polygon18"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.262,5.4 3.262,6.325 2.8,6.325 3.725,7.25 4.65,6.325 4.188,6.325 4.188,5.4 3.262,5.4 "
+     id="polygon20"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="2.8"
+     y="11.5"
+     id="text22"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstops</text>
+  <polygon
+     points="3.262,8.7 3.262,9.625 2.8,9.625 3.725,10.55 4.65,9.625 4.188,9.625 4.188,8.7 3.262,8.7 "
+     id="polygon24"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.262,8.7 3.262,9.625 2.8,9.625 3.725,10.55 4.65,9.625 4.188,9.625 4.188,8.7 3.262,8.7 "
+     id="polygon26"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.262,8.7 3.262,9.625 2.8,9.625 3.725,10.55 4.65,9.625 4.188,9.625 4.188,8.7 3.262,8.7 "
+     id="polygon28"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="3.362,12.1 3.362,13.025 2.9,13.025 3.825,13.95 4.75,13.025 4.287,13.025 4.287,12.1 3.362,12.1 "
+     id="polygon30"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.362,12.1 3.362,13.025 2.9,13.025 3.825,13.95 4.75,13.025 4.287,13.025 4.287,12.1 3.362,12.1 "
+     id="polygon32"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.362,12.1 3.362,13.025 2.9,13.025 3.825,13.95 4.75,13.025 4.287,13.025 4.287,12.1 3.362,12.1 "
+     id="polygon34"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="0.30000001"
+     y="15"
+     id="text36"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-postscript</text>
+  <polygon
+     points="10.5,14.275 12,14.275 12,13.8 13.5,14.75 12,15.7 12,15.225 10.5,15.225 10.5,14.275 "
+     id="polygon38"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="10.5,14.275 12,14.275 12,13.8 13.5,14.75 12,15.7 12,15.225 10.5,15.225 10.5,14.275 "
+     id="polygon40"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="10.5,14.275 12,14.275 12,13.8 13.5,14.75 12,15.7 12,15.225 10.5,15.225 10.5,14.275 "
+     id="polygon42"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="14.2"
+     y="14.9"
+     id="text44"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">cupsomatic</text>
+  <rect
+     width="10.5"
+     height="3.8"
+     x="14.4"
+     y="10"
+     id="rect46"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="10.5"
+     height="3.8"
+     x="14.4"
+     y="10"
+     id="rect48"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="14.9"
+     y="11"
+     id="text50"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(constructs complicated</text>
+  <text
+     x="14.9"
+     y="11.8"
+     id="text52"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Ghostscript commandline</text>
+  <text
+     x="14.9"
+     y="12.6"
+     id="text54"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">to let the file be processed by a</text>
+  <text
+     x="14.9"
+     y="13.4"
+     id="text56"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">&quot;-sDEVICE-s.th.&quot; call...)</text>
+  <polygon
+     points="3.462,15.7 3.462,16.625 3,16.625 3.925,17.55 4.85,16.625 4.388,16.625 4.388,15.7 3.462,15.7 "
+     id="polygon58"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.462,15.7 3.462,16.625 3,16.625 3.925,17.55 4.85,16.625 4.388,16.625 4.388,15.7 3.462,15.7 "
+     id="polygon60"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.462,15.7 3.462,16.625 3,16.625 3.925,17.55 4.85,16.625 4.388,16.625 4.388,15.7 3.462,15.7 "
+     id="polygon62"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="2.6159999"
+     y="18.299999"
+     id="text64"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstoraster</text>
+  <text
+     x="0.26800001"
+     y="19.1"
+     id="text66"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(= &quot;postscript interpreter&quot;)</text>
+  <polygon
+     points="3.562,19.4 3.562,20.325 3.1,20.325 4.025,21.25 4.95,20.325 4.487,20.325 4.487,19.4 3.562,19.4 "
+     id="polygon68"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.562,19.4 3.562,20.325 3.1,20.325 4.025,21.25 4.95,20.325 4.487,20.325 4.487,19.4 3.562,19.4 "
+     id="polygon70"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.562,19.4 3.562,20.325 3.1,20.325 4.025,21.25 4.95,20.325 4.487,20.325 4.487,19.4 3.562,19.4 "
+     id="polygon72"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="0.80000001"
+     y="22.299999"
+     id="text74"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-raster</text>
+  <polygon
+     points="3.663,23 3.663,23.925 3.2,23.925 4.125,24.85 5.05,23.925 4.588,23.925 4.588,23 3.663,23 "
+     id="polygon76"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.663,23 3.663,23.925 3.2,23.925 4.125,24.85 5.05,23.925 4.588,23.925 4.588,23 3.663,23 "
+     id="polygon78"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.663,23 3.663,23.925 3.2,23.925 4.125,24.85 5.05,23.925 4.588,23.925 4.588,23 3.663,23 "
+     id="polygon80"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="1.7"
+     y="25.5"
+     id="text82"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">rastertosomething</text>
+  <text
+     x="1.7"
+     y="26.299999"
+     id="text84"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(= &quot;raster driver&quot;)</text>
+  <polygon
+     points="16.915,16.1 16.915,17.129 16.4,17.129 17.429,18.159 18.459,17.129 17.944,17.129 17.944,16.1 16.915,16.1 "
+     id="polygon86"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="16.915,16.1 16.915,17.129 16.4,17.129 17.429,18.159 18.459,17.129 17.944,17.129 17.944,16.1 16.915,16.1 "
+     id="polygon88"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="16.915,16.1 16.915,17.129 16.4,17.129 17.429,18.159 18.459,17.129 17.944,17.129 17.944,16.1 16.915,16.1 "
+     id="polygon90"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="3.762,26.8 3.762,27.725 3.3,27.725 4.225,28.65 5.15,27.725 4.688,27.725 4.688,26.8 3.762,26.8 "
+     id="polygon92"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.762,26.8 3.762,27.725 3.3,27.725 4.225,28.65 5.15,27.725 4.688,27.725 4.688,26.8 3.762,26.8 "
+     id="polygon94"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.762,26.8 3.762,27.725 3.3,27.725 4.225,28.65 5.15,27.725 4.688,27.725 4.688,26.8 3.762,26.8 "
+     id="polygon96"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="1"
+     y="29.6"
+     id="text98"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">something device specific</text>
+  <polygon
+     points="3.762,30.3 3.762,31.225 3.3,31.225 4.225,32.15 5.15,31.225 4.688,31.225 4.688,30.3 3.762,30.3 "
+     id="polygon100"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.762,30.3 3.762,31.225 3.3,31.225 4.225,32.15 5.15,31.225 4.688,31.225 4.688,30.3 3.762,30.3 "
+     id="polygon102"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.762,30.3 3.762,31.225 3.3,31.225 4.225,32.15 5.15,31.225 4.688,31.225 4.688,30.3 3.762,30.3 "
+     id="polygon104"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="3.2"
+     y="33.299999"
+     id="text106"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">backend</text>
+  <polygon
+     points="11.65,32.413 10.625,32.413 10.625,31.9 9.6,32.925 10.625,33.95 10.625,33.438 11.65,33.438 11.65,32.413 "
+     id="polygon108"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="11.65,32.413 10.625,32.413 10.625,31.9 9.6,32.925 10.625,33.95 10.625,33.438 11.65,33.438 11.65,32.413 "
+     id="polygon110"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="11.65,32.413 10.625,32.413 10.625,31.9 9.6,32.925 10.625,33.95 10.625,33.438 11.65,33.438 11.65,32.413 "
+     id="polygon112"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="7.5"
+     height="14.3"
+     x="14.6"
+     y="19.4"
+     id="rect114"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="7.5"
+     height="14.3"
+     x="14.6"
+     y="19.4"
+     id="rect116"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="15.28"
+     y="26.6"
+     id="text118"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Ghostscript at work....</text>
+  <text
+     x="1.2"
+     y="35.5"
+     id="text120"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Note, that cupsomatic &quot;kidnaps&quot; the printfile after the</text>
+  <text
+     x="1.2"
+     y="36.299999"
+     id="text122"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-postscript stage and deviates it gh</text>
+  <text
+     x="1.2"
+     y="37.099998"
+     id="text124"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">the CUPS-external, systemwide Ghostscript installation, bypassing the</text>
+  <text
+     x="1.2"
+     y="37.900002"
+     id="text126"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">&quot;pstoraster&quot; filter (therefore also bypassing the CUPS-raster-drivers</text>
+  <text
+     x="1.2"
+     y="38.700001"
+     id="text128"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">&quot;rastertosomething&quot;, and hands the rasterized file directly to the CUPS</text>
+  <text
+     x="1.2"
+     y="39.5"
+     id="text130"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">backend...</text>
+  <text
+     x="1.2"
+     y="41.099998"
+     id="text132"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">cupsomatic is not made by the CUPS developers. It is an independent</text>
+  <text
+     x="1.2"
+     y="41.900002"
+     id="text134"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">contribution to printing development, made by people from</text>
+  <text
+     x="1.2"
+     y="42.700001"
+     id="text136"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Linuxprinting.org. (see also http://www.cups.org/cups-help.html)</text>
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/domain.svg b/docs-xml/Samba3-HOWTO/images/domain.svg
new file mode 100644
index 00000000000..aca5d4be42f
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/domain.svg
@@ -0,0 +1,2288 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="30cm"
+   height="19.163cm"
+   viewBox="0.15 0.887 30.15 20.05"
+   id="svg2">
+  <defs
+     id="defs603" />
+  <ellipse
+     cx="15.15"
+     cy="11.2"
+     rx="14.95"
+     ry="8.8000002"
+     id="ellipse4"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.1830001"
+     height="6.5500002"
+     x="8.1999998"
+     y="3.9000001"
+     id="rect6"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.1830001"
+     height="6.5500002"
+     x="8.1999998"
+     y="3.9000001"
+     id="rect8"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.1830001"
+     height="6.5500002"
+     x="8.1999998"
+     y="3.9000001"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.747"
+     height="2.6199999"
+     x="8.4180002"
+     y="4.118"
+     id="rect12"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.747"
+     height="2.6199999"
+     x="8.4180002"
+     y="4.118"
+     id="rect14"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.747"
+     height="2.6199999"
+     x="8.4180002"
+     y="4.118"
+     id="rect16"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.4180002"
+     y1="4.5549998"
+     x2="10.165"
+     y2="4.5549998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.165"
+     y1="4.9920001"
+     x2="8.4180002"
+     y2="4.9920001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line20"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.4180002"
+     y1="5.428"
+     x2="10.165"
+     y2="5.428"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line22"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.4180002"
+     y1="5.8649998"
+     x2="10.165"
+     y2="5.8649998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line24"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.165"
+     y1="6.302"
+     x2="8.4180002"
+     y2="6.302"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.201"
+     height="0.65499997"
+     x="8.4180002"
+     y="6.9569998"
+     id="rect28"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.201"
+     height="0.65499997"
+     x="8.4180002"
+     y="6.9569998"
+     id="rect30"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.201"
+     height="0.65499997"
+     x="8.4180002"
+     y="6.9569998"
+     id="rect32"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.1999998"
+     y1="8.0480003"
+     x2="10.383"
+     y2="8.0480003"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line34"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.109"
+     height="0.109"
+     x="9.1820002"
+     y="8.2670002"
+     id="rect36"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.109"
+     height="0.109"
+     x="9.1820002"
+     y="8.2670002"
+     id="rect38"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.109"
+     height="0.109"
+     x="9.1820002"
+     y="8.2670002"
+     id="rect40"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.109"
+     height="0.109"
+     x="9.6190004"
+     y="8.2670002"
+     id="rect42"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.109"
+     height="0.109"
+     x="9.6190004"
+     y="8.2670002"
+     id="rect44"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.109"
+     height="0.109"
+     x="9.6190004"
+     y="8.2670002"
+     id="rect46"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.109"
+     height="0.109"
+     x="10.056"
+     y="8.2670002"
+     id="rect48"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.109"
+     height="0.109"
+     x="10.056"
+     y="8.2670002"
+     id="rect50"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.109"
+     height="0.109"
+     x="10.056"
+     y="8.2670002"
+     id="rect52"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.21799999"
+     height="0.21799999"
+     x="9.9469995"
+     y="7.612"
+     id="rect54"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.21799999"
+     height="0.21799999"
+     x="9.9469995"
+     y="7.612"
+     id="rect56"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.21799999"
+     height="0.21799999"
+     x="9.9469995"
+     y="7.612"
+     id="rect58"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.4180002"
+     y1="7.2839999"
+     x2="9.6190004"
+     y2="7.2839999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line60"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.32800001"
+     height="0.32800001"
+     x="8.4180002"
+     y="8.1569996"
+     id="rect62"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.32800001"
+     height="0.32800001"
+     x="8.4180002"
+     y="8.1569996"
+     id="rect64"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.32800001"
+     height="0.32800001"
+     x="8.4180002"
+     y="8.1569996"
+     id="rect66"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.528"
+     height="0.109"
+     x="8.5270004"
+     y="6.4109998"
+     id="rect68"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.528"
+     height="0.109"
+     x="8.5270004"
+     y="6.4109998"
+     id="rect70"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.528"
+     height="0.109"
+     x="8.5270004"
+     y="6.4109998"
+     id="rect72"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.5270004"
+     y1="7.066"
+     x2="9.5100002"
+     y2="7.066"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.5100002"
+     y1="7.1750002"
+     x2="9.401"
+     y2="7.1750002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line76"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.5270004"
+     y1="7.1750002"
+     x2="8.6370001"
+     y2="7.1750002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line78"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.546"
+     height="0.109"
+     x="8.7460003"
+     y="7.066"
+     id="rect80"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.546"
+     height="0.109"
+     x="8.7460003"
+     y="7.066"
+     id="rect82"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.546"
+     height="0.109"
+     x="8.7460003"
+     y="7.066"
+     id="rect84"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.5270004"
+     y1="6.6290002"
+     x2="8.6370001"
+     y2="6.6290002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line86"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.7460003"
+     y1="6.6290002"
+     x2="8.8549995"
+     y2="6.6290002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line88"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="9.8369999"
+     y1="6.6290002"
+     x2="10.056"
+     y2="6.6290002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line90"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.309"
+     y1="10.341"
+     x2="10.274"
+     y2="10.341"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line92"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.274"
+     y1="10.232"
+     x2="8.309"
+     y2="10.232"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line94"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.309"
+     y1="10.123"
+     x2="10.274"
+     y2="10.123"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line96"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.274"
+     y1="10.013"
+     x2="8.309"
+     y2="10.013"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line98"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.309"
+     y1="9.9040003"
+     x2="10.274"
+     y2="9.9040003"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line100"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.274"
+     y1="9.7950001"
+     x2="8.309"
+     y2="9.7950001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line102"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.309"
+     y1="9.6859999"
+     x2="10.274"
+     y2="9.6859999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line104"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.274"
+     y1="9.5769997"
+     x2="8.309"
+     y2="9.5769997"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line106"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.309"
+     y1="9.467"
+     x2="10.274"
+     y2="9.467"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line108"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.274"
+     y1="9.3579998"
+     x2="8.309"
+     y2="9.3579998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line110"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.309"
+     y1="9.2489996"
+     x2="10.274"
+     y2="9.2489996"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line112"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.274"
+     y1="9.1400003"
+     x2="8.309"
+     y2="9.1400003"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line114"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="8.309"
+     y1="9.0310001"
+     x2="10.274"
+     y2="9.0310001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line116"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="10.274"
+     y1="8.9219999"
+     x2="8.309"
+     y2="8.9219999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line118"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="4.9000001"
+     y="5.6999998"
+     id="text120"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Primary</text>
+  <text
+     x="4.9000001"
+     y="6.5"
+     id="text122"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Domain</text>
+  <text
+     x="4.9000001"
+     y="7.3000002"
+     id="text124"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Controller</text>
+  <rect
+     width="2.6359999"
+     height="5.2709999"
+     x="1.7"
+     y="9.1000004"
+     id="rect126"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.6359999"
+     height="5.2709999"
+     x="1.7"
+     y="9.1000004"
+     id="rect128"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.6359999"
+     height="5.2709999"
+     x="1.7"
+     y="9.1000004"
+     id="rect130"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="2.108"
+     height="2.108"
+     x="1.964"
+     y="9.3640003"
+     id="rect132"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.108"
+     height="2.108"
+     x="1.964"
+     y="9.3640003"
+     id="rect134"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.108"
+     height="2.108"
+     x="1.964"
+     y="9.3640003"
+     id="rect136"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.072"
+     y1="9.8909998"
+     x2="1.964"
+     y2="9.8909998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line138"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.964"
+     y1="10.418"
+     x2="4.072"
+     y2="10.418"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line140"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.072"
+     y1="10.813"
+     x2="1.964"
+     y2="10.813"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line142"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.45"
+     height="0.79100001"
+     x="1.964"
+     y="11.736"
+     id="rect144"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.45"
+     height="0.79100001"
+     x="1.964"
+     y="11.736"
+     id="rect146"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.45"
+     height="0.79100001"
+     x="1.964"
+     y="11.736"
+     id="rect148"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.7"
+     y1="12.658"
+     x2="4.336"
+     y2="12.658"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line150"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="2.8859999"
+     y="12.922"
+     id="rect152"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="2.8859999"
+     y="12.922"
+     id="rect154"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="2.8859999"
+     y="12.922"
+     id="rect156"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="3.4130001"
+     y="12.922"
+     id="rect158"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="3.4130001"
+     y="12.922"
+     id="rect160"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="3.4130001"
+     y="12.922"
+     id="rect162"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="3.9400001"
+     y="12.922"
+     id="rect164"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="3.9400001"
+     y="12.922"
+     id="rect166"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="3.9400001"
+     y="12.922"
+     id="rect168"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.264"
+     height="0.132"
+     x="3.8080001"
+     y="12.131"
+     id="rect170"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.264"
+     height="0.132"
+     x="3.8080001"
+     y="12.131"
+     id="rect172"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.264"
+     height="0.132"
+     x="3.8080001"
+     y="12.131"
+     id="rect174"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.964"
+     y1="12.131"
+     x2="3.4130001"
+     y2="12.131"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line176"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.39500001"
+     height="0.39500001"
+     x="1.964"
+     y="12.79"
+     id="rect178"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.39500001"
+     height="0.39500001"
+     x="1.964"
+     y="12.79"
+     id="rect180"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.39500001"
+     height="0.39500001"
+     x="1.964"
+     y="12.79"
+     id="rect182"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.845"
+     height="0.132"
+     x="2.095"
+     y="10.945"
+     id="rect184"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.845"
+     height="0.132"
+     x="2.095"
+     y="10.945"
+     id="rect186"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.845"
+     height="0.132"
+     x="2.095"
+     y="10.945"
+     id="rect188"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.095"
+     y1="11.867"
+     x2="3.2809999"
+     y2="11.867"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line190"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.2809999"
+     y1="11.999"
+     x2="3.1500001"
+     y2="11.999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line192"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.095"
+     y1="11.999"
+     x2="2.227"
+     y2="11.999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line194"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.65899998"
+     height="0.132"
+     x="2.359"
+     y="11.867"
+     id="rect196"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.65899998"
+     height="0.132"
+     x="2.359"
+     y="11.867"
+     id="rect198"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.65899998"
+     height="0.132"
+     x="2.359"
+     y="11.867"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.095"
+     y1="11.208"
+     x2="2.227"
+     y2="11.208"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line202"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="2.359"
+     y1="11.208"
+     x2="2.4909999"
+     y2="11.208"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line204"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="3.677"
+     y1="11.208"
+     x2="3.9400001"
+     y2="11.208"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line206"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.204"
+     y1="14.239"
+     x2="1.832"
+     y2="14.239"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line208"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.832"
+     y1="14.108"
+     x2="4.204"
+     y2="14.108"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line210"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.204"
+     y1="13.976"
+     x2="1.832"
+     y2="13.976"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line212"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.832"
+     y1="13.844"
+     x2="4.204"
+     y2="13.844"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line214"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.204"
+     y1="13.712"
+     x2="1.832"
+     y2="13.712"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line216"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="1.832"
+     y1="13.58"
+     x2="4.204"
+     y2="13.58"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line218"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="4.204"
+     y1="13.449"
+     x2="1.832"
+     y2="13.449"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line220"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="3.5"
+     y="15.5"
+     id="text222"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Backup Domain</text>
+  <text
+     x="3.5"
+     y="16.299999"
+     id="text224"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Controller 1</text>
+  <rect
+     width="2.6359999"
+     height="5.2709999"
+     x="13.6"
+     y="13.5"
+     id="rect226"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.6359999"
+     height="5.2709999"
+     x="13.6"
+     y="13.5"
+     id="rect228"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.6359999"
+     height="5.2709999"
+     x="13.6"
+     y="13.5"
+     id="rect230"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="2.108"
+     height="2.108"
+     x="13.864"
+     y="13.764"
+     id="rect232"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.108"
+     height="2.108"
+     x="13.864"
+     y="13.764"
+     id="rect234"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.108"
+     height="2.108"
+     x="13.864"
+     y="13.764"
+     id="rect236"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.972"
+     y1="14.291"
+     x2="13.864"
+     y2="14.291"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line238"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.864"
+     y1="14.818"
+     x2="15.972"
+     y2="14.818"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line240"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.972"
+     y1="15.213"
+     x2="13.864"
+     y2="15.213"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line242"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.45"
+     height="0.79100001"
+     x="13.864"
+     y="16.136"
+     id="rect244"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="1.45"
+     height="0.79100001"
+     x="13.864"
+     y="16.136"
+     id="rect246"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.45"
+     height="0.79100001"
+     x="13.864"
+     y="16.136"
+     id="rect248"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.6"
+     y1="17.058001"
+     x2="16.236"
+     y2="17.058001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line250"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="14.786"
+     y="17.322001"
+     id="rect252"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="14.786"
+     y="17.322001"
+     id="rect254"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="14.786"
+     y="17.322001"
+     id="rect256"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="15.313"
+     y="17.322001"
+     id="rect258"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="15.313"
+     y="17.322001"
+     id="rect260"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="15.313"
+     y="17.322001"
+     id="rect262"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="15.84"
+     y="17.322001"
+     id="rect264"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="15.84"
+     y="17.322001"
+     id="rect266"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.132"
+     height="0.132"
+     x="15.84"
+     y="17.322001"
+     id="rect268"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.264"
+     height="0.132"
+     x="15.708"
+     y="16.531"
+     id="rect270"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.264"
+     height="0.132"
+     x="15.708"
+     y="16.531"
+     id="rect272"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.264"
+     height="0.132"
+     x="15.708"
+     y="16.531"
+     id="rect274"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.864"
+     y1="16.531"
+     x2="15.313"
+     y2="16.531"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line276"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.39500001"
+     height="0.39500001"
+     x="13.864"
+     y="17.190001"
+     id="rect278"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.39500001"
+     height="0.39500001"
+     x="13.864"
+     y="17.190001"
+     id="rect280"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.39500001"
+     height="0.39500001"
+     x="13.864"
+     y="17.190001"
+     id="rect282"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.845"
+     height="0.132"
+     x="13.995"
+     y="15.345"
+     id="rect284"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.845"
+     height="0.132"
+     x="13.995"
+     y="15.345"
+     id="rect286"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.845"
+     height="0.132"
+     x="13.995"
+     y="15.345"
+     id="rect288"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.995"
+     y1="16.267"
+     x2="15.181"
+     y2="16.267"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line290"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.181"
+     y1="16.399"
+     x2="15.05"
+     y2="16.399"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line292"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.995"
+     y1="16.399"
+     x2="14.127"
+     y2="16.399"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line294"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.65899998"
+     height="0.132"
+     x="14.259"
+     y="16.267"
+     id="rect296"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.65899998"
+     height="0.132"
+     x="14.259"
+     y="16.267"
+     id="rect298"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.65899998"
+     height="0.132"
+     x="14.259"
+     y="16.267"
+     id="rect300"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.995"
+     y1="15.608"
+     x2="14.127"
+     y2="15.608"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line302"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="14.259"
+     y1="15.608"
+     x2="14.391"
+     y2="15.608"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line304"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="15.577"
+     y1="15.608"
+     x2="15.84"
+     y2="15.608"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line306"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.104"
+     y1="18.639"
+     x2="13.732"
+     y2="18.639"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line308"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.732"
+     y1="18.507999"
+     x2="16.104"
+     y2="18.507999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line310"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.104"
+     y1="18.375999"
+     x2="13.732"
+     y2="18.375999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line312"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.732"
+     y1="18.243999"
+     x2="16.104"
+     y2="18.243999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line314"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.104"
+     y1="18.112"
+     x2="13.732"
+     y2="18.112"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line316"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="13.732"
+     y1="17.98"
+     x2="16.104"
+     y2="17.98"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line318"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="16.104"
+     y1="17.849001"
+     x2="13.732"
+     y2="17.849001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line320"
+     style="stroke:#000000;stroke-width:0.01" />
+  <text
+     x="16.9"
+     y="14.7"
+     id="text322"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Backup Domain</text>
+  <text
+     x="16.9"
+     y="15.5"
+     id="text324"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Controller 2</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="4.336,11.736 4.336,12.000 9.292,12.000 9.292,10.450 "
+     id="polyline326"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="14.918,13.500 14.918,11.975 9.292,11.975 9.292,10.450 "
+     id="polyline328"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="5.3000002"
+     height="1.767"
+     x="17.4"
+     y="4.9000001"
+     id="rect330"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="5.3000002"
+     height="1.767"
+     x="17.4"
+     y="4.9000001"
+     id="rect332"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="5.3000002"
+     height="1.767"
+     x="17.4"
+     y="4.9000001"
+     id="rect334"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="2.0190001"
+     height="1.01"
+     x="20.555"
+     y="5.4050002"
+     id="rect336"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.0190001"
+     height="1.01"
+     x="20.555"
+     y="5.4050002"
+     id="rect338"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.0190001"
+     height="1.01"
+     x="20.555"
+     y="5.4050002"
+     id="rect340"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="22.573999"
+     y1="5.9099998"
+     x2="20.555"
+     y2="5.9099998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line342"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.37900001"
+     height="1.388"
+     x="20.049999"
+     y="5.026"
+     id="rect344"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.37900001"
+     height="1.388"
+     x="20.049999"
+     y="5.026"
+     id="rect346"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.37900001"
+     height="1.388"
+     x="20.049999"
+     y="5.026"
+     id="rect348"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.126"
+     height="0.126"
+     x="18.662001"
+     y="5.152"
+     id="rect350"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.126"
+     height="0.126"
+     x="18.662001"
+     y="5.152"
+     id="rect352"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.126"
+     height="0.126"
+     x="18.662001"
+     y="5.152"
+     id="rect354"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.126"
+     height="0.126"
+     x="18.914"
+     y="5.152"
+     id="rect356"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.126"
+     height="0.126"
+     x="18.914"
+     y="5.152"
+     id="rect358"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.126"
+     height="0.126"
+     x="18.914"
+     y="5.152"
+     id="rect360"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.126"
+     height="0.126"
+     x="19.167"
+     y="5.152"
+     id="rect362"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.126"
+     height="0.126"
+     x="19.167"
+     y="5.152"
+     id="rect364"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.126"
+     height="0.126"
+     x="19.167"
+     y="5.152"
+     id="rect366"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.252"
+     height="0.252"
+     x="19.545"
+     y="5.026"
+     id="rect368"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.252"
+     height="0.252"
+     x="19.545"
+     y="5.026"
+     id="rect370"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.252"
+     height="0.252"
+     x="19.545"
+     y="5.026"
+     id="rect372"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.37900001"
+     height="0.37900001"
+     x="17.652"
+     y="5.026"
+     id="rect374"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.37900001"
+     height="0.37900001"
+     x="17.652"
+     y="5.026"
+     id="rect376"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.37900001"
+     height="0.37900001"
+     x="17.652"
+     y="5.026"
+     id="rect378"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.767"
+     height="0.126"
+     x="20.681"
+     y="6.0359998"
+     id="rect380"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.767"
+     height="0.126"
+     x="20.681"
+     y="6.0359998"
+     id="rect382"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.767"
+     height="0.126"
+     x="20.681"
+     y="6.0359998"
+     id="rect384"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.176001"
+     y1="5.152"
+     x2="20.176001"
+     y2="6.2880001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line386"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.126"
+     height="0.63099998"
+     x="20.176001"
+     y="5.4050002"
+     id="rect388"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.126"
+     height="0.63099998"
+     x="20.176001"
+     y="5.4050002"
+     id="rect390"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.126"
+     height="0.63099998"
+     x="20.176001"
+     y="5.4050002"
+     id="rect392"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="22.195"
+     y1="6.2880001"
+     x2="22.448"
+     y2="6.2880001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line394"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.525999"
+     y1="5.783"
+     x2="19.798"
+     y2="5.783"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line396"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.798"
+     y1="5.9099998"
+     x2="17.525999"
+     y2="5.9099998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line398"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.525999"
+     y1="6.0359998"
+     x2="19.798"
+     y2="6.0359998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line400"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.798"
+     y1="6.414"
+     x2="17.525999"
+     y2="6.414"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line402"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.525999"
+     y1="6.2880001"
+     x2="19.798"
+     y2="6.2880001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line404"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.798"
+     y1="6.1620002"
+     x2="17.525999"
+     y2="6.1620002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line406"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.681"
+     y1="6.2880001"
+     x2="20.806999"
+     y2="6.2880001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line408"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.933001"
+     y1="6.2880001"
+     x2="21.059999"
+     y2="6.2880001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line410"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.302"
+     y1="6.2880001"
+     x2="20.302"
+     y2="6.1620002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line412"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.302"
+     y1="5.2789998"
+     x2="20.302"
+     y2="5.152"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line414"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="5.4000001"
+     height="1.8"
+     x="17.4"
+     y="7.4000001"
+     id="rect416"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="5.4000001"
+     height="1.8"
+     x="17.4"
+     y="7.4000001"
+     id="rect418"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="5.4000001"
+     height="1.8"
+     x="17.4"
+     y="7.4000001"
+     id="rect420"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="2.0569999"
+     height="1.029"
+     x="20.614"
+     y="7.914"
+     id="rect422"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.0569999"
+     height="1.029"
+     x="20.614"
+     y="7.914"
+     id="rect424"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.0569999"
+     height="1.029"
+     x="20.614"
+     y="7.914"
+     id="rect426"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="22.671"
+     y1="8.4289999"
+     x2="20.614"
+     y2="8.4289999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line428"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.38600001"
+     height="1.414"
+     x="20.1"
+     y="7.5289998"
+     id="rect430"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.38600001"
+     height="1.414"
+     x="20.1"
+     y="7.5289998"
+     id="rect432"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.38600001"
+     height="1.414"
+     x="20.1"
+     y="7.5289998"
+     id="rect434"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.12899999"
+     height="0.12899999"
+     x="18.686001"
+     y="7.6570001"
+     id="rect436"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.12899999"
+     height="0.12899999"
+     x="18.686001"
+     y="7.6570001"
+     id="rect438"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.12899999"
+     height="0.12899999"
+     x="18.686001"
+     y="7.6570001"
+     id="rect440"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.12899999"
+     height="0.12899999"
+     x="18.943001"
+     y="7.6570001"
+     id="rect442"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.12899999"
+     height="0.12899999"
+     x="18.943001"
+     y="7.6570001"
+     id="rect444"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.12899999"
+     height="0.12899999"
+     x="18.943001"
+     y="7.6570001"
+     id="rect446"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.12899999"
+     height="0.12899999"
+     x="19.200001"
+     y="7.6570001"
+     id="rect448"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.12899999"
+     height="0.12899999"
+     x="19.200001"
+     y="7.6570001"
+     id="rect450"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.12899999"
+     height="0.12899999"
+     x="19.200001"
+     y="7.6570001"
+     id="rect452"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.257"
+     height="0.257"
+     x="19.586"
+     y="7.5289998"
+     id="rect454"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.257"
+     height="0.257"
+     x="19.586"
+     y="7.5289998"
+     id="rect456"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.257"
+     height="0.257"
+     x="19.586"
+     y="7.5289998"
+     id="rect458"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.38600001"
+     height="0.38600001"
+     x="17.657"
+     y="7.5289998"
+     id="rect460"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.38600001"
+     height="0.38600001"
+     x="17.657"
+     y="7.5289998"
+     id="rect462"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.38600001"
+     height="0.38600001"
+     x="17.657"
+     y="7.5289998"
+     id="rect464"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.8"
+     height="0.12899999"
+     x="20.743"
+     y="8.5570002"
+     id="rect466"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.8"
+     height="0.12899999"
+     x="20.743"
+     y="8.5570002"
+     id="rect468"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.8"
+     height="0.12899999"
+     x="20.743"
+     y="8.5570002"
+     id="rect470"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.229"
+     y1="7.6570001"
+     x2="20.229"
+     y2="8.8140001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line472"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.12899999"
+     height="0.64300001"
+     x="20.229"
+     y="7.914"
+     id="rect474"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.12899999"
+     height="0.64300001"
+     x="20.229"
+     y="7.914"
+     id="rect476"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.12899999"
+     height="0.64300001"
+     x="20.229"
+     y="7.914"
+     id="rect478"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="22.285999"
+     y1="8.8140001"
+     x2="22.542999"
+     y2="8.8140001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line480"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.528999"
+     y1="8.3000002"
+     x2="19.843"
+     y2="8.3000002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line482"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.843"
+     y1="8.4289999"
+     x2="17.528999"
+     y2="8.4289999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line484"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.528999"
+     y1="8.5570002"
+     x2="19.843"
+     y2="8.5570002"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line486"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.843"
+     y1="8.9429998"
+     x2="17.528999"
+     y2="8.9429998"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line488"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.528999"
+     y1="8.8140001"
+     x2="19.843"
+     y2="8.8140001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line490"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.843"
+     y1="8.6859999"
+     x2="17.528999"
+     y2="8.6859999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line492"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.743"
+     y1="8.8140001"
+     x2="20.871"
+     y2="8.8140001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line494"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21"
+     y1="8.8140001"
+     x2="21.129"
+     y2="8.8140001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line496"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.357"
+     y1="8.8140001"
+     x2="20.357"
+     y2="8.6859999"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line498"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.357"
+     y1="7.7859998"
+     x2="20.357"
+     y2="7.6570001"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line500"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="5.4499998"
+     height="1.817"
+     x="17.5"
+     y="9.8000002"
+     id="rect502"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="5.4499998"
+     height="1.817"
+     x="17.5"
+     y="9.8000002"
+     id="rect504"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="5.4499998"
+     height="1.817"
+     x="17.5"
+     y="9.8000002"
+     id="rect506"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="2.076"
+     height="1.038"
+     x="20.743999"
+     y="10.319"
+     id="rect508"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="2.076"
+     height="1.038"
+     x="20.743999"
+     y="10.319"
+     id="rect510"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="2.076"
+     height="1.038"
+     x="20.743999"
+     y="10.319"
+     id="rect512"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="22.82"
+     y1="10.838"
+     x2="20.743999"
+     y2="10.838"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line514"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.389"
+     height="1.427"
+     x="20.225"
+     y="9.9300003"
+     id="rect516"
+     style="fill:#d9d9cd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.389"
+     height="1.427"
+     x="20.225"
+     y="9.9300003"
+     id="rect518"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.389"
+     height="1.427"
+     x="20.225"
+     y="9.9300003"
+     id="rect520"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.13"
+     height="0.13"
+     x="18.798"
+     y="10.06"
+     id="rect522"
+     style="fill:#00cd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.13"
+     height="0.13"
+     x="18.798"
+     y="10.06"
+     id="rect524"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.13"
+     height="0.13"
+     x="18.798"
+     y="10.06"
+     id="rect526"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.13"
+     height="0.13"
+     x="19.056999"
+     y="10.06"
+     id="rect528"
+     style="fill:#cdcd00;stroke:none;stroke-width:0" />
+  <rect
+     width="0.13"
+     height="0.13"
+     x="19.056999"
+     y="10.06"
+     id="rect530"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.13"
+     height="0.13"
+     x="19.056999"
+     y="10.06"
+     id="rect532"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.13"
+     height="0.13"
+     x="19.316999"
+     y="10.06"
+     id="rect534"
+     style="fill:#cd0000;stroke:none;stroke-width:0" />
+  <rect
+     width="0.13"
+     height="0.13"
+     x="19.316999"
+     y="10.06"
+     id="rect536"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.13"
+     height="0.13"
+     x="19.316999"
+     y="10.06"
+     id="rect538"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.25999999"
+     height="0.25999999"
+     x="19.705999"
+     y="9.9300003"
+     id="rect540"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.25999999"
+     height="0.25999999"
+     x="19.705999"
+     y="9.9300003"
+     id="rect542"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.25999999"
+     height="0.25999999"
+     x="19.705999"
+     y="9.9300003"
+     id="rect544"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.389"
+     height="0.389"
+     x="17.76"
+     y="9.9300003"
+     id="rect546"
+     style="fill:#cdcdbd;stroke:none;stroke-width:0" />
+  <rect
+     width="0.389"
+     height="0.389"
+     x="17.76"
+     y="9.9300003"
+     id="rect548"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.389"
+     height="0.389"
+     x="17.76"
+     y="9.9300003"
+     id="rect550"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.817"
+     height="0.13"
+     x="20.874001"
+     y="10.968"
+     id="rect552"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="1.817"
+     height="0.13"
+     x="20.874001"
+     y="10.968"
+     id="rect554"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.817"
+     height="0.13"
+     x="20.874001"
+     y="10.968"
+     id="rect556"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.355"
+     y1="10.06"
+     x2="20.355"
+     y2="11.227"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line558"
+     style="stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.13"
+     height="0.64899999"
+     x="20.355"
+     y="10.319"
+     id="rect560"
+     style="fill:#cdcdc1;stroke:none;stroke-width:0" />
+  <rect
+     width="0.13"
+     height="0.64899999"
+     x="20.355"
+     y="10.319"
+     id="rect562"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="0.13"
+     height="0.64899999"
+     x="20.355"
+     y="10.319"
+     id="rect564"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="22.431"
+     y1="11.227"
+     x2="22.690001"
+     y2="11.227"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line566"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.629999"
+     y1="10.708"
+     x2="19.965"
+     y2="10.708"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line568"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.965"
+     y1="10.838"
+     x2="17.629999"
+     y2="10.838"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line570"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.629999"
+     y1="10.968"
+     x2="19.965"
+     y2="10.968"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line572"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.965"
+     y1="11.357"
+     x2="17.629999"
+     y2="11.357"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line574"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="17.629999"
+     y1="11.227"
+     x2="19.965"
+     y2="11.227"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line576"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="19.965"
+     y1="11.098"
+     x2="17.629999"
+     y2="11.098"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line578"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.874001"
+     y1="11.227"
+     x2="21.004"
+     y2="11.227"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line580"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="21.132999"
+     y1="11.227"
+     x2="21.263"
+     y2="11.227"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line582"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.485001"
+     y1="11.227"
+     x2="20.485001"
+     y2="11.098"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line584"
+     style="stroke:#000000;stroke-width:0.01" />
+  <line
+     x1="20.485001"
+     y1="10.189"
+     x2="20.485001"
+     y2="10.06"
+     stroke="#000000"
+     stroke-width="0.010"
+     id="line586"
+     style="stroke:#000000;stroke-width:0.01" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="9.300,12.000 13.992,12.000 13.992,5.783 17.400,5.783 "
+     id="polyline588"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="17.400,8.300 14.000,8.300 14.000,12.000 10.200,12.000 "
+     id="polyline590"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="17.500,10.708 14.000,10.708 14.000,12.000 10.300,12.000 "
+     id="polyline592"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="17.700001"
+     y="4.3000002"
+     id="text594"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Workstation A</text>
+  <text
+     x="23.799999"
+     y="8.6000004"
+     id="text596"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Workstation B</text>
+  <text
+     x="23.799999"
+     y="10.9"
+     id="text598"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Workstation C</text>
+  <text
+     x="13.1"
+     y="1.7"
+     id="text600"
+     style="font-size:1.20000005px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">DOMAIN</text>
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/ethereal1.png b/docs-xml/Samba3-HOWTO/images/ethereal1.png
new file mode 100644
index 00000000000..c8655389d06
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/ethereal1.png
diff --git a/docs-xml/Samba3-HOWTO/images/ethereal2.png b/docs-xml/Samba3-HOWTO/images/ethereal2.png
new file mode 100644
index 00000000000..f366772d3b7
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/ethereal2.png
diff --git a/docs-xml/Samba3-HOWTO/images/idmap-gid2sid.svg b/docs-xml/Samba3-HOWTO/images/idmap-gid2sid.svg
new file mode 100644
index 00000000000..61181b75c8a
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/idmap-gid2sid.svg
@@ -0,0 +1,277 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="24.174cm"
+   height="19.486cm"
+   viewBox="-0.49 0.171 23.684 19.657"
+   id="svg2">
+  <defs
+     id="defs97" />
+  <path
+     d="M 3.333,0.221 L 5.667,0.221 C 5.989,0.221 6.25,0.626 6.25,1.125 C 6.25,1.624 5.989,2.029 5.667,2.029 L 3.333,2.029 C 3.011,2.029 2.75,1.624 2.75,1.125 C 2.75,0.626 3.011,0.221 3.333,0.221"
+     id="path4"
+     style="fill:#c9c9c9;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 3.333,0.221 L 5.667,0.221 C 5.989,0.221 6.25,0.626 6.25,1.125 C 6.25,1.624 5.989,2.029 5.667,2.029 L 3.333,2.029 C 3.011,2.029 2.75,1.624 2.75,1.125 C 2.75,0.626 3.011,0.221 3.333,0.221"
+     id="path6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.7609999"
+     y="1.303"
+     id="text8"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">GID</text>
+  <line
+     x1="4.5040002"
+     y1="5.5"
+     x2="4.5019999"
+     y2="6.1500001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line10"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.102,6.149 4.5,6.95 4.902,6.151 4.102,6.149 "
+     id="polygon12"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 5.883,16.8 L 9.117,16.8 C 9.564,16.8 9.926,17.428 9.926,18.204 C 9.926,18.979 9.564,19.607 9.117,19.607 L 5.883,19.607 C 5.436,19.607 5.074,18.979 5.074,18.204 C 5.074,17.428 5.436,16.8 5.883,16.8"
+     id="path14"
+     style="fill:#d5d5d5;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 5.883,16.8 L 9.117,16.8 C 9.564,16.8 9.926,17.428 9.926,18.204 C 9.926,18.979 9.564,19.607 9.117,19.607 L 5.883,19.607 C 5.436,19.607 5.074,18.979 5.074,18.204 C 5.074,17.428 5.436,16.8 5.883,16.8"
+     id="path16"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.2859998"
+     y="17.881001"
+     id="text18"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">group</text>
+  <text
+     x="6.7989998"
+     y="18.881001"
+     id="text20"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
+  <path
+     d="M 16.083,11.65 L 18.417,11.65 C 18.739,11.65 19,12.055 19,12.554 C 19,13.053 18.739,13.457 18.417,13.457 L 16.083,13.457 C 15.761,13.457 15.5,13.053 15.5,12.554 C 15.5,12.055 15.761,11.65 16.083,11.65"
+     id="path22"
+     style="fill:#dbd8d8;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 16.083,11.65 L 18.417,11.65 C 18.739,11.65 19,12.055 19,12.554 C 19,13.053 18.739,13.457 18.417,13.457 L 16.083,13.457 C 15.761,13.457 15.5,13.053 15.5,12.554 C 15.5,12.055 15.761,11.65 16.083,11.65"
+     id="path24"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="16.525999"
+     y="12.731"
+     id="text26"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Fail</text>
+  <line
+     x1="13"
+     y1="12.5"
+     x2="14.65"
+     y2="12.5"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line28"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="14.65,12.9 15.45,12.5 14.65,12.1 14.65,12.9 "
+     id="polygon30"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="11,11 13,12.5 11,14 9,12.5 11,11 "
+     id="polygon32"
+     style="fill:#abfafe;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="11,11 13,12.5 11,14 9,12.5 11,11 "
+     id="polygon34"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="9.5229998"
+     y="12.75"
+     id="text36"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
+  <text
+     x="11.531"
+     y="15"
+     id="text38"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
+  <line
+     x1="10.989"
+     y1="9.3999996"
+     x2="10.994"
+     y2="10.15"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line40"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="10.594,10.153 11,10.95 11.394,10.147 10.594,10.153 "
+     id="polygon42"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="13.104"
+     y="12.25"
+     id="text44"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
+  <line
+     x1="7.5"
+     y1="15.25"
+     x2="7.5"
+     y2="15.95"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="7.1,15.95 7.5,16.75 7.9,15.95 7.1,15.95 "
+     id="polygon48"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.5,7 6.5,8.5 4.5,10 2.5,8.5 4.5,7 "
+     id="polygon50"
+     style="fill:#c5effb;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.5,7 6.5,8.5 4.5,10 2.5,8.5 4.5,7 "
+     id="polygon52"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.0220001"
+     y="8.75"
+     id="text54"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
+  <text
+     x="5.0310001"
+     y="10.75"
+     id="text56"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
+  <line
+     x1="4.5"
+     y1="2.029"
+     x2="4.5009999"
+     y2="2.55"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line58"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.101,2.551 4.503,3.35 4.901,2.549 4.101,2.551 "
+     id="polygon60"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="6.6040001"
+     y="8.25"
+     id="text62"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
+  <line
+     x1="6.5"
+     y1="8.5"
+     x2="8.1499996"
+     y2="8.5"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line64"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="8.15,8.9 8.95,8.5 8.15,8.1 8.15,8.9 "
+     id="polygon66"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <rect
+     width="4.4899998"
+     height="2.0999999"
+     x="8.7440004"
+     y="7.4000001"
+     id="rect68"
+     style="fill:#d5d5d5;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4899998"
+     height="2.0999999"
+     x="8.7440004"
+     y="7.4000001"
+     id="rect70"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="9.2939997"
+     y="8.6280003"
+     id="text72"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Winbind</text>
+  <line
+     x1="13.25"
+     y1="8.75"
+     x2="15.25"
+     y2="9.5"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="13.25"
+     y1="8.25"
+     x2="15.25"
+     y2="7.5"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line76"
+     style="stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="8"
+     height="2"
+     x="15.5"
+     y="7.5"
+     id="rect78"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="8"
+     height="2"
+     x="15.5"
+     y="7.5"
+     id="rect80"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="15.316"
+     y="8.25"
+     id="text82"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">winbindd_idmap.tdb</text>
+  <text
+     x="17.761999"
+     y="9.25"
+     id="text84"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
+  <line
+     x1="23.5"
+     y1="8.5"
+     x2="15.5"
+     y2="8.5"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line86"
+     style="stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="9.8870001"
+     height="2.0999999"
+     x="-0.44"
+     y="3.4000001"
+     id="rect88"
+     style="fill:#dcdcdc;stroke:none;stroke-width:0" />
+  <rect
+     width="9.8870001"
+     height="2.0999999"
+     x="-0.44"
+     y="3.4000001"
+     id="rect90"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.11"
+     y="4.6269999"
+     id="text92"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">groupmap_idmap.tdb</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="4.500,10.000 4.500,15.250 11.000,15.250 11.000,14.000 "
+     id="polyline94"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/idmap-groups.svg b/docs-xml/Samba3-HOWTO/images/idmap-groups.svg
new file mode 100644
index 00000000000..58b1dc6be6c
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/idmap-groups.svg
@@ -0,0 +1,129 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="9.6999998cm"
+   height="17.848cm"
+   viewBox="2.95 0.95 12.65 18.798"
+   id="svg2">
+  <defs
+     id="defs49" />
+  <text
+     x="3.7"
+     y="1.9"
+     id="text4"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Grou</text>
+  <text
+     x="3.7"
+     y="2"
+     id="text6"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">group</text>
+  <rect
+     width="9.6000004"
+     height="3"
+     x="3"
+     y="1"
+     id="rect8"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="9.6000004"
+     height="3"
+     x="3"
+     y="1"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="9.5500002"
+     height="3.3"
+     x="3"
+     y="15.4"
+     id="rect12"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="9.5500002"
+     height="3.3"
+     x="3"
+     y="15.4"
+     id="rect14"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="9.5500002"
+     height="3.5"
+     x="3"
+     y="8"
+     id="rect16"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="9.5500002"
+     height="3.5"
+     x="3"
+     y="8"
+     id="rect18"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.75"
+     y="2.05"
+     id="text20"
+     style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">group_mapping tdb</text>
+  <text
+     x="3.6500001"
+     y="3.5"
+     id="text22"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">contains samba groups</text>
+  <text
+     x="5.5999999"
+     y="9.0620003"
+     id="text24"
+     style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">idmap gid</text>
+  <text
+     x="4.25"
+     y="10.25"
+     id="text26"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">maps UNIX groups to</text>
+  <text
+     x="4.25"
+     y="11.05"
+     id="text28"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">samba groups</text>
+  <text
+     x="5.0500002"
+     y="16.5"
+     id="text30"
+     style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">UNIX groups</text>
+  <text
+     x="4.8499999"
+     y="17.6"
+     id="text32"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">/etc/group or other</text>
+  <text
+     x="4.8499999"
+     y="18.4"
+     id="text34"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">NSS backend</text>
+  <polygon
+     points="7.183,6.963 7.183,5.01 6.694,5.01 7.671,4.034 8.647,5.01 8.159,5.01 8.159,6.963 8.647,6.963 7.671,7.939 6.694,6.963 7.183,6.963 "
+     id="polygon36"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="7.183,6.963 7.183,5.01 6.694,5.01 7.671,4.034 8.647,5.01 8.159,5.01 8.159,6.963 8.647,6.963 7.671,7.939 6.694,6.963 7.183,6.963 "
+     id="polygon38"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="7.183,6.963 7.183,5.01 6.694,5.01 7.671,4.034 8.647,5.01 8.159,5.01 8.159,6.963 8.647,6.963 7.671,7.939 6.694,6.963 7.183,6.963 "
+     id="polygon40"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="7.196,14.421 7.196,12.521 6.721,12.521 7.671,11.571 8.621,12.521 8.146,12.521 8.146,14.421 8.621,14.421 7.671,15.371 6.721,14.421 7.196,14.421 "
+     id="polygon42"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="7.196,14.421 7.196,12.521 6.721,12.521 7.671,11.571 8.621,12.521 8.146,12.521 8.146,14.421 8.621,14.421 7.671,15.371 6.721,14.421 7.196,14.421 "
+     id="polygon44"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="7.196,14.421 7.196,12.521 6.721,12.521 7.671,11.571 8.621,12.521 8.146,12.521 8.146,14.421 8.621,14.421 7.671,15.371 6.721,14.421 7.196,14.421 "
+     id="polygon46"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/idmap-sid2gid.svg b/docs-xml/Samba3-HOWTO/images/idmap-sid2gid.svg
new file mode 100644
index 00000000000..95944e9851f
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/idmap-sid2gid.svg
@@ -0,0 +1,277 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="23.674999cm"
+   height="19.329cm"
+   viewBox="-0.492 0 23.184 19.329"
+   id="svg2">
+  <defs
+     id="defs97" />
+  <path
+     d="M 6.333,17.471 L 8.667,17.471 C 8.989,17.471 9.25,17.876 9.25,18.375 C 9.25,18.874 8.989,19.279 8.667,19.279 L 6.333,19.279 C 6.011,19.279 5.75,18.874 5.75,18.375 C 5.75,17.876 6.011,17.471 6.333,17.471"
+     id="path4"
+     style="fill:#dcdcdc;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 6.333,17.471 L 8.667,17.471 C 8.989,17.471 9.25,17.876 9.25,18.375 C 9.25,18.874 8.989,19.279 8.667,19.279 L 6.333,19.279 C 6.011,19.279 5.75,18.874 5.75,18.375 C 5.75,17.876 6.011,17.471 6.333,17.471"
+     id="path6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.7610002"
+     y="18.552"
+     id="text8"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">GID</text>
+  <line
+     x1="4.5019999"
+     y1="6"
+     x2="4.5009999"
+     y2="6.6500001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line10"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.101,6.649 4.5,7.45 4.901,6.651 4.101,6.649 "
+     id="polygon12"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 2.883,0.05 L 6.117,0.05 C 6.564,0.05 6.926,0.678 6.926,1.454 C 6.926,2.229 6.564,2.857 6.117,2.857 L 2.883,2.857 C 2.436,2.857 2.074,2.229 2.074,1.454 C 2.074,0.678 2.436,0.05 2.883,0.05"
+     id="path14"
+     style="fill:#cfcfcf;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 2.883,0.05 L 6.117,0.05 C 6.564,0.05 6.926,0.678 6.926,1.454 C 6.926,2.229 6.564,2.857 6.117,2.857 L 2.883,2.857 C 2.436,2.857 2.074,2.229 2.074,1.454 C 2.074,0.678 2.436,0.05 2.883,0.05"
+     id="path16"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.286"
+     y="1.131"
+     id="text18"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">group</text>
+  <text
+     x="3.799"
+     y="2.131"
+     id="text20"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
+  <path
+     d="M 15.181,12.15 L 17.435,12.15 C 17.746,12.15 17.999,12.555 17.999,13.054 C 17.999,13.553 17.746,13.957 17.435,13.957 L 15.181,13.957 C 14.869,13.957 14.617,13.553 14.617,13.054 C 14.617,12.555 14.869,12.15 15.181,12.15"
+     id="path22"
+     style="fill:#dcdcdc;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 15.181,12.15 L 17.435,12.15 C 17.746,12.15 17.999,12.555 17.999,13.054 C 17.999,13.553 17.746,13.957 17.435,13.957 L 15.181,13.957 C 14.869,13.957 14.617,13.553 14.617,13.054 C 14.617,12.555 14.869,12.15 15.181,12.15"
+     id="path24"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="15.584"
+     y="13.231"
+     id="text26"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Fail</text>
+  <line
+     x1="12.5"
+     y1="13"
+     x2="13.9"
+     y2="13"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line28"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="13.9,13.4 14.7,13 13.9,12.6 13.9,13.4 "
+     id="polygon30"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="10.5,11.5 12.5,13 10.5,14.5 8.5,13 10.5,11.5 "
+     id="polygon32"
+     style="fill:#bef2ff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="10.5,11.5 12.5,13 10.5,14.5 8.5,13 10.5,11.5 "
+     id="polygon34"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="9.0229998"
+     y="13.25"
+     id="text36"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
+  <text
+     x="11.031"
+     y="15.5"
+     id="text38"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
+  <line
+     x1="10.489"
+     y1="10"
+     x2="10.494"
+     y2="10.65"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line40"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="10.094,10.653 10.5,11.45 10.894,10.647 10.094,10.653 "
+     id="polygon42"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="12.604"
+     y="12.75"
+     id="text44"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
+  <line
+     x1="7.5"
+     y1="15.75"
+     x2="7.5"
+     y2="16.65"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="7.1,16.65 7.5,17.45 7.9,16.65 7.1,16.65 "
+     id="polygon48"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.5,7.5 6.5,9 4.5,10.5 2.5,9 4.5,7.5 "
+     id="polygon50"
+     style="fill:#acedff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.5,7.5 6.5,9 4.5,10.5 2.5,9 4.5,7.5 "
+     id="polygon52"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.0220001"
+     y="9.25"
+     id="text54"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
+  <text
+     x="5.0310001"
+     y="11.25"
+     id="text56"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
+  <line
+     x1="4.5"
+     y1="2.8570001"
+     x2="4.5"
+     y2="3.05"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line58"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.1,3.051 4.502,3.85 4.9,3.049 4.1,3.051 "
+     id="polygon60"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="6.6040001"
+     y="8.75"
+     id="text62"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
+  <line
+     x1="6.5"
+     y1="9"
+     x2="7.6500001"
+     y2="9"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line64"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="7.65,9.4 8.45,9 7.65,8.6 7.65,9.4 "
+     id="polygon66"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <rect
+     width="4.4899998"
+     height="2.0999999"
+     x="8.2440004"
+     y="7.9000001"
+     id="rect68"
+     style="fill:#dcdcdc;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4899998"
+     height="2.0999999"
+     x="8.2440004"
+     y="7.9000001"
+     id="rect70"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="8.7939997"
+     y="9.1280003"
+     id="text72"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Winbind</text>
+  <line
+     x1="12.75"
+     y1="9.25"
+     x2="14.75"
+     y2="10"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="12.75"
+     y1="8.75"
+     x2="14.75"
+     y2="8"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line76"
+     style="stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="8"
+     height="2"
+     x="15"
+     y="8"
+     id="rect78"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="8"
+     height="2"
+     x="15"
+     y="8"
+     id="rect80"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="14.816"
+     y="8.75"
+     id="text82"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">winbindd_idmap.tdb</text>
+  <text
+     x="17.261999"
+     y="9.75"
+     id="text84"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
+  <line
+     x1="23"
+     y1="9"
+     x2="15"
+     y2="9"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line86"
+     style="stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="9.8870001"
+     height="2.0999999"
+     x="-0.442"
+     y="3.9000001"
+     id="rect88"
+     style="fill:#d3d3d3;stroke:none;stroke-width:0" />
+  <rect
+     width="9.8870001"
+     height="2.0999999"
+     x="-0.442"
+     y="3.9000001"
+     id="rect90"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.108"
+     y="5.1269999"
+     id="text92"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">groupmap_idmap.tdb</text>
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="4.500,10.500 4.500,15.500 10.500,15.500 10.500,14.500 "
+     id="polyline94"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/idmap-sid2uid.svg b/docs-xml/Samba3-HOWTO/images/idmap-sid2uid.svg
new file mode 100644
index 00000000000..84faf099f61
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/idmap-sid2uid.svg
@@ -0,0 +1,365 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="33.234001cm"
+   height="20.391001cm"
+   viewBox="0.066 0.921 33.3 21.312"
+   id="svg2">
+  <defs
+     id="defs121" />
+  <line
+     x1="12.5"
+     y1="2.779"
+     x2="12.5"
+     y2="4.9000001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line4"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.1,4.9 12.5,5.7 12.9,4.9 12.1,4.9 "
+     id="polygon6"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 11.333,0.971 L 13.667,0.971 C 13.989,0.971 14.25,1.376 14.25,1.875 C 14.25,2.374 13.989,2.779 13.667,2.779 L 11.333,2.779 C 11.011,2.779 10.75,2.374 10.75,1.875 C 10.75,1.376 11.011,0.971 11.333,0.971"
+     id="path8"
+     style="fill:#d9d9d9;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 11.333,0.971 L 13.667,0.971 C 13.989,0.971 14.25,1.376 14.25,1.875 C 14.25,2.374 13.989,2.779 13.667,2.779 L 11.333,2.779 C 11.011,2.779 10.75,2.374 10.75,1.875 C 10.75,1.376 11.011,0.971 11.333,0.971"
+     id="path10"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="11.799"
+     y="2.053"
+     id="text12"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
+  <polygon
+     points="12.5,5.75 15.5,7.75 12.5,9.75 9.5,7.75 12.5,5.75 "
+     id="polygon14"
+     style="fill:#aff3f6;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.5,5.75 15.5,7.75 12.5,9.75 9.5,7.75 12.5,5.75 "
+     id="polygon16"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="9.8459997"
+     y="8"
+     id="text18"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Our Domain?</text>
+  <line
+     x1="15.5"
+     y1="7.75"
+     x2="17.65"
+     y2="7.75"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line20"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="17.65,8.15 18.45,7.75 17.65,7.35 17.65,8.15 "
+     id="polygon22"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="16.031"
+     y="7.5"
+     id="text24"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
+  <line
+     x1="12.5"
+     y1="9.75"
+     x2="12.493"
+     y2="11.55"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line26"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.093,11.548 12.49,12.35 12.893,11.552 12.093,11.548 "
+     id="polygon28"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <text
+     x="12.854"
+     y="10.75"
+     id="text30"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
+  <line
+     x1="16.5"
+     y1="15.25"
+     x2="16.5"
+     y2="17.4"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line32"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="16.1,17.4 16.5,18.2 16.9,17.4 16.1,17.4 "
+     id="polygon34"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 21.833,18.9 L 24.167,18.9 C 24.489,18.9 24.75,19.305 24.75,19.804 C 24.75,20.303 24.489,20.707 24.167,20.707 L 21.833,20.707 C 21.511,20.707 21.25,20.303 21.25,19.804 C 21.25,19.305 21.511,18.9 21.833,18.9"
+     id="path36"
+     style="fill:#d9d9d9;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 21.833,18.9 L 24.167,18.9 C 24.489,18.9 24.75,19.305 24.75,19.804 C 24.75,20.303 24.489,20.707 24.167,20.707 L 21.833,20.707 C 21.511,20.707 21.25,20.303 21.25,19.804 C 21.25,19.305 21.511,18.9 21.833,18.9"
+     id="path38"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="22.264999"
+     y="19.981001"
+     id="text40"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">UID</text>
+  <polygon
+     points="16.5,18.25 18.5,19.75 16.5,21.25 14.5,19.75 16.5,18.25 "
+     id="polygon42"
+     style="fill:#a1fdfb;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="16.5,18.25 18.5,19.75 16.5,21.25 14.5,19.75 16.5,18.25 "
+     id="polygon44"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="15.023"
+     y="20"
+     id="text46"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
+  <text
+     x="18.781"
+     y="19.5"
+     id="text48"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
+  <text
+     x="13.354"
+     y="19.5"
+     id="text50"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
+  <line
+     x1="18.5"
+     y1="19.75"
+     x2="20.4"
+     y2="19.75"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line52"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="20.4,20.15 21.2,19.75 20.4,19.35 20.4,20.15 "
+     id="polygon54"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="14.5"
+     y1="19.75"
+     x2="12.6"
+     y2="19.75"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line56"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.6,19.35 11.8,19.75 12.6,20.15 12.6,19.35 "
+     id="polygon58"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 8.833,18.9 L 11.167,18.9 C 11.489,18.9 11.75,19.305 11.75,19.804 C 11.75,20.303 11.489,20.707 11.167,20.707 L 8.833,20.707 C 8.511,20.707 8.25,20.303 8.25,19.804 C 8.25,19.305 8.511,18.9 8.833,18.9"
+     id="path60"
+     style="fill:#d7d7d7;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 8.833,18.9 L 11.167,18.9 C 11.489,18.9 11.75,19.305 11.75,19.804 C 11.75,20.303 11.489,20.707 11.167,20.707 L 8.833,20.707 C 8.511,20.707 8.25,20.303 8.25,19.804 C 8.25,19.305 8.511,18.9 8.833,18.9"
+     id="path62"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="9.276"
+     y="19.981001"
+     id="text64"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Fail</text>
+  <rect
+     width="4.1399999"
+     height="2.0999999"
+     x="18.419001"
+     y="6.6500001"
+     id="rect66"
+     style="fill:#d9d6d6;stroke:none;stroke-width:0" />
+  <rect
+     width="4.1399999"
+     height="2.0999999"
+     x="18.419001"
+     y="6.6500001"
+     id="rect68"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="18.969"
+     y="7.8779998"
+     id="text70"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">PassDB</text>
+  <line
+     x1="22.75"
+     y1="6.5"
+     x2="25"
+     y2="5.25"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line72"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="22.75"
+     y1="8.75"
+     x2="25"
+     y2="10"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line74"
+     style="stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="8"
+     height="5.25"
+     x="25.25"
+     y="5"
+     id="rect76"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="8"
+     height="5.25"
+     x="25.25"
+     y="5"
+     id="rect78"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="28.089001"
+     y="5.75"
+     id="text80"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">guest</text>
+  <text
+     x="26.85"
+     y="6.75"
+     id="text82"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">smbpasswd</text>
+  <text
+     x="27.709"
+     y="7.75"
+     id="text84"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">tdbsam</text>
+  <text
+     x="27.511999"
+     y="8.75"
+     id="text86"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
+  <text
+     x="25.799999"
+     y="9.75"
+     id="text88"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam_compat</text>
+  <line
+     x1="25.25"
+     y1="6"
+     x2="33.25"
+     y2="6"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line90"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="25.25"
+     y1="7"
+     x2="33.25"
+     y2="7"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line92"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="25.25"
+     y1="8"
+     x2="33.25"
+     y2="8"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line94"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="25.25"
+     y1="9"
+     x2="33.25"
+     y2="9"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line96"
+     style="stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="4.4899998"
+     height="2.0999999"
+     x="10.244"
+     y="12.4"
+     id="rect98"
+     style="fill:#d7d7d7;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4899998"
+     height="2.0999999"
+     x="10.244"
+     y="12.4"
+     id="rect100"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="10.794"
+     y="13.628"
+     id="text102"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Winbind</text>
+  <rect
+     width="7.5"
+     height="2.75"
+     x="0.5"
+     y="12"
+     id="rect104"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="7.5"
+     height="2.75"
+     x="0.5"
+     y="12"
+     id="rect106"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="0.066"
+     y="13"
+     id="text108"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">winbindd_idmap.tdb</text>
+  <text
+     x="2.513"
+     y="14.25"
+     id="text110"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
+  <line
+     x1="8"
+     y1="13.375"
+     x2="0.5"
+     y2="13.375"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line112"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="8.25"
+     y1="12"
+     x2="10.25"
+     y2="12.75"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line114"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="8.25"
+     y1="14.75"
+     x2="10.25"
+     y2="14"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line116"
+     style="stroke:#000000;stroke-width:0.05" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="12.489,14.500 12.489,15.500 20.489,15.500 20.489,8.750 "
+     id="polyline118"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/idmap-store-gid2sid.svg b/docs-xml/Samba3-HOWTO/images/idmap-store-gid2sid.svg
new file mode 100644
index 00000000000..bf155049749
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/idmap-store-gid2sid.svg
@@ -0,0 +1,122 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="26.294001cm"
+   height="2.4000001cm"
+   viewBox="0.45 1.35 26.744 3.75"
+   id="svg2">
+  <defs
+     id="defs41" />
+  <path
+     d="M 13.02,1.721 L 15.23,1.721 C 15.535,1.721 15.782,2.126 15.782,2.625 C 15.782,3.124 15.535,3.529 15.23,3.529 L 13.02,3.529 C 12.715,3.529 12.468,3.124 12.468,2.625 C 12.468,2.126 12.715,1.721 13.02,1.721"
+     id="path4"
+     style="fill:#d7d7d7;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 13.02,1.721 L 15.23,1.721 C 15.535,1.721 15.782,2.126 15.782,2.625 C 15.782,3.124 15.535,3.529 15.23,3.529 L 13.02,3.529 C 12.715,3.529 12.468,3.124 12.468,2.625 C 12.468,2.126 12.715,1.721 13.02,1.721"
+     id="path6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="13.424"
+     y="2.803"
+     id="text8"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
+  <path
+     d="M 1.083,1.65 L 3.417,1.65 C 3.739,1.65 4,2.055 4,2.554 C 4,3.053 3.739,3.457 3.417,3.457 L 1.083,3.457 C 0.761,3.457 0.5,3.053 0.5,2.554 C 0.5,2.055 0.761,1.65 1.083,1.65"
+     id="path10"
+     style="fill:#d7d7d7;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 1.083,1.65 L 3.417,1.65 C 3.739,1.65 4,2.055 4,2.554 C 4,3.053 3.739,3.457 3.417,3.457 L 1.083,3.457 C 0.761,3.457 0.5,3.053 0.5,2.554 C 0.5,2.055 0.761,1.65 1.083,1.65"
+     id="path12"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="1.511"
+     y="2.7309999"
+     id="text14"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">GID</text>
+  <line
+     x1="16"
+     y1="3"
+     x2="18"
+     y2="3.5"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="16"
+     y1="2"
+     x2="18"
+     y2="1.5"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="4"
+     y1="2.5539999"
+     x2="11.65"
+     y2="2.618"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line20"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="11.647,3.018 12.45,2.625 11.653,2.218 11.647,3.018 "
+     id="polygon22"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <rect
+     width="6.9219999"
+     height="2.0999999"
+     x="4.572"
+     y="1.4"
+     id="rect24"
+     style="fill:#d7d7d7;stroke:none;stroke-width:0" />
+  <rect
+     width="6.9219999"
+     height="2.0999999"
+     x="4.572"
+     y="1.4"
+     id="rect26"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="5.1220002"
+     y="2.6270001"
+     id="text28"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">net groupmap</text>
+  <rect
+     width="8.1999998"
+     height="2.2"
+     x="18.25"
+     y="1.5"
+     id="rect30"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="8.1999998"
+     height="2.2"
+     x="18.25"
+     y="1.5"
+     id="rect32"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="20.511999"
+     y="2.25"
+     id="text34"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
+  <text
+     x="17.955999"
+     y="3.2"
+     id="text36"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">groupmap_idmap.tdb</text>
+  <line
+     x1="26.549999"
+     y1="2.45"
+     x2="18.35"
+     y2="2.45"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line38"
+     style="stroke:#000000;stroke-width:0.05" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/idmap-uid2sid.svg b/docs-xml/Samba3-HOWTO/images/idmap-uid2sid.svg
new file mode 100644
index 00000000000..13aca9cf703
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/idmap-uid2sid.svg
@@ -0,0 +1,365 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="21.431cm"
+   height="23.086cm"
+   viewBox="10.369 0.921 31.8 24.007"
+   id="svg2">
+  <defs
+     id="defs121" />
+  <line
+     x1="19.25"
+     y1="12.75"
+     x2="19.25"
+     y2="14.15"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line4"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="18.85,14.15 19.25,14.95 19.65,14.15 18.85,14.15 "
+     id="polygon6"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="12.5"
+     y1="2.779"
+     x2="12.5"
+     y2="4.6500001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line8"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.1,4.65 12.5,5.45 12.9,4.65 12.1,4.65 "
+     id="polygon10"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 11.333,0.971 L 13.667,0.971 C 13.989,0.971 14.25,1.376 14.25,1.875 C 14.25,2.374 13.989,2.779 13.667,2.779 L 11.333,2.779 C 11.011,2.779 10.75,2.374 10.75,1.875 C 10.75,1.376 11.011,0.971 11.333,0.971"
+     id="path12"
+     style="fill:#dcdcdc;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 11.333,0.971 L 13.667,0.971 C 13.989,0.971 14.25,1.376 14.25,1.875 C 14.25,2.374 13.989,2.779 13.667,2.779 L 11.333,2.779 C 11.011,2.779 10.75,2.374 10.75,1.875 C 10.75,1.376 11.011,0.971 11.333,0.971"
+     id="path14"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="11.765"
+     y="2.053"
+     id="text16"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">UID</text>
+  <line
+     x1="12.489"
+     y1="7.5"
+     x2="12.497"
+     y2="9.6499996"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line18"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="12.097,9.651 12.5,10.45 12.897,9.649 12.097,9.651 "
+     id="polygon20"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 14.833,22.15 L 17.167,22.15 C 17.489,22.15 17.75,22.555 17.75,23.054 C 17.75,23.553 17.489,23.957 17.167,23.957 L 14.833,23.957 C 14.511,23.957 14.25,23.553 14.25,23.054 C 14.25,22.555 14.511,22.15 14.833,22.15"
+     id="path22"
+     style="fill:#d5d5d5;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 14.833,22.15 L 17.167,22.15 C 17.489,22.15 17.75,22.555 17.75,23.054 C 17.75,23.553 17.489,23.957 17.167,23.957 L 14.833,23.957 C 14.511,23.957 14.25,23.553 14.25,23.054 C 14.25,22.555 14.511,22.15 14.833,22.15"
+     id="path24"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="15.299"
+     y="23.231001"
+     id="text26"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
+  <polygon
+     points="12.5,10.5 14.5,12 12.5,13.5 10.5,12 12.5,10.5 "
+     id="polygon28"
+     style="fill:#b8f5fc;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="12.5,10.5 14.5,12 12.5,13.5 10.5,12 12.5,10.5 "
+     id="polygon30"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="11.023"
+     y="12.25"
+     id="text32"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
+  <text
+     x="13.031"
+     y="14.5"
+     id="text34"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
+  <text
+     x="14.854"
+     y="11.75"
+     id="text36"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
+  <line
+     x1="14.5"
+     y1="12"
+     x2="16.4"
+     y2="12"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line38"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="16.4,12.4 17.2,12 16.4,11.6 16.4,12.4 "
+     id="polygon40"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <line
+     x1="16"
+     y1="19.25"
+     x2="16"
+     y2="21.4"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line42"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="15.6,21.4 16,22.2 16.4,21.4 15.6,21.4 "
+     id="polygon44"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 24.083,15.65 L 26.417,15.65 C 26.739,15.65 27,16.055 27,16.554 C 27,17.053 26.739,17.457 26.417,17.457 L 24.083,17.457 C 23.761,17.457 23.5,17.053 23.5,16.554 C 23.5,16.055 23.761,15.65 24.083,15.65"
+     id="path46"
+     style="fill:#d9d9d9;stroke:none;stroke-width:0.1" />
+  <path
+     d="M 24.083,15.65 L 26.417,15.65 C 26.739,15.65 27,16.055 27,16.554 C 27,17.053 26.739,17.457 26.417,17.457 L 24.083,17.457 C 23.761,17.457 23.5,17.053 23.5,16.554 C 23.5,16.055 23.761,15.65 24.083,15.65"
+     id="path48"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="24.525999"
+     y="16.731001"
+     id="text50"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Fail</text>
+  <rect
+     width="4.1399999"
+     height="2.0999999"
+     x="10.419"
+     y="5.4000001"
+     id="rect52"
+     style="fill:#dcd7d7;stroke:none;stroke-width:0" />
+  <rect
+     width="4.1399999"
+     height="2.0999999"
+     x="10.419"
+     y="5.4000001"
+     id="rect54"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="10.969"
+     y="6.6279998"
+     id="text56"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">PassDB</text>
+  <line
+     x1="14.75"
+     y1="5.25"
+     x2="17"
+     y2="4"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line58"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="14.75"
+     y1="7.5"
+     x2="17"
+     y2="8.75"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line60"
+     style="stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="8"
+     height="5.25"
+     x="17.25"
+     y="3.75"
+     id="rect62"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="8"
+     height="5.25"
+     x="17.25"
+     y="3.75"
+     id="rect64"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="20.089001"
+     y="4.5"
+     id="text66"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">guest</text>
+  <text
+     x="18.85"
+     y="5.5"
+     id="text68"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">smbpasswd</text>
+  <text
+     x="19.709"
+     y="6.5"
+     id="text70"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">tdbsam</text>
+  <text
+     x="19.511999"
+     y="7.5"
+     id="text72"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
+  <text
+     x="17.799999"
+     y="8.5"
+     id="text74"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam_compat</text>
+  <line
+     x1="17.25"
+     y1="4.75"
+     x2="25.25"
+     y2="4.75"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line76"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="17.25"
+     y1="5.75"
+     x2="25.25"
+     y2="5.75"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line78"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="17.25"
+     y1="6.75"
+     x2="25.25"
+     y2="6.75"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line80"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="17.25"
+     y1="7.75"
+     x2="25.25"
+     y2="7.75"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line82"
+     style="stroke:#000000;stroke-width:0.05" />
+  <polyline
+     fill="none"
+     stroke="#000000"
+     stroke-width="0.100"
+     points="12.500,13.500 12.500,19.000 19.250,19.000 19.250,18.000 "
+     id="polyline84"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="4.4899998"
+     height="2.0999999"
+     x="16.993999"
+     y="10.9"
+     id="rect86"
+     style="fill:#d7d7d7;stroke:none;stroke-width:0" />
+  <rect
+     width="4.4899998"
+     height="2.0999999"
+     x="16.993999"
+     y="10.9"
+     id="rect88"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="17.544001"
+     y="12.128"
+     id="text90"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Winbind</text>
+  <line
+     x1="21.5"
+     y1="12.5"
+     x2="23.5"
+     y2="13.25"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line92"
+     style="stroke:#000000;stroke-width:0.05" />
+  <line
+     x1="21.5"
+     y1="11.25"
+     x2="23.5"
+     y2="10.5"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line94"
+     style="stroke:#000000;stroke-width:0.05" />
+  <rect
+     width="7.6669998"
+     height="2.75"
+     x="23.75"
+     y="10.5"
+     id="rect96"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="7.6669998"
+     height="2.75"
+     x="23.75"
+     y="10.5"
+     id="rect98"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="23.433001"
+     y="11.507"
+     id="text100"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">winbindd_idmap.tdb</text>
+  <text
+     x="25.761999"
+     y="12.75"
+     id="text102"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
+  <line
+     x1="31.417"
+     y1="11.875"
+     x2="23.75"
+     y2="11.875"
+     stroke="#000000"
+     stroke-width="0.050"
+     id="line104"
+     style="stroke:#000000;stroke-width:0.05" />
+  <polygon
+     points="19.25,15 21.25,16.5 19.25,18 17.25,16.5 19.25,15 "
+     id="polygon106"
+     style="fill:#bcf9ff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="19.25,15 21.25,16.5 19.25,18 17.25,16.5 19.25,15 "
+     id="polygon108"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="17.773001"
+     y="16.75"
+     id="text110"
+     style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
+  <text
+     x="19.781"
+     y="19"
+     id="text112"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
+  <text
+     x="21.604"
+     y="16.25"
+     id="text114"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
+  <line
+     x1="21.25"
+     y1="16.5"
+     x2="22.65"
+     y2="16.5"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line116"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="22.65,16.9 23.45,16.5 22.65,16.1 22.65,16.9 "
+     id="polygon118"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/idmap.svg b/docs-xml/Samba3-HOWTO/images/idmap.svg
new file mode 100644
index 00000000000..db2d883551d
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/idmap.svg
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="8.1999998cm"
+   height="17.198cm"
+   viewBox="1.45 1.4 9.65 18.598"
+   id="svg2">
+  <defs
+     id="defs45" />
+  <rect
+     width="7.3000002"
+     height="2.5999999"
+     x="1.5"
+     y="1.7"
+     id="rect4"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="7.3000002"
+     height="2.5999999"
+     x="1.5"
+     y="1.7"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="5.9000001"
+     height="2.7"
+     x="2.3"
+     y="8.5"
+     id="rect8"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="5.9000001"
+     height="2.7"
+     x="2.3"
+     y="8.5"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="2.7"
+     y="2.8"
+     id="text12"
+     style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">passdb backend</text>
+  <text
+     x="1.7"
+     y="3.7"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">contains samba users</text>
+  <text
+     x="4.5"
+     y="9.3999996"
+     id="text16"
+     style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">idmap</text>
+  <text
+     x="3.3"
+     y="10.2"
+     id="text18"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">maps unix to</text>
+  <text
+     x="3.3"
+     y="11"
+     id="text20"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">samba users</text>
+  <rect
+     width="7.6999998"
+     height="3"
+     x="1.9"
+     y="15.5"
+     id="rect22"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="7.6999998"
+     height="3"
+     x="1.9"
+     y="15.5"
+     id="rect24"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.675,7.35 4.675,5.45 4.2,5.45 5.15,4.5 6.1,5.45 5.625,5.45 5.625,7.35 6.1,7.35 5.15,8.3 4.2,7.35 4.675,7.35 "
+     id="polygon26"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.675,7.35 4.675,5.45 4.2,5.45 5.15,4.5 6.1,5.45 5.625,5.45 5.625,7.35 6.1,7.35 5.15,8.3 4.2,7.35 4.675,7.35 "
+     id="polygon28"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.675,7.35 4.675,5.45 4.2,5.45 5.15,4.5 6.1,5.45 5.625,5.45 5.625,7.35 6.1,7.35 5.15,8.3 4.2,7.35 4.675,7.35 "
+     id="polygon30"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="4.763,14.175 4.763,12.325 4.3,12.325 5.225,11.4 6.15,12.325 5.688,12.325 5.688,14.175 6.15,14.175 5.225,15.1 4.3,14.175 4.763,14.175 "
+     id="polygon32"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.763,14.175 4.763,12.325 4.3,12.325 5.225,11.4 6.15,12.325 5.688,12.325 5.688,14.175 6.15,14.175 5.225,15.1 4.3,14.175 4.763,14.175 "
+     id="polygon34"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.763,14.175 4.763,12.325 4.3,12.325 5.225,11.4 6.15,12.325 5.688,12.325 5.688,14.175 6.15,14.175 5.225,15.1 4.3,14.175 4.763,14.175 "
+     id="polygon36"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="3.7"
+     y="16.299999"
+     id="text38"
+     style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">Unix users</text>
+  <text
+     x="2.4000001"
+     y="17.4"
+     id="text40"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">/etc/passwd</text>
+  <text
+     x="2.4000001"
+     y="18.200001"
+     id="text42"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">or other NSS backend</text>
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/idmap_winbind_no_loop.png b/docs-xml/Samba3-HOWTO/images/idmap_winbind_no_loop.png
new file mode 100644
index 00000000000..5393f6a1925
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/idmap_winbind_no_loop.png
diff --git a/docs-xml/Samba3-HOWTO/images/pdftoepsonusb.svg b/docs-xml/Samba3-HOWTO/images/pdftoepsonusb.svg
new file mode 100644
index 00000000000..d9434d7e26f
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/pdftoepsonusb.svg
@@ -0,0 +1,156 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="18.5cm"
+   height="4.9990001cm"
+   viewBox="5.85 2.808 24.35 7.807"
+   id="svg2">
+  <defs
+     id="defs59" />
+  <rect
+     width="4.0999999"
+     height="1"
+     x="5.9000001"
+     y="3"
+     id="rect4"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.0999999"
+     height="1"
+     x="5.9000001"
+     y="3"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.8039999"
+     y="3.8"
+     id="text8"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pdftops</text>
+  <rect
+     width="4.0999999"
+     height="1"
+     x="12.8"
+     y="3"
+     id="rect10"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.0999999"
+     height="1"
+     x="12.8"
+     y="3"
+     id="rect12"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="13.835"
+     y="3.8"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstops</text>
+  <rect
+     width="4.0999999"
+     height="1"
+     x="19.9"
+     y="3"
+     id="rect16"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.7609506"
+     height="0.99263805"
+     x="19.903681"
+     y="3.0036809"
+     id="rect18"
+     style="fill:none;stroke:#000000;stroke-width:0.10736195" />
+  <text
+     x="20.409"
+     y="3.8"
+     id="text20"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstoraster</text>
+  <polygon
+     points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
+     id="polygon22"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
+     id="polygon24"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
+     id="polygon26"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
+     id="polygon28"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
+     id="polygon30"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
+     id="polygon32"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="4.8000002"
+     height="1"
+     x="19.5"
+     y="6.3000002"
+     id="rect34"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="6.0224352"
+     height="0.9886266"
+     x="19.505686"
+     y="6.305687"
+     id="rect36"
+     style="fill:none;stroke:#000000;stroke-width:0.11137342" />
+  <text
+     x="19.865999"
+     y="7.0999999"
+     id="text38"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">rastertoepson</text>
+  <polygon
+     points="21.6,4.4 21.6,5.2 21.2,5.2 22,6 22.8,5.2 22.4,5.2 22.4,4.4 21.6,4.4 "
+     id="polygon40"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="21.6,4.4 21.6,5.2 21.2,5.2 22,6 22.8,5.2 22.4,5.2 22.4,4.4 21.6,4.4 "
+     id="polygon42"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="21.6,4.4 21.6,5.2 21.2,5.2 22,6 22.8,5.2 22.4,5.2 22.4,4.4 21.6,4.4 "
+     id="polygon44"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="4.0999999"
+     height="1"
+     x="12.5"
+     y="6.3000002"
+     id="rect46"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.0999999"
+     height="1"
+     x="12.5"
+     y="6.3000002"
+     id="rect48"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="13.979"
+     y="7.0999999"
+     id="text50"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">usb</text>
+  <polygon
+     points="18.886,6.422 18.043,6.422 18.043,6 17.2,6.843 18.043,7.686 18.043,7.265 18.886,7.265 18.886,6.422 "
+     id="polygon52"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="18.886,6.422 18.043,6.422 18.043,6 17.2,6.843 18.043,7.686 18.043,7.265 18.886,7.265 18.886,6.422 "
+     id="polygon54"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="18.886,6.422 18.043,6.422 18.043,6 17.2,6.843 18.043,7.686 18.043,7.265 18.886,7.265 18.886,6.422 "
+     id="polygon56"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/pdftosocket.svg b/docs-xml/Samba3-HOWTO/images/pdftosocket.svg
new file mode 100644
index 00000000000..1c9732c3d2e
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/pdftosocket.svg
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="18.200001cm"
+   height="1.484cm"
+   viewBox="5.85 2.808 24.05 4.292"
+   id="svg2">
+  <defs
+     id="defs35" />
+  <rect
+     width="4.0999999"
+     height="1"
+     x="5.9000001"
+     y="3"
+     id="rect4"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.0999999"
+     height="1"
+     x="5.9000001"
+     y="3"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="6.8039999"
+     y="3.8"
+     id="text8"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pdftops</text>
+  <rect
+     width="4.0999999"
+     height="1"
+     x="12.8"
+     y="3"
+     id="rect10"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.0999999"
+     height="1"
+     x="12.8"
+     y="3"
+     id="rect12"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="13.835"
+     y="3.8"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstops</text>
+  <rect
+     width="4.0999999"
+     height="1"
+     x="19.9"
+     y="3"
+     id="rect16"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="4.0999999"
+     height="1"
+     x="19.9"
+     y="3"
+     id="rect18"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="20.959"
+     y="3.8"
+     id="text20"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">socket</text>
+  <polygon
+     points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
+     id="polygon22"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
+     id="polygon24"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
+     id="polygon26"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
+     id="polygon28"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
+     id="polygon30"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
+     id="polygon32"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/trusts1.svg b/docs-xml/Samba3-HOWTO/images/trusts1.svg
new file mode 100644
index 00000000000..9845d493cfc
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/trusts1.svg
@@ -0,0 +1,792 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="27.1cm"
+   height="8.493cm"
+   viewBox="6.95 1.958 34.05 10.45"
+   id="svg2">
+  <defs
+     id="defs273" />
+  <rect
+     width="1.367"
+     height="3.1900001"
+     x="8.8730001"
+     y="5"
+     id="rect4"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.367"
+     height="3.1900001"
+     x="8.8730001"
+     y="5"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.094"
+     height="0.36500001"
+     x="9.0100002"
+     y="5.191"
+     id="rect8"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.094"
+     height="0.36500001"
+     x="9.0100002"
+     y="5.5560002"
+     id="rect10"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.094"
+     height="0.36500001"
+     x="9.0100002"
+     y="5.921"
+     id="rect12"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.094"
+     height="0.36500001"
+     x="9.0100002"
+     y="6.2849998"
+     id="rect14"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.68400002"
+     height="0.219"
+     x="9.0100002"
+     y="6.723"
+     id="rect16"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="10.036"
+     cy="6.7589998"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse18"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="10.036"
+     cy="6.7589998"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse20"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="10.036"
+     cy="6.9050002"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse22"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="10.036"
+     cy="6.9050002"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse24"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.164"
+     height="0.146"
+     x="9.7620001"
+     y="6.796"
+     id="rect26"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.164"
+     height="0.146"
+     x="9.7620001"
+     y="6.796"
+     id="rect28"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.101,7.233 L 9.101,8.031"
+     id="path30"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.329,7.233 L 9.329,8.031"
+     id="path32"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.557,7.233 L 9.557,8.031"
+     id="path34"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 9.785,7.233 L 9.785,8.031"
+     id="path36"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.013,7.233 L 10.013,8.031"
+     id="path38"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 10.241,7.233 L 10.241,8.031"
+     id="path40"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="8.6,8.464 8.873,7.917 8.873,8.19 10.241,8.19 10.241,7.917 10.605,8.464 8.6,8.464 "
+     id="polygon42"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="8.6,8.464 8.873,7.917 8.873,8.19 10.241,8.19 10.241,7.917 10.605,8.464 8.6,8.464 "
+     id="polygon44"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="12.25"
+     cy="6.6999998"
+     rx="5.25"
+     ry="3.5999999"
+     id="ellipse46"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.365"
+     height="3.1860001"
+     x="11.273"
+     y="5"
+     id="rect48"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.365"
+     height="3.1860001"
+     x="11.273"
+     y="5"
+     id="rect50"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.092"
+     height="0.36399999"
+     x="11.41"
+     y="5.191"
+     id="rect52"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.092"
+     height="0.36399999"
+     x="11.41"
+     y="5.5549998"
+     id="rect54"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.092"
+     height="0.36399999"
+     x="11.41"
+     y="5.9190001"
+     id="rect56"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.092"
+     height="0.36399999"
+     x="11.41"
+     y="6.2839999"
+     id="rect58"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.68300003"
+     height="0.21799999"
+     x="11.41"
+     y="6.7199998"
+     id="rect60"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="12.434"
+     cy="6.757"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse62"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="12.434"
+     cy="6.757"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse64"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="12.434"
+     cy="6.902"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse66"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="12.434"
+     cy="6.902"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse68"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.164"
+     height="0.146"
+     x="12.161"
+     y="6.7930002"
+     id="rect70"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.164"
+     height="0.146"
+     x="12.161"
+     y="6.7930002"
+     id="rect72"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 11.501,7.23 L 11.501,8.027"
+     id="path74"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 11.728,7.23 L 11.728,8.027"
+     id="path76"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 11.956,7.23 L 11.956,8.027"
+     id="path78"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 12.183,7.23 L 12.183,8.027"
+     id="path80"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 12.411,7.23 L 12.411,8.027"
+     id="path82"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 12.639,7.23 L 12.639,8.027"
+     id="path84"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="11,8.459 11.273,7.913 11.273,8.186 12.639,8.186 12.639,7.913 13.003,8.459 11,8.459 "
+     id="polygon86"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="11,8.459 11.273,7.913 11.273,8.186 12.639,8.186 12.639,7.913 13.003,8.459 11,8.459 "
+     id="polygon88"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.322"
+     height="3.086"
+     x="13.764"
+     y="5.0999999"
+     id="rect90"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.322"
+     height="3.086"
+     x="13.764"
+     y="5.0999999"
+     id="rect92"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.058"
+     height="0.35299999"
+     x="13.897"
+     y="5.2849998"
+     id="rect94"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.058"
+     height="0.35299999"
+     x="13.897"
+     y="5.638"
+     id="rect96"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.058"
+     height="0.35299999"
+     x="13.897"
+     y="5.9899998"
+     id="rect98"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.058"
+     height="0.35299999"
+     x="13.897"
+     y="6.3429999"
+     id="rect100"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66100001"
+     height="0.212"
+     x="13.897"
+     y="6.7659998"
+     id="rect102"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="14.888"
+     cy="6.8010001"
+     rx="0.046"
+     ry="0.046"
+     id="ellipse104"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="14.888"
+     cy="6.8010001"
+     rx="0.046"
+     ry="0.046"
+     id="ellipse106"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="14.888"
+     cy="6.9419999"
+     rx="0.046"
+     ry="0.046"
+     id="ellipse108"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="14.888"
+     cy="6.9419999"
+     rx="0.046"
+     ry="0.046"
+     id="ellipse110"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.15899999"
+     height="0.141"
+     x="14.624"
+     y="6.8369999"
+     id="rect112"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.15899999"
+     height="0.141"
+     x="14.624"
+     y="6.8369999"
+     id="rect114"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 13.985,7.26 L 13.985,8.031"
+     id="path116"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 14.205,7.26 L 14.205,8.031"
+     id="path118"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 14.426,7.26 L 14.426,8.031"
+     id="path120"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 14.646,7.26 L 14.646,8.031"
+     id="path122"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 14.866,7.26 L 14.866,8.031"
+     id="path124"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 15.087,7.26 L 15.087,8.031"
+     id="path126"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="13.5,8.45 13.764,7.921 13.764,8.186 15.087,8.186 15.087,7.921 15.439,8.45 13.5,8.45 "
+     id="polygon128"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="13.5,8.45 13.764,7.921 13.764,8.186 15.087,8.186 15.087,7.921 15.439,8.45 13.5,8.45 "
+     id="polygon130"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="10.5"
+     y="2.5"
+     id="text132"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Domain A</text>
+  <text
+     x="27.299999"
+     y="2.8"
+     id="text134"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Domain B</text>
+  <polygon
+     points="18.5,6.5 20.6,6.5 20.6,6.2 22.7,6.8 20.6,7.4 20.6,7.1 18.5,7.1 18.5,6.5 "
+     id="polygon136"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="18.5,6.5 20.6,6.5 20.6,6.2 22.7,6.8 20.6,7.4 20.6,7.1 18.5,7.1 18.5,6.5 "
+     id="polygon138"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="18.5,6.5 20.6,6.5 20.6,6.2 22.7,6.8 20.6,7.4 20.6,7.1 18.5,7.1 18.5,6.5 "
+     id="polygon140"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <text
+     x="19.299999"
+     y="5.9000001"
+     id="text142"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Trusts</text>
+  <rect
+     width="1.367"
+     height="3.1900001"
+     x="25.372999"
+     y="5.0999999"
+     id="rect144"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.367"
+     height="3.1900001"
+     x="25.372999"
+     y="5.0999999"
+     id="rect146"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.094"
+     height="0.36500001"
+     x="25.51"
+     y="5.2909999"
+     id="rect148"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.094"
+     height="0.36500001"
+     x="25.51"
+     y="5.6560001"
+     id="rect150"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.094"
+     height="0.36500001"
+     x="25.51"
+     y="6.0209999"
+     id="rect152"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.094"
+     height="0.36500001"
+     x="25.51"
+     y="6.3850002"
+     id="rect154"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.68400002"
+     height="0.219"
+     x="25.51"
+     y="6.823"
+     id="rect156"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="26.535999"
+     cy="6.8590002"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse158"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="26.535999"
+     cy="6.8590002"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse160"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="26.535999"
+     cy="7.0050001"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse162"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="26.535999"
+     cy="7.0050001"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse164"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.164"
+     height="0.146"
+     x="26.261999"
+     y="6.8959999"
+     id="rect166"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.164"
+     height="0.146"
+     x="26.261999"
+     y="6.8959999"
+     id="rect168"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 25.601,7.333 L 25.601,8.131"
+     id="path170"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 25.829,7.333 L 25.829,8.131"
+     id="path172"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 26.057,7.333 L 26.057,8.131"
+     id="path174"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 26.285,7.333 L 26.285,8.131"
+     id="path176"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 26.513,7.333 L 26.513,8.131"
+     id="path178"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 26.741,7.333 L 26.741,8.131"
+     id="path180"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="25.1,8.564 25.373,8.017 25.373,8.29 26.741,8.29 26.741,8.017 27.105,8.564 25.1,8.564 "
+     id="polygon182"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="25.1,8.564 25.373,8.017 25.373,8.29 26.741,8.29 26.741,8.017 27.105,8.564 25.1,8.564 "
+     id="polygon184"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="28.75"
+     cy="6.8000002"
+     rx="5.25"
+     ry="3.5999999"
+     id="ellipse186"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="1.365"
+     height="3.1860001"
+     x="27.773001"
+     y="5.0999999"
+     id="rect188"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.365"
+     height="3.1860001"
+     x="27.773001"
+     y="5.0999999"
+     id="rect190"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.092"
+     height="0.36399999"
+     x="27.91"
+     y="5.2909999"
+     id="rect192"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.092"
+     height="0.36399999"
+     x="27.91"
+     y="5.6550002"
+     id="rect194"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.092"
+     height="0.36399999"
+     x="27.91"
+     y="6.0190001"
+     id="rect196"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.092"
+     height="0.36399999"
+     x="27.91"
+     y="6.3839998"
+     id="rect198"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.68300003"
+     height="0.21799999"
+     x="27.91"
+     y="6.8200002"
+     id="rect200"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="28.934"
+     cy="6.8569999"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse202"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="28.934"
+     cy="6.8569999"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse204"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="28.934"
+     cy="7.0019999"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse206"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="28.934"
+     cy="7.0019999"
+     rx="0.048"
+     ry="0.048"
+     id="ellipse208"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.164"
+     height="0.146"
+     x="28.660999"
+     y="6.8930001"
+     id="rect210"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.164"
+     height="0.146"
+     x="28.660999"
+     y="6.8930001"
+     id="rect212"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 28.001,7.33 L 28.001,8.127"
+     id="path214"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 28.228,7.33 L 28.228,8.127"
+     id="path216"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 28.456,7.33 L 28.456,8.127"
+     id="path218"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 28.683,7.33 L 28.683,8.127"
+     id="path220"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 28.911,7.33 L 28.911,8.127"
+     id="path222"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 29.139,7.33 L 29.139,8.127"
+     id="path224"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="27.5,8.559 27.773,8.013 27.773,8.286 29.139,8.286 29.139,8.013 29.503,8.559 27.5,8.559 "
+     id="polygon226"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="27.5,8.559 27.773,8.013 27.773,8.286 29.139,8.286 29.139,8.013 29.503,8.559 27.5,8.559 "
+     id="polygon228"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.322"
+     height="3.086"
+     x="30.264"
+     y="5.1999998"
+     id="rect230"
+     style="fill:#b3b3b3;stroke:none;stroke-width:0" />
+  <rect
+     width="1.322"
+     height="3.086"
+     x="30.264"
+     y="5.1999998"
+     id="rect232"
+     style="fill:none;stroke:#000000;stroke-width:0.08" />
+  <rect
+     width="1.058"
+     height="0.35299999"
+     x="30.396999"
+     y="5.3850002"
+     id="rect234"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.058"
+     height="0.35299999"
+     x="30.396999"
+     y="5.7379999"
+     id="rect236"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.058"
+     height="0.35299999"
+     x="30.396999"
+     y="6.0900002"
+     id="rect238"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="1.058"
+     height="0.35299999"
+     x="30.396999"
+     y="6.4429998"
+     id="rect240"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.66100001"
+     height="0.212"
+     x="30.396999"
+     y="6.8660002"
+     id="rect242"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="31.388"
+     cy="6.901"
+     rx="0.046"
+     ry="0.046"
+     id="ellipse244"
+     style="fill:#00ff00;stroke:none" />
+  <ellipse
+     cx="31.388"
+     cy="6.901"
+     rx="0.046"
+     ry="0.046"
+     id="ellipse246"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <ellipse
+     cx="31.388"
+     cy="7.0430002"
+     rx="0.046"
+     ry="0.046"
+     id="ellipse248"
+     style="fill:#ffff00;stroke:none" />
+  <ellipse
+     cx="31.388"
+     cy="7.0430002"
+     rx="0.046"
+     ry="0.046"
+     id="ellipse250"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <rect
+     width="0.15899999"
+     height="0.141"
+     x="31.124001"
+     y="6.9369998"
+     id="rect252"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="0.15899999"
+     height="0.141"
+     x="31.124001"
+     y="6.9369998"
+     id="rect254"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 30.485,7.36 L 30.485,8.131"
+     id="path256"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 30.705,7.36 L 30.705,8.131"
+     id="path258"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 30.926,7.36 L 30.926,8.131"
+     id="path260"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 31.146,7.36 L 31.146,8.131"
+     id="path262"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 31.366,7.36 L 31.366,8.131"
+     id="path264"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <path
+     d="M 31.587,7.36 L 31.587,8.131"
+     id="path266"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+  <polygon
+     points="30,8.55 30.264,8.021 30.264,8.286 31.587,8.286 31.587,8.021 31.939,8.55 30,8.55 "
+     id="polygon268"
+     style="fill:#999999;stroke:none;stroke-width:0.01" />
+  <polygon
+     points="30,8.55 30.264,8.021 30.264,8.286 31.587,8.286 31.587,8.021 31.939,8.55 30,8.55 "
+     id="polygon270"
+     style="fill:none;stroke:#000000;stroke-width:0.01" />
+</svg>
diff --git a/docs-xml/Samba3-HOWTO/images/w2kp001.png b/docs-xml/Samba3-HOWTO/images/w2kp001.png
new file mode 100644
index 00000000000..43adf234637
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/w2kp001.png
diff --git a/docs-xml/Samba3-HOWTO/images/w2kp002.png b/docs-xml/Samba3-HOWTO/images/w2kp002.png
new file mode 100644
index 00000000000..13bb029f537
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/w2kp002.png
diff --git a/docs-xml/Samba3-HOWTO/images/w2kp003.png b/docs-xml/Samba3-HOWTO/images/w2kp003.png
new file mode 100644
index 00000000000..c7b779900e9
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/w2kp003.png
diff --git a/docs-xml/Samba3-HOWTO/images/w2kp004.png b/docs-xml/Samba3-HOWTO/images/w2kp004.png
new file mode 100644
index 00000000000..d0e005a36e6
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/w2kp004.png
diff --git a/docs-xml/Samba3-HOWTO/images/w2kp005.png b/docs-xml/Samba3-HOWTO/images/w2kp005.png
new file mode 100644
index 00000000000..a729b40cd7b
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/w2kp005.png
diff --git a/docs-xml/Samba3-HOWTO/images/w2kp006.png b/docs-xml/Samba3-HOWTO/images/w2kp006.png
new file mode 100644
index 00000000000..ea96db055ab
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/w2kp006.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp001.png b/docs-xml/Samba3-HOWTO/images/wxpp001.png
new file mode 100644
index 00000000000..2e689a17e25
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp001.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp004.png b/docs-xml/Samba3-HOWTO/images/wxpp004.png
new file mode 100644
index 00000000000..656f67942e3
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp004.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp006.png b/docs-xml/Samba3-HOWTO/images/wxpp006.png
new file mode 100644
index 00000000000..a20b3ed5836
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp006.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp007.png b/docs-xml/Samba3-HOWTO/images/wxpp007.png
new file mode 100644
index 00000000000..cf413522208
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp007.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp008.png b/docs-xml/Samba3-HOWTO/images/wxpp008.png
new file mode 100644
index 00000000000..9958c7c873a
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp008.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp010.png b/docs-xml/Samba3-HOWTO/images/wxpp010.png
new file mode 100644
index 00000000000..068a0dfc733
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp010.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp011.png b/docs-xml/Samba3-HOWTO/images/wxpp011.png
new file mode 100644
index 00000000000..0cf88c04a6c
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp011.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp012.png b/docs-xml/Samba3-HOWTO/images/wxpp012.png
new file mode 100644
index 00000000000..d89f3b5d31b
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp012.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp013.png b/docs-xml/Samba3-HOWTO/images/wxpp013.png
new file mode 100644
index 00000000000..451240ee383
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp013.png
diff --git a/docs-xml/Samba3-HOWTO/images/wxpp015.png b/docs-xml/Samba3-HOWTO/images/wxpp015.png
new file mode 100644
index 00000000000..12fe2f31b26
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/images/wxpp015.png
diff --git a/docs-xml/Samba3-HOWTO/index.xml b/docs-xml/Samba3-HOWTO/index.xml
new file mode 100644
index 00000000000..1253b0352e0
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/index.xml
@@ -0,0 +1,237 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE book PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<book id="Samba-HOWTO-Collection"
+	xmlns:xi="http://www.w3.org/2003/XInclude">
+<title>The Official Samba 3.2.x HOWTO and Reference Guide</title>
+
+<bookinfo>
+	<authorgroup>
+	<editor>&person.jelmer;</editor>
+	<editor>&person.jht;</editor>
+	<editor>&person.jerry;</editor>
+	</authorgroup>
+	<pubdate><?latex \today ?></pubdate>
+</bookinfo>
+
+	<?latex \setcounter{page}{5} ?>
+
+	<xi:include href="TOSHARG-inside-cover.xml"/>
+
+	<?latex \cleardoublepage ?>
+
+	<xi:include href="../Samba3-HOWTO-attributions.xml">
+		<xi:fallback/>
+	</xi:include>
+
+	<?latex \cleardoublepage ?>
+
+<!-- Contents -->
+	<toc/>
+
+	<?latex \cleardoublepage ?>
+
+	<?latex \listofexamples ?>
+
+	<?latex \cleardoublepage ?>
+
+	<lot/>
+
+	<xi:include href="TOSHARG-foreword-cargill.xml"/>
+
+	<?latex \cleardoublepage ?>
+
+	<xi:include href="TOSHARG-preface.xml"/>
+
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-IntroSMB.xml"/>
+
+	<?latex \cleardoublepage ?>
+
+<!-- Chapters -->
+<part id="introduction">
+<title>General Installation</title>
+<?latex \pagenumbering{arabic} ?>
+
+<partintro>
+<title>Preparing Samba for Configuration</title>
+
+<para>
+This section of the Samba-HOWTO-Collection contains general info on how to install Samba 
+and how to configure the parts of Samba you will most likely need.
+PLEASE read this.
+</para>
+
+</partintro>
+
+	<?latex \cleardoublepage ?>
+
+	<xi:include href="TOSHARG-Install.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-FastStart.xml"/>
+	<?latex \cleardoublepage ?>
+
+</part>
+
+<part id="type">
+<title>Server Configuration Basics</title>
+<partintro>
+<title>First Steps in Server Configuration</title>
+
+<para>
+Samba can operate in various modes within SMB networks. This HOWTO section contains information on
+configuring Samba to function as the type of server your network requires. Please read this
+section carefully.
+</para>
+
+</partintro>
+
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-ServerType.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-PDC.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-BDC.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-DomainMember.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-StandAloneServer.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-WindowsClientConfig.xml"/>
+	<?latex \cleardoublepage ?>
+
+</part>
+
+<part id="optional">
+<title>Advanced Configuration</title>
+<partintro>
+<title>Valuable Nuts and Bolts Information</title>
+
+<para>
+Samba has several features that you might want or might not want to use.
+The chapters in this part each cover specific Samba features.
+</para>
+
+</partintro>
+
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-ChangeNotes.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-NetworkBrowsing.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Passdb.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Group-Mapping.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-TheNetCommand.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-IDMAP.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-RightsAndPriviliges.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-AccessControls.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-locking.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Securing.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-InterdomainTrusts.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-msdfs.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Printing.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-CUPS-printing.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-VFS.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Winbind.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-AdvancedNetworkAdmin.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-PolicyMgmt.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-ProfileMgmt.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-PAM.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Integrating-with-Windows.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Unicode.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Backup.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-HighAvailability.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-LargeFile.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-ConfigSmarts.xml"/>
+	<?latex \cleardoublepage ?>
+
+</part>
+
+<part id="migration">
+<title>Migration and Updating</title>
+
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-upgrading-to-3.0.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-NT4Migration.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-SWAT.xml"/>
+	<?latex \cleardoublepage ?>
+
+</part>
+
+<part id="troubleshooting">
+<title>Troubleshooting</title>
+
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Diagnosis.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Problems.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Bugs.xml"/>
+	<?latex \cleardoublepage ?>
+
+</part>
+
+<part id="Appendix">
+<title>Reference Section</title>
+
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Compiling.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Portability.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Other-Clients.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Speed.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-SecureLDAP.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-Support.xml"/>
+	<?latex \cleardoublepage ?>
+	<xi:include href="TOSHARG-DNS-DHCP-Configuration.xml"/>
+	<?latex \cleardoublepage ?>
+</part>
+
+<!-- Comment out the following line to include the manpages.
+	 *Please* do not commit with the two lines below enabled! -->
+<!--
+	<?latex \cleardoublepage ?>
+	<xi:include href="manpages.xml"/>
+-->
+	<?latex \cleardoublepage ?>
+
+<xi:include href="gpl-3.0.xml"/>
+
+	<?latex \cleardoublepage ?>
+<xi:include href="TOSHARG-glossary.xml"/>
+
+	<?latex \cleardoublepage ?>
+<?latex \chaptermark{Subject index} ?>
+
+<index/>
+
+</book>
diff --git a/docs-xml/Samba3-HOWTO/manpages.xml b/docs-xml/Samba3-HOWTO/manpages.xml
new file mode 100644
index 00000000000..4de54bf4f53
--- /dev/null
+++ b/docs-xml/Samba3-HOWTO/manpages.xml
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE reference PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<reference xmlns:xi="http://www.w3.org/2003/XInclude">
+	<title>Manual pages</title>
+
+	<para>This chapter contains most of the manual pages from the official Samba distribution.
+		All manual pages have been written by members of 
+		<ulink url="http://www.samba.org/samba/team.html">the Samba Team</ulink>.</para>
+
+	<xi:include href="../manpages-3/eventlogadm.8.xml"/>
+	<xi:include href="../manpages-3/findsmb.1.xml"/>
+	<xi:include href="../manpages-3/idmap_ad.8.xml"/>
+	<xi:include href="../manpages-3/idmap_ldap.8.xml"/>
+	<xi:include href="../manpages-3/idmap_nss.8.xml"/>
+	<xi:include href="../manpages-3/idmap_rid.8.xml"/>
+	<xi:include href="../manpages-3/idmap_tdb.8.xml"/>
+	<xi:include href="../manpages-3/libsmbclient.7.xml"/>
+	<xi:include href="../manpages-3/lmhosts.5.xml"/>
+	<xi:include href="../manpages-3/log2pcap.1.xml"/>
+	<xi:include href="../manpages-3/mount.cifs.8.xml"/>
+	<xi:include href="../manpages-3/net.8.xml"/>
+	<xi:include href="../manpages-3/nmbd.8.xml"/>
+	<xi:include href="../manpages-3/nmblookup.1.xml"/>
+	<xi:include href="../manpages-3/ntlm_auth.1.xml"/>
+	<xi:include href="../manpages-3/pam_winbind.7.xml"/>
+	<xi:include href="../manpages-3/pdbedit.8.xml"/>
+	<xi:include href="../manpages-3/profiles.1.xml"/>
+	<xi:include href="../manpages-3/rpcclient.1.xml"/>
+	<xi:include href="../manpages-3/smbcacls.1.xml"/>
+	<xi:include href="../manpages-3/smbclient.1.xml"/>
+	<xi:include href="../manpages-3/smb.conf.5.xml"/>
+	<xi:include href="../manpages-3/smbcontrol.1.xml"/>
+	<xi:include href="../manpages-3/smbcquotas.1.xml"/>
+	<xi:include href="../manpages-3/smbd.8.xml"/>
+	<xi:include href="../manpages-3/smbget.1.xml"/>
+	<xi:include href="../manpages-3/smbgetrc.5.xml"/>
+	<xi:include href="../manpages-3/smbpasswd.5.xml"/>
+	<xi:include href="../manpages-3/smbpasswd.8.xml"/>
+	<xi:include href="../manpages-3/smbsh.1.xml"/>
+	<xi:include href="../manpages-3/smbstatus.1.xml"/>
+	<xi:include href="../manpages-3/smbtar.1.xml"/>
+	<xi:include href="../manpages-3/smbtree.1.xml"/>
+	<xi:include href="../manpages-3/smbumount.8.xml"/>
+	<xi:include href="../manpages-3/swat.8.xml"/>
+	<xi:include href="../manpages-3/tdbbackup.8.xml"/>
+	<xi:include href="../manpages-3/tdbdump.8.xml"/>
+	<xi:include href="../manpages-3/tdbtool.8.xml"/>
+	<xi:include href="../manpages-3/testparm.1.xml"/>
+	<xi:include href="../manpages-3/wbinfo.1.xml"/>
+	<xi:include href="../manpages-3/winbindd.8.xml"/>
+	<xi:include href="../manpages-3/umount.cifs.8.xml"/>
+	<xi:include href="../manpages-3/vfs_audit.8.xml"/>
+	<xi:include href="../manpages-3/vfs_cacheprime.8.xml"/>
+	<xi:include href="../manpages-3/vfs_cap.8.xml"/>
+	<xi:include href="../manpages-3/vfs_catia.8.xml"/>
+	<xi:include href="../manpages-3/vfs_commit.8.xml"/>
+	<xi:include href="../manpages-3/vfs_default_quota.8.xml"/>
+	<xi:include href="../manpages-3/vfs_extd_audit.8.xml"/>
+	<xi:include href="../manpages-3/vfs_fake_perms.8.xml"/>
+	<xi:include href="../manpages-3/vfs_full_audit.8.xml"/>
+	<xi:include href="../manpages-3/vfs_gpfs.8.xml"/>
+	<xi:include href="../manpages-3/vfs_netatalk.8.xml"/>
+	<xi:include href="../manpages-3/vfs_notify_fam.8.xml"/>
+	<xi:include href="../manpages-3/vfs_prealloc.8.xml"/>
+	<xi:include href="../manpages-3/vfs_readahead.8.xml"/>
+	<xi:include href="../manpages-3/vfs_readonly.8.xml"/>
+	<xi:include href="../manpages-3/vfs_recycle.8.xml"/>
+	<xi:include href="../manpages-3/vfs_shadow_copy.8.xml"/>
+	<xi:include href="../manpages-3/vfstest.1.xml"/>
+	<xi:include href="../manpages-3/wbinfo.1.xml"/>
+	<xi:include href="../manpages-3/winbindd.8.xml"/>
+
+</reference>
diff --git a/docs-xml/Samba4-HOWTO/ad-dc.xml b/docs-xml/Samba4-HOWTO/ad-dc.xml
new file mode 100644
index 00000000000..cdfc358edc3
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/ad-dc.xml
@@ -0,0 +1,4 @@
+<chapter id="ad-dc">
+	<title>Active Directory - Domain Controller</title>
+
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/ad-member.xml b/docs-xml/Samba4-HOWTO/ad-member.xml
new file mode 100644
index 00000000000..b46d99be74d
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/ad-member.xml
@@ -0,0 +1,4 @@
+<chapter id="ad-member">
+	<title>Active Directory - Member</title>
+
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/auth.xml b/docs-xml/Samba4-HOWTO/auth.xml
new file mode 100644
index 00000000000..58b25f4035b
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/auth.xml
@@ -0,0 +1,4 @@
+<chapter id="authentication">
+	<title>Authentication</title>
+
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/cifsfs.xml b/docs-xml/Samba4-HOWTO/cifsfs.xml
new file mode 100644
index 00000000000..190c3840d6c
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/cifsfs.xml
@@ -0,0 +1,4 @@
+<chapter id="cifsfs">
+	<title>CIFSFS</title>
+
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/compiling.xml b/docs-xml/Samba4-HOWTO/compiling.xml
new file mode 100644
index 00000000000..048a0f4b8e5
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/compiling.xml
@@ -0,0 +1,24 @@
+<chapter id="compiling">
+	<title>Compiling</title>
+
+	<sect1>
+		<title>Downloading the source - Tar Ball</title>
+
+	</sect1>
+
+	<sect1>
+		<title>Downloading the source - Subversion</title>
+
+	</sect1>
+
+	<sect1>
+		<title>Compiling the source</title>
+
+	</sect1>
+
+	<sect1>
+		<title>Installing</title>
+
+	</sect1>
+
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/config.xml b/docs-xml/Samba4-HOWTO/config.xml
new file mode 100644
index 00000000000..e251c698abe
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/config.xml
@@ -0,0 +1,5 @@
+<chapter id="config">
+	<title>Configuration</title>
+
+	<para>Chapter describing Samba's configuration in detail.</para>
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/domain-bdc.xml b/docs-xml/Samba4-HOWTO/domain-bdc.xml
new file mode 100644
index 00000000000..61c420fe7bf
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/domain-bdc.xml
@@ -0,0 +1,4 @@
+<chapter id="bdc">
+	<title>Backup Domain Controller</title>
+
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/domain-member.xml b/docs-xml/Samba4-HOWTO/domain-member.xml
new file mode 100644
index 00000000000..8be3758792e
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/domain-member.xml
@@ -0,0 +1,2 @@
+<chapter id="domain-member">
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/domain-pdc.xml b/docs-xml/Samba4-HOWTO/domain-pdc.xml
new file mode 100644
index 00000000000..b3fb6e6f7b4
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/domain-pdc.xml
@@ -0,0 +1 @@
+<chapter id="domain-pdc"/>
diff --git a/docs-xml/Samba4-HOWTO/gui-clients.xml b/docs-xml/Samba4-HOWTO/gui-clients.xml
new file mode 100644
index 00000000000..0c50ccc8c66
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/gui-clients.xml
@@ -0,0 +1 @@
+<chapter id="gui-clients"/>
diff --git a/docs-xml/Samba4-HOWTO/history.xml b/docs-xml/Samba4-HOWTO/history.xml
new file mode 100644
index 00000000000..e69de29bb2d
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/history.xml
diff --git a/docs-xml/Samba4-HOWTO/index.xml b/docs-xml/Samba4-HOWTO/index.xml
new file mode 100644
index 00000000000..6562a7ed349
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/index.xml
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<book id="Samba-HOWTO"
+	xmlns:xi="http://www.w3.org/2003/XInclude">
+<title>The Official Samba-4 HOWTO</title>
+
+<bookinfo>
+	<authorgroup>
+	<editor>&person.jelmer;</editor>
+	</authorgroup>
+	<pubdate><?latex \today ?></pubdate>
+
+</bookinfo>
+
+<?latex \setcounter{page}{5} ?>
+
+<preface>
+	<title>Attribution</title>
+	<para>
+		<xi:include href="../Samba4-HOWTO-attributions.xml"/>
+	</para>
+</preface>
+
+<?latex \cleardoublepage ?>
+
+<!-- Contents -->
+<toc/>
+<?latex \cleardoublepage ?>
+
+<part>
+	<title>Introduction to SMB networks</title>
+
+	<para>Not everybody is already familiar with SMB networks and the jargon 
+		used in such networks. This part describes the evolution of SMB, 
+		how the protocol is structured and what Samba can be used for. </para>
+
+	<para>NT admins, already familiar with SMB networks, are probably only 
+		interested in the chapter about Samba itself.</para>
+
+	<xi:include href="protocol.xml"/>
+	<xi:include href="samba.xml"/>
+
+</part>
+
+<part>
+	<title>Samba 4 Basics</title>
+
+	<para>FIXME</para>
+
+	<xi:include href="config.xml"/>
+	<xi:include href="ldb.xml"/>
+</part>
+
+<part>
+	<title>Network model</title>
+
+	<para>
+		A SMB server is used in a certain network type 
+		(workgroup, domain, active directory) with a specific 
+		role (stand-alone, primary domain controller, backup domain controller, etc) in that network. Samba has to be configured according to that role. 
+		Each of the chapters in this part describes how to configure Samba 
+		for a specific role.
+	</para>
+
+</part>
+
+<part>
+	<title>Network Model: Share-based security</title>
+		
+	<xi:include href="security=share.xml"/>
+</part>
+
+<part>
+	<title>Network Model: User-based security</title>
+	<xi:include href="security=user.xml"/>
+</part>
+
+<part id="domain">
+	<title>Network Model: NT4-style domains</title>
+
+	<xi:include href="domain-pdc.xml"/>
+	<xi:include href="domain-bdc.xml"/>
+	<xi:include href="domain-member.xml"/>
+</part>
+
+<part id="ad">
+	<title>Network Model - Active Directory</title>
+
+	<xi:include href="ad-dc.xml"/>
+	<xi:include href="ad-member.xml"/>
+</part>
+
+<part>
+	<title>Common services</title>
+
+	<para>
+		Independent of the role the server has, it can provide services. 
+		Examples of services are printing, user management, authentication, etc.
+	</para>
+
+	<xi:include href="shares.xml"/>
+	<xi:include href="printing.xml"/>
+	<xi:include href="auth.xml"/>
+	<xi:include href="registry.xml"/>
+</part>
+
+<part>
+	<title>Clients</title>
+
+	<para>Samba includes a number of different clients for accessing 
+	SMB file, print and other services. Pretty much every service can 
+	be access using a command-line utility, though there are several 
+	GUI clients available as well.</para>
+
+	<xi:include href="smbclient.xml"/>
+	<xi:include href="cifsfs.xml"/>
+	<xi:include href="gui-clients.xml"/>
+</part>
+
+<part>
+	<title>Appendices</title>
+
+	<xi:include href="compiling.xml"/>
+
+</part>
+
+<lot/>
+
+<?latex \include{gpl}?>
+
+<!--<xi:include href="../Samba-HOWTO-Collection/glossary.xml"/>-->
+
+<?latex \chaptermark{Subject index} ?>
+<index/>
+
+</book>
diff --git a/docs-xml/Samba4-HOWTO/ldb.xml b/docs-xml/Samba4-HOWTO/ldb.xml
new file mode 100644
index 00000000000..5b1eb862e62
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/ldb.xml
@@ -0,0 +1 @@
+<chapter id="ldb"/>
diff --git a/docs-xml/Samba4-HOWTO/printing.xml b/docs-xml/Samba4-HOWTO/printing.xml
new file mode 100644
index 00000000000..5ffb2b76801
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/printing.xml
@@ -0,0 +1,11 @@
+<chapter id="printing">
+	<title>Printing</title>
+
+	<!--FIXME: Some Windows printing background information -->
+
+	<sect1 id="unix">
+		<title>Unix printing types</title>
+
+	</sect1>
+	
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/protocol.xml b/docs-xml/Samba4-HOWTO/protocol.xml
new file mode 100644
index 00000000000..f2961116e0b
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/protocol.xml
@@ -0,0 +1,204 @@
+<chapter id="protocol">
+	<title>The SMB/CIFS protocol</title>
+
+	<!-- 
+	Some parts shamelessly borrowed from myself. 
+	Original on http://jelmer.vernstok.nl/publications/cifs-developments.pdf
+	-->
+
+	<para>
+		"SMB" (also known as "CIFS") is a 
+		file-sharing protocol that has been used since the mid-eighties. 
+		Most people know SMB as the protocol behind the "Network Neighbourhood" 
+		and remote printing in Windows.
+	</para>
+
+	<para>
+		Several parts of the protocol are not discussed in this chapter, such 
+		as mailslots, browsing and dfs, to prevent it from getting too complex. 
+		CIFS internals are documented in detail in <citation>Hertel, 2003</citation>.
+	</para>
+
+
+	<sect1>
+		<title>History</title>
+
+		<sect2>
+			<title>Invention by IBM</title>
+
+			<para>
+				SMB is not very old, but it has a long history of modifications and extensions.
+				The original protocol was meant to run over ``NetBIOS'', which was the 
+				name of the DOS interface to a very simple LAN system developed by IBM.
+				NetBIOS was developed because SNA, IBM's other main 
+				protocol at the time, was much too advanced for use in DOS.
+			</para>
+
+			<para>
+				The NetBIOS API in these days (early eighties) was nothing more then the 
+				interface to a very simple link-layer protocol 
+				over which several protocols, including SMB, were used. It could do reads and 
+				writes to services on remote hosts, which were identified by case-insensitive 
+				names, and discover all available hosts and services.
+			</para>
+
+			<para>
+				Dr. Barry Feigenbau, an IBM employee, invented the core of the original SMB protocol, 
+				which he initially named after himself: ``BAF''. He later changed the name to 
+				be ``SMB'' (for ``Server Message Block''). Every packet in the protocol 
+				starts with a byte $0xFF$ and these three letters. 
+			</para>
+
+			<para>
+				IBM, Microsoft, 3Com and Intel made up the rest of the initial protocol 
+				together. The commands the protocol supported at this stage were basically
+				a mirror of the DOS File IO API calls, which meant the protocol wasn't very 
+				efficient. The protocol also lacked authentication support. Everybody on the 
+				network could do reads and writes, which meant this protocol 
+				wasn't very suitable for large enterprises.
+			</para>
+
+			<para>
+				NetBIOS is an API that has had various implementations; there is 
+				NetBIOS over TCP/IP (NBT), NetBIOS over IPX, NetBIOS over SNA and 
+				even NetBIOS over DECNEt. Mostly used these days is
+				NetBIOS over TCP (NBT). 
+			</para>
+
+			<para>
+				This is also were things are starting to get hairy. Since NetBIOS identifies 
+				hosts by their name, NetBIOS clients had to start doing IP broadcasts to 
+				figure out the IP of the host they had to connect to. Several schemes were 
+				introduced to do name lookups crossing subnet boundaries, using name servers, 
+				etc. We're basically emulating a NetBIOS LAN in order to be able to run SMB.
+			</para>
+
+			<para>
+				Doing NetBIOS over IP is not very sane, however, the NBT implementation itself 
+				in Windows isn't very nice either. It has horrible 
+				limits, special exceptions, several broken schemes for looking up 
+				names (including two kinds of name servers). NetBIOS and NetBIOS over TCP/IP 
+				are described in RFC1001 and RFC1002.
+			</para>	
+		</sect2>
+
+		<sect2>
+			<title>The various incarnations of SMB</title>
+
+			<para>Over the years, several usage models for SMB have been developed. While SMB originally started out as a file sharing protocol, it was later extended to include support for network management and other network services 
+				as well.</para>
+
+			<para>
+				One of the reasons for the various "upgrades" of the SMB 
+				protocol is the fact that networks have become larger 
+				and larger and with them the need for privilege separation 
+				and scalability has increased.
+			</para>
+
+			<sect3>
+				<title>DOS</title>
+
+				<para>
+					The original model in which SMB was used was as a 
+					simple file-sharing service in a NetBIOS-environment.
+				</para>
+				
+				<para>
+					File sharing worked basically by specifying a list of directories that had 
+					to be shared and what name they had to be shared under ("shares"). Eventually, 
+					one could password-protect a share. At most one password per share could be set.
+				</para>
+			</sect3>
+
+			<sect3>
+				<title>Windows For Workgroups</title>
+				
+				<para>
+					After the ``CORE'' dialect, 
+					IBM and Microsoft implemented a new dialect known as ``LANMAN''.
+					This dialect was used by Windows for 
+					Workgroups, OS/2 and Windows 9x which all know it under a different name. A 
+					'virtual' file system was also added, which was used for doing remote function 
+					calls (RAP, for ``Remote Administration Protocol'').
+				</para>
+
+				<para>
+					Computers are grouped into "Workgroups" in this model. Everybody is equal to 
+					the others and there is no central point of control.
+				</para>
+			</sect3>
+
+			<sect3>
+				<title>Windows NT</title>
+				<para>
+					For Windows NT, yet another dialect was added, named 'NT'. The NT dialect 
+					had it's own set of file I/O functions (similar to the NT File I/O API) 
+					and it had support for yet another way of doing remote function calls:
+					DCE/RPC. RPC's are used for DCOM and several of the subsystems in NT
+					that can be accessed remotely (registry, printing, user management, logging 
+					on, etc).
+				</para>
+
+				<para>
+					Windows NT works with a new concept for grouping computers called ``domains''<footnote>In the protocol, domains are actually an upgraded version of a workgroup</footnote>. Each computer is member of exactly one domain. There are several roles a computer can have in the domain: PDC (primary domain controller, the "manager" of the domain, that coordinates all authentication and authorization), BDC (Backup domain controller, in case the PDC goes down) or just a regular domain member. The PDC decides who is to be a member of the domain.
+				</para>
+			</sect3>
+
+			<sect3>
+				<title>Windows 2000</title>
+				<para>
+					In Windows NT 5 (marketing name: Windows 2000), NetBIOS-less SMB was
+					introduced. This means SMB is used directly over TCP port 445 instead of 
+					via NetBIOS over TCP/IP. DNS 
+					is used for looking up machine names. 
+				</para>
+
+				<para>Windows 2000 was also the first operating system from Microsoft
+					that had support for Active Directory. Active Directory is very 
+					similar to the "domain" concept used by NT4, though it 
+					is implemented differently (using modified open protocols), 
+					and has some additional features (one of the most important ones being decentralized).
+				</para>
+
+				<para>
+					Active directory no longer uses a central point of authority 
+					and there are fewer limits to the size of a domain. Several 
+					DC's can exist, so there is no longer a single point of 
+					failure as well as better scalability. 
+				</para>
+			</sect3>
+		</sect2>
+
+		<sect2>
+			<title>Samba versions and their support for the SMB models</title>
+
+			<sect3>
+				<title>Samba 2.2</title>
+
+				<para>Full CORE and Workgroup support. Somewhat basic 
+					NT4-style support.</para>
+			</sect3>
+
+			<sect3>
+				<title>Samba 3.0</title>
+
+				<para>Full CORE and Workgroup support. Almost complete 
+					NT4-style support.
+				</para>
+			</sect3>
+
+			<sect3>
+				<title>Samba 3.2</title>
+
+				<para>FIXME</para>
+			</sect3>
+
+			<sect3>
+				<title>Samba 4.0</title>
+				
+				<para>Full CORE, Workgroup, NT4 and ADS support.</para>
+
+			</sect3>
+		</sect2>
+	</sect1>
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/registry.xml b/docs-xml/Samba4-HOWTO/registry.xml
new file mode 100644
index 00000000000..2ef11d34578
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/registry.xml
@@ -0,0 +1,4 @@
+<chapter id="registry">
+	<title>Registry</title>
+
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/samba.xml b/docs-xml/Samba4-HOWTO/samba.xml
new file mode 100644
index 00000000000..8fed58559a6
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/samba.xml
@@ -0,0 +1,48 @@
+<chapter id="samba">
+	<title>Samba</title>
+
+	<para>
+		Samba is an Open Source application that provides 
+		an SMB implementation for POSIX-compatible 
+		operating systems. 
+	</para>
+
+	<para>
+		Providing support for a Windows-based file-sharing protocol
+		on POSIX servers sometimes requires mapping Windows semantics to 
+		POSIX semantics.
+	</para>
+
+	<para>
+		Samba has always been catching up with Microsoft. Here is a list 
+		of Samba releases and what they support (or will support).
+	</para>
+
+	<sect1>
+	<title>Samba 2.2</title>
+
+	<para>Full CORE and Workgroup support. Somewhat basic 
+		NT4-style support.</para>
+	</sect1>
+
+	<sect1>
+		<title>Samba 3.0</title>
+
+		<para>Full CORE and Workgroup support. Almost complete 
+			NT4-style support.
+		</para>
+	</sect1>
+
+	<sect1>
+		<title>Samba 3.2</title>
+
+		<para>FIXME</para>
+	</sect1>
+
+	<sect1>
+		<title>Samba 4.0</title>
+		
+		<para>Full CORE, Workgroup, NT4 and ADS support.</para>
+
+	</sect1>
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/security=share.xml b/docs-xml/Samba4-HOWTO/security=share.xml
new file mode 100644
index 00000000000..1731bc08622
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/security=share.xml
@@ -0,0 +1,8 @@
+<chapter id="security=share">
+	<title>Share-based stand-alone server</title>
+
+<para>
+	One of the simplest 
+</para>
+
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/security=user.xml b/docs-xml/Samba4-HOWTO/security=user.xml
new file mode 100644
index 00000000000..1713c99c7cb
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/security=user.xml
@@ -0,0 +1,6 @@
+<chapter id="security=user">
+	<title>User-based Stand-alone server</title>
+
+	<para></para>
+	
+</chapter>
diff --git a/docs-xml/Samba4-HOWTO/shares.xml b/docs-xml/Samba4-HOWTO/shares.xml
new file mode 100644
index 00000000000..13e9b4c3dc2
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/shares.xml
@@ -0,0 +1 @@
+<chapter id="shares"/>
diff --git a/docs-xml/Samba4-HOWTO/smbclient.xml b/docs-xml/Samba4-HOWTO/smbclient.xml
new file mode 100644
index 00000000000..1f97ce62656
--- /dev/null
+++ b/docs-xml/Samba4-HOWTO/smbclient.xml
@@ -0,0 +1,4 @@
+<chapter id="smbclient">
+	<title>smbclient</title>
+
+</chapter>
diff --git a/docs-xml/aclocal.m4 b/docs-xml/aclocal.m4
new file mode 100644
index 00000000000..9ecbda5e6bc
--- /dev/null
+++ b/docs-xml/aclocal.m4
@@ -0,0 +1,64 @@
+dnl (C) 2003-2004 Jelmer Vernooij <jelmer@samba.org>
+dnl Published under the GNU GPL
+dnl
+dnl DOCS_DEFINE_TARGET
+dnl arg1: Target that is defined
+dnl arg2: Requirement
+dnl arg3: Official name
+dnl arg4: Makefile target name
+
+AC_DEFUN(DOCS_DEFINE_TARGET, [
+	if test "x$$1_REQUIRES" = x; then
+		$1_REQUIRES="$$2_REQUIRES"
+	else
+		$1_REQUIRES="$$1_REQUIRES $$2_REQUIRES"
+	fi
+
+	if test x"$$1_REQUIRES" = x; then
+		TARGETS="$TARGETS $4"
+	else
+		AC_MSG_RESULT([Building the $3 requires : $$1_REQUIRES])
+	fi
+])
+
+dnl DOCS_TARGET_REQUIRE_PROGRAM
+dnl arg1: program variable
+dnl arg2: program executable name
+dnl arg3: target that requires it
+
+AC_DEFUN(DOCS_TARGET_REQUIRE_PROGRAM, [
+	AC_CHECK_PROGS([$1], [$2])
+	if test x"$$1" = x; then
+		if test x"$$3_REQUIRES" = x; then
+			$3_REQUIRES="$2"
+		else
+			$3_REQUIRES="$$3_REQUIRES $2"
+		fi
+	fi
+])
+
+dnl DOCS_TARGET_REQUIRE_DIR
+dnl arg1: list of possible paths
+dnl arg2: file in dir know to exist
+dnl arg3: variable to store found path in
+dnl arg4: target that requires it
+
+AC_DEFUN(DOCS_TARGET_REQUIRE_DIR, [
+    AC_MSG_CHECKING([for $2])
+	AC_SUBST($3)
+	for I in $1; 
+	do 
+		test -f "$I/$2" && $3="$I"
+	done
+
+	if test x$$3 = x; then
+		if test x"$$4_REQUIRES" = x; then
+			$4_REQUIRES="$3"
+		else
+			$4_REQUIRES="$$4_REQUIRES $3"
+		fi
+		AC_MSG_RESULT([not found])
+	else
+		AC_MSG_RESULT([found in $$3])
+	fi
+])
diff --git a/docs-xml/archives/THANKS b/docs-xml/archives/THANKS
new file mode 100644
index 00000000000..789042f78e1
--- /dev/null
+++ b/docs-xml/archives/THANKS
@@ -0,0 +1,137 @@
+=====================================================================
+This file is for thanks to individuals or organisations who have
+helped with the development of Samba, other than by coding or bug
+reports. Their contributions are gratefully acknowledged.
+
+Please refer to the manual pages and change-log for a list of those
+who have contributed in the form of patches, bug fixes or other 
+direct changes to the package.
+
+Contributions of any kind are welcomed. If you want to help then
+please contact Andrew.Tridgell@anu.edu.au, or via normal mail at 
+
+	Andrew Tridgell
+	3 Ballow Crescent
+	Macgregor, A.C.T
+	2615 Australia
+=====================================================================
+
+
+Lee Fisher (leefi@microsoft.com)
+Charles Fox (cfox@microsoft.com)
+Dan Perry (danp@exchnge.microsoft.com)
+Paul Leach (paulle@microsoft.com)
+Isaac Heizer (isaache@microsoft.com)
+
+    These Microsoft people have been very helpful and supportive of
+    the development of Samba over some years.
+
+    Lee very kindly supplied me with a copy of the X/Open SMB
+    specs. These have been invaluable in getting the details of the
+    implementation right. They will become even more important as we move
+    towards a Lanman 2.1 compliant server. Lee has provided very
+    useful advice on several aspects of the server.
+    Lee has also provided me with copies of Windows NTAS 3.1, Visual C
+    and a developers CD-ROM. Being able to run NT at home is a
+    great help.
+
+    Charles has helped out in numerous ways with the provision of SMB
+    specifications and helpful advice. He has been following the
+    discussion of Samba on the mailing list and has stepped in
+    regularly to clarify points and to offer help.
+    
+    Dan has put me in touch with NT developers to help sort out bugs and
+    compatability issues. He has also supplied me with a copy of the
+    NT browsing spec, which will help a lot in the development of the
+    Samba browser code.
+
+    Paul was responsible for Microsoft paying my flight to Seattle for the
+    first CIFS conference (see http://samba.org/cifs) and has been
+    generally helpful and cooperative as the SMB community moves towards
+    an Internet-ready specification. Isaac has regularly provided help on
+    the behaviour of NT networks.
+
+Bruce Perens (bruce@pixar.com)
+
+    In appreciation of his effort on Samba we have sent Andrew copies of
+    various Pixar computer-graphics software products. Pixar is best known
+    for its "Renderman" product, the 3-D renderer used by ILM to make special
+    effects for "Terminator II" and "Jurassic Park". We won the first Oscar
+    given to a computer graphic animated feature for our short film "Tin Toy".
+    Our retail products "Typestry" and "Showplace", incorporate the same
+    renderer used on the films, and are available on Windows and the
+    Macintosh.
+
+
+
+Henry Lee (hyl@microplex.co)
+
+    Henry sent me a M202 ethernet print server, making my little lan
+    one of the few home networks to have it's own print server!
+
+  ``Microplex Systems Ltd. is a manufacturer of local and wide area
+    network communications equipment based in beautiful Vancouver, British
+    Columbia, Canada.  Microplex's first products were synchronous wide
+    area network devices used in the mainframe communication networks.  In
+    August 1991 Microplex introduced its first LAN product, the M200 print
+    server, the first high performance print server under US$1,000.''
+
+
+Tom Haapanen (tomh@metrics.com)
+
+    Tom sent me two 16 bit SMC ethernet cards to replace my ancient 8
+    bit ones. The performance is much better!
+
+    Software Metrics Inc. is a small custom software development and
+    consulting firm located in Waterloo, Ontario, Canada.  We work
+    with a variety of environments (such as Windows, Windows NT and
+    Unix), tools and application areas, and can provide assistance for
+    development work ranging from a few days to to multiple man-year
+    projects.  You can find more information at http://www.metrics.com/.
+    
+
+Steve Kennedy (steve@gbnet.net)
+
+	Steve sent me 16Mb of ram so that I could install/test
+	NT3.5. I previous had only 8Mb ram in my test machine, which
+	wasn't enough to install a properly functioning copy of
+	NTAS. Being able to directly test NT3.5 allowed me to solve
+	several long standing NT<->Samba problems. Thanks Steve!
+
+John Terpstra (jht@aquasoft.com.au)
+
+        Aquasoft are a specialist consulting company whose Samba-using
+        customers span the world.
+
+        Aquasoft have been avid supporters of the Samba project. As a
+        token of appreciation Aquasoft have donated a 486DX2/66 PC with
+        a 540MB EIDE drive and 20MB RAM.
+
+        John has helped to isolate quite a few little glitches over time
+        and has managed to implement some very interesting installations
+        of Samba.
+
+        The donation of the new PC will make it possible to more fully
+        diagnose and observe the behaviour of Samba in conjuction with
+        other SMB protocol utilising systems.
+
+
+Timothy F. Sipples (tsipple@vnet.IBM.COM)
+Steve Withers (swithers@vnet.IBM.COM)
+
+	Tim and Steve from IBM organised a copy of the OS/2 developers
+	connection CD set for me, and gave lots of help in getting
+	OS/2 Warp installed. I hope this will allow me to finally fix
+	up those annoying OS/2 related Samba bugs that I have been
+	receiving reports of.
+
+Keith Wilkins (wilki1k@nectech.co.uk)
+
+	Keith from NEC in England very generously supplied a PC to
+	Luke Leighton to help with his nmbd development work. At the
+	same time Keith offered to help me with some new hardware, and
+	he sent me a pentium motherboard with 32MB of ram
+	onboard. This was very helpful as it allowed me to upgrade
+	my aging server to be a very powerful system. Thanks!
+
+
diff --git a/docs-xml/archives/history b/docs-xml/archives/history
new file mode 100644
index 00000000000..7bcbe3564ad
--- /dev/null
+++ b/docs-xml/archives/history
@@ -0,0 +1,218 @@
+Contributor:	Andrew Tridgell and the Samba Team
+Date:		June 27, 1997
+Satus:		Always out of date! (Would not be the same without it!)
+
+Subject:	A bit of history and a bit of fun
+============================================================================
+
+This is a short history of this project. It's not supposed to be
+comprehensive, just enough so that new users can get a feel for where
+this project has come from and maybe where it's going to.
+
+The whole thing really started in December 1991. I was (and still am)
+a PhD student in the Computer Sciences Laboratory at the Australian
+National University, in Canberra, Australia. We had just got a
+beta copy of eXcursion from Digital, and I was testing it on my PC. At
+this stage I was a MS-DOS user, dabbling in windows.
+
+eXcursion ran (at the time) only with Dec's `Pathworks' network for
+DOS. I had up till then been using PC-NFS to connect to our local sun
+workstations, and was reasonably happy with it. In order to run
+pathworks I had to stop using PC-NFS and try using pathworks to mount
+disk space. Unfortunately pathworks was only available for digital
+workstations running VMS or Ultrix so I couldn't mount from the suns
+anymore.
+
+I had access to a a decstation 3100 running Ultrix that I used to
+administer, and I got the crazy notion that the protocol that
+pathworks used to talk to ultrix couldn't be that hard, and maybe I
+could work it out. I had never written a network program before, and
+certainly didn't know what a socket was.
+
+In a few days, after looking at some example code for sockets, I
+discovered it was pretty easy to write a program to "spy" on the file
+sharing protocol. I wrote and installed this program (the sockspy.c
+program supplied with this package) and captured everything that the
+pathworks client said to the pathworks server.
+
+I then tried writing short C programs (using Turbo C under DOS) to do
+simple file operations on the network drive (open, read, cd etc) and
+looked at the packets that the server and client exchanged. From this
+I worked out what some of the bytes in the packets meant, and started
+to write my own program to do the same thing on a sun.
+
+After a day or so more I had my first successes and actually managed
+to get a connection and to read a file. From there it was all
+downhill, and a week later I was happily (if a little unreliably)
+mounting disk space from a sun to my PC running pathworks. The server
+code had a lot of `magic' values in it, which seemed to be always
+present with the ultrix server. It was not till 2 years later that I
+found out what all these values meant.
+
+Anyway, I thought other people might be interested in what I had done,
+so I asked a few people at uni, and noone seemed much interested. I
+also spoke to a person at Digital in Canberra (the person who had
+organised a beta test of eXcursion) and asked if I could distribute
+what I'd done, or was it illegal. It was then that I first heard the
+word "netbios" when he told me that he thought it was all covered by a
+spec of some sort (the netbios spec) and thus what I'd done was not
+only legal, but silly.
+
+I found the netbios spec after asking around a bit (the RFC1001 and
+RFC1002 specs) and found they looked nothing like what I'd written, so
+I thought maybe the Digital person was mistaken. I didn't realise RFCs
+referred to the name negotiation and packet encapsulation over TCP/IP,
+and what I'd written was really a SMB implementation.
+
+Anyway, he encouraged me to release it so I put out "Server 0.1" in
+January 1992. I got quite a good response from people wanting to use
+pathworks with non-digital unix workstations, and I soon fixed a few
+bugs, and released "Server 0.5" closely followed by "Server 1.0". All
+three releases came out within about a month of each other.
+
+At this point I got an X Terminal on my desk, and I no longer needed eXcursion
+and I prompty forgot about the whole project, apart from a few people
+who e-mailed me occasionally about it.
+
+Nearly two years then passed with just occasional e-mails asking about
+new versions and bugs. I even added a note to the ftp site asking for
+a volunteer to take over the code as I no longer used it. No one
+volunteered.
+
+During this time I did hear from a couple of people who said it should
+be possible to use my code with Lanmanager, but I never got any
+definite confirmation.
+
+One e-mail I got about the code did, however, make an impression. It
+was from Dan Shearer at the university of South Australia, and he said
+this:
+
+ 
+	I heard a hint about a free Pathworks server for Unix in the
+	Net channel of the Linux list. After quite a bit of chasing
+	(and lots of interested followups from other Linux people) I
+	got hold of a release news article from you, posted in Jan 92,
+	from someone in the UK.
+
+	Can you tell me what the latest status is? I think you might
+	suddenly find a whole lot of interested hackers in the Linux
+	world at least, which is a place where things tend to happen
+	fast (and even some reliable code gets written, BION!)
+
+I asked him what Linux was, and he told me it was a free Unix for PCs.
+This was in November 1992 and a few months later I was a Linux
+convert! I still didn't need a pathworks server though, so I didn't do
+the port, but I think Dan did.
+
+At about this time I got an e-mail from Digital, from a person working
+on the Alpha software distribution. He asked if I would mind if they
+included my server with the "contributed" cd-rom. This was a bit of a
+shock to me as I never expected Dec to ask me if they could use my
+code! I wrote back saying it was OK, but never heard from him again. I
+don't know if it went on the cd-rom.
+
+Anyway, the next big event was in December 1993, when Dan again sent
+me an e-mail saying my server had "raised its ugly head" on
+comp.protocols.tcpip.ibmpc. I had a quick look on the group, and was
+surprised to see that there were people interested in this thing.
+
+At this time a person from our computer center offered me a couple of
+cheap ethernet cards (3c505s for $15 each) and coincidentially someone
+announced on one of the Linux channels that he had written a 3c505
+driver for Linux. I bought the cards, hacked the driver a little and
+setup a home network between my wifes PC and my Linux box. I then
+needed some way to connect the two, and I didn't own PC-NFS at home,
+so I thought maybe my server could be useful. On the newsgroup among
+the discussions of my server someone had mentioned that there was a
+free client that might work with my server that Microsoft had put up
+for ftp. I downloaded it and found to my surprise that it worked first
+time with my `pathworks' server!
+
+Well, I then did a bit of hacking, asked around a bit and found (I
+think from Dan) that the spec I needed was for the "SMB" protocol, and
+that it was available via ftp. I grabbed it and started removing all
+those ugly constants from the code, now that all was explained.
+
+On December 1st 1993 I announced the start of the "Netbios for Unix"
+project, seeding the mailing list with all the people who had e-mailed
+me over the years asking about the server.
+
+About 35 versions (and two months) later I wrote a short history of
+the project, which you have just read. There are now over a hundred
+people on the mailing list, and lots of people report that they use
+the code and like it. In a few days I will be announcing the release
+of version 1.6 to some of the more popular (and relevant) newsgroups.
+
+
+Andrew Tridgell
+6th February 1994
+
+---------------------
+
+It is now May 1995 and there are about 1400 people on the mailing
+list. I got downloads from the main Samba ftp site from around 5000
+unique hosts in a two month period. There are several mirror
+sites as well. The current version number is 1.9.13.
+
+---------------------
+
+
+---------------------
+It's now March 1996 and version 1.9.16alpha1 has just been
+released. There have been lots of changes recently with master browser
+support and the ability to do domain logons etc. Samba has also been
+ported to OS/2, the amiga and NetWare. There are now 3000 people on
+the samba mailing list.
+---------------------
+
+
+---------------------
+It's now June 1997 and samba-1.9.17 is due out soon. My how time passes!
+Please refer to the WHATSNEW.txt for an update on new features. Just when
+you think you understand what is happening the ground rules change - this
+is a real world after all. Since the heady days of March 1996 there has
+been a concerted effort within the SMB protocol using community to document
+and standardize the protocols. The CIFS initiative has helped a long way
+towards creating a better understood and more interoperable environment.
+The Samba Team has grown in number and have been very active in the standards
+formation and documentation process.
+
+The net effect has been that we have had to do a lot of work to bring Samba
+into line with new features and capabilities in the SMB protocols.
+
+The past year has been a productive one with the following releases:
+	1.9.16, 1.9.16p2, 1.9.16p6, 1.9.16p9, 1.9.16p10, 1.9.16p11
+
+There are some who believe that 1.9.15p8 was the best release and others
+who would not want to be without the latest. Whatever your perception we
+hope that 1.9.17 will close the gap and convince you all that the long
+wait and the rolling changes really were worth it. Here is functionality
+and a level of code maturity that ..., well - you can be the judge!
+
+Happy SMB networking!
+Samba Team
+
+ps: The bugs are ours, so please report any you find.
+---------------------
+
+---------------------
+It's now October 1998. We just got back from the 3rd CIFS conference
+in SanJose. The Samba Team was the biggest contingent there.
+
+Samba 2.0 should be shipping in the next few weeks with much better
+domain controller support, GUI configuration, a new user space SMB
+filesystem and lots of other neat stuff. I've also noticed that a
+search of job ads in DejaNews turned up 3900 that mention Samba. Looks
+like we've created a small industry.
+
+I've been asked again where the name Samba came from. I might as well
+put it down here for everyone to read. The code in Samba was first
+called just "server", it then got renamed "smbserver" when I
+discovered that the protocol is called SMB. Then in April 1994 I got
+an email from Syntax, the makers of "TotalNet advanced Server", a
+commercial SMB server. They told me that they had a trademark on the
+name SMBserver and I would have to change the name. I ran an egrep for
+words containing S, M, and B on /usr/dict/words and the name Samba
+looked like the best choice. Strangely enough when I repeat that now I
+notice that Samba isn't in /usr/dict/words on my system anymore! 
+---------------------
diff --git a/docs-xml/build/README b/docs-xml/build/README
new file mode 100644
index 00000000000..736f6731530
--- /dev/null
+++ b/docs-xml/build/README
@@ -0,0 +1,26 @@
+HOW TO BUILD SAMBA DOCUMENTATION WITHOUT NETWORK ACCESS
+-------------------------------------------------------
+
+Samba documentation depends on several DTD schema specification and XML files
+that are stored in samba-web Subversion repository and hosted publicly through
+Samba.org web-site. In order to do networkless builds a local XML catalog should
+provide a local replica of those files.
+
+The easiest way to provide them is to fetch samba-docs subversion repository.
+In this directory (build/) we reference samba-web repository as external source
+so that Subversion fetches current state of DTDs out of samba-web repository.
+You then need to point xsltproc utility to use locally-provided version of DTDs.
+
+It is done by setting XML_CATALOG_FILES variable:
+
+export XML_CATALOG_FILES="file:///etc/xml/catalog file://$(pwd)/build/catalog.xml"
+
+where $(pwd)/build/catalog.xml is generated from $(pwd)/build/catalog.xml.in by a 
+following command:
+
+cat $(pwd)/build/catalog.xml.in | sed -e "s|@BUILDDIR@|$(pwd)|g" > $(pwd)/build/catalog.xml
+
+where $(pwd) assumes that you're in the top-level directory of samba-docs.
+
+After those steps a regular make process can be followed and xsltproc will automatically
+use locally-provided DTDs through catalog.xml we've created.
diff --git a/docs-xml/build/catalog.xml.in b/docs-xml/build/catalog.xml.in
new file mode 100644
index 00000000000..03ac0bdd99e
--- /dev/null
+++ b/docs-xml/build/catalog.xml.in
@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
+<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
+
+<!--  XML Catalog file for SAMBA. -->
+
+    <rewriteURI
+			uriStartString="http://www.samba.org/samba/DTD/"
+			rewritePrefix="file://@BUILDDIR@/build/DTD/"/>
+
+    <rewriteURI
+			uriStartString="http://www.gnu.org/licenses/"
+			rewritePrefix="file://@BUILDDIR@/Samba3-ByExample/"/>
+</catalog>
diff --git a/docs-xml/configure.ac b/docs-xml/configure.ac
new file mode 100644
index 00000000000..97c2b2201fe
--- /dev/null
+++ b/docs-xml/configure.ac
@@ -0,0 +1,97 @@
+AC_INIT(xslt/latex.xsl)
+
+AC_ARG_WITH(samba-sources,
+[ --with-samba-sources=DIR Specify path to Samba sources],
+[ test "$withval" && SPECIFIED_SOURCEDIR="$withval" ])
+
+LATEX_DOCUMENTCLASS_OPTIONS="letterpaper,11pt,openright,twoside"
+AC_ARG_ENABLE(prentice-hall,
+[ --enable-prentice-hall     Produce Prentice-Hall compatible output],
+[ test "$enableval" && LATEX_DOCUMENTCLASS_OPTIONS="letterpaper,10pt,openleft,twoside,ph" ])
+AC_SUBST(LATEX_DOCUMENTCLASS_OPTIONS)
+
+DOC_BUILD_DATE=`date '+%d-%m-%Y'`
+AC_SUBST(DOC_BUILD_DATE)
+AC_SUBST(SAMBASOURCEDIR)
+
+DOCS_TARGET_REQUIRE_PROGRAM(XSLTPROC, xsltproc, ALL)
+DOCS_TARGET_REQUIRE_PROGRAM(RM, rm, ALL)
+dnl DOCS_TARGET_REQUIRE_PROGRAM(DIA, dia, LATEX)
+dnl DOCS_TARGET_REQUIRE_PROGRAM(DIA, dia, PS)
+dnl DOCS_TARGET_REQUIRE_PROGRAM(DIA, dia, PDF)
+dnl DOCS_TARGET_REQUIRE_PROGRAM(DIA, dia, HTML)
+dnl DOCS_TARGET_REQUIRE_PROGRAM(DIA, dia, HTMLHELP)
+dnl DOCS_TARGET_REQUIRE_PROGRAM(DIA, dia, PEARSON)
+dnl DOCS_TARGET_REQUIRE_PROGRAM(DIA, dia, PLUCKER)
+dnl DOCS_TARGET_REQUIRE_PROGRAM(DIA, dia, FOPDF)
+DOCS_TARGET_REQUIRE_PROGRAM(INKSCAPE, inkscape, LATEX)
+DOCS_TARGET_REQUIRE_PROGRAM(INKSCAPE, inkscape, PS)
+DOCS_TARGET_REQUIRE_PROGRAM(INKSCAPE, inkscape, PDF)
+DOCS_TARGET_REQUIRE_PROGRAM(INKSCAPE, inkscape, HTML)
+DOCS_TARGET_REQUIRE_PROGRAM(INKSCAPE, inkscape, HTMLHELP)
+DOCS_TARGET_REQUIRE_PROGRAM(INKSCAPE, inkscape, PEARSON)
+DOCS_TARGET_REQUIRE_PROGRAM(INKSCAPE, inkscape, PLUCKER)
+DOCS_TARGET_REQUIRE_PROGRAM(INKSCAPE, inkscape, FOPDF)
+# Check dia version number
+
+#if test -n "$DIA"; then
+#   [ DIA_VERSION=`$DIA -v | egrep -o '([0-9]+)\.([0-9]+)'`]
+#   DIA_MAJ_VERSION=`echo $DIA_VERSION | cut -d . -f 1`
+#   DIA_MIN_VERSION=`echo $DIA_VERSION | cut -d . -f 2`
+
+#   if test "$DIA_MAJ_VERSION" -le "0"
+#   then
+#	if test "$DIA_MIN_VERSION" -le "92" && test -z "$DISPLAY"
+#	then
+#		AC_MSG_ERROR([Dia below 0.93 requires an X environment. Set \$DISPLAY or install Dia 0.93 or higher])
+#	fi
+#   fi   
+#fi
+
+DOCS_TARGET_REQUIRE_PROGRAM(MAKEINDEX, makeindex, LATEX)
+DOCS_TARGET_REQUIRE_PROGRAM(PDFLATEX, pdflatex, PDF)
+DOCS_TARGET_REQUIRE_PROGRAM(EPSTOPDF, epstopdf, PDF)
+DOCS_TARGET_REQUIRE_PROGRAM(THUMBPDF, thumbpdf, PDF)
+DOCS_TARGET_REQUIRE_PROGRAM(PNGTOPNM, pngtopnm, PS)
+DOCS_TARGET_REQUIRE_PROGRAM(PNMTOPS, pnmtops, PS)
+DOCS_TARGET_REQUIRE_PROGRAM(LATEX, latex, PS)
+DOCS_TARGET_REQUIRE_PROGRAM(DVIPS, dvips, PS)
+DOCS_TARGET_REQUIRE_PROGRAM(PLUCKERBUILD, plucker-build, PLUCKER)
+DOCS_TARGET_REQUIRE_PROGRAM(HTML2TEXT, html2text, TXT)
+DOCS_TARGET_REQUIRE_PROGRAM(PERL, perl, UNDOCUMENTED)
+DOCS_TARGET_REQUIRE_PROGRAM(XMLLINT, xmllint, VALIDATE)
+DOCS_TARGET_REQUIRE_PROGRAM(FOP, fop, FOPDF)
+DOCS_TARGET_REQUIRE_PROGRAM(DB2TEXI, docbook2x-texi, TEXI)
+DOCS_TARGET_REQUIRE_PROGRAM(MAKEINFO, makeinfo, TEXIINFO)
+DOCS_TARGET_REQUIRE_DIR([$SPECIFIED_SOURCEDIR $SPECIFIED_SOURCEDIR/source ..], [param/loadparm.c], SAMBASOURCEDIR, UNDOCUMENTED)
+
+AC_MSG_RESULT([])
+AC_MSG_RESULT([Summary:])
+AC_MSG_RESULT([--------------])
+
+DOCS_DEFINE_TARGET(ALL, [], [base requirements], [])
+DOCS_DEFINE_TARGET(LATEX, ALL, [LaTeX versions], [tex])
+DOCS_DEFINE_TARGET(PDF, LATEX, [PDF versions], [pdf])
+DOCS_DEFINE_TARGET(PS, LATEX, [PostScript versions], [ps])
+DOCS_DEFINE_TARGET(HTML, ALL, [HTML versions], [html])
+DOCS_DEFINE_TARGET(HTMLHELP, ALL, [HTML Help versions], [htmlhelp])
+DOCS_DEFINE_TARGET(HTMLMAN, ALL, [HTML versions of the manpages], [htmlman3])
+DOCS_DEFINE_TARGET(MANPAGES, ALL, [manpages], [manpages3])
+DOCS_DEFINE_TARGET(PEARSON, ALL, [pearson-compatible XML], [pearson])
+DOCS_DEFINE_TARGET(PLUCKER, HTML, [plucker versions], [plucker])
+DOCS_DEFINE_TARGET(VALIDATE, ALL, [validating docbook output], [])
+DOCS_DEFINE_TARGET(FOPDF, ALL, [PDF versions thru FO], [fo-pdf])
+DOCS_DEFINE_TARGET(TEXI, ALL, [TexInfo versions], [texi])
+DOCS_DEFINE_TARGET(TEXIINFO, ALL, [TexInfo Info versions], [texiinfo])
+DOCS_DEFINE_TARGET(UNDOCUMENTED, MANPAGES, [list of undocumented options], [undocumented])
+DOCS_DEFINE_TARGET(TXT, HTML, [text versions], [txt])
+
+if test x"$TARGETS" = x; then 
+	AC_MSG_ERROR([You won't be able to build any of the docs])
+else 
+	AC_MSG_RESULT([You will be able to build: $TARGETS])
+fi
+
+AC_SUBST(TARGETS)
+
+AC_OUTPUT( Makefile.settings)
diff --git a/docs-xml/gpl-3.0.xml b/docs-xml/gpl-3.0.xml
new file mode 100644
index 00000000000..559c89dc4f0
--- /dev/null
+++ b/docs-xml/gpl-3.0.xml
@@ -0,0 +1,836 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+<appendix>
+  <title>
+    <acronym>GNU</acronym> General Public License version 3
+  </title>
+  <para>
+    Version 3, 29 June 2007
+  </para>
+  <para>
+    Copyright &copy; 2007 Free Software Foundation, Inc.
+    <ulink url="http://fsf.org/">http://fsf.org/</ulink>
+  </para>
+  <para>
+    Everyone is permitted to copy and distribute verbatim copies of this license
+    document, but changing it is not allowed.
+  </para>
+  <bridgehead renderas="sect1">
+    Preamble
+  </bridgehead>
+  <para>
+    The <acronym>GNU</acronym> General Public License is a free, copyleft
+    license for software and other kinds of works.
+  </para>
+  <para>
+    The licenses for most software and other practical works are designed to
+    take away your freedom to share and change the works.  By contrast, the
+    <acronym>GNU</acronym> General Public License is intended to guarantee your
+    freedom to share and change all versions of a program&mdash;to make sure it
+    remains free software for all its users.  We, the Free Software Foundation,
+    use the <acronym>GNU</acronym> General Public License for most of our
+    software; it applies also to any other work released this way by its
+    authors.  You can apply it to your programs, too.
+  </para>
+  <para>
+    When we speak of free software, we are referring to freedom, not price.  Our
+    General Public Licenses are designed to make sure that you have the freedom
+    to distribute copies of free software (and charge for them if you wish),
+    that you receive source code or can get it if you want it, that you can
+    change the software or use pieces of it in new free programs, and that you
+    know you can do these things.
+  </para>
+  <para>
+    To protect your rights, we need to prevent others from denying you these
+    rights or asking you to surrender the rights.  Therefore, you have certain
+    responsibilities if you distribute copies of the software, or if you modify
+    it: responsibilities to respect the freedom of others.
+  </para>
+  <para>
+    For example, if you distribute copies of such a program, whether gratis or
+    for a fee, you must pass on to the recipients the same freedoms that you
+    received.  You must make sure that they, too, receive or can get the source
+    code.  And you must show them these terms so they know their rights.
+  </para>
+  <para>
+    Developers that use the <acronym>GNU</acronym> <acronym>GPL</acronym>
+    protect your rights with two steps: (1) assert copyright on the software,
+    and (2) offer you this License giving you legal permission to copy,
+    distribute and/or modify it.
+  </para>
+  <para>
+    For the developers&rsquo; and authors&rsquo; protection, the
+    <acronym>GPL</acronym> clearly explains that there is no warranty for this
+    free software.  For both users&rsquo; and authors&rsquo; sake, the
+    <acronym>GPL</acronym> requires that modified versions be marked as changed,
+    so that their problems will not be attributed erroneously to authors of
+    previous versions.
+  </para>
+  <para>
+    Some devices are designed to deny users access to install or run modified
+    versions of the software inside them, although the manufacturer can do so.
+    This is fundamentally incompatible with the aim of protecting users&rsquo;
+    freedom to change the software.  The systematic pattern of such abuse occurs
+    in the area of products for individuals to use, which is precisely where it
+    is most unacceptable.  Therefore, we have designed this version of the
+    <acronym>GPL</acronym> to prohibit the practice for those products.  If such
+    problems arise substantially in other domains, we stand ready to extend this
+    provision to those domains in future versions of the <acronym>GPL</acronym>,
+    as needed to protect the freedom of users.
+  </para>
+  <para>
+    Finally, every program is threatened constantly by software patents.  States
+    should not allow patents to restrict development and use of software on
+    general-purpose computers, but in those that do, we wish to avoid the
+    special danger that patents applied to a free program could make it
+    effectively proprietary.  To prevent this, the <acronym>GPL</acronym>
+    assures that patents cannot be used to render the program non-free.
+  </para>
+  <para>
+    The precise terms and conditions for copying, distribution and modification
+    follow.
+  </para>
+  <bridgehead>
+    TERMS AND CONDITIONS
+  </bridgehead>
+  <bridgehead renderas="sect1">
+    0. Definitions.
+  </bridgehead>
+  <para>
+    &ldquo;This License&rdquo; refers to version 3 of the <acronym>GNU</acronym>
+    General Public License.
+  </para>
+  <para>
+    &ldquo;Copyright&rdquo; also means copyright-like laws that apply to other
+    kinds of works, such as semiconductor masks.
+  </para>
+  <para>
+    &ldquo;The Program&rdquo; refers to any copyrightable work licensed under
+    this License.  Each licensee is addressed as &ldquo;you&rdquo;.
+    &ldquo;Licensees&rdquo; and &ldquo;recipients&rdquo; may be individuals or
+    organizations.
+  </para>
+  <para>
+    To &ldquo;modify&rdquo; a work means to copy from or adapt all or part of
+    the work in a fashion requiring copyright permission, other than the making
+    of an exact copy.  The resulting work is called a &ldquo;modified
+    version&rdquo; of the earlier work or a work &ldquo;based on&rdquo; the
+    earlier work.
+  </para>
+  <para>
+    A &ldquo;covered work&rdquo; means either the unmodified Program or a work
+    based on the Program.
+  </para>
+  <para>
+    To &ldquo;propagate&rdquo; a work means to do anything with it that, without
+    permission, would make you directly or secondarily liable for infringement
+    under applicable copyright law, except executing it on a computer or
+    modifying a private copy.  Propagation includes copying, distribution (with
+    or without modification), making available to the public, and in some
+    countries other activities as well.
+  </para>
+  <para>
+    To &ldquo;convey&rdquo; a work means any kind of propagation that enables
+    other parties to make or receive copies.  Mere interaction with a user
+    through a computer network, with no transfer of a copy, is not conveying.
+  </para>
+  <para>
+    An interactive user interface displays &ldquo;Appropriate Legal
+    Notices&rdquo; to the extent that it includes a convenient and prominently
+    visible feature that (1) displays an appropriate copyright notice, and (2)
+    tells the user that there is no warranty for the work (except to the extent
+    that warranties are provided), that licensees may convey the work under this
+    License, and how to view a copy of this License.  If the interface presents
+    a list of user commands or options, such as a menu, a prominent item in the
+    list meets this criterion.
+  </para>
+  <bridgehead renderas="sect1">
+    1. Source Code.
+  </bridgehead>
+  <para>
+    The &ldquo;source code&rdquo; for a work means the preferred form of the
+    work for making modifications to it.  &ldquo;Object code&rdquo; means any
+    non-source form of a work.
+  </para>
+  <para>
+    A &ldquo;Standard Interface&rdquo; means an interface that either is an
+    official standard defined by a recognized standards body, or, in the case of
+    interfaces specified for a particular programming language, one that is
+    widely used among developers working in that language.
+  </para>
+  <para>
+    The &ldquo;System Libraries&rdquo; of an executable work include anything,
+    other than the work as a whole, that (a) is included in the normal form of
+    packaging a Major Component, but which is not part of that Major Component,
+    and (b) serves only to enable use of the work with that Major Component, or
+    to implement a Standard Interface for which an implementation is available
+    to the public in source code form.  A &ldquo;Major Component&rdquo;, in this
+    context, means a major essential component (kernel, window system, and so
+    on) of the specific operating system (if any) on which the executable work
+    runs, or a compiler used to produce the work, or an object code interpreter
+    used to run it.
+  </para>
+  <para>
+    The &ldquo;Corresponding Source&rdquo; for a work in object code form means
+    all the source code needed to generate, install, and (for an executable
+    work) run the object code and to modify the work, including scripts to
+    control those activities.  However, it does not include the work&rsquo;s
+    System Libraries, or general-purpose tools or generally available free
+    programs which are used unmodified in performing those activities but which
+    are not part of the work.  For example, Corresponding Source includes
+    interface definition files associated with source files for the work, and
+    the source code for shared libraries and dynamically linked subprograms that
+    the work is specifically designed to require, such as by intimate data
+    communication or control flow between those subprograms and other parts of
+    the work.
+  </para>
+  <para>
+    The Corresponding Source need not include anything that users can regenerate
+    automatically from other parts of the Corresponding Source.
+  </para>
+  <para>
+    The Corresponding Source for a work in source code form is that same work.
+  </para>
+  <bridgehead renderas="sect1">
+    2. Basic Permissions.
+  </bridgehead>
+  <para>
+    All rights granted under this License are granted for the term of copyright
+    on the Program, and are irrevocable provided the stated conditions are met.
+    This License explicitly affirms your unlimited permission to run the
+    unmodified Program.  The output from running a covered work is covered by
+    this License only if the output, given its content, constitutes a covered
+    work.  This License acknowledges your rights of fair use or other
+    equivalent, as provided by copyright law.
+  </para>
+  <para>
+    You may make, run and propagate covered works that you do not convey,
+    without conditions so long as your license otherwise remains in force.  You
+    may convey covered works to others for the sole purpose of having them make
+    modifications exclusively for you, or provide you with facilities for
+    running those works, provided that you comply with the terms of this License
+    in conveying all material for which you do not control copyright.  Those
+    thus making or running the covered works for you must do so exclusively on
+    your behalf, under your direction and control, on terms that prohibit them
+    from making any copies of your copyrighted material outside their
+    relationship with you.
+  </para>
+  <para>
+    Conveying under any other circumstances is permitted solely under the
+    conditions stated below.  Sublicensing is not allowed; section 10 makes it
+    unnecessary.
+  </para>
+  <bridgehead renderas="sect1">
+    3. Protecting Users&rsquo; Legal Rights From Anti-Circumvention Law.
+  </bridgehead>
+  <para>
+    No covered work shall be deemed part of an effective technological measure
+    under any applicable law fulfilling obligations under article 11 of the WIPO
+    copyright treaty adopted on 20 December 1996, or similar laws prohibiting or
+    restricting circumvention of such measures.
+  </para>
+  <para>
+    When you convey a covered work, you waive any legal power to forbid
+    circumvention of technological measures to the extent such circumvention is
+    effected by exercising rights under this License with respect to the covered
+    work, and you disclaim any intention to limit operation or modification of
+    the work as a means of enforcing, against the work&rsquo;s users, your or
+    third parties&rsquo; legal rights to forbid circumvention of technological
+    measures.
+  </para>
+  <bridgehead renderas="sect1">
+    4. Conveying Verbatim Copies.
+  </bridgehead>
+  <para>
+    You may convey verbatim copies of the Program&rsquo;s source code as you
+    receive it, in any medium, provided that you conspicuously and appropriately
+    publish on each copy an appropriate copyright notice; keep intact all
+    notices stating that this License and any non-permissive terms added in
+    accord with section 7 apply to the code; keep intact all notices of the
+    absence of any warranty; and give all recipients a copy of this License
+    along with the Program.
+  </para>
+  <para>
+    You may charge any price or no price for each copy that you convey, and you
+    may offer support or warranty protection for a fee.
+  </para>
+  <bridgehead renderas="sect1">
+    5. Conveying Modified Source Versions.
+  </bridgehead>
+  <para>
+    You may convey a work based on the Program, or the modifications to produce
+    it from the Program, in the form of source code under the terms of section
+    4, provided that you also meet all of these conditions:
+  </para>
+  <orderedlist numeration="loweralpha">
+    <listitem>
+      <para>
+        The work must carry prominent notices stating that you modified it, and
+        giving a relevant date.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The work must carry prominent notices stating that it is released under
+        this License and any conditions added under section 7.  This requirement
+        modifies the requirement in section 4 to &ldquo;keep intact all
+        notices&rdquo;.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        You must license the entire work, as a whole, under this License to
+        anyone who comes into possession of a copy.  This License will therefore
+        apply, along with any applicable section 7 additional terms, to the
+        whole of the work, and all its parts, regardless of how they are
+        packaged.  This License gives no permission to license the work in any
+        other way, but it does not invalidate such permission if you have
+        separately received it.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        If the work has interactive user interfaces, each must display
+        Appropriate Legal Notices; however, if the Program has interactive
+        interfaces that do not display Appropriate Legal Notices, your work need
+        not make them do so.
+      </para>
+    </listitem>
+  </orderedlist>
+  <para>
+    A compilation of a covered work with other separate and independent works,
+    which are not by their nature extensions of the covered work, and which are
+    not combined with it such as to form a larger program, in or on a volume of
+    a storage or distribution medium, is called an &ldquo;aggregate&rdquo; if
+    the compilation and its resulting copyright are not used to limit the access
+    or legal rights of the compilation&rsquo;s users beyond what the individual works
+    permit.  Inclusion of a covered work in an aggregate does not cause
+    this License to apply to the other parts of the aggregate.
+  </para>
+  <bridgehead renderas="sect1">
+    6. Conveying Non-Source Forms.
+  </bridgehead>
+  <para>
+    You may convey a covered work in object code form under the terms of
+    sections 4 and 5, provided that you also convey the machine-readable
+    Corresponding Source under the terms of this License, in one of these ways:
+  </para>
+  <orderedlist numeration="loweralpha">
+    <listitem>
+      <para>
+        Convey the object code in, or embodied in, a physical product (including
+        a physical distribution medium), accompanied by the Corresponding Source
+        fixed on a durable physical medium customarily used for software
+        interchange.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey the object code in, or embodied in, a physical product (including
+        a physical distribution medium), accompanied by a written offer, valid
+        for at least three years and valid for as long as you offer spare parts
+        or customer support for that product model, to give anyone who possesses
+        the object code either (1) a copy of the Corresponding Source for all
+        the software in the product that is covered by this License, on a
+        durable physical medium customarily used for software interchange, for a
+        price no more than your reasonable cost of physically performing this
+        conveying of source, or (2) access to copy the Corresponding Source from
+        a network server at no charge.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey individual copies of the object code with a copy of the written
+        offer to provide the Corresponding Source.  This alternative is allowed
+        only occasionally and noncommercially, and only if you received the
+        object code with such an offer, in accord with subsection 6b.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey the object code by offering access from a designated place
+        (gratis or for a charge), and offer equivalent access to the
+        Corresponding Source in the same way through the same place at no
+        further charge.  You need not require recipients to copy the
+        Corresponding Source along with the object code.  If the place to copy
+        the object code is a network server, the Corresponding Source may be on
+        a different server (operated by you or a third party) that supports
+        equivalent copying facilities, provided you maintain clear directions
+        next to the object code saying where to find the Corresponding Source.
+        Regardless of what server hosts the Corresponding Source, you remain
+        obligated to ensure that it is available for as long as needed to
+        satisfy these requirements.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Convey the object code using peer-to-peer transmission, provided you
+        inform other peers where the object code and Corresponding Source of the
+        work are being offered to the general public at no charge under
+        subsection 6d.
+      </para>
+    </listitem>
+  </orderedlist>
+  <para>
+    A separable portion of the object code, whose source code is excluded from
+    the Corresponding Source as a System Library, need not be included in
+    conveying the object code work.
+  </para>
+  <para>
+    A &ldquo;User Product&rdquo; is either (1) a &ldquo;consumer product&rdquo;,
+    which means any tangible personal property which is normally used for
+    personal, family, or household purposes, or (2) anything designed or sold
+    for incorporation into a dwelling.  In determining whether a product is a
+    consumer product, doubtful cases shall be resolved in favor of coverage.
+    For a particular product received by a particular user, &ldquo;normally
+    used&rdquo; refers to a typical or common use of that class of product,
+    regardless of the status of the particular user or of the way in which the
+    particular user actually uses, or expects or is expected to use, the
+    product.  A product is a consumer product regardless of whether the product
+    has substantial commercial, industrial or non-consumer uses, unless such
+    uses represent the only significant mode of use of the product.
+  </para>
+  <para>
+    &ldquo;Installation Information&rdquo; for a User Product means any methods,
+    procedures, authorization keys, or other information required to install and
+    execute modified versions of a covered work in that User Product from a
+    modified version of its Corresponding Source.  The information must suffice
+    to ensure that the continued functioning of the modified object code is in
+    no case prevented or interfered with solely because modification has been
+    made.
+  </para>
+  <para>
+    If you convey an object code work under this section in, or with, or
+    specifically for use in, a User Product, and the conveying occurs as part of
+    a transaction in which the right of possession and use of the User Product
+    is transferred to the recipient in perpetuity or for a fixed term
+    (regardless of how the transaction is characterized), the Corresponding
+    Source conveyed under this section must be accompanied by the Installation
+    Information.  But this requirement does not apply if neither you nor any
+    third party retains the ability to install modified object code on the User
+    Product (for example, the work has been installed in
+    <acronym>ROM</acronym>).
+  </para>
+  <para>
+    The requirement to provide Installation Information does not include a
+    requirement to continue to provide support service, warranty, or updates for
+    a work that has been modified or installed by the recipient, or for the User
+    Product in which it has been modified or installed.  Access to a network may
+    be denied when the modification itself materially and adversely affects the
+    operation of the network or violates the rules and protocols for
+    communication across the network.
+  </para>
+  <para>
+    Corresponding Source conveyed, and Installation Information provided, in
+    accord with this section must be in a format that is publicly documented
+    (and with an implementation available to the public in source code form),
+    and must require no special password or key for unpacking, reading or
+    copying.
+  </para>
+   <bridgehead renderas="sect1">
+     7. Additional Terms.
+   </bridgehead>
+   <para>
+     &ldquo;Additional permissions&rdquo; are terms that supplement the terms of
+     this License by making exceptions from one or more of its conditions.
+     Additional permissions that are applicable to the entire Program shall be
+     treated as though they were included in this License, to the extent that
+     they are valid under applicable law.  If additional permissions apply only
+     to part of the Program, that part may be used separately under those
+     permissions, but the entire Program remains governed by this License
+     without regard to the additional permissions.
+   </para>
+   <para>
+     When you convey a copy of a covered work, you may at your option remove any
+     additional permissions from that copy, or from any part of it.  (Additional
+     permissions may be written to require their own removal in certain cases
+     when you modify the work.)  You may place additional permissions on
+     material, added by you to a covered work, for which you have or can give
+     appropriate copyright permission.
+   </para>
+   <para>
+     Notwithstanding any other provision of this License, for material you add
+     to a covered work, you may (if authorized by the copyright holders of that
+     material) supplement the terms of this License with terms:
+   </para>
+   <orderedlist numeration="loweralpha">
+     <listitem>
+       <para>
+         Disclaiming warranty or limiting liability differently from the terms
+         of sections 15 and 16 of this License; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Requiring preservation of specified reasonable legal notices or author
+         attributions in that material or in the Appropriate Legal Notices
+         displayed by works containing it; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Prohibiting misrepresentation of the origin of that material, or
+         requiring that modified versions of such material be marked in
+         reasonable ways as different from the original version; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Limiting the use for publicity purposes of names of licensors or
+         authors of the material; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Declining to grant rights under trademark law for use of some trade
+         names, trademarks, or service marks; or
+       </para>
+     </listitem>
+     <listitem>
+       <para>
+         Requiring indemnification of licensors and authors of that material by
+         anyone who conveys the material (or modified versions of it) with
+         contractual assumptions of liability to the recipient, for any
+         liability that these contractual assumptions directly impose on those
+         licensors and authors.
+       </para>
+     </listitem>
+   </orderedlist>
+   <para>
+     All other non-permissive additional terms are considered &ldquo;further
+     restrictions&rdquo; within the meaning of section 10.  If the Program as
+     you received it, or any part of it, contains a notice stating that it is
+     governed by this License along with a term that is a further restriction,
+     you may remove that term.  If a license document contains a further
+     restriction but permits relicensing or conveying under this License, you
+     may add to a covered work material governed by the terms of that license
+     document, provided that the further restriction does not survive such
+     relicensing or conveying.
+   </para>
+   <para>
+     If you add terms to a covered work in accord with this section, you must
+     place, in the relevant source files, a statement of the additional terms
+     that apply to those files, or a notice indicating where to find the
+     applicable terms.
+   </para>
+   <para>
+     Additional terms, permissive or non-permissive, may be stated in the form
+     of a separately written license, or stated as exceptions; the above
+     requirements apply either way.
+   </para>
+   <bridgehead renderas="sect1">
+     8. Termination.
+   </bridgehead>
+   <para>
+     You may not propagate or modify a covered work except as expressly provided
+     under this License.  Any attempt otherwise to propagate or modify it is
+     void, and will automatically terminate your rights under this License
+     (including any patent licenses granted under the third paragraph of section
+     11).
+   </para>
+   <para>
+     However, if you cease all violation of this License, then your license from
+     a particular copyright holder is reinstated (a) provisionally, unless and
+     until the copyright holder explicitly and finally terminates your license,
+     and (b) permanently, if the copyright holder fails to notify you of the
+     violation by some reasonable means prior to 60 days after the cessation.
+   </para>
+   <para>
+     Moreover, your license from a particular copyright holder is reinstated
+     permanently if the copyright holder notifies you of the violation by some
+     reasonable means, this is the first time you have received notice of
+     violation of this License (for any work) from that copyright holder, and
+     you cure the violation prior to 30 days after your receipt of the notice.
+   </para>
+   <para>
+     Termination of your rights under this section does not terminate the
+     licenses of parties who have received copies or rights from you under this
+     License.  If your rights have been terminated and not permanently
+     reinstated, you do not qualify to receive new licenses for the same
+     material under section 10.
+   </para>
+   <bridgehead renderas="sect1">
+     9. Acceptance Not Required for Having Copies.
+   </bridgehead>
+   <para>
+     You are not required to accept this License in order to receive or run a
+     copy of the Program.  Ancillary propagation of a covered work occurring
+     solely as a consequence of using peer-to-peer transmission to receive a
+     copy likewise does not require acceptance.  However, nothing other than
+     this License grants you permission to propagate or modify any covered work.
+     These actions infringe copyright if you do not accept this License.
+     Therefore, by modifying or propagating a covered work, you indicate your
+     acceptance of this License to do so.
+   </para>
+   <bridgehead renderas="sect1">
+     10. Automatic Licensing of Downstream Recipients.
+   </bridgehead>
+   <para>
+     Each time you convey a covered work, the recipient automatically receives a
+     license from the original licensors, to run, modify and propagate that
+     work, subject to this License.  You are not responsible for enforcing
+     compliance by third parties with this License.
+   </para>
+   <para>
+     An &ldquo;entity transaction&rdquo; is a transaction transferring control
+     of an organization, or substantially all assets of one, or subdividing an
+     organization, or merging organizations.  If propagation of a covered work
+     results from an entity transaction, each party to that transaction who
+     receives a copy of the work also receives whatever licenses to the work the
+     party&rsquo;s predecessor in interest had or could give under the previous
+     paragraph, plus a right to possession of the Corresponding Source of the
+     work from the predecessor in interest, if the predecessor has it or can get
+     it with reasonable efforts.
+   </para>
+   <para>
+     You may not impose any further restrictions on the exercise of the rights
+     granted or affirmed under this License.  For example, you may not impose a
+     license fee, royalty, or other charge for exercise of rights granted under
+     this License, and you may not initiate litigation (including a cross-claim
+     or counterclaim in a lawsuit) alleging that any patent claim is infringed
+     by making, using, selling, offering for sale, or importing the Program or
+     any portion of it.
+   </para>
+  <bridgehead renderas="sect1">
+    11. Patents.
+  </bridgehead>
+  <para>
+    A &ldquo;contributor&rdquo; is a copyright holder who authorizes use under
+    this License of the Program or a work on which the Program is based.  The
+    work thus licensed is called the contributor&rsquo;s &ldquo;contributor
+    version&rdquo;.
+  </para>
+  <para>
+    A contributor&rsquo;s &ldquo;essential patent claims&rdquo; are all patent
+    claims owned or controlled by the contributor, whether already acquired or
+    hereafter acquired, that would be infringed by some manner, permitted by
+    this License, of making, using, or selling its contributor version, but do
+    not include claims that would be infringed only as a consequence of further
+    modification of the contributor version.  For purposes of this definition,
+    &ldquo;control&rdquo; includes the right to grant patent sublicenses in a
+    manner consistent with the requirements of this License.
+  </para>
+  <para>
+    Each contributor grants you a non-exclusive, worldwide, royalty-free patent
+    license under the contributor&rsquo;s essential patent claims, to make, use,
+    sell, offer for sale, import and otherwise run, modify and propagate the
+    contents of its contributor version.
+  </para>
+  <para>
+    In the following three paragraphs, a &ldquo;patent license&rdquo; is any
+    express agreement or commitment, however denominated, not to enforce a
+    patent (such as an express permission to practice a patent or covenant not
+    to sue for patent infringement).  To &ldquo;grant&rdquo; such a patent
+    license to a party means to make such an agreement or commitment not to
+    enforce a patent against the party.
+  </para>
+  <para>
+    If you convey a covered work, knowingly relying on a patent license, and the
+    Corresponding Source of the work is not available for anyone to copy, free
+    of charge and under the terms of this License, through a publicly available
+    network server or other readily accessible means, then you must either (1)
+    cause the Corresponding Source to be so available, or (2) arrange to deprive
+    yourself of the benefit of the patent license for this particular work, or
+    (3) arrange, in a manner consistent with the requirements of this License,
+    to extend the patent license to downstream recipients.  &ldquo;Knowingly
+    relying&rdquo; means you have actual knowledge that, but for the patent
+    license, your conveying the covered work in a country, or your
+    recipient&rsquo;s use of the covered work in a country, would infringe one
+    or more identifiable patents in that country that you have reason to believe
+    are valid.
+  </para>
+  <para>
+    If, pursuant to or in connection with a single transaction or arrangement,
+    you convey, or propagate by procuring conveyance of, a covered work, and
+    grant a patent license to some of the parties receiving the covered work
+    authorizing them to use, propagate, modify or convey a specific copy of the
+    covered work, then the patent license you grant is automatically extended to
+    all recipients of the covered work and works based on it.
+  </para>
+  <para>
+    A patent license is &ldquo;discriminatory&rdquo; if it does not include
+    within the scope of its coverage, prohibits the exercise of, or is
+    conditioned on the non-exercise of one or more of the rights that are
+    specifically granted under this License.  You may not convey a covered work
+    if you are a party to an arrangement with a third party that is in the
+    business of distributing software, under which you make payment to the third
+    party based on the extent of your activity of conveying the work, and under
+    which the third party grants, to any of the parties who would receive the
+    covered work from you, a discriminatory patent license (a) in connection
+    with copies of the covered work conveyed by you (or copies made from those
+    copies), or (b) primarily for and in connection with specific products or
+    compilations that contain the covered work, unless you entered into that
+    arrangement, or that patent license was granted, prior to 28 March 2007.
+  </para>
+  <para>
+    Nothing in this License shall be construed as excluding or limiting any
+    implied license or other defenses to infringement that may otherwise be
+    available to you under applicable patent law.
+  </para>
+  <bridgehead renderas="sect1">
+    12. No Surrender of Others&rsquo; Freedom.
+  </bridgehead>
+  <para>
+    If conditions are imposed on you (whether by court order, agreement or
+    otherwise) that contradict the conditions of this License, they do not
+    excuse you from the conditions of this License.  If you cannot convey a
+    covered work so as to satisfy simultaneously your obligations under this
+    License and any other pertinent obligations, then as a consequence you may
+    not convey it at all.  For example, if you agree to terms that obligate you
+    to collect a royalty for further conveying from those to whom you convey the
+    Program, the only way you could satisfy both those terms and this License
+    would be to refrain entirely from conveying the Program.
+  </para>
+  <bridgehead renderas="sect1">
+    13. Use with the <acronym>GNU</acronym> Affero General Public License.
+  </bridgehead>
+  <para>
+    Notwithstanding any other provision of this License, you have permission to
+    link or combine any covered work with a work licensed under version 3 of the
+    <acronym>GNU</acronym> Affero General Public License into a single combined
+    work, and to convey the resulting work.  The terms of this License will
+    continue to apply to the part which is the covered work, but the special
+    requirements of the <acronym>GNU</acronym> Affero General Public License,
+    section 13, concerning interaction through a network will apply to the
+    combination as such.
+  </para>
+  <bridgehead renderas="sect1">
+    14. Revised Versions of this License.
+  </bridgehead>
+  <para>
+    The Free Software Foundation may publish revised and/or new versions of the
+    <acronym>GNU</acronym> General Public License from time to time.  Such new
+    versions will be similar in spirit to the present version, but may differ in
+    detail to address new problems or concerns.
+  </para>
+  <para>
+    Each version is given a distinguishing version number.  If the Program
+    specifies that a certain numbered version of the <acronym>GNU</acronym>
+    General Public License &ldquo;or any later version&rdquo; applies to it, you
+    have the option of following the terms and conditions either of that
+    numbered version or of any later version published by the Free Software
+    Foundation.  If the Program does not specify a version number of the
+    <acronym>GNU</acronym> General Public License, you may choose any version
+    ever published by the Free Software Foundation.
+  </para>
+  <para>
+    If the Program specifies that a proxy can decide which future versions of
+    the <acronym>GNU</acronym> General Public License can be used, that
+    proxy&rsquo;s public statement of acceptance of a version permanently
+    authorizes you to choose that version for the Program.
+  </para>
+  <para>
+    Later license versions may give you additional or different permissions.
+    However, no additional obligations are imposed on any author or copyright
+    holder as a result of your choosing to follow a later version.
+  </para>
+  <bridgehead renderas="sect1">
+    15. Disclaimer of Warranty.
+  </bridgehead>
+  <para>
+    THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
+    LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+    OTHER PARTIES PROVIDE THE PROGRAM &ldquo;AS IS&rdquo; WITHOUT WARRANTY OF
+    ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+    THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
+    YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
+    NECESSARY SERVICING, REPAIR OR CORRECTION.
+  </para>
+  <bridgehead renderas="sect1">
+    16. Limitation of Liability.
+  </bridgehead>
+  <para>
+    IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
+    ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
+    PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+    GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE
+    OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA
+    OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+    PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+    EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+    SUCH DAMAGES.
+  </para>
+  <bridgehead renderas="sect1">
+    17. Interpretation of Sections 15 and 16.
+  </bridgehead>
+  <para>
+    If the disclaimer of warranty and limitation of liability provided above
+    cannot be given local legal effect according to their terms, reviewing
+    courts shall apply local law that most closely approximates an absolute
+    waiver of all civil liability in connection with the Program, unless a
+    warranty or assumption of liability accompanies a copy of the Program in
+    return for a fee.
+  </para>
+  <bridgehead>
+    END OF TERMS AND CONDITIONS
+  </bridgehead>
+  <bridgehead renderas="sect1">
+    How to Apply These Terms to Your New Programs
+  </bridgehead>
+  <para>
+    If you develop a new program, and you want it to be of the greatest possible
+    use to the public, the best way to achieve this is to make it free software
+    which everyone can redistribute and change under these terms.
+  </para>
+  <para>
+    To do so, attach the following notices to the program.  It is safest to
+    attach them to the start of each source file to most effectively state the
+    exclusion of warranty; and each file should have at least the
+    &ldquo;copyright&rdquo; line and a pointer to where the full notice is
+    found.
+  </para>
+  <screen>
+<replaceable>one line to give the program&rsquo;s name and a brief idea of what it does.</replaceable>
+Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the <acronym>GNU</acronym> General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+<acronym>GNU</acronym> General Public License for more details.
+
+You should have received a copy of the <acronym>GNU</acronym> General Public License
+along with this program.  If not, see <ulink url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
+  </screen>
+  <para>
+    Also add information on how to contact you by electronic and paper mail.
+  </para>
+  <para>
+    If the program does terminal interaction, make it output a short notice like
+    this when it starts in an interactive mode:
+  </para>
+  <screen>
+<replaceable>program</replaceable> Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
+This program comes with ABSOLUTELY NO WARRANTY; for details type &lsquo;<literal>show w</literal>&rsquo;.
+This is free software, and you are welcome to redistribute it
+under certain conditions; type &lsquo;<literal>show c</literal>&rsquo; for details.
+  </screen>
+  <para>
+    The hypothetical commands &lsquo;<literal>show w</literal>&rsquo; and
+    &lsquo;<literal>show c</literal>&rsquo; should show the appropriate parts of
+    the General Public License.  Of course, your program&rsquo;s commands might be
+    different; for a GUI interface, you would use an &ldquo;about box&rdquo;.
+  </para>
+  <para>
+    You should also get your employer (if you work as a programmer) or school,
+    if any, to sign a &ldquo;copyright disclaimer&rdquo; for the program, if
+    necessary.  For more information on this, and how to apply and follow the
+    <acronym>GNU</acronym> <acronym>GPL</acronym>, see <ulink
+    url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
+  </para>
+  <para>
+    The <acronym>GNU</acronym> General Public License does not permit
+    incorporating your program into proprietary programs.  If your program is a
+    subroutine library, you may consider it more useful to permit linking
+    proprietary applications with the library.  If this is what you want to do,
+    use the <acronym>GNU</acronym> Lesser General Public License instead of this
+    License.  But first, please read <ulink
+    url="http://www.gnu.org/philosophy/why-not-lgpl.html">http://www.gnu.org/philosophy/why-not-lgpl.html</ulink>.
+  </para>
+</appendix>
diff --git a/docs-xml/htmldocs.html b/docs-xml/htmldocs.html
new file mode 100644
index 00000000000..e22808c535a
--- /dev/null
+++ b/docs-xml/htmldocs.html
@@ -0,0 +1,41 @@
+<html>
+<head><title>Samba documentation collection</title>
+<link rel="stylesheet" href="samba.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<hr>
+<div class="book" lang="en">
+ <div class="titlepage">
+  <h1 class="title"><a name="Samba documentation collection"></a>Samba documentation collection</h1>
+ </div>
+</div>
+<hr>
+<table>
+ <td valign="top">SAMBA <a href="Samba3-Developers-Guide/index.html">Developers</a> Guide</td>
+ <td valign="top">This book is a collection of documents that might be useful for people developing samba or those interested in doing so. It's nothing more than a collection of documents written by samba developers about the internals of various parts of samba and the SMB protocol. It's still (and will always be) incomplete.</td>
+</tr>
+<tr>
+<td valign="top">Samba-3 by <a href="Samba3-ByExample/index.html">Example</a></td>
+ <td valign="top">Practical Exercises in Successful Samba Deployment.</td>
+</tr>
+<tr>
+ <td valign="top">The Official Samba-3 <a href="Samba3-HOWTO/index.html">HOWTO</a> and Reference Guide</td>
+ <td valign="top">This book provides example configurations, it documents key aspects of Microsoft Windows networking, provides in-depth insight into the important configuration of Samba-3, and helps to put all of these into a useful framework.</td>
+</tr>
+<tr>
+ <td valign="top"><a href="using_samba/toc.html">Using Samba</a>, 2nd Edition</td>
+ <td valign="top"><i>Using Samba</i>, Second Edition is a comprehensive guide to Samba administration. It covers all versions of Samba from 2.0 to 2.2, including selected features from an alpha version of 3.0, as well as the SWAT graphical configuration tool. Updated for Windows 2000, ME, and XP, the book also explores Samba's new role as a primary domain controller and domain member server, its support for the use of Windows NT/2000/XP authentication and filesystem security on the host Unix system, and accessing shared files and printers from Unix clients.</td>
+</tr>
+<tr>
+ <td valign="top"><a href="manpages/index.html">Man pages</a></td>
+ <td valign="top">The Samba man pages in HTML.</td>
+</tr>
+<tr>
+ <td valign="top"><a href="../../WHATSNEW.txt">WHATSNEW</a></td>
+  <td valign="top">Samba Release Notes.</td>
+</tr>
+<tr>
+ <td valign="top"><a href="../../README.VENDOR">README.VENDOR</a></td>
+  <td valign="top">VENDOR specific information.</td>
+</tr>
+</table></body></html>
diff --git a/docs-xml/linux-client/linux-cifs-client-guide.odt b/docs-xml/linux-client/linux-cifs-client-guide.odt
new file mode 100644
index 00000000000..f35b807760f
--- /dev/null
+++ b/docs-xml/linux-client/linux-cifs-client-guide.odt
diff --git a/docs-xml/manpages-3/eventlogadm.8.xml b/docs-xml/manpages-3/eventlogadm.8.xml
new file mode 100644
index 00000000000..04ba0220322
--- /dev/null
+++ b/docs-xml/manpages-3/eventlogadm.8.xml
@@ -0,0 +1,252 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="eventlogadm.8">
+
+<refmeta>
+	<refentrytitle>eventlogadm</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>eventlogadm</refname>
+	<refpurpose>push records into the Samba event log store</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+
+		<command>eventlogadm</command>
+		<arg><option>-d</option></arg>
+		<arg><option>-h</option></arg>
+		<arg choice="plain"><option>-o</option>
+		<literal>addsource</literal>
+		<replaceable>EVENTLOG</replaceable>
+		<replaceable>SOURCENAME</replaceable>
+		<replaceable>MSGFILE</replaceable>
+		</arg>
+
+	</cmdsynopsis>
+	<cmdsynopsis>
+		<command>eventlogadm</command>
+		<arg><option>-d</option></arg>
+		<arg><option>-h</option></arg>
+		<arg choice="plain"><option>-o</option>
+		<literal>write</literal>
+		<replaceable>EVENTLOG</replaceable>
+		</arg>
+
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> suite.</para>
+
+	<para><command>eventlogadm</command> is a filter that accepts
+	formatted event log records on standard input and writes them
+	to the Samba event log store. Windows client can then manipulate
+	these record using the usual administration tools.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term><option>-d</option></term>
+		<listitem><para>
+		The <command>-d</command> option causes <command>eventlogadm</command> to emit debugging
+		information.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>
+		<option>-o</option>
+		<literal>addsource</literal>
+		<replaceable>EVENTLOG</replaceable>
+		<replaceable>SOURCENAME</replaceable>
+		<replaceable>MSGFILE</replaceable>
+		</term>
+		<listitem><para>
+		The <command>-o addsource</command> option creates a
+		new event log source.
+		</para> </listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>
+		<option>-o</option>
+		<literal>write</literal>
+		<replaceable>EVENTLOG</replaceable>
+		</term>
+		<listitem><para>
+		The <command>-o write</command> reads event log
+		records from standard input and writes them to theSamba
+		event log store named by EVENTLOG.
+		</para> </listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>-h</option></term>
+		<listitem><para>
+		Print usage information.
+		</para></listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>EVENTLOG RECORD FORMAT</title>
+
+	<para>For the write operation, <command>eventlogadm</command>
+	expects to be able to read structured records from standard
+	input. These records are a sequence of lines, with the record key
+	and data separated by a colon character. Records are separated
+	by at least one or more blank line.</para>
+
+	<para>The event log record field are:</para>
+	<itemizedlist>
+
+		<listitem><para>
+		<command>LEN</command> - This field should be 0, since <command>eventlogadm</command> will calculate this value.
+		</para></listitem>
+
+		<listitem><para>
+		<command>RS1</command> - This must be the value 1699505740.
+		</para></listitem>
+
+		<listitem><para>
+		<command>RCN</command> -  This field should be 0.
+		</para></listitem>
+
+		<listitem><para>
+		<command>TMG</command> - The time the eventlog record
+		was generated; format is the number of seconds since
+		00:00:00 January 1, 1970, UTC.
+		</para></listitem>
+
+		<listitem><para>
+		<command>TMW</command> - The time the eventlog record was
+		written; format is the number of seconds since 00:00:00
+		January 1, 1970, UTC.
+		</para></listitem>
+
+		<listitem><para>
+		<command>EID</command> - The eventlog ID.
+		</para></listitem>
+
+		<listitem><para>
+		<command>ETP</command> - The event type -- one of
+		&quot;INFO&quot;,
+		&quot;ERROR&quot;, &quot;WARNING&quot;, &quot;AUDIT
+		SUCCESS&quot; or &quot;AUDIT FAILURE&quot;.
+		</para></listitem>
+
+		<listitem><para>
+		<command>ECT</command> - The event category; this depends
+		on the message file. It is primarily used as a means of
+		filtering in the eventlog viewer.
+		</para></listitem>
+
+		<listitem><para>
+		<command>RS2</command> - This field should be 0.
+		</para></listitem>
+
+		<listitem><para>
+		<command>CRN</command> - This field should be 0.
+		</para></listitem>
+
+		<listitem><para>
+		<command>USL</command> - This field should be 0.
+		</para></listitem>
+
+		<listitem><para>
+		<command>SRC</command> - This field contains the source
+		name associated with the event log. If a message file is
+		used with an event log, there will be a registry entry
+		for associating this source name with a message file DLL.
+		</para></listitem>
+
+		<listitem><para>
+		<command>SRN</command> - he name of the machine on
+		which the eventlog was generated. This is typically the
+		host name.
+		</para></listitem>
+
+		<listitem><para>
+		<command>STR</command> - The text associated with the
+		eventlog. There may be more than one string in a record.
+		</para></listitem>
+
+		<listitem><para>
+		<command>DAT</command> - This field should be left unset.
+		</para></listitem>
+
+	</itemizedlist>
+
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+	<para>An example of the record format accepted by <command>eventlogadm</command>:</para>
+
+	<programlisting>
+	LEN: 0
+	RS1: 1699505740
+	RCN: 0
+	TMG: 1128631322
+	TMW: 1128631322
+	EID: 1000
+	ETP: INFO
+	ECT: 0
+	RS2: 0
+	CRN: 0
+	USL: 0
+	SRC: cron
+	SRN: dmlinux
+	STR: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
+	DAT:
+	</programlisting>
+
+	<para>Set up an eventlog source, specifying a message file DLL:</para>
+	<programlisting>
+	eventlogadm -o addsource Application MyApplication | \\
+	    	%SystemRoot%/system32/MyApplication.dll
+	</programlisting>
+
+	<para>Filter messages from the system log into an event log:</para>
+	<programlisting>
+	tail -f /var/log/messages | \\
+		my_program_to_parse_into_eventlog_records | \\
+	      	eventlogadm SystemLogEvents
+	</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para> The original Samba software and related utilities were
+	created by Andrew Tridgell.  Samba is now developed by the
+	Samba Team as an Open Source project similar to the way the
+	Linux kernel is developed.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/findsmb.1.xml b/docs-xml/manpages-3/findsmb.1.xml
new file mode 100644
index 00000000000..9161dc4f14a
--- /dev/null
+++ b/docs-xml/manpages-3/findsmb.1.xml
@@ -0,0 +1,153 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="findsmb.1">
+
+<refmeta>
+	<refentrytitle>findsmb</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>findsmb</refname>
+	<refpurpose>list info about machines that respond to SMB 
+	name queries on a subnet</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>findsmb</command>
+		<arg choice="opt">subnet broadcast address</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+	
+	<para>This perl script is part of the <citerefentry>
+	<refentrytitle>samba</refentrytitle><manvolnum>7</manvolnum></citerefentry>
+	suite.</para>
+
+	<para><command>findsmb</command> is a perl script that
+	prints out several pieces of information about machines 
+	on a subnet that respond to SMB  name query requests.
+	It uses <citerefentry><refentrytitle>nmblookup</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+	and <citerefentry><refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+	to obtain this information.
+	</para>
+</refsect1>		
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-r</term>
+		<listitem><para>Controls whether <command>findsmb</command> takes
+		bugs in Windows95 into account when trying to find a Netbios name
+		registered of the remote machine. This option is disabled by default
+		because it is specific to Windows 95 and Windows 95 machines only. 
+		If set, <citerefentry><refentrytitle>nmblookup</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+		will be called with <constant>-B</constant> option.</para></listitem>
+		</varlistentry>
+		<varlistentry>
+		<term>subnet broadcast address</term>
+		<listitem><para>Without this option, <command>findsmb
+		</command> will probe the subnet of the machine where 
+		<citerefentry><refentrytitle>findsmb</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+		is run. This value is passed to 
+		<citerefentry><refentrytitle>nmblookup</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+		as part of the <constant>-B</constant> option.</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>The output of <command>findsmb</command> lists the following 
+	information for all machines that respond to the initial 
+	<command>nmblookup</command> for any name: IP address, NetBIOS name, 
+	Workgroup name, operating system, and SMB server version.</para>
+
+	<para>There will be a '+' in front of the workgroup name for 
+	machines that are local master browsers for that workgroup. There 
+	will be an '*' in front of the workgroup name for 
+	machines that are the domain master browser for that workgroup. 
+	Machines that are running Windows for Workgroups, Windows 95 or 
+	Windows 98 will 
+	not show any information about the operating system or server 
+	version.</para>
+
+	<para>The command with <constant>-r</constant> option
+	must be run on a system without <citerefentry>
+	<refentrytitle>nmbd</refentrytitle><manvolnum>8</manvolnum>
+	</citerefentry>	running. 
+
+	If <command>nmbd</command> is running on the system, you will 
+	only  get the IP address and the DNS name of the machine. To 
+	get proper responses  from Windows 95 and Windows 98 machines, 
+	the command must be run as root and with <constant>-r</constant>
+	option on a machine without <command>nmbd</command> running.</para>
+
+	<para>For example, running <command>findsmb</command> 
+	without <constant>-r</constant> option set would yield output similar
+	to the following</para>
+
+<programlisting>
+IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION 
+--------------------------------------------------------------------- 
+192.168.35.10   MINESET-TEST1  [DMVENGR]
+192.168.35.55   LINUXBOX      *[MYGROUP] [Unix] [Samba 2.0.6]
+192.168.35.56   HERBNT2        [HERB-NT]
+192.168.35.63   GANDALF        [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
+192.168.35.65   SAUNA          [WORKGROUP] [Unix] [Samba 1.9.18p10]
+192.168.35.71   FROGSTAR       [ENGR] [Unix] [Samba 2.0.0 for IRIX]
+192.168.35.78   HERBDHCP1     +[HERB]
+192.168.35.88   SCNT2         +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
+192.168.35.93   FROGSTAR-PC    [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
+192.168.35.97   HERBNT1       *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
+</programlisting>
+
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry>
+	<refentrytitle>nmbd</refentrytitle><manvolnum>8</manvolnum>
+	</citerefentry>,
+	<citerefentry><refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum>
+	</citerefentry>, and <citerefentry><refentrytitle>nmblookup</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink 
+	url="ftp://ftp.icce.rug.nl/pub/unix/">ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 
+	and updated for the Samba 2.0 release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook
+	XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/idmap_ad.8.xml b/docs-xml/manpages-3/idmap_ad.8.xml
new file mode 100644
index 00000000000..766eb850902
--- /dev/null
+++ b/docs-xml/manpages-3/idmap_ad.8.xml
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="idmap_ad.8">
+
+<refmeta>
+	<refentrytitle>idmap_ad</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>idmap_ad</refname>
+	<refpurpose>Samba's idmap_ad Backend for Winbind</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<title>DESCRIPTION</title>
+	<para>The idmap_ad plugin provides a way for Winbind to read
+	id mappings from an AD server that uses RFC2307/SFU schema
+	extensions. This module implements only the &quot;idmap&quot;
+	API, and is READONLY. Mappings must be provided in advance
+	by the administrator by adding the posixAccount/posixGroup
+	classess and relative attribute/value pairs to the users and
+	groups objects in AD</para>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>IDMAP OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>range = low - high</term>
+		<listitem><para>
+			Defines the available matching uid and gid range for which the
+			backend is authoritative. Note that the range acts as a filter.
+			If specified any UID or GID stored in AD that fall outside the
+			range is ignored and the corresponding map is discarded.
+			It is intended as a way to avoid accidental UID/GID overlaps
+			between local and remotely defined IDs.
+		</para></listitem>
+		</varlistentry>
+		<varlistentry>
+		<term>schema_mode = &lt;rfc2307 | sfu &gt;</term>
+		<listitem><para>
+			Defines the schema that idmap_ad should use when querying
+			Active Directory regarding user and group information.
+			This can either the RFC2307 schema support included
+			in Windows 2003 R2 or the Service for Unix (SFU) schema.
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+	<para>
+	The following example shows how to retrieve idmappings from our principal and
+	and trusted AD domains. All is needed is to set default to yes. If trusted
+	domains are present id conflicts must be resolved beforehand, there is no
+	guarantee on the order conflicting mappings would be resolved at this point.
+
+	This example also shows how to leave a small non conflicting range for local
+	id allocation that may be used in internal backends like BUILTIN.
+	</para>
+
+	<programlisting>
+	[global]
+	idmap domains = ALLDOMAINS
+	idmap config ALLDOMAINS:backend      = ad
+	idmap config ALLDOMAINS:default      = yes
+	idmap config ALLDOMAINS:range        = 10000 - 300000000
+
+	idmap alloc backend = tdb
+	idmap alloc config:range        = 5000 - 9999
+	</programlisting>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>
+	The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.
+	</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/idmap_ldap.8.xml b/docs-xml/manpages-3/idmap_ldap.8.xml
new file mode 100644
index 00000000000..ea7def3a0c1
--- /dev/null
+++ b/docs-xml/manpages-3/idmap_ldap.8.xml
@@ -0,0 +1,165 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="idmap_ldap.8">
+
+<refmeta>
+	<refentrytitle>idmap_ldap</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>idmap_ldap</refname>
+	<refpurpose>Samba's idmap_ldap Backend for Winbind</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<title>DESCRIPTION</title>
+
+	<para>The idmap_ldap plugin provides a means for Winbind to
+	store and retrieve SID/uid/gid mapping tables in an LDAP directory
+	service.  The module implements both the &quot;idmap&quot; and
+	&quot;idmap alloc&quot; APIs.
+	</para>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>IDMAP OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>ldap_base_dn = DN</term>
+		<listitem><para>
+			Defines the directory base suffix to use when searching for
+			SID/uid/gid mapping entries.  If not defined, idmap_ldap will default
+			to using the &quot;ldap idmap suffix&quot; option from smb.conf.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>ldap_user_dn = DN</term>
+		<listitem><para>
+			Defines the user DN to be used for authentication. If absent an
+			anonymous bind will be performed.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>ldap_url = ldap://server/</term>
+		<listitem><para>
+			Specifies the LDAP server to use when searching for existing
+			SID/uid/gid map entries. If not defined, idmap_ldap will
+			assume that ldap://localhost/ should be used.
+		</para></listitem>
+		</varlistentry>
+
+                <varlistentry>
+		<term>range = low - high</term>
+                <listitem><para>
+			Defines the available matching uid and gid range for which the
+			backend is authoritative.  Note that the range commonly matches
+			the allocation range due to the fact that the same backend will
+			store and retrieve SID/uid/gid mapping entries.  If the parameter
+			is absent, Winbind fail over to use the &quot;idmap uid&quot; and
+			&quot;idmap gid&quot; options from smb.conf.
+                </para></listitem>
+                </varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>IDMAP ALLOC OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>ldap_base_dn = DN</term>
+		<listitem><para>
+			Defines the directory base suffix under which new SID/uid/gid mapping
+			entries should be stored.  If not defined, idmap_ldap will default
+			to using the &quot;ldap idmap suffix&quot; option from smb.conf.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>ldap_user_dn = DN</term>
+		<listitem><para>
+			Defines the user DN to be used for authentication. If absent an
+			anonymous bind will be performed.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>ldap_url = ldap://server/</term>
+		<listitem><para>
+			Specifies the LDAP server to which modify/add/delete requests should
+			be sent.  If not defined, idmap_ldap will assume that ldap://localhost/
+			should be used.
+		</para></listitem>
+		</varlistentry>
+
+                <varlistentry>
+		<term>range = low - high</term>
+                <listitem><para>
+			Defines the available matching uid and gid range from which
+			winbindd can allocate for users and groups.  If the parameter
+			is absent, Winbind fail over to use the &quot;idmap uid&quot;
+			and &quot;idmap gid&quot; options from smb.conf.
+                </para></listitem>
+                </varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>
+	The follow sets of a LDAP configuration which uses a slave server
+	running on localhost for fast fetching SID/gid/uid mappings, it
+	implies correct configuration of referrals.
+	The idmap alloc backend is pointed directly to the master to skip
+	the referral (and consequent reconnection to the master) that the
+	slave would return as allocation requires writing on the master.
+	</para>
+
+	<programlisting>
+	[global]
+	    idmap domains = ALLDOMAINS
+	    idmap config ALLDOMAINS:default      = yes
+	    idmap config ALLDOMAINS:backend      = ldap
+	    idmap config ALLDOMAINS:ldap_base_dn = ou=idmap,dc=example,dc=com
+	    idmap config ALLDOMAINS:ldap_url     = ldap://localhost/
+	    idmap config ALLDOMAINS:range        = 10000 - 50000
+
+	    idmap alloc backend = ldap
+	    idmap alloc config:ldap_base_dn = ou=idmap,dc=example,dc=com
+	    idmap alloc config:ldap_url     = ldap://master.example.com/
+	    idmap alloc config:range        = 10000 - 50000
+	</programlisting>
+</refsect1>
+
+<refsynopsisdiv>
+	<title>NOTE</title>
+
+	<para>In order to use authentication against ldap servers you may
+	need to provide a DN and a password. To avoid exposing the password
+	in plain text in the configuration file we store it into a security
+	store. The &quot;net idmap &quot; command is used to store a secret
+	for the DN specified in a specific idmap domain.
+	</para>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>
+	The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.
+	</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/idmap_nss.8.xml b/docs-xml/manpages-3/idmap_nss.8.xml
new file mode 100644
index 00000000000..063ce73748e
--- /dev/null
+++ b/docs-xml/manpages-3/idmap_nss.8.xml
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="idmap_nss.8">
+
+<refmeta>
+	<refentrytitle>idmap_nss</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>idmap_nss</refname>
+	<refpurpose>Samba's idmap_nss Backend for Winbind</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<title>DESCRIPTION</title>
+
+	<para>The idmap_nss plugin provides a means to map Unix users and groups
+	to Windows accounts and obseletes the &quot;winbind trusted domains only&quot;
+	smb.conf option.  This provides a simple means of ensuring that the SID
+	for a Unix user named jsmith is reported as the one assigned to
+	DOMAIN\jsmith which is necessary for reporting ACLs on files and printers
+	stored on a Samba member server.
+	</para>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>
+	This example shows how to use idmap_nss to check the local accounts for its
+	own domain while using allocation to create new mappings for trusted domains
+	</para>
+
+	<programlisting>
+	[global]
+	    idmap domains = SAMBA TRUSTEDDOMAINS
+
+	    idmap config SAMBA:backend  = nss
+	    idmap config SAMBA:readonly = yes
+
+	    idmap config TRUSTEDDOMAINS:default = yes
+	    idmap config TRUSTEDDOMAINS:backend = tdb
+	    idmap config TRUSTEDDOMAINS:range   = 10000 - 50000
+
+	    idmap alloc backend      = tdb
+	    idmap alloc config:range = 10000 - 50000
+	</programlisting>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>
+	The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.
+	</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/idmap_rid.8.xml b/docs-xml/manpages-3/idmap_rid.8.xml
new file mode 100644
index 00000000000..1d80bf3a0eb
--- /dev/null
+++ b/docs-xml/manpages-3/idmap_rid.8.xml
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="idmap_rid.8">
+
+<refmeta>
+	<refentrytitle>idmap_rid</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>idmap_rid</refname>
+	<refpurpose>Samba's idmap_rid Backend for Winbind</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<title>DESCRIPTION</title>
+	<para>The idmap_rid backend provides a way to use an algorithmic
+	mapping scheme to map UIDs/GIDs and SIDs. No database is required
+	in this case as the mapping is deterministic.</para>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>IDMAP OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>range = low - high</term>
+		<listitem><para>
+			Defines the available matching uid and gid range for which the
+			backend is authoritative. Note that the range acts as a filter.
+			If algorithmically determined UID or GID fall outside the
+			range, they are ignored and the corresponding map is discarded.
+			It is intended as a way to avoid accidental UID/GID overlaps
+			between local and remotely defined IDs.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>base_rid = INTEGER</term>
+		<listitem><para>
+			Defines the base integer used to build SIDs out of an UID or a GID,
+			and to rebase the UID or GID to be obtained from a SID. User RIDs
+			by default start at 1000 (512 hexadecimal), this means a good value
+			for base_rid can be 1000 as the resulting ID is calculated this way:
+			ID = RID - BASE_RID + LOW RANGE ID.
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+	<para>This example shows how to configure 2 domains with idmap_rid</para>
+
+	<programlisting>
+	[global]
+	    idmap domains = MAIN TRUSTED1
+
+	    idmap config MAIN:backend      = rid
+	    idmap config MAIN:base_rid     = 0
+	    idmap config MAIN:range        = 10000 - 49999
+
+	    idmap config TRUSTED1:backend  = rid
+	    idmap config TRUSTED1:base_rid = 1000
+	    idmap config TRUSTED1:range    = 50000 - 99999
+	</programlisting>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>
+	The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.
+	</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/idmap_tdb.8.xml b/docs-xml/manpages-3/idmap_tdb.8.xml
new file mode 100644
index 00000000000..2caba1e6cb3
--- /dev/null
+++ b/docs-xml/manpages-3/idmap_tdb.8.xml
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="idmap_tdb.8">
+
+<refmeta>
+	<refentrytitle>idmap_tdb</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>idmap_tdb</refname>
+	<refpurpose>Samba's idmap_tdb Backend for Winbind</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<title>DESCRIPTION</title>
+
+	<para>The idmap_tdb plugin is the default backend used by winbindd
+	for storing SID/uid/gid mapping tables and implements
+	both the &quot;idmap&quot; and &quot;idmap alloc&quot; APIs.
+	</para>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>IDMAP OPTIONS</title>
+
+	<variablelist>
+                <varlistentry>
+		<term>range = low - high</term>
+                <listitem><para>
+			Defines the available matching uid and gid range for which the
+			backend is authoritative.  Note that the range commonly matches
+			the allocation range due to the fact that the same backend will
+			store and retrieve SID/uid/gid mapping entries.  If the parameter
+			is absent, Winbind fail over to use the &quot;idmap uid&quot; and
+			&quot;idmap gid&quot; options from smb.conf.
+                </para></listitem>
+                </varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>IDMAP ALLOC OPTIONS</title>
+
+	<variablelist>
+                <varlistentry>
+		<term>range = low - high</term>
+                <listitem><para>
+			Defines the available matching uid and gid range from which
+			winbindd can allocate for users and groups.  If the parameter
+			is absent, Winbind fail over to use the &quot;idmap uid&quot;
+			and &quot;idmap gid&quot; options from smb.conf.
+                </para></listitem>
+                </varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>
+	The following example is equivalent to the pre-3.0.25 default idmap
+	configuration using the &quot;idmap backend = tdb&quot; setting.
+	</para>
+
+	<programlisting>
+	[global]
+	    idmap domains = ALLDOMAINS
+	    idmap config ALLDOMAINS:default = yes
+	    idmap config ALLDOMAINS:backend = tdb
+	    idmap config ALLDOMAINS:range   = 10000 - 50000
+
+	    idmap alloc backend = tdb
+	    idmap alloc config:range = 10000 - 50000
+	</programlisting>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>
+	The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.
+	</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/ldb.3.xml b/docs-xml/manpages-3/ldb.3.xml
new file mode 100644
index 00000000000..a19422a438d
--- /dev/null
+++ b/docs-xml/manpages-3/ldb.3.xml
@@ -0,0 +1,265 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<refentry id="ldb.3">
+
+<refmeta>
+	<refentrytitle>ldb</refentrytitle>
+	<manvolnum>3</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">C Library Functions</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+<refnamediv>
+	<refname>ldb</refname>
+	<refclass>The Samba Project</refclass>
+	<refpurpose>A light-weight database library</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<synopsis>#include &lt;ldb.h&gt;</synopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>description</title>
+
+	<para>
+ldb is a light weight embedded database library and API. With a
+programming interface that is very similar to LDAP, ldb can store its
+data either in a tdb(3) database or in a real LDAP database.
+	</para>
+
+	<para>
+When used with the tdb backend ldb does not require any database
+daemon. Instead, ldb function calls are processed immediately by the
+ldb library, which does IO directly on the database, while allowing
+multiple readers/writers using operating system byte range locks. This
+leads to an API with very low overheads, often resulting in speeds of
+more than 10x what can be achieved with a more traditional LDAP
+architecture.
+	</para>
+
+	<para>
+In a taxonomy of databases ldb would sit half way between key/value
+pair databases (such as berkley db or tdb) and a full LDAP
+database. With a structured attribute oriented API like LDAP and good
+indexing capabilities, ldb can be used for quite sophisticated
+applications that need a light weight database, without the
+administrative overhead of a full LDAP installation.
+	</para>
+
+	<para>
+Included with ldb are a number of useful command line tools for
+manipulating a ldb database. These tools are similar in style to the
+equivalent ldap command line tools.
+	</para>
+
+	<para>
+In its default mode of operation with a tdb backend, ldb can also be
+seen as a "schema-less LDAP". By default ldb does not require a
+schema, which greatly reduces the complexity of getting started with
+ldb databases. As the complexity of you application grows you can take
+advantage of some of the optional schema-like attributes that ldb
+offers, or you can migrate to using the full LDAP api while keeping
+your exiting ldb code.
+	</para>
+
+	<para>
+If you are new to ldb, then I suggest starting with the manual pages
+for ldbsearch(1) and ldbedit(1), and experimenting with a local
+database. Then I suggest you look at the ldb_connect(3) and
+ldb_search(3) manual pages.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>TOOLS</title>
+
+	<itemizedlist>
+		<listitem><para>
+			<application>ldbsearch(1)</application>
+			  - command line ldb search utility
+		</para></listitem>
+
+		<listitem><para>
+			<application>ldbedit(1)</application>
+			 - edit all or part of a ldb database using your favourite editor
+		</para></listitem>
+
+		<listitem><para>
+			<application>ldbadd(1)</application>
+			 - add records to a ldb database using LDIF formatted input
+		</para></listitem>
+
+		<listitem><para>
+			<application>ldbdel(1)</application>
+			 - delete records from a ldb database
+		</para></listitem>
+
+		<listitem><para>
+			<application>ldbmodify(1)</application>
+			 - modify records in a ldb database using LDIF formatted input
+		</para></listitem>
+	</itemizedlist>
+</refsect1>
+
+<refsect1>
+	<title>FUNCTIONS</title>
+
+	<itemizedlist>
+		<listitem><para>
+			<function>ldb_connect(3)</function>
+			 - connect to a ldb backend
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_search(3)</function>
+			 - perform a database search
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_add(3)</function>
+			 - add a record to the database
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_delete(3)</function>
+			 - delete a record from the database
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_modify(3)</function>
+			 - modify a record in the database
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_errstring(3)</function>
+			 - retrieve extended error information from the last operation
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_ldif_write(3)</function>
+			 - write a LDIF formatted message
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_ldif_write_file(3)</function>
+			 - write a LDIF formatted message to a file
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_ldif_read(3)</function>
+			 - read a LDIF formatted message
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_ldif_read_free(3)</function>
+			 - free the result of a ldb_ldif_read()
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_ldif_read_file(3)</function>
+			 - read a LDIF message from a file
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_ldif_read_string(3)</function>
+			 - read a LDIF message from a string
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_msg_find_element(3)</function>
+			 - find an element in a ldb_message
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_val_equal_exact(3)</function>
+			 - compare two ldb_val structures
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_msg_find_val(3)</function>
+			 - find an element by value
+		</para></listitem>
+
+		<listitem><para>
+			<function>ldb_msg_add_empty(3)</function>
+			 - add an empty message element to a ldb_message
+		</para></listitem>
+
+
+		<listitem><para>
+			<function>ldb_msg_add(3)</function>
+			 - add a non-empty message element to a ldb_message
+		</para></listitem>
+
+
+		<listitem><para>
+			<function>ldb_msg_element_compare(3)</function>
+			 - compare two ldb_message_element structures
+		</para></listitem>
+
+
+		<listitem><para>
+			<function>ldb_msg_find_int(3)</function>
+			 - return an integer value from a ldb_message
+		</para></listitem>
+
+
+		<listitem><para>
+			<function>ldb_msg_find_uint(3)</function>
+			 - return an unsigned integer value from a ldb_message
+		</para></listitem>
+
+
+		<listitem><para>
+			<function>ldb_msg_find_double(3)</function>
+			 - return a double value from a ldb_message
+		</para></listitem>
+
+
+		<listitem><para>
+			<function>ldb_msg_find_string(3)</function>
+			 - return a string value from a ldb_message
+		</para></listitem>
+
+
+		<listitem><para>
+			<function>ldb_set_alloc(3)</function>
+			 - set the memory allocation function to be used by ldb
+		</para></listitem>
+
+
+		<listitem><para>
+			<function>ldb_set_debug(3)</function>
+			 - set a debug handler to be used by ldb
+		</para></listitem>
+
+
+		<listitem><para>
+			<function>ldb_set_debug_stderr(3)</function>
+			 - set a debug handler for stderr output
+		</para></listitem>
+	</itemizedlist>
+</refsect1>
+
+<refsect1>
+	<title>Author</title>
+
+	<para>
+		ldb was written by 
+		 <ulink url="http://samba.org/~tridge/">Andrew Tridgell</ulink>.
+	</para>
+
+	<para>
+If you wish to report a problem or make a suggestion then please see
+the <ulink url="http://ldb.samba.org/"/> web site for
+current contact and maintainer information.
+	</para>
+
+	<para>
+ldb is released under the GNU Lesser General Public License version 2
+or later. Please see the file COPYING for license details.
+	</para>
+</refsect1>
+</refentry>
diff --git a/docs-xml/manpages-3/ldbadd.1.xml b/docs-xml/manpages-3/ldbadd.1.xml
new file mode 100644
index 00000000000..fb57be29c60
--- /dev/null
+++ b/docs-xml/manpages-3/ldbadd.1.xml
@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<refentry id="ldbadd.1">
+
+<refmeta>
+	<refentrytitle>ldbadd</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>ldbadd</refname>
+	<refpurpose>Command-line utility for adding records to an LDB</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>ldbadd</command>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-H LDB-URL</arg>
+		<arg choice="opt">ldif-file1</arg>
+		<arg choice="opt">ldif-file2</arg>
+		<arg choice="opt">...</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>ldbadd adds records to an ldb(7) database. It reads 
+		the ldif(5) files specified on the command line and adds 
+		the records from these files to the LDB database, which is specified 
+		by the -H option or the LDB_URL environment variable.
+	</para>
+
+	<para>If - is specified as a ldb file, the ldif input is read from 
+		standard input.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-h</term>
+		<listitem><para>
+		Show list of available options.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>-H &lt;ldb-url&gt;</term>
+			<listitem><para>
+				LDB URL to connect to. See ldb(7) for details.
+			</para></listitem>
+		</varlistentry>
+		
+	</variablelist>
+	
+</refsect1>
+
+<refsect1>
+	<title>ENVIRONMENT</title>
+
+	<variablelist>
+		<varlistentry><term>LDB_URL</term>
+			<listitem><para>LDB URL to connect to (can be overrided by using the 
+					-H command-line option.)</para></listitem>
+		</varlistentry>
+	</variablelist>
+	
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 4.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+
+	<para>ldb(7), ldbmodify, ldbdel, ldif(5)</para>
+
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para> ldb was written by 
+		 <ulink url="http://samba.org/~tridge/">Andrew Tridgell</ulink>.
+	</para>
+
+	<para>
+If you wish to report a problem or make a suggestion then please see
+the <ulink url="http://ldb.samba.org/"/> web site for
+current contact and maintainer information.
+	</para>
+
+	<para>This manpage was written by Jelmer Vernooij.</para>
+	
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/ldbdel.1.xml b/docs-xml/manpages-3/ldbdel.1.xml
new file mode 100644
index 00000000000..158c5f1a764
--- /dev/null
+++ b/docs-xml/manpages-3/ldbdel.1.xml
@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<refentry id="ldbdel.1">
+
+<refmeta>
+	<refentrytitle>ldbdel</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>ldbdel</refname>
+	<refpurpose>Command-line program for deleting LDB records</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>ldbdel</command>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-H LDB-URL</arg>
+		<arg choice="opt">dn</arg>
+		<arg choice="opt">...</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>ldbdel deletes records from an ldb(7) database. 
+		It deletes the records identified by the dn's specified 
+		on the command-line. </para>
+
+	<para>ldbdel uses either the database that is specified with 
+		the -H option or the database specified by the LDB_URL environment
+		variable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-h</term>
+		<listitem><para>
+		Show list of available options.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>-H &lt;ldb-url&gt;</term>
+			<listitem><para>
+				LDB URL to connect to. See ldb(7) for details.
+			</para></listitem>
+		</varlistentry>
+		
+	</variablelist>
+	
+</refsect1>
+
+<refsect1>
+	<title>ENVIRONMENT</title>
+
+	<variablelist>
+		<varlistentry><term>LDB_URL</term>
+			<listitem><para>LDB URL to connect to (can be overrided by using the 
+					-H command-line option.)</para></listitem>
+		</varlistentry>
+	</variablelist>
+	
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 4.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+
+	<para>ldb(7), ldbmodify, ldbadd, ldif(5)</para>
+
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+		<para> ldb was written by 
+		 <ulink url="http://samba.org/~tridge/">Andrew Tridgell</ulink>.
+	</para>
+
+	<para>
+If you wish to report a problem or make a suggestion then please see
+the <ulink url="http://ldb.samba.org/"/> web site for
+current contact and maintainer information.
+	</para>
+
+	<para>ldbdel was written by Andrew Tridgell.</para>
+
+	<para>This manpage was written by Jelmer Vernooij.</para>
+	
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/ldbedit.1.xml b/docs-xml/manpages-3/ldbedit.1.xml
new file mode 100644
index 00000000000..2d11ca94f73
--- /dev/null
+++ b/docs-xml/manpages-3/ldbedit.1.xml
@@ -0,0 +1,203 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<refentry id="ldbedit.1">
+
+    <refmeta>
+	<refentrytitle>ldbedit</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+    </refmeta>
+
+
+    <refnamediv>
+	<refname>ldbedit</refname>
+	<refpurpose>Edit LDB databases using your preferred editor</refpurpose>
+    </refnamediv>
+
+    <refsynopsisdiv>
+	<cmdsynopsis>
+	    <command>ldbedit</command>
+	    <arg choice="opt">-?</arg>
+	    <arg choice="opt">--usage</arg>
+	    <arg choice="opt">-s base|one|sub</arg>
+	    <arg choice="opt">-b basedn</arg>
+	    <arg choice="opt">-a</arg>
+	    <arg choice="opt">-e editor</arg>
+	    <arg choice="opt">-H LDB-URL</arg>
+	    <arg choice="opt">expression</arg>
+	    <arg rep="repeat" choice="opt">attributes</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>ldbedit is a utility that allows you to edit LDB entries (in 
+	    tdb files, sqlite files or LDAP servers) using your preferred editor.
+	    ldbedit generates an LDIF file based on your query, allows you to edit
+	    the LDIF, and then merges that LDIF back into the LDB backend.
+	</para>
+
+</refsect1>
+
+
+    <refsect1>
+	<title>OPTIONS</title>
+	
+	<variablelist>
+	    <varlistentry>
+		<term>-?</term>
+		<term>--help</term>
+		<listitem>
+		    <para>
+			Show list of available options, and a phrase describing what that option
+			does.
+		    </para>
+		</listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+		<term>--usage</term>
+		<listitem>
+		    <para>
+			Show list of available options. This is similar to the help option, 
+			however it does not provide any description, and is hence shorter.
+		    </para>
+		</listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+		<term>-H &lt;ldb-url&gt;</term>
+		<listitem>
+		    <para>
+			LDB URL to connect to. For a tdb database,
+			this will be of the form
+			tdb://<replaceable>filename</replaceable>.
+			For a LDAP connection over unix domain
+			sockets, this will be of the form
+			ldapi://<replaceable>socket</replaceable>. For
+			a (potentially remote) LDAP connection over
+			TCP, this will be of the form
+			ldap://<replaceable>hostname</replaceable>. For
+			an SQLite database, this will be of the form
+			sqlite://<replaceable>filename</replaceable>.
+		    </para>
+		</listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+		<term>-s one|sub|base</term>
+		<listitem><para>Search scope to use. One-level, subtree or base.</para></listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+		<term>-a</term>
+		<term>-all</term>
+		<listitem>
+		    <para>Edit all records. This allows you to
+			apply the same change to a number of records
+			at once. You probably want to combine this
+			with an expression of the form
+			"objectclass=*".
+		    </para>
+		</listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+		<term>-e editor</term>
+		<term>--editor editor</term>
+		<listitem>
+		    <para>Specify the editor that should be used (overrides 
+			the VISUAL and EDITOR environment
+			variables). If this option is not used, and
+			neither VISUAL nor EDITOR environment variables
+			are set, then the vi editor will be used.
+		    </para>
+		</listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+		<term>-b basedn</term>
+		<listitem><para>Specify Base Distinguished Name to use.</para></listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+		<term>-v</term>
+		<term>--verbose</term>
+		<listitem>
+		    <para>Make ldbedit more verbose about the
+			operations that are being performed. Without
+			this option, ldbedit will only provide a
+			summary change line.
+		    </para>
+		</listitem>
+	    </varlistentry>
+		
+	</variablelist>
+	
+    </refsect1>
+
+    <refsect1>
+	<title>ENVIRONMENT</title>
+
+	<variablelist>
+	    <varlistentry>
+		<term>LDB_URL</term>
+		<listitem>
+		    <para>LDB URL to connect to. This can be
+		    overridden by using the -H command-line option.)
+		    </para>
+		</listitem>
+	    </varlistentry>
+	    <varlistentry>
+		<term>VISUAL and EDITOR</term>
+		<listitem>
+		    <para>
+			Environment variables used to determine what 
+			editor to use. VISUAL takes precedence over
+			EDITOR, and both are overridden by the
+			-e command-line option.
+		    </para>
+		</listitem>
+	    </varlistentry>
+	</variablelist>
+	
+    </refsect1>
+
+    <refsect1>
+	<title>VERSION</title>
+	
+	<para>This man page is correct for version 4.0 of the Samba suite.</para>
+    </refsect1>
+
+    <refsect1>
+	<title>SEE ALSO</title>
+	
+	<para>ldb(7), ldbmodify(1), ldbdel(1), ldif(5), vi(1)</para>
+
+    </refsect1>
+
+    <refsect1>
+	<title>AUTHOR</title>
+
+	<para>
+	    ldb was written by 
+	    <ulink url="http://samba.org/~tridge/">Andrew Tridgell</ulink>.
+	</para>
+
+	<para>
+	    If you wish to report a problem or make a suggestion then please see
+	    the <ulink url="http://ldb.samba.org/"/> web site for
+	    current contact and maintainer information.
+	</para>
+
+	<para>
+	    This manpage was written by Jelmer Vernooij and updated
+	    by Brad Hards.
+	</para>
+	
+    </refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/ldbmodify.1.xml b/docs-xml/manpages-3/ldbmodify.1.xml
new file mode 100644
index 00000000000..a46ae5047b5
--- /dev/null
+++ b/docs-xml/manpages-3/ldbmodify.1.xml
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<refentry id="ldbmodify.1">
+
+<refmeta>
+	<refentrytitle>ldbmodify</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>ldbmodify</refname>
+	<refpurpose>Modify records in a LDB database</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>ldbmodify</command>
+		<arg choice="opt">-H LDB-URL</arg>
+		<arg choice="opt">ldif-file</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>
+		ldbmodify changes, adds and deletes records in a LDB database. 
+		The changes that should be made to the LDB database are read from 
+		the specified LDIF-file. If - is specified as the filename, input is read from stdin.
+	</para>
+
+	<para>For now, see ldapmodify(1) for details on the LDIF file format.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+			<term>-H &lt;ldb-url&gt;</term>
+			<listitem><para>
+				LDB URL to connect to. See ldb(7) for details.
+			</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>ENVIRONMENT</title>
+
+	<variablelist>
+		<varlistentry><term>LDB_URL</term>
+			<listitem><para>LDB URL to connect to (can be overrided by using the 
+					-H command-line option.)</para></listitem>
+		</varlistentry>
+	</variablelist>
+	
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 4.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+
+	<para>ldb(7), ldbedit</para>
+
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para> ldb was written by 
+		 <ulink url="http://samba.org/~tridge/">Andrew Tridgell</ulink>.
+	</para>
+
+	<para>
+If you wish to report a problem or make a suggestion then please see
+the <ulink url="http://ldb.samba.org/"/> web site for
+current contact and maintainer information.
+	</para>
+
+	<para>This manpage was written by Jelmer Vernooij.</para>
+	
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/ldbsearch.1.xml b/docs-xml/manpages-3/ldbsearch.1.xml
new file mode 100644
index 00000000000..398860bca02
--- /dev/null
+++ b/docs-xml/manpages-3/ldbsearch.1.xml
@@ -0,0 +1,122 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<refentry id="ldbsearch.1">
+
+<refmeta>
+	<refentrytitle>ldbsearch</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>ldbsearch</refname>
+	<refpurpose>Search for records in a LDB database</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>ldbsearch</command>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-s base|one|sub</arg>
+		<arg choice="opt">-b basedn</arg>
+		<arg chioce="opt">-i</arg>
+		<arg choice="opt">-H LDB-URL</arg>
+		<arg choice="opt">expression</arg>
+		<arg choice="opt">attributes</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>ldbsearch searches a LDB database for records matching the 
+		specified expression (see the ldapsearch(1) manpage for 
+		a description of the expression format). For each 
+		record, the specified attributes are printed.
+	</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-h</term>
+		<listitem><para>
+		Show list of available options.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>-H &lt;ldb-url&gt;</term>
+			<listitem><para>
+				LDB URL to connect to. See ldb(7) for details.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>-s one|sub|base</term>
+			<listitem><para>Search scope to use. One-level, subtree or base.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>-i</term>
+			<listitem><para>Read search expressions from stdin. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>-b basedn</term>
+			<listitem><para>Specify Base DN to use.</para></listitem>
+		</varlistentry>
+		
+	</variablelist>
+	
+</refsect1>
+
+<refsect1>
+	<title>ENVIRONMENT</title>
+
+	<variablelist>
+		<varlistentry><term>LDB_URL</term>
+			<listitem><para>LDB URL to connect to (can be overrided by using the 
+					-H command-line option.)</para></listitem>
+		</varlistentry>
+	</variablelist>
+	
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 4.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+
+	<para>ldb(7), ldbedit(1)</para>
+
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para> ldb was written by 
+		 <ulink url="http://samba.org/~tridge/">Andrew Tridgell</ulink>.
+	</para>
+
+	<para>
+If you wish to report a problem or make a suggestion then please see
+the <ulink url="http://ldb.samba.org/"/> web site for
+current contact and maintainer information.
+	</para>
+
+	<para>This manpage was written by Jelmer Vernooij.</para>
+	
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/libsmbclient.7.xml b/docs-xml/manpages-3/libsmbclient.7.xml
new file mode 100644
index 00000000000..61016c55cec
--- /dev/null
+++ b/docs-xml/manpages-3/libsmbclient.7.xml
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="libsmbclient.7">
+
+<refmeta>
+	<refentrytitle>libsmbclient</refentrytitle>
+	<manvolnum>7</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">7</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>libsmbclient</refname>
+	<refpurpose>An extension library for browsers and that can be used as a generic browsing API.</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>Browser URL:</command>
+	<para>
+        smb://[[[domain:]user[:password@]]server[/share[/path[/file]]]] [?options]
+    </para>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>
+	This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.
+	</para>
+
+	<para>
+	<command>libsmbclient</command> is a library toolset that permits applications to manipulate CIFS/SMB network
+	resources using many of the standards POSIX functions available for manipulating local UNIX/Linux files. It
+	permits much more than just browsing, files can be opened and read or written, permissions changed, file times
+	modified, attributes and ACL's can be manipulated, and so on. Of course, its functionality includes all the
+	capabilities commonly called browsing.
+	</para>
+
+	<para>
+	<command>libsmbclient</command> can not be used directly from the command line, instead it provides an
+	extension of the capabilities of tools such as file managers and browsers.  This man page describes the
+	configuration options for this tool so that the user may obtain greatest utility of use.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<para>
+	What the URLs mean:
+	</para>
+
+	<variablelist>
+		<varlistentry>
+			<term>smb://</term>
+			<listitem><para>
+			Shows all workgroups or domains that are visible in the network. The behavior matches
+			that of the Microsoft Windows Explorer.
+			</para>
+
+			<para>
+			The method of locating the list of workgroups (domains also) varies depending on the setting of
+			the context variable <literal>(context-&gt;options.browse_max_lmb_count)</literal>. It is the
+			responsibility of the application that calls this library to set this to a sensible value.  This
+			is a compile-time option. This value determines the maximum number of local master browsers to
+			query for the list of workgroups.  In order to ensure that the list is complete for those present
+			on the network, all master browsers must be querried. If there are a large number of workgroups
+			on the network, the time spent querying will be significant. For small networks (just a few
+			workgroups), it is suggested to set this value to 0, instructing libsmbclient to query all local
+			master browsers. In an environment that has many workgroups a more reasonable setting may be around 3.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>smb://name/</term>
+			<listitem><para>
+			This command causes libsmbclient to perform a name look-up. If the NAME&lt;1D&gt; or
+			NAME&lt;1B&gt; exists (workgroup name), libsmbclient will list all servers in the
+			workgroup (or domain). Otherwise, a name look-up for the NAME&lt;20&gt; (machine name)
+			will be performed, and the list of shared resources on the server will be displayed.
+			</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>
+	When libsmbclient is invoked by an application it searches for a directory called
+	<filename>.smb</filename> in the $HOME directory that is specified in the users shell
+	environment. It then searches for a file called <filename>smb.conf</filename> which,
+	if present, will fully over-ride the system <filename>/etc/samba/smb.conf</filename> file. If
+	instead libsmbclient finds a file called <filename>~/.smb/smb.conf.append</filename>,
+	it will read the system <filename>/etc/samba/smb.conf</filename> and then append the
+	contents of the <filename>~/.smb/smb.conf.append</filename> to it.
+	</para>
+
+	<para>
+	<command>libsmbclient</command> will check the users shell environment for the <literal>USER</literal>
+	parameter and will use its value when if the <literal>user</literal> parameter was not included
+	in the URL.
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>PROGRAMMERS GUIDE</title>
+
+	<para>
+	Watch this space for future updates.
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>
+	This man page is correct for version 3.0 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>
+	The original Samba software and related utilities were created by Andrew Tridgell.
+	Samba is now developed by the Samba Team as an Open Source project similar to the way
+	the Linux kernel is developed.
+	</para> 
+
+	<para>
+	The libsmbclient manpage page was written by John H Terpstra.
+	</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/lmhosts.5.xml b/docs-xml/manpages-3/lmhosts.5.xml
new file mode 100644
index 00000000000..ec271770c4f
--- /dev/null
+++ b/docs-xml/manpages-3/lmhosts.5.xml
@@ -0,0 +1,127 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="lmhosts.5">
+
+<refmeta>
+	<refentrytitle>lmhosts</refentrytitle>
+	<manvolnum>5</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">File Formats and Conventions</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>lmhosts</refname>
+	<refpurpose>The Samba NetBIOS hosts file</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<para><filename>lmhosts</filename> is the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> NetBIOS name to IP address mapping file.</para> 
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+	
+	<para>This file is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><filename>lmhosts</filename> is the <emphasis>Samba
+	</emphasis> NetBIOS name to IP address mapping file.  It 
+	is very similar to the <filename>/etc/hosts</filename> file 
+	format, except that the hostname component must correspond 
+	to the NetBIOS naming format.</para>
+</refsect1>
+
+<refsect1>
+	<title>FILE FORMAT</title>
+	<para>It is an ASCII file containing one line for NetBIOS name. 
+	The two fields on each line are separated from each other by 
+	white space. Any entry beginning with '#' is ignored. Each line 
+	in the lmhosts file contains the following information:</para>
+
+	<itemizedlist>
+		<listitem><para>IP Address - in dotted decimal format.</para>
+		</listitem>
+
+		<listitem><para>NetBIOS Name - This name format is a 
+		maximum fifteen character host name, with an optional 
+		trailing '#' character followed by the NetBIOS name type 
+		as two hexadecimal digits.</para>
+
+		<para>If the trailing '#' is omitted then the given IP 
+		address will be returned for all names that match the given 
+		name, whatever the NetBIOS name type in the lookup.</para>
+		</listitem>
+	</itemizedlist>
+
+	<para>An example follows:
+<programlisting>
+#
+# Sample Samba lmhosts file.
+#
+192.9.200.1	TESTPC
+192.9.200.20	NTSERVER#20
+192.9.200.21	SAMBASERVER
+</programlisting>
+	</para>
+	
+	<para>Contains three IP to NetBIOS name mappings. The first 
+	and third will be returned for any queries for the names "TESTPC" 
+	and "SAMBASERVER" respectively, whatever the type component of 
+	the NetBIOS name requested.</para>
+
+	<para>The second mapping will be returned only when the "0x20" name 
+	type for a name "NTSERVER" is queried. Any other name type will not 
+	be resolved.</para>
+
+	<para>The default location of the <filename>lmhosts</filename> file 
+	is in the same directory as the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> file.</para>
+	
+</refsect1>
+
+<refsect1>
+	<title>FILES</title>
+
+	<para>lmhosts is loaded from the configuration directory. This is 
+		usually <filename>/etc/samba</filename> or <filename>/usr/local/samba/lib</filename>.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry>
+	<refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum>
+	</citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum>
+	</citerefentry>, and <citerefentry><refentrytitle>smbpasswd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at
+	<ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook
+	XML 4.2 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/log2pcap.1.xml b/docs-xml/manpages-3/log2pcap.1.xml
new file mode 100644
index 00000000000..48eb1a1a240
--- /dev/null
+++ b/docs-xml/manpages-3/log2pcap.1.xml
@@ -0,0 +1,138 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="log2pcap.1">
+
+<refmeta>
+	<refentrytitle>log2pcap</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>log2pcap</refname>
+	<refpurpose>Extract network traces from Samba log files</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>log2pcap</command>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-q</arg>
+		<arg choice="opt">logfile</arg>
+		<arg choice="opt">pcap_file</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>log2pcap</command> reads in a 
+	samba log file and generates a pcap file (readable 
+	by most sniffers, such as ethereal or tcpdump) based on the packet 
+	dumps in the log file.</para>
+
+	<para>The log file must have a <parameter>log level</parameter> 
+	of at least <constant>5</constant> to get the SMB header/parameters 
+	right, <constant>10</constant> to get the first 512 data bytes of the 
+	packet and <constant>50</constant> to get the whole packet.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+	    <varlistentry>
+		<term>-h</term>
+		<listitem><para>If this parameter is 
+		specified the output file will be a 
+		hex dump, in a format that is readable 
+		by the <application>text2pcap</application> utility.</para></listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+	    	<term>-q</term>
+		<listitem><para>Be quiet. No warning messages about missing 
+		or incomplete data will be given.</para></listitem>
+	    </varlistentry>
+		
+	    <varlistentry>
+		<term>logfile</term>
+		<listitem><para>
+		Samba log file. log2pcap will try to read the log from stdin 
+		if the log file is not specified.
+		</para></listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+		<term>pcap_file</term>
+		<listitem><para>
+		Name of the output file to write the pcap (or hexdump) data to.
+		If this argument is not specified, output data will be written 
+		to stdout.
+		</para></listitem>
+	    </varlistentry>
+
+	    &stdarg.help;
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Extract all network traffic from all samba log files:</para>
+
+	<para><programlisting>
+			<prompt>$</prompt> log2pcap &lt; /var/log/* &gt; trace.pcap
+	</programlisting></para>
+
+	<para>Convert to pcap using text2pcap:</para>
+
+	<para><programlisting>
+	<prompt>$</prompt> log2pcap -h samba.log | text2pcap -T 139,139 - trace.pcap
+	</programlisting></para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>BUGS</title>
+
+	<para>Only SMB data is extracted from the samba logs, no LDAP, 
+	NetBIOS lookup or other data.</para>
+
+	<para>The generated TCP and IP headers don't contain a valid 
+	checksum.</para>
+	
+</refsect1>
+
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>text2pcap</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>ethereal</refentrytitle><manvolnum>1</manvolnum></citerefentry></para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>This manpage was written by Jelmer Vernooij.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/mount.cifs.8.xml b/docs-xml/manpages-3/mount.cifs.8.xml
new file mode 100644
index 00000000000..51a22b38794
--- /dev/null
+++ b/docs-xml/manpages-3/mount.cifs.8.xml
@@ -0,0 +1,614 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="mount.cifs.8">
+
+<refmeta>
+	<refentrytitle>mount.cifs</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>mount.cifs</refname>
+	<refpurpose>mount using the Common Internet File System (CIFS)</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+
+		<command>mount.cifs</command>
+		<arg choice="req">service</arg>	
+		<arg choice="req">mount-point</arg>	
+		<arg choice="opt">-o options</arg>	
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>mount.cifs mounts a Linux CIFS filesystem. It
+is usually invoked indirectly by
+the <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry> command when using the 
+"-t cifs" option. This command only works in Linux, and the kernel must
+support the cifs filesystem. The CIFS protocol is the successor to the 
+SMB protocol and is supported by most Windows servers and many other
+commercial servers and Network Attached Storage appliances as well as 
+by the popular Open Source server Samba.
+	</para>
+
+	<para>
+	The mount.cifs utility attaches the UNC name (exported network resource) to
+	the local directory <emphasis>mount-point</emphasis>. It is possible to set the mode for mount.cifs to 
+setuid root to allow non-root users to mount shares to directories for which they
+have write permission.
+	</para>
+
+	<para>
+		Options to <emphasis>mount.cifs</emphasis> are specified as a comma-separated
+list of key=value pairs. It is possible to send options other
+than those listed here, assuming that the cifs filesystem kernel module (cifs.ko) supports them.   
+Unrecognized cifs mount options passed to the cifs vfs kernel code will be logged to the
+kernel log.
+
+	</para>
+
+	<para><emphasis>mount.cifs</emphasis> causes the cifs vfs to launch a thread named cifsd. After mounting it keeps running until
+		the mounted resource is unmounted (usually via the umount utility).
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+	<variablelist>
+		<varlistentry><term>user=<replaceable>arg</replaceable></term>
+
+		<listitem><para>specifies the username to connect as. If
+				this is not given, then the environment variable <emphasis>USER</emphasis> is used. This option can also take the
+form "user%password" or "workgroup/user" or
+"workgroup/user%password" to allow the password and workgroup
+to be specified as part of the username.
+		</para>
+
+<note>
+	<para>
+	The cifs vfs accepts the parameter <parameter>user=</parameter>, or for users familiar with smbfs it accepts the longer form of the parameter <parameter>username=</parameter>.  Similarly the longer smbfs style parameter names may be accepted as synonyms for the shorter cifs parameters <parameter>pass=</parameter>,<parameter>dom=</parameter> and <parameter>cred=</parameter>.
+	</para>
+</note>
+
+		</listitem>
+	</varlistentry>
+
+	<varlistentry><term>password=<replaceable>arg</replaceable></term>
+
+		<listitem><para>specifies the CIFS password. If this
+option is not given then the environment variable
+<emphasis>PASSWD</emphasis> is used. If the password is not specified 
+directly or indirectly via an argument to mount, <emphasis>mount.cifs</emphasis> will prompt
+for a password, unless the guest option is specified.
+</para>
+
+<para>Note that a password which contains the delimiter
+character (i.e. a comma ',') will fail to be parsed correctly
+on the command line.  However, the same password defined
+in the PASSWD environment variable or via a credentials file (see
+below) or entered at the password prompt will be read correctly.
+</para>
+	</listitem></varlistentry>
+
+	<varlistentry><term>credentials=<replaceable>filename</replaceable></term>
+
+		<listitem><para>
+				specifies a file that contains a username
+				and/or password. The format of the file is:
+			</para>
+
+<programlisting>
+		username=<replaceable>value</replaceable>
+		password=<replaceable>value</replaceable>
+</programlisting>
+		
+		<para>
+This is preferred over having passwords in plaintext in a
+shared file, such as <filename>/etc/fstab</filename>. Be sure to protect any
+credentials file properly.
+		</para>
+	</listitem></varlistentry>
+
+	<varlistentry>
+		<term>uid=<replaceable>arg</replaceable></term>
+
+		<listitem><para>sets the uid that will own all files on
+	the mounted filesystem.
+	It may be specified as either a username or a numeric uid.
+	For mounts to servers which do support the CIFS Unix extensions, 
+        such as a properly configured Samba server, the server provides
+                the uid, gid and mode so this parameter should not be
+                specified unless the server and client uid and gid
+                numbering differ.  If the server and client are in the
+                same domain (e.g. running winbind or nss_ldap) and
+                the server supports the Unix Extensions then the uid
+                and gid can be retrieved from the server (and uid
+                and gid would not have to be specifed on the mount. 
+                For servers which do not support the CIFS Unix
+                extensions, the default uid (and gid) returned on lookup 
+                of existing files will be the uid (gid) of the person
+                who executed the mount (root, except when mount.cifs
+                is configured setuid for user mounts) unless the "uid="
+                (gid) mount option is specified.  For the uid (gid) of newly
+                created files and directories, ie files created since
+                the last mount of the server share, the expected uid
+                (gid) is cached as long as the inode remains in
+                memory on the client.   Also note that permission
+                checks (authorization checks) on accesses to a file occur
+                at the server, but there are cases in which an administrator
+                may want to restrict at the client as well.  For those
+                servers which do not report a uid/gid owner
+                (such as Windows), permissions can also be checked at the
+                client, and a crude form of client side permission checking
+                can be enabled by specifying file_mode and dir_mode on
+                the client.  Note that the mount.cifs helper must be
+                at version 1.10 or higher to support specifying the uid
+                (or gid) in non-numeric form.
+	</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>gid=<replaceable>arg</replaceable></term>
+
+		<listitem><para>sets the gid that will own all files on
+the mounted filesystem.  It may be specified as either a groupname or a numeric 
+gid. For other considerations see the description of uid above. 
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>port=<replaceable>arg</replaceable></term>
+
+		<listitem><para>sets the port number on the server to attempt to contact to negotiate
+CIFS support.  If the CIFS server is not listening on this port or
+if it is not specified, the default ports will be tried i.e. 
+port 445 is tried and if no response then port 139 is tried.
+		</para></listitem>
+	</varlistentry>
+
+        <varlistentry>
+                <term>servern=<replaceable>arg</replaceable></term>
+
+                <listitem><para>
+		Specify the server netbios name (RFC1001 name) to use
+                when attempting to setup a session to the server. Although
+		rarely needed for mounting to newer servers, this option
+                is needed for mounting to some older servers (such
+                as OS/2 or Windows 98 and Windows ME) since when connecting
+		over port 139 they, unlike most newer servers, do not
+                support a default server name.  A server name can be up
+                to 15 characters long and is usually uppercased.
+                </para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>netbiosname=<replaceable>arg</replaceable></term>
+
+                <listitem><para>When mounting to servers via port 139, specifies the RFC1001
+                source name to use to represent the client netbios machine
+                name when doing the RFC1001 netbios session initialize.
+		</para></listitem>
+        </varlistentry>
+
+	<varlistentry>
+		<term>file_mode=<replaceable>arg</replaceable></term>
+
+		<listitem><para>If the server does not support the CIFS Unix extensions this
+				overrides the default file mode.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>dir_mode=<replaceable>arg</replaceable></term>
+
+		<listitem><para>If the server does not support the CIFS Unix extensions this
+				overrides the default mode for directories. </para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>ip=<replaceable>arg</replaceable></term>
+
+		<listitem><para>sets the destination IP address.  This option is set automatically if the server name portion of the requested UNC name can be resolved so rarely needs to be specified by the user.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>domain=<replaceable>arg</replaceable></term>
+
+		<listitem><para>sets the domain (workgroup) of the user </para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>guest</term>
+
+		<listitem><para>don't prompt for a password </para></listitem>
+
+	</varlistentry>
+
+	<varlistentry>
+		<term>iocharset</term>
+
+		<listitem><para>Charset used to convert local path names to and from
+		Unicode. Unicode is used by default for network path
+		names if the server supports it. If iocharset is
+		not specified then the nls_default specified
+		during the local client kernel build will be used.
+		If server does not support Unicode, this parameter is
+		unused. </para></listitem>
+
+	</varlistentry>
+
+	<varlistentry>
+		<term>ro</term>
+
+		<listitem><para>mount read-only</para></listitem>
+
+	</varlistentry>
+
+	<varlistentry>
+		<term>rw</term>
+		<listitem><para>mount read-write</para></listitem>
+	</varlistentry>
+
+        <varlistentry>
+                <term>setuids</term>
+                <listitem><para>If the CIFS Unix extensions are negotiated with the server
+                the client will attempt to set the effective uid and gid of
+                the local process on newly created files, directories, and
+                devices (create, mkdir, mknod). If the CIFS Unix Extensions
+                are not negotiated, for newly created files and directories
+                instead of using the default uid and gid specified on the
+                the mount, cache the new file's uid and gid locally which means
+                that the uid for the file can change when the inode is
+                reloaded (or the user remounts the share).</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>nosetuids</term>
+                <listitem><para>The client will not attempt to set the uid and gid on
+                on newly created files, directories, and devices (create,
+                mkdir, mknod) which will result in the server setting the
+                uid and gid to the default (usually the server uid of the
+                user who mounted the share).  Letting the server (rather than
+                the client) set the uid and gid is the default.If the CIFS
+                Unix Extensions are not negotiated then the uid and gid for
+                new files will appear to be the uid (gid) of the mounter or the
+                uid (gid) parameter specified on the mount.</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>perm</term>
+                <listitem><para>Client does permission checks (vfs_permission check of uid
+                and gid of the file against the mode and desired operation),
+                Note that this is in addition to the normal ACL check on the
+                target machine done by the server software.
+                Client permission checking is enabled by default.</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>noperm</term>
+                <listitem><para>Client does not do permission checks.  This can expose
+                files on this mount to access by other users on the local
+                client system. It is typically only needed when the server
+                supports the CIFS Unix Extensions but the UIDs/GIDs on the
+                client and server system do not match closely enough to allow
+                access by the user doing the mount.
+                Note that this does not affect the normal ACL check on the
+                target machine done by the server software (of the server
+                ACL against the user name provided at mount time).</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>directio</term>
+                <listitem><para>Do not do inode data caching on files opened on this mount.
+                This precludes mmaping files on this mount. In some cases
+                with fast networks and little or no caching benefits on the
+                client (e.g. when the application is doing large sequential
+                reads bigger than page size without rereading the same data)
+                this can provide better performance than the default
+                behavior which caches reads (readahead) and writes
+                (writebehind) through the local Linux client pagecache
+                if oplock (caching token) is granted and held. Note that
+                direct allows write operations larger than page size
+                to be sent to the server. On some kernels this requires the cifs.ko module
+		to be built with the CIFS_EXPERIMENTAL configure option.</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>mapchars</term>
+                <listitem><para>Translate six of the seven reserved characters (not backslash, but including the colon, question mark, pipe, asterik, greater than and less than characters)
+                to the remap range (above 0xF000), which also
+                allows the CIFS client to recognize files created with
+                such characters by Windows's POSIX emulation. This can
+                also be useful when mounting to most versions of Samba
+                (which also forbids creating and opening files
+                whose names contain any of these seven characters).
+                This has no effect if the server does not support
+                Unicode on the wire.</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>nomapchars</term>
+                <listitem><para>Do not translate any of these seven characters (default)</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>intr</term>
+                <listitem><para>currently unimplemented</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>nointr</term>
+                <listitem><para>(default) currently unimplemented </para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>hard</term>
+                <listitem><para>The  program  accessing  a file on the cifs mounted file system will hang when the
+              server crashes.</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>soft</term>
+                <listitem><para>(default) The  program  accessing  a file on the cifs mounted file system will not hang when the server crashes and will return errors to the user application.</para></listitem>
+        </varlistentry>
+
+	<varlistentry>
+                <term>noacl</term>
+                <listitem><para>Do not allow POSIX ACL operations even if server would support them.</para><para>
+		The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers
+		version 3.10 and later.  Setting POSIX ACLs requires enabling both XATTR and
+		then POSIX support in the CIFS configuration options when building the cifs
+		module.  POSIX ACL support can be disabled on a per mount basic by specifying
+		"noacl" on mount.</para>
+		</listitem>
+	</varlistentry>
+
+        <varlistentry>
+                <term>nocase</term>
+                <listitem>
+		<para>Request case insensitive path name matching (case
+                sensitive is the default if the server suports it).
+		</para>
+                </listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>sec=</term>
+                <listitem>
+                <para>Security mode.  Allowed values are:</para>
+			<itemizedlist>
+                        <listitem><para>none    attempt to connection as a null user (no name) </para></listitem>
+                        <listitem><para>krb5    Use Kerberos version 5 authentication</para></listitem>
+                        <listitem><para>krb5i   Use Kerberos authentication and packet signing</para></listitem>
+                        <listitem><para>ntlm    Use NTLM password hashing (default)</para></listitem>
+                        <listitem><para>ntlmi   Use NTLM password hashing with signing (if
+                                /proc/fs/cifs/PacketSigningEnabled on or if
+                                server requires signing also can be the default)</para></listitem>
+                        <listitem><para>ntlmv2  Use NTLMv2 password hashing</para></listitem>
+                        <listitem><para>ntlmv2i Use NTLMv2 password hashing with packet signing</para></listitem>
+			</itemizedlist>
+
+			<para>[NB This [sec parameter] is under development and expected to be available in cifs kernel module 1.40 and later]
+                </para>
+                </listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>nobrl</term>
+                <listitem>
+                <para>Do not send byte range lock requests to the server.
+                This is necessary for certain applications that break
+                with cifs style mandatory byte range locks (and most
+                cifs servers do not yet support requesting advisory
+                byte range locks).
+                </para>
+                </listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>sfu</term>
+                <listitem>
+                <para>
+		When the CIFS Unix Extensions are not negotiated, attempt to
+                create device files and fifos in a format compatible with
+                Services for Unix (SFU).  In addition retrieve bits 10-12
+                of the mode via the SETFILEBITS extended attribute (as
+                SFU does).  In the future the bottom 9 bits of the mode
+                mode also will be emulated using queries of the security
+                descriptor (ACL). [NB: requires version 1.39 or later
+		of the CIFS VFS.  To recognize symlinks and be able
+		to create symlinks in an SFU interoperable form
+		requires version 1.40 or later of the CIFS VFS kernel module.
+                </para>
+                </listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>serverino</term>
+                <listitem><para>Use inode numbers (unique persistent file identifiers)
+		returned by the server instead of automatically generating
+                temporary inode numbers on the client.  Although server inode numbers
+                make it easier to spot hardlinked files (as they will have
+                the same inode numbers) and inode numbers may be persistent (which is
+		userful for some sofware),
+                the server does not guarantee that the inode numbers
+                are unique if multiple server side mounts are exported under a
+                single share (since inode numbers on the servers might not
+                be unique if multiple filesystems are mounted under the same
+                shared higher level directory).  Note that not all 
+                servers support returning server inode numbers, although
+		those that support the CIFS Unix Extensions, and Windows 2000 and
+		later servers typically do support this (although not necessarily
+		on every local server filesystem). Parameter has no effect if
+                the server lacks support for returning inode numbers or equivalent.
+		</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>noserverino</term>
+                <listitem><para>client generates inode numbers (rather than using the actual one
+                from the server) by default.
+		</para></listitem>
+        </varlistentry>
+
+        <varlistentry>
+                <term>nouser_xattr</term>
+                <listitem><para>(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise. </para></listitem>
+        </varlistentry>
+
+	<varlistentry>
+		<term>rsize=<replaceable>arg</replaceable></term>
+		<listitem><para>default network read size (usually 16K). The client currently
+                can not use rsize larger than CIFSMaxBufSize. CIFSMaxBufSize
+                defaults to 16K and may be changed (from 8K to the maximum
+                kmalloc size allowed by your kernel) at module install time
+                for cifs.ko. Setting CIFSMaxBufSize to a very large value
+                will cause cifs to use more memory and may reduce performance
+                in some cases.  To use rsize greater than 127K (the original
+                cifs protocol maximum) also requires that the server support
+                a new Unix Capability flag (for very large read) which some
+                newer servers (e.g. Samba 3.0.26 or later) do. rsize can be
+                set from a minimum of 2048 to a maximum of 130048 (127K or
+                CIFSMaxBufSize, whichever is smaller)
+
+		</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>wsize=<replaceable>arg</replaceable></term>
+
+		<listitem><para>default network write size (default 57344)
+                maximum wsize currently allowed by CIFS is 57344 (fourteen
+                4096 byte pages)</para></listitem>
+	</varlistentry>
+	 <varlistentry>
+                <term>--verbose</term>
+                <listitem><para>Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:</para><para>mount -t cifs //server/share /mnt --verbose -o user=username</para></listitem>
+        </varlistentry>
+
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>SERVICE FORMATTING AND DELIMITERS</title>
+
+	<para>
+		It's generally preferred to use forward slashes (/) as a delimiter in service names. They are considered to be the "universal delimiter" since they are generally not allowed to be embedded within path components on Windows machines and the client can convert them to blackslashes (\) unconditionally. Conversely, backslash characters are allowed by POSIX to be part of a path component, and can't be automatically converted in the same way.
+	</para>
+	<para>
+		mount.cifs will attempt to convert backslashes to forward slashes where it's able to do so, but it cannot do so in any path component following the sharename.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>ENVIRONMENT VARIABLES</title>
+
+	<para>
+		The variable <emphasis>USER</emphasis> may contain the username of the
+person to be used to authenticate to the server.
+The variable can be used to set both username and
+password by using the format username%password.
+	</para>
+	
+	<para>
+		The variable <emphasis>PASSWD</emphasis> may contain the password of the
+person using the client.
+	</para>
+
+	<para>
+		The variable <emphasis>PASSWD_FILE</emphasis> may contain the pathname
+of a file to read the password from. A single line of input is
+read and used as the password.
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>NOTES</title>
+	
+	<para>This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled.</para>
+</refsect1>
+
+<refsect1>
+	<title>CONFIGURATION</title>
+		<para>
+The primary mechanism for making configuration changes and for reading 
+debug information for the cifs vfs is via the Linux /proc filesystem.
+In the directory <filename>/proc/fs/cifs</filename> are various 
+configuration files and pseudo files which can display debug information.  
+There are additional startup options such as maximum buffer size and number
+of buffers which only may be set when the kernel cifs vfs (cifs.ko module) is 
+loaded.  These can be seen by running the modinfo utility against the file
+cifs.ko which will list the options that may be passed to cifs during module
+installation (device driver load).
+For more information see the kernel file <filename>fs/cifs/README</filename>.
+</para>
+</refsect1>
+
+<refsect1>
+	<title>BUGS</title>
+
+	<para>Mounting using the CIFS URL specification is currently not supported.
+	</para>
+
+	<para>The credentials file does not handle usernames or passwords with
+		leading space.</para>
+
+	<para>
+Note that the typical response to a bug report is a suggestion
+to try the latest version first. So please try doing that first,
+and always include which versions you use of relevant software
+when reporting bugs (minimum: mount.cifs (try mount.cifs -V), kernel (see /proc/version) and
+server type you are trying to contact.
+</para>
+</refsect1>
+
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 1.52 of 
+	the cifs vfs filesystem (roughly Linux kernel 2.6.24).</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para>
+	Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel
+	source tree may contain additional options and information.
+</para>
+        <para><citerefentry><refentrytitle>umount.cifs</refentrytitle>
+        <manvolnum>8</manvolnum></citerefentry></para>
+
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>Steve French</para>
+
+	<para>The syntax and manpage were loosely based on that of smbmount. It 
+		was converted to Docbook/XML by Jelmer Vernooij.</para>
+
+	<para>The maintainer of the Linux cifs vfs and the userspace
+		tool <emphasis>mount.cifs</emphasis> is <ulink url="mailto:sfrench@samba.org">Steve French</ulink>.
+		The <ulink url="mailto:linux-cifs-client@lists.samba.org">Linux CIFS Mailing list</ulink> 
+		is the preferred place to ask questions regarding these programs. 
+	</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/net.8.xml b/docs-xml/manpages-3/net.8.xml
new file mode 100644
index 00000000000..9e2558eb322
--- /dev/null
+++ b/docs-xml/manpages-3/net.8.xml
@@ -0,0 +1,1548 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="net.8">
+
+<refmeta>
+	<refentrytitle>net</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>net</refname>
+	<refpurpose>Tool for administration of Samba and remote
+	CIFS servers.
+	</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>net</command>
+		<arg choice="req">&lt;ads|rap|rpc&gt;</arg>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-w workgroup</arg>
+		<arg choice="opt">-W myworkgroup</arg>
+		<arg choice="opt">-U user</arg>
+		<arg choice="opt">-I ip-address</arg>
+		<arg choice="opt">-p port</arg>
+		<arg choice="opt">-n myname</arg>
+		<arg choice="opt">-s conffile</arg>
+		<arg choice="opt">-S server</arg>
+		<arg choice="opt">-l</arg>
+		<arg choice="opt">-P</arg>
+		<arg choice="opt">-d debuglevel</arg>
+		<arg choice="opt">-V</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The Samba net utility is meant to work just like the net utility 
+	available for windows and DOS. The first argument should be used 
+	to specify the protocol to use when executing a certain command. 
+	ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) 
+	clients and RPC can be used for NT4 and Windows 2000. If this 
+	argument is omitted, net will try to determine it automatically. 
+	Not all commands are available on all protocols.
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		&stdarg.help;
+		
+		<varlistentry>
+		<term>-w target-workgroup</term>
+		<listitem><para>
+		Sets target workgroup or domain. You have to specify 
+		either this option or the IP address or the name of a server.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-W workgroup</term>
+		<listitem><para>
+		Sets client workgroup or domain
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-U user</term>
+		<listitem><para>
+		User name to use
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-I ip-address</term>
+		<listitem><para>
+		IP address of target server to use. You have to
+		specify either this option or a target workgroup or
+		a target server.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-p port</term>
+		<listitem><para>
+		Port on the target server to connect to (usually 139 or 445). 
+		Defaults to trying 445 first, then 139.
+		</para></listitem>
+		</varlistentry>
+
+		&stdarg.netbios.name;
+		&stdarg.configfile;
+
+		<varlistentry>
+		<term>-S server</term>
+		<listitem><para>
+		Name of target server. You should specify either 
+		this option or a target workgroup or a target IP address.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-l</term>
+		<listitem><para>
+		When listing data, give more information on each item.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-P</term>
+		<listitem><para>
+		Make queries to the external server using the machine account of the local server.
+		</para></listitem>
+		</varlistentry>
+
+		&stdarg.server.debug;
+	</variablelist>
+</refsect1>
+
+<refsect1>
+<title>COMMANDS</title>
+
+<refsect2>
+<title>CHANGESECRETPW</title>
+
+<para>This command allows the Samba machine account password to be set from an external application
+to a machine account password that has already been stored in Active Directory. DO NOT USE this command
+unless you know exactly what you are doing. The use of this command requires that the force flag (-f)
+be used also. There will be NO command prompt. Whatever information is piped into stdin, either by
+typing at the command line or otherwise, will be stored as the literal machine password. Do NOT use
+this without care and attention as it will overwrite a legitimate machine password without warning.
+YOU HAVE BEEN WARNED.
+</para>
+
+</refsect2>
+
+<refsect2>
+	<title>TIME</title>
+
+	<para>The <command>NET TIME</command> command allows you to view the time on a remote server
+	or synchronise the time on the local server with the time on the remote server.</para>
+
+<refsect3>
+<title>TIME</title>
+
+<para>Without any options, the <command>NET TIME</command> command 
+displays the time on the remote server.
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>TIME SYSTEM</title>
+
+<para>Displays the time on the remote server in a format ready for <command>/bin/date</command>.</para>
+
+</refsect3>
+
+<refsect3>
+<title>TIME SET</title>
+<para>Tries to set the date and time of the local server to that on 
+the remote server using <command>/bin/date</command>. </para>
+
+</refsect3>
+
+<refsect3>
+<title>TIME ZONE</title>
+
+<para>Displays the timezone in hours from GMT on the remote computer.</para>
+
+</refsect3>
+</refsect2>
+
+<refsect2>
+<title>[RPC|ADS] JOIN [TYPE] [-U username[%password]] [createupn=UPN] [createcomputer=OU] [options]</title>
+
+<para>
+Join a domain.  If the account already exists on the server, and 
+[TYPE] is MEMBER, the machine will attempt to join automatically. 
+(Assuming that the machine has been created in server manager)
+Otherwise, a password will be prompted for, and a new account may
+be created.</para>
+
+<para>
+[TYPE] may be PDC, BDC or MEMBER to specify the type of server
+joining the domain.
+</para>
+
+<para>
+[UPN] (ADS only) set the principalname attribute during the join.  The default
+format is host/netbiosname@REALM.
+</para>
+
+<para>
+[OU] (ADS only) Precreate the computer account in a specific OU.  The
+OU string reads from top to bottom without RDNs, and is delimited by
+a '/'.  Please note that '\' is used for escape by both the shell
+and ldap, so it may need to be doubled or quadrupled to pass through, 
+and it is not used as a delimiter.
+</para>
+</refsect2>
+
+<refsect2>
+<title>[RPC] OLDJOIN [options]</title>
+
+<para>Join a domain. Use the OLDJOIN option to join the domain 
+using the old style of domain joining - you need to create a trust 
+account in server manager first.</para>
+</refsect2>
+
+<refsect2>
+<title>[RPC|ADS] USER</title>
+
+<refsect3>
+<title>[RPC|ADS] USER</title>
+
+<para>List all users</para>
+
+</refsect3>
+
+<refsect3>
+<title>[RPC|ADS] USER DELETE <replaceable>target</replaceable></title>
+
+<para>Delete specified user</para>
+
+</refsect3>
+
+<refsect3>
+<title>[RPC|ADS] USER INFO <replaceable>target</replaceable></title>
+
+<para>List the domain groups of the specified user.</para>
+
+</refsect3>
+
+<refsect3>
+<title>[RPC|ADS] USER RENAME <replaceable>oldname</replaceable> <replaceable>newname</replaceable></title>
+
+<para>Rename specified user.</para>
+
+</refsect3>
+
+<refsect3>
+<title>[RPC|ADS] USER ADD <replaceable>name</replaceable> [password] [-F user flags] [-C comment]</title>
+
+<para>Add specified user.</para>
+</refsect3>
+</refsect2>
+
+<refsect2>
+<title>[RPC|ADS] GROUP</title>
+
+<refsect3>
+<title>[RPC|ADS] GROUP [misc options] [targets]</title>
+<para>List user groups.</para>
+</refsect3>
+
+<refsect3>
+<title>[RPC|ADS] GROUP DELETE <replaceable>name</replaceable> [misc. options]</title>
+
+<para>Delete specified group.</para>
+
+</refsect3>
+
+<refsect3>
+<title>[RPC|ADS] GROUP ADD <replaceable>name</replaceable> [-C comment]</title>
+
+<para>Create specified group.</para>
+
+</refsect3>
+</refsect2>
+
+<refsect2>
+<title>[RAP|RPC] SHARE</title>
+
+<refsect3>
+<title>[RAP|RPC] SHARE [misc. options] [targets]</title>
+
+<para>Enumerates all exported resources (network shares) on target server.</para>
+
+</refsect3>
+
+<refsect3>
+<title>[RAP|RPC] SHARE ADD <replaceable>name=serverpath</replaceable> [-C comment] [-M maxusers] [targets]</title>
+
+<para>Adds a share from a server (makes the export active). Maxusers 
+specifies the number of users that can be connected to the 
+share simultaneously.</para>
+
+</refsect3>
+
+<refsect3>
+<title>SHARE DELETE <replaceable>sharename</replaceable></title>
+
+<para>Delete specified share.</para>
+</refsect3>
+</refsect2>
+
+<refsect2>
+<title>[RPC|RAP] FILE</title>
+
+<refsect3>
+<title>[RPC|RAP] FILE</title>
+
+<para>List all open files on remote server.</para>
+
+</refsect3>
+
+<refsect3>
+<title>[RPC|RAP] FILE CLOSE <replaceable>fileid</replaceable></title>
+
+<para>Close file with specified <replaceable>fileid</replaceable> on 
+remote server.</para>
+
+</refsect3>
+
+<refsect3>
+<title>[RPC|RAP] FILE INFO <replaceable>fileid</replaceable></title>
+
+<para>
+Print information on specified <replaceable>fileid</replaceable>. 
+Currently listed are: file-id, username, locks, path, permissions.
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>[RAP|RPC] FILE USER <replaceable>user</replaceable></title>
+
+<para>
+List files opened by specified <replaceable>user</replaceable>.
+Please note that <command>net rap file user</command> does not work
+against Samba servers. 
+</para>
+
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>SESSION</title>
+
+<refsect3>
+<title>RAP SESSION</title>
+
+<para>Without any other options, SESSION enumerates all active SMB/CIFS 
+sessions on the target server.</para>
+
+</refsect3>
+
+<refsect3>
+<title>RAP SESSION DELETE|CLOSE <replaceable>CLIENT_NAME</replaceable></title>
+
+<para>Close the specified sessions.</para>
+
+</refsect3>
+
+<refsect3>
+<title>RAP SESSION INFO <replaceable>CLIENT_NAME</replaceable></title>
+
+<para>Give a list with all the open files in specified session.</para>
+
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>RAP SERVER <replaceable>DOMAIN</replaceable></title>
+
+<para>List all servers in specified domain or workgroup. Defaults
+to local domain.</para>
+
+</refsect2>
+
+<refsect2>
+<title>RAP DOMAIN</title>
+
+<para>Lists all domains and workgroups visible on the 
+current network.</para>
+
+</refsect2>
+
+<refsect2>
+<title>RAP PRINTQ</title>
+
+<refsect3>
+<title>RAP PRINTQ LIST <replaceable>QUEUE_NAME</replaceable></title>
+
+<para>Lists the specified print queue and print jobs on the server.
+If the <replaceable>QUEUE_NAME</replaceable> is omitted, all 
+queues are listed.</para>
+
+</refsect3>
+
+<refsect3>
+<title>RAP PRINTQ DELETE <replaceable>JOBID</replaceable></title>
+
+<para>Delete job with specified id.</para>
+
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>RAP VALIDATE <replaceable>user</replaceable> [<replaceable>password</replaceable>]</title>
+
+<para>
+Validate whether the specified user can log in to the 
+remote server. If the password is not specified on the commandline, it 
+will be prompted. 
+</para>
+
+&not.implemented;
+
+</refsect2>
+
+<refsect2>
+<title>RAP GROUPMEMBER</title>
+
+<refsect3>
+<title>RAP GROUPMEMBER LIST <replaceable>GROUP</replaceable></title>
+
+<para>List all members of the specified group.</para>
+
+</refsect3>
+
+<refsect3>
+<title>RAP GROUPMEMBER DELETE <replaceable>GROUP</replaceable> <replaceable>USER</replaceable></title>
+
+<para>Delete member from group.</para>
+
+</refsect3>
+
+<refsect3>
+<title>RAP GROUPMEMBER ADD <replaceable>GROUP</replaceable> <replaceable>USER</replaceable></title>
+
+<para>Add member to group.</para>
+
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>RAP ADMIN <replaceable>command</replaceable></title>
+
+<para>Execute the specified <replaceable>command</replaceable> on 
+the remote server. Only works with OS/2 servers.
+</para>
+
+&not.implemented;
+
+</refsect2>
+
+<refsect2>
+<title>RAP SERVICE</title>
+
+<refsect3>
+<title>RAP SERVICE START <replaceable>NAME</replaceable> [arguments...]</title>
+
+<para>Start the specified service on the remote server. Not implemented yet.</para>
+
+&not.implemented;
+
+</refsect3>
+
+<refsect3>
+<title>RAP SERVICE STOP</title>
+
+<para>Stop the specified service on the remote server.</para>
+
+&not.implemented;
+
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>RAP PASSWORD <replaceable>USER</replaceable> <replaceable>OLDPASS</replaceable> <replaceable>NEWPASS</replaceable></title>
+
+<para>
+Change password of <replaceable>USER</replaceable> from <replaceable>OLDPASS</replaceable> to <replaceable>NEWPASS</replaceable>.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>LOOKUP</title>
+
+<refsect3>
+<title>LOOKUP HOST <replaceable>HOSTNAME</replaceable> [<replaceable>TYPE</replaceable>]</title>
+
+<para>
+Lookup the IP address of the given host with the specified type (netbios suffix). 
+The type defaults to 0x20 (workstation).
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>LOOKUP LDAP [<replaceable>DOMAIN</replaceable>]</title>
+
+<para>Give IP address of LDAP server of specified <replaceable>DOMAIN</replaceable>. Defaults to local domain.</para>
+
+</refsect3>
+
+<refsect3>
+<title>LOOKUP KDC [<replaceable>REALM</replaceable>]</title>
+
+<para>Give IP address of KDC for the specified <replaceable>REALM</replaceable>.
+Defaults to local realm.</para>
+
+</refsect3>
+
+<refsect3>
+<title>LOOKUP DC [<replaceable>DOMAIN</replaceable>]</title>
+
+<para>Give IP's of Domain Controllers for specified <replaceable>
+DOMAIN</replaceable>. Defaults to local domain.</para>
+
+</refsect3>
+
+<refsect3>
+<title>LOOKUP MASTER <replaceable>DOMAIN</replaceable></title>
+
+<para>Give IP of master browser for specified <replaceable>DOMAIN</replaceable>
+or workgroup. Defaults to local domain.</para>
+
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>CACHE</title>
+
+<para>Samba uses a general caching interface called 'gencache'. It 
+can be controlled using 'NET CACHE'.</para>
+
+<para>All the timeout parameters support the suffixes:
+
+<simplelist>
+<member>s - Seconds</member>
+<member>m - Minutes</member>
+<member>h - Hours</member>
+<member>d - Days</member>
+<member>w - Weeks</member>
+</simplelist>
+
+</para>
+
+<refsect3>
+<title>CACHE ADD <replaceable>key</replaceable> <replaceable>data</replaceable> <replaceable>time-out</replaceable></title>
+
+<para>Add specified key+data to the cache with the given timeout.</para>
+
+</refsect3>
+
+<refsect3>
+<title>CACHE DEL <replaceable>key</replaceable></title>
+
+<para>Delete key from the cache.</para>
+
+</refsect3>
+
+<refsect3>
+<title>CACHE SET <replaceable>key</replaceable> <replaceable>data</replaceable> <replaceable>time-out</replaceable></title>
+
+<para>Update data of existing cache entry.</para>
+
+</refsect3>
+
+<refsect3>
+<title>CACHE SEARCH <replaceable>PATTERN</replaceable></title>
+
+<para>Search for the specified pattern in the cache data.</para>
+
+</refsect3>
+
+<refsect3>
+<title>CACHE LIST</title>
+
+<para>
+List all current items in the cache.
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>CACHE FLUSH</title>
+
+<para>Remove all the current items from the cache.</para>
+
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>GETLOCALSID [DOMAIN]</title>
+
+<para>Prints the SID of the specified domain, or if the parameter is
+omitted, the SID of the local server.</para>
+
+</refsect2>
+
+<refsect2>
+<title>SETLOCALSID S-1-5-21-x-y-z</title>
+
+<para>Sets SID for the local server to the specified SID.</para>
+
+</refsect2>
+
+<refsect2>
+<title>GETDOMAINSID</title>
+
+<para>Prints the local machine SID and the SID of the current 
+domain.</para>
+
+</refsect2>
+
+<refsect2>
+<title>SETDOMAINSID</title>
+
+<para>Sets the SID of the current domain.</para>
+
+</refsect2>
+
+<refsect2>
+<title>GROUPMAP</title>
+
+<para>Manage the mappings between Windows group SIDs and UNIX groups.
+Common options include:</para>
+
+<itemizedlist>
+<listitem><para>unixgroup - Name of the UNIX group</para></listitem>
+<listitem><para>ntgroup - Name of the Windows NT group (must be
+  resolvable to a SID</para></listitem>
+<listitem><para>rid - Unsigned 32-bit integer</para></listitem>
+<listitem><para>sid - Full SID in the form of "S-1-..."</para></listitem>
+<listitem><para>type - Type of the group; either 'domain', 'local',
+  or 'builtin'</para></listitem>
+<listitem><para>comment - Freeform text description of the group</para></listitem>
+</itemizedlist>
+
+<refsect3>
+<title>GROUPMAP ADD</title>
+
+<para>
+Add a new group mapping entry:
+<programlisting>
+net groupmap add {rid=int|sid=string} unixgroup=string \
+	[type={domain|local}] [ntgroup=string] [comment=string]
+</programlisting>
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>GROUPMAP DELETE</title>
+
+<para>Delete a group mapping entry. If more than one group name matches, the first entry found is deleted.</para>
+
+<para>net groupmap delete {ntgroup=string|sid=SID}</para>
+
+</refsect3>
+
+<refsect3>
+<title>GROUPMAP MODIFY</title>
+
+<para>Update en existing group entry.</para>
+
+<para>
+<programlisting>
+net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] \
+       [comment=string] [type={domain|local}]
+</programlisting>
+</para>
+</refsect3>
+
+<refsect3>
+<title>GROUPMAP LIST</title>
+
+<para>List existing group mapping entries.</para>
+
+<para>net groupmap list [verbose] [ntgroup=string] [sid=SID]</para>
+
+</refsect3>
+</refsect2>
+
+
+
+<refsect2>
+<title>MAXRID</title>
+
+<para>Prints out the highest RID currently in use on the local
+server (by the active 'passdb backend').
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>RPC INFO</title>
+
+<para>Print information about the domain of the remote server,
+such as domain name, domain sid and number of users and groups.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>[RPC|ADS] TESTJOIN</title>
+
+<para>Check whether participation in a domain is still valid.</para>
+
+</refsect2>
+
+<refsect2>
+<title>[RPC|ADS] CHANGETRUSTPW</title>
+
+<para>Force change of domain trust password.</para>
+
+</refsect2>
+
+<refsect2>
+<title>RPC TRUSTDOM</title>
+
+<refsect3>
+<title>RPC TRUSTDOM ADD <replaceable>DOMAIN</replaceable></title>
+
+<para>Add a interdomain trust account for <replaceable>DOMAIN</replaceable>. 
+This is in fact a Samba account named <replaceable>DOMAIN$</replaceable> 
+with the account flag <constant>'I'</constant> (interdomain trust account). 
+If the command is used against localhost it has the same effect as 
+<command>smbpasswd -a -i DOMAIN</command>. Please note that both commands
+expect a appropriate UNIX account. 
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>RPC TRUSTDOM DEL <replaceable>DOMAIN</replaceable></title>
+
+<para>Remove interdomain trust account for 
+<replaceable>DOMAIN</replaceable>. If it is used against localhost 
+it has the same effect as <command>smbpasswd -x DOMAIN$</command>. 
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>RPC TRUSTDOM ESTABLISH <replaceable>DOMAIN</replaceable></title>
+
+<para>
+Establish a trust relationship to a trusting domain. 
+Interdomain account must already be created on the remote PDC.
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>RPC TRUSTDOM REVOKE <replaceable>DOMAIN</replaceable></title>
+<para>Abandon relationship to trusted domain</para>
+
+</refsect3>
+
+<refsect3>
+<title>RPC TRUSTDOM LIST</title>
+
+<para>List all current interdomain trust relationships.</para>
+
+</refsect3>
+
+<refsect3>
+<title>RPC RIGHTS</title>
+
+<para>This subcommand is used to view and manage Samba's rights assignments (also 
+referred to as privileges).  There are three options currently available: 
+<parameter>list</parameter>, <parameter>grant</parameter>, and 
+<parameter>revoke</parameter>.  More details on Samba's privilege model and its use
+can be found in the Samba-HOWTO-Collection.</para>
+
+</refsect3>
+
+
+</refsect2>
+
+<refsect2>
+<title>RPC ABORTSHUTDOWN</title>
+
+<para>Abort the shutdown of a remote server.</para>
+
+</refsect2>
+
+<refsect2>
+<title>RPC SHUTDOWN [-t timeout] [-r] [-f] [-C message]</title>
+
+<para>Shut down the remote server.</para>
+
+<variablelist>
+<varlistentry>
+<term>-r</term>
+<listitem><para>
+Reboot after shutdown.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>-f</term>
+<listitem><para>
+Force shutting down all applications.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>-t timeout</term>
+<listitem><para>
+Timeout before system will be shut down. An interactive 
+user of the system can use this time to cancel the shutdown.
+</para></listitem>
+</varlistentry>'>
+
+<varlistentry>
+<term>-C message</term>
+<listitem><para>Display the specified message on the screen to 
+announce the shutdown.</para></listitem>
+</varlistentry>
+</variablelist>
+
+</refsect2>
+
+<refsect2>
+<title>RPC SAMDUMP</title>
+
+<para>Print out sam database of remote server. You need
+to run this against the PDC, from a Samba machine joined as a BDC. </para>
+</refsect2>
+
+<refsect2>
+<title>RPC VAMPIRE</title>
+
+<para>Export users, aliases and groups from remote server to 
+local server.  You need to run this against the PDC, from a Samba machine joined as a BDC. 
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>RPC GETSID</title>
+
+<para>Fetch domain SID and store it in the local <filename>secrets.tdb</filename>. </para>
+
+</refsect2>
+
+<refsect2>
+<title>ADS LEAVE</title>
+
+<para>Make the remote host leave the domain it is part of. </para>
+
+</refsect2>
+
+<refsect2>
+<title>ADS STATUS</title>
+
+<para>Print out status of machine account of the local machine in ADS.
+Prints out quite some debug info. Aimed at developers, regular 
+users should use <command>NET ADS TESTJOIN</command>.</para>
+
+</refsect2>
+
+<refsect2>
+<title>ADS PRINTER</title>
+
+<refsect3>
+<title>ADS PRINTER INFO [<replaceable>PRINTER</replaceable>] [<replaceable>SERVER</replaceable>]</title>
+
+<para>
+Lookup info for <replaceable>PRINTER</replaceable> on <replaceable>SERVER</replaceable>. The printer name defaults to "*", the 
+server name defaults to the local host.</para>
+
+</refsect3>
+
+<refsect3>
+<title>ADS PRINTER PUBLISH <replaceable>PRINTER</replaceable></title>
+
+<para>Publish specified printer using ADS.</para>
+
+</refsect3>
+
+<refsect3>
+<title>ADS PRINTER REMOVE <replaceable>PRINTER</replaceable></title>
+
+<para>Remove specified printer from ADS directory.</para>
+
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>ADS SEARCH <replaceable>EXPRESSION</replaceable> <replaceable>ATTRIBUTES...</replaceable></title>
+
+<para>Perform a raw LDAP search on a ADS server and dump the results. The 
+expression is a standard LDAP search expression, and the 
+attributes are a list of LDAP fields to show in the results.</para>
+
+<para>Example: <userinput>net ads search '(objectCategory=group)' sAMAccountName</userinput>
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>ADS DN <replaceable>DN</replaceable> <replaceable>(attributes)</replaceable></title>
+
+<para>
+Perform a raw LDAP search on a ADS server and dump the results. The 
+DN standard LDAP DN, and the attributes are a list of LDAP fields 
+to show in the result. 
+</para>
+
+<para>Example: <userinput>net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName</userinput></para>
+
+</refsect2>
+
+<refsect2>
+<title>ADS WORKGROUP</title>
+
+<para>Print out workgroup name for specified kerberos realm.</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM CREATEBUILTINGROUP &lt;NAME&gt;</title>
+
+<para>
+(Re)Create a BUILTIN group.
+Only a wellknown set of BUILTIN groups can be created with this command.
+This is the list of currently recognized group names: Administrators,
+Users, Guests, Power Users, Account Operators, Server Operators, Print
+Operators, Backup Operators, Replicator, RAS Servers, Pre-Windows 2000
+compatible Access.
+
+This command requires a running Winbindd with idmap allocation properly
+configured. The group gid will be allocated out of the winbindd range.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM CREATELOCALGROUP &lt;NAME&gt;</title>
+
+<para>
+Create a LOCAL group (also known as Alias).
+
+This command requires a running Winbindd with idmap allocation properly
+configured. The group gid will be allocated out of the winbindd range.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM DELETELOCALGROUP &lt;NAME&gt;</title>
+
+<para>
+Delete an existing LOCAL group (also known as Alias).
+
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM MAPUNIXGROUP &lt;NAME&gt;</title>
+
+<para>
+Map an existing Unix group and make it a Domain Group, the domain group
+will have the same name.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM UNMAPUNIXGROUP &lt;NAME&gt;</title>
+
+<para>
+Remove an existing group mapping entry.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM ADDMEM &lt;GROUP&gt; &lt;MEMBER&gt;</title>
+
+<para>
+Add a member to a Local group. The group can be specified only by name,
+the member can be specified by name or SID.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM DELMEM  &lt;GROUP&gt; &lt;MEMBER&gt;</title>
+
+<para>
+Remove a member from a Local group. The group and the member must be
+specified by name.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM LISTMEM &lt;GROUP&gt;</title>
+
+<para>
+List Local group members. The group must be specified by name.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM LIST &lt;users|groups|localgroups|builtin|workstations&gt; [verbose]</title>
+
+<para>
+List the specified set of accounts by name. If verbose is specified,
+the rid and description is also provided for each account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SHOW &lt;NAME&gt;</title>
+
+<para>
+Show the full DOMAIN\\NAME the SID and the type for the corresponding
+account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET HOMEDIR &lt;NAME&gt; &lt;DIRECTORY&gt;</title>
+
+<para>
+Set the home directory for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET PROFILEPATH &lt;NAME&gt; &lt;PATH&gt;</title>
+
+<para>
+Set the profile path for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET COMMENT &lt;NAME&gt; &lt;COMMENT&gt;</title>
+
+<para>
+Set the comment for a user or group account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET FULLNAME &lt;NAME&gt; &lt;FULL NAME&gt;</title>
+
+<para>
+Set the full name for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET LOGONSCRIPT &lt;NAME&gt; &lt;SCRIPT&gt;</title>
+
+<para>
+Set the logon script for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET HOMEDRIVE &lt;NAME&gt; &lt;DRIVE&gt;</title>
+
+<para>
+Set the home drive for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET WORKSTATIONS &lt;NAME&gt; &lt;WORKSTATIONS&gt;</title>
+
+<para>
+Set the workstations a user account is allowed to log in from.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET DISABLE &lt;NAME&gt;</title>
+
+<para>
+Set the "disabled" flag for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET PWNOTREQ &lt;NAME&gt;</title>
+
+<para>
+Set the "password not required" flag for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET AUTOLOCK &lt;NAME&gt;</title>
+
+<para>
+Set the "autolock" flag for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET PWNOEXP &lt;NAME&gt;</title>
+
+<para>
+Set the "password do not expire" flag for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM SET PWDMUSTCHANGENOW &lt;NAME&gt; [yes|no]</title>
+
+<para>
+Set or unset the "password must change" flag for a user account.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM POLICY LIST</title>
+
+<para>
+List the available account policies.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM POLICY SHOW &lt;account policy&gt;</title>
+
+<para>
+Show the account policy value.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM POLICY SET &lt;account policy&gt; &lt;value&gt;</title>
+
+<para>
+Set a value for the account policy.
+Valid values can be: "forever", "never", "off", or a number.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>SAM PROVISION</title>
+
+<para>
+Only available if ldapsam:editposix is set and winbindd is running.
+Properly populates the ldap tree with the basic accounts (Administrator)
+and groups (Domain Users, Domain Admins, Domain Guests) on the ldap tree.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>IDMAP DUMP &lt;local tdb file name&gt;</title>
+
+<para>
+Dumps the mappings contained in the local tdb file specified.
+This command is useful to dump only the mappings produced by the idmap_tdb backend.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>IDMAP RESTORE [input file]</title>
+
+<para>
+Restore the mappings from the specified file or stdin.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>IDMAP SECRET &lt;DOMAIN&gt;|ALLOC &lt;secret&gt;</title>
+
+<para>
+Store a secret for the specified domain, used primarily for domains
+that use idmap_ldap as a backend. In this case the secret is used
+as the password for the user DN used to bind to the ldap server.
+</para>
+
+</refsect2>
+
+<refsect2>
+<title>USERSHARE</title>
+
+<para>Starting with version 3.0.23, a Samba server now supports the ability for
+non-root users to add user defined shares to be exported using the "net usershare"
+commands.
+</para>
+
+<para>
+To set this up, first set up your smb.conf by adding to the [global] section:
+
+usershare path = /usr/local/samba/lib/usershares
+
+Next create the directory /usr/local/samba/lib/usershares, change the owner to root and
+set the group owner to the UNIX group who should have the ability to create usershares,
+for example a group called "serverops".
+
+Set the permissions on /usr/local/samba/lib/usershares to 01770.
+
+(Owner and group all access, no access for others, plus the sticky bit,
+which means that a file in that directory can be renamed or deleted only
+by the owner of the file).
+
+Finally, tell smbd how many usershares you will allow by adding to the [global]
+section of smb.conf a line such as :
+
+usershare max shares = 100.
+
+To allow 100 usershare definitions. Now, members of the UNIX group "serverops"
+can create user defined shares on demand using the commands below.
+</para>
+
+<para>The usershare commands are:
+
+<simplelist>
+<member>net usershare add sharename path [comment] [acl] [guest_ok=[y|n]] - to add or change a user defined share.</member>
+<member>net usershare delete sharename - to delete a user defined share.</member>
+<member>net usershare info [-l|--long] [wildcard sharename] - to print info about a user defined share.</member>
+<member>net usershare list [-l|--long] [wildcard sharename] - to list user defined shares.</member>
+</simplelist>
+
+</para>
+
+<refsect3>
+<title>USERSHARE ADD <replaceable>sharename</replaceable> <replaceable>path</replaceable> <replaceable>[comment]</replaceable> <replaceable>[acl]</replaceable> <replaceable>[guest_ok=[y|n]]</replaceable></title>
+
+<para>
+Add or replace a new user defined share, with name "sharename".
+</para>
+
+<para>
+"path" specifies the absolute pathname on the system to be exported.
+Restrictions may be put on this, see the global smb.conf parameters:
+"usershare owner only", "usershare prefix allow list", and
+"usershare prefix deny list".
+</para>
+
+<para>
+The optional "comment" parameter is the comment that will appear
+on the share when browsed to by a client.
+</para>
+
+<para>The optional "acl" field
+specifies which users have read and write access to the entire share.
+Note that guest connections are not allowed unless the smb.conf parameter
+"usershare allow guests" has been set. The definition of a user
+defined share acl is: "user:permission", where user is a valid
+username on the system and permission can be "F", "R", or "D".
+"F" stands for "full permissions", ie. read and write permissions.
+"D" stands for "deny" for a user, ie. prevent this user from accessing
+this share.
+"R" stands for "read only", ie. only allow read access to this
+share (no creation of new files or directories or writing to files).
+</para>
+
+<para>
+The default if no "acl" is given is "Everyone:R", which means any 
+authenticated user has read-only access.
+</para>
+
+<para>
+The optional "guest_ok" has the same effect as the parameter of the
+same name in smb.conf, in that it allows guest access to this user
+defined share. This parameter is only allowed if the global parameter
+"usershare allow guests" has been set to true in the smb.conf.
+</para>
+
+There is no separate command to modify an existing user defined share,
+just use the "net usershare add [sharename]" command using the same
+sharename as the one you wish to modify and specify the new options
+you wish. The Samba smbd daemon notices user defined share modifications
+at connect time so will see the change immediately, there is no need
+to restart smbd on adding, deleting or changing a user defined share.
+</refsect3>
+
+<refsect3>
+<title>USERSHARE DELETE <replaceable>sharename</replaceable></title>
+
+<para>
+Deletes the user defined share by name. The Samba smbd daemon
+immediately notices this change, although it will not disconnect
+any users currently connected to the deleted share.
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>USERSHARE INFO <replaceable>[-l|--long]</replaceable> <replaceable>[wildcard sharename]</replaceable></title>
+
+<para>
+Get info on user defined shares owned by the current user matching the given pattern, or all users.
+</para>
+
+<para>
+net usershare info on its own dumps out info on the user defined shares that were
+created by the current user, or restricts them to share names that match the given
+wildcard pattern ('*' matches one or more characters, '?' matches only one character).
+If the '-l' or '--long' option is also given, it prints out info on user defined
+shares created by other users.
+</para>
+
+<para>
+The information given about a share looks like:
+
+[foobar]
+path=/home/jeremy
+comment=testme
+usershare_acl=Everyone:F
+guest_ok=n
+
+And is a list of the current settings of the user defined share that can be
+modified by the "net usershare add" command.
+</para>
+
+</refsect3>
+
+<refsect3>
+<title>USERSHARE LIST <replaceable>[-l|--long]</replaceable> <replaceable>wildcard sharename</replaceable></title>
+
+<para>
+List all the user defined shares owned by the current user matching the given pattern, or all users.
+</para>
+
+<para>
+net usershare list on its own list out the names of the user defined shares that were
+created by the current user, or restricts the list to share names that match the given
+wildcard pattern ('*' matches one or more characters, '?' matches only one character).
+If the '-l' or '--long' option is also given, it includes the names of user defined
+shares created by other users.
+</para>
+
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>CONF</title>
+
+<para>Starting with version 3.2.0, a Samba server can be configured by data
+stored in registry. This configuration data can be edited with the new "net
+conf" commands.
+</para>
+
+<para>
+The deployment of this configuration data can be activated in two levels from the
+<emphasis>smb.conf</emphasis> file: Share definitions from registry are
+activated by setting <parameter>registry shares</parameter> to
+<quote>yes</quote> in the [global] section and global configuration options are
+activated by setting <smbconfoption name="include">registry</smbconfoption> in
+the [global] section.
+See the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+<manvolnum>5</manvolnum></citerefentry> manpage for details.
+</para>
+
+<para>The conf commands are:
+<simplelist>
+<member>net conf list - Dump the complete configuration in smb.conf like
+format.</member>
+<member>net conf import - Import configuration from file in smb.conf
+format.</member>
+<member>net conf listshares - List the registry shares.</member>
+<member>net conf drop - Delete the complete configuration from
+registry.</member>
+<member>net conf showshare - Show the definition of a registry share.</member>
+<member>net conf addshare - Create a new registry share.</member>
+<member>net conf delshare - Delete a registry share.</member>
+<member>net conf setparm - Store a parameter.</member>
+<member>net conf getparm - Retrieve the value of a parameter.</member>
+<member>net conf delparm - Delete a parameter.</member>
+</simplelist>
+</para>
+
+<refsect3>
+<title>CONF LIST</title>
+
+<para>
+Print the configuration data stored in the registry in a smb.conf-like format to
+standard output.
+</para>
+</refsect3>
+
+<refsect3>
+<title>CONF IMPORT <replaceable>[--test|-T]</replaceable> <replaceable>filename</replaceable> <replaceable>[section]</replaceable></title>
+
+<para>
+This command imports configuration from a file in smb.conf format.
+If a section encountered in the input file is present in registry,
+its contents is replaced. Sections of registry configuration that have
+no counterpart in the input file are not affected. If you want to delete these,
+you will have to use the "net conf drop" or "net conf delshare" commands.
+Optionally, a section may be specified to restrict the effect of the
+import command to that specific section. A test mode is enabled by specifying
+the parameter "-T" on the commandline. In test mode, no changes are made to the
+registry, and the resulting configuration is printed to standard output instead.
+</para>
+</refsect3>
+
+<refsect3>
+<title>CONF LISTSHARES</title>
+
+<para>
+List the names of the shares defined in registry.
+</para>
+</refsect3>
+
+<refsect3>
+<title>CONF DROP</title>
+
+<para>
+Delete the complete configuration data from registry.
+</para>
+</refsect3>
+
+<refsect3>
+<title>CONF SHOWSHARE <replaceable>sharename</replaceable></title>
+
+<para>
+Show the definition of the share or section specified. It is valid to specify
+"global" as sharename to retrieve the global configuration options from
+registry.
+</para>
+</refsect3>
+
+<refsect3>
+<title>CONF ADDSHARE <replaceable>sharename</replaceable> <replaceable>path</replaceable> [<replaceable>writeable={y|N}</replaceable> [<replaceable>guest_ok={y|N}</replaceable> [<replaceable>comment</replaceable>]]] </title>
+
+<para>Create a new share definition in registry.
+The sharename and path have to be given. The share name may
+<emphasis>not</emphasis> be "global". Optionally, values for the very
+common options "writeable", "guest ok" and a "comment" may be specified.
+The same result may be obtained by a sequence of "net conf setparm"
+commands.
+</para>
+</refsect3>
+
+<refsect3>
+<title>CONF DELSHARE <replaceable>sharename</replaceable></title>
+
+<para>
+Delete a share definition from registry.
+</para>
+</refsect3>
+
+<refsect3>
+<title>CONF SETPARM <replaceable>section</replaceable> <replaceable>parameter</replaceable> <replaceable>value</replaceable></title>
+
+<para>
+Store a parameter in registry. The section may be global or a sharename.
+The section is created if it does not exist yet.
+</para>
+</refsect3>
+
+<refsect3>
+<title>CONF GETPARM <replaceable>section</replaceable> <replaceable>parameter</replaceable></title>
+
+<para>
+Show a parameter stored in registry.
+</para>
+</refsect3>
+
+<refsect3>
+<title>CONF DELPARM <replaceable>section</replaceable> <replaceable>parameter</replaceable></title>
+
+<para>
+Delete a parameter stored in registry.
+</para>
+</refsect3>
+
+<refsect3>
+<title></title>
+
+<para>
+</para>
+</refsect3>
+
+</refsect2>
+
+<refsect2>
+<title>HELP [COMMAND]</title>
+
+<para>Gives usage information for the specified command.</para>
+
+</refsect2>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is complete for version 3.0 of the Samba 
+	suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+
+	<para>The net manpage was written by Jelmer Vernooij.</para>
+	
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/nmbd.8.xml b/docs-xml/manpages-3/nmbd.8.xml
new file mode 100644
index 00000000000..5c17044d256
--- /dev/null
+++ b/docs-xml/manpages-3/nmbd.8.xml
@@ -0,0 +1,294 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="nmbd.8">
+
+<refmeta>
+	<refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>nmbd</refname>
+	<refpurpose>NetBIOS name server to provide NetBIOS 
+	over IP naming services to clients</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>nmbd</command>
+		<arg choice="opt">-D</arg>
+		<arg choice="opt">-F</arg>
+		<arg choice="opt">-S</arg>
+		<arg choice="opt">-a</arg>
+		<arg choice="opt">-i</arg>
+		<arg choice="opt">-o</arg>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-V</arg>
+		<arg choice="opt">-d &lt;debug level&gt;</arg>
+		<arg choice="opt">-H &lt;lmhosts file&gt;</arg>
+		<arg choice="opt">-l &lt;log directory&gt;</arg>
+		<arg choice="opt">-p &lt;port number&gt;</arg>
+		<arg choice="opt">-s &lt;configuration file&gt;</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+	<para>This program is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>nmbd</command> is a server that understands 
+	and can reply to NetBIOS over IP name service requests, like 
+	those produced by SMB/CIFS clients such as Windows 95/98/ME, 
+	Windows NT, Windows 2000, Windows XP and LanManager clients. It also
+	participates in the browsing protocols which make up the 
+	Windows "Network Neighborhood" view.</para>
+
+	<para>SMB/CIFS clients, when they start up, may wish to 
+	locate an SMB/CIFS server. That is, they wish to know what 
+	IP number a specified host is using.</para>
+
+	<para>Amongst other services, <command>nmbd</command> will 
+	listen for such requests, and if its own NetBIOS name is 
+	specified it will respond with the IP number of the host it 
+	is running on.  Its "own NetBIOS name" is by
+	default the primary DNS name of the host it is running on, 
+	but this can be overridden by the <smbconfoption name="netbios name"/>
+	in &smb.conf;. Thus <command>nmbd</command> will 
+	reply to broadcast queries for its own name(s). Additional
+	names for <command>nmbd</command> to respond on can be set 
+	via parameters in the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> configuration file.</para>
+
+	<para><command>nmbd</command> can also be used as a WINS 
+	(Windows Internet Name Server) server. What this basically means 
+	is that it will act as a WINS database server, creating a 
+	database from name registration requests that it receives and 
+	replying to queries from clients for these names.</para>
+
+	<para>In addition, <command>nmbd</command> can act as a WINS 
+	proxy, relaying broadcast queries from clients that do 
+	not understand how to talk the WINS protocol to a WINS 
+	server.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-D</term>
+		<listitem><para>If specified, this parameter causes 
+		<command>nmbd</command> to operate as a daemon. That is, 
+		it detaches itself and runs in the background, fielding 
+		requests on the appropriate port. By default, <command>nmbd</command> 
+		will operate as a daemon if launched from a command shell. 
+		nmbd can also be operated from the <command>inetd</command> 
+		meta-daemon, although this is not recommended.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-F</term>
+		<listitem><para>If specified, this parameter causes
+		the main <command>nmbd</command> process to not daemonize,
+		i.e. double-fork and disassociate with the terminal.
+		Child processes are still created as normal to service
+		each connection request, but the main process does not
+		exit. This operation mode is suitable for running
+		<command>nmbd</command> under process supervisors such
+		as <command>supervise</command> and <command>svscan</command>
+		from Daniel J. Bernstein's <command>daemontools</command>
+		package, or the AIX process monitor.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-S</term>
+		<listitem><para>If specified, this parameter causes
+		<command>nmbd</command> to log to standard output rather
+		than a file.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-i</term>
+		<listitem><para>If this parameter is specified it causes the
+		server to run "interactively", not as a daemon, even if the
+		server is executed on the command line of a shell. Setting this
+		parameter negates the implicit daemon mode when run from the
+		command line. <command>nmbd</command> also logs to standard
+		output, as if the <constant>-S</constant> parameter had been
+		given. </para></listitem>
+		</varlistentry>
+
+		&stdarg.help;
+		
+		<varlistentry>
+		<term>-H &lt;filename&gt;</term>
+		<listitem><para>NetBIOS lmhosts file.  The lmhosts 
+		file is a list of NetBIOS names to IP addresses that 
+		is loaded by the nmbd server and used via the name 
+		resolution mechanism <smbconfoption name="name resolve order"/> described in <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> to resolve any 
+		NetBIOS name queries needed by the server. Note 
+		that the contents of this file are <emphasis>NOT</emphasis> 
+		used by <command>nmbd</command> to answer any name queries. 
+		Adding a line to this file affects name NetBIOS resolution 
+		from this host <emphasis>ONLY</emphasis>.</para>
+
+		<para>The default path to this file is compiled into 
+		Samba as part of the build process. Common defaults 
+		are <filename>/usr/local/samba/lib/lmhosts</filename>,
+		<filename>/usr/samba/lib/lmhosts</filename> or
+		<filename>/etc/samba/lmhosts</filename>. See the <citerefentry><refentrytitle>lmhosts</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> man page for details on the contents of this file.</para></listitem>
+		</varlistentry>
+
+		&stdarg.server.debug;
+		&popt.common.samba;
+		
+		<varlistentry>
+		<term>-p &lt;UDP port number&gt;</term>
+		<listitem><para>UDP port number is a positive integer value.
+		This option changes the default UDP port number (normally 137)
+		that <command>nmbd</command> responds to name queries on. Don't
+		use this option unless you are an expert, in which case you
+		won't need help!</para></listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>FILES</title>
+
+	<variablelist>
+		<varlistentry>
+		<term><filename>/etc/inetd.conf</filename></term>
+		<listitem><para>If the server is to be run by the
+		<command>inetd</command> meta-daemon, this file
+		must contain suitable startup information for the
+		meta-daemon. 
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><filename>/etc/rc</filename></term>
+		<listitem><para>or whatever initialization script your
+		system uses).</para>
+
+		<para>If running the server as a daemon at startup,
+		this file will need to contain an appropriate startup
+		sequence for the server.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><filename>/etc/services</filename></term>
+		<listitem><para>If running the server via the
+		meta-daemon <command>inetd</command>, this file
+		must contain a mapping of service name (e.g., netbios-ssn)
+		to service port (e.g., 139) and protocol type (e.g., tcp).
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><filename>/usr/local/samba/lib/smb.conf</filename></term>
+		<listitem><para>This is the default location of 
+		the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> server
+		configuration file. Other common places that systems
+		install this file are <filename>/usr/samba/lib/smb.conf</filename>
+		and <filename>/etc/samba/smb.conf</filename>.</para>
+
+		<para>When run as a WINS server (see the
+			<smbconfoption name="wins support"/>
+		parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> man page),
+		<command>nmbd</command>
+		will store the WINS database in the file <filename>wins.dat</filename>
+		in the <filename>var/locks</filename> directory configured under
+		wherever Samba was configured to install itself.</para>
+
+		<para>If <command>nmbd</command> is acting as a <emphasis>
+				browse master</emphasis> (see the <smbconfoption name="local master"/>
+		parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> man page, <command>nmbd</command>
+		will store the browsing database in the file <filename>browse.dat
+		</filename> in the <filename>var/locks</filename> directory
+		configured under wherever Samba was configured to install itself.
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>SIGNALS</title>
+
+	<para>To shut down an <command>nmbd</command> process it is recommended
+	that SIGKILL (-9) <emphasis>NOT</emphasis> be used, except as a last
+	resort, as this may leave the name database in an inconsistent state.
+	The correct way to terminate <command>nmbd</command> is to send it
+	a SIGTERM (-15) signal and wait for it to die on its own.</para>
+
+	<para><command>nmbd</command> will accept SIGHUP, which will cause
+	it to dump out its namelists into the file <filename>namelist.debug
+	</filename> in the <filename>/usr/local/samba/var/locks</filename>
+	directory (or the <filename>var/locks</filename> directory configured
+	under wherever Samba was configured to install itself). This will also
+	cause <command>nmbd</command> to dump out its server database in
+	the <filename>log.nmb</filename> file.</para>
+
+	<para>The debug log level of nmbd may be raised or lowered
+	using <citerefentry><refentrytitle>smbcontrol</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> (SIGUSR[1|2] signals
+	are no longer used since Samba 2.2). This is to allow
+	transient problems to be diagnosed, whilst still running 
+	at a normally low log level.</para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para>
+	<citerefentry><refentrytitle>inetd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testparm</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testprns</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, and the Internet 
+	RFC's <filename>rfc1001.txt</filename>, <filename>rfc1002.txt</filename>. 
+	In addition the CIFS (formerly SMB) specification is available 
+	as a link from the Web page <ulink noescape="1" url="http://samba.org/cifs/"> 
+	http://samba.org/cifs/</ulink>.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook
+	XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/nmblookup.1.xml b/docs-xml/manpages-3/nmblookup.1.xml
new file mode 100644
index 00000000000..3a8672c7e04
--- /dev/null
+++ b/docs-xml/manpages-3/nmblookup.1.xml
@@ -0,0 +1,223 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="nmblookup">
+
+<refmeta>
+	<refentrytitle>nmblookup</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>nmblookup</refname>
+	<refpurpose>NetBIOS over TCP/IP client used to lookup NetBIOS 
+	names</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>nmblookup</command>
+		<arg choice="opt">-M</arg>
+		<arg choice="opt">-R</arg>
+		<arg choice="opt">-S</arg>
+		<arg choice="opt">-r</arg>
+		<arg choice="opt">-A</arg>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-B &lt;broadcast address&gt;</arg>
+		<arg choice="opt">-U &lt;unicast address&gt;</arg>
+		<arg choice="opt">-d &lt;debug level&gt;</arg>
+		<arg choice="opt">-s &lt;smb config file&gt;</arg>
+		<arg choice="opt">-i &lt;NetBIOS scope&gt;</arg>
+		<arg choice="opt">-T</arg>
+		<arg choice="opt">-f</arg>
+		<arg choice="req">name</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>nmblookup</command> is used to query NetBIOS names 
+	and map them to IP addresses in a network using NetBIOS over TCP/IP 
+	queries. The options allow the name queries to be directed at a 
+	particular IP broadcast area or to a particular machine. All queries 
+	are done over UDP.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-M</term>
+		<listitem><para>Searches for a master browser by looking 
+		up the  NetBIOS name <replaceable>name</replaceable> with a 
+		type of <constant>0x1d</constant>. If <replaceable>
+		name</replaceable> is "-" then it does a lookup on the special name 
+		<constant>__MSBROWSE__</constant>. Please note that in order to 
+		use the name "-", you need to make sure "-" isn't parsed as an 
+		argument, e.g. use : 
+		<userinput>nmblookup -M -- -</userinput>.</para></listitem> 
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-R</term>
+		<listitem><para>Set the recursion desired bit in the packet 
+		to do a recursive lookup. This is used when sending a name 
+		query to a machine running a WINS server and the user wishes 
+		to query the names in the WINS server.  If this bit is unset 
+		the normal (broadcast responding) NetBIOS processing code 
+		on a machine is used instead. See RFC1001, RFC1002 for details.
+		</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-S</term>
+		<listitem><para>Once the name query has returned an IP 
+		address then do a node status query as well. A node status 
+		query returns the NetBIOS names registered by a host.
+		</para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-r</term> 
+		<listitem><para>Try and bind to UDP port 137 to send and receive UDP
+		datagrams. The reason for this option is a bug in Windows 95 
+		where it ignores the source port of the requesting packet 
+	 	and only replies to UDP port 137. Unfortunately, on most UNIX 
+		systems root privilege is needed to bind to this port, and 
+		in addition, if the <citerefentry><refentrytitle>nmbd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> daemon is running on this machine it also binds to this port.
+		</para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-A</term>
+		<listitem><para>Interpret <replaceable>name</replaceable> as 
+		an IP Address and do a node status query on this address.</para>
+		</listitem>
+		</varlistentry>
+
+
+
+		&popt.common.connection;
+		&stdarg.help;
+
+		<varlistentry>
+		<term>-B &lt;broadcast address&gt;</term> 
+		<listitem><para>Send the query to the given broadcast address. Without 
+		this option the default behavior of nmblookup is to send the 
+		query to the broadcast address of the network interfaces as 
+		either auto-detected or defined in the <ulink 
+		url="smb.conf.5.html#INTERFACES"><parameter>interfaces</parameter>
+		</ulink> parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> file.
+		</para></listitem>
+		</varlistentry>
+
+
+
+		<varlistentry>
+		<term>-U &lt;unicast address&gt;</term>
+		<listitem><para>Do a unicast query to the specified address or 
+		host <replaceable>unicast address</replaceable>. This option 
+		(along with the <parameter>-R</parameter> option) is needed to 
+		query a WINS server.</para></listitem>
+		</varlistentry>
+		
+		&stdarg.server.debug;	
+		&popt.common.samba;
+
+		<varlistentry>
+		<term>-T</term> 
+		<listitem><para>This causes any IP addresses found in the 
+		lookup to be looked up via a reverse DNS lookup into a 
+		DNS name, and printed out before each</para>
+		
+		<para><emphasis>IP address .... NetBIOS name</emphasis></para>
+		
+		<para> pair that is the normal output.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-f</term>
+		<listitem><para>
+		Show which flags apply to the name that has been looked up. Possible 
+		answers are zero or more of: Response, Authoritative, 
+		Truncated, Recursion_Desired, Recursion_Available, Broadcast.
+		</para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>name</term>
+		<listitem><para>This is the NetBIOS name being queried. Depending 
+		upon the previous options this may be a NetBIOS name or IP address. 
+		If a NetBIOS name then the different name types may be specified 
+		by appending '#&lt;type&gt;' to the name. This name may also be
+		'*', which will return all registered names within a broadcast 
+		area.</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+		<para><command>nmblookup</command> can be used to query 
+		a WINS server (in the same way <command>nslookup</command> is 
+		used to query DNS servers). To query a WINS server, <command>nmblookup</command> 
+		must be called like this:</para>
+
+		<para><command>nmblookup -U server -R 'name'</command></para>
+
+		<para>For example, running :</para>
+
+		<para><command>nmblookup -U samba.org -R 'IRIX#1B'</command></para>
+
+		<para>would query the WINS server samba.org for the domain 
+		master browser (1B name type) for the IRIX workgroup.</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry>, and <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook
+	XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/ntlm_auth.1.xml b/docs-xml/manpages-3/ntlm_auth.1.xml
new file mode 100644
index 00000000000..d1301fc6426
--- /dev/null
+++ b/docs-xml/manpages-3/ntlm_auth.1.xml
@@ -0,0 +1,410 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="ntlm-auth.1">
+
+<refmeta>
+	<refentrytitle>ntlm_auth</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>ntlm_auth</refname>
+	<refpurpose>tool to allow external access to Winbind's NTLM authentication function</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>ntlm_auth</command>
+		<arg choice="opt">-d debuglevel</arg>
+		<arg choice="opt">-l logdir</arg>
+		<arg choice="opt">-s &lt;smb config file&gt;</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>ntlm_auth</command> is a helper utility that authenticates 
+	users using NT/LM authentication. It returns 0 if the users is authenticated
+	successfully and 1 if access was denied. ntlm_auth uses winbind to access 
+	the user and authentication data for a domain.  This utility 
+	is only indended to be used by other programs (currently
+	<ulink url="http://www.squid-cache.org/">Squid</ulink>
+	and <ulink url="http://download.samba.org/ftp/unpacked/lorikeet/trunk/mod_ntlm_winbind/">mod_ntlm_winbind</ulink>)
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>OPERATIONAL REQUIREMENTS</title>
+
+    <para>
+    The <citerefentry><refentrytitle>winbindd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> daemon must be operational
+    for many of these commands to function.</para>
+
+    <para>Some of these commands also require access to the directory 
+    <filename>winbindd_privileged</filename> in
+    <filename>$LOCKDIR</filename>.  This should be done either by running
+    this command as root or providing group access
+    to the <filename>winbindd_privileged</filename> directory.  For
+    security reasons, this directory should not be world-accessable. </para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+	<varlistentry>
+	<term>--helper-protocol=PROTO</term>
+	<listitem><para>
+	Operate as a stdio-based helper.  Valid helper protocols are:
+        </para> 
+        <variablelist>
+	      <varlistentry>
+		<term>squid-2.4-basic</term>
+		<listitem><para>
+                Server-side helper for use with Squid 2.4's basic (plaintext)
+		authentication.  </para>
+                </listitem>
+		</varlistentry>
+	      <varlistentry>
+		<term>squid-2.5-basic</term>
+		<listitem><para>
+                Server-side helper for use with Squid 2.5's basic (plaintext)
+		authentication. </para>
+                </listitem>
+		</varlistentry>
+	      <varlistentry>
+		<term>squid-2.5-ntlmssp</term>
+		<listitem><para>
+                Server-side helper for use with Squid 2.5's NTLMSSP 
+		authentication. </para>
+		  <para>Requires access to the directory 
+                <filename>winbindd_privileged</filename> in
+		<filename>$LOCKDIR</filename>.  The protocol used is
+		described here: <ulink
+		url="http://devel.squid-cache.org/ntlm/squid_helper_protocol.html">http://devel.squid-cache.org/ntlm/squid_helper_protocol.html</ulink>.
+		This protocol has been extended to allow the
+		NTLMSSP Negotiate packet to be included as an argument
+		to the <command>YR</command> command. (Thus avoiding
+		loss of information in the protocol exchange).
+                </para>
+                </listitem>
+	      </varlistentry>
+	      <varlistentry>
+		<term>ntlmssp-client-1</term>
+		<listitem><para>
+                Client-side helper for use with arbitrary external
+		programs that may wish to use Samba's NTLMSSP 
+		authentication knowledge. </para>
+		  <para>This helper is a client, and as such may be run by any
+		user.  The protocol used is
+		effectively the reverse of the previous protocol.  A
+		<command>YR</command> command (without any arguments)
+		starts the authentication exchange.
+                </para>
+                </listitem>
+	      </varlistentry>
+
+	      <varlistentry>
+		<term>gss-spnego</term>
+		<listitem><para>
+                Server-side helper that implements GSS-SPNEGO.  This
+		uses a protocol that is almost the same as
+		<command>squid-2.5-ntlmssp</command>, but has some
+		subtle differences that are undocumented outside the
+		source at this stage.
+                </para>
+		  <para>Requires access to the directory 
+                <filename>winbindd_privileged</filename> in
+		<filename>$LOCKDIR</filename>.   
+               </para>
+                </listitem>
+		</varlistentry>
+                 
+	        <varlistentry>
+				<term>gss-spnego-client</term>
+		<listitem><para>
+                Client-side helper that implements GSS-SPNEGO.  This
+		also uses a protocol similar to the above helpers, but
+		is currently undocumented.
+                </para>
+                </listitem>
+		</varlistentry>
+
+	        <varlistentry>
+				<term>ntlm-server-1</term>
+		<listitem><para>
+                Server-side helper protocol, intended for use by a
+		RADIUS server or the 'winbind' plugin for pppd, for
+		the provision of MSCHAP and MSCHAPv2 authentication.  
+                </para>
+		<para>This protocol consists of lines in the form:
+                <command>Parameter: value</command> and <command>Parameter::
+                Base64-encode value</command>.  The presence of a single
+                period <command>.</command> indicates that one side has
+                finished supplying data to the other.  (Which in turn
+                could cause the helper to authenticate the
+                user). </para>
+
+		<para>Curently implemented parameters from the
+		external program to the helper are:</para>
+		<variablelist>
+		  <varlistentry>
+		  <term>Username</term>
+		  
+                <listitem><para>The username, expected to be in
+                Samba's <smbconfoption name="unix charset"/>.
+                </para>
+
+		      <para><example>Username: bob</example></para>
+		      <para><example>Username:: Ym9i</example></para>
+		    </listitem></varlistentry>
+
+		  <varlistentry>
+		  <term>Username</term>
+                <listitem><para>The user's domain, expected to be in
+                Samba's <smbconfoption name="unix charset"/>.
+                </para>
+
+		      <para><example>Domain: WORKGROUP</example></para>
+		      <para><example>Domain:: V09SS0dST1VQ</example></para>
+		    </listitem></varlistentry>
+
+		  <varlistentry>
+		  <term>Full-Username</term>
+                <listitem><para>The fully qualified username, expected to be in
+                Samba's <smbconfoption><name>unix
+                charset</name></smbconfoption> and qualified with the
+                <smbconfoption name="winbind separator"/>.
+                </para>
+
+		      <para><example>Full-Username: WORKGROUP\bob</example></para>
+		      <para><example>Full-Username:: V09SS0dST1VQYm9i</example></para>
+		    </listitem></varlistentry>
+
+		  <varlistentry>
+		  <term>LANMAN-Challenge</term>
+		  
+                <listitem><para>The 8 byte <command>LANMAN Challenge</command> value,
+                generated randomly by the server, or (in cases such as
+                MSCHAPv2) generated in some way by both the server and
+                the client.
+                </para>	
+		      <para><example>LANMAN-Challege: 0102030405060708</example></para>
+		    </listitem></varlistentry>
+
+		  <varlistentry>
+		  <term>LANMAN-Response</term>
+		  
+                <listitem><para>The 24 byte <command>LANMAN Response</command> value,
+                calculated from the user's password and the supplied
+                <command>LANMAN Challenge</command>.  Typically, this
+                is provided over the network by a client wishing to authenticate.
+                </para>	
+		      <para><example>LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</example></para>
+
+		    </listitem></varlistentry>
+
+		  <varlistentry>
+		  <term>NT-Response</term>
+                <listitem><para>The >= 24 byte <command>NT Response</command>
+                calculated from the user's password and the supplied
+                <command>LANMAN Challenge</command>.  Typically, this is 
+                provided over the network by a client wishing to authenticate.
+                 </para>	
+		      <para><example>NT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</example></para>
+
+		    </listitem></varlistentry>
+
+		  <varlistentry>
+		  <term>Password</term>
+                <listitem><para>The user's password.  This would be
+                provided by a network client, if the helper is being
+                used in a legacy situation that exposes plaintext
+                passwords in this way.
+                 </para>	
+		      <para><example>Password: samba2</example></para>
+		      <para><example>Password:: c2FtYmEy</example></para>
+
+		    </listitem></varlistentry>
+
+		  <varlistentry>
+		  <term>Request-User-Session-Key</term>
+                <listitem><para>Apon sucessful authenticaiton, return
+                the user session key associated with the login.
+                 </para>	
+		      <para><example>Request-User-Session-Key: Yes</example></para>
+
+		    </listitem></varlistentry>
+
+		  <varlistentry>
+		  <term>Request-LanMan-Session-Key</term>
+                <listitem><para>Apon sucessful authenticaiton, return
+                the LANMAN session key associated with the login.
+                 </para>	
+		      <para><example>Request-LanMan-Session-Key: Yes</example></para>
+
+		    </listitem></varlistentry>
+
+		<para><warning>Implementors should take care to base64 encode
+		any data (such as usernames/passwords) that may contain malicous user data, such as
+		a newline.  They may also need to decode strings from
+		the helper, which likewise may have been base64 encoded.</warning></para>
+	</variablelist>
+
+                </listitem>
+		</varlistentry>
+	</variablelist>
+	</listitem>
+      </varlistentry>
+      
+      <varlistentry>
+	<term>--username=USERNAME</term>
+	<listitem><para>
+	Specify username of user to authenticate
+	</para></listitem>
+	
+      </varlistentry>
+      
+      <varlistentry>
+	<term>--domain=DOMAIN</term>
+	<listitem><para>
+	Specify domain of user to authenticate
+	</para></listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>--workstation=WORKSTATION</term>
+	<listitem><para>
+	Specify the workstation the user authenticated from
+	</para></listitem>
+      </varlistentry>
+
+	<varlistentry>
+	<term>--challenge=STRING</term>
+	<listitem><para>NTLM challenge (in HEXADECIMAL)</para>
+	</listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>--lm-response=RESPONSE</term>
+	<listitem><para>LM Response to the challenge (in HEXADECIMAL)</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>--nt-response=RESPONSE</term>
+	<listitem><para>NT or NTLMv2 Response to the challenge (in HEXADECIMAL)</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>--password=PASSWORD</term>
+	<listitem><para>User's plaintext password</para><para>If 
+	not specified on the command line, this is prompted for when
+	required.  </para>
+
+	  <para>For the NTLMSSP based server roles, this parameter
+	  specifies the expected password, allowing testing without
+	  winbindd operational.</para>
+	</listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>--request-lm-key</term>
+	<listitem><para>Retreive LM session key</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>--request-nt-key</term>
+	<listitem><para>Request NT key</para></listitem>
+	</varlistentry>
+
+      <varlistentry>
+	<term>--diagnostics</term>
+	<listitem><para>Perform Diagnostics on the authentication
+	chain.  Uses the password from <command>--password</command>
+	or prompts for one.</para>
+        </listitem>
+        </varlistentry>
+	
+	<varlistentry>
+	    <term>--require-membership-of={SID|Name}</term>
+	    <listitem><para>Require that a user be a member of specified 
+	    group (either name or SID) for authentication to succeed.</para>
+	    </listitem>
+	</varlistentry>
+
+	  &stdarg.server.debug;
+	  &popt.common.samba;
+	  &stdarg.help;
+	
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLE SETUP</title>
+
+        <para>To setup ntlm_auth for use by squid 2.5, with both basic and
+	NTLMSSP authentication, the following
+	should be placed in the <filename>squid.conf</filename> file.
+<programlisting>
+auth_param ntlm program ntlm_auth --helper-protocol=squid-2.5-ntlmssp
+auth_param basic program ntlm_auth --helper-protocol=squid-2.5-basic
+auth_param basic children 5
+auth_param basic realm Squid proxy-caching web server
+auth_param basic credentialsttl 2 hours
+</programlisting></para>
+
+<note><para>This example assumes that ntlm_auth has been installed into your
+      path, and that the group permissions on
+      <filename>winbindd_privileged</filename> are as described above.</para></note>
+
+	<para>To setup ntlm_auth for use by squid 2.5 with group limitation in addition to the above
+	example, the following should be added to the <filename>squid.conf</filename> file.
+<programlisting>
+auth_param ntlm program ntlm_auth --helper-protocol=squid-2.5-ntlmssp --require-membership-of='WORKGROUP\Domain Users'
+auth_param basic program ntlm_auth --helper-protocol=squid-2.5-basic --require-membership-of='WORKGROUP\Domain Users'
+</programlisting></para>
+	
+</refsect1>
+
+<refsect1>
+	<title>TROUBLESHOOTING</title>
+	
+	<para>If you're experiencing problems with authenticating Internet Explorer running
+	under MS Windows 9X or Millenium Edition against ntlm_auth's NTLMSSP authentication
+	helper (--helper-protocol=squid-2.5-ntlmssp), then please read 
+	<ulink url="http://support.microsoft.com/support/kb/articles/Q239/8/69.ASP">
+	the Microsoft Knowledge Base article #239869 and follow instructions described there</ulink>.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba 
+	suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The ntlm_auth manpage was written by Jelmer Vernooij and
+	Andrew Bartlett.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/pam_winbind.7.xml b/docs-xml/manpages-3/pam_winbind.7.xml
new file mode 100644
index 00000000000..26e3060d6e4
--- /dev/null
+++ b/docs-xml/manpages-3/pam_winbind.7.xml
@@ -0,0 +1,173 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="pam_winbind.7">
+
+<refmeta>
+	<refentrytitle>pam_winbind</refentrytitle>
+	<manvolnum>7</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">7</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>pam_winbind</refname>
+	<refpurpose>PAM module for Winbind</refpurpose>
+</refnamediv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>
+	pam_winbind is a PAM module that can authenticate users against the local domain by talking to the Winbind daemon.
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+	<para>
+	
+		pam_winbind supports several options which can either be set in
+		the PAM configuration files or in the pam_winbind configuration
+		file situated at
+		<filename>/etc/security/pam_winbind.conf</filename>. Options
+		from the PAM configuration file take precedence to those from
+		the configuration file.
+
+		<variablelist>
+
+		<varlistentry>
+		<term>debug</term>
+		<listitem><para>Gives debugging output to syslog.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>debug_state</term>
+		<listitem><para>Gives detailed PAM state debugging output to syslog.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>require_membership_of=[SID or NAME]</term>
+		<listitem><para>
+		If this option is set, pam_winbind will only succeed if the user is a member of the given SID or NAME. A SID
+		can be either a group-SID, an alias-SID or even an user-SID. It is also possible to give a NAME instead of the
+		SID. That name must have the form: <parameter>MYDOMAIN\\mygroup</parameter> or
+		<parameter>MYDOMAIN\\myuser</parameter>.  pam_winbind will, in that case, lookup the SID internally. Note that
+		NAME may not contain any spaces. It is thus recommended to only use SIDs. You can verify the list of SIDs a
+		user is a member of with <command>wbinfo --user-sids=SID</command>.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>try_first_pass</term>
+		<listitem><para></para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>use_first_pass</term>
+		<listitem><para>
+		By default, pam_winbind tries to get the authentication token from a previous module. If no token is available
+		it asks the user for the old password. With this option, pam_winbind aborts with an error if no authentication
+		token from a previous module is available.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>use_authtok</term>
+		<listitem><para>
+		Set the new password to the one provided by the previously stacked password module. If this option is not set 
+		pam_winbind will ask the user for the new password.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>krb5_auth</term>
+		<listitem><para>
+
+		pam_winbind can authenticate using Kerberos when winbindd is
+		talking to an Active Directory domain controller. Kerberos
+		authentication must be enabled with this parameter. When
+		Kerberos authentication can not succeed (e.g. due to clock
+		skew), winbindd will fallback to samlogon authentication over
+		MSRPC. When this parameter is used in conjunction with
+		<parameter>winbind refresh tickets</parameter>, winbind will
+		keep your Ticket Granting Ticket (TGT) uptodate by refreshing
+		it whenever necessary.
+
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>krb5_ccache_type=[type]</term>
+		<listitem><para>
+		
+		When pam_winbind is configured to try kerberos authentication
+		by enabling the <parameter>krb5_auth</parameter> option, it can
+		store the retrieved Ticket Granting Ticket (TGT) in a
+		credential cache. The type of credential cache can be set with
+		this option. Currently the only supported value is:
+		<parameter>FILE</parameter>. In that case a credential cache in
+		the form of /tmp/krb5cc_UID will be created, where UID is
+		replaced with the numeric user id.  Leave empty to just do
+		kerberos authentication without having a ticket cache after the
+		logon has succeeded.
+
+		</para></listitem>
+		</varlistentry>
+	
+		<varlistentry>
+		<term>cached_login</term>
+		<listitem><para>
+		Winbind allows to logon using cached credentials when <parameter>winbind offline logon</parameter> is enabled. To use this feature from the PAM module this option must be set.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>silent</term>
+		<listitem><para>
+		Do not emit any messages.
+		</para></listitem>
+		</varlistentry>
+
+		</variablelist>
+
+
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry>
+	<refentrytitle>wbinfo</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry>
+	<refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
+	<refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry></para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of Samba.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>
+	The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by
+	the Samba Team as an Open Source project similar to the way the Linux kernel is developed.
+	</para>
+	
+	<para>This manpage was written by Jelmer Vernooij and Guenther Deschner.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/pdbedit.8.xml b/docs-xml/manpages-3/pdbedit.8.xml
new file mode 100644
index 00000000000..102cb258547
--- /dev/null
+++ b/docs-xml/manpages-3/pdbedit.8.xml
@@ -0,0 +1,456 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="pdbedit.8">
+
+<refmeta>
+	<refentrytitle>pdbedit</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>pdbedit</refname>
+	<refpurpose>manage the SAM database (Database of Samba Users)</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>pdbedit</command>
+		<arg choice="opt">-L</arg>	
+		<arg choice="opt">-v</arg>	
+		<arg choice="opt">-w</arg>	
+		<arg choice="opt">-u username</arg>	
+		<arg choice="opt">-f fullname</arg>	
+		<arg choice="opt">-h homedir</arg>	
+		<arg choice="opt">-D drive</arg>	
+		<arg choice="opt">-S script</arg>
+		<arg choice="opt">-p profile</arg>	
+		<arg choice="opt">-a</arg>	
+		<arg choice="opt">-t, --password-from-stdin</arg>
+		<arg choice="opt">-m</arg>	
+		<arg choice="opt">-r</arg>	
+		<arg choice="opt">-x</arg>	
+		<arg choice="opt">-i passdb-backend</arg>	
+		<arg choice="opt">-e passdb-backend</arg>   
+		<arg choice="opt">-b passdb-backend</arg>
+		<arg choice="opt">-g</arg>
+		<arg choice="opt">-d debuglevel</arg>
+		<arg choice="opt">-s configfile</arg>
+		<arg choice="opt">-P account-policy</arg>
+		<arg choice="opt">-C value</arg>
+		<arg choice="opt">-c account-control</arg>
+		<arg choice="opt">-y</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The pdbedit program is used to manage the users accounts
+	stored in the sam database and can only be run by root.</para>
+
+	<para>The pdbedit tool uses the passdb modular interface and is
+	independent from the kind of users database used (currently there
+	are smbpasswd, ldap, nis+ and tdb based and more can be added
+	without changing the tool).</para>
+
+	<para>There are five main ways to use pdbedit: adding a user account,
+	removing a user account, modifing a user account, listing user
+	accounts, importing users accounts.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+	<variablelist>
+		<varlistentry>
+		<term>-L</term>
+		<listitem><para>This option lists all the user accounts
+		present in the users database.
+		This option prints a list of user/uid pairs separated by
+		the ':' character.</para>
+		<para>Example: <command>pdbedit -L</command></para>
+		<para><programlisting>
+sorce:500:Simo Sorce
+samba:45:Test User
+</programlisting></para>
+		</listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-v</term>
+		<listitem><para>This option enables the verbose listing format.
+		It causes pdbedit to list the users in the database, printing
+		out the account fields in a descriptive format.</para>
+
+		<para>Example: <command>pdbedit -L -v</command></para>
+		<para><programlisting>
+---------------
+username:       sorce
+user ID/Group:  500/500
+user RID/GRID:  2000/2001
+Full Name:      Simo Sorce
+Home Directory: \\BERSERKER\sorce
+HomeDir Drive:  H:
+Logon Script:   \\BERSERKER\netlogon\sorce.bat
+Profile Path:   \\BERSERKER\profile
+---------------
+username:       samba
+user ID/Group:  45/45
+user RID/GRID:  1090/1091
+Full Name:      Test User
+Home Directory: \\BERSERKER\samba
+HomeDir Drive:  
+Logon Script:   
+Profile Path:   \\BERSERKER\profile
+</programlisting></para>
+		</listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-w</term>
+		<listitem><para>This option sets the "smbpasswd" listing format.
+		It will make pdbedit list the users in the database, printing
+		out the account fields in a format compatible with the
+		<filename>smbpasswd</filename> file format. (see the
+		<citerefentry><refentrytitle>smbpasswd</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> for details)</para>
+
+		<para>Example: <command>pdbedit -L -w</command></para>
+		<programlisting>
+sorce:500:508818B733CE64BEAAD3B435B51404EE:
+          D2A2418EFC466A8A0F6B1DBB5C3DB80C:
+          [UX         ]:LCT-00000000:
+samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:
+          BC281CE3F53B6A5146629CD4751D3490:
+          [UX         ]:LCT-3BFA1E8D:
+</programlisting>
+		</listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-u username</term>
+		<listitem><para>This option specifies the username to be
+		used for the operation requested (listing, adding, removing).
+		It is <emphasis>required</emphasis> in add, remove and modify
+		operations and <emphasis>optional</emphasis> in list
+		operations.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-f fullname</term>
+		<listitem><para>This option can be used while adding or
+		modifing a user account. It will specify the user's full
+		name. </para>
+
+		<para>Example: <command>-f "Simo Sorce"</command></para>
+		</listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-h homedir</term>
+		<listitem><para>This option can be used while adding or
+		modifing a user account. It will specify the user's home
+		directory network path.</para>
+
+		<para>Example: <command>-h "\\\\BERSERKER\\sorce"</command>
+		</para>
+		</listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-D drive</term>
+		<listitem><para>This option can be used while adding or
+		modifing a user account. It will specify the windows drive
+		letter to be used to map the home directory.</para>
+
+		<para>Example: <command>-D "H:"</command>
+		</para>
+		</listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-S script</term>
+		<listitem><para>This option can be used while adding or
+		modifing a user account. It will specify the user's logon
+		script path.</para>
+
+		<para>Example: <command>-S "\\\\BERSERKER\\netlogon\\sorce.bat"</command>
+		</para>
+		</listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-p profile</term>
+		<listitem><para>This option can be used while adding or
+		modifing a user account. It will specify the user's profile
+		directory.</para>
+
+		<para>Example: <command>-p "\\\\BERSERKER\\netlogon"</command>
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-G SID|rid</term>
+		<listitem><para>
+		This option can be used while adding or modifying a user account. It 
+		will specify the users' new primary group SID (Security Identifier) or 
+		rid. </para>
+
+		<para>Example: <command>-G S-1-5-21-2447931902-1787058256-3961074038-1201</command></para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-U SID|rid</term>
+		<listitem><para>
+		This option can be used while adding or modifying a user account. It 
+		will specify the users' new SID (Security Identifier) or 
+		rid. </para>
+
+		<para>Example: <command>-U S-1-5-21-2447931902-1787058256-3961074038-5004</command></para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-c account-control</term>
+		<listitem><para>This option can be used while adding or modifying a user
+				account. It will specify the users' account control property. Possible flags are listed below.
+	</para>
+
+	<para>
+		<itemizedlist>
+			<listitem><para>N: No password required</para></listitem>
+			<listitem><para>D: Account disabled</para></listitem>
+			<listitem><para>H: Home directory required</para></listitem>
+			<listitem><para>T: Temporary duplicate of other account</para></listitem>
+			<listitem><para>U: Regular user account</para></listitem>
+			<listitem><para>M: MNS logon user account</para></listitem>
+			<listitem><para>W: Workstation Trust Account</para></listitem>
+			<listitem><para>S: Server Trust Account</para></listitem>
+			<listitem><para>L: Automatic Locking</para></listitem>
+			<listitem><para>X: Password does not expire</para></listitem>
+			<listitem><para>I: Domain Trust Account</para></listitem>
+		</itemizedlist>
+	</para>
+
+		<para>Example: <command>-c "[X          ]"</command></para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-a</term>
+		<listitem><para>This option is used to add a user into the
+		database. This command needs a user name specified with
+		the -u switch. When adding a new user, pdbedit will also
+		ask for the password to be used.</para>
+
+		<para>Example: <command>pdbedit -a -u sorce</command>
+<programlisting>new password:
+retype new password
+</programlisting>
+</para>
+
+		<note><para>pdbedit does not call the unix password syncronisation 
+				script if <smbconfoption name="unix password sync"/>
+				has been set. It only updates the data in the Samba 
+				user database. 
+			</para>
+
+			<para>If you wish to add a user and synchronise the password
+				that immediately, use <command>smbpasswd</command>'s <option>-a</option> option.
+			</para>
+		</note>
+		</listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-t, --password-from-stdin</term>
+		<listitem><para>This option causes pdbedit to read the password
+		from standard input, rather than from /dev/tty (like the
+		<command>passwd(1)</command> program does).  The password has
+		to be submitted twice and terminated by a newline each.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-r</term>
+		<listitem><para>This option is used to modify an existing user 
+		in the database. This command needs a user name specified with the -u 
+		switch. Other options can be specified to modify the properties of 
+		the specified user. This flag is kept for backwards compatibility, but 
+		it is no longer necessary to specify it.
+		</para></listitem>
+		</varlistentry>
+			
+		<varlistentry>
+		<term>-m</term>
+		<listitem><para>This option may only be used in conjunction 
+		with the <parameter>-a</parameter> option. It will make
+		pdbedit to add a machine trust account instead of a user
+		account (-u username will provide the machine name).</para>
+
+		<para>Example: <command>pdbedit -a -m -u w2k-wks</command>
+		</para>
+		</listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-x</term>
+		<listitem><para>This option causes pdbedit to delete an account
+		from the database. It needs a username specified with the
+		-u switch.</para>
+
+		<para>Example: <command>pdbedit -x -u bob</command></para>
+		</listitem>
+		</varlistentry>
+		
+
+		<varlistentry>
+		<term>-i passdb-backend</term>
+		<listitem><para>Use a different passdb backend to retrieve users
+                than the one specified in smb.conf. Can be used to import data into
+                your local user database.</para>
+
+		<para>This option will ease migration from one passdb backend to
+		another.</para>
+
+		<para>Example: <command>pdbedit -i smbpasswd:/etc/smbpasswd.old
+                </command></para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-e passdb-backend</term>
+		<listitem><para>Exports all currently available users to the
+		specified password database backend.</para>
+
+		<para>This option will ease migration from one passdb backend to
+		another and will ease backing up.</para>
+		
+		<para>Example: <command>pdbedit -e smbpasswd:/root/samba-users.backup</command></para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-g</term>
+		<listitem><para>If you specify <parameter>-g</parameter>,
+		then <parameter>-i in-backend -e out-backend</parameter>
+		applies to the group mapping instead of the user database.</para>
+
+		<para>This option will ease migration from one passdb backend to
+		another and will ease backing up.</para>
+		
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-b passdb-backend</term>
+		<listitem><para>Use a different default passdb backend. </para>
+
+		<para>Example: <command>pdbedit -b xml:/root/pdb-backup.xml -l</command></para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-P account-policy</term>
+		<listitem><para>Display an account policy</para>
+		<para>Valid policies are: minimum password age, reset count minutes, disconnect time,
+		user must logon to change password, password history, lockout duration, min password length,
+		maximum password age and bad lockout attempt.</para>
+
+		<para>Example: <command>pdbedit -P "bad lockout attempt"</command></para>
+<para><programlisting>
+account policy value for bad lockout attempt is 0
+</programlisting></para>
+
+		</listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-C account-policy-value</term>
+		<listitem><para>Sets an account policy to a specified value. 
+		This option may only be used in conjunction
+		with the <parameter>-P</parameter> option.
+		</para>
+
+		<para>Example: <command>pdbedit -P "bad lockout attempt" -C 3</command></para>
+<para><programlisting>
+account policy value for bad lockout attempt was 0
+account policy value for bad lockout attempt is now 3
+</programlisting></para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-y</term>
+		<listitem><para>If you specify <parameter>-y</parameter>,
+		then <parameter>-i in-backend -e out-backend</parameter>
+		applies to the account policies instead of the user database.</para>
+
+		<para>This option will allow to migrate account policies from their default
+		tdb-store into a passdb backend, e.g. an LDAP directory server.</para>
+
+		<para>Example: <command>pdbedit -y -i tdbsam: -e ldapsam:ldap://my.ldap.host</command></para>
+	
+		</listitem>
+		</varlistentry>
+
+		&stdarg.help;
+		&stdarg.server.debug;
+		&popt.common.samba;
+
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>NOTES</title>
+	
+	<para>This command may be used only by root.</para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>smbpasswd</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry></para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+
+	<para>The pdbedit manpage was written by Simo Sorce and Jelmer Vernooij.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/profiles.1.xml b/docs-xml/manpages-3/profiles.1.xml
new file mode 100644
index 00000000000..e0787c69ce3
--- /dev/null
+++ b/docs-xml/manpages-3/profiles.1.xml
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="profiles.1">
+
+<refmeta>
+	<refentrytitle>profiles</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>profiles</refname>
+	<refpurpose>A utility to report and change SIDs in registry files
+	</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>profiles</command>
+		<arg choice="opt">-v</arg>
+		<arg choice="opt">-c SID</arg>
+		<arg choice="opt">-n SID</arg>
+		<arg choice="req">file</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>profiles</command> is a utility that 
+	reports and changes SIDs in windows registry files. It currently only 
+	supports NT.
+	</para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>file</term>
+		<listitem><para>Registry file to view or edit.  </para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-v,--verbose</term>
+		<listitem><para>Increases verbosity of messages. 
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-c SID1 -n SID2</term>
+		<listitem><para>Change all occurences of SID1 in <filename>file</filename> by SID2.
+		</para></listitem>
+		</varlistentry>
+
+		&stdarg.help;
+		
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba 
+	suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The profiles man page was written by Jelmer Vernooij. </para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/rpcclient.1.xml b/docs-xml/manpages-3/rpcclient.1.xml
new file mode 100644
index 00000000000..b9f5afbf472
--- /dev/null
+++ b/docs-xml/manpages-3/rpcclient.1.xml
@@ -0,0 +1,487 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="rpcclient.1">
+
+<refmeta>
+	<refentrytitle>rpcclient</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>rpcclient</refname>
+	<refpurpose>tool for executing client side 
+	MS-RPC functions</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>rpcclient</command>
+		<arg choice="opt">-A authfile</arg>
+		<arg choice="opt">-c &lt;command string&gt;</arg>
+		<arg choice="opt">-d debuglevel</arg>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-l logdir</arg>
+		<arg choice="opt">-N</arg>
+		<arg choice="opt">-s &lt;smb config file&gt;</arg>
+		<arg choice="opt">-U username[%password]</arg>
+		<arg choice="opt">-W workgroup</arg>
+		<arg choice="opt">-N</arg>
+		<arg choice="opt">-I destinationIP</arg>
+		<arg choice="req">server</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>rpcclient</command> is a utility initially developed
+	to test MS-RPC functionality in Samba itself.  It has undergone 
+	several stages of development and stability.  Many system administrators
+	have now written scripts around it to manage Windows NT clients from 
+	their UNIX workstation. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>server</term>
+		<listitem><para>NetBIOS name of Server to which to connect. 
+		The server can be  any SMB/CIFS server.  The name is 
+		resolved using the <smbconfoption name="name resolve order"/> line from <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>.</para></listitem>
+	</varlistentry>
+
+
+		<varlistentry>
+		<term>-c|--command='command string'</term>
+		<listitem><para>execute semicolon separated commands (listed 
+		below)) </para></listitem>
+		</varlistentry>
+
+		
+		<varlistentry>
+		<term>-I IP-address</term>
+		<listitem><para><replaceable>IP address</replaceable> is the address of the server to connect to. 
+		It should be specified in standard "a.b.c.d" notation. </para>
+
+		<para>Normally the client would attempt to locate a named 
+		SMB/CIFS server by looking it up via the NetBIOS name resolution 
+		mechanism described above in the <parameter>name resolve order</parameter> 
+		parameter above. Using this parameter will force the client
+		to assume that the server is on the machine with the specified IP 
+		address and the NetBIOS name component of the resource being 
+		connected to will be ignored. </para>
+
+		<para>There is no default for this parameter. If not supplied, 
+		it will be determined automatically by the client as described 
+		above. </para></listitem>
+		</varlistentry>
+
+		&stdarg.server.debug;
+		&popt.common.samba;
+		&popt.common.credentials;		
+		&popt.common.connection;
+		&stdarg.help;
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>COMMANDS</title>
+
+	<refsect2>
+	<title>LSARPC</title>
+
+	<variablelist>
+		<varlistentry><term>lsaquery</term><listitem><para>Query info policy</para></listitem></varlistentry>
+		
+		<varlistentry><term>lookupsids</term><listitem><para>Resolve a list 
+		of SIDs to usernames.
+		</para></listitem></varlistentry>
+		
+		<varlistentry><term>lookupnames</term><listitem><para>Resolve a list 
+		of usernames to SIDs.
+		</para></listitem></varlistentry>
+		
+		<varlistentry><term>enumtrusts</term><listitem><para>Enumerate trusted domains</para></listitem></varlistentry>
+
+		<varlistentry><term>enumprivs</term><listitem><para>Enumerate privileges</para></listitem></varlistentry>
+
+		<varlistentry><term>getdispname</term><listitem><para>Get the privilege name</para></listitem></varlistentry>
+
+		<varlistentry><term>lsaenumsid</term><listitem><para>Enumerate the LSA SIDS</para></listitem></varlistentry>
+
+		<varlistentry><term>lsaenumprivsaccount</term><listitem><para>Enumerate the privileges of an SID</para></listitem></varlistentry>
+
+		<varlistentry><term>lsaenumacctrights</term><listitem><para>Enumerate the rights of an SID</para></listitem></varlistentry>
+
+		<varlistentry><term>lsaenumacctwithright</term><listitem><para>Enumerate accounts with a right</para></listitem></varlistentry>
+
+		<varlistentry><term>lsaaddacctrights</term><listitem><para>Add rights to an account</para></listitem></varlistentry>
+
+		<varlistentry><term>lsaremoveacctrights</term><listitem><para>Remove rights from an account</para></listitem></varlistentry>
+
+		<varlistentry><term>lsalookupprivvalue</term><listitem><para>Get a privilege value given its name</para></listitem></varlistentry>
+
+		<varlistentry><term>lsaquerysecobj</term><listitem><para>Query LSA security object</para></listitem></varlistentry>
+
+	</variablelist>	
+	</refsect2>
+	
+	<refsect2>
+	<title>LSARPC-DS</title>
+	
+	<variablelist>
+		<varlistentry><term>dsroledominfo</term><listitem><para>Get Primary Domain Information</para></listitem></varlistentry>
+	</variablelist>
+
+	<para> </para>
+
+	<para><emphasis>DFS</emphasis></para>
+	<variablelist>
+		<varlistentry><term>dfsexist</term><listitem><para>Query DFS support</para></listitem></varlistentry>
+		<varlistentry><term>dfsadd</term><listitem><para>Add a DFS share</para></listitem></varlistentry>
+		<varlistentry><term>dfsremove</term><listitem><para>Remove a DFS share</para></listitem></varlistentry>
+		<varlistentry><term>dfsgetinfo</term><listitem><para>Query DFS share info</para></listitem></varlistentry>
+		<varlistentry><term>dfsenum</term><listitem><para>Enumerate dfs shares</para></listitem></varlistentry>
+	</variablelist>
+
+	</refsect2>
+
+	<refsect2>
+	<title>REG</title>
+	<variablelist>
+		<varlistentry><term>shutdown</term><listitem><para>Remote Shutdown</para></listitem></varlistentry>
+		<varlistentry><term>abortshutdown</term><listitem><para>Abort Shutdown</para></listitem></varlistentry>
+	</variablelist>
+
+	</refsect2>
+
+	<refsect2>
+	<title>SRVSVC</title>
+
+	<variablelist>
+		<varlistentry><term>srvinfo</term><listitem><para>Server query info</para></listitem></varlistentry>
+		
+		<varlistentry><term>netshareenum</term><listitem><para>Enumerate shares</para></listitem></varlistentry>
+
+		<varlistentry><term>netfileenum</term><listitem><para>Enumerate open files</para></listitem></varlistentry>
+		
+		<varlistentry><term>netremotetod</term><listitem><para>Fetch remote time of day</para></listitem></varlistentry>
+		
+	</variablelist>
+
+	</refsect2>
+
+	<refsect2>
+	<title>SAMR</title>
+
+	<variablelist>
+		<varlistentry><term>queryuser</term><listitem><para>Query user info</para></listitem></varlistentry>
+		<varlistentry><term>querygroup</term><listitem><para>Query group info</para></listitem></varlistentry>
+		<varlistentry><term>queryusergroups</term><listitem><para>Query user groups</para></listitem></varlistentry>
+		<varlistentry><term>querygroupmem</term><listitem><para>Query group membership</para></listitem></varlistentry>
+		<varlistentry><term>queryaliasmem</term><listitem><para>Query alias membership</para></listitem></varlistentry>
+		<varlistentry><term>querydispinfo</term><listitem><para>Query display info</para></listitem></varlistentry>
+		<varlistentry><term>querydominfo</term><listitem><para>Query domain info</para></listitem></varlistentry>
+		<varlistentry><term>enumdomusers</term><listitem><para>Enumerate domain users</para></listitem></varlistentry>
+		<varlistentry><term>enumdomgroups</term><listitem><para>Enumerate domain groups</para></listitem></varlistentry>
+		<varlistentry><term>enumalsgroups</term><listitem><para>Enumerate alias groups</para></listitem></varlistentry>
+		<varlistentry><term>createdomuser</term><listitem><para>Create domain user</para></listitem></varlistentry>
+		<varlistentry><term>samlookupnames</term><listitem><para>Look up names</para></listitem></varlistentry>
+		<varlistentry><term>samlookuprids</term><listitem><para>Look up names</para></listitem></varlistentry>
+		<varlistentry><term>deletedomuser</term><listitem><para>Delete domain user</para></listitem></varlistentry>
+		<varlistentry><term>samquerysecobj</term><listitem><para>Query SAMR security object</para></listitem></varlistentry>
+		<varlistentry><term>getdompwinfo</term><listitem><para>Retrieve domain password info</para></listitem></varlistentry>
+		<varlistentry><term>lookupdomain</term><listitem><para>Look up domain</para></listitem></varlistentry>
+	</variablelist>
+
+	</refsect2>
+
+	<refsect2>
+	<title>SPOOLSS</title>
+
+	<variablelist>
+		<varlistentry><term>adddriver &lt;arch&gt; &lt;config&gt; [&lt;version&gt;]</term> 
+		<listitem><para>
+		Execute an AddPrinterDriver() RPC to install the printer driver 
+		information on the server.  Note that the driver files should 
+		already exist in the directory returned by  
+		<command>getdriverdir</command>.  Possible values for 
+		<parameter>arch</parameter> are the same as those for 
+		the <command>getdriverdir</command> command.
+		The <parameter>config</parameter> parameter is defined as 
+		follows: </para>
+		
+<para><programlisting>
+Long Printer Name:\
+Driver File Name:\
+Data File Name:\
+Config File Name:\
+Help File Name:\
+Language Monitor Name:\
+Default Data Type:\
+Comma Separated list of Files
+</programlisting></para>
+
+		<para>Any empty fields should be enter as the string "NULL". </para>
+		
+		<para>Samba does not need to support the concept of Print Monitors
+		since these only apply to local printers whose driver can make
+		use of a bi-directional link for communication.  This field should 
+		be "NULL".   On a remote NT print server, the Print Monitor for a 
+		driver must already be installed prior to adding the driver or 
+		else the RPC will fail. </para>
+
+		<para>The <parameter>version</parameter> parameter lets you
+		specify the printer driver version number.  If omitted, the
+		default driver version for the specified architecture will
+		be used.  This option can be used to upload Windows 2000
+		(version 3) printer drivers.</para></listitem></varlistentry>
+	
+		<varlistentry><term>addprinter &lt;printername&gt; 
+		&lt;sharename&gt; &lt;drivername&gt; &lt;port&gt;</term>
+		<listitem><para>
+		Add a printer on the remote server.  This printer 
+ 		will be automatically shared.  Be aware that the printer driver 
+		must already be installed on the server (see <command>adddriver</command>) 
+		and the <parameter>port</parameter>must be a valid port name (see
+		<command>enumports</command>.</para>
+		</listitem></varlistentry>
+
+
+		<varlistentry><term>deldriver</term><listitem><para>Delete the 
+		specified printer driver for all architectures.  This
+		does not delete the actual driver files from the server,
+		only the entry from the server's list of drivers.
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>deldriverex &lt;driver&gt; [architecture] [version]
+		</term><listitem><para>Delete the specified printer driver including driver files. 
+		You can limit this action to a specific architecture and a specific version. 
+		If no architecure is given, all driver files of that driver will be deleted. 
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>enumdata</term><listitem><para>Enumerate all 
+		printer setting data stored on the server. On Windows NT  clients, 
+		these values are stored  in the registry, while Samba servers 
+		store them in the printers TDB.  This command corresponds
+		to the MS Platform SDK GetPrinterData() function (* This
+		command is currently unimplemented).</para></listitem></varlistentry>
+
+		<varlistentry><term>enumdataex</term><listitem><para>Enumerate printer data for a key</para></listitem></varlistentry>
+
+		<varlistentry><term>enumjobs &lt;printer&gt;</term>
+		<listitem><para>List the jobs and status of a given printer. 
+		This command corresponds to the MS Platform SDK EnumJobs() 
+		function</para></listitem></varlistentry>
+
+		<varlistentry><term>enumkey</term><listitem><para>Enumerate
+		printer keys</para></listitem></varlistentry>
+		
+		<varlistentry><term>enumports [level]</term>
+		<listitem><para>
+		Executes an EnumPorts() call using the specified 
+		info level. Currently only info levels 1 and 2 are supported. 
+		</para></listitem></varlistentry>
+
+
+
+		<varlistentry><term>enumdrivers [level]</term> 
+		<listitem><para>
+		Execute an EnumPrinterDrivers() call.  This lists the various installed 
+		printer drivers for all architectures.  Refer to the MS Platform SDK 
+		documentation for more details of the various flags and calling 
+		options. Currently supported info levels are 1, 2, and 3.</para></listitem></varlistentry>
+
+
+
+		<varlistentry><term>enumprinters [level]</term>
+		<listitem><para>Execute an EnumPrinters() call.  This lists the various installed 
+		and share printers.  Refer to the MS Platform SDK documentation for 
+		more details of the various flags and calling options. Currently
+		supported info levels are 1, 2 and 5.</para></listitem></varlistentry>
+
+
+
+
+		<varlistentry><term>getdata &lt;printername&gt; &lt;valuename;&gt;</term> 
+		<listitem><para>Retrieve the data for a given printer setting.  See 
+		the  <command>enumdata</command> command for more information.  
+		This command corresponds to the GetPrinterData() MS Platform 
+		SDK function. </para></listitem></varlistentry>
+
+		<varlistentry><term>getdataex</term><listitem><para>Get
+		printer driver data with
+		keyname</para></listitem></varlistentry>
+
+		
+		<varlistentry><term>getdriver &lt;printername&gt;</term>
+		<listitem><para>
+		Retrieve the printer driver information (such as driver file, 
+		config file, dependent files, etc...) for 
+		the given printer. This command corresponds to the GetPrinterDriver()
+		MS Platform  SDK function. Currently info level 1, 2, and 3 are supported.
+		</para></listitem></varlistentry>
+	
+
+		<varlistentry><term>getdriverdir &lt;arch&gt;</term>
+		<listitem><para>
+		Execute a GetPrinterDriverDirectory()
+		RPC to retrieve the SMB share name and subdirectory for 
+		storing printer driver files for a given architecture.  Possible 
+		values for <parameter>arch</parameter> are "Windows 4.0" 
+		(for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
+		Alpha_AXP", and "Windows NT R4000". </para></listitem></varlistentry>
+
+
+
+		<varlistentry><term>getprinter &lt;printername&gt;</term> 
+		<listitem><para>Retrieve the current printer information.  This command 
+		corresponds to the GetPrinter() MS Platform SDK function. 
+		</para></listitem></varlistentry>
+
+		<varlistentry><term>getprintprocdir</term><listitem><para>Get
+		print processor
+		directory</para></listitem></varlistentry>
+		
+		<varlistentry><term>openprinter &lt;printername&gt;</term> 
+		<listitem><para>Execute an OpenPrinterEx() and ClosePrinter() RPC 
+		against a given printer. </para></listitem></varlistentry>
+
+		<varlistentry><term>setdriver &lt;printername&gt;
+		&lt;drivername&gt;</term>
+		<listitem><para>Execute a SetPrinter() command to update the printer driver
+		associated with an installed printer.  The printer driver must
+		already be correctly installed on the print server.  </para>
+
+		<para>See also the <command>enumprinters</command> and 
+		<command>enumdrivers</command> commands for obtaining a list of
+		of installed printers and drivers.</para></listitem></varlistentry>
+
+		<varlistentry><term>addform</term><listitem><para>Add form</para></listitem></varlistentry>
+		<varlistentry><term>setform</term><listitem><para>Set form</para></listitem></varlistentry>
+		<varlistentry><term>getform</term><listitem><para>Get form</para></listitem></varlistentry>
+		<varlistentry><term>deleteform</term><listitem><para>Delete form</para></listitem></varlistentry>
+		<varlistentry><term>enumforms</term><listitem><para>Enumerate form</para></listitem></varlistentry>
+		<varlistentry><term>setprinter</term><listitem><para>Set printer comment</para></listitem></varlistentry>
+		<varlistentry><term>setprinterdata</term><listitem><para>Set REG_SZ printer data</para></listitem></varlistentry>
+
+		<varlistentry><term>setprintername &lt;printername&gt;
+		&lt;newprintername&gt;</term>
+		<listitem><para>Set printer name</para></listitem></varlistentry>
+
+		<varlistentry><term>rffpcnex</term><listitem><para>Rffpcnex test</para></listitem></varlistentry>
+		
+
+	</variablelist>
+
+	</refsect2>
+
+	<refsect2>
+	<title>NETLOGON</title>
+
+	<variablelist>
+
+	<varlistentry><term>logonctrl2</term>
+	<listitem><para>Logon Control 2</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>logonctrl</term>
+	<listitem><para>Logon Control</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>samsync</term>
+	<listitem><para>Sam Synchronisation</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>samdeltas</term>
+	<listitem><para>Query Sam Deltas</para></listitem>
+	</varlistentry>
+
+	<varlistentry><term>samlogon</term>
+	<listitem><para>Sam Logon</para></listitem>
+	</varlistentry>
+
+	</variablelist>
+	</refsect2>
+
+	<refsect2>
+	<title>GENERAL COMMANDS</title>
+
+	<variablelist>
+		<varlistentry><term>debuglevel</term><listitem><para>Set the current
+		debug level used to log information.</para></listitem></varlistentry>
+
+		<varlistentry><term>help (?)</term><listitem><para>Print a listing of all 
+		known commands or extended help  on a particular command. 
+		</para></listitem></varlistentry>
+		
+		<varlistentry><term>quit (exit)</term><listitem><para>Exit <command>rpcclient
+		</command>.</para></listitem></varlistentry>
+	</variablelist>
+	</refsect2>
+
+</refsect1>
+
+<refsect1>
+	<title>BUGS</title>
+	
+	<para><command>rpcclient</command> is designed as a developer testing tool 
+	and may not be robust in certain areas (such as command line parsing).  
+	It has been known to  generate a core dump upon failures when invalid 
+	parameters where passed to the interpreter. </para>
+
+	<para>From Luke Leighton's original rpcclient man page:</para>
+	
+	<para><emphasis>WARNING!</emphasis> The MSRPC over SMB code has 
+	been developed from examining  Network traces. No documentation is 
+	available from the original creators  (Microsoft) on how MSRPC over 
+	SMB works, or how the individual MSRPC services  work. Microsoft's 
+	implementation of these services has been demonstrated  (and reported) 
+	to be... a bit flaky in places. </para>
+
+	<para>The development of Samba's implementation is also a bit rough, 
+	and as more of the services are understood, it can even result in 
+	versions of <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>rpcclient</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> that are incompatible for some commands or  services. Additionally, 
+	the developers are sending reports to Microsoft,  and problems found 
+	or reported to Microsoft are fixed in Service Packs,  which may 
+	result in incompatibilities.</para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba 
+	suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original rpcclient man page was written by Matthew 
+	Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter.  
+	The conversion to DocBook for Samba 2.2 was done by Gerald 
+	Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was
+	done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/samba.7.xml b/docs-xml/manpages-3/samba.7.xml
new file mode 100644
index 00000000000..75b0fef4f13
--- /dev/null
+++ b/docs-xml/manpages-3/samba.7.xml
@@ -0,0 +1,362 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="samba.7">
+
+<refmeta>
+	<refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">Miscellanea</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>samba</refname>
+	<refpurpose>A Windows SMB/CIFS fileserver for UNIX</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis><command>samba</command></cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+	
+	<para>The Samba software suite is a collection of programs 
+	that implements the Server Message Block (commonly abbreviated 
+	as SMB) protocol for UNIX systems. This protocol is sometimes 
+	also referred to as the Common Internet File System (CIFS). For a
+	more thorough description, see <ulink url="http://www.ubiqx.org/cifs/">
+	http://www.ubiqx.org/cifs/</ulink>. Samba also implements the NetBIOS
+	protocol in nmbd.</para>
+	
+	<variablelist>
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry></term>
+		<listitem><para>The <command>smbd</command> daemon provides the file and print services to 
+		SMB clients, such as Windows 95/98, Windows NT, Windows 
+		for Workgroups or LanManager. The configuration file 
+		for this daemon is described in <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry>
+		</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term><citerefentry><refentrytitle>nmbd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry></term>
+		<listitem><para>The <command>nmbd</command>
+		daemon provides NetBIOS nameservice and browsing
+		support. The configuration file for this daemon 
+		is described in <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry></para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbclient</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>smbclient</command>
+		program implements a simple ftp-like client. This 
+		is useful for accessing SMB shares on other compatible
+		servers (such as Windows NT), and can also be used 
+		to allow a UNIX box to print to a printer attached to 
+		any SMB server (such as a PC running Windows NT).</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>testparm</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>testparm</command>
+		utility is a simple syntax checker for Samba's <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> configuration file.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>testprns</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>testprns</command>
+		utility supports testing printer names defined 
+		in your <filename>printcap</filename> file used 
+		by Samba.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbstatus</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>smbstatus</command>
+		tool provides access to information about the 
+		current connections to <command>smbd</command>.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>nmblookup</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>nmblookup</command>
+		tools allows NetBIOS name queries to be made 
+		from a UNIX host.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbpasswd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry></term>
+		<listitem><para>The <command>smbpasswd</command>
+		command is a tool for changing LanMan and Windows NT 
+		password hashes on Samba and Windows NT servers.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbcacls</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>smbcacls</command> command is 
+		a tool to set ACL's on remote CIFS servers. </para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbsh</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>smbsh</command> command is 
+		a program that allows you to run a unix shell with 
+		with an overloaded VFS.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbtree</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>smbtree</command> command 
+		is a text-based network neighborhood tool.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbtar</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>smbtar</command> can make 
+		backups of data on CIFS/SMB servers.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbspool</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry></term>
+		<listitem><para><command>smbspool</command> is a 
+		helper utility for printing on printers connected 
+		to CIFS servers. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbcontrol</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para><command>smbcontrol</command> is a utility
+		that can change the behaviour of running samba daemons.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>rpcclient</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para><command>rpcclient</command> is a utility
+		that can be used to execute RPC commands on remote 
+		CIFS servers.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>pdbedit</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry></term>
+		<listitem><para>The <command>pdbedit</command> command 
+		can be used to maintain the local user database on 
+		a samba server.</para></listitem></varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>findsmb</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para>The <command>findsmb</command> command 
+		can be used to find SMB servers on the local network.
+		</para></listitem></varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>net</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry></term>
+		<listitem><para>The <command>net</command> command 
+		is supposed to work similar to the DOS/Windows
+		NET.EXE command.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>swat</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry></term>
+		<listitem><para><command>swat</command> is a web-based
+		interface to configuring <filename>smb.conf</filename>.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>winbindd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry></term>
+		<listitem><para><command>winbindd</command> is a daemon 
+		that is used for integrating authentication and 
+		the user database into unix.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>wbinfo</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para><command>wbinfo</command> is a utility 
+		that retrieves and stores information related to winbind.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>profiles</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para><command>profiles</command> is a command-line
+		utility that can be used to replace all occurences of 
+		a certain SID with another SID.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>log2pcap</refentrytitle>
+				<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para><command>log2pcap</command> is a utility 
+				for generating pcap trace files from Samba log 
+				files.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>vfstest</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para><command>vfstest</command> is a utility
+		that can be used to test vfs modules.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>ntlm_auth</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para><command>ntlm_auth</command> is a helper-utility
+		for external programs wanting to do NTLM-authentication.
+		</para></listitem></varlistentry>
+
+		<varlistentry>
+			<term>
+<citerefentry><refentrytitle>smbmount</refentrytitle><manvolnum>8</manvolnum></citerefentry>, 
+<citerefentry><refentrytitle>smbumount</refentrytitle><manvolnum>8</manvolnum></citerefentry>, 
+<citerefentry><refentrytitle>smbmnt</refentrytitle><manvolnum>8</manvolnum></citerefentry></term>
+		<listitem><para><command>smbmount</command>,<command>smbumount</command> and <command>smbmnt</command> are commands that can be used to 
+		mount CIFS/SMB shares on Linux.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smbcquotas</refentrytitle>
+		<manvolnum>1</manvolnum></citerefentry></term>
+		<listitem><para><command>smbcquotas</command> is a tool that 
+		can set remote QUOTA's on server with NTFS 5. </para>
+		</listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>COMPONENTS</title>
+	
+	<para>The Samba suite is made up of several components. Each 
+	component is described in a separate manual page. It is strongly 
+	recommended that you read the documentation that comes with Samba 
+	and the manual pages of those components that you use. If the 
+	manual pages and documents aren't clear enough then please visit
+	<ulink url="http://devel.samba.org/">http://devel.samba.org</ulink>
+	for information on how to file a bug report or submit a patch.</para>
+
+	<para>If you require help, visit the Samba webpage at
+	<ulink url="http://samba.org/">http://www.samba.org/</ulink> and
+	explore the many option available to you.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AVAILABILITY</title>
+	
+	<para>The Samba software suite is licensed under the 
+	GNU Public License(GPL). A copy of that license should 
+	have come with the package in the file COPYING. You are 
+	encouraged to distribute copies of the Samba suite, but 
+	please obey the terms of this license.</para>
+
+	<para>The latest version of the Samba suite can be 
+	obtained via anonymous ftp from samba.org in the
+	directory pub/samba/. It is also available on several 
+	mirror sites worldwide.</para>
+	
+	<para>You may also find useful information about Samba 
+	on the newsgroup <ulink url="news:comp.protocols.smb">
+	comp.protocol.smb</ulink> and the Samba mailing 
+	list. Details on how to join the mailing list are given in 
+	the README file that comes with Samba.</para>
+	
+	<para>If you have access to a WWW viewer (such as Mozilla
+	or Konqueror) then you will also find lots of useful information, 
+	including back issues of the Samba mailing list, at
+	<ulink url="http://lists.samba.org/">http://lists.samba.org</ulink>.</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	
+	<para>This man page is correct for version 3.0 of the 
+	Samba suite. </para>
+</refsect1>
+
+<refsect1>
+	<title>CONTRIBUTIONS</title>
+	
+	<para>If you wish to contribute to the Samba project, 
+	then I suggest you join the Samba mailing list at 
+	<ulink url="http://lists.samba.org/">http://lists.samba.org</ulink>.
+	</para>
+
+	<para>If you have patches to submit, visit
+	<ulink url="http://devel.samba.org/">http://devel.samba.org/</ulink>
+	for information on how to do it properly. We prefer patches 
+	in <command>diff -u</command> format.</para>
+</refsect1>
+
+<refsect1>
+	<title>CONTRIBUTORS</title>
+	
+	<para>Contributors to the project are now too numerous 
+	to mention here but all deserve the thanks of all Samba 
+	users. To see a full list, look at the
+	<filename>change-log</filename> in the source package 
+	for the pre-CVS changes and at <ulink 
+	url="http://cvs.samba.org/">
+	http://cvs.samba.org/</ulink>
+	for the contributors to Samba post-CVS. CVS is the Open Source 
+	source code control system used by the Samba Team to develop 
+	Samba. The project would have been unmanageable without it.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML
+	4.2 for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smb.conf.5.xml b/docs-xml/manpages-3/smb.conf.5.xml
new file mode 100644
index 00000000000..ff94ab696e0
--- /dev/null
+++ b/docs-xml/manpages-3/smb.conf.5.xml
@@ -0,0 +1,859 @@
+<refentry id="smb.conf.5" xmlns:xi="http://www.w3.org/2003/XInclude"
+	                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+	
+<refmeta>
+	<refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">File Formats and Conventions</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smb.conf</refname>
+	<refpurpose>The configuration file for the Samba suite</refpurpose>
+</refnamediv>
+
+<refsect1>
+	<title>SYNOPSIS</title>
+
+	<para>
+	The <filename moreinfo="none">smb.conf</filename> file is a configuration  file for the Samba suite. <filename
+	moreinfo="none">smb.conf</filename> contains  runtime configuration information for the Samba programs. The
+	 <filename moreinfo="none">smb.conf</filename> file is designed to be configured and administered by the
+	 <citerefentry><refentrytitle>swat</refentrytitle> <manvolnum>8</manvolnum></citerefentry> program. The
+	complete description of the file format and possible parameters held within are here for reference purposes.
+	</para> 
+</refsect1>
+
+<refsect1 id="FILEFORMATSECT">
+	<title>FILE FORMAT</title>
+
+	<para>
+	The file consists of sections and parameters. A section begins with the name of the section in square brackets
+	and continues until the next section begins. Sections contain parameters of the form:
+<programlisting>
+<replaceable>name</replaceable> = <replaceable>value </replaceable>
+</programlisting>
+	</para>
+
+	<para>
+	The file is line-based - that is, each newline-terminated line represents either a comment, a section name or
+	a parameter.
+	</para>
+
+	<para>Section and parameter names are not case sensitive.</para>
+
+	<para>
+	Only the first equals sign in a parameter is significant.  Whitespace before or after the first equals sign is
+	discarded.  Leading, trailing and internal whitespace in section and parameter names is irrelevant. Leading
+	and trailing whitespace in a parameter value is discarded. Internal whitespace within a parameter value is
+	retained verbatim.
+	</para>
+
+	<para>
+	Any line beginning with a semicolon (<quote>;</quote>) or a hash (<quote>#</quote>) 
+	character is ignored, as are lines containing only whitespace.
+	</para>
+
+	<para>
+	Any line ending in a <quote><literal>\</literal></quote> is continued on the next line in the customary UNIX fashion.
+	</para>
+
+	<para>
+	The values following the equals sign in parameters are all either a string (no quotes needed) or a boolean,
+	which may be given as yes/no, 0/1 or true/false. Case is not significant in boolean values, but is preserved
+	in string values. Some items such as create masks are numeric.
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>SECTION DESCRIPTIONS</title>
+
+	<para>
+	Each section in the configuration file (except for the [global] section) describes a shared resource (known as
+	a <quote>share</quote>). The section name is the name of the shared resource and the parameters within the
+	section define the shares attributes.
+	</para>
+
+	<para>
+	There are three special sections, [global], [homes] and [printers], which are described under
+	 <emphasis>special sections</emphasis>. The following notes apply to ordinary section descriptions.
+	</para>
+
+	<para>
+	A share consists of a directory to which access is being given plus a description of the access rights
+	which are granted to the user of the service. Some housekeeping options are also specifiable.
+	</para>
+	
+	<para>
+	Sections are either file share services (used by the client as an extension of their native file systems)
+	or printable services (used by the client to access print services on the host running the server).
+	</para>
+	
+	<para>
+	Sections may be designated <emphasis>guest</emphasis> services, in which case no password is required to
+	access them. A specified UNIX <emphasis>guest account</emphasis> is used to define access privileges in this
+	case.
+	</para>
+
+	<para>
+	Sections other than guest services will require a password to access them. The client provides the
+	username. As older clients only provide passwords and not usernames, you may specify a list of usernames to
+	check against the password using the <literal>user =</literal> option in the share definition. For modern clients
+	such as Windows 95/98/ME/NT/2000, this should not be necessary.
+	</para> 
+
+	<para>
+	The access rights granted by the server are masked by the access rights granted to the specified or guest
+	UNIX user by the host system. The server does not grant more access than the host system grants.
+	</para>
+	
+	<para>
+	The following sample section defines a file space share.  The user has write access to the path <filename
+	moreinfo="none">/home/bar</filename>.  The share is accessed via the share name <literal>foo</literal>:
+<programlisting>
+	<smbconfsection name="[foo]"/>
+	<smbconfoption name="path">/home/bar</smbconfoption>
+	<smbconfoption name="read only">no</smbconfoption>
+</programlisting>
+	</para>
+
+	<para>
+	The following sample section defines a printable share.  The share is read-only, but printable. That is,
+	the only write access permitted is via calls to open, write to and close a spool file. The <emphasis>guest
+	ok</emphasis> parameter means access will be permitted as the default guest user (specified elsewhere):
+<programlisting>
+	<smbconfsection name="[aprinter]"/>
+	<smbconfoption name="path">/usr/spool/public</smbconfoption>
+	<smbconfoption name="read only">yes</smbconfoption>
+	<smbconfoption name="printable">yes</smbconfoption>
+	<smbconfoption name="guest ok">yes</smbconfoption>
+</programlisting>
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>SPECIAL SECTIONS</title>
+	
+	<refsect2>
+		<title>The [global] section</title>
+		
+		<para>
+		Parameters in this section apply to the server as a whole, or are defaults for sections that do not
+		specifically define certain items. See the notes under PARAMETERS for more information.
+		</para>
+	</refsect2>
+	
+	<refsect2 id="HOMESECT">
+		<title>The [homes] section</title>
+		
+		<para>
+		If a section called [homes] is included in the configuration file, services connecting clients
+		to their home directories can be created on the fly by the server.
+		</para>
+
+		<para>
+		When the connection request is made, the existing sections are scanned. If a match is found, it is
+		used. If no match is found, the requested section name is treated as a username and looked up in the local
+		password file. If the name exists and the correct password has been given, a share is created by cloning the
+		[homes] section.
+		</para>
+		
+		<para>
+		Some modifications are then made to the newly created share:
+		</para>
+		
+		<itemizedlist>
+			<listitem><para>
+			The share name is changed from homes to the located username.
+			</para></listitem>
+
+			<listitem><para>
+			If no path was given, the path is set to the user's home directory.
+			</para></listitem>
+		</itemizedlist>
+
+		<para>
+		If you decide to use a <emphasis>path =</emphasis> line in your [homes] section, it may be useful 
+		to use the %S macro. For example:
+<programlisting>
+<userinput moreinfo="none">path = /data/pchome/%S</userinput>
+</programlisting>
+		is useful if you have different home directories for your PCs than for UNIX access.
+		</para>
+
+		<para>
+		This is a fast and simple way to give a large number of clients access to their home directories with a minimum 
+		of fuss.
+		</para>
+
+		<para>
+		A similar process occurs if the requested section name is <quote>homes</quote>, except that the share
+		name is not changed to that of the requesting user. This method of using the [homes] section works well if
+		different users share a client PC.
+		</para>
+		
+		<para>
+		The [homes] section can specify all the parameters a normal service section can specify, though some make more sense 
+		than others. The following is a typical and suitable [homes] section:
+<programlisting>
+<smbconfsection name="[homes]"/>
+<smbconfoption name="read only">no</smbconfoption>
+</programlisting>
+		</para>
+	
+		<para>
+		An important point is that if guest access is specified in the [homes] section, all home directories will be 
+		visible to all clients <emphasis>without a password</emphasis>.  In the very unlikely event that this is actually
+		desirable, it is wise to also specify <emphasis>read only access</emphasis>.
+		</para>
+
+		<para>
+		The <emphasis>browseable</emphasis> flag for auto home directories will be inherited from the global browseable 
+		flag, not the [homes] browseable flag. This is useful as it means setting <emphasis>browseable = no</emphasis> in
+		the [homes] section will hide the [homes] share but make any auto home directories visible.
+		</para>
+	</refsect2>
+
+	<refsect2 id="PRINTERSSECT">
+		<title>The [printers] section</title>
+		
+		<para>
+		This section works like [homes], but for printers.
+		</para>
+
+		<para>
+		If a [printers] section occurs in the configuration file, users are able to connect to any printer 
+		specified in the local host's printcap file.
+		</para>
+
+		<para>
+		When a connection request is made, the existing sections are scanned. If a match is found, it is used.
+		If no match is found, but a [homes] section exists, it is used as described above. Otherwise, the requested
+		section name is treated as a printer name and the appropriate printcap file is scanned to see if the requested
+		section name is a valid printer share name. If a match is found, a new printer share is created by cloning the
+		[printers] section.
+		</para>
+
+		<para>
+		A few modifications are then made to the newly created share:
+		</para>
+
+		<itemizedlist>
+			<listitem><para>The share name is set to the located printer name</para></listitem>
+
+			<listitem><para>If no printer name was given, the printer name is set to the located printer name</para></listitem>
+
+			<listitem><para>If the share does not permit guest access and no username was given, the username is set
+				to the located printer name.</para></listitem>
+		</itemizedlist>
+
+		<para>
+		The [printers] service MUST be printable - if you specify otherwise, the server will refuse 
+		to load the configuration file.
+		</para>
+		
+		<para>
+		Typically the path specified is that of a world-writeable spool directory with the sticky bit set on 
+		it. A typical [printers] entry looks like this:
+<programlisting>
+<smbconfsection name="[printers]"/>
+<smbconfoption name="path">/usr/spool/public</smbconfoption>
+<smbconfoption name="guest ok">yes</smbconfoption>
+<smbconfoption name="printable">yes</smbconfoption>
+</programlisting>
+		</para>
+
+		<para>
+		All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned. 
+		If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap. This is a file
+		consisting of one or more lines like this:
+<programlisting>
+alias|alias|alias|alias...    
+</programlisting>
+		</para>
+
+		<para>
+		Each alias should be an acceptable printer name for your printing subsystem. In the [global] section,
+		specify the new file as your printcap.  The server will only recognize names found in your pseudo-printcap,
+		which of course can contain whatever aliases you like. The same technique could be used simply to limit access
+		to a subset of your local printers.
+		</para>
+
+		<para>
+		An alias, by the way, is defined as any component of the first entry of a printcap record. Records are separated by newlines,
+		components (if there are more than one) are separated by vertical bar symbols (<literal>|</literal>).
+		</para>
+		
+		<note><para>
+		On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use
+		<literal>printcap name = lpstat</literal> to automatically obtain a list of printers. See the
+		<literal>printcap name</literal> option for more details.
+		</para></note>
+	</refsect2>
+</refsect1>
+
+<refsect1>
+	<title>USERSHARES</title>
+
+	<para>Starting with Samba version 3.0.23 the capability for non-root users to add, modify, and delete
+	their own share definitions has been added. This capability is called <emphasis>usershares</emphasis> and
+	is controlled by a set of parameters in the [global] section of the smb.conf.
+	The relevant parameters are :
+	</para>
+
+	<variablelist>
+		<varlistentry>
+		<term>usershare allow guests</term>
+		<listitem><para>Controls if usershares can permit guest access.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>usershare max shares</term>
+		<listitem><para>Maximum number of user defined shares allowed.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>usershare owner only</term>
+		<listitem><para>If set only directories owned by the sharing user can be shared.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>usershare path</term>
+		<listitem><para>Points to the directory containing the user defined share definitions.
+		The filesystem permissions on this directory control who can create user defined shares.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>usershare prefix allow list</term>
+		<listitem><para>Comma-separated list of absolute pathnames restricting what directories
+		can be shared. Only directories below the pathnames in this list are permitted.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>usershare prefix deny list</term>
+		<listitem><para>Comma-separated list of absolute pathnames restricting what directories
+		can be shared. Directories below the pathnames in this list are prohibited.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>usershare template share</term>
+		<listitem><para>Names a pre-existing share used as a template for creating new usershares.
+		All other share parameters not specified in the user defined share definition
+		are copied from this named share.</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>To allow members of the UNIX group <literal>foo</literal> to create user defined
+	shares, create the directory to contain the share definitions as follows:
+	</para>
+	<para>Become root:</para>
+<programlisting>
+mkdir /usr/local/samba/lib/usershares
+chgrp foo /usr/local/samba/lib/usershares
+chmod 1770 /usr/local/samba/lib/usershares
+</programlisting>
+<para>Then add the parameters 
+
+<programlisting>
+	<smbconfoption name="usershare path">/usr/local/samba/lib/usershares</smbconfoption>
+	<smbconfoption name="usershare max shares">10</smbconfoption> # (or the desired number of shares)
+</programlisting> 
+
+	to the global
+	section of your <filename>smb.conf</filename>. Members of the group foo may then manipulate the user defined shares
+	using the following commands.</para>
+
+	<variablelist>
+		<varlistentry>
+		<term>net usershare add sharename path [comment] [acl] [guest_ok=[y|n]]</term>
+		<listitem><para>To create or modify (overwrite) a user defined share.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>net usershare delete sharename</term>
+		<listitem><para>To delete a user defined share.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>net usershare list wildcard-sharename</term>
+		<listitem><para>To list user defined shares.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>net usershare info wildcard-sharename</term>
+		<listitem><para>To print information about user defined shares.</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+	
+<refsect1>
+	<title>PARAMETERS</title>
+
+	<para>Parameters define the specific attributes of sections.</para>
+
+	<para>
+	Some parameters are specific to the [global] section (e.g., <emphasis>security</emphasis>).  Some parameters
+	are usable in all sections (e.g., <emphasis>create mask</emphasis>). All others are permissible only in normal
+	sections. For the purposes of the following descriptions the [homes] and [printers] sections will be
+	considered normal.  The letter <emphasis>G</emphasis> in parentheses indicates that a parameter is specific to
+	the [global] section. The letter <emphasis>S</emphasis> indicates that a parameter can be specified in a
+	service specific section. All <emphasis>S</emphasis> parameters can also be specified in the [global] section
+	- in which case they will define the default behavior for all services.
+	</para>
+
+	<para>
+	Parameters are arranged here in alphabetical order - this may not create best bedfellows, but at least you can
+	find them! Where there are synonyms, the preferred synonym is described, others refer to the preferred
+	synonym.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>VARIABLE SUBSTITUTIONS</title>
+
+	<para>
+	Many of the strings that are settable in the config file can take substitutions. For example the option
+	<quote>path = /tmp/%u</quote> is interpreted as <quote>path = /tmp/john</quote> if the user connected with the
+	username john.
+	</para>
+
+	<para>
+	These substitutions are mostly noted in the descriptions below, but there are some general substitutions
+	which apply whenever they might be relevant. These are:
+	</para>
+
+	<variablelist>
+		<varlistentry>
+		<term>%U</term>
+		<listitem><para>session username (the username that the client wanted, not
+			necessarily the same as the one they got).</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>%G</term>
+		<listitem><para>primary group name of %U.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>%h</term>
+		<listitem><para>the Internet hostname that Samba is running on.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>%m</term>
+		<listitem><para>the NetBIOS name of the client machine (very useful).</para>
+
+			<para>This parameter is not available when Samba listens on port 445, as clients no longer
+			send this information. If you use this macro in an include statement on a domain that has
+			a Samba domain controller be sure to set in the [global] section <parameter>smb ports =
+			139</parameter>. This will cause Samba to not listen on port 445 and will permit include
+			functionality to function as it did with Samba 2.x.
+			</para></listitem>
+
+		</varlistentry>
+		
+		<varlistentry>
+		<term>%L</term>
+		<listitem><para>the NetBIOS name of the server. This allows you to change your config based on what
+			the client calls you. Your server can have a <quote>dual personality</quote>.
+		</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>%M</term>
+		<listitem><para>the Internet name of the client machine.
+		</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>%R</term>
+		<listitem><para>the selected protocol level after protocol negotiation. It can be one of CORE, COREPLUS, 
+			LANMAN1, LANMAN2 or NT1.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>%d</term>
+		<listitem><para>the process id of the current server
+			process.</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>%a</term>
+		<listitem><para>
+		    The architecture of the remote
+		    machine.  It currently recognizes Samba (<constant>Samba</constant>), 
+		    the Linux CIFS file system (<constant>CIFSFS</constant>), OS/2, (<constant>OS2</constant>),
+		    Windows for Workgroups (<constant>WfWg</constant>), Windows 9x/ME 
+		    (<constant>Win95</constant>), Windows NT (<constant>WinNT</constant>),
+		    Windows 2000 (<constant>Win2K</constant>),
+		    Windows XP (<constant>WinXP</constant>),
+		    Windows XP 64-bit(<constant>WinXP64</constant>),
+		    Windows 2003 including
+		    2003R2 (<constant>Win2K3</constant>), and Windows
+		    Vista (<constant>Vista</constant>).  Anything else will be known as 
+		    <constant>UNKNOWN</constant>.</para> 
+		</listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>%I</term>
+		<listitem><para>the IP address of the client machine.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>%i</term>
+		<listitem><para>the local IP address to which a client connected.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>%T</term>
+		<listitem><para>the current date and time.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>%D</term>
+		<listitem><para>name of the domain or workgroup of the current user.</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>%w</term>
+		<listitem><para>the winbind separator.</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>%$(<replaceable>envvar</replaceable>)</term>
+		<listitem><para>the value of the environment variable
+		<replaceable>envar</replaceable>.</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>
+	The following substitutes apply only to some configuration options (only those that are
+	used when a connection has been established):
+	</para>
+
+	<variablelist>
+		<varlistentry>
+		<term>%S</term>
+		<listitem><para>the name of the current service, if any.</para>
+		</listitem>
+		</varlistentry>
+	
+		<varlistentry>
+		<term>%P</term>
+		<listitem><para>the root directory of the current service, if any.</para></listitem>
+		</varlistentry>
+	
+		<varlistentry>
+		<term>%u</term>
+		<listitem><para>username of the current service, if any.</para>
+		</listitem>
+		</varlistentry>
+	
+		<varlistentry>
+		<term>%g</term>
+		<listitem><para>primary group name of %u.</para></listitem>
+		</varlistentry>
+	
+		<varlistentry>
+		<term>%H</term>
+		<listitem><para>the home directory of the user given by %u.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>%N</term>
+		<listitem><para>
+			the name of your NIS home directory server.  This is obtained from your NIS auto.map entry. 
+			If you have not compiled Samba with the <emphasis>--with-automount</emphasis> option, this
+			value will be the same as %L.</para></listitem>
+		</varlistentry>
+	
+		<varlistentry>
+		<term>%p</term>
+		<listitem><para>
+			the path of the service's home directory, obtained from your NIS auto.map entry. The NIS
+			auto.map entry is split up as <literal>%N:%p</literal>.</para></listitem>
+		</varlistentry>
+	</variablelist>
+	
+	<para>
+	There are some quite creative things that can be done with these substitutions and other
+	<filename moreinfo="none">smb.conf</filename> options.
+	</para>
+</refsect1>
+
+<refsect1 id="NAMEMANGLINGSECT">
+	<title>NAME MANGLING</title>
+	
+	<para>
+	Samba supports <literal>name mangling</literal> so that DOS and Windows clients can use files that don't
+	conform to the 8.3 format. It can also be set to adjust the case of 8.3 format filenames.
+	</para>
+
+	<para>
+	There are several options that control the way mangling is performed, and they are grouped here rather
+	than listed separately. For the defaults look at the output of the testparm program.
+	</para>
+
+	<para>
+	These options can be set separately for each service.
+	</para>
+
+	<para>
+	The options are:
+	</para>
+	
+	<variablelist>
+	
+	<varlistentry>
+		<term>case sensitive = yes/no/auto</term>
+		<listitem><para>
+		controls whether filenames are case sensitive. If they aren't, Samba must do a filename search and match on
+		passed names. The default setting of auto allows clients that support case sensitive filenames (Linux CIFSVFS
+		and smbclient 3.0.5 and above currently) to tell the Samba server on a per-packet basis that they wish to
+		access the file system in a case-sensitive manner (to support UNIX case sensitive semantics). No Windows or
+		DOS system supports case-sensitive filename so setting this option to auto is that same as setting it to no
+		for them. Default <emphasis>auto</emphasis>.
+		</para></listitem>
+		</varlistentry> 
+
+		<varlistentry>
+		<term>default case = upper/lower</term>
+		<listitem><para>
+		controls what the default case is for new filenames (ie. files that don't currently exist in the filesystem).
+		Default <emphasis>lower</emphasis>.  IMPORTANT NOTE: This option will be used to modify the case of
+		<emphasis>all</emphasis> incoming client filenames, not just new filenames if the options <smbconfoption
+		name="case sensitive">yes</smbconfoption>, <smbconfoption name="preserve case">No</smbconfoption>,
+		<smbconfoption name="short preserve case">No</smbconfoption> are set.  This change is needed as part of the
+		optimisations for directories containing large numbers of files.
+		</para></listitem>
+		</varlistentry> 
+	
+		<varlistentry>
+		<term>preserve case = yes/no</term>
+		<listitem><para>
+		controls whether new files (ie. files that don't currently exist in the filesystem) are created with the case
+		that the client passes, or if they are forced to be the <literal>default</literal> case. Default
+		<emphasis>yes</emphasis>.
+		</para></listitem>
+		</varlistentry> 
+
+		<varlistentry>
+		<term>short preserve case = yes/no</term>
+		<listitem><para>
+		controls if new files (ie. files that don't currently exist in the filesystem) which conform to 8.3 syntax,
+		that is all in upper case and of suitable length, are created upper case, or if they are forced to be the
+		<literal>default</literal> case. This option can be used with <literal>preserve case = yes</literal> to permit
+		long filenames to retain their case, while short names are lowercased. Default <emphasis>yes</emphasis>.
+		</para></listitem>
+		</varlistentry> 
+	</variablelist>
+	
+	<para>
+	By default, Samba 3.0 has the same semantics as a Windows NT server, in that it is case insensitive
+	but case preserving. As a special case for directories with large numbers of files, if the case
+	options are set as follows, "case sensitive = yes", "case preserve = no", "short preserve case = no"
+	then the "default case" option will be applied and will modify all filenames sent from the client
+	when accessing this share.
+	</para>
+	
+</refsect1>
+
+<refsect1 id="VALIDATIONSECT">
+	<title>NOTE ABOUT USERNAME/PASSWORD VALIDATION</title>
+
+	<para>
+	There are a number of ways in which a user can connect to a service. The server uses the following steps
+	in determining if it will allow a connection to a specified service. If all the steps fail, the connection
+	request is rejected.  However, if one of the steps succeeds, the following steps are not checked.
+	</para>
+
+	<para>
+	If the service is marked <quote>guest only = yes</quote> and the server is running with share-level
+	security (<quote>security = share</quote>, steps 1 to 5 are skipped.
+	</para>
+
+
+	<orderedlist continuation="restarts" inheritnum="ignore" numeration="arabic">
+		<listitem><para>
+		If the client has passed a username/password pair and that username/password pair is validated by the UNIX 
+		system's password programs, the connection is made as that username. This includes the
+		<literal>\\server\service</literal>%<replaceable>username</replaceable> method of passing a username.
+		</para></listitem>
+
+		<listitem><para>
+		If the client has previously registered a username with the system and now supplies a correct password for that 
+		username, the connection is allowed.
+		</para></listitem>
+		
+		<listitem><para>
+		The client's NetBIOS name and any previously used usernames are checked against the supplied password. If 
+		they match, the connection is allowed as the corresponding user.
+		</para></listitem>
+		
+		<listitem><para>
+		If the client has previously validated a username/password pair with the server and the client has passed 
+		the validation token, that username is used.
+		</para></listitem>
+
+		<listitem><para>
+		If a <literal>user = </literal> field is given in the <filename moreinfo="none">smb.conf</filename> file for the
+		service and the client has supplied a password, and that password matches (according to the UNIX system's
+		password checking) with one of the usernames from the <literal>user =</literal> field, the connection is made as
+		the username in the <literal>user =</literal> line. If one of the usernames in the <literal>user =</literal> list
+		begins with a <literal>@</literal>, that name expands to a list of names in the group of the same name.
+		</para></listitem>
+
+		<listitem><para>
+		If the service is a guest service, a connection is made as the username given in the <literal>guest account
+		=</literal> for the service, irrespective of the supplied password.
+		</para></listitem>
+	</orderedlist>
+
+</refsect1>
+
+<refsect1>
+	<title>REGISTRY-BASED CONFIGURATION</title>
+
+	<para>
+		Starting with Samba version 3.2.0, the capability to
+		store Samba configuration in the registry is available.
+		There are two levels of registry configuration:
+	</para>
+
+	<orderedlist continuation="restarts" inheritnum="ignore" numeration="arabic">
+		<listitem><para>Share definitions stored in registry are used.
+		This is triggered by setting the global 
+		parameter <parameter>registry shares</parameter> to <quote>yes</quote> 
+		in <emphasis>smb.conf</emphasis>.
+		</para>
+
+		<para>Note: Shares defined in <emphasis>smb.conf</emphasis>
+		always take priority over
+		shares of the same name defined in registry.
+		</para></listitem>
+
+		<listitem><para>Global <emphasis>smb.conf</emphasis> options stored in
+		registry are used. This	is triggered by the 
+		parameter <smbconfoption name="config backend">registry</smbconfoption> in
+		the [global] section of <emphasis>smb.conf</emphasis>.
+		This removes everything that has been read from config files
+		to this point and reads the content of the global configuration
+		section from the registry.
+		Activation of global registry options automatically
+		activates registry shares. In this case, no share definitions
+		from smb.conf are read: This is a registry only configuration
+		with the advantage that share definitions are not read
+		in a bulk at startup time but on demand when a share is
+		accessed.
+		</para></listitem>
+	</orderedlist>
+
+	<para>
+		Caveat: To make registry-based configurations foolproof at least to a
+		certain extent, the use 
+		of <parameter>lock directory</parameter>, 
+		 <parameter>config backend</parameter>, and
+		 <parameter>include</parameter> inside the registry
+		configuration has been disabled. Especially, by changing the
+		 <parameter>lock directory</parameter> inside the registry
+		configuration, one would create a broken setup where the daemons
+		do not see the configuration they loaded once it is active.
+	</para>
+
+	<para>
+		The registry configuration can be accessed with
+		tools like <emphasis>regedit</emphasis> or <emphasis>net rpc
+		registry</emphasis> in the key
+		 <emphasis><literal>HKLM\Software\Samba\smbconf</literal></emphasis>.
+
+		More conveniently, the <emphasis>conf</emphasis> subcommand of the
+		 <citerefentry><refentrytitle>net</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> utility
+		offers a dedicated interface to read and write the
+		registry based configuration locally, i.e. directly
+		accessing the database file, circumventing the
+		server.
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>EXPLANATION OF EACH PARAMETER</title>
+	
+	<samba:parameterlist>
+		<xi:include href="../smbdotconf/parameters.all.xml" parse="xml"/>
+	</samba:parameterlist>
+
+</refsect1>
+
+<refsect1>
+	<title>WARNINGS</title>
+	
+	<para>
+	Although the configuration file permits service names to contain spaces, your client software may not.
+	Spaces will be ignored in comparisons anyway, so it shouldn't be a problem - but be aware of the possibility.
+	</para>
+
+	<para>
+	On a similar note, many clients - especially DOS clients - limit service names to eight characters.
+	<citerefentry><refentrytitle>smbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry> has no such
+	limitation, but attempts to connect from such clients will fail if they truncate the service names.  For this
+	reason you should probably keep your service names down to eight characters in length.
+	</para>
+
+	<para>
+	Use of the <literal>[homes]</literal> and <literal>[printers]</literal> special sections make life 
+	for an administrator easy, but the various combinations of default attributes can be tricky. Take extreme
+	care when designing these sections. In particular, ensure that the permissions on spool directories are
+	correct.
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para>
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbpasswd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>swat</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>nmblookup</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testparm</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testprns</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>
+	The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.
+	</para>
+	
+	<para>
+	The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink noescape="1" url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 release by Jeremy Allison.  The conversion
+	to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by
+	Alexander Bokovoy.
+	</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbcacls.1.xml b/docs-xml/manpages-3/smbcacls.1.xml
new file mode 100644
index 00000000000..695d58ae640
--- /dev/null
+++ b/docs-xml/manpages-3/smbcacls.1.xml
@@ -0,0 +1,264 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbcacls.1">
+
+<refmeta>
+	<refentrytitle>smbcacls</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbcacls</refname>
+	<refpurpose>Set or get ACLs on an NT file or directory names</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbcacls</command>
+		<arg choice="req">//server/share</arg>
+		<arg choice="req">filename</arg>
+		<arg choice="opt">-D acls</arg>
+		<arg choice="opt">-M acls</arg>
+		<arg choice="opt">-a acls</arg>
+		<arg choice="opt">-S acls</arg>
+		<arg choice="opt">-C name</arg>
+		<arg choice="opt">-G name</arg>
+		<arg choice="opt">--numeric</arg>
+		<arg choice="opt">-t</arg>
+		<arg choice="opt">-U username</arg>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-d</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>smbcacls</command> program manipulates NT Access Control
+	Lists (ACLs) on SMB file shares. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<para>The following options are available to the <command>smbcacls</command> program.  
+	The format of ACLs is described in the section ACL FORMAT </para>
+
+
+	<variablelist>
+		<varlistentry>
+		<term>-a acls</term>
+		<listitem><para>Add the ACLs specified to the ACL list.  Existing 
+		access control entries are unchanged. </para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-M acls</term>
+		<listitem><para>Modify the mask value (permissions) for the ACLs 
+		specified on the command line.  An error will be printed for each 
+		ACL specified that was not already present in the ACL list
+		</para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-D acls</term>
+		<listitem><para>Delete any ACLs specified on the command line.  
+		An error will be printed for each ACL specified that was not 
+		already present in the ACL list. </para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-S acls</term>
+		<listitem><para>This command sets the ACLs on the file with 
+		only the ones specified on the command line.  All other ACLs are 
+		erased. Note that the ACL specified must contain at least a revision,
+		type, owner and group for the call to succeed. </para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-U username</term>
+		<listitem><para>Specifies a username used to connect to the 
+		specified service.  The username may be of the form "username" in 
+		which case the user is prompted to enter in a password and the 
+		workgroup specified in the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> file is 
+		used, or "username%password"  or "DOMAIN\username%password" and the 
+		password and workgroup names are used as provided. </para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-C name</term>
+		<listitem><para>The owner of a file or directory can be changed 
+		to the name given using the <parameter>-C</parameter> option.  
+		The name can be a sid in the form S-1-x-y-z or a name resolved 
+		against the server specified in the first argument. </para>
+		
+		<para>This command is a shortcut for -M OWNER:name. 
+		</para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-G name</term>
+		<listitem><para>The group owner of a file or directory can 
+		be changed to the name given using the <parameter>-G</parameter> 
+		option.  The name can be a sid in the form S-1-x-y-z or a name 
+		resolved against the server specified n the first argument.
+		</para>
+		
+		<para>This command is a shortcut for -M GROUP:name.</para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>--numeric</term>
+		<listitem><para>This option displays all ACL information in numeric 
+		format.  The default is to convert SIDs to names and ACE types 
+		and masks to a readable string format.  </para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-t</term>
+		<listitem><para>
+		Don't actually do anything, only validate the correctness of 
+		the arguments.
+		</para></listitem>
+		</varlistentry>
+				
+		&stdarg.help;
+		&stdarg.server.debug;
+		&popt.common.samba;
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>ACL FORMAT</title>
+
+	<para>The format of an ACL is one or more ACL entries separated by 
+	either commas or newlines.  An ACL entry is one of the following: </para>
+
+<para><programlisting> 
+REVISION:&lt;revision number&gt;
+OWNER:&lt;sid or name&gt;
+GROUP:&lt;sid or name&gt;
+ACL:&lt;sid or name&gt;:&lt;type&gt;/&lt;flags&gt;/&lt;mask&gt;
+</programlisting></para>
+  
+
+	<para>The revision of the ACL specifies the internal Windows 
+	NT ACL revision for the security descriptor.  
+	If not specified it defaults to 1.  Using values other than 1 may 
+	cause strange behaviour. </para>
+
+	<para>The owner and group specify the owner and group sids for the 
+	object.  If a SID in the format S-1-x-y-z is specified this is used, 
+	otherwise the name specified is resolved using the server on which 
+	the file or directory resides. </para>
+
+	<para>ACLs specify permissions granted to the SID.  This SID again 
+	can be specified in S-1-x-y-z format or as a name in which case 
+	it is resolved against the server on which the file or directory 
+	resides.  The type, flags and mask values determine the type of 
+	access granted to the SID. </para>
+
+	<para>The type can be either 0 or 1 corresponding to ALLOWED or 
+	DENIED access to the SID.  The flags values are generally
+	zero for file ACLs and either 9 or 2 for directory ACLs.  Some 
+	common flags are: </para>
+
+	<itemizedlist> 
+		<listitem><para><constant>#define SEC_ACE_FLAG_OBJECT_INHERIT     	0x1</constant></para></listitem>
+		<listitem><para><constant>#define SEC_ACE_FLAG_CONTAINER_INHERIT  	0x2</constant></para></listitem>
+		<listitem><para><constant>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT     0x4</constant></para></listitem>
+		<listitem><para><constant>#define SEC_ACE_FLAG_INHERIT_ONLY       	0x8</constant></para></listitem>
+ 	</itemizedlist>
+  
+	<para>At present flags can only be specified as decimal or 
+	hexadecimal values.</para>
+ 
+	<para>The mask is a value which expresses the access right 
+	granted to the SID. It can be given as a decimal or hexadecimal value, 
+	or by using one of the following text strings which map to the NT 
+	file permissions of the same name. </para>
+
+	<itemizedlist>
+		<listitem><para><emphasis>R</emphasis> - Allow read access </para></listitem>
+		<listitem><para><emphasis>W</emphasis> - Allow write access</para></listitem>
+		<listitem><para><emphasis>X</emphasis> - Execute permission on the object</para></listitem>
+		<listitem><para><emphasis>D</emphasis> - Delete the object</para></listitem>
+		<listitem><para><emphasis>P</emphasis> - Change permissions</para></listitem>
+		<listitem><para><emphasis>O</emphasis> - Take ownership</para></listitem>
+	</itemizedlist>
+
+
+	<para>The following combined permissions can be specified:</para>
+
+
+	<itemizedlist>
+		<listitem><para><emphasis>READ</emphasis> -  Equivalent to 'RX'
+		permissions</para></listitem>
+		<listitem><para><emphasis>CHANGE</emphasis> - Equivalent to 'RXWD' permissions
+		</para></listitem>
+		<listitem><para><emphasis>FULL</emphasis> - Equivalent to 'RWXDPO' 
+		permissions</para></listitem>
+	</itemizedlist>
+	</refsect1>
+
+<refsect1>
+	<title>EXIT STATUS</title>
+
+	<para>The <command>smbcacls</command> program sets the exit status 
+	depending on the success or otherwise of the operations performed.  
+	The exit status may be one of the following values. </para>
+
+	<para>If the operation succeeded, smbcacls returns and exit 
+	status of 0.  If <command>smbcacls</command> couldn't connect to the specified server, 
+	or there was an error getting or setting the ACLs, an exit status 
+	of 1 is returned.  If there was an error parsing any command line 
+	arguments, an exit status of 2 is returned. </para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para><command>smbcacls</command> was written by Andrew Tridgell 
+	and Tim Potter.</para>
+	
+	<para>The conversion to DocBook for Samba 2.2 was done 
+	by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done
+	by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbclient.1.xml b/docs-xml/manpages-3/smbclient.1.xml
new file mode 100644
index 00000000000..e8e1b215cdd
--- /dev/null
+++ b/docs-xml/manpages-3/smbclient.1.xml
@@ -0,0 +1,1135 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbclient.1">
+
+<refmeta>
+	<refentrytitle>smbclient</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbclient</refname>
+	<refpurpose>ftp-like client to access SMB/CIFS resources 
+	on servers</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbclient</command>
+		<arg choice="opt">-b &lt;buffer size&gt;</arg>
+		<arg choice="opt">-d debuglevel</arg>
+		<arg choice="opt">-e</arg>
+		<arg choice="opt">-L &lt;netbios name&gt;</arg>
+		<arg choice="opt">-U username</arg>
+		<arg choice="opt">-I destinationIP</arg>
+		<arg choice="opt">-M &lt;netbios name&gt;</arg>
+		<arg choice="opt">-m maxprotocol</arg>
+		<arg choice="opt">-A authfile</arg>
+		<arg choice="opt">-N</arg>
+		<arg choice="opt">-i scope</arg>
+		<arg choice="opt">-O &lt;socket options&gt;</arg>
+		<arg choice="opt">-p port</arg>
+		<arg choice="opt">-R &lt;name resolve order&gt;</arg>
+		<arg choice="opt">-s &lt;smb config file&gt;</arg>
+		<arg choice="opt">-k</arg>
+		<arg choice="opt">-P</arg>
+		<arg choice="opt">-c &lt;command&gt;</arg>
+	</cmdsynopsis>
+		
+	<cmdsynopsis>
+		<command>smbclient</command>
+		<arg choice="req">servicename</arg>
+		<arg choice="opt">password</arg>
+		<arg choice="opt">-b &lt;buffer size&gt;</arg>
+		<arg choice="opt">-d debuglevel</arg>
+		<arg choice="opt">-e</arg>
+		<arg choice="opt">-D Directory</arg>
+		<arg choice="opt">-U username</arg>
+		<arg choice="opt">-W workgroup</arg>
+		<arg choice="opt">-M &lt;netbios name&gt;</arg>
+		<arg choice="opt">-m maxprotocol</arg>
+		<arg choice="opt">-A authfile</arg>
+		<arg choice="opt">-N</arg>
+		<arg choice="opt">-l log-basename</arg>
+		<arg choice="opt">-I destinationIP</arg>
+		<arg choice="opt">-E</arg>
+		<arg choice="opt">-c &lt;command string&gt;</arg>
+		<arg choice="opt">-i scope</arg>
+		<arg choice="opt">-O &lt;socket options&gt;</arg>
+		<arg choice="opt">-p port</arg>
+		<arg choice="opt">-R &lt;name resolve order&gt;</arg>
+		<arg choice="opt">-s &lt;smb config file&gt;</arg>
+		<arg choice="opt">-T&lt;c|x&gt;IXFqgbNan</arg>
+		<arg choice="opt">-k</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>smbclient</command> is a client that can 
+	'talk' to an SMB/CIFS server. It offers an interface
+	similar to that of the ftp program (see <citerefentry><refentrytitle>ftp</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>).  
+	Operations include things like getting files from the server 
+	to the local machine, putting files from the local machine to 
+	the server, retrieving directory information from the server 
+	and so on. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+	
+	<variablelist>
+		<varlistentry>
+		<term>servicename</term>
+		<listitem><para>servicename is the name of the service 
+		you want to use on the server. A service name takes the form
+		<filename>//server/service</filename> where <parameter>server
+		</parameter> is the NetBIOS name of the SMB/CIFS server 
+		offering the desired service and <parameter>service</parameter> 
+		is the name of the service offered.  Thus to connect to 
+		the service "printer" on the SMB/CIFS server "smbserver",
+		you would use the servicename <filename>//smbserver/printer
+		</filename></para>
+
+		<para>Note that the server name required is NOT necessarily 
+		the IP (DNS) host name of the server !  The name required is 
+		a NetBIOS server name, which may or may not be the
+		same as the IP hostname of the machine running the server.
+		</para>
+
+		<para>The server name is looked up according to either 
+		the <parameter>-R</parameter> parameter to <command>smbclient</command> or 
+		using the name resolve order parameter in 
+		the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> file, 
+		allowing an administrator to change the order and methods 
+		by which server names are looked up. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>password</term>
+		<listitem><para>The password required to access the specified 
+		service on the specified server. If this parameter is 
+		supplied, the <parameter>-N</parameter> option (suppress 
+		password prompt) is assumed. </para>
+
+		<para>There is no default password. If no password is supplied 
+		on the command line (either by using this parameter or adding 
+		a password to the <parameter>-U</parameter> option (see 
+		below)) and the <parameter>-N</parameter> option is not 
+		specified, the client will prompt for a password, even if 
+		the desired service does not require one. (If no password is 
+		required, simply press ENTER to provide a null password.)
+		</para>
+
+		<para>Note: Some servers (including OS/2 and Windows for 
+		Workgroups) insist on an uppercase password. Lowercase 
+		or mixed case passwords may be rejected by these servers. 		
+		</para>
+
+		<para>Be cautious about including passwords in scripts.
+		</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-R &lt;name resolve order&gt;</term> 
+		<listitem><para>This option is used by the programs in the Samba 
+		suite to determine what naming services and in what order to resolve 
+		host names to IP addresses. The option takes a space-separated 
+		string of different name resolution options.</para>
+
+		<para>The options are :"lmhosts", "host", "wins" and "bcast". They 
+		cause names to be resolved as follows:</para>
+
+		<itemizedlist>
+			<listitem><para><constant>lmhosts</constant>: Lookup an IP 
+			address in the Samba lmhosts file. If the line in lmhosts has 
+			no name type attached to the NetBIOS name (see 
+			the <citerefentry><refentrytitle>lmhosts</refentrytitle>
+			<manvolnum>5</manvolnum></citerefentry> for details) then
+			any name type matches for lookup.</para>
+			</listitem>
+			
+			<listitem><para><constant>host</constant>: Do a standard host 
+			name to IP address resolution, using the system <filename>/etc/hosts
+			</filename>, NIS, or DNS lookups. This method of name resolution 
+			is operating system dependent, for instance on IRIX or Solaris this 
+			may be controlled by the <filename>/etc/nsswitch.conf</filename> 
+			file).  Note that this method is only used if the NetBIOS name 
+			type being queried is the 0x20 (server) name type, otherwise 
+			it is ignored.</para>
+			</listitem>
+			
+			<listitem><para><constant>wins</constant>: Query a name with 
+			the IP address listed in the <parameter>wins server</parameter>
+			parameter.  If no WINS server has
+			been specified this method will be ignored.</para>
+			</listitem>
+			
+			<listitem><para><constant>bcast</constant>: Do a broadcast on 
+			each of the known local interfaces listed in the 
+			<parameter>interfaces</parameter>
+			parameter. This is the least reliable of the name resolution 
+			methods as it depends on the target host being on a locally 
+			connected subnet.</para>
+			</listitem>
+		</itemizedlist>
+
+		<para>If this parameter is not set then the name resolve order 
+		defined in the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> file parameter  
+		(name resolve order) will be used. </para>
+
+		<para>The default order is lmhosts, host, wins, bcast and without 
+		this parameter or any entry in the <parameter>name resolve order
+		</parameter> parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> file the name resolution
+		methods will be attempted in this order. </para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-M NetBIOS name</term>
+		<listitem><para>This options allows you to send messages, using 
+		the "WinPopup" protocol, to another computer. Once a connection is 
+		established you then type your message, pressing ^D (control-D) to 
+		end. </para>
+
+		<para>If the receiving computer is running WinPopup the user will 
+		receive the message and probably a beep. If they are not running 
+		WinPopup the message will be lost, and no error message will 
+		occur. </para>
+
+		<para>The message is also automatically truncated if the message 
+		is over 1600 bytes, as this is the limit of the protocol. 
+		</para>
+
+		<para>
+		One useful trick is to pipe the message through <command>smbclient</command>. 
+		For example: smbclient -M FRED &lt; mymessage.txt will send the 
+		message in the file <filename>mymessage.txt</filename> to the 
+		machine FRED.
+		</para>
+
+		<para>You may also find the <parameter>-U</parameter> and 
+		<parameter>-I</parameter> options useful, as they allow you to 
+		control the FROM and TO parts of the message. </para>
+
+		<para>See the <parameter>message command</parameter> parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> for a description of how to handle incoming 
+		WinPopup messages in Samba. </para>
+
+		<para><emphasis>Note</emphasis>: Copy WinPopup into the startup group 
+		on your WfWg PCs if you want them to always be able to receive 
+		messages. </para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-p port</term>
+		<listitem><para>This number is the TCP port number that will be used 
+		when making connections to the server. The standard (well-known)
+		TCP port number for an SMB/CIFS server is 139, which is the 
+		default. </para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-P</term>
+		<listitem><para>
+		Make queries to the external server using the machine account of the local server.
+		</para></listitem>
+		</varlistentry>
+		
+		&stdarg.help;
+		
+		<varlistentry>
+		<term>-I IP-address</term>
+		<listitem><para><replaceable>IP address</replaceable> is the address of the server to connect to. 
+		It should be specified in standard "a.b.c.d" notation. </para>
+
+		<para>Normally the client would attempt to locate a named 
+		SMB/CIFS server by looking it up via the NetBIOS name resolution 
+		mechanism described above in the <parameter>name resolve order</parameter> 
+		parameter above. Using this parameter will force the client
+		to assume that the server is on the machine with the specified IP 
+		address and the NetBIOS name component of the resource being 
+		connected to will be ignored. </para>
+
+		<para>There is no default for this parameter. If not supplied, 
+		it will be determined automatically by the client as described 
+		above. </para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-E</term>
+		<listitem><para>This parameter causes the client to write messages 
+		to the standard error stream (stderr) rather than to the standard 
+		output stream. </para>
+		
+		<para>By default, the client writes messages to standard output 
+		- typically the user's tty. </para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-L</term>
+		<listitem><para>This option allows you to look at what services 
+		are available on a server. You use it as <command>smbclient -L 
+		host</command> and a list should appear.  The <parameter>-I
+		</parameter> option may be useful if your NetBIOS names don't 
+		match your TCP/IP DNS host names or if you are trying to reach a 
+		host on another network. </para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-t terminal code</term>
+		<listitem><para>This option tells <command>smbclient</command> how to interpret 
+		filenames coming from the remote server. Usually Asian language 
+		multibyte UNIX implementations use different character sets than 
+		SMB/CIFS servers (<emphasis>EUC</emphasis> instead of <emphasis>
+		SJIS</emphasis> for example). Setting this parameter will let 
+		<command>smbclient</command> convert between the UNIX filenames and 
+		the SMB filenames correctly. This option has not been seriously tested 
+		and may have some problems. </para>
+
+		<para>The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8,
+		CWjunet, CWhex, CWcap. This is not a complete list, check the Samba 
+		source code for the complete list. </para></listitem>
+		</varlistentry>
+			
+		<varlistentry>	
+		<term>-b buffersize</term>
+		<listitem><para>This option changes the transmit/send buffer 
+		size when getting or putting a file from/to the server. The default 
+		is 65520 bytes. Setting this value smaller (to 1200 bytes) has been 
+		observed to speed up file transfers to and from a Win9x server. 
+		</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-e</term>
+		<listitem><para>This command line parameter requires the remote
+		server support the UNIX extensions. Request that the connection be
+		encrypted. This is new for Samba 3.2 and will only work with Samba
+		3.2 or above servers. Negotiates SMB encryption using GSSAPI. Uses
+		the given credentials for the encryption negotiaion (either kerberos
+		or NTLMv1/v2 if given domain/username/password triple. Fails the
+		connection if encryption cannot be negotiated.
+		</para></listitem>
+		</varlistentry>
+		
+		&stdarg.client.debug;
+		&popt.common.samba;
+		&popt.common.credentials;
+		&popt.common.connection;
+		
+		<varlistentry>
+		<term>-T tar options</term>
+		<listitem><para>smbclient may be used to create <command>tar(1)
+		</command> compatible backups of all the files on an SMB/CIFS
+		share. The secondary tar flags that can be given to this option 
+		are : </para>
+		
+		<itemizedlist>
+			<listitem><para><parameter>c</parameter> - Create a tar file on UNIX. 
+			Must be followed by the name of a tar file, tape device
+			or "-" for standard output. If using standard output you must 
+			turn the log level to its lowest value -d0 to avoid corrupting 
+			your tar file. This flag is mutually exclusive with the 
+			<parameter>x</parameter> flag. </para></listitem>
+			
+			<listitem><para><parameter>x</parameter> - Extract (restore) a local 
+			tar file back to a share. Unless the -D option is given, the tar 
+			files will be restored from the top level of the share. Must be 
+			followed by the name of the tar file, device or "-" for standard 
+			input. Mutually exclusive with the <parameter>c</parameter> flag. 
+			Restored files have their creation times (mtime) set to the
+			date saved in the tar file. Directories currently do not get 
+			their creation dates restored properly. </para></listitem>
+			
+			<listitem><para><parameter>I</parameter> - Include files and directories. 
+			Is the default behavior when filenames are specified above. Causes 
+			files to be included in an extract or create (and therefore 
+			everything else to be excluded). See example below.  Filename globbing 
+			works  in one of two ways.  See <parameter>r</parameter> below. </para></listitem>
+			
+			<listitem><para><parameter>X</parameter> - Exclude files and directories. 
+			Causes files to be excluded from an extract or create. See 
+			example below.  Filename globbing works in one of two ways now. 
+			See <parameter>r</parameter> below. </para></listitem>
+			
+			<listitem><para><parameter>F</parameter> - File containing a list of files and directories.
+			The <parameter>F</parameter> causes the name following the tarfile to
+			create to be read as a filename that contains a list of files and directories to 
+			be included in an extract or create (and therefore everything else to be excluded).
+			See example below. Filename globbing works in one of two ways.
+			See <parameter>r</parameter> below.
+			</para></listitem>
+			
+			<listitem><para><parameter>b</parameter> - Blocksize. Must be followed 
+			by a valid (greater than zero) blocksize.  Causes tar file to be 
+			written out in blocksize*TBLOCK (usually 512 byte) blocks. 
+			</para></listitem>
+			
+			<listitem><para><parameter>g</parameter> - Incremental. Only back up 
+			files that have the archive bit set. Useful only with the 
+			<parameter>c</parameter> flag. </para></listitem>
+
+			<listitem><para><parameter>q</parameter> - Quiet. Keeps tar from printing 
+			diagnostics as it works.  This is the same as tarmode quiet. 
+			</para></listitem>
+			
+			<listitem><para><parameter>r</parameter> - Regular expression include
+			or exclude.  Uses regular  expression matching for 
+			excluding or excluding files if  compiled with HAVE_REGEX_H. 
+			However this mode can be very slow. If  not compiled with 
+			HAVE_REGEX_H, does a limited wildcard match on '*' and  '?'. 
+			</para></listitem>
+			
+			<listitem><para><parameter>N</parameter> - Newer than. Must be followed 
+			by the name of a file whose date is compared against files found 
+			on the share during a create. Only files newer than the file 
+			specified are backed up to the tar file. Useful only with the 
+			<parameter>c</parameter> flag. </para></listitem>
+			
+			<listitem><para><parameter>a</parameter> - Set archive bit. Causes the 
+			archive bit to be reset when a file is backed up. Useful with the 
+			<parameter>g</parameter> and <parameter>c</parameter> flags. 
+			</para></listitem>
+		</itemizedlist>
+			
+		<para><emphasis>Tar Long File Names</emphasis></para>
+			
+		<para><command>smbclient</command>'s tar option now supports long 
+		file names both on backup and restore. However, the full path 
+		name of the file must be less than 1024 bytes.  Also, when
+		a tar archive is created, <command>smbclient</command>'s tar option places all 
+		files in the archive with relative names, not absolute names. 
+		</para>
+
+		<para><emphasis>Tar Filenames</emphasis></para>
+			
+		<para>All file names can be given as DOS path names (with '\\' 
+		as the component separator) or as UNIX path names (with '/' as 
+		the component separator). </para>
+			
+		<para><emphasis>Examples</emphasis></para>
+		
+		<para>Restore from tar file <filename>backup.tar</filename> into myshare on mypc 
+		(no password on share). </para>
+		
+		<para><command>smbclient //mypc/yshare "" -N -Tx backup.tar
+		</command></para>
+		
+		<para>Restore everything except <filename>users/docs</filename>
+		</para>
+		
+		<para><command>smbclient //mypc/myshare "" -N -TXx backup.tar 
+		users/docs</command></para>
+		
+		<para>Create a tar file of the files beneath <filename>
+		users/docs</filename>. </para>
+		
+		<para><command>smbclient //mypc/myshare "" -N -Tc
+		backup.tar users/docs </command></para>
+		
+		<para>Create the same tar file as above, but now use 
+		a DOS path name. </para>
+		
+		<para><command>smbclient //mypc/myshare "" -N -tc backup.tar 
+		users\edocs </command></para>
+		
+		<para>Create a tar file of the files listed in the file <filename>tarlist</filename>.</para>
+		
+		<para><command>smbclient //mypc/myshare "" -N -TcF
+		backup.tar tarlist</command></para>
+		
+		<para>Create a tar file of all the files and directories in 
+		the share. </para>
+		
+		<para><command>smbclient //mypc/myshare "" -N -Tc backup.tar *
+		</command></para>
+		</listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-D initial directory</term>
+		<listitem><para>Change to initial directory before starting. Probably 
+		only of any use with the tar -T option. </para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-c command string</term>
+		<listitem><para>command string is a semicolon-separated list of 
+		commands to be executed instead of prompting from stdin. <parameter>
+		-N</parameter> is implied by <parameter>-c</parameter>.</para>
+
+		<para>This is particularly useful in scripts and for printing stdin 
+		to the server, e.g. <command>-c 'print -'</command>. </para></listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>OPERATIONS</title>
+
+	<para>Once the client is running, the user is presented with 
+	a prompt : </para>
+
+	<para><prompt>smb:\&gt; </prompt></para>
+
+	<para>The backslash ("\\") indicates the current working directory 
+	on the server, and will change if the current working directory 
+	is changed. </para>
+
+	<para>The prompt indicates that the client is ready and waiting to 
+	carry out a user command. Each command is a single word, optionally 
+	followed by parameters specific to that command. Command and parameters 
+	are space-delimited unless these notes specifically
+	state otherwise. All commands are case-insensitive.  Parameters to 
+	commands may or may not be case sensitive, depending on the command. 
+	</para>
+
+	<para>You can specify file names which have spaces in them by quoting 
+	the name with double quotes, for example "a long file name". </para>
+
+	<para>Parameters shown in square brackets (e.g., "[parameter]") are 
+	optional.  If not given, the command will use suitable defaults. Parameters 
+	shown in angle brackets (e.g., "&lt;parameter&gt;") are required.
+	</para>
+
+
+	<para>Note that all commands operating on the server are actually 
+	performed by issuing a request to the server. Thus the behavior may 
+	vary from server to server, depending on how the server was implemented. 
+	</para>
+
+	<para>The commands available are given here in alphabetical order. </para>
+
+	<variablelist>
+		<varlistentry>
+		<term>? [command]</term>
+		<listitem><para>If <replaceable>command</replaceable> is specified, the ? command will display
+		a brief informative message about the specified command.  If no
+		command is specified, a list of available commands will
+		be displayed. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>! [shell command]</term>
+		<listitem><para>If <replaceable>shell command</replaceable> is specified, the !
+		command will execute a shell locally and run the specified shell
+		command. If no command is specified, a local shell will be run.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>allinfo file</term>
+		<listitem><para>The client will request that the server return
+		all known information about a file or directory (including streams).
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>altname file</term>
+		<listitem><para>The client will request that the server return
+		the "alternate" name (the 8.3 name) for a file or directory.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>archive &lt;number&gt;</term>
+		<listitem><para>Sets the archive level when operating on files.
+		0 means ignore the archive bit, 1 means only operate on files with this bit set,
+		2 means only operate on files with this bit set and reset it after operation,
+		3 means operate on all files and reset it after operation. The default is 0.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>blocksize &lt;number&gt;</term>
+		<listitem><para>Sets the blocksize parameter for a tar operation. The default is 20.
+		Causes tar file to be written out in blocksize*TBLOCK (normally 512 byte) units.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>cancel jobid0 [jobid1] ... [jobidN]</term>
+		<listitem><para>The client will request that the server cancel
+		the printjobs identified by the given numeric print job ids.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>case_sensitive</term>
+		<listitem><para>Toggles the setting of the flag in SMB packets that
+		tells the server to treat filenames as case sensitive. Set to OFF by
+		default (tells file server to treat filenames as case insensitive). Only
+		currently affects Samba 3.0.5 and above file servers with the case sensitive
+		parameter set to auto in the smb.conf.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>cd &lt;directory name&gt;</term>
+		<listitem><para>If "directory name" is specified, the current
+		working directory on the server will be changed to the directory
+		specified. This operation will fail if for any reason the specified
+		directory is inaccessible. </para>
+
+		<para>If no directory name is specified, the current working
+		directory on the server will be reported. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>chmod file mode in octal</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. The client requests that the server
+		change the UNIX permissions to the given octal mode, in standard UNIX format.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>chown file uid gid</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. The client requests that the server
+		change the UNIX user and group ownership to the given decimal values. Note there is
+		currently no way to remotely look up the UNIX uid and gid values for a given name.
+		This may be addressed in future versions of the CIFS UNIX extensions.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>close &lt;fileid&gt;</term>
+		<listitem><para>Closes a file explicitly opened by the open command. Used for
+		internal Samba testing purposes.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>del &lt;mask&gt;</term>
+		<listitem><para>The client will request that the server attempt
+		to delete all files matching <replaceable>mask</replaceable> from the current working
+		directory on the server. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>dir &lt;mask&gt;</term>
+		<listitem><para>A list of the files matching <replaceable>mask</replaceable> in the current
+		working directory on the server will be retrieved from the server
+		and displayed. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>du &lt;filename&gt;</term>
+		<listitem><para>Does a directory listing and then prints out the current disk useage and free space on a share.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>echo &lt;number&gt; &lt;data&gt;</term>
+		<listitem><para>Does an SMBecho request to ping the server. Used for internal Samba testing purposes.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>exit</term>
+		<listitem><para>Terminate the connection with the server and exit
+		from the program. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>get &lt;remote file name&gt; [local file name]</term>
+		<listitem><para>Copy the file called <filename>remote file name</filename> from
+		the server to the machine running the client. If specified, name
+		the local copy <filename>local file name</filename>.  Note that all transfers in
+		<command>smbclient</command> are binary. See also the
+		lowercase command. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>getfacl &lt;filename&gt;</term>
+		<listitem><para>Requires the server support the UNIX extensions. Requests and prints
+		the POSIX ACL on a file.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>hardlink &lt;src&gt; &lt;dest&lt;</term>
+		<listitem><para>Creates a hardlink on the server using Windows CIFS semantics.
+		the POSIX ACL on a file.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>help [command]</term>
+		<listitem><para>See the ? command above. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>history</term> <listitem><para>Displays the command history.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>iosize &lt;bytes&gt;</term>
+		<listitem><para>When sending or receiving files, smbclient uses an
+		internal memory buffer by default of size 64512 bytes. This command
+		allows this size to be set to any range between 16384 (0x4000) bytes
+		and 16776960 (0xFFFF00) bytes. Larger sizes may mean more efficient
+		data transfer as smbclient will try and use the most efficient
+		read and write calls for the connected server.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>lcd [directory name]</term>
+		<listitem><para>If <replaceable>directory name</replaceable> is specified, the current
+		working directory on the local machine will be changed to
+		the directory specified. This operation will fail if for any
+		reason the specified directory is inaccessible. </para>
+
+		<para>If no directory name is specified, the name of the
+		current working directory on the local machine will be reported.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>link target linkname</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. The client requests that the server
+		create a hard link between the linkname and target files. The linkname file
+		must not exist.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>listconnect</term>
+		<listitem><para>Show the current connections held for DFS purposes.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>lock &lt;filenum&gt; &lt;r|w&gt; &lt;hex-start&gt; &lt;hex-len&gt;</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. Tries to set a POSIX
+		fcntl lock of the given type on the given range. Used for internal Samba testing purposes.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>logon &lt;username&gt; &lt;password&gt;</term>
+		<listitem><para>Establishes a new vuid for this session by logging on again.
+		Replaces the current vuid. Prints out the new vuid. Used for internal Samba testing purposes.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>lowercase</term>
+		<listitem><para>Toggle lowercasing of filenames for the get and
+		mget commands.		
+		</para>	
+
+		<para>When lowercasing is toggled ON, local filenames are converted
+		to lowercase when using the get and mget commands. This is
+		often useful when copying (say) MSDOS files from a server, because
+		lowercase filenames are the norm on UNIX systems. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>ls &lt;mask&gt;</term>
+		<listitem><para>See the dir command above. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>mask &lt;mask&gt;</term>
+		<listitem><para>This command allows the user to set up a mask
+		which will be used during recursive operation of the mget and
+		mput commands. </para>
+
+		<para>The masks specified to the mget and mput commands act as
+		filters for directories rather than files when recursion is
+		toggled ON. </para>
+
+		<para>The mask specified with the mask command is necessary
+		to filter files within those directories. For example, if the
+		mask specified in an mget command is "source*" and the mask
+		specified with the mask command is "*.c" and recursion is
+		toggled ON, the mget command will retrieve all files matching
+		"*.c" in all directories below and including all directories
+		matching "source*" in the current working directory. </para>
+
+		<para>Note that the value for mask defaults to blank (equivalent
+		to "*") and remains so until the mask command is used to change it.
+		It retains the most recently specified value indefinitely. To
+		avoid unexpected results it would be wise to change the value of
+		mask back to "*" after using the mget or mput commands. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>md &lt;directory name&gt;</term>
+		<listitem><para>See the mkdir command. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>mget &lt;mask&gt;</term>
+		<listitem><para>Copy all files matching <replaceable>mask</replaceable> from the server to
+		the machine running the client. </para>
+
+		<para>Note that <replaceable>mask</replaceable> is interpreted differently during recursive
+		operation and non-recursive operation - refer to the recurse and
+		mask commands for more information. Note that all transfers in
+		<command>smbclient</command> are binary. See also the lowercase command. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>mkdir &lt;directory name&gt;</term>
+		<listitem><para>Create a new directory on the server (user access
+		privileges permitting) with the specified name. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>more &lt;file name&gt;</term>
+		<listitem><para>Fetch a remote file and view it with the contents
+		of your PAGER environment variable.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>mput &lt;mask&gt;</term>
+		<listitem><para>Copy all files matching <replaceable>mask</replaceable> in the current working
+		directory on the local machine to the current working directory on
+		the server. </para>
+
+		<para>Note that <replaceable>mask</replaceable> is interpreted differently during recursive
+		operation and non-recursive operation - refer to the recurse and mask
+		commands for more information. Note that all transfers in <command>smbclient</command>
+		are binary. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>posix</term>
+		<listitem><para>Query the remote server to see if it supports the CIFS UNIX
+		extensions and prints out the list of capabilities supported. If so, turn
+		on POSIX pathname processing and large file read/writes (if available),.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>posix_encrypt &lt;domain&gt; &lt;username&gt; &lt;password&gt;</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. Attempt to negotiate
+		SMB encryption on this connection. If smbclient connected with kerberos
+		credentials (-k) the arguments to this command are ignored and the kerberos
+		credentials are used to negotiate GSSAPI signing and sealing instead. See
+		also the -e option to smbclient to force encryption on initial connection.
+		This command is new with Samba 3.2.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>posix_open &lt;filename&gt; &lt;octal mode&gt;</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. Opens a remote file
+		using the CIFS UNIX extensions and prints a fileid. Used for internal Samba
+		testing purposes.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>posix_mkdir &lt;directoryname&gt; &lt;octal mode&gt;</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. Creates a remote directory
+		using the CIFS UNIX extensions with the given mode.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>posix_rmdir &lt;directoryname&gt;</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. Deletes a remote directory
+		using the CIFS UNIX extensions.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>posix_unlink &lt;filename&gt;</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. Deletes a remote file
+		using the CIFS UNIX extensions.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>print &lt;file name&gt;</term>
+		<listitem><para>Print the specified file from the local machine
+		through a printable service on the server. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>prompt</term>
+		<listitem><para>Toggle prompting for filenames during operation
+		of the mget and mput commands. </para>
+
+		<para>When toggled ON, the user will be prompted to confirm
+		the transfer of each file during these commands. When toggled
+		OFF, all specified files will be transferred without prompting.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>put &lt;local file name&gt; [remote file name]</term>
+		<listitem><para>Copy the file called <filename>local file name</filename> from the
+		machine running the client to the server. If specified,
+		name the remote copy <filename>remote file name</filename>. Note that all transfers
+		in <command>smbclient</command> are binary. See also the lowercase command.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>queue</term>
+		<listitem><para>Displays the print queue, showing the job id,
+		name, size and current status. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>quit</term>
+		<listitem><para>See the exit command. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>rd &lt;directory name&gt;</term>
+		<listitem><para>See the rmdir command. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recurse</term>
+		<listitem><para>Toggle directory recursion for the commands mget
+		and mput. </para>
+
+		<para>When toggled ON, these commands will process all directories
+		in the source directory (i.e., the directory they are copying
+		from ) and will recurse into any that match the mask specified
+		to the command. Only files that match the mask specified using
+		the mask command will be retrieved. See also the mask command.
+		</para>
+
+		<para>When recursion is toggled OFF, only files from the current
+		working directory on the source machine that match the mask specified
+		to the mget or mput commands will be copied, and any mask specified
+		using the mask command will be ignored. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>rm &lt;mask&gt;</term>
+		<listitem><para>Remove all files matching <replaceable>mask</replaceable> from the current
+		working directory on the server. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>rmdir &lt;directory name&gt;</term>
+ 		<listitem><para>Remove the specified directory (user access
+		privileges permitting) from the server. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>setmode &lt;filename&gt; &lt;perm=[+|\-]rsha&gt;</term>
+		<listitem><para>A version of the DOS attrib command to set
+		file permissions. For example: </para>
+
+		<para><command>setmode myfile +r </command></para>
+
+		<para>would make myfile read only. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>showconnect</term>
+		<listitem><para>Show the currently active connection held for DFS purposes.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>stat file</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. The client requests the
+		UNIX basic info level and prints out the same info that the Linux stat command
+		would about the file. This includes the size, blocks used on disk, file type,
+		permissions, inode number, number of links and finally the three timestamps
+		(access, modify and change). If the file is a special file (symlink, character or
+		block device, fifo or socket) then extra information may also be printed.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>symlink target linkname</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. The client requests that the server
+		create a symbolic hard link between the target and linkname files. The linkname file
+		must not exist. Note that the server will not create a link to any path that lies
+		outside the currently connected share. This is enforced by the Samba server.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>tar &lt;c|x&gt;[IXbgNa]</term>
+		<listitem><para>Performs a tar operation - see the <parameter>-T
+		</parameter> command line option above. Behavior may be affected
+		by the tarmode command (see below). Using g (incremental) and N
+		(newer) will affect tarmode settings. Note that using the "-" option
+		with tar x may not work - use the command line option instead.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>blocksize &lt;blocksize&gt;</term>
+		<listitem><para>Blocksize. Must be followed by a valid (greater
+		than zero) blocksize. Causes tar file to be written out in
+		<replaceable>blocksize</replaceable>*TBLOCK (usually 512 byte) blocks. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>tarmode &lt;full|inc|reset|noreset&gt;</term>
+		<listitem><para>Changes tar's behavior with regard to archive
+		bits. In full mode, tar will back up everything regardless of the
+		archive bit setting (this is the default mode). In incremental mode,
+		tar will only back up files with the archive bit set. In reset mode,
+		tar will reset the archive bit on all files it backs up (implies
+		read/write share). </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>unlock &lt;filenum&gt; &lt;hex-start&gt; &lt;hex-len&gt;</term>
+		<listitem><para>This command depends on the server supporting the CIFS
+		UNIX extensions and will fail if the server does not. Tries to unlock a POSIX
+		fcntl lock on the given range. Used for internal Samba testing purposes.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>volume</term>
+		<listitem><para>Prints the current volume name of the share.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>vuid &lt;number&gt;</term>
+		<listitem><para>Changes the currently used vuid in the protocol to
+		the given arbitrary number. Without an argument prints out the current
+		vuid being used. Used for internal Samba testing purposes.
+		</para></listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>NOTES</title>
+
+	<para>Some servers are fussy about the case of supplied usernames,
+	passwords, share names (AKA service names) and machine names.
+	If you fail to connect try giving all parameters in uppercase.
+	</para>
+
+	<para>It is often necessary to use the -n option when connecting
+	to some types of servers. For example OS/2 LanManager insists
+	on a valid NetBIOS name being used, so you need to supply a valid
+	name that would be known to the server.</para>
+
+	<para>smbclient supports long file names where the server 
+	supports the LANMAN2 protocol or above. </para>
+</refsect1>
+
+<refsect1>
+	<title>ENVIRONMENT VARIABLES</title>
+
+	<para>The variable <envar>USER</envar> may contain the 
+	username of the person  using the client. This information is 
+	used only if the protocol  level is high enough to support 
+	session-level passwords.</para>
+
+
+	<para>The variable <envar>PASSWD</envar> may contain 
+	the password of the person using the client.  This information is 
+	used only if the protocol level is high enough to support 
+	session-level passwords. </para>
+
+	<para>The variable <envar>LIBSMB_PROG</envar> may contain 
+	the path, executed with system(), which the client should connect 
+        to instead of connecting to a server.  This functionality is primarily
+        intended as a development aid, and works best when using a LMHOSTS 
+        file</para>
+</refsect1>
+
+
+<refsect1>
+	<title>INSTALLATION</title>
+
+	<para>The location of the client program is a matter for 
+	individual system administrators. The following are thus
+	suggestions only. </para>
+
+	<para>It is recommended that the smbclient software be installed
+	in the <filename>/usr/local/samba/bin/</filename> or <filename>
+	/usr/samba/bin/</filename> directory, this directory readable 
+	by all, writeable only by root. The client program itself should 
+	be executable by all. The client should <emphasis>NOT</emphasis> be 
+	setuid or setgid! </para>
+
+	<para>The client log files should be put in a directory readable 
+	and writeable only by the user. </para>
+
+	<para>To test the client, you will need to know the name of a 
+	running SMB/CIFS server. It is possible to run <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> as an ordinary user - running that server as a daemon 
+	on a user-accessible port (typically any port number over 1024)
+	would provide a suitable test server. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>DIAGNOSTICS</title>
+
+	<para>Most diagnostics issued by the client are logged in a 
+	specified log file. The log file name is specified at compile time, 
+	but may be overridden on the command line. </para>
+
+	<para>The number and nature of diagnostics available depends 
+	on the debug level used by the client. If you have problems, 
+	set the debug level to 3 and peruse the log files. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.2 of the Samba suite.</para>
+</refsect1>
+
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
+	was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbcontrol.1.xml b/docs-xml/manpages-3/smbcontrol.1.xml
new file mode 100644
index 00000000000..4dcf8d31c62
--- /dev/null
+++ b/docs-xml/manpages-3/smbcontrol.1.xml
@@ -0,0 +1,297 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbcontrol.1">
+
+<refmeta>
+	<refentrytitle>smbcontrol</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbcontrol</refname>
+	<refpurpose>send messages to smbd, nmbd or winbindd processes</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbcontrol</command>
+		<arg>-i</arg>
+		<arg>-s</arg>
+	</cmdsynopsis>
+	
+	<cmdsynopsis>
+		<command>smbcontrol</command>
+		<arg>destination</arg>
+		<arg>message-type</arg>
+		<arg>parameter</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>smbcontrol</command> is a very small program, which 
+	sends messages to a <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, a <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, or a <citerefentry><refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> daemon running on the system.</para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		&stdarg.help;
+		&stdarg.configfile;
+		<varlistentry>
+		<term>-i</term>
+		<listitem><para>Run interactively. Individual commands 
+		of the form destination message-type parameters can be entered 
+		on STDIN. An empty command line or a "q" will quit the 
+		program.</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>destination</term>
+		<listitem><para>One of <parameter>nmbd</parameter>, <parameter>smbd</parameter> or a process ID.</para>
+
+		<para>The <parameter>smbd</parameter> destination causes the 
+		message to "broadcast" to all smbd daemons.</para>
+
+		<para>The <parameter>nmbd</parameter> destination causes the 
+		message to be sent to the nmbd daemon specified in the 
+		<filename>nmbd.pid</filename> file.</para>
+
+		<para>If a single process ID is given, the message is sent 
+		to only that process.</para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>message-type</term>
+		<listitem><para>Type of message to send. See 
+		the section <constant>MESSAGE-TYPES</constant> for details.
+		</para></listitem></varlistentry>
+		
+
+	
+		<varlistentry>
+		<term>parameters</term>
+		<listitem><para>any parameters required for the message-type</para>
+		</listitem>
+		</varlistentry>
+	</variablelist>
+	
+</refsect1>
+
+<refsect1>
+	<title>MESSAGE-TYPES</title>
+
+	<para>Available message types are:</para>
+
+	<variablelist>
+	<varlistentry><term>close-share</term>
+	<listitem><para>Order smbd to close the client 
+	connections to the named share. Note that this doesn't affect client 
+	connections to any other shares. This message-type takes an argument of the
+	share name for which client connections will be closed, or the
+	"*" character which will close all currently open shares.
+	This may be useful if you made changes to the access controls on the share.
+	This message can only be sent to <constant>smbd</constant>.</para>
+	</listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>debug</term>
+	<listitem><para>Set debug level to the value specified by the 
+	parameter. This can be sent to any of the destinations.</para>
+	</listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>force-election</term>
+	<listitem><para>This message causes the <command>nmbd</command> daemon to 
+	force a new browse master election. </para>
+	</listitem></varlistentry>
+
+	<varlistentry>
+	<term>ping</term>
+	<listitem><para>
+	Send specified number of "ping" messages and 
+	wait for the same number of  reply "pong" messages. This can be sent to 
+	any of the destinations.</para>
+	</listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>profile</term>
+	<listitem><para>Change profile settings of a daemon, based on the 
+	parameter. The parameter can be "on" to turn on profile stats 
+	collection, "off" to turn off profile stats collection, "count"
+	to enable only collection of count stats (time stats are 
+	disabled), and "flush" to zero the current profile stats. This can 
+	be sent to any smbd or nmbd destinations.</para>
+	</listitem></varlistentry>
+
+	<varlistentry>
+	<term>debuglevel</term>
+	<listitem><para>
+	Request debuglevel of a certain daemon and write it to stdout. This 
+	can be sent to any of the destinations.</para>
+	</listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>profilelevel</term>
+	<listitem><para>
+	Request profilelevel of a certain daemon and write it to stdout. 
+	This can be sent to any smbd or nmbd destinations.</para>
+	</listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>printnotify</term>
+	<listitem><para>
+	Order smbd to send a printer notify message to any Windows NT clients 
+	connected to a printer. This message-type takes the following arguments:
+	</para>
+	
+	<variablelist>
+
+	    <varlistentry>
+	    <term>queuepause printername</term>
+	    <listitem><para>Send a queue pause change notify
+	    message to the printer specified.</para></listitem>
+ 	    </varlistentry>
+
+	    <varlistentry>
+	    <term>queueresume printername</term>
+	    <listitem><para>Send a queue resume change notify
+	    message for the printer specified.</para></listitem>
+ 	    </varlistentry>
+
+		<varlistentry>
+	    <term>jobpause printername unixjobid</term>
+	    <listitem><para>Send a job pause change notify
+	    message for the printer and unix jobid
+	    specified.</para></listitem> 
+ 	    </varlistentry>
+
+	    <varlistentry>
+	    <term>jobresume printername unixjobid</term>
+	    <listitem><para>Send a job resume change notify
+	    message for the printer and unix jobid
+	    specified.</para></listitem>  
+	    </varlistentry>
+
+	    <varlistentry>
+	    <term>jobdelete printername unixjobid</term>
+	    <listitem><para>Send a job delete change notify
+	    message for the printer and unix jobid
+	    specified.</para></listitem> 
+	    </varlistentry>
+	</variablelist>
+
+	<para>
+	Note that this message only sends notification that an
+	event has occured.  It doesn't actually cause the
+	event to happen.
+	</para>
+
+	<para>This message can only be sent to <constant>smbd</constant>. </para>
+	</listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>samsync</term>
+	<listitem><para>Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to <constant>smbd</constant>. </para>
+	<note><para>Not working at the moment</para></note>
+	</listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>samrepl</term>
+	<listitem><para>Send sam replication message, with specified serial. Can only be sent to <constant>smbd</constant>. Should not be used manually.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>dmalloc-mark</term>
+	<listitem><para>Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>dmalloc-log-changed</term>
+	<listitem><para>
+	Dump the pointers that have changed since the mark set by dmalloc-mark. 
+	Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>shutdown</term>
+	<listitem><para>Shut down specified daemon. Can be sent to both smbd and nmbd.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>pool-usage</term>
+	<listitem><para>Print a human-readable description of all 
+	talloc(pool) memory usage by the specified daemon/process. Available 
+	for both smbd and nmbd.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>drvupgrade</term>
+	<listitem><para>Force clients of printers using specified driver 
+	to update their local version of the driver. Can only be 
+	sent to smbd.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+	<term>reload-config</term>
+	<listitem><para>Force daemon to reload smb.conf configuration file. Can be sent
+	to <constant>smbd</constant>, <constant>nmbd</constant>, or <constant>winbindd</constant>.
+	</para></listitem>
+	</varlistentry>
+
+</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
+	Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbcquotas.1.xml b/docs-xml/manpages-3/smbcquotas.1.xml
new file mode 100644
index 00000000000..09916751e1d
--- /dev/null
+++ b/docs-xml/manpages-3/smbcquotas.1.xml
@@ -0,0 +1,183 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbcquotas.1">
+
+<refmeta>
+	<refentrytitle>smbcquotas</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbcquotas</refname>
+	<refpurpose>Set or get QUOTAs of NTFS 5 shares</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbcquotas</command>
+		<arg choice="req">//server/share</arg>
+		<arg choice="opt">-u user</arg>
+		<arg choice="opt">-L</arg>
+		<arg choice="opt">-F</arg>
+		<arg choice="opt">-S QUOTA_SET_COMMAND</arg>
+		<arg choice="opt">-n</arg>
+		<arg choice="opt">-t</arg>
+		<arg choice="opt">-v</arg>
+
+		<arg choice="opt">-d debuglevel</arg>
+		<arg choice="opt">-s configfile</arg>
+		<arg choice="opt">-l logdir</arg>
+		<arg choice="opt">-V</arg>
+
+		<arg choice="opt">-U username</arg>
+		<arg choice="opt">-N</arg>
+		<arg choice="opt">-k</arg>
+		<arg choice="opt">-A</arg>
+
+
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>smbcquotas</command> program manipulates NT Quotas on SMB file shares. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<para>The following options are available to the <command>smbcquotas</command> program. </para>
+
+
+	<variablelist>
+		<varlistentry>
+		<term>-u user</term>
+		<listitem><para> Specifies the user of whom the quotas are get or set.
+		By default the current user's username will be used.</para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-L</term>
+		<listitem><para>Lists all quota records of the share.</para></listitem>
+		</varlistentry>
+
+		
+		
+		<varlistentry>
+		<term>-F</term>
+		<listitem><para>Show the share quota status and default limits.</para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-S QUOTA_SET_COMMAND</term>
+		<listitem><para>This command sets/modifies quotas for a user or on the share,
+		depending on the QUOTA_SET_COMMAND parameter which is described later.</para></listitem>
+		</varlistentry>
+
+		
+		<varlistentry>
+		<term>-n</term>
+		<listitem><para>This option displays all QUOTA information in numeric 
+		format.  The default is to convert SIDs to names and QUOTA limits 
+		to a readable string format.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-t</term>
+		<listitem><para>
+		Don't actually do anything, only validate the correctness of the arguments.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-v</term>
+		<listitem><para>
+		Be verbose.
+		</para></listitem>
+		</varlistentry>
+				
+		&stdarg.help;
+		&stdarg.server.debug;
+		&popt.common.samba;
+		&popt.common.credentials;
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>QUOTA_SET_COMAND</title>
+
+	<para>The format of an the QUOTA_SET_COMMAND is an operation
+	name followed by a set of parameters specific to that operation.
+	</para>
+
+	<para>To set user quotas for the user specified by -u or for the
+	current username: </para>
+
+	<para><userinput>
+	UQLIM:&lt;username&gt;:&lt;softlimit&gt;/&lt;hardlimit&gt;
+	</userinput></para>
+
+	<para>To set the default quotas for a share:
+	</para>
+
+	<para><userinput>
+	FSQLIM:&lt;softlimit&gt;/&lt;hardlimit&gt;
+	</userinput></para>
+
+	<para>
+	To change the share quota settings:
+	</para>
+
+	<para><userinput>
+	FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT
+	</userinput></para>
+
+	<para>All limits are specified as a number of bytes.</para>
+</refsect1>
+
+<refsect1>
+	<title>EXIT STATUS</title>
+
+	<para>The <command>smbcquotas</command> program sets the exit status
+	depending on the success or otherwise of the operations performed.
+	The exit status may be one of the following values. </para>
+
+	<para>If the operation succeeded, smbcquotas returns an exit
+	status of 0.  If <command>smbcquotas</command> couldn't connect to the specified server,
+	or when there was an error getting or setting the quota(s), an exit status
+	of 1 is returned.  If there was an error parsing any command line
+	arguments, an exit status of 2 is returned. </para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+	<para><command>smbcquotas</command> was written by Stefan Metzmacher.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbd.8.xml b/docs-xml/manpages-3/smbd.8.xml
new file mode 100644
index 00000000000..a82d91015b4
--- /dev/null
+++ b/docs-xml/manpages-3/smbd.8.xml
@@ -0,0 +1,445 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbd.8">
+
+<refmeta>
+	<refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbd</refname>
+	<refpurpose>server to provide SMB/CIFS services to clients</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbd</command>
+		<arg choice="opt">-D</arg>
+		<arg choice="opt">-F</arg>
+		<arg choice="opt">-S</arg>
+		<arg choice="opt">-i</arg>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-V</arg>
+		<arg choice="opt">-b</arg>
+		<arg choice="opt">-d &lt;debug level&gt;</arg>
+		<arg choice="opt">-l &lt;log directory&gt;</arg>
+		<arg choice="opt">-p &lt;port number(s)&gt;</arg>
+		<arg choice="opt">-P &lt;profiling level&gt;</arg>
+		<arg choice="opt">-O &lt;socket option&gt;</arg>
+		<arg choice="opt">-s &lt;configuration file&gt;</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+	<para>This program is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>smbd</command> is the server daemon that 
+	provides filesharing and printing services to Windows clients. 
+	The server provides filespace and printer services to
+	clients using the SMB (or CIFS) protocol. This is compatible 
+	with the LanManager protocol, and can service LanManager 
+	clients.  These include MSCLIENT 3.0 for DOS, Windows for 
+	Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, 
+	OS/2, DAVE for Macintosh, and smbfs for Linux.</para>
+
+	<para>An extensive description of the services that the 
+	server can provide is given in the man page for the 
+	configuration file controlling the attributes of those 
+	services (see <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>.  This man page will not describe the 
+	services, but will concentrate on the administrative aspects 
+	of running the server.</para>
+
+	<para>Please note that there are significant security 
+	implications to running this server, and the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> manual page should be regarded as mandatory reading before 
+	proceeding with installation.</para>
+
+	<para>A session is created whenever a client requests one. 
+	Each client gets a copy of the server for each session. This 
+	copy then services all connections made by the client during 
+	that session. When all connections from its client are closed, 
+	the copy of the server for that client terminates.</para>
+
+	<para>The configuration file, and any files that it includes, 
+	are automatically reloaded every minute, if they change.  You 
+	can force a reload by sending a SIGHUP to the server.  Reloading 
+	the configuration file will not affect connections to any service 
+	that is already established.  Either the user will have to 
+	disconnect from the service, or <command>smbd</command> killed and restarted.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-D</term>
+		<listitem><para>If specified, this parameter causes 
+		the server to operate as a daemon. That is, it detaches 
+		itself and runs in the background, fielding requests 
+		on the appropriate port. Operating the server as a
+		daemon is the recommended way of running <command>smbd</command> for 
+		servers that provide more than casual use file and 
+		print services.  This switch is assumed if <command>smbd
+		</command> is executed on the command line of a shell.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-F</term>
+		<listitem><para>If specified, this parameter causes
+		the main <command>smbd</command> process to not daemonize,
+		i.e. double-fork and disassociate with the terminal.
+		Child processes are still created as normal to service
+		each connection request, but the main process does not
+		exit. This operation mode is suitable for running
+		<command>smbd</command> under process supervisors such
+		as <command>supervise</command> and <command>svscan</command>
+		from Daniel J. Bernstein's <command>daemontools</command>
+		package, or the AIX process monitor.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-S</term>
+		<listitem><para>If specified, this parameter causes
+		<command>smbd</command> to log to standard output rather
+		than a file.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-i</term>
+		<listitem><para>If this parameter is specified it causes the
+		server to run "interactively", not as a daemon, even if the
+		server is executed on the command line of a shell. Setting this
+		parameter negates the implicit deamon mode when run from the
+		command line. <command>smbd</command> also logs to standard
+		output, as if the <command>-S</command> parameter had been
+		given.
+		</para></listitem>
+		</varlistentry>
+		
+		&stdarg.server.debug;
+		&popt.common.samba;
+		&stdarg.help;
+
+		<varlistentry>
+		<term>-b</term>
+		<listitem><para>Prints information about how 
+		Samba was built.</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-p|--port&lt;port number(s)&gt;</term>
+		<listitem><para><replaceable>port number(s)</replaceable> is a 
+		space or comma-separated list of TCP ports smbd should listen on.
+		The default value is taken from the <smbconfoption name="ports"/> parameter in &smb.conf;</para>
+
+		<para>The default ports are 139 (used for SMB over NetBIOS over TCP)
+			and port 445 (used for plain SMB over TCP).
+		</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>-P|--profiling-level&lt;profiling level&gt;</term>
+		<listitem><para><replaceable>profiling level</replaceable> is a
+		number specifying the level of profiling data to be collected.
+		0 turns off profiling, 1 turns on counter profiling only,
+		2 turns on complete profiling, and 3 resets all profiling data.
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>FILES</title>
+
+	<variablelist>
+		<varlistentry>
+		<term><filename>/etc/inetd.conf</filename></term>
+		<listitem><para>If the server is to be run by the 
+		<command>inetd</command> meta-daemon, this file 
+		must contain suitable startup information for the 
+		meta-daemon. 
+		</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term><filename>/etc/rc</filename></term>
+		<listitem><para>or whatever initialization script your 
+		system uses).</para>
+
+		<para>If running the server as a daemon at startup, 
+		this file will need to contain an appropriate startup 
+		sequence for the server. </para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term><filename>/etc/services</filename></term>
+		<listitem><para>If running the server via the 
+		meta-daemon <command>inetd</command>, this file 
+		must contain a mapping of service name (e.g., netbios-ssn) 
+		to service port (e.g., 139) and protocol type (e.g., tcp). 
+		</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term><filename>/usr/local/samba/lib/smb.conf</filename></term>
+		<listitem><para>This is the default location of the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> server configuration file. Other common places that systems 
+		install this file are <filename>/usr/samba/lib/smb.conf</filename> 
+		and <filename>/etc/samba/smb.conf</filename>.</para>
+		
+		<para>This file describes all the services the server 
+		is to make available to clients. See <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> for more information.</para>
+		</listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>LIMITATIONS</title>
+	<para>On some systems <command>smbd</command> cannot change uid back 
+	to root after a setuid() call.  Such systems are called 
+	trapdoor uid systems. If you have such a system, 
+	you will be unable to connect from a client (such as a PC) as 
+	two different users at once. Attempts to connect the
+	second user will result in access denied or 
+	similar.</para>
+</refsect1>
+
+<refsect1>
+	<title>ENVIRONMENT VARIABLES</title>
+
+	<variablelist>
+		<varlistentry>
+		<term><envar>PRINTER</envar></term>
+		<listitem><para>If no printer name is specified to 
+		printable services, most systems will use the value of 
+		this variable (or <constant>lp</constant> if this variable is 
+		not defined) as the name of the printer to use. This 
+		is not specific to the server, however.</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+        <title>PAM INTERACTION</title>
+	<para>Samba uses PAM for authentication (when presented with a plaintext 
+	password), for account checking (is this account disabled?) and for
+	session management.  The degree too which samba supports PAM is restricted
+	by the limitations of the SMB protocol and the <smbconfoption name="obey pam restrictions"/> <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> paramater.  When this is set, the following restrictions apply:
+	</para>
+
+	<itemizedlist>
+	<listitem><para><emphasis>Account Validation</emphasis>:  All accesses to a 
+	samba server are checked 
+	against PAM to see if the account is vaild, not disabled and is permitted to 
+	login at this time.  This also applies to encrypted logins.
+	</para></listitem>
+
+	<listitem><para><emphasis>Session Management</emphasis>:  When not using share 
+	level secuirty, users must pass PAM's session checks before access 
+	is granted.  Note however, that this is bypassed in share level secuirty.  
+	Note also that some older pam configuration files may need a line 
+	added for session support. 
+	</para></listitem>
+	</itemizedlist>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>DIAGNOSTICS</title>
+
+	<para>Most diagnostics issued by the server are logged 
+	in a specified log file. The log file name is specified 
+	at compile time, but may be overridden on the command line.</para>
+
+	<para>The number and nature of diagnostics available depends 
+	on the debug level used by the server. If you have problems, set 
+	the debug level to 3 and peruse the log files.</para>
+
+	<para>Most messages are reasonably self-explanatory. Unfortunately, 
+	at the time this man page was created, there are too many diagnostics 
+	available in the source code to warrant describing each and every 
+	diagnostic. At this stage your best bet is still to grep the 
+	source code and inspect the conditions that gave rise to the 
+	diagnostics you are seeing.</para>
+</refsect1>
+
+<refsect1>
+	<title>TDB FILES</title>
+
+	<para>Samba stores it's data in several TDB (Trivial Database) files, usually located in <filename>/var/lib/samba</filename>.</para>
+	
+	<para>
+	(*) information persistent across restarts (but not
+	necessarily important to backup).
+	</para>
+
+<variablelist>
+<varlistentry><term>account_policy.tdb*</term>
+<listitem>
+<para>NT account policy settings such as pw expiration, etc...</para>
+</listitem>
+</varlistentry>
+
+<varlistentry><term>brlock.tdb</term>
+<listitem><para>byte range locks</para></listitem>
+</varlistentry>
+
+<varlistentry><term>browse.dat</term>
+<listitem><para>browse lists</para></listitem>
+</varlistentry>
+
+<varlistentry><term>connections.tdb</term>
+<listitem><para>share connections (used to enforce max connections, etc...)</para></listitem>
+</varlistentry>
+
+<varlistentry><term>gencache.tdb</term>
+<listitem><para>generic caching db</para></listitem>
+</varlistentry>
+
+<varlistentry><term>group_mapping.tdb*</term>
+<listitem><para>group mapping information</para></listitem>
+</varlistentry>
+
+<varlistentry><term>locking.tdb</term>
+<listitem><para>share modes &amp; oplocks</para></listitem>
+</varlistentry>
+
+<varlistentry><term>login_cache.tdb*</term>
+<listitem><para>bad pw attempts</para></listitem>
+</varlistentry>
+
+<varlistentry><term>messages.tdb</term>
+<listitem><para>Samba messaging system</para></listitem>
+</varlistentry>
+
+<varlistentry><term>netsamlogon_cache.tdb*</term>
+<listitem><para>cache of user net_info_3 struct	from net_samlogon() request (as a domain member)</para></listitem>
+</varlistentry>
+
+<varlistentry><term>ntdrivers.tdb*</term>
+<listitem><para>installed printer drivers</para></listitem>
+</varlistentry>
+
+<varlistentry><term>ntforms.tdb*</term>
+<listitem><para>installed printer forms</para></listitem>
+</varlistentry>
+
+<varlistentry><term>ntprinters.tdb*</term>
+<listitem><para>installed printer information</para></listitem>
+</varlistentry>
+
+<varlistentry><term>printing/</term>
+<listitem><para>directory containing tdb per print queue of cached lpq output</para></listitem>
+</varlistentry>
+
+<varlistentry><term>registry.tdb</term>
+<listitem><para>Windows registry skeleton (connect via regedit.exe)</para></listitem>
+</varlistentry>
+
+<varlistentry><term>sessionid.tdb</term>
+<listitem><para>session information (e.g. support for 'utmp = yes')</para></listitem>
+</varlistentry>
+
+<varlistentry><term>share_info.tdb*</term>
+<listitem><para>share acls</para></listitem>
+</varlistentry>
+
+<varlistentry><term>winbindd_cache.tdb</term>
+<listitem><para>winbindd's cache of user lists, etc...</para></listitem>
+</varlistentry>
+
+<varlistentry><term>winbindd_idmap.tdb*</term>
+<listitem><para>winbindd's local idmap db</para></listitem>
+</varlistentry>
+
+<varlistentry><term>wins.dat*</term>
+<listitem><para>wins database when 'wins support = yes'</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</refsect1>
+
+<refsect1>
+	<title>SIGNALS</title>
+
+	<para>Sending the <command>smbd</command> a SIGHUP will cause it to 
+	reload its <filename>smb.conf</filename> configuration 
+	file within a short period of time.</para>
+
+	<para>To shut down a user's <command>smbd</command> process it is recommended 
+	that <command>SIGKILL (-9)</command> <emphasis>NOT</emphasis> 
+	be used, except as a last resort, as this may leave the shared
+	memory area in an inconsistent state. The safe way to terminate 
+	an <command>smbd</command> is to send it a SIGTERM (-15) signal and wait for 
+	it to die on its own.</para>
+
+	<para>The debug log level of <command>smbd</command> may be raised
+	or lowered using <citerefentry><refentrytitle>smbcontrol</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> program (SIGUSR[1|2] signals are no longer 
+	used since Samba 2.2). This is to allow transient problems to be diagnosed, 
+	whilst still running at a normally low log level.</para>
+
+	<para>Note that as the signal handlers send a debug write, 
+	they are not re-entrant in <command>smbd</command>. This you should wait until 
+	<command>smbd</command> is in a state of waiting for an incoming SMB before 
+	issuing them. It is possible to make the signal handlers safe 
+	by un-blocking the signals before the select call and re-blocking 
+	them after, however this would affect performance.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>hosts_access</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>inetd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testparm</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testprns</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, and the 
+	Internet RFC's	<filename>rfc1001.txt</filename>, <filename>rfc1002.txt</filename>. 
+	In addition the CIFS (formerly SMB) specification is available 
+	as a link from the Web page <ulink noescape="1" url="http://samba.org/cifs/"> 
+	http://samba.org/cifs/</ulink>.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
+	Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbget.1.xml b/docs-xml/manpages-3/smbget.1.xml
new file mode 100644
index 00000000000..756ccb94b80
--- /dev/null
+++ b/docs-xml/manpages-3/smbget.1.xml
@@ -0,0 +1,211 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbget.1">
+
+<refmeta>
+	<refentrytitle>smbget</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbget</refname>
+	<refpurpose>wget-like utility for download files over SMB</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbget</command>
+		<arg choice="opt">-a, --guest</arg>
+		<arg choice="opt">-r, --resume</arg>
+		<arg choice="opt">-R, --recursive</arg>
+		<arg choice="opt">-u, --username=STRING</arg>
+		<arg choice="opt">-p, --password=STRING</arg>
+		<arg choice="opt">-w, --workgroup=STRING</arg>
+		<arg choice="opt">-n, --nonprompt</arg>
+		<arg choice="opt">-d, --debuglevel=INT</arg>
+		<arg choice="opt">-D, --dots</arg>
+		<arg choice="opt">-P, --keep-permissions</arg>
+		<arg choice="opt">-o, --outputfile</arg>
+		<arg choice="opt">-f, --rcfile</arg>
+		<arg choice="opt">-q, --quiet</arg>
+		<arg choice="opt">-v, --verbose</arg>
+		<arg choice="opt">-b, --blocksize</arg>
+		<arg choice="opt">-?, --help</arg>
+		<arg choice="opt">--usage</arg>
+		<arg choice="req">smb://host/share/path/to/file</arg>
+		<arg choice="opt">smb://url2/</arg>
+		<arg choice="opt">...</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>smbget is a simple utility with wget-like semantics, that can download files from SMB servers. You can specify the files you would like to download on the command-line. 
+	</para>
+
+	<para>
+		The files should be in the smb-URL standard, e.g. use smb://host/share/file
+		for the UNC path <emphasis>\\\\HOST\\SHARE\\file</emphasis>.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<varlistentry>
+		<term>-a, --guest</term>
+		<listitem><para>Work as user guest</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-r, --resume</term>
+		<listitem><para>Automatically resume aborted files</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-R, --recursive</term>
+		<listitem><para>Recursively download files</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-u, --username=STRING</term>
+		<listitem><para>Username to use</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-p, --password=STRING</term>
+		<listitem><para>Password to use</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-w, --workgroup=STRING</term>
+		<listitem><para>Workgroup to use (optional)</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-n, --nonprompt</term>
+		<listitem><para>Don't ask anything (non-interactive)</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-d, --debuglevel=INT</term>
+		<listitem><para>Debuglevel to use</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-D, --dots</term>
+		<listitem><para>Show dots as progress indication</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-P, --keep-permissions</term>
+		<listitem><para>Set same permissions on local file as are set on remote file.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-o, --outputfile</term>
+		<listitem><para>Write the file that is being download to the specified file. Can not be used together with -R.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-f, --rcfile</term>
+		<listitem><para>Use specified rcfile. This will be loaded in the order it was specified - e.g. if you specify any options before this one, they might get overriden by the contents of the rcfile.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-q, --quiet</term>
+		<listitem><para>Be quiet</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-v, --verbose</term>
+		<listitem><para>Be verbose</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-b, --blocksize</term>
+		<listitem><para>Number of bytes to download in a block. Defaults to 64000.</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>-?, --help</term>
+		<listitem><para>Show help message</para></listitem>
+	</varlistentry>
+
+	<varlistentry>
+		<term>--usage</term>
+		<listitem><para>Display brief usage message</para></listitem>
+	</varlistentry>
+</refsect1>
+
+<refsect1>
+	<title>SMB URLS</title>
+
+	<para> SMB URL's should be specified in the following format:</para>
+
+	<para><programlisting>
+smb://[[[domain;]user[:password@]]server[/share[/path[/file]]]]
+</programlisting></para>
+
+<para><programlisting>
+smb:// means all the workgroups
+</programlisting></para>
+
+<para><programlisting>
+smb://name/ means, if <replaceable>name</replaceable> is a workgroup, all the servers in this workgroup, or if <replaceable>name</replaceable> is a server, all the shares on this server.
+</programlisting></para>
+
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+	
+<programlisting>
+# Recursively download 'src' directory
+smbget -R smb://rhonwyn/jelmer/src
+# Download FreeBSD ISO and enable resuming
+smbget -r smb://rhonwyn/isos/FreeBSD5.1.iso
+# Recursively download all ISOs
+smbget -Rr smb://rhonwyn/isos
+# Backup my data on rhonwyn
+smbget -Rr smb://rhonwyn/
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>BUGS</title>
+
+	<para>Permission denied is returned in some cases where the cause of the error is unknown 
+(such as an illegally formatted smb:// url or trying to get a directory without -R 
+turned on).</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+
+	<para>The smbget manpage was written by Jelmer Vernooij.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbgetrc.5.xml b/docs-xml/manpages-3/smbgetrc.5.xml
new file mode 100644
index 00000000000..d555927bc31
--- /dev/null
+++ b/docs-xml/manpages-3/smbgetrc.5.xml
@@ -0,0 +1,116 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbgetrc.5">
+
+<refmeta>
+	<refentrytitle>smbgetrc</refentrytitle>
+	<manvolnum>5</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">File Formats and Conventions</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbgetrc</refname>
+	<refpurpose>configuration file for smbget</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<para><filename>smbgetrc</filename></para>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>
+		This manual page documents the format and options of the <emphasis>smbgetrc</emphasis> 
+		file. This is the configuration file used by the <citerefentry><refentrytitle>smbget</refentrytitle><manvolnum>1</manvolnum></citerefentry> 
+		utility. The file contains of key-value pairs, one pair on each line. The key 
+			and value should be separated by a space.
+	</para>
+
+	<para>By default, smbget reads its configuration from <emphasis>$HOME/.smbgetrc</emphasis>, though 
+		other locations can be specified using the command-line options.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<para>
+	The following keys can be set:
+</para>
+
+	<variablelist>
+		<varlistentry><term>resume on|off</term>
+			<listitem><para>
+			Whether aborted downloads should be automatically resumed.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>recursive on|off</term>
+			<listitem><para>Whether directories should be downloaded recursively</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>username <replaceable>name</replaceable></term>
+			<listitem><para>Username to use when logging in to the remote server. Use an empty string for anonymous access.
+			</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>password <replaceable>pass</replaceable></term>
+			<listitem><para>Password to use when logging in.</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>workgroup <replaceable>wg</replaceable></term>
+			<listitem><para>Workgroup to use when logging in</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>nonprompt on|off</term>
+			<listitem><para>Turns off asking for username and password. Useful for scripts.</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>debuglevel <replaceable>int</replaceable></term>
+			<listitem><para>(Samba) debuglevel to run at. Useful for tracking down protocol level problems.</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>dots on|off</term>
+			<listitem><para>Whether a single dot should be printed for each block that has been downloaded, instead of the default progress indicator.</para></listitem>
+		</varlistentry>
+
+		<varlistentry><term>blocksize <replaceable>int</replaceable></term>
+			<listitem><para>Number of bytes to put in a block. </para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>smbget</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> and <citerefentry><refentrytitle>Samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry>.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+
+	<para>This manual page was written by Jelmer Vernooij</para>
+	
+</refsect1>
+
+</refentry>
+
+
diff --git a/docs-xml/manpages-3/smbpasswd.5.xml b/docs-xml/manpages-3/smbpasswd.5.xml
new file mode 100644
index 00000000000..592a7de8b84
--- /dev/null
+++ b/docs-xml/manpages-3/smbpasswd.5.xml
@@ -0,0 +1,211 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbpasswd.5">
+
+<refmeta>
+	<refentrytitle>smbpasswd</refentrytitle>
+	<manvolnum>5</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">File Formats and Conventions</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbpasswd</refname>
+	<refpurpose>The Samba encrypted password file</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<para><filename>smbpasswd</filename></para>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>smbpasswd is the Samba encrypted password file. It contains 
+	the username, Unix user id and the SMB hashed passwords of the 
+	user, as well as account flag information and the time the 
+	password was last changed. This file format has been evolving with 
+	Samba and has had several different formats in the past. </para>
+</refsect1>
+
+<refsect1>
+	<title>FILE FORMAT</title>
+
+	<para>The format of the smbpasswd file used by Samba 2.2 
+	is very similar to the familiar Unix <filename>passwd(5)</filename> 
+	file. It is an ASCII file containing one line for each user. Each field 
+	ithin each line is separated from the next by a colon. Any entry 
+	beginning with '#' is ignored. The smbpasswd file contains the 
+	following information for each user: </para>
+
+	<variablelist>
+		<varlistentry>
+		<term>name</term>
+		<listitem><para> This is the user name. It must be a name that 
+		already exists in the standard UNIX passwd file. </para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>uid</term>
+		<listitem><para>This is the UNIX uid. It must match the uid
+		field for the same user entry in the standard UNIX passwd file. 
+		If this does not match then Samba will refuse to recognize 
+		this smbpasswd file entry as being valid for a user. 
+		</para></listitem>
+		</varlistentry>
+		 
+		 
+		<varlistentry>
+		<term>Lanman Password Hash</term>
+		<listitem><para>This is the LANMAN hash of the user's password, 
+		encoded as 32 hex digits.  The LANMAN hash is created by DES 
+		encrypting a well known string with the user's password as the 
+		DES key. This is the same password used by Windows 95/98 machines. 
+		Note that this password hash is regarded as weak as it is
+		vulnerable to dictionary attacks and if two users choose the 
+		same password this entry will be identical (i.e. the password 
+		is not "salted" as the UNIX password is). If the user has a 
+		null password this field will contain the characters "NO PASSWORD" 
+		as the start of the hex string. If the hex string is equal to 
+		32 'X' characters then the user's account is marked as 
+		<constant>disabled</constant> and the user will not be able to 
+		log onto the Samba server. </para>
+		
+		<para><emphasis>WARNING !!</emphasis> Note that, due to 
+		the challenge-response nature of the SMB/CIFS authentication
+		protocol, anyone with a knowledge of this password hash will 
+		be able to impersonate the user on the network. For this
+		reason these hashes are known as <emphasis>plain text 
+		equivalents</emphasis> and must <emphasis>NOT</emphasis> be made 
+		available to anyone but the root user. To protect these passwords 
+		the smbpasswd file is placed in a directory with read and 
+		traverse access only to the root user and the smbpasswd file 
+		itself must be set to be read/write only by root, with no
+		other access. </para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>NT Password Hash</term>
+		<listitem><para>This is the Windows NT hash of the user's 
+		password, encoded as 32 hex digits.  The Windows NT hash is 
+		created by taking the user's password as represented in 
+		16-bit, little-endian UNICODE and then applying the MD4 
+		(internet rfc1321) hashing algorithm to it. </para>
+		
+		<para>This password hash is considered more secure than
+		the LANMAN Password Hash as it preserves the case of the 
+		password and uses a much higher quality hashing algorithm. 
+		However, it is still the case that if two users choose the same 
+		password this entry will be identical (i.e. the password is 
+		not "salted" as the UNIX password is). </para>
+
+		<para><emphasis>WARNING !!</emphasis>. Note that, due to 
+		the challenge-response nature of the SMB/CIFS authentication
+		protocol, anyone with a knowledge of this password hash will 
+		be able to impersonate the user on the network. For this
+		reason these hashes are known as <emphasis>plain text 
+		equivalents</emphasis> and must <emphasis>NOT</emphasis> be made 
+		available to anyone but the root user. To protect these passwords 
+		the smbpasswd file is placed in a directory with read and 
+		traverse access only to the root user and the smbpasswd file 
+		itself must be set to be read/write only by root, with no
+		other access. </para></listitem>
+		</varlistentry>
+		
+
+		<varlistentry>
+		<term>Account Flags</term>
+		<listitem><para>This section contains flags that describe 
+		the attributes of the users account.  This field is bracketed by 
+		'[' and ']' characters and is always 13 characters in length 
+		(including the '[' and ']' characters).
+		The contents of this field may be any of the following characters:
+		</para>
+		
+		<itemizedlist>
+			<listitem><para><emphasis>U</emphasis> - This means 
+			this is a "User" account, i.e. an ordinary user.</para></listitem>
+			
+			<listitem><para><emphasis>N</emphasis> - This means the
+			account has no password (the passwords in the fields LANMAN 
+			Password Hash and NT Password Hash are ignored). Note that this 
+			will only allow users to log on with no password if the <parameter>
+			null passwords</parameter> parameter is set in the 
+			<citerefentry><refentrytitle>smb.conf</refentrytitle>
+			<manvolnum>5</manvolnum></citerefentry> config file. </para></listitem>
+				
+			<listitem><para><emphasis>D</emphasis> - This means the account 
+			is disabled and no SMB/CIFS logins  will be allowed for this user. </para></listitem>
+			
+			<listitem><para><emphasis>X</emphasis> - This means the password 
+			does not expire. </para></listitem>
+			
+			<listitem><para><emphasis>W</emphasis> - This means this account 
+			is a "Workstation Trust" account. This kind of account is used 
+			in the Samba PDC code stream to allow Windows NT Workstations 
+			and Servers to join a Domain hosted by a Samba PDC. </para>
+			</listitem>
+		</itemizedlist>
+		
+		<para>Other flags may be added as the code is extended in future.
+		The rest of this field space is filled in with spaces. For further
+		information regarding the flags that are supported please refer to the
+		man page for the <command>pdbedit</command> command.</para>
+		</listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>Last Change Time</term>
+		<listitem><para>This field consists of the time the account was 
+		last modified. It consists of the characters 'LCT-' (standing for 
+		"Last Change Time") followed by a numeric encoding of the UNIX time 
+		in seconds since the epoch (1970) that the last change was made. 
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+	
+	<para>All other colon separated fields are ignored at this time.</para> 
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>smbpasswd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>Samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry>, and
+	the Internet RFC1321 for details on the MD4 algorithm.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink noescape="1" url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
+	for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbpasswd.8.xml b/docs-xml/manpages-3/smbpasswd.8.xml
new file mode 100644
index 00000000000..bc951bcf5f7
--- /dev/null
+++ b/docs-xml/manpages-3/smbpasswd.8.xml
@@ -0,0 +1,431 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbpasswd.8">
+
+<refmeta>
+	<refentrytitle>smbpasswd</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbpasswd</refname>
+	<refpurpose>change a user's SMB password</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbpasswd</command>
+		<arg choice="opt">-a</arg>	
+		<arg choice="opt">-c &lt;config file&gt;</arg>	
+		<arg choice="opt">-x</arg>	
+		<arg choice="opt">-d</arg>	
+		<arg choice="opt">-e</arg>	
+		<arg choice="opt">-D debuglevel</arg>	
+		<arg choice="opt">-n</arg>	
+		<arg choice="opt">-r &lt;remote machine&gt;</arg>	
+		<arg choice="opt">-R &lt;name resolve order&gt;</arg>	
+		<arg choice="opt">-m</arg>	
+		<arg choice="opt">-U username[%password]</arg>	
+		<arg choice="opt">-h</arg>	
+		<arg choice="opt">-s</arg>	
+		<arg choice="opt">-w pass</arg>	
+		<arg choice="opt">-W</arg>
+		<arg choice="opt">-i</arg>
+		<arg choice="opt">-L</arg>
+		<arg choice="opt">username</arg>	
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+	
+	<para>The smbpasswd program has several different 
+	functions, depending on whether it is run by the <emphasis>root</emphasis> user 
+	or not. When run as a normal user it allows the user to change 
+	the password used for their SMB sessions on any machines that store 
+	SMB passwords. </para>
+
+	<para>By default (when run with no arguments) it will attempt to 
+	change the current user's SMB password on the local machine. This is 
+	similar to the way the <command>passwd(1)</command> program works. <command>
+	smbpasswd</command> differs from how the passwd program works 
+	however in that it is not <emphasis>setuid root</emphasis> but works in 
+	a client-server mode and communicates with a 
+	locally running <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>. As a consequence in order for this to 
+	succeed the smbd daemon must be running on the local machine. On a 
+	UNIX machine the encrypted SMB passwords are usually stored in 
+	the <citerefentry><refentrytitle>smbpasswd</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> file. </para>
+
+	<para>When run by an ordinary user with no options, smbpasswd 
+	will prompt them for their old SMB password and then ask them 
+	for their new password twice, to ensure that the new password
+	was typed correctly. No passwords will be echoed on the screen 
+	whilst being typed. If you have a blank SMB password (specified by 
+	the string "NO PASSWORD" in the smbpasswd file) then just press 
+	the &lt;Enter&gt; key when asked for your old password. </para>
+
+	<para>smbpasswd can also be used by a normal user to change their
+	SMB password on remote machines, such as Windows NT Primary Domain 
+	Controllers.   See the (<parameter>-r</parameter>) and <parameter>-U</parameter> options 
+	below. </para>
+
+	<para>When run by root, smbpasswd allows new users to be added 
+	and deleted in the smbpasswd file, as well as allows changes to 
+	the attributes of the user in this file to be made. When run by root, <command>
+	smbpasswd</command> accesses the local smbpasswd file 
+	directly, thus enabling changes to be made even if smbd is not 
+	running. </para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+	<variablelist>
+		<varlistentry>
+		<term>-a</term>
+		<listitem><para>
+		This option specifies that the username following should be added to the local smbpasswd file, with the new
+		password typed (type &lt;Enter&gt; for the old password). This option is ignored if the username following
+		already exists in the smbpasswd file and it is treated like a regular change password command.  Note that the
+		default passdb backends require the user to already exist in the system password file (usually
+		<filename>/etc/passwd</filename>), else the request to add the user will fail.
+		</para>
+		
+		<para>This option is only available when running smbpasswd 
+		as root. </para></listitem>
+		</varlistentry>
+		
+
+		<varlistentry>
+		<term>-c</term>
+		<listitem><para>
+		This option can be used to specify the path and file name of the &smb.conf; configuration file when it
+		is important to use other than the default file and / or location.
+		</para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-x</term>
+		<listitem><para>
+		This option specifies that the username following should be deleted from the local smbpasswd file.
+		</para>
+
+		<para>
+		This option is only available when running smbpasswd as root.
+		</para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-d</term>
+		<listitem><para>This option specifies that the username following 
+		should be <constant>disabled</constant> in the local smbpasswd 
+		file. This is done by writing a <constant>'D'</constant> flag 
+		into the account control space in the smbpasswd file. Once this 
+		is done all attempts to authenticate via SMB using this username 
+		will fail. </para>
+		
+		<para>If the smbpasswd file is in the 'old' format (pre-Samba 2.0 
+		format) there is no space in the user's password entry to write
+		this information and the command will FAIL. See <citerefentry><refentrytitle>smbpasswd</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> for details on the 'old' and new password file formats.
+		</para>
+
+		<para>This option is only available when running smbpasswd as 
+		root.</para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-e</term>
+		<listitem><para>This option specifies that the username following 
+		should be <constant>enabled</constant> in the local smbpasswd file, 
+		if the account was previously disabled. If the account was not 
+		disabled this option has no effect. Once the account is enabled then 
+		the user will be able to authenticate via SMB once again. </para>
+		
+		<para>If the smbpasswd file is in the 'old' format, then <command>
+		smbpasswd</command> will FAIL to enable the account.  
+                See <citerefentry><refentrytitle>smbpasswd</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> for 
+		details on the 'old' and new password file formats. </para>
+
+		<para>This option is only available when running smbpasswd as root. 
+		</para></listitem>
+		</varlistentry>
+		
+
+
+		<varlistentry>
+		<term>-D debuglevel</term>
+		<listitem><para><replaceable>debuglevel</replaceable> is an integer 
+		from 0 to 10.  The default value if this parameter is not specified 
+		is zero. </para>
+
+		<para>The higher this value, the more detail will be logged to the 
+		log files about the activities of smbpasswd. At level 0, only 
+		critical errors and serious warnings will be logged. </para>
+
+		<para>Levels above 1 will generate considerable amounts of log 
+		data, and should only be used when investigating a problem. Levels 
+		above 3 are designed for use only by developers and generate
+		HUGE amounts of log data, most of which is extremely cryptic. 
+		</para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-n</term>
+		<listitem><para>This option specifies that the username following 
+		should have their password set to null (i.e. a blank password) in 
+		the local smbpasswd file. This is done by writing the string "NO 
+		PASSWORD" as the first part of the first password stored in the 
+		smbpasswd file. </para>
+
+		<para>Note that to allow users to logon to a Samba server once 
+		the password has been set to "NO PASSWORD" in the smbpasswd
+		file the administrator must set the following parameter in the [global]
+		section of the <filename>smb.conf</filename> file : </para>
+		
+		<para><command>null passwords = yes</command></para> 
+		
+		<para>This option is only available when running smbpasswd as 
+		root.</para></listitem>
+		</varlistentry>
+		
+		
+		
+		<varlistentry>
+		<term>-r remote machine name</term>
+		<listitem><para>This option allows a user to specify what machine 
+		they wish to change their password on. Without this parameter 
+		smbpasswd defaults to the local host. The <replaceable>remote 
+		machine name</replaceable> is the NetBIOS name of the SMB/CIFS 
+		server to contact to attempt the password change. This name is 
+		resolved into an IP address using the standard name resolution 
+		mechanism in all programs of the Samba suite. See the <parameter>-R 
+		name resolve order</parameter> parameter for details on changing 
+		this resolving mechanism. </para>
+
+		<para>The username whose password is changed is that of the 
+		current UNIX logged on user. See the <parameter>-U username</parameter>
+		parameter for details on changing the password for a different 
+		username. </para>
+
+		<para>Note that if changing a Windows NT Domain password the 
+		remote machine specified must be the Primary Domain Controller for 
+		the domain (Backup Domain Controllers only have a read-only
+		copy of the user account database and will not allow the password 
+		change).</para>
+		
+		<para><emphasis>Note</emphasis> that Windows 95/98 do not have 
+		a real password database so it is not possible to change passwords 
+		specifying a Win95/98  machine as remote machine target. </para>
+		</listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-R name resolve order</term>
+		<listitem><para>This option allows the user of smbpasswd to determine
+		what name resolution services to use when looking up the NetBIOS
+		name of the host being connected to. </para>
+
+		<para>The options are :"lmhosts", "host", "wins" and "bcast". They
+		 cause names to be resolved as follows: </para>
+			<itemizedlist>
+				<listitem><para><constant>lmhosts</constant>: Lookup an IP 
+            address in the Samba lmhosts file. If the line in lmhosts has 
+            no name type attached to the NetBIOS name (see the <citerefentry><refentrytitle>lmhosts</refentrytitle>
+	    <manvolnum>5</manvolnum></citerefentry> for details) then
+            any name type matches for lookup.</para></listitem>
+
+            <listitem><para><constant>host</constant>: Do a standard host 
+            name to IP address resolution, using the system <filename>/etc/hosts
+            </filename>, NIS, or DNS lookups. This method of name resolution 
+            is operating system depended for instance on IRIX or Solaris this 
+            may be controlled by the <filename>/etc/nsswitch.conf</filename> 
+            file).  Note that this method is only used if the NetBIOS name 
+            type being queried is the 0x20 (server) name type, otherwise 
+            it is ignored.</para></listitem>
+
+            <listitem><para><constant>wins</constant>: Query a name with 
+            the IP address listed in the <parameter>wins server</parameter> 
+	    parameter.  If no WINS server has been specified this method 
+	    will be ignored.</para></listitem>
+
+            <listitem><para><constant>bcast</constant>: Do a broadcast on 
+            each of the known local interfaces listed in the
+            <parameter>interfaces</parameter> parameter. This is the least 
+	    reliable of the name resolution methods as it depends on the 
+	    target host being on a locally connected subnet.</para></listitem>
+		</itemizedlist>
+		
+		<para>The default order is <command>lmhosts, host, wins, bcast</command> 
+		and without this parameter or any entry in the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> file the name resolution methods will 
+		be attempted in this order. </para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-m</term>
+		<listitem><para>This option tells smbpasswd that the account 
+		being changed is a MACHINE account. Currently this is used 
+		when Samba is being used as an NT Primary Domain Controller.</para>
+
+		<para>This option is only available when running smbpasswd as root.
+		</para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-U username</term>
+		<listitem><para>This option may only be used in conjunction 
+		with the <parameter>-r</parameter> option. When changing
+		a password on a remote machine it allows the user to specify 
+		the user name on that machine whose password will be changed. It 
+		is present to allow users who have different user names on 
+		different systems to change these passwords. </para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-h</term>
+		<listitem><para>This option prints the help string for <command>
+		smbpasswd</command>, selecting the correct one for running as root 
+		or as an ordinary user. </para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-s</term>
+		<listitem><para>This option causes smbpasswd to be silent (i.e. 
+		not issue prompts) and to read its old and new passwords from 
+		standard  input, rather than from <filename>/dev/tty</filename> 
+		(like the <command>passwd(1)</command> program does). This option 
+		is to aid people writing scripts to drive smbpasswd</para>
+		</listitem>
+		</varlistentry>
+		
+
+		<varlistentry>
+		<term>-w password</term>
+		<listitem><para>This parameter is only available if Samba
+		has been compiled with LDAP support. The <parameter>-w</parameter> 
+		switch is used to specify the password to be used with the 
+		<smbconfoption name="ldap admin dn"/>.  Note that the password is stored in
+		the <filename>secrets.tdb</filename> and is keyed off 
+		of the admin's DN.  This means that if the value of <parameter>ldap
+		admin dn</parameter> ever changes, the password will need to be 
+		manually updated as well.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-W</term>
+		<listitem><para><command>NOTE: </command> This option is same as "-w"
+		except that the password should be entered using stdin.
+		</para>
+		<para>This parameter is only available if Samba
+		has been compiled with LDAP support. The <parameter>-W</parameter>
+		switch is used to specify the password to be used with the
+		<smbconfoption name="ldap admin dn"/>.  Note that the password is stored in
+		the <filename>secrets.tdb</filename> and is keyed off
+		of the admin's DN.  This means that if the value of <parameter>ldap
+		admin dn</parameter> ever changes, the password will need to be
+		manually updated as well.
+		</para>
+		</listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-i</term>
+		<listitem><para>This option tells smbpasswd that the account 
+		being changed is an interdomain trust account. Currently this is used 
+		when Samba is being used as an NT Primary Domain Controller. 
+		The account contains the info about another trusted domain.</para>
+
+		<para>This option is only available when running smbpasswd as root.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-L</term>
+		<listitem><para>Run in local mode.</para></listitem>
+		</varlistentry>
+		
+		<varlistentry>
+		<term>username</term>
+		<listitem><para>This specifies the username for all of the 
+		<emphasis>root only</emphasis> options to operate on. Only root 
+		can specify this parameter as only root has the permission needed 
+		to modify attributes directly in the local smbpasswd file. 
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>NOTES</title>
+	
+	<para>Since <command>smbpasswd</command> works in client-server 
+	mode communicating  with a local smbd for a non-root user then 
+	the smbd daemon must be running for this to work. A common problem 
+	is to add a restriction to the hosts that may access the <command>
+	smbd</command> running on the local machine by specifying either <parameter>allow
+	hosts</parameter> or <parameter>deny hosts</parameter> entry in 
+	the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> file and neglecting to 
+	allow "localhost" access to the smbd. </para>
+
+	<para>In addition, the smbpasswd command is only useful if Samba
+	has been set up to use encrypted passwords. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>smbpasswd</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>Samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry>.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
+	for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbsh.1.xml b/docs-xml/manpages-3/smbsh.1.xml
new file mode 100644
index 00000000000..50439a90c2b
--- /dev/null
+++ b/docs-xml/manpages-3/smbsh.1.xml
@@ -0,0 +1,164 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbsh.1">
+
+<refmeta>
+	<refentrytitle>smbsh</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbsh</refname>
+	<refpurpose>Allows access to remote SMB shares
+	using UNIX commands</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbsh</command>
+		<arg choice="opt">-W workgroup</arg>
+		<arg choice="opt">-U username</arg>
+		<arg choice="opt">-P prefix</arg>
+		<arg choice="opt">-R &lt;name resolve order&gt;</arg>
+		<arg choice="opt">-d &lt;debug level&gt;</arg>
+		<arg choice="opt">-l logdir</arg>
+		<arg choice="opt">-L libdir</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>smbsh</command> allows you to access an NT filesystem 
+	using UNIX commands such as <command>ls</command>, <command>
+	egrep</command>, and <command>rcp</command>. You must use a 
+	shell that is dynamically linked in order for <command>smbsh</command> 
+	to work correctly.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+	    <varlistentry>
+		<term>-W WORKGROUP</term>
+		<listitem><para>Override the default workgroup specified in the 
+		workgroup parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> file 
+		for this session. This may be needed to connect to some 
+		servers. </para></listitem>
+	    </varlistentry>
+		
+	    <varlistentry>
+		<term>-U username[%pass]</term>
+		<listitem><para>Sets the SMB username or username and password.
+		If this option is not specified, the user will be prompted for 
+		both the username and the password.  If %pass is not specified, 
+		the user will be prompted for the password.
+		</para></listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+		<term>-P prefix</term>
+		<listitem><para>This option allows
+		the user to set the directory prefix for SMB access. The 
+		default value if this option is not specified is 
+		<emphasis>smb</emphasis>.
+		</para></listitem>
+	    </varlistentry>
+
+		&stdarg.configfile;
+		&stdarg.server.debug;
+		&stdarg.resolve.order;
+
+	    <varlistentry>
+		<term>-L libdir</term>
+		<listitem><para>This parameter specifies the location of the 
+		shared libraries used by <command>smbsh</command>. The default
+		value is specified at compile time.
+		</para></listitem>
+	    </varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>To use the <command>smbsh</command> command, execute <command>
+	smbsh</command> from the prompt and enter the username and password 
+	that authenticates you to the machine running the Windows NT 
+	operating system.
+<programlisting>
+<prompt>system% </prompt><userinput>smbsh</userinput>
+<prompt>Username: </prompt><userinput>user</userinput>
+<prompt>Password: </prompt><userinput>XXXXXXX</userinput>
+</programlisting></para>
+
+
+	<para>Any dynamically linked command you execute from 
+	this shell will access the <filename>/smb</filename> directory 
+	using the smb protocol. For example, the command <command>ls /smb
+	</command> will show a list of workgroups. The command 
+	<command>ls /smb/MYGROUP </command> will show all the machines in 
+	the  workgroup MYGROUP. The command 
+	<command>ls /smb/MYGROUP/&lt;machine-name&gt;</command> will show the share 
+	names for that machine. You could then, for example, use the <command>
+	cd</command> command to change directories, <command>vi</command> to 
+	edit files, and <command>rcp</command>  to copy files.</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>BUGS</title>
+	
+	<para><command>smbsh</command> works by intercepting the standard 
+	libc calls with the dynamically loaded versions in <filename>
+	smbwrapper.o</filename>. Not all calls have been "wrapped", so 
+	some programs may not function correctly under <command>smbsh
+	</command>.</para>
+
+	<para>Programs which are not dynamically linked cannot make 
+	use of <command>smbsh</command>'s functionality. Most versions 
+	of UNIX have a <command>file</command> command that will 
+	describe how a program was linked.</para>
+</refsect1>
+
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry></para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
+	for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbspool.8.xml b/docs-xml/manpages-3/smbspool.8.xml
new file mode 100644
index 00000000000..f43650295c9
--- /dev/null
+++ b/docs-xml/manpages-3/smbspool.8.xml
@@ -0,0 +1,133 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbspool.8">
+
+<refmeta>
+	<refentrytitle>smbspool</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbspool</refname>
+	<refpurpose>send a print file to an SMB printer</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbspool</command>
+		<arg choice="req">job</arg> 
+		<arg choice="req">user</arg> 
+		<arg choice="req">title</arg> 
+		<arg choice="req">copies</arg> 
+		<arg choice="req">options</arg> 
+		<arg choice="opt">filename</arg> 
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>smbspool is a very small print spooling program that 
+	sends a print file to an SMB printer. The command-line arguments 
+	are position-dependent for compatibility with the Common UNIX 
+	Printing System, but you can use smbspool with any printing system 
+	or from a program or script.</para>
+
+	<para><emphasis>DEVICE URI</emphasis></para>
+
+	<para>smbspool specifies the destination using a Uniform Resource 
+	Identifier ("URI") with a method of "smb". This string can take 
+	a number of forms:</para>
+
+	<itemizedlist>
+		<listitem><para>smb://server[:port]/printer</para></listitem>
+		<listitem><para>smb://workgroup/server[:port]/printer</para></listitem>
+		<listitem><para>smb://username:password@server[:port]/printer</para></listitem>
+		<listitem><para>smb://username:password@workgroup/server[:port]/printer</para></listitem>
+	</itemizedlist>
+
+	<para>smbspool tries to get the URI from the environment variable
+	<envar>DEVICE_URI</envar>. If <envar>DEVICE_URI</envar> is not present, 
+	smbspool will use argv[0] if that starts with <quote>smb://</quote> 
+	or argv[1] if that is not the case.</para>
+
+	<para>Programs using the <command>exec(2)</command> functions can 
+	pass the URI in argv[0], while shell scripts must set the 
+	<envar>DEVICE_URI</envar> environment variable prior to
+	running smbspool.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<itemizedlist>
+		<listitem><para>The job argument (argv[1]) contains the 
+		job ID number and is presently not used by smbspool.
+		</para></listitem>
+
+		<listitem><para>The user argument (argv[2]) contains the 
+		print user's name and is presently not used by smbspool.
+		</para></listitem>
+
+		<listitem><para>The title argument (argv[3]) contains the 
+		job title string and is passed as the remote file name 
+		when sending the print job.</para></listitem>
+
+		<listitem><para>The copies argument (argv[4]) contains 
+		the number of copies to be printed of the named file. If 
+		no filename is provided then this argument is not used by 
+		smbspool.</para></listitem>
+
+		<listitem><para>The options argument (argv[5]) contains 
+		the print options in a single string and is currently 
+		not used by smbspool.</para></listitem>
+
+		<listitem><para>The filename argument (argv[6]) contains the 
+		name of the file to print. If this argument is not specified 
+		then the print file is read from the standard input.</para>
+		</listitem>
+	</itemizedlist>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry>.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para><command>smbspool</command> was written by Michael Sweet 
+	at Easy Software Products.</para>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
+	for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbstatus.1.xml b/docs-xml/manpages-3/smbstatus.1.xml
new file mode 100644
index 00000000000..cd0a76a9ff1
--- /dev/null
+++ b/docs-xml/manpages-3/smbstatus.1.xml
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbstatus.1">
+
+<refmeta>
+	<refentrytitle>smbstatus</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbstatus</refname>
+	<refpurpose>report on current Samba connections</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbstatus</command>
+		<arg choice="opt">-P</arg>
+		<arg choice="opt">-b</arg>
+		<arg choice="opt">-d &lt;debug level&gt;</arg>
+		<arg choice="opt">-v</arg>
+		<arg choice="opt">-L</arg>
+		<arg choice="opt">-B</arg>
+		<arg choice="opt">-p</arg>
+		<arg choice="opt">-S</arg>
+		<arg choice="opt">-s &lt;configuration file&gt;</arg>
+		<arg choice="opt">-u &lt;username&gt;</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>smbstatus</command> is a very simple program to 
+	list the current Samba connections.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-P|--profile</term>
+		<listitem><para>If samba has been compiled with the 
+		profiling option, print only the contents of the profiling 
+		shared memory area.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-b|--brief</term>
+		<listitem><para>gives brief output.</para></listitem>
+		</varlistentry>
+
+		&stdarg.server.debug;
+		&popt.common.samba;
+	
+		<varlistentry>
+		<term>-v|--verbose</term>
+		<listitem><para>gives verbose output.</para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-L|--locks</term>
+		<listitem><para>causes smbstatus to only list locks.</para>
+		</listitem>
+		</varlistentry>
+
+		
+		<varlistentry>
+		<term>-B|--byterange</term>
+		<listitem><para>causes smbstatus to include byte range locks.
+		</para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-p|--processes</term>
+		<listitem><para>print a list of <citerefentry><refentrytitle>smbd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> processes and exit. 
+		Useful for scripting.</para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-S|--shares</term>
+		<listitem><para>causes smbstatus to only list shares.</para>
+		</listitem>
+		</varlistentry>
+
+		&stdarg.help;
+
+		<varlistentry>
+		<term>-u|--user=&lt;username&gt;</term>
+		<listitem><para>selects information relevant to <parameter>username</parameter> only.</para>
+		</listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
+	for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbtar.1.xml b/docs-xml/manpages-3/smbtar.1.xml
new file mode 100644
index 00000000000..ee2bff0f3a5
--- /dev/null
+++ b/docs-xml/manpages-3/smbtar.1.xml
@@ -0,0 +1,237 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbtar.1">
+
+<refmeta>
+	<refentrytitle>smbtar</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbtar</refname>
+	<refpurpose>shell script for backing up SMB/CIFS shares 
+	directly to UNIX tape drives</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbtar</command>
+		<arg choice="opt">-r</arg>
+		<arg choice="opt">-i</arg>
+		<arg choice="opt">-a</arg>
+		<arg choice="opt">-v</arg>
+		<arg choice="req">-s server</arg>
+		<arg choice="opt">-p password</arg>
+		<arg choice="opt">-x services</arg>
+		<arg choice="opt">-X</arg>
+		<arg choice="opt">-N filename</arg>
+		<arg choice="opt">-b blocksize</arg>
+		<arg choice="opt">-d directory</arg>
+		<arg choice="opt">-l loglevel</arg>
+		<arg choice="opt">-u user</arg>
+		<arg choice="opt">-t tape</arg>
+		<arg choice="req">filenames</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>smbtar</command> is a very small shell script on top 
+	of <citerefentry><refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum>
+	</citerefentry> which dumps SMB shares directly to tape.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-s server</term>
+		<listitem><para>The SMB/CIFS server that the share resides 
+		upon.</para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-x service</term>
+		<listitem><para>The share name on the server to connect to. 
+		The default is "backup".</para></listitem>
+		</varlistentry>
+		
+		
+		<varlistentry>
+		<term>-X</term>
+		<listitem><para>Exclude mode. Exclude filenames... from tar 
+		create or restore. </para></listitem>
+		</varlistentry>
+
+
+
+		<varlistentry>
+		<term>-d directory</term>
+		<listitem><para>Change to initial <parameter>directory
+		</parameter> before restoring / backing up files. </para></listitem>
+		</varlistentry>
+
+
+
+		<varlistentry>
+		<term>-v</term>
+		<listitem><para>Verbose mode.</para></listitem>
+		</varlistentry>
+
+
+
+		<varlistentry>
+		<term>-p password</term>
+		<listitem><para>The password to use to access a share. 
+		Default: none </para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-u user</term>
+		<listitem><para>The user id to connect as. Default: 
+		UNIX login name. </para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-a</term>
+		<listitem><para>Reset DOS archive bit mode to 
+		indicate file has been archived. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-t tape</term>
+		<listitem><para>Tape device. May be regular file or tape 
+		device. Default: <parameter>$TAPE</parameter> environmental 
+		variable; if not set, a file called <filename>tar.out
+		</filename>. </para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-b blocksize</term>
+		<listitem><para>Blocking factor. Defaults to 20. See
+		<command>tar(1)</command> for a fuller explanation. </para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-N filename</term>
+		<listitem><para>Backup only files newer than filename. Could 
+		be used (for example) on a log file to implement incremental
+		backups. </para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-i</term>
+		<listitem><para>Incremental mode; tar files are only backed 
+		up if they have the archive bit set. The archive bit is reset 
+		after each file is read. </para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-r</term>
+		<listitem><para>Restore. Files are restored to the share 
+		from the tar file. </para></listitem>
+		</varlistentry>
+
+
+
+		<varlistentry>
+		<term>-l log level</term>
+		<listitem><para>Log (debug) level. Corresponds to the 
+		<parameter>-d</parameter> flag of <citerefentry>
+		<refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum>
+		</citerefentry>.</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>ENVIRONMENT VARIABLES</title>
+
+	<para>The <parameter>$TAPE</parameter> variable specifies the 
+	default tape device to write to. May be overridden
+	with the -t option. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>BUGS</title>
+
+	<para>The <command>smbtar</command> script has different 
+	options from ordinary tar and from smbclient's tar command. </para>
+
+</refsect1>
+
+<refsect1>
+	<title>CAVEATS</title>
+
+	<para>Sites that are more careful about security may not like 
+	the way the script handles PC passwords. Backup and restore work 
+	on entire shares; should work on file lists. smbtar works best
+	with GNU tar and may not work well with other versions. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>DIAGNOSTICS</title>
+
+	<para>See the <emphasis>DIAGNOSTICS</emphasis> section for the <citerefentry>
+	<refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum>
+	</citerefentry> command.</para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
+	<refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum>
+	</citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+<para><ulink noescape="1" url="mailto:poultenr@logica.co.uk">Ricky Poulten</ulink>  
+	wrote the tar extension and this man page. The <command>smbtar</command> 
+	script was heavily rewritten and improved by <ulink noescape="1"
+	url="mailto:Martin.Kraemer@mch.sni.de">Martin Kraemer</ulink>. Many 
+	thanks to everyone who suggested extensions, improvements, bug 
+	fixes, etc. The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink noescape="1" url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
+	Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/smbtree.1.xml b/docs-xml/manpages-3/smbtree.1.xml
new file mode 100644
index 00000000000..bc9450137c8
--- /dev/null
+++ b/docs-xml/manpages-3/smbtree.1.xml
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="smbtree.1">
+
+<refmeta>
+	<refentrytitle>smbtree</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smbtree</refname>
+	<refpurpose>A text based smb network browser
+	</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>smbtree</command>
+		<arg choice="opt">-b</arg>
+		<arg choice="opt">-D</arg>
+		<arg choice="opt">-S</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>smbtree</command> is a smb browser program 
+	in text mode. It is similar to the "Network Neighborhood" found 
+	on Windows computers. It prints a tree with all 
+	the known domains, the servers in those domains and 
+	the shares on the servers.
+	</para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-b</term>
+		<listitem><para>Query network nodes by sending requests 
+		as broadcasts instead of querying the local master browser.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-D</term>
+		<listitem><para>Only print a list of all 
+		the domains known on broadcast or by the 
+		master browser</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-S</term>
+		<listitem><para>Only print a list of 
+		all the domains and servers responding on broadcast or 
+		known by the master browser. 
+		</para></listitem>
+		</varlistentry>
+
+		&stdarg.server.debug;
+		&popt.common.samba;
+		&popt.common.credentials;
+		&stdarg.help;
+		
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba 
+	suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The smbtree man page was written by Jelmer Vernooij. </para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/swat.8.xml b/docs-xml/manpages-3/swat.8.xml
new file mode 100644
index 00000000000..2a2630763a0
--- /dev/null
+++ b/docs-xml/manpages-3/swat.8.xml
@@ -0,0 +1,237 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="swat.8">
+
+<refmeta>
+	<refentrytitle>swat</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>swat</refname>
+	<refpurpose>Samba Web Administration Tool</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>swat</command>
+		<arg choice="opt">-s &lt;smb config file&gt;</arg>
+		<arg choice="opt">-a</arg>
+		<arg choice="opt">-P</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+
+	<para><command>swat</command> allows a Samba administrator to 
+	configure the complex <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> file via a Web browser. In addition, 
+	a <command>swat</command> configuration page has help links 
+	to all the configurable options in the <filename>smb.conf</filename> file allowing an 
+	administrator to easily look up the effects of any change. </para>
+
+	<para><command>swat</command> is run from <command>inetd</command> </para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-s smb configuration file</term>
+		<listitem><para>The default configuration file path is 
+		determined at compile time.  The file specified contains 
+		the configuration details required by the <citerefentry><refentrytitle>smbd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> server. This is the file 
+		that <command>swat</command> will modify. 
+		The information in this file includes server-specific 
+		information such as what printcap file to use, as well as 
+		descriptions of all the services that the server is to provide.
+		See <filename>smb.conf</filename> for more information. 
+		</para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>-a</term>
+		<listitem><para>This option disables authentication and 
+		places <command>swat</command> in demo mode. In that mode anyone will be able to modify 
+		the <filename>smb.conf</filename> file. </para>
+		
+		<para><emphasis>WARNING: Do NOT enable this option on a production 
+		server. </emphasis></para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-P</term>
+		<listitem><para>This option restricts read-only users to the password 
+        management page.  <command>swat</command> can then be used to change
+        user passwords without users seeing the "View" and "Status" menu 
+        buttons.</para></listitem>
+		</varlistentry>
+
+		&stdarg.server.debug;
+		&popt.common.samba;
+		&stdarg.help;
+
+	</variablelist>
+
+</refsect1>
+
+<refsect1>
+
+	<title>INSTALLATION</title>
+
+	<para>Swat is included as binary package with most distributions. The 
+	package manager in this case takes care of the installation and 
+	configuration. This section is only for those who have compiled 
+	swat from scratch.
+	</para>
+
+	<para>After you compile SWAT you need to run <command>make install
+	</command> to install the <command>swat</command> binary
+	and the various help files and images. A default install would put 
+	these in: </para>
+	
+	<itemizedlist>
+		<listitem><para>/usr/local/samba/sbin/swat</para></listitem>
+		<listitem><para>/usr/local/samba/swat/images/*</para></listitem>
+		<listitem><para>/usr/local/samba/swat/help/*</para></listitem>
+	</itemizedlist>
+
+	<refsect2> 
+		<title>Inetd Installation</title>
+
+		<para>You need to edit your <filename>/etc/inetd.conf
+		</filename> and <filename>/etc/services</filename>
+		to enable SWAT to be launched via <command>inetd</command>.</para>
+
+		<para>In <filename>/etc/services</filename> you need to 
+		add a line like this: </para>
+
+		<para><command>swat            901/tcp</command></para>
+
+		<para>Note for NIS/YP and LDAP users - you may need to rebuild the 
+		NIS service maps rather than alter your local <filename>
+		/etc/services</filename> file. </para>
+
+		<para>the choice of port number isn't really important 
+		except that it should be less than 1024 and not currently 
+		used (using a number above 1024 presents an obscure security 
+		hole depending on the implementation details of your 
+		<command>inetd</command> daemon). </para>
+
+		<para>In <filename>/etc/inetd.conf</filename> you should 
+		add a line like this: </para>
+
+		<para><command>swat    stream  tcp     nowait.400  root
+		/usr/local/samba/sbin/swat swat</command></para>
+	
+		<para>Once you have edited <filename>/etc/services</filename> 
+		and <filename>/etc/inetd.conf</filename> you need to send a 
+		HUP signal to inetd. To do this use <command>kill -1 PID
+		</command> where PID is the process ID of the inetd daemon. </para>
+
+	</refsect2>
+
+
+
+</refsect1>
+
+<refsect1>
+	<title>LAUNCHING</title>
+
+	<para>To launch SWAT just run your favorite web browser and 
+	point it at "http://localhost:901/".</para>
+
+	<para>Note that you can attach to SWAT from any IP connected 
+	machine but connecting from a remote machine leaves your 
+	connection open to password sniffing as passwords will be sent 
+	in the clear over the wire. </para>
+</refsect1>
+
+<refsect1>
+	<title>FILES</title>
+	
+	<variablelist>
+		<varlistentry>
+		<term><filename>/etc/inetd.conf</filename></term>
+		<listitem><para>This file must contain suitable startup 
+		information for the meta-daemon.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><filename>/etc/services</filename></term>
+		<listitem><para>This file must contain a mapping of service name 
+		(e.g., swat) to service port (e.g., 901) and protocol type 
+		(e.g., tcp).  </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><filename>/usr/local/samba/lib/smb.conf</filename></term>
+		<listitem><para>This is the default location of the <citerefentry>
+		<refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum>
+		</citerefentry> server configuration file that swat edits. Other 
+		common places that systems install this file are <filename>
+		/usr/samba/lib/smb.conf</filename> and <filename>/etc/smb.conf
+		</filename>.  This file describes all the services the server 
+		is to make available to clients. </para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>WARNINGS</title>
+
+	<para><command>swat</command> will rewrite your <citerefentry>
+	<refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum>
+	</citerefentry> file. It will rearrange the entries and delete all 
+	comments, <parameter>include=</parameter> and <parameter>copy=
+	</parameter> options. If you have a carefully crafted <filename>
+	smb.conf</filename> then back it up or don't use swat! </para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><command>inetd(5)</command>, <citerefentry>
+	<refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum>
+	</citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry></para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
+	Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/tdbbackup.8.xml b/docs-xml/manpages-3/tdbbackup.8.xml
new file mode 100644
index 00000000000..b1d6a21f3f4
--- /dev/null
+++ b/docs-xml/manpages-3/tdbbackup.8.xml
@@ -0,0 +1,136 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="tdbbackup.8">
+
+<refmeta>
+	<refentrytitle>tdbbackup</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>tdbbackup</refname>
+	<refpurpose>tool for backing up and for validating the integrity of samba .tdb files</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>tdbbackup</command>
+		<arg choice="opt">-s suffix</arg>
+		<arg choice="opt">-v</arg>
+		<arg choice="opt">-h</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> suite.</para>
+
+	<para><command>tdbbackup</command> is a tool that may be used to backup samba .tdb
+	files. This tool may also be used to verify the integrity of the .tdb files prior
+	to samba startup or during normal operation. If it finds file damage and it finds 
+	a prior backup the backup file will be restored. 
+	</para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>-h</term>
+		<listitem><para>
+		Get help information.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-s suffix</term>
+		<listitem><para>
+		The <command>-s</command> option allows the adminisistrator to specify a file
+		backup extension. This way it is possible to keep a history of tdb backup
+		files by using a new suffix for each backup.
+		</para> </listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-v</term>
+		<listitem><para>
+		The <command>-v</command> will check the database for damages (currupt data)
+		which if detected causes the backup to be restored.
+		</para></listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>COMMANDS</title>
+
+	<para><emphasis>GENERAL INFORMATION</emphasis></para>
+
+	<para>
+	The <command>tdbbackup</command> utility can safely be run at any time. It was designed so
+	that it can be used at any time to validate the integrity of tdb files, even during Samba
+	operation. Typical usage for the command will be:
+	</para>
+
+	<para>tdbbackup [-s suffix] *.tdb</para>
+
+	<para>
+	Before restarting samba the following command may be run to validate .tdb files:
+	</para>
+
+	<para>tdbbackup -v [-s suffix] *.tdb</para>
+
+	<para>
+	Samba .tdb files are stored in various locations, be sure to run backup all
+	.tdb file on the system. Important files includes:
+	</para>
+
+	<itemizedlist>
+		<listitem><para>
+		<command>secrets.tdb</command> - usual location is in the /usr/local/samba/private
+		directory, or on some systems in /etc/samba.
+		</para></listitem>
+
+		<listitem><para>
+		<command>passdb.tdb</command> - usual location is in the /usr/local/samba/private
+		directory, or on some systems in /etc/samba.
+		</para></listitem>
+
+		<listitem><para>
+		<command>*.tdb</command> located in the /usr/local/samba/var directory or on some
+		systems in the /var/cache or /var/lib/samba directories.
+		</para></listitem>
+	</itemizedlist>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>
+	The original Samba software and related utilities were created by Andrew Tridgell.
+	Samba is now developed by the Samba Team as an Open Source project similar to the way
+	the Linux kernel is developed.
+	</para> 
+
+	<para>The tdbbackup man page was written by John H Terpstra.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/tdbdump.8.xml b/docs-xml/manpages-3/tdbdump.8.xml
new file mode 100644
index 00000000000..94b6052e9c8
--- /dev/null
+++ b/docs-xml/manpages-3/tdbdump.8.xml
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="tdbdump.8">
+
+<refmeta>
+	<refentrytitle>tdbdump</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>tdbdump</refname>
+	<refpurpose>tool for printing the contents of a TDB file</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>tdbdump</command>
+		<arg choice="req">filename</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> suite.</para>
+
+	<para><command>tdbdump</command> is a very simple utility that 'dumps' the 
+		contents of a TDB (Trivial DataBase) file to standard output in a 
+		human-readable format.
+	</para>
+
+	<para>This tool can be used when debugging problems with TDB files. It is 
+		intended for those who are somewhat familiar with Samba internals.
+	</para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>
+	The original Samba software and related utilities were created by Andrew Tridgell.
+	Samba is now developed by the Samba Team as an Open Source project similar to the way
+	the Linux kernel is developed.
+	</para> 
+
+	<para>The tdbdump man page was written by Jelmer Vernooij.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/tdbtool.8.xml b/docs-xml/manpages-3/tdbtool.8.xml
new file mode 100644
index 00000000000..3f5dec4ecd8
--- /dev/null
+++ b/docs-xml/manpages-3/tdbtool.8.xml
@@ -0,0 +1,227 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="tdbtool.8">
+
+<refmeta>
+	<refentrytitle>tdbtool</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>tdbtool</refname>
+	<refpurpose>manipulate the contents TDB files</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+
+	<cmdsynopsis>
+		<command>tdbtool</command>
+	</cmdsynopsis>
+
+	<cmdsynopsis>
+		<command>tdbtool</command>
+		<arg choice="plain">
+		<replaceable>TDBFILE</replaceable>
+		</arg>
+		<arg rep="repeat" choice="opt">
+		<replaceable>COMMANDS</replaceable>
+		</arg>
+	</cmdsynopsis>
+
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> suite.</para>
+
+	<para><command>tdbtool</command> a tool for displaying and
+	altering the contents of Samba TDB (Trivial DataBase) files. Each
+	of the commands listed below can be entered interactively or
+	provided on the command line.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>COMMANDS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term><option>create</option>
+		<replaceable>TDBFILE</replaceable></term>
+		<listitem><para>Create a new database named
+		<replaceable>TDBFILE</replaceable>.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>open</option>
+		<replaceable>TDBFILE</replaceable></term>
+		<listitem><para>Open an existing database named
+		<replaceable>TDBFILE</replaceable>.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>erase</option></term>
+		<listitem><para>Erase the current database.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>dump</option></term>
+		<listitem><para>Dump the current database as strings.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>cdump</option></term>
+		<listitem><para>Dump the current database as connection records.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>keys</option></term>
+		<listitem><para>Dump the current database keys as strings.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>hexkeys</option></term>
+		<listitem><para>Dump the current database keys as hex values.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>info</option></term>
+		<listitem><para>Print summary information about the
+		current database.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>insert</option>
+		<replaceable>KEY</replaceable>
+		<replaceable>DATA</replaceable>
+		</term>
+		<listitem><para>Insert a record into the
+		current database.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>move</option>
+		<replaceable>KEY</replaceable>
+		<replaceable>TDBFILE</replaceable>
+		</term>
+		<listitem><para>Move a record from the 
+		current database into <replaceable>TDBFILE</replaceable>.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>store</option>
+		<replaceable>KEY</replaceable>
+		<replaceable>DATA</replaceable>
+		</term>
+		<listitem><para>Store (replace) a record in the
+		current database.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>show</option>
+		<replaceable>KEY</replaceable>
+		</term>
+		<listitem><para>Show a record by key.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>delete</option>
+		<replaceable>KEY</replaceable>
+		</term>
+		<listitem><para>Delete a record by key.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>list</option>
+		</term>
+		<listitem><para>Print the current database hash table and free list.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>free</option>
+		</term>
+		<listitem><para>Print the current database and free list.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term><option>!</option>
+		<replaceable>COMMAND</replaceable>
+		</term>
+		<listitem><para>Execute the given system command.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>
+		<option>first</option>
+		</term>
+		<listitem><para>Print the first record in the current database.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>
+		<option>next</option>
+		</term>
+		<listitem><para>Print the next record in the current database.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>
+		<option>quit</option>
+		</term>
+		<listitem><para>Exit <command>tdbtool</command>.
+		</para></listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>CAVEATS</title>
+	<para>The contents of the Samba TDB files are private
+	to the implementation and should not be altered with
+	<command>tdbtool</command>.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para> The original Samba software and related utilities were
+	created by Andrew Tridgell.  Samba is now developed by the
+	Samba Team as an Open Source project similar to the way the
+	Linux kernel is developed.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/testparm.1.xml b/docs-xml/manpages-3/testparm.1.xml
new file mode 100644
index 00000000000..f93b6e90c89
--- /dev/null
+++ b/docs-xml/manpages-3/testparm.1.xml
@@ -0,0 +1,210 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="testparm.1">
+
+<refmeta>
+	<refentrytitle>testparm</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>testparm</refname>
+	<refpurpose>check an smb.conf configuration file for 
+	internal correctness</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>testparm</command>
+		<arg choice="opt">-s</arg>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-v</arg>
+		<arg choice="opt">-L &lt;servername&gt;</arg>
+		<arg choice="opt">-t &lt;encoding&gt;</arg>
+		<arg choice="req">config filename</arg>
+		<arg choice="opt">hostname hostIP</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>testparm</command> is a very simple test program 
+	to check an <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> configuration file for 
+	internal correctness. If this program reports no problems, you 
+	can use the configuration file with confidence that <command>smbd
+	</command> will successfully load the configuration file.</para>
+
+
+	<para>Note that this is <emphasis>NOT</emphasis> a guarantee that 
+	the services specified in the configuration file will be 
+	available or will operate as expected. </para>
+
+	<para>If the optional host name and host IP address are 
+	specified on the command line, this test program will run through 
+	the service entries reporting whether the specified host
+	has access to each service. </para>
+
+	<para>If <command>testparm</command> finds an error in the <filename>
+	smb.conf</filename> file it returns an exit code of 1 to the calling 
+	program, else it returns an exit code of 0. This allows shell scripts 
+	to test the output from <command>testparm</command>.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-s</term>
+		<listitem><para>Without this option, <command>testparm</command> 
+		will prompt for a carriage return after printing the service 
+		names and before dumping the service definitions.</para></listitem>
+		</varlistentry>
+
+		&stdarg.help;
+		&stdarg.version;
+		
+		<varlistentry>
+		<term>-L servername</term>
+		<listitem><para>Sets the value of the %L macro to <replaceable>servername</replaceable>.
+		This is useful for testing include files specified with the 
+		%L macro. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-v</term>
+		<listitem><para>If this option is specified, testparm 
+		will also output all options that were not used in <citerefentry>
+		<refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum>
+		</citerefentry> and are thus set to their defaults.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-t encoding</term>
+		<listitem><para>
+		Output data in specified encoding.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--parameter-name parametername</term>
+		<listitem><para>
+		Dumps the named parameter.  If no section-name is set the view
+		is limited by default to the global section.
+
+		It is also possible to dump a parametrical option.  Therfore
+		the option has to be separated by a colon from the
+		parametername.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--section-name sectionname</term>
+		<listitem><para>
+		Dumps the named section.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>configfilename</term>
+		<listitem><para>This is the name of the configuration file 
+		to check. If this parameter is not present then the 
+		default <citerefentry><refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum>
+		</citerefentry> file will be checked. 	
+		</para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>hostname</term>
+		<listitem><para>If this parameter and the following are 
+		specified, then <command>testparm</command> will examine the <parameter>hosts
+		allow</parameter> and <parameter>hosts deny</parameter> 
+		parameters in the <citerefentry>
+		<refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum>
+		</citerefentry> file to 
+		determine if the hostname with this IP address would be
+		allowed access to the <command>smbd</command> server.  If 
+		this parameter is supplied, the hostIP parameter must also
+		be supplied.</para></listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>hostIP</term>
+		<listitem><para>This is the IP address of the host specified 
+		in the previous parameter.  This address must be supplied 
+		if the hostname parameter is supplied. </para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>FILES</title>
+
+	<variablelist>
+		<varlistentry>
+		<term><citerefentry><refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum>
+		</citerefentry></term>
+		<listitem><para>This is usually the name of the configuration 
+		file used by <citerefentry><refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum>
+		</citerefentry>. 
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>DIAGNOSTICS</title>
+
+	<para>The program will issue a message saying whether the 
+	configuration file loaded OK or not. This message may be preceded by 
+	errors and warnings if the file did not load. If the file was 
+	loaded OK, the program then dumps all known service details 
+	to stdout. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of 
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry>
+		<refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum>
+		</citerefentry>, <citerefentry>
+		<refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum>
+		</citerefentry></para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>
+	
+	<para>The original Samba man pages were written by Karl Auer. 
+	The man page sources were converted to YODL format (another 
+	excellent piece of Open Source software, available at <ulink noescape="1" url="ftp://ftp.icce.rug.nl/pub/unix/">
+	ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 
+	release by Jeremy Allison.  The conversion to DocBook for 
+	Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
+	for Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/umount.cifs.8.xml b/docs-xml/manpages-3/umount.cifs.8.xml
new file mode 100644
index 00000000000..38ce24228dc
--- /dev/null
+++ b/docs-xml/manpages-3/umount.cifs.8.xml
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="umount.cifs.8">
+
+<refmeta>
+	<refentrytitle>umount.cifs</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>umount.cifs</refname>
+	<refpurpose>for normal, non-root users, to unmount their own Common Internet File System (CIFS) mounts</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+
+		<command>umount.cifs</command>
+		<arg choice="req">mount-point</arg>	
+		<arg choice="opt">-nVvhfle</arg>	
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>umount.cifs unmounts a Linux CIFS filesystem. It can be invoked
+indirectly by the
+<citerefentry><refentrytitle>umount</refentrytitle><manvolnum>8</manvolnum></citerefentry> command 
+when umount.cifs is in /sbin directory, unless you specify the "-i" option to umount.  Specifying -i to umount avoids execution of umount helpers such as umount.cifs. The umount.cifs command only works in Linux, and the kernel must
+support the cifs filesystem. The CIFS protocol is the successor to the 
+SMB protocol and is supported by most Windows servers and many other
+commercial servers and Network Attached Storage appliances as well as 
+by the popular Open Source server Samba.
+	</para>
+
+	<para>
+	The umount.cifs utility detaches the local directory <emphasis>mount-point</emphasis> from the corresponding UNC name (exported network resource) and frees the associated kernel resources.
+It is possible to set the mode for umount.cifs to 
+setuid root (or equivalently update the /etc/permissions file) to allow non-root users to umount shares to directories for which they have write permission.  The umount.cifs utility is typically
+not needed if unmounts need only be performed by root users, or if user mounts and unmounts
+can rely on specifying explicit entries in /etc/fstab See</para>
+        <para><citerefentry><refentrytitle>fstab</refentrytitle>
+        <manvolnum>5</manvolnum></citerefentry></para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+	<variablelist>
+        <varlistentry>
+                <term>--verbose</term>
+                <listitem><para>print additional debugging information</para></listitem>
+        </varlistentry>
+        <varlistentry>
+                <term>--no-mtab</term>
+                <listitem><para>Do not update the mtab even if unmount completes successfully (/proc/mounts will still display the correct information)</para></listitem>
+        </varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>NOTES</title>
+	
+	<para>This command is normally intended to be installed setuid (since root users can already run unmount).  An alternative to using umount.cifs is to add specfic entries for the user mounts that you wish a particular user or users to mount and unmount to /etc/fstab</para>
+</refsect1>
+
+<refsect1>
+	<title>CONFIGURATION</title>
+		<para>
+The primary mechanism for making configuration changes and for reading 
+debug information for the cifs vfs is via the Linux /proc filesystem.
+In the directory <filename>/proc/fs/cifs</filename> are various 
+configuration files and pseudo files which can display debug information.  
+For more information see the kernel file <filename>fs/cifs/README</filename>.
+</para>
+</refsect1>
+
+<refsect1>
+	<title>BUGS</title>
+
+	<para>At this time umount.cifs does not lock the mount table using the same lock as the umount utility does, so do not attempt to do multiple unmounts from different processes (and in particular unmounts of a cifs mount and another type of filesystem mount at the same time).
+	</para>
+
+	<para>If the same mount point is mounted multiple times by cifs, umount.cifs will remove all of the matching entries from the mount table (although umount.cifs will actually only unmount the last one), rather than only removing the last matching entry in /etc/mtab.  The pseudofile /proc/mounts will display correct information though, and the lack of an entry in /etc/mtab does not prevent subsequent unmounts.</para>
+
+	<para>
+Note that the typical response to a bug report is a suggestion
+to try the latest version first. So please try doing that first,
+and always include which versions you use of relevant software
+when reporting bugs (minimum: umount.cifs (try umount.cifs -V), kernel (see /proc/version) and
+server type you are trying to contact.
+</para>
+</refsect1>
+
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 1.34 of 
+	the cifs vfs filesystem (roughly Linux kernel 2.6.12).</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para>
+	Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel
+	source tree may contain additional options and information.
+</para>
+        <para><citerefentry><refentrytitle>mount.cifs</refentrytitle>
+        <manvolnum>8</manvolnum></citerefentry></para>
+
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+	
+	<para>Steve French</para>
+
+	<para>The syntax was loosely based on the umount utility and the manpage was loosely based on that of mount.cifs.8. The man page was created by Steve French</para> 
+	<para>The maintainer of the Linux cifs vfs and the userspace
+		tool <emphasis>umount.cifs</emphasis> is <ulink url="mailto:sfrench@samba.org">Steve French</ulink>.
+		The <ulink url="mailto:linux-cifs-client@lists.samba.org">Linux CIFS Mailing list</ulink> 
+		is the preferred place to ask questions regarding these programs. 
+	</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_audit.8.xml b/docs-xml/manpages-3/vfs_audit.8.xml
new file mode 100644
index 00000000000..ce2c3e4bd0b
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_audit.8.xml
@@ -0,0 +1,122 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_audit.8">
+
+<refmeta>
+	<refentrytitle>vfs_audit</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_audit</refname>
+	<refpurpose>record selected Samba VFS operations in the system log</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = audit</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_audit</command> VFS module records selected
+	client operations to the system log using
+	<citerefentry><refentrytitle>syslog</refentrytitle>
+	<manvolnum>3</manvolnum></citerefentry>.</para>
+
+	<para>The following Samba VFS operations are recorded:</para>
+	<simplelist>
+	<member>connect</member>
+	<member>disconnect</member>
+	<member>opendir</member>
+	<member>mkdir</member>
+	<member>rmdir</member>
+	<member>open</member>
+	<member>close</member>
+	<member>rename</member>
+	<member>unlink</member>
+	<member>chmod</member>
+	<member>fchmod</member>
+	<member>chmod_acl</member>
+	<member>fchmod_acl</member>
+	</simplelist>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>audit:facility = FACILITY</term>
+		<listitem>
+		<para>Log messages to the named
+		<citerefentry><refentrytitle>syslog</refentrytitle>
+		<manvolnum>3</manvolnum></citerefentry> facility.
+
+		</para>
+
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>audit:priority = PRIORITY</term>
+		<listitem>
+		<para>Log messages with the named
+		<citerefentry><refentrytitle>syslog</refentrytitle>
+		<manvolnum>3</manvolnum></citerefentry> priority.
+		</para>
+
+		</listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Log operations on all shares using the LOCAL1 facility
+	and NOTICE priority:</para>
+
+<programlisting>
+        <smbconfsection name="[global]"/>
+	<smbconfoption name="vfs objects">audit</smbconfoption>
+	<smbconfoption name="audit:facility">LOCAL1</smbconfoption>
+	<smbconfoption name="audit:priority">NOTICE</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_cacheprime.8.xml b/docs-xml/manpages-3/vfs_cacheprime.8.xml
new file mode 100644
index 00000000000..0249ac27b8a
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_cacheprime.8.xml
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_cacheprime.8">
+
+<refmeta>
+	<refentrytitle>vfs_cacheprime</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_cacheprime</refname>
+	<refpurpose>prime the kernel file data cache</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = cacheprime</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_cacheprime</command> VFS module reads chunks
+	of file data near the range requested by clients in order to
+	make sure the data is present in the kernel file data cache at
+	the time when it is actually requested by clients. </para>
+
+	<para>The size of the disk read operations performed
+	by <command>vfs_cacheprime</command> is determined by the
+	cacheprime:rsize option. All disk read operations are aligned
+	on boundaries that are a multiple of this size. Each range of
+	the file data is primed at most once during the time the client
+	has the file open. </para>
+
+	<para>This module is stackable.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>cacheprime:rsize = BYTES</term>
+		<listitem>
+		<para>The number of bytes with which to prime
+		the kernel data cache.</para>
+		<para>The following suffixes may be applied to BYTES:</para>
+		<itemizedlist>
+		<listitem><para><command>K</command> - BYTES is a number of kilobytes</para></listitem>
+		<listitem><para><command>M</command> - BYTES is a number of megabytes</para></listitem>
+		<listitem><para><command>G</command> - BYTES is a number of gigabytes</para></listitem>
+		</itemizedlist>
+
+		</listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>For a hypothetical disk array, it is necessary to ensure
+	that all read operations are of size 1 megabyte (1048576 bytes),
+	and aligned on 1 megabyte boundaries:
+	</para>
+<programlisting>
+	<smbconfsection name="[hypothetical]"/>
+	<smbconfoption name="vfs objects">cacheprime</smbconfoption>
+	<smbconfoption name="cacheprime:rsize">1M</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>CAVEATS</title>
+	<para><command>cacheprime</command> is not a a substitute for
+	a general-purpose readahead mechanism. It is intended for use
+	only in very specific environments where disk operations must
+	be aligned and sized to known values (as much as that is possible).
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_cap.8.xml b/docs-xml/manpages-3/vfs_cap.8.xml
new file mode 100644
index 00000000000..93dab4a196e
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_cap.8.xml
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_cap.8">
+
+<refmeta>
+	<refentrytitle>vfs_cap</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_cap</refname>
+	<refpurpose>CAP encode filenames</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = cap</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>CAP (Columbia Appletalk Protocol) encoding is a
+	technique for representing non-ASCII filenames in ASCII. The
+	<command>vfs_cap</command> VFS module translates filenames to and
+	from CAP format, allowing users to name files in their native
+	encoding.  </para>
+
+	<para>CAP encoding is most commonly
+	used in Japanese language environments. </para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>On a system using GNU libiconv, use CAP encoding to support
+	users in the Shift_JIS locale:</para>
+
+<programlisting>
+        <smbconfsection name="[global]"/>
+	<smbconfoption name="dos charset">CP932</smbconfoption>
+	<smbconfoption name="dos charset">CP932</smbconfoption>
+	<smbconfoption name="vfs objects">cap</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_catia.8.xml b/docs-xml/manpages-3/vfs_catia.8.xml
new file mode 100644
index 00000000000..736aee00a8c
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_catia.8.xml
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_catia.8">
+
+<refmeta>
+	<refentrytitle>vfs_catia</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_catia</refname>
+	<refpurpose>translate illegal characters in Catia filenames</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = catia</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The Catia CAD package commonly creates filenames that
+	use characters that are illegal in CIFS filenames. The
+	<command>vfs_catia</command> VFS module implements a fixed character
+	mapping so that these files can be shared with CIFS clients.
+	</para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Map Catia filenames on the [CAD] share:</para>
+
+<programlisting>
+        <smbconfsection name="[CAD]"/>
+	<smbconfoption name="path">/data/cad</smbconfoption>
+	<smbconfoption name="vfs objects">catia</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_commit.8.xml b/docs-xml/manpages-3/vfs_commit.8.xml
new file mode 100644
index 00000000000..ab2d234baaa
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_commit.8.xml
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_commit.8">
+
+<refmeta>
+	<refentrytitle>vfs_commit</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_commit</refname>
+	<refpurpose>flush dirty data at specified intervals</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = commit</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_commit</command> VFS module keeps track of
+	the amount of data written to a file and synchronizes it to
+	disk when a specified amount accumulates.
+	</para>
+
+	<para><command>vfs_commit</command> is useful in two
+	circumstances. First, if you have very precious data, the
+	impact of unexpected power loss can be minimized by a small
+	commit:dthresh value. Secondly, write performance can be
+	improved on some systems by flushing file data early and at
+	regular intervals.</para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>commit:dthresh = BYTES</term>
+		<listitem>
+		<para>Synchronize file data each time the specified
+		number of bytes has been written.
+		</para>
+
+		<para>The following suffixes may be applied to BYTES:</para>
+		<itemizedlist>
+		<listitem><para><command>K</command> - BYTES is a number of kilobytes</para></listitem>
+		<listitem><para><command>M</command> - BYTES is a number of megabytes</para></listitem>
+		<listitem><para><command>G</command> - BYTES is a number of gigabytes</para></listitem>
+		</itemizedlist>
+
+		</listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Synchronize the file data on the [precious] share after
+	every 512 kilobytes (524288 bytes) of data is written:</para>
+<programlisting>
+        <smbconfsection name="[precious]"/>
+	<smbconfoption name="path">/data/precious</smbconfoption>
+	<smbconfoption name="vfs objects">commit</smbconfoption>
+	<smbconfoption name="commit:dthresh">512K</smbconfoption>
+</programlisting>
+</refsect1>
+
+<refsect1>
+	<title>CAVEATS</title>
+	<para>On some systems, the data synchronization performed by
+	<command>commit</command> may reduce performance.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_default_quota.8.xml b/docs-xml/manpages-3/vfs_default_quota.8.xml
new file mode 100644
index 00000000000..28d2413a7db
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_default_quota.8.xml
@@ -0,0 +1,136 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_default_quota.8">
+
+<refmeta>
+	<refentrytitle>vfs_default_quota</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_default_quota</refname>
+	<refpurpose>store default quota records for Windows clients</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = default_quota</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry>
+	suite.</para>
+
+	<para>Many common quota implementations only store
+	quotas for users and groups, but do not store a default quota. The
+	<command>vfs_default_quota</command> module allows Samba to store
+	default quota values which can be examined using the Windows
+	Explorer interface.
+	</para>
+
+	<para>By default, Samba returns NO_LIMIT the default quota and
+	refuses to update them. <command>vfs_default_quota</command> maps
+	the default quota to the quota record of a user. By default the
+	root user is taken because quota limits for root are typically
+	not enforced.</para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>default_quota:uid = UID</term>
+		<listitem>
+		<para>UID specifies the user ID of the quota record where the
+		default user quota values are stored.
+		</para>
+
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>default_quota:gid = GID</term>
+		<listitem>
+		<para>GID specifies the group ID of the quota record where the
+		default group quota values are stored.
+		</para>
+
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>default_quota:uid nolimit = BOOL</term>
+		<listitem>
+		<para>If this parameter is True, then the user whose
+		quota record is storing the default user quota will
+		be reported as having a quota of NO_LIMIT. Otherwise,
+		the stored values will be reported.
+		</para>
+
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>default_quota:gid nolimit = BOOL</term>
+		<listitem>
+		<para>If this parameter is True, then the group whose
+		quota record is storing the default group quota will
+		be reported as having a quota of NO_LIMIT. Otherwise,
+		the stored values will be reported.
+		</para>
+
+		</listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Store the default quota record in the quota record for
+	the user with ID 65535 and report that user as having no quota
+	limits:</para>
+
+<programlisting>
+        <smbconfsection name="[global]"/>
+	<smbconfoption name="vfs objects">default_quota</smbconfoption>
+	<smbconfoption name="default_quota:uid">65535</smbconfoption>
+	<smbconfoption name="default_quota:uid nolimit">yes</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_extd_audit.8.xml b/docs-xml/manpages-3/vfs_extd_audit.8.xml
new file mode 100644
index 00000000000..0e12bd1b1d9
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_extd_audit.8.xml
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_extd_audit.8">
+
+<refmeta>
+	<refentrytitle>vfs_extd_audit</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_extd_audit</refname>
+	<refpurpose>record selected Samba VFS operations</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = extd_audit</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>extd_audit</command> VFS module records selected
+	client operations to both the
+	<citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> log and
+	system log (using
+	<citerefentry><refentrytitle>syslog</refentrytitle>
+	<manvolnum>3</manvolnum></citerefentry>).</para>
+
+	<para>Other than logging to the
+	<citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> log,
+	<command>vfs_extd_audit</command> is identical to
+	<citerefentry><refentrytitle>vfs_audit</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>.
+	</para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_fake_perms.8.xml b/docs-xml/manpages-3/vfs_fake_perms.8.xml
new file mode 100644
index 00000000000..87279bee2a1
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_fake_perms.8.xml
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_fake_perms.8">
+
+<refmeta>
+	<refentrytitle>vfs_fake_perms</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_fake_perms</refname>
+	<refpurpose>enable read only Roaming Profiles</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = fake_perms</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_fake_perms</command> VFS module was created
+	to allow Roaming Profile files and directories to be set (on
+	the Samba server under UNIX) as read only. This module will,
+	if installed on the Profiles share, report to the client that
+	the Profile files and directories are writeable. This satisfies
+	the client even though the files will never be overwritten as
+	the client logs out or shuts down.
+	</para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+<programlisting>
+        <smbconfsection name="[Profiles]"/>
+	<smbconfoption name="path">/profiles</smbconfoption>
+	<smbconfoption name="vfs objects">fake_perms</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_full_audit.8.xml b/docs-xml/manpages-3/vfs_full_audit.8.xml
new file mode 100644
index 00000000000..eec3f3127ce
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_full_audit.8.xml
@@ -0,0 +1,266 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_full_audit.8">
+
+<refmeta>
+	<refentrytitle>vfs_full_audit</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_full_audit</refname>
+	<refpurpose>record Samba VFS operations in the system log</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = full_audit</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_full_audit</command> VFS module records selected
+	client operations to the system log using
+	<citerefentry><refentrytitle>syslog</refentrytitle>
+	<manvolnum>3</manvolnum></citerefentry>.</para>
+
+	<para><command>vfs_full_audit</command> is able to record the
+	complete set of Samba VFS operations:</para>
+
+	<simplelist>
+        <member>aio_cancel</member>
+        <member>aio_error</member>
+        <member>aio_fsync</member>
+        <member>aio_read</member>
+        <member>aio_return</member>
+        <member>aio_suspend</member>
+        <member>aio_write</member>
+        <member>chdir</member>
+        <member>chflags</member>
+        <member>chmod</member>
+        <member>chmod_acl</member>
+        <member>chown</member>
+        <member>close</member>
+        <member>closedir</member>
+        <member>connect</member>
+        <member>disconnect</member>
+        <member>disk_free</member>
+        <member>fchmod</member>
+        <member>fchmod_acl</member>
+        <member>fchown</member>
+        <member>fget_nt_acl</member>
+        <member>fgetxattr</member>
+        <member>flistxattr</member>
+        <member>fremovexattr</member>
+        <member>fset_nt_acl</member>
+        <member>fsetxattr</member>
+        <member>fstat</member>
+        <member>fsync</member>
+        <member>ftruncate</member>
+        <member>get_nt_acl</member>
+        <member>get_quota</member>
+        <member>get_shadow_copy_data</member>
+        <member>getlock</member>
+        <member>getwd</member>
+        <member>getxattr</member>
+        <member>kernel_flock</member>
+        <member>lgetxattr</member>
+        <member>link</member>
+        <member>linux_setlease</member>
+        <member>listxattr</member>
+        <member>llistxattr</member>
+        <member>lock</member>
+        <member>lremovexattr</member>
+        <member>lseek</member>
+        <member>lsetxattr</member>
+        <member>lstat</member>
+        <member>mkdir</member>
+        <member>mknod</member>
+        <member>open</member>
+        <member>opendir</member>
+        <member>pread</member>
+        <member>pwrite</member>
+        <member>read</member>
+        <member>readdir</member>
+        <member>readlink</member>
+        <member>realpath</member>
+        <member>removexattr</member>
+        <member>rename</member>
+        <member>rewinddir</member>
+        <member>rmdir</member>
+        <member>seekdir</member>
+        <member>sendfile</member>
+        <member>set_nt_acl</member>
+        <member>set_quota</member>
+        <member>setxattr</member>
+        <member>stat</member>
+        <member>statvfs</member>
+        <member>symlink</member>
+        <member>sys_acl_add_perm</member>
+        <member>sys_acl_clear_perms</member>
+        <member>sys_acl_create_entry</member>
+        <member>sys_acl_delete_def_file</member>
+        <member>sys_acl_free_acl</member>
+        <member>sys_acl_free_qualifier</member>
+        <member>sys_acl_free_text</member>
+        <member>sys_acl_get_entry</member>
+        <member>sys_acl_get_fd</member>
+        <member>sys_acl_get_file</member>
+        <member>sys_acl_get_perm</member>
+        <member>sys_acl_get_permset</member>
+        <member>sys_acl_get_qualifier</member>
+        <member>sys_acl_get_tag_type</member>
+        <member>sys_acl_init</member>
+        <member>sys_acl_set_fd</member>
+        <member>sys_acl_set_file</member>
+        <member>sys_acl_set_permset</member>
+        <member>sys_acl_set_qualifier</member>
+        <member>sys_acl_set_tag_type</member>
+        <member>sys_acl_to_text</member>
+        <member>sys_acl_valid</member>
+        <member>telldir</member>
+        <member>unlink</member>
+        <member>utime</member>
+        <member>write</member>
+	</simplelist>
+
+	<para>In addition to these operations,
+	<command>vfs_full_audit</command> recognizes the special operation
+	names &quot;all&quot; and &quot;none &quot;, which refer to all
+	the VFS operations and none of the VFS operations respectively.
+	</para>
+
+	<para><command>vfs_full_audit</command> records operations in fixed
+	format consisting of fields separated by '|' characters. The
+	format is: </para>
+	<programlisting>
+		smbd_audit: PREFIX|OPERATION|RESULT|FILE
+	</programlisting>
+
+	<para>The record fields are:</para>
+
+	<itemizedlist>
+	<listitem><para><command>PREFIX</command> - the result of the full_audit:prefix string after variable substitutions</para></listitem>
+	<listitem><para><command>OPERATION</command> - the name of the VFS operation</para></listitem>
+	<listitem><para><command>RESULT</command> - whether the operation succeeded or failed</para></listitem>
+	<listitem><para><command>FILE</command> - the name of the file or directory the operation was performed on</para></listitem>
+
+	</itemizedlist>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>vfs_full_audit:prefix = STRING</term>
+		<listitem>
+		<para>Prepend audit messages with STRING. STRING is
+		processed for standard substitution variables listed in
+		<citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry>. The default
+		prefix is &quot;%u|%I&quot;. </para>
+
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>vfs_full_audit:success = LIST</term>
+		<listitem>
+		<para>LIST is a list of VFS operations that should be
+		recorded if they succeed. Operations are specified using
+		the names listed above.
+		</para>
+
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>vfs_full_audit:failure = LIST</term>
+		<listitem>
+		<para>LIST is a list of VFS operations that should be
+		recorded if they failed. Operations are specified using
+		the names listed above.
+		</para>
+
+		</listitem>
+		</varlistentry>
+
+                <varlistentry>
+                <term>full_audit:facility = FACILITY</term>
+                <listitem>
+                <para>Log messages to the named
+                <citerefentry><refentrytitle>syslog</refentrytitle>
+                <manvolnum>3</manvolnum></citerefentry> facility.
+
+                </para>
+
+                </listitem>
+                </varlistentry>
+
+                <varlistentry>
+                <term>full_audit:priority = PRIORITY</term>
+                <listitem>
+                <para>Log messages with the named
+                <citerefentry><refentrytitle>syslog</refentrytitle>
+                <manvolnum>3</manvolnum></citerefentry> priority.
+                </para>
+
+                </listitem>
+                </varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Log file and directory open operations on the [records]
+	share using the LOCAL7 facility and ALERT priority, including
+	the username and IP address:</para>
+
+<programlisting>
+        <smbconfsection name="[records]"/>
+	<smbconfoption name="path">/data/records</smbconfoption>
+	<smbconfoption name="vfs objects">full_audit</smbconfoption>
+	<smbconfoption name="full_audit:prefix">%u|%I</smbconfoption>
+	<smbconfoption name="full_audit:success">open opendir</smbconfoption>
+	<smbconfoption name="full_audit:failure">all</smbconfoption>
+	<smbconfoption name="full_audit:facility">LOCAL7</smbconfoption>
+	<smbconfoption name="full_audit:priority">ALERT</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_gpfs.8.xml b/docs-xml/manpages-3/vfs_gpfs.8.xml
new file mode 100644
index 00000000000..f926ecacf90
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_gpfs.8.xml
@@ -0,0 +1,164 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_gpfs.8">
+
+<refmeta>
+	<refentrytitle>vfs_gpfs</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_gpfs</refname>
+	<refpurpose>gpfs specific samba extensions like acls and prealloc</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = gpfs</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>gpfs</command> VFS module is the home
+	for all gpfs extensions that Samba requires for proper integration
+	with GPFS. It uses the GPL library interfaces provided by GPFS.
+	</para>
+
+	<para>Currently the gpfs vfs module provides extensions in following areas :
+	<itemizedlist>
+	<listitem><para>NFSv4 ACL Interfaces with configurable options for GPFS</para></listitem>
+	<listitem><para>Kernel oplock support on GPFS</para></listitem>
+	<listitem><para>Lease support on GPFS</para></listitem>
+	</itemizedlist>
+	</para>
+
+	<para><command>NOTE:</command>This module follows the posix-acl behaviour
+	and hence allows permission stealing via chown. Samba might allow at a later
+	point in time, to restrict the chown via this module as such restrictions
+	are the responsibility of the underlying filesystem than of Samba.
+	</para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+
+		<term>nfs4:mode = [ simple | special ]</term>
+		<listitem>
+		<para>
+		Enable/Disable substitution of special IDs on GPFS. This parameter
+		should not affect the windows users in anyway. It only ensures that Samba
+		sets the special IDs - OWNER@ and GROUP@ ( mappings to simple uids )
+		that are relevant to GPFS.
+		</para>
+
+		<para>The following MODEs are understood by the module:</para>
+		<itemizedlist>
+		<listitem><para><command>simple(default)</command> - do not use special IDs in GPFS ACEs</para></listitem>
+		<listitem><para><command>special</command> - use special IDs in GPFS ACEs. </para> </listitem>
+		</itemizedlist>
+		</listitem>
+
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>nfs4:acedup = [dontcare|reject|ignore|merge]</term>
+		<listitem>
+		<para>
+		This parameter configures how Samba handles duplicate ACEs encountered in GPFS ACLs.
+		GPFS allows/creates duplicate ACE for different bits for same ID.
+		</para>
+
+		<para>Following is the behaviour of Samba for different values :</para>
+		<itemizedlist>
+		<listitem><para><command>dontcare (default)</command> - copy the ACEs as they come</para></listitem>
+		<listitem><para><command>reject</command> - stop operation and exit with error on ACL set op</para></listitem>
+		<listitem><para><command>ignore</command> - don't include the second matching ACE</para></listitem>
+		<listitem><para><command>merge</command> - bitwise OR the 2 ace.flag fields and 2 ace.mask fields of the 2 duplicate ACEs into 1 ACE</para></listitem>
+		</itemizedlist>
+		</listitem>
+		</varlistentry>
+
+
+		<varlistentry>
+		<term>nfs4:chown = [yes|no]</term>
+		<listitem>
+		<para>This parameter allows enabling or disabling the chown supported
+		by the underlying filesystem. This parameter should be enabled with
+		care as it might leave your system insecure.</para>
+		<para>Some filesystems allow chown as a) giving b) stealing. It is the latter
+		that is considered a risk.</para>
+
+		<para>Following is the behaviour of Samba for different values : </para>
+		<itemizedlist>
+		<listitem><para><command>yes</command> - Enable chown if as supported by the under filesystem</para></listitem>
+		<listitem><para><command>no (default)</command> - Disable chown</para></listitem>
+		</itemizedlist>
+		</listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>A GPFS mount can be exported via Samba as follows :</para>
+
+<programlisting>
+        <smbconfsection name="[samba_gpfs_share]"/>
+	<smbconfoption name="vfs objects">gpfs</smbconfoption>
+	<smbconfoption name="path">/test/gpfs_mount</smbconfoption>
+	<smbconfoption name="nfs4: mode">special</smbconfoption>
+	<smbconfoption name="nfs4: acedup">merge</smbconfoption>
+</programlisting>
+</refsect1>
+
+<refsect1>
+	<title>CAVEATS</title>
+	<para>The gpfs gpl libraries are required by <command>gpfs</command> VFS
+	module during both compilation and runtime.
+	Also this VFS module is tested to work on SLES 9/10 and RHEL 4.4
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+	<para>The GPFS VFS module was created with contributions from
+	Volker Lendecke and the developers at IBM.
+	</para>
+
+	<para> This manpage was created by the IBM FSCC team </para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_netatalk.8.xml b/docs-xml/manpages-3/vfs_netatalk.8.xml
new file mode 100644
index 00000000000..e4f6772a7b9
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_netatalk.8.xml
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_netatalk.8">
+
+<refmeta>
+	<refentrytitle>vfs_netatalk</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_netatalk</refname>
+	<refpurpose>hide .AppleDouble files from CIFS clients</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = netatalk</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_netatalk</command> VFS module dynamically
+	hides .AppleDouble files, preventing spurious errors on some
+	CIFS clients. .AppleDouble files may be created by historic
+	implementations of AFP (Apple Filing Protocol) on servers. </para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Hide .AppleDouble files on the [data] share:</para>
+<programlisting>
+        <smbconfsection name="[data]"/>
+	<smbconfoption name="vfs objects">netatalk</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>CAVEATS</title>
+	<para>This module is largely historic and unlikely to be of use
+	in modern networks since current Apple systems are able to mount CIFS
+	shares natively.
+	</para>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_notify_fam.8.xml b/docs-xml/manpages-3/vfs_notify_fam.8.xml
new file mode 100644
index 00000000000..10605753c85
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_notify_fam.8.xml
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_notify_fam.8">
+
+<refmeta>
+	<refentrytitle>vfs_notify_fam</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_notify_fam</refname>
+	<refpurpose>FAM support for file change notifications</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = notify_fam</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_notify_fam</command> module makes use of
+	the system FAM (File Alteration Monitor) daemon to implement
+	file change notifications for Windows clients. FAM is generally
+	present only on IRIX and some BSD systems.</para>
+
+	<para>This module is not stackable.</para>
+
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Support FAM notifications globally:</para>
+
+<programlisting>
+        <smbconfsection name="[global]"/>
+	<smbconfoption name="vfs objects">notify_fam</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_prealloc.8.xml b/docs-xml/manpages-3/vfs_prealloc.8.xml
new file mode 100644
index 00000000000..36cc2894f3b
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_prealloc.8.xml
@@ -0,0 +1,107 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_prealloc.8">
+
+<refmeta>
+	<refentrytitle>vfs_prealloc</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_prealloc</refname>
+	<refpurpose>preallocate matching files to a predetermined size</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = prealloc</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_prealloc</command> VFS module preallocates
+	files to a specified size each time a new file is created. This
+	is useful in environments where files are of a predetermined
+	size will be written to a disk subsystem where extending file
+	allocations is expensive.  </para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>prealloc:EXT = BYTES</term>
+		<listitem>
+		<para>Preallocate all files with the extension EXT to
+		the size specified by BYTES.
+		</para>
+
+		<para>The following suffixes may be applied to BYTES:</para>
+		<itemizedlist>
+		<listitem><para><command>K</command> - BYTES is a number of kilobytes</para></listitem>
+		<listitem><para><command>M</command> - BYTES is a number of megabytes</para></listitem>
+		<listitem><para><command>G</command> - BYTES is a number of gigabytes</para></listitem>
+		</itemizedlist>
+
+		</listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>A process writes TIFF files to a Samba share, and the
+	is known these files will almost always be around 4 megabytes
+	(4194304 bytes): </para>
+
+<programlisting>
+        <smbconfsection name="[frames]"/>
+	<smbconfoption name="path">/data/frames</smbconfoption>
+	<smbconfoption name="vfs objects">prealloc</smbconfoption>
+	<smbconfoption name="prealloc:tiff">4M</smbconfoption>
+</programlisting>
+</refsect1>
+
+<refsect1>
+	<title>CAVEATS</title>
+	<para><command>vfs_prealloc</command> is not supported on all
+	platforms and filesystems. Currently only XFS filesystems on
+	Linux and IRIX are supported.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_readahead.8.xml b/docs-xml/manpages-3/vfs_readahead.8.xml
new file mode 100644
index 00000000000..0f4bd6aa501
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_readahead.8.xml
@@ -0,0 +1,115 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_readahead.8">
+
+<refmeta>
+	<refentrytitle>vfs_readahead</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_readahead</refname>
+	<refpurpose>pre-load the kernel buffer cache</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = readahead</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>This <command>vfs_readahead</command> VFS module detects
+	read requests at multiples of a given offset (hex 0x80000 by
+	default) and then tells the kernel via either the readahead
+	system call (on Linux) or the posix_fadvise system call to
+	pre-fetch this data into the buffer cache.</para>
+
+	<para>This module is useful for Windows Vista clients reading
+	data using the Windows Explorer program, which asynchronously
+	does multiple file read requests at offset boundaries of 0x80000
+	bytes.</para>
+
+	<para>The offset multiple used is given by the readahead:offset
+	option, which defaults to 0x80000.</para>
+
+	<para>The size of the disk read operations performed
+	by <command>vfs_readahead</command> is determined by the
+	readahead:length option. By default this is set to the
+	same value as the readahead:offset option and if not
+	set explicitly will use the current value of
+	readahead:offset.</para>
+
+	<para>This module is stackable.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>readahead:offset = BYTES</term>
+		<listitem>
+		<para>The offset multiple that causes readahead to be
+		requested of the kernel buffer cache.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>readahead:length = BYTES</term>
+		<listitem>
+		<para>The number of bytes requested to be
+		read into the kernel buffer cache on each
+		readahead call.</para>
+		</listitem>
+		</varlistentry>
+
+		<para>The following suffixes may be applied to BYTES:</para>
+		<itemizedlist>
+		<listitem><para><command>K</command> - BYTES is a number of kilobytes</para></listitem>
+		<listitem><para><command>M</command> - BYTES is a number of megabytes</para></listitem>
+		<listitem><para><command>G</command> - BYTES is a number of gigabytes</para></listitem>
+		</itemizedlist>
+
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+<programlisting>
+	<smbconfsection name="[hypothetical]"/>
+	<smbconfoption name="vfs objects">readahead</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_readonly.8.xml b/docs-xml/manpages-3/vfs_readonly.8.xml
new file mode 100644
index 00000000000..1d3d979cb03
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_readonly.8.xml
@@ -0,0 +1,101 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_readonly.8">
+
+<refmeta>
+	<refentrytitle>vfs_readonly</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_readonly</refname>
+	<refpurpose>make a Samba share read only for a specified time period</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = readonly</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_readonly</command> VFS module marks a share
+	as read only for all clients connecting within the configured
+	time period. Clients connecting during this time will be denied
+	write access to all files in the share, irrespective of ther
+	actual access privileges.</para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>readonly:period = BEGIN, END</term>
+		<listitem>
+		<para>Only mark the share as read only if the client
+		connection was made between the times marked by the
+		BEGIN and END date specifiers.
+		The syntax of these date specifiers is the
+		same as that accepted by the -d option of GNU
+		<citerefentry><refentrytitle>date</refentrytitle>
+			<manvolnum>1</manvolnum></citerefentry>.
+		</para>
+
+		</listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Mark all shares read only:</para>
+<programlisting>
+        <smbconfsection name="[global]"/>
+	<smbconfoption name="vfs objects">readonly</smbconfoption>
+</programlisting>
+
+	<para>Mark the [backup] share as read only during business hours:</para>
+<programlisting>
+        <smbconfsection name="[backup]"/>
+	<smbconfoption name="path">/readonly</smbconfoption>
+	<smbconfoption name="vfs objects">readonly</smbconfoption>
+	<smbconfoption name="readonly:period">readonly:period = "today 9:00","today 17:00"</smbconfoption>
+</programlisting>
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_recycle.8.xml b/docs-xml/manpages-3/vfs_recycle.8.xml
new file mode 100644
index 00000000000..ca95f881b73
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_recycle.8.xml
@@ -0,0 +1,217 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_recycle.8">
+
+<refmeta>
+	<refentrytitle>vfs_recycle</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_recycle</refname>
+	<refpurpose>Samba VFS recycle bin</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = recycle</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_recycle</command> intercepts file deletion
+	requests and moves the affected files to a temporary repository
+	rather than deleting them immediately. This gives the same effect
+	as the Recycle Bin on Windows computers. </para>
+
+	<para>The Recycle Bin will not appear in Windows Explorer
+	views of the network file system (share) nor on any mapped
+	drive. Instead, a directory called .recycle will be automatically
+	created when the first file is deleted and recycle:repository is
+	not configured. If recycle:repository is configured, the name
+	of the created directory depends on recycle:repository. Users
+	can recover files from the recycle bin. If the recycle:keeptree
+	option has been specified, deleted files will be found in a path
+	identical with that from which the file was deleted.  </para>
+
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>recycle:repository = PATH</term>
+		<listitem>
+		<para>Path of the directory where deleted files should be moved.
+		</para>
+		<para>If this option is not set, the default path .recycle
+		is used. </para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:directory_mode = MODE</term>
+		<listitem>
+		<para>Set MODE to the octal mode the recycle repository
+		should be created with.  The recycle repository will be
+		created when first file is deleted. If recycle:subdir_mode
+		is not set, MODE also applies to subdirectories.
+		</para>
+		<para>If this option is not set, the default mode
+		0700 is used. </para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:subdir_mode = MODE</term>
+		<listitem>
+		<para>Set MODE to the octal mode with which
+		sub directories of the recycle repository should be created.
+		</para>
+		<para>If this option is not set, subdirectories
+		will be created with the mode from recycle:directory_mode.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:keeptree = BOOL</term>
+		<listitem>
+		<para>Specifies whether the directory structure should
+		be preserved or whether the files in a directory that is being
+		deleted should be kept separately in the repository.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:versions = BOOL</term>
+		<listitem>
+		<para>If this option is True, two files with the same
+		name that are deleted will both be kept in the repository.
+		Newer deleted versions of a file will be called
+		&quot;Copy #x of filename&quot;.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:touch = BOOL</term>
+		<listitem>
+		<para>Specifies whether a file's access date should be
+		updated when the file is moved to the repository.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:touch_mtime = BOOL</term>
+		<listitem>
+		<para>Specifies whether a file's last modified date should be
+		updated when the file is moved to the repository.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:minsize = BYTES</term>
+		<listitem>
+		<para>Files that are smaller than the number of bytes
+		specified by this parameter will not be put into the
+		repository.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:maxsize = BYTES</term>
+		<listitem>
+		<para>Files that are larger than the number of bytes
+		specified by this parameter will not be put into the
+		repository.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:exclude = LIST</term>
+		<listitem>
+		<para>List of files that should not be put into the
+		repository when deleted, but deleted in the normal way.
+		Wildcards such as * and ? are supported.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:exclude_dir = LIST</term>
+		<listitem>
+		<para>List of directories whose files should not be put
+		into the repository when deleted, but deleted in the
+		normal way. Wildcards such as * and ? are supported.
+		</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>recycle:noversions = LIST</term>
+		<listitem>
+		<para>Specifies a list of paths (wildcards such as *
+		and ? are supported) for which no versioning should
+		be used. Only useful when recycle:versions is enabled.
+		</para>
+		</listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Log operations on all shares using the LOCAL1 facility
+	and NOTICE priority:</para>
+
+<programlisting>
+        <smbconfsection name="[global]"/>
+	<smbconfoption name="vfs objects">recycle</smbconfoption>
+	<smbconfoption name="recycle:facility">LOCAL1</smbconfoption>
+	<smbconfoption name="recycle:priority">NOTICE</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_shadow_copy.8.xml b/docs-xml/manpages-3/vfs_shadow_copy.8.xml
new file mode 100644
index 00000000000..49f79542d3f
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_shadow_copy.8.xml
@@ -0,0 +1,121 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_shadow_copy.8">
+
+<refmeta>
+	<refentrytitle>vfs_shadow_copy</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_shadow_copy</refname>
+	<refpurpose>Make a Samba share read only for a specified time period</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = shadow_copy</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_shadow_copy</command> VFS module functionality
+	that is similar to Microsoft Shadow Copy services. When setup properly,
+	this module allows Microsoft Shadow Copy clients to browse
+	"shadow copies" on Samba shares.
+	</para>
+
+	<para>This module is stackable.</para>
+
+</refsect1>
+
+<refsect1>
+	<title>CONFIGURATION</title>
+
+	<para><command>vfs_shadow_copy</command> relies on a filesystem
+	snapshot implementation. Many common filesystems have native
+	support for this.
+	</para>
+
+	<para>Filesystem snapshots must be mounted on
+	specially named directories in order to be recognized by
+	<command>vfs_shadow_copy</command>. The snapshot mount points must
+	be immediate children of a the directory being shared.</para>
+
+	<para>The snapshot naming convention is @GMT-YYYY.MM.DD-hh.mm.ss,
+	where:
+       	<itemizedlist>
+       		<listitem><para><command>YYYY</command> is the 4 digit year</para></listitem>
+       		<listitem><para><command>MM</command> is the 2 digit month</para></listitem>
+       		<listitem><para><command>DD</command> is the 2 digit day</para></listitem>
+       		<listitem><para><command>hh</command> is the 2 digit hour</para></listitem>
+       		<listitem><para><command>mm</command> is the 2 digit minute</para></listitem>
+       		<listitem><para><command>ss</command> is the 2 digit second.</para></listitem>
+       	</itemizedlist>
+	</para>
+
+       	<para>The <command>vfs_shadow_copy</command> snapshot naming convention can be produced with the following
+	<citerefentry><refentrytitle>date</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> command:
+	<programlisting>
+	TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S
+	</programlisting></para>
+
+</refsect1>
+
+<refsect1>
+	<title>EXAMPLES</title>
+
+	<para>Add shadow copy support to user home directories:</para>
+<programlisting>
+        <smbconfsection name="[homes]"/>
+	<smbconfoption name="vfs objects">shadow_copy</smbconfoption>
+</programlisting>
+
+</refsect1>
+
+<refsect1>
+	<title>CAVEATS</title>
+
+	<para>This is not a backup, archival, or version control solution.
+	</para>
+
+	<para>With Samba or Windows servers,
+	<command>vfs_shadow_copy</command> is designed to be an end-user
+	tool only. It does not replace or enhance your backup and
+	archival solutions and should in no way be considered as
+	such. Additionally, if you need version control, implement a
+	version control system.</para>
+
+</refsect1>
+
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0.25 of the Samba suite.
+	</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfs_xattr_tdb.8.xml b/docs-xml/manpages-3/vfs_xattr_tdb.8.xml
new file mode 100644
index 00000000000..4f3b70223f5
--- /dev/null
+++ b/docs-xml/manpages-3/vfs_xattr_tdb.8.xml
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfs_xattr_tdb.8">
+
+<refmeta>
+	<refentrytitle>vfs_xattr_tdb</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfs_xattr_tdb</refname>
+	<refpurpose>Save Extended Attributes (EAs) in a tdb file</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfs objects = xattr_tdb</command>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This VFS module is part of the
+	<citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>vfs_xattr_tdb</command> VFS module stores
+	Extended Attributes (EAs) in a tdb file. 
+	This enables the usage of Extended Attributes on OS and 
+	filesystems which do not support Extended Attributes 
+	by themselves.	
+	</para>
+
+	<para>This module is stackable.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>xattr_tdb:file = PATH</term>
+		<listitem>
+		<para>Name of the tdb file the EAs are stored in.
+		If this option is not set, the default filename 
+		<filename>xattr.tdb</filename> is used.</para>
+		</listitem>
+		</varlistentry>
+	</variablelist>
+
+	
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/vfstest.1.xml b/docs-xml/manpages-3/vfstest.1.xml
new file mode 100644
index 00000000000..d0cef85e714
--- /dev/null
+++ b/docs-xml/manpages-3/vfstest.1.xml
@@ -0,0 +1,153 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="vfstest.1">
+
+<refmeta>
+	<refentrytitle>vfstest</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>vfstest</refname>
+	<refpurpose>tool for testing samba VFS modules </refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>vfstest</command>
+		<arg choice="opt">-d debuglevel</arg>
+		<arg choice="opt">-c command</arg>
+		<arg choice="opt">-l logdir</arg>
+		<arg choice="opt">-h</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>vfstest</command> is a small command line
+	utility that has the ability to test dso samba VFS modules. It gives the
+	user the ability to call the various VFS functions manually and
+	supports cascaded VFS modules.
+	</para>
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+
+		<varlistentry>
+		<term>-c|--command=command</term>
+		<listitem><para>Execute the specified (colon-separated) commands.
+		See below for the commands that are available.
+		</para> </listitem>
+		</varlistentry>
+
+		&stdarg.help;
+
+		<varlistentry>
+		<term>-l|--logfile=logbasename</term>
+		<listitem><para>File name for log/debug files. The extension
+		<constant>'.client'</constant> will be appended. The log file is never removed
+		by the client.
+		</para></listitem>
+		</varlistentry>
+
+		&stdarg.server.debug;
+		&popt.common.samba;
+
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>COMMANDS</title>
+
+	<para><emphasis>VFS COMMANDS</emphasis></para>
+	<itemizedlist>
+		<listitem><para><command>load &lt;module.so&gt;</command> - Load specified VFS module </para></listitem>
+
+		<listitem><para><command>populate &lt;char&gt; &lt;size&gt;</command> - Populate a data buffer with the specified data
+		</para></listitem>
+
+		<listitem><para><command>showdata [&lt;offset&gt; &lt;len&gt;]</command> - Show data currently in data buffer
+		</para></listitem>
+
+		<listitem><para><command>connect</command> - VFS connect()</para></listitem>
+		<listitem><para><command>disconnect</command> - VFS disconnect()</para></listitem>
+		<listitem><para><command>disk_free</command> - VFS disk_free()</para></listitem>
+		<listitem><para><command>opendir</command> - VFS opendir()</para></listitem>
+		<listitem><para><command>readdir</command> - VFS readdir()</para></listitem>
+		<listitem><para><command>mkdir</command> - VFS mkdir()</para></listitem>
+		<listitem><para><command>rmdir</command> - VFS rmdir()</para></listitem>
+		<listitem><para><command>closedir</command> - VFS closedir()</para></listitem>
+		<listitem><para><command>open</command> - VFS open()</para></listitem>
+		<listitem><para><command>close</command> - VFS close()</para></listitem>
+		<listitem><para><command>read</command> - VFS read()</para></listitem>
+		<listitem><para><command>write</command> - VFS write()</para></listitem>
+		<listitem><para><command>lseek</command> - VFS lseek()</para></listitem>
+		<listitem><para><command>rename</command> - VFS rename()</para></listitem>
+		<listitem><para><command>fsync</command> - VFS fsync()</para></listitem>
+		<listitem><para><command>stat</command> - VFS stat()</para></listitem>
+		<listitem><para><command>fstat</command> - VFS fstat()</para></listitem>
+		<listitem><para><command>lstat</command> - VFS lstat()</para></listitem>
+		<listitem><para><command>unlink</command> - VFS unlink()</para></listitem>
+		<listitem><para><command>chmod</command> - VFS chmod()</para></listitem>
+		<listitem><para><command>fchmod</command> - VFS fchmod()</para></listitem>
+		<listitem><para><command>chown</command> - VFS chown()</para></listitem>
+		<listitem><para><command>fchown</command> - VFS fchown()</para></listitem>
+		<listitem><para><command>chdir</command> - VFS chdir()</para></listitem>
+		<listitem><para><command>getwd</command> - VFS getwd()</para></listitem>
+		<listitem><para><command>utime</command> - VFS utime()</para></listitem>
+		<listitem><para><command>ftruncate</command> - VFS ftruncate()</para></listitem>
+		<listitem><para><command>lock</command> - VFS lock()</para></listitem>
+		<listitem><para><command>symlink</command> - VFS symlink()</para></listitem>
+		<listitem><para><command>readlink</command> - VFS readlink()</para></listitem>
+		<listitem><para><command>link</command> - VFS link()</para></listitem>
+		<listitem><para><command>mknod</command> - VFS mknod()</para></listitem>
+		<listitem><para><command>realpath</command> - VFS realpath()</para></listitem>
+	</itemizedlist>
+
+	<para><emphasis>GENERAL COMMANDS</emphasis></para>
+	<itemizedlist>
+		<listitem><para><command>conf &lt;smb.conf&gt;</command> - Load a different configuration file</para></listitem>
+
+		<listitem><para><command>help [&lt;command&gt;]</command> - Get list of commands or info about specified command</para></listitem>
+
+		<listitem><para><command>debuglevel &lt;level&gt;</command> - Set debug level</para></listitem>
+
+		<listitem><para><command>freemem</command> - Free memory currently in use</para></listitem>
+
+		<listitem><para><command>exit</command> - Exit vfstest</para></listitem>
+	</itemizedlist>
+
+</refsect1>
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of the Samba
+	suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+	<para>The vfstest man page was written by Jelmer Vernooij.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/wbinfo.1.xml b/docs-xml/manpages-3/wbinfo.1.xml
new file mode 100644
index 00000000000..52116889774
--- /dev/null
+++ b/docs-xml/manpages-3/wbinfo.1.xml
@@ -0,0 +1,380 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="wbinfo.1">
+
+<refmeta>
+	<refentrytitle>wbinfo</refentrytitle>
+	<manvolnum>1</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">User Commands</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>wbinfo</refname>
+	<refpurpose>Query information from winbind daemon</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>wbinfo</command>
+		<arg choice="opt">-a user%password</arg>
+		<arg choice="opt">--all-domains</arg>
+		<arg choice="opt">--allocate-gid</arg>
+		<arg choice="opt">--allocate-uid</arg>
+		<arg choice="opt">-D domain</arg>
+		<arg choice="opt">--domain domain</arg>
+		<arg choice="opt">-g</arg>
+		<arg choice="opt">--getdcname domain</arg>
+		<arg choice="opt">--get-auth-user</arg>
+		<arg choice="opt">-G gid</arg>
+		<arg choice="opt">-h</arg>
+		<arg choice="opt">-i user</arg>
+		<arg choice="opt">-I ip</arg>
+		<arg choice="opt">-K user%password</arg>
+		<arg choice="opt">-m</arg>
+		<arg choice="opt">-n name</arg>
+		<arg choice="opt">-N netbios-name</arg>
+		<arg choice="opt">--own-domain</arg>
+		<arg choice="opt">-p</arg>
+		<arg choice="opt">-r user</arg>
+		<arg choice="opt">-s sid</arg>
+		<arg choice="opt">--separator</arg>
+		<arg choice="opt">--sequence</arg>
+		<arg choice="opt">--set-auth-user user%password</arg>
+		<arg choice="opt">-S sid</arg>
+		<arg choice="opt">-t</arg>
+		<arg choice="opt">-u</arg>
+		<arg choice="opt">--uid-info uid</arg>
+		<arg choice="opt">--user-domgroups sid</arg>
+		<arg choice="opt">--user-sids sid</arg>
+		<arg choice="opt">-U uid</arg>
+		<arg choice="opt">-V</arg>
+		<arg choice="opt">-Y sid</arg>
+		<arg choice="opt">--verbose</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This tool is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para>The <command>wbinfo</command> program queries and returns information
+	created and used by the <citerefentry><refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> daemon. </para>
+
+	<para>The <citerefentry><refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> daemon must be configured
+	and running for the <command>wbinfo</command> program to be able
+	to return information.</para>
+</refsect1>
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-a|--authenticate username%password</term>
+		<listitem><para>Attempt to authenticate a user via winbindd.
+                This checks both authenticaion methods and reports its results.
+		</para><note><para>Do not be tempted to use this
+		functionality for authentication in third-party
+		applications.  Instead use <citerefentry><refentrytitle>ntlm_auth</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>.</para></note></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--allocate-gid</term>
+		<listitem><para>Get a new GID out of idmap
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--allocate-uid</term>
+		<listitem><para>Get a new UID out of idmap
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--all-domains</term>
+		<listitem><para>List all domains (trusted and
+		own domain).
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--domain name</term>
+		<listitem><para>This parameter sets the domain on which any specified
+		operations will performed.  If special domain name '.' is used to represent
+		the current domain to which winbindd belongs.  Currently only the
+		<option>--sequence</option>,
+		<option>-u</option>, and <option>-g</option> options honor this parameter.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-D|--domain-info domain</term>
+		<listitem><para>Show most of the info we have about the domain.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-g|--domain-groups</term>
+		<listitem><para>This option will list all groups available
+		in the Windows NT domain for which the <citerefentry><refentrytitle>samba</refentrytitle>
+		<manvolnum>7</manvolnum></citerefentry> daemon is operating in. Groups in all trusted domains
+		will also be listed.  Note that this operation does not assign
+		group ids to any groups that have not already been
+		seen by <citerefentry><refentrytitle>winbindd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry>. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--get-auth-user</term>
+		<listitem><para>Print username and password used by winbindd
+		during session setup to a domain controller. Username
+		and password can be set using <option>--set-auth-user</option>.
+		Only available for root.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--getdcname domain</term>
+		<listitem><para>Get the DC name for the specified domain.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-G|--gid-to-sid gid</term>
+		<listitem><para>Try to convert a UNIX group id to a Windows
+		NT SID.  If the gid specified does not refer to one within
+		the idmap gid range then the operation will fail. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-i|--user-info user</term>
+		<listitem><para>Get user info.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-I|--WINS-by-ip ip</term>
+		<listitem><para>The <parameter>-I</parameter> option
+		queries <citerefentry><refentrytitle>winbindd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> to send a node status
+		request to get the NetBIOS name associated with the IP address
+		specified by the <parameter>ip</parameter> parameter.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-K|--krb5auth username%password</term>
+		<listitem><para>Attempt to authenticate a user via Kerberos.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-m|--trusted-domains</term>
+		<listitem><para>Produce a list of domains trusted by the
+		Windows NT server <citerefentry><refentrytitle>winbindd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> contacts
+		when resolving names.  This list does not include the Windows
+		NT domain the server is a Primary Domain Controller for.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-n|--name-to-sid name</term>
+		<listitem><para>The <parameter>-n</parameter> option
+		queries <citerefentry><refentrytitle>winbindd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> for the SID
+		associated with the name specified. Domain names can be specified
+		before the user name by using the winbind separator character.
+		For example CWDOM1/Administrator refers to the Administrator
+		user in the domain CWDOM1.  If no domain is specified then the
+		domain used is the one specified in the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry>	<parameter>workgroup
+		</parameter> parameter. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-N|--WINS-by-name name</term>
+		<listitem><para>The <parameter>-N</parameter> option
+		queries <citerefentry><refentrytitle>winbindd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> to query the WINS
+		server for the IP address associated with the NetBIOS name
+		specified by the <parameter>name</parameter> parameter.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--own-domain</term>
+		<listitem><para>List own domain.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-p|--ping</term>
+		<listitem><para>Check whether winbindd is still alive.
+		Prints out either 'succeeded' or 'failed'.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-r|--user-groups username</term>
+		<listitem><para>Try to obtain the list of UNIX group ids
+		to which the user belongs.  This only works for users
+		defined on a Domain Controller.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-s|--sid-to-name sid</term>
+		<listitem><para>Use <parameter>-s</parameter> to resolve
+		a SID to a name.  This is the inverse of the <parameter>-n
+		</parameter> option above.  SIDs must be specified as ASCII strings
+		in the traditional Microsoft format. For example,
+		S-1-5-21-1455342024-3071081365-2475485837-500. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--separator</term>
+		<listitem><para>Get the active winbind separator.
+		</para></listitem>
+
+		</varlistentry>
+		<varlistentry>
+		<term>--sequence</term>
+		<listitem><para>Show sequence numbers of
+		all known domains</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--set-auth-user username%password</term>
+		<listitem><para>Store username and password used by winbindd
+		during session setup to a domain controller.  This enables
+		winbindd to operate in a Windows 2000 domain with Restrict
+		Anonymous turned on (a.k.a. Permissions compatible with
+		Windows 2000 servers only).
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-S|--sid-to-uid sid</term>
+		<listitem><para>Convert a SID to a UNIX user id.  If the SID
+		does not correspond to a UNIX user mapped by <citerefentry>
+		<refentrytitle>winbindd</refentrytitle><manvolnum>8</manvolnum>
+		</citerefentry> then the operation will fail. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-t|--check-secret</term>
+		<listitem><para>Verify that the workstation trust account
+		created when the Samba server is added to the Windows NT
+		domain is working. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-u|--domain-users</term>
+		<listitem><para>This option will list all users available
+		in the Windows NT domain for which the <citerefentry><refentrytitle>winbindd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> daemon is operating in. Users in all trusted domains
+		will also be listed.  Note that this operation does not assign
+		user ids to any users that have not already been seen by <citerefentry>
+		<refentrytitle>winbindd</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+		.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--uid-info UID</term>
+		<listitem><para>Get user info for the user conencted to
+		user id UID.</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--user-domgroups SID</term>
+		<listitem><para>Get user domain groups.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>--user-sids SID</term>
+		<listitem><para>Get user group SIDs for user.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-U|--uid-to-sid uid</term>
+		<listitem><para>Try to convert a UNIX user id to a Windows NT
+		SID.  If the uid specified does not refer to one within
+		the idmap uid range then the operation will fail. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		  <term>--verbose</term>
+		  <listitem><para>
+		      Print additional information about the query
+		      results.
+		  </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-Y|--sid-to-gid sid</term>
+		<listitem><para>Convert a SID to a UNIX group id.  If the SID
+		does not correspond to a UNIX group mapped by <citerefentry>
+		<refentrytitle>winbindd</refentrytitle><manvolnum>8</manvolnum></citerefentry> then
+		the operation will fail. </para></listitem>
+		</varlistentry>
+
+
+		&stdarg.version;
+		&stdarg.help;
+
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>EXIT STATUS</title>
+
+	<para>The wbinfo program returns 0 if the operation
+	succeeded, or 1 if the operation failed.  If the <citerefentry>
+	<refentrytitle>winbindd</refentrytitle><manvolnum>8</manvolnum>
+	</citerefentry> daemon is not working <command>wbinfo</command> will always return
+	failure. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of
+	the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+	<para><citerefentry><refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>ntlm_auth</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry></para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+	<para><command>wbinfo</command> and <command>winbindd</command>
+	were written by Tim Potter.</para>
+
+	<para>The conversion to DocBook for Samba 2.2 was done
+	by Gerald Carter. The conversion to DocBook XML 4.2 for Samba
+	3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/manpages-3/winbindd.8.xml b/docs-xml/manpages-3/winbindd.8.xml
new file mode 100644
index 00000000000..7e3948c461d
--- /dev/null
+++ b/docs-xml/manpages-3/winbindd.8.xml
@@ -0,0 +1,512 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="winbindd.8">
+
+<refmeta>
+	<refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum>
+	<refmiscinfo class="source">Samba</refmiscinfo>
+	<refmiscinfo class="manual">System Administration tools</refmiscinfo>
+	<refmiscinfo class="version">3.2</refmiscinfo>
+</refmeta>
+
+
+<refnamediv>
+	<refname>winbindd</refname>
+	<refpurpose>Name Service Switch daemon for resolving names
+	from NT servers</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<cmdsynopsis>
+		<command>winbindd</command>
+		<arg choice="opt">-D</arg>
+		<arg choice="opt">-F</arg>
+		<arg choice="opt">-S</arg>
+		<arg choice="opt">-i</arg>
+		<arg choice="opt">-Y</arg>
+		<arg choice="opt">-d &lt;debug level&gt;</arg>
+		<arg choice="opt">-s &lt;smb config file&gt;</arg>
+		<arg choice="opt">-n</arg>
+	</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+
+	<para>This program is part of the <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+	<para><command>winbindd</command> is a daemon that provides
+	a number of services to the Name Service Switch capability found
+	in most modern C libraries, to arbitrary applications via PAM
+	and <command>ntlm_auth</command> and to Samba itself.</para>
+
+	<para>Even if winbind is not used for nsswitch, it still provides a
+	service to <command>smbd</command>, <command>ntlm_auth</command>
+	and the <command>pam_winbind.so</command> PAM module, by managing connections to
+	domain controllers.  In this configuraiton the
+	<smbconfoption name="idmap uid"/> and
+	<smbconfoption name="idmap gid"/>
+	parameters are not required. (This is known as `netlogon proxy only mode'.)</para>
+
+        <para> The Name Service Switch allows user
+	and system information to be obtained from different databases
+	services such as NIS or DNS.  The exact behaviour can be configured
+	throught the <filename>/etc/nsswitch.conf</filename> file.
+	Users and groups are allocated as they are resolved to a range
+	of user and group ids specified by the administrator of the
+	Samba system.</para>
+
+	<para>The service provided by <command>winbindd</command> is called `winbind' and
+	can be used to resolve user and group information from a
+	Windows NT server. The service can also provide authentication
+	services via an associated PAM module. </para>
+
+	<para>
+	The <filename>pam_winbind</filename> module supports the
+        <parameter>auth</parameter>, <parameter>account</parameter>
+        and <parameter>password</parameter>
+        module-types.  It should be noted that the
+        <parameter>account</parameter> module simply performs a getpwnam() to verify that
+        the system can obtain a uid for the user, as the domain
+        controller has already performed access control.  If the
+        <filename>libnss_winbind</filename> library has been correctly
+        installed, or an alternate source of names configured, this should always succeed.
+	</para>
+
+	<para>The following nsswitch databases are implemented by
+	the winbindd service: </para>
+
+	<variablelist>
+		<varlistentry>
+		<term>-D</term>
+		<listitem><para>If specified, this parameter causes
+		the server to operate as a daemon. That is, it detaches
+		itself and runs in the background on the appropriate port. 
+		This switch is assumed if <command>winbindd</command> is 
+		executed on the command line of a shell.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>hosts</term>
+		<listitem><para>This feature is only available on IRIX.
+		User information traditionally stored in
+		the <filename>hosts(5)</filename> file and used by
+		<command>gethostbyname(3)</command> functions. Names are
+		resolved through the WINS server or by broadcast.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>passwd</term>
+		<listitem><para>User information traditionally stored in
+		the <filename>passwd(5)</filename> file and used by
+		<command>getpwent(3)</command> functions. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>group</term>
+		<listitem><para>Group information traditionally stored in
+		the <filename>group(5)</filename> file and used by
+		<command>getgrent(3)</command> functions. </para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>For example, the following simple configuration in the
+	<filename>/etc/nsswitch.conf</filename> file can be used to initially
+	resolve user and group information from <filename>/etc/passwd
+	</filename> and <filename>/etc/group</filename> and then from the
+	Windows NT server.
+<programlisting>
+passwd:         files winbind
+group:          files winbind
+## only available on IRIX; Linux users should us libnss_wins.so
+hosts:          files dns winbind
+</programlisting></para>
+
+	<para>The following simple configuration in the
+	<filename>/etc/nsswitch.conf</filename> file can be used to initially
+	resolve hostnames from <filename>/etc/hosts</filename> and then from the
+	WINS server.</para>
+<programlisting>
+hosts:		files wins
+</programlisting>
+
+</refsect1>
+
+
+<refsect1>
+	<title>OPTIONS</title>
+
+	<variablelist>
+		<varlistentry>
+		<term>-F</term>
+		<listitem><para>If specified, this parameter causes
+		the main <command>winbindd</command> process to not daemonize,
+		i.e. double-fork and disassociate with the terminal.
+		Child processes are still created as normal to service
+		each connection request, but the main process does not
+		exit. This operation mode is suitable for running
+		<command>winbindd</command> under process supervisors such
+		as <command>supervise</command> and <command>svscan</command>
+		from Daniel J. Bernstein's <command>daemontools</command>
+		package, or the AIX process monitor.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-S</term>
+		<listitem><para>If specified, this parameter causes
+		<command>winbindd</command> to log to standard output rather
+		than a file.</para></listitem>
+		</varlistentry>
+
+		&stdarg.server.debug;
+		&popt.common.samba;
+		&stdarg.help;
+
+		<varlistentry>
+		<term>-i</term>
+		<listitem><para>Tells <command>winbindd</command> to not
+		become a daemon and detach from the current terminal. This
+		option is used by developers when interactive debugging
+		of <command>winbindd</command> is required.
+		<command>winbindd</command> also logs to standard output,
+		as if the <command>-S</command> parameter had been given.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-n</term>
+		<listitem><para>Disable caching. This means winbindd will
+		always have to wait for a response from the domain controller
+		before it can respond to a client and this thus makes things
+		slower. The results will however be more accurate, since
+		results from the cache might not be up-to-date. This
+		might also temporarily hang winbindd if the DC doesn't respond.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>-Y</term>
+		<listitem><para>Single daemon mode. This means winbindd will run
+		as a single process (the mode of operation in Samba 2.2).  Winbindd's
+		default behavior is to launch a child process that is responsible for
+		updating expired cache entries.
+		</para></listitem>
+		</varlistentry>
+
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>NAME AND ID RESOLUTION</title>
+
+	<para>Users and groups on a Windows NT server are assigned
+	a security id (SID) which is globally unique when the
+	user or group is created.  To convert the Windows NT user or group
+	into a unix user or group, a mapping between SIDs and unix user
+	and group ids is required.  This is one of the jobs that <command>
+	winbindd</command> performs. </para>
+
+	<para>As winbindd users and groups are resolved from a server, user
+	and group ids are allocated from a specified range.  This
+	is done on a first come, first served basis, although all existing
+	users and groups will be mapped as soon as a client performs a user
+	or group enumeration command.  The allocated unix ids are stored
+	in a database and will be remembered. </para>
+
+	<para>WARNING: The SID to unix id database is the only location
+	where the user and group mappings are stored by winbindd.  If this
+	store is deleted or corrupted, there is no way for winbindd to
+	determine which user and group ids correspond to Windows NT user
+	and group rids. </para>
+
+        <para>See the <smbconfoption><name>idmap
+        domains</name></smbconfoption> or the old <smbconfoption><name>idmap
+	backend</name></smbconfoption> parameters in
+        <filename>smb.conf</filename> for options for sharing this
+        database, such as via LDAP.</para>
+</refsect1>
+
+
+<refsect1>
+	<title>CONFIGURATION</title>
+
+	<para>Configuration of the <command>winbindd</command> daemon
+	is done through configuration parameters in the <citerefentry>
+	<refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum>
+	</citerefentry> file.  All parameters should be specified in the
+	[global] section of smb.conf. </para>
+
+	<itemizedlist>
+		<listitem><para>
+		<smbconfoption name="winbind separator"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="idmap uid"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="idmap gid"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="idmap backend"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="winbind cache time"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="winbind enum users"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="winbind enum groups"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="template homedir"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="template shell"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="winbind use default domain"/></para></listitem>
+		<listitem><para>
+		<smbconfoption name="winbind: rpc only"/>
+		Setting this parameter forces winbindd to use RPC
+		instead of LDAP to retrieve information from Domain
+		Controllers.
+		</para></listitem>
+	</itemizedlist>
+</refsect1>
+
+
+<refsect1>
+	<title>EXAMPLE SETUP</title>
+
+	<para>
+	To setup winbindd for user and group lookups plus
+	authentication from a domain controller use something like the
+	following setup. This was tested on an early Red Hat Linux box.
+	</para>
+
+	<para>In <filename>/etc/nsswitch.conf</filename> put the
+	following:
+<programlisting>
+passwd: files winbind
+group:  files winbind
+</programlisting>
+	</para>
+
+	<para>In <filename>/etc/pam.d/*</filename> replace the <parameter>
+	auth</parameter> lines with something like this:
+<programlisting>
+auth  required    /lib/security/pam_securetty.so
+auth  required	  /lib/security/pam_nologin.so
+auth  sufficient  /lib/security/pam_winbind.so
+auth  required    /lib/security/pam_unix.so \
+                  use_first_pass shadow nullok
+</programlisting>
+	</para>
+
+	<note><para>
+	The PAM module pam_unix has recently replaced the module pam_pwdb.
+	Some Linux systems use the module pam_unix2 in place of pam_unix.
+	</para></note>
+
+	<para>Note in particular the use of the <parameter>sufficient
+	</parameter> keyword and the <parameter>use_first_pass</parameter> keyword. </para>
+
+	<para>Now replace the account lines with this: </para>
+
+	<para><command>account    required	/lib/security/pam_winbind.so
+	</command></para>
+
+  	<para>The next step is to join the domain. To do that use the
+	<command>net</command> program like this:  </para>
+
+	<para><command>net join -S PDC -U Administrator</command></para>
+
+	<para>The username after the <parameter>-U</parameter> can be any
+	Domain user that has administrator privileges on the machine.
+	Substitute the name or IP of your PDC for "PDC".</para>
+
+	<para>Next copy <filename>libnss_winbind.so</filename> to
+	<filename>/lib</filename> and <filename>pam_winbind.so
+	</filename> to <filename>/lib/security</filename>.  A symbolic link needs to be
+	made from <filename>/lib/libnss_winbind.so</filename> to
+	<filename>/lib/libnss_winbind.so.2</filename>.  If you are using an
+	older version of glibc then the target of the link should be
+	<filename>/lib/libnss_winbind.so.1</filename>.</para>
+
+	<para>Finally, setup a <citerefentry><refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry> containing directives like the
+	following:
+<programlisting>
+[global]
+	winbind separator = +
+        winbind cache time = 10
+        template shell = /bin/bash
+        template homedir = /home/%D/%U
+        idmap uid = 10000-20000
+        idmap gid = 10000-20000
+        workgroup = DOMAIN
+        security = domain
+        password server = *
+</programlisting></para>
+
+
+	<para>Now start winbindd and you should find that your user and
+	group database is expanded to include your NT users and groups,
+	and that you can login to your unix box as a domain user, using
+	the DOMAIN+user syntax for the username. You may wish to use the
+	commands <command>getent passwd</command> and <command>getent group
+	</command> to confirm the correct operation of winbindd.</para>
+</refsect1>
+
+
+<refsect1>
+	<title>NOTES</title>
+
+	<para>The following notes are useful when configuring and
+	running <command>winbindd</command>: </para>
+
+	<para><citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> must be running on the local machine
+	for <command>winbindd</command> to work. </para>
+
+	<para>PAM is really easy to misconfigure.  Make sure you know what
+	you are doing when modifying PAM configuration files.  It is possible
+	to set up PAM such that you can no longer log into your system. </para>
+
+	<para>If more than one UNIX machine is running <command>winbindd</command>,
+	then in general the user and groups ids allocated by winbindd will not
+	be the same.  The user and group ids will only be valid for the local
+	machine, unless a shared <smbconfoption><name>idmap
+	backend</name></smbconfoption> is configured.</para>
+
+	<para>If the the Windows NT SID to UNIX user and group id mapping
+	file is damaged or destroyed then the mappings will be lost. </para>
+</refsect1>
+
+
+<refsect1>
+	<title>SIGNALS</title>
+
+	<para>The following signals can be used to manipulate the
+	<command>winbindd</command> daemon. </para>
+
+	<variablelist>
+		<varlistentry>
+		<term>SIGHUP</term>
+		<listitem><para>Reload the <citerefentry><refentrytitle>smb.conf</refentrytitle>
+		<manvolnum>5</manvolnum></citerefentry> file and
+		apply any parameter changes to the running
+		version of winbindd.  This signal also clears any cached
+		user and group information.  The list of other domains trusted
+		by winbindd is also reloaded.  </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>SIGUSR2</term>
+		<listitem><para>The SIGUSR2 signal will cause <command>
+		winbindd</command> to write status information to the winbind
+		log file.</para>
+
+		<para>Log files are stored in the filename specified by the
+		log file parameter.</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+<refsect1>
+	<title>FILES</title>
+
+	<variablelist>
+		<varlistentry>
+		<term><filename>/etc/nsswitch.conf(5)</filename></term>
+		<listitem><para>Name service switch configuration file.</para>
+		</listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>/tmp/.winbindd/pipe</term>
+		<listitem><para>The UNIX pipe over which clients communicate with
+		the <command>winbindd</command> program.  For security reasons, the
+		winbind client will only attempt to connect to the winbindd daemon
+		if both the <filename>/tmp/.winbindd</filename> directory
+		and <filename>/tmp/.winbindd/pipe</filename> file are owned by
+		root. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>$LOCKDIR/winbindd_privileged/pipe</term>
+	        <listitem><para>The UNIX pipe over which 'privileged' clients
+                communicate with the <command>winbindd</command> program.  For security
+                reasons, access to some winbindd functions - like those needed by
+                the <command>ntlm_auth</command> utility - is restricted.  By default,
+                only users in the 'root' group will get this access, however the administrator
+                may change the group permissions on $LOCKDIR/winbindd_privileged to allow
+                programs like 'squid' to use ntlm_auth.
+		Note that the winbind client will only attempt to connect to the winbindd daemon
+		if both the <filename>$LOCKDIR/winbindd_privileged</filename> directory
+		and <filename>$LOCKDIR/winbindd_privileged/pipe</filename> file are owned by
+		root. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>/lib/libnss_winbind.so.X</term>
+		<listitem><para>Implementation of name service switch library.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>$LOCKDIR/winbindd_idmap.tdb</term>
+		<listitem><para>Storage for the Windows NT rid to UNIX user/group
+		id mapping.  The lock directory is specified when Samba is initially
+		compiled using the <parameter>--with-lockdir</parameter> option.
+		This directory is by default <filename>/usr/local/samba/var/locks
+		</filename>. </para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>$LOCKDIR/winbindd_cache.tdb</term>
+		<listitem><para>Storage for cached user and group information.
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+</refsect1>
+
+
+<refsect1>
+	<title>VERSION</title>
+
+	<para>This man page is correct for version 3.0 of
+        the Samba suite.</para>
+</refsect1>
+
+<refsect1>
+	<title>SEE ALSO</title>
+
+	<para><filename>nsswitch.conf(5)</filename>, <citerefentry>
+	<refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry>, <citerefentry>
+	<refentrytitle>wbinfo</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry>, <citerefentry>
+	<refentrytitle>ntlm_auth</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
+	<refentrytitle>smb.conf</refentrytitle>
+	<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
+	<refentrytitle>pam_winbind</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry></para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar
+	to the way the Linux kernel is developed.</para>
+
+	<para><command>wbinfo</command> and <command>winbindd</command> were
+	written by Tim Potter.</para>
+
+	<para>The conversion to DocBook for Samba 2.2 was done
+	by Gerald Carter. The conversion to DocBook XML 4.2 for
+	Samba 3.0 was done by Alexander Bokovoy.</para>
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/registry/FolderRedir.adm b/docs-xml/registry/FolderRedir.adm
new file mode 100644
index 00000000000..b87a99456b8
--- /dev/null
+++ b/docs-xml/registry/FolderRedir.adm
@@ -0,0 +1,35 @@
+CLASS MACHINE

+

+CATEGORY !!Shell

+

+        CATEGORY !!CustomSharedAppFolders

+                KEYNAME "Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders"

+

+                POLICY !!CustomFolders_SharedAppData

+                        PART !!CustomFolders_SharedAppDataPath         EDITTEXT REQUIRED  EXPANDABLETEXT

+                        DEFAULT !!CustomFolders_SharedAppDataDefault

+                        VALUENAME "AppData"

+                        END PART

+                END POLICY

+

+                POLICY !!CustomFolders_SharedMyDocs

+                        PART !!CustomFolders_SharedMyDocsPath         EDITTEXT REQUIRED  EXPANDABLETEXT

+                        DEFAULT !!CustomFolders_SharedMyDocsDefault

+                        VALUENAME "Personal"

+                        END PART

+                END POLICY

+

+        END CATEGORY

+

+END CATEGORY    ; Shell

+

+

+[strings]

+Shell="Shared User Profile Folders"

+CustomSharedAppFolders="Custom Shared Folders"

+CustomFolders_SharedAppData="Custom Shared Application Folders"

+CustomFolders_SharedAppDataPath="Path to location of Shared Application Data"

+CustomFolders_SharedAppDataDefault="%USERPROFILE%\Local Settings\Application Data"

+CustomFolders_SharedMyDocs="Custom Shared Documentation Folder"

+CustomFolders_SharedMyDocsPath="Path to location of Shared My Documents"

+CustomFolders_SharedMyDocsDefault="%USERPROFILE%\MY Documents"
\ No newline at end of file
diff --git a/docs-xml/registry/NT4-Locking.reg b/docs-xml/registry/NT4-Locking.reg
new file mode 100644
index 00000000000..6175fd51459
--- /dev/null
+++ b/docs-xml/registry/NT4-Locking.reg
@@ -0,0 +1,24 @@
+REGEDIT4

+

+;Contributor:   John H Terpstra <jht@samba.org>

+;Corrected: Stefan Kanthak <skanthak@nexgo.de>

+;Updated: Jun 25, 2001

+;

+;Subject:	Registry Entries That Affect Locking and Caching

+

+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

+"BufFilesDenyWrite"=dword:00000000

+"BufNamedPipes"=dword:00000000

+"UseOpportunisticLocking"=dword:00000000

+"DormantFileLimit"=dword:00000000

+

+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\Linkage]

+"UtilizeNtCaching"=dword:00000000

+

+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Filesystem]

+"Win95TruncatedExtensions"=dword:00000000

+"NTFSDisable8dot3NameCreation"=dword:00000001

+

+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters]

+"EnableOpLockForceClose"=dword:00000001

+"EnableOpLocks"=dword:00000000

diff --git a/docs-xml/registry/NT4_PlainPassword.reg b/docs-xml/registry/NT4_PlainPassword.reg
new file mode 100644
index 00000000000..b30db150c24
--- /dev/null
+++ b/docs-xml/registry/NT4_PlainPassword.reg
@@ -0,0 +1,11 @@
+REGEDIT4

+

+;Contributor:   Tim Small (tim.small@virgin.net)

+;Updated:	20 August 1997

+;Status:	Current

+;

+;Subject:	Registry file to enable plain text passwords in NT4-SP3 and later

+

+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters]

+"EnablePlainTextPassword"=dword:00000001

+

diff --git a/docs-xml/registry/Win-2Kx-XPP-DeleteCachedProfiles.reg b/docs-xml/registry/Win-2Kx-XPP-DeleteCachedProfiles.reg
new file mode 100644
index 00000000000..1867c06fa98
--- /dev/null
+++ b/docs-xml/registry/Win-2Kx-XPP-DeleteCachedProfiles.reg
diff --git a/docs-xml/registry/Win-2Kx-XPP-ForceLocalProfile.reg b/docs-xml/registry/Win-2Kx-XPP-ForceLocalProfile.reg
new file mode 100644
index 00000000000..bc09627ca69
--- /dev/null
+++ b/docs-xml/registry/Win-2Kx-XPP-ForceLocalProfile.reg
diff --git a/docs-xml/registry/Win-NT-DeleteRoamingProfile.reg b/docs-xml/registry/Win-NT-DeleteRoamingProfile.reg
new file mode 100644
index 00000000000..2620ad7cc84
--- /dev/null
+++ b/docs-xml/registry/Win-NT-DeleteRoamingProfile.reg
@@ -0,0 +1,11 @@
+REGEDIT4

+

+;Contributor:   John H Terpstra

+;Updated:	December 17, 2002

+;Status:	Current

+;

+;Subject:	Registry file update to delete roaming profiles on logout

+

+[HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon]

+"DeleteRoamingCache"=dword:00000001

+

diff --git a/docs-xml/registry/Win2000_PlainPassword.reg b/docs-xml/registry/Win2000_PlainPassword.reg
new file mode 100644
index 00000000000..e0ae280b1c2
--- /dev/null
+++ b/docs-xml/registry/Win2000_PlainPassword.reg
@@ -0,0 +1,11 @@
+REGEDIT4

+

+;Contributor:   Herb Lewis (herb@sgi.com)

+;Updated:	16 July 1999

+;Status:	Current

+;

+;Subject:	Registry file to enable plain text passwords in Windows 2000

+

+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkStation\Parameters]

+"EnablePlainTextPassword"=dword:00000001

+

diff --git a/docs-xml/registry/Win95_PlainPassword.reg b/docs-xml/registry/Win95_PlainPassword.reg
new file mode 100644
index 00000000000..9dd3103689c
--- /dev/null
+++ b/docs-xml/registry/Win95_PlainPassword.reg
@@ -0,0 +1,4 @@
+REGEDIT4

+

+[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP]

+"EnablePlainTextPassword"=dword:00000001

diff --git a/docs-xml/registry/Win98_PlainPassword.reg b/docs-xml/registry/Win98_PlainPassword.reg
new file mode 100644
index 00000000000..9dd3103689c
--- /dev/null
+++ b/docs-xml/registry/Win98_PlainPassword.reg
@@ -0,0 +1,4 @@
+REGEDIT4

+

+[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP]

+"EnablePlainTextPassword"=dword:00000001

diff --git a/docs-xml/registry/Win9X-CacheHandling.reg b/docs-xml/registry/Win9X-CacheHandling.reg
new file mode 100644
index 00000000000..265e335b402
--- /dev/null
+++ b/docs-xml/registry/Win9X-CacheHandling.reg
@@ -0,0 +1,7 @@
+REGEDIT4

+

+; Contributor:	John H Terpstra <jht@samba.org>

+; Date:		Feb 15, 1999

+

+[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VREDIR]

+"DiscardCacheOnOpen"=string:00000001

diff --git a/docs-xml/registry/WinME_PlainPassword.reg b/docs-xml/registry/WinME_PlainPassword.reg
new file mode 100644
index 00000000000..9dd3103689c
--- /dev/null
+++ b/docs-xml/registry/WinME_PlainPassword.reg
@@ -0,0 +1,4 @@
+REGEDIT4

+

+[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP]

+"EnablePlainTextPassword"=dword:00000001

diff --git a/docs-xml/registry/WinXP_PlainPassword.reg b/docs-xml/registry/WinXP_PlainPassword.reg
new file mode 100644
index 00000000000..243f72c60ae
--- /dev/null
+++ b/docs-xml/registry/WinXP_PlainPassword.reg
diff --git a/docs-xml/registry/WindowsTerminalServer.reg b/docs-xml/registry/WindowsTerminalServer.reg
new file mode 100644
index 00000000000..73c3b177d20
--- /dev/null
+++ b/docs-xml/registry/WindowsTerminalServer.reg
@@ -0,0 +1,7 @@
+REGEDIT4

+

+;Subject:	Registry file to force multiple NT terminal server users to have their own connections.

+

+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters]

+"MultipleUsersOnConnection"=dword:00000000

+

diff --git a/docs-xml/scripts/find_missing_doc.pl b/docs-xml/scripts/find_missing_doc.pl
new file mode 100755
index 00000000000..2b557b974d1
--- /dev/null
+++ b/docs-xml/scripts/find_missing_doc.pl
@@ -0,0 +1,57 @@
+#!/usr/bin/perl
+
+my %doc;
+
+$topdir = (shift @ARGV) or $topdir = ".";
+
+##################################################
+# Reading links from manpage
+
+$curdir = $ENV{PWD};
+
+chdir("smbdotconf");
+
+open(IN,"xsltproc --xinclude --param smb.context ALL generate-context.xsl parameters.all.xml|");
+
+while(<IN>) {
+	if( /<listitem><para><link linkend="([^"]*)"><parameter moreinfo="none">([^<]*)<\/parameter><\/link><\/para><\/listitem>/g ){
+		$doc{$2} = $1;
+	}
+}
+
+close(IN);
+
+chdir($curdir);
+
+#################################################
+# Reading entries from source code
+
+
+open(SOURCE,"$topdir/param/loadparm.c") or die("Can't open $topdir/param/loadparm.c: $!");
+
+while ($ln = <SOURCE>) {
+  last if $ln =~ m/^static\ struct\ parm_struct\ parm_table.*/;
+} #burn through the preceding lines
+
+while ($ln = <SOURCE>) {
+  last if $ln =~ m/^\s*\}\;\s*$/;
+  #pull in the param names only
+  next if $ln =~ m/.*P_SEPARATOR.*/;
+  next unless $ln =~ /\s*\{\"(.*)\".*/;
+
+  if($doc{lc($1)}) {
+	$doc{lc($1)} = "FOUND";
+  } else {
+	print "'$1' is not documented\n";
+  }
+}
+close SOURCE;
+
+##################################################
+# Trying to find missing references
+
+foreach (keys %doc) {
+	if($doc{$_} cmp "FOUND") {
+		print "'$_' is documented but is not a configuration option\n";
+	}
+}
diff --git a/docs-xml/scripts/find_missing_manpages.pl b/docs-xml/scripts/find_missing_manpages.pl
new file mode 100755
index 00000000000..c468d7d1ee1
--- /dev/null
+++ b/docs-xml/scripts/find_missing_manpages.pl
@@ -0,0 +1,39 @@
+#!/usr/bin/perl
+
+my %doc;
+
+$invar = 0;
+
+$topdir = (shift @ARGV) or $topdir = ".";
+
+$progs = "";
+
+open(IN, "$topdir/Makefile.in");
+while(<IN>) {
+	if($invar && /^([ \t]*)(.*?)([\\])$/) {
+		$progs.=" " . $2;
+		if($4) { $invar = 1; } else { $invar = 0; }
+	} elsif(/^([^ ]*)_PROGS([0-9]*) = (.*?)([\\])$/) {
+		$progs.=" " . $3;
+		if($4) { $invar = 1; }
+	} else { $invar = 0; }
+}
+
+foreach(split(/bin\//, $progs)) {
+	next if($_ eq " ");
+	s/\@EXEEXT\@//g;
+	s/ //g;
+
+
+	$f = $_;
+	
+	$found = 0;
+
+	for($i = 0; $i < 9; $i++) {
+		if(-e "manpages/$f.$i.xml") { $found = 1; }
+	}
+
+	if(!$found) {
+		print "'$f' does not have a manpage\n";
+	}
+}
diff --git a/docs-xml/scripts/indent-smb.conf.pl b/docs-xml/scripts/indent-smb.conf.pl
new file mode 100755
index 00000000000..c4c87a15112
--- /dev/null
+++ b/docs-xml/scripts/indent-smb.conf.pl
@@ -0,0 +1,8 @@
+#!/usr/bin/perl
+
+while(<STDIN>) {
+	if(/^$/) { }
+	elsif(/^([ \t]*)#(.*)/) { print "#$2\n"; }
+	elsif(/^([ \t]*)(.*) = (.*)$/) { print "\t$2 = $3\n"; }
+	elsif(/^([ \t]*)\[(.*)\]([ \t]*)$/) { print "\n[$2]\n"; }
+}
diff --git a/docs-xml/scripts/neatquotes.pl b/docs-xml/scripts/neatquotes.pl
new file mode 100755
index 00000000000..9d5aa6e9e36
--- /dev/null
+++ b/docs-xml/scripts/neatquotes.pl
@@ -0,0 +1,12 @@
+#!/usr/bin/perl
+
+my $inprog = 0;
+
+while(<STDIN>) {
+	if(/<(programlisting|screen)>/) { $inprog = 1; }
+	if(/<\/(programlisting|screen)>/) { $inprog = 0; }
+	if(not /="(.*)"/ and not $inprog) {
+		s/"(.*?)"/<quote>\1<\/quote>/g;
+	}
+	print $_;
+}
diff --git a/docs-xml/smbdotconf/base/bindinterfacesonly.xml b/docs-xml/smbdotconf/base/bindinterfacesonly.xml
new file mode 100644
index 00000000000..bccac4a0da4
--- /dev/null
+++ b/docs-xml/smbdotconf/base/bindinterfacesonly.xml
@@ -0,0 +1,69 @@
+<samba:parameter name="bind interfaces only"
+				type="boolean"
+                 context="G"
+                 advanced="1" wizard="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+        <para>This global parameter allows the Samba admin 
+        to limit what interfaces on a machine will serve SMB requests. It 
+        affects file service <citerefentry><refentrytitle>smbd</refentrytitle>
+        <manvolnum>8</manvolnum></citerefentry> and name service <citerefentry><refentrytitle>nmbd</refentrytitle>
+        <manvolnum>8</manvolnum></citerefentry> in a slightly different ways.</para>
+
+	<para>
+	For name service it causes <command moreinfo="none">nmbd</command> to bind to ports 137 and 138 on the
+	interfaces listed in the <smbconfoption name="interfaces"/> parameter. <command moreinfo="none">nmbd</command>
+	also binds to the &quot;all addresses&quot; interface (0.0.0.0) on ports 137 and 138 for the purposes of
+	reading broadcast messages.  If this option is not set then <command moreinfo="none">nmbd</command> will
+	service name requests on all of these sockets. If <smbconfoption name="bind interfaces only"/> is set then
+	 <command moreinfo="none">nmbd</command> will check the source address of any packets coming in on the
+	broadcast sockets and discard any that don't match the broadcast addresses of the interfaces in the
+	<smbconfoption name="interfaces"/> parameter list.  As unicast packets are received on the other sockets it
+	allows <command moreinfo="none">nmbd</command> to refuse to serve names to machines that send packets that
+	arrive through any interfaces not listed in the <smbconfoption name="interfaces"/> list.  IP Source address
+	spoofing does defeat this simple check, however, so it must not be used seriously as a security feature for
+	 <command moreinfo="none">nmbd</command>.
+	</para>
+
+	<para>
+	For file service it causes <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> to bind only to the interface list given in the <smbconfoption
+	name="interfaces"/> parameter. This restricts the networks that <command moreinfo="none">smbd</command> will
+	serve to packets coming in those interfaces.  Note that you should not use this parameter for machines that
+	are serving PPP or other intermittent or non-broadcast network interfaces as it will not cope with
+	non-permanent interfaces.
+	</para>
+
+	<para>
+	If <smbconfoption name="bind interfaces only"/> is set then unless the network address
+	 <emphasis>127.0.0.1</emphasis> is added to the <smbconfoption name="interfaces"/> parameter list
+	 <citerefentry><refentrytitle>smbpasswd</refentrytitle> <manvolnum>8</manvolnum></citerefentry> and
+	 <citerefentry><refentrytitle>swat</refentrytitle> <manvolnum>8</manvolnum></citerefentry> may not work as
+	expected due to the reasons covered below.
+	</para>
+
+	<para>
+	To change a users SMB password, the <command moreinfo="none">smbpasswd</command> by default connects to the
+	 <emphasis>localhost - 127.0.0.1</emphasis> address as an SMB client to issue the password change request. If
+	<smbconfoption name="bind interfaces only"/> is set then unless the network address
+	 <emphasis>127.0.0.1</emphasis> is added to the <smbconfoption name="interfaces"/> parameter list then <command
+	moreinfo="none"> smbpasswd</command> will fail to connect in it's default mode.  <command
+	moreinfo="none">smbpasswd</command> can be forced to use the primary IP interface of the local host by using
+	its <citerefentry><refentrytitle>smbpasswd</refentrytitle> <manvolnum>8</manvolnum></citerefentry>	<parameter
+	moreinfo="none">-r <replaceable>remote machine</replaceable></parameter> parameter, with <replaceable>remote
+	machine</replaceable> set to the IP name of the primary interface of the local host.
+	</para>
+
+	<para>
+	The <command moreinfo="none">swat</command> status page tries to connect with <command
+	moreinfo="none">smbd</command> and <command moreinfo="none">nmbd</command> at the address
+	<emphasis>127.0.0.1</emphasis> to determine if they are running.  Not adding <emphasis>127.0.0.1</emphasis>
+	will cause <command moreinfo="none"> smbd</command> and <command moreinfo="none">nmbd</command> to always show
+	&quot;not running&quot; even if they really are.  This can prevent <command moreinfo="none"> swat</command>
+	from starting/stopping/restarting <command moreinfo="none">smbd</command> and <command
+	moreinfo="none">nmbd</command>.
+	</para>
+
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/comment.xml b/docs-xml/smbdotconf/base/comment.xml
new file mode 100644
index 00000000000..ce3b574ddf6
--- /dev/null
+++ b/docs-xml/smbdotconf/base/comment.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="comment"
+                 context="S"
+				 type="string"
+                 basic="1" advanced="1" share="1" print="1" developer="1" 
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This is a text field that is seen next to a share 
+	when a client does a queries the server, either via the network 
+	neighborhood or via <command moreinfo="none">net view</command> to list what shares 
+	are available.</para>
+
+	<para>If you want to set the string that is displayed next to the 
+		machine name then see the <smbconfoption name="server string"/> parameter.</para>
+
+</description>
+<value type="default"><comment>No comment</comment></value>
+<value type="example">Fred's Files</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/configbackend.xml b/docs-xml/smbdotconf/base/configbackend.xml
new file mode 100644
index 00000000000..f9da1345557
--- /dev/null
+++ b/docs-xml/smbdotconf/base/configbackend.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="config backend"
+                 context="G"
+				 type="enum"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+		This controls the backend for storing the configuration.
+		Possible values are <emphasis>file</emphasis> (the default)
+		and <emphasis>registry</emphasis>.
+		When <smbconfoption name="config backend">registry</smbconfoption>
+		 is encountered while loading <emphasis>smb.conf</emphasis>,
+		the configuration read so far is dropped and the global
+		options are read from registry instead. So this triggers a
+		registry only configuration. Share definitions are not read
+		immediately but instead <parameter>registry
+		shares</parameter> is set to <emphasis>yes</emphasis>.
+	</para>
+	<para>
+		Note: This option can not be set inside the registry
+		configuration itself.
+	</para>
+</description>
+<value type="default">file</value>
+<value type="example">registry</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/displaycharset.xml b/docs-xml/smbdotconf/base/displaycharset.xml
new file mode 100644
index 00000000000..5bace5b6b09
--- /dev/null
+++ b/docs-xml/smbdotconf/base/displaycharset.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="display charset"
+				 type="string"
+                 context="G"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	Specifies the charset that samba will use to print messages to stdout and stderr.
+	The default value is "LOCALE", which means automatically set, depending on the
+	current locale. The value should generally be the same as the value of the parameter
+	<smbconfoption name="unix charset"/>.
+	</para>
+</description>
+
+<value type="default">"LOCALE" or "ASCII" (depending on the system)</value>
+<value type="example">UTF8</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/doscharset.xml b/docs-xml/smbdotconf/base/doscharset.xml
new file mode 100644
index 00000000000..4b5872ce382
--- /dev/null
+++ b/docs-xml/smbdotconf/base/doscharset.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="dos charset"
+				 type="string"
+                 context="G"
+                 advanced="1" developer="1"
+				 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+        <para>DOS SMB clients assume the server has 
+	the same charset as they do. This option specifies which 
+	charset Samba should talk to DOS clients.
+	</para>
+
+	<para>The default depends on which charsets you have installed. 
+	Samba tries to use charset 850 but falls back to ASCII in 
+	case it is not available. Run <citerefentry><refentrytitle>testparm</refentrytitle>
+	<manvolnum>1</manvolnum></citerefentry> to check the default on your system.</para>
+</description>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/interfaces.xml b/docs-xml/smbdotconf/base/interfaces.xml
new file mode 100644
index 00000000000..2b13200ea6b
--- /dev/null
+++ b/docs-xml/smbdotconf/base/interfaces.xml
@@ -0,0 +1,55 @@
+<samba:parameter name="interfaces"
+                 context="G"
+				 type="list"
+                 basic="1" advanced="1" wizard="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+        <para>This option allows you to override the default 
+	network interfaces list that Samba will use for browsing, name 
+	registration and other NBT traffic. By default Samba will query 
+	the kernel for the list of all active interfaces and use any 
+	interfaces except 127.0.0.1 that are broadcast capable.</para>
+
+	<para>The option takes a list of interface strings. Each string 
+	can be in any of the following forms:</para>
+
+	<itemizedlist>
+		<listitem><para>a network interface name (such as eth0). 
+		This may include shell-like wildcards so eth* will match 
+		any interface starting with the substring &quot;eth&quot;</para></listitem>
+			
+		<listitem><para>an IP address. In this case the netmask is 
+		determined from the list of interfaces obtained from the 
+		kernel</para></listitem>
+			
+		<listitem><para>an IP/mask pair. </para></listitem>
+			
+		<listitem><para>a broadcast/mask pair.</para></listitem>
+	</itemizedlist>
+
+	<para>The &quot;mask&quot; parameters can either be a bit length (such 
+	as 24 for a C class network) or a full netmask in dotted 
+	decimal form.</para>
+
+	<para>The &quot;IP&quot; parameters above can either be a full dotted 
+	decimal IP address or a hostname which will be looked up via 
+	the OS's normal hostname resolution mechanisms.</para>
+
+	<para>
+	By default Samba enables all active interfaces that are broadcast capable
+	except the loopback adaptor (IP address 127.0.0.1).
+	</para>
+	
+	<para>
+	The example below configures three network interfaces corresponding 
+	to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. 
+	The netmasks of the latter two interfaces would be set to 255.255.255.0.
+	</para>
+
+</description>
+<related>bind interfaces only</related>
+
+<value type="example">eth0 192.168.2.10/24 192.168.3.10/255.255.255.0</value>
+
+<value type="default"/>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/netbiosaliases.xml b/docs-xml/smbdotconf/base/netbiosaliases.xml
new file mode 100644
index 00000000000..5d58fc23976
--- /dev/null
+++ b/docs-xml/smbdotconf/base/netbiosaliases.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="netbios aliases"
+                 context="G"
+				 type="list"
+                 advanced="1" wizard="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+        <para>This is a list of NetBIOS names that nmbd will 
+        advertise as additional names by which the Samba server is known. This allows one machine 
+	to appear in browse lists under multiple names. If a machine is acting as a browse server 
+        or logon server none of these names will be advertised as either browse server or logon 
+	servers, only the primary name of the machine will be advertised with these capabilities.
+        </para>
+</description>
+<related>netbios name</related>
+<value type="default"><comment>empty string (no additional names)</comment></value>
+<value type="example">TEST TEST1 TEST2</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/netbiosname.xml b/docs-xml/smbdotconf/base/netbiosname.xml
new file mode 100644
index 00000000000..3e00bf16b94
--- /dev/null
+++ b/docs-xml/smbdotconf/base/netbiosname.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="netbios name"
+                 context="G"
+                 basic="1" advanced="1" wizard="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+        <para>
+		This sets the NetBIOS name by which a Samba server is known. By default it is the same as the first component
+		of the host's DNS name. If a machine is a browse server or logon server this name (or the first component of
+		the hosts DNS name) will be the name that these services are advertised under.
+		</para>
+
+		<para>
+		There is a bug in Samba-3 that breaks operation of browsing and access to shares if the netbios name
+		is set to the literal name <literal>PIPE</literal>. To avoid this problem, do not name your Samba-3
+		server <literal>PIPE</literal>.
+		</para>
+</description>
+
+<related>netbios aliases</related>
+<value type="default"><comment>machine DNS name</comment></value>
+<value type="example">MYNAME</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/netbiosscope.xml b/docs-xml/smbdotconf/base/netbiosscope.xml
new file mode 100644
index 00000000000..253d0b5a164
--- /dev/null
+++ b/docs-xml/smbdotconf/base/netbiosscope.xml
@@ -0,0 +1,12 @@
+<samba:parameter name="netbios scope"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+        <para>This sets the NetBIOS scope that Samba will 
+	operate under. This should not be set unless every machine 
+	on your LAN also sets this value.</para>
+</description>
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/path.xml b/docs-xml/smbdotconf/base/path.xml
new file mode 100644
index 00000000000..7828e624417
--- /dev/null
+++ b/docs-xml/smbdotconf/base/path.xml
@@ -0,0 +1,31 @@
+<samba:parameter name="path"
+                 context="S"
+                 basic="1" advanced="1" share="1" print="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>directory</synonym>
+<description>
+        <para>This parameter specifies a directory to which 
+	the user of the service is to be given access. In the case of 
+	printable services, this is where print data will spool prior to 
+	being submitted to the host for printing.</para>
+
+	<para>For a printable service offering guest access, the service 
+	should be readonly and the path should be world-writeable and 
+	have the sticky bit set. This is not mandatory of course, but 
+	you probably won't get the results you expect if you do 
+	otherwise.</para>
+
+	<para>Any occurrences of <parameter moreinfo="none">%u</parameter> in the path 
+	will be replaced with the UNIX username that the client is using 
+	on this connection. Any occurrences of <parameter moreinfo="none">%m</parameter> 
+	will be replaced by the NetBIOS name of the machine they are 
+	connecting from. These replacements are very useful for setting 
+	up pseudo home directories for users.</para>
+
+<para>Note that this path will be based on <smbconfoption name="root dir"/>
+	 if one was specified.</para>
+	</description>
+
+	<value type="default"></value>
+	<value type="example">/home/fred</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/realm.xml b/docs-xml/smbdotconf/base/realm.xml
new file mode 100644
index 00000000000..98c7e285e6a
--- /dev/null
+++ b/docs-xml/smbdotconf/base/realm.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="realm"
+                 context="G"
+				 type="string"
+                 basic="1" advanced="1" wizard="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+        <para>This option specifies the kerberos realm to use. The realm is 
+	used as the ADS equivalent of the NT4 <command moreinfo="none">domain</command>. It
+	is usually set to the DNS name of the kerberos server.
+	</para>
+</description>
+		
+<value type="default"></value>
+<value type="example">mysambabox.mycompany.com</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/serverstring.xml b/docs-xml/smbdotconf/base/serverstring.xml
new file mode 100644
index 00000000000..275e31ac498
--- /dev/null
+++ b/docs-xml/smbdotconf/base/serverstring.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="server string"
+                 context="G"
+                 basic="1" advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+        <para>This controls what string will show up in the printer comment box in print 
+        manager and next to the IPC connection in <command moreinfo="none">net view</command>. It 
+        can be any string that you wish to show to your users.</para>
+		
+	<para>It also sets what will appear in browse lists next 
+	to the machine name.</para>
+
+	<para>A <parameter moreinfo="none">%v</parameter> will be replaced with the Samba 
+	version number.</para>
+
+	<para>A <parameter moreinfo="none">%h</parameter> will be replaced with the 
+		hostname.</para>
+</description>
+<value type="default">Samba %v</value>
+<value type="example">University of GNUs Samba Server</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/unixcharset.xml b/docs-xml/smbdotconf/base/unixcharset.xml
new file mode 100644
index 00000000000..c4032c2ea28
--- /dev/null
+++ b/docs-xml/smbdotconf/base/unixcharset.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="unix charset"
+	context="G"
+	type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+        <para>Specifies the charset the unix machine 
+		Samba runs on uses. Samba needs to know this in order to be able to 
+		convert text to the charsets other SMB clients use.
+	</para>
+
+	<para>This is also the charset Samba will use when specifying arguments 
+		to scripts that it invokes.
+	</para>
+</description>
+
+<value type="default">UTF8</value>
+<value type="example">ASCII</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/base/workgroup.xml b/docs-xml/smbdotconf/base/workgroup.xml
new file mode 100644
index 00000000000..d62c3d5e126
--- /dev/null
+++ b/docs-xml/smbdotconf/base/workgroup.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="workgroup"
+                 context="G"
+				 type="string"
+                 basic="1" advanced="1" wizard="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+        <para>This controls what workgroup your server will 
+	appear to be in when queried by clients. Note that this parameter 
+	also controls the Domain name used with 
+	the <smbconfoption name="security">domain</smbconfoption>
+		setting.</para>
+</description>
+<value type="default">WORKGROUP</value>
+<value type="example">MYGROUP</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/administrative_share.xml b/docs-xml/smbdotconf/browse/administrative_share.xml
new file mode 100644
index 00000000000..95db5f1c85d
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/administrative_share.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="administrative share"
+                 context="S"
+                 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>If this parameter is set to <constant>yes</constant> for
+      a share, then the share will be an administrative share. The Administrative
+      Shares are the default network shares created by all Windows NT-based
+      operating systems. These are shares like C$, D$ or ADMIN$. The type of these
+      shares is STYPE_DISKTREE_HIDDEN.</para>
+
+    <para>See the section below on <smbconfoption name="security"/> for more 
+      information about this option.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/browseable.xml b/docs-xml/smbdotconf/browse/browseable.xml
new file mode 100644
index 00000000000..e58e1912e28
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/browseable.xml
@@ -0,0 +1,11 @@
+<samba:parameter name="browseable" context="S" type="boolean"
+                 basic="1" advanced="1" print="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>browsable</synonym>
+<description>
+	<para>This controls whether this share is seen in 
+	the list of available shares in a net view and in the browse list.</para>
+
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/browselist.xml b/docs-xml/smbdotconf/browse/browselist.xml
new file mode 100644
index 00000000000..dd858b7fafb
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/browselist.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="browse list"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This controls whether <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> will serve a browse list to 
+	a client doing a <command moreinfo="none">NetServerEnum</command> call. Normally 
+	set to <constant>yes</constant>. You should never need to change 
+	this.</para>
+		
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/domainmaster.xml b/docs-xml/smbdotconf/browse/domainmaster.xml
new file mode 100644
index 00000000000..eee53d66464
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/domainmaster.xml
@@ -0,0 +1,42 @@
+<samba:parameter name="domain master"
+				 type="boolean"
+                 context="G"
+                 basic="1" advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	Tell <citerefentry><refentrytitle>smbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry> to enable
+	WAN-wide browse list collation. Setting this option causes <command moreinfo="none">nmbd</command> to claim a
+	special domain specific NetBIOS name that identifies it as a domain master browser for its given
+	<smbconfoption name="workgroup"/>. Local master browsers in the same <smbconfoption name="workgroup"/> on
+	broadcast-isolated subnets will give this <command moreinfo="none">nmbd</command> their local browse lists,
+	and then ask <citerefentry><refentrytitle>smbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry> for a
+	complete copy of the browse list for the whole wide area network.  Browser clients will then contact their
+	local master browser, and will receive the domain-wide browse list, instead of just the list for their
+	broadcast-isolated subnet.
+	</para>
+
+	<para>
+	Note that Windows NT Primary Domain Controllers expect to be able to claim this <smbconfoption
+	name="workgroup"/> specific special NetBIOS name that identifies them as domain master browsers for that
+	<smbconfoption name="workgroup"/> by default (i.e. there is no way to prevent a Windows NT PDC from attempting
+	to do this). This means that if this parameter is set and <command moreinfo="none">nmbd</command> claims the
+	special name for a <smbconfoption name="workgroup"/> before a Windows NT PDC is able to do so then cross
+	subnet browsing will behave strangely and may fail.
+	</para>
+		
+	<para>
+	If <smbconfoption name="domain logons">yes</smbconfoption>, then the default behavior is to enable the
+	<smbconfoption name="domain master"/> parameter.  If <smbconfoption name="domain logons"/> is not enabled (the
+	default setting), then neither will <smbconfoption name="domain master"/> be enabled by default.
+	</para>
+
+	<para>
+	When <smbconfoption name="domain logons">Yes</smbconfoption> the default setting for this parameter is
+	Yes, with the result that Samba will be a PDC. If <smbconfoption name="domain master">No</smbconfoption>,
+	Samba will function as a BDC. In general, this parameter should be set to 'No' only on a BDC.
+	</para>
+
+</description>
+<value type="default">auto</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/enhancedbrowsing.xml b/docs-xml/smbdotconf/browse/enhancedbrowsing.xml
new file mode 100644
index 00000000000..13f2cd64464
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/enhancedbrowsing.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="enhanced browsing"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This option enables a couple of enhancements to 
+	cross-subnet browse propagation that have been added in Samba 
+	but which are not standard in Microsoft implementations.  
+	</para>
+
+	<para>The first enhancement to browse propagation consists of a regular
+	wildcard query to a Samba WINS server for all Domain Master Browsers,
+	followed by a browse synchronization with each of the returned
+	DMBs. The second enhancement consists of a regular randomised browse
+	synchronization with all currently known DMBs.</para>
+
+	<para>You may wish to disable this option if you have a problem with empty
+	workgroups not disappearing from browse lists. Due to the restrictions
+	of the browse protocols these enhancements can cause a empty workgroup
+	to stay around forever which can be annoying.</para>
+
+	<para>In general you should leave this option enabled as it makes
+	cross-subnet browse propagation much more reliable.</para>
+
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/lmannounce.xml b/docs-xml/smbdotconf/browse/lmannounce.xml
new file mode 100644
index 00000000000..92365d8e508
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/lmannounce.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="lm announce"
+                 context="G"
+				 type="boolean-auto"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter determines if <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> will produce Lanman announce 
+	broadcasts that are needed by OS/2 clients in order for them to see 
+	the Samba server in their browse list. This parameter can have three 
+	values, <constant>yes</constant>, <constant>no</constant>, or
+	<constant>auto</constant>. The default is <constant>auto</constant>.  
+	If set to <constant>no</constant> Samba will never produce these 
+	broadcasts. If set to <constant>yes</constant> Samba will produce 
+	Lanman announce broadcasts at a frequency set by the parameter 
+	<smbconfoption name="lm interval"/>. If set to <constant>auto</constant> 
+	Samba will not send Lanman announce broadcasts by default but will 
+	listen for them. If it hears such a broadcast on the wire it will 
+	then start sending them at a frequency set by the parameter 
+	<smbconfoption name="lm interval"/>.</para>
+</description>
+
+<related>lm interval</related>
+<value type="default">auto</value>
+<value type="example">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/lminterval.xml b/docs-xml/smbdotconf/browse/lminterval.xml
new file mode 100644
index 00000000000..4f381651477
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/lminterval.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="lm interval"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>If Samba is set to produce Lanman announce 
+	broadcasts needed by OS/2 clients (see the 
+		<smbconfoption name="lm announce"/> parameter) then this 
+	parameter defines the frequency in seconds with which they will be 
+	made.  If this is set to zero then no Lanman announcements will be 
+	made despite the setting of the <smbconfoption name="lm announce"/> 
+	parameter.</para>
+</description>
+<related>lm announce</related>
+<value type="default">60</value>
+<value type="example">120</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/localmaster.xml b/docs-xml/smbdotconf/browse/localmaster.xml
new file mode 100644
index 00000000000..47c7e561a19
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/localmaster.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="local master"
+                 context="G"
+                 basic="1" advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This option allows <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> to try and become a local master browser 
+	on a subnet. If set to <constant>no</constant> then <command moreinfo="none">
+	nmbd</command> will not attempt to become a local master browser 
+	on a subnet and will also lose in all browsing elections. By
+	default this value is set to <constant>yes</constant>. Setting this value to 
+	<constant>yes</constant> doesn't mean that Samba will <emphasis>become</emphasis> the 
+	local master browser on a subnet, just that <command moreinfo="none">nmbd</command> 
+	will <emphasis>participate</emphasis> in elections for local master browser.</para>
+
+	<para>Setting this value to <constant>no</constant> will cause <command 
+	moreinfo="none">nmbd</command> <emphasis>never</emphasis> to become a local 
+master browser.</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/oslevel.xml b/docs-xml/smbdotconf/browse/oslevel.xml
new file mode 100644
index 00000000000..7556a830513
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/oslevel.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="os level"
+                 context="G"
+				 type="integer"
+                 basic="1" advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This integer value controls what level Samba advertises itself as for browse elections. The value of this
+	parameter determines whether <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> has a chance of becoming a local master browser for the <smbconfoption
+	name="workgroup"/> in the local broadcast area.
+</para>
+		
+	<para><emphasis>
+	Note:</emphasis> By default, Samba will win a local master browsing election over all Microsoft operating
+	systems except a Windows NT 4.0/2000 Domain Controller. This means that a misconfigured Samba host can
+	effectively isolate a subnet for browsing purposes. This parameter is largely auto-configured in the Samba-3
+	release series and it is seldom necessary to manually override the default setting. Please refer to
+	chapter 9 of the Samba-3 HOWTO document for further information regarding the use of this parameter.
+	<emphasis>Note:</emphasis> The maximum value for this parameter is 255. If you use higher values, counting
+	will start at 0!
+	</para>
+</description>
+<value type="default">20</value>
+<value type="example">65</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/browse/preferredmaster.xml b/docs-xml/smbdotconf/browse/preferredmaster.xml
new file mode 100644
index 00000000000..edddae8ce79
--- /dev/null
+++ b/docs-xml/smbdotconf/browse/preferredmaster.xml
@@ -0,0 +1,29 @@
+<samba:parameter name="preferred master"
+                 context="G"
+				 type="boolean-auto"
+                 basic="1" advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>prefered master</synonym>
+ <description>
+	<para>
+	This boolean parameter controls if <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> is a preferred master browser  for its workgroup.
+	</para>
+
+	<para>
+	If this is set to <constant>yes</constant>, on startup, <command moreinfo="none">nmbd</command> will force
+	an election, and it will have a slight advantage in winning the election.  It is recommended that this
+	parameter is used in conjunction with <smbconfoption name="domain master">yes</smbconfoption>, so that
+	<command moreinfo="none">nmbd</command> can guarantee becoming a domain master.
+	</para>
+		
+	<para>
+	Use this option with caution, because if there are several hosts (whether Samba servers, Windows 95 or NT)
+	that are preferred  master browsers on the same subnet, they will each periodically  and continuously attempt
+	to become the local master browser. This will result in unnecessary broadcast traffic and reduced browsing
+	capabilities.
+	</para>
+</description>
+<related>os level</related>
+<value type="default">auto</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/domain/machinepasswordtimeout.xml b/docs-xml/smbdotconf/domain/machinepasswordtimeout.xml
new file mode 100644
index 00000000000..a8e312ba363
--- /dev/null
+++ b/docs-xml/smbdotconf/domain/machinepasswordtimeout.xml
@@ -0,0 +1,23 @@
+<samba:parameter name="machine password timeout"
+                 context="G"
+				 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+	 <description>
+
+	<para>
+	If a Samba server is a member of a Windows NT Domain (see the <smbconfoption
+	name="security">domain</smbconfoption> parameter) then periodically a running smbd process will try and change
+	the MACHINE ACCOUNT PASSWORD stored in the TDB called <filename moreinfo="none">private/secrets.tdb
+	</filename>.  This parameter specifies how often this password will be changed, in seconds. The default is one
+	week (expressed in seconds), the same as a Windows NT Domain member server.
+	</para>
+
+	<para>
+	See also <citerefentry><refentrytitle>smbpasswd</refentrytitle> <manvolnum>8</manvolnum></citerefentry>,
+	and the <smbconfoption name="security">domain</smbconfoption> parameter.
+	</para>
+
+</description>
+<value type="default">604800</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/casesensitive.xml b/docs-xml/smbdotconf/filename/casesensitive.xml
new file mode 100644
index 00000000000..ed770501cdb
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/casesensitive.xml
@@ -0,0 +1,12 @@
+<samba:parameter name="case sensitive"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>casesignames</synonym>
+
+<description>
+	<para>See the discussion in the section <smbconfoption name="name mangling"/>.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/defaultcase.xml b/docs-xml/smbdotconf/filename/defaultcase.xml
new file mode 100644
index 00000000000..1efb37c8b59
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/defaultcase.xml
@@ -0,0 +1,9 @@
+<samba:parameter name="default case"
+	context="S"
+	type="string" xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>See the section on <smbconfoption name="name mangling"/>.
+	Also note the <smbconfoption name="short preserve case"/> parameter.</para>
+</description>
+<value type="default">lower</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/deletevetofiles.xml b/docs-xml/smbdotconf/filename/deletevetofiles.xml
new file mode 100644
index 00000000000..31138aa8e2a
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/deletevetofiles.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="delete veto files"
+				 type="boolean"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This option is used when Samba is attempting to 
+	delete a directory that contains one or more vetoed directories 
+	(see the <smbconfoption name="veto files"/>
+	option).  If this option is set to <constant>no</constant> (the default) then if a vetoed 
+	directory contains any non-vetoed files or directories then the 
+	directory delete will fail. This is usually what you want.</para>
+
+	<para>If this option is set to <constant>yes</constant>, then Samba 
+	will attempt to recursively delete any files and directories within 
+	the vetoed directory. This can be useful for integration with file 
+	serving systems such as NetAtalk which create meta-files within 
+	directories you might normally veto DOS/Windows users from seeing 
+	(e.g. <filename moreinfo="none">.AppleDouble</filename>)</para>
+
+	<para>Setting <smbconfoption name="delete veto files">yes</smbconfoption> allows these 
+	directories to be  transparently deleted when the parent directory 
+	is deleted (so long as the user has permissions to do so).</para>
+</description>
+<related>veto files</related>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/hidedotfiles.xml b/docs-xml/smbdotconf/filename/hidedotfiles.xml
new file mode 100644
index 00000000000..9f31f2cd5d4
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/hidedotfiles.xml
@@ -0,0 +1,10 @@
+<samba:parameter name="hide dot files"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This is a boolean parameter that controls whether 
+	files starting with a dot appear as hidden files.</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/hidefiles.xml b/docs-xml/smbdotconf/filename/hidefiles.xml
new file mode 100644
index 00000000000..0b475053ee1
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/hidefiles.xml
@@ -0,0 +1,46 @@
+<samba:parameter name="hide files"
+				 type="string"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This is a list of files or directories that are not 
+	visible but are accessible.  The DOS 'hidden' attribute is applied 
+	to any files or directories that match.</para>
+
+	<para>Each entry in the list must be separated by a '/', 
+	which allows spaces to be included in the entry.  '*'
+	and '?' can be used to specify multiple files or directories 
+	as in DOS wildcards.</para>
+
+	<para>Each entry must be a Unix path, not a DOS path and must 
+	not include the Unix directory separator '/'.</para>
+
+	<para>Note that the case sensitivity option is applicable 
+	in hiding files.</para>
+		
+	<para>Setting this parameter will affect the performance of Samba, 
+	as it will be forced to check all files and directories for a match 
+	as they are scanned.</para>
+
+	<para>
+	The example shown above is based on files that the Macintosh 
+	SMB client (DAVE) available from <ulink url="http://www.thursby.com"> 
+	Thursby</ulink> creates for internal use, and also still hides 
+	all files beginning with a dot.
+	</para>
+
+	<para>
+	An example of us of this parameter is:
+<programlisting>
+hide files = /.*/DesktopFolderDB/TrashFor%m/resource.frk/
+</programlisting>
+	</para>
+</description>
+
+<related>hide dot files</related>
+<related>veto files</related>
+<related>case sensitive</related>
+
+<value type="default"><comment>no file are hidden</comment></value>
+
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/hidespecialfiles.xml b/docs-xml/smbdotconf/filename/hidespecialfiles.xml
new file mode 100644
index 00000000000..ea2b68a66c0
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/hidespecialfiles.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="hide special files"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>
+	This parameter prevents clients from seeing special files such as sockets, devices and
+	fifo's in directory listings.
+	</para>
+
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/hideunreadable.xml b/docs-xml/smbdotconf/filename/hideunreadable.xml
new file mode 100644
index 00000000000..c2c1654c1cf
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/hideunreadable.xml
@@ -0,0 +1,10 @@
+<samba:parameter name="hide unreadable"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>This parameter prevents clients from seeing the
+		existance of files that cannot be read. Defaults to off.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/hideunwriteablefiles.xml b/docs-xml/smbdotconf/filename/hideunwriteablefiles.xml
new file mode 100644
index 00000000000..831e8c69c9e
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/hideunwriteablefiles.xml
@@ -0,0 +1,12 @@
+<samba:parameter name="hide unwriteable files"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This parameter prevents clients from seeing the existance of files that cannot be written to. 
+    Defaults to off. Note that unwriteable directories are shown as usual.
+    </para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/mangledmap.xml b/docs-xml/smbdotconf/filename/mangledmap.xml
new file mode 100644
index 00000000000..b4be3a80d26
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/mangledmap.xml
@@ -0,0 +1,33 @@
+<samba:parameter name="mangled map"
+				 type="string"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This is for those who want to directly map UNIX file names which cannot be represented on 
+	Windows/DOS.  The mangling of names is not always what is needed.  In particular you may have 
+	documents with file extensions that differ between DOS and UNIX. 
+	For example, under UNIX it is common to use <filename moreinfo="none">.html</filename> 
+	for HTML files, whereas under Windows/DOS <filename moreinfo="none">.htm</filename> 
+	is more commonly used.
+	</para>
+
+	<para>
+	So to map <filename moreinfo="none">html</filename> to <filename moreinfo="none">htm</filename> 
+	you would use:
+	</para>
+		
+	<para>
+	<smbconfoption name="mangled map">(*.html *.htm)</smbconfoption>.
+	</para>
+
+	<para>
+	One very useful case is to remove the annoying <filename moreinfo="none">;1</filename> off 
+	the ends of filenames on some CDROMs (only visible under some UNIXes). To do this use a map of 
+	(*;1 *;).
+	</para>
+</description>
+
+<value type="default"><comment>no mangled map</comment></value>
+<value type="example">(*;1 *;)</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/manglednames.xml b/docs-xml/smbdotconf/filename/manglednames.xml
new file mode 100644
index 00000000000..90bbc586676
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/manglednames.xml
@@ -0,0 +1,58 @@
+<samba:parameter name="mangled names"
+				 type="boolean"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This controls whether non-DOS names under UNIX 
+	should be mapped to DOS-compatible names (&quot;mangled&quot;) and made visible, 
+	or whether non-DOS names should simply be ignored.</para>
+
+	<para>See the section on <smbconfoption name="name mangling"/> for 
+	details on how to control the mangling process.</para>
+
+	<para>If mangling is used then the mangling algorithm is as follows:</para>
+
+	<itemizedlist>
+		<listitem>
+			<para>The first (up to) five alphanumeric characters 
+			before the rightmost dot of the filename are preserved, forced 
+			to upper case, and appear as the first (up to) five characters 
+			of the mangled name.</para>
+		</listitem>
+		
+		<listitem>
+			<para>A tilde &quot;~&quot; is appended to the first part of the mangled
+			name, followed by a two-character unique sequence, based on the
+			original root name (i.e., the original filename minus its final
+			extension). The final extension is included in the hash calculation
+			only if it contains any upper case characters or is longer than three
+			characters.</para>
+
+			<para>Note that the character to use may be specified using 
+				the <smbconfoption name="mangling char"/>
+			option, if you don't like '~'.</para>
+		</listitem>
+
+		<listitem>
+			<para>Files whose UNIX name begins with a dot will be 
+			presented as DOS hidden files. The mangled name will be created as 
+			for other filenames, but with the leading dot removed and &quot;___&quot; as 
+			its extension regardless of actual original extension (that's three 
+			underscores).</para>
+		</listitem>
+	</itemizedlist>
+
+	<para>The two-digit hash value consists of upper case alphanumeric characters.</para>
+
+	<para>This algorithm can cause name collisions only if files 
+	in a directory share the same first five alphanumeric characters. 
+	The probability of such a clash is 1/1300.</para>
+
+	<para>The name mangling (if enabled) allows a file to be 
+	copied between UNIX directories from Windows/DOS while retaining 
+	the long UNIX filename. UNIX files can be renamed to a new extension 
+	from Windows/DOS and will retain the same basename. Mangled names 
+	do not change between sessions.</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/mangleprefix.xml b/docs-xml/smbdotconf/filename/mangleprefix.xml
new file mode 100644
index 00000000000..fd96c2c4fe3
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/mangleprefix.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="mangle prefix"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para> controls the number of prefix
+	characters from the original name used when generating
+	the mangled names. A larger value will give a weaker
+	hash and therefore more name collisions. The minimum
+	value is 1 and the maximum value is 6.</para>
+
+	<para>
+	mangle prefix is effective only when mangling method is hash2.
+	</para>
+</description>
+<value type="default">1</value>
+<value type="example">4</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/manglingchar.xml b/docs-xml/smbdotconf/filename/manglingchar.xml
new file mode 100644
index 00000000000..95b47794d1d
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/manglingchar.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="mangling char"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>This controls what character is used as 
+	the <emphasis>magic</emphasis> character in <smbconfoption name="name mangling"/>. The 
+	default is a '~' but this may interfere with some software. Use this option to set 
+	it to whatever you prefer. This is effective only when mangling method is hash.</para>
+</description>
+<value type="default">~</value>
+<value type="example">^</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/manglingmethod.xml b/docs-xml/smbdotconf/filename/manglingmethod.xml
new file mode 100644
index 00000000000..f6e2edaac3e
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/manglingmethod.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="mangling method"
+			 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para> controls the algorithm used for the generating
+	the mangled names. Can take two different values, &quot;hash&quot; and
+	&quot;hash2&quot;. &quot;hash&quot; is the algorithm that was used
+	used in Samba for many years and was the default in Samba 2.2.x &quot;hash2&quot; is
+        now the default and is newer and considered a better algorithm (generates less collisions) in
+        the names. Many Win32 applications store the mangled names and so
+	changing to algorithms must not be done lightly as these applications
+        may break unless reinstalled.</para>
+</description>
+<value type="default">hash2</value>
+<value type="example">hash</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/maparchive.xml b/docs-xml/smbdotconf/filename/maparchive.xml
new file mode 100644
index 00000000000..ead72cf25a1
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/maparchive.xml
@@ -0,0 +1,23 @@
+<samba:parameter name="map archive"
+                 context="S"
+				 type="boolean"
+				 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This controls whether the DOS archive attribute 
+	should be mapped to the UNIX owner execute bit.  The DOS archive bit 
+	is set when a file has been modified since its last backup.  One 
+	motivation for this option is to keep Samba/your PC from making 
+	any file it touches from becoming executable under UNIX.  This can 
+	be quite annoying for shared source code, documents, etc...
+	</para>
+
+	<para>
+	Note that this requires the <smbconfoption name="create mask"/>	parameter to be set such that owner 
+	execute bit is not masked out (i.e. it must include 100). See the parameter 
+	<smbconfoption name="create mask"/> for details.
+	</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/maphidden.xml b/docs-xml/smbdotconf/filename/maphidden.xml
new file mode 100644
index 00000000000..841c6876e62
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/maphidden.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="map hidden"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This controls whether DOS style hidden files should be mapped to the UNIX world execute bit.
+	</para>
+
+	<para>
+	Note that this requires the <smbconfoption name="create mask"/> to be set such that the world execute 
+	bit is not masked out (i.e. it must include 001). See the parameter <smbconfoption name="create mask"/> 
+	for details.
+	</para>
+
+</description>
+<value type="boolean">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/mapreadonly.xml b/docs-xml/smbdotconf/filename/mapreadonly.xml
new file mode 100644
index 00000000000..3ec2d3bf279
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/mapreadonly.xml
@@ -0,0 +1,43 @@
+<samba:parameter name="map read only"
+                 context="S"
+		 type="enum"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This controls how the DOS read only attribute should be mapped from a UNIX filesystem.
+	</para>
+
+	<para>
+	This parameter can take three different values, which tell <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> how to display the read only attribute on files, where either
+	<smbconfoption name="store dos attributes"/> is set to <constant>No</constant>, or no extended attribute is
+	present. If <smbconfoption name="store dos attributes"/> is set to <constant>yes</constant> then this
+	parameter is <emphasis>ignored</emphasis>. This is a new parameter introduced in Samba version 3.0.21.
+	</para>
+
+    <para>The three settings are :</para>
+
+    <itemizedlist>
+		<listitem><para>
+		<constant>Yes</constant> - The read only DOS attribute is mapped to the inverse of the user
+		or owner write bit in the unix permission mode set. If the owner write bit is not set, the
+		read only attribute is reported as being set on the file.
+		</para></listitem>
+
+		<listitem><para>
+		<constant>Permissions</constant> - The read only DOS attribute is mapped to the effective permissions of
+		the connecting user, as evaluated by <citerefentry><refentrytitle>smbd</refentrytitle>
+		<manvolnum>8</manvolnum></citerefentry> by reading the unix permissions and POSIX ACL (if present).
+		If the connecting user does not have permission to modify the file, the read only attribute
+		is reported as being set on the file.
+		</para></listitem>
+
+		<listitem><para>
+		<constant>No</constant> - The read only DOS attribute is unaffected by permissions, and can only be set by
+		the <smbconfoption name="store dos attributes"/> method. This may be useful for exporting mounted CDs.
+		</para></listitem>
+    </itemizedlist>
+
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/mapsystem.xml b/docs-xml/smbdotconf/filename/mapsystem.xml
new file mode 100644
index 00000000000..021602d5785
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/mapsystem.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="map system"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This controls whether DOS style system files should be mapped to the UNIX group execute bit.
+	</para>
+
+	<para>
+	Note that this requires the <smbconfoption name="create mask"/>	to be set such that the group 
+	execute bit is not masked out (i.e. it must include 010). See the parameter 
+	<smbconfoption name="create mask"/> for details.
+	</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/maxstatcachesize.xml b/docs-xml/smbdotconf/filename/maxstatcachesize.xml
new file mode 100644
index 00000000000..607fe5840fd
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/maxstatcachesize.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="max stat cache size"
+                 context="G"
+                 developer="1"
+		 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter limits the size in memory of any 
+	 <parameter moreinfo="none">stat cache</parameter> being used
+	to speed up case insensitive name mappings. This parameter is
+	the number of kilobyte (1024) units the stat cache can use.
+	A value of zero means unlimited which is not advised aѕ it can
+	use a lot of memory.
+	You should not need to change this parameter.</para>
+</description>
+<related>stat cache</related>
+<value type="default">256</value>
+<value type="example">100</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/preservecase.xml b/docs-xml/smbdotconf/filename/preservecase.xml
new file mode 100644
index 00000000000..875900d4c2a
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/preservecase.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="preserve case"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This controls if new filenames are created with the case that the client passes, or if 
+	they are forced to be the <smbconfoption name="default case"/>.
+	</para>
+	
+	<para>
+	See the section on <link linkend="NAMEMANGLINGSECT">NAME MANGLING</link> for a fuller discussion.
+	</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/shortpreservecase.xml b/docs-xml/smbdotconf/filename/shortpreservecase.xml
new file mode 100644
index 00000000000..90188a076ec
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/shortpreservecase.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="short preserve case"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This boolean parameter controls if new files which conform to 8.3 syntax, that is all in upper case and of
+	suitable length, are created upper case, or if they are forced to be the <smbconfoption name="default case"/>.
+	This  option can be use with <smbconfoption name="preserve case">yes</smbconfoption> to permit long filenames
+	to retain their case, while short names are lowered.
+	</para>
+		
+	<para>See the section on <link linkend="NAMEMANGLINGSECT">NAME MANGLING</link>.</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/statcache.xml b/docs-xml/smbdotconf/filename/statcache.xml
new file mode 100644
index 00000000000..c38fb11a888
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/statcache.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="stat cache"
+                 context="G"
+                 developer="1"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter determines if <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> will use a cache in order to 
+	speed up case insensitive name mappings. You should never need 
+	to change this parameter.</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/storedosattributes.xml b/docs-xml/smbdotconf/filename/storedosattributes.xml
new file mode 100644
index 00000000000..6fcab82f9c7
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/storedosattributes.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="store dos attributes"
+                 context="S"
+		 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	If this parameter is set Samba attempts to first read DOS attributes (SYSTEM, HIDDEN, ARCHIVE or
+	READ-ONLY) from a filesystem extended attribute, before mapping DOS attributes to UNIX permission bits (such
+	as occurs with <smbconfoption name="map hidden"/> and <smbconfoption name="map readonly"/>).  When set, DOS
+	attributes will be stored onto an extended attribute in the UNIX filesystem, associated with the file or
+	directory.  For no other mapping to occur as a fall-back, the parameters <smbconfoption name="map hidden"/>,
+	<smbconfoption name="map system"/>, <smbconfoption name="map archive"/> and <smbconfoption name="map
+	readonly"/> must be set to off.  This parameter writes the DOS attributes as a string into the extended
+	attribute named "user.DOSATTRIB". This extended attribute is explicitly hidden from smbd clients requesting an
+	EA list. On Linux the filesystem must have been mounted with the mount option user_xattr in order for
+	extended attributes to work, also extended attributes must be compiled into the Linux kernel.
+	</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/vetofiles.xml b/docs-xml/smbdotconf/filename/vetofiles.xml
new file mode 100644
index 00000000000..48e0c40fff8
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/vetofiles.xml
@@ -0,0 +1,52 @@
+<samba:parameter name="veto files"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>
+	This is a list of files and directories that are neither visible nor accessible.  Each entry in 
+	the list must be separated by a '/', which allows spaces to be included in the entry. '*' and '?' 
+	can be used to specify multiple files or directories as in DOS wildcards.
+	</para>
+
+	<para>
+	Each entry must be a unix path, not a DOS path and must <emphasis>not</emphasis> include the  
+	unix directory 	separator '/'.
+	</para>
+
+	<para>
+	Note that the <smbconfoption name="case sensitive"/> option is applicable in vetoing files.
+	</para>
+		
+	<para>
+	One feature of the veto files parameter that it is important to be aware of is Samba's behaviour when
+	trying to delete a directory. If a directory that is to be deleted contains nothing but veto files this
+	deletion will <emphasis>fail</emphasis> unless you also set the <smbconfoption name="delete veto files"/> 
+	parameter to <parameter moreinfo="none">yes</parameter>.
+	</para>
+
+	<para>
+	Setting this parameter will affect the performance of Samba, as it will be forced to check all files 
+	and directories for a match as they are scanned.
+	</para>
+
+	<para>
+	Examples of use include:
+<programlisting>
+; Veto any files containing the word Security,
+; any ending in .tmp, and any directory containing the
+; word root.
+veto files = /*Security*/*.tmp/*root*/
+
+; Veto the Apple specific files that a NetAtalk server
+; creates.
+veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
+</programlisting>
+	</para>
+
+</description>
+<related>hide files</related>
+<related>case sensitive</related>
+
+<value type="default">No files or directories are vetoed.</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/filename/vetooplockfiles.xml b/docs-xml/smbdotconf/filename/vetooplockfiles.xml
new file mode 100644
index 00000000000..b99ab003857
--- /dev/null
+++ b/docs-xml/smbdotconf/filename/vetooplockfiles.xml
@@ -0,0 +1,32 @@
+<samba:parameter name="veto oplock files"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>
+	This parameter is only valid when the <smbconfoption name="oplocks"/>
+	parameter is turned on for a share. It allows the Samba administrator
+	to selectively turn off the granting of oplocks on selected files that
+	match a wildcarded list, similar to the wildcarded list used in the
+	<smbconfoption name="veto files"/> parameter.
+	</para>
+
+
+	<para>
+	You might want to do this on files that you know will be heavily contended 
+	for by clients. A good example of this is in the NetBench SMB benchmark 
+	program, which causes heavy client contention for files ending in 
+	<filename moreinfo="none">.SEM</filename>. To cause Samba not to grant 
+	oplocks on these files you would use the line (either in the [global] 
+	section or in the section for the particular NetBench share.
+	</para>
+
+	<para>
+	An example of use is:
+<programlisting>
+veto oplock files = /.*SEM/
+</programlisting>
+	</para>
+</description>
+<value type="default"><comment>No files are vetoed for oplock grants</comment></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/generate-context.xsl b/docs-xml/smbdotconf/generate-context.xsl
new file mode 100644
index 00000000000..4afba52a863
--- /dev/null
+++ b/docs-xml/smbdotconf/generate-context.xsl
@@ -0,0 +1,49 @@
+<?xml version='1.0'?>
+<!-- vim:set sts=2 shiftwidth=2 syntax=xml: -->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                xmlns:exsl="http://exslt.org/common"
+                xmlns:samba="http://samba.org/common"
+		version="1.1"
+                extension-element-prefixes="exsl">
+
+<xsl:output method="xml" omit-xml-declaration="yes"/>
+
+<xsl:param name="smb.context" select="'G'"/>
+
+<!-- This is needed to copy content unchanged -->
+<xsl:template match="@*|node()">
+  <xsl:copy>
+    <xsl:apply-templates select="@*|node()"/>
+  </xsl:copy>
+</xsl:template>
+
+<xsl:template match="variablelist">
+     <xsl:element name="itemizedlist">
+        <xsl:apply-templates/>
+     </xsl:element>
+</xsl:template>
+
+<xsl:template match="//samba:parameter">
+  <xsl:variable name="name"><xsl:value-of select="translate(translate(string(@name),' ',''),
+                  'abcdefghijklmnopqrstuvwxyz','ABCDEFGHIJKLMNOPQRSTUVWXYZ')"/>
+  </xsl:variable>
+  
+  <xsl:if test="contains(@context,$smb.context) or $smb.context='ALL'">
+     <xsl:element name="listitem">
+        <xsl:element name="para">
+           <xsl:element name="link">
+              <xsl:attribute name="linkend">
+                 <xsl:value-of select="$name"/>
+              </xsl:attribute>
+              <xsl:element name="parameter">
+                 <xsl:attribute name="moreinfo"><xsl:text>none</xsl:text></xsl:attribute>
+                 <xsl:value-of select="@name"/>
+              </xsl:element>
+           </xsl:element>
+        </xsl:element>
+     </xsl:element>
+     <xsl:text>&#10;</xsl:text>     
+  </xsl:if>
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/smbdotconf/generate-file-list.sh b/docs-xml/smbdotconf/generate-file-list.sh
new file mode 100755
index 00000000000..262830de4ba
--- /dev/null
+++ b/docs-xml/smbdotconf/generate-file-list.sh
@@ -0,0 +1,19 @@
+#!/bin/sh
+DIR=.
+if [ "x$1" != "x" ]
+then
+	DIR="$1"
+fi
+
+OLD=`pwd`
+cd $DIR
+
+echo "<variablelist xmlns:xi=\"http://www.w3.org/2003/XInclude\">"
+for I in `find . -mindepth 2 -type f -name '*.xml' | sort -t/ -k3 | xargs`
+do 
+	echo "<xi:include href='$I' parse='xml'/>"
+done
+                
+echo "</variablelist>"
+
+cd $OLD
diff --git a/docs-xml/smbdotconf/ldap/clientldapsaslwrapping.xml b/docs-xml/smbdotconf/ldap/clientldapsaslwrapping.xml
new file mode 100644
index 00000000000..a926cec6458
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/clientldapsaslwrapping.xml
@@ -0,0 +1,44 @@
+<samba:parameter name="client ldap sasl wrapping"
+                 context="G"
+               	 type="string"
+		 advanced="1" 
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	The <smbconfoption name="client ldap sasl wrapping"/> defines whether
+	ldap traffic will be signed or signed and encrypted (sealed). 
+	Possible values are <emphasis>plain</emphasis>, <emphasis>sign</emphasis> 
+	and <emphasis>seal</emphasis>. 	
+	</para>
+
+	<para>
+	The values <emphasis>sign</emphasis> and <emphasis>seal</emphasis> are 
+	only available if Samba has been compiled against a modern 
+	OpenLDAP version (2.3.x or higher).
+	</para>
+	
+	<para>
+	This option is needed in the case of Domain Controllers enforcing 
+	the usage of signed LDAP connections (e.g. Windows 2000 SP3 or higher).
+	LDAP sign and seal can be controlled with the registry key
+	"<literal>HKLM\System\CurrentControlSet\Services\</literal>
+	<literal>NTDS\Parameters\LDAPServerIntegrity</literal>"
+	on the Windows server side.  
+	</para>
+
+	<para>
+	Depending on the used KRB5 library (MIT and older Heimdal versions)
+	it is possible that the message "integrity only" is not supported. 
+	In this case, <emphasis>sign</emphasis> is just an alias for 
+	<emphasis>seal</emphasis>.
+	</para>
+
+	<para>
+	The default value is <emphasis>plain</emphasis> which is not irritable 
+	to KRB5 clock skew errors. That implies synchronizing the time
+	with the KDC in the case of using <emphasis>sign</emphasis> or 
+	<emphasis>seal</emphasis>.
+	</para>
+</description>
+<value type="default">plain</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapadmindn.xml b/docs-xml/smbdotconf/ldap/ldapadmindn.xml
new file mode 100644
index 00000000000..442d242679d
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapadmindn.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="ldap admin dn"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+				 <description>
+
+	 <para>
+	The <smbconfoption name="ldap admin dn"/> defines the Distinguished  Name (DN) name used by Samba to contact
+	the ldap server when retreiving  user account information. The <smbconfoption name="ldap admin dn"/> is used
+	in conjunction with the admin dn password stored in the <filename moreinfo="none">private/secrets.tdb</filename>
+	file.  See the <citerefentry><refentrytitle>smbpasswd</refentrytitle> <manvolnum>8</manvolnum></citerefentry>
+	man page for more information on how  to accomplish this.
+	</para>
+
+	<para>
+	The <smbconfoption name="ldap admin dn"/> requires a fully specified DN. The <smbconfoption name="ldap
+	suffix"/> is not appended to the <smbconfoption name="ldap admin dn"/>.
+	</para>
+</description>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapdeletedn.xml b/docs-xml/smbdotconf/ldap/ldapdeletedn.xml
new file mode 100644
index 00000000000..48f5c9b65a1
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapdeletedn.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="ldap delete dn"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para> This parameter specifies whether a delete
+	operation in the ldapsam deletes the complete entry or only the attributes
+	specific to Samba.
+	</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapgroupsuffix.xml b/docs-xml/smbdotconf/ldap/ldapgroupsuffix.xml
new file mode 100644
index 00000000000..8fe033a2f9a
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapgroupsuffix.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="ldap group suffix"
+                 context="G"
+				 type="string"
+		 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies the suffix that is 
+	used for groups when these are added to the LDAP directory.
+	If this parameter is unset, the value of <smbconfoption 
+	name="ldap suffix"/> will be used instead.  The suffix string is pre-pended to the
+        <smbconfoption name="ldap suffix"/> string so use a partial DN.</para>
+
+</description>
+<value type="default"></value>
+<value type="example">ou=Groups</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapidmapsuffix.xml b/docs-xml/smbdotconf/ldap/ldapidmapsuffix.xml
new file mode 100644
index 00000000000..e397138741b
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapidmapsuffix.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="ldap idmap suffix"
+                 context="G"
+		 advanced="1" developer="1"
+		 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameters specifies the suffix that is used when storing idmap mappings. If this parameter 
+	is unset, the value of <smbconfoption name="ldap suffix"/> will be used instead.  The suffix 
+	string is pre-pended to the <smbconfoption name="ldap suffix"/> string so use a partial DN.
+	</para>
+</description>
+<value type="default"></value>
+<value type="example">ou=Idmap</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapmachinesuffix.xml b/docs-xml/smbdotconf/ldap/ldapmachinesuffix.xml
new file mode 100644
index 00000000000..b54f6383e8a
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapmachinesuffix.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="ldap machine suffix"
+		context="G"
+		advanced="1"
+		developer="1"
+		type="string"
+		xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+
+<description>
+	<para>
+	It specifies where machines should be added to the ldap tree.  If this parameter is unset, the value of
+	<smbconfoption name="ldap suffix"/> will be used instead.  The suffix string is pre-pended to the
+	<smbconfoption name="ldap suffix"/> string so use a partial DN.
+	</para>
+</description>
+
+<value type="default"/>
+<value type="example">ou=Computers</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldappasswdsync.xml b/docs-xml/smbdotconf/ldap/ldappasswdsync.xml
new file mode 100644
index 00000000000..864bfc45a09
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldappasswdsync.xml
@@ -0,0 +1,38 @@
+<samba:parameter name="ldap passwd sync"
+			context="G"
+			advanced="1"
+			developer="1"
+			type="enum"
+			xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+
+<description>
+	<para>
+	This option is used to define whether or not Samba should sync the LDAP password with the NT
+	and LM hashes for normal accounts (NOT for workstation, server or domain trusts) on a password
+	change via SAMBA.  
+	</para>
+
+	<para>
+	The <smbconfoption name="ldap passwd sync"/> can be set to one of three values: 
+	</para>
+	
+	<itemizedlist>
+		<listitem>
+			<para><parameter moreinfo="none">Yes</parameter>  =  Try 
+			to update the LDAP, NT and LM passwords and update the pwdLastSet time.</para>
+		</listitem>
+			
+		<listitem>
+			<para><parameter moreinfo="none">No</parameter> = Update NT and 
+			LM passwords and update the pwdLastSet time.</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">Only</parameter> = Only update 
+			the LDAP password and let the LDAP server do the rest.</para>
+		</listitem>
+	</itemizedlist>		
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapreplicationsleep.xml b/docs-xml/smbdotconf/ldap/ldapreplicationsleep.xml
new file mode 100644
index 00000000000..4710e2b3b3f
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapreplicationsleep.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="ldap replication sleep"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	When Samba is asked to write to a read-only LDAP replica, we are redirected to talk to the read-write master server.
+	This server then replicates our changes back to the 'local' server, however the replication might take some seconds, 
+	especially over slow links.  Certain client activities, particularly domain joins, can become confused by the 'success' 
+	that does not immediately change the LDAP back-end's data.
+	</para>
+        
+	<para>
+	This option simply causes Samba to wait a short time, to allow the LDAP server to catch up.  If you have a particularly
+	high-latency network, you may wish to time the LDAP replication with a network sniffer, and increase this value accordingly.  
+	Be aware that no checking is performed that the data has actually replicated.
+	</para>
+	
+        <para>
+	The value is specified in milliseconds, the maximum value is 5000 (5 seconds).
+	</para>
+</description>
+<value type="default">1000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapsameditposix.xml b/docs-xml/smbdotconf/ldap/ldapsameditposix.xml
new file mode 100644
index 00000000000..ace6c6c64d5
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapsameditposix.xml
@@ -0,0 +1,93 @@
+<samba:parameter name="ldapsam:editposix"
+	context="G"
+	type="string"
+		 advanced="1" developer="0"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>
+	Editposix is an option that leverages ldapsam:trusted to make it simpler to manage a domain controller
+	eliminating the need to set up custom scripts to add and manage the posix users and groups. This option
+	will instead directly manipulate the ldap tree to create, remove and modify user and group entries.
+	This option also requires a running winbindd as it is used to allocate new uids/gids on user/group
+	creation. The allocation range must be therefore configured.
+	</para>
+
+	<para>
+	To use this option, a basic ldap tree must be provided and the ldap suffix parameters must be properly
+	configured. On virgin servers the default users and groups (Administrator, Guest, Domain Users,
+	Domain Admins, Domain Guests) can be precreated with the command <command moreinfo="none">net sam
+	provision</command>. To run this command the ldap server must be running, Winindd must be running and
+	the smb.conf ldap options must be properly configured.
+
+	The typical ldap setup used with the <smbconfoption name="ldapsam:trusted">yes</smbconfoption> option
+	is usually sufficient to use <smbconfoption name="ldapsam:editposix">yes</smbconfoption> as well.
+	</para>
+
+	<para>
+	An example configuration can be the following:
+
+	<programlisting>
+	encrypt passwords = true
+	passdb backend = ldapsam
+
+	ldapsam:trusted=yes
+	ldapsam:editposix=yes
+
+	ldap admin dn = cn=admin,dc=samba,dc=org
+	ldap delete dn = yes
+	ldap group suffix = ou=groups
+	ldap idmap suffix = ou=idmap
+	ldap machine suffix = ou=computers
+	ldap user suffix = ou=users
+	ldap suffix = dc=samba,dc=org
+
+	idmap backend = ldap:"ldap://localhost"
+
+	idmap uid = 5000-50000
+	idmap gid = 5000-50000
+	</programlisting>
+
+	This configuration assume the ldap server have been loaded with a base tree like described
+	in the following ldif:
+
+	<programlisting>
+	dn: dc=samba,dc=org
+	objectClass: top
+	objectClass: dcObject
+	objectClass: organization
+	o: samba.org
+	dc: samba
+
+	dn: cn=admin,dc=samba,dc=org
+	objectClass: simpleSecurityObject
+	objectClass: organizationalRole
+	cn: admin
+	description: LDAP administrator
+	userPassword: secret
+
+	dn: ou=users,dc=samba,dc=org
+	objectClass: top
+	objectClass: organizationalUnit
+	ou: users
+
+	dn: ou=groups,dc=samba,dc=org
+	objectClass: top
+	objectClass: organizationalUnit
+	ou: groups
+
+	dn: ou=idmap,dc=samba,dc=org
+	objectClass: top
+	objectClass: organizationalUnit
+	ou: idmap
+
+	dn: ou=computers,dc=samba,dc=org
+	objectClass: top
+	objectClass: organizationalUnit
+	ou: computers
+	</programlisting>
+	</para>
+
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapsamtrusted.xml b/docs-xml/smbdotconf/ldap/ldapsamtrusted.xml
new file mode 100644
index 00000000000..2e4e1dbd7cb
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapsamtrusted.xml
@@ -0,0 +1,30 @@
+<samba:parameter name="ldapsam:trusted"
+	context="G"
+	type="string"
+		 advanced="1" developer="0"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>
+	By default, Samba as a Domain Controller with an LDAP backend needs to use the Unix-style NSS subsystem to
+	access user and group information. Due to the way Unix stores user information in /etc/passwd and /etc/group
+	this inevitably leads to inefficiencies. One important question a user needs to know is the list of groups he
+	is member of. The plain UNIX model involves a complete enumeration of the file /etc/group and its NSS
+	counterparts in LDAP. UNIX has optimized functions to enumerate group membership. Sadly, other functions that
+	are used to deal with user and group attributes lack such optimization.
+	</para>
+
+	<para>
+	To make Samba scale well in large environments, the <smbconfoption name="ldapsam:trusted">yes</smbconfoption>
+	option assumes that the complete user and group database that is relevant to Samba is stored in LDAP with the
+	standard posixAccount/posixGroup attributes. It further assumes that the Samba auxiliary object classes are 
+	stored together with the POSIX data in the same LDAP object. If these assumptions are met, 
+	<smbconfoption name="ldapsam:trusted">yes</smbconfoption> can be activated and Samba can bypass the 
+	NSS system to query user group memberships. Optimized LDAP queries can greatly speed up domain logon and 
+	administration tasks. Depending on the size of the LDAP database a factor of 100 or more for common queries 
+	is easily achieved.
+	</para>
+
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapssl.xml b/docs-xml/smbdotconf/ldap/ldapssl.xml
new file mode 100644
index 00000000000..39ed08fe82d
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapssl.xml
@@ -0,0 +1,38 @@
+<samba:parameter name="ldap ssl"
+                 context="G"
+				 type="enum"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>This option is used to define whether or not Samba should
+	use SSL when connecting to the ldap server
+	This is <emphasis>NOT</emphasis> related to
+	Samba's previous SSL support which was enabled by specifying the 
+	 <command moreinfo="none">--with-ssl</command> option to the <filename moreinfo="none">configure</filename> 
+	script.</para>
+		
+<para>The <smbconfoption name="ldap ssl"/> can be set to one of three values:</para>	
+	<itemizedlist>
+		<listitem>
+			<para><parameter moreinfo="none">Off</parameter> = Never 
+			use SSL when querying the directory.</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">Start_tls</parameter> = Use 
+			the LDAPv3 StartTLS extended operation (RFC2830) for 
+			communicating with the directory server.</para>
+		</listitem>
+	    
+		<listitem>
+			<para><parameter moreinfo="none">On</parameter>  = Use SSL 
+			on the ldaps port when contacting the <parameter 
+			moreinfo="none">ldap server</parameter>. Only available when the 
+			backwards-compatiblity <command 
+			moreinfo="none">--with-ldapsam</command> option is specified
+		to configure. See <smbconfoption name="passdb backend"/></para>.
+		</listitem>
+	</itemizedlist>		
+</description>
+<value type="default">start_tls</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapsuffix.xml b/docs-xml/smbdotconf/ldap/ldapsuffix.xml
new file mode 100644
index 00000000000..48595139a27
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapsuffix.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="ldap suffix"
+                 context="G"
+		 type="string"
+		 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>Specifies the base for all ldap suffixes and for storing the sambaDomain object.</para>
+
+	<para>
+	The ldap suffix will be appended to the values specified for the <smbconfoption name="ldap user suffix"/>,
+	 <smbconfoption name="ldap group suffix"/>, <smbconfoption name="ldap machine suffix"/>, and the
+	 <smbconfoption name="ldap idmap suffix"/>. Each of these should be given only a DN relative to the
+	 <smbconfoption name ="ldap suffix"/>.
+	</para>
+</description>
+<value type="default"></value>
+<value type="example">dc=samba,dc=org</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldaptimeout.xml b/docs-xml/smbdotconf/ldap/ldaptimeout.xml
new file mode 100644
index 00000000000..cd884949035
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldaptimeout.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="ldap timeout"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	When Samba connects to an ldap server that servermay be down or unreachable. To prevent Samba from hanging whilst
+	waiting for the connection this parameter specifies in seconds how long Samba should wait before failing the 
+	connect. The default is to only wait fifteen seconds for the ldap server to respond to the connect request.
+	</para>
+</description>
+<value type="default">15</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/ldap/ldapusersuffix.xml b/docs-xml/smbdotconf/ldap/ldapusersuffix.xml
new file mode 100644
index 00000000000..6b4eec378d4
--- /dev/null
+++ b/docs-xml/smbdotconf/ldap/ldapusersuffix.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="ldap user suffix"
+	context="G"
+	type="string"
+	advanced="1" developer="1"
+        xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter specifies where users are added to the tree. If this parameter is unset, 
+	the value of <smbconfoption name="ldap suffix"/> will be used instead.  The suffix 
+	string is pre-pended to the  <smbconfoption name="ldap suffix"/> string so use a partial DN.
+	</para>
+
+</description>
+<value type="default"/>
+<value type="example">ou=people</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/blockinglocks.xml b/docs-xml/smbdotconf/locking/blockinglocks.xml
new file mode 100644
index 00000000000..493f281fdba
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/blockinglocks.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="blocking locks"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter controls the behavior 
+	of <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> when given a request by a client 
+	to obtain a byte range lock on a region of an open file, and the 
+	request has a time limit associated with it.</para>
+		
+	<para>If this parameter is set and the lock range requested 
+	cannot be immediately satisfied, samba will internally 
+	queue the lock request, and periodically attempt to obtain 
+	the lock until the timeout period expires.</para>
+
+	<para>If this parameter is set to <constant>no</constant>, then 
+	samba will behave as previous versions of Samba would and 
+	will fail the lock request immediately if the lock range 
+	cannot be obtained.</para>
+
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/cscpolicy.xml b/docs-xml/smbdotconf/locking/cscpolicy.xml
new file mode 100644
index 00000000000..6131e1269f9
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/cscpolicy.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="csc policy"
+                 context="S"
+				 type="enum"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This stands for <emphasis>client-side caching policy</emphasis>, and specifies how clients capable of offline
+	caching will cache the files in the share. The valid values are: manual, documents, programs, disable.
+	</para>
+
+	<para>
+	These values correspond to those used on Windows servers.
+	</para>
+
+	<para>
+	For example, shares containing roaming profiles can have offline caching disabled using 
+	<smbconfoption name="csc policy">disable</smbconfoption>.
+	</para>
+</description>
+<value type="default">manual</value>
+<value type="example">programs</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/fakeoplocks.xml b/docs-xml/smbdotconf/locking/fakeoplocks.xml
new file mode 100644
index 00000000000..fa004d7497a
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/fakeoplocks.xml
@@ -0,0 +1,30 @@
+<samba:parameter name="fake oplocks"
+				 type="boolean"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>Oplocks are the way that SMB clients get permission 
+	from a server to locally cache file operations. If a server grants 
+	an oplock (opportunistic lock) then the client is free to assume 
+	that it is the only one accessing the file and it will aggressively 
+	cache file data. With some oplock types the client may even cache 
+	file open/close operations. This can give enormous performance benefits.
+	</para>
+
+	<para>When you set <command moreinfo="none">fake oplocks = yes</command>, <citerefentry>
+	<refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum></citerefentry> will
+	always grant oplock requests no matter how many clients are using the file.</para>
+
+	<para>It is generally much better to use the real <smbconfoption name="oplocks"/> support rather 
+	than this parameter.</para>
+		
+	<para>If you enable this option on all read-only shares or 
+	shares that you know will only be accessed from one client at a 
+	time such as physically read-only media like CDROMs, you will see 
+	a big performance improvement on many operations. If you enable 
+	this option on shares where multiple clients may be accessing the 
+	files read-write at the same time you can get data corruption. Use 
+	this option carefully!</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/kerneloplocks.xml b/docs-xml/smbdotconf/locking/kerneloplocks.xml
new file mode 100644
index 00000000000..c4f12b9bd42
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/kerneloplocks.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="kernel oplocks"
+				 type="boolean"
+                 context="G"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>For UNIXes that support kernel based <smbconfoption name="oplocks"/>
+	(currently only IRIX and the Linux 2.4 kernel), this parameter 
+	allows the use of them to be turned on or off.</para>
+
+	<para>Kernel oplocks support allows Samba <parameter moreinfo="none">oplocks
+	</parameter> to be broken whenever a local UNIX process or NFS operation 
+	accesses a file that <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> has oplocked. This allows complete 
+	data consistency between SMB/CIFS, NFS and local file access (and is 
+	a <emphasis>very</emphasis> cool feature :-).</para>
+
+	<para>This parameter defaults to <constant>on</constant>, but is translated
+	to a no-op on systems that no not have the necessary kernel support.
+	You should never need to touch this parameter.</para>
+</description>
+
+<related>oplocks</related>
+<related>level2 oplocks</related>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/level2oplocks.xml b/docs-xml/smbdotconf/locking/level2oplocks.xml
new file mode 100644
index 00000000000..496701b1885
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/level2oplocks.xml
@@ -0,0 +1,40 @@
+<samba:parameter name="level2 oplocks"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter controls whether Samba supports
+	level2 (read-only) oplocks on a share.</para>
+		
+	<para>Level2, or read-only oplocks allow Windows NT clients 
+	that have an oplock on a file to downgrade from a read-write oplock 
+	to a read-only oplock once a second client opens the file (instead 
+	of releasing all oplocks on a second open, as in traditional, 
+	exclusive oplocks). This allows all openers of the file that 
+	support level2 oplocks to cache the file for read-ahead only (ie. 
+	they may not cache writes or lock requests) and increases performance 
+	for many accesses of files that are not commonly written (such as 
+	application .EXE files).</para>
+
+	<para>Once one of the clients which have a read-only oplock 
+	writes to the file all clients are notified (no reply is needed 
+	or waited for) and told to break their oplocks to &quot;none&quot; and 
+	delete any read-ahead caches.</para>
+
+	<para>It is recommended that this parameter be turned on to
+	speed access to shared executables.</para>
+
+	<para>For more discussions on level2 oplocks see the CIFS spec.</para>
+
+	<para>
+	Currently, if <smbconfoption name="kernel oplocks"/> are supported then
+	level2 oplocks are not granted (even if this parameter is set to
+	<constant>yes</constant>).  Note also, the <smbconfoption name="oplocks"/>
+	parameter must be set to <constant>yes</constant> on this share in order for 
+	this parameter to have any effect.</para>
+</description>
+
+<related>oplocks</related>
+<related>kernel oplocks</related>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/locking.xml b/docs-xml/smbdotconf/locking/locking.xml
new file mode 100644
index 00000000000..0d0eec4fc93
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/locking.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="locking"
+				 type="boolean"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This controls whether or not locking will be 
+	performed by the server in response to lock requests from the 
+	client.</para>
+
+	<para>If <command moreinfo="none">locking = no</command>, all lock and unlock 
+	requests will appear to succeed and all lock queries will report 
+	that the file in question is available for locking.</para>
+
+	<para>If <command moreinfo="none">locking = yes</command>, real locking will be performed 
+	by the server.</para>
+
+	<para>This option <emphasis>may</emphasis> be useful for read-only 
+	filesystems which <emphasis>may</emphasis> not need locking (such as 
+	CDROM drives), although setting this parameter of <constant>no</constant> 
+	is not really recommended even in this case.</para>
+
+	<para>Be careful about disabling locking either globally or in a 
+	specific service, as lack of locking may result in data corruption. 
+	You should never need to set this parameter.</para>
+</description>
+
+<value type="boolean">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/lockspincount.xml b/docs-xml/smbdotconf/locking/lockspincount.xml
new file mode 100644
index 00000000000..9d74bd75300
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/lockspincount.xml
@@ -0,0 +1,12 @@
+<samba:parameter name="lock spin count"
+                 context="G"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter has been made inoperative in Samba 3.0.24.
+	The functionality it contolled is now controlled by the parameter
+	<smbconfoption name="lock spin time"/>.
+	</para>
+</description>
+<value type="default">0</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/lockspintime.xml b/docs-xml/smbdotconf/locking/lockspintime.xml
new file mode 100644
index 00000000000..da84d9379b8
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/lockspintime.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="lock spin time"
+				 type="integer"
+                 context="G"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>The time in microseconds that smbd should 
+	keep waiting to see if a failed lock request can
+	be granted. This parameter has changed in default
+	value from Samba 3.0.23 from 10 to 200. The associated
+	<smbconfoption name="lock spin count"/> parameter is
+	no longer used in Samba 3.0.24. You should not need
+	to change the value of this parameter.</para>
+</description>
+<value type="default">200</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/oplockbreakwaittime.xml b/docs-xml/smbdotconf/locking/oplockbreakwaittime.xml
new file mode 100644
index 00000000000..bede0408407
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/oplockbreakwaittime.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="oplock break wait time"
+                 context="G"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>
+	This is a tuning parameter added due to bugs in both Windows 9x and WinNT. If Samba responds to a client too 
+	quickly when that client issues an SMB that can cause an oplock break request, then the network client can 
+	fail and not respond to the break request. This tuning parameter (which is set in milliseconds) is the amount 
+	of time Samba will wait before sending an oplock break request to such (broken) clients.
+	</para>
+
+	<warning><para>
+	DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
+	</para></warning>
+</description>
+<value type="default">0</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/oplockcontentionlimit.xml b/docs-xml/smbdotconf/locking/oplockcontentionlimit.xml
new file mode 100644
index 00000000000..3ee3c45eb38
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/oplockcontentionlimit.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="oplock contention limit"
+                 context="S"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This is a <emphasis>very</emphasis> advanced <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> tuning option to improve the efficiency of the 
+	granting of oplocks under multiple client contention for the same file.
+	</para>
+		
+	<para>
+	In brief it specifies a number, which causes <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>not to grant an oplock even when requested if the 
+	approximate number of clients contending for an oplock on the same file goes over this 
+	limit. This causes <command moreinfo="none">smbd</command> to behave in a similar 
+	way to Windows NT.
+	</para>
+
+	<warning><para>
+	DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
+	</para></warning>
+
+</description>
+<value type="default">2</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/oplocks.xml b/docs-xml/smbdotconf/locking/oplocks.xml
new file mode 100644
index 00000000000..0c6c26927cd
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/oplocks.xml
@@ -0,0 +1,31 @@
+<samba:parameter name="oplocks"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This boolean option tells <command moreinfo="none">smbd</command> whether to 
+	issue oplocks (opportunistic locks) to file open requests on this 
+	share. The oplock code can dramatically (approx. 30% or more) improve 
+	the speed of access to files on Samba servers. It allows the clients 
+	to aggressively cache files locally and you may want to disable this 
+	option for unreliable network environments (it is turned on by 
+	default in Windows NT Servers).  For more information see the file 
+	<filename moreinfo="none">Speed.txt</filename> in the Samba 
+	<filename moreinfo="none">docs/</filename> directory.
+	</para>
+
+	<para>
+	Oplocks may be selectively turned off on certain files with a share. See 
+	the <smbconfoption name="veto oplock files"/> parameter. On some systems 
+	oplocks are recognized by the underlying operating system. This 
+	allows data synchronization between all access to oplocked files, 
+	whether it be via Samba or NFS or a local UNIX process. See the 
+	<smbconfoption name="kernel oplocks"/> parameter for details.
+	</para>
+</description>
+
+<related>kernel oplocks</related>
+<related>level2 oplocks</related>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/posixlocking.xml b/docs-xml/smbdotconf/locking/posixlocking.xml
new file mode 100644
index 00000000000..e5a89f59aaf
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/posixlocking.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="posix locking"
+				 type="boolean"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	The <citerefentry><refentrytitle>smbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry>
+	daemon maintains an database of file locks obtained by SMB clients. The default behavior is 
+	to map this internal database to POSIX locks. This means that file locks obtained by SMB clients are 
+	consistent with those seen by POSIX compliant applications accessing the files via a non-SMB 
+	method (e.g. NFS or local file access). You should never need to disable this parameter.
+	</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/sharemodes.xml b/docs-xml/smbdotconf/locking/sharemodes.xml
new file mode 100644
index 00000000000..e8371a563da
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/sharemodes.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="share modes"
+	type="boolean"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This enables or disables the honoring of 
+	the <parameter moreinfo="none">share modes</parameter> during a file open. These 
+	modes are used by clients to gain exclusive read or write access 
+	to a file.</para>
+
+	<para>These open modes are not directly supported by UNIX, so
+	they are simulated using shared memory, or lock files if your 
+	UNIX doesn't support shared memory (almost all do).</para>
+
+	<para>The share modes that are enabled by this option are 
+	 <constant>DENY_DOS</constant>, <constant>DENY_ALL</constant>,
+	<constant>DENY_READ</constant>, <constant>DENY_WRITE</constant>,
+	<constant>DENY_NONE</constant> and <constant>DENY_FCB</constant>.
+	</para>
+
+	<para>This option gives full share compatibility and enabled 
+	by default.</para>
+
+	<para>You should <emphasis>NEVER</emphasis> turn this parameter 
+	off as many Windows applications will break if you do so.</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/locking/strictlocking.xml b/docs-xml/smbdotconf/locking/strictlocking.xml
new file mode 100644
index 00000000000..e3a0ed7b4c5
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/strictlocking.xml
@@ -0,0 +1,29 @@
+<samba:parameter name="strict locking"
+                 context="S"
+				 type="enum"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This is an enumerated type that controls the handling of file locking in the server. When this is set to <constant>yes</constant>,
+	the server will check every read and write access for file locks, and deny access if locks exist. This can be slow on 
+	some systems.
+	</para>
+
+	<para>
+	When strict locking is set to Auto (the default), the server performs file lock checks only on non-oplocked files.
+	As most Windows redirectors perform file locking checks locally on oplocked files this is a good trade off for
+	inproved performance.
+	</para>
+
+	<para>
+	When strict locking is disabled, the server performs file lock checks only when the client explicitly asks for them.
+	</para>
+
+	<para>
+	Well-behaved clients always ask for lock checks when it is important.  So in the vast majority of cases, 
+	 <command moreinfo="none">strict locking = Auto</command> or
+	 <command moreinfo="none">strict locking = no</command> is acceptable.
+	</para>
+</description>
+<value type="default">Auto</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/debugclass.xml b/docs-xml/smbdotconf/logging/debugclass.xml
new file mode 100644
index 00000000000..cc4b84acd7f
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/debugclass.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="debug class"
+                 context="G"
+		 type="boolean"
+                 developer="1" advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    With this boolean parameter enabled, the debug class (DBGC_CLASS) 
+    will be displayed in the debug header.
+    </para>
+    <para>
+    For more information about currently available debug classes, see
+    section about <smbconfoption name="log level"/>.
+    </para>
+
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/debughirestimestamp.xml b/docs-xml/smbdotconf/logging/debughirestimestamp.xml
new file mode 100644
index 00000000000..6f32bd593b8
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/debughirestimestamp.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="debug hires timestamp"
+                 context="G"
+                 developer="1"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this 
+    boolean parameter adds microsecond resolution to the timestamp  message header when turned on.
+    </para>
+
+    <para>
+    Note that the parameter <smbconfoption name="debug timestamp"/> must be on for this to have an effect.
+    </para>
+
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/debugpid.xml b/docs-xml/smbdotconf/logging/debugpid.xml
new file mode 100644
index 00000000000..017d0109406
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/debugpid.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="debug pid"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    When using only one log file for more then one forked <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry>-process there may be hard to follow which process outputs which 
+    message. This boolean parameter is adds the process-id to the timestamp message headers in the
+    logfile when turned on.
+    </para>
+
+    <para>
+    Note that the parameter <smbconfoption name="debug timestamp"/> must be on for this to have an effect.
+    </para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/debugprefixtimestamp.xml b/docs-xml/smbdotconf/logging/debugprefixtimestamp.xml
new file mode 100644
index 00000000000..62a65746134
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/debugprefixtimestamp.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="debug prefix timestamp"
+                 context="G"
+                 developer="1"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    With this option enabled, the timestamp message header is prefixed to the debug message without the
+    filename and function information that is included with the <smbconfoption name="debug timestamp"/> 
+    parameter. This gives timestamps to the messages without adding an additional line.
+    </para>
+
+    <para>
+    Note that this parameter overrides the <smbconfoption name="debug timestamp"/> parameter.
+    </para>
+
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/debugtimestamp.xml b/docs-xml/smbdotconf/logging/debugtimestamp.xml
new file mode 100644
index 00000000000..b335eba465f
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/debugtimestamp.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="debug timestamp"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>timestamp logs</synonym>
+<description>
+    <para>
+    Samba debug log messages are timestamped by default. If you are running at a high 
+    <smbconfoption name="debug level"/> these timestamps can be distracting. This 
+    boolean parameter allows timestamping to be turned off.
+	</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/debuguid.xml b/docs-xml/smbdotconf/logging/debuguid.xml
new file mode 100644
index 00000000000..5cfa541a45c
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/debuguid.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="debug uid"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the 
+    current euid, egid, uid and gid to the timestamp message headers in the log file if turned on.
+    </para>
+		
+    <para>
+    Note that the parameter <smbconfoption name="debug timestamp"/> must be on for this to have an effect.
+    </para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/ldapdebuglevel.xml b/docs-xml/smbdotconf/logging/ldapdebuglevel.xml
new file mode 100644
index 00000000000..fdb6d40f25a
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/ldapdebuglevel.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="ldap debug level"
+		 type="integer"
+		context="G"
+		developer="1" advanced="1"
+		xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+		This parameter controls the debug level of the LDAP library
+		calls. In the case of OpenLDAP, it is the same
+		bit-field as understood by the server and documented in the
+		 <citerefentry>
+			<refentrytitle>slapd.conf</refentrytitle>
+			<manvolnum>5</manvolnum>
+		</citerefentry>
+		manpage.
+		A typical useful value will be
+		 <emphasis>1</emphasis> for tracing function calls.
+	</para>
+	<para>
+		The debug ouput from the LDAP libraries appears with the
+		prefix [LDAP] in Samba's logging output.
+		The level at which LDAP logging is printed is controlled by the
+		parameter <parameter>ldap debug threshold</parameter>.
+	</para>
+</description>
+<value type="default">0</value>
+<value type="example">1</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/ldapdebugthreshold.xml b/docs-xml/smbdotconf/logging/ldapdebugthreshold.xml
new file mode 100644
index 00000000000..e023ff689bc
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/ldapdebugthreshold.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="ldap debug threshold"
+		type="integer"
+		context="G"
+		developer="1" advanced="1"
+		xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+		This parameter controls the Samba debug level at which
+		the ldap library debug output is
+		printed in the Samba logs. See the description of
+		 <parameter>ldap debug level</parameter> for details.
+	</para>
+</description>
+<value type="default">10</value>
+<value type="example">5</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/logfile.xml b/docs-xml/smbdotconf/logging/logfile.xml
new file mode 100644
index 00000000000..838d302b7ba
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/logfile.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="log file"
+                 context="G"
+				 type="string"
+                 developer="1" advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This option allows you to override the name of the Samba log file (also known as the debug file).
+    </para>
+
+    <para>
+    This option takes the standard substitutions, allowing you to have separate log files for each user or machine.
+    </para>
+</description>
+<value type="example">/usr/local/samba/var/log.%m</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/loglevel.xml b/docs-xml/smbdotconf/logging/loglevel.xml
new file mode 100644
index 00000000000..d5562f42bbe
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/loglevel.xml
@@ -0,0 +1,45 @@
+<samba:parameter name="log level"
+				 type="string"
+                 context="G"
+                 developer="1" advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>debuglevel</synonym>
+<description>
+    <para>
+    The value of the parameter (a astring) allows the debug level (logging level) to be specified in the 
+    <filename moreinfo="none">smb.conf</filename> file. 
+    </para>
+
+    <para>This parameter has been extended since the 2.2.x 
+    series, now it allows to specify the debug level for multiple 
+    debug classes. This is to give greater flexibility in the configuration 
+    of the system. The following debug classes are currently implemented:
+    </para>
+
+    <itemizedlist>
+	<listitem><para><parameter moreinfo="none">all</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">tdb</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">printdrivers</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">lanman</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">smb</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">rpc_parse</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">rpc_srv</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">rpc_cli</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">passdb</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">sam</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">auth</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">winbind</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">vfs</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">idmap</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">quota</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">acls</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">locking</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">msdfs</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">dmapi</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">registry</parameter></para></listitem>
+    </itemizedlist>
+    
+</description>
+<value type="default">0</value>
+<value type="example">3 passdb:5 auth:10 winbind:2</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/maxlogsize.xml b/docs-xml/smbdotconf/logging/maxlogsize.xml
new file mode 100644
index 00000000000..3d5239ccdf8
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/maxlogsize.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="max log size"
+				 type="integer"
+                 context="G"
+                 developer="1" advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This option (an integer in kilobytes) specifies the max size the log file should grow to. 
+    Samba periodically checks the size and if it is exceeded it will rename the file, adding 
+	a <filename moreinfo="none">.old</filename> extension.
+	</para>
+
+	<para>A size of 0 means no limit.
+	</para>
+</description>
+<value type="default">5000</value>
+<value type="example">1000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/syslog.xml b/docs-xml/smbdotconf/logging/syslog.xml
new file mode 100644
index 00000000000..e4722d8164f
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/syslog.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="syslog"
+                 context="G"
+				 type="integer"
+                 developer="1" advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This parameter maps how Samba debug messages are logged onto the system syslog logging levels. 
+    Samba debug level zero maps onto syslog <constant>LOG_ERR</constant>, debug level one maps onto 
+    <constant>LOG_WARNING</constant>, debug level two maps onto <constant>LOG_NOTICE</constant>,
+    debug level three maps onto LOG_INFO. All higher levels are mapped to <constant>LOG_DEBUG</constant>.
+    </para>
+
+    <para>
+    This parameter sets the threshold for sending messages to syslog.  Only messages with debug 
+    level less than this value will be sent to syslog. There still will be some
+    logging to log.[sn]mbd even if <emphasis>syslog only</emphasis> is enabled.
+    </para>
+</description>
+<value type="default">1</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logging/syslogonly.xml b/docs-xml/smbdotconf/logging/syslogonly.xml
new file mode 100644
index 00000000000..0fe74713e2c
--- /dev/null
+++ b/docs-xml/smbdotconf/logging/syslogonly.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="syslog only"
+                 context="G"
+				 type="boolean"
+                 developer="1" advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    If this parameter is set then Samba debug messages are logged into the system 
+    syslog only, and not to the debug log files. There still will be some
+	logging to log.[sn]mbd even if <emphasis>syslog only</emphasis> is enabled.
+    </para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/abortshutdownscript.xml b/docs-xml/smbdotconf/logon/abortshutdownscript.xml
new file mode 100644
index 00000000000..45bed073eab
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/abortshutdownscript.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="abort shutdown script"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This a full path name to a script called by <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> that
+	should stop a shutdown procedure issued by the <smbconfoption name="shutdown script"/>.</para>
+		
+	<para>If the connected user posseses the <constant>SeRemoteShutdownPrivilege</constant>,
+	right, this command will be run as user.</para>
+</description>
+<value type="default">&quot;&quot;</value>
+<value type="example">/sbin/shutdown -c</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/addgroupscript.xml b/docs-xml/smbdotconf/logon/addgroupscript.xml
new file mode 100644
index 00000000000..3804e144ffc
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/addgroupscript.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="add group script"
+		context="G"
+		type="string"
+		advanced="1" developer="1"
+		xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This is the full pathname to a script that will be run <emphasis>AS ROOT</emphasis> by <citerefentry>
+	<refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum></citerefentry> when a new group is requested. It
+	will expand any <parameter moreinfo="none">%g</parameter> to the group name passed. This script is only useful
+	for installations using the Windows NT domain administration tools. The script is free to create a group with
+	an arbitrary name to circumvent unix group name restrictions. In that case the script must print the numeric
+	gid of the created group on stdout.
+	</para>
+</description>
+
+<value type="default"/>
+<value type="example">/usr/sbin/groupadd %g</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/addmachinescript.xml b/docs-xml/smbdotconf/logon/addmachinescript.xml
new file mode 100644
index 00000000000..c06a4a964ff
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/addmachinescript.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="add machine script"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This is the full pathname to a script that will  be run by
+	 <citerefentry><refentrytitle>smbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry> when a machine is
+	added to Samba's domain and a Unix account matching the machine's name appended with a &quot;$&quot; does not
+	already exist.
+	</para>
+        <para>This option is very similar to the <smbconfoption
+        name="add user script"/>, and likewise uses the %u
+        substitution for the account name.  Do not use the %m
+        substitution.  </para>
+</description>
+
+<value type="default"/>
+<value type="example">/usr/sbin/adduser -n -g machines -c Machine -d /var/lib/nobody -s /bin/false %u</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/adduserscript.xml b/docs-xml/smbdotconf/logon/adduserscript.xml
new file mode 100644
index 00000000000..7128cb73c7e
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/adduserscript.xml
@@ -0,0 +1,55 @@
+<samba:parameter name="add user script"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This is the full pathname to a script that will be run <emphasis>AS ROOT</emphasis> by 
+	<citerefentry><refentrytitle>smbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry> 
+	under special circumstances described below.
+	</para>
+
+	<para>
+	Normally, a Samba server requires that UNIX users are created for all users accessing 
+	files on this server. For sites that use Windows NT account databases as their primary 
+	user database creating these users and keeping the user list in sync with the Windows 
+	NT PDC is an onerous task. This option allows smbd to create the required UNIX users 
+	 <emphasis>ON DEMAND</emphasis> when a user accesses the Samba server.
+	</para>
+
+	<para>
+	In order to use this option, <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> must <emphasis>NOT</emphasis> be set to 
+	<smbconfoption name="security">share</smbconfoption> and <smbconfoption name="add user script"/> 
+	must be set to a full pathname for a script that will create a UNIX user given one argument of 
+	<parameter moreinfo="none">%u</parameter>, which expands into the UNIX user name to create.
+	</para>
+
+	<para>
+	When the Windows user attempts to access the Samba server, at login (session setup in 
+	the SMB protocol) time, <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> contacts the <smbconfoption name="password server"/> 
+	and attempts to authenticate the given user with the given password. If the authentication 
+	succeeds then <command moreinfo="none">smbd</command> attempts to find a UNIX user in the UNIX 
+	password database to map the Windows user into. If this lookup fails, and 
+	<smbconfoption name="add user script"/> is set then <command moreinfo="none">smbd</command> will
+	call the specified script <emphasis>AS ROOT</emphasis>, expanding any 
+	<parameter moreinfo="none">%u</parameter> argument to be the user name to create.
+	</para>
+
+	<para>
+	If this script successfully creates the user then <command moreinfo="none">smbd</command> will 
+	continue on as though the UNIX user already existed. In this way, UNIX users are dynamically created to
+	match existing Windows NT accounts.
+	</para>
+
+	<para>
+	See also <smbconfoption name="security"/>, <smbconfoption name="password server"/>,
+	<smbconfoption name="delete user script"/>.
+	</para>
+</description>
+
+<value type="default"/>
+<value type="example">/usr/local/samba/bin/add_user %u</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/addusertogroupscript.xml b/docs-xml/smbdotconf/logon/addusertogroupscript.xml
new file mode 100644
index 00000000000..f7eb410024c
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/addusertogroupscript.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="add user to group script"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	Full path to the script that will be called when a user is added to a group using the Windows NT domain administration 
+	tools. It will be run by <citerefentry><refentrytitle>smbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry>
+	<emphasis>AS ROOT</emphasis>. Any <parameter moreinfo="none">%g</parameter> will be replaced with the group name and 
+	any <parameter moreinfo="none">%u</parameter> will be replaced with the user name.
+	</para>
+
+	<para>
+	Note that the <command>adduser</command> command used in the example below does 
+	not support the used syntax on all systems. 
+	</para>
+
+</description>
+<value type="default"></value>
+<value type="example">/usr/sbin/adduser %u %g</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/deletegroupscript.xml b/docs-xml/smbdotconf/logon/deletegroupscript.xml
new file mode 100644
index 00000000000..bd265b7fc82
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/deletegroupscript.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="delete group script"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This is the full pathname to a script that will 
+	be run <emphasis>AS ROOT</emphasis> <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> when a group is requested to be deleted. 
+	It will expand any <parameter moreinfo="none">%g</parameter> to the group name passed.  
+	This script is only useful for installations using the Windows NT domain administration tools.
+	</para>
+</description>
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/deleteuserfromgroupscript.xml b/docs-xml/smbdotconf/logon/deleteuserfromgroupscript.xml
new file mode 100644
index 00000000000..a685ab52906
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/deleteuserfromgroupscript.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="delete user from group script"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>Full path to the script that will be called when 
+	a user is removed from a group using the Windows NT domain administration 
+	tools. It will be run by <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> <emphasis>AS ROOT</emphasis>. 
+	Any <parameter moreinfo="none">%g</parameter> will be replaced with the group name and 
+	any <parameter moreinfo="none">%u</parameter> will be replaced with the user name.
+</para>
+</description>
+<value type="default"/>
+<value type="example">/usr/sbin/deluser %u %g</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/deleteuserscript.xml b/docs-xml/smbdotconf/logon/deleteuserscript.xml
new file mode 100644
index 00000000000..b3abe23e4cb
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/deleteuserscript.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="delete user script"
+			     type="string"
+                 context="G"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This is the full pathname to a script that will 
+	be run by <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> when managing users 
+	with remote RPC (NT) tools.
+	</para>
+
+	<para>This script is called when a remote client removes a user
+	from the server, normally using 'User Manager for Domains' or
+	<command moreinfo="none">rpcclient</command>.</para>
+
+	<para>This script should delete the given UNIX username.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">/usr/local/samba/bin/del_user %u</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/domainlogons.xml b/docs-xml/smbdotconf/logon/domainlogons.xml
new file mode 100644
index 00000000000..d274faa18ba
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/domainlogons.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="domain logons"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	If set to <constant>yes</constant>, the Samba server will
+	provide the netlogon service for Windows 9X network logons for the
+	<smbconfoption name="workgroup"/> it is in.
+	This will also cause the Samba server to act as a domain
+	controller for NT4 style domain services. For more details on
+	setting up this feature see the Domain Control chapter of the
+	Samba HOWTO Collection.
+	</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/enableprivileges.xml b/docs-xml/smbdotconf/logon/enableprivileges.xml
new file mode 100644
index 00000000000..3e958e0ce9a
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/enableprivileges.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="enable privileges"
+                 context="G"
+		 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either
+	 <command>net rpc rights</command> or one of the Windows user and group manager tools.  This parameter is
+	enabled by default. It can be disabled to prevent members of the Domain Admins group from being able to
+	assign privileges to users or groups which can then result in certain smbd operations running as root that
+	would normally run under the context of the connected user.
+	</para>
+
+	<para>
+	An example of how privileges can be used is to assign the right to join clients to a Samba controlled
+	domain without providing root access to the server via smbd.
+	</para>
+
+	<para>
+	Please read the extended description provided in the Samba HOWTO documentation.
+	</para>
+
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/logondrive.xml b/docs-xml/smbdotconf/logon/logondrive.xml
new file mode 100644
index 00000000000..b32cfd70066
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/logondrive.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="logon drive"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter specifies the local path to which the home directory will be
+	connected (see <smbconfoption name="logon home"/>) and is only used by NT
+	Workstations.
+	</para>
+
+	<para>
+	Note that this option is only useful if Samba is set up as a logon server.
+	</para>
+</description>
+<value type="default"></value>
+<value type="example">h:</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/logonhome.xml b/docs-xml/smbdotconf/logon/logonhome.xml
new file mode 100644
index 00000000000..b7a10a98fca
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/logonhome.xml
@@ -0,0 +1,57 @@
+<samba:parameter name="logon home"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC.  
+	It allows you to do
+	</para>
+		
+	<para>
+	<prompt moreinfo="none">C:\&gt;</prompt><userinput moreinfo="none">NET USE H: /HOME</userinput>
+	</para>
+
+	<para>
+	from a command prompt, for example.
+	</para>
+
+	<para>
+	This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
+	</para>
+
+	<para>
+	This parameter can be used with Win9X workstations to ensure that roaming profiles are stored in a 
+	subdirectory of the user's 	home directory.  This is done in the following way:
+	</para>
+
+	<para>
+	<command moreinfo="none">logon home = \\%N\%U\profile</command>
+	</para>
+
+	<para>
+	This tells Samba to return the above string, with substitutions made when a client requests the info, generally 
+	in a NetUserGetInfo request.  Win9X clients truncate the info to \\server\share when a user does 
+  	 <command moreinfo="none">net use /home</command> but use the whole string when dealing with profiles.
+	</para>
+
+	<para>
+	Note that in prior versions of Samba, the <smbconfoption name="logon path"/> was returned rather than 
+	<parameter moreinfo="none">logon home</parameter>.  This broke <command moreinfo="none">net use /home</command> 
+	but allowed profiles outside the home directory. The current implementation is correct, and can be used for 
+	profiles if you use the above trick.
+	</para>
+
+	<para>
+	Disable this feature by setting <smbconfoption name="logon home">""</smbconfoption> - using the empty string.
+	</para>
+
+	<para>
+	This option is only useful if Samba is set up as a logon server.
+	</para>
+</description>
+
+<value type="default">\\%N\%U</value>
+<value type="example">\\remote_smb_server\%U</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/logonpath.xml b/docs-xml/smbdotconf/logon/logonpath.xml
new file mode 100644
index 00000000000..f0a3817106e
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/logonpath.xml
@@ -0,0 +1,70 @@
+<samba:parameter name="logon path"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter specifies the directory where roaming profiles (Desktop, NTuser.dat, etc) are 
+	stored.  Contrary to previous versions of these manual pages, it has nothing to do with Win 9X roaming
+	profiles.  To find out how to handle roaming profiles for Win 9X system, see the
+	<smbconfoption name="logon home"/> parameter.
+	</para>
+
+	<para>
+	This option takes the standard substitutions, allowing you to have separate logon scripts for each user or
+	machine.  It also specifies the directory from which the &quot;Application Data&quot;, <filename
+	moreinfo="none">desktop</filename>, <filename moreinfo="none">start menu</filename>, <filename
+	moreinfo="none">network neighborhood</filename>, <filename moreinfo="none">programs</filename> and other
+	folders, and their contents, are loaded and displayed on your Windows NT client.
+	</para>
+
+	<para>
+	The share and the path must be readable by the user for the preferences and directories to be loaded onto the
+	Windows NT client. The share must be writeable when the user logs in for the first time, in order that the
+	Windows NT client can create the NTuser.dat and other directories.  
+	Thereafter, the directories and any of the contents can, if required, be made read-only.  It is not advisable
+	that the NTuser.dat file be made read-only - rename it to NTuser.man to achieve the desired effect (a
+	<emphasis>MAN</emphasis>datory profile).
+	</para>
+
+	<para>
+	Windows clients can sometimes maintain a connection to the [homes] share, even though there is no user logged
+	in.  Therefore, it is vital that the logon path does not include a reference to the homes share (i.e. setting
+	this parameter to \\%N\homes\profile_path will cause problems).
+	</para>
+
+	<para>
+	This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
+	</para>
+
+	<warning><para>
+	Do not quote the value. Setting this as <quote>\\%N\profile\%U</quote>
+	will break profile handling. Where the tdbsam or ldapsam passdb backend
+	is used, at the time the user account is created the value configured
+	for this parameter is written to the passdb backend and that value will
+	over-ride the parameter value present in the smb.conf file. Any error
+	present in the passdb backend account record must be editted using the
+	appropriate tool (pdbedit on the command-line, or any other locally
+	provided system tool).
+	</para></warning>
+
+	<para>Note that this option is only useful if Samba is set up as a domain controller.</para>
+
+	<para>
+	Disable the use of roaming profiles by setting the value of this parameter to the empty string. For
+	example, <smbconfoption name="logon path">""</smbconfoption>. Take note that even if the default setting
+	in the smb.conf file is the empty string, any value specified in the user account settings in the passdb
+	backend will over-ride the effect of setting this parameter to null. Disabling of all roaming profile use
+	requires that the user account settings must also be blank.
+	</para>
+
+	<para>
+	An example of use is:
+<programlisting>
+logon path = \\PROFILESERVER\PROFILE\%U
+</programlisting>
+	</para>
+</description>
+<value type="default">\\%N\%U\profile</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/logonscript.xml b/docs-xml/smbdotconf/logon/logonscript.xml
new file mode 100644
index 00000000000..5b304514d06
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/logonscript.xml
@@ -0,0 +1,51 @@
+<samba:parameter name="logon script"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter specifies the batch file (<filename>.bat</filename>) or NT command file
+	(<filename>.cmd</filename>) to be downloaded and run on a machine when a user successfully logs in.  The file
+	must contain the DOS style CR/LF line endings. Using a DOS-style editor to create the file is recommended.
+	</para>
+		
+	<para>
+	The script must be a relative path to the <smbconfsection name="[netlogon]"/> service.  If the [netlogon]
+	service specifies a <smbconfoption name="path"/> of <filename
+	moreinfo="none">/usr/local/samba/netlogon</filename>, and <smbconfoption name="logon
+	script">STARTUP.BAT</smbconfoption>, then the file that will be downloaded is:
+<programlisting>
+	/usr/local/samba/netlogon/STARTUP.BAT
+</programlisting>
+	</para>
+
+	<para>
+	The contents of the batch file are entirely your choice.  A suggested command would be to add <command
+	moreinfo="none">NET TIME \\SERVER /SET /YES</command>, to force every machine to synchronize clocks with the
+	same time server.  Another use would be to add <command moreinfo="none">NET USE U: \\SERVER\UTILS</command>
+	for commonly used utilities, or 
+<programlisting>
+<userinput>NET USE Q: \\SERVER\ISO9001_QA</userinput>
+</programlisting> 
+	for example.
+	</para>
+
+	<para>
+	Note that it is particularly important not to allow write access to the [netlogon] share, or to grant users
+	write permission on the batch files in a secure environment, as this would allow the batch files to be
+	arbitrarily modified and security to be breached.	
+	</para>
+
+	<para>
+	This option takes the standard substitutions, allowing you to have separate logon scripts for each user or
+	machine.
+	</para>
+
+	<para>
+	This option is only useful if Samba is set up as a logon server.
+	</para>
+</description>
+<value type="default"></value>
+<value type="example">scripts\%U.bat</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/setprimarygroupscript.xml b/docs-xml/smbdotconf/logon/setprimarygroupscript.xml
new file mode 100644
index 00000000000..b348501e8b6
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/setprimarygroupscript.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="set primary group script"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>Thanks to the Posix subsystem in NT a Windows User has a
+	primary group in addition to the auxiliary groups.  This script
+	sets the primary group in the unix userdatase when an
+	administrator sets the primary group from the windows user
+	manager or when fetching a SAM with <command>net rpc
+	vampire</command>. <parameter>%u</parameter> will be replaced
+	with the user whose primary group is to be set. 
+	<parameter>%g</parameter> will be replaced with the group to
+	set.</para>
+</description>
+<value type="default"></value>
+<value type="example">/usr/sbin/usermod -g '%g' '%u'</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/logon/shutdownscript.xml b/docs-xml/smbdotconf/logon/shutdownscript.xml
new file mode 100644
index 00000000000..7e8ec8fd3aa
--- /dev/null
+++ b/docs-xml/smbdotconf/logon/shutdownscript.xml
@@ -0,0 +1,60 @@
+<samba:parameter name="shutdown script"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This a full path name to a script called by 
+	 <citerefentry><refentrytitle>smbd</refentrytitle> 
+        <manvolnum>8</manvolnum></citerefentry> that should 
+	start a shutdown procedure.</para>
+
+	<para>If the connected user posseses the <constant>SeRemoteShutdownPrivilege</constant>,
+	right, this command will be run as user.</para>
+
+	<para>The %z %t %r %f variables are expanded as follows:</para>
+	
+	<itemizedlist>
+		<listitem>
+			<para><parameter moreinfo="none">%z</parameter> will be substituted with the
+			shutdown message sent to the server.</para>
+		</listitem>
+		
+		<listitem>
+			<para><parameter moreinfo="none">%t</parameter> will be substituted with the
+			number of seconds to wait before effectively starting the
+			shutdown procedure.</para>
+		</listitem>
+		
+		<listitem>
+			<para><parameter moreinfo="none">%r</parameter> will be substituted with the
+			switch <emphasis>-r</emphasis>. It means reboot after shutdown
+			for NT.</para>
+		</listitem>
+		
+		<listitem>
+			<para><parameter moreinfo="none">%f</parameter> will be substituted with the
+			switch <emphasis>-f</emphasis>. It means force the shutdown
+			even if applications do not respond for NT.</para>
+		</listitem>
+	</itemizedlist>
+
+	<para>Shutdown script example:
+<programlisting format="linespecific">
+#!/bin/bash
+		
+$time=0
+let &quot;time/60&quot;
+let &quot;time++&quot;
+
+/sbin/shutdown $3 $4 +$time $1 &amp;
+</programlisting>
+        Shutdown does not return so we need to launch it in background.
+	</para>
+
+</description>
+<related>abort shutdown script</related>
+<value type="default"></value>
+<value type="example">/usr/local/samba/sbin/shutdown %m %t %r %f</value>
+
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/addsharecommand.xml b/docs-xml/smbdotconf/misc/addsharecommand.xml
new file mode 100644
index 00000000000..9eb50f3dc3b
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/addsharecommand.xml
@@ -0,0 +1,68 @@
+<samba:parameter name="add share command"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server
+	Manager.  The <parameter moreinfo="none">add share command</parameter> is used to define an external program
+	or script which will add a new service definition to <filename moreinfo="none">smb.conf</filename>.  In order
+	to successfully execute the <parameter moreinfo="none">add share command</parameter>, <command
+	moreinfo="none">smbd</command> requires that the administrator be connected using a root account (i.e.  uid == 0).
+	</para>
+
+    <para>
+    If the connected account has <literal>SeDiskOperatorPrivilege</literal>, scripts defined in
+    <parameter moreinfo="none">change share</parameter> parameter are executed as root.
+    </para>
+
+	<para>
+	When executed, <command moreinfo="none">smbd</command> will automatically invoke the
+	<parameter moreinfo="none">add share command</parameter> with five parameters.
+	</para>
+
+	<itemizedlist>
+		<listitem>
+			<para><parameter moreinfo="none">configFile</parameter> - the location of the global <filename
+			moreinfo="none">smb.conf</filename> file.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">shareName</parameter> - the name of the new share.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">pathName</parameter> - path to an **existing**
+			directory on disk.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">comment</parameter> - comment string to associate with the new
+			share.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">max
+			connections</parameter>
+			Number of maximum simultaneous connections to this
+			share.
+			</para>
+		</listitem>
+	</itemizedlist>
+
+	<para>
+	This parameter is only used for add file shares.  To add printer shares, see the <smbconfoption
+	name="addprinter command"/>.
+	</para>
+</description>
+
+<related>change share command</related>
+<related>delete share command</related>
+<value type="default"></value>
+<value type="example">/usr/local/bin/addshare</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/afsshare.xml b/docs-xml/smbdotconf/misc/afsshare.xml
new file mode 100644
index 00000000000..67d42d491f6
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/afsshare.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="afs share"
+	         context="S"
+			 type="boolean"
+		 advanced="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter controls whether special AFS features are enabled
+	for this share. If enabled, it assumes that the directory exported via
+	the <parameter>path</parameter> parameter is a local AFS import. The
+	special AFS features include the attempt to hand-craft an AFS token
+	if you enabled --with-fake-kaserver in configure.
+	</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/afsusernamemap.xml b/docs-xml/smbdotconf/misc/afsusernamemap.xml
new file mode 100644
index 00000000000..8e68ffec74e
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/afsusernamemap.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="afs username map"
+                 context="G"
+				 type="string"
+                 advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>If you are using the fake kaserver AFS feature, you might
+	want to hand-craft the usernames you are creating tokens for.
+	For example this is necessary if you have users from several domain
+	in your AFS Protection Database. One possible scheme to code users
+	as DOMAIN+User as it is done by winbind with the + as a separator.
+	</para>
+
+	<para>The mapped user name must contain the cell name to log into,
+	so without setting this parameter there will be no token.</para>
+</description>
+
+<value type="default"/>
+<value type="example">%u@afs.samba.org</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/available.xml b/docs-xml/smbdotconf/misc/available.xml
new file mode 100644
index 00000000000..4535bad1ce1
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/available.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="available"
+	         context="S"
+		 basic="1" advanced="1" print="1"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter lets you &quot;turn off&quot; a service. If 
+	<parameter moreinfo="none">available = no</parameter>, then <emphasis>ALL</emphasis> 
+	attempts to connect to the service will fail. Such failures are 
+	logged.</para>
+
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/changenotify.xml b/docs-xml/smbdotconf/misc/changenotify.xml
new file mode 100644
index 00000000000..9ff6f02f6fe
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/changenotify.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="change notify"
+                 context="S"
+				 type="boolean"
+                 advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies whether Samba should reply
+	to a client's file change notify requests.
+	</para>
+
+	<para>You should never need to change this parameter</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/changesharecommand.xml b/docs-xml/smbdotconf/misc/changesharecommand.xml
new file mode 100644
index 00000000000..5a42e225594
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/changesharecommand.xml
@@ -0,0 +1,70 @@
+<samba:parameter name="change share command"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server
+Manager.  The <parameter moreinfo="none">change share command</parameter> is used to define an external
+program or script which will modify an existing service definition in <filename
+moreinfo="none">smb.conf</filename>.  In order to successfully execute the <parameter moreinfo="none">change
+share command</parameter>, <command moreinfo="none">smbd</command> requires that the administrator be
+connected using a root account (i.e. uid == 0).
+	</para>
+
+	<para>
+	If the connected account has <literal>SeDiskOperatorPrivilege</literal>, scripts defined in
+	<parameter moreinfo="none">change share</parameter> parameter are executed as root.
+	</para>
+
+	<para>
+	When executed, <command moreinfo="none">smbd</command> will automatically invoke the
+	<parameter moreinfo="none">change share command</parameter> with five parameters.
+	</para>
+
+	<itemizedlist>
+		<listitem>
+			<para><parameter moreinfo="none">configFile</parameter> - the location
+			of the global <filename moreinfo="none">smb.conf</filename> file.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">shareName</parameter> - the name of the new
+			share.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">pathName</parameter> - path to an **existing**
+			directory on disk.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">comment</parameter> - comment string to associate
+			with the new share.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">max
+			connections</parameter>
+			Number of maximum simultaneous connections to this
+			share.
+			</para>
+		</listitem>
+	</itemizedlist>
+
+	<para>
+	This parameter is only used modify existing file shares definitions.  To modify
+	printer shares, use the &quot;Printers...&quot; folder as seen when browsing the Samba host.
+	</para>
+</description>
+
+<related>add share command</related>
+<related>delete share command</related>
+<value type="default"></value>
+<value type="example">/usr/local/bin/addshare</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/configfile.xml b/docs-xml/smbdotconf/misc/configfile.xml
new file mode 100644
index 00000000000..b1dc0d1b290
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/configfile.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="config file"
+                 context="G"
+				 type="string"
+		 hide="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This allows you to override the config file 
+	to use, instead of the default (usually <filename moreinfo="none">smb.conf</filename>). 
+	There is a chicken and egg problem here as this option is set 
+	in the config file!</para>
+
+	<para>For this reason, if the name of the config file has changed 
+	when the parameters are loaded then it will reload them from 
+	the new config file.</para>
+
+	<para>This option takes the usual substitutions, which can 
+	be very useful.</para>
+
+	<para>If the config file doesn't exist then it won't be loaded 
+	(allowing you to special case the config files of just a few 
+	clients).</para>
+</description>
+<value type="example">/usr/local/samba/lib/smb.conf.%m</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/copy.xml b/docs-xml/smbdotconf/misc/copy.xml
new file mode 100644
index 00000000000..608071e6e8c
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/copy.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="copy" context="S" hide="1" xmlns:samba="http://www.samba.org/samba/DTD/samba-doc" type="string">
+<description>
+	<para>This parameter allows you to &quot;clone&quot; service 
+	entries. The specified service is simply duplicated under the 
+	current service's name. Any parameters specified in the current 
+	section will override those in the section being copied.</para>
+
+	<para>This feature lets you set up a 'template' service and 
+	create similar services easily. Note that the service being 
+	copied must occur earlier in the configuration file than the 
+	service doing the copying.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">otherservice</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/defaultservice.xml b/docs-xml/smbdotconf/misc/defaultservice.xml
new file mode 100644
index 00000000000..ca986d460a9
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/defaultservice.xml
@@ -0,0 +1,30 @@
+<samba:parameter name="default service"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>default</synonym>
+<description>
+	<para>This parameter specifies the name of a service
+	which will be connected to if the service actually requested cannot
+	be found. Note that the square brackets are <emphasis>NOT</emphasis>
+	given in the parameter value (see example below).</para>
+
+	<para>There is no default value for this parameter. If this 
+	parameter is not given, attempting to connect to a nonexistent 
+	service results in an error.</para>
+
+	<para>
+	Typically the default service would be a <smbconfoption name="guest ok"/>, <smbconfoption
+	name="read-only"/> service.</para> <para>Also note that the apparent service name will be changed to equal
+	that of the requested service, this is very useful as it allows you to use macros like <parameter
+	moreinfo="none">%S</parameter> to make a wildcard service.
+	</para>
+
+	<para>Note also that any &quot;_&quot; characters in the name of the service 
+	used in the default service will get mapped to a &quot;/&quot;. This allows for
+	interesting things.</para>
+</description>
+<value type="default"></value>
+<value type="example">pub</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/deletereadonly.xml b/docs-xml/smbdotconf/misc/deletereadonly.xml
new file mode 100644
index 00000000000..de4f566a0ad
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/deletereadonly.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="delete readonly"
+		 context="S"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter allows readonly files to be deleted.  
+	This is not normal DOS semantics, but is allowed by UNIX.</para>
+		
+	<para>This option may be useful for running applications such 
+	as rcs, where UNIX file ownership prevents changing file 
+	permissions, and DOS semantics prevent deletion of a read only file.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/deletesharecommand.xml b/docs-xml/smbdotconf/misc/deletesharecommand.xml
new file mode 100644
index 00000000000..40eb6495dbf
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/deletesharecommand.xml
@@ -0,0 +1,50 @@
+<samba:parameter name="delete share command"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server
+	Manager.  The <parameter moreinfo="none">delete share command</parameter> is used to define an external
+	program or script which will remove an existing service definition from
+	<filename moreinfo="none">smb.conf</filename>.  In order to successfully execute the
+	<parameter moreinfo="none">delete share command</parameter>, <command moreinfo="none">smbd</command>
+	requires that the administrator be connected using a root account (i.e.  uid == 0).
+	</para>
+
+    <para>
+    If the connected account has <literal>SeDiskOperatorPrivilege</literal>, scripts defined in
+    <parameter moreinfo="none">change share</parameter> parameter are executed as root.
+    </para>
+
+	<para>
+	When executed, <command moreinfo="none">smbd</command> will automatically invoke the
+	<parameter moreinfo="none">delete share command</parameter> with two parameters.
+	</para>
+
+	<itemizedlist>
+		<listitem>
+			<para><parameter moreinfo="none">configFile</parameter> - the location
+			of the global <filename moreinfo="none">smb.conf</filename> file.
+			</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">shareName</parameter> - the name of
+			the existing service.
+			</para>
+		</listitem>
+	</itemizedlist>
+
+	<para>
+	This parameter is only used to remove file shares.  To delete printer shares,
+	see the <smbconfoption name="deleteprinter command"/>.
+	</para>
+</description>
+
+<related>add share command</related>
+<related>delete share command</related>
+<value type="default"></value>
+<value type="example">/usr/local/bin/delshare</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/dfreecachetime.xml b/docs-xml/smbdotconf/misc/dfreecachetime.xml
new file mode 100644
index 00000000000..2a8805e9488
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/dfreecachetime.xml
@@ -0,0 +1,27 @@
+<samba:parameter name="dfree cache time"
+	         context="S"
+			 type="integer"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>
+	The <parameter moreinfo="none">dfree cache time</parameter> should only be used on systems where a problem
+	occurs with the internal disk space calculations. This has been known to happen with Ultrix, but may occur
+	with other operating systems. The symptom that was seen was an error of &quot;Abort Retry Ignore&quot; at the
+	end of each directory listing.
+	</para>
+
+	<para>
+	This is a new parameter introduced in Samba version 3.0.21.  It specifies in seconds the time that smbd will
+	cache the output of a disk free query. If set to zero (the default) no caching is done. This allows a heavily
+	loaded server to prevent rapid spawning of <smbconfoption name="dfree command"/> scripts increasing the load.
+	</para>
+
+	<para>
+	By default this parameter is zero, meaning no caching will be done.
+	</para>
+
+</description>
+<value type="example">dfree cache time = 60</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/dfreecommand.xml b/docs-xml/smbdotconf/misc/dfreecommand.xml
new file mode 100644
index 00000000000..de60c5e0767
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/dfreecommand.xml
@@ -0,0 +1,60 @@
+<samba:parameter name="dfree command"
+	         context="S"
+			 type="string"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>
+	The <parameter moreinfo="none">dfree command</parameter> setting should only be used on systems where a
+	problem occurs with the internal disk space calculations. This has been known to happen with Ultrix, but may
+	occur with other operating systems. The symptom that was seen was an error of &quot;Abort Retry Ignore&quot;
+	at the end of each directory listing.
+	</para>
+
+	<para>
+	This setting allows the replacement of the internal routines to calculate the total disk space and amount
+	available with an external routine. The example below gives a possible script that might fulfill this
+	function.
+	</para>
+
+	<para>
+	In Samba version 3.0.21 this parameter has been changed to be a per-share parameter, and in addition the
+	parameter <smbconfoption name="dfree cache time"/> was added to allow the output of this script to be cached
+	for systems under heavy load.
+	</para>
+
+	<para>
+	The external program will be passed a single parameter indicating a directory in the filesystem being queried.
+	This will typically consist of the string <filename moreinfo="none">./</filename>. The script should return
+	two integers in ASCII. The first should be the total disk space in blocks, and the second should be the number
+	of available blocks. An optional third return value can give the block size in bytes. The default blocksize is
+	1024 bytes.
+	</para>
+
+	<para>
+	Note: Your script should <emphasis>NOT</emphasis> be setuid or setgid and should be owned by (and writeable
+	only by) root!
+	</para>
+
+	<para>
+	Where the script dfree (which must be made executable) could be:
+<programlisting format="linespecific"> 
+#!/bin/sh
+df $1 | tail -1 | awk '{print $(NF-4),$(NF-2)}'
+</programlisting>
+	or perhaps (on Sys V based systems):
+<programlisting format="linespecific"> 
+#!/bin/sh
+/usr/bin/df -k $1 | tail -1 | awk '{print $3&quot; &quot;$5}'
+</programlisting>
+	Note that you may have to replace the command names with full path names on some systems.
+	</para>
+
+	<para>
+	By default internal routines for determining the disk capacity and remaining space will be used.
+	</para>
+
+</description>
+<value type="example">/usr/local/samba/bin/dfree</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/dmapisupport.xml b/docs-xml/smbdotconf/misc/dmapisupport.xml
new file mode 100644
index 00000000000..fbd145d0480
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/dmapisupport.xml
@@ -0,0 +1,29 @@
+<samba:parameter name="dmapi support"
+                 context="S"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies whether Samba should use DMAPI to
+	determine whether a file is offline or not. This would typically
+	be used in conjunction with a hierarchical storage system that
+	automatically migrates files to tape.
+	</para>
+
+	<para>Note that Samba infers the status of a file by examining the
+	events that a DMAPI application has registered interest in. This
+	heuristic is satisfactory for a number of hierarchical storage
+	systems, but there may be system for which it will fail. In this
+	case, Samba may erroneously report files to be offline.
+	</para>
+
+	<para>This parameter is only available if a supported DMAPI
+	implementation was found at compilation time. It will only be used
+	if DMAPI is found to enabled on the system at run time.
+	</para>
+
+	<para>
+	</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/dontdescend.xml b/docs-xml/smbdotconf/misc/dontdescend.xml
new file mode 100644
index 00000000000..e12593939df
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/dontdescend.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="dont descend"
+	         context="S"
+			 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>There are certain directories on some systems 
+	(e.g., the <filename moreinfo="none">/proc</filename> tree under Linux) that are either not 
+	of interest to clients or are infinitely deep (recursive). This 
+	parameter allows you to specify a comma-delimited list of directories 
+	that the server should always show as empty.</para>
+
+	<para>Note that Samba can be very fussy about the exact format 
+	of the &quot;dont descend&quot; entries. For example you may need <filename moreinfo="none">
+	./proc</filename> instead of just <filename moreinfo="none">/proc</filename>. 
+	Experimentation is the best policy :-)  </para>
+</description>
+
+<value type="default"></value>
+<value type="example">/proc,/dev</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/dosfilemode.xml b/docs-xml/smbdotconf/misc/dosfilemode.xml
new file mode 100644
index 00000000000..ae3b475107b
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/dosfilemode.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="dos filemode"
+		 context="S"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para> The default behavior in Samba is to provide 
+	UNIX-like behavior where only the owner of a file/directory is 
+	able to change the permissions on it.  However, this behavior
+	is often confusing to  DOS/Windows users.  Enabling this parameter 
+	allows a user who has write access to the file (by whatever 
+	means) to modify the permissions (including ACL) on it.  Note that a user
+	belonging to the group owning the file will not be allowed to
+	change permissions if the group is only granted read access.
+	Ownership of the file/directory may also be changed.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/dosfiletimeresolution.xml b/docs-xml/smbdotconf/misc/dosfiletimeresolution.xml
new file mode 100644
index 00000000000..130f0fd91e9
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/dosfiletimeresolution.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="dos filetime resolution"
+		 context="S"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>Under the DOS and Windows FAT filesystem, the finest 
+	granularity on time resolution is two seconds. Setting this parameter 
+	for a share causes Samba to round the reported time down to the 
+	nearest two second boundary when a query call that requires one second 
+	resolution is made to <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>.</para>
+
+	<para>This option is mainly used as a compatibility option for Visual 
+	C++ when used against Samba shares. If oplocks are enabled on a 
+	share, Visual C++ uses two different time reading calls to check if a 
+	file has changed since it was last read. One of these calls uses a
+	one-second granularity, the other uses a two second granularity. As
+	the two second call rounds any odd second down, then if the file has a
+	timestamp of an odd number of seconds then the two timestamps will not
+	match and Visual C++ will keep reporting the file has changed. Setting
+	this option causes the two timestamps to match, and Visual C++ is
+	happy.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/dosfiletimes.xml b/docs-xml/smbdotconf/misc/dosfiletimes.xml
new file mode 100644
index 00000000000..90f93a03e8b
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/dosfiletimes.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="dos filetimes"
+		 context="S"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>Under DOS and Windows, if a user can write to a 
+	file they can change the timestamp on it. Under POSIX semantics, 
+	only the owner of the file or root may change the timestamp. By 
+	default, Samba runs with POSIX semantics and refuses to change the 
+	timestamp on a file if the user <command moreinfo="none">smbd</command> is acting 
+	on behalf of is not the file owner. Setting this option to <constant>
+	yes</constant> allows DOS semantics and <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> will change the file 
+	timestamp as DOS requires. Due to changes in Microsoft Office 2000 and beyond,
+	the default for this parameter has been changed from "no" to "yes" in Samba 3.0.14
+	and above. Microsoft Excel will display dialog box warnings about the file being
+	changed by another user if this parameter is not set to "yes" and files are being
+	shared between users.
+	</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/fakedirectorycreatetimes.xml b/docs-xml/smbdotconf/misc/fakedirectorycreatetimes.xml
new file mode 100644
index 00000000000..974b6f0f30c
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/fakedirectorycreatetimes.xml
@@ -0,0 +1,34 @@
+<samba:parameter name="fake directory create times"
+		 context="S"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>NTFS and Windows VFAT file systems keep a create 
+	time for all files and directories. This is not the same as the 
+	ctime - status change time - that Unix keeps, so Samba by default 
+	reports the earliest of the various times Unix does keep. Setting 
+	this parameter for a share causes Samba to always report midnight 
+	1-1-1980 as the create time for directories.</para>
+
+	<para>This option is mainly used as a compatibility option for 
+	Visual C++ when used against Samba shares. Visual C++ generated 
+	makefiles have the object directory as a dependency for each object 
+	file, and a make rule to create the directory. Also, when NMAKE 
+	compares timestamps it uses the creation time when examining a 
+	directory. Thus the object directory will be created if it does not 
+	exist, but once it does exist it will always have an earlier 
+	timestamp than the object files it contains.</para>
+
+	<para>However, Unix time semantics mean that the create time 
+	reported by Samba will be updated whenever a file is created or 
+	or deleted in the directory.  NMAKE finds all object files in 
+	the object directory.  The timestamp of the last one built is then 
+	compared to the timestamp of the object directory.  If the 
+	directory's timestamp if newer, then all object files
+	will be rebuilt.  Enabling this option 
+	ensures directories always predate their contents and an NMAKE build 
+	will proceed as expected.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/followsymlinks.xml b/docs-xml/smbdotconf/misc/followsymlinks.xml
new file mode 100644
index 00000000000..c0fd920bf9c
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/followsymlinks.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="follow symlinks"
+	         context="S"
+			 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter allows the Samba administrator to stop <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>	from following symbolic links in a particular share. Setting this 
+	parameter to <constant>no</constant> prevents any file or directory that is a symbolic link from being 
+	followed (the user will get an 	error).  This option is very useful to stop users from adding a symbolic 
+	link to <filename moreinfo="none">/etc/passwd</filename> in their home directory for instance.  However 
+	it will slow filename lookups down slightly.
+	</para>
+
+	<para>
+	This option is enabled (i.e. <command moreinfo="none">smbd</command> will follow symbolic links) by default.
+	</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/fstype.xml b/docs-xml/smbdotconf/misc/fstype.xml
new file mode 100644
index 00000000000..c7df18c38b3
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/fstype.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="fstype"
+	         context="S"
+			 type="string"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter allows the administrator to configure the string that specifies the type of filesystem a share 
+	is using that is reported by <citerefentry><refentrytitle>smbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry> 
+	when a client queries the filesystem type for a share. The default type is <constant>NTFS</constant> for compatibility 
+	with Windows NT but this can be changed to other strings such as <constant>Samba</constant> or <constant>FAT</constant> 
+	if required.
+	</para>
+</description>
+<value type="default">NTFS</value>
+<value type="example">Samba</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/homedirmap.xml b/docs-xml/smbdotconf/misc/homedirmap.xml
new file mode 100644
index 00000000000..37b46ee0b69
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/homedirmap.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="homedir map"
+	         context="G"
+			 type="string"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>
+	If <smbconfoption name="nis homedir"/> is <constant>yes</constant>, and <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> is also acting 	as a Win95/98 <parameter moreinfo="none">logon server</parameter> 
+	then this parameter specifies the NIS (or YP) map from which the server for the user's 	home directory should be extracted.  
+	At present, only the Sun auto.home map format is understood. The form of the map is:
+<programlisting>
+<command moreinfo="none">username server:/some/file/system</command>
+</programlisting>
+	and the program will extract the servername from before the first ':'.  There should probably be a better parsing system 
+	that copes with different map formats and also Amd (another automounter) maps.
+	</para>
+		
+	<note><para>
+	A working NIS client is required on the system for this option to work.
+	</para></note>
+</description>
+<related>nis homedir</related>
+<related>domain logons</related>
+
+<value type="default"></value>
+<value type="example">amd.homedir</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/include.xml b/docs-xml/smbdotconf/misc/include.xml
new file mode 100644
index 00000000000..1a08b49464d
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/include.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="include"
+	         context="G"
+		 type="string"
+		 hide="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This allows you to include one config file inside another.  The file is included literally, as though typed 
+	in place.
+	</para>
+
+	<para>
+	It takes the standard substitutions, except <parameter moreinfo="none">%u</parameter>, 
+	<parameter moreinfo="none">%P</parameter> and <parameter moreinfo="none">%S</parameter>.
+	</para>
+</description>
+
+	<para>
+		Note: This option can not be set inside registry
+		configurations.
+	</para>
+
+<value type="default"></value>
+<value type="example">/usr/local/samba/lib/admin_smb.conf</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/kernelchangenotify.xml b/docs-xml/smbdotconf/misc/kernelchangenotify.xml
new file mode 100644
index 00000000000..ef932201a10
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/kernelchangenotify.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="kernel change notify"
+                 context="S"
+				 type="boolean"
+                 advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies whether Samba should ask the 
+	kernel for change notifications in directories so that
+	SMB clients can refresh whenever the data on the server changes.
+	</para>
+
+	<para>This parameter is only used when your kernel supports 
+	change notification to user programs using the inotify interface.
+	</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/lockdirectory.xml b/docs-xml/smbdotconf/misc/lockdirectory.xml
new file mode 100644
index 00000000000..cbe10d5b8d7
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/lockdirectory.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="lock directory"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>lock dir</synonym>
+<description>
+	<para>This option specifies the directory where lock 
+	files will be placed.  The lock files are used to implement the 
+	<smbconfoption name="max connections"/> option.
+	</para>
+
+	<para>
+		Note: This option can not be set inside registry
+		configurations.
+	</para>
+</description>
+
+<value type="default">${prefix}/var/locks</value>
+<value type="example">/var/run/samba/locks</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/magicoutput.xml b/docs-xml/smbdotconf/misc/magicoutput.xml
new file mode 100644
index 00000000000..47e514fdce2
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/magicoutput.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="magic output"
+		 context="S"
+		 type="string"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter specifies the name of a file which will contain output created by a magic script (see the 
+	<smbconfoption name="magic script"/> parameter below).
+	</para>
+
+	<warning><para>If two clients use the same <parameter moreinfo="none">magic script
+	</parameter> in the same directory the output file content is undefined.
+	</para></warning>
+</description>
+
+<value type="default">&lt;magic script name&gt;.out</value>
+<value type="example">myfile.txt</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/magicscript.xml b/docs-xml/smbdotconf/misc/magicscript.xml
new file mode 100644
index 00000000000..b621f00c389
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/magicscript.xml
@@ -0,0 +1,30 @@
+<samba:parameter name="magic script"
+		 context="S"
+		 type="string"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies the name of a file which, 
+	if opened, will be executed by the server when the file is closed. 
+	This allows a UNIX script to be sent to the Samba host and 
+	executed on behalf of the connected user.</para>
+
+	<para>Scripts executed in this way will be deleted upon 
+	completion assuming that the user has the appropriate level 
+	of privilege and the file permissions allow the deletion.</para>
+
+	<para>If the script generates output, output will be sent to 
+	the file specified by the <smbconfoption name="magic output"/>
+	parameter (see above).</para>
+
+	<para>Note that some shells are unable to interpret scripts 
+	containing CR/LF instead of CR as 
+	the end-of-line marker. Magic scripts must be executable 
+	<emphasis>as is</emphasis> on the host, which for some hosts and 
+	some shells will require filtering at the DOS end.</para>
+
+	<para>Magic scripts are <emphasis>EXPERIMENTAL</emphasis> and 
+		should <emphasis>NOT</emphasis> be relied upon.</para>
+</description>
+<value type="default"></value>
+<value type="example">user.csh</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/messagecommand.xml b/docs-xml/smbdotconf/misc/messagecommand.xml
new file mode 100644
index 00000000000..91df58ab5d1
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/messagecommand.xml
@@ -0,0 +1,79 @@
+<samba:parameter name="message command"
+	         context="G"
+			 type="string"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This specifies what command to run when the 
+	server receives a WinPopup style message.</para>
+
+	<para>This would normally be a command that would 
+	deliver the message somehow. How this is to be done is 
+	up to your imagination.</para>
+
+	<para>An example is:
+<programlisting>
+<command moreinfo="none">message command = csh -c 'xedit %s;rm %s' &amp;</command>
+</programlisting>
+	</para>
+
+	<para>This delivers the message using <command moreinfo="none">xedit</command>, then 
+	removes it afterwards. <emphasis>NOTE THAT IT IS VERY IMPORTANT 
+	THAT THIS COMMAND RETURN IMMEDIATELY</emphasis>. That's why I 
+	have the '&amp;' on the end. If it doesn't return immediately then 
+	your PCs may freeze when sending messages (they should recover 
+	after 30 seconds, hopefully).</para>
+
+	<para>All messages are delivered as the global guest user. 
+	The command takes the standard substitutions, although <parameter moreinfo="none">
+	%u</parameter> won't work (<parameter moreinfo="none">%U</parameter> may be better 
+	in this case).</para>
+
+	<para>Apart from the standard substitutions, some additional 
+	ones apply. In particular:</para>
+
+	<itemizedlist>
+		<listitem>
+			<para><parameter moreinfo="none">%s</parameter> = the filename containing 
+				the message.</para>
+		</listitem>
+			
+		<listitem>
+			<para><parameter moreinfo="none">%t</parameter> = the destination that 
+				the message was sent to (probably the server name).</para>
+		</listitem>
+
+		<listitem>
+			<para><parameter moreinfo="none">%f</parameter> = who the message 
+				is from.</para>
+		</listitem>
+	</itemizedlist>
+
+	<para>You could make this command send mail, or whatever else 
+	takes your fancy. Please let us know of any really interesting 
+	ideas you have.</para>
+
+	<para>
+	Here's a way of sending the messages as mail to root:
+<programlisting>
+<command moreinfo="none">message command = /bin/mail -s 'message from %f on %m' root &lt; %s; rm %s</command>
+</programlisting>
+	</para>
+
+	<para>If you don't have a message command then the message 
+	won't be delivered and Samba will tell the sender there was 
+	an error. Unfortunately WfWg totally ignores the error code 
+	and carries on regardless, saying that the message was delivered.
+	</para>
+
+	<para>
+	If you want to silently delete it then try:
+<programlisting>
+<command moreinfo="none">message command = rm %s</command>
+</programlisting>
+	</para>
+	
+</description>
+<value type="default"></value>
+<value type="example">csh -c 'xedit %s; rm %s' &amp;</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/nishomedir.xml b/docs-xml/smbdotconf/misc/nishomedir.xml
new file mode 100644
index 00000000000..45c451197e4
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/nishomedir.xml
@@ -0,0 +1,33 @@
+<samba:parameter name="nis homedir"
+	         context="G"
+			 type="boolean"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>Get the home share server from a NIS map. For 
+	UNIX systems that use an automounter, the user's home directory 
+	will often be mounted on a workstation on demand from a remote 
+	server. </para>
+
+	<para>When the Samba logon server is not the actual home directory 
+	server, but is mounting the home directories via NFS then two 
+	network hops would be required to access the users home directory 
+	if the logon server told the client to use itself as the SMB server 
+	for home directories (one over SMB and one over NFS). This can 
+	be very slow.</para>
+
+	<para>This option allows Samba to return the home share as 
+	being on a different server to the logon server and as 
+	long as a Samba daemon is running on the home directory server, 
+	it will be mounted on the Samba client directly from the directory 
+	server. When Samba is returning the home share to the client, it 
+	will consult the NIS map specified in
+	<smbconfoption name="homedir map"/> and return the server 
+	listed there.</para>
+
+	<para>Note that for this option to work there must be a working 
+	NIS system and the Samba server with this option must also 
+	be a logon server.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/panicaction.xml b/docs-xml/smbdotconf/misc/panicaction.xml
new file mode 100644
index 00000000000..b8ffa704589
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/panicaction.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="panic action"
+		 context="G"
+		 type="string"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This is a Samba developer option that allows a 
+	system command to be called when either <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> or <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>	crashes. This is usually used to 
+	draw attention to the fact that a problem occurred.
+	</para>
+</description>
+
+<value type="default"></value>
+<value type="example">&quot;/bin/sleep 90000&quot;</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/piddirectory.xml b/docs-xml/smbdotconf/misc/piddirectory.xml
new file mode 100644
index 00000000000..c9f05338ace
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/piddirectory.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="pid directory"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This option specifies the directory where pid files will be placed.  
+	</para>
+</description>
+
+<value type="default">${prefix}/var/locks</value>
+<value type="example">pid directory = /var/run/</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/postexec.xml b/docs-xml/smbdotconf/misc/postexec.xml
new file mode 100644
index 00000000000..3f0cb5073ac
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/postexec.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="postexec"
+	         context="S"
+			 type="string"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This option specifies a command to be run 
+	whenever the service is disconnected. It takes the usual 
+	substitutions. The command may be run as the root on some 
+	systems.</para>
+
+	<para>An interesting example may be to unmount server 
+	resources:</para>
+
+<para><command moreinfo="none">postexec = /etc/umount /cdrom</command></para>
+</description>
+<related>preexec</related> 
+
+<value type="default"></value>
+<value type="example">echo \&quot;%u disconnected from %S from %m (%I)\&quot; &gt;&gt; /tmp/log</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/preexec.xml b/docs-xml/smbdotconf/misc/preexec.xml
new file mode 100644
index 00000000000..6608c830501
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/preexec.xml
@@ -0,0 +1,29 @@
+<samba:parameter name="preexec"
+		 context="S"
+		 type="string"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <synonym>exec</synonym>
+<description>
+	<para>This option specifies a command to be run whenever 
+	the service is connected to. It takes the usual substitutions.</para>
+
+	<para>An interesting example is to send the users a welcome 
+	message every time they log in. Maybe a message of the day? Here 
+	is an example:</para>
+
+	<para>
+	<command moreinfo="none">preexec = csh -c 'echo \&quot;Welcome to %S!\&quot; |
+	/usr/local/samba/bin/smbclient -M %m -I %I' &amp; </command>
+	</para>
+
+	<para>Of course, this could get annoying after a while :-)</para>
+
+	<para>
+	See also <smbconfoption name="preexec close"/> and <smbconfoption name="postexec"/>.
+	</para>
+</description>
+
+<value type="default"></value>
+<value type="example">echo \&quot;%u connected to %S from %m (%I)\&quot; &gt;&gt; /tmp/log</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/preexecclose.xml b/docs-xml/smbdotconf/misc/preexecclose.xml
new file mode 100644
index 00000000000..7a477e16fea
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/preexecclose.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="preexec close"
+		 context="S"
+		 type="boolean"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This boolean option controls whether a non-zero return code from <smbconfoption name="preexec"/> 
+	should close the service being connected to.
+	</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/preload.xml b/docs-xml/smbdotconf/misc/preload.xml
new file mode 100644
index 00000000000..94905a67ef7
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/preload.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="preload"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>auto services</synonym>
+<description>
+	<para>This is a list of services that you want to be 
+	automatically added to the browse lists. This is most useful 
+	for homes and printers services that would otherwise not be 
+	visible.</para>
+
+	<para>
+	Note that if you just want all printers in your 
+	printcap file loaded then the <smbconfoption name="load printers"/>
+	 option is easier.
+	</para>
+</description>
+
+<value type="default"></value>
+<value type="example">fred lp colorlp</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/registryshares.xml b/docs-xml/smbdotconf/misc/registryshares.xml
new file mode 100644
index 00000000000..76c83e194c8
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/registryshares.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="registry shares"
+                 context="G"
+		 type="bool"
+		 advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This turns on or off support for share definitions read from
+	registry. Shares defined in <emphasis>smb.conf</emphasis> take
+	precedence over shares with the same name defined in
+	registry. See the section on registry-based configuration
+	for details. 
+	</para>
+
+	<para>
+		Note that this parameter defaults to <emphasis>no</emphasis>,
+		but it is set to <emphasis>yes</emphasis> when
+		 <parameter>config backend</parameter> is set
+		to <emphasis>registry</emphasis>.
+	</para>
+</description>
+<value type="default">no</value>
+<value type="example">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/remoteannounce.xml b/docs-xml/smbdotconf/misc/remoteannounce.xml
new file mode 100644
index 00000000000..f23968b5015
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/remoteannounce.xml
@@ -0,0 +1,42 @@
+<samba:parameter name="remote announce"
+	         context="G"
+		 advanced="1" developer="1"
+		 type="list"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This option allows you to setup <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>to periodically announce itself 
+	to arbitrary IP addresses with an arbitrary workgroup name.
+	</para>
+
+	<para>
+	This is useful if you want your Samba server to appear in a remote workgroup for 
+	which the normal browse propagation rules don't work. The remote workgroup can be 
+	anywhere that you can send IP packets to.
+	</para>
+
+	<para>
+	For example:
+<programlisting>
+<command moreinfo="none">remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF</command>
+</programlisting>
+	the above line would cause <command moreinfo="none">nmbd</command> to announce itself 
+	to the two given IP addresses using the given workgroup names. If you leave out the 
+	workgroup name then the one given in the <smbconfoption name="workgroup"/> parameter 
+	is used instead.
+	</para>
+
+	<para>
+	The IP addresses you choose would normally be the broadcast addresses of the remote 
+	networks, but can also be the IP addresses of known browse masters if your network 
+	config is that stable.
+	</para>
+
+	<para>
+	See the chapter on Network Browsing in the Samba-HOWTO book.
+	</para>
+</description>
+
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/remotebrowsesync.xml b/docs-xml/smbdotconf/misc/remotebrowsesync.xml
new file mode 100644
index 00000000000..c966c95be07
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/remotebrowsesync.xml
@@ -0,0 +1,50 @@
+<samba:parameter name="remote browse sync"
+	         context="G"
+		 advanced="1" developer="1"
+		 type="list"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This option allows you to setup <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> to periodically request 
+	synchronization of browse lists with the master browser of a Samba 
+	server that is on a remote segment. This option will allow you to 
+	gain browse lists for multiple workgroups across routed networks. This 
+	is done in a manner that does not work with any non-Samba servers.
+	</para>
+
+	<para>
+	This is useful if you want your Samba server and all local 
+	clients to appear in a remote workgroup for which the normal browse 
+	propagation rules don't work. The remote workgroup can be anywhere 
+	that you can send IP packets to.
+	</para>
+
+	<para>
+	For example:
+<programlisting>
+<parameter>remote browse sync = 192.168.2.255 192.168.4.255</parameter>
+</programlisting>
+	the above line would cause <command>nmbd</command> to request the master browser on the 
+	specified subnets or addresses to synchronize their browse lists with 
+	the local server.
+	</para>
+
+	<para>
+	The IP addresses you choose would normally be the broadcast 
+	addresses of the remote networks, but can also be the IP addresses 
+	of known browse masters if your network config is that stable. If 
+	a machine IP address is given Samba makes NO attempt to validate 
+	that the remote machine is available, is listening, nor that it 
+	is in fact the browse master on its segment.
+	</para>
+
+	<para>
+	The <smbconfoption name="remote browse sync"/> may be used on networks
+	where there is no WINS server, and may be used on disjoint networks where
+	each network has its own WINS server.
+	</para>
+</description>
+
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/resetonzerovc.xml b/docs-xml/smbdotconf/misc/resetonzerovc.xml
new file mode 100644
index 00000000000..3276cf51439
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/resetonzerovc.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="reset on zero vc"
+		 context="G"
+		 type="boolean"
+		 advanced="1" developer="0"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This boolean option controls whether an incoming session setup
+	should kill other connections coming from the same IP. This matches
+        the default Windows 2003 behaviour.
+
+	Setting this parameter to yes becomes necessary when you have a flaky
+	network and windows decides to reconnect while the old connection
+	still has files with share modes open. These files become inaccessible
+	over the new connection.
+
+	The client sends a zero VC on the new connection, and Windows 2003
+	kills all other connections coming from the same IP. This way the
+	locked files are accessible again.
+
+	Please be aware that enabling this option will kill connections behind
+	a masquerading router.
+
+	</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/rootpostexec.xml b/docs-xml/smbdotconf/misc/rootpostexec.xml
new file mode 100644
index 00000000000..4aff4f03341
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/rootpostexec.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="root postexec"
+		 context="S"
+		 type="string"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This is the same as the <parameter moreinfo="none">postexec</parameter>
+	parameter except that the command is run as root. This is useful for 
+	unmounting filesystems (such as CDROMs) after a connection is closed.
+	</para>
+</description>
+
+<related>postexec</related>
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/rootpreexec.xml b/docs-xml/smbdotconf/misc/rootpreexec.xml
new file mode 100644
index 00000000000..89d10ec53b4
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/rootpreexec.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="root preexec"
+		 context="S"
+		 type="string"
+		 advanced="1" wizard="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This is the same as the <parameter moreinfo="none">preexec</parameter>
+	parameter except that the command is run as root. This is useful for 
+	mounting filesystems (such as CDROMs) when a connection is opened.
+	</para>
+</description>
+
+<related>preexec</related>
+<related>preexec close</related>
+
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/rootpreexecclose.xml b/docs-xml/smbdotconf/misc/rootpreexecclose.xml
new file mode 100644
index 00000000000..e0f11b567a8
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/rootpreexecclose.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="root preexec close"
+		 context="S"
+		 type="boolean"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This is the same as the <parameter moreinfo="none">preexec close
+	</parameter> parameter except that the command is run as root.</para>
+</description>
+
+<related>preexec</related>
+<related>preexec close</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/setdirectory.xml b/docs-xml/smbdotconf/misc/setdirectory.xml
new file mode 100644
index 00000000000..5e7b379a046
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/setdirectory.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="set directory"
+	         context="S"
+			 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	If <command moreinfo="none">set directory = no</command>, then 	users of the 
+	service may not use the setdir command to change directory.
+	</para>
+
+	<para>
+	The <command moreinfo="none">setdir</command> command is only implemented 
+	in the Digital Pathworks client. See the Pathworks documentation 
+	for details.
+	</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/socketaddress.xml b/docs-xml/smbdotconf/misc/socketaddress.xml
new file mode 100644
index 00000000000..7566380e709
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/socketaddress.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="socket address"
+	         context="G"
+			 type="string"
+		 developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This option allows you to control what 
+	address Samba will listen for connections on. This is used to 
+	support multiple virtual interfaces on the one server, each 
+	with a different configuration.</para>
+		
+	<para>By default Samba will accept connections on any 
+		address.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">192.168.2.20</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/timeoffset.xml b/docs-xml/smbdotconf/misc/timeoffset.xml
new file mode 100644
index 00000000000..1afc514e60d
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/timeoffset.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="time offset"
+	         context="G"
+			 type="integer"
+		 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter is a setting in minutes to add 
+	to the normal GMT to local time conversion. This is useful if 
+	you are serving a lot of PCs that have incorrect daylight 
+	saving time handling.</para>
+</description>
+
+<value type="default">0</value>
+<value type="example">60</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/usershareallowguests.xml b/docs-xml/smbdotconf/misc/usershareallowguests.xml
new file mode 100644
index 00000000000..738f3a11bad
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/usershareallowguests.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="usershare allow guests"
+	         context="G"
+		 basic="1" advanced="1"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter controls whether user defined shares are allowed
+	to be accessed by non-authenticated users or not. It is the equivalent
+	of allowing people who can create a share the option of setting
+	<parameter moreinfo="none">guest ok = yes</parameter> in a share
+	definition. Due to the security sensitive nature of this the default
+	is set to off.</para>
+
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/usersharemaxshares.xml b/docs-xml/smbdotconf/misc/usersharemaxshares.xml
new file mode 100644
index 00000000000..ed76283e614
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/usersharemaxshares.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="usershare max shares"
+	         context="G"
+		 basic="1" advanced="1"
+		 type="integer"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies the number of user defined shares
+	that are allowed to be created by users belonging to the group owning the
+	usershare directory. If set to zero (the default) user defined shares are ignored.
+	</para>
+
+</description>
+<value type="default">0</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/usershareowneronly.xml b/docs-xml/smbdotconf/misc/usershareowneronly.xml
new file mode 100644
index 00000000000..4aab43a0daf
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/usershareowneronly.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="usershare owner only"
+	         context="G"
+		 basic="1" advanced="1"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter controls whether the pathname exported by
+	a user defined shares must be owned by the user creating the
+	user defined share or not. If set to True (the default) then
+	smbd checks that the directory path being shared is owned by
+	the user who owns the usershare file defining this share and
+	refuses to create the share if not. If set to False then no
+	such check is performed and any directory path may be exported
+	regardless of who owns it.
+	</para>
+
+</description>
+<value type="default">True</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/usersharepath.xml b/docs-xml/smbdotconf/misc/usersharepath.xml
new file mode 100644
index 00000000000..9e0bfe57d51
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/usersharepath.xml
@@ -0,0 +1,33 @@
+<samba:parameter name="usershare path"
+	         context="G"
+		 basic="1" advanced="1"
+		 type="string"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies the absolute path of the directory on the
+	filesystem used to store the user defined share definition files.
+	This directory must be owned by root, and have no access for
+	other, and be writable only by the group owner. In addition the
+	"sticky" bit must also be set, restricting rename and delete to
+	owners of a file (in the same way the /tmp directory is usually configured).
+	Members of the group owner of this directory are the users allowed to create
+	usershares. If this parameter is undefined then no user defined
+	shares are allowed.
+	</para>
+	<para>
+	For example, a valid usershare directory might be /usr/local/samba/lib/usershares,
+	set up as follows.
+	</para>
+	<para>
+	<programlisting>
+	ls -ld /usr/local/samba/lib/usershares/
+	drwxrwx--T  2 root power_users 4096 2006-05-05 12:27 /usr/local/samba/lib/usershares/
+	</programlisting>
+	</para>
+	<para>
+	In this case, only members of the group "power_users" can create user defined shares.
+	</para>
+
+</description>
+<value type="default">NULL</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/usershareprefixallowlist.xml b/docs-xml/smbdotconf/misc/usershareprefixallowlist.xml
new file mode 100644
index 00000000000..bacc2e9530e
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/usershareprefixallowlist.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="usershare prefix allow list"
+	         context="G"
+		 basic="1" advanced="1"
+		 type="string"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies a list of absolute pathnames
+	the root of which are allowed to be exported by user defined share definitions.
+	If the pathname exported doesn't start with one of the strings in this
+	list the user defined share will not be allowed. This allows the Samba
+	administrator to restrict the directories on the system that can be
+	exported by user defined shares.
+	</para>
+	<para>
+	If there is a "usershare prefix deny list" and also a
+	"usershare prefix allow list" the deny list is processed
+	first, followed by the allow list, thus leading to the most
+	restrictive interpretation.
+	</para>
+
+</description>
+<value type="default">NULL</value>
+<value type="example">/home /data /space</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/usershareprefixdenylist.xml b/docs-xml/smbdotconf/misc/usershareprefixdenylist.xml
new file mode 100644
index 00000000000..75d4ba9afc1
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/usershareprefixdenylist.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="usershare prefix deny list"
+	         context="G"
+		 basic="1" advanced="1"
+		 type="string"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies a list of absolute pathnames
+	the root of which are NOT allowed to be exported by user defined share definitions.
+	If the pathname exported starts with one of the strings in this
+	list the user defined share will not be allowed. Any pathname not
+	starting with one of these strings will be allowed to be exported
+	as a usershare. This allows the Samba administrator to restrict the
+	directories on the system that can be exported by user defined shares.
+	</para>
+	<para>
+	If there is a "usershare prefix deny list" and also a
+	"usershare prefix allow list" the deny list is processed
+	first, followed by the allow list, thus leading to the most
+	restrictive interpretation.
+	</para>
+
+</description>
+<value type="default">NULL</value>
+<value type="example">/etc /dev /private</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/usersharetemplateshare.xml b/docs-xml/smbdotconf/misc/usersharetemplateshare.xml
new file mode 100644
index 00000000000..efe2e81d22c
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/usersharetemplateshare.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="usershare template share"
+	         context="G"
+		 basic="1" advanced="1"
+		 type="string"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>User defined shares only have limited possible parameters
+	such as path, guest ok etc. This parameter allows usershares to
+	"cloned" from an existing share. If "usershare template share"
+	is set to the name of an existing share, then all usershares
+	created have their defaults set from the parameters set on this
+	share.
+	</para>
+	<para>
+	The target share may be set to be invalid for real file
+	sharing by setting the parameter "-valid = False" on the template
+	share definition. This causes it not to be seen as a real exported
+	share but to be able to be used as a template for usershares.
+	</para>
+
+</description>
+<value type="default">NULL</value>
+<value type="example">template_share</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/utmp.xml b/docs-xml/smbdotconf/misc/utmp.xml
new file mode 100644
index 00000000000..67c02cc64c0
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/utmp.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="utmp"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This boolean parameter is only available if Samba has been configured and compiled  
+	with the option <command moreinfo="none">--with-utmp</command>. If set to 
+	 <constant>yes</constant> then Samba will attempt to add utmp or utmpx records 
+	(depending on the UNIX system) whenever a connection is made to a Samba server. 
+	Sites may use this to record the user connecting to a Samba share.
+	</para>
+
+	<para>
+	Due to the requirements of the utmp record, we 	are required to create a unique 
+	identifier for the incoming user.  Enabling this option creates an n^2 	algorithm 
+	to find this number.  This may impede performance on large installations. 
+	</para>
+</description>
+
+<related>utmp directory</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/utmpdirectory.xml b/docs-xml/smbdotconf/misc/utmpdirectory.xml
new file mode 100644
index 00000000000..b02fc93bf0f
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/utmpdirectory.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="utmp directory"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter is only available if Samba has 
+	been configured and compiled with the option <command moreinfo="none">
+	--with-utmp</command>. It specifies a directory pathname that is
+	used to store the utmp or utmpx files (depending on the UNIX system) that
+	record user connections to a Samba server. By default this is 
+	not set, meaning the system will use whatever utmp file the 
+	native system is set to use (usually 
+	<filename moreinfo="none">/var/run/utmp</filename> on Linux).</para>
+</description>
+
+<related>utmp</related>
+
+<value type="default"><comment>Determined automatically</comment></value>
+<value type="example">/var/run/utmp</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/valid.xml b/docs-xml/smbdotconf/misc/valid.xml
new file mode 100644
index 00000000000..2f92f6367cc
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/valid.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="-valid"
+		 context="S"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para> This parameter indicates whether a share is 
+	valid and thus can be used. When this parameter is set to false, 
+	the share will be in no way visible nor accessible.
+	</para>
+
+	<para>
+	This option should not be 
+	used by regular users but might be of help to developers. 
+	Samba uses this option internally to mark shares as deleted.
+	</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/volume.xml b/docs-xml/smbdotconf/misc/volume.xml
new file mode 100644
index 00000000000..d3385e704c6
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/volume.xml
@@ -0,0 +1,12 @@
+<samba:parameter name="volume"
+		 context="S"
+		 type="string"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This allows you to override the volume label 
+	returned for a share. Useful for CDROMs with installation programs 
+	that insist on a particular volume label.</para>
+</description>
+
+<value type="default"><comment>the name of the share</comment></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/widelinks.xml b/docs-xml/smbdotconf/misc/widelinks.xml
new file mode 100644
index 00000000000..fb707c1950a
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/widelinks.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="wide links"
+		 context="S"
+		 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter controls whether or not links 
+	in the UNIX file system may be followed by the server. Links 
+	that point to areas within the directory tree exported by the 
+	server are always allowed; this parameter controls access only 
+	to areas that are outside the directory tree being exported.</para>
+
+	<para>Note that setting this parameter can have a negative 
+	effect on your server performance due to the extra system calls 
+	that Samba has to  do in order to perform the link checks.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/misc/wtmpdirectory.xml b/docs-xml/smbdotconf/misc/wtmpdirectory.xml
new file mode 100644
index 00000000000..f58b5225734
--- /dev/null
+++ b/docs-xml/smbdotconf/misc/wtmpdirectory.xml
@@ -0,0 +1,23 @@
+<samba:parameter name="wtmp directory"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter is only available if Samba has been configured and compiled with the option <command moreinfo="none">
+	--with-utmp</command>. It specifies a directory pathname that is used to store the wtmp or wtmpx files (depending on 
+	the UNIX system) that record user connections to a Samba server. The difference with the utmp directory is the fact 
+	that user info is kept after a user has logged out.
+	</para>
+		
+	<para>
+	By default this is not set, meaning the system will use whatever utmp file the 	native system is set to use (usually 
+	<filename moreinfo="none">/var/run/wtmp</filename> on Linux).
+	</para>
+</description>
+
+<related>utmp</related>
+<value type="default"/>
+<value type="example">/var/log/wtmp</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/addportcommand.xml b/docs-xml/smbdotconf/printing/addportcommand.xml
new file mode 100644
index 00000000000..294ea8e188b
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/addportcommand.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="add port command"
+                 context="G"
+				 type="string"
+		 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>Samba 3.0.23 introduced support for adding printer ports
+	remotely using the Windows &quot;Add Standard TCP/IP Port Wizard&quot;.
+	This option defines an external program to be executed when
+	smbd receives a request to add a new Port to the system.
+	The script is passed two parameters:</para>
+		
+    <itemizedlist>
+	<listitem><para><parameter moreinfo="none">port name</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">device URI</parameter></para></listitem>
+    </itemizedlist>
+		
+    <para>The deviceURI is in the for of socket://&lt;hostname&gt;[:&lt;portnumber&gt;]
+	or lpd://&lt;hostname&gt;/&lt;queuename&gt;.</para>
+</description>
+
+<related>enum ports command</related>
+
+<value type="default"></value>
+<value type="example">/etc/samba/scripts/addport.sh</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/addprintercommand.xml b/docs-xml/smbdotconf/printing/addprintercommand.xml
new file mode 100644
index 00000000000..ed3c5aa3be2
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/addprintercommand.xml
@@ -0,0 +1,62 @@
+<samba:parameter name="add printer command"
+                 context="G"
+				 type="string"
+		 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>With the introduction of MS-RPC based printing
+    support for Windows NT/2000 clients in Samba 2.2, The MS Add
+    Printer Wizard (APW) icon is now also available in the 
+    &quot;Printers...&quot; folder displayed a share listing.  The APW
+    allows for printers to be add remotely to a Samba or Windows 
+    NT/2000 print server.</para>
+		
+    <para>For a Samba host this means that the printer must be 
+    physically added to the underlying printing system.  The <parameter moreinfo="none">add 
+    printer command</parameter> defines a script to be run which 
+    will perform the necessary operations for adding the printer
+    to the print system and to add the appropriate service definition 
+    to the  <filename moreinfo="none">smb.conf</filename> file in order that it can be 
+    shared by <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry>.</para>
+		
+    <para>The <parameter moreinfo="none">addprinter command</parameter> is
+    automatically invoked with the following parameter (in 
+    order):</para>
+		
+    <itemizedlist>
+	<listitem><para><parameter moreinfo="none">printer name</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">share name</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">port name</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">driver name</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">location</parameter></para></listitem>
+	<listitem><para><parameter moreinfo="none">Windows 9x driver location</parameter></para></listitem>
+    </itemizedlist>
+		
+    <para>All parameters are filled in from the PRINTER_INFO_2 structure sent 
+    by the Windows NT/2000 client with one exception.  The &quot;Windows 9x
+    driver location&quot; parameter is included for backwards compatibility
+    only.  The remaining fields in the structure are generated from answers
+    to the APW questions.</para>
+
+    <para>Once the <parameter moreinfo="none">addprinter command</parameter> has 
+    been executed, <command moreinfo="none">smbd</command> will reparse the <filename moreinfo="none">
+    smb.conf</filename> to determine if the share defined by the APW
+    exists.  If the sharename is still invalid, then <command moreinfo="none">smbd
+    </command> will return an ACCESS_DENIED error to the client.</para>
+
+    <para>
+    The &quot;add printer command&quot; program can output a single line of text,
+    which Samba will set as the port the new printer is connected to. 
+    If this line isn't output, Samba won't reload its printer shares.
+    </para>
+		
+</description>
+
+<related>deleteprinter command</related>
+<related>printing</related>
+<related>show add printer wizard</related>
+
+<value type="default"></value>
+<value type="example">/usr/bin/addprinter</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/cupsoptions.xml b/docs-xml/smbdotconf/printing/cupsoptions.xml
new file mode 100644
index 00000000000..616e2732669
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/cupsoptions.xml
@@ -0,0 +1,35 @@
+<samba:parameter name="cups options"
+                 context="S"
+		 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This parameter is only applicable if <smbconfoption name="printing"/> is 
+    set to <constant>cups</constant>.  Its value is a free form string of options
+    passed directly to the cups library.  
+    </para>
+
+   <para>
+   You can pass any generic print option known to CUPS (as listed
+   in the CUPS "Software Users' Manual").  You can also pass any printer
+   specific option (as listed in "lpoptions -d printername -l")
+   valid for the target queue.
+   Multiple parameters should be space-delimited name/value pairs according to
+   the PAPI text option ABNF specification. Collection values
+   ("name={a=... b=... c=...}") are stored with the curley brackets intact.
+   </para>
+
+   <para>
+   You should set this parameter to <constant>raw</constant> if your CUPS server 
+   <filename>error_log</filename> file contains messages such as
+   "Unsupported format 'application/octet-stream'" when printing from a Windows client 
+   through Samba.  It is no longer necessary to enable
+   system wide raw printing in <filename>/etc/cups/mime.{convs,types}</filename>.
+   </para>
+
+</description>
+
+<value type="default">""</value>
+<value type="example">"raw media=a4"</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/cupsserver.xml b/docs-xml/smbdotconf/printing/cupsserver.xml
new file mode 100644
index 00000000000..b31db33eac5
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/cupsserver.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="cups server"
+                 context="G"
+		 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This parameter is only applicable if <smbconfoption name="printing"/> is set to <constant>cups</constant>.
+    </para>
+
+   <para>
+   If set, this option overrides the ServerName option in the CUPS <filename>client.conf</filename>. This is 
+   necessary if you have virtual samba servers that connect to different CUPS daemons.
+   </para>
+
+   <para>Optionally, a port can be specified by separating the server name 
+	   and port number with a colon. If no port was specified, 
+	   the default port for IPP (631) will be used.
+   </para>
+	  
+</description>
+
+<value type="default">""</value>
+<value type="example">mycupsserver</value>
+<value type="example">mycupsserver:1631</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/defaultdevmode.xml b/docs-xml/smbdotconf/printing/defaultdevmode.xml
new file mode 100644
index 00000000000..218ddcb3561
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/defaultdevmode.xml
@@ -0,0 +1,38 @@
+<samba:parameter name="default devmode"
+                 context="S"
+				 type="boolean"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter is only applicable to <smbconfoption name="printable"/> services.
+    When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba
+    server has a Device Mode which defines things such as paper size and
+    orientation and duplex settings.  The device mode can only correctly be
+    generated by the printer driver itself (which can only be executed on a
+    Win32 platform).  Because smbd is unable to execute the driver code
+    to generate the device mode, the default behavior is to set this field
+    to NULL.
+    </para>
+
+    <para>Most problems with serving printer drivers to Windows NT/2k/XP clients
+    can be traced to a problem with the generated device mode.  Certain drivers
+    will do things such as crashing the client's Explorer.exe with a NULL devmode.
+    However, other printer drivers can cause the client's spooler service
+    (spoolsv.exe) to die if the devmode was not created by the driver itself
+    (i.e. smbd generates a default devmode).
+    </para>
+
+    <para>This parameter should be used with care and tested with the printer
+    driver in question.  It is better to leave the device mode to NULL
+    and let the Windows client set the correct values.  Because drivers do not
+    do this all the time, setting <command moreinfo="none">default devmode = yes</command>
+    will instruct smbd to generate a default one.
+    </para>
+
+    <para>For more information on Windows NT/2k printing and Device Modes,
+    see the <ulink url="http://msdn.microsoft.com/">MSDN documentation</ulink>.
+</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/deleteprintercommand.xml b/docs-xml/smbdotconf/printing/deleteprintercommand.xml
new file mode 100644
index 00000000000..b48ab5700d1
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/deleteprintercommand.xml
@@ -0,0 +1,36 @@
+<samba:parameter name="deleteprinter command"
+                 context="G"
+				 type="string"
+		 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>With the introduction of MS-RPC based printer
+    support for Windows NT/2000 clients in Samba 2.2, it is now 
+    possible to delete printer at run time by issuing the 
+    DeletePrinter() RPC call.</para>
+		
+    <para>For a Samba host this means that the printer must be 
+    physically deleted from underlying printing system.  The 
+    <smbconfoption name="deleteprinter command"/> defines a script to be run which 
+    will perform the necessary operations for removing the printer
+    from the print system and from <filename moreinfo="none">smb.conf</filename>.
+    </para>
+		
+    <para>The <smbconfoption name="deleteprinter command"/> is 
+    automatically called with only one parameter: <smbconfoption name="printer name"/>.
+	</para>
+		
+    <para>Once the <smbconfoption name="deleteprinter command"/> has 
+    been executed, <command moreinfo="none">smbd</command> will reparse the <filename moreinfo="none">
+    smb.conf</filename> to associated printer no longer exists.  
+    If the sharename is still valid, then <command moreinfo="none">smbd
+    </command> will return an ACCESS_DENIED error to the client.</para>
+</description>
+
+<related>addprinter command</related>
+<related>printing</related>
+<related>show add printer wizard</related>
+
+<value type="default"></value>
+<value type="example">/usr/bin/removeprinter</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/disablespoolss.xml b/docs-xml/smbdotconf/printing/disablespoolss.xml
new file mode 100644
index 00000000000..9367eae8b31
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/disablespoolss.xml
@@ -0,0 +1,23 @@
+<samba:parameter name="disable spoolss"
+                 context="G"
+				 type="boolean"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>Enabling this parameter will disable Samba's support
+    for the SPOOLSS set of MS-RPC's and will yield identical behavior
+    as Samba 2.0.x.  Windows NT/2000 clients will downgrade to using
+    Lanman style printing commands. Windows 9x/ME will be unaffected by
+    the parameter. However, this will also disable the ability to upload
+    printer drivers to a Samba server via the Windows NT Add Printer
+    Wizard or by using the NT printer properties dialog window.  It will
+    also disable the capability of Windows NT/2000 clients to download
+    print drivers from the Samba host upon demand.
+    <emphasis>Be very careful about enabling this parameter.</emphasis>
+</para>
+</description>
+
+<related>use client driver</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/enumportscommand.xml b/docs-xml/smbdotconf/printing/enumportscommand.xml
new file mode 100644
index 00000000000..41db7395446
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/enumportscommand.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="enumports command"
+                 context="G"
+				 type="string"
+		 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>The concept of a &quot;port&quot; is fairly foreign
+    to UNIX hosts.  Under Windows NT/2000 print servers, a port
+    is associated with a port monitor and generally takes the form of
+    a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
+    (i.e. LPD Port Monitor, etc...).  By default, Samba has only one
+    port defined--<constant>&quot;Samba Printer Port&quot;</constant>.  Under 
+    Windows NT/2000, all printers must have a valid port name.  
+    If you wish to have a list of ports displayed (<command moreinfo="none">smbd
+    </command> does not use a port name for anything) other than 
+    the default <constant>&quot;Samba Printer Port&quot;</constant>, you 
+    can define <parameter moreinfo="none">enumports command</parameter> to point to
+    a program which should generate a list of ports, one per line,
+    to standard output.  This listing will then be used in response
+    to the level 1 and 2 EnumPorts() RPC.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">/usr/bin/listports</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/forceprintername.xml b/docs-xml/smbdotconf/printing/forceprintername.xml
new file mode 100644
index 00000000000..453feedc781
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/forceprintername.xml
@@ -0,0 +1,39 @@
+<samba:parameter name="force printername"
+                 context="S"
+		 type="boolean"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>When printing from Windows NT (or later), 
+    each printer in <filename>smb.conf</filename> has two 
+    associated names which can be used by the client.  The first
+    is the sharename (or shortname) defined in smb.conf.  This
+    is the only printername available for use by Windows 9x clients.
+    The second name associated with a printer can be seen when 
+    browsing to the "Printers" (or "Printers and Faxes") folder 
+    on the Samba server.  This is referred to simply as the printername
+    (not to be confused with the <parameter>printer name</parameter> option).
+    </para>
+
+    <para>When assigning a new driver to a printer on a remote 
+    Windows compatible print server such as Samba, the Windows client
+    will rename the printer to match the driver name just uploaded.
+    This can result in confusion for users when multiple 
+    printers are bound to the same driver.  To prevent Samba from
+    allowing the printer's printername to differ from the sharename
+    defined in smb.conf, set <parameter>force printername = yes</parameter>.
+    </para>
+
+    <para>Be aware that enabling this parameter may affect migrating
+    printers from a Windows server to Samba since Windows has no way to 
+    force the sharename and printername to match.</para>
+
+    <para>It is recommended that this parameter's value not be changed
+    once the printer is in use by clients as this could cause a user
+    not be able to delete printer connections from their local Printers 
+    folder.</para>
+
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/iprintserver.xml b/docs-xml/smbdotconf/printing/iprintserver.xml
new file mode 100644
index 00000000000..81c7ca55a24
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/iprintserver.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="iprint server"
+                 context="G"
+		 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This parameter is only applicable if <smbconfoption name="printing"/> is set to <constant>iprint</constant>.
+    </para>
+
+   <para>
+   If set, this option overrides the ServerName option in the CUPS <filename>client.conf</filename>. This is 
+   necessary if you have virtual samba servers that connect to different CUPS daemons.
+   </para>
+</description>
+
+<value type="default">""</value>
+<value type="example">MYCUPSSERVER</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/loadprinters.xml b/docs-xml/smbdotconf/printing/loadprinters.xml
new file mode 100644
index 00000000000..7e40ebee182
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/loadprinters.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="load printers"
+                 context="G"
+				 type="boolean"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>A boolean variable that controls whether all 
+    printers in the printcap will be loaded for browsing by default. 
+    See the <smbconfoption name="printers"/> section for 
+    more details.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/lppausecommand.xml b/docs-xml/smbdotconf/printing/lppausecommand.xml
new file mode 100644
index 00000000000..0bb66226f2d
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/lppausecommand.xml
@@ -0,0 +1,39 @@
+<samba:parameter name="lppause command"
+                 context="S"
+				 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter specifies the command to be 
+    executed on the server host in order to stop printing or spooling 
+    a specific print job.</para>
+
+    <para>This command should be a program or script which takes 
+    a printer name and job number to pause the print job. One way 
+    of implementing this is by using job priorities, where jobs 
+    having a too low priority won't be sent to the printer.</para>
+
+    <para>If a <parameter moreinfo="none">%p</parameter> is given then the printer name 
+    is put in its place. A <parameter moreinfo="none">%j</parameter> is replaced with 
+    the job number (an integer).  On HPUX (see <parameter moreinfo="none">printing=hpux
+    </parameter>), if the <parameter moreinfo="none">-p%p</parameter> option is added 
+    to the lpq command, the job will show up with the correct status, i.e. 
+    if the job priority is lower than the set fence priority it will 
+    have the PAUSED status, whereas if  the priority is equal or higher it 
+    will have the SPOOLED or PRINTING status.</para>
+
+    <para>Note that it is good practice to include the absolute path 
+    in the lppause command as the PATH may not be available to the server.</para>
+</description>
+
+<related>printing</related>
+
+<value type="default"><comment>Currently no default value is given to 
+    this string, unless the value of the <smbconfoption name="printing"/> 
+    parameter is <constant>SYSV</constant>, in which case the default is : 
+    <command moreinfo="none">lp -i %p-%j -H hold</command> or if the value of the 
+    <parameter moreinfo="none">printing</parameter> parameter is 
+    <constant>SOFTQ</constant>, then the default is: 
+    <command moreinfo="none">qstat -s -j%j -h</command>. </comment></value>
+<value type="example">/usr/bin/lpalt %p-%j -p0</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/lpqcachetime.xml b/docs-xml/smbdotconf/printing/lpqcachetime.xml
new file mode 100644
index 00000000000..5a64937906a
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/lpqcachetime.xml
@@ -0,0 +1,29 @@
+<samba:parameter name="lpq cache time"
+		 context="G"
+		 type="integer"
+		 developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This controls how long lpq info will be cached 
+	for to prevent the <command moreinfo="none">lpq</command> command being called too 
+	often. A separate cache is kept for each variation of the <command moreinfo="none">
+	lpq</command> command used by the system, so if you use different 
+	<command moreinfo="none">lpq</command> commands for different users then they won't
+	share cache information.</para>
+
+	<para>The cache files are stored in <filename moreinfo="none">/tmp/lpq.xxxx</filename> 
+	where xxxx is a hash of the <command moreinfo="none">lpq</command> command in use.</para>
+
+	<para>The default is 30 seconds, meaning that the cached results 
+	of a previous identical <command moreinfo="none">lpq</command> command will be used 
+	if the cached data is less than 30 seconds old. A large value may 
+	be advisable if your <command moreinfo="none">lpq</command> command is very slow.</para>
+
+<para>A value of 0 will disable caching completely.</para>
+</description>
+
+<related>printing</related>
+
+<value type="default">30</value>
+<value type="example">10</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/lpqcommand.xml b/docs-xml/smbdotconf/printing/lpqcommand.xml
new file mode 100644
index 00000000000..8c06b758985
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/lpqcommand.xml
@@ -0,0 +1,42 @@
+<samba:parameter name="lpq command"
+                 context="S"
+				 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+    <para>This parameter specifies the command to be 
+    executed on the server host in order to obtain <command moreinfo="none">lpq
+    </command>-style printer status information.</para>
+
+    <para>This command should be a program or script which 
+    takes a printer name as its only parameter and outputs printer 
+    status information.</para>
+
+    <para>Currently nine styles of printer status information 
+    are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ. 
+    This covers most UNIX systems. You control which type is expected 
+    using the <parameter moreinfo="none">printing =</parameter> option.</para>
+
+    <para>Some clients (notably Windows for Workgroups) may not 
+    correctly send the connection number for the printer they are 
+    requesting status information about. To get around this, the 
+    server reports on the first printer service connected to by the 
+    client. This only happens if the connection number sent is invalid.</para>
+
+    <para>If a <parameter moreinfo="none">%p</parameter> is given then the printer name 
+    is put in its place. Otherwise it is placed at the end of the 
+    command.</para>
+
+    <para>Note that it is good practice to include the absolute path 
+    in the <parameter moreinfo="none">lpq command</parameter> as the <envar>$PATH
+    </envar> may not be available to the server.  When compiled with
+    the CUPS libraries, no <parameter moreinfo="none">lpq command</parameter> is
+    needed because smbd will make a library call to obtain the 
+	print queue listing.</para>
+</description>
+
+<related>printing</related>
+
+<value type="example">/usr/bin/lpq -P%p</value>
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/lpresumecommand.xml b/docs-xml/smbdotconf/printing/lpresumecommand.xml
new file mode 100644
index 00000000000..706a999b1f7
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/lpresumecommand.xml
@@ -0,0 +1,38 @@
+<samba:parameter name="lpresume command"
+                 context="S"
+				 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter specifies the command to be 
+    executed on the server host in order to restart or continue 
+    printing or spooling a specific print job.</para>
+
+    <para>This command should be a program or script which takes 
+    a printer name and job number to resume the print job. See 
+    also the <smbconfoption name="lppause command"/> parameter.</para>
+
+    <para>If a <parameter moreinfo="none">%p</parameter> is given then the printer name 
+    is put in its place. A <parameter moreinfo="none">%j</parameter> is replaced with 
+    the job number (an integer).</para>
+		
+    <para>Note that it is good practice to include the absolute path 
+    in the <parameter moreinfo="none">lpresume command</parameter> as the PATH may not 
+    be available to the server.</para>
+		
+    <para>See also the <smbconfoption name="printing"/> parameter.</para>
+
+    <para>Default: Currently no default value is given 
+    to this string, unless the value of the <parameter moreinfo="none">printing</parameter> 
+    parameter is <constant>SYSV</constant>, in which case the default is:</para>
+
+    <para><command moreinfo="none">lp -i %p-%j -H resume</command></para>
+
+    <para>or if the value of the <parameter moreinfo="none">printing</parameter> parameter 
+    is <constant>SOFTQ</constant>, then the default is:</para>
+
+    <para><command moreinfo="none">qstat -s -j%j -r</command></para>
+</description>
+
+<value type="example">/usr/bin/lpalt %p-%j -p2</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/lprmcommand.xml b/docs-xml/smbdotconf/printing/lprmcommand.xml
new file mode 100644
index 00000000000..0b8375f94d9
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/lprmcommand.xml
@@ -0,0 +1,36 @@
+<samba:parameter name="lprm command"
+                 context="S"
+				 type="string"
+				 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter specifies the command to be 
+    executed on the server host in order to delete a print job.</para>
+
+    <para>This command should be a program or script which takes 
+    a printer name and job number, and deletes the print job.</para>
+
+    <para>If a <parameter moreinfo="none">%p</parameter> is given then the printer name 
+    is put in its place. A <parameter moreinfo="none">%j</parameter> is replaced with 
+    the job number (an integer).</para>
+
+    <para>Note that it is good practice to include the absolute 
+    path in the <parameter moreinfo="none">lprm command</parameter> as the PATH may not be 
+    available to the server.</para>
+
+	<para>
+	Examples of use are:
+<programlisting>
+lprm command = /usr/bin/lprm -P%p %j
+
+or
+
+lprm command = /usr/bin/cancel %p-%j
+</programlisting>
+	</para>
+
+</description>
+<related>printing</related>
+
+<value type="default"> determined by printing parameter</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/maxprintjobs.xml b/docs-xml/smbdotconf/printing/maxprintjobs.xml
new file mode 100644
index 00000000000..51801620e8b
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/maxprintjobs.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="max print jobs"
+                 context="S"
+		 print="1"
+		 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter limits the maximum number of 
+    jobs allowable in a Samba printer queue at any given moment.
+    If this number is exceeded, <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> will remote &quot;Out of Space&quot; to the client.
+	</para>
+</description>
+
+<value type="default">1000</value>
+<value type="example">5000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/maxreportedprintjobs.xml b/docs-xml/smbdotconf/printing/maxreportedprintjobs.xml
new file mode 100644
index 00000000000..34a5eb71c1a
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/maxreportedprintjobs.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="max reported print jobs"
+                 context="S"
+				 type="integer"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This parameter limits the maximum number of jobs displayed in a port monitor for 
+    Samba printer queue at any given moment. If this number is exceeded, the excess 
+    jobs will not be shown. A value of zero means there is no limit on the number of 
+    print jobs reported.
+    </para>
+</description>
+
+<related>max print jobs</related>
+
+<value type="default">0</value>
+<value type="example">1000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/os2drivermap.xml b/docs-xml/smbdotconf/printing/os2drivermap.xml
new file mode 100644
index 00000000000..a578d3af443
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/os2drivermap.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="os2 driver map"
+                 context="G"
+		 advanced="1" developer="1"
+		 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>The parameter is used to define the absolute
+    path to a file containing a mapping of Windows NT printer driver
+    names to OS/2 printer driver names.  The format is:</para>
+		
+    <para>&lt;nt driver name&gt; = &lt;os2 driver name&gt;.&lt;device name&gt;</para>
+		
+    <para>For example, a valid entry using the HP LaserJet 5
+    printer driver would appear as <command moreinfo="none">HP LaserJet 5L = LASERJET.HP 
+    LaserJet 5L</command>.</para>
+		
+    <para>
+    The need for the file is due to the printer driver namespace problem described in 
+    the chapter on Classical Printing in the Samba3-HOWTO book.  For more
+    details on OS/2 clients, please refer to chapter on other clients in the Samba3-HOWTO book.
+    </para>
+</description>
+<value type="default"/>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/printable.xml b/docs-xml/smbdotconf/printing/printable.xml
new file mode 100644
index 00000000000..73aa533ed3b
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/printable.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="printable"
+                 context="S"
+				 print="1"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>print ok</synonym>
+<description>
+    <para>If this parameter is <constant>yes</constant>, then 
+    clients may open, write to and submit spool files on the directory 
+    specified for the service. </para>
+		
+    <para>Note that a printable service will ALWAYS allow writing 
+    to the service path (user privileges permitting) via the spooling 
+    of print data. The <smbconfoption name="read only"/> parameter controls only non-printing access to 
+    the resource.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/printcapcachetime.xml b/docs-xml/smbdotconf/printing/printcapcachetime.xml
new file mode 100644
index 00000000000..7dcd1b62d47
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/printcapcachetime.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="printcap cache time"
+	context="G"
+	type="integer"
+		 print="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option specifies the number of seconds before the printing
+    subsystem is again asked for the known printers.  If the value
+    is greater than 60 the initial waiting time is set to 60 seconds
+    to allow an earlier first rescan of the printing subsystem.
+    </para>
+
+    <para>Setting this parameter to 0 disables any rescanning for new 
+    or removed printers after the initial startup.
+    </para>
+</description>
+
+
+<value type="default">750</value>
+<value type="example">600</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/printcapname.xml b/docs-xml/smbdotconf/printing/printcapname.xml
new file mode 100644
index 00000000000..90c575f31c2
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/printcapname.xml
@@ -0,0 +1,55 @@
+<samba:parameter name="printcap name"
+	context="S"
+	type="string"
+		 print="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>printcap</synonym>
+<description>
+    <para>
+	This parameter may be used to override the compiled-in default printcap name used by the server (usually
+	<filename moreinfo="none"> /etc/printcap</filename>). See the discussion of the <link
+	linkend="PRINTERSSECT">[printers]</link> section above for reasons why you might want to do this.
+	</para>
+
+    <para>
+	To use the CUPS printing interface set <command moreinfo="none">printcap name = cups </command>. This should
+	be supplemented by an addtional setting <smbconfoption name="printing">cups</smbconfoption> in the [global]
+	section.  <command moreinfo="none">printcap name = cups</command> will use the  &quot;dummy&quot; printcap
+	created by CUPS, as specified in your CUPS configuration file.
+    </para>
+
+    <para>
+	On System V systems that use <command moreinfo="none">lpstat</command> to 
+    list available printers you can use <command moreinfo="none">printcap name = lpstat
+    </command> to automatically obtain lists of available printers. This 
+    is the default for systems that define SYSV at configure time in 
+    Samba (this includes most System V based systems). If <parameter moreinfo="none">
+    printcap name</parameter> is set to <command moreinfo="none">lpstat</command> on 
+    these systems then Samba will launch <command moreinfo="none">lpstat -v</command> and 
+    attempt to parse the output to obtain a printer list.
+	</para>
+
+    <para>
+	A minimal printcap file would look something like this:
+<programlisting format="linespecific">
+print1|My Printer 1
+print2|My Printer 2
+print3|My Printer 3
+print4|My Printer 4
+print5|My Printer 5
+</programlisting>
+    where the '|' separates aliases of a printer. The fact that the second alias has a space in
+	it gives a hint to Samba that it's a comment.
+	</para>
+
+    <note><para>
+	Under AIX the default printcap name is <filename moreinfo="none">/etc/qconfig</filename>. Samba will
+	assume the file is in AIX <filename moreinfo="none">qconfig</filename> format if the string <filename
+	moreinfo="none">qconfig</filename> appears in the printcap filename.
+	</para></note>
+
+</description>
+	
+<value type="default">/etc/printcap</value>
+<value type="example">/etc/myprintcap</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/printcommand.xml b/docs-xml/smbdotconf/printing/printcommand.xml
new file mode 100644
index 00000000000..461d6de8e38
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/printcommand.xml
@@ -0,0 +1,88 @@
+<samba:parameter name="print command"
+                 context="S"
+				 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>After a print job has finished spooling to 
+    a service, this command will be used via a <command moreinfo="none">system()</command> 
+    call to process the spool file. Typically the command specified will 
+    submit the spool file to the host's printing subsystem, but there 
+    is no requirement that this be the case. The server will not remove 
+    the spool file, so whatever command you specify should remove the 
+    spool file when it has been processed, otherwise you will need to 
+    manually remove old spool files.</para>
+		
+    <para>The print command is simply a text string. It will be used 
+    verbatim after macro substitutions have been made:</para>
+
+	<para>%s, %f - the path to the spool
+    file name</para>
+
+    <para>%p - the appropriate printer 
+    name</para>
+
+    <para>%J - the job 
+    name as transmitted by the client.</para>
+
+    <para>%c - The number of printed pages
+    of the spooled job (if known).</para>
+
+    <para>%z - the size of the spooled
+    print job (in bytes)</para>
+
+    <para>The print command <emphasis>MUST</emphasis> contain at least 
+    one occurrence of <parameter moreinfo="none">%s</parameter> or <parameter moreinfo="none">%f
+    </parameter> - the <parameter moreinfo="none">%p</parameter> is optional. At the time 
+    a job is submitted, if no printer name is supplied the <parameter moreinfo="none">%p
+    </parameter> will be silently removed from the printer command.</para>
+
+    <para>If specified in the [global] section, the print command given 
+    will be used for any printable service that does not have its own 
+    print command specified.</para>
+
+    <para>If there is neither a specified print command for a 
+    printable service nor a global print command, spool files will 
+    be created but not processed and (most importantly) not removed.</para>
+
+    <para>Note that printing may fail on some UNIXes from the 
+    <constant>nobody</constant> account. If this happens then create 
+    an alternative guest account that can print and set the <smbconfoption name="guest account"/> 
+    in the [global] section.</para>
+
+    <para>You can form quite complex print commands by realizing 
+    that they are just passed to a shell. For example the following 
+    will log a print job, print the file, then remove it. Note that 
+    ';' is the usual separator for command in shell scripts.</para>
+
+    <para><command moreinfo="none">print command = echo Printing %s &gt;&gt; 
+    /tmp/print.log; lpr -P %p %s; rm %s</command></para>
+
+    <para>You may have to vary this command considerably depending 
+    on how you normally print files on your system. The default for 
+    the parameter varies depending on the setting of the <smbconfoption name="printing"/>
+	parameter.</para>
+
+    <para>Default: For <command moreinfo="none">printing = BSD, AIX, QNX, LPRNG 
+    or PLP :</command></para>
+    <para><command moreinfo="none">print command = lpr -r -P%p %s</command></para>
+
+    <para>For <command moreinfo="none">printing = SYSV or HPUX :</command></para>
+    <para><command moreinfo="none">print command = lp -c -d%p %s; rm %s</command></para>
+
+    <para>For <command moreinfo="none">printing = SOFTQ :</command></para>
+    <para><command moreinfo="none">print command = lp -d%p -s %s; rm %s</command></para>
+
+    <para>For printing = CUPS :   If SAMBA is compiled against
+    libcups, then <smbconfoption name="printcap">cups</smbconfoption> 
+    uses the CUPS API to
+    submit jobs, etc.  Otherwise it maps to the System V
+    commands with the -oraw option for printing, i.e. it
+    uses <command moreinfo="none">lp -c -d%p -oraw; rm %s</command>.   
+    With <command moreinfo="none">printing = cups</command>,
+    and if SAMBA is compiled against libcups, any manually 
+	set print command will be ignored.</para>
+</description>
+
+<value type="example">/usr/local/samba/bin/myprintscript %p %s</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/printername.xml b/docs-xml/smbdotconf/printing/printername.xml
new file mode 100644
index 00000000000..fad127cad19
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/printername.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="printer name"
+                 context="S"
+		 print="1"
+		 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <synonym>printer</synonym>
+<description>
+    <para>
+	This parameter specifies the name of the printer to which print jobs spooled through a printable service
+	will be sent.
+	</para>
+
+    <para>
+	If specified in the [global] section, the printer name given will be used for any printable service that
+	does not have its own printer name specified.
+	</para>
+
+	<para>
+	The default value of the <smbconfoption name="printer name"/> may be <literal>lp</literal> on many
+	systems.
+	</para>
+</description>
+
+<value type="default">none</value>
+<value type="example">laserwriter</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/printing.xml b/docs-xml/smbdotconf/printing/printing.xml
new file mode 100644
index 00000000000..3be0f429392
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/printing.xml
@@ -0,0 +1,36 @@
+<samba:parameter name="printing"
+                 context="S"
+				 type="enum"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameters controls how printer status  information is
+    interpreted on your system. It also affects the  default values for
+    the <parameter moreinfo="none">print command</parameter>,  <parameter
+    moreinfo="none">lpq command</parameter>, <parameter
+    moreinfo="none">lppause command </parameter>, <parameter
+    moreinfo="none">lpresume command</parameter>, and  <parameter
+    moreinfo="none">lprm command</parameter> if specified in the 
+    [global] section.</para>
+
+    <para>Currently nine printing styles are supported. They are
+    <constant>BSD</constant>, <constant>AIX</constant>, 
+    <constant>LPRNG</constant>, <constant>PLP</constant>,
+    <constant>SYSV</constant>, <constant>HPUX</constant>,
+    <constant>QNX</constant>, <constant>SOFTQ</constant>,
+    and <constant>CUPS</constant>.</para>
+
+    <para>To see what the defaults are for the other print 
+    commands when using the various options use the <citerefentry><refentrytitle>testparm</refentrytitle>
+    <manvolnum>1</manvolnum></citerefentry> program.</para>
+
+    <para>This option can be set on a per printer basis.  Please be 
+    aware however, that you must place any of the various printing 
+    commands (e.g. print command, lpq command, etc...) after defining
+    the value for the <parameter>printing</parameter> option since it will 
+    reset the printing commands to default values.</para>
+
+    <para>See also the discussion in the <link linkend="PRINTERSSECT">
+    [printers]</link> section.</para>
+</description>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/printjobusername.xml b/docs-xml/smbdotconf/printing/printjobusername.xml
new file mode 100644
index 00000000000..8f72fee8c32
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/printjobusername.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="printjob username"
+                 context="S"
+				 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter specifies which user information will be 
+    passed to the printing system. Usually, the username is sent,
+    but in some cases, e.g. the domain prefix is useful, too.</para>
+</description>
+
+<related>printing</related>
+
+<value type="example">%D\%U</value>
+<value type="default">%U</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/queuepausecommand.xml b/docs-xml/smbdotconf/printing/queuepausecommand.xml
new file mode 100644
index 00000000000..aee822ea804
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/queuepausecommand.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="queuepause command"
+                 context="S"
+				 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter specifies the command to be 
+    executed on the server host in order to pause the printer queue.</para>
+
+    <para>This command should be a program or script which takes 
+    a printer name as its only parameter and stops the printer queue, 
+    such that no longer jobs are submitted to the printer.</para>
+
+    <para>This command is not supported by Windows for Workgroups, 
+    but can be issued from the Printers window under Windows 95 
+    and NT.</para>
+		
+    <para>If a <parameter moreinfo="none">%p</parameter> is given then the printer name 
+    is put in its place. Otherwise it is placed at the end of the command.
+    </para>
+
+    <para>Note that it is good practice to include the absolute 
+    path in the command as the PATH may not be available to the 
+	server.</para>
+</description>
+
+<value type="example">disable %p</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/queueresumecommand.xml b/docs-xml/smbdotconf/printing/queueresumecommand.xml
new file mode 100644
index 00000000000..f6593c22899
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/queueresumecommand.xml
@@ -0,0 +1,31 @@
+<samba:parameter name="queueresume command"
+                 context="S"
+				 type="string"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter specifies the command to be 
+    executed on the server host in order to resume the printer queue. It 
+    is the command to undo the behavior that is caused by the 
+    previous parameter (<smbconfoption name="queuepause command"/>).</para>
+ 
+    <para>This command should be a program or script which takes 
+    a printer name as its only parameter and resumes the printer queue, 
+    such that queued jobs are resubmitted to the printer.</para>
+
+    <para>This command is not supported by Windows for Workgroups, 
+    but can be issued from the Printers window under Windows 95 
+    and NT.</para>
+
+    <para>If a <parameter moreinfo="none">%p</parameter> is given then the printer name 
+    is put in its place. Otherwise it is placed at the end of the 
+    command.</para>
+
+    <para>Note that it is good practice to include the absolute 
+    path in the command as the PATH may not be available to the 
+	server.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">enable %p</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/showaddprinterwizard.xml b/docs-xml/smbdotconf/printing/showaddprinterwizard.xml
new file mode 100644
index 00000000000..293cf9d1aaa
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/showaddprinterwizard.xml
@@ -0,0 +1,36 @@
+<samba:parameter name="show add printer wizard"
+                 context="G"
+				 type="boolean"
+		 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>With the introduction of MS-RPC based printing support
+    for Windows NT/2000 client in Samba 2.2, a &quot;Printers...&quot; folder will 
+    appear on Samba hosts in the share listing.  Normally this folder will 
+    contain an icon for the MS Add Printer Wizard (APW).  However, it is 
+    possible to disable this feature regardless of the level of privilege 
+    of the connected user.</para>
+		
+    <para>Under normal circumstances, the Windows NT/2000 client will 
+    open a handle on the printer server with OpenPrinterEx() asking for
+    Administrator privileges.  If the user does not have administrative
+    access on the print server (i.e is not root or a member of the 
+    <parameter moreinfo="none">printer admin</parameter> group), the OpenPrinterEx() 
+    call fails and the client makes another open call with a request for 
+    a lower privilege level.  This should succeed, however the APW 
+    icon will not be displayed.</para>
+		
+    <para>Disabling the <parameter moreinfo="none">show add printer wizard</parameter>
+    parameter will always cause the OpenPrinterEx() on the server
+	to fail.  Thus the APW icon will never be displayed. 
+</para>
+<note><para>This does not prevent the same user from having 
+		administrative privilege on an individual printer.</para></note>
+</description>
+
+<related>addprinter command</related>
+<related>deleteprinter command</related>
+<related>printer admin</related>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/printing/useclientdriver.xml b/docs-xml/smbdotconf/printing/useclientdriver.xml
new file mode 100644
index 00000000000..99e85568110
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/useclientdriver.xml
@@ -0,0 +1,40 @@
+<samba:parameter name="use client driver"
+                 context="S"
+				 type="boolean"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter applies only to Windows NT/2000
+    clients.  It has no effect on Windows 95/98/ME clients.  When 
+    serving a printer to Windows NT/2000 clients without first installing
+    a valid printer driver on the Samba host, the client will be required
+    to install a local printer driver.  From this point on, the client
+    will treat the print as a local printer and not a network printer 
+    connection.  This is much the same behavior that will occur
+    when <command moreinfo="none">disable spoolss = yes</command>.
+    </para>
+
+    <para>The differentiating  factor is that under normal
+    circumstances, the NT/2000 client will  attempt to open the network
+    printer using MS-RPC.  The problem is that because the client
+    considers the printer to be local, it will attempt to issue the
+    OpenPrinterEx() call requesting access rights associated  with the
+    logged on user. If the user possesses local administator rights but
+    not root privilege on the Samba host (often the case), the
+    OpenPrinterEx() call will fail.  The result is that the client will
+    now display an &quot;Access Denied; Unable to connect&quot; message
+    in the printer queue window (even though jobs may successfully be
+    printed).  </para>
+
+    <para>If this parameter is enabled for a printer, then any attempt
+    to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped
+    to PRINTER_ACCESS_USE instead.  Thus allowing the OpenPrinterEx()
+    call to succeed.  <emphasis>This parameter MUST not be able enabled
+    on a print share which has valid print driver installed on the Samba 
+	server.</emphasis></para>
+</description>
+
+<related>disable spoolss</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/aclcheckpermissions.xml b/docs-xml/smbdotconf/protocol/aclcheckpermissions.xml
new file mode 100644
index 00000000000..69162617596
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/aclcheckpermissions.xml
@@ -0,0 +1,30 @@
+<samba:parameter name="acl check permissions"
+                 context="S"
+		 type="boolean"
+                 advanced="1" wizard="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean parameter controls what <citerefentry><refentrytitle>smbd</refentrytitle> 
+    <manvolnum>8</manvolnum></citerefentry>does on receiving a protocol request of "open for delete"
+    from a Windows client. If a Windows client doesn't have permissions to delete a file then they
+    expect this to be denied at open time. POSIX systems normally only detect restrictions on delete by
+    actually attempting to delete the file or directory. As Windows clients can (and do) "back out" a
+    delete request by unsetting the "delete on close" bit Samba cannot delete the file immediately
+    on "open for delete" request as we cannot restore such a deleted file. With this parameter set to
+    true (the default) then smbd checks the file system permissions directly on "open for delete" and denies the
+    request without actually deleting the file if the file system permissions would seem to deny it.
+    This is not perfect, as it's possible a user could have deleted a file without Samba being able to
+    check the permissions correctly, but it is close enough to Windows semantics for mostly correct
+    behaviour. Samba will correctly check POSIX ACL semantics in this case.
+    </para>
+    <para>If this parameter is set to "false" Samba doesn't check permissions on "open for delete"
+    and allows the open. If the user doesn't have permission to delete the file this will only be
+    discovered at close time, which is too late for the Windows user tools to display an error message
+    to the user. The symptom of this is files that appear to have been deleted "magically" re-appearing
+    on a Windows explorer refersh. This is an extremely advanced protocol option which should not
+    need to be changed. This parameter was introduced in its final form in 3.0.21, an earlier version
+    with slightly different semantics was introduced in 3.0.20. That older version is not documented here.
+    </para>
+</description>
+<value type="default">True</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/aclmapfullcontrol.xml b/docs-xml/smbdotconf/protocol/aclmapfullcontrol.xml
new file mode 100644
index 00000000000..c38ac3cfbfa
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/aclmapfullcontrol.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="acl map full control"
+		context="S"
+		type="boolean"
+		advanced="1" wizard="1"
+		xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	This boolean parameter controls whether <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>maps a POSIX ACE entry of "rwx" (read/write/execute), the maximum
+	allowed POSIX permission set, into a Windows ACL of "FULL CONTROL". If this parameter is set to true any POSIX
+	ACE entry of "rwx" will be returned in a Windows ACL as "FULL CONTROL", is this parameter is set to false any
+	POSIX ACE entry of "rwx" will be returned as the specific Windows ACL bits representing read, write and
+	execute.
+	</para>
+</description>
+<value type="default">True</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/announceas.xml b/docs-xml/smbdotconf/protocol/announceas.xml
new file mode 100644
index 00000000000..88914961941
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/announceas.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="announce as"
+                 context="G"
+				 type="string"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This specifies what type of server <citerefentry><refentrytitle>nmbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> will announce itself as, to a network neighborhood browse 
+    list. By default this is set to Windows NT. The valid options 
+    are : &quot;NT Server&quot; (which can also be written as &quot;NT&quot;), 
+    &quot;NT Workstation&quot;, &quot;Win95&quot; or &quot;WfW&quot; meaning Windows NT Server, 
+    Windows NT Workstation, Windows 95 and Windows for Workgroups 
+    respectively. Do not change this parameter unless you have a 
+    specific need to stop Samba appearing as an NT server as this 
+    may prevent Samba servers from participating as browser servers 
+	correctly.</para>
+</description>
+
+<value type="default">NT Server</value>
+<value type="example">Win95</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/announceversion.xml b/docs-xml/smbdotconf/protocol/announceversion.xml
new file mode 100644
index 00000000000..ecdcd4c7349
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/announceversion.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="announce version"
+                 context="G"
+                 developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This specifies the major and minor version numbers 
+    that nmbd will use when announcing itself as a server. The default 
+    is 4.9.  Do not change this parameter unless you have a specific 
+	need to set a Samba server to be a downlevel server.</para>
+</description>
+<value type="default">4.9</value>
+<value type="example">2.0</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/clientusespnego.xml b/docs-xml/smbdotconf/protocol/clientusespnego.xml
new file mode 100644
index 00000000000..c688a656f4f
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/clientusespnego.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="client use spnego"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para> This variable controls whether Samba clients will try 
+    to use Simple and Protected NEGOciation (as specified by rfc2478) with 
+    supporting servers (including WindowsXP, Windows2000 and Samba
+    3.0) to agree upon an authentication
+    mechanism.  This enables Kerberos authentication in particular.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/defersharingviolations.xml b/docs-xml/smbdotconf/protocol/defersharingviolations.xml
new file mode 100644
index 00000000000..f54916c7765
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/defersharingviolations.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="defer sharing violations"
+                 context="G"
+		 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	Windows allows specifying how a file will be shared with 
+	other processes when it is opened. Sharing violations occur when 
+	a file is opened by a different process using options that violate 
+	the share settings specified by other processes. This parameter causes
+	smbd to act as a Windows server does, and defer returning a "sharing
+	violation" error message for up to one second, allowing the client
+	to close the file causing the violation in the meantime.
+	</para>
+
+	<para>UNIX by default does not have this behaviour.</para>
+
+	<para>
+	There should be no reason to turn off this parameter, as it is
+	designed to enable Samba to more correctly emulate Windows.
+	</para>
+</description>
+
+<value type="default">True</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/disablenetbios.xml b/docs-xml/smbdotconf/protocol/disablenetbios.xml
new file mode 100644
index 00000000000..e78cb8c4f7c
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/disablenetbios.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="disable netbios"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>Enabling this parameter will disable netbios support
+    in Samba. Netbios is the only available form of browsing in 
+    all windows versions except for 2000 and XP. </para>
+
+    <note><para>Clients that only support netbios won't be able to 
+    see your samba server when netbios support is disabled.
+	</para></note>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/easupport.xml b/docs-xml/smbdotconf/protocol/easupport.xml
new file mode 100644
index 00000000000..ba210fdac7e
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/easupport.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="ea support"
+                 context="S"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean parameter controls whether <citerefentry><refentrytitle>smbd</refentrytitle>                                       
+    <manvolnum>8</manvolnum></citerefentry> will allow clients to attempt to store OS/2 style Extended
+    attributes on a share. In order to enable this parameter the underlying filesystem exported by
+    the share must support extended attributes (such as provided on XFS and EXT3 on Linux, with the
+    correct kernel patches). On Linux the filesystem must have been mounted with the mount
+        option user_xattr in order for extended attributes to work, also
+		extended attributes must be compiled into the Linux kernel.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/enableasusupport.xml b/docs-xml/smbdotconf/protocol/enableasusupport.xml
new file mode 100644
index 00000000000..cd4f30fb8d6
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/enableasusupport.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="enable asu support"
+                 context="G"
+                 advanced="1" developer="1"
+		 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>Hosts running the "Advanced Server for Unix (ASU)" product 
+    require some special accomodations such as creating a builting [ADMIN$] 
+    share that only supports IPC connections.  The has been the default
+    behavior in smbd for many years.  However, certain Microsoft applications
+    such as the Print Migrator tool require that the remote server support
+    an [ADMIN$} file share.  Disabling this parameter allows for creating 
+    an [ADMIN$] file share in smb.conf.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/eventloglist.xml b/docs-xml/smbdotconf/protocol/eventloglist.xml
new file mode 100644
index 00000000000..e98559bc179
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/eventloglist.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="eventlog list"
+		 type="string"
+                 context="G"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option defines a list of log names that Samba will 
+    report to the Microsoft EventViewer utility.  The listed 
+    eventlogs will be associated with tdb file on disk in the 
+    <filename>$(lockdir)/eventlog</filename>.
+    </para>
+
+    <para>
+    The administrator must use an external process to parse the normal 
+    Unix logs such as <filename>/var/log/messages</filename>
+    and write then entries to the eventlog tdb files.  Refer to the
+    eventlogadm(8) utility for how to write eventlog entries.
+    </para>
+</description>
+
+<value type="default"/>
+<value type="example">Security Application Syslog Apache</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/largereadwrite.xml b/docs-xml/smbdotconf/protocol/largereadwrite.xml
new file mode 100644
index 00000000000..12be741322e
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/largereadwrite.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="large readwrite"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter determines whether or not
+    <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> supports the new 64k
+    streaming read and write varient SMB requests introduced with
+    Windows 2000. Note that due to Windows 2000 client redirector bugs
+    this requires Samba to be running on a 64-bit capable operating
+    system such as IRIX, Solaris or a Linux 2.4 kernel. Can improve
+    performance by 10% with Windows 2000 clients. Defaults to on. Not as
+	tested as some other Samba code paths.</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/mapaclinherit.xml b/docs-xml/smbdotconf/protocol/mapaclinherit.xml
new file mode 100644
index 00000000000..ef0b4eb6d6e
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/mapaclinherit.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="map acl inherit"
+                 context="S"
+				 type="boolean"
+                 advanced="1" wizard="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean parameter controls whether <citerefentry><refentrytitle>smbd</refentrytitle>                                       
+    <manvolnum>8</manvolnum></citerefentry> will attempt to map the 'inherit' and 'protected'
+    access control entry flags stored in Windows ACLs into an extended attribute
+    called user.SAMBA_PAI. This parameter only takes effect if Samba is being run
+    on a platform that supports extended attributes (Linux and IRIX so far) and
+    allows the Windows 2000 ACL editor to correctly use inheritance with the Samba
+    POSIX ACL mapping code.
+    </para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/maxmux.xml b/docs-xml/smbdotconf/protocol/maxmux.xml
new file mode 100644
index 00000000000..71998c974fc
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/maxmux.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="max mux"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option controls the maximum number of 
+    outstanding simultaneous SMB operations that Samba tells the client 
+	it will allow. You should never need to set this parameter.</para>
+</description>
+
+<value type="default">50</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/maxprotocol.xml b/docs-xml/smbdotconf/protocol/maxprotocol.xml
new file mode 100644
index 00000000000..e785909147d
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/maxprotocol.xml
@@ -0,0 +1,48 @@
+<samba:parameter name="max protocol"
+                 context="G"
+				 type="enum"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>The value of the parameter (a string) is the highest 
+    protocol level that will be supported by the server.</para>
+
+    <para>Possible values are :</para>
+    <itemizedlist>
+	<listitem>
+	    <para><constant>CORE</constant>: Earliest version. No 
+	    concept of user names.</para>
+	</listitem>
+			
+	<listitem>
+	    <para><constant>COREPLUS</constant>: Slight improvements on 
+	    CORE for efficiency.</para>
+	</listitem>
+
+	<listitem>
+	    <para><constant>LANMAN1</constant>: First <emphasis>
+	    modern</emphasis> version of the protocol. Long filename
+	    support.</para>
+	</listitem>
+
+	<listitem>
+	    <para><constant>LANMAN2</constant>: Updates to Lanman1 protocol.</para>
+	</listitem>
+
+	<listitem>
+	    <para><constant>NT1</constant>: Current up to date version of the protocol. 
+	    Used by Windows NT. Known as CIFS.</para>
+	</listitem>
+    </itemizedlist>
+
+    <para>Normally this option should not be set as the automatic 
+    negotiation phase in the SMB protocol takes care of choosing 
+	the appropriate protocol.</para>
+</description>
+
+<related>min protocol</related>
+<synonym>protocol</synonym>
+
+<value type="default">NT1</value>
+<value type="example">LANMAN1</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/maxttl.xml b/docs-xml/smbdotconf/protocol/maxttl.xml
new file mode 100644
index 00000000000..00f735d3a94
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/maxttl.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="max ttl"
+                 context="G"
+				 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option tells <citerefentry><refentrytitle>nmbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> what the default 'time to live' 
+    of NetBIOS names should be (in seconds) when <command moreinfo="none">nmbd</command> is 
+    requesting a name using either a broadcast packet or from a WINS server. You should 
+	never need to change this parameter. The default is 3 days.</para>
+</description>
+<value type="default">259200</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/maxwinsttl.xml b/docs-xml/smbdotconf/protocol/maxwinsttl.xml
new file mode 100644
index 00000000000..09935cdd9b6
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/maxwinsttl.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="max wins ttl"
+				 type="integer"
+                 context="G"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option tells <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> when acting as a WINS server
+	(<smbconfoption name="wins support">yes</smbconfoption>) what the maximum
+    'time to live' of NetBIOS names that <command moreinfo="none">nmbd</command> 
+    will grant will be (in seconds). You should never need to change this
+	parameter.  The default is 6 days (518400 seconds).</para>
+</description>
+
+<related>min wins ttl</related>
+<value type="default">518400</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/maxxmit.xml b/docs-xml/smbdotconf/protocol/maxxmit.xml
new file mode 100644
index 00000000000..3804ae21e35
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/maxxmit.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="max xmit"
+                 context="G"
+				 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option controls the maximum packet size 
+    that will be negotiated by Samba. The default is 16644, which 
+    matches the behavior of Windows 2000.  A value below 2048 is likely to cause problems.
+    You should never need to change this parameter from its default value.
+</para>
+</description>
+
+<value type="default">16644</value>
+<value type="example">8192</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/minprotocol.xml b/docs-xml/smbdotconf/protocol/minprotocol.xml
new file mode 100644
index 00000000000..0bec282467c
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/minprotocol.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="min protocol"
+                 context="G"
+				 type="string"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>The value of the parameter (a string) is the 
+    lowest SMB protocol dialect than Samba will support.  Please refer
+    to the <smbconfoption name="max protocol"/>
+    parameter for a list of valid protocol names and a brief description
+    of each.  You may also wish to refer to the C source code in
+    <filename moreinfo="none">source/smbd/negprot.c</filename> for a listing of known protocol
+    dialects supported by clients.</para>
+		
+    <para>If you are viewing this parameter as a security measure, you should
+    also refer to the <smbconfoption name="lanman auth"/> parameter.  Otherwise, you should never need 
+    to change this parameter.</para>
+</description>
+
+<value type="default">CORE</value>
+<value type="example">NT1</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/minreceivefilesize.xml b/docs-xml/smbdotconf/protocol/minreceivefilesize.xml
new file mode 100644
index 00000000000..2df6c178db2
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/minreceivefilesize.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="min receivefile size"
+		type="integer"
+		context="G"
+		advanced="1" developer="1"
+		xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+<para>This option changes the behavior of <citerefentry><refentrytitle>smbd</refentrytitle>
+<manvolnum>8</manvolnum></citerefentry> when processing SMBwriteX calls. Any incoming
+SMBwriteX call on a non-signed SMB/CIFS connection greater than this value will not be processed in the normal way but will
+be passed to any underlying kernel recvfile or splice system call (if there is no such
+call Samba will emulate in user space). This allows zero-copy writes directly from network
+socket buffers into the filesystem buffer cache, if available. It may improve performance
+but user testing is recommended. If set to zero Samba processes SMBwriteX calls in the
+normal way. To enable POSIX large write support (SMB/CIFS writes up to 16Mb) this option must be
+nonzero. The maximum value is 128k. Values greater than 128k will be silently set to 128k.</para>
+<para>Note this option will have NO EFFECT if set on a SMB signed connection.</para>
+<para>The default is zero, which diables this option.</para>
+</description>
+
+<related>min receivefile size</related>
+<value type="default">0</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/minwinsttl.xml b/docs-xml/smbdotconf/protocol/minwinsttl.xml
new file mode 100644
index 00000000000..38fbd7b0ebb
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/minwinsttl.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="min wins ttl"
+                 context="G"
+				 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option tells <citerefentry><refentrytitle>nmbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry>
+    when acting as a WINS server (<smbconfoption name="wins support">yes</smbconfoption>) what the minimum 'time to live' 
+    of NetBIOS names that <command moreinfo="none">nmbd</command> will grant will be (in 
+    seconds). You should never need to change this parameter.  The default 
+    is 6 hours (21600 seconds).</para>
+</description>
+
+<value type="default">21600</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/nameresolveorder.xml b/docs-xml/smbdotconf/protocol/nameresolveorder.xml
new file mode 100644
index 00000000000..9b1ad075b13
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/nameresolveorder.xml
@@ -0,0 +1,70 @@
+<samba:parameter name="name resolve order"
+                 context="G"
+				 type="list"
+                 advanced="1" wizard="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 
+<description>
+    <para>This option is used by the programs in the Samba 
+    suite to determine what naming services to use and in what order 
+    to resolve host names to IP addresses. Its main purpose to is to
+    control how netbios name resolution is performed.  The option takes a space 
+    separated string of name resolution options.</para>
+
+    <para>The options are: &quot;lmhosts&quot;, &quot;host&quot;,
+    &quot;wins&quot; and &quot;bcast&quot;. They cause names to be
+    resolved as follows:</para>
+
+    <itemizedlist>
+	<listitem>
+	    <para>
+		<constant>lmhosts</constant> : Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has 
+	    no name type attached to the NetBIOS name (see the manpage for lmhosts for details) then
+	    any name type matches for lookup.
+		</para>
+	</listitem>
+
+	<listitem>
+	    <para>
+		<constant>host</constant> : Do a standard host name to IP address resolution, using the system
+		<filename moreinfo="none">/etc/hosts </filename>, NIS, or DNS lookups. This method of name resolution is
+		operating system depended for instance on IRIX or Solaris this may be controlled by the <filename
+		moreinfo="none">/etc/nsswitch.conf</filename> file.  Note that this method is used only if the NetBIOS name
+		type being queried is the 0x20 (server) name type or 0x1c (domain controllers).  The latter case is only
+		useful for active directory domains and results in a DNS query for the SRV RR entry matching
+		_ldap._tcp.domain.
+	</para>
+	</listitem>
+
+	<listitem>
+	    <para><constant>wins</constant> : Query a name with 
+	    the IP address listed in the <smbconfoption name="WINSSERVER"><parameter moreinfo="none">
+	    wins server</parameter></smbconfoption> parameter.  If no WINS server has
+	    been specified this method will be ignored.</para>
+	</listitem>
+
+	<listitem>
+	    <para><constant>bcast</constant> : Do a broadcast on 
+	    each of the known local interfaces listed in the <smbconfoption name="interfaces"/> 
+	    parameter. This is the least reliable of the name resolution 
+	    methods as it depends on the target host being on a locally 
+	    connected subnet.</para>
+	</listitem>
+</itemizedlist>
+
+    <para>The example below will cause the local lmhosts file to be examined 
+    first, followed by a broadcast attempt, followed by a normal 
+    system hostname lookup.</para>
+
+    <para>When Samba is functioning in ADS security mode (<command moreinfo="none">security = ads</command>)
+    it is advised to use following settings for <parameter moreinfo="none">name resolve order</parameter>:</para>
+
+    <para><command moreinfo="none">name resolve order = wins bcast</command></para>
+
+    <para>DC lookups will still be done via DNS, but fallbacks to netbios names will
+		not inundate your DNS servers with needless querys for DOMAIN&lt;0x1c&gt; lookups.</para>
+ 
+</description>
+
+<value type="default">lmhosts host wins bcast</value>
+<value type="example">lmhosts bcast host</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/ntaclsupport.xml b/docs-xml/smbdotconf/protocol/ntaclsupport.xml
new file mode 100644
index 00000000000..1e9cedf931d
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/ntaclsupport.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="nt acl support"
+                 context="S"
+                 advanced="1" wizard="1"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean parameter controls whether <citerefentry><refentrytitle>smbd</refentrytitle>                                       
+    <manvolnum>8</manvolnum></citerefentry> will attempt to map 
+    UNIX permissions into Windows NT access control lists.  The UNIX
+    permissions considered are the the traditional UNIX owner and
+    group permissions, as well as POSIX ACLs set on any files or
+    directories.  This parameter was formally a global parameter in
+    releases prior to 2.2.2.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/ntpipesupport.xml b/docs-xml/smbdotconf/protocol/ntpipesupport.xml
new file mode 100644
index 00000000000..7c310846b2f
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/ntpipesupport.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="nt pipe support"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean parameter controls whether 
+    <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> will allow Windows NT 
+    clients to connect to the NT SMB specific <constant>IPC$</constant> 
+    pipes. This is a developer debugging option and can be left
+	alone.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/ntstatussupport.xml b/docs-xml/smbdotconf/protocol/ntstatussupport.xml
new file mode 100644
index 00000000000..4dfc142e2e6
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/ntstatussupport.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="nt status support"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean parameter controls whether <citerefentry><refentrytitle>smbd</refentrytitle>                                       
+    <manvolnum>8</manvolnum></citerefentry> will negotiate NT specific status
+    support with Windows NT/2k/XP clients. This is a developer debugging option and should be left alone.
+    If this option is set to <constant>no</constant> then Samba offers
+    exactly the same DOS error codes that versions prior to Samba 2.2.3
+    reported.</para>
+
+    <para>You should not need to ever disable this parameter.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/profileacls.xml b/docs-xml/smbdotconf/protocol/profileacls.xml
new file mode 100644
index 00000000000..1c6f0c9ebf5
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/profileacls.xml
@@ -0,0 +1,41 @@
+<samba:parameter name="profile acls"
+                 context="S"
+				 type="boolean"
+                 advanced="1" wizard="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This boolean parameter was added to fix the problems that people have been
+	having with storing user profiles on Samba shares from Windows 2000 or
+	Windows XP clients. New versions of Windows 2000 or Windows XP service
+	packs do security ACL checking on the owner and ability to write of the
+	profile directory stored on a local workstation when copied from a Samba
+	share.
+	</para>
+
+	<para>
+	When not in domain mode with winbindd then the security info copied
+	onto the local workstation has no meaning to the logged in user (SID) on
+	that workstation so the profile storing fails. Adding this parameter
+	onto a share used for profile storage changes two things about the
+	returned Windows ACL. Firstly it changes the owner and group owner
+	of all reported files and directories to be BUILTIN\\Administrators,
+	BUILTIN\\Users respectively (SIDs S-1-5-32-544, S-1-5-32-545). Secondly
+	it adds an ACE entry of "Full Control" to the SID BUILTIN\\Users to
+	every returned ACL. This will allow any Windows 2000 or XP workstation
+	user to access the profile.
+	</para>
+	
+	<para>
+	Note that if you have multiple users logging
+	on to a workstation then in order to prevent them from being able to access
+	each others profiles you must remove the "Bypass traverse checking" advanced
+	user right. This will prevent access to other users profile directories as
+	the top level profile directory (named after the user) is created by the
+	workstation profile code and has an ACL restricting entry to the directory
+	tree to the owning user.
+	</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/readraw.xml b/docs-xml/smbdotconf/protocol/readraw.xml
new file mode 100644
index 00000000000..2ca23075ee9
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/readraw.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="read raw"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter controls whether or not the server 
+    will support the raw read SMB requests when transferring data 
+    to clients.</para>
+
+    <para>If enabled, raw reads allow reads of 65535 bytes in 
+    one packet. This typically provides a major performance benefit.
+    </para>
+
+    <para>However, some clients either negotiate the allowable 
+    block size incorrectly or are incapable of supporting larger block 
+	sizes, and for these clients you may need to disable raw reads.</para>
+
+<para>In general this parameter should be viewed as a system tuning 
+	tool and left severely alone.</para>
+</description>
+
+<value type="default">yes</value>
+
+<related>write raw</related>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/smbports.xml b/docs-xml/smbdotconf/protocol/smbports.xml
new file mode 100644
index 00000000000..aaf4919db03
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/smbports.xml
@@ -0,0 +1,11 @@
+<samba:parameter name="smb ports"
+                 context="G"
+				 type="list"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>Specifies which ports the server should listen on for SMB traffic.</para>
+</description>
+
+<value type="default">445 139</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/svcctllist.xml b/docs-xml/smbdotconf/protocol/svcctllist.xml
new file mode 100644
index 00000000000..660a2800886
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/svcctllist.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="svcctl list"
+		 type="string"
+                 context="G"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option defines a list of init scripts that smbd
+    will use for starting and stopping Unix services via the Win32 
+    ServiceControl API.  This allows Windows administrators to 
+    utilize the MS Management Console plug-ins to manage a 
+    Unix server running Samba.</para>
+
+    <para>The administrator must create a directory
+    name <filename>svcctl</filename> in Samba's $(libdir)
+    and create symbolic links to the init scripts in 
+    <filename>/etc/init.d/</filename>.  The name of the links
+    must match the names given as part of the <parameter>svcctl list</parameter>.
+    </para>
+</description>
+
+<value type="default"/>
+<value type="example">cups postfix portmap httpd</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/timeserver.xml b/docs-xml/smbdotconf/protocol/timeserver.xml
new file mode 100644
index 00000000000..93d89183b5a
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/timeserver.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="time server"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter determines if <citerefentry><refentrytitle>nmbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> advertises itself as a time server to Windows 
+clients.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/unixextensions.xml b/docs-xml/smbdotconf/protocol/unixextensions.xml
new file mode 100644
index 00000000000..5b4a36a4015
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/unixextensions.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="unix extensions"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+    <para>This boolean parameter controls whether Samba 
+    implments the CIFS UNIX extensions, as defined by HP. 
+    These extensions enable Samba to better serve UNIX CIFS clients
+    by supporting features such as symbolic links, hard links, etc...
+    These extensions require a similarly enabled client, and are of
+    no current use to Windows clients.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/usespnego.xml b/docs-xml/smbdotconf/protocol/usespnego.xml
new file mode 100644
index 00000000000..8fb559c1775
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/usespnego.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="use spnego"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This variable controls controls whether samba will try 
+    to use Simple and Protected NEGOciation (as specified by rfc2478) with 
+    WindowsXP and Windows2000 clients to agree upon an authentication mechanism. 
+</para>
+
+<para>
+    Unless further issues are discovered with our SPNEGO
+    implementation, there is no reason this should ever be
+	disabled.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/protocol/writeraw.xml b/docs-xml/smbdotconf/protocol/writeraw.xml
new file mode 100644
index 00000000000..f299fa84836
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/writeraw.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="write raw"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter controls whether or not the server 
+    will support raw write SMB's when transferring data from clients. 
+    You should never need to change this parameter.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/aclgroupcontrol.xml b/docs-xml/smbdotconf/security/aclgroupcontrol.xml
new file mode 100644
index 00000000000..e2600ca9da5
--- /dev/null
+++ b/docs-xml/smbdotconf/security/aclgroupcontrol.xml
@@ -0,0 +1,43 @@
+<samba:parameter name="acl group control"
+                 context="S"
+		 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	In a POSIX filesystem, only the owner of a file or directory and the superuser can modify the permissions
+	and ACLs on a file. If this parameter is set, then Samba overrides this restriction, and also allows the
+ 	 <emphasis>primary group owner</emphasis> of a file or directory to modify the permissions and ACLs
+	on that file.
+	</para>
+	<para>
+	On a Windows server, groups may be the owner of a file or directory - thus allowing anyone in
+	that group to modify the permissions on it. This allows the delegation of security controls
+	on a point in the filesystem to the group owner of a directory and anything below it also owned
+	by that group. This means there are multiple people with permissions to modify ACLs on a file
+	or directory, easing managability.
+	</para>
+	<para>
+	This parameter allows Samba to also permit delegation of the control over a point in the exported
+	directory hierarchy in much the same way as Windows. This allows all members of a UNIX group to
+	control the permissions on a file or directory they have group ownership on.
+	</para>
+
+	<para>
+	This parameter is best used with the <smbconfoption name="inherit owner"/> option and also
+	on on a share containing directories with the UNIX <emphasis>setgid bit</emphasis> set
+	on them, which causes new files and directories created within it to inherit the group
+	ownership from the containing directory. 
+	</para>
+
+	<para>
+	This is parameter has been marked deprecated in Samba 3.0.23.  The same behavior is now
+	implemented by the <parameter moreinfo="none">dos filemode</parameter> option.
+	</para>
+
+</description>
+
+<related>inherit owner</related>
+<related>inherit permissions</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/adminusers.xml b/docs-xml/smbdotconf/security/adminusers.xml
new file mode 100644
index 00000000000..d8f14b6d740
--- /dev/null
+++ b/docs-xml/smbdotconf/security/adminusers.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="admin users"
+                 context="S"
+				 type="list"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This is a list of users who will be granted 
+    administrative privileges on the share. This means that they 
+    will do all file operations as the super-user (root).</para>
+
+    <para>You should use this option very carefully, as any user in 
+    this list will be able to do anything they like on the share, 
+    irrespective of file permissions.</para>
+
+    <para>This parameter will not work with the <smbconfoption name="security">share</smbconfoption> in
+    Samba 3.0.  This is by design.</para>
+
+</description>
+
+<value type="default"/>
+<value type="example">jason</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/algorithmicridbase.xml b/docs-xml/smbdotconf/security/algorithmicridbase.xml
new file mode 100644
index 00000000000..24a31500246
--- /dev/null
+++ b/docs-xml/smbdotconf/security/algorithmicridbase.xml
@@ -0,0 +1,27 @@
+<samba:parameter name="algorithmic rid base"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="integer"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This determines how Samba will use its
+    algorithmic mapping from uids/gid to the RIDs needed to construct
+    NT Security Identifiers.
+    </para>
+
+    <para>Setting this option to a larger value could be useful to sites
+    transitioning from WinNT and Win2k, as existing user and 
+    group rids would otherwise clash with sytem users etc. 
+    </para>
+
+    <para>All UIDs and GIDs must be able to be resolved into SIDs for  
+    the correct operation of ACLs on the server.  As such the algorithmic
+    mapping can't be 'turned off', but pushing it 'out of the way' should
+    resolve the issues.  Users and groups can then be assigned 'low' RIDs
+    in arbitrary-rid supporting backends.
+    </para>
+</description>
+
+<value type="default">1000</value>
+<value type="example">100000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/allowtrusteddomains.xml b/docs-xml/smbdotconf/security/allowtrusteddomains.xml
new file mode 100644
index 00000000000..57bf1d2422b
--- /dev/null
+++ b/docs-xml/smbdotconf/security/allowtrusteddomains.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="allow trusted domains"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This option only takes effect when the <smbconfoption name="security"/> option is set to 
+    <constant>server</constant>, <constant>domain</constant> or <constant>ads</constant>.  
+    If it is set to no, then attempts to connect to a resource from 
+    a domain or workgroup other than the one which smbd is running 
+    in will fail, even if that domain is trusted by the remote server 
+    doing the authentication.</para>
+		
+    <para>This is useful if you only want your Samba server to 
+    serve resources to users in the domain it is a member of. As 
+    an example, suppose that there are two domains DOMA and DOMB.  DOMB 
+    is trusted by DOMA, which contains the Samba server.  Under normal 
+    circumstances, a user with an account in DOMB can then access the 
+    resources of a UNIX account with the same account name on the 
+    Samba server even if they do not have an account in DOMA.  This 
+    can make implementing a security boundary difficult.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/authmethods.xml b/docs-xml/smbdotconf/security/authmethods.xml
new file mode 100644
index 00000000000..39d211dbd3f
--- /dev/null
+++ b/docs-xml/smbdotconf/security/authmethods.xml
@@ -0,0 +1,34 @@
+<samba:parameter name="auth methods"
+                 context="G"
+				 type="list"
+                 basic="1" advanced="1" wizard="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+    <para>
+    This option allows the administrator to chose what authentication methods <command  moreinfo="none">smbd</command> 
+    will use when authenticating a user. This option defaults to sensible values based on <smbconfoption name="security"/>.  
+    This should be considered a developer option and used only in rare circumstances.  In the majority (if not all) 
+    of production servers, the default setting should be adequate.
+    </para>
+
+    <para>
+    Each entry in the list attempts to authenticate the user in turn, until
+    the user authenticates.  In practice only one method will ever actually 
+    be able to complete the authentication.
+    </para>
+
+    <para>
+    Possible options include <constant>guest</constant> (anonymous access), 
+    <constant>sam</constant> (lookups in local list of accounts based on netbios 
+    name or domain name), <constant>winbind</constant> (relay authentication requests
+    for remote users through winbindd), <constant>ntdomain</constant> (pre-winbindd 
+    method of authentication for remote domain users; deprecated in favour of winbind method), 
+    <constant>trustdomain</constant> (authenticate trusted users by contacting the 
+    remote DC directly from smbd; deprecated in favour of winbind method).
+    </para>
+
+</description>
+<value type="default"/>
+<value type="example">guest sam winbind</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/checkpasswordscript.xml b/docs-xml/smbdotconf/security/checkpasswordscript.xml
new file mode 100644
index 00000000000..9169891c298
--- /dev/null
+++ b/docs-xml/smbdotconf/security/checkpasswordscript.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="check password script"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>The name of a program that can be used to check password
+    complexity. The password is sent to the program's standrad input.</para>
+ 
+    <para>The program must return 0 on good password any other value otherwise.
+    In case the password is considered weak (the program do not return 0) the
+    user will be notified and the password change will fail.</para>
+
+    <para>Note: In the example directory there is a sample program called crackcheck
+    that uses cracklib to checkpassword quality.</para>
+
+</description>
+
+<value type="default">Disabled</value>
+<value type="example">check password script = /usr/local/sbin/crackcheck</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/clientlanmanauth.xml b/docs-xml/smbdotconf/security/clientlanmanauth.xml
new file mode 100644
index 00000000000..5266fef6a24
--- /dev/null
+++ b/docs-xml/smbdotconf/security/clientlanmanauth.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="client lanman auth"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter determines whether or not <citerefentry><refentrytitle>smbclient</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> and other samba client
+    tools will attempt to authenticate itself to servers using the
+    weaker LANMAN password hash. If disabled, only server which support NT 
+    password hashes (e.g. Windows NT/2000, Samba, etc... but not 
+    Windows 95/98) will be able to be connected from the Samba client.</para>
+
+    <para>The LANMAN encrypted response is easily broken, due to it's
+    case-insensitive nature, and the choice of algorithm.  Clients
+    without Windows 95/98 servers are advised to disable
+    this option.  </para>
+
+    <para>Disabling this option will also disable the <command
+    moreinfo="none">client plaintext auth</command> option</para>
+
+    <para>Likewise, if the <command moreinfo="none">client ntlmv2
+    auth</command> parameter is enabled, then only NTLMv2 logins will be
+    attempted.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/clientntlmv2auth.xml b/docs-xml/smbdotconf/security/clientntlmv2auth.xml
new file mode 100644
index 00000000000..9f0627abbf4
--- /dev/null
+++ b/docs-xml/smbdotconf/security/clientntlmv2auth.xml
@@ -0,0 +1,32 @@
+<samba:parameter name="client ntlmv2 auth"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter determines whether or not <citerefentry><refentrytitle>smbclient</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> will attempt to
+    authenticate itself to servers using the NTLMv2 encrypted password
+    response.</para>
+
+    <para>If enabled, only an NTLMv2 and LMv2 response (both much more
+    secure than earlier versions) will be sent.  Many servers
+    (including NT4 &lt; SP4, Win9x and Samba 2.2) are not compatible with
+    NTLMv2.  </para>
+
+    <para>Similarly, if enabled, NTLMv1, <command
+    moreinfo="none">client lanman auth</command> and <command
+    moreinfo="none">client plaintext auth</command>
+    authentication will be disabled.  This also disables share-level 
+    authentication. </para>
+
+    <para>If disabled, an NTLM response (and possibly a LANMAN response)
+    will be sent by the client, depending on the value of <command
+    moreinfo="none">client lanman auth</command>.  </para>
+
+    <para>Note that some sites (particularly
+    those following 'best practice' security polices) only allow NTLMv2
+	responses, and not the weaker LM or NTLM.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/clientplaintextauth.xml b/docs-xml/smbdotconf/security/clientplaintextauth.xml
new file mode 100644
index 00000000000..c4061559db8
--- /dev/null
+++ b/docs-xml/smbdotconf/security/clientplaintextauth.xml
@@ -0,0 +1,12 @@
+<samba:parameter name="client plaintext auth"
+                 context="G"
+				 type="boolean"
+                 basic="1" advanced="1" wizard="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>Specifies whether a client should send a plaintext 
+		password if the server does not support encrypted passwords.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
+
diff --git a/docs-xml/smbdotconf/security/clientschannel.xml b/docs-xml/smbdotconf/security/clientschannel.xml
new file mode 100644
index 00000000000..e229182f978
--- /dev/null
+++ b/docs-xml/smbdotconf/security/clientschannel.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="client schannel"
+                 context="G"
+                 basic="1"
+				 type="boolean-auto"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+    <para>
+    This controls whether the client offers or even demands the use of the netlogon schannel.
+    <smbconfoption name="client schannel">no</smbconfoption> does not offer the schannel, 
+    <smbconfoption name="client schannel">auto</smbconfoption> offers the schannel but does not
+    enforce it, and <smbconfoption name="client schannel">yes</smbconfoption> denies access 
+    if the server is not able to speak netlogon schannel. 
+    </para>
+</description>
+<value type="default">auto</value>
+<value type="example">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/clientsigning.xml b/docs-xml/smbdotconf/security/clientsigning.xml
new file mode 100644
index 00000000000..bf37cbb8746
--- /dev/null
+++ b/docs-xml/smbdotconf/security/clientsigning.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="client signing"
+                 context="G"
+				 type="boolean-auto"
+                 basic="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This controls whether the client offers or requires
+    the server it talks to to use SMB signing. Possible values 
+    are <emphasis>auto</emphasis>, <emphasis>mandatory</emphasis> 
+    and <emphasis>disabled</emphasis>. 
+    </para>
+
+    <para>When set to auto, SMB signing is offered, but not enforced. 
+    When set to mandatory, SMB signing is required and if set 
+	to disabled, SMB signing is not offered either.
+</para>
+</description>
+
+<value type="default">auto</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/createmask.xml b/docs-xml/smbdotconf/security/createmask.xml
new file mode 100644
index 00000000000..cf6864c78ec
--- /dev/null
+++ b/docs-xml/smbdotconf/security/createmask.xml
@@ -0,0 +1,43 @@
+<samba:parameter name="create mask"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+
+<synonym>create mode</synonym>
+<description>
+    <para>
+	When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to
+	UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter. This parameter may
+	be thought of as a bit-wise MASK for the UNIX modes of a file. Any bit <emphasis>not</emphasis> set here will
+	be removed from the modes set on a file when it is created.
+	</para>
+
+    <para>
+	The default value of this parameter removes the <literal>group</literal> and <literal>other</literal>
+	write and execute bits from the UNIX modes.
+	</para>
+
+    <para>
+	Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the
+	<smbconfoption name="force create mode"/> parameter which is set to 000 by default.
+	</para>
+
+    <para>
+	This parameter does not affect directory masks. See the parameter <smbconfoption name="directory mask"/>
+	for details.
+	</para>
+
+    <para>
+	Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors. If the
+	administrator wishes to enforce a mask on access control lists also, they need to set the <smbconfoption
+	name="security mask"/>.
+	</para>
+</description>
+
+<related>force create mode</related>
+<related>directory mode</related>
+<related>inherit permissions</related>
+
+<value type="default">0744</value>
+<value type="example">0775</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/directorymask.xml b/docs-xml/smbdotconf/security/directorymask.xml
new file mode 100644
index 00000000000..7b67f79214a
--- /dev/null
+++ b/docs-xml/smbdotconf/security/directorymask.xml
@@ -0,0 +1,38 @@
+<samba:parameter name="directory mask"
+	context="S"
+	type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>directory mode</synonym>
+<description>
+    <para>This parameter is the octal modes which are 
+    used when converting DOS modes to UNIX modes when creating UNIX 
+    directories.</para>
+
+    <para>When a directory is created, the necessary permissions are 
+    calculated according to the mapping from DOS modes to UNIX permissions, 
+    and the resulting UNIX mode is then bit-wise 'AND'ed with this 
+    parameter. This parameter may be thought of as a bit-wise MASK for 
+    the UNIX modes of a directory. Any bit <emphasis>not</emphasis> set 
+    here will be removed from the modes set on a directory when it is 
+    created.</para>
+
+    <para>The default value of this parameter removes the 'group' 
+    and 'other' write bits from the UNIX mode, allowing only the 
+    user who owns the directory to modify it.</para>
+		
+    <para>Following this Samba will bit-wise 'OR' the UNIX mode 
+    created from this parameter with the value of the <smbconfoption name="force directory mode"/> parameter. 
+    This parameter is set to 000 by default (i.e. no extra mode bits are added).</para>
+
+    <para>Note that this parameter does not apply to permissions
+    set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
+    a mask on access control lists also, they need to set the <smbconfoption name="directory security mask"/>.</para>
+</description>
+
+<related>force directory mode</related>
+<related>create mask</related>
+<related>directory security mask</related>
+<related>inherit permissions</related>
+<value type="default">0755</value>
+<value type="example">0775</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/directorysecuritymask.xml b/docs-xml/smbdotconf/security/directorysecuritymask.xml
new file mode 100644
index 00000000000..5ed85ae3f86
--- /dev/null
+++ b/docs-xml/smbdotconf/security/directorysecuritymask.xml
@@ -0,0 +1,39 @@
+<samba:parameter name="directory security mask"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter controls what UNIX permission bits
+    will be set when a Windows NT client is manipulating the UNIX
+    permission on a directory using the native NT security dialog
+    box.</para>
+
+    <para>
+	This parameter is applied as a mask (AND'ed with) to the incoming permission bits, thus resetting
+        any bits not in this mask.  Make sure not to mix up this parameter with <smbconfoption name="force
+	directory security mode"/>, which works similar like this one but uses logical OR instead of AND.
+	Essentially, zero bits in this mask are a set of bits that will always be set to zero.
+	</para>
+
+    <para>
+	Essentially, all bits set to zero in this mask will result in setting to zero the corresponding bits on the
+	file permissions regardless of the previous status of this bits on the file.
+    </para>
+
+    <para>If not set explicitly this parameter is set to 0777
+    meaning a user is allowed to set all the user/group/world
+    permissions on a directory.</para>
+
+    <para><emphasis>Note</emphasis> that users who can access the 
+    Samba server through other means can easily bypass this restriction, 
+    so it is primarily useful for standalone &quot;appliance&quot; systems.  
+    Administrators of most normal systems will probably want to leave
+	it as the default of <constant>0777</constant>.</para>
+</description>
+
+<related>force directory security mode</related>
+<related>security mask</related>
+<related>force security mode</related>
+<value type="default">0777</value>
+<value type="example">0700</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/encryptpasswords.xml b/docs-xml/smbdotconf/security/encryptpasswords.xml
new file mode 100644
index 00000000000..1a631fd098f
--- /dev/null
+++ b/docs-xml/smbdotconf/security/encryptpasswords.xml
@@ -0,0 +1,40 @@
+<samba:parameter name="encrypt passwords"
+                 context="G"
+				 type="boolean"
+                 basic="1" advanced="1" wizard="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean controls whether encrypted passwords 
+    will be negotiated with the client. Note that Windows NT 4.0 SP3 and 
+    above and also Windows 98 will by default expect encrypted passwords 
+    unless a registry entry is changed. To use encrypted passwords in 
+    Samba see the chapter "User Database" in the Samba HOWTO Collection.
+    </para>
+
+    <para>
+    MS Windows clients that expect Microsoft encrypted passwords and that
+    do not have plain text password support enabled will be able to
+    connect only to a Samba server that has encrypted password support
+    enabled and for which the user accounts have a valid encrypted password.
+    Refer to the smbpasswd command man page for information regarding the
+    creation of encrypted passwords for user accounts.
+    </para>
+
+    <para>
+    The use of plain text passwords is NOT advised as support for this feature
+    is no longer maintained in Microsoft Windows products. If you want to use
+    plain text passwords you must set this parameter to no.
+    </para>
+
+    <para>In order for encrypted passwords to work correctly
+    <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> must either 
+    have access to a local <citerefentry><refentrytitle>smbpasswd</refentrytitle>
+    <manvolnum>5</manvolnum></citerefentry> file (see the <citerefentry><refentrytitle>smbpasswd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> program for information on how to set up 
+    and maintain this file), or set the <smbconfoption name="security">[server|domain|ads]</smbconfoption> parameter which 
+    causes <command moreinfo="none">smbd</command> to authenticate against another 
+	server.</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/forcecreatemode.xml b/docs-xml/smbdotconf/security/forcecreatemode.xml
new file mode 100644
index 00000000000..8a6449fe21c
--- /dev/null
+++ b/docs-xml/smbdotconf/security/forcecreatemode.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="force create mode"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter specifies a set of UNIX mode bit 
+    permissions that will <emphasis>always</emphasis> be set on a 
+    file created by Samba. This is done by bitwise 'OR'ing these bits onto 
+    the mode bits of a file that is being created or having its 
+    permissions changed. The default for this parameter is (in octal) 
+    000. The modes in this parameter are bitwise 'OR'ed onto the file 
+    mode after the mask set in the <parameter moreinfo="none">create mask</parameter> 
+    parameter is applied.</para>
+
+	<para>The example below would force all created files to have read and execute 
+    permissions set for 'group' and 'other' as well as the 
+    read/write/execute bits set for the 'user'.</para>
+
+</description>
+
+<related>create mask</related>
+<related>inherit permissions</related>
+
+<value type="default">000</value>
+<value type="example">0755</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/forcedirectorymode.xml b/docs-xml/smbdotconf/security/forcedirectorymode.xml
new file mode 100644
index 00000000000..7effc0e3999
--- /dev/null
+++ b/docs-xml/smbdotconf/security/forcedirectorymode.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="force directory mode"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter specifies a set of UNIX mode bit 
+    permissions that will <emphasis>always</emphasis> be set on a directory 
+    created by Samba. This is done by bitwise 'OR'ing these bits onto the 
+    mode bits of a directory that is being created. The default for this 
+    parameter is (in octal) 0000 which will not add any extra permission 
+    bits to a created directory. This operation is done after the mode 
+    mask in the parameter <parameter moreinfo="none">directory mask</parameter> is 
+    applied.</para>
+
+	<para>The example below would force all created directories to have read and execute
+    permissions set for 'group' and 'other' as well as the
+    read/write/execute bits set for the 'user'.</para>
+</description>
+
+<value type="default">000</value>
+<value type="example">0755</value>
+
+<related>directory mask</related>
+<related>inherit permissions</related>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/forcedirectorysecuritymode.xml b/docs-xml/smbdotconf/security/forcedirectorysecuritymode.xml
new file mode 100644
index 00000000000..2c15ec2753a
--- /dev/null
+++ b/docs-xml/smbdotconf/security/forcedirectorysecuritymode.xml
@@ -0,0 +1,43 @@
+<samba:parameter name="force directory security mode"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating
+	the UNIX permission on a directory using the native NT security dialog box.
+	</para>
+
+    <para>
+	This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this
+	mask that the user may have modified to be on.  Make sure not to mix up this parameter with <smbconfoption
+	name="directory security mask"/>, which works in a similar manner to this one, but uses a logical AND instead
+	of an OR. 
+	</para>
+
+	<para>
+	Essentially, this mask may be treated as a set of bits that, when modifying security on a directory, 
+	to will enable (1) any flags that are off (0) but which the mask has set to on (1).
+	</para>
+
+    <para>
+	If not set explicitly this parameter is 0000, which allows a user to modify all the user/group/world
+	permissions on a directory without restrictions.
+	</para>
+
+    <note><para>
+	Users who can access the Samba server through other means can easily bypass this restriction, so it is
+	primarily useful for standalone &quot;appliance&quot; systems.  Administrators of most normal systems will
+	probably want to leave it set as 0000.
+	</para></note>
+
+</description>
+
+<value type="default">0</value>
+<value type="example">700</value>
+
+<related>directory security mask</related>
+<related>security mask</related>
+<related>force security mode</related>
+
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/forcegroup.xml b/docs-xml/smbdotconf/security/forcegroup.xml
new file mode 100644
index 00000000000..f6c9974f99d
--- /dev/null
+++ b/docs-xml/smbdotconf/security/forcegroup.xml
@@ -0,0 +1,39 @@
+<samba:parameter name="force group"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>group</synonym>
+<description>
+    <para>This specifies a UNIX group name that will be 
+    assigned as the default primary group for all users connecting 
+    to this service. This is useful for sharing files by ensuring 
+    that all access to files on service will use the named group for 
+    their permissions checking. Thus, by assigning permissions for this 
+    group to the files and directories within this service the Samba 
+    administrator can restrict or allow sharing of these files.</para>
+
+    <para>In Samba 2.0.5 and above this parameter has extended 
+    functionality in the following way. If the group name listed here 
+    has a '+' character prepended to it then the current user accessing 
+    the share only has the primary group default assigned to this group 
+    if they are already assigned as a member of that group. This allows 
+    an administrator to decide that only users who are already in a 
+    particular group will create files with group ownership set to that 
+    group. This gives a finer granularity of ownership assignment. For 
+    example, the setting <filename moreinfo="none">force group = +sys</filename> means 
+    that only users who are already in group sys will have their default
+    primary group assigned to sys when accessing this Samba share. All
+    other users will retain their ordinary primary group.</para>
+
+    <para>
+	If the <smbconfoption name="force user"/> parameter is also set the group specified in 
+    <parameter moreinfo="none">force group</parameter> will override the primary group
+    set in <parameter moreinfo="none">force user</parameter>.</para>
+
+</description>
+
+<related>force user</related>
+
+<value type="default"/>
+<value type="example">agroup</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/forcesecuritymode.xml b/docs-xml/smbdotconf/security/forcesecuritymode.xml
new file mode 100644
index 00000000000..7451ef91ae8
--- /dev/null
+++ b/docs-xml/smbdotconf/security/forcesecuritymode.xml
@@ -0,0 +1,41 @@
+<samba:parameter name="force security mode"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating 
+    the UNIX permission on a file using the native NT security dialog box.
+	</para>
+		
+    <para>
+	This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this
+	mask that the user may have modified to be on.  Make sure not to mix up this parameter with <smbconfoption
+	name="security mask"/>, which works similar like this one but uses logical AND instead of OR. 
+	</para>
+
+	<para>
+	Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a file,
+	the user has always set to be on.
+	</para>
+
+    <para>
+	If not set explicitly this parameter is set to 0, and allows a user to modify all the user/group/world
+	permissions on a file, with no restrictions.
+	</para>
+		
+    <para><emphasis>
+	Note</emphasis> that users who can access the Samba server through other means can easily bypass this
+	restriction, so it is primarily useful for standalone &quot;appliance&quot; systems. Administrators of most
+	normal systems will probably want to leave this set to 0000.
+	</para>
+
+</description>
+
+<value type="default">0</value>
+<value type="example">700</value>
+
+<related>force directory security mode</related>
+<related>directory security mask</related>
+<related>security mask</related>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/forceunknownacluser.xml b/docs-xml/smbdotconf/security/forceunknownacluser.xml
new file mode 100644
index 00000000000..4c0949f052a
--- /dev/null
+++ b/docs-xml/smbdotconf/security/forceunknownacluser.xml
@@ -0,0 +1,27 @@
+<samba:parameter name="force unknown acl user"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+
+<description>
+    <para>
+    If this parameter is set, a Windows NT ACL that contains an unknown SID (security descriptor, or 
+    representation of a user or group id) as the owner or group owner of the file will be silently
+    mapped into the current UNIX uid or gid of the currently connected user.
+    </para>
+
+    <para>
+    This is designed to allow Windows NT clients to copy files and folders containing ACLs that were 
+    created locally on the client machine and contain users local to that machine only (no domain
+    users) to be copied to a Samba server (usually with XCOPY /O) and have the unknown userid and 
+    groupid of the file owner map to the current connected user.  This can only be fixed correctly
+    when winbindd allows arbitrary mapping from any Windows NT SID to a UNIX uid or gid.
+    </para>
+
+    <para>
+    Try using this parameter when XCOPY /O gives an ACCESS_DENIED error.
+    </para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/forceuser.xml b/docs-xml/smbdotconf/security/forceuser.xml
new file mode 100644
index 00000000000..f1ec5d449c4
--- /dev/null
+++ b/docs-xml/smbdotconf/security/forceuser.xml
@@ -0,0 +1,27 @@
+<samba:parameter name="force user"
+				 type="string"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This specifies a UNIX user name that will be 
+    assigned as the default user for all users connecting to this service. 
+    This is useful for sharing files. You should also use it carefully 
+    as using it incorrectly can cause security problems.</para>
+
+    <para>This user name only gets used once a connection is established. 
+    Thus clients still need to connect as a valid user and supply a 
+    valid password. Once connected, all file operations will be performed 
+    as the &quot;forced user&quot;, no matter what username the client connected 
+    as.  This can be very useful.</para>
+
+    <para>In Samba 2.0.5 and above this parameter also causes the 
+    primary group of the forced user to be used as the primary group 
+    for all file activity. Prior to 2.0.5 the primary group was left 
+    as the primary group of the connecting user (this was a bug).</para>
+
+</description>
+
+<related>force group</related>
+<value type="default"/>
+<value type="example">auser</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/guestaccount.xml b/docs-xml/smbdotconf/security/guestaccount.xml
new file mode 100644
index 00000000000..8132835a821
--- /dev/null
+++ b/docs-xml/smbdotconf/security/guestaccount.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="guest account"
+                 context="G"
+				 type="string"
+                 basic="1" advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This is a username which will be used for access 
+    to services which are specified as <smbconfoption name="guest ok"/> (see below). Whatever privileges this 
+    user has will be available to any client connecting to the guest service. 
+    This user must exist in the password file, but does not require
+    a valid login. The user account &quot;ftp&quot; is often a good choice 
+    for this parameter. 
+    </para>
+
+    <para>On some systems the default guest account &quot;nobody&quot; may not 
+    be able to print. Use another account in this case. You should test 
+    this by trying to log in as your guest user (perhaps by using the 
+    <command moreinfo="none">su -</command> command) and trying to print using the 
+    system print command such as <command moreinfo="none">lpr(1)</command> or <command moreinfo="none">
+    lp(1)</command>.</para>
+
+    <para>This parameter does not accept % macros, because
+    many parts of the system require this value to be
+	constant for correct operation.</para>
+</description>
+<value type="default">nobody<comment>default can be changed at compile-time</comment></value>
+<value type="example">ftp</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/guestok.xml b/docs-xml/smbdotconf/security/guestok.xml
new file mode 100644
index 00000000000..7cbf4e50bbd
--- /dev/null
+++ b/docs-xml/smbdotconf/security/guestok.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="guest ok"
+				 type="boolean"
+                 context="S"
+                 basic="1" advanced="1" print="1" developer="1"
+				 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>public</synonym>
+<description>
+    <para>If this parameter is <constant>yes</constant> for 
+    a service, then no password is required to connect to the service. 
+    Privileges will be those of the <smbconfoption name="guest account"/>.</para>
+
+    <para>This paramater nullifies the benifits of setting
+    <smbconfoption name="restrict anonymous">2</smbconfoption>
+	</para>
+
+    <para>See the section below on <smbconfoption name="security"/> for more information about this option.
+	</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/guestonly.xml b/docs-xml/smbdotconf/security/guestonly.xml
new file mode 100644
index 00000000000..258eba92678
--- /dev/null
+++ b/docs-xml/smbdotconf/security/guestonly.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="guest only"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>only guest</synonym>
+<description>
+    <para>If this parameter is <constant>yes</constant> for 
+    a service, then only guest connections to the service are permitted. 
+    This parameter will have no effect if <smbconfoption name="guest ok"/> is not set for the service.</para>
+
+    <para>See the section below on <smbconfoption name="security"/> for more information about this option.
+	</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/hostsallow.xml b/docs-xml/smbdotconf/security/hostsallow.xml
new file mode 100644
index 00000000000..849b515f46a
--- /dev/null
+++ b/docs-xml/smbdotconf/security/hostsallow.xml
@@ -0,0 +1,63 @@
+<samba:parameter name="hosts allow"
+                 context="S"
+				 type="list"
+                 basic="1" advanced="1" print="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>allow hosts</synonym>
+<description>
+    <para>A synonym for this parameter is <smbconfoption name="allow hosts"/>.</para>
+		
+    <para>This parameter is a comma, space, or tab delimited 
+    set of hosts which are permitted to access a service.</para>
+
+    <para>If specified in the [global] section then it will
+    apply to all services, regardless of whether the individual 
+    service has a different setting.</para>
+
+    <para>You can specify the hosts by name or IP number. For 
+    example, you could restrict access to only the hosts on a 
+    Class C subnet with something like <command>allow hosts = 150.203.5.</command>.
+	The full syntax of the list is described in the man 
+    page <filename>hosts_access(5)</filename>. Note that this man
+    page may not be present on your system, so a brief description will
+    be given here also.</para>
+
+    <para>Note that the localhost address 127.0.0.1 will always 
+    be allowed access unless specifically denied by a <smbconfoption name="hosts deny"/> option.</para>
+
+    <para>You can also specify hosts by network/netmask pairs and 
+    by netgroup names if your system supports netgroups. The 
+    <emphasis>EXCEPT</emphasis> keyword can also be used to limit a 
+    wildcard list. The following examples may provide some help:</para>
+
+<para>Example 1: allow all IPs in 150.203.*.*; except one</para>
+
+    <para><command moreinfo="none">hosts allow = 150.203. EXCEPT 150.203.6.66</command></para>
+
+    <para>Example 2: allow hosts that match the given network/netmask</para>
+
+    <para><command moreinfo="none">hosts allow = 150.203.15.0/255.255.255.0</command></para>
+
+    <para>Example 3: allow a couple of hosts</para>
+
+    <para><command moreinfo="none">hosts allow = lapland, arvidsjaur</command></para>
+
+    <para>Example 4: allow only hosts in NIS netgroup &quot;foonet&quot;, but 
+    deny access from one particular host</para>
+
+    <para><command moreinfo="none">hosts allow = @foonet</command></para>
+
+    <para><command moreinfo="none">hosts deny = pirate</command></para>
+
+    <note><para>Note that access still requires suitable user-level passwords.</para></note>
+
+    <para>See <citerefentry><refentrytitle>testparm</refentrytitle>
+    <manvolnum>1</manvolnum></citerefentry> for a way of testing your host access 
+    to see if it does what you expect.</para>
+
+		
+</description>
+
+<value type="example">150.203.5. myhost.mynet.edu.au</value>
+<value type="default"><comment>none (i.e., all hosts permitted access)</comment></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/hostsdeny.xml b/docs-xml/smbdotconf/security/hostsdeny.xml
new file mode 100644
index 00000000000..136f86c9c8a
--- /dev/null
+++ b/docs-xml/smbdotconf/security/hostsdeny.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="hosts deny"
+                 context="S"
+				 type="list"
+                 basic="1" advanced="1" print="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>deny hosts</synonym>
+<description>
+    <para>The opposite of <parameter moreinfo="none">hosts allow</parameter> 
+    - hosts listed here are <emphasis>NOT</emphasis> permitted access to 
+    services unless the specific services have their own lists to override 
+    this one. Where the lists conflict, the <parameter moreinfo="none">allow</parameter> 
+	list takes precedence.</para>
+
+	<para>
+	In the event that it is necessary to deny all by default, use the keyword
+	ALL (or the netmask <literal>0.0.0.0/0</literal>) and then explicitly specify
+	to the <smbconfoption name="hosts allow">hosts allow</smbconfoption> parameter those hosts
+	that should be permitted access.
+	</para>
+</description>
+
+<value type="default"><comment>none (i.e., no hosts specifically excluded)</comment></value>
+
+<value type="example">150.203.4. badhost.mynet.edu.au</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/inheritacls.xml b/docs-xml/smbdotconf/security/inheritacls.xml
new file mode 100644
index 00000000000..44afa8a3e2e
--- /dev/null
+++ b/docs-xml/smbdotconf/security/inheritacls.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="inherit acls"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter can be used to ensure that if default acls
+    exist on parent directories, they are always honored when creating a
+    new file or subdirectory in these parent directories. The default 
+    behavior is to use the unix mode specified when creating the directory. 
+    Enabling this option sets the unix mode to 0777, thus guaranteeing that 
+    default directory acls are propagated.
+</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/inheritowner.xml b/docs-xml/smbdotconf/security/inheritowner.xml
new file mode 100644
index 00000000000..ba4fc617cb5
--- /dev/null
+++ b/docs-xml/smbdotconf/security/inheritowner.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="inherit owner"
+                 context="S"
+		 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>The ownership of new files and directories 
+	is normally governed by effective uid of the connected user.
+	This option allows the Samba administrator to specify that
+	the ownership for new files and directories should be controlled
+	by the ownership of the parent directory.</para>
+	
+	<para>Common scenarios where this behavior is useful is in 
+	implementing drop-boxes where users can create and edit files but not 
+	delete them and to ensure that newly create files in a user's
+	roaming profile directory are actually owner by the user.</para>
+</description>
+
+<related>inherit permissions</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/inheritpermissions.xml b/docs-xml/smbdotconf/security/inheritpermissions.xml
new file mode 100644
index 00000000000..6e09f4f033c
--- /dev/null
+++ b/docs-xml/smbdotconf/security/inheritpermissions.xml
@@ -0,0 +1,35 @@
+<samba:parameter name="inherit permissions"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	The permissions on new files and directories are normally governed by <smbconfoption name="create mask"/>,
+	<smbconfoption name="directory mask"/>, <smbconfoption name="force create mode"/> and <smbconfoption
+	name="force directory mode"/> but the boolean inherit permissions parameter overrides this.
+	</para>
+		
+    <para>New directories inherit the mode of the parent directory,
+    including bits such as setgid.</para>
+
+    <para>
+	New files inherit their read/write bits from the parent directory.  Their execute bits continue to be
+	determined by <smbconfoption name="map archive"/>, <smbconfoption name="map hidden"/> and <smbconfoption
+	name="map system"/> as usual.
+	</para>
+
+    <para>Note that the setuid bit is <emphasis>never</emphasis> set via 
+    inheritance (the code explicitly prohibits this).</para>
+
+    <para>This can be particularly useful on large systems with 
+    many users, perhaps several thousand, to allow a single [homes] 
+    share to be used flexibly by each user.</para>
+</description>
+
+<related>create mask</related>
+<related>directory mask</related>
+<related>force create mode</related>
+<related>force directory mode</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/invalidusers.xml b/docs-xml/smbdotconf/security/invalidusers.xml
new file mode 100644
index 00000000000..f4ed66f3145
--- /dev/null
+++ b/docs-xml/smbdotconf/security/invalidusers.xml
@@ -0,0 +1,34 @@
+<samba:parameter name="invalid users"
+                 context="S"
+				 type="list"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This is a list of users that should not be allowed 
+    to login to this service. This is really a <emphasis>paranoid</emphasis> 
+    check to absolutely ensure an improper setting does not breach 
+    your security.</para>
+		
+    <para>A name starting with a '@' is interpreted as an NIS 
+    netgroup first (if your system supports NIS), and then as a UNIX 
+    group if the name was not found in the NIS netgroup database.</para>
+
+    <para>A name starting with '+' is interpreted only 
+    by looking in the UNIX group database via the NSS getgrnam() interface. A name starting with 
+    '&amp;' is interpreted only by looking in the NIS netgroup database 
+    (this requires NIS to be working on your system). The characters 
+    '+' and '&amp;' may be used at the start of the name in either order 
+    so the value <parameter moreinfo="none">+&amp;group</parameter> means check the 
+    UNIX group database, followed by the NIS netgroup database, and 
+    the value <parameter moreinfo="none">&amp;+group</parameter> means check the NIS
+    netgroup database, followed by the UNIX group database (the 
+    same as the '@' prefix).</para>
+
+    <para>The current servicename is substituted for <parameter moreinfo="none">%S</parameter>. 
+		This is useful in the [homes] section.</para>
+</description>
+
+<related>valid users</related>
+
+<value type="default"><comment>no invalid users</comment></value>
+<value type="example">root fred admin @wheel</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/lanmanauth.xml b/docs-xml/smbdotconf/security/lanmanauth.xml
new file mode 100644
index 00000000000..341952205f6
--- /dev/null
+++ b/docs-xml/smbdotconf/security/lanmanauth.xml
@@ -0,0 +1,33 @@
+<samba:parameter name="lanman auth"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter determines whether or not <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> will attempt to
+    authenticate users or permit password changes
+    using the LANMAN password hash. If disabled, only clients which support NT 
+    password hashes (e.g. Windows NT/2000 clients, smbclient, but not 
+    Windows 95/98 or the MS DOS network client) will be able to
+    connect to the Samba host.</para>
+
+    <para>The LANMAN encrypted response is easily broken, due to it's
+    case-insensitive nature, and the choice of algorithm.  Servers
+    without Windows 95/98/ME or MS DOS clients are advised to disable
+    this option.  </para>
+		
+    <para>Unlike the <command moreinfo="none">encrypt
+    passwords</command> option, this parameter cannot alter client
+    behaviour, and the LANMAN response will still be sent over the
+    network.  See the <command moreinfo="none">client lanman
+    auth</command> to disable this for Samba's clients (such as smbclient)</para>
+
+    <para>If this option, and <command moreinfo="none">ntlm
+    auth</command> are both disabled, then only NTLMv2 logins will be
+    permited.  Not all clients support NTLMv2, and most will require
+    special configuration to use it.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/maptoguest.xml b/docs-xml/smbdotconf/security/maptoguest.xml
new file mode 100644
index 00000000000..0f680ae71c4
--- /dev/null
+++ b/docs-xml/smbdotconf/security/maptoguest.xml
@@ -0,0 +1,76 @@
+<samba:parameter name="map to guest"
+				 type="enum"
+                 context="G"
+                 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter is only useful in <smbconfoption name="SECURITY">
+    security</smbconfoption> modes other than <parameter moreinfo="none">security = share</parameter> 
+    and <parameter moreinfo="none">security = server</parameter>
+    - i.e. <constant>user</constant>, and <constant>domain</constant>.</para>
+
+    <para>This parameter can take four different values, which tell
+    <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> what to do with user 
+    login requests that don't match a valid UNIX user in some way.</para>
+
+    <para>The four settings are :</para>
+
+    <itemizedlist>
+	<listitem>
+	    <para><constant>Never</constant> - Means user login 
+	    requests with an invalid password are rejected. This is the 
+	    default.</para>
+	</listitem>
+			
+	<listitem>
+	    <para><constant>Bad User</constant> - Means user
+	    logins with an invalid password are rejected, unless the username 
+	    does not exist, in which case it is treated as a guest login and 
+	    mapped into the <smbconfoption name="guest account"/>.</para>
+	</listitem>
+
+	<listitem>
+	    <para><constant>Bad Password</constant> - Means user logins 
+	    with an invalid password are treated as a guest login and mapped 
+	    into the <smbconfoption name="guest account"/>. Note that 
+	    this can cause problems as it means that any user incorrectly typing 
+	    their password will be silently logged on as &quot;guest&quot; - and 
+	    will not know the reason they cannot access files they think
+	    they should - there will have been no message given to them
+	    that they got their password wrong. Helpdesk services will
+	    <emphasis>hate</emphasis> you if you set the <parameter moreinfo="none">map to 
+	    guest</parameter> parameter this way :-).</para>
+	</listitem>
+	<listitem>
+	    <para><constant>Bad Uid</constant> - Is only applicable when Samba is configured
+	    in some type of domain mode security (security = {domain|ads}) and means that
+	    user logins which are successfully authenticated but which have no valid Unix
+	    user account (and smbd is unable to create one) should be mapped to the defined
+	    guest account. This was the default behavior of Samba 2.x releases.  Note that 
+	    if a member server is running winbindd,  this option should never be required
+	    because the nss_winbind library will export the Windows domain users and groups
+	    to the underlying OS via the Name Service Switch interface.</para>
+	</listitem>
+    </itemizedlist>
+
+    <para>Note that this parameter is needed to set up &quot;Guest&quot; 
+    share services when using <parameter moreinfo="none">security</parameter> modes other than 
+    share and server. This is because in these modes the name of the resource being
+    requested is <emphasis>not</emphasis> sent to the server until after 
+    the server has successfully authenticated the client so the server 
+    cannot make authentication decisions at the correct time (connection 
+    to the share) for &quot;Guest&quot; shares. This parameter is not useful with
+    <parameter moreinfo="none">security = server</parameter> as in this security mode
+    no information is returned about whether a user logon failed due to
+    a bad username or bad password, the same error is returned from a modern server
+    in both cases.</para>
+
+    <para>For people familiar with the older Samba releases, this 
+    parameter maps to the old compile-time setting of the <constant>
+		GUEST_SESSSETUP</constant> value in local.h.</para>
+</description>
+
+<value type="default">Never</value>
+<value type="example">Bad User</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/ntlmauth.xml b/docs-xml/smbdotconf/security/ntlmauth.xml
new file mode 100644
index 00000000000..ebcdad72a1e
--- /dev/null
+++ b/docs-xml/smbdotconf/security/ntlmauth.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="ntlm auth"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter determines whether or not <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> will attempt to
+    authenticate users using the NTLM encrypted password response.
+    If disabled, either the lanman password hash or an NTLMv2 response
+    will need to be sent by the client.</para>
+
+    <para>If this option, and <command moreinfo="none">lanman
+    auth</command> are both disabled, then only NTLMv2 logins will be
+    permited.  Not all clients support NTLMv2, and most will require
+	special configuration to us it.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/nullpasswords.xml b/docs-xml/smbdotconf/security/nullpasswords.xml
new file mode 100644
index 00000000000..402114e2598
--- /dev/null
+++ b/docs-xml/smbdotconf/security/nullpasswords.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="null passwords"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>Allow or disallow client access to accounts that have null passwords. </para>
+
+    <para>See also <citerefentry><refentrytitle>smbpasswd</refentrytitle>
+			<manvolnum>5</manvolnum></citerefentry>.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/obeypamrestrictions.xml b/docs-xml/smbdotconf/security/obeypamrestrictions.xml
new file mode 100644
index 00000000000..40777f4f5da
--- /dev/null
+++ b/docs-xml/smbdotconf/security/obeypamrestrictions.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="obey pam restrictions"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>When Samba 3.0 is configured to enable PAM support
+    (i.e. --with-pam), this parameter will control whether or not Samba
+    should obey PAM's account and session management directives.  The 
+    default behavior is to use PAM for clear text authentication only
+    and to ignore any account or session management.  Note that Samba
+    always ignores PAM for authentication in the case of <smbconfoption 
+	name="encrypt passwords">yes</smbconfoption>.  The reason 
+    is that PAM modules cannot support the challenge/response
+    authentication mechanism needed in the presence of SMB password encryption.
+</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/onlyuser.xml b/docs-xml/smbdotconf/security/onlyuser.xml
new file mode 100644
index 00000000000..b1ef1b76060
--- /dev/null
+++ b/docs-xml/smbdotconf/security/onlyuser.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="only user"
+					type="boolean"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This is a boolean option that controls whether 
+    connections with usernames not in the <parameter moreinfo="none">user</parameter> 
+    list will be allowed. By default this option is disabled so that a 
+    client can supply a username to be used by the server.  Enabling
+    this parameter will force the server to only use the login 
+    names from the <parameter moreinfo="none">user</parameter> list and is only really
+    useful in <smbconfoption name="security">share</smbconfoption> level security.</para>
+
+    <para>Note that this also means Samba won't try to deduce 
+    usernames from the service name. This can be annoying for 
+    the [homes] section. To get around this you could use <command moreinfo="none">user =
+    %S</command> which means your <parameter moreinfo="none">user</parameter> list
+    will be just the service name, which for home directories is the 
+    name of the user.</para>
+</description>
+
+<related>user</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/pampasswordchange.xml b/docs-xml/smbdotconf/security/pampasswordchange.xml
new file mode 100644
index 00000000000..e5c04d405cc
--- /dev/null
+++ b/docs-xml/smbdotconf/security/pampasswordchange.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="pam password change"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>With the addition of better PAM support in Samba 2.2, 
+    this parameter, it is possible to use PAM's password change control 
+    flag for Samba.  If enabled, then PAM will be used for password
+    changes when requested by an SMB client instead of the program listed in 
+    <smbconfoption name="passwd program"/>. 
+    It should be possible to enable this without changing your 
+    <smbconfoption name="passwd chat"/> parameter for most setups.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/passdbbackend.xml b/docs-xml/smbdotconf/security/passdbbackend.xml
new file mode 100644
index 00000000000..487d8b8a9d1
--- /dev/null
+++ b/docs-xml/smbdotconf/security/passdbbackend.xml
@@ -0,0 +1,64 @@
+<samba:parameter name="passdb backend"
+                 context="G"
+		 type="list"
+                 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+    <para>This option allows the administrator to chose which backend
+    will be used for storing user and possibly group information.  This allows 
+    you to swap between different storage mechanisms without recompile. </para>
+
+    <para>The parameter value is divided into two parts, the backend's name, and a 'location'
+    string that has meaning only to that particular backed.  These are separated
+    by a : character.</para>
+
+    <para>Available backends can include:
+	<itemizedlist>
+	    <listitem>
+		<para><command moreinfo="none">smbpasswd</command> - The default smbpasswd
+		backend. Takes a path to the smbpasswd file as an optional argument.
+		</para>
+	    </listitem>
+			
+	    <listitem>
+		<para><command moreinfo="none">tdbsam</command> - The TDB based password storage
+                backend.  Takes a path to the TDB as an optional argument (defaults to passdb.tdb 
+                in the <smbconfoption name="private dir"/> directory.</para>
+	    </listitem>
+			
+	    <listitem>
+		<para><command moreinfo="none">ldapsam</command> - The LDAP based passdb 
+                backend.  Takes an LDAP URL as an optional argument (defaults to 
+                <command moreinfo="none">ldap://localhost</command>)</para>
+			
+		<para>LDAP connections should be secured where possible.  This may be done using either
+                Start-TLS (see <smbconfoption name="ldap ssl"/>) or by
+                specifying <parameter moreinfo="none">ldaps://</parameter> in
+                the URL argument. </para>
+
+                <para>Multiple servers may also be specified in double-quotes.
+		Whether multiple servers are supported or not and the exact
+		syntax depends on the LDAP library you use.
+		</para>
+
+	    </listitem>
+	</itemizedlist>
+
+    </para>
+	Examples of use are:
+<programlisting>
+passdb backend = tdbsam:/etc/samba/private/passdb.tdb 
+
+or multi server LDAP URL with OpenLDAP library:
+
+passdb backend = ldapsam:"ldap://ldap-1.example.com ldap://ldap-2.example.com"
+
+or multi server LDAP URL with Netscape based LDAP library:
+
+passdb backend = ldapsam:"ldap://ldap-1.example.com ldap-2.example.com"
+</programlisting>
+</description>
+
+<value type="default">smbpasswd</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/passdbexpandexplicit.xml b/docs-xml/smbdotconf/security/passdbexpandexplicit.xml
new file mode 100644
index 00000000000..08c893191a2
--- /dev/null
+++ b/docs-xml/smbdotconf/security/passdbexpandexplicit.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="passdb expand explicit"
+                 context="G"
+                 advanced="1" developer="0"
+				 type="boolean"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	This parameter controls whether Samba substitutes %-macros in the passdb fields if they are explicitly set. We
+	used to expand macros here, but this turned out to be a bug because the Windows client can expand a variable
+	%G_osver% in which %G would have been substituted by the user's primary group.
+    </para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/passwdchat.xml b/docs-xml/smbdotconf/security/passwdchat.xml
new file mode 100644
index 00000000000..da18142dfa3
--- /dev/null
+++ b/docs-xml/smbdotconf/security/passwdchat.xml
@@ -0,0 +1,60 @@
+<samba:parameter name="passwd chat"
+                 context="G"
+		 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This string controls the <emphasis>&quot;chat&quot;</emphasis> 
+    conversation that takes places between <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> and the local password changing
+    program to change the user's password. The string describes a 
+    sequence of response-receive pairs that <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> uses to determine what to send to the 
+    <smbconfoption name="passwd program"/> and what to expect back. If the expected output is not 
+    received then the password is not changed.</para>
+
+    <para>This chat sequence is often quite site specific, depending 
+    on what local methods are used for password control (such as NIS 
+    etc).</para>
+
+    <para>Note that this parameter only is only used if the <smbconfoption
+    name="unix password sync"/> parameter is set  to <constant>yes</constant>. This sequence is 
+    then called <emphasis>AS ROOT</emphasis> when the SMB password  in the 
+    smbpasswd file is being changed, without access to the old password
+    cleartext. This means that root must be able to reset the user's password without
+    knowing the text of the previous password. In the presence of
+    NIS/YP,  this means that the <smbconfoption name="passwd program"/> must
+    be executed on the NIS master.
+    </para>
+
+    <para>The string can contain the macro <parameter
+    moreinfo="none">%n</parameter> which is substituted 
+    for the new password.  The old passsword (<parameter 
+    moreinfo="none">%o</parameter>) is only available when
+    <smbconfoption name="encrypt passwords"/> has been disabled.
+    The chat sequence can also contain the standard macros 
+    \n, \r, \t and \s to give line-feed, carriage-return, tab 
+    and space.  The chat sequence string can also contain 
+    a '*' which matches any sequence of characters. Double quotes can 
+    be used to collect strings with spaces in them into a single 
+    string.</para>
+
+    <para>If the send string in any part of the chat sequence  is a full
+    stop &quot;.&quot;,  then no string is sent. Similarly,  if the
+    expect string is a full stop then no string is expected.</para>
+
+    <para>If the <smbconfoption name="pam password change"/> parameter is set to <constant>yes</constant>, the
+	chat pairs may be matched in any order, and success is determined by the PAM result, not any particular
+	output. The \n macro is ignored for PAM conversions.
+    </para>
+
+</description>
+
+<related>unix password sync</related>
+<related>passwd program</related>
+<related>passwd chat debug</related>
+<related>pam password change</related>
+
+<value type="default">*new*password* %n\n*new*password* %n\n *changed*</value>
+<value type="example">&quot;*Enter NEW password*&quot; %n\n &quot;*Reenter NEW password*&quot; %n\n &quot;*Password changed*&quot;</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/passwdchatdebug.xml b/docs-xml/smbdotconf/security/passwdchatdebug.xml
new file mode 100644
index 00000000000..24bcbdba108
--- /dev/null
+++ b/docs-xml/smbdotconf/security/passwdchatdebug.xml
@@ -0,0 +1,27 @@
+<samba:parameter name="passwd chat debug"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean specifies if the passwd chat script 
+    parameter is run in <emphasis>debug</emphasis> mode. In this mode the 
+    strings passed to and received from the passwd chat are printed 
+    in the <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> log with a 
+    <smbconfoption name="debug level"/> 
+    of 100. This is a dangerous option as it will allow plaintext passwords 
+    to be seen in the <command moreinfo="none">smbd</command> log. It is available to help 
+    Samba admins debug their <parameter moreinfo="none">passwd chat</parameter> scripts 
+    when calling the <parameter moreinfo="none">passwd program</parameter> and should 
+    be turned off after this has been done. This option has no effect if the 
+    <smbconfoption name="pam password change"/>
+	parameter is set. This parameter is off by default.</para>
+</description>
+
+<related>passwd chat</related>
+<related>pam password change</related>
+<related>passwd program</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/passwdchattimeout.xml b/docs-xml/smbdotconf/security/passwdchattimeout.xml
new file mode 100644
index 00000000000..c371aa2c88c
--- /dev/null
+++ b/docs-xml/smbdotconf/security/passwdchattimeout.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="passwd chat timeout"
+                 context="G"
+				 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This integer specifies the number of seconds smbd will wait for an initial
+    answer from a passwd chat script being run. Once the initial answer is received
+    the subsequent answers must be received in one tenth of this time. The default it
+    two seconds.</para>
+</description>
+
+<value type="default">2</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/passwdprogram.xml b/docs-xml/smbdotconf/security/passwdprogram.xml
new file mode 100644
index 00000000000..4158c1b7a6a
--- /dev/null
+++ b/docs-xml/smbdotconf/security/passwdprogram.xml
@@ -0,0 +1,37 @@
+<samba:parameter name="passwd program"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+    <para>The name of a program that can be used to set 
+    UNIX user passwords.  Any occurrences of <parameter moreinfo="none">%u</parameter> 
+    will be replaced with the user name. The user name is checked for 
+    existence before calling the password changing program.</para>
+
+    <para>Also note that many passwd programs insist in <emphasis>reasonable
+    </emphasis> passwords, such as a minimum length, or the inclusion 
+    of mixed case chars and digits. This can pose a problem as some clients 
+    (such as Windows for Workgroups) uppercase the password before sending 
+    it.</para>
+
+    <para><emphasis>Note</emphasis> that if the <parameter moreinfo="none">unix 
+    password sync</parameter> parameter is set to <constant>yes
+    </constant> then this program is called <emphasis>AS ROOT</emphasis> 
+    before the SMB password in the smbpasswd
+    file is changed. If this UNIX password change fails, then 
+    <command moreinfo="none">smbd</command> will fail to change the SMB password also 
+    (this is by design).</para>
+
+    <para>If the <parameter moreinfo="none">unix password sync</parameter> parameter 
+    is set this parameter <emphasis>MUST USE ABSOLUTE PATHS</emphasis> 
+    for <emphasis>ALL</emphasis> programs called, and must be examined 
+    for security implications. Note that by default <parameter moreinfo="none">unix 
+    password sync</parameter> is set to <constant>no</constant>.</para>
+	</description>
+
+	<related>unix password symc</related>
+
+	<value type="default"></value>
+<value type="example">/bin/passwd %u</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/passwordlevel.xml b/docs-xml/smbdotconf/security/passwordlevel.xml
new file mode 100644
index 00000000000..1da11e406bd
--- /dev/null
+++ b/docs-xml/smbdotconf/security/passwordlevel.xml
@@ -0,0 +1,48 @@
+<samba:parameter name="password level"
+                 context="G"
+				 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>Some client/server combinations have difficulty 
+    with mixed-case passwords.  One offending client is Windows for 
+    Workgroups, which for some reason forces passwords to upper 
+    case when using the LANMAN1 protocol, but leaves them alone when 
+    using COREPLUS!  Another problem child is the Windows 95/98
+    family of operating systems.  These clients upper case clear
+    text passwords even when NT LM 0.12 selected by the protocol
+    negotiation request/response.</para>
+
+    <para>This parameter defines the maximum number of characters 
+    that may be upper case in passwords.</para>
+
+    <para>For example, say the password given was &quot;FRED&quot;. If <parameter moreinfo="none">
+    password level</parameter> is set to 1, the following combinations 
+    would be tried if &quot;FRED&quot; failed:</para>
+
+    <para>&quot;Fred&quot;, &quot;fred&quot;, &quot;fRed&quot;, &quot;frEd&quot;,&quot;freD&quot;</para>
+
+    <para>If <parameter moreinfo="none">password level</parameter> was set to 2, 
+    the following combinations would also be tried: </para>
+
+    <para>&quot;FRed&quot;, &quot;FrEd&quot;, &quot;FreD&quot;, &quot;fREd&quot;, &quot;fReD&quot;, &quot;frED&quot;, ..</para>
+
+    <para>And so on.</para>
+
+    <para>The higher value this parameter is set to the more likely 
+    it is that a mixed case password will be matched against a single 
+    case password. However, you should be aware that use of this 
+    parameter reduces security and increases the time taken to 
+    process a new connection.</para>
+
+    <para>A value of zero will cause only two attempts to be 
+    made - the password as is and the password in all-lower case.</para>
+
+    <para>This parameter is used only when using plain-text passwords. It is
+    not at all used when encrypted passwords as in use (that is the default
+    since samba-3.0.0). Use this only when <smbconfoption name="encrypt passwords">No</smbconfoption>.</para>
+</description>
+
+<value type="default">0</value>
+<value type="example">4</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/passwordserver.xml b/docs-xml/smbdotconf/security/passwordserver.xml
new file mode 100644
index 00000000000..188cea88d1a
--- /dev/null
+++ b/docs-xml/smbdotconf/security/passwordserver.xml
@@ -0,0 +1,99 @@
+<samba:parameter name="password server"
+                 context="G"
+				 type="list"
+                 advanced="1" wizard="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>By specifying the name of another SMB server 
+    or Active Directory domain controller with this option, 
+    and using <command moreinfo="none">security = [ads|domain|server]</command> 
+    it is possible to get Samba to 
+    to do all its username/password validation using a specific remote server.</para>
+
+    <para>This option sets the name or IP address of the password server to use. 
+    New syntax has been added to support defining the port to use when connecting 
+    to the server the case of an ADS realm.  To define a port other than the
+    default LDAP port of 389, add the port number using a colon after the 
+    name or IP address (e.g. 192.168.1.100:389).  If you do not specify a port,
+    Samba will use the standard LDAP port of tcp/389.  Note that port numbers
+    have no effect on password servers for Windows NT 4.0 domains or netbios 
+    connections.</para>
+
+    <para>If parameter is a name, it is looked up using the 
+    parameter <smbconfoption name="name resolve order"/> and so may resolved
+    by any method and order described in that parameter.</para>
+
+    <para>The password server must be a machine capable of using 
+    the &quot;LM1.2X002&quot; or the &quot;NT LM 0.12&quot; protocol, and it must be in 
+    user level security mode.</para>
+
+    <note><para>Using a password server  means your UNIX box (running
+    Samba) is only as secure as your  password server. <emphasis>DO NOT
+    CHOOSE A PASSWORD SERVER THAT  YOU DON'T COMPLETELY TRUST</emphasis>.
+    </para></note>
+		
+    <para>Never point a Samba server at itself for password serving.
+    This will cause a loop and could lock up your Samba  server!</para>
+
+    <para>The name of the password server takes the standard 
+    substitutions, but probably the only useful one is <parameter moreinfo="none">%m
+    </parameter>, which means the Samba server will use the incoming 
+    client as the password server. If you use this then you better 
+    trust your clients, and you had better restrict them with hosts allow!</para>
+
+    <para>If the <parameter moreinfo="none">security</parameter> parameter is set to
+    <constant>domain</constant> or <constant>ads</constant>, then the list of machines in this 
+    option must be a list of Primary or Backup Domain controllers for the
+    Domain or the character '*', as the Samba server is effectively
+    in that domain, and will use cryptographically authenticated RPC calls
+    to authenticate the user logging on. The advantage of using <command moreinfo="none">
+    security = domain</command> is that if you list several hosts in the 
+    <parameter moreinfo="none">password server</parameter> option then <command moreinfo="none">smbd
+    </command> will try each in turn till it finds one that responds.  This
+    is useful in case your primary server goes down.</para>
+
+    <para>If the <parameter moreinfo="none">password server</parameter> option is set 
+    to the character '*', then Samba will attempt to auto-locate the 
+    Primary or Backup Domain controllers to authenticate against by 
+    doing a query for the name <constant>WORKGROUP&lt;1C&gt;</constant> 
+    and then contacting each server returned in the list of IP 
+    addresses from the name resolution source. </para>
+
+    <para>If the list of servers contains both names/IP's and the '*'
+    character, the list is treated as a list of preferred 
+    domain controllers, but an auto lookup of all remaining DC's
+    will be added to the list as well.  Samba will not attempt to optimize 
+    this list by locating the closest DC.</para>
+		
+    <para>If the <parameter moreinfo="none">security</parameter> parameter is 
+    set to <constant>server</constant>, then there are different
+    restrictions that <command moreinfo="none">security = domain</command> doesn't 
+    suffer from:</para>
+
+    <itemizedlist>
+	<listitem>
+	    <para>You may list several password servers in 
+	    the <parameter moreinfo="none">password server</parameter> parameter, however if an 
+	    <command moreinfo="none">smbd</command> makes a connection to a password server, 
+	    and then the password server fails, no more users will be able 
+	    to be authenticated from this <command moreinfo="none">smbd</command>.  This is a 
+	    restriction of the SMB/CIFS protocol when in <command moreinfo="none">security = server
+	    </command> mode and cannot be fixed in Samba.</para>
+	</listitem>
+	    
+	<listitem>
+	    <para>If you are using a Windows NT server as your 
+	    password server then you will have to ensure that your users 
+	    are able to login from the Samba server, as when in <command moreinfo="none">
+	    security = server</command>  mode the network logon will appear to 
+	    come from there rather than from the users workstation.</para>
+	</listitem>
+    </itemizedlist>
+</description>
+
+<related>security</related>
+<value type="default"></value>
+<value type="example">NT-PDC, NT-BDC1, NT-BDC2, *</value>
+<value type="example">windc.mydomain.com:389 192.168.1.101 *</value>
+<value type="example">*</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/preloadmodules.xml b/docs-xml/smbdotconf/security/preloadmodules.xml
new file mode 100644
index 00000000000..1d985a1995a
--- /dev/null
+++ b/docs-xml/smbdotconf/security/preloadmodules.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="preload modules"
+		type="list"
+		 context="G"
+		 basic="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This is a list of paths to modules that should
+	be loaded into smbd before a client connects. This improves
+	the speed of smbd when reacting to new connections somewhat. </para>
+</description>
+
+<value type="default"></value>
+<value type="example">/usr/lib/samba/passdb/mysql.so</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/printeradmin.xml b/docs-xml/smbdotconf/security/printeradmin.xml
new file mode 100644
index 00000000000..a0dd9929c05
--- /dev/null
+++ b/docs-xml/smbdotconf/security/printeradmin.xml
@@ -0,0 +1,27 @@
+<samba:parameter name="printer admin"
+                 context="S"
+				 type="list"
+		 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This lists users who can do anything to printers
+	via the remote administration interfaces offered
+	by MS-RPC (usually using a NT workstation).
+	This parameter can be set per-share or globally.
+	Note: The root user always has admin rights. Use
+	caution with use in the global stanza as this can
+	cause side effects.
+	</para>
+
+	<para>
+	This parameter has been marked deprecated in favor 
+	of using the SePrintOperatorPrivilege and individual
+	print security descriptors.  It will be removed in a future release.
+	</para>
+	
+</description>
+
+<value type="default"></value>
+<value type="example">admin, @staff</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/privatedir.xml b/docs-xml/smbdotconf/security/privatedir.xml
new file mode 100644
index 00000000000..d0cbcfad59d
--- /dev/null
+++ b/docs-xml/smbdotconf/security/privatedir.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="private dir"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameters defines the directory
+    smbd will use for storing such files as <filename moreinfo="none">smbpasswd</filename>
+    and <filename moreinfo="none">secrets.tdb</filename>.
+</para>
+</description>
+
+<value type="default">${prefix}/private</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/readlist.xml b/docs-xml/smbdotconf/security/readlist.xml
new file mode 100644
index 00000000000..df6b4f129bb
--- /dev/null
+++ b/docs-xml/smbdotconf/security/readlist.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="read list"
+                 context="S"
+				 type="list"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	This is a list of users that are given read-only access to a service. If the connecting user is in this list
+	then they will not be given write access, no matter what the <smbconfoption name="read only"/> option is set
+	to. The list can include group names using the syntax described in the <smbconfoption name="invalid users"/>
+	parameter.
+	</para>
+  
+    <para>This parameter will not work with the <smbconfoption name="security">share</smbconfoption> in 
+    Samba 3.0.  This is by design.</para>
+</description>
+
+<related>write list</related>
+<related>invalid users</related>
+
+<value type="default"></value>
+<value type="example">mary, @students</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/readonly.xml b/docs-xml/smbdotconf/security/readonly.xml
new file mode 100644
index 00000000000..6e1f6dd2b83
--- /dev/null
+++ b/docs-xml/smbdotconf/security/readonly.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="read only"
+                 context="S"
+				 type="boolean"
+                 basic="1" advanced="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>An inverted synonym is <smbconfoption name="writeable"/>.</para>
+
+    <para>If this parameter is <constant>yes</constant>, then users 
+    of a service may not create or modify files in the service's 
+    directory.</para>
+
+    <para>Note that a printable service (<command moreinfo="none">printable = yes</command>)
+    will <emphasis>ALWAYS</emphasis> allow writing to the directory 
+    (user privileges permitting), but only via spooling operations.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/renameuserscript.xml b/docs-xml/smbdotconf/security/renameuserscript.xml
new file mode 100644
index 00000000000..1ec1dcb6eb1
--- /dev/null
+++ b/docs-xml/smbdotconf/security/renameuserscript.xml
@@ -0,0 +1,33 @@
+<samba:parameter name="rename user script"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="boolean"
+				 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	This is the full pathname to a script that will be run as root by <citerefentry><refentrytitle>smbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> under special circumstances described below.
+	</para>
+
+	<para>
+	When a user with admin authority or SeAddUserPrivilege rights renames a user (e.g.: from the NT4 User Manager
+	for Domains), this script will be run to rename the POSIX user.  Two variables, <literal>%uold</literal> and
+	<literal>%unew</literal>, will be substituted with the old and new usernames, respectively.  The script should
+	return 0 upon successful completion, and nonzero otherwise.
+	</para>
+
+	<note><para>
+	The script has all responsibility to rename all the necessary data that is accessible in this posix method.
+	This can mean different requirements for different backends.  The tdbsam and smbpasswd backends will take care
+	of the contents of their respective files, so the script is responsible only for changing the POSIX username, and
+	other data that may required for your circumstances, such as home directory.  Please also consider whether or
+	not you need to rename the actual home directories themselves.  The ldapsam backend will not make any changes,
+	because of the potential issues with renaming the LDAP naming attribute.  In this case the script is
+	responsible for changing the attribute that samba uses (uid) for locating users, as well as any data that
+	needs to change for other applications using the same directory.
+	</para></note>
+
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/restrictanonymous.xml b/docs-xml/smbdotconf/security/restrictanonymous.xml
new file mode 100644
index 00000000000..1fbf983d54d
--- /dev/null
+++ b/docs-xml/smbdotconf/security/restrictanonymous.xml
@@ -0,0 +1,38 @@
+<samba:parameter name="restrict anonymous"
+	type="integer"
+                 context="G"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>The setting of this parameter determines whether user and
+    group list information is returned for an anonymous connection.
+    and mirrors the effects of the
+<programlisting>
+HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
+           Control\LSA\RestrictAnonymous
+</programlisting>
+	registry key in Windows 2000 and Windows NT.  When set to 0, user
+	and group list information is returned to anyone who asks.  When set
+    to 1, only an authenticated user can retrive user and
+    group list information.  For the value 2, supported by
+    Windows 2000/XP and Samba, no anonymous connections are allowed at
+    all.  This can break third party and Microsoft
+    applications which expect to be allowed to perform
+	operations anonymously.</para>
+
+	<para>
+    The security advantage of using restrict anonymous = 1 is dubious,
+    as user and group list information can be obtained using other
+	means.
+	</para>
+
+	<note>
+	<para>
+    The security advantage of using restrict anonymous = 2 is removed
+    by setting <smbconfoption name="guest ok">yes</smbconfoption> on any share.
+	</para>
+	</note>
+</description>
+
+<value type="default">0</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/rootdirectory.xml b/docs-xml/smbdotconf/security/rootdirectory.xml
new file mode 100644
index 00000000000..8736598001f
--- /dev/null
+++ b/docs-xml/smbdotconf/security/rootdirectory.xml
@@ -0,0 +1,35 @@
+<samba:parameter name="root directory"
+	context="G"
+	type="string"
+                 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>root</synonym>
+<synonym>root dir</synonym>
+<description>
+    <para>The server will <command moreinfo="none">chroot()</command> (i.e. 
+    Change its root directory) to this directory on startup. This is 
+    not strictly necessary for secure operation. Even without it the 
+    server will deny access to files not in one of the service entries. 
+    It may also check for, and deny access to, soft links to other 
+    parts of the filesystem, or attempts to use &quot;..&quot; in file names 
+    to access other directories (depending on the setting of the
+	<smbconfoption name="wide smbconfoptions"/> parameter).
+    </para>
+
+    <para>Adding a <parameter moreinfo="none">root directory</parameter> entry other 
+    than &quot;/&quot; adds an extra level of security, but at a price. It 
+    absolutely ensures that no access is given to files not in the 
+    sub-tree specified in the <parameter moreinfo="none">root directory</parameter> 
+    option, <emphasis>including</emphasis> some files needed for 
+    complete operation of the server. To maintain full operability 
+    of the server you will need to mirror some system files 
+    into the <parameter moreinfo="none">root directory</parameter> tree. In particular 
+    you will need to mirror <filename moreinfo="none">/etc/passwd</filename> (or a 
+    subset of it), and any binaries or configuration files needed for 
+    printing (if required). The set of files that must be mirrored is
+    operating system dependent.</para>
+</description>
+
+<value type="default">/</value>
+<value type="example">/homes/smb</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/security.xml b/docs-xml/smbdotconf/security/security.xml
new file mode 100644
index 00000000000..3ad5175712e
--- /dev/null
+++ b/docs-xml/smbdotconf/security/security.xml
@@ -0,0 +1,250 @@
+<samba:parameter name="security"
+                 context="G"
+				 type="enum"
+                 basic="1" advanced="1" wizard="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+		 <when_value value="security">
+			 <requires option="encrypted passwords">/(yes|true)/</requires>
+		 </when_value>
+<description>
+    <para>This option affects how clients respond to 
+    Samba and is one of the most important settings in the <filename moreinfo="none">
+    smb.conf</filename> file.</para>
+
+    <para>The option sets the &quot;security mode bit&quot; in replies to 
+    protocol negotiations with <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> to turn share level security on or off. Clients decide 
+    based on this bit whether (and how) to transfer user and password 
+    information to the server.</para>
+
+
+    <para>The default is <command moreinfo="none">security = user</command>, as this is
+    the most common setting needed when talking to Windows 98 and 
+    Windows NT.</para>
+
+    <para>The alternatives are <command moreinfo="none">security = share</command>,
+    <command moreinfo="none">security = server</command> or <command moreinfo="none">security = domain
+    </command>.</para>
+
+    <para>In versions of Samba prior to 2.0.0, the default was 
+    <command moreinfo="none">security = share</command> mainly because that was
+    the only option at one stage.</para>
+
+    <para>There is a bug in WfWg that has relevance to this 
+    setting. When in user or server level security a WfWg client 
+    will totally ignore the username and password you type in the &quot;connect 
+    drive&quot; dialog box. This makes it very difficult (if not impossible) 
+    to connect to a Samba service as anyone except the user that 
+    you are logged into WfWg as.</para>
+
+    <para>If your PCs use usernames that are the same as their 
+    usernames on the UNIX machine then you will want to use 
+    <command moreinfo="none">security = user</command>. If you mostly use usernames 
+    that don't exist on the UNIX box then use <command moreinfo="none">security = 
+    share</command>.</para>
+
+    <para>You should also use <command moreinfo="none">security = share</command> if you 
+    want to mainly setup shares without a password (guest shares). This 
+    is commonly used for a shared printer server. It is more difficult 
+    to setup guest shares with <command moreinfo="none">security = user</command>, see 
+    the <smbconfoption name="map to guest"/>parameter for details.</para>
+		
+    <para>It is possible to use <command moreinfo="none">smbd</command> in a <emphasis>
+    hybrid mode</emphasis> where it is offers both user and share 
+    level security under different <smbconfoption name="NetBIOS aliases"/>. </para>
+
+    <para>The different settings will now be explained.</para>
+
+
+    <para><anchor id="SECURITYEQUALSSHARE"/><emphasis>SECURITY = SHARE</emphasis></para> 
+		
+    <para>When clients connect to a share level security server they 
+    need not log onto the server with a valid username and password before 
+    attempting to connect to a shared resource (although modern clients 
+    such as Windows 95/98 and Windows NT will send a logon request with 
+    a username but no password when talking to a <command moreinfo="none">security = share
+    </command> server). Instead, the clients send authentication information 
+    (passwords) on a per-share basis, at the time they attempt to connect 
+    to that share.</para>
+
+    <para>Note that <command moreinfo="none">smbd</command> <emphasis>ALWAYS</emphasis> 
+    uses a valid UNIX user to act on behalf of the client, even in
+    <command moreinfo="none">security = share</command> level security.</para>
+
+    <para>As clients are not required to send a username to the server
+    in share level security, <command moreinfo="none">smbd</command> uses several
+    techniques to determine the correct UNIX user to use on behalf
+    of the client.</para>
+
+    <para>A list of possible UNIX usernames to match with the given
+    client password is constructed using the following methods :</para>
+
+    <itemizedlist>
+	<listitem>
+	    <para>If the <smbconfoption name="guest only"/> parameter is set, then all the other 
+	    stages are missed and only the <smbconfoption name="guest account"/> username is checked.
+	    </para>
+	</listitem>
+
+	<listitem>
+	    <para>Is a username is sent with the share connection 
+	    request, then this username (after mapping - see <smbconfoption name="username map"/>), 
+	    is added as a potential username.
+	    </para>
+	</listitem>
+
+	<listitem>
+	    <para>If the client did a previous <emphasis>logon
+	    </emphasis> request (the SessionSetup SMB call) then the 
+	    username sent in this SMB will be added as a potential username.
+	    </para>
+	</listitem>
+
+	<listitem>
+	    <para>The name of the service the client requested is 
+	    added as a potential username.
+	    </para>
+	</listitem>
+
+	<listitem>
+	    <para>The NetBIOS name of the client is added to 
+	    the list as a potential username.
+	    </para>
+	</listitem>
+
+	<listitem>
+	    <para>Any users on the <smbconfoption name="user"/> list are added as potential usernames.
+	    </para>
+	</listitem>
+    </itemizedlist>
+
+    <para>If the <parameter moreinfo="none">guest only</parameter> parameter is 
+    not set, then this list is then tried with the supplied password. 
+    The first user for whom the password matches will be used as the 
+    UNIX user.</para>
+
+    <para>If the <parameter moreinfo="none">guest only</parameter> parameter is 
+    set, or no username can be determined then if the share is marked 
+    as available to the <parameter moreinfo="none">guest account</parameter>, then this 
+    guest user will be used, otherwise access is denied.</para>
+
+    <para>Note that it can be <emphasis>very</emphasis> confusing 
+    in share-level security as to which UNIX username will eventually
+    be used in granting access.</para>
+
+    <para>See also the section <link linkend="VALIDATIONSECT">
+    NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para>
+
+    <para><anchor id="SECURITYEQUALSUSER"/><emphasis>SECURITY = USER</emphasis></para>
+
+    <para>This is the default security setting in Samba 3.0. 
+    With user-level security a client must first &quot;log-on&quot; with a 
+    valid username and password (which can be mapped using the <smbconfoption name="username map"/> 
+    parameter). Encrypted passwords (see the <smbconfoption name="encrypted passwords"/> parameter) can also
+    be used in this security mode. Parameters such as <smbconfoption name="user"/> and <smbconfoption
+	name="guest only"/> if set	are then applied and 
+    may change the UNIX user to use on this connection, but only after 
+    the user has been successfully authenticated.</para>
+
+    <para><emphasis>Note</emphasis> that the name of the resource being 
+    requested is <emphasis>not</emphasis> sent to the server until after 
+    the server has successfully authenticated the client. This is why 
+    guest shares don't work in user level security without allowing 
+    the server to automatically map unknown users into the <smbconfoption name="guest account"/>. 
+    See the <smbconfoption name="map to guest"/> parameter for details on doing this.</para>
+
+    <para>See also the section <link linkend="VALIDATIONSECT">NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para>
+
+    <para><anchor id="SECURITYEQUALSDOMAIN"/><emphasis>SECURITY = DOMAIN</emphasis></para>
+
+    <para>This mode will only work correctly if <citerefentry><refentrytitle>net</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> has been used to add this
+    machine into a Windows NT Domain. It expects the <smbconfoption name="encrypted passwords"/>
+	parameter to be set to <constant>yes</constant>. In this 
+    mode Samba will try to validate the username/password by passing
+    it to a Windows NT Primary or Backup Domain Controller, in exactly 
+    the same way that a Windows NT Server would do.</para>
+
+    <para><emphasis>Note</emphasis> that a valid UNIX user must still 
+    exist as well as the account on the Domain Controller to allow 
+    Samba to have a valid UNIX account to map file access to.</para>
+
+    <para><emphasis>Note</emphasis> that from the client's point 
+    of view <command moreinfo="none">security = domain</command> is the same 
+    as <command moreinfo="none">security = user</command>. It only 
+    affects how the server deals with the authentication, 
+    it does not in any way affect what the client sees.</para>
+
+    <para><emphasis>Note</emphasis> that the name of the resource being 
+    requested is <emphasis>not</emphasis> sent to the server until after 
+    the server has successfully authenticated the client. This is why 
+    guest shares don't work in user level security without allowing 
+    the server to automatically map unknown users into the <smbconfoption name="guest account"/>. 
+    See the <smbconfoption name="map to guest"/> parameter for details on doing this.</para>
+
+    <para>See also the section <link linkend="VALIDATIONSECT">
+    NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para>
+
+    <para>See also the <smbconfoption name="password server"/> parameter and
+	 the <smbconfoption name="encrypted passwords"/> parameter.</para>
+
+    <para><anchor id="SECURITYEQUALSSERVER"/><emphasis>SECURITY = SERVER</emphasis></para>
+
+    <para>
+	In this mode Samba will try to validate the username/password by passing it to another SMB server, such as an
+	NT box. If this fails it will revert to <command moreinfo="none">security = user</command>. It expects the
+	<smbconfoption name="encrypted passwords"/> parameter to be set to <constant>yes</constant>, unless the remote
+	server does not support them.  However note that if encrypted passwords have been negotiated then Samba cannot
+	revert back to checking the UNIX password file, it must have a valid <filename
+	moreinfo="none">smbpasswd</filename> file to check users against. See the chapter about the User Database in
+	the Samba HOWTO Collection for details on how to set this up.
+</para>
+
+	<note><para>This mode of operation has
+    significant pitfalls since it is more vulnerable to
+    man-in-the-middle attacks and server impersonation.  In particular,
+    this mode of operation can cause significant resource consuption on
+    the PDC, as it must maintain an active connection for the duration
+    of the user's session.  Furthermore, if this connection is lost,
+    there is no way to reestablish it, and futher authentications to the
+    Samba server may fail (from a single client, till it disconnects).
+	</para></note>
+
+	<note><para>From the client's point of 
+    view <command moreinfo="none">security = server</command> is the
+    same as <command moreinfo="none">security = user</command>.  It
+    only affects how the server deals  with the authentication, it does
+	not in any way affect what the  client sees.</para></note>
+
+    <para><emphasis>Note</emphasis> that the name of the resource being 
+    requested is <emphasis>not</emphasis> sent to the server until after 
+    the server has successfully authenticated the client. This is why 
+    guest shares don't work in user level security without allowing 
+    the server to automatically map unknown users into the <smbconfoption name="guest account"/>. 
+    See the <smbconfoption name="map to guest"/> parameter for details on doing this.</para>
+
+    <para>See also the section <link linkend="VALIDATIONSECT">
+    NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para>
+
+    <para>See also the <smbconfoption name="password server"/> parameter and the 
+	<smbconfoption name="encrypted passwords"/> parameter.</para>
+
+	<para><anchor id="SECURITYEQUALSADS"/><emphasis>SECURITY = ADS</emphasis></para>
+	
+	<para>In this mode, Samba will act as a domain member in an ADS realm. To operate 
+		in this mode, the machine running Samba will need to have Kerberos installed 
+		and configured and Samba will need to be joined to the ADS realm using the 
+		net utility. </para>
+	
+	<para>Note that this mode does NOT make Samba operate as a Active Directory Domain 
+		Controller. </para>
+	
+	<para>Read the chapter about Domain Membership in the HOWTO for details.</para>
+</description>
+
+<related>realm</related>
+<related>encrypt passwords</related>
+
+<value type="default">USER</value>
+<value type="example">DOMAIN</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/securitymask.xml b/docs-xml/smbdotconf/security/securitymask.xml
new file mode 100644
index 00000000000..23bc2808db4
--- /dev/null
+++ b/docs-xml/smbdotconf/security/securitymask.xml
@@ -0,0 +1,39 @@
+<samba:parameter name="security mask"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	This parameter controls what UNIX permission bits will be set when a Windows NT client is manipulating the
+	UNIX permission on a file using the native NT security dialog box.
+	</para>
+
+    <para>
+	This parameter is applied as a mask (AND'ed with) to the incoming permission bits, thus resetting
+	any bits not in this mask. Make sure not to mix up this parameter with <smbconfoption name="force
+	security mode"/>, which works in a manner similar to this one but uses a logical OR instead of an AND. 
+	</para>
+
+    <para>
+	Essentially, all bits set to zero in this mask will result in setting to zero the corresponding bits on the
+	file permissions regardless of the previous status of this bits on the file.
+    </para>
+
+    <para>
+	If not set explicitly this parameter is 0777, allowing a user to set all the user/group/world permissions on a file.
+    </para>
+
+    <para><emphasis>
+	Note</emphasis> that users who can access the Samba server through other means can easily bypass this 
+    restriction, so it is primarily useful for standalone &quot;appliance&quot; systems.  Administrators of
+	most normal systems will probably want to leave it set to <constant>0777</constant>.
+	</para>
+</description>
+
+<related>force directory security mode</related>
+<related>directory security mask</related>
+<related>force security mode</related>
+
+<value type="default">0777</value>
+<value type="example">0770</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/serverschannel.xml b/docs-xml/smbdotconf/security/serverschannel.xml
new file mode 100644
index 00000000000..6317448fb62
--- /dev/null
+++ b/docs-xml/smbdotconf/security/serverschannel.xml
@@ -0,0 +1,23 @@
+<samba:parameter name="server schannel"
+                 context="G"
+				 type="boolean-auto"
+                 basic="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	This controls whether the server offers or even demands the use of the netlogon schannel.
+	<smbconfoption name="server schannel">no</smbconfoption> does not offer the schannel, <smbconfoption
+	name="server schannel">auto</smbconfoption> offers the schannel but does not enforce it, and <smbconfoption
+	name="server schannel">yes</smbconfoption> denies access if the client is not able to speak netlogon schannel.
+	This is only the case for Windows NT4 before SP4.
+	</para>
+
+    <para>
+	Please note that with this set to <literal>no</literal> you will have to apply the WindowsXP
+	<filename>WinXP_SignOrSeal.reg</filename> registry patch found in the docs/registry subdirectory of the Samba distribution tarball.
+	</para>
+</description>
+
+<value type="default">auto</value>
+<value type="example">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/serversigning.xml b/docs-xml/smbdotconf/security/serversigning.xml
new file mode 100644
index 00000000000..f2f56295861
--- /dev/null
+++ b/docs-xml/smbdotconf/security/serversigning.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="server signing"
+                 context="G"
+				 type="enum"
+                 basic="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+    <para>This controls whether the server offers or requires
+    the client it talks to to use SMB signing. Possible values 
+    are <emphasis>auto</emphasis>, <emphasis>mandatory</emphasis> 
+    and <emphasis>disabled</emphasis>. 
+    </para>
+
+    <para>When set to auto, SMB signing is offered, but not enforced. 
+    When set to mandatory, SMB signing is required and if set 
+	to disabled, SMB signing is not offered either.</para>
+</description>
+
+<value type="default">Disabled</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/smbencrypt.xml b/docs-xml/smbdotconf/security/smbencrypt.xml
new file mode 100644
index 00000000000..eb91ce51fa3
--- /dev/null
+++ b/docs-xml/smbdotconf/security/smbencrypt.xml
@@ -0,0 +1,45 @@
+<samba:parameter name="smb encrypt"
+                 context="S"
+				 type="enum"
+                 basic="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+    <para>This is a new feature introduced with Samba 3.2 and above. It is an
+    extension to the SMB/CIFS protocol negotiated as part of the UNIX extensions.
+    SMB encryption uses the GSSAPI (SSPI on Windows) ability to encrypt
+    and sign every request/response in a SMB protocol stream. When
+    enabled it provides a secure method of SMB/CIFS communication,
+    similar to an ssh protected session, but using SMB/CIFS authentication
+    to negotiate encryption and signing keys. Currently this is only
+    supported by Samba 3.2 smbclient, and hopefully soon Linux CIFSFS
+    and MacOS/X clients. Windows clients do not support this feature.
+    </para>
+
+    <para>This controls whether the server offers or requires
+    the client it talks to to use SMB encryption. Possible values 
+    are <emphasis>auto</emphasis>, <emphasis>mandatory</emphasis> 
+    and <emphasis>disabled</emphasis>. This may be set on a per-share
+    basis, but clients may chose to encrypt the entire session, not
+    just traffic to a specific share. If this is set to mandatory
+    then all traffic to a share <emphasis>must</emphasis> must
+    be encrypted once the connection has been made to the share.
+    The server would return "access denied" to all non-encrypted
+    requests on such a share. Selecting encrypted traffic reduces
+    throughput as smaller packet sizes must be used (no huge UNIX
+    style read/writes allowed) as well as the overhead of encrypting
+    and signing all the data.
+    </para>
+
+    <para>If SMB encryption is selected, Windows style SMB signing (see
+    the <smbconfoption name="server signing"/> option) is no longer necessary,
+    as the GSSAPI flags use select both signing and sealing of the data.
+    </para>
+
+    <para>When set to auto, SMB encryption is offered, but not enforced. 
+    When set to mandatory, SMB encryption is required and if set 
+    to disabled, SMB encryption can not be negotiated.</para>
+</description>
+
+<value type="default">auto</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/smbpasswdfile.xml b/docs-xml/smbdotconf/security/smbpasswdfile.xml
new file mode 100644
index 00000000000..209fa74422b
--- /dev/null
+++ b/docs-xml/smbdotconf/security/smbpasswdfile.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="smb passwd file"
+	type="string"
+                 context="G"
+                 advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option sets the path to the encrypted smbpasswd file. By
+    default the path to the smbpasswd file  is compiled into Samba.</para>
+
+    <para>
+    An example of use is:
+<programlisting>
+smb passwd file = /etc/samba/smbpasswd
+</programlisting>
+    </para>
+</description>
+
+<value type="default">${prefix}/private/smbpasswd</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/unixpasswordsync.xml b/docs-xml/smbdotconf/security/unixpasswordsync.xml
new file mode 100644
index 00000000000..7f30c47d90f
--- /dev/null
+++ b/docs-xml/smbdotconf/security/unixpasswordsync.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="unix password sync"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean parameter controls whether Samba 
+    attempts to synchronize the UNIX password with the SMB password 
+    when the encrypted SMB password in the smbpasswd file is changed. 
+    If this is set to <constant>yes</constant> the program specified in the <parameter moreinfo="none">passwd
+    program</parameter>parameter is called <emphasis>AS ROOT</emphasis> - 
+    to allow the new UNIX password to be set without access to the 
+    old UNIX password (as the SMB password change code has no 
+	access to the old password cleartext, only the new).</para>
+</description>
+
+<related>passwd program</related>
+<related>passwd chat</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/updateencrypted.xml b/docs-xml/smbdotconf/security/updateencrypted.xml
new file mode 100644
index 00000000000..da493665cf2
--- /dev/null
+++ b/docs-xml/smbdotconf/security/updateencrypted.xml
@@ -0,0 +1,34 @@
+<samba:parameter name="update encrypted"
+                 context="G"
+				 type="boolean"
+                 basic="1" advanced="1" developer="1"
+		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+    <para>
+	This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed)
+	password in the smbpasswd file to be updated automatically as they log on. This option allows a site to
+	migrate from plaintext password authentication (users authenticate with plaintext password over the
+	wire, and are checked against a UNIX account atabase) to encrypted password authentication (the SMB
+	challenge/response authentication mechanism) without forcing all users to re-enter their passwords via
+	smbpasswd at the time the change is made. This is a convenience option to allow the change over to encrypted
+	passwords to be made over a longer period.  Once all users have encrypted representations of their passwords
+	in the smbpasswd file this parameter should be set to <constant>no</constant>.
+	</para>
+
+    <para>
+	In order for this parameter to be operative the <smbconfoption name="encrypt passwords"/> parameter must 
+    be set to <constant>no</constant>. The default value of <smbconfoption name="encrypt
+	passwords">Yes</smbconfoption>. Note: This must be set to <constant>no</constant> for this <smbconfoption
+	name="update encrypted"/> to work.
+	</para>
+
+    <para>
+	Note that even when this parameter is set a user authenticating to <command moreinfo="none">smbd</command>
+	must still enter a valid password in order to connect correctly, and to update their hashed (smbpasswd)
+	passwords.
+	</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/usekerberoskeytab.xml b/docs-xml/smbdotconf/security/usekerberoskeytab.xml
new file mode 100644
index 00000000000..ad6cc882785
--- /dev/null
+++ b/docs-xml/smbdotconf/security/usekerberoskeytab.xml
@@ -0,0 +1,23 @@
+<samba:parameter name="use kerberos keytab"
+                 context="G"
+		 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	Specifies whether Samba should attempt to maintain service principals in the systems
+	keytab file for <constant>host/FQDN</constant> and <constant>cifs/FQDN</constant>.
+	</para>
+
+	<para>
+	When you are using the heimdal Kerberos libraries, you must also specify the following in
+	<filename>/etc/krb5.conf</filename>:
+<programlisting>
+[libdefaults]
+default_keytab_name = FILE:/etc/krb5.keytab
+</programlisting>
+	</para>
+
+</description>
+
+<value type="default">False</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/username.xml b/docs-xml/smbdotconf/security/username.xml
new file mode 100644
index 00000000000..3a45d4d72fc
--- /dev/null
+++ b/docs-xml/smbdotconf/security/username.xml
@@ -0,0 +1,65 @@
+<samba:parameter name="username"
+	context="S"
+	type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>user</synonym>
+<synonym>users</synonym>
+<description>
+    <para>Multiple users may be specified in a comma-delimited 
+    list, in which case the supplied password will be tested against 
+    each username in turn (left to right).</para>
+
+    <para>The <parameter moreinfo="none">username</parameter> line is needed only when 
+    the PC is unable to supply its own username. This is the case 
+    for the COREPLUS protocol or where your users have different WfWg 
+    usernames to UNIX usernames. In both these cases you may also be 
+    better using the \\server\share%user syntax instead.</para>
+
+    <para>The <parameter moreinfo="none">username</parameter> line is not a great 
+    solution in many cases as it means Samba will try to validate 
+    the supplied password against each of the usernames in the 
+    <parameter moreinfo="none">username</parameter> line in turn. This is slow and 
+    a bad idea for lots of users in case of duplicate passwords. 
+    You may get timeouts or security breaches using this parameter 
+    unwisely.</para>
+
+    <para>Samba relies on the underlying UNIX security. This 
+    parameter does not restrict who can login, it just offers hints 
+    to the Samba server as to what usernames might correspond to the 
+    supplied password. Users can login as whoever they please and 
+    they will be able to do no more damage than if they started a 
+    telnet session. The daemon runs as the user that they log in as, 
+    so they cannot do anything that user cannot do.</para>
+
+    <para>To restrict a service to a particular set of users you 
+    can use the <smbconfoption name="valid users"/> parameter.</para>
+
+    <para>If any of the usernames begin with a '@' then the name 
+    will be looked up first in the NIS netgroups list (if Samba 
+    is compiled with netgroup support), followed by a lookup in 
+    the UNIX groups database and will expand to a list of all users 
+    in the group of that name.</para>
+		
+    <para>If any of the usernames begin with a '+' then the name 
+    will be looked up only in the UNIX groups database and will 
+    expand to a list of all users in the group of that name.</para>
+
+    <para>If any of the usernames begin with a '&amp;' then the name 
+    will be looked up only in the NIS netgroups database (if Samba 
+    is compiled with netgroup support) and will expand to a list 
+    of all users in the netgroup group of that name.</para>
+
+    <para>Note that searching though a groups database can take 
+    quite some time, and some clients may time out during the 
+    search.</para>
+
+    <para>See the section <link linkend="VALIDATIONSECT">NOTE ABOUT
+	USERNAME/PASSWORD VALIDATION</link> for more information on how 
+	this parameter determines access to the services.</para>
+</description>
+
+<value type="default"><comment>The guest account if a guest service, 
+		else &lt;empty string&gt;.</comment></value>
+
+<value type="example">fred, mary, jack, jane, @users, @pcgroup</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/usernamelevel.xml b/docs-xml/smbdotconf/security/usernamelevel.xml
new file mode 100644
index 00000000000..adb00134d7b
--- /dev/null
+++ b/docs-xml/smbdotconf/security/usernamelevel.xml
@@ -0,0 +1,27 @@
+<samba:parameter name="username level"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option helps Samba to try and 'guess' at 
+    the real UNIX username, as many DOS clients send an all-uppercase 
+    username. By default Samba tries all lowercase, followed by the 
+    username with the first letter capitalized, and fails if the 
+    username is not found on the UNIX machine.</para>
+
+    <para>If this parameter is set to non-zero the behavior changes. 
+    This parameter is a number that specifies the number of uppercase
+    combinations to try while trying to determine the UNIX user name. The
+    higher the number the more combinations will be tried, but the slower
+    the discovery of usernames will be. Use this parameter when you have
+    strange usernames on your UNIX machine, such as <constant>AstrangeUser
+    </constant>.</para>
+
+    <para>This parameter is needed only on UNIX systems that have case
+    sensitive usernames.</para>
+</description>
+
+<value type="default">0</value>
+<value type="example">5</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/usernamemap.xml b/docs-xml/smbdotconf/security/usernamemap.xml
new file mode 100644
index 00000000000..54179690be5
--- /dev/null
+++ b/docs-xml/smbdotconf/security/usernamemap.xml
@@ -0,0 +1,130 @@
+<samba:parameter name="username map"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+	This option allows you to specify a file containing a mapping of usernames from the clients to the server.
+	This can be used for several purposes. The most common is to map usernames that users use on DOS or Windows
+	machines to those that the UNIX box uses. The other is to map multiple users to a single username so that they
+	can more easily share files.
+	</para>
+
+    <para>
+	Please note that for user or share mode security, the username map is applied prior to validating the user
+	credentials.  Domain member servers (domain or ads) apply the username map after the user has been
+	successfully authenticated by the domain controller and require fully qualified enties in the map table (e.g.
+	biddle = <literal>DOMAIN\foo</literal>).
+	</para>
+    
+    <para>
+	The map file is parsed line by line. Each line should contain a single UNIX username on the left then a '='
+	followed by a list of usernames on the right. The list of usernames on the right may contain names of the form
+	@group in which case they will match any UNIX username in that group. The special client name '*' is a
+	wildcard and matches any name. Each line of the map file may be up to 1023 characters long.
+	</para>
+
+    <para>
+	The file is processed on each line by taking the supplied username and comparing it with each username on the
+	right hand side of the '=' signs. If the supplied name matches any of the names on the right hand side then it
+	is replaced with the name on the left. Processing then continues with the next line.
+	</para>
+
+    <para>
+	If any line begins with a '#' or a ';' then it is ignored.
+	</para>
+
+    <para>
+	If any line begins with an '!' then the processing will stop after that line if a mapping was done by the
+	line.  Otherwise mapping continues with every line being processed.  Using '!' is most useful when you have a
+	wildcard mapping line later in the file.
+	</para>
+
+    <para>
+	For example to map from the name <constant>admin</constant> or <constant>administrator</constant> to the UNIX
+	name <constant> root</constant> you would use:
+<programlisting>
+<command moreinfo="none">root = admin administrator</command>
+</programlisting>
+	Or to map anyone in the UNIX group <constant>system</constant> to the UNIX name <constant>sys</constant> you would use:
+<programlisting>
+<command moreinfo="none">sys = @system</command>
+</programlisting>
+	</para>
+
+    <para>
+	You can have as many mappings as you like in a username map file.
+	</para>
+
+
+    <para>
+	If your system supports the NIS NETGROUP option then the netgroup database is checked before the <filename
+	moreinfo="none">/etc/group </filename> database for matching groups.
+	</para>
+
+    <para>
+	You can map Windows usernames that have spaces in them by using double quotes around the name. For example:
+<programlisting>
+<command moreinfo="none">tridge = &quot;Andrew Tridgell&quot;</command>
+</programlisting>
+    would map the windows username &quot;Andrew Tridgell&quot; to the unix username &quot;tridge&quot;.
+	</para>
+
+    <para>
+	The following example would map mary and fred to the unix user sys, and map the rest to guest. Note the use of the
+    '!' to tell Samba to stop processing if it gets a match on that line:
+<programlisting format="linespecific">
+!sys = mary fred
+guest = *
+</programlisting>
+    </para>
+
+    <para>
+	Note that the remapping is applied to all occurrences of usernames.  Thus if you connect to \\server\fred and
+	<constant>fred</constant> is remapped to <constant>mary</constant> then you will actually be connecting to
+	\\server\mary and will need to supply a password suitable for <constant>mary</constant> not
+	<constant>fred</constant>. The only exception to this is the username passed to the <smbconfoption
+	name="password server"/> (if you have one). The password server will receive whatever username the client
+	supplies without  modification.
+    </para>
+
+    <para>
+	Also note that no reverse mapping is done. The main effect this has is with printing. Users who have been
+	mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don't own the print
+	job.
+	</para>
+
+   <para>
+	Samba versions prior to 3.0.8 would only support reading the fully qualified username 
+	(e.g.: <literal>DOMAIN\user</literal>) from
+	the username map when performing a kerberos login from a client.  However, when looking up a map entry for a
+	user authenticated by NTLM[SSP], only the login name would be used for matches.  This resulted in inconsistent
+	behavior sometimes even on the same server.
+   </para>
+
+   <para>
+   The following functionality is obeyed in version 3.0.8 and later:
+   </para>
+
+   <para>
+    When performing local authentication, the username map is applied to the login name before attempting to authenticate
+    the connection.
+    </para>
+
+    <para>
+    When relying upon a external domain controller for validating authentication requests, smbd will apply the username map
+    to the fully qualified username (i.e. <literal>DOMAIN\user</literal>) only after the user has been successfully authenticated.
+    </para>
+
+    <para>
+    An example of use is:
+<programlisting>
+username map = /usr/local/samba/lib/users.map
+</programlisting>
+    </para>
+
+</description>
+
+<value type="default"><comment>no username map</comment></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/usernamemapscript.xml b/docs-xml/smbdotconf/security/usernamemapscript.xml
new file mode 100644
index 00000000000..6df134c2575
--- /dev/null
+++ b/docs-xml/smbdotconf/security/usernamemapscript.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="username map script"
+                 context="G"
+		 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This script is a mutually exclusive alternative to the 
+	<smbconfoption name="username map"/> parameter.  This parameter 
+	specifies and external program or script that must accept a single 
+	command line option (the username transmitted in the authentication
+	request) and return a line line on standard output (the name to which 
+	the account should mapped).  In this way, it is possible to store
+	username map tables in an LDAP or NIS directory services.
+	</para>
+</description>
+
+<value type="default"/>
+<value type="example">/etc/samba/scripts/mapusers.sh</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/validusers.xml b/docs-xml/smbdotconf/security/validusers.xml
new file mode 100644
index 00000000000..313739d7c15
--- /dev/null
+++ b/docs-xml/smbdotconf/security/validusers.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="valid users"
+                 context="S"
+				 type="list"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This is a list of users that should be allowed to login to this service. Names starting with 
+    '@', '+' and  '&amp;' are interpreted using the same rules as described in the 
+    <parameter moreinfo="none">invalid users</parameter> parameter.
+    </para>
+
+    <para>
+    If this is empty (the default) then any user can login. If a username is in both this list 
+    and the <parameter moreinfo="none">invalid users</parameter> list then access is denied 
+    for that user.
+    </para>
+
+    <para>
+    The current servicename is substituted for <parameter moreinfo="none">%S</parameter>. 
+    This is useful in the [homes] section.
+    </para>
+</description>
+
+<related>invalid users</related>
+
+<value type="default"><comment>No valid users list (anyone can login) </comment></value>
+<value type="example">greg, @pcusers</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/writeable.xml b/docs-xml/smbdotconf/security/writeable.xml
new file mode 100644
index 00000000000..f811c47e5c2
--- /dev/null
+++ b/docs-xml/smbdotconf/security/writeable.xml
@@ -0,0 +1,9 @@
+<samba:parameter name="writeable"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>writable</synonym>
+<description>
+    <para>Inverted synonym for <smbconfoption name="read only"/>.</para>
+</description>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/security/writelist.xml b/docs-xml/smbdotconf/security/writelist.xml
new file mode 100644
index 00000000000..60db3f19f0f
--- /dev/null
+++ b/docs-xml/smbdotconf/security/writelist.xml
@@ -0,0 +1,29 @@
+<samba:parameter name="write list"
+                 context="S"
+				 type="list"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>
+    This is a list of users that are given read-write access to a service. If the 
+    connecting user is in this list then they will be given write access, no matter 
+    what the <smbconfoption name="read only"/> option is set to. The list can 
+    include group names using the @group syntax.
+    </para>
+
+    <para>
+    Note that if a user is in both the read list and the write list then they will be 
+    given write access.
+    </para>
+
+    <para>
+    By design, this parameter will not work with the 
+    <smbconfoption name="security">share</smbconfoption> in Samba 3.0.
+    </para>
+
+</description>
+
+<related>read list</related>
+
+<value type="default"></value>
+<value type="example">admin, root, @staff</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/aioreadsize.xml b/docs-xml/smbdotconf/tuning/aioreadsize.xml
new file mode 100644
index 00000000000..082cf5ddfde
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/aioreadsize.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="aio read size"
+                 context="S"
+		 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+  <para>If Samba has been built with asynchronous I/O support and this
+    integer parameter is set to non-zero value,
+    Samba will read from file asynchronously when size of request is bigger
+    than this value. Note that it happens only for non-chained and non-chaining
+    reads and when not using write cache.</para>
+
+  <para>Current implementation of asynchronous I/O in Samba 3.0 does support
+    only up to 10 outstanding asynchronous requests, read and write combined.</para>
+
+  <related>write cache size</related>
+  <related>aio write size</related>
+</description>
+
+<value type="default">0</value>
+<value type="example">16384<comment> Use asynchronous I/O for reads bigger than 16KB
+    request size</comment></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/aiowritesize.xml b/docs-xml/smbdotconf/tuning/aiowritesize.xml
new file mode 100644
index 00000000000..e33a60e98e0
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/aiowritesize.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="aio write size"
+                 context="S"
+		 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+  <para>If Samba has been built with asynchronous I/O support and this
+    integer parameter is set to non-zero value,
+    Samba will write to file asynchronously when size of request is bigger
+    than this value. Note that it happens only for non-chained and non-chaining
+    reads and when not using write cache.</para>
+
+  <para>Current implementation of asynchronous I/O in Samba 3.0 does support
+    only up to 10 outstanding asynchronous requests, read and write combined.</para>
+  
+  <related>write cache size</related>
+  <related>aio read size</related>
+</description>
+
+<value type="default">0</value>
+<value type="example">16384<comment> Use asynchronous I/O for writes bigger than 16KB
+    request size</comment></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/allocationroundupsize.xml b/docs-xml/smbdotconf/tuning/allocationroundupsize.xml
new file mode 100644
index 00000000000..5fc013b5a0b
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/allocationroundupsize.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="allocation roundup size"
+                 context="S"
+		 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter allows an administrator to tune the 
+    allocation size reported to Windows clients.  The default 
+    size of 1Mb generally results in improved Windows client
+    performance.   However, rounding the allocation size may cause
+    difficulties for some applications, e.g. MS Visual Studio.
+    If the MS Visual Studio compiler starts to crash with an
+    internal error, set this parameter to zero for this share.
+    </para>
+
+    <para>The integer parameter specifies the roundup size in bytes.</para>
+</description>
+
+<value type="default">1048576</value>
+<value type="example">0<comment>(to disable roundups)</comment></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/blocksize.xml b/docs-xml/smbdotconf/tuning/blocksize.xml
new file mode 100644
index 00000000000..1a0cc545a37
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/blocksize.xml
@@ -0,0 +1,27 @@
+<samba:parameter name="block size"
+				type="integer"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter controls the behavior of <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> when reporting disk free 
+    sizes. By default, this reports a disk block size of 1024 bytes.
+    </para>        
+		
+    <para>Changing this parameter may have some effect on the
+    efficiency of client writes, this is not yet confirmed. This
+    parameter was added to allow advanced administrators to change
+    it (usually to a higher value) and test the effect it has on
+    client write performance without re-compiling the code. As this
+    is an experimental option it may be removed in a future release.
+    </para>
+
+    <para>Changing this option does not change the disk free reporting
+    size, just the block size unit reported to the client.
+    </para>
+</description>
+
+<value type="default">1024</value>
+<value type="example">4096</value>
+
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/deadtime.xml b/docs-xml/smbdotconf/tuning/deadtime.xml
new file mode 100644
index 00000000000..51b76bd85a5
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/deadtime.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="deadtime"
+                 context="G"
+                 developer="1"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>The value of the parameter (a decimal integer) 
+    represents the number of minutes of inactivity before a connection 
+    is considered dead, and it is disconnected. The deadtime only takes 
+    effect if the number of open files is zero.</para>
+		
+    <para>This is useful to stop a server's resources being 
+    exhausted by a large number of inactive connections.</para>
+
+    <para>Most clients have an auto-reconnect feature when a 
+    connection is broken so in most cases this parameter should be 
+    transparent to users.</para>
+
+    <para>Using this parameter with a timeout of a few minutes 
+    is recommended for most systems.</para>
+
+    <para>A deadtime of zero indicates that no auto-disconnection 
+		should be performed.</para>
+</description>
+
+<value type="default">0</value>
+<value type="example">15</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/getwdcache.xml b/docs-xml/smbdotconf/tuning/getwdcache.xml
new file mode 100644
index 00000000000..74d30c28e54
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/getwdcache.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="getwd cache"
+                 context="G"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This is a tuning option. When this is enabled a 
+    caching algorithm will be used to reduce the time taken for getwd() 
+    calls. This can have a significant impact on performance, especially 
+    when the <smbconfoption name="wide smbconfoptions"/> parameter is set to <constant>no</constant>.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/hostnamelookups.xml b/docs-xml/smbdotconf/tuning/hostnamelookups.xml
new file mode 100644
index 00000000000..68f4ec4f408
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/hostnamelookups.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="hostname lookups"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>Specifies whether samba should use (expensive)
+    hostname lookups or use the ip addresses instead. An example place
+    where hostname lookups are currently used is when checking 
+    the <command moreinfo="none">hosts deny</command> and <command moreinfo="none">hosts allow</command>.
+    </para>
+</description>
+
+<value type="default">no</value>
+<value type="example">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/keepalive.xml b/docs-xml/smbdotconf/tuning/keepalive.xml
new file mode 100644
index 00000000000..0586365512f
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/keepalive.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="keepalive"
+                 context="G"
+				 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>The value of the parameter (an integer) represents 
+    the number of seconds between <parameter moreinfo="none">keepalive</parameter> 
+    packets. If this parameter is zero, no keepalive packets will be 
+    sent. Keepalive packets, if sent, allow the server to tell whether 
+    a client is still present and responding.</para>
+
+    <para>Keepalives should, in general, not be needed if the socket 
+    has the SO_KEEPALIVE attribute set on it by default. (see <smbconfoption name="socket options"/>). 
+Basically you should only use this option if you strike difficulties.</para>
+</description>
+
+<value type="default">300</value>
+<value type="example">600</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/maxconnections.xml b/docs-xml/smbdotconf/tuning/maxconnections.xml
new file mode 100644
index 00000000000..1e3043b2f7a
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/maxconnections.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="max connections"
+                 context="S"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option allows the number of simultaneous connections to a service to be limited.
+    If <parameter moreinfo="none">max connections</parameter> is greater than 0 then connections
+    will be refused if this number of connections to the service are already open. A value 
+    of zero mean an unlimited number of connections may be made.</para>
+
+    <para>Record lock files are used to implement this feature. The lock files will be stored in 
+    the directory specified by the <smbconfoption name="lock directory"/> option.</para>
+</description>
+
+<value type="default">0</value>
+<value type="example">10</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/maxdisksize.xml b/docs-xml/smbdotconf/tuning/maxdisksize.xml
new file mode 100644
index 00000000000..ee53105a8a5
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/maxdisksize.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="max disk size"
+                 context="G"
+				 type="integer"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option allows you to put an upper limit 
+    on the apparent size of disks. If you set this option to 100 
+    then all shares will appear to be not larger than 100 MB in 
+    size.</para>
+
+    <para>Note that this option does not limit the amount of 
+    data you can put on the disk. In the above case you could still 
+    store much more than 100 MB on the disk, but if a client ever asks 
+    for the amount of free disk space or the total disk size then the 
+    result will be bounded by the amount specified in <parameter moreinfo="none">max 
+    disk size</parameter>.</para>
+
+    <para>This option is primarily useful to work around bugs 
+    in some pieces of software that can't handle very large disks, 
+    particularly disks over 1GB in size.</para>
+
+    <para>A <parameter moreinfo="none">max disk size</parameter> of 0 means no limit.</para>
+</description>
+
+<value type="default">0</value>
+<value type="example">1000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/maxopenfiles.xml b/docs-xml/smbdotconf/tuning/maxopenfiles.xml
new file mode 100644
index 00000000000..ea0a33980a0
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/maxopenfiles.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="max open files"
+				 type="integer"
+                 context="G"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter limits the maximum number of 
+    open files that one <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> file 
+    serving process may have open for a client at any one time. The 
+    default for this parameter is set very high (10,000) as Samba uses 
+    only one bit per unopened file.</para>
+		
+    <para>The limit of the number of open files is usually set 
+    by the UNIX per-process file descriptor limit rather than 
+    this parameter so you should never need to touch this parameter.</para>
+</description>
+
+<value type="default">10000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/maxsmbdprocesses.xml b/docs-xml/smbdotconf/tuning/maxsmbdprocesses.xml
new file mode 100644
index 00000000000..677d731aa95
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/maxsmbdprocesses.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="max smbd processes"
+				 type="integer"
+                 context="G"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This parameter limits the maximum number of <citerefentry><refentrytitle>smbd</refentrytitle>                                       
+    <manvolnum>8</manvolnum></citerefentry> processes concurrently running on a system and is intended
+    as a stopgap to prevent degrading service to clients in the event that the server has insufficient
+    resources to handle more than this number of connections.  Remember that under normal operating
+    conditions, each user will have an <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> associated with him or her to handle connections to all
+    shares from a given host.</para>
+</description>
+
+<value type="default">0</value>
+<value type="example">1000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/minprintspace.xml b/docs-xml/smbdotconf/tuning/minprintspace.xml
new file mode 100644
index 00000000000..706e4a70cf1
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/minprintspace.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="min print space"
+                 context="S"
+				 type="integer"
+                 print="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This sets the minimum amount of free disk 
+    space that must be available before a user will be able to spool 
+    a print job. It is specified in kilobytes. The default is 0, which 
+    means a user can always spool a print job.</para>
+</description>
+
+<related>printing</related>
+<value type="default">0</value>
+<value type="example">2000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/namecachetimeout.xml b/docs-xml/smbdotconf/tuning/namecachetimeout.xml
new file mode 100644
index 00000000000..32ad55f1d0e
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/namecachetimeout.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="name cache timeout"
+                 context="G"
+				 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>Specifies the number of seconds it takes before 
+    entries in samba's hostname resolve cache time out. If 
+    the timeout is set to 0. the caching is disabled.
+</para>
+</description>
+
+<value type="default">660</value>
+<value type="example">0</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/paranoidserversecurity.xml b/docs-xml/smbdotconf/tuning/paranoidserversecurity.xml
new file mode 100644
index 00000000000..e5c2fe0ad14
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/paranoidserversecurity.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="paranoid server security"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>Some version of NT 4.x allow non-guest 
+    users with a bad passowrd. When this option is enabled, samba will not 
+    use a broken NT 4.x server as password server, but instead complain
+    to the logs and exit.  
+    </para>
+
+    <para>Disabling this option prevents Samba from making
+    this check, which involves deliberatly attempting a
+    bad logon to the remote server.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/socketoptions.xml b/docs-xml/smbdotconf/tuning/socketoptions.xml
new file mode 100644
index 00000000000..7a5c2219398
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/socketoptions.xml
@@ -0,0 +1,75 @@
+<samba:parameter name="socket options"
+                 context="G"
+				 type="list"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This option allows you to set socket options 
+    to be used when talking with the client.</para>
+
+    <para>Socket options are controls on the networking layer 
+    of the operating systems which allow the connection to be 
+    tuned.</para>
+
+    <para>This option will typically be used to tune your Samba  server
+    for optimal performance for your local network. There is  no way
+    that Samba can know what the optimal parameters are for  your net,
+    so you must experiment and choose them yourself. We  strongly
+    suggest you read the appropriate documentation for your  operating
+    system first (perhaps <command moreinfo="none">man
+    setsockopt</command> will help).</para>
+
+    <para>You may find that on some systems Samba will say 
+    &quot;Unknown socket option&quot; when you supply an option. This means you 
+    either incorrectly  typed it or you need to add an include file 
+    to includes.h for your OS.  If the latter is the case please 
+    send the patch to <ulink url="mailto:samba-technical@samba.org">
+    samba-technical@samba.org</ulink>.</para>
+
+    <para>Any of the supported socket options may be combined 
+    in any way you like, as long as your OS allows it.</para>
+
+    <para>This is the list of socket options currently settable 
+    using this option:</para>
+
+    <itemizedlist>
+    	<listitem><para>SO_KEEPALIVE</para></listitem>
+    	<listitem><para>SO_REUSEADDR</para></listitem>
+    	<listitem><para>SO_BROADCAST</para></listitem>
+    	<listitem><para>TCP_NODELAY</para></listitem>
+    	<listitem><para>IPTOS_LOWDELAY</para></listitem>
+    	<listitem><para>IPTOS_THROUGHPUT</para></listitem>
+    	<listitem><para>SO_SNDBUF *</para></listitem>
+    	<listitem><para>SO_RCVBUF *</para></listitem>
+    	<listitem><para>SO_SNDLOWAT *</para></listitem>
+    	<listitem><para>SO_RCVLOWAT *</para></listitem>
+    </itemizedlist>
+
+    <para>Those marked with a <emphasis>'*'</emphasis> take an integer 
+    argument. The others can optionally take a 1 or 0 argument to enable 
+    or disable the option, by default they will be enabled if you 
+    don't specify 1 or 0.</para>
+
+    <para>To specify an argument use the syntax SOME_OPTION = VALUE 
+    for example <command moreinfo="none">SO_SNDBUF = 8192</command>. Note that you must 
+    not have any spaces before or after the = sign.</para>
+
+    <para>If you are on a local network then a sensible option 
+    might be:</para>
+
+    <para><command moreinfo="none">socket options = IPTOS_LOWDELAY</command></para>
+
+    <para>If you have a local network then you could try:</para>
+
+    <para><command moreinfo="none">socket options = IPTOS_LOWDELAY TCP_NODELAY</command></para>
+
+    <para>If you are on a wide area network then perhaps try 
+    setting IPTOS_THROUGHPUT. </para>
+
+    <para>Note that several of the options may cause your Samba 
+		server to fail completely. Use these options with caution!</para>
+</description>
+
+<value type="default">TCP_NODELAY</value>
+<value type="example">IPTOS_LOWDELAY</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/strictallocate.xml b/docs-xml/smbdotconf/tuning/strictallocate.xml
new file mode 100644
index 00000000000..2606f2028b3
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/strictallocate.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="strict allocate"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This is a boolean that controls the handling of 
+    disk space allocation in the server. When this is set to <constant>yes</constant> 
+    the server will change from UNIX behaviour of not committing real
+    disk storage blocks when a file is extended to the Windows behaviour
+    of actually forcing the disk system to allocate real storage blocks
+    when a file is created or extended to be a given size. In UNIX
+    terminology this means that Samba will stop creating sparse files.
+    This can be slow on some systems.</para>
+
+    <para>When strict allocate is <constant>no</constant> the server does sparse
+    disk block allocation when a file is extended.</para>
+
+    <para>Setting this to <constant>yes</constant> can help Samba return
+    out of quota messages on systems that are restricting the disk quota
+    of users.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/strictsync.xml b/docs-xml/smbdotconf/tuning/strictsync.xml
new file mode 100644
index 00000000000..0d338455131
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/strictsync.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="strict sync"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+    <para>Many Windows applications (including the Windows 98 explorer
+    shell) seem to confuse flushing buffer contents to disk with doing
+    a sync to disk. Under UNIX, a sync call forces the process to be
+    suspended until the kernel has ensured that all outstanding data in
+    kernel disk buffers has been safely stored onto stable storage.
+    This is very slow and should only be done rarely. Setting this
+    parameter to <constant>no</constant> (the default) means that
+    <citerefentry><refentrytitle>smbd</refentrytitle>
+    <manvolnum>8</manvolnum></citerefentry> ignores the Windows
+    applications requests for a sync call. There is only a possibility
+    of losing data if the operating system itself that Samba is running
+    on crashes, so there is little danger in this default setting. In
+    addition, this fixes many performance problems that people have
+    reported with the new Windows98 explorer shell file copies.</para>
+</description>
+
+<related>sync always</related>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/syncalways.xml b/docs-xml/smbdotconf/tuning/syncalways.xml
new file mode 100644
index 00000000000..5d8eb2d5682
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/syncalways.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="sync always"
+	context="S"
+	type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This is a boolean parameter that controls 
+    whether writes will always be written to stable storage before 
+    the write call returns. If this is <constant>no</constant> then the server will be 
+    guided by the client's request in each write call (clients can 
+    set a bit indicating that a particular write should be synchronous). 
+    If this is <constant>yes</constant> then every write will be followed by a <command moreinfo="none">fsync()
+    </command> call to ensure the data is written to disk. Note that 
+    the <parameter moreinfo="none">strict sync</parameter> parameter must be set to
+    <constant>yes</constant> in order for this parameter to have 
+    any affect.</para>
+</description>
+
+<related>strict sync</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/usemmap.xml b/docs-xml/smbdotconf/tuning/usemmap.xml
new file mode 100644
index 00000000000..c23fc358407
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/usemmap.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="use mmap"
+                 context="G"
+				 type="boolean"
+                 developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This global parameter determines if the tdb internals of Samba can
+    depend on mmap working correctly on the running system. Samba requires a coherent
+    mmap/read-write system memory cache. Currently only HPUX does not have such a
+    coherent cache, and so this parameter is set to <constant>no</constant> by
+    default on HPUX. On all other systems this parameter should be left alone. This
+    parameter is provided to help the Samba developers track down problems with
+    the tdb internal code.
+    </para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/usesendfile.xml b/docs-xml/smbdotconf/tuning/usesendfile.xml
new file mode 100644
index 00000000000..e721531fed4
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/usesendfile.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="use sendfile"
+                 context="S"
+				 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>If this parameter is <constant>yes</constant>, and the <constant>sendfile()</constant> 
+    system call is supported by the underlying operating system, then some SMB read calls 
+    (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that
+    are exclusively oplocked. This may make more efficient use of the system CPU's
+    and cause Samba to be faster. Samba automatically turns this off for clients
+    that use protocol levels lower than NT LM 0.12 and when it detects a client is
+    Windows 9x (using sendfile from Linux will cause these clients to fail).
+    </para>
+</description>
+
+<value type="default">false</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/tuning/writecachesize.xml b/docs-xml/smbdotconf/tuning/writecachesize.xml
new file mode 100644
index 00000000000..12965b40487
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/writecachesize.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="write cache size"
+                 context="S"
+				 type="integer"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>If this integer parameter is set to non-zero value,
+    Samba will create an in-memory cache for each oplocked file 
+    (it does <emphasis>not</emphasis> do this for 
+    non-oplocked files). All writes that the client does not request 
+    to be flushed directly to disk will be stored in this cache if possible. 
+    The cache is flushed onto disk when a write comes in whose offset 
+    would not fit into the cache or when the file is closed by the client. 
+    Reads for the file are also served from this cache if the data is stored 
+    within it.</para>
+
+    <para>This cache allows Samba to batch client writes into a more 
+    efficient write size for RAID disks (i.e. writes may be tuned to 
+    be the RAID stripe size) and can improve performance on systems 
+    where the disk subsystem is a bottleneck but there is free 
+    memory for userspace programs.</para>
+
+    <para>The integer parameter specifies the size of this cache 
+		(per oplocked file) in bytes.</para>
+</description>
+
+<value type="default">0</value>
+<value type="example">262144<comment> for a 256k cache size per file</comment></value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/vfs/aclcompatibility.xml b/docs-xml/smbdotconf/vfs/aclcompatibility.xml
new file mode 100644
index 00000000000..7891adc13b5
--- /dev/null
+++ b/docs-xml/smbdotconf/vfs/aclcompatibility.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="acl compatibility"
+                 context="S"
+				 type="enum"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies what OS ACL semantics should 
+	be compatible with. Possible values are <emphasis>winnt</emphasis> for Windows NT 4, 
+	<emphasis>win2k</emphasis> for Windows 2000 and above and <emphasis>auto</emphasis>.
+	If you specify <emphasis>auto</emphasis>, the value for this parameter 
+	will be based upon the version of the client. There should 
+	be no reason to change this parameter from the default.</para>
+</description>
+
+<value type="default">Auto</value>
+<value type="example">win2k</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/vfs/getquotacommand.xml b/docs-xml/smbdotconf/vfs/getquotacommand.xml
new file mode 100644
index 00000000000..809d1a118f2
--- /dev/null
+++ b/docs-xml/smbdotconf/vfs/getquotacommand.xml
@@ -0,0 +1,55 @@
+<samba:parameter name="get quota command"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>The <command>get quota command</command> should only be used 
+	whenever there is no operating system API available from the OS that 
+	samba can use.</para>
+
+	<para>This option is only available with <command>./configure --with-sys-quotas</command>.
+	Or on linux when <command>./configure --with-quotas</command> was used and a working quota api 
+	was found in the system.</para>
+
+	<para>This parameter should specify the path to a script that 
+	queries the quota information for the specified 
+	user/group for the partition that 
+	the specified directory is on.</para>
+
+	<para>Such a script should take 3 arguments:</para>
+
+	<itemizedlist>
+		<listitem><para>directory</para></listitem>
+		<listitem><para>type of query</para></listitem>
+		<listitem><para>uid of user or gid of group</para></listitem>
+	</itemizedlist>
+
+	<para>The type of query can be one of :</para>
+
+	<itemizedlist>
+		<listitem><para>1 - user quotas</para></listitem>
+		<listitem><para>2 - user default quotas (uid = -1)</para></listitem>
+		<listitem><para>3 - group quotas</para></listitem>
+		<listitem><para>4 - group default quotas (gid = -1)</para></listitem>
+	</itemizedlist>
+
+	<para>This script should print one line as output with spaces between the arguments. The arguments are: 
+	      </para>
+
+	<itemizedlist>
+		<listitem><para>Arg 1 - quota flags (0 = no quotas, 1 = quotas enabled, 2 = quotas enabled and enforced)</para></listitem>
+		<listitem><para>Arg 2 - number of currently used blocks</para></listitem>
+		<listitem><para>Arg 3 - the softlimit number of blocks</para></listitem>
+		<listitem><para>Arg 4 - the hardlimit number of blocks</para></listitem>
+		<listitem><para>Arg 5 - currently used number of inodes</para></listitem>
+		<listitem><para>Arg 6 - the softlimit number of inodes</para></listitem>
+		<listitem><para>Arg 7 - the hardlimit number of inodes</para></listitem>
+		<listitem><para>Arg 8(optional) - the number of bytes in a block(default is 1024)</para></listitem>
+	</itemizedlist>
+</description>
+
+<related>set quote command</related>
+<value type="default"></value>
+<value type="example">/usr/local/sbin/query_quota</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/vfs/hostmsdfs.xml b/docs-xml/smbdotconf/vfs/hostmsdfs.xml
new file mode 100644
index 00000000000..67f67dce45a
--- /dev/null
+++ b/docs-xml/smbdotconf/vfs/hostmsdfs.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="host msdfs"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>
+	If set to <constant>yes</constant>, Samba will act as a Dfs server, and allow Dfs-aware clients to browse
+	Dfs trees hosted on the server.
+	</para>
+
+	<para>
+	See also the <smbconfoption name="msdfs root"/> share  level  parameter.  For more  information  on
+	setting  up a Dfs tree on Samba, refer to the MSFDS chapter in the book Samba3-HOWTO.
+	</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/vfs/msdfsproxy.xml b/docs-xml/smbdotconf/vfs/msdfsproxy.xml
new file mode 100644
index 00000000000..5117bae2241
--- /dev/null
+++ b/docs-xml/smbdotconf/vfs/msdfsproxy.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="msdfs proxy"
+                 context="S"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter indicates that the share is a
+	stand-in for another CIFS share whose location is specified by
+	the value of the parameter. When clients attempt to connect to
+	this share, they are redirected to the proxied share using
+	the SMB-Dfs protocol.</para>
+
+	<para>Only Dfs roots can act as proxy shares. Take a look at the
+	<smbconfoption name="msdfs root"/> and <smbconfoption name="host msdfs"/>
+	options to find out how to set up a Dfs root share.</para>
+</description>
+
+<value type="example">\otherserver\someshare</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/vfs/msdfsroot.xml b/docs-xml/smbdotconf/vfs/msdfsroot.xml
new file mode 100644
index 00000000000..86dc6f1d8cb
--- /dev/null
+++ b/docs-xml/smbdotconf/vfs/msdfsroot.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="msdfs root"
+                 context="S"
+				 tye="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>If set to <constant>yes</constant>, Samba treats the
+	share as a Dfs root and allows clients to browse the
+	distributed file system tree rooted at the share directory.
+	Dfs links are specified in the share directory by symbolic
+	links of the form <filename>msdfs:serverA\\shareA,serverB\\shareB</filename>
+	and so on.  For more information on setting up a Dfs tree on
+	Samba, refer to the MSDFS chapter in the Samba3-HOWTO book.</para>
+</description>
+
+<related>host msdfs</related>
+<value type="default">no</value>
+<para>See also <smbconfoption name="host msdfs"/></para>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/vfs/setquotacommand.xml b/docs-xml/smbdotconf/vfs/setquotacommand.xml
new file mode 100644
index 00000000000..b00a6206286
--- /dev/null
+++ b/docs-xml/smbdotconf/vfs/setquotacommand.xml
@@ -0,0 +1,44 @@
+<samba:parameter name="set quota command"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>The <command>set quota command</command> should only be used 
+	whenever there is no operating system API available from the OS that 
+	samba can use.</para>
+
+	<para>This option is only available if Samba was configured with the argument <command>--with-sys-quotas</command> or 
+	on linux when <command>./configure --with-quotas</command> was used and a working quota api 
+	was found in the system. Most packages are configured with these options already.</para>
+
+	<para>This parameter should specify the path to a script that 
+	can set quota for the specified arguments.</para>
+
+	<para>The specified script should take the following arguments:</para>
+
+	<itemizedlist>
+		<listitem><para>1 - quota type
+			<itemizedlist>
+				<listitem><para>1 - user quotas</para></listitem>
+				<listitem><para>2 - user default quotas (uid = -1)</para></listitem>
+				<listitem><para>3 - group quotas</para></listitem>
+				<listitem><para>4 - group default quotas (gid = -1)</para></listitem>
+			</itemizedlist></para></listitem>
+		<listitem><para>2 - id (uid for user, gid for group, -1 if N/A)</para></listitem>
+		<listitem><para>3 - quota state (0 = disable, 1 = enable, 2 = enable and enforce)</para></listitem>
+		<listitem><para>4 - block softlimit</para></listitem>
+		<listitem><para>5 - block hardlimit</para></listitem>
+		<listitem><para>6 - inode softlimit</para></listitem>
+		<listitem><para>7 - inode hardlimit</para></listitem>
+		<listitem><para>8(optional) - block size, defaults to 1024</para></listitem>
+	</itemizedlist>
+
+	<para>The script should output at least one line of data on success. And nothing on failure.</para>
+</description>
+
+<related>get quota command</related>
+
+<value type="default"></value>
+<value type="example">/usr/local/sbin/set_quota</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/vfs/vfsobjects.xml b/docs-xml/smbdotconf/vfs/vfsobjects.xml
new file mode 100644
index 00000000000..09d41c75b0e
--- /dev/null
+++ b/docs-xml/smbdotconf/vfs/vfsobjects.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="vfs objects"
+				type="list"
+                 context="S"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>vfs object</synonym>
+<description>
+	<para>This parameter specifies the backend names which 
+	are used for Samba VFS I/O operations.  By default, normal 
+	disk I/O operations are used but these can be overloaded 
+	with one or more VFS objects. </para>
+</description>
+
+<value type="default"/>
+<value type="example">extd_audit recycle</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/idmapallocbackend.xml b/docs-xml/smbdotconf/winbind/idmapallocbackend.xml
new file mode 100644
index 00000000000..60e20b82d5e
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/idmapallocbackend.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="idmap alloc backend"
+                 context="G"
+		 type="string"
+                 advanced="1" developer="1" hide="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	The idmap alloc backend provides a plugin interface for Winbind to use
+	when allocating Unix uids/gids for Windows SIDs.  This option is
+	to be used in conjunction with the <smbconfoption name="idmap domains"/> 
+	parameter and refers to the name of the idmap module which will provide
+	the id allocation functionality.  Please refer to the man page 
+	for each idmap plugin to determine whether or not the module implements
+	the allocation feature.  The most common plugins are the tdb (<citerefentry>
+        <refentrytitle>idmap_tdb</refentrytitle><manvolnum>8</manvolnum></citerefentry>)
+        and ldap (<citerefentry><refentrytitle>idmap_ldap</refentrytitle>
+        <manvolnum>8</manvolnum></citerefentry>) libraries.
+	</para>
+
+	<para>Also refer to the <smbconfoption name="idmap alloc config"/> option.
+	</para>
+</description>
+
+<value type="example">tdb</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/idmapallocconfig.xml b/docs-xml/smbdotconf/winbind/idmapallocconfig.xml
new file mode 100644
index 00000000000..013904122c0
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/idmapallocconfig.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="idmap alloc config"
+                 context="G"
+		 type="string"
+                 advanced="1" developer="1" hide="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	The idmap alloc config prefix provides a means of managing settings
+	for the backend defined by the <smbconfoption name="idmap alloc backend"/> 
+	parameter.  Refer to the man page for each idmap plugin regarding
+	specific configuration details.
+	</para>
+</description>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/idmapbackend.xml b/docs-xml/smbdotconf/winbind/idmapbackend.xml
new file mode 100644
index 00000000000..20e1115c5fc
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/idmapbackend.xml
@@ -0,0 +1,28 @@
+<samba:parameter name="idmap backend"
+                 context="G"
+		 type="string"
+                 advanced="1" developer="1" hide="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	The idmap backend provides a plugin interface for Winbind to use
+	varying backends to store SID/uid/gid mapping tables.  This
+	option is mutually exclusive with the newer and more flexible
+	<smbconfoption name="idmap domains"/> parameter.  The main difference
+	between the &quot;idmap backend&quot; and the &quot;idmap domains&quot;
+	is that the former only allows on backend for all domains while the
+	latter supports configuring backends on a per domain basis.
+	</para>
+
+	<para>Examples of SID/uid/gid backends include tdb (<citerefentry>
+	<refentrytitle>idmap_tdb</refentrytitle><manvolnum>8</manvolnum></citerefentry>),
+	ldap (<citerefentry><refentrytitle>idmap_ldap</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>), rid (<citerefentry>
+	<refentrytitle>idmap_rid</refentrytitle><manvolnum>8</manvolnum></citerefentry>),
+	and ad (<citerefentry><refentrytitle>idmap_tdb</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry>).
+	</para>
+</description>
+
+<value type="default">tdb</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/idmapcachetime.xml b/docs-xml/smbdotconf/winbind/idmapcachetime.xml
new file mode 100644
index 00000000000..1636cdfa58e
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/idmapcachetime.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="idmap cache time"
+                 context="G"
+		 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies the number of seconds that Winbind's
+	idmap interface will cache positive SID/uid/gid query results.
+	</para>
+</description>
+
+<value type="default">900</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/idmapconfig.xml b/docs-xml/smbdotconf/winbind/idmapconfig.xml
new file mode 100644
index 00000000000..63b0a907a8d
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/idmapconfig.xml
@@ -0,0 +1,65 @@
+<samba:parameter name="idmap config"
+                 context="G"
+		 type="string"
+                 advanced="1" developer="1" hide="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	The idmap config prefix provides a means of managing each domain 
+	defined by the <smbconfoption name="idmap domains"/> option using Samba's
+	parameteric option support.  The idmap config prefix should be 
+	followed by the name of the domain, a colon, and a setting specific to 
+	the chosen backend.  There are three options available for all domains:
+	</para>
+	<variablelist>  
+		<varlistentry>
+		<term>backend = backend_name</term>
+		<listitem><para>
+			Specifies the name of the idmap plugin to use as the 
+			SID/uid/gid backend for this domain.
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>default = [yes|no]</term>
+		<listitem><para>
+			The default domain/backend will be used for searching for 
+			users and groups not belonging to one of the explicitly
+			listed domains (matched by comparing the account SID and the 
+			domain SID).
+		</para></listitem>
+		</varlistentry>
+
+		<varlistentry>
+		<term>readonly = [yes|no]</term>
+		<listitem><para>
+			Mark the domain as readonly which means that no attempts to
+			allocate a uid or gid (by the <smbconfoption name="idmap alloc 
+			backend"/>) for any user or group in that domain
+			will be attempted.
+		</para></listitem>
+		</varlistentry>
+	</variablelist>
+
+	<para>
+	The following example illustrates how to configure the <citerefentry>
+	<refentrytitle>idmap_ad</refentrytitle><manvolnum>8</manvolnum></citerefentry> 
+	for the CORP domain and the <citerefentry><refentrytitle>idmap_tdb</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> backend for all other domains.  The 
+	TRUSTEDDOMAINS string is simply a key used to reference the &quot;idmap 
+	config&quot; settings and does not represent the actual name of a domain.
+	</para>
+
+	<programlisting>
+	idmap domains = CORP TRUSTEDDOMAINS
+
+	idmap config CORP:backend  = ad
+	idmap config CORP:readonly = yes
+
+	idmap config TRUSTEDDOMAINS:backend = tdb
+	idmap config TRUSTEDDOMAINS:default = yes
+	idmap config TRUSTEDDOMAINS:range   = 1000 - 9999
+	</programlisting>
+	
+</description>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/idmapdomains.xml b/docs-xml/smbdotconf/winbind/idmapdomains.xml
new file mode 100644
index 00000000000..131b9e8167b
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/idmapdomains.xml
@@ -0,0 +1,27 @@
+<samba:parameter name="idmap domains"
+                 context="G"
+		 type="string"
+                 advanced="1" developer="1" hide="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	The idmap domains option defines a list of Windows domains which will each
+	have a separately configured backend for managing Winbind's SID/uid/gid
+	tables.  This parameter is mutually exclusive with the older <smbconfoption 
+	name="idmap backend"/> option.
+	</para>
+
+	<para>
+	Values consist of the short domain name for Winbind's primary or collection
+	of trusted domains.  You may also use an arbitrary string to represent a catchall
+	domain backend for any domain not explicitly listed.
+	</para>
+
+	<para>
+	Refer to the <smbconfoption name="idmap config"/> for details about
+	managing the SID/uid/gid backend for each domain.
+	</para>
+</description>
+
+<value type="example">default AD CORP</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/idmapgid.xml b/docs-xml/smbdotconf/winbind/idmapgid.xml
new file mode 100644
index 00000000000..28d88b51b0d
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/idmapgid.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="idmap gid"
+                 context="G"
+		 type="string"
+                 advanced="1" developer="1" hide="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+		<synonym>winbind gid</synonym>
+<description>
+	<para>The idmap gid parameter specifies the range of group ids 
+	that are allocated for the purpose of mapping UNX groups to NT group 
+	SIDs. This range of group ids should have no 
+	existing local or NIS groups within it as strange conflicts can 
+	occur otherwise.</para>
+
+	<para>See also the <smbconfoption name="idmap backend"/>, <smbconfoption 
+	name="idmap domains"/>, and <smbconfoption name="idmap config"/> options.
+	</para>
+</description>
+
+<value type="default"></value>
+<value type="example">10000-20000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/idmapnegativecachetime.xml b/docs-xml/smbdotconf/winbind/idmapnegativecachetime.xml
new file mode 100644
index 00000000000..6790938d947
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/idmapnegativecachetime.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="idmap negative cache time"
+                 context="G"
+		 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies the number of seconds that Winbind's
+	idmap interface will cache negative SID/uid/gid query results.
+	</para>
+</description>
+
+<value type="default">120</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/idmapuid.xml b/docs-xml/smbdotconf/winbind/idmapuid.xml
new file mode 100644
index 00000000000..de4074cfa4c
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/idmapuid.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="idmap uid"
+			 type="string"
+                 context="G"
+                 advanced="1" developer="1" hide="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<synonym>winbind uid</synonym>
+<description>
+	<para>
+	The idmap uid parameter specifies the range of user ids that are 
+	allocated for use in mapping UNIX users to NT user SIDs. This 
+	range of ids should have no existing local
+	or NIS users within it as strange conflicts can occur otherwise.</para>
+
+	<para>See also the <smbconfoption name="idmap backend"/>, <smbconfoption 
+	name="idmap domains"/>, and <smbconfoption name="idmap config"/> options.
+	</para>
+</description>
+
+<value type="default"></value>
+<value type="example">10000-20000</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/templatehomedir.xml b/docs-xml/smbdotconf/winbind/templatehomedir.xml
new file mode 100644
index 00000000000..f5965c613c0
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/templatehomedir.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="template homedir"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>When filling out the user information for a Windows NT 
+	user, the <citerefentry><refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> daemon  uses this
+	parameter to fill in the home directory for that user. If the
+	string <parameter moreinfo="none">%D</parameter> is present it
+	is substituted  with the user's Windows NT domain name. If the
+	string <parameter  moreinfo="none">%U</parameter> is present it
+	is substituted with the user's Windows  NT user name.</para>
+</description>
+
+<value type="default">/home/%D/%U</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/templateshell.xml b/docs-xml/smbdotconf/winbind/templateshell.xml
new file mode 100644
index 00000000000..ce59cd12d0c
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/templateshell.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="template shell"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>When filling out the user information for a Windows NT 
+	user, the <citerefentry><refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> daemon uses this
+	parameter to fill in the login shell for that user.</para>
+</description>
+
+<value type="string">/bin/false</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindcachetime.xml b/docs-xml/smbdotconf/winbind/winbindcachetime.xml
new file mode 100644
index 00000000000..6bdcf0d06ed
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindcachetime.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="winbind cache time"
+                 context="G"
+				 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies the number of 
+	seconds the <citerefentry><refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> daemon will cache 
+	user and group information before querying a Windows NT server 
+	again.</para>
+
+        <para>
+	This does not apply to authentication requests, these are always 
+	evaluated in real time unless the <smbconfoption name="winbind 
+	offline logon"/> option has been enabled.
+	</para>
+</description>
+
+<value type="default">300</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindenumgroups.xml b/docs-xml/smbdotconf/winbind/winbindenumgroups.xml
new file mode 100644
index 00000000000..74f6feed017
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindenumgroups.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="winbind enum groups"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>On large installations using <citerefentry><refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> it may be necessary to suppress 
+	the enumeration of groups through the <command moreinfo="none">setgrent()</command>,
+	<command moreinfo="none">getgrent()</command> and
+	<command moreinfo="none">endgrent()</command> group of system calls.  If
+	the <parameter moreinfo="none">winbind enum groups</parameter> parameter is
+	<constant>no</constant>, calls to the <command moreinfo="none">getgrent()</command> system
+	call will not return any data. </para>
+
+<warning><para>Turning off group enumeration may cause some programs to behave oddly.  </para></warning>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindenumusers.xml b/docs-xml/smbdotconf/winbind/winbindenumusers.xml
new file mode 100644
index 00000000000..c987feaf8af
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindenumusers.xml
@@ -0,0 +1,23 @@
+<samba:parameter name="winbind enum users"
+                 context="G"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>On large installations using <citerefentry><refentrytitle>winbindd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> it may be
+	necessary to suppress the enumeration of users through the <command moreinfo="none">setpwent()</command>,
+	 <command moreinfo="none">getpwent()</command> and
+	 <command moreinfo="none">endpwent()</command> group of system calls.  If
+	the <parameter moreinfo="none">winbind enum users</parameter> parameter is
+	 <constant>no</constant>, calls to the <command moreinfo="none">getpwent</command> system call
+	will not return any data. </para>
+
+<warning><para>Turning off user
+	enumeration may cause some programs to behave oddly.  For
+	example, the finger program relies on having access to the
+	full user list when searching for matching
+	usernames. </para></warning>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindexpandgroups.xml b/docs-xml/smbdotconf/winbind/winbindexpandgroups.xml
new file mode 100644
index 00000000000..19b81b3e0ae
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindexpandgroups.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="winbind expand groups"
+                 context="G"
+		 type="integer"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This option controls the maximum depth that winbindd
+              will traverse when flattening nested group memberships
+	      of Windows domain groups.  This is different from the
+	      <smbconfoption name="winbind nested groups"/> option
+              which implements the Windows NT4 model of local group 
+	      nesting.  The &quot;winbind expand groups&quot;
+              parameter specifically applies to the membership of 
+	      domain groups.</para>
+
+	 <para>Be aware that a high value for this parameter can
+	 result in system slowdown as the main parent winbindd daemon
+	 must perform the group unrolling and will be unable to answer
+	 incoming NSS or authentication requests during this time.</para>
+  
+</description>
+
+<value type="default">1</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindnestedgroups.xml b/docs-xml/smbdotconf/winbind/winbindnestedgroups.xml
new file mode 100644
index 00000000000..01e95bbaca6
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindnestedgroups.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="winbind nested groups"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>If set to yes, this parameter activates the support for nested
+                 groups. Nested groups are also called local groups or
+                 aliases. They work like their counterparts in Windows: Nested
+                 groups are defined locally on any machine (they are shared
+                 between DC's through their SAM) and can contain users and
+                 global groups from any trusted SAM. To be able to use nested
+                 groups, you need to run nss_winbind.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindnormalizenames.xml b/docs-xml/smbdotconf/winbind/winbindnormalizenames.xml
new file mode 100644
index 00000000000..28826cf5f36
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindnormalizenames.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="winbind normalize names"
+                 context="G"
+		 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter controls whether winbindd will replace
+	whitespace in user and group names with an underscore (_) character.
+	For example, whether the name &quot;Space Kadet&quot; should be
+	replaced with the string &quot;space_kadet&quot;.
+	Frequently Unix shell scripts will have difficulty with usernames 
+	contains whitespace due to the default field separator in the shell.
+	Do not enable this option if the underscore character is used in
+	account names within your domain
+	</para>
+</description>
+
+<value type="default">no</value>
+<value type="example">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindnssinfo.xml b/docs-xml/smbdotconf/winbind/winbindnssinfo.xml
new file mode 100644
index 00000000000..d6e40c6bf68
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindnssinfo.xml
@@ -0,0 +1,40 @@
+<samba:parameter name="winbind nss info"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>This parameter is designed to control how Winbind retrieves Name
+	Service Information to construct a user's home directory and login shell. 
+	Currently the following settings are available: 
+
+	<itemizedlist>
+		<listitem>
+			<para><parameter moreinfo="none">template</parameter> 
+			- The default, using the parameters of <parameter moreinfo="none">template 
+			shell</parameter> and <parameter moreinfo="none">template homedir</parameter>)
+			</para>
+		</listitem>
+			
+		<listitem>
+			<para><parameter moreinfo="none">&lt;sfu | rfc2307 &gt;</parameter>
+			- When Samba is running in security = ads and your Active Directory
+			Domain Controller does support the Microsoft "Services for Unix" (SFU)
+			LDAP schema, winbind can retrieve the login shell and the home
+			directory attributes directly from your Directory Server. Note that
+			retrieving UID and GID from your ADS-Server requires to 
+			use <parameter moreinfo="non">idmap backend</parameter> = ad 
+			or <parameter moreinfo="non">idmap config DOMAIN:backend</parameter> = ad 
+			as well.
+			</para>
+		</listitem>
+			
+	</itemizedlist>
+
+</para>
+</description>
+
+<value type="default">template</value>
+<value type="example">template sfu</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindofflinelogon.xml b/docs-xml/smbdotconf/winbind/winbindofflinelogon.xml
new file mode 100644
index 00000000000..b5a0de16315
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindofflinelogon.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="winbind offline logon"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>This parameter is designed to control whether Winbind should
+	allow to login with the <parameter moreinfo="none">pam_winbind</parameter> 
+	module using Cached Credentials. If enabled, winbindd will store user credentials
+	from successful logins encrypted in a local cache.
+	</para>
+
+</description>
+
+<value type="default">false</value>
+<value type="example">true</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindrefreshtickets.xml b/docs-xml/smbdotconf/winbind/winbindrefreshtickets.xml
new file mode 100644
index 00000000000..d39cb768610
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindrefreshtickets.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="winbind refresh tickets"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>This parameter is designed to control whether Winbind should refresh Kerberos Tickets
+	retrieved using the <parameter moreinfo="none">pam_winbind</parameter> module.
+
+</para>
+</description>
+
+<value type="default">false</value>
+<value type="example">true</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindrpconly.xml b/docs-xml/smbdotconf/winbind/winbindrpconly.xml
new file mode 100644
index 00000000000..53a08773502
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindrpconly.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="winbind rpc only"
+	context="G"
+	type="string"
+		 advanced="1" developer="0"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+	<para>
+	Setting this parameter to <value type="example">yes</value> forces 
+	winbindd to use RPC instead of LDAP to retrieve information from Domain
+        Controllers.
+	</para>
+	
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindseparator.xml b/docs-xml/smbdotconf/winbind/winbindseparator.xml
new file mode 100644
index 00000000000..63ab42000d1
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindseparator.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="winbind separator"
+                 context="G"
+                 advanced="1" developer="1"
+				 type="string"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter allows an admin to define the character 
+	used when listing a username of the form of <replaceable>DOMAIN
+	</replaceable>\<replaceable>user</replaceable>.  This parameter 
+	is only applicable when using the <filename moreinfo="none">pam_winbind.so</filename>
+	and <filename moreinfo="none">nss_winbind.so</filename> modules for UNIX services.
+	</para>
+
+	<para>Please note that setting this parameter to + causes problems
+	with group membership at least on glibc systems, as the character +
+	is used as a special character for NIS in /etc/group.</para>
+</description>
+
+<value type="default">'\'</value>
+<value type="example">+</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindtrusteddomainsonly.xml b/docs-xml/smbdotconf/winbind/winbindtrusteddomainsonly.xml
new file mode 100644
index 00000000000..6ca229cfe92
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindtrusteddomainsonly.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="winbind trusted domains only"
+                 context="G"
+		 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>
+	This parameter is designed to allow Samba servers that are members 
+	of a Samba controlled domain to use UNIX accounts distributed via NIS, 
+	rsync, or LDAP as the uid's for winbindd users in the hosts primary domain.
+	Therefore, the user <literal>DOMAIN\user1</literal> would be mapped to 
+	the account user1 in /etc/passwd instead of allocating a new uid for him or her.
+	</para>
+
+	<para>
+	This parameter is now deprecated in favor of the newer idmap_nss backend.
+	Refer to the <smbconfoption name="idmap domains"/> smb.conf option and
+	the <citerefentry><refentrytitle>idmap_nss</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> man page for more information.
+	</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/winbind/winbindusedefaultdomain.xml b/docs-xml/smbdotconf/winbind/winbindusedefaultdomain.xml
new file mode 100644
index 00000000000..334068a329a
--- /dev/null
+++ b/docs-xml/smbdotconf/winbind/winbindusedefaultdomain.xml
@@ -0,0 +1,19 @@
+<samba:parameter name="winbind use default domain"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This parameter specifies whether the
+	 <citerefentry><refentrytitle>winbindd</refentrytitle> 
+	<manvolnum>8</manvolnum></citerefentry> daemon should operate on users  
+	without domain component in their username. Users without a domain
+	component are treated as is part of the winbindd server's own
+	domain. While this does not benifit Windows users, it makes SSH, FTP and
+	e-mail function in a way much closer to the way they
+	would in a native unix system.</para>
+</description>
+
+<value type="default">no</value>
+<value type="example">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/wins/dnsproxy.xml b/docs-xml/smbdotconf/wins/dnsproxy.xml
new file mode 100644
index 00000000000..018c7d93a7f
--- /dev/null
+++ b/docs-xml/smbdotconf/wins/dnsproxy.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="dns proxy"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>Specifies that <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> when acting as a WINS server and 
+	finding that a NetBIOS name has not been registered, should treat the 
+	NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server 
+	for that name on behalf of the name-querying client.</para>
+
+	<para>Note that the maximum length for a NetBIOS name is 15 
+	characters, so the DNS name (or DNS alias) can likewise only be 
+	15 characters, maximum.</para>
+
+	<para><command moreinfo="none">nmbd</command> spawns a second copy of itself to do the
+	DNS name lookup requests, as doing a name lookup is a blocking 
+	action.</para>
+</description>
+
+<related>wins support</related>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/wins/winshook.xml b/docs-xml/smbdotconf/wins/winshook.xml
new file mode 100644
index 00000000000..9e41fbd7c8a
--- /dev/null
+++ b/docs-xml/smbdotconf/wins/winshook.xml
@@ -0,0 +1,58 @@
+<samba:parameter name="wins hook"
+                 context="G"
+				 type="string"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>When Samba is running as a WINS server this 
+	allows you to call an external program for all changes to the 
+	WINS database. The primary use for this option is to allow the 
+	dynamic update of external name resolution databases such as 
+	dynamic DNS.</para>
+
+	<para>The wins hook parameter specifies the name of a script 
+	or executable that will be called as follows:</para>
+
+	<para><command moreinfo="none">wins_hook operation name nametype ttl IP_list</command></para>
+
+	<itemizedlist>
+		<listitem>
+			<para>The first argument is the operation and is
+			one  of &quot;add&quot;, &quot;delete&quot;, or
+			&quot;refresh&quot;. In most cases the operation
+			can  be ignored as the rest of the parameters
+			provide sufficient  information. Note that
+			&quot;refresh&quot; may sometimes be called when
+			the  name has not previously been added, in that
+			case it should be treated  as an add.</para>
+		</listitem>
+
+		<listitem>
+			<para>The second argument is the NetBIOS name. If the 
+			name is not a legal name then the wins hook is not called. 
+			Legal names contain only  letters, digits, hyphens, underscores 
+			and periods.</para>
+		</listitem>
+
+		<listitem>
+			<para>The third argument is the NetBIOS name 
+			type as a 2 digit hexadecimal number. </para>
+		</listitem>
+
+		<listitem>
+			<para>The fourth argument is the TTL (time to live) 
+			for the name in seconds.</para>
+		</listitem>
+			
+		<listitem>
+			<para>The fifth and subsequent arguments are the IP 
+			addresses currently registered for that name. If this list is 
+			empty then the name should be deleted.</para>
+		</listitem>
+	</itemizedlist>
+
+	<para>An example script that calls the BIND dynamic DNS update 
+	program <command moreinfo="none">nsupdate</command> is provided in the examples 
+	directory of the Samba source code. </para>
+</description>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/wins/winsproxy.xml b/docs-xml/smbdotconf/wins/winsproxy.xml
new file mode 100644
index 00000000000..8f98687dba1
--- /dev/null
+++ b/docs-xml/smbdotconf/wins/winsproxy.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="wins proxy"
+                 context="G"
+				 type="boolean"
+                 advanced="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This is a boolean that controls if <citerefentry><refentrytitle>nmbd</refentrytitle>                                 
+	<manvolnum>8</manvolnum></citerefentry> will respond to broadcast name 
+	queries on behalf of  other hosts. You may need to set this 
+	to <constant>yes</constant> for some older clients.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/wins/winsserver.xml b/docs-xml/smbdotconf/wins/winsserver.xml
new file mode 100644
index 00000000000..afced35f507
--- /dev/null
+++ b/docs-xml/smbdotconf/wins/winsserver.xml
@@ -0,0 +1,34 @@
+<samba:parameter name="wins server"
+                 context="G"
+				 type="boolean"
+                 basic="1" advanced="1" wizard="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>This specifies the IP address (or DNS name: IP 
+	address for preference) of the WINS server that <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> should register with. If you have a WINS server on 
+	your network then you should set this to the WINS server's IP.</para>
+
+	<para>You should point this at your WINS server if you have a
+	multi-subnetted network.</para>
+
+	<para>If you want to work in multiple namespaces, you can 
+	give every wins server a 'tag'. For each tag, only one 
+	(working) server will be queried for a name. The tag should be 
+	separated from the ip address by a colon.
+	</para>
+
+	<note><para>You need to set up Samba to point 
+	to a WINS server if you have multiple subnets and wish cross-subnet 
+	browsing to work correctly.</para></note>
+	<para>See the chapter in the Samba3-HOWTO on Network Browsing.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61
+	<comment>For this example when querying a certain name, 192.19.200.1 will 
+	be asked first and if that doesn't respond 192.168.2.61. If either 
+	of those doesn't know the name 192.168.3.199 will be queried.</comment></value>
+
+<value type="example">192.9.200.1 192.168.2.61</value>
+</samba:parameter>
diff --git a/docs-xml/smbdotconf/wins/winssupport.xml b/docs-xml/smbdotconf/wins/winssupport.xml
new file mode 100644
index 00000000000..b4f89528ec7
--- /dev/null
+++ b/docs-xml/smbdotconf/wins/winssupport.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="wins support"
+	type="boolean"
+                 context="G"
+                 basic="1" advanced="1" wizard="1" developer="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+ <description>
+	<para>This boolean controls if the <citerefentry><refentrytitle>nmbd</refentrytitle>
+	<manvolnum>8</manvolnum></citerefentry> process in Samba will act as a WINS server. You should 
+	not set this to <constant>yes</constant> unless you have a multi-subnetted network and 
+	you wish a particular <command moreinfo="none">nmbd</command> to be your WINS server. 
+	Note that you should <emphasis>NEVER</emphasis> set this to <constant>yes</constant>
+	on more than one machine in your network.</para>
+
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs-xml/structure.svg b/docs-xml/structure.svg
new file mode 100644
index 00000000000..82dfd4650d1
--- /dev/null
+++ b/docs-xml/structure.svg
@@ -0,0 +1,585 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   version="1.0"
+   width="33.269001cm"
+   height="34.450001cm"
+   viewBox="0.35 1.35 33.619 35.8"
+   id="svg2">
+  <defs
+     id="defs197" />
+  <rect
+     width="10.55"
+     height="1.9"
+     x="3.375"
+     y="1.4"
+     id="rect4"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="13.364128"
+     height="1.8878119"
+     x="3.381094"
+     y="1.406094"
+     id="rect6"
+     style="fill:none;stroke:#000000;stroke-width:0.11218806" />
+  <text
+     x="4.2309999"
+     y="2.493"
+     id="text8"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Samba DocBook Source (XML)</text>
+  <polygon
+     points="4.653,6.75 12.794,6.75 12.066,8.75 3.925,8.75 4.653,6.75 "
+     id="polygon10"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.653,6.75 12.794,6.75 12.066,8.75 3.925,8.75 4.653,6.75 "
+     transform="matrix(1.211345,0,0,0.9951043,-0.8246336,3.7941591e-2)"
+     id="polygon12"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="5.1760001"
+     y="7.8920002"
+     id="text14"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">expand-sambadoc.xsl</text>
+  <line
+     x1="8.6499996"
+     y1="3.3"
+     x2="8.7130003"
+     y2="6.263"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line16"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="8.721,6.638 8.461,6.144 8.713,6.263 8.96,6.133 8.721,6.638 "
+     id="polygon18"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="8.721,6.638 8.461,6.144 8.713,6.263 8.96,6.133 8.721,6.638 "
+     id="polygon20"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="8.1999998"
+     height="1.9"
+     x="4.8499999"
+     y="11.65"
+     id="rect22"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="10.289943"
+     height="1.8883237"
+     x="4.8558378"
+     y="11.655838"
+     id="rect24"
+     style="fill:none;stroke:#000000;stroke-width:0.11167629" />
+  <text
+     x="5.6350002"
+     y="12.742"
+     id="text26"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">DocBook Source (XML)</text>
+  <line
+     x1="7.9499998"
+     y1="8.5500002"
+     x2="8.8009996"
+     y2="11.187"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line28"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="8.916,11.544 8.524,11.144 8.801,11.187 9,10.991 8.916,11.544 "
+     id="polygon30"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="8.916,11.544 8.524,11.144 8.801,11.187 9,10.991 8.916,11.544 "
+     id="polygon32"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="6.6999998"
+     height="1.9"
+     x="7"
+     y="21.700001"
+     id="rect34"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="6.6999998"
+     height="1.9"
+     x="7"
+     y="21.700001"
+     id="rect36"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7.704"
+     y="22.792999"
+     id="text38"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans" />
+  <text
+     x="7.704"
+     y="22.792999"
+     id="text5583"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans" />
+  <polygon
+     points="7.328,16.55 12.319,16.55 11.591,18.55 6.6,18.55 7.328,16.55 "
+     id="polygon40"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="7.328,16.55 12.319,16.55 11.591,18.55 6.6,18.55 7.328,16.55 "
+     transform="matrix(1.1005379,0,0,0.9976095,-0.6611594,4.1953777e-2)"
+     id="polygon42"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="7.3450627"
+     y="17.691999"
+     id="text44"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">xslt/man.xsl</text>
+  <line
+     x1="8.6999998"
+     y1="13.45"
+     x2="9.658"
+     y2="16.091999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line46"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="9.785,16.445 9.38,16.06 9.658,16.092 9.85,15.89 9.785,16.445 "
+     id="polygon48"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="9.785,16.445 9.38,16.06 9.658,16.092 9.85,15.89 9.785,16.445 "
+     id="polygon50"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <g
+     id="g5595">
+    <line
+       style="stroke:#000000;stroke-width:0.1"
+       id="line52"
+       stroke-width="0.100"
+       stroke="#000000"
+       y2="21.247999"
+       x2="10.17"
+       y1="18.549999"
+       x1="9.0959997" />
+    <polygon
+       points="10.309,21.596 9.891,21.224 10.17,21.248 10.356,21.039 10.309,21.596 "
+       id="polygon54"
+       style="fill:#000000;stroke:none;stroke-width:0.1" />
+    <polygon
+       points="10.309,21.596 9.891,21.224 10.17,21.248 10.356,21.039 10.309,21.596 "
+       id="polygon56"
+       style="fill:none;stroke:#000000;stroke-width:0.1" />
+  </g>
+  <polygon
+     points="18.853,16.6 27.394,16.6 26.666,18.6 18.125,18.6 18.853,16.6 "
+     id="polygon58"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="18.853,16.6 27.394,16.6 26.666,18.6 18.125,18.6 18.853,16.6 "
+     transform="matrix(1.1478017,0,0,0.9965254,-2.9687126,6.1153121e-2)"
+     id="polygon60"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="18.508806"
+     y="17.742001"
+     id="text62"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">db2latex (xslt/latex.xsl)</text>
+  <rect
+     width="5.3000002"
+     height="1.9"
+     x="20.75"
+     y="21.549999"
+     id="rect64"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="5.7650704"
+     height="1.8958195"
+     x="20.75209"
+     y="21.55209"
+     id="rect66"
+     style="fill:none;stroke:#000000;stroke-width:0.10418041" />
+  <text
+     x="20.932089"
+     y="22.643"
+     id="text68"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">LaTeX Source</text>
+  <line
+     x1="11"
+     y1="13.55"
+     x2="22.650999"
+     y2="16.481001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line70"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="23.015,16.573 22.469,16.693 22.651,16.481 22.591,16.208 23.015,16.573 "
+     id="polygon72"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="23.015,16.573 22.469,16.693 22.651,16.481 22.591,16.208 23.015,16.573 "
+     id="polygon74"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="22.396"
+     y1="18.6"
+     x2="23.243"
+     y2="21.089001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line76"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="23.364,21.444 22.966,21.051 23.243,21.089 23.439,20.89 23.364,21.444 "
+     id="polygon78"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="23.364,21.444 22.966,21.051 23.243,21.089 23.439,20.89 23.364,21.444 "
+     id="polygon80"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="18.828,29.2 23.219,29.2 22.491,31.2 18.1,31.2 18.828,29.2 "
+     id="polygon82"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="18.828,29.2 23.219,29.2 22.491,31.2 18.1,31.2 18.828,29.2 "
+     transform="matrix(1.1760017,0,0,0.9958897,-3.1815209,0.1241298)"
+     id="polygon84"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="19.246"
+     y="30.341999"
+     id="text86"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">PDFLaTeX</text>
+  <rect
+     width="2.3"
+     height="1.9"
+     x="17"
+     y="33.849998"
+     id="rect88"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="2.3"
+     height="1.9"
+     x="17"
+     y="33.849998"
+     id="rect90"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="17.582001"
+     y="34.943001"
+     id="text92"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">PDF</text>
+  <line
+     x1="23.4"
+     y1="23.450001"
+     x2="21.209"
+     y2="28.75"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line94"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="21.066,29.097 21.026,28.539 21.209,28.75 21.488,28.73 21.066,29.097 "
+     id="polygon96"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="21.066,29.097 21.026,28.539 21.209,28.75 21.488,28.73 21.066,29.097 "
+     id="polygon98"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="20.296"
+     y1="31.200001"
+     x2="18.455999"
+     y2="33.472"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line100"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="18.22,33.763 18.341,33.217 18.456,33.472 18.729,33.532 18.22,33.763 "
+     id="polygon102"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="18.22,33.763 18.341,33.217 18.456,33.472 18.729,33.532 18.22,33.763 "
+     id="polygon104"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="13.703,16.6 17.944,16.6 17.216,18.6 12.975,18.6 13.703,16.6 "
+     id="polygon106"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="13.703,16.6 17.944,16.6 17.216,18.6 12.975,18.6 13.703,16.6 "
+     id="polygon108"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="13.54009"
+     y="17.742001"
+     id="text110"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">xslt/fo.xsl</text>
+  <line
+     x1="8.9499998"
+     y1="13.55"
+     x2="15.379"
+     y2="16.403"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line112"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="15.721,16.555 15.163,16.58 15.379,16.403 15.366,16.123 15.721,16.555 "
+     id="polygon114"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="15.721,16.555 15.163,16.58 15.379,16.403 15.366,16.123 15.721,16.555 "
+     id="polygon116"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="5.3000002"
+     height="1.9"
+     x="14.039402"
+     y="21.591343"
+     id="rect118"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="6.3466492"
+     height="1.8908348"
+     x="14.043984"
+     y="21.595926"
+     id="rect120"
+     style="fill:none;stroke:#000000;stroke-width:0.10916522" />
+  <text
+     x="14.691403"
+     y="22.683344"
+     id="text122"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">FO Document</text>
+  <polygon
+     points="15.178,29.25 17.769,29.25 17.041,31.25 14.45,31.25 15.178,29.25 "
+     id="polygon130"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="15.178,29.25 17.769,29.25 17.041,31.25 14.45,31.25 15.178,29.25 "
+     id="polygon132"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="15.537"
+     y="30.392"
+     id="text134"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">FOP</text>
+  <line
+     x1="17.1"
+     y1="23.549999"
+     x2="16.527"
+     y2="28.766001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line136"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="16.486,29.139 16.292,28.615 16.527,28.766 16.789,28.669 16.486,29.139 "
+     id="polygon138"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="16.486,29.139 16.292,28.615 16.527,28.766 16.789,28.669 16.486,29.139 "
+     id="polygon140"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="15.746"
+     y1="31.25"
+     x2="17.819"
+     y2="33.493"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line142"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="18.074,33.768 17.551,33.571 17.819,33.493 17.918,33.231 18.074,33.768 "
+     id="polygon144"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="18.074,33.768 17.551,33.571 17.819,33.493 17.918,33.231 18.074,33.768 "
+     id="polygon146"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="1.528,16.5 6.519,16.5 5.791,18.5 0.8,18.5 1.528,16.5 "
+     id="polygon148"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="1.528,16.5 6.519,16.5 5.791,18.5 0.8,18.5 1.528,16.5 "
+     transform="matrix(1.1005379,0,0,0.9976095,-0.6577968,4.1834251e-2)"
+     id="polygon150"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="1.001155"
+     y="17.642"
+     id="text152"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">xslt/html.xsl</text>
+  <rect
+     width="6.0999999"
+     height="1.9"
+     x="0.34134367"
+     y="21.700001"
+     id="rect154"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="6.0862045"
+     height="2.4659617"
+     x="0.40689769"
+     y="21.706898"
+     id="rect156"
+     style="fill:none;stroke:#000000;stroke-width:0.11379541" />
+  <line
+     x1="6.9000001"
+     y1="13.55"
+     x2="4.3629999"
+     y2="16.150999"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line160"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="4.102,16.42 4.272,15.887 4.363,16.151 4.63,16.236 4.102,16.42 "
+     id="polygon162"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="4.102,16.42 4.272,15.887 4.363,16.151 4.63,16.236 4.102,16.42 "
+     id="polygon164"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <line
+     x1="3.296"
+     y1="18.5"
+     x2="3.427"
+     y2="21.214001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line166"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="3.445,21.588 3.171,21.101 3.427,21.214 3.67,21.077 3.445,21.588 "
+     id="polygon168"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="3.445,21.588 3.171,21.101 3.427,21.214 3.67,21.077 3.445,21.588 "
+     id="polygon170"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="28.678,16.75 33.569,16.75 32.841,18.75 27.95,18.75 28.678,16.75 "
+     id="polygon172"
+     style="fill:#ffffff;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="28.678,16.75 33.569,16.75 32.841,18.75 27.95,18.75 28.678,16.75 "
+     transform="matrix(1.0511507,0,0,0.9987687,-1.0178379,2.1854741e-2)"
+     id="polygon174"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="29.027"
+     y="17.892"
+     id="text176"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">xslt/yodl.xsl</text>
+  <line
+     x1="13.05"
+     y1="13.55"
+     x2="30.643999"
+     y2="16.665001"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line178"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="31.013,16.731 30.477,16.89 30.644,16.665 30.565,16.397 31.013,16.731 "
+     id="polygon180"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="31.013,16.731 30.477,16.89 30.644,16.665 30.565,16.397 31.013,16.731 "
+     id="polygon182"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <rect
+     width="6"
+     height="1.9"
+     x="26.948059"
+     y="21.6"
+     id="rect184"
+     style="fill:#ffffff;stroke:none;stroke-width:0" />
+  <rect
+     width="6.8730097"
+     height="1.8931645"
+     x="27.303417"
+     y="21.603418"
+     id="rect186"
+     style="fill:none;stroke:#000000;stroke-width:0.10683542" />
+  <text
+     x="27.394091"
+     y="22.693001"
+     id="text188"
+     style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">YODL Document</text>
+  <line
+     x1="30.15"
+     y1="18.700001"
+     x2="30.275"
+     y2="21.114"
+     stroke="#000000"
+     stroke-width="0.100"
+     id="line190"
+     style="stroke:#000000;stroke-width:0.1" />
+  <polygon
+     points="30.294,21.488 30.019,21.002 30.275,21.114 30.518,20.976 30.294,21.488 "
+     id="polygon192"
+     style="fill:#000000;stroke:none;stroke-width:0.1" />
+  <polygon
+     points="30.294,21.488 30.019,21.002 30.275,21.114 30.518,20.976 30.294,21.488 "
+     id="polygon194"
+     style="fill:none;stroke:#000000;stroke-width:0.1" />
+  <text
+     x="3.6583791"
+     y="22.583603"
+     id="text5573"
+     xml:space="preserve"
+     style="font-size:0.82118881px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Vera Sans"><tspan
+       x="3.7890956"
+       y="22.583603"
+       id="tspan5575">HTML </tspan><tspan
+       x="3.6583791"
+       y="23.610088"
+       id="tspan5577">Document</tspan></text>
+  <text
+     x="1.0326539"
+     y="22.656073"
+     id="text5579"
+     xml:space="preserve"
+     style="font-size:40px;font-style:normal;font-weight:normal;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Vera Sans"><tspan
+       x="1.0326539"
+       y="22.656073"
+       id="tspan5581" /></text>
+  <text
+     x="10.297968"
+     y="22.32135"
+     id="text5585"
+     xml:space="preserve"
+     style="font-size:0.82118881px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Vera Sans"><tspan
+       x="10.297968"
+       y="22.32135"
+       id="tspan5587">Man pages</tspan><tspan
+       x="10.297968"
+       y="23.347836"
+       id="tspan5589">(NROFF)</tspan></text>
+  <g
+     transform="translate(6.2483064,3.7332239e-2)"
+     id="g5600">
+    <line
+       style="stroke:#000000;stroke-width:0.1"
+       id="line5602"
+       y2="21.247999"
+       x2="10.17"
+       y1="18.549999"
+       x1="9.0959997" />
+    <polygon
+       points="10.309,21.596 9.891,21.224 10.17,21.248 10.356,21.039 10.309,21.596 "
+       id="polygon5604"
+       style="fill:#000000;stroke:none;stroke-width:0.1" />
+    <polygon
+       points="10.309,21.596 9.891,21.224 10.17,21.248 10.356,21.039 10.309,21.596 "
+       id="polygon5606"
+       style="fill:none;stroke:#000000;stroke-width:0.1" />
+  </g>
+</svg>
diff --git a/docs-xml/templates/attributions.xml b/docs-xml/templates/attributions.xml
new file mode 100644
index 00000000000..281a9e51eae
--- /dev/null
+++ b/docs-xml/templates/attributions.xml
@@ -0,0 +1,5 @@
+<?xml version="1.0"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<preface>
+</preface>
+
diff --git a/docs-xml/templates/template.5.xml b/docs-xml/templates/template.5.xml
new file mode 100644
index 00000000000..9d3ce8ad09d
--- /dev/null
+++ b/docs-xml/templates/template.5.xml
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+<refentry id="lmhosts.5">
+
+<refmeta>
+	<refentrytitle>smb-idmap</refentrytitle>
+	<manvolnum>5</manvolnum>
+</refmeta>
+
+
+<refnamediv>
+	<refname>smb-idmap</refname>
+	<refpurpose>The Samba IdMap Interface</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+	<para>The IdMap interface in <citerefentry><refentrytitle>samba</refentrytitle>
+	<manvolnum>7</manvolnum></citerefentry> is responsible for 
+	mapping Windows SIDs to Unix uids/gids.</para> 
+</refsynopsisdiv>
+
+<refsect1>
+	<title>DESCRIPTION</title>
+	
+	<para>To be filled in.</para>
+</refsect1>
+
+<refsect1>
+	<title>AUTHOR</title>
+
+	<para>The original Samba software and related utilities 
+	were created by Andrew Tridgell. Samba is now developed
+	by the Samba Team as an Open Source project similar 
+	to the way the Linux kernel is developed.</para>	
+</refsect1>
+
+</refentry>
diff --git a/docs-xml/test/index.xml b/docs-xml/test/index.xml
new file mode 100644
index 00000000000..c225a08a908
--- /dev/null
+++ b/docs-xml/test/index.xml
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE book PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<book id="testdoc"
+	xmlns:xi="http://www.w3.org/2003/XInclude">
+<title>Test-document</title>
+
+<bookinfo>
+	<authorgroup>
+	<editor>&person.jelmer;</editor>
+	</authorgroup>
+	<pubdate><?latex \today ?></pubdate>
+</bookinfo>
+
+<chapter>
+	<title>Foo</title>
+
+	<para>Bar</para>
+</chapter>
+
+</book>
diff --git a/docs-xml/xslt/db2latex-xsl/AUTHOR b/docs-xml/xslt/db2latex-xsl/AUTHOR
new file mode 100644
index 00000000000..6d5543d6fcc
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/AUTHOR
@@ -0,0 +1,15 @@
+<!--############################################################################# 
+ |	$Id: AUTHOR,v 1.1.1.1 2003/03/14 10:42:51 rcasellas Exp $
+ |- #############################################################################
+ |	$Author: rcasellas $
+ |														
+ |   PURPOSE:
+ + ############################################################################## -->
+
+Ramon Casellas <casellas@aist.enst.fr>, <casellas@infres.enst.fr>
+	* Project manager and Developer.
+	* with the help of many other people <xref linkend="thanks"/> :)
+
+James Devenish <j-devenish@users.sourceforge.net> 
+	* Project manager and Developer.
+	* Patches and improvements. 
diff --git a/docs-xml/xslt/db2latex-xsl/CHANGES b/docs-xml/xslt/db2latex-xsl/CHANGES
new file mode 100644
index 00000000000..b5edb15e885
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/CHANGES
@@ -0,0 +1,2 @@
+A ChangeLog is not available for 0.8pre1 but will be present
+in the final 0.8 release.
diff --git a/docs-xml/xslt/db2latex-xsl/COPYING b/docs-xml/xslt/db2latex-xsl/COPYING
new file mode 100644
index 00000000000..a43ea2126fb
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/COPYING
@@ -0,0 +1,339 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+                          675 Mass Ave, Cambridge, MA 02139, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	Appendix: How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) 19yy  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) 19yy name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/docs-xml/xslt/db2latex-xsl/COPYRIGHT b/docs-xml/xslt/db2latex-xsl/COPYRIGHT
new file mode 100644
index 00000000000..31f9b6f32c1
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/COPYRIGHT
@@ -0,0 +1,104 @@
+<!--############################################################################# 
+ |	$Id: COPYRIGHT,v 1.3 2004/01/25 01:45:16 j-devenish Exp $
+ |- #############################################################################
+ |	$Author: j-devenish $
+ |														
+ |   PURPOSE:
+ |   DB2LaTeX is distributed according to the GPL v2 license.
+ + ############################################################################## -->
+
+<warning><para>
+IMPORTANT: These stylesheets ARE NOT the official DocBook XSL stylesheets. These stylesheets ARE NOT
+maintained by Norman Walsh. Please, DO NOT e-mail Norman about any question regarding these stylesheets
+</para></warning>
+
+**********************************************************************
+   This program is distributed in the hope that it will be useful,
+   but WITHOUT ANY WARRANTY; without even the implied warranty of
+   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+**********************************************************************
+
+
+DocBook to LaTeX XSL Transformation Stylesheets
+(c) 2000-2004 Ramon Casellas
+
+
+--------------------------------------------------------------------------------
+
+   
+FROM THE OFFICIAL XSL Docbook Stylesheets
+____________________________________________
+Copyright (C) 1999, 2000, 2001, 2002 Norman Walsh
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the ``Software''), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or
+sell copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+Except as contained in this notice, the names of individuals
+credited with contribution to this software shall not be used in
+advertising or otherwise to promote the sale, use or other
+dealings in this Software without prior written authorization
+from the individuals in question.
+
+Any stylesheet derived from this Software that is publically
+distributed will be identified with a different name and the
+version strings in any derived Software will be changed so that
+no possibility of confusion between the derived package and this
+Software will exist.
+
+Warranty
+--------
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT.  IN NO EVENT SHALL NORMAN WALSH OR ANY OTHER
+CONTRIBUTOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.
+
+ORIGINAL DOCBOOK XSL STYLESHEETS
+* Norman Walsh XSL Stylesheets http://www.nwalsh.com
+
+DOCBOOK DTD
+* Arbortex, Oasis, etc
+* See Docbook copyrigth
+
+MATHML PORTIONS
+--------------------------------------------------------------
+  Unlimited use, reproduction, and distribution of this software is
+  permitted.  Any copy of this software must include both the above
+  copyright notice of Xerox Corporation and this paragraph.  Any
+  distribution of this software must comply with all applicable United
+  States export control laws.  This software is made available AS IS,
+  and XEROX CORPORATION DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
+  INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY
+  AND FITNESS FOR A PARTICULAR PURPOSE, AND NOTWITHSTANDING ANY OTHER
+  PROVISION CONTAINED HEREIN, ANY LIABILITY FOR DAMAGES RESULTING FROM
+  THE SOFTWARE OR ITS USE IS EXPRESSLY DISCLAIMED, WHETHER ARISING IN
+  CONTRACT, TORT (INCLUDING NEGLIGENCE) OR STRICT LIABILITY, EVEN IF
+  XEROX CORPORATION IS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+  emmanuel.pietriga@xrce.xerox.com
+  This work is done for the OPERA project (INRIA) during a thesis work under a
+  CIFRE contract.
+-----------------------------------------------------------------
+
+* string-replace by David Carlisle http://www.jclark.com
+
+* xt by James Clarck http://www.jclark.com
+
+
+BUGS and MISSING FEATURES :)
+* Ramon Casellas 
+casellas@aist.enst.fr
+http://www.enst.fr/~casellas
diff --git a/docs-xml/xslt/db2latex-xsl/DOCBOOK.RFE b/docs-xml/xslt/db2latex-xsl/DOCBOOK.RFE
new file mode 100644
index 00000000000..c749ac99ed6
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/DOCBOOK.RFE
@@ -0,0 +1,8 @@
+<!--############################################################################# 
+ |	$Id: DOCBOOK.RFE,v 1.1.1.1 2003/03/14 10:42:51 rcasellas Exp $
+ |- #############################################################################
+ |	$Author: rcasellas $
+ |														
+ |   PURPOSE:
+ + ############################################################################## -->
+
diff --git a/docs-xml/xslt/db2latex-xsl/README b/docs-xml/xslt/db2latex-xsl/README
new file mode 100644
index 00000000000..cf76210f09d
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/README
@@ -0,0 +1,39 @@
+<!--############################################################################# 
+ |	$Id: README,v 1.2 2004/01/31 12:53:35 j-devenish Exp $
+ |- #############################################################################
+ |	$Author: j-devenish $
+ |														
+ |   PURPOSE:
+ + ############################################################################## -->
+
+Note
+=====================
+This file is obsolete. Please see the instructions available at the DB2LaTeX
+project website <http://db2latex.sourceforge.net/> -- a local HTML copy
+accompanies this distribution.
+
+Disclaimer
+=====================
+Documentation is *needed* and obviously very important, but bear
+in mind that it is also very boring. WYSIWID:  What you see is 
+what it's done... 
+
+Installation
+=====================
+DB2LaTeX is now a standalone product, the main driver stylesheet is docbook.xsl. 
+Process your document with your favourite (and I hope supported) XSLT engine.
+See the sample directory.
+
+Extending the stylesheets
+=========================
+XSL variables that are supposed to affect the output of the XSLT are in vars.mod.xsl
+Cfr. Norman Walsh documentation on how to extend (add a customization layer).
+
+Thanks
+=====================
+See the THANKS file
+
+Authors
+=====================
+Ramon Casellas casellas@infres.enst.fr
+James Devenish j-devenish@users.sourceforge.net
diff --git a/docs-xml/xslt/db2latex-xsl/THANKS b/docs-xml/xslt/db2latex-xsl/THANKS
new file mode 100644
index 00000000000..18acd0731e7
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/THANKS
@@ -0,0 +1,82 @@
+Without this people, DB2LaTeX would not exist:
+---------------------------------------------------
+* Norman Walsh and OASIS comitee:
+* Docbook/DSSSL/XSL/Mailing Lists contributors
+* Open Source Developers
+* David Carlisle
+* James Clark
+
+
+
+DB2LaTeX
+------------------
+The following people have contributed by sending sending patches, bug reports, suggestions or simply interesting comments.  
+Thank you.
+R.
+
+* Michel Goosens
+* James Devenish
+* Michael Wiedmann
+* Steve Fisher
+* Camille Begnis
+* Andrea Giuliano.
+* Frederic Schwebel
+* Emmanuel Pietriga
+* Benoit G/Nicolas Marsgui
+* Sebastien Blondeel
+* Olivier Dameron
+* Sebastien Schneider
+* Marco Kuhlmann
+* Raphael Goubet
+* Indrek Pehk
+* Balazs Scheider
+* Jakob VoB
+* David Nelson
+* Jirka Kosek
+* Steinar Bang
+* Vitaly Ostanin
+* Brian McGurk
+
+* Roman Kennkee roman(at)cognition(dot)uni-freiburg(dot)de 24 Feb 2003 11:50:13 +0100
+	- Patches for MathML
+
+* Ralph Meijer rmeijer(at)users(dot)sourceforge(dot)net 12 Mar 2003 12:01:30 +0100
+	- Bug report : mediaobject is not processed according to DocBook guidelines.
+	- Submitted patch for mediaobject.mod.xsl
+
+* Stephane Bortzmeyer 13 Mar 2003
+	- Bug reports
+	- Patch for qanda.mod.xsl 
+
+* Jan Pavlovic 02 Avr 2003
+	- Bug reports and Suggestions
+	- Suggested the use of textbackslash
+	- Suggested a new processing for lot. Now you can use the @label to output only tables, figures or both
+	- graphic.default.extension is now honoured.
+	- added support for child::editor and others in biblio.
+	- Index terms are now scaped.
+	- updated keywordset so now it uses latex.mapping
+    - added xsl template for keyword
+	- added xsl template for inlineequation
+	- keywords are now processed in bookinfo
+
+* Thomas Schraitle (tom_schr) 14 Avr 2003
+	- Submitted patch for indexterm.
+
+* Michael Wiedmann <mw(at)miwie(dot)in-berlin(dot)de>  14 Avr 2003 and beyond
+	- Bug Reports concerning authorgroup/author articleinfo and incorrect title in preface processing.
+	- Useful comments.
+	- Patches.
+	- 'Contrib' templates.
+	- Gentext localisation strings.
+
+* Florence HENRY <Florence(dot)Henry(at)obspm(dot)fr> 7 Oct 2003
+	- Several LaTeX suggestions.
+	- Help with colsep.
+
+* LEGUEDOIS, Frederic <F.LEGUEDOIS(at)OBERTHURCS(dot)com>
+	- Bug report in xsl/common/common.xsl regarding count() and has.ext with saxon.
+
+* Cesar A. R. Crusius <cesarcrusius(at)earthlink(dot)net> 3 Nov 2003
+	- Some new MathML templates.
+
diff --git a/docs-xml/xslt/db2latex-xsl/TODO b/docs-xml/xslt/db2latex-xsl/TODO
new file mode 100644
index 00000000000..0c5327780ca
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/TODO
@@ -0,0 +1,77 @@
+<!--############################################################################# 
+ |	$Id: TODO,v 1.11 2003/06/29 08:31:10 j-devenish Exp $
+ |- #############################################################################
+ |	$Author: j-devenish $
+ |														
+ |   PURPOSE:
+ + ############################################################################## -->
+
+SHORT
+
+20030418 - JD 
+	* Hyperlinks in QandA
+	* Support for regular typeface characterset within verbatim (for literallayout
+	  support -- see test_article).
+	* Fix \maketitle to reduce space waste in articles.
+
+20030418 - RCAS 
+	* Refactor code regarding authors and authorgroups in a single named tempalte.
+	* Test articles in books   -> book/article and the author/authorgroup prcessing
+	* Start support por partinfos/chapterinfos and to be able to output a ToC per
+	  part / chapter ...
+
+200303XX - JD
+	* There also needs to be some way of handling character entities like
+	&mdash; (or their Unicode equivalents).  It is a pity that XPath
+	doesn't have functions for regular expression substitution.
+
+	* Tables, tables, tables, always tables... Anyone?
+	* Bibliography 
+		* bibliomixed is not supported
+		* Manage .bst files ?
+
+	* Qanda is not supported at all (but patch supplied by S.B. 13 Mar 2003)
+		RCAS: Added basic support.
+			A QandASet has several QandADivs that have several QandAEntries.
+			See xsl/sample/test_qanda
+
+	* Math
+		* Improve support for MathElems tags (customized DTD)
+		* Improve support for tm and inlinetm (embedded LaTeX Math)
+		* Start MathML support
+	* Lists
+		* Ordered lists are mapped to enumerate, regardless of 'continues'
+
+	* Index : basic support. Only ONE index per LaTeX Document.
+		Support for several see/seealso
+
+	* Footnote: if possible, improve upon the existing \catcode kludge
+		for \urls within \footnotes.
+
+	* Tables/figures: look into whether page-spanning floats are possible
+		when using two-column <article>s. Add Q&A about this.
+
+LONG
+	* Update localisation.
+
+	* Overhaul handling of titles.
+
+	* Index support.
+
+	* Add chunking, so each chapter/part/etc... is created on a separate .tex file
+	  and manage the \input. (Also: automation of cover file generation.)
+
+		RCAS: Done. See xsl/sample/chunking
+		Depends on Norman Walsh chunker.xsl.
+
+	* Document latex.* variables (see vars.mod.xsl).
+
+	* Better support of everything :)
+
+	* Package.. rpm/deb/tgz 
+		RCAS: rpm & tar.gz ok.
+		RCAS: .deb pending (check debian mailing lists for a mantainer.)
+
+	* Add autoconf/automake 
+		* Detect jdk if required.
+		* Detect xslt processors.
diff --git a/docs-xml/xslt/db2latex-xsl/VERSION b/docs-xml/xslt/db2latex-xsl/VERSION
new file mode 100644
index 00000000000..ecc00bbb6ff
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/VERSION
@@ -0,0 +1 @@
+0.8pre1
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/VERSION.xml b/docs-xml/xslt/db2latex-xsl/xsl/VERSION.xml
new file mode 100644
index 00000000000..2e71a6b9685
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/VERSION.xml
@@ -0,0 +1,24 @@
+<?xml version='1.0'?>
+<!--############################################################################# 
+ |	$Id: VERSION.xml,v 1.6 2004/01/31 12:47:11 j-devenish Exp $
+ |- #############################################################################
+ |	$Author: j-devenish $
+ |														
+ |   PURPOSE:
+ + ############################################################################## -->
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'>
+<xsl:variable name="VERSION">0.8pre1</xsl:variable>
+<xsl:variable name="LASTRELEASE">0.7</xsl:variable>
+<xsl:variable name="TAG">
+  <xsl:variable name="RCSTAG" select="substring-before(substring-after('$Name: DB2LATEX_0_8PRE1 $',concat('$','Name: ')),'$')"/>
+  <xsl:choose>
+    <xsl:when test="normalize-space($RCSTAG)=''">HEAD</xsl:when>
+    <xsl:otherwise><xsl:value-of select="$RCSTAG" /></xsl:otherwise>
+  </xsl:choose>
+</xsl:variable>
+<xsl:variable name="CVSVERSION">$Id: VERSION.xml,v 1.6 2004/01/31 12:47:11 j-devenish Exp $</xsl:variable>
+
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/abstract.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/abstract.mod.xsl
new file mode 100644
index 00000000000..995930d1b91
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/abstract.mod.xsl
@@ -0,0 +1,87 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: abstract.mod.xsl,v 1.12 2003/12/30 13:38:04 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="abstract" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: abstract.mod.xsl,v 1.12 2003/12/30 13:38:04 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.6">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Abstracts <filename>abstract.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>abstract.mod.xsl</filename> contains the
+			XSL template for <doc:db>abstract</doc:db>.</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template basename="abstract" match="abstract" xmlns="">
+		<refpurpose>Process <doc:db>abstract</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Uses the &latex; <function condition='env'>abstract</function> environment
+				to format <quote>abstracts</quote> as blocks.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>Currently, the <doc:db>title</doc:db> is not honoured.</para>
+			<para>The &db2latex; template for <doc:db>abstract</doc:db> is intended for use with <doc:db>article</doc:db> and <doc:db>book</doc:db>, only.</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_book;
+				&test_ddh;
+				&test_ieeebiblio;
+				&test_varioref;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="abstract">
+		<xsl:variable name="keyword">
+			<xsl:value-of select="local-name(.)"/>
+			<xsl:if test="title">
+				<!-- choose a different mapping -->
+				<xsl:text>-title</xsl:text>
+			</xsl:if>
+		</xsl:variable>
+		<xsl:call-template name="map.begin">
+			<xsl:with-param name="keyword" select="$keyword"/>
+		</xsl:call-template>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end">
+			<xsl:with-param name="keyword" select="$keyword"/>
+		</xsl:call-template>
+	</xsl:template>
+
+</xsl:stylesheet>
+
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/admonition.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/admonition.mod.xsl
new file mode 100644
index 00000000000..c42f040d9c9
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/admonition.mod.xsl
@@ -0,0 +1,283 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: admonition.mod.xsl,v 1.14 2004/01/03 09:48:34 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference name="admonition" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: admonition.mod.xsl,v 1.14 2004/01/03 09:48:34 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.6">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Admonitions <filename>admonition.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			&DocBook; includes admonitions (<doc:db>warning</doc:db>,
+			<doc:db>tip</doc:db>, <doc:db>important</doc:db>,
+			<doc:db>caution</doc:db>, <doc:db>note</doc:db>), which are set off
+			from the main text. &DB2LaTeX; places these in the normal text flow
+			but surrounds them with a box border.
+			
+			</para>
+			<doc:variables>
+				<itemizedlist>
+					<listitem><simpara><xref linkend="param.latex.use.fancybox"/></simpara></listitem>
+					<listitem><simpara><xref linkend="param.admon.graphics.path"/></simpara></listitem>
+					<listitem><simpara><xref linkend="param.latex.admonition.imagesize"/></simpara></listitem>
+					<listitem><simpara><xref linkend="param.latex.apply.title.templates.admonitions"/></simpara></listitem>
+				</itemizedlist>
+			</doc:variables>
+		</partintro>
+	</doc:reference>
+
+	<doc:param xmlns="">
+		<refpurpose>
+			Declares a new environment to be used for admonitions
+		</refpurpose>
+		<doc:description>
+			<para>
+
+			This &LaTeX; environment is emitted during the preamble. That
+			environment has two mandatory parameters. Instances of the
+			environment are customised for each admonition via those
+			parameters. Instances will be typeset as boxed areas in the
+			document flow.
+
+			</para>
+			<para>
+
+			The first argument is the filename for graphics (e.g.
+			<filename>$admon.graphics.path/warning</filename>).
+			The second argument is the admonition title or the associated
+			generic text.
+
+			</para>
+
+			<example>
+				<title>Processing the <doc:db>warning</doc:db> admonition</title>
+				<para> When processing the admonition, the following code is generated: </para>
+				<programlisting>
+				<![CDATA[\begin{admonition}{figures/warning}{My WARNING}
+...
+\end{admonition}]]>
+				</programlisting>
+			</example>
+		</doc:description>
+		<doc:notes>
+			<!-- notes about spacing? -->
+			<para>
+				The environment uses graphics by default. This may generate errors or warnings
+				if &LaTeX; cannot find the graphics. If necessary, graphics may be disabled
+				via <xref linkend="param.admon.graphics.path"/>.
+			</para>
+		</doc:notes>
+		<!--
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.para"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+		-->
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.fancybox"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.admon.graphics.path"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.admonition.imagesize"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+	</doc:param>
+
+	<xsl:param name="latex.admonition.environment">
+		<xsl:text>% ----------------------------------------------&#10;</xsl:text>
+		<xsl:text>% Define a new LaTeX environment (adminipage)&#10;</xsl:text>
+		<xsl:text>% ----------------------------------------------&#10;</xsl:text>
+		<xsl:text>\newenvironment{admminipage}%&#10;</xsl:text>
+		<xsl:text>{ % this code corresponds to the \begin{adminipage} command&#10;</xsl:text>
+		<xsl:text> \begin{Sbox}%&#10;</xsl:text>
+		<xsl:text> \begin{minipage}%&#10;</xsl:text>
+		<xsl:text>} %done&#10;</xsl:text>
+		<xsl:text>{ % this code corresponds to the \end{adminipage} command&#10;</xsl:text>
+		<xsl:text> \end{minipage}&#10;</xsl:text>
+		<xsl:text> \end{Sbox}&#10;</xsl:text>
+		<xsl:text> \fbox{\TheSbox}&#10;</xsl:text>
+		<xsl:text>} %done&#10;</xsl:text>
+		<xsl:text>% ----------------------------------------------&#10;</xsl:text>
+		<xsl:text>% Define a new LaTeX length (admlength)&#10;</xsl:text>
+		<xsl:text>% ----------------------------------------------&#10;</xsl:text>
+		<xsl:text>\newlength{\admlength}&#10;</xsl:text>
+		<xsl:text>% ----------------------------------------------&#10;</xsl:text>
+		<xsl:text>% Define a new LaTeX environment (admonition)&#10;</xsl:text>
+		<xsl:text>% With 2 parameters:&#10;</xsl:text>
+		<xsl:text>% #1 The file (e.g. note.pdf)&#10;</xsl:text>
+		<xsl:text>% #2 The caption&#10;</xsl:text>
+		<xsl:text>% ----------------------------------------------&#10;</xsl:text>
+		<xsl:text>\newenvironment{admonition}[2] &#10;</xsl:text>
+		<xsl:text>{ % this code corresponds to the \begin{admonition} command&#10;</xsl:text>
+		<xsl:text> \hspace{0mm}\newline\hspace*\fill\newline&#10;</xsl:text>
+		<xsl:text> \noindent&#10;</xsl:text>
+		<xsl:text> \setlength{\fboxsep}{5pt}&#10;</xsl:text>
+		<xsl:text> \setlength{\admlength}{\linewidth}&#10;</xsl:text>
+		<xsl:text> \addtolength{\admlength}{-10\fboxsep}&#10;</xsl:text>
+		<xsl:text> \addtolength{\admlength}{-10\fboxrule}&#10;</xsl:text>
+		<xsl:text> \admminipage{\admlength}&#10;</xsl:text>
+		<xsl:text> {\bfseries \sc\large{#2}}</xsl:text>
+		<xsl:text> \newline&#10;</xsl:text>
+		<xsl:text> \\[1mm]&#10;</xsl:text>
+		<xsl:text> \sffamily&#10;</xsl:text>
+		<!--
+		If we cannot find the admon.graphics.path;
+		Comment out the next line (\includegraphics).
+		This tactic is to avoid deleting the \includegraphics
+		altogether, as that could confuse a person trying to
+		find the use of parameter #1 in the environment.
+		-->
+		<xsl:if test="$admon.graphics.path=''">
+			<xsl:text>%</xsl:text>
+		</xsl:if>
+		<xsl:text> \includegraphics[</xsl:text> <xsl:value-of select="$latex.admonition.imagesize" /> <xsl:text>]{#1}&#10;</xsl:text>
+		<xsl:text> \addtolength{\admlength}{-1cm}&#10;</xsl:text>
+		<xsl:text> \addtolength{\admlength}{-20pt}&#10;</xsl:text>
+		<xsl:text> \begin{minipage}[lt]{\admlength}&#10;</xsl:text>
+		<xsl:text> \parskip=0.5\baselineskip \advance\parskip by 0pt plus 2pt&#10;</xsl:text>
+		<xsl:text>} %done&#10;</xsl:text>
+		<xsl:text>{ % this code corresponds to the \end{admonition} command&#10;</xsl:text>
+		<xsl:text> \vspace{5mm} &#10;</xsl:text>
+		<xsl:text> \end{minipage}&#10;</xsl:text>
+		<xsl:text> \endadmminipage&#10;</xsl:text>
+		<xsl:text> \vspace{.5em}&#10;</xsl:text>
+		<xsl:text> \par&#10;</xsl:text>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:param>
+
+	<doc:template xmlns="">
+		<refpurpose> Choose an admonition graphic </refpurpose>
+		<doc:description>
+			<para>
+
+			For each admonition element
+			(<doc:db>warning</doc:db>, <doc:db>tip</doc:db>, <doc:db>important</doc:db>, <doc:db>caution</doc:db>, <doc:db>note</doc:db>),
+			this template chooses the graphics filename. If the admonition element is
+			not known, the <doc:db>note</doc:db> graphic is used.
+
+			</para>
+		</doc:description>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>name</term>
+					<listitem>
+						<para>
+
+							The name of the adminition. &DB2LaTeX; includes
+							different graphics for different adminitions. By
+							default, <literal>name</literal> defaults to the
+							XSLT <function
+							condition="xslt">local-name</function> of the
+							current node.
+
+						</para>
+					</listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+	</doc:template>
+
+	<xsl:template name="admon.graphic">
+		<xsl:param name="name" select="local-name(.)"/>
+		<xsl:choose>
+			<xsl:when test="$name='note'">note</xsl:when>
+			<xsl:when test="$name='warning'">warning</xsl:when>
+			<xsl:when test="$name='caution'">caution</xsl:when>
+			<xsl:when test="$name='tip'">tip</xsl:when>
+			<xsl:when test="$name='important'">important</xsl:when>
+			<xsl:otherwise>note</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Process admonitions </refpurpose>
+		<doc:description>
+			<para>
+
+			Invokes the environment provided by <xref
+			linkend="param.latex.admonition.environment"/>
+			and applies templates.
+
+			</para>
+			<note><para>An admonition will look something like this <doc:db>note</doc:db>.</para></note>
+		</doc:description>
+		<doc:notes>
+			<para>
+
+			There can be <quote>excessive</quote> whitespace between
+			the bottom of the admonition area and a subsequent paragraph.
+
+			</para>
+		</doc:notes>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.admon.graphics.path"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.apply.title.templates.admonitions"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_adm;
+				&test_bind;
+				&test_book;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><para>&mapping;</para></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+
+	<xsl:template match="note|important|warning|caution|tip">
+		<xsl:call-template name="map.begin">
+			<xsl:with-param name="keyword">admonition</xsl:with-param>
+			<xsl:with-param name="string">
+				<xsl:text>{</xsl:text>
+				<xsl:value-of select="$admon.graphics.path"/><xsl:text>/</xsl:text>
+				<xsl:call-template name="admon.graphic"/>
+				<xsl:text>}{</xsl:text>
+				<xsl:choose>
+					<xsl:when test="title and $latex.apply.title.templates.admonitions='1'">
+						<xsl:call-template name="extract.object.title">
+							<xsl:with-param name="object" select="."/>
+						</xsl:call-template>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:call-template name="gentext.element.name"/>
+					</xsl:otherwise>
+				</xsl:choose>
+				<xsl:text>}</xsl:text>
+			</xsl:with-param>
+		</xsl:call-template>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end">
+			<xsl:with-param name="keyword">admonition</xsl:with-param>
+		</xsl:call-template>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/authorgroup.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/authorgroup.mod.xsl
new file mode 100644
index 00000000000..3c625d3d1b8
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/authorgroup.mod.xsl
@@ -0,0 +1,218 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: authorgroup.mod.xsl,v 1.10 2003/12/30 13:38:54 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $												
++ ############################################################################## -->
+
+<xsl:stylesheet 
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="authorgroup" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: authorgroup.mod.xsl,v 1.10 2003/12/30 13:38:54 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.6">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Authorgroups <filename>authorgroup.mod.xsl</filename></title>
+		<partintro>
+ 			<para>The file <filename>authorgroup.mod.xsl</filename> contains the
+ 			XSL templates for <doc:db>author</doc:db>, <doc:db>editor</doc:db>,
+ 			<doc:db>othercredit</doc:db><doc:db>personname</doc:db>, <doc:db>authorblurb</doc:db>,
+ 			<doc:db>authorgroup</doc:db> and <doc:db>authorinitials</doc:db>.</para>
+			<section>
+				<title>Pertinent Variables</title>
+				<itemizedlist>
+					<listitem><simpara><xref linkend="param.biblioentry.item.separator"/></simpara></listitem>
+				</itemizedlist>
+			</section>
+		</partintro>
+	</doc:reference>
+
+	<doc:template basename="authorgroup" xmlns="">
+		<refpurpose>Process <doc:db>authorgroup</doc:db> elements</refpurpose>
+		<doc:description>
+ 			<para>
+				Formats a list of authors for typsetting as a formatted block
+				(not inline).
+ 			</para>
+			<para>
+				Applies templates for <doc:db>author</doc:db> elements,
+				inserting <quote>and</quote> between authors' names.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>person.list</term>
+					<listitem>
+						<para>
+
+							The nodes to be formatted. By default, the template
+							will select child::author, child::corpauthor,
+							child::othercredit and child::editor for the
+							current node.
+
+						</para>
+					</listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+ 			<para>
+
+ 				May be called from any template when the current node has
+ 				<doc:db>author</doc:db>, <doc:db>editor</doc:db>,
+ 				<doc:db>corpauthor</doc:db> or <doc:db>othercredit</doc:db> children.
+
+ 			</para>
+ 			<para>
+
+				This template uses <function
+				condition='xslt'>person.name.list</function> from
+				<filename>db2latex/xsl/common/common.xsl</filename> to format
+				the list of authors.
+
+			</para>
+ 
+ 			<para>
+			
+				For compatibility with &latex;, <xref
+				linkend="template.normalize-scape"/> is called on the output of
+				<function condition='xslt'>person.name.list</function>.
+				<doc:todo>This may pose problems but has not been
+				investigated.</doc:todo>
+			
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_biblio;
+				&test_bind;
+				&test_book;
+				&test_ieeebiblio;
+				&test_minimal;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+
+	<xsl:template match="authorgroup" name="authorgroup">
+		<xsl:param name="person.list" select="./author|./corpauthor|./othercredit|./editor"/>
+		<xsl:call-template name="normalize-scape">
+			<xsl:with-param name="string">
+				<xsl:call-template name="person.name.list">
+					<xsl:with-param name="person.list" select="$person.list"/>
+				</xsl:call-template>
+			</xsl:with-param>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process names of <doc:db>authors</doc:db> and similar elements</refpurpose>
+		<doc:description>
+			<para>
+
+				Formats a person's name for inline display.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+
+			<para>
+			
+			This template uses <function
+			condition='xslt'>person.name</function> from
+			<filename>db2latex/xsl/common/common.xsl</filename> to format the
+			names of <doc:db>author</doc:db>, <doc:db>editor</doc:db>,
+			<doc:db>othercredit</doc:db> and <doc:db>personname</doc:db>
+			elements.
+			
+			</para>
+
+ 			<para>
+			
+				For compatibility with &latex;, <xref
+				linkend="template.normalize-scape"/> is called on the output of
+				<function condition='xslt'>person.name.list</function>.
+				<doc:todo>This may pose problems but has not been
+				investigated.</doc:todo>
+			
+			</para>
+
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				<member>See <xref linkend="template.authorgroup"/>.</member>
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+
+	<xsl:template match="author|editor|othercredit|personname">
+		<xsl:call-template name="normalize-scape">
+			<xsl:with-param name="string">
+				<xsl:call-template name="person.name"/>
+			</xsl:with-param>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template basename="authorinitials" xmlns="">
+		<refpurpose>Process <doc:db>authorinitials</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+
+				Represents <doc:db>authorinitials</doc:db> by applying templates
+				normally and then appending <xref
+				linkend="param.biblioentry.item.separator"/>.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.biblioentry.item.separator"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+			<doc:todo>The use of <xref linkend="param.biblioentry.item.separator"/>
+			should be replaced with the normal localisation mechanism.</doc:todo>
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_article;
+				&test_ieeebiblio;
+				&test_minimal;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+
+	<xsl:template match="authorinitials">
+		<xsl:apply-templates/>
+		<xsl:value-of select="$biblioentry.item.separator"/>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/biblio.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/biblio.mod.xsl
new file mode 100644
index 00000000000..a1da6ce9249
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/biblio.mod.xsl
@@ -0,0 +1,1069 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: biblio.mod.xsl,v 1.21 2004/01/26 08:57:46 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+    <doc:reference id="biblio" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: biblio.mod.xsl,v 1.21 2004/01/26 08:57:46 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.16">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Bibliographies <filename>biblio.mod.xsl</filename></title>
+		<partintro>
+
+			<para>The file <filename>biblio.mod.xsl</filename> contains the XSL
+			template for <doc:db>bibliography</doc:db> and associated
+			elements.</para>
+
+			<!--
+		<para>This reference describes the templates and parameters relevant
+		    to formatting DocBook bibliography markup.</para>
+			-->
+
+			<bridgehead><quote>All</quote> versus <quote>cited</quote> mode</bridgehead>
+				<note>
+					<para>These modes are superseded by &BibTeX;
+					when using &BibTeX;.</para>
+				</note>
+				<para>
+
+				The <xref linkend="param.latex.biblio.output"/> option can be used
+				to select <quote>all</quote> mode or <quote>cited</quote> mode.
+				With the <quote>cited</quote> mode, only the <doc:db
+				basename="biblioentry">biblioentries</doc:db> that have been
+				cited somewhere in the document are output. Otherwise (in
+				<quote>all</quote> mode) all biblioentries found are output (as
+				the HTML stylesheets do).
+
+				</para>
+
+			<bridgehead>&DocBook; versus &BibTeX;</bridgehead>
+				<para>
+					
+					&DB2LaTeX; supports &BibTeX;. When this mode is enabled,
+					you can use a &BibTeX; citations file. Your <doc:db
+					basename="citation">citations</doc:db> can then refer to
+					your &BibTeX; keys (<doc:db basename="xref">xrefs</doc:db>
+					are unlikely to work, though). You will need to provide a
+					&LaTeX; command to select a bibliographic citation style as
+					is normal for &BibTeX; (see <xref
+					linkend="bibtex.example"/>). You must also run the
+					<command>bibtex</command> command when typesetting your
+					document with &LaTeX;.
+					
+				</para>
+				<note>
+					<para>Although &DocBook; allows <doc:db basename="bibliography">bibliographies</doc:db>
+					within a number of components, such as <doc:db>section</doc:db>, the use of &BibTeX;
+					is only useful for a single, chapter-level bibliography.</para>
+				</note>
+				<para>
+
+					To enable &BibTeX; mode, insert an empty
+					<doc:db>bibliography</doc:db> element in your &DocBook;
+					document. However, note that this is not valid &DocBook;,
+					though it will lead to the desired results with most
+					&DocBook; XSL stylesheets (including those for HTML).
+					You will also need to set the <xref linkend="param.latex.bibfiles"/>
+					variable to the correct path of your &BibTeX; citations file.
+
+					Alternatively, you may choose to use a processing
+					instruction named <quote>bibtex-bibliography</quote>
+					instead of an empty element. The name of the citations file
+					may be specified within the processing instruction or via
+					<xref linkend="param.latex.bibfiles"/> (see
+					<xref linkend="bibtex.example"/>).
+
+				</para>
+				<example id="bibtex.example">
+					<title>Using &BibTeX; with &DB2LaTeX;</title>
+					<para>
+
+						A &BibTeX; bibliography may be enabled by providing the
+						name of your citations file, the name of a &BibTeX; style,
+						and the insertion of an appropriate node in your
+						&DocBook; document. In your customisation layer:
+
+					<programlisting><![CDATA[
+<xsl:variable name="latex.book.preamble.post">
+% Your LaTeX customisation commands
+\bibliographystyle{ieeetr}
+</xsl:variable>
+<xsl:variable name="latex.bibfiles" select="'../citations.bib'"/>
+]]></programlisting>
+
+						Then, in your document, type this:
+
+					<programlisting><![CDATA[
+<bibliography/>
+]]></programlisting>
+
+						Although this is not valid according to the &DocBook;
+						DTD, it will work with most stylesheets (not just
+						&DB2LaTeX;). Alternatively, you may instead use a
+						processing instruction in compliance with the DTD,
+						though this will work only with &DB2LaTeX; and you will
+						not be able to specify a custom <doc:db>title</doc:db>
+						for your bibliography:
+
+					<programlisting><![CDATA[
+<?bibtex-bibliography?>
+]]></programlisting>
+
+						You may optionally specify the citations file directly
+						(you will not need to set
+						<literal>latex.bibfiles</literal>):
+
+					<programlisting><![CDATA[
+<?bibtex-bibliography ../citations.bib?>
+]]></programlisting>
+
+					</para>
+				</example>
+
+			<doc:variables>
+				<itemizedlist>
+					<listitem><simpara><xref linkend="param.latex.bibfiles"/></simpara></listitem>
+					<listitem><simpara><xref linkend="param.latex.biblio.output"/></simpara></listitem>
+				</itemizedlist>
+			</doc:variables>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose> Essential preamble for <filename>biblio.mod.xsl</filename> support </refpurpose>
+		<doc:description>
+			<para>
+
+				Defines <function condition="latex">docbooktolatexbibname</function>,
+				<function condition="latex">docbooktolatexbibaux</function>
+				and <function condition="env">docbooktolatexbibliography</function>.
+
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&preamble;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+
+	<xsl:template name="latex.preamble.essential.biblio">
+		<xsl:text>
+			<![CDATA[
+\AtBeginDocument{\ifx\refname\@undefined\let\docbooktolatexbibname\bibname\def\docbooktolatexbibnamex{\bibname}\else\let\docbooktolatexbibname\refname\def\docbooktolatexbibnamex{\refname}\fi}
+% Facilitate use of \cite with \label
+\newcommand{\docbooktolatexbibaux}[2]{%
+  \protected@write\@auxout{}{\string\global\string\@namedef{docbooktolatexcite@#1}{#2}}
+}
+% Provide support for bibliography `subsection' environments with titles
+\newenvironment{docbooktolatexbibliography}[3]{
+   \begingroup
+   \let\save@@chapter\chapter
+   \let\save@@section\section
+   \let\save@@@mkboth\@mkboth
+   \let\save@@bibname\bibname
+   \let\save@@refname\refname
+   \let\@mkboth\@gobbletwo
+   \def\@tempa{#3}
+   \def\@tempb{}
+   \ifx\@tempa\@tempb
+      \let\chapter\@gobbletwo
+      \let\section\@gobbletwo
+      \let\bibname\relax
+   \else
+      \let\chapter#2
+      \let\section#2
+      \let\bibname\@tempa
+   \fi
+   \let\refname\bibname
+   \begin{thebibliography}{#1}
+}{
+   \end{thebibliography}
+   \let\chapter\save@@chapter
+   \let\section\save@@section
+   \let\@mkboth\save@@@mkboth
+   \let\bibname\save@@bibname
+   \let\refname\save@@refname
+   \endgroup
+}
+]]>
+		</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="bibliography" xmlns="">
+		<refpurpose>Process <doc:db>bibliography</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				This is a complex template that can format bibliographies as
+				chapter-level or section-level components.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.biblio.output"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.bibwidelabel"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>makechapter</term>
+					<listitem>
+						<para>
+
+							Whether to make a chapter-level bibliography or
+							not. This is normally determined by examining
+							whether the <doc:db>bibliography</doc:db> element
+							occurs as a child of a <doc:db>book</doc:db> or
+							<doc:db>part</doc:db>. If so, the bibliography will
+							be formatted as an unnumbered chapter. If not, the
+							bibliography will be formatted as an unnumbered
+							section. This effect does not hold for &BibTeX;
+							bibliographies, which will be formatted by the
+							&LaTeX; <function
+							condition="latex">bibliography</function> command.
+
+						</para>
+					</listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>This template probably contains many bugs.</para>
+			&essential_preamble;
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_biblio;
+				&test_bind;
+				&test_book;
+				&test_cited;
+				&test_ieeebiblio;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;: this template will use the <literal>bibliography-chapter</literal>
+				and <literal>bibliography-section</literal> mappings.</simpara></listitem>
+				<listitem><simpara><xref linkend="citation"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="bibliography">
+		<xsl:param name="makechapter" select="local-name(..)='book' or local-name(..)='part'"/>
+		<xsl:variable name="keyword">
+			<xsl:choose>
+				<xsl:when test="$makechapter">
+					<xsl:text>bibliography-chapter</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>bibliography-section</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:variable name="environment">
+			<xsl:choose>
+				<xsl:when test="$makechapter">thebibliography</xsl:when>
+				<xsl:otherwise>docbooktolatexbibliography</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:variable name="title">
+			<xsl:apply-templates select="title|subtitle"/>
+		</xsl:variable>
+		<!--
+		<xsl:message>DB2LaTeX: Processing BIBLIOGRAPHY</xsl:message>
+		-->
+		<xsl:if test="$title!=''">
+			<xsl:text>\let\oldbibname\bibname&#10;</xsl:text>
+			<xsl:text>\let\oldrefname\refname&#10;</xsl:text>
+			<xsl:text>\def\bibname{</xsl:text>
+			<xsl:value-of select="$title"/>
+			<xsl:text>}&#10;</xsl:text>
+			<xsl:text>\let\refname\bibname&#10;</xsl:text>
+		</xsl:if>
+		<xsl:call-template name="map.begin">
+			<xsl:with-param name="keyword" select="$keyword"/>
+		</xsl:call-template>
+		<xsl:choose>
+			<xsl:when test="biblioentry or bibliodiv">
+				<xsl:variable name="separatetitle" select="not(biblioentry or bibliodiv[1]/@title)"/>
+				<xsl:message>DB2LaTeX: Bibliographic Output Mode :  <xsl:value-of select="$latex.biblio.output"/></xsl:message>
+				<xsl:choose>
+					<xsl:when test="$separatetitle and $makechapter">
+						<xsl:text>\chapter*{\docbooktolatexbibnamex}\hypertarget{</xsl:text>
+						<xsl:call-template name="generate.label.id"/>
+						<xsl:text>}{}&#10;</xsl:text>
+					</xsl:when>
+					<xsl:when test="$separatetitle and not($makechapter)">
+						<xsl:text>\section*{\docbooktolatexbibnamex}\hypertarget{</xsl:text>
+						<xsl:call-template name="generate.label.id"/>
+						<xsl:text>}{}&#10;</xsl:text>
+					</xsl:when>
+					<xsl:when test="biblioentry"><!-- implies not($separatetitle) -->
+						<xsl:text>\begin{</xsl:text>
+						<xsl:value-of select="$environment"/>
+						<xsl:text>}{</xsl:text>
+						<xsl:value-of select="$latex.bibwidelabel"/>
+						<xsl:if test="$environment='docbooktolatexbibliography'">
+							<xsl:text>}{\</xsl:text>
+							<!-- TODO choose the correct nesting, rather than assuming something -->
+							<xsl:choose>
+								<xsl:when test="$makechapter">chapter</xsl:when>
+								<xsl:otherwise>section</xsl:otherwise>
+							</xsl:choose>
+							<xsl:text>}{</xsl:text>
+							<xsl:choose>
+								<xsl:when test="$title!=''">
+									<xsl:value-of select="$title"/>
+								</xsl:when>
+								<xsl:otherwise>
+									<xsl:text>\docbooktolatexbibname</xsl:text>
+								</xsl:otherwise>
+							</xsl:choose>
+						</xsl:if>
+						<xsl:text>}\hypertarget{</xsl:text>
+						<xsl:call-template name="generate.label.id"/>
+						<xsl:text>}{}&#10;</xsl:text>
+						<xsl:choose>
+							<xsl:when test="$latex.biblio.output ='cited'">
+								<xsl:apply-templates select="biblioentry" mode="bibliography.cited">
+									<xsl:sort select="./abbrev"/>
+									<xsl:sort select="./@xreflabel"/>
+									<xsl:sort select="./@id"/>
+								</xsl:apply-templates>
+							</xsl:when>
+							<xsl:when test="$latex.biblio.output ='all'">
+								<xsl:apply-templates select="biblioentry" mode="bibliography.all">
+									<xsl:sort select="./abbrev"/>
+									<xsl:sort select="./@xreflabel"/>
+									<xsl:sort select="./@id"/>
+								</xsl:apply-templates>
+							</xsl:when>
+							<xsl:otherwise>
+								<xsl:apply-templates select="biblioentry">
+									<xsl:sort select="./abbrev"/>
+									<xsl:sort select="./@xreflabel"/>
+									<xsl:sort select="./@id"/>
+								</xsl:apply-templates>
+							</xsl:otherwise>
+						</xsl:choose>
+						<!-- <xsl:apply-templates select="child::*[name(.)!='biblioentry']"/>  -->
+						<xsl:text>&#10;\end{</xsl:text>
+						<xsl:value-of select="$environment"/>
+						<xsl:text>}&#10;</xsl:text>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:text>\hypertarget{</xsl:text>
+						<xsl:call-template name="generate.label.id"/>
+						<xsl:text>}{}&#10;</xsl:text>
+					</xsl:otherwise>
+				</xsl:choose>
+				<xsl:apply-templates select="bibliodiv"/>
+			</xsl:when>
+			<xsl:when test="child::*">
+				<xsl:choose>
+					<xsl:when test="$makechapter">
+						<xsl:text>\chapter*</xsl:text>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:text>\section*</xsl:text>
+					</xsl:otherwise>
+				</xsl:choose>
+				<xsl:text>{\docbooktolatexbibnamex}\hypertarget{</xsl:text>
+				<xsl:call-template name="generate.label.id"/>
+				<xsl:text>}{}&#10;</xsl:text>
+				<xsl:call-template name="content-templates"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>% Assume that an empty &lt;bibliography&gt; means ``use BibTeX'' or similar.&#10;</xsl:text>
+				<xsl:text>\bibliography{</xsl:text><xsl:value-of select="$latex.bibfiles"/><xsl:text>}&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:call-template name="map.end">
+			<xsl:with-param name="keyword" select="$keyword"/>
+		</xsl:call-template>
+		<xsl:if test="$title!=''">
+			<xsl:text>\let\bibname\oldbibname&#10;</xsl:text>
+			<xsl:text>\let\refname\oldrefname&#10;</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag class="xmlpi">bibtex-bibliography</sgmltag> nodes</refpurpose>
+		<doc:description>
+			<para>
+				Output a &BibTeX; bibliography.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.bibfiles"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>makechapter</term>
+					<listitem>
+						<para>
+
+							Choose which &LaTeX; mapping to use. This is
+							normally determined by examining whether the PI
+							occurs as a child of a <doc:db>book</doc:db> or
+							<doc:db>part</doc:db>. Regardless of this
+							parameter, the bibliography will be formatted as a
+							chapter via the &LaTeX; <function
+							condition="latex">bibliography</function> command.
+
+						</para>
+					</listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>filename</term>
+					<listitem>
+						<para>
+
+							The filename of the &BibTeX; citations source file.
+							By default, this will be obtained from the content
+							of the process instruction, if present, or
+							otherwise from <xref
+							linkend="param.latex.bibfiles"/>.
+
+						</para>
+					</listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>This PI is not part of &DocBook; and is only supported by &DB2LaTeX;
+			The formatting of the bibliography is performed by &LaTeX; and is not
+			configurable by &DB2LaTeX;.</para>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;: This template will use the <literal>bibliography-chapter</literal>
+				or <literal>bibliography-section</literal> mapping.</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="processing-instruction('bibtex-bibliography')">
+		<xsl:param name="makechapter" select="local-name(..)='book' or local-name(..)='part'"/>
+		<xsl:param name="filename">
+			<xsl:choose>
+				<xsl:when test="normalize-space(.)!=''">
+					<xsl:value-of select="."/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="$latex.bibfiles"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:variable name="keyword">
+			<xsl:choose>
+				<xsl:when test="$makechapter">
+					<xsl:text>bibliography-chapter</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>bibliography-section</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:call-template name="map.begin">
+			<xsl:with-param name="keyword" select="$keyword"/>
+		</xsl:call-template>
+		<xsl:text>\bibliography{</xsl:text><xsl:value-of select="$filename"/><xsl:text>}&#10;</xsl:text>
+		<xsl:call-template name="map.end">
+			<xsl:with-param name="keyword" select="$keyword"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>bibliodiv</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats subdivisions of bibliographies.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.biblio.output"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			&essential_preamble;
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_biblio;
+				&test_bind;
+				&test_book;
+				&test_cited;
+				&test_ieeebiblio;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="bibliodiv">
+		<xsl:param name="environment">
+			<xsl:variable name="parent" select="local-name(..)"/>
+			<xsl:choose>
+				<xsl:when test="starts-with($parent,'sect')">docbooktolatexbibliography</xsl:when>
+				<xsl:otherwise>thebibliography</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<!--
+		<xsl:message>DB2LaTeX: Processing BIBLIOGRAPHY - BIBLIODIV</xsl:message>
+		-->
+		<xsl:text>&#10;\begin{docbooktolatexbibliography}{</xsl:text>
+		<xsl:value-of select="$latex.bibwidelabel"/>
+		<xsl:text>}{\</xsl:text>
+		<!-- TODO choose the correct nesting, rather than assuming subsection -->
+		<xsl:text>subsection</xsl:text>
+		<xsl:text>}{</xsl:text>
+		<xsl:apply-templates select="title|subtitle"/>
+		<xsl:text>}\hypertarget{</xsl:text>
+		<xsl:call-template name="generate.label.id"/>
+		<xsl:text>}{}&#10;</xsl:text>
+		<xsl:choose>
+			<xsl:when test="$latex.biblio.output ='cited'">
+				<xsl:apply-templates select="biblioentry" mode="bibliography.cited">
+					<xsl:sort select="./abbrev"/>
+					<xsl:sort select="./@xreflabel"/>
+					<xsl:sort select="./@id"/>
+				</xsl:apply-templates>
+			</xsl:when>
+			<xsl:when test="$latex.biblio.output ='all'">
+				<xsl:apply-templates select="biblioentry">
+					<xsl:sort select="./abbrev"/>
+					<xsl:sort select="./@xreflabel"/>
+					<xsl:sort select="./@id"/>
+				</xsl:apply-templates>
+			</xsl:when>
+		</xsl:choose>
+		<xsl:text>&#10;\end{docbooktolatexbibliography}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="biblioentry" xmlns="">
+		<refpurpose>Process <doc:db>biblioentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Emits a bibiographic entry if the reference was cited in the document.
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<para>This template calls <xref linkend="template.biblioentry.output"/> to format the entry.</para>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="biblioentry" mode="bibliography.cited">
+		<xsl:param name="bibid" select="@id"/>
+		<xsl:param name="ab" select="abbrev"/>
+		<xsl:variable name="nx" select="//xref[@linkend=$bibid]"/>
+		<xsl:variable name="nc" select="//citation[text()=$ab]"/>
+		<xsl:if test="count($nx) &gt; 0 or count($nc) &gt; 0">
+			<xsl:call-template name="biblioentry.output"/>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template basename="biblioentry" xmlns="">
+		<refpurpose>Process <doc:db>biblioentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Emits a bibiographic entry unconditionally.
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<para>This template calls <xref linkend="template.biblioentry.output"/> to format the entry.</para>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="biblioentry" mode="bibliography.all">
+		<xsl:call-template name="biblioentry.output"/>
+	</xsl:template>
+
+	<doc:template basename="biblioentry" xmlns="">
+		<refpurpose>Process <doc:db>biblioentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Emits a bibiographic entry unconditionally.
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<para>This template calls <xref linkend="template.biblioentry.output"/> to format the entry.</para>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="biblioentry">
+		<xsl:call-template name="biblioentry.output"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Format <doc:db basename="biblioentry">biblioentries</doc:db></refpurpose>
+		<doc:description>
+			<para>
+				Formats a bibiographic entry.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.biblioentry.style"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<note>
+				<para>
+					This template does not apply to &BibTeX; bibliographies.
+				</para>
+			</note>
+			<para>
+				A <function condition="latex">bibitem</function> is emitted.
+				If can be linked via <doc:db>citation</doc:db> or <doc:db>xref</doc:db>.
+				The <doc:db>title</doc:db> will be formatted in italics, followed by
+				<xref linkend="param.biblioentry.item.separator"/>, the <doc:db>author</doc:db>
+				or <doc:db>authorgroup</doc:db>, and then the following elements separated
+				by <literal>biblioentry.item.separator</literal>:
+				<doc:db>copyright</doc:db>, <doc:db>publisher</doc:db>,
+				<doc:db>pubdate</doc:db>, <doc:db>pagenums</doc:db>,
+				<doc:db>isbn</doc:db>, <doc:db>editor</doc:db>,
+				<doc:db>releaseinfo</doc:db>.
+			</para>
+			<note>
+				<para>
+					All templates for all &DocBook; elements will be applied
+					with the <quote>bibliography.mode</quote> XSLT mode.
+				</para>
+			</note>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_biblio;
+				&test_bind;
+				&test_book;
+				&test_cited;
+				&test_ieeebiblio;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template name="biblioentry.output">
+		<xsl:variable name="biblioentry.label">
+			<xsl:choose>
+				<xsl:when test="@xreflabel">
+					<xsl:value-of select="normalize-space(@xreflabel)"/> 
+				</xsl:when>
+				<xsl:when test="abbrev">
+					<xsl:apply-templates select="abbrev" mode="bibliography.mode"/> 
+				</xsl:when>
+				<xsl:when test="@id">
+					<xsl:value-of select="normalize-space(@id)"/> 
+				</xsl:when>
+				<xsl:otherwise>
+					<!-- TODO is there any need for a warning? -->
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:variable name="biblioentry.id">
+			<xsl:choose>
+				<xsl:when test="abbrev">
+					<xsl:apply-templates select="abbrev" mode="bibliography.mode"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:call-template name="generate.label.id"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:call-template name="biblioentry.output.format">
+			<xsl:with-param name="biblioentry.label" select="$biblioentry.label"/>
+			<xsl:with-param name="biblioentry.id" select="$biblioentry.id"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<xsl:template name="biblioentry.output.format">
+		<xsl:param name="biblioentry.label"/>
+		<xsl:param name="biblioentry.id"/>
+		<xsl:choose>
+			<xsl:when test="$latex.biblioentry.style='ieee' or $latex.biblioentry.style='IEEE'">
+				<xsl:text>% -------------- biblioentry &#10;</xsl:text>
+				<xsl:text>\bibitem</xsl:text>
+				<xsl:text>{</xsl:text>
+				<xsl:value-of select="$biblioentry.id"/>
+				<xsl:text>}\docbooktolatexbibaux{</xsl:text>
+				<xsl:call-template name="generate.label.id"/>
+				<xsl:text>}{</xsl:text>
+				<xsl:value-of select="$biblioentry.id"/>
+				<xsl:text>}&#10;\hypertarget{</xsl:text>
+				<xsl:call-template name="generate.label.id"/>
+				<xsl:text>}&#10;</xsl:text>
+				<xsl:apply-templates select="author|authorgroup" mode="bibliography.mode"/>
+				<xsl:value-of select="$biblioentry.item.separator"/>
+				<xsl:text>\emph{</xsl:text> <xsl:apply-templates select="title" mode="bibliography.mode"/><xsl:text>}</xsl:text>
+				<xsl:for-each select="child::copyright|child::publisher|child::pubdate|child::pagenums|child::isbn">
+					<xsl:value-of select="$biblioentry.item.separator"/>
+					<xsl:apply-templates select="." mode="bibliography.mode"/>
+				</xsl:for-each>
+				<xsl:text>. </xsl:text>
+				<xsl:text>&#10;&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>% -------------- biblioentry &#10;</xsl:text>
+				<xsl:choose>
+					<xsl:when test="$biblioentry.label=''">
+						<xsl:text>\bibitem</xsl:text> 
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:text>\bibitem[{</xsl:text>
+						<xsl:call-template name="normalize-scape">
+							<xsl:with-param name="string" select="$biblioentry.label"/>
+						</xsl:call-template>
+						<xsl:text>}]</xsl:text>
+					</xsl:otherwise>
+				</xsl:choose>
+				<xsl:text>{</xsl:text>
+				<xsl:value-of select="$biblioentry.id"/>
+				<xsl:text>}\docbooktolatexbibaux{</xsl:text>
+				<xsl:call-template name="generate.label.id"/>
+				<xsl:text>}{</xsl:text>
+				<xsl:value-of select="$biblioentry.id"/>
+				<xsl:text>}&#10;\hypertarget{</xsl:text>
+				<xsl:call-template name="generate.label.id"/>
+				<xsl:text>}{\emph{</xsl:text> <xsl:apply-templates select="title" mode="bibliography.mode"/> <xsl:text>}}</xsl:text>
+				<xsl:value-of select="$biblioentry.item.separator"/>
+				<xsl:apply-templates select="author|authorgroup" mode="bibliography.mode"/>
+				<xsl:for-each select="child::copyright|child::publisher|child::pubdate|child::pagenums|child::isbn|child::editor|child::releaseinfo">
+					<xsl:value-of select="$biblioentry.item.separator"/>
+					<xsl:apply-templates select="." mode="bibliography.mode"/>
+				</xsl:for-each>
+				<xsl:text>.</xsl:text>
+				<xsl:text>&#10;&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<xsl:template name="biblioentry.output.format.ieee">
+	</xsl:template>
+
+    <xsl:template match="abbrev" mode="bibliography.mode">
+		<xsl:apply-templates mode="bibliography.mode"/>
+    </xsl:template>
+
+	<!--
+	<doc:template basename="abstract" match="abstract" mode="bibliography.mode" xmlns="">
+		<refpurpose>Process <doc:db>abstract</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Currently, <doc:db basename="abstract">abstracts</doc:db> are deleted
+				in <literal>bibliography.mode</literal>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>Abstracts are suppressed in &DB2LaTeX; bibliographies.</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="abstract" mode="bibliography.mode"/>
+	-->
+
+	<xsl:template match="address" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="affiliation" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="authorblurb" mode="bibliography.mode"/>
+
+	<xsl:template match="artheader" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="artpagenums" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="author" mode="bibliography.mode">
+		<xsl:apply-templates select="."/>
+	</xsl:template>
+
+	<xsl:template match="authorgroup" mode="bibliography.mode">
+		<xsl:apply-templates select="."/>
+	</xsl:template>
+
+	<!-- basename="authorinitials" -->
+	<xsl:template match="authorinitials" mode="bibliography.mode">
+		<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="bibliomisc" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="bibliomset" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="bibliomixed" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="biblioset" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="biblioset/title|biblioset/citetitle" mode="bibliography.mode">
+	<xsl:variable name="relation" select="../@relation"/>
+	<xsl:choose>
+		<xsl:when test="$relation='article'">
+		<xsl:call-template name="gentext.startquote"/>
+		<xsl:apply-templates/>
+		<xsl:call-template name="gentext.endquote"/>
+		</xsl:when>
+		<xsl:otherwise>
+		<xsl:apply-templates/>
+		</xsl:otherwise>
+	</xsl:choose>
+	</xsl:template>
+
+	<xsl:template match="bookbiblio" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="citetitle" mode="bibliography.mode">
+	<I><xsl:apply-templates mode="bibliography.mode"/></I>
+	</xsl:template>
+
+	<xsl:template match="collab" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="collabname" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="confgroup" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="confdates" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="conftitle" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="confnum" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="confsponsor" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="contractnum" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="contractsponsor" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="contrib" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="copyright" mode="bibliography.mode">
+	<xsl:call-template name="gentext.element.name"/>
+	<xsl:call-template name="gentext.space"/>
+	<xsl:call-template name="dingbat">
+		<xsl:with-param name="dingbat">copyright</xsl:with-param>
+	</xsl:call-template>
+	<xsl:call-template name="gentext.space"/>
+	<xsl:apply-templates select="year" mode="bibliography.mode"/>
+	<xsl:call-template name="gentext.space"/>
+	<xsl:apply-templates select="holder" mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="year" mode="bibliography.mode">
+	<xsl:apply-templates/><xsl:text>, </xsl:text>
+	</xsl:template>
+
+	<xsl:template match="year[position()=last()]" mode="bibliography.mode">
+	<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="holder" mode="bibliography.mode">
+	<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="corpauthor" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="corpname" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="date" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="edition" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="editor" mode="bibliography.mode">
+	<xsl:call-template name="person.name"/>
+	</xsl:template>
+
+	<xsl:template match="firstname" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="honorific" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="indexterm" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="invpartnumber" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="isbn" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="issn" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="issuenum" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="jobtitle" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="lineage" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="orgname" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="orgdiv" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="othercredit" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="othername" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="pagenums" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="printhistory" mode="bibliography.mode">
+	<!-- suppressed -->
+	</xsl:template>
+
+	<xsl:template match="productname" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="productnumber" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="pubdate" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="publisher" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="publishername" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="pubsnumber" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="releaseinfo" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="revhistory" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="seriesinfo" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="seriesvolnums" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="shortaffil" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="subtitle" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="surname" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="title" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="titleabbrev" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="volumenum" mode="bibliography.mode">
+	<xsl:apply-templates mode="bibliography.mode"/>
+	</xsl:template>
+
+	<xsl:template match="*" mode="bibliography.mode">
+	<xsl:apply-templates select="."/>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/block.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/block.mod.xsl
new file mode 100644
index 00000000000..5c80221ea47
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/block.mod.xsl
@@ -0,0 +1,396 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--#############################################################################
+|	$Id: block.mod.xsl,v 1.15 2004/01/26 09:44:38 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="block" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: block.mod.xsl,v 1.15 2004/01/26 09:44:38 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.6">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Block Objects <filename>block.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>block.mod.xsl</filename> contains the
+			XSL templates for sundry block-formatted components.</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			Generic handler for interior elements of block-formatted components
+		</refpurpose>
+		<doc:description>
+			<para>
+			Applies all templates, excluding from <doc:db>title</doc:db>-related
+			and <doc:db>blockinfo</doc:db>-like elements.
+			</para>
+		</doc:description>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>info</term>
+					<listitem>
+						<para>
+
+						The name of the &DocBook; <quote>info</quote>-type
+						element for this component. By default, this is equal
+						to the name of the component with <literal>info</literal>
+						appended. For example: <doc:db>sectioninfo</doc:db>
+						for <doc:db>section</doc:db>.
+
+						</para>
+					</listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+	</doc:template>
+
+	<xsl:template name="content-templates">
+		<xsl:param name="info" select="concat(local-name(.),'info')"/>
+		<xsl:apply-templates select="node()[not(self::title or self::subtitle or self::titleabbrev or self::blockinfo or self::docinfo or local-name(.)=$info)]"/>
+	</xsl:template>
+
+	<xsl:template name="content-templates-rootid">
+		<!--
+		<xsl:message>Rootid <xsl:value-of select="$rootid"/></xsl:message>
+		<xsl:message>local-name(.) <xsl:value-of select="local-name(.)"/></xsl:message>
+		<xsl:message>count(ancestor::*) <xsl:value-of select="count(ancestor::*)"/></xsl:message>
+		-->
+		<xsl:choose>
+			<xsl:when test="$rootid != '' and count(ancestor::*) = 0">
+				<xsl:variable name="node" select="key('id', $rootid)"/>
+				<xsl:message>count($node) <xsl:value-of select="count($node)"/></xsl:message>
+				<xsl:choose>
+					<xsl:when test="count($node) = 0">
+						<xsl:message terminate="yes">
+							<xsl:text>Root ID '</xsl:text>
+							<xsl:value-of select="$rootid"/>
+							<xsl:text>' not found in document.</xsl:text>
+						</xsl:message>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:apply-templates select="$node"/>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="content-templates"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			Generic handler for block-formatted components
+		</refpurpose>
+		<doc:description>
+			<para>
+			Calls <xref linkend="template.label.id"/>,
+			applies templates for <doc:db>title</doc:db>,
+			then applies templates for content elements.
+			</para>
+		</doc:description>
+	</doc:template>
+
+	<xsl:template name="block.object">
+		<xsl:call-template name="label.id"/>
+		<xsl:apply-templates select="title"/>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:call-template name="content-templates"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			A quotation set off from the main text (not inline)
+		</refpurpose>
+		<doc:description>
+			<para>
+			Uses the &LaTeX; <function condition='env'>quote</function> environment.
+			If an attribution is present, it will be set at the end.
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><para><xref linkend="template.attribution-block.attribution"/></para></listitem>
+				<listitem><para>&mapping;</para></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+
+	<xsl:template match="blockquote">
+		<xsl:call-template name="map.begin"/>
+		<xsl:apply-templates/>
+		<xsl:apply-templates select="attribution" mode="block.attribution"/>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			A short inscription that occurs at the beginning of a section, chapter, or document
+		</refpurpose>
+		<doc:description>
+			<para>
+			Uses the &LaTeX; <function condition='env'>quote</function> environment.
+			If an attribution is present, it will be set at the end.
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><para><xref linkend="template.attribution-block.attribution"/></para></listitem>
+				<listitem><para>&mapping;</para></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+
+	<xsl:template match="epigraph">
+		<xsl:call-template name="map.begin"/>
+		<xsl:apply-templates/>
+		<xsl:apply-templates select="attribution" mode="block.attribution"/>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			This template produces no output
+		</refpurpose>
+		<doc:description>
+			<para>
+
+			The <doc:db>attribution</doc:db> element only occurs within <xref
+			linkend="template.blockquote"/> and <xref
+			linkend="template.epigraph"/>. However, the templates for those
+			elements use a <quote>mode</quote> mechanism. Therefore, this
+			template is intentionally suppressed and a replacement exists. See
+			<xref linkend="template.attribution-block.attribution"/> instead.
+
+			</para>
+		</doc:description>
+	</doc:template>
+
+	<xsl:template match="attribution"/>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			The source of a block quote or epigraph
+		</refpurpose>
+		<doc:description>
+			<para>
+			Starts a new line with right-aligned text preceded by an em dash.
+			</para>
+		</doc:description>
+	</doc:template>
+
+	<xsl:template match="attribution" mode="block.attribution">
+		<xsl:text>&#10;\hspace*\fill---</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			A block of text that is isolated from the main flow
+		</refpurpose>
+		<doc:description>
+			<para>
+			This is formatted as a plain block.
+			</para>
+		</doc:description>
+		<doc:notes>
+			<para>
+			This template should create sidebars (but it doesn't)!
+			</para>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><para><xref linkend="template.block.object"/></para></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+
+	<xsl:template match="sidebar">
+		<xsl:call-template name="block.object"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			Titles and subtitles
+		</refpurpose>
+		<doc:description>
+			<para>
+				Simply applies templates.
+			</para>
+			<para>
+
+				This is the default template, for <doc:db
+				basename="title">title</doc:db> and <doc:db
+				basename="subtitle">subtitles</doc:db>. The use of this
+				template is controlled by the template for closing elements,
+				which will often not apply templates for <sgmltag
+				class="starttag">subtitles</sgmltag>. Furthermore, there may be
+				templates to match <sgmltag class="starttag">titles</sgmltag>
+				in specific contexts (in which case this template will not be
+				used).
+
+			</para>
+			<para>
+				
+				This template is also used by &mapping;.
+				
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.apply.title.templates"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.apply.title.templates.admonitions"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.formal.title.placement"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.maketitle"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.titlepage.file"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.formalpara.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.step.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.book.article.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.article.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.procedure.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.formalpara.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.figure.title.style"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><para>&mapping;</para></listitem>
+				<listitem><para><xref linkend="template.content-templates"/></para></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+
+	<xsl:template match="title|subtitle">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			Captions generated from <doc:db>title</doc:db>s
+		</refpurpose>
+		<doc:description>
+			<para>
+			Simply applies templates.
+			</para>
+			<para>
+				The formatting of titles in <literal>caption.mode</literal> may
+				depend on the enclosing element's template.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.formalpara.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.step.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.book.article.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.article.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.procedure.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.formalpara.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.figure.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.formal.title.placement"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.caption.swapskip"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.equation.caption.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.example.caption.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.figure.caption.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.table.caption.style"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+			Since captions may be incorporated into hyperlinks and
+			tables of cross references, <quote>anchor</quote>-type
+			elements should not be applied when in this mode.
+			</para>
+		</doc:notes>
+	</doc:template>
+
+	<xsl:template match="title|subtitle" mode="caption.mode">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>
+			Acknowledgements in an <doc:db>article</doc:db>
+		</refpurpose>
+		<doc:description>
+			<para>
+			This is formatted as a plain block by applying templates
+			with leading and trailing blank lines.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+
+	<xsl:template match="ackno">
+		<xsl:text>&#10;</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template>
+		<refpurpose> Interpret a user's placement preferences for certain &LaTeX; floats </refpurpose>
+		<doc:notes>
+			<para>
+
+				This template should be invoked when the current node is a
+				<doc:db>figure</doc:db> or <doc:db>table</doc:db>. If a
+				<sgmltag class="attribute">condition</sgmltag> attribute exists
+				and begins with <quote>db2latex:</quote>, or a <sgmltag
+				class="pi">latex-float-placement</sgmltag> processing
+				instruction is present, the remainder of its value will be used
+				as the &LaTeX; <quote>float</quote> placement. Otherwise, the
+				default placement is determined by the element's template.
+
+			</para>
+			<para>
+
+				Currently, this template is used for <doc:db>figure</doc:db>s
+				and <doc:db>table</doc:db>s but not <doc:db>example</doc:db>s
+				or <doc:db>equation</doc:db>s.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="generate.latex.float.position">
+		<xsl:param name="default" select="'hbt'"/>
+		<xsl:choose>
+			<xsl:when test="processing-instruction('latex-float-placement')">
+				<xsl:value-of select="processing-instruction('latex-float-placement')"/>
+			</xsl:when>
+			<xsl:when test="starts-with(@condition, 'db2latex:')">
+				<xsl:value-of select="substring-after(@condition, 'db2latex:')"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="$default"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/book-article.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/book-article.mod.xsl
new file mode 100644
index 00000000000..8ee1ea318cd
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/book-article.mod.xsl
@@ -0,0 +1,854 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: book-article.mod.xsl,v 1.41 2004/01/31 11:05:54 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="book-article" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: book-article.mod.xsl,v 1.41 2004/01/31 11:05:54 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.28">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Books and Articles <filename>book-article.mod.xsl</filename></title>
+		<partintro>
+
+			<para>
+
+			Most &DocBook; documents are either <doc:db
+			basename="article">articles</doc:db> or <doc:db
+			basename="book">books</doc:db>, so this XSL template file is a
+			classical entry point when processing &DocBook; documents.
+
+			</para>
+
+			<!--
+			<doc:variables>
+				&no_var;
+			</doc:variables>
+			-->
+		</partintro>
+	</doc:reference>
+
+	<doc:template basename="book" xmlns="">
+		<refpurpose>Process a &DocBook; <doc:db>book</doc:db> document</refpurpose>
+		<doc:description>
+			<para>
+				Entry point for <doc:db basename="book">books</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.book.afterauthor"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.toc.section.depth"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.section.depth"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.book.begindocument"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.titlepage.file"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.maketitle"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<!--
+		<doc:notes>
+		</doc:notes>
+		-->
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_defguide;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.generate.latex.book.preamble"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="book">
+		<!-- book:1: generate.latex.book.preamble -->
+		<xsl:call-template name="generate.latex.book.preamble"/>
+		<!-- book:2: output title information     -->
+		<xsl:text>\title{</xsl:text>
+			<xsl:apply-templates select="title|bookinfo/title"/>
+			<xsl:apply-templates select="subtitle|bookinfo/subtitle"/>
+		<xsl:text>}&#10;</xsl:text>
+		<!-- book:3: output author information     -->
+		<xsl:text>\author{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="bookinfo/authorgroup">
+				<xsl:apply-templates select="bookinfo/authorgroup"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:for-each select="bookinfo">
+					<xsl:call-template name="authorgroup"/>
+				</xsl:for-each>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}&#10;</xsl:text>
+		<!-- book:4: dump any preamble after author  -->
+		<xsl:value-of select="$latex.book.afterauthor"/>
+		<!-- book:5: set some counters  -->
+		<xsl:text>&#10;\setcounter{tocdepth}{</xsl:text><xsl:value-of select="$toc.section.depth"/><xsl:text>}&#10;</xsl:text>
+		<xsl:text>&#10;\setcounter{secnumdepth}{</xsl:text><xsl:value-of select="$section.depth"/><xsl:text>}&#10;</xsl:text>
+		<!-- book:6: dump the begin document command  -->
+		<xsl:value-of select="$latex.book.begindocument"/>
+		<!-- book:7: include external Cover page if specified -->
+		<xsl:if test="$latex.titlepage.file != ''">
+			<xsl:text>&#10;\InputIfFileExists{</xsl:text><xsl:value-of select="$latex.titlepage.file"/>
+			<xsl:text>}{\typeout{WARNING: Using cover page </xsl:text>
+			<xsl:value-of select="$latex.titlepage.file"/>
+			<xsl:text>}}</xsl:text>
+		</xsl:if>
+		<!-- book:7b: maketitle and set up pagestyle -->
+		<xsl:value-of select="$latex.maketitle"/>
+		<!-- book:8: - APPLY TEMPLATES -->
+		<xsl:apply-templates select="bookinfo"/>
+		<xsl:call-template name="content-templates-rootid"/>
+		<!-- book:9:  call map.end -->
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<doc:template basename="title" xmlns="">
+		<refpurpose>Process <doc:db>title</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Typesets a bold title.
+			</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="book/title">\bfseries <xsl:apply-templates/></xsl:template>
+
+	<doc:template basename="subtitle" xmlns="">
+		<refpurpose>Process <doc:db>subtitle</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Typesets a bold subtitle, spaced 12pt from the preceding <doc:db>title</doc:db>.
+			</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="book/subtitle">\\[12pt]\normalsize <xsl:apply-templates/></xsl:template>
+
+	<doc:template basename="title" xmlns="">
+		<refpurpose>Process <doc:db>title</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Typesets a bold title.
+			</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="book/bookinfo/title">\bfseries <xsl:apply-templates/></xsl:template>
+
+	<doc:template basename="subtitle" xmlns="">
+		<refpurpose>Process <doc:db>subtitle</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Typesets a bold subtitle, spaced 12pt from the preceding <doc:db>title</doc:db>.
+			</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="book/bookinfo/subtitle">\\[12pt]\normalsize <xsl:apply-templates/></xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>bookinfo</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Processes a <doc:db>book</doc:db>'s <doc:db>bookinfo</doc:db>
+				(will be invoked after the title page has been typeset).
+			</para>
+		</doc:description>
+		<doc:notes>
+			<para>
+
+				Only the <doc:db>revhistory</doc:db>,
+				<doc:db>abstract</doc:db>, <doc:db>keywordset</doc:db>,
+				<doc:db>copyright</doc:db> and <doc:db>legalnotice</doc:db> are
+				processed. Users may override this in their customisation
+				layer.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="book/bookinfo">
+		<xsl:apply-templates select="revhistory" />
+		<xsl:apply-templates select="copyright" />
+		<xsl:apply-templates select="keywordset" />
+		<xsl:apply-templates select="legalnotice" />
+		<xsl:apply-templates select="abstract" />
+	</xsl:template>
+
+	<doc:template basename="copyright" xmlns="">
+		<refpurpose>Process <doc:db>bookinfo</doc:db>'s <doc:db>copyright</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a block-style copyright.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:description>
+			<para>Calls <xref linkend="template.copyright"/>.</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="bookinfo/copyright">
+		<xsl:text>\begin{center}</xsl:text>
+		<xsl:call-template name="copyright"/>
+		<xsl:text>\end{center}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="article" xmlns="">
+		<refpurpose>Process a <doc:db>book</doc:db>'s <doc:db>article</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Entry point for a <literal>book</literal>'s <doc:db basename="article">articles</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.book.article.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.book.article.header.style"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+				For double-sided books, each article will commence on a right-hand page.
+			</para>
+			<para>
+				
+				This template will call upon the following variables or
+				templates in this order:
+				<literal>generate.latex.pagestyle</literal>,
+				<literal>title</literal> (or <doc:db>articleinfo</doc:db> or
+				<doc:db>artheader</doc:db>),
+				<literal>$latex.book.article.title.style</literal>,
+				<literal>date</literal> (from <literal>articleinfo</literal> or
+				<literal>artheader</literal>), <literal>authorgroup</literal>
+				or <literal>author</literal> (or <literal>articleinfo</literal>
+				or <literal>artheader</literal>),
+				<literal>$latex.book.article.header.style</literal>,
+				<literal>articleinfo</literal> or <literal>artheader</literal>
+				in the XSLT <literal>article.within.book</literal> mode,
+				<literal>content-templates</literal>.
+
+			</para>
+		</doc:notes>
+		<!--
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_defguide;
+			</simplelist>
+		</doc:samples>
+		-->
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.generate.latex.pagestyle"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.article/artheader|article/articleinfo-article.within.book"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+		<!--
+	    <formalpara><title>Tasks</title>
+		<itemizedlist>
+		    <listitem><para>Calls <literal>generate.latex.article.preamble</literal>.</para></listitem>
+		    <listitem><para>Outputs \title, \author, \date, getting the information from its children.</para></listitem>
+		    <listitem><para>Calls <literal>latex.article.begindocument</literal>.</para></listitem>
+		    <listitem><para>Calls <literal>latex.article.maketitle.</literal></para></listitem>
+		    <listitem><para>Applies templates.</para></listitem>
+		    <listitem><para>Calls <literal>latex.article.end</literal> template.</para></listitem>
+		</itemizedlist>
+	    </formalpara>
+		-->
+	<xsl:template match="book/article">
+		<xsl:text>&#10;\makeatletter\if@openright\cleardoublepage\else\clearpage\fi</xsl:text>
+		<xsl:call-template name="generate.latex.pagestyle"/>
+		<xsl:text>\makeatother&#10;</xsl:text>	
+		<!-- Get and output article title -->
+		<xsl:variable name="article.title">
+			<xsl:choose>
+				<xsl:when test="./title"> 
+					<xsl:apply-templates select="./title"/>
+				</xsl:when>
+				<xsl:when test="./articleinfo/title">
+					<xsl:apply-templates select="./articleinfo/title"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:apply-templates select="./artheader/title"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:text>\begin{center}{</xsl:text>
+		<xsl:value-of select="$latex.book.article.title.style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:value-of select="$article.title"/>
+		<xsl:text>}}\par&#10;</xsl:text>
+		<!-- Display date information -->
+		<xsl:variable name="article.date">
+			<xsl:apply-templates select="./artheader/date|./articleinfo/date"/>
+		</xsl:variable>
+		<xsl:if test="$article.date!=''">
+			<xsl:text>{</xsl:text>
+			<xsl:value-of select="$article.date"/>
+			<xsl:text>}\par&#10;</xsl:text>
+		</xsl:if>
+		<!-- Display author information -->
+		<xsl:text>{</xsl:text>
+		<xsl:value-of select="$latex.book.article.header.style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="articleinfo/authorgroup">
+				<xsl:apply-templates select="articleinfo/authorgroup"/>
+			</xsl:when>
+			<xsl:when test="artheader/authorgroup">
+				<xsl:apply-templates select="artheader/authorgroup"/>
+			</xsl:when>
+			<xsl:when test="articleinfo/author">
+				<xsl:for-each select="artheader">
+					<xsl:call-template name="authorgroup"/>
+				</xsl:for-each>
+			</xsl:when>
+			<xsl:when test="artheader/author">
+				<xsl:for-each select="artheader">
+					<xsl:call-template name="authorgroup"/>
+				</xsl:for-each>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="authorgroup"/>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}}\par&#10;</xsl:text>
+		<xsl:apply-templates select="artheader|articleinfo" mode="article.within.book"/>
+		<xsl:text>\end{center}&#10;</xsl:text>
+		<xsl:call-template name="content-templates"/>
+	</xsl:template>
+
+	<doc:template basename="article" xmlns="">
+		<refpurpose>Process a &DocBook; <doc:db>article</doc:db> document</refpurpose>
+		<doc:description>
+			<para>
+				Entry point for <doc:db basename="article">articles</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.toc.section.depth"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.section.depth"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.article.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.maketitle"/></simpara></listitem>
+				<!--
+				<listitem><simpara><xref linkend="param.latex.article.begindocument"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.article.end"/></simpara></listitem>
+				-->
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+				
+				This template will call upon the following variables or
+				templates in this order:
+				<literal>generate.latex.article.preamble</literal>,
+				<literal>$toc.section.depth</literal>,
+				<literal>$section.depth</literal>,
+				<literal>title</literal> (or <doc:db>articleinfo</doc:db> or
+				<doc:db>artheader</doc:db>),
+				<literal>$latex.article.title.style</literal>,
+				<literal>date</literal> (from <literal>articleinfo</literal> or
+				<literal>artheader</literal>), <literal>authorgroup</literal>
+				or <literal>author</literal> (or <literal>articleinfo</literal>
+				or <literal>artheader</literal>), <literal>map.begin</literal>,
+				<literal>$latex.maketitle</literal>,
+				<literal>articleinfo</literal> or <literal>artheader</literal>,
+				<literal>content-templates</literal>,
+				<literal>map.end</literal>.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_minimal;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;: this template will use the <literal>article</literal> mappings.</simpara></listitem>
+				<listitem><simpara><xref linkend="template.article/artheader|article/articleinfo-standalone.article"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.generate.latex.article.preamble"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="article">
+		<xsl:call-template name="generate.latex.article.preamble"/>
+		<xsl:text>&#10;\setcounter{tocdepth}{</xsl:text><xsl:value-of select="$toc.section.depth"/><xsl:text>}&#10;</xsl:text>
+		<xsl:text>&#10;\setcounter{secnumdepth}{</xsl:text><xsl:value-of select="$section.depth"/><xsl:text>}&#10;</xsl:text>
+	<!-- Get and output article title -->
+		<xsl:variable name="article.title">
+			<xsl:choose>
+				<xsl:when test="./title"> 
+					<xsl:apply-templates select="./title"/>
+				</xsl:when>
+				<xsl:when test="./articleinfo/title">
+					<xsl:apply-templates select="./articleinfo/title"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:apply-templates select="./artheader/title"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:text>\title{</xsl:text>
+		<xsl:value-of select="$latex.article.title.style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:value-of select="$article.title"/>
+		<xsl:text>}}&#10;</xsl:text>
+		<!-- Display date information -->
+		<xsl:variable name="article.date">
+			<xsl:apply-templates select="./artheader/date|./articleinfo/date"/>
+		</xsl:variable>
+		<xsl:if test="$article.date!=''">
+			<xsl:text>\date{</xsl:text>
+			<xsl:value-of select="$article.date"/>
+			<xsl:text>}&#10;</xsl:text>
+		</xsl:if>
+		<!-- Display author information -->
+		<xsl:text>\author{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="articleinfo/authorgroup">
+				<xsl:apply-templates select="articleinfo/authorgroup"/>
+			</xsl:when>
+			<xsl:when test="artheader/authorgroup">
+				<xsl:apply-templates select="artheader/authorgroup"/>
+			</xsl:when>
+			<xsl:when test="articleinfo/author">
+				<xsl:for-each select="artheader">
+					<xsl:call-template name="authorgroup"/>
+				</xsl:for-each>
+			</xsl:when>
+			<xsl:when test="artheader/author">
+				<xsl:for-each select="artheader">
+					<xsl:call-template name="authorgroup"/>
+				</xsl:for-each>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="authorgroup"/>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}&#10;</xsl:text>
+		<!-- Display  begindocument command -->
+		<xsl:call-template name="map.begin"/>
+		<xsl:value-of select="$latex.maketitle"/>
+		<xsl:apply-templates select="artheader|articleinfo" mode="standalone.article"/>
+		<xsl:call-template name="content-templates-rootid"/>
+		<xsl:call-template name="map.end"/>
+    </xsl:template>
+
+	<doc:template basename="date" xmlns="">
+		<refpurpose>Process <doc:db>date</doc:db> in <doc:db>articleinfo</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<!--
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_defguide;
+			</simplelist>
+		</doc:samples>
+		-->
+	</doc:template>
+	<xsl:template match="articleinfo/date|artheader/date">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template basename="articleinfo" xmlns="">
+		<refpurpose>Process <doc:db>articleinfo</doc:db> in <doc:db>article</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates for <doc:db>legalnotice</doc:db> and <doc:db>abstract</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<!--
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_defguide;
+			</simplelist>
+		</doc:samples>
+		-->
+	</doc:template>
+	<xsl:template match="article/artheader|article/articleinfo" mode="standalone.article">
+		<xsl:apply-templates select="keywordset" />
+		<xsl:apply-templates select="legalnotice" />
+		<xsl:apply-templates select="abstract"/>
+	</xsl:template>
+
+	<xsl:template match="article/artheader|article/articleinfo"/>
+
+	<doc:template basename="articleinfo" xmlns="">
+		<refpurpose>Process <doc:db>articleinfo</doc:db> in <doc:db>article</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates for <doc:db>abstract</doc:db> and <doc:db>legalnotice</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<!--
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_defguide;
+			</simplelist>
+		</doc:samples>
+		-->
+	</doc:template>
+	<xsl:template match="article/artheader|article/articleinfo" mode="article.within.book">
+		<xsl:apply-templates select="abstract"/>
+		<xsl:apply-templates select="legalnotice" />
+	</xsl:template>
+
+	<doc:template basename="legalnotice" xmlns="">
+		<refpurpose>Process <doc:db>legalnotice</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Typesets legal notices.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<note>
+				<para>This should be done via the mapping system!</para>
+			</note>
+			<para>
+
+				For two-column documents, the <doc:db>title</doc:db> is
+				formatted in italics and followed immediately by the notice's
+				content. For single-column documents, the
+				<literal>title</literal> is formatted in bold, centred on a
+				line of its own, and the body of the legal notice is formatted
+				as an indented small-font quotation.
+
+			</para>
+			<para>
+				The <doc:db>blockinfo</doc:db> is not processed
+				(only the <doc:db>title</doc:db> is used).
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_entities;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.legalnotice.title"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="legalnotice">
+		<xsl:text>&#10;{\if@twocolumn&#10;</xsl:text>
+			<xsl:text>\noindent\small\textit{&#10;</xsl:text>
+			<xsl:call-template name="legalnotice.title"/>
+			<xsl:text>}\/\bfseries---$\!$%&#10;</xsl:text>
+		<xsl:text>\else&#10;</xsl:text>
+			<xsl:text>\noindent\begin{center}\small\bfseries &#10;</xsl:text>
+			<xsl:call-template name="legalnotice.title"/>
+			<xsl:text>\end{center}\begin{quote}\small&#10;</xsl:text>
+		<xsl:text>\fi&#10;</xsl:text>
+		<xsl:call-template name="content-templates"/>
+		<xsl:text>\vspace{0.6em}\par\if@twocolumn\else\end{quote}\fi}&#10;</xsl:text>
+		<!--
+		<xsl:text>\normalsize\rmfamily&#10;</xsl:text>
+		-->
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Choose a title for <doc:db basename="legalnotice">legalnotices</doc:db> </refpurpose>
+		<doc:description>
+			<para>
+				Typesets a title.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				Will look for
+				<doc:db>blockinfo</doc:db>/<doc:db>title</doc:db>,
+				<doc:db>legalnotice</doc:db>/<doc:db>title</doc:db>
+				or a <quote>gentext</quote> title
+				(the first of the three will be used).
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<para>See <xref linkend="template.legalnotice"/></para>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.legalnotice.title"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="legalnotice.title">
+		<xsl:param name="title" select="blockinfo/title|title"/>
+		<xsl:choose>
+			<xsl:when test="count($title)>0">
+				<xsl:apply-templates select="$title[1]"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="gentext">
+					<xsl:with-param name="key">legalnotice</xsl:with-param>
+				</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template basename="toc" xmlns="">
+		<refpurpose> Generate and typeset a <doc:db>toc</doc:db> </refpurpose>
+		<doc:description>
+			<para>
+				Produce a chapter-level table of contents in &LaTeX;.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				This template ignores its contents and instead invokes the
+				&LaTeX; <function condition="latex">tableofcontents</function>
+				command. You will need to run your typesetter at least twice,
+				and possibly three times, to have the table of contents
+				generated normally. The headers, footers, and chapter title
+				will be generated by &LaTeX;.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_lot;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.latex.noparskip"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.restoreparskip"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="toc" name="toc">
+		<xsl:text>&#10;</xsl:text>
+		<xsl:call-template name="latex.noparskip"/>
+		<xsl:choose>
+			<xsl:when test="$latex.use.hyperref=1">
+				<xsl:text>
+\makeatletter
+\def\dbtolatex@contentsid{</xsl:text>
+				<xsl:call-template name="generate.label.id"/>
+				<xsl:text>}
+\let\dbtolatex@@contentsname\contentsname
+\newif\ifdocbooktolatexcontentsname\docbooktolatexcontentsnametrue
+\def\dbtolatex@contentslabel{%
+ \label{\dbtolatex@contentsid}\hypertarget{\dbtolatex@contentsid}{\dbtolatex@@contentsname}%
+ \global\docbooktolatexcontentsnamefalse}
+\def\contentsname{\ifdocbooktolatexcontentsname\dbtolatex@contentslabel\else\dbtolatex@@contentsname\fi}
+\tableofcontents
+\let\contentsname\dbtolatex@@contentsname
+\Hy@writebookmark{}{\dbtolatex@@contentsname}{\dbtolatex@contentsid}{0}{toc}%
+\makeatother
+				</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>\tableofcontents&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:call-template name="latex.restoreparskip"/>
+	</xsl:template>
+
+	<doc:template basename="toc" xmlns="">
+		<refpurpose> Generate and typeset a <doc:db>toc</doc:db> </refpurpose>
+		<doc:description>
+			<para>
+				Produce a chapter-level table of contents in &LaTeX;.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>prefer</term>
+					<listitem>
+						<para>
+
+							&LaTeX; can provide <function
+							condition="latex">listoffigures</function> and
+							<function condition="latex">listoftables</function>
+							by default. This parameter allows you to select
+							which should be used. Recognised values are
+							<quote>figures</quote> and <quote>tables</quote>.
+							If the value is empty or not recognised, both lists
+							will be output. By default, the value of the
+							current node's non-empty <sgmltag
+							class="attribute">condition</sgmltag>, <sgmltag
+							class="attribute">role</sgmltag> or <sgmltag
+							class="attribute">label</sgmltag> attribute will be
+							used.
+
+						</para>
+					</listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+
+				This template ignores its contents and instead invokes the
+				&LaTeX; <function condition="latex">listoffigures</function> or
+				<function condition="latex">listoftables</function> commands.
+				You will need to run your typesetter at least twice, and
+				possibly three times, to have the table of contents generated
+				normally. The headers, footers, and chapter title will be
+				generated by &LaTeX;.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_lot1;
+				&test_lot2;
+				&test_lot3;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.bridgehead.in.lot"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.noparskip"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.restoreparskip"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="lot" name="lot">
+		<xsl:param name="prefer">
+			<xsl:choose>
+				<xsl:when test="@condition!=''">
+					<xsl:value-of select="@condition"/>
+				</xsl:when>
+				<xsl:when test="@role!=''">
+					<xsl:value-of select="@role"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="@label"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:call-template name="latex.noparskip"/>
+		<xsl:choose>
+			<xsl:when test="$prefer='figures'">
+				<xsl:text>\listoffigures&#10;</xsl:text>
+			</xsl:when>
+			<xsl:when test="$prefer='tables'">
+				<xsl:text>\listoftables&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>\listoffigures&#10;</xsl:text>
+				<xsl:text>\listoftables&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:call-template name="latex.restoreparskip"/>
+	</xsl:template>
+
+<!--
+	<xsl:template match="lotentry">
+	</xsl:template>
+
+	<xsl:template match="lotentry"/>
+	<xsl:template match="tocpart|tocchap|tocfront|tocback|tocentry"/>
+	<xsl:template match="toclevel1|toclevel2|toclevel3|toclevel4|toclevel5"/>
+-->
+
+	<doc:template xmlns="">
+		<refpurpose> Choose the preferred page style for document body </refpurpose>
+		<doc:description>
+			<para>
+
+				If no page style is preferred by the user, the defaults will be
+				<literal>empty</literal> for <doc:db
+				basename="article">articles</doc:db>, <literal>plain</literal>
+				for <doc:db basename="book">books</doc:db>, or
+				<literal>fancy</literal> (if the &LaTeX;
+				<productname>fancyhdr</productname> package is permitted).
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.pagestyle"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.fancyhdr"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+			
+			The &LaTeX; <function condition="latex">pagestyle</function>
+			command is used to effect the page style.
+			
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="generate.latex.pagestyle">
+		<xsl:text>\pagestyle{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="$latex.pagestyle!=''">
+				<xsl:value-of select="$latex.pagestyle"/>
+			</xsl:when>
+			<xsl:when test="count(//book)&gt;0">
+				<xsl:choose>
+					<xsl:when test="$latex.use.fancyhdr=1"><xsl:text>fancy</xsl:text></xsl:when>
+					<xsl:otherwise><xsl:text>plain</xsl:text></xsl:otherwise>
+				</xsl:choose>
+			</xsl:when>
+			<xsl:otherwise><xsl:text>empty</xsl:text></xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+	
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/bridgehead.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/bridgehead.mod.xsl
new file mode 100644
index 00000000000..bef74a2bca3
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/bridgehead.mod.xsl
@@ -0,0 +1,120 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: bridgehead.mod.xsl,v 1.12 2004/01/11 11:35:25 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet 
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="bridgehead" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: bridgehead.mod.xsl,v 1.12 2004/01/11 11:35:25 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.10">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Free-floating Headings <filename>bridgehead.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>bridgehead.mod.xsl</filename> contains the
+			XSL template for <doc:db>bridgehead</doc:db>.</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template basename="bridgehead" xmlns="">
+		<refpurpose>Process <doc:db>bridgehead</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+
+				Free-floating headings for <doc:db
+				basename="bridgehead">bridgeheads</doc:db> elements. Renders
+				un-numbered section headings.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>renderas</term>
+					<listitem><simpara>The sectioning level to be emulated (e.g. <quote>1</quote> for <doc:db>sect1</doc:db>). Chooses the current node's <literal>@renderas</literal> attribute by default.</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>content</term>
+					<listitem><simpara>The content that forms the bridgehead text. By default, normal templates will be applied for the current node.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+				
+				The emulation of section headings is achieved through the
+				normal &latex; section commands such as
+				<function condition="latex">section</function>, <function condition="latex">subsection</function>,
+				and so forth. However, levels above three (3) will be typeset
+				with the &latex; <function condition="latex">paragraph*</function> command.
+				
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_subfig;
+				&test_tables;
+			</simplelist>
+		</doc:samples>
+		<!--
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+		-->
+	</doc:template>
+	<xsl:template match="bridgehead" name="bridgehead">
+		<xsl:param name="renderas" select="@renderas"/>
+		<xsl:param name="content"><xsl:apply-templates/></xsl:param>
+		<xsl:choose>
+			<xsl:when test="$renderas='sect1' or $renderas='sect2' or $renderas='sect3'">
+				<xsl:text>&#10;\</xsl:text>
+				<xsl:if test="$renderas='sect2'"><xsl:text>sub</xsl:text></xsl:if>
+				<xsl:if test="$renderas='sect3'"><xsl:text>subsub</xsl:text></xsl:if>
+				<xsl:text>section*{</xsl:text>
+				<xsl:copy-of select="$content"/>
+				<xsl:text>}</xsl:text>
+				<xsl:call-template name="label.id"/>
+				<xsl:text>&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<!--
+				<xsl:text>&#10;&#10;</xsl:text>
+				<xsl:text>\vspace{1em}\noindent{\bfseries </xsl:text><xsl:copy-of select="$content"/><xsl:text>}</xsl:text>
+				<xsl:call-template name="label.id"/>
+				<xsl:text>\par\noindent&#10;</xsl:text>
+				-->
+				<xsl:text>&#10;\paragraph*{</xsl:text>
+				<xsl:copy-of select="$content"/>
+				<xsl:text>}</xsl:text>
+				<xsl:call-template name="label.id"/>
+				<xsl:text>&#10;&#10;\noindent&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/callout.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/callout.mod.xsl
new file mode 100644
index 00000000000..c671d30b7dd
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/callout.mod.xsl
@@ -0,0 +1,884 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: callout.mod.xsl,v 1.10 2004/01/14 14:54:32 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="callout" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: callout.mod.xsl,v 1.10 2004/01/14 14:54:32 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.5">&rev_2003_05;</doc:revision>
+				<doc:revision rcasver="1.6">
+					<date>January 2004</date>
+					<revremark>Added callout support.</revremark>
+				</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Callouts <filename>callout.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			These template use the concept of an <quote>areamark</quote>, an
+			<quote>arearef</quote> and an <quote>areasymbol</quote>. An areamark
+			is a way of illustrating a callout area as part of an image or
+			listing. An arearef is a way of illustrating a callout area as part of
+			a callout list. By default, the areamark and the arearef are both
+			represented by the areasymbol. (Aside: that the areamark is drawn
+			first.) This system allows opens the possibility for an areamark to
+			draw a box around an area in addition to displaying the areasymbol.
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose> Essential preamble for <filename>callout.mod.xsl</filename> support </refpurpose>
+		<doc:description>
+			<para>
+
+				Loads the <productname>overpic</productname> packages and
+				defines <function condition="latex">calsscale</function>
+				and <function condition="latex">calspair</function> (which
+				are used to convert <quote>calspair</quote> coordinates into
+				<productname>overpic</productname> percent-style coordinates.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			<variablelist>
+				<varlistentry>
+					<term><xref linkend="param.latex.use.overpic"/></term>
+					<listitem><simpara>
+						Whether to enable this preamble or not.
+						If 0, callouts will cause &LaTeX; errors.
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&preamble;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="latex.preamble.essential.callout">
+		<xsl:if test="$latex.use.overpic=1 and //callout">
+			<xsl:text>
+				<![CDATA[
+\usepackage[percent]{overpic}
+\newdimen\dblatex@ascale \newdimen\dblatex@bscale
+\newdimen\dblatex@adimen \newdimen\dblatex@bdimen
+\newdimen\dblatex@cdimen \newdimen\dblatex@ddimen
+\newcommand{\calsscale}{%
+   \ifnum\@tempcnta>\@tempcntb%
+      \dblatex@ascale=1pt%
+      \dblatex@bscale=\@tempcntb pt%
+      \divide\dblatex@bscale by \@tempcnta%
+   \else%
+      \dblatex@bscale=1 pt%
+      \dblatex@ascale=\@tempcnta pt%
+      \divide\dblatex@ascale by \@tempcntb%
+   \fi%
+}
+\newcommand{\calspair}[3]{
+   \sbox{\z@}{#3}
+   \settowidth{\dblatex@cdimen}{\usebox{\z@}}
+   \settoheight{\dblatex@ddimen}{\usebox{\z@}}
+   \divide\dblatex@cdimen by 2
+   \divide\dblatex@ddimen by 2
+   \dblatex@adimen=#1 pt \dblatex@adimen=\strip@pt\dblatex@ascale\dblatex@adimen
+   \dblatex@bdimen=#2 pt \dblatex@bdimen=\strip@pt\dblatex@bscale\dblatex@bdimen
+   \put(\strip@pt\dblatex@adimen,\strip@pt\dblatex@bdimen){\hspace{-\dblatex@cdimen}\raisebox{-\dblatex@ddimen}{\usebox{\z@}}}
+}
+]]>
+			</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>programlistingco</doc:db> and <doc:db>screenco</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="programlistingco|screenco">
+		<xsl:apply-templates select="programlisting|screen|calloutlist"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>areaset</doc:db>-related elements</refpurpose>
+		<doc:description>
+			<para>
+				Suppressed (<doc:db>area</doc:db> templates are applied by
+				<xref linkend="template.imagedata"/>).
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	 <xsl:template match="areaspec|areaset"/>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>co</doc:db>-related elements</refpurpose>
+		<doc:description>
+			<para>
+				Print a callout number as a parenthesis.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>This template is probably never applied, because
+			we can't yet handled <doc:db basename="co">cos</doc:db>
+			in verbatim environments.</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="co">
+		<xsl:variable name="conum">
+			<xsl:number count="co" format="1"/>
+		</xsl:variable>
+		<xsl:text>(</xsl:text>
+		<xsl:value-of select="$conum"/>
+		<xsl:text>)</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>calloutlist</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="calloutlist">
+		<xsl:apply-templates select="./title"/>
+		<xsl:text>&#10;\begin{description}&#10;</xsl:text>
+		<xsl:apply-templates select="callout"/>
+		<xsl:text>\end{description}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process titles for <doc:db>calloutlist</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Formats a title.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<variablelist>
+				<varlistentry>
+					<term><xref linkend="param.latex.list.title.style"/></term>
+					<listitem><simpara>
+						The &LaTeX; command for formatting titles.
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>style</term>
+					<listitem><simpara>The &LaTeX; command to use. Defaults to
+					<xref linkend="param.latex.list.title.style"/>.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+				Applies templates as a paragraph, formatted with the specified style.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="calloutlist/title">
+		<xsl:param name="style" select="$latex.list.title.style"/>
+		<xsl:text>&#10;{</xsl:text>
+		<xsl:value-of select="$style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>}}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="callout" xmlns="">
+		<refpurpose>Process <doc:db>callout</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats arearefs as an <function condition="latex">item</function>,
+				then applies templates. Since there may be multiple IDs specified
+				in the <sgmltag class="attribute">arearefs</sgmltag> attribute,
+				the <xref linkend="template.generate.callout.arearefs"/> template is
+				called recursively to generate the arearefs.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="callout">
+		<xsl:text>\item[{</xsl:text>
+		<xsl:call-template name="generate.callout.arearefs"/>
+		<xsl:text>}]\null{}&#10;</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Determine a <doc:db>callout</doc:db>'s arearefs</refpurpose>
+		<doc:description>
+			<para>
+				Splits the arearef attribute on whitespace, then
+				constructs a list of references by applying templates
+				in <quote>generate.callout.arearef</quote> mode.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				The current node must be a <doc:db>callout</doc:db>.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="generate.callout.arearefs">
+		<xsl:param name="arearefs" select="normalize-space(@arearefs)"/>
+		<xsl:param name="count" select="1"/>
+		<xsl:if test="$arearefs!=''">
+			<xsl:choose>
+				<xsl:when test="substring-before($arearefs,' ')=''">
+					<xsl:apply-templates select="." mode="generate.callout.arearef">
+						<xsl:with-param name="arearef" select="$arearefs"/>
+						<xsl:with-param name="count" select="$count"/>
+						<xsl:with-param name="last" select="true()"/>
+					</xsl:apply-templates>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:apply-templates select="." mode="generate.callout.arearef">
+						<xsl:with-param name="arearef" select="substring-before($arearefs,' ')"/>
+						<xsl:with-param name="count" select="$count"/>
+						<xsl:with-param name="last" select="false()"/>
+					</xsl:apply-templates>
+				</xsl:otherwise>
+			</xsl:choose>
+			<xsl:call-template name="generate.callout.arearefs">
+				<xsl:with-param name="arearefs" select="substring-after($arearefs,' ')"/>
+				<xsl:with-param name="count" select="$count + 1"/>
+			</xsl:call-template>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Format a <doc:db>callout</doc:db>'s arearefs</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates in <quote>generate.callout.arearef</quote> mode.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>arearef</term>
+					<listitem><simpara>
+						The ID of the <doc:db>area</doc:db> to which a <doc:db>callout</doc:db>
+						refers.
+					</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>area</term>
+					<listitem><simpara>
+						The <doc:db>area</doc:db> object to which a <doc:db>callout</doc:db>
+						refers. By default, this searches for a area whose <sgmltag
+						class="attribute">id</sgmltag> attribute equals the
+						<literal>arearef</literal> parameter.
+					</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>count</term>
+					<listitem><simpara>
+						The position of this reference in the list of references
+						used by a given <doc:db>callout</doc:db>. Influences
+						delimiters for list items.
+					</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>last</term>
+					<listitem><simpara>
+						Whether this area reference is the last one for a given
+						<doc:db>callout</doc:db>. Influences delimiters for list
+						items.
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+				Formats a reference for a single arearef. This is performed by
+				applying templates for the <doc:db>area</doc:db> in
+				<quote>generate.area.arearef</quote> mode.
+			</para>
+			<para>
+				The current node must be a <doc:db>callout</doc:db>.
+			</para>
+			<para>
+				Uses the <quote>naturalinlinelist</quote> localisation context.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="callout" mode="generate.callout.arearef">
+		<xsl:param name="arearef" select="@arearefs"/>
+		<xsl:param name="area" select="key('id', $arearef)"/>
+		<xsl:param name="last" select="false()"/>
+		<xsl:param name="count" select="1"/>
+		<xsl:variable name="first" select="$count=1"/>
+		<xsl:choose>
+			<xsl:when test="$first">
+				<xsl:call-template name="gentext.template">
+					<xsl:with-param name="context" select="'naturalinlinelist'"/>
+					<xsl:with-param name="name" select="'start'"/>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$last">
+				<xsl:call-template name="gentext.template">
+					<xsl:with-param name="context" select="'naturalinlinelist'"/>
+					<xsl:with-param name="name">
+						<xsl:choose>
+							<xsl:when test="$count &gt; 2">
+								<xsl:text>lastofmany</xsl:text>
+							</xsl:when>
+							<xsl:otherwise>
+								<xsl:text>lastoftwo</xsl:text>
+							</xsl:otherwise>
+						</xsl:choose>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="gentext.template">
+					<xsl:with-param name="context" select="'naturalinlinelist'"/>
+					<xsl:with-param name="name" select="'middle'"/>
+				</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:choose>
+			<xsl:when test="$area">
+				<xsl:apply-templates select="$area" mode="generate.area.arearef"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>?</xsl:text>
+				<xsl:message>
+					<xsl:text>Error: no ID for constraint arearefs: </xsl:text>
+					<xsl:value-of select="$arearef"/>
+					<xsl:text>.</xsl:text>
+				</xsl:message>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:if test="$last">
+			<xsl:call-template name="gentext.template">
+				<xsl:with-param name="context" select="'naturalinlinelist'"/>
+				<xsl:with-param name="name" select="'end'"/>
+			</xsl:call-template>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template basename="area" xmlns="">
+		<refpurpose>Illustrate a reference to a callout's area</refpurpose>
+		<doc:description>
+			<para>
+				Formats an <doc:db>area</doc:db> as part of a
+				callout list.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				The current node must be an <doc:db>area</doc:db>.
+			</para>
+			<para>
+				Applies templates in the <quote>generate.arearef.calspair</quote>,
+				<quote>generate.arearef.linerange</quote> and
+				<quote>generate.arearef</quote> modes.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="area" mode="generate.area.arearef">
+		<xsl:variable name="units">
+			<xsl:choose>
+				<xsl:when test="@units!=''">
+					<xsl:value-of select="@units"/>
+				</xsl:when>
+				<xsl:when test="../@units!=''">
+					<xsl:value-of select="../@units"/>
+				</xsl:when>
+				<xsl:when test="../../@units!=''">
+					<xsl:value-of select="../../@units"/>
+				</xsl:when>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:choose>
+			<xsl:when test="$units='calspair'">
+				<xsl:apply-templates select="." mode="generate.arearef.calspair"/>
+			</xsl:when>
+			<xsl:when test="$units='linerange'">
+				<xsl:apply-templates select="." mode="generate.arearef.linerange"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:apply-templates select="." mode="generate.arearef">
+					<xsl:with-param name="units" select="$units"/>
+				</xsl:apply-templates>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template basename="area" xmlns="">
+		<refpurpose>Illustrate a reference to a callout's area</refpurpose>
+		<doc:description>
+			<para>
+				Formats an <doc:db>area</doc:db> as part of a
+				callout list.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				This is a fallback template for unknown units.
+				It does not format an arearef but instead prints
+				an error message.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="area" mode="generate.arearef">
+		<xsl:param name="units"/>
+		<xsl:message>Error: unsupported arearef units <xsl:value-of select="$units"/>.</xsl:message>
+	</xsl:template>
+
+	<doc:template basename="area" xmlns="">
+		<refpurpose>Illustrate a reference to a callout's area</refpurpose>
+		<doc:description>
+			<para>
+				Formats calspair units for a callout list.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.area-generate.area.areasymbol"/>.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="area" mode="generate.arearef.calspair">
+		<xsl:apply-templates select="." mode="generate.area.areasymbol"/>
+	</xsl:template>
+
+	<doc:template basename="area" xmlns="">
+		<refpurpose>Illustrate a reference to a callout's area</refpurpose>
+		<doc:description>
+			<para>
+				Formats linerange units for a callout list.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Formats a line range numerically, condensing the line range
+				down to a single line reference if the starting line is the
+				same as the finishing line.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="area" mode="generate.arearef.linerange">
+		<xsl:choose>
+			<xsl:when test="not(contains(@coords, ' '))">
+				<xsl:value-of select="@coords"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:variable name="start" select="substring-before(@coords, ' ')"/>
+				<xsl:variable name="finish" select="substring-after(@coords, ' ')"/>
+				<xsl:choose>
+					<xsl:when test="$start=$finish">
+						<xsl:value-of select="$start"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:call-template name="string-replace">
+							<xsl:with-param name="from" select="' '"/>
+							<xsl:with-param name="to" select="'--'"/>
+							<xsl:with-param name="string" select="@coords"/>
+						</xsl:call-template>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template basename="area" xmlns="">
+		<refpurpose>Illustrate a callout's area as part of an image or listing</refpurpose>
+		<doc:description>
+			<para>
+				Formats an <doc:db>area</doc:db> as part of a
+				displayed image or listing.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Applies templates in the <quote>generate.area.areamark</quote> mode.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="area">
+		<xsl:apply-templates select="." mode="generate.area.areamark"/>
+	</xsl:template>
+
+	<doc:template basename="area" xmlns="">
+		<refpurpose>Illustrate a callout's area as part of an image or listing</refpurpose>
+		<doc:description>
+			<para>
+				Formats an <doc:db>area</doc:db> as part of a
+				displayed image or listing.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Applies templates in the <quote>generate.areamark.calspair</quote> or
+				<quote>generate.areamark</quote> modes.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="area" mode="generate.area.areamark">
+		<xsl:variable name="units">
+			<xsl:choose>
+				<xsl:when test="@units!=''">
+					<xsl:value-of select="@units"/>
+				</xsl:when>
+				<xsl:when test="../@units!=''">
+					<xsl:value-of select="../@units"/>
+				</xsl:when>
+				<xsl:when test="../../@units!=''">
+					<xsl:value-of select="../../@units"/>
+				</xsl:when>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:choose>
+			<xsl:when test="$units='calspair'">
+				<xsl:apply-templates select="." mode="generate.areamark.calspair"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:apply-templates select="." mode="generate.areamark">
+					<xsl:with-param name="units" select="$units"/>
+				</xsl:apply-templates>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template basename="area" xmlns="">
+		<refpurpose>Illustrate a callout's area as part of an image or listing</refpurpose>
+		<doc:description>
+			<para>
+				Formats an <doc:db>area</doc:db> as part of a
+				displayed image or listing.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				This is a fallback template for unknown units.
+				It does not format an areamark but instead prints
+				an error message.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="area" mode="generate.areamark">
+		<xsl:param name="units"/>
+		<xsl:message>Error: unsupported areamark units <xsl:value-of select="$units"/>.</xsl:message>
+	</xsl:template>
+
+	<doc:template basename="area" xmlns="">
+		<refpurpose>Illustrate a callout's area as part of an image or listing</refpurpose>
+		<doc:description>
+			<para>
+				Formats calspair units for a displayed image or listing.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Converts calspair coordinates relative to the width and height of the
+				displayed image area. Will understand "x1,y1 x2,y2" and also "x1 y1".
+				In the former case, the drawing location is moved to the centre of
+				the implied rectangle. Templates are then applied in the
+				<quote>generate.area.areasymbol</quote> mode.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="area" mode="generate.areamark.calspair">
+		<xsl:choose>
+			<xsl:when test="not(contains(@coords, ' '))">
+				<xsl:message>Error: invalid calspair '<xsl:value-of select="@coords"/>'.</xsl:message>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:variable name="x1y1">
+					<xsl:value-of select="substring-before(@coords, ' ')"/>
+				</xsl:variable>
+				<xsl:variable name="x1">
+					<xsl:choose>
+						<xsl:when test="contains($x1y1, ',')">
+							<xsl:value-of select="substring-before($x1y1, ',')"/>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:value-of select="$x1y1"/>
+						</xsl:otherwise>
+					</xsl:choose>
+				</xsl:variable>
+				<xsl:variable name="y1">
+					<xsl:choose>
+						<xsl:when test="contains($x1y1, ',')">
+							<xsl:value-of select="substring-after($x1y1, ',')"/>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:value-of select="''"/>
+						</xsl:otherwise>
+					</xsl:choose>
+				</xsl:variable>
+				<xsl:variable name="x2y2">
+					<xsl:value-of select="substring-after(@coords, ' ')"/>
+				</xsl:variable>
+				<xsl:variable name="y2">
+					<xsl:choose>
+						<xsl:when test="contains($x2y2, ',')">
+							<xsl:value-of select="substring-after($x2y2, ',')"/>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:value-of select="$x2y2"/>
+						</xsl:otherwise>
+					</xsl:choose>
+				</xsl:variable>
+				<xsl:variable name="x2">
+					<xsl:choose>
+						<xsl:when test="contains($x2y2, ',')">
+							<xsl:value-of select="substring-before($x2y2, ',')"/>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:value-of select="''"/>
+						</xsl:otherwise>
+					</xsl:choose>
+				</xsl:variable>
+				<xsl:text>\calspair{</xsl:text>
+				<!-- choose horizontal coordinate -->
+				<xsl:choose>
+					<xsl:when test="$x1 != '' and $x2 != ''">
+						<xsl:value-of select="(number($x1)+number($x2)) div 200"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:value-of select="number(concat($x1, $x2)) div 100"/>
+					</xsl:otherwise>
+				</xsl:choose>
+				<xsl:text>}{</xsl:text>
+				<!-- choose vertical coordinate -->
+				<xsl:choose>
+					<xsl:when test="$y1 != '' and $y2 != ''">
+						<xsl:value-of select="(number($y1)+number($y2)) div 200"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:value-of select="number(concat($y1, $y2)) div 100"/>
+					</xsl:otherwise>
+				</xsl:choose>
+				<xsl:text>}{</xsl:text>
+				<xsl:apply-templates select="." mode="generate.area.areasymbol"/>
+				<xsl:text>}&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template basename="area" xmlns="">
+		<refpurpose>Illustrate a callout's area as part of an image or listing</refpurpose>
+		<doc:description>
+			<para>
+				Formats an <doc:db>area</doc:db> as an overlay
+				on an image or listing.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				If the area has a <sgmltag class="attribute">label</sgmltag>
+				attribute, it is used as raw &LaTeX; code.
+			</para>
+			<para>
+				If the area has a linkends attribute, templates are
+				applied for the first linkend using
+				<quote>generate.callout.areasymbol</quote> mode.
+				It is implicit in this scenario that an arearef
+				and an areamark will both consist of an identical
+				icon for an area.
+			</para>
+			<para>
+				If none of the above were performed, an asterisk is printed.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="area" mode="generate.area.areasymbol">
+		<xsl:param name="linkends" select="normalize-space(@linkends)"/>
+		<xsl:choose>
+			<xsl:when test="@label">
+				<xsl:value-of select="@label"/>
+			</xsl:when>
+			<xsl:when test="$linkends!=''">
+				<xsl:variable name="linkend">
+					<xsl:choose>
+						<xsl:when test="contains($linkends, ' ')">
+							<xsl:value-of select="substring-before($linkends, ' ')"/>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:value-of select="$linkends"/>
+						</xsl:otherwise>
+					</xsl:choose>
+				</xsl:variable>
+				<xsl:variable name="target" select="key('id', $linkend)"/>
+				<xsl:choose>
+					<xsl:when test="count($target)&gt;0">
+						<xsl:for-each select="$target">
+							<xsl:apply-templates select="." mode="generate.callout.areasymbol">
+								<xsl:with-param name="arearef" select="generate-id(current())"/>
+								<xsl:with-param name="area" select="current()"/>
+							</xsl:apply-templates>
+						</xsl:for-each>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:text>?</xsl:text>
+						<xsl:message>
+							<xsl:text>Error: no ID for constraint linkends: </xsl:text>
+							<xsl:value-of select="$linkends"/>
+							<xsl:text>.</xsl:text>
+						</xsl:message>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>*</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template basename="callout" xmlns="">
+		<refpurpose>Illustrate a callout's area as part of an image or listing</refpurpose>
+		<doc:description>
+			<para>
+				Illustrates an <doc:db>area</doc:db> as part of a
+				displayed image or listing.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Prints the numeric position of the <doc:db>callout</doc:db> within its <doc:db>calloutlist</doc:db>.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="callout" mode="generate.callout.areasymbol">
+		<xsl:number count="callout" format="1"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>mediaobjectco</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="mediaobjectco">
+		<xsl:text>&#10;</xsl:text>
+		<xsl:apply-templates select="imageobjectco"/>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>imageobjectco</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="imageobjectco">
+		<xsl:apply-templates select="imageobject"/>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:apply-templates select="calloutlist"/>
+	</xsl:template>
+
+	<doc:template basename="imageobject" xmlns="">
+		<refpurpose>Process a <doc:db>imageobjectco</doc:db>'s <doc:db>imageobject</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates for <doc:db>imagedata</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="imageobjectco/imageobject">
+		<xsl:apply-templates select="imagedata">
+			<xsl:with-param name="is.imageobjectco" select="true()"/>
+		</xsl:apply-templates>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/citation.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/citation.mod.xsl
new file mode 100644
index 00000000000..da9ffe5fb9a
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/citation.mod.xsl
@@ -0,0 +1,132 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: citation.mod.xsl,v 1.6 2003/12/29 01:30:32 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+
+	<doc:reference id="citation" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: citation.mod.xsl,v 1.6 2003/12/29 01:30:32 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.6">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Citations <filename>citation.mod.xsl</filename></title>
+		<partintro>
+
+			<para>This file contains a single XSL template that maps <doc:db
+			basename="citation">citations</doc:db> to the &LaTeX;
+			<function condition="latex">cite{}</function>. command.</para>
+
+		</partintro>
+	</doc:reference>
+
+	<doc:template basename="citation" xmlns="">
+		<refpurpose> Process <doc:db>citation</doc:db> elements  </refpurpose>
+		<doc:description>
+
+			<para>
+
+			Outputs a <function condition="latex">cite{...}</function> command
+			using the text value of the <doc:db>citation</doc:db>.
+
+			</para>
+
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			&essential_preamble;
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_cited;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+
+	<xsl:template match="citation">
+		<!-- todo: biblio-citation-check -->
+		<xsl:text>\docbooktolatexcite{</xsl:text>
+			<xsl:value-of select="."/>
+		<xsl:text>}{}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Essential preamble for <filename>citation.mod.xsl</filename> support </refpurpose>
+		<doc:description>
+			<para>
+
+				Defines <function
+				condition="latex">docbooktolatexcite</function>. This function
+				helps to integrate <doc:db>bibioentry</doc:db>/@<sgmltag
+				class="attribute">id</sgmltag> and
+				<doc:db>bibioentry</doc:db>/<doc:db>abbrev</doc:db> with
+				&LaTeX;.
+				Also defines <function condition="latex">docbooktolatexbackcite</function>
+				for compatability with <productname>hyperref</productname>'s
+				<productname>backref</productname> functionality.
+
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&preamble;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+
+	<xsl:template name="latex.preamble.essential.citation">
+		<xsl:text>
+			<![CDATA[
+%\usepackage{cite}
+%\renewcommand\citeleft{(}  % parentheses around list
+%\renewcommand\citeright{)} % parentheses around list
+\newcommand{\docbooktolatexcite}[2]{%
+  \@ifundefined{docbooktolatexcite@#1}%
+  {\cite{#1}}%
+  {\def\@docbooktolatextemp{#2}\ifx\@docbooktolatextemp\@empty%
+   \cite{\@nameuse{docbooktolatexcite@#1}}%
+   \else\cite[#2]{\@nameuse{docbooktolatexcite@#1}}%
+   \fi%
+  }%
+}
+\newcommand{\docbooktolatexbackcite}[1]{%
+  \ifx\Hy@backout\@undefined\else%
+    \@ifundefined{docbooktolatexcite@#1}{%
+      % emit warning?
+    }{%
+      \ifBR@verbose%
+        \PackageInfo{backref}{back cite \string`#1\string' as \string`\@nameuse{docbooktolatexcite@#1}\string'}%
+      \fi%
+      \Hy@backout{\@nameuse{docbooktolatexcite@#1}}%
+    }%
+  \fi%
+}
+]]>
+		</xsl:text>
+	</xsl:template>
+
+</xsl:stylesheet>
+
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/af.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/af.xml
new file mode 100644
index 00000000000..93acec17d50
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/af.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="af" english-language-name="Afrikaans">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/af.xml -->
+  <l:gentext key="Abstract" text="Samevatting"/>
+  <l:gentext key="abstract" text="samevatting"/>
+  <l:gentext key="Answer" text="Antwoord:"/>
+  <l:gentext key="answer" text="antwoord:"/>
+  <l:gentext key="Appendix" text="Aanhangsel"/>
+  <l:gentext key="appendix" text="aanhangsel"/>
+  <l:gentext key="Article" text="Artikel"/>
+  <l:gentext key="article" text="artikel"/>
+  <l:gentext key="Bibliography" text="Bibliografie"/>
+  <l:gentext key="bibliography" text="bibliografie"/>
+  <l:gentext key="Book" text="Boek"/>
+  <l:gentext key="book" text="boek"/>
+  <l:gentext key="Caution" text="Pas op"/>
+  <l:gentext key="caution" text="pas op"/>
+  <l:gentext key="CAUTION" text="PAS OP"/>
+  <l:gentext key="Chapter" text="Hoofdstuk"/>
+  <l:gentext key="chapter" text="hoofdstuk"/>
+  <l:gentext key="Colophon" text="Kolifon"/>
+  <l:gentext key="colophon" text="kolifon"/>
+  <l:gentext key="Copyright" text="Kopie reg"/>
+  <l:gentext key="copyright" text="kopie reg"/>
+  <l:gentext key="Dedication" text="Opgedra aan"/>
+  <l:gentext key="dedication" text="opgedra aan"/>
+  <l:gentext key="Edition" text="Uitgawe"/>
+  <l:gentext key="edition" text="uitgawe"/>
+  <l:gentext key="Equation" text="Vergelyking"/>
+  <l:gentext key="equation" text="vergelyking"/>
+  <l:gentext key="Example" text="Voorbeeld"/>
+  <l:gentext key="example" text="voorbeeld"/>
+  <l:gentext key="Figure" text="Figuur"/>
+  <l:gentext key="figure" text="figuur"/>
+  <l:gentext key="Glossary" text="Woordlys"/>
+  <l:gentext key="glossary" text="woordlys"/>
+  <l:gentext key="GlossSee" text="WoordelysSien"/>
+  <l:gentext key="glosssee" text="woordelyssien"/>
+  <l:gentext key="GlossSeeAlso" text="WoordelysSienOok"/>
+  <l:gentext key="glossseealso" text="woordelyssienook"/>
+  <l:gentext key="IMPORTANT" text="BELANGRIK"/>
+  <l:gentext key="Important" text="Belangrik"/>
+  <l:gentext key="important" text="belangrik"/>
+  <l:gentext key="Index" text="Indeks"/>
+  <l:gentext key="index" text="indeks"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="isbn"/>
+  <l:gentext key="LegalNotice" text="RegsKennisgewing"/>
+  <l:gentext key="legalnotice" text="regskennisgewing"/>
+  <l:gentext key="MsgAud" text="Teikengroep"/>
+  <l:gentext key="msgaud" text="teikengroep"/>
+  <l:gentext key="MsgLevel" text="Vlak"/>
+  <l:gentext key="msglevel" text="vlak"/>
+  <l:gentext key="MsgOrig" text="Herkoms"/>
+  <l:gentext key="msgorig" text="herkoms"/>
+  <l:gentext key="note" text="opmerking"/>
+  <l:gentext key="NOTE" text="OPMERKING"/>
+  <l:gentext key="Note" text="Opmerking"/>
+  <l:gentext key="Part" text="Deel"/>
+  <l:gentext key="part" text="deel"/>
+  <l:gentext key="Preface" text="Voorwoord"/>
+  <l:gentext key="preface" text="voorwoord"/>
+  <l:gentext key="Procedure" text="Prosedure"/>
+  <l:gentext key="procedure" text="prosedure"/>
+  <l:gentext key="ProductionSet" text="ProduksieStel"/>
+  <l:gentext key="Published" text="Uitgegee"/>
+  <l:gentext key="published" text="uitgegee"/>
+  <l:gentext key="Question" text="Vraag:"/>
+  <l:gentext key="question" text="vraag:"/>
+  <l:gentext key="RefEntry" text="Verwysingslemma"/>
+  <l:gentext key="refentry" text="verwysingslemma"/>
+  <l:gentext key="Reference" text="Verwysing"/>
+  <l:gentext key="reference" text="verwysing"/>
+  <l:gentext key="RefName" text="Verwysingsnaam"/>
+  <l:gentext key="refname" text="verwysingsnaam"/>
+  <l:gentext key="RefSection" text="Verwysingsparagraaf"/>
+  <l:gentext key="refsection" text="verwysingsparagraaf"/>
+  <l:gentext key="RefSynopsisDiv" text="Verwysingsamevatting"/>
+  <l:gentext key="refsynopsisdiv" text="verwysingsamevatting"/>
+  <l:gentext key="RevHistory" text="Hersiening geskiedenis"/>
+  <l:gentext key="revhistory" text="hersiening geskiedenis"/>
+  <l:gentext key="Revision" text="Hersiening"/>
+  <l:gentext key="revision" text="hersiening"/>
+  <l:gentext key="sect1" text="Paragraaf"/>
+  <l:gentext key="sect2" text="Paragraaf"/>
+  <l:gentext key="sect3" text="Paragraaf"/>
+  <l:gentext key="sect4" text="Paragraaf"/>
+  <l:gentext key="sect5" text="Paragraaf"/>
+  <l:gentext key="Section" text="Paragraaf"/>
+  <l:gentext key="section" text="paragraaf"/>
+  <l:gentext key="see" text="sien"/>
+  <l:gentext key="See" text="Sien"/>
+  <l:gentext key="Seealso" text="Sien ook"/>
+  <l:gentext key="seealso" text="sien ook"/>
+  <l:gentext key="SeeAlso" text="Sien Ook"/>
+  <l:gentext key="set" text="versameling"/>
+  <l:gentext key="Set" text="Versameling"/>
+  <l:gentext key="SetIndex" text="VersamelingIndeks"/>
+  <l:gentext key="setindex" text="versamelingindeks"/>
+  <l:gentext key="Sidebar" text="Kantbalk"/>
+  <l:gentext key="sidebar" text="kantbalk"/>
+  <l:gentext key="step" text="stap"/>
+  <l:gentext key="Step" text="Stap"/>
+  <l:gentext key="table" text="tabel"/>
+  <l:gentext key="Table" text="Tabel"/>
+  <l:gentext key="TIP" text="LEIDRAAD"/>
+  <l:gentext key="Tip" text="Leidraad"/>
+  <l:gentext key="tip" text="leidraad"/>
+  <l:gentext key="WARNING" text="WAARSKUWING"/>
+  <l:gentext key="Warning" text="Waarskuwing"/>
+  <l:gentext key="warning" text="waarskuwing"/>
+  <l:gentext key="and" text="en"/>
+  <l:gentext key="by" text="deur"/>
+  <l:gentext key="Edited" text="Geredigeer"/>
+  <l:gentext key="edited" text="geredigeer"/>
+  <l:gentext key="Editedby" text="Geredigeer deur"/>
+  <l:gentext key="editedby" text="geredigeer deur"/>
+  <l:gentext key="in" text="in"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="element bestaan nie"/>
+  <l:gentext key="notes" text="Notas"/>
+  <l:gentext key="Notes" text="notas"/>
+  <l:gentext key="Pgs" text="bl."/>
+  <l:gentext key="pgs" text="bl."/>
+  <l:gentext key="Revisedby" text="Hersien deur"/>
+  <l:gentext key="revisedby" text="hersien deur"/>
+  <l:gentext key="TableNotes" text="TabelOpmerking"/>
+  <l:gentext key="tablenotes" text="tabelopmerking"/>
+  <l:gentext key="TableofContents" text="Inhoudsopgawe"/>
+  <l:gentext key="tableofcontents" text="inhoudsopgawe"/>
+  <l:gentext key="unexpectedelementname" text="onverwagte element naam"/>
+  <l:gentext key="unsupported" text="nie geondersteun"/>
+  <l:gentext key="xrefto" text="verwysing na"/>
+  <l:gentext key="listofequations" text="lys van vergelykings"/>
+  <l:gentext key="ListofEquations" text="Lys van vergelykings"/>
+  <l:gentext key="ListofExamples" text="Lys van voorbeelde"/>
+  <l:gentext key="listofexamples" text="lys van voorbeelde"/>
+  <l:gentext key="ListofFigures" text="Lys van figure"/>
+  <l:gentext key="listoffigures" text="lys van figure"/>
+  <l:gentext key="listoftables" text="lys van tabelle"/>
+  <l:gentext key="ListofTables" text="Lys van tabelle"/>
+  <l:gentext key="ListofUnknown" text="Lys van onbekende tipes"/>
+  <l:gentext key="listofunknown" text="lys van onbekende tipes"/>
+  <l:gentext key="nav-home" text="Begin"/>
+  <l:gentext key="nav-next" text="Volgende"/>
+  <l:gentext key="nav-next-sibling" text="Verder vooruit"/>
+  <l:gentext key="nav-prev" text="Terug"/>
+  <l:gentext key="nav-prev-sibling" text="Verder terug"/>
+  <l:gentext key="nav-up" text="Boontoe"/>
+  <l:gentext key="Draft" text="Proef"/>
+  <l:gentext key="above" text="bo"/>
+  <l:gentext key="below" text="onder"/>
+  <l:gentext key="sectioncalled" text="die seksie genaamd"/>
+  <l:gentext key="index symbols" text="indeks simbole"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/af.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Aanhangsel %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Hoofdstuk %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Vergelyking %n. %t"/>
+    <l:template name="example" text="Voorbeeld %n. %t"/>
+    <l:template name="figure" text="Figuur %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Deel %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Prosedure&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="ProduksieStel&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabel %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Aanhangsel %n. %t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="Hoofdstuk %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Antwoord:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Vraag:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Vraag:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="section" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="die seksie genaamd &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Antwoord:&#160;%n"/>
+    <l:template name="appendix" text="Aanhangsel&#160;%n"/>
+    <l:template name="bridgehead" text="Paragraaf&#160;%n"/>
+    <l:template name="chapter" text="Hoofdstuk&#160;%n"/>
+    <l:template name="equation" text="Vergelyking&#160;%n"/>
+    <l:template name="example" text="Voorbeeld&#160;%n"/>
+    <l:template name="figure" text="Figuur&#160;%n"/>
+    <l:template name="part" text="Deel&#160;%n"/>
+    <l:template name="procedure" text="Prosedure&#160;%n"/>
+    <l:template name="productionset" text="ProduksieStel&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Vraag:&#160;%n"/>
+    <l:template name="question" text="Vraag:&#160;%n"/>
+    <l:template name="sect1" text="Paragraaf&#160;%n"/>
+    <l:template name="sect2" text="Paragraaf&#160;%n"/>
+    <l:template name="sect3" text="Paragraaf&#160;%n"/>
+    <l:template name="sect4" text="Paragraaf&#160;%n"/>
+    <l:template name="sect5" text="Paragraaf&#160;%n"/>
+    <l:template name="section" text="Paragraaf&#160;%n"/>
+    <l:template name="table" text="Tabel&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Aanhangsel&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Hoofdstuk&#160;%n, %t"/>
+    <l:template name="equation" text="Vergelyking&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Voorbeeld&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figuur&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Deel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Prosedure&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="ProduksieStel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="die seksie genaamd &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabel&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" en "/>
+    <l:template name="seplast" text=", en "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="WoordelysSien "/>
+    <l:template name="seealso" text="WoordelysSienOok "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Teikengroep: "/>
+    <l:template name="MsgLevel" text="Vlak: "/>
+    <l:template name="MsgOrig" text="Herkoms: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0436 Afrikaans"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/ar.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/ar.xml
new file mode 100644
index 00000000000..bd69a54cc06
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/ar.xml
@@ -0,0 +1,492 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="ar" english-language-name="Arabic">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ar.xml -->
+  <l:gentext key="Abstract" text="&#1582;&#1604;&#1575;&#1589;&#1577;"/>
+  <l:gentext key="abstract" text="&#1582;&#1604;&#1575;&#1589;&#1577;"/>
+  <l:gentext key="Answer" text="&#1580;:"/>
+  <l:gentext key="answer" text="&#1580;:"/>
+  <l:gentext key="Appendix" text="&#1605;&#1604;&#1581;&#1602;"/>
+  <l:gentext key="appendix" text="&#1605;&#1604;&#1581;&#1602;"/>
+  <l:gentext key="Article" text="&#1605;&#1602;&#1575;&#1604;"/>
+  <l:gentext key="article" text="&#1605;&#1602;&#1575;&#1604;"/>
+  <l:gentext key="Bibliography" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1605;&#1585;&#1575;&#1580;&#1593;"/>
+  <l:gentext key="bibliography" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1605;&#1585;&#1575;&#1580;&#1593;"/>
+  <l:gentext key="Book" text="&#1603;&#1578;&#1575;&#1576;"/>
+  <l:gentext key="book" text="&#1603;&#1578;&#1575;&#1576;"/>
+  <l:gentext key="CAUTION" text="&#1578;&#1581;&#1584;&#1610;&#1585;"/>
+  <l:gentext key="Caution" text="&#1578;&#1581;&#1584;&#1610;&#1585;"/>
+  <l:gentext key="caution" text="&#1578;&#1581;&#1584;&#1610;&#1585;"/>
+  <l:gentext key="Chapter" text="&#1601;&#1589;&#1604;"/>
+  <l:gentext key="chapter" text="&#1601;&#1589;&#1604;"/>
+  <l:gentext key="Colophon" text="&#1575;&#1604;&#1606;&#1575;&#1588;&#1585;"/>
+  <l:gentext key="colophon" text="&#1575;&#1604;&#1606;&#1575;&#1588;&#1585;"/>
+  <l:gentext key="Copyright" text="&#1581;&#1602;&#1608;&#1602; &#1575;&#1604;&#1606;&#1588;&#1585;"/>
+  <l:gentext key="copyright" text="&#1581;&#1602;&#1608;&#1602; &#1575;&#1604;&#1606;&#1588;&#1585;"/>
+  <l:gentext key="Dedication" text="&#1573;&#1607;&#1583;&#1575;&#1569;"/>
+  <l:gentext key="dedication" text="&#1573;&#1607;&#1583;&#1575;&#1569;"/>
+  <l:gentext key="Edition" text="&#1606;&#1587;&#1582;&#1577;"/>
+  <l:gentext key="edition" text="&#1606;&#1587;&#1582;&#1577;"/>
+  <l:gentext key="Equation" text="&#1605;&#1593;&#1575;&#1583;&#1604;&#1577;"/>
+  <l:gentext key="equation" text="&#1605;&#1593;&#1575;&#1583;&#1604;&#1577;"/>
+  <l:gentext key="Example" text="&#1605;&#1579;&#1575;&#1604;"/>
+  <l:gentext key="example" text="&#1605;&#1579;&#1575;&#1604;"/>
+  <l:gentext key="Figure" text="&#1588;&#1603;&#1604;"/>
+  <l:gentext key="figure" text="&#1588;&#1603;&#1604;"/>
+  <l:gentext key="Glossary" text="&#1602;&#1575;&#1605;&#1608;&#1587; &#1575;&#1604;&#1605;&#1601;&#1585;&#1583;&#1575;&#1578;"/>
+  <l:gentext key="glossary" text="&#1602;&#1575;&#1605;&#1608;&#1587; &#1575;&#1604;&#1605;&#1601;&#1585;&#1583;&#1575;&#1578;"/>
+  <l:gentext key="GlossSee" text="&#1575;&#1606;&#1592;&#1585;"/>
+  <l:gentext key="glosssee" text="&#1575;&#1606;&#1592;&#1585;"/>
+  <l:gentext key="GlossSeeAlso" text="&#1575;&#1606;&#1592;&#1585; &#1571;&#1610;&#1590;&#1575;&#1611;"/>
+  <l:gentext key="glossseealso" text="&#1575;&#1606;&#1592;&#1585; &#1571;&#1610;&#1590;&#1575;&#1611;"/>
+  <l:gentext key="IMPORTANT" text="&#1607;&#1575;&#1605;"/>
+  <l:gentext key="important" text="&#1607;&#1575;&#1605;"/>
+  <l:gentext key="Important" text="&#1607;&#1575;&#1605;"/>
+  <l:gentext key="Index" text="&#1601;&#1607;&#1585;&#1587;"/>
+  <l:gentext key="index" text="&#1601;&#1607;&#1585;&#1587;"/>
+  <l:gentext key="ISBN" text="&#1575;&#1604;&#1578;&#1585;&#1602;&#1610;&#1605; &#1575;&#1604;&#1593;&#1575;&#1604;&#1605;&#1610; &#1575;&#1604;&#1602;&#1610;&#1575;&#1587;&#1610; &#1604;&#1604;&#1603;&#1578;&#1575;&#1576;"/>
+  <l:gentext key="isbn" text="&#1575;&#1604;&#1578;&#1585;&#1602;&#1610;&#1605; &#1575;&#1604;&#1593;&#1575;&#1604;&#1605;&#1610; &#1575;&#1604;&#1602;&#1610;&#1575;&#1587;&#1610; &#1604;&#1604;&#1603;&#1578;&#1575;&#1576;"/>
+  <l:gentext key="LegalNotice" text="&#1605;&#1604;&#1575;&#1581;&#1592;&#1577; &#1602;&#1575;&#1606;&#1608;&#1606;&#1610;&#1577;"/>
+  <l:gentext key="legalnotice" text="&#1605;&#1604;&#1575;&#1581;&#1592;&#1577; &#1602;&#1575;&#1606;&#1608;&#1606;&#1610;&#1577;"/>
+  <l:gentext key="MsgAud" text="&#1575;&#1604;&#1580;&#1605;&#1607;&#1608;&#1585;"/>
+  <l:gentext key="msgaud" text="&#1575;&#1604;&#1580;&#1605;&#1607;&#1608;&#1585;"/>
+  <l:gentext key="MsgLevel" text="&#1575;&#1604;&#1605;&#1587;&#1578;&#1608;&#1609;"/>
+  <l:gentext key="msglevel" text="&#1575;&#1604;&#1605;&#1587;&#1578;&#1608;&#1609;"/>
+  <l:gentext key="MsgOrig" text="&#1575;&#1604;&#1605;&#1589;&#1583;&#1585;"/>
+  <l:gentext key="msgorig" text="&#1575;&#1604;&#1605;&#1589;&#1583;&#1585;"/>
+  <l:gentext key="NOTE" text="&#1605;&#1604;&#1575;&#1581;&#1592;&#1577;"/>
+  <l:gentext key="Note" text="&#1605;&#1604;&#1575;&#1581;&#1592;&#1577;"/>
+  <l:gentext key="note" text="&#1605;&#1604;&#1575;&#1581;&#1592;&#1577;"/>
+  <l:gentext key="Part" text="&#1580;&#1586;&#1569;"/>
+  <l:gentext key="part" text="&#1580;&#1586;&#1569;"/>
+  <l:gentext key="Preface" text="&#1605;&#1602;&#1583;&#1605;&#1577;"/>
+  <l:gentext key="preface" text="&#1605;&#1602;&#1583;&#1605;&#1577;"/>
+  <l:gentext key="Procedure" text="&#1573;&#1580;&#1585;&#1575;&#1569;"/>
+  <l:gentext key="procedure" text="&#1573;&#1580;&#1585;&#1575;&#1569;"/>
+  <l:gentext key="ProductionSet" text="&#1605;&#1606;&#1578;&#1580;"/>
+  <l:gentext key="Published" text="&#1605;&#1606;&#1588;&#1608;&#1585;"/>
+  <l:gentext key="published" text="&#1605;&#1606;&#1588;&#1608;&#1585;"/>
+  <l:gentext key="Question" text="&#1587;:"/>
+  <l:gentext key="question" text="&#1587;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#1605;&#1585;&#1580;&#1593;"/>
+  <l:gentext key="reference" text="&#1605;&#1585;&#1580;&#1593;"/>
+  <l:gentext key="RefName" text="&#1575;&#1604;&#1575;&#1587;&#1605;"/>
+  <l:gentext key="refname" text="&#1575;&#1604;&#1575;&#1587;&#1605;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#1575;&#1604;&#1605;&#1582;&#1578;&#1589;&#1585;"/>
+  <l:gentext key="refsynopsisdiv" text="&#1575;&#1604;&#1605;&#1582;&#1578;&#1589;&#1585;"/>
+  <l:gentext key="RevHistory" text="&#1578;&#1575;&#1585;&#1610;&#1582; &#1575;&#1604;&#1605;&#1585;&#1575;&#1580;&#1593;&#1577;"/>
+  <l:gentext key="revhistory" text="&#1578;&#1575;&#1585;&#1610;&#1582; &#1575;&#1604;&#1605;&#1585;&#1575;&#1580;&#1593;&#1577;"/>
+  <l:gentext key="revision" text="&#1605;&#1585;&#1575;&#1580;&#1593;&#1577;"/>
+  <l:gentext key="Revision" text="&#1605;&#1585;&#1575;&#1580;&#1593;&#1577;"/>
+  <l:gentext key="sect1" text="&#1602;&#1587;&#1605;"/>
+  <l:gentext key="sect2" text="&#1602;&#1587;&#1605;"/>
+  <l:gentext key="sect3" text="&#1602;&#1587;&#1605;"/>
+  <l:gentext key="sect4" text="&#1602;&#1587;&#1605;"/>
+  <l:gentext key="sect5" text="&#1602;&#1587;&#1605;"/>
+  <l:gentext key="section" text="&#1602;&#1587;&#1605;"/>
+  <l:gentext key="Section" text="&#1602;&#1587;&#1605;"/>
+  <l:gentext key="see" text="&#1575;&#1587;&#1578;&#1593;&#1585;&#1590;"/>
+  <l:gentext key="seealso" text="&#1575;&#1587;&#1578;&#1593;&#1585;&#1590; &#1571;&#1610;&#1590;&#1575;&#1611;"/>
+  <l:gentext key="set" text="&#1605;&#1580;&#1605;&#1608;&#1593;&#1577;"/>
+  <l:gentext key="Set" text="&#1605;&#1580;&#1605;&#1608;&#1593;&#1577;"/>
+  <l:gentext key="setindex" text="&#1601;&#1607;&#1585;&#1587; &#1575;&#1604;&#1605;&#1580;&#1605;&#1608;&#1593;&#1577;"/>
+  <l:gentext key="SetIndex" text="&#1601;&#1607;&#1585;&#1587; &#1575;&#1604;&#1605;&#1580;&#1605;&#1608;&#1593;&#1577;"/>
+  <l:gentext key="Sidebar" text="&#1575;&#1604;&#1588;&#1585;&#1610;&#1591; &#1575;&#1604;&#1580;&#1575;&#1606;&#1576;&#1610;"/>
+  <l:gentext key="sidebar" text="&#1575;&#1604;&#1588;&#1585;&#1610;&#1591; &#1575;&#1604;&#1580;&#1575;&#1606;&#1576;&#1610;"/>
+  <l:gentext key="step" text="&#1582;&#1591;&#1608;&#1577;"/>
+  <l:gentext key="Step" text="&#1582;&#1591;&#1608;&#1577;"/>
+  <l:gentext key="Table" text="&#1580;&#1583;&#1608;&#1604;"/>
+  <l:gentext key="table" text="&#1580;&#1583;&#1608;&#1604;"/>
+  <l:gentext key="tip" text="&#1601;&#1603;&#1585;&#1577; &#1605;&#1601;&#1610;&#1583;&#1577;"/>
+  <l:gentext key="TIP" text="&#1601;&#1603;&#1585;&#1577; &#1605;&#1601;&#1610;&#1583;&#1577;"/>
+  <l:gentext key="Tip" text="&#1601;&#1603;&#1585;&#1577; &#1605;&#1601;&#1610;&#1583;&#1577;"/>
+  <l:gentext key="Warning" text="&#1578;&#1606;&#1576;&#1610;&#1607;"/>
+  <l:gentext key="warning" text="&#1578;&#1606;&#1576;&#1610;&#1607;"/>
+  <l:gentext key="WARNING" text="&#1578;&#1606;&#1576;&#1610;&#1607;"/>
+  <l:gentext key="and" text="&#1608;"/>
+  <l:gentext key="by" text="&#1576;&#1608;&#1575;&#1587;&#1591;&#1577;"/>
+  <l:gentext key="Edited" text="&#1605;&#1593;&#1583;&#1604;"/>
+  <l:gentext key="edited" text="&#1605;&#1593;&#1583;&#1604;"/>
+  <l:gentext key="Editedby" text="&#1605;&#1593;&#1583;&#1604; &#1576;&#1608;&#1575;&#1587;&#1591;&#1577;"/>
+  <l:gentext key="editedby" text="&#1605;&#1593;&#1583;&#1604; &#1576;&#1608;&#1575;&#1587;&#1591;&#1577;"/>
+  <l:gentext key="in" text="&#1601;&#1610;"/>
+  <l:gentext key="lastlistcomma" text="&#1548;"/>
+  <l:gentext key="listcomma" text="&#1548;"/>
+  <l:gentext key="nonexistantelement" text="&#1593;&#1606;&#1589;&#1585; &#1605;&#1601;&#1602;&#1608;&#1583;"/>
+  <l:gentext key="notes" text="&#1605;&#1604;&#1575;&#1581;&#1592;&#1575;&#1578;"/>
+  <l:gentext key="Notes" text="&#1605;&#1604;&#1575;&#1581;&#1592;&#1575;&#1578;"/>
+  <l:gentext key="Pgs" text="&#1589;&#1601;&#1581;&#1575;&#1578;"/>
+  <l:gentext key="pgs" text="&#1589;&#1601;&#1581;&#1575;&#1578;"/>
+  <l:gentext key="Revisedby" text="&#1578;&#1605;&#1578; &#1575;&#1604;&#1605;&#1585;&#1575;&#1580;&#1593;&#1577; &#1576;&#1608;&#1575;&#1587;&#1591;&#1577;: "/>
+  <l:gentext key="revisedby" text="&#1578;&#1605;&#1578; &#1575;&#1604;&#1605;&#1585;&#1575;&#1580;&#1593;&#1577; &#1576;&#1608;&#1575;&#1587;&#1591;&#1577;: "/>
+  <l:gentext key="TableNotes" text="&#1605;&#1604;&#1575;&#1581;&#1592;&#1575;&#1578;"/>
+  <l:gentext key="tablenotes" text="&#1605;&#1604;&#1575;&#1581;&#1592;&#1575;&#1578;"/>
+  <l:gentext key="TableofContents" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1605;&#1581;&#1578;&#1608;&#1610;&#1575;&#1578;"/>
+  <l:gentext key="tableofcontents" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1605;&#1581;&#1578;&#1608;&#1610;&#1575;&#1578;"/>
+  <l:gentext key="unexpectedelementname" text="&#1575;&#1587;&#1605; &#1593;&#1606;&#1589;&#1585; &#1594;&#1610;&#1585; &#1605;&#1578;&#1608;&#1602;&#1593;"/>
+  <l:gentext key="unsupported" text="&#1594;&#1610;&#1585; &#1605;&#1583;&#1593;&#1608;&#1605;"/>
+  <l:gentext key="xrefto" text="&#1573;&#1588;&#1575;&#1585;&#1577; &#1573;&#1604;&#1609;"/>
+  <l:gentext key="listofequations" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1605;&#1593;&#1575;&#1583;&#1604;&#1575;&#1578;"/>
+  <l:gentext key="ListofEquations" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1605;&#1593;&#1575;&#1583;&#1604;&#1575;&#1578;"/>
+  <l:gentext key="ListofExamples" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1571;&#1605;&#1579;&#1604;&#1577;"/>
+  <l:gentext key="listofexamples" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1571;&#1605;&#1579;&#1604;&#1577;"/>
+  <l:gentext key="ListofFigures" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1571;&#1588;&#1603;&#1575;&#1604;"/>
+  <l:gentext key="listoffigures" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1571;&#1588;&#1603;&#1575;&#1604;"/>
+  <l:gentext key="ListofProcedures" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1573;&#1580;&#1585;&#1575;&#1569;&#1575;&#1578;"/>
+  <l:gentext key="listofprocedures" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1573;&#1580;&#1585;&#1575;&#1569;&#1575;&#1578;"/>
+  <l:gentext key="listoftables" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1580;&#1583;&#1575;&#1608;&#1604;"/>
+  <l:gentext key="ListofTables" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1580;&#1583;&#1575;&#1608;&#1604;"/>
+  <l:gentext key="ListofUnknown" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1605;&#1580;&#1607;&#1608;&#1604;&#1575;&#1578;"/>
+  <l:gentext key="listofunknown" text="&#1602;&#1575;&#1574;&#1605;&#1577; &#1575;&#1604;&#1605;&#1580;&#1607;&#1608;&#1604;&#1575;&#1578;"/>
+  <l:gentext key="nav-home" text="&#1575;&#1604;&#1576;&#1583;&#1575;&#1610;&#1577;"/>
+  <l:gentext key="nav-next" text="&#1575;&#1604;&#1578;&#1575;&#1604;&#1610;"/>
+  <l:gentext key="nav-next-sibling" text="&#1573;&#1604;&#1609; &#1575;&#1604;&#1571;&#1605;&#1575;&#1605;"/>
+  <l:gentext key="nav-prev" text="&#1575;&#1604;&#1587;&#1575;&#1576;&#1602;"/>
+  <l:gentext key="nav-prev-sibling" text="&#1573;&#1604;&#1609; &#1575;&#1604;&#1582;&#1604;&#1601;"/>
+  <l:gentext key="nav-up" text="&#1571;&#1593;&#1604;&#1609;"/>
+  <l:gentext key="nav-toc" text="&#1575;&#1604;&#1601;&#1607;&#1585;&#1587;"/>
+  <l:gentext key="Draft" text="&#1605;&#1587;&#1608;&#1583;&#1577;"/>
+  <l:gentext key="above" text="&#1571;&#1593;&#1604;&#1609;"/>
+  <l:gentext key="below" text="&#1601;&#1610;&#1605;&#1575; &#1610;&#1604;&#1610;"/>
+  <l:gentext key="sectioncalled" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609;"/>
+  <l:gentext key="index symbols" text="&#1575;&#1604;&#1585;&#1605;&#1608;&#1586;"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+  <l:gentext key="hyphenation-character" text="&#8208;"/>
+  <l:gentext key="hyphenation-push-character-count" text="2"/>
+  <l:gentext key="hyphenation-remain-character-count" text="2"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ar.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#1605;&#1604;&#1581;&#1602;&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#1601;&#1589;&#1604;&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#1605;&#1593;&#1575;&#1583;&#1604;&#1577;&#160;%n.&#160;%t"/>
+    <l:template name="example" text="&#1605;&#1579;&#1575;&#1604;&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="&#1588;&#1603;&#1604;&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#1580;&#1586;&#1569;&#160;%n.&#160;%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#1573;&#1580;&#1585;&#1575;&#1569;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="&#1605;&#1606;&#1578;&#1580;&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#1580;&#1583;&#1608;&#1604;&#160;%n.&#160;%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#1605;&#1604;&#1581;&#1602;&#160;%n.&#160;%t"/>
+    <l:template name="article/appendix" text="%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="&#1601;&#1589;&#1604;&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#1580;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#1587;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#1587;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#1580;:&#160;%n"/>
+    <l:template name="appendix" text="&#1605;&#1604;&#1581;&#1602;&#160;%n"/>
+    <l:template name="bridgehead" text="&#1602;&#1587;&#1605;&#160;%n"/>
+    <l:template name="chapter" text="&#1601;&#1589;&#1604;&#160;%n"/>
+    <l:template name="equation" text="&#1605;&#1593;&#1575;&#1583;&#1604;&#1577;&#160;%n"/>
+    <l:template name="example" text="&#1605;&#1579;&#1575;&#1604;&#160;%n"/>
+    <l:template name="figure" text="&#1588;&#1603;&#1604;&#160;%n"/>
+    <l:template name="part" text="&#1580;&#1586;&#1569;&#160;%n"/>
+    <l:template name="procedure" text="&#1573;&#1580;&#1585;&#1575;&#1569;&#160;%n"/>
+    <l:template name="productionset" text="&#1605;&#1606;&#1578;&#1580;&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#1587;:&#160;%n"/>
+    <l:template name="question" text="&#1587;:&#160;%n"/>
+    <l:template name="sect1" text="&#1602;&#1587;&#1605;&#160;%n"/>
+    <l:template name="sect2" text="&#1602;&#1587;&#1605;&#160;%n"/>
+    <l:template name="sect3" text="&#1602;&#1587;&#1605;&#160;%n"/>
+    <l:template name="sect4" text="&#1602;&#1587;&#1605;&#160;%n"/>
+    <l:template name="sect5" text="&#1602;&#1587;&#1605;&#160;%n"/>
+    <l:template name="section" text="&#1602;&#1587;&#1605;&#160;%n"/>
+    <l:template name="table" text="&#1580;&#1583;&#1608;&#1604;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#1605;&#1604;&#1581;&#1602;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#1602;&#1587;&#1605;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="&#1601;&#1589;&#1604;&#160;%n, %t"/>
+    <l:template name="equation" text="&#1605;&#1593;&#1575;&#1583;&#1604;&#1577;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="&#1605;&#1579;&#1575;&#1604;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="&#1588;&#1603;&#1604;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="&#1580;&#1586;&#1569;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="&#1573;&#1580;&#1585;&#1575;&#1569;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="&#1605;&#1606;&#1578;&#1580;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#1602;&#1587;&#1605;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#1602;&#1587;&#1605;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#1602;&#1587;&#1605;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#1602;&#1587;&#1605;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#1602;&#1587;&#1605;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#1602;&#1587;&#1605;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#1575;&#1604;&#1602;&#1587;&#1605; &#1575;&#1604;&#1605;&#1587;&#1605;&#1609; &#8220;%t&#8221;"/>
+    <l:template name="table" text="&#1580;&#1583;&#1608;&#1604;&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text="&#1548; "/>
+    <l:template name="sep2" text=" &#1608; "/>
+    <l:template name="seplast" text="&#1548; &#1608; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#1575;&#1606;&#1592;&#1585; "/>
+    <l:template name="seealso" text="&#1575;&#1606;&#1592;&#1585; &#1571;&#1610;&#1590;&#1575;&#1611; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#1575;&#1604;&#1580;&#1605;&#1607;&#1608;&#1585;: "/>
+    <l:template name="MsgLevel" text="&#1575;&#1604;&#1605;&#1587;&#1578;&#1608;&#1609;: "/>
+    <l:template name="MsgOrig" text="&#1575;&#1604;&#1605;&#1589;&#1583;&#1585;: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d/m/Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="&#1610;&#1606;&#1575;&#1610;&#1585;"/>
+    <l:template name="February" text="&#1601;&#1576;&#1585;&#1575;&#1610;&#1585;"/>
+    <l:template name="March" text="&#1605;&#1575;&#1585;&#1587;"/>
+    <l:template name="April" text="&#1571;&#1576;&#1585;&#1610;&#1604;"/>
+    <l:template name="May" text="&#1605;&#1575;&#1610;&#1608;"/>
+    <l:template name="June" text="&#1610;&#1608;&#1606;&#1610;&#1608;"/>
+    <l:template name="July" text="&#1610;&#1608;&#1604;&#1610;&#1608;"/>
+    <l:template name="August" text="&#1571;&#1594;&#1587;&#1591;&#1587;"/>
+    <l:template name="September" text="&#1587;&#1576;&#1578;&#1605;&#1576;&#1585;"/>
+    <l:template name="October" text="&#1571;&#1603;&#1578;&#1608;&#1576;&#1585;"/>
+    <l:template name="November" text="&#1606;&#1608;&#1601;&#1605;&#1576;&#1585;"/>
+    <l:template name="December" text="&#1583;&#1610;&#1587;&#1605;&#1576;&#1585;"/>
+    <l:template name="Monday" text="&#1575;&#1604;&#1573;&#1579;&#1606;&#1610;&#1606;"/>
+    <l:template name="Tuesday" text="&#1575;&#1604;&#1579;&#1604;&#1575;&#1579;&#1575;&#1569;"/>
+    <l:template name="Wednesday" text="&#1575;&#1604;&#1571;&#1585;&#1576;&#1593;&#1575;&#1569;"/>
+    <l:template name="Thursday" text="&#1575;&#1604;&#1582;&#1605;&#1610;&#1587;"/>
+    <l:template name="Friday" text="&#1575;&#1604;&#1580;&#1605;&#1593;&#1577;"/>
+    <l:template name="Saturday" text="&#1575;&#1604;&#1587;&#1576;&#1578;"/>
+    <l:template name="Sunday" text="&#1575;&#1604;&#1571;&#1581;&#1583;"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="&#1610;&#1606;&#1575;&#1610;&#1585;"/>
+    <l:template name="Feb" text="&#1601;&#1576;&#1585;&#1575;&#1610;&#1585;"/>
+    <l:template name="Mar" text="&#1605;&#1575;&#1585;&#1587;"/>
+    <l:template name="Apr" text="&#1571;&#1576;&#1585;&#1610;&#1604;"/>
+    <l:template name="May" text="&#1605;&#1575;&#1610;&#1608;"/>
+    <l:template name="Jun" text="&#1610;&#1608;&#1606;&#1610;&#1608;"/>
+    <l:template name="Jul" text="&#1610;&#1608;&#1604;&#1610;&#1608;"/>
+    <l:template name="Aug" text="&#1571;&#1594;&#1587;&#1591;&#1587;"/>
+    <l:template name="Sep" text="&#1587;&#1576;&#1578;&#1605;&#1576;&#1585;"/>
+    <l:template name="Oct" text="&#1571;&#1603;&#1578;&#1608;&#1576;&#1585;"/>
+    <l:template name="Nov" text="&#1606;&#1608;&#1601;&#1605;&#1576;&#1585;"/>
+    <l:template name="Dec" text="&#1583;&#1610;&#1587;&#1605;&#1576;&#1585;"/>
+    <l:template name="Mon" text="&#1575;&#1604;&#1573;&#1579;&#1606;&#1610;&#1606;"/>
+    <l:template name="Tue" text="&#1575;&#1604;&#1579;&#1604;&#1575;&#1579;&#1575;&#1569;"/>
+    <l:template name="Wed" text="&#1575;&#1604;&#1571;&#1585;&#1576;&#1593;&#1575;&#1569;"/>
+    <l:template name="Thu" text="&#1575;&#1604;&#1582;&#1605;&#1610;&#1587;"/>
+    <l:template name="Fri" text="&#1575;&#1604;&#1580;&#1605;&#1593;&#1577;"/>
+    <l:template name="Sat" text="&#1575;&#1604;&#1587;&#1576;&#1578;"/>
+    <l:template name="Sun" text="&#1575;&#1604;&#1571;&#1581;&#1583;"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/bg.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/bg.xml
new file mode 100644
index 00000000000..808a97afb86
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/bg.xml
@@ -0,0 +1,445 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="bg" english-language-name="Bulgarian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/bg.xml -->
+  <l:gentext key="Abstract" text="&#1040;&#1085;&#1086;&#1090;&#1072;&#1094;&#1080;&#1103;"/>
+  <l:gentext key="abstract" text="&#1040;&#1085;&#1086;&#1090;&#1072;&#1094;&#1080;&#1103;"/>
+  <l:gentext key="Answer" text="&#1054;:"/>
+  <l:gentext key="answer" text="&#1054;:"/>
+  <l:gentext key="Appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="appendix" text="&#1087;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Article" text="&#1057;&#1090;&#1072;&#1090;&#1080;&#1103;"/>
+  <l:gentext key="article" text="&#1057;&#1090;&#1072;&#1090;&#1080;&#1103;"/>
+  <l:gentext key="Bibliography" text="&#1051;&#1080;&#1090;&#1077;&#1088;&#1072;&#1090;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="bibliography" text="&#1051;&#1080;&#1090;&#1077;&#1088;&#1072;&#1090;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="Book" text="&#1050;&#1085;&#1080;&#1075;&#1072;"/>
+  <l:gentext key="book" text="&#1050;&#1085;&#1080;&#1075;&#1072;"/>
+  <l:gentext key="CAUTION" text="&#1042;&#1053;&#1048;&#1052;&#1040;&#1053;&#1048;&#1045;"/>
+  <l:gentext key="Caution" text="&#1042;&#1085;&#1080;&#1084;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="caution" text="&#1042;&#1085;&#1080;&#1084;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072;"/>
+  <l:gentext key="chapter" text="&#1075;&#1083;&#1072;&#1074;&#1072;"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="&#1055;&#1086;&#1089;&#1074;&#1077;&#1097;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="dedication" text="&#1055;&#1086;&#1089;&#1074;&#1077;&#1097;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Edition" text="&#1048;&#1079;&#1076;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="edition" text="&#1048;&#1079;&#1076;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;"/>
+  <l:gentext key="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;"/>
+  <l:gentext key="Example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;"/>
+  <l:gentext key="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;"/>
+  <l:gentext key="Figure" text="&#1060;&#1080;&#1075;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="figure" text="&#1060;&#1080;&#1075;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="Glossary" text="&#1058;&#1077;&#1088;&#1084;&#1080;&#1085;&#1086;&#1083;&#1086;&#1075;&#1080;&#1095;&#1077;&#1085; &#1088;&#1077;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="glossary" text="&#1058;&#1077;&#1088;&#1084;&#1080;&#1085;&#1086;&#1083;&#1086;&#1075;&#1080;&#1095;&#1077;&#1085; &#1088;&#1077;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="GlossSee" text="&#1074;&#1078;."/>
+  <l:gentext key="glosssee" text="&#1074;&#1078;."/>
+  <l:gentext key="GlossSeeAlso" text="&#1074;&#1078;. &#1089;&#1098;&#1097;&#1086;"/>
+  <l:gentext key="glossseealso" text="&#1074;&#1078;. &#1089;&#1098;&#1097;&#1086;"/>
+  <l:gentext key="IMPORTANT" text="&#1042;&#1040;&#1046;&#1053;&#1054;"/>
+  <l:gentext key="important" text="&#1042;&#1072;&#1078;&#1085;&#1086;"/>
+  <l:gentext key="Important" text="&#1042;&#1072;&#1078;&#1085;&#1086;"/>
+  <l:gentext key="Index" text="&#1048;&#1085;&#1076;&#1077;&#1082;&#1089;"/>
+  <l:gentext key="index" text="&#1048;&#1085;&#1076;&#1077;&#1082;&#1089;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="&#1040;&#1074;&#1090;&#1086;&#1088;&#1089;&#1082;&#1080; &#1087;&#1088;&#1072;&#1074;&#1072;"/>
+  <l:gentext key="legalnotice" text="&#1040;&#1074;&#1090;&#1086;&#1088;&#1089;&#1082;&#1080; &#1087;&#1088;&#1072;&#1074;&#1072;"/>
+  <l:gentext key="MsgAud" text="Audience"/>
+  <l:gentext key="msgaud" text="Audience"/>
+  <l:gentext key="MsgLevel" text="&#1053;&#1080;&#1074;&#1086;"/>
+  <l:gentext key="msglevel" text="&#1053;&#1080;&#1074;&#1086;"/>
+  <l:gentext key="MsgOrig" text="&#1048;&#1079;&#1090;&#1086;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="msgorig" text="&#1048;&#1079;&#1090;&#1086;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="NOTE" text="&#1047;&#1040;&#1041;&#1045;&#1051;&#1045;&#1046;&#1050;&#1040;"/>
+  <l:gentext key="Note" text="&#1047;&#1072;&#1073;&#1077;&#1083;&#1077;&#1078;&#1082;&#1072;"/>
+  <l:gentext key="note" text="&#1047;&#1072;&#1073;&#1077;&#1083;&#1077;&#1078;&#1082;&#1072;"/>
+  <l:gentext key="Part" text="&#1063;&#1072;&#1089;&#1090;"/>
+  <l:gentext key="part" text="&#1063;&#1072;&#1089;&#1090;"/>
+  <l:gentext key="Preface" text="&#1055;&#1088;&#1077;&#1076;&#1075;&#1086;&#1074;&#1086;&#1088;"/>
+  <l:gentext key="preface" text="&#1055;&#1088;&#1077;&#1076;&#1075;&#1086;&#1074;&#1086;&#1088;"/>
+  <l:gentext key="Procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="&#1048;&#1079;&#1076;&#1072;&#1076;&#1077;&#1085;"/>
+  <l:gentext key="published" text="&#1048;&#1079;&#1076;&#1072;&#1076;&#1077;&#1085;"/>
+  <l:gentext key="Question" text="&#1042;:"/>
+  <l:gentext key="question" text="&#1042;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#1057;&#1087;&#1088;&#1072;&#1074;&#1086;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="reference" text="&#1057;&#1087;&#1088;&#1072;&#1074;&#1086;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="RefName" text="&#1053;&#1072;&#1079;&#1074;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="refname" text="&#1053;&#1072;&#1079;&#1074;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#1057;&#1080;&#1085;&#1090;&#1072;&#1082;&#1089;&#1080;&#1089;"/>
+  <l:gentext key="refsynopsisdiv" text="&#1057;&#1080;&#1085;&#1090;&#1072;&#1082;&#1089;&#1080;&#1089;"/>
+  <l:gentext key="RevHistory" text="&#1055;&#1088;&#1086;&#1084;&#1077;&#1085;&#1080;"/>
+  <l:gentext key="revhistory" text="&#1055;&#1088;&#1086;&#1084;&#1077;&#1085;&#1080;"/>
+  <l:gentext key="revision" text="&#1048;&#1079;&#1076;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Revision" text="&#1048;&#1079;&#1076;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="sect1" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="sect2" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="sect3" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="sect4" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="sect5" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="section" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="Section" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="see" text="&#1074;&#1078;."/>
+  <l:gentext key="seealso" text="&#1074;&#1078;. &#1089;&#1098;&#1097;&#1086;"/>
+  <l:gentext key="set" text="&#1059;&#1082;&#1072;&#1079;&#1072;&#1090;&#1077;&#1083;"/>
+  <l:gentext key="Set" text="&#1059;&#1082;&#1072;&#1079;&#1072;&#1090;&#1077;&#1083;"/>
+  <l:gentext key="setindex" text="&#1059;&#1082;&#1072;&#1079;&#1072;&#1090;&#1077;&#1083;"/>
+  <l:gentext key="SetIndex" text="&#1059;&#1082;&#1072;&#1079;&#1072;&#1090;&#1077;&#1083;"/>
+  <l:gentext key="Sidebar" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#1080;&#1090;&#1077;&#1083;"/>
+  <l:gentext key="sidebar" text="&#1088;&#1072;&#1079;&#1076;&#1077;&#1083;&#1080;&#1090;&#1077;&#1083;"/>
+  <l:gentext key="step" text="&#1057;&#1090;&#1098;&#1087;&#1082;&#1072;"/>
+  <l:gentext key="Step" text="&#1057;&#1090;&#1098;&#1087;&#1082;&#1072;"/>
+  <l:gentext key="Table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072;"/>
+  <l:gentext key="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072;"/>
+  <l:gentext key="tip" text="&#1055;&#1086;&#1079;&#1076;&#1089;&#1082;&#1072;&#1079;&#1082;&#1072;"/>
+  <l:gentext key="TIP" text="&#1055;&#1054;&#1044;&#1057;&#1050;&#1040;&#1047;&#1050;&#1040;"/>
+  <l:gentext key="Tip" text="&#1055;&#1086;&#1079;&#1076;&#1089;&#1082;&#1072;&#1079;&#1082;&#1072;"/>
+  <l:gentext key="Warning" text="&#1042;&#1085;&#1080;&#1084;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="warning" text="&#1042;&#1085;&#1080;&#1084;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="WARNING" text="&#1042;&#1053;&#1048;&#1052;&#1040;&#1053;&#1048;&#1045;"/>
+  <l:gentext key="and" text=""/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="Edited" text="&#1056;&#1077;&#1076;&#1072;&#1082;&#1090;&#1080;&#1088;&#1072;&#1085;&#1086; &#1086;&#1090;"/>
+  <l:gentext key="edited" text="&#1056;&#1077;&#1076;&#1072;&#1082;&#1090;&#1080;&#1088;&#1072;&#1085;&#1086; &#1086;&#1090;"/>
+  <l:gentext key="Editedby" text="&#1056;&#1077;&#1076;&#1072;&#1082;&#1090;&#1080;&#1088;&#1072;&#1085;&#1086; &#1086;&#1090;"/>
+  <l:gentext key="editedby" text="&#1056;&#1077;&#1076;&#1072;&#1082;&#1090;&#1080;&#1088;&#1072;&#1085;&#1086; &#1086;&#1090;"/>
+  <l:gentext key="in" text="&#1074;"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="non-existant element"/>
+  <l:gentext key="notes" text="&#1047;&#1072;&#1073;&#1077;&#1083;&#1077;&#1078;&#1082;&#1080;"/>
+  <l:gentext key="Notes" text="&#1047;&#1072;&#1073;&#1077;&#1083;&#1077;&#1078;&#1082;&#1080;"/>
+  <l:gentext key="Pgs" text="&#1089;&#1090;&#1088;."/>
+  <l:gentext key="pgs" text="&#1089;&#1090;&#1088;."/>
+  <l:gentext key="Revisedby" text="&#1054;&#1076;&#1086;&#1073;&#1088;&#1077;&#1085;&#1086; &#1086;&#1090;: "/>
+  <l:gentext key="revisedby" text="&#1054;&#1076;&#1086;&#1073;&#1088;&#1077;&#1085;&#1086; &#1086;&#1090;: "/>
+  <l:gentext key="TableNotes" text="&#1047;&#1072;&#1073;&#1077;&#1083;&#1077;&#1078;&#1082;&#1080;"/>
+  <l:gentext key="tablenotes" text="&#1047;&#1072;&#1073;&#1077;&#1083;&#1077;&#1078;&#1082;&#1080;"/>
+  <l:gentext key="TableofContents" text="&#1057;&#1098;&#1076;&#1098;&#1088;&#1078;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="tableofcontents" text="&#1057;&#1098;&#1076;&#1098;&#1088;&#1078;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="unexpectedelementname" text="unexpected element name"/>
+  <l:gentext key="unsupported" text="unsupported"/>
+  <l:gentext key="xrefto" text="xref to"/>
+  <l:gentext key="listofequations" text="&#1057;&#1087;&#1080;&#1089;&#1098;&#1082; &#1085;&#1072; &#1092;&#1086;&#1088;&#1084;&#1091;&#1083;&#1080;&#1090;&#1077;"/>
+  <l:gentext key="ListofEquations" text="&#1057;&#1087;&#1080;&#1089;&#1098;&#1082; &#1085;&#1072; &#1092;&#1086;&#1088;&#1084;&#1091;&#1083;&#1080;&#1090;&#1077;"/>
+  <l:gentext key="ListofExamples" text="&#1057;&#1087;&#1080;&#1089;&#1098;&#1082; &#1085;&#1072; &#1087;&#1088;&#1080;&#1084;&#1077;&#1088;&#1080;&#1090;&#1077;"/>
+  <l:gentext key="listofexamples" text="&#1057;&#1087;&#1080;&#1089;&#1098;&#1082; &#1085;&#1072; &#1087;&#1088;&#1080;&#1084;&#1077;&#1088;&#1080;&#1090;&#1077;"/>
+  <l:gentext key="ListofFigures" text="&#1057;&#1087;&#1080;&#1089;&#1098;&#1082; &#1085;&#1072; &#1092;&#1080;&#1075;&#1091;&#1088;&#1080;&#1090;&#1077;"/>
+  <l:gentext key="listoffigures" text="&#1057;&#1087;&#1080;&#1089;&#1098;&#1082; &#1085;&#1072; &#1092;&#1080;&#1075;&#1091;&#1088;&#1080;&#1090;&#1077;"/>
+  <l:gentext key="listoftables" text="&#1057;&#1087;&#1080;&#1089;&#1098;&#1082; &#1085;&#1072; &#1090;&#1072;&#1073;&#1083;&#1080;&#1094;&#1080;&#1090;&#1077;"/>
+  <l:gentext key="ListofTables" text="&#1057;&#1087;&#1080;&#1089;&#1098;&#1082; &#1085;&#1072; &#1090;&#1072;&#1073;&#1083;&#1080;&#1094;&#1080;&#1090;&#1077;"/>
+  <l:gentext key="ListofUnknown" text="&#1053;&#1077;&#1086;&#1087;&#1088;&#1077;&#1076;&#1077;&#1083;&#1077;&#1085; &#1089;&#1087;&#1080;&#1089;&#1098;&#1082;"/>
+  <l:gentext key="listofunknown" text="&#1053;&#1077;&#1086;&#1087;&#1088;&#1077;&#1076;&#1077;&#1083;&#1077;&#1085; &#1089;&#1087;&#1080;&#1089;&#1098;&#1082;"/>
+  <l:gentext key="nav-home" text="&#1053;&#1072;&#1095;&#1072;&#1083;&#1086;"/>
+  <l:gentext key="nav-next" text="&#1057;&#1083;&#1077;&#1076;&#1074;&#1072;&#1097;&#1072; &#1089;&#1090;&#1088;&#1072;&#1085;&#1080;&#1094;&#1072;"/>
+  <l:gentext key="nav-next-sibling" text="&#1057;&#1083;&#1077;&#1076;&#1074;&#1072;&#1097; &#1088;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="nav-prev" text="&#1055;&#1088;&#1077;&#1076;&#1080;&#1096;&#1085;&#1072; &#1089;&#1090;&#1088;&#1072;&#1085;&#1080;&#1094;&#1072;"/>
+  <l:gentext key="nav-prev-sibling" text="&#1055;&#1088;&#1077;&#1076;&#1080;&#1096;&#1077;&#1085; &#1088;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="nav-up" text="&#1053;&#1072;&#1095;&#1072;&#1083;&#1086; &#1085;&#1072; &#1088;&#1072;&#1079;&#1076;&#1077;&#1083;&#1072;"/>
+  <l:gentext key="nav-toc" text="&#1057;&#1098;&#1076;&#1098;&#1088;&#1078;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Draft" text="&#1063;&#1077;&#1088;&#1085;&#1086;&#1074;&#1072;"/>
+  <l:gentext key="above" text="&#1087;&#1086;-&#1075;&#1086;&#1088;&#1077;"/>
+  <l:gentext key="below" text="&#1087;&#1086;-&#1076;&#1086;&#1083;&#1091;"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="index symbols" text="&#1057;&#1080;&#1084;&#1074;&#1086;&#1083;&#1080;"/>
+  <l:gentext key="lowercase.alpha" text="&#1072;&#1073;&#1074;&#1075;&#1076;&#1077;&#1078;&#1079;&#1080;&#1081;&#1082;&#1083;&#1084;&#1085;&#1086;&#1087;&#1088;&#1089;&#1090;&#1091;&#1092;&#1093;&#1094;&#1095;&#1096;&#1097;&#1098;&#1099;&#1100;&#1101;&#1102;&#1103;"/>
+  <l:gentext key="uppercase.alpha" text="&#1040;&#1041;&#1042;&#1043;&#1044;&#1045;&#1046;&#1047;&#1048;&#1049;&#1050;&#1051;&#1052;&#1053;&#1054;&#1055;&#1056;&#1057;&#1058;&#1059;&#1060;&#1061;&#1062;&#1063;&#1064;&#1065;&#1066;&#1067;&#1068;&#1069;&#1070;&#1071;"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/bg.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="&#1060;&#1080;&#1075;&#1091;&#1088;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#1063;&#1072;&#1089;&#1090;&#160;%n.&#160;%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;&#160;%n.&#160;%t"/>
+    <l:template name="article/appendix" text="%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#1054;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#1042;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#1042;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="section" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#1054;:&#160;%n"/>
+    <l:template name="appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;&#160;%n"/>
+    <l:template name="bridgehead" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072;&#160;%n"/>
+    <l:template name="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;&#160;%n"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;&#160;%n"/>
+    <l:template name="figure" text="&#1060;&#1080;&#1075;&#1091;&#1088;&#1072;&#160;%n"/>
+    <l:template name="part" text="&#1063;&#1072;&#1089;&#1090;&#160;%n"/>
+    <l:template name="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#1042;:&#160;%n"/>
+    <l:template name="question" text="&#1042;:&#160;%n"/>
+    <l:template name="sect1" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="sect2" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="sect3" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="sect4" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="sect5" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="section" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072;&#160;%n, %t"/>
+    <l:template name="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="&#1060;&#1080;&#1075;&#1091;&#1088;&#1072;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="&#1063;&#1072;&#1089;&#1090;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072;&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text="  "/>
+    <l:template name="seplast" text=",  "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#1074;&#1078;. "/>
+    <l:template name="seealso" text="&#1074;&#1078;. &#1089;&#1098;&#1097;&#1086; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Audience: "/>
+    <l:template name="MsgLevel" text="&#1053;&#1080;&#1074;&#1086;: "/>
+    <l:template name="MsgOrig" text="&#1048;&#1079;&#1090;&#1086;&#1095;&#1085;&#1080;&#1082;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0402 Bulgarian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/bn.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/bn.xml
new file mode 100644
index 00000000000..1640fc7c395
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/bn.xml
@@ -0,0 +1,504 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="bn" english-language-name="Bangla">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/bn.xml -->
+  <l:gentext key="Abstract" text="&#2488;&#2494;&#2480;&#2488;&#2434;&#2453;&#2509;&#2487;&#2503;&#2474;"/>
+  <l:gentext key="abstract" text="&#2488;&#2494;&#2480;&#2488;&#2434;&#2453;&#2509;&#2487;&#2503;&#2474;"/>
+  <l:gentext key="Answer" text="&#2441;&#2468;&#2509;&#2468;&#2480;:"/>
+  <l:gentext key="answer" text="&#2441;&#2468;&#2509;&#2468;&#2480;:"/>
+  <l:gentext key="Appendix" text="&#2474;&#2480;&#2495;&#2486;&#2495;&#2487;&#2509;&#2463;"/>
+  <l:gentext key="appendix" text="&#2474;&#2480;&#2495;&#2486;&#2495;&#2487;&#2509;&#2463;"/>
+  <l:gentext key="Article" text="&#2474;&#2509;&#2480;&#2476;&#2472;&#2509;&#2471;"/>
+  <l:gentext key="article" text="&#2474;&#2509;&#2480;&#2476;&#2472;&#2509;&#2471;"/>
+  <l:gentext key="Bibliography" text="&#2455;&#2509;&#2480;&#2472;&#2509;&#2469; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="bibliography" text="&#2455;&#2509;&#2480;&#2472;&#2509;&#2469; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="Book" text="&#2476;&#2439;"/>
+  <l:gentext key="book" text="&#2476;&#2439;"/>
+  <l:gentext key="CAUTION" text="&#2488;&#2468;&#2480;&#2509;&#2453;&#2468;&#2494;"/>
+  <l:gentext key="Caution" text="&#2488;&#2468;&#2480;&#2509;&#2453;&#2468;&#2494;"/>
+  <l:gentext key="caution" text="&#2488;&#2468;&#2480;&#2509;&#2453;&#2468;&#2494;"/>
+  <l:gentext key="Chapter" text="&#2437;&#2471;&#2509;&#2479;&#2494;&#2527;"/>
+  <l:gentext key="chapter" text="&#2437;&#2471;&#2509;&#2479;&#2494;&#2527;"/>
+  <l:gentext key="Colophon" text="&#2474;&#2509;&#2480;&#2453;&#2494;&#2486;&#2472;&#2494; &#2468;&#2469;&#2509;&#2479; &#2474;&#2499;&#2487;&#2509;&#2464;&#2494;"/>
+  <l:gentext key="colophon" text="&#2474;&#2509;&#2480;&#2453;&#2494;&#2486;&#2472;&#2494; &#2468;&#2469;&#2509;&#2479; &#2474;&#2499;&#2487;&#2509;&#2464;&#2494;"/>
+  <l:gentext key="Copyright" text="&#2488;&#2509;&#2476;&#2468;&#2509;&#2476;"/>
+  <l:gentext key="copyright" text="&#2488;&#2509;&#2476;&#2468;&#2509;&#2476;"/>
+  <l:gentext key="Dedication" text="&#2441;&#2468;&#2509;&#8205;&#2488;&#2480;&#2509;&#2455;"/>
+  <l:gentext key="dedication" text="&#2441;&#2468;&#2509;&#8205;&#2488;&#2480;&#2509;&#2455;"/>
+  <l:gentext key="Edition" text="&#2488;&#2434;&#2488;&#2509;&#2453;&#2480;&#2467;"/>
+  <l:gentext key="edition" text="&#2488;&#2434;&#2488;&#2509;&#2453;&#2480;&#2467;"/>
+  <l:gentext key="Equation" text="&#2488;&#2478;&#2496;&#2453;&#2480;&#2467;"/>
+  <l:gentext key="equation" text="&#2488;&#2478;&#2496;&#2453;&#2480;&#2467;"/>
+  <l:gentext key="Example" text="&#2441;&#2470;&#2494;&#2489;&#2480;&#2467;"/>
+  <l:gentext key="example" text="&#2441;&#2470;&#2494;&#2489;&#2480;&#2467;"/>
+  <l:gentext key="Figure" text="&#2458;&#2495;&#2468;&#2509;&#2480;"/>
+  <l:gentext key="figure" text="&#2458;&#2495;&#2468;&#2509;&#2480;"/>
+  <l:gentext key="Glossary" text="&#2472;&#2495;&#2480;&#2509;&#2456;&#2472;&#2509;&#2463;"/>
+  <l:gentext key="glossary" text="&#2472;&#2495;&#2480;&#2509;&#2456;&#2472;&#2509;&#2463;"/>
+  <l:gentext key="GlossSee" text="&#2470;&#2503;&#2454;&#2497;&#2472;"/>
+  <l:gentext key="glosssee" text="&#2470;&#2503;&#2454;&#2497;&#2472;"/>
+  <l:gentext key="GlossSeeAlso" text="&#2438;&#2480;&#2507; &#2470;&#2503;&#2454;&#2497;&#2472;"/>
+  <l:gentext key="glossseealso" text="&#2438;&#2480;&#2507; &#2470;&#2503;&#2454;&#2497;&#2472;"/>
+  <l:gentext key="IMPORTANT" text="&#2455;&#2497;&#2480;&#2497;&#2468;&#2509;&#2476;&#2474;&#2498;&#2480;&#2509;&#2467;"/>
+  <l:gentext key="important" text="&#2455;&#2497;&#2480;&#2497;&#2468;&#2509;&#2476;&#2474;&#2498;&#2480;&#2509;&#2467;"/>
+  <l:gentext key="Important" text="&#2455;&#2497;&#2480;&#2497;&#2468;&#2509;&#2476;&#2474;&#2498;&#2480;&#2509;&#2467;"/>
+  <l:gentext key="Index" text="&#2488;&#2498;&#2458;&#2495;"/>
+  <l:gentext key="index" text="&#2488;&#2498;&#2458;&#2495;"/>
+  <l:gentext key="ISBN" text="&#2438;&#2439;&#2447;&#2488;&#2476;&#2495;&#2447;&#2472; (ISBN)"/>
+  <l:gentext key="isbn" text="&#2438;&#2439;&#2447;&#2488;&#2476;&#2495;&#2447;&#2472; (ISBN)"/>
+  <l:gentext key="LegalNotice" text="&#2438;&#2439;&#2472;&#2496; &#2476;&#2495;&#2460;&#2509;&#2462;&#2474;&#2509;&#2468;&#2495;"/>
+  <l:gentext key="legalnotice" text="&#2438;&#2439;&#2472;&#2496; &#2476;&#2495;&#2460;&#2509;&#2462;&#2474;&#2509;&#2468;&#2495;"/>
+  <l:gentext key="MsgAud" text="&#2486;&#2509;&#2480;&#2507;&#2468;&#2494;"/>
+  <l:gentext key="msgaud" text="&#2486;&#2509;&#2480;&#2507;&#2468;&#2494;"/>
+  <l:gentext key="MsgLevel" text="&#2488;&#2509;&#2468;&#2480;"/>
+  <l:gentext key="msglevel" text="&#2488;&#2509;&#2468;&#2480;"/>
+  <l:gentext key="MsgOrig" text="&#2441;&#2468;&#2509;&#8205;&#2488;"/>
+  <l:gentext key="msgorig" text="&#2441;&#2468;&#2509;&#8205;&#2488;"/>
+  <l:gentext key="NOTE" text="&#2482;&#2453;&#2509;&#2487;&#2467;&#2496;&#2527;"/>
+  <l:gentext key="Note" text="&#2482;&#2453;&#2509;&#2487;&#2467;&#2496;&#2527;"/>
+  <l:gentext key="note" text="&#2482;&#2453;&#2509;&#2487;&#2467;&#2496;&#2527;"/>
+  <l:gentext key="Part" text="&#2454;&#2472;&#2509;&#2465;"/>
+  <l:gentext key="part" text="&#2454;&#2472;&#2509;&#2465;"/>
+  <l:gentext key="Preface" text="&#2478;&#2497;&#2454;&#2476;&#2472;&#2509;&#2471;"/>
+  <l:gentext key="preface" text="&#2478;&#2497;&#2454;&#2476;&#2472;&#2509;&#2471;"/>
+  <l:gentext key="Procedure" text="&#2474;&#2470;&#2509;&#2471;&#2468;&#2495;"/>
+  <l:gentext key="procedure" text="&#2474;&#2470;&#2509;&#2471;&#2468;&#2495;"/>
+  <l:gentext key="ProductionSet" text="&#2441;&#2468;&#2509;&#8205;&#2474;&#2494;&#2470;&#2472;"/>
+  <l:gentext key="PubDate" text="&#2474;&#2509;&#2480;&#2453;&#2494;&#2486;&#2472;&#2494;&#2480; &#2468;&#2494;&#2480;&#2495;&#2454;"/>
+  <l:gentext key="pubdate" text="&#2474;&#2509;&#2480;&#2453;&#2494;&#2486;&#2472;&#2494;&#2480; &#2468;&#2494;&#2480;&#2495;&#2454;"/>
+  <l:gentext key="Published" text="&#2474;&#2509;&#2480;&#2453;&#2494;&#2486;&#2495;&#2468;"/>
+  <l:gentext key="published" text="&#2474;&#2509;&#2480;&#2453;&#2494;&#2486;&#2495;&#2468;"/>
+  <l:gentext key="Question" text="&#2474;&#2509;&#2480;&#2486;&#2509;&#2472;:"/>
+  <l:gentext key="question" text="&#2474;&#2509;&#2480;&#2486;&#2509;&#2472;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#2455;&#2509;&#2480;&#2472;&#2509;&#2469;&#2488;&#2498;&#2468;&#2509;&#2480;"/>
+  <l:gentext key="reference" text="&#2455;&#2509;&#2480;&#2472;&#2509;&#2469;&#2488;&#2498;&#2468;&#2509;&#2480;"/>
+  <l:gentext key="RefName" text="&#2472;&#2494;&#2478;"/>
+  <l:gentext key="refname" text="&#2472;&#2494;&#2478;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#2488;&#2494;&#2480;&#2494;&#2434;&#2486;"/>
+  <l:gentext key="refsynopsisdiv" text="&#2488;&#2494;&#2480;&#2494;&#2434;&#2486;"/>
+  <l:gentext key="RevHistory" text="&#2474;&#2480;&#2495;&#2476;&#2480;&#2509;&#2471;&#2472; &#2451; &#2474;&#2480;&#2495;&#2476;&#2480;&#2509;&#2468;&#2472; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="revhistory" text="&#2474;&#2480;&#2495;&#2476;&#2480;&#2509;&#2471;&#2472; &#2451; &#2474;&#2480;&#2495;&#2476;&#2480;&#2509;&#2468;&#2472; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="revision" text="&#2488;&#2434;&#2488;&#2509;&#2453;&#2480;&#2467;"/>
+  <l:gentext key="Revision" text="&#2488;&#2434;&#2488;&#2509;&#2453;&#2480;&#2467;"/>
+  <l:gentext key="sect1" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;"/>
+  <l:gentext key="sect2" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;"/>
+  <l:gentext key="sect3" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;"/>
+  <l:gentext key="sect4" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;"/>
+  <l:gentext key="sect5" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;"/>
+  <l:gentext key="section" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;"/>
+  <l:gentext key="Section" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;"/>
+  <l:gentext key="see" text="&#2470;&#2503;&#2454;&#2497;&#2472;"/>
+  <l:gentext key="See" text="&#2470;&#2503;&#2454;&#2497;&#2472;"/>
+  <l:gentext key="seealso" text="&#2438;&#2480;&#2507; &#2470;&#2503;&#2454;&#2497;&#2472;"/>
+  <l:gentext key="Seealso" text="&#2438;&#2480;&#2507; &#2470;&#2503;&#2454;&#2497;&#2472;"/>
+  <l:gentext key="SeeAlso" text="&#2438;&#2480;&#2507; &#2470;&#2503;&#2454;&#2497;&#2472;"/>
+  <l:gentext key="set" text="&#2488;&#2478;&#2487;&#2509;&#2463;&#2495;"/>
+  <l:gentext key="Set" text="&#2488;&#2478;&#2487;&#2509;&#2463;&#2495;"/>
+  <l:gentext key="setindex" text="&#2488;&#2498;&#2458;&#2495;&#2488;&#2478;&#2487;&#2509;&#2463;&#2495;"/>
+  <l:gentext key="SetIndex" text="&#2488;&#2498;&#2458;&#2495;&#2488;&#2478;&#2487;&#2509;&#2463;&#2495;"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="&#2488;&#2494;&#2439;&#2465;&#2476;&#2494;&#2480;"/>
+  <l:gentext key="step" text="&#2471;&#2494;&#2474;"/>
+  <l:gentext key="Step" text="&#2471;&#2494;&#2474;"/>
+  <l:gentext key="Table" text="&#2459;&#2453;"/>
+  <l:gentext key="table" text="&#2459;&#2453;"/>
+  <l:gentext key="tip" text="&#2439;&#2457;&#2509;&#2455;&#2495;&#2468;"/>
+  <l:gentext key="TIP" text="&#2439;&#2457;&#2509;&#2455;&#2495;&#2468;"/>
+  <l:gentext key="Tip" text="&#2439;&#2457;&#2509;&#2455;&#2495;&#2468;"/>
+  <l:gentext key="Warning" text="&#2488;&#2468;&#2480;&#2509;&#2453;&#2476;&#2494;&#2467;&#2496;"/>
+  <l:gentext key="warning" text="&#2488;&#2468;&#2480;&#2509;&#2453;&#2476;&#2494;&#2467;&#2496;"/>
+  <l:gentext key="WARNING" text="&#2488;&#2468;&#2480;&#2509;&#2453;&#2476;&#2494;&#2467;&#2496;"/>
+  <l:gentext key="and" text="&#2447;&#2476;&#2434;"/>
+  <l:gentext key="by" text="&#2470;&#2509;&#2476;&#2494;&#2480;&#2494;"/>
+  <l:gentext key="called" text="&#2441;&#2482;&#2509;&#2482;&#2503;&#2454;&#2453;&#2499;&#2468;"/>
+  <l:gentext key="Edited" text="&#2488;&#2478;&#2509;&#2474;&#2494;&#2470;&#2495;&#2468;"/>
+  <l:gentext key="edited" text="&#2488;&#2478;&#2509;&#2474;&#2494;&#2470;&#2495;&#2468;"/>
+  <l:gentext key="Editedby" text="&#2488;&#2478;&#2509;&#2474;&#2494;&#2470;&#2453;"/>
+  <l:gentext key="editedby" text="&#2488;&#2478;&#2509;&#2474;&#2494;&#2470;&#2453;"/>
+  <l:gentext key="in" text="&#2478;&#2471;&#2509;&#2479;&#2503;"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="&#2437;&#2488;&#2509;&#2468;&#2495;&#2468;&#2509;&#2476;&#2489;&#2496;&#2472; &#2441;&#2474;&#2494;&#2470;&#2494;&#2472;"/>
+  <l:gentext key="notes" text="&#2472;&#2507;&#2463;"/>
+  <l:gentext key="Notes" text="&#2472;&#2507;&#2463;"/>
+  <l:gentext key="Pgs" text="&#2474;&#2499;&#2487;&#2509;&#2464;&#2494;."/>
+  <l:gentext key="pgs" text="&#2474;&#2499;&#2487;&#2509;&#2464;&#2494;."/>
+  <l:gentext key="Revisedby" text="&#2474;&#2480;&#2495;&#2478;&#2494;&#2480;&#2509;&#2460;&#2472;&#2494;&#2453;&#2494;&#2480;&#2496;: "/>
+  <l:gentext key="revisedby" text="&#2474;&#2480;&#2495;&#2478;&#2494;&#2480;&#2509;&#2460;&#2472;&#2494;&#2453;&#2494;&#2480;&#2496;: "/>
+  <l:gentext key="TableNotes" text="&#2472;&#2507;&#2463;"/>
+  <l:gentext key="tablenotes" text="&#2472;&#2507;&#2463;"/>
+  <l:gentext key="TableofContents" text="&#2488;&#2498;&#2458;&#2495;&#2474;&#2468;&#2509;&#2480;"/>
+  <l:gentext key="tableofcontents" text="&#2488;&#2498;&#2458;&#2495;&#2474;&#2468;&#2509;&#2480;"/>
+  <l:gentext key="the" text=""/>
+  <l:gentext key="unexpectedelementname" text="&#2437;&#2474;&#2509;&#2480;&#2468;&#2509;&#2479;&#2494;&#2486;&#2495;&#2468; &#2441;&#2474;&#2494;&#2470;&#2494;&#2472;&#2503;&#2480; &#2472;&#2494;&#2478;"/>
+  <l:gentext key="unsupported" text="&#2437;&#2488;&#2478;&#2480;&#2509;&#2469;&#2495;&#2468;"/>
+  <l:gentext key="xrefto" text="&#2472;&#2495;&#2480;&#2509;&#2470;&#2503;&#2486; &#2453;&#2480;&#2503;"/>
+  <l:gentext key="listofequations" text="&#2488;&#2478;&#2496;&#2453;&#2480;&#2467; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="ListofEquations" text="&#2488;&#2478;&#2496;&#2453;&#2480;&#2467; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="ListofExamples" text="&#2441;&#2470;&#2494;&#2489;&#2480;&#2467; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="listofexamples" text="&#2441;&#2470;&#2494;&#2489;&#2480;&#2467; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="ListofFigures" text="&#2458;&#2495;&#2468;&#2509;&#2480;&#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="listoffigures" text="&#2458;&#2495;&#2468;&#2509;&#2480;&#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="ListofProcedures" text="&#2474;&#2470;&#2509;&#2471;&#2468;&#2495;&#2480; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="listofprocedures" text="&#2474;&#2470;&#2509;&#2471;&#2468;&#2495;&#2480; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="listoftables" text="&#2459;&#2453;&#2503;&#2480; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="ListofTables" text="&#2459;&#2453;&#2503;&#2480; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="ListofUnknown" text="&#2437;&#2460;&#2509;&#2462;&#2494;&#2468; &#2476;&#2488;&#2509;&#2468;&#2497;&#2480; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="listofunknown" text="&#2437;&#2460;&#2509;&#2462;&#2494;&#2468; &#2476;&#2488;&#2509;&#2468;&#2497;&#2480; &#2468;&#2494;&#2482;&#2495;&#2453;&#2494;"/>
+  <l:gentext key="nav-home" text="&#2474;&#2509;&#2480;&#2469;&#2478; &#2437;&#2476;&#2488;&#2509;&#2469;&#2494;&#2472; (Home)"/>
+  <l:gentext key="nav-next" text="&#2474;&#2480;&#2476;&#2480;&#2509;&#2468;&#2496;"/>
+  <l:gentext key="nav-next-sibling" text="&#2470;&#2509;&#2480;&#2497;&#2468; &#2488;&#2478;&#2509;&#2478;&#2497;&#2454;&#2503;"/>
+  <l:gentext key="nav-prev" text="&#2474;&#2498;&#2480;&#2509;&#2476;&#2476;&#2480;&#2509;&#2468;&#2496;"/>
+  <l:gentext key="nav-prev-sibling" text="&#2470;&#2509;&#2480;&#2497;&#2468; &#2474;&#2486;&#2509;&#2458;&#2494;&#2468;&#2503;"/>
+  <l:gentext key="nav-up" text="&#2441;&#2474;&#2480;"/>
+  <l:gentext key="nav-toc" text="&#2488;&#2498;&#2458;&#2495;&#2474;&#2468;&#2509;&#2480;"/>
+  <l:gentext key="Draft" text="&#2454;&#2488;&#2524;&#2494;"/>
+  <l:gentext key="above" text="&#2441;&#2474;&#2480;"/>
+  <l:gentext key="below" text="&#2472;&#2495;&#2458;"/>
+  <l:gentext key="sectioncalled" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;"/>
+  <l:gentext key="index symbols" text="&#2474;&#2509;&#2480;&#2468;&#2496;&#2453;"/>
+  <l:gentext key="lowercase.alpha" text="&#2437;&#2438;&#2439;&#2440;&#2441;&#2442;&#2447;&#2448;&#2451;&#2452;&#2443;&#2453;&#2454;&#2455;&#2456;&#2457;&#2458;&#2459;&#2460;&#2461;&#2462;&#2463;&#2464;&#2465;&#2466;&#2467;&#2468;&#2469;&#2470;&#2471;&#2472;&#2474;&#2475;&#2476;&#2477;&#2478;&#2479;&#2480;&#2482;&#2486;&#2487;&#2488;&#2489;&#2434;&#2435;"/>
+  <l:gentext key="uppercase.alpha" text="&#2437;&#2438;&#2439;&#2440;&#2441;&#2442;&#2447;&#2448;&#2451;&#2452;&#2443;&#2453;&#2454;&#2455;&#2456;&#2457;&#2458;&#2459;&#2460;&#2461;&#2462;&#2463;&#2464;&#2465;&#2466;&#2467;&#2468;&#2469;&#2470;&#2471;&#2472;&#2474;&#2475;&#2476;&#2477;&#2478;&#2479;&#2480;&#2482;&#2486;&#2487;&#2488;&#2489;&#2434;&#2435;"/>
+  <l:gentext key="hyphenation-character" text="-"/>
+  <l:gentext key="hyphenation-push-character-count" text="2"/>
+  <l:gentext key="hyphenation-remain-character-count" text="2"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/bn.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="singlestartquote" text="&#8216;"/>
+  <l:dingbat key="singleendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#2474;&#2480;&#2495;&#2486;&#2495;&#2487;&#2509;&#2463;&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#2437;&#2471;&#2509;&#2479;&#2494;&#2527;&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#2488;&#2478;&#2496;&#2453;&#2480;&#2467;&#160;%n.&#160;%t"/>
+    <l:template name="example" text="&#2441;&#2470;&#2494;&#2489;&#2480;&#2467;&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="&#2458;&#2495;&#2468;&#2509;&#2480;&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#2454;&#2472;&#2509;&#2465;&#160;%n.&#160;%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#2474;&#2470;&#2509;&#2471;&#2468;&#2495;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="&#2441;&#2468;&#2509;&#8205;&#2474;&#2494;&#2470;&#2472;&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#2459;&#2453;&#160;%n.&#160;%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#2474;&#2480;&#2495;&#2486;&#2495;&#2487;&#2509;&#2463;&#160;%n.&#160;%t"/>
+    <l:template name="article/appendix" text="%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="&#2437;&#2471;&#2509;&#2479;&#2494;&#2527;&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#2441;&#2468;&#2509;&#2468;&#2480;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#2474;&#2509;&#2480;&#2486;&#2509;&#2472;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#2474;&#2509;&#2480;&#2486;&#2509;&#2472;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#2441;&#2468;&#2509;&#2468;&#2480;:&#160;%n"/>
+    <l:template name="appendix" text="&#2474;&#2480;&#2495;&#2486;&#2495;&#2487;&#2509;&#2463;&#160;%n"/>
+    <l:template name="bridgehead" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n"/>
+    <l:template name="chapter" text="&#2437;&#2471;&#2509;&#2479;&#2494;&#2527;&#160;%n"/>
+    <l:template name="equation" text="&#2488;&#2478;&#2496;&#2453;&#2480;&#2467;&#160;%n"/>
+    <l:template name="example" text="&#2441;&#2470;&#2494;&#2489;&#2480;&#2467;&#160;%n"/>
+    <l:template name="figure" text="&#2458;&#2495;&#2468;&#2509;&#2480;&#160;%n"/>
+    <l:template name="part" text="&#2454;&#2472;&#2509;&#2465;&#160;%n"/>
+    <l:template name="procedure" text="&#2474;&#2470;&#2509;&#2471;&#2468;&#2495;&#160;%n"/>
+    <l:template name="productionset" text="&#2441;&#2468;&#2509;&#8205;&#2474;&#2494;&#2470;&#2472;&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#2474;&#2509;&#2480;&#2486;&#2509;&#2472;:&#160;%n"/>
+    <l:template name="question" text="&#2474;&#2509;&#2480;&#2486;&#2509;&#2472;:&#160;%n"/>
+    <l:template name="sect1" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n"/>
+    <l:template name="sect2" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n"/>
+    <l:template name="sect3" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n"/>
+    <l:template name="sect4" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n"/>
+    <l:template name="sect5" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n"/>
+    <l:template name="section" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n"/>
+    <l:template name="table" text="&#2459;&#2453;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#2474;&#2480;&#2495;&#2486;&#2495;&#2487;&#2509;&#2463;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="&#2437;&#2471;&#2509;&#2479;&#2494;&#2527;&#160;%n, %t"/>
+    <l:template name="equation" text="&#2488;&#2478;&#2496;&#2453;&#2480;&#2467;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="&#2441;&#2470;&#2494;&#2489;&#2480;&#2467;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="&#2458;&#2495;&#2468;&#2509;&#2480;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="&#2454;&#2472;&#2509;&#2465;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="&#2474;&#2470;&#2509;&#2471;&#2468;&#2495;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="&#2441;&#2468;&#2509;&#8205;&#2474;&#2494;&#2470;&#2472;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#2437;&#2472;&#2497;&#2458;&#2509;&#2459;&#2503;&#2470; &#8220;%t&#8221;"/>
+    <l:template name="table" text="&#2459;&#2453;&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#2447;&#2476;&#2434; "/>
+    <l:template name="seplast" text=", &#2447;&#2476;&#2434; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#2470;&#2503;&#2454;&#2497;&#2472; "/>
+    <l:template name="seealso" text="&#2438;&#2480;&#2507; &#2470;&#2503;&#2454;&#2497;&#2472; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#2486;&#2509;&#2480;&#2507;&#2468;&#2494;: "/>
+    <l:template name="MsgLevel" text="&#2488;&#2509;&#2468;&#2480;: "/>
+    <l:template name="MsgOrig" text="&#2441;&#2468;&#2509;&#8205;&#2488;: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d/m/Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="&#2460;&#2494;&#2472;&#2497;&#2527;&#2494;&#2480;&#2496;"/>
+    <l:template name="February" text="&#2475;&#2503;&#2476;&#2509;&#2480;&#2497;&#2527;&#2494;&#2480;&#2496;"/>
+    <l:template name="March" text="&#2478;&#2494;&#2480;&#2509;&#2458;"/>
+    <l:template name="April" text="&#2447;&#2474;&#2509;&#2480;&#2495;&#2482;"/>
+    <l:template name="May" text="&#2478;&#2503;"/>
+    <l:template name="June" text="&#2460;&#2497;&#2472;"/>
+    <l:template name="July" text="&#2460;&#2497;&#2482;&#2494;&#2439;"/>
+    <l:template name="August" text="&#2438;&#2455;&#2488;&#2509;&#2463;"/>
+    <l:template name="September" text="&#2488;&#2503;&#2474;&#2509;&#2463;&#2503;&#2478;&#2509;&#2476;&#2480;"/>
+    <l:template name="October" text="&#2437;&#2453;&#2509;&#2463;&#2507;&#2476;&#2480;"/>
+    <l:template name="November" text="&#2472;&#2477;&#2503;&#2478;&#2509;&#2476;&#2480;"/>
+    <l:template name="December" text="&#2465;&#2495;&#2488;&#2503;&#2478;&#2509;&#2476;&#2480;"/>
+    <l:template name="Monday" text="&#2488;&#2507;&#2478;&#2476;&#2494;&#2480;"/>
+    <l:template name="Tuesday" text="&#2478;&#2457;&#2509;&#2455;&#2482;&#2476;&#2494;&#2480;"/>
+    <l:template name="Wednesday" text="&#2476;&#2497;&#2471;&#2476;&#2494;&#2480;"/>
+    <l:template name="Thursday" text="&#2476;&#2499;&#2489;&#2435;&#2488;&#2509;&#2474;&#2468;&#2495;&#2476;&#2494;&#2480;"/>
+    <l:template name="Friday" text="&#2486;&#2497;&#2453;&#2509;&#2480;&#2476;&#2494;&#2480;"/>
+    <l:template name="Saturday" text="&#2486;&#2472;&#2495;&#2476;&#2494;&#2480;"/>
+    <l:template name="Sunday" text="&#2480;&#2476;&#2495;&#2476;&#2494;&#2480;"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="&#2460;&#2494;&#2472;&#2497;&#2527;&#2494;&#2480;&#2496;"/>
+    <l:template name="Feb" text="&#2475;&#2503;&#2476;&#2509;&#2480;&#2497;&#2527;&#2494;&#2480;&#2496;"/>
+    <l:template name="Mar" text="&#2478;&#2494;&#2480;&#2509;&#2458;"/>
+    <l:template name="Apr" text="&#2447;&#2474;&#2509;&#2480;&#2495;&#2482;"/>
+    <l:template name="May" text="&#2478;&#2503;"/>
+    <l:template name="Jun" text="&#2460;&#2497;&#2472;"/>
+    <l:template name="Jul" text="&#2460;&#2497;&#2482;&#2494;&#2439;"/>
+    <l:template name="Aug" text="&#2438;&#2455;&#2488;&#2509;&#2463;"/>
+    <l:template name="Sep" text="&#2488;&#2503;&#2474;&#2509;&#2463;&#2503;&#2478;&#2509;&#2476;&#2480;"/>
+    <l:template name="Oct" text="&#2437;&#2453;&#2509;&#2463;&#2507;&#2476;&#2480;"/>
+    <l:template name="Nov" text="&#2472;&#2477;&#2503;&#2478;&#2509;&#2476;&#2480;"/>
+    <l:template name="Dec" text="&#2465;&#2495;&#2488;&#2503;&#2478;&#2509;&#2476;&#2480;"/>
+    <l:template name="Mon" text="&#2488;&#2507;&#2478;"/>
+    <l:template name="Tue" text="&#2478;&#2457;&#2509;&#2455;&#2482;"/>
+    <l:template name="Wed" text="&#2476;&#2497;&#2471;"/>
+    <l:template name="Thu" text="&#2476;&#2499;&#2489;&#2435;&#2488;&#2509;&#2474;&#2468;&#2495;"/>
+    <l:template name="Fri" text="&#2486;&#2497;&#2453;&#2509;&#2480;"/>
+    <l:template name="Sat" text="&#2486;&#2472;&#2495;"/>
+    <l:template name="Sun" text="&#2480;&#2476;&#2495;"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text=" 0x0439 Bangla (Bangladesh and India)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/ca.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/ca.xml
new file mode 100644
index 00000000000..f2556c136a9
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/ca.xml
@@ -0,0 +1,445 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="ca" english-language-name="Catalan">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ca.xml -->
+  <l:gentext key="Abstract" text="Resum"/>
+  <l:gentext key="abstract" text="Resum"/>
+  <l:gentext key="Answer" text="Answer"/>
+  <l:gentext key="answer" text="Answer"/>
+  <l:gentext key="appendix" text="ap&#232;ndex"/>
+  <l:gentext key="Appendix" text="Ap&#232;ndix"/>
+  <l:gentext key="Article" text="Article"/>
+  <l:gentext key="article" text="Article"/>
+  <l:gentext key="Bibliography" text="Bibliografia"/>
+  <l:gentext key="bibliography" text="Bibliografia"/>
+  <l:gentext key="Book" text="Llibre"/>
+  <l:gentext key="book" text="Llibre"/>
+  <l:gentext key="Caution" text="Atenci&#243;"/>
+  <l:gentext key="caution" text="Atenci&#243;"/>
+  <l:gentext key="CAUTION" text="ATENCI&#211;"/>
+  <l:gentext key="Chapter" text="Cap&#237;tol"/>
+  <l:gentext key="chapter" text="cap&#237;tol"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Dret de reproducci&#243;"/>
+  <l:gentext key="copyright" text="Dret de reproducci&#243;"/>
+  <l:gentext key="Dedication" text="Dedicat&#242;ria"/>
+  <l:gentext key="dedication" text="Dedicat&#242;ria"/>
+  <l:gentext key="Edition" text="Edici&#243;"/>
+  <l:gentext key="edition" text="Edici&#243;"/>
+  <l:gentext key="Equation" text="Equaci&#243;"/>
+  <l:gentext key="equation" text="Equaci&#243;"/>
+  <l:gentext key="Example" text="Exemple"/>
+  <l:gentext key="example" text="Exemple"/>
+  <l:gentext key="Figure" text="Figura"/>
+  <l:gentext key="figure" text="Figura"/>
+  <l:gentext key="Glossary" text="Glossari"/>
+  <l:gentext key="glossary" text="Glossari"/>
+  <l:gentext key="GlossSee" text="Veure"/>
+  <l:gentext key="glosssee" text="Veure"/>
+  <l:gentext key="GlossSeeAlso" text="Veure tamb&#233;"/>
+  <l:gentext key="glossseealso" text="Veure tamb&#233;"/>
+  <l:gentext key="IMPORTANT" text="IMPORTANT"/>
+  <l:gentext key="Important" text="Important"/>
+  <l:gentext key="important" text="Important"/>
+  <l:gentext key="Index" text="&#205;ndex alfab&#232;tic"/>
+  <l:gentext key="index" text="&#205;ndex alfab&#232;tic"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text=""/>
+  <l:gentext key="legalnotice" text=""/>
+  <l:gentext key="MsgAud" text="Audi&#232;ncia"/>
+  <l:gentext key="msgaud" text="Audi&#232;ncia"/>
+  <l:gentext key="MsgLevel" text="Nivell"/>
+  <l:gentext key="msglevel" text="Nivell"/>
+  <l:gentext key="MsgOrig" text="Origen"/>
+  <l:gentext key="msgorig" text="Origen"/>
+  <l:gentext key="note" text="Nota"/>
+  <l:gentext key="NOTE" text="NOTA"/>
+  <l:gentext key="Note" text="Nota"/>
+  <l:gentext key="Part" text="Part"/>
+  <l:gentext key="part" text="Part"/>
+  <l:gentext key="Preface" text="Prefaci"/>
+  <l:gentext key="preface" text="Prefaci"/>
+  <l:gentext key="Procedure" text="Procediment"/>
+  <l:gentext key="procedure" text="Procediment"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="PubDate" text="Data de publicaci&#243;"/>
+  <l:gentext key="pubdate" text="Data de publicaci&#243;"/>
+  <l:gentext key="Published" text="Data de publicaci&#243;"/>
+  <l:gentext key="published" text="Data de publicaci&#243;"/>
+  <l:gentext key="Question" text="Question"/>
+  <l:gentext key="question" text="Question"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Refer&#232;ncia"/>
+  <l:gentext key="reference" text="Refer&#232;ncia"/>
+  <l:gentext key="RefName" text="Nom"/>
+  <l:gentext key="refname" text="Nom"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Historial de revisions"/>
+  <l:gentext key="revhistory" text="Historial de revisions"/>
+  <l:gentext key="Revision" text="Revisi&#243;"/>
+  <l:gentext key="revision" text="Revisi&#243;"/>
+  <l:gentext key="sect1" text="Secci&#243;"/>
+  <l:gentext key="sect2" text="Secci&#243;"/>
+  <l:gentext key="sect3" text="Secci&#243;"/>
+  <l:gentext key="sect4" text="Secci&#243;"/>
+  <l:gentext key="sect5" text="Secci&#243;"/>
+  <l:gentext key="Section" text="Secci&#243;"/>
+  <l:gentext key="section" text="secci&#243;"/>
+  <l:gentext key="see" text="Veure"/>
+  <l:gentext key="See" text="Veure"/>
+  <l:gentext key="Seealso" text="Veure tamb&#233;"/>
+  <l:gentext key="seealso" text="Veure tambi&#233;"/>
+  <l:gentext key="SeeAlso" text="Veure tambi&#233;"/>
+  <l:gentext key="Set" text="Conjunt"/>
+  <l:gentext key="set" text="Conjunt"/>
+  <l:gentext key="SetIndex" text="&#205;ndex del conjunt"/>
+  <l:gentext key="setindex" text="&#205;ndex del conjunt"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="glossa"/>
+  <l:gentext key="step" text="pas"/>
+  <l:gentext key="Step" text="Pas"/>
+  <l:gentext key="table" text="Taula"/>
+  <l:gentext key="Table" text="Taula"/>
+  <l:gentext key="TIP" text="SUGGERIMENT"/>
+  <l:gentext key="Tip" text="Suggeriment"/>
+  <l:gentext key="tip" text="Suggeriment"/>
+  <l:gentext key="WARNING" text="AV&#205;S"/>
+  <l:gentext key="Warning" text="Av&#237;s"/>
+  <l:gentext key="warning" text="Av&#237;s"/>
+  <l:gentext key="and" text="i"/>
+  <l:gentext key="by" text="per"/>
+  <l:gentext key="Edited" text="Editat"/>
+  <l:gentext key="edited" text="Editat"/>
+  <l:gentext key="Editedby" text="Editat per"/>
+  <l:gentext key="editedby" text="Editat per"/>
+  <l:gentext key="in" text="a"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="element inexistent"/>
+  <l:gentext key="notes" text="Notes"/>
+  <l:gentext key="Notes" text="Notes"/>
+  <l:gentext key="Pgs" text="P&#224;gs."/>
+  <l:gentext key="pgs" text="P&#224;gs."/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text="Notes"/>
+  <l:gentext key="tablenotes" text="Notes"/>
+  <l:gentext key="TableofContents" text="Sumari"/>
+  <l:gentext key="tableofcontents" text="Sumari"/>
+  <l:gentext key="unexpectedelementname" text="Nom d'element no esperat"/>
+  <l:gentext key="unsupported" text="no reconeguda"/>
+  <l:gentext key="xrefto" text="xref a"/>
+  <l:gentext key="listofequations" text="&#205;ndex d'equacions"/>
+  <l:gentext key="ListofEquations" text="&#205;ndex d'equacions"/>
+  <l:gentext key="ListofExamples" text="&#205;ndex d'exemples"/>
+  <l:gentext key="listofexamples" text="&#205;ndex d'exemples"/>
+  <l:gentext key="ListofFigures" text="&#205;ndex de figures"/>
+  <l:gentext key="listoffigures" text="&#205;ndex de figures"/>
+  <l:gentext key="listoftables" text="&#205;ndex de taules"/>
+  <l:gentext key="ListofTables" text="&#205;ndex de taules"/>
+  <l:gentext key="ListofUnknown" text="&#205;ndex de desconegut ?"/>
+  <l:gentext key="listofunknown" text="&#205;ndex de desconegut ?"/>
+  <l:gentext key="nav-home" text="Inici"/>
+  <l:gentext key="nav-next" text="Seguent"/>
+  <l:gentext key="nav-next-sibling" text="Avancar"/>
+  <l:gentext key="nav-prev" text="Anterior"/>
+  <l:gentext key="nav-prev-sibling" text="Retrocedir"/>
+  <l:gentext key="nav-up" text="Pujar"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ca.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="last-first"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Ap&#232;ndix %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Cap&#237;tol %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Equaci&#243; %n. %t"/>
+    <l:template name="example" text="Exemple %n. %t"/>
+    <l:template name="figure" text="Figura %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Part %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procediment&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Taula %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Ap&#232;ndix %n. %t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="Cap&#237;tol %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Answer&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Question&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Question&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="bridgehead" text=" &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Answer&#160;%n"/>
+    <l:template name="appendix" text="Ap&#232;ndix&#160;%n"/>
+    <l:template name="bridgehead" text="Secci&#243;&#160;%n"/>
+    <l:template name="chapter" text="Cap&#237;tol&#160;%n"/>
+    <l:template name="equation" text="Equaci&#243;&#160;%n"/>
+    <l:template name="example" text="Exemple&#160;%n"/>
+    <l:template name="figure" text="Figura&#160;%n"/>
+    <l:template name="part" text="Part&#160;%n"/>
+    <l:template name="procedure" text="Procediment&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Question&#160;%n"/>
+    <l:template name="question" text="Question&#160;%n"/>
+    <l:template name="sect1" text="Secci&#243;&#160;%n"/>
+    <l:template name="sect2" text="Secci&#243;&#160;%n"/>
+    <l:template name="sect3" text="Secci&#243;&#160;%n"/>
+    <l:template name="sect4" text="Secci&#243;&#160;%n"/>
+    <l:template name="sect5" text="Secci&#243;&#160;%n"/>
+    <l:template name="section" text="Secci&#243;&#160;%n"/>
+    <l:template name="table" text="Taula&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Ap&#232;ndix&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Secci&#243;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Cap&#237;tol&#160;%n, %t"/>
+    <l:template name="equation" text="Equaci&#243;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Exemple&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figura&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Part&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procediment&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Secci&#243;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Secci&#243;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Secci&#243;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Secci&#243;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Secci&#243;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Secci&#243;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Taula&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" i "/>
+    <l:template name="seplast" text=", i "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Veure "/>
+    <l:template name="seealso" text="Veure tamb&#233; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Audi&#232;ncia: "/>
+    <l:template name="MsgLevel" text="Nivell: "/>
+    <l:template name="MsgOrig" text="Origen: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0403 Catalan"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/common.xsl b/docs-xml/xslt/db2latex-xsl/xsl/common/common.xsl
new file mode 100644
index 00000000000..5a1d978c07f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/common.xsl
@@ -0,0 +1,1573 @@
+<?xml version='1.0'?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+                exclude-result-prefixes="doc"
+                version='1.0'>
+
+<!-- ********************************************************************
+     $Id: common.xsl,v 1.6 2004/01/04 09:25:06 j-devenish Exp $
+     ********************************************************************
+
+     This file is part of the XSL DocBook Stylesheet distribution.
+
+     Copyright (C) 1999, 2000, 2001, 2002 Norman Walsh.
+     ******************************************************************** -->
+
+<doc:reference xmlns="">
+<referenceinfo>
+<releaseinfo role="meta">
+$Id: common.xsl,v 1.6 2004/01/04 09:25:06 j-devenish Exp $
+</releaseinfo>
+<author><surname>Walsh</surname>
+<firstname>Norman</firstname></author>
+<copyright><year>1999</year><year>2000</year>
+<holder>Norman Walsh</holder>
+</copyright>
+</referenceinfo>
+<title>Common Template Reference</title>
+
+<partintro>
+<section><title>Introduction</title>
+
+<para>This is technical reference documentation for the DocBook XSL
+Stylesheets; it documents (some of) the parameters, templates, and
+other elements of the stylesheets.</para>
+
+<para>This is not intended to be <quote>user</quote> documentation.
+It is provided for developers writing customization layers for the
+stylesheets, and for anyone who's interested in <quote>how it
+works</quote>.</para>
+
+<para>Although I am trying to be thorough, this documentation is known
+to be incomplete. Don't forget to read the source, too :-)</para>
+</section>
+</partintro>
+
+</doc:reference>
+
+<!-- ==================================================================== -->
+<!-- Establish strip/preserve whitespace rules -->
+
+<xsl:preserve-space elements="*"/>
+
+<xsl:strip-space elements="
+abstract affiliation anchor answer appendix area areaset areaspec
+artheader article audiodata audioobject author authorblurb authorgroup
+beginpage bibliodiv biblioentry bibliography biblioset blockquote book
+bookbiblio bookinfo callout calloutlist caption caution chapter
+citerefentry cmdsynopsis co collab colophon colspec confgroup
+copyright dedication docinfo editor entry entrytbl epigraph equation
+example figure footnote footnoteref formalpara funcprototype
+funcsynopsis glossary glossdef glossdiv glossentry glosslist graphicco
+group highlights imagedata imageobject imageobjectco important index
+indexdiv indexentry indexterm informalequation informalexample
+informalfigure informaltable inlineequation inlinemediaobject
+itemizedlist itermset keycombo keywordset legalnotice listitem lot
+mediaobject mediaobjectco menuchoice msg msgentry msgexplan msginfo
+msgmain msgrel msgset msgsub msgtext note objectinfo
+orderedlist othercredit part partintro preface printhistory procedure
+programlistingco publisher qandadiv qandaentry qandaset question
+refentry reference refmeta refnamediv refsect1 refsect1info refsect2
+refsect2info refsect3 refsect3info refsynopsisdiv refsynopsisdivinfo
+revhistory revision row sbr screenco screenshot sect1 sect1info sect2
+sect2info sect3 sect3info sect4 sect4info sect5 sect5info section
+sectioninfo seglistitem segmentedlist seriesinfo set setindex setinfo
+shortcut sidebar simplelist simplesect spanspec step subject
+subjectset substeps synopfragment table tbody textobject tfoot tgroup
+thead tip toc tocchap toclevel1 toclevel2 toclevel3 toclevel4
+toclevel5 tocpart varargs variablelist varlistentry videodata
+videoobject void warning subjectset
+
+classsynopsis
+constructorsynopsis
+destructorsynopsis
+fieldsynopsis
+methodparam
+methodsynopsis
+ooclass
+ooexception
+oointerface
+simplemsgentry
+"/>
+
+<!-- ====================================================================== -->
+
+<doc:template name="is.component" xmlns="">
+<refpurpose>Tests if a given node is a component-level element</refpurpose>
+
+<refdescription>
+<para>This template returns '1' if the specified node is a component
+(Chapter, Appendix, etc.), and '0' otherwise.</para>
+</refdescription>
+
+<refparameter>
+<variablelist>
+<varlistentry><term>node</term>
+<listitem>
+<para>The node which is to be tested.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</refparameter>
+
+<refreturn>
+<para>This template returns '1' if the specified node is a component
+(Chapter, Appendix, etc.), and '0' otherwise.</para>
+</refreturn>
+</doc:template>
+
+<xsl:template name="is.component">
+  <xsl:param name="node" select="."/>
+  <xsl:choose>
+    <xsl:when test="local-name($node) = 'appendix'
+                    or local-name($node) = 'article'
+                    or local-name($node) = 'chapter'
+                    or local-name($node) = 'preface'
+                    or local-name($node) = 'bibliography'
+                    or local-name($node) = 'glossary'
+                    or local-name($node) = 'index'">1</xsl:when>
+    <xsl:otherwise>0</xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ====================================================================== -->
+
+<doc:template name="is.section" xmlns="">
+<refpurpose>Tests if a given node is a section-level element</refpurpose>
+
+<refdescription>
+<para>This template returns '1' if the specified node is a section
+(Section, Sect1, Sect2, etc.), and '0' otherwise.</para>
+</refdescription>
+
+<refparameter>
+<variablelist>
+<varlistentry><term>node</term>
+<listitem>
+<para>The node which is to be tested.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</refparameter>
+
+<refreturn>
+<para>This template returns '1' if the specified node is a section
+(Section, Sect1, Sect2, etc.), and '0' otherwise.</para>
+</refreturn>
+</doc:template>
+
+<xsl:template name="is.section">
+  <xsl:param name="node" select="."/>
+  <xsl:choose>
+    <xsl:when test="local-name($node) = 'section'
+                    or local-name($node) = 'sect1'
+                    or local-name($node) = 'sect2'
+                    or local-name($node) = 'sect3'
+                    or local-name($node) = 'sect4'
+                    or local-name($node) = 'sect5'
+                    or local-name($node) = 'refsect1'
+                    or local-name($node) = 'refsect2'
+                    or local-name($node) = 'refsect3'
+                    or local-name($node) = 'simplesect'">1</xsl:when>
+    <xsl:otherwise>0</xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ====================================================================== -->
+
+<doc:template name="section.level" xmlns="">
+<refpurpose>Returns the hierarchical level of a section.</refpurpose>
+
+<refdescription>
+<para>This template calculates the hierarchical level of a section.
+The element <sgmltag>sect1</sgmltag> is at level 1, <sgmltag>sect2</sgmltag> is
+at level 2, etc.</para>
+
+<para>Recursive sections are calculated down to the fifth level.</para>
+</refdescription>
+
+<refparameter>
+<variablelist>
+<varlistentry><term>node</term>
+<listitem>
+<para>The section node for which the level should be calculated.
+Defaults to the context node.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</refparameter>
+
+<refreturn>
+<para>The section level, <quote>1</quote>, <quote>2</quote>, etc.
+</para>
+</refreturn>
+</doc:template>
+
+<xsl:template name="section.level">
+  <xsl:param name="node" select="."/>
+  <xsl:choose>
+    <xsl:when test="name($node)='sect1'">1</xsl:when>
+    <xsl:when test="name($node)='sect2'">2</xsl:when>
+    <xsl:when test="name($node)='sect3'">3</xsl:when>
+    <xsl:when test="name($node)='sect4'">4</xsl:when>
+    <xsl:when test="name($node)='sect5'">5</xsl:when>
+    <xsl:when test="name($node)='section'">
+      <xsl:choose>
+        <xsl:when test="$node/../../../../../../section">6</xsl:when>
+        <xsl:when test="$node/../../../../../section">5</xsl:when>
+        <xsl:when test="$node/../../../../section">4</xsl:when>
+        <xsl:when test="$node/../../../section">3</xsl:when>
+        <xsl:when test="$node/../../section">2</xsl:when>
+        <xsl:otherwise>1</xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:when test="name($node)='refsect1' or
+                    name($node)='refsect2' or
+                    name($node)='refsect3' or
+                    name($node)='refsection' or
+                    name($node)='refsynopsisdiv'">
+      <xsl:call-template name="refentry.section.level">
+        <xsl:with-param name="node" select="$node"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:when test="name($node)='simplesect'">
+      <xsl:choose>
+        <xsl:when test="$node/../../sect1">2</xsl:when>
+        <xsl:when test="$node/../../sect2">3</xsl:when>
+        <xsl:when test="$node/../../sect3">4</xsl:when>
+        <xsl:when test="$node/../../sect4">5</xsl:when>
+        <xsl:when test="$node/../../sect5">5</xsl:when>
+        <xsl:when test="$node/../../section">
+          <xsl:choose>
+            <xsl:when test="$node/../../../../../section">5</xsl:when>
+            <xsl:when test="$node/../../../../section">4</xsl:when>
+            <xsl:when test="$node/../../../section">3</xsl:when>
+            <xsl:otherwise>2</xsl:otherwise>
+          </xsl:choose>
+        </xsl:when>
+        <xsl:otherwise>1</xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:otherwise>1</xsl:otherwise>
+  </xsl:choose>
+</xsl:template><!-- section.level -->
+
+<doc:template name="qanda.section.level" xmlns="">
+<refpurpose>Returns the hierarchical level of a QandASet.</refpurpose>
+
+<refdescription>
+<para>This template calculates the hierarchical level of a QandASet.
+</para>
+</refdescription>
+
+<refreturn>
+<para>The level, <quote>1</quote>, <quote>2</quote>, etc.
+</para>
+</refreturn>
+</doc:template>
+
+<xsl:template name="qanda.section.level">
+  <xsl:variable name="section"
+                select="(ancestor::section
+                         |ancestor::simplesect
+                         |ancestor::sect5
+                         |ancestor::sect4
+                         |ancestor::sect3
+                         |ancestor::sect2
+                         |ancestor::sect1
+                         |ancestor::refsect3
+                         |ancestor::refsect2
+                         |ancestor::refsect1)[last()]"/>
+
+  <xsl:choose>
+    <xsl:when test="count($section) = 0">1</xsl:when>
+    <xsl:otherwise>
+      <xsl:variable name="slevel">
+        <xsl:call-template name="section.level">
+          <xsl:with-param name="node" select="$section"/>
+        </xsl:call-template>
+      </xsl:variable>
+      <xsl:value-of select="$slevel + 1"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- Finds the total section depth of a section in a refentry -->
+<xsl:template name="refentry.section.level">
+  <xsl:param name="node" select="."/>
+
+  <xsl:variable name="RElevel">
+    <xsl:call-template name="refentry.level">
+      <xsl:with-param name="node" select="$node/ancestor::refentry[1]"/>
+    </xsl:call-template>
+  </xsl:variable>
+
+  <xsl:variable name="levelinRE">
+    <xsl:choose>
+      <xsl:when test="name($node)='refsynopsisdiv'">1</xsl:when>
+      <xsl:when test="name($node)='refsect1'">1</xsl:when>
+      <xsl:when test="name($node)='refsect2'">2</xsl:when>
+      <xsl:when test="name($node)='refsect3'">3</xsl:when>
+      <xsl:when test="name($node)='refsection'">
+        <xsl:choose>
+          <xsl:when test="$node/../../../../../refsection">5</xsl:when>
+          <xsl:when test="$node/../../../../refsection">4</xsl:when>
+          <xsl:when test="$node/../../../refsection">3</xsl:when>
+          <xsl:when test="$node/../../refsection">2</xsl:when>
+          <xsl:otherwise>1</xsl:otherwise>
+        </xsl:choose>
+      </xsl:when>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:value-of select="$levelinRE + $RElevel"/>
+</xsl:template>
+
+<!-- Finds the section depth of a refentry -->
+<xsl:template name="refentry.level">
+  <xsl:param name="node" select="."/>
+  <xsl:variable name="container"
+                select="($node/ancestor::section |
+                        $node/ancestor::sect1 |
+                        $node/ancestor::sect2 |
+                        $node/ancestor::sect3 |
+                        $node/ancestor::sect4 |
+                        $node/ancestor::sect5)[last()]"/>
+
+  <xsl:choose>
+    <xsl:when test="$container">
+      <xsl:variable name="slevel">
+        <xsl:call-template name="section.level">
+          <xsl:with-param name="node" select="$container"/>
+        </xsl:call-template>
+      </xsl:variable>
+      <xsl:value-of select="$slevel + 1"/>
+    </xsl:when>
+    <xsl:otherwise>1</xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="qandadiv.section.level">
+  <xsl:variable name="section.level">
+    <xsl:call-template name="qanda.section.level"/>
+  </xsl:variable>
+  <xsl:variable name="anc.divs" select="ancestor::qandadiv"/>
+
+  <xsl:value-of select="count($anc.divs) + number($section.level)"/>
+</xsl:template>
+
+
+<xsl:template match="qandaset" mode="number">
+  <!-- FIXME: -->
+</xsl:template>
+
+<xsl:template match="qandadiv" mode="number">
+  <xsl:number level="multiple" from="qandaset" format="1."/>
+</xsl:template>
+
+<xsl:template match="qandaentry" mode="number">
+  <xsl:choose>
+    <xsl:when test="ancestor::qandadiv">
+      <xsl:number level="single" from="qandadiv" format="1."/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:number level="single" from="qandaset" format="1."/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ====================================================================== -->
+
+<xsl:template name="object.id">
+  <xsl:param name="object" select="."/>
+  <xsl:choose>
+    <xsl:when test="$object/@id">
+      <xsl:value-of select="$object/@id"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:value-of select="generate-id($object)"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="person.name">
+  <!-- Formats a personal name. Handles corpauthor as a special case. -->
+  <xsl:param name="node" select="."/>
+
+  <xsl:variable name="style">
+    <xsl:choose>
+      <xsl:when test="$node/@role">
+        <xsl:value-of select="$node/@role"/>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:call-template name="gentext.template">
+          <xsl:with-param name="context" select="'styles'"/>
+          <xsl:with-param name="name" select="'person-name'"/>
+        </xsl:call-template>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:choose>
+    <!-- the personname element is a specialcase -->
+    <xsl:when test="$node/personname">
+      <xsl:call-template name="person.name">
+        <xsl:with-param name="node" select="$node/personname"/>
+      </xsl:call-template>
+    </xsl:when>
+
+    <!-- handle corpauthor as a special case...-->
+    <xsl:when test="name($node)='corpauthor'">
+      <xsl:apply-templates select="$node"/>
+    </xsl:when>
+
+    <xsl:otherwise>
+      <xsl:choose>
+        <xsl:when test="$style = 'family-given'">
+          <xsl:call-template name="person.name.family-given">
+            <xsl:with-param name="node" select="$node"/>
+          </xsl:call-template>
+        </xsl:when>
+        <xsl:when test="$style = 'last-first'">
+          <xsl:call-template name="person.name.last-first">
+            <xsl:with-param name="node" select="$node"/>
+          </xsl:call-template>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:call-template name="person.name.first-last">
+            <xsl:with-param name="node" select="$node"/>
+          </xsl:call-template>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="person.name.family-given">
+  <xsl:param name="node" select="."/>
+
+  <!-- The family-given style applies a convention for identifying given -->
+  <!-- and family names in locales where it may be ambiguous -->
+  <xsl:apply-templates select="$node//surname[1]"/>
+
+  <xsl:if test="$node//surname and $node//firstname">
+    <xsl:text> </xsl:text>
+  </xsl:if>
+
+  <xsl:apply-templates select="$node//firstname[1]"/>
+
+  <xsl:text> [FAMILY Given]</xsl:text>
+</xsl:template>
+
+<xsl:template name="person.name.last-first">
+  <xsl:param name="node" select="."/>
+
+  <xsl:apply-templates select="$node//surname[1]"/>
+
+  <xsl:if test="$node//surname and $node//firstname">
+    <xsl:text>, </xsl:text>
+  </xsl:if>
+
+  <xsl:apply-templates select="$node//firstname[1]"/>
+</xsl:template>
+
+<xsl:template name="person.name.first-last">
+  <xsl:param name="node" select="."/>
+
+  <xsl:if test="$node//honorific">
+    <xsl:apply-templates select="$node//honorific[1]"/>
+    <xsl:value-of select="$punct.honorific"/>
+  </xsl:if>
+
+  <xsl:if test="$node//firstname">
+    <xsl:if test="$node//honorific">
+      <xsl:text> </xsl:text>
+    </xsl:if>
+    <xsl:apply-templates select="$node//firstname[1]"/>
+  </xsl:if>
+
+  <xsl:if test="$node//othername and $author.othername.in.middle != 0">
+    <xsl:if test="$node//honorific or $node//firstname">
+      <xsl:text> </xsl:text>
+    </xsl:if>
+    <xsl:apply-templates select="$node//othername[1]"/>
+  </xsl:if>
+
+  <xsl:if test="$node//surname">
+    <xsl:if test="$node//honorific or $node//firstname
+                  or ($node//othername and $author.othername.in.middle != 0)">
+      <xsl:text> </xsl:text>
+    </xsl:if>
+    <xsl:apply-templates select="$node//surname[1]"/>
+  </xsl:if>
+
+  <xsl:if test="$node//lineage">
+    <xsl:text>, </xsl:text>
+    <xsl:apply-templates select="$node//lineage[1]"/>
+  </xsl:if>
+</xsl:template>
+
+<xsl:template name="person.name.list">
+  <!-- Return a formatted string representation of the contents of
+       the current element. The current element must contain one or
+       more AUTHORs, CORPAUTHORs, OTHERCREDITs, and/or EDITORs.
+
+       John Doe
+     or
+       John Doe and Jane Doe
+     or
+       John Doe, Jane Doe, and A. Nonymous
+  -->
+  <xsl:param name="person.list"
+             select="author|corpauthor|othercredit|editor"/>
+  <xsl:param name="person.count" select="count($person.list)"/>
+  <xsl:param name="count" select="1"/>
+
+  <xsl:choose>
+    <xsl:when test="$count &gt; $person.count"></xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="person.name">
+        <xsl:with-param name="node" select="$person.list[position()=$count]"/>
+      </xsl:call-template>
+
+      <xsl:choose>
+        <xsl:when test="$person.count = 2 and $count = 1">
+          <xsl:call-template name="gentext.template">
+            <xsl:with-param name="context" select="'authorgroup'"/>
+            <xsl:with-param name="name" select="'sep2'"/>
+          </xsl:call-template>
+        </xsl:when>
+        <xsl:when test="$person.count &gt; 2 and $count+1 = $person.count">
+          <xsl:call-template name="gentext.template">
+            <xsl:with-param name="context" select="'authorgroup'"/>
+            <xsl:with-param name="name" select="'seplast'"/>
+          </xsl:call-template>
+        </xsl:when>
+        <xsl:when test="$count &lt; $person.count">
+          <xsl:call-template name="gentext.template">
+            <xsl:with-param name="context" select="'authorgroup'"/>
+            <xsl:with-param name="name" select="'sep'"/>
+          </xsl:call-template>
+        </xsl:when>
+      </xsl:choose>
+
+      <xsl:call-template name="person.name.list">
+        <xsl:with-param name="person.list" select="$person.list"/>
+        <xsl:with-param name="person.count" select="$person.count"/>
+        <xsl:with-param name="count" select="$count+1"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template><!-- person.name.list -->
+
+<!-- === synopsis ======================================================= -->
+<!-- The following definitions match those given in the reference
+     documentation for DocBook V3.0
+-->
+
+<xsl:variable name="arg.choice.opt.open.str">[</xsl:variable>
+<xsl:variable name="arg.choice.opt.close.str">]</xsl:variable>
+<xsl:variable name="arg.choice.req.open.str">{</xsl:variable>
+<xsl:variable name="arg.choice.req.close.str">}</xsl:variable>
+<xsl:variable name="arg.choice.plain.open.str"><xsl:text> </xsl:text></xsl:variable>
+<xsl:variable name="arg.choice.plain.close.str"><xsl:text> </xsl:text></xsl:variable>
+<xsl:variable name="arg.choice.def.open.str">[</xsl:variable>
+<xsl:variable name="arg.choice.def.close.str">]</xsl:variable>
+<xsl:variable name="arg.rep.repeat.str">...</xsl:variable>
+<xsl:variable name="arg.rep.norepeat.str"></xsl:variable>
+<xsl:variable name="arg.rep.def.str"></xsl:variable>
+<xsl:variable name="arg.or.sep"> | </xsl:variable>
+<xsl:variable name="cmdsynopsis.hanging.indent">4pi</xsl:variable>
+
+<!-- ====================================================================== -->
+
+<!--
+<xsl:template name="xref.g.subst">
+  <xsl:param name="string"></xsl:param>
+  <xsl:param name="target" select="."/>
+  <xsl:variable name="subst">%g</xsl:variable>
+
+  <xsl:choose>
+    <xsl:when test="contains($string, $subst)">
+      <xsl:value-of select="substring-before($string, $subst)"/>
+      <xsl:call-template name="gentext.element.name">
+        <xsl:with-param name="element.name" select="name($target)"/>
+      </xsl:call-template>
+      <xsl:call-template name="xref.g.subst">
+        <xsl:with-param name="string"
+                        select="substring-after($string, $subst)"/>
+        <xsl:with-param name="target" select="$target"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:value-of select="$string"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="xref.t.subst">
+  <xsl:param name="string"></xsl:param>
+  <xsl:param name="target" select="."/>
+  <xsl:variable name="subst">%t</xsl:variable>
+
+  <xsl:choose>
+    <xsl:when test="contains($string, $subst)">
+      <xsl:call-template name="xref.g.subst">
+        <xsl:with-param name="string"
+                        select="substring-before($string, $subst)"/>
+        <xsl:with-param name="target" select="$target"/>
+      </xsl:call-template>
+      <xsl:call-template name="title.xref">
+        <xsl:with-param name="target" select="$target"/>
+      </xsl:call-template>
+      <xsl:call-template name="xref.t.subst">
+        <xsl:with-param name="string"
+                        select="substring-after($string, $subst)"/>
+        <xsl:with-param name="target" select="$target"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="xref.g.subst">
+        <xsl:with-param name="string" select="$string"/>
+        <xsl:with-param name="target" select="$target"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="xref.n.subst">
+  <xsl:param name="string"></xsl:param>
+  <xsl:param name="target" select="."/>
+  <xsl:variable name="subst">%n</xsl:variable>
+
+  <xsl:choose>
+    <xsl:when test="contains($string, $subst)">
+      <xsl:call-template name="xref.t.subst">
+        <xsl:with-param name="string"
+                        select="substring-before($string, $subst)"/>
+        <xsl:with-param name="target" select="$target"/>
+      </xsl:call-template>
+      <xsl:call-template name="number.xref">
+        <xsl:with-param name="target" select="$target"/>
+      </xsl:call-template>
+      <xsl:call-template name="xref.t.subst">
+        <xsl:with-param name="string"
+                        select="substring-after($string, $subst)"/>
+        <xsl:with-param name="target" select="$target"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="xref.t.subst">
+        <xsl:with-param name="string" select="$string"/>
+        <xsl:with-param name="target" select="$target"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="subst.xref.text">
+  <xsl:param name="xref.text"></xsl:param>
+  <xsl:param name="target" select="."/>
+
+  <xsl:call-template name="xref.n.subst">
+    <xsl:with-param name="string" select="$xref.text"/>
+    <xsl:with-param name="target" select="$target"/>
+  </xsl:call-template>
+</xsl:template>
+-->
+
+<!-- ====================================================================== -->
+
+<xsl:template name="filename-basename">
+  <!-- We assume all filenames are really URIs and use "/" -->
+  <xsl:param name="filename"></xsl:param>
+  <xsl:param name="recurse" select="false()"/>
+
+  <xsl:choose>
+    <xsl:when test="substring-after($filename, '/') != ''">
+      <xsl:call-template name="filename-basename">
+        <xsl:with-param name="filename"
+                        select="substring-after($filename, '/')"/>
+        <xsl:with-param name="recurse" select="true()"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:value-of select="$filename"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="filename-extension">
+  <xsl:param name="filename"></xsl:param>
+  <xsl:param name="recurse" select="false()"/>
+
+  <!-- Make sure we only look at the base name... -->
+  <xsl:variable name="basefn">
+    <xsl:choose>
+      <xsl:when test="$recurse">
+        <xsl:value-of select="$filename"/>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:call-template name="filename-basename">
+          <xsl:with-param name="filename" select="$filename"/>
+        </xsl:call-template>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:choose>
+    <xsl:when test="substring-after($basefn, '.') != ''">
+      <xsl:call-template name="filename-extension">
+        <xsl:with-param name="filename"
+                        select="substring-after($basefn, '.')"/>
+        <xsl:with-param name="recurse" select="true()"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:when test="$recurse">
+      <xsl:value-of select="$basefn"/>
+    </xsl:when>
+    <xsl:otherwise></xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ====================================================================== -->
+
+<doc:template name="select.mediaobject" xmlns="">
+<refpurpose>Selects and processes an appropriate media object from a list</refpurpose>
+
+<refdescription>
+<para>This template takes a list of media objects (usually the
+children of a mediaobject or inlinemediaobject) and processes
+the "right" object.</para>
+
+<para>This template relies on a template named 
+"select.mediaobject.index" to determine which object
+in the list is appropriate.</para>
+
+<para>If no acceptable object is located, nothing happens.</para>
+</refdescription>
+
+<refparameter>
+<variablelist>
+<varlistentry><term>olist</term>
+<listitem>
+<para>The node list of potential objects to examine.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</refparameter>
+
+<refreturn>
+<para>Calls &lt;xsl:apply-templates&gt; on the selected object.</para>
+</refreturn>
+</doc:template>
+
+<xsl:template name="select.mediaobject">
+  <xsl:param name="olist"
+             select="imageobject|imageobjectco
+                     |videoobject|audioobject|textobject"/>
+  
+  <xsl:variable name="mediaobject.index">
+    <xsl:call-template name="select.mediaobject.index">
+      <xsl:with-param name="olist" select="$olist"/>
+      <xsl:with-param name="count" select="1"/>
+    </xsl:call-template>
+  </xsl:variable>
+
+  <xsl:if test="$mediaobject.index != ''">
+    <xsl:apply-templates select="$olist[position() = $mediaobject.index]"/>
+  </xsl:if>
+</xsl:template>
+
+<!-- ====================================================================== -->
+
+<doc:template name="select.mediaobject.index" xmlns="">
+<refpurpose>Selects the position of the appropriate media object from a list</refpurpose>
+
+<refdescription>
+<para>This template takes a list of media objects (usually the
+children of a mediaobject or inlinemediaobject) and determines
+the "right" object. It returns the position of that object
+to be used by the calling template.</para>
+
+<para>If the parameter <parameter>use.role.for.mediaobject</parameter>
+is nonzero, then it first checks for an object with
+a role attribute of the appropriate value.  It takes the first
+of those.  Otherwise, it takes the first acceptable object
+through a recursive pass through the list.</para>
+
+<para>This template relies on a template named "is.acceptable.mediaobject"
+to determine if a given object is an acceptable graphic. The semantics
+of media objects is that the first acceptable graphic should be used.
+</para>
+
+<para>If no acceptable object is located, no index is returned.</para>
+</refdescription>
+
+<refparameter>
+<variablelist>
+<varlistentry><term>olist</term>
+<listitem>
+<para>The node list of potential objects to examine.</para>
+</listitem>
+</varlistentry>
+<varlistentry><term>count</term>
+<listitem>
+<para>The position in the list currently being considered by the 
+recursive process.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</refparameter>
+
+<refreturn>
+<para>Returns the position in the original list of the selected object.</para>
+</refreturn>
+</doc:template>
+
+<xsl:template name="select.mediaobject.index">
+  <xsl:param name="olist"
+             select="imageobject|imageobjectco
+                     |videoobject|audioobject|textobject"/>
+  <xsl:param name="count">1</xsl:param>
+
+  <xsl:choose>
+    <!-- Test for objects preferred by role -->
+    <xsl:when test="$use.role.for.mediaobject != 0 
+               and $preferred.mediaobject.role != ''
+               and $olist[@role = $preferred.mediaobject.role]"> 
+      
+      <!-- Get the first hit's position index -->
+      <xsl:for-each select="$olist">
+        <xsl:if test="@role = $preferred.mediaobject.role and
+             not(preceding-sibling::*[@role = $preferred.mediaobject.role])"> 
+          <xsl:value-of select="position()"/> 
+        </xsl:if>
+      </xsl:for-each>
+    </xsl:when>
+
+    <xsl:when test="$use.role.for.mediaobject != 0 
+               and $olist[@role = $stylesheet.result.type]">
+      <!-- Get the first hit's position index -->
+      <xsl:for-each select="$olist">
+        <xsl:if test="@role = $stylesheet.result.type and 
+              not(preceding-sibling::*[@role = $stylesheet.result.type])"> 
+          <xsl:value-of select="position()"/> 
+        </xsl:if>
+      </xsl:for-each>
+    </xsl:when>
+    <!-- Accept 'html' for $stylesheet.result.type = 'xhtml' -->
+    <xsl:when test="$use.role.for.mediaobject != 0 
+               and $stylesheet.result.type = 'xhtml'
+               and $olist[@role = 'html']">
+      <!-- Get the first hit's position index -->
+      <xsl:for-each select="$olist">
+        <xsl:if test="@role = 'html' and 
+              not(preceding-sibling::*[@role = 'html'])"> 
+          <xsl:value-of select="position()"/> 
+        </xsl:if>
+      </xsl:for-each>
+    </xsl:when>
+    <xsl:otherwise>
+      <!-- Otherwise select first acceptable object -->
+      <xsl:if test="$count &lt;= count($olist)">
+        <xsl:variable name="object" select="$olist[position()=$count]"/>
+    
+        <xsl:variable name="useobject">
+          <xsl:choose>
+            <!-- The phrase is used only when contains TeX Math and output is FO -->
+            <xsl:when test="name($object)='textobject' and $object/phrase
+                            and $object/@role='tex' and $stylesheet.result.type = 'fo'
+                            and $tex.math.in.alt != ''">
+              <xsl:text>1</xsl:text> 
+            </xsl:when>
+            <!-- The phrase is never used -->
+            <xsl:when test="name($object)='textobject' and $object/phrase">
+              <xsl:text>0</xsl:text>
+            </xsl:when>
+            <xsl:when test="name($object)='textobject'
+                            and $object/ancestor::equation ">
+            <!-- The first textobject is not a reasonable fallback
+                 for equation image -->
+              <xsl:text>0</xsl:text>
+            </xsl:when>
+            <!-- The first textobject is a reasonable fallback -->
+            <xsl:when test="name($object)='textobject'
+                            and $object[not(@role) or @role!='tex']">
+              <xsl:text>1</xsl:text>
+            </xsl:when>
+            <!-- don't use graphic when output is FO, TeX Math is used 
+                 and there is math in alt element -->
+            <xsl:when test="$object/ancestor::equation and 
+                            $object/ancestor::equation/alt[@role='tex']
+                            and $stylesheet.result.type = 'fo'
+                            and $tex.math.in.alt != ''">
+              <xsl:text>0</xsl:text>
+            </xsl:when>
+            <!-- If there's only one object, use it -->
+            <xsl:when test="$count = 1 and count($olist) = 1">
+               <xsl:text>1</xsl:text>
+            </xsl:when>
+            <!-- Otherwise, see if this one is a useable graphic -->
+            <xsl:otherwise>
+              <xsl:choose>
+                <!-- peek inside imageobjectco to simplify the test -->
+                <xsl:when test="local-name($object) = 'imageobjectco'">
+                  <xsl:call-template name="is.acceptable.mediaobject">
+                    <xsl:with-param name="object" select="$object/imageobject"/>
+                  </xsl:call-template>
+                </xsl:when>
+                <xsl:otherwise>
+                  <xsl:call-template name="is.acceptable.mediaobject">
+                    <xsl:with-param name="object" select="$object"/>
+                  </xsl:call-template>
+                </xsl:otherwise>
+              </xsl:choose>
+            </xsl:otherwise>
+          </xsl:choose>
+        </xsl:variable>
+    
+        <xsl:choose>
+          <xsl:when test="$useobject='1'">
+            <xsl:value-of select="$count"/>
+          </xsl:when>
+          <xsl:otherwise>
+            <xsl:call-template name="select.mediaobject.index">
+              <xsl:with-param name="olist" select="$olist"/>
+              <xsl:with-param name="count" select="$count + 1"/>
+            </xsl:call-template>
+          </xsl:otherwise>
+        </xsl:choose>
+      </xsl:if>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<doc:template name="is.acceptable.mediaobject" xmlns="">
+<refpurpose>Returns '1' if the specified media object is recognized.</refpurpose>
+
+<refdescription>
+<para>This template examines a media object and returns '1' if the
+object is recognized as a graphic.</para>
+</refdescription>
+
+<refparameter>
+<variablelist>
+<varlistentry><term>object</term>
+<listitem>
+<para>The media object to consider.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</refparameter>
+
+<refreturn>
+<para>0 or 1</para>
+</refreturn>
+</doc:template>
+
+<xsl:template name="is.acceptable.mediaobject">
+  <xsl:param name="object"></xsl:param>
+
+  <xsl:variable name="filename">
+    <xsl:call-template name="mediaobject.filename">
+      <xsl:with-param name="object" select="$object"/>
+    </xsl:call-template>
+  </xsl:variable>
+
+  <xsl:variable name="ext">
+    <xsl:call-template name="filename-extension">
+      <xsl:with-param name="filename" select="$filename"/>
+    </xsl:call-template>
+  </xsl:variable>
+
+  <!-- there will only be one -->
+  <xsl:variable name="data" select="$object/videodata
+                                    |$object/imagedata
+                                    |$object/audiodata"/>
+
+  <xsl:variable name="format" select="$data/@format"/>
+
+  <xsl:variable name="graphic.format">
+    <xsl:if test="$format">
+      <xsl:call-template name="is.graphic.format">
+        <xsl:with-param name="format" select="$format"/>
+      </xsl:call-template>
+    </xsl:if>
+  </xsl:variable>
+
+  <xsl:variable name="graphic.ext">
+    <xsl:if test="$ext">
+      <xsl:call-template name="is.graphic.extension">
+        <xsl:with-param name="ext" select="$ext"/>
+      </xsl:call-template>
+    </xsl:if>
+  </xsl:variable>
+
+  <xsl:choose>
+    <xsl:when test="$use.svg = 0 and $format = 'SVG'">0</xsl:when>
+    <xsl:when xmlns:svg="http://www.w3.org/2000/svg"
+              test="$use.svg != 0 and $object/svg:*">1</xsl:when>
+    <xsl:when test="$graphic.format = '1'">1</xsl:when>
+    <xsl:when test="$graphic.ext = '1'">1</xsl:when>
+    <xsl:otherwise>0</xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="mediaobject.filename">
+  <xsl:param name="object"></xsl:param>
+
+  <xsl:variable name="data" select="$object/videodata
+                                    |$object/imagedata
+                                    |$object/audiodata
+                                    |$object"/>
+
+  <xsl:variable name="filename">
+    <xsl:choose>
+      <xsl:when test="$data[@fileref]">
+        <xsl:value-of select="$data/@fileref"/>
+      </xsl:when>
+      <xsl:when test="$data[@entityref]">
+        <xsl:value-of select="unparsed-entity-uri($data/@entityref)"/>
+      </xsl:when>
+      <xsl:otherwise></xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:variable name="real.ext">
+    <xsl:call-template name="filename-extension">
+      <xsl:with-param name="filename" select="$filename"/>
+    </xsl:call-template>
+  </xsl:variable>
+
+  <xsl:variable name="ext">
+    <xsl:choose>
+      <xsl:when test="$real.ext != ''">
+        <xsl:value-of select="$real.ext"/>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:value-of select="$graphic.default.extension"/>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:variable name="graphic.ext">
+    <xsl:call-template name="is.graphic.extension">
+      <xsl:with-param name="ext" select="$ext"/>
+    </xsl:call-template>
+  </xsl:variable>
+
+  <xsl:choose>
+    <xsl:when test="$real.ext = ''">
+      <xsl:choose>
+        <xsl:when test="$ext != ''">
+          <xsl:value-of select="$filename"/>
+          <xsl:text>.</xsl:text>
+          <xsl:value-of select="$ext"/>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:value-of select="$filename"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:when test="not($graphic.ext)">
+      <xsl:choose>
+        <xsl:when test="$graphic.default.extension != ''">
+          <xsl:value-of select="$filename"/>
+          <xsl:text>.</xsl:text>
+          <xsl:value-of select="$graphic.default.extension"/>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:value-of select="$filename"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:value-of select="$filename"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ====================================================================== -->
+
+<doc:template name="check.id.unique" xmlns="">
+<refpurpose>Warn users about references to non-unique IDs</refpurpose>
+<refdescription>
+<para>If passed an ID in <varname>linkend</varname>,
+<function>check.id.unique</function> prints
+a warning message to the user if either the ID does not exist or
+the ID is not unique.</para>
+</refdescription>
+</doc:template>
+
+<xsl:template name="check.id.unique">
+  <xsl:param name="linkend"></xsl:param>
+  <xsl:if test="$linkend != ''">
+    <xsl:variable name="targets" select="key('id',$linkend)"/>
+    <xsl:variable name="target" select="$targets[1]"/>
+
+    <xsl:if test="count($targets)=0">
+      <xsl:message>
+        <xsl:text>Error: no ID for constraint linkend: </xsl:text>
+        <xsl:value-of select="$linkend"/>
+        <xsl:text>.</xsl:text>
+      </xsl:message>
+      <!--
+      <xsl:message>
+        <xsl:text>If the ID exists in your document, did your </xsl:text>
+        <xsl:text>XSLT Processor load the DTD?</xsl:text>
+      </xsl:message>
+      -->
+    </xsl:if>
+
+    <xsl:if test="count($targets)>1">
+      <xsl:message>
+        <xsl:text>Warning: multiple "IDs" for constraint linkend: </xsl:text>
+        <xsl:value-of select="$linkend"/>
+        <xsl:text>.</xsl:text>
+      </xsl:message>
+    </xsl:if>
+  </xsl:if>
+</xsl:template>
+
+<doc:template name="check.idref.targets" xmlns="">
+<refpurpose>Warn users about incorrectly typed references</refpurpose>
+<refdescription>
+<para>If passed an ID in <varname>linkend</varname>,
+<function>check.idref.targets</function> makes sure that the element
+pointed to by the link is one of the elements listed in
+<varname>element-list</varname> and warns the user otherwise.</para>
+</refdescription>
+</doc:template>
+
+<xsl:template name="check.idref.targets">
+  <xsl:param name="linkend"></xsl:param>
+  <xsl:param name="element-list"></xsl:param>
+  <xsl:if test="$linkend != ''">
+    <xsl:variable name="targets" select="key('id',$linkend)"/>
+    <xsl:variable name="target" select="$targets[1]"/>
+
+    <xsl:if test="count($target) &gt; 0">
+      <xsl:if test="not(contains(concat(' ', $element-list, ' '), name($target)))">
+        <xsl:message>
+          <xsl:text>Error: linkend (</xsl:text>
+          <xsl:value-of select="$linkend"/>
+          <xsl:text>) points to "</xsl:text>
+          <xsl:value-of select="name($target)"/>
+          <xsl:text>" not (one of): </xsl:text>
+          <xsl:value-of select="$element-list"/>
+        </xsl:message>
+      </xsl:if>
+    </xsl:if>
+  </xsl:if>
+</xsl:template>
+
+<!-- ====================================================================== -->
+<!-- Procedure Step Numeration -->
+
+<xsl:param name="procedure.step.numeration.formats" select="'1aiAI'"/>
+
+<xsl:template name="procedure.step.numeration">
+  <xsl:param name="context" select="."/>
+  <xsl:variable name="format.length"
+                select="string-length($procedure.step.numeration.formats)"/>
+  <xsl:choose>
+    <xsl:when test="local-name($context) = 'substeps'">
+      <xsl:variable name="ssdepth"
+                    select="count($context/ancestor::substeps)"/>
+      <xsl:variable name="sstype" select="($ssdepth mod $format.length)+2"/>
+      <xsl:choose>
+        <xsl:when test="$sstype &gt; $format.length">
+          <xsl:value-of select="substring($procedure.step.numeration.formats,1,1)"/>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:value-of select="substring($procedure.step.numeration.formats,$sstype,1)"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:when test="local-name($context) = 'step'">
+      <xsl:variable name="sdepth"
+                    select="count($context/ancestor::substeps)"/>
+      <xsl:variable name="stype" select="($sdepth mod $format.length)+1"/>
+      <xsl:value-of select="substring($procedure.step.numeration.formats,$stype,1)"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:message>
+        <xsl:text>Unexpected context in procedure.step.numeration: </xsl:text>
+        <xsl:value-of select="local-name($context)"/>
+      </xsl:message>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="step" mode="number">
+  <xsl:param name="rest" select="''"/>
+  <xsl:param name="recursive" select="1"/>
+  <xsl:variable name="format">
+    <xsl:call-template name="procedure.step.numeration"/>
+  </xsl:variable>
+  <xsl:variable name="num">
+    <xsl:number count="step" format="{$format}"/>
+  </xsl:variable>
+  <xsl:choose>
+    <xsl:when test="$recursive != 0 and ancestor::step">
+      <xsl:apply-templates select="ancestor::step[1]" mode="number">
+        <xsl:with-param name="rest" select="concat('.', $num, $rest)"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:value-of select="concat($num, $rest)"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ====================================================================== -->
+<!-- OrderedList Numeration -->
+
+<xsl:template name="orderedlist-starting-number">
+  <xsl:param name="list" select="."/>
+  <xsl:choose>
+    <xsl:when test="not($list/@continuation = 'continues')">1</xsl:when>
+    <xsl:otherwise>
+      <xsl:variable name="prevlist"
+                    select="$list/preceding::orderedlist[1]"/>
+      <xsl:choose>
+        <xsl:when test="count($prevlist) = 0">2</xsl:when>
+        <xsl:otherwise>
+          <xsl:variable name="prevlength" select="count($prevlist/listitem)"/>
+          <xsl:variable name="prevstart">
+            <xsl:call-template name="orderedlist-starting-number">
+              <xsl:with-param name="list" select="$prevlist"/>
+            </xsl:call-template>
+          </xsl:variable>
+          <xsl:value-of select="$prevstart + $prevlength"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="orderedlist-item-number">
+  <!-- context node must be a listitem in an orderedlist -->
+  <xsl:param name="node" select="."/>
+
+  <xsl:choose>
+    <xsl:when test="$node/@override">
+      <xsl:value-of select="$node/@override"/>
+    </xsl:when>
+    <xsl:when test="$node/preceding-sibling::listitem">
+      <xsl:variable name="pnum">
+        <xsl:call-template name="orderedlist-item-number">
+          <xsl:with-param name="node" select="$node/preceding-sibling::listitem[1]"/>
+        </xsl:call-template>
+      </xsl:variable>
+      <xsl:value-of select="$pnum + 1"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="orderedlist-starting-number">
+        <xsl:with-param name="list" select="parent::*"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="next.numeration">
+  <xsl:param name="numeration" select="'default'"/>
+  <xsl:choose>
+    <!-- Change this list if you want to change the order of numerations -->
+    <xsl:when test="$numeration = 'arabic'">loweralpha</xsl:when>
+    <xsl:when test="$numeration = 'loweralpha'">lowerroman</xsl:when>
+    <xsl:when test="$numeration = 'lowerroman'">upperalpha</xsl:when>
+    <xsl:when test="$numeration = 'upperalpha'">upperroman</xsl:when>
+    <xsl:when test="$numeration = 'upperroman'">arabic</xsl:when>
+    <xsl:otherwise>arabic</xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="list.numeration">
+  <xsl:param name="node" select="."/>
+
+  <xsl:choose>
+    <xsl:when test="$node/@numeration">
+      <xsl:value-of select="$node/@numeration"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:choose>
+        <xsl:when test="$node/ancestor::orderedlist">
+          <xsl:call-template name="next.numeration">
+            <xsl:with-param name="numeration">
+              <xsl:call-template name="list.numeration">
+                <xsl:with-param name="node" select="$node/ancestor::orderedlist[1]"/>
+              </xsl:call-template>
+            </xsl:with-param>
+          </xsl:call-template>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:call-template name="next.numeration"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ====================================================================== -->
+<!-- ItemizedList "Numeration" -->
+
+<xsl:template name="next.itemsymbol">
+  <xsl:param name="itemsymbol" select="'default'"/>
+  <xsl:choose>
+    <!-- Change this list if you want to change the order of symbols -->
+    <xsl:when test="$itemsymbol = 'disc'">circle</xsl:when>
+    <xsl:when test="$itemsymbol = 'round'">square</xsl:when>
+    <xsl:otherwise>disc</xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="list.itemsymbol">
+  <xsl:param name="node" select="."/>
+
+  <xsl:choose>
+    <xsl:when test="$node/@mark">
+      <xsl:value-of select="$node/@mark"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:choose>
+        <xsl:when test="$node/ancestor::itemizedlist">
+          <xsl:call-template name="next.itemsymbol">
+            <xsl:with-param name="itemsymbol">
+              <xsl:call-template name="list.itemsymbol">
+                <xsl:with-param name="node" select="$node/ancestor::itemizedlist[1]"/>
+              </xsl:call-template>
+            </xsl:with-param>
+          </xsl:call-template>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:call-template name="next.itemsymbol"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ====================================================================== -->
+
+<doc:template name="copyright.years" xmlns="">
+<refpurpose>Print a set of years with collapsed ranges</refpurpose>
+
+<refdescription>
+<para>This template prints a list of year elements with consecutive
+years printed as a range. In other words:</para>
+
+<screen><![CDATA[<year>1992</year>
+<year>1993</year>
+<year>1994</year>]]></screen>
+
+<para>is printed <quote>1992-1994</quote>, whereas:</para>
+
+<screen><![CDATA[<year>1992</year>
+<year>1994</year>]]></screen>
+
+<para>is printed <quote>1992, 1994</quote>.</para>
+
+<para>This template assumes that all the year elements contain only
+decimal year numbers, that the elements are sorted in increasing
+numerical order, that there are no duplicates, and that all the years
+are expressed in full <quote>century+year</quote>
+(<quote>1999</quote> not <quote>99</quote>) notation.</para>
+</refdescription>
+
+<refparameter>
+<variablelist>
+<varlistentry><term>years</term>
+<listitem>
+<para>The initial set of year elements.</para>
+</listitem>
+</varlistentry>
+<varlistentry><term>print.ranges</term>
+<listitem>
+<para>If non-zero, multi-year ranges are collapsed. If zero, all years
+are printed discretely.</para>
+</listitem>
+</varlistentry>
+<varlistentry><term>single.year.ranges</term>
+<listitem>
+<para>If non-zero, two consecutive years will be printed as a range,
+otherwise, they will be printed discretely. In other words, a single
+year range is <quote>1991-1992</quote> but discretely it's
+<quote>1991, 1992</quote>.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</refparameter>
+
+<refreturn>
+<para>This template returns the formatted list of years.</para>
+</refreturn>
+</doc:template>
+
+<xsl:template name="copyright.years">
+  <xsl:param name="years"/>
+  <xsl:param name="print.ranges" select="1"/>
+  <xsl:param name="single.year.ranges" select="0"/>
+  <xsl:param name="firstyear" select="0"/>
+  <xsl:param name="nextyear" select="0"/>
+
+  <!--
+  <xsl:message terminate="no">
+    <xsl:text>CY: </xsl:text>
+    <xsl:value-of select="count($years)"/>
+    <xsl:text>, </xsl:text>
+    <xsl:value-of select="$firstyear"/>
+    <xsl:text>, </xsl:text>
+    <xsl:value-of select="$nextyear"/>
+    <xsl:text>, </xsl:text>
+    <xsl:value-of select="$print.ranges"/>
+    <xsl:text>, </xsl:text>
+    <xsl:value-of select="$single.year.ranges"/>
+    <xsl:text> (</xsl:text>
+    <xsl:value-of select="$years[1]"/>
+    <xsl:text>)</xsl:text>
+  </xsl:message>
+  -->
+
+  <xsl:choose>
+    <xsl:when test="$print.ranges = 0 and count($years) &gt; 0">
+      <xsl:choose>
+        <xsl:when test="count($years) = 1">
+          <xsl:apply-templates select="$years[1]" mode="titlepage.mode"/>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:apply-templates select="$years[1]" mode="titlepage.mode"/>
+          <xsl:text>, </xsl:text>
+          <xsl:call-template name="copyright.years">
+            <xsl:with-param name="years"
+                            select="$years[position() &gt; 1]"/>
+            <xsl:with-param name="print.ranges" select="$print.ranges"/>
+            <xsl:with-param name="single.year.ranges"
+                            select="$single.year.ranges"/>
+          </xsl:call-template>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:when test="count($years) = 0">
+      <xsl:variable name="lastyear" select="$nextyear - 1"/>
+      <xsl:choose>
+        <xsl:when test="$firstyear = 0">
+          <!-- there weren't any years at all -->
+        </xsl:when>
+        <xsl:when test="$firstyear = $lastyear">
+          <xsl:value-of select="$firstyear"/>
+        </xsl:when>
+        <xsl:when test="$single.year.ranges = 0
+                        and $lastyear = $firstyear + 1">
+          <xsl:value-of select="$firstyear"/>
+          <xsl:text>, </xsl:text>
+          <xsl:value-of select="$lastyear"/>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:value-of select="$firstyear"/>
+          <xsl:text>-</xsl:text>
+          <xsl:value-of select="$lastyear"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:when test="$firstyear = 0">
+      <xsl:call-template name="copyright.years">
+        <xsl:with-param name="years"
+                        select="$years[position() &gt; 1]"/>
+        <xsl:with-param name="firstyear" select="$years[1]"/>
+        <xsl:with-param name="nextyear" select="$years[1] + 1"/>
+        <xsl:with-param name="print.ranges" select="$print.ranges"/>
+        <xsl:with-param name="single.year.ranges"
+                        select="$single.year.ranges"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:when test="$nextyear = $years[1]">
+      <xsl:call-template name="copyright.years">
+        <xsl:with-param name="years"
+                        select="$years[position() &gt; 1]"/>
+        <xsl:with-param name="firstyear" select="$firstyear"/>
+        <xsl:with-param name="nextyear" select="$nextyear + 1"/>
+        <xsl:with-param name="print.ranges" select="$print.ranges"/>
+        <xsl:with-param name="single.year.ranges"
+                        select="$single.year.ranges"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <!-- we have years left, but they aren't in the current range -->
+      <xsl:choose>
+        <xsl:when test="$nextyear = $firstyear + 1">
+          <xsl:value-of select="$firstyear"/>
+          <xsl:text>, </xsl:text>
+        </xsl:when>
+        <xsl:when test="$single.year.ranges = 0
+                        and $nextyear = $firstyear + 2">
+          <xsl:value-of select="$firstyear"/>
+          <xsl:text>, </xsl:text>
+          <xsl:value-of select="$nextyear - 1"/>
+          <xsl:text>, </xsl:text>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:value-of select="$firstyear"/>
+          <xsl:text>-</xsl:text>
+          <xsl:value-of select="$nextyear - 1"/>
+          <xsl:text>, </xsl:text>
+        </xsl:otherwise>
+      </xsl:choose>
+      <xsl:call-template name="copyright.years">
+        <xsl:with-param name="years"
+                        select="$years[position() &gt; 1]"/>
+        <xsl:with-param name="firstyear" select="$years[1]"/>
+        <xsl:with-param name="nextyear" select="$years[1] + 1"/>
+        <xsl:with-param name="print.ranges" select="$print.ranges"/>
+        <xsl:with-param name="single.year.ranges"
+                        select="$single.year.ranges"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ====================================================================== -->
+
+<doc:template name="find.path.params" xmlns="">
+<refpurpose>Search in a table for the "best" match for the node</refpurpose>
+
+<refdescription>
+<para>This template searches in a table for the value that most-closely
+(in the typical best-match sense of XSLT) matches the current (element)
+node location.</para>
+</refdescription>
+</doc:template>
+
+<xsl:template name="find.path.params">
+  <xsl:param name="node" select="."/>
+  <xsl:param name="table" select="''"/>
+  <xsl:param name="location">
+    <xsl:call-template name="xpath.location">
+      <xsl:with-param name="node" select="$node"/>
+    </xsl:call-template>
+  </xsl:param>
+
+  <xsl:variable name="value">
+    <xsl:call-template name="lookup.key">
+      <xsl:with-param name="key" select="$location"/>
+      <xsl:with-param name="table" select="$table"/>
+    </xsl:call-template>
+  </xsl:variable>
+
+  <xsl:choose>
+    <xsl:when test="$value != ''">
+      <xsl:value-of select="$value"/>
+    </xsl:when>
+    <xsl:when test="contains($location, '/')">
+      <xsl:call-template name="find.path.params">
+        <xsl:with-param name="node" select="$node"/>
+        <xsl:with-param name="table" select="$table"/>
+        <xsl:with-param name="location" select="substring-after($location, '/')"/>
+      </xsl:call-template>
+    </xsl:when>
+  </xsl:choose>
+</xsl:template>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/cs.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/cs.xml
new file mode 100644
index 00000000000..4442e00cfca
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/cs.xml
@@ -0,0 +1,491 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="cs" english-language-name="Czech">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+  <l:gentext key="keywordset" text="Kl&#237;&#269;ov&#237;slova"/>
+  <l:gentext key="keyword" text="Kl&#237;&#269;ov&#233;slovo"/>
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/cs.xml -->
+  <l:gentext key="Abstract" text="Abstrakt"/>
+  <l:gentext key="abstract" text="Abstrakt"/>
+  <l:gentext key="Answer" text="Odpov&#283;&#271;:"/>
+  <l:gentext key="answer" text="Odpov&#283;&#271;:"/>
+  <l:gentext key="Appendix" text="P&#345;&#237;loha"/>
+  <l:gentext key="appendix" text="P&#345;&#237;loha"/>
+  <l:gentext key="Article" text="&#268;l&#225;nek"/>
+  <l:gentext key="article" text="&#268;l&#225;nek"/>
+  <l:gentext key="Bibliography" text="Bibliografie"/>
+  <l:gentext key="bibliography" text="Bibliografie"/>
+  <l:gentext key="Book" text="Kniha"/>
+  <l:gentext key="book" text="Kniha"/>
+  <l:gentext key="CAUTION" text="V&#253;straha"/>
+  <l:gentext key="Caution" text="V&#253;straha"/>
+  <l:gentext key="caution" text="V&#253;straha"/>
+  <l:gentext key="Chapter" text="Kapitola"/>
+  <l:gentext key="chapter" text="Kapitola"/>
+  <l:gentext key="Colophon" text="Tir&#225;&#382;"/>
+  <l:gentext key="colophon" text="Tir&#225;&#382;"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="V&#283;nov&#225;n&#237;"/>
+  <l:gentext key="dedication" text="V&#283;nov&#225;n&#237;"/>
+  <l:gentext key="Edition" text="Vyd&#225;n&#237;"/>
+  <l:gentext key="edition" text="Vyd&#225;n&#237;"/>
+  <l:gentext key="Equation" text="Rovnice"/>
+  <l:gentext key="equation" text="Rovnice"/>
+  <l:gentext key="Example" text="P&#345;&#237;klad"/>
+  <l:gentext key="example" text="P&#345;&#237;klad"/>
+  <l:gentext key="Figure" text="Obr&#225;zek"/>
+  <l:gentext key="figure" text="Obr&#225;zek"/>
+  <l:gentext key="Glossary" text="Slovn&#237;k"/>
+  <l:gentext key="glossary" text="Slovn&#237;k"/>
+  <l:gentext key="GlossSee" text="Viz"/>
+  <l:gentext key="glosssee" text="Viz"/>
+  <l:gentext key="GlossSeeAlso" text="Viz t&#233;&#382;"/>
+  <l:gentext key="glossseealso" text="Viz t&#233;&#382;"/>
+  <l:gentext key="IMPORTANT" text="D&#367;le&#382;it&#233;"/>
+  <l:gentext key="Important" text="D&#367;le&#382;it&#233;"/>
+  <l:gentext key="important" text="D&#367;le&#382;it&#233;"/>
+  <l:gentext key="Index" text="Rejst&#345;&#237;k"/>
+  <l:gentext key="index" text="Rejst&#345;&#237;k"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Pr&#225;vn&#237; dolo&#382;ka"/>
+  <l:gentext key="legalnotice" text="Pr&#225;vn&#237; dolo&#382;ka"/>
+  <l:gentext key="MsgAud" text="Publikum"/>
+  <l:gentext key="msgaud" text="Publikum"/>
+  <l:gentext key="MsgLevel" text="&#218;rove&#328;"/>
+  <l:gentext key="msglevel" text="&#218;rove&#328;"/>
+  <l:gentext key="MsgOrig" text="P&#367;vod"/>
+  <l:gentext key="msgorig" text="P&#367;vod"/>
+  <l:gentext key="NOTE" text="Pozn&#225;mka"/>
+  <l:gentext key="Note" text="Pozn&#225;mka"/>
+  <l:gentext key="note" text="Pozn&#225;mka"/>
+  <l:gentext key="Part" text="&#268;&#225;st"/>
+  <l:gentext key="part" text="&#268;&#225;st"/>
+  <l:gentext key="Preface" text="P&#345;edmluva"/>
+  <l:gentext key="preface" text="P&#345;edmluva"/>
+  <l:gentext key="Procedure" text="Postup"/>
+  <l:gentext key="procedure" text="Postup"/>
+  <l:gentext key="ProductionSet" text="Produkce"/>
+  <l:gentext key="Published" text="Vyd&#225;no"/>
+  <l:gentext key="published" text="Vyd&#225;no"/>
+  <l:gentext key="Question" text="Ot&#225;zka:"/>
+  <l:gentext key="question" text="Ot&#225;zka:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Odkaz"/>
+  <l:gentext key="reference" text="Odkaz"/>
+  <l:gentext key="RefName" text="Jm&#233;no"/>
+  <l:gentext key="refname" text="Jm&#233;no"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="P&#345;ehled"/>
+  <l:gentext key="refsynopsisdiv" text="P&#345;ehled"/>
+  <l:gentext key="RevHistory" text="P&#345;ehled reviz&#237;"/>
+  <l:gentext key="revhistory" text="P&#345;ehled reviz&#237;"/>
+  <l:gentext key="Revision" text="Revize"/>
+  <l:gentext key="revision" text="Revize"/>
+  <l:gentext key="sect1" text="Odd&#237;l"/>
+  <l:gentext key="sect2" text="Odd&#237;l"/>
+  <l:gentext key="sect3" text="Odd&#237;l"/>
+  <l:gentext key="sect4" text="Odd&#237;l"/>
+  <l:gentext key="sect5" text="Odd&#237;l"/>
+  <l:gentext key="Section" text="Odd&#237;l"/>
+  <l:gentext key="section" text="Odd&#237;l"/>
+  <l:gentext key="See" text="Viz"/>
+  <l:gentext key="see" text="Viz"/>
+  <l:gentext key="SeeAlso" text="Viz t&#233;&#382;"/>
+  <l:gentext key="Seealso" text="Viz t&#233;&#382;"/>
+  <l:gentext key="seealso" text="Viz t&#233;&#382;"/>
+  <l:gentext key="Set" text="Sada"/>
+  <l:gentext key="set" text="Sada"/>
+  <l:gentext key="SetIndex" text="Rejst&#345;&#237;k sady"/>
+  <l:gentext key="setindex" text="Rejst&#345;&#237;k sady"/>
+  <l:gentext key="Sidebar" text="Margin&#225;lie"/>
+  <l:gentext key="sidebar" text="Margin&#225;lie"/>
+  <l:gentext key="Step" text="Krok"/>
+  <l:gentext key="step" text="krok"/>
+  <l:gentext key="Table" text="Tabulka"/>
+  <l:gentext key="table" text="Tabulka"/>
+  <l:gentext key="TIP" text="Tip"/>
+  <l:gentext key="Tip" text="Tip"/>
+  <l:gentext key="tip" text="Tip"/>
+  <l:gentext key="WARNING" text="Varov&#225;n&#237;"/>
+  <l:gentext key="Warning" text="Varov&#225;n&#237;"/>
+  <l:gentext key="warning" text="Varov&#225;n&#237;"/>
+  <l:gentext key="and" text="a"/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="Edited" text="Vyd&#225;no"/>
+  <l:gentext key="edited" text="Vyd&#225;no"/>
+  <l:gentext key="Editedby" text="Sestavil"/>
+  <l:gentext key="editedby" text="Sestavil"/>
+  <l:gentext key="in" text="v"/>
+  <l:gentext key="lastlistcomma" text=""/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="neexistuj&#237;c&#237; prvek"/>
+  <l:gentext key="notes" text="Pozn&#225;mky"/>
+  <l:gentext key="Notes" text="Pozn&#225;mky"/>
+  <l:gentext key="Pgs" text="Str."/>
+  <l:gentext key="pgs" text="Str."/>
+  <l:gentext key="Revisedby" text="Revidoval: "/>
+  <l:gentext key="revisedby" text="Revidoval: "/>
+  <l:gentext key="TableNotes" text="Pozn&#225;mky"/>
+  <l:gentext key="tablenotes" text="Pozn&#225;mky"/>
+  <l:gentext key="TableofContents" text="Obsah"/>
+  <l:gentext key="tableofcontents" text="Obsah"/>
+  <l:gentext key="unexpectedelementname" text="Neo&#269;ek&#225;van&#233; jm&#233;no prvku"/>
+  <l:gentext key="unsupported" text="nepodporovan&#253;"/>
+  <l:gentext key="xrefto" text="xref k"/>
+  <l:gentext key="listofequations" text="Seznam rovnic"/>
+  <l:gentext key="ListofEquations" text="Seznam rovnic"/>
+  <l:gentext key="ListofExamples" text="Seznam p&#345;&#237;klad&#367;"/>
+  <l:gentext key="listofexamples" text="Seznam p&#345;&#237;klad&#367;"/>
+  <l:gentext key="ListofFigures" text="Seznam obr&#225;zk&#367;"/>
+  <l:gentext key="listoffigures" text="Seznam obr&#225;zk&#367;"/>
+  <l:gentext key="listoftables" text="Seznam tabulek"/>
+  <l:gentext key="ListofTables" text="Seznam tabulek"/>
+  <l:gentext key="ListofUnknown" text="Seznam nezn&#225;m&#233;ho"/>
+  <l:gentext key="listofunknown" text="Seznam nezn&#225;m&#233;ho"/>
+  <l:gentext key="nav-home" text="Dom&#367;"/>
+  <l:gentext key="nav-next" text="Dal&#353;&#237;"/>
+  <l:gentext key="nav-next-sibling" text="Rychle dop&#345;edu"/>
+  <l:gentext key="nav-prev" text="P&#345;edch&#225;zej&#237;c&#237;"/>
+  <l:gentext key="nav-prev-sibling" text="Rychle zp&#283;t"/>
+  <l:gentext key="nav-up" text="Nahoru"/>
+  <l:gentext key="sectioncalled" text="odd&#237;l nazvan&#253;"/>
+  <l:gentext key="Draft" text="N&#225;vrh"/>
+  <l:gentext key="above" text="nad"/>
+  <l:gentext key="below" text="pod"/>
+  <l:gentext key="index symbols" text="Symboly"/>
+  <l:gentext key="lowercase.alpha" text="a&#225;bc&#269;d&#271;e&#233;&#283;fghi&#237;jklmno&#243;pqr&#345;s&#353;t&#357;u&#250;&#367;vwxy&#253;z&#382;"/>
+  <l:gentext key="uppercase.alpha" text="A&#193;BC&#268;D&#270;E&#201;&#282;FGHI&#205;JKLMNO&#211;PQR&#344;S&#352;T&#356;U&#218;&#366;VWXY&#221;Z&#381;"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/cs.xml -->
+  <l:dingbat key="startquote" text="&#8222;"/>
+  <l:dingbat key="endquote" text="&#8220;"/>
+  <l:dingbat key="nestedstartquote" text="&#8218;"/>
+  <l:dingbat key="nestedendquote" text="&#8216;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="P&#345;&#237;loha %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Kapitola %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Rovnice %n. %t"/>
+    <l:template name="example" text="P&#345;&#237;klad %n. %t"/>
+    <l:template name="figure" text="Obr&#225;zek %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#268;&#225;st %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Postup %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Produkce %n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabulka %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="P&#345;&#237;loha %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="Kapitola %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8222;%t&#8220;"/>
+    <l:template name="refsection" text="&#8222;%t&#8220;"/>
+    <l:template name="refsect1" text="&#8222;%t&#8220;"/>
+    <l:template name="refsect2" text="&#8222;%t&#8220;"/>
+    <l:template name="refsect3" text="&#8222;%t&#8220;"/>
+    <l:template name="sect1" text="&#8222;%t&#8220;"/>
+    <l:template name="sect2" text="&#8222;%t&#8220;"/>
+    <l:template name="sect3" text="&#8222;%t&#8220;"/>
+    <l:template name="sect4" text="&#8222;%t&#8220;"/>
+    <l:template name="sect5" text="&#8222;%t&#8220;"/>
+    <l:template name="section" text="&#8222;%t&#8220;"/>
+    <l:template name="simplesect" text="&#8222;%t&#8220;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="%n"/>
+    <l:template name="appendix" text="%n"/>
+    <l:template name="bridgehead" text="%n"/>
+    <l:template name="chapter" text="%n"/>
+    <l:template name="equation" text="%n"/>
+    <l:template name="example" text="%n"/>
+    <l:template name="figure" text="%n"/>
+    <l:template name="part" text="%n"/>
+    <l:template name="procedure" text="%n"/>
+    <l:template name="productionset" text="%n"/>
+    <l:template name="qandadiv" text="%n"/>
+    <l:template name="qandaentry" text="%n"/>
+    <l:template name="question" text="%n"/>
+    <l:template name="sect1" text="%n"/>
+    <l:template name="sect2" text="%n"/>
+    <l:template name="sect3" text="%n"/>
+    <l:template name="sect4" text="%n"/>
+    <l:template name="sect5" text="%n"/>
+    <l:template name="section" text="%n"/>
+    <l:template name="table" text="%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="bridgehead" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="chapter" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="equation" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="example" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="figure" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="part" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="procedure" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="productionset" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="qandadiv" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="refsect1" text="&#8222;%t&#8220;"/>
+    <l:template name="refsect2" text="&#8222;%t&#8220;"/>
+    <l:template name="refsect3" text="&#8222;%t&#8220;"/>
+    <l:template name="refsection" text="&#8222;%t&#8220;"/>
+    <l:template name="sect1" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="sect2" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="sect3" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="sect4" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="sect5" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="section" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="simplesect" text="%n &#8211; &#8222;%t&#8220;"/>
+    <l:template name="table" text="%n &#8211; &#8222;%t&#8220;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" a "/>
+    <l:template name="seplast" text=" a "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Viz "/>
+    <l:template name="seealso" text="Viz t&#233;&#382; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Publikum: "/>
+    <l:template name="MsgLevel" text="&#218;rove&#328;: "/>
+    <l:template name="MsgOrig" text="P&#367;vod: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d.&#160;B Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="ledna"/>
+    <l:template name="February" text="&#250;nora"/>
+    <l:template name="March" text="b&#345;ezna"/>
+    <l:template name="April" text="dubna"/>
+    <l:template name="May" text="kv&#283;tna"/>
+    <l:template name="June" text="&#269;ervna"/>
+    <l:template name="July" text="&#269;ervence"/>
+    <l:template name="August" text="srpna"/>
+    <l:template name="September" text="z&#225;&#345;&#237;"/>
+    <l:template name="October" text="&#345;&#237;jna"/>
+    <l:template name="November" text="listopadu"/>
+    <l:template name="December" text="prosince"/>
+    <l:template name="Monday" text="pond&#283;l&#237;"/>
+    <l:template name="Tuesday" text="&#250;ter&#253;"/>
+    <l:template name="Wednesday" text="st&#345;eda"/>
+    <l:template name="Thursday" text="&#269;tvrtek"/>
+    <l:template name="Friday" text="p&#225;tek"/>
+    <l:template name="Saturday" text="sobota"/>
+    <l:template name="Sunday" text="ned&#283;le"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="led"/>
+    <l:template name="Feb" text="&#250;no"/>
+    <l:template name="Mar" text="b&#345;e"/>
+    <l:template name="Apr" text="dub"/>
+    <l:template name="May" text="kv&#283;"/>
+    <l:template name="Jun" text="&#269;er"/>
+    <l:template name="Jul" text="&#269;nc"/>
+    <l:template name="Aug" text="srp"/>
+    <l:template name="Sep" text="z&#225;&#345;"/>
+    <l:template name="Oct" text="&#345;ij"/>
+    <l:template name="Nov" text="lis"/>
+    <l:template name="Dec" text="pro"/>
+    <l:template name="Mon" text="po"/>
+    <l:template name="Tue" text="&#250;t"/>
+    <l:template name="Wed" text="st"/>
+    <l:template name="Thu" text="&#269;t"/>
+    <l:template name="Fri" text="p&#225;"/>
+    <l:template name="Sat" text="so"/>
+    <l:template name="Sun" text="ne"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0405 Czech"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/da.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/da.xml
new file mode 100644
index 00000000000..67077b991ae
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/da.xml
@@ -0,0 +1,492 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="da" english-language-name="Danish">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/da.xml -->
+  <l:gentext key="Abstract" text="Resum&#233;"/>
+  <l:gentext key="abstract" text="resum&#233;"/>
+  <l:gentext key="Answer" text="Svar"/>
+  <l:gentext key="answer" text="svar"/>
+  <l:gentext key="Appendix" text="Appendiks"/>
+  <l:gentext key="appendix" text="appendiks"/>
+  <l:gentext key="Article" text="Artikel"/>
+  <l:gentext key="article" text="artikel"/>
+  <l:gentext key="Bibliography" text="Litteraturliste"/>
+  <l:gentext key="bibliography" text="litteraturliste"/>
+  <l:gentext key="Book" text="Bog"/>
+  <l:gentext key="book" text="bog"/>
+  <l:gentext key="CAUTION" text="PAS P&#197;"/>
+  <l:gentext key="Caution" text="Pas p&#229;"/>
+  <l:gentext key="caution" text="pas p&#229;"/>
+  <l:gentext key="Chapter" text="Kapitel"/>
+  <l:gentext key="chapter" text="kapitel"/>
+  <l:gentext key="Colophon" text="Kolofon"/>
+  <l:gentext key="colophon" text="kolofon"/>
+  <l:gentext key="Copyright" text="Ophavsret"/>
+  <l:gentext key="copyright" text="ophavsret"/>
+  <l:gentext key="Dedication" text="Tilegnet"/>
+  <l:gentext key="dedication" text="tilegnet"/>
+  <l:gentext key="Edition" text="Udgave"/>
+  <l:gentext key="edition" text="udgave"/>
+  <l:gentext key="Equation" text="Ligning"/>
+  <l:gentext key="equation" text="ligning"/>
+  <l:gentext key="Example" text="Eksempel"/>
+  <l:gentext key="example" text="eksempel"/>
+  <l:gentext key="Figure" text="Figur"/>
+  <l:gentext key="figure" text="figur"/>
+  <l:gentext key="Glossary" text="Ordliste"/>
+  <l:gentext key="glossary" text="ordliste"/>
+  <l:gentext key="GlossSee" text="Se"/>
+  <l:gentext key="glosssee" text="se"/>
+  <l:gentext key="GlossSeeAlso" text="Se ogs&#229;"/>
+  <l:gentext key="glossseealso" text="se ogs&#229;"/>
+  <l:gentext key="IMPORTANT" text="VIGTIGT"/>
+  <l:gentext key="Important" text="Vigtigt"/>
+  <l:gentext key="important" text="vigtigt"/>
+  <l:gentext key="Index" text="Stikordsregister"/>
+  <l:gentext key="index" text="stikordsregister"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Retslig note"/>
+  <l:gentext key="legalnotice" text="retslig note"/>
+  <l:gentext key="MsgAud" text="M&#229;lgruppe"/>
+  <l:gentext key="msgaud" text="m&#229;lgruppe"/>
+  <l:gentext key="MsgLevel" text="Niveau"/>
+  <l:gentext key="msglevel" text="niveau"/>
+  <l:gentext key="MsgOrig" text="Grundlag"/>
+  <l:gentext key="msgorig" text="grundlag"/>
+  <l:gentext key="NOTE" text="BEM&#198;RK"/>
+  <l:gentext key="Note" text="Bem&#230;rk"/>
+  <l:gentext key="note" text="bem&#230;rk"/>
+  <l:gentext key="Part" text="Del"/>
+  <l:gentext key="part" text="del"/>
+  <l:gentext key="Preface" text="Forord"/>
+  <l:gentext key="preface" text="forord"/>
+  <l:gentext key="Procedure" text="Procedure"/>
+  <l:gentext key="procedure" text="procedure"/>
+  <l:gentext key="ProductionSet" text="Produktion"/>
+  <l:gentext key="Published" text="Udgivet"/>
+  <l:gentext key="published" text="udgivet"/>
+  <l:gentext key="Question" text="Sp&#248;rgsm&#229;l"/>
+  <l:gentext key="question" text="sp&#248;rgsm&#229;l"/>
+  <l:gentext key="RefEntry" text="Punkt"/>
+  <l:gentext key="refentry" text="punkt"/>
+  <l:gentext key="Reference" text="Henvisning"/>
+  <l:gentext key="reference" text="henvisning"/>
+  <l:gentext key="RefName" text="Navn"/>
+  <l:gentext key="refname" text="navn"/>
+  <l:gentext key="RefSection" text="Afsnit"/>
+  <l:gentext key="refsection" text="afsnit"/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="synopsis"/>
+  <l:gentext key="RevHistory" text="Revisionshistorie"/>
+  <l:gentext key="revhistory" text="revisionshistorie"/>
+  <l:gentext key="revision" text="revision"/>
+  <l:gentext key="Revision" text="Revision"/>
+  <l:gentext key="sect1" text="Afsnit"/>
+  <l:gentext key="sect2" text="Afsnit"/>
+  <l:gentext key="sect3" text="Afsnit"/>
+  <l:gentext key="sect4" text="Afsnit"/>
+  <l:gentext key="sect5" text="Afsnit"/>
+  <l:gentext key="section" text="afsnit"/>
+  <l:gentext key="Section" text="Afsnit"/>
+  <l:gentext key="See" text="Se"/>
+  <l:gentext key="see" text="se"/>
+  <l:gentext key="SeeAlso" text="Se ogs&#229;"/>
+  <l:gentext key="seealso" text="se ogs&#229;"/>
+  <l:gentext key="Seealso" text="Se ogs&#229;"/>
+  <l:gentext key="set" text="s&#230;t"/>
+  <l:gentext key="Set" text="S&#230;t"/>
+  <l:gentext key="setindex" text="s&#230;t indeks"/>
+  <l:gentext key="SetIndex" text="S&#230;t indeks"/>
+  <l:gentext key="Sidebar" text="Sidebj&#230;lke"/>
+  <l:gentext key="sidebar" text="sidebj&#230;lke"/>
+  <l:gentext key="step" text="trin"/>
+  <l:gentext key="Step" text="Trin"/>
+  <l:gentext key="Table" text="Tabel"/>
+  <l:gentext key="table" text="tabel"/>
+  <l:gentext key="tip" text="vink"/>
+  <l:gentext key="TIP" text="VINK"/>
+  <l:gentext key="Tip" text="Vink"/>
+  <l:gentext key="Warning" text="Advarsel"/>
+  <l:gentext key="warning" text="advarsel"/>
+  <l:gentext key="WARNING" text="ADVARSEL"/>
+  <l:gentext key="and" text="og"/>
+  <l:gentext key="by" text="af"/>
+  <l:gentext key="Edited" text="Redigeret"/>
+  <l:gentext key="edited" text="redigeret"/>
+  <l:gentext key="Editedby" text="Redigeret af"/>
+  <l:gentext key="editedby" text="redigeret af"/>
+  <l:gentext key="in" text="i"/>
+  <l:gentext key="lastlistcomma" text=" og "/>
+  <l:gentext key="listcomma" text=", "/>
+  <l:gentext key="nonexistantelement" text="ikke-eksisterende element"/>
+  <l:gentext key="notes" text="slutbem&#230;rkning:"/>
+  <l:gentext key="Notes" text="Slutbem&#230;rkning:"/>
+  <l:gentext key="Pgs" text="Siderne"/>
+  <l:gentext key="pgs" text="siderne"/>
+  <l:gentext key="Revisedby" text="Revideret af: "/>
+  <l:gentext key="revisedby" text="revideret af: "/>
+  <l:gentext key="TableNotes" text="Noter:"/>
+  <l:gentext key="tablenotes" text="noter:"/>
+  <l:gentext key="TableofContents" text="Indholdsfortegnelse"/>
+  <l:gentext key="tableofcontents" text="indholdsfortegnelse"/>
+  <l:gentext key="unexpectedelementname" text="uventet elementnavn"/>
+  <l:gentext key="unsupported" text="ikke underst&#248;ttet"/>
+  <l:gentext key="xrefto" text="krydshenvisning til"/>
+  <l:gentext key="listofequations" text="ligningsliste"/>
+  <l:gentext key="ListofEquations" text="Ligningsliste"/>
+  <l:gentext key="ListofExamples" text="Eksempelliste"/>
+  <l:gentext key="listofexamples" text="eksempelliste"/>
+  <l:gentext key="ListofFigures" text="Figurliste"/>
+  <l:gentext key="listoffigures" text="figurliste"/>
+  <l:gentext key="listoftables" text="tabelliste"/>
+  <l:gentext key="ListofTables" text="Tabelliste"/>
+  <l:gentext key="ListofUnknown" text="Liste over ukendte"/>
+  <l:gentext key="listofunknown" text="liste over ukendte"/>
+  <l:gentext key="nav-home" text="hjem"/>
+  <l:gentext key="nav-next" text="n&#230;ste"/>
+  <l:gentext key="nav-next-sibling" text="hurtigt fremad"/>
+  <l:gentext key="nav-prev" text="forrige"/>
+  <l:gentext key="nav-prev-sibling" text="hurtigt tilbage"/>
+  <l:gentext key="nav-up" text="op"/>
+  <l:gentext key="Draft" text="Kladde"/>
+  <l:gentext key="above" text="over"/>
+  <l:gentext key="below" text="under"/>
+  <l:gentext key="sectioncalled" text="afsnittet der hedder"/>
+  <l:gentext key="index symbols" text="symboler"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz&#230;&#248;&#229;"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ&#198;&#216;&#197;"/>
+  <l:gentext key="hyphenation-character" text="-"/>
+  <l:gentext key="hyphenation-push-character-count" text="2"/>
+  <l:gentext key="hyphenation-remain-character-count" text="2"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/da.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Appendiks %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Kapitel %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Ligning %n. %t"/>
+    <l:template name="example" text="Eksempel %n. %t"/>
+    <l:template name="figure" text="Figur %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Del %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedure %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Produktion %n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Sp&#248;rgsm&#229;l %n"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabel %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Appendiks %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="Kapitel %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Svar %n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Sp&#248;rgsm&#229;l %n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Sp&#248;rgsm&#229;l %n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="afsnittet der hedder &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Svar&#160;%n"/>
+    <l:template name="appendix" text="Appendiks&#160;%n"/>
+    <l:template name="bridgehead" text="Afsnit&#160;%n"/>
+    <l:template name="chapter" text="Kapitel&#160;%n"/>
+    <l:template name="equation" text="Ligning&#160;%n"/>
+    <l:template name="example" text="Eksempel&#160;%n"/>
+    <l:template name="figure" text="Figur&#160;%n"/>
+    <l:template name="part" text="Del&#160;%n"/>
+    <l:template name="procedure" text="Procedure&#160;%n"/>
+    <l:template name="productionset" text="Produktion&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Sp&#248;rgsm&#229;l&#160;%n"/>
+    <l:template name="question" text="Sp&#248;rgsm&#229;l&#160;%n"/>
+    <l:template name="sect1" text="Afsnit&#160;%n"/>
+    <l:template name="sect2" text="Afsnit&#160;%n"/>
+    <l:template name="sect3" text="Afsnit&#160;%n"/>
+    <l:template name="sect4" text="Afsnit&#160;%n"/>
+    <l:template name="sect5" text="Afsnit&#160;%n"/>
+    <l:template name="section" text="Afsnit&#160;%n"/>
+    <l:template name="table" text="Tabel&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Appendiks&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Afsnit&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Kapitel&#160;%n, %t"/>
+    <l:template name="equation" text="Ligning&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Eksempel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figur&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procedure&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Produktion&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="afsnittet der hedder &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="afsnittet der hedder &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="afsnittet der hedder &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="afsnittet der hedder &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Afsnit&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Afsnit&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Afsnit&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Afsnit&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Afsnit&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Afsnit&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="afsnittet der hedder &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabel&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=",  "/>
+    <l:template name="sep2" text=" og "/>
+    <l:template name="seplast" text=" og  og "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Se "/>
+    <l:template name="seealso" text="Se ogs&#229; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="M&#229;lgruppe: "/>
+    <l:template name="MsgLevel" text="Niveau: "/>
+    <l:template name="MsgOrig" text="Grundlag: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d/m/Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="Januar"/>
+    <l:template name="February" text="Februar"/>
+    <l:template name="March" text="Marts"/>
+    <l:template name="April" text="April"/>
+    <l:template name="May" text="Maj"/>
+    <l:template name="June" text="Juni"/>
+    <l:template name="July" text="July"/>
+    <l:template name="August" text="August"/>
+    <l:template name="September" text="September"/>
+    <l:template name="October" text="Oktober"/>
+    <l:template name="November" text="November"/>
+    <l:template name="December" text="December"/>
+    <l:template name="Monday" text="Mandag"/>
+    <l:template name="Tuesday" text="Tirsdag"/>
+    <l:template name="Wednesday" text="Onsdag"/>
+    <l:template name="Thursday" text="Torsdag"/>
+    <l:template name="Friday" text="Fredag"/>
+    <l:template name="Saturday" text="L&#248;rdag"/>
+    <l:template name="Sunday" text="S&#248;ndag"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="Jan"/>
+    <l:template name="Feb" text="Feb"/>
+    <l:template name="Mar" text="Mar"/>
+    <l:template name="Apr" text="Apr"/>
+    <l:template name="May" text="Maj"/>
+    <l:template name="Jun" text="Jun"/>
+    <l:template name="Jul" text="Jul"/>
+    <l:template name="Aug" text="Aug"/>
+    <l:template name="Sep" text="Sep"/>
+    <l:template name="Oct" text="Okt"/>
+    <l:template name="Nov" text="Nov"/>
+    <l:template name="Dec" text="Dec"/>
+    <l:template name="Mon" text="Man"/>
+    <l:template name="Tue" text="Tir"/>
+    <l:template name="Wed" text="ins"/>
+    <l:template name="Thu" text="Tor"/>
+    <l:template name="Fri" text="Fre"/>
+    <l:template name="Sat" text="L&#248;r"/>
+    <l:template name="Sun" text="S&#248;n"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0406 Danish"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/de.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/de.xml
new file mode 100644
index 00000000000..136dac0c7f8
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/de.xml
@@ -0,0 +1,538 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="de" english-language-name="German">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+  <l:gentext key="blockquote" text=""/>
+  <l:gentext key="formalpara" text="Paragraph"/>
+  <l:gentext key="glossseealso" text="Siehe auch"/>
+  <l:gentext key="keyword" text="Stichwort"/>
+  <l:gentext key="keywords" text="Stichw&#246;rter"/>
+  <l:gentext key="keywordset" text="Stichw&#246;rter"/>
+  <l:gentext key="the section called" text="der Abschnitt namens"/>
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/de.xml -->
+  <l:gentext key="Abstract" text="Zusammenfassung"/>
+  <l:gentext key="abstract" text="Zusammenfassung"/>
+  <l:gentext key="Answer" text="A:"/>
+  <l:gentext key="answer" text="A:"/>
+  <l:gentext key="Appendix" text="Anhang"/>
+  <l:gentext key="appendix" text="Anhang"/>
+  <l:gentext key="Article" text="Artikel"/>
+  <l:gentext key="article" text="Artikel"/>
+  <l:gentext key="Bibliography" text="Literaturverzeichnis"/>
+  <l:gentext key="bibliography" text="Literaturverzeichnis"/>
+  <l:gentext key="Book" text="Buch"/>
+  <l:gentext key="book" text="Buch"/>
+  <l:gentext key="Caution" text="Achtung"/>
+  <l:gentext key="caution" text="Achtung"/>
+  <l:gentext key="CAUTION" text="ACHTUNG"/>
+  <l:gentext key="Chapter" text="Kapitel"/>
+  <l:gentext key="chapter" text="Kapitel"/>
+  <l:gentext key="Colophon" text="Kolophon"/>
+  <l:gentext key="colophon" text="Kolophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Widmung"/>
+  <l:gentext key="dedication" text="Widmung"/>
+  <l:gentext key="Edition" text="Ausgabe"/>
+  <l:gentext key="edition" text="Ausgabe"/>
+  <l:gentext key="Equation" text="Gleichung"/>
+  <l:gentext key="equation" text="Gleichung"/>
+  <l:gentext key="Example" text="Beispiel"/>
+  <l:gentext key="example" text="Beispiel"/>
+  <l:gentext key="Figure" text="Abbildung"/>
+  <l:gentext key="figure" text="Abbildung"/>
+  <l:gentext key="Glossary" text="Glossar"/>
+  <l:gentext key="glossary" text="Glossar"/>
+  <l:gentext key="GlossSee" text="Siehe"/>
+  <l:gentext key="glosssee" text="Siehe"/>
+  <l:gentext key="GlossSeeAlso" text="Siehe auch"/>
+  <l:gentext key="IMPORTANT" text="WICHTIG"/>
+  <l:gentext key="Important" text="Wichtig"/>
+  <l:gentext key="important" text="Wichtig"/>
+  <l:gentext key="Index" text="Stichwortverzeichnis"/>
+  <l:gentext key="index" text="Stichwortverzeichnis"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Rechtlicher Hinweis"/>
+  <l:gentext key="legalnotice" text="Rechtlicher Hinweis"/>
+  <l:gentext key="MsgAud" text="Zielgruppe"/>
+  <l:gentext key="msgaud" text="Zielgruppe"/>
+  <l:gentext key="MsgLevel" text="Dringlichkeit"/>
+  <l:gentext key="msglevel" text="Dringlichkeit"/>
+  <l:gentext key="MsgOrig" text="Ursprung"/>
+  <l:gentext key="msgorig" text="Ursprung"/>
+  <l:gentext key="note" text="Anmerkung"/>
+  <l:gentext key="NOTE" text="ANMERKUNG"/>
+  <l:gentext key="Note" text="Anmerkung"/>
+  <l:gentext key="part" text="Teil"/>
+  <l:gentext key="Part" text="Teil"/>
+  <l:gentext key="Preface" text="Vorwort"/>
+  <l:gentext key="preface" text="Vorwort"/>
+  <l:gentext key="Procedure" text="Prozedur"/>
+  <l:gentext key="procedure" text="Prozedur"/>
+  <l:gentext key="ProductionSet" text="Produktion"/>
+  <l:gentext key="PubDate" text="Ver&#246;ffentlicht"/>
+  <l:gentext key="pubdate" text="Ver&#246;ffentlicht"/>
+  <l:gentext key="Published" text="Ver&#246;ffentlicht"/>
+  <l:gentext key="published" text="Ver&#246;ffentlicht"/>
+  <l:gentext key="Qandadiv" text="F &amp; A"/>
+  <l:gentext key="qandadiv" text="F &amp; A"/>
+  <l:gentext key="Question" text="F:"/>
+  <l:gentext key="question" text="F:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Verweis"/>
+  <l:gentext key="reference" text="Verweis"/>
+  <l:gentext key="refname" text="Name"/>
+  <l:gentext key="RefName" text="Name"/>
+  <l:gentext key="RefSection" text="Abschnitt"/>
+  <l:gentext key="refsection" text="Abschnitt"/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Versionsgeschichte"/>
+  <l:gentext key="revhistory" text="Versionsgeschichte"/>
+  <l:gentext key="Revision" text="Version"/>
+  <l:gentext key="revision" text="Version"/>
+  <l:gentext key="Section" text="Abschnitt"/>
+  <l:gentext key="section" text="Abschnitt"/>
+  <l:gentext key="sect1" text="Abschnitt"/>
+  <l:gentext key="sect2" text="Abschnitt"/>
+  <l:gentext key="sect3" text="Abschnitt"/>
+  <l:gentext key="sect4" text="Abschnitt"/>
+  <l:gentext key="sect5" text="Abschnitt"/>
+  <l:gentext key="see" text="Siehe"/>
+  <l:gentext key="See" text="Siehe"/>
+  <l:gentext key="SeeAlso" text="Siehe auch"/>
+  <l:gentext key="seealso" text="Siehe auch"/>
+  <l:gentext key="Seealso" text="Siehe auch"/>
+  <l:gentext key="Set" text="Satz"/>
+  <l:gentext key="set" text="Satz"/>
+  <l:gentext key="setindex" text="Stichwortverzeichnis"/>
+  <l:gentext key="SetIndex" text="Stichwortverzeichnis"/>
+  <l:gentext key="sidebar" text="randnotiz"/>
+  <l:gentext key="Sidebar" text="Randnotiz"/>
+  <l:gentext key="Step" text="Schritt"/>
+  <l:gentext key="step" text="Schritt"/>
+  <l:gentext key="table" text="Tabelle"/>
+  <l:gentext key="Table" text="Tabelle"/>
+  <l:gentext key="TIP" text="TIPP"/>
+  <l:gentext key="Tip" text="Tipp"/>
+  <l:gentext key="tip" text="Tipp"/>
+  <l:gentext key="Warning" text="Warnung"/>
+  <l:gentext key="warning" text="Warnung"/>
+  <l:gentext key="WARNING" text="WARNUNG"/>
+  <l:gentext key="and" text="und"/>
+  <l:gentext key="by" text="von"/>
+  <l:gentext key="Edited" text="Herausgegeben"/>
+  <l:gentext key="edited" text="Herausgegeben"/>
+  <l:gentext key="Editedby" text="Herausgegeben von"/>
+  <l:gentext key="editedby" text="Herausgegeben von"/>
+  <l:gentext key="in" text="in"/>
+  <l:gentext key="lastlistcomma" text=""/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="nicht existierendes Element"/>
+  <l:gentext key="notes" text="Fu&#223;noten"/>
+  <l:gentext key="Notes" text="Fu&#223;noten"/>
+  <l:gentext key="Pgs" text="Seiten"/>
+  <l:gentext key="pgs" text="Seiten"/>
+  <l:gentext key="Revisedby" text="Ge&#228;ndert durch: "/>
+  <l:gentext key="revisedby" text="Ge&#228;ndert durch: "/>
+  <l:gentext key="TableNotes" text="Bemerkungen"/>
+  <l:gentext key="tablenotes" text="Bemerkungen"/>
+  <l:gentext key="TableofContents" text="Inhaltsverzeichnis"/>
+  <l:gentext key="tableofcontents" text="Inhaltsverzeichnis"/>
+  <l:gentext key="the" text=""/>
+  <l:gentext key="unexpectedelementname" text="Unerwarteter Elementname"/>
+  <l:gentext key="unsupported" text="wird nicht unterst&#252;tzt"/>
+  <l:gentext key="xrefto" text="xref auf"/>
+  <l:gentext key="listofequations" text="Gleichungen"/>
+  <l:gentext key="ListofEquations" text="Gleichungen"/>
+  <l:gentext key="ListofExamples" text="Beispiele"/>
+  <l:gentext key="listofexamples" text="Beispiele"/>
+  <l:gentext key="ListofFigures" text="Abbildungsverzeichnis"/>
+  <l:gentext key="listoffigures" text="Abbildungsverzeichnis"/>
+  <l:gentext key="listoftables" text="Tabellenverzeichnis"/>
+  <l:gentext key="ListofTables" text="Tabellenverzeichnis"/>
+  <l:gentext key="ListofUnknown" text="???-Verzeichnis"/>
+  <l:gentext key="listofunknown" text="???-Verzeichnis"/>
+  <l:gentext key="nav-home" text="Zum Anfang"/>
+  <l:gentext key="nav-next" text="Weiter"/>
+  <l:gentext key="nav-next-sibling" text="Schnell weiter"/>
+  <l:gentext key="nav-prev" text="Zur&#252;ck"/>
+  <l:gentext key="nav-prev-sibling" text="Schnell zur&#252;ck"/>
+  <l:gentext key="nav-up" text="Nach oben"/>
+  <l:gentext key="nav-toc" text="InhV"/>
+  <l:gentext key="sectioncalled" text="der Abschnitt namens"/>
+  <l:gentext key="Draft" text="Entwurf"/>
+  <l:gentext key="above" text="oben"/>
+  <l:gentext key="below" text="unten"/>
+  <l:gentext key="index symbols" text="Symbole"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz&#228;&#246;&#252;&#223;"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ&#196;&#214;&#220;&#223;"/>
+  <l:gentext key="hyphenation-character" text="-"/>
+  <l:gentext key="hyphenation-push-character-count" text="2"/>
+  <l:gentext key="hyphenation-remain-character-count" text="3"/>
+  <l:dingbat key="startquote" text="\glqq{}"/>
+  <l:dingbat key="endquote" text="\grqq{}"/>
+  <l:dingbat key="nestedstartquote" text="\glq{}"/>
+  <l:dingbat key="nestedendquote" text="\grq{}"/>
+  <l:dingbat key="singlestartquote" text="\glq{}"/>
+  <l:dingbat key="singleendquote" text="\grq{}"/>
+  <l:dingbat key="urlstartquote" text="{\textless}"/>
+  <l:dingbat key="urlendquote" text="{\textgreater}"/>
+  <l:dingbat key="bullet" text="\textbullet{}"/>
+  <l:dingbat key="decimalpoint" text=","/>
+  <l:dingbat key="latexdecimal" text=","/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/de.xml -->
+<!-- The following contexts were merged from two source files. -->
+  <l:context name="naturalinlinelist">
+    <l:template name="start" text=""/>
+    <l:template name="middle" text=", "/>
+    <l:template name="lastoftwo" text=" und "/>
+    <l:template name="lastofmany" text=" und "/>
+    <l:template name="end" text=". "/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/de.xml -->
+  </l:context>
+  <l:context name="naturalblocklist">
+    <l:template name="start" text=""/>
+    <l:template name="middle" text=", "/>
+    <l:template name="lastoftwo" text=", "/>
+    <l:template name="lastofmany" text=", "/>
+    <l:template name="end" text=""/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/de.xml -->
+  </l:context>
+  <l:context name="xref">
+    <l:template element="page.citation" text=" auf Seite %p" lang="en"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/de.xml -->
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="F:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="F: %n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="page" text="(Seite %p)"/>
+    <l:template name="pageabbrev" text="(S. %p)"/>
+    <l:template name="Page" text="Seite %p"/>
+    <l:template name="bridgehead" text="&#8222;%t&#8220;"/>
+    <l:template name="refsection" text="&#8222;%t&#8220;"/>
+    <l:template name="refsect1" text="&#8222;%t&#8220;"/>
+    <l:template name="refsect2" text="&#8222;%t&#8220;"/>
+    <l:template name="refsect3" text="&#8222;%t&#8220;"/>
+    <l:template name="sect1" text="&#8222;%t&#8220;"/>
+    <l:template name="sect2" text="&#8222;%t&#8220;"/>
+    <l:template name="sect3" text="&#8222;%t&#8220;"/>
+    <l:template name="sect4" text="&#8222;%t&#8220;"/>
+    <l:template name="sect5" text="&#8222;%t&#8220;"/>
+    <l:template name="section" text="&#8222;%t&#8220;"/>
+    <l:template name="simplesect" text="&#8222;%t&#8220;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="appendix" text="Anhang&#160;%n"/>
+    <l:template name="chapter" text="Kapitel&#160;%n %t"/>
+    <l:template name="reference" text="Verweis&#160;%n"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/de.xml -->
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="bridgehead" text="Abschnitt&#160;%n"/>
+    <l:template name="equation" text="Gleichung&#160;%n"/>
+    <l:template name="example" text="Beispiel&#160;%n"/>
+    <l:template name="figure" text="Abbildung&#160;%n"/>
+    <l:template name="part" text="Teil&#160;%n"/>
+    <l:template name="procedure" text="Prozedur&#160;%n"/>
+    <l:template name="productionset" text="Produktion&#160;%n"/>
+    <l:template name="qandadiv" text="F &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="F:&#160;%n"/>
+    <l:template name="question" text="F:&#160;%n"/>
+    <l:template name="sect1" text="Abschnitt&#160;%n"/>
+    <l:template name="sect2" text="Abschnitt&#160;%n"/>
+    <l:template name="sect3" text="Abschnitt&#160;%n"/>
+    <l:template name="sect4" text="Abschnitt&#160;%n"/>
+    <l:template name="sect5" text="Abschnitt&#160;%n"/>
+    <l:template name="section" text="Abschnitt&#160;%n"/>
+    <l:template name="table" text="Tabelle&#160;%n"/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d.m.Y"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/de.xml -->
+  </l:context>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Anhang %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Kapitel %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Gleichung %n. %t"/>
+    <l:template name="example" text="Beispiel %n. %t"/>
+    <l:template name="figure" text="Abbildung %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Teil %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Prozedur %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Produktion&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="F: %n"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabelle %n. %t"/>
+    <l:template name="task" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Anhang %n. %t"/>
+    <l:template name="article/appendix" text="%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="Kapitel %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Anhang&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Abschnitt&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="chapter" text="Kapitel&#160;%n, %t"/>
+    <l:template name="equation" text="Gleichung&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="example" text="Beispiel&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="figure" text="Abbildung&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="part" text="Teil&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="procedure" text="Prozedur&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="productionset" text="Produktion&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="qandadiv" text="F &amp; A&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="refsect1" text="der Abschnitt namens &#8222;%t&#8220;"/>
+    <l:template name="refsect2" text="der Abschnitt namens &#8222;%t&#8220;"/>
+    <l:template name="refsect3" text="der Abschnitt namens &#8222;%t&#8220;"/>
+    <l:template name="refsection" text="der Abschnitt namens &#8222;%t&#8220;"/>
+    <l:template name="sect1" text="Abschnitt&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="sect2" text="Abschnitt&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="sect3" text="Abschnitt&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="sect4" text="Abschnitt&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="sect5" text="Abschnitt&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="section" text="Abschnitt&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="simplesect" text="der Abschnitt namens &#8222;%t&#8220;"/>
+    <l:template name="table" text="Tabelle&#160;%n, &#8222;%t&#8220;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" und "/>
+    <l:template name="seplast" text=" und "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Siehe "/>
+    <l:template name="seealso" text="Siehe auch "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Zielgruppe: "/>
+    <l:template name="MsgLevel" text="Dringlichkeit: "/>
+    <l:template name="MsgOrig" text="Ursprung: "/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="Januar"/>
+    <l:template name="February" text="Februar"/>
+    <l:template name="March" text="M&#228;rz"/>
+    <l:template name="April" text="April"/>
+    <l:template name="May" text="Mai"/>
+    <l:template name="June" text="Juni"/>
+    <l:template name="July" text="Juli"/>
+    <l:template name="August" text="August"/>
+    <l:template name="September" text="September"/>
+    <l:template name="October" text="Oktober"/>
+    <l:template name="November" text="November"/>
+    <l:template name="December" text="Dezember"/>
+    <l:template name="Monday" text="Montag"/>
+    <l:template name="Tuesday" text="Dienstag"/>
+    <l:template name="Wednesday" text="Mittwoch"/>
+    <l:template name="Thursday" text="Donnerstag"/>
+    <l:template name="Friday" text="Freitag"/>
+    <l:template name="Saturday" text="Samstag"/>
+    <l:template name="Sunday" text="Sonntag"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="Jan"/>
+    <l:template name="Feb" text="Feb"/>
+    <l:template name="Mar" text="Mar"/>
+    <l:template name="Apr" text="Apr"/>
+    <l:template name="May" text="Mai"/>
+    <l:template name="Jun" text="Jun"/>
+    <l:template name="Jul" text="Jul"/>
+    <l:template name="Aug" text="Aug"/>
+    <l:template name="Sep" text="Sep"/>
+    <l:template name="Oct" text="Okt"/>
+    <l:template name="Nov" text="Nov"/>
+    <l:template name="Dec" text="Dez"/>
+    <l:template name="Mon" text="Mo"/>
+    <l:template name="Tue" text="Di"/>
+    <l:template name="Wed" text="Mi"/>
+    <l:template name="Thu" text="Do"/>
+    <l:template name="Fri" text="Fr"/>
+    <l:template name="Sat" text="Sa"/>
+    <l:template name="Sun" text="So"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0407 German (GERMANY)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/el.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/el.xml
new file mode 100644
index 00000000000..26deb44a387
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/el.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="el" english-language-name="Greek">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/el.xml -->
+  <l:gentext key="Abstract" text="&#208;&#229;&#241;&#223;&#235;&#231;&#248;&#231;"/>
+  <l:gentext key="Answer" text="&#193;:"/>
+  <l:gentext key="Appendix" text="&#208;&#225;&#241;&#220;&#241;&#244;&#231;&#236;&#225;"/>
+  <l:gentext key="Article" text="&#182;&#241;&#232;&#241;&#239;"/>
+  <l:gentext key="Bibliography" text="&#194;&#233;&#226;&#235;&#233;&#239;&#227;&#241;&#225;&#246;&#223;&#225;"/>
+  <l:gentext key="Book" text="&#194;&#233;&#226;&#235;&#223;&#239;"/>
+  <l:gentext key="CAUTION" text="&#208;&#209;&#207;&#211;&#207;&#215;&#199;"/>
+  <l:gentext key="Caution" text="&#208;&#241;&#239;&#243;&#239;&#247;&#222;"/>
+  <l:gentext key="Chapter" text="&#202;&#229;&#246;&#220;&#235;&#225;&#233;&#239;"/>
+  <l:gentext key="Colophon" text="&#202;&#239;&#241;&#249;&#237;&#223;&#228;&#225;"/>
+  <l:gentext key="Copyright" text="&#208;&#237;&#229;&#245;&#236;&#225;&#244;&#233;&#234;&#220; &#196;&#233;&#234;&#225;&#233;&#254;&#236;&#225;&#244;&#225;"/>
+  <l:gentext key="Dedication" text="&#193;&#246;&#233;&#221;&#241;&#249;&#243;&#231;"/>
+  <l:gentext key="Edition" text="&#184;&#234;&#228;&#239;&#243;&#231;"/>
+  <l:gentext key="Equation" text="&#197;&#238;&#223;&#243;&#249;&#243;&#231;"/>
+  <l:gentext key="Example" text="&#208;&#225;&#241;&#220;&#228;&#229;&#233;&#227;&#236;&#225;"/>
+  <l:gentext key="Figure" text="&#211;&#247;&#222;&#236;&#225;"/>
+  <l:gentext key="GlossSee" text="&#196;&#229;&#223;&#244;&#229;"/>
+  <l:gentext key="GlossSeeAlso" text="&#196;&#229;&#223;&#244;&#229; &#197;&#240;&#223;&#243;&#231;&#242;"/>
+  <l:gentext key="Glossary" text="&#195;&#235;&#249;&#243;&#243;&#220;&#241;&#233;&#239;"/>
+  <l:gentext key="IMPORTANT" text="&#211;&#199;&#204;&#193;&#205;&#212;&#201;&#202;&#207;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="Important" text="&#211;&#231;&#236;&#225;&#237;&#244;&#233;&#234;&#252;"/>
+  <l:gentext key="Index" text="&#197;&#245;&#241;&#229;&#244;&#222;&#241;&#233;&#239;"/>
+  <l:gentext key="LegalNotice" text="&#205;&#239;&#236;&#233;&#234;&#222; &#211;&#231;&#236;&#229;&#223;&#249;&#243;&#231;"/>
+  <l:gentext key="MsgAud" text="&#193;&#234;&#241;&#239;&#225;&#244;&#222;&#241;&#233;&#239;"/>
+  <l:gentext key="MsgLevel" text="&#197;&#240;&#223;&#240;&#229;&#228;&#239;"/>
+  <l:gentext key="MsgOrig" text="&#208;&#231;&#227;&#222;"/>
+  <l:gentext key="NOTE" text="&#211;&#199;&#204;&#197;&#201;&#217;&#211;&#199;"/>
+  <l:gentext key="Note" text="&#211;&#231;&#236;&#229;&#223;&#249;&#243;&#231;"/>
+  <l:gentext key="Part" text="&#204;&#221;&#241;&#239;&#242;"/>
+  <l:gentext key="Preface" text="&#197;&#233;&#243;&#225;&#227;&#249;&#227;&#222;"/>
+  <l:gentext key="Procedure" text="&#196;&#233;&#225;&#228;&#233;&#234;&#225;&#243;&#223;&#225;"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="&#196;&#231;&#236;&#239;&#243;&#233;&#229;&#245;&#236;&#221;&#237;&#239;"/>
+  <l:gentext key="Question" text="&#197;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="RefName" text="&#188;&#237;&#239;&#236;&#225;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#211;&#253;&#237;&#239;&#248;&#231;"/>
+  <l:gentext key="Reference" text="&#193;&#237;&#225;&#246;&#239;&#241;&#220;"/>
+  <l:gentext key="RevHistory" text="&#201;&#243;&#244;&#239;&#241;&#233;&#234;&#252; &#193;&#237;&#225;&#232;&#229;&#249;&#241;&#222;&#243;&#229;&#249;&#237;"/>
+  <l:gentext key="Revision" text="&#193;&#237;&#225;&#232;&#229;&#254;&#241;&#231;&#243;&#231;"/>
+  <l:gentext key="Section" text="&#212;&#236;&#222;&#236;&#225;"/>
+  <l:gentext key="See" text="&#196;&#229;&#223;&#244;&#229;"/>
+  <l:gentext key="SeeAlso" text="&#196;&#229;&#223;&#244;&#229; &#197;&#240;&#223;&#243;&#231;&#242;"/>
+  <l:gentext key="Seealso" text="&#196;&#229;&#223;&#244;&#229; &#229;&#240;&#223;&#243;&#231;&#242;"/>
+  <l:gentext key="Set" text="&#211;&#253;&#237;&#239;&#235;&#239;"/>
+  <l:gentext key="SetIndex" text="&#197;&#245;&#241;&#229;&#244;&#222;&#241;&#233;&#239; &#211;&#245;&#237;&#252;&#235;&#249;&#237;"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="Step" text="&#214;&#220;&#243;&#231;"/>
+  <l:gentext key="TIP" text="&#213;&#208;&#207;&#196;&#197;&#201;&#206;&#199;"/>
+  <l:gentext key="Table" text="&#208;&#223;&#237;&#225;&#234;&#225;&#242;"/>
+  <l:gentext key="Tip" text="&#213;&#240;&#252;&#228;&#229;&#233;&#238;&#231;"/>
+  <l:gentext key="WARNING" text="&#208;&#209;&#207;&#197;&#201;&#196;&#207;&#208;&#207;&#201;&#199;&#211;&#199;"/>
+  <l:gentext key="Warning" text="&#208;&#241;&#239;&#229;&#233;&#228;&#239;&#240;&#239;&#223;&#231;&#243;&#231;"/>
+  <l:gentext key="abstract" text="&#208;&#229;&#241;&#223;&#235;&#231;&#248;&#231;"/>
+  <l:gentext key="answer" text="&#193;:"/>
+  <l:gentext key="appendix" text="&#240;&#225;&#241;&#220;&#241;&#244;&#231;&#236;&#225;"/>
+  <l:gentext key="article" text="&#182;&#241;&#232;&#241;&#239;"/>
+  <l:gentext key="bibliography" text="&#194;&#233;&#226;&#235;&#233;&#239;&#227;&#241;&#225;&#246;&#223;&#225;"/>
+  <l:gentext key="book" text="&#194;&#233;&#226;&#235;&#223;&#239;"/>
+  <l:gentext key="caution" text="&#208;&#241;&#239;&#243;&#239;&#247;&#222;"/>
+  <l:gentext key="chapter" text="&#234;&#229;&#246;&#220;&#235;&#225;&#233;&#239;"/>
+  <l:gentext key="colophon" text="&#202;&#239;&#241;&#249;&#237;&#223;&#228;&#225;"/>
+  <l:gentext key="copyright" text="&#208;&#237;&#229;&#245;&#236;&#225;&#244;&#233;&#234;&#220; &#196;&#233;&#234;&#225;&#233;&#254;&#236;&#225;&#244;&#225;"/>
+  <l:gentext key="dedication" text="&#193;&#246;&#233;&#221;&#241;&#249;&#243;&#231;"/>
+  <l:gentext key="edition" text="&#184;&#234;&#228;&#239;&#243;&#231;"/>
+  <l:gentext key="equation" text="&#197;&#238;&#223;&#243;&#249;&#243;&#231;"/>
+  <l:gentext key="example" text="&#208;&#225;&#241;&#220;&#228;&#229;&#233;&#227;&#236;&#225;"/>
+  <l:gentext key="figure" text="&#211;&#247;&#222;&#236;&#225;"/>
+  <l:gentext key="glossary" text="&#195;&#235;&#249;&#243;&#243;&#220;&#241;&#233;&#239;"/>
+  <l:gentext key="glosssee" text="&#196;&#229;&#223;&#244;&#229;"/>
+  <l:gentext key="glossseealso" text="&#196;&#229;&#223;&#244;&#229; &#197;&#240;&#223;&#243;&#231;&#242;"/>
+  <l:gentext key="important" text="&#211;&#231;&#236;&#225;&#237;&#244;&#233;&#234;&#252;"/>
+  <l:gentext key="index" text="&#197;&#245;&#241;&#229;&#244;&#222;&#241;&#233;&#239;"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="legalnotice" text="&#205;&#239;&#236;&#233;&#234;&#222; &#211;&#231;&#236;&#229;&#223;&#249;&#243;&#231;"/>
+  <l:gentext key="msgaud" text="&#193;&#234;&#241;&#239;&#225;&#244;&#222;&#241;&#233;&#239;"/>
+  <l:gentext key="msglevel" text="&#197;&#240;&#223;&#240;&#229;&#228;&#239;"/>
+  <l:gentext key="msgorig" text="&#208;&#231;&#227;&#222;"/>
+  <l:gentext key="note" text="&#211;&#231;&#236;&#229;&#223;&#249;&#243;&#231;"/>
+  <l:gentext key="part" text="&#204;&#221;&#241;&#239;&#242;"/>
+  <l:gentext key="preface" text="&#197;&#233;&#243;&#225;&#227;&#249;&#227;&#222;"/>
+  <l:gentext key="procedure" text="&#196;&#233;&#225;&#228;&#233;&#234;&#225;&#243;&#223;&#225;"/>
+  <l:gentext key="published" text="&#196;&#231;&#236;&#239;&#243;&#233;&#229;&#245;&#236;&#221;&#237;&#239;"/>
+  <l:gentext key="question" text="&#197;:"/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="reference" text="&#193;&#237;&#225;&#246;&#239;&#241;&#220;"/>
+  <l:gentext key="refname" text="&#188;&#237;&#239;&#236;&#225;"/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="refsynopsisdiv" text="&#211;&#253;&#237;&#239;&#248;&#231;"/>
+  <l:gentext key="revhistory" text="&#201;&#243;&#244;&#239;&#241;&#233;&#234;&#252; &#193;&#237;&#225;&#232;&#229;&#249;&#241;&#222;&#243;&#229;&#249;&#237;"/>
+  <l:gentext key="revision" text="&#193;&#237;&#225;&#232;&#229;&#254;&#241;&#231;&#243;&#231;"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="section" text="&#244;&#236;&#222;&#236;&#225;"/>
+  <l:gentext key="see" text="&#196;&#229;&#223;&#244;&#229;"/>
+  <l:gentext key="seealso" text="&#196;&#229;&#223;&#244;&#229; &#197;&#240;&#223;&#243;&#231;&#242;"/>
+  <l:gentext key="set" text="&#211;&#253;&#237;&#239;&#235;&#239;"/>
+  <l:gentext key="setindex" text="&#197;&#245;&#241;&#229;&#244;&#222;&#241;&#233;&#239; &#211;&#245;&#237;&#252;&#235;&#249;&#237;"/>
+  <l:gentext key="sidebar" text="&#229;&#240;&#229;&#238;&#231;&#227;&#231;&#236;&#225;&#244;&#233;&#234;&#252; &#240;&#235;&#229;&#245;&#241;&#233;&#234;&#252; &#225;&#241;&#232;&#241;&#223;&#228;&#233;&#239;"/>
+  <l:gentext key="step" text="&#246;&#220;&#243;&#231;"/>
+  <l:gentext key="table" text="&#208;&#223;&#237;&#225;&#234;&#225;&#242;"/>
+  <l:gentext key="tip" text="&#213;&#240;&#252;&#228;&#229;&#233;&#238;&#231;"/>
+  <l:gentext key="warning" text="&#208;&#241;&#239;&#229;&#233;&#228;&#239;&#240;&#239;&#223;&#231;&#243;&#231;"/>
+  <l:gentext key="and" text="&#234;&#225;&#233;"/>
+  <l:gentext key="by" text="&#225;&#240;&#252;"/>
+  <l:gentext key="Edited" text="&#197;&#240;&#233;&#236;&#221;&#235;&#229;&#233;&#225;"/>
+  <l:gentext key="edited" text="&#197;&#240;&#233;&#236;&#221;&#235;&#229;&#233;&#225;"/>
+  <l:gentext key="Editedby" text="&#197;&#240;&#233;&#236;&#221;&#235;&#229;&#233;&#225; &#225;&#240;&#252;"/>
+  <l:gentext key="editedby" text="&#197;&#240;&#233;&#236;&#221;&#235;&#229;&#233;&#225; &#225;&#240;&#252;"/>
+  <l:gentext key="in" text="&#243;&#229;"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="&#236;&#231;-&#245;&#240;&#225;&#241;&#234;&#244;&#252; &#243;&#244;&#239;&#233;&#247;&#229;&#223;&#239;"/>
+  <l:gentext key="notes" text="&#211;&#231;&#236;&#229;&#233;&#254;&#243;&#229;&#233;&#242;"/>
+  <l:gentext key="Notes" text="&#211;&#231;&#236;&#229;&#233;&#254;&#243;&#229;&#233;&#242;"/>
+  <l:gentext key="Pgs" text="&#211;&#235;&#228;&#242;."/>
+  <l:gentext key="pgs" text="&#211;&#235;&#228;&#242;."/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text="&#208;&#223;&#237;&#225;&#234;&#225;&#242; &#211;&#231;&#236;&#229;&#233;&#254;&#243;&#229;&#249;&#237;"/>
+  <l:gentext key="tablenotes" text="&#208;&#223;&#237;&#225;&#234;&#225;&#242; &#211;&#231;&#236;&#229;&#233;&#254;&#243;&#229;&#249;&#237;"/>
+  <l:gentext key="TableofContents" text="&#208;&#223;&#237;&#225;&#234;&#225;&#242; &#208;&#229;&#241;&#233;&#229;&#247;&#239;&#236;&#221;&#237;&#249;&#237;"/>
+  <l:gentext key="tableofcontents" text="&#208;&#223;&#237;&#225;&#234;&#225;&#242; &#208;&#229;&#241;&#233;&#229;&#247;&#239;&#236;&#221;&#237;&#249;&#237;"/>
+  <l:gentext key="unexpectedelementname" text="&#204;&#231; &#225;&#237;&#225;&#236;&#229;&#237;&#252;&#236;&#229;&#237;&#239; &#252;&#237;&#239;&#236;&#225; &#243;&#244;&#239;&#233;&#247;&#229;&#223;&#239;&#245;"/>
+  <l:gentext key="unsupported" text="&#236;&#231; &#245;&#240;&#239;&#243;&#244;&#231;&#241;&#233;&#230;&#252;&#236;&#229;&#237;&#239;"/>
+  <l:gentext key="xrefto" text="&#225;&#237;&#244;&#233;&#240;&#225;&#241;&#225;&#240;&#239;&#236;&#240;&#222; &#243;&#229;"/>
+  <l:gentext key="listofequations" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#197;&#238;&#233;&#243;&#254;&#243;&#229;&#249;&#237;"/>
+  <l:gentext key="ListofEquations" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#197;&#238;&#233;&#243;&#254;&#243;&#229;&#249;&#237;"/>
+  <l:gentext key="ListofExamples" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#208;&#225;&#241;&#225;&#228;&#229;&#233;&#227;&#236;&#220;&#244;&#249;&#237;"/>
+  <l:gentext key="listofexamples" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#208;&#225;&#241;&#225;&#228;&#229;&#233;&#227;&#236;&#220;&#244;&#249;&#237;"/>
+  <l:gentext key="ListofFigures" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#211;&#247;&#231;&#236;&#220;&#244;&#249;&#237;"/>
+  <l:gentext key="listoffigures" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#211;&#247;&#231;&#236;&#220;&#244;&#249;&#237;"/>
+  <l:gentext key="listoftables" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#208;&#233;&#237;&#220;&#234;&#249;&#237;"/>
+  <l:gentext key="ListofTables" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#208;&#233;&#237;&#220;&#234;&#249;&#237;"/>
+  <l:gentext key="ListofUnknown" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#193;&#227;&#237;&#254;&#243;&#244;&#249;&#237;"/>
+  <l:gentext key="listofunknown" text="&#202;&#225;&#244;&#220;&#235;&#239;&#227;&#239;&#242; &#193;&#227;&#237;&#254;&#243;&#244;&#249;&#237;"/>
+  <l:gentext key="nav-home" text="&#193;&#241;&#247;&#222;"/>
+  <l:gentext key="nav-next" text="&#197;&#240;&#252;&#236;&#229;&#237;&#239;"/>
+  <l:gentext key="nav-next-sibling" text="&#208;&#241;&#239;&#242; &#244;&#239; &#244;&#221;&#235;&#239;&#242;"/>
+  <l:gentext key="nav-prev" text="&#208;&#241;&#239;&#231;&#227;"/>
+  <l:gentext key="nav-prev-sibling" text="&#208;&#241;&#239;&#242; &#244;&#231;&#237; &#225;&#241;&#247;&#222;"/>
+  <l:gentext key="nav-up" text="&#208;&#220;&#237;&#249;"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/el.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#208;&#225;&#241;&#220;&#241;&#244;&#231;&#236;&#225; %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#202;&#229;&#246;&#220;&#235;&#225;&#233;&#239; %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#197;&#238;&#223;&#243;&#249;&#243;&#231; %n. %t"/>
+    <l:template name="example" text="&#208;&#225;&#241;&#220;&#228;&#229;&#233;&#227;&#236;&#225; %n. %t"/>
+    <l:template name="figure" text="&#211;&#247;&#222;&#236;&#225; %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#204;&#221;&#241;&#239;&#242; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#196;&#233;&#225;&#228;&#233;&#234;&#225;&#243;&#223;&#225;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#208;&#223;&#237;&#225;&#234;&#225;&#242; %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#208;&#225;&#241;&#220;&#241;&#244;&#231;&#236;&#225; %n. %t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="&#202;&#229;&#246;&#220;&#235;&#225;&#233;&#239; %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#193;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#197;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#197;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#193;:&#160;%n"/>
+    <l:template name="appendix" text="&#208;&#225;&#241;&#220;&#241;&#244;&#231;&#236;&#225;&#160;%n"/>
+    <l:template name="bridgehead" text="&#212;&#236;&#222;&#236;&#225;&#160;%n"/>
+    <l:template name="chapter" text="&#202;&#229;&#246;&#220;&#235;&#225;&#233;&#239;&#160;%n"/>
+    <l:template name="equation" text="&#197;&#238;&#223;&#243;&#249;&#243;&#231;&#160;%n"/>
+    <l:template name="example" text="&#208;&#225;&#241;&#220;&#228;&#229;&#233;&#227;&#236;&#225;&#160;%n"/>
+    <l:template name="figure" text="&#211;&#247;&#222;&#236;&#225;&#160;%n"/>
+    <l:template name="part" text="&#204;&#221;&#241;&#239;&#242;&#160;%n"/>
+    <l:template name="procedure" text="&#196;&#233;&#225;&#228;&#233;&#234;&#225;&#243;&#223;&#225;&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#197;:&#160;%n"/>
+    <l:template name="question" text="&#197;:&#160;%n"/>
+    <l:template name="sect1" text="&#212;&#236;&#222;&#236;&#225;&#160;%n"/>
+    <l:template name="sect2" text="&#212;&#236;&#222;&#236;&#225;&#160;%n"/>
+    <l:template name="sect3" text="&#212;&#236;&#222;&#236;&#225;&#160;%n"/>
+    <l:template name="sect4" text="&#212;&#236;&#222;&#236;&#225;&#160;%n"/>
+    <l:template name="sect5" text="&#212;&#236;&#222;&#236;&#225;&#160;%n"/>
+    <l:template name="section" text="&#212;&#236;&#222;&#236;&#225;&#160;%n"/>
+    <l:template name="table" text="&#208;&#223;&#237;&#225;&#234;&#225;&#242;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#208;&#225;&#241;&#220;&#241;&#244;&#231;&#236;&#225;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#212;&#236;&#222;&#236;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="&#202;&#229;&#246;&#220;&#235;&#225;&#233;&#239;&#160;%n, %t"/>
+    <l:template name="equation" text="&#197;&#238;&#223;&#243;&#249;&#243;&#231;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="&#208;&#225;&#241;&#220;&#228;&#229;&#233;&#227;&#236;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="&#211;&#247;&#222;&#236;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="&#204;&#221;&#241;&#239;&#242;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="&#196;&#233;&#225;&#228;&#233;&#234;&#225;&#243;&#223;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#212;&#236;&#222;&#236;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#212;&#236;&#222;&#236;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#212;&#236;&#222;&#236;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#212;&#236;&#222;&#236;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#212;&#236;&#222;&#236;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#212;&#236;&#222;&#236;&#225;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="&#208;&#223;&#237;&#225;&#234;&#225;&#242;&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#234;&#225;&#233; "/>
+    <l:template name="seplast" text=", &#234;&#225;&#233; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#196;&#229;&#223;&#244;&#229; "/>
+    <l:template name="seealso" text="&#196;&#229;&#223;&#244;&#229; &#197;&#240;&#223;&#243;&#231;&#242; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#193;&#234;&#241;&#239;&#225;&#244;&#222;&#241;&#233;&#239;: "/>
+    <l:template name="MsgLevel" text="&#197;&#240;&#223;&#240;&#229;&#228;&#239;: "/>
+    <l:template name="MsgOrig" text="&#208;&#231;&#227;&#222;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0408 Greek"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/en.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/en.xml
new file mode 100644
index 00000000000..1606883f22f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/en.xml
@@ -0,0 +1,551 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="en" english-language-name="English">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+  <l:gentext key="blockquote" text=""/>
+  <l:gentext key="formalpara" text="Paragraph"/>
+  <l:gentext key="nonexistantelement" text="non-existent element"/>
+  <l:gentext key="glossseealso" text="See also"/>
+  <l:gentext key="keyword" text="Keyword"/>
+  <l:gentext key="keywords" text="Keywords"/>
+  <l:gentext key="keywordset" text="Keywords"/>
+  <l:gentext key="the section called" text="the section called"/>
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/en.xml -->
+  <l:gentext key="Abstract" text="Abstract"/>
+  <l:gentext key="abstract" text="Abstract"/>
+  <l:gentext key="Answer" text="A:"/>
+  <l:gentext key="answer" text="A:"/>
+  <l:gentext key="Appendix" text="Appendix"/>
+  <l:gentext key="appendix" text="appendix"/>
+  <l:gentext key="Article" text="Article"/>
+  <l:gentext key="article" text="Article"/>
+  <l:gentext key="Bibliography" text="Bibliography"/>
+  <l:gentext key="bibliography" text="Bibliography"/>
+  <l:gentext key="Book" text="Book"/>
+  <l:gentext key="book" text="Book"/>
+  <l:gentext key="CAUTION" text="CAUTION"/>
+  <l:gentext key="Caution" text="Caution"/>
+  <l:gentext key="caution" text="Caution"/>
+  <l:gentext key="Chapter" text="Chapter"/>
+  <l:gentext key="chapter" text="chapter"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Dedication"/>
+  <l:gentext key="dedication" text="Dedication"/>
+  <l:gentext key="Edition" text="Edition"/>
+  <l:gentext key="edition" text="Edition"/>
+  <l:gentext key="Equation" text="Equation"/>
+  <l:gentext key="equation" text="Equation"/>
+  <l:gentext key="Example" text="Example"/>
+  <l:gentext key="example" text="Example"/>
+  <l:gentext key="Figure" text="Figure"/>
+  <l:gentext key="figure" text="Figure"/>
+  <l:gentext key="Glossary" text="Glossary"/>
+  <l:gentext key="glossary" text="Glossary"/>
+  <l:gentext key="GlossSee" text="See"/>
+  <l:gentext key="glosssee" text="See"/>
+  <l:gentext key="GlossSeeAlso" text="See Also"/>
+  <l:gentext key="IMPORTANT" text="IMPORTANT"/>
+  <l:gentext key="important" text="Important"/>
+  <l:gentext key="Important" text="Important"/>
+  <l:gentext key="Index" text="Index"/>
+  <l:gentext key="index" text="Index"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Legal Notice"/>
+  <l:gentext key="legalnotice" text="Legal Notice"/>
+  <l:gentext key="MsgAud" text="Audience"/>
+  <l:gentext key="msgaud" text="Audience"/>
+  <l:gentext key="MsgLevel" text="Level"/>
+  <l:gentext key="msglevel" text="Level"/>
+  <l:gentext key="MsgOrig" text="Origin"/>
+  <l:gentext key="msgorig" text="Origin"/>
+  <l:gentext key="NOTE" text="NOTE"/>
+  <l:gentext key="Note" text="Note"/>
+  <l:gentext key="note" text="Note"/>
+  <l:gentext key="Part" text="Part"/>
+  <l:gentext key="part" text="Part"/>
+  <l:gentext key="Preface" text="Preface"/>
+  <l:gentext key="preface" text="Preface"/>
+  <l:gentext key="Procedure" text="Procedure"/>
+  <l:gentext key="procedure" text="Procedure"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="PubDate" text="Publication Date"/>
+  <l:gentext key="pubdate" text="Publication date"/>
+  <l:gentext key="Published" text="Published"/>
+  <l:gentext key="published" text="Published"/>
+  <l:gentext key="Qandadiv" text="Q &amp; A"/>
+  <l:gentext key="qandadiv" text="Q &amp; A"/>
+  <l:gentext key="Question" text="Q:"/>
+  <l:gentext key="question" text="Q:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Reference"/>
+  <l:gentext key="reference" text="Reference"/>
+  <l:gentext key="RefName" text="Name"/>
+  <l:gentext key="refname" text="Name"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Revision History"/>
+  <l:gentext key="revhistory" text="Revision History"/>
+  <l:gentext key="revision" text="Revision"/>
+  <l:gentext key="Revision" text="Revision"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="section" text="Section"/>
+  <l:gentext key="Section" text="Section"/>
+  <l:gentext key="see" text="see"/>
+  <l:gentext key="See" text="See"/>
+  <l:gentext key="seealso" text="see also"/>
+  <l:gentext key="Seealso" text="See also"/>
+  <l:gentext key="SeeAlso" text="See Also"/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="setindex" text="Set Index"/>
+  <l:gentext key="SetIndex" text="Set Index"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="step" text="step"/>
+  <l:gentext key="Step" text="Step"/>
+  <l:gentext key="Table" text="Table"/>
+  <l:gentext key="table" text="Table"/>
+  <l:gentext key="tip" text="Tip"/>
+  <l:gentext key="TIP" text="TIP"/>
+  <l:gentext key="Tip" text="Tip"/>
+  <l:gentext key="Warning" text="Warning"/>
+  <l:gentext key="warning" text="Warning"/>
+  <l:gentext key="WARNING" text="WARNING"/>
+  <l:gentext key="and" text="and"/>
+  <l:gentext key="by" text="by"/>
+  <l:gentext key="called" text="called"/>
+  <l:gentext key="Edited" text="Edited"/>
+  <l:gentext key="edited" text="Edited"/>
+  <l:gentext key="Editedby" text="Edited by"/>
+  <l:gentext key="editedby" text="Edited by"/>
+  <l:gentext key="in" text="in"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="notes" text="Notes"/>
+  <l:gentext key="Notes" text="Notes"/>
+  <l:gentext key="Pgs" text="Pgs."/>
+  <l:gentext key="pgs" text="Pgs."/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text="Notes"/>
+  <l:gentext key="tablenotes" text="Notes"/>
+  <l:gentext key="TableofContents" text="Table of Contents"/>
+  <l:gentext key="tableofcontents" text="Table of Contents"/>
+  <l:gentext key="the" text=""/>
+  <l:gentext key="unexpectedelementname" text="Unexpected element name"/>
+  <l:gentext key="unsupported" text="unsupported"/>
+  <l:gentext key="xrefto" text="xref to"/>
+  <l:gentext key="listofequations" text="List of Equations"/>
+  <l:gentext key="ListofEquations" text="List of Equations"/>
+  <l:gentext key="ListofExamples" text="List of Examples"/>
+  <l:gentext key="listofexamples" text="List of Examples"/>
+  <l:gentext key="ListofFigures" text="List of Figures"/>
+  <l:gentext key="listoffigures" text="List of Figures"/>
+  <l:gentext key="ListofProcedures" text="List of Procedures"/>
+  <l:gentext key="listofprocedures" text="List of Procedures"/>
+  <l:gentext key="listoftables" text="List of Tables"/>
+  <l:gentext key="ListofTables" text="List of Tables"/>
+  <l:gentext key="ListofUnknown" text="List of Unknown"/>
+  <l:gentext key="listofunknown" text="List of Unknown"/>
+  <l:gentext key="nav-home" text="Home"/>
+  <l:gentext key="nav-next" text="Next"/>
+  <l:gentext key="nav-next-sibling" text="Fast Forward"/>
+  <l:gentext key="nav-prev" text="Prev"/>
+  <l:gentext key="nav-prev-sibling" text="Fast Backward"/>
+  <l:gentext key="nav-up" text="Up"/>
+  <l:gentext key="nav-toc" text="ToC"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+  <l:gentext key="hyphenation-character" text="-"/>
+  <l:gentext key="hyphenation-push-character-count" text="2"/>
+  <l:gentext key="hyphenation-remain-character-count" text="2"/>
+  <l:dingbat key="startquote" text="{``}"/>
+  <l:dingbat key="endquote" text="{''}"/>
+  <l:dingbat key="nestedstartquote" text="{`}"/>
+  <l:dingbat key="nestedendquote" text="{'}"/>
+  <l:dingbat key="singlestartquote" text="{`}"/>
+  <l:dingbat key="singleendquote" text="{'}"/>
+  <l:dingbat key="urlstartquote" text="{\textless}"/>
+  <l:dingbat key="urlendquote" text="{\textgreater}"/>
+  <l:dingbat key="bullet" text="\textbullet{}"/>
+  <l:dingbat key="decimalpoint" text="."/>
+  <l:dingbat key="latexdecimal" text="."/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/en.xml -->
+<!-- The following contexts were merged from two source files. -->
+  <l:context name="table">
+    <l:template name="thead.continued" text=""/>
+    <l:template name="tfoot.continued" text=" \textit{(P.T.O.)}"/>
+    <l:template name="thead.continuation" text="\textit{(continued)}"/>
+    <l:template name="tfoot.continuation" text=""/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/en.xml -->
+  </l:context>
+  <l:context name="naturalinlinelist">
+    <l:template name="start" text=""/>
+    <l:template name="middle" text=", "/>
+    <l:template name="lastoftwo" text=" and "/>
+    <l:template name="lastofmany" text=", and "/>
+    <l:template name="end" text=". "/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/en.xml -->
+  </l:context>
+  <l:context name="naturalblocklist">
+    <l:template name="start" text=""/>
+    <l:template name="middle" text=", "/>
+    <l:template name="lastoftwo" text=", "/>
+    <l:template name="lastofmany" text=", "/>
+    <l:template name="end" text=""/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/en.xml -->
+  </l:context>
+  <l:context name="xref">
+    <l:template name="page.citation" text=" on page %p"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/en.xml -->
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page" text="(page %p)"/>
+    <l:template name="pageabbrev" text="(p. %p)"/>
+    <l:template name="Page" text="Page %p"/>
+    <l:template name="bridgehead" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="section" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="appendix" text="Appendix&#160;%n"/>
+    <l:template name="chapter" text="Chapter&#160;%n, %t"/>
+    <l:template name="reference" text="Reference&#160;%n"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/en.xml -->
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="bridgehead" text="Section&#160;%n"/>
+    <l:template name="equation" text="Equation&#160;%n"/>
+    <l:template name="example" text="Example&#160;%n"/>
+    <l:template name="figure" text="Figure&#160;%n"/>
+    <l:template name="part" text="Part&#160;%n"/>
+    <l:template name="procedure" text="Procedure&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="sect1" text="Section&#160;%n"/>
+    <l:template name="sect2" text="Section&#160;%n"/>
+    <l:template name="sect3" text="Section&#160;%n"/>
+    <l:template name="sect4" text="Section&#160;%n"/>
+    <l:template name="sect5" text="Section&#160;%n"/>
+    <l:template name="section" text="Section&#160;%n"/>
+    <l:template name="table" text="Table&#160;%n"/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="Y-m-d"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/en.xml -->
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0809 English (UNITED KINGDOM)"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/en.xml -->
+  </l:context>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Appendix&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliolist" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Chapter&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Equation&#160;%n.&#160;%t"/>
+    <l:template name="example" text="Example&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="Figure&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glosslist" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Part&#160;%n.&#160;%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedure&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Table&#160;%n.&#160;%t"/>
+    <l:template name="task" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Appendix&#160;%n.&#160;%t"/>
+    <l:template name="article/appendix" text="%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="Chapter&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Appendix&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Section&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Chapter&#160;%n, %t"/>
+    <l:template name="equation" text="Equation&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Example&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figure&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Part&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procedure&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Section&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Section&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Section&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Section&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Section&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Section&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Table&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" and "/>
+    <l:template name="seplast" text=", and "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="See "/>
+    <l:template name="seealso" text="See Also "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Audience: "/>
+    <l:template name="MsgLevel" text="Level: "/>
+    <l:template name="MsgOrig" text="Origin: "/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="January"/>
+    <l:template name="February" text="February"/>
+    <l:template name="March" text="March"/>
+    <l:template name="April" text="April"/>
+    <l:template name="May" text="May"/>
+    <l:template name="June" text="June"/>
+    <l:template name="July" text="July"/>
+    <l:template name="August" text="August"/>
+    <l:template name="September" text="September"/>
+    <l:template name="October" text="October"/>
+    <l:template name="November" text="November"/>
+    <l:template name="December" text="December"/>
+    <l:template name="Monday" text="Monday"/>
+    <l:template name="Tuesday" text="Tuesday"/>
+    <l:template name="Wednesday" text="Wednesday"/>
+    <l:template name="Thursday" text="Thursday"/>
+    <l:template name="Friday" text="Friday"/>
+    <l:template name="Saturday" text="Saturday"/>
+    <l:template name="Sunday" text="Sunday"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="Jan"/>
+    <l:template name="Feb" text="Feb"/>
+    <l:template name="Mar" text="Mar"/>
+    <l:template name="Apr" text="Apr"/>
+    <l:template name="May" text="May"/>
+    <l:template name="Jun" text="Jun"/>
+    <l:template name="Jul" text="Jul"/>
+    <l:template name="Aug" text="Aug"/>
+    <l:template name="Sep" text="Sep"/>
+    <l:template name="Oct" text="Oct"/>
+    <l:template name="Nov" text="Nov"/>
+    <l:template name="Dec" text="Dec"/>
+    <l:template name="Mon" text="Mon"/>
+    <l:template name="Tue" text="Tue"/>
+    <l:template name="Wed" text="Wed"/>
+    <l:template name="Thu" text="Thu"/>
+    <l:template name="Fri" text="Fri"/>
+    <l:template name="Sat" text="Sat"/>
+    <l:template name="Sun" text="Sun"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/es.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/es.xml
new file mode 100644
index 00000000000..59abd1caa5a
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/es.xml
@@ -0,0 +1,482 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="es" english-language-name="Spanish">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+  <l:gentext key="blockquote" text=""/>
+  <l:gentext key="formalpara" text="p&#225;rrafo"/>
+  <l:gentext key="nonexistantelement" text="elemento inexistente"/>
+  <l:gentext key="glossseealso" text="Ver tambi&#233;n"/>
+  <l:gentext key="keyword" text="palabra clave"/>
+  <l:gentext key="keywords" text="Palabras Clave"/>
+  <l:gentext key="keywordset" text="Palabras Clave"/>
+  <l:gentext key="the section called" text="the secci&#243; titulada"/>
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/es.xml -->
+  <l:gentext key="Abstract" text="Resumen"/>
+  <l:gentext key="abstract" text="resumen"/>
+  <l:gentext key="Answer" text="R:"/>
+  <l:gentext key="answer" text="r:"/>
+  <l:gentext key="Appendix" text="Ap&#233;ndice"/>
+  <l:gentext key="appendix" text="ap&#233;ndice"/>
+  <l:gentext key="Article" text="Art&#237;culo"/>
+  <l:gentext key="article" text="art&#237;culo"/>
+  <l:gentext key="Bibliography" text="Bibliograf&#237;a"/>
+  <l:gentext key="bibliography" text="bibliograf&#237;a"/>
+  <l:gentext key="Book" text="Libro"/>
+  <l:gentext key="book" text="libro"/>
+  <l:gentext key="CAUTION" text="ATENCI&#211;N"/>
+  <l:gentext key="Caution" text="Atenci&#243;n"/>
+  <l:gentext key="caution" text="atenci&#243;n"/>
+  <l:gentext key="Chapter" text="Cap&#237;tulo"/>
+  <l:gentext key="chapter" text="cap&#237;tulo"/>
+  <l:gentext key="Colophon" text="Colof&#243;n"/>
+  <l:gentext key="colophon" text="colof&#243;n"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="copyright"/>
+  <l:gentext key="Dedication" text="Dedicatoria"/>
+  <l:gentext key="dedication" text="dedicatoria"/>
+  <l:gentext key="Edition" text="Edici&#243;n"/>
+  <l:gentext key="edition" text="edici&#243;n"/>
+  <l:gentext key="Equation" text="Ecuaci&#243;n"/>
+  <l:gentext key="equation" text="ecuaci&#243;n"/>
+  <l:gentext key="Example" text="Ejemplo"/>
+  <l:gentext key="example" text="ejemplo"/>
+  <l:gentext key="Figure" text="Figura"/>
+  <l:gentext key="figure" text="figura"/>
+  <l:gentext key="Glossary" text="Glosario"/>
+  <l:gentext key="glossary" text="glosario"/>
+  <l:gentext key="GlossSee" text="Ver"/>
+  <l:gentext key="glosssee" text="ver"/>
+  <l:gentext key="GlossSeeAlso" text="Ver tambi&#233;n"/>
+  <l:gentext key="IMPORTANT" text="IMPORTANTE"/>
+  <l:gentext key="Important" text="Importante"/>
+  <l:gentext key="important" text="importante"/>
+  <l:gentext key="Index" text="&#205;ndice"/>
+  <l:gentext key="index" text="&#237;ndice"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="isbn"/>
+  <l:gentext key="LegalNotice" text="Aviso Legal"/>
+  <l:gentext key="legalnotice" text="aviso legal"/>
+  <l:gentext key="MsgAud" text="Audiencia"/>
+  <l:gentext key="msgaud" text="audiencia"/>
+  <l:gentext key="MsgLevel" text="Nivel"/>
+  <l:gentext key="msglevel" text="nivel"/>
+  <l:gentext key="MsgOrig" text="Origen"/>
+  <l:gentext key="msgorig" text="origen"/>
+  <l:gentext key="NOTE" text="NOTA"/>
+  <l:gentext key="Note" text="Nota"/>
+  <l:gentext key="note" text="nota"/>
+  <l:gentext key="Part" text="Parte"/>
+  <l:gentext key="part" text="parte"/>
+  <l:gentext key="Preface" text="Prefacio"/>
+  <l:gentext key="preface" text="prefacio"/>
+  <l:gentext key="Procedure" text="Procedimiento"/>
+  <l:gentext key="procedure" text="procedimiento"/>
+  <l:gentext key="ProductionSet" text="Producci&#243;n"/>
+  <l:gentext key="PubDate" text="Fecha de publicaci&#243;n"/>
+  <l:gentext key="pubdate" text="fecha de publicaci&#243;n"/>
+  <l:gentext key="Published" text="Publicado"/>
+  <l:gentext key="published" text="publicado"/>
+  <l:gentext key="Question" text="P:"/>
+  <l:gentext key="question" text="p:"/>
+  <l:gentext key="RefEntry" text="Entrada de referencia"/>
+  <l:gentext key="refentry" text="entrada de referencia"/>
+  <l:gentext key="Reference" text="Referencia"/>
+  <l:gentext key="reference" text="referencia"/>
+  <l:gentext key="RefName" text="Nombre de referencia"/>
+  <l:gentext key="refname" text="nombre de referencia"/>
+  <l:gentext key="RefSection" text="Secci&#243;n de referencia"/>
+  <l:gentext key="refsection" text="secci&#243;n de referencia"/>
+  <l:gentext key="RefSynopsisDiv" text="Sinopsis"/>
+  <l:gentext key="refsynopsisdiv" text="sinopsis"/>
+  <l:gentext key="RevHistory" text="Historial de revisiones"/>
+  <l:gentext key="revhistory" text="Historial de revisiones"/>
+  <l:gentext key="Revision" text="Revisi&#243;n"/>
+  <l:gentext key="revision" text="revisi&#243;n"/>
+  <l:gentext key="sect1" text="Secci&#243;n"/>
+  <l:gentext key="sect2" text="Secci&#243;n"/>
+  <l:gentext key="sect3" text="Secci&#243;n"/>
+  <l:gentext key="sect4" text="Secci&#243;n"/>
+  <l:gentext key="sect5" text="Secci&#243;n"/>
+  <l:gentext key="Section" text="Secci&#243;n"/>
+  <l:gentext key="section" text="secci&#243;n"/>
+  <l:gentext key="See" text="Ver"/>
+  <l:gentext key="see" text="ver"/>
+  <l:gentext key="SeeAlso" text="Ver Tambi&#233;n"/>
+  <l:gentext key="Seealso" text="Ver tambi&#233;n"/>
+  <l:gentext key="seealso" text="ver tambi&#233;n"/>
+  <l:gentext key="Set" text="Conjunto"/>
+  <l:gentext key="set" text="conjunto"/>
+  <l:gentext key="SetIndex" text="&#205;ndice del Conjunto"/>
+  <l:gentext key="setindex" text="&#237;ndice del conjunto"/>
+  <l:gentext key="Sidebar" text="Barra lateral"/>
+  <l:gentext key="sidebar" text="barra lateral"/>
+  <l:gentext key="Step" text="Paso"/>
+  <l:gentext key="step" text="paso"/>
+  <l:gentext key="Table" text="Tabla"/>
+  <l:gentext key="table" text="tabla"/>
+  <l:gentext key="TIP" text="SUGERENCIA"/>
+  <l:gentext key="Tip" text="Sugerencia"/>
+  <l:gentext key="tip" text="sugerencia"/>
+  <l:gentext key="WARNING" text="AVISO"/>
+  <l:gentext key="Warning" text="Aviso"/>
+  <l:gentext key="warning" text="aviso"/>
+  <l:gentext key="and" text="y"/>
+  <l:gentext key="by" text="por"/>
+  <l:gentext key="Edited" text="Editado"/>
+  <l:gentext key="edited" text="editado"/>
+  <l:gentext key="Editedby" text="Editado por"/>
+  <l:gentext key="editedby" text="editado por"/>
+  <l:gentext key="in" text="en"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="notes" text="notas"/>
+  <l:gentext key="Notes" text="Notas"/>
+  <l:gentext key="Pgs" text="Pags."/>
+  <l:gentext key="pgs" text="pags."/>
+  <l:gentext key="Revisedby" text="Revisado por: "/>
+  <l:gentext key="revisedby" text="revisado por: "/>
+  <l:gentext key="TableNotes" text="Notas de Tabla"/>
+  <l:gentext key="tablenotes" text="notas de tabla"/>
+  <l:gentext key="TableofContents" text="Tabla de contenidos"/>
+  <l:gentext key="tableofcontents" text="tabla de contenidos"/>
+  <l:gentext key="unexpectedelementname" text="nombre de elemento inesperado"/>
+  <l:gentext key="unsupported" text="no soportado"/>
+  <l:gentext key="xrefto" text="referencia a"/>
+  <l:gentext key="listofequations" text="lista de ecuaciones"/>
+  <l:gentext key="ListofEquations" text="Lista de ecuaciones"/>
+  <l:gentext key="ListofExamples" text="Lista de ejemplos"/>
+  <l:gentext key="listofexamples" text="lista de ejemplos"/>
+  <l:gentext key="ListofFigures" text="Lista de figuras"/>
+  <l:gentext key="listoffigures" text="lista de figuras"/>
+  <l:gentext key="listoftables" text="lista de tablas"/>
+  <l:gentext key="ListofTables" text="Lista de tablas"/>
+  <l:gentext key="ListofUnknown" text="Lista de desconocido"/>
+  <l:gentext key="listofunknown" text="lista de desconocido"/>
+  <l:gentext key="nav-home" text="Inicio"/>
+  <l:gentext key="nav-next" text="Siguiente"/>
+  <l:gentext key="nav-next-sibling" text="Avanzar"/>
+  <l:gentext key="nav-prev" text="Anterior"/>
+  <l:gentext key="nav-prev-sibling" text="Retroceder"/>
+  <l:gentext key="nav-up" text="Subir"/>
+  <l:gentext key="index symbols" text="S&#237;mbolos"/>
+  <l:gentext key="Draft" text="Borrador"/>
+  <l:gentext key="above" text="arriba"/>
+  <l:gentext key="below" text="abajo"/>
+  <l:gentext key="sectioncalled" text="secci&#243;n llamada"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz&#225;&#233;&#237;&#243;&#250;&#241;"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ&#193;&#201;&#205;&#211;&#218;&#209;"/>
+  <l:dingbat key="startquote" text="{``}"/>
+  <l:dingbat key="endquote" text="{''}"/>
+  <l:dingbat key="nestedstartquote" text="{`}"/>
+  <l:dingbat key="nestedendquote" text="{'}"/>
+  <l:dingbat key="singlestartquote" text="{`}"/>
+  <l:dingbat key="singleendquote" text="{'}"/>
+  <l:dingbat key="urlstartquote" text="{\textless}"/>
+  <l:dingbat key="urlendquote" text="{\textgreater}"/>
+  <l:dingbat key="bullet" text="\textbullet{}"/>
+  <l:dingbat key="decimalpoint" text="."/>
+  <l:dingbat key="latexdecimal" text="."/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/es.xml -->
+<!-- The following contexts were merged from two source files. -->
+  <l:context name="naturalinlinelist">
+    <l:template name="start" text=""/>
+    <l:template name="middle" text=", "/>
+    <l:template name="lastoftwo" text=" y "/>
+    <l:template name="lastofmany" text=", y "/>
+    <l:template name="end" text=". "/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/es.xml -->
+  </l:context>
+  <l:context name="naturalblocklist">
+    <l:template name="start" text=""/>
+    <l:template name="middle" text=", "/>
+    <l:template name="lastoftwo" text=", "/>
+    <l:template name="lastofmany" text=", "/>
+    <l:template name="end" text=""/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/es.xml -->
+  </l:context>
+  <l:context name="xref">
+    <l:template name="page.citation" text=" en la p&#225;gina %p"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/es.xml -->
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="R:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="P:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="P:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="appendix" text="Ap&#233;ndice&#160;%n"/>
+    <l:template name="chapter" text="Cap&#237;tulo&#160;%n, %t"/>
+    <l:template name="reference" text="Referencia&#160;%n"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/es.xml -->
+    <l:template name="answer" text="R:&#160;%n"/>
+    <l:template name="bridgehead" text="Secci&#243;n&#160;%n"/>
+    <l:template name="equation" text="Ecuaci&#243;n&#160;%n"/>
+    <l:template name="example" text="Ejemplo&#160;%n"/>
+    <l:template name="figure" text="Figura&#160;%n"/>
+    <l:template name="part" text="Parte&#160;%n"/>
+    <l:template name="procedure" text="Procedimiento&#160;%n"/>
+    <l:template name="productionset" text="Producci&#243;n&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="P:&#160;%n"/>
+    <l:template name="question" text="P:&#160;%n"/>
+    <l:template name="sect1" text="Secci&#243;n&#160;%n"/>
+    <l:template name="sect2" text="Secci&#243;n&#160;%n"/>
+    <l:template name="sect3" text="Secci&#243;n&#160;%n"/>
+    <l:template name="sect4" text="Secci&#243;n&#160;%n"/>
+    <l:template name="sect5" text="Secci&#243;n&#160;%n"/>
+    <l:template name="section" text="Secci&#243;n&#160;%n"/>
+    <l:template name="table" text="Tabla&#160;%n"/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d-m-Y"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/es.xml -->
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0C0A Spanish (SPAIN)"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/es.xml -->
+  </l:context>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Ap&#233;ndice %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Cap&#237;tulo %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Ecuaci&#243;n %n. %t"/>
+    <l:template name="example" text="Ejemplo %n. %t"/>
+    <l:template name="figure" text="Figura %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Parte %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedimiento %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Producci&#243;n %n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabla %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Ap&#233;ndice %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="Cap&#237;tulo %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Ap&#233;ndice&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Secci&#243;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Cap&#237;tulo&#160;%n, %t"/>
+    <l:template name="equation" text="Ecuaci&#243;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Ejemplo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figura&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Parte&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procedimiento&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Producci&#243;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="secci&#243;n llamada &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="secci&#243;n llamada &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="secci&#243;n llamada &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="secci&#243;n llamada &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Secci&#243;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Secci&#243;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Secci&#243;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Secci&#243;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Secci&#243;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Secci&#243;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="secci&#243;n llamada &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabla&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" y "/>
+    <l:template name="seplast" text=", y "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Ver "/>
+    <l:template name="seealso" text="Ver tambi&#233;n "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Audiencia: "/>
+    <l:template name="MsgLevel" text="Nivel: "/>
+    <l:template name="MsgOrig" text="Origen: "/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/et.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/et.xml
new file mode 100644
index 00000000000..3a12eadd334
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/et.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="et" english-language-name="Estonian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/et.xml -->
+  <l:gentext key="Abstract" text="&#220;levaade"/>
+  <l:gentext key="abstract" text="&#220;levaade"/>
+  <l:gentext key="Answer" text="V:"/>
+  <l:gentext key="answer" text="V:"/>
+  <l:gentext key="Appendix" text="Lisa"/>
+  <l:gentext key="appendix" text="lisa"/>
+  <l:gentext key="Article" text="Artikkel"/>
+  <l:gentext key="article" text="Artikkel"/>
+  <l:gentext key="Bibliography" text="Bibliograafia"/>
+  <l:gentext key="bibliography" text="Bibliograafia"/>
+  <l:gentext key="Book" text="Raamat"/>
+  <l:gentext key="book" text="Raamat"/>
+  <l:gentext key="CAUTION" text="ETTEVAATUST"/>
+  <l:gentext key="Caution" text="Ettevaatust"/>
+  <l:gentext key="caution" text="Ettevaatust"/>
+  <l:gentext key="Chapter" text="Peat&#252;kk"/>
+  <l:gentext key="chapter" text="peat&#252;kk"/>
+  <l:gentext key="Colophon" text="L&#245;pum&#228;rgis"/>
+  <l:gentext key="colophon" text="L&#245;pum&#228;rgis"/>
+  <l:gentext key="Copyright" text="Autori&#245;igus"/>
+  <l:gentext key="copyright" text="Autori&#245;igus"/>
+  <l:gentext key="Dedication" text="P&#252;hendus"/>
+  <l:gentext key="dedication" text="P&#252;hendus"/>
+  <l:gentext key="Edition" text="V&#228;ljaanne"/>
+  <l:gentext key="edition" text="V&#228;ljaanne"/>
+  <l:gentext key="Equation" text="Valem"/>
+  <l:gentext key="equation" text="Valem"/>
+  <l:gentext key="Example" text="N&#228;ide"/>
+  <l:gentext key="example" text="N&#228;ide"/>
+  <l:gentext key="Figure" text="Joonis"/>
+  <l:gentext key="figure" text="Joonis"/>
+  <l:gentext key="Glossary" text="S&#245;nastik"/>
+  <l:gentext key="glossary" text="S&#245;nastik"/>
+  <l:gentext key="GlossSee" text="Vt."/>
+  <l:gentext key="glosssee" text="Vt."/>
+  <l:gentext key="GlossSeeAlso" text="Vt. ka"/>
+  <l:gentext key="glossseealso" text="Vt. ka"/>
+  <l:gentext key="IMPORTANT" text="OLULINE"/>
+  <l:gentext key="Important" text="Oluline"/>
+  <l:gentext key="important" text="Oluline"/>
+  <l:gentext key="Index" text="Aineregister"/>
+  <l:gentext key="index" text="Aineregister"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Autori&#245;iguse m&#228;rge"/>
+  <l:gentext key="legalnotice" text="Autori&#245;iguse m&#228;rge"/>
+  <l:gentext key="MsgAud" text="Auditoorium"/>
+  <l:gentext key="msgaud" text="Auditoorium"/>
+  <l:gentext key="MsgLevel" text="Tase"/>
+  <l:gentext key="msglevel" text="Tase"/>
+  <l:gentext key="MsgOrig" text="Algallikas"/>
+  <l:gentext key="msgorig" text="Algallikas"/>
+  <l:gentext key="NOTE" text="M&#196;RKUS"/>
+  <l:gentext key="Note" text="M&#228;rkus"/>
+  <l:gentext key="note" text="M&#228;rkus"/>
+  <l:gentext key="Part" text="Osa"/>
+  <l:gentext key="part" text="Osa"/>
+  <l:gentext key="Preface" text="Eess&#245;na"/>
+  <l:gentext key="preface" text="Eess&#245;na"/>
+  <l:gentext key="Procedure" text="Protseduur"/>
+  <l:gentext key="procedure" text="Protseduur"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="Avaldatud"/>
+  <l:gentext key="published" text="Avaldatud"/>
+  <l:gentext key="Question" text="K:"/>
+  <l:gentext key="question" text="K:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Viide"/>
+  <l:gentext key="reference" text="Viide"/>
+  <l:gentext key="RefName" text="Nimi"/>
+  <l:gentext key="refname" text="Nimi"/>
+  <l:gentext key="RefSection" text="L&#245;ik"/>
+  <l:gentext key="refsection" text="L&#245;ik"/>
+  <l:gentext key="RefSynopsisDiv" text="S&#252;nopsis"/>
+  <l:gentext key="refsynopsisdiv" text="S&#252;nopsis"/>
+  <l:gentext key="RevHistory" text="Vigade paranduste ajalugu"/>
+  <l:gentext key="revhistory" text="Vigade paranduste ajalugu"/>
+  <l:gentext key="Revision" text="Vigade parandus"/>
+  <l:gentext key="revision" text="Vigade parandus"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="section" text="l&#245;ik"/>
+  <l:gentext key="Section" text="Sektsioon"/>
+  <l:gentext key="See" text="Vt."/>
+  <l:gentext key="see" text="Vt."/>
+  <l:gentext key="SeeAlso" text="Vt. ka"/>
+  <l:gentext key="Seealso" text="Vt. ka"/>
+  <l:gentext key="seealso" text="Vt. ka"/>
+  <l:gentext key="Set" text="Sea"/>
+  <l:gentext key="set" text="Sea"/>
+  <l:gentext key="SetIndex" text="Sea indeks"/>
+  <l:gentext key="setindex" text="Sea indeks"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="k&#252;lgriba"/>
+  <l:gentext key="Step" text="Samm"/>
+  <l:gentext key="step" text="samm"/>
+  <l:gentext key="Table" text="Tabel"/>
+  <l:gentext key="table" text="Tabel"/>
+  <l:gentext key="TIP" text="VIHJE"/>
+  <l:gentext key="Tip" text="Vihje"/>
+  <l:gentext key="tip" text="Vihje"/>
+  <l:gentext key="WARNING" text="HOIATUS"/>
+  <l:gentext key="Warning" text="Hoiatus"/>
+  <l:gentext key="warning" text="Hoiatus"/>
+  <l:gentext key="and" text="ja"/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="Edited" text="Redaktsioon"/>
+  <l:gentext key="edited" text="Redaktsioon"/>
+  <l:gentext key="Editedby" text="Redaktsiooni autor(id)"/>
+  <l:gentext key="editedby" text="Redaktsiooni autor(id)"/>
+  <l:gentext key="in" text=""/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="mitte eksisteeriv element"/>
+  <l:gentext key="Notes" text="M&#228;rkused"/>
+  <l:gentext key="notes" text="M&#228;rkused"/>
+  <l:gentext key="Pgs" text="Lk."/>
+  <l:gentext key="pgs" text="Lk."/>
+  <l:gentext key="Revisedby" text="&#220;le vaadanud: "/>
+  <l:gentext key="revisedby" text="&#220;le vaadanud: "/>
+  <l:gentext key="TableNotes" text="M&#228;rkused"/>
+  <l:gentext key="tablenotes" text="M&#228;rkused"/>
+  <l:gentext key="TableofContents" text="Sisukord"/>
+  <l:gentext key="tableofcontents" text="Sisukord"/>
+  <l:gentext key="unexpectedelementname" text="Ootamatu elemendi nimi"/>
+  <l:gentext key="unsupported" text="toetuseta"/>
+  <l:gentext key="xrefto" text="viide"/>
+  <l:gentext key="listofequations" text="Valemite nimekiri"/>
+  <l:gentext key="ListofEquations" text="Valemite nimekiri"/>
+  <l:gentext key="ListofExamples" text="N&#228;idete nimekiri"/>
+  <l:gentext key="listofexamples" text="N&#228;idete nimekiri"/>
+  <l:gentext key="ListofFigures" text="Jooniste nimekiri"/>
+  <l:gentext key="listoffigures" text="Jooniste nimekiri"/>
+  <l:gentext key="listoftables" text="Tabelite nimekiri"/>
+  <l:gentext key="ListofTables" text="Tabelite nimekiri"/>
+  <l:gentext key="ListofUnknown" text="Tundmatute nimekiri"/>
+  <l:gentext key="listofunknown" text="Tundmatute nimekiri"/>
+  <l:gentext key="nav-home" text="Koju"/>
+  <l:gentext key="nav-next" text="J&#228;rgmine"/>
+  <l:gentext key="nav-next-sibling" text="Kiiresti edasi"/>
+  <l:gentext key="nav-prev" text="Eelmine"/>
+  <l:gentext key="nav-prev-sibling" text="Kiiresti tagasi"/>
+  <l:gentext key="nav-up" text="&#220;les"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/et.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Lisa %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Peat&#252;kk %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Valem %n. %t"/>
+    <l:template name="example" text="N&#228;ide %n. %t"/>
+    <l:template name="figure" text="Joonis %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Osa %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Protseduur&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabel %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Lisa %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="Peat&#252;kk %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="V:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="K:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="K:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="V:&#160;%n"/>
+    <l:template name="appendix" text="Lisa&#160;%n"/>
+    <l:template name="bridgehead" text="Sektsioon&#160;%n"/>
+    <l:template name="chapter" text="Peat&#252;kk&#160;%n"/>
+    <l:template name="equation" text="Valem&#160;%n"/>
+    <l:template name="example" text="N&#228;ide&#160;%n"/>
+    <l:template name="figure" text="Joonis&#160;%n"/>
+    <l:template name="part" text="Osa&#160;%n"/>
+    <l:template name="procedure" text="Protseduur&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="K:&#160;%n"/>
+    <l:template name="question" text="K:&#160;%n"/>
+    <l:template name="sect1" text="Sektsioon&#160;%n"/>
+    <l:template name="sect2" text="Sektsioon&#160;%n"/>
+    <l:template name="sect3" text="Sektsioon&#160;%n"/>
+    <l:template name="sect4" text="Sektsioon&#160;%n"/>
+    <l:template name="sect5" text="Sektsioon&#160;%n"/>
+    <l:template name="section" text="Sektsioon&#160;%n"/>
+    <l:template name="table" text="Tabel&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Lisa&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Sektsioon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Peat&#252;kk&#160;%n, %t"/>
+    <l:template name="equation" text="Valem&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="N&#228;ide&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Joonis&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Osa&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Protseduur&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Sektsioon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Sektsioon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Sektsioon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Sektsioon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Sektsioon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Sektsioon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabel&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" ja "/>
+    <l:template name="seplast" text=", ja "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Vt. "/>
+    <l:template name="seealso" text="Vt. ka "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Auditoorium: "/>
+    <l:template name="MsgLevel" text="Tase: "/>
+    <l:template name="MsgOrig" text="Algallikas: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0425 Estonian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/eu.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/eu.xml
new file mode 100644
index 00000000000..9a04138f210
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/eu.xml
@@ -0,0 +1,444 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="eu" english-language-name="Basque">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/eu.xml -->
+  <l:gentext key="Abstract" text="Laburpena"/>
+  <l:gentext key="abstract" text="Laburpena"/>
+  <l:gentext key="Answer" text="E:"/>
+  <l:gentext key="answer" text="E:"/>
+  <l:gentext key="Appendix" text="Eranskina"/>
+  <l:gentext key="appendix" text="eranskina"/>
+  <l:gentext key="Article" text="Artikulua"/>
+  <l:gentext key="article" text="Artikulua"/>
+  <l:gentext key="Bibliography" text="Bibliografia"/>
+  <l:gentext key="bibliography" text="Bibliografia"/>
+  <l:gentext key="Book" text="Liburua"/>
+  <l:gentext key="book" text="Liburua"/>
+  <l:gentext key="CAUTION" text="KONTUZ"/>
+  <l:gentext key="Caution" text="Kontuz"/>
+  <l:gentext key="caution" text="Kontuz"/>
+  <l:gentext key="Chapter" text="Atala"/>
+  <l:gentext key="chapter" text="atala"/>
+  <l:gentext key="Colophon" text="Azken ohar"/>
+  <l:gentext key="colophon" text="Azken ohar"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Eskaintza"/>
+  <l:gentext key="dedication" text="Eskaintza"/>
+  <l:gentext key="Edition" text="Edizioa"/>
+  <l:gentext key="edition" text="Edizioa"/>
+  <l:gentext key="Equation" text="Ekuazioa"/>
+  <l:gentext key="equation" text="Ekuazioa"/>
+  <l:gentext key="Example" text="Adibidea"/>
+  <l:gentext key="example" text="Adibidea"/>
+  <l:gentext key="Figure" text="Irudia"/>
+  <l:gentext key="figure" text="Irudia"/>
+  <l:gentext key="Glossary" text="Glosarioa"/>
+  <l:gentext key="glossary" text="Glosarioa"/>
+  <l:gentext key="GlossSee" text="Ikus"/>
+  <l:gentext key="glosssee" text="Ikus"/>
+  <l:gentext key="GlossSeeAlso" text="Ikus baita ere"/>
+  <l:gentext key="glossseealso" text="Ikus baita ere"/>
+  <l:gentext key="IMPORTANT" text="GARRANTZITSUA"/>
+  <l:gentext key="important" text="Garrantzitsua"/>
+  <l:gentext key="Important" text="Garrantzitsua"/>
+  <l:gentext key="Index" text="Indizea"/>
+  <l:gentext key="index" text="Indizea"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Legezko abisua"/>
+  <l:gentext key="legalnotice" text="Legezko abisua"/>
+  <l:gentext key="MsgAud" text="Audientzia"/>
+  <l:gentext key="msgaud" text="Audientzia"/>
+  <l:gentext key="MsgLevel" text="Maila"/>
+  <l:gentext key="msglevel" text="Maila"/>
+  <l:gentext key="MsgOrig" text="Jatorria"/>
+  <l:gentext key="msgorig" text="Jatorria"/>
+  <l:gentext key="NOTE" text="OHARRA"/>
+  <l:gentext key="Note" text="Oharra"/>
+  <l:gentext key="note" text="Oharra"/>
+  <l:gentext key="Part" text="Zatia"/>
+  <l:gentext key="part" text="Zatia"/>
+  <l:gentext key="Preface" text="Hitzaurrea"/>
+  <l:gentext key="preface" text="Hitzaurrea"/>
+  <l:gentext key="Procedure" text="Prozedura"/>
+  <l:gentext key="procedure" text="Prozedura"/>
+  <l:gentext key="ProductionSet" text="Ekoizpena"/>
+  <l:gentext key="Published" text="Argitaratua"/>
+  <l:gentext key="published" text="Argitaratua"/>
+  <l:gentext key="Question" text="Galdera"/>
+  <l:gentext key="question" text="galdera"/>
+  <l:gentext key="RefEntry" text="Sarrera"/>
+  <l:gentext key="refentry" text="Sarrera"/>
+  <l:gentext key="Reference" text="Erreferentzia"/>
+  <l:gentext key="reference" text="Erreferentzia"/>
+  <l:gentext key="RefName" text="Izena"/>
+  <l:gentext key="refname" text="Izena"/>
+  <l:gentext key="RefSection" text="Sekzioa"/>
+  <l:gentext key="refsection" text="sekzioa"/>
+  <l:gentext key="RefSynopsisDiv" text="Laburpena"/>
+  <l:gentext key="refsynopsisdiv" text="Laburpena"/>
+  <l:gentext key="RevHistory" text="Berrikuspenaren historia"/>
+  <l:gentext key="revhistory" text="Berrikuspenaren historia"/>
+  <l:gentext key="revision" text="Berrikuspena"/>
+  <l:gentext key="Revision" text="Berrikuspena"/>
+  <l:gentext key="sect1" text="Atala"/>
+  <l:gentext key="sect2" text="Atala"/>
+  <l:gentext key="sect3" text="Atala"/>
+  <l:gentext key="sect4" text="Atala"/>
+  <l:gentext key="sect5" text="Atala"/>
+  <l:gentext key="section" text="Atala"/>
+  <l:gentext key="Section" text="Atala"/>
+  <l:gentext key="See" text="Ikus"/>
+  <l:gentext key="see" text="Ikus"/>
+  <l:gentext key="SeeAlso" text="Ikus baita ere"/>
+  <l:gentext key="seealso" text="Ikus baita ere"/>
+  <l:gentext key="Seealso" text="Ikus baita ere"/>
+  <l:gentext key="set" text="Konfiguratu"/>
+  <l:gentext key="Set" text="Konfiguratu"/>
+  <l:gentext key="setindex" text="Konfiguratu indizea"/>
+  <l:gentext key="SetIndex" text="Konfiguratu indizea"/>
+  <l:gentext key="Sidebar" text="Alboko barra"/>
+  <l:gentext key="sidebar" text="alboko barra"/>
+  <l:gentext key="step" text="urratsa"/>
+  <l:gentext key="Step" text="Urratsa"/>
+  <l:gentext key="Table" text="Taula"/>
+  <l:gentext key="table" text="Taula"/>
+  <l:gentext key="tip" text="Iradokizuna"/>
+  <l:gentext key="TIP" text="IRADOKIZUNA"/>
+  <l:gentext key="Tip" text="Iradokizuna"/>
+  <l:gentext key="Warning" text="Abisua"/>
+  <l:gentext key="warning" text="Abisua"/>
+  <l:gentext key="WARNING" text="ABISUA"/>
+  <l:gentext key="and" text="eta"/>
+  <l:gentext key="by" text="Honek"/>
+  <l:gentext key="Edited" text="editatua"/>
+  <l:gentext key="edited" text="editatua"/>
+  <l:gentext key="Editedby" text="Honek editatua"/>
+  <l:gentext key="editedby" text="Honek editatua"/>
+  <l:gentext key="in" text="non"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="lehendik ez dagoen elementua"/>
+  <l:gentext key="notes" text="Oharrak"/>
+  <l:gentext key="Notes" text="Oharrak"/>
+  <l:gentext key="Pgs" text="Orr."/>
+  <l:gentext key="pgs" text="Orr."/>
+  <l:gentext key="Revisedby" text="Berrikuspena: "/>
+  <l:gentext key="revisedby" text="Berrikuspena: "/>
+  <l:gentext key="TableNotes" text="Oharrak"/>
+  <l:gentext key="tablenotes" text="Oharrak"/>
+  <l:gentext key="TableofContents" text="Edukien aurkibidea"/>
+  <l:gentext key="tableofcontents" text="Edukien aurkibidea"/>
+  <l:gentext key="unexpectedelementname" text="Ustekabeko elemetu-izena"/>
+  <l:gentext key="unsupported" text="onartzen ez den"/>
+  <l:gentext key="xrefto" text="xref honi"/>
+  <l:gentext key="listofequations" text="Ekuazioen zerrenda"/>
+  <l:gentext key="ListofEquations" text="Ekuazioen zerrenda"/>
+  <l:gentext key="ListofExamples" text="Adibideen zerrenda"/>
+  <l:gentext key="listofexamples" text="Adibideen zerrenda"/>
+  <l:gentext key="ListofFigures" text="Irudien zerrenda"/>
+  <l:gentext key="listoffigures" text="Irudien zerrenda"/>
+  <l:gentext key="listoftables" text="Taulen zerrenda"/>
+  <l:gentext key="ListofTables" text="Taulen zerrenda"/>
+  <l:gentext key="ListofUnknown" text="Ezezagunen zerrenda"/>
+  <l:gentext key="listofunknown" text="Ezazagunen zerrenda"/>
+  <l:gentext key="nav-home" text="Etxea"/>
+  <l:gentext key="nav-next" text="Hurrengoa"/>
+  <l:gentext key="nav-next-sibling" text="Aurreratze azkarra"/>
+  <l:gentext key="nav-prev" text="Aurrekoa"/>
+  <l:gentext key="nav-prev-sibling" text="Atzeratze azkarra"/>
+  <l:gentext key="nav-up" text="Gora"/>
+  <l:gentext key="sectioncalled" text="honela deritzon atala"/>
+  <l:gentext key="Draft" text="Zirriborroa"/>
+  <l:gentext key="above" text="goian"/>
+  <l:gentext key="below" text="behean"/>
+  <l:gentext key="index symbols" text="Ikurrak"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/eu.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Eranskina %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Atala %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Ekuazioa %n. %t"/>
+    <l:template name="example" text="Adibidea %n. %t"/>
+    <l:template name="figure" text="Irudia %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Zatia %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Prozedura %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Ekoizpena %n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Taula %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Eranskina %n. %t"/>
+    <l:template name="chapter" text="Atala %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="E:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Galdera&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Galdera&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="section" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="honela deritzon atala &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="E:&#160;%n"/>
+    <l:template name="appendix" text="Eranskina&#160;%n"/>
+    <l:template name="bridgehead" text="Atala&#160;%n"/>
+    <l:template name="chapter" text="Atala&#160;%n"/>
+    <l:template name="equation" text="Ekuazioa&#160;%n"/>
+    <l:template name="example" text="Adibidea&#160;%n"/>
+    <l:template name="figure" text="Irudia&#160;%n"/>
+    <l:template name="part" text="Zatia&#160;%n"/>
+    <l:template name="procedure" text="Prozedura&#160;%n"/>
+    <l:template name="productionset" text="Ekoizpena&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Galdera&#160;%n"/>
+    <l:template name="question" text="Galdera&#160;%n"/>
+    <l:template name="sect1" text="Atala&#160;%n"/>
+    <l:template name="sect2" text="Atala&#160;%n"/>
+    <l:template name="sect3" text="Atala&#160;%n"/>
+    <l:template name="sect4" text="Atala&#160;%n"/>
+    <l:template name="sect5" text="Atala&#160;%n"/>
+    <l:template name="section" text="Atala&#160;%n"/>
+    <l:template name="table" text="Taula&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Eranskina&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Atala&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Atala&#160;%n, %t"/>
+    <l:template name="equation" text="Ekuazioa&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Adibidea&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Irudia&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Zatia&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Prozedura&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Ekoizpena&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Atala&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Atala&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Atala&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Atala&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Atala&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Atala&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="honela deritzon atala &#8220;%t&#8221;"/>
+    <l:template name="table" text="Taula&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" eta "/>
+    <l:template name="seplast" text=", eta "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Ikus "/>
+    <l:template name="seealso" text="Ikus baita ere "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Audientzia: "/>
+    <l:template name="MsgLevel" text="Maila: "/>
+    <l:template name="MsgOrig" text="Jatorria: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x042d Basque"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/fi.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/fi.xml
new file mode 100644
index 00000000000..a641a029ef4
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/fi.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="fi" english-language-name="Finnish">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fi.xml -->
+  <l:gentext key="Abstract" text="Lyhennelm&#228;"/>
+  <l:gentext key="abstract" text="Lyhennelm&#228;"/>
+  <l:gentext key="Answer" text="A:"/>
+  <l:gentext key="answer" text="A:"/>
+  <l:gentext key="Appendix" text="Liite"/>
+  <l:gentext key="appendix" text="liite"/>
+  <l:gentext key="Article" text="Artikkeli"/>
+  <l:gentext key="article" text="Artikkeli"/>
+  <l:gentext key="Bibliography" text="L&#228;hteet"/>
+  <l:gentext key="bibliography" text="L&#228;hteet"/>
+  <l:gentext key="Book" text="Kirja"/>
+  <l:gentext key="book" text="Kirja"/>
+  <l:gentext key="CAUTION" text="VARO"/>
+  <l:gentext key="Caution" text="Varo"/>
+  <l:gentext key="caution" text="Varo"/>
+  <l:gentext key="Chapter" text="Luku"/>
+  <l:gentext key="chapter" text="luku"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Omistus"/>
+  <l:gentext key="dedication" text="Omistus"/>
+  <l:gentext key="Edition" text="Edition"/>
+  <l:gentext key="edition" text="Edition"/>
+  <l:gentext key="Equation" text="Kaava"/>
+  <l:gentext key="equation" text="Kaava"/>
+  <l:gentext key="Example" text="Esimerkki"/>
+  <l:gentext key="example" text="Esimerkki"/>
+  <l:gentext key="Figure" text="Kuva"/>
+  <l:gentext key="figure" text="Kuva"/>
+  <l:gentext key="Glossary" text="Sanasto"/>
+  <l:gentext key="glossary" text="Sanasto"/>
+  <l:gentext key="GlossSee" text="Katso"/>
+  <l:gentext key="glosssee" text="Katso"/>
+  <l:gentext key="GlossSeeAlso" text="Katso my&#246;s"/>
+  <l:gentext key="glossseealso" text="Katso my&#246;s"/>
+  <l:gentext key="IMPORTANT" text="T&#196;RKE&#196;&#196;"/>
+  <l:gentext key="Important" text="T&#228;rke&#228;&#228;"/>
+  <l:gentext key="important" text="T&#228;rke&#228;&#228;"/>
+  <l:gentext key="Index" text="Indeksi"/>
+  <l:gentext key="index" text="Indeksi"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text=""/>
+  <l:gentext key="legalnotice" text=""/>
+  <l:gentext key="MsgAud" text="Yleis&#246;"/>
+  <l:gentext key="msgaud" text="Yleis&#246;"/>
+  <l:gentext key="MsgLevel" text="Taso"/>
+  <l:gentext key="msglevel" text="Taso"/>
+  <l:gentext key="MsgOrig" text="Alkuper&#228;"/>
+  <l:gentext key="msgorig" text="Alkuper&#228;"/>
+  <l:gentext key="NOTE" text="HUOMAA"/>
+  <l:gentext key="Note" text="Huomaa"/>
+  <l:gentext key="note" text="Huomaa"/>
+  <l:gentext key="Part" text="Osa"/>
+  <l:gentext key="part" text="Osa"/>
+  <l:gentext key="Preface" text="Esipuhe"/>
+  <l:gentext key="preface" text="Esipuhe"/>
+  <l:gentext key="Procedure" text="Aliohjelma"/>
+  <l:gentext key="procedure" text="Aliohjelma"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="Julkaistu"/>
+  <l:gentext key="published" text="Julkaistu"/>
+  <l:gentext key="Question" text="Q:"/>
+  <l:gentext key="question" text="Q:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="L&#228;hdeluettelo"/>
+  <l:gentext key="reference" text="L&#228;hdeluettelo"/>
+  <l:gentext key="RefName" text="Nimi"/>
+  <l:gentext key="refname" text="Nimi"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Versiohistoria"/>
+  <l:gentext key="revhistory" text="Versiohistoria"/>
+  <l:gentext key="Revision" text="Versio"/>
+  <l:gentext key="revision" text="Versio"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="Kohta"/>
+  <l:gentext key="section" text="kohta"/>
+  <l:gentext key="See" text="Katso"/>
+  <l:gentext key="see" text="Katso"/>
+  <l:gentext key="SeeAlso" text="Katso my&#246;s"/>
+  <l:gentext key="Seealso" text="Katso my&#246;s"/>
+  <l:gentext key="seealso" text="Katso my&#246;s"/>
+  <l:gentext key="Set" text="Kokoelma"/>
+  <l:gentext key="set" text="Kokoelma"/>
+  <l:gentext key="SetIndex" text="Kokoelman indeksi"/>
+  <l:gentext key="setindex" text="Kokoelman indeksi"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sivupalkki"/>
+  <l:gentext key="Step" text="Step"/>
+  <l:gentext key="step" text="step"/>
+  <l:gentext key="Table" text="Taulu"/>
+  <l:gentext key="table" text="Taulu"/>
+  <l:gentext key="TIP" text="VIHJE"/>
+  <l:gentext key="Tip" text="Vihje"/>
+  <l:gentext key="tip" text="Vihje"/>
+  <l:gentext key="WARNING" text="VAROITUS"/>
+  <l:gentext key="Warning" text="Varoitus"/>
+  <l:gentext key="warning" text="Varoitus"/>
+  <l:gentext key="and" text="ja"/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="Edited" text="Toim."/>
+  <l:gentext key="edited" text="Toim."/>
+  <l:gentext key="Editedby" text="Toimittanut"/>
+  <l:gentext key="editedby" text="Toimittanut"/>
+  <l:gentext key="in" text="teoksessa"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="elementti&#228; ei ole olemassa"/>
+  <l:gentext key="notes" text=""/>
+  <l:gentext key="Notes" text=""/>
+  <l:gentext key="Pgs" text="Sivut"/>
+  <l:gentext key="pgs" text="Sivut"/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text=""/>
+  <l:gentext key="tablenotes" text=""/>
+  <l:gentext key="TableofContents" text="Sis&#228;llys"/>
+  <l:gentext key="tableofcontents" text="Sis&#228;llys"/>
+  <l:gentext key="unexpectedelementname" text="Odottamaton elementin nimi"/>
+  <l:gentext key="unsupported" text="ei tueta"/>
+  <l:gentext key="xrefto" text="xref johonkin"/>
+  <l:gentext key="listofequations" text="Luettelo esimerkeist&#228;"/>
+  <l:gentext key="ListofEquations" text="Luettelo esimerkeist&#228;"/>
+  <l:gentext key="ListofExamples" text="Luettelo esimerkeist&#228;"/>
+  <l:gentext key="listofexamples" text="Luettelo esimerkeist&#228;"/>
+  <l:gentext key="ListofFigures" text="Luettelo kuvista"/>
+  <l:gentext key="listoffigures" text="Luettelo kuvista"/>
+  <l:gentext key="listoftables" text="Luettelo tauluista"/>
+  <l:gentext key="ListofTables" text="Luettelo tauluista"/>
+  <l:gentext key="ListofUnknown" text="Luettelo tuntemattomista"/>
+  <l:gentext key="listofunknown" text="Luettelo tuntemattomista"/>
+  <l:gentext key="nav-home" text="Alkuun"/>
+  <l:gentext key="nav-next" text="Seuraava"/>
+  <l:gentext key="nav-next-sibling" text="Nopeasti eteenp&#228;in"/>
+  <l:gentext key="nav-prev" text="Edellinen"/>
+  <l:gentext key="nav-prev-sibling" text="Nopeasti taaksep&#228;in"/>
+  <l:gentext key="nav-up" text="Yl&#246;s"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fi.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Liite %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Luku %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Kaava %n. %t"/>
+    <l:template name="example" text="Esimerkki %n. %t"/>
+    <l:template name="figure" text="Kuva %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Osa %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Aliohjelma&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Taulu %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Liite %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Luku %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="Liite&#160;%n"/>
+    <l:template name="bridgehead" text="Kohta&#160;%n"/>
+    <l:template name="chapter" text="Luku&#160;%n"/>
+    <l:template name="equation" text="Kaava&#160;%n"/>
+    <l:template name="example" text="Esimerkki&#160;%n"/>
+    <l:template name="figure" text="Kuva&#160;%n"/>
+    <l:template name="part" text="Osa&#160;%n"/>
+    <l:template name="procedure" text="Aliohjelma&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="sect1" text="Kohta&#160;%n"/>
+    <l:template name="sect2" text="Kohta&#160;%n"/>
+    <l:template name="sect3" text="Kohta&#160;%n"/>
+    <l:template name="sect4" text="Kohta&#160;%n"/>
+    <l:template name="sect5" text="Kohta&#160;%n"/>
+    <l:template name="section" text="Kohta&#160;%n"/>
+    <l:template name="table" text="Taulu&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Liite&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Kohta&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Luku&#160;%n, %t"/>
+    <l:template name="equation" text="Kaava&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Esimerkki&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Kuva&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Osa&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Aliohjelma&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Kohta&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Kohta&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Kohta&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Kohta&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Kohta&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Kohta&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Taulu&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" ja "/>
+    <l:template name="seplast" text=", ja "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Katso "/>
+    <l:template name="seealso" text="Katso my&#246;s "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Yleis&#246;: "/>
+    <l:template name="MsgLevel" text="Taso: "/>
+    <l:template name="MsgOrig" text="Alkuper&#228;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x040b Finnish"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/fr.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/fr.xml
new file mode 100644
index 00000000000..0e6d82a2b62
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/fr.xml
@@ -0,0 +1,543 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="fr" english-language-name="French">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+  <l:gentext key="blockquote" text=""/>
+  <l:gentext key="formalpara" text="paragraphe"/>
+  <l:gentext key="nonexistantelement" text="element non-existant"/>
+  <l:gentext key="glossseealso" text="Voir aussi"/>
+  <l:gentext key="keyword" text="Mot Cl&#233;"/>
+  <l:gentext key="keywords" text="Mots Cl&#233;s"/>
+  <l:gentext key="keywordset" text="Mots Cl&#233;s"/>
+  <l:gentext key="the section called" text="the section called"/>
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fr.xml -->
+  <l:gentext key="Abstract" text="R&#233;sum&#233;"/>
+  <l:gentext key="abstract" text="R&#233;sum&#233;"/>
+  <l:gentext key="Answer" text="R&#160;:"/>
+  <l:gentext key="answer" text="R&#160;:"/>
+  <l:gentext key="Appendix" text="Annexe"/>
+  <l:gentext key="appendix" text="annexe"/>
+  <l:gentext key="Article" text="Article"/>
+  <l:gentext key="article" text="Article"/>
+  <l:gentext key="Bibliography" text="Bibliographie"/>
+  <l:gentext key="bibliography" text="Bibliographie"/>
+  <l:gentext key="Book" text="Livre"/>
+  <l:gentext key="book" text="Livre"/>
+  <l:gentext key="Caution" text="Attention"/>
+  <l:gentext key="caution" text="Attention"/>
+  <l:gentext key="CAUTION" text="ATTENTION"/>
+  <l:gentext key="Chapter" text="Chapitre"/>
+  <l:gentext key="chapter" text="chapitre"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="D&#233;dicace"/>
+  <l:gentext key="dedication" text="D&#233;dicace"/>
+  <l:gentext key="Edition" text="&#201;dition"/>
+  <l:gentext key="edition" text="&#201;dition"/>
+  <l:gentext key="Equation" text="&#201;quation"/>
+  <l:gentext key="equation" text="&#201;quation"/>
+  <l:gentext key="Example" text="Exemple"/>
+  <l:gentext key="example" text="Exemple"/>
+  <l:gentext key="Figure" text="Figure"/>
+  <l:gentext key="figure" text="Figure"/>
+  <l:gentext key="Glossary" text="Glossaire"/>
+  <l:gentext key="glossary" text="Glossaire"/>
+  <l:gentext key="GlossSee" text="Voir"/>
+  <l:gentext key="glosssee" text="Voir"/>
+  <l:gentext key="GlossSeeAlso" text="Voir aussi"/>
+  <l:gentext key="IMPORTANT" text="IMPORTANT"/>
+  <l:gentext key="important" text="Important"/>
+  <l:gentext key="Important" text="Important"/>
+  <l:gentext key="Index" text="Index"/>
+  <l:gentext key="index" text="Index"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Note l&#233;gale"/>
+  <l:gentext key="legalnotice" text="Note l&#233;gale"/>
+  <l:gentext key="MsgAud" text="Public vis&#233;"/>
+  <l:gentext key="msgaud" text="Public vis&#233;"/>
+  <l:gentext key="MsgLevel" text="Niveau"/>
+  <l:gentext key="msglevel" text="Niveau"/>
+  <l:gentext key="MsgOrig" text="Origine"/>
+  <l:gentext key="msgorig" text="Origine"/>
+  <l:gentext key="NOTE" text="NOTE"/>
+  <l:gentext key="Note" text="Note"/>
+  <l:gentext key="note" text="Note"/>
+  <l:gentext key="Part" text="Partie"/>
+  <l:gentext key="part" text="Partie"/>
+  <l:gentext key="Preface" text="Pr&#233;face"/>
+  <l:gentext key="preface" text="Pr&#233;face"/>
+  <l:gentext key="Procedure" text="Proc&#233;dure"/>
+  <l:gentext key="procedure" text="Proc&#233;dure"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="PubDate" text="Date de publication"/>
+  <l:gentext key="pubdate" text="Date de publication"/>
+  <l:gentext key="Published" text="Publi&#233;"/>
+  <l:gentext key="published" text="Publi&#233;"/>
+  <l:gentext key="Qandadiv" text="Q &amp; R"/>
+  <l:gentext key="qandadiv" text="Q &amp; R"/>
+  <l:gentext key="Question" text="Q&#160;:"/>
+  <l:gentext key="question" text="Q&#160;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="R&#233;f&#233;rence"/>
+  <l:gentext key="reference" text="R&#233;f&#233;rence"/>
+  <l:gentext key="RefName" text="Nom"/>
+  <l:gentext key="refname" text="Nom"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Historique des versions"/>
+  <l:gentext key="revhistory" text="Historique des versions"/>
+  <l:gentext key="Revision" text="Version"/>
+  <l:gentext key="revision" text="Version"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="section" text="section"/>
+  <l:gentext key="Section" text="Section"/>
+  <l:gentext key="see" text="voir"/>
+  <l:gentext key="See" text="Voir"/>
+  <l:gentext key="seealso" text="voir aussi"/>
+  <l:gentext key="Seealso" text="Voir aussi"/>
+  <l:gentext key="SeeAlso" text="Voir Aussi"/>
+  <l:gentext key="set" text="Ensemble"/>
+  <l:gentext key="Set" text="Ensemble"/>
+  <l:gentext key="setindex" text="Index"/>
+  <l:gentext key="SetIndex" text="Index"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text=""/>
+  <l:gentext key="step" text="&#233;tape"/>
+  <l:gentext key="Step" text="&#201;tape"/>
+  <l:gentext key="Table" text="Tableau"/>
+  <l:gentext key="table" text="Tableau"/>
+  <l:gentext key="tip" text="ASTUCE"/>
+  <l:gentext key="TIP" text="ASTUCE"/>
+  <l:gentext key="Tip" text="Astuce"/>
+  <l:gentext key="Warning" text="Avertissement"/>
+  <l:gentext key="WARNING" text="AVERTISSEMENT"/>
+  <l:gentext key="warning" text="AVERTISSEMENT"/>
+  <l:gentext key="and" text="et"/>
+  <l:gentext key="by" text="par"/>
+  <l:gentext key="called" text="intitul&#233;"/>
+  <l:gentext key="Edited" text="Publi&#233;"/>
+  <l:gentext key="edited" text="Publi&#233;"/>
+  <l:gentext key="Editedby" text="Publi&#233; par"/>
+  <l:gentext key="editedby" text="Publi&#233; par"/>
+  <l:gentext key="in" text="dans"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="notes" text="Notes"/>
+  <l:gentext key="Notes" text="Notes"/>
+  <l:gentext key="Pgs" text="Pages"/>
+  <l:gentext key="pgs" text="Pages"/>
+  <l:gentext key="Revisedby" text="Revu par&#160;: "/>
+  <l:gentext key="revisedby" text="Revu par&#160;: "/>
+  <l:gentext key="TableNotes" text="Remarques"/>
+  <l:gentext key="tablenotes" text="Remarques"/>
+  <l:gentext key="TableofContents" text="Table des mati&#232;res"/>
+  <l:gentext key="tableofcontents" text="Table des mati&#232;res"/>
+  <l:gentext key="the" text=""/>
+  <l:gentext key="unexpectedelementname" text="Nom d'&#233;l&#233;ment non attendu"/>
+  <l:gentext key="unsupported" text="Non reconnu par le syst&#232;me"/>
+  <l:gentext key="xrefto" text="R&#233;f&#233;rence vers"/>
+  <l:gentext key="listofequations" text="Liste des &#233;quations"/>
+  <l:gentext key="ListofEquations" text="Liste des &#233;quations"/>
+  <l:gentext key="ListofExamples" text="Liste des exemples"/>
+  <l:gentext key="listofexamples" text="Liste des exemples"/>
+  <l:gentext key="ListofFigures" text="Liste des illustrations"/>
+  <l:gentext key="listoffigures" text="Liste des illustrations"/>
+  <l:gentext key="ListofProcedures" text="Liste des proc&#233;dures"/>
+  <l:gentext key="listofprocedures" text="Liste des proc&#233;dures"/>
+  <l:gentext key="listoftables" text="Liste des tableaux"/>
+  <l:gentext key="ListofTables" text="Liste des tableaux"/>
+  <l:gentext key="ListofUnknown" text="Liste des inconnues"/>
+  <l:gentext key="listofunknown" text="Liste des inconnues"/>
+  <l:gentext key="nav-home" text="Sommaire"/>
+  <l:gentext key="nav-next" text="Suivant"/>
+  <l:gentext key="nav-next-sibling" text="Avance rapide"/>
+  <l:gentext key="nav-prev" text="Pr&#233;c&#233;dent"/>
+  <l:gentext key="nav-prev-sibling" text="Arri&#232;re rapide"/>
+  <l:gentext key="nav-up" text="Niveau sup&#233;rieur"/>
+  <l:gentext key="nav-toc" text="TdM"/>
+  <l:gentext key="Draft" text="Brouillon"/>
+  <l:gentext key="above" text="au dessus"/>
+  <l:gentext key="below" text="au dessous"/>
+  <l:gentext key="sectioncalled" text="la section intitul&#233;e"/>
+  <l:gentext key="index symbols" text="Symboles"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz&#226;&#234;&#238;&#244;&#251;&#235;&#239;&#252;&#224;&#232;&#249;&#233;&#231;&#230;&#339;"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ&#194;&#202;&#206;&#212;&#219;&#203;&#207;&#220;&#192;&#200;&#217;&#201;&#199;&#198;&#338;"/>
+  <l:gentext key="hyphenation-character" text="-"/>
+  <l:gentext key="hyphenation-push-character-count" text="2"/>
+  <l:gentext key="hyphenation-remain-character-count" text="2"/>
+  <l:dingbat key="startquote" text="&#171;"/>
+  <l:dingbat key="endquote" text="&#187;"/>
+  <l:dingbat key="nestedstartquote" text="{``}"/>
+  <l:dingbat key="nestedendquote" text="{''}"/>
+  <l:dingbat key="singlestartquote" text="\guilsinglleft{}"/>
+  <l:dingbat key="singleendquote" text="\guilsinglright{}"/>
+  <l:dingbat key="urlstartquote" text="{\textless}"/>
+  <l:dingbat key="urlendquote" text="{\textgreater}"/>
+  <l:dingbat key="bullet" text="\textbullet{}"/>
+  <l:dingbat key="decimalpoint" text="."/>
+  <l:dingbat key="latexdecimal" text="."/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fr.xml -->
+<!-- The following contexts were merged from two source files. -->
+  <l:context name="naturalinlinelist">
+    <l:template name="start" text=""/>
+    <l:template name="middle" text=", "/>
+    <l:template name="lastoftwo" text=" et "/>
+    <l:template name="lastofmany" text=", et "/>
+    <l:template name="end" text=". "/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fr.xml -->
+  </l:context>
+  <l:context name="naturalblocklist">
+    <l:template name="start" text=""/>
+    <l:template name="middle" text=", "/>
+    <l:template name="lastoftwo" text=", "/>
+    <l:template name="lastofmany" text=", "/>
+    <l:template name="end" text=""/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fr.xml -->
+  </l:context>
+  <l:context name="xref">
+    <l:template name="page.citation" text=" &#224; la page %p"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fr.xml -->
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="R&#160;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Q&#160;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Q&#160;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page" text="(page %p)"/>
+    <l:template name="pageabbrev" text="(p. %p)"/>
+    <l:template name="Page" text="Page %p"/>
+    <l:template name="bridgehead" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="refsection" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="refsect1" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="refsect2" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="refsect3" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect1" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect2" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect3" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect4" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect5" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="section" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="simplesect" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="appendix" text="Annexe&#160;%n"/>
+    <l:template name="chapter" text="Chapitre&#160;%n, %t"/>
+    <l:template name="reference" text="R&#233;f&#233;rence&#160;%n"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fr.xml -->
+    <l:template name="answer" text="R&#160;:&#160;%n"/>
+    <l:template name="bridgehead" text="Section&#160;%n"/>
+    <l:template name="equation" text="&#201;quation&#160;%n"/>
+    <l:template name="example" text="Exemple&#160;%n"/>
+    <l:template name="figure" text="Figure&#160;%n"/>
+    <l:template name="part" text="Partie&#160;%n"/>
+    <l:template name="procedure" text="Proc&#233;dure&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; R&#160;%n"/>
+    <l:template name="qandaentry" text="Q&#160;:&#160;%n"/>
+    <l:template name="question" text="Q&#160;:&#160;%n"/>
+    <l:template name="sect1" text="Section&#160;%n"/>
+    <l:template name="sect2" text="Section&#160;%n"/>
+    <l:template name="sect3" text="Section&#160;%n"/>
+    <l:template name="sect4" text="Section&#160;%n"/>
+    <l:template name="sect5" text="Section&#160;%n"/>
+    <l:template name="section" text="Section&#160;%n"/>
+    <l:template name="table" text="Tableau&#160;%n"/>
+  </l:context>
+  <l:context name="datetime">
+<!-- The following templates override or supplement those lower down. -->
+    <l:template name="format" text="d-m-Y"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fr.xml -->
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x040C French (FRANCE)"/>
+<!-- Any further templates were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/fr.xml -->
+  </l:context>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Annexe&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Chapitre&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#201;quation&#160;%n.&#160;%t"/>
+    <l:template name="example" text="Exemple&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="Figure&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Proc&#233;dure&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tableau&#160;%n.&#160;%t"/>
+    <l:template name="task" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Annexe&#160;%n.&#160;%t"/>
+    <l:template name="article/appendix" text="%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="Chapitre&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Annexe&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Section&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="chapter" text="Chapitre&#160;%n, %t"/>
+    <l:template name="equation" text="&#201;quation&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="example" text="Exemple&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="figure" text="Figure&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="part" text="Partie&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="procedure" text="Proc&#233;dure&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="qandadiv" text="Q &amp; R&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="refsect1" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="refsect2" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="refsect3" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="refsection" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect1" text="Section&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect2" text="Section&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect3" text="Section&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect4" text="Section&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="sect5" text="Section&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="section" text="Section&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="simplesect" text="la section intitul&#233;e &#171;&#160;%t&#160;&#187;"/>
+    <l:template name="table" text="Tableau&#160;%n, &#171;&#160;%t&#160;&#187;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" et "/>
+    <l:template name="seplast" text=", et "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Voir "/>
+    <l:template name="seealso" text="Voir aussi "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Public vis&#233;: "/>
+    <l:template name="MsgLevel" text="Niveau: "/>
+    <l:template name="MsgOrig" text="Origine: "/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="janvier"/>
+    <l:template name="February" text="f&#233;vrier"/>
+    <l:template name="March" text="mars"/>
+    <l:template name="April" text="avril"/>
+    <l:template name="May" text="mai"/>
+    <l:template name="June" text="juin"/>
+    <l:template name="July" text="juillet"/>
+    <l:template name="August" text="ao&#251;t"/>
+    <l:template name="September" text="septembre"/>
+    <l:template name="October" text="octobre"/>
+    <l:template name="November" text="novembre"/>
+    <l:template name="December" text="d&#233;cembre"/>
+    <l:template name="Monday" text="lundi"/>
+    <l:template name="Tuesday" text="mardi"/>
+    <l:template name="Wednesday" text="mercredi"/>
+    <l:template name="Thursday" text="jeudi"/>
+    <l:template name="Friday" text="vendredi"/>
+    <l:template name="Saturday" text="samedi"/>
+    <l:template name="Sunday" text="dimanche"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="jan"/>
+    <l:template name="Feb" text="f&#233;v"/>
+    <l:template name="Mar" text="mar"/>
+    <l:template name="Apr" text="avr"/>
+    <l:template name="May" text="mai"/>
+    <l:template name="Jun" text="jun"/>
+    <l:template name="Jul" text="jui"/>
+    <l:template name="Aug" text="ao&#251;"/>
+    <l:template name="Sep" text="sep"/>
+    <l:template name="Oct" text="oct"/>
+    <l:template name="Nov" text="nov"/>
+    <l:template name="Dec" text="d&#233;c"/>
+    <l:template name="Mon" text="lun"/>
+    <l:template name="Tue" text="mar"/>
+    <l:template name="Wed" text="mer"/>
+    <l:template name="Thu" text="jeu"/>
+    <l:template name="Fri" text="ven"/>
+    <l:template name="Sat" text="sam"/>
+    <l:template name="Sun" text="dim"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/gentext.xsl b/docs-xml/xslt/db2latex-xsl/xsl/common/gentext.xsl
new file mode 100644
index 00000000000..c4ac3f2312c
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/gentext.xsl
@@ -0,0 +1,716 @@
+<?xml version='1.0'?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+                exclude-result-prefixes="doc"
+                version='1.0'>
+
+<!-- ********************************************************************
+     $Id: gentext.xsl,v 1.4 2004/01/04 09:26:24 j-devenish Exp $
+     ********************************************************************
+
+     This file is part of the XSL DocBook Stylesheet distribution.
+
+     Copyright (C) 1999, 2000, 2001, 2002 Norman Walsh.
+     ******************************************************************** -->
+
+<!-- ==================================================================== -->
+
+<xsl:param name="appendix.autolabel" select="0"/>
+
+<xsl:template match="*" mode="object.title.template">
+  <xsl:call-template name="gentext.template">
+    <xsl:with-param name="context" select="'title'"/>
+    <xsl:with-param name="name">
+      <xsl:call-template name="xpath.location"/>
+    </xsl:with-param>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template match="chapter" mode="object.title.template">
+  <xsl:choose>
+    <xsl:when test="$chapter.autolabel != 0">
+      <xsl:call-template name="gentext.template">
+        <xsl:with-param name="context" select="'title-numbered'"/>
+        <xsl:with-param name="name">
+          <xsl:call-template name="xpath.location"/>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext.template">
+        <xsl:with-param name="context" select="'title-unnumbered'"/>
+        <xsl:with-param name="name">
+          <xsl:call-template name="xpath.location"/>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="appendix" mode="object.title.template">
+  <xsl:choose>
+    <xsl:when test="$appendix.autolabel != 0">
+      <xsl:call-template name="gentext.template">
+        <xsl:with-param name="context" select="'title-numbered'"/>
+        <xsl:with-param name="name">
+          <xsl:call-template name="xpath.location"/>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext.template">
+        <xsl:with-param name="context" select="'title-unnumbered'"/>
+        <xsl:with-param name="name">
+          <xsl:call-template name="xpath.location"/>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="section|sect1|sect2|sect3|sect4|sect5|simplesect
+                     |bridgehead"
+              mode="object.title.template">
+  <xsl:choose>
+    <xsl:when test="$section.autolabel != 0">
+      <xsl:call-template name="gentext.template">
+        <xsl:with-param name="context" select="'title-numbered'"/>
+        <xsl:with-param name="name">
+          <xsl:call-template name="xpath.location"/>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext.template">
+        <xsl:with-param name="context" select="'title-unnumbered'"/>
+        <xsl:with-param name="name">
+          <xsl:call-template name="xpath.location"/>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="procedure" mode="object.title.template">
+  <xsl:choose>
+    <xsl:when test="$formal.procedures != 0">
+      <xsl:call-template name="gentext.template">
+        <xsl:with-param name="context" select="'title'"/>
+        <xsl:with-param name="name">
+          <xsl:call-template name="xpath.location"/>
+          <xsl:text>.formal</xsl:text>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext.template">
+        <xsl:with-param name="context" select="'title'"/>
+        <xsl:with-param name="name">
+          <xsl:call-template name="xpath.location"/>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template match="*" mode="object.subtitle.template">
+  <xsl:call-template name="gentext.template">
+    <xsl:with-param name="context" select="'subtitle'"/>
+    <xsl:with-param name="name">
+      <xsl:call-template name="xpath.location"/>
+    </xsl:with-param>
+  </xsl:call-template>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template match="*" mode="is.autonumber">
+  <xsl:value-of select="'0'"/>
+</xsl:template>
+
+<xsl:template match="section|sect1|sect2|sect3|sect4|sect5" 
+              mode="is.autonumber">
+  <xsl:value-of select="$section.autolabel"/>
+</xsl:template>
+
+<xsl:template match="figure|example|table|equation" mode="is.autonumber">
+  <xsl:value-of select="'1'"/>
+</xsl:template>
+
+<xsl:template match="appendix" mode="is.autonumber">
+  <xsl:value-of select="$appendix.autolabel"/>
+</xsl:template>
+
+<xsl:template match="chapter" mode="is.autonumber">
+  <xsl:value-of select="$chapter.autolabel"/>
+</xsl:template>
+
+<xsl:template match="part" mode="is.autonumber">
+  <xsl:value-of select="$part.autolabel"/>
+</xsl:template>
+
+<xsl:template match="preface" mode="is.autonumber">
+  <xsl:value-of select="$preface.autolabel"/>
+</xsl:template>
+
+<xsl:template match="question|answer" mode="is.autonumber">
+  <xsl:choose>
+    <xsl:when test="$qanda.defaultlabel = 'number'
+                    and not(label)">
+      <xsl:value-of select="'1'"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:value-of select="'0'"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="qandadiv" mode="is.autonumber">
+  <xsl:value-of select="$qandadiv.autolabel"/>
+</xsl:template>
+
+<xsl:template match="bridgehead" mode="is.autonumber">
+  <xsl:value-of select="$section.autolabel"/>
+</xsl:template>
+
+<xsl:template match="*" mode="object.xref.template">
+  <xsl:param name="purpose"/>
+  <xsl:param name="xrefstyle"/>
+  <xsl:param name="referrer"/>
+
+  <!-- Is autonumbering on? -->
+  <xsl:variable name="autonumber">
+    <xsl:apply-templates select="." mode="is.autonumber"/>
+  </xsl:variable>
+
+  <xsl:variable name="number-and-title-template">
+    <xsl:call-template name="gentext.template.exists">
+      <xsl:with-param name="context" select="'xref-number-and-title'"/>
+      <xsl:with-param name="name">
+        <xsl:call-template name="xpath.location"/>
+      </xsl:with-param>
+    </xsl:call-template>
+  </xsl:variable>
+
+  <xsl:variable name="number-template">
+    <xsl:call-template name="gentext.template.exists">
+      <xsl:with-param name="context" select="'xref-number'"/>
+      <xsl:with-param name="name">
+        <xsl:call-template name="xpath.location"/>
+      </xsl:with-param>
+    </xsl:call-template>
+  </xsl:variable>
+
+  <xsl:variable name="context">
+    <xsl:choose>
+      <xsl:when test="$autonumber != 0 
+                      and $number-and-title-template != 0
+                      and $xref.with.number.and.title != 0">
+         <xsl:value-of select="'xref-number-and-title'"/>
+      </xsl:when>
+      <xsl:when test="$autonumber != 0 
+                      and $number-template != 0">
+         <xsl:value-of select="'xref-number'"/>
+      </xsl:when>
+      <xsl:otherwise>
+         <xsl:value-of select="'xref'"/>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:call-template name="gentext.template">
+    <xsl:with-param name="context" select="$context"/>
+    <xsl:with-param name="name">
+      <xsl:call-template name="xpath.location"/>
+    </xsl:with-param>
+    <xsl:with-param name="purpose" select="$purpose"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:call-template>
+
+</xsl:template>
+
+
+<!-- ============================================================ -->
+
+<xsl:template match="*" mode="object.title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:variable name="template">
+    <xsl:apply-templates select="." mode="object.title.template"/>
+  </xsl:variable>
+
+<!--
+  <xsl:message>
+    <xsl:text>object.title.markup: </xsl:text>
+    <xsl:value-of select="local-name(.)"/>
+    <xsl:text>: </xsl:text>
+    <xsl:value-of select="$template"/>
+  </xsl:message>
+-->
+
+  <xsl:call-template name="substitute-markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+    <xsl:with-param name="template" select="$template"/>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template match="*" mode="object.title.markup.textonly">
+  <xsl:variable name="title">
+    <xsl:apply-templates select="." mode="object.title.markup"/>
+  </xsl:variable>
+  <xsl:value-of select="$title"/>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template match="*" mode="object.titleabbrev.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+
+  <!-- Just for consistency in template naming -->
+
+  <xsl:apply-templates select="." mode="titleabbrev.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template match="*" mode="object.subtitle.markup">
+  <xsl:variable name="template">
+    <xsl:apply-templates select="." mode="object.subtitle.template"/>
+  </xsl:variable>
+
+  <xsl:call-template name="substitute-markup">
+    <xsl:with-param name="template" select="$template"/>
+  </xsl:call-template>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template match="*" mode="object.xref.markup">
+  <xsl:param name="purpose"/>
+  <xsl:param name="xrefstyle"/>
+  <xsl:param name="referrer"/>
+
+  <xsl:variable name="template">
+    <xsl:choose>
+      <xsl:when test="starts-with(normalize-space($xrefstyle), 'select:')">
+        <xsl:call-template name="make.gentext.template">
+          <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+          <xsl:with-param name="purpose" select="$purpose"/>
+          <xsl:with-param name="referrer" select="$referrer"/>
+        </xsl:call-template>
+      </xsl:when>
+      <xsl:when test="starts-with(normalize-space($xrefstyle), 'template:')">
+        <xsl:value-of select="substring-after(normalize-space($xrefstyle), 'template:')"/>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:apply-templates select="." mode="object.xref.template">
+          <xsl:with-param name="purpose" select="$purpose"/>
+          <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+          <xsl:with-param name="referrer" select="$referrer"/>
+        </xsl:apply-templates>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+<!-- 
+  <xsl:message>
+    <xsl:text>object.xref.markup: </xsl:text>
+    <xsl:value-of select="local-name(.)"/>
+    <xsl:text>(</xsl:text>
+    <xsl:value-of select="$xrefstyle"/>
+    <xsl:text>, </xsl:text>
+    <xsl:value-of select="$purpose"/>
+    <xsl:text>)</xsl:text>
+    <xsl:text>: [</xsl:text>
+    <xsl:value-of select="$template"/>
+    <xsl:text>]</xsl:text>
+  </xsl:message>
+-->
+
+  <xsl:if test="$template = ''">
+    <xsl:message>
+      <xsl:text>object.xref.markup: empty xref template</xsl:text>
+      <xsl:text> for linkend="</xsl:text>
+      <xsl:value-of select="@id"/>
+      <xsl:text>" and @xrefstyle="</xsl:text>
+      <xsl:value-of select="$xrefstyle"/>
+      <xsl:text>"</xsl:text>
+    </xsl:message>
+  </xsl:if>
+
+  <xsl:call-template name="substitute-markup">
+    <xsl:with-param name="purpose" select="$purpose"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+    <xsl:with-param name="template" select="$template"/>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template match="listitem" mode="object.xref.markup">
+  <xsl:choose>
+    <xsl:when test="parent::orderedlist">
+      <xsl:variable name="template">
+        <xsl:apply-templates select="." mode="object.xref.template"/>
+      </xsl:variable>
+      <xsl:call-template name="substitute-markup">
+        <xsl:with-param name="template" select="$template"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:message>
+        <xsl:text>Xref is only supported to listitems in an</xsl:text>
+        <xsl:text> orderedlist: </xsl:text>
+        <xsl:value-of select="@id"/>
+      </xsl:message>
+      <xsl:text>???</xsl:text>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="question" mode="object.xref.markup">
+  <xsl:param name="purpose"/>
+  <xsl:param name="xrefstyle"/>
+  <xsl:param name="referrer"/>
+
+  <xsl:variable name="deflabel">
+    <xsl:choose>
+      <xsl:when test="ancestor-or-self::*[@defaultlabel]">
+        <xsl:value-of select="(ancestor-or-self::*[@defaultlabel])[last()]
+                              /@defaultlabel"/>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:value-of select="$qanda.defaultlabel"/>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:variable name="template">
+    <xsl:choose>
+      <!-- This avoids double Q: Q: in xref when defaultlabel=qanda -->
+      <xsl:when test="$deflabel = 'qanda' and not(label)">%n</xsl:when>
+      <xsl:otherwise>
+        <xsl:apply-templates select="." mode="object.xref.template">
+          <xsl:with-param name="purpose" select="$purpose"/>
+          <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+          <xsl:with-param name="referrer" select="$referrer"/>
+        </xsl:apply-templates>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:call-template name="substitute-markup">
+    <xsl:with-param name="purpose" select="$purpose"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+    <xsl:with-param name="template" select="$template"/>
+  </xsl:call-template>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template name="substitute-markup">
+  <xsl:param name="template" select="''"/>
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:param name="title" select="''"/>
+  <xsl:param name="subtitle" select="''"/>
+  <xsl:param name="label" select="''"/>
+  <xsl:param name="pagenumber" select="''"/>
+  <xsl:param name="purpose"/>
+  <xsl:param name="xrefstyle"/>
+  <xsl:param name="referrer"/>
+
+  <xsl:choose>
+    <xsl:when test="contains($template, '%')">
+      <xsl:value-of select="substring-before($template, '%')"/>
+      <xsl:variable name="candidate"
+             select="substring(substring-after($template, '%'), 1, 1)"/>
+      <xsl:choose>
+        <xsl:when test="$candidate = 't'">
+          <xsl:apply-templates select="." mode="insert.title.markup">
+            <xsl:with-param name="purpose" select="$purpose"/>
+            <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+            <xsl:with-param name="title">
+              <xsl:choose>
+                <xsl:when test="$title != ''">
+                  <xsl:copy-of select="$title"/>
+                </xsl:when>
+                <xsl:otherwise>
+                  <xsl:apply-templates select="." mode="title.markup">
+                    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+                  </xsl:apply-templates>
+                </xsl:otherwise>
+              </xsl:choose>
+            </xsl:with-param>
+          </xsl:apply-templates>
+        </xsl:when>
+        <xsl:when test="$candidate = 's'">
+          <xsl:apply-templates select="." mode="insert.subtitle.markup">
+            <xsl:with-param name="purpose" select="$purpose"/>
+            <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+            <xsl:with-param name="subtitle">
+              <xsl:choose>
+                <xsl:when test="$subtitle != ''">
+                  <xsl:copy-of select="$subtitle"/>
+                </xsl:when>
+                <xsl:otherwise>
+                  <xsl:apply-templates select="." mode="subtitle.markup">
+                    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+                  </xsl:apply-templates>
+                </xsl:otherwise>
+              </xsl:choose>
+            </xsl:with-param>
+          </xsl:apply-templates>
+        </xsl:when>
+        <xsl:when test="$candidate = 'n'">
+          <xsl:apply-templates select="." mode="insert.label.markup">
+            <xsl:with-param name="purpose" select="$purpose"/>
+            <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+            <xsl:with-param name="label">
+              <xsl:choose>
+                <xsl:when test="$label != ''">
+                  <xsl:copy-of select="$label"/>
+                </xsl:when>
+                <xsl:otherwise>
+                  <xsl:apply-templates select="." mode="label.markup"/>
+                </xsl:otherwise>
+              </xsl:choose>
+            </xsl:with-param>
+          </xsl:apply-templates>
+        </xsl:when>
+        <xsl:when test="$candidate = 'p'">
+          <xsl:apply-templates select="." mode="insert.pagenumber.markup">
+            <xsl:with-param name="purpose" select="$purpose"/>
+            <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+            <xsl:with-param name="pagenumber">
+              <xsl:choose>
+                <xsl:when test="$pagenumber != ''">
+                  <xsl:copy-of select="$pagenumber"/>
+                </xsl:when>
+                <xsl:otherwise>
+                  <xsl:apply-templates select="." mode="pagenumber.markup"/>
+                </xsl:otherwise>
+              </xsl:choose>
+            </xsl:with-param>
+          </xsl:apply-templates>
+        </xsl:when>
+        <xsl:when test="$candidate = 'd'">
+          <xsl:apply-templates select="." mode="insert.direction.markup">
+            <xsl:with-param name="purpose" select="$purpose"/>
+            <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+            <xsl:with-param name="direction">
+              <xsl:choose>
+                <xsl:when test="$referrer">
+                  <xsl:variable name="referent-is-below">
+                    <xsl:for-each select="preceding::xref">
+                      <xsl:if test="generate-id(.) = generate-id($referrer)">1</xsl:if>
+                    </xsl:for-each>
+                  </xsl:variable>
+                  <xsl:choose>
+                    <xsl:when test="$referent-is-below = ''">
+                      <xsl:call-template name="gentext">
+                        <xsl:with-param name="key" select="'above'"/>
+                      </xsl:call-template>
+                    </xsl:when>
+                    <xsl:otherwise>
+                      <xsl:call-template name="gentext">
+                        <xsl:with-param name="key" select="'below'"/>
+                      </xsl:call-template>
+                    </xsl:otherwise>
+                  </xsl:choose>
+                </xsl:when>
+                <xsl:otherwise>
+                  <xsl:message>Attempt to use %d in gentext with no referrer!</xsl:message>
+                </xsl:otherwise>
+              </xsl:choose>
+            </xsl:with-param>
+          </xsl:apply-templates>
+        </xsl:when>
+        <xsl:when test="$candidate = '%' ">
+          <xsl:text>%</xsl:text>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:text>%</xsl:text><xsl:value-of select="$candidate"/>
+        </xsl:otherwise>
+      </xsl:choose>
+      <!-- recurse with the rest of the template string -->
+      <xsl:variable name="rest"
+            select="substring($template,
+            string-length(substring-before($template, '%'))+3)"/>
+      <xsl:call-template name="substitute-markup">
+        <xsl:with-param name="template" select="$rest"/>
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+        <xsl:with-param name="title" select="$title"/>
+        <xsl:with-param name="subtitle" select="$subtitle"/>
+        <xsl:with-param name="label" select="$label"/>
+        <xsl:with-param name="pagenumber" select="$pagenumber"/>
+        <xsl:with-param name="purpose" select="$purpose"/>
+        <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+        <xsl:with-param name="referrer" select="$referrer"/>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:value-of select="$template"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template name="make.gentext.template">
+  <xsl:param name="xrefstyle" select="''"/>
+  <xsl:param name="purpose"/>
+  <xsl:param name="referrer"/>
+  <xsl:param name="lang">
+    <xsl:call-template name="l10n.language"/>
+  </xsl:param>
+
+  <!-- parse xrefstyle to get parts -->
+  <xsl:variable name="parts"
+      select="substring-after(normalize-space($xrefstyle), 'select:')"/>
+
+  <xsl:variable name="labeltype">
+    <xsl:choose>
+      <xsl:when test="contains($parts, 'labelnumber')">
+         <xsl:text>labelnumber</xsl:text>
+      </xsl:when>
+      <xsl:when test="contains($parts, 'labelname')">
+         <xsl:text>labelname</xsl:text>
+      </xsl:when>
+      <xsl:when test="contains($parts, 'label')">
+         <xsl:text>label</xsl:text>
+      </xsl:when>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:variable name="titletype">
+    <xsl:choose>
+      <xsl:when test="contains($parts, 'quotedtitle')">
+         <xsl:text>quotedtitle</xsl:text>
+      </xsl:when>
+      <xsl:when test="contains($parts, 'title')">
+         <xsl:text>title</xsl:text>
+      </xsl:when>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:variable name="pagetype">
+    <xsl:choose>
+      <xsl:when test="$insert.xref.page.number = 'no'">
+        <!-- suppress page numbers -->
+      </xsl:when>
+      <xsl:when test="contains($parts, 'nopage')">
+         <xsl:text>nopage</xsl:text>
+      </xsl:when>
+      <xsl:when test="contains($parts, 'pagenumber')">
+         <xsl:text>pagenumber</xsl:text>
+      </xsl:when>
+      <xsl:when test="contains($parts, 'pageabbrev')">
+         <xsl:text>pageabbrev</xsl:text>
+      </xsl:when>
+      <xsl:when test="contains($parts, 'Page')">
+         <xsl:text>Page</xsl:text>
+      </xsl:when>
+      <xsl:when test="contains($parts, 'page')">
+         <xsl:text>page</xsl:text>
+      </xsl:when>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:if test="$labeltype != ''">
+    <xsl:choose>
+      <xsl:when test="$labeltype = 'labelname'">
+        <xsl:call-template name="gentext"/>
+      </xsl:when>
+      <xsl:when test="$labeltype = 'labelnumber'">
+        <xsl:text>%n</xsl:text>
+      </xsl:when>
+      <xsl:when test="$labeltype = 'label'">
+        <xsl:call-template name="gentext.template">
+          <xsl:with-param name="context" select="'xref-number'"/>
+          <xsl:with-param name="name">
+            <xsl:call-template name="xpath.location"/>
+          </xsl:with-param>
+          <xsl:with-param name="purpose" select="$purpose"/>
+          <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+          <xsl:with-param name="referrer" select="$referrer"/>
+        </xsl:call-template>
+      </xsl:when>
+    </xsl:choose>
+
+    <xsl:choose>
+      <xsl:when test="$titletype != ''">
+        <xsl:value-of select="$xref.label-title.separator"/>
+      </xsl:when>
+      <xsl:when test="$pagetype != ''">
+        <xsl:value-of select="$xref.label-page.separator"/>
+      </xsl:when>
+    </xsl:choose>
+  </xsl:if>
+
+  <xsl:if test="$titletype != ''">
+    <xsl:choose>
+      <xsl:when test="$titletype = 'title'">
+        <xsl:text>%t</xsl:text>
+      </xsl:when>
+      <xsl:when test="$titletype = 'quotedtitle'">
+        <xsl:call-template name="gentext.dingbat">
+          <xsl:with-param name="dingbat" select="'startquote'"/>
+        </xsl:call-template>
+        <xsl:text>%t</xsl:text>
+        <xsl:call-template name="gentext.dingbat">
+          <xsl:with-param name="dingbat" select="'endquote'"/>
+        </xsl:call-template>
+      </xsl:when>
+    </xsl:choose>
+
+    <xsl:choose>
+      <xsl:when test="$pagetype != '' and $pagetype != 'nopage'">
+        <xsl:value-of select="$xref.title-page.separator"/>
+      </xsl:when>
+    </xsl:choose>
+  </xsl:if>
+  
+  <xsl:if test="$pagetype != ''">
+    <xsl:choose>
+      <!-- special case: use regular xref template -->
+      <xsl:when test="$pagetype = 'nopage' 
+                      and $labeltype = '' 
+                      and $titletype = ''">
+        <xsl:apply-templates select="." mode="object.xref.template">
+          <xsl:with-param name="purpose" select="$purpose"/>
+          <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+          <xsl:with-param name="referrer" select="$referrer"/>
+        </xsl:apply-templates>
+      </xsl:when>
+      <xsl:when test="$pagetype = 'page'">
+        <xsl:call-template name="gentext.template">
+          <xsl:with-param name="context" select="'xref'"/>
+          <xsl:with-param name="name" select="'page'"/>
+        </xsl:call-template>
+      </xsl:when>
+      <xsl:when test="$pagetype = 'Page'">
+        <xsl:call-template name="gentext.template">
+          <xsl:with-param name="context" select="'xref'"/>
+          <xsl:with-param name="name" select="'Page'"/>
+        </xsl:call-template>
+      </xsl:when>
+      <xsl:when test="$pagetype = 'pageabbrev'">
+        <xsl:call-template name="gentext.template">
+          <xsl:with-param name="context" select="'xref'"/>
+          <xsl:with-param name="name" select="'pageabbrev'"/>
+        </xsl:call-template>
+      </xsl:when>
+      <xsl:when test="$pagetype = 'pagenumber'">
+        <xsl:text>%p</xsl:text>
+      </xsl:when>
+    </xsl:choose>
+
+  </xsl:if>
+
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/he.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/he.xml
new file mode 100644
index 00000000000..4ce5e5a622f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/he.xml
@@ -0,0 +1,444 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="he" english-language-name="Hebrew">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/he.xml -->
+  <l:gentext key="Abstract" text="&#1505;&#1497;&#1499;&#1493;&#1501;"/>
+  <l:gentext key="abstract" text="&#1505;&#1497;&#1499;&#1493;&#1501;"/>
+  <l:gentext key="Answer" text="&#1514;:"/>
+  <l:gentext key="answer" text="&#1514;:"/>
+  <l:gentext key="Appendix" text="&#1504;&#1505;&#1508;&#1495;"/>
+  <l:gentext key="appendix" text="&#1504;&#1505;&#1508;&#1495;"/>
+  <l:gentext key="Article" text="&#1502;&#1488;&#1502;&#1512;"/>
+  <l:gentext key="article" text="&#1502;&#1488;&#1502;&#1512;"/>
+  <l:gentext key="Bibliography" text="&#1489;&#1497;&#1489;&#1500;&#1497;&#1493;&#1490;&#1512;&#1508;&#1497;&#1492;"/>
+  <l:gentext key="bibliography" text="&#1489;&#1497;&#1489;&#1500;&#1497;&#1493;&#1490;&#1512;&#1508;&#1497;&#1492;"/>
+  <l:gentext key="Book" text="&#1505;&#1508;&#1512;"/>
+  <l:gentext key="book" text="&#1505;&#1508;&#1512;"/>
+  <l:gentext key="CAUTION" text="&#1488;&#1494;&#1492;&#1512;&#1492;"/>
+  <l:gentext key="Caution" text="&#1488;&#1494;&#1492;&#1512;&#1492;"/>
+  <l:gentext key="caution" text="&#1488;&#1494;&#1492;&#1512;&#1492;"/>
+  <l:gentext key="Chapter" text="&#1508;&#1512;&#1511;"/>
+  <l:gentext key="chapter" text="&#1508;&#1512;&#1511;"/>
+  <l:gentext key="Colophon" text="&#1511;&#1493;&#1500;&#1493;&#1508;&#1493;&#1503;"/>
+  <l:gentext key="colophon" text="&#1511;&#1493;&#1500;&#1493;&#1508;&#1493;&#1503;"/>
+  <l:gentext key="Copyright" text="&#1494;&#1499;&#1493;&#1497;&#1493;&#1514; &#1497;&#1493;&#1510;&#1512;&#1497;&#1501;"/>
+  <l:gentext key="copyright" text="&#1494;&#1499;&#1493;&#1497;&#1493;&#1514; &#1497;&#1493;&#1510;&#1512;&#1497;&#1501;"/>
+  <l:gentext key="Dedication" text="&#1492;&#1511;&#1491;&#1513;&#1492;"/>
+  <l:gentext key="dedication" text="&#1492;&#1511;&#1491;&#1513;&#1492;"/>
+  <l:gentext key="Edition" text="&#1502;&#1492;&#1491;&#1493;&#1512;&#1492;"/>
+  <l:gentext key="edition" text="&#1502;&#1492;&#1491;&#1493;&#1512;&#1492;"/>
+  <l:gentext key="Equation" text="&#1502;&#1513;&#1493;&#1493;&#1488;&#1492;"/>
+  <l:gentext key="equation" text="&#1502;&#1513;&#1493;&#1493;&#1488;&#1492;"/>
+  <l:gentext key="Example" text="&#1491;&#1493;&#1490;&#1502;&#1492;"/>
+  <l:gentext key="example" text="&#1491;&#1493;&#1490;&#1502;&#1492;"/>
+  <l:gentext key="Figure" text="&#1488;&#1497;&#1493;&#1512;"/>
+  <l:gentext key="figure" text="&#1488;&#1497;&#1493;&#1512;"/>
+  <l:gentext key="Glossary" text="&#1502;&#1497;&#1500;&#1493;&#1503; &#1502;&#1493;&#1504;&#1495;&#1497;&#1501;"/>
+  <l:gentext key="glossary" text="&#1502;&#1497;&#1500;&#1493;&#1503; &#1502;&#1493;&#1504;&#1495;&#1497;&#1501;"/>
+  <l:gentext key="GlossSee" text="&#1512;&#1488;&#1492;"/>
+  <l:gentext key="glosssee" text="&#1512;&#1488;&#1492;"/>
+  <l:gentext key="GlossSeeAlso" text="&#1512;&#1488;&#1492; &#1490;&#1501;"/>
+  <l:gentext key="glossseealso" text="&#1512;&#1488;&#1492; &#1490;&#1501;"/>
+  <l:gentext key="IMPORTANT" text="&#1495;&#1513;&#1493;&#1489;"/>
+  <l:gentext key="important" text="&#1495;&#1513;&#1493;&#1489;"/>
+  <l:gentext key="Important" text="&#1495;&#1513;&#1493;&#1489;"/>
+  <l:gentext key="Index" text="&#1488;&#1497;&#1504;&#1491;&#1511;&#1505;"/>
+  <l:gentext key="index" text="&#1488;&#1497;&#1504;&#1491;&#1511;&#1505;"/>
+  <l:gentext key="ISBN" text="&#1502;&#1505;&#1508;&#1512; &#1505;&#1508;&#1512; &#1505;&#1496;&#1504;&#1491;&#1512;&#1496;&#1497; &#1489;&#1497;&#1504;&#1500;&#1488;&#1493;&#1502;&#1497;"/>
+  <l:gentext key="isbn" text="&#1502;&#1505;&#1508;&#1512; &#1505;&#1508;&#1512; &#1505;&#1496;&#1504;&#1491;&#1512;&#1496;&#1497; &#1489;&#1497;&#1504;&#1500;&#1488;&#1493;&#1502;&#1497;"/>
+  <l:gentext key="LegalNotice" text="&#1492;&#1493;&#1491;&#1506;&#1492; &#1502;&#1513;&#1508;&#1496;&#1497;&#1514;"/>
+  <l:gentext key="legalnotice" text="&#1492;&#1493;&#1491;&#1506;&#1492; &#1502;&#1513;&#1508;&#1496;&#1497;&#1514;"/>
+  <l:gentext key="MsgAud" text="&#1511;&#1492;&#1500; &#1497;&#1506;&#1491;"/>
+  <l:gentext key="msgaud" text="&#1511;&#1492;&#1500; &#1497;&#1506;&#1491;"/>
+  <l:gentext key="MsgLevel" text="&#1512;&#1502;&#1492;"/>
+  <l:gentext key="msglevel" text="&#1512;&#1502;&#1492;"/>
+  <l:gentext key="MsgOrig" text="&#1502;&#1511;&#1493;&#1512;"/>
+  <l:gentext key="msgorig" text="&#1502;&#1511;&#1493;&#1512;"/>
+  <l:gentext key="NOTE" text="&#1513;&#1497;&#1501; &#1500;&#1489;"/>
+  <l:gentext key="Note" text="&#1513;&#1497;&#1501; &#1500;&#1489;"/>
+  <l:gentext key="note" text="&#1513;&#1497;&#1501; &#1500;&#1489;"/>
+  <l:gentext key="Part" text="&#1495;&#1500;&#1511;"/>
+  <l:gentext key="part" text="&#1495;&#1500;&#1511;"/>
+  <l:gentext key="Preface" text="&#1502;&#1489;&#1493;&#1488;"/>
+  <l:gentext key="preface" text="&#1502;&#1489;&#1493;&#1488;"/>
+  <l:gentext key="Procedure" text="&#1492;&#1500;&#1497;&#1498;"/>
+  <l:gentext key="procedure" text="&#1492;&#1500;&#1497;&#1498;"/>
+  <l:gentext key="ProductionSet" text="&#1497;&#1497;&#1510;&#1493;&#1512;"/>
+  <l:gentext key="Published" text="&#1492;&#1493;&#1510;&#1488; &#1500;&#1488;&#1493;&#1512;"/>
+  <l:gentext key="published" text="&#1492;&#1493;&#1510;&#1488; &#1500;&#1488;&#1493;&#1512;"/>
+  <l:gentext key="Question" text="&#1513;:"/>
+  <l:gentext key="question" text="&#1513;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#1502;&#1512;&#1488;&#1492; &#1502;&#1511;&#1493;&#1501;"/>
+  <l:gentext key="reference" text="&#1502;&#1512;&#1488;&#1492; &#1502;&#1511;&#1493;&#1501;"/>
+  <l:gentext key="RefName" text="&#1513;&#1501;"/>
+  <l:gentext key="refname" text="&#1513;&#1501;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#1514;&#1502;&#1510;&#1497;&#1514;"/>
+  <l:gentext key="refsynopsisdiv" text="&#1514;&#1502;&#1510;&#1497;&#1514;"/>
+  <l:gentext key="RevHistory" text="&#1492;&#1497;&#1505;&#1496;&#1493;&#1512;&#1497;&#1497;&#1514; &#1490;&#1497;&#1512;&#1505;&#1488;&#1493;&#1514;"/>
+  <l:gentext key="revhistory" text="&#1492;&#1497;&#1505;&#1496;&#1493;&#1512;&#1497;&#1497;&#1514; &#1490;&#1497;&#1512;&#1505;&#1488;&#1493;&#1514;"/>
+  <l:gentext key="revision" text="&#1490;&#1497;&#1512;&#1505;&#1492;"/>
+  <l:gentext key="Revision" text="&#1490;&#1497;&#1512;&#1505;&#1492;"/>
+  <l:gentext key="sect1" text="&#1505;&#1506;&#1497;&#1507;"/>
+  <l:gentext key="sect2" text="&#1505;&#1506;&#1497;&#1507;"/>
+  <l:gentext key="sect3" text="&#1505;&#1506;&#1497;&#1507;"/>
+  <l:gentext key="sect4" text="&#1505;&#1506;&#1497;&#1507;"/>
+  <l:gentext key="sect5" text="&#1505;&#1506;&#1497;&#1507;"/>
+  <l:gentext key="section" text="&#1505;&#1506;&#1497;&#1507;"/>
+  <l:gentext key="Section" text="&#1505;&#1506;&#1497;&#1507;"/>
+  <l:gentext key="See" text="&#1512;&#1488;&#1492;"/>
+  <l:gentext key="see" text="&#1512;&#1488;&#1492;"/>
+  <l:gentext key="SeeAlso" text="&#1512;&#1488;&#1492; &#1490;&#1501;"/>
+  <l:gentext key="seealso" text="&#1512;&#1488;&#1492; &#1490;&#1501;"/>
+  <l:gentext key="Seealso" text="&#1512;&#1488;&#1492; &#1490;&#1501;"/>
+  <l:gentext key="set" text="&#1505;&#1497;&#1491;&#1512;&#1492;"/>
+  <l:gentext key="Set" text="&#1505;&#1497;&#1491;&#1512;&#1492;"/>
+  <l:gentext key="setindex" text="&#1488;&#1497;&#1504;&#1511;&#1491;&#1511;&#1505; &#1505;&#1491;&#1512;&#1493;&#1514;"/>
+  <l:gentext key="SetIndex" text="&#1488;&#1497;&#1504;&#1491;&#1511;&#1505; &#1505;&#1491;&#1512;&#1493;&#1514;"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="&#1508;&#1505; &#1510;&#1491;&#1491;&#1497;"/>
+  <l:gentext key="step" text="&#1510;&#1506;&#1491;"/>
+  <l:gentext key="Step" text="&#1510;&#1506;&#1491;"/>
+  <l:gentext key="Table" text="&#1496;&#1489;&#1500;&#1492;"/>
+  <l:gentext key="table" text="&#1496;&#1489;&#1500;&#1492;"/>
+  <l:gentext key="tip" text="&#1506;&#1510;&#1492;"/>
+  <l:gentext key="TIP" text="&#1506;&#1510;&#1492;"/>
+  <l:gentext key="Tip" text="&#1506;&#1510;&#1492;"/>
+  <l:gentext key="Warning" text="&#1488;&#1494;&#1492;&#1512;&#1492;"/>
+  <l:gentext key="warning" text="&#1488;&#1494;&#1492;&#1512;&#1492;"/>
+  <l:gentext key="WARNING" text="&#1488;&#1494;&#1492;&#1512;&#1492;"/>
+  <l:gentext key="and" text="&#1493;"/>
+  <l:gentext key="by" text="&#1502;&#1488;&#1514;"/>
+  <l:gentext key="Edited" text="&#1504;&#1506;&#1512;&#1498;"/>
+  <l:gentext key="edited" text="&#1504;&#1506;&#1512;&#1498;"/>
+  <l:gentext key="Editedby" text="&#1504;&#1506;&#1512;&#1498; &#1506;&#1500; &#1497;&#1491;&#1497;"/>
+  <l:gentext key="editedby" text="&#1504;&#1506;&#1512;&#1498; &#1506;&#1500; &#1497;&#1491;&#1497;"/>
+  <l:gentext key="in" text="&#1489;"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="&#1502;&#1512;&#1499;&#1497;&#1489; &#1513;&#1488;&#1497;&#1504;&#1493; &#1511;&#1497;&#1497;&#1501;"/>
+  <l:gentext key="notes" text="&#1492;&#1506;&#1512;&#1493;&#1514;"/>
+  <l:gentext key="Notes" text="&#1492;&#1506;&#1512;&#1493;&#1514;"/>
+  <l:gentext key="Pgs" text="&#1506;&#1502;&#1493;&#1491;&#1497;&#1501;"/>
+  <l:gentext key="pgs" text="&#1506;&#1502;&#1493;&#1491;&#1497;&#1501;"/>
+  <l:gentext key="Revisedby" text="&#1492;&#1493;&#1490;&#1492; &#1506;&#1500; &#1497;&#1491;&#1497;: "/>
+  <l:gentext key="revisedby" text="&#1492;&#1493;&#1490;&#1492; &#1506;&#1500; &#1497;&#1491;&#1497;: "/>
+  <l:gentext key="TableNotes" text="&#1492;&#1506;&#1512;&#1493;&#1514;"/>
+  <l:gentext key="tablenotes" text="&#1492;&#1506;&#1512;&#1493;&#1514;"/>
+  <l:gentext key="TableofContents" text="&#1514;&#1493;&#1499;&#1503; &#1492;&#1506;&#1504;&#1497;&#1497;&#1504;&#1497;&#1501;"/>
+  <l:gentext key="tableofcontents" text="&#1514;&#1493;&#1499;&#1503; &#1492;&#1506;&#1504;&#1497;&#1497;&#1504;&#1497;&#1501;"/>
+  <l:gentext key="unexpectedelementname" text="&#1513;&#1501; &#1502;&#1512;&#1499;&#1497;&#1489; &#1489;&#1500;&#1514;&#1497; &#1510;&#1508;&#1493;&#1497;"/>
+  <l:gentext key="unsupported" text="&#1500;&#1488; &#1504;&#1514;&#1502;&#1498;"/>
+  <l:gentext key="xrefto" text="&#1492;&#1514;&#1497;&#1497;&#1495;&#1505;&#1493;&#1514; &#1510;&#1493;&#1500;&#1489;&#1514; &#1488;&#1500;"/>
+  <l:gentext key="listofequations" text="&#1512;&#1513;&#1497;&#1502;&#1514; &#1502;&#1513;&#1493;&#1493;&#1488;&#1493;&#1514;"/>
+  <l:gentext key="ListofEquations" text="&#1512;&#1513;&#1497;&#1502;&#1514; &#1502;&#1513;&#1493;&#1493;&#1488;&#1493;&#1514;"/>
+  <l:gentext key="ListofExamples" text="&#1512;&#1513;&#1497;&#1502;&#1514; &#1491;&#1493;&#1490;&#1502;&#1488;&#1493;&#1514;"/>
+  <l:gentext key="listofexamples" text="&#1512;&#1513;&#1497;&#1502;&#1514; &#1491;&#1493;&#1490;&#1502;&#1488;&#1493;&#1514;"/>
+  <l:gentext key="ListofFigures" text="&#1512;&#1513;&#1497;&#1502;&#1514; &#1488;&#1497;&#1493;&#1512;&#1497;&#1501;"/>
+  <l:gentext key="listoffigures" text="&#1512;&#1513;&#1497;&#1502;&#1514; &#1488;&#1497;&#1493;&#1512;&#1497;&#1501;"/>
+  <l:gentext key="listoftables" text="&#1512;&#1513;&#1497;&#1502;&#1514; &#1496;&#1489;&#1500;&#1488;&#1493;&#1514;"/>
+  <l:gentext key="ListofTables" text="&#1512;&#1513;&#1497;&#1502;&#1514; &#1496;&#1489;&#1500;&#1488;&#1493;&#1514;"/>
+  <l:gentext key="ListofUnknown" text="&#1512;&#1513;&#1497;&#1502;&#1492; &#1513;&#1500; &#1502;&#1512;&#1499;&#1497;&#1489;&#1497;&#1501; &#1500;&#1488; &#1497;&#1491;&#1493;&#1506;&#1497;&#1501;"/>
+  <l:gentext key="listofunknown" text="&#1512;&#1513;&#1497;&#1502;&#1492; &#1513;&#1500; &#1502;&#1512;&#1499;&#1497;&#1489;&#1497;&#1501; &#1500;&#1488; &#1497;&#1491;&#1493;&#1506;&#1497;&#1501;"/>
+  <l:gentext key="nav-home" text="&#1512;&#1488;&#1513;&#1497;"/>
+  <l:gentext key="nav-next" text="&#1492;&#1489;&#1488;"/>
+  <l:gentext key="nav-next-sibling" text="&#1491;&#1500;&#1490; &#1500;&#1505;&#1493;&#1507;"/>
+  <l:gentext key="nav-prev" text="&#1492;&#1511;&#1493;&#1491;&#1501;"/>
+  <l:gentext key="nav-prev-sibling" text="&#1495;&#1494;&#1493;&#1512; &#1500;&#1492;&#1514;&#1495;&#1500;&#1492;"/>
+  <l:gentext key="nav-up" text="&#1500;&#1502;&#1506;&#1500;&#1492;"/>
+  <l:gentext key="sectioncalled" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488;"/>
+  <l:gentext key="Draft" text="&#1496;&#1497;&#1493;&#1496;&#1492;"/>
+  <l:gentext key="above" text="&#1500;&#1502;&#1506;&#1500;&#1492;"/>
+  <l:gentext key="below" text="&#1500;&#1502;&#1496;&#1492;"/>
+  <l:gentext key="index symbols" text="&#1505;&#1502;&#1500;&#1497;&#1501;"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/he.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#1504;&#1505;&#1508;&#1495; %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#1508;&#1512;&#1511; %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#1502;&#1513;&#1493;&#1493;&#1488;&#1492; %n. %t"/>
+    <l:template name="example" text="&#1491;&#1493;&#1490;&#1502;&#1492; %n. %t"/>
+    <l:template name="figure" text="&#1488;&#1497;&#1493;&#1512; %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#1495;&#1500;&#1511; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#1492;&#1500;&#1497;&#1498; %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="&#1497;&#1497;&#1510;&#1493;&#1512; %n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#1496;&#1489;&#1500;&#1492; %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#1504;&#1505;&#1508;&#1495; %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="&#1508;&#1512;&#1511; %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#1514;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#1513;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#1513;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#1514;:&#160;%n"/>
+    <l:template name="appendix" text="&#1504;&#1505;&#1508;&#1495;&#160;%n"/>
+    <l:template name="bridgehead" text="&#1505;&#1506;&#1497;&#1507;&#160;%n"/>
+    <l:template name="chapter" text="&#1508;&#1512;&#1511;&#160;%n"/>
+    <l:template name="equation" text="&#1502;&#1513;&#1493;&#1493;&#1488;&#1492;&#160;%n"/>
+    <l:template name="example" text="&#1491;&#1493;&#1490;&#1502;&#1492;&#160;%n"/>
+    <l:template name="figure" text="&#1488;&#1497;&#1493;&#1512;&#160;%n"/>
+    <l:template name="part" text="&#1495;&#1500;&#1511;&#160;%n"/>
+    <l:template name="procedure" text="&#1492;&#1500;&#1497;&#1498;&#160;%n"/>
+    <l:template name="productionset" text="&#1497;&#1497;&#1510;&#1493;&#1512;&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#1513;:&#160;%n"/>
+    <l:template name="question" text="&#1513;:&#160;%n"/>
+    <l:template name="sect1" text="&#1505;&#1506;&#1497;&#1507;&#160;%n"/>
+    <l:template name="sect2" text="&#1505;&#1506;&#1497;&#1507;&#160;%n"/>
+    <l:template name="sect3" text="&#1505;&#1506;&#1497;&#1507;&#160;%n"/>
+    <l:template name="sect4" text="&#1505;&#1506;&#1497;&#1507;&#160;%n"/>
+    <l:template name="sect5" text="&#1505;&#1506;&#1497;&#1507;&#160;%n"/>
+    <l:template name="section" text="&#1505;&#1506;&#1497;&#1507;&#160;%n"/>
+    <l:template name="table" text="&#1496;&#1489;&#1500;&#1492;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#1504;&#1505;&#1508;&#1495;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#1505;&#1506;&#1497;&#1507;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="&#1508;&#1512;&#1511;&#160;%n, %t"/>
+    <l:template name="equation" text="&#1502;&#1513;&#1493;&#1493;&#1488;&#1492;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="&#1491;&#1493;&#1490;&#1502;&#1492;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="&#1488;&#1497;&#1493;&#1512;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="&#1495;&#1500;&#1511;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="&#1492;&#1500;&#1497;&#1498;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="&#1497;&#1497;&#1510;&#1493;&#1512;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#1505;&#1506;&#1497;&#1507;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#1505;&#1506;&#1497;&#1507;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#1505;&#1506;&#1497;&#1507;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#1505;&#1506;&#1497;&#1507;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#1505;&#1506;&#1497;&#1507;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#1505;&#1506;&#1497;&#1507;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#1492;&#1505;&#1506;&#1497;&#1507; &#1513;&#1504;&#1511;&#1512;&#1488; &#8220;%t&#8221;"/>
+    <l:template name="table" text="&#1496;&#1489;&#1500;&#1492;&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#1493; "/>
+    <l:template name="seplast" text=", &#1493; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#1512;&#1488;&#1492; "/>
+    <l:template name="seealso" text="&#1512;&#1488;&#1492; &#1490;&#1501; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#1511;&#1492;&#1500; &#1497;&#1506;&#1491;: "/>
+    <l:template name="MsgLevel" text="&#1512;&#1502;&#1492;: "/>
+    <l:template name="MsgOrig" text="&#1502;&#1511;&#1493;&#1512;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x040d Hebrew (ISRAEL)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/hr.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/hr.xml
new file mode 100644
index 00000000000..c643646d267
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/hr.xml
@@ -0,0 +1,495 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="hr" english-language-name="Croatian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/hr.xml -->
+  <l:gentext key="Abstract" text="Sa&#382;etak"/>
+  <l:gentext key="abstract" text="Sa&#382;etak"/>
+  <l:gentext key="Answer" text="Odgovor:"/>
+  <l:gentext key="answer" text="Odgovor:"/>
+  <l:gentext key="Appendix" text="Dodatak"/>
+  <l:gentext key="appendix" text="dodatak"/>
+  <l:gentext key="Article" text="&#268;lanak"/>
+  <l:gentext key="article" text="&#268;lanak"/>
+  <l:gentext key="Bibliography" text="Literatura"/>
+  <l:gentext key="bibliography" text="Literatura"/>
+  <l:gentext key="Book" text="Knjiga"/>
+  <l:gentext key="book" text="Knjiga"/>
+  <l:gentext key="CAUTION" text="OPREZ"/>
+  <l:gentext key="Caution" text="Oprez"/>
+  <l:gentext key="caution" text="Oprez"/>
+  <l:gentext key="Chapter" text="Poglavlje"/>
+  <l:gentext key="chapter" text="poglavlje"/>
+  <l:gentext key="Colophon" text="Impresum"/>
+  <l:gentext key="colophon" text="Impresum"/>
+  <l:gentext key="Copyright" text="Autorska prava"/>
+  <l:gentext key="copyright" text="Autorska prava"/>
+  <l:gentext key="Dedication" text="Posveta"/>
+  <l:gentext key="dedication" text="Posveta"/>
+  <l:gentext key="Edition" text="Izdanje"/>
+  <l:gentext key="edition" text="Izdanje"/>
+  <l:gentext key="Equation" text="Jednad&#382;ba"/>
+  <l:gentext key="equation" text="Jednad&#382;ba"/>
+  <l:gentext key="Example" text="Primjer"/>
+  <l:gentext key="example" text="Primjer"/>
+  <l:gentext key="Figure" text="Slika"/>
+  <l:gentext key="figure" text="Slika"/>
+  <l:gentext key="Glossary" text="Rje&#269;nik"/>
+  <l:gentext key="glossary" text="Rje&#269;nik"/>
+  <l:gentext key="GlossSee" text="Vidi"/>
+  <l:gentext key="glosssee" text="Vidi"/>
+  <l:gentext key="GlossSeeAlso" text="Vidi i"/>
+  <l:gentext key="glossseealso" text="Vidi i"/>
+  <l:gentext key="IMPORTANT" text="VA&#381;NO"/>
+  <l:gentext key="important" text="Va&#382;no"/>
+  <l:gentext key="Important" text="Va&#382;no"/>
+  <l:gentext key="Index" text="Kazalo"/>
+  <l:gentext key="index" text="Kazalo"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Pravne odredbe"/>
+  <l:gentext key="legalnotice" text="Pravne odredbe"/>
+  <l:gentext key="MsgAud" text="Primatelji"/>
+  <l:gentext key="msgaud" text="Primatelji"/>
+  <l:gentext key="MsgLevel" text="Razina"/>
+  <l:gentext key="msglevel" text="Razina"/>
+  <l:gentext key="MsgOrig" text="Izvor"/>
+  <l:gentext key="msgorig" text="Izvor"/>
+  <l:gentext key="NOTE" text="BILJE&#352;KA"/>
+  <l:gentext key="Note" text="Bilje&#353;ka"/>
+  <l:gentext key="note" text="Bilje&#353;ka"/>
+  <l:gentext key="Part" text="Dio"/>
+  <l:gentext key="part" text="Dio"/>
+  <l:gentext key="Preface" text="Predgovor"/>
+  <l:gentext key="preface" text="Predgovor"/>
+  <l:gentext key="Procedure" text="Postupak"/>
+  <l:gentext key="procedure" text="Postupak"/>
+  <l:gentext key="ProductionSet" text="Produkcija"/>
+  <l:gentext key="Published" text="Objavljeno"/>
+  <l:gentext key="published" text="Objavljeno"/>
+  <l:gentext key="Question" text="Pitanje:"/>
+  <l:gentext key="question" text="Pitanje:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Referenca"/>
+  <l:gentext key="reference" text="Referenca"/>
+  <l:gentext key="RefName" text="Ime"/>
+  <l:gentext key="refname" text="Ime"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Pregled"/>
+  <l:gentext key="refsynopsisdiv" text="Pregled"/>
+  <l:gentext key="RevHistory" text="Povijest preinaka"/>
+  <l:gentext key="revhistory" text="Povijest preinaka"/>
+  <l:gentext key="revision" text="Preinaka"/>
+  <l:gentext key="Revision" text="Preinaka"/>
+  <l:gentext key="sect1" text="Odjeljak"/>
+  <l:gentext key="sect2" text="Odjeljak"/>
+  <l:gentext key="sect3" text="Odjeljak"/>
+  <l:gentext key="sect4" text="Odjeljak"/>
+  <l:gentext key="sect5" text="Odjeljak"/>
+  <l:gentext key="section" text="Odjeljak"/>
+  <l:gentext key="Section" text="Odjeljak"/>
+  <l:gentext key="see" text="vidi"/>
+  <l:gentext key="seealso" text="vidi i"/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="setindex" text="Kazalo seta"/>
+  <l:gentext key="SetIndex" text="Kazalo seta"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="step" text="korak"/>
+  <l:gentext key="Step" text="Korak"/>
+  <l:gentext key="Table" text="Tablica"/>
+  <l:gentext key="table" text="Tablica"/>
+  <l:gentext key="tip" text="Savjet"/>
+  <l:gentext key="TIP" text="SAVJET"/>
+  <l:gentext key="Tip" text="Savjet"/>
+  <l:gentext key="Warning" text="Upozorenje"/>
+  <l:gentext key="warning" text="Upozorenje"/>
+  <l:gentext key="WARNING" text="UPOZORENJE"/>
+  <l:gentext key="and" text="i"/>
+  <l:gentext key="by" text="po"/>
+  <l:gentext key="Edited" text="Uredio/la"/>
+  <l:gentext key="edited" text="Uredio/la"/>
+  <l:gentext key="Editedby" text="Uredio/la"/>
+  <l:gentext key="editedby" text="Uredio/la"/>
+  <l:gentext key="in" text="u"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="nepostoje&#263;i element"/>
+  <l:gentext key="notes" text="Bilje&#353;ke"/>
+  <l:gentext key="Notes" text="Bilje&#353;ke"/>
+  <l:gentext key="Pgs" text="Str."/>
+  <l:gentext key="pgs" text="Str."/>
+  <l:gentext key="Revisedby" text="Promijenjeno po: "/>
+  <l:gentext key="revisedby" text="Promijenjeno po: "/>
+  <l:gentext key="TableNotes" text="Napomene"/>
+  <l:gentext key="tablenotes" text="Napomene"/>
+  <l:gentext key="TableofContents" text="Sadr&#382;aj"/>
+  <l:gentext key="tableofcontents" text="Sadr&#382;aj"/>
+  <l:gentext key="unexpectedelementname" text="Neo&#269;ekivano ime elementa"/>
+  <l:gentext key="unsupported" text="nepodr&#382;ano"/>
+  <l:gentext key="xrefto" text="xref za"/>
+  <l:gentext key="listofequations" text="Popis jednad&#382;bi"/>
+  <l:gentext key="ListofEquations" text="Popis jednad&#382;bi"/>
+  <l:gentext key="ListofExamples" text="Popis primjera"/>
+  <l:gentext key="listofexamples" text="Popis primjera"/>
+  <l:gentext key="ListofFigures" text="Popis slika"/>
+  <l:gentext key="listoffigures" text="Popis slika"/>
+  <l:gentext key="ListofProcedures" text="Popis postupaka"/>
+  <l:gentext key="listofprocedures" text="Popis postupaka"/>
+  <l:gentext key="listoftables" text="Popis tablica"/>
+  <l:gentext key="ListofTables" text="Popis tablica "/>
+  <l:gentext key="ListofUnknown" text="Popis nepoznanica"/>
+  <l:gentext key="listofunknown" text="Popis nepoznanica"/>
+  <l:gentext key="nav-home" text="Po&#269;etak"/>
+  <l:gentext key="nav-next" text="Naprijed"/>
+  <l:gentext key="nav-next-sibling" text="Sko&#269;i unaprijed"/>
+  <l:gentext key="nav-prev" text="Natrag"/>
+  <l:gentext key="nav-prev-sibling" text="Sko&#269;i unatrag"/>
+  <l:gentext key="nav-up" text="Gore"/>
+  <l:gentext key="nav-toc" text="Sadr&#382;aj"/>
+  <l:gentext key="Draft" text="Nacrt"/>
+  <l:gentext key="above" text="iznad"/>
+  <l:gentext key="below" text="ispod"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="index symbols" text="Oznake"/>
+  <l:gentext key="lowercase.alpha" text="abc&#269;&#263;d&#273;efghijklmnopqrs&#353;tuvwxyz&#382;"/>
+  <l:gentext key="uppercase.alpha" text="ABC&#268;&#262;D&#272;EFGHIJKLMNOPQRS&#352;TUVWXYZ&#381;"/>
+  <l:gentext key="hyphenation-character" text="&#8208;"/>
+  <l:gentext key="hyphenation-push-character-count" text="2"/>
+  <l:gentext key="hyphenation-remain-character-count" text="2"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/hr.xml -->
+  <l:dingbat key="startquote" text="&#8222;"/>
+  <l:dingbat key="endquote" text="&#8220;"/>
+  <l:dingbat key="nestedstartquote" text="&#8218;"/>
+  <l:dingbat key="nestedendquote" text="&#8216;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Dodatak&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Poglavlje&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Jednad&#382;ba&#160;%n.&#160;%t"/>
+    <l:template name="example" text="Primjer&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="Slika&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Dio&#160;%n.&#160;%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Postupak&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Produkcija&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tablica&#160;%n.&#160;%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Dodatak&#160;%n.&#160;%t"/>
+    <l:template name="article/appendix" text="%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="Poglavlje&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Odgovor:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Pitanje:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Pitanje:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="refsection" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="refsect1" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="refsect2" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="refsect3" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="sect1" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="sect2" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="sect3" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="sect4" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="sect5" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="section" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="simplesect" text="the section called &#8222;%t&#8220;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Odgovor:&#160;%n"/>
+    <l:template name="appendix" text="Dodatak&#160;%n"/>
+    <l:template name="bridgehead" text="Odjeljak&#160;%n"/>
+    <l:template name="chapter" text="Poglavlje&#160;%n"/>
+    <l:template name="equation" text="Jednad&#382;ba&#160;%n"/>
+    <l:template name="example" text="Primjer&#160;%n"/>
+    <l:template name="figure" text="Slika&#160;%n"/>
+    <l:template name="part" text="Dio&#160;%n"/>
+    <l:template name="procedure" text="Postupak&#160;%n"/>
+    <l:template name="productionset" text="Produkcija&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Pitanje:&#160;%n"/>
+    <l:template name="question" text="Pitanje:&#160;%n"/>
+    <l:template name="sect1" text="Odjeljak&#160;%n"/>
+    <l:template name="sect2" text="Odjeljak&#160;%n"/>
+    <l:template name="sect3" text="Odjeljak&#160;%n"/>
+    <l:template name="sect4" text="Odjeljak&#160;%n"/>
+    <l:template name="sect5" text="Odjeljak&#160;%n"/>
+    <l:template name="section" text="Odjeljak&#160;%n"/>
+    <l:template name="table" text="Tablica&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Dodatak&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Odjeljak&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="chapter" text="Poglavlje&#160;%n, %t"/>
+    <l:template name="equation" text="Jednad&#382;ba&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="example" text="Primjer&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="figure" text="Slika&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="part" text="Dio&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="procedure" text="Postupak&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="productionset" text="Produkcija&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="refsect1" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="refsect2" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="refsect3" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="refsection" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="sect1" text="Odjeljak&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="sect2" text="Odjeljak&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="sect3" text="Odjeljak&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="sect4" text="Odjeljak&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="sect5" text="Odjeljak&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="section" text="Odjeljak&#160;%n, &#8222;%t&#8220;"/>
+    <l:template name="simplesect" text="the section called &#8222;%t&#8220;"/>
+    <l:template name="table" text="Tablica&#160;%n, &#8222;%t&#8220;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" i "/>
+    <l:template name="seplast" text=", i "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Vidi "/>
+    <l:template name="seealso" text="Vidi i "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Primatelji: "/>
+    <l:template name="MsgLevel" text="Razina: "/>
+    <l:template name="MsgOrig" text="Izvor: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="m/d/Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="Sije&#269;anj"/>
+    <l:template name="February" text="Velja&#269;a"/>
+    <l:template name="March" text="O&#382;ujak"/>
+    <l:template name="April" text="Travanj"/>
+    <l:template name="May" text="Svibanj"/>
+    <l:template name="June" text="Lipanj"/>
+    <l:template name="July" text="Srpanj"/>
+    <l:template name="August" text="Kolovoz"/>
+    <l:template name="September" text="Rujan"/>
+    <l:template name="October" text="Listopad"/>
+    <l:template name="November" text="Studeni"/>
+    <l:template name="December" text="Prosinac"/>
+    <l:template name="Monday" text="Ponedjeljak"/>
+    <l:template name="Tuesday" text="Utorak"/>
+    <l:template name="Wednesday" text="Srijeda"/>
+    <l:template name="Thursday" text="&#268;etvrtak"/>
+    <l:template name="Friday" text="Petak"/>
+    <l:template name="Saturday" text="Subota"/>
+    <l:template name="Sunday" text="Nedjelja"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="Sij"/>
+    <l:template name="Feb" text="Velj"/>
+    <l:template name="Mar" text="O&#382;u"/>
+    <l:template name="Apr" text="Tra"/>
+    <l:template name="May" text="Svi"/>
+    <l:template name="Jun" text="Lip"/>
+    <l:template name="Jul" text="Srp"/>
+    <l:template name="Aug" text="Kol"/>
+    <l:template name="Sep" text="Ruj"/>
+    <l:template name="Oct" text="Lis"/>
+    <l:template name="Nov" text="Stu"/>
+    <l:template name="Dec" text="Pro"/>
+    <l:template name="Mon" text="Pon"/>
+    <l:template name="Tue" text="Uto"/>
+    <l:template name="Wed" text="Sri"/>
+    <l:template name="Thu" text="&#268;et"/>
+    <l:template name="Fri" text="Pet"/>
+    <l:template name="Sat" text="Sub"/>
+    <l:template name="Sun" text="Ned"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x041a Croatian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/hu.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/hu.xml
new file mode 100644
index 00000000000..24db854d76f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/hu.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="hu" english-language-name="Hungarian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/hu.xml -->
+  <l:gentext key="Abstract" text="Kivonat"/>
+  <l:gentext key="abstract" text="kivonat"/>
+  <l:gentext key="Answer" text="V:"/>
+  <l:gentext key="answer" text="v:"/>
+  <l:gentext key="Appendix" text="F&#252;ggel&#233;k"/>
+  <l:gentext key="appendix" text="f&#252;ggel&#233;k"/>
+  <l:gentext key="Article" text="Cikk"/>
+  <l:gentext key="article" text="cikk"/>
+  <l:gentext key="Bibliography" text="Irodalomjegyz&#233;k"/>
+  <l:gentext key="bibliography" text="irodalomjegyz&#233;k"/>
+  <l:gentext key="Book" text="K&#246;nyv"/>
+  <l:gentext key="book" text="k&#246;nyv"/>
+  <l:gentext key="CAUTION" text="FIGYELEM"/>
+  <l:gentext key="Caution" text="Figyelem"/>
+  <l:gentext key="caution" text="figyelem"/>
+  <l:gentext key="Chapter" text="Fejezet"/>
+  <l:gentext key="chapter" text="fejezet"/>
+  <l:gentext key="Colophon" text="V&#233;gsz&#243;"/>
+  <l:gentext key="colophon" text="v&#233;gsz&#243;"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="copyright"/>
+  <l:gentext key="Dedication" text="Aj&#225;nl&#225;s"/>
+  <l:gentext key="dedication" text="aj&#225;nl&#225;s"/>
+  <l:gentext key="Edition" text="Kiad&#225;s"/>
+  <l:gentext key="edition" text="kiad&#225;s"/>
+  <l:gentext key="Equation" text="Egyenlet"/>
+  <l:gentext key="equation" text="egyenlet"/>
+  <l:gentext key="Example" text="P&#233;lda"/>
+  <l:gentext key="example" text="p&#233;lda"/>
+  <l:gentext key="Figure" text="&#193;bra"/>
+  <l:gentext key="figure" text="&#225;bra"/>
+  <l:gentext key="Glossary" text="Sz&#243;jegyz&#233;k"/>
+  <l:gentext key="glossary" text="sz&#243;jegyz&#233;k"/>
+  <l:gentext key="GlossSee" text="L&#225;sd"/>
+  <l:gentext key="glosssee" text="l&#225;sd"/>
+  <l:gentext key="GlossSeeAlso" text="L&#225;sd m&#233;g"/>
+  <l:gentext key="glossseealso" text="l&#225;sd m&#233;g"/>
+  <l:gentext key="IMPORTANT" text="FONTOS"/>
+  <l:gentext key="Important" text="Fontos"/>
+  <l:gentext key="important" text="fontos"/>
+  <l:gentext key="Index" text="T&#225;rgymutat&#243;"/>
+  <l:gentext key="index" text="t&#225;rgymutat&#243;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="isbn"/>
+  <l:gentext key="LegalNotice" text="Jogi k&#246;zlem&#233;ny"/>
+  <l:gentext key="legalnotice" text="jogi k&#246;zlem&#233;ny"/>
+  <l:gentext key="MsgAud" text="C&#233;lk&#246;z&#246;ns&#233;g"/>
+  <l:gentext key="msgaud" text="c&#233;lk&#246;z&#246;ns&#233;g"/>
+  <l:gentext key="MsgLevel" text="Szint"/>
+  <l:gentext key="msglevel" text="szint"/>
+  <l:gentext key="MsgOrig" text="Eredet"/>
+  <l:gentext key="msgorig" text="eredet"/>
+  <l:gentext key="NOTE" text="MEGJEGYZ&#201;S"/>
+  <l:gentext key="Note" text="Megjegyz&#233;s"/>
+  <l:gentext key="note" text="megjegyz&#233;s"/>
+  <l:gentext key="Part" text="R&#233;sz"/>
+  <l:gentext key="part" text="r&#233;sz"/>
+  <l:gentext key="Preface" text="El&#337;sz&#243;"/>
+  <l:gentext key="preface" text="el&#337;sz&#243;"/>
+  <l:gentext key="Procedure" text="Elj&#225;r&#225;s"/>
+  <l:gentext key="procedure" text="elj&#225;r&#225;s"/>
+  <l:gentext key="ProductionSet" text="Elemcsoport"/>
+  <l:gentext key="Published" text="Megjelent"/>
+  <l:gentext key="published" text="megjelent"/>
+  <l:gentext key="Question" text="K:"/>
+  <l:gentext key="question" text="k:"/>
+  <l:gentext key="RefEntry" text="Bejegyz&#233;s"/>
+  <l:gentext key="refentry" text="bejegyz&#233;s"/>
+  <l:gentext key="Reference" text="Referencia"/>
+  <l:gentext key="reference" text="referencia"/>
+  <l:gentext key="RefName" text="N&#233;v"/>
+  <l:gentext key="refname" text="n&#233;v"/>
+  <l:gentext key="RefSection" text="Szakasz"/>
+  <l:gentext key="refsection" text="szakasz"/>
+  <l:gentext key="RefSynopsisDiv" text="&#193;ttekint&#233;s"/>
+  <l:gentext key="refsynopsisdiv" text="&#225;ttekint&#233;s"/>
+  <l:gentext key="RevHistory" text="Verzi&#243;t&#246;rt&#233;net"/>
+  <l:gentext key="revhistory" text="verzi&#243;t&#246;rt&#233;net"/>
+  <l:gentext key="Revision" text="Verzi&#243;"/>
+  <l:gentext key="revision" text="verzi&#243;"/>
+  <l:gentext key="sect1" text="Szakasz"/>
+  <l:gentext key="sect2" text="Szakasz"/>
+  <l:gentext key="sect3" text="Szakasz"/>
+  <l:gentext key="sect4" text="Szakasz"/>
+  <l:gentext key="sect5" text="Szakasz"/>
+  <l:gentext key="Section" text="Szakasz"/>
+  <l:gentext key="section" text="szakasz"/>
+  <l:gentext key="See" text="L&#225;sd"/>
+  <l:gentext key="see" text="l&#225;sd"/>
+  <l:gentext key="SeeAlso" text="L&#225;sd m&#233;g"/>
+  <l:gentext key="Seealso" text="L&#225;sd m&#233;g"/>
+  <l:gentext key="seealso" text="l&#225;sd m&#233;g"/>
+  <l:gentext key="Set" text="Csoport"/>
+  <l:gentext key="set" text="csoport"/>
+  <l:gentext key="SetIndex" text="Csoportmutat&#243;"/>
+  <l:gentext key="setindex" text="csoportmutat&#243;"/>
+  <l:gentext key="Sidebar" text="Sz&#233;ljegyzet"/>
+  <l:gentext key="sidebar" text="sz&#233;ljegyzet"/>
+  <l:gentext key="Step" text="L&#233;p&#233;s"/>
+  <l:gentext key="step" text="l&#233;p&#233;s"/>
+  <l:gentext key="Table" text="T&#225;bl&#225;zat"/>
+  <l:gentext key="table" text="t&#225;bl&#225;zat"/>
+  <l:gentext key="TIP" text="TIPP"/>
+  <l:gentext key="Tip" text="Tipp"/>
+  <l:gentext key="tip" text="tipp"/>
+  <l:gentext key="WARNING" text="FIGYELEM"/>
+  <l:gentext key="Warning" text="Figyelem"/>
+  <l:gentext key="warning" text="figyelem"/>
+  <l:gentext key="and" text="&#233;s"/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="Edited" text="Szerk."/>
+  <l:gentext key="edited" text="szerk."/>
+  <l:gentext key="Editedby" text="Szerkesztette"/>
+  <l:gentext key="editedby" text="szerkesztette"/>
+  <l:gentext key="in" text=""/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="nem l&#233;tez&#337; elem"/>
+  <l:gentext key="notes" text="megjegyz&#233;sek"/>
+  <l:gentext key="Notes" text="Megjegyz&#233;sek"/>
+  <l:gentext key="Pgs" text="Lsz."/>
+  <l:gentext key="pgs" text="lsz."/>
+  <l:gentext key="Revisedby" text="Megvizsg&#225;lva"/>
+  <l:gentext key="revisedby" text="megvizsg&#225;lva"/>
+  <l:gentext key="TableNotes" text="Megjegyz&#233;sek"/>
+  <l:gentext key="tablenotes" text="megjegyz&#233;sek"/>
+  <l:gentext key="TableofContents" text="Tartalom"/>
+  <l:gentext key="tableofcontents" text="tartalom"/>
+  <l:gentext key="unexpectedelementname" text="nem v&#225;rt elemn&#233;v"/>
+  <l:gentext key="unsupported" text="nem t&#225;mogatott"/>
+  <l:gentext key="xrefto" text="keresztref"/>
+  <l:gentext key="listofequations" text="az egyenletek list&#225;ja"/>
+  <l:gentext key="ListofEquations" text="Az egyenletek list&#225;ja"/>
+  <l:gentext key="ListofExamples" text="A p&#233;ld&#225;k list&#225;ja"/>
+  <l:gentext key="listofexamples" text="a p&#233;ld&#225;k list&#225;ja"/>
+  <l:gentext key="ListofFigures" text="Az &#225;br&#225;k list&#225;ja"/>
+  <l:gentext key="listoffigures" text="az &#225;br&#225;k list&#225;ja"/>
+  <l:gentext key="listoftables" text="a t&#225;bl&#225;zatok list&#225;ja"/>
+  <l:gentext key="ListofTables" text="A t&#225;bl&#225;zatok list&#225;ja"/>
+  <l:gentext key="ListofUnknown" text="Az egy&#233;b elemek list&#225;ja"/>
+  <l:gentext key="listofunknown" text="az egy&#233;b elemek list&#225;ja"/>
+  <l:gentext key="nav-home" text="Tartalom"/>
+  <l:gentext key="nav-next" text="K&#246;vetkez&#337;"/>
+  <l:gentext key="nav-next-sibling" text="Gyors el&#337;re"/>
+  <l:gentext key="nav-prev" text="El&#337;z&#337;"/>
+  <l:gentext key="nav-prev-sibling" text="Gyors vissza"/>
+  <l:gentext key="nav-up" text="Fel"/>
+  <l:gentext key="sectioncalled" text="ilyen nev&#369; szakasz:"/>
+  <l:gentext key="Draft" text="V&#225;zlat"/>
+  <l:gentext key="above" text="fent"/>
+  <l:gentext key="below" text="lent"/>
+  <l:gentext key="index symbols" text="szimb&#243;lummutat&#243;"/>
+  <l:gentext key="lowercase.alpha" text="a&#225;bcde&#233;fghi&#237;jklmno&#243;&#246;&#337;pqrstu&#250;&#252;&#171;vwxyz"/>
+  <l:gentext key="uppercase.alpha" text="A&#193;BCDE&#201;FGHI&#205;JKLMNO&#211;&#214;&#336;PQRSTU&#218;&#220;&#368;VWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/hu.xml -->
+  <l:dingbat key="startquote" text="&#8222;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#187;"/>
+  <l:dingbat key="nestedendquote" text="&#171;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="last-first"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="%n. f&#252;ggel&#233;k - %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%n. fejezet - %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%n. egyenlet - %t"/>
+    <l:template name="example" text="%n. p&#233;lda - %t"/>
+    <l:template name="figure" text="%n. &#225;bra - %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%n. r&#233;sz - %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Elj&#225;r&#225;s&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Elemcsoport&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="%n. t&#225;bl&#225;zat - %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="%n. f&#252;ggel&#233;k - %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%n. fejezet - %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="V:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="K:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="K:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8222;%t&#8221;"/>
+    <l:template name="refsection" text="&#8222;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8222;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8222;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8222;%t&#8221;"/>
+    <l:template name="sect1" text="&#8222;%t&#8221;"/>
+    <l:template name="sect2" text="&#8222;%t&#8221;"/>
+    <l:template name="sect3" text="&#8222;%t&#8221;"/>
+    <l:template name="sect4" text="&#8222;%t&#8221;"/>
+    <l:template name="sect5" text="&#8222;%t&#8221;"/>
+    <l:template name="section" text="&#8222;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8222;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="V:&#160;%n"/>
+    <l:template name="appendix" text="%n. f&#252;ggel&#233;k"/>
+    <l:template name="bridgehead" text="Szakasz&#160;%n"/>
+    <l:template name="chapter" text="%n. fejezet"/>
+    <l:template name="equation" text="Egyenlet&#160;%n"/>
+    <l:template name="example" text="%n. p&#233;lda"/>
+    <l:template name="figure" text="%n. &#225;bra"/>
+    <l:template name="part" text="%n. r&#233;sz"/>
+    <l:template name="procedure" text="Elj&#225;r&#225;s&#160;%n"/>
+    <l:template name="productionset" text="Elemcsoport&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="K:&#160;%n"/>
+    <l:template name="question" text="K:&#160;%n"/>
+    <l:template name="sect1" text="%n. szakasz"/>
+    <l:template name="sect2" text="%n. szakasz"/>
+    <l:template name="sect3" text="%n. szakasz"/>
+    <l:template name="sect4" text="%n. szakasz"/>
+    <l:template name="sect5" text="%n. szakasz"/>
+    <l:template name="section" text="%n. szakasz"/>
+    <l:template name="table" text="T&#225;bl&#225;zat&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="%n. f&#252;ggel&#233;k - %t"/>
+    <l:template name="bridgehead" text="Szakasz&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="chapter" text="%n. fejezet - %t"/>
+    <l:template name="equation" text="Egyenlet&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="example" text="%n. p&#233;lda - %t"/>
+    <l:template name="figure" text="%n. &#225;bra - %t"/>
+    <l:template name="part" text="%n. r&#233;sz - %t"/>
+    <l:template name="procedure" text="Elj&#225;r&#225;s&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="productionset" text="Elemcsoport&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8222;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8222;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8222;%t&#8221;"/>
+    <l:template name="refsection" text="&#8222;%t&#8221;"/>
+    <l:template name="sect1" text="%n. szakasz - %t"/>
+    <l:template name="sect2" text="%n. szakasz - %t"/>
+    <l:template name="sect3" text="%n. szakasz - %t"/>
+    <l:template name="sect4" text="%n. szakasz - %t"/>
+    <l:template name="sect5" text="%n. szakasz - %t"/>
+    <l:template name="section" text="%n. szakasz - %t"/>
+    <l:template name="simplesect" text="&#8222;%t&#8221;"/>
+    <l:template name="table" text="%n. t&#225;bl&#225;zat - %t"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#233;s "/>
+    <l:template name="seplast" text=", &#233;s "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="L&#225;sd "/>
+    <l:template name="seealso" text="L&#225;sd m&#233;g "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="C&#233;lk&#246;z&#246;ns&#233;g: "/>
+    <l:template name="MsgLevel" text="Szint: "/>
+    <l:template name="MsgOrig" text="Eredet: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x040e Hungarian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/id.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/id.xml
new file mode 100644
index 00000000000..736cf5ff792
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/id.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="id" english-language-name="Indonesian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/id.xml -->
+  <l:gentext key="Abstract" text="Abstrak"/>
+  <l:gentext key="abstract" text="Abstrak"/>
+  <l:gentext key="Answer" text="Jawab:"/>
+  <l:gentext key="answer" text="Jawab:"/>
+  <l:gentext key="Appendix" text="Lampiran"/>
+  <l:gentext key="appendix" text="lampiran"/>
+  <l:gentext key="Article" text="Artikel"/>
+  <l:gentext key="article" text="Artikel"/>
+  <l:gentext key="Bibliography" text="Bibliografi"/>
+  <l:gentext key="bibliography" text="Bibliografi"/>
+  <l:gentext key="Book" text="Buku"/>
+  <l:gentext key="book" text="Buku"/>
+  <l:gentext key="CAUTION" text="PERHATIAN"/>
+  <l:gentext key="Caution" text="Perhatian"/>
+  <l:gentext key="caution" text="Perhatian"/>
+  <l:gentext key="Chapter" text="Bab"/>
+  <l:gentext key="chapter" text="bab"/>
+  <l:gentext key="Colophon" text="Kolofon"/>
+  <l:gentext key="colophon" text="Kolofon"/>
+  <l:gentext key="Copyright" text="Hak Cipta"/>
+  <l:gentext key="copyright" text="Hak Cipta"/>
+  <l:gentext key="Dedication" text="Dedikasi"/>
+  <l:gentext key="dedication" text="Dedikasi"/>
+  <l:gentext key="Edition" text="Edisi"/>
+  <l:gentext key="edition" text="Edisi"/>
+  <l:gentext key="Equation" text="Persamaan"/>
+  <l:gentext key="equation" text="Persamaan"/>
+  <l:gentext key="Example" text="Teladan"/>
+  <l:gentext key="example" text="Teladan"/>
+  <l:gentext key="Figure" text="Gambar"/>
+  <l:gentext key="figure" text="Gambar"/>
+  <l:gentext key="Glossary" text="Daftar Istilah"/>
+  <l:gentext key="glossary" text="Daftar Istilah"/>
+  <l:gentext key="GlossSee" text="Lihat"/>
+  <l:gentext key="glosssee" text="Lihat"/>
+  <l:gentext key="GlossSeeAlso" text="Lihat Juga"/>
+  <l:gentext key="glossseealso" text="Lihat Juga"/>
+  <l:gentext key="IMPORTANT" text="PENTING"/>
+  <l:gentext key="Important" text="Penting"/>
+  <l:gentext key="important" text="Penting"/>
+  <l:gentext key="Index" text="Indeks"/>
+  <l:gentext key="index" text="Indeks"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Aspek Hukum"/>
+  <l:gentext key="legalnotice" text="Aspek Hukum"/>
+  <l:gentext key="MsgAud" text="Pemirsa"/>
+  <l:gentext key="msgaud" text="Pemirsa"/>
+  <l:gentext key="MsgLevel" text="Tingkatan"/>
+  <l:gentext key="msglevel" text="Tingkatan"/>
+  <l:gentext key="MsgOrig" text="Asal"/>
+  <l:gentext key="msgorig" text="Asal"/>
+  <l:gentext key="NOTE" text="CATATAN"/>
+  <l:gentext key="Note" text="Catatan"/>
+  <l:gentext key="note" text="Catatan"/>
+  <l:gentext key="Part" text="Bagian"/>
+  <l:gentext key="part" text="Bagian"/>
+  <l:gentext key="Preface" text="Kata Pengantar"/>
+  <l:gentext key="preface" text="Kata Pengantar"/>
+  <l:gentext key="Procedure" text="Prosedur"/>
+  <l:gentext key="procedure" text="Prosedur"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="Diterbitkan"/>
+  <l:gentext key="published" text="Diterbitkan"/>
+  <l:gentext key="Question" text="Tanya:"/>
+  <l:gentext key="question" text="Tanya:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Referensi"/>
+  <l:gentext key="reference" text="Referensi"/>
+  <l:gentext key="RefName" text="Nama"/>
+  <l:gentext key="refname" text="Nama"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Sinopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Sinopsis"/>
+  <l:gentext key="RevHistory" text="Catatan Revisi"/>
+  <l:gentext key="revhistory" text="Catatan Revisi"/>
+  <l:gentext key="Revision" text="Revisi"/>
+  <l:gentext key="revision" text="Revisi"/>
+  <l:gentext key="sect1" text="Bagian"/>
+  <l:gentext key="sect2" text="Bagian"/>
+  <l:gentext key="sect3" text="Bagian"/>
+  <l:gentext key="sect4" text="Bagian"/>
+  <l:gentext key="sect5" text="Bagian"/>
+  <l:gentext key="Section" text="Bagian"/>
+  <l:gentext key="section" text="bagian"/>
+  <l:gentext key="See" text="Lihat"/>
+  <l:gentext key="see" text="Lihat"/>
+  <l:gentext key="SeeAlso" text="Lihat Juga"/>
+  <l:gentext key="Seealso" text="Lihat juga"/>
+  <l:gentext key="seealso" text="Lihat Juga"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="SetIndex" text="Indeks Set"/>
+  <l:gentext key="setindex" text="Indeks Set"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="Step" text="Tahap"/>
+  <l:gentext key="step" text="tahap"/>
+  <l:gentext key="Table" text="Tabel"/>
+  <l:gentext key="table" text="Tabel"/>
+  <l:gentext key="TIP" text="TIP"/>
+  <l:gentext key="Tip" text="Tip"/>
+  <l:gentext key="tip" text="Tip"/>
+  <l:gentext key="WARNING" text="AWAS"/>
+  <l:gentext key="Warning" text="Awas"/>
+  <l:gentext key="warning" text="Awas"/>
+  <l:gentext key="and" text="dan"/>
+  <l:gentext key="by" text="oleh"/>
+  <l:gentext key="Edited" text="disunting"/>
+  <l:gentext key="edited" text="disunting"/>
+  <l:gentext key="Editedby" text="disunting oleh"/>
+  <l:gentext key="editedby" text="disunting oleh"/>
+  <l:gentext key="in" text="di"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="elemen tak tampak"/>
+  <l:gentext key="notes" text="Catatan"/>
+  <l:gentext key="Notes" text="Catatan"/>
+  <l:gentext key="Pgs" text="Hal."/>
+  <l:gentext key="pgs" text="Hal."/>
+  <l:gentext key="Revisedby" text="Direvisi oleh: "/>
+  <l:gentext key="revisedby" text="Direvisi oleh: "/>
+  <l:gentext key="TableNotes" text="Catatan"/>
+  <l:gentext key="tablenotes" text="Catatan"/>
+  <l:gentext key="TableofContents" text="Daftar Isi"/>
+  <l:gentext key="tableofcontents" text="Daftar Isi"/>
+  <l:gentext key="unexpectedelementname" text="Nama Elemen seharusnya tidak ada"/>
+  <l:gentext key="unsupported" text="tidak didukung"/>
+  <l:gentext key="xrefto" text="xref ke"/>
+  <l:gentext key="listofequations" text="Daftar Persamaan"/>
+  <l:gentext key="ListofEquations" text="Daftar Persamaan"/>
+  <l:gentext key="ListofExamples" text="Daftar Teladan"/>
+  <l:gentext key="listofexamples" text="Daftar Teladan"/>
+  <l:gentext key="ListofFigures" text="Daftar Gambar"/>
+  <l:gentext key="listoffigures" text="Daftar Gambar"/>
+  <l:gentext key="listoftables" text="Daftar Tabel"/>
+  <l:gentext key="ListofTables" text="Daftar Tabel"/>
+  <l:gentext key="ListofUnknown" text="Daftar Gaib"/>
+  <l:gentext key="listofunknown" text="Daftar Gaib"/>
+  <l:gentext key="nav-home" text="Depan"/>
+  <l:gentext key="nav-next" text="Lanjut"/>
+  <l:gentext key="nav-next-sibling" text="Lewati"/>
+  <l:gentext key="nav-prev" text="Kembali"/>
+  <l:gentext key="nav-prev-sibling" text="Sebelumnya"/>
+  <l:gentext key="nav-up" text="Induk"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/id.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Lampiran %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Bab %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Persamaan %n. %t"/>
+    <l:template name="example" text="Teladan %n. %t"/>
+    <l:template name="figure" text="Gambar %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Bagian %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Prosedur&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabel %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Lampiran %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Bab %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Jawab:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Tanya:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Tanya:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Jawab:&#160;%n"/>
+    <l:template name="appendix" text="Lampiran&#160;%n"/>
+    <l:template name="bridgehead" text="Bagian&#160;%n"/>
+    <l:template name="chapter" text="Bab&#160;%n"/>
+    <l:template name="equation" text="Persamaan&#160;%n"/>
+    <l:template name="example" text="Teladan&#160;%n"/>
+    <l:template name="figure" text="Gambar&#160;%n"/>
+    <l:template name="part" text="Bagian&#160;%n"/>
+    <l:template name="procedure" text="Prosedur&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Tanya:&#160;%n"/>
+    <l:template name="question" text="Tanya:&#160;%n"/>
+    <l:template name="sect1" text="Bagian&#160;%n"/>
+    <l:template name="sect2" text="Bagian&#160;%n"/>
+    <l:template name="sect3" text="Bagian&#160;%n"/>
+    <l:template name="sect4" text="Bagian&#160;%n"/>
+    <l:template name="sect5" text="Bagian&#160;%n"/>
+    <l:template name="section" text="Bagian&#160;%n"/>
+    <l:template name="table" text="Tabel&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Lampiran&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Bagian&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Bab&#160;%n, %t"/>
+    <l:template name="equation" text="Persamaan&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Teladan&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Gambar&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Bagian&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Prosedur&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Bagian&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Bagian&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Bagian&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Bagian&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Bagian&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Bagian&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabel&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" dan "/>
+    <l:template name="seplast" text=", dan "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Lihat "/>
+    <l:template name="seealso" text="Lihat Juga "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Pemirsa: "/>
+    <l:template name="MsgLevel" text="Tingkatan: "/>
+    <l:template name="MsgOrig" text="Asal: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0421 Indonesian (INDONESIA)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/it.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/it.xml
new file mode 100644
index 00000000000..3f49cfb29be
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/it.xml
@@ -0,0 +1,444 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="it" english-language-name="Italian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/it.xml -->
+  <l:gentext key="Abstract" text="Estratto"/>
+  <l:gentext key="abstract" text="Estratto"/>
+  <l:gentext key="Answer" text="R:"/>
+  <l:gentext key="answer" text="R:"/>
+  <l:gentext key="Appendix" text="Appendice"/>
+  <l:gentext key="appendix" text="appendice"/>
+  <l:gentext key="Article" text="Articolo"/>
+  <l:gentext key="article" text="Articolo"/>
+  <l:gentext key="Bibliography" text="Bibliografia"/>
+  <l:gentext key="bibliography" text="Bibliografia"/>
+  <l:gentext key="Book" text="Libro"/>
+  <l:gentext key="book" text="Libro"/>
+  <l:gentext key="CAUTION" text="ATTENZIONE"/>
+  <l:gentext key="Caution" text="Attenzione"/>
+  <l:gentext key="caution" text="Attenzione"/>
+  <l:gentext key="Chapter" text="Capitolo"/>
+  <l:gentext key="chapter" text="capitolo"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Dedica"/>
+  <l:gentext key="dedication" text="Dedica"/>
+  <l:gentext key="Edition" text="Edizione"/>
+  <l:gentext key="edition" text="Edizione"/>
+  <l:gentext key="Equation" text="Equazione"/>
+  <l:gentext key="equation" text="Equazione"/>
+  <l:gentext key="Example" text="Esempio"/>
+  <l:gentext key="example" text="Esempio"/>
+  <l:gentext key="Figure" text="Figura"/>
+  <l:gentext key="figure" text="Figura"/>
+  <l:gentext key="Glossary" text="Glossario"/>
+  <l:gentext key="glossary" text="Glossario"/>
+  <l:gentext key="GlossSee" text="Vedi"/>
+  <l:gentext key="glosssee" text="Vedi"/>
+  <l:gentext key="GlossSeeAlso" text="Vedi Anche"/>
+  <l:gentext key="glossseealso" text="Vedi Anche"/>
+  <l:gentext key="IMPORTANT" text="IMPORTANTE"/>
+  <l:gentext key="important" text="Importante"/>
+  <l:gentext key="Important" text="Importante"/>
+  <l:gentext key="Index" text="Indice"/>
+  <l:gentext key="index" text="Indice"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Note Legali"/>
+  <l:gentext key="legalnotice" text="Note Legali"/>
+  <l:gentext key="MsgAud" text="Pubblico"/>
+  <l:gentext key="msgaud" text="Pubblico"/>
+  <l:gentext key="MsgLevel" text="Livello"/>
+  <l:gentext key="msglevel" text="Livello"/>
+  <l:gentext key="MsgOrig" text="Origine"/>
+  <l:gentext key="msgorig" text="Origine"/>
+  <l:gentext key="NOTE" text="NOTA"/>
+  <l:gentext key="Note" text="Nota"/>
+  <l:gentext key="note" text="Nota"/>
+  <l:gentext key="Part" text="Parte"/>
+  <l:gentext key="part" text="Parte"/>
+  <l:gentext key="Preface" text="Prefazione"/>
+  <l:gentext key="preface" text="Prefazione"/>
+  <l:gentext key="Procedure" text="Procedura"/>
+  <l:gentext key="procedure" text="Procedura"/>
+  <l:gentext key="ProductionSet" text="Produzione"/>
+  <l:gentext key="Published" text="Pubblicato"/>
+  <l:gentext key="published" text="Pubblicato"/>
+  <l:gentext key="Question" text="D:"/>
+  <l:gentext key="question" text="D:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Riferimento"/>
+  <l:gentext key="reference" text="Riferimento"/>
+  <l:gentext key="RefName" text="Nome"/>
+  <l:gentext key="refname" text="Nome"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Sinossi"/>
+  <l:gentext key="refsynopsisdiv" text="Sinossi"/>
+  <l:gentext key="RevHistory" text="Diario delle Revisioni"/>
+  <l:gentext key="revhistory" text="Diario delle Revisioni"/>
+  <l:gentext key="revision" text="Revisione"/>
+  <l:gentext key="Revision" text="Revisione"/>
+  <l:gentext key="sect1" text="Sezione"/>
+  <l:gentext key="sect2" text="Sezione"/>
+  <l:gentext key="sect3" text="Sezione"/>
+  <l:gentext key="sect4" text="Sezione"/>
+  <l:gentext key="sect5" text="Sezione"/>
+  <l:gentext key="section" text="Sezione"/>
+  <l:gentext key="Section" text="Sezione"/>
+  <l:gentext key="See" text="Vd."/>
+  <l:gentext key="see" text="Vd."/>
+  <l:gentext key="SeeAlso" text="Vd. Anche"/>
+  <l:gentext key="seealso" text="Vd. Anche"/>
+  <l:gentext key="Seealso" text="Vd. anche"/>
+  <l:gentext key="set" text="Raccolta"/>
+  <l:gentext key="Set" text="Raccolta"/>
+  <l:gentext key="setindex" text="Indice Raccolta"/>
+  <l:gentext key="SetIndex" text="Indice Raccolta"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="nota a margine"/>
+  <l:gentext key="step" text="passo"/>
+  <l:gentext key="Step" text="Passo"/>
+  <l:gentext key="Table" text="Tabella"/>
+  <l:gentext key="table" text="Tabella"/>
+  <l:gentext key="tip" text="Suggerimento"/>
+  <l:gentext key="TIP" text="SUGGERIMENTO"/>
+  <l:gentext key="Tip" text="Suggerimento"/>
+  <l:gentext key="Warning" text="Avvertimento"/>
+  <l:gentext key="warning" text="avvertimento"/>
+  <l:gentext key="WARNING" text="AVVERTIMENTO"/>
+  <l:gentext key="and" text="e"/>
+  <l:gentext key="by" text="di"/>
+  <l:gentext key="Edited" text="A cura"/>
+  <l:gentext key="edited" text="A cura"/>
+  <l:gentext key="Editedby" text="A cura di"/>
+  <l:gentext key="editedby" text="A cura di"/>
+  <l:gentext key="in" text="in"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="elemento non esistente"/>
+  <l:gentext key="notes" text="Note"/>
+  <l:gentext key="Notes" text="Note"/>
+  <l:gentext key="Pgs" text="pp."/>
+  <l:gentext key="pgs" text="pp."/>
+  <l:gentext key="Revisedby" text="Revisionato da: "/>
+  <l:gentext key="revisedby" text="Revisionato da: "/>
+  <l:gentext key="TableNotes" text="Note"/>
+  <l:gentext key="tablenotes" text="Note"/>
+  <l:gentext key="TableofContents" text="Sommario"/>
+  <l:gentext key="tableofcontents" text="Sommario"/>
+  <l:gentext key="unexpectedelementname" text="Nome elemento inaspettato"/>
+  <l:gentext key="unsupported" text="non supportato"/>
+  <l:gentext key="xrefto" text="riferimento a"/>
+  <l:gentext key="listofequations" text="Lista delle Equazioni"/>
+  <l:gentext key="ListofEquations" text="Lista delle Equazioni"/>
+  <l:gentext key="ListofExamples" text="Lista degli Esempi"/>
+  <l:gentext key="listofexamples" text="Lista degli Esempi"/>
+  <l:gentext key="ListofFigures" text="Lista delle Figure"/>
+  <l:gentext key="listoffigures" text="Lista delle Figure"/>
+  <l:gentext key="listoftables" text="Lista delle Tabelle"/>
+  <l:gentext key="ListofTables" text="Lista delle Tabelle"/>
+  <l:gentext key="ListofUnknown" text="Lista degli Sconosciuti"/>
+  <l:gentext key="listofunknown" text="Lista degli Sconosciuti"/>
+  <l:gentext key="nav-home" text="Partenza"/>
+  <l:gentext key="nav-next" text="Avanti"/>
+  <l:gentext key="nav-next-sibling" text="Salta Avanti"/>
+  <l:gentext key="nav-prev" text="Indietro"/>
+  <l:gentext key="nav-prev-sibling" text="Salta Indietro"/>
+  <l:gentext key="nav-up" text="Risali"/>
+  <l:gentext key="Draft" text="Bozza"/>
+  <l:gentext key="above" text="sopra"/>
+  <l:gentext key="below" text="sotto"/>
+  <l:gentext key="sectioncalled" text="la sezione chiamata"/>
+  <l:gentext key="index symbols" text="Simboli"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/it.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Appendice&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Capitolo&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Equazione&#160;%n.&#160;%t"/>
+    <l:template name="example" text="Esempio&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="Figura&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Parte&#160;%n.&#160;%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedura&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Produzione&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabella&#160;%n.&#160;%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Appendice&#160;%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="Capitolo&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="R:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="D:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="D:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="section" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="la sezione chiamata &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="R:&#160;%n"/>
+    <l:template name="appendix" text="Appendice&#160;%n"/>
+    <l:template name="bridgehead" text="Sezione&#160;%n"/>
+    <l:template name="chapter" text="Capitolo&#160;%n"/>
+    <l:template name="equation" text="Equazione&#160;%n"/>
+    <l:template name="example" text="Esempio&#160;%n"/>
+    <l:template name="figure" text="Figura&#160;%n"/>
+    <l:template name="part" text="Parte&#160;%n"/>
+    <l:template name="procedure" text="Procedura&#160;%n"/>
+    <l:template name="productionset" text="Produzione&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="D:&#160;%n"/>
+    <l:template name="question" text="D:&#160;%n"/>
+    <l:template name="sect1" text="Sezione&#160;%n"/>
+    <l:template name="sect2" text="Sezione&#160;%n"/>
+    <l:template name="sect3" text="Sezione&#160;%n"/>
+    <l:template name="sect4" text="Sezione&#160;%n"/>
+    <l:template name="sect5" text="Sezione&#160;%n"/>
+    <l:template name="section" text="Sezione&#160;%n"/>
+    <l:template name="table" text="Tabella&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Appendice&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Sezione&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Capitolo&#160;%n, %t"/>
+    <l:template name="equation" text="Equazione&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Esempio&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figura&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Parte&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procedura&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Produzione&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Sezione&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Sezione&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Sezione&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Sezione&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Sezione&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Sezione&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="la sezione chiamata &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabella&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" e "/>
+    <l:template name="seplast" text=", e "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Vedi "/>
+    <l:template name="seealso" text="Vedi Anche "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Pubblico: "/>
+    <l:template name="MsgLevel" text="Livello: "/>
+    <l:template name="MsgOrig" text="Origine: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0410 Italian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/ja.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/ja.xml
new file mode 100644
index 00000000000..d2e8fb805a4
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/ja.xml
@@ -0,0 +1,445 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="ja" english-language-name="Japanese">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ja.xml -->
+  <l:gentext key="Abstract" text="&#27010;&#35201;"/>
+  <l:gentext key="abstract" text="&#27010;&#35201;"/>
+  <l:gentext key="Answer" text="&#31572;&#65306;"/>
+  <l:gentext key="answer" text="&#31572;&#65306;"/>
+  <l:gentext key="Appendix" text="&#20184;&#37682;"/>
+  <l:gentext key="appendix" text="&#20184;&#37682;"/>
+  <l:gentext key="Article" text="&#38917;&#30446;"/>
+  <l:gentext key="article" text="&#38917;&#30446;"/>
+  <l:gentext key="Bibliography" text="&#21442;&#32771;&#25991;&#29486;"/>
+  <l:gentext key="bibliography" text="&#21442;&#32771;&#25991;&#29486;"/>
+  <l:gentext key="Book" text="&#12502;&#12483;&#12463;"/>
+  <l:gentext key="book" text="&#12502;&#12483;&#12463;"/>
+  <l:gentext key="Caution" text="&#27880;&#24847;"/>
+  <l:gentext key="caution" text="&#27880;&#24847;"/>
+  <l:gentext key="CAUTION" text="&#27880;&#24847;"/>
+  <l:gentext key="chapter" text="&#31456;"/>
+  <l:gentext key="Chapter" text="&#31456;"/>
+  <l:gentext key="chapter1" text="&#31532;"/>
+  <l:gentext key="Chapter1" text="&#31532;"/>
+  <l:gentext key="Chapter2" text="&#31456;"/>
+  <l:gentext key="chapter2" text="&#31456;"/>
+  <l:gentext key="Colophon" text="&#22885;&#20184;"/>
+  <l:gentext key="colophon" text="&#22885;&#20184;"/>
+  <l:gentext key="Copyright" text="&#35069;&#20316;&#33879;&#20316;"/>
+  <l:gentext key="copyright" text="&#35069;&#20316;&#33879;&#20316;"/>
+  <l:gentext key="Dedication" text="&#35613;&#36766;"/>
+  <l:gentext key="dedication" text="&#35613;&#36766;"/>
+  <l:gentext key="Edition" text="&#32232;&#38598;"/>
+  <l:gentext key="edition" text="&#32232;&#38598;"/>
+  <l:gentext key="Equation" text="&#24335;"/>
+  <l:gentext key="equation" text="&#24335;"/>
+  <l:gentext key="Example" text="&#20363;"/>
+  <l:gentext key="example" text="&#20363;"/>
+  <l:gentext key="Figure" text="&#22259;"/>
+  <l:gentext key="figure" text="&#22259;"/>
+  <l:gentext key="Glossary" text="&#29992;&#35486;&#38598;"/>
+  <l:gentext key="glossary" text="&#29992;&#35486;&#38598;"/>
+  <l:gentext key="GlossSee" text="&#21442;&#29031;"/>
+  <l:gentext key="glosssee" text="&#21442;&#29031;"/>
+  <l:gentext key="GlossSeeAlso" text="&#21442;&#29031;"/>
+  <l:gentext key="glossseealso" text="&#21442;&#29031;"/>
+  <l:gentext key="IMPORTANT" text="&#37325;&#35201;&#38917;&#30446;"/>
+  <l:gentext key="Important" text="&#37325;&#35201;&#38917;&#30446;"/>
+  <l:gentext key="important" text="&#37325;&#35201;&#38917;&#30446;"/>
+  <l:gentext key="Index" text="&#30446;&#27425;"/>
+  <l:gentext key="index" text="&#30446;&#27425;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text=""/>
+  <l:gentext key="legalnotice" text=""/>
+  <l:gentext key="MsgAud" text="&#23550;&#35937;&#32773;"/>
+  <l:gentext key="msgaud" text="&#23550;&#35937;&#32773;"/>
+  <l:gentext key="MsgLevel" text="&#12524;&#12505;&#12523;"/>
+  <l:gentext key="msglevel" text="&#12524;&#12505;&#12523;"/>
+  <l:gentext key="MsgOrig" text="&#30330;&#20449;&#20803;"/>
+  <l:gentext key="msgorig" text="&#30330;&#20449;&#20803;"/>
+  <l:gentext key="note" text="&#27880;&#24847;"/>
+  <l:gentext key="Note" text="&#27880;&#24847;"/>
+  <l:gentext key="NOTE" text="&#27880;&#24847;"/>
+  <l:gentext key="Part" text="&#12497;&#12540;&#12488;"/>
+  <l:gentext key="part" text="&#12497;&#12540;&#12488;"/>
+  <l:gentext key="Preface" text="&#24207;&#25991;"/>
+  <l:gentext key="preface" text="&#24207;&#25991;"/>
+  <l:gentext key="Procedure" text="&#25163;&#38918;"/>
+  <l:gentext key="procedure" text="&#25163;&#38918;"/>
+  <l:gentext key="ProductionSet" text="&#12503;&#12525;&#12480;&#12463;&#12471;&#12519;&#12531;"/>
+  <l:gentext key="Published" text="&#30330;&#34892;"/>
+  <l:gentext key="published" text="&#30330;&#34892;"/>
+  <l:gentext key="Question" text="&#21839;&#65306;"/>
+  <l:gentext key="question" text="&#21839;&#65306;"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#21442;&#29031;"/>
+  <l:gentext key="reference" text="&#21442;&#29031;"/>
+  <l:gentext key="RefName" text="&#21517;&#21069;"/>
+  <l:gentext key="refname" text="&#21517;&#21069;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#27010;&#35201;"/>
+  <l:gentext key="refsynopsisdiv" text="&#27010;&#35201;"/>
+  <l:gentext key="RevHistory" text="&#25913;&#35330;&#23653;&#27508;"/>
+  <l:gentext key="revhistory" text="&#25913;&#35330;&#23653;&#27508;"/>
+  <l:gentext key="revision" text="&#25913;&#35330;"/>
+  <l:gentext key="Revision" text="&#25913;&#35330;"/>
+  <l:gentext key="sect1" text="&#38917;"/>
+  <l:gentext key="sect2" text="&#38917;"/>
+  <l:gentext key="sect3" text="&#38917;"/>
+  <l:gentext key="sect4" text="&#38917;"/>
+  <l:gentext key="sect5" text="&#38917;"/>
+  <l:gentext key="Section" text="&#38917;"/>
+  <l:gentext key="section" text="&#38917;"/>
+  <l:gentext key="See" text="&#21442;&#29031;"/>
+  <l:gentext key="see" text="&#21442;&#29031;"/>
+  <l:gentext key="seealso" text="&#21442;&#29031;"/>
+  <l:gentext key="SeeAlso" text="&#21442;&#29031;"/>
+  <l:gentext key="Seealso" text="&#21442;&#29031;"/>
+  <l:gentext key="Set" text="&#35373;&#23450;"/>
+  <l:gentext key="set" text="&#35373;&#23450;"/>
+  <l:gentext key="SetIndex" text="&#30446;&#27425;&#35373;&#23450;"/>
+  <l:gentext key="setindex" text="&#30446;&#27425;&#35373;&#23450;"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="&#12469;&#12452;&#12489;&#12496;&#12540;"/>
+  <l:gentext key="step" text="&#12473;&#12486;&#12483;&#12503;"/>
+  <l:gentext key="Step" text="&#12473;&#12486;&#12483;&#12503;"/>
+  <l:gentext key="table" text="&#34920;"/>
+  <l:gentext key="Table" text="&#34920;"/>
+  <l:gentext key="TIP" text="&#12486;&#12451;&#12483;&#12503;"/>
+  <l:gentext key="Tip" text="&#12486;&#12451;&#12483;&#12503;"/>
+  <l:gentext key="tip" text="&#12486;&#12451;&#12483;&#12503;"/>
+  <l:gentext key="WARNING" text="&#35686;&#21578;"/>
+  <l:gentext key="Warning" text="&#35686;&#21578;"/>
+  <l:gentext key="warning" text="&#35686;&#21578;"/>
+  <l:gentext key="and" text="&#12289;"/>
+  <l:gentext key="by" text="&#65306;"/>
+  <l:gentext key="Edited" text="&#20316;&#32773;"/>
+  <l:gentext key="edited" text="&#20316;&#32773;"/>
+  <l:gentext key="Editedby" text="&#20316;&#32773;&#65306;"/>
+  <l:gentext key="editedby" text="&#20316;&#32773;&#65306;"/>
+  <l:gentext key="in" text=""/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="&#35201;&#32032;&#12364;&#23384;&#22312;&#12375;&#12414;&#12379;&#12435;"/>
+  <l:gentext key="notes" text="&#27880;&#24847;"/>
+  <l:gentext key="Notes" text="&#27880;&#24847;"/>
+  <l:gentext key="Pgs" text="&#20583;&#29486;"/>
+  <l:gentext key="pgs" text="&#20583;&#29486;"/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text="&#27880;&#24847;"/>
+  <l:gentext key="tablenotes" text="&#27880;&#24847;"/>
+  <l:gentext key="TableofContents" text="&#30446;&#27425;"/>
+  <l:gentext key="tableofcontents" text="&#30446;&#27425;"/>
+  <l:gentext key="unexpectedelementname" text="&#19981;&#26126;&#12394;&#35201;&#32032;&#21517;"/>
+  <l:gentext key="unsupported" text="&#12469;&#12509;&#12540;&#12488;&#12375;&#12414;&#12379;&#12435;"/>
+  <l:gentext key="xrefto" text="xref to"/>
+  <l:gentext key="listofequations" text="&#24335;&#30446;&#27425;"/>
+  <l:gentext key="ListofEquations" text="&#24335;&#30446;&#27425;"/>
+  <l:gentext key="ListofExamples" text="&#20363;&#30446;&#27425;"/>
+  <l:gentext key="listofexamples" text="&#20363;&#30446;&#27425;"/>
+  <l:gentext key="ListofFigures" text="&#22259;&#30446;&#27425;"/>
+  <l:gentext key="listoffigures" text="&#22259;&#30446;&#27425;"/>
+  <l:gentext key="listoftables" text="&#34920;&#30446;&#27425;"/>
+  <l:gentext key="ListofTables" text="&#34920;&#30446;&#27425;"/>
+  <l:gentext key="ListofUnknown" text="&#19981;&#26126;&#30446;&#27425;"/>
+  <l:gentext key="listofunknown" text="&#19981;&#26126;&#30446;&#27425;"/>
+  <l:gentext key="nav-home" text="&#12507;&#12540;&#12512;"/>
+  <l:gentext key="nav-next" text="&#27425;&#12398;&#12506;&#12540;&#12472;"/>
+  <l:gentext key="nav-next-sibling" text="&#26089;&#36865;&#12426;"/>
+  <l:gentext key="nav-prev" text="&#21069;&#12398;&#12506;&#12540;&#12472;"/>
+  <l:gentext key="nav-prev-sibling" text="&#24059;&#25147;&#12375;"/>
+  <l:gentext key="nav-up" text="&#19978;&#12395;&#25147;&#12427;"/>
+  <l:gentext key="index symbols" text="&#12471;&#12531;&#12508;&#12523;"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ja.xml -->
+  <l:dingbat key="startquote" text="&#12300;"/>
+  <l:dingbat key="endquote" text="&#12301;"/>
+  <l:dingbat key="nestedstartquote" text="&#12302;"/>
+  <l:dingbat key="nestedendquote" text="&#12303;"/>
+  <l:dingbat key="bullet" text="&#9679;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="family-given"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#20184;&#37682; %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#31532;%n&#31456; %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#24335; %n. %t"/>
+    <l:template name="example" text="&#20363; %n. %t"/>
+    <l:template name="figure" text="&#22259; %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#12497;&#12540;&#12488; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#25163;&#38918; %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="&#12503;&#12525;&#12480;&#12463;&#12471;&#12519;&#12531; %n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#34920; %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#20184;&#37682; %n. %t"/>
+    <l:template name="chapter" text="&#31532;%n&#31456; %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#31572;&#65306;&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#21839;&#65306;&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#21839;&#65306;&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="%t&#38917;"/>
+    <l:template name="refsection" text="%t&#38917;"/>
+    <l:template name="refsect1" text="%t&#38917;"/>
+    <l:template name="refsect2" text="%t&#38917;"/>
+    <l:template name="refsect3" text="%t&#38917;"/>
+    <l:template name="sect1" text="%t&#38917;"/>
+    <l:template name="sect2" text="%t&#38917;"/>
+    <l:template name="sect3" text="%t&#38917;"/>
+    <l:template name="sect4" text="%t&#38917;"/>
+    <l:template name="sect5" text="%t&#38917;"/>
+    <l:template name="section" text="%t&#38917;"/>
+    <l:template name="simplesect" text="%t&#38917;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#31572;&#65306;&#160;%n"/>
+    <l:template name="appendix" text="&#20184;&#37682;%n"/>
+    <l:template name="bridgehead" text="&#38917;&#160;%n"/>
+    <l:template name="chapter" text="&#31532;%n&#31456;"/>
+    <l:template name="equation" text="&#24335;&#160;%n"/>
+    <l:template name="example" text="&#20363;&#160;%n"/>
+    <l:template name="figure" text="&#22259;&#160;%n"/>
+    <l:template name="part" text="&#12497;&#12540;&#12488;&#160;%n"/>
+    <l:template name="procedure" text="&#25163;&#38918;&#160;%n"/>
+    <l:template name="productionset" text="&#12503;&#12525;&#12480;&#12463;&#12471;&#12519;&#12531;&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#21839;&#65306;&#160;%n"/>
+    <l:template name="question" text="&#21839;&#65306;&#160;%n"/>
+    <l:template name="sect1" text="&#38917;%n"/>
+    <l:template name="sect2" text="&#38917;%n"/>
+    <l:template name="sect3" text="&#38917;%n"/>
+    <l:template name="sect4" text="&#38917;%n"/>
+    <l:template name="sect5" text="&#38917;%n"/>
+    <l:template name="section" text="&#38917;%n"/>
+    <l:template name="table" text="&#34920;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#20184;&#37682;&#160;%n. %t"/>
+    <l:template name="bridgehead" text="&#38917;&#160;%n. &#12300;%t&#12301;"/>
+    <l:template name="chapter" text="&#31456;&#160;%n. %t"/>
+    <l:template name="equation" text="&#24335;&#160;%n. &#12300;%t&#12301;"/>
+    <l:template name="example" text="&#20363;&#160;%n. &#12300;%t&#12301;"/>
+    <l:template name="figure" text="&#22259;&#160;%n. &#12300;%t&#12301;"/>
+    <l:template name="part" text="&#12497;&#12540;&#12488;&#160;%n. &#12300;%t&#12301;"/>
+    <l:template name="procedure" text="&#25163;&#38918;&#160;%n. &#12300;%t&#12301;"/>
+    <l:template name="productionset" text="&#12503;&#12525;&#12480;&#12463;&#12471;&#12519;&#12531;&#160;%n. &#12300;%t&#12301;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n. &#12300;%t&#12301;"/>
+    <l:template name="refsect1" text="&#12300;%t&#12301;"/>
+    <l:template name="refsect2" text="&#12300;%t&#12301;"/>
+    <l:template name="refsect3" text="&#12300;%t&#12301;"/>
+    <l:template name="refsection" text="&#12300;%t&#12301;"/>
+    <l:template name="sect1" text="&#38917;%n. &#12300;%t&#12301;"/>
+    <l:template name="sect2" text="&#38917;%n. &#12300;%t&#12301;"/>
+    <l:template name="sect3" text="&#38917;%n. &#12300;%t&#12301;"/>
+    <l:template name="sect4" text="&#38917;%n. &#12300;%t&#12301;"/>
+    <l:template name="sect5" text="&#38917;%n. &#12300;%t&#12301;"/>
+    <l:template name="section" text="&#38917;%n. &#12300;%t&#12301;"/>
+    <l:template name="simplesect" text="&#12300;%t&#12301;"/>
+    <l:template name="table" text="&#34920;&#160;%n. &#12300;%t&#12301;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#12289; "/>
+    <l:template name="seplast" text=", &#12289; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#21442;&#29031; "/>
+    <l:template name="seealso" text="&#21442;&#29031; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#23550;&#35937;&#32773;: "/>
+    <l:template name="MsgLevel" text="&#12524;&#12505;&#12523;: "/>
+    <l:template name="MsgOrig" text="&#30330;&#20449;&#20803;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0411 Japanese"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/ko.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/ko.xml
new file mode 100644
index 00000000000..549817910a3
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/ko.xml
@@ -0,0 +1,441 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="ko" english-language-name="Korean">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ko.xml -->
+  <l:gentext key="Abstract" text="&#52488;&#47197;"/>
+  <l:gentext key="abstract" text="&#52488;&#47197;"/>
+  <l:gentext key="Answer" text="&#45813;&#48320;"/>
+  <l:gentext key="answer" text="&#45813;&#48320;"/>
+  <l:gentext key="Appendix" text="&#48512;&#47197;"/>
+  <l:gentext key="appendix" text="&#48512;&#47197;"/>
+  <l:gentext key="Article" text="&#47928;&#49436;"/>
+  <l:gentext key="article" text="&#47928;&#49436;"/>
+  <l:gentext key="Bibliography" text="&#49436;&#51648;&#49324;&#54637;"/>
+  <l:gentext key="bibliography" text="&#49436;&#51648;&#49324;&#54637;"/>
+  <l:gentext key="Book" text="&#52293;"/>
+  <l:gentext key="book" text="&#52293;"/>
+  <l:gentext key="Caution" text="&#44221;&#44256;"/>
+  <l:gentext key="caution" text="&#44221;&#44256;"/>
+  <l:gentext key="CAUTION" text="[&#44221;&#44256;]"/>
+  <l:gentext key="Chapter" text="&#51109;"/>
+  <l:gentext key="chapter" text="&#51109;"/>
+  <l:gentext key="Colophon" text="&#54032;&#44428;"/>
+  <l:gentext key="colophon" text="&#54032;&#44428;"/>
+  <l:gentext key="Copyright" text="&#51200;&#51089;&#44428;"/>
+  <l:gentext key="copyright" text="&#51200;&#51089;&#44428;"/>
+  <l:gentext key="Dedication" text="&#48148;&#52824;&#45716; &#44544;"/>
+  <l:gentext key="dedication" text="&#48148;&#52824;&#45716; &#44544;"/>
+  <l:gentext key="Edition" text="&#50670;&#51020;"/>
+  <l:gentext key="edition" text="&#50670;&#51020;"/>
+  <l:gentext key="Equation" text="&#49688;&#49885;"/>
+  <l:gentext key="equation" text="&#49688;&#49885;"/>
+  <l:gentext key="Example" text="&#50696;"/>
+  <l:gentext key="example" text="&#50696;"/>
+  <l:gentext key="Figure" text="&#44536;&#47548;"/>
+  <l:gentext key="figure" text="&#44536;&#47548;"/>
+  <l:gentext key="Glossary" text="&#50857;&#50612;&#54644;&#49444;"/>
+  <l:gentext key="glossary" text="&#50857;&#50612;&#54644;&#49444;"/>
+  <l:gentext key="GlossSee" text="&#49332;&#54196;&#48380; &#45236;&#50857;"/>
+  <l:gentext key="glosssee" text="&#49332;&#54196;&#48380; &#45236;&#50857;"/>
+  <l:gentext key="GlossSeeAlso" text="&#45796;&#47480; &#49332;&#54196;&#48380; &#45236;&#50857;"/>
+  <l:gentext key="glossseealso" text="&#45796;&#47480; &#49332;&#54196;&#48380; &#45236;&#50857;"/>
+  <l:gentext key="Important" text="&#51473;&#50836;"/>
+  <l:gentext key="important" text="&#51473;&#50836;"/>
+  <l:gentext key="IMPORTANT" text="[&#51473;&#50836;]"/>
+  <l:gentext key="Index" text="&#49353;&#51064;"/>
+  <l:gentext key="index" text="&#49353;&#51064;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="&#48277;&#51201; &#44277;&#51648;"/>
+  <l:gentext key="legalnotice" text="&#48277;&#51201; &#44277;&#51648;"/>
+  <l:gentext key="MsgAud" text="&#48155;&#45716; &#51060;"/>
+  <l:gentext key="msgaud" text="&#48155;&#45716; &#51060;"/>
+  <l:gentext key="MsgLevel" text="&#51473;&#50836;&#46020;"/>
+  <l:gentext key="msglevel" text="&#51473;&#50836;&#46020;"/>
+  <l:gentext key="MsgOrig" text="&#48372;&#45236;&#45716; &#51060;"/>
+  <l:gentext key="msgorig" text="&#48372;&#45236;&#45716; &#51060;"/>
+  <l:gentext key="Note" text="&#52280;&#44256;"/>
+  <l:gentext key="note" text="&#52280;&#44256;"/>
+  <l:gentext key="NOTE" text="[&#52280;&#44256;]"/>
+  <l:gentext key="Part" text="&#48512;"/>
+  <l:gentext key="part" text="&#48512;"/>
+  <l:gentext key="Preface" text="&#49436;&#47928;"/>
+  <l:gentext key="preface" text="&#49436;&#47928;"/>
+  <l:gentext key="Procedure" text="&#51208;&#52264;"/>
+  <l:gentext key="procedure" text="&#51208;&#52264;"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="&#54196;&#45252;"/>
+  <l:gentext key="published" text="&#54196;&#45252;"/>
+  <l:gentext key="Question" text="&#51656;&#47928;"/>
+  <l:gentext key="question" text="&#51656;&#47928;"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#52280;&#44256;&#47928;&#54732;"/>
+  <l:gentext key="reference" text="&#52280;&#44256;&#47928;&#54732;"/>
+  <l:gentext key="RefName" text="&#51228;&#47785;"/>
+  <l:gentext key="refname" text="&#51228;&#47785;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#50836;&#50557;"/>
+  <l:gentext key="refsynopsisdiv" text="&#50836;&#50557;"/>
+  <l:gentext key="RevHistory" text="&#44256;&#52828; &#44284;&#51221;"/>
+  <l:gentext key="revhistory" text="&#44256;&#52828; &#44284;&#51221;"/>
+  <l:gentext key="Revision" text="&#44256;&#52840;"/>
+  <l:gentext key="revision" text="&#44256;&#52840;"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="&#51208;"/>
+  <l:gentext key="section" text="&#51208;"/>
+  <l:gentext key="See" text="&#49332;&#54196;&#48380; &#45236;&#50857;"/>
+  <l:gentext key="see" text="&#49332;&#54196;&#48380; &#45236;&#50857;"/>
+  <l:gentext key="Seealso" text="&#49332;&#54196;&#48380; &#45796;&#47480; &#45236;&#50857;"/>
+  <l:gentext key="SeeAlso" text="[&#49332;&#54196;&#48380; &#45796;&#47480; &#45236;&#50857;]"/>
+  <l:gentext key="seealso" text="[&#49332;&#54196;&#48380; &#45796;&#47480; &#45236;&#50857;]"/>
+  <l:gentext key="Set" text="&#51204;&#51665;"/>
+  <l:gentext key="set" text="&#51204;&#51665;"/>
+  <l:gentext key="SetIndex" text="&#51204;&#51665; &#49353;&#51064;"/>
+  <l:gentext key="setindex" text="&#51204;&#51665; &#49353;&#51064;"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="&#45927;&#48537;&#51076;"/>
+  <l:gentext key="Step" text="&#45800;&#44228;"/>
+  <l:gentext key="step" text="&#45800;&#44228;"/>
+  <l:gentext key="Table" text="&#54364;"/>
+  <l:gentext key="table" text="&#54364;"/>
+  <l:gentext key="Tip" text="&#51089;&#51008; &#51221;&#48372;"/>
+  <l:gentext key="tip" text="&#51089;&#51008; &#51221;&#48372;"/>
+  <l:gentext key="TIP" text="[&#51089;&#51008; &#51221;&#48372;]"/>
+  <l:gentext key="WARNING" text="&#51452;&#51032;!"/>
+  <l:gentext key="Warning" text="&#51452;&#51032;"/>
+  <l:gentext key="warning" text="&#51452;&#51032;"/>
+  <l:gentext key="and" text="&#44536;&#47532;&#44256;"/>
+  <l:gentext key="by" text="&#51648;&#51008;&#51060;"/>
+  <l:gentext key="Edited" text="&#50670;&#51020;"/>
+  <l:gentext key="edited" text="&#50670;&#51020;"/>
+  <l:gentext key="Editedby" text="&#50670;&#51008;&#51060;"/>
+  <l:gentext key="editedby" text="&#50670;&#51008;&#51060;"/>
+  <l:gentext key="in" text="-"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="&#51316;&#51116;&#54616;&#51648; &#50506;&#45716; &#44592;&#52488;&#50836;&#49548;&#51077;&#45768;&#45796;"/>
+  <l:gentext key="notes" text="&#51452;&#49437;"/>
+  <l:gentext key="Notes" text="&#51452;&#49437;"/>
+  <l:gentext key="Pgs" text="Pgs."/>
+  <l:gentext key="pgs" text="Pgs."/>
+  <l:gentext key="Revisedby" text="&#44256;&#52828;&#51060; "/>
+  <l:gentext key="revisedby" text="&#44256;&#52828;&#51060; "/>
+  <l:gentext key="TableNotes" text="&#52280;&#44256;"/>
+  <l:gentext key="tablenotes" text="&#52280;&#44256;"/>
+  <l:gentext key="TableofContents" text="&#52264;&#47168;"/>
+  <l:gentext key="tableofcontents" text="&#52264;&#47168;"/>
+  <l:gentext key="unexpectedelementname" text="&#50508; &#49688; &#50630;&#45716; &#44592;&#52488;&#50836;&#49548; &#51060;&#47492;&#51077;&#45768;&#45796;"/>
+  <l:gentext key="unsupported" text="&#51648;&#50896;&#46104;&#51648; &#50506;&#49845;&#45768;&#45796;"/>
+  <l:gentext key="xrefto" text="&#51060; &#44275;&#51012; &#52280;&#51312;&#54616;&#49464;&#50836; : "/>
+  <l:gentext key="listofequations" text="&#49688;&#49885; &#47785;&#47197;"/>
+  <l:gentext key="ListofEquations" text="&#49688;&#49885; &#47785;&#47197;"/>
+  <l:gentext key="ListofExamples" text="&#50696; &#47785;&#47197;"/>
+  <l:gentext key="listofexamples" text="&#50696; &#47785;&#47197;"/>
+  <l:gentext key="ListofFigures" text="&#44536;&#47548; &#47785;&#47197;"/>
+  <l:gentext key="listoffigures" text="&#44536;&#47548; &#47785;&#47197;"/>
+  <l:gentext key="listoftables" text="&#54364; &#47785;&#47197;"/>
+  <l:gentext key="ListofTables" text="&#54364; &#47785;&#47197;"/>
+  <l:gentext key="ListofUnknown" text="&#44592;&#53440; &#47785;&#47197;"/>
+  <l:gentext key="listofunknown" text="&#44592;&#53440; &#47785;&#47197;"/>
+  <l:gentext key="nav-home" text="&#52376;&#51020;&#51004;&#47196;"/>
+  <l:gentext key="nav-next" text="&#45796;&#51020;"/>
+  <l:gentext key="nav-next-sibling" text="&#45796;&#51020;&#51004;&#47196; &#44148;&#45320;&#46848;"/>
+  <l:gentext key="nav-prev" text="&#51060;&#51204;"/>
+  <l:gentext key="nav-prev-sibling" text="&#51060;&#51204;&#51004;&#47196; &#44148;&#45320;&#46848;"/>
+  <l:gentext key="nav-up" text="&#50948;&#47196;"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ko.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#48512;&#47197; %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%n&#51109;. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#49688;&#49885; %n. %t"/>
+    <l:template name="example" text="&#50696; %n. %t"/>
+    <l:template name="figure" text="&#44536;&#47548; %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%n&#48512;. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#51208;&#52264;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#54364; %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#48512;&#47197; %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="%n&#51109;. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#45813;&#48320;&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#51656;&#47928;&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#51656;&#47928;&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#45813;&#48320;&#160;%n"/>
+    <l:template name="appendix" text="&#48512;&#47197;&#160;%n"/>
+    <l:template name="bridgehead" text="&#51208;&#160;%n"/>
+    <l:template name="chapter" text="%n&#51109;"/>
+    <l:template name="equation" text="&#49688;&#49885;&#160;%n"/>
+    <l:template name="example" text="&#50696;&#160;%n"/>
+    <l:template name="figure" text="&#44536;&#47548;&#160;%n"/>
+    <l:template name="part" text="%n&#48512;"/>
+    <l:template name="procedure" text="&#51208;&#52264;&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#51656;&#47928;&#160;%n"/>
+    <l:template name="question" text="&#51656;&#47928;&#160;%n"/>
+    <l:template name="sect1" text="%n&#51208;"/>
+    <l:template name="sect2" text="%n&#51208;"/>
+    <l:template name="sect3" text="%n&#51208;"/>
+    <l:template name="sect4" text="%n&#51208;"/>
+    <l:template name="sect5" text="%n&#51208;"/>
+    <l:template name="section" text="%n&#51208;"/>
+    <l:template name="table" text="&#54364;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#48512;&#47197;&#160;%n. %t"/>
+    <l:template name="bridgehead" text="&#51208;&#160;%n. &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="%n&#51109;. %t"/>
+    <l:template name="equation" text="&#49688;&#49885;&#160;%n. &#8220;%t&#8221;"/>
+    <l:template name="example" text="&#50696;&#160;%n. &#8220;%t&#8221;"/>
+    <l:template name="figure" text="&#44536;&#47548;&#160;%n. &#8220;%t&#8221;"/>
+    <l:template name="part" text="%n&#48512;. %t"/>
+    <l:template name="procedure" text="&#51208;&#52264;&#160;%n. &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n. &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n. &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="startquote/&gt;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="%n&#51208;. &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="%n&#51208;. &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="%n&#51208;. &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="%n&#51208;. &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="%n&#51208;. &#8220;%t&#8221;"/>
+    <l:template name="section" text="%n&#51208;. &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+    <l:template name="table" text="&#54364;&#160;%n. &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#44536;&#47532;&#44256; "/>
+    <l:template name="seplast" text=", &#44536;&#47532;&#44256; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#49332;&#54196;&#48380; &#45236;&#50857; "/>
+    <l:template name="seealso" text="&#45796;&#47480; &#49332;&#54196;&#48380; &#45236;&#50857; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#48155;&#45716; &#51060;: "/>
+    <l:template name="MsgLevel" text="&#51473;&#50836;&#46020;: "/>
+    <l:template name="MsgOrig" text="&#48372;&#45236;&#45716; &#51060;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0412 Korean"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/l10n.dtd b/docs-xml/xslt/db2latex-xsl/xsl/common/l10n.dtd
new file mode 100644
index 00000000000..0e75ed7a0e9
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/l10n.dtd
@@ -0,0 +1,63 @@
+<!ENTITY % prefix "l">
+
+<!ENTITY % xmlns "xmlns:%prefix;">
+<!ENTITY % uri "'http://docbook.sourceforge.net/xmlns/l10n/1.0'">
+
+<!ENTITY % i18n "%prefix;:i18n">
+<!ENTITY % l10n "%prefix;:l10n">
+<!ENTITY % gentext "%prefix;:gentext">
+<!ENTITY % dingbat "%prefix;:dingbat">
+<!ENTITY % context "%prefix;:context">
+<!ENTITY % template "%prefix;:template">
+<!ENTITY % letters "%prefix;:letters">
+<!ENTITY % l "%prefix;:l">
+<!ENTITY % lang "lang NMTOKEN #IMPLIED"> 
+
+<!ELEMENT %i18n; ((%l10n;)+)>
+<!ATTLIST %i18n;
+	%xmlns;		CDATA	#FIXED "'http://docbook.sourceforge.net/xmlns/l10n/1.0'"
+>
+
+<!ELEMENT %l10n; (%gentext;|%dingbat;|%context;|%letters;)*>
+<!ATTLIST %l10n;
+	%xmlns;		CDATA	#FIXED "'http://docbook.sourceforge.net/xmlns/l10n/1.0'"
+	language	CDATA	#REQUIRED
+	english-language-name	CDATA	#IMPLIED
+>
+
+<!ELEMENT %gentext; EMPTY>
+<!ATTLIST %gentext;
+	%lang;
+	key		CDATA	#REQUIRED
+	text		CDATA	#REQUIRED
+>
+
+<!ELEMENT %dingbat; EMPTY>
+<!ATTLIST %dingbat;
+        %lang;
+	key		CDATA	#REQUIRED
+	text		CDATA	#REQUIRED
+>
+
+<!ELEMENT %context; ((%template;)+)>
+<!ATTLIST %context;
+	name		CDATA	#REQUIRED
+>
+
+<!ELEMENT %template; EMPTY>
+<!ATTLIST %template;
+        %lang;
+	name		CDATA	#REQUIRED
+	text		CDATA	#REQUIRED
+	style		CDATA	#IMPLIED
+>
+
+<!ELEMENT %letters; ((%l;)+)>
+<!ATTLIST %letters;
+          %lang;
+>
+
+<!ELEMENT %l; (#PCDATA)>
+<!ATTLIST %l;
+          i 		CDATA 	#REQUIRED
+>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/l10n.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/l10n.xml
new file mode 100644
index 00000000000..583f2196614
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/l10n.xml
@@ -0,0 +1,89 @@
+<?xml version='1.0'?>
+<!DOCTYPE l:i18n SYSTEM "l10n.dtd" [
+<!ENTITY af SYSTEM "af.xml">
+<!ENTITY bg SYSTEM "bg.xml">
+<!ENTITY bn SYSTEM "bn.xml">
+<!ENTITY ca SYSTEM "ca.xml">
+<!ENTITY cs SYSTEM "cs.xml">
+<!ENTITY da SYSTEM "da.xml">
+<!ENTITY de SYSTEM "de.xml">
+<!ENTITY el SYSTEM "el.xml">
+<!ENTITY en SYSTEM "en.xml">
+<!ENTITY es SYSTEM "es.xml">
+<!ENTITY et SYSTEM "et.xml">
+<!ENTITY eu SYSTEM "eu.xml">
+<!ENTITY fi SYSTEM "fi.xml">
+<!ENTITY fr SYSTEM "fr.xml">
+<!ENTITY he SYSTEM "he.xml">
+<!ENTITY hu SYSTEM "hu.xml">
+<!ENTITY id SYSTEM "id.xml">
+<!ENTITY it SYSTEM "it.xml">
+<!ENTITY ja SYSTEM "ja.xml">
+<!ENTITY ko SYSTEM "ko.xml">
+<!ENTITY la SYSTEM "la.xml">
+<!ENTITY lit SYSTEM "lt.xml">
+<!ENTITY nl SYSTEM "nl.xml">
+<!ENTITY nn SYSTEM "nn.xml">
+<!ENTITY no SYSTEM "no.xml">
+<!ENTITY pl SYSTEM "pl.xml">
+<!ENTITY pt SYSTEM "pt.xml">
+<!ENTITY pt_br SYSTEM "pt_br.xml">
+<!ENTITY ro SYSTEM "ro.xml">
+<!ENTITY ru SYSTEM "ru.xml">
+<!ENTITY sk SYSTEM "sk.xml">
+<!ENTITY sl SYSTEM "sl.xml">
+<!ENTITY sr SYSTEM "sr.xml">
+<!ENTITY sr_Latn SYSTEM "sr_Latn.xml">
+<!ENTITY sv SYSTEM "sv.xml">
+<!ENTITY th SYSTEM "th.xml">
+<!ENTITY tr SYSTEM "tr.xml">
+<!ENTITY uk SYSTEM "uk.xml">
+<!ENTITY vi SYSTEM "vi.xml">
+<!ENTITY xh SYSTEM "xh.xml">
+<!ENTITY zh_cn SYSTEM "zh_cn.xml">
+<!ENTITY zh_tw SYSTEM "zh_tw.xml">
+]>
+<l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
+&af;
+&bg;
+&bn;
+&ca;
+&cs;
+&da;
+&de;
+&el;
+&en;
+&es;
+&et;
+&eu;
+&fi;
+&fr;
+&he;
+&hu;
+&id;
+&it;
+&ja;
+&ko;
+&la;
+&lit;
+&nl;
+&nn;
+&no;
+&pl;
+&pt;
+&pt_br;
+&ro;
+&ru;
+&sk;
+&sl;
+&sr;
+&sr_Latn;
+&sv;
+&th;
+&tr;
+&uk;
+&vi;
+&xh;
+&zh_cn;
+&zh_tw;
+</l:i18n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/l10n.xsl b/docs-xml/xslt/db2latex-xsl/xsl/common/l10n.xsl
new file mode 100644
index 00000000000..d573bda19eb
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/l10n.xsl
@@ -0,0 +1,467 @@
+<?xml version='1.0'?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0"
+                exclude-result-prefixes="l"
+                version='1.0'>
+
+<!-- ********************************************************************
+     $Id: l10n.xsl,v 1.8 2004/01/28 02:09:23 j-devenish Exp $
+     ********************************************************************
+
+     This file is part of the XSL DocBook Stylesheet distribution.
+
+     This file contains localization templates (for internationalization)
+
+     Copyright (C) 1999, 2000, 2001, 2002 Norman Walsh.
+     ******************************************************************** -->
+
+<xsl:param name="l10n.xml" select="document('../common/l10n.xml')"/>
+<xsl:param name="local.l10n.xml" select="document('')"/>
+<xsl:param name="l10n.gentext.language" select="''"/>
+<xsl:param name="l10n.gentext.default.language" select="'fr'"/>
+<xsl:param name="l10n.gentext.use.xref.language" select="false()"/>
+
+<xsl:template name="l10n.language">
+  <xsl:param name="target" select="."/>
+  <xsl:param name="xref-context" select="false()"/>
+
+  <xsl:variable name="mc-language">
+    <xsl:choose>
+      <xsl:when test="$l10n.gentext.language != ''">
+        <xsl:value-of select="$l10n.gentext.language"/>
+      </xsl:when>
+
+      <xsl:when test="$xref-context or $l10n.gentext.use.xref.language != 0">
+        <!-- can't do this one step: attributes are unordered! -->
+        <xsl:variable name="lang-scope"
+                      select="($target/ancestor-or-self::*[@lang]
+                               |$target/ancestor-or-self::*[@xml:lang])[last()]"/>
+        <xsl:variable name="lang-attr"
+                      select="($lang-scope/@lang | $lang-scope/@xml:lang)[1]"/>
+        <xsl:choose>
+          <xsl:when test="string($lang-attr) = ''">
+            <xsl:value-of select="$l10n.gentext.default.language"/>
+          </xsl:when>
+          <xsl:otherwise>
+            <xsl:value-of select="$lang-attr"/>
+          </xsl:otherwise>
+        </xsl:choose>
+      </xsl:when>
+
+      <xsl:otherwise>
+        <!-- can't do this one step: attributes are unordered! -->
+        <xsl:variable name="lang-scope"
+                      select="($target/ancestor-or-self::*[@lang]
+                           |$target/ancestor-or-self::*[@xml:lang])[last()]"/>
+        <xsl:variable name="lang-attr"
+                      select="($lang-scope/@lang | $lang-scope/@xml:lang)[1]"/>
+
+        <xsl:choose>
+          <xsl:when test="string($lang-attr) = ''">
+            <xsl:value-of select="$l10n.gentext.default.language"/>
+          </xsl:when>
+          <xsl:otherwise>
+            <xsl:value-of select="$lang-attr"/>
+          </xsl:otherwise>
+        </xsl:choose>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:variable name="language" select="translate($mc-language,
+                                        'ABCDEFGHIJKLMNOPQRSTUVWXYZ',
+                                        'abcdefghijklmnopqrstuvwxyz')"/>
+
+  <xsl:variable name="adjusted.language">
+    <xsl:choose>
+      <xsl:when test="contains($language,'-')">
+        <xsl:value-of select="substring-before($language,'-')"/>
+        <xsl:text>_</xsl:text>
+        <xsl:value-of select="substring-after($language,'-')"/>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:value-of select="$language"/>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:choose>
+    <xsl:when test="$l10n.xml/l:i18n/l:l10n[@language=$adjusted.language]">
+      <xsl:value-of select="$adjusted.language"/>
+    </xsl:when>
+    <!-- try just the lang code without country -->
+    <xsl:when test="$l10n.xml/l:i18n/l:l10n[@language=substring-before($adjusted.language,'_')]">
+      <xsl:value-of select="substring-before($adjusted.language,'_')"/>
+    </xsl:when>
+    <!-- or use the default -->
+    <xsl:otherwise>
+      <xsl:message>
+        <xsl:text>No localization exists for "</xsl:text>
+        <xsl:value-of select="$adjusted.language"/>
+        <xsl:text>" or "</xsl:text>
+        <xsl:value-of select="substring-before($adjusted.language,'_')"/>
+        <xsl:text>". Using default "</xsl:text>
+        <xsl:value-of select="$l10n.gentext.default.language"/>
+        <xsl:text>".</xsl:text>
+      </xsl:message>
+      <xsl:value-of select="$l10n.gentext.default.language"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="language.attribute">
+  <xsl:param name="node" select="."/>
+
+  <xsl:variable name="language">
+    <xsl:choose>
+      <xsl:when test="$l10n.gentext.language != ''">
+        <xsl:value-of select="$l10n.gentext.language"/>
+      </xsl:when>
+
+      <xsl:otherwise>
+        <!-- can't do this one step: attributes are unordered! -->
+        <xsl:variable name="lang-scope"
+                      select="($node/ancestor-or-self::*[@lang]
+                               |$node/ancestor-or-self::*[@xml:lang])[last()]"/>
+        <xsl:variable name="lang-attr"
+                      select="($lang-scope/@lang | $lang-scope/@xml:lang)[1]"/>
+
+        <xsl:choose>
+          <xsl:when test="string($lang-attr) = ''">
+            <xsl:value-of select="$l10n.gentext.default.language"/>
+          </xsl:when>
+          <xsl:otherwise>
+            <xsl:value-of select="$lang-attr"/>
+          </xsl:otherwise>
+        </xsl:choose>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:if test="$language != ''">
+    <xsl:attribute name="lang">
+      <xsl:value-of select="$language"/>
+    </xsl:attribute>
+  </xsl:if>
+</xsl:template>
+
+<xsl:template name="gentext">
+  <xsl:param name="key" select="local-name(.)"/>
+  <xsl:param name="lang">
+    <xsl:call-template name="l10n.language"/>
+  </xsl:param>
+
+  <xsl:variable name="local.l10n.gentext"
+                select="($local.l10n.xml//l:i18n/l:l10n[@language=$lang]/l:gentext[@key=$key])[1]"/>
+
+  <xsl:variable name="l10n.gentext"
+                select="($l10n.xml/l:i18n/l:l10n[@language=$lang]/l:gentext[@key=$key])[1]"/>
+
+  <xsl:choose>
+    <xsl:when test="count($local.l10n.gentext) &gt; 0">
+      <xsl:value-of select="$local.l10n.gentext/@text"/>
+    </xsl:when>
+    <xsl:when test="count($l10n.gentext) &gt; 0">
+      <xsl:value-of select="$l10n.gentext/@text"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:message>
+        <xsl:text>No "</xsl:text>
+        <xsl:value-of select="$lang"/>
+        <xsl:text>" localization of "</xsl:text>
+        <xsl:value-of select="$key"/>
+        <xsl:text>" exists</xsl:text>
+	<xsl:choose>
+	  <xsl:when test="$lang = 'en'">
+	     <xsl:text>.</xsl:text>
+	  </xsl:when>
+	  <xsl:otherwise>
+	     <xsl:text>; using "en".</xsl:text>
+	  </xsl:otherwise>
+	</xsl:choose>
+      </xsl:message>
+
+      <xsl:value-of select="($l10n.xml/l:i18n/l:l10n[@language='en']/l:gentext[@key=$key])[1]/@text"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="gentext.element.name">
+  <xsl:param name="element.name" select="name(.)"/>
+  <xsl:param name="lang">
+    <xsl:call-template name="l10n.language"/>
+  </xsl:param>
+
+  <xsl:call-template name="gentext">
+    <xsl:with-param name="key" select="$element.name"/>
+    <xsl:with-param name="lang" select="$lang"/>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.space">
+  <xsl:text> </xsl:text>
+</xsl:template>
+
+<xsl:template name="gentext.edited.by">
+  <xsl:call-template name="gentext">
+    <xsl:with-param name="key" select="'Editedby'"/>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.by">
+  <xsl:call-template name="gentext">
+    <xsl:with-param name="key" select="'by'"/>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.dingbat">
+  <xsl:param name="dingbat">bullet</xsl:param>
+  <xsl:param name="lang">
+    <xsl:call-template name="l10n.language"/>
+  </xsl:param>
+
+  <xsl:variable name="local.l10n.dingbat"
+                select="($local.l10n.xml//l:i18n/l:l10n[@language=$lang]/l:dingbat[@key=$dingbat])[1]"/>
+
+  <xsl:variable name="l10n.dingbat"
+                select="($l10n.xml/l:i18n/l:l10n[@language=$lang]/l:dingbat[@key=$dingbat])[1]"/>
+
+  <xsl:choose>
+    <xsl:when test="count($local.l10n.dingbat) &gt; 0">
+      <xsl:value-of select="$local.l10n.dingbat/@text"/>
+    </xsl:when>
+    <xsl:when test="count($l10n.dingbat) &gt; 0">
+      <xsl:value-of select="$l10n.dingbat/@text"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:message>
+        <xsl:text>No "</xsl:text>
+        <xsl:value-of select="$lang"/>
+        <xsl:text>" localization of dingbat </xsl:text>
+        <xsl:value-of select="$dingbat"/>
+        <xsl:text> exists; using "en".</xsl:text>
+      </xsl:message>
+
+      <xsl:value-of select="($l10n.xml/l:i18n/l:l10n[@language='en']/l:dingbat[@key=$dingbat])[1]/@text"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="gentext.startquote">
+  <xsl:call-template name="gentext.dingbat">
+    <xsl:with-param name="dingbat">startquote</xsl:with-param>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.endquote">
+  <xsl:call-template name="gentext.dingbat">
+    <xsl:with-param name="dingbat">endquote</xsl:with-param>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.nestedstartquote">
+  <xsl:call-template name="gentext.dingbat">
+    <xsl:with-param name="dingbat">nestedstartquote</xsl:with-param>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.nestedendquote">
+  <xsl:call-template name="gentext.dingbat">
+    <xsl:with-param name="dingbat">nestedendquote</xsl:with-param>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.nav.prev">
+  <xsl:call-template name="gentext">
+    <xsl:with-param name="key" select="'nav-prev'"/>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.nav.next">
+  <xsl:call-template name="gentext">
+    <xsl:with-param name="key" select="'nav-next'"/>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.nav.home">
+  <xsl:call-template name="gentext">
+    <xsl:with-param name="key" select="'nav-home'"/>
+  </xsl:call-template>
+</xsl:template>
+
+<xsl:template name="gentext.nav.up">
+  <xsl:call-template name="gentext">
+    <xsl:with-param name="key" select="'nav-up'"/>
+  </xsl:call-template>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template name="gentext.template">
+  <xsl:param name="context" select="'default'"/>
+  <xsl:param name="name" select="'default'"/>
+  <xsl:param name="origname" select="$name"/>
+  <xsl:param name="purpose"/>
+  <xsl:param name="xrefstyle"/>
+  <xsl:param name="referrer"/>
+  <xsl:param name="lang">
+    <xsl:call-template name="l10n.language"/>
+  </xsl:param>
+
+  <xsl:variable name="local.localization.node"
+                select="($local.l10n.xml//l:i18n/l:l10n[@language=$lang])[1]"/>
+
+  <xsl:variable name="localization.node"
+                select="($l10n.xml/l:i18n/l:l10n[@language=$lang])[1]"/>
+
+  <xsl:if test="count($localization.node) = 0
+                and count($local.localization.node) = 0">
+    <xsl:message>
+      <xsl:text>No "</xsl:text>
+      <xsl:value-of select="$lang"/>
+      <xsl:text>" localization exists.</xsl:text>
+    </xsl:message>
+  </xsl:if>
+
+  <xsl:variable name="local.context.node"
+                select="$local.localization.node/l:context[@name=$context]"/>
+
+  <xsl:variable name="context.node"
+                select="$localization.node/l:context[@name=$context]"/>
+
+  <xsl:variable name="en.context.node"
+                select="$l10n.xml/l:i18n/l:l10n[@language='en']/l:context[@name=$context]"/>
+
+  <xsl:if test="count($context.node) = 0
+                and count($local.context.node) = 0">
+    <xsl:message>
+      <xsl:text>No context named "</xsl:text>
+      <xsl:value-of select="$context"/>
+      <xsl:text>" exists in the "</xsl:text>
+      <xsl:value-of select="$lang"/>
+      <xsl:text>" localization; trying "en".</xsl:text>
+    </xsl:message>
+  </xsl:if>
+
+  <xsl:variable name="local.template.node"
+                select="($local.context.node/l:template[@name=$name
+                                                        and @style
+                                                        and @style=$xrefstyle]
+                        |$local.context.node/l:template[@name=$name
+                                                        and not(@style)])[1]"/>
+
+  <xsl:variable name="template.node"
+                select="($context.node/l:template[@name=$name
+                                                  and @style
+                                                  and @style=$xrefstyle]
+                        |$context.node/l:template[@name=$name
+                                                  and not(@style)])[1]"/>
+
+  <xsl:variable name="en.template.node"
+                select="($en.context.node/l:template[@name=$name
+                                                  and @style
+                                                  and @style=$xrefstyle]
+                        |$en.context.node/l:template[@name=$name
+                                                  and not(@style)])[1]"/>
+
+  <xsl:choose>
+    <xsl:when test="$local.template.node/@text">
+      <xsl:value-of select="$local.template.node/@text"/>
+    </xsl:when>
+    <xsl:when test="$template.node/@text">
+      <xsl:value-of select="$template.node/@text"/>
+    </xsl:when>
+    <xsl:when test="$en.template.node/@text">
+      <xsl:value-of select="$en.template.node/@text"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:choose>
+        <xsl:when test="contains($name, '/')">
+          <xsl:call-template name="gentext.template">
+            <xsl:with-param name="context" select="$context"/>
+            <xsl:with-param name="name" select="substring-after($name, '/')"/>
+            <xsl:with-param name="origname" select="$origname"/>
+            <xsl:with-param name="purpose" select="$purpose"/>
+            <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+            <xsl:with-param name="referrer" select="$referrer"/>
+            <xsl:with-param name="lang" select="$lang"/>
+          </xsl:call-template>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:message>
+            <xsl:text>No template for "</xsl:text>
+            <xsl:value-of select="$origname"/>
+            <xsl:text>" (or any of its leaves) exists
+in the context named "</xsl:text>
+            <xsl:value-of select="$context"/>
+            <xsl:text>" in the "</xsl:text>
+            <xsl:value-of select="$lang"/>
+            <xsl:text>" localization.</xsl:text>
+          </xsl:message>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template name="gentext.template.exists">
+  <xsl:param name="context" select="'default'"/>
+  <xsl:param name="name" select="'default'"/>
+  <xsl:param name="origname" select="$name"/>
+  <xsl:param name="purpose"/>
+  <xsl:param name="xrefstyle"/>
+  <xsl:param name="referrer"/>
+  <xsl:param name="lang">
+    <xsl:call-template name="l10n.language"/>
+  </xsl:param>
+
+  <xsl:variable name="local.localization.node"
+                select="($local.l10n.xml//l:i18n/l:l10n[@language=$lang])[1]"/>
+
+  <xsl:variable name="localization.node"
+                select="($l10n.xml/l:i18n/l:l10n[@language=$lang])[1]"/>
+
+  <xsl:variable name="local.context.node"
+                select="$local.localization.node/l:context[@name=$context]"/>
+
+  <xsl:variable name="context.node"
+                select="$localization.node/l:context[@name=$context]"/>
+
+  <xsl:variable name="local.template.node"
+                select="($local.context.node/l:template[@name=$name
+                                                        and @style
+                                                        and @style=$xrefstyle]
+                        |$local.context.node/l:template[@name=$name
+                                                        and not(@style)])[1]"/>
+
+  <xsl:variable name="template.node"
+                select="($context.node/l:template[@name=$name
+                                                  and @style
+                                                  and @style=$xrefstyle]
+                        |$context.node/l:template[@name=$name
+                                                  and not(@style)])[1]"/>
+
+  <xsl:choose>
+    <xsl:when test="$local.template.node/@text">1</xsl:when>
+    <xsl:when test="$template.node/@text">1</xsl:when>
+    <xsl:otherwise>
+      <xsl:choose>
+        <xsl:when test="contains($name, '/')">
+          <xsl:call-template name="gentext.template.exists">
+            <xsl:with-param name="context" select="$context"/>
+            <xsl:with-param name="name" select="substring-after($name, '/')"/>
+            <xsl:with-param name="origname" select="$origname"/>
+            <xsl:with-param name="purpose" select="$purpose"/>
+            <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+            <xsl:with-param name="referrer" select="$referrer"/>
+            <xsl:with-param name="lang" select="$lang"/>
+          </xsl:call-template>
+        </xsl:when>
+        <xsl:otherwise>0</xsl:otherwise>
+      </xsl:choose>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/la.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/la.xml
new file mode 100644
index 00000000000..fb4120934a8
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/la.xml
@@ -0,0 +1,492 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="la" english-language-name="Latin">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/la.xml -->
+  <l:gentext key="Abstract" text="Summarium"/>
+  <l:gentext key="abstract" text="summarium"/>
+  <l:gentext key="Answer" text="R:"/>
+  <l:gentext key="answer" text="r:"/>
+  <l:gentext key="Appendix" text="Additamentum"/>
+  <l:gentext key="appendix" text="additamentum"/>
+  <l:gentext key="Article" text="Articulus"/>
+  <l:gentext key="article" text="articulus"/>
+  <l:gentext key="Bibliography" text="Conspectus librorum"/>
+  <l:gentext key="bibliography" text="conspectus librorum"/>
+  <l:gentext key="Book" text="Liber"/>
+  <l:gentext key="book" text="liber"/>
+  <l:gentext key="CAUTION" text="Caveat"/>
+  <l:gentext key="Caution" text="Caveat"/>
+  <l:gentext key="caution" text="caveat"/>
+  <l:gentext key="Chapter" text="Capitulum"/>
+  <l:gentext key="chapter" text="capitulum"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="copyright"/>
+  <l:gentext key="Dedication" text="Dedicatoria"/>
+  <l:gentext key="dedication" text="dedicatoria"/>
+  <l:gentext key="Edition" text="Editio"/>
+  <l:gentext key="edition" text="editio"/>
+  <l:gentext key="Equation" text="Equatio"/>
+  <l:gentext key="equation" text="equatio"/>
+  <l:gentext key="Example" text="Exemplum"/>
+  <l:gentext key="example" text="exemplum"/>
+  <l:gentext key="Figure" text="Descriptio"/>
+  <l:gentext key="figure" text="descriptio"/>
+  <l:gentext key="Glossary" text="Glossarium"/>
+  <l:gentext key="glossary" text="glossarium"/>
+  <l:gentext key="GlossSee" text="Cfr."/>
+  <l:gentext key="glosssee" text="Cfr."/>
+  <l:gentext key="GlossSeeAlso" text="Cfr. autem"/>
+  <l:gentext key="glossseealso" text="cfr. autem"/>
+  <l:gentext key="IMPORTANT" text="GRAVE"/>
+  <l:gentext key="important" text="grave"/>
+  <l:gentext key="Important" text="Grave"/>
+  <l:gentext key="Index" text="Index"/>
+  <l:gentext key="index" text="index"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="isbn"/>
+  <l:gentext key="LegalNotice" text="Nuntius legalis"/>
+  <l:gentext key="legalnotice" text="nuntius legalis"/>
+  <l:gentext key="MsgAud" text="Legentes"/>
+  <l:gentext key="msgaud" text="legentes"/>
+  <l:gentext key="MsgLevel" text="Libra"/>
+  <l:gentext key="msglevel" text="libra"/>
+  <l:gentext key="MsgOrig" text="Fons"/>
+  <l:gentext key="msgorig" text="fons"/>
+  <l:gentext key="NOTE" text="NOTA"/>
+  <l:gentext key="Note" text="Nota"/>
+  <l:gentext key="note" text="nota"/>
+  <l:gentext key="Part" text="Pars"/>
+  <l:gentext key="part" text="pars"/>
+  <l:gentext key="Preface" text="Praefatio"/>
+  <l:gentext key="preface" text="praefatio"/>
+  <l:gentext key="Procedure" text="Progressio"/>
+  <l:gentext key="procedure" text="progressio"/>
+  <l:gentext key="ProductionSet" text="Compositio"/>
+  <l:gentext key="Published" text="Editum"/>
+  <l:gentext key="published" text="editum"/>
+  <l:gentext key="Question" text="Q:"/>
+  <l:gentext key="question" text="q:"/>
+  <l:gentext key="RefEntry" text="Mentionis descriptio"/>
+  <l:gentext key="refentry" text="mentionis descriptio"/>
+  <l:gentext key="Reference" text="Mentio"/>
+  <l:gentext key="reference" text="mentio"/>
+  <l:gentext key="RefName" text="Mentionis signum"/>
+  <l:gentext key="refname" text="mentionis signum"/>
+  <l:gentext key="RefSection" text="Mentionis pars"/>
+  <l:gentext key="refsection" text="mentionis pars"/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Revisionum historia"/>
+  <l:gentext key="revhistory" text="revisionum historia"/>
+  <l:gentext key="revision" text="Revisio"/>
+  <l:gentext key="Revision" text="revisio"/>
+  <l:gentext key="sect1" text="Sectio"/>
+  <l:gentext key="sect2" text="Sectio"/>
+  <l:gentext key="sect3" text="Sectio"/>
+  <l:gentext key="sect4" text="Sectio"/>
+  <l:gentext key="sect5" text="Sectio"/>
+  <l:gentext key="section" text="Sectio"/>
+  <l:gentext key="Section" text="Sectio"/>
+  <l:gentext key="see" text="videtur"/>
+  <l:gentext key="seealso" text="videtur autem"/>
+  <l:gentext key="set" text="complexus"/>
+  <l:gentext key="Set" text="Complexus"/>
+  <l:gentext key="setindex" text="complexi index"/>
+  <l:gentext key="SetIndex" text="Complexi index"/>
+  <l:gentext key="Sidebar" text="Linea a latere posita"/>
+  <l:gentext key="sidebar" text="linea a latere posita"/>
+  <l:gentext key="step" text="peractio"/>
+  <l:gentext key="Step" text="Peractio"/>
+  <l:gentext key="Table" text="Tabula"/>
+  <l:gentext key="table" text="tabula"/>
+  <l:gentext key="tip" text="consilium"/>
+  <l:gentext key="TIP" text="CONSILIUM"/>
+  <l:gentext key="Tip" text="Consilium"/>
+  <l:gentext key="Warning" text="MONITUS"/>
+  <l:gentext key="warning" text="monitus"/>
+  <l:gentext key="WARNING" text="MONITUS"/>
+  <l:gentext key="and" text="et"/>
+  <l:gentext key="by" text="a"/>
+  <l:gentext key="Edited" text="Editum"/>
+  <l:gentext key="edited" text="editum"/>
+  <l:gentext key="Editedby" text="Editum a"/>
+  <l:gentext key="editedby" text="editum a"/>
+  <l:gentext key="in" text="in"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="quod non est"/>
+  <l:gentext key="notes" text="commentaria"/>
+  <l:gentext key="Notes" text="Commentaria"/>
+  <l:gentext key="Pgs" text="Pag."/>
+  <l:gentext key="pgs" text="pag."/>
+  <l:gentext key="Revisedby" text="Excussum a: "/>
+  <l:gentext key="revisedby" text="excussum a: "/>
+  <l:gentext key="TableNotes" text="Tabulae commentaria"/>
+  <l:gentext key="tablenotes" text="tabulae commentaria"/>
+  <l:gentext key="TableofContents" text="Index rerum notabilium"/>
+  <l:gentext key="tableofcontents" text="index rerum notabilium"/>
+  <l:gentext key="unexpectedelementname" text="necopinatum nomen"/>
+  <l:gentext key="unsupported" text="non sustentatus"/>
+  <l:gentext key="xrefto" text="mentio"/>
+  <l:gentext key="listofequations" text="index aequationum"/>
+  <l:gentext key="ListofEquations" text="Index aequationum"/>
+  <l:gentext key="ListofExamples" text="Index exemplorum"/>
+  <l:gentext key="listofexamples" text="index exemplorum"/>
+  <l:gentext key="ListofFigures" text="Index descriptionum"/>
+  <l:gentext key="listoffigures" text="index descriptionum"/>
+  <l:gentext key="ListofProcedures" text="Index progressiorum"/>
+  <l:gentext key="listofprocedures" text="index progressiorum"/>
+  <l:gentext key="listoftables" text="index tabularum"/>
+  <l:gentext key="ListofTables" text="Index tabularum"/>
+  <l:gentext key="ListofUnknown" text="Index ignotorum"/>
+  <l:gentext key="listofunknown" text="index ignotorum"/>
+  <l:gentext key="nav-home" text="Initium"/>
+  <l:gentext key="nav-next" text="Sequens"/>
+  <l:gentext key="nav-next-sibling" text="Procede"/>
+  <l:gentext key="nav-prev" text="Praecedens"/>
+  <l:gentext key="nav-prev-sibling" text="Recede"/>
+  <l:gentext key="nav-up" text="Ascende"/>
+  <l:gentext key="nav-toc" text="Index"/>
+  <l:gentext key="Draft" text="Plagula"/>
+  <l:gentext key="above" text="supra"/>
+  <l:gentext key="below" text="sub"/>
+  <l:gentext key="sectioncalled" text="sectio vocata"/>
+  <l:gentext key="index symbols" text="signa"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+  <l:gentext key="hyphenation-character" text="&#8208;"/>
+  <l:gentext key="hyphenation-push-character-count" text="2"/>
+  <l:gentext key="hyphenation-remain-character-count" text="2"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/la.xml -->
+  <l:dingbat key="startquote" text="&#738;"/>
+  <l:dingbat key="endquote" text="&#1762;"/>
+  <l:dingbat key="nestedstartquote" text="&#8249;"/>
+  <l:dingbat key="nestedendquote" text="&#8250;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Additamentum%n.%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Capitulum%n.%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Equatio%n.%t"/>
+    <l:template name="example" text="Exemplum%n.%t"/>
+    <l:template name="figure" text="Descriptio%n.%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Pars%n.%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Progressio%n.%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Compositio%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabula%n.%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Additamentum%n.%t"/>
+    <l:template name="article/appendix" text="%n.%t"/>
+    <l:template name="bridgehead" text="%n.%t"/>
+    <l:template name="chapter" text="Capitulum%n.%t"/>
+    <l:template name="sect1" text="%n.%t"/>
+    <l:template name="sect2" text="%n.%t"/>
+    <l:template name="sect3" text="%n.%t"/>
+    <l:template name="sect4" text="%n.%t"/>
+    <l:template name="sect5" text="%n.%t"/>
+    <l:template name="section" text="%n.%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="R:%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Q:%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Q:%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="refsection" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="refsect1" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="refsect2" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="refsect3" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="sect1" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="sect2" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="sect3" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="sect4" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="sect5" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="section" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="simplesect" text="sectio vocata &#738;%t&#1762;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="R:%n"/>
+    <l:template name="appendix" text="Additamentum%n"/>
+    <l:template name="bridgehead" text="Sectio%n"/>
+    <l:template name="chapter" text="Capitulum%n"/>
+    <l:template name="equation" text="Equatio%n"/>
+    <l:template name="example" text="Exemplum%n"/>
+    <l:template name="figure" text="Descriptio%n"/>
+    <l:template name="part" text="Pars%n"/>
+    <l:template name="procedure" text="Progressio%n"/>
+    <l:template name="productionset" text="Compositio%n"/>
+    <l:template name="qandadiv" text="Q &amp; A%n"/>
+    <l:template name="qandaentry" text="Q:%n"/>
+    <l:template name="question" text="Q:%n"/>
+    <l:template name="sect1" text="Sectio%n"/>
+    <l:template name="sect2" text="Sectio%n"/>
+    <l:template name="sect3" text="Sectio%n"/>
+    <l:template name="sect4" text="Sectio%n"/>
+    <l:template name="sect5" text="Sectio%n"/>
+    <l:template name="section" text="Sectio%n"/>
+    <l:template name="table" text="Tabula%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Additamentum%n, %t"/>
+    <l:template name="bridgehead" text="Sectio%n, &#738;%t&#1762;"/>
+    <l:template name="chapter" text="Capitulum%n, %t"/>
+    <l:template name="equation" text="Equatio%n, &#738;%t&#1762;"/>
+    <l:template name="example" text="Exemplum%n, &#738;%t&#1762;"/>
+    <l:template name="figure" text="Descriptio%n, &#738;%t&#1762;"/>
+    <l:template name="part" text="Pars%n, &#738;%t&#1762;"/>
+    <l:template name="procedure" text="Progressio%n, &#738;%t&#1762;"/>
+    <l:template name="productionset" text="Compositio%n, &#738;%t&#1762;"/>
+    <l:template name="qandadiv" text="Q &amp; A%n, &#738;%t&#1762;"/>
+    <l:template name="refsect1" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="refsect2" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="refsect3" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="refsection" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="sect1" text="Sectio%n, &#738;%t&#1762;"/>
+    <l:template name="sect2" text="Sectio%n, &#738;%t&#1762;"/>
+    <l:template name="sect3" text="Sectio%n, &#738;%t&#1762;"/>
+    <l:template name="sect4" text="Sectio%n, &#738;%t&#1762;"/>
+    <l:template name="sect5" text="Sectio%n, &#738;%t&#1762;"/>
+    <l:template name="section" text="Sectio%n, &#738;%t&#1762;"/>
+    <l:template name="simplesect" text="sectio vocata &#738;%t&#1762;"/>
+    <l:template name="table" text="Tabula%n, &#738;%t&#1762;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" et "/>
+    <l:template name="seplast" text=", et "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Cfr. "/>
+    <l:template name="seealso" text="Cfr. autem "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Legentes: "/>
+    <l:template name="MsgLevel" text="Libra: "/>
+    <l:template name="MsgOrig" text="Fons: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d/m/Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="Ianuarii"/>
+    <l:template name="February" text="Februarii"/>
+    <l:template name="March" text="Martii"/>
+    <l:template name="April" text="Aprilis"/>
+    <l:template name="May" text="Maii"/>
+    <l:template name="June" text="Iunii"/>
+    <l:template name="July" text="Iulii"/>
+    <l:template name="August" text="Augusti"/>
+    <l:template name="September" text="Septembris"/>
+    <l:template name="October" text="Octobris"/>
+    <l:template name="November" text="Novembris"/>
+    <l:template name="December" text="Decembris"/>
+    <l:template name="Monday" text="Lunae"/>
+    <l:template name="Tuesday" text="Martis"/>
+    <l:template name="Wednesday" text="Mercurii"/>
+    <l:template name="Thursday" text="Iovis"/>
+    <l:template name="Friday" text="Veneris"/>
+    <l:template name="Saturday" text="Sabathi"/>
+    <l:template name="Sunday" text="Dominica"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="Ian"/>
+    <l:template name="Feb" text="Feb"/>
+    <l:template name="Mar" text="Mar"/>
+    <l:template name="Apr" text="Apr"/>
+    <l:template name="May" text="Mai"/>
+    <l:template name="Jun" text="Iun"/>
+    <l:template name="Jul" text="Iul"/>
+    <l:template name="Aug" text="Aug"/>
+    <l:template name="Sep" text="Sep"/>
+    <l:template name="Oct" text="Oct"/>
+    <l:template name="Nov" text="Nov"/>
+    <l:template name="Dec" text="Dec"/>
+    <l:template name="Mon" text="Lun"/>
+    <l:template name="Tue" text="Mar"/>
+    <l:template name="Wed" text="Mer"/>
+    <l:template name="Thu" text="Iov"/>
+    <l:template name="Fri" text="Ven"/>
+    <l:template name="Sat" text="Sab"/>
+    <l:template name="Sun" text="Dom"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/lt.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/lt.xml
new file mode 100644
index 00000000000..6637fb14609
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/lt.xml
@@ -0,0 +1,442 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="lt" english-language-name="Lithuanian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/lt.xml -->
+  <l:gentext key="Abstract" text="Santrauka"/>
+  <l:gentext key="abstract" text="Santrauka"/>
+  <l:gentext key="Answer" text="Ats:"/>
+  <l:gentext key="answer" text="Ats:"/>
+  <l:gentext key="Appendix" text="Priedas"/>
+  <l:gentext key="appendix" text="priedas"/>
+  <l:gentext key="Article" text="Straipsnis"/>
+  <l:gentext key="article" text="Straipsnis"/>
+  <l:gentext key="Bibliography" text="Bibliografija"/>
+  <l:gentext key="bibliography" text="Bibliografija"/>
+  <l:gentext key="Book" text="Knyga"/>
+  <l:gentext key="book" text="Knyga"/>
+  <l:gentext key="CAUTION" text="ATSARGIAI"/>
+  <l:gentext key="Caution" text="Atsargiai"/>
+  <l:gentext key="caution" text="Atsargiai"/>
+  <l:gentext key="Chapter" text="Skyrius"/>
+  <l:gentext key="chapter" text="skyrius"/>
+  <l:gentext key="Colophon" text="&#302;&#382;anga &#303; knyg&#261;"/>
+  <l:gentext key="colophon" text="&#302;&#382;anga &#303; knyg&#336;"/>
+  <l:gentext key="Copyright" text="Autorin&#279;s teis&#279;s"/>
+  <l:gentext key="copyright" text="Autorin&#279;s teis&#279;s"/>
+  <l:gentext key="Dedication" text="Dedikacija"/>
+  <l:gentext key="dedication" text="Dedikacija"/>
+  <l:gentext key="Edition" text="Leidimas"/>
+  <l:gentext key="edition" text="Leidimas"/>
+  <l:gentext key="Equation" text="Lygtis"/>
+  <l:gentext key="equation" text="Lygtis"/>
+  <l:gentext key="Example" text="Pavyzdys"/>
+  <l:gentext key="example" text="Pavyzdys"/>
+  <l:gentext key="Figure" text="Pav."/>
+  <l:gentext key="figure" text="Pav."/>
+  <l:gentext key="Glossary" text="Termin&#371; &#382;odyn&#279;lis"/>
+  <l:gentext key="glossary" text="Termin&#371; &#382;odyn&#279;lis"/>
+  <l:gentext key="GlossSee" text="Termin&#261; &#382;r."/>
+  <l:gentext key="glosssee" text="Termin&#261; &#382;r."/>
+  <l:gentext key="GlossSeeAlso" text="Taip pat &#382;r."/>
+  <l:gentext key="glossseealso" text="Taip pat &#382;r."/>
+  <l:gentext key="IMPORTANT" text="SVARBU"/>
+  <l:gentext key="important" text="Svarbu"/>
+  <l:gentext key="Important" text="Svarbu"/>
+  <l:gentext key="Index" text="Rodykl&#279;"/>
+  <l:gentext key="index" text="Rodykl&#279;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Teisin&#279; pastaba"/>
+  <l:gentext key="legalnotice" text="Teisin&#279; pastaba"/>
+  <l:gentext key="MsgAud" text="Auditorija"/>
+  <l:gentext key="msgaud" text="Auditorija"/>
+  <l:gentext key="MsgLevel" text="Lygmuo"/>
+  <l:gentext key="msglevel" text="Lygmuo"/>
+  <l:gentext key="MsgOrig" text="Kilm&#279;"/>
+  <l:gentext key="msgorig" text="Kilm&#279;"/>
+  <l:gentext key="NOTE" text="PASTABA"/>
+  <l:gentext key="Note" text="Pastaba"/>
+  <l:gentext key="note" text="Pastaba"/>
+  <l:gentext key="Part" text="Dalis"/>
+  <l:gentext key="part" text="Dalis"/>
+  <l:gentext key="Preface" text="&#302;&#382;anga"/>
+  <l:gentext key="preface" text="&#302;&#382;anga"/>
+  <l:gentext key="Procedure" text="Proced&#363;ra"/>
+  <l:gentext key="procedure" text="Proced&#363;ra"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="I&#353;leistas"/>
+  <l:gentext key="published" text="I&#353;leistas"/>
+  <l:gentext key="Question" text="Klausimas:"/>
+  <l:gentext key="question" text="Klausimas:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Nuoroda"/>
+  <l:gentext key="reference" text="Nuoroda"/>
+  <l:gentext key="RefName" text="Pavadinimas"/>
+  <l:gentext key="refname" text="Pavadinimas"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Trumpa ap&#382;valga"/>
+  <l:gentext key="refsynopsisdiv" text="Trumpa ap&#382;valga"/>
+  <l:gentext key="RevHistory" text="Pataisym&#371; istorija"/>
+  <l:gentext key="revhistory" text="Pataisym&#371; istorija"/>
+  <l:gentext key="revision" text="Pataisytas leidimas"/>
+  <l:gentext key="Revision" text="Pataisytas leidimas"/>
+  <l:gentext key="sect1" text="Skyrius"/>
+  <l:gentext key="sect2" text="Skyrius"/>
+  <l:gentext key="sect3" text="Skyrius"/>
+  <l:gentext key="sect4" text="Skyrius"/>
+  <l:gentext key="sect5" text="Skyrius"/>
+  <l:gentext key="section" text="Skyrius"/>
+  <l:gentext key="Section" text="Skyrius"/>
+  <l:gentext key="see" text="&#382;r."/>
+  <l:gentext key="seealso" text="&#382;r."/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="setindex" text="Set Index"/>
+  <l:gentext key="SetIndex" text="Set Index"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="step" text="&#382;ingsnis"/>
+  <l:gentext key="Step" text="&#381;ingsnis"/>
+  <l:gentext key="Table" text="Lentel&#279;"/>
+  <l:gentext key="table" text="Lentel&#279;"/>
+  <l:gentext key="tip" text="Patarimas"/>
+  <l:gentext key="TIP" text="PATARIMAS"/>
+  <l:gentext key="Tip" text="Patarimas"/>
+  <l:gentext key="Warning" text="&#302;sp&#279;jimas"/>
+  <l:gentext key="warning" text="&#302;sp&#279;jimas"/>
+  <l:gentext key="WARNING" text="&#302;SP&#278;JIMAS"/>
+  <l:gentext key="and" text="ir"/>
+  <l:gentext key="by" text="by"/>
+  <l:gentext key="Edited" text="Redaguotas"/>
+  <l:gentext key="edited" text="Redaguotas"/>
+  <l:gentext key="Editedby" text="Redaguotas:"/>
+  <l:gentext key="editedby" text="Redaguotas:"/>
+  <l:gentext key="in" text="in"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="neegzistuojantis elementas"/>
+  <l:gentext key="notes" text="Pastabos"/>
+  <l:gentext key="Notes" text="Pastabos"/>
+  <l:gentext key="Pgs" text="Pgs."/>
+  <l:gentext key="pgs" text="Pgs."/>
+  <l:gentext key="Revisedby" text="Patais&#279;: "/>
+  <l:gentext key="revisedby" text="Patais&#279;: "/>
+  <l:gentext key="TableNotes" text="Lentel&#279;s pastabos"/>
+  <l:gentext key="tablenotes" text="Lentel&#279;s pastabos"/>
+  <l:gentext key="TableofContents" text="T&#363;rinys"/>
+  <l:gentext key="tableofcontents" text="T&#363;rinys"/>
+  <l:gentext key="unexpectedelementname" text="Unexpected element name"/>
+  <l:gentext key="unsupported" text="nepalaikomas"/>
+  <l:gentext key="xrefto" text="xref to"/>
+  <l:gentext key="listofequations" text="Lyg&#269;i&#371; s&#261;ra&#353;as"/>
+  <l:gentext key="ListofEquations" text="Lyg&#269;i&#371; s&#261;ra&#353;as"/>
+  <l:gentext key="ListofExamples" text="Pavyzd&#382;i&#371; s&#261;ra&#353;as"/>
+  <l:gentext key="listofexamples" text="Pavyzd&#382;i&#371; s&#261;ra&#353;as"/>
+  <l:gentext key="ListofFigures" text="Pav. s&#261;ra&#353;as"/>
+  <l:gentext key="listoffigures" text="Pav. s&#261;ra&#353;as"/>
+  <l:gentext key="listoftables" text="Lenteli&#371; s&#261;ra&#353;as"/>
+  <l:gentext key="ListofTables" text="Lenteli&#371; s&#261;ra&#353;as"/>
+  <l:gentext key="ListofUnknown" text="Ne&#382;inomas s&#261;ra&#353;as"/>
+  <l:gentext key="listofunknown" text="Ne&#382;inomas s&#261;ra&#353;as"/>
+  <l:gentext key="nav-home" text="Namai"/>
+  <l:gentext key="nav-next" text="Sekantis"/>
+  <l:gentext key="nav-next-sibling" text="Fast Forward"/>
+  <l:gentext key="nav-prev" text="Paskesnis"/>
+  <l:gentext key="nav-prev-sibling" text="Fast Backward"/>
+  <l:gentext key="nav-up" text="&#302; vir&#353;&#371;"/>
+  <l:gentext key="nav-toc" text="ToC"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/lt.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Priedas&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Skyrius&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Lygtis&#160;%n.&#160;%t"/>
+    <l:template name="example" text="Pavyzdys&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="Pav.&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Dalis&#160;%n.&#160;%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Proced&#363;ra&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Lentel&#279;&#160;%n.&#160;%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Priedas&#160;%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="Skyrius&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Ats:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Klausimas:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Klausimas:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="section" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Ats:&#160;%n"/>
+    <l:template name="appendix" text="Priedas&#160;%n"/>
+    <l:template name="bridgehead" text="Skyrius&#160;%n"/>
+    <l:template name="chapter" text="Skyrius&#160;%n"/>
+    <l:template name="equation" text="Lygtis&#160;%n"/>
+    <l:template name="example" text="Pavyzdys&#160;%n"/>
+    <l:template name="figure" text="Pav.&#160;%n"/>
+    <l:template name="part" text="Dalis&#160;%n"/>
+    <l:template name="procedure" text="Proced&#363;ra&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Klausimas:&#160;%n"/>
+    <l:template name="question" text="Klausimas:&#160;%n"/>
+    <l:template name="sect1" text="Skyrius&#160;%n"/>
+    <l:template name="sect2" text="Skyrius&#160;%n"/>
+    <l:template name="sect3" text="Skyrius&#160;%n"/>
+    <l:template name="sect4" text="Skyrius&#160;%n"/>
+    <l:template name="sect5" text="Skyrius&#160;%n"/>
+    <l:template name="section" text="Skyrius&#160;%n"/>
+    <l:template name="table" text="Lentel&#279;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Priedas&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Skyrius&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Skyrius&#160;%n, %t"/>
+    <l:template name="equation" text="Lygtis&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Pavyzdys&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Pav.&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Dalis&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Proced&#363;ra&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Skyrius&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Skyrius&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Skyrius&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Skyrius&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Skyrius&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Skyrius&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Lentel&#279;&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" ir "/>
+    <l:template name="seplast" text=", ir "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Termin&#261; &#382;r. "/>
+    <l:template name="seealso" text="Taip pat &#382;r. "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Auditorija: "/>
+    <l:template name="MsgLevel" text="Lygmuo: "/>
+    <l:template name="MsgOrig" text="Kilm&#279;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0427 Lithuanian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/nl.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/nl.xml
new file mode 100644
index 00000000000..2099a12fe73
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/nl.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="nl" english-language-name="Dutch">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/nl.xml -->
+  <l:gentext key="Abstract" text="Samenvatting"/>
+  <l:gentext key="abstract" text="Samenvatting"/>
+  <l:gentext key="Answer" text="Antwoord:"/>
+  <l:gentext key="answer" text="Antwoord:"/>
+  <l:gentext key="Appendix" text="Aanhangsel"/>
+  <l:gentext key="appendix" text="aanhangsel"/>
+  <l:gentext key="Article" text="Artikel"/>
+  <l:gentext key="article" text="Artikel"/>
+  <l:gentext key="Bibliography" text="Literatuurlijst"/>
+  <l:gentext key="bibliography" text="Literatuurlijst"/>
+  <l:gentext key="Book" text="Boek"/>
+  <l:gentext key="book" text="Boek"/>
+  <l:gentext key="CAUTION" text="LET OP"/>
+  <l:gentext key="Caution" text="Let op"/>
+  <l:gentext key="caution" text="Let op"/>
+  <l:gentext key="Chapter" text="Hoofdstuk"/>
+  <l:gentext key="chapter" text="hoofdstuk"/>
+  <l:gentext key="Colophon" text="Colofon"/>
+  <l:gentext key="colophon" text="Colofon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Opdracht"/>
+  <l:gentext key="dedication" text="Opdracht"/>
+  <l:gentext key="Edition" text="Uitgave"/>
+  <l:gentext key="edition" text="Uitgave"/>
+  <l:gentext key="Equation" text="Vergelijking"/>
+  <l:gentext key="equation" text="Vergelijking"/>
+  <l:gentext key="Example" text="Voorbeeld"/>
+  <l:gentext key="example" text="Voorbeeld"/>
+  <l:gentext key="Figure" text="Figuur"/>
+  <l:gentext key="figure" text="Figuur"/>
+  <l:gentext key="Glossary" text="Woordenlijst"/>
+  <l:gentext key="glossary" text="Woordenlijst"/>
+  <l:gentext key="GlossSee" text="Zie"/>
+  <l:gentext key="glosssee" text="Zie"/>
+  <l:gentext key="GlossSeeAlso" text="Zie ook"/>
+  <l:gentext key="glossseealso" text="Zie ook"/>
+  <l:gentext key="IMPORTANT" text="BELANGRIJK"/>
+  <l:gentext key="Important" text="Belangrijk"/>
+  <l:gentext key="important" text="Belangrijk"/>
+  <l:gentext key="Index" text="Register"/>
+  <l:gentext key="index" text="Register"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Bericht"/>
+  <l:gentext key="legalnotice" text="Bericht"/>
+  <l:gentext key="MsgAud" text="Doelgroep"/>
+  <l:gentext key="msgaud" text="Doelgroep"/>
+  <l:gentext key="MsgLevel" text="Niveau"/>
+  <l:gentext key="msglevel" text="Niveau"/>
+  <l:gentext key="MsgOrig" text="Herkomst"/>
+  <l:gentext key="msgorig" text="Herkomst"/>
+  <l:gentext key="NOTE" text="OPMERKING"/>
+  <l:gentext key="Note" text="Opmerking"/>
+  <l:gentext key="note" text="Opmerking"/>
+  <l:gentext key="Part" text="Deel"/>
+  <l:gentext key="part" text="Deel"/>
+  <l:gentext key="Preface" text="Voorwoord"/>
+  <l:gentext key="preface" text="Voorwoord"/>
+  <l:gentext key="Procedure" text="Procedure"/>
+  <l:gentext key="procedure" text="Procedure"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="Uitgegeven"/>
+  <l:gentext key="published" text="Uitgegeven"/>
+  <l:gentext key="Question" text="Vraag:"/>
+  <l:gentext key="question" text="Vraag:"/>
+  <l:gentext key="RefEntry" text="Referentielemma"/>
+  <l:gentext key="refentry" text="Referentielemma"/>
+  <l:gentext key="Reference" text="Referentie"/>
+  <l:gentext key="reference" text="Referentie"/>
+  <l:gentext key="RefName" text="Referentienaam"/>
+  <l:gentext key="refname" text="Referentienaam"/>
+  <l:gentext key="RefSection" text="Referentieparagraaf"/>
+  <l:gentext key="refsection" text="Referentieparagraaf"/>
+  <l:gentext key="RefSynopsisDiv" text="Referentiesamenvatting"/>
+  <l:gentext key="refsynopsisdiv" text="Referentiesamenvatting"/>
+  <l:gentext key="RevHistory" text="Wijzigingen"/>
+  <l:gentext key="revhistory" text="Wijzigingen"/>
+  <l:gentext key="Revision" text="Herziening"/>
+  <l:gentext key="revision" text="Herziening"/>
+  <l:gentext key="sect1" text="Paragraaf"/>
+  <l:gentext key="sect2" text="Paragraaf"/>
+  <l:gentext key="sect3" text="Paragraaf"/>
+  <l:gentext key="sect4" text="Paragraaf"/>
+  <l:gentext key="sect5" text="Paragraaf"/>
+  <l:gentext key="Section" text="Paragraaf"/>
+  <l:gentext key="section" text="paragraaf"/>
+  <l:gentext key="See" text="Zie"/>
+  <l:gentext key="see" text="Zie"/>
+  <l:gentext key="SeeAlso" text="Zie ook"/>
+  <l:gentext key="Seealso" text="Zie ook"/>
+  <l:gentext key="seealso" text="Zie ook"/>
+  <l:gentext key="Set" text="Verzameling"/>
+  <l:gentext key="set" text="Verzameling"/>
+  <l:gentext key="SetIndex" text="Hoofdregister"/>
+  <l:gentext key="setindex" text="Hoofdregister"/>
+  <l:gentext key="Sidebar" text="Excursie"/>
+  <l:gentext key="sidebar" text="excursie"/>
+  <l:gentext key="Step" text="Stap"/>
+  <l:gentext key="step" text="stap"/>
+  <l:gentext key="Table" text="Tabel"/>
+  <l:gentext key="table" text="Tabel"/>
+  <l:gentext key="TIP" text="TIP"/>
+  <l:gentext key="Tip" text="Tip"/>
+  <l:gentext key="tip" text="Tip"/>
+  <l:gentext key="WARNING" text="WAARSCHUWING"/>
+  <l:gentext key="Warning" text="Waarschuwing"/>
+  <l:gentext key="warning" text="Waarschuwing"/>
+  <l:gentext key="and" text="en"/>
+  <l:gentext key="by" text="door"/>
+  <l:gentext key="Edited" text="Redactie"/>
+  <l:gentext key="edited" text="Redactie"/>
+  <l:gentext key="Editedby" text="Redactie door"/>
+  <l:gentext key="editedby" text="Redactie door"/>
+  <l:gentext key="in" text="in"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="niet bestaand element"/>
+  <l:gentext key="notes" text="Noten"/>
+  <l:gentext key="Notes" text="Noten"/>
+  <l:gentext key="Pgs" text="blz."/>
+  <l:gentext key="pgs" text="blz."/>
+  <l:gentext key="Revisedby" text="Herzien door: "/>
+  <l:gentext key="revisedby" text="Herzien door: "/>
+  <l:gentext key="TableNotes" text="Opmerkingen"/>
+  <l:gentext key="tablenotes" text="Opmerkingen"/>
+  <l:gentext key="TableofContents" text="Inhoudsopgave"/>
+  <l:gentext key="tableofcontents" text="Inhoudsopgave"/>
+  <l:gentext key="unexpectedelementname" text="ONVERWACHT-ELEMENT"/>
+  <l:gentext key="unsupported" text="niet ondersteund"/>
+  <l:gentext key="xrefto" text="verwijzing naar"/>
+  <l:gentext key="listofequations" text="Lijst van vergelijkingen"/>
+  <l:gentext key="ListofEquations" text="Lijst van vergelijkingen"/>
+  <l:gentext key="ListofExamples" text="Lijst van voorbeelden"/>
+  <l:gentext key="listofexamples" text="Lijst van voorbeelden"/>
+  <l:gentext key="ListofFigures" text="Lijst van figuren"/>
+  <l:gentext key="listoffigures" text="Lijst van figuren"/>
+  <l:gentext key="listoftables" text="Lijst van tabellen"/>
+  <l:gentext key="ListofTables" text="Lijst van tabellen"/>
+  <l:gentext key="ListofUnknown" text="Lijst van ???"/>
+  <l:gentext key="listofunknown" text="Lijst van ???"/>
+  <l:gentext key="nav-home" text="Begin"/>
+  <l:gentext key="nav-next" text="Volgende"/>
+  <l:gentext key="nav-next-sibling" text="Verder vooruit"/>
+  <l:gentext key="nav-prev" text="Terug"/>
+  <l:gentext key="nav-prev-sibling" text="Verder terug"/>
+  <l:gentext key="nav-up" text="Omhoog"/>
+  <l:gentext key="Draft" text="Ontwerp"/>
+  <l:gentext key="above" text="boven"/>
+  <l:gentext key="below" text="onder"/>
+  <l:gentext key="index symbols" text="Symbolen"/>
+  <l:gentext key="sectioncalled" text="de paragraaf"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz&#235;&#239;&#233;"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ&#203;&#207;&#201;"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/nl.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Aanhangsel %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Hoofdstuk %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Vergelijking %n. %t"/>
+    <l:template name="example" text="Voorbeeld %n. %t"/>
+    <l:template name="figure" text="Figuur %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Deel %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedure&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabel %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Aanhangsel %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="Hoofdstuk %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Antwoord:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Vraag:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Vraag:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="section" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="de paragraaf &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Antwoord:&#160;%n"/>
+    <l:template name="appendix" text="Aanhangsel&#160;%n"/>
+    <l:template name="bridgehead" text="Paragraaf&#160;%n"/>
+    <l:template name="chapter" text="Hoofdstuk&#160;%n"/>
+    <l:template name="equation" text="Vergelijking&#160;%n"/>
+    <l:template name="example" text="Voorbeeld&#160;%n"/>
+    <l:template name="figure" text="Figuur&#160;%n"/>
+    <l:template name="part" text="Deel&#160;%n"/>
+    <l:template name="procedure" text="Procedure&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Vraag:&#160;%n"/>
+    <l:template name="question" text="Vraag:&#160;%n"/>
+    <l:template name="sect1" text="Paragraaf&#160;%n"/>
+    <l:template name="sect2" text="Paragraaf&#160;%n"/>
+    <l:template name="sect3" text="Paragraaf&#160;%n"/>
+    <l:template name="sect4" text="Paragraaf&#160;%n"/>
+    <l:template name="sect5" text="Paragraaf&#160;%n"/>
+    <l:template name="section" text="Paragraaf&#160;%n"/>
+    <l:template name="table" text="Tabel&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Aanhangsel&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Hoofdstuk&#160;%n, %t"/>
+    <l:template name="equation" text="Vergelijking&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Voorbeeld&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figuur&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Deel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procedure&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Paragraaf&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="de paragraaf &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabel&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" en "/>
+    <l:template name="seplast" text=", en "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Zie "/>
+    <l:template name="seealso" text="Zie ook "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Doelgroep: "/>
+    <l:template name="MsgLevel" text="Niveau: "/>
+    <l:template name="MsgOrig" text="Herkomst: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0413 Dutch"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/nn.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/nn.xml
new file mode 100644
index 00000000000..e9048261237
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/nn.xml
@@ -0,0 +1,449 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="nn" english-language-name="Nynorsk">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/nn.xml -->
+  <l:gentext key="Abstract" text="Samandrag"/>
+  <l:gentext key="abstract" text="Samandrag"/>
+  <l:gentext key="Answer" text="Svar"/>
+  <l:gentext key="answer" text="svar"/>
+  <l:gentext key="Appendix" text="Tillegg"/>
+  <l:gentext key="appendix" text="tillegg"/>
+  <l:gentext key="Article" text="Artikkel"/>
+  <l:gentext key="article" text="artikkel"/>
+  <l:gentext key="Bibliography" text="Bibliografi"/>
+  <l:gentext key="bibliography" text="bibliografi"/>
+  <l:gentext key="Book" text="Bok"/>
+  <l:gentext key="book" text="bok"/>
+  <l:gentext key="CAUTION" text="OBS"/>
+  <l:gentext key="Caution" text="Obs"/>
+  <l:gentext key="caution" text="OBS"/>
+  <l:gentext key="caution" text="OBS"/>
+  <l:gentext key="Chapter" text="Kapittel"/>
+  <l:gentext key="chapter" text="kapittel"/>
+  <l:gentext key="Colophon" text="Kolofon"/>
+  <l:gentext key="colophon" text="kolofon"/>
+  <l:gentext key="Copyright" text="Opphavsrett"/>
+  <l:gentext key="copyright" text="opphavsrett"/>
+  <l:gentext key="Dedication" text="Dedikasjon"/>
+  <l:gentext key="dedication" text="dedikasjon"/>
+  <l:gentext key="Edition" text="Utg&#229;ve"/>
+  <l:gentext key="edition" text="utg&#229;ve"/>
+  <l:gentext key="Equation" text="Formel"/>
+  <l:gentext key="equation" text="formel"/>
+  <l:gentext key="Example" text="D&#248;me"/>
+  <l:gentext key="example" text="d&#248;me"/>
+  <l:gentext key="Figure" text="Figur"/>
+  <l:gentext key="figure" text="figur"/>
+  <l:gentext key="Glossary" text="Ordliste"/>
+  <l:gentext key="glossary" text="ordliste"/>
+  <l:gentext key="GlossSee" text="Sj&#229;"/>
+  <l:gentext key="glosssee" text="sj&#229;"/>
+  <l:gentext key="GlossSeeAlso" text="Sj&#229; &#242;g"/>
+  <l:gentext key="glossseealso" text="sj&#229; &#242;g"/>
+  <l:gentext key="IMPORTANT" text="VIKTIG"/>
+  <l:gentext key="Important" text="Viktig"/>
+  <l:gentext key="important" text="viktig"/>
+  <l:gentext key="important" text="viktig"/>
+  <l:gentext key="Index" text="Indeks"/>
+  <l:gentext key="index" text="indeks"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text=""/>
+  <l:gentext key="legalnotice" text=""/>
+  <l:gentext key="MsgAud" text="Publikum"/>
+  <l:gentext key="msgaud" text="publikum"/>
+  <l:gentext key="MsgLevel" text="Niv&#229;"/>
+  <l:gentext key="msglevel" text="niv&#229;"/>
+  <l:gentext key="MsgOrig" text="Opphav"/>
+  <l:gentext key="msgorig" text="Opphav"/>
+  <l:gentext key="NOTE" text="NOTAT"/>
+  <l:gentext key="Note" text="Notat"/>
+  <l:gentext key="note" text="NOTAT"/>
+  <l:gentext key="note" text="NOTAT"/>
+  <l:gentext key="Part" text="Del"/>
+  <l:gentext key="part" text="del"/>
+  <l:gentext key="Preface" text="Forord"/>
+  <l:gentext key="preface" text="forord"/>
+  <l:gentext key="Procedure" text="Prosedyre"/>
+  <l:gentext key="procedure" text="prosedyre"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="Utgitt"/>
+  <l:gentext key="published" text="utgitt"/>
+  <l:gentext key="Question" text="Sp&#248;rsm&#229;l"/>
+  <l:gentext key="question" text="sp&#248;rsm&#229;l"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Referanse"/>
+  <l:gentext key="reference" text="referanse"/>
+  <l:gentext key="RefName" text="Namn"/>
+  <l:gentext key="refname" text="namn"/>
+  <l:gentext key="RefSection" text="Del"/>
+  <l:gentext key="refsection" text="del"/>
+  <l:gentext key="RefSynopsisDiv" text="Oversyn"/>
+  <l:gentext key="refsynopsisdiv" text="oversyn"/>
+  <l:gentext key="RevHistory" text="Revisjonshistorie"/>
+  <l:gentext key="revhistory" text="revisjonshistorie"/>
+  <l:gentext key="Revision" text="Revisjon"/>
+  <l:gentext key="revision" text="revisjon"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="Del"/>
+  <l:gentext key="section" text="del"/>
+  <l:gentext key="See" text="Sj&#229;"/>
+  <l:gentext key="see" text="sj&#229;"/>
+  <l:gentext key="SeeAlso" text="Sj&#229; &#242;g"/>
+  <l:gentext key="seealso" text="sj&#229; &#242;g"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="set" text="set"/>
+  <l:gentext key="SetIndex" text="Indeks"/>
+  <l:gentext key="setindex" text="Indeks"/>
+  <l:gentext key="Sidebar" text="Sidestolpe"/>
+  <l:gentext key="sidebar" text="sidestolpe"/>
+  <l:gentext key="Step" text="Steg"/>
+  <l:gentext key="step" text="steg"/>
+  <l:gentext key="Table" text="Tabell"/>
+  <l:gentext key="table" text="tabell"/>
+  <l:gentext key="TIP" text="TIPS"/>
+  <l:gentext key="Tip" text="Tips"/>
+  <l:gentext key="tip" text="tips"/>
+  <l:gentext key="tip" text="tips"/>
+  <l:gentext key="WARNING" text="&#197;TVARING"/>
+  <l:gentext key="Warning" text="&#197;tvaring"/>
+  <l:gentext key="warning" text="&#229;tvaring"/>
+  <l:gentext key="warning" text="&#229;tvaring"/>
+  <l:gentext key="Seealso" text="Sj&#229; &#242;g"/>
+  <l:gentext key="seealso" text="sj&#229; &#242;g"/>
+  <l:gentext key="TableofContents" text="Innhald"/>
+  <l:gentext key="tableofcontents" text="Innhald"/>
+  <l:gentext key="in" text="i"/>
+  <l:gentext key="by" text="av"/>
+  <l:gentext key="Edited" text="Redigert"/>
+  <l:gentext key="edited" text="redigert"/>
+  <l:gentext key="Editedby" text="Redigert av"/>
+  <l:gentext key="editedby" text="redigert av"/>
+  <l:gentext key="and" text="og"/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="Notes" text="Merknader"/>
+  <l:gentext key="notes" text="merknader"/>
+  <l:gentext key="TableNotes" text="Merknader"/>
+  <l:gentext key="tablenotes" text="merknader"/>
+  <l:gentext key="nonexistantelement" text="ikkje-eksisterande element"/>
+  <l:gentext key="Pgs" text="Sider"/>
+  <l:gentext key="pgs" text="sider"/>
+  <l:gentext key="unsupported" text="ikkje st&#248;tta"/>
+  <l:gentext key="xrefto" text="xref til"/>
+  <l:gentext key="unexpectedelementname" text="UVENTA-ELEMENTNAVN"/>
+  <l:gentext key="Revisedby" text="Revidert av: "/>
+  <l:gentext key="revisedby" text="revidert av: "/>
+  <l:gentext key="ListofTables" text="Tabelloversikt"/>
+  <l:gentext key="listoftables" text="tabelloversikt"/>
+  <l:gentext key="ListofExamples" text="D&#248;meoversikt"/>
+  <l:gentext key="listofexamples" text="d&#248;meoversikt"/>
+  <l:gentext key="ListofFigures" text="Figuroversikt"/>
+  <l:gentext key="listoffigures" text="figuroversikt"/>
+  <l:gentext key="ListofEquations" text="Formeloversikt"/>
+  <l:gentext key="listofequations" text="formeloversikt"/>
+  <l:gentext key="ListofUnknown" text="???-oversikt"/>
+  <l:gentext key="listofunknown" text="???-oversikt"/>
+  <l:gentext key="nav-prev" text="Att"/>
+  <l:gentext key="nav-prev-sibling" text="Raskt bakover"/>
+  <l:gentext key="nav-next-sibling" text="Raskt framover"/>
+  <l:gentext key="nav-next" text="Fram"/>
+  <l:gentext key="nav-up" text="Opp"/>
+  <l:gentext key="nav-home" text="Heim"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/nn.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Tillegg %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Kapittel %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Formel %n. %t"/>
+    <l:template name="example" text="D&#248;me %n. %t"/>
+    <l:template name="figure" text="Figur %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Del %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Prosedyre&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabell %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Tillegg %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Kapittel %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Svar&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Sp&#248;rsm&#229;l&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Sp&#248;rsm&#229;l&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Svar&#160;%n"/>
+    <l:template name="appendix" text="Tillegg&#160;%n"/>
+    <l:template name="bridgehead" text="Del&#160;%n"/>
+    <l:template name="chapter" text="Kapittel&#160;%n"/>
+    <l:template name="equation" text="Formel&#160;%n"/>
+    <l:template name="example" text="D&#248;me&#160;%n"/>
+    <l:template name="figure" text="Figur&#160;%n"/>
+    <l:template name="part" text="Del&#160;%n"/>
+    <l:template name="procedure" text="Prosedyre&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Sp&#248;rsm&#229;l&#160;%n"/>
+    <l:template name="question" text="Sp&#248;rsm&#229;l&#160;%n"/>
+    <l:template name="sect1" text="Del&#160;%n"/>
+    <l:template name="sect2" text="Del&#160;%n"/>
+    <l:template name="sect3" text="Del&#160;%n"/>
+    <l:template name="sect4" text="Del&#160;%n"/>
+    <l:template name="sect5" text="Del&#160;%n"/>
+    <l:template name="section" text="Del&#160;%n"/>
+    <l:template name="table" text="Tabell&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Tillegg&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Kapittel&#160;%n, %t"/>
+    <l:template name="equation" text="Formel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="D&#248;me&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figur&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Prosedyre&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabell&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" og "/>
+    <l:template name="seplast" text=", og "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Sj&#229; "/>
+    <l:template name="seealso" text="Sj&#229; &#242;g "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgLevel" text="Niv&#229;: "/>
+    <l:template name="MsgOrig" text="Opphav: "/>
+    <l:template name="MsgAud" text="Publikum: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0814 Norwegian (Nynorsk)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/no.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/no.xml
new file mode 100644
index 00000000000..3c6f344515f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/no.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="no" english-language-name="Norwegian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/no.xml -->
+  <l:gentext key="Abstract" text="Abstract"/>
+  <l:gentext key="abstract" text="Abstract"/>
+  <l:gentext key="Answer" text="A:"/>
+  <l:gentext key="answer" text="A:"/>
+  <l:gentext key="Appendix" text="Tillegg"/>
+  <l:gentext key="appendix" text="Tillegg"/>
+  <l:gentext key="Article" text=""/>
+  <l:gentext key="article" text=""/>
+  <l:gentext key="Bibliography" text="Bibliografi"/>
+  <l:gentext key="bibliography" text="Bibliografi"/>
+  <l:gentext key="Book" text=""/>
+  <l:gentext key="book" text=""/>
+  <l:gentext key="CAUTION" text="OBS"/>
+  <l:gentext key="Caution" text="Obs"/>
+  <l:gentext key="caution" text="Obs"/>
+  <l:gentext key="Chapter" text="Kapittel"/>
+  <l:gentext key="chapter" text="Kapittel"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Dedikasjon"/>
+  <l:gentext key="dedication" text="Dedikasjon"/>
+  <l:gentext key="Edition" text=""/>
+  <l:gentext key="edition" text=""/>
+  <l:gentext key="Equation" text="Formel"/>
+  <l:gentext key="equation" text="Formel"/>
+  <l:gentext key="Example" text="Eksempel"/>
+  <l:gentext key="example" text="Eksempel"/>
+  <l:gentext key="Figure" text="Figur"/>
+  <l:gentext key="figure" text="Figur"/>
+  <l:gentext key="Glossary" text="Ordliste"/>
+  <l:gentext key="glossary" text="Ordliste"/>
+  <l:gentext key="GlossSee" text="Se"/>
+  <l:gentext key="glosssee" text="Se"/>
+  <l:gentext key="GlossSeeAlso" text="Se Ogs&#229;"/>
+  <l:gentext key="glossseealso" text="Se Ogs&#229;"/>
+  <l:gentext key="IMPORTANT" text="VIKTIG"/>
+  <l:gentext key="Important" text="Viktig"/>
+  <l:gentext key="important" text="Viktig"/>
+  <l:gentext key="Index" text="Indeks"/>
+  <l:gentext key="index" text="Indeks"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text=""/>
+  <l:gentext key="legalnotice" text=""/>
+  <l:gentext key="MsgAud" text="Publikum"/>
+  <l:gentext key="msgaud" text="Publikum"/>
+  <l:gentext key="MsgLevel" text="Niv&#229;"/>
+  <l:gentext key="msglevel" text="Niv&#229;"/>
+  <l:gentext key="MsgOrig" text="Opphav"/>
+  <l:gentext key="msgorig" text="Opphav"/>
+  <l:gentext key="NOTE" text="NOTAT"/>
+  <l:gentext key="Note" text="Notat"/>
+  <l:gentext key="note" text="Notat"/>
+  <l:gentext key="Part" text="Del"/>
+  <l:gentext key="part" text="Del"/>
+  <l:gentext key="Preface" text="Forord"/>
+  <l:gentext key="preface" text="Forord"/>
+  <l:gentext key="Procedure" text="Prosedyre"/>
+  <l:gentext key="procedure" text="Prosedyre"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text=""/>
+  <l:gentext key="published" text=""/>
+  <l:gentext key="Question" text="Q:"/>
+  <l:gentext key="question" text="Q:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Referanse"/>
+  <l:gentext key="reference" text="Referanse"/>
+  <l:gentext key="RefName" text="Navn"/>
+  <l:gentext key="refname" text="Navn"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Revisjonshistorie"/>
+  <l:gentext key="revhistory" text="Revisjonshistorie"/>
+  <l:gentext key="Revision" text="Revisjon"/>
+  <l:gentext key="revision" text="Revisjon"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="Seksjon"/>
+  <l:gentext key="section" text="seksjon"/>
+  <l:gentext key="See" text="Se"/>
+  <l:gentext key="see" text="Se"/>
+  <l:gentext key="SeeAlso" text="Se Ogs&#229;"/>
+  <l:gentext key="Seealso" text="Se ogs&#229;"/>
+  <l:gentext key="seealso" text="Se Ogs&#229;"/>
+  <l:gentext key="Set" text=""/>
+  <l:gentext key="set" text=""/>
+  <l:gentext key="SetIndex" text="Indeks"/>
+  <l:gentext key="setindex" text="Indeks"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text=""/>
+  <l:gentext key="Step" text="Steg"/>
+  <l:gentext key="step" text="steg"/>
+  <l:gentext key="Table" text="Tabell"/>
+  <l:gentext key="table" text="Tabell"/>
+  <l:gentext key="TIP" text="TIPS"/>
+  <l:gentext key="Tip" text="Tips"/>
+  <l:gentext key="tip" text="Tips"/>
+  <l:gentext key="WARNING" text="ADVARSEL"/>
+  <l:gentext key="Warning" text="Advarsel"/>
+  <l:gentext key="warning" text="Advarsel"/>
+  <l:gentext key="and" text="og"/>
+  <l:gentext key="by" text="av"/>
+  <l:gentext key="Edited" text="Redigert"/>
+  <l:gentext key="edited" text="Redigert"/>
+  <l:gentext key="Editedby" text="Redigert av"/>
+  <l:gentext key="editedby" text="Redigert av"/>
+  <l:gentext key="in" text="i"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="ikke-eksisterende element"/>
+  <l:gentext key="notes" text="Sluttnotater"/>
+  <l:gentext key="Notes" text="Sluttnotater"/>
+  <l:gentext key="Pgs" text="Sdr."/>
+  <l:gentext key="pgs" text="Sdr."/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text="Notater"/>
+  <l:gentext key="tablenotes" text="Notater"/>
+  <l:gentext key="TableofContents" text="Innholdsfortegnelse"/>
+  <l:gentext key="tableofcontents" text="Innholdsfortegnelse"/>
+  <l:gentext key="unexpectedelementname" text="UVENTET-ELEMENTNAVN"/>
+  <l:gentext key="unsupported" text="ikke st&#248;ttet"/>
+  <l:gentext key="xrefto" text="xref til"/>
+  <l:gentext key="listofequations" text="Formeloversikt"/>
+  <l:gentext key="ListofEquations" text="Formeloversikt"/>
+  <l:gentext key="ListofExamples" text="Eksempeloversikt"/>
+  <l:gentext key="listofexamples" text="Eksempeloversikt"/>
+  <l:gentext key="ListofFigures" text="Figuroversikt"/>
+  <l:gentext key="listoffigures" text="Figuroversikt"/>
+  <l:gentext key="listoftables" text="Tabelloversikt"/>
+  <l:gentext key="ListofTables" text="Tabelloversikt"/>
+  <l:gentext key="ListofUnknown" text="???-oversikt"/>
+  <l:gentext key="listofunknown" text="???-oversikt"/>
+  <l:gentext key="nav-home" text="Hjem"/>
+  <l:gentext key="nav-next" text="Neste"/>
+  <l:gentext key="nav-next-sibling" text="Raskt Fremover"/>
+  <l:gentext key="nav-prev" text="Forrige"/>
+  <l:gentext key="nav-prev-sibling" text="Raskt Bakover"/>
+  <l:gentext key="nav-up" text="Opp"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/no.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Tillegg %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Kapittel %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Formel %n. %t"/>
+    <l:template name="example" text="Eksempel %n. %t"/>
+    <l:template name="figure" text="Figur %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Del %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Prosedyre&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabell %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Tillegg %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Kapittel %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="Tillegg&#160;%n"/>
+    <l:template name="bridgehead" text="Seksjon&#160;%n"/>
+    <l:template name="chapter" text="Kapittel&#160;%n"/>
+    <l:template name="equation" text="Formel&#160;%n"/>
+    <l:template name="example" text="Eksempel&#160;%n"/>
+    <l:template name="figure" text="Figur&#160;%n"/>
+    <l:template name="part" text="Del&#160;%n"/>
+    <l:template name="procedure" text="Prosedyre&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="sect1" text="Seksjon&#160;%n"/>
+    <l:template name="sect2" text="Seksjon&#160;%n"/>
+    <l:template name="sect3" text="Seksjon&#160;%n"/>
+    <l:template name="sect4" text="Seksjon&#160;%n"/>
+    <l:template name="sect5" text="Seksjon&#160;%n"/>
+    <l:template name="section" text="Seksjon&#160;%n"/>
+    <l:template name="table" text="Tabell&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Tillegg&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Seksjon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Kapittel&#160;%n, %t"/>
+    <l:template name="equation" text="Formel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Eksempel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figur&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Prosedyre&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Seksjon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Seksjon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Seksjon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Seksjon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Seksjon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Seksjon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabell&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" og "/>
+    <l:template name="seplast" text=", og "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Se "/>
+    <l:template name="seealso" text="Se Ogs&#229; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Publikum: "/>
+    <l:template name="MsgLevel" text="Niv&#229;: "/>
+    <l:template name="MsgOrig" text="Opphav: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0414 Norwegian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/pl.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/pl.xml
new file mode 100644
index 00000000000..f45a4413b76
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/pl.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="pl" english-language-name="Polish">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/pl.xml -->
+  <l:gentext key="Abstract" text="Abstrakt"/>
+  <l:gentext key="abstract" text="Abstrakt"/>
+  <l:gentext key="Answer" text="Odp:"/>
+  <l:gentext key="answer" text="Odp:"/>
+  <l:gentext key="Appendix" text="Dodatek"/>
+  <l:gentext key="appendix" text="dodatek"/>
+  <l:gentext key="Article" text="Artyku&#322;"/>
+  <l:gentext key="article" text="Artyku&#322;"/>
+  <l:gentext key="Bibliography" text="Bibliografia"/>
+  <l:gentext key="bibliography" text="Bibliografia"/>
+  <l:gentext key="Book" text="Ksi&#261;&#380;ka"/>
+  <l:gentext key="book" text="Ksi&#261;&#380;ka"/>
+  <l:gentext key="CAUTION" text="PRZYPADEK"/>
+  <l:gentext key="Caution" text="Uwaga!"/>
+  <l:gentext key="caution" text="Uwaga!"/>
+  <l:gentext key="Chapter" text="Rozdzia&#322;"/>
+  <l:gentext key="chapter" text="rozdzia&#322;;"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Dedykacja"/>
+  <l:gentext key="dedication" text="Dedykacja"/>
+  <l:gentext key="Edition" text="Wydanie"/>
+  <l:gentext key="edition" text="Wydanie"/>
+  <l:gentext key="Equation" text="R&#243;wnanie"/>
+  <l:gentext key="equation" text="R&#243;wnanie"/>
+  <l:gentext key="Example" text="Przyk&#322;ad"/>
+  <l:gentext key="example" text="Przyk&#322;ad"/>
+  <l:gentext key="Figure" text="Rysunek"/>
+  <l:gentext key="figure" text="Rysunek"/>
+  <l:gentext key="Glossary" text="Glossary"/>
+  <l:gentext key="glossary" text="Glossary"/>
+  <l:gentext key="GlossSee" text="Patrz"/>
+  <l:gentext key="glosssee" text="Patrz"/>
+  <l:gentext key="GlossSeeAlso" text="Patrz te&#380;"/>
+  <l:gentext key="glossseealso" text="Patrz te&#380;"/>
+  <l:gentext key="IMPORTANT" text="WA&#379;NE"/>
+  <l:gentext key="Important" text="WA&#379;NE"/>
+  <l:gentext key="important" text="WA&#379;NE"/>
+  <l:gentext key="Index" text="Indeks"/>
+  <l:gentext key="index" text="Indeks"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text=""/>
+  <l:gentext key="legalnotice" text=""/>
+  <l:gentext key="MsgAud" text="Odbiorcy"/>
+  <l:gentext key="msgaud" text="Odbiorcy"/>
+  <l:gentext key="MsgLevel" text="Poziom"/>
+  <l:gentext key="msglevel" text="Poziom"/>
+  <l:gentext key="MsgOrig" text="Nadawca"/>
+  <l:gentext key="msgorig" text="Nadawca"/>
+  <l:gentext key="NOTE" text="Notatka"/>
+  <l:gentext key="Note" text="Notatka"/>
+  <l:gentext key="note" text="Notatka"/>
+  <l:gentext key="Part" text="Cz&#281;&#347;&#263;"/>
+  <l:gentext key="part" text="Cz&#281;&#347;&#263;"/>
+  <l:gentext key="Preface" text="Przedmowa"/>
+  <l:gentext key="preface" text="Przedmowa"/>
+  <l:gentext key="Procedure" text="Procedura"/>
+  <l:gentext key="procedure" text="Procedura"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="Data wydania"/>
+  <l:gentext key="published" text="Data wydania"/>
+  <l:gentext key="question" text="Pyt:"/>
+  <l:gentext key="Question" text="Pyt:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Materia&#322;y &#378;r&#243;d&#322;owe"/>
+  <l:gentext key="reference" text="Materia&#322;y &#378;r&#243;d&#322;owe"/>
+  <l:gentext key="RefName" text="Nazwa"/>
+  <l:gentext key="refname" text="Nazwa"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Historia zmian"/>
+  <l:gentext key="revhistory" text="Historia zmian"/>
+  <l:gentext key="Revision" text="Zmiana"/>
+  <l:gentext key="revision" text="Zmiana"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="Sekcja"/>
+  <l:gentext key="section" text="sekcja"/>
+  <l:gentext key="See" text="Patrz"/>
+  <l:gentext key="see" text="Patrz"/>
+  <l:gentext key="SeeAlso" text="Patrz te&#380;"/>
+  <l:gentext key="Seealso" text="Patrz te&#380;"/>
+  <l:gentext key="seealso" text="Patrz te&#380;"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="SetIndex" text="Indeks"/>
+  <l:gentext key="setindex" text="Indeks"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text=""/>
+  <l:gentext key="Step" text="krok"/>
+  <l:gentext key="step" text="krok"/>
+  <l:gentext key="Table" text="Tabela"/>
+  <l:gentext key="table" text="Tabela"/>
+  <l:gentext key="TIP" text="Podpowied&#378;"/>
+  <l:gentext key="Tip" text="Podpowied&#378;"/>
+  <l:gentext key="tip" text="Podpowied&#378;"/>
+  <l:gentext key="WARNING" text="Ostrze&#380;enie"/>
+  <l:gentext key="Warning" text="Ostrze&#380;enie"/>
+  <l:gentext key="warning" text="Ostrze&#380;enie"/>
+  <l:gentext key="and" text="i"/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="Edited" text="Edited"/>
+  <l:gentext key="edited" text="Edited"/>
+  <l:gentext key="Editedby" text="Redakcja: "/>
+  <l:gentext key="editedby" text="Redakcja: "/>
+  <l:gentext key="in" text="w"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="nie istniej&#261;cy element"/>
+  <l:gentext key="notes" text="Przypisy"/>
+  <l:gentext key="Notes" text="Przypisy"/>
+  <l:gentext key="Pgs" text="stron"/>
+  <l:gentext key="pgs" text="stron"/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text="Przypisy"/>
+  <l:gentext key="tablenotes" text="Przypisy"/>
+  <l:gentext key="TableofContents" text="Spis tre&#347;ci"/>
+  <l:gentext key="tableofcontents" text="Spis tre&#347;ci"/>
+  <l:gentext key="unexpectedelementname" text="Unexpected element name"/>
+  <l:gentext key="unsupported" text="nie wspierany"/>
+  <l:gentext key="xrefto" text="xref to"/>
+  <l:gentext key="listofequations" text="Spis r&#243;wna&#324;"/>
+  <l:gentext key="ListofEquations" text="Spis r&#243;wna&#324;"/>
+  <l:gentext key="ListofExamples" text="Spis przyk&#322;ad&#243;w"/>
+  <l:gentext key="listofexamples" text="Spis przyk&#322;ad&#243;w"/>
+  <l:gentext key="ListofFigures" text="Spis rysunk&#243;w"/>
+  <l:gentext key="listoffigures" text="Spis rysunk&#243;w"/>
+  <l:gentext key="listoftables" text="Spis tabel"/>
+  <l:gentext key="ListofTables" text="Spis tabel"/>
+  <l:gentext key="ListofUnknown" text="Spis ???"/>
+  <l:gentext key="listofunknown" text="Spis ???"/>
+  <l:gentext key="nav-home" text="Spis tre&#347;ci"/>
+  <l:gentext key="nav-next" text="Nast&#281;pny"/>
+  <l:gentext key="nav-next-sibling" text="Nast&#281;pny rozdzia&#322;"/>
+  <l:gentext key="nav-prev" text="Poprzedni"/>
+  <l:gentext key="nav-prev-sibling" text="Poprzedni rozdzia&#322;"/>
+  <l:gentext key="nav-up" text="Pocz&#261;tek rozdzia&#322;u"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/pl.xml -->
+  <l:dingbat key="startquote" text="&#8222;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#171;"/>
+  <l:dingbat key="nestedendquote" text="&#187;"/>
+  <l:dingbat key="bullet" text="&#2022;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Dodatek %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Rozdzia&#322; %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="R&#243;wnanie %n. %t"/>
+    <l:template name="example" text="Przyk&#322;ad %n. %t"/>
+    <l:template name="figure" text="Rysunek %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Cz&#281;&#347;&#263; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedura&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabela %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Dodatek %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Rozdzia&#322; %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Odp:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Pyt:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Pyt:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8222;%t&#8221;"/>
+    <l:template name="refsection" text="&#8222;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8222;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8222;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8222;%t&#8221;"/>
+    <l:template name="sect1" text="&#8222;%t&#8221;"/>
+    <l:template name="sect2" text="&#8222;%t&#8221;"/>
+    <l:template name="sect3" text="&#8222;%t&#8221;"/>
+    <l:template name="sect4" text="&#8222;%t&#8221;"/>
+    <l:template name="sect5" text="&#8222;%t&#8221;"/>
+    <l:template name="section" text="&#8222;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8222;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Odp:&#160;%n"/>
+    <l:template name="appendix" text="Dodatek&#160;%n"/>
+    <l:template name="bridgehead" text="Sekcja&#160;%n"/>
+    <l:template name="chapter" text="Rozdzia&#322;&#160;%n"/>
+    <l:template name="equation" text="R&#243;wnanie&#160;%n"/>
+    <l:template name="example" text="Przyk&#322;ad&#160;%n"/>
+    <l:template name="figure" text="Rysunek&#160;%n"/>
+    <l:template name="part" text="Cz&#281;&#347;&#263;&#160;%n"/>
+    <l:template name="procedure" text="Procedura&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Pyt:&#160;%n"/>
+    <l:template name="question" text="Pyt:&#160;%n"/>
+    <l:template name="sect1" text="Sekcja&#160;%n"/>
+    <l:template name="sect2" text="Sekcja&#160;%n"/>
+    <l:template name="sect3" text="Sekcja&#160;%n"/>
+    <l:template name="sect4" text="Sekcja&#160;%n"/>
+    <l:template name="sect5" text="Sekcja&#160;%n"/>
+    <l:template name="section" text="Sekcja&#160;%n"/>
+    <l:template name="table" text="Tabela&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Dodatek&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Sekcja&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="chapter" text="Rozdzia&#322;&#160;%n, %t"/>
+    <l:template name="equation" text="R&#243;wnanie&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="example" text="Przyk&#322;ad&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="figure" text="Rysunek&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="part" text="Cz&#281;&#347;&#263;&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="procedure" text="Procedura&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8222;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8222;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8222;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8222;%t&#8221;"/>
+    <l:template name="sect1" text="Sekcja&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="sect2" text="Sekcja&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="sect3" text="Sekcja&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="sect4" text="Sekcja&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="sect5" text="Sekcja&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="section" text="Sekcja&#160;%n, &#8222;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8222;%t&#8221;"/>
+    <l:template name="table" text="Tabela&#160;%n, &#8222;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" i "/>
+    <l:template name="seplast" text=", i "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Patrz "/>
+    <l:template name="seealso" text="Patrz te&#380; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Odbiorcy: "/>
+    <l:template name="MsgLevel" text="Poziom: "/>
+    <l:template name="MsgOrig" text="Nadawca: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0415 Polish"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/pt.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/pt.xml
new file mode 100644
index 00000000000..1c03625c13e
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/pt.xml
@@ -0,0 +1,445 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="pt" english-language-name="Portuguese">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/pt.xml -->
+  <l:gentext key="Abstract" text="Resumo"/>
+  <l:gentext key="abstract" text="Resumo"/>
+  <l:gentext key="Answer" text="R:"/>
+  <l:gentext key="answer" text="R:"/>
+  <l:gentext key="Appendix" text="Ap&#234;ndice"/>
+  <l:gentext key="appendix" text="ap&#234;ndice"/>
+  <l:gentext key="Article" text="Artigo"/>
+  <l:gentext key="article" text="Artigo"/>
+  <l:gentext key="Bibliography" text="Bibliografia"/>
+  <l:gentext key="bibliography" text="Bibliografia"/>
+  <l:gentext key="Book" text="Livro"/>
+  <l:gentext key="book" text="Livro"/>
+  <l:gentext key="CAUTION" text="CAUTELA"/>
+  <l:gentext key="Caution" text="Cautela"/>
+  <l:gentext key="caution" text="Cautela"/>
+  <l:gentext key="Chapter" text="Cap&#237;tulo"/>
+  <l:gentext key="chapter" text="cap&#237;tulo"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Dedicat&#243;ria"/>
+  <l:gentext key="dedication" text="Dedicat&#243;ria"/>
+  <l:gentext key="Edition" text="Edi&#231;&#227;o"/>
+  <l:gentext key="edition" text="Edi&#231;&#227;o"/>
+  <l:gentext key="Equation" text="Equa&#231;&#227;o"/>
+  <l:gentext key="equation" text="Equa&#231;&#227;o"/>
+  <l:gentext key="Example" text="Exemplo"/>
+  <l:gentext key="example" text="Exemplo"/>
+  <l:gentext key="Figure" text="Figura"/>
+  <l:gentext key="figure" text="Figura"/>
+  <l:gentext key="Glossary" text="Gloss&#193;rio"/>
+  <l:gentext key="glossary" text="Gloss&#193;rio"/>
+  <l:gentext key="GlossSee" text="Ver"/>
+  <l:gentext key="glosssee" text="Ver"/>
+  <l:gentext key="GlossSeeAlso" text="Ver Tamb&#233;m"/>
+  <l:gentext key="glossseealso" text="Ver Tamb&#233;m"/>
+  <l:gentext key="IMPORTANT" text="IMPORTANTE"/>
+  <l:gentext key="Important" text="Importante"/>
+  <l:gentext key="important" text="Importante"/>
+  <l:gentext key="Index" text="&#205;ndice Remissivo"/>
+  <l:gentext key="index" text="&#205;ndice Remissivo"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Aviso Legal"/>
+  <l:gentext key="legalnotice" text="Aviso Legal"/>
+  <l:gentext key="MsgAud" text="Audi&#234;ncia"/>
+  <l:gentext key="msgaud" text="Audi&#234;ncia"/>
+  <l:gentext key="MsgLevel" text="N&#237;vel"/>
+  <l:gentext key="msglevel" text="N&#237;vel"/>
+  <l:gentext key="MsgOrig" text="Origem"/>
+  <l:gentext key="msgorig" text="Origem"/>
+  <l:gentext key="NOTE" text="NOTA"/>
+  <l:gentext key="Note" text="Nota"/>
+  <l:gentext key="note" text="Nota"/>
+  <l:gentext key="Part" text="Parte"/>
+  <l:gentext key="part" text="Parte"/>
+  <l:gentext key="Preface" text="Pref&#225;cio"/>
+  <l:gentext key="preface" text="Pref&#225;cio"/>
+  <l:gentext key="Procedure" text="Procedimento"/>
+  <l:gentext key="procedure" text="Procedimento"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="PubDate" text="Editado"/>
+  <l:gentext key="pubdate" text="Editado"/>
+  <l:gentext key="Published" text="Publicado"/>
+  <l:gentext key="published" text="Publicado"/>
+  <l:gentext key="Question" text="P:"/>
+  <l:gentext key="question" text="P:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Refer&#234;ncia"/>
+  <l:gentext key="reference" text="Refer&#234;ncia"/>
+  <l:gentext key="RefName" text="Nome"/>
+  <l:gentext key="refname" text="Nome"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Sinopse"/>
+  <l:gentext key="refsynopsisdiv" text="Sinopse"/>
+  <l:gentext key="RevHistory" text="Historial de Revis&#245;es"/>
+  <l:gentext key="revhistory" text="Historial de Revis&#245;es"/>
+  <l:gentext key="Revision" text="Revis&#227;o"/>
+  <l:gentext key="revision" text="Revis&#227;o"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="Sec&#231;&#227;o"/>
+  <l:gentext key="section" text="sec&#231;&#227;o"/>
+  <l:gentext key="See" text="Ver"/>
+  <l:gentext key="see" text="Ver"/>
+  <l:gentext key="SeeAlso" text="Ver Tamb&#233;m"/>
+  <l:gentext key="Seealso" text="ver tamb&#233;m"/>
+  <l:gentext key="seealso" text="Ver Tamb&#233;m"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="SetIndex" text="Set Index"/>
+  <l:gentext key="setindex" text="Set Index"/>
+  <l:gentext key="Sidebar" text="Sidebar"/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="Step" text="Passo"/>
+  <l:gentext key="step" text="passo"/>
+  <l:gentext key="Table" text="Tabela"/>
+  <l:gentext key="table" text="Tabela"/>
+  <l:gentext key="TIP" text="DICA"/>
+  <l:gentext key="Tip" text="Dica"/>
+  <l:gentext key="tip" text="Dica"/>
+  <l:gentext key="WARNING" text="ATEN&#199;&#195;O"/>
+  <l:gentext key="Warning" text="Aten&#231;&#227;o"/>
+  <l:gentext key="warning" text="Aten&#231;&#227;o"/>
+  <l:gentext key="and" text="e"/>
+  <l:gentext key="by" text="por"/>
+  <l:gentext key="Edited" text="Editado"/>
+  <l:gentext key="edited" text="Editado"/>
+  <l:gentext key="Editedby" text="Editado por"/>
+  <l:gentext key="editedby" text="Editado por"/>
+  <l:gentext key="in" text=""/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="non-existant element"/>
+  <l:gentext key="notes" text="Notas"/>
+  <l:gentext key="Notes" text="Notas"/>
+  <l:gentext key="Pgs" text="P&#225;ginas"/>
+  <l:gentext key="pgs" text="P&#225;ginas"/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text="Notas"/>
+  <l:gentext key="tablenotes" text="Notas"/>
+  <l:gentext key="TableofContents" text="&#205;ndice"/>
+  <l:gentext key="tableofcontents" text="&#205;ndice"/>
+  <l:gentext key="unexpectedelementname" text="Unexpected element name"/>
+  <l:gentext key="unsupported" text="unsupported"/>
+  <l:gentext key="xrefto" text="xref to"/>
+  <l:gentext key="listofequations" text="Lista de Equa&#231;&#245;es"/>
+  <l:gentext key="ListofEquations" text="Lista de Equa&#231;&#245;es"/>
+  <l:gentext key="ListofExamples" text="Lista de Exemplos"/>
+  <l:gentext key="listofexamples" text="Lista de Exemplos"/>
+  <l:gentext key="ListofFigures" text="Lista de Figuras"/>
+  <l:gentext key="listoffigures" text="Lista de Figuras"/>
+  <l:gentext key="listoftables" text="Lista de Tabelas"/>
+  <l:gentext key="ListofTables" text="Lista de Tabelas"/>
+  <l:gentext key="ListofUnknown" text="List of ???"/>
+  <l:gentext key="listofunknown" text="List of ???"/>
+  <l:gentext key="nav-home" text="Home"/>
+  <l:gentext key="nav-next" text="Next"/>
+  <l:gentext key="nav-next-sibling" text="Fast Forward"/>
+  <l:gentext key="nav-prev" text="Prev"/>
+  <l:gentext key="nav-prev-sibling" text="Fast Backward"/>
+  <l:gentext key="nav-up" text="Up"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/pt.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Ap&#234;ndice %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Cap&#237;tulo %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Equa&#231;&#227;o %n. %t"/>
+    <l:template name="example" text="Exemplo %n. %t"/>
+    <l:template name="figure" text="Figura %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Parte %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedimento&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Pergunta %n"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabela %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Ap&#234;ndice %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Cap&#237;tulo %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="R:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="P:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="P:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="R:&#160;%n"/>
+    <l:template name="appendix" text="Ap&#234;ndice&#160;%n"/>
+    <l:template name="bridgehead" text="Sec&#231;&#227;o&#160;%n"/>
+    <l:template name="chapter" text="Cap&#237;tulo&#160;%n"/>
+    <l:template name="equation" text="Equa&#231;&#227;o&#160;%n"/>
+    <l:template name="example" text="Exemplo&#160;%n"/>
+    <l:template name="figure" text="Figura&#160;%n"/>
+    <l:template name="part" text="Parte&#160;%n"/>
+    <l:template name="procedure" text="Procedimento&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="P:&#160;%n"/>
+    <l:template name="question" text="P:&#160;%n"/>
+    <l:template name="sect1" text="Sec&#231;&#227;o&#160;%n"/>
+    <l:template name="sect2" text="Sec&#231;&#227;o&#160;%n"/>
+    <l:template name="sect3" text="Sec&#231;&#227;o&#160;%n"/>
+    <l:template name="sect4" text="Sec&#231;&#227;o&#160;%n"/>
+    <l:template name="sect5" text="Sec&#231;&#227;o&#160;%n"/>
+    <l:template name="section" text="Sec&#231;&#227;o&#160;%n"/>
+    <l:template name="table" text="Tabela&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Ap&#234;ndice&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Sec&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Cap&#237;tulo&#160;%n, %t"/>
+    <l:template name="equation" text="Equa&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Exemplo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figura&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Parte&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procedimento&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Sec&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Sec&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Sec&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Sec&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Sec&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Sec&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabela&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" e "/>
+    <l:template name="seplast" text=", e "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Ver "/>
+    <l:template name="seealso" text="Ver Tamb&#233;m "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Audi&#234;ncia: "/>
+    <l:template name="MsgLevel" text="N&#237;vel: "/>
+    <l:template name="MsgOrig" text="Origem: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0816 Portuguese (PORTUGAL)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/pt_br.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/pt_br.xml
new file mode 100644
index 00000000000..3413cf46a1c
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/pt_br.xml
@@ -0,0 +1,442 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="pt_br" english-language-name="Portuguese (Brazil)">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/pt_br.xml -->
+  <l:gentext key="Abstract" text="Resumo"/>
+  <l:gentext key="abstract" text="Resumo"/>
+  <l:gentext key="Answer" text="R:"/>
+  <l:gentext key="answer" text="R:"/>
+  <l:gentext key="Appendix" text="Ap&#234;ndice"/>
+  <l:gentext key="appendix" text="ap&#234;ndice"/>
+  <l:gentext key="Article" text="Artigo"/>
+  <l:gentext key="article" text="Artigo"/>
+  <l:gentext key="Bibliography" text="Bibliografia"/>
+  <l:gentext key="bibliography" text="Bibliografia"/>
+  <l:gentext key="Book" text="Livro"/>
+  <l:gentext key="book" text="Livro"/>
+  <l:gentext key="CAUTION" text="CUIDADO"/>
+  <l:gentext key="Caution" text="Cuidado"/>
+  <l:gentext key="caution" text="Cuidado"/>
+  <l:gentext key="Chapter" text="Cap&#237;tulo"/>
+  <l:gentext key="chapter" text="cap&#237;tulo"/>
+  <l:gentext key="Colophon" text="Considera&#231;&#245;es finais"/>
+  <l:gentext key="colophon" text="Considera&#231;&#245;es finais"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Dedicat&#243;ria"/>
+  <l:gentext key="dedication" text="Dedicat&#243;ria"/>
+  <l:gentext key="Edition" text="Edi&#231;&#227;o"/>
+  <l:gentext key="edition" text="Edi&#231;&#227;o"/>
+  <l:gentext key="Equation" text="Equa&#231;&#227;o"/>
+  <l:gentext key="equation" text="Equa&#231;&#227;o"/>
+  <l:gentext key="Example" text="Exemplo"/>
+  <l:gentext key="example" text="Exemplo"/>
+  <l:gentext key="Figure" text="Figura"/>
+  <l:gentext key="figure" text="Figura"/>
+  <l:gentext key="Glossary" text="Gloss&#225;rio"/>
+  <l:gentext key="glossary" text="Gloss&#225;rio"/>
+  <l:gentext key="GlossSee" text="Ver"/>
+  <l:gentext key="glosssee" text="Ver"/>
+  <l:gentext key="GlossSeeAlso" text="Ver Tamb&#233;m"/>
+  <l:gentext key="glossseealso" text="Ver Tamb&#233;m"/>
+  <l:gentext key="IMPORTANT" text="IMPORTANTE"/>
+  <l:gentext key="Important" text="Importante"/>
+  <l:gentext key="important" text="Importante"/>
+  <l:gentext key="Index" text="&#205;ndice Remissivo"/>
+  <l:gentext key="index" text="&#205;ndice Remissivo"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Nota Legal"/>
+  <l:gentext key="legalnotice" text="Nota Legal"/>
+  <l:gentext key="MsgAud" text="Audi&#234;ncia"/>
+  <l:gentext key="msgaud" text="Audi&#234;ncia"/>
+  <l:gentext key="MsgLevel" text="N&#237;vel"/>
+  <l:gentext key="msglevel" text="N&#237;vel"/>
+  <l:gentext key="MsgOrig" text="Origem"/>
+  <l:gentext key="msgorig" text="Origem"/>
+  <l:gentext key="NOTE" text="NOTA"/>
+  <l:gentext key="Note" text="Nota"/>
+  <l:gentext key="note" text="Nota"/>
+  <l:gentext key="Part" text="Parte"/>
+  <l:gentext key="part" text="Parte"/>
+  <l:gentext key="Preface" text="Pref&#225;cio"/>
+  <l:gentext key="preface" text="Pref&#225;cio"/>
+  <l:gentext key="Procedure" text="Procedimento"/>
+  <l:gentext key="procedure" text="Procedimento"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="PubDate" text="Data de Publica&#231;&#227;o"/>
+  <l:gentext key="pubdate" text="Data de Publica&#231;&#227;o"/>
+  <l:gentext key="Published" text="Publicado"/>
+  <l:gentext key="published" text="Publicado"/>
+  <l:gentext key="Question" text="P:"/>
+  <l:gentext key="question" text="P:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Refer&#234;ncia"/>
+  <l:gentext key="reference" text="Refer&#234;ncia"/>
+  <l:gentext key="RefName" text="Nome"/>
+  <l:gentext key="refname" text="Nome"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Sinopse"/>
+  <l:gentext key="refsynopsisdiv" text="Sinopse"/>
+  <l:gentext key="RevHistory" text="Hist&#243;rico de Revis&#245;es"/>
+  <l:gentext key="revhistory" text="Hist&#243;rico de Revis&#245;es"/>
+  <l:gentext key="Revision" text="Revis&#227;o"/>
+  <l:gentext key="revision" text="Revis&#227;o"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="Se&#231;&#227;o"/>
+  <l:gentext key="section" text="se&#231;&#227;o"/>
+  <l:gentext key="See" text="Ver"/>
+  <l:gentext key="see" text="Ver"/>
+  <l:gentext key="SeeAlso" text="Ver Tamb&#233;m"/>
+  <l:gentext key="Seealso" text="ver tamb&#233;m"/>
+  <l:gentext key="seealso" text="Ver Tamb&#233;m"/>
+  <l:gentext key="Set" text="Conjunto"/>
+  <l:gentext key="set" text="Conjunto"/>
+  <l:gentext key="SetIndex" text="&#205;ndice do Conjunto"/>
+  <l:gentext key="setindex" text="&#205;ndice do Conjunto"/>
+  <l:gentext key="Sidebar" text="Quadro Lateral"/>
+  <l:gentext key="sidebar" text="quadro lateral"/>
+  <l:gentext key="Step" text="Passo"/>
+  <l:gentext key="step" text="passo"/>
+  <l:gentext key="Table" text="Tabela"/>
+  <l:gentext key="table" text="Tabela"/>
+  <l:gentext key="TIP" text="DICA"/>
+  <l:gentext key="Tip" text="Dica"/>
+  <l:gentext key="tip" text="Dica"/>
+  <l:gentext key="WARNING" text="ATEN&#199;&#195;O"/>
+  <l:gentext key="Warning" text="Aten&#231;&#227;o"/>
+  <l:gentext key="warning" text="Aten&#231;&#227;o"/>
+  <l:gentext key="and" text="e"/>
+  <l:gentext key="by" text="por"/>
+  <l:gentext key="edited" text="Editado"/>
+  <l:gentext key="Edited" text="Editado"/>
+  <l:gentext key="editedby" text="Editado por"/>
+  <l:gentext key="Editedby" text="Editado por"/>
+  <l:gentext key="in" text=""/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="elemento inexistente"/>
+  <l:gentext key="Notes" text="Notas"/>
+  <l:gentext key="notes" text="Notas"/>
+  <l:gentext key="Pgs" text="P&#225;ginas"/>
+  <l:gentext key="pgs" text="P&#225;ginas"/>
+  <l:gentext key="Revisedby" text="Revisado por: "/>
+  <l:gentext key="revisedby" text="Revisado por: "/>
+  <l:gentext key="tablenotes" text="Notas"/>
+  <l:gentext key="TableNotes" text="Notas"/>
+  <l:gentext key="TableofContents" text="&#205;ndice"/>
+  <l:gentext key="tableofcontents" text="&#205;ndice"/>
+  <l:gentext key="unexpectedelementname" text="Nome de elemento inesperado"/>
+  <l:gentext key="unsupported" text="n&#227;o suportado"/>
+  <l:gentext key="xrefto" text="refer&#234;ncia para"/>
+  <l:gentext key="listofequations" text="Lista de Equa&#231;&#245;es"/>
+  <l:gentext key="ListofEquations" text="Lista de Equa&#231;&#245;es"/>
+  <l:gentext key="ListofExamples" text="Lista de Exemplos"/>
+  <l:gentext key="listofexamples" text="Lista de Exemplos"/>
+  <l:gentext key="ListofFigures" text="Lista de Figuras"/>
+  <l:gentext key="listoffigures" text="Lista de Figuras"/>
+  <l:gentext key="listoftables" text="Lista de Tabelas"/>
+  <l:gentext key="ListofTables" text="Lista de Tabelas"/>
+  <l:gentext key="ListofUnknown" text="Lista de ???"/>
+  <l:gentext key="listofunknown" text="Lista de ???"/>
+  <l:gentext key="nav-home" text="Principal"/>
+  <l:gentext key="nav-next" text="Pr&#243;xima"/>
+  <l:gentext key="nav-next-sibling" text="Fim"/>
+  <l:gentext key="nav-prev" text="Anterior"/>
+  <l:gentext key="nav-prev-sibling" text="In&#237;cio"/>
+  <l:gentext key="nav-up" text="Acima"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/pt_br.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Ap&#234;ndice %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Cap&#237;tulo %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Equa&#231;&#227;o %n. %t"/>
+    <l:template name="example" text="Exemplo %n. %t"/>
+    <l:template name="figure" text="Figura %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Parte %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedimento&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabela %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Ap&#234;ndice %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Cap&#237;tulo %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="R:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="P:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="P:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="R:&#160;%n"/>
+    <l:template name="appendix" text="Ap&#234;ndice&#160;%n"/>
+    <l:template name="bridgehead" text="Se&#231;&#227;o&#160;%n"/>
+    <l:template name="chapter" text="Cap&#237;tulo&#160;%n"/>
+    <l:template name="equation" text="Equa&#231;&#227;o&#160;%n"/>
+    <l:template name="example" text="Exemplo&#160;%n"/>
+    <l:template name="figure" text="Figura&#160;%n"/>
+    <l:template name="part" text="Parte&#160;%n"/>
+    <l:template name="procedure" text="Procedimento&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="P:&#160;%n"/>
+    <l:template name="question" text="P:&#160;%n"/>
+    <l:template name="sect1" text="Se&#231;&#227;o&#160;%n"/>
+    <l:template name="sect2" text="Se&#231;&#227;o&#160;%n"/>
+    <l:template name="sect3" text="Se&#231;&#227;o&#160;%n"/>
+    <l:template name="sect4" text="Se&#231;&#227;o&#160;%n"/>
+    <l:template name="sect5" text="Se&#231;&#227;o&#160;%n"/>
+    <l:template name="section" text="Se&#231;&#227;o&#160;%n"/>
+    <l:template name="table" text="Tabela&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Ap&#234;ndice&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Se&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Cap&#237;tulo&#160;%n, %t"/>
+    <l:template name="equation" text="Equa&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Exemplo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figura&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Parte&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procedimento&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Se&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Se&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Se&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Se&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Se&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Se&#231;&#227;o&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabela&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" e "/>
+    <l:template name="seplast" text=", e "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Ver "/>
+    <l:template name="seealso" text="Ver Tamb&#233;m "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Audi&#234;ncia: "/>
+    <l:template name="MsgLevel" text="N&#237;vel: "/>
+    <l:template name="MsgOrig" text="Origem: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0416 Portuguese (BRAZIL)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/ro.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/ro.xml
new file mode 100644
index 00000000000..cab93834425
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/ro.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="ro" english-language-name="Romanian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ro.xml -->
+  <l:gentext key="Abstract" text="Rezumat"/>
+  <l:gentext key="abstract" text="Rezumat"/>
+  <l:gentext key="Answer" text="A:"/>
+  <l:gentext key="answer" text="A:"/>
+  <l:gentext key="Appendix" text="Anexa"/>
+  <l:gentext key="appendix" text="anexa"/>
+  <l:gentext key="Article" text="Articol"/>
+  <l:gentext key="article" text="Articol"/>
+  <l:gentext key="Bibliography" text="Bibliografie"/>
+  <l:gentext key="bibliography" text="Bibliografie"/>
+  <l:gentext key="Book" text="Carte"/>
+  <l:gentext key="book" text="Carte"/>
+  <l:gentext key="CAUTION" text="ATEN&#222;IE"/>
+  <l:gentext key="Caution" text="Aten&#254;ie"/>
+  <l:gentext key="caution" text="Aten&#254;ie"/>
+  <l:gentext key="Chapter" text="Cap."/>
+  <l:gentext key="chapter" text="cap."/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Dedica&#254;ie"/>
+  <l:gentext key="dedication" text="Dedica&#254;ie"/>
+  <l:gentext key="Edition" text="Edi&#254;ie"/>
+  <l:gentext key="edition" text="Edi&#254;ie"/>
+  <l:gentext key="Equation" text="ecua&#254;ia"/>
+  <l:gentext key="equation" text="ecua&#254;ia"/>
+  <l:gentext key="Example" text="Exemplu"/>
+  <l:gentext key="example" text="Exemplu"/>
+  <l:gentext key="Figure" text="Fig."/>
+  <l:gentext key="figure" text="Fig."/>
+  <l:gentext key="Glossary" text="Glosar"/>
+  <l:gentext key="glossary" text="Glosar"/>
+  <l:gentext key="GlossSee" text="Vezi"/>
+  <l:gentext key="glosssee" text="Vezi"/>
+  <l:gentext key="GlossSeeAlso" text="Vezi &#351;i"/>
+  <l:gentext key="glossseealso" text="Vezi &#351;i"/>
+  <l:gentext key="IMPORTANT" text="IMPORTANT"/>
+  <l:gentext key="Important" text="Important"/>
+  <l:gentext key="important" text="Important"/>
+  <l:gentext key="Index" text="Index"/>
+  <l:gentext key="index" text="Index"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text=""/>
+  <l:gentext key="legalnotice" text=""/>
+  <l:gentext key="MsgAud" text=""/>
+  <l:gentext key="msgaud" text=""/>
+  <l:gentext key="MsgLevel" text="Nivel"/>
+  <l:gentext key="msglevel" text="Nivel"/>
+  <l:gentext key="MsgOrig" text="Origine"/>
+  <l:gentext key="msgorig" text="Origine"/>
+  <l:gentext key="NOTE" text="NOT&#195;"/>
+  <l:gentext key="Note" text="Not&#227;"/>
+  <l:gentext key="note" text="Not&#227;"/>
+  <l:gentext key="Part" text="Parte"/>
+  <l:gentext key="part" text="Parte"/>
+  <l:gentext key="Preface" text="Prefa&#254;&#227;"/>
+  <l:gentext key="preface" text="Prefa&#254;&#227;"/>
+  <l:gentext key="Procedure" text="Procedur&#227;"/>
+  <l:gentext key="procedure" text="Procedur&#227;"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="Publicat"/>
+  <l:gentext key="published" text="Publicat"/>
+  <l:gentext key="Question" text="Q:"/>
+  <l:gentext key="question" text="Q:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Referin&#254;&#227;"/>
+  <l:gentext key="reference" text="Referin&#254;&#227;"/>
+  <l:gentext key="RefName" text="Nume"/>
+  <l:gentext key="refname" text="Nume"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Rezumat"/>
+  <l:gentext key="refsynopsisdiv" text="Rezumat"/>
+  <l:gentext key="RevHistory" text="Istoricul versiunilor"/>
+  <l:gentext key="revhistory" text="Istoricul versiunilor"/>
+  <l:gentext key="Revision" text="Versiune"/>
+  <l:gentext key="revision" text="Versiune"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="Sec&#254;iune"/>
+  <l:gentext key="section" text="sec."/>
+  <l:gentext key="See" text="Vezi"/>
+  <l:gentext key="see" text="Vezi"/>
+  <l:gentext key="SeeAlso" text="Vezi &#351;i"/>
+  <l:gentext key="Seealso" text="Vezi &#351;i"/>
+  <l:gentext key="seealso" text="Vezi &#351;i"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="SetIndex" text="Index"/>
+  <l:gentext key="setindex" text="Index"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="Step" text="Opera&#254;ie"/>
+  <l:gentext key="step" text="opera&#254;iune"/>
+  <l:gentext key="Table" text="Tabel"/>
+  <l:gentext key="table" text="Tabel"/>
+  <l:gentext key="TIP" text="INDICA&#222;IE"/>
+  <l:gentext key="Tip" text="Indica&#254;ie"/>
+  <l:gentext key="tip" text="Indica&#254;ie"/>
+  <l:gentext key="WARNING" text="AVERTISMENT"/>
+  <l:gentext key="Warning" text="Avertisment"/>
+  <l:gentext key="warning" text="Avertisment"/>
+  <l:gentext key="and" text="&#351;i"/>
+  <l:gentext key="by" text="de"/>
+  <l:gentext key="Edited" text="Publicat"/>
+  <l:gentext key="edited" text="Publicat"/>
+  <l:gentext key="Editedby" text="Publicat de"/>
+  <l:gentext key="editedby" text="Publicat de"/>
+  <l:gentext key="in" text="&#238;n"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="element inexistent"/>
+  <l:gentext key="notes" text="Note"/>
+  <l:gentext key="Notes" text="Note"/>
+  <l:gentext key="Pgs" text="Pagini"/>
+  <l:gentext key="pgs" text="Pagini"/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text="Remarci"/>
+  <l:gentext key="tablenotes" text="Remarci"/>
+  <l:gentext key="TableofContents" text="Cuprins"/>
+  <l:gentext key="tableofcontents" text="Cuprins"/>
+  <l:gentext key="unexpectedelementname" text="Nume de element nea&#351;teptat"/>
+  <l:gentext key="unsupported" text="nerecunoscut de sisitem"/>
+  <l:gentext key="xrefto" text="referin&#254;&#227; c&#227;tre"/>
+  <l:gentext key="listofequations" text="List&#227; de ecua&#254;ii"/>
+  <l:gentext key="ListofEquations" text="List&#227; de ecua&#254;ii"/>
+  <l:gentext key="ListofExamples" text="List&#227; de exemple"/>
+  <l:gentext key="listofexamples" text="List&#227; de exemple"/>
+  <l:gentext key="ListofFigures" text="List&#227; de figuri"/>
+  <l:gentext key="listoffigures" text="List&#227; de figuri"/>
+  <l:gentext key="listoftables" text="List&#227; de tabele"/>
+  <l:gentext key="ListofTables" text="List&#227; de tabele"/>
+  <l:gentext key="ListofUnknown" text="List&#227; de necunoscute"/>
+  <l:gentext key="listofunknown" text="List&#227; de necunoscute"/>
+  <l:gentext key="nav-home" text="Acas&#227;"/>
+  <l:gentext key="nav-next" text="&#206;nainte"/>
+  <l:gentext key="nav-next-sibling" text="Repede &#239;nainte"/>
+  <l:gentext key="nav-prev" text="&#206;napoi"/>
+  <l:gentext key="nav-prev-sibling" text="Repede &#238;napoi"/>
+  <l:gentext key="nav-up" text="Sus"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ro.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Anexa %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Cap. %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="ecua&#254;ia %n. %t"/>
+    <l:template name="example" text="Exemplu %n. %t"/>
+    <l:template name="figure" text="Fig. %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Parte %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedur&#227;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabel %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Anexa %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Cap. %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="Anexa&#160;%n"/>
+    <l:template name="bridgehead" text="Sec&#254;iune&#160;%n"/>
+    <l:template name="chapter" text="Cap.&#160;%n"/>
+    <l:template name="equation" text="ecua&#254;ia&#160;%n"/>
+    <l:template name="example" text="Exemplu&#160;%n"/>
+    <l:template name="figure" text="Fig.&#160;%n"/>
+    <l:template name="part" text="Parte&#160;%n"/>
+    <l:template name="procedure" text="Procedur&#227;&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="sect1" text="Sec&#254;iune&#160;%n"/>
+    <l:template name="sect2" text="Sec&#254;iune&#160;%n"/>
+    <l:template name="sect3" text="Sec&#254;iune&#160;%n"/>
+    <l:template name="sect4" text="Sec&#254;iune&#160;%n"/>
+    <l:template name="sect5" text="Sec&#254;iune&#160;%n"/>
+    <l:template name="section" text="Sec&#254;iune&#160;%n"/>
+    <l:template name="table" text="Tabel&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Anexa&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Sec&#254;iune&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Cap.&#160;%n, %t"/>
+    <l:template name="equation" text="ecua&#254;ia&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Exemplu&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Fig.&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Parte&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procedur&#227;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Sec&#254;iune&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Sec&#254;iune&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Sec&#254;iune&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Sec&#254;iune&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Sec&#254;iune&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Sec&#254;iune&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabel&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#351;i "/>
+    <l:template name="seplast" text=", &#351;i "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Vezi "/>
+    <l:template name="seealso" text="Vezi &#351;i "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text=": "/>
+    <l:template name="MsgLevel" text="Nivel: "/>
+    <l:template name="MsgOrig" text="Origine: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0418 Romanian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/ru.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/ru.xml
new file mode 100644
index 00000000000..ad5dd822ad5
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/ru.xml
@@ -0,0 +1,517 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="ru" english-language-name="Russian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ru.xml -->
+  <l:gentext key="Abstract" text="&#1040;&#1085;&#1085;&#1086;&#1090;&#1072;&#1094;&#1080;&#1103;"/>
+  <l:gentext key="abstract" text="&#1040;&#1085;&#1085;&#1086;&#1090;&#1072;&#1094;&#1080;&#1103;"/>
+  <l:gentext key="Answer" text="&#1054;:"/>
+  <l:gentext key="answer" text="&#1054;:"/>
+  <l:gentext key="Appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="appendix" text="&#1087;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Appendix.abr" text="&#1055;&#1088;&#1080;&#1083;."/>
+  <l:gentext key="appendix.abr" text="&#1055;&#1088;&#1080;&#1083;."/>
+  <l:gentext key="Article" text="&#1057;&#1090;&#1072;&#1090;&#1100;&#1103;"/>
+  <l:gentext key="article" text="&#1057;&#1090;&#1072;&#1090;&#1100;&#1103;"/>
+  <l:gentext key="Audience" text="&#1040;&#1091;&#1076;&#1080;&#1090;&#1086;&#1088;&#1080;&#1103;"/>
+  <l:gentext key="audience" text="&#1040;&#1091;&#1076;&#1080;&#1090;&#1086;&#1088;&#1080;&#1103;"/>
+  <l:gentext key="Bibliography" text="&#1051;&#1080;&#1090;&#1077;&#1088;&#1072;&#1090;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="bibliography" text="&#1051;&#1080;&#1090;&#1077;&#1088;&#1072;&#1090;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="Book" text="&#1050;&#1085;&#1080;&#1075;&#1072;"/>
+  <l:gentext key="book" text="&#1050;&#1085;&#1080;&#1075;&#1072;"/>
+  <l:gentext key="CAUTION" text="&#1055;&#1056;&#1045;&#1044;&#1054;&#1057;&#1058;&#1045;&#1056;&#1045;&#1046;&#1045;&#1053;&#1048;&#1045;"/>
+  <l:gentext key="Caution" text="&#1055;&#1088;&#1077;&#1076;&#1086;&#1089;&#1090;&#1077;&#1088;&#1077;&#1078;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="caution" text="&#1055;&#1088;&#1077;&#1076;&#1086;&#1089;&#1090;&#1077;&#1088;&#1077;&#1078;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072;"/>
+  <l:gentext key="chapter" text="&#1075;&#1083;&#1072;&#1074;&#1072;"/>
+  <l:gentext key="Chapter.abr" text="&#1043;&#1083;."/>
+  <l:gentext key="chapter.abr" text="&#1043;&#1083;."/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="&#1055;&#1086;&#1089;&#1074;&#1103;&#1097;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="dedication" text="&#1055;&#1086;&#1089;&#1074;&#1103;&#1097;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Edition" text="&#1056;&#1077;&#1076;&#1072;&#1082;&#1094;&#1080;&#1103;"/>
+  <l:gentext key="edition" text="&#1056;&#1077;&#1076;&#1072;&#1082;&#1094;&#1080;&#1103;"/>
+  <l:gentext key="Equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;"/>
+  <l:gentext key="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;"/>
+  <l:gentext key="Equation.abr" text="&#1060;."/>
+  <l:gentext key="equation.abr" text="&#1060;."/>
+  <l:gentext key="Example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;"/>
+  <l:gentext key="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;"/>
+  <l:gentext key="Example.abr" text="&#1055;&#1088;&#1080;&#1084;."/>
+  <l:gentext key="example.abr" text="&#1055;&#1088;&#1080;&#1084;."/>
+  <l:gentext key="Figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082;"/>
+  <l:gentext key="figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082;"/>
+  <l:gentext key="Figure.abr" text="&#1056;&#1080;&#1089;."/>
+  <l:gentext key="figure.abr" text="&#1056;&#1080;&#1089;."/>
+  <l:gentext key="Glossary" text="&#1043;&#1083;&#1086;&#1089;&#1089;&#1072;&#1088;&#1080;&#1081;"/>
+  <l:gentext key="glossary" text="&#1043;&#1083;&#1086;&#1089;&#1089;&#1072;&#1088;&#1080;&#1081;"/>
+  <l:gentext key="GlossSee" text="&#1057;&#1084;."/>
+  <l:gentext key="glosssee" text="&#1057;&#1084;."/>
+  <l:gentext key="GlossSeeAlso" text="&#1057;&#1084;. &#1090;&#1072;&#1082;&#1078;&#1077;"/>
+  <l:gentext key="glossseealso" text="&#1057;&#1084;. &#1090;&#1072;&#1082;&#1078;&#1077;"/>
+  <l:gentext key="IMPORTANT" text="&#1042;&#1040;&#1046;&#1053;&#1054;"/>
+  <l:gentext key="Important" text="&#1042;&#1072;&#1078;&#1085;&#1086;"/>
+  <l:gentext key="important" text="&#1042;&#1072;&#1078;&#1085;&#1086;"/>
+  <l:gentext key="Index" text="&#1055;&#1088;&#1077;&#1076;&#1084;&#1077;&#1090;&#1085;&#1099;&#1081; &#1091;&#1082;&#1072;&#1079;&#1072;&#1090;&#1077;&#1083;&#1100;"/>
+  <l:gentext key="index" text="&#1055;&#1088;&#1077;&#1076;&#1084;&#1077;&#1090;&#1085;&#1099;&#1081; &#1091;&#1082;&#1072;&#1079;&#1072;&#1090;&#1077;&#1083;&#1100;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="&#1040;&#1074;&#1090;&#1086;&#1088;&#1089;&#1082;&#1080;&#1077; &#1087;&#1088;&#1072;&#1074;&#1072;"/>
+  <l:gentext key="legalnotice" text="&#1040;&#1074;&#1090;&#1086;&#1088;&#1089;&#1082;&#1080;&#1077; &#1087;&#1088;&#1072;&#1074;&#1072;"/>
+  <l:gentext key="Level" text="&#1059;&#1088;&#1086;&#1074;&#1077;&#1085;&#1100;"/>
+  <l:gentext key="level" text="&#1059;&#1088;&#1086;&#1074;&#1077;&#1085;&#1100;"/>
+  <l:gentext key="MsgAud" text="Audience"/>
+  <l:gentext key="msgaud" text="Audience"/>
+  <l:gentext key="MsgLevel" text="Level"/>
+  <l:gentext key="msglevel" text="Level"/>
+  <l:gentext key="MsgOrig" text="Origin"/>
+  <l:gentext key="msgorig" text="Origin"/>
+  <l:gentext key="Name" text="&#1048;&#1084;&#1103;"/>
+  <l:gentext key="name" text="&#1048;&#1084;&#1103;"/>
+  <l:gentext key="NOTE" text="&#1047;&#1040;&#1052;&#1045;&#1063;&#1040;&#1053;&#1048;&#1045;"/>
+  <l:gentext key="Note" text="&#1047;&#1072;&#1084;&#1077;&#1095;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="note" text="&#1047;&#1072;&#1084;&#1077;&#1095;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Origin" text="&#1048;&#1089;&#1090;&#1086;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="origin" text="&#1048;&#1089;&#1090;&#1086;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="Part" text="&#1063;&#1072;&#1089;&#1090;&#1100;"/>
+  <l:gentext key="part" text="&#1063;&#1072;&#1089;&#1090;&#1100;"/>
+  <l:gentext key="Part.abr" text="&#1063;."/>
+  <l:gentext key="part.abr" text="&#1063;."/>
+  <l:gentext key="Preface" text="&#1055;&#1088;&#1077;&#1076;&#1080;&#1089;&#1083;&#1086;&#1074;&#1080;&#1077;"/>
+  <l:gentext key="preface" text="&#1055;&#1088;&#1077;&#1076;&#1080;&#1089;&#1083;&#1086;&#1074;&#1080;&#1077;"/>
+  <l:gentext key="Procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="Procedure.abr" text="&#1055;&#1088;&#1086;&#1094;."/>
+  <l:gentext key="procedure.abr" text="&#1055;&#1088;&#1086;&#1094;."/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="&#1054;&#1087;&#1091;&#1073;&#1083;&#1080;&#1082;&#1086;&#1074;&#1072;&#1085;&#1086;"/>
+  <l:gentext key="published" text="&#1054;&#1087;&#1091;&#1073;&#1083;&#1080;&#1082;&#1086;&#1074;&#1072;&#1085;&#1086;"/>
+  <l:gentext key="Question" text="&#1042;:"/>
+  <l:gentext key="question" text="&#1042;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#1057;&#1089;&#1099;&#1083;&#1082;&#1072;"/>
+  <l:gentext key="reference" text="&#1057;&#1089;&#1099;&#1083;&#1082;&#1072;"/>
+  <l:gentext key="RefName" text="&#1053;&#1072;&#1079;&#1074;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="refname" text="&#1053;&#1072;&#1079;&#1074;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#1057;&#1080;&#1085;&#1090;&#1072;&#1082;&#1089;&#1080;&#1089;"/>
+  <l:gentext key="refsynopsisdiv" text="&#1057;&#1080;&#1085;&#1090;&#1072;&#1082;&#1089;&#1080;&#1089;"/>
+  <l:gentext key="RevHistory" text="&#1048;&#1089;&#1090;&#1086;&#1088;&#1080;&#1103; &#1087;&#1077;&#1088;&#1077;&#1080;&#1079;&#1076;&#1072;&#1085;&#1080;&#1103;"/>
+  <l:gentext key="revhistory" text="&#1048;&#1089;&#1090;&#1086;&#1088;&#1080;&#1103; &#1087;&#1077;&#1088;&#1077;&#1080;&#1079;&#1076;&#1072;&#1085;&#1080;&#1103;"/>
+  <l:gentext key="Revision" text="&#1048;&#1079;&#1076;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="revision" text="&#1048;&#1079;&#1076;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="sect1" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="sect2" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="sect3" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="sect4" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="sect5" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="Section" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="section" text="&#1088;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="Section.abr" text="&#1056;&#1072;&#1079;&#1076;."/>
+  <l:gentext key="section.abr" text="&#1056;&#1072;&#1079;&#1076;."/>
+  <l:gentext key="See" text="&#1057;&#1084;."/>
+  <l:gentext key="see" text="&#1057;&#1084;."/>
+  <l:gentext key="SeeAlso" text="&#1057;&#1084;. &#1090;&#1072;&#1082;&#1078;&#1077;"/>
+  <l:gentext key="Seealso" text="&#1057;&#1084;. &#1090;&#1072;&#1082;&#1078;&#1077;"/>
+  <l:gentext key="seealso" text="&#1057;&#1084;. &#1090;&#1072;&#1082;&#1078;&#1077;"/>
+  <l:gentext key="Set" text="&#1055;&#1086;&#1076;&#1073;&#1086;&#1088;&#1082;&#1072;"/>
+  <l:gentext key="set" text="&#1055;&#1086;&#1076;&#1073;&#1086;&#1088;&#1082;&#1072;"/>
+  <l:gentext key="SetIndex" text="&#1048;&#1085;&#1076;&#1077;&#1082;&#1089; &#1087;&#1086;&#1076;&#1073;&#1086;&#1088;&#1082;&#1080;"/>
+  <l:gentext key="setindex" text="&#1048;&#1085;&#1076;&#1077;&#1082;&#1089; &#1087;&#1086;&#1076;&#1073;&#1086;&#1088;&#1082;&#1080;"/>
+  <l:gentext key="Sidebar" text="&#1042;&#1099;&#1076;&#1077;&#1083;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="sidebar" text="&#1074;&#1099;&#1076;&#1077;&#1083;&#1077;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="Step" text="&#1064;&#1072;&#1075;"/>
+  <l:gentext key="step" text="&#1096;&#1072;&#1075;"/>
+  <l:gentext key="Table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072;"/>
+  <l:gentext key="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072;"/>
+  <l:gentext key="Table.abr" text="&#1058;&#1072;&#1073;&#1083;."/>
+  <l:gentext key="table.abr" text="&#1058;&#1072;&#1073;&#1083;."/>
+  <l:gentext key="TIP" text="&#1055;&#1054;&#1044;&#1057;&#1050;&#1040;&#1047;&#1050;&#1040;"/>
+  <l:gentext key="Tip" text="&#1055;&#1086;&#1076;&#1089;&#1082;&#1072;&#1079;&#1082;&#1072;"/>
+  <l:gentext key="tip" text="&#1055;&#1086;&#1076;&#1089;&#1082;&#1072;&#1079;&#1082;&#1072;"/>
+  <l:gentext key="WARNING" text="&#1042;&#1053;&#1048;&#1052;&#1040;&#1053;&#1048;&#1045;"/>
+  <l:gentext key="Warning" text="&#1042;&#1085;&#1080;&#1084;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="warning" text="&#1042;&#1085;&#1080;&#1084;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="and" text=""/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="called" text=""/>
+  <l:gentext key="edited" text="&#1055;&#1086;&#1076; &#1088;&#1077;&#1076;&#1072;&#1082;&#1094;&#1080;&#1077;&#1081;"/>
+  <l:gentext key="Edited" text="&#1055;&#1086;&#1076; &#1088;&#1077;&#1076;&#1072;&#1082;&#1094;&#1080;&#1077;&#1081;"/>
+  <l:gentext key="Editedby" text="&#1055;&#1086;&#1076; &#1088;&#1077;&#1076;&#1072;&#1082;&#1094;&#1080;&#1077;&#1081;"/>
+  <l:gentext key="editedby" text="&#1055;&#1086;&#1076; &#1088;&#1077;&#1076;&#1072;&#1082;&#1094;&#1080;&#1077;&#1081;"/>
+  <l:gentext key="in" text="&#1074;"/>
+  <l:gentext key="TableofContents" text="&#1057;&#1086;&#1076;&#1077;&#1088;&#1078;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="tableofcontents" text="&#1057;&#1086;&#1076;&#1077;&#1088;&#1078;&#1072;&#1085;&#1080;&#1077;"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="Notes" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1095;&#1072;&#1085;&#1080;&#1103;"/>
+  <l:gentext key="notes" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1095;&#1072;&#1085;&#1080;&#1103;"/>
+  <l:gentext key="TableNotes" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1095;&#1072;&#1085;&#1080;&#1103;"/>
+  <l:gentext key="tablenotes" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1095;&#1072;&#1085;&#1080;&#1103;"/>
+  <l:gentext key="nonexistantelement" text="non-existant element"/>
+  <l:gentext key="pgs" text="&#1057;&#1090;&#1088;."/>
+  <l:gentext key="Pgs" text="&#1057;&#1090;&#1088;."/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="the" text=""/>
+  <l:gentext key="unexpectedelementname" text="unexpected element name"/>
+  <l:gentext key="unsupported" text="unsupported"/>
+  <l:gentext key="xrefto" text="xref to"/>
+  <l:gentext key="listofequations" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1092;&#1086;&#1088;&#1084;&#1091;&#1083;"/>
+  <l:gentext key="ListofEquations" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1092;&#1086;&#1088;&#1084;&#1091;&#1083;"/>
+  <l:gentext key="ListofExamples" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1087;&#1088;&#1080;&#1084;&#1077;&#1088;&#1086;&#1074;"/>
+  <l:gentext key="listofexamples" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1087;&#1088;&#1080;&#1084;&#1077;&#1088;&#1086;&#1074;"/>
+  <l:gentext key="ListofFigures" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1080;&#1083;&#1083;&#1102;&#1089;&#1090;&#1088;&#1072;&#1094;&#1080;&#1081;"/>
+  <l:gentext key="listoffigures" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1080;&#1083;&#1083;&#1102;&#1089;&#1090;&#1088;&#1072;&#1094;&#1080;&#1081;"/>
+  <l:gentext key="listoftables" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1090;&#1072;&#1073;&#1083;&#1080;&#1094;"/>
+  <l:gentext key="ListofTables" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1090;&#1072;&#1073;&#1083;&#1080;&#1094;"/>
+  <l:gentext key="ListofUnknown" text="&#1053;&#1077;&#1086;&#1087;&#1088;&#1077;&#1076;&#1077;&#1083;&#1077;&#1085;&#1085;&#1099;&#1081; &#1089;&#1087;&#1080;&#1089;&#1086;&#1082;"/>
+  <l:gentext key="listofunknown" text="&#1053;&#1077;&#1086;&#1087;&#1088;&#1077;&#1076;&#1077;&#1083;&#1077;&#1085;&#1085;&#1099;&#1081; &#1089;&#1087;&#1080;&#1089;&#1086;&#1082;"/>
+  <l:gentext key="nav-next" text="&#1057;&#1083;&#1077;&#1076;."/>
+  <l:gentext key="nav-next-sibling" text="&#1057;&#1083;&#1077;&#1076;. &#1087;&#1086;&#1076;&#1088;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="nav-prev" text="&#1055;&#1088;&#1077;&#1076;."/>
+  <l:gentext key="nav-prev-sibling" text="&#1055;&#1088;&#1077;&#1076;. &#1087;&#1086;&#1076;&#1088;&#1072;&#1079;&#1076;&#1077;&#1083;"/>
+  <l:gentext key="x-nav-next" text="&#1057;&#1083;&#1077;&#1076;."/>
+  <l:gentext key="nav-home" text="&#1053;&#1072;&#1095;&#1072;&#1083;&#1086;"/>
+  <l:gentext key="nav-up" text="&#1059;&#1088;&#1086;&#1074;&#1077;&#1085;&#1100; &#1074;&#1099;&#1096;&#1077;"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="&#1063;&#1077;&#1088;&#1085;&#1086;&#1074;&#1080;&#1082;"/>
+  <l:gentext key="above" text="&#1074;&#1099;&#1096;&#1077;"/>
+  <l:gentext key="below" text="&#1085;&#1080;&#1078;&#1077;"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="&#1072;&#1073;&#1074;&#1075;&#1076;&#1077;&#1105;&#1078;&#1079;&#1080;&#1081;&#1082;&#1083;&#1084;&#1085;&#1086;&#1087;&#1088;&#1089;&#1090;&#1091;&#1092;&#1093;&#1094;&#1095;&#1096;&#1097;&#1098;&#1099;&#1100;&#1101;&#1102;&#1103;"/>
+  <l:gentext key="uppercase.alpha" text="&#1040;&#1041;&#1042;&#1043;&#1044;&#1045;&#1025;&#1046;&#1047;&#1048;&#1049;&#1050;&#1051;&#1052;&#1053;&#1054;&#1055;&#1056;&#1057;&#1058;&#1059;&#1060;&#1061;&#1062;&#1063;&#1064;&#1065;&#1066;&#1067;&#1068;&#1069;&#1070;&#1071;"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/ru.xml -->
+  <l:dingbat key="startquote" text="&#171;"/>
+  <l:dingbat key="endquote" text="&#187;"/>
+  <l:dingbat key="nestedstartquote" text="&#8222;"/>
+  <l:dingbat key="nestedendquote" text="&#8220;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077; %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072; %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072; %n. %t"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088; %n. %t"/>
+    <l:template name="figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082; %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#1063;&#1072;&#1089;&#1090;&#1100; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072; %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077; %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072; %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#1054;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#1042;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#1042;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#171;%t&#187;"/>
+    <l:template name="refsection" text="&#171;%t&#187;"/>
+    <l:template name="refsect1" text="&#171;%t&#187;"/>
+    <l:template name="refsect2" text="&#171;%t&#187;"/>
+    <l:template name="refsect3" text="&#171;%t&#187;"/>
+    <l:template name="sect1" text="&#171;%t&#187;"/>
+    <l:template name="sect2" text="&#171;%t&#187;"/>
+    <l:template name="sect3" text="&#171;%t&#187;"/>
+    <l:template name="sect4" text="&#171;%t&#187;"/>
+    <l:template name="sect5" text="&#171;%t&#187;"/>
+    <l:template name="section" text="&#171;%t&#187;"/>
+    <l:template name="simplesect" text="&#171;%t&#187;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#1054;:&#160;%n"/>
+    <l:template name="appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;&#160;%n"/>
+    <l:template name="bridgehead" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072;&#160;%n"/>
+    <l:template name="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;&#160;%n"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;&#160;%n"/>
+    <l:template name="figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082;&#160;%n"/>
+    <l:template name="part" text="&#1063;&#1072;&#1089;&#1090;&#1100;&#160;%n"/>
+    <l:template name="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#1042;:&#160;%n"/>
+    <l:template name="question" text="&#1042;:&#160;%n"/>
+    <l:template name="sect1" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="sect2" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="sect3" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="sect4" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="sect5" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="section" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#1055;&#1088;&#1080;&#1083;&#1086;&#1078;&#1077;&#1085;&#1080;&#1077;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="chapter" text="&#1043;&#1083;&#1072;&#1074;&#1072;&#160;%n, %t"/>
+    <l:template name="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="part" text="&#1063;&#1072;&#1089;&#1090;&#1100;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#171;%t&#187;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#171;%t&#187;"/>
+    <l:template name="refsect1" text="the section called &#171;%t&#187;"/>
+    <l:template name="refsect2" text="the section called &#171;%t&#187;"/>
+    <l:template name="refsect3" text="the section called &#171;%t&#187;"/>
+    <l:template name="refsection" text="the section called &#171;%t&#187;"/>
+    <l:template name="sect1" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="sect2" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="sect3" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="sect4" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="sect5" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="section" text="&#1056;&#1072;&#1079;&#1076;&#1077;&#1083;&#160;%n, &#171;%t&#187;"/>
+    <l:template name="simplesect" text="the section called &#171;%t&#187;"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1072;&#160;%n, &#171;%t&#187;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text="  "/>
+    <l:template name="seplast" text=",  "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#1057;&#1084;. "/>
+    <l:template name="seealso" text="&#1057;&#1084;. &#1090;&#1072;&#1082;&#1078;&#1077; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Audience: "/>
+    <l:template name="MsgLevel" text="Level: "/>
+    <l:template name="MsgOrig" text="Origin: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="m/d/Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="&#1103;&#1085;&#1074;&#1072;&#1088;&#1103;"/>
+    <l:template name="February" text="&#1092;&#1077;&#1074;&#1088;&#1072;&#1083;&#1103;"/>
+    <l:template name="March" text="&#1084;&#1072;&#1088;&#1090;&#1072;"/>
+    <l:template name="April" text="&#1072;&#1087;&#1088;&#1077;&#1083;&#1103;"/>
+    <l:template name="May" text="&#1084;&#1072;&#1103;"/>
+    <l:template name="June" text="&#1080;&#1102;&#1085;&#1103;"/>
+    <l:template name="July" text="&#1080;&#1102;&#1083;&#1103;"/>
+    <l:template name="August" text="&#1072;&#1074;&#1075;&#1091;&#1089;&#1090;&#1072;"/>
+    <l:template name="September" text="&#1089;&#1077;&#1085;&#1090;&#1103;&#1073;&#1088;&#1103;"/>
+    <l:template name="October" text="&#1086;&#1082;&#1090;&#1103;&#1073;&#1088;&#1103;"/>
+    <l:template name="November" text="&#1085;&#1086;&#1103;&#1073;&#1088;&#1103;"/>
+    <l:template name="December" text="&#1076;&#1077;&#1082;&#1072;&#1073;&#1088;&#1103;"/>
+    <l:template name="Monday" text="&#1087;&#1086;&#1085;&#1077;&#1076;&#1077;&#1083;&#1100;&#1085;&#1080;&#1082;"/>
+    <l:template name="Tuesday" text="&#1074;&#1090;&#1086;&#1088;&#1085;&#1080;&#1082;"/>
+    <l:template name="Wednesday" text="&#1089;&#1088;&#1077;&#1076;&#1072;"/>
+    <l:template name="Thursday" text="&#1095;&#1077;&#1090;&#1074;&#1101;&#1088;&#1075;"/>
+    <l:template name="Friday" text="&#1087;&#1103;&#1090;&#1085;&#1080;&#1094;&#1072;"/>
+    <l:template name="Saturday" text="&#1089;&#1091;&#1073;&#1073;&#1086;&#1090;&#1072;"/>
+    <l:template name="Sunday" text="&#1074;&#1086;&#1089;&#1082;&#1088;&#1077;&#1089;&#1077;&#1085;&#1100;&#1077;"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="&#1071;&#1085;&#1074;"/>
+    <l:template name="Feb" text="&#1060;&#1077;&#1074;"/>
+    <l:template name="Mar" text="&#1052;&#1072;&#1088;"/>
+    <l:template name="Apr" text="&#1040;&#1087;&#1088;"/>
+    <l:template name="May" text="&#1052;&#1072;&#1081;"/>
+    <l:template name="Jun" text="&#1048;&#1102;&#1085;"/>
+    <l:template name="Jul" text="&#1048;&#1102;&#1083;"/>
+    <l:template name="Aug" text="&#1040;&#1074;&#1075;"/>
+    <l:template name="Sep" text="&#1057;&#1077;&#1085;"/>
+    <l:template name="Oct" text="&#1054;&#1082;&#1090;"/>
+    <l:template name="Nov" text="&#1053;&#1086;&#1103;"/>
+    <l:template name="Dec" text="&#1044;&#1077;&#1082;"/>
+    <l:template name="Mon" text="&#1055;&#1085;&#1076;"/>
+    <l:template name="Tue" text="&#1042;&#1090;&#1088;"/>
+    <l:template name="Wed" text="&#1057;&#1088;&#1076;"/>
+    <l:template name="Thu" text="&#1063;&#1090;&#1074;"/>
+    <l:template name="Fri" text="&#1055;&#1090;&#1085;"/>
+    <l:template name="Sat" text="&#1057;&#1073;&#1090;"/>
+    <l:template name="Sun" text="&#1042;&#1089;&#1082;"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0419 Russian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/sk.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/sk.xml
new file mode 100644
index 00000000000..581a1d4d2cf
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/sk.xml
@@ -0,0 +1,488 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="sk" english-language-name="Slovak">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sk.xml -->
+  <l:gentext key="Abstract" text="Abstrakt"/>
+  <l:gentext key="abstract" text="Abstrakt"/>
+  <l:gentext key="Answer" text="A:"/>
+  <l:gentext key="answer" text="A:"/>
+  <l:gentext key="Appendix" text="Dodatok"/>
+  <l:gentext key="appendix" text="dodatok"/>
+  <l:gentext key="Article" text="&#268;l&#225;nok"/>
+  <l:gentext key="article" text="&#268;l&#225;nok"/>
+  <l:gentext key="Bibliography" text="Bibliografia"/>
+  <l:gentext key="bibliography" text="Bibliografia"/>
+  <l:gentext key="Book" text="Kniha"/>
+  <l:gentext key="book" text="Kniha"/>
+  <l:gentext key="CAUTION" text="V&#221;STRAHA"/>
+  <l:gentext key="Caution" text="V&#253;straha"/>
+  <l:gentext key="caution" text="V&#253;straha"/>
+  <l:gentext key="Chapter" text="Kapitola"/>
+  <l:gentext key="chapter" text="kapitola"/>
+  <l:gentext key="Colophon" text="Tir&#225;&#382;"/>
+  <l:gentext key="colophon" text="Tir&#225;&#382;"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Venovanie"/>
+  <l:gentext key="dedication" text="Venovanie"/>
+  <l:gentext key="Edition" text="Vydanie"/>
+  <l:gentext key="edition" text="Vydanie"/>
+  <l:gentext key="Equation" text="Rovnica"/>
+  <l:gentext key="equation" text="Rovnica"/>
+  <l:gentext key="Example" text="Pr&#237;klad"/>
+  <l:gentext key="example" text="Pr&#237;klad"/>
+  <l:gentext key="Figure" text="Obr&#225;zok"/>
+  <l:gentext key="figure" text="Obr&#225;zok"/>
+  <l:gentext key="Glossary" text="Slovn&#237;k"/>
+  <l:gentext key="glossary" text="Slovn&#237;k"/>
+  <l:gentext key="GlossSee" text="Pozri"/>
+  <l:gentext key="glosssee" text="Pozri"/>
+  <l:gentext key="GlossSeeAlso" text="Pozri tie&#382;"/>
+  <l:gentext key="glossseealso" text="Pozri tie&#382;"/>
+  <l:gentext key="IMPORTANT" text="D&#212;LE&#381;IT&#201;"/>
+  <l:gentext key="Important" text="D&#244;le&#382;it&#233;"/>
+  <l:gentext key="important" text="D&#244;le&#382;it&#233;"/>
+  <l:gentext key="Index" text="Zoznam"/>
+  <l:gentext key="index" text="Zoznam"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Pr&#225;vna pozn&#225;mka"/>
+  <l:gentext key="legalnotice" text="Pr&#225;vna pozn&#225;mka"/>
+  <l:gentext key="MsgAud" text="Publikum"/>
+  <l:gentext key="msgaud" text="Publikum"/>
+  <l:gentext key="MsgLevel" text="&#218;rove&#328;"/>
+  <l:gentext key="msglevel" text="&#218;rove&#328;"/>
+  <l:gentext key="MsgOrig" text="P&#244;vod"/>
+  <l:gentext key="msgorig" text="P&#244;vod"/>
+  <l:gentext key="NOTE" text="POZN&#193;MKA"/>
+  <l:gentext key="Note" text="Pozn&#225;mka"/>
+  <l:gentext key="note" text="Pozn&#225;mka"/>
+  <l:gentext key="Part" text="&#268;as&#357;"/>
+  <l:gentext key="part" text="&#268;as&#357;"/>
+  <l:gentext key="Preface" text="&#218;vod"/>
+  <l:gentext key="preface" text="&#218;vod"/>
+  <l:gentext key="Procedure" text="Postup"/>
+  <l:gentext key="procedure" text="Postup"/>
+  <l:gentext key="ProductionSet" text="Produkcia"/>
+  <l:gentext key="Published" text="Vydan&#233;"/>
+  <l:gentext key="published" text="Vydan&#233;"/>
+  <l:gentext key="Question" text="Q:"/>
+  <l:gentext key="question" text="Q:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Odkaz"/>
+  <l:gentext key="reference" text="Odkaz"/>
+  <l:gentext key="RefName" text="Meno"/>
+  <l:gentext key="refname" text="Meno"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Preh&#318;ad"/>
+  <l:gentext key="refsynopsisdiv" text="Preh&#318;ad"/>
+  <l:gentext key="RevHistory" text="Preh&#318;ad rev&#237;zi&#237;"/>
+  <l:gentext key="revhistory" text="Preh&#318;ad rev&#237;zi&#237;"/>
+  <l:gentext key="Revision" text="Rev&#237;zia"/>
+  <l:gentext key="revision" text="Rev&#237;zia"/>
+  <l:gentext key="sect1" text="Oddiel"/>
+  <l:gentext key="sect2" text="Oddiel"/>
+  <l:gentext key="sect3" text="Oddiel"/>
+  <l:gentext key="sect4" text="Oddiel"/>
+  <l:gentext key="sect5" text="Oddiel"/>
+  <l:gentext key="Section" text="Oddiel"/>
+  <l:gentext key="section" text="oddiel"/>
+  <l:gentext key="See" text="Pozri"/>
+  <l:gentext key="see" text="Pozri"/>
+  <l:gentext key="SeeAlso" text="Pozri tie&#382;"/>
+  <l:gentext key="Seealso" text="Pozri tie&#382;"/>
+  <l:gentext key="seealso" text="Pozri tie&#382;"/>
+  <l:gentext key="Set" text="Nastavi&#357;"/>
+  <l:gentext key="set" text="Nastavi&#357;"/>
+  <l:gentext key="SetIndex" text="Nastavi&#357; index"/>
+  <l:gentext key="setindex" text="nastavi&#357; index"/>
+  <l:gentext key="Sidebar" text="Margin&#225;lia"/>
+  <l:gentext key="sidebar" text="margin&#225;lia"/>
+  <l:gentext key="Step" text="Krok"/>
+  <l:gentext key="step" text="krok"/>
+  <l:gentext key="Table" text="Tabu&#318;ka"/>
+  <l:gentext key="table" text="Tabu&#318;ka"/>
+  <l:gentext key="TIP" text="TIP"/>
+  <l:gentext key="Tip" text="Tip"/>
+  <l:gentext key="tip" text="Tip"/>
+  <l:gentext key="WARNING" text="VAROVANIE"/>
+  <l:gentext key="Warning" text="Varovanie"/>
+  <l:gentext key="warning" text="Varovanie"/>
+  <l:gentext key="and" text="a"/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="Edited" text="Vydan&#233;"/>
+  <l:gentext key="edited" text="Vydan&#233;"/>
+  <l:gentext key="Editedby" text="Zostavil: "/>
+  <l:gentext key="editedby" text="Zostavil: "/>
+  <l:gentext key="in" text="v"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="neexistuj&#250;ci prvok"/>
+  <l:gentext key="notes" text="Pozn&#225;mky"/>
+  <l:gentext key="Notes" text="Pozn&#225;mky"/>
+  <l:gentext key="Pgs" text="Str."/>
+  <l:gentext key="pgs" text="Str."/>
+  <l:gentext key="Revisedby" text="Revidoval: "/>
+  <l:gentext key="revisedby" text="Revidoval: "/>
+  <l:gentext key="TableNotes" text="Pozn&#225;mky"/>
+  <l:gentext key="tablenotes" text="Pozn&#225;mky"/>
+  <l:gentext key="TableofContents" text="Obsah"/>
+  <l:gentext key="tableofcontents" text="Obsah"/>
+  <l:gentext key="unexpectedelementname" text="Neo&#269;ak&#225;van&#233; meno prvku"/>
+  <l:gentext key="unsupported" text="nepodporovan&#253;"/>
+  <l:gentext key="xrefto" text="xref k"/>
+  <l:gentext key="listofequations" text="Zoznam rovn&#237;c"/>
+  <l:gentext key="ListofEquations" text="Zoznam rovn&#237;c"/>
+  <l:gentext key="ListofExamples" text="Zoznam pr&#237;kladov"/>
+  <l:gentext key="listofexamples" text="Zoznam pr&#237;kladov"/>
+  <l:gentext key="ListofFigures" text="Zoznam obr&#225;zkov"/>
+  <l:gentext key="listoffigures" text="Zoznam obr&#225;zkov"/>
+  <l:gentext key="listoftables" text="Zoznam tabuliek"/>
+  <l:gentext key="ListofTables" text="Zoznam tabuliek"/>
+  <l:gentext key="ListofUnknown" text="Zoznam nezn&#225;meho"/>
+  <l:gentext key="listofunknown" text="Zoznam nezn&#225;meho"/>
+  <l:gentext key="nav-home" text="Domov"/>
+  <l:gentext key="nav-next" text="Nasleduj&#250;ci"/>
+  <l:gentext key="nav-next-sibling" text="R&#253;chlo dopredu"/>
+  <l:gentext key="nav-prev" text="Predch&#225;dzaj&#250;ci"/>
+  <l:gentext key="nav-prev-sibling" text="R&#253;chlo nazp&#228;t"/>
+  <l:gentext key="nav-up" text="Hore"/>
+  <l:gentext key="sectioncalled" text="oddiel nazvan&#253;"/>
+  <l:gentext key="Draft" text="Koncept"/>
+  <l:gentext key="above" text="nad"/>
+  <l:gentext key="below" text="pod"/>
+  <l:gentext key="index symbols" text="Symboly"/>
+  <l:gentext key="lowercase.alpha" text="a&#225;&#228;bc&#269;d&#271;e&#233;fghi&#237;jkl&#314;&#318;mn&#328;o&#243;&#244;pqr&#341;s&#353;t&#357;u&#250;vwxy&#253;z&#382;"/>
+  <l:gentext key="uppercase.alpha" text="A&#193;&#196;BC&#268;D&#270;E&#201;FGHI&#205;JKL&#313;&#317;MN&#327;O&#211;&#212;PQR&#340;S&#352;T&#356;U&#218;VWXY&#221;Z&#381;"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sk.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Dodatok %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Kapitola %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Rovnica %n. %t"/>
+    <l:template name="example" text="Pr&#237;klad %n. %t"/>
+    <l:template name="figure" text="Obr&#225;zok %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#268;as&#357; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Postup&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Produkcia&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabu&#318;ka %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Dodatok %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Kapitola %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="Dodatok&#160;%n"/>
+    <l:template name="bridgehead" text="Oddiel&#160;%n"/>
+    <l:template name="chapter" text="Kapitola&#160;%n"/>
+    <l:template name="equation" text="Rovnica&#160;%n"/>
+    <l:template name="example" text="Pr&#237;klad&#160;%n"/>
+    <l:template name="figure" text="Obr&#225;zok&#160;%n"/>
+    <l:template name="part" text="&#268;as&#357;&#160;%n"/>
+    <l:template name="procedure" text="Postup&#160;%n"/>
+    <l:template name="productionset" text="Produkcia&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Q:&#160;%n"/>
+    <l:template name="question" text="Q:&#160;%n"/>
+    <l:template name="sect1" text="Oddiel&#160;%n"/>
+    <l:template name="sect2" text="Oddiel&#160;%n"/>
+    <l:template name="sect3" text="Oddiel&#160;%n"/>
+    <l:template name="sect4" text="Oddiel&#160;%n"/>
+    <l:template name="sect5" text="Oddiel&#160;%n"/>
+    <l:template name="section" text="Oddiel&#160;%n"/>
+    <l:template name="table" text="Tabu&#318;ka&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Dodatok&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Oddiel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Kapitola&#160;%n, %t"/>
+    <l:template name="equation" text="Rovnica&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Pr&#237;klad&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Obr&#225;zok&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="&#268;as&#357;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Postup&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Produkcia&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="oddiel nazvan&#253; &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="oddiel nazvan&#253; &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="oddiel nazvan&#253; &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="oddiel nazvan&#253; &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Oddiel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Oddiel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Oddiel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Oddiel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Oddiel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Oddiel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="oddiel nazvan&#253; &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabu&#318;ka&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" a "/>
+    <l:template name="seplast" text=", a "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Pozri "/>
+    <l:template name="seealso" text="Pozri tie&#382; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Publikum: "/>
+    <l:template name="MsgLevel" text="&#218;rove&#328;: "/>
+    <l:template name="MsgOrig" text="P&#244;vod: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d.&#160;B Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="janu&#225;ra"/>
+    <l:template name="February" text="febru&#225;ra"/>
+    <l:template name="March" text="marca"/>
+    <l:template name="April" text="apr&#237;la"/>
+    <l:template name="May" text="m&#225;ja"/>
+    <l:template name="June" text="j&#250;na"/>
+    <l:template name="July" text="j&#250;la"/>
+    <l:template name="August" text="augusta"/>
+    <l:template name="September" text="septembra"/>
+    <l:template name="October" text="okt&#243;bra"/>
+    <l:template name="November" text="novembra"/>
+    <l:template name="December" text="decembra"/>
+    <l:template name="Monday" text="pondelok"/>
+    <l:template name="Tuesday" text="utorok"/>
+    <l:template name="Wednesday" text="streda"/>
+    <l:template name="Thursday" text="&#353;tvrtok"/>
+    <l:template name="Friday" text="piatok"/>
+    <l:template name="Saturday" text="sobota"/>
+    <l:template name="Sunday" text="nede&#318;a"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="jan"/>
+    <l:template name="Feb" text="feb"/>
+    <l:template name="Mar" text="mar"/>
+    <l:template name="Apr" text="apr"/>
+    <l:template name="May" text="m&#225;j"/>
+    <l:template name="Jun" text="j&#250;n"/>
+    <l:template name="Jul" text="j&#250;l"/>
+    <l:template name="Aug" text="aug"/>
+    <l:template name="Sep" text="sep"/>
+    <l:template name="Oct" text="okt"/>
+    <l:template name="Nov" text="nov"/>
+    <l:template name="Dec" text="dec"/>
+    <l:template name="Mon" text="po"/>
+    <l:template name="Tue" text="ut"/>
+    <l:template name="Wed" text="st"/>
+    <l:template name="Thu" text="&#353;t"/>
+    <l:template name="Fri" text="pi"/>
+    <l:template name="Sat" text="so"/>
+    <l:template name="Sun" text="ne"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x041b Slovak"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/sl.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/sl.xml
new file mode 100644
index 00000000000..1f417c4c02f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/sl.xml
@@ -0,0 +1,444 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="sl" english-language-name="Slovenian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sl.xml -->
+  <l:gentext key="Abstract" text="Povzetek"/>
+  <l:gentext key="abstract" text="Povzetek"/>
+  <l:gentext key="Answer" text="O:"/>
+  <l:gentext key="answer" text="O:"/>
+  <l:gentext key="Appendix" text="Dodatek"/>
+  <l:gentext key="appendix" text="dodatek"/>
+  <l:gentext key="Article" text="&#268;lanek"/>
+  <l:gentext key="article" text="&#268;lanek"/>
+  <l:gentext key="Bibliography" text="Literatura"/>
+  <l:gentext key="bibliography" text="Literatura"/>
+  <l:gentext key="Book" text="Knjiga"/>
+  <l:gentext key="book" text="Knjiga"/>
+  <l:gentext key="Caution" text="Opozorilo"/>
+  <l:gentext key="caution" text="Opozorilo"/>
+  <l:gentext key="CAUTION" text="OPOZORILO"/>
+  <l:gentext key="Chapter" text="Poglavje"/>
+  <l:gentext key="chapter" text="poglavje"/>
+  <l:gentext key="Colophon" text="Kolofon"/>
+  <l:gentext key="colophon" text="Kolofon"/>
+  <l:gentext key="Copyright" text="Pravna za&#353;&#269;ita"/>
+  <l:gentext key="copyright" text="Pravna za&#353;&#269;ita"/>
+  <l:gentext key="Dedication" text="Posvetilo"/>
+  <l:gentext key="dedication" text="Posvetilo"/>
+  <l:gentext key="Edition" text="Izdaja"/>
+  <l:gentext key="edition" text="Izdaja"/>
+  <l:gentext key="Equation" text="Ena&#269;ba"/>
+  <l:gentext key="equation" text="Ena&#269;ba"/>
+  <l:gentext key="Example" text="Primer"/>
+  <l:gentext key="example" text="Primer"/>
+  <l:gentext key="Figure" text="Slika"/>
+  <l:gentext key="figure" text="Slika"/>
+  <l:gentext key="Glossary" text="Slovar&#269;ek"/>
+  <l:gentext key="glossary" text="Slovar&#269;ek"/>
+  <l:gentext key="GlossSee" text="glej"/>
+  <l:gentext key="glosssee" text="glej"/>
+  <l:gentext key="GlossSeeAlso" text="glej tudi"/>
+  <l:gentext key="glossseealso" text="glej tudi"/>
+  <l:gentext key="IMPORTANT" text="POMEMBNO"/>
+  <l:gentext key="Important" text="Pomembno"/>
+  <l:gentext key="important" text="Pomembno"/>
+  <l:gentext key="Index" text="Stvarno kazalo"/>
+  <l:gentext key="index" text="Stvarno kazalo"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Pravno sporo&#269;ilo"/>
+  <l:gentext key="legalnotice" text="Pravno sporo&#269;ilo"/>
+  <l:gentext key="MsgAud" text="Ob&#269;instvo"/>
+  <l:gentext key="msgaud" text="Ob&#269;instvo"/>
+  <l:gentext key="MsgLevel" text="Raven"/>
+  <l:gentext key="msglevel" text="Raven"/>
+  <l:gentext key="MsgOrig" text="Izvor"/>
+  <l:gentext key="msgorig" text="Izvor"/>
+  <l:gentext key="note" text="Opomba"/>
+  <l:gentext key="NOTE" text="OPOMBA"/>
+  <l:gentext key="Note" text="Opomba"/>
+  <l:gentext key="Part" text="Del"/>
+  <l:gentext key="part" text="Del"/>
+  <l:gentext key="Preface" text="Predgovor"/>
+  <l:gentext key="preface" text="Predgovor"/>
+  <l:gentext key="Procedure" text="Postopek"/>
+  <l:gentext key="procedure" text="Postopek"/>
+  <l:gentext key="ProductionSet" text="Izdelava"/>
+  <l:gentext key="Published" text="Izdano"/>
+  <l:gentext key="published" text="Izdano"/>
+  <l:gentext key="Question" text="V:"/>
+  <l:gentext key="question" text="V:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Sklic"/>
+  <l:gentext key="reference" text="Sklic"/>
+  <l:gentext key="RefName" text="Ime"/>
+  <l:gentext key="refname" text="Ime"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Sinopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Sinopsis"/>
+  <l:gentext key="RevHistory" text="Zgodovina razli&#269;ic"/>
+  <l:gentext key="revhistory" text="Zgodovina razli&#269;ic"/>
+  <l:gentext key="Revision" text="Razli&#269;ica"/>
+  <l:gentext key="revision" text="Razli&#269;ica"/>
+  <l:gentext key="sect1" text="Razdelek"/>
+  <l:gentext key="sect2" text="Razdelek"/>
+  <l:gentext key="sect3" text="Razdelek"/>
+  <l:gentext key="sect4" text="Razdelek"/>
+  <l:gentext key="sect5" text="Razdelek"/>
+  <l:gentext key="Section" text="Razdelek"/>
+  <l:gentext key="section" text="razdelek"/>
+  <l:gentext key="see" text="glej"/>
+  <l:gentext key="See" text="glej"/>
+  <l:gentext key="Seealso" text="Glej tudi"/>
+  <l:gentext key="seealso" text="glej tudi"/>
+  <l:gentext key="SeeAlso" text="glej tudi"/>
+  <l:gentext key="Set" text="Postavi"/>
+  <l:gentext key="set" text="Postavi"/>
+  <l:gentext key="SetIndex" text="Postavi stvarno kazalo"/>
+  <l:gentext key="setindex" text="Postavi stvarno kazalo"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="step" text="korak"/>
+  <l:gentext key="Step" text="Korak"/>
+  <l:gentext key="table" text="Tabela"/>
+  <l:gentext key="Table" text="Tabela"/>
+  <l:gentext key="TIP" text="NAMIG"/>
+  <l:gentext key="Tip" text="Namig"/>
+  <l:gentext key="tip" text="Namig"/>
+  <l:gentext key="WARNING" text="POZOR"/>
+  <l:gentext key="Warning" text="Pozor"/>
+  <l:gentext key="warning" text="Pozor"/>
+  <l:gentext key="and" text="in"/>
+  <l:gentext key="by" text="od"/>
+  <l:gentext key="Edited" text="Urejeno"/>
+  <l:gentext key="edited" text="Urejeno"/>
+  <l:gentext key="Editedby" text="Uredil"/>
+  <l:gentext key="editedby" text="Uredil"/>
+  <l:gentext key="in" text="v"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="neobstoje&#269;i element"/>
+  <l:gentext key="Notes" text="Notes"/>
+  <l:gentext key="notes" text="Notes"/>
+  <l:gentext key="Pgs" text="Str."/>
+  <l:gentext key="pgs" text="Str."/>
+  <l:gentext key="Revisedby" text="Pregledal: "/>
+  <l:gentext key="revisedby" text="Pregledal: "/>
+  <l:gentext key="TableNotes" text="Notes"/>
+  <l:gentext key="tablenotes" text="Notes"/>
+  <l:gentext key="TableofContents" text="Kazalo"/>
+  <l:gentext key="tableofcontents" text="Kazalo"/>
+  <l:gentext key="unexpectedelementname" text="Nepri&#269;akovano ime elementa"/>
+  <l:gentext key="unsupported" text="nepodprto"/>
+  <l:gentext key="xrefto" text="xref na"/>
+  <l:gentext key="listofequations" text="Seznam ena&#269;b"/>
+  <l:gentext key="ListofEquations" text="Seznam ena&#269;b"/>
+  <l:gentext key="ListofExamples" text="Seznam primerov"/>
+  <l:gentext key="listofexamples" text="Seznam primerov"/>
+  <l:gentext key="ListofFigures" text="Seznam slik"/>
+  <l:gentext key="listoffigures" text="Seznam slik"/>
+  <l:gentext key="listoftables" text="Seznam tabel"/>
+  <l:gentext key="ListofTables" text="Seznam tabel"/>
+  <l:gentext key="ListofUnknown" text="Seznam neznanih stvari"/>
+  <l:gentext key="listofunknown" text="Seznam neznanih stvari"/>
+  <l:gentext key="nav-home" text="Domov"/>
+  <l:gentext key="nav-next" text="Naprej"/>
+  <l:gentext key="nav-next-sibling" text="Hitro naprej"/>
+  <l:gentext key="nav-prev" text="Nazaj"/>
+  <l:gentext key="nav-prev-sibling" text="Hitro nazaj"/>
+  <l:gentext key="nav-up" text="Gor"/>
+  <l:gentext key="sectioncalled" text="razdelek, imenovan"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Simboli"/>
+  <l:gentext key="lowercase.alpha" text="abc&#269;defghijklmnopqrs&#353;tuvwxyz&#382;"/>
+  <l:gentext key="uppercase.alpha" text="ABC&#268;DEFGHIJKLMNOPQRS&#352;TUVWXYZ&#381;"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sl.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Dodatek %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Poglavje %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Ena&#269;ba %n. %t"/>
+    <l:template name="example" text="Primer %n. %t"/>
+    <l:template name="figure" text="Slika %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Del %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Postopek %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Izdelava %n"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabela %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Dodatek %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Poglavje %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="O:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="V:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="V:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="O:&#160;%n"/>
+    <l:template name="appendix" text="Dodatek&#160;%n"/>
+    <l:template name="bridgehead" text="Razdelek&#160;%n"/>
+    <l:template name="chapter" text="Poglavje&#160;%n"/>
+    <l:template name="equation" text="Ena&#269;ba&#160;%n"/>
+    <l:template name="example" text="Primer&#160;%n"/>
+    <l:template name="figure" text="Slika&#160;%n"/>
+    <l:template name="part" text="Del&#160;%n"/>
+    <l:template name="procedure" text="Postopek&#160;%n"/>
+    <l:template name="productionset" text="Izdelava&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="V:&#160;%n"/>
+    <l:template name="question" text="V:&#160;%n"/>
+    <l:template name="sect1" text="Razdelek&#160;%n"/>
+    <l:template name="sect2" text="Razdelek&#160;%n"/>
+    <l:template name="sect3" text="Razdelek&#160;%n"/>
+    <l:template name="sect4" text="Razdelek&#160;%n"/>
+    <l:template name="sect5" text="Razdelek&#160;%n"/>
+    <l:template name="section" text="Razdelek&#160;%n"/>
+    <l:template name="table" text="Tabela&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Dodatek&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Razdelek&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Poglavje&#160;%n, %t"/>
+    <l:template name="equation" text="Ena&#269;ba&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Primer&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Slika&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Postopek&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Izdelava&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="razdelek, imenovan &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="razdelek, imenovan &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="razdelek, imenovan &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="razdelek, imenovan &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Razdelek&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Razdelek&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Razdelek&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Razdelek&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Razdelek&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Razdelek&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="razdelek, imenovan &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabela&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" in "/>
+    <l:template name="seplast" text=", in "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="glej "/>
+    <l:template name="seealso" text="glej tudi "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Ob&#269;instvo: "/>
+    <l:template name="MsgLevel" text="Raven: "/>
+    <l:template name="MsgOrig" text="Izvor: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0424 Slovenian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/sr.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/sr.xml
new file mode 100644
index 00000000000..af8e59879cc
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/sr.xml
@@ -0,0 +1,510 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="sr" english-language-name="Serbian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sr.xml -->
+  <l:gentext key="Abstract" text="&#1055;&#1088;&#1077;&#1075;&#1083;&#1077;&#1076;"/>
+  <l:gentext key="abstract" text="&#1087;&#1088;&#1077;&#1075;&#1083;&#1077;&#1076;"/>
+  <l:gentext key="Answer" text="&#1054;:"/>
+  <l:gentext key="answer" text="&#1086;:"/>
+  <l:gentext key="Appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1072;&#1082;"/>
+  <l:gentext key="appendix" text="&#1076;&#1086;&#1076;&#1072;&#1090;&#1072;&#1082;"/>
+  <l:gentext key="Article" text="&#1063;&#1083;&#1072;&#1085;&#1072;&#1082;"/>
+  <l:gentext key="article" text="&#1095;&#1083;&#1072;&#1085;&#1072;&#1082;"/>
+  <l:gentext key="Bibliography" text="&#1051;&#1080;&#1090;&#1077;&#1088;&#1072;&#1090;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="bibliography" text="&#1083;&#1080;&#1090;&#1077;&#1088;&#1072;&#1090;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="Book" text="&#1050;&#1114;&#1080;&#1075;&#1072;"/>
+  <l:gentext key="book" text="&#1082;&#1114;&#1080;&#1075;&#1072;"/>
+  <l:gentext key="CAUTION" text="&#1059;&#1055;&#1054;&#1047;&#1054;&#1056;&#1045;&#1034;&#1045;"/>
+  <l:gentext key="Caution" text="&#1059;&#1087;&#1086;&#1079;&#1086;&#1088;&#1077;&#1114;&#1077;"/>
+  <l:gentext key="caution" text="&#1091;&#1087;&#1086;&#1079;&#1086;&#1088;&#1077;&#1114;&#1077;"/>
+  <l:gentext key="Chapter" text="&#1055;&#1086;&#1075;&#1083;&#1072;&#1074;&#1113;&#1077;"/>
+  <l:gentext key="chapter" text="&#1087;&#1086;&#1075;&#1083;&#1072;&#1074;&#1113;&#1077;"/>
+  <l:gentext key="Colophon" text="Colophon" lang="en"/>
+  <l:gentext key="colophon" text="Colophon" lang="en"/>
+  <l:gentext key="Copyright" text="Copyright" lang="en"/>
+  <l:gentext key="copyright" text="Copyright" lang="en"/>
+  <l:gentext key="Dedication" text="&#1055;&#1086;&#1089;&#1074;&#1077;&#1090;&#1072;"/>
+  <l:gentext key="dedication" text="&#1087;&#1086;&#1089;&#1074;&#1077;&#1090;&#1072;"/>
+  <l:gentext key="Edition" text="&#1048;&#1079;&#1076;&#1072;&#1114;&#1077;"/>
+  <l:gentext key="edition" text="&#1080;&#1079;&#1076;&#1072;&#1114;&#1077;"/>
+  <l:gentext key="Equation" text="&#1032;&#1077;&#1076;&#1085;&#1072;&#1095;&#1080;&#1085;&#1072;"/>
+  <l:gentext key="equation" text="&#1112;&#1077;&#1076;&#1085;&#1072;&#1095;&#1080;&#1085;&#1072;"/>
+  <l:gentext key="Example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;"/>
+  <l:gentext key="example" text="&#1087;&#1088;&#1080;&#1084;&#1077;&#1088;"/>
+  <l:gentext key="Figure" text="&#1060;&#1080;&#1075;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="figure" text="&#1092;&#1080;&#1075;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="Glossary" text="&#1056;&#1077;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="glossary" text="&#1088;&#1077;&#1095;&#1085;&#1080;&#1082;"/>
+  <l:gentext key="GlossSee" text="&#1042;&#1080;&#1076;&#1080;"/>
+  <l:gentext key="glosssee" text="&#1074;&#1080;&#1076;&#1080;"/>
+  <l:gentext key="GlossSeeAlso" text="&#1042;&#1080;&#1076;&#1080;  &#1090;&#1072;&#1082;&#1086;&#1106;&#1077;"/>
+  <l:gentext key="glossseealso" text="&#1074;&#1080;&#1076;&#1080;  &#1090;&#1072;&#1082;&#1086;&#1106;&#1077;"/>
+  <l:gentext key="IMPORTANT" text="&#1042;&#1040;&#1046;&#1053;&#1054;"/>
+  <l:gentext key="important" text="&#1074;&#1072;&#1078;&#1085;&#1086;"/>
+  <l:gentext key="Important" text="&#1042;&#1072;&#1078;&#1085;&#1086;"/>
+  <l:gentext key="Index" text="&#1048;&#1085;&#1076;&#1077;&#1082;&#1089;"/>
+  <l:gentext key="index" text="&#1080;&#1085;&#1076;&#1077;&#1082;&#1089;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Legal Notice" lang="en"/>
+  <l:gentext key="legalnotice" text="Legal Notice" lang="en"/>
+  <l:gentext key="MsgAud" text="&#1055;&#1091;&#1073;&#1083;&#1080;&#1082;&#1072;"/>
+  <l:gentext key="msgaud" text="&#1087;&#1091;&#1073;&#1083;&#1080;&#1082;&#1072;"/>
+  <l:gentext key="MsgLevel" text="&#1053;&#1080;&#1074;&#1086;"/>
+  <l:gentext key="msglevel" text="&#1085;&#1080;&#1074;&#1086;"/>
+  <l:gentext key="MsgOrig" text="&#1048;&#1079;&#1074;&#1086;&#1088;"/>
+  <l:gentext key="msgorig" text="&#1080;&#1079;&#1074;&#1086;&#1088;"/>
+  <l:gentext key="NOTE" text="&#1055;&#1056;&#1048;&#1052;&#1045;&#1044;&#1041;&#1040;"/>
+  <l:gentext key="Note" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1076;&#1073;&#1072;"/>
+  <l:gentext key="note" text="&#1087;&#1088;&#1080;&#1084;&#1077;&#1076;&#1073;&#1072;"/>
+  <l:gentext key="Part" text="&#1044;&#1077;&#1086;"/>
+  <l:gentext key="part" text="&#1076;&#1077;&#1086;"/>
+  <l:gentext key="Preface" text="&#1055;&#1088;&#1077;&#1076;&#1075;&#1086;&#1074;&#1086;&#1088;"/>
+  <l:gentext key="preface" text="&#1087;&#1088;&#1077;&#1076;&#1075;&#1086;&#1074;&#1086;&#1088;"/>
+  <l:gentext key="Procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="procedure" text="&#1087;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="ProductionSet" text="Production" lang="en"/>
+  <l:gentext key="PubDate" text="&#1044;&#1072;&#1090;&#1091;&#1084;  &#1080;&#1079;&#1076;&#1072;&#1074;&#1072;&#1114;&#1072;"/>
+  <l:gentext key="pubdate" text="&#1076;&#1072;&#1090;&#1091;&#1084;  &#1080;&#1079;&#1076;&#1072;&#1074;&#1072;&#1114;&#1072;"/>
+  <l:gentext key="Published" text="&#1048;&#1079;&#1076;&#1072;&#1085;&#1086;"/>
+  <l:gentext key="published" text="&#1080;&#1079;&#1076;&#1072;&#1085;&#1086;"/>
+  <l:gentext key="Qandadiv" text="&#1055; &#1080; &#1054;"/>
+  <l:gentext key="qandadiv" text="&#1087; &#1080; &#1086;"/>
+  <l:gentext key="Question" text="&#1055;:"/>
+  <l:gentext key="question" text="&#1087;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#1056;&#1077;&#1092;&#1077;&#1088;&#1077;&#1085;&#1094;&#1072;"/>
+  <l:gentext key="reference" text="&#1088;&#1077;&#1092;&#1077;&#1088;&#1077;&#1085;&#1094;&#1072;"/>
+  <l:gentext key="RefName" text="&#1048;&#1084;&#1077;"/>
+  <l:gentext key="refname" text="&#1080;&#1084;&#1077;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#1050;&#1088;&#1072;&#1090;&#1072;&#1082;  &#1089;&#1072;&#1076;&#1088;&#1078;&#1072;&#1112;"/>
+  <l:gentext key="refsynopsisdiv" text="&#1082;&#1088;&#1072;&#1090;&#1072;&#1082;  &#1089;&#1072;&#1076;&#1088;&#1078;&#1072;&#1112;"/>
+  <l:gentext key="RevHistory" text="&#1048;&#1089;&#1090;&#1086;&#1088;&#1080;&#1112;&#1072;  &#1088;&#1077;&#1074;&#1080;&#1079;&#1080;&#1112;&#1072;"/>
+  <l:gentext key="revhistory" text="&#1080;&#1089;&#1090;&#1086;&#1088;&#1080;&#1112;&#1072;  &#1088;&#1077;&#1074;&#1080;&#1079;&#1080;&#1112;&#1072;"/>
+  <l:gentext key="revision" text="&#1088;&#1077;&#1074;&#1080;&#1079;&#1080;&#1112;&#1072;"/>
+  <l:gentext key="Revision" text="&#1056;&#1077;&#1074;&#1080;&#1079;&#1080;&#1112;&#1072;"/>
+  <l:gentext key="sect1" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;"/>
+  <l:gentext key="sect2" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;"/>
+  <l:gentext key="sect3" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;"/>
+  <l:gentext key="sect4" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;"/>
+  <l:gentext key="sect5" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;"/>
+  <l:gentext key="section" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;"/>
+  <l:gentext key="Section" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;"/>
+  <l:gentext key="see" text="&#1074;&#1080;&#1076;&#1080;"/>
+  <l:gentext key="See" text="&#1042;&#1080;&#1076;&#1080;"/>
+  <l:gentext key="seealso" text="&#1074;&#1080;&#1076;&#1080;  &#1090;&#1072;&#1082;&#1086;&#1106;&#1077;"/>
+  <l:gentext key="Seealso" text="&#1042;&#1080;&#1076;&#1080;  &#1090;&#1072;&#1082;&#1086;&#1106;&#1077;"/>
+  <l:gentext key="SeeAlso" text="&#1042;&#1080;&#1076;&#1080;  &#1090;&#1072;&#1082;&#1086;&#1106;&#1077;"/>
+  <l:gentext key="set" text="&#1089;&#1082;&#1091;&#1087;"/>
+  <l:gentext key="Set" text="&#1057;&#1082;&#1091;&#1087;"/>
+  <l:gentext key="setindex" text="&#1048;&#1085;&#1076;&#1077;&#1082;&#1089;  &#1089;&#1082;&#1091;&#1087;&#1072;"/>
+  <l:gentext key="SetIndex" text="&#1048;&#1085;&#1076;&#1077;&#1082;&#1089;  &#1089;&#1082;&#1091;&#1087;&#1072;"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="&#1087;&#1086;&#1074;&#1088;&#1096;  &#1087;&#1086;&#1089;&#1090;&#1088;&#1072;&#1085;&#1094;&#1077;"/>
+  <l:gentext key="step" text="&#1082;&#1086;&#1088;&#1072;&#1082;"/>
+  <l:gentext key="Step" text="&#1050;&#1086;&#1088;&#1072;&#1082;"/>
+  <l:gentext key="Table" text="&#1058;&#1072;&#1073;&#1077;&#1083;&#1072;"/>
+  <l:gentext key="table" text="&#1090;&#1072;&#1073;&#1077;&#1083;&#1072;"/>
+  <l:gentext key="tip" text="&#1089;&#1072;&#1074;&#1077;&#1090;"/>
+  <l:gentext key="TIP" text="&#1057;&#1040;&#1042;&#1045;&#1058;"/>
+  <l:gentext key="Tip" text="&#1057;&#1072;&#1074;&#1077;&#1090;"/>
+  <l:gentext key="Warning" text="&#1059;&#1087;&#1086;&#1079;&#1086;&#1088;&#1077;&#1114;&#1077;"/>
+  <l:gentext key="warning" text="&#1091;&#1087;&#1086;&#1079;&#1086;&#1088;&#1077;&#1114;&#1077;"/>
+  <l:gentext key="WARNING" text="&#1059;&#1055;&#1054;&#1047;&#1054;&#1056;&#1045;&#1034;&#1045;"/>
+  <l:gentext key="and" text="&#1080;"/>
+  <l:gentext key="by" text="&#1086;&#1076;"/>
+  <l:gentext key="called" text="&#1087;&#1086;&#1076;  &#1080;&#1084;&#1077;&#1085;&#1086;&#1084;"/>
+  <l:gentext key="Edited" text="&#1059;&#1088;&#1077;&#1106;&#1077;&#1085;&#1086;"/>
+  <l:gentext key="edited" text="&#1091;&#1088;&#1077;&#1106;&#1077;&#1085;&#1086;"/>
+  <l:gentext key="Editedby" text="&#1059;&#1088;&#1077;&#1076;&#1080;&#1086;(&#1083;&#1072;)"/>
+  <l:gentext key="editedby" text="&#1059;&#1088;&#1077;&#1076;&#1080;&#1086;(&#1083;&#1072;)"/>
+  <l:gentext key="in" text="&#1091;"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="&#1085;&#1077;&#1087;&#1086;&#1089;&#1090;&#1086;&#1112;&#1077;&#1115;&#1080;  &#1077;&#1083;&#1077;&#1084;&#1077;&#1085;&#1090;"/>
+  <l:gentext key="notes" text="&#1087;&#1088;&#1080;&#1084;&#1077;&#1076;&#1073;&#1077;"/>
+  <l:gentext key="Notes" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1076;&#1073;&#1077;"/>
+  <l:gentext key="Pgs" text="&#1057;&#1090;&#1088;."/>
+  <l:gentext key="pgs" text="&#1089;&#1090;&#1088;."/>
+  <l:gentext key="Revisedby" text="&#1055;&#1088;&#1077;&#1075;&#1083;&#1077;&#1076;&#1072;&#1086;(&#1083;&#1072;):  "/>
+  <l:gentext key="revisedby" text="&#1087;&#1088;&#1077;&#1075;&#1083;&#1077;&#1076;&#1072;&#1086;(&#1083;&#1072;):  "/>
+  <l:gentext key="TableNotes" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1076;&#1073;&#1077;"/>
+  <l:gentext key="tablenotes" text="&#1087;&#1088;&#1080;&#1084;&#1077;&#1076;&#1073;&#1077;"/>
+  <l:gentext key="TableofContents" text="&#1057;&#1072;&#1076;&#1088;&#1078;&#1072;&#1112;"/>
+  <l:gentext key="tableofcontents" text="&#1089;&#1072;&#1076;&#1088;&#1078;&#1072;&#1112;"/>
+  <l:gentext key="the" text=""/>
+  <l:gentext key="unexpectedelementname" text="&#1085;&#1077;&#1086;&#1095;&#1077;&#1082;&#1080;&#1074;&#1072;&#1085;&#1086;  &#1080;&#1084;&#1077;  &#1077;&#1083;&#1077;&#1084;&#1077;&#1085;&#1090;&#1072;"/>
+  <l:gentext key="unsupported" text="&#1085;&#1080;&#1112;&#1077;  &#1087;&#1086;&#1076;&#1088;&#1078;&#1072;&#1085;&#1086;"/>
+  <l:gentext key="xrefto" text="&#1091;&#1085;&#1072;&#1082;&#1088;&#1089;&#1085;&#1072;  &#1088;&#1077;&#1092;&#1077;&#1088;&#1077;&#1085;&#1094;&#1072;  &#1085;&#1072;"/>
+  <l:gentext key="listofequations" text="&#1083;&#1080;&#1089;&#1090;&#1072;  &#1112;&#1077;&#1076;&#1085;&#1072;&#1095;&#1080;&#1085;&#1072;"/>
+  <l:gentext key="ListofEquations" text="&#1051;&#1080;&#1089;&#1090;&#1072;  &#1112;&#1077;&#1076;&#1085;&#1072;&#1095;&#1080;&#1085;&#1072;"/>
+  <l:gentext key="ListofExamples" text="&#1051;&#1080;&#1089;&#1090;&#1072;  &#1087;&#1088;&#1080;&#1084;&#1077;&#1088;&#1072;"/>
+  <l:gentext key="listofexamples" text="&#1083;&#1080;&#1089;&#1090;&#1072;  &#1087;&#1088;&#1080;&#1084;&#1077;&#1088;&#1072;"/>
+  <l:gentext key="ListofFigures" text="&#1051;&#1080;&#1089;&#1090;&#1072;  &#1092;&#1080;&#1075;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="listoffigures" text="&#1083;&#1080;&#1089;&#1090;&#1072;  &#1092;&#1080;&#1075;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="ListofProcedures" text="&#1051;&#1080;&#1089;&#1090;&#1072;  &#1087;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="listofprocedures" text="&#1083;&#1080;&#1089;&#1090;&#1072;  &#1087;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="listoftables" text="&#1083;&#1080;&#1089;&#1090;&#1072;  &#1090;&#1072;&#1073;&#1077;&#1083;&#1072;"/>
+  <l:gentext key="ListofTables" text="&#1051;&#1080;&#1089;&#1090;&#1072;  &#1090;&#1072;&#1073;&#1077;&#1083;&#1072;"/>
+  <l:gentext key="ListofUnknown" text="&#1051;&#1080;&#1089;&#1090;&#1072;  &#1085;&#1077;&#1087;&#1086;&#1079;&#1085;&#1072;&#1090;&#1080;&#1093;"/>
+  <l:gentext key="listofunknown" text="&#1083;&#1080;&#1089;&#1090;&#1072;  &#1085;&#1077;&#1087;&#1086;&#1079;&#1085;&#1072;&#1090;&#1080;&#1093;"/>
+  <l:gentext key="nav-home" text="&#1055;&#1086;&#1095;&#1077;&#1090;&#1072;&#1082;"/>
+  <l:gentext key="nav-next" text="&#1057;&#1083;&#1077;&#1076;&#1077;&#1115;&#1077;"/>
+  <l:gentext key="nav-next-sibling" text="&#1041;&#1088;&#1079;&#1086;  &#1085;&#1072;&#1087;&#1088;&#1077;&#1076;"/>
+  <l:gentext key="nav-prev" text="&#1055;&#1088;&#1077;&#1090;&#1093;&#1086;&#1076;&#1085;&#1086;"/>
+  <l:gentext key="nav-prev-sibling" text="&#1041;&#1088;&#1079;&#1086;  &#1085;&#1072;&#1079;&#1072;&#1076;"/>
+  <l:gentext key="nav-up" text="&#1042;&#1088;&#1093;"/>
+  <l:gentext key="nav-toc" text="&#1057;&#1072;&#1076;&#1088;."/>
+  <l:gentext key="Draft" text="&#1053;&#1072;&#1094;&#1088;&#1090;"/>
+  <l:gentext key="above" text="&#1080;&#1079;&#1085;&#1072;&#1076;"/>
+  <l:gentext key="below" text="&#1080;&#1089;&#1087;&#1086;&#1076;"/>
+  <l:gentext key="sectioncalled" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076;  &#1080;&#1084;&#1077;&#1085;&#1086;&#1084;"/>
+  <l:gentext key="index symbols" text="&#1057;&#1080;&#1084;&#1073;&#1086;&#1083;&#1080;"/>
+  <l:gentext key="lowercase.alpha" text="&#1072;&#1073;&#1074;&#1075;&#1076;&#1106;&#1077;&#1078;&#1079;&#1080;&#1112;&#1082;&#1083;&#1113;&#1084;&#1085;&#1114;&#1086;&#1087;&#1088;&#1089;&#1090;&#1115;&#1091;&#1092;&#1093;&#1094;&#1095;&#1119;&#1096;"/>
+  <l:gentext key="uppercase.alpha" text="&#1040;&#1041;&#1042;&#1043;&#1044;&#1026;&#1045;&#1046;&#1047;&#1048;&#1032;&#1050;&#1051;&#1033;&#1052;&#1053;&#1034;&#1054;&#1055;&#1056;&#1057;&#1058;&#1035;&#1059;&#1060;&#1061;&#1062;&#1063;&#1039;&#1064;"/>
+  <l:gentext key="hyphenation-character" text="-"/>
+  <l:gentext key="hyphenation-push-character-count" text="2"/>
+  <l:gentext key="hyphenation-remain-character-count" text="2"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sr.xml -->
+  <l:dingbat key="startquote" text="&#8222;"/>
+  <l:dingbat key="endquote" text="&#8220;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="singlestartquote" text="&#8216;"/>
+  <l:dingbat key="singleendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="&#1080;&#1084;&#1077;-&#1087;&#1088;&#1077;&#1079;&#1080;&#1084;&#1077;"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1072;&#1082;&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#1055;&#1086;&#1075;&#1083;&#1072;&#1074;&#1113;&#1077;&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#1032;&#1077;&#1076;&#1085;&#1072;&#1095;&#1080;&#1085;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="&#1060;&#1080;&#1075;&#1091;&#1088;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#1044;&#1077;&#1086;&#160;%n.&#160;%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n&quot; &#10;lang=&quot;en"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1077;&#1083;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="task" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1072;&#1082;&#160;%n.&#160;%t"/>
+    <l:template name="article/appendix" text="%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="&#1055;&#1086;&#1075;&#1083;&#1072;&#1074;&#1113;&#1077;&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#1054;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#1055;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#1055;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="page" text="(&#1089;&#1090;&#1088;&#1072;&#1085;&#1072; %p)"/>
+    <l:template name="pageabbrev" text="(&#1089;&#1090;&#1088;. %p)"/>
+    <l:template name="Page" text="&#1057;&#1090;&#1088;&#1072;&#1085;&#1072; %p"/>
+    <l:template name="bridgehead" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="refsection" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="refsect1" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="refsect2" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="refsect3" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="sect1" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="sect2" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="sect3" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="sect4" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="sect5" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="section" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="simplesect" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#1054;:&#160;%n"/>
+    <l:template name="appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1072;&#1082;&#160;%n"/>
+    <l:template name="bridgehead" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n"/>
+    <l:template name="chapter" text="&#1055;&#1086;&#1075;&#1083;&#1072;&#1074;&#1113;&#1077;&#160;%n"/>
+    <l:template name="equation" text="&#1032;&#1077;&#1076;&#1085;&#1072;&#1095;&#1080;&#1085;&#1072;&#160;%n"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;&#160;%n"/>
+    <l:template name="figure" text="&#1060;&#1080;&#1075;&#1091;&#1088;&#1072;&#160;%n"/>
+    <l:template name="part" text="&#1044;&#1077;&#1086;&#160;%n"/>
+    <l:template name="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n&quot; lang=&quot;en"/>
+    <l:template name="qandadiv" text="&#1055; &#1080; &#1054;&#160;%n"/>
+    <l:template name="qandaentry" text="&#1055;:&#160;%n"/>
+    <l:template name="question" text="&#1055;:&#160;%n"/>
+    <l:template name="sect1" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n"/>
+    <l:template name="sect2" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n"/>
+    <l:template name="sect3" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n"/>
+    <l:template name="sect4" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n"/>
+    <l:template name="sect5" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n"/>
+    <l:template name="section" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1077;&#1083;&#1072;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1072;&#1082;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="chapter" text="&#1055;&#1086;&#1075;&#1083;&#1072;&#1074;&#1113;&#1077;&#160;%n, &#10;%t"/>
+    <l:template name="equation" text="&#1032;&#1077;&#1076;&#1085;&#1072;&#1095;&#1080;&#1085;&#1072;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1084;&#1077;&#1088;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="figure" text="&#1060;&#1080;&#1075;&#1091;&#1088;&#1072;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="part" text="&#1044;&#1077;&#1086;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#10;&#8222;%t&#8220;&quot; lang=&quot;en"/>
+    <l:template name="qandadiv" text="&#1055; &#1080; &#1054;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="refsect1" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="refsect2" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="refsect3" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="refsection" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="sect1" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="sect2" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="sect3" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="sect4" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="sect5" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="section" text="&#1054;&#1076;&#1077;&#1113;&#1072;&#1082;&#160;%n, &#10;&#8222;%t&#8220;"/>
+    <l:template name="simplesect" text="&#1086;&#1076;&#1077;&#1113;&#1072;&#1082; &#1087;&#1086;&#1076; &#10;&#1080;&#1084;&#1077;&#1085;&#1086;&#1084; &#8222;%t&#8220;"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1077;&#1083;&#1072;&#160;%n, &#10;&#8222;%t&#8220;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#1080; "/>
+    <l:template name="seplast" text=", &#1080; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#1042;&#1080;&#1076;&#1080; "/>
+    <l:template name="seealso" text="&#1042;&#1080;&#1076;&#1080; &#10;&#1090;&#1072;&#1082;&#1086;&#1106;&#1077; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#1055;&#1091;&#1073;&#1083;&#1080;&#1082;&#1072;: "/>
+    <l:template name="MsgLevel" text="&#1053;&#1080;&#1074;&#1086;: "/>
+    <l:template name="MsgOrig" text="&#1048;&#1079;&#1074;&#1086;&#1088;: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d.m.Y."/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="&#1112;&#1072;&#1085;&#1091;&#1072;&#1088;"/>
+    <l:template name="February" text="&#1092;&#1077;&#1073;&#1088;&#1091;&#1072;&#1088;"/>
+    <l:template name="March" text="&#1084;&#1072;&#1088;&#1090;"/>
+    <l:template name="April" text="&#1072;&#1087;&#1088;&#1080;&#1083;"/>
+    <l:template name="May" text="&#1084;&#1072;&#1112;"/>
+    <l:template name="June" text="&#1112;&#1091;&#1085;"/>
+    <l:template name="July" text="&#1112;&#1091;&#1083;"/>
+    <l:template name="August" text="&#1072;&#1074;&#1075;&#1091;&#1089;&#1090;"/>
+    <l:template name="September" text="&#1089;&#1077;&#1087;&#1090;&#1077;&#1084;&#1073;&#1072;&#1088;"/>
+    <l:template name="October" text="&#1086;&#1082;&#1090;&#1086;&#1073;&#1072;&#1088;"/>
+    <l:template name="November" text="&#1085;&#1086;&#1074;&#1077;&#1084;&#1073;&#1072;&#1088;"/>
+    <l:template name="December" text="&#1076;&#1077;&#1094;&#1077;&#1084;&#1073;&#1072;&#1088;"/>
+    <l:template name="Monday" text="&#1087;&#1086;&#1085;&#1077;&#1076;&#1077;&#1113;&#1072;&#1082;"/>
+    <l:template name="Tuesday" text="&#1091;&#1090;&#1086;&#1088;&#1072;&#1082;"/>
+    <l:template name="Wednesday" text="&#1089;&#1088;&#1077;&#1076;&#1072;"/>
+    <l:template name="Thursday" text="&#1095;&#1077;&#1090;&#1074;&#1088;&#1090;&#1072;&#1082;"/>
+    <l:template name="Friday" text="&#1087;&#1077;&#1090;&#1072;&#1082;"/>
+    <l:template name="Saturday" text="&#1089;&#1091;&#1073;&#1086;&#1090;&#1072;"/>
+    <l:template name="Sunday" text="&#1085;&#1077;&#1076;&#1077;&#1113;&#1072;"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="&#1112;&#1072;&#1085;"/>
+    <l:template name="Feb" text="&#1092;&#1077;&#1073;"/>
+    <l:template name="Mar" text="&#1084;&#1072;&#1088;"/>
+    <l:template name="Apr" text="&#1072;&#1087;&#1088;"/>
+    <l:template name="May" text="&#1084;&#1072;&#1112;"/>
+    <l:template name="Jun" text="&#1112;&#1091;&#1085;"/>
+    <l:template name="Jul" text="&#1112;&#1091;&#1083;"/>
+    <l:template name="Aug" text="&#1072;&#1074;&#1075;"/>
+    <l:template name="Sep" text="&#1089;&#1077;&#1087;"/>
+    <l:template name="Oct" text="&#1086;&#1082;&#1090;"/>
+    <l:template name="Nov" text="&#1085;&#1086;&#1074;"/>
+    <l:template name="Dec" text="&#1076;&#1077;&#1094;"/>
+    <l:template name="Mon" text="&#1087;&#1086;&#1085;"/>
+    <l:template name="Tue" text="&#1091;&#1090;&#1086;"/>
+    <l:template name="Wed" text="&#1089;&#1088;&#1077;"/>
+    <l:template name="Thu" text="&#1095;&#1077;&#1090;"/>
+    <l:template name="Fri" text="&#1087;&#1077;&#1090;"/>
+    <l:template name="Sat" text="&#1089;&#1091;&#1073;"/>
+    <l:template name="Sun" text="&#1085;&#1077;&#1076;"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x081a Serbian (Cyrillic)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/sr_Latn.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/sr_Latn.xml
new file mode 100644
index 00000000000..9afa066ec71
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/sr_Latn.xml
@@ -0,0 +1,443 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="sr_Latn" english-language-name="Serbian in Latin script">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sr_Latn.xml -->
+  <l:gentext key="Abstract" text="Pregled"/>
+  <l:gentext key="abstract" text="Pregled"/>
+  <l:gentext key="Answer" text="O:"/>
+  <l:gentext key="answer" text="O:"/>
+  <l:gentext key="Appendix" text="Dodatak"/>
+  <l:gentext key="appendix" text="dodatak"/>
+  <l:gentext key="Article" text="&#268;lanak"/>
+  <l:gentext key="article" text="&#268;lanak"/>
+  <l:gentext key="Bibliography" text="Literatura"/>
+  <l:gentext key="bibliography" text="Literatura"/>
+  <l:gentext key="Book" text="Knjiga"/>
+  <l:gentext key="book" text="Knjiga"/>
+  <l:gentext key="CAUTION" text="UPOZORENJE"/>
+  <l:gentext key="Caution" text="Upozorenje"/>
+  <l:gentext key="caution" text="Upozorenje"/>
+  <l:gentext key="Chapter" text="Poglavlje"/>
+  <l:gentext key="chapter" text="poglavlje"/>
+  <l:gentext key="Colophon" text="Kolofon"/>
+  <l:gentext key="colophon" text="Kolofon"/>
+  <l:gentext key="Copyright" text="Pravna za&#353;tita"/>
+  <l:gentext key="copyright" text="Pravna za&#353;tita"/>
+  <l:gentext key="Dedication" text="Posveta"/>
+  <l:gentext key="dedication" text="Posveta"/>
+  <l:gentext key="Edition" text="Izdanje"/>
+  <l:gentext key="edition" text="Izdanje"/>
+  <l:gentext key="Equation" text="Jedna&#269;ina"/>
+  <l:gentext key="equation" text="Jedna&#269;ina"/>
+  <l:gentext key="Example" text="Primer"/>
+  <l:gentext key="example" text="Primer"/>
+  <l:gentext key="Figure" text="Slika"/>
+  <l:gentext key="figure" text="Slika"/>
+  <l:gentext key="Glossary" text="Re&#269;nik"/>
+  <l:gentext key="glossary" text="Re&#269;nik"/>
+  <l:gentext key="GlossSee" text="Vidi"/>
+  <l:gentext key="glosssee" text="Vidi"/>
+  <l:gentext key="GlossSeeAlso" text="Vidi tako&#273;e"/>
+  <l:gentext key="glossseealso" text="Vidi tako&#273;e"/>
+  <l:gentext key="IMPORTANT" text="VA&#381;NO"/>
+  <l:gentext key="Important" text="Va&#382;no"/>
+  <l:gentext key="important" text="Va&#382;no"/>
+  <l:gentext key="Index" text="Indeks"/>
+  <l:gentext key="index" text="Indeks"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Pravno obave&#353;tenje"/>
+  <l:gentext key="legalnotice" text="Pravno obave&#353;tenje"/>
+  <l:gentext key="MsgAud" text="MsgAud"/>
+  <l:gentext key="msgaud" text="MsgAud"/>
+  <l:gentext key="MsgLevel" text="Nivo"/>
+  <l:gentext key="msglevel" text="Nivo"/>
+  <l:gentext key="MsgOrig" text="Izvor"/>
+  <l:gentext key="msgorig" text="Izvor"/>
+  <l:gentext key="NOTE" text="PRIMEDBA"/>
+  <l:gentext key="Note" text="Primedba"/>
+  <l:gentext key="note" text="Primedba"/>
+  <l:gentext key="Part" text="Deo"/>
+  <l:gentext key="part" text="Deo"/>
+  <l:gentext key="Preface" text="Predgovor"/>
+  <l:gentext key="preface" text="Predgovor"/>
+  <l:gentext key="Procedure" text="Postupak"/>
+  <l:gentext key="procedure" text="Postupak"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="Izdato"/>
+  <l:gentext key="published" text="Izdato"/>
+  <l:gentext key="Question" text="P:"/>
+  <l:gentext key="question" text="P:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Referenca"/>
+  <l:gentext key="reference" text="Referenca"/>
+  <l:gentext key="RefName" text="Ime"/>
+  <l:gentext key="refname" text="Ime"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Sinopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Sinopsis"/>
+  <l:gentext key="RevHistory" text="Istorija revizija"/>
+  <l:gentext key="revhistory" text="Istorija revizija"/>
+  <l:gentext key="Revision" text="Revizija"/>
+  <l:gentext key="revision" text="Revizija"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="Odeljak"/>
+  <l:gentext key="section" text="sekcija"/>
+  <l:gentext key="See" text="vidi"/>
+  <l:gentext key="see" text="vidi"/>
+  <l:gentext key="SeeAlso" text="vidi tako&#273;e"/>
+  <l:gentext key="Seealso" text="Vidi tako&#273;e"/>
+  <l:gentext key="seealso" text="vidi tako&#273;e"/>
+  <l:gentext key="Set" text="Postavi"/>
+  <l:gentext key="set" text="Postavi"/>
+  <l:gentext key="SetIndex" text="Postavi indeks"/>
+  <l:gentext key="setindex" text="Postavi indeks"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="Step" text="Korak"/>
+  <l:gentext key="step" text="korak"/>
+  <l:gentext key="Table" text="Tabela"/>
+  <l:gentext key="table" text="Tabela"/>
+  <l:gentext key="TIP" text="SAVET"/>
+  <l:gentext key="Tip" text="Savet"/>
+  <l:gentext key="tip" text="Savet"/>
+  <l:gentext key="WARNING" text="UPOZORENJE"/>
+  <l:gentext key="Warning" text="Upozorenje"/>
+  <l:gentext key="warning" text="Upozorenje"/>
+  <l:gentext key="and" text="i"/>
+  <l:gentext key="by" text="od"/>
+  <l:gentext key="Edited" text="Ure&#273;eno"/>
+  <l:gentext key="edited" text="Ure&#273;eno"/>
+  <l:gentext key="Editedby" text="Ure&#273;eno od"/>
+  <l:gentext key="editedby" text="Ure&#273;eno od"/>
+  <l:gentext key="in" text="u"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="nepostoje&#263;i element"/>
+  <l:gentext key="notes" text="Notes"/>
+  <l:gentext key="Notes" text="Notes"/>
+  <l:gentext key="Pgs" text="Str."/>
+  <l:gentext key="pgs" text="Str."/>
+  <l:gentext key="Revisedby" text="Revised by: "/>
+  <l:gentext key="revisedby" text="Revised by: "/>
+  <l:gentext key="TableNotes" text="Notes"/>
+  <l:gentext key="tablenotes" text="Notes"/>
+  <l:gentext key="TableofContents" text="Sadr&#382;aj"/>
+  <l:gentext key="tableofcontents" text="Sadr&#382;aj"/>
+  <l:gentext key="unexpectedelementname" text="Neo&#269;ekivano ime elementa"/>
+  <l:gentext key="unsupported" text="nepodr&#382;ano"/>
+  <l:gentext key="xrefto" text="xref na"/>
+  <l:gentext key="listofequations" text="Spisak jedna&#269;ina"/>
+  <l:gentext key="ListofEquations" text="Spisak jedna&#269;ina"/>
+  <l:gentext key="ListofExamples" text="Spisak primera"/>
+  <l:gentext key="listofexamples" text="Spisak primera"/>
+  <l:gentext key="ListofFigures" text="Spisak slika"/>
+  <l:gentext key="listoffigures" text="Spisak slika"/>
+  <l:gentext key="listoftables" text="Spisak tabela"/>
+  <l:gentext key="ListofTables" text="Spisak tabela"/>
+  <l:gentext key="ListofUnknown" text="Spisak nepoznanica"/>
+  <l:gentext key="listofunknown" text="Spisak nepoznanica"/>
+  <l:gentext key="nav-home" text="Ku&#263;i"/>
+  <l:gentext key="nav-next" text="Napred"/>
+  <l:gentext key="nav-next-sibling" text="Brzo napred"/>
+  <l:gentext key="nav-prev" text="Nazad"/>
+  <l:gentext key="nav-prev-sibling" text="Brzo nazad"/>
+  <l:gentext key="nav-up" text="Gore"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sr_Latn.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Dodatak %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Poglavlje %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Jedna&#269;ina %n. %t"/>
+    <l:template name="example" text="Primer %n. %t"/>
+    <l:template name="figure" text="Slika %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Deo %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Postupak&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabela %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Dodatak %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Poglavlje %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="O:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="P:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="P:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="O:&#160;%n"/>
+    <l:template name="appendix" text="Dodatak&#160;%n"/>
+    <l:template name="bridgehead" text="Odeljak&#160;%n"/>
+    <l:template name="chapter" text="Poglavlje&#160;%n"/>
+    <l:template name="equation" text="Jedna&#269;ina&#160;%n"/>
+    <l:template name="example" text="Primer&#160;%n"/>
+    <l:template name="figure" text="Slika&#160;%n"/>
+    <l:template name="part" text="Deo&#160;%n"/>
+    <l:template name="procedure" text="Postupak&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="P:&#160;%n"/>
+    <l:template name="question" text="P:&#160;%n"/>
+    <l:template name="sect1" text="Odeljak&#160;%n"/>
+    <l:template name="sect2" text="Odeljak&#160;%n"/>
+    <l:template name="sect3" text="Odeljak&#160;%n"/>
+    <l:template name="sect4" text="Odeljak&#160;%n"/>
+    <l:template name="sect5" text="Odeljak&#160;%n"/>
+    <l:template name="section" text="Odeljak&#160;%n"/>
+    <l:template name="table" text="Tabela&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Dodatak&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Odeljak&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Poglavlje&#160;%n, %t"/>
+    <l:template name="equation" text="Jedna&#269;ina&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Primer&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Slika&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Deo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Postupak&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Odeljak&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Odeljak&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Odeljak&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Odeljak&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Odeljak&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Odeljak&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabela&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" i "/>
+    <l:template name="seplast" text=", i "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Vidi "/>
+    <l:template name="seealso" text="Vidi tako&#273;e "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="MsgAud: "/>
+    <l:template name="MsgLevel" text="Nivo: "/>
+    <l:template name="MsgOrig" text="Izvor: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x081a Serbian (Latin)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/subtitles.xsl b/docs-xml/xslt/db2latex-xsl/xsl/common/subtitles.xsl
new file mode 100644
index 00000000000..7126b009939
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/subtitles.xsl
@@ -0,0 +1,140 @@
+<?xml version='1.0'?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+                exclude-result-prefixes="doc"
+                version='1.0'>
+
+<!-- ********************************************************************
+     $Id: subtitles.xsl,v 1.2 2004/01/04 09:25:57 j-devenish Exp $
+     ********************************************************************
+
+     This file is part of the XSL DocBook Stylesheet distribution.
+
+     Copyright (C) 1999, 2000, 2001, 2002 Norman Walsh.
+     ******************************************************************** -->
+
+<!-- ==================================================================== -->
+
+<!-- subtitle markup -->
+
+<doc:mode mode="subtitle.markup" xmlns="">
+<refpurpose>Provides access to element subtitles</refpurpose>
+<refdescription>
+<para>Processing an element in the
+<literal role="mode">subtitle.markup</literal> mode produces the
+subtitle of the element.
+</para>
+</refdescription>
+</doc:mode>
+
+<xsl:template match="*" mode="subtitle.markup">
+  <xsl:message>
+    <xsl:text>Request for subtitle of unexpected element: </xsl:text>
+    <xsl:value-of select="name(.)"/>
+  </xsl:message>
+  <xsl:text>???SUBTITLE???</xsl:text>
+</xsl:template>
+
+<xsl:template match="subtitle" mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="set" mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates select="(setinfo/subtitle|subtitle)[1]"
+                       mode="subtitle.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="book" mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates select="(bookinfo/subtitle|subtitle)[1]"
+                       mode="subtitle.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="part" mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates select="(partinfo/subtitle
+                                |docinfo/subtitle
+                                |subtitle)[1]"
+                       mode="subtitle.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="preface|chapter|appendix" mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates select="(docinfo/subtitle
+                                |prefaceinfo/subtitle
+                                |chapterinfo/subtitle
+                                |appendixinfo/subtitle
+                                |subtitle)[1]"
+                       mode="subtitle.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="article" mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates select="(artheader/subtitle
+                                |articleinfo/subtitle
+                                |subtitle)[1]"
+                       mode="subtitle.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="dedication|colophon" mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates select="subtitle"
+                       mode="subtitle.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="reference" mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates select="(referenceinfo/subtitle
+                                |docinfo/subtitle
+                                |subtitle)[1]"
+                       mode="subtitle.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="refentry" mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates select="(refentryinfo/subtitle
+                                |docinfo/subtitle)[1]"
+                       mode="subtitle.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="section
+                     |sect1|sect2|sect3|sect4|sect5
+                     |refsect1|refsect2|refsect3
+                     |simplesect"
+              mode="subtitle.markup">
+  <xsl:param name="allow-anchors" select="'0'"/>
+  <xsl:apply-templates select="(sectioninfo/subtitle
+                                |sect1info/subtitle
+                                |sect2info/subtitle
+                                |sect3info/subtitle
+                                |sect4info/subtitle
+                                |sect5info/subtitle
+                                |refsect1info/subtitle
+                                |refsect2info/subtitle
+                                |refsect3info/subtitle
+                                |subtitle)[1]"
+                       mode="subtitle.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/sv.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/sv.xml
new file mode 100644
index 00000000000..6101b453a5c
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/sv.xml
@@ -0,0 +1,487 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="sv" english-language-name="Swedish">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sv.xml -->
+  <l:gentext key="Abstract" text="Sammanfattning"/>
+  <l:gentext key="abstract" text="Sammanfattning"/>
+  <l:gentext key="Answer" text="A:"/>
+  <l:gentext key="answer" text="A:"/>
+  <l:gentext key="Appendix" text="Appendix"/>
+  <l:gentext key="appendix" text="appendix"/>
+  <l:gentext key="Article" text="Artikel"/>
+  <l:gentext key="article" text="Artikel"/>
+  <l:gentext key="Bibliography" text="Bibliografi"/>
+  <l:gentext key="bibliography" text="Bibliografi"/>
+  <l:gentext key="Book" text="Bok"/>
+  <l:gentext key="book" text="Bok"/>
+  <l:gentext key="CAUTION" text="OBSERVERA"/>
+  <l:gentext key="Caution" text="Observera"/>
+  <l:gentext key="caution" text="Observera"/>
+  <l:gentext key="Chapter" text="Kapitel"/>
+  <l:gentext key="chapter" text="kapitel"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="Copyright"/>
+  <l:gentext key="copyright" text="Copyright"/>
+  <l:gentext key="Dedication" text="Dedikation"/>
+  <l:gentext key="dedication" text="Dedikation"/>
+  <l:gentext key="Edition" text="Utg&#229;va"/>
+  <l:gentext key="edition" text="Utg&#229;va"/>
+  <l:gentext key="Equation" text="Ekvation"/>
+  <l:gentext key="equation" text="Ekvation"/>
+  <l:gentext key="Example" text="Exempel"/>
+  <l:gentext key="example" text="Exempel"/>
+  <l:gentext key="Figure" text="Figur"/>
+  <l:gentext key="figure" text="Figur"/>
+  <l:gentext key="Glossary" text="Gloslista"/>
+  <l:gentext key="glossary" text="Gloslista"/>
+  <l:gentext key="GlossSee" text="Se"/>
+  <l:gentext key="glosssee" text="Se"/>
+  <l:gentext key="GlossSeeAlso" text="Se &#196;ven"/>
+  <l:gentext key="glossseealso" text="Se &#196;ven"/>
+  <l:gentext key="IMPORTANT" text="VIKTIGT"/>
+  <l:gentext key="Important" text="Viktigt"/>
+  <l:gentext key="important" text="Viktigt"/>
+  <l:gentext key="Index" text="Index"/>
+  <l:gentext key="index" text="Index"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Legal Notice"/>
+  <l:gentext key="legalnotice" text="Legal Notice"/>
+  <l:gentext key="MsgAud" text="M&#229;lgrupp"/>
+  <l:gentext key="msgaud" text="M&#229;lgrupp"/>
+  <l:gentext key="MsgLevel" text="Niv&#229;"/>
+  <l:gentext key="msglevel" text="Niv&#229;"/>
+  <l:gentext key="MsgOrig" text="Ursprung"/>
+  <l:gentext key="msgorig" text="Ursprung"/>
+  <l:gentext key="NOTE" text="NOT"/>
+  <l:gentext key="Note" text="Not"/>
+  <l:gentext key="note" text="Not"/>
+  <l:gentext key="Part" text="Del"/>
+  <l:gentext key="part" text="Del"/>
+  <l:gentext key="Preface" text="F&#246;retal"/>
+  <l:gentext key="preface" text="F&#246;retal"/>
+  <l:gentext key="Procedure" text="Procedur"/>
+  <l:gentext key="procedure" text="Procedur"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="Publicerad"/>
+  <l:gentext key="published" text="Publicerad"/>
+  <l:gentext key="Question" text="Fr&#229;ga:"/>
+  <l:gentext key="question" text="Fr&#229;ga:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Referens"/>
+  <l:gentext key="reference" text="Referens"/>
+  <l:gentext key="RefName" text="Namn"/>
+  <l:gentext key="refname" text="Namn"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Revisionshistorik"/>
+  <l:gentext key="revhistory" text="Revisionshistorik"/>
+  <l:gentext key="Revision" text="Revision"/>
+  <l:gentext key="revision" text="Revision"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="Avsnitt"/>
+  <l:gentext key="section" text="avsnitt"/>
+  <l:gentext key="See" text="Se"/>
+  <l:gentext key="see" text="se"/>
+  <l:gentext key="SeeAlso" text="Se &#196;ven"/>
+  <l:gentext key="seealso" text="se &#228;ven"/>
+  <l:gentext key="Seealso" text="Se &#228;ven"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="SetIndex" text="Set Index"/>
+  <l:gentext key="setindex" text="Set Index"/>
+  <l:gentext key="Sidebar" text="Sidebar"/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="Step" text="Steg"/>
+  <l:gentext key="step" text="steg"/>
+  <l:gentext key="Table" text="Tabell"/>
+  <l:gentext key="table" text="Tabell"/>
+  <l:gentext key="TIP" text="TIPS"/>
+  <l:gentext key="Tip" text="Tips"/>
+  <l:gentext key="tip" text="Tips"/>
+  <l:gentext key="WARNING" text="VARNING"/>
+  <l:gentext key="Warning" text="Varning"/>
+  <l:gentext key="warning" text="Varning"/>
+  <l:gentext key="and" text="och"/>
+  <l:gentext key="by" text="av"/>
+  <l:gentext key="called" text="kallas"/>
+  <l:gentext key="Edited" text="Redigerad"/>
+  <l:gentext key="edited" text="Redigerad"/>
+  <l:gentext key="Editedby" text="Redigerad av"/>
+  <l:gentext key="editedby" text="Redigerad av"/>
+  <l:gentext key="in" text="i"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="icke-existerande element"/>
+  <l:gentext key="Notes" text="Noter"/>
+  <l:gentext key="notes" text="Noter"/>
+  <l:gentext key="Pgs" text="Sid."/>
+  <l:gentext key="pgs" text="Sid."/>
+  <l:gentext key="Revisedby" text="Reviderad av: "/>
+  <l:gentext key="revisedby" text="Reviderad av: "/>
+  <l:gentext key="TableNotes" text="Noter"/>
+  <l:gentext key="tablenotes" text="Noter"/>
+  <l:gentext key="TableofContents" text="Inneh&#229;llsf&#246;rteckning"/>
+  <l:gentext key="tableofcontents" text="Inneh&#229;llsf&#246;rteckning"/>
+  <l:gentext key="the" text=""/>
+  <l:gentext key="unexpectedelementname" text="Ov&#228;ntat elementnamn"/>
+  <l:gentext key="unsupported" text="unsupported"/>
+  <l:gentext key="xrefto" text="korsreferens till"/>
+  <l:gentext key="ListofEquations" text="Ekvationsf&#246;rteckning"/>
+  <l:gentext key="listofequations" text="Ekvationsf&#246;rteckning"/>
+  <l:gentext key="ListofExamples" text="Exempelf&#246;rteckning"/>
+  <l:gentext key="listofexamples" text="Exempelf&#246;rteckning"/>
+  <l:gentext key="ListofFigures" text="Figurf&#246;rteckning"/>
+  <l:gentext key="listoffigures" text="Figurf&#246;rteckning"/>
+  <l:gentext key="ListofTables" text="Tabellf&#246;rteckning"/>
+  <l:gentext key="listoftables" text="Tabellf&#246;rteckning"/>
+  <l:gentext key="ListofUnknown" text="F&#246;rteckning av ok&#228;nda"/>
+  <l:gentext key="listofunknown" text="F&#246;rteckning av ok&#228;nda"/>
+  <l:gentext key="nav-home" text="Hem"/>
+  <l:gentext key="nav-next" text="N&#228;sta"/>
+  <l:gentext key="nav-next-sibling" text="Snabbt fram&#229;t"/>
+  <l:gentext key="nav-prev" text="F&#246;reg&#229;ende"/>
+  <l:gentext key="nav-prev-sibling" text="Snabbt bak&#229;t"/>
+  <l:gentext key="nav-up" text="Upp"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/sv.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Appendix %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Kapitel %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Ekvation %n. %t"/>
+    <l:template name="example" text="Exempel %n. %t"/>
+    <l:template name="figure" text="Figur %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Del %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Procedur&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tabell %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Appendix %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="Kapitel %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Fr&#229;ga:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Fr&#229;ga:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="A:&#160;%n"/>
+    <l:template name="appendix" text="Appendix&#160;%n"/>
+    <l:template name="bridgehead" text="Avsnitt&#160;%n"/>
+    <l:template name="chapter" text="Kapitel&#160;%n"/>
+    <l:template name="equation" text="Ekvation&#160;%n"/>
+    <l:template name="example" text="Exempel&#160;%n"/>
+    <l:template name="figure" text="Figur&#160;%n"/>
+    <l:template name="part" text="Del&#160;%n"/>
+    <l:template name="procedure" text="Procedur&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="Fr&#229;ga:&#160;%n"/>
+    <l:template name="question" text="Fr&#229;ga:&#160;%n"/>
+    <l:template name="sect1" text="Avsnitt&#160;%n"/>
+    <l:template name="sect2" text="Avsnitt&#160;%n"/>
+    <l:template name="sect3" text="Avsnitt&#160;%n"/>
+    <l:template name="sect4" text="Avsnitt&#160;%n"/>
+    <l:template name="sect5" text="Avsnitt&#160;%n"/>
+    <l:template name="section" text="Avsnitt&#160;%n"/>
+    <l:template name="table" text="Tabell&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Appendix&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Avsnitt&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Kapitel&#160;%n, %t"/>
+    <l:template name="equation" text="Ekvation&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Exempel&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Figur&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Del&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Procedur&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Avsnitt&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Avsnitt&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Avsnitt&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Avsnitt&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Avsnitt&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Avsnitt&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tabell&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" och "/>
+    <l:template name="seplast" text=", och "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Se "/>
+    <l:template name="seealso" text="Se &#196;ven "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="M&#229;lgrupp: "/>
+    <l:template name="MsgLevel" text="Niv&#229;: "/>
+    <l:template name="MsgOrig" text="Ursprung: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d-m-Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="Januari"/>
+    <l:template name="February" text="Februari"/>
+    <l:template name="March" text="Mars"/>
+    <l:template name="April" text="April"/>
+    <l:template name="May" text="Maj"/>
+    <l:template name="June" text="Juni"/>
+    <l:template name="July" text="Juli"/>
+    <l:template name="August" text="Augusti"/>
+    <l:template name="September" text="September"/>
+    <l:template name="October" text="Oktober"/>
+    <l:template name="November" text="November"/>
+    <l:template name="December" text="December"/>
+    <l:template name="Monday" text="M&#229;ndag"/>
+    <l:template name="Tuesday" text="Tisdag"/>
+    <l:template name="Wednesday" text="Onsdag"/>
+    <l:template name="Thursday" text="Torsdag"/>
+    <l:template name="Friday" text="Fredag"/>
+    <l:template name="Saturday" text="L&#246;rdag"/>
+    <l:template name="Sunday" text="S&#246;ndag"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="Jan"/>
+    <l:template name="Feb" text="Feb"/>
+    <l:template name="Mar" text="Mar"/>
+    <l:template name="Apr" text="Apr"/>
+    <l:template name="May" text="Maj"/>
+    <l:template name="Jun" text="Jun"/>
+    <l:template name="Jul" text="Jul"/>
+    <l:template name="Aug" text="Aug"/>
+    <l:template name="Sep" text="Sep"/>
+    <l:template name="Oct" text="Okt"/>
+    <l:template name="Nov" text="Nov"/>
+    <l:template name="Dec" text="Dec"/>
+    <l:template name="Mon" text="Mon"/>
+    <l:template name="Tue" text="Tis"/>
+    <l:template name="Wed" text="Ons"/>
+    <l:template name="Thu" text="Tor"/>
+    <l:template name="Fri" text="Fre"/>
+    <l:template name="Sat" text="L&#246;r"/>
+    <l:template name="Sun" text="S&#246;n"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x041d Swedish"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/th.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/th.xml
new file mode 100644
index 00000000000..847d59e2032
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/th.xml
@@ -0,0 +1,444 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="th" english-language-name="Thai">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/th.xml -->
+  <l:gentext key="Abstract" text="&#3610;&#3607;&#3588;&#3633;&#3604;&#3618;&#3656;&#3629;"/>
+  <l:gentext key="abstract" text="&#3610;&#3607;&#3588;&#3633;&#3604;&#3618;&#3656;&#3629;"/>
+  <l:gentext key="Answer" text="&#3605;&#3629;&#3610;:"/>
+  <l:gentext key="answer" text="&#3605;&#3629;&#3610;:"/>
+  <l:gentext key="Appendix" text="&#3616;&#3634;&#3588;&#3612;&#3609;&#3623;&#3585;"/>
+  <l:gentext key="appendix" text="&#3616;&#3634;&#3588;&#3612;&#3609;&#3623;&#3585;"/>
+  <l:gentext key="Article" text="&#3610;&#3607;&#3588;&#3623;&#3634;&#3617;"/>
+  <l:gentext key="article" text="&#3610;&#3607;&#3588;&#3623;&#3634;&#3617;"/>
+  <l:gentext key="Bibliography" text="&#3610;&#3619;&#3619;&#3603;&#3634;&#3609;&#3640;&#3585;&#3619;&#3617;"/>
+  <l:gentext key="bibliography" text="&#3610;&#3619;&#3619;&#3603;&#3634;&#3609;&#3640;&#3585;&#3619;&#3617;"/>
+  <l:gentext key="Book" text="&#3627;&#3609;&#3633;&#3591;&#3626;&#3639;&#3629;"/>
+  <l:gentext key="book" text="&#3627;&#3609;&#3633;&#3591;&#3626;&#3639;&#3629;"/>
+  <l:gentext key="CAUTION" text="&#3588;&#3635;&#3648;&#3605;&#3639;&#3629;&#3609;"/>
+  <l:gentext key="Caution" text="&#3588;&#3635;&#3648;&#3605;&#3639;&#3629;&#3609;"/>
+  <l:gentext key="caution" text="&#3588;&#3635;&#3648;&#3605;&#3639;&#3629;&#3609;"/>
+  <l:gentext key="Chapter" text="&#3610;&#3607;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="chapter" text="&#3610;&#3607;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="Colophon" text="&#3648;&#3610;&#3639;&#3657;&#3629;&#3591;&#3627;&#3621;&#3633;&#3591;"/>
+  <l:gentext key="colophon" text="&#3648;&#3610;&#3639;&#3657;&#3629;&#3591;&#3627;&#3621;&#3633;&#3591;"/>
+  <l:gentext key="Copyright" text="&#3626;&#3591;&#3623;&#3609;&#3626;&#3636;&#3586;&#3626;&#3636;&#3607;&#3608;&#3636;&#3660;"/>
+  <l:gentext key="copyright" text="&#3626;&#3591;&#3623;&#3609;&#3626;&#3636;&#3586;&#3626;&#3636;&#3607;&#3608;&#3636;&#3660;"/>
+  <l:gentext key="Dedication" text="&#3588;&#3635;&#3629;&#3640;&#3607;&#3636;&#3624;"/>
+  <l:gentext key="dedication" text="&#3588;&#3635;&#3629;&#3640;&#3607;&#3636;&#3624;"/>
+  <l:gentext key="Edition" text="&#3593;&#3610;&#3633;&#3610;"/>
+  <l:gentext key="edition" text="&#3593;&#3610;&#3633;&#3610;"/>
+  <l:gentext key="Equation" text="&#3626;&#3617;&#3585;&#3634;&#3619;"/>
+  <l:gentext key="equation" text="&#3626;&#3617;&#3585;&#3634;&#3619;"/>
+  <l:gentext key="Example" text="&#3605;&#3633;&#3623;&#3629;&#3618;&#3656;&#3634;&#3591;"/>
+  <l:gentext key="example" text="&#3605;&#3633;&#3623;&#3629;&#3618;&#3656;&#3634;&#3591;"/>
+  <l:gentext key="Figure" text="&#3619;&#3641;&#3611;"/>
+  <l:gentext key="figure" text="&#3619;&#3641;&#3611;"/>
+  <l:gentext key="Glossary" text="&#3629;&#3616;&#3636;&#3607;&#3634;&#3609;&#3624;&#3633;&#3614;&#3607;&#3660;"/>
+  <l:gentext key="glossary" text="&#3629;&#3616;&#3636;&#3607;&#3634;&#3609;&#3624;&#3633;&#3614;&#3607;&#3660;"/>
+  <l:gentext key="GlossSee" text="&#3604;&#3641;"/>
+  <l:gentext key="glosssee" text="&#3604;&#3641;"/>
+  <l:gentext key="GlossSeeAlso" text="&#3604;&#3641;&#3648;&#3614;&#3636;&#3656;&#3617;&#3648;&#3605;&#3636;&#3617;"/>
+  <l:gentext key="glossseealso" text="&#3604;&#3641;&#3648;&#3614;&#3636;&#3656;&#3617;&#3648;&#3605;&#3636;&#3617;"/>
+  <l:gentext key="IMPORTANT" text="&#3586;&#3657;&#3629;&#3588;&#3623;&#3619;&#3592;&#3635;"/>
+  <l:gentext key="important" text="&#3586;&#3657;&#3629;&#3588;&#3623;&#3619;&#3592;&#3635;"/>
+  <l:gentext key="Important" text="&#3586;&#3657;&#3629;&#3588;&#3623;&#3619;&#3592;&#3635;"/>
+  <l:gentext key="Index" text="&#3604;&#3619;&#3619;&#3594;&#3609;&#3637;"/>
+  <l:gentext key="index" text="&#3604;&#3619;&#3619;&#3594;&#3609;&#3637;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="&#3586;&#3657;&#3629;&#3612;&#3641;&#3585;&#3614;&#3633;&#3609;&#3605;&#3634;&#3617;&#3585;&#3598;&#3627;&#3617;&#3634;&#3618;"/>
+  <l:gentext key="legalnotice" text="&#3586;&#3657;&#3629;&#3612;&#3641;&#3585;&#3614;&#3633;&#3609;&#3605;&#3634;&#3617;&#3585;&#3598;&#3627;&#3617;&#3634;&#3618;"/>
+  <l:gentext key="MsgAud" text="&#3612;&#3641;&#3657;&#3629;&#3656;&#3634;&#3609;"/>
+  <l:gentext key="msgaud" text="&#3612;&#3641;&#3657;&#3629;&#3656;&#3634;&#3609;"/>
+  <l:gentext key="MsgLevel" text="&#3619;&#3632;&#3604;&#3633;&#3610;"/>
+  <l:gentext key="msglevel" text="&#3619;&#3632;&#3604;&#3633;&#3610;"/>
+  <l:gentext key="MsgOrig" text="&#3607;&#3637;&#3656;&#3617;&#3634;"/>
+  <l:gentext key="msgorig" text="&#3607;&#3637;&#3656;&#3617;&#3634;"/>
+  <l:gentext key="NOTE" text="&#3627;&#3617;&#3634;&#3618;&#3648;&#3627;&#3605;&#3640;"/>
+  <l:gentext key="Note" text="&#3627;&#3617;&#3634;&#3618;&#3648;&#3627;&#3605;&#3640;"/>
+  <l:gentext key="note" text="&#3627;&#3617;&#3634;&#3618;&#3648;&#3627;&#3605;&#3640;"/>
+  <l:gentext key="Part" text="&#3616;&#3634;&#3588;"/>
+  <l:gentext key="part" text="&#3616;&#3634;&#3588;"/>
+  <l:gentext key="Preface" text="&#3588;&#3635;&#3609;&#3635;"/>
+  <l:gentext key="preface" text="&#3588;&#3635;&#3609;&#3635;"/>
+  <l:gentext key="Procedure" text="&#3619;&#3632;&#3648;&#3610;&#3637;&#3618;&#3610;&#3585;&#3634;&#3619;"/>
+  <l:gentext key="procedure" text="&#3619;&#3632;&#3648;&#3610;&#3637;&#3618;&#3610;&#3585;&#3634;&#3619;"/>
+  <l:gentext key="ProductionSet" text="&#3612;&#3621;&#3636;&#3605;"/>
+  <l:gentext key="Published" text="&#3605;&#3637;&#3614;&#3636;&#3617;&#3614;&#3660;"/>
+  <l:gentext key="published" text="&#3605;&#3637;&#3614;&#3636;&#3617;&#3614;&#3660;"/>
+  <l:gentext key="Question" text="&#3606;&#3634;&#3617;:"/>
+  <l:gentext key="question" text="&#3606;&#3634;&#3617;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#3627;&#3609;&#3633;&#3591;&#3626;&#3639;&#3629;&#3629;&#3657;&#3634;&#3591;&#3629;&#3636;&#3591;"/>
+  <l:gentext key="reference" text="&#3627;&#3609;&#3633;&#3591;&#3626;&#3639;&#3629;&#3629;&#3657;&#3634;&#3591;&#3629;&#3636;&#3591;"/>
+  <l:gentext key="RefName" text="&#3594;&#3639;&#3656;&#3629;"/>
+  <l:gentext key="refname" text="&#3594;&#3639;&#3656;&#3629;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#3626;&#3634;&#3619;&#3632;&#3626;&#3635;&#3588;&#3633;&#3597;"/>
+  <l:gentext key="refsynopsisdiv" text="&#3626;&#3634;&#3619;&#3632;&#3626;&#3635;&#3588;&#3633;&#3597;"/>
+  <l:gentext key="RevHistory" text="&#3610;&#3633;&#3609;&#3607;&#3638;&#3585;&#3619;&#3640;&#3656;&#3609;"/>
+  <l:gentext key="revhistory" text="&#3610;&#3633;&#3609;&#3607;&#3638;&#3585;&#3619;&#3640;&#3656;&#3609;"/>
+  <l:gentext key="revision" text="&#3619;&#3640;&#3656;&#3609;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="Revision" text="&#3619;&#3640;&#3656;&#3609;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="sect1" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="sect2" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="sect3" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="sect4" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="sect5" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="section" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="Section" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;"/>
+  <l:gentext key="See" text="&#3604;&#3641;"/>
+  <l:gentext key="see" text="&#3604;&#3641;"/>
+  <l:gentext key="SeeAlso" text="&#3604;&#3641;&#3648;&#3614;&#3636;&#3656;&#3617;&#3648;&#3605;&#3636;&#3617;"/>
+  <l:gentext key="seealso" text="&#3604;&#3641;&#3648;&#3614;&#3636;&#3656;&#3617;&#3648;&#3605;&#3636;&#3617;"/>
+  <l:gentext key="Seealso" text="&#3604;&#3641;&#3648;&#3614;&#3636;&#3656;&#3617;&#3648;&#3605;&#3636;&#3617;"/>
+  <l:gentext key="set" text="&#3594;&#3640;&#3604;"/>
+  <l:gentext key="Set" text="&#3594;&#3640;&#3604;"/>
+  <l:gentext key="setindex" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3594;&#3640;&#3604;"/>
+  <l:gentext key="SetIndex" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3594;&#3640;&#3604;"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="step" text="&#3621;&#3635;&#3604;&#3633;&#3610;"/>
+  <l:gentext key="Step" text="&#3621;&#3635;&#3604;&#3633;&#3610;"/>
+  <l:gentext key="Table" text="&#3605;&#3634;&#3619;&#3634;&#3591;"/>
+  <l:gentext key="table" text="&#3605;&#3634;&#3619;&#3634;&#3591;"/>
+  <l:gentext key="tip" text="&#3588;&#3635;&#3649;&#3609;&#3632;&#3609;&#3635;"/>
+  <l:gentext key="TIP" text="&#3588;&#3635;&#3649;&#3609;&#3632;&#3609;&#3635;"/>
+  <l:gentext key="Tip" text="&#3588;&#3635;&#3649;&#3609;&#3632;&#3609;&#3635;"/>
+  <l:gentext key="Warning" text="&#3650;&#3611;&#3619;&#3604;&#3619;&#3632;&#3623;&#3633;&#3591;"/>
+  <l:gentext key="warning" text="&#3650;&#3611;&#3619;&#3604;&#3619;&#3632;&#3623;&#3633;&#3591;"/>
+  <l:gentext key="WARNING" text="&#3650;&#3611;&#3619;&#3604;&#3619;&#3632;&#3623;&#3633;&#3591;"/>
+  <l:gentext key="and" text="&#3649;&#3621;&#3632;"/>
+  <l:gentext key="by" text="&#3650;&#3604;&#3618;"/>
+  <l:gentext key="Edited" text="&#3648;&#3619;&#3637;&#3618;&#3610;&#3648;&#3619;&#3637;&#3618;&#3591;"/>
+  <l:gentext key="edited" text="&#3648;&#3619;&#3637;&#3618;&#3610;&#3648;&#3619;&#3637;&#3618;&#3591;"/>
+  <l:gentext key="Editedby" text="&#3648;&#3619;&#3637;&#3618;&#3610;&#3648;&#3619;&#3637;&#3618;&#3591;&#3650;&#3604;&#3610;"/>
+  <l:gentext key="editedby" text="&#3648;&#3619;&#3637;&#3618;&#3610;&#3648;&#3619;&#3637;&#3618;&#3591;&#3650;&#3604;&#3610;"/>
+  <l:gentext key="in" text="&#3651;&#3609;"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="&#3652;&#3617;&#3656;&#3614;&#3610;&#3626;&#3656;&#3623;&#3609;&#3607;&#3637;&#3656;&#3605;&#3657;&#3629;&#3591;&#3585;&#3634;&#3619;"/>
+  <l:gentext key="notes" text="&#3627;&#3617;&#3634;&#3618;&#3648;&#3627;&#3605;&#3640;"/>
+  <l:gentext key="Notes" text="&#3627;&#3617;&#3634;&#3618;&#3648;&#3627;&#3605;&#3640;"/>
+  <l:gentext key="Pgs" text="&#3627;&#3609;&#3657;&#3634;"/>
+  <l:gentext key="pgs" text="&#3627;&#3609;&#3657;&#3634;"/>
+  <l:gentext key="Revisedby" text="&#3649;&#3585;&#3657;&#3652;&#3586;&#3611;&#3619;&#3633;&#3610;&#3611;&#3619;&#3640;&#3591;&#3650;&#3604;&#3618;: "/>
+  <l:gentext key="revisedby" text="&#3649;&#3585;&#3657;&#3652;&#3586;&#3611;&#3619;&#3633;&#3610;&#3611;&#3619;&#3640;&#3591;&#3650;&#3604;&#3618;: "/>
+  <l:gentext key="TableNotes" text="&#3627;&#3617;&#3634;&#3618;&#3648;&#3627;&#3605;&#3640;"/>
+  <l:gentext key="tablenotes" text="&#3627;&#3617;&#3634;&#3618;&#3648;&#3627;&#3605;&#3640;"/>
+  <l:gentext key="TableofContents" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;"/>
+  <l:gentext key="tableofcontents" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;"/>
+  <l:gentext key="unexpectedelementname" text="&#3614;&#3610;&#3626;&#3656;&#3623;&#3609;&#3607;&#3637;&#3656;&#3652;&#3617;&#3656;&#3605;&#3657;&#3629;&#3591;&#3585;&#3634;&#3619;"/>
+  <l:gentext key="unsupported" text="&#3652;&#3617;&#3656;&#3626;&#3609;&#3633;&#3610;&#3626;&#3609;&#3640;&#3609;"/>
+  <l:gentext key="xrefto" text="xref to"/>
+  <l:gentext key="listofequations" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3626;&#3617;&#3585;&#3634;&#3619;"/>
+  <l:gentext key="ListofEquations" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3626;&#3617;&#3585;&#3634;&#3619;"/>
+  <l:gentext key="ListofExamples" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3605;&#3633;&#3623;&#3629;&#3618;&#3656;&#3634;&#3591;"/>
+  <l:gentext key="listofexamples" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3605;&#3633;&#3623;&#3629;&#3618;&#3656;&#3634;&#3591;"/>
+  <l:gentext key="ListofFigures" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3619;&#3641;&#3611;"/>
+  <l:gentext key="listoffigures" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3619;&#3641;&#3611;"/>
+  <l:gentext key="listoftables" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3605;&#3634;&#3619;&#3634;&#3591;"/>
+  <l:gentext key="ListofTables" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3605;&#3634;&#3619;&#3634;&#3591;"/>
+  <l:gentext key="ListofUnknown" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3629;&#3639;&#3656;&#3609; &#3654;"/>
+  <l:gentext key="listofunknown" text="&#3626;&#3634;&#3619;&#3610;&#3633;&#3597;&#3629;&#3639;&#3656;&#3609; &#3654;"/>
+  <l:gentext key="nav-home" text="&#3627;&#3609;&#3657;&#3634;&#3649;&#3619;&#3585;"/>
+  <l:gentext key="nav-next" text="&#3605;&#3656;&#3629;&#3652;&#3611;"/>
+  <l:gentext key="nav-next-sibling" text="&#3605;&#3656;&#3629;&#3652;&#3611;"/>
+  <l:gentext key="nav-prev" text="&#3585;&#3656;&#3629;&#3609;&#3627;&#3609;&#3657;&#3634;"/>
+  <l:gentext key="nav-prev-sibling" text="&#3585;&#3656;&#3629;&#3609;&#3627;&#3609;&#3657;&#3634;"/>
+  <l:gentext key="nav-up" text="&#3585;&#3621;&#3633;&#3610;"/>
+  <l:gentext key="sectioncalled" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634;"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="&#3626;&#3633;&#3597;&#3621;&#3633;&#3585;&#3625;&#3603;&#3660;"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/th.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#3616;&#3634;&#3588;&#3612;&#3609;&#3623;&#3585; %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#3610;&#3607;&#3607;&#3637;&#3656; %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#3626;&#3617;&#3585;&#3634;&#3619; %n. %t"/>
+    <l:template name="example" text="&#3605;&#3633;&#3623;&#3629;&#3618;&#3656;&#3634;&#3591; %n. %t"/>
+    <l:template name="figure" text="&#3619;&#3641;&#3611; %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#3616;&#3634;&#3588; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#3619;&#3632;&#3648;&#3610;&#3637;&#3618;&#3610;&#3585;&#3634;&#3619; %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="&#3612;&#3621;&#3636;&#3605; %n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#3605;&#3634;&#3619;&#3634;&#3591; %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#3616;&#3634;&#3588;&#3612;&#3609;&#3623;&#3585; %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="&#3610;&#3607;&#3607;&#3637;&#3656; %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#3605;&#3629;&#3610;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#3606;&#3634;&#3617;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#3606;&#3634;&#3617;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#3605;&#3629;&#3610;:&#160;%n"/>
+    <l:template name="appendix" text="&#3616;&#3634;&#3588;&#3612;&#3609;&#3623;&#3585;&#160;%n"/>
+    <l:template name="bridgehead" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n"/>
+    <l:template name="chapter" text="&#3610;&#3607;&#3607;&#3637;&#3656;&#160;%n"/>
+    <l:template name="equation" text="&#3626;&#3617;&#3585;&#3634;&#3619;&#160;%n"/>
+    <l:template name="example" text="&#3605;&#3633;&#3623;&#3629;&#3618;&#3656;&#3634;&#3591;&#160;%n"/>
+    <l:template name="figure" text="&#3619;&#3641;&#3611;&#160;%n"/>
+    <l:template name="part" text="&#3616;&#3634;&#3588;&#160;%n"/>
+    <l:template name="procedure" text="&#3619;&#3632;&#3648;&#3610;&#3637;&#3618;&#3610;&#3585;&#3634;&#3619;&#160;%n"/>
+    <l:template name="productionset" text="&#3612;&#3621;&#3636;&#3605;&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#3606;&#3634;&#3617;:&#160;%n"/>
+    <l:template name="question" text="&#3606;&#3634;&#3617;:&#160;%n"/>
+    <l:template name="sect1" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n"/>
+    <l:template name="sect2" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n"/>
+    <l:template name="sect3" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n"/>
+    <l:template name="sect4" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n"/>
+    <l:template name="sect5" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n"/>
+    <l:template name="section" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n"/>
+    <l:template name="table" text="&#3605;&#3634;&#3619;&#3634;&#3591;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#3616;&#3634;&#3588;&#3612;&#3609;&#3623;&#3585;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="&#3610;&#3607;&#3607;&#3637;&#3656;&#160;%n, %t"/>
+    <l:template name="equation" text="&#3626;&#3617;&#3585;&#3634;&#3619;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="&#3605;&#3633;&#3623;&#3629;&#3618;&#3656;&#3634;&#3591;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="&#3619;&#3641;&#3611;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="&#3616;&#3634;&#3588;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="&#3619;&#3632;&#3648;&#3610;&#3637;&#3618;&#3610;&#3585;&#3634;&#3619;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="&#3612;&#3621;&#3636;&#3605;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#3605;&#3629;&#3609;&#3607;&#3637;&#3656;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#3605;&#3629;&#3609;&#3609;&#3637;&#3657;&#3648;&#3657;&#3619;&#3637;&#3618;&#3585;&#3623;&#3656;&#3634; &#8220;%t&#8221;"/>
+    <l:template name="table" text="&#3605;&#3634;&#3619;&#3634;&#3591;&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#3649;&#3621;&#3632; "/>
+    <l:template name="seplast" text=", &#3649;&#3621;&#3632; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#3604;&#3641; "/>
+    <l:template name="seealso" text="&#3604;&#3641;&#3648;&#3614;&#3636;&#3656;&#3617;&#3648;&#3605;&#3636;&#3617; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#3612;&#3641;&#3657;&#3629;&#3656;&#3634;&#3609;: "/>
+    <l:template name="MsgLevel" text="&#3619;&#3632;&#3604;&#3633;&#3610;: "/>
+    <l:template name="MsgOrig" text="&#3607;&#3637;&#3656;&#3617;&#3634;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x041e Thai"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/titles.xsl b/docs-xml/xslt/db2latex-xsl/xsl/common/titles.xsl
new file mode 100644
index 00000000000..628741c2fbc
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/titles.xsl
@@ -0,0 +1,595 @@
+<?xml version='1.0'?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+                exclude-result-prefixes="doc"
+                version='1.0'>
+
+<!-- ********************************************************************
+     $Id: titles.xsl,v 1.2 2004/01/04 09:25:57 j-devenish Exp $
+     ********************************************************************
+
+     This file is part of the XSL DocBook Stylesheet distribution.
+
+     Copyright (C) 1999, 2000, 2001, 2002 Norman Walsh.
+     ******************************************************************** -->
+
+<!-- ==================================================================== -->
+
+<!-- title markup -->
+
+<doc:mode mode="title.markup" xmlns="">
+<refpurpose>Provides access to element titles</refpurpose>
+<refdescription>
+<para>Processing an element in the
+<literal role="mode">title.markup</literal> mode produces the
+title of the element. This does not include the label.
+</para>
+</refdescription>
+</doc:mode>
+
+<xsl:template match="*" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:param name="verbose" select="1"/>
+
+  <xsl:choose>
+    <xsl:when test="title">
+      <xsl:apply-templates select="title[1]" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:when test="local-name(.) = 'partintro'">
+      <!-- partintro's don't have titles, use the parent (part or reference)
+           title instead. -->
+      <xsl:apply-templates select="parent::*" mode="title.markup"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:if test="$verbose">
+        <xsl:message>
+          <xsl:text>Request for title of element with no title: </xsl:text>
+          <xsl:value-of select="name(.)"/>
+          <xsl:if test="@id">
+            <xsl:text> (id="</xsl:text>
+            <xsl:value-of select="@id"/>
+            <xsl:text>")</xsl:text>
+          </xsl:if>
+        </xsl:message>
+      </xsl:if>
+      <xsl:text>???TITLE???</xsl:text>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="title" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+
+  <xsl:choose>
+    <xsl:when test="$allow-anchors != 0">
+      <xsl:apply-templates/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates mode="no.anchor.mode"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- only occurs in HTML Tables! -->
+<xsl:template match="caption" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+
+  <xsl:choose>
+    <xsl:when test="$allow-anchors != 0">
+      <xsl:apply-templates/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates mode="no.anchor.mode"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="set" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:apply-templates select="(setinfo/title|title)[1]"
+                       mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="book" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:apply-templates select="(bookinfo/title|title)[1]"
+                       mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="part" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:apply-templates select="(partinfo/title|docinfo/title|title)[1]"
+                       mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="preface|chapter|appendix" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+
+<!--
+  <xsl:message>
+    <xsl:value-of select="name(.)"/>
+    <xsl:text> </xsl:text>
+    <xsl:value-of select="$allow-anchors"/>
+  </xsl:message>
+-->
+
+  <xsl:variable name="title" select="(docinfo/title
+                                      |prefaceinfo/title
+                                      |chapterinfo/title
+                                      |appendixinfo/title
+                                      |title)[1]"/>
+  <xsl:apply-templates select="$title" mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="dedication" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:choose>
+    <xsl:when test="title">
+      <xsl:apply-templates select="title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key" select="'Dedication'"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="colophon" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:choose>
+    <xsl:when test="title">
+      <xsl:apply-templates select="title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key" select="'Colophon'"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="article" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:variable name="title" select="(artheader/title
+                                      |articleinfo/title
+                                      |title)[1]"/>
+
+  <xsl:apply-templates select="$title" mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="reference" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:apply-templates select="(referenceinfo/title|docinfo/title|title)[1]"
+                       mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="refentry" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:variable name="refmeta" select=".//refmeta"/>
+  <xsl:variable name="refentrytitle" select="$refmeta//refentrytitle"/>
+  <xsl:variable name="refnamediv" select=".//refnamediv"/>
+  <xsl:variable name="refname" select="$refnamediv//refname"/>
+
+  <xsl:variable name="title">
+    <xsl:choose>
+      <xsl:when test="$refentrytitle">
+        <xsl:apply-templates select="$refentrytitle[1]" mode="title.markup"/>
+      </xsl:when>
+      <xsl:when test="$refname">
+        <xsl:apply-templates select="$refname[1]" mode="title.markup"/>
+      </xsl:when>
+      <xsl:otherwise>REFENTRY WITHOUT TITLE???</xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:copy-of select="$title"/>
+</xsl:template>
+
+<xsl:template match="refentrytitle|refname" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:choose>
+    <xsl:when test="$allow-anchors != 0">
+      <xsl:apply-templates/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates mode="no.anchor.mode"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="section
+                     |sect1|sect2|sect3|sect4|sect5
+                     |refsect1|refsect2|refsect3
+                     |simplesect"
+              mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:variable name="title" select="(sectioninfo/title
+                                      |sect1info/title
+                                      |sect2info/title
+                                      |sect3info/title
+                                      |sect4info/title
+                                      |sect5info/title
+                                      |refsect1info/title
+                                      |refsect2info/title
+                                      |refsect3info/title
+                                      |title)[1]"/>
+
+  <xsl:apply-templates select="$title" mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="bridgehead" mode="title.markup">
+  <xsl:apply-templates mode="title.markup"/>
+</xsl:template>
+
+<xsl:template match="refsynopsisdiv" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:choose>
+    <xsl:when test="title">
+      <xsl:apply-templates select="title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key" select="'RefSynopsisDiv'"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="bibliography" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:variable name="title" select="(bibliographyinfo/title|title)[1]"/>
+  <xsl:choose>
+    <xsl:when test="$title">
+      <xsl:apply-templates select="$title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key" select="'Bibliography'"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="glossary" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:variable name="title" select="(glossaryinfo/title|title)[1]"/>
+  <xsl:choose>
+    <xsl:when test="$title">
+      <xsl:apply-templates select="$title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext.element.name">
+        <xsl:with-param name="element.name" select="name(.)"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="glossentry" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:apply-templates select="glossterm" mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="glossterm" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+
+  <xsl:choose>
+    <xsl:when test="$allow-anchors != 0">
+      <xsl:apply-templates/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates mode="no.anchor.mode"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="index" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:variable name="title" select="(indexinfo/title|title)[1]"/>
+  <xsl:choose>
+    <xsl:when test="$title">
+      <xsl:apply-templates select="$title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key" select="'Index'"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="setindex" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:variable name="title" select="(setindexinfo/title|title)[1]"/>
+  <xsl:choose>
+    <xsl:when test="$title">
+      <xsl:apply-templates select="$title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key" select="'SetIndex'"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="figure|example|equation" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:apply-templates select="title" mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="table" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:apply-templates select="title|caption" mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="procedure" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:apply-templates select="title" mode="title.markup">
+    <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="abstract" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:choose>
+    <xsl:when test="title">
+      <xsl:apply-templates select="title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key" select="'Abstract'"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="caution|tip|warning|important|note" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:variable name="title" select="title[1]"/>
+  <xsl:choose>
+    <xsl:when test="$title">
+      <xsl:apply-templates select="$title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key">
+          <xsl:choose>
+            <xsl:when test="local-name(.)='note'">Note</xsl:when>
+            <xsl:when test="local-name(.)='important'">Important</xsl:when>
+            <xsl:when test="local-name(.)='caution'">Caution</xsl:when>
+            <xsl:when test="local-name(.)='warning'">Warning</xsl:when>
+            <xsl:when test="local-name(.)='tip'">Tip</xsl:when>
+          </xsl:choose>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="question" mode="title.markup">
+  <!-- questions don't have titles -->
+  <xsl:text>Question</xsl:text>
+</xsl:template>
+
+<xsl:template match="answer" mode="title.markup">
+  <!-- answers don't have titles -->
+  <xsl:text>Answer</xsl:text>
+</xsl:template>
+
+<xsl:template match="qandaentry" mode="title.markup">
+  <!-- qandaentrys are represented by the first question in them -->
+  <xsl:text>Question</xsl:text>
+</xsl:template>
+
+<xsl:template match="legalnotice" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:choose>
+    <xsl:when test="title">
+      <xsl:apply-templates select="title" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key" select="'LegalNotice'"/>
+      </xsl:call-template>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template match="*" mode="titleabbrev.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:param name="verbose" select="1"/>
+
+  <xsl:choose>
+    <xsl:when test="titleabbrev">
+      <xsl:apply-templates select="titleabbrev[1]" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates select="." mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+        <xsl:with-param name="verbose" select="$verbose"/>
+      </xsl:apply-templates>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="preface|chapter|appendix" mode="titleabbrev.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:param name="verbose" select="1"/>
+
+  <xsl:variable name="titleabbrev" select="(docinfo/titleabbrev
+                                           |prefaceinfo/titleabbrev
+                                           |chapterinfo/titleabbrev
+                                           |appendixinfo/titleabbrev
+                                           |titleabbrev)[1]"/>
+
+  <xsl:choose>
+    <xsl:when test="$titleabbrev">
+      <xsl:apply-templates select="$titleabbrev" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates select="." mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+        <xsl:with-param name="verbose" select="$verbose"/>
+      </xsl:apply-templates>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="article" mode="titleabbrev.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:param name="verbose" select="1"/>
+
+  <xsl:variable name="titleabbrev" select="(artheader/titleabbrev
+                                           |articleinfo/titleabbrev
+                                           |titleabbrev)[1]"/>
+
+  <xsl:choose>
+    <xsl:when test="$titleabbrev">
+      <xsl:apply-templates select="$titleabbrev" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates select="." mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+        <xsl:with-param name="verbose" select="$verbose"/>
+      </xsl:apply-templates>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="section
+                     |sect1|sect2|sect3|sect4|sect5
+                     |refsect1|refsect2|refsect3
+                     |simplesect"
+              mode="titleabbrev.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+  <xsl:param name="verbose" select="1"/>
+
+  <xsl:variable name="titleabbrev" select="(sectioninfo/titleabbrev
+                                      |sect1info/titleabbrev
+                                      |sect2info/titleabbrev
+                                      |sect3info/titleabbrev
+                                      |sect4info/titleabbrev
+                                      |sect5info/titleabbrev
+                                      |refsect1info/titleabbrev
+                                      |refsect2info/titleabbrev
+                                      |refsect3info/titleabbrev
+                                      |titleabbrev)[1]"/>
+
+  <xsl:choose>
+    <xsl:when test="$titleabbrev">
+      <xsl:apply-templates select="$titleabbrev" mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+      </xsl:apply-templates>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates select="." mode="title.markup">
+        <xsl:with-param name="allow-anchors" select="$allow-anchors"/>
+        <xsl:with-param name="verbose" select="$verbose"/>
+      </xsl:apply-templates>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="titleabbrev" mode="title.markup">
+  <xsl:param name="allow-anchors" select="0"/>
+
+  <xsl:choose>
+    <xsl:when test="$allow-anchors != 0">
+      <xsl:apply-templates/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates mode="no.anchor.mode"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- ============================================================ -->
+
+<xsl:template match="*" mode="no.anchor.mode">
+  <xsl:apply-templates mode="no.anchor.mode"/>
+</xsl:template>
+
+<xsl:template match="footnote" mode="no.anchor.mode">
+  <!-- nop, suppressed -->
+</xsl:template>
+
+<xsl:template match="anchor" mode="no.anchor.mode">
+  <!-- nop, suppressed -->
+</xsl:template>
+
+<xsl:template match="ulink" mode="no.anchor.mode">
+  <xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="link" mode="no.anchor.mode">
+  <xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="olink" mode="no.anchor.mode">
+  <xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="indexterm" mode="no.anchor.mode">
+  <!-- nop, suppressed -->
+</xsl:template>
+
+<xsl:template match="xref" mode="no.anchor.mode">
+  <!-- FIXME: this should generate the text without the link... -->
+</xsl:template>
+
+<!-- ============================================================ -->
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/tr.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/tr.xml
new file mode 100644
index 00000000000..f531ca4a16e
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/tr.xml
@@ -0,0 +1,510 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="tr" english-language-name="Turkish">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/tr.xml -->
+  <l:gentext key="Abstract" text="&#214;zet"/>
+  <l:gentext key="abstract" text="&#214;zet"/>
+  <l:gentext key="Answer" text="Cevap:"/>
+  <l:gentext key="answer" text="Cevap:"/>
+  <l:gentext key="Appendix" text="Ek"/>
+  <l:gentext key="appendix" text="ek"/>
+  <l:gentext key="Article" text="Makale"/>
+  <l:gentext key="article" text="Makale"/>
+  <l:gentext key="Bibliography" text="Kaynak&#231;a"/>
+  <l:gentext key="bibliography" text="Kaynak&#231;a"/>
+  <l:gentext key="Book" text="Kitap"/>
+  <l:gentext key="book" text="Kitap"/>
+  <l:gentext key="CAUTION" text="D&#304;KKAT"/>
+  <l:gentext key="Caution" text="Dikkat"/>
+  <l:gentext key="caution" text="Dikkat"/>
+  <l:gentext key="Chapter" text="B&#246;l&#252;m"/>
+  <l:gentext key="chapter" text="b&#246;l&#252;m"/>
+  <l:gentext key="Colophon" text="Kitap hakk&#305;nda"/>
+  <l:gentext key="colophon" text="Kitap hakk&#305;nda"/>
+  <l:gentext key="Copyright" text="Telif Hakk&#305;"/>
+  <l:gentext key="copyright" text="Telif Hakk&#305;"/>
+  <l:gentext key="Dedication" text="&#304;thaf"/>
+  <l:gentext key="dedication" text="&#304;thaf"/>
+  <l:gentext key="Edition" text="Bask&#305;"/>
+  <l:gentext key="edition" text="Bask&#305;"/>
+  <l:gentext key="Equation" text="Denklem"/>
+  <l:gentext key="equation" text="Denklem"/>
+  <l:gentext key="Example" text="&#214;rnek"/>
+  <l:gentext key="example" text="&#214;rnek"/>
+  <l:gentext key="Figure" text="&#350;ekil"/>
+  <l:gentext key="figure" text="&#350;ekil"/>
+  <l:gentext key="Glossary" text="S&#246;zl&#252;k"/>
+  <l:gentext key="glossary" text="S&#246;zl&#252;k"/>
+  <l:gentext key="GlossSee" text="Bkz."/>
+  <l:gentext key="glosssee" text="Bkz."/>
+  <l:gentext key="GlossSeeAlso" text="Bkz."/>
+  <l:gentext key="glossseealso" text="Bkz."/>
+  <l:gentext key="IMPORTANT" text="&#214;NEML&#304;"/>
+  <l:gentext key="important" text="&#214;nemli"/>
+  <l:gentext key="Important" text="&#214;nemli"/>
+  <l:gentext key="Index" text="Dizin"/>
+  <l:gentext key="index" text="Dizin"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Yasal Uyar&#305;"/>
+  <l:gentext key="legalnotice" text="Yasal Uyar&#305;"/>
+  <l:gentext key="MsgAud" text="Hedef Okuyucu"/>
+  <l:gentext key="msgaud" text="Hedef Okuyucu"/>
+  <l:gentext key="MsgLevel" text="Level"/>
+  <l:gentext key="msglevel" text="D&#252;zey"/>
+  <l:gentext key="MsgOrig" text="D&#252;zey"/>
+  <l:gentext key="msgorig" text="Kaynak"/>
+  <l:gentext key="NOTE" text="NOT"/>
+  <l:gentext key="Note" text="Not"/>
+  <l:gentext key="note" text="Not"/>
+  <l:gentext key="Part" text="K&#305;s&#305;m"/>
+  <l:gentext key="part" text="K&#305;s&#305;m"/>
+  <l:gentext key="Preface" text="&#214;ns&#246;z"/>
+  <l:gentext key="preface" text="&#214;ns&#246;z"/>
+  <l:gentext key="Procedure" text="Y&#246;nerge"/>
+  <l:gentext key="procedure" text="Y&#246;nerge"/>
+  <l:gentext key="ProductionSet" text="Prod&#252;ksiyon"/>
+  <l:gentext key="PubDate" text="Yay&#305;mlanma Tarihi"/>
+  <l:gentext key="pubdate" text="Yay&#305;mlanma Tarihi"/>
+  <l:gentext key="Published" text="Yay&#305;mlanma"/>
+  <l:gentext key="published" text="Yay&#305;mlanma"/>
+  <l:gentext key="Qandadiv" text="S ve C"/>
+  <l:gentext key="qandadiv" text="S ve C"/>
+  <l:gentext key="Question" text="Soru:"/>
+  <l:gentext key="question" text="Soru:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Referans"/>
+  <l:gentext key="reference" text="Referans"/>
+  <l:gentext key="RefName" text="Referans Ad&#305;"/>
+  <l:gentext key="refname" text="Referans Ad&#305;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Synopsis"/>
+  <l:gentext key="refsynopsisdiv" text="Synopsis"/>
+  <l:gentext key="RevHistory" text="Bask&#305; Tarih&#231;esi"/>
+  <l:gentext key="revhistory" text="Bask&#305; Tarih&#231;esi"/>
+  <l:gentext key="revision" text="Bask&#305;"/>
+  <l:gentext key="Revision" text="Bask&#305;"/>
+  <l:gentext key="sect1" text="K&#305;s&#305;m"/>
+  <l:gentext key="sect2" text="K&#305;s&#305;m"/>
+  <l:gentext key="sect3" text="K&#305;s&#305;m"/>
+  <l:gentext key="sect4" text="K&#305;s&#305;m"/>
+  <l:gentext key="sect5" text="K&#305;s&#305;m"/>
+  <l:gentext key="section" text="K&#305;s&#305;m"/>
+  <l:gentext key="Section" text="K&#305;s&#305;m"/>
+  <l:gentext key="see" text="Bkz."/>
+  <l:gentext key="See" text="Bkz."/>
+  <l:gentext key="seealso" text="Bkz."/>
+  <l:gentext key="Seealso" text="Bak&#305;n&#305;z"/>
+  <l:gentext key="SeeAlso" text="Bak&#305;n&#305;z"/>
+  <l:gentext key="set" text="Tak&#305;m"/>
+  <l:gentext key="Set" text="Tak&#305;m"/>
+  <l:gentext key="setindex" text="Tak&#305;m Dizini"/>
+  <l:gentext key="SetIndex" text="Tak&#305;m Dizini"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text=""/>
+  <l:gentext key="step" text="ad&#305;m"/>
+  <l:gentext key="Step" text="Ad&#305;m"/>
+  <l:gentext key="Table" text="Tablo"/>
+  <l:gentext key="table" text="Tablo"/>
+  <l:gentext key="tip" text="&#304;pucu"/>
+  <l:gentext key="TIP" text="&#304;PUCU"/>
+  <l:gentext key="Tip" text="&#304;pucu"/>
+  <l:gentext key="Warning" text="Uyar&#305;"/>
+  <l:gentext key="warning" text="Uyar&#305;"/>
+  <l:gentext key="WARNING" text="UYARI"/>
+  <l:gentext key="and" text="ve"/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="called" text=""/>
+  <l:gentext key="Edited" text="Yay&#305;na haz&#305;rlayan"/>
+  <l:gentext key="edited" text="yay&#305;na haz&#305;rlayan"/>
+  <l:gentext key="Editedby" text="Yay&#305;na haz&#305;rlayan"/>
+  <l:gentext key="editedby" text="yay&#305;na haz&#305;rlayan"/>
+  <l:gentext key="in" text=""/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="varolmayan eleman"/>
+  <l:gentext key="notes" text="Notlar"/>
+  <l:gentext key="Notes" text="Notlar"/>
+  <l:gentext key="Pgs" text="Sayfa"/>
+  <l:gentext key="pgs" text="Sayfa"/>
+  <l:gentext key="Revisedby" text="D&#252;zeltmeler: "/>
+  <l:gentext key="revisedby" text="D&#252;zeltmeler: "/>
+  <l:gentext key="TableNotes" text="Notlar"/>
+  <l:gentext key="tablenotes" text="Notlar"/>
+  <l:gentext key="the" text=""/>
+  <l:gentext key="TableofContents" text="&#304;&#231;indekiler"/>
+  <l:gentext key="tableofcontents" text="&#304;&#231;indekiler"/>
+  <l:gentext key="unexpectedelementname" text="Beklenmeyen eleman ad&#305;"/>
+  <l:gentext key="unsupported" text="desteklenmiyor"/>
+  <l:gentext key="xrefto" text=""/>
+  <l:gentext key="listofequations" text="Denklemler"/>
+  <l:gentext key="ListofEquations" text="Denklemler"/>
+  <l:gentext key="ListofExamples" text="&#214;rnekler"/>
+  <l:gentext key="listofexamples" text="&#214;rnekler"/>
+  <l:gentext key="ListofFigures" text="&#350;ekiller"/>
+  <l:gentext key="listoffigures" text="&#350;ekiller"/>
+  <l:gentext key="listoftables" text="Tablolar"/>
+  <l:gentext key="ListofTables" text="Tablolar"/>
+  <l:gentext key="ListofProcedures" text="Y&#246;nergeler"/>
+  <l:gentext key="listofprocedures" text="Y&#246;nergeler"/>
+  <l:gentext key="ListofUnknown" text="Bilinmeyenler"/>
+  <l:gentext key="listofunknown" text="Bilinmeyenler"/>
+  <l:gentext key="nav-home" text="Ba&#351;lang&#305;&#231;"/>
+  <l:gentext key="nav-next" text="Sonraki"/>
+  <l:gentext key="nav-next-sibling" text="Sonraki B&#246;l&#252;m"/>
+  <l:gentext key="nav-prev" text="&#214;nceki"/>
+  <l:gentext key="nav-prev-sibling" text="&#214;nceki B&#246;l&#252;m"/>
+  <l:gentext key="nav-up" text="Yukar&#305;"/>
+  <l:gentext key="nav-toc" text="&#304;&#231;indekiler"/>
+  <l:gentext key="sectioncalled" text=""/>
+  <l:gentext key="Draft" text="Taslak"/>
+  <l:gentext key="above" text="&#252;st&#252;nde"/>
+  <l:gentext key="below" text="alt&#305;nda"/>
+  <l:gentext key="index symbols" text="Semboller"/>
+  <l:gentext key="lowercase.alpha" text="abc&#231;defg&#287;h&#305;ijklmno&#246;prs&#351;tu&#252;vyz"/>
+  <l:gentext key="uppercase.alpha" text="ABC&#199;DEFG&#286;HI&#304;JKLMNO&#214;PRS&#350;TU&#220;VYZ"/>
+  <l:gentext key="hyphenation-character" text="-"/>
+  <l:gentext key="hyphenation-push-character-count" text="3"/>
+  <l:gentext key="hyphenation-remain-character-count" text="2"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/tr.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="singlestartquote" text="&#8216;"/>
+  <l:dingbat key="singleendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Ek %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="B&#246;l&#252;m %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Denklem %n. %t"/>
+    <l:template name="example" text="&#214;rnek %n. %t"/>
+    <l:template name="figure" text="&#350;ekil %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="glossentry" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="K&#305;s&#305;m %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Y&#246;nerge %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Prod&#252;ksiyon %n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Tablo %n. %t"/>
+    <l:template name="task" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article/appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Ek %n. %t"/>
+    <l:template name="article/appendix" text="%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="B&#246;l&#252;m %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="Cevap: %n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="Soru: %n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="Soru: %n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="page" text="(sayfa %p)"/>
+    <l:template name="pageabbrev" text="(shf. %p)"/>
+    <l:template name="Page" text="Sayfa %p"/>
+    <l:template name="bridgehead" text=" &#8220;%t&#8221;"/>
+    <l:template name="refsection" text=" &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text=" &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text=" &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text=" &#8220;%t&#8221;"/>
+    <l:template name="sect1" text=" &#8220;%t&#8221;"/>
+    <l:template name="sect2" text=" &#8220;%t&#8221;"/>
+    <l:template name="sect3" text=" &#8220;%t&#8221;"/>
+    <l:template name="sect4" text=" &#8220;%t&#8221;"/>
+    <l:template name="sect5" text=" &#8220;%t&#8221;"/>
+    <l:template name="section" text=" &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text=" &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="Cevap:&#160;%n"/>
+    <l:template name="appendix" text="Ek&#160;%n"/>
+    <l:template name="bridgehead" text="K&#305;s&#305;m&#160;%n"/>
+    <l:template name="chapter" text="B&#246;l&#252;m&#160;%n"/>
+    <l:template name="equation" text="Denklem&#160;%n"/>
+    <l:template name="example" text="&#214;rnek&#160;%n"/>
+    <l:template name="figure" text="&#350;ekil&#160;%n"/>
+    <l:template name="part" text="K&#305;s&#305;m&#160;%n"/>
+    <l:template name="procedure" text="Y&#246;nerge&#160;%n"/>
+    <l:template name="productionset" text="Prod&#252;ksiyon&#160;%n"/>
+    <l:template name="qandadiv" text="S ve C&#160;%n"/>
+    <l:template name="qandaentry" text="Soru:&#160;%n"/>
+    <l:template name="question" text="Soru:&#160;%n"/>
+    <l:template name="sect1" text="K&#305;s&#305;m&#160;%n"/>
+    <l:template name="sect2" text="K&#305;s&#305;m&#160;%n"/>
+    <l:template name="sect3" text="K&#305;s&#305;m&#160;%n"/>
+    <l:template name="sect4" text="K&#305;s&#305;m&#160;%n"/>
+    <l:template name="sect5" text="K&#305;s&#305;m&#160;%n"/>
+    <l:template name="section" text="K&#305;s&#305;m&#160;%n"/>
+    <l:template name="table" text="Tablo&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Ek&#160;%n, %t"/>
+    <l:template name="bridgehead" text="K&#305;s&#305;m&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="B&#246;l&#252;m&#160;%n, %t"/>
+    <l:template name="equation" text="Denklem&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="&#214;rnek&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="&#350;ekil&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="K&#305;s&#305;m&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Y&#246;nerge&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Prod&#252;ksiyon&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="S ve C&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text=" &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text=" &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text=" &#8220;%t&#8221;"/>
+    <l:template name="refsection" text=" &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="K&#305;s&#305;m&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="K&#305;s&#305;m&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="K&#305;s&#305;m&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="K&#305;s&#305;m&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="K&#305;s&#305;m&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="K&#305;s&#305;m&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text=" &#8220;%t&#8221;"/>
+    <l:template name="table" text="Tablo&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" ve "/>
+    <l:template name="seplast" text=", ve "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Bkz. "/>
+    <l:template name="seealso" text="Bkz. "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Hedef Okuyucu: "/>
+    <l:template name="MsgLevel" text="Level: "/>
+    <l:template name="MsgOrig" text="D&#252;zey: "/>
+  </l:context>
+  <l:context name="datetime">
+    <l:template name="format" text="d/m/Y"/>
+  </l:context>
+  <l:context name="datetime-full">
+    <l:template name="January" text="Ocak"/>
+    <l:template name="February" text="&#350;ubat"/>
+    <l:template name="March" text="Mart"/>
+    <l:template name="April" text="Nisan"/>
+    <l:template name="May" text="May&#305;s"/>
+    <l:template name="June" text="Haziran"/>
+    <l:template name="July" text="Temmuz"/>
+    <l:template name="August" text="A&#287;ustos"/>
+    <l:template name="September" text="Eyl&#252;l"/>
+    <l:template name="October" text="Ekim"/>
+    <l:template name="November" text="Kas&#305;m"/>
+    <l:template name="December" text="Aral&#305;k"/>
+    <l:template name="Monday" text="Pazartesi"/>
+    <l:template name="Tuesday" text="Sal&#305;"/>
+    <l:template name="Wednesday" text="&#199;ar&#351;amba"/>
+    <l:template name="Thursday" text="Per&#351;embe"/>
+    <l:template name="Friday" text="Cuma"/>
+    <l:template name="Saturday" text="Cumartesi"/>
+    <l:template name="Sunday" text="Pazar"/>
+  </l:context>
+  <l:context name="datetime-abbrev">
+    <l:template name="Jan" text="Oca"/>
+    <l:template name="Feb" text="&#350;ub"/>
+    <l:template name="Mar" text="Mar"/>
+    <l:template name="Apr" text="Nis"/>
+    <l:template name="May" text="May"/>
+    <l:template name="Jun" text="Haz"/>
+    <l:template name="Jul" text="Tem"/>
+    <l:template name="Aug" text="A&#287;u"/>
+    <l:template name="Sep" text="Eyl"/>
+    <l:template name="Oct" text="Eki"/>
+    <l:template name="Nov" text="Kas"/>
+    <l:template name="Dec" text="Ara"/>
+    <l:template name="Mon" text="Pzt"/>
+    <l:template name="Tue" text="Sal"/>
+    <l:template name="Wed" text="&#199;ar"/>
+    <l:template name="Thu" text="Per"/>
+    <l:template name="Fri" text="Cum"/>
+    <l:template name="Sat" text="Cts"/>
+    <l:template name="Sun" text="Paz"/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x041f Turkish"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/uk.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/uk.xml
new file mode 100644
index 00000000000..2d245a97764
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/uk.xml
@@ -0,0 +1,473 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="uk" english-language-name="Ukranian">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/uk.xml -->
+  <l:gentext key="Abstract" text="&#1040;&#1085;&#1086;&#1090;&#1072;&#1094;&#1110;&#1103;"/>
+  <l:gentext key="abstract" text="&#1040;&#1085;&#1086;&#1090;&#1072;&#1094;&#1110;&#1103;"/>
+  <l:gentext key="Answer" text="&#1042;:"/>
+  <l:gentext key="answer" text="&#1074;:"/>
+  <l:gentext key="Appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1086;&#1082;"/>
+  <l:gentext key="appendix" text="&#1076;&#1086;&#1076;&#1072;&#1090;&#1086;&#1082;"/>
+  <l:gentext key="Appendix.abr" text="&#1044;&#1086;&#1076;."/>
+  <l:gentext key="appendix.abr" text="&#1076;&#1086;&#1076;."/>
+  <l:gentext key="Article" text="&#1057;&#1090;&#1072;&#1090;&#1090;&#1103;"/>
+  <l:gentext key="article" text="&#1089;&#1090;&#1072;&#1090;&#1090;&#1103;"/>
+  <l:gentext key="Audience" text="&#1040;&#1091;&#1076;&#1080;&#1090;&#1086;&#1088;&#1110;&#1103;"/>
+  <l:gentext key="audience" text="&#1040;&#1091;&#1076;&#1080;&#1090;&#1086;&#1088;&#1110;&#1103;"/>
+  <l:gentext key="Bibliography" text="&#1051;&#1080;&#1090;&#1077;&#1088;&#1072;&#1090;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="bibliography" text="&#1083;&#1080;&#1090;&#1077;&#1088;&#1072;&#1090;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="Book" text="&#1050;&#1085;&#1080;&#1075;&#1072;"/>
+  <l:gentext key="book" text="&#1082;&#1085;&#1080;&#1075;&#1072;"/>
+  <l:gentext key="CAUTION" text="&#1047;&#1040;&#1057;&#1058;&#1045;&#1056;&#1045;&#1046;&#1045;&#1053;&#1053;&#1071;"/>
+  <l:gentext key="Caution" text="&#1047;&#1072;&#1089;&#1090;&#1077;&#1088;&#1077;&#1078;&#1077;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="caution" text="&#1079;&#1072;&#1089;&#1090;&#1077;&#1088;&#1077;&#1078;&#1077;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="Chapter" text="&#1056;&#1086;&#1079;&#1076;&#1110;&#1083;"/>
+  <l:gentext key="chapter" text="&#1088;&#1086;&#1079;&#1076;&#1110;&#1083;"/>
+  <l:gentext key="Chapter.abr" text="&#1056;&#1086;&#1079;&#1076;."/>
+  <l:gentext key="chapter.abr" text="&#1088;&#1086;&#1079;&#1076;."/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="&#1040;&#1074;&#1090;&#1086;&#1088;&#1089;&#1100;&#1082;&#1077; &#1087;&#1088;&#1072;&#1074;&#1086;"/>
+  <l:gentext key="copyright" text="&#1072;&#1074;&#1090;&#1086;&#1088;&#1089;&#1100;&#1082;&#1077; &#1087;&#1088;&#1072;&#1074;&#1086;"/>
+  <l:gentext key="Dedication" text="&#1055;&#1088;&#1080;&#1089;&#1074;&#1103;&#1095;&#1077;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="dedication" text="&#1087;&#1088;&#1080;&#1089;&#1074;&#1103;&#1095;&#1077;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="Edition" text="&#1042;&#1080;&#1076;&#1072;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="edition" text="&#1074;&#1080;&#1076;&#1072;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="Equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;"/>
+  <l:gentext key="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;"/>
+  <l:gentext key="Equation.abr" text="&#1060;."/>
+  <l:gentext key="equation.abr" text="&#1060;."/>
+  <l:gentext key="Example" text="&#1055;&#1088;&#1080;&#1082;&#1083;&#1072;&#1076;"/>
+  <l:gentext key="example" text="&#1087;&#1088;&#1080;&#1082;&#1083;&#1072;&#1076;"/>
+  <l:gentext key="Example.abr" text="&#1055;&#1088;&#1080;&#1082;&#1083;."/>
+  <l:gentext key="example.abr" text="&#1087;&#1088;&#1080;&#1082;&#1083;."/>
+  <l:gentext key="Figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082;"/>
+  <l:gentext key="figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082;"/>
+  <l:gentext key="Figure.abr" text="&#1056;&#1080;&#1089;."/>
+  <l:gentext key="figure.abr" text="&#1056;&#1080;&#1089;."/>
+  <l:gentext key="Glossary" text="&#1043;&#1083;&#1086;&#1089;&#1072;&#1088;&#1110;&#1081;"/>
+  <l:gentext key="glossary" text="&#1075;&#1083;&#1086;&#1089;&#1072;&#1088;&#1110;&#1081;"/>
+  <l:gentext key="GlossSee" text="&#1044;&#1080;&#1074;."/>
+  <l:gentext key="glosssee" text="&#1076;&#1080;&#1074;."/>
+  <l:gentext key="GlossSeeAlso" text="&#1044;&#1080;&#1074;. &#1090;&#1072;&#1082;&#1086;&#1078;"/>
+  <l:gentext key="glossSeeAlso" text="&#1076;&#1080;&#1074;. &#1090;&#1072;&#1082;&#1086;&#1078;"/>
+  <l:gentext key="glossseealso" text="&#1076;&#1080;&#1074;. &#1090;&#1072;&#1082;&#1086;&#1078;"/>
+  <l:gentext key="IMPORTANT" text="&#1042;&#1040;&#1046;&#1051;&#1048;&#1042;&#1054;"/>
+  <l:gentext key="Important" text="&#1042;&#1072;&#1078;&#1083;&#1080;&#1074;&#1086;"/>
+  <l:gentext key="important" text="&#1074;&#1072;&#1078;&#1083;&#1080;&#1074;&#1086;"/>
+  <l:gentext key="Index" text="&#1055;&#1088;&#1077;&#1076;&#1084;&#1077;&#1090;&#1085;&#1099;&#1081; &#1087;&#1086;&#1082;&#1072;&#1078;chcy;&#1080;&#1082;"/>
+  <l:gentext key="index" text="&#1087;&#1088;&#1077;&#1076;&#1084;&#1077;&#1090;&#1085;&#1099;&#1081; &#1087;&#1086;&#1082;&#1072;&#1078;chcy;&#1080;&#1082;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="&#1055;&#1088;&#1072;&#1074;&#1086;&#1074;&#1072; &#1087;&#1088;&#1080;&#1084;&#1110;&#1090;&#1082;&#1072;"/>
+  <l:gentext key="legalnotice" text="&#1087;&#1088;&#1072;&#1074;&#1086;&#1074;&#1072; &#1087;&#1088;&#1080;&#1084;&#1110;&#1090;&#1082;&#1072;"/>
+  <l:gentext key="Level" text="&#1056;&#1110;&#1074;&#1077;&#1085;&#1100;"/>
+  <l:gentext key="level" text="&#1088;&#1110;&#1074;&#1077;&#1085;&#1100;"/>
+  <l:gentext key="MsgAud" text="&#1040;&#1091;&#1076;&#1080;&#1090;&#1086;&#1088;&#1110;&#1103;"/>
+  <l:gentext key="msgaud" text="&#1072;&#1091;&#1076;&#1080;&#1090;&#1086;&#1088;&#1110;&#1103;"/>
+  <l:gentext key="MsgLevel" text="&#1056;&#1110;&#1074;&#1077;&#1085;&#1100;"/>
+  <l:gentext key="msglevel" text="&#1088;&#1110;&#1074;&#1077;&#1085;&#1100;"/>
+  <l:gentext key="MsgOrig" text="&#1044;&#1078;&#1077;&#1088;&#1077;&#1083;&#1086;"/>
+  <l:gentext key="msgorig" text="&#1076;&#1078;&#1077;&#1088;&#1077;&#1083;&#1086;"/>
+  <l:gentext key="Name" text="&#1030;&#1084;';&#1103;"/>
+  <l:gentext key="name" text="&#1110;&#1084;';&#1103;"/>
+  <l:gentext key="NOTE" text="&#1055;&#1056;&#1048;&#1052;&#1030;&#1058;&#1050;&#1040;"/>
+  <l:gentext key="Note" text="&#1055;&#1088;&#1080;&#1084;&#1110;&#1090;&#1082;&#1072;"/>
+  <l:gentext key="note" text="&#1087;&#1088;&#1080;&#1084;&#1110;&#1090;&#1082;&#1072;"/>
+  <l:gentext key="Origin" text="&#1044;&#1078;&#1077;&#1088;&#1077;&#1083;&#1086;"/>
+  <l:gentext key="origin" text="&#1076;&#1078;&#1077;&#1088;&#1077;&#1083;&#1086;"/>
+  <l:gentext key="Part" text="&#1063;&#1072;&#1089;&#1090;&#1080;&#1085;&#1072;"/>
+  <l:gentext key="part" text="&#1095;&#1072;&#1089;&#1090;&#1080;&#1085;&#1072;"/>
+  <l:gentext key="Part.abr" text="&#1063;."/>
+  <l:gentext key="part.abr" text="&#1063;."/>
+  <l:gentext key="Preface" text="&#1055;&#1077;&#1088;&#1077;&#1076;&#1084;&#1086;&#1074;&#1072;"/>
+  <l:gentext key="preface" text="&#1087;&#1077;&#1088;&#1077;&#1076;&#1084;&#1086;&#1074;&#1072;"/>
+  <l:gentext key="Procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;"/>
+  <l:gentext key="Procedure.abr" text="&#1055;&#1088;&#1086;&#1094;."/>
+  <l:gentext key="procedure.abr" text="&#1055;&#1088;&#1086;&#1094;."/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="&#1054;&#1087;&#1091;&#1073;&#1083;&#1110;&#1082;&#1086;&#1074;&#1072;&#1085;&#1086;"/>
+  <l:gentext key="published" text="&#1086;&#1087;&#1091;&#1073;&#1083;&#1110;&#1082;&#1086;&#1074;&#1072;&#1085;&#1086;"/>
+  <l:gentext key="Question" text="&#1055;"/>
+  <l:gentext key="question" text="&#1087;"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#1055;&#1086;&#1089;&#1080;&#1083;&#1072;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="reference" text="&#1087;&#1086;&#1089;&#1080;&#1083;&#1072;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="RefName" text="Name"/>
+  <l:gentext key="refname" text="Name"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#1050;&#1086;&#1088;&#1086;&#1090;&#1082;&#1080;&#1081; &#1086;&#1075;&#1083;&#1103;&#1076;"/>
+  <l:gentext key="refsynopsisdiv" text="&#1082;&#1086;&#1088;&#1086;&#1090;&#1082;&#1080;&#1081; &#1086;&#1075;&#1083;&#1103;&#1076;"/>
+  <l:gentext key="RevHistory" text="&#1054;&#1087;&#1080;&#1089; zcy;&#1084;&#1110;&#1085;"/>
+  <l:gentext key="revhistory" text="&#1086;&#1087;&#1080;&#1089; zcy;&#1084;&#1110;&#1085;"/>
+  <l:gentext key="Revision" text="&#1055;&#1077;&#1088;&#1077;&#1075;&#1083;&#1103;&#1076;"/>
+  <l:gentext key="revision" text="&#1087;&#1077;&#1088;&#1077;&#1075;&#1083;&#1103;&#1076;"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;"/>
+  <l:gentext key="section" text="&#1087;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;"/>
+  <l:gentext key="Section.abr" text="&#1055;&#1072;&#1088;."/>
+  <l:gentext key="section.abr" text="&#1087;&#1072;&#1088;."/>
+  <l:gentext key="See" text="&#1044;&#1080;&#1074;."/>
+  <l:gentext key="see" text="&#1076;&#1080;&#1074;."/>
+  <l:gentext key="SeeAlso" text="&#1044;&#1080;&#1074;. tcy;&#1072;&#1082;&#1086;&#1078;"/>
+  <l:gentext key="Seealso" text="&#1044;&#1080;&#1074;. tcy;&#1072;&#1082;&#1086;&#1078;"/>
+  <l:gentext key="seealso" text="&#1089;&#1080;&#1074;. tcy;&#1072;&#1082;&#1086;&#1078;"/>
+  <l:gentext key="Set" text="&#1042;&#1080;&#1073;&#1110;&#1088;&#1082;&#1072;"/>
+  <l:gentext key="set" text="&#1074;&#1080;&#1073;&#1110;&#1088;&#1082;&#1072;"/>
+  <l:gentext key="SetIndex" text="&#1048;&#1085;&#1076;&#1077;&#1082;&#1089; &#1074;&#1080;&#1073;&#1110;&#1088;&#1082;&#1080;"/>
+  <l:gentext key="setindex" text="&#1080;&#1085;&#1076;&#1077;&#1082;&#1089; &#1074;&#1080;&#1073;&#1110;&#1088;&#1082;&#1080;"/>
+  <l:gentext key="Sidebar" text="&#1042;&#1099;&#1076;&#1110;&#1083;&#1077;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="sidebar" text="&#1074;&#1099;&#1076;&#1110;&#1083;&#1077;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="Step" text="&#1050;&#1088;&#1086;&#1082;"/>
+  <l:gentext key="step" text="&#1082;&#1088;&#1086;&#1082;"/>
+  <l:gentext key="Table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1103;"/>
+  <l:gentext key="table" text="&#1090;&#1072;&#1073;&#1083;&#1080;&#1094;&#1103;"/>
+  <l:gentext key="Table.abr" text="&#1058;&#1072;&#1073;&#1083;."/>
+  <l:gentext key="table.abr" text="&#1090;&#1072;&#1073;&#1083;."/>
+  <l:gentext key="TIP" text="&#1055;&#1030;&#1044;&#1050;&#1040;&#1047;&#1050;&#1040;"/>
+  <l:gentext key="Tip" text="&#1055;&#1110;&#1076;&#1082;&#1072;&#1079;&#1082;&#1072;"/>
+  <l:gentext key="tip" text="&#1087;&#1110;&#1076;&#1082;&#1072;&#1079;&#1082;&#1072;"/>
+  <l:gentext key="WARNING" text="&#1047;&#1040;&#1057;&#1058;&#1045;&#1056;&#1045;&#1046;&#1045;&#1053;&#1053;&#1071;"/>
+  <l:gentext key="Warning" text="&#1047;&#1072;&#1089;&#1090;&#1077;&#1088;&#1077;&#1078;&#1077;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="warning" text="&#1079;&#1072;&#1089;&#1090;&#1077;&#1088;&#1077;&#1078;&#1077;&#1085;&#1085;&#1103;"/>
+  <l:gentext key="and" text=""/>
+  <l:gentext key="by" text=""/>
+  <l:gentext key="called" text=""/>
+  <l:gentext key="edited" text="&#1087;&#1080;&#1076; &#1088;&#1077;&#1076;&#1072;&#1082;&#1094;&#1110;&#1108;&#1102;"/>
+  <l:gentext key="Edited" text="&#1055;&#1080;&#1076; &#1088;&#1077;&#1076;&#1072;&#1082;&#1094;&#1110;&#1108;&#1102;"/>
+  <l:gentext key="Editedby" text="&#1055;&#1080;&#1076; &#1088;&#1077;&#1076;&#1072;&#1082;&#1094;&#1110;&#1108;&#1102;"/>
+  <l:gentext key="editedby" text="&#1087;&#1080;&#1076; &#1088;&#1077;&#1076;&#1072;&#1082;&#1094;&#1110;&#1108;&#1102;"/>
+  <l:gentext key="in" text="&#1074;"/>
+  <l:gentext key="TableofContents" text="&#1047;&#1084;&#1110;&#1089;&#1090;"/>
+  <l:gentext key="tableofcontents" text="&#1079;&#1084;&#1110;&#1089;&#1090;"/>
+  <l:gentext key="lastlistcomma" text="."/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="Notes" text="&#1055;&#1088;&#1080;&#1084;&#1110;&#1090;&#1082;&#1080;"/>
+  <l:gentext key="notes" text="&#1087;&#1088;&#1080;&#1084;&#1110;&#1090;&#1082;&#1080;"/>
+  <l:gentext key="TableNotes" text="&#1055;&#1088;&#1080;&#1084;&#1110;&#1090;&#1082;&#1080;"/>
+  <l:gentext key="tablenotes" text="&#1087;&#1088;&#1080;&#1084;&#1110;&#1090;&#1082;&#1080;"/>
+  <l:gentext key="nonexistantelement" text="non-existant element"/>
+  <l:gentext key="pgs" text="&#1089;&#1090;&#1086;&#1088;."/>
+  <l:gentext key="Pgs" text="&#1057;&#1090;&#1086;&#1088;."/>
+  <l:gentext key="Revisedby" text="&#1050;&#1086;&#1088;&#1077;&#1082;&#1090;&#1091;&#1088;&#1072;:;"/>
+  <l:gentext key="revisedby" text="&#1082;&#1086;&#1088;&#1077;&#1082;&#1090;&#1091;&#1088;&#1072;:;"/>
+  <l:gentext key="the" text=""/>
+  <l:gentext key="unexpectedelementname" text="unexpected element name"/>
+  <l:gentext key="unsupported" text="unsupported"/>
+  <l:gentext key="xrefto" text="xref to"/>
+  <l:gentext key="listofequations" text="&#1089;&#1087;&#1080;&#1089;&#1086;&#1082; &#1092;&#1086;&#1088;&#1084;&#1091;&#1083;"/>
+  <l:gentext key="ListofEquations" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1092;&#1086;&#1088;&#1084;&#1091;&#1083;"/>
+  <l:gentext key="ListofExamples" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1087;&#1088;&#1080;&#1082;&#1083;&#1072;&#1076;&#1110;&#1074;"/>
+  <l:gentext key="listofexamples" text="&#1089;&#1087;&#1080;&#1089;&#1086;&#1082; &#1087;&#1088;&#1080;&#1082;&#1083;&#1072;&#1076;&#1110;&#1074;"/>
+  <l:gentext key="ListofFigures" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1110;&#1083;&#1102;&#1089;&#1090;&#1088;&#1072;&#1094;&#1110;&#1081;"/>
+  <l:gentext key="listoffigures" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1110;&#1083;&#1102;&#1089;&#1090;&#1088;&#1072;&#1094;&#1110;&#1081;"/>
+  <l:gentext key="listoftables" text="&#1089;&#1087;&#1080;&#1089;&#1086;&#1082; &#1090;&#1072;&#1073;&#1083;&#1080;&#1094;&#1100;"/>
+  <l:gentext key="ListofTables" text="&#1057;&#1087;&#1080;&#1089;&#1086;&#1082; &#1090;&#1072;&#1073;&#1083;&#1080;&#1094;;&#1100;"/>
+  <l:gentext key="ListofUnknown" text="&#1053;&#1077;&#1074;&#1080;&#1079;&#1085;&#1072;&#1095;&#1077;&#1085;&#1080;&#1081; &#1089;&#1087;&#1080;&#1089;&#1086;&#1082;"/>
+  <l:gentext key="listofunknown" text="&#1085;&#1077;&#1074;&#1080;&#1079;&#1085;&#1072;&#1095;&#1077;&#1085;&#1080;&#1081; &#1089;&#1087;&#1080;&#1089;&#1086;&#1082;"/>
+  <l:gentext key="nav-next" text="&#1076;&#1072;&#1083;&#1110;"/>
+  <l:gentext key="nav-next-sibling" text="&#1076;&#1072;&#1083;&#1110; &#1087;&#1086; &#1088;&#1110;&#1074;&#1085;&#1102;"/>
+  <l:gentext key="nav-prev" text="&#1085;&#1072;&#1079;&#1072;&#1076;"/>
+  <l:gentext key="nav-prev-sibling" text="&#1085;&#1072;&#1079;&#1072;&#1076; &#1087;&#1086; &#1088;&#1110;&#1074;&#1085;&#1102;"/>
+  <l:gentext key="x-nav-next" text="&#1076;&#1072;&#1083;&#1110;"/>
+  <l:gentext key="nav-home" text="&#1055;&#1086;&#1095;&#1072;&#1090;&#1086;&#1082;"/>
+  <l:gentext key="nav-up" text="&#1044;&#1086;&#1075;&#1086;&#1088;&#1080;"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/uk.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1086;&#1082; %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#1056;&#1086;&#1079;&#1076;&#1110;&#1083; %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072; %n. %t"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1082;&#1083;&#1072;&#1076; %n. %t"/>
+    <l:template name="figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082; %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#1063;&#1072;&#1089;&#1090;&#1080;&#1085;&#1072; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1103; %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1086;&#1082; %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="&#1056;&#1086;&#1079;&#1076;&#1110;&#1083; %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#1042;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#1055;&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#1055;&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&#8220;%t&#8221;"/>
+    <l:template name="refsection" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="&#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#8220;%t&#8221;"/>
+    <l:template name="section" text="&#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="&#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#1042;:&#160;%n"/>
+    <l:template name="appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1086;&#1082;&#160;%n"/>
+    <l:template name="bridgehead" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n"/>
+    <l:template name="chapter" text="&#1056;&#1086;&#1079;&#1076;&#1110;&#1083;&#160;%n"/>
+    <l:template name="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;&#160;%n"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1082;&#1083;&#1072;&#1076;&#160;%n"/>
+    <l:template name="figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082;&#160;%n"/>
+    <l:template name="part" text="&#1063;&#1072;&#1089;&#1090;&#1080;&#1085;&#1072;&#160;%n"/>
+    <l:template name="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#1055;&#160;%n"/>
+    <l:template name="question" text="&#1055;&#160;%n"/>
+    <l:template name="sect1" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n"/>
+    <l:template name="sect2" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n"/>
+    <l:template name="sect3" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n"/>
+    <l:template name="sect4" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n"/>
+    <l:template name="sect5" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n"/>
+    <l:template name="section" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1103;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#1044;&#1086;&#1076;&#1072;&#1090;&#1086;&#1082;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="&#1056;&#1086;&#1079;&#1076;&#1110;&#1083;&#160;%n, %t"/>
+    <l:template name="equation" text="&#1060;&#1086;&#1088;&#1084;&#1091;&#1083;&#1072;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="&#1055;&#1088;&#1080;&#1082;&#1083;&#1072;&#1076;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="&#1056;&#1080;&#1089;&#1091;&#1085;&#1086;&#1082;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="&#1063;&#1072;&#1089;&#1090;&#1080;&#1085;&#1072;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="&#1055;&#1088;&#1086;&#1094;&#1077;&#1076;&#1091;&#1088;&#1072;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Production&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="&#1055;&#1072;&#1088;&#1072;&#1075;&#1088;&#1072;&#1092;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="the section called &#8220;%t&#8221;"/>
+    <l:template name="table" text="&#1058;&#1072;&#1073;&#1083;&#1080;&#1094;&#1103;&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text="  "/>
+    <l:template name="seplast" text=".  "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#1044;&#1080;&#1074;. "/>
+    <l:template name="seealso" text="&#1044;&#1080;&#1074;. &#1090;&#1072;&#1082;&#1086;&#1078; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#1040;&#1091;&#1076;&#1080;&#1090;&#1086;&#1088;&#1110;&#1103;: "/>
+    <l:template name="MsgLevel" text="&#1056;&#1110;&#1074;&#1077;&#1085;&#1100;: "/>
+    <l:template name="MsgOrig" text="&#1044;&#1078;&#1077;&#1088;&#1077;&#1083;&#1086;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0422 Ukrainian"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/vi.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/vi.xml
new file mode 100644
index 00000000000..2485b0a20e5
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/vi.xml
@@ -0,0 +1,442 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="vi" english-language-name="Vietnamese">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/vi.xml -->
+  <l:gentext key="Abstract" text="T&#7893;ng quan"/>
+  <l:gentext key="abstract" text="T&#7893;ng quan"/>
+  <l:gentext key="Answer" text="&#272;:"/>
+  <l:gentext key="answer" text="&#272;:"/>
+  <l:gentext key="Appendix" text="Ph&#7909; l&#7909;c"/>
+  <l:gentext key="appendix" text="ph&#7909; l&#7909;c"/>
+  <l:gentext key="Article" text="B&#224;i vi&#7871;t"/>
+  <l:gentext key="article" text="B&#224;i vi&#7871;t"/>
+  <l:gentext key="Bibliography" text="Th&#432; m&#7909;c"/>
+  <l:gentext key="bibliography" text="Th&#432; m&#7909;c"/>
+  <l:gentext key="Book" text="S&#225;ch"/>
+  <l:gentext key="book" text="S&#225;ch"/>
+  <l:gentext key="CAUTION" text="C&#7848;N TH&#7852;N"/>
+  <l:gentext key="Caution" text="C&#7849;n th&#7853;n"/>
+  <l:gentext key="caution" text="C&#7849;n th&#7853;n"/>
+  <l:gentext key="Chapter" text="Ch&#432;&#417;ng"/>
+  <l:gentext key="chapter" text="ch&#432;&#417;ng"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="B&#7843;n quy&#7873;n"/>
+  <l:gentext key="copyright" text="B&#7843;n quy&#7873;n"/>
+  <l:gentext key="Dedication" text="T&#7863;ng"/>
+  <l:gentext key="dedication" text="T&#7863;ng"/>
+  <l:gentext key="Edition" text="Edition"/>
+  <l:gentext key="edition" text="Edition"/>
+  <l:gentext key="Equation" text="Ph&#432;&#417;ng tr&#236;nh"/>
+  <l:gentext key="equation" text="Ph&#432;&#417;ng tr&#236;nh"/>
+  <l:gentext key="Example" text="V&#237; d&#7909;"/>
+  <l:gentext key="example" text="V&#237; d&#7909;"/>
+  <l:gentext key="Figure" text="H&#236;nh"/>
+  <l:gentext key="figure" text="H&#236;nh"/>
+  <l:gentext key="Glossary" text="Thu&#7853;t ng&#7919;"/>
+  <l:gentext key="glossary" text="Thu&#7853;t ng&#7919;"/>
+  <l:gentext key="GlossSee" text="Xem"/>
+  <l:gentext key="glosssee" text="Xem"/>
+  <l:gentext key="GlossSeeAlso" text="Xem th&#234;m"/>
+  <l:gentext key="glossseealso" text="Xem th&#234;m"/>
+  <l:gentext key="IMPORTANT" text="QUAN TR&#7884;NG"/>
+  <l:gentext key="important" text="Quan tr&#7885;ng"/>
+  <l:gentext key="Important" text="Quan tr&#7885;ng"/>
+  <l:gentext key="Index" text="Ch&#7881; m&#7909;c"/>
+  <l:gentext key="index" text="Ch&#7881; m&#7909;c"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="Legal Notice"/>
+  <l:gentext key="legalnotice" text="Legal Notice"/>
+  <l:gentext key="MsgAud" text="&#272;&#7885;c gi&#7843;"/>
+  <l:gentext key="msgaud" text="&#272;&#7885;c gi&#7843;"/>
+  <l:gentext key="MsgLevel" text="C&#7845;p"/>
+  <l:gentext key="msglevel" text="C&#7845;p"/>
+  <l:gentext key="MsgOrig" text="G&#7889;c"/>
+  <l:gentext key="msgorig" text="G&#7889;c"/>
+  <l:gentext key="NOTE" text="GHI CH&#218;"/>
+  <l:gentext key="Note" text="Ghi ch&#250;"/>
+  <l:gentext key="note" text="Ghi ch&#250;"/>
+  <l:gentext key="Part" text="Ph&#7847;n"/>
+  <l:gentext key="part" text="Ph&#7847;n"/>
+  <l:gentext key="Preface" text="M&#7903; &#273;&#7847;u"/>
+  <l:gentext key="preface" text="M&#7903; &#273;&#7847;u"/>
+  <l:gentext key="Procedure" text="Th&#7911; t&#7909;c"/>
+  <l:gentext key="procedure" text="Th&#7911; t&#7909;c"/>
+  <l:gentext key="ProductionSet" text="S&#7843;n ph&#7849;m"/>
+  <l:gentext key="Published" text="Xu&#7845;t b&#7843;n"/>
+  <l:gentext key="published" text="Xu&#7845;t b&#7843;n"/>
+  <l:gentext key="Question" text="H:"/>
+  <l:gentext key="question" text="H:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Tham kh&#7843;o"/>
+  <l:gentext key="reference" text="Tham kh&#7843;o"/>
+  <l:gentext key="RefName" text="T&#234;n"/>
+  <l:gentext key="refname" text="T&#234;n"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="T&#243;m t&#7855;t"/>
+  <l:gentext key="refsynopsisdiv" text="T&#243;m t&#7855;t"/>
+  <l:gentext key="RevHistory" text="Revision History"/>
+  <l:gentext key="revhistory" text="Revision History"/>
+  <l:gentext key="revision" text="B&#7843;n hi&#7879;u ch&#7881;nh"/>
+  <l:gentext key="Revision" text="B&#7843;n hi&#7879;u ch&#7881;nh"/>
+  <l:gentext key="sect1" text="Ph&#7847;n"/>
+  <l:gentext key="sect2" text="Ph&#7847;n"/>
+  <l:gentext key="sect3" text="Ph&#7847;n"/>
+  <l:gentext key="sect4" text="Ph&#7847;n"/>
+  <l:gentext key="sect5" text="Ph&#7847;n"/>
+  <l:gentext key="section" text="Ph&#7847;n"/>
+  <l:gentext key="Section" text="Ph&#7847;n"/>
+  <l:gentext key="see" text="xem"/>
+  <l:gentext key="seealso" text="xem th&#234;m"/>
+  <l:gentext key="set" text="&#272;&#7863;t"/>
+  <l:gentext key="Set" text="&#272;&#7863;t"/>
+  <l:gentext key="setindex" text="&#272;&#7863;t ch&#7881; m&#7909;c"/>
+  <l:gentext key="SetIndex" text="&#272;&#7863;t ch&#7881; m&#7909;c"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="thanh b&#234;n"/>
+  <l:gentext key="step" text="b&#432;&#7899;c"/>
+  <l:gentext key="Step" text="B&#432;&#7899;c"/>
+  <l:gentext key="Table" text="B&#7843;ng"/>
+  <l:gentext key="table" text="B&#7843;ng"/>
+  <l:gentext key="tip" text="M&#7865;o"/>
+  <l:gentext key="TIP" text="M&#7864;O"/>
+  <l:gentext key="Tip" text="M&#7865;o"/>
+  <l:gentext key="Warning" text="C&#7843;nh b&#225;o"/>
+  <l:gentext key="warning" text="C&#7843;nh b&#225;o"/>
+  <l:gentext key="WARNING" text="C&#7842;NH B&#193;O"/>
+  <l:gentext key="and" text="v&#224;"/>
+  <l:gentext key="by" text="b&#7903;i"/>
+  <l:gentext key="Edited" text="&#272;&#432;&#7907;c bi&#234;n so&#7841;n"/>
+  <l:gentext key="edited" text="&#272;&#432;&#7907;c bi&#234;n so&#7841;n"/>
+  <l:gentext key="Editedby" text="&#272;&#432;&#7907;c bi&#234;n so&#7841;n b&#7903;i"/>
+  <l:gentext key="editedby" text="&#272;&#432;&#7907;c bi&#234;n so&#7841;n b&#7903;i"/>
+  <l:gentext key="in" text="trong"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="ph&#7847;n t&#7917; kh&#244;ng c&#243;"/>
+  <l:gentext key="notes" text="Ghi ch&#250;"/>
+  <l:gentext key="Notes" text="Ghi ch&#250;"/>
+  <l:gentext key="Pgs" text="Pgs."/>
+  <l:gentext key="pgs" text="Pgs."/>
+  <l:gentext key="Revisedby" text="Hi&#7879;u ch&#7881;nh b&#7903;i: "/>
+  <l:gentext key="revisedby" text="Hi&#7879;u ch&#7881;nh b&#7903;i: "/>
+  <l:gentext key="TableNotes" text="Ghi ch&#250;"/>
+  <l:gentext key="tablenotes" text="Ghi ch&#250;"/>
+  <l:gentext key="TableofContents" text="M&#7909;c l&#7909;c"/>
+  <l:gentext key="tableofcontents" text="M&#7909;c l&#7909;c"/>
+  <l:gentext key="unexpectedelementname" text="T&#234;n ph&#7847;n t&#7917; kh&#244;ng &#273;&#250;ng"/>
+  <l:gentext key="unsupported" text="kh&#244;ng h&#7895; tr&#7907;"/>
+  <l:gentext key="xrefto" text="xref t&#7899;i"/>
+  <l:gentext key="listofequations" text="Danh s&#225;ch Ph&#432;&#417;ng tr&#236;nh"/>
+  <l:gentext key="ListofEquations" text="Danh s&#225;ch Ph&#432;&#417;ng tr&#236;nh"/>
+  <l:gentext key="ListofExamples" text="Danh s&#225;ch V&#237; d&#7909;"/>
+  <l:gentext key="listofexamples" text="Danh s&#225;ch V&#237; d&#7909;"/>
+  <l:gentext key="ListofFigures" text="Danh s&#225;ch H&#236;nh"/>
+  <l:gentext key="listoffigures" text="Danh s&#225;ch H&#236;nh"/>
+  <l:gentext key="listoftables" text="Danh s&#225;ch B&#7843;ng"/>
+  <l:gentext key="ListofTables" text="Danh s&#225;ch B&#7843;ng"/>
+  <l:gentext key="ListofUnknown" text="Danh s&#225;ch L&#7841;"/>
+  <l:gentext key="listofunknown" text="Danh s&#225;ch L&#7841;"/>
+  <l:gentext key="nav-home" text="&#272;&#7847;u"/>
+  <l:gentext key="nav-next" text="K&#7871; ti&#7871;p"/>
+  <l:gentext key="nav-next-sibling" text="T&#7899;i nhanh"/>
+  <l:gentext key="nav-prev" text="Tr&#432;&#7899;c &#273;&#243;"/>
+  <l:gentext key="nav-prev-sibling" text="L&#249;i nhanh"/>
+  <l:gentext key="nav-up" text="L&#234;n"/>
+  <l:gentext key="nav-toc" text="M&#7909;c l&#7909;c"/>
+  <l:gentext key="Draft" text="B&#7843;n th&#7843;o"/>
+  <l:gentext key="above" text="tr&#234;n"/>
+  <l:gentext key="below" text="d&#432;&#7899;i"/>
+  <l:gentext key="sectioncalled" text="ph&#7847;n"/>
+  <l:gentext key="index symbols" text="K&#253; hi&#7879;u"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/vi.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="last-first"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Ph&#7909; l&#7909;c&#160;%n.&#160;%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Ch&#432;&#417;ng&#160;%n.&#160;%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Ph&#432;&#417;ng tr&#236;nh&#160;%n.&#160;%t"/>
+    <l:template name="example" text="V&#237; d&#7909;&#160;%n.&#160;%t"/>
+    <l:template name="figure" text="H&#236;nh&#160;%n.&#160;%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Ph&#7847;n&#160;%n.&#160;%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Th&#7911; t&#7909;c&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="S&#7843;n ph&#7849;m&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="B&#7843;ng&#160;%n.&#160;%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Ph&#7909; l&#7909;c&#160;%n.&#160;%t"/>
+    <l:template name="bridgehead" text="%n.&#160;%t"/>
+    <l:template name="chapter" text="Ch&#432;&#417;ng&#160;%n.&#160;%t"/>
+    <l:template name="sect1" text="%n.&#160;%t"/>
+    <l:template name="sect2" text="%n.&#160;%t"/>
+    <l:template name="sect3" text="%n.&#160;%t"/>
+    <l:template name="sect4" text="%n.&#160;%t"/>
+    <l:template name="sect5" text="%n.&#160;%t"/>
+    <l:template name="section" text="%n.&#160;%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#272;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="H:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="H:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="section" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="ph&#7847;n &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#272;:&#160;%n"/>
+    <l:template name="appendix" text="Ph&#7909; l&#7909;c&#160;%n"/>
+    <l:template name="bridgehead" text="Ph&#7847;n&#160;%n"/>
+    <l:template name="chapter" text="Ch&#432;&#417;ng&#160;%n"/>
+    <l:template name="equation" text="Ph&#432;&#417;ng tr&#236;nh&#160;%n"/>
+    <l:template name="example" text="V&#237; d&#7909;&#160;%n"/>
+    <l:template name="figure" text="H&#236;nh&#160;%n"/>
+    <l:template name="part" text="Ph&#7847;n&#160;%n"/>
+    <l:template name="procedure" text="Th&#7911; t&#7909;c&#160;%n"/>
+    <l:template name="productionset" text="S&#7843;n ph&#7849;m&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="H:&#160;%n"/>
+    <l:template name="question" text="H:&#160;%n"/>
+    <l:template name="sect1" text="Ph&#7847;n&#160;%n"/>
+    <l:template name="sect2" text="Ph&#7847;n&#160;%n"/>
+    <l:template name="sect3" text="Ph&#7847;n&#160;%n"/>
+    <l:template name="sect4" text="Ph&#7847;n&#160;%n"/>
+    <l:template name="sect5" text="Ph&#7847;n&#160;%n"/>
+    <l:template name="section" text="Ph&#7847;n&#160;%n"/>
+    <l:template name="table" text="B&#7843;ng&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Ph&#7909; l&#7909;c&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Ph&#7847;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Ch&#432;&#417;ng&#160;%n, %t"/>
+    <l:template name="equation" text="Ph&#432;&#417;ng tr&#236;nh&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="V&#237; d&#7909;&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="H&#236;nh&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Ph&#7847;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Th&#7911; t&#7909;c&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="S&#7843;n ph&#7849;m&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Ph&#7847;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Ph&#7847;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Ph&#7847;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Ph&#7847;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Ph&#7847;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Ph&#7847;n&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="ph&#7847;n &#8220;%t&#8221;"/>
+    <l:template name="table" text="B&#7843;ng&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" v&#224; "/>
+    <l:template name="seplast" text=", v&#224; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Xem "/>
+    <l:template name="seealso" text="Xem th&#234;m "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#272;&#7885;c gi&#7843;: "/>
+    <l:template name="MsgLevel" text="C&#7845;p: "/>
+    <l:template name="MsgOrig" text="G&#7889;c: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x242a Vietnamese"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/xh.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/xh.xml
new file mode 100644
index 00000000000..1b47d7207a3
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/xh.xml
@@ -0,0 +1,441 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="xh" english-language-name="Xhosa">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/xh.xml -->
+  <l:gentext key="Abstract" text="Isiqalo"/>
+  <l:gentext key="abstract" text="Isiqalo"/>
+  <l:gentext key="Answer" text="I:"/>
+  <l:gentext key="answer" text="I:"/>
+  <l:gentext key="Appendix" text="Isivalo"/>
+  <l:gentext key="appendix" text="isivalo"/>
+  <l:gentext key="Article" text="Umba"/>
+  <l:gentext key="article" text="Umba"/>
+  <l:gentext key="Bibliography" text="Ezobunzululwazi"/>
+  <l:gentext key="bibliography" text="Ezobunzululwazi"/>
+  <l:gentext key="Book" text="Incwadi"/>
+  <l:gentext key="book" text="Incwadi"/>
+  <l:gentext key="CAUTION" text="ISILUMKISO"/>
+  <l:gentext key="Caution" text="Isilumkiso"/>
+  <l:gentext key="caution" text="Isilumkiso"/>
+  <l:gentext key="Chapter" text="Isiqendu"/>
+  <l:gentext key="chapter" text="isiqendu"/>
+  <l:gentext key="Colophon" text="Ikolophon"/>
+  <l:gentext key="colophon" text="Ikolophon"/>
+  <l:gentext key="Copyright" text="Ushicilelo olusemthethweni"/>
+  <l:gentext key="copyright" text="Ushicilelo olusemthethweni"/>
+  <l:gentext key="Dedication" text="Ulwaziso"/>
+  <l:gentext key="dedication" text="Ulwaziso"/>
+  <l:gentext key="Edition" text="Uhlelo"/>
+  <l:gentext key="edition" text="Uhlelo"/>
+  <l:gentext key="Equation" text="Ulinganiselo"/>
+  <l:gentext key="equation" text="Ulinganiselo"/>
+  <l:gentext key="Example" text="Umzekelo"/>
+  <l:gentext key="example" text="Umzekelo"/>
+  <l:gentext key="Figure" text="Ulungu"/>
+  <l:gentext key="figure" text="Ulungu"/>
+  <l:gentext key="Glossary" text="Inkcazelo yamagama"/>
+  <l:gentext key="glossary" text="Inkcazelo yamagama"/>
+  <l:gentext key="GlossSee" text="Bona"/>
+  <l:gentext key="glosssee" text="Bona"/>
+  <l:gentext key="GlossSeeAlso" text="Bona Kwakhona"/>
+  <l:gentext key="glossseealso" text="Bona Kwakhona"/>
+  <l:gentext key="IMPORTANT" text="IBALULEKILE"/>
+  <l:gentext key="important" text="Ibalulekile"/>
+  <l:gentext key="Important" text="Ibalulekile"/>
+  <l:gentext key="Index" text="Isalathiso"/>
+  <l:gentext key="index" text="Isalathiso"/>
+  <l:gentext key="ISBN" text="iISBN"/>
+  <l:gentext key="isbn" text="iISBN"/>
+  <l:gentext key="LegalNotice" text="Isaziso Esesimthethweni"/>
+  <l:gentext key="legalnotice" text="Isaziso Esesimthethweni"/>
+  <l:gentext key="MsgAud" text="Ababhali"/>
+  <l:gentext key="msgaud" text="Ababhali"/>
+  <l:gentext key="MsgLevel" text="Umphakamo"/>
+  <l:gentext key="msglevel" text="Umphakamo"/>
+  <l:gentext key="MsgOrig" text="Uqobo"/>
+  <l:gentext key="msgorig" text="Uqobo"/>
+  <l:gentext key="NOTE" text="QAPHELA"/>
+  <l:gentext key="Note" text="Qaphela"/>
+  <l:gentext key="note" text="Qaphela"/>
+  <l:gentext key="Part" text="Inxenye"/>
+  <l:gentext key="part" text="Inxenye"/>
+  <l:gentext key="Preface" text="Isihloko"/>
+  <l:gentext key="preface" text="Isihloko"/>
+  <l:gentext key="Procedure" text="Inkqubo"/>
+  <l:gentext key="procedure" text="Inkqubo"/>
+  <l:gentext key="ProductionSet" text="Imveliso"/>
+  <l:gentext key="Published" text="Ipapashwe"/>
+  <l:gentext key="published" text="Ipapashwe"/>
+  <l:gentext key="Question" text="U:"/>
+  <l:gentext key="question" text="U:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="Uthelekiso"/>
+  <l:gentext key="reference" text="Uthelekiso"/>
+  <l:gentext key="RefName" text="Igama lothelekiso"/>
+  <l:gentext key="refname" text="Igama lothelekiso"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="Isinopsisi"/>
+  <l:gentext key="refsynopsisdiv" text="Isinopsisi"/>
+  <l:gentext key="RevHistory" text="Imbali yophindo"/>
+  <l:gentext key="revhistory" text="Imbali yophindo"/>
+  <l:gentext key="revision" text="Iphindo"/>
+  <l:gentext key="Revision" text="Iphindo"/>
+  <l:gentext key="sect1" text="Icandelo"/>
+  <l:gentext key="sect2" text="Icandelo"/>
+  <l:gentext key="sect3" text="Icandelo"/>
+  <l:gentext key="sect4" text="Icandelo"/>
+  <l:gentext key="sect5" text="Icandelo"/>
+  <l:gentext key="section" text="Icandelo"/>
+  <l:gentext key="Section" text="Icandelo"/>
+  <l:gentext key="See" text="Bona"/>
+  <l:gentext key="see" text="Bona"/>
+  <l:gentext key="SeeAlso" text="Bona Kwakhona"/>
+  <l:gentext key="seealso" text="Bona Kwakhona"/>
+  <l:gentext key="Seealso" text="Bona Kwakhona"/>
+  <l:gentext key="set" text="Cwangcisa"/>
+  <l:gentext key="Set" text="Cwangcisa"/>
+  <l:gentext key="setindex" text="Cwangcisa Isalathiso"/>
+  <l:gentext key="SetIndex" text="Cwangcisa Isalathiso"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="ibar esecaleni"/>
+  <l:gentext key="step" text="inqwanqwa"/>
+  <l:gentext key="Step" text="Inqwanqwa"/>
+  <l:gentext key="Table" text="Indlela Yokwenza Imigca"/>
+  <l:gentext key="table" text="Indlela Yokwenza Imigca"/>
+  <l:gentext key="tip" text="Incam"/>
+  <l:gentext key="TIP" text="INCAM"/>
+  <l:gentext key="Tip" text="Incam"/>
+  <l:gentext key="Warning" text="Isilumkiso"/>
+  <l:gentext key="warning" text="Isilumkiso"/>
+  <l:gentext key="WARNING" text="ISILUMKISO"/>
+  <l:gentext key="and" text="no"/>
+  <l:gentext key="by" text="by"/>
+  <l:gentext key="Edited" text="Ihleliwe"/>
+  <l:gentext key="edited" text="Ihleliwe"/>
+  <l:gentext key="Editedby" text="Ihlelwe"/>
+  <l:gentext key="editedby" text="Ihlelwe"/>
+  <l:gentext key="in" text="in"/>
+  <l:gentext key="lastlistcomma" text=", "/>
+  <l:gentext key="listcomma" text=", "/>
+  <l:gentext key="nonexistantelement" text="isiqalelo esingekhayo"/>
+  <l:gentext key="notes" text="Iziqaphelo"/>
+  <l:gentext key="Notes" text="Iziqaphelo"/>
+  <l:gentext key="Pgs" text="Amaphepha"/>
+  <l:gentext key="pgs" text="Amaphepha"/>
+  <l:gentext key="Revisedby" text="Iphindwe ngu: "/>
+  <l:gentext key="revisedby" text="Iphindwe ngu:"/>
+  <l:gentext key="TableNotes" text="Iziqaphelo"/>
+  <l:gentext key="tablenotes" text="Iziqaphelo"/>
+  <l:gentext key="TableofContents" text="Imigca Yemixholo"/>
+  <l:gentext key="tableofcontents" text="Imigca Yemixholo"/>
+  <l:gentext key="unexpectedelementname" text="Igama lesiqalelo esingalindelwanga"/>
+  <l:gentext key="unsupported" text="ayixhaswanga"/>
+  <l:gentext key="xrefto" text="thelekiso ku"/>
+  <l:gentext key="listofequations" text="Uluhlu Lemilinganiselo"/>
+  <l:gentext key="ListofEquations" text="Uluhlu Lemilinganiselo"/>
+  <l:gentext key="ListofExamples" text="Uluhlu Lemizekelo"/>
+  <l:gentext key="listofexamples" text="Uluhlu Lemizekelo"/>
+  <l:gentext key="ListofFigures" text="Uluhlu Lamalungu"/>
+  <l:gentext key="listoffigures" text="Uluhlu Lamalungu"/>
+  <l:gentext key="listoftables" text="Uluhlu Lendlela Yokwenza Imigca"/>
+  <l:gentext key="ListofTables" text="Uluhlu Lendlela Yokwenza Imigca"/>
+  <l:gentext key="ListofUnknown" text="Uluhlu Lokungaziwayo"/>
+  <l:gentext key="listofunknown" text="Uluhlu Lokungaziwayo"/>
+  <l:gentext key="nav-home" text="Ikhaya"/>
+  <l:gentext key="nav-next" text="Elandelayo"/>
+  <l:gentext key="nav-next-sibling" text="Yisa Phambili"/>
+  <l:gentext key="nav-prev" text="Edlulileyo"/>
+  <l:gentext key="nav-prev-sibling" text="Yisa Emva"/>
+  <l:gentext key="nav-up" text="Phezulu"/>
+  <l:gentext key="sectioncalled" text="icandelo libizwa ngokuba"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Iimpawu"/>
+  <l:gentext key="lowercase.alpha" text="abcdefghijklmnopqrstuvwxyz"/>
+  <l:gentext key="uppercase.alpha" text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/xh.xml -->
+  <l:dingbat key="startquote" text="&#8220;"/>
+  <l:dingbat key="endquote" text="&#8221;"/>
+  <l:dingbat key="nestedstartquote" text="&#8216;"/>
+  <l:dingbat key="nestedendquote" text="&#8217;"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="Isivalo %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="Isiqendu %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="Ulinganiselo %n. %t"/>
+    <l:template name="example" text="Umzekelo %n. %t"/>
+    <l:template name="figure" text="Ulungu %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="Inxenye %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="Inkqubo %n. %t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Imveliso %n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsection" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="Indlela Yokwenza Imigca %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text=""/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="Isivalo %n. %t"/>
+    <l:template name="bridgehead" text="%n. %t"/>
+    <l:template name="chapter" text="Isiqendu %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsection" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="I:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="U:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="U:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="section" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="I:&#160;%n"/>
+    <l:template name="appendix" text="Isivalo&#160;%n"/>
+    <l:template name="bridgehead" text="Icandelo&#160;%n"/>
+    <l:template name="chapter" text="Isiqendu&#160;%n"/>
+    <l:template name="equation" text="Ulinganiselo&#160;%n"/>
+    <l:template name="example" text="Umzekelo&#160;%n"/>
+    <l:template name="figure" text="Ulungu&#160;%n"/>
+    <l:template name="part" text="Inxenye&#160;%n"/>
+    <l:template name="procedure" text="Inkqubo&#160;%n"/>
+    <l:template name="productionset" text="Imveliso&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="U:&#160;%n"/>
+    <l:template name="question" text="U:&#160;%n"/>
+    <l:template name="sect1" text="Icandelo&#160;%n"/>
+    <l:template name="sect2" text="Icandelo&#160;%n"/>
+    <l:template name="sect3" text="Icandelo&#160;%n"/>
+    <l:template name="sect4" text="Icandelo&#160;%n"/>
+    <l:template name="sect5" text="Icandelo&#160;%n"/>
+    <l:template name="section" text="Icandelo&#160;%n"/>
+    <l:template name="table" text="Indlela Yokwenza Imigca&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="Isivalo&#160;%n, %t"/>
+    <l:template name="bridgehead" text="Icandelo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="chapter" text="Isiqendu&#160;%n, %t"/>
+    <l:template name="equation" text="Ulinganiselo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="example" text="Umzekelo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="figure" text="Ulungu&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="part" text="Inxenye&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="procedure" text="Inkqubo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="productionset" text="Imveliso&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="refsect1" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="refsect2" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="refsect3" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="refsection" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="sect1" text="Icandelo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect2" text="Icandelo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect3" text="Icandelo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect4" text="Icandelo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="sect5" text="Icandelo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="section" text="Icandelo&#160;%n, &#8220;%t&#8221;"/>
+    <l:template name="simplesect" text="icandelo libizwa ngokuba &#8220;%t&#8221;"/>
+    <l:template name="table" text="Indlela Yokwenza Imigca&#160;%n, &#8220;%t&#8221;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=" no "/>
+    <l:template name="sep2" text=" no "/>
+    <l:template name="seplast" text=" no "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="Bona "/>
+    <l:template name="seealso" text="Bona Kwakhona "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="Ababhali: "/>
+    <l:template name="MsgLevel" text="Umphakamo: "/>
+    <l:template name="MsgOrig" text="Uqobo: "/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/zh_cn.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/zh_cn.xml
new file mode 100644
index 00000000000..6cd9e733a3e
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/zh_cn.xml
@@ -0,0 +1,438 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="zh_cn" english-language-name="Chinese (Continental)">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/zh_cn.xml -->
+  <l:gentext key="Abstract" text="&#25688;&#35201;"/>
+  <l:gentext key="abstract" text="&#25688;&#35201;"/>
+  <l:gentext key="Answer" text="&#31572;:"/>
+  <l:gentext key="answer" text="&#31572;:"/>
+  <l:gentext key="Appendix" text="&#38468;&#24405;"/>
+  <l:gentext key="appendix" text="&#38468;&#24405;"/>
+  <l:gentext key="Article" text="&#25991;&#31456;"/>
+  <l:gentext key="article" text="&#25991;&#31456;"/>
+  <l:gentext key="Bibliography" text="&#21442;&#32771;&#20070;&#30446;"/>
+  <l:gentext key="bibliography" text="&#21442;&#32771;&#20070;&#30446;"/>
+  <l:gentext key="Book" text="&#20070;&#30446;"/>
+  <l:gentext key="book" text="&#20070;&#30446;"/>
+  <l:gentext key="CAUTION" text="&#27880;&#24847;"/>
+  <l:gentext key="Caution" text="&#27880;&#24847;"/>
+  <l:gentext key="caution" text="&#27880;&#24847;"/>
+  <l:gentext key="Chapter" text="&#31456;"/>
+  <l:gentext key="chapter" text="&#31456;"/>
+  <l:gentext key="Colophon" text="Colophon"/>
+  <l:gentext key="colophon" text="Colophon"/>
+  <l:gentext key="Copyright" text="&#29256;&#26435;"/>
+  <l:gentext key="copyright" text="&#29256;&#26435;"/>
+  <l:gentext key="Dedication" text="&#22857;&#29486;"/>
+  <l:gentext key="dedication" text="&#22857;&#29486;"/>
+  <l:gentext key="Edition" text="&#29256;"/>
+  <l:gentext key="edition" text="&#29256;"/>
+  <l:gentext key="Equation" text="&#26041;&#31243;"/>
+  <l:gentext key="equation" text="&#26041;&#31243;"/>
+  <l:gentext key="Example" text="&#20363;&#23376;"/>
+  <l:gentext key="example" text="&#20363;&#23376;"/>
+  <l:gentext key="Figure" text="&#22270;&#24418;"/>
+  <l:gentext key="figure" text="&#22270;&#24418;"/>
+  <l:gentext key="Glossary" text="&#26415;&#35821;&#34920;"/>
+  <l:gentext key="glossary" text="&#26415;&#35821;&#34920;"/>
+  <l:gentext key="GlossSee" text="&#35265;"/>
+  <l:gentext key="glosssee" text="&#35265;"/>
+  <l:gentext key="GlossSeeAlso" text="&#21478;&#35265;"/>
+  <l:gentext key="glossseealso" text="&#21478;&#35265;"/>
+  <l:gentext key="IMPORTANT" text="&#37325;&#35201;"/>
+  <l:gentext key="Important" text="&#37325;&#35201;"/>
+  <l:gentext key="important" text="&#37325;&#35201;"/>
+  <l:gentext key="Index" text="&#32034;&#24341;"/>
+  <l:gentext key="index" text="&#32034;&#24341;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="&#27861;&#24459;&#24067;&#21578;"/>
+  <l:gentext key="legalnotice" text="&#27861;&#24459;&#24067;&#21578;"/>
+  <l:gentext key="MsgAud" text="&#35835;&#32773;"/>
+  <l:gentext key="msgaud" text="&#35835;&#32773;"/>
+  <l:gentext key="MsgLevel" text="&#38590;&#24230;"/>
+  <l:gentext key="msglevel" text="&#38590;&#24230;"/>
+  <l:gentext key="MsgOrig" text="&#20986;&#22788;"/>
+  <l:gentext key="msgorig" text="&#20986;&#22788;"/>
+  <l:gentext key="NOTE" text="&#27880;"/>
+  <l:gentext key="Note" text="&#27880;"/>
+  <l:gentext key="note" text="&#27880;"/>
+  <l:gentext key="Part" text="&#37096;&#20998;"/>
+  <l:gentext key="part" text="&#37096;&#20998;"/>
+  <l:gentext key="Preface" text="&#21069;&#35328;"/>
+  <l:gentext key="preface" text="&#21069;&#35328;"/>
+  <l:gentext key="Procedure" text="&#36807;&#31243;"/>
+  <l:gentext key="procedure" text="&#36807;&#31243;"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="&#20986;&#29256;"/>
+  <l:gentext key="published" text="&#20986;&#29256;"/>
+  <l:gentext key="Question" text="&#38382;:"/>
+  <l:gentext key="question" text="&#38382;:"/>
+  <l:gentext key="RefEntry" text=""/>
+  <l:gentext key="refentry" text=""/>
+  <l:gentext key="Reference" text="&#21442;&#32771;"/>
+  <l:gentext key="reference" text="&#21442;&#32771;"/>
+  <l:gentext key="RefName" text="&#21517;&#23383;"/>
+  <l:gentext key="refname" text="&#21517;&#23383;"/>
+  <l:gentext key="RefSection" text=""/>
+  <l:gentext key="refsection" text=""/>
+  <l:gentext key="RefSynopsisDiv" text="&#22823;&#32434;"/>
+  <l:gentext key="refsynopsisdiv" text="&#22823;&#32434;"/>
+  <l:gentext key="RevHistory" text="&#20462;&#35746;&#21382;&#21490;"/>
+  <l:gentext key="revhistory" text="&#20462;&#35746;&#21382;&#21490;"/>
+  <l:gentext key="Revision" text="&#20462;&#35746;"/>
+  <l:gentext key="revision" text="&#20462;&#35746;"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="&#33410;"/>
+  <l:gentext key="section" text="&#33410;"/>
+  <l:gentext key="See" text="&#35265;"/>
+  <l:gentext key="see" text="&#35265;"/>
+  <l:gentext key="SeeAlso" text="&#21478;&#35265;"/>
+  <l:gentext key="Seealso" text="&#21478;&#35265;"/>
+  <l:gentext key="seealso" text="&#21478;&#35265;"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="SetIndex" text="Set Index"/>
+  <l:gentext key="setindex" text="Set Index"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text="sidebar"/>
+  <l:gentext key="Step" text="&#27493;&#39588;"/>
+  <l:gentext key="step" text="&#27493;&#39588;"/>
+  <l:gentext key="Table" text="&#34920;&#26684;"/>
+  <l:gentext key="table" text="&#34920;&#26684;"/>
+  <l:gentext key="TIP" text="&#25552;&#31034;"/>
+  <l:gentext key="Tip" text="&#25552;&#31034;"/>
+  <l:gentext key="tip" text="&#25552;&#31034;"/>
+  <l:gentext key="WARNING" text="&#35686;&#21578;"/>
+  <l:gentext key="Warning" text="&#35686;&#21578;"/>
+  <l:gentext key="warning" text="&#35686;&#21578;"/>
+  <l:gentext key="and" text="&#21644;"/>
+  <l:gentext key="by" text="&#30001;"/>
+  <l:gentext key="Edited" text="&#32534;&#36753;"/>
+  <l:gentext key="edited" text="&#32534;&#36753;"/>
+  <l:gentext key="Editedby" text="&#32534;&#36753;"/>
+  <l:gentext key="editedby" text="&#32534;&#36753;"/>
+  <l:gentext key="in" text="&#22312;"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="&#19981;&#23384;&#22312;&#30340;&#20803;&#32032;"/>
+  <l:gentext key="Notes" text="&#27880;"/>
+  <l:gentext key="notes" text="&#27880;"/>
+  <l:gentext key="Pgs" text="&#39029;"/>
+  <l:gentext key="pgs" text="&#39029;"/>
+  <l:gentext key="Revisedby" text="&#20462;&#35746;"/>
+  <l:gentext key="revisedby" text="&#20462;&#35746;"/>
+  <l:gentext key="TableNotes" text="&#27880;"/>
+  <l:gentext key="tablenotes" text="&#27880;"/>
+  <l:gentext key="TableofContents" text="&#30446;&#24405;"/>
+  <l:gentext key="tableofcontents" text="&#30446;&#24405;"/>
+  <l:gentext key="unexpectedelementname" text="&#26410;&#39044;&#26009;&#21040;&#30340;&#20803;&#32032;&#21517;"/>
+  <l:gentext key="unsupported" text="&#19981;&#25903;&#25345;"/>
+  <l:gentext key="xrefto" text="&#21442;&#29031;"/>
+  <l:gentext key="ListofEquations" text="&#26041;&#31243;&#24335;&#21015;&#34920;"/>
+  <l:gentext key="listofequations" text="&#26041;&#31243;&#24335;&#21015;&#34920;"/>
+  <l:gentext key="ListofExamples" text="&#31034;&#20363;&#21015;&#34920;"/>
+  <l:gentext key="listofexamples" text="&#31034;&#20363;&#21015;&#34920;"/>
+  <l:gentext key="ListofFigures" text="&#22270;&#24418;&#21015;&#34920;"/>
+  <l:gentext key="listoffigures" text="&#22270;&#24418;&#21015;&#34920;"/>
+  <l:gentext key="ListofTables" text="&#34920;&#26684;&#21015;&#34920;"/>
+  <l:gentext key="listoftables" text="&#34920;&#26684;&#21015;&#34920;"/>
+  <l:gentext key="ListofUnknown" text="&#20854;&#20182;&#20869;&#23481;&#21015;&#34920;"/>
+  <l:gentext key="listofunknown" text="&#20854;&#20182;&#20869;&#23481;&#21015;&#34920;"/>
+  <l:gentext key="nav-home" text="&#36215;&#28857;"/>
+  <l:gentext key="nav-next" text="&#21069;&#36827;"/>
+  <l:gentext key="nav-next-sibling" text="&#24555;&#36895;&#21069;&#36827;"/>
+  <l:gentext key="nav-prev" text="&#21518;&#36864;"/>
+  <l:gentext key="nav-prev-sibling" text="&#24555;&#36895;&#21518;&#36864;"/>
+  <l:gentext key="nav-up" text="&#19978;&#19968;&#32423;"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/zh_cn.xml -->
+  <l:dingbat key="startquote" text="&quot;"/>
+  <l:dingbat key="endquote" text="&quot;"/>
+  <l:dingbat key="nestedstartquote" text="'"/>
+  <l:dingbat key="nestedendquote" text="'"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#38468;&#24405; %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#31456; %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#26041;&#31243; %n. %t"/>
+    <l:template name="example" text="&#20363;&#23376; %n. %t"/>
+    <l:template name="figure" text="&#22270;&#24418; %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#37096;&#20998; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#36807;&#31243;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#34920;&#26684; %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#38468;&#24405; %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="&#31456; %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#31572;:&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#38382;:&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#38382;:&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&quot;%t&quot;"/>
+    <l:template name="refsect1" text="&quot;%t&quot;"/>
+    <l:template name="refsect2" text="&quot;%t&quot;"/>
+    <l:template name="refsect3" text="&quot;%t&quot;"/>
+    <l:template name="sect1" text="&quot;%t&quot;"/>
+    <l:template name="sect2" text="&quot;%t&quot;"/>
+    <l:template name="sect3" text="&quot;%t&quot;"/>
+    <l:template name="sect4" text="&quot;%t&quot;"/>
+    <l:template name="sect5" text="&quot;%t&quot;"/>
+    <l:template name="section" text="&quot;%t&quot;"/>
+    <l:template name="simplesect" text="&quot;%t&quot;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#31572;:&#160;%n"/>
+    <l:template name="appendix" text="&#38468;&#24405;&#160;%n"/>
+    <l:template name="bridgehead" text="&#33410;&#160;%n"/>
+    <l:template name="chapter" text="&#31456;&#160;%n"/>
+    <l:template name="equation" text="&#26041;&#31243;&#160;%n"/>
+    <l:template name="example" text="&#20363;&#23376;&#160;%n"/>
+    <l:template name="figure" text="&#22270;&#24418;&#160;%n"/>
+    <l:template name="part" text="&#37096;&#20998;&#160;%n"/>
+    <l:template name="procedure" text="&#36807;&#31243;&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#38382;:&#160;%n"/>
+    <l:template name="question" text="&#38382;:&#160;%n"/>
+    <l:template name="sect1" text="&#33410;&#160;%n"/>
+    <l:template name="sect2" text="&#33410;&#160;%n"/>
+    <l:template name="sect3" text="&#33410;&#160;%n"/>
+    <l:template name="sect4" text="&#33410;&#160;%n"/>
+    <l:template name="sect5" text="&#33410;&#160;%n"/>
+    <l:template name="section" text="&#33410;&#160;%n"/>
+    <l:template name="table" text="&#34920;&#26684;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#38468;&#24405;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#33410;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="chapter" text="&#31456;&#160;%n, %t"/>
+    <l:template name="equation" text="&#26041;&#31243;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="example" text="&#20363;&#23376;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="figure" text="&#22270;&#24418;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="part" text="&#37096;&#20998;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="procedure" text="&#36807;&#31243;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="productionset" text="Production&#160;%n, &quot;%t&quot;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &quot;%t&quot;"/>
+    <l:template name="refsect1" text="the section called &quot;%t&quot;"/>
+    <l:template name="refsect2" text="the section called &quot;%t&quot;"/>
+    <l:template name="refsect3" text="the section called &quot;%t&quot;"/>
+    <l:template name="refsection" text="the section called &quot;%t&quot;"/>
+    <l:template name="sect1" text="&#33410;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="sect2" text="&#33410;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="sect3" text="&#33410;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="sect4" text="&#33410;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="sect5" text="&#33410;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="section" text="&#33410;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="simplesect" text="the section called &quot;%t&quot;"/>
+    <l:template name="table" text="&#34920;&#26684;&#160;%n, &quot;%t&quot;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#21644; "/>
+    <l:template name="seplast" text=", &#21644; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#35265; "/>
+    <l:template name="seealso" text="&#21478;&#35265; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#35835;&#32773;: "/>
+    <l:template name="MsgLevel" text="&#38590;&#24230;: "/>
+    <l:template name="MsgOrig" text="&#20986;&#22788;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0804 Chinese (CHINA)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/common/zh_tw.xml b/docs-xml/xslt/db2latex-xsl/xsl/common/zh_tw.xml
new file mode 100644
index 00000000000..42b3e1b513a
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/common/zh_tw.xml
@@ -0,0 +1,439 @@
+<?xml version="1.0" encoding="us-ascii"?>
+<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="zh_tw" english-language-name="Chinese (Traditional)">
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<!-- -->
+<!-- Any further gentexts were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/zh_tw.xml -->
+  <l:gentext key="Abstract" text="&#25688;&#35201;"/>
+  <l:gentext key="abstract" text="&#25688;&#35201;"/>
+  <l:gentext key="Answer" text="&#31572;&#65306;"/>
+  <l:gentext key="answer" text="&#31572;&#65306;"/>
+  <l:gentext key="Appendix" text="&#38468;&#37636;"/>
+  <l:gentext key="appendix" text="&#38468;&#37636;"/>
+  <l:gentext key="Article" text="&#25991;&#31456;"/>
+  <l:gentext key="article" text="&#25991;&#31456;"/>
+  <l:gentext key="Bibliography" text="&#21443;&#32771;&#25991;&#29563;"/>
+  <l:gentext key="bibliography" text="&#21443;&#32771;&#25991;&#29563;"/>
+  <l:gentext key="Book" text="&#26360;&#30446;"/>
+  <l:gentext key="book" text="&#26360;&#30446;"/>
+  <l:gentext key="CAUTION" text="&#27880;&#24847;"/>
+  <l:gentext key="Caution" text="&#27880;&#24847;"/>
+  <l:gentext key="caution" text="&#27880;&#24847;"/>
+  <l:gentext key="Chapter" text="&#31456;"/>
+  <l:gentext key="chapter" text="&#31456;"/>
+  <l:gentext key="Colophon" text="&#29256;&#26412;&#35352;&#37636;"/>
+  <l:gentext key="colophon" text="&#29256;&#26412;&#35352;&#37636;"/>
+  <l:gentext key="Copyright" text="&#29256;&#27402;"/>
+  <l:gentext key="copyright" text="&#29256;&#27402;"/>
+  <l:gentext key="Dedication" text="&#22857;&#29563;"/>
+  <l:gentext key="dedication" text="&#22857;&#29563;"/>
+  <l:gentext key="Edition" text="&#29256;"/>
+  <l:gentext key="edition" text="&#29256;"/>
+  <l:gentext key="Equation" text="&#26041;&#31243;&#24335;"/>
+  <l:gentext key="equation" text="&#26041;&#31243;&#24335;"/>
+  <l:gentext key="Example" text="&#31684;&#20363;"/>
+  <l:gentext key="example" text="&#31684;&#20363;"/>
+  <l:gentext key="Figure" text="&#22294;&#24418;"/>
+  <l:gentext key="figure" text="&#22294;&#24418;"/>
+  <l:gentext key="Glossary" text="&#23567;&#36781;&#24409;"/>
+  <l:gentext key="glossary" text="&#23567;&#36781;&#24409;"/>
+  <l:gentext key="GlossSee" text="&#21443;&#35211;"/>
+  <l:gentext key="glosssee" text="&#21443;&#35211;"/>
+  <l:gentext key="GlossSeeAlso" text="&#21478;&#21443;&#35211;"/>
+  <l:gentext key="glossseealso" text="&#21478;&#21443;&#35211;"/>
+  <l:gentext key="IMPORTANT" text="&#37325;&#35201;"/>
+  <l:gentext key="Important" text="&#37325;&#35201;"/>
+  <l:gentext key="important" text="&#37325;&#35201;"/>
+  <l:gentext key="Index" text="&#32034;&#24341;"/>
+  <l:gentext key="index" text="&#32034;&#24341;"/>
+  <l:gentext key="ISBN" text="ISBN"/>
+  <l:gentext key="isbn" text="ISBN"/>
+  <l:gentext key="LegalNotice" text="&#27861;&#24459;&#32882;&#26126;"/>
+  <l:gentext key="legalnotice" text="&#27861;&#24459;&#32882;&#26126;"/>
+  <l:gentext key="MsgAud" text="&#35712;&#32773;"/>
+  <l:gentext key="msgaud" text="&#35712;&#32773;"/>
+  <l:gentext key="MsgLevel" text="&#31243;&#24230;"/>
+  <l:gentext key="msglevel" text="&#31243;&#24230;"/>
+  <l:gentext key="MsgOrig" text="&#20986;&#34389;"/>
+  <l:gentext key="msgorig" text="&#20986;&#34389;"/>
+  <l:gentext key="NOTE" text="&#27880;"/>
+  <l:gentext key="Note" text="&#27880;"/>
+  <l:gentext key="note" text="&#27880;"/>
+  <l:gentext key="Part" text="&#37096;"/>
+  <l:gentext key="part" text="&#37096;"/>
+  <l:gentext key="Preface" text="&#24207;&#35328;"/>
+  <l:gentext key="preface" text="&#24207;&#35328;"/>
+  <l:gentext key="Procedure" text="&#36942;&#31243;"/>
+  <l:gentext key="procedure" text="&#36942;&#31243;"/>
+  <l:gentext key="ProductionSet" text="Production"/>
+  <l:gentext key="Published" text="&#20986;&#29256;"/>
+  <l:gentext key="published" text="&#20986;&#29256;"/>
+  <l:gentext key="Question" text="&#21839;&#65306;"/>
+  <l:gentext key="question" text="&#21839;&#65306;"/>
+  <l:gentext key="RefEntry" text="&#21443;&#29031;&#38917;&#30446;"/>
+  <l:gentext key="refentry" text="&#21443;&#29031;&#38917;&#30446;"/>
+  <l:gentext key="Reference" text="&#21443;&#32771;"/>
+  <l:gentext key="reference" text="&#21443;&#32771;"/>
+  <l:gentext key="RefName" text="&#21443;&#32771;&#21517;"/>
+  <l:gentext key="refname" text="&#21443;&#32771;&#21517;"/>
+  <l:gentext key="RefSection" text="&#21443;&#29031;&#31456;&#31680;"/>
+  <l:gentext key="refsection" text="&#21443;&#29031;&#31456;&#31680;"/>
+  <l:gentext key="RefSynopsisDiv" text="&#22823;&#32177;"/>
+  <l:gentext key="refsynopsisdiv" text="&#22823;&#32177;"/>
+  <l:gentext key="RevHistory" text="&#20462;&#35330;&#35352;&#37636;"/>
+  <l:gentext key="revhistory" text="&#20462;&#35330;&#35352;&#37636;"/>
+  <l:gentext key="Revision" text="&#20462;&#35330;"/>
+  <l:gentext key="revision" text="&#20462;&#35330;"/>
+  <l:gentext key="sect1" text="Section"/>
+  <l:gentext key="sect2" text="Section"/>
+  <l:gentext key="sect3" text="Section"/>
+  <l:gentext key="sect4" text="Section"/>
+  <l:gentext key="sect5" text="Section"/>
+  <l:gentext key="Section" text="&#31680;"/>
+  <l:gentext key="section" text="&#31680;"/>
+  <l:gentext key="See" text="&#35211;"/>
+  <l:gentext key="see" text="&#35211;"/>
+  <l:gentext key="SeeAlso" text="&#21478;&#35211;"/>
+  <l:gentext key="Seealso" text="&#21478;&#35211;"/>
+  <l:gentext key="seealso" text="&#21478;&#35211;"/>
+  <l:gentext key="Set" text="Set"/>
+  <l:gentext key="set" text="Set"/>
+  <l:gentext key="SetIndex" text="Set Index"/>
+  <l:gentext key="setindex" text="Set Index"/>
+  <l:gentext key="Sidebar" text=""/>
+  <l:gentext key="sidebar" text=""/>
+  <l:gentext key="Step" text="&#27493;&#39519;"/>
+  <l:gentext key="step" text="&#27493;&#39519;"/>
+  <l:gentext key="Table" text="&#34920;&#26684;"/>
+  <l:gentext key="table" text="&#34920;&#26684;"/>
+  <l:gentext key="TIP" text="&#25552;&#31034;"/>
+  <l:gentext key="Tip" text="&#25552;&#31034;"/>
+  <l:gentext key="tip" text="&#25552;&#31034;"/>
+  <l:gentext key="WARNING" text="&#35686;&#21578;"/>
+  <l:gentext key="Warning" text="&#35686;&#21578;"/>
+  <l:gentext key="warning" text="&#35686;&#21578;"/>
+  <l:gentext key="edited" text="&#32232;&#36655;"/>
+  <l:gentext key="Edited" text="&#32232;&#36655;"/>
+  <l:gentext key="editedby" text="&#32232;&#36655;"/>
+  <l:gentext key="Editedby" text="&#32232;&#36655;"/>
+  <l:gentext key="Notes" text="&#27880;"/>
+  <l:gentext key="notes" text="&#27880;"/>
+  <l:gentext key="Pgs" text="&#38913;"/>
+  <l:gentext key="pgs" text="&#38913;"/>
+  <l:gentext key="Revisedby" text="&#20462;&#35330;"/>
+  <l:gentext key="revisedby" text="&#20462;&#35330;"/>
+  <l:gentext key="TableNotes" text="&#27880;&#37323;"/>
+  <l:gentext key="tablenotes" text="&#27880;&#37323;"/>
+  <l:gentext key="TableofContents" text="&#20839;&#23481;&#30446;&#37636;"/>
+  <l:gentext key="tableofcontents" text="&#20839;&#23481;&#30446;&#37636;"/>
+  <l:gentext key="and" text="&#19988;"/>
+  <l:gentext key="by" text="&#30001;"/>
+  <l:gentext key="in" text="&#22312;"/>
+  <l:gentext key="lastlistcomma" text=","/>
+  <l:gentext key="listcomma" text=","/>
+  <l:gentext key="nonexistantelement" text="&#19981;&#23384;&#22312;&#30340;&#20803;&#32032;"/>
+  <l:gentext key="page.citation" text="&#38913;"/>
+  <l:gentext key="unexpectedelementname" text="&#38750;&#38928;&#26399;&#30340;&#20803;&#32032;&#21517;"/>
+  <l:gentext key="unsupported" text="&#26410;&#25903;&#25588;"/>
+  <l:gentext key="xrefto" text="&#21443;&#29031;"/>
+  <l:gentext key="ListofEquations" text="&#20844;&#24335;&#30446;&#37636;"/>
+  <l:gentext key="listofequations" text="&#20844;&#24335;&#30446;&#37636;"/>
+  <l:gentext key="ListofExamples" text="&#31684;&#20363;&#30446;&#37636;"/>
+  <l:gentext key="listofexamples" text="&#31684;&#20363;&#30446;&#37636;"/>
+  <l:gentext key="ListofFigures" text="&#38468;&#22294;&#30446;&#37636;"/>
+  <l:gentext key="listoffigures" text="&#38468;&#22294;&#30446;&#37636;"/>
+  <l:gentext key="ListofTables" text="&#38468;&#34920;&#30446;&#37636;"/>
+  <l:gentext key="listoftables" text="&#38468;&#34920;&#30446;&#37636;"/>
+  <l:gentext key="ListofUnknown" text="&#20854;&#23427;&#20839;&#23481;&#30446;&#37636;"/>
+  <l:gentext key="listofunknown" text="&#20854;&#23427;&#20839;&#23481;&#30446;&#37636;"/>
+  <l:gentext key="nav-home" text="&#20839;&#23481;"/>
+  <l:gentext key="nav-next" text="&#19979;&#19968;&#38913;"/>
+  <l:gentext key="nav-next-sibling" text="&#24555;&#36895;&#21521;&#24460;"/>
+  <l:gentext key="nav-prev" text="&#21069;&#19968;&#38913;"/>
+  <l:gentext key="nav-prev-sibling" text="&#24555;&#36895;&#21521;&#21069;"/>
+  <l:gentext key="nav-up" text="&#19978;&#19968;&#23652;"/>
+  <l:gentext key="sectioncalled" text="the section called"/>
+  <l:gentext key="Draft" text="Draft"/>
+  <l:gentext key="above" text="above"/>
+  <l:gentext key="below" text="below"/>
+  <l:gentext key="index symbols" text="Symbols"/>
+<!-- Any further dingbats were selectively imported from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/docbook/gentext/locale/zh_tw.xml -->
+  <l:dingbat key="startquote" text="&quot;"/>
+  <l:dingbat key="endquote" text="&quot;"/>
+  <l:dingbat key="nestedstartquote" text="'"/>
+  <l:dingbat key="nestedendquote" text="'"/>
+  <l:dingbat key="bullet" text="&#8226;"/>
+<!-- Any further contexts were found only in the "other" file. -->
+  <l:context name="styles">
+    <l:template name="person-name" text="first-last"/>
+  </l:context>
+  <l:context name="title">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="%t"/>
+    <l:template name="appendix" text="&#38468;&#37636; %n. %t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="biblioentry" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomixed" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="&#31456; %n. %t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="&#26041;&#31243;&#24335; %n. %t"/>
+    <l:template name="example" text="&#31684;&#20363; %n. %t"/>
+    <l:template name="figure" text="&#22294;&#24418; %n. %t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text=""/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="&#37096; %n. %t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="procedure.formal" text="&#36942;&#31243;&#160;%n.&#160;%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="productionset.formal" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="%t"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="%t"/>
+    <l:template name="refentry" text="%t"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsect1" text="%t"/>
+    <l:template name="refsect2" text="%t"/>
+    <l:template name="refsect3" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="refsynopsisdivinfo" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="step" text="%t"/>
+    <l:template name="table" text="&#34920;&#26684; %n. %t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="warning" text="%t"/>
+  </l:context>
+  <l:context name="title-unnumbered">
+    <l:template name="appendix" text="%t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="sect1" text="%t"/>
+    <l:template name="sect2" text="%t"/>
+    <l:template name="sect3" text="%t"/>
+    <l:template name="sect4" text="%t"/>
+    <l:template name="sect5" text="%t"/>
+    <l:template name="section" text="%t"/>
+    <l:template name="simplesect" text="%t"/>
+  </l:context>
+  <l:context name="title-numbered">
+    <l:template name="appendix" text="&#38468;&#37636; %n. %t"/>
+    <l:template name="bridgehead" text="%t"/>
+    <l:template name="chapter" text="&#31456; %n. %t"/>
+    <l:template name="sect1" text="%n. %t"/>
+    <l:template name="sect2" text="%n. %t"/>
+    <l:template name="sect3" text="%n. %t"/>
+    <l:template name="sect4" text="%n. %t"/>
+    <l:template name="sect5" text="%n. %t"/>
+    <l:template name="section" text="%n. %t"/>
+    <l:template name="simplesect" text="%n. %t"/>
+  </l:context>
+  <l:context name="subtitle">
+    <l:template name="appendix" text="%s"/>
+    <l:template name="article" text="%s"/>
+    <l:template name="bibliodiv" text="%s"/>
+    <l:template name="biblioentry" text="%s"/>
+    <l:template name="bibliography" text="%s"/>
+    <l:template name="bibliomixed" text="%s"/>
+    <l:template name="bibliomset" text="%s"/>
+    <l:template name="biblioset" text="%s"/>
+    <l:template name="book" text="%s"/>
+    <l:template name="chapter" text="%s"/>
+    <l:template name="colophon" text="%s"/>
+    <l:template name="dedication" text="%s"/>
+    <l:template name="glossary" text="%s"/>
+    <l:template name="glossdiv" text="%s"/>
+    <l:template name="index" text="%s"/>
+    <l:template name="indexdiv" text="%s"/>
+    <l:template name="lot" text="%s"/>
+    <l:template name="part" text="%s"/>
+    <l:template name="partintro" text="%s"/>
+    <l:template name="preface" text="%s"/>
+    <l:template name="refentry" text="%s"/>
+    <l:template name="reference" text="%s"/>
+    <l:template name="refsect1" text="%s"/>
+    <l:template name="refsect2" text="%s"/>
+    <l:template name="refsect3" text="%s"/>
+    <l:template name="refsynopsisdiv" text="%s"/>
+    <l:template name="sect1" text="%s"/>
+    <l:template name="sect2" text="%s"/>
+    <l:template name="sect3" text="%s"/>
+    <l:template name="sect4" text="%s"/>
+    <l:template name="sect5" text="%s"/>
+    <l:template name="section" text="%s"/>
+    <l:template name="set" text="%s"/>
+    <l:template name="setindex" text="%s"/>
+    <l:template name="sidebar" text="%s"/>
+    <l:template name="simplesect" text="%s"/>
+    <l:template name="toc" text="%s"/>
+  </l:context>
+  <l:context name="xref">
+    <l:template name="abstract" text="%t"/>
+    <l:template name="answer" text="&#31572;&#65306;&#160;%n"/>
+    <l:template name="appendix" text="%t"/>
+    <l:template name="article" text="%t"/>
+    <l:template name="authorblurb" text="%t"/>
+    <l:template name="bibliodiv" text="%t"/>
+    <l:template name="bibliography" text="%t"/>
+    <l:template name="bibliomset" text="%t"/>
+    <l:template name="biblioset" text="%t"/>
+    <l:template name="blockquote" text="%t"/>
+    <l:template name="book" text="%t"/>
+    <l:template name="calloutlist" text="%t"/>
+    <l:template name="caution" text="%t"/>
+    <l:template name="chapter" text="%t"/>
+    <l:template name="colophon" text="%t"/>
+    <l:template name="constraintdef" text="%t"/>
+    <l:template name="dedication" text="%t"/>
+    <l:template name="equation" text="%t"/>
+    <l:template name="example" text="%t"/>
+    <l:template name="figure" text="%t"/>
+    <l:template name="formalpara" text="%t"/>
+    <l:template name="glossary" text="%t"/>
+    <l:template name="glossdiv" text="%t"/>
+    <l:template name="important" text="%t"/>
+    <l:template name="index" text="%t"/>
+    <l:template name="indexdiv" text="%t"/>
+    <l:template name="itemizedlist" text="%t"/>
+    <l:template name="legalnotice" text="%t"/>
+    <l:template name="listitem" text="%n"/>
+    <l:template name="lot" text="%t"/>
+    <l:template name="msg" text="%t"/>
+    <l:template name="msgexplan" text="%t"/>
+    <l:template name="msgmain" text="%t"/>
+    <l:template name="msgrel" text="%t"/>
+    <l:template name="msgset" text="%t"/>
+    <l:template name="msgsub" text="%t"/>
+    <l:template name="note" text="%t"/>
+    <l:template name="orderedlist" text="%t"/>
+    <l:template name="part" text="%t"/>
+    <l:template name="partintro" text="%t"/>
+    <l:template name="preface" text="%t"/>
+    <l:template name="procedure" text="%t"/>
+    <l:template name="productionset" text="%t"/>
+    <l:template name="qandadiv" text="%t"/>
+    <l:template name="qandaentry" text="&#21839;&#65306;&#160;%n"/>
+    <l:template name="qandaset" text="%t"/>
+    <l:template name="question" text="&#21839;&#65306;&#160;%n"/>
+    <l:template name="reference" text="%t"/>
+    <l:template name="refsynopsisdiv" text="%t"/>
+    <l:template name="segmentedlist" text="%t"/>
+    <l:template name="set" text="%t"/>
+    <l:template name="setindex" text="%t"/>
+    <l:template name="sidebar" text="%t"/>
+    <l:template name="table" text="%t"/>
+    <l:template name="tip" text="%t"/>
+    <l:template name="toc" text="%t"/>
+    <l:template name="variablelist" text="%t"/>
+    <l:template name="varlistentry" text="%n"/>
+    <l:template name="warning" text="%t"/>
+    <l:template name="page.citation" text=" [%p]"/>
+    <l:template name="bridgehead" text="&quot;%t&quot;"/>
+    <l:template name="refsect1" text="&quot;%t&quot;"/>
+    <l:template name="refsect2" text="&quot;%t&quot;"/>
+    <l:template name="refsect3" text="&quot;%t&quot;"/>
+    <l:template name="sect1" text="&quot;%t&quot;"/>
+    <l:template name="sect2" text="&quot;%t&quot;"/>
+    <l:template name="sect3" text="&quot;%t&quot;"/>
+    <l:template name="sect4" text="&quot;%t&quot;"/>
+    <l:template name="sect5" text="&quot;%t&quot;"/>
+    <l:template name="section" text="&quot;%t&quot;"/>
+    <l:template name="simplesect" text="&quot;%t&quot;"/>
+  </l:context>
+  <l:context name="xref-number">
+    <l:template name="answer" text="&#31572;&#65306;&#160;%n"/>
+    <l:template name="appendix" text="&#38468;&#37636;&#160;%n"/>
+    <l:template name="bridgehead" text="&#31680;&#160;%n"/>
+    <l:template name="chapter" text="&#31456;&#160;%n"/>
+    <l:template name="equation" text="&#26041;&#31243;&#24335;&#160;%n"/>
+    <l:template name="example" text="&#31684;&#20363;&#160;%n"/>
+    <l:template name="figure" text="&#22294;&#24418;&#160;%n"/>
+    <l:template name="part" text="&#37096;&#160;%n"/>
+    <l:template name="procedure" text="&#36942;&#31243;&#160;%n"/>
+    <l:template name="productionset" text="Production&#160;%n"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n"/>
+    <l:template name="qandaentry" text="&#21839;&#65306;&#160;%n"/>
+    <l:template name="question" text="&#21839;&#65306;&#160;%n"/>
+    <l:template name="sect1" text="&#31680;&#160;%n"/>
+    <l:template name="sect2" text="&#31680;&#160;%n"/>
+    <l:template name="sect3" text="&#31680;&#160;%n"/>
+    <l:template name="sect4" text="&#31680;&#160;%n"/>
+    <l:template name="sect5" text="&#31680;&#160;%n"/>
+    <l:template name="section" text="&#31680;&#160;%n"/>
+    <l:template name="table" text="&#34920;&#26684;&#160;%n"/>
+  </l:context>
+  <l:context name="xref-number-and-title">
+    <l:template name="appendix" text="&#38468;&#37636;&#160;%n, %t"/>
+    <l:template name="bridgehead" text="&#31680;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="chapter" text="&#31456;&#160;%n, %t"/>
+    <l:template name="equation" text="&#26041;&#31243;&#24335;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="example" text="&#31684;&#20363;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="figure" text="&#22294;&#24418;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="part" text="&#37096;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="procedure" text="&#36942;&#31243;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="productionset" text="Production&#160;%n, &quot;%t&quot;"/>
+    <l:template name="qandadiv" text="Q &amp; A&#160;%n, &quot;%t&quot;"/>
+    <l:template name="refsect1" text="the section called &quot;%t&quot;"/>
+    <l:template name="refsect2" text="the section called &quot;%t&quot;"/>
+    <l:template name="refsect3" text="the section called &quot;%t&quot;"/>
+    <l:template name="refsection" text="the section called &quot;%t&quot;"/>
+    <l:template name="sect1" text="&#31680;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="sect2" text="&#31680;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="sect3" text="&#31680;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="sect4" text="&#31680;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="sect5" text="&#31680;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="section" text="&#31680;&#160;%n, &quot;%t&quot;"/>
+    <l:template name="simplesect" text="the section called &quot;%t&quot;"/>
+    <l:template name="table" text="&#34920;&#26684;&#160;%n, &quot;%t&quot;"/>
+  </l:context>
+  <l:context name="authorgroup">
+    <l:template name="sep" text=", "/>
+    <l:template name="sep2" text=" &#19988; "/>
+    <l:template name="seplast" text=", &#19988; "/>
+  </l:context>
+  <l:context name="glossary">
+    <l:template name="see" text="&#21443;&#35211; "/>
+    <l:template name="seealso" text="&#21478;&#21443;&#35211; "/>
+  </l:context>
+  <l:context name="msgset">
+    <l:template name="MsgAud" text="&#35712;&#32773;: "/>
+    <l:template name="MsgLevel" text="&#31243;&#24230;: "/>
+    <l:template name="MsgOrig" text="&#20986;&#34389;: "/>
+  </l:context>
+  <l:context name="htmlhelp">
+    <l:template name="langcode" text="0x0404 Chinese (TAIWAN)"/>
+  </l:context>
+</l:l10n>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/component.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/component.mod.xsl
new file mode 100644
index 00000000000..6e64189a8c7
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/component.mod.xsl
@@ -0,0 +1,93 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: component.mod.xsl,v 1.6 2004/01/03 12:17:59 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="component" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: component.mod.xsl,v 1.6 2004/01/03 12:17:59 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.3">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Chapter-level Components <filename>component.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>component.mod.xsl</filename> contains
+			XSL templates for a number of chapter-level components.</para>
+		</partintro>
+	</doc:reference>
+
+	<!--
+	<xsl:template name="component.title">
+		<xsl:variable name="id">
+			<xsl:call-template name="label.id"><xsl:with-param name="object" select="."/></xsl:call-template>
+		</xsl:variable>
+		<xsl:text>&#10;{\sc </xsl:text><xsl:apply-templates select="." mode="title.ref"/><xsl:text>}</xsl:text>
+	</xsl:template>
+
+	<xsl:template name="component.subtitle">
+		<xsl:variable name="subtitle"><xsl:apply-templates select="." mode="subtitle.content"/></xsl:variable>
+		<xsl:if test="$subtitle != ''">
+			<xsl:text>&#10;{\sc </xsl:text><xsl:copy-of select="$subtitle"/><xsl:text>}</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<xsl:template name="component.separator"/>
+	-->
+
+	<doc:template xmlns="">
+		<refpurpose>Process some simply chapter-level components</refpurpose>
+		<doc:description>
+			<para>
+				Invokes the mapping templates and applies content templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.content-templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="dedication|colophon|preface|partintro">
+		<xsl:call-template name="map.begin"/>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<!--
+	<xsl:template match="colophon">
+		<xsl:call-template name="label.id"/>
+		<xsl:text>&#10;{\sc </xsl:text><xsl:apply-templates select="." mode="title.ref"/><xsl:text>}</xsl:text>
+		<xsl:if test="subtitle">
+			<xsl:text>&#10;{\sc </xsl:text>
+			<xsl:apply-templates select="subtitle"/>
+			<xsl:text>}</xsl:text>
+		</xsl:if>
+		<xsl:call-template name="content-templates"/>
+	</xsl:template>
+	-->
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/dingbat.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/dingbat.mod.xsl
new file mode 100644
index 00000000000..8e7546f70a0
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/dingbat.mod.xsl
@@ -0,0 +1,85 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: dingbat.mod.xsl,v 1.4 2004/01/02 05:11:38 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="dingbat" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: dingbat.mod.xsl,v 1.4 2004/01/02 05:11:38 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.4">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Dingbats <filename>dingbat.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			Provides some named dingbats. These should probably be incorporated
+			into the normal localisation mechanism, in future.
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose> Generate a &LaTeX; dingbat </refpurpose>
+		<doc:description>
+			<para>
+			
+			Chooses a &LaTeX; sequence based on the requested dingbat name.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>dingbat</term>
+					<listitem><simpara>The name of the dingbat.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+	</doc:template>
+	<xsl:template name="dingbat">
+		<xsl:param name="dingbat">bullet</xsl:param>
+		<xsl:choose>
+			<xsl:when test="$dingbat='bullet'"> $\bullet$ </xsl:when>
+			<xsl:when test="$dingbat='copyright'">\copyright{}</xsl:when>
+			<xsl:when test="$dingbat='trademark'">\texttrademark{}</xsl:when>
+			<xsl:when test="$dingbat='registered'">\textregistered{}</xsl:when>
+			<xsl:when test="$dingbat='nbsp'">~</xsl:when>
+			<xsl:when test="$dingbat='ldquo'">``</xsl:when>
+			<xsl:when test="$dingbat='rdquo'">''</xsl:when>
+			<xsl:when test="$dingbat='lsquo'">`</xsl:when>
+			<xsl:when test="$dingbat='rsquo'">'</xsl:when>
+			<xsl:when test="$dingbat='em-dash'">---</xsl:when>
+			<xsl:when test="$dingbat='mdash'">---</xsl:when>
+			<xsl:when test="$dingbat='en-dash'">--</xsl:when>
+			<xsl:when test="$dingbat='ndash'">--</xsl:when>
+			<xsl:otherwise>
+			<xsl:text> [dingbat?] </xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/docbook.xsl b/docs-xml/xslt/db2latex-xsl/xsl/docbook.xsl
new file mode 100644
index 00000000000..10892ae0c3d
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/docbook.xsl
@@ -0,0 +1,232 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: docbook.xsl,v 1.14 2004/01/04 09:03:25 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet 
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="docbook" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: docbook.xsl,v 1.14 2004/01/04 09:03:25 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.10">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>DocBook Driver <filename>docbook.xsl</filename></title>
+		<partintro>
+			<para>
+				
+				This is the <quote>parent</quote> stylesheet. The used
+				<quote>modules</quote> are included here. The output encoding
+				is <literal>text</literal> in ISO-8859-1, indented. Parameters
+				may be found in
+				<!--
+				<link linkend="vars">vars.mod.xsl</link>,
+				-->
+				<link linkend="param-common">param-common.xsl</link>,
+				<link linkend="param-switch">param-switch.xsl</link> and
+				<link linkend="param-direct">param-direct.xsl</link>. Users
+				may use this stylesheets directory or may construct their own
+				<quote>customisation layer</quote> that uses
+				<literal>xsl:import</literal>. Users may also override the
+				<link linkend="latex.mapping">default &latex; mappings</link>.
+				
+			</para>
+			<para>
+				
+				An <literal>id</literal> XSLT key is defined for all elements,
+				matching their <sgmltag class="attribute">id</sgmltag>
+				attribute, to work around <productname>xsltproc</productname>
+				bugs.
+				
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<xsl:output method="text" encoding="ISO-8859-1" indent="yes"/>
+	<xsl:key name="id" match="*" use="@id"/>
+
+	<xsl:include href="common/l10n.xsl"/>
+	<xsl:include href="common/common.xsl"/>
+	<xsl:include href="common/gentext.xsl"/>
+	<xsl:include href="common/subtitles.xsl"/>
+	<xsl:include href="common/titles.xsl"/>
+	<!--
+	<xsl:include href="lib/lib.xsl"/>
+	-->
+
+	<xsl:include href="VERSION.xml"/>
+	<xsl:include href="param-common.mod.xsl"/>
+	<xsl:include href="param-switch.mod.xsl"/>
+	<xsl:include href="param-direct.mod.xsl"/>
+	<xsl:include href="latex.mapping.xsl"/>
+	<xsl:include href="preamble.mod.xsl"/>
+	<xsl:include href="labelid.mod.xsl"/>
+
+	<xsl:include href="book-article.mod.xsl"/>
+
+	<xsl:include href="component.mod.xsl"/>
+
+	<xsl:include href="part-chap-app.mod.xsl"/>
+
+	<xsl:include href="sections.mod.xsl"/>
+	<xsl:include href="bridgehead.mod.xsl"/>
+
+	<xsl:include href="abstract.mod.xsl"/>
+	<xsl:include href="biblio.mod.xsl"/>
+	<xsl:include href="revision.mod.xsl"/>
+
+	<xsl:include href="admonition.mod.xsl"/>
+	<xsl:include href="verbatim.mod.xsl"/>
+	<xsl:include href="email.mod.xsl"/>
+	<xsl:include href="sgmltag.mod.xsl"/>
+	<xsl:include href="citation.mod.xsl"/>
+	<xsl:include href="qandaset.mod.xsl"/>
+	<xsl:include href="procedure.mod.xsl"/>
+	<xsl:include href="lists.mod.xsl"/>
+	<xsl:include href="callout.mod.xsl"/>
+
+	<xsl:include href="figure.mod.xsl"/>
+	<xsl:include href="graphic.mod.xsl"/>
+	<xsl:include href="mediaobject.mod.xsl"/>
+
+	<xsl:include href="index.mod.xsl"/>
+
+	<xsl:include href="xref.mod.xsl"/>
+	<xsl:include href="formal.mod.xsl"/>
+	<xsl:include href="example.mod.xsl"/>
+	<xsl:include href="table.mod.xsl"/>
+	<xsl:include href="inline.mod.xsl"/>
+	<xsl:include href="authorgroup.mod.xsl"/>
+	<xsl:include href="dingbat.mod.xsl"/>
+	<xsl:include href="keywords.mod.xsl"/>
+	<xsl:include href="refentry.mod.xsl"/>
+	<xsl:include href="glossary.mod.xsl"/>
+	<xsl:include href="block.mod.xsl"/>
+
+	<xsl:include href="synop-oop.mod.xsl"/>
+	<xsl:include href="synop-struct.mod.xsl"/>
+
+	<xsl:include href="pi.mod.xsl"/>
+
+	<xsl:include href="footnote.mod.xsl"/>
+
+	<xsl:include href="texmath.mod.xsl"/>
+	<xsl:include href="mathelem.mod.xsl"/>
+	<xsl:include href="mathml/mathml.mod.xsl"/>
+	<xsl:include href="mathml/mathml.presentation.mod.xsl"/>
+	<xsl:include href="mathml/mathml.content.mod.xsl"/>
+	<xsl:include href="mathml/mathml.content.token.mod.xsl"/>
+	<xsl:include href="mathml/mathml.content.functions.mod.xsl"/>
+	<xsl:include href="mathml/mathml.content.constsymb.mod.xsl"/>
+
+	<xsl:include href="para.mod.xsl"/>
+	<xsl:include href="msgset.mod.xsl"/>
+
+	<xsl:include href="normalize-scape.mod.xsl"/>
+
+	<doc:template match="/" xmlns="">
+		<refpurpose>Root node</refpurpose>
+		<doc:description>
+			<para>
+
+				This template begins the conversion of a &docbook; document to
+				&latex;.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="/">
+		<xsl:variable name="xsl-vendor" select="system-property('xsl:vendor')"/>
+		<xsl:message>################################################################################</xsl:message>
+		<xsl:message> XSLT stylesheets DocBook - LaTeX 2e                                            </xsl:message>
+		<xsl:message> Reqs: LaTeX 2e installation common packages                                    </xsl:message>
+		<xsl:message>################################################################################</xsl:message>
+		<xsl:message> RELEASE : <xsl:value-of select="$VERSION"/>                                    </xsl:message>
+		<xsl:message> VERSION : <xsl:value-of select="$CVSVERSION"/>                                 </xsl:message>
+		<xsl:message>     TAG : <xsl:value-of select="$TAG"/>                                        </xsl:message>
+		<xsl:message>     WWW : http://db2latex.sourceforge.net                                      </xsl:message>
+		<xsl:message> SUMMARY : http://www.sourceforge.net/projects/db2latex                         </xsl:message>
+		<xsl:message>  AUTHOR : Ramon Casellas  casellas@infres.enst.fr                              </xsl:message>
+		<xsl:message>  AUTHOR : James Devenish  j-devenish@users.sf.net                              </xsl:message>
+		<xsl:message>   USING : <xsl:call-template name="set-vendor"/>                               </xsl:message>
+		<xsl:message>################################################################################</xsl:message>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<!--############################################################################# -->
+	<!-- XSL Processor Vendor														  -->
+	<!-- XSL Mailing Lists http://www.dpawson.co.uk/xsl/N10378.html					  -->
+	<!--############################################################################# -->
+	<xsl:template name="set-vendor">
+		<xsl:variable name="xsl-vendor" select="system-property('xsl:vendor')"/>
+		<xsl:choose>
+			<xsl:when test="contains($xsl-vendor, 'SAXON 6.4')">
+			<xsl:text>SAXON 6.4.X</xsl:text>
+			</xsl:when>
+			<xsl:when test="contains($xsl-vendor, 'SAXON 6.2')">
+			<xsl:text>SAXON 6.2.X</xsl:text>
+			</xsl:when>
+			<xsl:when test="starts-with($xsl-vendor,'SAXON')">
+			<xsl:text>SAXON</xsl:text>
+			</xsl:when>
+			<xsl:when test="contains($xsl-vendor,'Apache')">
+			<xsl:text>XALAN</xsl:text>
+			</xsl:when>
+			<xsl:when test="contains($xsl-vendor,'Xalan')">
+			<xsl:text>XALAN</xsl:text>
+			</xsl:when>
+			<xsl:when test="contains($xsl-vendor,'libxslt')">
+			<xsl:text>libxslt/xsltproc</xsl:text>
+			</xsl:when>
+			<xsl:when test="contains($xsl-vendor,'Clark')">
+			<xsl:text>XT</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+			<xsl:text>UNKNOWN</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template match="*" xmlns="">
+		<refpurpose>Catches unhandled elements</refpurpose>
+		<doc:description>
+			<para>
+
+				This template emits an XSL message when &db2latex; has no
+				template for an element that was encountered.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="*">
+		<xsl:message>DB2LaTeX: Need to process XPath match <xsl:value-of select="concat(name(..),'/',name(.))"/></xsl:message>
+		<xsl:text> [</xsl:text><xsl:value-of select="name(.)"/><xsl:text>] &#10;</xsl:text>
+		<xsl:apply-templates/> 
+		<xsl:text> [/</xsl:text><xsl:value-of select="name(.)"/><xsl:text>] &#10;</xsl:text>
+	</xsl:template>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/email.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/email.mod.xsl
new file mode 100644
index 00000000000..2817790fbbd
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/email.mod.xsl
@@ -0,0 +1,77 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: email.mod.xsl,v 1.6 2003/12/28 10:43:16 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet 
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="email" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: email.mod.xsl,v 1.6 2003/12/28 10:43:16 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.6">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>E-mail Addreses <filename>email.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>email.mod.xsl</filename> contains the
+			XSL template for <doc:db>email</doc:db>.</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template basename="email" match="email" xmlns="">
+		<refpurpose>Process <doc:db>email</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Constructs a URL from the given e-mail address and
+				formats it with the template for <doc:db>ulink</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<para>As for the <xref linkend="template.ulink"/> template.</para>
+		</doc:variables>
+		<doc:notes>
+			<para>When a an <doc:db>email</doc:db> is a child of an <doc:db>address</doc:db>,
+			it will be formatted along with all <quote>verbatim</quote> address text. In this
+			case, it might not be hyperlinked.</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_ddh;
+				&test_links;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.ulink"/></simpara></listitem>
+				<!--
+				<listitem><simpara>&mapping;</simpara></listitem>
+				-->
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="email">
+		<xsl:call-template name="ulink">
+			<xsl:with-param name="url" select="concat('mailto:',.)"/>
+			<xsl:with-param name="content" select="."/>
+		</xsl:call-template>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/example.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/example.mod.xsl
new file mode 100644
index 00000000000..0937cfb6d6f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/example.mod.xsl
@@ -0,0 +1,119 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: example.mod.xsl,v 1.9 2004/01/26 09:40:43 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="example" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: example.mod.xsl,v 1.9 2004/01/26 09:40:43 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.7">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Examples <filename>example.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>example.mod.xsl</filename> contains the
+			XSL templates for <doc:db>example</doc:db> and
+			<doc:db>informalexample</doc:db>.</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>example</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Format a caption.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.example.caption.style"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<!--
+		<doc:notes>
+		</doc:notes>
+		-->
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_program;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.generate.formal.title.placement"/></simpara></listitem>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.title-caption.mode"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="example">
+		<xsl:variable name="placement">
+			<xsl:call-template name="generate.formal.title.placement">
+				<xsl:with-param name="object" select="local-name(.)" />
+			</xsl:call-template>
+		</xsl:variable>
+		<xsl:variable name="caption">
+			<xsl:text>{</xsl:text>
+			<xsl:value-of select="$latex.example.caption.style"/>
+			<xsl:text>{\caption{</xsl:text>
+			<xsl:apply-templates select="title" mode="caption.mode"/>
+			<xsl:text>}</xsl:text>
+			<xsl:call-template name="label.id"/>
+			<xsl:text>}}&#10;</xsl:text>
+		</xsl:variable>
+		<xsl:call-template name="map.begin"/>
+		<xsl:if test="$placement='before'">
+			<xsl:text>\captionswapskip{}</xsl:text>
+			<xsl:value-of select="$caption" />
+			<xsl:text>\captionswapskip{}</xsl:text>
+		</xsl:if>
+		<xsl:call-template name="content-templates"/>
+		<xsl:if test="$placement!='before'"><xsl:value-of select="$caption" /></xsl:if>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>informalexample</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Calls <xref linkend="template.informal.object"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<!--
+		<doc:notes>
+		</doc:notes>
+		-->
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="informalexample">
+		<xsl:call-template name="informal.object"/>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figure.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/figure.mod.xsl
new file mode 100644
index 00000000000..eda03111a9a
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figure.mod.xsl
@@ -0,0 +1,259 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: figure.mod.xsl,v 1.17 2004/01/26 09:43:31 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $												
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="figure" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: figure.mod.xsl,v 1.17 2004/01/26 09:43:31 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.14">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Figures and InformalFigures <filename>figure.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			<doc:todo>Insert documentation here.</doc:todo>
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose> Typeset a caption for a formal figure  </refpurpose>
+		<doc:description>
+			<para>
+			
+			Formats a caption, if any, as a centred block.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.figure.caption.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.caption.lot.titles.only"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.figure.title.style"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				The &LaTeX; caption is a combination of <doc:db>title</doc:db>
+				and <doc:db>caption</doc:db> children.
+				A <link linkend="template.lot">list of figures</link>
+				will contain cross-references to these formal figures.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_subfig;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template name="generate.aux.figure.caption">
+		<xsl:text>{</xsl:text>
+		<xsl:value-of select="$latex.figure.caption.style"/>
+		<xsl:choose>
+			<xsl:when test="$latex.caption.lot.titles.only='1'">
+				<xsl:text>{\caption[{</xsl:text>
+				<xsl:apply-templates select="title"/>
+				<xsl:text>}]{{</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>{\caption{{</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:value-of select="$latex.figure.title.style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:apply-templates select="title"/>
+		<xsl:text>}}</xsl:text>
+		<xsl:if test="count(child::mediaobject/caption)=1">
+			<xsl:text>. </xsl:text>
+			<xsl:apply-templates select="mediaobject/caption" />
+		</xsl:if>
+		<xsl:text>}</xsl:text>
+		<xsl:call-template name="label.id"/>
+		<xsl:text>}}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Process <doc:db>figure</doc:db> elements </refpurpose>
+		<doc:description>
+			<para>
+			
+			Formats a formal, <quote>floating</quote> figure with a title and caption.
+			The figure may contain multiple subfigures.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.formal.title.placement"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				If the figure contains only one mediaobject, that mediaobject's
+				caption will be used as the figure caption. However, if there
+				are multiple meid in the figure, then it will be divided into
+				subfigures with their own caption.
+
+			</para>
+			<para>
+
+				If a <sgmltag class="attribute">condition</sgmltag> attribute
+				exists and begins with <quote>db2latex:</quote>, or a <sgmltag
+				class="pi">latex-float-placement</sgmltag> processing
+				instruction is present, the remainder of its value will be used
+				as the &LaTeX; <quote>float</quote> placement. Otherwise, the
+				default placement is <quote>hbt</quote>.
+
+			</para>
+			&essential_preamble;
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_subfig;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.generate.aux.figure.caption"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="figure">
+		<xsl:variable name="placement">
+			<xsl:call-template name="generate.formal.title.placement">
+				<xsl:with-param name="object" select="local-name(.)" />
+			</xsl:call-template>
+		</xsl:variable>
+		<xsl:variable name="position">
+			<xsl:call-template name="generate.latex.float.position">
+				<xsl:with-param name="default" select="'hbt'"/>
+			</xsl:call-template>
+		</xsl:variable>
+		<xsl:call-template name="map.begin">
+			<xsl:with-param name="string" select="$position"/>
+		</xsl:call-template>
+		<xsl:if test="$placement='before'">
+			<xsl:text>\captionswapskip{}</xsl:text>
+			<xsl:call-template name="generate.aux.figure.caption" />
+			<xsl:text>\captionswapskip{}</xsl:text>
+		</xsl:if>
+		<xsl:apply-templates select="*[name(.) != 'title']"/>
+		<xsl:if test="$placement!='before'">
+			<xsl:call-template name="generate.aux.figure.caption" />
+		</xsl:if>
+		<xsl:call-template name="map.end">
+			<xsl:with-param name="string" select="$position"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Typeset a caption for an informal figure  </refpurpose>
+		<doc:description>
+			<para>
+			
+			Formats a caption, if any, as a centred block.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				A caption, if any, is gleaned from the <doc:db>caption</doc:db>
+				child of any <doc:db>mediaobject</doc:db> contained within the
+				<doc:db>informalfigure</doc:db>, and will be formatted as a
+				centred block.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_subfig;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template name="generate.aux.informalfigure.caption">
+		<xsl:if test="count(child::mediaobject/caption)=1">
+			<xsl:text>\begin{center}&#10;</xsl:text>
+			<xsl:apply-templates select="mediaobject/caption" />
+			<xsl:text>\end{center}&#10;</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>informalfigure</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Apply templates for an informal figure.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				The caption is inserted below the informalfigure.
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_subfig;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.generate.aux.informalfigure.caption"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="informalfigure">
+		<xsl:call-template name="map.begin"/>
+		<xsl:apply-templates/>
+		<xsl:call-template name="generate.aux.informalfigure.caption" />
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<!--
+    <xsl:template match="figure[programlisting]">
+	<xsl:call-template name="map.begin">
+	    <xsl:with-param name="keyword" select="programlisting"/>
+	</xsl:call-template>
+	<xsl:apply-templates />
+	<xsl:call-template name="map.end">
+	    <xsl:with-param name="keyword" select="programlisting"/>
+	</xsl:call-template>
+    </xsl:template>
+	-->
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/caution.eps b/docs-xml/xslt/db2latex-xsl/xsl/figures/caution.eps
new file mode 100644
index 00000000000..c9473b72720
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/caution.eps
@@ -0,0 +1,1348 @@
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-3
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/12/05 8:20 PM
+%%BoundingBox: 0 0 29 29
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-3
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-3
+%ALDBoundingBox: -2 -2 29 29
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if 
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put 
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub 
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed { 
+_NXLevel2 not { 
+/colorimage where {
+userdict eq {
+/_rci false def 
+} if
+} if
+} if
+} if
+/md defed{ 
+md type /dicttype eq { 
+/colorimage where { 
+md eq { 
+/_rci false def 
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if 
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add 
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf 
+}ifelse
+/privrectpath { 
+4 -2 roll m
+dtransform round exch round exch idtransform 
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed 
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/` 
+{ 
+false setoverprint 
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1 
+statusdict begin
+/processcolors defed 
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end 
+def
+/printerRes 
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency} 
+{GrayAngle GrayFrequency} 
+{0 Width Height matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60} 
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch 
+}
+ifelse
+printerRes 300 max exch div exch 
+2 copy 
+sin mul round dup mul 
+3 1 roll 
+cos mul round dup mul 
+add 1 add 
+dup maxsteps gt {pop maxsteps} if 
+dup minsteps lt {pop minsteps} if 
+}
+ifelse
+} bdf
+/nextrelease defed { 
+/languagelevel defed not { 
+/framebuffer defed { 
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps 
+{
+forcemaxsteps 
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max 
+printerRes div 
+gradfrequency mul 
+round 
+5 max 
+min 
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def 
+/delta -0 def 
+/frac -0 def 
+/height -0 def 
+/left -0 def 
+/numsteps1 -0 def 
+/radius -0 def 
+/right -0 def 
+/top -0 def 
+/width -0 def 
+/xt -0 def 
+/yt -0 def 
+/df currentflat def 
+/tempstr 1 string def 
+/clipflatness currentflat def 
+/inverted? 
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def 
+/tc2 [0 0 0 1] def 
+/storerect{/top xdf /right xdf /bottom xdf /left xdf 
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known 
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup} 
+{dup} ifelse 
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{ 
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def 
+{ 
+exch dup 
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall 
+NF
+}bdf
+/MN{
+1 index length 
+/Len exch def 
+dup length Len add 
+string dup 
+Len 
+4 -1 roll 
+putinterval 
+dup 
+0 
+4 -1 roll 
+putinterval 
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll 
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFJ 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFJ{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCJ} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont 
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFJ 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup 
+hasfont 
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFK 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFK{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCK} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/JCsm
+hasfont 
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFK{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFK 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFTC 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFTC{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCTC} 
+ifelse
+}bdf
+/FDFTC
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/DFMing-Lt-HK-BF
+hasfont 
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFTC 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat 
+exch 
+dup 0 le{pop 1}if 
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if} 
+{exit} 
+ifelse
+}loop 
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf 
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def 
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash 
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont 
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh 
+
+_efh 
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin 
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor { 
+max max max 
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf 
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{ 
+4 index 1 index get 0.3 mul 
+4 index 2 index get 0.59 mul 
+4 index 3 index get 0.11 mul 
+4 index 4 index get 
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx 
+6 -1 roll/exec cvx 
+7 -1 roll/exec cvx 
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx 
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le 
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st 
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop 
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub 
+1.0 dup im ik add min sub 
+1.0 dup iy ik add min sub 
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll 
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll 
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf 
+/setspotcolor { 
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf 
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def 
+/_lfp4 {
+1 pop 
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def 
+/_lfs4 {
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 2 lt {pop 2} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop 
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def 
+/vc{
+AltsysDict /cvc 2 index put 
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf 
+0 setseparationgray
+/imgr {1692.47 1570.59 1723.65 1601.77 } def 
+/bleed 0 def 
+/clpr {1692.47 1570.59 1723.65 1601.77 } def 
+/xs 1 def 
+/ys 1 def 
+/botx 0 def 
+/overlap 0 def 
+/wdist 18 def 
+0 2 mul fhsetspreadsize 
+0 0 ne {/df 0 def /clipflatness 0 def} if 
+/maxsteps 256 def 
+/forcemaxsteps false def 
+/minsteps 0 def 
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end 
+vms
+-1694 -1572 translate
+
+/currentpacking defed{false setpacking}if 
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+q
+[1 0 0 1 -249.981674 -586.867554] concat
+vms
+1946.9506 2177.5114 m
+1954.4907 2185.0516 L
+1956.7047 2187.2656 1960.2943 2187.2656 1962.5083 2185.0516 C
+1970.0485 2177.5114 L
+1972.2625 2175.2974 1972.2625 2171.7078 1970.0485 2169.4938 C
+1962.5083 2161.9537 L
+1960.2943 2159.7396 1956.7047 2159.7396 1954.4907 2161.9537 C
+1946.9506 2169.4938 L
+1944.7365 2171.7078 1944.7365 2175.2974 1946.9506 2177.5114 C
+s 
+n
+true eomode
+1958.5469 2181.0039 m
+1959.2148 2181.0039 1959.7012 2180.9296 1960.0059 2180.7813 C
+1960.3142 2180.6326 1960.4684 2180.363 1960.4688 2179.9727 C
+1960.4688 2179.7383 1960.3398 2178.8026 1960.082 2177.166 C
+1959.0742 2170.4219 L
+1958.9373 2170.3241 1958.7615 2170.2754 1958.5469 2170.2754 C
+1958.3319 2170.2754 1958.1561 2170.3241 1958.0195 2170.4219 C
+1957.0117 2177.166 L
+1956.7539 2178.8026 1956.625 2179.7379 1956.625 2179.9727 C
+1956.625 2180.363 1956.7792 2180.6326 1957.0879 2180.7813 C
+1957.4003 2180.9296 1957.8866 2181.0035 1958.5469 2181.0039 C
+h
+1958.5469 2165.166 m
+1958.0389 2165.166 1957.5878 2165.3499 1957.1934 2165.7168 C
+1956.7986 2166.0837 1956.6016 2166.5485 1956.6016 2167.1113 C
+1956.6016 2167.6698 1956.7891 2168.1404 1957.1641 2168.5234 C
+1957.5427 2168.9102 1958.0038 2169.1035 1958.5469 2169.1035 C
+1959.1094 2169.1035 1959.5741 2168.9043 1959.9414 2168.5059 C
+1960.3083 2168.1074 1960.4918 2167.6423 1960.4922 2167.1113 C
+1960.4922 2166.748 1960.4102 2166.4177 1960.2461 2166.1211 C
+1960.082 2165.8241 1959.8513 2165.5916 1959.5547 2165.4238 C
+1959.2577 2165.2521 1958.9219 2165.1664 1958.5469 2165.166 C
+true setoverprint
+f 
+false setoverprint
+n
+vmr
+Q
+false eomode
+vmr
+vmr
+end
+%%Trailer
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/caution.pdf b/docs-xml/xslt/db2latex-xsl/xsl/figures/caution.pdf
new file mode 100644
index 00000000000..a0afabfa232
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/caution.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/important.eps b/docs-xml/xslt/db2latex-xsl/xsl/figures/important.eps
new file mode 100644
index 00000000000..c9473b72720
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/important.eps
@@ -0,0 +1,1348 @@
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-3
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/12/05 8:20 PM
+%%BoundingBox: 0 0 29 29
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-3
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-3
+%ALDBoundingBox: -2 -2 29 29
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if 
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put 
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub 
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed { 
+_NXLevel2 not { 
+/colorimage where {
+userdict eq {
+/_rci false def 
+} if
+} if
+} if
+} if
+/md defed{ 
+md type /dicttype eq { 
+/colorimage where { 
+md eq { 
+/_rci false def 
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if 
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add 
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf 
+}ifelse
+/privrectpath { 
+4 -2 roll m
+dtransform round exch round exch idtransform 
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed 
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/` 
+{ 
+false setoverprint 
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1 
+statusdict begin
+/processcolors defed 
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end 
+def
+/printerRes 
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency} 
+{GrayAngle GrayFrequency} 
+{0 Width Height matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60} 
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch 
+}
+ifelse
+printerRes 300 max exch div exch 
+2 copy 
+sin mul round dup mul 
+3 1 roll 
+cos mul round dup mul 
+add 1 add 
+dup maxsteps gt {pop maxsteps} if 
+dup minsteps lt {pop minsteps} if 
+}
+ifelse
+} bdf
+/nextrelease defed { 
+/languagelevel defed not { 
+/framebuffer defed { 
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps 
+{
+forcemaxsteps 
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max 
+printerRes div 
+gradfrequency mul 
+round 
+5 max 
+min 
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def 
+/delta -0 def 
+/frac -0 def 
+/height -0 def 
+/left -0 def 
+/numsteps1 -0 def 
+/radius -0 def 
+/right -0 def 
+/top -0 def 
+/width -0 def 
+/xt -0 def 
+/yt -0 def 
+/df currentflat def 
+/tempstr 1 string def 
+/clipflatness currentflat def 
+/inverted? 
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def 
+/tc2 [0 0 0 1] def 
+/storerect{/top xdf /right xdf /bottom xdf /left xdf 
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known 
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup} 
+{dup} ifelse 
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{ 
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def 
+{ 
+exch dup 
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall 
+NF
+}bdf
+/MN{
+1 index length 
+/Len exch def 
+dup length Len add 
+string dup 
+Len 
+4 -1 roll 
+putinterval 
+dup 
+0 
+4 -1 roll 
+putinterval 
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll 
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFJ 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFJ{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCJ} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont 
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFJ 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup 
+hasfont 
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFK 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFK{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCK} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/JCsm
+hasfont 
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFK{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFK 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFTC 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFTC{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCTC} 
+ifelse
+}bdf
+/FDFTC
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/DFMing-Lt-HK-BF
+hasfont 
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFTC 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat 
+exch 
+dup 0 le{pop 1}if 
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if} 
+{exit} 
+ifelse
+}loop 
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf 
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def 
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash 
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont 
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh 
+
+_efh 
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin 
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor { 
+max max max 
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf 
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{ 
+4 index 1 index get 0.3 mul 
+4 index 2 index get 0.59 mul 
+4 index 3 index get 0.11 mul 
+4 index 4 index get 
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx 
+6 -1 roll/exec cvx 
+7 -1 roll/exec cvx 
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx 
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le 
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st 
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop 
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub 
+1.0 dup im ik add min sub 
+1.0 dup iy ik add min sub 
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll 
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll 
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf 
+/setspotcolor { 
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf 
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def 
+/_lfp4 {
+1 pop 
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def 
+/_lfs4 {
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 2 lt {pop 2} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop 
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def 
+/vc{
+AltsysDict /cvc 2 index put 
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf 
+0 setseparationgray
+/imgr {1692.47 1570.59 1723.65 1601.77 } def 
+/bleed 0 def 
+/clpr {1692.47 1570.59 1723.65 1601.77 } def 
+/xs 1 def 
+/ys 1 def 
+/botx 0 def 
+/overlap 0 def 
+/wdist 18 def 
+0 2 mul fhsetspreadsize 
+0 0 ne {/df 0 def /clipflatness 0 def} if 
+/maxsteps 256 def 
+/forcemaxsteps false def 
+/minsteps 0 def 
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end 
+vms
+-1694 -1572 translate
+
+/currentpacking defed{false setpacking}if 
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+q
+[1 0 0 1 -249.981674 -586.867554] concat
+vms
+1946.9506 2177.5114 m
+1954.4907 2185.0516 L
+1956.7047 2187.2656 1960.2943 2187.2656 1962.5083 2185.0516 C
+1970.0485 2177.5114 L
+1972.2625 2175.2974 1972.2625 2171.7078 1970.0485 2169.4938 C
+1962.5083 2161.9537 L
+1960.2943 2159.7396 1956.7047 2159.7396 1954.4907 2161.9537 C
+1946.9506 2169.4938 L
+1944.7365 2171.7078 1944.7365 2175.2974 1946.9506 2177.5114 C
+s 
+n
+true eomode
+1958.5469 2181.0039 m
+1959.2148 2181.0039 1959.7012 2180.9296 1960.0059 2180.7813 C
+1960.3142 2180.6326 1960.4684 2180.363 1960.4688 2179.9727 C
+1960.4688 2179.7383 1960.3398 2178.8026 1960.082 2177.166 C
+1959.0742 2170.4219 L
+1958.9373 2170.3241 1958.7615 2170.2754 1958.5469 2170.2754 C
+1958.3319 2170.2754 1958.1561 2170.3241 1958.0195 2170.4219 C
+1957.0117 2177.166 L
+1956.7539 2178.8026 1956.625 2179.7379 1956.625 2179.9727 C
+1956.625 2180.363 1956.7792 2180.6326 1957.0879 2180.7813 C
+1957.4003 2180.9296 1957.8866 2181.0035 1958.5469 2181.0039 C
+h
+1958.5469 2165.166 m
+1958.0389 2165.166 1957.5878 2165.3499 1957.1934 2165.7168 C
+1956.7986 2166.0837 1956.6016 2166.5485 1956.6016 2167.1113 C
+1956.6016 2167.6698 1956.7891 2168.1404 1957.1641 2168.5234 C
+1957.5427 2168.9102 1958.0038 2169.1035 1958.5469 2169.1035 C
+1959.1094 2169.1035 1959.5741 2168.9043 1959.9414 2168.5059 C
+1960.3083 2168.1074 1960.4918 2167.6423 1960.4922 2167.1113 C
+1960.4922 2166.748 1960.4102 2166.4177 1960.2461 2166.1211 C
+1960.082 2165.8241 1959.8513 2165.5916 1959.5547 2165.4238 C
+1959.2577 2165.2521 1958.9219 2165.1664 1958.5469 2165.166 C
+true setoverprint
+f 
+false setoverprint
+n
+vmr
+Q
+false eomode
+vmr
+vmr
+end
+%%Trailer
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/important.pdf b/docs-xml/xslt/db2latex-xsl/xsl/figures/important.pdf
new file mode 100644
index 00000000000..a0afabfa232
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/important.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/note.eps b/docs-xml/xslt/db2latex-xsl/xsl/figures/note.eps
new file mode 100644
index 00000000000..39be23fa778
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/note.eps
@@ -0,0 +1,1387 @@
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-1
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/07/16 10:41 PM
+%%BoundingBox: 0 0 27 27
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-1
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-1
+%ALDBoundingBox: -153 -436 442 406
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if 
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put 
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub 
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed { 
+_NXLevel2 not { 
+/colorimage where {
+userdict eq {
+/_rci false def 
+} if
+} if
+} if
+} if
+/md defed{ 
+md type /dicttype eq { 
+/colorimage where { 
+md eq { 
+/_rci false def 
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if 
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add 
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf 
+}ifelse
+/privrectpath { 
+4 -2 roll m
+dtransform round exch round exch idtransform 
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed 
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/` 
+{ 
+false setoverprint 
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1 
+statusdict begin
+/processcolors defed 
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end 
+def
+/printerRes 
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency} 
+{GrayAngle GrayFrequency} 
+{0 Width Height matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60} 
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch 
+}
+ifelse
+printerRes 300 max exch div exch 
+2 copy 
+sin mul round dup mul 
+3 1 roll 
+cos mul round dup mul 
+add 1 add 
+dup maxsteps gt {pop maxsteps} if 
+dup minsteps lt {pop minsteps} if 
+}
+ifelse
+} bdf
+/nextrelease defed { 
+/languagelevel defed not { 
+/framebuffer defed { 
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps 
+{
+forcemaxsteps 
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max 
+printerRes div 
+gradfrequency mul 
+round 
+5 max 
+min 
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def 
+/delta -0 def 
+/frac -0 def 
+/height -0 def 
+/left -0 def 
+/numsteps1 -0 def 
+/radius -0 def 
+/right -0 def 
+/top -0 def 
+/width -0 def 
+/xt -0 def 
+/yt -0 def 
+/df currentflat def 
+/tempstr 1 string def 
+/clipflatness currentflat def 
+/inverted? 
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def 
+/tc2 [0 0 0 1] def 
+/storerect{/top xdf /right xdf /bottom xdf /left xdf 
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known 
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup} 
+{dup} ifelse 
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{ 
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def 
+{ 
+exch dup 
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall 
+NF
+}bdf
+/MN{
+1 index length 
+/Len exch def 
+dup length Len add 
+string dup 
+Len 
+4 -1 roll 
+putinterval 
+dup 
+0 
+4 -1 roll 
+putinterval 
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll 
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFJ 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFJ{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCJ} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont 
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFJ 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup 
+hasfont 
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFK 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFK{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCK} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/JCsm
+hasfont 
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFK{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFK 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFTC 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFTC{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCTC} 
+ifelse
+}bdf
+/FDFTC
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/DFMing-Lt-HK-BF
+hasfont 
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFTC 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat 
+exch 
+dup 0 le{pop 1}if 
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if} 
+{exit} 
+ifelse
+}loop 
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf 
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def 
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash 
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont 
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh 
+
+_efh 
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin 
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor { 
+max max max 
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf 
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{ 
+4 index 1 index get 0.3 mul 
+4 index 2 index get 0.59 mul 
+4 index 3 index get 0.11 mul 
+4 index 4 index get 
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx 
+6 -1 roll/exec cvx 
+7 -1 roll/exec cvx 
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx 
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le 
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st 
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop 
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub 
+1.0 dup im ik add min sub 
+1.0 dup iy ik add min sub 
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll 
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll 
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf 
+/setspotcolor { 
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf 
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def 
+/_lfp4 {
+1 pop 
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def 
+/_lfs4 {
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 2 lt {pop 2} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop 
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def 
+/vc{
+AltsysDict /cvc 2 index put 
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf 
+0 setseparationgray
+/imgr {1692.47 1570.59 2287.75 2412.48 } def 
+/bleed 0 def 
+/clpr {1692.47 1570.59 2287.75 2412.48 } def 
+/xs 1 def 
+/ys 1 def 
+/botx 0 def 
+/overlap 0 def 
+/wdist 18 def 
+0 2 mul fhsetspreadsize 
+0 0 ne {/df 0 def /clipflatness 0 def} if 
+/maxsteps 256 def 
+/forcemaxsteps false def 
+/minsteps 0 def 
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end 
+vms
+0.15 0.15 scale %JND
+-1845 -2006 translate
+
+/currentpacking defed{false setpacking}if 
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+1848.4365 2094.0422 m
+1848.4365 2140.987 1886.4917 2179.0422 1933.4365 2179.0422 C
+1980.3813 2179.0422 2018.4365 2140.987 2018.4365 2094.0422 C
+2018.4365 2047.0974 1980.3813 2009.0422 1933.4365 2009.0422 C
+1886.4917 2009.0422 1848.4365 2047.0974 1848.4365 2094.0422 C
+5.3858 w
+3.863693 M
+s 
+n
+true eomode
+1880.5612 2118.7403 m
+1880.5612 2121.7396 1881.6862 2124.8795 1883.9362 2128.1622 C
+1886.1862 2131.4889 1888.4581 2133.1522 1890.7565 2133.1544 C
+1892.2089 2133.1544 1893.4042 2132.5677 1894.3424 2131.3966 C
+1895.3268 2130.2233 1895.819 2128.7467 1895.819 2126.9669 C
+1895.819 2124.0599 1894.6237 2121.0826 1892.233 2118.0372 C
+1889.8885 2114.9896 1887.6144 2113.4669 1885.4127 2113.4669 C
+1884.0526 2113.4669 1882.9034 2113.9591 1881.9674 2114.9435 C
+1881.0292 2115.974 1880.5612 2117.2396 1880.5612 2118.7403 C
+h
+1948.2018 2061.1544 m
+1978.4362 2061.0138 L
+1980.451 2062.6068 1981.9034 2064.3163 1982.7955 2066.1466 C
+1983.7316 2068.0209 1984.1996 2070.2005 1984.2018 2072.6857 C
+1984.2018 2073.2482 L
+1969.2252 2099.6153 L
+1969.2252 2099.3341 1969.2472 2098.8639 1969.2955 2098.2091 C
+1969.3417 2097.5983 1969.3636 2097.1544 1969.3658 2096.8732 C
+1969.3658 2089.888 1967.5597 2083.3732 1963.9518 2077.3263 C
+1960.3878 2071.2794 1955.1385 2065.8873 1948.2018 2061.1544 C
+h
+1905.8737 2139.4825 m
+1910.0924 2124.2247 L
+1964.233 2092.5841 L
+1964.6066 2094.3177 1964.8636 2095.724 1965.0065 2096.8028 C
+1965.1471 2097.9278 1965.2174 2098.9122 1965.2174 2099.756 C
+1965.2174 2100.4108 1965.1691 2101.5599 1965.0768 2103.2013 C
+1964.9823 2103.5748 1964.9362 2103.8561 1964.9362 2104.045 C
+1905.8737 2139.4825 L
+h
+1908.4752 2120.3575 m
+1898.983 2105.5216 L
+1954.3893 2072.8263 L
+1956.4987 2074.7005 1958.2565 2076.8561 1959.6627 2079.295 C
+1961.1151 2081.7779 1962.2863 2084.6608 1963.1783 2087.9435 C
+1908.4752 2120.3575 L
+h
+1896.2408 2102.3575 m
+1880.5612 2099.0528 L
+1942.9283 2062.631 L
+1944.5675 2063.5209 1946.0682 2064.5272 1947.4283 2065.6544 C
+1948.7863 2066.7794 1950.0057 2068.0209 1951.0846 2069.381 C
+1896.2408 2102.3575 L
+h
+1871.2096 2120.7794 m
+1876.3424 2102.3575 L
+1894.2018 2105.9435 L
+1906.1549 2125.2794 L
+1900.8815 2142.506 L
+1882.7408 2139.2013 L
+1871.2096 2120.7794 L
+h
+1866.7096 2121.4825 m
+1880.1393 2142.3653 L
+1901.3033 2146.5841 L
+1963.6705 2109.3888 L
+1968.0299 2106.8092 1971.005 2103.9747 1972.6002 2100.881 C
+1972.8815 2100.2701 1973.1144 2099.8021 1973.3033 2099.4747 C
+1991.444 2068.256 L
+1991.6769 2067.8341 1992.0043 2067.2474 1992.4283 2066.4982 C
+1994.0675 2064.013 1994.8871 2062.0904 1994.8893 2060.7325 C
+1994.8893 2059.4186 1994.3971 2058.4825 1993.4127 2057.92 C
+1992.4745 2057.4037 1990.6705 2057.1466 1987.9987 2057.1466 C
+1948.0612 2057.1466 L
+1946.4198 2057.1466 1944.7784 2057.4037 1943.1393 2057.92 C
+1941.4979 2058.4825 1939.4127 2059.513 1936.8815 2061.0138 C
+1873.6705 2098.631 L
+1866.7096 2121.4825 L
+true setoverprint
+f 
+false setoverprint
+n
+vmr
+vmr
+end
+%%Trailer
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/note.pdf b/docs-xml/xslt/db2latex-xsl/xsl/figures/note.pdf
new file mode 100644
index 00000000000..ec6c248a2a9
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/note.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/tip.eps b/docs-xml/xslt/db2latex-xsl/xsl/figures/tip.eps
new file mode 100644
index 00000000000..a28ad883eb7
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/tip.eps
@@ -0,0 +1,1503 @@
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-1
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/07/16 10:41 PM
+%%BoundingBox: 0 0 27 27
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-1
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-1
+%ALDBoundingBox: -153 -436 442 406
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if 
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put 
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub 
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed { 
+_NXLevel2 not { 
+/colorimage where {
+userdict eq {
+/_rci false def 
+} if
+} if
+} if
+} if
+/md defed{ 
+md type /dicttype eq { 
+/colorimage where { 
+md eq { 
+/_rci false def 
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if 
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add 
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf 
+}ifelse
+/privrectpath { 
+4 -2 roll m
+dtransform round exch round exch idtransform 
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed 
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/` 
+{ 
+false setoverprint 
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1 
+statusdict begin
+/processcolors defed 
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end 
+def
+/printerRes 
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency} 
+{GrayAngle GrayFrequency} 
+{0 Width Height matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60} 
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch 
+}
+ifelse
+printerRes 300 max exch div exch 
+2 copy 
+sin mul round dup mul 
+3 1 roll 
+cos mul round dup mul 
+add 1 add 
+dup maxsteps gt {pop maxsteps} if 
+dup minsteps lt {pop minsteps} if 
+}
+ifelse
+} bdf
+/nextrelease defed { 
+/languagelevel defed not { 
+/framebuffer defed { 
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps 
+{
+forcemaxsteps 
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max 
+printerRes div 
+gradfrequency mul 
+round 
+5 max 
+min 
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def 
+/delta -0 def 
+/frac -0 def 
+/height -0 def 
+/left -0 def 
+/numsteps1 -0 def 
+/radius -0 def 
+/right -0 def 
+/top -0 def 
+/width -0 def 
+/xt -0 def 
+/yt -0 def 
+/df currentflat def 
+/tempstr 1 string def 
+/clipflatness currentflat def 
+/inverted? 
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def 
+/tc2 [0 0 0 1] def 
+/storerect{/top xdf /right xdf /bottom xdf /left xdf 
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known 
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup} 
+{dup} ifelse 
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{ 
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def 
+{ 
+exch dup 
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall 
+NF
+}bdf
+/MN{
+1 index length 
+/Len exch def 
+dup length Len add 
+string dup 
+Len 
+4 -1 roll 
+putinterval 
+dup 
+0 
+4 -1 roll 
+putinterval 
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll 
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFJ 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFJ{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCJ} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont 
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFJ 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup 
+hasfont 
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFK 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFK{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCK} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/JCsm
+hasfont 
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFK{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFK 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFTC 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFTC{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCTC} 
+ifelse
+}bdf
+/FDFTC
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/DFMing-Lt-HK-BF
+hasfont 
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFTC 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat 
+exch 
+dup 0 le{pop 1}if 
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if} 
+{exit} 
+ifelse
+}loop 
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf 
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def 
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash 
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont 
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh 
+
+_efh 
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin 
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor { 
+max max max 
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf 
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{ 
+4 index 1 index get 0.3 mul 
+4 index 2 index get 0.59 mul 
+4 index 3 index get 0.11 mul 
+4 index 4 index get 
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx 
+6 -1 roll/exec cvx 
+7 -1 roll/exec cvx 
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx 
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le 
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st 
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop 
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub 
+1.0 dup im ik add min sub 
+1.0 dup iy ik add min sub 
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll 
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll 
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf 
+/setspotcolor { 
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf 
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def 
+/_lfp4 {
+1 pop 
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def 
+/_lfs4 {
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 2 lt {pop 2} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop 
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def 
+/vc{
+AltsysDict /cvc 2 index put 
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf 
+0 setseparationgray
+/imgr {1692.47 1570.59 2287.75 2412.48 } def 
+/bleed 0 def 
+/clpr {1692.47 1570.59 2287.75 2412.48 } def 
+/xs 1 def 
+/ys 1 def 
+/botx 0 def 
+/overlap 0 def 
+/wdist 18 def 
+0 2 mul fhsetspreadsize 
+0 0 ne {/df 0 def /clipflatness 0 def} if 
+/maxsteps 256 def 
+/forcemaxsteps false def 
+/minsteps 0 def 
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end 
+vms
+0.15 0.15 scale %JND
+-1845 -2006 translate
+
+/currentpacking defed{false setpacking}if 
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+1848.4365 2094.0422 m
+1848.4365 2140.987 1886.4917 2179.0422 1933.4365 2179.0422 C
+1980.3813 2179.0422 2018.4365 2140.987 2018.4365 2094.0422 C
+2018.4365 2047.0974 1980.3813 2009.0422 1933.4365 2009.0422 C
+1886.4917 2009.0422 1848.4365 2047.0974 1848.4365 2094.0422 C
+5.3858 w
+3.863693 M
+s 
+n
+true eomode
+1897.6516 2067.1709 m
+1897.6087 2066.5538 L
+1885.3743 2066.1319 L
+1883.1946 2062.4053 L
+1869.9055 2063.9522 L
+1869.9055 2067.1712 L
+1897.6516 2067.1709 L
+h
+1944.0852 2067.1709 m
+1944.0852 2067.0077 1944.0852 2066.8741 1944.0852 2066.7647 C
+1944.1314 2066.5757 1944.1775 2066.4131 1944.2258 2066.2725 C
+1945.0213 2065.0992 1946.0056 2064.2554 1947.179 2063.7413 C
+1948.3963 2063.2249 1950.0134 2062.9678 1952.0305 2062.9678 C
+1956.0142 2062.9678 1959.7627 2063.9522 1963.2805 2065.9209 C
+1964.0204 2066.3353 1964.6824 2066.7527 1965.2665 2067.1732 C
+1971.313 2067.1709 L
+1970.2122 2065.693 1968.5893 2064.3153 1966.4446 2063.0381 C
+1962.0369 2060.4585 1956.8821 2059.1709 1950.9758 2059.1709 C
+1948.6775 2059.1709 1946.7791 2059.5445 1945.2805 2060.2959 C
+1943.7798 2061.0914 1942.5142 2062.357 1941.4837 2064.0928 C
+1941.2486 2064.0928 1940.8728 2064.0928 1940.3587 2064.0928 C
+1937.5462 2063.9039 1935.4829 2063.8116 1934.1712 2063.8116 C
+1929.2954 2063.8116 1925.1228 2064.2796 1921.6555 2065.2178 C
+1919.9787 2065.6936 1918.2362 2066.3443 1916.4282 2067.1704 C
+1944.0852 2067.1709 L
+true setoverprint
+f 
+false setoverprint
+n
+1884.4125 2075.1709 m
+1884.4602 2073.585 L
+1893.1087 2073.0225 L
+1893.1087 2075.1712 L
+1910.8456 2075.1709 L
+1910.98 2075.0913 1911.1146 2075.0069 1911.2493 2074.9209 C
+1911.9986 2074.3584 1912.583 2073.9585 1913.0071 2073.7256 C
+1916.804 2071.4756 1920.2954 2069.9288 1923.4837 2069.085 C
+1926.718 2068.2413 1931.0071 2067.8194 1936.3508 2067.8194 C
+1940.3587 2067.8194 L
+1940.7805 2070.7022 L
+1938.9524 2070.8428 1937.522 2071.4053 1936.4915 2072.3897 C
+1935.7726 2073.1422 1935.3163 2074.0693 1935.1223 2075.1726 C
+1940.1696 2075.1709 L
+1940.3293 2074.9768 1940.5095 2074.8018 1940.7102 2074.6397 C
+1941.7407 2073.8421 1943.147 2073.4444 1944.929 2073.4444 C
+1948.4128 2073.4444 1951.8259 2074.0193 1955.1674 2075.169 C
+1963.5704 2075.1709 L
+1962.8877 2074.843 1962.0411 2074.4337 1961.0305 2073.9366 C
+1958.1697 2072.5303 1955.2166 2071.4976 1952.1712 2070.8428 C
+1951.3274 2070.7022 1950.2244 2070.5132 1948.8665 2070.2803 C
+1945.6782 2069.7178 1944.0852 2068.8038 1944.0852 2067.5381 C
+1944.0852 2067.4017 1944.0852 2067.2776 1944.0852 2067.1658 C
+1916.4282 2067.1709 L
+1914.4953 2068.0535 1912.4877 2069.1369 1910.4055 2070.4209 C
+1910.0759 2070.6539 1909.6321 2070.9593 1909.0696 2071.335 C
+1905.9275 2073.5367 1902.9041 2074.6375 1899.9993 2074.6397 C
+1899.9509 2074.6397 1899.6939 2074.6155 1899.2258 2074.5694 C
+1898.7556 2074.521 1898.4041 2074.5452 1898.1712 2074.6397 C
+1897.6516 2067.1709 L
+1869.9055 2067.1709 L
+1869.9055 2075.1714 L
+1884.4125 2075.1709 L
+h
+1972.5022 2075.1709 m
+1972.8687 2074.2606 1973.0523 2073.2652 1973.054 2072.1788 C
+1973.054 2070.3983 1972.4736 2068.7289 1971.313 2067.1709 C
+1965.2666 2067.1709 L
+1967.4581 2068.751 1968.554 2070.3727 1968.554 2072.0381 C
+1968.554 2073.0686 1968.2486 2073.9827 1967.6399 2074.7803 C
+1967.5373 2074.922 1967.4334 2075.0518 1967.3283 2075.1698 C
+1972.5022 2075.1709 L
+true setoverprint
+f 
+false setoverprint
+n
+1869.9055 2075.1709 m
+1869.9055 2119.0772 L
+1897.1868 2119.8506 L
+1897.8899 2114.2256 L
+1899.2962 2114.2256 L
+1901.0759 2114.2256 1902.7876 2114.5069 1904.429 2115.0694 C
+1906.1165 2115.678 1908.2478 2116.825 1910.8274 2118.5147 C
+1911.9524 2119.2178 L
+1919.5923 2124.1397 1925.4041 2126.6006 1929.3899 2126.6006 C
+1930.8423 2126.6006 1932.3408 2126.3655 1933.8899 2125.8975 C
+1935.4368 2125.4756 1937.1463 2124.7945 1939.0227 2123.8584 C
+1940.1939 2123.9046 1941.8814 2123.9507 1944.0852 2123.9991 C
+1950.0376 2124.0914 1954.0674 2124.1375 1956.179 2124.1397 C
+1972.7244 2124.1397 1984.583 2123.1311 1991.7571 2121.1163 C
+1998.9751 2119.1475 2002.583 2115.9351 2002.5852 2111.4834 C
+2002.5852 2107.8272 2000.2869 2105.2959 1995.6946 2103.8897 C
+1991.1463 2102.5296 1981.865 2101.8506 1967.8508 2101.8506 C
+1963.5618 2101.8506 L
+1964.6384 2100.8179 1965.4361 2099.8116 1965.9524 2098.8272 C
+1966.4666 2097.8428 1966.7236 2096.8343 1966.7258 2095.8038 C
+1966.7258 2095.3335 1966.6314 2094.7952 1966.4446 2094.1866 C
+1966.2556 2093.6241 1965.9041 2092.8506 1965.3899 2091.8663 C
+1967.1697 2091.1631 1968.5056 2090.1788 1969.3977 2088.9131 C
+1970.2876 2087.6936 1970.7315 2086.1929 1970.7337 2084.4131 C
+1970.7337 2083.521 1970.615 2082.6311 1970.3821 2081.7413 C
+1970.147 2080.8492 1969.7954 2079.9593 1969.3274 2079.0694 C
+1970.5447 2078.2256 1971.4588 2077.2171 1972.0696 2076.0459 C
+1972.2346 2075.7625 1972.3788 2075.4685 1972.5022 2075.1642 C
+1967.3284 2075.1709 L
+1966.8077 2075.7539 1966.2562 2076.0459 1965.6712 2076.0459 C
+1965.5191 2076.0459 1964.8189 2075.7521 1963.5704 2075.1643 C
+1955.1674 2075.1709 L
+1956.5004 2075.6277 1957.8219 2076.1778 1959.1321 2076.8194 C
+1963.7727 2079.1155 1966.093 2081.5523 1966.093 2084.1319 C
+1966.093 2085.303 1965.7173 2086.2632 1964.968 2087.0147 C
+1964.2649 2087.764 1963.3508 2088.1375 1962.2258 2088.1397 C
+1961.7556 2088.1397 1959.0838 2086.9905 1954.2102 2084.6944 C
+1949.3806 2082.396 1944.4368 2080.6624 1939.3743 2079.4913 C
+1939.2798 2079.3023 1939.2337 2079.0914 1939.2337 2078.8584 C
+1939.2337 2078.6695 1939.2337 2078.3663 1939.2337 2077.9444 C
+1939.2337 2076.8248 1939.5456 2075.8974 1940.1695 2075.1644 C
+1935.1224 2075.1709 L
+1935.0507 2075.5803 1935.0149 2076.012 1935.0149 2076.4678 C
+1935.0149 2076.8414 1935.0369 2077.2391 1935.0852 2077.6631 C
+1935.1775 2078.085 1935.294 2078.5992 1935.4368 2079.21 C
+1934.7337 2079.21 L
+1931.9673 2079.21 1929.7876 2080.0296 1928.1946 2081.6709 C
+1926.5994 2083.3101 1925.804 2085.514 1925.804 2088.2803 C
+1925.804 2088.9834 L
+1924.3032 2088.6077 1922.9673 2088.3265 1921.7962 2088.1397 C
+1920.6712 2087.9507 1919.6626 2087.8584 1918.7727 2087.8584 C
+1916.8501 2087.8584 1914.9517 2088.232 1913.0774 2088.9834 C
+1911.2493 2089.7789 1909.2102 2091.0906 1906.9602 2092.9209 C
+1906.8196 2094.6084 L
+1909.1619 2093.7647 1911.2713 2093.1077 1913.1477 2092.6397 C
+1915.022 2092.2178 1916.7556 2092.0069 1918.3508 2092.0069 C
+1920.6931 2092.0069 1922.9431 2092.521 1925.1008 2093.5538 C
+1927.3025 2094.5843 1929.5986 2096.2476 1931.9915 2098.5459 C
+1925.804 2107.7569 L
+1927.0696 2109.4444 L
+1928.4275 2108.3655 1930.2556 2106.7945 1932.554 2104.7334 C
+1938.2251 2099.6226 1942.9361 2097.0694 1946.6868 2097.0694 C
+1948.5149 2097.0694 1950.1782 2097.5132 1951.679 2098.4053 C
+1953.2258 2099.2952 1953.9993 2100.1851 1953.9993 2101.0772 C
+1953.9993 2101.6397 1952.9446 2103.1866 1950.8352 2105.7178 C
+1948.772 2108.2491 1946.1946 2111.0374 1943.1008 2114.085 C
+1939.4446 2117.6006 1936.7244 2119.8023 1934.9446 2120.6944 C
+1933.2088 2121.6304 1931.3103 2122.0984 1929.2493 2122.1006 C
+1925.3579 2122.1006 1920.3657 2120.0374 1914.2727 2115.9131 C
+1913.5696 2115.4913 1913.0532 2115.1617 1912.7258 2114.9288 C
+1909.6321 2112.8194 1907.1228 2111.4131 1905.2024 2110.71 C
+1903.2798 2110.053 1901.2166 2109.7256 1899.0149 2109.7256 C
+1898.0305 2109.7256 L
+1898.0305 2078.6475 L
+1899.8587 2078.6475 L
+1903.4329 2078.6475 1907.0952 2077.4884 1910.8456 2075.1742 C
+1893.1087 2075.1709 L
+1893.1087 2115.7725 L
+1883.1946 2115.6319 L
+1884.4125 2075.171 L
+1869.9055 2075.1709 L
+h
+1957.9368 2101.0772 m
+1957.3259 2098.5459 1956.0603 2096.6695 1954.1399 2095.4522 C
+1952.2634 2094.2327 1949.6399 2093.6241 1946.2649 2093.6241 C
+1945.1861 2093.6241 1943.615 2093.9273 1941.554 2094.5381 C
+1939.5369 2095.1929 1938.0383 2095.5203 1937.054 2095.5225 C
+1935.3665 2095.5225 1933.679 2094.8194 1931.9915 2093.4131 C
+1930.3501 2092.0069 1929.5305 2090.5765 1929.5305 2089.1241 C
+1929.5305 2087.107 1930.0447 2085.5601 1931.0774 2084.4834 C
+1932.1079 2083.4507 1933.6065 2082.9366 1935.5774 2082.9366 C
+1937.5462 2082.9366 1940.1477 2083.4046 1943.3821 2084.3428 C
+1946.6626 2085.3272 1949.9673 2086.5928 1953.2962 2088.1397 C
+1956.3416 2089.5459 1958.5674 2090.8819 1959.9758 2092.1475 C
+1961.3821 2093.4131 1962.0852 2094.6788 1962.0852 2095.9444 C
+1962.0852 2096.8343 1961.7556 2097.678 1961.1008 2098.4756 C
+1960.4439 2099.3194 1959.3892 2100.1851 1957.9368 2101.0772 C
+h
+1943.3821 2119.71 m
+1946.054 2117.1788 1948.3501 2114.8584 1950.2727 2112.7491 C
+1952.2415 2110.6397 1954.0213 2108.5303 1955.6165 2106.4209 C
+1958.5696 2106.1397 1961.2876 2105.9288 1963.7727 2105.7881 C
+1966.304 2105.6475 1968.6243 2105.5772 1970.7337 2105.5772 C
+1980.7642 2105.5772 1987.7471 2106.021 1991.6868 2106.9131 C
+1995.6704 2107.803 1997.6611 2109.3719 1997.6633 2111.6241 C
+1997.6633 2114.4366 1994.2883 2116.5459 1987.5383 2117.9522 C
+1980.8345 2119.4046 1970.8259 2120.1297 1957.5149 2120.1319 C
+1955.4055 2120.1319 1953.1555 2120.0835 1950.7649 2119.9913 C
+1948.4204 2119.9429 1945.9595 2119.8506 1943.3821 2119.71 C
+true setoverprint
+f 
+false setoverprint
+n
+vmr
+vmr
+end
+%%Trailer
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/tip.pdf b/docs-xml/xslt/db2latex-xsl/xsl/figures/tip.pdf
new file mode 100644
index 00000000000..54f5dedb5d4
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/tip.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/warning.eps b/docs-xml/xslt/db2latex-xsl/xsl/figures/warning.eps
new file mode 100644
index 00000000000..c9473b72720
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/warning.eps
@@ -0,0 +1,1348 @@
+%!PS-Adobe-2.0 EPSF-1.2
+%%Title: Untitled-3
+%%Creator: FreeHand 9.0
+%%CreationDate: 2002/12/05 8:20 PM
+%%BoundingBox: 0 0 29 29
+%%FHPathName:Untitled:FreeHand 9:English:Untitled-3
+%ALDOriginalFile:Untitled:FreeHand 9:English:Untitled-3
+%ALDBoundingBox: -2 -2 29 29
+%%FHPageNum:1
+%%DocumentSuppliedResources: procset Altsys_header 4 0
+%%ColorUsage: Color
+%%DocumentProcessColors: Black
+%%EndComments
+%%BeginResource: procset Altsys_header 4 0
+userdict begin /AltsysDict 300 dict def end
+AltsysDict begin
+/bdf{bind def}bind def
+/xdf{exch def}bdf
+/defed{where{pop true}{false}ifelse}bdf
+/ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf
+/d{setdash}bdf
+/h{closepath}bdf
+/H{}bdf
+/J{setlinecap}bdf
+/j{setlinejoin}bdf
+/M{setmiterlimit}bdf
+/n{newpath}bdf
+/N{newpath}bdf
+/q{gsave}bdf
+/Q{grestore}bdf
+/w{setlinewidth}bdf
+/Xic{matrix invertmatrix concat}bdf
+/Xq{matrix currentmatrix mark}bdf
+/XQ{cleartomark setmatrix}bdf
+/sepdef{
+dup where not
+{
+AltsysSepDict
+}
+if 
+3 1 roll exch put
+}bdf
+/st{settransfer}bdf
+/colorimage defed /_rci xdf
+/cntr 0 def
+/readbinarystring{
+/cntr 0 def
+2 copy readstring
+{
+{
+dup
+(\034) search
+{
+length exch pop exch
+dup length 0 ne
+{
+dup dup 0 get 32 sub 0 exch put 
+/cntr cntr 1 add def
+}
+{
+pop 1 string dup
+0 6 index read pop 32 sub put
+}ifelse
+3 copy
+putinterval pop
+1 add
+1 index length 1 sub
+1 index sub 
+dup 0 le {pop pop exit}if
+getinterval
+}
+{
+pop exit
+} ifelse
+} loop
+}if
+cntr 0 gt
+{
+pop 2 copy
+dup length cntr sub cntr getinterval
+readbinarystring
+} if
+pop exch pop
+} bdf
+/_NXLevel2 defed { 
+_NXLevel2 not { 
+/colorimage where {
+userdict eq {
+/_rci false def 
+} if
+} if
+} if
+} if
+/md defed{ 
+md type /dicttype eq { 
+/colorimage where { 
+md eq { 
+/_rci false def 
+}if
+}if
+/settransfer where {
+md eq {
+/st systemdict /settransfer get def
+}if
+}if
+}if 
+}if
+/setstrokeadjust defed
+{
+true setstrokeadjust
+/C{curveto}bdf
+/L{lineto}bdf
+/m{moveto}bdf
+}
+{
+/dr{transform .25 sub round .25 add 
+exch .25 sub round .25 add exch itransform}bdf
+/C{dr curveto}bdf
+/L{dr lineto}bdf
+/m{dr moveto}bdf
+/setstrokeadjust{pop}bdf 
+}ifelse
+/privrectpath { 
+4 -2 roll m
+dtransform round exch round exch idtransform 
+2 copy 0 lt exch 0 lt xor
+{dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto}
+{exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto}
+ifelse
+closepath
+}bdf
+/rectclip{newpath privrectpath clip newpath}def
+/rectfill{gsave newpath privrectpath fill grestore}def
+/rectstroke{gsave newpath privrectpath stroke grestore}def
+/_fonthacksave false def
+/currentpacking defed 
+{
+/_bfh {/_fonthacksave currentpacking def false setpacking} bdf
+/_efh {_fonthacksave setpacking} bdf
+}
+{
+/_bfh {} bdf
+/_efh {} bdf
+}ifelse
+/packedarray{array astore readonly}ndf
+/` 
+{ 
+false setoverprint 
+/-save0- save def
+5 index concat
+pop
+storerect left bottom width height rectclip
+pop
+/MMdict_count countdictstack def
+/MMop_count count 1 sub def
+userdict begin
+/showpage {} def
+0 setgray 0 setlinecap 1 setlinewidth
+0 setlinejoin 10 setmiterlimit [] 0 setdash newpath
+} bdf
+/currentpacking defed{true setpacking}if
+/min{2 copy gt{exch}if pop}bdf
+/max{2 copy lt{exch}if pop}bdf
+/xformfont { currentfont exch makefont setfont } bdf
+/fhnumcolors 1 
+statusdict begin
+/processcolors defed 
+{
+pop processcolors
+}
+{
+/deviceinfo defed {
+deviceinfo /Colors known {
+pop deviceinfo /Colors get
+} if
+} if
+} ifelse
+end 
+def
+/printerRes 
+gsave
+matrix defaultmatrix setmatrix
+72 72 dtransform
+abs exch abs
+max
+grestore
+def
+/graycalcs
+[
+{Angle Frequency} 
+{GrayAngle GrayFrequency} 
+{0 Width Height matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+{0 GrayWidth GrayHeight matrix defaultmatrix idtransform 
+dup mul exch dup mul add sqrt 72 exch div} 
+] def
+/calcgraysteps {
+forcemaxsteps
+{
+maxsteps
+}
+{
+/currenthalftone defed
+{currenthalftone /dicttype eq}{false}ifelse
+{
+currenthalftone begin
+HalftoneType 4 le
+{graycalcs HalftoneType 1 sub get exec}
+{
+HalftoneType 5 eq
+{
+Default begin
+{graycalcs HalftoneType 1 sub get exec}
+end
+}
+{0 60} 
+ifelse
+}
+ifelse
+end
+}
+{
+currentscreen pop exch 
+}
+ifelse
+printerRes 300 max exch div exch 
+2 copy 
+sin mul round dup mul 
+3 1 roll 
+cos mul round dup mul 
+add 1 add 
+dup maxsteps gt {pop maxsteps} if 
+dup minsteps lt {pop minsteps} if 
+}
+ifelse
+} bdf
+/nextrelease defed { 
+/languagelevel defed not { 
+/framebuffer defed { 
+0 40 string framebuffer 9 1 roll 8 {pop} repeat
+dup 516 eq exch 520 eq or
+{
+/fhnumcolors 3 def
+/currentscreen {60 0 {pop pop 1}}bdf
+/calcgraysteps {maxsteps} bdf
+}if
+}if
+}if
+}if
+fhnumcolors 1 ne {
+/calcgraysteps {maxsteps} bdf
+} if
+/currentpagedevice defed {
+currentpagedevice /PreRenderingEnhance known
+{
+currentpagedevice /PreRenderingEnhance get
+{
+/calcgraysteps 
+{
+forcemaxsteps 
+{maxsteps}
+{256 maxsteps min}
+ifelse
+} def
+} if
+} if
+} if
+/gradfrequency 144 def
+printerRes 1000 lt {
+/gradfrequency 72 def
+} if
+/adjnumsteps {
+dup dtransform abs exch abs max 
+printerRes div 
+gradfrequency mul 
+round 
+5 max 
+min 
+}bdf
+/goodsep {
+spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or
+}bdf
+/BeginGradation defed
+{/bb{BeginGradation}bdf}
+{/bb{}bdf}
+ifelse
+/EndGradation defed
+{/eb{EndGradation}bdf}
+{/eb{}bdf}
+ifelse
+/bottom -0 def 
+/delta -0 def 
+/frac -0 def 
+/height -0 def 
+/left -0 def 
+/numsteps1 -0 def 
+/radius -0 def 
+/right -0 def 
+/top -0 def 
+/width -0 def 
+/xt -0 def 
+/yt -0 def 
+/df currentflat def 
+/tempstr 1 string def 
+/clipflatness currentflat def 
+/inverted? 
+0 currenttransfer exec .5 ge def
+/tc1 [0 0 0 1] def 
+/tc2 [0 0 0 1] def 
+/storerect{/top xdf /right xdf /bottom xdf /left xdf 
+/width right left sub def /height top bottom sub def}bdf
+/concatprocs{
+systemdict /packedarray known 
+{dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+proc1 aload pop proc2 aload pop
+proc1 length proc2 length add packedarray cvx
+}
+{ 
+/proc2 exch cvlit def /proc1 exch cvlit def
+/newproc proc1 length proc2 length add array def
+newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval
+newproc cvx
+}ifelse
+}bdf
+/i{dup 0 eq
+{pop df dup} 
+{dup} ifelse 
+/clipflatness xdf setflat
+}bdf
+version cvr 38.0 le
+{/setrgbcolor{
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+currenttransfer exec 3 1 roll
+setrgbcolor}bdf}if
+/vms {/vmsv save def} bdf
+/vmr {vmsv restore} bdf
+/vmrs{vmsv restore /vmsv save def}bdf
+/eomode{ 
+{/filler /eofill load def /clipper /eoclip load def}
+{/filler /fill load def /clipper /clip load def}
+ifelse
+}bdf
+/normtaper{}bdf
+/logtaper{9 mul 1 add log}bdf
+/CD{
+/NF exch def 
+{ 
+exch dup 
+/FID ne 1 index/UniqueID ne and
+{exch NF 3 1 roll put}
+{pop pop}
+ifelse
+}forall 
+NF
+}bdf
+/MN{
+1 index length 
+/Len exch def 
+dup length Len add 
+string dup 
+Len 
+4 -1 roll 
+putinterval 
+dup 
+0 
+4 -1 roll 
+putinterval 
+}bdf
+/RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch
+{1 index MN cvn/NewN exch def cvn
+findfont dup maxlength dict CD dup/FontName NewN put dup
+/Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf
+/RF{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RC}
+ifelse
+}bdf
+/FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known
+{exch pop findfont 3 -1 roll pop}
+{pop dup findfont dup maxlength dict CD dup dup
+/Encoding exch /Encoding get 256 array copy 7 -1 roll 
+{3 -1 roll dup 4 -2 roll put}forall put definefont}
+ifelse}bdf
+/RCJ{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFJ 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFJ{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCJ} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFJ
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/Ryumin-Light-83pv-RKSJ-H
+hasfont 
+{
+/Ryumin-Light-83pv-RKSJ-H
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFJ{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFJ 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/GS {
+dup 
+hasfont 
+{
+findfont
+exch makesetfont
+exch
+pop
+ts
+}
+{
+pop pop pop
+ts
+} ifelse
+} bdf
+/RCK{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFK 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFK{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCK} 
+ifelse
+}bdf
+/hasfont
+{
+/resourcestatus where 
+{
+pop 
+/Font resourcestatus
+{ 
+pop pop true
+}
+{ 
+false
+}
+ifelse
+}
+{
+dup FontDirectory exch known
+{pop true}
+{
+256 string
+cvs
+(fonts/) exch MN
+status
+{pop pop pop pop true}
+{false}
+ifelse
+}
+ifelse
+}
+ifelse
+}bdf
+/FDFK
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/JCsm
+hasfont 
+{
+/JCsm
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFK{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFK 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/RCTC{4 -1 roll 
+/ourvec xdf 
+256 string cvs 
+(|______) anchorsearch
+{pop 
+cvn 
+dup FDFTC 
+exch 
+1 index 
+eq 
+{
+_bfh findfont _efh 
+dup 
+maxlength dict 
+CD 
+dup 
+/FontName 
+3 index 
+put 
+dup 
+/Encoding ourvec put 
+1 index 
+exch 
+definefont 
+pop 
+}
+{exch pop} 
+ifelse
+}
+{pop} 
+ifelse
+}bdf
+/RFTC{ 
+dup 
+FontDirectory exch 
+known 
+{pop 3 -1 roll pop} 
+{RCTC} 
+ifelse
+}bdf
+/FDFTC
+{
+dup 
+hasfont 
+not 
+{ 
+pop
+/DFMing-Lt-HK-BF
+hasfont 
+{
+/DFMing-Lt-HK-BF
+}
+{
+/Courier
+}
+ifelse 
+}
+if
+}bdf
+/FFTC{
+_bfh
+dup 
+256 string cvs 
+(|______)exch MN 
+cvn 
+dup 
+FontDirectory
+exch known 
+{ 
+exch 
+pop 
+findfont 
+3 -1 roll 
+pop 
+}
+{ 
+pop 
+FDFTC 
+dup findfont 
+dup maxlength dict 
+CD 
+dup dup 
+/Encoding exch 
+/Encoding get 
+256 array copy 
+7 -1 roll 
+{ 
+3 -1 roll 
+dup 
+4 -2 roll 
+put 
+}forall
+put 
+definefont 
+}
+ifelse
+_efh
+}bdf
+/fps{
+currentflat 
+exch 
+dup 0 le{pop 1}if 
+{
+dup setflat 3 index stopped
+{1.3 mul dup 3 index gt{pop setflat pop pop stop}if} 
+{exit} 
+ifelse
+}loop 
+pop setflat pop pop
+}bdf
+/fp{100 currentflat fps}bdf
+/clipper{clip}bdf 
+/W{/clipper load 100 clipflatness dup setflat fps}bdf
+
+userdict begin /BDFontDict 29 dict def end
+BDFontDict begin
+/bu{}def
+/bn{}def
+/setTxMode{av 70 ge{pop}if pop}def
+/gm{m}def
+/show{pop}def
+/gr{pop}def
+/fnt{pop pop pop}def
+/fs{pop}def
+/fz{pop}def
+/lin{pop pop}def
+/:M {pop pop} def
+/sf {pop} def
+/S {pop} def
+/@b {pop pop pop pop pop pop pop pop} def
+/_bdsave /save load def
+/_bdrestore /restore load def
+/save { dup /fontsave eq {null} {_bdsave} ifelse } def
+/restore { dup null eq { pop } { _bdrestore } ifelse } def
+/fontsave null def
+end
+/MacVec 256 array def 
+MacVec 0 /Helvetica findfont
+/Encoding get 0 128 getinterval putinterval
+MacVec 127 /DEL put MacVec 16#27 /quotesingle put MacVec 16#60 /grave put
+/NUL/SOH/STX/ETX/EOT/ENQ/ACK/BEL/BS/HT/LF/VT/FF/CR/SO/SI
+/DLE/DC1/DC2/DC3/DC4/NAK/SYN/ETB/CAN/EM/SUB/ESC/FS/GS/RS/US
+MacVec 0 32 getinterval astore pop
+/Adieresis/Aring/Ccedilla/Eacute/Ntilde/Odieresis/Udieresis/aacute
+/agrave/acircumflex/adieresis/atilde/aring/ccedilla/eacute/egrave
+/ecircumflex/edieresis/iacute/igrave/icircumflex/idieresis/ntilde/oacute
+/ograve/ocircumflex/odieresis/otilde/uacute/ugrave/ucircumflex/udieresis
+/dagger/degree/cent/sterling/section/bullet/paragraph/germandbls
+/registered/copyright/trademark/acute/dieresis/notequal/AE/Oslash
+/infinity/plusminus/lessequal/greaterequal/yen/mu/partialdiff/summation
+/product/pi/integral/ordfeminine/ordmasculine/Omega/ae/oslash 
+/questiondown/exclamdown/logicalnot/radical/florin/approxequal/Delta/guillemotleft
+/guillemotright/ellipsis/nbspace/Agrave/Atilde/Otilde/OE/oe
+/endash/emdash/quotedblleft/quotedblright/quoteleft/quoteright/divide/lozenge
+/ydieresis/Ydieresis/fraction/currency/guilsinglleft/guilsinglright/fi/fl
+/daggerdbl/periodcentered/quotesinglbase/quotedblbase
+/perthousand/Acircumflex/Ecircumflex/Aacute
+/Edieresis/Egrave/Iacute/Icircumflex/Idieresis/Igrave/Oacute/Ocircumflex
+/apple/Ograve/Uacute/Ucircumflex/Ugrave/dotlessi/circumflex/tilde
+/macron/breve/dotaccent/ring/cedilla/hungarumlaut/ogonek/caron
+MacVec 128 128 getinterval astore pop
+/findheaderfont {
+/Helvetica findfont 
+} def
+end %. AltsysDict
+%%EndResource
+%%EndProlog
+
+%%BeginSetup
+
+AltsysDict begin
+_bfh 
+
+_efh 
+end %. AltsysDict
+
+%%EndSetup
+AltsysDict begin 
+
+/onlyk4{false}ndf
+/ccmyk{dup 5 -1 roll sub 0 max exch}ndf
+/cmyk2gray{
+4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul
+add add add 1 min neg 1 add
+}bdf
+/setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf
+/maxcolor { 
+max max max 
+} ndf
+/maxspot {
+pop
+} ndf
+/setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf
+/findcmykcustomcolor{5 packedarray}ndf
+/setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf
+/setseparationgray{setgray}ndf
+/setoverprint{pop}ndf 
+/currentoverprint false ndf
+/cmykbufs2gray{
+0 1 2 index length 1 sub
+{ 
+4 index 1 index get 0.3 mul 
+4 index 2 index get 0.59 mul 
+4 index 3 index get 0.11 mul 
+4 index 4 index get 
+add add add cvi 255 min
+255 exch sub
+2 index 3 1 roll put
+}for
+4 1 roll pop pop pop
+}bdf
+/colorimage{
+pop pop
+[
+5 -1 roll/exec cvx 
+6 -1 roll/exec cvx 
+7 -1 roll/exec cvx 
+8 -1 roll/exec cvx
+/cmykbufs2gray cvx
+]cvx 
+image
+}
+%. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only)
+version cvr 47.1 le 
+statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse
+and{userdict begin bdf end}{ndf}ifelse
+fhnumcolors 1 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+ic im iy ik cmyk2gray /xt xdf
+currenttransfer
+{dup 1.0 exch sub xt mul add}concatprocs
+st 
+image
+}
+ifelse
+}ndf
+fhnumcolors 1 ne {yt restore} if
+fhnumcolors 3 ne {/yt save def} if
+/customcolorimage{
+aload pop 
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+1.0 dup ic ik add min sub 
+1.0 dup im ik add min sub 
+1.0 dup iy ik add min sub 
+/ic xdf /iy xdf /im xdf
+currentcolortransfer
+4 1 roll 
+{dup 1.0 exch sub ic mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub iy mul add}concatprocs 4 1 roll 
+{dup 1.0 exch sub im mul add}concatprocs 4 1 roll 
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 3 ne {yt restore} if
+fhnumcolors 4 ne {/yt save def} if
+/customcolorimage{
+aload pop
+(_vc_Registration) eq 
+{
+pop pop pop pop separationimage
+}
+{
+/ik xdf /iy xdf /im xdf /ic xdf
+currentcolortransfer
+{1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll
+{1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll
+setcolortransfer
+{/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy}
+true 4 colorimage
+}
+ifelse
+}ndf
+fhnumcolors 4 ne {yt restore} if
+/separationimage{image}ndf
+/spotascmyk false ndf
+/newcmykcustomcolor{6 packedarray}ndf
+/inkoverprint false ndf
+/setinkoverprint{pop}ndf 
+/setspotcolor { 
+spots exch get
+dup 4 get (_vc_Registration) eq
+{pop 1 exch sub setseparationgray}
+{0 5 getinterval exch setcustomcolor}
+ifelse
+}ndf
+/currentcolortransfer{currenttransfer dup dup dup}ndf
+/setcolortransfer{st pop pop pop}ndf
+/fas{}ndf
+/sas{}ndf
+/fhsetspreadsize{pop}ndf
+/filler{fill}bdf 
+/F{gsave {filler}fp grestore}bdf
+/f{closepath F}bdf
+/S{gsave {stroke}fp grestore}bdf
+/s{closepath S}bdf
+userdict /islevel2
+systemdict /languagelevel known dup
+{
+pop systemdict /languagelevel get 2 ge
+} if
+put
+islevel2 not
+{
+/currentcmykcolor
+{
+0 0 0 1 currentgray sub
+} ndf
+} if
+/tc
+{
+gsave
+setcmykcolor currentcmykcolor
+grestore
+} bind def
+/testCMYKColorThrough
+{
+tc add add add 0 ne
+} bind def
+/fhiscomposite where not {
+userdict /fhiscomposite
+islevel2
+{
+gsave 1 1 1 1 setcmykcolor currentcmykcolor grestore
+add add add 4 eq
+}
+{
+1 0 0 0 testCMYKColorThrough
+0 1 0 0 testCMYKColorThrough
+0 0 1 0 testCMYKColorThrough
+0 0 0 1 testCMYKColorThrough
+and and and
+} ifelse
+put
+}
+{ pop }
+ifelse
+/bc4 [0 0 0 0] def 
+/_lfp4 {
+1 pop 
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+taperfcn /frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/bcs [0 0] def 
+/_lfs4 {
+/yt xdf 
+/xt xdf 
+/ang xdf 
+storerect
+/taperfcn xdf
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+height abs adjnumsteps 
+dup 2 lt {pop 2} if 
+1 sub /numsteps1 xdf
+currentflat mark 
+currentflat clipflatness 
+/delta top bottom sub numsteps1 1 add div def 
+/right right left sub def 
+/botsv top delta sub def 
+{
+{
+W
+xt yt translate 
+ang rotate
+xt neg yt neg translate 
+dup setflat 
+/bottom botsv def
+0 1 numsteps1 
+{
+numsteps1 div taperfcn /frac xdf
+bcs 0
+1.0 tint2 tint1 sub frac mul tint1 add sub
+put bcs vc
+1 index setflat 
+{ 
+mark {newpath left bottom right delta rectfill}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+/bottom bottom delta sub def
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfs6 {
+/tint2 xdf 
+/tint1 xdf 
+bcs exch 1 exch put 
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+tint1 tint2 sub abs 
+bcs 1 get maxspot 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bcs 0
+tint2 tint1 sub frac mul tint1 add
+put bcs vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/_rfp6 {
+1 pop 
+/k2 xdf /y2 xdf /m2 xdf /c2 xdf
+/k1 xdf /y1 xdf /m1 xdf /c1 xdf
+/inrad xdf 
+/radius xdf 
+/yt xdf 
+/xt xdf 
+c1 c2 sub abs
+m1 m2 sub abs
+y1 y2 sub abs
+k1 k2 sub abs
+maxcolor 
+calcgraysteps mul abs round 
+radius inrad sub abs 
+adjnumsteps 
+dup 1 lt {pop 1} if 
+1 sub /numsteps1 xdf
+radius inrad sub numsteps1 dup 0 eq {pop} {div} ifelse 
+2 div /halfstep xdf 
+currentflat mark 
+currentflat clipflatness 
+{
+{
+dup setflat 
+W 
+0 1 numsteps1 
+{
+dup /radindex xdf
+numsteps1 dup 0 eq {pop pop 0.5} {div} ifelse 
+/frac xdf
+bc4 0 c2 c1 sub frac mul c1 add put
+bc4 1 m2 m1 sub frac mul m1 add put
+bc4 2 y2 y1 sub frac mul y1 add put
+bc4 3 k2 k1 sub frac mul k1 add put
+bc4 vc
+1 index setflat 
+{ 
+newpath mark 
+xt yt radius inrad sub 1 frac sub mul halfstep add inrad add 0 360
+{ arc
+radindex numsteps1 ne 
+inrad 0 gt or 
+{
+xt yt 
+numsteps1 0 eq
+{ inrad } 
+{ 
+radindex 1 add numsteps1 div 1 exch sub
+radius inrad sub mul halfstep add inrad add
+}ifelse
+dup xt add yt moveto
+360 0 arcn 
+} if
+fill
+}stopped
+{cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if}
+{cleartomark exit}ifelse
+}loop
+}for
+}
+gsave stopped grestore
+{exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if}
+{exit}ifelse
+}loop
+cleartomark setflat
+}bdf
+/lfp4{_lfp4}ndf
+/lfs4{_lfs4}ndf
+/rfs6{_rfs6}ndf
+/rfp6{_rfp6}ndf
+/cvc [0 0 0 1] def 
+/vc{
+AltsysDict /cvc 2 index put 
+aload length dup 4 eq
+{pop dup -1 eq{pop setrgbcolor}{setcmykcolor}ifelse}
+{6 eq {sethexcolor} {setspotcolor} ifelse }
+ifelse
+}bdf 
+0 setseparationgray
+/imgr {1692.47 1570.59 1723.65 1601.77 } def 
+/bleed 0 def 
+/clpr {1692.47 1570.59 1723.65 1601.77 } def 
+/xs 1 def 
+/ys 1 def 
+/botx 0 def 
+/overlap 0 def 
+/wdist 18 def 
+0 2 mul fhsetspreadsize 
+0 0 ne {/df 0 def /clipflatness 0 def} if 
+/maxsteps 256 def 
+/forcemaxsteps false def 
+/minsteps 0 def 
+
+userdict begin /AGDOrigMtx matrix currentmatrix def end 
+vms
+-1694 -1572 translate
+
+/currentpacking defed{false setpacking}if 
+/spots[
+
+1 0 0 0 (Process Cyan) false newcmykcustomcolor
+
+0 1 0 0 (Process Magenta) false newcmykcustomcolor
+
+0 0 1 0 (Process Yellow) false newcmykcustomcolor
+
+0 0 0 1 (Process Black) false newcmykcustomcolor
+]def
+n
+[] 0 d
+3.863708 M
+1 w
+0 j
+0 J
+false setoverprint
+0 i
+false eomode
+[0 0 0 1]vc
+vms
+q
+[1 0 0 1 -249.981674 -586.867554] concat
+vms
+1946.9506 2177.5114 m
+1954.4907 2185.0516 L
+1956.7047 2187.2656 1960.2943 2187.2656 1962.5083 2185.0516 C
+1970.0485 2177.5114 L
+1972.2625 2175.2974 1972.2625 2171.7078 1970.0485 2169.4938 C
+1962.5083 2161.9537 L
+1960.2943 2159.7396 1956.7047 2159.7396 1954.4907 2161.9537 C
+1946.9506 2169.4938 L
+1944.7365 2171.7078 1944.7365 2175.2974 1946.9506 2177.5114 C
+s 
+n
+true eomode
+1958.5469 2181.0039 m
+1959.2148 2181.0039 1959.7012 2180.9296 1960.0059 2180.7813 C
+1960.3142 2180.6326 1960.4684 2180.363 1960.4688 2179.9727 C
+1960.4688 2179.7383 1960.3398 2178.8026 1960.082 2177.166 C
+1959.0742 2170.4219 L
+1958.9373 2170.3241 1958.7615 2170.2754 1958.5469 2170.2754 C
+1958.3319 2170.2754 1958.1561 2170.3241 1958.0195 2170.4219 C
+1957.0117 2177.166 L
+1956.7539 2178.8026 1956.625 2179.7379 1956.625 2179.9727 C
+1956.625 2180.363 1956.7792 2180.6326 1957.0879 2180.7813 C
+1957.4003 2180.9296 1957.8866 2181.0035 1958.5469 2181.0039 C
+h
+1958.5469 2165.166 m
+1958.0389 2165.166 1957.5878 2165.3499 1957.1934 2165.7168 C
+1956.7986 2166.0837 1956.6016 2166.5485 1956.6016 2167.1113 C
+1956.6016 2167.6698 1956.7891 2168.1404 1957.1641 2168.5234 C
+1957.5427 2168.9102 1958.0038 2169.1035 1958.5469 2169.1035 C
+1959.1094 2169.1035 1959.5741 2168.9043 1959.9414 2168.5059 C
+1960.3083 2168.1074 1960.4918 2167.6423 1960.4922 2167.1113 C
+1960.4922 2166.748 1960.4102 2166.4177 1960.2461 2166.1211 C
+1960.082 2165.8241 1959.8513 2165.5916 1959.5547 2165.4238 C
+1959.2577 2165.2521 1958.9219 2165.1664 1958.5469 2165.166 C
+true setoverprint
+f 
+false setoverprint
+n
+vmr
+Q
+false eomode
+vmr
+vmr
+end
+%%Trailer
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/figures/warning.pdf b/docs-xml/xslt/db2latex-xsl/xsl/figures/warning.pdf
new file mode 100644
index 00000000000..a0afabfa232
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/figures/warning.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/footnote.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/footnote.mod.xsl
new file mode 100644
index 00000000000..ed3d927ec8b
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/footnote.mod.xsl
@@ -0,0 +1,174 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: footnote.mod.xsl,v 1.10 2004/01/02 06:45:25 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="footnote" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: footnote.mod.xsl,v 1.10 2004/01/02 06:45:25 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.10">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Footnotes <filename>footnote.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>footnote</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Format a footnote.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Applies templates within a &LaTeX; <function
+				condition="latex">footnote</function> command. Note that this
+				may not work within some tables. Also, <doc:db
+				basename="indexterm">indexterms</doc:db> may fail.
+			</para>
+			&essential_preamble;
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_links;
+				&test_tables;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="footnote">
+		<xsl:call-template name="label.id"/>
+		<xsl:text>\begingroup\catcode`\#=12\footnote{</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>}\endgroup\docbooktolatexmakefootnoteref{</xsl:text>
+		<xsl:call-template name="generate.label.id"/>
+		<xsl:text>}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Essential preamble for <filename>footnote.mod.xsl</filename> support </refpurpose>
+		<doc:description>
+			<para>
+
+				Defines <function
+				condition="latex">docbooktolatexusefootnoteref</function> and
+				<function
+				condition="latex">docbooktolatexmakefootnoteref</function>.
+				These functions help to integrate
+				<doc:db>footnote</doc:db>/@<sgmltag
+				class="attribute">id</sgmltag> cross-references with &LaTeX;.
+
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&preamble;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="latex.preamble.essential.footnote">
+		<xsl:text>
+			<![CDATA[
+% --------------------------------------------
+% A way to honour <footnoteref>s
+% Blame j-devenish (at) users.sourceforge.net
+% In any other LaTeX context, this would probably go into a style file.
+\newcommand{\docbooktolatexusefootnoteref}[1]{\@ifundefined{@fn@label@#1}%
+  {\hbox{\@textsuperscript{\normalfont ?}}%
+    \@latex@warning{Footnote label `#1' was not defined}}%
+  {\@nameuse{@fn@label@#1}}}
+\newcommand{\docbooktolatexmakefootnoteref}[1]{%
+  \protected@write\@auxout{}%
+    {\global\string\@namedef{@fn@label@#1}{\@makefnmark}}%
+  \@namedef{@fn@label@#1}{\hbox{\@textsuperscript{\normalfont ?}}}%
+  }
+]]>
+		</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>ulink</doc:db> elements within <doc:db>footnote</doc:db>s</refpurpose>
+		<doc:description>
+			<para>
+			Format a <doc:db>ulink</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Footnotes are <quote>tricky</quote> and require special handling for
+				a number of link-type commands.
+			</para>
+			<para>This template exists in this file so that all
+			the footnote-generating templates are close to each other. However,
+			it is actually a part of the <literal>ulink</literal> template in <filename>xref.mod.xsl</filename></para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="generate.ulink.in.footnote">
+		<xsl:param name="hyphenation"/>
+		<xsl:param name="url"/>
+		<xsl:call-template name="label.id"/>
+		<xsl:text>\begingroup\catcode`\#=12\footnote{</xsl:text>
+		<xsl:call-template name="generate.typeset.url">
+			<xsl:with-param name="hyphenation" select="$hyphenation"/>
+			<xsl:with-param name="url" select="$url"/>
+		</xsl:call-template>
+		<xsl:text>}\endgroup\docbooktolatexmakefootnoteref{</xsl:text>
+		<xsl:call-template name="generate.label.id"/>
+		<xsl:text>}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>footnote</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Make a link to a <doc:db>footnote</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			&essential_preamble;
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="footnoteref">
+		<xsl:variable name="footnote" select="key('id',@linkend)"/>
+		<xsl:text>\docbooktolatexusefootnoteref{</xsl:text>
+		<xsl:value-of select="@linkend"/>
+		<xsl:text>}</xsl:text>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/formal.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/formal.mod.xsl
new file mode 100644
index 00000000000..f49bd9a85ad
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/formal.mod.xsl
@@ -0,0 +1,344 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: formal.mod.xsl,v 1.13 2004/01/03 09:48:34 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="formal" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: formal.mod.xsl,v 1.13 2004/01/03 09:48:34 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.10">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Formal Objects <filename>formal.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>formal.mod.xsl</filename> contains generic
+			XSL templates for <quote>formal</quote> (title-bearing, block-style)
+			components and <quote>informal</quote> (no-title, block-style)
+			components.
+			It also contains templates for <doc:db>equation</doc:db>
+			and <doc:db>informalequation</doc:db> (which should probably
+			be moved to <filename>block.mod.xsl</filename>).</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose> Typeset a formal object generically </refpurpose>
+		<doc:description>
+			<para>
+				This template formats the current node as a formal object
+				by calling <xref linkend="template.formal.object.title"/>
+				then <xref linkend="template.content-templates"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.formal.object.title"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.content-templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="formal.object">
+		<xsl:call-template name="formal.object.title"/>
+		<xsl:call-template name="content-templates"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Typeset the title of a formal object generically </refpurpose>
+		<doc:description>
+			<para>
+
+				Outputs an anchor for cross-references and hyper-links, then
+				applies templates in the <literal>title.content</literal> mode
+				(supported by <filename>common/common.xsl</filename>)
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template name="formal.object.title">
+		<xsl:param name="title">
+			<xsl:apply-templates select="." mode="title.content"/>
+		</xsl:param>
+		<xsl:call-template name="label.id"/>
+		<xsl:copy-of select="$title"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Typeset an informal object generically </refpurpose>
+		<doc:description>
+			<para>
+
+				Outputs an anchor for cross-references and hyper-links, then
+				applies all templates.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template name="informal.object">
+		<xsl:call-template name="label.id"/>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Typeset formal or informal object generically </refpurpose>
+		<doc:description>
+			<para>
+
+				Chooses whether the current node is a <quote>formal</quote>-
+				or <quote>informal</quote>-like object and calls either
+				<xref linkend="template.formal.object"/> or
+				<xref linkend="template.informal.object"/>.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template name="semiformal.object">
+		<xsl:choose>
+			<xsl:when test="title"><xsl:call-template name="formal.object"/></xsl:when>
+			<xsl:otherwise><xsl:call-template name="informal.object"/></xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Determine the relative position for a <doc:db>caption</doc:db> </refpurpose>
+		<doc:description>
+			<para>
+				Chooses the position of a caption to be <quote>before</quote>
+				or <quote>after</quote> the selected object.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.formal.title.placement"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>object</term>
+					<listitem>
+						<para>
+
+						The type of object (i.e. name of the element) to which the caption pertains.
+
+						</para>
+					</listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+
+				If <quote>after</quote> has not been specified for the given
+				object in <xref linkend="param.formal.title.placement"/>,
+				<quote>before</quote> will be used by default.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="generate.formal.title.placement">
+		<xsl:param name="object" select="figure" />
+		<xsl:variable name="param.placement" select="substring-after(normalize-space($formal.title.placement),concat($object, ' '))"/>
+		<xsl:choose>
+			<xsl:when test="contains($param.placement, ' ')">
+				<xsl:value-of select="substring-before($param.placement, ' ')"/>
+			</xsl:when>
+			<xsl:when test="$param.placement = ''">before</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="$param.placement"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<!-- ========================================  -->
+	<!-- XSL Template for DocBook Equation Element -->
+	<!-- 2003/07/04 Applied patches from J.Pavlovic -->
+	<!-- ========================================  -->
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>equation</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats an titled, block-style equation.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.equation.caption.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.alt.is.preferred"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				If an <doc:db>informalequation</doc:db> is present, it will be
+				typeset in preference to any other elements. Otherwise, this
+				template will follow the same logic as the <xref
+				linkend="template.informalequation"/> template.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.generate.formal.title.placement"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="equation">
+		<!-- Equation title placement -->
+		<xsl:variable name="placement">
+			<xsl:call-template name="generate.formal.title.placement">
+				<xsl:with-param name="object" select="local-name(.)" />
+			</xsl:call-template>
+		</xsl:variable>
+		<!-- Equation caption -->
+		<xsl:variable name="caption">
+			<xsl:text>{</xsl:text>
+			<xsl:value-of select="$latex.equation.caption.style"/>
+			<xsl:text>{\caption{</xsl:text>
+			<xsl:apply-templates select="title" mode="caption.mode"/>
+			<xsl:text>}</xsl:text>
+			<xsl:call-template name="label.id"/>
+			<xsl:text>}}&#10;</xsl:text>
+		</xsl:variable>
+		<xsl:call-template name="map.begin"/>
+		<xsl:if test="$placement='before'">
+			<xsl:text>\captionswapskip{}</xsl:text>
+			<xsl:value-of select="$caption" />
+			<xsl:text>\captionswapskip{}</xsl:text>
+		</xsl:if>
+		<xsl:choose>
+			<xsl:when test="informalequation">
+				<xsl:apply-templates select="informalequation"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:variable name="tex" select="alt[@role='tex' or @role='latex']|mediaobject/textobject[@role='tex' or @role='latex']|mediaobject/textobject/phrase[@role='tex' or @role='latex']"/>
+				<xsl:choose>
+					<xsl:when test="$tex">
+						<xsl:apply-templates select="$tex"/>
+					</xsl:when>
+					<xsl:when test="alt and $latex.alt.is.preferred='1'">
+						<xsl:apply-templates select="alt"/>
+					</xsl:when>
+					<xsl:when test="mediaobject">
+						<xsl:apply-templates select="mediaobject"/>
+					</xsl:when>
+					<xsl:when test="alt">
+						<xsl:apply-templates select="alt"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:apply-templates select="graphic"/>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:if test="$placement!='before'"><xsl:value-of select="$caption" /></xsl:if>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>informalequation</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats an untitled, block-style equation.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.alt.is.preferred"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				The <quote>equation</quote> will be found by searching the
+				<sgmltag>informalequation</sgmltag> for its <quote>most
+				appropriate</quote> child elements. Firstly, this template will
+				search for all <doc:db>alt</doc:db>, <doc:db
+				basename="textobject">mediaobject/textobject</doc:db> or
+				<doc:db
+				basename="phrase">mediaobject/textobject/phrase</doc:db>
+				children that have a &roleattr; of <quote>latex</quote> or
+				<quote>tex</quote>. If none were found, the template will
+				search for generic <doc:db>mediaobject</doc:db> or
+				<doc:db>alt</doc:db> children. If <xref
+				linkend="param.latex.alt.is.preferred"/> is set, <sgmltag
+				basename="alt">alts</sgmltag> will be preferred over <sgmltag
+				basename="mediaobject">mediaobjects</sgmltag>. If none of these
+				elements was found, the template will format any
+				<doc:db>graphic</doc:db> children.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				<!--
+				&test_pavlov;
+				-->
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="informalequation">
+		<xsl:variable name="tex" select="alt[@role='tex' or @role='latex']|mediaobject/textobject[@role='tex' or @role='latex']|mediaobject/textobject/phrase[@role='tex' or @role='latex']"/>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:choose>
+			<xsl:when test="$tex">
+				<xsl:apply-templates select="$tex"/>
+			</xsl:when>
+			<xsl:when test="alt and $latex.alt.is.preferred='1'">
+				<xsl:apply-templates select="alt"/>
+			</xsl:when>
+			<xsl:when test="mediaobject">
+				<xsl:apply-templates select="mediaobject"/>
+			</xsl:when>
+			<xsl:when test="alt">
+				<xsl:apply-templates select="alt"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:apply-templates select="graphic"/>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>&#10;&#10;</xsl:text>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/glossary.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/glossary.mod.xsl
new file mode 100644
index 00000000000..926dd6bdbb3
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/glossary.mod.xsl
@@ -0,0 +1,392 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: glossary.mod.xsl,v 1.16 2004/01/26 08:58:10 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="glossary" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: glossary.mod.xsl,v 1.16 2004/01/26 08:58:10 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.12">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Glossaries <filename>glossary.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			Although &LaTeX; provides some glossary support, the better glossary
+			management support motivates the bypass of the &LaTeX;
+			<function condition="latex">makeglossary</function> command.
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>glossary</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			The <doc:db>glossary</doc:db> element is the entry point to a
+			&DocBook; glossary. The &DB2LaTeX; processing of the element is
+			quite straight- forward. First thing is to check whether the
+			document is a <doc:db>book</doc:db> or <doc:db>article</doc:db>. In
+			both cases, two new &LaTeX; commands are defined: <function
+			condition="latex">dbglossary</function> and <function
+			condition="latex">dbglossdiv</function>. In the former case, they
+			are mapped to <function condition="latex">chapter*</function> and
+			<function condition="latex">section*</function>. In the second case
+			to <function condition="latex">section*</function> and <function
+			condition="latex">subsection*</function>. The <function
+			condition="env">description</function> environment is used for
+			<doc:db basename="glossentry">glossentries</doc:db>.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<itemizedlist>
+				<listitem><para>Call template map.begin.</para></listitem>
+				<listitem><para>Apply Templates for Preamble, GlossDivs and GlossEntries (serial).</para></listitem>
+				<listitem><para>Call template map.end.</para></listitem>
+			</itemizedlist>
+			&essential_preamble;
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_gloss;
+				&test_ieeebiblio;
+				&test_mapping;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="glossary">
+		<xsl:variable name="divs" select="glossdiv"/>
+		<xsl:variable name="entries" select="glossentry"/>
+		<xsl:variable name="preamble" select="node()[not(self::glossaryinfo or self::title or self::subtitle or self::titleabbrev or self::glossdiv or self::glossentry or self::bibliography)]"/>
+		<xsl:call-template name="map.begin"/>
+		<!--
+		<xsl:if test="./subtitle"><xsl:apply-templates select="./subtitle" mode="component.title.mode"/> </xsl:if>
+		-->
+		<xsl:if test="$preamble"> <xsl:apply-templates select="$preamble"/> </xsl:if>
+		<xsl:if test="$divs"> <xsl:apply-templates select="$divs"/> </xsl:if>
+		<xsl:if test="$entries">
+			<xsl:text>\noindent%&#10;</xsl:text>
+			<xsl:text>\begin{description}&#10;</xsl:text>
+			<xsl:apply-templates select="$entries"/>
+			<xsl:text>\end{description}&#10;</xsl:text>
+		</xsl:if>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>glossdiv</doc:db> and <doc:db>glosslist</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes the mapping templates and applies content templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.content-templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="glossdiv|glosslist">
+		<xsl:call-template name="map.begin"/>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<!--
+    <doc:template match="glossentry" xmlns="">
+	<refpurpose> Glossary Entry XSL template / entry point  </refpurpose>
+	<doc:description>
+	    <para>T.B.D.</para>
+	</doc:description>
+	<itemizedlist>
+	    <listitem><para>Apply Templates.</para></listitem>
+	</itemizedlist>
+	<formalpara><title>Remarks and Bugs</title>
+	    <itemizedlist>
+		<listitem><para>Explicit Templates for <literal>glossentry/glossterm</literal></para></listitem>
+		<listitem><para>Explicit Templates for <literal>glossentry/acronym</literal></para></listitem>
+		<listitem><para>Explicit Templates for <literal>glossentry/abbrev</literal></para></listitem>
+		<listitem><para>Explicit Templates for <literal>glossentry/glossdef</literal></para></listitem>
+		<listitem><para>Explicit Templates for <literal>glossentry/glosssee</literal></para></listitem>
+		<listitem><para>Explicit Templates for <literal>glossentry/glossseealso</literal></para></listitem>
+		<listitem><para>Template for glossentry/revhistory is EMPTY.</para></listitem>
+	    </itemizedlist>
+	</formalpara>
+    </doc:template>
+	-->
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>glossentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Simply applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="glossentry">
+		<xsl:apply-templates/>
+		<xsl:text>&#10;&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process a <doc:db>glossentry</doc:db>'s <doc:db>glossterm</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Creates a &LaTeX; <function condition="latex">item</function> and
+				a <function condition="latex">hypertarget</function>, then applies
+				templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="glossentry/glossterm">
+		<xsl:text>\item[</xsl:text>
+		<xsl:if test="../@id!=''">
+			<xsl:text>\hypertarget{</xsl:text>
+			<xsl:value-of select="../@id"/>
+			<xsl:text>}</xsl:text>
+		</xsl:if>
+		<xsl:text>{</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>}] </xsl:text>
+	</xsl:template>
+
+	<doc:template basename="acronym" xmlns="">
+		<refpurpose>Process a <doc:db>glossentry</doc:db>'s <doc:db>acronym</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Format an acronym as part of a glossentry.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				The <doc:db>acronym</doc:db> is formatted as monospaced text
+				and delimited by round brackets. It appears in the <quote>body</quote>
+				(e.g. <doc:db>glossdef</doc:db>) region of the glossary entry, not
+				as part of the <doc:db>glossterm</doc:db>.
+			</para>
+			<para>
+				The delimiters should probably be localised.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="glossentry/acronym">
+	<xsl:text> ( </xsl:text> <xsl:call-template name="inline.monoseq"/> <xsl:text> ) </xsl:text>
+	</xsl:template>
+
+	<doc:template basename="abbrev" xmlns="">
+		<refpurpose>Process a <doc:db>glossentry</doc:db>'s <doc:db>abbrev</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Format an abbrev as part of a glossentry.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				The <doc:db>abbrev</doc:db> is delimited by square brackets. It
+				appears in the <quote>body</quote> (e.g.
+				<doc:db>glossdef</doc:db>) region of the glossary entry, not as
+				part of the <doc:db>glossterm</doc:db>.
+			</para>
+			<para>
+				The delimiters should probably be localised.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="glossentry/abbrev">
+	<xsl:text> [ </xsl:text> <xsl:apply-templates/> <xsl:text> ] </xsl:text> 
+	</xsl:template>
+
+	<doc:template basename="revhistory" xmlns="">
+		<refpurpose>Process a <doc:db>glossentry</doc:db>'s <doc:db>revhistory</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Currently, <doc:db basename="revhistory">revhistories</doc:db>
+				are suppressed within <doc:db basename="glossentry">glossentries</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="glossentry/revhistory"/>
+
+	<doc:template basename="glossdef" xmlns="">
+		<refpurpose>Process a <doc:db>glossentry</doc:db>'s <doc:db>glossdef</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="glossentry/glossdef">
+		<xsl:text>&#10;</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>glossseealso</doc:db> and <doc:db>glosssee</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Format a glossary cross-reference.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+			
+			Will call the following gentet templates:
+			<literal>gentext.element.name</literal>,
+			<literal>gentext.space</literal>,
+			<literal>gentext.startquote</literal>,
+			<literal>gentext.endquote</literal>.
+			It will then output a full stop (<quote>period</quote>).
+			
+			</para>
+			<para>
+			
+			If the <quote>otherterm</quote> was successfully found, and this
+			element is empty, then the appropriate cross-reference will be
+			generated. This this element is not empty but the otherterm was
+			also found, the behaviour will depend on <xref
+			linkend="param.latex.otherterm.is.preferred"/>.
+			
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_gloss;
+				&test_ieeebiblio;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.otherterm.is.preferred"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="glossseealso|glosssee">
+		<xsl:variable name="otherterm" select="@otherterm"/>
+		<xsl:variable name="targets" select="key('id',$otherterm)"/>
+		<xsl:variable name="target" select="$targets[1]"/>
+		<xsl:call-template name="gentext.element.name"/>
+		<xsl:call-template name="gentext.space"/>
+		<xsl:call-template name="gentext.startquote"/>
+		<xsl:choose>
+			<xsl:when test="$otherterm">
+				<xsl:text>\hyperlink{</xsl:text><xsl:value-of select="$otherterm"/>
+				<xsl:text>}{</xsl:text>
+				<xsl:choose>
+					<xsl:when test="$latex.otherterm.is.preferred=1">
+						<xsl:apply-templates select="$target" mode="xref"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:apply-templates/>
+					</xsl:otherwise>
+				</xsl:choose>
+				<xsl:text>}</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:apply-templates/>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:call-template name="gentext.endquote"/>
+		<xsl:text>. </xsl:text>
+	</xsl:template>
+
+	<xsl:template match="glossentry" mode="xref">
+		<xsl:apply-templates select="./glossterm" mode="xref"/>
+	</xsl:template>
+
+	<xsl:template match="glossterm" mode="xref">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Essential preamble for <filename>glossary.mod.xsl</filename> support </refpurpose>
+		<doc:description>
+			<para>
+
+				Defines the <function condition="env">dbglossary</function>
+				command.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&preamble;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="latex.preamble.essential.glossary">
+		<xsl:if test="//glossary">
+			<xsl:choose>
+				<xsl:when test="/book or /part">
+					<xsl:text>\newcommand{\dbglossary}[1]{\chapter*{#1}%&#10;</xsl:text>
+					<xsl:text>\markboth{\MakeUppercase{#1}}{\MakeUppercase{#1}}}%&#10;</xsl:text>
+					<xsl:text>\newcommand{\dbglossdiv}[1]{\section*{#1}}%&#10;</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>\newcommand{\dbglossary}[1]{\section*{#1}}%&#10;</xsl:text>
+					<xsl:text>\newcommand{\dbglossdiv}[1]{\subsection*{#1}}%&#10;</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:if>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/graphic.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/graphic.mod.xsl
new file mode 100644
index 00000000000..1893b85cb20
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/graphic.mod.xsl
@@ -0,0 +1,117 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: graphic.mod.xsl,v 1.5 2004/01/02 07:25:45 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="graphic" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: graphic.mod.xsl,v 1.5 2004/01/02 07:25:45 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.12">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Graphics <filename>graphic.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>screenshot</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="screenshot">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>screeninfo</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Suppressed.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="screeninfo"/>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>graphic</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a graphic as a paragraph.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.inlinegraphic"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="graphic">
+		<xsl:text>&#10;&#10;</xsl:text>
+		<xsl:call-template name="inlinegraphic"/>
+		<xsl:text>&#10;&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>inlinegraphic</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Calls &LaTeX; <function
+				condition="latex">includegraphics</function>
+				with the value of <sgmltag class="attribute">fileref</sgmltag>
+				or the URI of <sgmltag class="attribute">entityref</sgmltag>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="inlinegraphic" name="inlinegraphic">
+		<xsl:text>\includegraphics{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="@entityref">
+				<xsl:value-of select="unparsed-entity-uri(@entityref)"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="@fileref"/>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}</xsl:text>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/index.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/index.mod.xsl
new file mode 100644
index 00000000000..b58e1d19102
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/index.mod.xsl
@@ -0,0 +1,470 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: index.mod.xsl,v 1.17 2004/01/27 05:59:51 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="index" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: index.mod.xsl,v 1.17 2004/01/27 05:59:51 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.11">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Indices <filename>index.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>index.mod.xsl</filename> contains the
+			XSL template for <doc:db>index</doc:db>.</para>
+			<!-- TODO: -->
+			<para>Describe indexterm-range key.</para>
+			<para>
+				
+				An <literal>indexterm-range</literal> XSLT key is defined for
+				all <quote>startofrange</quote> <doc:db>indexterm</doc:db>
+				elements, matching their <sgmltag
+				class="attribute">id</sgmltag> attribute.
+				
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<!-- Our key for ranges -->
+	<xsl:key name="indexterm-range" match="indexterm[@class='startofrange']" use="@id"/>
+
+	<doc:template basename="index" xmlns="">
+		<refpurpose>Process <doc:db>index</doc:db> and <doc:db>setindex</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Produce a chapter-level index in &LaTeX;.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+
+			<para>
+
+				You will need to run your typesetter at least twice, and
+				possibly three times, to have the index generated normally (you
+				will also need to run the <command>makeidx</command> command).
+
+			</para>
+
+			&essential_preamble;
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_index;
+				&test_draft;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="index|setindex">
+		<xsl:variable name="preamble" select="node()[not(self::indexinfo or self::setindexinfo or self::title or self::subtitle or self::titleabbrev or self::indexdiv or self::indexentry)]"/>
+      <xsl:text>\setlength\saveparskip\parskip&#10;</xsl:text>
+      <xsl:text>\setlength\saveparindent\parindent&#10;</xsl:text>
+		<xsl:text>\begin{dbtolatexindex}{</xsl:text>
+		<xsl:call-template name="generate.label.id"/>
+		<xsl:text>}&#10;</xsl:text>
+      <xsl:text>\setlength\tempparskip\parskip \setlength\tempparindent\parindent&#10;</xsl:text>
+      <xsl:text>\parskip\saveparskip \parindent\saveparindent&#10;</xsl:text>
+      <xsl:text>\noindent </xsl:text><!-- &#10; -->
+		<xsl:apply-templates select="$preamble"/>
+		<xsl:call-template name="map.begin"/>
+      <xsl:text>\parskip\tempparskip&#10;</xsl:text>
+      <xsl:text>\parindent\tempparindent&#10;</xsl:text>
+		<xsl:text>\makeatletter\@input@{\jobname.ind}\makeatother&#10;</xsl:text>
+		<xsl:call-template name="map.end"/>
+		<xsl:text>\end{dbtolatexindex}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Essential preamble for <filename>index.mod.xsl</filename> support </refpurpose>
+		<doc:description>
+			<para>
+
+				This preamble aids the following:
+				<itemizedlist>
+					<listitem>
+						<simpara>
+							Allow user to override the &LaTeX; default index name
+							with a &DocBook; localisation.
+						</simpara>
+						<simpara>
+							Integrate <doc:db>index</doc:db>/@<sgmltag
+							class="attribute">id</sgmltag> cross-references
+							with &LaTeX; and tables of contents (makes indices
+							behave a bit like chapters).
+						</simpara>
+						<simpara>
+							Allow <quote>preamble</quote> templates or
+							mappings to be applied for indices.
+						</simpara>
+					</listitem>
+				</itemizedlist>
+
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&preamble;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="latex.preamble.essential.index">
+		<xsl:text>
+			<![CDATA[
+% index labeling helper
+\newif\ifdocbooktolatexprintindex\docbooktolatexprintindextrue
+\let\dbtolatex@@theindex\theindex
+\let\dbtolatex@@endtheindex\endtheindex
+\def\theindex{\relax}
+\def\endtheindex{\relax}
+\newenvironment{dbtolatexindex}[1]
+   {
+\if@openright\cleardoublepage\else\clearpage\fi
+\let\dbtolatex@@indexname\indexname
+\def\dbtolatex@indexlabel{%
+ \ifnum \c@secnumdepth >\m@ne \refstepcounter{chapter}\fi%
+ \label{#1}\hypertarget{#1}{\dbtolatex@@indexname}%
+ \global\docbooktolatexprintindexfalse}
+\def\indexname{\ifdocbooktolatexprintindex\dbtolatex@indexlabel\else\dbtolatex@@indexname\fi}
+\dbtolatex@@theindex
+   }
+   {
+\dbtolatex@@endtheindex\let\indexname\dbtolatex@@indexname
+   }
+
+\newlength\saveparskip \newlength\saveparindent
+\newlength\tempparskip \newlength\tempparindent
+]]>
+		</xsl:text>
+	</xsl:template>
+
+<!--
+	<xsl:template match="index/title">
+		<xsl:call-template name="label.id"> <xsl:with-param name="object" select=".."/> </xsl:call-template>
+	</xsl:template>
+
+<xsl:template match="indexdiv">
+	<xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="indexdiv/title">
+	<xsl:call-template name="label.id"> <xsl:with-param name="object" select=".."/> </xsl:call-template>
+</xsl:template>
+
+	<xsl:template match="primary|secondary|tertiary|see|seealso"/>
+
+-->
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>indexterm</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Identify an instance of an indexed term.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.generate.indexterm"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>style</term>
+					<listitem><simpara>
+						&LaTeX; code used to format the displayed entry.
+						By default, this is drawn from any <quote>latex-index-style</quote>
+						processing instructions (and is therefore empty most of the time).
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+				A &LaTeX; <function condition="latex">index</function> command
+				is issued. When an <doc:db>index</doc:db> element is included
+				in your document and indexing is enabled, this indexterm will
+				be indexed.
+			</para>
+			<para>
+				When <link linkend="param.latex.is.draft">draft mode</link> is
+				enabled, the physical location of <doc:db
+				basename="indexterm">indexterms</doc:db> will be highlighted
+				within the body of the text as well as appearing in the index
+				proper.
+			</para>
+			<para>
+				&DB2LaTeX; includes some logic to handle the
+				<quote>startofrange</quote> and <quote>endofrange</quote>
+				classes.
+			</para>
+			<para>
+				It is possible to format an entry (e.g.
+				make it bold or italic) by inserting a processing instruction
+				named <quote>latex-index-style</quote> in the appropriate
+				subterm.
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_ddh;
+				&test_draft1;
+				&test_draft2;
+				&test_index;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.is.draft"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<!-- INDEX TERM CONTENT MODEL
+	IndexTerm ::=
+	(Primary,
+	((Secondary,
+	((Tertiary,
+	(See|SeeAlso+)?)|
+	See|SeeAlso+)?)|
+	See|SeeAlso+)?)
+	-->
+	<xsl:template match="indexterm">
+		<xsl:if test="$latex.generate.indexterm='1'">
+			<xsl:variable name="idxterm">
+				<xsl:apply-templates mode="indexterm"/>
+			</xsl:variable>
+
+			<xsl:if test="@class and @zone">
+				<xsl:message terminate="yes">Error: Only one attribute (@class or @zone) is in indexterm possible!</xsl:message>
+			</xsl:if>
+
+			<xsl:choose>
+				<xsl:when test="@class='startofrange'">
+					<xsl:text>\index{</xsl:text>
+					<xsl:value-of select="$idxterm"/>
+					<xsl:text>|(}</xsl:text>
+				</xsl:when>
+				<xsl:when test="@class='endofrange'">
+					<xsl:choose>
+						<xsl:when test="count(key('indexterm-range',@startref)) = 0">
+							<xsl:message terminate="yes"><xsl:text>Error: No indexterm with </xsl:text>
+							<xsl:text>id='</xsl:text><xsl:value-of select="@startref"/>
+							<xsl:text>' found!</xsl:text>
+							<xsl:text>  Check your attributs id/startref in your indexterms!</xsl:text>
+							</xsl:message>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:variable name="thekey" select="key('indexterm-range',@startref)"/>
+							<xsl:for-each select="$thekey[1]">
+								<xsl:text>\index{</xsl:text>
+								<xsl:apply-templates mode="indexterm"/>
+								<xsl:text>|)}</xsl:text>
+							</xsl:for-each>
+						</xsl:otherwise>
+					</xsl:choose>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>\index{</xsl:text>
+					<xsl:value-of select="$idxterm"/>
+					<xsl:text>}</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:if>
+	</xsl:template>
+
+	<xsl:template match="*" mode="indexterm">
+		<xsl:message>WARNING: Element '<xsl:value-of select="local-name()"/>' in indexterm not supported and skipped!</xsl:message>
+	</xsl:template>
+
+	<!--
+	<xsl:template match="acronym|foreignphrase" mode="indexterm">
+		<xsl:apply-templates mode="indexterm"/>
+	</xsl:template>
+	-->
+
+	<doc:template xmlns="">
+		<refpurpose>Process the contents of <doc:db basename="indexterm">indexterms</doc:db></refpurpose>
+		<doc:description>
+			<para>
+				Register a primary index term.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.index.subterm"/>.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="primary" mode="indexterm">
+		<xsl:call-template name="index.subterm"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process the contents of <doc:db basename="indexterm">indexterms</doc:db></refpurpose>
+		<doc:description>
+			<para>
+				Register a secondary or tertiary index term.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.index.subterm"/>.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="secondary|tertiary" mode="indexterm">
+		<xsl:text>!</xsl:text>
+		<xsl:call-template name="index.subterm"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process the contents of <doc:db basename="indexterm">indexterms</doc:db></refpurpose>
+		<doc:description>
+			<para>
+				Register a primary, secondary or tertiary index term.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				If no <sgmltag class="attribute">sortas</sgmltag> attribute is
+				present, the contents of <doc:db>primary</doc:db>,
+				<doc:db>secondary</doc:db> and <doc:db>tertiary</doc:db>
+				elements are converted to text-only and no templates are
+				applied. If the <sgmltag class="attribute">sortas</sgmltag>
+				attribute is present and non-empty, its value is used for indexing
+				and sorting (but not for display)<!-- and templates
+				<emphasis>are</emphasis> applied for display purposes-->.
+
+			</para>
+			<para>
+
+				If a <quote>latex-index-style</quote> processing instruction is
+				present, the displayed indexterm will be formatted by treating
+				the content of the PI as a &LaTeX; command.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="index.subterm">
+		<xsl:variable name="style" select="processing-instruction('latex-index-style')"/>
+		<xsl:choose>
+			<xsl:when test="@sortas!=''">
+				<xsl:variable name="string">
+					<xsl:call-template name="scape-indexterm">
+						<xsl:with-param name="string" select="@sortas"/>
+					</xsl:call-template>
+				</xsl:variable>
+				<xsl:variable name="content">
+					<xsl:call-template name="scape-indexterm">
+						<xsl:with-param name="string" select="."/>
+					</xsl:call-template>
+				</xsl:variable>
+				<xsl:value-of select="normalize-space($string)"/>
+				<xsl:text>@{</xsl:text>
+				<xsl:value-of select="$style"/>
+				<xsl:text>{</xsl:text>
+				<xsl:value-of select="normalize-space($content)"/>
+				<xsl:text>}}</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:variable name="string">
+					<xsl:call-template name="scape-indexterm">
+						<xsl:with-param name="string" select="."/>
+					</xsl:call-template>
+				</xsl:variable>
+				<xsl:value-of select="normalize-space($string)"/>
+				<xsl:if test="$style!=''">
+					<xsl:text>@{</xsl:text>
+					<xsl:value-of select="$style"/>
+					<xsl:text>{</xsl:text>
+					<xsl:value-of select="normalize-space($string)"/>
+					<xsl:text>}}</xsl:text>
+				</xsl:if>
+			</xsl:otherwise>
+		</xsl:choose>
+		<!--
+		<xsl:apply-templates mode="indexterm"/>
+		-->
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process the contents of <doc:db>see</doc:db> and <doc:db>seealso</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Annotate an index entry with a <quote>See</quote> or <quote>See also</quote> cross-reference.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Templates are applied.
+				<quote>See</quote> or <quote>see also</quote> text
+				is generated by <literal>gentext.element.name</literal>
+				and formatted in italics.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="see|seealso" mode="indexterm">
+		<xsl:text>|textit{</xsl:text>
+		<xsl:call-template name="gentext.element.name"/>
+		<xsl:text>} {</xsl:text>
+		<xsl:apply-templates/>
+		<!--
+		<xsl:apply-templates mode="indexterm"/>
+		-->
+		<xsl:text>} </xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Skip <doc:db>indexentry</doc:db>-related elements </refpurpose>
+		<doc:description>
+			<para>
+				Ignores the elements.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				&DB2LaTeX; only supports indices that are generated by &LaTeX; itself.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="indexentry|primaryie|secondaryie|tertiaryie|seeie|seealsoie"/>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/inline.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/inline.mod.xsl
new file mode 100644
index 00000000000..c7b2dcddbf8
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/inline.mod.xsl
@@ -0,0 +1,1602 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: inline.mod.xsl,v 1.21 2004/01/05 09:58:47 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="inline" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: inline.mod.xsl,v 1.21 2004/01/05 09:58:47 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.16">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Inline Elements <filename>inline.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process regular text</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="normalize-scape"/></simpara></listitem>
+				<listitem><simpara><xref linkend="scape"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="inline.charseq">
+		<xsl:param name="content">
+			<xsl:apply-templates/>
+		</xsl:param>
+		<xsl:copy-of select="$content"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process monospace text</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates within a &LaTeX;
+				<function condition="latex">texttt</function> command.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.hyphenation.tttricks"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="normalize-scape"/></simpara></listitem>
+				<listitem><simpara><xref linkend="scape"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="inline.monoseq">
+		<xsl:param name="hyphenation">\docbookhyphenatedot</xsl:param>
+		<xsl:param name="content">
+			<xsl:apply-templates/>
+		</xsl:param>
+		<xsl:text>{\texttt{</xsl:text>
+		<xsl:if test="$latex.hyphenation.tttricks='1'"><xsl:value-of select="$hyphenation" /></xsl:if>
+		<xsl:text>{</xsl:text>
+		<xsl:copy-of select="$content"/>
+		<xsl:text>}}}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process bold text</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates within a &LaTeX;
+				<function condition="latex">bfseries</function> command.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="normalize-scape"/></simpara></listitem>
+				<listitem><simpara><xref linkend="scape"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="inline.boldseq">
+		<xsl:param name="content">
+			<xsl:apply-templates/>
+		</xsl:param>
+		<xsl:text>{\bfseries{</xsl:text>
+		<xsl:copy-of select="$content"/>
+		<xsl:text>}}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process italic text</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates within a &LaTeX;
+				<function condition="latex">em</function> command.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="normalize-scape"/></simpara></listitem>
+				<listitem><simpara><xref linkend="scape"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="inline.italicseq">
+		<xsl:param name="content">
+			<xsl:apply-templates/>
+		</xsl:param>
+		<xsl:text>{\em{</xsl:text>
+		<xsl:copy-of select="$content"/>
+		<xsl:text>}}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process bold monospace text</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates within &LaTeX;
+				<function condition="latex">ttfamily</function>
+				and
+				<function condition="latex">bfseries</function>
+				commands.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.hyphenation.tttricks"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="normalize-scape"/></simpara></listitem>
+				<listitem><simpara><xref linkend="scape"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="inline.boldmonoseq">
+		<xsl:param name="hyphenation">\docbookhyphenatedot</xsl:param>
+		<xsl:param name="content">
+			<xsl:apply-templates/>
+		</xsl:param>
+		<xsl:text>{\ttfamily\bfseries{</xsl:text>
+		<xsl:if test="$latex.hyphenation.tttricks='1'"><xsl:value-of select="$hyphenation" /></xsl:if>
+		<xsl:text>{</xsl:text>
+		<xsl:copy-of select="$content"/>
+		<xsl:text>}}}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process italic monospace text</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates within &LaTeX;
+				<function condition="latex">ttfamily</function>
+				and
+				<function condition="latex">itshape</function>
+				commands.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.hyphenation.tttricks"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="normalize-scape"/></simpara></listitem>
+				<listitem><simpara><xref linkend="scape"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="inline.italicmonoseq">
+		<xsl:param name="hyphenation">\docbookhyphenatedot</xsl:param>
+		<xsl:param name="content">
+			<xsl:apply-templates/>
+		</xsl:param>
+		<xsl:text>{\ttfamily\itshape{</xsl:text>
+		<xsl:if test="$latex.hyphenation.tttricks='1'"><xsl:value-of select="$hyphenation" /></xsl:if>
+		<xsl:text>{</xsl:text>
+		<xsl:copy-of select="$content"/>
+		<xsl:text>}}}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process superscript text</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates within a &LaTeX;
+				<function condition="latex">text</function>
+				command within an inline mathematics environment.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="normalize-scape"/></simpara></listitem>
+				<listitem><simpara><xref linkend="scape"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="inline.superscriptseq">
+		<xsl:param name="content">
+			<xsl:apply-templates/>
+		</xsl:param>
+		<xsl:text>$^\text{</xsl:text>
+		<xsl:copy-of select="$content"/>
+		<xsl:text>}$</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process subscript text</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates within a &LaTeX;
+				<function condition="latex">text</function>
+				command within an inline mathematics environment.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="normalize-scape"/></simpara></listitem>
+				<listitem><simpara><xref linkend="scape"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="inline.subscriptseq">
+		<xsl:param name="content">
+			<xsl:apply-templates/>
+		</xsl:param>
+		<xsl:text>$_\text{</xsl:text>
+		<xsl:copy-of select="$content"/>
+		<xsl:text>}$</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>accel</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="accel">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>action</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="action">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process name-type elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="honorific|firstname|surname|lineage|othername">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>application</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="application">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>classname</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="classname">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template basename="copyright" xmlns="">
+		<refpurpose>Process <doc:db>copyright</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates with a copyright dingbat.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="copyright" name="copyright">
+		<xsl:call-template name="gentext.element.name"/>
+		<xsl:call-template name='gentext.space'/>
+		<xsl:call-template name="dingbat">
+			<xsl:with-param name="dingbat">copyright</xsl:with-param>
+		</xsl:call-template>
+		<xsl:call-template name='gentext.space'/>
+		<xsl:apply-templates select="year"/>
+		<xsl:call-template name='gentext.space'/>
+		<xsl:apply-templates select="holder"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process a <doc:db>copyright</doc:db>'s <doc:db>holder</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="copyright/holder">
+		<xsl:apply-templates />
+	</xsl:template>
+
+	<xsl:template match="copyright/year[position()&lt;last()-1]">
+		<xsl:apply-templates />
+		<xsl:text>, </xsl:text>
+	</xsl:template>
+
+	<!-- RCAS 2003/03/11 FIXME : "and" -->
+	<xsl:template match="copyright/year[position()=last()-1]">
+		<xsl:apply-templates />
+		<xsl:text>, </xsl:text>
+	</xsl:template>
+
+	<xsl:template match="copyright/year[position()=last()]">
+		<xsl:apply-templates />
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>exceptionname</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="exceptionname">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>interfacename</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="interfacename">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>methodname</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="methodname">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>command</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.boldseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="command">
+		<xsl:call-template name="inline.boldseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>computeroutput</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="computeroutput">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>constant</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="constant">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>database</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="database">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>errorcode</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="errorcode">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>errorname</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="errorname">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>errortype</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="errortype">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>envar</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="envar">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>filename</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="filename">
+		<xsl:call-template name="inline.monoseq">
+			<xsl:with-param name="hyphenation">\docbookhyphenatefilename</xsl:with-param>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>function</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				<doc:todo>Insert documentation here.</doc:todo>
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="function">
+		<xsl:choose>
+			<xsl:when test="$function.parens = 1 or parameter or function or replaceable">
+				<xsl:variable name="nodes" select="text()|*"/>
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+					<xsl:apply-templates select="$nodes[1]"/>
+					</xsl:with-param>
+				</xsl:call-template>
+				<xsl:text>(</xsl:text>
+				<xsl:apply-templates select="$nodes[position()>1]"/>
+				<xsl:text>)</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="inline.monoseq"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process a <doc:db>function</doc:db>'s <doc:db>parameter</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicmonoseq"/> and
+				separates subsequent <doc:db
+				basename="replaceable">replaceables</doc:db> with commas.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="function/parameter" priority="2">
+		<xsl:call-template name="inline.italicmonoseq"/>
+		<xsl:if test="following-sibling::*">
+			<xsl:text>, </xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process a <doc:db>function</doc:db>'s <doc:db>replaceable</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicmonoseq"/> and
+				separates subsequent <doc:db
+				basename="replaceable">replaceables</doc:db> with commas.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="function/replaceable" priority="2">
+		<xsl:call-template name="inline.italicmonoseq"/>
+		<xsl:if test="following-sibling::*">
+			<xsl:text>, </xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process GUI-type elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>
+				within a &LaTeX; <function condition="latex">sffamily</function>
+				and <function condition="latex">bfseries</function> commands.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="guibutton|guiicon|guilabel|guimenu|guimenuitem|guisubmenu|interface">
+		<xsl:text>{\sffamily \bfseries </xsl:text>
+		<xsl:call-template name="inline.charseq" />
+		<xsl:text>}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>hardware</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="hardware">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>interfacedefinition</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="interfacedefinition">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>keycap</doc:db> and <doc:db>keysym</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.boldseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="keycap|keysym">
+		<xsl:call-template name="inline.boldseq" />
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>keycode</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="keycode">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>literal</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="literal">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>medialabel</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="medialabel">
+		<xsl:call-template name="inline.italicseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>shortcut</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="shortcut">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>mousebutton</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="mousebutton">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>option</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="option">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>parameter</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicmonoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="parameter" priority="1">
+		<xsl:call-template name="inline.italicmonoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>property</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="property">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>prompt</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="prompt">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>replaceable</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicmonoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="replaceable" priority="1">
+		<xsl:call-template name="inline.italicmonoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>returnvalue</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="returnvalue">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>structfield</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicmonoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="structfield">
+		<xsl:call-template name="inline.italicmonoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>structname</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="structname">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>symbol</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="symbol">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>systemitem</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="systemitem">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>token</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="token">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>type</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="type">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>userinput</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.boldmonoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="userinput">
+		<xsl:call-template name="inline.boldmonoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>abbrev</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				<doc:todo>It would be useful if a terminating full stop
+				were not to induce sentence-end whitespace spacing.</doc:todo>
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="abbrev">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>acronym</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="acronym">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>citerefentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="citerefentry">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>citetitle</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="citetitle">
+		<xsl:call-template name="inline.italicseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>corpauthor</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="corpauthor">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>emphasis</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="emphasis">
+		<xsl:call-template name="inline.italicseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="" basename="emphasis">
+		<refpurpose>Process <doc:db>emphasis</doc:db> elements with <quote>bold</quote> role</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.boldseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="emphasis[@role='bold']">
+		<xsl:call-template name="inline.boldseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>foreignphrase</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="foreignphrase">
+		<xsl:call-template name="inline.italicseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>jobtitle</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="jobtitle">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>markup</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies template using the <literal>latex.verbatim</literal>
+				mode.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="markup">
+		<xsl:apply-templates mode="latex.verbatim"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>orgdiv</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="orgdiv">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>orgname</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="orgname">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>phrase</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Normally, <xref linkend="template.inline.charseq"/> is used.
+				However, the use of <quote>latex</quote> or <quote>tex</quote>
+				for the <sgmltag class="attribute">role</sgmltag> attribute
+				will convert the contents to plain text without &LaTeX;
+				active-character escaping.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="phrase">
+		<xsl:choose>
+			<xsl:when test="@role='tex' or @role='latex'">
+				<xsl:value-of select="."/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="inline.charseq"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>quote</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				The contents will be enclosed in quotation marks,
+				using <literal>gentext.startquote</literal>
+				and <literal>gentext.nestedstartquote</literal>
+				alternating according to the <doc:db>quote</doc:db>
+				nesting level.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="quote">
+		<xsl:choose>
+			<xsl:when test="count(ancestor::quote) mod 2=0">
+				<xsl:call-template name="gentext.startquote"/>
+				<xsl:call-template name="inline.charseq"/>
+				<xsl:call-template name="gentext.endquote"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="gentext.nestedstartquote"/>
+				<xsl:call-template name="inline.charseq"/>
+				<xsl:call-template name="gentext.nestedendquote"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>varname</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.monoseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="varname">
+		<xsl:call-template name="inline.monoseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>wordasword</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="wordasword">
+		<xsl:call-template name="inline.italicseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>lineannotation</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="lineannotation">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>superscript</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.superscriptseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="superscript">
+		<xsl:call-template name="inline.superscriptseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>subscript</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.subscriptseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="subscript">
+		<xsl:call-template name="inline.subscriptseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>trademark</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>,
+				then appends a <quote>trademark</quote> dingbat.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.dingbat"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="trademark">
+		<xsl:call-template name="inline.charseq"/>
+		<xsl:call-template name="dingbat">
+			<xsl:with-param name="dingbat">trademark</xsl:with-param>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>firstterm</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.italicseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+    <xsl:template match="firstterm">
+	<xsl:call-template name="inline.italicseq"/>
+    </xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>glossterm</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="glossterm">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>keycombo</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a key combination using conjugation characters.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Templates are applied for all children, with comjugation
+				characters based upon the <sgmltag
+				class="attribute">action</sgmltag> attribute.
+			</para>
+			<para>
+				For <quote>seq</quote> actions, a space character is used.
+				For <quote>simul</quote> actions, a plus sign (+) is used.
+				For <quote>other</quote> actions, no conjugation character is
+				used (children will be abutting).
+				For all other actions, an en-dash is used.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="keycombo">
+		<xsl:variable name="action" select="@action"/>
+		<xsl:variable name="joinchar">
+			<xsl:choose>
+			<xsl:when test="$action='seq'"><xsl:text> </xsl:text></xsl:when>
+			<xsl:when test="$action='simul'">+</xsl:when>
+			<xsl:when test="$action='press'">--</xsl:when>
+			<xsl:when test="$action='click'">--</xsl:when>
+			<xsl:when test="$action='double-click'">--</xsl:when>
+			<xsl:when test="$action='other'"></xsl:when>
+			<xsl:otherwise>--</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:for-each select="./*">
+			<xsl:if test="position()>1"><xsl:value-of select="$joinchar"/></xsl:if>
+			<xsl:apply-templates select="."/>
+		</xsl:for-each>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>menuchoice</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes templates for non-shortcut children, then formats any
+				<doc:db basename="shortcut">shortcuts</doc:db> in parentheses.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.process.menuchoice"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="menuchoice">
+		<xsl:variable name="shortcut" select="./shortcut"/>
+		<xsl:call-template name="process.menuchoice"/>
+		<xsl:if test="$shortcut">
+			<xsl:text> (</xsl:text>
+			<xsl:apply-templates select="$shortcut"/>
+			<xsl:text>)</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>menuchoice</doc:db> children (not shortcut) </refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Selects children of the current node (does not select <doc:db>shortcut</doc:db> elements).
+				Subsequent children are delimited by a plug sign, in general, or an arrow,
+				for <doc:db>guimenuitem</doc:db> and <doc:db>guisubmenu</doc:db>.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="process.menuchoice">
+		<xsl:param name="nodelist" select="guibutton|guiicon|guilabel|guimenu|guimenuitem|guisubmenu|interface"/><!-- not(shortcut) -->
+		<xsl:param name="count" select="1"/>
+		<xsl:choose>
+			<xsl:when test="$count>count($nodelist)"/>
+			<xsl:when test="$count=1">
+				<xsl:apply-templates select="$nodelist[$count=position()]"/>
+				<xsl:call-template name="process.menuchoice">
+					<xsl:with-param name="nodelist" select="$nodelist"/>
+					<xsl:with-param name="count" select="$count+1"/>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:variable name="node" select="$nodelist[$count=position()]"/>
+				<xsl:choose>
+					<xsl:when test="name($node)='guimenuitem' or name($node)='guisubmenu'">
+					<xsl:text> $\to$ </xsl:text>
+					</xsl:when>
+					<xsl:otherwise>+</xsl:otherwise>
+				</xsl:choose>
+				<xsl:apply-templates select="$node"/>
+				<xsl:call-template name="process.menuchoice">
+					<xsl:with-param name="nodelist" select="$nodelist"/>
+					<xsl:with-param name="count" select="$count+1"/>
+				</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>optional</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>,
+				surrounded by $arg.choice.opt.open.str and
+				$arg.choice.opt.close.str.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="optional">
+		<xsl:value-of select="$arg.choice.opt.open.str"/>
+		<xsl:call-template name="inline.charseq"/>
+		<xsl:value-of select="$arg.choice.opt.close.str"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>remark</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates as a margin note.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.show.comments"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>When <xref linkend="param.show.comments"/> is set,
+			templates will be applied within a &LaTeX;
+			<function condition="latex">marginpar</function> command,
+			using <function condition="latex">footnotesize</function>.</para>
+			<para>If <xref linkend="param.show.comments"/> is not set,
+			then content is suppressed.</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="comment|remark">
+		<xsl:if test="$show.comments=1">
+			<xsl:text>\marginpar{\footnotesize{</xsl:text>
+			<xsl:apply-templates/>
+			<xsl:text>}}</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>productname</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="productname">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>productnumber</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="productnumber">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process address-like elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes <xref linkend="template.inline.charseq"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="pob|street|city|state|postcode|country|phone|fax|otheraddr">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>beginpage</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Suppressed.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="beginpage"/>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/keywords.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/keywords.mod.xsl
new file mode 100644
index 00000000000..f059b0c5903
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/keywords.mod.xsl
@@ -0,0 +1,140 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: keywords.mod.xsl,v 1.7 2004/01/09 12:02:15 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="keywords" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: keywords.mod.xsl,v 1.7 2004/01/09 12:02:15 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.6">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Keywords <filename>keywords.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>keywords.mod.xsl</filename> contains the
+			XSL templates for <doc:db>keywordsset</doc:db>
+			and <doc:db>sectionset</doc:db>.</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>keywordset</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Uses a &LaTeX; mapping to express a block representation
+				of keywords.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+
+			<para><doc:db>keywordset</doc:db>s are only rendered in a limited
+			number of situations.</para>
+
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><para>&mapping;</para></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+
+	<xsl:template match="keywordset">
+		<xsl:call-template name="map.begin"/>
+		<xsl:call-template name="gentext.template">
+			<xsl:with-param name="context" select="'naturalblocklist'"/>
+			<xsl:with-param name="name" select="'start'"/>
+		</xsl:call-template>
+		<xsl:apply-templates/>
+		<xsl:call-template name="gentext.template">
+			<xsl:with-param name="context" select="'naturalblocklist'"/>
+			<xsl:with-param name="name" select="'end'"/>
+		</xsl:call-template>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db basename="keyword">keywords</doc:db></refpurpose>
+		<doc:description>
+			<para>
+				Emits keywords as regular text plus a separator.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara>Localisation for the <literal>keyword.separator</literal> in the <literal>keywordset</literal> context.</simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+
+	<xsl:template match="keyword">
+		<xsl:if test="position() &gt; 1">
+			<xsl:choose>
+				<xsl:when test="position()=last() and position() &gt; 2">
+					<xsl:call-template name="gentext.template">
+						<xsl:with-param name="context" select="'naturalblocklist'"/>
+						<xsl:with-param name="name" select="'lastofmany'"/>
+					</xsl:call-template>
+				</xsl:when>
+				<xsl:when test="position()=last()">
+					<xsl:call-template name="gentext.template">
+						<xsl:with-param name="context" select="'naturalblocklist'"/>
+						<xsl:with-param name="name" select="'lastoftwo'"/>
+					</xsl:call-template>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:call-template name="gentext.template">
+						<xsl:with-param name="context" select="'naturalblocklist'"/>
+						<xsl:with-param name="name" select="'middle'"/>
+					</xsl:call-template>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:if>
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<doc:template match="subjectset|subject" xmlns="">
+		<refpurpose>Process <doc:db>subjectset</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Suppresses <doc:db basename="subjectset">subjectsets</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+
+	<xsl:template match="subjectset"/>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/labelid.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/labelid.mod.xsl
new file mode 100644
index 00000000000..e6f90c63eb9
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/labelid.mod.xsl
@@ -0,0 +1,503 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: labelid.mod.xsl,v 1.5 2004/01/01 12:26:41 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="labelid" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: labelid.mod.xsl,v 1.5 2004/01/01 12:26:41 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.5">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Labels and Anchors for Cross-referencing <filename>labelid.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose> Generate &LaTeX; <function condition="latex">label</function>s </refpurpose>
+		<doc:description>
+			<para>
+		
+			This template marks the current object with a <function
+			condition="latex">label</function>.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<!--
+		<doc:params>
+			<variablelist>
+			<varlistentry><term>object</term>
+				<listitem><para>The node whose id is to be used.</para></listitem>
+			</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+		</doc:notes>
+		-->
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.generate.label.id"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="label.id">
+		<xsl:text>\label{</xsl:text>
+		<xsl:call-template name="generate.label.id"/>
+		<xsl:text>}</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Generate a reliable cross-reference id </refpurpose>
+		<doc:description>
+			<para>
+			
+			The passed argument indicates the object whose <sgmltag
+			class="attribute">id</sgmltag> attribute is used to generate the
+			label. In this sense, in most cases its the current node itself. If
+			the used object has not an id attribute, a unique id is obtained by
+			means of the <literal>generate-id</literal> function. Moreover, if
+			we are using the hyperref package, a hypertarget is also defined
+			for this object.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+			<varlistentry><term>object</term>
+				<listitem><para>The node whose id is to be used.</para></listitem>
+			</varlistentry>
+			</variablelist>
+		</doc:params>
+	</doc:template>
+	<xsl:template name="generate.label.id">
+		<xsl:param name="object" select="."/>
+		<xsl:variable name="id">
+			<xsl:choose>
+			<xsl:when test="$object/@id">
+				<xsl:value-of select="$object/@id"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="generate-id($object)"/>
+			</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:value-of select="normalize-space($id)"/>
+	</xsl:template>
+
+    <!--
+    <xsl:template match="*" mode="label.content">
+	<xsl:message>
+	    <xsl:text>Request for label of unexpected element: </xsl:text>
+	    <xsl:value-of select="name(.)"/>
+	</xsl:message>
+    </xsl:template>
+
+    <xsl:template match="set|book" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:if test="@label">
+	    <xsl:value-of select="@label"/>
+	    <xsl:value-of select="$punct"/>
+	</xsl:if>
+    </xsl:template>
+
+    <xsl:template match="part" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$part.autolabel != 0">
+		<xsl:number from="book" count="part" format="I"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+
+    <xsl:template match="preface" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$preface.autolabel != 0">
+		<xsl:number from="book" count="preface" format="1" level="any"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="chapter" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$chapter.autolabel != 0">
+		<xsl:number from="book" count="chapter" format="1" level="any"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="appendix" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$chapter.autolabel != 0">
+		<xsl:number from="book" count="appendix" format="A" level="any"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="article" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:if test="@label">
+	    <xsl:value-of select="@label"/>
+	    <xsl:value-of select="$punct"/>
+	</xsl:if>
+    </xsl:template>
+
+
+    <xsl:template match="dedication|colophon" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:if test="@label">
+	    <xsl:value-of select="@label"/>
+	    <xsl:value-of select="$punct"/>
+	</xsl:if>
+    </xsl:template>
+
+    <xsl:template match="reference" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$part.autolabel != 0">
+		<xsl:number from="book" count="reference" format="I" level="any"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="refentry" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:if test="@label">
+	    <xsl:value-of select="@label"/>
+	    <xsl:value-of select="$punct"/>
+	</xsl:if>
+    </xsl:template>
+
+    <xsl:template match="section" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+
+	<xsl:if test="local-name(..) = 'section'">
+	    <xsl:apply-templates select=".." mode="label.content">
+		<xsl:with-param name="punct">.</xsl:with-param>
+	    </xsl:apply-templates>
+	</xsl:if>
+
+	<xsl:variable name="parent.is.component">
+	    <xsl:call-template name="is.component">
+		<xsl:with-param name="node" select=".."/>
+	    </xsl:call-template>
+	</xsl:variable>
+
+	<xsl:variable name="label">
+	    <xsl:call-template name="label.this.section">
+		<xsl:with-param name="section" select="."/>
+	    </xsl:call-template>
+	</xsl:variable>
+
+	<xsl:if test="$section.label.includes.component.label != 0
+	    and $parent.is.component != 0">
+	    <xsl:apply-templates select=".." mode="label.content">
+		<xsl:with-param name="punct">.</xsl:with-param>
+	    </xsl:apply-templates>
+	</xsl:if>
+
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$label != 0">
+		<xsl:number count="section"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="sect1" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+
+	<xsl:variable name="parent.is.component">
+	    <xsl:call-template name="is.component">
+		<xsl:with-param name="node" select=".."/>
+	    </xsl:call-template>
+	</xsl:variable>
+	<xsl:if test="$section.label.includes.component.label != 0
+	    and $parent.is.component">
+	    <xsl:apply-templates select=".." mode="label.content">
+		<xsl:with-param name="punct">.</xsl:with-param>
+	    </xsl:apply-templates>
+	</xsl:if>
+
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$section.autolabel != 0">
+		<xsl:number count="sect1"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="sect2|sect3|sect4|sect5" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+
+	<xsl:apply-templates select=".." mode="label.content">
+	    <xsl:with-param name="punct">.</xsl:with-param>
+	</xsl:apply-templates>
+
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$section.autolabel != 0">
+		<xsl:choose>
+		    <xsl:when test="local-name(.) = 'sect2'">
+			<xsl:number count="sect2"/>
+		    </xsl:when>
+		    <xsl:when test="local-name(.) = 'sect3'">
+			<xsl:number count="sect3"/>
+		    </xsl:when>
+		    <xsl:when test="local-name(.) = 'sect4'">
+			<xsl:number count="sect4"/>
+		    </xsl:when>
+		    <xsl:when test="local-name(.) = 'sect5'">
+			<xsl:number count="sect5"/>
+		    </xsl:when>
+		    <xsl:otherwise>
+			<xsl:message>label.content: this can't happen!</xsl:message>
+		    </xsl:otherwise>
+		</xsl:choose>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+    <xsl:template match="refsect1|refsect2|refsect3" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$section.autolabel != 0">
+		<xsl:number level="multiple" count="refsect1|refsect2|refsect3"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="simplesect" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$section.autolabel != 0">
+		<xsl:number level="multiple" count="section
+		    |sect1|sect2|sect3|sect4|sect5
+		    |refsect1|refsect2|refsect3
+		    |simplesect"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="qandadiv" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:variable name="prefix">
+	    <xsl:if test="$qanda.inherit.numeration != 0">
+		<xsl:variable name="lparent" select="(ancestor::set
+		    |ancestor::book
+		    |ancestor::chapter
+		    |ancestor::appendix
+		    |ancestor::preface
+		    |ancestor::section
+		    |ancestor::simplesect
+		    |ancestor::sect1
+		    |ancestor::sect2
+		    |ancestor::sect3
+		    |ancestor::sect4
+		    |ancestor::sect5
+		    |ancestor::refsect1
+		    |ancestor::refsect2
+		    |ancestor::refsect3)[last()]"/>
+		<xsl:if test="count($lparent)>0">
+		    <xsl:apply-templates select="$lparent" mode="label.content"/>
+		</xsl:if>
+	    </xsl:if>
+	</xsl:variable>
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="$prefix"/>
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:when test="$qandadiv.autolabel != 0">
+		<xsl:value-of select="$prefix"/>
+		<xsl:number level="multiple" count="qandadiv" format="1"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="question|answer" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:variable name="prefix">
+	    <xsl:if test="$qanda.inherit.numeration != 0">
+		<xsl:variable name="lparent" select="(ancestor::set
+		    |ancestor::book
+		    |ancestor::chapter
+		    |ancestor::appendix
+		    |ancestor::preface
+		    |ancestor::section
+		    |ancestor::simplesect
+		    |ancestor::sect1
+		    |ancestor::sect2
+		    |ancestor::sect3
+		    |ancestor::sect4
+		    |ancestor::sect5
+		    |ancestor::refsect1
+		    |ancestor::refsect2
+		    |ancestor::refsect3
+		    |ancestor::qandadiv)[last()]"/>
+		<xsl:if test="count($lparent)>0">
+		    <xsl:apply-templates select="$lparent" mode="label.content"/>
+		</xsl:if>
+	    </xsl:if>
+	</xsl:variable>
+
+	<xsl:variable name="inhlabel"
+	    select="ancestor-or-self::qandaset/@defaultlabel[1]"/>
+
+	<xsl:variable name="deflabel">
+	    <xsl:choose>
+		<xsl:when test="$inhlabel != ''">
+		    <xsl:value-of select="$inhlabel"/>
+		</xsl:when>
+		<xsl:otherwise>
+		    <xsl:value-of select="$qanda.defaultlabel"/>
+		</xsl:otherwise>
+	    </xsl:choose>
+	</xsl:variable>
+
+	<xsl:variable name="label" select="label"/>
+
+	<xsl:choose>
+	    <xsl:when test="count($label)>0">
+		<xsl:value-of select="$prefix"/>
+		<xsl:apply-templates select="$label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+
+	    <xsl:when test="$deflabel = 'qanda'">
+		<xsl:call-template name="gentext.element.name"/>
+	    </xsl:when>
+
+	    <xsl:when test="$deflabel = 'number'">
+		<xsl:if test="name(.) = 'question'">
+		    <xsl:value-of select="$prefix"/>
+		    <xsl:number level="multiple" count="qandaentry" format="1"/>
+		    <xsl:value-of select="$punct"/>
+		</xsl:if>
+	    </xsl:when>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="bibliography|glossary|index" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:if test="@label">
+	    <xsl:value-of select="@label"/>
+	    <xsl:value-of select="$punct"/>
+	</xsl:if>
+    </xsl:template>
+
+    <xsl:template match="figure|table|example|equation" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="@label">
+		<xsl:value-of select="@label"/>
+		<xsl:value-of select="$punct"/>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:variable name="pchap"
+		    select="ancestor::chapter|ancestor::appendix"/>
+		<xsl:choose>
+		    <xsl:when test="count($pchap)>0">
+			<xsl:apply-templates select="$pchap" mode="label.content">
+			    <xsl:with-param name="punct">.</xsl:with-param>
+			</xsl:apply-templates>
+			<xsl:number format="1" from="chapter|appendix" level="any"/>
+			<xsl:value-of select="$punct"/>
+		    </xsl:when>
+		    <xsl:otherwise>
+			<xsl:number format="1" from="book|article" level="any"/>
+			<xsl:value-of select="$punct"/>
+		    </xsl:otherwise>
+		</xsl:choose>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="abstract" mode="label.content">
+	<xsl:param name="punct">.</xsl:param>
+    </xsl:template>
+    --> 
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/latex.mapping.dtd b/docs-xml/xslt/db2latex-xsl/xsl/latex.mapping.dtd
new file mode 100644
index 00000000000..361ce5a18dc
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/latex.mapping.dtd
@@ -0,0 +1,13 @@
+<!ELEMENT latexbindings	(latexmapping+)>
+<!ELEMENT latexmapping 	(mapping+)>
+<!ELEMENT mapping (line*)>
+<!ELEMENT line (#PCDATA)>
+
+<!ATTLIST latexmapping 
+role	CDATA	#REQUIRED
+>
+<!ATTLIST mapping 
+key	CDATA	#REQUIRED
+text	CDATA	#REQUIRED
+>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/latex.mapping.xml b/docs-xml/xslt/db2latex-xsl/xsl/latex.mapping.xml
new file mode 100644
index 00000000000..8e1e0e1f96c
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/latex.mapping.xml
@@ -0,0 +1,498 @@
+<?xml version='1.0'?>
+<!DOCTYPE latexbindings SYSTEM "latex.mapping.dtd" []>
+
+<latexbindings>
+
+    <!-- 	
+    ################################################################
+    Keywords
+    %id%
+    %title%
+    ################################################################ -->	
+
+
+    <!-- LaTeX mapping, role, BEGIN -->
+    <latexmapping role="begin">
+
+	<mapping key="abstract" text="">
+	    <line>&#10;</line>
+	    <line>% --------------------------------------------&#10;</line>
+	    <line>% Abstract &#10;</line>
+	    <line>% --------------------------------------------&#10;</line>
+	    <line>\begin{abstract}&#10;</line>
+	</mapping>	
+
+	<mapping key="abstract-title" text="">
+	    <line>&#10;</line>
+	    <line>% --------------------------------------------&#10;</line>
+	    <line>% Abstract &#10;</line>
+	    <line>% --------------------------------------------&#10;</line>
+      <line>\makeatletter\let\save@@abstractname\abstractname\makeatother&#10;</line>
+      <line>\renewcommand{\abstractname}{%title%}&#10;</line>
+	    <line>\begin{abstract}&#10;</line>
+	</mapping>	
+
+	<mapping key="admonition"	text="">
+	    <line>&#10;</line>
+	    <line>\begin{admonition}%title%% NOTICE: see the db2latex FAQ w.r.t db2latex variable $latex.admonition.path&#10;</line>
+	</mapping>
+
+	<mapping key="appendices-chapter"	text="">
+	    <line>% ------------------------------------------------------------- &#10;</line>
+	    <line>% Appendices start here&#10;</line>
+	    <line>% -------------------------------------------------------------&#10;</line>
+	    <line>\appendix&#10;</line>
+	</mapping>
+
+	<mapping key="appendices-section"	text=""/>
+
+	<mapping key="appendix"		text="">
+	    <line>&#10;</line>
+	    <line>% -------------------------------------------------------------&#10;</line>
+	    <line>% appendix:  %title% &#10;</line>
+	    <line>% ------------------------------------------------------------- 	&#10;</line>
+	    <line>\dbappendix{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="article"	text="">
+    <line>\begin{document}&#10;</line>
+	</mapping>
+
+	<mapping key="bibliography-chapter" text="">
+		<line>% ------------------------------------------- &#10;</line>
+		<line>%&#10;</line>
+		<line>%  Bibliography - chapter&#10;</line>
+		<line>%&#10;</line>
+		<line>% ------------------------------------------- &#10;</line>
+	</mapping>
+
+	<mapping key="bibliography-section" text=""/>
+
+	<mapping key="blockquote"	text="">
+		<line>\begin{quote}&#10;</line>
+	</mapping>
+
+	<mapping key="chapter"	text="">
+	    <line>&#10;</line>
+	    <line>% -------------------------------------------------------------&#10;</line>
+	    <line>% Chapter %title% &#10;</line>
+	    <line>% ------------------------------------------------------------- 	&#10;</line>
+	    <line>\chapter{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="colophon" text="">
+		<line>% -------------------------------------------------------------&#10;</line>
+		<line>% Colophon &#10;</line>
+		<line>% -------------------------------------------------------------&#10;</line>
+		<line>\chapter*{%title%}%&#10;</line>
+		<line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="dedication" text="">
+		<line>% -------------------------------------------------------------&#10;</line>
+		<line>% Dedication &#10;</line>
+		<line>% -------------------------------------------------------------&#10;</line>
+		<line>\chapter*{%title%}%&#10;</line>
+		<line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="epigraph"	text="">
+		<line>\begin{quote}&#10;</line>
+	</mapping>
+
+	<mapping key="figure"	text="">
+	    <line>&#10;</line>
+	    <line>% figure ------------------------------------------------------&#10;</line>
+	    <line>\begin{figure}[%title%]&#10;</line>
+	    <line>\begin{center}%&#10;</line>
+	    <line>\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="index" text="">
+		<line>\indexspace&#10;</line>
+	</mapping>
+
+	<mapping key="informalfigure"	text="">
+	    <line>&#10;</line>
+	    <line>% informalfigure ------------------------------------------------------&#10;</line>
+	    <line>\begin{center}%&#10;</line>
+	    <line>\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="keywordset"	text="">
+	    <line>&#10;</line>
+	    <line>% keywords ------------------------------------------------------&#10;</line>
+	    <line><![CDATA[
+\vspace{-.3em}{
+\if@twocolumn\small\textit{%title%}\bfseries---$\!$%
+\else\begin{center}\small\bfseries{%title%}\end{center}\begin{quote}\small%
+\fi
+]]></line>
+	</mapping>
+
+	<mapping key="table"	text="">
+	    <line>&#10;</line>
+	    <line>% table ------------------------------------------------------&#10;</line>
+	    <line>\begin{table}[%title%]&#10;</line>
+	    <line>\begin{center}%&#10;</line>
+	    <line>\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="informaltable"	text="">
+	    <line>&#10;</line>
+	    <line>% tabular ------------------------------------------------------&#10;</line>
+	    <line>\begin{center}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="equation"	text="">
+	    <line>&#10;\begin{dbequation}&#10;</line>
+	    <line>\begin{center}&#10;</line>
+	    <line>\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="glossary"	text="">
+	    <line>% ------------------------------------------------------------- &#10;</line>
+	    <line>% &#10;</line>
+	    <line>% GLOSSARY %title%&#10;</line>
+	    <line>% &#10;</line>
+	    <line>% ------------------------------------------------------------- &#10;</line>
+	    <line>\dbglossary{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="glossdiv"	text="">
+	    <line>% &#10;</line>
+	    <line>% ------------------------------------------------------------- &#10;</line>
+	    <line>\dbglossdiv{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	    <line>\noindent%&#10;</line>
+	    <line>\begin{description}%&#10;</line>
+	</mapping>
+
+	<mapping key="glosslist"	text="">
+	    <line>% &#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	    <line>\noindent%&#10;</line>
+	    <line>\begin{description}%&#10;</line>
+	</mapping>
+
+	<mapping key="part"	text="">
+	    <line>% ------------------------------------------------------------- &#10;</line>
+	    <line>% &#10;</line>
+	    <line>% PART %title%&#10;</line>
+	    <line>% &#10;</line>
+	    <line>% ------------------------------------------------------------- &#10;</line>
+	    <line>\part{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="partintro"	text="">
+	    <line>&#10;</line>
+	    <line>% -------------------------------------------------------------&#10;</line>
+	    <line>% PartIntro %title% &#10;</line>
+	    <line>% ------------------------------------------------------------- 	&#10;</line>
+	    <line>\chapter*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="preface" text="">
+		<line>% -------------------------------------------------------------&#10;</line>
+		<line>% Preface &#10;</line>
+		<line>% -------------------------------------------------------------&#10;</line>
+		<line>\chapter*{%title%}%&#10;</line>
+		<line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="refentry"	text="">
+	    <line>% &#10;</line>
+	    <line>% -------------------------------------------------------------&#10;</line>
+	    <line>% Refentry &#10;</line>
+	    <line>% ------------------------------------------------------------- 	&#10;</line>
+	    <line>\section*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="refsect1"		text="&#10;\subsection*{%title%}&#10;\label{%id%}&#10;"/>
+	<mapping key="refsect2"		text="&#10;\subsubsection*{%title%}&#10;\label{%id%}&#10;"/>
+	<mapping key="refsect3"		text="&#10;\paragraph*{%title%}&#10;\label{%id%}&#10;"/>
+
+	<mapping key="reference" text="">
+	    <line>% &#10;</line>
+	    <line>% -------------------------------------------------------------&#10;</line>
+	    <line>% Reference &#10;</line>
+	    <line>% ------------------------------------------------------------- 	&#10;</line>
+	    <line>\chapter{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="revhistory" text="">
+	    <line>&#10;</line>
+	    <line>% ------------------------   &#10;</line>
+	    <line>% RevHistory                                 &#10;</line>
+	    <line>% ------------------------   &#10;</line>
+	    <line>\pagebreak&#10;</line>
+	    <line>\section*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	    <line>\begin{center}&#10;</line>
+	    <line>\begin{tt}&#10;</line>
+	    <line>\begin{tabular}{|l||l|l|} \hline&#10;</line>
+	</mapping>
+
+	<mapping key="example"		text="&#10;\begin{example}%&#10;\hypertarget{%id%}{}%&#10;"/>
+
+	<mapping key="programlisting"	text="&#10;\begin{program}%&#10;"/>
+
+	<mapping key="sect1"		text="">
+	    <line>&#10;</line>
+	    <line>% ------------------------   &#10;</line>
+	    <line>% Section &#10;</line>
+	    <line>\section{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect1*"		text="">
+	    <line>&#10;</line>
+	    <line>% ------------------------   &#10;</line>
+	    <line>% Section &#10;</line>
+	    <line>\section*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect2"		text="">
+	    <line>\subsection{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect2*"		text="">
+	    <line>\subsection*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect3"		text="">
+	    <line>\subsubsection{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect3*"		text="">
+	    <line>\subsubsection*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect4"		text="">
+	    <line>\subparagraph*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect4*"		text="">
+	    <line>\subparagraph*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect5"		text="">
+	    <line>\subparagraph*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect5*"		text="">
+	    <line>\subparagraph*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect6"		text="">
+	    <line>\subparagraph*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="sect6*"		text="">
+	    <line>\subparagraph*{%title%}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="set"	text="">
+	    <line>% ------------------------------------------------------------- &#10;</line>
+	    <line>% &#10;</line>
+	    <line>% SET %title%&#10;</line>
+	    <line>% &#10;</line>
+	    <line>% ------------------------------------------------------------- &#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+	<mapping key="setindex" text="">
+		<line>\indexspace&#10;</line>
+	</mapping>
+
+	<mapping key="formalpara"		text="">
+	    <line>\subsubsection*{\small{%title%}}&#10;</line>
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	</mapping>
+
+    </latexmapping>
+
+
+
+    <!-- LaTeX mapping, role, END -->
+
+    <latexmapping role="end">
+
+	<mapping key="abstract" text="">
+	    <line>\end{abstract}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="abstract-title" text="">
+	    <line>\end{abstract}&#10;</line>
+      <line>\makeatletter\let\abstractname\save@@abstractname\makeatother&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="admonition" text="">
+	    <line>\end{admonition}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="appendices-chapter"	text=""/>
+
+	<mapping key="appendices-section"	text=""/>
+
+	<mapping key="appendix"		text=""/>
+
+	<mapping key="article"	text="">
+    <line>\end{document}&#10;</line>
+	</mapping>
+
+	<mapping key="bibliography-chapter" text="">
+		<line>\addcontentsline{toc}{chapter}{%title%}&#10;</line>
+	</mapping>
+
+	<mapping key="bibliography-section" text=""/>
+
+	<mapping key="blockquote"	text="">
+		<line>\end{quote}&#10;</line>
+	</mapping>
+
+	<mapping key="book" text="">
+	    <line>&#10;</line>
+	    <line>\end{document}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="chapter"	text=""/>
+
+	<mapping key="colophon" text=""/>
+
+	<mapping key="dedication" text=""/>
+
+	<mapping key="epigraph"	text="">
+		<line>\end{quote}&#10;</line>
+	</mapping>
+
+	<mapping key="example" text="">
+	    <line>\end{example}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="figure" text="">
+	    <line>\end{center}&#10;</line>
+	    <line>\end{figure}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="index" text="">
+		<line>\addcontentsline{toc}{chapter}{%title%}&#10;</line>
+	</mapping>
+
+	<mapping key="informalfigure" text="">
+	    <line>\label{%id%}&#10;</line>
+	    <line>\end{center}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="equation" text="">
+	    <line>\end{center}&#10;</line>
+	    <line>\end{dbequation}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="glossary"	text="">
+    <line>\addcontentsline{toc}{chapter}{%title%}&#10;</line>
+	</mapping>
+
+	<mapping key="glossdiv"	text="">
+	    <line>\end{description}%&#10;</line>
+	</mapping>
+
+	<mapping key="glosslist"	text="">
+	    <line>\end{description}%&#10;</line>
+	</mapping>
+
+	<mapping key="informaltable" text="">
+	    <line>\end{center}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="keywordset"	text="">
+	    <line><![CDATA[
+\vspace{0.6em}\par
+\if@twocolumn\else\end{quote}\fi
+%\normalsize\rmfamily
+}
+]]></line>
+	</mapping>
+
+	<mapping key="part"	text=""/>
+	<mapping key="partintro"	text=""/>
+	<mapping key="reference"		text=""/>
+	<mapping key="refentry"		text=""/>
+	<mapping key="refsect1"		text=""/>
+	<mapping key="refsect2"		text=""/>
+	<mapping key="refsect3"		text=""/>
+
+	<mapping key="sect1"		text=""/>
+	<mapping key="sect1*"		text=""/>
+	<mapping key="sect2"		text=""/>
+	<mapping key="sect2*"		text=""/>
+	<mapping key="sect3"		text=""/>
+	<mapping key="sect3*"		text=""/>
+	<mapping key="sect4"		text=""/>
+	<mapping key="sect4*"		text=""/>
+	<mapping key="sect5"		text=""/>
+	<mapping key="sect5*"		text=""/>
+	<mapping key="set"	text=""/>
+
+	<mapping key="setindex" text="">
+		<line>\addcontentsline{toc}{chapter}{%title%}&#10;</line>
+	</mapping>
+
+	<mapping key="table" text="">
+	    <line>\end{center}&#10;</line>
+	    <line>\end{table}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="preface" text=""/>
+
+	<mapping key="programlisting" text="">
+	    <line>\label{%id%}\hypertarget{%id%}{}%&#10;</line>
+	    <line>\end{center}&#10;</line>
+	    <line>\end{program}&#10;</line>
+	    <line>&#10;</line>
+	</mapping>	
+
+	<mapping key="revhistory" text="">
+	    <line>\end{tabular}&#10;</line>
+	    <line>\end{tt}&#10;</line>
+	    <line>\end{center}&#10;</line>
+	    <line>% ------------------------  &#10;</line>
+	    <line>% End RevHistory  &#10;</line>
+	    <line>% ------------------------  &#10;</line>
+	</mapping>	
+    </latexmapping>
+
+    <latexmapping role="entities">
+	<mapping key="&#x0221E;"	text=" \infty "/>
+    </latexmapping>
+
+</latexbindings>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/latex.mapping.xsl b/docs-xml/xslt/db2latex-xsl/xsl/latex.mapping.xsl
new file mode 100644
index 00000000000..a1dc5dbf27a
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/latex.mapping.xsl
@@ -0,0 +1,282 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--#############################################################################
+|      $Id: latex.mapping.xsl,v 1.18 2004/01/14 14:54:32 j-devenish Exp $
+|- #############################################################################
+|      $Author: j-devenish $
+|
+|   PURPOSE:
++ ############################################################################## -->
+
+<xsl:stylesheet
+    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+    xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+    exclude-result-prefixes="doc" version='1.0'>
+
+	<!--############################################################################# -->
+	<!-- DOCUMENTATION                                                                -->
+	<doc:reference id="latex.mapping" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+			$Id: latex.mapping.xsl,v 1.18 2004/01/14 14:54:32 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon; &james;
+			</authorgroup>
+			<copyright>
+			<year>2000</year> <year>2001</year> <year>2002</year> <year>2003</year>
+			<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.11">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>The &DB2LaTeX; mapping system <filename>latex.mapping.xsl</filename></title>
+		<partintro>
+			<section><title>Introduction</title>
+			<para>The &DB2LaTeX; mapping system centralises the mapping
+			of &DocBook; tags (e.g. <doc:db>chapter</doc:db>)
+			to &LaTeX; commands (e.g. <function condition="latex">chapter</function>).
+			It uses an auxiliary file, <filename>latex.mapping.xml</filename>,
+			to define the start and end of each mapping.
+			You can override this <quote>mapping file</quote>
+			in order to customise &DB2LaTeX;.</para>
+			</section>
+		</partintro>
+	</doc:reference>
+	<!--############################################################################# -->
+
+	<doc:param name="latex.mapping.xml">
+		<refpurpose>The primary mapping file</refpurpose>
+		<doc:description>
+			<para>
+				&DB2LaTeX; will search for mappings in this file.
+				The value of this variable must be an XML document.
+				If mappings cannot be found in this file, &DB2LaTeX; will
+				search the <link linkend="param.latex.mapping.xml.default">default mapping file</link>.
+			</para>
+		</doc:description>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_mapping;
+			</simplelist>
+		</doc:samples>
+	</doc:param>
+    <xsl:param name="latex.mapping.xml" select="document('latex.mapping.xml')"/>
+
+	<doc:param name="latex.mapping.xml.default">
+		<refpurpose>The default mapping file</refpurpose>
+		<doc:description>
+			<para>
+				Defines the mapping file that &DB2LaTeX; will search
+				when it cannot find a template in the
+				<link linkend="param.latex.mapping.xml">primary mapping file</link>.
+				The value of this variable must be an XML document.
+			</para>
+		</doc:description>
+	</doc:param>
+    <xsl:param name="latex.mapping.xml.default" select="document('latex.mapping.xml')"/>
+
+	<doc:template xmlns="">
+		<refpurpose>Perform &DocBook; to &LaTeX; mapping</refpurpose>
+		<doc:description>
+			
+			
+			
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.mapping.xml"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.mapping.xml.default"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="latex.mapping">
+		<xsl:param name="object" select="."/>
+		<xsl:param name="keyword" select="local-name($object)"/>
+		<xsl:param name="role" select="begin"/>
+		<xsl:param name="string">
+			<xsl:call-template name="extract.object.title">
+				<xsl:with-param name="object" select="$object"/>
+			</xsl:call-template>
+		</xsl:param>
+		<xsl:variable name="id">
+			<xsl:call-template name="generate.label.id">
+				<xsl:with-param name="object" select="$object"/>
+			</xsl:call-template>
+		</xsl:variable>
+		<xsl:variable name="title">
+			<xsl:choose>
+			<xsl:when test="starts-with(local-name($object),'informal')">
+				<xsl:if test="$string!=''">
+					<xsl:message>Ignoring title for <xsl:value-of select="local-name($object)"/>.</xsl:message>
+				</xsl:if>
+			</xsl:when>
+			<xsl:when test="$string=''">
+				<xsl:call-template name="gentext.element.name"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="normalize-space($string)"/>
+			</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:variable name="local.mapping" select="$latex.mapping.xml/latexbindings/latexmapping[@role=$role]/mapping[@key=$keyword]"/>
+		<xsl:variable name="default.mapping" select="$latex.mapping.xml.default/latexbindings/latexmapping[@role=$role]/mapping[@key=$keyword]"/>
+		
+		<xsl:choose>
+			<xsl:when test="$local.mapping and ($local.mapping/@text!='' or not($local.mapping/line))">
+				<xsl:call-template name="string-replace">
+					<xsl:with-param name="to"><xsl:value-of select="$id"/></xsl:with-param>
+					<xsl:with-param name="from">%id%</xsl:with-param>
+					<xsl:with-param name="string">
+						<xsl:call-template name="string-replace">
+							<xsl:with-param name="to"><xsl:value-of select="$title"/></xsl:with-param>
+							<xsl:with-param name="from">%title%</xsl:with-param>
+							<xsl:with-param name="string">
+								<xsl:value-of select="$local.mapping/@text"/>
+							</xsl:with-param>
+						</xsl:call-template>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+
+			<xsl:when test="$local.mapping/line">
+				<xsl:for-each select="$local.mapping/line">
+					<xsl:call-template name="string-replace">
+						<xsl:with-param name="to"><xsl:value-of select="$id"/></xsl:with-param>
+						<xsl:with-param name="from">%id%</xsl:with-param>
+						<xsl:with-param name="string">
+							<xsl:call-template name="string-replace">
+								<xsl:with-param name="to"><xsl:value-of select="$title"/></xsl:with-param>
+								<xsl:with-param name="from">%title%</xsl:with-param>
+								<xsl:with-param name="string" select="."/>
+							</xsl:call-template>
+						</xsl:with-param>
+					</xsl:call-template>
+				</xsl:for-each>
+			</xsl:when>
+
+			<xsl:when test="$default.mapping/@text!=''">
+				<xsl:call-template name="string-replace">
+					<xsl:with-param name="to"><xsl:value-of select="$id"/></xsl:with-param>
+					<xsl:with-param name="from">%id%</xsl:with-param>
+					<xsl:with-param name="string">
+						<xsl:call-template name="string-replace">
+							<xsl:with-param name="to"><xsl:value-of select="$title"/></xsl:with-param>
+							<xsl:with-param name="from">%title%</xsl:with-param>
+							<xsl:with-param name="string">
+								<xsl:value-of select="$default.mapping/@text"/>
+							</xsl:with-param>
+						</xsl:call-template>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+
+			<xsl:when test="$default.mapping">
+			<xsl:for-each select="$default.mapping/line">
+				<xsl:call-template name="string-replace">
+					<xsl:with-param name="to"><xsl:value-of select="$id"/></xsl:with-param>
+					<xsl:with-param name="from">%id%</xsl:with-param>
+					<xsl:with-param name="string">
+						<xsl:call-template name="string-replace">
+							<xsl:with-param name="to"><xsl:value-of select="$title"/></xsl:with-param>
+							<xsl:with-param name="from">%title%</xsl:with-param>
+							<xsl:with-param name="string" select="."/>
+						</xsl:call-template>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:for-each>
+
+			</xsl:when>
+				<xsl:otherwise>
+					<xsl:message terminate="no">
+						<xsl:text>Warning: Unable to find LaTeX mapping for &#10;</xsl:text>
+						<xsl:text>KEYWORD:</xsl:text><xsl:value-of select="$keyword"/><xsl:text>&#10;</xsl:text>
+						<xsl:text>ROLE:</xsl:text><xsl:value-of select="$role"/><xsl:text>&#10;</xsl:text>
+					</xsl:message>
+				</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+
+
+
+    <xsl:template name="map.begin">
+	<xsl:param name="object"  select="."/>
+	<xsl:param name="keyword" select="local-name($object)"/>
+	<xsl:param name="string">
+		<xsl:call-template name="extract.object.title">
+			<xsl:with-param name="object" select="$object"/>
+		</xsl:call-template>
+	</xsl:param>
+	<xsl:call-template name="latex.mapping">
+	    <xsl:with-param name="keyword" select="$keyword"/>
+	    <xsl:with-param name="role">begin</xsl:with-param>
+	    <xsl:with-param name="string" select="$string"/>
+	</xsl:call-template>
+    </xsl:template>
+
+    <xsl:template name="map.end">
+	<xsl:param name="object"  select="."/>
+	<xsl:param name="keyword" select="local-name($object)"/>
+	<xsl:param name="role" 	  select="begin"/>
+	<xsl:param name="string">
+		<xsl:call-template name="extract.object.title">
+			<xsl:with-param name="object" select="$object"/>
+		</xsl:call-template>
+	</xsl:param>
+	<xsl:call-template name="latex.mapping">
+	    <xsl:with-param name="keyword" select="$keyword"/>
+	    <xsl:with-param name="string" select="$string"/>
+	    <xsl:with-param name="role">end</xsl:with-param>
+	</xsl:call-template>
+    </xsl:template>
+
+	<doc:template name="extract.object.title">
+		<refpurpose>Choose a title for an object</refpurpose>
+		<doc:description>
+			<para>
+				Processes the <sgmltag class="element">title</sgmltag> child
+				of the specified object. Uses the context node as the default object.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.apply.title.templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry><term>object</term><listitem><simpara>The node for which a title is desired.</simpara></listitem></varlistentry>
+			</variablelist>
+		</doc:params>
+	</doc:template>
+	<xsl:template name="extract.object.title">
+		<xsl:param name="object"  select="."/>
+		<xsl:choose>
+			<xsl:when test="$latex.apply.title.templates='1'">
+				<xsl:apply-templates select="$object/title" mode="latex"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="normalize-scape">
+					<xsl:with-param name="string" select="$object/title"/>
+				</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template match="title" mode="latex">
+		<refpurpose>Process <doc:db>title</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>Applies templates with no mode. This template is called by <xref linkend="template.extract.object.title"/>.</para>
+			<para>This differs from the modeless <doc:db>title</doc:db>
+			templates because they suppress the output of titles.</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="title" mode="latex"><xsl:apply-templates/></xsl:template>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/lists.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/lists.mod.xsl
new file mode 100644
index 00000000000..d04f9c77da5
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/lists.mod.xsl
@@ -0,0 +1,783 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: lists.mod.xsl,v 1.25 2004/01/31 11:53:50 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="lists" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: lists.mod.xsl,v 1.25 2004/01/31 11:53:50 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.16">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Lists <filename>lists.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process titles for <doc:db>variablelist</doc:db>, <doc:db>orderedlist</doc:db>, <doc:db>itemizedlist</doc:db> and <doc:db>simplelist</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Formats a title.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<variablelist>
+				<varlistentry>
+					<term><xref linkend="param.latex.list.title.style"/></term>
+					<listitem><simpara>
+					The &LaTeX; command for formatting titles.
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>style</term>
+					<listitem><simpara>The &LaTeX; command to use. Defaults to
+					<xref linkend="param.latex.list.title.style"/>.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+				Applies templates as a paragraph, formatted with the specified style.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="variablelist/title|orderedlist/title|itemizedlist/title|simplelist/title">
+		<xsl:param name="style" select="$latex.list.title.style"/>
+		<xsl:text>&#10;{</xsl:text>
+		<xsl:value-of select="$style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>}}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="listitem" xmlns="">
+		<refpurpose>Process <doc:db>listitem</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a list item.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Applies templates within a &LaTeX; <function condition="latex">item</function>
+				command.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="listitem">
+		<xsl:text>&#10;%--- Item&#10;</xsl:text>
+		<xsl:text>\item </xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>itemizedlist</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats an itemised list.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.noindent"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Applies templates. Uses a &LaTeX; <function condition="env">itemize</function>
+				environment.
+			</para>
+			<para>
+				The <sgmltag class="attribute">spacing</sgmltag>=<quote>compact</quote>
+				attribute is recognised.
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_chemistry;
+				&test_lists;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="itemizedlist">
+		<xsl:apply-templates select="node()[not(self::listitem)]"/>
+		<xsl:call-template name="compactlist.pre"/>
+		<xsl:text>&#10;\begin{itemize}</xsl:text>
+		<xsl:call-template name="compactlist.begin"/>
+		<xsl:apply-templates select="listitem"/>
+		<xsl:text>\end{itemize}&#10;</xsl:text>
+		<xsl:call-template name="compactlist.post"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>variablelist</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a list in which each item is denoted by a textual label.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.noindent"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Applies templates. Uses a &LaTeX; <function condition="env">description</function>
+				environment.
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_bind;
+				&test_book;
+				&test_ddh;
+				&test_lists;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="variablelist">
+		<xsl:apply-templates select="node()[not(self::varlistentry)]"/>
+		<xsl:text>&#10;\begin{description}&#10;</xsl:text>
+		<xsl:apply-templates select="varlistentry"/>
+		<xsl:text>\end{description}&#10;</xsl:text>
+		<xsl:if test="$latex.use.noindent=1">
+			<xsl:text>\noindent </xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>orderedlist</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a list in which each item is denoted by a numeric label.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.noindent"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>The only &DocBook; attribute that is supported is <sgmltag class="attribute">numeration</sgmltag>.</para>
+			<para>
+				Applies templates. Uses a &LaTeX; <function condition="env">enumerate</function>
+				environment.
+			</para>
+			<para>
+				The <sgmltag class="attribute">spacing</sgmltag>=<quote>compact</quote>
+				attribute is recognised.
+			</para>
+			<para>
+				The <sgmltag class="attribute">numeration</sgmltag> attribute
+				is recognised.
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_chemistry;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="orderedlist">
+		<xsl:variable name="numeration">
+			<xsl:choose>
+				<xsl:when test="@numeration">
+					<xsl:value-of select="@numeration"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="arabic"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:apply-templates select="node()[not(self::listitem)]"/>
+		<xsl:call-template name="compactlist.pre"/>
+		<xsl:text>&#10;\begin{enumerate}</xsl:text>
+		<xsl:if test="@numeration">
+			<xsl:choose>
+			<xsl:when test="@numeration='arabic'"> 	<xsl:text>[1]</xsl:text>&#10;</xsl:when>
+			<xsl:when test="@numeration='upperalpha'"><xsl:text>[A]</xsl:text>&#10;</xsl:when>
+			<xsl:when test="@numeration='loweralpha'"><xsl:text>[a]</xsl:text>&#10;</xsl:when>
+			<xsl:when test="@numeration='upperroman'"><xsl:text>[I]</xsl:text>&#10;</xsl:when>
+			<xsl:when test="@numeration='lowerroman'"><xsl:text>[i]</xsl:text>&#10;</xsl:when>
+			</xsl:choose>
+		</xsl:if>
+		<xsl:call-template name="compactlist.begin"/>
+		<xsl:apply-templates select="listitem"/>
+		<xsl:text>\end{enumerate}&#10;</xsl:text>
+		<xsl:call-template name="compactlist.post"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>varlistentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a labeled list item.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Applies templates within a &LaTeX; <function condition="latex">item</function>
+				command.
+				A comma is inserted between successive <doc:db basename="term">terms</doc:db>.
+			</para>
+			<para>
+				A &LaTeX; <function condition="latex">null{}</function> command is
+				inserted after the <function condition="latex">item</function> to
+				guard against empty <doc:db basename="listitem">listitems</doc:db>.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="varlistentry">
+		<xsl:param name="object" select="listitem/*[1]"/>
+		<xsl:param name="next.is.list">
+			<xsl:value-of select="count($object[self::itemizedlist or self::orderedlist or self::variablelist])"/>
+		</xsl:param>
+		<xsl:variable name="id">
+			<xsl:call-template name="label.id"/>
+		</xsl:variable>
+		<xsl:text>% \null and \mbox are tricks to induce different typesetting decisions&#10;</xsl:text>
+		<xsl:text>\item[{</xsl:text>
+		<xsl:for-each select="term">
+			<xsl:apply-templates/>
+			<xsl:if test="position()!=last()">
+				<xsl:text>, </xsl:text>
+			</xsl:if>
+		</xsl:for-each>
+		<xsl:choose>
+			<xsl:when test="$next.is.list=1">
+				<xsl:text>}]\mbox{}</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>}]\null{}</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:apply-templates select="listitem"/>
+	</xsl:template>
+
+	<doc:template basename="term" xmlns="">
+		<refpurpose>Process <doc:db>varlistentry</doc:db>'s <doc:db>term</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="varlistentry/term">
+		<xsl:apply-templates/><xsl:text>, </xsl:text>
+	</xsl:template>
+
+	<doc:template basename="listitem" xmlns="">
+		<refpurpose>Process <doc:db>listitem</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Unlike <xref linkend="template.listitem"/>, the \item
+				has been output by the enclosing element's template.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="varlistentry/listitem">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Generate a <function condition="env">tabular</function> specification</refpurpose>
+		<doc:description>
+			<para>
+			
+			Produces a left-aligned tabular specification list.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>cols</term>
+					<listitem><simpara>The number of repetitions</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+	</doc:template>
+	<xsl:template name="generate.simplelist.tabular.string">
+		<xsl:param name="cols" select="1"/>
+		<xsl:param name="i" select="1"/>
+		<xsl:choose>
+			<xsl:when test="$i > $cols"></xsl:when>
+			<xsl:otherwise>
+			<xsl:text>l</xsl:text>
+			<xsl:call-template name="generate.simplelist.tabular.string">
+				<xsl:with-param name="i" select="$i+1"/>
+				<xsl:with-param name="cols" select="$cols"/>
+			</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template basename="simplelist" xmlns="">
+		<refpurpose>Process <doc:db>simplelist</doc:db> elements with inline <doc:db basename="member">members</doc:db></refpurpose>
+		<doc:description>
+			<para>
+			Formats a simple, comma-separated list for a <doc:db>simplelist</doc:db>
+			that has a <sgmltag class="attribute">type</sgmltag> attribute equal to <quote>inline</quote>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				This is not made into a paragraph and is not temrinated by a full stop (<quote>period</quote>).
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="simplelist[@type='inline']" name="generate.simplelist.inline">
+		<xsl:for-each select="member">
+			<xsl:apply-templates/>
+			<xsl:if test="position()!=last()">
+				<xsl:text>, </xsl:text>
+			</xsl:if>
+		</xsl:for-each>
+	</xsl:template>
+
+	<doc:template basename="simplelist" xmlns="">
+		<refpurpose>Process <doc:db>simplelist</doc:db> elements with <quote>horiz</quote> <doc:db basename="member">members</doc:db></refpurpose>
+		<doc:description>
+			<para>
+			Formats a simple, comma-separated list for a <doc:db>simplelist</doc:db>
+			that has a <sgmltag class="attribute">type</sgmltag> attribute equal to <quote>horiz</quote>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>environment</term>
+					<listitem><simpara>The &LaTeX; tabular-like environment to use. Defaults to <quote>tabular</quote> unless <xref linkend="param.latex.use.ltxtable"/> or <xref linkend="param.latex.use.longtable"/> is enabled, in which case the default is <quote>longtable</quote>.</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>cols</term>
+					<listitem><simpara>The number of members per line (defaults to the value of the <sgmltag class="attribute">columns</sgmltag> attribute).</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+				This is formatted as a border-less &LaTeX; table.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="simplelist[@type='horiz']" name="generate.simplelist.horiz">
+		<xsl:param name="environment">
+			<xsl:choose>
+				<xsl:when test="$latex.use.ltxtable='1' or $latex.use.longtable='1'">
+					<xsl:text>longtable</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>tabular</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:param name="cols">
+			<xsl:choose>
+			<xsl:when test="@columns">
+				<xsl:value-of select="@columns"/>
+			</xsl:when>
+			<xsl:otherwise>1</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>\begin{</xsl:text>
+		<xsl:value-of select="$environment"/>
+		<xsl:text>}{</xsl:text>
+		<xsl:call-template name="generate.simplelist.tabular.string">
+			<xsl:with-param name="cols" select="$cols"/>
+		</xsl:call-template>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:call-template name="simplelist.horiz">
+			<xsl:with-param name="cols" select="$cols"/>
+		</xsl:call-template>
+		<xsl:text>&#10;\end{</xsl:text>
+		<xsl:value-of select="$environment"/>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+    <xsl:template name="simplelist.horiz">
+	<xsl:param name="cols">1</xsl:param>
+	<xsl:param name="cell">1</xsl:param>
+	<xsl:param name="members" select="./member"/>
+	<xsl:if test="$cell &lt;= count($members)">
+	    <xsl:text>&#10;</xsl:text> 
+	    <xsl:call-template name="simplelist.horiz.row">
+		<xsl:with-param name="cols" select="$cols"/>
+		<xsl:with-param name="cell" select="$cell"/>
+		<xsl:with-param name="members" select="$members"/>
+	    </xsl:call-template>
+	    <xsl:text> \\</xsl:text> 
+	    <xsl:call-template name="simplelist.horiz">
+		<xsl:with-param name="cols" select="$cols"/>
+		<xsl:with-param name="cell" select="$cell + $cols"/>
+		<xsl:with-param name="members" select="$members"/>
+	    </xsl:call-template>
+	</xsl:if>
+    </xsl:template>
+
+    <xsl:template name="simplelist.horiz.row">
+	<xsl:param name="cols">1</xsl:param>
+	<xsl:param name="cell">1</xsl:param>
+	<xsl:param name="members" select="./member"/>
+	<xsl:param name="curcol">1</xsl:param>
+	<xsl:if test="$curcol &lt;= $cols">
+	    <xsl:choose>
+		<xsl:when test="$members[position()=$cell]">
+		    <xsl:apply-templates select="$members[position()=$cell]"/>
+		    <xsl:text> </xsl:text> 
+		    <xsl:if test="$curcol &lt; $cols">
+			<xsl:call-template name="generate.latex.cell.separator"/>
+		    </xsl:if>
+		</xsl:when>
+	    </xsl:choose>
+	    <xsl:call-template name="simplelist.horiz.row">
+		<xsl:with-param name="cols" select="$cols"/>
+		<xsl:with-param name="cell" select="$cell+1"/>
+		<xsl:with-param name="members" select="$members"/>
+		<xsl:with-param name="curcol" select="$curcol+1"/>
+	    </xsl:call-template>
+	</xsl:if>
+    </xsl:template>
+
+	<doc:template basename="simplelist" xmlns="">
+		<refpurpose>Process <doc:db>simplelist</doc:db> elements with <quote>vert</quote> <doc:db basename="member">members</doc:db></refpurpose>
+		<doc:description>
+			<para>
+			Formats a simple, comma-separated list for a <doc:db>simplelist</doc:db>
+			that has a <sgmltag class="attribute">type</sgmltag> attribute that is either
+			empty or equal to <quote>vert</quote>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>environment</term>
+					<listitem><simpara>The &LaTeX; tabular-like environment to use. Defaults to <quote>tabular</quote> unless <xref linkend="param.latex.use.ltxtable"/> or <xref linkend="param.latex.use.longtable"/> is set, in which case the default is <quote>longtable</quote>.</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>cols</term>
+					<listitem><simpara>The number of members per line (defaults to the value of the <sgmltag class="attribute">columns</sgmltag> attribute).</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+				This is formatted as a border-less &LaTeX; table.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="simplelist|simplelist[@type='vert']" name="generate.simplelist.vert">
+		<xsl:param name="environment">
+			<xsl:choose>
+				<xsl:when test="$latex.use.ltxtable='1' or $latex.use.longtable='1'">
+					<xsl:text>longtable</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>tabular</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:param name="cols">
+			<xsl:choose>
+			<xsl:when test="@columns">
+				<xsl:value-of select="@columns"/>
+			</xsl:when>
+			<xsl:otherwise>1</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>\begin{</xsl:text>
+		<xsl:value-of select="$environment"/>
+		<xsl:text>}{</xsl:text>
+		<xsl:call-template name="generate.simplelist.tabular.string">
+			<xsl:with-param name="cols" select="$cols"/>
+		</xsl:call-template>
+		<xsl:text>}&#10;</xsl:text> 
+		<xsl:call-template name="simplelist.vert">
+			<xsl:with-param name="cols" select="$cols"/>
+		</xsl:call-template>
+		<xsl:text>&#10;\end{</xsl:text>
+		<xsl:value-of select="$environment"/>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+    <xsl:template name="simplelist.vert">
+	<xsl:param name="cols">1</xsl:param>
+	<xsl:param name="cell">1</xsl:param>
+	<xsl:param name="members" select="./member"/>
+	<xsl:param name="rows" select="floor((count($members)+$cols - 1) div $cols)"/>
+	<xsl:if test="$cell &lt;= $rows">
+	    <xsl:text>&#10;</xsl:text> 
+	    <xsl:call-template name="simplelist.vert.row">
+		<xsl:with-param name="cols" select="$cols"/>
+		<xsl:with-param name="rows" select="$rows"/>
+		<xsl:with-param name="cell" select="$cell"/>
+		<xsl:with-param name="members" select="$members"/>
+	    </xsl:call-template>
+	    <xsl:text> \\</xsl:text> 
+	    <xsl:call-template name="simplelist.vert">
+		<xsl:with-param name="cols" select="$cols"/>
+		<xsl:with-param name="cell" select="$cell+1"/>
+		<xsl:with-param name="members" select="$members"/>
+		<xsl:with-param name="rows" select="$rows"/>
+	    </xsl:call-template>
+	</xsl:if>
+    </xsl:template>
+
+    <xsl:template name="simplelist.vert.row">
+	<xsl:param name="cols">1</xsl:param>
+	<xsl:param name="rows">1</xsl:param>
+	<xsl:param name="cell">1</xsl:param>
+	<xsl:param name="members" select="./member"/>
+	<xsl:param name="curcol">1</xsl:param>
+	<xsl:if test="$curcol &lt;= $cols">
+	    <xsl:choose>
+		<xsl:when test="$members[position()=$cell]">
+		    <xsl:apply-templates select="$members[position()=$cell]"/>
+		    <xsl:text> </xsl:text> 
+		    <xsl:if test="$curcol &lt; $cols">
+			<xsl:call-template name="generate.latex.cell.separator"/>
+		    </xsl:if>
+		</xsl:when>
+		<xsl:otherwise>
+		</xsl:otherwise>
+	    </xsl:choose>
+	    <xsl:call-template name="simplelist.vert.row">
+		<xsl:with-param name="cols" select="$cols"/>
+		<xsl:with-param name="rows" select="$rows"/>
+		<xsl:with-param name="cell" select="$cell+$rows"/>
+		<xsl:with-param name="members" select="$members"/>
+		<xsl:with-param name="curcol" select="$curcol+1"/>
+	    </xsl:call-template>
+	</xsl:if>
+    </xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>member</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="member">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>segmentedlist</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="segmentedlist">
+		<xsl:apply-templates select="title|titleabbrev"/>
+		<xsl:apply-templates select="seglistitem"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process titles for <doc:db>segmentedlist</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			Formats a title as a paragraph.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>style</term>
+					<listitem><simpara>The &LaTeX; command to use.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+				Applies templates as a paragraph, formatted with the specified style, and
+				terminated with a newline command.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="segmentedlist/title">
+		<xsl:param name="style" select="$latex.list.title.style"/>
+		<xsl:text>&#10;{</xsl:text>
+		<xsl:value-of select="$style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>}}\\&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>segtitle</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="segtitle">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>seglistitem</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a segmented list item.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>Applies <doc:db>seg</doc:db> templates. Each item is separated by a &LaTeX;
+			<function condition="latex">\</function> command.</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="seglistitem">
+		<xsl:apply-templates/>
+		<xsl:choose>
+			<xsl:when test="position()=last()"><xsl:text>&#10;&#10;</xsl:text></xsl:when>
+			<xsl:otherwise><xsl:text> \\&#10;</xsl:text></xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>seg</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a <doc:db>seg</doc:db> with its <doc:db>segtitle</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.segtitle.style"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="seg">
+		<xsl:variable name="segnum" select="position()"/>
+		<xsl:variable name="seglist" select="ancestor::segmentedlist"/>
+		<xsl:variable name="segtitles" select="$seglist/segtitle"/>
+
+		<!--
+		Note: segtitle is only going to be the right thing in a well formed
+		SegmentedList.  If there are too many Segs or too few SegTitles,
+		you'll get something odd...maybe an error
+		-->
+
+		<xsl:text> {</xsl:text>
+		<xsl:value-of select="$latex.segtitle.style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:apply-templates select="$segtitles[$segnum=position()]"/>
+		<xsl:text>:}} </xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template name="compactlist.pre">
+		<xsl:if test="@spacing='compact'">
+			<xsl:if test="$latex.use.parskip=1">
+				<xsl:text>&#10;\docbooktolatexnoparskip</xsl:text>
+			</xsl:if>
+		</xsl:if>
+	</xsl:template>
+
+	<xsl:template name="compactlist.begin">
+		<xsl:if test="@spacing='compact' and $latex.use.parskip!=1">
+			<xsl:text>\setlength{\itemsep}{-0.25em}&#10;</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<xsl:template name="compactlist.post">
+		<xsl:if test="@spacing='compact' and $latex.use.parskip=1">
+			<xsl:text>\docbooktolatexrestoreparskip&#10;</xsl:text>
+		</xsl:if>
+		<xsl:if test="$latex.use.noindent=1">
+			<xsl:text>\noindent </xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathelem.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/mathelem.mod.xsl
new file mode 100644
index 00000000000..6b78a8f4206
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathelem.mod.xsl
@@ -0,0 +1,297 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: mathelem.mod.xsl,v 1.4 2004/01/02 05:03:28 j-devenish Exp $		
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="mathelems" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: mathelem.mod.xsl,v 1.4 2004/01/02 05:03:28 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.4">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Mathematics <filename>mathelems.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			Mathelements as theorems, lemmas, propositions, etc. Note: these
+			elements are not part of the &DocBook; DTD. I have extended the
+			&DocBook; in order to support this tags, so that's why I have these
+			templates here.
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathelement</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="mathelement">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Typeset mathelement environments</refpurpose>
+		<doc:description>
+			<para>
+
+				Applies templates within the specified &LaTeX; environment,
+				with a title from any <doc:db>title</doc:db> child.
+				<doc:todo>No hypertarget is generated.</doc:todo>
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>environment</term>
+					<listitem><simpara>The name of the &LaTeX; environment command.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+	</doc:template>
+	<xsl:template name="mathelement.environment">
+		<xsl:param name="environment" select="'hypothesis'"/>
+		<xsl:text>\begin{</xsl:text>
+		<xsl:value-of select="$environment"/>
+		<xsl:text>}[{</xsl:text>
+		<xsl:call-template name="normalize-scape">
+			<xsl:with-param name="string" select="title"/> 
+		</xsl:call-template>
+		<xsl:text>}]&#10;</xsl:text>
+		<xsl:variable name="id"> <xsl:call-template name="label.id"/> </xsl:variable>
+		<xsl:call-template name="content-templates"/>
+		<xsl:text>\end{</xsl:text>
+		<xsl:value-of select="$environment"/>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathelement/mathhypothesis</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a hypothesis.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.mathelement.environment"/>
+				for the <quote>hypothesis</quote> environment.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="mathelement/mathhypothesis">
+		<xsl:call-template name="mathelement.environment">
+			<xsl:with-param name="environment" select="'hypothesis'"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathelement/mathremark</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a mathematical remark.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.mathelement.environment"/>
+				for the <quote>rem</quote> environment.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="mathelement/mathremark">
+		<xsl:call-template name="mathelement.environment">
+			<xsl:with-param name="environment" select="'rem'"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathelement/mathexample</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a mathematical example.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.mathelement.environment"/>
+				for the <quote>exm</quote> environment.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="mathelement/mathexample">
+		<xsl:call-template name="mathelement.environment">
+			<xsl:with-param name="environment" select="'exm'"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathelement/mathproposition</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a mathematical proposition.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.mathelement.environment"/>
+				for the <quote>prop</quote> environment.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="mathelement/mathproposition">
+		<xsl:call-template name="mathelement.environment">
+			<xsl:with-param name="environment" select="'prop'"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathelement/maththeorem</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a mathematical theorem.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.mathelement.environment"/>
+				for the <quote>thm</quote> environment.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="mathelement/maththeorem">
+		<xsl:call-template name="mathelement.environment">
+			<xsl:with-param name="environment" select="'thm'"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathelement/mathdefinition</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a mathematical definition.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.mathelement.environment"/>
+				for the <quote>defn</quote> environment.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="mathelement/mathdefinition">
+		<xsl:call-template name="mathelement.environment">
+			<xsl:with-param name="environment" select="'defn'"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathelement/mathlemma</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a mathematical lemma.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.mathelement.environment"/>
+				for the <quote>lem</quote> environment.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="mathelement/mathlemma">
+		<xsl:call-template name="mathelement.environment">
+			<xsl:with-param name="environment" select="'lem'"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathelement/mathproof</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a mathematical proof.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Calls <xref linkend="template.mathelement.environment"/>
+				for the <quote>proof</quote> environment.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="mathelement/mathproof">
+		<xsl:call-template name="mathelement.environment">
+			<xsl:with-param name="environment" select="'proof'"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>mathphrase</sgmltag>, <sgmltag>mathcondition</sgmltag> and <sgmltag>mathassertion</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="mathphrase|mathcondition|mathassertion">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsa.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsa.ent
new file mode 100644
index 00000000000..5ecf4db2162
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsa.ent
@@ -0,0 +1,173 @@
+
+<!--
+     File isoamsa.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY angzarr          "&#x0237C;" ><!--angle with down zig-zag arrow -->
+<!ENTITY cirmid           "&#x02AEF;" ><!--circle, mid below -->
+<!ENTITY cudarrl          "&#x02938;" ><!--left, curved, down arrow -->
+<!ENTITY cudarrr          "&#x02935;" ><!--right, curved, down arrow -->
+<!ENTITY cularr           "&#x021B6;" ><!--/curvearrowleft A: left curved arrow -->
+<!ENTITY cularrp          "&#x0293D;" ><!--curved left arrow with plus -->
+<!ENTITY curarr           "&#x021B7;" ><!--/curvearrowright A: rt curved arrow -->
+<!ENTITY curarrm          "&#x0293C;" ><!--curved right arrow with minus -->
+<!ENTITY dArr             "&#x021D3;" ><!--/Downarrow A: down dbl arrow -->
+<!ENTITY Darr             "&#x021A1;" ><!--down two-headed arrow -->
+<!ENTITY ddarr            "&#x021CA;" ><!--/downdownarrows A: two down arrows -->
+<!ENTITY DDotrahd         "&#x02911;" ><!--right arrow with dotted stem -->
+<!ENTITY dfisht           "&#x0297F;" ><!--down fish tail -->
+<!ENTITY dHar             "&#x02965;" ><!--down harpoon-left, down harpoon-right -->
+<!ENTITY dharl            "&#x021C3;" ><!--/downharpoonleft A: dn harpoon-left -->
+<!ENTITY dharr            "&#x021C2;" ><!--/downharpoonright A: down harpoon-rt -->
+<!ENTITY duarr            "&#x021F5;" ><!--down arrow, up arrow -->
+<!ENTITY duhar            "&#x0296F;" ><!--down harp, up harp -->
+<!ENTITY dzigrarr         "&#x021DD;" ><!--right long zig-zag arrow -->
+<!ENTITY erarr            "&#x02971;" ><!--equal, right arrow below -->
+<!ENTITY harr             "&#x02194;" ><!--/leftrightarrow A: l&r arrow -->
+<!ENTITY hArr             "&#x021D4;" ><!--/Leftrightarrow A: l&r dbl arrow -->
+<!ENTITY harrcir          "&#x02948;" ><!--left and right arrow with a circle -->
+<!ENTITY harrw            "&#x021AD;" ><!--/leftrightsquigarrow A: l&r arr-wavy -->
+<!ENTITY hoarr            "&#x021FF;" ><!--horizontal open arrow -->
+<!ENTITY imof             "&#x022B7;" ><!--image of -->
+<!ENTITY lAarr            "&#x021DA;" ><!--/Lleftarrow A: left triple arrow -->
+<!ENTITY Larr             "&#x0219E;" ><!--/twoheadleftarrow A: -->
+<!ENTITY larrbfs          "&#x0291F;" ><!--left arrow-bar, filled square -->
+<!ENTITY larrfs           "&#x0291D;" ><!--left arrow, filled square -->
+<!ENTITY larrhk           "&#x021A9;" ><!--/hookleftarrow A: left arrow-hooked -->
+<!ENTITY larrlp           "&#x021AB;" ><!--/looparrowleft A: left arrow-looped -->
+<!ENTITY larrpl           "&#x02939;" ><!--left arrow, plus -->
+<!ENTITY larrsim          "&#x02973;" ><!--left arrow, similar -->
+<!ENTITY larrtl           "&#x021A2;" ><!--/leftarrowtail A: left arrow-tailed -->
+<!ENTITY latail           "&#x02919;" ><!--left arrow-tail -->
+<!ENTITY lAtail           "&#x0291B;" ><!--left double arrow-tail -->
+<!ENTITY lbarr            "&#x0290C;" ><!--left broken arrow -->
+<!ENTITY lBarr            "&#x0290E;" ><!--left doubly broken arrow -->
+<!ENTITY ldca             "&#x02936;" ><!--left down curved arrow -->
+<!ENTITY ldrdhar          "&#x02967;" ><!--left harpoon-down over right harpoon-down -->
+<!ENTITY ldrushar         "&#x0294B;" ><!--left-down-right-up harpoon -->
+<!ENTITY ldsh             "&#x021B2;" ><!--left down angled arrow -->
+<!ENTITY lfisht           "&#x0297C;" ><!--left fish tail -->
+<!ENTITY lHar             "&#x02962;" ><!--left harpoon-up over left harpoon-down -->
+<!ENTITY lhard            "&#x021BD;" ><!--/leftharpoondown A: l harpoon-down -->
+<!ENTITY lharu            "&#x021BC;" ><!--/leftharpoonup A: left harpoon-up -->
+<!ENTITY lharul           "&#x0296A;" ><!--left harpoon-up over long dash -->
+<!ENTITY llarr            "&#x021C7;" ><!--/leftleftarrows A: two left arrows -->
+<!ENTITY llhard           "&#x0296B;" ><!--left harpoon-down below long dash -->
+<!ENTITY loarr            "&#x021FD;" ><!--left open arrow -->
+<!ENTITY lrarr            "&#x021C6;" ><!--/leftrightarrows A: l arr over r arr -->
+<!ENTITY lrhar            "&#x021CB;" ><!--/leftrightharpoons A: l harp over r -->
+<!ENTITY lrhard           "&#x0296D;" ><!--right harpoon-down below long dash -->
+<!ENTITY lsh              "&#x021B0;" ><!--/Lsh A: -->
+<!ENTITY lurdshar         "&#x0294A;" ><!--left-up-right-down harpoon -->
+<!ENTITY luruhar          "&#x02966;" ><!--left harpoon-up over right harpoon-up -->
+<!ENTITY map              "&#x021A6;" ><!--/mapsto A: -->
+<!ENTITY Map              "&#x02905;" ><!--twoheaded mapsto -->
+<!ENTITY midcir           "&#x02AF0;" ><!--mid, circle below  -->
+<!ENTITY mumap            "&#x022B8;" ><!--/multimap A: -->
+<!ENTITY nearhk           "&#x02924;" ><!--NE arrow-hooked -->
+<!ENTITY nearr            "&#x02197;" ><!--/nearrow A: NE pointing arrow -->
+<!ENTITY neArr            "&#x021D7;" ><!--NE pointing dbl arrow -->
+<!ENTITY nesear           "&#x02928;" ><!--/toea A: NE & SE arrows -->
+<!ENTITY nharr            "&#x021AE;" ><!--/nleftrightarrow A: not l&r arrow -->
+<!ENTITY nhArr            "&#x021CE;" ><!--/nLeftrightarrow A: not l&r dbl arr -->
+<!ENTITY nlarr            "&#x0219A;" ><!--/nleftarrow A: not left arrow -->
+<!ENTITY nlArr            "&#x021CD;" ><!--/nLeftarrow A: not implied by -->
+<!ENTITY nrarr            "&#x0219B;" ><!--/nrightarrow A: not right arrow -->
+<!ENTITY nrArr            "&#x021CF;" ><!--/nRightarrow A: not implies -->
+<!ENTITY nrarrc           "&#x02933;&#x00338;" ><!--not right arrow-curved -->
+<!ENTITY nrarrw           "&#x0219D;&#x00338;" ><!--not right arrow-wavy -->
+<!ENTITY nvHarr           "&#x021CE;" ><!--not, vert, left and right double arrow  -->
+<!ENTITY nvlArr           "&#x021CD;" ><!--not, vert, left double arrow -->
+<!ENTITY nvrArr           "&#x021CF;" ><!--not, vert, right double arrow -->
+<!ENTITY nwarhk           "&#x02923;" ><!--NW arrow-hooked -->
+<!ENTITY nwarr            "&#x02196;" ><!--/nwarrow A: NW pointing arrow -->
+<!ENTITY nwArr            "&#x021D6;" ><!--NW pointing dbl arrow -->
+<!ENTITY nwnear           "&#x02927;" ><!--NW & NE arrows -->
+<!ENTITY olarr            "&#x021BA;" ><!--/circlearrowleft A: l arr in circle -->
+<!ENTITY orarr            "&#x021BB;" ><!--/circlearrowright A: r arr in circle -->
+<!ENTITY origof           "&#x022B6;" ><!--original of -->
+<!ENTITY rAarr            "&#x021DB;" ><!--/Rrightarrow A: right triple arrow -->
+<!ENTITY Rarr             "&#x021A0;" ><!--/twoheadrightarrow A: -->
+<!ENTITY rarrap           "&#x02975;" ><!--approximate, right arrow above -->
+<!ENTITY rarrbfs          "&#x02920;" ><!--right arrow-bar, filled square -->
+<!ENTITY rarrc            "&#x02933;" ><!--right arrow-curved -->
+<!ENTITY rarrfs           "&#x0291E;" ><!--right arrow, filled square -->
+<!ENTITY rarrhk           "&#x021AA;" ><!--/hookrightarrow A: rt arrow-hooked -->
+<!ENTITY rarrlp           "&#x021AC;" ><!--/looparrowright A: rt arrow-looped -->
+<!ENTITY rarrpl           "&#x02945;" ><!--right arrow, plus -->
+<!ENTITY rarrsim          "&#x02974;" ><!--right arrow, similar -->
+<!ENTITY rarrtl           "&#x021A3;" ><!--/rightarrowtail A: rt arrow-tailed -->
+<!ENTITY Rarrtl           "&#x02916;" ><!--right two-headed arrow with tail -->
+<!ENTITY rarrw            "&#x021DD;" ><!--/rightsquigarrow A: rt arrow-wavy -->
+<!ENTITY ratail           "&#x021A3;" ><!--right arrow-tail -->
+<!ENTITY rAtail           "&#x0291C;" ><!--right double arrow-tail -->
+<!ENTITY rbarr            "&#x0290D;" ><!--/bkarow A: right broken arrow -->
+<!ENTITY rBarr            "&#x0290F;" ><!--/dbkarow A: right doubly broken arrow -->
+<!ENTITY RBarr            "&#x02910;" ><!--/drbkarow A: twoheaded right broken arrow -->
+<!ENTITY rdca             "&#x02937;" ><!--right down curved arrow -->
+<!ENTITY rdldhar          "&#x02969;" ><!--right harpoon-down over left harpoon-down -->
+<!ENTITY rdsh             "&#x021B3;" ><!--right down angled arrow -->
+<!ENTITY rfisht           "&#x0297D;" ><!--right fish tail -->
+<!ENTITY rHar             "&#x02964;" ><!--right harpoon-up over right harpoon-down -->
+<!ENTITY rhard            "&#x021C1;" ><!--/rightharpoondown A: rt harpoon-down -->
+<!ENTITY rharu            "&#x021C0;" ><!--/rightharpoonup A: rt harpoon-up -->
+<!ENTITY rharul           "&#x0296C;" ><!--right harpoon-up over long dash -->
+<!ENTITY rlarr            "&#x021C4;" ><!--/rightleftarrows A: r arr over l arr -->
+<!ENTITY rlhar            "&#x021CC;" ><!--/rightleftharpoons A: r harp over l -->
+<!ENTITY roarr            "&#x021FE;" ><!--right open arrow -->
+<!ENTITY rrarr            "&#x021C9;" ><!--/rightrightarrows A: two rt arrows -->
+<!ENTITY rsh              "&#x021B1;" ><!--/Rsh A: -->
+<!ENTITY ruluhar          "&#x02968;" ><!--right harpoon-up over left harpoon-up -->
+<!ENTITY searhk           "&#x02925;" ><!--/hksearow A: SE arrow-hooken -->
+<!ENTITY searr            "&#x02198;" ><!--/searrow A: SE pointing arrow -->
+<!ENTITY seArr            "&#x021D8;" ><!--SE pointing dbl arrow -->
+<!ENTITY seswar           "&#x02929;" ><!--/tosa A: SE & SW arrows -->
+<!ENTITY simrarr          "&#x02972;" ><!--similar, right arrow below -->
+<!ENTITY slarr            "&#x02190;&#x02063;" ><!--short left arrow -->
+<!ENTITY srarr            "&#x02192;&#x02063;" ><!--short right arrow -->
+<!ENTITY swarhk           "&#x02926;" ><!--/hkswarow A: SW arrow-hooked -->
+<!ENTITY swarr            "&#x02199;" ><!--/swarrow A: SW pointing arrow -->
+<!ENTITY swArr            "&#x021D9;" ><!--SW pointing dbl arrow -->
+<!ENTITY swnwar           "&#x0292A;" ><!--SW & NW arrows -->
+<!ENTITY uArr             "&#x021D1;" ><!--/Uparrow A: up dbl arrow -->
+<!ENTITY Uarr             "&#x0219F;" ><!--up two-headed arrow -->
+<!ENTITY Uarrocir         "&#x02949;" ><!--up two-headed arrow above circle -->
+<!ENTITY udarr            "&#x021C5;" ><!--up arrow, down arrow -->
+<!ENTITY udhar            "&#x0296E;" ><!--up harp, down harp -->
+<!ENTITY ufisht           "&#x0297E;" ><!--up fish tail -->
+<!ENTITY uHar             "&#x02963;" ><!--up harpoon-left, up harpoon-right -->
+<!ENTITY uharl            "&#x021BF;" ><!--/upharpoonleft A: up harpoon-left -->
+<!ENTITY uharr            "&#x021BE;" ><!--/upharpoonright /restriction A: up harp-r -->
+<!ENTITY uuarr            "&#x021C8;" ><!--/upuparrows A: two up arrows -->
+<!ENTITY varr             "&#x02195;" ><!--/updownarrow A: up&down arrow -->
+<!ENTITY vArr             "&#x021D5;" ><!--/Updownarrow A: up&down dbl arrow -->
+<!ENTITY xharr            "&#x02194;" ><!--/longleftrightarrow A: long l&r arr -->
+<!ENTITY xhArr            "&#x021D4;" ><!--/Longleftrightarrow A: long l&r dbl arr -->
+<!ENTITY xlarr            "&#x02190;" ><!--/longleftarrow A: long left arrow -->
+<!ENTITY xlArr            "&#x021D0;" ><!--/Longleftarrow A: long l dbl arrow -->
+<!ENTITY xmap             "&#x021A6;" ><!--/longmapsto A: -->
+<!ENTITY xrarr            "&#x02192;" ><!--/longrightarrow A: long right arrow -->
+<!ENTITY xrArr            "&#x021D2;" ><!--/Longrightarrow A: long rt dbl arr -->
+<!ENTITY zigrarr          "&#x021DD;" ><!--right zig-zag arrow -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsb.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsb.ent
new file mode 100644
index 00000000000..08e646c2bd0
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsb.ent
@@ -0,0 +1,146 @@
+
+<!--
+     File isoamsb.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY ac               "&#x0290F;" ><!--most positive -->
+<!ENTITY acE              "&#x029DB;" ><!--most positive, two lines below -->
+<!ENTITY amalg            "&#x02A3F;" ><!--/amalg B: amalgamation or coproduct -->
+<!ENTITY barvee           "&#x022BD;" ><!--bar, vee -->
+<!ENTITY barwed           "&#x022BC;" ><!--/barwedge B: logical and, bar above -->
+<!ENTITY Barwed           "&#x02306;" ><!--/doublebarwedge B: log and, dbl bar above -->
+<!ENTITY bsolb            "&#x029C5;" ><!--reverse solidus in square -->
+<!ENTITY Cap              "&#x022D2;" ><!--/Cap /doublecap B: dbl intersection -->
+<!ENTITY capand           "&#x02A44;" ><!--intersection, and -->
+<!ENTITY capbrcup         "&#x02A49;" ><!--intersection, bar, union -->
+<!ENTITY capcap           "&#x02A4B;" ><!--intersection, intersection, joined -->
+<!ENTITY capcup           "&#x02A47;" ><!--intersection above union -->
+<!ENTITY capdot           "&#x02A40;" ><!--intersection, with dot -->
+<!ENTITY caps             "&#x02229;&#x02063;" ><!--intersection, serifs -->
+<!ENTITY ccaps            "&#x02A4D;" ><!--closed intersection, serifs -->
+<!ENTITY ccups            "&#x02A4C;" ><!--closed union, serifs -->
+<!ENTITY ccupssm          "&#x02A50;" ><!--closed union, serifs, smash product -->
+<!ENTITY coprod           "&#x02210;" ><!--/coprod L: coproduct operator -->
+<!ENTITY Cup              "&#x022D3;" ><!--/Cup /doublecup B: dbl union -->
+<!ENTITY cupbrcap         "&#x02A48;" ><!--union, bar, intersection -->
+<!ENTITY cupcap           "&#x02A46;" ><!--union above intersection -->
+<!ENTITY cupcup           "&#x02A4A;" ><!--union, union, joined -->
+<!ENTITY cupdot           "&#x0228D;" ><!--union, with dot -->
+<!ENTITY cupor            "&#x02A45;" ><!--union, or -->
+<!ENTITY cups             "&#x0222A;&#x02063;" ><!--union, serifs -->
+<!ENTITY cuvee            "&#x022CE;" ><!--/curlyvee B: curly logical or -->
+<!ENTITY cuwed            "&#x022CF;" ><!--/curlywedge B: curly logical and -->
+<!ENTITY dagger           "&#x02020;" ><!--/dagger B: dagger relation -->
+<!ENTITY Dagger           "&#x02021;" ><!--/ddagger B: double dagger relation -->
+<!ENTITY diam             "&#x022C4;" ><!--/diamond B: open diamond -->
+<!ENTITY divonx           "&#x022C7;" ><!--/divideontimes B: division on times -->
+<!ENTITY eplus            "&#x02A71;" ><!--equal, plus -->
+<!ENTITY hercon           "&#x022B9;" ><!--hermitian conjugate matrix -->
+<!ENTITY intcal           "&#x022BA;" ><!--/intercal B: intercal -->
+<!ENTITY iprod            "&#x02A3C;" ><!--/intprod -->
+<!ENTITY loplus           "&#x02A2D;" ><!--plus sign in left half circle -->
+<!ENTITY lotimes          "&#x02A34;" ><!--multiply sign in left half circle  -->
+<!ENTITY lthree           "&#x022CB;" ><!--/leftthreetimes B: -->
+<!ENTITY ltimes           "&#x022C9;" ><!--/ltimes B: times sign, left closed -->
+<!ENTITY midast           "&#x0002A;" ><!--/ast B: asterisk -->
+<!ENTITY minusb           "&#x0229F;" ><!--/boxminus B: minus sign in box -->
+<!ENTITY minusd           "&#x02238;" ><!--/dotminus B: minus sign, dot above -->
+<!ENTITY minusdu          "&#x02A2A;" ><!--minus sign, dot below -->
+<!ENTITY ncap             "&#x02A43;" ><!--bar, intersection -->
+<!ENTITY ncup             "&#x02A42;" ><!--bar, union -->
+<!ENTITY oast             "&#x0229B;" ><!--/circledast B: asterisk in circle -->
+<!ENTITY ocir             "&#x0229A;" ><!--/circledcirc B: small circle in circle -->
+<!ENTITY odash            "&#x0229D;" ><!--/circleddash B: hyphen in circle -->
+<!ENTITY odiv             "&#x02A38;" ><!--divide in circle -->
+<!ENTITY odot             "&#x02299;" ><!--/odot B: middle dot in circle -->
+<!ENTITY odsold           "&#x029BC;" ><!--dot, solidus, dot in circle -->
+<!ENTITY ofcir            "&#x029BF;" ><!--filled circle in circle -->
+<!ENTITY ogt              "&#x029C1;" ><!--greater-than in circle -->
+<!ENTITY ohbar            "&#x029B5;" ><!--circle with horizontal bar -->
+<!ENTITY olcir            "&#x029BE;" ><!--large circle in circle -->
+<!ENTITY olt              "&#x029C0;" ><!--less-than in circle -->
+<!ENTITY omid             "&#x029B6;" ><!--vertical bar in circle -->
+<!ENTITY ominus           "&#x02296;" ><!--/ominus B: minus sign in circle -->
+<!ENTITY opar             "&#x029B7;" ><!--parallel in circle -->
+<!ENTITY operp            "&#x029B9;" ><!--perpendicular in circle -->
+<!ENTITY oplus            "&#x02295;" ><!--/oplus B: plus sign in circle -->
+<!ENTITY osol             "&#x02298;" ><!--/oslash B: solidus in circle -->
+<!ENTITY otimes           "&#x02297;" ><!--/otimes B: multiply sign in circle -->
+<!ENTITY Otimes           "&#x02A37;" ><!--multiply sign in double circle -->
+<!ENTITY otimesas         "&#x02A36;" ><!--multiply sign in circle, circumflex accent -->
+<!ENTITY ovbar            "&#x0233D;" ><!--circle with vertical bar -->
+<!ENTITY plusacir         "&#x02A23;" ><!--plus, circumflex accent above -->
+<!ENTITY plusb            "&#x0229E;" ><!--/boxplus B: plus sign in box -->
+<!ENTITY pluscir          "&#x02A22;" ><!--plus, small circle above -->
+<!ENTITY plusdo           "&#x02214;" ><!--/dotplus B: plus sign, dot above -->
+<!ENTITY plusdu           "&#x02A25;" ><!--plus sign, dot below -->
+<!ENTITY pluse            "&#x02A72;" ><!--plus, equals -->
+<!ENTITY plussim          "&#x02A26;" ><!--plus, similar below -->
+<!ENTITY plustwo          "&#x02A27;" ><!--plus, two; Nim-addition -->
+<!ENTITY prod             "&#x0220F;" ><!--/prod L: product operator -->
+<!ENTITY race             "&#x029DA;" ><!--reverse most positive, line below -->
+<!ENTITY roplus           "&#x02A2E;" ><!--plus sign in right half circle -->
+<!ENTITY rotimes          "&#x02A35;" ><!--multiply sign in right half circle -->
+<!ENTITY rthree           "&#x022CC;" ><!--/rightthreetimes B: -->
+<!ENTITY rtimes           "&#x022CA;" ><!--/rtimes B: times sign, right closed -->
+<!ENTITY sdot             "&#x022C5;" ><!--/cdot B: small middle dot -->
+<!ENTITY sdotb            "&#x022A1;" ><!--/dotsquare /boxdot B: small dot in box -->
+<!ENTITY setmn            "&#x02216;" ><!--/setminus B: reverse solidus -->
+<!ENTITY simplus          "&#x02A24;" ><!--plus, similar above -->
+<!ENTITY smashp           "&#x02A33;" ><!--smash product -->
+<!ENTITY solb             "&#x029C4;" ><!--solidus in square -->
+<!ENTITY sqcap            "&#x02293;" ><!--/sqcap B: square intersection -->
+<!ENTITY sqcaps           "&#x02293;&#x02063;" ><!--square intersection, serifs -->
+<!ENTITY sqcup            "&#x02294;" ><!--/sqcup B: square union -->
+<!ENTITY sqcups           "&#x02294;&#x02063;" ><!--square union, serifs -->
+<!ENTITY ssetmn           "&#x02216;" ><!--/smallsetminus B: sm reverse solidus -->
+<!ENTITY sstarf           "&#x022C6;" ><!--/star B: small star, filled -->
+<!ENTITY subdot           "&#x02ABD;" ><!--subset, with dot -->
+<!ENTITY sum              "&#x02211;" ><!--/sum L: summation operator -->
+<!ENTITY supdot           "&#x02ABE;" ><!--superset, with dot -->
+<!ENTITY timesb           "&#x022A0;" ><!--/boxtimes B: multiply sign in box -->
+<!ENTITY timesbar         "&#x02A31;" ><!--multiply sign, bar below -->
+<!ENTITY timesd           "&#x02A30;" ><!--times, dot -->
+<!ENTITY tridot           "&#x025EC;" ><!--dot in triangle -->
+<!ENTITY triminus         "&#x02A3A;" ><!--minus in triangle -->
+<!ENTITY triplus          "&#x02A39;" ><!--plus in triangle -->
+<!ENTITY trisb            "&#x029CD;" ><!--triangle, serifs at bottom -->
+<!ENTITY tritime          "&#x02A3B;" ><!--multiply in triangle -->
+<!ENTITY uplus            "&#x0228E;" ><!--/uplus B: plus sign in union -->
+<!ENTITY veebar           "&#x022BB;" ><!--/veebar B: logical or, bar below -->
+<!ENTITY wedbar           "&#x02A5F;" ><!--wedge, bar below -->
+<!ENTITY wreath           "&#x02240;" ><!--/wr B: wreath product -->
+<!ENTITY xcap             "&#x022C2;" ><!--/bigcap L: intersection operator -->
+<!ENTITY xcirc            "&#x025EF;" ><!--/bigcirc B: large circle -->
+<!ENTITY xcup             "&#x022C3;" ><!--/bigcup L: union operator -->
+<!ENTITY xdtri            "&#x025BD;" ><!--/bigtriangledown B: big dn tri, open -->
+<!ENTITY xodot            "&#x02299;" ><!--/bigodot L: circle dot operator -->
+<!ENTITY xoplus           "&#x02295;" ><!--/bigoplus L: circle plus operator -->
+<!ENTITY xotime           "&#x02297;" ><!--/bigotimes L: circle times operator -->
+<!ENTITY xsqcup           "&#x02294;" ><!--/bigsqcup L: square union operator -->
+<!ENTITY xuplus           "&#x0228E;" ><!--/biguplus L: -->
+<!ENTITY xutri            "&#x025B3;" ><!--/bigtriangleup B: big up tri, open -->
+<!ENTITY xvee             "&#x022C1;" ><!--/bigvee L: logical and operator -->
+<!ENTITY xwedge           "&#x022C0;" ><!--/bigwedge L: logical or operator -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsc.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsc.ent
new file mode 100644
index 00000000000..cce399cf9d4
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsc.ent
@@ -0,0 +1,49 @@
+
+<!--
+     File isoamsc.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY dlcorn           "&#x0231E;" ><!--/llcorner O: lower left corner -->
+<!ENTITY drcorn           "&#x0231F;" ><!--/lrcorner C: lower right corner -->
+<!ENTITY gtlPar           "&#x02995;" ><!--dbl left parenthesis, greater -->
+<!ENTITY langd            "&#x02991;" ><!--left angle, dot -->
+<!ENTITY lbrke            "&#x0298B;" ><!--left bracket, equal -->
+<!ENTITY lbrksld          "&#x0298F;" ><!--left bracket, solidus bottom corner -->
+<!ENTITY lbrkslu          "&#x0298D;" ><!--left bracket, solidus top corner -->
+<!ENTITY lceil            "&#x02308;" ><!--/lceil O: left ceiling -->
+<!ENTITY lfloor           "&#x0230A;" ><!--/lfloor O: left floor -->
+<!ENTITY lmoust           "&#x02998;" ><!--/lmoustache -->
+<!ENTITY lparlt           "&#x02993;" ><!--O: left parenthesis, lt -->
+<!ENTITY ltrPar           "&#x02996;" ><!--dbl right parenthesis, less -->
+<!ENTITY rangd            "&#x02992;" ><!--right angle, dot -->
+<!ENTITY rbrke            "&#x0298C;" ><!--right bracket, equal -->
+<!ENTITY rbrksld          "&#x0298E;" ><!--right bracket, solidus bottom corner -->
+<!ENTITY rbrkslu          "&#x02990;" ><!--right bracket, solidus top corner -->
+<!ENTITY rceil            "&#x02309;" ><!--/rceil C: right ceiling -->
+<!ENTITY rfloor           "&#x0230B;" ><!--/rfloor C: right floor -->
+<!ENTITY rmoust           "&#x02997;" ><!--/rmoustache -->
+<!ENTITY rpargt           "&#x02994;" ><!--C: right paren, gt -->
+<!ENTITY ulcorn           "&#x0231C;" ><!--/ulcorner O: upper left corner -->
+<!ENTITY urcorn           "&#x0231D;" ><!--/urcorner C: upper right corner -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsn.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsn.ent
new file mode 100644
index 00000000000..cddeba066e5
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsn.ent
@@ -0,0 +1,117 @@
+
+<!--
+     File isoamsn.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY gnap             "&#x02A8A;" ><!--/gnapprox N: greater, not approximate -->
+<!ENTITY gne              "&#x02269;" ><!--/gneq N: greater, not equals -->
+<!ENTITY gnE              "&#x02269;" ><!--/gneqq N: greater, not dbl equals -->
+<!ENTITY gnsim            "&#x022E7;" ><!--/gnsim N: greater, not similar -->
+<!ENTITY gvnE             "&#x02269;&#x00338;" ><!--/gvertneqq N: gt, vert, not dbl eq -->
+<!ENTITY lnap             "&#x02A89;" ><!--/lnapprox N: less, not approximate -->
+<!ENTITY lne              "&#x02268;" ><!--/lneq N: less, not equals -->
+<!ENTITY lnE              "&#x02268;" ><!--/lneqq N: less, not double equals -->
+<!ENTITY lnsim            "&#x022E6;" ><!--/lnsim N: less, not similar -->
+<!ENTITY lvnE             "&#x02268;&#x00338;" ><!--/lvertneqq N: less, vert, not dbl eq -->
+<!ENTITY nap              "&#x02249;" ><!--/napprox N: not approximate -->
+<!ENTITY napE             "&#x02A70;&#x00338;" ><!--not approximately equal or equal to -->
+<!ENTITY napid            "&#x0224B;&#x00338;" ><!--not approximately identical to -->
+<!ENTITY ncong            "&#x02247;" ><!--/ncong N: not congruent with -->
+<!ENTITY ncongdot         "&#x02A6D;&#x00338;" ><!--not congruent, dot -->
+<!ENTITY nequiv           "&#x02262;" ><!--/nequiv N: not identical with -->
+<!ENTITY nge              "&#x02271;&#x020E5;" ><!--/ngeq N: not greater-than-or-equal -->
+<!ENTITY ngE              "&#x02271;" ><!--/ngeqq N: not greater, dbl equals -->
+<!ENTITY nges             "&#x02271;" ><!--/ngeqslant N: not gt-or-eq, slanted -->
+<!ENTITY nGg              "&#x022D9;&#x00338;" ><!--not triple greater than -->
+<!ENTITY ngsim            "&#x02275;" ><!--not greater, similar -->
+<!ENTITY ngt              "&#x0226F;" ><!--/ngtr N: not greater-than -->
+<!ENTITY nGt              "&#x0226B;&#x00338;" ><!--not, vert, much greater than -->
+<!ENTITY nGtv             "&#x0226B;&#x00338;&#x02063;" ><!--not much greater than, variant -->
+<!ENTITY nle              "&#x02270;&#x020E5;" ><!--/nleq N: not less-than-or-equal -->
+<!ENTITY nlE              "&#x02270;" ><!--/nleqq N: not less, dbl equals -->
+<!ENTITY nles             "&#x02270;" ><!--/nleqslant N: not less-or-eq, slant -->
+<!ENTITY nLl              "&#x022D8;&#x00338;" ><!--not triple less than -->
+<!ENTITY nlsim            "&#x02274;" ><!--not less, similar -->
+<!ENTITY nlt              "&#x0226E;" ><!--/nless N: not less-than -->
+<!ENTITY nLt              "&#x0226A;&#x00338;" ><!--not, vert, much less than -->
+<!ENTITY nltri            "&#x022EA;" ><!--/ntriangleleft N: not left triangle -->
+<!ENTITY nltrie           "&#x022EC;" ><!--/ntrianglelefteq N: not l tri, eq -->
+<!ENTITY nLtv             "&#x0226A;&#x00338;&#x02063;" ><!--not much less than, variant -->
+<!ENTITY nmid             "&#x02224;" ><!--/nmid -->
+<!ENTITY npar             "&#x02226;" ><!--/nparallel N: not parallel -->
+<!ENTITY npr              "&#x02280;" ><!--/nprec N: not precedes -->
+<!ENTITY nprcue           "&#x022E0;" ><!--not curly precedes, eq -->
+<!ENTITY npre             "&#x02AAF;&#x00338;" ><!--/npreceq N: not precedes, equals -->
+<!ENTITY nrtri            "&#x022EB;" ><!--/ntriangleright N: not rt triangle -->
+<!ENTITY nrtrie           "&#x022ED;" ><!--/ntrianglerighteq N: not r tri, eq -->
+<!ENTITY nsc              "&#x02281;" ><!--/nsucc N: not succeeds -->
+<!ENTITY nsccue           "&#x022E1;" ><!--not succeeds, curly eq -->
+<!ENTITY nsce             "&#x02AB0;&#x00338;" ><!--/nsucceq N: not succeeds, equals -->
+<!ENTITY nsim             "&#x02241;" ><!--/nsim N: not similar -->
+<!ENTITY nsime            "&#x02244;" ><!--/nsimeq N: not similar, equals -->
+<!ENTITY nsmid            "&#x02224;&#x02063;" ><!--/nshortmid -->
+<!ENTITY nspar            "&#x02226;&#x02063;" ><!--/nshortparallel N: not short par -->
+<!ENTITY nsqsube          "&#x022E2;" ><!--not, square subset, equals -->
+<!ENTITY nsqsupe          "&#x022E3;" ><!--not, square superset, equals -->
+<!ENTITY nsub             "&#x02284;" ><!--not subset -->
+<!ENTITY nsube            "&#x02288;" ><!--/nsubseteq N: not subset, equals -->
+<!ENTITY nsubE            "&#x02288;" ><!--/nsubseteqq N: not subset, dbl eq -->
+<!ENTITY nsup             "&#x02285;" ><!--not superset -->
+<!ENTITY nsupe            "&#x02289;" ><!--/nsupseteq N: not superset, equals -->
+<!ENTITY nsupE            "&#x02289;" ><!--/nsupseteqq N: not superset, dbl eq -->
+<!ENTITY ntgl             "&#x02279;" ><!--not greater, less -->
+<!ENTITY ntlg             "&#x02278;" ><!--not less, greater -->
+<!ENTITY nvap             "&#x02249;&#x00338;" ><!--not, vert, approximate -->
+<!ENTITY nvdash           "&#x022AC;" ><!--/nvdash N: not vertical, dash -->
+<!ENTITY nvDash           "&#x022AD;" ><!--/nvDash N: not vertical, dbl dash -->
+<!ENTITY nVdash           "&#x022AE;" ><!--/nVdash N: not dbl vertical, dash -->
+<!ENTITY nVDash           "&#x022AF;" ><!--/nVDash N: not dbl vert, dbl dash -->
+<!ENTITY nvge             "&#x02271;" ><!--not, vert, greater-than-or-equal -->
+<!ENTITY nvgt             "&#x0226F;" ><!--not, vert, greater-than -->
+<!ENTITY nvle             "&#x02270;" ><!--not, vert, less-than-or-equal -->
+<!ENTITY nvlt             "&#x0226E;" ><!--not, vert, less-than -->
+<!ENTITY nvltrie          "&#x022EC;&#x00338;" ><!--not, vert, left triangle, equals -->
+<!ENTITY nvrtrie          "&#x022ED;&#x00338;" ><!--not, vert, right triangle, equals -->
+<!ENTITY nvsim            "&#x02241;&#x00338;" ><!--not, vert, similar -->
+<!ENTITY parsim           "&#x02AF3;" ><!--parallel, similar -->
+<!ENTITY prnap            "&#x022E8;" ><!--/precnapprox N: precedes, not approx -->
+<!ENTITY prnE             "&#x02AB5;" ><!--/precneqq N: precedes, not dbl eq -->
+<!ENTITY prnsim           "&#x022E8;" ><!--/precnsim N: precedes, not similar -->
+<!ENTITY rnmid            "&#x02AEE;" ><!--reverse /nmid -->
+<!ENTITY scnap            "&#x022E9;" ><!--/succnapprox N: succeeds, not approx -->
+<!ENTITY scnE             "&#x02AB6;" ><!--/succneqq N: succeeds, not dbl eq -->
+<!ENTITY scnsim           "&#x022E9;" ><!--/succnsim N: succeeds, not similar -->
+<!ENTITY simne            "&#x02246;" ><!--similar, not equals -->
+<!ENTITY solbar           "&#x0233F;" ><!--solidus, bar through -->
+<!ENTITY subne            "&#x0228A;" ><!--/subsetneq N: subset, not equals -->
+<!ENTITY subnE            "&#x0228A;" ><!--/subsetneqq N: subset, not dbl eq -->
+<!ENTITY supne            "&#x0228B;" ><!--/supsetneq N: superset, not equals -->
+<!ENTITY supnE            "&#x0228B;" ><!--/supsetneqq N: superset, not dbl eq -->
+<!ENTITY vnsub            "&#x02284;" ><!--/nsubset N: not subset, var -->
+<!ENTITY vnsup            "&#x02285;" ><!--/nsupset N: not superset, var -->
+<!ENTITY vsubne           "&#x0228A;&#x02063;" ><!--/varsubsetneq N: subset, not eq, var -->
+<!ENTITY vsubnE           "&#x0228A;&#x02063;" ><!--/varsubsetneqq N: subset not dbl eq, var -->
+<!ENTITY vsupne           "&#x0228B;&#x02063;" ><!--/varsupsetneq N: superset, not eq, var -->
+<!ENTITY vsupnE           "&#x0228B;&#x02063;" ><!--/varsupsetneqq N: super not dbl eq, var -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamso.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamso.ent
new file mode 100644
index 00000000000..8ac4bdb619f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamso.ent
@@ -0,0 +1,77 @@
+
+<!--
+     File isoamso.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY ang              "&#x02220;" ><!--/angle - angle -->
+<!ENTITY ange             "&#x029A4;" ><!--angle, equal -->
+<!ENTITY angmsd           "&#x02221;" ><!--/measuredangle - angle-measured -->
+<!ENTITY angmsdaa         "&#x029A8;" ><!--angle-measured, arrow, up, right -->
+<!ENTITY angmsdab         "&#x029A9;" ><!--angle-measured, arrow, up, left -->
+<!ENTITY angmsdac         "&#x029AA;" ><!--angle-measured, arrow, down, right -->
+<!ENTITY angmsdad         "&#x029AB;" ><!--angle-measured, arrow, down, left -->
+<!ENTITY angmsdae         "&#x029AC;" ><!--angle-measured, arrow, right, up -->
+<!ENTITY angmsdaf         "&#x029AD;" ><!--angle-measured, arrow, left, up -->
+<!ENTITY angmsdag         "&#x029AE;" ><!--angle-measured, arrow, right, down -->
+<!ENTITY angmsdah         "&#x029AF;" ><!--angle-measured, arrow, left, down -->
+<!ENTITY angrtvb          "&#x0299D;&#x02063;" ><!--right angle-measured -->
+<!ENTITY angrtvbd         "&#x0299D;" ><!--right angle-measured, dot -->
+<!ENTITY bbrk             "&#x023B5;" ><!--bottom square bracket -->
+<!ENTITY bemptyv          "&#x029B0;" ><!--reversed circle, slash -->
+<!ENTITY beth             "&#x02136;" ><!--/beth - beth, Hebrew -->
+<!ENTITY boxbox           "&#x029C9;" ><!--two joined squares -->
+<!ENTITY bprime           "&#x02035;" ><!--/backprime - reverse prime -->
+<!ENTITY bsemi            "&#x0204F;" ><!--reverse semi-colon -->
+<!ENTITY cemptyv          "&#x029B2;" ><!--circle, slash, small circle above -->
+<!ENTITY cirE             "&#x029C3;" ><!--circle, two horizontal stroked to the right -->
+<!ENTITY cirscir          "&#x029C2;" ><!--circle, small circle to the right -->
+<!ENTITY comp             "&#x02201;" ><!--/complement - complement sign -->
+<!ENTITY daleth           "&#x02138;" ><!--/daleth - daleth, Hebrew -->
+<!ENTITY demptyv          "&#x029B1;" ><!--circle, slash, bar above -->
+<!ENTITY ell              "&#x02113;" ><!--/ell - cursive small l -->
+<!ENTITY empty            "&#x02205;&#x02063;" ><!--/emptyset - zero, slash -->
+<!ENTITY emptyv           "&#x02205;" ><!--/varnothing - circle, slash -->
+<!ENTITY gimel            "&#x02137;" ><!--/gimel - gimel, Hebrew -->
+<!ENTITY iiota            "&#x02129;" ><!--inverted iota -->
+<!ENTITY image            "&#x02111;" ><!--/Im - imaginary   -->
+<!ENTITY imath            "&#x00131;" ><!--/imath - small i, no dot -->
+<!ENTITY jmath            "&#x0006A;&#x02063;" ><!--/jmath - small j, no dot -->
+<!ENTITY laemptyv         "&#x029B4;" ><!--circle, slash, left arrow above -->
+<!ENTITY lltri            "&#x025FA;" ><!--lower left triangle -->
+<!ENTITY lrtri            "&#x022BF;" ><!--lower right triangle -->
+<!ENTITY mho              "&#x02127;" ><!--/mho - conductance -->
+<!ENTITY nang             "&#x02220;&#x00338;" ><!--not, vert, angle -->
+<!ENTITY nexist           "&#x02204;" ><!--/nexists - negated exists -->
+<!ENTITY oS               "&#x024C8;" ><!--/circledS - capital S in circle -->
+<!ENTITY plank            "&#x0210F;" ><!--/hbar - Planck's over 2pi -->
+<!ENTITY plankv           "&#x0210F;" ><!--/hslash - variant Planck's over 2pi -->
+<!ENTITY raemptyv         "&#x029B3;" ><!--circle, slash, right arrow above -->
+<!ENTITY range            "&#x029A5;" ><!--reverse angle, equal -->
+<!ENTITY real             "&#x0211C;" ><!--/Re - real -->
+<!ENTITY tbrk             "&#x023B4;" ><!--top square bracket -->
+<!ENTITY ultri            "&#x025F8;" ><!--upper left triangle -->
+<!ENTITY urtri            "&#x025F9;" ><!--upper right triangle -->
+<!ENTITY vzigzag          "&#x0299A;" ><!--vertical zig-zag line -->
+<!ENTITY weierp           "&#x02118;" ><!--/wp - Weierstrass p -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsr.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsr.ent
new file mode 100644
index 00000000000..7fec5825557
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isoamsr.ent
@@ -0,0 +1,205 @@
+
+<!--
+     File isoamsr.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY ape              "&#x0224A;" ><!--/approxeq R: approximate, equals -->
+<!ENTITY apE              "&#x0224A;" ><!--approximately equal or equal to -->
+<!ENTITY apid             "&#x0224B;" ><!--approximately identical to -->
+<!ENTITY asymp            "&#x0224D;" ><!--/asymp R: asymptotically equal to -->
+<!ENTITY Barv             "&#x02AE7;" ><!--vert, dbl bar (over) -->
+<!ENTITY bcong            "&#x0224C;" ><!--/backcong R: reverse congruent -->
+<!ENTITY bepsi            "&#x0213C;" ><!--/backepsilon R: such that -->
+<!ENTITY bowtie           "&#x022C8;" ><!--/bowtie R: -->
+<!ENTITY bsim             "&#x0223D;" ><!--/backsim R: reverse similar -->
+<!ENTITY bsime            "&#x022CD;" ><!--/backsimeq R: reverse similar, eq -->
+<!ENTITY bsolhsub         "&#x0005C;&#x02282;" ><!--reverse solidus, subset -->
+<!ENTITY bump             "&#x0224E;" ><!--/Bumpeq R: bumpy equals -->
+<!ENTITY bumpe            "&#x0224F;" ><!--/bumpeq R: bumpy equals, equals -->
+<!ENTITY bumpE            "&#x02AAE;" ><!--bump, equals -->
+<!ENTITY cire             "&#x02257;" ><!--/circeq R: circle, equals -->
+<!ENTITY Colon            "&#x02237;" ><!--/Colon, two colons -->
+<!ENTITY colone           "&#x02254;" ><!--/coloneq R: colon, equals -->
+<!ENTITY Colone           "&#x02A74;" ><!--double colon, equals -->
+<!ENTITY congdot          "&#x02A6D;" ><!--congruent, dot -->
+<!ENTITY csub             "&#x02ACF;" ><!--subset, closed -->
+<!ENTITY csube            "&#x02AD1;" ><!--subset, closed, equals -->
+<!ENTITY csup             "&#x02AD0;" ><!--superset, closed -->
+<!ENTITY csupe            "&#x02AD2;" ><!--superset, closed, equals -->
+<!ENTITY cuepr            "&#x022DE;" ><!--/curlyeqprec R: curly eq, precedes -->
+<!ENTITY cuesc            "&#x022DF;" ><!--/curlyeqsucc R: curly eq, succeeds -->
+<!ENTITY dashv            "&#x022A3;" ><!--/dashv R: dash, vertical -->
+<!ENTITY Dashv            "&#x02AE4;" ><!--dbl dash, vertical -->
+<!ENTITY easter           "&#x0225B;" ><!--equal, asterisk above -->
+<!ENTITY ecir             "&#x02256;" ><!--/eqcirc R: circle on equals sign -->
+<!ENTITY ecolon           "&#x02255;" ><!--/eqcolon R: equals, colon -->
+<!ENTITY eDDot            "&#x02A77;" ><!--/ddotseq R: equal with four dots -->
+<!ENTITY eDot             "&#x02251;" ><!--/doteqdot /Doteq R: eq, even dots -->
+<!ENTITY efDot            "&#x02252;" ><!--/fallingdotseq R: eq, falling dots -->
+<!ENTITY eg               "&#x02A9A;" ><!--equal-or-greater -->
+<!ENTITY egs              "&#x022DD;" ><!--/eqslantgtr R: equal-or-gtr, slanted -->
+<!ENTITY egsdot           "&#x02A98;" ><!--equal-or-greater, slanted, dot inside -->
+<!ENTITY el               "&#x02A99;" ><!--equal-or-less -->
+<!ENTITY els              "&#x022DC;" ><!--/eqslantless R: eq-or-less, slanted -->
+<!ENTITY elsdot           "&#x02A97;" ><!--equal-or-less, slanted, dot inside -->
+<!ENTITY equest           "&#x0225F;" ><!--/questeq R: equal with questionmark -->
+<!ENTITY equivDD          "&#x02A78;" ><!--equivalent, four dots above -->
+<!ENTITY erDot            "&#x02253;" ><!--/risingdotseq R: eq, rising dots -->
+<!ENTITY esdot            "&#x02250;" ><!--/doteq R: equals, single dot above -->
+<!ENTITY esim             "&#x02242;" ><!--/esim R: equals, similar -->
+<!ENTITY Esim             "&#x02A73;" ><!--equal, similar -->
+<!ENTITY fork             "&#x022D4;" ><!--/pitchfork R: pitchfork -->
+<!ENTITY forkv            "&#x02AD9;" ><!--fork, variant -->
+<!ENTITY frown            "&#x02322;" ><!--/frown R: down curve -->
+<!ENTITY gap              "&#x02273;" ><!--/gtrapprox R: greater, approximate -->
+<!ENTITY gE               "&#x02267;" ><!--/geqq R: greater, double equals -->
+<!ENTITY gel              "&#x022DB;" ><!--/gtreqless R: greater, equals, less -->
+<!ENTITY gEl              "&#x022DB;" ><!--/gtreqqless R: gt, dbl equals, less -->
+<!ENTITY ges              "&#x02A7E;" ><!--/geqslant R: gt-or-equal, slanted -->
+<!ENTITY gescc            "&#x02AA9;" ><!--greater than, closed by curve, equal, slanted -->
+<!ENTITY gesdot           "&#x02A80;" ><!--greater-than-or-equal, slanted, dot inside -->
+<!ENTITY gesdoto          "&#x02A82;" ><!--greater-than-or-equal, slanted, dot above -->
+<!ENTITY gesdotol         "&#x02A84;" ><!--greater-than-or-equal, slanted, dot above left -->
+<!ENTITY gesl             "&#x022DB;&#x02063;" ><!--greater, equal, slanted, less -->
+<!ENTITY gesles           "&#x02A94;" ><!--greater, equal, slanted, less, equal, slanted -->
+<!ENTITY Gg               "&#x022D9;" ><!--/ggg /Gg /gggtr R: triple gtr-than -->
+<!ENTITY gl               "&#x02277;" ><!--/gtrless R: greater, less -->
+<!ENTITY gla              "&#x02AA5;" ><!--greater, less, apart -->
+<!ENTITY glE              "&#x02A92;" ><!--greater, less, equal -->
+<!ENTITY glj              "&#x02AA4;" ><!--greater, less, overlapping -->
+<!ENTITY gsim             "&#x02273;" ><!--/gtrsim R: greater, similar -->
+<!ENTITY gsime            "&#x02A8E;" ><!--greater, similar, equal -->
+<!ENTITY gsiml            "&#x02A90;" ><!--greater, similar, less -->
+<!ENTITY Gt               "&#x0226B;" ><!--/gg R: dbl greater-than sign -->
+<!ENTITY gtcc             "&#x02AA7;" ><!--greater than, closed by curve -->
+<!ENTITY gtcir            "&#x02A7A;" ><!--greater than, circle inside -->
+<!ENTITY gtdot            "&#x022D7;" ><!--/gtrdot R: greater than, with dot -->
+<!ENTITY gtquest          "&#x02A7C;" ><!--greater than, questionmark above -->
+<!ENTITY gtrarr           "&#x02978;" ><!--greater than, right arrow -->
+<!ENTITY homtht           "&#x0223B;" ><!--homothetic -->
+<!ENTITY lap              "&#x02272;" ><!--/lessapprox R: less, approximate -->
+<!ENTITY lat              "&#x02AAB;" ><!--larger than -->
+<!ENTITY late             "&#x02AAD;" ><!--larger than or equal -->
+<!ENTITY lates            "&#x02AAD;&#x02063;" ><!--larger than or equal, slanted -->
+<!ENTITY lE               "&#x02266;" ><!--/leqq R: less, double equals -->
+<!ENTITY leg              "&#x022DA;" ><!--/lesseqgtr R: less, eq, greater -->
+<!ENTITY lEg              "&#x022DA;" ><!--/lesseqqgtr R: less, dbl eq, greater -->
+<!ENTITY les              "&#x02A7D;" ><!--/leqslant R: less-than-or-eq, slant -->
+<!ENTITY lescc            "&#x02AA8;" ><!--less than, closed by curve, equal, slanted -->
+<!ENTITY lesdot           "&#x02A7F;" ><!--less-than-or-equal, slanted, dot inside -->
+<!ENTITY lesdoto          "&#x02A81;" ><!--less-than-or-equal, slanted, dot above -->
+<!ENTITY lesdotor         "&#x02A83;" ><!--less-than-or-equal, slanted, dot above right -->
+<!ENTITY lesg             "&#x022DA;&#x02063;" ><!--less, equal, slanted, greater -->
+<!ENTITY lesges           "&#x02A93;" ><!--less, equal, slanted, greater, equal, slanted -->
+<!ENTITY lg               "&#x02276;" ><!--/lessgtr R: less, greater -->
+<!ENTITY lgE              "&#x02A91;" ><!--less, greater, equal -->
+<!ENTITY Ll               "&#x022D8;" ><!--/Ll /lll /llless R: triple less-than -->
+<!ENTITY lsim             "&#x02272;" ><!--/lesssim R: less, similar -->
+<!ENTITY lsime            "&#x02A8D;" ><!--less, similar, equal -->
+<!ENTITY lsimg            "&#x02A8F;" ><!--less, similar, greater -->
+<!ENTITY Lt               "&#x0226A;" ><!--/ll R: double less-than sign -->
+<!ENTITY ltcc             "&#x02AA6;" ><!--less than, closed by curve -->
+<!ENTITY ltcir            "&#x02A79;" ><!--less than, circle inside -->
+<!ENTITY ltdot            "&#x022D6;" ><!--/lessdot R: less than, with dot -->
+<!ENTITY ltlarr           "&#x02976;" ><!--less than, left arrow -->
+<!ENTITY ltquest          "&#x02A7B;" ><!--less than, questionmark above -->
+<!ENTITY ltrie            "&#x022B4;" ><!--/trianglelefteq R: left triangle, eq -->
+<!ENTITY mcomma           "&#x02A29;" ><!--minus, comma above -->
+<!ENTITY mDDot            "&#x0223A;" ><!--minus with four dots, geometric properties -->
+<!ENTITY mid              "&#x02223;" ><!--/mid R: -->
+<!ENTITY mlcp             "&#x02ADB;" ><!--/mlcp -->
+<!ENTITY models           "&#x022A7;" ><!--/models R: -->
+<!ENTITY mstpos           "&#x0223E;" ><!--most positive -->
+<!ENTITY pr               "&#x0227A;" ><!--/prec R: precedes -->
+<!ENTITY Pr               "&#x02ABB;" ><!--dbl precedes -->
+<!ENTITY prap             "&#x0227E;" ><!--/precapprox R: precedes, approximate -->
+<!ENTITY prcue            "&#x0227C;" ><!--/preccurlyeq R: precedes, curly eq -->
+<!ENTITY pre              "&#x02AAF;" ><!--/preceq R: precedes, equals -->
+<!ENTITY prE              "&#x02AAF;" ><!--precedes, dbl equals -->
+<!ENTITY prsim            "&#x0227E;" ><!--/precsim R: precedes, similar -->
+<!ENTITY prurel           "&#x022B0;" ><!--element precedes under relation -->
+<!ENTITY ratio            "&#x02236;" ><!--/ratio -->
+<!ENTITY rtrie            "&#x022B5;" ><!--/trianglerighteq R: right tri, eq -->
+<!ENTITY rtriltri         "&#x029CE;" ><!--right triangle above left triangle -->
+<!ENTITY sc               "&#x0227B;" ><!--/succ R: succeeds -->
+<!ENTITY Sc               "&#x02ABC;" ><!--dbl succeeds -->
+<!ENTITY scap             "&#x0227F;" ><!--/succapprox R: succeeds, approximate -->
+<!ENTITY sccue            "&#x0227D;" ><!--/succcurlyeq R: succeeds, curly eq -->
+<!ENTITY sce              "&#x0227D;" ><!--/succeq R: succeeds, equals -->
+<!ENTITY scE              "&#x0227E;" ><!--succeeds, dbl equals -->
+<!ENTITY scsim            "&#x0227F;" ><!--/succsim R: succeeds, similar -->
+<!ENTITY sdote            "&#x02A66;" ><!--equal, dot below -->
+<!ENTITY simg             "&#x02A9E;" ><!--similar, greater -->
+<!ENTITY simgE            "&#x02AA0;" ><!--similar, greater, equal -->
+<!ENTITY siml             "&#x02A9D;" ><!--similar, less -->
+<!ENTITY simlE            "&#x02A9F;" ><!--similar, less, equal -->
+<!ENTITY smid             "&#x02223;&#x02063;" ><!--/shortmid R: -->
+<!ENTITY smile            "&#x02323;" ><!--/smile R: up curve -->
+<!ENTITY smt              "&#x02AAA;" ><!--smaller than -->
+<!ENTITY smte             "&#x02AAC;" ><!--smaller than or equal -->
+<!ENTITY smtes            "&#x02AAC;&#x02063;" ><!--smaller than or equal, slanted -->
+<!ENTITY spar             "&#x02225;&#x02063;" ><!--/shortparallel R: short parallel -->
+<!ENTITY sqsub            "&#x0228F;" ><!--/sqsubset R: square subset -->
+<!ENTITY sqsube           "&#x02291;" ><!--/sqsubseteq R: square subset, equals -->
+<!ENTITY sqsup            "&#x02290;" ><!--/sqsupset R: square superset -->
+<!ENTITY sqsupe           "&#x02292;" ><!--/sqsupseteq R: square superset, eq -->
+<!ENTITY Sub              "&#x022D0;" ><!--/Subset R: double subset -->
+<!ENTITY subE             "&#x02286;" ><!--/subseteqq R: subset, dbl equals -->
+<!ENTITY subedot          "&#x02AC3;" ><!--subset, equals, dot -->
+<!ENTITY submult          "&#x02AC1;" ><!--subset, multiply -->
+<!ENTITY subplus          "&#x02ABF;" ><!--subset, plus -->
+<!ENTITY subrarr          "&#x02979;" ><!--subset, right arrow -->
+<!ENTITY subsim           "&#x02AC7;" ><!--subset, similar -->
+<!ENTITY subsub           "&#x02AD5;" ><!--subset above subset -->
+<!ENTITY subsup           "&#x02AD3;" ><!--subset above superset -->
+<!ENTITY Sup              "&#x022D1;" ><!--/Supset R: dbl superset -->
+<!ENTITY supdsub          "&#x02AD8;" ><!--superset, subset, dash joining them -->
+<!ENTITY supE             "&#x02287;" ><!--/supseteqq R: superset, dbl equals -->
+<!ENTITY supedot          "&#x02AC4;" ><!--superset, equals, dot -->
+<!ENTITY suphsol          "&#x02283;&#x0002F;" ><!--superset, solidus -->
+<!ENTITY suphsub          "&#x02AD7;" ><!--superset, subset -->
+<!ENTITY suplarr          "&#x0297B;" ><!--superset, left arrow -->
+<!ENTITY supmult          "&#x02AC2;" ><!--superset, multiply -->
+<!ENTITY supplus          "&#x02AC0;" ><!--superset, plus -->
+<!ENTITY supsim           "&#x02AC8;" ><!--superset, similar -->
+<!ENTITY supsub           "&#x02AD4;" ><!--superset above subset -->
+<!ENTITY supsup           "&#x02AD6;" ><!--superset above superset -->
+<!ENTITY thkap            "&#x02248;&#x02063;" ><!--/thickapprox R: thick approximate -->
+<!ENTITY thksim           "&#x0223C;" ><!--/thicksim R: thick similar -->
+<!ENTITY topfork          "&#x02ADA;" ><!--fork with top -->
+<!ENTITY trie             "&#x0225C;" ><!--/triangleq R: triangle, equals -->
+<!ENTITY twixt            "&#x0226C;" ><!--/between R: between -->
+<!ENTITY vBar             "&#x02AE8;" ><!--vert, dbl bar (under) -->
+<!ENTITY Vbar             "&#x02AEB;" ><!--dbl vert, bar (under) -->
+<!ENTITY vBarv            "&#x02AE9;" ><!--dbl bar, vert over and under -->
+<!ENTITY vdash            "&#x022A2;" ><!--/vdash R: vertical, dash -->
+<!ENTITY vDash            "&#x022A8;" ><!--/vDash R: vertical, dbl dash -->
+<!ENTITY Vdash            "&#x022A9;" ><!--/Vdash R: dbl vertical, dash -->
+<!ENTITY VDash            "&#x022AB;" ><!--dbl vert, dbl dash -->
+<!ENTITY Vdashl           "&#x02AE6;" ><!--vertical, dash (long) -->
+<!ENTITY vltri            "&#x022B2;" ><!--/vartriangleleft R: l tri, open, var -->
+<!ENTITY vprop            "&#x0221D;" ><!--/varpropto R: proportional, variant -->
+<!ENTITY vrtri            "&#x022B3;" ><!--/vartriangleright R: r tri, open, var -->
+<!ENTITY Vvdash           "&#x022AA;" ><!--/Vvdash R: triple vertical, dash -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isobox.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isobox.ent
new file mode 100644
index 00000000000..630edc5597b
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isobox.ent
@@ -0,0 +1,67 @@
+
+<!--
+     File isobox.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY boxdl            "&#x02510;" ><!--lower left quadrant -->
+<!ENTITY boxdL            "&#x02555;" ><!--lower left quadrant -->
+<!ENTITY boxDl            "&#x02556;" ><!--lower left quadrant -->
+<!ENTITY boxDL            "&#x02557;" ><!--lower left quadrant -->
+<!ENTITY boxdr            "&#x0250C;" ><!--lower right quadrant -->
+<!ENTITY boxdR            "&#x02552;" ><!--lower right quadrant -->
+<!ENTITY boxDr            "&#x02553;" ><!--lower right quadrant -->
+<!ENTITY boxDR            "&#x02554;" ><!--lower right quadrant -->
+<!ENTITY boxh             "&#x02500;" ><!--horizontal line  -->
+<!ENTITY boxH             "&#x02550;" ><!--horizontal line -->
+<!ENTITY boxhd            "&#x0252C;" ><!--lower left and right quadrants -->
+<!ENTITY boxhD            "&#x02565;" ><!--lower left and right quadrants -->
+<!ENTITY boxHd            "&#x02564;" ><!--lower left and right quadrants -->
+<!ENTITY boxHD            "&#x02566;" ><!--lower left and right quadrants -->
+<!ENTITY boxhu            "&#x02534;" ><!--upper left and right quadrants -->
+<!ENTITY boxhU            "&#x02568;" ><!--upper left and right quadrants -->
+<!ENTITY boxHu            "&#x02567;" ><!--upper left and right quadrants -->
+<!ENTITY boxHU            "&#x02569;" ><!--upper left and right quadrants -->
+<!ENTITY boxul            "&#x02518;" ><!--upper left quadrant -->
+<!ENTITY boxuL            "&#x0255B;" ><!--upper left quadrant -->
+<!ENTITY boxUl            "&#x0255C;" ><!--upper left quadrant -->
+<!ENTITY boxUL            "&#x0255D;" ><!--upper left quadrant -->
+<!ENTITY boxur            "&#x02514;" ><!--upper right quadrant -->
+<!ENTITY boxuR            "&#x02558;" ><!--upper right quadrant -->
+<!ENTITY boxUr            "&#x02559;" ><!--upper right quadrant -->
+<!ENTITY boxUR            "&#x0255A;" ><!--upper right quadrant -->
+<!ENTITY boxv             "&#x02502;" ><!--vertical line -->
+<!ENTITY boxV             "&#x02551;" ><!--vertical line -->
+<!ENTITY boxvh            "&#x0253C;" ><!--all four quadrants -->
+<!ENTITY boxvH            "&#x0256A;" ><!--all four quadrants -->
+<!ENTITY boxVh            "&#x0256B;" ><!--all four quadrants -->
+<!ENTITY boxVH            "&#x0256C;" ><!--all four quadrants -->
+<!ENTITY boxvl            "&#x02524;" ><!--upper and lower left quadrants -->
+<!ENTITY boxvL            "&#x02561;" ><!--upper and lower left quadrants -->
+<!ENTITY boxVl            "&#x02562;" ><!--upper and lower left quadrants -->
+<!ENTITY boxVL            "&#x02563;" ><!--upper and lower left quadrants -->
+<!ENTITY boxvr            "&#x0251C;" ><!--upper and lower right quadrants -->
+<!ENTITY boxvR            "&#x0255E;" ><!--upper and lower right quadrants -->
+<!ENTITY boxVr            "&#x0255F;" ><!--upper and lower right quadrants -->
+<!ENTITY boxVR            "&#x02560;" ><!--upper and lower right quadrants -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isocyr1.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isocyr1.ent
new file mode 100644
index 00000000000..4bcc9e416e4
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isocyr1.ent
@@ -0,0 +1,94 @@
+
+<!--
+     File isocyr1.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY acy              "&#x00430;" ><!--=small a, Cyrillic -->
+<!ENTITY Acy              "&#x00410;" ><!--=capital A, Cyrillic -->
+<!ENTITY bcy              "&#x00431;" ><!--=small be, Cyrillic -->
+<!ENTITY Bcy              "&#x00411;" ><!--=capital BE, Cyrillic -->
+<!ENTITY chcy             "&#x00447;" ><!--=small che, Cyrillic -->
+<!ENTITY CHcy             "&#x00427;" ><!--=capital CHE, Cyrillic -->
+<!ENTITY dcy              "&#x00434;" ><!--=small de, Cyrillic -->
+<!ENTITY Dcy              "&#x00414;" ><!--=capital DE, Cyrillic -->
+<!ENTITY ecy              "&#x0044D;" ><!--=small e, Cyrillic -->
+<!ENTITY Ecy              "&#x0042D;" ><!--=capital E, Cyrillic -->
+<!ENTITY fcy              "&#x00444;" ><!--=small ef, Cyrillic -->
+<!ENTITY Fcy              "&#x00424;" ><!--=capital EF, Cyrillic -->
+<!ENTITY gcy              "&#x00433;" ><!--=small ghe, Cyrillic -->
+<!ENTITY Gcy              "&#x00413;" ><!--=capital GHE, Cyrillic -->
+<!ENTITY hardcy           "&#x0044A;" ><!--=small hard sign, Cyrillic -->
+<!ENTITY HARDcy           "&#x0042A;" ><!--=capital HARD sign, Cyrillic -->
+<!ENTITY icy              "&#x00438;" ><!--=small i, Cyrillic -->
+<!ENTITY Icy              "&#x00418;" ><!--=capital I, Cyrillic -->
+<!ENTITY iecy             "&#x00435;" ><!--=small ie, Cyrillic -->
+<!ENTITY IEcy             "&#x00415;" ><!--=capital IE, Cyrillic -->
+<!ENTITY iocy             "&#x00451;" ><!--=small io, Russian -->
+<!ENTITY IOcy             "&#x00401;" ><!--=capital IO, Russian -->
+<!ENTITY jcy              "&#x00439;" ><!--=small short i, Cyrillic -->
+<!ENTITY Jcy              "&#x00419;" ><!--=capital short I, Cyrillic -->
+<!ENTITY kcy              "&#x0043A;" ><!--=small ka, Cyrillic -->
+<!ENTITY Kcy              "&#x0041A;" ><!--=capital KA, Cyrillic -->
+<!ENTITY khcy             "&#x00445;" ><!--=small ha, Cyrillic -->
+<!ENTITY KHcy             "&#x00425;" ><!--=capital HA, Cyrillic -->
+<!ENTITY lcy              "&#x0043B;" ><!--=small el, Cyrillic -->
+<!ENTITY Lcy              "&#x0041B;" ><!--=capital EL, Cyrillic -->
+<!ENTITY mcy              "&#x0043C;" ><!--=small em, Cyrillic -->
+<!ENTITY Mcy              "&#x0041C;" ><!--=capital EM, Cyrillic -->
+<!ENTITY ncy              "&#x0043D;" ><!--=small en, Cyrillic -->
+<!ENTITY Ncy              "&#x0041D;" ><!--=capital EN, Cyrillic -->
+<!ENTITY numero           "&#x02116;" ><!--=numero sign -->
+<!ENTITY ocy              "&#x0043E;" ><!--=small o, Cyrillic -->
+<!ENTITY Ocy              "&#x0041E;" ><!--=capital O, Cyrillic -->
+<!ENTITY pcy              "&#x0043F;" ><!--=small pe, Cyrillic -->
+<!ENTITY Pcy              "&#x0041F;" ><!--=capital PE, Cyrillic -->
+<!ENTITY rcy              "&#x00440;" ><!--=small er, Cyrillic -->
+<!ENTITY Rcy              "&#x00420;" ><!--=capital ER, Cyrillic -->
+<!ENTITY scy              "&#x00441;" ><!--=small es, Cyrillic -->
+<!ENTITY Scy              "&#x00421;" ><!--=capital ES, Cyrillic -->
+<!ENTITY shchcy           "&#x00449;" ><!--=small shcha, Cyrillic -->
+<!ENTITY SHCHcy           "&#x00429;" ><!--=capital SHCHA, Cyrillic -->
+<!ENTITY shcy             "&#x00448;" ><!--=small sha, Cyrillic -->
+<!ENTITY SHcy             "&#x00428;" ><!--=capital SHA, Cyrillic -->
+<!ENTITY softcy           "&#x0044C;" ><!--=small soft sign, Cyrillic -->
+<!ENTITY SOFTcy           "&#x0042C;" ><!--=capital SOFT sign, Cyrillic -->
+<!ENTITY tcy              "&#x00442;" ><!--=small te, Cyrillic -->
+<!ENTITY Tcy              "&#x00422;" ><!--=capital TE, Cyrillic -->
+<!ENTITY tscy             "&#x00446;" ><!--=small tse, Cyrillic -->
+<!ENTITY TScy             "&#x00426;" ><!--=capital TSE, Cyrillic -->
+<!ENTITY ucy              "&#x00443;" ><!--=small u, Cyrillic -->
+<!ENTITY Ucy              "&#x00423;" ><!--=capital U, Cyrillic -->
+<!ENTITY vcy              "&#x00432;" ><!--=small ve, Cyrillic -->
+<!ENTITY Vcy              "&#x00412;" ><!--=capital VE, Cyrillic -->
+<!ENTITY yacy             "&#x0044F;" ><!--=small ya, Cyrillic -->
+<!ENTITY YAcy             "&#x0042F;" ><!--=capital YA, Cyrillic -->
+<!ENTITY ycy              "&#x0044B;" ><!--=small yeru, Cyrillic -->
+<!ENTITY Ycy              "&#x0042B;" ><!--=capital YERU, Cyrillic -->
+<!ENTITY yucy             "&#x0044E;" ><!--=small yu, Cyrillic -->
+<!ENTITY YUcy             "&#x0042E;" ><!--=capital YU, Cyrillic -->
+<!ENTITY zcy              "&#x00437;" ><!--=small ze, Cyrillic -->
+<!ENTITY Zcy              "&#x00417;" ><!--=capital ZE, Cyrillic -->
+<!ENTITY zhcy             "&#x00436;" ><!--=small zhe, Cyrillic -->
+<!ENTITY ZHcy             "&#x00416;" ><!--=capital ZHE, Cyrillic -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isocyr2.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isocyr2.ent
new file mode 100644
index 00000000000..67c477b24db
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isocyr2.ent
@@ -0,0 +1,53 @@
+
+<!--
+     File isocyr2.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY djcy             "&#x00452;" ><!--=small dje, Serbian -->
+<!ENTITY DJcy             "&#x00402;" ><!--=capital DJE, Serbian -->
+<!ENTITY dscy             "&#x00455;" ><!--=small dse, Macedonian -->
+<!ENTITY DScy             "&#x00405;" ><!--=capital DSE, Macedonian -->
+<!ENTITY dzcy             "&#x0045F;" ><!--=small dze, Serbian -->
+<!ENTITY DZcy             "&#x0040F;" ><!--=capital dze, Serbian -->
+<!ENTITY gjcy             "&#x00453;" ><!--=small gje, Macedonian -->
+<!ENTITY GJcy             "&#x00403;" ><!--=capital GJE Macedonian -->
+<!ENTITY iukcy            "&#x00456;" ><!--=small i, Ukrainian -->
+<!ENTITY Iukcy            "&#x00406;" ><!--=capital I, Ukrainian -->
+<!ENTITY jsercy           "&#x00458;" ><!--=small je, Serbian -->
+<!ENTITY Jsercy           "&#x00408;" ><!--=capital JE, Serbian -->
+<!ENTITY jukcy            "&#x00454;" ><!--=small je, Ukrainian -->
+<!ENTITY Jukcy            "&#x00404;" ><!--=capital JE, Ukrainian -->
+<!ENTITY kjcy             "&#x0045C;" ><!--=small kje Macedonian -->
+<!ENTITY KJcy             "&#x0040C;" ><!--=capital KJE, Macedonian -->
+<!ENTITY ljcy             "&#x00459;" ><!--=small lje, Serbian -->
+<!ENTITY LJcy             "&#x00409;" ><!--=capital LJE, Serbian -->
+<!ENTITY njcy             "&#x0045A;" ><!--=small nje, Serbian -->
+<!ENTITY NJcy             "&#x0040A;" ><!--=capital NJE, Serbian -->
+<!ENTITY tshcy            "&#x0045B;" ><!--=small tshe, Serbian -->
+<!ENTITY TSHcy            "&#x0040B;" ><!--=capital TSHE, Serbian -->
+<!ENTITY ubrcy            "&#x0045E;" ><!--=small u, Byelorussian -->
+<!ENTITY Ubrcy            "&#x0040E;" ><!--=capital U, Byelorussian -->
+<!ENTITY yicy             "&#x00457;" ><!--=small yi, Ukrainian -->
+<!ENTITY YIcy             "&#x00407;" ><!--=capital YI, Ukrainian -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isodia.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isodia.ent
new file mode 100644
index 00000000000..ba6496300fc
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isodia.ent
@@ -0,0 +1,41 @@
+
+<!--
+     File isodia.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY acute            "&#x000B4;" ><!--=acute accent -->
+<!ENTITY breve            "&#x002D8;" ><!--=breve -->
+<!ENTITY caron            "&#x002C7;" ><!--=caron -->
+<!ENTITY cedil            "&#x000B8;" ><!--=cedilla -->
+<!ENTITY circ             "&#x0005E;" ><!--circumflex accent -->
+<!ENTITY dblac            "&#x002DD;" ><!--=double acute accent -->
+<!ENTITY die              "&#x000A8;" ><!--=dieresis -->
+<!ENTITY dot              "&#x002D9;" ><!--=dot above -->
+<!ENTITY grave            "&#x00060;" ><!--=grave accent -->
+<!ENTITY macr             "&#x000AF;" ><!--=macron -->
+<!ENTITY ogon             "&#x002DB;" ><!--=ogonek -->
+<!ENTITY ring             "&#x002DA;" ><!--=ring -->
+<!ENTITY tilde            "&#x002DC;" ><!--=tilde -->
+<!ENTITY uml              "&#x000A8;" ><!--=umlaut mark -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk1.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk1.ent
new file mode 100644
index 00000000000..63b9f14ce89
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk1.ent
@@ -0,0 +1,75 @@
+<!-- 
+
+     File isogrk1.ent produced by the dsssl script ent.dsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments in the STIX proposal for characters
+     for Mathematics.
+
+     The STIX assignments are temporary and will change if
+     the proposal or some variant of it is adopted by the
+     Unicode Consortium.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+-->
+
+<!ENTITY agr        "&#945;"   ><!--U03B1 =small alpha, Greek -->
+<!ENTITY Agr        "&#913;"   ><!--U0391 =capital Alpha, Greek -->
+<!ENTITY bgr        "&#946;"   ><!--U03B2 =small beta, Greek -->
+<!ENTITY Bgr        "&#914;"   ><!--U0392 =capital Beta, Greek -->
+<!ENTITY dgr        "&#948;"   ><!--U03B4 =small delta, Greek -->
+<!ENTITY Dgr        "&#916;"   ><!--U0394 =capital Delta, Greek -->
+<!ENTITY eegr       "&#951;"   ><!--U03B7 =small eta, Greek -->
+<!ENTITY egr        "&#949;"   ><!--U03B5 =small epsilon, Greek -->
+<!ENTITY EEgr       "&#919;"   ><!--U0397 =capital Eta, Greek -->
+<!ENTITY Egr        "&#917;"   ><!--U0395 =capital Epsilon, Greek -->
+<!ENTITY ggr        "&#947;"   ><!--U03B3 =small gamma, Greek -->
+<!ENTITY Ggr        "&#915;"   ><!--U0393 =capital Gamma, Greek -->
+<!ENTITY igr        "&#953;"   ><!--U03B9 =small iota, Greek -->
+<!ENTITY Igr        "&#921;"   ><!--U0399 =capital Iota, Greek -->
+<!ENTITY kgr        "&#954;"   ><!--U03BA =small kappa, Greek -->
+<!ENTITY khgr       "&#967;"   ><!--U03C7 =small chi, Greek -->
+<!ENTITY Kgr        "&#922;"   ><!--U039A =capital Kappa, Greek -->
+<!ENTITY KHgr       "&#935;"   ><!--U03A7 =capital Chi, Greek -->
+<!ENTITY lgr        "&#955;"   ><!--U03BB =small lambda, Greek -->
+<!ENTITY Lgr        "&#923;"   ><!--U039B =capital Lambda, Greek -->
+<!ENTITY mgr        "&#956;"   ><!--U03BC =small mu, Greek -->
+<!ENTITY Mgr        "&#924;"   ><!--U039C =capital Mu, Greek -->
+<!ENTITY ngr        "&#957;"   ><!--U03BD =small nu, Greek -->
+<!ENTITY Ngr        "&#925;"   ><!--U039D =capital Nu, Greek -->
+<!ENTITY ogr        "&#959;"   ><!--U03BF =small omicron, Greek -->
+<!ENTITY ohgr       "&#969;"   ><!--U03C9 =small omega, Greek -->
+<!ENTITY Ogr        "&#927;"   ><!--U039F =capital Omicron, Greek -->
+<!ENTITY OHgr       "&#937;"   ><!--U03A9 =capital Omega, Greek -->
+<!ENTITY pgr        "&#960;"   ><!--U03C0 =small pi, Greek -->
+<!ENTITY phgr       "&#966;"   ><!--U03C6 =small phi, Greek -->
+<!ENTITY psgr       "&#968;"   ><!--U03C8 =small psi, Greek -->
+<!ENTITY Pgr        "&#928;"   ><!--U03A0 =capital Pi, Greek -->
+<!ENTITY PHgr       "&#934;"   ><!--U03A6 =capital Phi, Greek -->
+<!ENTITY PSgr       "&#936;"   ><!--U03A8 =capital Psi, Greek -->
+<!ENTITY rgr        "&#961;"   ><!--U03C1 =small rho, Greek -->
+<!ENTITY Rgr        "&#929;"   ><!--U03A1 =capital Rho, Greek -->
+<!ENTITY sfgr       "&#962;"   ><!--U03C2 =final small sigma, Greek -->
+<!ENTITY sgr        "&#963;"   ><!--U03C3 =small sigma, Greek -->
+<!ENTITY Sgr        "&#931;"   ><!--U03A3 =capital Sigma, Greek -->
+<!ENTITY tgr        "&#964;"   ><!--U03C4 =small tau, Greek -->
+<!ENTITY thgr       "&#952;"   ><!--U03B8 =small theta, Greek -->
+<!ENTITY Tgr        "&#932;"   ><!--U03A4 =capital Tau, Greek -->
+<!ENTITY THgr       "&#920;"   ><!--U0398 =capital Theta, Greek -->
+<!ENTITY ugr        "&#965;"   ><!--U03C5 =small upsilon, Greek -->
+<!ENTITY Ugr        "&#933;"   ><!--U03A5 =capital Upsilon, Greek -->
+<!ENTITY xgr        "&#958;"   ><!--U03BE =small xi, Greek -->
+<!ENTITY Xgr        "&#926;"   ><!--U039E =capital Xi, Greek -->
+<!ENTITY zgr        "&#950;"   ><!--U03B6 =small zeta, Greek -->
+<!ENTITY Zgr        "&#918;"   ><!--U0396 =capital Zeta, Greek -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk2.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk2.ent
new file mode 100644
index 00000000000..424786cabbf
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk2.ent
@@ -0,0 +1,46 @@
+<!-- 
+
+     File isogrk2.ent produced by the dsssl script ent.dsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments in the STIX proposal for characters
+     for Mathematics.
+
+     The STIX assignments are temporary and will change if
+     the proposal or some variant of it is adopted by the
+     Unicode Consortium.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+-->
+
+<!ENTITY aacgr      "&#940;"   ><!--U03AC =small alpha, accent, Greek -->
+<!ENTITY Aacgr      "&#902;"   ><!--U0386 =capital Alpha, accent, Greek -->
+<!ENTITY eacgr      "&#941;"   ><!--U03AD =small epsilon, accent, Greek -->
+<!ENTITY eeacgr     "&#942;"   ><!--U03AE =small eta, accent, Greek -->
+<!ENTITY Eacgr      "&#904;"   ><!--U0388 =capital Epsilon, accent, Greek -->
+<!ENTITY EEacgr     "&#905;"   ><!--U0389 =capital Eta, accent, Greek -->
+<!ENTITY iacgr      "&#943;"   ><!--U03AF =small iota, accent, Greek -->
+<!ENTITY idiagr     "&#912;"   ><!--U0390 =small iota, dieresis, accent, Greek -->
+<!ENTITY idigr      "&#970;"   ><!--U03CA =small iota, dieresis, Greek -->
+<!ENTITY Iacgr      "&#906;"   ><!--U038A =capital Iota, accent, Greek -->
+<!ENTITY Idigr      "&#938;"   ><!--U03AA =capital Iota, dieresis, Greek -->
+<!ENTITY oacgr      "&#972;"   ><!--U03CC =small omicron, accent, Greek -->
+<!ENTITY ohacgr     "&#974;"   ><!--U03CE =small omega, accent, Greek -->
+<!ENTITY Oacgr      "&#908;"   ><!--U038C =capital Omicron, accent, Greek -->
+<!ENTITY OHacgr     "&#911;"   ><!--U038F =capital Omega, accent, Greek -->
+<!ENTITY uacgr      "&#973;"   ><!--U03CD =small upsilon, accent, Greek -->
+<!ENTITY udiagr     "&#944;"   ><!--U03B0 =small upsilon, dieresis, accent, Greek -->
+<!ENTITY udigr      "&#971;"   ><!--U03CB =small upsilon, dieresis, Greek -->
+<!ENTITY Uacgr      "&#910;"   ><!--U038E =capital Upsilon, accent, Greek -->
+<!ENTITY Udigr      "&#939;"   ><!--U03AB =capital Upsilon, dieresis, Greek -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk3.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk3.ent
new file mode 100644
index 00000000000..fa033550489
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk3.ent
@@ -0,0 +1,70 @@
+
+<!--
+     File isogrk3.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY alpha            "&#x003B1;" ><!--/alpha small alpha, Greek -->
+<!ENTITY beta             "&#x003B2;" ><!--/beta small beta, Greek -->
+<!ENTITY chi              "&#x003C7;" ><!--/chi small chi, Greek -->
+<!ENTITY delta            "&#x003B4;" ><!--/delta small delta, Greek -->
+<!ENTITY Delta            "&#x00394;" ><!--/Delta capital Delta, Greek -->
+<!ENTITY epsi             "&#x003B5;" ><!--/straightepsilon, small epsilon, Greek -->
+<!ENTITY epsiv            "&#x0025B;" ><!--/varepsilon -->
+<!ENTITY eta              "&#x003B7;" ><!--/eta small eta, Greek -->
+<!ENTITY gamma            "&#x003B3;" ><!--/gamma small gamma, Greek -->
+<!ENTITY Gamma            "&#x00393;" ><!--/Gamma capital Gamma, Greek -->
+<!ENTITY gammad           "&#x003DC;" ><!--/digamma -->
+<!ENTITY Gammad           "&#x003DC;" ><!--capital digamma -->
+<!ENTITY iota             "&#x003B9;" ><!--/iota small iota, Greek -->
+<!ENTITY kappa            "&#x003BA;" ><!--/kappa small kappa, Greek -->
+<!ENTITY kappav           "&#x003F0;" ><!--/varkappa -->
+<!ENTITY lambda           "&#x003BB;" ><!--/lambda small lambda, Greek -->
+<!ENTITY Lambda           "&#x0039B;" ><!--/Lambda capital Lambda, Greek -->
+<!ENTITY mu               "&#x003BC;" ><!--/mu small mu, Greek -->
+<!ENTITY nu               "&#x003BD;" ><!--/nu small nu, Greek -->
+<!ENTITY omega            "&#x003C9;" ><!--/omega small omega, Greek -->
+<!ENTITY Omega            "&#x003A9;" ><!--/Omega capital Omega, Greek -->
+<!ENTITY phi              "&#x003C6;" ><!--/straightphi - small phi, Greek -->
+<!ENTITY Phi              "&#x003A6;" ><!--/Phi capital Phi, Greek -->
+<!ENTITY phiv             "&#x003D5;" ><!--/varphi - curly or open phi -->
+<!ENTITY pi               "&#x003C0;" ><!--/pi small pi, Greek -->
+<!ENTITY Pi               "&#x003A0;" ><!--/Pi capital Pi, Greek -->
+<!ENTITY piv              "&#x003D6;" ><!--/varpi -->
+<!ENTITY psi              "&#x003C8;" ><!--/psi small psi, Greek -->
+<!ENTITY Psi              "&#x003A8;" ><!--/Psi capital Psi, Greek -->
+<!ENTITY rho              "&#x003C1;" ><!--/rho small rho, Greek -->
+<!ENTITY rhov             "&#x003F1;" ><!--/varrho -->
+<!ENTITY sigma            "&#x003C3;" ><!--/sigma small sigma, Greek -->
+<!ENTITY Sigma            "&#x003A3;" ><!--/Sigma capital Sigma, Greek -->
+<!ENTITY sigmav           "&#x003C2;" ><!--/varsigma -->
+<!ENTITY tau              "&#x003C4;" ><!--/tau small tau, Greek -->
+<!ENTITY theta            "&#x003B8;" ><!--/theta straight theta, small theta, Greek -->
+<!ENTITY Theta            "&#x00398;" ><!--/Theta capital Theta, Greek -->
+<!ENTITY thetav           "&#x003D1;" ><!--/vartheta - curly or open theta -->
+<!ENTITY upsi             "&#x003C5;" ><!--/upsilon small upsilon, Greek -->
+<!ENTITY Upsi             "&#x003D2;" ><!--/Upsilon capital Upsilon, Greek -->
+<!ENTITY xi               "&#x003BE;" ><!--/xi small xi, Greek -->
+<!ENTITY Xi               "&#x0039E;" ><!--/Xi capital Xi, Greek -->
+<!ENTITY zeta             "&#x003B6;" ><!--/zeta small zeta, Greek -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk4.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk4.ent
new file mode 100644
index 00000000000..71f834042bc
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isogrk4.ent
@@ -0,0 +1,69 @@
+<!-- 
+
+     File isogrk4.ent produced by the dsssl script ent.dsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments in the STIX proposal for characters
+     for Mathematics.
+
+     The STIX assignments are temporary and will change if
+     the proposal or some variant of it is adopted by the
+     Unicode Consortium.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+-->
+
+<!ENTITY b.alpha    "&#59136;" ><!--UE700 small alpha, Greek -->
+<!ENTITY b.beta     "&#59137;" ><!--UE701 small beta, Greek -->
+<!ENTITY b.chi      "&#59175;" ><!--UE727 small chi, Greek -->
+<!ENTITY b.delta    "&#59142;" ><!--UE706 small delta, Greek -->
+<!ENTITY b.Delta    "&#59143;" ><!--UE707 capital delta, Greek -->
+<!ENTITY b.epsi     "&#59144;" ><!--UE708 small epsilon, Greek -->
+<!ENTITY b.epsiv    "&#59146;" ><!--UE709 varepsilion -->
+<!ENTITY b.eta      "&#59148;" ><!--UE70C small eta, Greek -->
+<!ENTITY b.gamma    "&#59138;" ><!--UE702 small gamma, Greek -->
+<!ENTITY b.gammad   "&#59140;" ><!--UE704 digamma, Greek -->
+<!ENTITY b.Gamma    "&#59139;" ><!--UE703 capital gamma, Greek -->
+<!ENTITY b.Gammad   "&#59141;" ><!--UE705 capital digamma, Greek -->
+<!ENTITY b.iota     "&#59152;" ><!--UE710 small iota, Greek -->
+<!ENTITY b.kappa    "&#59153;" ><!--UE711 small kappa, Greek -->
+<!ENTITY b.kappav   "&#59154;" ><!--UE712 var kappa, Greek -->
+<!ENTITY b.lambda   "&#59155;" ><!--UE713 small lambda, Greek -->
+<!ENTITY b.Lambda   "&#59156;" ><!--UE714 capital lambda, Greek -->
+<!ENTITY b.mu       "&#59157;" ><!--UE715 small mu, Greek -->
+<!ENTITY b.nu       "&#59158;" ><!--UE716 small nu, Greek -->
+<!ENTITY b.omega    "&#59178;" ><!--UE72A small omega, Greek -->
+<!ENTITY b.Omega    "&#59179;" ><!--UE72B capital Omega, Greek -->
+<!ENTITY b.phis     "&#59172;" ><!--UE724 straight phi, Greek -->
+<!ENTITY b.phiv     "&#59174;" ><!--UE726 varphi -->
+<!ENTITY b.pi       "&#59161;" ><!--UE719 small pi, Greek -->
+<!ENTITY b.piv      "&#59163;" ><!--UE71B varpi -->
+<!ENTITY b.psi      "&#59176;" ><!--UE728 small psi, Greek -->
+<!ENTITY b.Phi      "&#59173;" ><!--UE725 capital Phi, Greek -->
+<!ENTITY b.Pi       "&#59162;" ><!--UE71A capital pi, Greek -->
+<!ENTITY b.Psi      "&#59177;" ><!--UE729 capital Psi, Greek -->
+<!ENTITY b.rho      "&#59164;" ><!--UE71C small rho, Greek -->
+<!ENTITY b.rhov     "&#59165;" ><!--UE71D varrho -->
+<!ENTITY b.sigma    "&#59166;" ><!--UE71E small sigma, Greek -->
+<!ENTITY b.sigmav   "&#59168;" ><!--UE720 varsigma -->
+<!ENTITY b.Sigma    "&#59167;" ><!--UE71F capital sigma, Greek -->
+<!ENTITY b.tau      "&#59169;" ><!--UE721 small tau, Greek -->
+<!ENTITY b.thetas   "&#59149;" ><!--UE70D straight theta, Greek -->
+<!ENTITY b.thetav   "&#59151;" ><!--UE70F var theta, Greek -->
+<!ENTITY b.Theta    "&#59150;" ><!--UE70E capital theta, Greek -->
+<!ENTITY b.upsi     "&#59170;" ><!--UE722 small upsilon, Greek -->
+<!ENTITY b.Upsilon  "&#59171;" ><!--UE723 capital upsilon, Greek -->
+<!ENTITY b.xi       "&#59159;" ><!--UE717 small xi, Greek -->
+<!ENTITY b.Xi       "&#59160;" ><!--UE718 capital xi, Greek -->
+<!ENTITY b.zeta     "&#59145;" ><!--UE70B small zeta, Greek -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isolat1.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isolat1.ent
new file mode 100644
index 00000000000..849d360aeae
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isolat1.ent
@@ -0,0 +1,89 @@
+
+<!--
+     File isolat1.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY aacute           "&#x000E1;" ><!--=small a, acute accent -->
+<!ENTITY Aacute           "&#x000C1;" ><!--=capital A, acute accent -->
+<!ENTITY acirc            "&#x000E2;" ><!--=small a, circumflex accent -->
+<!ENTITY Acirc            "&#x000C2;" ><!--=capital A, circumflex accent -->
+<!ENTITY aelig            "&#x000E6;" ><!--=small ae diphthong (ligature) -->
+<!ENTITY AElig            "&#x000C6;" ><!--=capital AE diphthong (ligature) -->
+<!ENTITY agrave           "&#x000E0;" ><!--=small a, grave accent -->
+<!ENTITY Agrave           "&#x000C0;" ><!--=capital A, grave accent -->
+<!ENTITY aring            "&#x000E5;" ><!--=small a, ring -->
+<!ENTITY Aring            "&#x000C5;" ><!--=capital A, ring -->
+<!ENTITY atilde           "&#x000E3;" ><!--=small a, tilde -->
+<!ENTITY Atilde           "&#x000C3;" ><!--=capital A, tilde -->
+<!ENTITY auml             "&#x000E4;" ><!--=small a, dieresis or umlaut mark -->
+<!ENTITY Auml             "&#x000C4;" ><!--=capital A, dieresis or umlaut mark -->
+<!ENTITY ccedil           "&#x000E7;" ><!--=small c, cedilla -->
+<!ENTITY Ccedil           "&#x000C7;" ><!--=capital C, cedilla -->
+<!ENTITY eacute           "&#x000E9;" ><!--=small e, acute accent -->
+<!ENTITY Eacute           "&#x000C9;" ><!--=capital E, acute accent -->
+<!ENTITY ecirc            "&#x000EA;" ><!--=small e, circumflex accent -->
+<!ENTITY Ecirc            "&#x000CA;" ><!--=capital E, circumflex accent -->
+<!ENTITY egrave           "&#x000E8;" ><!--=small e, grave accent -->
+<!ENTITY Egrave           "&#x000C8;" ><!--=capital E, grave accent -->
+<!ENTITY eth              "&#x000F0;" ><!--=small eth, Icelandic -->
+<!ENTITY ETH              "&#x000D0;" ><!--=capital Eth, Icelandic -->
+<!ENTITY euml             "&#x000EB;" ><!--=small e, dieresis or umlaut mark -->
+<!ENTITY Euml             "&#x000CB;" ><!--=capital E, dieresis or umlaut mark -->
+<!ENTITY iacute           "&#x000ED;" ><!--=small i, acute accent -->
+<!ENTITY Iacute           "&#x000CD;" ><!--=capital I, acute accent -->
+<!ENTITY icirc            "&#x000EE;" ><!--=small i, circumflex accent -->
+<!ENTITY Icirc            "&#x000CE;" ><!--=capital I, circumflex accent -->
+<!ENTITY igrave           "&#x000EC;" ><!--=small i, grave accent -->
+<!ENTITY Igrave           "&#x000CC;" ><!--=capital I, grave accent -->
+<!ENTITY iuml             "&#x000EF;" ><!--=small i, dieresis or umlaut mark -->
+<!ENTITY Iuml             "&#x000CF;" ><!--=capital I, dieresis or umlaut mark -->
+<!ENTITY ntilde           "&#x000F1;" ><!--=small n, tilde -->
+<!ENTITY Ntilde           "&#x000D1;" ><!--=capital N, tilde -->
+<!ENTITY oacute           "&#x000F3;" ><!--=small o, acute accent -->
+<!ENTITY Oacute           "&#x000D3;" ><!--=capital O, acute accent -->
+<!ENTITY ocirc            "&#x000F4;" ><!--=small o, circumflex accent -->
+<!ENTITY Ocirc            "&#x000D4;" ><!--=capital O, circumflex accent -->
+<!ENTITY ograve           "&#x000F2;" ><!--=small o, grave accent -->
+<!ENTITY Ograve           "&#x000D2;" ><!--=capital O, grave accent -->
+<!ENTITY oslash           "&#x000F8;" ><!--latin small letter o with stroke -->
+<!ENTITY Oslash           "&#x000D8;" ><!--=capital O, slash -->
+<!ENTITY otilde           "&#x000F5;" ><!--=small o, tilde -->
+<!ENTITY Otilde           "&#x000D5;" ><!--=capital O, tilde -->
+<!ENTITY ouml             "&#x000F6;" ><!--=small o, dieresis or umlaut mark -->
+<!ENTITY Ouml             "&#x000D6;" ><!--=capital O, dieresis or umlaut mark -->
+<!ENTITY szlig            "&#x000DF;" ><!--=small sharp s, German (sz ligature) -->
+<!ENTITY thorn            "&#x000FE;" ><!--=small thorn, Icelandic -->
+<!ENTITY THORN            "&#x000DE;" ><!--=capital THORN, Icelandic -->
+<!ENTITY uacute           "&#x000FA;" ><!--=small u, acute accent -->
+<!ENTITY Uacute           "&#x000DA;" ><!--=capital U, acute accent -->
+<!ENTITY ucirc            "&#x000FB;" ><!--=small u, circumflex accent -->
+<!ENTITY Ucirc            "&#x000DB;" ><!--=capital U, circumflex accent -->
+<!ENTITY ugrave           "&#x000F9;" ><!--=small u, grave accent -->
+<!ENTITY Ugrave           "&#x000D9;" ><!--=capital U, grave accent -->
+<!ENTITY uuml             "&#x000FC;" ><!--=small u, dieresis or umlaut mark -->
+<!ENTITY Uuml             "&#x000DC;" ><!--=capital U, dieresis or umlaut mark -->
+<!ENTITY yacute           "&#x000FD;" ><!--=small y, acute accent -->
+<!ENTITY Yacute           "&#x000DD;" ><!--=capital Y, acute accent -->
+<!ENTITY yuml             "&#x000FF;" ><!--=small y, dieresis or umlaut mark -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isolat2.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isolat2.ent
new file mode 100644
index 00000000000..3049be7f1f1
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isolat2.ent
@@ -0,0 +1,148 @@
+
+<!--
+     File isolat2.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY abreve           "&#x00103;" ><!--=small a, breve -->
+<!ENTITY Abreve           "&#x00102;" ><!--=capital A, breve -->
+<!ENTITY amacr            "&#x00101;" ><!--=small a, macron -->
+<!ENTITY Amacr            "&#x00100;" ><!--=capital A, macron -->
+<!ENTITY aogon            "&#x00105;" ><!--=small a, ogonek -->
+<!ENTITY Aogon            "&#x00104;" ><!--=capital A, ogonek -->
+<!ENTITY cacute           "&#x00107;" ><!--=small c, acute accent -->
+<!ENTITY Cacute           "&#x00106;" ><!--=capital C, acute accent -->
+<!ENTITY ccaron           "&#x0010D;" ><!--=small c, caron -->
+<!ENTITY Ccaron           "&#x0010C;" ><!--=capital C, caron -->
+<!ENTITY ccirc            "&#x00109;" ><!--=small c, circumflex accent -->
+<!ENTITY Ccirc            "&#x00108;" ><!--=capital C, circumflex accent -->
+<!ENTITY cdot             "&#x0010B;" ><!--=small c, dot above -->
+<!ENTITY Cdot             "&#x0010A;" ><!--=capital C, dot above -->
+<!ENTITY dcaron           "&#x0010F;" ><!--=small d, caron -->
+<!ENTITY Dcaron           "&#x0010E;" ><!--=capital D, caron -->
+<!ENTITY dstrok           "&#x00111;" ><!--=small d, stroke -->
+<!ENTITY Dstrok           "&#x00110;" ><!--=capital D, stroke -->
+<!ENTITY ecaron           "&#x0011B;" ><!--=small e, caron -->
+<!ENTITY Ecaron           "&#x0011A;" ><!--=capital E, caron -->
+<!ENTITY edot             "&#x00117;" ><!--=small e, dot above -->
+<!ENTITY Edot             "&#x00116;" ><!--=capital E, dot above -->
+<!ENTITY emacr            "&#x00113;" ><!--=small e, macron -->
+<!ENTITY Emacr            "&#x00112;" ><!--=capital E, macron -->
+<!ENTITY eng              "&#x0014B;" ><!--=small eng, Lapp -->
+<!ENTITY ENG              "&#x0014A;" ><!--=capital ENG, Lapp -->
+<!ENTITY eogon            "&#x00119;" ><!--=small e, ogonek -->
+<!ENTITY Eogon            "&#x00118;" ><!--=capital E, ogonek -->
+<!ENTITY gacute           "&#x001F5;" ><!--=small g, acute accent -->
+<!ENTITY gbreve           "&#x0011F;" ><!--=small g, breve -->
+<!ENTITY Gbreve           "&#x0011E;" ><!--=capital G, breve -->
+<!ENTITY Gcedil           "&#x00122;" ><!--=capital G, cedilla -->
+<!ENTITY gcirc            "&#x0011D;" ><!--=small g, circumflex accent -->
+<!ENTITY Gcirc            "&#x0011C;" ><!--=capital G, circumflex accent -->
+<!ENTITY gdot             "&#x00121;" ><!--=small g, dot above -->
+<!ENTITY Gdot             "&#x00120;" ><!--=capital G, dot above -->
+<!ENTITY hcirc            "&#x00125;" ><!--=small h, circumflex accent -->
+<!ENTITY Hcirc            "&#x00124;" ><!--=capital H, circumflex accent -->
+<!ENTITY hstrok           "&#x00127;" ><!--=small h, stroke -->
+<!ENTITY Hstrok           "&#x00126;" ><!--=capital H, stroke -->
+<!ENTITY Idot             "&#x00130;" ><!--=capital I, dot above -->
+<!ENTITY ijlig            "&#x00133;" ><!--=small ij ligature -->
+<!ENTITY IJlig            "&#x00132;" ><!--=capital IJ ligature -->
+<!ENTITY imacr            "&#x0012B;" ><!--=small i, macron -->
+<!ENTITY Imacr            "&#x0012A;" ><!--=capital I, macron -->
+<!ENTITY inodot           "&#x00131;" ><!--=small i without dot -->
+<!ENTITY iogon            "&#x0012F;" ><!--=small i, ogonek -->
+<!ENTITY Iogon            "&#x0012E;" ><!--=capital I, ogonek -->
+<!ENTITY itilde           "&#x00129;" ><!--=small i, tilde -->
+<!ENTITY Itilde           "&#x00128;" ><!--=capital I, tilde -->
+<!ENTITY jcirc            "&#x00135;" ><!--=small j, circumflex accent -->
+<!ENTITY Jcirc            "&#x00134;" ><!--=capital J, circumflex accent -->
+<!ENTITY kcedil           "&#x00137;" ><!--=small k, cedilla -->
+<!ENTITY Kcedil           "&#x00136;" ><!--=capital K, cedilla -->
+<!ENTITY kgreen           "&#x00138;" ><!--=small k, Greenlandic -->
+<!ENTITY lacute           "&#x0013A;" ><!--=small l, acute accent -->
+<!ENTITY Lacute           "&#x00139;" ><!--=capital L, acute accent -->
+<!ENTITY lcaron           "&#x0013E;" ><!--=small l, caron -->
+<!ENTITY Lcaron           "&#x0013D;" ><!--=capital L, caron -->
+<!ENTITY lcedil           "&#x0013C;" ><!--=small l, cedilla -->
+<!ENTITY Lcedil           "&#x0013B;" ><!--=capital L, cedilla -->
+<!ENTITY lmidot           "&#x00140;" ><!--=small l, middle dot -->
+<!ENTITY Lmidot           "&#x0013F;" ><!--=capital L, middle dot -->
+<!ENTITY lstrok           "&#x00142;" ><!--=small l, stroke -->
+<!ENTITY Lstrok           "&#x00141;" ><!--=capital L, stroke -->
+<!ENTITY nacute           "&#x00144;" ><!--=small n, acute accent -->
+<!ENTITY Nacute           "&#x00143;" ><!--=capital N, acute accent -->
+<!ENTITY napos            "&#x00149;" ><!--=small n, apostrophe -->
+<!ENTITY ncaron           "&#x00148;" ><!--=small n, caron -->
+<!ENTITY Ncaron           "&#x00147;" ><!--=capital N, caron -->
+<!ENTITY ncedil           "&#x00146;" ><!--=small n, cedilla -->
+<!ENTITY Ncedil           "&#x00145;" ><!--=capital N, cedilla -->
+<!ENTITY odblac           "&#x00151;" ><!--=small o, double acute accent -->
+<!ENTITY Odblac           "&#x00150;" ><!--=capital O, double acute accent -->
+<!ENTITY oelig            "&#x00153;" ><!--=small oe ligature -->
+<!ENTITY OElig            "&#x00152;" ><!--=capital OE ligature -->
+<!ENTITY omacr            "&#x0014D;" ><!--=small o, macron -->
+<!ENTITY Omacr            "&#x0014C;" ><!--=capital O, macron -->
+<!ENTITY racute           "&#x00155;" ><!--=small r, acute accent -->
+<!ENTITY Racute           "&#x00154;" ><!--=capital R, acute accent -->
+<!ENTITY rcaron           "&#x00159;" ><!--=small r, caron -->
+<!ENTITY Rcaron           "&#x00158;" ><!--=capital R, caron -->
+<!ENTITY rcedil           "&#x00157;" ><!--=small r, cedilla -->
+<!ENTITY Rcedil           "&#x00156;" ><!--=capital R, cedilla -->
+<!ENTITY sacute           "&#x0015B;" ><!--=small s, acute accent -->
+<!ENTITY Sacute           "&#x0015A;" ><!--=capital S, acute accent -->
+<!ENTITY scaron           "&#x00161;" ><!--=small s, caron -->
+<!ENTITY Scaron           "&#x00160;" ><!--=capital S, caron -->
+<!ENTITY scedil           "&#x0015F;" ><!--=small s, cedilla -->
+<!ENTITY Scedil           "&#x0015E;" ><!--=capital S, cedilla -->
+<!ENTITY scirc            "&#x0015D;" ><!--=small s, circumflex accent -->
+<!ENTITY Scirc            "&#x0015C;" ><!--=capital S, circumflex accent -->
+<!ENTITY tcaron           "&#x00165;" ><!--=small t, caron -->
+<!ENTITY Tcaron           "&#x00164;" ><!--=capital T, caron -->
+<!ENTITY tcedil           "&#x00163;" ><!--=small t, cedilla -->
+<!ENTITY Tcedil           "&#x00162;" ><!--=capital T, cedilla -->
+<!ENTITY tstrok           "&#x00167;" ><!--=small t, stroke -->
+<!ENTITY Tstrok           "&#x00166;" ><!--=capital T, stroke -->
+<!ENTITY ubreve           "&#x0016D;" ><!--=small u, breve -->
+<!ENTITY Ubreve           "&#x0016C;" ><!--=capital U, breve -->
+<!ENTITY udblac           "&#x00171;" ><!--=small u, double acute accent -->
+<!ENTITY Udblac           "&#x00170;" ><!--=capital U, double acute accent -->
+<!ENTITY umacr            "&#x0016B;" ><!--=small u, macron -->
+<!ENTITY Umacr            "&#x0016A;" ><!--=capital U, macron -->
+<!ENTITY uogon            "&#x00173;" ><!--=small u, ogonek -->
+<!ENTITY Uogon            "&#x00172;" ><!--=capital U, ogonek -->
+<!ENTITY uring            "&#x0016F;" ><!--=small u, ring -->
+<!ENTITY Uring            "&#x0016E;" ><!--=capital U, ring -->
+<!ENTITY utilde           "&#x00169;" ><!--=small u, tilde -->
+<!ENTITY Utilde           "&#x00168;" ><!--=capital U, tilde -->
+<!ENTITY wcirc            "&#x00175;" ><!--=small w, circumflex accent -->
+<!ENTITY Wcirc            "&#x00174;" ><!--=capital W, circumflex accent -->
+<!ENTITY ycirc            "&#x00177;" ><!--=small y, circumflex accent -->
+<!ENTITY Ycirc            "&#x00176;" ><!--=capital Y, circumflex accent -->
+<!ENTITY Yuml             "&#x00178;" ><!--=capital Y, dieresis or umlaut mark -->
+<!ENTITY zacute           "&#x0017A;" ><!--=small z, acute accent -->
+<!ENTITY Zacute           "&#x00179;" ><!--=capital Z, acute accent -->
+<!ENTITY zcaron           "&#x0017E;" ><!--=small z, caron -->
+<!ENTITY Zcaron           "&#x0017D;" ><!--=capital Z, caron -->
+<!ENTITY zdot             "&#x0017C;" ><!--=small z, dot above -->
+<!ENTITY Zdot             "&#x0017B;" ><!--=capital Z, dot above -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isomfrk.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isomfrk.ent
new file mode 100644
index 00000000000..397212a6432
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isomfrk.ent
@@ -0,0 +1,79 @@
+
+<!--
+     File isomfrk.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY afr              "&#x1D51E;" ><!--/frak a, lower case a -->
+<!ENTITY Afr              "&#x1D504;" ><!--/frak A, upper case a -->
+<!ENTITY bfr              "&#x1D51F;" ><!--/frak b, lower case b -->
+<!ENTITY Bfr              "&#x1D505;" ><!--/frak B, upper case b -->
+<!ENTITY cfr              "&#x1D520;" ><!--/frak c, lower case c -->
+<!ENTITY Cfr              "&#x1D506;" ><!--/frak C, upper case c -->
+<!ENTITY dfr              "&#x1D521;" ><!--/frak d, lower case d -->
+<!ENTITY Dfr              "&#x1D507;" ><!--/frak D, upper case d -->
+<!ENTITY efr              "&#x1D522;" ><!--/frak e, lower case e -->
+<!ENTITY Efr              "&#x1D508;" ><!--/frak E, upper case e -->
+<!ENTITY ffr              "&#x1D523;" ><!--/frak f, lower case f -->
+<!ENTITY Ffr              "&#x1D509;" ><!--/frak F, upper case f -->
+<!ENTITY gfr              "&#x1D524;" ><!--/frak g, lower case g -->
+<!ENTITY Gfr              "&#x1D50A;" ><!--/frak G, upper case g -->
+<!ENTITY hfr              "&#x1D525;" ><!--/frak h, lower case h -->
+<!ENTITY Hfr              "&#x1D50B;" ><!--/frak H, upper case h -->
+<!ENTITY ifr              "&#x1D526;" ><!--/frak i, lower case i -->
+<!ENTITY Ifr              "&#x1D50C;" ><!--/frak I, upper case i -->
+<!ENTITY jfr              "&#x1D527;" ><!--/frak j, lower case j -->
+<!ENTITY Jfr              "&#x1D50D;" ><!--/frak J, upper case j -->
+<!ENTITY kfr              "&#x1D528;" ><!--/frak k, lower case k -->
+<!ENTITY Kfr              "&#x1D50E;" ><!--/frak K, upper case k -->
+<!ENTITY lfr              "&#x1D529;" ><!--/frak l, lower case l -->
+<!ENTITY Lfr              "&#x1D50F;" ><!--/frak L, upper case l -->
+<!ENTITY mfr              "&#x1D52A;" ><!--/frak m, lower case m -->
+<!ENTITY Mfr              "&#x1D510;" ><!--/frak M, upper case m -->
+<!ENTITY nfr              "&#x1D52B;" ><!--/frak n, lower case n -->
+<!ENTITY Nfr              "&#x1D511;" ><!--/frak N, upper case n -->
+<!ENTITY ofr              "&#x1D52C;" ><!--/frak o, lower case o -->
+<!ENTITY Ofr              "&#x1D512;" ><!--/frak O, upper case o -->
+<!ENTITY pfr              "&#x1D52D;" ><!--/frak p, lower case p -->
+<!ENTITY Pfr              "&#x1D513;" ><!--/frak P, upper case p -->
+<!ENTITY qfr              "&#x1D52E;" ><!--/frak q, lower case q -->
+<!ENTITY Qfr              "&#x1D514;" ><!--/frak Q, upper case q -->
+<!ENTITY rfr              "&#x1D52F;" ><!--/frak r, lower case r -->
+<!ENTITY Rfr              "&#x1D515;" ><!--/frak R, upper case r -->
+<!ENTITY sfr              "&#x1D530;" ><!--/frak s, lower case s -->
+<!ENTITY Sfr              "&#x1D516;" ><!--/frak S, upper case s -->
+<!ENTITY tfr              "&#x1D531;" ><!--/frak t, lower case t -->
+<!ENTITY Tfr              "&#x1D517;" ><!--/frak T, upper case t -->
+<!ENTITY ufr              "&#x1D532;" ><!--/frak u, lower case u -->
+<!ENTITY Ufr              "&#x1D518;" ><!--/frak U, upper case u -->
+<!ENTITY vfr              "&#x1D533;" ><!--/frak v, lower case v -->
+<!ENTITY Vfr              "&#x1D519;" ><!--/frak V, upper case v -->
+<!ENTITY wfr              "&#x1D534;" ><!--/frak w, lower case w -->
+<!ENTITY Wfr              "&#x1D51A;" ><!--/frak W, upper case w -->
+<!ENTITY xfr              "&#x1D535;" ><!--/frak x, lower case x -->
+<!ENTITY Xfr              "&#x1D51B;" ><!--/frak X, upper case x -->
+<!ENTITY yfr              "&#x1D536;" ><!--/frak y, lower case y -->
+<!ENTITY Yfr              "&#x1D51C;" ><!--/frak Y, upper case y -->
+<!ENTITY zfr              "&#x1D537;" ><!--/frak z, lower case z -->
+<!ENTITY Zfr              "&#x1D51D;" ><!--/frak Z, upper case z  -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isomopf.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isomopf.ent
new file mode 100644
index 00000000000..806b2fb4fef
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isomopf.ent
@@ -0,0 +1,53 @@
+
+<!--
+     File isomopf.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY Aopf             "&#x1D538;" ><!--/Bbb A, open face A -->
+<!ENTITY Bopf             "&#x1D539;" ><!--/Bbb B, open face B -->
+<!ENTITY Copf             "&#x1D53A;" ><!--/Bbb C, open face C -->
+<!ENTITY Dopf             "&#x1D53B;" ><!--/Bbb D, open face D -->
+<!ENTITY Eopf             "&#x1D53C;" ><!--/Bbb E, open face E -->
+<!ENTITY Fopf             "&#x1D53D;" ><!--/Bbb F, open face F -->
+<!ENTITY Gopf             "&#x1D53E;" ><!--/Bbb G, open face G -->
+<!ENTITY Hopf             "&#x1D53F;" ><!--/Bbb H, open face H -->
+<!ENTITY Iopf             "&#x1D540;" ><!--/Bbb I, open face I -->
+<!ENTITY Jopf             "&#x1D541;" ><!--/Bbb J, open face J -->
+<!ENTITY Kopf             "&#x1D542;" ><!--/Bbb K, open face K  -->
+<!ENTITY Lopf             "&#x1D543;" ><!--/Bbb L, open face L  -->
+<!ENTITY Mopf             "&#x1D544;" ><!--/Bbb M, open face M  -->
+<!ENTITY Nopf             "&#x1D545;" ><!--/Bbb N, open face N -->
+<!ENTITY Oopf             "&#x1D546;" ><!--/Bbb O, open face O -->
+<!ENTITY Popf             "&#x1D547;" ><!--/Bbb P, open face P -->
+<!ENTITY Qopf             "&#x1D548;" ><!--/Bbb Q, open face Q -->
+<!ENTITY Ropf             "&#x1D549;" ><!--/Bbb R, open face R -->
+<!ENTITY Sopf             "&#x1D54A;" ><!--/Bbb S, open face S -->
+<!ENTITY Topf             "&#x1D54B;" ><!--/Bbb T, open face T -->
+<!ENTITY Uopf             "&#x1D54C;" ><!--/Bbb U, open face U -->
+<!ENTITY Vopf             "&#x1D54D;" ><!--/Bbb V, open face V -->
+<!ENTITY Wopf             "&#x1D54E;" ><!--/Bbb W, open face W -->
+<!ENTITY Xopf             "&#x1D54F;" ><!--/Bbb X, open face X -->
+<!ENTITY Yopf             "&#x1D550;" ><!--/Bbb Y, open face Y -->
+<!ENTITY Zopf             "&#x1D551;" ><!--/Bbb Z, open face Z -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isomscr.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isomscr.ent
new file mode 100644
index 00000000000..a1bb39c36cb
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isomscr.ent
@@ -0,0 +1,79 @@
+
+<!--
+     File isomscr.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY ascr             "&#x1D4B6;" ><!--/scr a, script letter a -->
+<!ENTITY Ascr             "&#x1D49C;" ><!--/scr A, script letter A -->
+<!ENTITY bscr             "&#x1D4B7;" ><!--/scr b, script letter b -->
+<!ENTITY Bscr             "&#x1D49D;" ><!--/scr B, script letter B -->
+<!ENTITY cscr             "&#x1D4B8;" ><!--/scr c, script letter c -->
+<!ENTITY Cscr             "&#x1D49E;" ><!--/scr C, script letter C -->
+<!ENTITY dscr             "&#x1D4B9;" ><!--/scr d, script letter d -->
+<!ENTITY Dscr             "&#x1D49F;" ><!--/scr D, script letter D -->
+<!ENTITY escr             "&#x1D4BA;" ><!--/scr e, script letter e -->
+<!ENTITY Escr             "&#x1D4A0;" ><!--/scr E, script letter E -->
+<!ENTITY fscr             "&#x1D4BB;" ><!--/scr f, script letter f -->
+<!ENTITY Fscr             "&#x1D4A1;" ><!--/scr F, script letter F -->
+<!ENTITY gscr             "&#x1D4BC;" ><!--/scr g, script letter g -->
+<!ENTITY Gscr             "&#x1D4A2;" ><!--/scr G, script letter G -->
+<!ENTITY hscr             "&#x1D4BD;" ><!--/scr h, script letter h -->
+<!ENTITY Hscr             "&#x1D4A3;" ><!--/scr H, script letter H -->
+<!ENTITY iscr             "&#x1D4BE;" ><!--/scr i, script letter i -->
+<!ENTITY Iscr             "&#x1D4A4;" ><!--/scr I, script letter I -->
+<!ENTITY jscr             "&#x1D4BF;" ><!--/scr j, script letter j -->
+<!ENTITY Jscr             "&#x1D4A5;" ><!--/scr J, script letter J -->
+<!ENTITY kscr             "&#x1D4C0;" ><!--/scr k, script letter k -->
+<!ENTITY Kscr             "&#x1D4A6;" ><!--/scr K, script letter K -->
+<!ENTITY lscr             "&#x1D4C1;" ><!--/scr l, script letter l -->
+<!ENTITY Lscr             "&#x1D4A7;" ><!--/scr L, script letter L -->
+<!ENTITY mscr             "&#x1D4C2;" ><!--/scr m, script letter m -->
+<!ENTITY Mscr             "&#x1D4A8;" ><!--/scr M, script letter M -->
+<!ENTITY nscr             "&#x1D4C3;" ><!--/scr n, script letter n -->
+<!ENTITY Nscr             "&#x1D4A9;" ><!--/scr N, script letter N -->
+<!ENTITY oscr             "&#x1D4C4;" ><!--/scr o, script letter o -->
+<!ENTITY Oscr             "&#x1D4AA;" ><!--/scr O, script letter O -->
+<!ENTITY pscr             "&#x1D4C5;" ><!--/scr p, script letter p -->
+<!ENTITY Pscr             "&#x1D4AB;" ><!--/scr P, script letter P -->
+<!ENTITY qscr             "&#x1D4C6;" ><!--/scr q, script letter q -->
+<!ENTITY Qscr             "&#x1D4AC;" ><!--/scr Q, script letter Q -->
+<!ENTITY rscr             "&#x1D4C7;" ><!--/scr r, script letter r -->
+<!ENTITY Rscr             "&#x1D4AD;" ><!--/scr R, script letter R -->
+<!ENTITY sscr             "&#x1D4C8;" ><!--/scr s, script letter s -->
+<!ENTITY Sscr             "&#x1D4AE;" ><!--/scr S, script letter S -->
+<!ENTITY tscr             "&#x1D4C9;" ><!--/scr t, script letter t -->
+<!ENTITY Tscr             "&#x1D4AF;" ><!--/scr T, script letter T -->
+<!ENTITY uscr             "&#x1D4CA;" ><!--/scr u, script letter u -->
+<!ENTITY Uscr             "&#x1D4B0;" ><!--/scr U, script letter U -->
+<!ENTITY vscr             "&#x1D4CB;" ><!--/scr v, script letter v -->
+<!ENTITY Vscr             "&#x1D4B1;" ><!--/scr V, script letter V -->
+<!ENTITY wscr             "&#x1D4CC;" ><!--/scr w, script letter w -->
+<!ENTITY Wscr             "&#x1D4B2;" ><!--/scr W, script letter W -->
+<!ENTITY xscr             "&#x1D4CD;" ><!--/scr x, script letter x -->
+<!ENTITY Xscr             "&#x1D4B3;" ><!--/scr X, script letter X -->
+<!ENTITY yscr             "&#x1D4CE;" ><!--/scr y, script letter y -->
+<!ENTITY Yscr             "&#x1D4B4;" ><!--/scr Y, script letter Y -->
+<!ENTITY zscr             "&#x1D4CF;" ><!--/scr z, script letter z -->
+<!ENTITY Zscr             "&#x1D4B5;" ><!--/scr Z, script letter Z -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isonum.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isonum.ent
new file mode 100644
index 00000000000..e5a7002fb49
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isonum.ent
@@ -0,0 +1,103 @@
+
+<!--
+     File isonum.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY amp              "&#x26;&#x00026;" ><!--=ampersand -->
+<!ENTITY apos             "&#x00027;" ><!--=apostrophe -->
+<!ENTITY ast              "&#x0002A;" ><!--/ast B: =asterisk -->
+<!ENTITY brvbar           "&#x000A6;" ><!--=broken (vertical) bar -->
+<!ENTITY bsol             "&#x0005C;" ><!--/backslash =reverse solidus -->
+<!ENTITY cent             "&#x000A2;" ><!--=cent sign -->
+<!ENTITY colon            "&#x0003A;" ><!--/colon P: -->
+<!ENTITY comma            "&#x0002C;" ><!--P: =comma -->
+<!ENTITY commat           "&#x00040;" ><!--=commercial at -->
+<!ENTITY copy             "&#x000A9;" ><!--=copyright sign -->
+<!ENTITY curren           "&#x000A4;" ><!--=general currency sign -->
+<!ENTITY darr             "&#x02193;" ><!--/downarrow A: =downward arrow -->
+<!ENTITY deg              "&#x000B0;" ><!--=degree sign -->
+<!ENTITY divide           "&#x000F7;" ><!--/div B: =divide sign -->
+<!ENTITY dollar           "&#x00024;" ><!--=dollar sign -->
+<!ENTITY equals           "&#x0003D;" ><!--=equals sign R: -->
+<!ENTITY excl             "&#x00021;" ><!--=exclamation mark -->
+<!ENTITY frac12           "&#x000BD;" ><!--=fraction one-half -->
+<!ENTITY frac14           "&#x000BC;" ><!--=fraction one-quarter -->
+<!ENTITY frac18           "&#x0215B;" ><!--=fraction one-eighth -->
+<!ENTITY frac34           "&#x000BE;" ><!--=fraction three-quarters -->
+<!ENTITY frac38           "&#x0215C;" ><!--=fraction three-eighths -->
+<!ENTITY frac58           "&#x0215D;" ><!--=fraction five-eighths -->
+<!ENTITY frac78           "&#x0215E;" ><!--=fraction seven-eighths -->
+<!ENTITY gt               "&#x0003E;" ><!--=greater-than sign R: -->
+<!ENTITY half             "&#x000BD;" ><!--=fraction one-half -->
+<!ENTITY horbar           "&#x02015;" ><!--=horizontal bar -->
+<!ENTITY hyphen           "&#x02010;" ><!--=hyphen -->
+<!ENTITY iexcl            "&#x000A1;" ><!--=inverted exclamation mark -->
+<!ENTITY iquest           "&#x000BF;" ><!--=inverted question mark -->
+<!ENTITY laquo            "&#x000AB;" ><!--=angle quotation mark, left -->
+<!ENTITY larr             "&#x02190;" ><!--/leftarrow /gets A: =leftward arrow -->
+<!ENTITY lcub             "&#x0007B;" ><!--/lbrace O: =left curly bracket -->
+<!ENTITY ldquo            "&#x0201C;" ><!--=double quotation mark, left -->
+<!ENTITY lowbar           "&#x0005F;" ><!--=low line -->
+<!ENTITY lpar             "&#x00028;" ><!--O: =left parenthesis -->
+<!ENTITY lsqb             "&#x0005B;" ><!--/lbrack O: =left square bracket -->
+<!ENTITY lsquo            "&#x02018;" ><!--=single quotation mark, left -->
+<!ENTITY lt               "&#x26;&#x0003C;" ><!--=less-than sign R: -->
+<!ENTITY micro            "&#x000B5;" ><!--=micro sign -->
+<!ENTITY middot           "&#x000B7;" ><!--/centerdot B: =middle dot -->
+<!ENTITY nbsp             "&#x000A0;" ><!--=no break (required) space -->
+<!ENTITY not              "&#x000AC;" ><!--/neg /lnot =not sign -->
+<!ENTITY num              "&#x00023;" ><!--=number sign -->
+<!ENTITY ohm              "&#x02126;" ><!--=ohm sign -->
+<!ENTITY ordf             "&#x000AA;" ><!--=ordinal indicator, feminine -->
+<!ENTITY ordm             "&#x000BA;" ><!--=ordinal indicator, masculine -->
+<!ENTITY para             "&#x000B6;" ><!--=pilcrow (paragraph sign) -->
+<!ENTITY percnt           "&#x00025;" ><!--=percent sign -->
+<!ENTITY period           "&#x0002E;" ><!--=full stop, period -->
+<!ENTITY plus             "&#x0002B;" ><!--=plus sign B: -->
+<!ENTITY plusmn           "&#x000B1;" ><!--/pm B: =plus-or-minus sign -->
+<!ENTITY pound            "&#x000A3;" ><!--=pound sign -->
+<!ENTITY quest            "&#x0003F;" ><!--=question mark -->
+<!ENTITY quot             "&#x00022;" ><!--=quotation mark -->
+<!ENTITY raquo            "&#x000BB;" ><!--=angle quotation mark, right -->
+<!ENTITY rarr             "&#x02192;" ><!--/rightarrow /to A: =rightward arrow -->
+<!ENTITY rcub             "&#x0007D;" ><!--/rbrace C: =right curly bracket -->
+<!ENTITY rdquo            "&#x0201D;" ><!--=double quotation mark, right -->
+<!ENTITY reg              "&#x000AE;" ><!--/circledR =registered sign -->
+<!ENTITY rpar             "&#x00029;" ><!--C: =right parenthesis -->
+<!ENTITY rsqb             "&#x0005D;" ><!--/rbrack C: =right square bracket -->
+<!ENTITY rsquo            "&#x02019;" ><!--=single quotation mark, right -->
+<!ENTITY sect             "&#x000A7;" ><!--=section sign -->
+<!ENTITY semi             "&#x0003B;" ><!--=semicolon P: -->
+<!ENTITY shy              "&#x000AD;" ><!--=soft hyphen -->
+<!ENTITY sol              "&#x0002F;" ><!--=solidus -->
+<!ENTITY sung             "&#x0266A;" ><!--=music note (sung text sign) -->
+<!ENTITY sup1             "&#x000B9;" ><!--=superscript one -->
+<!ENTITY sup2             "&#x000B2;" ><!--=superscript two -->
+<!ENTITY sup3             "&#x000B3;" ><!--=superscript three -->
+<!ENTITY times            "&#x000D7;" ><!--/times B: =multiply sign -->
+<!ENTITY trade            "&#x02122;" ><!--=trade mark sign -->
+<!ENTITY uarr             "&#x02191;" ><!--/uparrow A: =upward arrow -->
+<!ENTITY verbar           "&#x0007C;" ><!--/vert =vertical bar -->
+<!ENTITY yen              "&#x000A5;" ><!--/yen =yen sign -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isopub.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isopub.ent
new file mode 100644
index 00000000000..5591fc390e3
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isopub.ent
@@ -0,0 +1,111 @@
+
+<!--
+     File isopub.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1986
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY blank            "&#x02423;" ><!--=significant blank symbol -->
+<!ENTITY blk12            "&#x02592;" ><!--=50% shaded block -->
+<!ENTITY blk14            "&#x02591;" ><!--=25% shaded block -->
+<!ENTITY blk34            "&#x02593;" ><!--=75% shaded block -->
+<!ENTITY block            "&#x02588;" ><!--=full block -->
+<!ENTITY bull             "&#x02022;" ><!--/bullet B: =round bullet, filled -->
+<!ENTITY caret            "&#x02041;" ><!--=caret (insertion mark) -->
+<!ENTITY check            "&#x02713;" ><!--/checkmark =tick, check mark -->
+<!ENTITY cir              "&#x025CB;" ><!--/circ B: =circle, open -->
+<!ENTITY clubs            "&#x02663;" ><!--/clubsuit =club suit symbol  -->
+<!ENTITY copysr           "&#x02117;" ><!--=sound recording copyright sign -->
+<!ENTITY cross            "&#x02717;" ><!--=ballot cross -->
+<!ENTITY dagger           "&#x02020;" ><!--/dagger B: =dagger -->
+<!ENTITY Dagger           "&#x02021;" ><!--/ddagger B: =double dagger -->
+<!ENTITY dash             "&#x02010;" ><!--=hyphen (true graphic) -->
+<!ENTITY diams            "&#x02666;" ><!--/diamondsuit =diamond suit symbol  -->
+<!ENTITY dlcrop           "&#x0230D;" ><!--downward left crop mark  -->
+<!ENTITY drcrop           "&#x0230C;" ><!--downward right crop mark  -->
+<!ENTITY dtri             "&#x025BF;" ><!--/triangledown =down triangle, open -->
+<!ENTITY dtrif            "&#x025BE;" ><!--/blacktriangledown =dn tri, filled -->
+<!ENTITY emsp             "&#x02003;" ><!--=em space -->
+<!ENTITY emsp13           "&#x02004;" ><!--=1/3-em space -->
+<!ENTITY emsp14           "&#x02005;" ><!--=1/4-em space -->
+<!ENTITY ensp             "&#x02002;" ><!--=en space (1/2-em) -->
+<!ENTITY female           "&#x02640;" ><!--=female symbol -->
+<!ENTITY ffilig           "&#x0FB03;" ><!--small ffi ligature -->
+<!ENTITY fflig            "&#x0FB00;" ><!--small ff ligature -->
+<!ENTITY ffllig           "&#x0FB04;" ><!--small ffl ligature -->
+<!ENTITY filig            "&#x0FB01;" ><!--small fi ligature -->
+<!ENTITY flat             "&#x0266D;" ><!--/flat =musical flat -->
+<!ENTITY fllig            "&#x0FB02;" ><!--small fl ligature -->
+<!ENTITY frac13           "&#x02153;" ><!--=fraction one-third -->
+<!ENTITY frac15           "&#x02155;" ><!--=fraction one-fifth -->
+<!ENTITY frac16           "&#x02159;" ><!--=fraction one-sixth -->
+<!ENTITY frac23           "&#x02154;" ><!--=fraction two-thirds -->
+<!ENTITY frac25           "&#x02156;" ><!--=fraction two-fifths -->
+<!ENTITY frac35           "&#x02157;" ><!--=fraction three-fifths -->
+<!ENTITY frac45           "&#x02158;" ><!--=fraction four-fifths -->
+<!ENTITY frac56           "&#x0215A;" ><!--=fraction five-sixths -->
+<!ENTITY hairsp           "&#x0200A;" ><!--=hair space -->
+<!ENTITY hearts           "&#x02661;" ><!--/heartsuit =heart suit symbol  -->
+<!ENTITY hellip           "&#x02026;" ><!--=ellipsis (horizontal) -->
+<!ENTITY hybull           "&#x02043;" ><!--rectangle, filled (hyphen bullet) -->
+<!ENTITY incare           "&#x02105;" ><!--=in-care-of symbol -->
+<!ENTITY ldquor           "&#x0201E;" ><!--=rising dbl quote, left (low) -->
+<!ENTITY lhblk            "&#x02584;" ><!--=lower half block -->
+<!ENTITY loz              "&#x025CA;" ><!--/lozenge - lozenge or total mark -->
+<!ENTITY lozf             "&#x029EB;" ><!--/blacklozenge - lozenge, filled -->
+<!ENTITY lsquor           "&#x0201A;" ><!--=rising single quote, left (low) -->
+<!ENTITY ltri             "&#x025C3;" ><!--/triangleleft B: l triangle, open -->
+<!ENTITY ltrif            "&#x025C2;" ><!--/blacktriangleleft R: =l tri, filled -->
+<!ENTITY male             "&#x02642;" ><!--=male symbol -->
+<!ENTITY malt             "&#x02720;" ><!--/maltese =maltese cross -->
+<!ENTITY marker           "&#x025AE;" ><!--=histogram marker -->
+<!ENTITY mdash            "&#x02014;" ><!--=em dash  -->
+<!ENTITY mldr             "&#x02026;" ><!--em leader -->
+<!ENTITY natur            "&#x0266E;" ><!--/natural - music natural -->
+<!ENTITY ndash            "&#x02013;" ><!--=en dash -->
+<!ENTITY nldr             "&#x02025;" ><!--=double baseline dot (en leader) -->
+<!ENTITY numsp            "&#x02007;" ><!--=digit space (width of a number) -->
+<!ENTITY phone            "&#x0260E;" ><!--=telephone symbol  -->
+<!ENTITY puncsp           "&#x02008;" ><!--=punctuation space (width of comma) -->
+<!ENTITY rdquor           "&#x0201D;" ><!--rising dbl quote, right (high) -->
+<!ENTITY rect             "&#x025AD;" ><!--=rectangle, open -->
+<!ENTITY rsquor           "&#x02019;" ><!--rising single quote, right (high) -->
+<!ENTITY rtri             "&#x025B9;" ><!--/triangleright B: r triangle, open -->
+<!ENTITY rtrif            "&#x025B8;" ><!--/blacktriangleright R: =r tri, filled -->
+<!ENTITY rx               "&#x0211E;" ><!--pharmaceutical prescription (Rx) -->
+<!ENTITY sext             "&#x02736;" ><!--sextile (6-pointed star) -->
+<!ENTITY sharp            "&#x0266F;" ><!--/sharp =musical sharp -->
+<!ENTITY spades           "&#x02660;" ><!--/spadesuit =spades suit symbol  -->
+<!ENTITY squ              "&#x025A1;" ><!--=square, open -->
+<!ENTITY squf             "&#x025AA;" ><!--/blacksquare =sq bullet, filled -->
+<!ENTITY star             "&#x022C6;" ><!--=star, open -->
+<!ENTITY starf            "&#x02605;" ><!--/bigstar - star, filled  -->
+<!ENTITY target           "&#x02316;" ><!--register mark or target -->
+<!ENTITY telrec           "&#x02315;" ><!--=telephone recorder symbol -->
+<!ENTITY thinsp           "&#x02009;" ><!--=thin space (1/6-em) -->
+<!ENTITY uhblk            "&#x02580;" ><!--=upper half block -->
+<!ENTITY ulcrop           "&#x0230F;" ><!--upward left crop mark  -->
+<!ENTITY urcrop           "&#x0230E;" ><!--upward right crop mark  -->
+<!ENTITY utri             "&#x025B5;" ><!--/triangle =up triangle, open -->
+<!ENTITY utrif            "&#x025B4;" ><!--/blacktriangle =up tri, filled -->
+<!ENTITY vellip           "&#x022EE;" ><!--vertical ellipsis -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isotech.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isotech.ent
new file mode 100644
index 00000000000..dc1fc013540
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/isotech.ent
@@ -0,0 +1,183 @@
+
+<!--
+     File isotech.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+     Entity names in this file are derived from files carrying the
+     following notice:
+
+     (C) International Organization for Standardization 1991
+     Permission to copy in any form is granted for use with
+     conforming SGML systems and applications as defined in
+     ISO 8879, provided this notice is included in all copies.
+
+-->
+
+<!ENTITY acd              "&#x0223F;" ><!--ac current -->
+<!ENTITY aleph            "&#x02135;" ><!--/aleph aleph, Hebrew -->
+<!ENTITY and              "&#x02227;" ><!--/wedge /land B: logical and -->
+<!ENTITY And              "&#x02A53;" ><!--dbl logical and -->
+<!ENTITY andand           "&#x02A55;" ><!--two logical and -->
+<!ENTITY andd             "&#x02A5C;" ><!--and, horizontal dash -->
+<!ENTITY andslope         "&#x02A58;" ><!--sloping large and -->
+<!ENTITY andv             "&#x02A5A;" ><!--and with middle stem -->
+<!ENTITY angrt            "&#x0221F;" ><!--right (90 degree) angle -->
+<!ENTITY angsph           "&#x02222;" ><!--/sphericalangle angle-spherical -->
+<!ENTITY angst            "&#x0212B;" ><!--Angstrom capital A, ring -->
+<!ENTITY ap               "&#x02248;" ><!--/approx R: approximate -->
+<!ENTITY apacir           "&#x02A6F;" ><!--approximate, circumflex accent -->
+<!ENTITY awconint         "&#x02233;" ><!--contour integral, anti-clockwise -->
+<!ENTITY awint            "&#x02A11;" ><!--anti clock-wise integration -->
+<!ENTITY becaus           "&#x02235;" ><!--/because R: because -->
+<!ENTITY bernou           "&#x0212C;" ><!--Bernoulli function (script capital B)  -->
+<!ENTITY bne              "&#x0003D;&#x020E5;" ><!--reverse not equal -->
+<!ENTITY bnequiv          "&#x02261;&#x020E5;" ><!--reverse not equivalent -->
+<!ENTITY bnot             "&#x02310;" ><!--reverse not -->
+<!ENTITY bNot             "&#x02AED;" ><!--reverse not with two horizontal strokes -->
+<!ENTITY bottom           "&#x022A5;" ><!--/bot bottom -->
+<!ENTITY cap              "&#x02229;" ><!--/cap B: intersection -->
+<!ENTITY Cconint          "&#x02230;" ><!--triple contour integral operator -->
+<!ENTITY cirfnint         "&#x02A10;" ><!--circulation function -->
+<!ENTITY compfn           "&#x02218;" ><!--/circ B: composite function (small circle) -->
+<!ENTITY cong             "&#x02245;" ><!--/cong R: congruent with -->
+<!ENTITY conint           "&#x0222E;" ><!--/oint L: contour integral operator -->
+<!ENTITY Conint           "&#x0222F;" ><!--double contour integral operator -->
+<!ENTITY ctdot            "&#x022EF;" ><!--/cdots, three dots, centered -->
+<!ENTITY cup              "&#x0222A;" ><!--/cup B: union or logical sum -->
+<!ENTITY cwconint         "&#x02232;" ><!--contour integral, clockwise -->
+<!ENTITY cwint            "&#x02231;" ><!--clockwise integral -->
+<!ENTITY cylcty           "&#x0232D;" ><!--cylindricity -->
+<!ENTITY disin            "&#x022F2;" ><!--set membership, long horizontal stroke -->
+<!ENTITY Dot              "&#x000A8;" ><!--dieresis or umlaut mark -->
+<!ENTITY DotDot           "&#x020DC;" ><!--four dots above -->
+<!ENTITY dsol             "&#x02052;" ><!--solidus, bar above -->
+<!ENTITY dtdot            "&#x022F1;" ><!--/ddots, three dots, descending -->
+<!ENTITY dwangle          "&#x029A6;" ><!--large downward pointing angle -->
+<!ENTITY epar             "&#x022D5;" ><!--parallel, equal; equal or parallel -->
+<!ENTITY eparsl           "&#x029E3;" ><!--parallel, slanted, equal; homothetically congruent to -->
+<!ENTITY equiv            "&#x02261;" ><!--/equiv R: identical with -->
+<!ENTITY eqvparsl         "&#x029E5;" ><!--equivalent, equal; congruent and parallel -->
+<!ENTITY exist            "&#x02203;" ><!--/exists at least one exists -->
+<!ENTITY fnof             "&#x00192;" ><!--function of (italic small f) -->
+<!ENTITY forall           "&#x02200;" ><!--/forall for all -->
+<!ENTITY fpartint         "&#x02A0D;" ><!--finite part integral -->
+<!ENTITY ge               "&#x02265;" ><!--/geq /ge R: greater-than-or-equal -->
+<!ENTITY hamilt           "&#x0210B;" ><!--Hamiltonian (script capital H)  -->
+<!ENTITY iff              "&#x021D4;" ><!--/iff if and only if  -->
+<!ENTITY iinfin           "&#x029DC;" ><!--infinity sign, incomplete -->
+<!ENTITY imped            "&#x1D543;" ><!--impedance -->
+<!ENTITY infin            "&#x0221E;" ><!--/infty infinity -->
+<!ENTITY int              "&#x0222B;" ><!--/int L: integral operator -->
+<!ENTITY Int              "&#x0222C;" ><!--double integral operator -->
+<!ENTITY intlarhk         "&#x02A17;" ><!--integral, left arrow with hook -->
+<!ENTITY isin             "&#x02208;" ><!--/in R: set membership  -->
+<!ENTITY isindot          "&#x022F5;" ><!--set membership, dot above -->
+<!ENTITY isinE            "&#x022F9;" ><!--set membership, two horizontal strokes -->
+<!ENTITY isins            "&#x022F4;" ><!--set membership, vertical bar on horizontal stroke -->
+<!ENTITY isinsv           "&#x022F3;" ><!--large set membership, vertical bar on horizontal stroke -->
+<!ENTITY isinv            "&#x02208;" ><!--set membership, variant -->
+<!ENTITY lagran           "&#x02112;" ><!--Lagrangian (script capital L)  -->
+<!ENTITY lang             "&#x03008;" ><!--/langle O: left angle bracket -->
+<!ENTITY Lang             "&#x0300A;" ><!--left angle bracket, double -->
+<!ENTITY lArr             "&#x021D0;" ><!--/Leftarrow A: is implied by -->
+<!ENTITY lbbrk            "&#x03014;" ><!--left broken bracket -->
+<!ENTITY le               "&#x02264;" ><!--/leq /le R: less-than-or-equal -->
+<!ENTITY loang            "&#x03018;" ><!--left open angular bracket -->
+<!ENTITY lobrk            "&#x0301A;" ><!--left open bracket -->
+<!ENTITY lopar            "&#x02985;" ><!--left open parenthesis -->
+<!ENTITY lowast           "&#x02217;" ><!--low asterisk -->
+<!ENTITY minus            "&#x02212;" ><!--B: minus sign -->
+<!ENTITY mnplus           "&#x02213;" ><!--/mp B: minus-or-plus sign -->
+<!ENTITY nabla            "&#x02207;" ><!--/nabla del, Hamilton operator -->
+<!ENTITY ne               "&#x02260;" ><!--/ne /neq R: not equal -->
+<!ENTITY nedot            "&#x02260;&#x02063;" ><!--not equal, dot -->
+<!ENTITY nhpar            "&#x02AF2;" ><!--not, horizontal, parallel -->
+<!ENTITY ni               "&#x0220B;" ><!--/ni /owns R: contains -->
+<!ENTITY nis              "&#x022FC;" ><!--contains, vertical bar on horizontal stroke -->
+<!ENTITY nisd             "&#x022FA;" ><!--contains, long horizontal stroke -->
+<!ENTITY niv              "&#x0220B;" ><!--contains, variant -->
+<!ENTITY Not              "&#x02AEC;" ><!--not with two horizontal strokes -->
+<!ENTITY notin            "&#x02209;" ><!--/notin N: negated set membership -->
+<!ENTITY notindot         "&#x022F6;&#x02063;" ><!--negated set membership, dot above -->
+<!ENTITY notinva          "&#x02209;&#x00338;" ><!--negated set membership, variant -->
+<!ENTITY notinvb          "&#x022F7;" ><!--negated set membership, variant -->
+<!ENTITY notinvc          "&#x022F6;" ><!--negated set membership, variant -->
+<!ENTITY notni            "&#x0220C;" ><!--negated contains -->
+<!ENTITY notniva          "&#x0220C;" ><!--negated contains, variant -->
+<!ENTITY notnivb          "&#x022FE;" ><!--contains, variant -->
+<!ENTITY notnivc          "&#x022FD;" ><!--contains, variant -->
+<!ENTITY nparsl           "&#x02225;&#x02063;&#x020E5;" ><!--not parallel, slanted -->
+<!ENTITY npart            "&#x02202;&#x00338;" ><!--not partial differential -->
+<!ENTITY npolint          "&#x02A14;" ><!--line integration, not including the pole -->
+<!ENTITY nvinfin          "&#x029DE;" ><!--not, vert, infinity -->
+<!ENTITY olcross          "&#x029BB;" ><!--circle, cross -->
+<!ENTITY or               "&#x02228;" ><!--/vee /lor B: logical or -->
+<!ENTITY Or               "&#x02A54;" ><!--dbl logical or -->
+<!ENTITY ord              "&#x02A5D;" ><!--or, horizontal dash -->
+<!ENTITY order            "&#x02134;" ><!--order of (script small o)  -->
+<!ENTITY oror             "&#x02A56;" ><!--two logical or -->
+<!ENTITY orslope          "&#x02A57;" ><!--sloping large or -->
+<!ENTITY orv              "&#x02A5B;" ><!--or with middle stem -->
+<!ENTITY par              "&#x02225;" ><!--/parallel R: parallel -->
+<!ENTITY parsl            "&#x02225;&#x02063;" ><!--parallel, slanted -->
+<!ENTITY part             "&#x02202;" ><!--/partial partial differential -->
+<!ENTITY permil           "&#x02030;" ><!--per thousand -->
+<!ENTITY perp             "&#x022A5;" ><!--/perp R: perpendicular -->
+<!ENTITY pertenk          "&#x02031;" ><!--per 10 thousand -->
+<!ENTITY phmmat           "&#x02133;" ><!--physics M-matrix (script capital M)  -->
+<!ENTITY pointint         "&#x02A15;" ><!--integral around a point operator -->
+<!ENTITY prime            "&#x02032;" ><!--/prime prime or minute -->
+<!ENTITY Prime            "&#x02033;" ><!--double prime or second -->
+<!ENTITY profalar         "&#x0232E;" ><!--all-around profile -->
+<!ENTITY profline         "&#x02312;" ><!--profile of a line -->
+<!ENTITY profsurf         "&#x02313;" ><!--profile of a surface -->
+<!ENTITY prop             "&#x0221D;" ><!--/propto R: is proportional to -->
+<!ENTITY qint             "&#x02A0C;" ><!--/iiiint quadruple integral operator -->
+<!ENTITY qprime           "&#x02057;" ><!--quadruple prime -->
+<!ENTITY quatint          "&#x02A16;" ><!--quaternion integral operator -->
+<!ENTITY radic            "&#x0221A;" ><!--/surd radical -->
+<!ENTITY rang             "&#x03009;" ><!--/rangle C: right angle bracket -->
+<!ENTITY Rang             "&#x0300B;" ><!--right angle bracket, double -->
+<!ENTITY rArr             "&#x021D2;" ><!--/Rightarrow A: implies -->
+<!ENTITY rbbrk            "&#x03015;" ><!--right broken bracket -->
+<!ENTITY roang            "&#x03019;" ><!--right open angular bracket -->
+<!ENTITY robrk            "&#x0301B;" ><!--right open bracket -->
+<!ENTITY ropar            "&#x02986;" ><!--right open parenthesis -->
+<!ENTITY rppolint         "&#x02A12;" ><!--line integration, rectangular path around pole -->
+<!ENTITY scpolint         "&#x02A13;" ><!--line integration, semi-circular path around pole -->
+<!ENTITY sim              "&#x0223C;" ><!--/sim R: similar -->
+<!ENTITY simdot           "&#x02A6A;" ><!--similar, dot -->
+<!ENTITY sime             "&#x02243;" ><!--/simeq R: similar, equals -->
+<!ENTITY smeparsl         "&#x029E4;" ><!--similar, parallel, slanted, equal -->
+<!ENTITY square           "&#x025A1;" ><!--/square, square -->
+<!ENTITY squarf           "&#x025AA;" ><!--/blacksquare, square, filled  -->
+<!ENTITY sub              "&#x02282;" ><!--/subset R: subset or is implied by -->
+<!ENTITY sube             "&#x02286;" ><!--/subseteq R: subset, equals -->
+<!ENTITY sup              "&#x02283;" ><!--/supset R: superset or implies -->
+<!ENTITY supe             "&#x02287;" ><!--/supseteq R: superset, equals -->
+<!ENTITY tdot             "&#x020DB;" ><!--three dots above -->
+<!ENTITY there4           "&#x02234;" ><!--/therefore R: therefore -->
+<!ENTITY tint             "&#x0222D;" ><!--/iiint triple integral operator -->
+<!ENTITY top              "&#x022A4;" ><!--/top top -->
+<!ENTITY topbot           "&#x02336;" ><!--top and bottom -->
+<!ENTITY topcir           "&#x02AF1;" ><!--top, circle below -->
+<!ENTITY tprime           "&#x02034;" ><!--triple prime -->
+<!ENTITY utdot            "&#x022F0;" ><!--three dots, ascending -->
+<!ENTITY uwangle          "&#x029A7;" ><!--large upward pointing angle -->
+<!ENTITY vangrt           "&#x022BE;" ><!--right angle, variant -->
+<!ENTITY veeeq            "&#x0225A;" ><!--logical or, equals -->
+<!ENTITY Verbar           "&#x02016;" ><!--/Vert dbl vertical bar -->
+<!ENTITY wedgeq           "&#x02259;" ><!--/wedgeq R: corresponds to (wedge, equals) -->
+<!ENTITY xnis             "&#x022FB;" ><!--large contains, vertical bar on horizontal stroke -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/mmlalias.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/mmlalias.ent
new file mode 100644
index 00000000000..f5901b3846a
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/mmlalias.ent
@@ -0,0 +1,529 @@
+
+<!--
+     File mmlalias.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+-->
+
+<!ENTITY angle            "&#x02220;" ><!--alias ISOAMSO ang -->
+<!ENTITY approx           "&#x02248;" ><!--alias ISOTECH ap -->
+<!ENTITY approxeq         "&#x0224A;" ><!--alias ISOAMSR ape -->
+<!ENTITY backcong         "&#x0224C;" ><!--alias ISOAMSR bcong -->
+<!ENTITY backepsilon      "&#x0213C;" ><!--alias ISOAMSR bepsi -->
+<!ENTITY backprime        "&#x02035;" ><!--alias ISOAMSO bprime -->
+<!ENTITY backsim          "&#x0223D;" ><!--alias ISOAMSR bsim -->
+<!ENTITY backsimeq        "&#x022CD;" ><!--alias ISOAMSR bsime -->
+<!ENTITY Backslash        "&#x02216;" ><!--alias ISOAMSB setmn -->
+<!ENTITY barwedge         "&#x022BC;" ><!--alias ISOAMSB barwed -->
+<!ENTITY because          "&#x02235;" ><!--alias ISOTECH becaus -->
+<!ENTITY Because          "&#x02235;" ><!--alias ISOTECH becaus -->
+<!ENTITY Bernoullis       "&#x0212C;" ><!--alias ISOTECH bernou -->
+<!ENTITY between          "&#x0226C;" ><!--alias ISOAMSR twixt -->
+<!ENTITY bigcap           "&#x022C2;" ><!--alias ISOAMSB xcap -->
+<!ENTITY bigcirc          "&#x025EF;" ><!--alias ISOAMSB xcirc -->
+<!ENTITY bigcup           "&#x022C3;" ><!--alias ISOAMSB xcup -->
+<!ENTITY bigodot          "&#x02299;" ><!--alias ISOAMSB xodot -->
+<!ENTITY bigoplus         "&#x02295;" ><!--alias ISOAMSB xoplus -->
+<!ENTITY bigotimes        "&#x02297;" ><!--alias ISOAMSB xotime -->
+<!ENTITY bigsqcup         "&#x02294;" ><!--alias ISOAMSB xsqcup -->
+<!ENTITY bigstar          "&#x02605;" ><!--ISOPUB    starf  -->
+<!ENTITY bigtriangledown  "&#x025BD;" ><!--alias ISOAMSB xdtri -->
+<!ENTITY bigtriangleup    "&#x025B3;" ><!--alias ISOAMSB xutri -->
+<!ENTITY biguplus         "&#x0228E;" ><!--alias ISOAMSB xuplus -->
+<!ENTITY bigvee           "&#x022C1;" ><!--alias ISOAMSB xvee -->
+<!ENTITY bigwedge         "&#x022C0;" ><!--alias ISOAMSB xwedge -->
+<!ENTITY bkarow           "&#x0290D;" ><!--alias ISOAMSA rbarr -->
+<!ENTITY blacklozenge     "&#x029EB;" ><!--alias ISOPUB lozf -->
+<!ENTITY blacksquare      "&#x025AA;" ><!--ISOTECH  squarf  -->
+<!ENTITY blacktriangle    "&#x025B4;" ><!--alias ISOPUB utrif -->
+<!ENTITY blacktriangledown "&#x025BE;" ><!--alias ISOPUB dtrif -->
+<!ENTITY blacktriangleleft "&#x025C2;" ><!--alias ISOPUB ltrif -->
+<!ENTITY blacktriangleright "&#x025B8;" ><!--alias ISOPUB rtrif -->
+<!ENTITY bot              "&#x022A5;" ><!--alias ISOTECH bottom -->
+<!ENTITY boxminus         "&#x0229F;" ><!--alias ISOAMSB minusb -->
+<!ENTITY boxplus          "&#x0229E;" ><!--alias ISOAMSB plusb -->
+<!ENTITY boxtimes         "&#x022A0;" ><!--alias ISOAMSB timesb -->
+<!ENTITY Breve            "&#x002D8;" ><!--alias ISODIA breve -->
+<!ENTITY bullet           "&#x02022;" ><!--alias ISOPUB bull -->
+<!ENTITY bumpeq           "&#x0224F;" ><!--alias ISOAMSR bumpe -->
+<!ENTITY Bumpeq           "&#x0224E;" ><!--alias ISOAMSR bump -->
+<!ENTITY Cedilla          "&#x000B8;" ><!--alias ISODIA cedil -->
+<!ENTITY centerdot        "&#x000B7;" ><!--alias ISONUM middot -->
+<!ENTITY CenterDot        "&#x000B7;" ><!--alias ISONUM middot -->
+<!ENTITY checkmark        "&#x02713;" ><!--alias ISOPUB check -->
+<!ENTITY circeq           "&#x02257;" ><!--alias ISOAMSR cire -->
+<!ENTITY circlearrowleft  "&#x021BA;" ><!--alias ISOAMSA olarr -->
+<!ENTITY circlearrowright "&#x021BB;" ><!--alias ISOAMSA orarr -->
+<!ENTITY circledast       "&#x0229B;" ><!--alias ISOAMSB oast -->
+<!ENTITY circledcirc      "&#x0229A;" ><!--alias ISOAMSB ocir -->
+<!ENTITY circleddash      "&#x0229D;" ><!--alias ISOAMSB odash -->
+<!ENTITY CircleDot        "&#x02299;" ><!--alias ISOAMSB odot -->
+<!ENTITY circledR         "&#x000AE;" ><!--alias ISONUM reg -->
+<!ENTITY circledS         "&#x024C8;" ><!--alias ISOAMSO oS -->
+<!ENTITY CircleMinus      "&#x02296;" ><!--alias ISOAMSB ominus -->
+<!ENTITY CirclePlus       "&#x02295;" ><!--alias ISOAMSB oplus -->
+<!ENTITY CircleTimes      "&#x02297;" ><!--alias ISOAMSB otimes -->
+<!ENTITY ClockwiseContourIntegral "&#x02232;" ><!--alias ISOTECH cwconint -->
+<!ENTITY CloseCurlyDoubleQuote "&#x0201D;" ><!--alias ISONUM rdquo -->
+<!ENTITY CloseCurlyQuote  "&#x02019;" ><!--alias ISONUM rsquo -->
+<!ENTITY clubsuit         "&#x02663;" ><!--ISOPUB    clubs  -->
+<!ENTITY coloneq          "&#x02254;" ><!--alias ISOAMSR colone -->
+<!ENTITY complement       "&#x02201;" ><!--alias ISOAMSO comp -->
+<!ENTITY Congruent        "&#x02261;" ><!--alias ISOTECH equiv -->
+<!ENTITY ContourIntegral  "&#x0222E;" ><!--alias ISOTECH conint -->
+<!ENTITY Coproduct        "&#x02210;" ><!--alias ISOAMSB coprod -->
+<!ENTITY CounterClockwiseContourIntegral "&#x02233;" ><!--alias ISOTECH awconint -->
+<!ENTITY CupCap           "&#x0224D;" ><!--alias ISOAMSR asymp -->
+<!ENTITY curlyeqprec      "&#x022DE;" ><!--alias ISOAMSR cuepr -->
+<!ENTITY curlyeqsucc      "&#x022DF;" ><!--alias ISOAMSR cuesc -->
+<!ENTITY curlyvee         "&#x022CE;" ><!--alias ISOAMSB cuvee -->
+<!ENTITY curlywedge       "&#x022CF;" ><!--alias ISOAMSB cuwed -->
+<!ENTITY curvearrowleft   "&#x021B6;" ><!--alias ISOAMSA cularr -->
+<!ENTITY curvearrowright  "&#x021B7;" ><!--alias ISOAMSA curarr -->
+<!ENTITY dbkarow          "&#x0290F;" ><!--alias ISOAMSA rBarr -->
+<!ENTITY ddagger          "&#x02021;" ><!--alias ISOPUB Dagger -->
+<!ENTITY ddotseq          "&#x02A77;" ><!--alias ISOAMSR eDDot -->
+<!ENTITY Del              "&#x02207;" ><!--alias ISOTECH nabla -->
+<!ENTITY DiacriticalAcute "&#x000B4;" ><!--alias ISODIA acute -->
+<!ENTITY DiacriticalDot   "&#x002D9;" ><!--alias ISODIA dot -->
+<!ENTITY DiacriticalDoubleAcute "&#x002DD;" ><!--alias ISODIA dblac -->
+<!ENTITY DiacriticalGrave "&#x00060;" ><!--alias ISODIA grave -->
+<!ENTITY DiacriticalTilde "&#x002DC;" ><!--alias ISODIA tilde -->
+<!ENTITY diamond          "&#x022C4;" ><!--alias ISOAMSB diam -->
+<!ENTITY Diamond          "&#x022C4;" ><!--alias ISOAMSB diam -->
+<!ENTITY diamondsuit      "&#x02666;" ><!--ISOPUB    diams  -->
+<!ENTITY digamma          "&#x003DC;" ><!--alias ISOGRK3 gammad -->
+<!ENTITY div              "&#x000F7;" ><!--alias ISONUM divide -->
+<!ENTITY divideontimes    "&#x022C7;" ><!--alias ISOAMSB divonx -->
+<!ENTITY doteq            "&#x02250;" ><!--alias ISOAMSR esdot -->
+<!ENTITY doteqdot         "&#x02251;" ><!--alias ISOAMSR eDot -->
+<!ENTITY DotEqual         "&#x02250;" ><!--alias ISOAMSR esdot -->
+<!ENTITY dotminus         "&#x02238;" ><!--alias ISOAMSB minusd -->
+<!ENTITY dotplus          "&#x02214;" ><!--alias ISOAMSB plusdo -->
+<!ENTITY dotsquare        "&#x022A1;" ><!--alias ISOAMSB sdotb -->
+<!ENTITY doublebarwedge   "&#x02306;" ><!--alias ISOAMSB Barwed -->
+<!ENTITY DoubleContourIntegral "&#x0222F;" ><!--alias ISOTECH Conint -->
+<!ENTITY DoubleDot        "&#x000A8;" ><!--alias ISODIA die -->
+<!ENTITY DoubleDownArrow  "&#x021D3;" ><!--alias ISOAMSA dArr -->
+<!ENTITY DoubleLeftArrow  "&#x021D0;" ><!--alias ISOTECH lArr -->
+<!ENTITY DoubleLeftRightArrow "&#x021D4;" ><!--alias ISOAMSA hArr -->
+<!ENTITY DoubleLeftTee    "&#x02AE4;" ><!--alias for  &Dashv;  -->
+<!ENTITY DoubleLongLeftArrow "&#x021D0;" ><!--alias ISOAMSA xlArr -->
+<!ENTITY DoubleLongLeftRightArrow "&#x021D4;" ><!--alias ISOAMSA xhArr -->
+<!ENTITY DoubleLongRightArrow "&#x021D2;" ><!--alias ISOAMSA xrArr -->
+<!ENTITY DoubleRightArrow "&#x021D2;" ><!--alias ISOTECH rArr -->
+<!ENTITY DoubleRightTee   "&#x022A8;" ><!--alias ISOAMSR vDash -->
+<!ENTITY DoubleUpArrow    "&#x021D1;" ><!--alias ISOAMSA uArr -->
+<!ENTITY DoubleUpDownArrow "&#x021D5;" ><!--alias ISOAMSA vArr -->
+<!ENTITY DoubleVerticalBar "&#x02225;" ><!--alias ISOTECH par -->
+<!ENTITY downarrow        "&#x02193;" ><!--alias ISONUM darr -->
+<!ENTITY Downarrow        "&#x021D3;" ><!--alias ISOAMSA dArr -->
+<!ENTITY DownArrow        "&#x02193;" ><!--alias ISONUM darr -->
+<!ENTITY DownArrowUpArrow "&#x021F5;" ><!--alias ISOAMSA duarr -->
+<!ENTITY downdownarrows   "&#x021CA;" ><!--alias ISOAMSA ddarr -->
+<!ENTITY downharpoonleft  "&#x021C3;" ><!--alias ISOAMSA dharl -->
+<!ENTITY downharpoonright "&#x021C2;" ><!--alias ISOAMSA dharr -->
+<!ENTITY DownLeftVector   "&#x021BD;" ><!--alias ISOAMSA lhard -->
+<!ENTITY DownRightVector  "&#x021C1;" ><!--alias ISOAMSA rhard -->
+<!ENTITY DownTee          "&#x022A4;" ><!--alias ISOTECH top -->
+<!ENTITY drbkarow         "&#x02910;" ><!--alias ISOAMSA RBarr -->
+<!ENTITY Element          "&#x02208;" ><!--alias ISOTECH isinv -->
+<!ENTITY emptyset         "&#x02205;&#x02063;" ><!--alias ISOAMSO empty -->
+<!ENTITY eqcirc           "&#x02256;" ><!--alias ISOAMSR ecir -->
+<!ENTITY eqcolon          "&#x02255;" ><!--alias ISOAMSR ecolon -->
+<!ENTITY eqsim            "&#x02242;" ><!--alias ISOAMSR esim -->
+<!ENTITY eqslantgtr       "&#x022DD;" ><!--alias ISOAMSR egs -->
+<!ENTITY eqslantless      "&#x022DC;" ><!--alias ISOAMSR els -->
+<!ENTITY EqualTilde       "&#x02242;" ><!--alias ISOAMSR esim -->
+<!ENTITY Equilibrium      "&#x021CC;" ><!--alias ISOAMSA rlhar -->
+<!ENTITY Exists           "&#x02203;" ><!--alias ISOTECH exist -->
+<!ENTITY fallingdotseq    "&#x02252;" ><!--alias ISOAMSR efDot -->
+<!ENTITY ForAll           "&#x02200;" ><!--alias ISOTECH forall -->
+<!ENTITY geq              "&#x02265;" ><!--alias ISOTECH ge -->
+<!ENTITY geqq             "&#x02267;" ><!--alias ISOAMSR gE -->
+<!ENTITY geqslant         "&#x02A7E;" ><!--alias ISOAMSR ges -->
+<!ENTITY gg               "&#x0226B;" ><!--alias ISOAMSR Gt -->
+<!ENTITY ggg              "&#x022D9;" ><!--alias ISOAMSR Gg -->
+<!ENTITY gnapprox         "&#x02A8A;" ><!--alias ISOAMSN gnap -->
+<!ENTITY gneq             "&#x02269;" ><!--alias ISOAMSN gne -->
+<!ENTITY gneqq            "&#x02269;" ><!--alias ISOAMSN gnE -->
+<!ENTITY GreaterEqual     "&#x02265;" ><!--alias ISOTECH ge -->
+<!ENTITY GreaterEqualLess "&#x022DB;" ><!--alias ISOAMSR gel -->
+<!ENTITY GreaterFullEqual "&#x02267;" ><!--alias ISOAMSR gE -->
+<!ENTITY GreaterLess      "&#x02277;" ><!--alias ISOAMSR gl -->
+<!ENTITY GreaterSlantEqual "&#x02A7E;" ><!--alias ISOAMSR ges -->
+<!ENTITY GreaterTilde     "&#x02273;" ><!--alias ISOAMSR gsim -->
+<!ENTITY gtrapprox        "&#x02273;" ><!--alias ISOAMSR gap -->
+<!ENTITY gtrdot           "&#x022D7;" ><!--alias ISOAMSR gtdot -->
+<!ENTITY gtreqless        "&#x022DB;" ><!--alias ISOAMSR gel -->
+<!ENTITY gtreqqless       "&#x022DB;" ><!--alias ISOAMSR gEl -->
+<!ENTITY gtrless          "&#x02277;" ><!--alias ISOAMSR gl -->
+<!ENTITY gtrsim           "&#x02273;" ><!--alias ISOAMSR gsim -->
+<!ENTITY gvertneqq        "&#x02269;&#x00338;" ><!--alias ISOAMSN gvnE -->
+<!ENTITY Hacek            "&#x002C7;" ><!--alias ISODIA caron -->
+<!ENTITY Hat              "&#x00302;" ><!--circumflex accent (circ in ISODIA) -->
+<!ENTITY hbar             "&#x0210F;" ><!--alias ISOAMSO plank -->
+<!ENTITY heartsuit        "&#x02661;" ><!--ISOPUB    hearts  -->
+<!ENTITY hksearow         "&#x02925;" ><!--alias ISOAMSA searhk -->
+<!ENTITY hkswarow         "&#x02926;" ><!--alias ISOAMSA swarhk -->
+<!ENTITY hookleftarrow    "&#x021A9;" ><!--alias ISOAMSA larrhk -->
+<!ENTITY hookrightarrow   "&#x021AA;" ><!--alias ISOAMSA rarrhk -->
+<!ENTITY hslash           "&#x0210F;" ><!--alias ISOAMSO plankv -->
+<!ENTITY HumpDownHump     "&#x0224E;" ><!--alias ISOAMSR bump -->
+<!ENTITY HumpEqual        "&#x0224F;" ><!--alias ISOAMSR bumpe -->
+<!ENTITY iiiint           "&#x02A0C;" ><!--alias ISOTECH qint -->
+<!ENTITY iiint            "&#x0222D;" ><!--alias ISOTECH tint -->
+<!ENTITY Im               "&#x02111;" ><!--alias ISOAMSO image -->
+<!ENTITY imagpart         "&#x02111;" ><!--alias ISOAMSO image -->
+<!ENTITY Implies          "&#x021D2;" ><!--alias ISOTECH rArr -->
+<!ENTITY in               "&#x02208;" ><!--ISOTECH   isin  -->
+<!ENTITY Integral         "&#x0222B;" ><!--alias ISOTECH int -->
+<!ENTITY intercal         "&#x022BA;" ><!--alias ISOAMSB intcal -->
+<!ENTITY Intersection     "&#x022C2;" ><!--alias ISOAMSB xcap -->
+<!ENTITY intprod          "&#x02A3C;" ><!--alias ISOAMSB iprod -->
+<!ENTITY langle           "&#x03008;" ><!--alias ISOTECH lang -->
+<!ENTITY lbrace           "&#x0007B;" ><!--alias ISONUM lcub -->
+<!ENTITY lbrack           "&#x0005B;" ><!--alias ISONUM lsqb -->
+<!ENTITY LeftAngleBracket "&#x03008;" ><!--alias ISOTECH lang -->
+<!ENTITY leftarrow        "&#x02190;" ><!--alias ISONUM larr -->
+<!ENTITY Leftarrow        "&#x021D0;" ><!--alias ISOTECH lArr -->
+<!ENTITY LeftArrow        "&#x02190;" ><!--alias ISONUM larr -->
+<!ENTITY LeftArrowRightArrow "&#x021C6;" ><!--alias ISOAMSA lrarr -->
+<!ENTITY leftarrowtail    "&#x021A2;" ><!--alias ISOAMSA larrtl -->
+<!ENTITY LeftCeiling      "&#x02308;" ><!--alias ISOAMSC lceil -->
+<!ENTITY LeftDoubleBracket "&#x0301A;" ><!--left double bracket delimiter -->
+<!ENTITY LeftDownVector   "&#x021C3;" ><!--alias ISOAMSA dharl -->
+<!ENTITY LeftFloor        "&#x0230A;" ><!--alias ISOAMSC lfloor -->
+<!ENTITY leftharpoondown  "&#x021BD;" ><!--alias ISOAMSA lhard -->
+<!ENTITY leftharpoonup    "&#x021BC;" ><!--alias ISOAMSA lharu -->
+<!ENTITY leftleftarrows   "&#x021C7;" ><!--alias ISOAMSA llarr -->
+<!ENTITY leftrightarrow   "&#x02194;" ><!--alias ISOAMSA harr -->
+<!ENTITY Leftrightarrow   "&#x021D4;" ><!--alias ISOAMSA hArr -->
+<!ENTITY LeftRightArrow   "&#x02194;" ><!--alias ISOAMSA harr -->
+<!ENTITY leftrightarrows  "&#x021C6;" ><!--alias ISOAMSA lrarr -->
+<!ENTITY leftrightharpoons "&#x021CB;" ><!--alias ISOAMSA lrhar -->
+<!ENTITY leftrightsquigarrow "&#x021AD;" ><!--alias ISOAMSA harrw -->
+<!ENTITY LeftTee          "&#x022A3;" ><!--alias ISOAMSR dashv -->
+<!ENTITY leftthreetimes   "&#x022CB;" ><!--alias ISOAMSB lthree -->
+<!ENTITY LeftTriangle     "&#x022B2;" ><!--alias ISOAMSR vltri -->
+<!ENTITY LeftTriangleEqual "&#x022B4;" ><!--alias ISOAMSR ltrie -->
+<!ENTITY LeftUpVector     "&#x021BF;" ><!--alias ISOAMSA uharl -->
+<!ENTITY LeftVector       "&#x021BC;" ><!--alias ISOAMSA lharu -->
+<!ENTITY leq              "&#x02264;" ><!--alias ISOTECH le -->
+<!ENTITY leqq             "&#x02266;" ><!--alias ISOAMSR lE -->
+<!ENTITY leqslant         "&#x02A7D;" ><!--alias ISOAMSR les -->
+<!ENTITY lessapprox       "&#x02272;" ><!--alias ISOAMSR lap -->
+<!ENTITY lessdot          "&#x022D6;" ><!--alias ISOAMSR ltdot -->
+<!ENTITY lesseqgtr        "&#x022DA;" ><!--alias ISOAMSR leg -->
+<!ENTITY lesseqqgtr       "&#x022DA;" ><!--alias ISOAMSR lEg -->
+<!ENTITY LessEqualGreater "&#x022DA;" ><!--alias ISOAMSR leg -->
+<!ENTITY LessFullEqual    "&#x02266;" ><!--alias ISOAMSR lE -->
+<!ENTITY LessGreater      "&#x02276;" ><!--alias ISOAMSR lg -->
+<!ENTITY lessgtr          "&#x02276;" ><!--alias ISOAMSR lg -->
+<!ENTITY lesssim          "&#x02272;" ><!--alias ISOAMSR lsim -->
+<!ENTITY LessSlantEqual   "&#x02A7D;" ><!--alias ISOAMSR les -->
+<!ENTITY LessTilde        "&#x02272;" ><!--alias ISOAMSR lsim -->
+<!ENTITY ll               "&#x0226A;" ><!--alias ISOAMSR Lt -->
+<!ENTITY llcorner         "&#x0231E;" ><!--alias ISOAMSC dlcorn -->
+<!ENTITY Lleftarrow       "&#x021DA;" ><!--alias ISOAMSA lAarr -->
+<!ENTITY lmoustache       "&#x02998;" ><!--alias ISOAMSC lmoust -->
+<!ENTITY lnapprox         "&#x02A89;" ><!--alias ISOAMSN lnap -->
+<!ENTITY lneq             "&#x02268;" ><!--alias ISOAMSN lne -->
+<!ENTITY lneqq            "&#x02268;" ><!--alias ISOAMSN lnE -->
+<!ENTITY longleftarrow    "&#x02190;" ><!--alias ISOAMSA xlarr -->
+<!ENTITY Longleftarrow    "&#x021D0;" ><!--alias ISOAMSA xlArr -->
+<!ENTITY LongLeftArrow    "&#x02190;" ><!--alias ISOAMSA xlarr -->
+<!ENTITY longleftrightarrow "&#x02194;" ><!--alias ISOAMSA xharr -->
+<!ENTITY Longleftrightarrow "&#x021D4;" ><!--alias ISOAMSA xhArr -->
+<!ENTITY LongLeftRightArrow "&#x02194;" ><!--alias ISOAMSA xharr -->
+<!ENTITY longmapsto       "&#x021A6;" ><!--alias ISOAMSA xmap -->
+<!ENTITY longrightarrow   "&#x02192;" ><!--alias ISOAMSA xrarr -->
+<!ENTITY Longrightarrow   "&#x021D2;" ><!--alias ISOAMSA xrArr -->
+<!ENTITY LongRightArrow   "&#x02192;" ><!--alias ISOAMSA xrarr -->
+<!ENTITY looparrowleft    "&#x021AB;" ><!--alias ISOAMSA larrlp -->
+<!ENTITY looparrowright   "&#x021AC;" ><!--alias ISOAMSA rarrlp -->
+<!ENTITY LowerLeftArrow   "&#x02199;" ><!--alias ISOAMSA swarr -->
+<!ENTITY LowerRightArrow  "&#x02198;" ><!--alias ISOAMSA searr -->
+<!ENTITY lozenge          "&#x025CA;" ><!--alias ISOPUB loz -->
+<!ENTITY lrcorner         "&#x0231F;" ><!--alias ISOAMSC drcorn -->
+<!ENTITY Lsh              "&#x021B0;" ><!--alias ISOAMSA lsh -->
+<!ENTITY lvertneqq        "&#x02268;&#x00338;" ><!--alias ISOAMSN lvnE -->
+<!ENTITY maltese          "&#x02720;" ><!--alias ISOPUB malt -->
+<!ENTITY mapsto           "&#x021A6;" ><!--alias ISOAMSA map -->
+<!ENTITY measuredangle    "&#x02221;" ><!--alias ISOAMSO angmsd -->
+<!ENTITY MinusPlus        "&#x02213;" ><!--alias ISOTECH mnplus -->
+<!ENTITY mp               "&#x02213;" ><!--alias ISOTECH mnplus -->
+<!ENTITY multimap         "&#x022B8;" ><!--alias ISOAMSA mumap -->
+<!ENTITY napprox          "&#x02249;" ><!--alias ISOAMSN nap -->
+<!ENTITY natural          "&#x0266E;" ><!--alias ISOPUB natur -->
+<!ENTITY nearrow          "&#x02197;" ><!--alias ISOAMSA nearr -->
+<!ENTITY NestedGreaterGreater "&#x0226B;" ><!--alias ISOAMSR Gt -->
+<!ENTITY NestedLessLess   "&#x0226A;" ><!--alias ISOAMSR Lt -->
+<!ENTITY nexists          "&#x02204;" ><!--alias ISOAMSO nexist -->
+<!ENTITY ngeq             "&#x02271;&#x020E5;" ><!--alias ISOAMSN nge -->
+<!ENTITY ngeqq            "&#x02271;" ><!--alias ISOAMSN ngE -->
+<!ENTITY ngeqslant        "&#x02271;" ><!--alias ISOAMSN nges -->
+<!ENTITY ngtr             "&#x0226F;" ><!--alias ISOAMSN ngt -->
+<!ENTITY nleftarrow       "&#x0219A;" ><!--alias ISOAMSA nlarr -->
+<!ENTITY nLeftarrow       "&#x021CD;" ><!--alias ISOAMSA nlArr -->
+<!ENTITY nleftrightarrow  "&#x021AE;" ><!--alias ISOAMSA nharr -->
+<!ENTITY nLeftrightarrow  "&#x021CE;" ><!--alias ISOAMSA nhArr -->
+<!ENTITY nleq             "&#x02270;&#x020E5;" ><!--alias ISOAMSN nle -->
+<!ENTITY nleqq            "&#x02270;" ><!--alias ISOAMSN nlE -->
+<!ENTITY nleqslant        "&#x02270;" ><!--alias ISOAMSN nles -->
+<!ENTITY nless            "&#x0226E;" ><!--alias ISOAMSN nlt -->
+<!ENTITY NotCongruent     "&#x02262;" ><!--alias ISOAMSN nequiv -->
+<!ENTITY NotDoubleVerticalBar "&#x02226;" ><!--alias ISOAMSN npar -->
+<!ENTITY NotElement       "&#x02209;" ><!--alias ISOTECH notin -->
+<!ENTITY NotEqual         "&#x02260;" ><!--alias ISOTECH ne -->
+<!ENTITY NotExists        "&#x02204;" ><!--alias ISOAMSO nexist -->
+<!ENTITY NotGreater       "&#x0226F;" ><!--alias ISOAMSN ngt -->
+<!ENTITY NotGreaterEqual  "&#x02271;&#x020E5;" ><!--alias ISOAMSN nge -->
+<!ENTITY NotGreaterFullEqual "&#x02270;" ><!--alias ISOAMSN nlE -->
+<!ENTITY NotGreaterGreater "&#x0226B;&#x00338;&#x02063;" ><!--alias ISOAMSN nGtv -->
+<!ENTITY NotGreaterLess   "&#x02279;" ><!--alias ISOAMSN ntvgl -->
+<!ENTITY NotGreaterSlantEqual "&#x02271;" ><!--alias ISOAMSN nges -->
+<!ENTITY NotGreaterTilde  "&#x02275;" ><!--alias ISOAMSN ngsim -->
+<!ENTITY NotLeftTriangle  "&#x022EA;" ><!--alias ISOAMSN nltri -->
+<!ENTITY NotLeftTriangleEqual "&#x022EC;" ><!--alias ISOAMSN nltrie -->
+<!ENTITY NotLess          "&#x0226E;" ><!--alias ISOAMSN nlt -->
+<!ENTITY NotLessEqual     "&#x02270;&#x020E5;" ><!--alias ISOAMSN nle -->
+<!ENTITY NotLessGreater   "&#x02278;" ><!--alias ISOAMSN ntvlg -->
+<!ENTITY NotLessLess      "&#x0226A;&#x00338;&#x02063;" ><!--alias ISOAMSN nLtv -->
+<!ENTITY NotLessSlantEqual "&#x02270;" ><!--alias ISOAMSN nles -->
+<!ENTITY NotLessTilde     "&#x02274;" ><!--alias ISOAMSN nlsim -->
+<!ENTITY NotPrecedes      "&#x02280;" ><!--alias ISOAMSN npr -->
+<!ENTITY NotPrecedesEqual "&#x02AAF;&#x00338;" ><!--alias ISOAMSN npre -->
+<!ENTITY NotPrecedesSlantEqual "&#x022E0;" ><!--alias ISOAMSN nprcue -->
+<!ENTITY NotReverseElement "&#x0220C;" ><!--alias ISOTECH notniva -->
+<!ENTITY NotRightTriangle "&#x022EB;" ><!--alias ISOAMSN nrtri -->
+<!ENTITY NotRightTriangleEqual "&#x022ED;" ><!--alias ISOAMSN nrtrie -->
+<!ENTITY NotSquareSubsetEqual "&#x022E2;" ><!--alias ISOAMSN nsqsube -->
+<!ENTITY NotSquareSupersetEqual "&#x022E3;" ><!--alias ISOAMSN nsqsupe -->
+<!ENTITY NotSubset        "&#x02284;" ><!--alias ISOAMSN vnsub -->
+<!ENTITY NotSubsetEqual   "&#x02288;" ><!--alias ISOAMSN nsube -->
+<!ENTITY NotSucceeds      "&#x02281;" ><!--alias ISOAMSN nsc -->
+<!ENTITY NotSucceedsEqual "&#x02AB0;&#x00338;" ><!--alias ISOAMSN nsce -->
+<!ENTITY NotSucceedsSlantEqual "&#x022E1;" ><!--alias ISOAMSN nsccue -->
+<!ENTITY NotSuperset      "&#x02285;" ><!--alias ISOAMSN vnsup -->
+<!ENTITY NotSupersetEqual "&#x02289;" ><!--alias ISOAMSN nsupe -->
+<!ENTITY NotTilde         "&#x02241;" ><!--alias ISOAMSN nsim -->
+<!ENTITY NotTildeEqual    "&#x02244;" ><!--alias ISOAMSN nsime -->
+<!ENTITY NotTildeFullEqual "&#x02247;" ><!--alias ISOAMSN ncong -->
+<!ENTITY NotTildeTilde    "&#x02249;" ><!--alias ISOAMSN nap -->
+<!ENTITY NotVerticalBar   "&#x02224;" ><!--alias ISOAMSN nmid -->
+<!ENTITY nparallel        "&#x02226;" ><!--alias ISOAMSN npar -->
+<!ENTITY nprec            "&#x02280;" ><!--alias ISOAMSN npr -->
+<!ENTITY npreceq          "&#x02AAF;&#x00338;" ><!--alias ISOAMSN npre -->
+<!ENTITY nrightarrow      "&#x0219B;" ><!--alias ISOAMSA nrarr -->
+<!ENTITY nRightarrow      "&#x021CF;" ><!--alias ISOAMSA nrArr -->
+<!ENTITY nshortmid        "&#x02224;&#x02063;" ><!--alias ISOAMSN nsmid -->
+<!ENTITY nshortparallel   "&#x02226;&#x02063;" ><!--alias ISOAMSN nspar -->
+<!ENTITY nsimeq           "&#x02244;" ><!--alias ISOAMSN nsime -->
+<!ENTITY nsubset          "&#x02284;" ><!--alias ISOAMSN vnsub -->
+<!ENTITY nsubseteq        "&#x02288;" ><!--alias ISOAMSN nsube -->
+<!ENTITY nsubseteqq       "&#x02288;" ><!--alias ISOAMSN nsubE -->
+<!ENTITY nsucc            "&#x02281;" ><!--alias ISOAMSN nsc -->
+<!ENTITY nsucceq          "&#x02AB0;&#x00338;" ><!--alias ISOAMSN nsce -->
+<!ENTITY nsupset          "&#x02285;" ><!--alias ISOAMSN vnsup -->
+<!ENTITY nsupseteq        "&#x02289;" ><!--alias ISOAMSN nsupe -->
+<!ENTITY nsupseteqq       "&#x02289;" ><!--alias ISOAMSN nsupE -->
+<!ENTITY ntriangleleft    "&#x022EA;" ><!--alias ISOAMSN nltri -->
+<!ENTITY ntrianglelefteq  "&#x022EC;" ><!--alias ISOAMSN nltrie -->
+<!ENTITY ntriangleright   "&#x022EB;" ><!--alias ISOAMSN nrtri -->
+<!ENTITY ntrianglerighteq "&#x022ED;" ><!--alias ISOAMSN nrtrie -->
+<!ENTITY nwarrow          "&#x02196;" ><!--alias ISOAMSA nwarr -->
+<!ENTITY oint             "&#x0222E;" ><!--alias ISOTECH conint -->
+<!ENTITY OpenCurlyDoubleQuote "&#x0201C;" ><!--alias ISONUM ldquo -->
+<!ENTITY OpenCurlyQuote   "&#x02018;" ><!--alias ISONUM lsquo -->
+<!ENTITY orderof          "&#x02134;" ><!--alias ISOTECH order -->
+<!ENTITY parallel         "&#x02225;" ><!--alias ISOTECH par -->
+<!ENTITY PartialD         "&#x02202;" ><!--alias ISOTECH part -->
+<!ENTITY pitchfork        "&#x022D4;" ><!--alias ISOAMSR fork -->
+<!ENTITY PlusMinus        "&#x000B1;" ><!--alias ISONUM plusmn -->
+<!ENTITY pm               "&#x000B1;" ><!--alias ISONUM plusmn -->
+<!ENTITY prec             "&#x0227A;" ><!--alias ISOAMSR pr -->
+<!ENTITY precapprox       "&#x0227E;" ><!--alias ISOAMSR prap -->
+<!ENTITY preccurlyeq      "&#x0227C;" ><!--alias ISOAMSR prcue -->
+<!ENTITY Precedes         "&#x0227A;" ><!--alias ISOAMSR pr -->
+<!ENTITY PrecedesEqual    "&#x02AAF;" ><!--alias ISOAMSR pre -->
+<!ENTITY PrecedesSlantEqual "&#x0227C;" ><!--alias ISOAMSR prcue -->
+<!ENTITY PrecedesTilde    "&#x0227E;" ><!--alias ISOAMSR prsim -->
+<!ENTITY preceq           "&#x02AAF;" ><!--alias ISOAMSR pre -->
+<!ENTITY precnapprox      "&#x022E8;" ><!--alias ISOAMSN prnap -->
+<!ENTITY precneqq         "&#x02AB5;" ><!--alias ISOAMSN prnE -->
+<!ENTITY precnsim         "&#x022E8;" ><!--alias ISOAMSN prnsim -->
+<!ENTITY precsim          "&#x0227E;" ><!--alias ISOAMSR prsim -->
+<!ENTITY Proportion       "&#x02237;" ><!--alias ISOAMSR Colon -->
+<!ENTITY Proportional     "&#x0221D;" ><!--alias ISOTECH prop -->
+<!ENTITY propto           "&#x0221D;" ><!--alias ISOTECH prop -->
+<!ENTITY questeq          "&#x0225F;" ><!--alias ISOAMSR equest -->
+<!ENTITY rangle           "&#x03009;" ><!--alias ISOTECH rang -->
+<!ENTITY rbrace           "&#x0007D;" ><!--alias ISONUM rcub -->
+<!ENTITY rbrack           "&#x0005D;" ><!--alias ISONUM rsqb -->
+<!ENTITY Re               "&#x0211C;" ><!--alias ISOAMSO real -->
+<!ENTITY realpart         "&#x0211C;" ><!--alias ISOAMSO real -->
+<!ENTITY ReverseElement   "&#x0220B;" ><!--alias ISOTECH niv -->
+<!ENTITY ReverseEquilibrium "&#x021CB;" ><!--alias ISOAMSA lrhar -->
+<!ENTITY ReverseUpEquilibrium "&#x0296F;" ><!--alias ISOAMSA duhar -->
+<!ENTITY RightAngleBracket "&#x03009;" ><!--alias ISOTECH rang -->
+<!ENTITY rightarrow       "&#x02192;" ><!--alias ISONUM rarr -->
+<!ENTITY Rightarrow       "&#x021D2;" ><!--alias ISOTECH rArr -->
+<!ENTITY RightArrow       "&#x02192;" ><!--alias ISONUM rarr -->
+<!ENTITY RightArrowLeftArrow "&#x021C4;" ><!--alias ISOAMSA rlarr -->
+<!ENTITY rightarrowtail   "&#x021A3;" ><!--alias ISOAMSA rarrtl -->
+<!ENTITY RightCeiling     "&#x02309;" ><!--alias ISOAMSC rceil -->
+<!ENTITY RightDoubleBracket "&#x0301B;" ><!--right double bracket delimiter -->
+<!ENTITY RightDownVector  "&#x021C2;" ><!--alias ISOAMSA dharr -->
+<!ENTITY RightFloor       "&#x0230B;" ><!--alias ISOAMSC rfloor -->
+<!ENTITY rightharpoondown "&#x021C1;" ><!--alias ISOAMSA rhard -->
+<!ENTITY rightharpoonup   "&#x021C0;" ><!--alias ISOAMSA rharu -->
+<!ENTITY rightleftarrows  "&#x021C4;" ><!--alias ISOAMSA rlarr -->
+<!ENTITY rightleftharpoons "&#x021CC;" ><!--alias ISOAMSA rlhar -->
+<!ENTITY rightrightarrows "&#x021C9;" ><!--alias ISOAMSA rrarr -->
+<!ENTITY rightsquigarrow  "&#x021DD;" ><!--alias ISOAMSA rarrw -->
+<!ENTITY RightTee         "&#x022A2;" ><!--alias ISOAMSR vdash -->
+<!ENTITY RightTeeArrow    "&#x021A6;" ><!--alias ISOAMSA map -->
+<!ENTITY rightthreetimes  "&#x022CC;" ><!--alias ISOAMSB rthree -->
+<!ENTITY RightTriangle    "&#x022B3;" ><!--alias ISOAMSR vrtri -->
+<!ENTITY RightTriangleEqual "&#x022B5;" ><!--alias ISOAMSR rtrie -->
+<!ENTITY RightUpVector    "&#x021BE;" ><!--alias ISOAMSA uharr -->
+<!ENTITY RightVector      "&#x021C0;" ><!--alias ISOAMSA rharu -->
+<!ENTITY risingdotseq     "&#x02253;" ><!--alias ISOAMSR erDot -->
+<!ENTITY rmoustache       "&#x02997;" ><!--alias ISOAMSC rmoust -->
+<!ENTITY Rrightarrow      "&#x021DB;" ><!--alias ISOAMSA rAarr -->
+<!ENTITY Rsh              "&#x021B1;" ><!--alias ISOAMSA rsh -->
+<!ENTITY searrow          "&#x02198;" ><!--alias ISOAMSA searr -->
+<!ENTITY setminus         "&#x02216;" ><!--alias ISOAMSB setmn -->
+<!ENTITY ShortLeftArrow   "&#x02190;&#x02063;" ><!--alias ISOAMSA slarr -->
+<!ENTITY shortmid         "&#x02223;&#x02063;" ><!--alias ISOAMSR smid -->
+<!ENTITY shortparallel    "&#x02225;&#x02063;" ><!--alias ISOAMSR spar -->
+<!ENTITY ShortRightArrow  "&#x02192;&#x02063;" ><!--alias ISOAMSA srarr -->
+<!ENTITY simeq            "&#x02243;" ><!--alias ISOTECH sime -->
+<!ENTITY SmallCircle      "&#x02218;" ><!--alias ISOTECH compfn -->
+<!ENTITY smallsetminus    "&#x02216;" ><!--alias ISOAMSB ssetmn -->
+<!ENTITY spadesuit        "&#x02660;" ><!--ISOPUB    spades  -->
+<!ENTITY Sqrt             "&#x0221A;" ><!--alias ISOTECH radic -->
+<!ENTITY sqsubset         "&#x0228F;" ><!--alias ISOAMSR sqsub -->
+<!ENTITY sqsubseteq       "&#x02291;" ><!--alias ISOAMSR sqsube -->
+<!ENTITY sqsupset         "&#x02290;" ><!--alias ISOAMSR sqsup -->
+<!ENTITY sqsupseteq       "&#x02292;" ><!--alias ISOAMSR sqsupe -->
+<!ENTITY Square           "&#x025A1;" ><!--alias for square -->
+<!ENTITY SquareIntersection "&#x02293;" ><!--alias ISOAMSB sqcap -->
+<!ENTITY SquareSubset     "&#x0228F;" ><!--alias ISOAMSR sqsub -->
+<!ENTITY SquareSubsetEqual "&#x02291;" ><!--alias ISOAMSR sqsube -->
+<!ENTITY SquareSuperset   "&#x02290;" ><!--alias ISOAMSR sqsup -->
+<!ENTITY SquareSupersetEqual "&#x02292;" ><!--alias ISOAMSR sqsupe -->
+<!ENTITY SquareUnion      "&#x02294;" ><!--alias ISOAMSB sqcup -->
+<!ENTITY Star             "&#x022C6;" ><!--alias ISOAMSB sstarf -->
+<!ENTITY straightepsilon  "&#x003B5;" ><!--alias ISOGRK3 epsi -->
+<!ENTITY straightphi      "&#x003C6;" ><!--alias ISOGRK3 phi -->
+<!ENTITY subset           "&#x02282;" ><!--alias ISOTECH sub -->
+<!ENTITY Subset           "&#x022D0;" ><!--alias ISOAMSR Sub -->
+<!ENTITY subseteq         "&#x02286;" ><!--alias ISOTECH sube -->
+<!ENTITY subseteqq        "&#x02286;" ><!--alias ISOAMSR subE -->
+<!ENTITY SubsetEqual      "&#x02286;" ><!--alias ISOTECH sube -->
+<!ENTITY subsetneq        "&#x0228A;" ><!--alias ISOAMSN subne -->
+<!ENTITY subsetneqq       "&#x0228A;" ><!--alias ISOAMSN subnE -->
+<!ENTITY succ             "&#x0227B;" ><!--alias ISOAMSR sc -->
+<!ENTITY succapprox       "&#x0227F;" ><!--alias ISOAMSR scap -->
+<!ENTITY succcurlyeq      "&#x0227D;" ><!--alias ISOAMSR sccue -->
+<!ENTITY Succeeds         "&#x0227B;" ><!--alias ISOAMSR sc -->
+<!ENTITY SucceedsEqual    "&#x0227D;" ><!--alias ISOAMSR sce -->
+<!ENTITY SucceedsSlantEqual "&#x0227D;" ><!--alias ISOAMSR sccue -->
+<!ENTITY SucceedsTilde    "&#x0227F;" ><!--alias ISOAMSR scsim -->
+<!ENTITY succeq           "&#x0227D;" ><!--alias ISOAMSR sce -->
+<!ENTITY succnapprox      "&#x022E9;" ><!--alias ISOAMSN scnap -->
+<!ENTITY succneqq         "&#x02AB6;" ><!--alias ISOAMSN scnE -->
+<!ENTITY succnsim         "&#x022E9;" ><!--alias ISOAMSN scnsim -->
+<!ENTITY succsim          "&#x0227F;" ><!--alias ISOAMSR scsim -->
+<!ENTITY SuchThat         "&#x0220B;" ><!--ISOTECH  ni -->
+<!ENTITY Sum              "&#x02211;" ><!--alias ISOAMSB sum -->
+<!ENTITY Superset         "&#x02283;" ><!--alias ISOTECH sup -->
+<!ENTITY SupersetEqual    "&#x02287;" ><!--alias ISOTECH supe -->
+<!ENTITY supset           "&#x02283;" ><!--alias ISOTECH sup -->
+<!ENTITY Supset           "&#x022D1;" ><!--alias ISOAMSR Sup -->
+<!ENTITY supseteq         "&#x02287;" ><!--alias ISOTECH supe -->
+<!ENTITY supseteqq        "&#x02287;" ><!--alias ISOAMSR supE -->
+<!ENTITY supsetneq        "&#x0228B;" ><!--alias ISOAMSN supne -->
+<!ENTITY supsetneqq       "&#x0228B;" ><!--alias ISOAMSN supnE -->
+<!ENTITY swarrow          "&#x02199;" ><!--alias ISOAMSA swarr -->
+<!ENTITY therefore        "&#x02234;" ><!--alias ISOTECH there4 -->
+<!ENTITY Therefore        "&#x02234;" ><!--alias ISOTECH there4 -->
+<!ENTITY thickapprox      "&#x02248;&#x02063;" ><!--ISOAMSR   thkap  -->
+<!ENTITY thicksim         "&#x0223C;" ><!--ISOAMSR   thksim -->
+<!ENTITY ThinSpace        "&#x02009;" ><!--space of width 3/18 em alias ISOPUB thinsp -->
+<!ENTITY Tilde            "&#x0223C;" ><!--alias ISOTECH sim -->
+<!ENTITY TildeEqual       "&#x02243;" ><!--alias ISOTECH sime -->
+<!ENTITY TildeFullEqual   "&#x02245;" ><!--alias ISOTECH cong -->
+<!ENTITY TildeTilde       "&#x02248;" ><!--alias ISOTECH ap -->
+<!ENTITY toea             "&#x02928;" ><!--alias ISOAMSA nesear -->
+<!ENTITY tosa             "&#x02929;" ><!--alias ISOAMSA seswar -->
+<!ENTITY triangle         "&#x025B5;" ><!--alias ISOPUB utri -->
+<!ENTITY triangledown     "&#x025BF;" ><!--alias ISOPUB dtri -->
+<!ENTITY triangleleft     "&#x025C3;" ><!--alias ISOPUB ltri -->
+<!ENTITY trianglelefteq   "&#x022B4;" ><!--alias ISOAMSR ltrie -->
+<!ENTITY triangleq        "&#x0225C;" ><!--alias ISOAMSR trie -->
+<!ENTITY triangleright    "&#x025B9;" ><!--alias ISOPUB rtri -->
+<!ENTITY trianglerighteq  "&#x022B5;" ><!--alias ISOAMSR rtrie -->
+<!ENTITY TripleDot        "&#x020DB;" ><!--alias ISOTECH tdot -->
+<!ENTITY twoheadleftarrow "&#x0219E;" ><!--alias ISOAMSA Larr -->
+<!ENTITY twoheadrightarrow "&#x021A0;" ><!--alias ISOAMSA Rarr -->
+<!ENTITY ulcorner         "&#x0231C;" ><!--alias ISOAMSC ulcorn -->
+<!ENTITY Union            "&#x022C3;" ><!--alias ISOAMSB xcup -->
+<!ENTITY UnionPlus        "&#x0228E;" ><!--alias ISOAMSB uplus -->
+<!ENTITY uparrow          "&#x02191;" ><!--alias ISONUM uarr -->
+<!ENTITY Uparrow          "&#x021D1;" ><!--alias ISOAMSA uArr -->
+<!ENTITY UpArrow          "&#x02191;" ><!--alias ISONUM uarr -->
+<!ENTITY UpArrowDownArrow "&#x021C5;" ><!--alias ISOAMSA udarr -->
+<!ENTITY updownarrow      "&#x02195;" ><!--alias ISOAMSA varr -->
+<!ENTITY Updownarrow      "&#x021D5;" ><!--alias ISOAMSA vArr -->
+<!ENTITY UpDownArrow      "&#x02195;" ><!--alias ISOAMSA varr -->
+<!ENTITY UpEquilibrium    "&#x0296E;" ><!--alias ISOAMSA udhar -->
+<!ENTITY upharpoonleft    "&#x021BF;" ><!--alias ISOAMSA uharl -->
+<!ENTITY upharpoonright   "&#x021BE;" ><!--alias ISOAMSA uharr -->
+<!ENTITY UpperLeftArrow   "&#x02196;" ><!--alias ISOAMSA nwarr -->
+<!ENTITY UpperRightArrow  "&#x02197;" ><!--alias ISOAMSA nearr -->
+<!ENTITY upsilon          "&#x003C5;" ><!--alias ISOGRK3 upsi -->
+<!ENTITY Upsilon          "&#x003D2;" ><!--alias ISOGRK3 Upsi -->
+<!ENTITY UpTee            "&#x022A5;" ><!--alias ISOTECH perp -->
+<!ENTITY upuparrows       "&#x021C8;" ><!--alias ISOAMSA uuarr -->
+<!ENTITY urcorner         "&#x0231D;" ><!--alias ISOAMSC urcorn -->
+<!ENTITY varepsilon       "&#x0025B;" ><!--alias ISOGRK3 epsiv -->
+<!ENTITY varkappa         "&#x003F0;" ><!--alias ISOGRK3 kappav -->
+<!ENTITY varnothing       "&#x02205;" ><!--alias ISOAMSO emptyv -->
+<!ENTITY varphi           "&#x003D5;" ><!--alias ISOGRK3 phiv -->
+<!ENTITY varpi            "&#x003D6;" ><!--alias ISOGRK3 piv -->
+<!ENTITY varpropto        "&#x0221D;" ><!--alias ISOAMSR vprop -->
+<!ENTITY varrho           "&#x003F1;" ><!--alias ISOGRK3 rhov -->
+<!ENTITY varsigma         "&#x003C2;" ><!--alias ISOGRK3 sigmav -->
+<!ENTITY varsubsetneq     "&#x0228A;&#x02063;" ><!--alias ISOAMSN vsubne -->
+<!ENTITY varsubsetneqq    "&#x0228A;&#x02063;" ><!--alias ISOAMSN vsubnE -->
+<!ENTITY varsupsetneq     "&#x0228B;&#x02063;" ><!--alias ISOAMSN vsupne -->
+<!ENTITY varsupsetneqq    "&#x0228B;&#x02063;" ><!--alias ISOAMSN vsupnE -->
+<!ENTITY vartheta         "&#x003D1;" ><!--alias ISOGRK3 thetav -->
+<!ENTITY vartriangleleft  "&#x022B2;" ><!--alias ISOAMSR vltri -->
+<!ENTITY vartriangleright "&#x022B3;" ><!--alias ISOAMSR vrtri -->
+<!ENTITY vee              "&#x02228;" ><!--alias ISOTECH or -->
+<!ENTITY Vee              "&#x022C1;" ><!--alias ISOAMSB xvee -->
+<!ENTITY vert             "&#x0007C;" ><!--alias ISONUM verbar -->
+<!ENTITY Vert             "&#x02016;" ><!--alias ISOTECH Verbar -->
+<!ENTITY VerticalBar      "&#x02223;" ><!--alias ISOAMSR mid -->
+<!ENTITY VerticalTilde    "&#x02240;" ><!--alias ISOAMSB wreath -->
+<!ENTITY VeryThinSpace    "&#x0200A;" ><!--space of width 1/18 em alias ISOPUB hairsp -->
+<!ENTITY wedge            "&#x02227;" ><!--alias ISOTECH and -->
+<!ENTITY Wedge            "&#x022C0;" ><!--alias ISOAMSB xwedge -->
+<!ENTITY wp               "&#x02118;" ><!--alias ISOAMSO weierp -->
+<!ENTITY wr               "&#x02240;" ><!--alias ISOAMSB wreath -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/mmlextra.ent b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/mmlextra.ent
new file mode 100644
index 00000000000..e76de448cc3
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/ent/mmlextra.ent
@@ -0,0 +1,134 @@
+
+<!--
+     File mmlextra.ent produced by the XSL script mmldtd.xsl
+     from input data in unicode.xml.
+
+     Please report any errors to 
+     David Carlisle <davidc@nag.co.uk>.
+
+     The numeric character values assigned to each entity
+     (should) match either official Unicode assignments
+     or assignments provisionally allocated by the
+     Unicode Consortium based on the characters in the `STIX'
+     propsal for mathematics. Note that these assignments
+     have not been ratified by the corresponding ISO
+     committee and thus should be considered liable to
+     change.
+
+-->
+
+<!ENTITY af               "&#x02061;" ><!--short form of &ApplyFunction; -->
+<!ENTITY ApplyFunction    "&#x02061;" ><!--character showing function application in presentation tagging -->
+<!ENTITY Assign           "&#x02254;" ><!--assignment operator -->
+<!ENTITY CapitalDifferentialD "&#x02145;" ><!--D for use in differentials, e.g., within integrals -->
+<!ENTITY Cayleys          "&#x0212D;" ><!--the non-associative ring of octonions or Cayley numbers -->
+<!ENTITY complexes        "&#x02102;" ><!--the field of complex numbers -->
+<!ENTITY Cross            "&#x02A2F;" ><!--cross or vector product -->
+<!ENTITY dd               "&#x02146;" ><!--short form of &DifferentialD; -->
+<!ENTITY DD               "&#x02145;" ><!--short form of CapitalDifferentialD -->
+<!ENTITY DifferentialD    "&#x02146;" ><!--d for use in differentials, e.g., within integrals -->
+<!ENTITY DownArrowBar     "&#x02913;" ><!--down arrow to bar -->
+<!ENTITY DownBreve        "&#x00311;" ><!--breve, inverted (non-spacing) -->
+<!ENTITY DownLeftRightVector "&#x02950;" ><!--left-down-right-down harpoon -->
+<!ENTITY DownLeftTeeVector "&#x0295E;" ><!--left-down harpoon from bar -->
+<!ENTITY DownLeftVectorBar "&#x02956;" ><!--left-down harpoon to bar -->
+<!ENTITY DownRightTeeVector "&#x0295F;" ><!--right-down harpoon from bar -->
+<!ENTITY DownRightVectorBar "&#x02957;" ><!--right-down harpoon to bar -->
+<!ENTITY DownTeeArrow     "&#x021A7;" ><!--alias for mapstodown -->
+<!ENTITY ee               "&#x02147;" ><!--short form of &ExponentialE; -->
+<!ENTITY EmptySmallSquare "&#x025FD;" ><!--empty small square -->
+<!ENTITY EmptyVerySmallSquare "&#x025FD;" ><!--empty small square -->
+<!ENTITY Equal            "&#x02A75;" ><!--two consecutive equal signs -->
+<!ENTITY expectation      "&#x02130;" ><!--expectation (operator) -->
+<!ENTITY exponentiale     "&#x0212F;" ><!--base of the Napierian logarithms -->
+<!ENTITY ExponentialE     "&#x02147;" ><!--e use for the exponential base of the natural logarithms -->
+<!ENTITY FilledSmallSquare "&#x025FE;" ><!--filled small square -->
+<!ENTITY FilledVerySmallSquare "&#x025FE;" ><!--filled very small square -->
+<!ENTITY Fouriertrf       "&#x02131;" ><!--Fourier transform -->
+<!ENTITY GreaterGreater   "&#x02AA2;" ><!--alias for GT -->
+<!ENTITY HilbertSpace     "&#x0210B;" ><!--Hilbert space -->
+<!ENTITY HorizontalLine   "&#x02500;" ><!--short horizontal line  -->
+<!ENTITY ic               "&#x0200B;" ><!--short form of  &InvisibleComma; -->
+<!ENTITY ii               "&#x02148;" ><!--short form of &ImaginaryI; -->
+<!ENTITY ImaginaryI       "&#x02148;" ><!--i for use as a square root of -1 -->
+<!ENTITY imagline         "&#x02110;" ><!--the geometric imaginary line -->
+<!ENTITY integers         "&#x02124;" ><!--the ring of integers -->
+<!ENTITY InvisibleComma   "&#x0200B;" ><!--used as a separator, e.g., in indices -->
+<!ENTITY InvisibleTimes   "&#x02062;" ><!--marks multiplication when it is understood without a mark -->
+<!ENTITY it               "&#x02062;" ><!--short form of &InvisibleTimes; -->
+<!ENTITY Laplacetrf       "&#x02112;" ><!--Laplace transform -->
+<!ENTITY larrb            "&#x021E4;" ><!--leftwards arrow to bar -->
+<!ENTITY LeftArrowBar     "&#x021E4;" ><!--alias for larrb -->
+<!ENTITY LeftDownTeeVector "&#x02961;" ><!--down-left harpoon from bar -->
+<!ENTITY LeftDownVectorBar "&#x02959;" ><!--down-left harpoon to bar -->
+<!ENTITY LeftRightVector  "&#x0294E;" ><!--left-up-right-up harpoon -->
+<!ENTITY LeftTeeArrow     "&#x021A4;" ><!--alias for mapstoleft -->
+<!ENTITY LeftTeeVector    "&#x0295A;" ><!--left-up harpoon from bar -->
+<!ENTITY LeftTriangleBar  "&#x029CF;" ><!--not left triangle, vertical bar -->
+<!ENTITY LeftUpDownVector "&#x02951;" ><!--up-left-down-left harpoon -->
+<!ENTITY LeftUpTeeVector  "&#x02960;" ><!--up-left harpoon from bar -->
+<!ENTITY LeftUpVectorBar  "&#x02958;" ><!--up-left harpoon to bar -->
+<!ENTITY LeftVectorBar    "&#x02952;" ><!--left-up harpoon to bar -->
+<!ENTITY LessLess         "&#x02AA1;" ><!--alias for Lt -->
+<!ENTITY mapstodown       "&#x021A7;" ><!--downwards arrow from bar -->
+<!ENTITY mapstoleft       "&#x021A4;" ><!--leftwards arrow from bar -->
+<!ENTITY mapstoup         "&#x021A5;" ><!--upwards arrow from bar -->
+<!ENTITY Mellintrf        "&#x02133;" ><!--Mellin transform -->
+<!ENTITY naturals         "&#x02115;" ><!--the semi-ring of natural numbers -->
+<!ENTITY nbump            "&#x0224E;&#x00338;" ><!--not bumpy equals -->
+<!ENTITY nbumpe           "&#x0224F;&#x00338;" ><!--not bumpy single equals -->
+<!ENTITY NegativeMediumSpace "&#x0205F;&#x02063;" ><!--space of width -4/18 em -->
+<!ENTITY NegativeThickSpace "&#x02005;&#x02063;" ><!--space of width -5/18 em -->
+<!ENTITY NegativeThinSpace "&#x02009;&#x02063;" ><!--space of width -3/18 em -->
+<!ENTITY NegativeVeryThinSpace "&#x0200A;&#x02063;" ><!--space of width -1/18 em -->
+<!ENTITY nesim            "&#x02242;&#x00338;" ><!--not equal or similar -->
+<!ENTITY NewLine          "&#x0000A;" ><!--force a line break; line feed -->
+<!ENTITY NoBreak          "&#x0FEFF;" ><!--never break line here -->
+<!ENTITY NotCupCap        "&#x0226D;" ><!--alias for &nasymp; -->
+<!ENTITY NotEqualTilde    "&#x02242;&#x00338;" ><!--alias for  &nesim; -->
+<!ENTITY NotHumpDownHump  "&#x0224E;&#x00338;" ><!--alias for &nbump; -->
+<!ENTITY NotHumpEqual     "&#x0224F;&#x00338;" ><!--alias for &nbumpe; -->
+<!ENTITY NotLeftTriangleBar "&#x029CF;&#x00338;" ><!--not left triangle, vertical bar -->
+<!ENTITY NotNestedGreaterGreater "&#x024A2;&#x00338;" ><!--not double greater-than sign -->
+<!ENTITY NotNestedLessLess "&#x024A1;&#x00338;" ><!--not double less-than sign -->
+<!ENTITY NotRightTriangleBar "&#x029D0;&#x00338;" ><!--not vertical bar, right triangle -->
+<!ENTITY NotSquareSubset  "&#x0228F;&#x00338;" ><!--square not subset -->
+<!ENTITY NotSquareSuperset "&#x02290;&#x00338;" ><!--negated set-like partial order operator -->
+<!ENTITY NotSucceedsTilde "&#x0227F;&#x00338;" ><!--not succeeds or similar -->
+<!ENTITY OverBar          "&#x000AF;" ><!--over bar -->
+<!ENTITY OverBrace        "&#x0FE37;" ><!--over brace  -->
+<!ENTITY OverBracket      "&#x023B4;" ><!--over bracket -->
+<!ENTITY OverParenthesis  "&#x0FE35;" ><!--over parenthesis -->
+<!ENTITY planckh          "&#x0210E;" ><!--the ring (skew field) of quaternions -->
+<!ENTITY Poincareplane    "&#x0210C;" ><!--the Poincare upper half-plane -->
+<!ENTITY primes           "&#x02119;" ><!--the prime natural numbers -->
+<!ENTITY Product          "&#x0220F;" ><!--alias for &prod -->
+<!ENTITY quaternions      "&#x0210D;" ><!--the ring (skew field) of quaternions -->
+<!ENTITY rarrb            "&#x021E5;" ><!--leftwards arrow to bar -->
+<!ENTITY rationals        "&#x0211A;" ><!--the field of rational numbers -->
+<!ENTITY realine          "&#x0211B;" ><!--the geometric real line -->
+<!ENTITY reals            "&#x0211D;" ><!--the field of real numbers -->
+<!ENTITY RightArrowBar    "&#x021E5;" ><!--alias for rarrb -->
+<!ENTITY RightDownTeeVector "&#x0295D;" ><!--down-right harpoon from bar -->
+<!ENTITY RightDownVectorBar "&#x02955;" ><!--down-right harpoon to bar -->
+<!ENTITY RightTeeVector   "&#x0295B;" ><!--right-up harpoon from bar -->
+<!ENTITY RightTriangleBar "&#x029D0;" ><!--vertical bar, right triangle -->
+<!ENTITY RightUpDownVector "&#x0294F;" ><!--up-right-down-right harpoon -->
+<!ENTITY RightUpTeeVector "&#x0295C;" ><!--up-right harpoon from bar -->
+<!ENTITY RightUpVectorBar "&#x02954;" ><!--up-right harpoon to bar -->
+<!ENTITY RightVectorBar   "&#x02953;" ><!--up-right harpoon to bar -->
+<!ENTITY RoundImplies     "&#x02970;" ><!--round implies -->
+<!ENTITY RuleDelayed      "&#x029F4;" ><!--rule-delayed (colon right arrow) -->
+<!ENTITY ShortDownArrow   "&#x02304;&#x02063;" ><!--short down arrow -->
+<!ENTITY ShortUpArrow     "&#x02303;&#x02063;" ><!--short up arrow  -->
+<!ENTITY Tab              "&#x00009;" ><!--tabulator stop; horizontal tabulation -->
+<!ENTITY ThickSpace       "&#x02005;" ><!--space of width 5/18 em -->
+<!ENTITY UnderBar         "&#x00332;" ><!--combining low line -->
+<!ENTITY UnderBrace       "&#x0FE38;" ><!--under brace  -->
+<!ENTITY UnderBracket     "&#x023B5;" ><!--under bracket -->
+<!ENTITY UpArrowBar       "&#x02912;" ><!--up arrow to bar -->
+<!ENTITY UpTeeArrow       "&#x021A5;" ><!--Alias mapstoup -->
+<!ENTITY VerticalLine     "&#x02758;" ><!--short vertical line  -->
+<!ENTITY VerticalSeparator "&#x02758;" ><!--vertical separating operator -->
+<!ENTITY zeetrf           "&#x02128;" ><!--zee transform -->
+<!ENTITY ZeroWidthSpace   "&#x0200B;" ><!--zero width space -->
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/latex.entities.dtd b/docs-xml/xslt/db2latex-xsl/xsl/mathml/latex.entities.dtd
new file mode 100644
index 00000000000..7ec703e2c75
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/latex.entities.dtd
@@ -0,0 +1,7 @@
+<!ELEMENT character (#PCDATA)>
+
+<!ATTLIST character 
+entity	CDATA	#REQUIRED
+arguments	CDATA	#IMPLIED
+>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/latex.entities.xml b/docs-xml/xslt/db2latex-xsl/xsl/mathml/latex.entities.xml
new file mode 100644
index 00000000000..e5290aba106
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/latex.entities.xml
@@ -0,0 +1,12 @@
+<?xml version='1.0'?>
+<!DOCTYPE latex SYSTEM "latex.entities.dtd" []>
+
+<latex>
+  <character entity="&#948;">\delta</character>
+  <character entity="&#954;">\kappa</character>
+  <character entity="&#960;">\pi</character>
+  <character entity="&#x02212;">-</character>
+  <character entity="&#x003B2;">\beta</character>
+  <character entity="&#x00302;">\sphat</character><!-- superscript=""-->
+  <character entity="&#x00302;" arguments="1">\hat</character>
+</latex>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.constsymb.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.constsymb.mod.xsl
new file mode 100644
index 00000000000..3d3afdded86
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.constsymb.mod.xsl
@@ -0,0 +1,101 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet
+[
+ <!ENTITY % mmlalias PUBLIC "MathML alias" "ent/mmlalias.ent">  %mmlalias;
+ <!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent">  %mmlextra;
+]>
+<!--############################################################################# 
+ |	$Id: mathml.content.constsymb.mod.xsl,v 1.2 2004/01/18 10:40:17 j-devenish Exp $
+ |- #############################################################################
+ |	$Author: j-devenish $												
+ |														
+ |   PURPOSE: MathML content markup, constants and symbols, 4.4.12.
+ |	MathML namespace used -> mml
+ + ############################################################################## -->
+
+<xsl:stylesheet version='1.0'
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
+	xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns="http://www.w3.org/1998/Math/MathML">
+
+<!-- integer numbers -->
+<xsl:template match="mml:integers">
+	<xsl:text>\mathbb Z </xsl:text>
+</xsl:template>
+
+<!-- real numbers -->
+<xsl:template match="mml:reals">
+	<xsl:text>\mathbb R </xsl:text>
+</xsl:template>
+
+<!-- rational numbers -->
+<xsl:template match="mml:rationals">
+	<xsl:text>\mathbb Q </xsl:text>
+</xsl:template>
+
+<!-- natural numbers -->
+<xsl:template match="mml:naturalnumbers">
+	<xsl:text>\mathbb N </xsl:text>
+</xsl:template>
+
+<!-- complex numbers -->
+<xsl:template match="mml:complexes">
+	<xsl:text>\mathbb C </xsl:text>
+</xsl:template>
+
+<!-- prime numbers -->
+<xsl:template match="mml:primes">
+	<xsl:text>\mathbb P </xsl:text>
+  <mi><xsl:text disable-output-escaping='yes'>&amp;#x1D547;</xsl:text></mi>  <!-- open face P --> <!-- UNICODE char does not work -->
+</xsl:template>
+
+
+
+
+
+
+
+<!-- exponential base -->
+<xsl:template match="mml:exponentiale">
+	<xsl:text>\textrm{e} </xsl:text>
+</xsl:template>
+
+<!-- square root of -1 -->
+<xsl:template match="mml:imaginaryi">
+	<xsl:text>\textrm{i} </xsl:text>
+</xsl:template>
+
+<xsl:template match="mml:notanumber">
+	<xsl:text>\NaN </xsl:text>
+</xsl:template>
+
+<!-- logical constant for truth -->
+<xsl:template match="mml:true">
+	<xsl:text>true</xsl:text>
+</xsl:template>
+
+<!-- logical constant for falsehood -->
+<xsl:template match="mml:false">
+	<xsl:text>false</xsl:text>
+</xsl:template>
+
+<!-- empty set -->
+<xsl:template match="mml:emptyset">
+	<xsl:text>\empty</xsl:text>
+</xsl:template>
+
+<!-- ratio of a circle's circumference to its diameter -->
+<xsl:template match="mml:pi">
+	<xsl:text>\pi</xsl:text>
+</xsl:template>
+
+<!-- Euler's constant -->
+<xsl:template match="mml:eulergamma">
+	<xsl:text>\Gamma</xsl:text>
+</xsl:template>
+
+<!-- Infinity -->
+<xsl:template match="mml:infinity">
+	<xsl:text>\infty</xsl:text>
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.functions.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.functions.mod.xsl
new file mode 100644
index 00000000000..2b6258e10ae
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.functions.mod.xsl
@@ -0,0 +1,750 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet
+[
+ <!ENTITY % mmlalias PUBLIC "MathML alias" "ent/mmlalias.ent">  %mmlalias;
+ <!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent">  %mmlextra;
+]>
+<!--############################################################################# 
+ |	$Id: mathml.content.functions.mod.xsl,v 1.2 2004/01/18 10:45:35 j-devenish Exp $		
+ |- #############################################################################
+ |	$Author: j-devenish $												
+ |														
+ |   PURPOSE: MathML content markup.
+ |	Note: these elements are not part of the DocBook DTD. I have extended
+ |    the docbook DTD in order to support this tags, so that's why I have these 
+ |	templates here.
+ |   
+ |	MathML namespace used -> mml
+ + ############################################################################## -->
+
+<xsl:stylesheet version='1.0'
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
+	xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns="http://www.w3.org/1998/Math/MathML">
+
+<xsl:template match="mml:fn">
+</xsl:template>
+
+<!--
+<xsl:template match="mml:apply/lowlimit">
+<xsl:variable name="first" select="../child::*[1]"/>
+</xsl:template>
+
+<xsl:template match="mml:apply/uplimit">
+<xsl:variable name="first" select="../child::*[1]"/>
+</xsl:template>
+
+<xsl:template match="mml:apply/degree">
+<xsl:variable name="first" select="../child::*[1]"/>
+</xsl:template>
+-->
+
+
+<!-- conditions -->
+<!-- no support for deprecated reln-->
+<xsl:template match="mml:condition">
+	<xsl:text>{</xsl:text><xsl:apply-templates/><xsl:text>}</xsl:text>
+</xsl:template>
+
+
+
+
+
+
+<!--UNARY 
+	  unary arithmetic			exp, factorial, minus, abs, conjugate, arg, real, imaginary
+        unary logical				not
+        unary functional			inverse, ident
+        unary elementary classical
+        functions					sin, cos, tan, sec, csc, cot, sinh, cosh, tanh, sech, csch, coth, arcsin,
+                                          arccos, arctan, arccosh, arccot, arccoth, arccsc, arccsch, arcsec, arcsech, arcsinh,
+                                          arctanh, exp, ln, log
+        unary linear algebra			determinant, transpose
+        unary calculus and vector calculus
+                                          divergence, grad, curl, laplacian
+        unary set-theoretic			card
+-->
+
+<!-- BINARY
+	  binary arithmetic 			quotient, divide, minus, power, rem
+        binary logical				implies, equivalent, approx
+        binary set operators			setdiff
+        binary linear algebra			vectorproduct, scalarproduct, outerproduct
+-->
+
+<!-- N-ARY and OTHER
+ 	 n-ary statistical mean, sdev, variance, median, mode
+        n-ary logical and, or, xor
+        n-ary linear algebra selector
+        n-ary set operator union, intersect
+        n-ary functional fn, compose
+        integral, sum, product operators int, sum, product
+        differential operator diff, partialdiff
+        quantifier forall, exists
+-->
+<!-- Get the first child (operator), and check if its name is a fn , or operator-->
+<!-- Is the operator taking qualifiers? -->
+<!-- Operators  : int, sum, product, root, diff, partialdiff, limit, log, moment, min, max, forall, exists -->
+<!-- Qualifiers : lowlimit, uplimit, bvar, degree, logbase, interval, condition  -->
+
+
+<!-- apply/apply -->
+<xsl:template match="mml:apply[mml:apply]">  <!-- when the function itself is defined by other functions: (F+G)(x) -->
+	<xsl:choose>
+		<xsl:when test="count(child::*)>=2">
+			<xsl:text>{</xsl:text><xsl:apply-templates select="child::*[position()=1]"/><xsl:text>}</xsl:text>	
+			<xsl:text>{</xsl:text><xsl:apply-templates select="child::*[position()!=1]"/><xsl:text>}</xsl:text>	
+		</xsl:when>
+	<xsl:otherwise> <!-- apply only contains apply, no operand-->
+			<xsl:text>{</xsl:text><xsl:apply-templates select="child::*"/><xsl:text>}</xsl:text>	
+	</xsl:otherwise>
+	</xsl:choose>
+</xsl:template>
+
+
+<!-- force function or operator MathML 1.0 deprecated-->
+<!-- partial support for func/operators defined using presentation markup-->
+<xsl:template match="mml:apply[mml:fn]">
+<mrow>
+<xsl:choose>
+<xsl:when test="*[position()=1 and self::mml:fn]/mml:mo/mml:mchar/@name='PlusMinus'">
+  <!--if operator is infix (we assume this to be the default when we have mchars(for instance PlusMinus); perhaps we should test further the name attribute)-->
+  <xsl:choose>
+  <xsl:when test="count(child::*)>=3">
+    <mrow>
+      <xsl:for-each select="child::*[position()!=last() and  position()!=1]">
+        <xsl:apply-templates select="."/><xsl:copy-of select="preceding-sibling::mml:fn/*"/>
+      </xsl:for-each>
+      <xsl:apply-templates select="child::*[position()!=1 and position()=last()]"/>
+    </mrow>
+  </xsl:when>
+  <xsl:when test="count(child::*)=2">
+    <mrow><xsl:copy-of select="child::mml:fn[position()=1]/*"/><xsl:apply-templates select="child::*[position()=2]"/></mrow>
+  </xsl:when>
+  <xsl:otherwise> <!-- apply only contains fn, no operand-->
+    <mrow><xsl:apply-templates select="child::mml:fn/*"/></mrow>
+  </xsl:otherwise>
+  </xsl:choose>
+</xsl:when>  
+<xsl:otherwise>  <!-- if operator is prefix (common case)-->
+  <xsl:choose>
+    <xsl:when test="name(mml:fn/*[position()=1])='apply'"> <!-- fn definition is complex, surround with brackets, but only one child-->
+      <mfenced separators=""><mrow><xsl:apply-templates select="mml:fn/*"/></mrow></mfenced>
+    </xsl:when>
+    <xsl:otherwise>
+      <mi><xsl:apply-templates select="mml:fn/*"/></mi>
+    </xsl:otherwise>
+  </xsl:choose>
+  <xsl:if test="count(*)>1">  <!-- if no operands, don't put empty parentheses-->
+    <mo><mchar name="ApplyFunction"/></mo>
+    <mfenced>
+      <xsl:apply-templates select="*[position()!=1]"/>
+    </mfenced>
+  </xsl:if>
+</xsl:otherwise>
+</xsl:choose>
+</mrow>
+</xsl:template>
+
+
+
+
+<!-- quotient -->
+<xsl:template match="mml:apply[mml:quotient]">
+  <mrow>  <!-- the third notation uses UNICODE chars x0230A and x0230B -->
+    <mo>integer part of</mo>
+    <mrow>
+      <xsl:choose> <!-- surround with brackets if operands are composed-->
+      <xsl:when test="child::*[position()=2] and name()='mml:apply'">
+        <mfenced separators=""><xsl:apply-templates select="*[position()=2]"/></mfenced>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:apply-templates select="*[position()=2]"/>
+      </xsl:otherwise>
+      </xsl:choose>
+      <mo>/</mo>
+      <xsl:choose>
+      <xsl:when test="child::*[position()=3] and name()='mml:apply'">
+        <mfenced separators=""><xsl:apply-templates select="*[position()=3]"/></mfenced>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:apply-templates select="*[position()=3]"/>
+      </xsl:otherwise>
+      </xsl:choose>
+    </mrow>
+  </mrow>
+</xsl:template>
+
+
+<!-- factorial -->
+<xsl:template match="mml:apply[mml:factorial]">
+	<xsl:text>{</xsl:text>
+	<xsl:choose> 
+		<xsl:when test="name(*[position()=2])='mml:apply'">
+			<xsl:text>{</xsl:text><xsl:apply-templates select="*[position()=2]"/><xsl:text>}</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:apply-templates select="*[position()=2]"/>
+		</xsl:otherwise>
+	</xsl:choose>
+	<xsl:text>!(fact)</xsl:text>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+
+<!-- divide -->
+<xsl:template match="mml:apply[mml:divide]">
+	<xsl:text>{ \frac</xsl:text>
+	<xsl:text>{ </xsl:text>
+	<xsl:apply-templates select="child::*[position()=2]"/>
+	<xsl:text>}</xsl:text>
+	<xsl:text>{ </xsl:text>
+	<xsl:apply-templates select="child::*[position()=3]"/>
+	<xsl:text>}</xsl:text>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+
+<!-- APPLY CONTAINING MAX	-->
+<xsl:template match="mml:apply/mml:max"/>
+<xsl:template match="mml:apply[mml:max]">
+	<xsl:text>{</xsl:text>
+	<xsl:choose>
+		<xsl:when test="mml:bvar"> <!-- if there are bvars-->
+			<xsl:text>\max_{</xsl:text>
+		<!-- Select every bvar except the last one (position() only counts bvars, not the other siblings)-->
+			<xsl:for-each select="mml:bvar[position()!=last()]">  
+            		<xsl:apply-templates select="."/><xsl:text>,</xsl:text>
+			</xsl:for-each>
+			<xsl:apply-templates select="mml:bvar[position()=last()]"/>
+			<xsl:text>}</xsl:text>
+		</xsl:when>
+		<xsl:otherwise> <!-- No bvars, no underscore... -->
+			<xsl:text>\max</xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+	<xsl:text>\left\{</xsl:text>
+     	<xsl:for-each select="child::*[name()!='mml:condition' and 	name()!='mml:bvar' and 	name()!='mml:max' and 	position()!=last()]">
+     		<xsl:apply-templates select="."/><xsl:text>,</xsl:text>
+		<xsl:message>RCAS: MathML mml:apply[mml:min] Applying templates to <xsl:copy-of select="name(.)"/></xsl:message>
+	</xsl:for-each>
+     	<xsl:apply-templates select="child::*[name()!='mml:condition' and	name()!='mml:bvar' and 	name()!='mml:max' and 	position()=last()]"/>
+	<!-- If there is a condition, do not close... -->	
+	<xsl:if test="mml:condition">
+     		<xsl:text>|</xsl:text><xsl:apply-templates select="mml:condition"/>
+	</xsl:if>
+     	<xsl:text>\right\}</xsl:text>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+
+<!-- APPLY CONTAINING MIN	-->
+<xsl:template match="mml:apply/mml:min"/>
+<xsl:template match="mml:apply[mml:min]">
+	<xsl:text>{</xsl:text>
+	<xsl:choose>
+		<xsl:when test="mml:bvar"> <!-- if there are bvars-->
+			<xsl:text>\min_{</xsl:text>
+			<!-- Select every bvar except the last one (position() only counts bvars, not the other siblings)-->
+			<xsl:for-each select="mml:bvar[position()!=last()]">  
+            		<xsl:apply-templates select="."/><xsl:text>,</xsl:text>
+			</xsl:for-each>
+			<xsl:apply-templates select="mml:bvar[position()=last()]"/>
+			<xsl:text>}</xsl:text>
+		</xsl:when>
+		<xsl:otherwise> <!-- No bvars, no underscore... -->
+			<xsl:text>\min</xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+	<xsl:text>\left\{</xsl:text>
+     	<xsl:for-each select="child::*[name()!='mml:condition' and 	name()!='mml:bvar' and 	name()!='mml:min' and 	position()!=last()]">
+		<xsl:message>RCAS: MathML mml:apply[mml:min] Applying templates to <xsl:copy-of select="name(.)"/></xsl:message>
+     		<xsl:apply-templates select="."/>
+		<xsl:text>,</xsl:text>
+	</xsl:for-each>
+     	<xsl:apply-templates select="child::*[name()!='mml:condition' and	name()!='mml:bvar' and 	name()!='mml:min' and 	position()=last()]"/>
+	<!-- If there is a condition, do not close... -->	
+	<xsl:if test="mml:condition">
+     		<xsl:text>|</xsl:text><xsl:apply-templates select="mml:condition"/>
+	</xsl:if>
+     	<xsl:text>\right\}</xsl:text>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+
+
+
+
+
+
+
+<!-- APPLY CONTAINING substraction(minus)	-->
+<!-- unary or binary operator			-->
+<xsl:template match="mml:apply[mml:minus]">
+<xsl:text>{</xsl:text>
+<xsl:choose> <!-- binary -->
+	<xsl:when test="count(child::*)=3">
+		<xsl:apply-templates select="child::*[position()=2]"/>
+		<xsl:text>-</xsl:text>
+		<xsl:choose>
+	      	<xsl:when test="((name(*[position()=3])='mml:ci' or name(*[position()=3])='mml:cn') and contains(*[position()=3]/text(),'-')) or (name(*[position()=3])='mml:apply')">
+			<xsl:text>\left(</xsl:text> <xsl:apply-templates select="*[position()=3]"/><xsl:text>\right)</xsl:text>
+			<!-- surround negative or complex things with brackets -->
+			</xsl:when>
+	      	<xsl:otherwise>
+      	  		<xsl:apply-templates select="*[position()=3]"/>
+		      </xsl:otherwise>
+		</xsl:choose>
+	</xsl:when>
+	<xsl:otherwise> <!-- unary -->
+		<xsl:text>-</xsl:text>
+		<xsl:choose>
+    		<xsl:when test=
+			"((name(*[position()=2])='mml:ci' or name(*[position()=2])='mml:cn') and contains(*[position()=2]/text(),'-')) or (name(*[position()=2])='mml:apply')">
+			<xsl:text>\left(</xsl:text>
+				<xsl:apply-templates select="child::*[position()=last()]"/>
+			<xsl:text>\right)</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:apply-templates select="child::*[position()=last()]"/>
+		</xsl:otherwise>
+		</xsl:choose>
+	</xsl:otherwise>
+</xsl:choose>
+<xsl:text>}</xsl:text>
+</xsl:template>
+
+
+<!-- addition -->
+<xsl:template match="mml:apply[mml:plus]">
+  <xsl:choose>
+  <xsl:when test="count(child::*)>=3">
+    <mrow>
+      <xsl:choose>
+        <xsl:when test="((name(*[position()=2])='mml:ci' or name(*[position()=2])='mml:cn') and contains(*[position()=2]/text(),'-')) or (*[position()=2 and self::mml:apply and child::mml:minus])">
+          <mfenced separators=""><xsl:apply-templates select="*[position()=2]"/></mfenced> <!-- surround negative things with brackets -->
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:apply-templates select="*[position()=2]"/>
+        </xsl:otherwise>
+      </xsl:choose>
+      <xsl:for-each select="child::*[position()!=1 and position()!=2]">
+        <xsl:choose>
+        <xsl:when test="((name(.)='mml:ci' or name(.)='mml:cn') and contains(./text(),'-')) or (self::mml:apply and child::mml:minus)"> <!-- surround negative things with brackets -->
+          <mo>+</mo><mfenced separators=""><xsl:apply-templates select="."/></mfenced>
+        </xsl:when>
+        <xsl:otherwise>
+          <mo>+</mo><xsl:apply-templates select="."/>
+        </xsl:otherwise>
+        </xsl:choose>
+      </xsl:for-each>
+    </mrow>
+  </xsl:when>
+  <xsl:when test="count(child::*)=2">
+    <mrow>
+      <mo>+</mo><xsl:apply-templates select="child::*[position()=2]"/>
+    </mrow>
+  </xsl:when>
+  <xsl:otherwise>
+    <mo>+</mo>
+  </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- power -->
+<xsl:template match="mml:apply[mml:power]">
+	<xsl:text> {</xsl:text>
+	<xsl:choose>
+		<xsl:when test="name(*[position()=2])='mml:apply'">
+			<xsl:text>\left(</xsl:text>
+			<xsl:apply-templates select="child::*[position()=2]"/>
+			<xsl:text>\rigth)</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:apply-templates select="child::*[position()=2]"/>
+		</xsl:otherwise>
+	</xsl:choose>
+	<xsl:text>}^{</xsl:text>
+		<xsl:apply-templates select="child::*[position()=3]"/>
+	<xsl:text>} </xsl:text>
+</xsl:template>
+
+<!-- remainder -->
+<xsl:template match="mml:apply[mml:rem]">
+  <mrow>
+    <xsl:choose> <!-- surround with brackets if operands are composed-->
+    <xsl:when test="name(*[position()=2])='mml:apply'">
+      <mfenced separators=""><xsl:apply-templates select="*[position()=2]"/></mfenced>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates select="*[position()=2]"/>
+    </xsl:otherwise>
+    </xsl:choose>
+    <mo>mod</mo>
+    <xsl:choose>
+    <xsl:when test="name(*[position()=3])='mml:apply'">
+      <mfenced separators=""><xsl:apply-templates select="*[position()=3]"/></mfenced>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates select="*[position()=3]"/>
+    </xsl:otherwise>
+    </xsl:choose>
+  </mrow>
+</xsl:template>
+
+<!-- multiplication -->
+<xsl:template match="mml:apply[mml:times]">
+<xsl:choose>
+<xsl:when test="count(child::*)>=3">
+  <mrow>
+    <xsl:for-each select="child::*[position()!=last() and  position()!=1]">
+      <xsl:choose>
+      <xsl:when test="mml:plus"> <!--add brackets around + children for priority purpose-->
+        <mfenced separators=""><xsl:apply-templates select="."/></mfenced><mo><mchar name="InvisibleTimes"/></mo>
+      </xsl:when>
+      <xsl:when test="mml:minus"> <!--add brackets around - children for priority purpose-->
+        <mfenced separators=""><xsl:apply-templates select="."/></mfenced><mo><mchar name="InvisibleTimes"/></mo>
+      </xsl:when>
+      <xsl:when test="(name(.)='mml:ci' or name(.)='mml:cn') and contains(text(),'-')"> <!-- have to do it using contains because starts-with doesn't seem to work well in XT-->
+        <mfenced separators=""><xsl:apply-templates select="."/></mfenced><mo><mchar name="InvisibleTimes"/></mo>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:apply-templates select="."/><mo><mchar name="InvisibleTimes"/></mo>
+      </xsl:otherwise>
+      </xsl:choose>
+    </xsl:for-each>
+    <xsl:for-each select="child::*[position()=last()]">
+      <xsl:choose>
+      <xsl:when test="mml:plus">
+        <mfenced separators=""><xsl:apply-templates select="."/></mfenced>
+      </xsl:when>
+      <xsl:when test="mml:minus">
+        <mfenced separators=""><xsl:apply-templates select="."/></mfenced>
+      </xsl:when>
+      <xsl:when test="(name(.)='mml:ci' or name(.)='mml:cn') and contains(text(),'-')"> <!-- have to do it using contains because starts-with doesn't seem to work well in  XT-->
+        <mfenced separators=""><xsl:apply-templates select="."/></mfenced>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:apply-templates select="."/>
+      </xsl:otherwise>
+      </xsl:choose>
+    </xsl:for-each>
+  </mrow>
+</xsl:when>
+<xsl:when test="count(child::*)=2">  <!-- unary -->
+  <mrow>
+    <mo><mchar name="InvisibleTimes"/></mo>
+    <xsl:choose>
+      <xsl:when test="mml:plus">
+        <mfenced separators=""><xsl:apply-templates select="*[position()=2]"/></mfenced>
+      </xsl:when>
+      <xsl:when test="mml:minus">
+        <mfenced separators=""><xsl:apply-templates select="*[position()=2]"/></mfenced>
+      </xsl:when>
+      <xsl:when test="(*[position()=2 and self::mml:ci] or *[position()=2 and self::mml:cn]) and contains(*[position()=2]/text(),'-')">
+        <mfenced separators=""><xsl:apply-templates select="*[position()=2]"/></mfenced>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:apply-templates select="*[position()=2]"/>
+      </xsl:otherwise>
+    </xsl:choose>
+  </mrow>
+</xsl:when>
+<xsl:otherwise>  <!-- no operand -->
+  <mo><mchar name="InvisibleTimes"/></mo>
+</xsl:otherwise>
+</xsl:choose>
+</xsl:template>
+
+<!-- root -->
+<xsl:template match="mml:apply[mml:root]">
+  <xsl:choose>
+  <xsl:when test="mml:degree">
+    <xsl:choose>
+    <xsl:when test="mml:degree/mml:cn/text()='2'"> <!--if degree=2 display a standard square root-->
+      <msqrt>
+        <xsl:apply-templates select="child::*[position()=3]"/>
+      </msqrt>
+    </xsl:when>
+    <xsl:otherwise>
+      <mroot>
+        <xsl:apply-templates select="child::*[position()=3]"/>
+        <mrow><xsl:apply-templates select="mml:degree/*"/></mrow>
+      </mroot>
+    </xsl:otherwise>
+    </xsl:choose>
+  </xsl:when>
+  <xsl:otherwise> <!-- no degree specified-->
+    <msqrt>
+      <xsl:apply-templates select="child::*[position()=2]"/>
+    </msqrt>
+  </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<!-- greatest common divisor -->
+<xsl:template match="mml:apply[mml:gcd]">
+  <mrow>
+    <mi>gcd</mi><mo><mchar name="ApplyFunction"/></mo>
+    <mfenced>
+      <xsl:apply-templates select="child::*[position()!=1]"/>
+    </mfenced>
+  </mrow>
+</xsl:template>
+
+<!-- AND -->
+<xsl:template match="mml:apply[mml:and]">
+<mrow>
+  <xsl:choose>
+  <xsl:when test="count(*)>=3"> <!-- at least two operands (common case)-->
+    <xsl:for-each select="child::*[position()!=last() and  position()!=1]">
+      <xsl:choose>
+      <xsl:when test="mml:or"> <!--add brackets around OR children for priority purpose-->
+        <mfenced separators=""><xsl:apply-templates select="."/></mfenced><mo><mchar name="And"/></mo>
+      </xsl:when>
+      <xsl:when test="mml:xor"> <!--add brackets around XOR children for priority purpose-->
+       <mfenced separators=""><xsl:apply-templates select="."/></mfenced><mo><mchar name="And"/></mo> 
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:apply-templates select="."/><mo><mchar name="And"/></mo>
+      </xsl:otherwise>
+      </xsl:choose>
+    </xsl:for-each>
+    <xsl:for-each select="child::*[position()=last()]">
+      <xsl:choose>
+      <xsl:when test="mml:or">
+        <mfenced separators=""><xsl:apply-templates select="."/></mfenced>
+      </xsl:when>
+      <xsl:when test="mml:xor">
+        <mfenced separators=""><xsl:apply-templates select="."/></mfenced>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:apply-templates select="."/>
+      </xsl:otherwise>
+      </xsl:choose>
+    </xsl:for-each>
+  </xsl:when>
+  <xsl:when test="count(*)=2">
+    <mo><mchar name="And"/></mo><xsl:apply-templates select="*[position()=last()]"/>
+  </xsl:when>
+  <xsl:otherwise>
+    <mo><mchar name="And"/></mo>
+  </xsl:otherwise>
+  </xsl:choose>
+</mrow>
+</xsl:template>
+
+<!-- OR -->
+<xsl:template match="mml:apply[mml:or]">
+<mrow>
+  <xsl:choose>
+  <xsl:when test="count(*)>=3">
+    <xsl:for-each select="child::*[position()!=last() and  position()!=1]">
+      <xsl:apply-templates select="."/><mo><mchar name="Or"/></mo>
+    </xsl:for-each>
+    <xsl:apply-templates select="child::*[position()=last()]"/>
+    </xsl:when>
+    <xsl:when test="count(*)=2">
+      <mo><mchar name="Or"/></mo><xsl:apply-templates select="*[position()=last()]"/>
+  </xsl:when>
+  <xsl:otherwise>
+    <mo><mchar name="Or"/></mo>
+  </xsl:otherwise>
+  </xsl:choose>
+</mrow>
+</xsl:template>
+
+<!-- XOR -->
+<xsl:template match="mml:apply[mml:xor]">
+<mrow>
+  <xsl:choose>
+  <xsl:when test="count(*)>=3">
+    <xsl:for-each select="child::*[position()!=last() and  position()!=1]">
+      <xsl:apply-templates select="."/><mo>xor</mo>
+    </xsl:for-each>
+    <xsl:apply-templates select="child::*[position()=last()]"/>
+    </xsl:when>
+    <xsl:when test="count(*)=2">
+      <mo>xor</mo><xsl:apply-templates select="*[position()=last()]"/>
+  </xsl:when>
+  <xsl:otherwise>
+    <mo>xor</mo>
+  </xsl:otherwise>
+  </xsl:choose>
+</mrow>
+</xsl:template>
+
+<!-- NOT -->
+<xsl:template match="mml:apply[mml:not]">
+  <mrow>
+    <mo><mchar name="Not"/></mo>
+    <xsl:choose>
+    <xsl:when test="child::mml:apply"><!--add brackets around OR,AND,XOR children for priority purpose-->
+      <mfenced separators="">
+        <xsl:apply-templates select="child::*[position()=2]"/>
+      </mfenced>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates select="child::*[position()=2]"/>
+    </xsl:otherwise>
+    </xsl:choose>
+  </mrow>
+</xsl:template>
+
+<!-- implies -->
+<xsl:template match="mml:apply[mml:implies]">
+  <mrow>
+    <xsl:apply-templates select="child::*[position()=2]"/>
+    <mo><mchar name="DoubleRightArrow"/></mo>
+    <xsl:apply-templates select="child::*[position()=3]"/>
+  </mrow>
+</xsl:template>
+
+<xsl:template match="mml:reln[mml:implies]">
+  <mrow>
+    <xsl:apply-templates select="child::*[position()=2]"/>
+    <mo><mchar name="DoubleRightArrow"/></mo>
+    <xsl:apply-templates select="child::*[position()=3]"/>
+  </mrow>
+</xsl:template>
+
+<!-- for all-->
+<xsl:template match="mml:apply[mml:forall]">
+  <mrow>
+    <mo><mchar name="ForAll"/></mo>
+    <mrow>
+      <xsl:for-each select="mml:bvar[position()!=last()]">
+        <xsl:apply-templates select="."/><mo>,</mo>
+      </xsl:for-each>
+      <xsl:apply-templates select="mml:bvar[position()=last()]"/>
+    </mrow>
+    <xsl:if test="mml:condition">
+      <mrow><mo>,</mo><xsl:apply-templates select="mml:condition"/></mrow>
+    </xsl:if>
+    <xsl:choose>
+      <xsl:when test="mml:apply">
+        <mo>:</mo><xsl:apply-templates select="mml:apply"/>
+      </xsl:when>
+      <xsl:when test="mml:reln">
+        <mo>:</mo><xsl:apply-templates select="mml:reln"/>
+      </xsl:when>
+    </xsl:choose>
+  </mrow>
+</xsl:template>
+
+<!-- in -->
+<xsl:template match="mml:apply[mml:in]">
+	<xsl:text>{</xsl:text>
+    	<xsl:apply-templates select="child::*[position()=2]"/>
+	<xsl:text>\in</xsl:text>
+    	<xsl:apply-templates select="child::*[position()=3]"/>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+<!-- leq -->
+<xsl:template match="mml:apply[mml:leq]">
+	<xsl:text>{</xsl:text>
+    	<xsl:apply-templates select="child::*[position()=2]"/>
+	<xsl:text>\leq</xsl:text>
+    	<xsl:apply-templates select="child::*[position()=3]"/>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+<!-- geq -->
+<xsl:template match="mml:apply[mml:geq]">
+	<xsl:text>{</xsl:text>
+    	<xsl:apply-templates select="child::*[position()=2]"/>
+	<xsl:text>\geq</xsl:text>
+    	<xsl:apply-templates select="child::*[position()=3]"/>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+<!-- domain -->
+<xsl:template match="mml:apply[mml:domain]">
+	<xsl:text>\mbox{dom}(</xsl:text>
+   	<xsl:apply-templates select="child::*[position()=2]"/>
+	<xsl:text>)</xsl:text>
+</xsl:template>
+
+<!-- notin -->
+<xsl:template match="mml:apply[mml:notin]">
+	<xsl:text>{</xsl:text>
+    	<xsl:apply-templates select="child::*[position()=2]"/>
+	<xsl:text>\notin</xsl:text>
+    	<xsl:apply-templates select="child::*[position()=3]"/>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+<!-- exist-->
+<xsl:template match="mml:apply[mml:exists]">
+  <mrow>
+    <mo><mchar name="Exists"/></mo>
+    <mrow>
+      <xsl:for-each select="mml:bvar[position()!=last()]">
+        <xsl:apply-templates select="."/><mo>,</mo>
+      </xsl:for-each>
+      <xsl:apply-templates select="mml:bvar[position()=last()]"/>
+    </mrow>
+    <xsl:if test="mml:condition">
+      <mrow><mo>,</mo><xsl:apply-templates select="mml:condition"/></mrow>
+    </xsl:if>
+    <xsl:choose>
+      <xsl:when test="mml:apply">
+        <mo>:</mo><xsl:apply-templates select="mml:apply"/>
+      </xsl:when>
+      <xsl:when test="mml:reln">
+        <mo>:</mo><xsl:apply-templates select="mml:reln"/>
+      </xsl:when>
+    </xsl:choose>
+  </mrow>
+</xsl:template>
+
+<!-- absolute value -->
+<xsl:template match="mml:apply[mml:abs]">
+  <mrow><mo>|</mo><xsl:apply-templates select="child::*[position()=last()]"/><mo>|</mo></mrow>
+</xsl:template>
+
+<!-- conjugate -->
+<xsl:template match="mml:apply[mml:conjugate]">
+  <mover>
+    <xsl:apply-templates select="child::*[position()=2]"/>
+    <mo><mchar name="ovbar"/></mo>  <!-- does not work, UNICODE x0233D  or perhaps OverBar-->
+  </mover>
+</xsl:template>
+
+<!-- argument of complex number -->
+<xsl:template match="mml:apply[mml:arg]">
+  <mrow>
+    <mi>arg</mi><mo><mchar name="ApplyFunction"/></mo><mfenced separators=""><xsl:apply-templates select="child::*[position()=2]"/></mfenced>
+  </mrow>
+</xsl:template>
+
+<!-- real part of complex number -->
+<xsl:template match="mml:apply[mml:real]">
+  <mrow>
+    <mi><xsl:text disable-output-escaping='yes'>&amp;#x0211C;</xsl:text><!-- mchar Re or realpart should work--></mi>
+    <mo><mchar name="ApplyFunction"/></mo>
+    <mfenced separators=""><xsl:apply-templates select="child::*[position()=2]"/></mfenced>
+  </mrow>
+</xsl:template>
+
+<!-- imaginary part of complex number -->
+<xsl:template match="mml:apply[mml:imaginary]">
+  <mrow>
+    <mi><xsl:text disable-output-escaping='yes'>&amp;#x02111;</xsl:text><!-- mchar Im or impart should work--></mi>
+    <mo><mchar name="ApplyFunction"/></mo>
+    <mfenced separators=""><xsl:apply-templates select="child::*[position()=2]"/></mfenced>
+  </mrow>
+</xsl:template>
+
+<!-- lowest common multiple -->
+<xsl:template match="mml:apply[mml:lcm]">
+  <mrow>
+    <mi>lcm</mi><mo><mchar name="ApplyFunction"/></mo>
+    <mfenced>
+      <xsl:apply-templates select="child::*[position()!=1]"/>
+    </mfenced>
+  </mrow>
+</xsl:template>
+
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.mod.xsl
new file mode 100644
index 00000000000..29d9d826828
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.mod.xsl
@@ -0,0 +1,99 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet
+[
+ <!ENTITY % mmlalias PUBLIC "MathML alias" "ent/mmlalias.ent">  %mmlalias;
+ <!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent">  %mmlextra;
+]>
+<!--############################################################################# 
+ |	$Id: mathml.content.mod.xsl,v 1.1.1.1 2003/03/14 10:42:54 rcasellas Exp $		
+ |- #############################################################################
+ |	$Author: rcasellas $												
+ |														
+ |   PURPOSE: MathML content markup.
+ |	Note: these elements are not part of the DocBook DTD. I have extended
+ |    the docbook DTD in order to support this tags, so that's why I have these 
+ |	templates here.
+ |   
+ |	MathML namespace used -> mml
+ + ############################################################################## -->
+
+<xsl:stylesheet version='1.0'
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
+	xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns="http://www.w3.org/1998/Math/MathML">
+
+<xsl:template match="mml:semantics">
+</xsl:template>
+
+
+<xsl:template match="mml:set|mml:list">
+</xsl:template>
+
+
+<xsl:template match="mml:matrix">
+</xsl:template>
+
+<xsl:template match="mml:reln">
+</xsl:template>
+
+<xsl:template match="mml:lambda">
+</xsl:template>
+
+
+
+
+
+
+<!-- Interval -->
+<!-- att. closure : open, closed, open-closed, or closed-open, with a default value of closed. -->
+<xsl:template match="mml:interval">
+<xsl:choose>
+	<xsl:when test="@closure = 'open'">		
+		<xsl:call-template name="interval.render">
+		<xsl:with-param name="node" select="."/>
+		<xsl:with-param name="fst">\left( </xsl:with-param>
+		<xsl:with-param name="scd">\right) </xsl:with-param>
+		</xsl:call-template>
+	</xsl:when>
+	<xsl:when test="@closure = 'open-closed'">	
+		<xsl:call-template name="interval.render">
+		<xsl:with-param name="node" select="."/>
+		<xsl:with-param name="fst">\left( </xsl:with-param>
+		<xsl:with-param name="scd">\right] </xsl:with-param>
+		</xsl:call-template>
+	</xsl:when>
+	<xsl:when test="@closure = 'closed-open'">	
+		<xsl:call-template name="interval.render">
+		<xsl:with-param name="node" select="."/>
+		<xsl:with-param name="fst">\left[ </xsl:with-param>
+		<xsl:with-param name="scd">\right) </xsl:with-param>
+		</xsl:call-template>
+	</xsl:when>
+	<xsl:otherwise> 
+		<xsl:call-template name="interval.render">
+		<xsl:with-param name="node" select="."/>
+		<xsl:with-param name="fst">\left[ </xsl:with-param>
+		<xsl:with-param name="scd">\right] </xsl:with-param>
+		</xsl:call-template>
+	</xsl:otherwise>
+</xsl:choose>
+</xsl:template>
+
+<xsl:template name="interval.render">
+<xsl:param name="node"/>
+<xsl:param name="fst"/>
+<xsl:param name="scd"/>
+<xsl:choose>
+	<!-- Two real numbers define the interval -->
+	<xsl:when test="count(child::*) = 2">
+		<xsl:value-of select="$fst"/>
+		<xsl:apply-templates select="$node/child::*[1]"/>
+		<xsl:text> , </xsl:text>
+		<xsl:apply-templates select="$node/child::*[2]"/>
+		<xsl:value-of select="$scd"/>
+	</xsl:when>
+	<!-- A condition defines the interval -->
+	<xsl:otherwise> </xsl:otherwise>
+</xsl:choose>
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.token.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.token.mod.xsl
new file mode 100644
index 00000000000..c36ca7162b5
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.content.token.mod.xsl
@@ -0,0 +1,232 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet
+[
+ <!ENTITY % mmlalias PUBLIC "MathML alias" "ent/mmlalias.ent">  %mmlalias;
+ <!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent">  %mmlextra;
+]>
+<!--############################################################################# 
+ |	$Id: mathml.content.token.mod.xsl,v 1.1.1.1 2003/03/14 10:42:54 rcasellas Exp $
+ |- #############################################################################
+ |	$Author: rcasellas $												
+ |	
+ |	PURPOSE: MathML Content Markup, tokens (ci, cn, csymbol)
+ |	MathML namespace used -> mml
+ + ############################################################################## -->
+
+<xsl:stylesheet version='1.0'
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
+	xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns="http://www.w3.org/1998/Math/MathML">
+
+<xsl:strip-space elements="mml:math mml:mrow"/>
+
+
+<!-- Content Number --> 
+<!-- support for bases and types-->
+<xsl:template match="mml:cn">
+	<xsl:text>{</xsl:text>
+	<xsl:text>{</xsl:text>
+      	<xsl:choose>  
+      	<xsl:when test="./@type='complex-cartesian' or ./@type='complex'">
+        		<mn><xsl:value-of select="text()[position()=1]"/></mn>
+			<xsl:choose>
+				<xsl:when test="contains(text()[position()=2],'-')">
+	  				<xsl:text>-</xsl:text><xsl:value-of select="substring-after(text()[position()=2],'-')"/>
+	  			<!--	substring-after does not seem to work well in XT :
+					if imaginary part is expressed with at least one space char 
+					before the minus sign, then it does not work (we end up with 
+					two minus sign since the one in the text is kept)-->
+				</xsl:when>
+				<xsl:otherwise>
+	  				<xsl:text>+</xsl:text> <xsl:value-of select="text()[position()=2]"/>
+				</xsl:otherwise>
+			</xsl:choose>
+			<xsl:text>\dot\textrm{i}</xsl:text>
+		</xsl:when>
+      	<xsl:when test="./@type='complex-polar'">
+        		<xsl:text>\textrm{Polar}(</xsl:text><xsl:value-of select="text()[position()=1]"/><xsl:text>,</xsl:text>
+						<xsl:value-of select="text()[position()=2]"/>
+        		<xsl:text>)</xsl:text>
+		</xsl:when>
+		<xsl:when test="./@type='rational'">
+        		<xsl:text>\frac{</xsl:text><xsl:value-of select="text()[position()=1]"/><xsl:text>}{</xsl:text>
+				<xsl:value-of select="text()[position()=2]"/>
+			<xsl:text>}</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:value-of select="."/>
+		</xsl:otherwise>
+	</xsl:choose>
+	<xsl:text>}</xsl:text>
+	<xsl:if test="@base and @base!=10">  <!-- base specified and different from 10 ; if base = 10 we do not display it -->
+			<xsl:text>_{</xsl:text><xsl:value-of select="@base"/><xsl:text>}</xsl:text>
+	</xsl:if>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+
+
+<!-- Content Identifier --> 
+<!-- identifier -->
+<!--support for presentation markup-->
+<xsl:template match="mml:ci">
+<xsl:choose>  
+<xsl:when test="./@type='complex-cartesian' or ./@type='complex'">
+    	<xsl:choose>
+    		<xsl:when test="count(*)>0">  <!--if identifier is composed of real+imag parts-->
+			<xsl:text>{</xsl:text>
+			<xsl:choose>
+				<xsl:when test="*[self::mml:mchar and position()=1]">  <!-- if real part is an mchar -->
+          				<xsl:text>\textrm{</xsl:text><xsl:copy-of select="*[position()=1]"/><xsl:text>}</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>  <!-- if real part is simple text -->
+          				<xsl:text>\textrm{</xsl:text><xsl:copy-of select="*[position()=1]"/><xsl:text>}</xsl:text>
+        			</xsl:otherwise>
+			</xsl:choose>
+			<xsl:choose> <!-- im part is negative-->
+				<xsl:when test="contains(text()[preceding-sibling::*[position()=1 and self::mml:sep]],'-')">
+          				<xsl:text>-\textrm{</xsl:text>
+					<xsl:choose>
+						<xsl:when test="mml:mchar[preceding-sibling::*[self::mml:sep]]"><!-- if im part is an mchar -->
+							<xsl:copy-of select="mml:mchar[preceding-sibling::*[self::mml:sep]]"/>
+						</xsl:when>
+						<xsl:otherwise><!-- if im part is simple text -->
+							<xsl:value-of select="substring-after(text()[preceding-sibling::*[position()=1 and self::mml:sep]],'-')"/>
+						</xsl:otherwise>
+					</xsl:choose>
+					<xsl:text>}</xsl:text>
+					<xsl:text>\dot\textrm{i}</xsl:text>
+				</xsl:when>
+				<xsl:otherwise> <!-- im part is not negative-->
+          				<xsl:text>+\textrm{</xsl:text>
+					<xsl:choose><!-- if im part is an mchar -->
+						<xsl:when test="mml:mchar[preceding-sibling::*[self::mml:sep]]">
+							<xsl:copy-of select="mml:mchar[preceding-sibling::*[self::mml:sep]]"/>
+						</xsl:when>
+						<xsl:otherwise><!-- if im part is simple text -->
+							<xsl:value-of select="text()[preceding-sibling::*[position()=1 and self::mml:sep]]"/>
+						</xsl:otherwise>
+					</xsl:choose>
+					<xsl:text>}</xsl:text>
+					<xsl:text>\dot\textrm{i}</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+			<xsl:text>}</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>  <!-- if identifier is composed only of one text child-->
+			<xsl:text>\dot\textrm{</xsl:text><xsl:value-of select="."/><xsl:text>}</xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+</xsl:when>
+<xsl:when test="./@type='complex-polar'">
+    <xsl:choose>
+    <xsl:when test="count(*)>0">   <!--if identifier is composed of real+imag parts-->
+      <xsl:text>{</xsl:text>
+        <mi>Polar</mi>
+        <mfenced><mi>
+        <xsl:value-of select="text()[following-sibling::*[self::mml:sep]]"/>
+        <xsl:if test="mml:mchar[following-sibling::*[self::mml:sep]]">
+          <xsl:copy-of select="mml:mchar[following-sibling::*[self::mml:sep]]"/>
+        </xsl:if>
+        </mi>
+        <mi>
+        <xsl:value-of select="text()[preceding-sibling::*[self::mml:sep]]"/>
+        <xsl:if test="mml:mchar[preceding-sibling::*[self::mml:sep]]">
+          <xsl:copy-of select="mml:mchar[preceding-sibling::*[self::mml:sep]]"/>
+        </xsl:if>
+        </mi></mfenced>
+      <xsl:text>}</xsl:text>
+    </xsl:when>
+    <xsl:otherwise>   <!-- if identifier is composed only of one text child-->
+      <mi><xsl:value-of select="."/></mi>
+    </xsl:otherwise>
+    </xsl:choose>
+</xsl:when> 
+<xsl:when test="./@type='rational'">
+    <xsl:choose>
+    <xsl:when test="count(*)>0"> <!--if identifier is composed of two parts-->
+      <xsl:text>{</xsl:text><mi>
+      <xsl:value-of select="text()[following-sibling::*[self::mml:sep]]"/>
+      <xsl:if test="mml:mchar[following-sibling::*[self::mml:sep]]">
+        <xsl:copy-of select="mml:mchar[following-sibling::*[self::mml:sep]]"/>
+      </xsl:if>
+      </mi>
+      <mo>/</mo>
+      <mi>
+      <xsl:value-of select="text()[preceding-sibling::*[self::mml:sep]]"/>
+      <xsl:if test="mml:mchar[preceding-sibling::*[self::mml:sep]]">
+        <xsl:copy-of select="mml:mchar[preceding-sibling::*[self::mml:sep]]"/>
+      </xsl:if>
+      </mi><xsl:text>}</xsl:text>
+    </xsl:when>
+    <xsl:otherwise>   <!-- if identifier is composed only of one text child-->
+      <mi><xsl:value-of select="."/></mi>
+    </xsl:otherwise>
+    </xsl:choose>
+  </xsl:when>
+  <xsl:when test="./@type='vector'">
+    <mi fontweight="bold">
+      <xsl:value-of select="text()"/>
+      <xsl:if test="mml:mchar">
+        <xsl:copy-of select="mml:mchar"/>
+      </xsl:if>
+    </mi>
+</xsl:when>
+  <!-- type 'set' seems to be deprecated (use 4.4.12 instead); besides, there is no easy way to translate set identifiers to chars in ISOMOPF -->
+<xsl:otherwise>  <!-- no type attribute provided -->
+	<xsl:choose>
+		<xsl:when test="mml:mchar"> <!-- test if identifier is expressed using mchar nodes -->
+      <mi><xsl:value-of select="text()"/><xsl:copy-of select="mml:mchar"/></mi>
+    </xsl:when>
+    <xsl:when test="count(node()) != count(text())">
+      <!--test if children are not all text nodes, meaning there is markup assumed 
+      to be presentation markup (the case where there are mchar nodes has been tested just before)-->
+	<xsl:text>{</xsl:text><xsl:copy-of select="child::*"/><xsl:text>}</xsl:text>
+    </xsl:when>
+    <xsl:otherwise>  <!-- common case -->
+      <mi><xsl:value-of select="."/></mi>
+    </xsl:otherwise>
+    </xsl:choose>
+</xsl:otherwise>
+</xsl:choose>
+</xsl:template>
+
+
+
+
+
+
+<!-- externally defined symbols-->
+<xsl:template match="mml:apply[mml:csymbol]">
+	<xsl:text>{</xsl:text>
+		<xsl:apply-templates select="mml:csymbol[position()=1]"/>
+	<xsl:text>\left(</xsl:text>
+	<xsl:for-each select="child::*[position()!=1]">
+		<xsl:apply-templates select="."/>
+	</xsl:for-each>
+	<xsl:text>\right)</xsl:text>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+
+<xsl:template match="mml:csymbol">
+<xsl:choose>
+	<!--test if children are not all text nodes, meaning there is markup assumed to be presentation markup-->
+	<!--perhaps it would be sufficient to test if there is more than one node or text node-->
+	<xsl:when test="count(node()) != count(text())"> 
+		<xsl:text>{</xsl:text> <xsl:copy-of select="child::*"/> <xsl:text>}</xsl:text>
+	</xsl:when>
+	<xsl:otherwise>
+		<xsl:text>\textrm{</xsl:text> <xsl:copy-of select="."/> <xsl:text>}</xsl:text>
+	</xsl:otherwise>
+</xsl:choose>
+</xsl:template>
+
+<xsl:template match="mml:mchar">
+  <xsl:copy-of select="."/>
+</xsl:template>
+<!--
+<xsl:template match="mml:mtext">
+  <xsl:copy-of select="."/>
+</xsl:template>
+-->
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.mod.xsl
new file mode 100644
index 00000000000..32262afab49
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.mod.xsl
@@ -0,0 +1,48 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet
+[
+ <!ENTITY % mmlalias PUBLIC "MathML alias" "ent/mmlalias.ent">  %mmlalias;
+ <!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent">  %mmlextra;
+]>
+<!--############################################################################# 
+ |	$Id: mathml.mod.xsl,v 1.4 2004/01/18 10:39:23 j-devenish Exp $		
+ |- #############################################################################
+ |	$Author: j-devenish $
+ |														
+ |   PURPOSE: MathML presentation and content markup.
+ |	Note: these elements are not part of the DocBook DTD. I have extended
+ |    the docbook DTD in order to support this tags, so that's why I have these 
+ |	templates here.
+ |   
+ |	MathML namespace used -> mml
+ + ############################################################################## -->
+
+<xsl:stylesheet version='1.0'
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns="http://www.w3.org/1998/Math/MathML">
+
+	<xsl:strip-space elements="mml:math mml:mrow"/>
+
+	<xsl:template match="mml:math">
+		<xsl:text>\begin{displaymath}</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>\end{displaymath}%&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="mml:math[@mode='inline']">
+		<xsl:text>\begin{math}</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>\end{math}</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="mml:math[@mode='display']">
+		<xsl:text>\begin{displaymath}</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>\end{displaymath}%&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="p">
+		<xsl:text>\section{</xsl:text> <xsl:value-of select="normalize-space(.)"/> <xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.presentation.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.presentation.mod.xsl
new file mode 100644
index 00000000000..a3a67e17beb
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mathml/mathml.presentation.mod.xsl
@@ -0,0 +1,493 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet
+[
+ <!ENTITY % mmlalias PUBLIC "MathML alias" "ent/mmlalias.ent">  %mmlalias;
+ <!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent">  %mmlextra;
+]>
+<!--############################################################################# 
+ |	$Id: mathml.presentation.mod.xsl,v 1.4 2004/01/18 10:39:50 j-devenish Exp $		
+ |- #############################################################################
+ |	$Author: j-devenish $												
+ |														
+ |   PURPOSE: MathML presentation markup.
+ |	Note: these elements are not part of the DocBook DTD. I have extended
+ |    the docbook DTD in order to support this tags, so that's why I have these 
+ |	templates here.
+ |   
+ |	MathML namespace used -> mml
+ + ############################################################################## -->
+
+<xsl:stylesheet version='1.0'
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
+	xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns="http://www.w3.org/1998/Math/MathML">
+
+<xsl:template match="mml:mrow">
+	<xsl:text>{</xsl:text> <xsl:apply-templates/> <xsl:text>}</xsl:text>
+</xsl:template>
+
+<xsl:variable name="latex.entities.xml" select="document('latex.entities.xml')"/>
+
+
+<!-- TOKENS -->
+<!-- Math Identifier -->
+<xsl:template match="mml:mi">
+	<xsl:variable name="fontstyle" select="@fontstyle"/>
+	<xsl:variable name="identifier" select="normalize-space(.)"/>
+	<xsl:variable name="equivalent">
+		<xsl:if test="string-length($identifier)=1">
+			<xsl:value-of select="$latex.entities.xml/latex/character[@entity=$identifier]"/>
+		</xsl:if>
+	</xsl:variable>
+	<xsl:choose>
+		<xsl:when test="$identifier='&ExponentialE;'">
+			<xsl:text>\textrm{e}</xsl:text>
+		</xsl:when>
+		<xsl:when test="$identifier='&ImaginaryI;'">
+			<xsl:text>\textrm{i}</xsl:text>
+		</xsl:when>
+		<xsl:when test="$identifier='&#x0221E;'"><!--/infty infinity -->
+			<xsl:text>\infty</xsl:text>
+		</xsl:when>
+		<!-- currently tries to map single-character identifiers only -->
+		<xsl:when test="$equivalent!=''">
+			<xsl:text>{</xsl:text>
+			<xsl:copy-of select="$equivalent"/>
+			<xsl:text>}</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:if test="$fontstyle='normal' or string-length($identifier)&gt;1">
+				<xsl:text>\textrm</xsl:text>
+			</xsl:if>
+			<xsl:text>{</xsl:text>
+			<xsl:copy-of select="$identifier"/>
+			<xsl:text>}</xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+</xsl:template>
+
+<!-- Math Number -->
+<xsl:template match="mml:mn">
+	<xsl:copy-of select="normalize-space(.)"/>
+</xsl:template>
+
+<!-- Math Phantom -->
+<xsl:template match="mml:mphantom">
+	<xsl:apply-templates/>
+</xsl:template>
+
+<!-- Empty unless $character is a single character -->
+<xsl:template name="generate.equivalent">
+	<xsl:param name="arguments" select="0"/>
+	<xsl:param name="character"/>
+	<xsl:if test="string-length($character)=1">
+		<xsl:choose>
+			<xsl:when test="$arguments&gt;0">
+				<xsl:value-of select="$latex.entities.xml/latex/character[@entity=$character and @arguments=$arguments]"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="$latex.entities.xml/latex/character[@entity=$character and @arguments='']"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:if>
+</xsl:template>
+
+<!-- Math Operator -->
+<xsl:template match="mml:mo">
+	<xsl:variable name="operator" select="normalize-space(.)"/>
+	<xsl:variable name="equivalent">
+		<xsl:call-template name="generate.equivalent">
+			<xsl:with-param name="character" select="$operator"/>
+		</xsl:call-template>
+	</xsl:variable>
+	<xsl:choose>
+		<xsl:when test="$operator='&ApplyFunction;'">
+			<xsl:text></xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&InvisibleComma;'">
+			<xsl:text>\thinspace</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&InvisibleTimes;'">
+			<xsl:text>\thinspace</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&Integral;'">
+			<xsl:text>\int</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&Product;'">
+			<xsl:text>\prod</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&Sum;'">
+			<xsl:text>\sum</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&Hat;'">
+			<xsl:text>\sphat</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&RightArrow;'">
+			<xsl:text>\longrightarrow</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&Element;'">
+			<xsl:text>\in</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&VerticalBar;'">
+			<xsl:text>|</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='&DifferentialD;'">
+			<xsl:text>\textrm{d}</xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='('">
+			<xsl:text> {\left( </xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator=')'">
+			<xsl:text> \right)} </xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='{'">
+			<xsl:text> {\left\{ </xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='}'">
+			<xsl:text> \right\}} </xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='['">
+			<xsl:text> {\left[ </xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator=']'">
+			<xsl:text> \right]} </xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='max'">
+			<xsl:text> \max </xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='min'">
+			<xsl:text> \min </xsl:text>
+		</xsl:when>
+		<xsl:when test="$operator='+' or $operator='-' or $operator='/' or $operator='*'">
+			<xsl:value-of select="$operator"/>
+		</xsl:when>
+		<xsl:when test="$equivalent">
+			<xsl:value-of select="$equivalent"/>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:text>\operatorname{</xsl:text>
+			<xsl:value-of select="$operator" />
+			<xsl:text>}</xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+</xsl:template>
+
+<!-- Math String -->
+<xsl:template match="mml:ms">
+	<xsl:text>\textrm{</xsl:text>
+	<xsl:copy-of select="normalize-space(.)" />
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+<!-- Math Text -->
+<xsl:template match="mml:mtext">
+	<xsl:message>RCAS mtext, <xsl:copy-of select="."/> </xsl:message>
+	<xsl:text>\textrm{</xsl:text>
+	<xsl:copy-of select="." />
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+<!-- Math Space -->
+<xsl:template match="mml:mspace">
+	<xsl:if test="@width!='' and not(contains(@width,'%'))">
+		<xsl:text>\textrm{\hspace{</xsl:text><!-- kludge! -->
+		<xsl:value-of select="@width"/>
+		<xsl:text>}}</xsl:text>
+	</xsl:if>
+	<xsl:if test="@height!='' or @depth!=''">
+		<xsl:message>Warning: mspace support does not include height or depth.</xsl:message>
+	</xsl:if>
+</xsl:template>
+
+
+
+
+
+<xsl:template match="mml:msup">
+        <xsl:apply-templates select="*[1]"/>
+        <xsl:text>^{</xsl:text><xsl:apply-templates select="*[2]"/><xsl:text>}</xsl:text>
+</xsl:template>
+
+<xsl:template match="mml:msub">
+        <xsl:apply-templates select="*[1]"/>
+        <xsl:text>_{</xsl:text><xsl:apply-templates select="*[2]"/><xsl:text>}</xsl:text>
+</xsl:template>
+
+<xsl:template match="mml:msubsup">
+<xsl:choose>
+	<xsl:when test="name(*[1])='mo'">
+		<xsl:apply-templates select="*[1]"/>
+		<!-- sub -->
+		<xsl:text>_{</xsl:text><xsl:apply-templates select="*[2]"/><xsl:text>}</xsl:text>
+		<!-- super -->
+		<xsl:text>^{</xsl:text><xsl:apply-templates select="*[3]"/><xsl:text>}</xsl:text>
+     </xsl:when>
+     <xsl:otherwise>
+	     	<!-- base -->
+		<xsl:text>{</xsl:text><xsl:apply-templates select="*[1]"/><xsl:text>}</xsl:text>
+		<!-- sub -->
+		<xsl:text>_{</xsl:text><xsl:apply-templates select="*[2]"/><xsl:text>}</xsl:text>
+		<!-- super -->
+		<xsl:text>^{</xsl:text><xsl:apply-templates select="*[3]"/><xsl:text>}</xsl:text>
+	</xsl:otherwise>
+</xsl:choose>
+</xsl:template>
+
+<xsl:template match="mml:mmultiscripts">
+</xsl:template>
+
+<xsl:template match="mml:munder">
+<!--
+<xsl:choose>
+	<xsl:when test="*[2] = &#818;">
+		<xsl:text>\underline{</xsl:text><xsl:apply-templates select="*[1]"/><xsl:text>}</xsl:text>
+	</xsl:when>
+	<xsl:when test="normalize-space(*[2]) = &#65080;">
+		<xsl:text>\underbrace{</xsl:text><xsl:apply-templates select="*[1]"/><xsl:text>}</xsl:text>
+	</xsl:when>
+	<xsl:when test="normalize-space(*[2]) = &#9141;">
+		<xsl:text>\underbrace{</xsl:text><xsl:apply-templates select="*[1]"/><xsl:text>}</xsl:text>
+	</xsl:when>
+	<xsl:otherwise>
+	<xsl:text>\underset{</xsl:text>
+		<xsl:apply-templates select="*[2]"/>
+	<xsl:text>}{</xsl:text>
+		<xsl:apply-templates select="*[1]"/>
+	<xsl:text>}</xsl:text>
+-->
+	<xsl:text>{</xsl:text>
+	<xsl:apply-templates select="*[1]"/>
+	<xsl:text>_{</xsl:text>
+	<xsl:apply-templates select="*[2]"/>
+	<xsl:text>}}</xsl:text>
+<!--
+	</xsl:otherwise>
+</xsl:choose>
+-->
+</xsl:template>
+<xsl:template match="mml:mover">
+<!--<xsl:choose>
+	<xsl:when test="normalize-space(*[2]) = &#175;">
+		<xsl:text>\overline{</xsl:text><xsl:apply-templates select="*[1]"/><xsl:text>}</xsl:text>
+	</xsl:when>
+	<xsl:when test="normalize-space(*[2]) = &#65079;"> 
+		<xsl:text>\overbrace{</xsl:text><xsl:apply-templates select="*[1]"/><xsl:text>}</xsl:text>
+	</xsl:when>
+	<xsl:when test="normalize-space(*[2]) = &#65077;"> 
+		<xsl:text>\widehat{</xsl:text><xsl:apply-templates select="*[1]"/><xsl:text>}</xsl:text>
+	</xsl:when>
+	<xsl:when test="normalize-space(*[2]) = &#9140;">
+		<xsl:text>\widehat{</xsl:text><xsl:apply-templates select="*[1]"/><xsl:text>}</xsl:text>
+	</xsl:when>
+	<xsl:otherwise>
+	</xsl:otherwise>
+</xsl:choose>-->
+	<xsl:choose>
+		<xsl:when test="@accent='true' or ( local-name(*[2])='mo' and not(@accent='false'))">
+			<xsl:variable name="equivalent">
+				<xsl:call-template name="generate.equivalent">
+					<xsl:with-param name="arguments" select="1"/>
+					<xsl:with-param name="character" select="normalize-space(*[2])"/>
+				</xsl:call-template>
+			</xsl:variable>
+			<xsl:choose>
+				<xsl:when test="$equivalent!=''">
+					<xsl:text>{</xsl:text>
+					<xsl:value-of select="$equivalent"/>
+					<xsl:text>{</xsl:text>
+					<xsl:apply-templates select="*[1]"/>
+					<xsl:text>}}</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>{</xsl:text>
+					<xsl:apply-templates select="*[1]"/>
+					<xsl:text>^{</xsl:text>
+					<xsl:apply-templates select="*[2]"/>
+					<xsl:text>}}</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:text>{</xsl:text>
+			<xsl:apply-templates select="*[1]"/>
+			<xsl:text>^{</xsl:text>
+			<xsl:apply-templates select="*[2]"/>
+			<xsl:text>}}</xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+</xsl:template>
+
+
+
+<!-- Math UnderOver -->
+<xsl:template match="mml:munderover">
+	<xsl:text>{</xsl:text>
+	<xsl:apply-templates select="*[1]"/>
+	<xsl:text>_{</xsl:text>
+	<xsl:apply-templates select="*[2]"/>
+	<xsl:text>}</xsl:text>
+	<xsl:text>^{</xsl:text>
+	<xsl:apply-templates select="*[3]"/>
+	<xsl:text>}}</xsl:text>
+	<!--
+	<xsl:text>\overset{</xsl:text>
+			<xsl:apply-templates select="*[3]"/>
+		<xsl:text>}{\underset{</xsl:text>
+				<xsl:apply-templates select="*[2]"/>
+					<xsl:text>}{</xsl:text>
+				<xsl:apply-templates select="*[1]"/>
+	<xsl:text>}}</xsl:text>
+	-->
+</xsl:template>
+
+
+
+<!-- Math Fenced -->
+<xsl:template match="mml:mfenced">
+<!-- get open,close, separators att -->
+	<xsl:choose>
+		<xsl:when test="@open='('">
+			<xsl:text> {\left( </xsl:text>
+		</xsl:when>
+		<xsl:when test="@open='{'">
+			<xsl:text> {\left\{ </xsl:text>
+		</xsl:when>
+		<xsl:when test="@open='['">
+			<xsl:text> {\left[\, </xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:text> {\left( </xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+	<xsl:apply-templates select="*[1]"/>
+	<xsl:choose>
+		<xsl:when test="@close=')'">
+			<xsl:text> \right)} </xsl:text>
+		</xsl:when>
+		<xsl:when test="@close='}'">
+			<xsl:text> \right\}} </xsl:text>
+		</xsl:when>
+		<xsl:when test="@close=']'">
+			<xsl:text> \,\right]} </xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:text> \right)} </xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+</xsl:template>
+
+
+
+<!-- Math frac -->
+<xsl:template match="mml:mfrac">
+<xsl:choose>
+<xsl:when test="@linethickness">
+	<xsl:choose>
+	<xsl:when test="@linethickness='thin'">
+		<xsl:text> \frac[1pt]{ </xsl:text>
+	</xsl:when>
+	<xsl:when test="@linethickness='medium'">
+		<xsl:text> \frac[1.1pt]{ </xsl:text>
+	</xsl:when>
+	<xsl:when test="@linethickness='thick'">
+		<xsl:text> \frac[1.2pt]{ </xsl:text>
+	</xsl:when>
+	<xsl:otherwise>
+		<xsl:text> \frac[</xsl:text><xsl:value-of select="@linethickness"/><xsl:text>]{ </xsl:text>
+	</xsl:otherwise>
+	</xsl:choose>
+</xsl:when>
+<xsl:otherwise>
+	<xsl:text> \frac{ </xsl:text>
+</xsl:otherwise>
+</xsl:choose>
+<!--	<xsl:value-of select="*[1]"/> -->
+<xsl:apply-templates select="*[1]"/>
+<xsl:text> }{ </xsl:text>
+<!--	<xsl:value-of select="*[2]"/> -->
+<xsl:apply-templates select="*[2]"/>
+<xsl:text> }</xsl:text>
+</xsl:template>
+
+
+<!-- Math msqrt -->
+<xsl:template match="mml:msqrt">
+	<xsl:text> \sqrt{ </xsl:text>
+	<xsl:apply-templates/>
+	<xsl:text> }</xsl:text>
+</xsl:template>
+
+
+<!-- Math mroot -->
+<xsl:template match="mml:mroot">
+	<xsl:text> \sqrt[</xsl:text><xsl:apply-templates select="*[1]"/><xsl:text>]{</xsl:text>
+		<xsl:apply-templates select="*[2]"/><xsl:text> }</xsl:text>
+</xsl:template>
+
+
+
+<xsl:template name="mtable.format.tabular">
+  	<xsl:param name="cols" select="1"/>
+	<xsl:param name="i" select="1"/>
+  	<xsl:choose>
+		<!-- Out of the recursive iteration -->
+    		<xsl:when test="$i > $cols"></xsl:when>
+		<!-- There are still columns to count -->
+    		<xsl:otherwise>
+        		<xsl:text>c</xsl:text>
+				<!-- Recursive for next column -->
+      			<xsl:call-template name="mtable.format.tabular">
+        				<xsl:with-param name="i" select="$i+1"/>
+        				<xsl:with-param name="cols" select="$cols"/>
+      			</xsl:call-template>
+    		</xsl:otherwise>
+	</xsl:choose>
+</xsl:template>
+
+
+<xsl:template match="mml:mtable">
+<xsl:variable name="rows" select="mml:mtr"/>
+<xsl:text>\begin{array}{</xsl:text>
+<xsl:call-template name="mtable.format.tabular"><xsl:with-param name="cols" select="count($rows)"/></xsl:call-template>
+<xsl:text>}&#10;</xsl:text>
+	<xsl:apply-templates/>
+<xsl:text>\end{array} </xsl:text>
+</xsl:template>
+
+<xsl:template match="mml:mtr">
+<!-- Row starts here -->
+<xsl:apply-templates/>
+<!-- End Row here -->
+</xsl:template>
+
+<xsl:template match="mml:mtd">
+    <xsl:apply-templates/><xsl:text> &amp; </xsl:text> 
+</xsl:template>
+
+<xsl:template match="mml:mtd[position()=last()]">
+    <xsl:apply-templates/><xsl:text>\\&#10;</xsl:text>
+</xsl:template>
+
+<xsl:template match="mml:mtd[position()=last()]">
+    <xsl:apply-templates/><xsl:text>\\&#10;</xsl:text>
+</xsl:template>
+
+<xsl:template match="mml:mphantom">
+    <xsl:apply-templates mode="phantom"/>
+</xsl:template>
+
+<xsl:template match="mml:mi" mode="phantom">
+	<xsl:variable name="fontstyle" select="@fontstyle"/>
+	<xsl:variable name="identifier" select="normalize-space(.)"/>
+	<xsl:choose>
+		<xsl:when test="$identifier='&ExponentialE;'">
+			<xsl:text>\textrm{e}</xsl:text>
+		</xsl:when>
+		<xsl:when test="$identifier='&ImaginaryI;'">
+			<xsl:text>\textrm{i}</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:text>\textrm{</xsl:text> <xsl:copy-of select="$identifier"/> <xsl:text>}</xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+</xsl:template>
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/mediaobject.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/mediaobject.mod.xsl
new file mode 100644
index 00000000000..b0a0bc5bd41
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/mediaobject.mod.xsl
@@ -0,0 +1,350 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: mediaobject.mod.xsl,v 1.22 2004/01/12 13:52:30 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="mediaobject" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: mediaobject.mod.xsl,v 1.22 2004/01/12 13:52:30 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.12">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>MediaObjects <filename>mediaobject.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>textobject</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="textobject">
+		<!-- TODO if mixed in with imageobjects, use subfigure (if appropriate) -->
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template basename="mediaobject" xmlns="">
+		<refpurpose>Process <doc:db>mediaobject</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Calls <xref linkend="template.mediacontent"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_subfig;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="mediaobject">
+		<xsl:if test="local-name(preceding-sibling::*[1])!='mediaobject'">
+			<xsl:text>&#10;</xsl:text>
+		</xsl:if>
+		<xsl:call-template name="mediacontent"/>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="mediaobject" xmlns="">
+		<refpurpose>Process a <doc:db>para</doc:db>'s <doc:db>mediaobject</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a <doc:db>mediaobject</doc:db> as a block surrounded by paragraph text.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Inserts newline characters around the output of <xref
+				linkend="template.mediacontent"/>.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="para/mediaobject">
+		<xsl:text>&#10;&#10;</xsl:text>
+		<xsl:call-template name="mediacontent"/>
+		<xsl:text>&#10;&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>inlinemediaobject</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="inlinemediaobject">
+		<xsl:call-template name="mediacontent"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process media and inline media </refpurpose>
+		<doc:description>
+			<para>
+				Formats image media.
+				Would be good to be able to include text media, too,
+				so that mixed-content figures look proper.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				The template first attempts to obtain a count of the number
+				of media within this <doc:db>figure</doc:db>, if this is within a <sgmltag>figure</sgmltag>.
+				If the number of objects is greater than one, a <function condition="latex">subfigure</function>
+				command will be invoked with the contents of any <doc:db>caption</doc:db>.
+				If there are no <doc:db basename="imageobject">imageobjects</doc:db>, <doc:db basename="textobject">textobjects</doc:db>
+				will be selected.
+				Otherwise, the following algorithm will be used:
+			</para>
+			<procedure>
+				<step><simpara>If <xref linkend="param.use.role.for.mediaobject"/> is set and there is an <doc:db>imageobject</doc:db> with a <sgmltag class="attribute">role</sgmltag> equal to the current <xref linkend="param.preferred.mediaobject.role"/> then that object will be used.</simpara></step>
+				<step><simpara>Otherwise, if <xref linkend="param.use.role.for.mediaobject"/> is set and there is an <sgmltag>imageobject</sgmltag> with a role of <quote>latex</quote> or <quote>tex</quote>, that object will be used.</simpara></step>
+				<step><simpara>Otherwise, if <xref linkend="param.latex.graphics.formats"/> is set and there are <sgmltag>imagedata</sgmltag> with non-empty <sgmltag class="attribute">format</sgmltag> attributes, and at least one of them has a matching format, then the first one of those objects is used. If none match, then the first <sgmltag>imagedata</sgmltag> with an <emphasis>empty</emphasis> format is used. Otherwise, the first <doc:db>textobject</doc:db> is used.</simpara></step>
+				<step><simpara>Otherwise, the first <sgmltag>imageobject</sgmltag> is used regardless.</simpara></step>
+			</procedure>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="mediacontent">
+		<!--
+		<xsl:variable name="actualmediacnt" select="count(../../..//mediaobject[imageobject or textobject])"/>
+		-->
+		<xsl:variable name="actualmediacnt" select="count(../mediaobject)"/>
+		<xsl:if test="$actualmediacnt &gt; 1 and $latex.use.subfigure='1' and count(ancestor::figure) &gt; 0">
+			<xsl:text>\subfigure[</xsl:text>
+			<!-- TODO does subfigure stuff up with there are square brackets in here? -->
+			<xsl:if test="caption">
+				<xsl:apply-templates select="caption[1]"/>
+			</xsl:if>
+			<xsl:text>]</xsl:text>
+		</xsl:if>
+		<xsl:text>{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="count(imageobject)&lt;1">
+				<xsl:apply-templates select="textobject[1]"/>
+			</xsl:when>
+			<xsl:when test="$use.role.for.mediaobject='1' and $preferred.mediaobject.role!='' and count(imageobject[@role=$preferred.mediaobject.role])!=0">
+				<xsl:apply-templates select="imageobject[@role=$preferred.mediaobject.role]"/>
+			</xsl:when>
+			<xsl:when test="$use.role.for.mediaobject='1' and count(imageobject[@role='latex'])!=0">
+				<xsl:apply-templates select="imageobject[@role='latex']"/>
+			</xsl:when>
+			<xsl:when test="$use.role.for.mediaobject='1' and count(imageobject[@role='tex'])!=0">
+				<xsl:apply-templates select="imageobject[@role='tex']"/>
+			</xsl:when>
+			<xsl:when test="$latex.graphics.formats!='' and count(imageobject/imagedata[@format!=''])!=0">
+				<!-- this is not really the right method: formats to the left of $latex.graphics.formats
+				should be given higher 'priority' than those to the right in a command-separated list -->
+				<xsl:variable name="formats" select="concat(',',$latex.graphics.formats,',')"/>
+				<xsl:variable name="candidates" select="imageobject/imagedata[contains($formats,concat(',',@format,','))]"/>
+				<xsl:choose>
+					<xsl:when test="count($candidates)!=0">
+						<xsl:apply-templates select="$candidates[1]"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:variable name="fallbacks" select="imageobject/imagedata[@format='']"/>
+						<xsl:choose>
+							<xsl:when test="count($fallbacks)!=0">
+								<xsl:apply-templates select="$fallbacks[1]"/>
+							</xsl:when>
+							<xsl:when test="count(textobject)!=0">
+								<xsl:apply-templates select="textobject[1]"/>
+							</xsl:when>
+							<xsl:otherwise>
+								<xsl:apply-templates select="imageobject[1]"/>
+							</xsl:otherwise>
+						</xsl:choose>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:apply-templates select="imageobject[1]"/>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="imageobject" xmlns="">
+		<refpurpose>Process <doc:db>imageobject</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="imageobject">
+		<xsl:apply-templates select="imagedata"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>imagedata</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a picture using <function condition="latex">includegraphics</function>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>filename</term>
+					<listitem><simpara>The file path to be passsed to <function
+					condition="latex">includegraphics</function>. By default,
+					the name of the graphics file is gathered from the <sgmltag
+					class="attribute">entityref</sgmltag> attribute, if it is
+					present, or otherwise from the <sgmltag
+					class="attribute">fileref</sgmltag> attribute.
+					Often with &LaTeX;, the <sgmltag class="attribute">fileref</sgmltag>
+					attribute need not end with any <quote>filename extension</quote>
+					(see <xref linkend="param.graphic.default.extension"/>).
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<itemizedlist>
+				<listitem><para>If both <literal>@width</literal> and <literal>@scale</literal> are given but <literal>@scalefit='0'</literal>, whitespace is added to the left and right in order to match the specified width.</para></listitem>
+				<listitem><para>If <literal>@width</literal> is given and either <literal>@scalefit=1</literal> or no <literal>@scale</literal> is given, then the image is scale to <literal>@width</literal>. Otherwise, <literal>@scale</literal> is used, if it is present.</para></listitem>
+				<listitem><para>If this is not the only <literal>imagedata</literal> within the figure, this will be rendered as a 'subfigure', including the <literal>caption</literal> of its enclosing <literal>mediaobject</literal>.</para></listitem>
+			</itemizedlist>
+			<para>
+				For widths, those containing a percent symbol (<quote>%</quote>) will be
+				taken relative to the <function condition="latex">textwidth</function>.
+			</para>
+			<para>
+				The <quote>PRN</quote> value of the <sgmltag class="attribute">format</sgmltag> attribute is honoured.
+			</para>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.content-templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="imagedata" name="imagedata">
+		<xsl:param name="filename">
+			<xsl:choose>
+				<xsl:when test="@entityref">
+					<xsl:value-of select="unparsed-entity-uri(@entityref)"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="@fileref"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:param name="is.imageobjectco" select="false()"/>
+		<xsl:variable name="width">
+			<xsl:choose>
+				<xsl:when test="contains(@width, '%') and substring-after(@width, '%')=''">
+					<xsl:value-of select="number(substring-before(@width, '%')) div 100"/>
+					<xsl:text>\textwidth</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="@width"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:if test="$width!='' and (@scalefit='0' or count(@scale)&gt;0)">
+			<xsl:text>\makebox[</xsl:text><xsl:value-of select='$width' /><xsl:text>]</xsl:text>
+		</xsl:if>
+		<!-- TODO this logic actually needs to make decisions based on the ALLOWED imagedata,
+		not all the imagedata present in the source file. -->
+		<xsl:choose>
+			<xsl:when test="$is.imageobjectco=1">
+				<xsl:text>{\begin{overpic}[</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>{\includegraphics[</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:choose>
+			<xsl:when test="@scale"> 
+			<xsl:text>scale=</xsl:text>
+			<xsl:value-of select="number(@scale) div 100"/>
+			</xsl:when>
+			<xsl:when test="$width!='' and @scalefit='1'">
+			<xsl:text>width=</xsl:text><xsl:value-of select="normalize-space($width)"/>
+			</xsl:when>
+			<xsl:when test="@depth!='' and @scalefit='1'">
+			<xsl:text>height=</xsl:text><xsl:value-of select="normalize-space(@depth)"/>
+			</xsl:when>
+		</xsl:choose>
+		<xsl:choose>
+			<xsl:when test="@format = 'PRN'"><xsl:text>,angle=270</xsl:text></xsl:when>
+		</xsl:choose>
+		<xsl:text>]{</xsl:text>
+		<xsl:value-of select="$filename"/>
+		<xsl:choose>
+			<xsl:when test="$is.imageobjectco=1">
+				<xsl:text>}&#10;\calsscale&#10;</xsl:text>
+				<xsl:apply-templates select="ancestor::imageobjectco/areaspec//area"/>
+				<xsl:text>\end{overpic}}</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>}}</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>caption</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="caption">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/msgset.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/msgset.mod.xsl
new file mode 100644
index 00000000000..06a8cd07d12
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/msgset.mod.xsl
@@ -0,0 +1,237 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: msgset.mod.xsl,v 1.2 2004/01/01 14:04:58 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="msgset" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: msgset.mod.xsl,v 1.2 2004/01/01 14:04:58 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.2">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Message Sets <filename>msgset.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msgset</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Applies templates.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="msgset">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msgentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a block object using <xref linkend="template.block.object"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msgentry">
+		<xsl:call-template name="block.object"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>simplemsgentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a block object using <xref linkend="template.block.object"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="simplemsgentry">
+		<xsl:call-template name="block.object"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msg</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a block object using <xref linkend="template.block.object"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msg">
+		<xsl:call-template name="block.object"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msgmain</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a block object using <xref linkend="template.block.object"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msgmain">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msgmain</doc:db>'s <doc:db>title</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates inside a <function condition="latex">textbf</function> command.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msgmain/title|msgsub/title|msgrel/title">
+		<xsl:text>{\textbf{</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>}} </xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msgsub</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msgsub">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msgrel</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msgrel">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msgtext</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msgtext">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msginfo</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a block object using <xref linkend="template.block.object"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msginfo">
+		<xsl:call-template name="block.object"/>
+	</xsl:template>
+
+	<!-- localised -->
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msglevel</doc:db>, <doc:db>msgorig</doc:db> and <doc:db>msgaud</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates as a block, preceded by gentext inside a
+				<function condition="latex">textbf</function> command.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msglevel|msgorig|msgaud">
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>{\textbf{</xsl:text>
+		<xsl:call-template name="gentext.element.name"/>
+		<xsl:text>: </xsl:text>
+		<xsl:text>}} </xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>msgexplan</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a block object using <xref linkend="template.block.object"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="msgexplan">
+		<xsl:call-template name="block.object"/>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/normalize-scape.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/normalize-scape.mod.xsl
new file mode 100644
index 00000000000..c561bd88e3f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/normalize-scape.mod.xsl
@@ -0,0 +1,615 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: normalize-scape.mod.xsl,v 1.33 2004/01/26 09:40:12 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
+|														
+|   PURPOSE:
+|	Escape LaTeX and normalize-space templates.
+|    < > # $ % & ~ _ ^ \ { } |
++ ############################################################################## -->
+
+<xsl:stylesheet 
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="normalize-scape" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: normalize-scape.mod.xsl,v 1.33 2004/01/26 09:40:12 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.30">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Whitespace Normalization and Character Encoding <filename>normalize-scape.mod.xsl</filename></title>
+		<partintro>
+
+			<para>Normalize whitespace and and escape <quote>active</quote> &latex; characters.</para>
+			<para>Includes the auto-generated <filename>scape.mod.xsl</filename> module.</para>
+
+		</partintro>
+	</doc:reference>
+
+	<xsl:include href="scape.mod.xsl"/>
+
+	<doc:template match="text()" xmlns="">
+		<refpurpose>Process <literal>text()</literal> nodes</refpurpose>
+		<doc:description>
+			<para>
+
+				Handles regular text content (i.e. <literal>#PCDATA</literal>)
+				from &docbook; documents.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				For most elements, &latex; active characters
+				will be escaped using the <xref linkend="template.scape"/>
+				template.
+				However, for text within the following elements, the
+				<xref linkend="template.scape-verbatim"/> template
+				will be used to typeset monospace text:
+				<doc:db>literal</doc:db>,
+				<doc:db>filename</doc:db>,
+				<doc:db>userinput</doc:db>,
+				<doc:db>systemitem</doc:db>,
+				<doc:db>prompt</doc:db>,
+				<doc:db>email</doc:db>,
+				<doc:db>sgmltag</doc:db>.
+
+			</para>
+			<para>
+
+				In all cases, interior whitespace will be normalised according
+				to the XSLT specification with the additional feature that
+				leading and trailing whitespace will be elided (as expected
+				with SGML parsers).
+
+			</para>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="gentext"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.inputenc"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="text()" name="text">
+		<xsl:call-template name="trim-outer">
+			<xsl:with-param name="string">
+				<xsl:choose>
+					<xsl:when test="ancestor::literal|ancestor::filename|ancestor::userinput|ancestor::systemitem|ancestor::prompt|ancestor::email|ancestor::sgmltag">
+						<xsl:call-template name="scape-verbatim">
+							<xsl:with-param name="string" select="."/>
+						</xsl:call-template>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:call-template name="scape">
+							<xsl:with-param name="string" select="."/>
+						</xsl:call-template>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:with-param>
+		</xsl:call-template>
+	</xsl:template>
+
+	<!--
+	<xsl:template match="abbrev/text()">
+		<xsl:variable name="string">
+			<xsl:call-template name="text"/>
+		</xsl:variable>
+		<xsl:call-template name="string-replace">
+			<xsl:with-param name="to">.\ </xsl:with-param>
+			<xsl:with-param name="from">. </xsl:with-param>
+			<xsl:with-param name="string" select="$string"/>
+		</xsl:call-template>
+	</xsl:template>
+	-->
+
+	<doc:template match="text()" mode="xref.text" xmlns="">
+		<refpurpose>Process <literal>text()</literal> nodes</refpurpose>
+		<doc:description>
+			<para>
+
+				Handles regular text content (i.e. <literal>#PCDATA</literal>)
+				from &docbook; documents when they are forming the displayed
+				text of an <doc:db>xref</doc:db>.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				&latex; active characters will be escaped using the <xref
+				linkend="template.scape"/> template.
+
+			</para>
+			<para>
+
+				In all cases, interior whitespace will be normalised according
+				to the XSLT specification with the additional feature that
+				leading and trailing whitespace will be elided (as expected
+				with SGML parsers).
+
+			</para>
+		</doc:notes>
+	</doc:template>
+    <xsl:template match="text()" mode="xref.text">
+		<xsl:call-template name="trim-outer">
+			<xsl:with-param name="string">
+				<xsl:call-template name="scape">
+					<xsl:with-param name="string" select="."/>
+				</xsl:call-template>
+			</xsl:with-param>
+		</xsl:call-template>
+    </xsl:template>
+
+	<doc:template match="text()" mode="xref-to" xmlns="">
+		<refpurpose>Process <literal>text()</literal> nodes</refpurpose>
+		<doc:description>
+			<para>
+
+				Handles regular text content (i.e. <literal>#PCDATA</literal>)
+				from &docbook; documents when they are forming the displayed
+				text of an <doc:db>xref</doc:db>.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				&latex; active characters will be escaped using the <xref
+				linkend="template.scape"/> template.
+
+			</para>
+			<para>
+
+				In all cases, interior whitespace will be normalised according
+				to the XSLT specification with the additional feature that
+				leading and trailing whitespace will be elided (as expected
+				with SGML parsers).
+
+			</para>
+		</doc:notes>
+	</doc:template>
+    <xsl:template match="text()" mode="xref-to">
+		<xsl:call-template name="trim-outer">
+			<xsl:with-param name="string">
+				<xsl:call-template name="scape">
+					<xsl:with-param name="string" select="."/>
+				</xsl:call-template>
+			</xsl:with-param>
+		</xsl:call-template>
+    </xsl:template>
+
+	<doc:template match="text()" mode="latex.verbatim" xmlns="">
+		<refpurpose>Process <literal>text()</literal> nodes</refpurpose>
+		<doc:description>
+			<para>
+
+				Handles regular text content (i.e. <literal>#PCDATA</literal>)
+				from &docbook; documents with they occur within certain
+				<quote>verbatim</quote>-mode elements.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			<variablelist>
+				<varlistentry>
+					<term><xref linkend="param.latex.trim.verbatim"/></term>
+					<listitem><simpara>
+						When this variable is enabled, leading and trailing whitespace
+						will be elided. Otherwise, all text is used verbatim.
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				Unlike other <literal>text()</literal> templates, &latex;
+				characters are not escaped by this template. This will result
+				in invalid output in some instances. However, it is currently
+				necessary for <quote>verbatim</quote>-mode support. Whitespace
+				is neither normalised nor elided.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+    <xsl:template match="text()" mode="latex.verbatim">
+		<xsl:choose>
+			<xsl:when test="$latex.trim.verbatim=1">
+				<xsl:call-template name="trim.verbatim"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="."/> 
+			</xsl:otherwise>
+		</xsl:choose>
+    </xsl:template>
+
+	<doc:template match="text()" mode="slash.hyphen" xmlns="">
+		<refpurpose>Process <literal>text()</literal> nodes</refpurpose>
+		<doc:description>
+			<para>
+
+				Handles URL text content from &docbook; documents.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				This template is only used by <xref
+				linkend="template.generate.string.url"/> and only when <xref
+				linkend="param.latex.hyphenation.tttricks"/> is disabled.
+				&latex; active characters will be escaped or hyphenated in a
+				fashion that is tailored for URLs via
+				<xref linkend="template.scape.slash.hyphen"/>.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+    <xsl:template match="text()" mode="slash.hyphen">
+		<xsl:call-template name="trim-outer">
+			<xsl:with-param name="string">
+				<xsl:call-template name="scape.slash.hyphen">
+					<xsl:with-param name="string" select="." />
+				</xsl:call-template>
+			</xsl:with-param>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template name="trim-outer" xmlns="">
+		<refpurpose>Whitespace Normalization and Discretionary Elision</refpurpose>
+		<doc:description>
+			<para>
+
+				This template is used by various <literal>text()</literal>
+				templates to normalise interior whitespace and trim whitespace
+				that occurs at the start or end of a &docbook; element's
+				content.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>string</term>
+					<listitem><simpara>The text to be processed.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+
+				The template is normally called when the context node is within
+				a &docbook; document. The elision of leading or trailing
+				whitespace is dependent on values of the XPath functions
+				<function condition="xpath">position()</function> and <function
+				condition="xpath">last()</function>. This is similar to the
+				handling of whitespace by SGML parsers and allows authors to
+				format their XML documents with <quote>pretty</quote>
+				indentation without causing spurious whitespace in &latex;.
+
+			</para>
+			<para>
+
+				In all cases, interiour whitespace will be normalised with the
+				XPath <function condition="xpath">normalize-space()</function>
+				function. This is necessary to prevent blank-line problems in
+				&latex;.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="trim-outer">
+		<xsl:param name="string"/>
+		<xsl:variable name="trimleft" select="position()=1"/>
+		<xsl:variable name="trimright" select="position()=last()"/>
+		<xsl:choose>
+			<xsl:when test="$trimleft and not($trimright)">
+				<xsl:value-of select="substring-before(normalize-space(concat($string,'$$')),'$$')"/>
+			</xsl:when>
+			<xsl:when test="$trimright and not($trimleft)">
+				<xsl:value-of select="substring-after(normalize-space(concat('$$',$string)),'$$')"/>
+			</xsl:when>
+			<xsl:when test="$trimleft and $trimright">
+				<xsl:value-of select="normalize-space($string)"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="substring-after(substring-before(normalize-space(concat('$$',$string,'$$$')),'$$$'),'$$')"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template name="scape.slash.hyphen" xmlns="">
+		<refpurpose>Process URL text</refpurpose>
+		<doc:description>
+			<para>
+
+				Escapes or hyphenates &latex; active characters is URLs.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>string</term>
+					<listitem><simpara>The URL text to be processed.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+
+				This template is called by <xref
+				linkend="template.text()-slash.hyphen"/>. Text will be escaped
+				and hyphenated by the <xref linkend="template.scape-slash"/>
+				template, except that any portion up to <literal>://</literal>
+				will not be treated specially.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="scape.slash.hyphen">
+	<xsl:param name="string" />
+	<xsl:choose>
+		<xsl:when test="contains($string,'://')">
+			<xsl:call-template name="scape-slash">
+				<xsl:with-param name="string">
+					<xsl:value-of select="substring-before($string,'://')"/>
+					<xsl:value-of select="'://'"/>
+					<xsl:call-template name="scape">
+						<xsl:with-param name="string" select="substring-after($string,'://')"/>
+					</xsl:call-template>
+				</xsl:with-param>
+			</xsl:call-template>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:call-template name="scape-slash">
+				<xsl:with-param name="string">
+					<xsl:call-template name="scape">
+						<xsl:with-param name="string" select="$string"/>
+					</xsl:call-template>
+				</xsl:with-param>
+			</xsl:call-template>
+		</xsl:otherwise>
+	</xsl:choose>
+	</xsl:template>
+
+	<doc:template name="normalize-scape" xmlns="">
+		<refpurpose>Character Escaping and Whitespace Normalization</refpurpose>
+		<doc:description>
+			<para>
+
+				This template is used by various templates to escape &latex;
+				active characters and to normalise whitespace.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>string</term>
+					<listitem><simpara>The text to be processed.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+
+				This template will call the <xref linkend="template.scape"/>
+				template and process its output with the XPath
+				<function condition="xpath">normalize-space</function>
+				function.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="normalize-scape">
+		<xsl:param name="string"/>
+		<xsl:variable name="result">
+			<xsl:call-template name="scape">
+				<xsl:with-param name="string" select="$string"/>
+			</xsl:call-template>
+		</xsl:variable>
+		<xsl:value-of select="normalize-space($result)"/>
+	</xsl:template>
+
+	<doc:template name="string-replace" xmlns="">
+		<refpurpose>Search-and-replace</refpurpose>
+		<doc:description>
+			<para>
+
+				This template performs search-and-replace to modify all
+				instances of a substring.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>string</term>
+					<listitem><simpara>The text to be searched.</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>from</term>
+					<listitem><simpara>The text (substring) to be replaced.</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>to</term>
+					<listitem><simpara>The text that replaces the <literal>from</literal> text.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+
+				This template will search within the <literal>string</literal>
+				text for all occurrences of <literal>from</literal> and replace
+				them with the <literal>to</literal> text.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="string-replace">
+		<xsl:param name="string"/>
+		<xsl:param name="from"/>
+		<xsl:param name="to"/>
+
+		<xsl:choose>
+			<xsl:when test="contains($string, $from)">
+
+			<xsl:variable name="before" select="substring-before($string, $from)"/>
+			<xsl:variable name="after" select="substring-after($string, $from)"/>
+			<xsl:variable name="prefix" select="concat($before, $to)"/>
+
+			<xsl:value-of select="$before"/>
+			<xsl:value-of select="$to"/>
+			<xsl:call-template name="string-replace">
+				<xsl:with-param name="string" select="$after"/>
+				<xsl:with-param name="from" select="$from"/>
+				<xsl:with-param name="to" select="$to"/>
+			</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+			<xsl:value-of select="$string"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+    <!--  
+    (c) David Carlisle
+    replace all occurences of the character(s) `from'
+    by the string `to' in the string `string'.
+    <xsl:template name="string-replace" >
+	<xsl:param name="string"/>
+	<xsl:param name="from"/>
+	<xsl:param name="to"/>
+	<xsl:choose>
+	    <xsl:when test="contains($string,$from)">
+		<xsl:value-of select="substring-before($string,$from)"/>
+		<xsl:value-of select="$to"/>
+		<xsl:call-template name="string-replace">
+		    <xsl:with-param name="string" select="substring-after($string,$from)"/>
+		    <xsl:with-param name="from" select="$from"/>
+		    <xsl:with-param name="to" select="$to"/>
+		</xsl:call-template>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:value-of select="$string"/>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+    -->
+
+	<xsl:template name="trim.verbatim">
+		<xsl:variable name="before" select="preceding-sibling::node()"/>
+		<xsl:variable name="after" select="following-sibling::node()"/>
+
+		<xsl:variable name="conts" select="."/>
+
+		<xsl:variable name="contsl">
+			<xsl:choose>
+				<xsl:when test="count($before) = 0">
+					<xsl:call-template name="remove-lf-left">
+						<xsl:with-param name="astr" select="$conts"/>
+					</xsl:call-template>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="$conts"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+
+		<xsl:variable name="contslr">
+			<xsl:choose>
+				<xsl:when test="count($after) = 0">
+					<xsl:call-template name="remove-ws-right">
+						<xsl:with-param name="astr" select="$contsl"/>
+					</xsl:call-template>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="$contsl"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+
+		<xsl:value-of select="$contslr"/>
+	</xsl:template>
+
+	<xsl:template name="remove-lf-left">
+		<xsl:param name="astr"/>
+		<xsl:choose>
+			<xsl:when test="starts-with($astr,'&#xA;') or
+			                starts-with($astr,'&#xD;') or
+			                starts-with($astr,'&#x20;') or
+			                starts-with($astr,'&#x9;')">
+				<xsl:call-template name="remove-lf-left">
+					<xsl:with-param name="astr" select="substring($astr, 2)"/>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="$astr"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<xsl:template name="remove-ws-right">
+		<xsl:param name="astr"/>
+		<xsl:variable name="last-char">
+			<xsl:value-of select="substring($astr, string-length($astr), 1)"/>
+		</xsl:variable>
+		<xsl:choose>
+			<xsl:when test="($last-char = '&#xA;') or
+			                ($last-char = '&#xD;') or
+			                ($last-char = '&#x20;') or
+			                ($last-char = '&#x9;')">
+				<xsl:call-template name="remove-ws-right">
+					<xsl:with-param name="astr" select="substring($astr, 1, string-length($astr) - 1)"/>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="$astr"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/para.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/para.mod.xsl
new file mode 100644
index 00000000000..13af7da4af7
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/para.mod.xsl
@@ -0,0 +1,221 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: para.mod.xsl,v 1.16 2004/01/13 14:17:45 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
+|														
+|   PURPOSE:
++ ############################################################################## -->
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+
+	<!--############################################################################# -->
+	<!-- DOCUMENTATION                                                                -->
+	<doc:reference id="para" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: para.mod.xsl,v 1.16 2004/01/13 14:17:45 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year> <year>2001</year> <year>2002</year> <year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.8">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Paragraphs <filename>para.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>para.mod.xsl</filename> contains the
+			XSL template for <doc:db>para</doc:db>, <doc:db>simpara</doc:db> and <doc:db>formalpara</doc:db>.</para>
+			<doc:variables>
+				<itemizedlist>
+					<listitem><simpara><xref linkend="param.latex.use.parskip"/></simpara></listitem>
+					<listitem><simpara><xref linkend="param.latex.formalpara.title.style"/></simpara></listitem>
+				</itemizedlist>
+			</doc:variables>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Use normal paragraph spacing instead of parskip spacing</refpurpose>
+		<doc:description>
+			<para>
+				Uses <function condition="latex">docbooktolatexnoparskip</function>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.parskip"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			&essential_preamble;
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="latex.noparskip">
+		<xsl:if test="$latex.use.parskip=1">
+			<xsl:text>\docbooktolatexnoparskip&#10;</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Use parkip spacing, if user desires it</refpurpose>
+		<doc:description>
+			<para>
+				Uses <function condition="latex">docbooktolatexrestoreparskip</function>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.parskip"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			&essential_preamble;
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="latex.restoreparskip">
+		<xsl:if test="$latex.use.parskip=1">
+			<xsl:text>\docbooktolatexrestoreparskip&#10;</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template basename="para" match="para|simpara" xmlns="">
+		<refpurpose>Process <doc:db>para</doc:db> and <doc:db>simpara</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Starts new lines above and below its contents.
+				Thus, consecutive <doc:db basename="para">paras</doc:db> will have
+				one blank line between them.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.parskip"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>In &latex;, there is no distinction between <doc:db>para</doc:db> and <doc:db>simpara</doc:db>.</para>
+			<para>The accuracy of block elements within <sgmltag basename="para">paras</sgmltag> is unknown.</para>
+			<para><doc:todo>The use of <sgmltag>para</sgmltag> within <doc:db basename="footnote">footnotes</doc:db> is unproven.</doc:todo></para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_blocks;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.para-noline"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="para|simpara">
+		<xsl:text>&#10;</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template match="formalpara" xmlns="">
+		<refpurpose>Process <doc:db>formalpara</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Starts new lines above and below its contents.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara>The <doc:db>title</doc:db> is typeset using <xref linkend="param.latex.formalpara.title.style"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>The accuracy of block elements within <doc:db basename="formalpara">formalparas</doc:db> is unknown.</para>
+			<para><doc:todo>The use of <sgmltag>formalpara</sgmltag> within <doc:db basename="footnote">footnotes</doc:db> is unproven.</doc:todo></para>
+			<para>Calls <xref linkend="template.generate.formalpara.title.delimiter"/>.</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_blocks;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="formalpara">
+		<xsl:text>&#10;{</xsl:text>
+		<xsl:value-of select="$latex.formalpara.title.style"/>
+		<xsl:text>{{</xsl:text>
+		<xsl:apply-templates select="title"/>
+		<xsl:text>}</xsl:text>
+		<xsl:call-template name="generate.formalpara.title.delimiter"/>
+		<xsl:text>}}\ </xsl:text>
+		<xsl:apply-templates select="node()[not(self::title)]"/>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Delimite a <doc:db>formalpara</doc:db>'s <doc:db>title</doc:db> from its <doc:db>para</doc:db></refpurpose>
+		<doc:description>
+			<para>
+				Emits a full stop (period).
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				This template can be used to emit any &LaTeX; sequence that you
+				desire. You can make the appearance be conditional upon some
+				attribute or document location, for instance. However, a
+				'space' will <emphasis>always</emphasis> be generated between
+				this delimiter and the subsequent <doc:db>para</doc:db>
+				contents.
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="generate.formalpara.title.delimiter">
+		<xsl:text>.</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="para" xmlns="">
+		<refpurpose>Suppressed paragraphs</refpurpose>
+		<doc:description>
+			<para>
+				These paragraphs are not separated like normal paragraphs.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>This template exists to handle &latex; problems with
+			<function condition="latex">par</function> in certain contexts. <doc:todo>These
+			problems should be periodically reviewed by the &db2latex; team.</doc:todo></para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_blocks;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="textobject/para|step/para|entry/para|question/para" name="para-noline">
+		<xsl:if test="position()&gt;1">
+			<xsl:text> </xsl:text>
+		</xsl:if>
+		<xsl:apply-templates/>
+		<xsl:if test="position()&lt;last()">
+			<xsl:text> </xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/param-common.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/param-common.mod.xsl
new file mode 100644
index 00000000000..dd77a9a4a50
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/param-common.mod.xsl
@@ -0,0 +1,381 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################
+|	$Id: param-common.mod.xsl,v 1.12 2004/01/26 13:25:17 j-devenish Exp $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="param-common" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: param-common.mod.xsl,v 1.12 2004/01/26 13:25:17 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.1">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Parameters: Common Options <filename>param-common.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			This file contains parameters that are shared with other XSL
+			stylesheets such as those as <ulink
+			url="http://docbook.sourceforge.net"/> (see <citetitle>Parameter
+			References</citetitle> in the <ulink
+			url="http://docbook.sourceforge.net/release/xsl/current/doc/reference.html">DocBook
+			XSL Stylesheet Reference Documentation</ulink>). These are
+			parameters are honoured so that you can coordinate your XHTML or FO
+			stylesheets with &DB2LaTeX;.
+			
+			</para>
+			<note>
+				<para>
+				
+				In some stylesheets, tests of parameter values use
+				<quote>!=0</quote> logic. However, &DB2LaTeX; uses
+				<quote>=1</quote> logic. This means that empty parameters are
+				<quote>off</quote> in &DB2LaTeX; but <quote>on</quote> in those
+				other stylesheets. The <ulink
+				url="http://www.w3.org">XPath</ulink> values
+				<quote>true()</quote> and <quote>false()</quote> work as
+				expected.
+				
+				</para>
+			</note>
+		</partintro>
+	</doc:reference>
+
+	<doc:param xmlns="">
+		<refpurpose> &LaTeX; location for admonition graphics </refpurpose>
+		<doc:description>
+			<para>The file path that will be passed to &LaTeX; in order to find admonition graphics.</para>
+			<para>An empty value suppresses the use of admonition graphics.</para>
+			<para>If your figures are in <quote>the current directory</quote> then use a value of
+			<quote>.</quote> (i.e. the full stop or period on its own) to signify this.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="admon.graphics.path">
+		<xsl:choose>
+			<xsl:when test="$latex.admonition.path!=''">
+				<xsl:message>Warning: $latex.admonition.path is deprecated: use $admon.graphics.path instead</xsl:message>
+				<xsl:value-of select="$latex.admonition.path"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>figures</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:param>
+	<xsl:param name="latex.admonition.path"/>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the escaping of <doc:db>alt</doc:db> text </refpurpose>
+		<doc:description>
+			<para>
+
+			Text within <doc:db>alt</doc:db> elements <!--within equation-type
+			elements--> is assumed to be valid &LaTeX; and is passed through
+			unescaped by default (though you should set its value to
+			<quote>plain</quote> or <quote>latex</quote>, which are considered
+			confirmative and equivalent by &DB2LaTeX;). If this is not
+			appropriate for your document, set this variable to the empty
+			value. If you use an explicit <sgmltag
+			class="attribute">role</sgmltag> attribute with the values
+			<quote>latex</quote> or <quote>tex</quote>, you need not concern
+			yourself with this variable. Alt text within equation-type
+			elements is currently assumed to be valid &LaTeX; regardless
+			of this variable (this is probably a bug!).
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="tex.math.in.alt">
+		<xsl:if test="$latex.alt.is.latex!=''">
+			<xsl:message>Warning: $latex.alt.is.latex is deprecated: use $tex.math.in.alt instead</xsl:message>
+			<xsl:if test="$latex.alt.is.latex=1">
+				<xsl:text>latex</xsl:text>
+			</xsl:if>
+		</xsl:if>
+	</xsl:param>
+	<xsl:param name="latex.alt.is.latex"/>
+
+	<doc:param xmlns="">
+		<refpurpose> Display <doc:db>remark</doc:db> and <doc:db>comment</doc:db> elements? </refpurpose>
+		<doc:description>
+			<para>
+			
+			Enables or disables the display of <doc:db basename="comment">comments</doc:db> and <doc:db basename="remark">remarks</doc:db>.
+			By default, this is equal to <xref linkend="param.latex.is.draft"/>.
+			
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="show.comments">
+		<xsl:value-of select="$latex.is.draft"/>
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the display of <doc:db>othername</doc:db> elements in <doc:db basename="author">authors</doc:db> </refpurpose>
+		<doc:description>
+			<para>
+			
+			When disabled, <doc:db>othername</doc:db> elements will be suppressed when
+			<doc:db>author</doc:db> elements are formatted.
+			
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="author.othername.in.middle" select="1"/>
+
+	<doc:param xmlns="">
+		<refpurpose> Separator for bibliography items </refpurpose>
+		<doc:description>
+			<para><doc:todo>This parameter is under review.</doc:todo></para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="biblioentry.item.separator">, </xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Cull table-of-contents entries that are deeply nested </refpurpose>
+		<doc:description>
+			<para>Specifies the maximum depth before sections are omitted from the table of contents.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="toc.section.depth">4</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the automatic numbering of section, parts, and chapters </refpurpose>
+		<doc:description>
+			<para>
+			Specifies the maximum depth before sections cease to be uniquely numbered.
+			This is passed to &LaTeX; using the <literal>secnumdepth</literal> counter.
+			Therefore, it is possible to use a value of <quote>0</quote> (zero) to disable section numbering.
+			A value of <quote>-1</quote> will disable the numbering of parts and chapters, too.
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="section.depth">4</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Default filename extension for <function condition="latex">includegraphics</function> </refpurpose>
+		<doc:description>
+			<para>
+				Specify the &LaTeX; search parameters for graphics filenames.
+				If empty, &DB2LaTeX; will specify some explicit defaults.
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="graphic.default.extension"/>
+
+	<doc:param xmlns="">
+		<refpurpose> Control <sgmltag class="element">mediaobject</sgmltag> selection methods </refpurpose>
+		<doc:description>
+			<para>
+			
+			This controls how &DB2LaTeX; behaves when a <doc:db>figure</doc:db>
+			contains multiple <doc:db
+			basename="mediaobject">mediaobjects</doc:db>. When enabled,
+			&DB2LaTeX; will prefer the <sgmltag>mediaobject</sgmltag> with the
+			<quote>latex</quote>, <quote>tex</quote> or <xref
+			linkend="param.preferred.mediaobject.role"/> role, if any.
+			
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="use.role.for.mediaobject">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control <sgmltag class="element">mediaobject</sgmltag> selection methods </refpurpose>
+		<doc:description>
+			<para>
+			
+			When <xref linkend="param.use.role.for.mediaobject"/> is enabled,
+			this variable can be used to specify the
+			<doc:db>mediaobject</doc:db> <sgmltag
+			class="attribute">role</sgmltag> that your document uses for
+			&LaTeX; output. &DB2LaTeX; will try to use this role before using
+			the <quote>latex</quote> or <quote>tex</quote> roles. For example,
+			some authors may choose to set this to
+			<quote><literal>pdf</literal></quote>.
+			
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="preferred.mediaobject.role"/>
+
+	<doc:param xmlns="">
+		<refpurpose> Specifies where formal component titles should occur </refpurpose>
+		<doc:description>
+			<para>
+
+				Titles for the formal object types (figure, example, quation,
+				table, and procedure) can be placed before or after those
+				objects. The keyword <quote>before</quote> is recognised. All
+				other strings qualify as <quote>after</quote>.
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="formal.title.placement">
+		figure not_before
+		example before
+		equation not_before
+		table before
+		procedure before
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the appearance of page numbers in cross references </refpurpose>
+		<doc:description>
+			<para>
+
+				When enabled, <doc:db basename="xref">xrefs</doc:db> will
+				include page numbers after their generated cross-reference
+				text.
+
+			</para>
+		</doc:description>
+		</doc:param>
+	<xsl:param name="insert.xref.page.number">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the display of URLs after <doc:db basename="ulink">ulinks</doc:db> </refpurpose>
+		<doc:description>
+			<para>
+
+			When this option is enabled, and a ulink has a URL that is different
+			from the displayed content, the URL will be typeset after the content.
+			If the URL and content are identical, only one of them will appear.
+			Otherwise, the URL is hyperlinked and the content is not.
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="ulink.show">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the generation of footnotes for ulinks </refpurpose>
+		<doc:description>
+			<para>
+
+			When this option is enabled, a <doc:db>ulink</doc:db> that has
+			content different to its URL will have an associated footnote. The
+			contents of the footnote will be the URL. If the ulink is within a
+			<doc:db>footnote</doc:db>, the URL is shown after the content.
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="ulink.footnotes">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Honour role as proxy for xrefstyle </refpurpose>
+		<doc:description>
+			<para>
+			
+			The <sgmltag class="attribute">xrefstyle</sgmltag> attribute is not
+			yet part of &DocBook; so the <sgmltag
+			class="attribute">role</sgmltag> attribute can be used until
+			xrefstyle is available for <doc:db>xref</doc:db> elements.
+			
+			</para>
+		</doc:description>
+	</doc:param>
+    <xsl:param name="use.role.as.xrefstyle">0</xsl:param>
+
+	<xsl:variable name="default-classsynopsis-language">java</xsl:variable>
+	<doc:param xmlns="">
+		<refpurpose> Choose whether to include <doc:db>manvolnum</doc:db> in cross-references </refpurpose>
+		<doc:description>
+			<para>
+
+				When this option is enabled, <doc:db
+				basename="manvolnum">manvolnums</doc:db> will be displayed when
+				cross-referencing <doc:db
+				basename="refentry">refentries</doc:db>.
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="refentry.xref.manvolnum" select="1"/>
+	<xsl:variable name="funcsynopsis.style">kr</xsl:variable>
+	<xsl:variable name="funcsynopsis.decoration" select="1"/>
+	<xsl:variable name="function.parens">0</xsl:variable>
+	<doc:param xmlns="">
+		<refpurpose> Control the use of NAME headers </refpurpose>
+		<doc:description>
+			<para>
+
+				See <ulink url="http://docbook.sourceforge.net/release/xsl/current/doc/fo/refentry.generate.name.html"/>.
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="refentry.generate.name" select="1"/>
+	<xsl:param name="glossentry.show.acronym" select="'no'"/>
+
+	<xsl:variable name="section.autolabel" select="1"/>
+	<xsl:variable name="section.label.includes.component.label" select="0"/>
+	<xsl:variable name="chapter.autolabel" select="1"/>
+	<xsl:variable name="preface.autolabel" select="0"/>
+	<xsl:variable name="part.autolabel" select="1"/>
+	<xsl:variable name="qandadiv.autolabel" select="1"/>
+	<xsl:variable name="autotoc.label.separator" select="'. '"/>
+	<xsl:variable name="qanda.inherit.numeration" select="1"/>
+	<xsl:variable name="qanda.defaultlabel">number</xsl:variable>
+
+	<xsl:param name="punct.honorific" select="'.'"/>
+	<xsl:param name="stylesheet.result.type" select="'xhtml'"/>
+	<xsl:param name="use.svg" select="0"/>
+	<xsl:param name="formal.procedures" select="1"/>
+	<xsl:param name="xref.with.number.and.title" select="1"/>
+	<xsl:param name="xref.label-title.separator">: </xsl:param>
+	<xsl:param name="xref.label-page.separator"><xsl:text> </xsl:text></xsl:param>
+	<xsl:param name="xref.title-page.separator"><xsl:text> </xsl:text></xsl:param>
+	<xsl:template name="is.graphic.extension">
+		<xsl:message terminate="yes">Logic error: is.graphic.extension is unsupported.</xsl:message>
+	</xsl:template>
+	<xsl:template name="is.graphic.format">
+		<xsl:message terminate="yes">Logic error: is.graphic.format is unsupported.</xsl:message>
+	</xsl:template>
+	<xsl:template name="lookup.key">
+		<xsl:message terminate="yes">Logic error: lookup.key is unsupported.</xsl:message>
+	</xsl:template>
+    <xsl:variable name="check.idref">1</xsl:variable>
+
+	<doc:param xmlns="">
+		<refpurpose> Process only one element tree within a document </refpurpose>
+		<doc:description>
+			<para>
+
+				When this variable is non-empty, it is interpreted as the ID of
+				an element that should be typeset by &DB2LaTeX;. The element's
+				children, but none of its siblings or ancestors, will be
+				processed as per normal. When the root element is a
+				<doc:db>book</doc:db> or <doc:db>article</doc:db>, that
+				component will have its normal infrastructure (including
+				<doc:db>bookinfo</doc:db> or <doc:db>articleinfo</doc:db>)
+				processed before the <quote>rootid</quote> element.
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="rootid" select="''"/>
+
+    <!--
+    <xsl:variable name="link.mailto.url"></xsl:variable>
+    <xsl:variable name="toc.list.type">dl</xsl:variable>
+    -->
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/param-direct.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/param-direct.mod.xsl
new file mode 100644
index 00000000000..e31b3dfb343
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/param-direct.mod.xsl
@@ -0,0 +1,589 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################
+|	$Id: param-direct.mod.xsl,v 1.7 2004/01/31 11:05:05 j-devenish Exp $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="param-direct" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: param-direct.mod.xsl,v 1.7 2004/01/31 11:05:05 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.1">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Parameters: &LaTeX;-direct Strings <filename>param-direct.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			The values of the parameters in this file will be passed
+			directly to &LaTeX;.
+			All parameter names begin with <quote>latex.</quote>.
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:param xmlns="">
+		<refpurpose> DB2LaTeX document class </refpurpose>
+		<doc:description>
+			<para>
+			This variable is normally empty and the stylesheets will determine
+			the correct document class according to whether the document is a
+			book or an article. If you wish to use your own document class,
+			put its non-empty value in this variable. It will apply for both
+			books and articles.
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.documentclass"></xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> The <literal>\maketitle</literal> for books and articles. </refpurpose>
+		<doc:description>
+			<para>Some users may wish to override or eliminate <literal>\maketitle</literal>.</para>
+			<note><para>Does not apply to <sgmltag class="element">article</sgmltag>s within <sgmltag class="element">book</sgmltag>s.</para></note>
+			<para>By default, uses LaTeX <literal>\maketitle</literal> with the 'empty' pagestyle
+			for the first page. The page style of subsequent pages is determined by
+			<xref linkend="template.generate.latex.pagestyle"/>.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.maketitle">
+		<xsl:text>{\maketitle</xsl:text>
+		<xsl:call-template name="generate.latex.pagestyle"/>
+		<xsl:text>\thispagestyle{empty}}&#10;</xsl:text>
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Undocumented </refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.article.preamble.pre">
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Undocumented </refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.article.preamble.post">
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Controls what is output after the LaTeX preamble. </refpurpose>
+		<doc:description>
+			<para>Default values decrease edge margins and allow a large quantity of figures to be set on each page. </para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.article.varsets">
+		<xsl:text><![CDATA[
+\usepackage{anysize}
+\marginsize{2cm}{2cm}{2cm}{2cm}
+\renewcommand\floatpagefraction{.9}
+\renewcommand\topfraction{.9}
+\renewcommand\bottomfraction{.9}
+\renewcommand\textfraction{.1}
+]]>
+		</xsl:text>
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Undocumented </refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.book.preamble.pre">
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Undocumented </refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.book.preamble.post">
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>
+			All purpose commands to change text width, height, counters, etc.
+			Defaults to a two-sided margin layout.
+		</refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.book.varsets">
+		<xsl:text>\usepackage{anysize}&#10;</xsl:text>
+		<xsl:text>\marginsize{3cm}{2cm}{1.25cm}{1.25cm}&#10;</xsl:text>
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> 
+			Begin document command
+		</refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.book.begindocument">
+		<xsl:text>\begin{document}&#10;</xsl:text>
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>
+			LaTeX code that is output after the author (e.g. 
+			<literal>\makeindex, \makeglossary</literal>
+		</refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.book.afterauthor">
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>\makeindex&#10;</xsl:text>
+		<xsl:text>\makeglossary&#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+	</xsl:param>
+
+	<doc:template xmlns="">
+		<refpurpose> Format the output of tabular headings. </refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:template>
+	<xsl:template name="latex.thead.row.entry">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Format the output of tabular footers. </refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:template>
+	<xsl:template name="latex.tfoot.row.entry">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of article titles </refpurpose>
+		<doc:description>
+			<para>This is passed directly to &LaTeX;. Typically,
+			it is either a \command or an empty string.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.article.title.style">\textbf</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of article titles within books </refpurpose>
+		<doc:description>
+			<para>This is passed directly to &LaTeX;. Typically,
+			it is either a \command or an empty string.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.book.article.title.style">\Large\textbf</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of authors and dates within a book's articles </refpurpose>
+		<doc:description>
+			<para>This is passed directly to &LaTeX;. Typically,
+			it is either a \command or an empty string.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.book.article.header.style">\textsf</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of equation captions  </refpurpose>
+		<doc:description>
+			<para>Figure captions are typeset in the default typeface (usually 'roman') but if
+			this option is set to a LaTeX command, such as <literal>\textit</literal>, then
+			that command will precede the caption and it will be typeset accordingly.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.equation.caption.style"></xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of example captions  </refpurpose>
+		<doc:description>
+			<para>Figure captions are typeset in the default typeface (usually 'roman') but if
+			this option is set to a LaTeX command, such as <literal>\textit</literal>, then
+			that command will precede the caption and it will be typeset accordingly.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.example.caption.style"></xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of figure captions  </refpurpose>
+		<doc:description>
+			<para>Figure captions are typeset in the default typeface (usually 'roman') but if
+			this option is set to a LaTeX command, such as <literal>\textit</literal>, then
+			that command will precede the caption and it will be typeset accordingly.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.figure.caption.style"></xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of figure titles  </refpurpose>
+		<doc:description>
+			<para>Figure titles are typeset in the default typeface (usually 'roman') but if
+			this option is set to a LaTeX command, such as <literal>\textit</literal>, then
+			that command will precede the title and it will be typeset accordingly.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.figure.title.style"></xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of equation captions  </refpurpose>
+		<doc:description>
+			<para>The titles of <doc:db basename="formalpara">formalparas</doc:db> are typeset in the bold typeface by default.
+			This parameter can be set to an alternative &latex; command, such as <function condition="latex">textit</function> (or empty).</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.formalpara.title.style">\textbf</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of list titles  </refpurpose>
+		<doc:description>
+			<para>List titles are typeset in small caps but if
+			this option is set to a LaTeX command, such as <literal>\textit</literal>, then
+			that command will precede the title and it will be typeset accordingly.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.list.title.style">\sc</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of procedure titles  </refpurpose>
+		<doc:description>
+			<para>Procedure titles are typeset in small caps but if
+			this option is set to a LaTeX command, such as <literal>\textit</literal>, then
+			that command will precede the title and it will be typeset accordingly.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.procedure.title.style">\sc</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of segtitles  </refpurpose>
+		<doc:description>
+			<para>This is passed directly to &LaTeX;. Typically,
+			it is either a \command or an empty string.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.segtitle.style">\em</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of step titles  </refpurpose>
+		<doc:description>
+			<para>Step titles are typeset in small caps but if
+			this option is set to a LaTeX command, such as <literal>\textit</literal>, then
+			that command will precede the title and it will be typeset accordingly.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.step.title.style">\bf</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the style of table captions  </refpurpose>
+		<doc:description>
+			<para>Figure captions are typeset in the default typeface (usually 'roman') but if
+			this option is set to a LaTeX command, such as <literal>\textit</literal>, then
+			that command will precede the caption and it will be typeset accordingly.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.table.caption.style"></xsl:param>
+
+	<xsl:param name="latex.fancyhdr.lh">Left Header</xsl:param>
+	<xsl:param name="latex.fancyhdr.ch">Center Header</xsl:param>
+	<xsl:param name="latex.fancyhdr.rh">Right Header</xsl:param>
+	<xsl:param name="latex.fancyhdr.lf">Left Footer</xsl:param>
+	<xsl:param name="latex.fancyhdr.cf">Center Footer</xsl:param>
+	<xsl:param name="latex.fancyhdr.rf">Right Footer</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Override DB2LaTeX's choice of LaTeX page numbering style </refpurpose>
+		<doc:description>
+			<para>By default, DB2LaTeX will choose the 'plain' or 'fancy' page styles,
+			depending on <xref linkend="param.latex.use.fancyhdr"/>. If non-empty, this
+			variable overrides the automatic selection. An example would be the literal
+			string 'empty', to eliminate headers and page numbers.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.pagestyle"/>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX hyperref options</refpurpose>
+	<doc:description>
+		<para>
+		In addition to this variable, you can specify additional options using
+		<literal>latex.hyperref.param.pdftex</literal> or <literal>latex.hyperref.param.dvips</literal>.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.hyperref.param.common">bookmarksnumbered,colorlinks,backref,bookmarks,breaklinks,linktocpage,plainpages=false</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX hyperref options for pdfTeX output</refpurpose>
+	<doc:description>
+		<para>
+		See the hyperref documentation for further information.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.hyperref.param.pdftex">pdfstartview=FitH</xsl:param>
+	<!--
+	what is the unicode option?
+	-->
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX hyperref options for dvips output</refpurpose>
+	<doc:description>
+		<para>
+		See the hyperref documentation for further information.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.hyperref.param.dvips"></xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Options for the <productname>varioref</productname> LaTeX package</refpurpose>
+		<doc:description><para>Support index generation.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.varioref.options">
+		<xsl:if test="$latex.language.option!='none'">
+			<xsl:value-of select="$latex.language.option" />
+		</xsl:if>
+	</xsl:param>
+
+	<doc:template name="latex.vpageref.options" xmlns="">
+		<refpurpose>Toggle the use of the <productname>varioref</productname> LaTeX package</refpurpose>
+		<doc:description><para>Support index generation.</para></doc:description>
+	</doc:template>
+	<xsl:template name="latex.vpageref.options">on this page</xsl:template>
+
+	<doc:param xmlns="">
+		<refpurpose>Choose indentation for tabs in verbatim environments</refpurpose>
+		<doc:description><para>When <xref linkend="param.latex.use.fancyvrb"/> is enabled,
+		this variable sets the width of a tab in terms of an equivalent number of spaces.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.fancyvrb.tabsize">3</xsl:param>
+
+	<doc:template name="latex.fancyvrb.options" xmlns="">
+		<refpurpose>Insert <productname>LaTeX</productname> options for <productname>fancyvrb</productname> Verbatim environments</refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:template>
+	<xsl:template name="latex.fancyvrb.options"/>
+
+	<doc:param xmlns="">
+		<refpurpose>Control the use of the <productname>inputenc</productname> LaTeX package</refpurpose>
+		<doc:description>
+			<para>
+			If this option is non-empty, the <productname>inputenc</productname> package
+			will be used with the specified encoding. This should agree with the your driver
+			file. For example, the default value of <literal>latin1</literal>
+			is compatible with <filename>docbook.xsl</filename>, which contains
+			<literal><![CDATA[<xsl:output method="text" encoding="ISO-8859-1" indent="yes"/>]]></literal>
+			</para>
+			<para>
+			If this option is empty, the <productname>inputenc</productname> package
+			will not be invoked by <productname>DB2LaTeX</productname>.
+			</para>
+			<segmentedlist>
+				<title>Common Combinations</title>
+				<segtitle>Output Encoding</segtitle><segtitle><productname>inputenc</productname> Option</segtitle>
+				<seglistitem><seg>ISO-8859-1</seg><seg>latin1</seg></seglistitem>
+				<seglistitem><seg>UTF-8</seg><seg>utf8<footnote><simpara>When used in conjunction with a package such as <ulink url="http://www.ctan.org/tools/cataloguesearch?action=/search/&amp;catstring=unicode"><productname>unicode</productname></ulink>.</simpara></footnote></seg></seglistitem>
+			</segmentedlist>
+			<para>
+			<productname>inputenc</productname> is a <productname>LaTeX</productname> base package.
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.inputenc">latin1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Options for the <productname>fontenc</productname> package </refpurpose>
+		<doc:description>
+			<para> Undocumented. </para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.fontenc"></xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Select the optional parameter(s) for the <productname>unicode</productname> LaTeX package</refpurpose>
+		<doc:description><para>See the <productname>unicode</productname> documentation for details.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.ucs.options"></xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Select the optional parameter for the <productname>babel</productname> LaTeX package</refpurpose>
+		<doc:description>
+			<para>See the <productname>babel</productname> documentation for details.</para>
+			<para>Although DB2LaTeX will try to choose the correct babel options for your
+			document, you may need to specify the correct choice here. The special value
+			of 'none' (without the quotes) will cause DB2LaTeX to skip babel configuration.</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.babel.language"></xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Adjust bibliography formatting </refpurpose>
+	<doc:description>
+		<para>The environment bibliography accepts a parameter that indicates
+		the widest label, which is used to correctly format the bibliography
+		output. The value of this parameter is output inside the
+		<literal>\begin{thebibliography[]}</literal> LaTeX command.</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.bibwidelabel">
+		<xsl:choose>
+			<xsl:when test="$latex.biblioentry.style='ieee' or $latex.biblioentry.style='IEEE'">
+				<xsl:text>123</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>WIDELABEL</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX document class options  </refpurpose>
+	<doc:description>
+		<para>
+		These are the first options to be passed to <literal>\documentclass</literal>
+		(The common options are
+		<!--
+		set to <literal>french,english</literal>
+		-->
+		blank
+		by default.)
+		They will be augmented or superseded by article/book options (see $latex.documentclass.article and $latex.documentclass.book) and pdftex/dvips options (see $latex.documentclass.pdftex and $latex.documentclass.dvips).
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.documentclass.common"></xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX document class options for articles</refpurpose>
+	<doc:description>
+		<para>
+		The article options are set to <literal>a4paper,10pt,twoside,twocolumn</literal> by default.
+		These are the intermediate options to be passed to <literal>\documentclass</literal>,
+		between the common options and the pdftex/dvips options.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.documentclass.article">a4paper,10pt,twoside,twocolumn</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX document class options for books</refpurpose>
+	<doc:description>
+		<para>
+		The book options are set to <literal>a4paper,10pt,twoside,openright</literal> by default.
+		These are the intermediate options to be passed to <literal>\documentclass</literal>,
+		between the common options and the pdftex/dvips options.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.documentclass.book">a4paper,10pt,twoside,openright</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX document class options for pdfTeX output</refpurpose>
+	<doc:description>
+		<para>
+		The pdfTeX options are empty by default.
+		These are the last options to be passed to <literal>\documentclass</literal>
+		and override the common/article/book options.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.documentclass.pdftex"></xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX document class options for dvips output</refpurpose>
+	<doc:description>
+		<para>
+		The dvips options are empty by default.
+		These are the last options to be passed to <literal>\documentclass</literal>
+		and override the common/article/book options.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.documentclass.dvips"></xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX graphics admonitions size</refpurpose>
+	<doc:description>
+		<para>
+			Is passed as an optional parameter for <literal>\includegraphics</literal> and
+			can take on any such legal values (or be empty).
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.admonition.imagesize">width=1cm</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX allows using an (externally generated) cover page  </refpurpose>
+	<doc:description>
+		<para>
+		You may supply a LaTeX file that will supersede DB2LaTeX's default
+		cover page or title. If the value of this variable is non-empty, the
+		generated LaTeX code includes \input{filename}. Otherwise, it uses the
+		\maketitle command.
+		</para>
+		<warning><para>
+			Bear in mind that using an external cover page breaks the
+			"encapsulation" of DocBook. Further revisions of these stylesheets
+			will add chunking support, and the automation of the cover file
+			generation.
+		</para></warning>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.titlepage.file">title</xsl:param>
+    <doc:param xmlns="">
+	<refpurpose> Document Font(s)  </refpurpose>
+	<doc:description>
+			<para>
+				Document fonts can be chosen by providing &LaTeX; package names.
+				Common values include <literal>default</literal>, <literal>times</literal>, <literal>palatcm</literal>, <literal>charter</literal>, <literal>helvet</literal>, <literal>palatino</literal>, <literal>avant</literal>, <literal>newcent</literal> and <literal>bookman</literal>.
+				Particular combinations may also work. For example, <literal>mathptm,charter,courier</literal>.
+			</para>
+			<!--
+			If you want to change explicitly to a certain font, use the command \fontfamily{XYZ}\selectfont whereby XYZ can be set to: pag for Adobe AvantGarde, pbk for Adobe Bookman, pcr for Adobe Courier, phv for Adobe Helvetica, pnc for Adobe NewCenturySchoolbook, ppl for Adobe Palatino, ptm for Adobe Times Roman, pzc for Adobe ZapfChancery
+			-->
+	</doc:description>
+    </doc:param>
+    <xsl:param name="latex.document.font">palatino</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Override DB2LaTeX's preamble with a custom preamble. </refpurpose>
+	<doc:description>
+		<para>
+		When this variable is set, the entire DB2LaTeX premable will be superseded.
+		<emphasis>You should not normally need or want to use this.</emphasis>
+		It may cause LaTeX typesetting problems. This is a last resort or
+		<quote>expert</quote> feature.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.override"></xsl:param>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/param-switch.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/param-switch.mod.xsl
new file mode 100644
index 00000000000..e0956967e3d
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/param-switch.mod.xsl
@@ -0,0 +1,698 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################
+|	$Id: param-switch.mod.xsl,v 1.17 2004/01/31 11:52:31 j-devenish Exp $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="param-switch" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: param-switch.mod.xsl,v 1.17 2004/01/31 11:52:31 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.1">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Parameters: &DB2LaTeX; Switches <filename>param-switch.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			The values of parameters in this file are used to influence
+			the behaviour of &DB2LaTeX; templates through the selection
+			of pre-defined options.
+			All parameter names begin with <quote>latex.</quote>.
+			
+			</para>
+			<note>
+				<para>
+				
+				In some stylesheets, tests of parameter values use
+				<quote>!=0</quote> logic. However, &DB2LaTeX; uses
+				<quote>=1</quote> logic. This means that empty parameters are
+				<quote>off</quote> in &DB2LaTeX; but <quote>on</quote> in those
+				other stylesheets. The <ulink
+				url="http://www.w3.org">XPath</ulink> values
+				<quote>true()</quote> and <quote>false()</quote> work as
+				expected.
+				
+				</para>
+			</note>
+		</partintro>
+	</doc:reference>
+
+	<doc:param xmlns="">
+	<refpurpose> Control the display of <doc:db basename="caption">captions</doc:db> in lists of figures.  </refpurpose>
+	<doc:description>
+		<para>
+		By default, lists of figures (see <xref linkend="template.lot"/>)
+		will include both figure <doc:db basename="title">titles</doc:db> and mediaobject <doc:db basename="caption">captions</doc:db>.
+		This is useful for readers, as they have a full description of each figure.
+		However, it is impractical for large documents because the list
+		of figures will occupy too many pages.
+		</para>
+		<para>
+		This variable, when set to '1', authorises DB2LaTeX to include
+		mediaobject captions in lists of figures. It is enabled by default.
+		When set to '0', lists of figures will contain only the
+		titles of figures.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.caption.lot.titles.only">1</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose>
+		Control the output of the \bibliography{.bib}.
+	</refpurpose>
+	<doc:description>
+		<para>The value of this parameter is output.</para>
+		<para>An example is <quote><filename>citations.bib</filename></quote>,
+		if your BibTeX file has that name.</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.bibfiles"></xsl:param>
+
+    <doc:param xmlns="">
+	<refpurpose> Controls the output of LaTeX packages and commands to support 
+	    documents with math commands and environments..</refpurpose>
+	<doc:description>
+	    <para>If this parameter is set to 1, the stylesheets generate code to 
+		<emphasis>DEFAULT: 1</emphasis> Only more code is generated. 
+	    </para>
+	</doc:description>
+    </doc:param>
+	<xsl:param name="latex.math.support">1</xsl:param>
+
+    <doc:param xmlns="">
+	<refpurpose> Controls  if the revision history table is generated as the first document 
+	    table.
+	</refpurpose>
+	<doc:description>
+	    <para>If this parameter is set to 1, the stylesheets generate code to 
+		<emphasis>DEFAULT: 1</emphasis> Only more code is generated. 
+	    </para>
+	</doc:description>
+    </doc:param>
+	<xsl:param name="latex.output.revhistory">1</xsl:param>
+
+    <doc:template name="latex.fancybox.options" xmlns="">
+	<refpurpose> Options for fancybox </refpurpose>
+	<doc:description>
+			<!--
+			<xsl:if test="@role">
+				<xsl:choose>
+					<xsl:when test="@role='small'">
+						<xsl:text>,fontsize=\small</xsl:text>
+					</xsl:when>
+					<xsl:when test="@role='large'">
+						<xsl:text>,fontsize=\large</xsl:text>
+					</xsl:when>
+				</xsl:choose>
+			</xsl:if>
+			-->
+			<para>
+				<doc:todo>Undocumented.</doc:todo>
+			</para>
+	</doc:description>
+    </doc:template>
+    <xsl:template name="latex.fancybox.options">
+	</xsl:template>
+
+    <doc:param xmlns="">
+	<refpurpose> Controls the output of LaTeX commands to support the generation 
+	    of PDF files.</refpurpose>
+	<doc:description>
+	    <para>If this parameter is set to 1, the stylesheets generate code to 
+		detect if it is either <literal>latex</literal> or <literal>pdflatex</literal>
+		the shell command that is being used to compile the LaTeX text file. Some
+		packages (<literal>graphicx</literal>, <literal>hyperref</literal>) are used
+		with the right parameters. Finally, the graphic extensions declared, to use in
+		<literal>\includegraphics</literal> commands depends also on which command is
+		being used. If this parameter is set to zero, such code is not generated (which 
+		does not mean that the file cannot compile with pdflatex, but some strange issues 
+		may appear). <emphasis>DEFAULT: 1</emphasis> Only more code is generated. 
+	    </para>
+	</doc:description>
+    </doc:param>
+	<xsl:param name="latex.pdf.support">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Enable the generation of indexterms </refpurpose>
+		<doc:description><para>Support index generation.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.generate.indexterm">1</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> DB2LaTeX hyphenation linebreak tricks </refpurpose>
+	<doc:description>
+		<para>
+		Usually, LaTeX does not perform hyphenation in <quote>teletype</quote> (monospace)
+		text. This can lead to formatting problems. But certain monospace texts, such as
+		URLs and filenames, have <quote>natural</quote> breakpoints such as full stops
+		and slashes. DB2LaTeX's <quote>tttricks</quote> exploit a hyphenation trick in
+		order to provide line wrapping in the middle of monospace text. Set this to '1'
+		to enable these tricks (they are not enabled by default). See also the FAQ.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.hyphenation.tttricks">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Decimal point for &LaTeX; tables </refpurpose>
+		<doc:description>
+			<para>
+			
+			This is a non-localisable character that may be used
+			for decimal alignment of &LaTeX; tables.
+			
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.decimal.point"/>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the trimming of leading and trailing whitespace in verbatim environments </refpurpose>
+		<doc:description><para>
+			In verbatim environments such as <doc:db>programlisting</doc:db> and <doc:db>screen</doc:db>,
+			it can be useful to trim leading and trailing whitespace. However, this is not compliant
+			with The Definitive Guide.
+		</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.trim.verbatim">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>ltxtable</productname> LaTeX package</refpurpose>
+		<doc:description>
+		<note><para>
+		This is not implemented as true ltxtable support, yet.
+		It uses longtable until we can integrate proper ltxtable support.
+		One the feature is supported, it should probably be enabled by
+		default!
+		</para></note>
+		<para>If this package is used then tables will be have the capability
+		to run over multiple pages when necessary.</para>
+		<warning><para>
+		Cells spanning multiple columns may require extra passes with LaTeX
+		in order for column widths to 'converge'.
+		</para></warning>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.ltxtable">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>longtable</productname> LaTeX package</refpurpose>
+		<doc:description>
+			<para>
+				Enabling this option allows <doc:db
+				basename="simplelist">simplelists</doc:db> to run over multiple
+				pages. In the future, it will be superseded by <xref
+				linkend="param.latex.use.ltxtable"/>.
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.longtable">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>overpic</productname> LaTeX package</refpurpose>
+		<doc:description><para>Facilitates overlays (for callouts).</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.overpic">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>umoline</productname> LaTeX package</refpurpose>
+		<doc:description><para>Provide underlining.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.umoline">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>url</productname> LaTeX package</refpurpose>
+		<doc:description><para>Provide partial support for hyperlinks.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.url">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the the <quote>draft</quote> preamble</refpurpose>
+		<doc:description><para>&DB2LaTeX; provides a number of draft-mode features to aid
+		the refinement of documents. Normally, this mode is enabled or disabled according
+		to the <sgmltag class='attribute'>status</sgmltag> attribute of the top-level
+		<doc:db>book</doc:db> or <doc:db>article</doc:db> element. However, this variable
+		will take precedence when it is not empty. It is empty by default.</para>
+		</doc:description>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_index_draft;
+				&test_draft;
+			</simplelist>
+		</doc:samples>
+	</doc:param>
+	<xsl:param name="latex.is.draft"/>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>varioref</productname> LaTeX package</refpurpose>
+		<doc:description><para><productname>varioref</productname> seemed like a good idea at first,
+		but we not realise it does understand &DocBook; gentext localisations. By default, it is enabled
+		when <xref linkend="param.insert.xref.page.number"/> is enabled.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.varioref">
+		<xsl:if test="$insert.xref.page.number='1'">1</xsl:if>
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>fancyhdr</productname> LaTeX package</refpurpose>
+		<doc:description><para>Provides page headers and footers. Disabling support for
+		this package will make headers and footer go away.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.fancyhdr">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the inclusion of chapter titles in <doc:db basename="lot">lots</doc:db> </refpurpose>
+		<doc:description>
+			<para>
+				When this variable is set, lists of tables and lists of figures
+				will be grouped and labeled by chapter.
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.bridgehead.in.lot">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Configure the application of truncation partitions </refpurpose>
+		<doc:description>
+			<para>
+
+				For <xref linkend="param.latex.fancyhdr.truncation.partition"/>, the
+				partition can be modulated in a left-right fashion or an
+				inside-outside fashion. Use <quote>lr</quote> for left-right,
+				all other values are inside-outside (<quote>io</quote> is
+				suggested). The default is <quote>io</quote>, because this
+				matches <xref linkend="param.latex.documentclass.book"/>.
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.fancyhdr.truncation.style">io</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Configure the width of header portions on each page </refpurpose>
+		<doc:description>
+			<para>
+
+				It is possible that the titles of chapter or sections will
+				occupy more than the width of a single line. When this variable
+				is empty, headers will be allowed to occupy multiple lines.
+				However, it is possible that the left-hand portion of a header
+				will collide with the right-hand portion of header. To prevent
+				this, headers can be truncated if they exceed an allowable
+				width. When this variables is set to a number from zero to 100,
+				the left-hand (or inside) side of each header will have that
+				width reserved. The right-hand (or outside) side will have the
+				remainder. A common option is to set this variable to zero and
+				set <xref linkend="param.latex.fancyhdr.truncation.style"/> to
+				<quote>io</quote>.
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.fancyhdr.truncation.partition">50</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Section/chapter style for fancy headers </refpurpose>
+		<doc:description>
+			<para>
+
+				&DB2LaTeX; comes with some pre-configured styles for page
+				headers. These include <quote></quote>, the default, which is
+				determined by the <productname>fancyhdr</productname> package.
+				Another option is <quote>natural</quote>, in which both the
+				chapter and section are shown on each page with their numbers.
+				An alternative is to provide your own <xref
+				linkend="template.generate.latex.pagestyle"/> template with a
+				value such as <literal>\pagestyle{headings}</literal> (the
+				<quote>headings</quote> page style, which is not a
+				<productname>fancyhdr</productname> style, shows page numbers
+				in the headers whereas the others show page numbers in the
+				footers).
+
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.fancyhdr.style"/>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>parskip</productname> &latex; package</refpurpose>
+		<doc:description>
+			<para>Use <quote>block</quote> paragraph style instead of indentation.</para>
+		</doc:description>
+		<doc:notes>
+			<para><productname>parskip</productname> introduces vertical whitespace between
+			paragraphs and list items. However, &db2latex;'s <doc:db>toc</doc:db> and
+			<doc:db>lot</doc:db> templates attempt to suppress this whitespace.</para>
+			<para>When this option is off, you may wish to investigate <xref linkend="param.latex.use.noindent"/>.</para>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.para"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:param>
+	<xsl:param name="latex.use.parskip">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of <function condition="latex">noindent</function> commands</refpurpose>
+		<doc:description>
+			<para>
+			
+			When this parameter is 1, &DB2LaTeX; will deliberately insert
+			noindents at particular locations within your document.
+
+			</para>
+		</doc:description>
+		<doc:notes>
+			<para>
+
+			When traditional &LaTeX; paragraph indentation and spacing is used,
+			it is often necessary to use <function
+			condition="latex">noindent</function> after certain block-formatted
+			elements (e.g. <doc:db>itemizedlist</doc:db>). Let us know if we
+			need to insert more <function
+			condition="latex">noindent</function>---so far, there are few
+			places where we make use of it.
+
+			</para>
+			<para>
+				
+			By default, this option will be turned on when <xref
+			linkend="param.latex.use.parskip"/> is <emphasis>off</emphasis> and
+			will be turned off when <xref linkend="param.latex.use.parskip"/>
+			is <emphasis>on</emphasis>.
+				
+			</para>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.parskip"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:param>
+	<xsl:param name="latex.use.noindent">
+		<xsl:choose>
+			<xsl:when test="$latex.use.parskip=1">
+				<xsl:value-of select="0"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="1"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>subfigure</productname> LaTeX package</refpurpose>
+		<doc:description><para>Used to provide nice layout of multiple mediaobjects in figures.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.subfigure">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>rotating</productname> LaTeX package</refpurpose>
+		<doc:description><para>Undocumented.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.rotating">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>tabularx</productname> LaTeX package</refpurpose>
+		<doc:description><para>Used to provide certain table features. Has some incompatabilities
+		with packages, but also solves some conflicts that the regular tabular
+		environment has.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.tabularx">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>dcolumn</productname> LaTeX package</refpurpose>
+		<doc:description>
+		<warning><para>
+			Currently, <productname>dcolumn</productname> support does not function
+			correctly.
+		</para></warning>
+		<para>
+			<productname>dcolumn</productname> provides support for the <literal>char</literal>
+			alignment of table cells.
+		</para>
+		</doc:description>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.decimal.point"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:param>
+	<xsl:param name="latex.use.dcolumn">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>hyperref</productname> LaTeX package</refpurpose>
+		<doc:description><para>This is used extensively for hyperlinking within documents.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.hyperref">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>fancybox</productname> LaTeX package</refpurpose>
+		<doc:description><para>This is essential for admonitions.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.fancybox">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>fancyvrb</productname> LaTeX package</refpurpose>
+		<doc:description><para>Provides support for tabbed whitespace in verbatim environments.
+		See also <xref linkend="param.latex.fancyvrb.tabsize"/>.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.fancyvrb">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose>Toggle the use of the <productname>isolatin1</productname> LaTeX package</refpurpose>
+		<doc:description>
+			<warning><para>
+			This option is deprecated. See <xref linkend="param.latex.inputenc"/>.
+			</para></warning>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.isolatin1">0</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Choose whether to use the <productname>unicode</productname> LaTeX package</refpurpose>
+		<doc:description><para>See the <productname>unicode</productname> documentation for details.</para></doc:description>
+	</doc:param>
+	<xsl:param name="latex.use.ucs">0</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Control which references are cited in the bibliography </refpurpose>
+	<doc:description>
+		<para>
+		The DB2LaTeX generated bibliography (bibitems) may either
+		include all biblioentries found in the document, or only thee ones explicitly
+		cited with <sgmltag class="element">citation</sgmltag>.
+		</para>
+	    <para>Two values are possible: <quote>all</quote> or <quote>cited</quote>.</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.biblio.output">all</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Control bibliographic citation style </refpurpose>
+	<doc:description>
+		<para>By default, this value is empty. Alternatively, a special value
+		is recognised: <quote>ieee</quote> (or <quote>IEEE</quote>).</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.biblioentry.style"/>
+
+	<doc:param xmlns="">
+	<refpurpose> Improved typesetting of captions  </refpurpose>
+	<doc:description>
+		<para>
+		DB2LaTeX supports <link linkend="param.formal.title.placement">$formal.title.placement</link>
+		as a mechanism for choosing whether captions will appear above or below the objects they describe.
+		<!--
+		($formal.title.placement is described in the <ulink
+		url="http://docbook.sourceforge.net/release/xsl/current/doc/html/formal.title.placement.html">DocBook
+		XSL Stylesheet HTML Parameter Reference</ulink>.)
+		-->
+		However, LaTeX will often produce an ugly result when captions occur
+		above their corresponding content. This usually arises because of
+		unsuitable \abovecaptionskip and \belowcaptionskip.
+		</para>
+		<para>
+		This variable, when set to '1', authorises DB2LaTeX to swap the caption
+		'skip' lengths when a caption is placed <emphasis>above</emphasis> its
+		corresponding content. This is enabled by default.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.caption.swapskip">1</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Control <sgmltag class="element">imagedata</sgmltag> selection. </refpurpose>
+	<doc:description>
+		<para>This controls how DB2LaTeX behaves when a <sgmltag class="element">mediaobject</sgmltag> contains
+		multiple <sgmltag class="element">imagedata</sgmltag>. When non-empty, DB2LaTeX will exclude
+		imagedata that have a format no listed within this variable.</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.graphics.formats"></xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Control Unicode character handling. </refpurpose>
+	<doc:description>
+		<para>
+		Normally, XSLT processors will convert SGML character entities into
+		Unicode characters and DB2LaTeX doesn't have much chance to do anything
+		toward converting them to LaTeX equivalents. We do not yet know how we
+		can solve this problem best.
+		</para>
+		<para>
+		Proposed values: 'catcode', 'unicode', 'extension'.
+		Currently only 'catcode' is supported. All other values will
+		cause no special handling except for certain mappings in MathML.
+		In future, perhaps the 'unicode' LaTeX package could be of assistance.
+		'Extension' could be an XSLT extension that handles the characters
+		using a mapping table.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.entities"></xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Control the use of <sgmltag class="attribute">otherterm</sgmltag> attributes </refpurpose>
+		<doc:description>
+			<para>
+				When a <doc:db>glosssee</doc:db> or <doc:db>glossseealso</doc:db> element contains
+				both an <quote>otherterm</quote> attribute <emphasis>and</emphasis> content templates,
+				this variable elects which will be the source of the displayed text. By default,
+				this variable is enabled and a cross-reference to the otherwterm will be
+				generated (i.e. content templates will be ignored).
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.otherterm.is.preferred">1</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Control the use of <sgmltag class="element">alt</sgmltag> text </refpurpose>
+	<doc:description>
+		<para>
+		By default, DB2LaTeX assumes that <sgmltag class="element">alt</sgmltag>
+		text should be typeset in preference to any 
+		<sgmltag class="element">mediaobject</sgmltag>s.
+		</para>
+	</doc:description>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.tex.math.in.alt"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:param>
+	<xsl:param name="latex.alt.is.preferred">1</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Whether to apply templates for component titles. </refpurpose>
+	<doc:description>
+		<para>
+		Controls whether component titles will be generated by
+		applying templates or by conversion to string values.
+		When enabled, templates will be applied. This enables template
+		expression in titles but may have problematic side-effects such
+		as nested links.
+		</para>
+		<note>
+			<para>
+				This variable does not influence all <sgmltag class="element">title</sgmltag>
+				elements. Some may have their own configuration variables or be non-configurable.
+			</para>
+		</note>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.apply.title.templates">1</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Whether to apply templates for admonition titles. </refpurpose>
+	<doc:description>
+		<para>
+		Controls whether admonition titles will be generated by
+		applying templates or by conversion to string values.
+		When enabled, templates will be applied.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.apply.title.templates.admonitions">1</xsl:param>
+
+	<doc:param xmlns="">
+	<refpurpose> Whether to delimit URLs with quotation characters </refpurpose>
+	<doc:description>
+		<para>
+		When this option is enabled, gentext quotation characters
+		(urlstartquote and urlendquote) are used to delimit the
+		URLs when they are displayed as part of <doc:db>ulink</doc:db>
+		formatting. The delimiters do not form part of the URL or
+		hyperlink per se.
+		</para>
+	</doc:description>
+	</doc:param>
+	<xsl:param name="latex.url.quotation">1</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Control string comparison for <doc:db basename="ulink">ulinks</doc:db> </refpurpose>
+		<doc:description>
+			<para>
+			
+			The formatting of a <doc:db>ulink</doc:db> element varies according
+			to whether its <sgmltag class="attribute">url</sgmltag> attribute
+			differs from its content. When this option is enabled, the
+			comparison between these two values ignores the
+			<quote>protocol</quote> portion of the URL (that which occurs
+			before ':' or '://', as a concession to HTTP URLs). For example,
+			when this option is enabled, <quote>a.b.c/d</quote> would be
+			considered equivalent to <quote>http://a.b.c/d</quote> and
+			<quote>file:a.b.c/d</quote>.
+			
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.ulink.protocols.relaxed">
+      <xsl:choose>
+         <xsl:when test="$ulink.protocols.relaxed!=''">
+            <xsl:message>Warning: $ulink.protocols.relaxed was a misnomer: use $latex.ulink.protocols.relaxed instead</xsl:message>
+            <xsl:value-of select="$ulink.protocols.relaxed"/>
+         </xsl:when>
+			<xsl:otherwise>
+            <xsl:value-of select="0"/>
+			</xsl:otherwise>
+      </xsl:choose>
+   </xsl:param>
+   <xsl:param name="ulink.protocols.relaxed"/>
+
+	<doc:param xmlns="">
+		<refpurpose> Control the suppression of headers/footers on blank pages in double-side documents </refpurpose>
+		<doc:description>
+			<para>
+			
+			When this option is enabled, &DB2LaTeX; will attempt to
+			suppress headers and footers on pages that contain no
+			other content (i.e. left-handed pages in a double-sided
+			document). When this option is disabled, &DB2LaTeX; does
+			not interfere with the default appearance of headers and
+			footers.
+			
+			</para>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.suppress.blank.page.headers">1</xsl:param>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/part-chap-app.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/part-chap-app.mod.xsl
new file mode 100644
index 00000000000..915a23f4d9d
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/part-chap-app.mod.xsl
@@ -0,0 +1,167 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: part-chap-app.mod.xsl,v 1.7 2004/01/18 11:56:29 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="part-chap-app" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: part-chap-app.mod.xsl,v 1.7 2004/01/18 11:56:29 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.4">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Parts, Chapters and Appendixes <filename>part-chap-app.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>set</doc:db>, <doc:db>part</doc:db> and <doc:db>chapter</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes the mapping templates and applies content templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.content-templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="set|part|chapter">
+		<xsl:call-template name="map.begin"/>
+		<xsl:call-template name="content-templates-rootid"/>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<!--
+    <doc:template match="chapter" xmlns="">
+	<refpurpose> XSL template for Chapters.</refpurpose>
+	<doc:description>
+	    <para> This is the main entry point for a <sgmltag class="start">chapter</sgmltag> subtree.
+		This template processes any chapter. Outputs <literal>\chapter{title}</literal>, calls 
+		templates and apply-templates. Since chapters only apply in books, 
+		some assumptions could be done in order to optimize the stylesheet behaviour.</para>
+
+	    <formalpara><title>Remarks and Bugs</title>
+		<itemizedlist>
+		    <listitem><para> 
+			EMPTY templates: chapter/title, 
+			chapter/titleabbrev, 
+			chapter/subtitle, 
+			chapter/docinfo|chapterinfo.</para></listitem>
+		</itemizedlist>
+	    </formalpara>
+
+	    <formalpara><title>Affected by</title> map. 
+	    </formalpara>
+	</doc:description>
+    </doc:template>
+	-->
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>appendix</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats appendices.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				For each appendix, mappings are used and content templates are
+				applies.
+			</para>
+			<para>
+				For <doc:db>appendix</doc:db> elements that occur as children of
+				<doc:db>book</doc:db> or <doc:db>part</doc:db>, the &LaTeX;
+				<function condition="latex">chapter</function> command will be
+				used. Otherwise, the <function condition="latex">section</function>
+				will be used.
+			</para>
+			<para>
+				If an <doc:db>appendix</doc:db> is the first, or the last, then
+				the &LaTeX; mappings for appendix-groups will be invoked in
+				addition to the mapping for the appendix itself. For
+				chapter-level appendices, the <quote>appendices-chapter</quote>
+				is used. Otherwise, the <quote>appendices-section</quote>
+				mapping is used.
+			</para>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.content-templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="appendix">
+		<xsl:if test="not (preceding-sibling::appendix)">
+			<xsl:text>&#10;</xsl:text>
+			<xsl:choose>
+				<xsl:when test="local-name(..)='book' or local-name(..)='part'">
+					<xsl:text>\newcommand{\dbappendix}[1]{\chapter{#1}}%&#10;</xsl:text>
+					<xsl:call-template name="map.begin">
+						<xsl:with-param name="keyword">appendices-chapter</xsl:with-param>
+					</xsl:call-template>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>\newcommand{\dbappendix}[1]{\section{#1}}%&#10;</xsl:text>
+					<xsl:call-template name="map.begin">
+						<xsl:with-param name="keyword">appendices-section</xsl:with-param>
+					</xsl:call-template>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:if>
+		<xsl:call-template name="map.begin"/>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end"/>
+		<xsl:if test="not (following-sibling::appendix)">
+			<xsl:text>&#10;</xsl:text>
+			<xsl:choose>
+				<xsl:when test="local-name(..)='book' or local-name(..)='part'">
+					<xsl:call-template name="map.end">
+						<xsl:with-param name="keyword">appendices-chapter</xsl:with-param>
+					</xsl:call-template>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:call-template name="map.end">
+						<xsl:with-param name="keyword">appendices-section</xsl:with-param>
+					</xsl:call-template>
+				</xsl:otherwise>
+			</xsl:choose>
+			<xsl:text>&#10;</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/pi.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/pi.mod.xsl
new file mode 100644
index 00000000000..efaf4974257
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/pi.mod.xsl
@@ -0,0 +1,231 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: pi.mod.xsl,v 1.6 2004/01/01 11:37:00 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="pi" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: pi.mod.xsl,v 1.6 2004/01/01 11:37:00 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.12">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Processing Instructions <filename>pi.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			Some processing instructions are handled by templates in this file
+			while other are present in <xref linkend="figure"/>, <xref
+			linkend="biblio"/> and <xref linkend="index"/>.
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose> Process generic processing instructions </refpurpose>
+		<doc:description>
+			<para>
+			
+			Processing instructions are allowed but are ignored unless they
+			have a &DB2LaTeX;-specific name.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>This template suppresses processing instructions.</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="processing-instruction()"/>
+
+	<doc:template xmlns="">
+		<refpurpose> Output arbitrary &LaTeX; text </refpurpose>
+		<doc:description>
+			<para>
+			
+			The contents of this processing instruction will
+			output directly by &DB2LaTeX;. This allows the
+			inclusion of &latex;-specific instructions that
+			will be recognised only by &latex; stylesheets.
+			For example, <literal><![CDATA[<?latex \sloppy?>]]></literal>
+			would insert <literal>\sloppy</literal> into the output
+			without any character escaping.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="processing-instruction('latex')">
+		<xsl:value-of select="."/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Output arbitrary &LaTeX; text </refpurpose>
+		<doc:description>
+			<para>
+			
+			The contents of this processing instruction will
+			output directly by &DB2LaTeX;. This allows the
+			inclusion of &latex;-specific instructions that
+			will be recognised only by &latex; stylesheets.
+			For example, <literal><![CDATA[<?latex \sloppy?>]]></literal>
+			would insert <literal>\sloppy</literal> into the output
+			without any character escaping.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="processing-instruction('db2latex')">
+		<xsl:value-of select="."/>
+	</xsl:template>
+
+    <xsl:template match="processing-instruction('rcas')">
+	<xsl:processing-instruction name="dbhtml">
+	    <xsl:value-of select="."/>
+	</xsl:processing-instruction>
+    </xsl:template>
+
+    <xsl:template name="process.cmdsynopsis.list">
+	<xsl:param name="cmdsynopses"/><!-- empty node list by default -->
+	<xsl:param name="count" select="1"/>
+
+	<xsl:choose>
+	    <xsl:when test="$count>count($cmdsynopses)"></xsl:when>
+	    <xsl:otherwise>
+		<xsl:variable name="cmdsyn" select="$cmdsynopses[$count]"/>
+
+		<dt>
+		    <a>
+			<xsl:attribute name="href">
+			    <xsl:call-template name="label.id">
+				<xsl:with-param name="object" select="$cmdsyn"/>
+			    </xsl:call-template>
+			</xsl:attribute>
+
+			<xsl:choose>
+			    <xsl:when test="$cmdsyn/@xreflabel">
+				<xsl:call-template name="xref.xreflabel">
+				    <xsl:with-param name="target" select="$cmdsyn"/>
+				</xsl:call-template>
+			    </xsl:when>
+			    <xsl:otherwise>
+				<!-- RCAS Fixme 
+				<xsl:call-template name="xref.cmdsynopsis">
+				    <xsl:with-param name="target" select="$cmdsyn"/>
+				</xsl:call-template>-->
+			    </xsl:otherwise>
+			</xsl:choose>
+		    </a>
+		</dt>
+
+		<xsl:call-template name="process.cmdsynopsis.list">
+		    <xsl:with-param name="cmdsynopses" select="$cmdsynopses"/>
+		    <xsl:with-param name="count" select="$count+1"/>
+		</xsl:call-template>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="processing-instruction('dbcmdlist')">
+	<xsl:variable name="cmdsynopses" select="..//cmdsynopsis"/>
+
+	<xsl:if test="count($cmdsynopses)&lt;1">
+	    <xsl:message><xsl:text>No cmdsynopsis elements matched dbcmdlist PI, perhaps it's nested too deep?</xsl:text>
+	    </xsl:message>
+	</xsl:if>
+
+	<dl>
+	    <xsl:call-template name="process.cmdsynopsis.list">
+		<xsl:with-param name="cmdsynopses" select="$cmdsynopses"/>
+	    </xsl:call-template>
+	</dl>
+    </xsl:template>
+
+    <!-- ==================================================================== -->
+
+    <xsl:template name="process.funcsynopsis.list">
+	<xsl:param name="funcsynopses"/><!-- empty node list by default -->
+	<xsl:param name="count" select="1"/>
+
+	<xsl:choose>
+	    <xsl:when test="$count>count($funcsynopses)"></xsl:when>
+	    <xsl:otherwise>
+		<xsl:variable name="cmdsyn" select="$funcsynopses[$count]"/>
+
+		<dt>
+		    <a>
+			<xsl:attribute name="href">
+			    <xsl:call-template name="label.id">
+				<xsl:with-param name="object" select="$cmdsyn"/>
+			    </xsl:call-template>
+			</xsl:attribute>
+
+			<xsl:choose>
+			    <xsl:when test="$cmdsyn/@xreflabel">
+				<xsl:call-template name="xref.xreflabel">
+				    <xsl:with-param name="target" select="$cmdsyn"/>
+				</xsl:call-template>
+			    </xsl:when>
+			    <xsl:otherwise>
+				<!-- RCAS Fixme 
+				<xsl:call-template name="xref.funcsynopsis">
+				    <xsl:with-param name="target" select="$cmdsyn"/>
+				</xsl:call-template>
+				-->
+			    </xsl:otherwise>
+			</xsl:choose>
+		    </a>
+		</dt>
+
+		<xsl:call-template name="process.funcsynopsis.list">
+		    <xsl:with-param name="funcsynopses" select="$funcsynopses"/>
+		    <xsl:with-param name="count" select="$count+1"/>
+		</xsl:call-template>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="processing-instruction('dbfunclist')">
+	<xsl:variable name="funcsynopses" select="..//funcsynopsis"/>
+
+	<xsl:if test="count($funcsynopses)&lt;1">
+	    <xsl:message><xsl:text>No funcsynopsis elements matched dbfunclist PI, perhaps it's nested too deep?</xsl:text>
+	    </xsl:message>
+	</xsl:if>
+
+	<dl>
+	    <xsl:call-template name="process.funcsynopsis.list">
+		<xsl:with-param name="funcsynopses" select="$funcsynopses"/>
+	    </xsl:call-template>
+	</dl>
+    </xsl:template>
+
+    <!-- ==================================================================== -->
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/preamble.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/preamble.mod.xsl
new file mode 100644
index 00000000000..3fce8c2a402
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/preamble.mod.xsl
@@ -0,0 +1,1131 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: preamble.mod.xsl,v 1.82 2004/01/31 12:26:12 j-devenish Exp $		
+|- #############################################################################
+|	$Author: j-devenish $
+|
+|   PURPOSE: Variables and templates to manage LaTeX preamble.
++ ############################################################################## -->
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="preamble" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: preamble.mod.xsl,v 1.82 2004/01/31 12:26:12 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.77">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Variables and Templates used in &LaTeX; Preamble Generation</title>
+		<partintro>
+			<para>
+			
+			This section described the variables and templates that are used in
+			the generation of the output &LaTeX; preamble. Basically, the
+			&LaTeX; preamble depends on the <acronym>XML</acronym> document, that is, on whether
+			it is an <doc:db>article</doc:db> or a <doc:db>book</doc:db>.
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template name="generate.latex.article.preamble" xmlns="">
+		<refpurpose>
+
+			Top level template, called by article template, responsible of
+			generating the &LaTeX; preamble according to user
+			<acronym>XSL</acronym> variables and templates.
+
+		</refpurpose>
+		<doc:description>
+			<para>
+
+			If <xref linkend="param.latex.override"/> is empty, the template
+			outputs <xref linkend="param.latex.article.preamblestart"/> and
+			<xref linkend="param.latex.article.preamble.pre"/>, then calls
+			<xref linkend="template.generate.latex.common.preamble"/> and <xref
+			linkend="template.generate.latex.essential.preamble"/> followed by
+			the value of <xref linkend="param.latex.article.preamble.post"/>.
+			Otherwise, it outputs the value of <xref linkend="param.latex.override"/>
+			followed by <xref
+			linkend="template.generate.latex.essential.preamble"/>.
+
+			</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template name="generate.latex.article.preamble">
+		<xsl:choose>
+			<xsl:when test="$latex.override = ''">
+				<xsl:value-of select="$latex.article.preamblestart"/>
+				<xsl:value-of select="$latex.article.preamble.pre"/>
+				<xsl:call-template name="label.id"/>
+				<xsl:call-template name="generate.latex.common.preamble"/>
+				<xsl:call-template name="generate.latex.essential.preamble"/>
+				<xsl:value-of select="$latex.article.preamble.post"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="$latex.override"/>
+				<xsl:call-template name="generate.latex.essential.preamble"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template name="generate.latex.book.preamble" xmlns="">
+		<refpurpose>
+
+			Top level template, called by book template, responsible of
+			generating the &LaTeX; preamble according to user
+			<acronym>XSL</acronym> variables and templates.
+
+		</refpurpose>
+		<doc:description>
+			<para>
+
+			If <xref linkend="param.latex.override"/> is empty, the template
+			outputs <xref linkend="param.latex.book.preamblestart"/> and
+			<xref linkend="param.latex.book.preamble.pre"/>, then calls
+			<xref linkend="template.generate.latex.common.preamble"/> and <xref
+			linkend="template.generate.latex.essential.preamble"/> followed by
+			the value of <xref linkend="param.latex.book.preamble.post"/>.
+			Otherwise, it outputs the value of <xref linkend="param.latex.override"/>
+			followed by <xref
+			linkend="template.generate.latex.essential.preamble"/>.
+
+			</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template name="generate.latex.book.preamble">
+		<xsl:choose>
+			<xsl:when test="$latex.override = ''">
+				<xsl:value-of select="$latex.book.preamblestart"/>
+				<xsl:value-of select="$latex.book.preamble.pre"/>
+				<xsl:call-template name="label.id"/>
+				<xsl:call-template name="generate.latex.common.preamble"/>
+				<xsl:call-template name="generate.latex.essential.preamble"/>
+				<xsl:value-of select="$latex.book.preamble.post"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="$latex.override"/>
+				<xsl:call-template name="generate.latex.essential.preamble"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:param name="latex.article.preamblestart" xmlns="">
+		<refpurpose> Generate <function condition="latex">documentclass</function> for <doc:db basename="article">articles</doc:db>  </refpurpose>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.documentclass.common"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.documentclass.article"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.documentclass.pdftex"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.documentclass.dvips"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.documentclass"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:description>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.article.preamblestart">
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>% Autogenerated LaTeX file for articles&#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>\ifx\pdfoutput\undefined&#10;</xsl:text>
+		<xsl:text>\documentclass[</xsl:text>
+		<xsl:value-of select='$latex.documentclass.common' />
+		<xsl:text>,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.article' />
+		<xsl:text>,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.pdftex' />
+		<xsl:text>]{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="$latex.documentclass!=''"><xsl:value-of select="$latex.documentclass" /></xsl:when>
+			<xsl:otherwise><xsl:text>article</xsl:text></xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:text>\else&#10;</xsl:text>
+		<xsl:text>\documentclass[pdftex,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.common' />
+		<xsl:text>,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.article' />
+		<xsl:text>,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.dvips' />
+		<xsl:text>]{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="$latex.documentclass!=''"><xsl:value-of select="$latex.documentclass" /></xsl:when>
+			<xsl:otherwise><xsl:text>article</xsl:text></xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:text>\fi&#10;</xsl:text>
+	</xsl:param>
+
+	<doc:param name="latex.book.preamblestart" xmlns="">
+		<refpurpose> Generate <function condition="latex">documentclass</function> for <doc:db basename="book">books</doc:db>  </refpurpose>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.documentclass.common"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.documentclass.book"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.documentclass.pdftex"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.documentclass.dvips"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.documentclass"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:description>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.book.preamblestart">
+		<xsl:text>% ------------------------------------------------------------	&#10;</xsl:text>
+		<xsl:text>% Autogenerated LaTeX file for books	&#10;</xsl:text>
+		<xsl:text>% ------------------------------------------------------------	&#10;</xsl:text>
+		<xsl:text>\ifx\pdfoutput\undefined&#10;</xsl:text>
+		<xsl:text>\documentclass[</xsl:text>
+		<xsl:value-of select='$latex.documentclass.common' />
+		<xsl:text>,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.book' />
+		<xsl:text>,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.pdftex' />
+		<xsl:text>]{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="$latex.documentclass!=''"><xsl:value-of select="$latex.documentclass" /></xsl:when>
+			<xsl:otherwise><xsl:text>report</xsl:text></xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:text>\else&#10;</xsl:text>
+		<xsl:text>\documentclass[pdftex,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.common' />
+		<xsl:text>,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.book' />
+		<xsl:text>,</xsl:text>
+		<xsl:value-of select='$latex.documentclass.dvips' />
+		<xsl:text>]{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="$latex.documentclass!=''"><xsl:value-of select="$latex.documentclass" /></xsl:when>
+			<xsl:otherwise><xsl:text>report</xsl:text></xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:text>\fi&#10;</xsl:text>
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Select localisation language  </refpurpose>
+		<doc:description>
+			<para>
+				Chooses the <quote>gentext</quote> language for the document.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				Selects the root <doc:db>set</doc:db>, <doc:db>book</doc:db> or
+				<doc:db>article</doc:db> element and reads its <sgmltag
+				class="attribute">lang</sgmltag> or <sgmltag
+				class="attribute">xml:lang</sgmltag> attribute.
+
+			</para>
+		</doc:notes>
+	</doc:param>
+	<xsl:param name="document.xml.language">
+		<xsl:call-template name="l10n.language">
+			<xsl:with-param name="target" select="(/set|/book|/article)[1]"/>
+			<!-- now, induce the use of $target rather than the current node: -->
+			<xsl:with-param name="xref-context" select="true()"/>
+		</xsl:call-template>
+	</xsl:param>
+
+	<doc:param xmlns="">
+		<refpurpose> Select <productname>babel</productname> option </refpurpose>
+		<doc:description>
+			<para>
+				If <xref linkend="param.latex.babel.language"/> is not set, this
+				template will select a <productname>babel</productname> option
+				based on the <xref linkend="param.document.xml.language"/>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.babel.language"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.document.xml.language"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>A special value of <quote><literal>none</literal></quote>
+			can be used to disable <productname>babel</productname>.</para>
+		</doc:notes>
+	</doc:param>
+	<xsl:param name="latex.language.option">
+		<xsl:choose>
+			<xsl:when test="$latex.babel.language!=''">
+				<xsl:value-of select="$latex.babel.language"/>
+			</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'af')">afrikaans</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'br')">breton</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'ca')">catalan</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'cs')">czech</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'cy')">welsh</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'da')">danish</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'de')">ngerman</xsl:when><!-- ngerman, german or germanb? -->
+			<xsl:when test="starts-with($document.xml.language,'el')">greek</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'en')">
+				<xsl:choose>
+					<xsl:when test="starts-with($document.xml.language,'en-CA')">canadian</xsl:when>
+					<xsl:when test="starts-with($document.xml.language,'en-GB')">british</xsl:when>
+					<xsl:when test="starts-with($document.xml.language,'en-US')">USenglish</xsl:when>
+					<xsl:otherwise>none</xsl:otherwise>
+				</xsl:choose>
+			</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'eo')">esperanto</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'es')">spanish</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'et')">estonian</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'fi')">finnish</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'fr')">french</xsl:when><!-- francais, french, or frenchb? -->
+			<xsl:when test="starts-with($document.xml.language,'ga')">irish</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'gd')">scottish</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'gl')">galician</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'he')">hebrew</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'hr')">croatian</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'hu')">hungarian</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'id')">bahasa</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'it')">italian</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'nl')">dutch</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'nn')">norsk</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'pl')">polish</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'pt')">
+				<xsl:choose>
+					<xsl:when test="starts-with($document.xml.language,'pt-BR')">brazil</xsl:when>
+					<xsl:otherwise>portugese</xsl:otherwise>
+				</xsl:choose>
+			</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'ro')">romanian</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'ru')">russian</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'sk')">slovak</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'sl')">slovene</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'sv')">swedish</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'tr')">turkish</xsl:when>
+			<xsl:when test="starts-with($document.xml.language,'uk')">ukrainian</xsl:when>
+		</xsl:choose>
+	</xsl:param>
+
+	<doc:template xmlns="">
+		<refpurpose>
+
+			Common &LaTeX; preamble shared by <doc:db>articles</doc:db> and
+			<doc:db>books</doc:db>, and other document classes. Most of the
+			packages and package options are managed here.
+
+		</refpurpose>
+		<doc:description>
+			<para>
+
+			The &LaTeX; preamble, after the <function
+			condition="latex">documentclass</function> command but before the
+			<function condition="env">document</function> environment.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.pdf.support"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.pdf.preamble"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.article.varsets"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.book.varsets"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.bridgehead.in.lot"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.fancyhdr"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.fancyhdr.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.fancyhdr.truncation.partition"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.fancyhdr.truncation.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.varioref"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.varioref.options"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.dcolumn"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.decimal.point"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.fancybox"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.fancyvrb"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.fancyvrb.tabsize"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.isolatin1"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.parskip"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.rotating"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.subfigure"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.tabularx"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.umoline"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.url"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.math.support"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.math.preamble"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.document.font"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.hyperref"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.admonition.environment"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.caption.swapskip"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.hyphenation.tttricks"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.language.option"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.is.draft"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.generate.latex.pagestyle"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.gentext.dingbat"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.hyperref.preamble"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.float.preamble"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.graphicext"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.generate.latex.draft.preamble"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="generate.latex.common.preamble">
+		<xsl:choose>
+			<xsl:when test="$latex.pdf.support=1"><xsl:value-of select="$latex.pdf.preamble"/></xsl:when>
+			<xsl:otherwise><xsl:text>\usepackage{graphicx}&#10;</xsl:text></xsl:otherwise>
+		</xsl:choose>
+		<xsl:if test="local-name(.)='article'">
+			<xsl:value-of select="$latex.article.varsets"/>
+		</xsl:if>
+		<xsl:if test="local-name(.)='book'">
+			<xsl:value-of select="$latex.book.varsets"/>
+		</xsl:if>
+		<xsl:if test="$latex.bridgehead.in.lot=1">
+			<xsl:text><![CDATA[
+\makeatletter
+% redefine the listoffigures and listoftables so that the name of the chapter
+% is printed whenever there are figures or tables from that chapter. encourage
+% pagebreak prior to the name of the chapter (discourage orphans).
+\let\save@@chapter\@chapter
+\let\save@@l@figure\l@figure
+\let\the@l@figure@leader\relax
+\def\@chapter[#1]#2{\save@@chapter[{#1}]{#2}%
+\addtocontents{lof}{\protect\def\the@l@figure@leader{\protect\pagebreak[0]\protect\contentsline{chapter}{\protect\numberline{\thechapter}#1}{}{\thepage}}}%
+\addtocontents{lot}{\protect\def\the@l@figure@leader{\protect\pagebreak[0]\protect\contentsline{chapter}{\protect\numberline{\thechapter}#1}{}{\thepage}}}%
+}
+\renewcommand*\l@figure{\the@l@figure@leader\let\the@l@figure@leader\relax\save@@l@figure}
+\let\l@table\l@figure
+\makeatother
+]]></xsl:text>
+		</xsl:if>
+		<xsl:if test="$latex.use.fancyhdr=1">
+			<xsl:text>\usepackage{fancyhdr}&#10;</xsl:text>
+			<xsl:text>\renewcommand{\headrulewidth}{0.4pt}&#10;</xsl:text>
+			<xsl:text>\renewcommand{\footrulewidth}{0.4pt}&#10;</xsl:text>
+			<xsl:if test="$latex.fancyhdr.truncation.partition!=''">
+				<xsl:variable name="partition">
+					<xsl:value-of select="round(number($latex.fancyhdr.truncation.partition))"/>
+				</xsl:variable>
+				<xsl:variable name="left.fraction">
+					<xsl:choose>
+						<xsl:when test="$partition&lt;1">
+							<xsl:text>0</xsl:text>
+						</xsl:when>
+						<xsl:when test="$partition>97">
+							<xsl:text>.98</xsl:text>
+						</xsl:when>
+						<xsl:otherwise>
+							<!-- example: 60 becomes .59 -->
+							<xsl:value-of select="($partition - 1) div 100"/>
+						</xsl:otherwise>
+					</xsl:choose>
+				</xsl:variable>
+				<xsl:variable name="right.fraction" select="0.98 - number($left.fraction)"/>
+				<xsl:text>% Safeguard against long headers.&#10;</xsl:text>
+				<xsl:text>\IfFileExists{truncate.sty}{&#10;</xsl:text>
+				<xsl:text>\usepackage{truncate}&#10;</xsl:text>
+				<xsl:text>% Use an ellipsis when text would be larger than x% of the text width.&#10;</xsl:text>
+				<xsl:text>% Preserve left/right text alignment using \hfill (works for English).&#10;</xsl:text>
+				<xsl:choose>
+					<xsl:when test="$latex.fancyhdr.truncation.style='lr'">
+						<!-- left vs. right -->
+						<xsl:choose>
+							<xsl:when test="$left.fraction &gt; 0.02">
+								<xsl:text>\fancyhead[ol]{\truncate{</xsl:text><xsl:value-of select="$left.fraction"/><xsl:text>\textwidth}{\sl\leftmark}}&#10;</xsl:text>
+								<xsl:text>\fancyhead[el]{\truncate{</xsl:text><xsl:value-of select="$left.fraction"/><xsl:text>\textwidth}{\sl\leftmark}}&#10;</xsl:text>
+							</xsl:when>
+							<xsl:otherwise>
+								<xsl:text>\fancyhead[ol]{}&#10;</xsl:text>
+								<xsl:text>\fancyhead[el]{}&#10;</xsl:text>
+							</xsl:otherwise>
+						</xsl:choose>
+						<xsl:choose>
+							<xsl:when test="$right.fraction &gt; 0.02">
+								<xsl:text>\fancyhead[or]{\truncate{</xsl:text><xsl:value-of select="$right.fraction"/><xsl:text>\textwidth}{\hfill\sl\rightmark}}&#10;</xsl:text>
+								<xsl:text>\fancyhead[er]{\truncate{</xsl:text><xsl:value-of select="$right.fraction"/><xsl:text>\textwidth}{\hfill\sl\rightmark}}&#10;</xsl:text>
+							</xsl:when>
+							<xsl:otherwise>
+								<xsl:text>\fancyhead[or]{}&#10;</xsl:text>
+								<xsl:text>\fancyhead[er]{}&#10;</xsl:text>
+							</xsl:otherwise>
+						</xsl:choose>
+					</xsl:when>
+					<xsl:otherwise>
+						<!-- inside vs. outside -->
+						<xsl:choose>
+							<xsl:when test="$left.fraction &gt; 0.02">
+								<xsl:text>\fancyhead[ol]{\truncate{</xsl:text><xsl:value-of select="$left.fraction"/><xsl:text>\textwidth}{\sl\leftmark}}&#10;</xsl:text>
+								<xsl:text>\fancyhead[er]{\truncate{</xsl:text><xsl:value-of select="$left.fraction"/><xsl:text>\textwidth}{\hfill\sl\rightmark}}&#10;</xsl:text>
+							</xsl:when>
+							<xsl:otherwise>
+								<xsl:text>\fancyhead[ol]{}&#10;</xsl:text>
+								<xsl:text>\fancyhead[er]{}&#10;</xsl:text>
+							</xsl:otherwise>
+						</xsl:choose>
+						<xsl:choose>
+							<xsl:when test="$right.fraction &gt; 0.02">
+								<xsl:text>\fancyhead[el]{\truncate{</xsl:text><xsl:value-of select="$right.fraction"/><xsl:text>\textwidth}{\sl\leftmark}}&#10;</xsl:text>
+								<xsl:text>\fancyhead[or]{\truncate{</xsl:text><xsl:value-of select="$right.fraction"/><xsl:text>\textwidth}{\hfill\sl\rightmark}}&#10;</xsl:text>
+							</xsl:when>
+							<xsl:otherwise>
+								<xsl:text>\fancyhead[el]{}&#10;</xsl:text>
+								<xsl:text>\fancyhead[or]{}&#10;</xsl:text>
+							</xsl:otherwise>
+						</xsl:choose>
+					</xsl:otherwise>
+				</xsl:choose>
+				<xsl:text>}{\typeout{WARNING: truncate.sty wasn't available and functionality was skipped.}}&#10;</xsl:text>
+			</xsl:if>
+			<xsl:choose>
+				<xsl:when test="$latex.fancyhdr.style='natural'">
+					<xsl:text><![CDATA[
+\makeatletter
+% Override the default from fancyhdr (which would be to have all-caps headings).
+\newcommand{\dblatex@chaptermark}[1]{\markboth{{\ifnum \c@secnumdepth>\m@ne \@chapapp\ \thechapter. \ \fi #1}}{}}
+\def\dblatex@chaptersmark#1{\markboth{{#1}}{}}
+\newcommand{\dblatex@sectionmark}[1]{\markright{{\ifnum \c@secnumdepth >\z@ \thesection. \ \fi #1}}}
+\let\dblatex@ps@fancy\ps@fancy
+\def\ps@fancy{
+	\dblatex@ps@fancy
+	\let\chaptermark\dblatex@chaptermark
+	\let\sectionmark\dblatex@sectionmark
+}
+\makeatother
+]]></xsl:text>
+				</xsl:when>
+			</xsl:choose>
+			<xsl:call-template name="generate.latex.pagestyle"/>
+			<!-- 
+			Add dollar...
+			<xsl:if test="latex.fancyhdr.lh !=''"><xsl:text>\lhead{</xsl:text><xsl:value-of select="$latex.fancyhdr.lh"/><xsl:text>}&#10;</xsl:text></xsl:if>
+			<xsl:if test="latex.fancyhdr.ch !=''"><xsl:text>\chead{</xsl:text><xsl:value-of select="$latex.fancyhdr.ch"/><xsl:text>}&#10;</xsl:text></xsl:if>
+			<xsl:if test="latex.fancyhdr.rh !=''"><xsl:text>\rhead{</xsl:text><xsl:value-of select="$latex.fancyhdr.rh"/><xsl:text>}&#10;</xsl:text></xsl:if>
+			<xsl:if test="latex.fancyhdr.lf !=''"><xsl:text>\lfoot{</xsl:text><xsl:value-of select="$latex.fancyhdr.lf"/><xsl:text>}&#10;</xsl:text></xsl:if>
+			<xsl:if test="latex.fancyhdr.cf !=''"><xsl:text>\cfoot{</xsl:text><xsl:value-of select="$latex.fancyhdr.cf"/><xsl:text>}&#10;</xsl:text></xsl:if>
+			<xsl:if test="latex.fancyhdr.rf !=''"><xsl:text>\rfoot{</xsl:text><xsl:value-of select="$latex.fancyhdr.rf"/><xsl:text>}&#10;</xsl:text></xsl:if> 
+			-->
+		</xsl:if>
+		<xsl:text>% ---------------------- &#10;</xsl:text>
+		<xsl:text>% Most Common Packages   &#10;</xsl:text>
+		<xsl:text>% ---------------------- &#10;</xsl:text>
+		<xsl:if test="$latex.use.varioref=1">
+			<xsl:text>\usepackage[</xsl:text>
+			<xsl:value-of select="$latex.varioref.options"/>
+			<xsl:text>]{varioref} &#10;</xsl:text>
+		</xsl:if>
+		<xsl:text>\usepackage{latexsym}         &#10;</xsl:text>
+		<xsl:if test="$latex.use.dcolumn=1">
+			<xsl:text>\usepackage{dcolumn}      &#10;</xsl:text>
+			<xsl:text>% Default decimal point-style column&#10;</xsl:text>
+			<xsl:text>\newcolumntype{d}{D{</xsl:text>
+			<xsl:call-template name="gentext.dingbat">
+				<xsl:with-param name="dingbat">decimalpoint</xsl:with-param>
+			</xsl:call-template>
+			<xsl:text>}{</xsl:text>
+			<xsl:choose>
+				<xsl:when test="$latex.decimal.point!=''">
+					<xsl:value-of select="$latex.decimal.point"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:call-template name="gentext.dingbat">
+						<xsl:with-param name="dingbat">latexdecimal</xsl:with-param>
+					</xsl:call-template>
+				 </xsl:otherwise>
+			</xsl:choose>
+			<xsl:text>}{-1}}&#10;</xsl:text>
+		</xsl:if>
+		<xsl:text>\usepackage{enumerate}         &#10;</xsl:text>
+		<xsl:if test="$latex.use.fancybox=1">
+			<!-- must be before \usepackage{fancyvrb} -->
+			<xsl:text>\usepackage{fancybox}      &#10;</xsl:text>
+		</xsl:if>
+		<xsl:text>\usepackage{float}       &#10;</xsl:text>
+		<xsl:text>\usepackage{ragged2e}       &#10;</xsl:text>
+		<xsl:if test="$latex.use.fancyvrb=1">
+			<!-- must be after \usepackage{fancybox} -->
+			<xsl:text>\usepackage{fancyvrb}         &#10;</xsl:text>
+			<xsl:text>\makeatletter\@namedef{FV@fontfamily@default}{\def\FV@FontScanPrep{}\def\FV@FontFamily{}}\makeatother&#10;</xsl:text>
+			<xsl:if test="$latex.fancyvrb.tabsize!=''">
+				<xsl:text>\fvset{obeytabs=true,tabsize=</xsl:text>
+				<xsl:value-of select="$latex.fancyvrb.tabsize"/>
+				<xsl:text>}&#10;</xsl:text>
+			</xsl:if>
+		</xsl:if>
+		<xsl:if test="$latex.use.isolatin1=1">
+			<xsl:message>Please use $latex.inputenc='latin1' instead of $latex.use.isolatin1='1'.</xsl:message>
+			<xsl:text>\usepackage{isolatin1}         &#10;</xsl:text>
+		</xsl:if>
+		<xsl:choose>
+			<xsl:when test="$latex.use.parskip=1">
+				<xsl:text>\usepackage{parskip}         &#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<!-- hack from parksip to stop excess whitespace after figure captions -->
+				<xsl:text><![CDATA[\makeatletter
+\let\dblatex@center\center\let\dblatex@endcenter\endcenter
+\def\dblatex@nolistI{\leftmargin\leftmargini\topsep\z@ \parsep\parskip \itemsep\z@}
+\def\center{\let\@listi\dblatex@nolistI\@listi\dblatex@center\let\@listi\@listI\@listi}
+\def\endcenter{\dblatex@endcenter}
+\makeatother
+]]></xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:if test="$latex.use.rotating=1"><xsl:text>\usepackage{rotating}         &#10;</xsl:text></xsl:if>
+		<xsl:if test="$latex.use.subfigure=1"><xsl:text>\usepackage{subfigure}         &#10;</xsl:text></xsl:if>
+		<xsl:if test="$latex.use.tabularx=1"><xsl:text>\usepackage{tabularx}         &#10;</xsl:text></xsl:if>
+		<xsl:if test="$latex.use.ltxtable=1 or $latex.use.longtable=1"><xsl:text>\usepackage{longtable}         &#10;</xsl:text></xsl:if>
+		<xsl:if test="$latex.use.umoline=1"><xsl:text>\usepackage{umoline}         &#10;</xsl:text></xsl:if>
+		<xsl:if test="$latex.use.url=1"><xsl:text>\usepackage{url}         &#10;</xsl:text></xsl:if>
+		<xsl:if test="$latex.math.support=1"><xsl:value-of select="$latex.math.preamble"/></xsl:if>
+
+		<!-- Configure document font. -->
+		<xsl:if test="$latex.document.font != 'default'">
+			<xsl:text>% ---------------&#10;</xsl:text>
+			<xsl:text>% Document Font  &#10;</xsl:text>
+			<xsl:text>% ---------------&#10;</xsl:text>
+			<xsl:text>\usepackage{</xsl:text><xsl:value-of select="$latex.document.font"/><xsl:text>}&#10;</xsl:text>
+		</xsl:if>
+
+		<xsl:if test="$latex.use.hyperref=1">
+			<xsl:call-template name="latex.hyperref.preamble"/>
+		</xsl:if>
+		<xsl:value-of select="$latex.admonition.environment"/>
+		<xsl:call-template name="latex.float.preamble"/>
+		<xsl:call-template name="latex.graphicext"/>
+		<xsl:choose>
+			<xsl:when test='$latex.caption.swapskip=1'>
+				<xsl:text>% --------------------------------------------&#10;</xsl:text>
+				<xsl:text>% $latex.caption.swapskip enabled for $formal.title.placement support&#10;</xsl:text>
+				<xsl:text>\newlength{\docbooktolatextempskip}&#10;</xsl:text>
+				<xsl:text>\newcommand{\captionswapskip}{\setlength{\docbooktolatextempskip}{\abovecaptionskip}</xsl:text>
+				<xsl:text>\setlength{\abovecaptionskip}{\belowcaptionskip}</xsl:text>
+				<xsl:text>\setlength{\belowcaptionskip}{\docbooktolatextempskip}}&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>\newcommand{\captionswapskip}{}&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:if test='$latex.hyphenation.tttricks=1'>
+			<xsl:text>% --------------------------------------------&#10;</xsl:text>
+			<xsl:text>% Better linebreaks&#10;</xsl:text>
+			<xsl:text>\newcommand{\docbookhyphenatedot}[1]{{\hyphenchar\font=`\.\relax #1\hyphenchar\font=`\-}}&#10;</xsl:text>
+			<xsl:text>\newcommand{\docbookhyphenatefilename}[1]{{\hyphenchar\font=`\.\relax #1\hyphenchar\font=`\-}}&#10;</xsl:text>
+			<xsl:text>\newcommand{\docbookhyphenateurl}[1]{{\hyphenchar\font=`\/\relax #1\hyphenchar\font=`\-}}&#10;</xsl:text>
+		</xsl:if>
+		<!--
+		<xsl:message>$document.xml.language: '<xsl:value-of select="$document.xml.language"/>'</xsl:message>
+		<xsl:message>$latex.language.option: '<xsl:value-of select="$latex.language.option"/>'</xsl:message>
+		-->
+		<xsl:if test="$latex.language.option!='none'">
+			<xsl:text>\usepackage[</xsl:text><xsl:value-of select="$latex.language.option" /><xsl:text>]{babel} &#10;</xsl:text>
+		</xsl:if>
+		<xsl:if test="$latex.use.hyperref='1'">
+			<xsl:text>% Guard against a problem with old package versions.&#10;</xsl:text>
+			<xsl:text>\makeatletter&#10;</xsl:text>
+			<xsl:text>\AtBeginDocument{&#10;</xsl:text>
+			<xsl:text>\DeclareRobustCommand\ref{\@refstar}&#10;</xsl:text>
+			<xsl:text>\DeclareRobustCommand\pageref{\@pagerefstar}&#10;</xsl:text>
+			<xsl:text>}&#10;</xsl:text>
+			<xsl:text>\makeatother&#10;</xsl:text>
+		</xsl:if>
+		<xsl:choose>
+			<xsl:when test="$latex.is.draft!=''">
+				<xsl:if test="$latex.is.draft=1">
+					<xsl:call-template name="generate.latex.draft.preamble"/>
+				</xsl:if>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:if test="(/set|/book|/article)[1]/@status='draft'">
+					<xsl:call-template name="generate.latex.draft.preamble"/>
+				</xsl:if>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>
+
+			Common &LaTeX; preamble shared by <doc:db basename="article">article</doc:db> and
+			<doc:db basename="book">book</doc:db> when their <sgmltag
+			class="attribute">status</sgmltag> is <quote>draft</quote>.
+
+		</refpurpose>
+		<doc:description>
+			<para>
+
+			
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.is.draft"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.varioref"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_index_draft;
+				&test_draft;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template name="generate.latex.draft.preamble">
+		<xsl:choose>
+			<xsl:when test="$latex.use.varioref='1'">
+				<xsl:message>Combining varioref with showkeys (and hyperref?) is not supported.</xsl:message>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>\usepackage[color]{showkeys}&#10;</xsl:text>
+				<xsl:text>\definecolor{refkey}{gray}{0.5}&#10;</xsl:text>
+				<xsl:text>\definecolor{labelkey}{gray}{0.5}&#10;</xsl:text>
+				<xsl:text>% Rip off things from showkeys to highlight index references&#10;</xsl:text>
+				<xsl:text>\definecolor{indexkey}{gray}{.5}%&#10;</xsl:text>
+				<xsl:text>\makeatletter&#10;</xsl:text>
+				<xsl:text>\def\SK@indexcolor{\color{indexkey}}&#10;</xsl:text>
+				<xsl:text>\def\SK@@@index#1{\@bsphack\SK@\SK@@index{#1}\begingroup\SK@index{#1}\endgroup\@esphack}&#10;</xsl:text>
+				<xsl:text>\def\SK@@index#1>#2\SK@{\leavevmode\vbox to\z@{\vss \SK@indexcolor \rlap{\vrule\raise .75em\hbox{}{\circle*{5}}}}}&#10;</xsl:text>
+				<xsl:text>\AtBeginDocument{\let\SK@index\index&#10;\let\index\SK@@@index}&#10;</xsl:text>
+				<xsl:text>\makeatother&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Unavoidable &LaTeX; preamble shared by <doc:db
+		basename="article">articles</doc:db> and <doc:db
+		basename="book">books</doc:db>  </refpurpose>
+		<doc:description>
+			<para>Contains custom commands <emphasis>that you just can't get rid of!</emphasis></para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.hyperref"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.suppress.blank.page.headers"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.ucs"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.entities"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.ucs.options"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.inputenc"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.fontenc"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.latex.preamble.essential.biblio"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.preamble.essential.callout"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.preamble.essential.citation"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.preamble.essential.footnote"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.preamble.essential.glossary"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.latex.preamble.essential.index"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="generate.latex.essential.preamble">
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>\makeatletter&#10;</xsl:text>
+		<xsl:text>\newcommand{\dbz}{\penalty \z@}&#10;</xsl:text>
+		<xsl:text>\newcommand{\docbooktolatexpipe}{\ensuremath{|}\dbz}&#10;</xsl:text>
+		<xsl:text>\newskip\docbooktolatexoldparskip&#10;</xsl:text>
+		<xsl:text>\newcommand{\docbooktolatexnoparskip}{\docbooktolatexoldparskip=\parskip\parskip=0pt plus 1pt}&#10;</xsl:text>
+		<xsl:text>\newcommand{\docbooktolatexrestoreparskip}{\parskip=\docbooktolatexoldparskip}&#10;</xsl:text>
+		<xsl:if test="$latex.use.hyperref!='1'">
+			<xsl:text>\newcommand{\href}[1]{{}}&#10;</xsl:text>
+			<xsl:text>\newcommand{\hyperlink}[1]{{}}&#10;</xsl:text>
+			<xsl:text>\newcommand{\hypertarget}[2]{#2}&#10;</xsl:text>
+		</xsl:if>
+		<!-- don't print headings on blank pages -->
+		<xsl:if test="$latex.suppress.blank.page.headers=1">
+			<xsl:text>\def\cleardoublepage{\clearpage\if@twoside \ifodd\c@page\else\hbox{}\thispagestyle{empty}\newpage\if@twocolumn\hbox{}\newpage\fi\fi\fi}&#10;</xsl:text>
+		</xsl:if>
+		<xsl:if test="$latex.use.ucs='1'">
+			<xsl:text>\usepackage[</xsl:text>
+			<xsl:value-of select="$latex.ucs.options"/>
+			<xsl:text>]{ucs}&#10;</xsl:text>
+		</xsl:if>
+		<xsl:if test="$latex.entities='catcode'">
+			<xsl:text>\catcode`\&amp;=\active\def&amp;{\@ifnextchar##{\begingroup\@sanitize\@docbooktolatexunicode\@gobble}{\&amp;}}&#10;</xsl:text>
+			<xsl:if test="$latex.use.ucs!='1'">
+				<xsl:text><![CDATA[
+% A few example Unicode characters.
+% For full support, use the unicode pacakge from Dominique Unruh/CTAN.
+%	\else\ifnum#1=8216{\textquoteleft}%
+%	\else\ifnum#1=8217{\textquoteright}%
+\newcommand{\unichar}[1]{%
+	\ifnum#1=8211{--}%
+	\else\ifnum#1=8212{---}%
+	\else\ifnum#1=8216{`}%
+	\else\ifnum#1=8217{'}%
+	\else\ifnum#1=8218{\glq}%
+	\else\ifnum#1=8220{``}%
+	\else\ifnum#1=8221{''}%
+	\else\ifnum#1=8222{\glqq}%
+	\else\&\##1;\fi%
+	\fi\fi\fi\fi\fi%
+	\fi\fi%
+}
+]]></xsl:text>
+			</xsl:if>
+			<xsl:text>\def\@docbooktolatexunicode#1;{\endgroup\edef\@dbtemp{#1}\unichar{\@dbtemp}}&#10;</xsl:text>
+		</xsl:if>
+		<xsl:if test="$latex.inputenc!=''">
+			<xsl:text>\usepackage[</xsl:text>
+			<xsl:value-of select="$latex.inputenc"/>
+			<xsl:text>]{inputenc}&#10;</xsl:text>
+		</xsl:if>
+		<xsl:if test="$latex.fontenc!=''">
+			<xsl:text>\usepackage[</xsl:text>
+			<xsl:value-of select="$latex.fontenc"/>
+			<xsl:text>]{fontenc}&#10;</xsl:text>
+		</xsl:if>
+		<!-- make proper headers for unnumbered chapter-level components -->
+		<!-- TODO make proper headers for unnumbered section-level components -->
+		<xsl:text><![CDATA[
+\ifx\dblatex@chaptersmark\@undefined\def\dblatex@chaptersmark#1{\markboth{\MakeUppercase{#1}}{}}\fi
+\let\save@makeschapterhead\@makeschapterhead
+\def\dblatex@makeschapterhead#1{\vspace*{-80pt}\save@makeschapterhead{#1}}
+\def\@makeschapterhead#1{\dblatex@makeschapterhead{#1}\dblatex@chaptersmark{#1}}
+]]></xsl:text>
+		<xsl:call-template name="latex.preamble.essential.biblio"/>
+		<xsl:call-template name="latex.preamble.essential.callout"/>
+		<xsl:call-template name="latex.preamble.essential.citation"/>
+		<xsl:call-template name="latex.preamble.essential.footnote"/>
+		<xsl:call-template name="latex.preamble.essential.glossary"/>
+		<xsl:call-template name="latex.preamble.essential.index"/>
+		<xsl:text><![CDATA[
+\def\docbooktolatexgobble{\expandafter\@gobble}
+% Prevent multiple openings of the same aux file
+% (happens when backref is used with multiple bibliography environments)
+\ifx\AfterBeginDocument\undefined\let\AfterBeginDocument\AtBeginDocument\fi
+\AfterBeginDocument{
+   \let\latex@@starttoc\@starttoc
+   \def\@starttoc#1{%
+      \@ifundefined{docbooktolatex@aux#1}{%
+         \global\@namedef{docbooktolatex@aux#1}{}%
+         \latex@@starttoc{#1}%
+      }{}
+   }
+}
+% --------------------------------------------
+% Hacks for honouring row/entry/@align
+% (\hspace not effective when in paragraph mode)
+% Naming convention for these macros is:
+% 'docbooktolatex' 'align' {alignment-type} {position-within-entry}
+% where r = right, l = left, c = centre
+\newcommand{\docbooktolatex@align}[2]{\protect\ifvmode#1\else\ifx\LT@@tabarray\@undefined#2\else#1\fi\fi}
+\newcommand{\docbooktolatexalignll}{\docbooktolatex@align{\raggedright}{}}
+\newcommand{\docbooktolatexalignlr}{\docbooktolatex@align{}{\hspace*\fill}}
+\newcommand{\docbooktolatexaligncl}{\docbooktolatex@align{\centering}{\hfill}}
+\newcommand{\docbooktolatexaligncr}{\docbooktolatex@align{}{\hspace*\fill}}
+\newcommand{\docbooktolatexalignrl}{\protect\ifvmode\raggedleft\else\hfill\fi}
+\newcommand{\docbooktolatexalignrr}{}
+\ifx\captionswapskip\@undefined\newcommand{\captionswapskip}{}\fi
+]]></xsl:text>
+		<xsl:text>\makeatother&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template>
+		<refpurpose> Preamble for certain floats </refpurpose>
+	</doc:template>
+	<xsl:template name="latex.float.preamble">
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>% Commands to manage/style/create floats      &#10;</xsl:text>
+		<xsl:text>% figures, tables, algorithms, examples, eqn  &#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text> \floatstyle{ruled}&#10;</xsl:text>
+		<xsl:text> \restylefloat{figure}&#10;</xsl:text>
+		<xsl:text> \floatstyle{ruled}&#10;</xsl:text>
+		<xsl:text> \restylefloat{table}&#10;</xsl:text>
+		<xsl:text> \floatstyle{ruled}&#10;</xsl:text>
+		<xsl:text> \newfloat{program}{ht}{lop}[section]&#10;</xsl:text>
+		<xsl:text> \floatstyle{ruled}&#10;</xsl:text>
+		<xsl:text> \newfloat{example}{ht}{loe}[section]&#10;</xsl:text>
+		<xsl:text> \floatname{example}{</xsl:text>
+		<xsl:call-template name="gentext.element.name">
+			<xsl:with-param name="element.name">example</xsl:with-param>
+		</xsl:call-template>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:text> \floatstyle{ruled}&#10;</xsl:text>
+		<xsl:text> \newfloat{dbequation}{ht}{loe}[section]&#10;</xsl:text>
+		<xsl:text> \makeatletter\def\toclevel@dbequation{0}\makeatother&#10;</xsl:text>
+		<xsl:text> \floatname{dbequation}{</xsl:text>
+		<xsl:call-template name="gentext.element.name">
+			<xsl:with-param name="element.name">equation</xsl:with-param>
+		</xsl:call-template>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:text> \floatstyle{boxed}&#10;</xsl:text>
+		<xsl:text> \newfloat{algorithm}{ht}{loa}[section]&#10;</xsl:text>
+		<xsl:text> \floatname{algorithm}{Algorithm}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:param name="latex.pdf.preamble" xmlns="">
+		<doc:description>
+			<screen>
+				\usepackage{ifthen}
+				% --------------------------------------------
+				% Check for PDFLaTeX/LaTeX 
+				% --------------------------------------------
+				\newif\ifpdf
+				\ifx\pdfoutput\undefined
+				\pdffalse % we are not running PDFLaTeX
+				\else
+				\pdfoutput=1 % we are running PDFLaTeX
+				\pdftrue
+				\fi
+				% --------------------------------------------
+				% Load graphicx package with pdf if needed 
+				% --------------------------------------------
+				\ifpdf
+				\usepackage[pdftex]{graphicx}
+				\pdfcompresslevel=9
+				\else
+				\usepackage{graphicx}
+				\fi
+			</screen>
+		</doc:description>
+	</doc:param>
+	<xsl:param name="latex.pdf.preamble">
+		<xsl:text>\usepackage{ifthen}&#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>% Check for PDFLaTeX/LaTeX &#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>\newif\ifpdf&#10;</xsl:text>
+		<xsl:text>\ifx\pdfoutput\undefined&#10;</xsl:text>
+		<xsl:text>\pdffalse % we are not running PDFLaTeX&#10;</xsl:text>
+		<xsl:text>\else&#10;</xsl:text>
+		<xsl:text>\pdfoutput=1 % we are running PDFLaTeX&#10;</xsl:text>
+		<xsl:text>\pdftrue&#10;</xsl:text>
+		<xsl:text>\fi&#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>% Load graphicx package with pdf if needed &#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>\ifpdf&#10;</xsl:text>
+		<xsl:text>\usepackage[pdftex]{graphicx}&#10;</xsl:text>
+		<xsl:text>\pdfcompresslevel=9&#10;</xsl:text>
+		<xsl:text>\else&#10;</xsl:text>
+		<xsl:text>\usepackage{graphicx}&#10;</xsl:text>
+		<xsl:text>\fi&#10;</xsl:text>
+	</xsl:param>
+
+	<doc:template name="latex.hyperref.preamble" xmlns="">
+		<refpurpose> Manage the part of the preamble that handles the hyperref package.</refpurpose>
+		<doc:description>
+			<para> This template outputs the LaTeX code <literal>\usepackage[...]{hyperref}</literal>
+			in order to use hyperlinks, backrefs and other goodies. If PDF support is activated, 
+			outputs laTeX code to detect whether the document is being compiled with 
+			<filename>pdflatex</filename> or <filename>latex</filename> to supply the
+			right parameters (pdftex, dvips, etc).
+			<doc:todo> The package options should be optained
+			from XSL variables.</doc:todo>
+			</para>
+			<para>Default Value with PDF support:
+			<screen>
+				% --------------------------------------------
+				% Load hyperref package with pdf if needed 
+				% --------------------------------------------
+				\ifpdf
+				\usepackage[pdftex,bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, linktocpage]{hyperref}
+				\else
+				\usepackage[bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, linktocpage]{hyperref}
+				\fi
+				% --------------------------------------------
+			</screen>
+			</para>
+			<para>Default Value without PDF support:
+			<screen>
+				% --------------------------------------------
+				% Load hyperref package 
+				% --------------------------------------------
+				\usepackage[bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, linktocpage]{hyperref}
+			</screen>
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.pdf.support"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.hyperref.param.common"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.hyperref.param.pdftex"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.hyperref.param.dvips"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+	</doc:template>
+	<xsl:template name="latex.hyperref.preamble">
+		<xsl:choose>
+		<xsl:when test="$latex.pdf.support=1">
+			<xsl:text>% --------------------------------------------&#10;</xsl:text>
+			<xsl:text>% Load hyperref package with pdf if needed &#10;</xsl:text>
+			<xsl:text>% --------------------------------------------&#10;</xsl:text>
+			<xsl:text>\ifpdf&#10;</xsl:text>
+			<xsl:text>\usepackage[pdftex,</xsl:text>
+			<xsl:value-of select="$latex.hyperref.param.common" />
+			<xsl:text>,</xsl:text>
+			<xsl:value-of select="$latex.hyperref.param.pdftex" />
+			<xsl:text>]{hyperref}&#10;</xsl:text>
+			<xsl:text>\else&#10;</xsl:text>
+			<xsl:text>\usepackage[</xsl:text>
+			<xsl:value-of select="$latex.hyperref.param.common" />
+			<xsl:text>,</xsl:text>
+			<xsl:value-of select="$latex.hyperref.param.dvips" />
+			<xsl:text>]{hyperref}&#10;</xsl:text>
+			<!--
+			<xsl:text>\makeatletter\def\pdfmark@[#1]#2{}\makeatother&#10;</xsl:text>
+			-->
+			<xsl:text>\fi&#10;</xsl:text>
+			<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:text>% --------------------------------------------&#10;</xsl:text>
+			<xsl:text>% Load hyperref package &#10;</xsl:text>
+			<xsl:text>% --------------------------------------------&#10;</xsl:text>
+			<xsl:text>\usepackage[</xsl:text>
+			<xsl:value-of select="$latex.hyperref.param.common" />
+			<xsl:text>,</xsl:text>
+			<xsl:value-of select="$latex.hyperref.param.dvips" />
+			<xsl:text>]{hyperref}&#10;</xsl:text>
+			<!--
+			<xsl:text>\makeatletter\def\pdfmark@[#1]#2{}\makeatother&#10;</xsl:text>
+			-->
+		</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:param xmlns="">
+		<refpurpose> &LaTeX; mathematics support  </refpurpose>
+	</doc:param>
+	<xsl:param name="latex.math.preamble">
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>% Math support                                &#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>\usepackage{amsmath,amsthm, amsfonts, amssymb, amsxtra,amsopn}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{thm}{Theorem}[section]&#10;</xsl:text>
+		<xsl:text>%\newtheorem{cor}[section]{Corollary}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{lem}[section]{Lemma}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{defn}[section]{Definition}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{prop}[section]{Proposition}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{ax}{Axiom}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{theorem}[section]{Theorem}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{corollary}{Corollary}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{lemma}{Lemma}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{proposition}{Proposition}&#10;</xsl:text>
+		<xsl:text>%\theoremstyle{definition}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{definition}{Definition}&#10;</xsl:text>
+		<xsl:text>%\theoremstyle{remark}&#10;</xsl:text>
+		<xsl:text>%\newtheorem{rem}{Remark}&#10;</xsl:text>
+		<xsl:text>%\newtheorem*{notation}{Notation}&#10;</xsl:text>
+		<xsl:text>%\newcommand{\ntt}{\normalfont\ttfamily}&#10;</xsl:text>
+		<xsl:text>%\newcommand{\thmref}[1]{Theorem~\ref{#1}}&#10;</xsl:text>
+		<xsl:text>%\newcommand{\secref}[1]{\S\ref{#1}}&#10;</xsl:text>
+		<xsl:text>%\newcommand{\lemref}[1]{Lemma~\ref{#1}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\bysame}{\mbox{\rule{3em}{.4pt}}\,}&#10;</xsl:text>
+		<xsl:text> \newcommand{\A}{\mathcal{A}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\B}{\mathcal{B}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\XcY}{{(X,Y)}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\SX}{{S_X}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\SY}{{S_Y}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\SXY}{{S_{X,Y}}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\SXgYy}{{S_{X|Y}(y)}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\Cw}[1]{{\hat C_#1(X|Y)}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\G}{{G(X|Y)}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\PY}{{P_{\mathcal{Y}}}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\X}{\mathcal{X}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\wt}{\widetilde}&#10;</xsl:text>
+		<xsl:text> \newcommand{\wh}{\widehat}&#10;</xsl:text>
+		<xsl:text> % --------------------------------------------&#10;</xsl:text>
+		<xsl:text> %\DeclareMathOperator{\per}{per}&#10;</xsl:text>
+		<xsl:text> \DeclareMathOperator{\cov}{cov}&#10;</xsl:text>
+		<xsl:text> \DeclareMathOperator{\non}{non}&#10;</xsl:text>
+		<xsl:text> \DeclareMathOperator{\cf}{cf}&#10;</xsl:text>
+		<xsl:text> \DeclareMathOperator{\add}{add}&#10;</xsl:text>
+		<xsl:text> \DeclareMathOperator{\Cham}{Cham}&#10;</xsl:text>
+		<xsl:text> \DeclareMathOperator{\IM}{Im}&#10;</xsl:text>
+		<xsl:text> \DeclareMathOperator{\esssup}{ess\,sup}&#10;</xsl:text>
+		<xsl:text> \DeclareMathOperator{\meas}{meas}&#10;</xsl:text>
+		<xsl:text> \DeclareMathOperator{\seg}{seg}&#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+	</xsl:param>
+
+	<doc:template xmlns="">
+		<refpurpose> Declared graphic extensions </refpurpose>
+		<doc:description>
+		<para>
+		This template checks whether the user has overridden <command>grafic.default.extension</command>
+		Otherwise, declares .pdf, .png, .jpg if using pdflatex and .eps if using latex.
+		</para>
+		<programlisting><![CDATA[
+<xsl:template name="latex.graphicext">
+<xsl:choose>
+<xsl:when test="$graphic.default.extension !=''">
+	<xsl:text>\DeclareGraphicsExtensions{</xsl:text>
+	<xsl:if test="not(contains($graphic.default.extension,'.'))">
+		<xsl:text>.</xsl:text>
+	</xsl:if>
+	<xsl:value-of select="$graphic.default.extension"/>
+	<xsl:text>}&#10;</xsl:text>
+</xsl:when>
+<xsl:otherwise>
+	<xsl:choose>
+	<xsl:when test="$latex.pdf.support=1">
+		<xsl:text>\ifpdf&#10;</xsl:text>
+		<xsl:text>\DeclareGraphicsExtensions{.pdf,.png,.jpg}&#10;</xsl:text>
+		<xsl:text>\else&#10;</xsl:text>
+		<xsl:text>\DeclareGraphicsExtensions{.eps}&#10;</xsl:text>
+		<xsl:text>\fi&#10;</xsl:text>
+	</xsl:when>
+	<xsl:otherwise>
+		<xsl:text>\DeclareGraphicsExtensions{.eps}&#10;</xsl:text>
+	</xsl:otherwise>
+	</xsl:choose>
+</xsl:otherwise>
+</xsl:choose>
+</xsl:template>
+]]></programlisting>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.graphic.default.extension"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.pdf.support"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+	</doc:template>
+	<xsl:template name="latex.graphicext">
+		<xsl:choose>
+			<xsl:when test="$graphic.default.extension !=''">
+				<xsl:text>\DeclareGraphicsExtensions{</xsl:text>
+				<xsl:if test="not(contains($graphic.default.extension,'.'))">
+					<xsl:text>.</xsl:text>
+				</xsl:if>
+				<xsl:value-of select="$graphic.default.extension"/>
+				<xsl:text>}&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:choose>
+				<xsl:when test="$latex.pdf.support=1">
+					<xsl:text>\ifpdf&#10;</xsl:text>
+					<xsl:text>\DeclareGraphicsExtensions{.pdf,.png,.jpg}&#10;</xsl:text>
+					<xsl:text>\else&#10;</xsl:text>
+					<xsl:text>\DeclareGraphicsExtensions{.eps}&#10;</xsl:text>
+					<xsl:text>\fi&#10;</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>\DeclareGraphicsExtensions{.eps}&#10;</xsl:text>
+				</xsl:otherwise>
+				</xsl:choose>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/procedure.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/procedure.mod.xsl
new file mode 100644
index 00000000000..f7c780bd6dc
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/procedure.mod.xsl
@@ -0,0 +1,421 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: procedure.mod.xsl,v 1.12 2004/01/13 04:35:43 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="procedure" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: procedure.mod.xsl,v 1.12 2004/01/13 04:35:43 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.10">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Procedures <filename>procedure.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>procedure</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Format a titled, enumerated list of steps.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.formal.title.placement"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>mode</term>
+					<listitem><simpara>
+						Although the <sgmltag class="attribute">mode</sgmltag>
+						parameter is normally empty, this template recognises a
+						special value of <quote>custom</quote>. This influences
+						the type of environment and the method of labelling
+						<doc:db basename="step">steps</doc:db>.
+					</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>environment</term>
+					<listitem><simpara>
+						This determines the &LaTeX; environment that will be
+						used for each <doc:db>step</doc:db>'s <function
+						condition="latex">item</function>. When the
+						<literal>mode</literal> is <quote>custom</quote>, this
+						parameter defaults to <quote>description</quote>.
+						Otherwise, the default is <quote>enumerate</quote>.
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+			
+			By default, the &LaTeX; <function
+			condition="env">enumerate</function> environment is used and any
+			<doc:db>step</doc:db>'s <doc:db>title</doc:db> will be typeset
+			after its automatic step number. However, when the
+			<literal>mode</literal> variable is equal to <quote>custom</quote>,
+			the <function condition="env">description</function> environment
+			will be used and step titles will be typeset
+			<emphasis>instead</emphasis> of step numbers.
+			
+			</para>
+			<para>
+
+			Although the procedure is a formal, titled block, is is not typeset
+			using <function condition="latex">subsection</function>.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_chemistry;
+				&test_procedure;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.procedure/title"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="procedure" name="procedure">
+		<xsl:param name="mode" select="''"/>
+		<xsl:param name="environment">
+			<xsl:choose>
+				<xsl:when test="$mode='custom'">
+					<xsl:text>description</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>enumerate</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:variable name="placement">
+			<xsl:call-template name="generate.formal.title.placement">
+				<xsl:with-param name="object" select="local-name(.)" />
+			</xsl:call-template>
+		</xsl:variable>
+		<xsl:variable name="preamble" select="node()[not(self::blockinfo or self::title or self::subtitle or self::titleabbrev or self::step)]"/>
+		<xsl:choose>
+			<xsl:when test="$placement='before' or $placement=''">
+				<xsl:apply-templates select="title" mode="procedure.title"/>
+				<xsl:apply-templates select="$preamble"/>
+				<xsl:text>\begin{</xsl:text>
+				<xsl:value-of select="$environment"/>
+				<xsl:text>}&#10;</xsl:text>
+				<xsl:apply-templates select="step">
+					<xsl:with-param name="mode" select="$mode"/>
+				</xsl:apply-templates>
+				<xsl:text>\end{</xsl:text>
+				<xsl:value-of select="$environment"/>
+				<xsl:text>}&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:apply-templates select="$preamble"/>
+				<xsl:text>\begin{</xsl:text>
+				<xsl:value-of select="$environment"/>
+				<xsl:text>}&#10;</xsl:text>
+				<xsl:apply-templates select="step">
+					<xsl:with-param name="mode" select="$mode"/>
+				</xsl:apply-templates>
+				<xsl:text>\end{</xsl:text>
+				<xsl:value-of select="$environment"/>
+				<xsl:text>}&#10;</xsl:text>
+				<xsl:apply-templates select="title" mode="procedure.title"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process a <doc:db>procedure</doc:db>'s <doc:db>title</doc:db> </refpurpose>
+		<doc:description>
+			<para>
+			
+			Format a special bridgehead.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.procedure.title.style"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.apply.title.templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+			
+			The title is typeset as a paragraph.
+			
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_procedure;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="procedure/title">
+		<xsl:text>&#10;&#10;{</xsl:text>
+		<xsl:value-of select="$latex.procedure.title.style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:choose>
+			<xsl:when test="$latex.apply.title.templates=1">
+				<xsl:apply-templates/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="."/>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="step" xmlns="">
+		<refpurpose>Process <doc:db>step</doc:db> elements </refpurpose>
+		<doc:description>
+			<para>
+			
+			Format steps and substeps as part of a procedure.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.step.title.style"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>mode</term>
+					<listitem><simpara>
+
+						The <quote>mode</quote> from the parent
+						<doc:db>procedure</doc:db>. This template
+						needs to know when the <quote>custom</quote>
+						mode is in use, because it needs to pass the
+						step's title as an optional argument to the
+						&LaTeX; <function condition="latex">item</function>
+						command (see <xref linkend="template.procedure"/>).
+						The mode is normally received from the enclosing
+						<doc:db>procedure</doc:db> or <doc:db>substeps</doc:db>
+						template.
+
+					</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>title</term>
+					<listitem><simpara>
+						The string (typically empty).
+						See <xref linkend="template.generate.step.title"/>
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+			
+			Each step is typeset using the &LaTeX; <function condition="latex">item</function> command.
+			
+			</para>
+			<para>
+				If there is no <doc:db>title</doc:db> element, the
+				step will be numbered automatically by &LaTeX;.
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_chemistry;
+				&test_procedure;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.generate.step.title"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="step" name="step">
+		<xsl:param name="mode" select="''"/>
+		<xsl:param name="title">
+			<xsl:call-template name="generate.step.title">
+				<xsl:with-param name="mode" select="$mode"/>
+			</xsl:call-template>
+		</xsl:param>
+		<xsl:choose>
+			<xsl:when test="$title!='' and $mode='custom'">
+				<xsl:text>&#10;\item[{</xsl:text>
+				<xsl:value-of select="$latex.step.title.style"/> <!-- by default \sc -->
+				<xsl:text>{</xsl:text>
+				<xsl:value-of select="$title"/>
+				<xsl:text>}}]&#10;{</xsl:text>
+			</xsl:when>
+			<xsl:when test="$title!=''">
+				<xsl:text>&#10;\item{{</xsl:text>
+				<xsl:value-of select="$latex.step.title.style"/> <!-- by default \sc -->
+				<xsl:text>{</xsl:text>
+				<xsl:value-of select="$title"/>
+				<xsl:text>}}&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>&#10;\item{</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		 <xsl:apply-templates select="node()[not(self::title)]"/>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Generate a <doc:db>step</doc:db>'s title </refpurpose>
+		<doc:description>
+			<para>
+			
+			By default, simply applies templates for <doc:db>title</doc:db>
+			elements.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>mode</term>
+					<listitem><simpara>
+
+						See <xref linkend="template.procedure"/>. When the mode
+						is <quote>custom</quote>, this template will use the
+						XSL <literal>number</literal> element to format a title
+						such as "1.", "2.", etc. Otherwise, any
+						<doc:db>title</doc:db> elements will be used.
+
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+
+				If this template generates no content, the
+				<doc:db>step</doc:db> will either be numbered automatically by
+				&LaTeX; or left unlabelled (depending on the
+				<quote>mode</quote>).
+
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template name="generate.step.title">
+		<xsl:param name="mode"/>
+		<xsl:choose>
+			<xsl:when test="title">
+				<xsl:apply-templates select="title"/>
+			</xsl:when>
+			<xsl:when test="$mode='custom'">
+				<xsl:number format="1."/>
+			</xsl:when>
+			<!-- otherwise, empty -->
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>substep</doc:db> elements </refpurpose>
+		<doc:description>
+			<para>
+			
+			Format substeps as part of a step.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>mode</term>
+					<listitem><simpara>
+						See <xref linkend="template.procedure"/>.
+					</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>environment</term>
+					<listitem><simpara>
+						See <xref linkend="template.procedure"/>.
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:notes>
+			<para>
+			
+			Substeps are typeset by nesting a &LaTeX;
+			<function condition="env">enumerate</function> environment.
+			
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_procedure;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="substeps">
+		<xsl:param name="mode" select="''"/>
+		<xsl:param name="environment">
+			<xsl:choose>
+				<xsl:when test="$mode='custom'">
+					<xsl:text>description</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>enumerate</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:text>\begin{</xsl:text>
+		<xsl:value-of select="$environment"/>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:apply-templates select="step">
+			<xsl:with-param name="mode" select="$mode"/>
+		</xsl:apply-templates>
+		<xsl:text>\end{</xsl:text>
+		<xsl:value-of select="$environment"/>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/qandaset.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/qandaset.mod.xsl
new file mode 100644
index 00000000000..3cf6fb9de4c
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/qandaset.mod.xsl
@@ -0,0 +1,415 @@
+<?xml version="1.0"?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: qandaset.mod.xsl,v 1.13 2004/01/04 13:22:27 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
+|   PURPOSE:
+|   Portions (c) Norman Walsh, official DocBook XSL stylesheets.
+|                See docbook.sf.net
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" 
+	exclude-result-prefixes="doc" version="1.0">
+
+	<doc:reference id="qandaset" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: qandaset.mod.xsl,v 1.13 2004/01/04 13:22:27 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.11">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>QandaSet <filename>qandaset.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+				Portions (c) Norman Walsh, official DocBook XSL stylesheets. See docbook.sf.net
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>qandadiv</doc:db> elements</refpurpose>
+		<doc:description>
+			<para><doc:todo>Undocumented.</doc:todo></para>
+		</doc:description>
+	</doc:template>
+<xsl:template match="qandaset">
+		<!-- get all children that are not the following -->
+		<xsl:variable name="preamble" select="*[name(.) != 'title'
+									  and name(.) != 'titleabbrev'
+									  and name(.) != 'blockinfo'
+									  and name(.) != 'qandadiv'
+									  and name(.) != 'qandaentry']"/>
+		<xsl:variable name="label-width"/>
+		<xsl:variable name="table-summary"/>
+		<xsl:variable name="cellpadding"/>
+		<xsl:variable name="cellspacing"/>
+		<xsl:variable name="toc"/>
+		<xsl:variable name="toc.params"/>
+  		<xsl:variable name="qalevel">
+    		<xsl:call-template name="qanda.section.level"/>
+  		</xsl:variable>
+		<xsl:text>% -------------------------------------------------------------&#10;</xsl:text>
+		<xsl:text>% QandASet                                                     &#10;</xsl:text>
+		<xsl:text>% -------------------------------------------------------------&#10;</xsl:text>
+		<xsl:choose>
+      		<xsl:when test="ancestor::sect2">
+	    		<xsl:text>\subsubsection*{</xsl:text>
+			</xsl:when>
+      		<xsl:when test="ancestor::sect1">
+	    		<xsl:text>\subsection*{</xsl:text>
+			</xsl:when>
+      		<xsl:when test="ancestor::article | ancestor::appendix">
+	    		<xsl:text>\section*{</xsl:text>
+			</xsl:when>
+      		<xsl:when test="ancestor::book">
+	    		<xsl:text>\chapter*{</xsl:text>
+			</xsl:when>
+		</xsl:choose>
+		<xsl:choose>
+			<xsl:when test="title">
+				<xsl:apply-templates select="title"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>F.A.Q.</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}&#10;</xsl:text>
+	    <xsl:call-template name="label.id"/>
+		<xsl:text>&#10;</xsl:text>
+
+		<!-- process toc -->
+		<xsl:if test="contains($toc.params, 'toc') and $toc != '0'">
+			<xsl:call-template name="process.qanda.toc"/>
+		</xsl:if>
+		<!-- process preamble -->
+		<xsl:apply-templates select="$preamble"/>
+		<!-- process divs and entries -->
+		<xsl:apply-templates select="qandaentry|qandadiv"/>
+</xsl:template>
+
+	<doc:template basename="qandaentry" xmlns="">
+		<refpurpose>Process <doc:db>qandadiv</doc:db> elements</refpurpose>
+		<doc:description>
+			<para><doc:todo>Undocumented.</doc:todo></para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="qandaset/qandaentry">
+		<xsl:text>\vspace{1em}&#10;</xsl:text>
+		<xsl:text>\noindent{}</xsl:text>
+		<xsl:value-of select="position()"/>
+		<xsl:text>.~</xsl:text>
+		<xsl:apply-templates select="question"/>
+		<xsl:text>\newline&#10;</xsl:text>
+		<xsl:apply-templates select="answer"/>
+		<xsl:text>\vspace{1em}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>qandadiv</doc:db> elements</refpurpose>
+		<doc:description>
+			<para><doc:todo>Undocumented.</doc:todo></para>
+		</doc:description>
+	</doc:template>
+<xsl:template match="qandadiv">
+	<!-- get the preamble -->
+  <xsl:variable name="preamble" select="*[name(.) != 'title'
+                                          and name(.) != 'titleabbrev'
+                                          and name(.) != 'qandadiv'
+                                          and name(.) != 'qandaentry']"/>
+  <xsl:variable name="qalevel">
+    <xsl:call-template name="qandadiv.section.level"/>
+  </xsl:variable>
+	<!-- process the title if it exists -->
+		<xsl:text>% -----------&#10;</xsl:text>
+		<xsl:text>% QandADiv   &#10;</xsl:text>
+		<xsl:text>% -----------&#10;</xsl:text>
+		<xsl:text>\noindent\begin{minipage}{\linewidth}&#10;</xsl:text>
+		<xsl:text>\vspace{0.25em}\hrule\vspace{0.25em}&#10;</xsl:text>
+		<xsl:choose>
+      		<xsl:when test="ancestor::sect2">
+	    		<xsl:text>\paragraph*{</xsl:text>
+			</xsl:when>
+      		<xsl:when test="ancestor::sect1">
+	    		<xsl:text>\subsubsection*{</xsl:text>
+			</xsl:when>
+      		<xsl:when test="ancestor::article | ancestor::appendix">
+	    		<xsl:text>\subsection*{</xsl:text>
+			</xsl:when>
+      		<xsl:when test="ancestor::book">
+	    		<xsl:text>\section*{</xsl:text>
+			</xsl:when>
+		</xsl:choose>
+		<xsl:choose>
+			<xsl:when test="title">
+				<xsl:apply-templates select="title"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>F.A.Q. Part</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:text>}</xsl:text>
+		<xsl:call-template name="label.id"/>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>\hrule\vspace{0.25em}&#10;</xsl:text>
+		<xsl:text>\end{minipage}&#10;</xsl:text>
+
+<!--
+	<xsl:text>\begin{toc}&#10;</xsl:text>
+	<xsl:for-each select="qandaentry">
+		<xsl:text>\tocref{</xsl:text>
+		<xsl:value-of select="@id"/>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:for-each>
+	<xsl:text>\end{toc}&#10;</xsl:text>
+-->
+
+<!-- pseudo table of contents -->
+	<!--
+	<xsl:choose>
+		<xsl:when test="title">
+			<xsl:text>\caption{</xsl:text>
+			<xsl:apply-templates select="title"/>
+			<xsl:text>}&#10;</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:text>\caption{</xsl:text>
+			<xsl:text>F.A.Q. Part</xsl:text>
+			<xsl:text>}&#10;</xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+	-->
+	<xsl:for-each select="qandaentry">
+	<xsl:text>\noindent{}</xsl:text>
+	<xsl:value-of select="position()"/>
+	<xsl:text>.~</xsl:text>
+	<xsl:apply-templates select="question"/>
+	<xsl:if test="position()!=last()"><xsl:text>\newline&#10;</xsl:text></xsl:if>
+	</xsl:for-each>
+	<xsl:text>\vspace{0.25em}\hrule&#10;</xsl:text>
+
+	<xsl:for-each select="qandaentry">
+	<xsl:text>\vspace{1em}&#10;</xsl:text>
+	<xsl:text>\noindent{}</xsl:text>
+	<xsl:value-of select="position()"/>
+	<xsl:text>.~</xsl:text>
+	<xsl:apply-templates select="question"/>
+	<xsl:text>\newline&#10;</xsl:text>
+	<xsl:apply-templates select="answer"/>
+	</xsl:for-each>
+	<xsl:text>\vspace{1em}&#10;</xsl:text>
+</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>question</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates as a italicised block, preceded by a bold
+				letter <quote>Q</quote>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>defaultlabel attributes are not honoured.</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="question">
+		<!-- get the default label
+		<xsl:variable name="deflabel">
+			<xsl:choose>
+				<xsl:when test="ancestor-or-self::*[@defaultlabel]">
+					<xsl:value-of select="(ancestor-or-self::*[@defaultlabel])[last()]/@defaultlabel"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="latex.qanda.defaultlabel"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		-->
+		<!-- process the question itself 
+		<xsl:apply-templates select="." mode="label.markup"/>
+		<xsl:choose>
+			<xsl:when test="$deflabel = 'none' and not(label)">
+				<xsl:apply-templates select="*[name(.) != 'label']"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:apply-templates select="*[name(.) != 'label']"/>
+			</xsl:otherwise>
+		</xsl:choose>
+		-->
+		<xsl:text>\textbf{Q:}~\textit{</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>answer</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates as a block, preceded by a bold
+				letter <quote>A</quote>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="answer">
+		<xsl:text>\noindent\textbf{A:}~</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>&#10;&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>label</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="label">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template name="process.qanda.toc">
+		<xsl:apply-templates select="qandadiv" mode="qandatoc.mode"/>
+		<xsl:apply-templates select="qandaentry" mode="qandatoc.mode"/>
+	</xsl:template>
+
+	<doc:template basename="qandadiv" xmlns="">
+		<refpurpose>Process <doc:db>qandadiv</doc:db> elements</refpurpose>
+		<doc:description>
+			<para><doc:todo>Undocumented.</doc:todo></para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="qandadiv" mode="qandatoc.mode">
+		<xsl:apply-templates select="title" mode="qandatoc.mode"/>
+		<xsl:call-template name="process.qanda.toc"/>
+	</xsl:template>
+
+	<doc:template basename="title" xmlns="">
+		<refpurpose>Process a <doc:db>qandadiv</doc:db>'s <doc:db>title</doc:db> elements</refpurpose>
+		<doc:description>
+			<para><doc:todo>Undocumented.</doc:todo></para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="qandadiv/title" mode="qandatoc.mode">
+		<xsl:variable name="qalevel">
+			<xsl:call-template name="qandadiv.section.level"/>
+		</xsl:variable>
+		<xsl:call-template name="label.id">
+			<xsl:with-param name="object" select="parent::*"/>
+		</xsl:call-template>
+		<xsl:apply-templates select="parent::qandadiv" mode="label.markup"/>
+		<xsl:value-of select="$autotoc.label.separator"/>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="" basename="qandaentry">
+		<refpurpose>Process <doc:db>qandaentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para><doc:todo>Undocumented.</doc:todo></para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="qandaentry" mode="qandatoc.mode">
+		<xsl:apply-templates mode="qandatoc.mode"/>
+	</xsl:template>
+
+	<doc:template basename="question" xmlns="">
+		<refpurpose>Process <doc:db>question</doc:db> elements</refpurpose>
+		<doc:description>
+			<para><doc:todo>Undocumented.</doc:todo></para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="question" mode="qandatoc.mode">
+		<xsl:variable name="firstch" select="(*[name(.)!='label'])[1]"/>
+		<xsl:apply-templates select="." mode="label.markup"/>
+		<xsl:text> </xsl:text>
+	</xsl:template>
+
+	<doc:template xmlns="" basename="answer">
+		<refpurpose>Process <doc:db>answer</doc:db> elements</refpurpose>
+		<doc:description>
+			<para><doc:todo>Undocumented.</doc:todo></para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="answer" mode="qandatoc.mode"/>
+
+	<doc:template xmlns="" basename="revhistory">
+		<refpurpose>Process <doc:db>revhistory</doc:db> elements</refpurpose>
+		<doc:description>
+			<para><doc:todo>Undocumented.</doc:todo></para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="revhistory" mode="qandatoc.mode"/>
+
+<xsl:template name="question.answer.label">
+	<!-- variable: deflabel -->
+  <xsl:variable name="deflabel">
+  	<!-- chck whether someone has a defaultlabel attribute -->
+    <xsl:choose>
+		<xsl:when test="ancestor-or-self::*[@defaultlabel]">
+        	<xsl:value-of select="(ancestor-or-self::*[@defaultlabel])[last()]/@defaultlabel"/>
+	      </xsl:when>
+      <xsl:otherwise>
+        <xsl:value-of select="latex.qanda.defaultlabel"/>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:variable name="label" select="@label"/>
+  <xsl:choose>
+    <xsl:when test="$deflabel = 'qanda'">
+      <xsl:call-template name="gentext">
+        <xsl:with-param name="key">
+          <xsl:choose>
+            <xsl:when test="local-name(.) = 'question'">question</xsl:when>
+            <xsl:when test="local-name(.) = 'answer'">answer</xsl:when>
+            <xsl:when test="local-name(.) = 'qandadiv'">qandadiv</xsl:when>
+            <xsl:otherwise>qandaset</xsl:otherwise>
+          </xsl:choose>
+        </xsl:with-param>
+      </xsl:call-template>
+    </xsl:when>
+    <xsl:when test="$deflabel = 'label'">
+      <xsl:value-of select="$label"/>
+    </xsl:when>
+    <xsl:when test="$deflabel = 'number' and local-name(.) = 'question'">
+      <xsl:apply-templates select="ancestor::qandaset[1]" mode="number"/>
+      <xsl:choose>
+        <xsl:when test="ancestor::qandadiv">
+          <xsl:apply-templates select="ancestor::qandadiv[1]" mode="number"/>
+          <xsl:apply-templates select="ancestor::qandaentry" mode="number"/>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:apply-templates select="ancestor::qandaentry" mode="number"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:otherwise>
+      <!-- nothing -->
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/refentry.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/refentry.mod.xsl
new file mode 100644
index 00000000000..98c68685645
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/refentry.mod.xsl
@@ -0,0 +1,343 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: refentry.mod.xsl,v 1.7 2004/01/14 14:54:32 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="refentry" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: refentry.mod.xsl,v 1.7 2004/01/14 14:54:32 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.5">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>References and Entries <filename>refentry.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>refentry.mod.xsl</filename> contains
+			XSL templates for <doc:db basename="reference">references</doc:db>.</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>reference</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes the mapping templates and applies content templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.content-templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="reference">
+		<xsl:call-template name="map.begin"/>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>refentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes the mapping templates and applies content templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.content-templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="refentry">
+		<xsl:variable name="refmeta" select=".//refmeta"/>
+		<xsl:variable name="refentrytitle" select="$refmeta//refentrytitle"/>
+		<xsl:variable name="refnamediv" select=".//refnamediv"/>
+		<xsl:variable name="refname" select="$refnamediv//refname"/>
+		<xsl:variable name="title">
+			<xsl:choose>
+			<xsl:when test="$refentrytitle">
+				<xsl:apply-templates select="$refentrytitle[1]"/>
+			</xsl:when>
+			<xsl:when test="$refname">
+				<xsl:apply-templates select="$refname[1]"/>
+				<xsl:apply-templates select="$refnamediv//refpurpose"/>
+			</xsl:when>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:call-template name="map.begin">
+			<xsl:with-param name="string" select="$title"/>
+		</xsl:call-template>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end">
+			<xsl:with-param name="string" select="$title"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>refentry</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Suppresses <doc:db basename="refentry">refentries</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="refmeta"/>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>refentrytitle</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Format a reference entry title.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				This template uses <literal>inline.charseq</literal>,
+				though I'm not sure if this should be changed to
+				a single <literal>apply-templates</literal>.
+			</para>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.inline.charseq"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="refentrytitle">
+		<xsl:call-template name="inline.charseq"/>
+	</xsl:template>
+
+	<!--
+	<xsl:template match="refnamediv">
+		<xsl:call-template name="block.object"/>
+	</xsl:template>
+	-->
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>manvolnum</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Format a reference volume number.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.refentry.xref.manvolnum"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+				If <xref linkend="param.refentry.xref.manvolnum"/> is set,
+				this template will apply templates. Otherwise, no output
+				is produced.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="manvolnum">
+		<xsl:if test="$refentry.xref.manvolnum != 0">
+			<xsl:text>(</xsl:text>
+			<xsl:apply-templates/>
+			<xsl:text>)</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>refnamediv</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Format a reference header.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:description>
+			<para>
+				Calls <xref linkend="template.block.object"/>.
+			</para>
+		</doc:description>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.block.object"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="refnamediv">
+		<xsl:call-template name="block.object"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>refname</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a <doc:db>refname</doc:db> as a start-of-section
+				for a <doc:db>refentry</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.refentry.generate.name"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>Will commence a &LaTeX; <function
+			condition="latex">section</function> if necessary.</para>
+			<para>Designed to accommodate multiple <doc:db>refname</doc:db>s in
+			a single <doc:db>refentry</doc:db>.</para>
+			<para>The use of a comma between multiple <doc:db>refname</doc:db>s
+			should probably be localised.</para>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="refname">
+		<xsl:if test="not (preceding-sibling::refname)">
+			<xsl:text>&#10;\section*{</xsl:text>
+			<xsl:if test="$refentry.generate.name != 0">
+			<xsl:call-template name="gentext.element.name"/>
+			</xsl:if>
+			<xsl:text>}&#10;</xsl:text>
+		</xsl:if>
+		<xsl:apply-templates/>
+		<xsl:if test="following-sibling::refname">
+			<xsl:text>, </xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>refpurpose</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a <doc:db>refpurpose</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>Outputs an em dash and then applies templates.</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="refpurpose">
+		<xsl:text> --- </xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>refdescriptor</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a <doc:db>refdescriptor</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>Suppressed.</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="refdescriptor">
+		<!-- todo: finish this -->
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>refclass</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a <doc:db>refclass</doc:db>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>Applies templates. If the role attribute is not empty,
+			it will be output prior to content, separated by a colon.</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="refclass">
+		<xsl:if test="@role!=''">
+			<xsl:value-of select="@role"/>
+			<xsl:text>: </xsl:text>
+		</xsl:if>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>refsynopsisdiv</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Formats a <doc:db>refsynopsisdiv</doc:db> as an unnumbered subsection.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="refsynopsisdiv">
+		<xsl:call-template name="label.id"/>
+		<xsl:text>&#10;\subsection*{Synopsis}&#10;</xsl:text>
+		<xsl:call-template name="content-templates"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>refsect</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Invokes the mapping templates and applies content templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.content-templates"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="refsect1|refsect2|refsect3">
+		<xsl:call-template name="map.begin"/>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/revision.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/revision.mod.xsl
new file mode 100644
index 00000000000..3e9ae23f896
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/revision.mod.xsl
@@ -0,0 +1,247 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: revision.mod.xsl,v 1.7 2004/01/03 09:48:34 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+    <doc:reference id="revision" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: revision.mod.xsl,v 1.7 2004/01/03 09:48:34 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.12">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Revision Management <filename>revision.mod.xsl</filename></title>
+		<partintro>
+			<para>
+
+				This file defines the &DB2LaTeX; XSL templates for
+				<doc:db>revision</doc:db> and its children. The basic mapping
+				is to output a &LaTeX; table and a table row for each revision.
+
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>revhistory</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Format a list of <doc:db basename="revision">revisions</doc:db>
+			as a block.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.output.revhistory"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Uses a &LaTeX; mapping and applies templates.
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_book;
+				&test_ddh;
+				&test_ieeebiblio;
+				&test_mapping;
+				&test_minimal;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="revhistory">
+	<!--
+	<xsl:message>RCAS: Processing Revision History </xsl:message>
+	-->
+		<xsl:if test="$latex.output.revhistory=1">
+			<xsl:call-template name="map.begin"/>
+			<xsl:apply-templates/>
+			<xsl:call-template name="map.end"/>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>revision</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Format a list of <doc:db basename="revision">revisions</doc:db>.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				
+				Each <doc:db>revision</doc:db> corresponds to a &LaTeX; table
+				row containing the revision number, the date, author initials
+				and the description/ remarks of the revision.
+				
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_book;
+				&test_ddh;
+				&test_ieeebiblio;
+				&test_mapping;
+				&test_minimal;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>Gentext</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="revision">
+		<xsl:variable name="revnumber" select=".//revnumber"/>
+		<xsl:variable name="revdate"   select=".//date"/>
+		<xsl:variable name="revauthor" select=".//authorinitials"/>
+		<xsl:variable name="revremark" select=".//revremark|.//revdescription"/>
+		<!-- Row starts here -->
+		<xsl:if test="$revnumber">
+			<xsl:call-template name="gentext.element.name"/>
+			<xsl:text> </xsl:text>
+			<xsl:apply-templates select="$revnumber"/>
+		</xsl:if>
+		<xsl:text> &amp; </xsl:text>
+		<xsl:apply-templates select="$revdate"/>
+		<xsl:text> &amp; </xsl:text>
+		<xsl:choose>
+			<xsl:when test="count($revauthor)=0">
+			<xsl:call-template name="dingbat">
+				<xsl:with-param name="dingbat">nbsp</xsl:with-param>
+			</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+			<xsl:apply-templates select="$revauthor"/>
+			</xsl:otherwise>
+		</xsl:choose>
+		<!-- End Row here -->
+		<xsl:text> \\ \hline&#10;</xsl:text>
+		<!-- Add Remark Row if exists-->
+		<xsl:if test="$revremark"> 
+			<xsl:text>\multicolumn{3}{|l|}{</xsl:text>
+			<xsl:apply-templates select="$revremark"/> 
+			<!-- End Row here -->
+			<xsl:text>} \\ \hline&#10;</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+
+	<doc:template basename="authorinitials" xmlns="">
+		<refpurpose>Process a <doc:db>revision</doc:db>'s <doc:db>authorinitials</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Applies templates and outputs a "comma" between multiple
+				<doc:db>authorinitials</doc:db> elements.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="revision/authorinitials">
+		<xsl:apply-templates/>
+		<xsl:if test="following-sibling::authorinitials">
+			<xsl:text>, </xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>revnumber</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="revnumber">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template basename="date" xmlns="">
+		<refpurpose>Process a <doc:db>revision</doc:db>'s <doc:db>date</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="revision/date">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>revremark</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="revremark">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>revdescription</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="revdescription">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/scape.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/scape.mod.xsl
new file mode 100644
index 00000000000..ef0b6374abb
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/scape.mod.xsl
@@ -0,0 +1,629 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- This file was generated automatically. -->
+<!-- Developers should not commit sundry patches against this file. -->
+<!-- The source file (with documentation!) is in the admin directory. -->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+  <doc:reference xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" id="scape">
+    <referenceinfo>
+      <releaseinfo role="meta">
+        $Id: scape.mod.xsl,v 1.4 2004/01/23 11:36:06 j-devenish Exp $
+      </releaseinfo>
+      <authorgroup>
+        <author>
+          <firstname>James</firstname>
+          <surname>Devenish</surname>
+        </author>
+      </authorgroup>
+      <copyright>
+        <year>2003</year>
+        <year>2004</year>
+        <holder>Ramon Casellas</holder>
+      </copyright>
+    </referenceinfo>
+    <title><productname condition="noindex">LaTeX</productname> Active-character Escaping</title>
+  </doc:reference>
+  <doc:template xmlns:doc="http://nwalsh.com/xsl/documentation/1.0">
+    <refpurpose>General text escaping for <productname condition="noindex">LaTeX</productname> active characters</refpurpose>
+    <doc:description>
+      <para>
+        Certain characters must be escaped so that <productname condition="noindex">LaTeX</productname> will typeset
+        them verbatim rather than attempting to interpret them as commands.
+      </para>
+    </doc:description>
+    <refsection>
+      <title>Mapping Source</title>
+      <programlisting><![CDATA[<template name="scape">
+    
+               <map from="&lt;" to="\textless{}"/>
+    
+               <map from="&gt;" to="\textgreater{}"/>
+    
+               <map from="~" to="\textasciitilde{}"/>
+    
+               <map from="^" to="\textasciicircum{}"/>
+    
+               <map from="&amp;" to="\&amp;"/>
+    
+               <map from="#" to="\#"/>
+    
+               <map from="_" to="\_"/>
+    
+               <map from="$" to="\$"/>
+    
+               <map from="%" to="\%"/>
+    
+               <map from="|" to="\docbooktolatexpipe{}"/>
+    
+               <map from="{" to="\{"/>
+    
+               <map from="}" to="\}"/>
+    
+               <map from="\textbackslash  " to="\textbackslash \ "/>
+    
+               <map from="\" to="\textbackslash "/>
+  
+            </template>]]></programlisting>
+    </refsection>
+  </doc:template>
+  <xsl:template name="scape">
+    <xsl:param name="string"/>
+    <xsl:call-template name="string-replace">
+      <xsl:with-param name="from">&lt;</xsl:with-param>
+      <xsl:with-param name="to">\textless{}</xsl:with-param>
+      <xsl:with-param name="string">
+        <xsl:call-template name="string-replace">
+          <xsl:with-param name="from">&gt;</xsl:with-param>
+          <xsl:with-param name="to">\textgreater{}</xsl:with-param>
+          <xsl:with-param name="string">
+            <xsl:call-template name="string-replace">
+              <xsl:with-param name="from">~</xsl:with-param>
+              <xsl:with-param name="to">\textasciitilde{}</xsl:with-param>
+              <xsl:with-param name="string">
+                <xsl:call-template name="string-replace">
+                  <xsl:with-param name="from">^</xsl:with-param>
+                  <xsl:with-param name="to">\textasciicircum{}</xsl:with-param>
+                  <xsl:with-param name="string">
+                    <xsl:call-template name="string-replace">
+                      <xsl:with-param name="from">&amp;</xsl:with-param>
+                      <xsl:with-param name="to">\&amp;</xsl:with-param>
+                      <xsl:with-param name="string">
+                        <xsl:call-template name="string-replace">
+                          <xsl:with-param name="from">#</xsl:with-param>
+                          <xsl:with-param name="to">\#</xsl:with-param>
+                          <xsl:with-param name="string">
+                            <xsl:call-template name="string-replace">
+                              <xsl:with-param name="from">_</xsl:with-param>
+                              <xsl:with-param name="to">\_</xsl:with-param>
+                              <xsl:with-param name="string">
+                                <xsl:call-template name="string-replace">
+                                  <xsl:with-param name="from">$</xsl:with-param>
+                                  <xsl:with-param name="to">\$</xsl:with-param>
+                                  <xsl:with-param name="string">
+                                    <xsl:call-template name="string-replace">
+                                      <xsl:with-param name="from">%</xsl:with-param>
+                                      <xsl:with-param name="to">\%</xsl:with-param>
+                                      <xsl:with-param name="string">
+                                        <xsl:call-template name="string-replace">
+                                          <xsl:with-param name="from">|</xsl:with-param>
+                                          <xsl:with-param name="to">\docbooktolatexpipe{}</xsl:with-param>
+                                          <xsl:with-param name="string">
+                                            <xsl:call-template name="string-replace">
+                                              <xsl:with-param name="from">{</xsl:with-param>
+                                              <xsl:with-param name="to">\{</xsl:with-param>
+                                              <xsl:with-param name="string">
+                                                <xsl:call-template name="string-replace">
+                                                  <xsl:with-param name="from">}</xsl:with-param>
+                                                  <xsl:with-param name="to">\}</xsl:with-param>
+                                                  <xsl:with-param name="string">
+                                                    <xsl:call-template name="string-replace">
+                                                      <xsl:with-param name="from">\textbackslash  </xsl:with-param>
+                                                      <xsl:with-param name="to">\textbackslash \ </xsl:with-param>
+                                                      <xsl:with-param name="string">
+                                                        <xsl:call-template name="string-replace">
+                                                          <xsl:with-param name="from">\</xsl:with-param>
+                                                          <xsl:with-param name="to">\textbackslash </xsl:with-param>
+                                                          <xsl:with-param name="string" select="$string"/>
+                                                        </xsl:call-template>
+                                                      </xsl:with-param>
+                                                    </xsl:call-template>
+                                                  </xsl:with-param>
+                                                </xsl:call-template>
+                                              </xsl:with-param>
+                                            </xsl:call-template>
+                                          </xsl:with-param>
+                                        </xsl:call-template>
+                                      </xsl:with-param>
+                                    </xsl:call-template>
+                                  </xsl:with-param>
+                                </xsl:call-template>
+                              </xsl:with-param>
+                            </xsl:call-template>
+                          </xsl:with-param>
+                        </xsl:call-template>
+                      </xsl:with-param>
+                    </xsl:call-template>
+                  </xsl:with-param>
+                </xsl:call-template>
+              </xsl:with-param>
+            </xsl:call-template>
+          </xsl:with-param>
+        </xsl:call-template>
+      </xsl:with-param>
+    </xsl:call-template>
+  </xsl:template>
+  <doc:template xmlns:doc="http://nwalsh.com/xsl/documentation/1.0">
+    <refpurpose>Escape characters for use with <function condition="latex">index</function> 
+         <productname condition="noindex">LaTeX</productname> command</refpurpose>
+    <doc:description>
+      <para>
+        In addition to the characters from <xref linkend="template.scape"/>,
+        certain extra characters must be escaped so that <productname condition="noindex">LaTeX</productname> will not treat
+        them as indexing directives.
+      </para>
+    </doc:description>
+    <refsection>
+      <title>Mapping Source</title>
+      <programlisting><![CDATA[<template name="scape-indexterm">
+    
+               <map from="!" to="&#34;!"/>
+    
+               <map from="|" to="\ensuremath{&#34;|}"/>
+    
+               <map from="@" to="&#34;@"/>
+    
+               <map from="&lt;" to="\textless{}"/>
+    
+               <map from="&gt;" to="\textgreater{}"/>
+    
+               <map from="~" to="\textasciitilde{}"/>
+    
+               <map from="^" to="\textasciicircum{}"/>
+    
+               <map from="&amp;" to="\&amp;"/>
+    
+               <map from="#" to="\#"/>
+    
+               <map from="_" to="\_"/>
+    
+               <map from="$" to="\$"/>
+    
+               <map from="%" to="\%"/>
+    
+               <map from="\}" to="\textbraceright{}"/>
+    
+               <map from="{" to="\textbraceleft{}"/>
+    
+               <map from="}" to="\}"/>
+    
+               <map from="&#34;" to="&#34;&#34;"/>
+    
+               <map from="\textbackslash  " to="\textbackslash \ "/>
+    
+               <map from="\" to="\textbackslash "/>
+  
+            </template>]]></programlisting>
+    </refsection>
+  </doc:template>
+  <xsl:template name="scape-indexterm">
+    <xsl:param name="string"/>
+    <xsl:call-template name="string-replace">
+      <xsl:with-param name="from">!</xsl:with-param>
+      <xsl:with-param name="to">"!</xsl:with-param>
+      <xsl:with-param name="string">
+        <xsl:call-template name="string-replace">
+          <xsl:with-param name="from">|</xsl:with-param>
+          <xsl:with-param name="to">\ensuremath{"|}</xsl:with-param>
+          <xsl:with-param name="string">
+            <xsl:call-template name="string-replace">
+              <xsl:with-param name="from">@</xsl:with-param>
+              <xsl:with-param name="to">"@</xsl:with-param>
+              <xsl:with-param name="string">
+                <xsl:call-template name="string-replace">
+                  <xsl:with-param name="from">&lt;</xsl:with-param>
+                  <xsl:with-param name="to">\textless{}</xsl:with-param>
+                  <xsl:with-param name="string">
+                    <xsl:call-template name="string-replace">
+                      <xsl:with-param name="from">&gt;</xsl:with-param>
+                      <xsl:with-param name="to">\textgreater{}</xsl:with-param>
+                      <xsl:with-param name="string">
+                        <xsl:call-template name="string-replace">
+                          <xsl:with-param name="from">~</xsl:with-param>
+                          <xsl:with-param name="to">\textasciitilde{}</xsl:with-param>
+                          <xsl:with-param name="string">
+                            <xsl:call-template name="string-replace">
+                              <xsl:with-param name="from">^</xsl:with-param>
+                              <xsl:with-param name="to">\textasciicircum{}</xsl:with-param>
+                              <xsl:with-param name="string">
+                                <xsl:call-template name="string-replace">
+                                  <xsl:with-param name="from">&amp;</xsl:with-param>
+                                  <xsl:with-param name="to">\&amp;</xsl:with-param>
+                                  <xsl:with-param name="string">
+                                    <xsl:call-template name="string-replace">
+                                      <xsl:with-param name="from">#</xsl:with-param>
+                                      <xsl:with-param name="to">\#</xsl:with-param>
+                                      <xsl:with-param name="string">
+                                        <xsl:call-template name="string-replace">
+                                          <xsl:with-param name="from">_</xsl:with-param>
+                                          <xsl:with-param name="to">\_</xsl:with-param>
+                                          <xsl:with-param name="string">
+                                            <xsl:call-template name="string-replace">
+                                              <xsl:with-param name="from">$</xsl:with-param>
+                                              <xsl:with-param name="to">\$</xsl:with-param>
+                                              <xsl:with-param name="string">
+                                                <xsl:call-template name="string-replace">
+                                                  <xsl:with-param name="from">%</xsl:with-param>
+                                                  <xsl:with-param name="to">\%</xsl:with-param>
+                                                  <xsl:with-param name="string">
+                                                    <xsl:call-template name="string-replace">
+                                                      <xsl:with-param name="from">\}</xsl:with-param>
+                                                      <xsl:with-param name="to">\textbraceright{}</xsl:with-param>
+                                                      <xsl:with-param name="string">
+                                                        <xsl:call-template name="string-replace">
+                                                          <xsl:with-param name="from">{</xsl:with-param>
+                                                          <xsl:with-param name="to">\textbraceleft{}</xsl:with-param>
+                                                          <xsl:with-param name="string">
+                                                            <xsl:call-template name="string-replace">
+                                                              <xsl:with-param name="from">}</xsl:with-param>
+                                                              <xsl:with-param name="to">\}</xsl:with-param>
+                                                              <xsl:with-param name="string">
+                                                                <xsl:call-template name="string-replace">
+                                                                  <xsl:with-param name="from">"</xsl:with-param>
+                                                                  <xsl:with-param name="to">""</xsl:with-param>
+                                                                  <xsl:with-param name="string">
+                                                                    <xsl:call-template name="string-replace">
+                                                                      <xsl:with-param name="from">\textbackslash  </xsl:with-param>
+                                                                      <xsl:with-param name="to">\textbackslash \ </xsl:with-param>
+                                                                      <xsl:with-param name="string">
+                                                                        <xsl:call-template name="string-replace">
+                                                                          <xsl:with-param name="from">\</xsl:with-param>
+                                                                          <xsl:with-param name="to">\textbackslash </xsl:with-param>
+                                                                          <xsl:with-param name="string" select="$string"/>
+                                                                        </xsl:call-template>
+                                                                      </xsl:with-param>
+                                                                    </xsl:call-template>
+                                                                  </xsl:with-param>
+                                                                </xsl:call-template>
+                                                              </xsl:with-param>
+                                                            </xsl:call-template>
+                                                          </xsl:with-param>
+                                                        </xsl:call-template>
+                                                      </xsl:with-param>
+                                                    </xsl:call-template>
+                                                  </xsl:with-param>
+                                                </xsl:call-template>
+                                              </xsl:with-param>
+                                            </xsl:call-template>
+                                          </xsl:with-param>
+                                        </xsl:call-template>
+                                      </xsl:with-param>
+                                    </xsl:call-template>
+                                  </xsl:with-param>
+                                </xsl:call-template>
+                              </xsl:with-param>
+                            </xsl:call-template>
+                          </xsl:with-param>
+                        </xsl:call-template>
+                      </xsl:with-param>
+                    </xsl:call-template>
+                  </xsl:with-param>
+                </xsl:call-template>
+              </xsl:with-param>
+            </xsl:call-template>
+          </xsl:with-param>
+        </xsl:call-template>
+      </xsl:with-param>
+    </xsl:call-template>
+  </xsl:template>
+  <doc:template xmlns:doc="http://nwalsh.com/xsl/documentation/1.0">
+    <refpurpose>Verbatim-text escaping for <productname condition="noindex">LaTeX</productname> active characters</refpurpose>
+    <refsection>
+      <title>Mapping Source</title>
+      <programlisting><![CDATA[<template name="scape-verbatim">
+    
+               <map from="~" to="\textasciitilde{}"/>
+    
+               <map from="^" to="\textasciicircum{}"/>
+    
+               <map from="&amp;" to="\&amp;"/>
+    
+               <map from="#" to="\#"/>
+    
+               <map from="_" to="\_\dbz{}"/>
+    
+               <map from="$" to="\$"/>
+    
+               <map from="%" to="\%"/>
+    
+               <map from="/" to="/\dbz{}"/>
+    
+               <map from="-" to="-\dbz{}"/>
+    
+               <map from="+" to="+\dbz{}"/>
+    
+               <map from="." to=".\dbz{}"/>
+    
+               <map from="(" to="(\dbz{}"/>
+    
+               <map from=")" to=")\dbz{}"/>
+    
+               <map from="{" to="\docbooktolatexgobble\string\{"/>
+    
+               <map from="}" to="\docbooktolatexgobble\string\}"/>
+    
+               <map from="\" to="\docbooktolatexgobble\string\\"/>
+  
+            </template>]]></programlisting>
+    </refsection>
+  </doc:template>
+  <xsl:template name="scape-verbatim">
+    <xsl:param name="string"/>
+    <xsl:call-template name="string-replace">
+      <xsl:with-param name="from">~</xsl:with-param>
+      <xsl:with-param name="to">\textasciitilde{}</xsl:with-param>
+      <xsl:with-param name="string">
+        <xsl:call-template name="string-replace">
+          <xsl:with-param name="from">^</xsl:with-param>
+          <xsl:with-param name="to">\textasciicircum{}</xsl:with-param>
+          <xsl:with-param name="string">
+            <xsl:call-template name="string-replace">
+              <xsl:with-param name="from">&amp;</xsl:with-param>
+              <xsl:with-param name="to">\&amp;</xsl:with-param>
+              <xsl:with-param name="string">
+                <xsl:call-template name="string-replace">
+                  <xsl:with-param name="from">#</xsl:with-param>
+                  <xsl:with-param name="to">\#</xsl:with-param>
+                  <xsl:with-param name="string">
+                    <xsl:call-template name="string-replace">
+                      <xsl:with-param name="from">_</xsl:with-param>
+                      <xsl:with-param name="to">\_\dbz{}</xsl:with-param>
+                      <xsl:with-param name="string">
+                        <xsl:call-template name="string-replace">
+                          <xsl:with-param name="from">$</xsl:with-param>
+                          <xsl:with-param name="to">\$</xsl:with-param>
+                          <xsl:with-param name="string">
+                            <xsl:call-template name="string-replace">
+                              <xsl:with-param name="from">%</xsl:with-param>
+                              <xsl:with-param name="to">\%</xsl:with-param>
+                              <xsl:with-param name="string">
+                                <xsl:call-template name="string-replace">
+                                  <xsl:with-param name="from">/</xsl:with-param>
+                                  <xsl:with-param name="to">/\dbz{}</xsl:with-param>
+                                  <xsl:with-param name="string">
+                                    <xsl:call-template name="string-replace">
+                                      <xsl:with-param name="from">-</xsl:with-param>
+                                      <xsl:with-param name="to">-\dbz{}</xsl:with-param>
+                                      <xsl:with-param name="string">
+                                        <xsl:call-template name="string-replace">
+                                          <xsl:with-param name="from">+</xsl:with-param>
+                                          <xsl:with-param name="to">+\dbz{}</xsl:with-param>
+                                          <xsl:with-param name="string">
+                                            <xsl:call-template name="string-replace">
+                                              <xsl:with-param name="from">.</xsl:with-param>
+                                              <xsl:with-param name="to">.\dbz{}</xsl:with-param>
+                                              <xsl:with-param name="string">
+                                                <xsl:call-template name="string-replace">
+                                                  <xsl:with-param name="from">(</xsl:with-param>
+                                                  <xsl:with-param name="to">(\dbz{}</xsl:with-param>
+                                                  <xsl:with-param name="string">
+                                                    <xsl:call-template name="string-replace">
+                                                      <xsl:with-param name="from">)</xsl:with-param>
+                                                      <xsl:with-param name="to">)\dbz{}</xsl:with-param>
+                                                      <xsl:with-param name="string">
+                                                        <xsl:call-template name="string-replace">
+                                                          <xsl:with-param name="from">{</xsl:with-param>
+                                                          <xsl:with-param name="to">\docbooktolatexgobble\string\{</xsl:with-param>
+                                                          <xsl:with-param name="string">
+                                                            <xsl:call-template name="string-replace">
+                                                              <xsl:with-param name="from">}</xsl:with-param>
+                                                              <xsl:with-param name="to">\docbooktolatexgobble\string\}</xsl:with-param>
+                                                              <xsl:with-param name="string">
+                                                                <xsl:call-template name="string-replace">
+                                                                  <xsl:with-param name="from">\</xsl:with-param>
+                                                                  <xsl:with-param name="to">\docbooktolatexgobble\string\\</xsl:with-param>
+                                                                  <xsl:with-param name="string" select="$string"/>
+                                                                </xsl:call-template>
+                                                              </xsl:with-param>
+                                                            </xsl:call-template>
+                                                          </xsl:with-param>
+                                                        </xsl:call-template>
+                                                      </xsl:with-param>
+                                                    </xsl:call-template>
+                                                  </xsl:with-param>
+                                                </xsl:call-template>
+                                              </xsl:with-param>
+                                            </xsl:call-template>
+                                          </xsl:with-param>
+                                        </xsl:call-template>
+                                      </xsl:with-param>
+                                    </xsl:call-template>
+                                  </xsl:with-param>
+                                </xsl:call-template>
+                              </xsl:with-param>
+                            </xsl:call-template>
+                          </xsl:with-param>
+                        </xsl:call-template>
+                      </xsl:with-param>
+                    </xsl:call-template>
+                  </xsl:with-param>
+                </xsl:call-template>
+              </xsl:with-param>
+            </xsl:call-template>
+          </xsl:with-param>
+        </xsl:call-template>
+      </xsl:with-param>
+    </xsl:call-template>
+  </xsl:template>
+  <doc:template xmlns:doc="http://nwalsh.com/xsl/documentation/1.0">
+    <refpurpose>Escape characters for use with the <productname>hyperref</productname> 
+         <productname condition="noindex">LaTeX</productname> package</refpurpose>
+    <refsection>
+      <title>Mapping Source</title>
+      <programlisting><![CDATA[<template name="scape-href">
+    
+               <map from="&amp;" to="\&amp;"/>
+    
+               <map from="%" to="\%"/>
+    
+               <map from="[" to="\["/>
+    
+               <map from="]" to="\]"/>
+    
+               <map from="{" to="\{"/>
+    
+               <map from="}" to="\}"/>
+    
+               <map from="\" to="\docbooktolatexgobble\string\\"/>
+  
+            </template>]]></programlisting>
+    </refsection>
+  </doc:template>
+  <xsl:template name="scape-href">
+    <xsl:param name="string"/>
+    <xsl:call-template name="string-replace">
+      <xsl:with-param name="from">&amp;</xsl:with-param>
+      <xsl:with-param name="to">\&amp;</xsl:with-param>
+      <xsl:with-param name="string">
+        <xsl:call-template name="string-replace">
+          <xsl:with-param name="from">%</xsl:with-param>
+          <xsl:with-param name="to">\%</xsl:with-param>
+          <xsl:with-param name="string">
+            <xsl:call-template name="string-replace">
+              <xsl:with-param name="from">[</xsl:with-param>
+              <xsl:with-param name="to">\[</xsl:with-param>
+              <xsl:with-param name="string">
+                <xsl:call-template name="string-replace">
+                  <xsl:with-param name="from">]</xsl:with-param>
+                  <xsl:with-param name="to">\]</xsl:with-param>
+                  <xsl:with-param name="string">
+                    <xsl:call-template name="string-replace">
+                      <xsl:with-param name="from">{</xsl:with-param>
+                      <xsl:with-param name="to">\{</xsl:with-param>
+                      <xsl:with-param name="string">
+                        <xsl:call-template name="string-replace">
+                          <xsl:with-param name="from">}</xsl:with-param>
+                          <xsl:with-param name="to">\}</xsl:with-param>
+                          <xsl:with-param name="string">
+                            <xsl:call-template name="string-replace">
+                              <xsl:with-param name="from">\</xsl:with-param>
+                              <xsl:with-param name="to">\docbooktolatexgobble\string\\</xsl:with-param>
+                              <xsl:with-param name="string" select="$string"/>
+                            </xsl:call-template>
+                          </xsl:with-param>
+                        </xsl:call-template>
+                      </xsl:with-param>
+                    </xsl:call-template>
+                  </xsl:with-param>
+                </xsl:call-template>
+              </xsl:with-param>
+            </xsl:call-template>
+          </xsl:with-param>
+        </xsl:call-template>
+      </xsl:with-param>
+    </xsl:call-template>
+  </xsl:template>
+  <doc:template xmlns:doc="http://nwalsh.com/xsl/documentation/1.0">
+    <refpurpose>Escape characters for use with the <productname>url</productname> 
+         <productname condition="noindex">LaTeX</productname> package</refpurpose>
+    <refsection>
+      <title>Mapping Source</title>
+      <programlisting><![CDATA[<template name="scape-url">
+    
+               <map from="&amp;" to="\string&amp;"/>
+    
+               <map from="%" to="\%"/>
+    
+               <map from="{" to="\{"/>
+    
+               <map from="}" to="\}"/>
+    
+               <map from="\" to="\docbooktolatexgobble\string\\"/>
+  
+            </template>]]></programlisting>
+    </refsection>
+  </doc:template>
+  <xsl:template name="scape-url">
+    <xsl:param name="string"/>
+    <xsl:call-template name="string-replace">
+      <xsl:with-param name="from">&amp;</xsl:with-param>
+      <xsl:with-param name="to">\string&amp;</xsl:with-param>
+      <xsl:with-param name="string">
+        <xsl:call-template name="string-replace">
+          <xsl:with-param name="from">%</xsl:with-param>
+          <xsl:with-param name="to">\%</xsl:with-param>
+          <xsl:with-param name="string">
+            <xsl:call-template name="string-replace">
+              <xsl:with-param name="from">{</xsl:with-param>
+              <xsl:with-param name="to">\{</xsl:with-param>
+              <xsl:with-param name="string">
+                <xsl:call-template name="string-replace">
+                  <xsl:with-param name="from">}</xsl:with-param>
+                  <xsl:with-param name="to">\}</xsl:with-param>
+                  <xsl:with-param name="string">
+                    <xsl:call-template name="string-replace">
+                      <xsl:with-param name="from">\</xsl:with-param>
+                      <xsl:with-param name="to">\docbooktolatexgobble\string\\</xsl:with-param>
+                      <xsl:with-param name="string" select="$string"/>
+                    </xsl:call-template>
+                  </xsl:with-param>
+                </xsl:call-template>
+              </xsl:with-param>
+            </xsl:call-template>
+          </xsl:with-param>
+        </xsl:call-template>
+      </xsl:with-param>
+    </xsl:call-template>
+  </xsl:template>
+  <doc:template xmlns:doc="http://nwalsh.com/xsl/documentation/1.0">
+    <refpurpose>Escape the ] character in <productname condition="noindex">LaTeX</productname> optional arguments (experimental)</refpurpose>
+    <refsection>
+      <title>Mapping Source</title>
+      <programlisting><![CDATA[<template name="scape-optionalarg">
+    
+               <map from="]" to="{\rbrack}"/>
+  
+            </template>]]></programlisting>
+    </refsection>
+  </doc:template>
+  <xsl:template name="scape-optionalarg">
+    <xsl:param name="string"/>
+    <xsl:call-template name="string-replace">
+      <xsl:with-param name="from">]</xsl:with-param>
+      <xsl:with-param name="to">{\rbrack}</xsl:with-param>
+      <xsl:with-param name="string" select="$string"/>
+    </xsl:call-template>
+  </xsl:template>
+  <doc:template xmlns:doc="http://nwalsh.com/xsl/documentation/1.0">
+    <refpurpose>Basic line-breaking for verbatim text</refpurpose>
+    <doc:description>
+      <para>
+        Allow line breaking after certain characters.
+        Text should be escaped with the <xref linkend="template.scape"/>
+        template before being passed to this template.
+      </para>
+    </doc:description>
+    <refsection>
+      <title>Mapping Source</title>
+      <programlisting><![CDATA[<template name="scape-slash">
+    
+               <map from="." to=".\dbz{}"/>
+    
+               <map from="/" to="/\dbz{}"/>
+  
+            </template>]]></programlisting>
+    </refsection>
+  </doc:template>
+  <xsl:template name="scape-slash">
+    <xsl:param name="string"/>
+    <xsl:call-template name="string-replace">
+      <xsl:with-param name="from">.</xsl:with-param>
+      <xsl:with-param name="to">.\dbz{}</xsl:with-param>
+      <xsl:with-param name="string">
+        <xsl:call-template name="string-replace">
+          <xsl:with-param name="from">/</xsl:with-param>
+          <xsl:with-param name="to">/\dbz{}</xsl:with-param>
+          <xsl:with-param name="string" select="$string"/>
+        </xsl:call-template>
+      </xsl:with-param>
+    </xsl:call-template>
+  </xsl:template>
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/sections.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/sections.mod.xsl
new file mode 100644
index 00000000000..c7cdd4a3977
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/sections.mod.xsl
@@ -0,0 +1,209 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: sections.mod.xsl,v 1.8 2004/01/03 12:19:15 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="sections" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: sections.mod.xsl,v 1.8 2004/01/03 12:19:15 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.6">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Sections <filename>sections.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>sections.mod.xsl</filename> contains the
+			XSL templates for <doc:db>section</doc:db>, <doc:db>simplesect</doc:db>,
+			and <doc:db>sect1</doc:db>, etc.</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process explicitly-nested sections</refpurpose>
+		<doc:description>
+			<para>
+				Formats a section's title (including numbering, if applicable)
+				then allows all child elements to be processed. The title
+				is formatted the using &LaTeX; mapping identified by the
+				element name (e.g. <doc:db>sect1</doc:db>, etc.).
+			</para>
+		</doc:description>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>bridgehead</term>
+					<listitem>
+						<para>
+
+							If <literal>true()</literal>, the title is
+							processed like a <doc:db>bridgehead</doc:db> (that
+							is, the section is unnumbered and does not appear
+							in the <doc:db>toc</doc:db>). This parameter
+							defaults to <literal>false()</literal> unless the
+							section appears within a preface.
+
+						</para>
+					</listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+
+			<para>Currently, <quote>info</quote> elements (e.g.
+			<doc:db>sect1info</doc:db>), <doc:db>subtitle</doc:db> and
+			<doc:db>titleabbrev</doc:db> are not honoured.</para>
+
+			<para>The use of special components such as <doc:db>toc</doc:db>,
+			<doc:db>lot</doc:db>, <doc:db>index</doc:db> and
+			<doc:db>glossary</doc:db> is unlikely to be successful.</para>
+
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_book;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><para>&mapping;</para></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+
+	<xsl:template match="sect1|sect2|sect3|sect4|sect5">
+		<xsl:param name="bridgehead" select="ancestor::preface|ancestor::colophon|ancestor::dedication|ancestor::partintro"/>
+		<xsl:variable name="template">
+			<xsl:value-of select="local-name(.)"/>
+			<xsl:if test="$bridgehead"><xsl:text>*</xsl:text></xsl:if>
+		</xsl:variable>
+		<xsl:call-template name="map.begin">
+			<xsl:with-param name="keyword" select="$template"/>
+		</xsl:call-template>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end">
+			<xsl:with-param name="keyword" select="$template"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process recursive and leaf sections</refpurpose>
+		<doc:description>
+			<para>
+				Formats a section's title (including numbering, if applicable)
+				then allows all child elements to be processed. The title
+				is formatted the using &LaTeX; mapping identified by the
+				equivalent explicit element (e.g. <doc:db>sect1</doc:db>, etc.).
+			</para>
+		</doc:description>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>bridgehead</term>
+					<listitem>
+						<para>
+
+							If <literal>true()</literal>, the title is
+							processed like a <doc:db>bridgehead</doc:db> (that
+							is, the section is unnumbered and does not appear
+							in the <doc:db>toc</doc:db>). This parameter
+							defaults to <literal>false()</literal> unless the
+							section appears within a preface.
+
+						</para>
+					</listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>level</term>
+					<listitem>
+						<para>
+
+						The numeric nesting level of the section. This is
+						automatically calculated as "one greater than the
+						number of ancestor <doc:db>section</doc:db>s".
+
+						</para>
+					</listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+
+			<para>Titles for sections nested beyond a depth of five are
+			formatted like <doc:db>sect5</doc:db>.</para>
+
+			<para>Currently, <quote>info</quote> elements (e.g.
+			<doc:db>sectioninfo</doc:db>), <doc:db>subtitle</doc:db> and
+			<doc:db>titleabbrev</doc:db> are not honoured.</para>
+
+			<para>The use of special components such as <doc:db>toc</doc:db>,
+			<doc:db>lot</doc:db>, <doc:db>index</doc:db> and
+			<doc:db>glossary</doc:db> is unlikely to be successful.</para>
+
+			<para>&LaTeX; makes no semantic distinction between
+			<doc:db>section</doc:db> and <doc:db>simplesect</doc:db>.</para>
+
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_book;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><para>&mapping;</para></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="section|simplesect">
+		<xsl:param name="bridgehead" select="ancestor::preface|ancestor::colophon|ancestor::dedication"/>
+		<xsl:param name="level" select="count(ancestor::section)+1"/>
+		<xsl:variable name="template">
+			<xsl:choose>
+				<xsl:when test='$level&lt;6'>
+					<xsl:text>sect</xsl:text>
+					<xsl:value-of select="$level"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:message>DB2LaTeX: recursive section|simplesect &gt; 5 not well supported.</xsl:message>
+					<xsl:text>sect6</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+			<xsl:if test="$bridgehead"><xsl:text>*</xsl:text></xsl:if>
+		</xsl:variable>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:call-template name="map.begin">
+			<xsl:with-param name="keyword" select="$template"/>
+		</xsl:call-template>
+		<xsl:call-template name="content-templates"/>
+		<xsl:call-template name="map.end">
+			<xsl:with-param name="keyword" select="$template"/>
+		</xsl:call-template>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/sgmltag.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/sgmltag.mod.xsl
new file mode 100644
index 00000000000..3040a4acd6f
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/sgmltag.mod.xsl
@@ -0,0 +1,170 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: sgmltag.mod.xsl,v 1.5 2003/12/31 13:18:04 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="sgmltag" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: sgmltag.mod.xsl,v 1.5 2003/12/31 13:18:04 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.4">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title><acronym>SGML</acronym> Tags <filename>sgmltag.mod.xsl</filename></title>
+		<partintro>
+			<para>The file <filename>sgmltag.mod.xsl</filename> contains the
+			XSL template for <doc:db>sgmltag</doc:db>.</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose> Process <doc:db>sgmltag</doc:db> elements </refpurpose>
+		<doc:description>
+			<para>
+
+				Expresses the element using inline sequences plus any necessary
+				punctuation. Some classes are formatted as monospace text.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Unknown classes are emitted without special formatting.
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+
+	<xsl:template match="sgmltag">
+		<xsl:param name="class">
+			<xsl:choose>
+				<xsl:when test="@class">
+					<xsl:value-of select="normalize-space(@class)"/>
+				</xsl:when>
+				<xsl:otherwise>element</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:choose>
+			<xsl:when test="$class='attribute'">
+				<xsl:call-template name="inline.charseq"/>
+			</xsl:when>
+			<xsl:when test="$class='attvalue'">
+				<xsl:call-template name="inline.monoseq"/>
+			</xsl:when>
+			<xsl:when test="$class='element'">
+				<xsl:call-template name="inline.monoseq"/>
+			</xsl:when>
+			<xsl:when test="$class='endtag'">
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+						<xsl:text>&lt;/</xsl:text>
+						<xsl:apply-templates/>
+						<xsl:text>&gt;</xsl:text>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$class='genentity'">
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+						<xsl:text>\&amp;</xsl:text>
+						<xsl:apply-templates/>
+						<xsl:text>;</xsl:text>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$class='numcharref'">
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+						<xsl:text>\&amp;\#</xsl:text>
+						<xsl:apply-templates/>
+						<xsl:text>;</xsl:text>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$class='paramentity'">
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+						<xsl:text>\%</xsl:text>
+						<xsl:apply-templates/>
+						<xsl:text>;</xsl:text>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$class='pi'">
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+						<xsl:text>&lt;?</xsl:text>
+						<xsl:apply-templates/>
+						<xsl:text>?&gt;</xsl:text>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$class='xmlpi'">
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+						<xsl:text>&lt;?</xsl:text>
+						<xsl:apply-templates/>
+						<xsl:text>?&gt;</xsl:text>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$class='starttag'">
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+						<xsl:text>&lt;</xsl:text>
+						<xsl:apply-templates/>
+						<xsl:text>&gt;</xsl:text>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$class='emptytag'">
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+						<xsl:text>&lt;</xsl:text>
+						<xsl:apply-templates/>
+						<xsl:text>/&gt;</xsl:text>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$class='sgmlcomment'">
+				<xsl:call-template name="inline.monoseq">
+					<xsl:with-param name="content">
+						<xsl:text>&lt;!--</xsl:text>
+						<xsl:apply-templates/>
+						<xsl:text>--&gt;</xsl:text>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="inline.charseq"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/foil.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/slides/foil.mod.xsl
new file mode 100644
index 00000000000..32f1b895bf1
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/foil.mod.xsl
@@ -0,0 +1,52 @@
+<?xml version='1.0'?>
+<!--############################################################################# 
+|	$Id: foil.mod.xsl,v 1.1 2003/04/06 18:31:49 rcasellas Exp $
+|- #############################################################################
+|	$Author: rcasellas $
+|														
+|   PURPOSE:
++ ############################################################################## -->
+
+<xsl:stylesheet 
+    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+    xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+    exclude-result-prefixes="doc" version='1.0'>
+
+
+    <!--############################################################################# -->
+    <!-- DOCUMENTATION                                                                -->
+    <doc:reference id="foil" xmlns="">
+    </doc:reference>
+    <!--############################################################################# -->
+
+    <xsl:template match="foilgroup">
+	<xsl:text>                                                                        &#10;&#10;</xsl:text>
+	<xsl:text>%---------------------------------------------------------------------- PART &#10;</xsl:text>
+	<xsl:text>\part{</xsl:text><xsl:apply-templates select="title"/><xsl:text>            }&#10;</xsl:text>
+	<xsl:text>%---------------------------------------------------------------------- PART &#10;</xsl:text>
+	<xsl:call-template name="label.id"/>
+	<xsl:text>&#10;&#10;</xsl:text>
+	<xsl:apply-templates select="foil"/>
+    </xsl:template>
+
+    <xsl:template match="foilgroup/title">
+	<xsl:apply-templates />
+    </xsl:template>
+
+    <xsl:template match="foil">
+	<xsl:text>&#10;</xsl:text>
+	<xsl:text>%---------------------------------------------------------------------- SLIDE &#10;</xsl:text>
+	<xsl:text>\begin{slide}{</xsl:text>
+	<xsl:apply-templates select="title"/>
+	<xsl:text>}&#10;</xsl:text>
+	<xsl:call-template name="label.id"/>
+	<xsl:text>&#10;</xsl:text>
+	<xsl:apply-templates select="*[not (self::title)]"/>
+	<xsl:text>\end{slide}&#10;</xsl:text>
+    </xsl:template>
+
+    <xsl:template match="foil/title">
+	<xsl:apply-templates />
+    </xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/caution.pdf b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/caution.pdf
new file mode 100755
index 00000000000..a0afabfa232
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/caution.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/important.pdf b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/important.pdf
new file mode 100755
index 00000000000..a0afabfa232
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/important.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/note.pdf b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/note.pdf
new file mode 100755
index 00000000000..ec6c248a2a9
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/note.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/tip.pdf b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/tip.pdf
new file mode 100755
index 00000000000..54f5dedb5d4
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/tip.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/warning.pdf b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/warning.pdf
new file mode 100755
index 00000000000..a0afabfa232
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/figures/warning.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.pdf b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.pdf
new file mode 100644
index 00000000000..43ae3e68b5b
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.pdf
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.tex b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.tex
new file mode 100644
index 00000000000..47fb1227d86
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.tex
@@ -0,0 +1,420 @@
+\documentclass[17pt,headrule,footrule,landscape]{foils}
+\usepackage[latin1]{inputenc}
+\usepackage{pstricks,pst-node,pst-text,pst-3d}
+\usepackage{subfigure}
+\usepackage{fancybox}
+\usepackage{a4wide}
+\usepackage{times}
+\usepackage{fancyvrb}
+\usepackage{amsmath,amsthm, amsfonts, amssymb, amsxtra,amsopn}
+\usepackage{anysize}
+\usepackage[pdftex,bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, linktocpage,hyperfigures,hyperindex,citecolor=blue,urlcolor=blue]{hyperref}
+\usepackage[english]{babel}
+\usepackage[pdftex]{graphicx}
+\pdfcompresslevel=9
+%------------------------------------------------------- Values and counters
+\marginsize{1.5cm}{1.5cm}{0.5cm}{0.5cm}
+\renewcommand\floatpagefraction{.9}
+\renewcommand\topfraction{.9}
+\renewcommand\bottomfraction{.9}
+\renewcommand\textfraction{.1}
+
+\usepackage[usenames,pdftex]{color}
+%------------------------------------------------------- BfBlue Command
+\newcommand{\bfblue}[1]{ \textcolor{blue}{\bf #1} }
+
+%------------------------------------------------------- BfGreen Command
+\newcommand{\bfgreen}[1]{ \textcolor{blue}{\bf #1} }
+
+%------------------------------------------------------- BfRed Command
+\newcommand{\bfred}[1]{ \textcolor{red}{\bf #1} }
+
+%------------------------------------------------------- BfBlue Command
+\newcommand{\emblue}[1]{ \textcolor{blue}{\emph{#1}} }
+
+%------------------------------------------------------- BfGreen Command
+\newcommand{\emgreen}[1]{ \textcolor{blue}{\emph{#1}} }
+
+%------------------------------------------------------- BfRed Command
+\newcommand{\emred}[1]{ \textcolor{red}{\emph{#1}} }
+
+%------------------------------------------------------- Part Command
+\newcommand{\part}[1]{
+\foilhead{}
+\vspace{2cm}
+\begin{center}
+\Huge{\textcolor{blue}{#1}}
+\end{center}}
+ \newcommand{\dbz}{} 
+%------------------------------------------------------- Slide Command
+\newcommand{\slide}[1]{
+\foilhead[-0.5in]{\large{\textcolor{blue}{#1}}}
+}
+\newcommand{\id}[1]{
+\label{#1}
+\hypertarget{#1}{}
+}
+% --------------------------------------------
+\newenvironment{admminipage}{
+\begin{Sbox}
+\begin{minipage}
+}{
+\end{minipage}
+\end{Sbox}
+\fbox{\TheSbox}
+}
+\newlength{\admlength}
+\newenvironment{admonition}[2] {
+\hspace{0mm}\newline\hspace*\fill\newline
+\noindent
+\setlength{\fboxsep}{5pt}
+\setlength{\admlength}{\linewidth}
+\addtolength{\admlength}{-10\fboxsep}
+\addtolength{\admlength}{-10\fboxrule}
+\admminipage{\admlength}
+\bfblue{\sc\large{#2}}\newline
+\\[1mm]
+%\sffamily
+\includegraphics[width=1cm]{#1}
+\addtolength{\admlength}{-1cm}
+\addtolength{\admlength}{-20pt}
+\begin{minipage}[lt]{\admlength}
+\parskip=0.5\baselineskip \advance\parskip by 0pt plus 2pt
+}{
+\vspace{5mm}
+\end{minipage}
+\endadmminipage
+\vspace{.5em}
+\par
+}
+%--------------------------------------------------SLIDES INFORMATION
+\title{{\black The Slides Document Type}}
+\author{{\black }}
+ \begin{document}
+\maketitle
+%--------------------------------------------------SLIDES INFORMATION
+\title{{\black The Slides Document Type}}
+\author{{\black }}
+ 
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Introduction}
+\label{id2739608}
+
+This is the introductory slide.
+
+If you use foil groups (previously called sections), you can have introductory slides before the first group.
+
+\begin{admonition}{figures/warning}{Warning! :)}% NOTICE: see the db2latex FAQ w.r.t db2latex variable $latex.admonition.path
+
+This is a work in progress ("release early, release often")
+\end{admonition}
+
+\end{slide}
+                                                                        
+
+%---------------------------------------------------------------------- PART 
+\part{Purpose and History            }
+%---------------------------------------------------------------------- PART 
+\label{id2739637}
+
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{What Are Slides?}
+\label{id2739648}
+
+\begin{itemize}
+%--- Item
+\item 
+An XML presentation tool
+
+
+%--- Item
+\item 
+Suitable for HTML or PDF presentations
+
+
+%--- Item
+\item 
+Supported by Open Source software
+
+\end{itemize}
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Where Do They Come From?}
+\label{id2739677}
+
+\begin{itemize}
+%--- Item
+\item 
+Maintained by the \href{http://docbook.sourceforge.net/}{DocBook Open Repository} Project at
+\href{http://sourceforge.net/}{SourceForge}
+
+
+%--- Item
+\item 
+Customization layer of \href{http://www.oasis-open.org/docbook/xml/simple/}{Simplified DocBook}
+
+\end{itemize}
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Why?}
+\label{id2739724}
+
+\begin{itemize}
+%--- Item
+\item 
+So Norm could give presentations
+
+
+%--- Item
+\item 
+So Norm could publish those presentations on the web
+
+
+%--- Item
+\item 
+So Norm could have {\em accessible} presentations that didn't rely on the grotesque HTML output of some otherwise bloated, proprietary tool
+
+
+%--- Item
+\item 
+So Norm could cut-and-paste from his DocBook articles and papers directly into his slides
+
+
+%--- Item
+\item 
+Oh, let's face it: because it was there. Like the proverbial mountain.
+
+\end{itemize}
+\end{slide}
+                                                                        
+
+%---------------------------------------------------------------------- PART 
+\part{Authoring            }
+%---------------------------------------------------------------------- PART 
+\label{id2739773}
+
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Minimal Presentation}
+\label{id2739783}
+
+The smallest possible presentation looks like this:
+
+\begin{Verbatim}[]
+<?xml version='1.0'?>
+<!DOCTYPE slides PUBLIC "-//Norman Walsh//DTD Slides XML V3.0b1//EN"
+                 "http://docbook.sourceforge.net/release/slides/3.0b1/slides.dtd">
+<slides>
+<slidesinfo>
+<title>Presentation Title</title>
+</slidesinfo>
+<foil><title>Foil Title</title>
+<para>Foil content</para>
+</foil>
+</slides>
+\end{Verbatim}
+
+Every presentation must contain at least one slide.
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Presentation Metadata}
+\label{id2739810}
+
+Presentations usually have more metadata in the {\texttt{{slidesinfo}}} wrapper. Here's a typical example:
+
+\begin{Verbatim}[]
+<slidesinfo>
+  <title>Supporting Localized Generated Text</title>
+  <titleabbrev>Generated Text</titleabbrev>
+  <author><firstname>Norman</firstname><surname>Walsh</surname></author>
+  <pubdate>Sunday, 08 Apr 2001</pubdate>
+  <confgroup>
+    <conftitle>XSLTUK-01</conftitle>
+    <confdates>08 Apr - 09 Apr 2001</confdates>
+    <conftitle role="address">Keble College, Oxford, UK</conftitle>
+    <confnum>1</confnum>
+  </confgroup>
+  <releaseinfo role="version">Version TEST</releaseinfo>
+  <copyright><year>2001</year>
+             <holder>Sun Microsystems, Inc.</holder></copyright>
+</slidesinfo>
+\end{Verbatim}
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Presentation Content}
+\label{id2739830}
+
+It's common for individual slides to consist of a single bulleted or numbered list. However, the full range of �block level� Simplified DocBook elements are avialable.
+\end{slide}
+                                                                        
+
+%---------------------------------------------------------------------- PART 
+\part{Styling            }
+%---------------------------------------------------------------------- PART 
+\label{id2739862}
+
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{HTML}
+\label{id2739872}
+
+There are a lot of HTML options. When you publish your presentation on the web, it's probably best to use one of the simpler, more accessible styles. For your actual live presentation, you may want to choose something fancier.
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Plain HTML}
+\label{id2739888}
+
+\begin{itemize}
+%--- Item
+\item 
+\href{../default/}{{\texttt{{default.\dbz{}xsl}}}}
+and
+\href{../plain/}{{\texttt{{plain.\dbz{}xsl}}}} produce fairly simple presentations
+
+
+%--- Item
+\item 
+\href{../tables/}{{\texttt{{tables.\dbz{}xsl}}}}
+uses a table to show the navigation context (somewhat like the tabular
+\href{http://docbook.sourceforge.net/}{Website} style)
+
+
+%--- Item
+\item 
+\href{../vslides/}{{\texttt{{vslides.\dbz{}xsl}}}} places navigation on the left side instead of the top and bottom
+
+
+%--- Item
+\item 
+\href{../w3c/}{{\texttt{{w3c.\dbz{}xsl}}}} produces slides that resemble the format used by the W3C for presentations
+
+\end{itemize}
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Fancy HTML}
+\label{id2739970}
+
+\begin{itemize}
+%--- Item
+\item 
+\href{../frames1/frames.html}{{\texttt{{frames.\dbz{}xsl}}}} uses frames. There are several options that you can apply:
+
+\begin{itemize}
+%--- Item
+\item 
+\href{../frames2/frames.html}{overlay} uses CSS absolute positioning to keep the navigation static on the pages (only works on recent browsers)
+
+
+%--- Item
+\item 
+\href{../frames3/frames.html}{multiframe} uses additional frames to keep the navigation static on the pages
+
+
+%--- Item
+\item 
+\href{../frames4/frames.html}{dynamic.toc} uses JavaScript to keep the table of contents and the current slide in sync (only works on recent browsers)
+
+
+%--- Item
+\item 
+\href{../frames5/frames.html}{active.toc} uses JavaScript to make
+the table of context �active� so that you can open and close the foil groups (only works on recent browsers)
+
+
+%--- Item
+\item 
+These toc styles can be combined with \href{../frames6/frames.html}{overlay} or \href{../frames7/frames.html}{multiframe}
+
+\end{itemize}
+
+\end{itemize}
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{PDF}
+\label{id2740078}
+
+The {\texttt{{fo-\dbz{}plain.\dbz{}xsl}}} stylesheet produces XSL Formatting Objects that can subsequently be turned into PDF.
+\end{slide}
+                                                                        
+
+%---------------------------------------------------------------------- PART 
+\part{Presentation            }
+%---------------------------------------------------------------------- PART 
+\label{id2740095}
+
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Look And Feel}
+\label{id2740106}
+
+For HTML display, most of the actual �look-and-feel� of the presentation is controlled by the CSS stylesheet(s) used.
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Presentation Tips}
+\label{id2740122}
+
+\begin{itemize}
+%--- Item
+\item 
+It's usually best if each slide is only one page (avoid scrolling).
+
+
+%--- Item
+\item 
+If you'll be giving your presentation with a projector, make sure you know what resolution you'll have available and test your presentation at that resolution.
+
+
+%--- Item
+\item 
+Make your fonts bigger so the folks in the back of the room can read your slides.
+
+
+%--- Item
+\item 
+Test the equipment before your presentation begins. Really.
+
+
+%--- Item
+\item 
+Speak more slowly. I always forget that one.
+
+\end{itemize}
+\end{slide}
+                                                                        
+
+%---------------------------------------------------------------------- PART 
+\part{Conclusions            }
+%---------------------------------------------------------------------- PART 
+\label{id2740169}
+
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Conclusions}
+\label{id2740175}
+
+It's customary to have a conclusions slide.
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{References}
+\label{id2740187}
+
+References are a good idea too.
+\end{slide}
+
+%---------------------------------------------------------------------- SLIDE 
+\begin{slide}{Q\&A}
+\label{id2740198}
+
+Any questions?
+\end{slide}
+\end{document}
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.xml b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.xml
new file mode 100644
index 00000000000..0774e297082
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.xml
@@ -0,0 +1,251 @@
+<?xml version='1.0'?>
+<!--
+<!DOCTYPE slides SYSTEM "../../schema/dtd/slides.dtd">
+-->
+<slides>
+<slidesinfo>
+  <title>The Slides Document Type</title>
+  <author><firstname>Norman</firstname><surname>Walsh</surname></author>
+  <pubdate>Tuesday, 25 June 2002</pubdate>
+  <releaseinfo role="version">3.1.0</releaseinfo>
+  <copyright><year>2002</year>
+             <holder>Norman Walsh</holder></copyright>
+</slidesinfo>
+
+<foil><title>Introduction</title>
+<para>This is the introductory slide.</para>
+<para>If you use foil groups (previously called sections), you can
+have introductory slides before the first group.</para>
+<warning><title>Warning! :)</title>
+<para>This is a work in progress ("release early, release often")</para>
+</warning>
+</foil>
+
+<foilgroup><title>Purpose and History</title>
+
+<para>Groups can now have introductory text as well.</para>
+
+<foil><title>What Are Slides?</title>
+<itemizedlist>
+<listitem><para>An XML presentation tool
+</para></listitem>
+<listitem><para>Suitable for HTML or PDF presentations
+</para></listitem>
+<listitem><para>Supported by Open Source software
+</para></listitem>
+</itemizedlist>
+</foil>
+
+<foil><title>Where Do They Come From?</title>
+
+<itemizedlist>
+<listitem><para>Maintained by the <ulink url="http://docbook.sourceforge.net/">DocBook
+Open Repository</ulink> Project at
+<ulink url="http://sourceforge.net/">SourceForge</ulink>
+</para></listitem>
+<listitem><para>Customization layer of
+<ulink url="http://www.oasis-open.org/docbook/xml/simple/">Simplified DocBook</ulink>
+</para></listitem>
+</itemizedlist>
+</foil>
+
+<foil><title>Why?</title>
+
+<itemizedlist>
+<listitem><para>So Norm could give presentations
+</para></listitem>
+<listitem><para>So Norm could publish those presentations on the web
+</para></listitem>
+<listitem><para>So Norm could have <emphasis>accessible</emphasis> presentations
+that didn't rely on the grotesque HTML output of some otherwise bloated, proprietary
+tool
+</para></listitem>
+<listitem><para>So Norm could cut-and-paste from his DocBook articles and papers
+directly into his slides
+</para></listitem>
+<listitem><para>Oh, let's face it: because it was there. Like the proverbial mountain.
+</para></listitem>
+</itemizedlist>
+</foil>
+</foilgroup>
+
+<foilgroup><title>Authoring</title>
+
+<para>How to write a presentation.</para>
+
+<foil><title>Minimal Presentation</title>
+
+<para>The smallest possible presentation looks like this:</para>
+
+<screen><![CDATA[<?xml version='1.0'?>
+<!DOCTYPE slides PUBLIC "-//Norman Walsh//DTD Slides XML V3.0b1//EN"
+                 "http://docbook.sourceforge.net/release/slides/3.0b1/slides.dtd">
+<slides>
+<slidesinfo>
+<title>Presentation Title</title>
+</slidesinfo>
+<foil><title>Foil Title</title>
+<para>Foil content</para>
+</foil>
+</slides>]]></screen>
+
+<para>Every presentation must contain at least one slide.</para>
+</foil>
+
+<foil><title>Presentation Metadata</title>
+
+<para>Presentations usually have more metadata in the <literal>slidesinfo</literal>
+wrapper. Here's a typical example:</para>
+
+<screen><![CDATA[<slidesinfo>
+  <title>Supporting Localized Generated Text</title>
+  <titleabbrev>Generated Text</titleabbrev>
+  <author><firstname>Norman</firstname><surname>Walsh</surname></author>
+  <pubdate>Sunday, 08 Apr 2001</pubdate>
+  <confgroup>
+    <conftitle>XSLTUK-01</conftitle>
+    <confdates>08 Apr - 09 Apr 2001</confdates>
+    <conftitle role="address">Keble College, Oxford, UK</conftitle>
+    <confnum>1</confnum>
+  </confgroup>
+  <releaseinfo role="version">Version TEST</releaseinfo>
+  <copyright><year>2001</year>
+             <holder>Sun Microsystems, Inc.</holder></copyright>
+</slidesinfo>]]></screen>
+</foil>
+
+<foil><title>Presentation Content</title>
+
+<para>It's common for individual slides to consist of a single
+bulleted or numbered list. However, the full range of <quote>block
+level</quote> Simplified DocBook elements are avialable.</para>
+
+</foil>
+</foilgroup>
+
+<foilgroup><title>Styling</title>
+
+<para>How to transform a presentation.</para>
+
+<foil><title>HTML</title>
+
+<para>There are a lot of HTML options. When you publish your
+presentation on the web, it's probably best to use one of the simpler,
+more accessible styles. For your actual live presentation, you may
+want to choose something fancier.</para>
+
+</foil>
+
+<foil><title>Plain HTML</title>
+
+<itemizedlist>
+<listitem><para><ulink url="../default/"><filename>default.xsl</filename></ulink>
+and
+<ulink url="../plain/"><filename>plain.xsl</filename></ulink>
+produce fairly simple presentations
+</para></listitem>
+<listitem><para><ulink url="../tables/"><filename>tables.xsl</filename></ulink>
+uses a table to show the navigation context (somewhat like the tabular
+<ulink url="http://docbook.sourceforge.net/">Website</ulink> style)
+</para></listitem>
+<listitem><para><ulink url="../vslides/"><filename>vslides.xsl</filename></ulink>
+places navigation on the left side instead of the top and bottom
+</para></listitem>
+<listitem><para><ulink url="../w3c/"><filename>w3c.xsl</filename></ulink>
+produces slides that resemble the format used by the W3C for presentations
+</para></listitem>
+</itemizedlist>
+
+</foil>
+
+<foil><title>Fancy HTML</title>
+
+<itemizedlist>
+<listitem><para><ulink url="../frames1/frames.html"><filename>frames.xsl</filename></ulink>
+uses frames. There are several options that you can apply:
+</para>
+<itemizedlist>
+<listitem><para><ulink url="../frames2/frames.html">overlay</ulink> uses CSS absolute positioning
+to keep the navigation static on the pages (only works on recent browsers)
+</para></listitem>
+<listitem><para><ulink url="../frames3/frames.html">multiframe</ulink> uses additional frames
+to keep the navigation static on the pages
+</para></listitem>
+<listitem><para><ulink url="../frames4/frames.html">dynamic.toc</ulink> uses JavaScript to keep
+the table of contents and the current slide in sync (only works on recent browsers)
+</para></listitem>
+<listitem><para><ulink url="../frames5/frames.html">active.toc</ulink> uses JavaScript to make
+the table of context <quote>active</quote> so that you can open and close the foil
+groups (only works on recent browsers)
+</para></listitem>
+<listitem><para>These toc styles can be combined with
+<ulink url="../frames6/frames.html">overlay</ulink> or <ulink url="../frames7/frames.html">multiframe</ulink>
+</para></listitem>
+</itemizedlist>
+</listitem>
+</itemizedlist>
+</foil>
+
+<foil><title>PDF</title>
+
+<para>The <filename>fo-plain.xsl</filename> stylesheet produces XSL Formatting
+Objects that can subsequently be turned into PDF.</para>
+
+</foil>
+
+</foilgroup>
+
+<foilgroup><title>Presentation</title>
+
+<para>How to customize and present a set of slides.</para>
+
+<foil><title>Look And Feel</title>
+
+<para>For HTML display, most of the actual
+<quote>look-and-feel</quote> of the presentation is controlled by the CSS
+stylesheet(s) used.</para>
+
+</foil>
+
+<foil><title>Presentation Tips</title>
+
+<itemizedlist>
+<listitem><para>It's usually best if each slide is only one page (avoid scrolling).
+</para></listitem>
+<listitem><para>If you'll be giving your presentation with a projector, make sure you
+know what resolution you'll have available and test your presentation at that resolution.
+</para></listitem>
+<listitem><para>Make your fonts bigger so the folks in the back of the room can read
+your slides.
+</para></listitem>
+<listitem><para>Test the equipment before your presentation begins. Really.
+</para></listitem>
+<listitem><para>Speak more slowly. I always forget that one.
+</para></listitem>
+</itemizedlist>
+</foil>
+
+</foilgroup>
+
+<foilgroup><title>Conclusions</title>
+
+<foil><title>Conclusions</title>
+
+<para>It's customary to have a conclusions slide.</para>
+
+</foil>
+
+<foil><title>References</title>
+
+<para>References are a good idea too.</para>
+
+</foil>
+
+<foil><title>Q&amp;A</title>
+
+<para>Any questions?</para>
+
+</foil>
+</foilgroup>
+
+</slides>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.xsl b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.xsl
new file mode 100644
index 00000000000..bb06cef611c
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/sample_foiltex/slides.xsl
@@ -0,0 +1,158 @@
+<?xml version='1.0'?>
+<!--############################################################################# 
+ |	$Id: slides.xsl,v 1.1 2003/07/22 07:12:13 rcasellas Exp $
+ |- #############################################################################
+ |	$Author: rcasellas $												
+ |														
+ + ############################################################################## -->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'>
+
+<xsl:import href="../slides.xsl"/>
+
+    <xsl:variable name="db2latex.slides.packages">
+    	<xsl:text>\usepackage[latin1]{inputenc}&#10;</xsl:text>
+    	<xsl:text>\usepackage{pstricks,pst-node,pst-text,pst-3d}&#10;</xsl:text>
+    	<xsl:text>\usepackage{subfigure}&#10;</xsl:text>
+    	<xsl:text>\usepackage{fancybox}&#10;</xsl:text>
+    	<xsl:text>\usepackage{a4wide}&#10;</xsl:text>
+    	<xsl:text>\usepackage{times}&#10;</xsl:text>
+    	<xsl:text>\usepackage{fancyvrb}&#10;</xsl:text>
+    	<xsl:text>\usepackage{amsmath,amsthm, amsfonts, amssymb, amsxtra,amsopn}&#10;</xsl:text>
+		<xsl:text>\usepackage{anysize}&#10;</xsl:text>
+		<xsl:text>\usepackage[pdftex,bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, </xsl:text>
+		<xsl:text>linktocpage,hyperfigures,hyperindex,citecolor=blue,urlcolor=blue]{hyperref}&#10;</xsl:text>
+		<xsl:text>\usepackage[english]{babel}&#10;</xsl:text>
+		<xsl:text>\usepackage[pdftex]{graphicx}&#10;</xsl:text>
+
+	</xsl:variable>
+
+	
+
+    <xsl:variable name="db2latex.slides.optpackages"/>
+
+
+    <xsl:variable name="db2latex.slides.beforebegin">
+		<xsl:text>\pdfcompresslevel=9&#10;</xsl:text>
+		<xsl:text>%------------------------------------------------------- Values and counters&#10;</xsl:text>
+		<xsl:text>\marginsize{1.5cm}{1.5cm}{0.5cm}{0.5cm}&#10;</xsl:text>
+		<xsl:text>\renewcommand\floatpagefraction{.9}&#10;</xsl:text>
+		<xsl:text>\renewcommand\topfraction{.9}&#10;</xsl:text>
+		<xsl:text>\renewcommand\bottomfraction{.9}&#10;</xsl:text>
+		<xsl:text>\renewcommand\textfraction{.1}&#10;</xsl:text>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>\usepackage[usenames,pdftex]{color}&#10;</xsl:text>
+		<xsl:text>%------------------------------------------------------- BfBlue Command&#10;</xsl:text>
+		<xsl:text>\newcommand{\bfblue}[1]{ \textcolor{blue}{\bf #1} }&#10;</xsl:text>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>%------------------------------------------------------- BfGreen Command&#10;</xsl:text>
+		<xsl:text>\newcommand{\bfgreen}[1]{ \textcolor{blue}{\bf #1} }&#10;</xsl:text>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>%------------------------------------------------------- BfRed Command&#10;</xsl:text>
+		<xsl:text>\newcommand{\bfred}[1]{ \textcolor{red}{\bf #1} }&#10;</xsl:text>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>%------------------------------------------------------- BfBlue Command&#10;</xsl:text>
+		<xsl:text>\newcommand{\emblue}[1]{ \textcolor{blue}{\emph{#1}} }&#10;</xsl:text>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>%------------------------------------------------------- BfGreen Command&#10;</xsl:text>
+		<xsl:text>\newcommand{\emgreen}[1]{ \textcolor{blue}{\emph{#1}} }&#10;</xsl:text>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>%------------------------------------------------------- BfRed Command&#10;</xsl:text>
+		<xsl:text>\newcommand{\emred}[1]{ \textcolor{red}{\emph{#1}} }&#10;</xsl:text>
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>%------------------------------------------------------- Part Command&#10;</xsl:text>
+		<xsl:text>\newcommand{\part}[1]{&#10;</xsl:text>
+		<xsl:text>\foilhead{}&#10;</xsl:text>
+		<xsl:text>\vspace{2cm}&#10;</xsl:text>
+		<xsl:text>\begin{center}&#10;</xsl:text>
+		<xsl:text>\Huge{\textcolor{blue}{#1}}&#10;</xsl:text>
+		<xsl:text>\end{center}}&#10;</xsl:text>
+		<xsl:text> \newcommand{\dbz}{} &#10;</xsl:text>
+		<xsl:text>%------------------------------------------------------- Slide Command&#10;</xsl:text>
+		<xsl:text>\newcommand{\slide}[1]{&#10;</xsl:text>
+		<xsl:text>\foilhead[-0.5in]{\large{\textcolor{blue}{#1}}}&#10;</xsl:text>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:text>\newcommand{\id}[1]{&#10;</xsl:text>
+		<xsl:text>\label{#1}&#10;</xsl:text>
+		<xsl:text>\hypertarget{#1}{}&#10;</xsl:text>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:text>% --------------------------------------------&#10;</xsl:text>
+		<xsl:text>\newenvironment{admminipage}{&#10;</xsl:text>
+		<xsl:text>\begin{Sbox}&#10;</xsl:text>
+		<xsl:text>\begin{minipage}&#10;</xsl:text>
+		<xsl:text>}{&#10;</xsl:text>
+		<xsl:text>\end{minipage}&#10;</xsl:text>
+		<xsl:text>\end{Sbox}&#10;</xsl:text>
+		<xsl:text>\fbox{\TheSbox}&#10;</xsl:text>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:text>\newlength{\admlength}&#10;</xsl:text>
+		<xsl:text>\newenvironment{admonition}[2] {&#10;</xsl:text>
+		<xsl:text>\hspace{0mm}\newline\hspace*\fill\newline&#10;</xsl:text>
+		<xsl:text>\noindent&#10;</xsl:text>
+		<xsl:text>\setlength{\fboxsep}{5pt}&#10;</xsl:text>
+		<xsl:text>\setlength{\admlength}{\linewidth}&#10;</xsl:text>
+		<xsl:text>\addtolength{\admlength}{-10\fboxsep}&#10;</xsl:text>
+		<xsl:text>\addtolength{\admlength}{-10\fboxrule}&#10;</xsl:text>
+		<xsl:text>\admminipage{\admlength}&#10;</xsl:text>
+		<xsl:text>\bfblue{\sc\large{#2}}\newline&#10;</xsl:text>
+		<xsl:text>\\[1mm]&#10;</xsl:text>
+		<xsl:text>%\sffamily&#10;</xsl:text>
+		<xsl:text>\includegraphics[width=1cm]{#1}&#10;</xsl:text>
+		<xsl:text>\addtolength{\admlength}{-1cm}&#10;</xsl:text>
+		<xsl:text>\addtolength{\admlength}{-20pt}&#10;</xsl:text>
+		<xsl:text>\begin{minipage}[lt]{\admlength}&#10;</xsl:text>
+		<xsl:text>\parskip=0.5\baselineskip \advance\parskip by 0pt plus 2pt&#10;</xsl:text>
+		<xsl:text>}{&#10;</xsl:text>
+		<xsl:text>\vspace{5mm}&#10;</xsl:text>
+		<xsl:text>\end{minipage}&#10;</xsl:text>
+		<xsl:text>\endadmminipage&#10;</xsl:text>
+		<xsl:text>\vspace{.5em}&#10;</xsl:text>
+		<xsl:text>\par&#10;</xsl:text>
+		<xsl:text>}&#10;</xsl:text>
+
+    </xsl:variable>
+
+
+
+    <xsl:template match="slides">
+<!-- Document class and preamble -->
+    <xsl:text>\documentclass[17pt,headrule,footrule,landscape]{foils}&#10;</xsl:text>
+    <xsl:value-of select="$db2latex.slides.packages"/>
+    <xsl:value-of select="$db2latex.slides.beforebegin"/>
+<!-- Process SlidesInfo -->
+    <xsl:apply-templates select="slidesinfo"/>
+    <xsl:text>\begin{document}&#10;</xsl:text>
+    <xsl:text>\maketitle&#10;</xsl:text>
+<!-- Process Everything except SlidesInfo -->
+    <xsl:apply-templates select="*[not(slidesinfo)]"/>
+<!-- <xsl:apply-templates select="foil|foilgroup"/> -->
+    <xsl:text>\end{document}&#10;</xsl:text>
+    </xsl:template>
+
+
+<xsl:template match="slidesinfo">
+<xsl:text>%--------------------------------------------------SLIDES INFORMATION&#10;</xsl:text>
+<xsl:text>\title{{\black </xsl:text>
+<xsl:apply-templates select="title"/>
+<xsl:text>}}&#10;</xsl:text>
+<xsl:text>\author{{\black </xsl:text>
+<xsl:apply-templates select="author|authorgroup"/>
+<xsl:text>}}&#10;</xsl:text>
+<xsl:text> </xsl:text>
+</xsl:template>
+
+
+
+<xsl:output method="text" encoding="ISO-8859-1" indent="yes"/>
+<xsl:variable name="latex.use.babel">1</xsl:variable>
+<xsl:variable name="latex.use.fancyvrb">1</xsl:variable>
+<xsl:variable name="latex.use.fancybox">1</xsl:variable>
+<xsl:variable name="latex.use.fancyhdr">1</xsl:variable>
+<xsl:variable name="latex.use.subfigure">1</xsl:variable>
+<xsl:variable name="latex.use.rotating">1</xsl:variable>
+<xsl:variable name="latex.use.makeidx">1</xsl:variable>
+<xsl:variable name="latex.pdf.support">1</xsl:variable>
+<xsl:variable name="latex.math.support">1</xsl:variable>
+
+<xsl:variable name="latex.biblio.output">all</xsl:variable>
+<xsl:variable name="latex.document.font">default</xsl:variable>
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/slides.xsl b/docs-xml/xslt/db2latex-xsl/xsl/slides/slides.xsl
new file mode 100644
index 00000000000..52446153b52
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/slides.xsl
@@ -0,0 +1,96 @@
+<?xml version='1.0'?>
+<!--############################################################################# 
+|	$Id: slides.xsl,v 1.2 2003/04/07 08:40:23 rcasellas Exp $		
+|- #############################################################################
+|	$Author: rcasellas $												
+|														
+|   PURPOSE: 
+| 	This is the "parent" stylesheet. The used "modules" are included here.
+|	output encoding text in ISO-8859-1 indented.
++ ############################################################################## -->
+
+<xsl:stylesheet 
+    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+    xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+    exclude-result-prefixes="doc" version='1.0'>
+
+    <xsl:include href="../docbook.xsl"/>
+    <xsl:output method="text" encoding="ISO-8859-1" indent="yes"/>
+    <xsl:include href="slidesinfo.mod.xsl"/>
+    <xsl:include href="slidestoc.mod.xsl"/>
+    <xsl:include href="foil.mod.xsl"/>
+
+
+    <xsl:template match="/">
+	<xsl:variable name="xsl-vendor" select="system-property('xsl:vendor')"/>
+	<xsl:message>################################################################################</xsl:message>
+	<xsl:message> XSLT stylesheets DocBook - LaTeX 2e                                            </xsl:message>
+	<xsl:message> SLIDES DTD                                                                     </xsl:message>
+	<xsl:message> Reqs: LaTeX 2e installation common packages                                    </xsl:message>
+	<xsl:message>################################################################################</xsl:message>
+	<xsl:message> RELEASE : <xsl:value-of select="$VERSION"/>                                    </xsl:message>
+	<xsl:message> VERSION : <xsl:value-of select="$CVSVERSION"/>                                 </xsl:message>
+	<xsl:message>     TAG : <xsl:value-of select="$TAG"/>                                        </xsl:message>
+	<xsl:message>     WWW : http://db2latex.sourceforge.net                                      </xsl:message>
+	<xsl:message> SUMMARY : http://www.sourceforge.net/projects/db2latex                         </xsl:message>
+	<xsl:message>  AUTHOR : Ramon Casellas   casellas@infres.enst.fr                             </xsl:message>
+	<xsl:message>  AUTHOR : James Devenish   j-devenish@users.sf.net                             </xsl:message>
+	<xsl:message>   USING : <xsl:call-template name="set-vendor"/>                               </xsl:message>
+	<xsl:message><xsl:value-of select="$xsl-vendor"/>                                            </xsl:message>
+	<xsl:message>################################################################################</xsl:message>
+	<xsl:apply-templates/>
+    </xsl:template>
+
+
+
+
+	<xsl:param name="db2latex.slides.class" select="'prosper'"/>
+
+	<xsl:param name="db2latex.slides.customclass" select="'rcas'"/>
+
+	<xsl:param name="db2latex.slides.options" select="'pdf,frames,slideColor'"/>
+
+	<xsl:variable name="db2latex.slides.packages">
+	<xsl:text>\usepackage[latin1]{inputenc}&#10;</xsl:text>
+	<xsl:text>\usepackage{pstricks,pst-node,pst-text,pst-3d}&#10;</xsl:text>
+	</xsl:variable>
+
+	<xsl:variable name="db2latex.slides.optpackages">
+	<xsl:text>\usepackage{subfigure}&#10;</xsl:text>
+	<xsl:text>\usepackage{a4wide}&#10;</xsl:text>
+	<xsl:text>\usepackage{times}&#10;</xsl:text>
+	<xsl:text>\usepackage{fancyvrb}&#10;</xsl:text>
+	<xsl:text>\usepackage{amsmath,amsthm, amsfonts, amssymb, amsxtra,amsopn}&#10;</xsl:text>
+	</xsl:variable>
+
+	<xsl:variable name="db2latex.slides.beforebegin">
+	<xsl:text>% Definition of new colors&#10;</xsl:text>
+	<xsl:text>\newrgbcolor{LemonChiffon}{1. 0.98 0.8}&#10;</xsl:text>
+	<xsl:text>\newrgbcolor{LightBlue}{0.68 0.85 0.9}&#10;</xsl:text>
+	<xsl:text>\hypersetup{pdfpagemode=FullScreen}&#10;</xsl:text>
+	<xsl:text>\makeatletter&#10;</xsl:text>
+	<xsl:text>%\newdimen\pst@dimz&#10;</xsl:text>
+	</xsl:variable>
+
+
+    <xsl:template match="slides">
+<!-- Document class and preamble -->
+	<xsl:text>\documentclass[</xsl:text><xsl:value-of select="$db2latex.slides.options"/>
+	<xsl:text>, </xsl:text><xsl:value-of select="$db2latex.slides.customclass"/>
+	<xsl:text>]{</xsl:text><xsl:value-of select="$db2latex.slides.class"/>
+	<xsl:text>}&#10;</xsl:text>
+	<xsl:value-of select="$db2latex.slides.packages"/>
+	<xsl:value-of select="$db2latex.slides.optpackages"/>
+	<xsl:value-of select="$db2latex.slides.beforebegin"/>
+<!-- Process SlidesInfo -->
+	<xsl:apply-templates select="slidesinfo"/>
+	<xsl:text>\begin{document}&#10;</xsl:text>
+	<xsl:text>\maketitle&#10;</xsl:text>
+<!-- Process Everything except SlidesInfo -->
+	<xsl:apply-templates select="*[not(slidesinfo)]"/>
+<!-- <xsl:apply-templates select="foil|foilgroup"/> -->
+	<xsl:text>\end{document}&#10;</xsl:text>
+    </xsl:template>
+
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/slidesinfo.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/slides/slidesinfo.mod.xsl
new file mode 100644
index 00000000000..176f852793c
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/slidesinfo.mod.xsl
@@ -0,0 +1,61 @@
+<?xml version='1.0'?>
+<!--############################################################################# 
+|	$Id: slidesinfo.mod.xsl,v 1.2 2003/07/22 07:12:13 rcasellas Exp $
+|- #############################################################################
+|	$Author: rcasellas $
+|														
+|   PURPOSE:
++ ############################################################################## -->
+
+<xsl:stylesheet 
+    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+    xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+    exclude-result-prefixes="doc" version='1.0'>
+
+
+
+<xsl:template match="slidesinfo">
+<xsl:text>%--------------------------------------------------SLIDES INFORMATION&#10;</xsl:text>
+<xsl:text>\title{{\black </xsl:text>
+<xsl:apply-templates select="title"/>
+<xsl:text>}}&#10;</xsl:text>
+<xsl:text>\subtitle{{\black </xsl:text>
+<xsl:apply-templates select="titleabbrev"/>
+<xsl:text>}}&#10;</xsl:text>
+<xsl:text>\author{{\black </xsl:text>
+<xsl:apply-templates select="author|authorgroup"/>
+<xsl:text>}}&#10;</xsl:text>
+<xsl:text>
+</xsl:text>
+<xsl:text>\renewcommand{\slideparindent}{0mm}&#10;</xsl:text>
+</xsl:template>
+
+
+
+
+<xsl:template match="slidesinfo/title|slidesinfo/titleabbrev">
+<xsl:apply-templates/>
+</xsl:template>
+
+
+<xsl:template match="slidesinfo/authorgroup">
+<xsl:apply-imports/>
+</xsl:template>
+
+<xsl:template match="slidesinfo/author|slidesinfo/authorgroup/author">
+<xsl:apply-imports/>
+</xsl:template>
+
+<xsl:template match="slidesinfo/releaseinfo">
+<xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="slidesinfo/date">
+<xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="slidesinfo/copyright">
+</xsl:template>
+
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/slides/slidestoc.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/slides/slidestoc.mod.xsl
new file mode 100644
index 00000000000..5390d319bfd
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/slides/slidestoc.mod.xsl
@@ -0,0 +1,34 @@
+<?xml version='1.0'?>
+<!--############################################################################# 
+|	$Id: slidestoc.mod.xsl,v 1.1 2003/04/06 18:31:49 rcasellas Exp $
+|- #############################################################################
+|	$Author: rcasellas $
+|														
+|   PURPOSE:
++ ############################################################################## -->
+
+<xsl:stylesheet 
+    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+    xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+    exclude-result-prefixes="doc" version='1.0'>
+
+
+    <!--############################################################################# -->
+    <!-- DOCUMENTATION                                                                -->
+    <doc:reference id="slides" xmlns="">
+    </doc:reference>
+    <!--############################################################################# -->
+
+
+<xsl:template match="slides" mode="toc">
+<xsl:call-template name="label.id"/>
+</xsl:template>
+
+<xsl:template match="title|titleabbrev" mode="toc">
+  <xsl:apply-templates mode="toc"/>
+</xsl:template>
+
+<xsl:template match="speakernotes" mode="toc">
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/synop-oop.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/synop-oop.mod.xsl
new file mode 100644
index 00000000000..0ae6e8e8bc7
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/synop-oop.mod.xsl
@@ -0,0 +1,691 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY RE "&#10;"> ]>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'>
+    <!--############################################################################# 
+    |	$Id: synop-oop.mod.xsl,v 1.1.1.1 2003/03/14 10:42:53 rcasellas Exp $
+    |- #############################################################################
+    |	$Author: rcasellas $
+    |														
+    |   PURPOSE:
+    + ############################################################################## -->
+
+
+
+    <xsl:template match="classsynopsis">
+	<!-- PARAM language : -->
+	<xsl:param name="language">
+	    <xsl:choose>
+		<xsl:when test="@language">
+		    <xsl:value-of select="@language"/>
+		</xsl:when>
+		<xsl:otherwise>
+		    <xsl:value-of select="$default-classsynopsis-language"/>
+		</xsl:otherwise>
+	    </xsl:choose>
+	</xsl:param>
+
+	<xsl:choose>
+	    <xsl:when test="$language='java'"> <xsl:apply-templates select="." mode="java"/> </xsl:when>
+	    <xsl:when test="$language='perl'"> <xsl:apply-templates select="." mode="perl"/> </xsl:when>
+	    <xsl:when test="$language='idl'">  <xsl:apply-templates select="." mode="idl"/>  </xsl:when>
+	    <xsl:when test="$language='cpp'">  <xsl:apply-templates select="." mode="cpp"/>  </xsl:when>
+	    <xsl:otherwise>
+		<xsl:message>Unrecognized language on classsynopsis: <xsl:value-of select="$language"/> </xsl:message>
+		<xsl:apply-templates select=".">
+		    <xsl:with-param name="language"  select="$default-classsynopsis-language"/>
+		</xsl:apply-templates>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+
+
+
+
+    <!-- ===== Java ======================================================== -->
+
+    <xsl:template match="classsynopsis" mode="java">
+	<pre class="{name(.)}">
+	    <xsl:apply-templates select="ooclass[1]" mode="java"/>
+	    <xsl:if test="ooclass[position() &gt; 1]">
+		<xsl:text> extends</xsl:text>
+		<xsl:apply-templates select="ooclass[position() &gt; 1]" mode="java"/>
+		<xsl:if test="oointerface|ooexception">
+		    <xsl:text>&RE;    </xsl:text>
+		</xsl:if>
+	    </xsl:if>
+	    <xsl:if test="oointerface">
+		<xsl:text>implements</xsl:text>
+		<xsl:apply-templates select="oointerface" mode="java"/>
+		<xsl:if test="ooexception">
+		    <xsl:text>&RE;    </xsl:text>
+		</xsl:if>
+	    </xsl:if>
+	    <xsl:if test="ooexception">
+		<xsl:text>throws</xsl:text>
+		<xsl:apply-templates select="ooexception" mode="java"/>
+	    </xsl:if>
+	    <xsl:text> {&RE;&RE;</xsl:text>
+	    <xsl:apply-templates select="constructorsynopsis
+		|destructorsynopsis
+		|fieldsynopsis
+		|methodsynopsis
+		|classsynopsisinfo" mode="java"/>
+	    <xsl:text>}</xsl:text>
+	</pre>
+    </xsl:template>
+
+    <xsl:template match="classsynopsisinfo" mode="java">
+	<xsl:apply-templates mode="java"/>
+    </xsl:template>
+
+    <xsl:template match="ooclass|oointerface|ooexception" mode="java">
+	<xsl:choose>
+	    <xsl:when test="position() &gt; 1">
+		<xsl:text>, </xsl:text>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:text> </xsl:text>
+	    </xsl:otherwise>
+	</xsl:choose>
+
+	<xsl:apply-templates mode="java"/>
+
+    </xsl:template>
+
+    <xsl:template match="modifier" mode="java">
+
+	<xsl:apply-templates mode="java"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="classname" mode="java">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'classname'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="java"/>
+
+    </xsl:template>
+
+    <xsl:template match="interfacename" mode="java">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'interfacename'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="java"/>
+
+    </xsl:template>
+
+    <xsl:template match="exceptionname" mode="java">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'exceptionname'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="java"/>
+
+    </xsl:template>
+
+    <xsl:template match="fieldsynopsis" mode="java">
+
+	<xsl:text>  </xsl:text>
+	<xsl:apply-templates mode="java"/>
+	<xsl:text>;</xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="type" mode="java">
+
+	<xsl:apply-templates mode="java"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="varname" mode="java">
+
+	<xsl:apply-templates mode="java"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="initializer" mode="java">
+
+	<xsl:text>= </xsl:text>
+	<xsl:apply-templates mode="java"/>
+
+    </xsl:template>
+
+    <xsl:template match="void" mode="java">
+
+	<xsl:text>void </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="methodname" mode="java">
+
+	<xsl:apply-templates mode="java"/>
+    </xsl:template>
+
+
+
+
+    <xsl:template match="methodparam" mode="java">
+	<!-- PARAM: indent := 0 -->
+	<xsl:param name="indent">0</xsl:param>
+	<xsl:if test="position() &gt; 1">
+	    <xsl:text>,&RE;</xsl:text>
+	    <xsl:if test="$indent &gt; 0">
+		<!-- RCAS FIXME: copy-string does not exist
+		<xsl:call-template name="copy-string">
+		    <xsl:with-param name="string"> </xsl:with-param>
+		    <xsl:with-param name="count" select="$indent + 1"/>
+		</xsl:call-template>
+		-->
+	    </xsl:if>
+	</xsl:if>
+	<xsl:apply-templates mode="java"/>
+    </xsl:template>
+
+
+
+    <xsl:template match="parameter" mode="java">
+	<xsl:apply-templates mode="java"/>
+    </xsl:template>
+
+    <xsl:template mode="java"
+	match="constructorsynopsis|destructorsynopsis|methodsynopsis">
+	<xsl:variable name="modifiers" select="modifier"/>
+	<xsl:variable name="notmod" select="*[name(.) != 'modifier']"/>
+	<xsl:variable name="decl">
+	    <xsl:text>  </xsl:text>
+	    <xsl:apply-templates select="$modifiers" mode="java"/>
+
+	    <!-- type -->
+	    <xsl:if test="name($notmod[1]) != 'methodname'">
+		<xsl:apply-templates select="$notmod[1]" mode="java"/>
+	    </xsl:if>
+
+	    <xsl:apply-templates select="methodname" mode="java"/>
+	</xsl:variable>
+
+
+	<xsl:copy-of select="$decl"/>
+	<xsl:text>(</xsl:text>
+	<xsl:apply-templates select="methodparam" mode="java">
+	    <xsl:with-param name="indent" select="string-length($decl)"/>
+	</xsl:apply-templates>
+	<xsl:text>)</xsl:text>
+	<xsl:if test="exceptionname">
+	    <xsl:text>&RE;    throws </xsl:text>
+	    <xsl:apply-templates select="exceptionname" mode="java"/>
+	</xsl:if>
+	<xsl:text>;</xsl:text>
+
+    </xsl:template>
+
+    <!-- ===== C++ ========================================================= -->
+
+    <xsl:template match="classsynopsis" mode="cpp">
+	<pre class="{name(.)}">
+	    <xsl:apply-templates select="ooclass[1]" mode="cpp"/>
+	    <xsl:if test="ooclass[position() &gt; 1]">
+		<xsl:text>: </xsl:text>
+		<xsl:apply-templates select="ooclass[position() &gt; 1]" mode="cpp"/>
+		<xsl:if test="oointerface|ooexception">
+		    <xsl:text>&RE;    </xsl:text>
+		</xsl:if>
+	    </xsl:if>
+	    <xsl:if test="oointerface">
+		<xsl:text> implements</xsl:text>
+		<xsl:apply-templates select="oointerface" mode="cpp"/>
+		<xsl:if test="ooexception">
+		    <xsl:text>&RE;    </xsl:text>
+		</xsl:if>
+	    </xsl:if>
+	    <xsl:if test="ooexception">
+		<xsl:text> throws</xsl:text>
+		<xsl:apply-templates select="ooexception" mode="cpp"/>
+	    </xsl:if>
+	    <xsl:text> {&RE;&RE;</xsl:text>
+	    <xsl:apply-templates select="constructorsynopsis
+		|destructorsynopsis
+		|fieldsynopsis
+		|methodsynopsis
+		|classsynopsisinfo" mode="cpp"/>
+	    <xsl:text>}</xsl:text>
+	</pre>
+    </xsl:template>
+
+    <xsl:template match="classsynopsisinfo" mode="cpp">
+	<xsl:apply-templates mode="cpp"/>
+    </xsl:template>
+
+    <xsl:template match="ooclass|oointerface|ooexception" mode="cpp">
+	<xsl:if test="position() &gt; 1">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="cpp"/>
+
+    </xsl:template>
+
+    <xsl:template match="modifier" mode="cpp">
+
+	<xsl:apply-templates mode="cpp"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="classname" mode="cpp">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'classname'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="cpp"/>
+
+    </xsl:template>
+
+    <xsl:template match="interfacename" mode="cpp">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'interfacename'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="cpp"/>
+
+    </xsl:template>
+
+    <xsl:template match="exceptionname" mode="cpp">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'exceptionname'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="cpp"/>
+
+    </xsl:template>
+
+    <xsl:template match="fieldsynopsis" mode="cpp">
+
+	<xsl:text>  </xsl:text>
+	<xsl:apply-templates mode="cpp"/>
+	<xsl:text>;</xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="type" mode="cpp">
+
+	<xsl:apply-templates mode="cpp"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="varname" mode="cpp">
+
+	<xsl:apply-templates mode="cpp"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="initializer" mode="cpp">
+
+	<xsl:text>= </xsl:text>
+	<xsl:apply-templates mode="cpp"/>
+
+    </xsl:template>
+
+    <xsl:template match="void" mode="cpp">
+
+	<xsl:text>void </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="methodname" mode="cpp">
+
+	<xsl:apply-templates mode="cpp"/>
+
+    </xsl:template>
+
+    <xsl:template match="methodparam" mode="cpp">
+	<xsl:if test="position() &gt; 1">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="cpp"/>
+
+    </xsl:template>
+
+    <xsl:template match="parameter" mode="cpp">
+
+	<xsl:apply-templates mode="cpp"/>
+
+    </xsl:template>
+
+    <xsl:template mode="cpp"
+	match="constructorsynopsis|destructorsynopsis|methodsynopsis">
+	<xsl:variable name="modifiers" select="modifier"/>
+	<xsl:variable name="notmod" select="*[name(.) != 'modifier']"/>
+	<xsl:variable name="type">
+	</xsl:variable>
+
+	<xsl:text>  </xsl:text>
+	<xsl:apply-templates select="$modifiers" mode="cpp"/>
+
+	<!-- type -->
+	<xsl:if test="name($notmod[1]) != 'methodname'">
+	    <xsl:apply-templates select="$notmod[1]" mode="cpp"/>
+	</xsl:if>
+
+	<xsl:apply-templates select="methodname" mode="cpp"/>
+	<xsl:text>(</xsl:text>
+	<xsl:apply-templates select="methodparam" mode="cpp"/>
+	<xsl:text>)</xsl:text>
+	<xsl:if test="exceptionname">
+	    <xsl:text>&RE;    throws </xsl:text>
+	    <xsl:apply-templates select="exceptionname" mode="cpp"/>
+	</xsl:if>
+	<xsl:text>;</xsl:text>
+
+    </xsl:template>
+
+    <!-- ===== IDL ========================================================= -->
+
+    <xsl:template match="classsynopsis" mode="idl">
+	<pre class="{name(.)}">
+	    <xsl:text>interface </xsl:text>
+	    <xsl:apply-templates select="ooclass[1]" mode="idl"/>
+	    <xsl:if test="ooclass[position() &gt; 1]">
+		<xsl:text>: </xsl:text>
+		<xsl:apply-templates select="ooclass[position() &gt; 1]" mode="idl"/>
+		<xsl:if test="oointerface|ooexception">
+		    <xsl:text>&RE;    </xsl:text>
+		</xsl:if>
+	    </xsl:if>
+	    <xsl:if test="oointerface">
+		<xsl:text> implements</xsl:text>
+		<xsl:apply-templates select="oointerface" mode="idl"/>
+		<xsl:if test="ooexception">
+		    <xsl:text>&RE;    </xsl:text>
+		</xsl:if>
+	    </xsl:if>
+	    <xsl:if test="ooexception">
+		<xsl:text> throws</xsl:text>
+		<xsl:apply-templates select="ooexception" mode="idl"/>
+	    </xsl:if>
+	    <xsl:text> {&RE;&RE;</xsl:text>
+	    <xsl:apply-templates select="constructorsynopsis
+		|destructorsynopsis
+		|fieldsynopsis
+		|methodsynopsis
+		|classsynopsisinfo" mode="idl"/>
+	    <xsl:text>}</xsl:text>
+	</pre>
+    </xsl:template>
+
+    <xsl:template match="classsynopsisinfo" mode="idl">
+	<xsl:apply-templates mode="idl"/>
+    </xsl:template>
+
+    <xsl:template match="ooclass|oointerface|ooexception" mode="idl">
+	<xsl:if test="position() &gt; 1">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="idl"/>
+
+    </xsl:template>
+
+    <xsl:template match="modifier" mode="idl">
+
+	<xsl:apply-templates mode="idl"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="classname" mode="idl">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'classname'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="idl"/>
+
+    </xsl:template>
+
+    <xsl:template match="interfacename" mode="idl">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'interfacename'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="idl"/>
+
+    </xsl:template>
+
+    <xsl:template match="exceptionname" mode="idl">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'exceptionname'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="idl"/>
+
+    </xsl:template>
+
+    <xsl:template match="fieldsynopsis" mode="idl">
+
+	<xsl:text>  </xsl:text>
+	<xsl:apply-templates mode="idl"/>
+	<xsl:text>;</xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="type" mode="idl">
+
+	<xsl:apply-templates mode="idl"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="varname" mode="idl">
+
+	<xsl:apply-templates mode="idl"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="initializer" mode="idl">
+
+	<xsl:text>= </xsl:text>
+	<xsl:apply-templates mode="idl"/>
+
+    </xsl:template>
+
+    <xsl:template match="void" mode="idl">
+
+	<xsl:text>void </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="methodname" mode="idl">
+
+	<xsl:apply-templates mode="idl"/>
+
+    </xsl:template>
+
+    <xsl:template match="methodparam" mode="idl">
+	<xsl:if test="position() &gt; 1">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="idl"/>
+
+    </xsl:template>
+
+    <xsl:template match="parameter" mode="idl">
+
+	<xsl:apply-templates mode="idl"/>
+
+    </xsl:template>
+
+    <xsl:template mode="idl"
+	match="constructorsynopsis|destructorsynopsis|methodsynopsis">
+	<xsl:variable name="modifiers" select="modifier"/>
+	<xsl:variable name="notmod" select="*[name(.) != 'modifier']"/>
+	<xsl:variable name="type">
+	</xsl:variable>
+
+	<xsl:text>  </xsl:text>
+	<xsl:apply-templates select="$modifiers" mode="idl"/>
+
+	<!-- type -->
+	<xsl:if test="name($notmod[1]) != 'methodname'">
+	    <xsl:apply-templates select="$notmod[1]" mode="idl"/>
+	</xsl:if>
+
+	<xsl:apply-templates select="methodname" mode="idl"/>
+	<xsl:text>(</xsl:text>
+	<xsl:apply-templates select="methodparam" mode="idl"/>
+	<xsl:text>)</xsl:text>
+	<xsl:if test="exceptionname">
+	    <xsl:text>&RE;    raises(</xsl:text>
+	    <xsl:apply-templates select="exceptionname" mode="idl"/>
+	    <xsl:text>)</xsl:text>
+	</xsl:if>
+	<xsl:text>;</xsl:text>
+
+    </xsl:template>
+
+
+
+
+
+    <!-- ===== Perl ======================================================== -->
+
+    <xsl:template match="classsynopsis" mode="perl">
+	<pre class="{name(.)}">
+	    <xsl:text>package </xsl:text>
+	    <xsl:apply-templates select="ooclass[1]" mode="perl"/>
+	    <xsl:text>;&RE;</xsl:text>
+
+	    <xsl:if test="ooclass[position() &gt; 1]">
+		<xsl:text>@ISA = (</xsl:text>
+		<xsl:apply-templates select="ooclass[position() &gt; 1]" mode="perl"/>
+		<xsl:text>);&RE;</xsl:text>
+	    </xsl:if>
+
+	    <xsl:apply-templates select="constructorsynopsis
+		|destructorsynopsis
+		|fieldsynopsis
+		|methodsynopsis
+		|classsynopsisinfo" mode="perl"/>
+	</pre>
+    </xsl:template>
+
+    <xsl:template match="classsynopsisinfo" mode="perl">
+	<xsl:apply-templates mode="perl"/>
+    </xsl:template>
+
+    <xsl:template match="ooclass|oointerface|ooexception" mode="perl">
+	<xsl:if test="position() &gt; 1">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="perl"/>
+
+    </xsl:template>
+
+    <xsl:template match="modifier" mode="perl">
+
+	<xsl:apply-templates mode="perl"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="classname" mode="perl">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'classname'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="perl"/>
+
+    </xsl:template>
+
+    <xsl:template match="interfacename" mode="perl">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'interfacename'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="perl"/>
+
+    </xsl:template>
+
+    <xsl:template match="exceptionname" mode="perl">
+	<xsl:if test="name(preceding-sibling::*[1]) = 'exceptionname'">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+
+	<xsl:apply-templates mode="perl"/>
+
+    </xsl:template>
+
+    <xsl:template match="fieldsynopsis" mode="perl">
+
+	<xsl:text>  </xsl:text>
+	<xsl:apply-templates mode="perl"/>
+	<xsl:text>;</xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="type" mode="perl">
+
+	<xsl:apply-templates mode="perl"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="varname" mode="perl">
+
+	<xsl:apply-templates mode="perl"/>
+	<xsl:text> </xsl:text>
+
+    </xsl:template>
+
+    <xsl:template match="initializer" mode="perl">
+
+	<xsl:text>= </xsl:text>
+	<xsl:apply-templates mode="perl"/>
+
+    </xsl:template>
+
+    <xsl:template match="void" mode="perl">
+
+	<xsl:text>void </xsl:text>
+
+    </xsl:template>
+
+
+
+    <xsl:template match="methodname" mode="perl">
+	<xsl:apply-templates mode="perl"/>
+    </xsl:template>
+
+    <xsl:template match="methodparam" mode="perl">
+	<xsl:if test="position() &gt; 1"> <xsl:text>, </xsl:text> </xsl:if>
+	<xsl:apply-templates mode="perl"/>
+    </xsl:template>
+
+
+    <xsl:template match="parameter" mode="perl">
+	<xsl:apply-templates mode="perl"/>
+    </xsl:template>
+
+
+    <xsl:template mode="perl" match="constructorsynopsis|destructorsynopsis|methodsynopsis">
+	<xsl:variable name="modifiers" select="modifier"/>
+	<xsl:variable name="notmod" select="*[name(.) != 'modifier']"/>
+	<xsl:variable name="type"> </xsl:variable>
+
+	<xsl:text>sub </xsl:text>
+
+	<xsl:apply-templates select="methodname" mode="perl"/>
+	<xsl:text> { ... };</xsl:text>
+    </xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/synop-struct.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/synop-struct.mod.xsl
new file mode 100644
index 00000000000..1b97f288e40
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/synop-struct.mod.xsl
@@ -0,0 +1,248 @@
+<?xml version='1.0'?>
+<!--############################################################################# 
+|	$Id: synop-struct.mod.xsl,v 1.5 2003/10/19 07:56:56 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
+|														
+|   PURPOSE:
++ ############################################################################## -->
+
+<xsl:stylesheet 
+    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+    xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+    exclude-result-prefixes="doc" version='1.0'>
+
+	<xsl:template match="synopsis">
+	<xsl:call-template name="label.id"/>
+	<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="cmdsynopsis">
+	<xsl:call-template name="label.id"/>
+	<xsl:text>&#10;\begin{list}{}{\setlength{\itemindent}{-\leftmargin}\setlength{\parsep}{0mm}}&#10;</xsl:text>
+	<xsl:if test="@label!=''">
+		<xsl:text>\item\textbf{</xsl:text>
+		<xsl:call-template name="normalize-scape"><xsl:with-param name="string" select="@label"/></xsl:call-template>
+		<xsl:text>}&#10;</xsl:text>
+	</xsl:if>
+	<xsl:text>\item\raggedright\texttt{</xsl:text>
+	<xsl:apply-templates/>
+	<xsl:text>}&#10;</xsl:text>
+	<xsl:text>\end{list}&#10;</xsl:text>
+	</xsl:template>
+
+
+	<xsl:template match="cmdsynopsis/command">
+	<xsl:apply-templates />
+	</xsl:template>
+
+
+	<xsl:template match="cmdsynopsis//replaceable" priority="2">
+	<xsl:text>\textit{</xsl:text>
+	<xsl:apply-templates />
+	<xsl:text>}</xsl:text>
+	</xsl:template>
+
+
+    <xsl:template match="group|arg">
+	<xsl:variable name="choice" select="@choice"/>
+	<xsl:variable name="rep" select="@rep"/>
+	<xsl:variable name="sepchar">
+	    <xsl:choose>
+		<xsl:when test="ancestor-or-self::*/@sepchar">
+		    <xsl:value-of select="ancestor-or-self::*/@sepchar"/>
+		</xsl:when>
+		<xsl:otherwise>
+		    <xsl:text> </xsl:text>
+		</xsl:otherwise>
+	    </xsl:choose>
+	</xsl:variable>
+	<xsl:if test="position()>1"><xsl:value-of select="$sepchar"/></xsl:if>
+	<xsl:choose>
+	    <xsl:when test="$choice='plain'">
+		<xsl:value-of select="$arg.choice.plain.open.str"/>
+	    </xsl:when>
+	    <xsl:when test="$choice='req'">
+		<xsl:value-of select="$arg.choice.req.open.str"/>
+	    </xsl:when>
+	    <xsl:when test="$choice='opt'">
+		<xsl:value-of select="$arg.choice.opt.open.str"/>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:value-of select="$arg.choice.def.open.str"/>
+	    </xsl:otherwise>
+	</xsl:choose>
+	<xsl:apply-templates/>
+	<xsl:choose>
+	    <xsl:when test="$rep='repeat'">
+		<xsl:value-of select="$arg.rep.repeat.str"/>
+	    </xsl:when>
+	    <xsl:when test="$rep='norepeat'">
+		<xsl:value-of select="$arg.rep.norepeat.str"/>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:value-of select="$arg.rep.def.str"/>
+	    </xsl:otherwise>
+	</xsl:choose>
+	<xsl:choose>
+	    <xsl:when test="$choice='plain'">
+		<xsl:value-of select="$arg.choice.plain.close.str"/>
+	    </xsl:when>
+	    <xsl:when test="$choice='req'">
+		<xsl:value-of select="$arg.choice.req.close.str"/>
+	    </xsl:when>
+	    <xsl:when test="$choice='opt'">
+		<xsl:value-of select="$arg.choice.opt.close.str"/>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:value-of select="$arg.choice.def.close.str"/>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="group/arg">
+	<xsl:variable name="choice" select="@choice"/>
+	<xsl:variable name="rep" select="@rep"/>
+	<xsl:if test="position()>1"><xsl:value-of select="$arg.or.sep"/></xsl:if>
+	<xsl:apply-templates/>
+    </xsl:template>
+
+    <xsl:template match="sbr">
+	<xsl:text>&#10;</xsl:text>
+    </xsl:template>
+
+    <!-- ==================================================================== -->
+
+    <xsl:template match="synopfragmentref">
+	<!-- VAR target : -->
+	<xsl:variable name="target" select="key('id',@linkend)"/>
+	<!-- VAR snum : -->
+	<xsl:variable name="snum">
+	    <xsl:apply-templates select="$target" mode="synopfragment.number"/>
+	</xsl:variable>
+
+	<xsl:text> {\em (</xsl:text> <xsl:value-of select="$snum"/> <xsl:text>) }</xsl:text>
+    </xsl:template>
+
+    <xsl:template match="synopfragment" mode="synopfragment.number">
+	<xsl:number format="1"/>
+    </xsl:template>
+
+    <xsl:template match="synopfragment">
+	<xsl:variable name="snum">
+	    <xsl:apply-templates select="." mode="synopfragment.number"/>
+	</xsl:variable>
+	<p>
+	    <a name="#{@id}">
+		<xsl:text>(</xsl:text>
+		<xsl:value-of select="$snum"/>
+		<xsl:text>)</xsl:text>
+	    </a>
+	    <xsl:text> </xsl:text>
+	    <xsl:apply-templates/>
+	</p>
+    </xsl:template>   
+
+
+    <xsl:template match="funcsynopsis">
+	<xsl:call-template name="informal.object"/>
+    </xsl:template>
+
+
+    <xsl:template match="funcsynopsisinfo">
+	<xsl:call-template name="verbatim.apply.templates"/>
+    </xsl:template>
+
+
+    <xsl:template match="funcprototype">
+	<xsl:apply-templates/>
+	<xsl:if test="$funcsynopsis.style='kr'">
+	    <xsl:apply-templates select="./paramdef" mode="kr-funcsynopsis-mode"/>
+	</xsl:if>
+    </xsl:template>
+
+    <xsl:template match="funcdef">
+	<xsl:apply-templates/>
+    </xsl:template>
+
+    <xsl:template match="funcdef/function">
+	<xsl:choose>
+	    <xsl:when test="$funcsynopsis.decoration != 0">
+		<xsl:text>\textbf{ </xsl:text><xsl:apply-templates/><xsl:text> } </xsl:text>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:apply-templates/>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+
+    <xsl:template match="void">
+	<xsl:choose>
+	    <xsl:when test="$funcsynopsis.style='ansi'">
+		<xsl:text>(void);</xsl:text>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:text>();</xsl:text>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="varargs">
+	<xsl:text>( ... );</xsl:text>
+    </xsl:template>
+
+    <xsl:template match="paramdef">
+	<!-- VAR paramnum -->
+	<xsl:variable name="paramnum"> <xsl:number count="paramdef" format="1"/> </xsl:variable>
+
+	<xsl:if test="$paramnum=1">(</xsl:if>
+	<xsl:choose>
+	    <xsl:when test="$funcsynopsis.style='ansi'">
+		<xsl:apply-templates/>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:apply-templates select="./parameter"/>
+	    </xsl:otherwise>
+	</xsl:choose>
+	<xsl:choose>
+	    <xsl:when test="following-sibling::paramdef">
+		<xsl:text>, </xsl:text>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:text>);</xsl:text>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+
+
+    <xsl:template match="paramdef/parameter">
+	<xsl:choose>
+	    <xsl:when test="$funcsynopsis.decoration != 0">
+		<xsl:apply-templates/>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:apply-templates/>
+	    </xsl:otherwise>
+	</xsl:choose>
+	<xsl:if test="following-sibling::parameter">
+	    <xsl:text>, </xsl:text>
+	</xsl:if>
+    </xsl:template>
+
+
+
+    <xsl:template match="paramdef" mode="kr-funcsynopsis-mode">
+	\newline
+	<xsl:apply-templates/>
+	<xsl:text>;</xsl:text>
+    </xsl:template>
+
+    <xsl:template match="funcparams">
+	<xsl:text>(</xsl:text>
+	<xsl:apply-templates/>
+	<xsl:text>)</xsl:text>
+    </xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/table.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/table.mod.xsl
new file mode 100644
index 00000000000..10a36e75e25
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/table.mod.xsl
@@ -0,0 +1,1414 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: table.mod.xsl,v 1.32 2004/01/28 02:08:41 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="table" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: table.mod.xsl,v 1.32 2004/01/28 02:08:41 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.24">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Tables <filename>table.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>table</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<variablelist>
+				<varlistentry>
+					<term><xref linkend="param.latex.table.caption.style"/></term>
+					<listitem><simpara>
+						The &LaTeX; command for formatting captions.
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+			
+				Unless <xref linkend="param.latex.use.ltxtable"/> is in use,
+				tables are typeset as <quote>floats</quote> using the <link
+				linkend="latex.mapping">mapping system</link>. This limits the
+				size of each table to one page. It is possible to use tables
+				without floats, but captions and cross-referencing will not
+				function as intended.
+			
+			</para>
+			<para>
+				
+				If a <sgmltag class="attribute">condition</sgmltag> attribute
+				exists and begins with <quote>db2latex:</quote>, or a <sgmltag
+				class="pi">latex-float-placement</sgmltag> processing
+				instruction is present, the remainder of its value will be used
+				as the &LaTeX; <quote>float</quote> placement. Otherwise, the
+				default placement is <quote>htb</quote>.
+				
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_ecos;
+				&test_pinkjuice;
+				&test_tables;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+				<listitem><simpara><xref linkend="template.generate.formal.title.placement"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="table">
+		<xsl:choose>
+			<xsl:when test="caption">
+				<xsl:message>Cannot cope with new-style tables lacking tgroup -- skipped.</xsl:message>
+			</xsl:when>
+			<xsl:when test="$latex.use.ltxtable='1'">
+				<!--
+				<xsl:message>No captions for ltxtable, yet.</xsl:message>
+				-->
+				<!--
+				Can use captions with longtable, but this is handled by
+				the thead and tfoot templates :-(
+				-->
+				<xsl:call-template name="content-templates"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:variable name="placement">
+					<xsl:call-template name="generate.formal.title.placement">
+						<xsl:with-param name="object" select="local-name(.)" />
+					</xsl:call-template>
+				</xsl:variable>
+				<xsl:variable name="position">
+					<xsl:call-template name="generate.latex.float.position">
+						<xsl:with-param name="default" select="'htb'"/>
+					</xsl:call-template>
+				</xsl:variable>
+				<xsl:variable name="caption">
+					<xsl:call-template name="generate.table.caption"/>
+				</xsl:variable>
+				<xsl:call-template name="map.begin">
+					<xsl:with-param name="string" select="$position"/>
+				</xsl:call-template>
+				<xsl:if test="$placement='before'">
+					<xsl:text>\captionswapskip{}</xsl:text>
+					<xsl:value-of select="$caption" />
+					<xsl:text>\captionswapskip{}</xsl:text>
+				</xsl:if>
+				<xsl:call-template name="content-templates"/>
+				<xsl:if test="$placement!='before'"><xsl:value-of select="$caption" /></xsl:if>
+				<xsl:call-template name="map.end">
+					<xsl:with-param name="string" select="$position"/>
+				</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<xsl:template name="generate.table.caption.longtable">
+		<xsl:for-each select="ancestor-or-self::table">
+			<xsl:text>\caption{</xsl:text>
+			<xsl:value-of select="$latex.table.caption.style"/>
+			<xsl:text>{</xsl:text>
+			<xsl:apply-templates select="title" mode="caption.mode"/>
+			<xsl:text>}</xsl:text>
+			<xsl:call-template name="label.id"/>
+			<xsl:text>}\hypertarget{</xsl:text>
+			<xsl:call-template name="generate.label.id"/>
+			<xsl:text>}{}&#10;</xsl:text>
+		</xsl:for-each>
+	</xsl:template>
+
+	<xsl:template name="generate.table.caption">
+		<xsl:for-each select="ancestor-or-self::table">
+			<xsl:text>{</xsl:text>
+			<xsl:value-of select="$latex.table.caption.style"/>
+			<xsl:text>{\caption{</xsl:text>
+			<xsl:apply-templates select="title" mode="caption.mode"/>
+			<xsl:text>}</xsl:text>
+			<xsl:call-template name="label.id"/>
+			<xsl:text>}}&#10;</xsl:text>
+		</xsl:for-each>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>informaltable</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Applies templates within a &LaTeX; mapping.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_bind;
+				&test_book;
+				&test_chemistry;
+				&test_tables;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara>&mapping;</simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="informaltable">
+		<xsl:call-template name="map.begin"/>
+		<xsl:apply-templates/>
+		<xsl:call-template name="map.end"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db basename="table">tables</doc:db> using <productname>tabularx</productname> </refpurpose>
+		<doc:description>
+			<para>
+			
+			Similar to <xref linkend="template.table.format.tabularx"/> but
+			calculates <quote>relative</quote> column sizes.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_tables;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.table.format.tabular"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="table.format.tabularx">
+		<xsl:param name="cols" select="1"/>
+		<xsl:param name="i" select="1"/>
+		<xsl:param name="colsep" select="1"/>
+		<!-- sum of numeric portions in 1*-like colwidths -->
+		<xsl:param name="starfactor" select="0"/>
+		<xsl:choose>
+			<!-- Out of the recursive iteration -->
+			<xsl:when test="$i > $cols"></xsl:when>
+			<!-- There are still columns to count -->
+			<xsl:otherwise>
+			<xsl:variable name="userwidth">
+				<xsl:choose>
+					<xsl:when test="./colspec[@colnum=$i]">
+						<xsl:value-of select="./colspec[@colnum=$i]/@colwidth"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:value-of select="./colspec[position()=$i]/@colwidth"/>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:variable>
+			<xsl:variable name="useralign">
+				<xsl:choose>
+					<xsl:when test="./colspec[@colnum=$i]/@align!=''">
+						<xsl:value-of select="./colspec[@colnum=$i]/@align"/>
+					</xsl:when>
+					<xsl:when test="./colspec[position()=$i]/@align!=''">
+						<xsl:value-of select="./colspec[position()=$i]/@align"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:value-of select="./@align"/>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:variable>
+			<xsl:variable name="width">
+				<xsl:variable name="cells" select="thead/row/entry[$i]|tbody/row/entry[$i]"/>
+				<xsl:choose>
+					<xsl:when test="string-length($userwidth)=0 and count($cells//itemizedlist|$cells//orderedlist|$cells//variablelist)&gt;0">
+						<!-- In these specific circumstances, we MUST use a line-wrapped column
+							 and yet the user hasn't specified one. -->
+						<xsl:value-of select="'1*'"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<!-- In the general case, we just do what the user wants (may even
+							 have no pre-specified width). -->
+						<xsl:value-of select="$userwidth"/>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:variable>
+			<!-- Try to take heed of colspecs -->
+			<xsl:choose>
+				<xsl:when test="$width!=''">
+					<xsl:text>&gt;{</xsl:text>
+					<xsl:if test="contains($width,'*')">
+						<!-- see tabularx documentation -->
+						<xsl:text>\hsize=</xsl:text>
+						<xsl:value-of select="substring-before($width,'*') * $starfactor" />
+						<xsl:text>\hsize</xsl:text>
+					</xsl:if>
+					<xsl:choose>
+						<xsl:when test="$useralign='left'"><xsl:text>\RaggedRight</xsl:text></xsl:when>
+						<xsl:when test="$useralign='right'"><xsl:text>\RaggedLeft</xsl:text></xsl:when>
+						<xsl:when test="$useralign='center'"><xsl:text>\Centering</xsl:text></xsl:when>
+						<xsl:when test="$useralign='char' and $latex.use.dcolumn='1'">
+							<xsl:variable name="char" select="(./colspec[@colnum=$i]/@char|./colspec[position()=$i]/@char)[1]"/>
+							<xsl:choose>
+								<xsl:when test="$char=''"><xsl:text>d</xsl:text></xsl:when>
+								<xsl:otherwise>D{<xsl:value-of select="$char"/>}{<xsl:value-of select="$char"/>}{-1}</xsl:otherwise>
+							</xsl:choose>
+						</xsl:when>
+						<xsl:when test="$useralign!=''"><xsl:message>Table column '<xsl:value-of select="$useralign"/>' alignment is not supported.</xsl:message></xsl:when>
+					</xsl:choose>
+					<xsl:text>}</xsl:text>
+					<xsl:choose>
+						<xsl:when test="contains($width,'*')">
+							<xsl:text>X</xsl:text>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:text>p{</xsl:text><xsl:value-of select="$width" /><xsl:text>}</xsl:text>
+						</xsl:otherwise>
+					</xsl:choose>
+					<xsl:if test="$i&lt;$cols and $colsep='1'">
+						<xsl:text>|</xsl:text>
+					</xsl:if>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:choose>
+						<xsl:when test="$useralign='left'"><xsl:text>l</xsl:text></xsl:when>
+						<xsl:when test="$useralign='right'"><xsl:text>r</xsl:text></xsl:when>
+						<xsl:when test="$useralign='center'"><xsl:text>c</xsl:text></xsl:when>
+						<xsl:when test="$useralign='justify'"><xsl:text>X</xsl:text></xsl:when>
+						<xsl:when test="$useralign='char' and $latex.use.dcolumn='1'">
+							<xsl:variable name="char" select="(./colspec[@colnum=$i]/@char|./colspec[position()=$i]/@char)[1]"/>
+							<xsl:choose>
+								<xsl:when test="$char=''"><xsl:text>d</xsl:text></xsl:when>
+								<xsl:otherwise>D{<xsl:value-of select="$char"/>}{<xsl:value-of select="$char"/>}{-1}</xsl:otherwise>
+							</xsl:choose>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:text>c</xsl:text>
+							<xsl:if test="$useralign!=''">
+								<xsl:message>Table column '<xsl:value-of select="$useralign"/>' alignment is not supported.</xsl:message>
+							</xsl:if>
+						</xsl:otherwise>
+					</xsl:choose>
+					<xsl:if test="$i&lt;$cols and $colsep='1'">
+						<xsl:text>|</xsl:text>
+					</xsl:if>
+				</xsl:otherwise>
+			</xsl:choose>
+			<!-- Recursive for next column -->
+			<xsl:call-template name="table.format.tabularx">
+				<xsl:with-param name="i" select="$i+1"/>
+				<xsl:with-param name="cols" select="$cols"/>
+				<xsl:with-param name="colsep" select="$colsep"/>
+				<xsl:with-param name="starfactor" select="$starfactor"/>
+			</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db basename="table">tables</doc:db> using <function condition="env">tabular</function> </refpurpose>
+		<doc:description>
+			<para>
+			
+			
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_tables;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.table.format.tabularx"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="table.format.tabular">
+		<xsl:param name="cols" select="1"/>
+		<xsl:param name="i" select="1"/>
+		<xsl:param name="colsep" select="1"/>
+		<xsl:choose>
+			<!-- Out of the recursive iteration -->
+			<xsl:when test="$i > $cols"></xsl:when>
+			<!-- There are still columns to count -->
+			<xsl:otherwise>
+			<!-- Try to take heed of colspecs -->
+			<xsl:variable name="width">
+				<xsl:variable name="userwidth">
+					<xsl:choose>
+						<xsl:when test="./colspec[@colnum=$i]">
+							<xsl:value-of select="./colspec[@colnum=$i]/@colwidth"/>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:value-of select="./colspec[position()=$i]/@colwidth"/>
+						</xsl:otherwise>
+					</xsl:choose>
+				</xsl:variable>
+				<xsl:variable name="cells" select="thead/row/entry[$i]|tbody/row/entry[$i]"/>
+				<xsl:choose>
+					<xsl:when test="string-length($userwidth)=0 and count($cells//itemizedlist|$cells//orderedlist|$cells//variablelist)&gt;0">
+						<!-- In these specific circumstances, we MUST use a line-wrapped column
+							 and yet the user hasn't specified one. -->
+						<xsl:value-of select="concat(1 div $cols,'\linewidth')"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<!-- In the general case, we just do what the user wants (may even
+							 have no pre-specified width). -->
+						<xsl:value-of select="$userwidth"/>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:variable>
+			<xsl:variable name="useralign">
+				<xsl:choose>
+					<xsl:when test="./colspec[@colnum=$i]/@align!=''">
+						<xsl:value-of select="./colspec[@colnum=$i]/@align"/>
+					</xsl:when>
+					<xsl:when test="./colspec[position()=$i]/@align!=''">
+						<xsl:value-of select="./colspec[position()=$i]/@align"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:value-of select="./@align"/>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:variable>
+			<xsl:choose>
+				<xsl:when test="$width!='' and not(contains($width,'*'))">
+					<xsl:choose>
+						<xsl:when test="$useralign='left'"><xsl:text>&gt;{\RaggedRight}</xsl:text></xsl:when>
+						<xsl:when test="$useralign='right'"><xsl:text>&gt;{\RaggedLeft}</xsl:text></xsl:when>
+						<xsl:when test="$useralign='center'"><xsl:text>&gt;{\Centering}</xsl:text></xsl:when>
+						<xsl:when test="$useralign='char'"><xsl:message>Table column 'char' alignment is not supported when width specified.</xsl:message></xsl:when>
+						<xsl:when test="$useralign!=''"><xsl:message>Table column '<xsl:value-of select="$useralign"/>' alignment is not supported.</xsl:message></xsl:when>
+					</xsl:choose>
+					<xsl:text>p{</xsl:text><xsl:value-of select="$width" /><xsl:text>}</xsl:text>
+					<xsl:if test="$i&lt;$cols and $colsep='1'">
+						<xsl:text>|</xsl:text>
+					</xsl:if>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:choose>
+						<xsl:when test="$useralign='left'"><xsl:text>l</xsl:text></xsl:when>
+						<xsl:when test="$useralign='right'"><xsl:text>r</xsl:text></xsl:when>
+						<xsl:when test="$useralign='center'"><xsl:text>c</xsl:text></xsl:when>
+						<xsl:when test="$useralign='justify'"><xsl:text>l</xsl:text></xsl:when>
+						<xsl:when test="$useralign='char' and $latex.use.dcolumn='1'">
+							<xsl:variable name="char" select="(./colspec[@colnum=$i]/@char|./colspec[position()=$i]/@char)[1]"/>
+							<xsl:choose>
+								<xsl:when test="$char=''"><xsl:text>d</xsl:text></xsl:when>
+								<xsl:otherwise>D{<xsl:value-of select="$char"/>}{<xsl:value-of select="$char"/>}{-1}</xsl:otherwise>
+							</xsl:choose>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:text>c</xsl:text>
+							<xsl:if test="$useralign!=''">
+								<xsl:message>Table column '<xsl:value-of select="$useralign"/>' alignment is not supported.</xsl:message>
+							</xsl:if>
+						</xsl:otherwise>
+					</xsl:choose>
+					<xsl:if test="$i&lt;$cols and $colsep='1'">
+						<xsl:text>|</xsl:text>
+					</xsl:if>
+				</xsl:otherwise>
+			</xsl:choose>
+			<!-- Recursive for next column -->
+			<xsl:call-template name="table.format.tabular">
+				<xsl:with-param name="i" select="$i+1"/>
+				<xsl:with-param name="cols" select="$cols"/>
+				<xsl:with-param name="colsep" select="$colsep"/>
+			</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<!-- See tabularx documentation. -->
+	<!-- For example, if we have a 1* column and a 3* column, then the
+	     the hsizes for each column are (1/(1+3)*2) and (3/(1+3)*2).
+		 The ratio of these to the star values (star values being 1 and 3)
+		 is 2/(1+3).
+		 BUT it is now very complicated because it takes into account columns
+		 where the user has not specified a width but LaTeX requires a
+		 fixed-width column (i.e. specialcols may vary).
+		 Relies on there being (a) colspecs for every column or (b) no
+		 colspecs.
+	 -->
+	<doc:template xmlns="">
+		<refpurpose>Calculate relative column sizes</refpurpose>
+		<doc:description>
+			<para>
+			
+			Determines the width of each column in terms of <quote>relative
+			units</quote>.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_tables;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.table.format.tabular"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.table.format.tabularx"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="generate.starfactor">
+		<xsl:param name="i" select="1"/>
+		<xsl:param name="cols" select="count(colspec)"/>
+		<xsl:param name="sum" select="0"/>
+		<xsl:param name="specialcols" select="count(colspec[contains(@colwidth,'*')])"/>
+		<xsl:choose>
+			<xsl:when test="$i&lt;=$cols and colspec[position()=$i and contains(@colwidth,'*')]">
+				<!-- a * column -->
+				<xsl:call-template name="generate.starfactor">
+					<xsl:with-param name="i" select="$i+1"/>
+					<xsl:with-param name="cols" select="$cols"/>
+					<xsl:with-param name="sum" select="$sum+substring-before(colspec[$i]/@colwidth,'*')"/>
+					<xsl:with-param name="specialcols" select="$specialcols"/>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="$i&lt;=$cols">
+				<!-- not a * column, but we are going to pretend that it is -->
+				<xsl:variable name="cells" select="thead/row/entry[$i]|tbody/row/entry[$i]"/>
+				<xsl:variable name="problems" select="count($cells//itemizedlist|$cells//orderedlist|$cells//variablelist)"/>
+				<xsl:choose>
+					<xsl:when test="$problems &gt; 0">
+						<xsl:call-template name="generate.starfactor">
+							<xsl:with-param name="i" select="$i+1"/>
+							<xsl:with-param name="cols" select="$cols"/>
+							<xsl:with-param name="sum" select="$sum+1"/>
+							<xsl:with-param name="specialcols" select="$specialcols+1"/>
+						</xsl:call-template>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:call-template name="generate.starfactor">
+							<xsl:with-param name="i" select="$i+1"/>
+							<xsl:with-param name="cols" select="$cols"/>
+							<xsl:with-param name="sum" select="$sum"/>
+							<xsl:with-param name="specialcols" select="$specialcols"/>
+						</xsl:call-template>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:value-of select="$specialcols div $sum"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>tgroup</doc:db> elements</refpurpose>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="tgroup">
+		<xsl:variable name="colsep">
+			<xsl:choose>
+				<xsl:when test="@colsep!=''">
+					<xsl:value-of select="number(@colsep)"/>
+				</xsl:when>
+				<xsl:when test="../@colsep!=''">
+					<xsl:value-of select="number(../@colsep)"/>
+				</xsl:when>
+				<xsl:otherwise>1</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:variable name="frame">
+			<xsl:choose>
+				<xsl:when test="string-length(../@frame)&lt;1">all</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="../@frame"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:variable name="colspecs" select="./colspec"/>
+		<xsl:variable name="usex">
+			<xsl:choose>
+				<xsl:when test="$latex.use.ltxtable='1'">
+					<xsl:text>0</xsl:text>
+				</xsl:when>
+				<!-- if there are lists within cells, we need tabularx -->
+				<xsl:when test="$latex.use.tabularx=1 and (descendant::itemizedlist|descendant::orderedlist|descendant::variablelist)">
+					<xsl:text>1</xsl:text>
+				</xsl:when>
+				<!-- if there are instances of 1*-style colwidths, we need tabularx -->
+				<xsl:when test="$latex.use.tabularx=1 and contains(colspec/@colwidth,'*')">
+					<xsl:text>1</xsl:text>
+				</xsl:when>
+				<!-- if there are colspecs with 'justify' alignment and no explicit width, we need tabularx -->
+				<xsl:when test="$latex.use.tabularx=1 and count(colspec[@align='justify'])&gt;0">
+					<xsl:text>1</xsl:text>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:text>0</xsl:text>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:variable name="useminipage">
+			<!-- Hack to get around LaTeX issue with tabular (not necessary with tabularx).
+			This is NOT a good solution, and has problems of its own, but at least the footnotes
+			do not actually disappear (which is what would otherwise happen). -->
+			<xsl:if test="count(.//footnote)!=0">1</xsl:if>
+		</xsl:variable>
+		<xsl:choose>
+			<xsl:when test="$usex='1'">
+				<xsl:text>\begin{tabularx}{\linewidth}{</xsl:text>
+			</xsl:when>
+			<xsl:when test="$latex.use.ltxtable='1'">
+				<xsl:if test="parent::informaltable">
+					<xsl:text>\addtocounter{table}{-1}</xsl:text>
+				</xsl:if>
+				<xsl:text>\begin{longtable}{</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:if test="$useminipage='1'"><xsl:text>\begin{minipage}{\linewidth}&#10;</xsl:text></xsl:if>
+				<xsl:text>\begin{tabular}{</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:if test="$frame='all' or $frame='sides'">
+			<xsl:text>|</xsl:text>
+		</xsl:if>
+		<xsl:variable name="cols">
+			<xsl:choose>
+				<xsl:when test="@cols">
+					<xsl:value-of select="@cols"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="count(tbody/row[1]/entry)"/>
+					<xsl:message>Warning: table's tgroup lacks cols attribute. Assuming <xsl:value-of select="count(tbody/row[1]/entry)"/>.</xsl:message>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:choose>
+			<xsl:when test="$usex=1">
+				<xsl:call-template name="table.format.tabularx">
+					<xsl:with-param name="cols" select="$cols"/>
+					<xsl:with-param name="colsep" select="$colsep"/>
+					<xsl:with-param name="starfactor">
+						<xsl:call-template name="generate.starfactor">
+							<xsl:with-param name="cols" select="$cols"/>
+						</xsl:call-template>
+					</xsl:with-param>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="table.format.tabular">
+					<xsl:with-param name="cols" select="$cols"/>
+					<xsl:with-param name="colsep" select="$colsep"/>
+				</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:if test="$frame='all' or $frame='sides'">
+			<xsl:text>|</xsl:text>
+		</xsl:if>
+		<xsl:text>}&#10;</xsl:text>
+		<xsl:variable name="thead.frame">
+			<xsl:choose>
+				<xsl:when test="$frame!='sides' and $frame!='none' and $frame!='bottom'">
+					<xsl:value-of select="1"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="0"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:variable name="tfoot.frame">
+			<xsl:choose>
+				<xsl:when test="$frame!='sides' and $frame!='none' and $frame!='top'">
+					<xsl:value-of select="1"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="0"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<!-- APPLY TEMPLATES -->
+		<xsl:choose>
+			<xsl:when test="$latex.use.ltxtable='1' and parent::table">
+				<!-- for tables only, not informaltables -->
+				<xsl:variable name="placement">
+					<xsl:call-template name="generate.formal.title.placement">
+						<xsl:with-param name="object" select="'table'" />
+					</xsl:call-template>
+				</xsl:variable>
+				<xsl:choose>
+					<xsl:when test="$placement='before'">
+						<xsl:choose>
+							<xsl:when test="thead">
+								<xsl:apply-templates select="thead" mode="longtable.caption">
+									<xsl:with-param name="frame" select="$thead.frame"/>
+								</xsl:apply-templates>
+								<xsl:apply-templates select="thead" mode="longtable.caption.continuation">
+									<xsl:with-param name="frame" select="$thead.frame"/>
+								</xsl:apply-templates>
+							</xsl:when>
+							<xsl:otherwise>
+								<xsl:call-template name="thead.longtable.caption">
+									<xsl:with-param name="frame" select="$thead.frame"/>
+								</xsl:call-template>
+								<xsl:call-template name="thead.longtable.caption.continuation">
+									<xsl:with-param name="frame" select="$thead.frame"/>
+								</xsl:call-template>
+							</xsl:otherwise>
+						</xsl:choose>
+						<xsl:apply-templates select="tfoot">
+							<xsl:with-param name="frame" select="$tfoot.frame"/>
+						</xsl:apply-templates>
+						<xsl:if test="$tfoot.frame=1 and not(tfoot)">
+							<xsl:text>\hline &#10;</xsl:text>
+						</xsl:if>
+						<xsl:apply-templates select="tbody"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:if test="$thead.frame=1 and not(thead)">
+							<xsl:text>\hline &#10;</xsl:text>
+						</xsl:if>
+						<xsl:apply-templates select="thead">
+							<xsl:with-param name="frame" select="$thead.frame"/>
+						</xsl:apply-templates>
+						<xsl:choose>
+							<xsl:when test="tfoot">
+								<xsl:apply-templates select="tfoot" mode="longtable.caption.continued">
+									<xsl:with-param name="frame" select="$tfoot.frame"/>
+								</xsl:apply-templates>
+								<xsl:apply-templates select="tfoot" mode="longtable.caption">
+									<xsl:with-param name="frame" select="$tfoot.frame"/>
+								</xsl:apply-templates>
+							</xsl:when>
+							<xsl:otherwise>
+								<xsl:call-template name="tfoot.longtable.caption.continued">
+									<xsl:with-param name="frame" select="$tfoot.frame"/>
+								</xsl:call-template>
+								<xsl:call-template name="tfoot.longtable.caption">
+									<xsl:with-param name="frame" select="$tfoot.frame"/>
+								</xsl:call-template>
+							</xsl:otherwise>
+						</xsl:choose>
+						<xsl:apply-templates select="tbody"/>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:if test="$thead.frame=1 and not(thead)">
+					<xsl:text>\hline &#10;</xsl:text>
+				</xsl:if>
+				<xsl:apply-templates select="thead">
+					<xsl:with-param name="frame" select="$thead.frame"/>
+				</xsl:apply-templates>
+				<xsl:apply-templates select="tbody"/>
+				<xsl:apply-templates select="tfoot">
+					<xsl:with-param name="frame" select="$tfoot.frame"/>
+				</xsl:apply-templates>
+				<xsl:if test="$tfoot.frame=1 and not(tfoot)">
+					<xsl:text>\hline &#10;</xsl:text>
+				</xsl:if>
+			</xsl:otherwise>
+		</xsl:choose>
+		<!--                 -->
+		<xsl:choose>
+			<xsl:when test="$usex=1">
+				<xsl:text>\end{tabularx}&#10;</xsl:text>
+			</xsl:when>
+			<xsl:when test="$latex.use.ltxtable='1'">
+				<xsl:text>\end{longtable}&#10;</xsl:text>
+				<!-- catcode touchup ARGH -->
+				<xsl:call-template name="generate.latex.cell.separator">
+					<xsl:with-param name="which" select="'post'"/>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>\end{tabular}&#10;</xsl:text>
+				<xsl:if test="$useminipage='1'"><xsl:text>\end{minipage}&#10;</xsl:text></xsl:if>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>colspec</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Suppressed.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				<doc:db basename="colspec">Colspec</doc:db> are interpreted by
+				the <doc:db>tgroup</doc:db> template.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_tables;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.tgroup"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="colspec"></xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>spanspec</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Suppressed.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				<doc:db basename="spanspec">Spanspecs</doc:db> are interpreted
+				by the <doc:db>tgroup</doc:db> template.
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_tables;
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.tgroup"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="spanspec"></xsl:template>
+
+	<doc:template basename="thead" xmlns="">
+		<refpurpose>Process <doc:db>thead</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Applies templates.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="thead">
+		<xsl:param name="frame" select="0"/>
+		<xsl:if test="$frame=1">
+			<xsl:text>\hline &#10;</xsl:text>
+		</xsl:if>
+		<xsl:apply-templates/>
+		<xsl:if test="$latex.use.ltxtable='1'">
+			<xsl:text> \endhead&#10;</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template basename="thead" xmlns="">
+		<refpurpose>Process <doc:db>thead</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Emits a caption and calls <function condition="latex">endfirsthead</function>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="thead" mode="longtable.caption" name="thead.longtable.caption">
+		<xsl:param name="frame" select="0"/>
+		<xsl:call-template name="generate.table.caption.longtable"/>
+		<xsl:text>\\&#10;</xsl:text><!-- or should this be \tabularnewline? -->
+		<xsl:if test="$frame=1">
+			<xsl:text>\hline &#10;</xsl:text>
+		</xsl:if>
+		<xsl:apply-templates select="row"/>
+		<xsl:text> \endfirsthead&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="thead" xmlns="">
+		<refpurpose>Process <doc:db>thead</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Emits a continuation caption and calls <function condition="latex">endhead</function>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="thead" mode="longtable.caption.continuation" name="thead.longtable.caption.continuation">
+		<xsl:param name="frame" select="0"/>
+		<xsl:text>\caption[]{</xsl:text>
+		<xsl:value-of select="$latex.table.caption.style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:call-template name="gentext.template">
+			<xsl:with-param name="context" select="'table'"/>
+			<xsl:with-param name="name" select="'thead.continuation'"/>
+		</xsl:call-template>
+		<xsl:text>}}\\&#10;</xsl:text><!-- or should this be \tabularnewline? -->
+		<xsl:if test="$frame=1">
+			<xsl:text>\hline &#10;</xsl:text>
+		</xsl:if>
+		<xsl:apply-templates select="row"/>
+		<xsl:text> \endhead&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="tfoot" xmlns="">
+		<refpurpose>Process <doc:db>tfoot</doc:db> elements</refpurpose>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="tfoot">
+		<xsl:param name="frame" select="0"/>
+		<xsl:apply-templates/>
+		<xsl:if test="$frame=1">
+			<xsl:text>\hline &#10;</xsl:text>
+		</xsl:if>
+		<xsl:if test="$latex.use.ltxtable='1'">
+			<xsl:text> \endfoot&#10;</xsl:text>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template basename="tfoot" xmlns="">
+		<refpurpose>Process <doc:db>tfoot</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Emits a caption and calls <function condition="latex">endlastfoot</function>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="tfoot" mode="longtable.caption" name="tfoot.longtable.caption">
+		<xsl:param name="frame" select="0"/>
+		<xsl:apply-templates select="row"/>
+		<xsl:if test="$frame=1">
+			<xsl:text>\hline &#10;</xsl:text>
+		</xsl:if>
+		<xsl:call-template name="generate.table.caption.longtable"/>
+		<xsl:text>\\&#10;</xsl:text><!-- or should this be \tabularnewline? -->
+		<xsl:text> \endlastfoot&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="tfoot" xmlns="">
+		<refpurpose>Process <doc:db>tfoot</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Emits a continuation caption and calls <function condition="latex">endfoot</function>.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="tfoot" mode="longtable.caption.continued" name="tfoot.longtable.caption.continued">
+		<xsl:param name="frame" select="0"/>
+		<xsl:apply-templates select="row"/>
+		<xsl:if test="$frame=1">
+			<xsl:text>\hline &#10;</xsl:text>
+		</xsl:if>
+		<xsl:text>\caption[]{</xsl:text>
+		<xsl:value-of select="$latex.table.caption.style"/>
+		<xsl:text>{</xsl:text>
+		<xsl:call-template name="gentext.template">
+			<xsl:with-param name="context" select="'table'"/>
+			<xsl:with-param name="name" select="'tfoot.continued'"/>
+		</xsl:call-template>
+		<xsl:text>}}\\&#10;</xsl:text><!-- or should this be \tabularnewline? -->
+		<xsl:text> \endfoot&#10;</xsl:text>
+	</xsl:template>
+
+	<doc:template basename="entry" xmlns="">
+		<refpurpose>Process a <doc:db>thead</doc:db>'s <doc:db>entry</doc:db> elements</refpurpose>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="thead/row/entry">
+		<xsl:call-template name="latex.entry.prealign"/>
+		<xsl:call-template name="latex.thead.row.entry"/>
+		<xsl:call-template name="latex.entry.postalign"/>
+		<xsl:if test="position()&lt;last()">
+			<xsl:call-template name="generate.latex.cell.separator">
+				<xsl:with-param name="which" select="'pre'"/>
+			</xsl:call-template>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template basename="entry" xmlns="">
+		<refpurpose>Process a <doc:db>tfoot</doc:db>'s <doc:db>entry</doc:db> elements</refpurpose>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="tfoot/row/entry">
+		<xsl:call-template name="latex.entry.prealign"/>
+		<xsl:call-template name="latex.tfoot.row.entry"/>
+		<xsl:call-template name="latex.entry.postalign"/>
+		<xsl:if test="position()&lt;last()">
+			<xsl:call-template name="generate.latex.cell.separator">
+				<xsl:with-param name="which" select="'pre'"/>
+			</xsl:call-template>
+		</xsl:if> 
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>tbody</doc:db> elements</refpurpose>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="tbody">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<doc:template basename="row" xmlns="">
+		<refpurpose>Process a <doc:db>tbody</doc:db>'s <doc:db>row</doc:db> elements</refpurpose>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="tbody/row">
+		<xsl:apply-templates/>
+		<xsl:text> \tabularnewline&#10;</xsl:text>
+		<xsl:call-template name="generate.table.row.separator"/>
+	</xsl:template>
+
+	<doc:template basename="row" xmlns="">
+		<refpurpose>Process a <doc:db>thead</doc:db>'s <doc:db>row</doc:db> elements</refpurpose>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="thead/row">
+		<xsl:apply-templates/>
+		<xsl:text> \tabularnewline&#10;</xsl:text>
+		<xsl:call-template name="generate.table.row.separator"/>
+	</xsl:template>
+
+	<doc:template basename="row" xmlns="">
+		<refpurpose>Process a <doc:db>tfoot</doc:db>'s <doc:db>row</doc:db> elements</refpurpose>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="tfoot/row">
+		<xsl:call-template name="generate.table.row.separator"/>
+		<xsl:apply-templates/>
+		<xsl:text> \tabularnewline&#10;</xsl:text>
+	</xsl:template>
+
+	<!-- The rule below the last row in the table is controlled by the 
+	Frame attribute of the enclosing Table or InformalTable and the RowSep 
+	of the last row is ignored. If unspecified, this attribute is 
+	inherited from enclosing elements, rowsep=1 by default. -->
+    <xsl:template name="generate.table.row.separator">
+		<xsl:param name="rowsep">
+			<xsl:choose>
+				<xsl:when test="ancestor::tgroup/@rowsep!=''">
+					<xsl:value-of select="number(ancestor::tgroup/@rowsep)"/>
+				</xsl:when>
+				<xsl:when test="ancestor::tgroup/../@rowsep!=''">
+					<xsl:value-of select="number(ancestor::tgroup/../@rowsep)"/>
+				</xsl:when>
+				<xsl:otherwise>1</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:variable name="parent_position" select="count(../preceding-sibling::node())+1"/>
+		<xsl:variable name="grandparent_children" select="count(../../child::node())"/>
+		<xsl:if test="$rowsep=1 and (position() != last() or $parent_position &lt; $grandparent_children)">
+		<xsl:call-template name="table.row.separator"/>
+		</xsl:if>
+	</xsl:template>
+
+	<xsl:template name="table.row.separator">
+		<xsl:text> \hline &#10;</xsl:text>
+	</xsl:template>
+
+    <xsl:template match="tbody/row/entry">
+	<xsl:call-template name="latex.entry.prealign"/>
+	<xsl:apply-templates/>
+	<xsl:call-template name="latex.entry.postalign"/>
+	<xsl:if test="position()&lt;last()">
+		<xsl:call-template name="generate.latex.cell.separator">
+			<xsl:with-param name="which" select="'pre'"/>
+		</xsl:call-template>
+	</xsl:if> 
+    </xsl:template>
+
+	<xsl:template name="latex.entry.prealign">
+	<xsl:variable name="span">
+		<xsl:choose>
+			<xsl:when test="@spanname!=''">
+				<xsl:call-template name="calculate.colspan">
+					<xsl:with-param name="namest" select="../../../spanspec[@spanname=@spanname]/@namest"/>
+					<xsl:with-param name="nameend" select="../../../spanspec[@spanname=@spanname]/@nameend"/>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:when test="@namest!=''">
+				<xsl:call-template name="calculate.colspan"/>
+			</xsl:when>
+			<xsl:otherwise>-1</xsl:otherwise>
+		</xsl:choose>
+	</xsl:variable>
+	<!-- Remember: if multicolumn is present, generate.latex.cell.separator post needs to occur within multicolumn -->
+	<xsl:if test="$span &gt; 1">
+		<xsl:text>\multicolumn{</xsl:text>
+		<xsl:value-of select="$span"/>
+		<xsl:text>}{|</xsl:text><!-- TODO take heed of @colsep on BOTH sides!! -->
+		<xsl:choose>
+			<xsl:when test="@align='left'"><xsl:text>l</xsl:text></xsl:when>
+			<xsl:when test="@align='right'"><xsl:text>r</xsl:text></xsl:when>
+			<xsl:when test="@align='center'"><xsl:text>c</xsl:text></xsl:when>
+			<xsl:when test="@align='char'">c<xsl:message>Table _entry_ 'char' alignment is not supported.</xsl:message></xsl:when>
+			<xsl:otherwise>c</xsl:otherwise>
+		</xsl:choose>
+	<!-- use this as a hook for some general warnings -->
+		<xsl:text>|}</xsl:text>
+	</xsl:if>
+	<!-- this is used when the entry's align spec wants to override the column default -->
+	<xsl:if test="$span &lt; 1">
+		<xsl:choose>
+			<xsl:when test="@align='left'"><xsl:text>\docbooktolatexalignll </xsl:text></xsl:when>
+			<xsl:when test="@align='right'"><xsl:text>\docbooktolatexalignrl </xsl:text></xsl:when>
+			<xsl:when test="@align='center'"><xsl:text>\docbooktolatexaligncl </xsl:text></xsl:when>
+			<xsl:when test="@align='char'"><xsl:message>Table _entry_ char alignment is not supported.</xsl:message></xsl:when>
+		</xsl:choose>
+	</xsl:if>
+	<xsl:text>{</xsl:text>
+	<xsl:call-template name="generate.latex.cell.separator">
+		<xsl:with-param name="which" select="'post'"/>
+	</xsl:call-template>
+	<xsl:if test="@rotate='1'">
+		<xsl:text>\rotatebox{90}</xsl:text>
+		<xsl:if test="@align!=''"><xsl:message>entry[@rotate='1' and @align!=''] probably doesn't work.</xsl:message></xsl:if>
+	</xsl:if>
+	<xsl:text>{</xsl:text>
+	<!-- use this as a hook for some general warnings -->
+	<xsl:if test="@morerows!=''"><xsl:message>The morerows attribute is not supported.</xsl:message></xsl:if>
+	</xsl:template>
+
+	<xsl:template name="latex.entry.postalign">
+	<xsl:text>}}</xsl:text>
+	<!-- this is used when the entry's align spec wants to override the column default -->
+	<xsl:if test="@namest='' and @spanspec=''"><!-- TODO improve -->
+		<xsl:choose>
+			<xsl:when test="@align='left'"><xsl:text>\docbooktolatexalignlr </xsl:text></xsl:when>
+			<xsl:when test="@align='right'"><xsl:text>\docbooktolatexalignrr </xsl:text></xsl:when>
+			<xsl:when test="@align='center'"><xsl:text>\docbooktolatexaligncr </xsl:text></xsl:when>
+		</xsl:choose>
+	</xsl:if>
+	</xsl:template>
+
+    <xsl:template name="process.cell">
+	<xsl:param name="cellgi">td</xsl:param>
+	<xsl:variable name="empty.cell" select="count(node()) = 0"/>
+
+	<xsl:element name="{$cellgi}">
+	    <xsl:if test="@morerows">
+		<xsl:attribute name="rowspan">
+		    <xsl:value-of select="@morerows+1"/>
+		</xsl:attribute>
+	    </xsl:if>
+	    <xsl:if test="@namest">
+		<xsl:attribute name="colspan">
+		    <xsl:call-template name="calculate.colspan"/>
+		</xsl:attribute>
+	    </xsl:if>
+	    <xsl:if test="@align">
+		<xsl:attribute name="align">
+		    <xsl:value-of select="@align"/>
+		</xsl:attribute>
+	    </xsl:if>
+	    <xsl:if test="@char">
+		<xsl:attribute name="char">
+		    <xsl:value-of select="@char"/>
+		</xsl:attribute>
+	    </xsl:if>
+	    <xsl:if test="@charoff">
+		<xsl:attribute name="charoff">
+		    <xsl:value-of select="@charoff"/>
+		</xsl:attribute>
+	    </xsl:if>
+	    <xsl:if test="@valign">
+		<xsl:attribute name="valign">
+		    <xsl:value-of select="@valign"/>
+		</xsl:attribute>
+	    </xsl:if>
+
+	    <xsl:choose>
+		<xsl:when test="$empty.cell">
+		    <xsl:text>&#160;</xsl:text>
+		</xsl:when>
+		<xsl:otherwise>
+		    <xsl:apply-templates/>
+		</xsl:otherwise>
+	    </xsl:choose>
+	</xsl:element>
+    </xsl:template>
+
+    <xsl:template name="generate.colgroup">
+	<xsl:param name="cols" select="1"/>
+	<xsl:param name="count" select="1"/>
+	<xsl:choose>
+	    <xsl:when test="$count>$cols"></xsl:when>
+	    <xsl:otherwise>
+		<xsl:call-template name="generate.col">
+		    <xsl:with-param name="countcol" select="$count"/>
+		</xsl:call-template>
+		<xsl:call-template name="generate.colgroup">
+		    <xsl:with-param name="cols" select="$cols"/>
+		    <xsl:with-param name="count" select="$count+1"/>
+		</xsl:call-template>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template name="generate.col">
+	<xsl:param name="countcol">1</xsl:param>
+	<xsl:param name="colspecs" select="./colspec"/>
+	<xsl:param name="count">1</xsl:param>
+	<xsl:param name="colnum">1</xsl:param>
+
+	<xsl:choose>
+	    <xsl:when test="$count>count($colspecs)">
+		<col/>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:variable name="colspec" select="$colspecs[$count=position()]"/>
+		<xsl:variable name="colspec.colnum">
+		    <xsl:choose>
+			<xsl:when test="$colspec/@colnum">
+			    <xsl:value-of select="$colspec/@colnum"/>
+			</xsl:when>
+			<xsl:otherwise>
+			    <xsl:value-of select="$colnum"/>
+			</xsl:otherwise>
+		    </xsl:choose>
+		</xsl:variable>
+
+		<xsl:choose>
+		    <xsl:when test="$colspec.colnum=$countcol">
+			<col>
+			    <xsl:if test="$colspec/@align">
+				<xsl:attribute name="align">
+				    <xsl:value-of select="$colspec/@align"/>
+				</xsl:attribute>
+			    </xsl:if>
+			    <xsl:if test="$colspec/@char">
+				<xsl:attribute name="char">
+				    <xsl:value-of select="$colspec/@char"/>
+				</xsl:attribute>
+			    </xsl:if>
+			    <xsl:if test="$colspec/@charoff">
+				<xsl:attribute name="charoff">
+				    <xsl:value-of select="$colspec/@charoff"/>
+				</xsl:attribute>
+			    </xsl:if>
+			</col>
+		    </xsl:when>
+		    <xsl:otherwise>
+			<xsl:call-template name="generate.col">
+			    <xsl:with-param name="countcol" select="$countcol"/>
+			    <xsl:with-param name="colspecs" select="$colspecs"/>
+			    <xsl:with-param name="count" select="$count+1"/>
+			    <xsl:with-param name="colnum">
+				<xsl:choose>
+				    <xsl:when test="$colspec/@colnum">
+					<xsl:value-of select="$colspec/@colnum + 1"/>
+				    </xsl:when>
+				    <xsl:otherwise>
+					<xsl:value-of select="$colnum + 1"/>
+				    </xsl:otherwise>
+				</xsl:choose>
+			    </xsl:with-param>
+			</xsl:call-template>
+		    </xsl:otherwise>
+		</xsl:choose>
+	    </xsl:otherwise>
+	</xsl:choose>
+
+    </xsl:template>
+
+    <xsl:template name="colspec.colnum">
+	<!-- when this macro is called, the current context must be an entry -->
+	<xsl:param name="colname"></xsl:param>
+	<!-- .. = row, ../.. = thead|tbody, ../../.. = tgroup -->
+	<xsl:param name="colspecs" select="../../../../tgroup/colspec"/>
+	<xsl:param name="count">1</xsl:param>
+	<xsl:param name="colnum">1</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="$count>count($colspecs)"></xsl:when>
+	    <xsl:otherwise>
+		<xsl:variable name="colspec" select="$colspecs[$count=position()]"/>
+		<!--
+		<xsl:value-of select="$count"/>:
+		<xsl:value-of select="$colspec/@colname"/>=
+		<xsl:value-of select="$colnum"/>
+		-->
+		<xsl:choose>
+		    <xsl:when test="$colspec/@colname=$colname">
+			<xsl:choose>
+			    <xsl:when test="$colspec/@colnum">
+				<xsl:value-of select="$colspec/@colnum"/>
+			    </xsl:when>
+			    <xsl:otherwise>
+				<xsl:value-of select="$colnum"/>
+			    </xsl:otherwise>
+			</xsl:choose>
+		    </xsl:when>
+		    <xsl:otherwise>
+			<xsl:call-template name="colspec.colnum">
+			    <xsl:with-param name="colname" select="$colname"/>
+			    <xsl:with-param name="colspecs" select="$colspecs"/>
+			    <xsl:with-param name="count" select="$count+1"/>
+			    <xsl:with-param name="colnum">
+				<xsl:choose>
+				    <xsl:when test="$colspec/@colnum">
+					<xsl:value-of select="$colspec/@colnum + 1"/>
+				    </xsl:when>
+				    <xsl:otherwise>
+					<xsl:value-of select="$colnum + 1"/>
+				    </xsl:otherwise>
+				</xsl:choose>
+			    </xsl:with-param>
+			</xsl:call-template>
+		    </xsl:otherwise>
+		</xsl:choose>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template name="colspec.colwidth">
+	<!-- when this macro is called, the current context must be an entry -->
+	<xsl:param name="colname"></xsl:param>
+	<!-- .. = row, ../.. = thead|tbody, ../../.. = tgroup -->
+	<xsl:param name="colspecs" select="../../../../tgroup/colspec"/>
+	<xsl:param name="count">1</xsl:param>
+	<xsl:choose>
+	    <xsl:when test="$count>count($colspecs)"></xsl:when>
+	    <xsl:otherwise>
+		<xsl:variable name="colspec" select="$colspecs[$count=position()]"/>
+		<xsl:choose>
+		    <xsl:when test="$colspec/@colname=$colname">
+			<xsl:value-of select="$colspec/@colwidth"/>
+		    </xsl:when>
+		    <xsl:otherwise>
+			<xsl:call-template name="colspec.colwidth">
+			    <xsl:with-param name="colname" select="$colname"/>
+			    <xsl:with-param name="colspecs" select="$colspecs"/>
+			    <xsl:with-param name="count" select="$count+1"/>
+			</xsl:call-template>
+		    </xsl:otherwise>
+		</xsl:choose>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template name="calculate.colspan">
+	<xsl:param name="namest" select="@namest"/>
+	<xsl:param name="nameend" select="@nameend"/>
+	<xsl:variable name="scol">
+	    <xsl:call-template name="colspec.colnum">
+		<xsl:with-param name="colname" select="$namest"/>
+	    </xsl:call-template>
+	</xsl:variable>
+	<xsl:variable name="ecol">
+	    <xsl:call-template name="colspec.colnum">
+		<xsl:with-param name="colname" select="$nameend"/>
+	    </xsl:call-template>
+	</xsl:variable>
+	<xsl:value-of select="$ecol - $scol + 1"/>
+    </xsl:template>
+
+	<!-- write docs:
+		The pre/post mechanism is to deal with multicolumn, which
+		needs to be the first command within a cell.
+	-->
+	<xsl:template name="generate.latex.cell.separator">
+		<xsl:param name="which"/>
+		<xsl:choose>
+			<xsl:when test="$which='pre'">
+				<xsl:if test="$latex.entities='catcode'">
+					<xsl:text> \catcode`\&amp;=4</xsl:text>
+				</xsl:if>
+				<xsl:text> &amp; </xsl:text>
+			</xsl:when>
+			<xsl:when test="$which='post'">
+				<xsl:if test="$latex.entities='catcode'">
+					<xsl:text>\catcode`\&amp;=\active </xsl:text>
+				</xsl:if>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:choose>
+					<xsl:when test="$latex.entities='catcode'">
+						<xsl:text> \catcode`\&amp;=4 &amp;\catcode`\&amp;=\active </xsl:text>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:text> &amp; </xsl:text>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/texmath.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/texmath.mod.xsl
new file mode 100644
index 00000000000..b17096a1820
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/texmath.mod.xsl
@@ -0,0 +1,259 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: texmath.mod.xsl,v 1.12 2004/01/03 03:19:08 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="texmath" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: texmath.mod.xsl,v 1.12 2004/01/03 03:19:08 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.11">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>&LaTeX;-only Commands <filename>texmath.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>alt</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara>
+					<xref linkend="param.tex.math.in.alt"/>
+				</simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				This template will modify its behaviour based upon its context
+				within a &DocBook; document.
+
+				If it is within an <doc:db>inlineequation</doc:db> and it has a
+				<sgmltag class="attribute">role</sgmltag> with the value of
+				<quote>latex</quote> or <quote>tex</quote>, then it will
+				typeset its contents inline as raw &LaTeX; input in mathematics
+				mode (using <function condition="latex">ensuremath</function>
+				command) if the variable <xref
+				linkend="param.tex.math.in.alt"/> is set.
+
+				If it is within an <doc:db>equation</doc:db> or
+				<doc:db>informalequation</doc:db> and it has a <sgmltag
+				class="attribute">role</sgmltag> with the value of
+				<quote>latex</quote> or <quote>tex</quote>, then it will
+				typeset its contents as raw &LaTeX; input in a <function
+				condition="env">displaymath</function> block environment if the
+				variable <xref linkend="param.tex.math.in.alt"/> is set.
+
+				Otherwise, if <xref linkend="param.tex.math.in.alt"/> is
+				set, the contents will be typeset as raw &LaTeX; input inline
+				(not in maths mode).
+
+				Otherwise, templates will be applied normally (not as raw
+				&LaTeX; input).
+
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				&test_theorem;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="alt">
+		<xsl:choose>
+			<xsl:when test="ancestor::inlineequation and (@role='tex' or @role='latex' or $tex.math.in.alt='plain' or $tex.math.in.alt='latex')">
+				<xsl:text>\ensuremath{</xsl:text>
+				<xsl:value-of select="."/>
+				<xsl:text>}</xsl:text>
+			</xsl:when>
+			<xsl:when test="(ancestor::equation|ancestor::informalequation) and (@role='tex' or @role='latex' or $tex.math.in.alt='plain' or $tex.math.in.alt='latex')">
+				<xsl:text>\begin{displaymath}</xsl:text>
+				<xsl:call-template name="label.id"/>
+				<xsl:value-of select="."/>
+				<xsl:text>\end{displaymath}&#10;</xsl:text>
+			</xsl:when>
+			<xsl:when test="$tex.math.in.alt='plain' or $tex.math.in.alt='latex'">
+				<xsl:value-of select="."/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:apply-templates/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag>latex</sgmltag> and <sgmltag>tex</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Passes contents through as raw &LaTeX; text.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				The <sgmltag>latex</sgmltag> and <sgmltag>tex</sgmltag> elements are not
+				part of &DocBook;.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="latex|tex">
+		<xsl:value-of select="."/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <sgmltag class="attribute">fileref</sgmltag> elements</refpurpose>
+		<doc:description>
+			<para>
+				Inputs a &LaTeX; file.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				For <sgmltag>latex</sgmltag> and <sgmltag>tex</sgmltag> elements with
+				<sgmltag class="attribute">fileref</sgmltag> attributes, their contents
+				are ignored and their fileref attributes are used as file paths for
+				the <function condition="latex">input</function> command.
+			</para>
+			<para>
+				The <sgmltag>latex</sgmltag> and <sgmltag>tex</sgmltag> elements are not
+				part of &DocBook;.
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="latex[@fileref]|tex[@fileref]">
+		<xsl:text>\input{</xsl:text><xsl:value-of select="@fileref"/><xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="tm[@fileref]">
+		<xsl:text>\input{</xsl:text><xsl:value-of select="@fileref"/><xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="tm[@tex]">
+		<xsl:value-of select="@tex"/>
+	</xsl:template>
+
+	<xsl:template match="inlinetm[@fileref]">
+		<xsl:text>\input{</xsl:text><xsl:value-of select="@fileref"/><xsl:text>}&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="inlinetm[@tex]">
+		<xsl:value-of select="@tex"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>inlineequation</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Process inline equations.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara>
+					<xref linkend="param.latex.alt.is.preferred"/>
+				</simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>
+
+				This template can accommodate raw &LaTeX; mathematics.
+
+				If the element has a
+				<sgmltag class="attribute">role</sgmltag> with a value of
+				<quote>latex</quote> or <quote>tex</quote>, or contains
+				an <doc:db>inlinemediaobject</doc:db>/<doc:db>textobject</doc:db>
+				or 
+				an <doc:db>inlinemediaobject</doc:db>/<doc:db>textobject</doc:db>/<doc:db>phrase</doc:db>
+				with such as attribute,
+				then it will
+				typeset then in preference to all other content.
+
+			</para>
+			<para>
+				
+				If such elements were not found, the template will search for
+				generic <doc:db>inlinemediaobject</doc:db> or
+				<doc:db>alt</doc:db> children. If <xref
+				linkend="param.latex.alt.is.preferred"/> is set, <sgmltag
+				basename="alt">alts</sgmltag> will be preferred over <sgmltag
+				basename="inlinemediaobject">inlinemediaobjects</sgmltag>. If
+				none of these elements was found, the template will format any
+				<doc:db>graphic</doc:db> children.
+				
+			</para>
+		</doc:notes>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_book;
+				<!--
+				&test_pavlov;
+				-->
+			</simplelist>
+		</doc:samples>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.alt"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.phrase"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template match="inlineequation">
+		<xsl:variable name="tex" select="alt[@role='tex' or @role='latex']|inlinemediaobject/textobject[@role='tex' or @role='latex']|inlinemediaobject/textobject/phrase[@role='tex' or @role='latex']" />
+		<xsl:choose>
+			<xsl:when test="$tex">
+				<xsl:apply-templates select="$tex"/>
+			</xsl:when>
+			<xsl:when test="alt and $latex.alt.is.preferred='1'">
+				<xsl:apply-templates select="alt"/>
+			</xsl:when>
+			<xsl:when test="inlinemediaobject">
+				<xsl:apply-templates select="inlinemediaobject"/>
+			</xsl:when>
+			<xsl:when test="alt">
+				<xsl:apply-templates select="alt"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:apply-templates select="graphic"/>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/verbatim.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/verbatim.mod.xsl
new file mode 100644
index 00000000000..7f6d26277da
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/verbatim.mod.xsl
@@ -0,0 +1,189 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: verbatim.mod.xsl,v 1.16 2004/01/31 11:53:14 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="verbatim" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: verbatim.mod.xsl,v 1.16 2004/01/31 11:53:14 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.12">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Verbatim <filename>verbatim.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+			
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose> Auxiliary template to output verbatim &LaTeX; code in verbatim mode </refpurpose>
+		<doc:description>
+			<para>Typeset verbatim, monospace text in which whitespace is significant.</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.use.fancyvrb"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:notes>
+			<para>This template is called by a number of element-related templates.</para>
+			<para> Takes into account whether the user is using fancyvrb or not. It allows
+			veratim line numbering and other fancy stuff. </para>
+			<para> In order to use a small or large font, you may also want to use 
+			implement <xref linkend="template.latex.fancyvrb.options"/>.
+			</para>
+			<!--
+			the <literal>role</literal> attribute: </para>
+	<screen><![CDATA[
+<programlisting role="small">
+</programlisting>
+<programlisting role="large">
+</programlisting>
+]]></screen>
+-->
+				<para>
+					This template will apply further templates using the
+					<literal>latex.verbatim</literal> mode.
+				</para>
+			<warning>
+				<para>
+					This doesn't work inside <doc:db basename="table">tables</doc:db>.
+					Also, if the element appears within a <doc:db>varlistentry</doc:db>,
+					some &LaTeX; code will be emitted so that the verbatim environment
+					starts on a new line.
+				</para>
+			</warning>
+		</doc:notes>
+		<doc:seealso>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="template.latex.fancyvrb.options"/></simpara></listitem>
+				<listitem><simpara><xref linkend="template.text()-latex.verbatim"/></simpara></listitem>
+			</itemizedlist>
+		</doc:seealso>
+	</doc:template>
+	<xsl:template name="verbatim.apply.templates">
+		<xsl:if test="ancestor::varlistentry">
+			<!-- start the environment on a new line -->
+			<xsl:text>\null{}</xsl:text>
+		</xsl:if>
+		<xsl:choose>
+			<xsl:when test="ancestor::entry">
+				<xsl:message>Problem with <xsl:value-of select="local-name(.)"/> inside table entries.</xsl:message>
+				<xsl:text>\texttt{</xsl:text>
+				<xsl:apply-templates mode="latex.verbatim"/>
+				<xsl:text>}</xsl:text>
+			</xsl:when>
+			<xsl:when test="$latex.use.fancyvrb='1'">
+				<xsl:variable name="not_monospaced" select="local-name(.)='literallayout' and @format!='monospaced'"/>
+				<xsl:text>&#10;\begin{Verbatim}[</xsl:text>
+				<xsl:if test="@linenumbering='numbered'">
+					<xsl:text>,numbers=left</xsl:text>
+				</xsl:if>
+				<xsl:if test="$not_monospaced">
+					<xsl:text>,fontfamily=default</xsl:text>
+				</xsl:if>
+				<xsl:call-template name="latex.fancyvrb.options"/>
+				<xsl:text>]&#10;</xsl:text>
+				<xsl:choose>
+					<xsl:when test="$not_monospaced">
+						<!-- Needs to be changed to cope with regular characterset! -->
+						<xsl:apply-templates mode="latex.verbatim"/>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:apply-templates mode="latex.verbatim"/>
+					</xsl:otherwise>
+				</xsl:choose>
+				<xsl:text>&#10;\end{Verbatim}&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>&#10;\begin{verbatim}&#10;</xsl:text>
+				<xsl:apply-templates mode="latex.verbatim"/>
+				<xsl:text>&#10;\end{verbatim}&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Process <quote>verbatim</quote> environment where whitespace is significant </refpurpose>
+		<doc:description>
+			<para>
+
+			Calls <xref linkend="template.verbatim.apply.templates"/>.
+
+			</para>
+		</doc:description>
+		<doc:variables>
+			<variablelist>
+				<varlistentry>
+					<term><xref linkend="param.latex.trim.verbatim"/></term>
+					<listitem><simpara>
+						See <xref linkend="text()-latex.verbatim"/>.
+						<!-- note: that is not a valid ID! -->
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:variables>
+		<doc:samples>
+			<simplelist type='inline'>
+				&test_article;
+				&test_bind;
+				&test_book;
+				&test_ddh;
+				&test_program;
+			</simplelist>
+		</doc:samples>
+	</doc:template>
+	<xsl:template match="address|screen|programlisting|literallayout">
+		<xsl:call-template name="verbatim.apply.templates"/>
+	</xsl:template>
+
+	<xsl:template name="next.is.verbatim">
+		<xsl:param name="object" select="following-sibling::*[1]"/>
+		<xsl:value-of select="count($object[self::address or self::screen or self::programlisting or self::literallayout])"/>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>literal</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+			
+			Applies templates in the <quote>template.latex.verbatim</quote>
+			mode within a &LaTeX; <function condition="latex">verb</function>
+			command.
+			
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+	</doc:template>
+	<xsl:template match="literal" mode="latex.verbatim">
+		<xsl:text>{\verb </xsl:text>
+		<xsl:apply-templates mode="latex.verbatim"/>
+		<xsl:text>}</xsl:text>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/xref.mod.xsl b/docs-xml/xslt/db2latex-xsl/xsl/xref.mod.xsl
new file mode 100644
index 00000000000..c03f9a0916e
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/xref.mod.xsl
@@ -0,0 +1,1208 @@
+<?xml version='1.0'?>
+<!DOCTYPE xsl:stylesheet [ <!ENTITY % xsldoc.ent SYSTEM "./xsldoc.ent"> %xsldoc.ent; ]>
+<!--############################################################################# 
+|	$Id: xref.mod.xsl,v 1.41 2004/01/28 02:07:08 j-devenish Exp $
+|- #############################################################################
+|	$Author: j-devenish $
++ ############################################################################## -->
+
+<xsl:stylesheet
+	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc" version='1.0'>
+
+	<doc:reference id="xref" xmlns="">
+		<referenceinfo>
+			<releaseinfo role="meta">
+				$Id: xref.mod.xsl,v 1.41 2004/01/28 02:07:08 j-devenish Exp $
+			</releaseinfo>
+			<authorgroup>
+				&ramon;
+				&james;
+			</authorgroup>
+			<copyright>
+				<year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
+				<holder>Ramon Casellas</holder>
+			</copyright>
+			<revhistory>
+				<doc:revision rcasver="1.12">&rev_2003_05;</doc:revision>
+			</revhistory>
+		</referenceinfo>
+		<title>Cross References <filename>xref.mod.xsl</filename></title>
+		<partintro>
+			<para>
+			
+				Portions (c) Norman Walsh, official DocBook XSL stylesheets. See docbook.sf.net
+			
+			</para>
+		</partintro>
+	</doc:reference>
+
+	<doc:template xmlns="">
+		<refpurpose>Process <doc:db>anchor</doc:db> elements</refpurpose>
+		<doc:description>
+			<para>
+				Identify a place in the document for cross references.
+			</para>
+		</doc:description>
+		<doc:variables>
+			&no_var;
+		</doc:variables>
+		<doc:notes>
+			<para>
+				Inserts a &LaTeX; <function condition="latex">hypertarget</function>
+				with the current node's id value and no content.
+				<doc:todo>Check to see whether this causes typesetting problems
+				with <command>latex</command> (as opposed to
+				<command>pdflatex</command>) due to insertion of errant
+				<literal>pdfmark</literal>s.</doc:todo>
+			</para>
+		</doc:notes>
+	</doc:template>
+	<xsl:template match="anchor">
+		<xsl:param name="id" select="@id"/>
+		<xsl:text>\hypertarget{</xsl:text>
+		<xsl:value-of select="$id"/>
+		<xsl:text>}{}</xsl:text>
+	</xsl:template>
+
+	<xsl:key name="cross-refs" match="xref|link" use="@linkend"/>
+	<doc:template name="id.is.xrefed" xmlns="">
+		<refpurpose>Auxiliary named template</refpurpose>
+		<doc:description>
+		<para>This template returns 1 if there exists somewhere an xref
+		or link whose linkend is the target's id.</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template name="id.is.xrefed">
+		<xsl:param name="target" select="."/>
+		<xsl:variable name="id">
+			<xsl:call-template name="generate.label.id">
+				<xsl:with-param name="object" select="$target"/>
+			</xsl:call-template>
+		</xsl:variable>
+		<xsl:choose>
+			<xsl:when test="count(key('cross-refs', $id))&gt;0">
+				<xsl:text>1</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>0</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+<doc:template name="xref.xreflabel" xmlns="">
+  <refpurpose>Auxiliary named template</refpurpose>
+  <doc:description>
+    <para> Called to process an xreflabel...you might use this to make 
+     xreflabels come out in the right font for different targets, 
+	 for example.</para>
+  </doc:description>
+</doc:template>
+    <xsl:template name="xref.xreflabel">
+	<xsl:param name="target" select="."/>
+	<xsl:value-of select="$target/@xreflabel"/>
+    </xsl:template>
+
+	<doc:template match="xref|link" xmlns="">
+		<refpurpose>Xref and Link XSL Template</refpurpose>
+		<doc:description>
+			<para>
+				<doc:todo>Undocumented.</doc:todo>
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.insert.xref.page.number"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.varioref"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+	</doc:template>
+    <xsl:template match="xref|link">
+	<xsl:variable name="targets" select="key('id',@linkend)"/>
+	<xsl:variable name="target" select="$targets[1]"/>
+	<xsl:variable name="refelem" select="local-name($target)"/>
+	<xsl:call-template name="check.id.unique"><xsl:with-param name="linkend" select="@linkend"/></xsl:call-template>
+	<xsl:choose>
+	    <xsl:when test="$refelem=''">
+		<xsl:message><xsl:text>XRef to nonexistent id: </xsl:text><xsl:value-of select="@linkend"/></xsl:message>
+		<xsl:text>XrefId[?</xsl:text>
+		<xsl:if test="local-name(.)='link'"><xsl:apply-templates/></xsl:if>
+		<xsl:text>?]</xsl:text>
+	    </xsl:when>
+
+	    <!-- This is a link with content ... -->
+		<xsl:when test="local-name(.)='link' and .!=''">
+		<xsl:call-template name="generate.hyperlink">
+			<xsl:with-param name="target" select="$target"/>
+			<xsl:with-param name="text"><xsl:apply-templates/></xsl:with-param>
+		</xsl:call-template>
+		</xsl:when>
+		
+	    <xsl:otherwise>
+		<xsl:choose>
+		    <xsl:when test="@endterm">
+			<xsl:variable name="etargets" select="key('id',@endterm)"/>
+			<xsl:variable name="etarget" select="$etargets[1]"/>
+			<xsl:choose>
+			    <xsl:when test="count($etarget) = 0">
+				<xsl:message>
+				    <xsl:value-of select="count($etargets)"/>
+				    <xsl:text>Endterm points to nonexistent ID: </xsl:text>
+				    <xsl:value-of select="@endterm"/>
+				</xsl:message>
+				<xsl:text>[NONEXISTENT ID]</xsl:text>
+			    </xsl:when>
+			    <xsl:otherwise>
+				<xsl:call-template name="generate.hyperlink">
+					<xsl:with-param name="target" select="$target"/>
+					<xsl:with-param name="text">
+						<xsl:call-template name="generate.xref.text">
+							<xsl:with-param name="target" select="$etarget"/>
+						</xsl:call-template>
+					</xsl:with-param>
+				</xsl:call-template>
+			    </xsl:otherwise>
+			</xsl:choose>
+		    </xsl:when>
+			<!-- If an xreflabel has been specified for the target ... -->
+			<xsl:when test="local-name(.)='xref' and $target/@xreflabel">
+			<xsl:call-template name="generate.hyperlink">
+				<xsl:with-param name="target" select="$target"/>
+				<xsl:with-param name="text">
+					<xsl:text>{[</xsl:text>
+					<xsl:call-template name="xref.xreflabel">
+						<xsl:with-param name="target" select="$target"/>
+					</xsl:call-template>
+					<xsl:text>]}</xsl:text>
+				</xsl:with-param>
+			</xsl:call-template>
+			</xsl:when>
+		    <xsl:otherwise>
+				<xsl:call-template name="generate.hyperlink">
+					<xsl:with-param name="target" select="$target"/>
+					<xsl:with-param name="text">
+						<xsl:call-template name="generate.xref.text">
+							<xsl:with-param name="target" select="$target"/>
+						</xsl:call-template>
+					</xsl:with-param>
+				</xsl:call-template>
+		    </xsl:otherwise>
+		</xsl:choose>
+	    </xsl:otherwise>
+	</xsl:choose>
+	<xsl:if test="$insert.xref.page.number=1 and not($latex.use.varioref='1') and $refelem!='' and local-name(.)='xref'">
+		<xsl:variable name="xref.text">
+			<xsl:call-template name="gentext.template">
+				<xsl:with-param name="context" select="'xref'"/>
+				<xsl:with-param name="name" select="'page.citation'"/>
+			</xsl:call-template>
+		</xsl:variable>
+		<xsl:for-each select="$target">
+			<xsl:call-template name="substitute-markup">
+				<xsl:with-param name="template" select="$xref.text"/>
+			</xsl:call-template>
+		</xsl:for-each>
+	</xsl:if>
+</xsl:template>
+
+	<doc:template>
+		<refpurpose> Generate xref text </refpurpose>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.use.role.as.xrefstyle"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+	</doc:template>
+	<xsl:template name="generate.xref.text">
+		<xsl:param name="target"/>
+        <xsl:apply-templates select="$target" mode="xref-to">
+          <xsl:with-param name="referrer" select="."/>
+          <xsl:with-param name="xrefstyle">
+            <xsl:choose>
+              <xsl:when test="@role and not(@xrefstyle) and $use.role.as.xrefstyle != 0">
+                <xsl:value-of select="@role"/>
+              </xsl:when>
+              <xsl:when test="@xrefstyle">
+                <xsl:value-of select="@xrefstyle"/>
+              </xsl:when>
+              <xsl:when test="local-name($target)='title' or local-name($target)='subtitle'">
+               <xsl:value-of select="concat(local-name($target), '-unnumbered')"/>
+              </xsl:when>
+              <xsl:otherwise>
+               <xsl:text>xref-number</xsl:text>
+              </xsl:otherwise>
+            </xsl:choose>
+          </xsl:with-param>
+        </xsl:apply-templates>
+	</xsl:template>
+
+	<doc:template name="generate.hyperlink" xmlns="">
+	<refpurpose> Choose hyperlink syntax </refpurpose>
+	<doc:description>
+		<para>Will use hyperref, if it is available. Otherwise, just outputs
+		unlinked text. If the destination is a citation, a backreference is
+		emitted (even though it is technically a hyperlink, not a citation).
+		If the 'text' arises from an @endterm, then the 'optional argument'
+		syntax of <literal>\cite</literal> is used.</para>
+	</doc:description>
+	</doc:template>
+	<xsl:template name="generate.hyperlink">
+		<xsl:param name="target"/>
+		<xsl:param name="text"/>
+		<xsl:variable name="element" select="local-name($target)"/>
+		<xsl:variable name="citation" select="$element='biblioentry' or $element='bibliomixed'"/>
+		<xsl:choose>
+			<xsl:when test="$citation and @endterm!=''">
+				<xsl:text>\docbooktolatexcite</xsl:text>
+				<xsl:text>{</xsl:text>
+				<xsl:value-of select="$target/@id"/>
+				<xsl:text>}{</xsl:text>
+				<xsl:call-template name="scape-optionalarg">
+					<xsl:with-param name="string" select="$text"/>
+				</xsl:call-template>
+				<xsl:text>}</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:if test="$latex.use.hyperref=1 and not(ancestor::title)">
+					<xsl:text>\hyperlink{</xsl:text>
+					<xsl:value-of select="$target/@id"/>
+					<xsl:text>}</xsl:text>
+				</xsl:if>
+				<xsl:text>{</xsl:text>
+				<xsl:if test="$citation">
+					<xsl:text>\docbooktolatexbackcite{</xsl:text>
+					<xsl:value-of select="$target/@id"/>
+					<xsl:text>}</xsl:text>
+				</xsl:if>
+				<xsl:value-of select="$text"/>
+				<xsl:text>}</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template basename="insert.label.markup" xmlns="">
+		<refpurpose>Numbering template</refpurpose>
+		<doc:description>
+			<para>
+			Let &LaTeX; manage the numbering. Otherwise sty files that
+			do specify another numberic (e.g I,II) get messed.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.insert.xref.page.number"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.varioref"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+	</doc:template>
+    <xsl:template match="*" mode="insert.label.markup" name="insert.label.markup">
+		<xsl:param name="id" select="@id"/>
+		<xsl:choose>
+			<xsl:when test="$insert.xref.page.number=1 and $latex.use.varioref='1'">
+				<xsl:text>{\vref{</xsl:text><xsl:value-of select="$id"/><xsl:text>}}</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>{\ref{</xsl:text><xsl:value-of select="$id"/><xsl:text>}}</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+    </xsl:template>
+
+	<doc:template basename="insert.label.markup" xmlns="">
+		<refpurpose>Numbering template -- uses parent's @id</refpurpose>
+		<doc:description>
+			<para>
+			Calls <xref linkend="template.insert.label.markup"/> using parent's @id.
+			</para>
+		</doc:description>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.insert.xref.page.number"/></simpara></listitem>
+				<listitem><simpara><xref linkend="param.latex.use.varioref"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+	</doc:template>
+    <xsl:template match="title" mode="insert.label.markup">
+		<xsl:call-template name="insert.label.markup">
+			<xsl:with-param name="id">
+				<xsl:choose>
+					<xsl:when test="contains(local-name(..), 'info')">
+						<xsl:call-template name="generate.label.id">
+							<xsl:with-param name="object" select="../.."/>
+						</xsl:call-template>
+					</xsl:when>
+					<xsl:otherwise>
+						<xsl:call-template name="generate.label.id">
+							<xsl:with-param name="object" select=".."/>
+						</xsl:call-template>
+					</xsl:otherwise>
+				</xsl:choose>
+			</xsl:with-param>
+		</xsl:call-template>
+    </xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Format titles in xref text </refpurpose>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>title</term>
+					<listitem><simpara>The text. This is expected to
+					be received from gentext.xsl, in which case it will
+					contain no deliberate &LaTeX; commands and must be
+					escaped.</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>is.component</term>
+					<listitem><simpara>Whether the node is considered
+					to be a <quote>component</quote> in the sense of &DocBook;.
+					If so, the formatting of the title may be different. By default,
+					the determination of component elements is performed by the
+					<literal>is.component</literal> template in
+					<filename>common.xsl</filename>.</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:description>
+			<para>
+				Calls <xref linkend="template.normalize-scape"/>. If the node
+				is a component type (e.g. appendix, article, chapter, preface,
+				bibliography, glossary or index) then gentext.startquote and
+				gentext.endquote are placed around the title.
+			</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="*" mode="insert.title.markup" name="generate.title.markup">
+		<xsl:param name="title"/>
+		<xsl:param name="is.component">
+			<xsl:call-template name="is.component"/>
+		</xsl:param>
+		<xsl:choose>
+			<xsl:when test="$is.component=1">
+				<xsl:call-template name="gentext.startquote"/>
+				<xsl:call-template name="normalize-scape">
+					<xsl:with-param name="string" select="$title"/>
+				</xsl:call-template>
+				<xsl:call-template name="gentext.endquote"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="normalize-scape">
+					<xsl:with-param name="string" select="$title"/>
+				</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Format titles in xref text </refpurpose>
+		<doc:params>
+			<variablelist>
+				<varlistentry>
+					<term>title</term>
+					<listitem><simpara>The text.</simpara></listitem>
+				</varlistentry>
+				<varlistentry>
+					<term>is.component</term>
+					<listitem><simpara>Whether the node's parent is considered
+					to be a <quote>component</quote> in the sense of &DocBook;.
+					</simpara></listitem>
+				</varlistentry>
+			</variablelist>
+		</doc:params>
+		<doc:description>
+			<para>
+				Calls <xref linkend="template.generate.title.markup"/>.
+			</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="title" mode="insert.title.markup">
+		<xsl:param name="title"/>
+		<xsl:param name="is.component">
+			<xsl:choose>
+				<xsl:when test="contains(local-name(..), 'info')">
+					<xsl:call-template name="is.component">
+						<xsl:with-param name="node" select="../.."/>
+					</xsl:call-template>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:call-template name="is.component">
+						<xsl:with-param name="node" select=".."/>
+					</xsl:call-template>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:param>
+		<xsl:call-template name="generate.title.markup">
+			<xsl:with-param name="title" select="$title"/>
+			<xsl:with-param name="is.component" select="$is.component"/>
+		</xsl:call-template>
+	</xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Format titles in xref text </refpurpose>
+		<doc:description>
+			<para>
+				Does not add quotation marks around the title
+				but does italicise it.
+			</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template match="book" mode="insert.title.markup">
+		<xsl:param name="title"/>
+		<xsl:text>{\textit{</xsl:text>
+		<xsl:call-template name="normalize-scape">
+			<xsl:with-param name="string" select="$title"/>
+		</xsl:call-template>
+		<xsl:text>}}</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="*" mode="insert.subtitle.markup">
+		<xsl:message>Warning: unexpected insert.subtitle.markup in DB2LaTeX</xsl:message>
+	</xsl:template>
+
+	<xsl:template match="*" mode="insert.pagenumber.markup">
+		<xsl:param name="target" select="."/>
+		<xsl:choose>
+			<xsl:when test="$latex.use.varioref='1'">
+				<xsl:variable name="options"><xsl:call-template name="latex.vpageref.options"/></xsl:variable>
+				<xsl:text>\vpageref</xsl:text>
+				<xsl:if test="$options!=''">
+					<xsl:choose>
+						<xsl:when test="contains($options,'[')">
+							<xsl:value-of select="$options"/>
+						</xsl:when>
+						<xsl:otherwise>
+							<xsl:text>[</xsl:text>
+							<xsl:value-of select="$options"/>
+							<xsl:text>]</xsl:text>
+						</xsl:otherwise>
+					</xsl:choose>
+				</xsl:if>
+				<xsl:text>{</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>\pageref{</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:value-of select="$target/@id"/>
+		<xsl:text>}</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="*" mode="insert.direction.markup">
+		<xsl:message>Warning: unexpected insert.direction.markup in DB2LaTeX</xsl:message>
+	</xsl:template>
+
+<doc:template match="ulink" xmlns="">
+  <refpurpose>A link that addresses its target by means of a URL (Uniform Resource Locator)</refpurpose>
+  <doc:variables>
+	<itemizedlist>
+		<listitem><simpara><xref linkend="param.ulink.show"/></simpara></listitem>
+		<listitem><simpara><xref linkend="param.ulink.footnotes"/></simpara></listitem>
+		<listitem><simpara><xref linkend="param.latex.ulink.protocols.relaxed"/></simpara></listitem>
+		<listitem><simpara><xref linkend="param.latex.hyphenation.tttricks"/></simpara></listitem>
+	</itemizedlist>
+  </doc:variables>
+</doc:template>
+    <xsl:template match="ulink" name="ulink">
+	<xsl:param name="hyphenation">\docbookhyphenateurl</xsl:param>
+	<xsl:param name="url" select="@url"/>
+	<xsl:param name="content">
+		<xsl:call-template name="trim-outer">
+			<xsl:with-param name="string" select="."/>
+		</xsl:call-template>
+	</xsl:param>
+	<xsl:choose>
+		<xsl:when test="$content = '' or $content = $url">
+			<xsl:call-template name="generate.typeset.url">
+				<xsl:with-param name="hyphenation" select="$hyphenation"/>
+				<xsl:with-param name="url" select="$url"/>
+				<xsl:with-param name="prepend" select="''"/>
+			</xsl:call-template>
+		</xsl:when>
+		<xsl:when test="$latex.ulink.protocols.relaxed='1' and (substring-after($url,':')=$content or substring-after($url,'://')=$content)">
+			<xsl:call-template name="generate.typeset.url">
+				<xsl:with-param name="hyphenation" select="$hyphenation"/>
+				<xsl:with-param name="url" select="$content"/>
+				<xsl:with-param name="prepend" select="''"/>
+			</xsl:call-template>
+			<xsl:if test="$ulink.footnotes='1' and count(ancestor::footnote)=0">
+				<xsl:call-template name="generate.ulink.in.footnote">
+					<xsl:with-param name="hyphenation" select="$hyphenation"/>
+					<xsl:with-param name="url" select="$url"/>
+				</xsl:call-template>
+			</xsl:if>
+		</xsl:when>
+		<xsl:when test="$latex.use.tabularx=1 and count(ancestor::table)&gt;0">
+			<xsl:apply-templates/>
+			<xsl:call-template name="generate.typeset.url">
+				<xsl:with-param name="hyphenation" select="$hyphenation"/>
+				<xsl:with-param name="url" select="$url"/>
+			</xsl:call-template>
+		</xsl:when>
+		<xsl:when test="$ulink.footnotes='1' or $ulink.show='1'">
+			<xsl:apply-templates/>
+			<xsl:if test="$ulink.footnotes='1' and count(ancestor::footnote)=0">
+				<xsl:call-template name="generate.ulink.in.footnote">
+					<xsl:with-param name="hyphenation" select="$hyphenation"/>
+					<xsl:with-param name="url" select="$url"/>
+				</xsl:call-template>
+			</xsl:if>
+			<xsl:if test="$ulink.show='1' or ($ulink.footnotes='1' and ancestor::footnote)">
+				<xsl:call-template name="generate.typeset.url">
+					<xsl:with-param name="hyphenation" select="$hyphenation"/>
+					<xsl:with-param name="url" select="$url"/>
+				</xsl:call-template>
+			</xsl:if>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:text>\href{</xsl:text>
+				<xsl:call-template name="scape-href">
+					<xsl:with-param name="string" select="$url"/>
+				</xsl:call-template>
+			<xsl:text>}</xsl:text>
+			<xsl:text>{</xsl:text>
+				<xsl:apply-templates/>
+			<xsl:text>}</xsl:text><!-- End Of second argument of \href -->
+		</xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+<doc:template match="olink" xmlns="">
+  <refpurpose>OLink XSL template</refpurpose>
+  <doc:description>
+  <para></para>
+  </doc:description>
+</doc:template>
+    <xsl:template match="olink">
+		<xsl:apply-templates/>
+    </xsl:template>
+
+    <xsl:template match="*" name="title.xref">
+	<xsl:param name="target" select="."/>
+	<xsl:choose>
+	    <xsl:when test="name($target) = 'figure'
+		or name($target) = 'example'
+		or name($target) = 'equation'
+		or name($target) = 'table'
+		or name($target) = 'dedication'
+		or name($target) = 'preface'
+		or name($target) = 'bibliography'
+		or name($target) = 'glossary'
+		or name($target) = 'index'
+		or name($target) = 'setindex'
+		or name($target) = 'colophon'">
+		<xsl:call-template name="gentext.startquote"/>
+		<xsl:apply-templates select="$target" mode="title.content"/>
+		<xsl:call-template name="gentext.endquote"/>
+	    </xsl:when>
+	    <xsl:otherwise>
+		<xsl:text>{\em </xsl:text><xsl:apply-templates select="$target" mode="title.content"/><xsl:text>}</xsl:text>
+	    </xsl:otherwise>
+	</xsl:choose>
+    </xsl:template>
+
+    <xsl:template match="title" mode="xref">
+	<xsl:apply-templates/>
+    </xsl:template>
+
+    <xsl:template match="command" mode="xref">
+	<xsl:call-template name="inline.boldseq"/>
+    </xsl:template>
+
+    <xsl:template match="function" mode="xref">
+	<xsl:call-template name="inline.monoseq"/>
+    </xsl:template>
+
+	<doc:template xmlns="">
+		<refpurpose> Typeset a URL using the <function condition="latex">url</function> or <function condition="latex">href</function> commands </refpurpose>
+		<doc:variables>
+			<itemizedlist>
+				<listitem><simpara><xref linkend="param.latex.url.quotation"/></simpara></listitem>
+			</itemizedlist>
+		</doc:variables>
+		<doc:description>
+			<para>If <xref linkend="param.latex.url.quotation"/> is set,
+			the <quote>urlstartquote</quote> and <quote>urlendquote</quote>
+			gentext dingbats will be emitted.</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template name="generate.typeset.url">
+		<xsl:param name="hyphenation"/>
+		<xsl:param name="url" select="@url"/>
+		<xsl:param name="prepend" select="' '"/>
+		<xsl:value-of select="$prepend"/>
+		<xsl:if test="$latex.url.quotation=1">
+			<xsl:call-template name="gentext.dingbat">
+				<xsl:with-param name="dingbat">urlstartquote</xsl:with-param>
+			</xsl:call-template>
+		</xsl:if>
+		<xsl:choose>
+			<xsl:when test="$latex.use.url='1'">
+				<xsl:text>\url{</xsl:text>
+				<xsl:call-template name="scape-url">
+					<xsl:with-param name="string" select="$url"/>
+				</xsl:call-template>
+				<xsl:text>}</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>\href{</xsl:text>
+				<xsl:call-template name="scape-href">
+					<xsl:with-param name="string" select="$url"/>
+				</xsl:call-template>
+				<xsl:text>}{\texttt{</xsl:text>
+				<xsl:call-template name="generate.string.url">
+					<xsl:with-param name="hyphenation" select="$hyphenation"/>
+					<xsl:with-param name="string" select="$url"/>
+				</xsl:call-template>
+				<xsl:text>}}</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:if test="$latex.url.quotation=1">
+			<xsl:call-template name="gentext.dingbat">
+				<xsl:with-param name="dingbat">urlendquote</xsl:with-param>
+			</xsl:call-template>
+		</xsl:if>
+	</xsl:template>
+
+	<doc:template name="generate.string.url" xmlns="">
+		<refpurpose>Escape and hyphenate a string as a teletype URL.</refpurpose>
+		<doc:description>
+		<para>
+		This template typsets teletype text using slash.hyphen if
+		$latex.hyphenation.tttricks is disabled.
+		Has two parameters: 'hyphenation' and 'string'.
+		</para>
+		</doc:description>
+	</doc:template>
+	<xsl:template name="generate.string.url">
+		<xsl:param name="hyphenation" />
+		<xsl:param name="string" />
+		<xsl:param name="url" select="$string"/>
+		<xsl:choose>
+			<xsl:when test="$latex.hyphenation.tttricks=1">
+				<xsl:value-of select="$hyphenation" />
+				<xsl:text>{</xsl:text>
+				<xsl:call-template name="normalize-scape"><xsl:with-param name="string" select="$string"/></xsl:call-template>
+				<xsl:text>}</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<!-- LaTeX chars are scaped. Each / except the :// is mapped to a /\- -->
+				<xsl:call-template name="scape.slash.hyphen"><xsl:with-param name="string" select="$url"/></xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<xsl:template name="xpath.location">
+	<!-- abbreviated -->
+		<xsl:param name="node" select="."/>
+		<xsl:value-of select="local-name($node)"/>
+	</xsl:template>
+
+<xsl:template match="*" mode="object.xref.template">
+  <xsl:param name="purpose"/>
+  <xsl:param name="xrefstyle"/>
+  <xsl:param name="referrer"/>
+
+  <xsl:variable name="user-template">
+	<xsl:if test="$xrefstyle != '' and not(contains($xrefstyle, ':'))">
+    <xsl:call-template name="gentext.template.exists">
+      <xsl:with-param name="context" select="$xrefstyle"/>
+      <xsl:with-param name="name">
+        <xsl:call-template name="xpath.location"/>
+      </xsl:with-param>
+    </xsl:call-template>
+	</xsl:if>
+  </xsl:variable>
+
+  <xsl:variable name="context">
+    <xsl:choose>
+      <xsl:when test="$user-template = 1">
+         <xsl:value-of select="$xrefstyle"/>
+      </xsl:when>
+      <xsl:otherwise>
+         <xsl:value-of select="'xref'"/>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:call-template name="gentext.template">
+    <xsl:with-param name="context" select="$context"/>
+    <xsl:with-param name="name">
+      <xsl:call-template name="xpath.location"/>
+    </xsl:with-param>
+    <xsl:with-param name="purpose" select="$purpose"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:call-template>
+
+</xsl:template>
+
+<xsl:template match="*" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:message>
+    <xsl:text>Don't know what gentext to create for xref to: "</xsl:text>
+    <xsl:value-of select="name(.)"/>
+    <xsl:text>"</xsl:text>
+  </xsl:message>
+  <xsl:text>?</xsl:text>
+  <xsl:value-of select="$referrer/@linkend"/>
+  <xsl:text>?</xsl:text>
+</xsl:template>
+
+<xsl:template match="title" mode="xref-to">
+	<xsl:param name="referrer"/>
+	<xsl:param name="purpose"/>
+	<xsl:param name="xrefstyle"/>
+	<xsl:param name="name">
+		<xsl:choose>
+			<xsl:when test="contains(local-name(parent::*), 'info')">
+				<xsl:call-template name="xpath.location">
+					<xsl:with-param name="node" select="../.."/>
+				</xsl:call-template>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:call-template name="xpath.location">
+					<xsl:with-param name="node" select=".."/>
+				</xsl:call-template>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:param>
+
+	<xsl:variable name="template">
+		<xsl:variable name="user-template">
+			<xsl:if test="$xrefstyle != '' and not(contains($xrefstyle, ':'))">
+				<xsl:call-template name="gentext.template.exists">
+					<xsl:with-param name="context" select="$xrefstyle"/>
+					<xsl:with-param name="name" select="$name"/>
+				</xsl:call-template>
+			</xsl:if>
+		</xsl:variable>
+		<xsl:variable name="context">
+			<xsl:choose>
+				<xsl:when test="$user-template = 1">
+					<xsl:value-of select="$xrefstyle"/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:value-of select="'title'"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+		<xsl:call-template name="gentext.template">
+			<xsl:with-param name="context" select="$context"/>
+			<xsl:with-param name="name" select="$name"/>
+			<xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+			<xsl:with-param name="purpose" select="$purpose"/>
+			<xsl:with-param name="referrer" select="$referrer"/>
+		</xsl:call-template>
+	</xsl:variable>
+
+	<xsl:call-template name="substitute-markup">
+		<xsl:with-param name="purpose" select="$purpose"/>
+		<xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+		<xsl:with-param name="referrer" select="$referrer"/>
+		<xsl:with-param name="template" select="$template"/>
+	</xsl:call-template>
+</xsl:template>
+
+<xsl:template match="abstract|article|authorblurb|bibliodiv|bibliomset
+                     |biblioset|blockquote|calloutlist|caution|colophon
+                     |constraintdef|formalpara|glossdiv|important|indexdiv
+                     |itemizedlist|legalnotice|lot|msg|msgexplan|msgmain
+                     |msgrel|msgset|msgsub|note|orderedlist|partintro
+                     |productionset|qandadiv|refsynopsisdiv|segmentedlist
+                     |set|setindex|sidebar|tip|toc|variablelist|warning"
+              mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <!-- catch-all for things with (possibly optional) titles -->
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="author|editor|othercredit|personname" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:call-template name="person.name"/>
+</xsl:template>
+
+<xsl:template match="authorgroup" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:call-template name="person.name.list"/>
+</xsl:template>
+
+<xsl:template match="figure|example|table|equation" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="procedure" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="cmdsynopsis" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="(.//command)[1]" mode="xref"/>
+</xsl:template>
+
+<xsl:template match="funcsynopsis" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="(.//function)[1]" mode="xref"/>
+</xsl:template>
+
+<xsl:template match="dedication|preface|chapter|appendix" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="bibliography" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<!--
+<xsl:template match="biblioentry|bibliomixed" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:text>[</xsl:text>
+  <xsl:choose>
+    <xsl:when test="string(.) = ''">
+      <xsl:variable name="bib" select="document($bibliography.collection)"/>
+      <xsl:variable name="id" select="@id"/>
+      <xsl:variable name="entry" select="$bib/bibliography/*[@id=$id][1]"/>
+      <xsl:choose>
+        <xsl:when test="$entry">
+          <xsl:choose>
+            <xsl:when test="$bibliography.numbered != 0">
+              <xsl:number from="bibliography" count="biblioentry|bibliomixed"
+                          level="any" format="1"/>
+            </xsl:when>
+            <xsl:when test="local-name($entry/*[1]) = 'abbrev'">
+              <xsl:apply-templates select="$entry/*[1]"/>
+            </xsl:when>
+            <xsl:otherwise>
+              <xsl:value-of select="@id"/>
+            </xsl:otherwise>
+          </xsl:choose>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:message>
+            <xsl:text>No bibliography entry: </xsl:text>
+            <xsl:value-of select="$id"/>
+            <xsl:text> found in </xsl:text>
+            <xsl:value-of select="$bibliography.collection"/>
+          </xsl:message>
+          <xsl:value-of select="@id"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:choose>
+        <xsl:when test="$bibliography.numbered != 0">
+          <xsl:number from="bibliography" count="biblioentry|bibliomixed"
+                      level="any" format="1"/>
+        </xsl:when>
+        <xsl:when test="local-name(*[1]) = 'abbrev'">
+          <xsl:apply-templates select="*[1]"/>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:value-of select="@id"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:otherwise>
+  </xsl:choose>
+  <xsl:text>]</xsl:text>
+</xsl:template>
+-->
+
+<xsl:template match="glossary" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="glossentry" mode="xref-to">
+  <xsl:choose>
+    <xsl:when test="$glossentry.show.acronym = 'primary'">
+      <xsl:choose>
+        <xsl:when test="acronym|abbrev">
+          <xsl:apply-templates select="(acronym|abbrev)[1]"/>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:apply-templates select="glossterm[1]" mode="xref-to"/>
+        </xsl:otherwise>
+      </xsl:choose>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates select="glossterm[1]" mode="xref-to"/>
+    </xsl:otherwise>
+  </xsl:choose>
+</xsl:template>
+
+<xsl:template match="glossterm" mode="xref-to">
+  <xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="index" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="listitem" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="section|simplesect
+                     |sect1|sect2|sect3|sect4|sect5
+                     |refsect1|refsect2|refsect3" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+  <!-- What about "in Chapter X"? -->
+</xsl:template>
+
+<xsl:template match="bridgehead" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+  <!-- What about "in Chapter X"? -->
+</xsl:template>
+
+<xsl:template match="qandaset" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="qandadiv" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="qandaentry" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="question[1]" mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="question|answer" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="part|reference" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="refentry" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:choose>
+    <xsl:when test="refmeta/refentrytitle">
+      <xsl:apply-templates select="refmeta/refentrytitle"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:apply-templates select="refnamediv/refname[1]"/>
+    </xsl:otherwise>
+  </xsl:choose>
+  <xsl:apply-templates select="refmeta/manvolnum"/>
+</xsl:template>
+
+<xsl:template match="refnamediv" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="refname[1]" mode="xref-to">
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="refname" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates mode="xref-to">
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="step" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:call-template name="gentext">
+    <xsl:with-param name="key" select="'Step'"/>
+  </xsl:call-template>
+  <xsl:text> </xsl:text>
+  <xsl:apply-templates select="." mode="number"/>
+</xsl:template>
+
+<xsl:template match="varlistentry" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="term[1]" mode="xref-to">
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="varlistentry/term" mode="xref-to">
+  <!-- to avoid the comma that will be generated if there are several terms -->
+  <xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="co" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="callout-bug"/>
+</xsl:template>
+
+<xsl:template match="book" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+</xsl:template>
+
+<xsl:template match="para" mode="xref-to">
+  <xsl:param name="referrer"/>
+  <xsl:param name="xrefstyle"/>
+
+  <xsl:variable name="context" select="(ancestor::simplesect
+                                       |ancestor::section
+                                       |ancestor::sect1
+                                       |ancestor::sect2
+                                       |ancestor::sect3
+                                       |ancestor::sect4
+                                       |ancestor::sect5
+                                       |ancestor::refsection
+                                       |ancestor::refsect1
+                                       |ancestor::refsect2
+                                       |ancestor::refsect3
+                                       |ancestor::chapter
+                                       |ancestor::appendix
+                                       |ancestor::preface
+                                       |ancestor::partintro
+                                       |ancestor::dedication
+                                       |ancestor::colophon
+                                       |ancestor::bibliography
+                                       |ancestor::index
+                                       |ancestor::glossary
+                                       |ancestor::glossentry
+                                       |ancestor::listitem
+                                       |ancestor::varlistentry)[last()]"/>
+
+  <xsl:apply-templates select="$context" mode="xref-to"/>
+<!--
+  <xsl:apply-templates select="." mode="object.xref.markup">
+    <xsl:with-param name="purpose" select="'xref'"/>
+    <xsl:with-param name="xrefstyle" select="$xrefstyle"/>
+    <xsl:with-param name="referrer" select="$referrer"/>
+  </xsl:apply-templates>
+-->
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/db2latex-xsl/xsl/xsldoc.ent b/docs-xml/xslt/db2latex-xsl/xsl/xsldoc.ent
new file mode 100644
index 00000000000..7bc763aaa5c
--- /dev/null
+++ b/docs-xml/xslt/db2latex-xsl/xsl/xsldoc.ent
@@ -0,0 +1,55 @@
+<!ENTITY DocBook "<productname condition='noindex'>DocBook</productname>">
+<!ENTITY docbook "<productname condition='noindex'>DocBook</productname>">
+<!ENTITY DB2LaTeX "<productname condition='noindex'>DB2<?latex \?>LaTeX</productname>">
+<!ENTITY db2latex "<productname condition='noindex'>DB2<?latex \?>LaTeX</productname>">
+<!ENTITY LaTeX "<productname condition='noindex'><?latex \?>LaTeX</productname>">
+<!ENTITY latex "<productname condition='noindex'><?latex \?>LaTeX</productname>">
+<!ENTITY BibTeX "<productname><?latex \?>BibTeX</productname>">
+<!ENTITY bibtex "<productname><?latex \?>BibTeX</productname>">
+
+<!ENTITY ramon "<author><firstname>Ramon</firstname><surname>Casellas</surname></author>">
+<!ENTITY james "<author><firstname>James</firstname><surname>Devenish</surname></author>">
+
+<!ENTITY mapping "<xref linkend='latex.mapping'/>">
+<!ENTITY preamble "<xref linkend='preamble'/>">
+<!ENTITY no_var "<para>There are no configuration variables for this template.</para>">
+<!ENTITY essential_preamble "<para>This template requires &LaTeX; commands that are part of the <quote>essential preamble</quote>.</para>">
+<!ENTITY rev_2003_05 "<date>May-January 2004</date><revremark>Major review of documentation.</revremark>">
+<!ENTITY roleattr "<sgmltag class='attribute'>role</sgmltag>">
+
+<!ENTITY test_article "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_article' xml='article.xml' xsl='article.xsl'/></member>">
+<!ENTITY test_adm "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_adm' xml='test.xml'/></member>">
+<!ENTITY test_biblio "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_biblio' xml='test.xml'/></member>">
+<!ENTITY test_bind "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_bind' xml='Bv9ARM-book.xml'/></member>">
+<!ENTITY test_blocks "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_blocks' xml='test.xml'/></member>">
+<!ENTITY test_book "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_book' xml='test.xml'/></member>">
+<!ENTITY test_chemistry "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_chemistry' xml='test.xml'/></member>">
+<!ENTITY test_cited "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_cited' xml='test.xml'/></member>">
+<!ENTITY test_ddh "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_ddh' xml='article.xml'/></member>">
+<!ENTITY test_defguide "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_defguide' xml='defguide.xml'/></member>">
+<!ENTITY test_draft "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_draft' xml='test.xml'/></member>">
+<!ENTITY test_draft1 "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_draft' xml='test.xml' xsl='test.xsl'/></member>">
+<!ENTITY test_draft2 "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_draft' xml='test.xml' xsl='hyperref.xsl'/></member>">
+<!ENTITY test_draft3 "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_draft' xml='test.xml' xsl='varioref1.xsl'/></member>">
+<!ENTITY test_draft4 "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_draft' xml='test.xml' xsl='varioref2.xsl'/></member>">
+<!ENTITY test_ecos "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_ecos' xml='user-guide.xml'/></member>">
+<!ENTITY test_entities "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_entities' xml='test.xml'/></member>">
+<!ENTITY test_gloss "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_gloss' xml='test.xml'/></member>">
+<!ENTITY test_ieeebiblio "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_ieeebiblio' xml='test.xml'/></member>">
+<!ENTITY test_index "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_index' xml='test.xml'/></member>">
+<!ENTITY test_index_draft "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_index' xml='test.xml' xsl='draft.xsl'/></member>">
+<!ENTITY test_links "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_links' xml='test.xml'/></member>">
+<!ENTITY test_lot "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_lot' xml='test1.xml'/></member>">
+<!ENTITY test_lot1 "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_lot' xml='test1.xml'/></member>">
+<!ENTITY test_lot2 "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_lot' xml='test2.xml'/></member>">
+<!ENTITY test_lot3 "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_lot' xml='test3.xml'/></member>">
+<!ENTITY test_lists "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_lists' xml='test.xml'/></member>">
+<!ENTITY test_mapping "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_mapping' xml='test.xml'/></member>">
+<!ENTITY test_minimal "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_minimal' xml='minimal.xml'/></member>">
+<!ENTITY test_pinkjuice "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_pinkjuice' xml='vimxml.xml'/></member>">
+<!ENTITY test_program "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_program' xml='test.xml'/></member>">
+<!ENTITY test_procedure "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_procedure' xml='test.xml'/></member>">
+<!ENTITY test_subfig "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_subfig' xml='test.xml'/></member>">
+<!ENTITY test_tables "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_tables' xml='test.xml'/></member>">
+<!ENTITY test_theorem "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_theorem' xml='test.xml'/></member>">
+<!ENTITY test_varioref "<member><sample xmlns='http://nwalsh.com/xsl/documentation/1.0' directory='test_varioref' xml='test.xml'/></member>">
diff --git a/docs-xml/xslt/docbook2pearson.xsl b/docs-xml/xslt/docbook2pearson.xsl
new file mode 100644
index 00000000000..ebe2a955a27
--- /dev/null
+++ b/docs-xml/xslt/docbook2pearson.xsl
@@ -0,0 +1,1042 @@
+<?xml version='1.0'?>
+<!-- 
+	Convert DocBook to XML validating against the Pearson DTD
+
+	(C) Jochen Hein
+	(C) Jelmer Vernooij <jelmer@samba.org>			2004
+-->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc"
+	version="1.1">
+
+	<!-- TODO <entry></entry> -> <entry><p/></entry> -->
+
+	<xsl:output method="xml"
+		encoding="UTF-8"
+		doctype-public="-//Pearson//DTD Books//DE"
+		doctype-system="http://www.pearson.de/pearson.dtd"
+		indent="yes"
+		omit-xml-declaration="no"
+		standalone="no"/>
+
+	<!-- Warn about DocBook elements that are not converted -->
+	<xsl:template match="*">
+		<xsl:message>
+			<xsl:text>No template matches </xsl:text>
+			<xsl:value-of select="name(.)"/>
+			<xsl:text>.</xsl:text>
+		</xsl:message>
+	</xsl:template>
+
+	<!--  
+	====================================================================  
+	-->
+	<!-- Establish strip/preserve whitespace rules -->
+
+	<xsl:preserve-space elements="*"/>
+
+	<xsl:strip-space elements="
+		abstract affiliation anchor answer appendix area areaset areaspec
+		artheader article audiodata audioobject author authorblurb authorgroup
+		beginpage bibliodiv biblioentry bibliography biblioset blockquote book
+		bookbiblio bookinfo callout calloutlist caption caution
+		city pubdate publisher publishername"/>
+
+	<xsl:template name="transform.id.attribute">
+		<xsl:if test="@id != ''">
+			<xsl:attribute name="id">
+				<xsl:value-of select="@id"/>
+			</xsl:attribute>
+		</xsl:if>
+	</xsl:template>
+
+	<xsl:template match="/" mode="default">
+		<xsl:processing-instruction  
+			name="xml-stylesheet">href="pearson.css"  
+			type="text/css"</xsl:processing-instruction>
+		<xsl:text>
+		</xsl:text>
+		<xsl:comment>
+			<xsl:text>Transformed with pearson.xsl by Jochen Hein</xsl:text>
+		</xsl:comment>
+		<xsl:text>
+		</xsl:text>
+		<!-- Releaseinfo einbauen? -->
+		<xsl:comment>
+			<xsl:apply-templates select=".//releaseinfo" mode="comment"/>
+		</xsl:comment>
+		<xsl:text>
+		</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="book">
+		<book>
+			<xsl:apply-templates/>
+		</book>
+	</xsl:template>
+
+	<xsl:template match="bookinfo">
+		<bookinfo>
+			<xsl:apply-templates/>
+		</bookinfo>
+	</xsl:template>
+
+	<xsl:template match="author">
+		<author>
+			<xsl:apply-templates/>
+		</author>
+	</xsl:template>
+
+	<xsl:template match="editor">
+		<editor>
+			<xsl:apply-templates/>
+		</editor>
+	</xsl:template>
+
+	<xsl:template match="chapter">
+		<chapter>
+			<xsl:call-template name="transform.id.attribute"/>
+			<xsl:apply-templates/>
+		</chapter>
+	</xsl:template>
+
+	<xsl:template match="chapter/title/command">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="index">
+       <xsl:comment> XXX insert index here </xsl:comment>
+   </xsl:template>
+
+   <xsl:template match="preface">
+	   <preface>
+		   <xsl:call-template name="transform.id.attribute"/>
+		   <xsl:apply-templates/>
+	   </preface>
+   </xsl:template>
+
+   <xsl:template match="section|sect1|sect2|sect3|sect4">
+	   <sect>
+		   <xsl:call-template name="transform.id.attribute"/>
+		   <xsl:apply-templates/>
+	   </sect>
+   </xsl:template>
+
+   <xsl:template match="partintro">
+	   <xsl:copy>
+		   <xsl:apply-templates select="@*|node()"/>
+	   </xsl:copy>
+   </xsl:template>
+
+   <xsl:template match="part">
+	   <appendix>
+		   <xsl:apply-templates/>
+	   </appendix>
+   </xsl:template>
+
+   <xsl:template match="appendix[1]">
+	   <appendix>
+		   <chapter>
+			   <xsl:call-template name="transform.id.attribute"/>
+			   <xsl:apply-templates/>
+		   </chapter>
+		   <xsl:for-each select="following-sibling::appendix">
+			   <chapter>
+				   <xsl:call-template name="transform.id.attribute"/>
+				   <xsl:apply-templates/>
+			   </chapter>
+		   </xsl:for-each>
+	   </appendix>
+   </xsl:template>
+
+   <xsl:template match="appendix[position() != 1]">
+   </xsl:template>
+
+   <xsl:template match="title">
+	   <title><xsl:apply-templates/></title>
+   </xsl:template>
+
+	<xsl:param name="notpchilds" select="'variablelist itemizedlist orderedlist'"/>
+
+	<xsl:template match="para"> 
+		<!-- loop thru all elements: -->
+		<xsl:for-each select="*|text()">
+			<xsl:choose>
+				<xsl:when test="string-length(name(.)) > 0 and contains($notpchilds,name(.))">
+					<xsl:message><xsl:text>Removing from p:</xsl:text><xsl:value-of select="name(.)"/></xsl:message>
+					<xsl:apply-templates select="."/>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:call-template name="hstartpara"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:for-each>
+	</xsl:template>
+
+	<!-- Do open paragraph when previous sibling was not a valid p child -->
+	<xsl:template name="hstartpara">
+		<xsl:if test="not(preceding-sibling::*[1]) or (contains($notpchilds,name(preceding-sibling::*[1])) and not(string-length(name(.)) > 0))">
+			<p>
+				<xsl:apply-templates select="."/>
+				<xsl:for-each select="following-sibling::*[not(contains($notpchilds,name(.)) and string-length(name(.)) > 0)]">
+					<xsl:apply-templates select="."/>
+				</xsl:for-each>
+			</p>
+		</xsl:if>
+	</xsl:template>
+
+	<xsl:template name="hsubpara">
+		<xsl:param name="data"/>
+		<xsl:apply-templates select="$data"/>
+		<xsl:if test="$data[following-sibling::*[1]]">
+			<xsl:param name="next" select="$data[following-sibling::*[1]]"/>
+			<xsl:message><xsl:value-of select="name(.)"/></xsl:message>
+			<xsl:if test="$next and (not(contains($notpchilds,name($next))) or $next[text()])">
+				<xsl:message><xsl:text>Followed by : </xsl:text><xsl:value-of select="name($next)"/></xsl:message>
+				<xsl:call-template name="hsubpara">
+					<xsl:with-param name="data" select="$next"/>
+				</xsl:call-template>
+				<xsl:message><xsl:text>Done Followed by : </xsl:text><xsl:value-of select="name($next)"/></xsl:message>
+			</xsl:if>
+		</xsl:if>
+	</xsl:template>
+
+	<xsl:template match="tip">
+		<tip><xsl:apply-templates/></tip>
+	</xsl:template>
+
+   <xsl:template match="warning|important|caution">
+	   <stop><xsl:apply-templates/></stop>
+   </xsl:template>
+
+   <xsl:template match="note">
+	   <info><xsl:apply-templates/></info>
+   </xsl:template>
+
+   <xsl:template match="emphasis">
+	   <xsl:variable name="role" select="@role"/>
+
+	   <xsl:choose>
+		   <xsl:when test="$role='italic'">
+			   <i><xsl:apply-templates/></i>
+		   </xsl:when>
+		   <xsl:otherwise>
+			   <em><xsl:apply-templates/></em>
+		   </xsl:otherwise>
+	   </xsl:choose>
+   </xsl:template>
+
+   <xsl:template match="ulink">
+	   <xsl:apply-templates/>
+	   <footnote><p><url><xsl:value-of select="@ulink"/></url></p></footnote>
+	</xsl:template>
+
+   <xsl:template match="email">
+	   <url>mailto:<xsl:apply-templates/></url>
+   </xsl:template>
+
+   <xsl:template match="indexterm">
+	   <ie><xsl:apply-templates/></ie>
+   </xsl:template>
+
+   <xsl:template match="primary">
+	   <t><xsl:apply-templates/></t>
+   </xsl:template>
+
+   <xsl:template match="secondary">
+	   <t><xsl:apply-templates/></t>
+   </xsl:template>
+
+   <xsl:template match="citerefentry">
+	   <xsl:value-of select="refentrytitle"/><xsl:text>(</xsl:text><xsl:value-of select="manvolnum"/><xsl:text>)</xsl:text>
+   </xsl:template>
+
+   <xsl:template match="formalpara">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="substeps">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="see|seealso">
+	   <synonym><xsl:apply-templates/></synonym>
+   </xsl:template>
+
+   <xsl:template  
+	   match="footnote"><footnote><xsl:apply-templates/></footnote></xsl:template>
+
+   <xsl:template match="command">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="function">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="systemitem">
+
+	   <!-- xsl:if test="@role != '' and @role != 'signal'">
+	   <xsl:message>
+		   Warning: role attribute is <xsl:value-of select="@role"/>
+	   </xsl:message>
+   </xsl:if -->
+   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="sgmltag">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="filename">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="errorcode">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="errortype">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="returnvalue">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="glosslist|glossary">
+	   <dl><xsl:apply-templates/></dl>
+   </xsl:template>
+
+   <xsl:template match="glossentry">
+	   <dlitem><xsl:apply-templates/></dlitem>
+   </xsl:template>
+
+   <xsl:template match="glossentry/acronym">
+	   <dt><xsl:apply-templates/></dt>
+   </xsl:template>
+
+   <xsl:template match="acronym">
+	   <b><xsl:apply-templates/></b>
+   </xsl:template>
+
+   <xsl:template match="glossterm">
+	   <dt><xsl:apply-templates/></dt>
+   </xsl:template>
+
+   <xsl:template match="glossdef">
+	   <dd><xsl:apply-templates/></dd>
+   </xsl:template>
+
+   <xsl:template match="itemizedlist">
+	   <ul><xsl:apply-templates/></ul>
+   </xsl:template>
+
+   <xsl:template match="varlistentry/term">
+	   <dt><xsl:apply-templates/></dt>
+   </xsl:template>
+
+   <xsl:template match="varlistentry/listitem">
+	   <dd><xsl:apply-templates/></dd>
+   </xsl:template>
+
+   <xsl:template match="varlistentry">
+	   <dlitem>
+		   	<xsl:apply-templates/>
+	   </dlitem>
+   </xsl:template>
+
+   <xsl:template match="variablelist">
+	   <dl><xsl:apply-templates/></dl>
+   </xsl:template>
+
+   <xsl:template match="simplelist">
+	   <ul>
+		   <xsl:for-each select="member">
+			   <li><p><xsl:apply-templates/></p></li>
+		   </xsl:for-each>
+	   </ul>
+   </xsl:template>
+
+   <xsl:template match="orderedlist">
+	   <xsl:variable name="numeration" select="@numeration"/>
+	   <ol>
+		   <xsl:if test="$numeration != ''">
+			   <xsl:attribute name="type">
+				   <xsl:value-of select="$numeration"/>
+			   </xsl:attribute>
+		   </xsl:if>
+		   <xsl:apply-templates/>
+	   </ol>
+   </xsl:template>
+
+   <xsl:template match="listitem">
+	   <li><xsl:apply-templates/></li>
+   </xsl:template>
+
+   <xsl:template match="firstterm">
+	   <em><xsl:apply-templates/></em>
+   </xsl:template>
+
+   <xsl:template match="literal/systemitem">
+	   <em><xsl:apply-templates/></em>
+   </xsl:template>
+
+   <xsl:template match="superscript">
+	   <sup><xsl:apply-templates/></sup>
+   </xsl:template>
+
+   <xsl:template match="productname">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="keycombo">
+
+	   <xsl:variable name="action" select="@action"/>
+	   <xsl:variable name="joinchar">
+
+		   <xsl:choose>
+
+			   <xsl:when test="$action='seq'">
+				   <xsl:text> </xsl:text></xsl:when>
+			   <xsl:when test="$action='simul'">+</xsl:when>
+			   <xsl:when test="$action='press'">-</xsl:when>
+			   <xsl:when test="$action='click'">-</xsl:when>
+			   <xsl:when test="$action='double-click'">-</xsl:when>
+			   <xsl:when test="$action='other'"></xsl:when>
+			   <xsl:otherwise>-</xsl:otherwise>
+		   </xsl:choose>
+	   </xsl:variable>
+
+	   <xsl:for-each select="*">
+		   <xsl:if test="position()>1"><xsl:value-of  
+				   select="$joinchar"/></xsl:if>
+		   <xsl:apply-templates select="."/>
+	   </xsl:for-each>
+
+   </xsl:template>
+
+
+   <xsl:template match="keycap">
+	   <key><xsl:apply-templates/></key>
+   </xsl:template>
+
+   <xsl:template match="keycap/replaceable">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+
+
+   <xsl:template match="menuchoice">
+	   <xsl:variable name="shortcut" select="./shortcut"/>
+	   <xsl:call-template name="process.menuchoice"/>
+	   <xsl:if test="$shortcut">
+		   <xsl:text> (</xsl:text>
+		   <xsl:apply-templates select="$shortcut"/>
+		   <xsl:text>)</xsl:text>
+	   </xsl:if>
+   </xsl:template>
+
+   <xsl:template name="process.menuchoice">
+	   <xsl:param name="nodelist"  
+		   select="guibutton|guiicon|guilabel|guimenu|guimenuitem|guisubmenu|interface"/><!-- not(shortcut) -->
+	   <xsl:param name="count" select="1"/>
+
+	   <xsl:choose>
+		   <xsl:when test="$count>count($nodelist)"></xsl:when>
+		   <xsl:when test="$count=1">
+			   <xsl:apply-templates select="$nodelist[$count=position()]"/>
+			   <xsl:call-template name="process.menuchoice">
+				   <xsl:with-param name="nodelist" select="$nodelist"/>
+				   <xsl:with-param name="count" select="$count+1"/>
+			   </xsl:call-template>
+		   </xsl:when>
+		   <xsl:otherwise>
+			   <xsl:variable name="node" select="$nodelist[$count=position()]"/>
+			   <xsl:choose>
+				   <xsl:when test="name($node)='guimenuitem'
+					   or name($node)='guisubmenu'">
+					   <xsl:text>-&gt;</xsl:text>
+				   </xsl:when>
+				   <xsl:otherwise>+</xsl:otherwise>
+			   </xsl:choose>
+			   <xsl:apply-templates select="$node"/>
+			   <xsl:call-template name="process.menuchoice">
+				   <xsl:with-param name="nodelist" select="$nodelist"/>
+				   <xsl:with-param name="count" select="$count+1"/>
+			   </xsl:call-template>
+		   </xsl:otherwise>
+	   </xsl:choose>
+   </xsl:template>
+
+
+   <xsl:template match="guimenu">
+	   <guiitem><xsl:apply-templates/></guiitem>
+   </xsl:template>
+
+   <xsl:template match="guimenuitem">
+	   <guiitem><xsl:apply-templates/></guiitem>
+   </xsl:template>
+
+	<xsl:template match="guiicon">
+	   <guiitem><xsl:apply-templates/></guiitem>
+   </xsl:template>
+
+   <xsl:template match="guilabel">
+	   <guiitem><xsl:apply-templates/></guiitem>
+   </xsl:template>
+
+   <xsl:template match="guibutton">
+	   <guiitem><xsl:apply-templates/></guiitem>
+   </xsl:template>
+
+   <xsl:template name="transform.epigraph">
+	   <xsl:apply-templates select="para"/>
+	   <xsl:apply-templates select="attribution"/>
+   </xsl:template>
+
+   <xsl:template match="epigraph">
+	   <chapterintro><motto><xsl:call-template  
+				   name="transform.epigraph"/></motto></chapterintro>
+   </xsl:template>
+
+   <xsl:template match="section/epigraph">
+	   <motto><xsl:call-template name="transform.epigraph"/></motto>
+   </xsl:template>
+
+   <xsl:template match="epigraph/para">
+	   <p><em><xsl:apply-templates/></em></p>
+   </xsl:template>
+   <xsl:template match="attribution">
+	   <p><i><xsl:apply-templates/></i></p>
+   </xsl:template>
+
+   <xsl:template match="errorname">
+	   <i><xsl:apply-templates/></i>
+   </xsl:template>
+
+   <xsl:template match="constant">
+	   <b><xsl:apply-templates/></b>
+   </xsl:template>
+
+   <xsl:template match="envar">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="literal">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="option">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="parameter">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="application">
+	   <b><xsl:apply-templates/></b>
+   </xsl:template>
+
+   <xsl:template match="screen/userinput">
+	   <b><xsl:apply-templates/></b>
+   </xsl:template>
+
+   <xsl:template match="screen/prompt">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="prompt">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="userinput">
+	   <code><b><xsl:apply-templates/></b></code>
+   </xsl:template>
+
+   <xsl:template match="computeroutput">
+	   <code><xsl:apply-templates/></code>
+   </xsl:template>
+
+   <xsl:template match="screen/computeroutput">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="replaceable">
+	   <i><xsl:apply-templates/></i>
+   </xsl:template>
+
+   <xsl:template match="userinput/replaceable">
+	   <i><xsl:apply-templates/></i>
+   </xsl:template>
+
+   <xsl:template match="citation"
+	   xmlns:xlink="http://www.w3.org/1999/xlink">
+
+	   <xsl:variable name="target" select="."/>
+	   <xsl:variable name="targets" select="id($target)"/>
+
+	   <!-- xsl:call-template name="check.id.unique">
+	   <xsl:with-param name="linkend" select="$target"/>
+   </xsl:call-template -->
+
+   <xsl:choose>
+	   <xsl:when test="count($targets) = 0">
+		   <xsl:message>
+			   <xsl:text>Citation of nonexistent id: </xsl:text>
+			   <xsl:value-of select="."/>
+		   </xsl:message>
+		   <xsl:text>[??? </xsl:text>
+		   <xsl:value-of select="."/>
+		   <xsl:text>]</xsl:text>
+	   </xsl:when>
+	   <xsl:otherwise>
+		   <xsl:text>[</xsl:text><xsl:value-of  
+			   select="."/><xsl:text>]</xsl:text>
+	   </xsl:otherwise>
+   </xsl:choose>
+
+   </xsl:template>
+
+   <xsl:template match="figure">
+	   <figure>
+		   <xsl:call-template name="transform.id.attribute"/>
+		   <xsl:apply-templates/>
+	   </figure>
+   </xsl:template>
+
+   <xsl:template match="graphic">
+	   <xsl:message>
+		   <xsl:text>Obsolete tag "graphic" found.</xsl:text>
+	   </xsl:message>
+
+	   <figureref>
+		   <xsl:attribute name="fileref">
+			   <xsl:value-of select="@fileref"/>
+		   </xsl:attribute>
+	   </figureref>
+   </xsl:template>
+
+   <xsl:template match="mediaobject">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="imageobject">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="imagedata">
+	   <xsl:variable name="scale" select="@scale"/>
+	   <figureref>
+		   <xsl:attribute name="fileref">
+			   <xsl:value-of select="@fileref"/>
+		   </xsl:attribute>
+		   <xsl:if test="$scale != ''">
+			   <xsl:attribute name="scale"><xsl:value-of  
+					   select="$scale"/>%</xsl:attribute>
+		   </xsl:if>
+	   </figureref>
+   </xsl:template>
+
+   <xsl:template match="example">
+	   <screen>
+		   <xsl:call-template name="transform.id.attribute"/>
+		   <xsl:apply-templates/>
+	   </screen>
+   </xsl:template>
+
+   <xsl:template match="listing">
+	   <screen>
+		   <xsl:call-template name="transform.id.attribute"/>
+		   <xsl:apply-templates/>    </screen>
+   </xsl:template>
+
+   <xsl:template name="check.title.not.empty">
+	   <xsl:variable name="title" select="."/>
+	   <xsl:if test="$title=''">
+		   <xsl:message>title tag is empty!</xsl:message>
+	   </xsl:if>
+   </xsl:template>
+
+   <xsl:template match="figure/title">
+	   <xsl:call-template name="check.title.not.empty"/>
+	   <description><xsl:apply-templates/></description>
+   </xsl:template>
+   <xsl:template match="listing/title">
+	   <xsl:call-template name="check.title.not.empty"/>
+	   <description><xsl:apply-templates/></description>
+   </xsl:template>
+   <xsl:template match="example/title">
+	   <xsl:call-template name="check.title.not.empty"/>
+	   <description><xsl:apply-templates/></description>
+   </xsl:template>
+
+   <xsl:template match="literallayout">
+	   <screentext><xsl:apply-templates/></screentext>
+   </xsl:template>
+   <xsl:template match="screen">
+	   <screentext><xsl:apply-templates/></screentext>
+   </xsl:template>
+
+   <xsl:template match="programlisting">
+	   <listing>
+		   <xsl:if test="title != ''">
+			   <description><xsl:value-of select="title"/></description>
+		   </xsl:if>
+		   <listingcode>
+			   <xsl:apply-templates/>
+		   </listingcode>
+		</listing>
+   </xsl:template>
+
+   <!-- Tabellen -->
+   <xsl:template match="table">
+	   <table>
+		   <xsl:call-template name="transform.id.attribute"/>
+		   <xsl:apply-templates/>
+	   </table>
+   </xsl:template>
+   <xsl:template match="table/title">
+	   <description><xsl:apply-templates/></description>
+   </xsl:template>
+
+   <xsl:template match="tgroup">
+	   <tgroup>
+		   <xsl:attribute name="cols">
+			   <xsl:value-of select="@cols"/></xsl:attribute>
+		   <xsl:apply-templates/>
+	   </tgroup>
+   </xsl:template>
+   <xsl:template match="thead">
+	   <thead><xsl:apply-templates/></thead>
+   </xsl:template>
+   <xsl:template match="tbody">
+	   <tbody><xsl:apply-templates/></tbody>
+   </xsl:template>
+   <xsl:template match="row">
+	   <row><xsl:apply-templates/></row>
+   </xsl:template>
+   <xsl:template match="entry">
+	   <entry><p><xsl:apply-templates/></p></entry>
+   </xsl:template>
+   <xsl:template match="colspec">
+	   <colspec><xsl:copy-of select="@*"/><xsl:apply-templates/></colspec>
+   </xsl:template>
+
+   <!-- xref nach pearson-equivalent - Einige Ideen stammen von Norm -->
+
+   <xsl:template name="object.id">
+	   <xsl:param name="object" select="."/>
+	   <xsl:choose>
+		   <xsl:when test="$object/@id">
+			   <xsl:value-of select="$object/@id"/>
+		   </xsl:when>
+		   <xsl:otherwise>
+			   <xsl:value-of select="generate-id($object)"/>
+		   </xsl:otherwise>
+	   </xsl:choose>
+   </xsl:template>
+
+   <xsl:template name="anchor">
+	   <xsl:param name="node" select="."/>
+	   <xsl:param name="conditional" select="1"/>
+	   <xsl:variable name="id">
+		   <xsl:call-template name="object.id">
+			   <xsl:with-param name="object" select="$node"/>
+		   </xsl:call-template>
+	   </xsl:variable>
+	   <xsl:if test="$conditional = 0 or $node/@id">
+		   <a name="{$id}"/>
+	   </xsl:if>
+   </xsl:template>
+
+   <xsl:template name="check.id.unique">
+	   <xsl:param name="linkend"></xsl:param>
+	   <xsl:if test="$linkend != ''">
+		   <xsl:variable name="targets" select="id($linkend)"/>
+		   <xsl:variable name="target" select="$targets[1]"/>
+
+		   <xsl:if test="count($targets)=0">
+			   <xsl:message>
+				   <xsl:text>Error: no ID for constraint linkend: </xsl:text>
+				   <xsl:value-of select="$linkend"/>
+				   <xsl:text>.</xsl:text>
+			   </xsl:message>
+		   </xsl:if>
+
+		   <xsl:if test="count($targets)>1">
+			   <xsl:message>
+				   <xsl:text>Warning: multiple "IDs" for constraint linkend:  
+				   </xsl:text>
+				   <xsl:value-of select="$linkend"/>
+				   <xsl:text>.</xsl:text>
+			   </xsl:message>
+		   </xsl:if>
+	   </xsl:if>
+   </xsl:template>
+
+   <xsl:template match="xref|link"
+	   xmlns:xlink="http://www.w3.org/1999/xlink">
+	   <xsl:variable name="linkend" select="@linkend"/>
+	   <xsl:variable name="targets" select="id(@linkend)"/>
+	   <xsl:variable name="target" select="$targets[1]"/>
+	   <xsl:variable name="refelem" select="local-name($target)"/>
+
+	   <xsl:call-template name="check.id.unique">
+		   <xsl:with-param name="linkend" select="$linkend"/>
+	   </xsl:call-template>
+
+	   <xsl:call-template name="anchor"/>
+
+	   <xsl:choose>
+		   <xsl:when test="count($targets) = 0">
+			   <xsl:message>
+				   <xsl:text>XRef to nonexistent id: </xsl:text>
+				   <xsl:value-of select="@linkend"/>
+			   </xsl:message>
+			   <xsl:text>[??? </xsl:text>
+			   <xsl:value-of select="@linkend"/>
+			   <xsl:text>]</xsl:text>
+		   </xsl:when>
+		   <xsl:when test="count($targets) > 1">
+			   <xsl:message>Uh, multiple linkends
+				   <xsl:value-of select="@linkend"/>
+			   </xsl:message>
+		   </xsl:when>
+	   </xsl:choose>
+
+	   <xsl:choose>
+		   <xsl:when test='$refelem = "chapter" or $refelem = "preface"'>
+			   <xsl:text>Kapitel </xsl:text>
+		   </xsl:when>
+		   <xsl:when test='$refelem = "section" or $refelem = "sect1" or $refelem = "sect2" or $refelem = "sect3" or $refelem = "sect4"'>
+			   <xsl:text>Abschnitt </xsl:text>
+		   </xsl:when>
+		   <xsl:when test='$refelem = "figure"'>
+			   <xsl:text>Abbildung </xsl:text>
+		   </xsl:when>
+		   <xsl:when test='$refelem = "example"'>
+			   <!-- xsl:choose>
+			   <xsl:when test="$target/@role='listing'">
+				   <xsl:text>Listing </xsl:text>
+			   </xsl:when>
+			   <xsl:otherwise -->
+				   <xsl:text>Listing </xsl:text>
+				   <!-- /xsl:otherwise>
+			   </xsl:choose -->
+		   </xsl:when>
+		   <xsl:when test='$refelem = "table"'>
+			   <xsl:text>Tabelle </xsl:text>
+		   </xsl:when>
+		   <xsl:when test='$refelem = "appendix"'>
+			   <xsl:text>Anhang </xsl:text>
+		   </xsl:when>
+		   <xsl:otherwise>
+			   <xsl:if test="$refelem != ''">
+				   <xsl:message>
+					   <xsl:text>Cant't handle xref to </xsl:text>
+					   <xsl:value-of select="$refelem"/>
+					   <xsl:text>:</xsl:text>
+					   <xsl:value-of select="@linkend"/>
+				   </xsl:message>
+				   <xsl:text>(??? $refelem)</xsl:text>
+			   </xsl:if>
+		   </xsl:otherwise>
+	   </xsl:choose>
+
+	   <xref>
+		   <xsl:attribute name="xlink:href"
+			   xmlns:xlink="http://www.w3.org/1999/xlink">
+			   <!-- xsl:attribute name="id" -->
+			   <xsl:value-of select="@linkend"/>
+		   </xsl:attribute>
+	   </xref>
+   </xsl:template>
+
+   <xsl:template match="quote">"<xsl:apply-templates/>"</xsl:template>
+   <!-- xsl:template  
+   match="quote"><quote><xsl:apply-templates/></quote></xsl:template -->
+
+
+   <xsl:template match="othername">
+	   <xsl:text>(</xsl:text><xsl:apply-templates/><xsl:text>)</xsl:text>0
+   </xsl:template>
+   <xsl:template match="firstname">
+	   <xsl:apply-templates/><xsl:text> </xsl:text>
+   </xsl:template>
+   <xsl:template match="surname">
+	   <xsl:apply-templates/>
+   </xsl:template>
+   <xsl:template match="copyright">
+	   <!-- empty -->
+   </xsl:template>
+   <xsl:template match="edition">
+	   <!-- empty -->
+   </xsl:template>
+   <xsl:template match="publisher">
+	   <!-- empty -->
+   </xsl:template>
+   <xsl:template match="pubdate">
+	   <xsl:apply-templates/>
+   </xsl:template>
+   <xsl:template match="isbn">
+	   ISBN <xsl:apply-templates/>
+   </xsl:template>
+
+   <!-- Literaturverzeichnis -->
+   <xsl:template match="bibliography">
+	   <sect>
+		   <xsl:apply-templates/>
+	   </sect>
+   </xsl:template>
+
+   <xsl:template name="process.bibliomixed">
+
+	   <xsl:variable name="bibid" select="id(@id)"/>
+	   <dlitem><dt>[<xsl:value-of select="@id"/>]</dt>
+		   <dd><p><xsl:apply-templates select=".//title"/>,
+				   <xsl:if test="count(.//subtitle)>0">
+					   <xsl:apply-templates select=".//subtitle"/>,
+				   </xsl:if>
+				   <xsl:apply-templates select=".//author"/>
+				   <xsl:apply-templates select=".//publisher"/>
+				   <xsl:apply-templates select=".//pubdate"/>
+				   <xsl:if test="count(.//isbn)>0">
+					   <xsl:text>, </xsl:text>
+					   <xsl:apply-templates select=".//isbn"/>
+				   </xsl:if>
+				   <xsl:text>.</xsl:text></p>
+			   <xsl:call-template name="process.abstract" select=".//abstract"/>
+		   </dd>
+	   </dlitem>
+   </xsl:template>
+
+   <xsl:template match="bibliomixed[1]">
+	   <dl><xsl:call-template name="process.bibliomixed"/>
+		   <xsl:for-each select="following-sibling::bibliomixed">
+			   <xsl:call-template name="process.bibliomixed"/>
+		   </xsl:for-each>
+	   </dl>
+   </xsl:template>
+
+
+   <xsl:template match="bibliomixed/title">
+	   <i><xsl:apply-templates/></i>
+   </xsl:template>
+
+   <xsl:template match="biblioentry/title">
+	   <i><xsl:apply-templates/></i>
+   </xsl:template>
+
+   <xsl:template match="bibliomixed/subtitle">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="bibliomixed/publisher">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="publishername">
+	   <xsl:apply-templates/>,
+   </xsl:template>
+   <xsl:template match="publisher/address">
+	   <xsl:apply-templates/>
+   </xsl:template>
+   <xsl:template match="city">
+	   <xsl:apply-templates/>,
+   </xsl:template>
+
+   <xsl:template name="process.abstract">
+	   <xsl:apply-templates select="abstract//para"/>
+   </xsl:template>
+   <xsl:template match="bibliomixed">
+	   <!-- empty -->
+   </xsl:template>
+
+   <xsl:template match="chapterinfo">
+	   <!-- empty -->
+   </xsl:template>
+
+   <xsl:template match="sectioninfo">
+	   <!-- empty -->
+   </xsl:template>
+
+   <xsl:template match="prefaceinfo">
+	   <!-- empty -->
+   </xsl:template>
+
+   <xsl:template match="appendixinfo">
+	   <!-- empty -->
+   </xsl:template>
+
+   <xsl:template match="releaseinfo">
+	   <xsl:comment><xsl:apply-templates/></xsl:comment>
+   </xsl:template>
+
+   <xsl:template match="releaseinfo" mode="comment">
+	   <xsl:text>
+	   </xsl:text>
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="trademark">
+	   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="processing-instruction('linebreak')">
+	   <br/>
+   </xsl:template>
+
+   <xsl:template match="processing-instruction('pearson')">
+	   <xsl:copy/>
+   </xsl:template>
+
+   <xsl:template match="procedure">
+		   <xsl:apply-templates/>
+   </xsl:template>
+
+   <xsl:template match="step">
+	   <step><xsl:apply-templates/></step>
+   </xsl:template>
+
+   <xsl:template match="toc">
+	   <xsl:element name="toc">
+		   <xsl:attribute name="role">
+			   <xsl:text>sect</xsl:text>
+		   </xsl:attribute>
+	   </xsl:element>
+   </xsl:template>
+
+   <xsl:template match="lot">
+	   <xsl:element name="toc">
+		   <xsl:attribute name="role">
+			   <xsl:text>table</xsl:text>
+		   </xsl:attribute>
+	   </xsl:element>
+   </xsl:template>
+
+   <xsl:template match="lof">
+	   <xsl:element name="toc">
+		   <xsl:attribute name="role">
+			   <xsl:text>figure</xsl:text>
+		   </xsl:attribute>
+	   </xsl:element>
+   </xsl:template>
+
+   <xsl:template match="blockquote">
+	   <motto><xsl:apply-templates/></motto>
+   </xsl:template>
+
+	<xsl:template match="authorgroup">
+		<xsl:apply-templates/>
+	</xsl:template>
+
+
+	<xsl:template match="affiliation">
+		<!-- Ignoring affiliations for now -->
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/expand-sambadoc.xsl b/docs-xml/xslt/expand-sambadoc.xsl
new file mode 100644
index 00000000000..5b539df54a5
--- /dev/null
+++ b/docs-xml/xslt/expand-sambadoc.xsl
@@ -0,0 +1,172 @@
+<?xml version='1.0'?>
+<!-- 
+	Samba-documentation specific stylesheets
+	Published under the GNU GPL
+
+	(C) Jelmer Vernooij 					2002-2004
+-->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"
+	version="1.1">
+
+	<xsl:output method="xml" encoding="UTF-8" doctype-public="-//OASIS//DTD DocBook XML V4.2//EN" indent="yes" doctype-system="http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"/>
+
+	<xsl:include href="strip-references.xsl"/>
+	<xsl:include href="expand-smbconfdoc.xsl"/>
+
+	<!-- This is needed to copy content unchanged -->
+	<xsl:template match="@*|node()">
+		<xsl:copy>
+			<xsl:apply-templates select="@*|node()"/>
+		</xsl:copy>
+	</xsl:template>
+
+	<xsl:template name="smbconfoption">
+		<xsl:param name="name"/>
+		<xsl:param name="content"/>
+		<xsl:variable name="linkcontent">
+			<xsl:element name="parameter">
+				<xsl:attribute name="moreinfo">
+					<xsl:text>none</xsl:text>
+				</xsl:attribute>
+				<xsl:value-of select="$name"/>	
+			</xsl:element>
+
+			<xsl:choose>
+				<xsl:when test="$content != ''">
+					<xsl:text> = </xsl:text>
+					<xsl:value-of select="$content"/>
+				</xsl:when>
+			</xsl:choose>
+		</xsl:variable>
+
+		<xsl:choose>
+			<xsl:when test="$noreference = 1">
+				<xsl:value-of select="$linkcontent"/>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:element name="link">
+					<xsl:attribute name="linkend">
+						<xsl:value-of select="translate(translate(string($name),' ',''),'abcdefghijklmnopqrstuvwxyz','ABCDEFGHIJKLMNOPQRSTUVWXYZ')"/>
+					</xsl:attribute>
+					<xsl:value-of select="$linkcontent"/>
+				</xsl:element>
+			</xsl:otherwise>
+		</xsl:choose>
+	</xsl:template>
+
+	<xsl:template match="related">
+		<xsl:element name="para">
+			<xsl:text>Related command: </xsl:text>
+			<xsl:call-template name="smbconfoption">
+				<xsl:with-param name="name" select="text()"/>
+			</xsl:call-template>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="smbconfblock/smbconfoption">
+		<xsl:element name="member">
+			<xsl:element name="indexterm">
+					<xsl:value-of select="@name"/>
+			</xsl:element>
+			<xsl:choose>
+				<xsl:when test="text() != ''">
+					<xsl:element name="parameter">
+						<xsl:value-of select="@name"/>
+						<xsl:text> = </xsl:text>
+						<xsl:value-of select="text()"/>
+					</xsl:element>
+				</xsl:when>
+			</xsl:choose>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="smbconfblock/smbconfcomment">
+		<xsl:element name="member">
+			<xsl:text># </xsl:text>
+			<xsl:apply-templates/>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="smbconfblock/smbconfsection">
+		<xsl:element name="member">
+			<xsl:text> </xsl:text>
+		</xsl:element>
+		<xsl:element name="member">
+			<xsl:element name="parameter">
+				<xsl:value-of select="@name"/>
+			</xsl:element>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="smbconfoption">
+		<xsl:call-template name="smbconfoption">
+			<xsl:with-param name="name" select="@name"/>
+			<xsl:with-param name="content"><xsl:copy-of select="text()"/></xsl:with-param>
+		</xsl:call-template>
+	</xsl:template>
+
+
+	<xsl:template match="smbconfblock">
+		<xsl:element name="simplelist">
+			<xsl:apply-templates/>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="smbconfsection">
+		<xsl:element name="parameter">
+			<xsl:value-of select="@name"/>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="imagefile">
+		<xsl:element name="mediaobject">
+			<xsl:element name="imageobject">
+				<xsl:attribute name="role"><xsl:text>html</xsl:text></xsl:attribute>
+				<xsl:element name="imagedata">
+					<xsl:attribute name="fileref">
+						<xsl:text>images/</xsl:text><xsl:value-of select="text()"/><xsl:text>.png</xsl:text></xsl:attribute>
+					<xsl:attribute name="scale">
+						<xsl:choose>
+							<xsl:when test="@scale != ''">
+								<xsl:value-of select="@scale"/>
+							</xsl:when>
+
+							<xsl:otherwise>
+								<xsl:text>100</xsl:text>
+							</xsl:otherwise>
+						</xsl:choose>
+					</xsl:attribute>
+					<xsl:attribute name="scalefit"><xsl:text>1</xsl:text></xsl:attribute>
+				</xsl:element>
+			</xsl:element>
+			<xsl:element name="imageobject">
+				<xsl:element name="imagedata">
+					<xsl:attribute name="fileref">
+						<xsl:text>images/</xsl:text><xsl:value-of select="text()"/><xsl:text>.png</xsl:text></xsl:attribute>
+					<xsl:attribute name="scale">
+						<xsl:choose>
+							<xsl:when test="@scale != ''">
+								<xsl:value-of select="@scale"/>
+							</xsl:when>
+
+							<xsl:otherwise>
+								<xsl:text>50</xsl:text>
+							</xsl:otherwise>
+						</xsl:choose>
+					</xsl:attribute>
+					<xsl:attribute name="scalefit"><xsl:text>1</xsl:text></xsl:attribute>
+				</xsl:element>
+			</xsl:element>
+			<xsl:element name="imageobject">
+				<xsl:attribute name="role"><xsl:text>latex</xsl:text></xsl:attribute>
+				<xsl:element name="imagedata">
+					<xsl:attribute name="fileref">
+						<xsl:value-of select="$latex.imagebasedir"/><xsl:text>images/</xsl:text><xsl:value-of select="text()"/></xsl:attribute>
+				</xsl:element>
+			</xsl:element>
+
+		</xsl:element>
+	</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/expand-smbconfdoc.xsl b/docs-xml/xslt/expand-smbconfdoc.xsl
new file mode 100644
index 00000000000..5472d61a9af
--- /dev/null
+++ b/docs-xml/xslt/expand-smbconfdoc.xsl
@@ -0,0 +1,168 @@
+<?xml version='1.0'?>
+<!-- 
+	smb.conf-documentation specific stylesheets
+	Published under the GNU GPL
+
+	(C) Jelmer Vernooij 					2002-2004
+	(C) Alexander Bokovoy 					2002-2004
+-->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"
+	version="1.1">
+
+	<xsl:template match="description"><xsl:apply-templates/></xsl:template>
+
+	<xsl:template match="value"><xsl:element name="literal"><xsl:apply-templates/></xsl:element></xsl:template>
+	
+	<xsl:template match="command"><xsl:element name="literal"><xsl:apply-templates/></xsl:element></xsl:template>
+
+	<xsl:template match="synonym"><xsl:apply-templates/></xsl:template>
+
+	<xsl:template match="related"><xsl:element name="para"><xsl:text>Related command</xsl:text><xsl:apply-templates/></xsl:element></xsl:template>
+
+	<xsl:template match="samba:parameterlist">
+		<xsl:apply-templates>
+			<xsl:sort select="samba:parameter/@name"/>
+		</xsl:apply-templates>
+	</xsl:template>
+
+	<xsl:template match="value/comment">
+		<xsl:text>&#10;# </xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="samba:parameter">
+		<xsl:variable name="cname"><xsl:value-of select="translate(translate(string(@name),' ',''),
+				'abcdefghijklmnopqrstuvwxyz','ABCDEFGHIJKLMNOPQRSTUVWXYZ')"/>
+		</xsl:variable>
+
+		<xsl:variable name="name"><xsl:value-of select="@name"/></xsl:variable>
+
+		<xsl:variable name="anchor">
+			<xsl:element name="anchor">
+				<xsl:attribute name="id">
+					<xsl:value-of select="$cname"/>
+				</xsl:attribute>
+			</xsl:element>
+		</xsl:variable>
+
+		<xsl:variable name="context">
+			<xsl:text> (</xsl:text>
+			<xsl:value-of select="@context"/>
+			<xsl:text>)</xsl:text>
+		</xsl:variable>
+
+		<xsl:variable name="term">
+			<xsl:element name="indexterm">
+				<xsl:copy-of select="$anchor"/>
+				<xsl:value-of select="@name"/>
+				<xsl:value-of select="$context"/>
+			</xsl:element>
+		</xsl:variable>
+
+
+		<!-- Generate list of examples -->
+		<xsl:variable name="examples">
+			<xsl:for-each select="value">
+				<xsl:if test="@type = 'example'">
+					<xsl:element name="para">
+						<xsl:text>Example: </xsl:text>
+						<xsl:element name="emphasis">
+							<xsl:element name="parameter">
+								<xsl:copy-of select="$name"/>
+							</xsl:element>
+							<xsl:text> = </xsl:text>
+							<xsl:apply-templates select="."/>
+							<xsl:text>&#10;</xsl:text>
+						</xsl:element>
+						<xsl:text>&#10;</xsl:text>
+					</xsl:element>
+				</xsl:if>
+			</xsl:for-each>
+		</xsl:variable>
+
+		<xsl:variable name="tdefault">
+			<xsl:for-each select="value">
+				<xsl:if test="@type = 'default'">
+					<xsl:element name="para">
+						<xsl:text>Default: </xsl:text>
+						<xsl:element name="emphasis">
+							<xsl:element name="parameter">
+								<xsl:copy-of select="$name"/>
+							</xsl:element>
+							<xsl:text> = </xsl:text>
+							<xsl:apply-templates select="."/>
+							<xsl:text>&#10;</xsl:text>
+						</xsl:element>
+						<xsl:text>&#10;</xsl:text>
+					</xsl:element>
+				</xsl:if>
+			</xsl:for-each>
+		</xsl:variable>
+
+		<xsl:variable name="default">
+			<xsl:choose>
+				<xsl:when test="$tdefault = ''">
+					<xsl:element name="para">
+						<xsl:element name="emphasis">
+							<xsl:text>No default</xsl:text>
+						</xsl:element>	
+					</xsl:element>
+				</xsl:when>
+				<xsl:otherwise>
+					<xsl:copy-of select="$tdefault"/>
+				</xsl:otherwise>
+			</xsl:choose>
+		</xsl:variable>
+
+		<xsl:variable name="content">
+			<xsl:apply-templates select="description"/>
+		</xsl:variable>
+
+		<xsl:for-each select="synonym">
+			<xsl:element name="varlistentry">
+				<xsl:text>&#10;</xsl:text>     
+				<xsl:element name="indexterm">
+					<xsl:attribute name="significance">
+						<xsl:text>preferred</xsl:text>
+					</xsl:attribute>
+					<xsl:element name="primary">
+						<xsl:value-of select="."/>
+					</xsl:element>
+					<xsl:element name="see">
+						<xsl:value-of select="$name"/>
+					</xsl:element>
+				</xsl:element>
+				<xsl:element name="term">
+					<xsl:element name="anchor">
+						<xsl:attribute name="id">
+							<xsl:value-of select="translate(translate(string(.),' ',''), 'abcdefghijklmnopqrstuvwxyz','ABCDEFGHIJKLMNOPQRSTUVWXYZ')"/>
+						</xsl:attribute>
+					</xsl:element>
+					<xsl:value-of select="."/>
+				</xsl:element>
+				<xsl:element name="listitem">
+					<xsl:element name="para"><xsl:text>This parameter is a synonym for </xsl:text><xsl:copy-of select="$name"/><xsl:text>.</xsl:text></xsl:element>
+				</xsl:element>
+			</xsl:element>
+		</xsl:for-each>
+
+		<xsl:element name="varlistentry">
+			<xsl:text>&#10;</xsl:text>     
+			<xsl:element name="indexterm">
+				<xsl:attribute name="significance">
+					<xsl:text>preferred</xsl:text>
+				</xsl:attribute>
+				<xsl:element name="primary">
+					<xsl:value-of select="@name"/>
+				</xsl:element>
+			</xsl:element>
+			<xsl:copy-of select="$term"/>
+			<xsl:element name="listitem">
+				<xsl:copy-of select="$content"/> <xsl:text>&#10;</xsl:text>
+				<xsl:copy-of select="$default"/> <xsl:text>&#10;</xsl:text>
+				<xsl:copy-of select="$examples"/> <xsl:text>&#10;</xsl:text>
+			</xsl:element>
+		</xsl:element>
+	</xsl:template>
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/extract-examples.xsl b/docs-xml/xslt/extract-examples.xsl
new file mode 100644
index 00000000000..fc90addecc2
--- /dev/null
+++ b/docs-xml/xslt/extract-examples.xsl
@@ -0,0 +1,50 @@
+<?xml version='1.0'?>
+<!--
+Extract examples out of DocBook/XML file
+	(C) Jelmer Vernooij	2003
+-->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                xmlns:exsl="http://exslt.org/common"
+				xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"
+		version="1.1"
+                extension-element-prefixes="exsl">
+
+<xsl:output method="xml"/>
+
+<xsl:template match="example/title"></xsl:template>
+
+<xsl:template match="example/simplelist/title"></xsl:template>
+
+<!-- Parse all varlistentries and extract those of them which are descriptions of smb.conf
+     parameters. We determine them by existence of <anchor> element inside <term> element.
+     If <anchor> is there, then its 'id' attribute is translated to lower case and is used
+     as basis for file name for that parameter.
+-->
+<xsl:template match="example">
+	<!-- reconstruct varlistentry - not all of them will go into separate files
+	and also we must repair the main varlistentry itself.
+	-->
+	<xsl:variable name="content">
+		<xsl:apply-templates/>
+	</xsl:variable>
+	<!-- Now put varlistentry into separate file _if_ it has anchor associated with it -->
+	<xsl:variable name="filename"><xsl:text>examples/</xsl:text><xsl:value-of select="@id"/>.conf</xsl:variable>
+	<!-- Debug message for an operator, just to show progress of processing :) -->
+	<xsl:message>
+		<xsl:text>Writing </xsl:text>
+		<xsl:value-of select="$filename"/>
+		<xsl:text> for </xsl:text>
+		<xsl:value-of select="title"/>
+	</xsl:message>
+	<!-- Write finally varlistentry to a separate file -->
+	<exsl:document href="{$filename}" 
+		method="xml" 
+		encoding="UTF-8" 
+		indent="yes"
+		omit-xml-declaration="yes">
+		<xsl:copy-of select="$content"/>
+	</exsl:document>
+</xsl:template>
+
+</xsl:stylesheet>
+
diff --git a/docs-xml/xslt/figures/caution.eps b/docs-xml/xslt/figures/caution.eps
new file mode 100644
index 00000000000..54bd2be6ba8
--- /dev/null
+++ b/docs-xml/xslt/figures/caution.eps
@@ -0,0 +1,158 @@
+%!PS-Adobe-3.0 EPSF-3.0
+%%Creator: GIMP PostScript file plugin V 1.16 by Peter Kirchgessner
+%%Title: /home/users/jht/SVN/samba-docs/xslt/figures/caution.eps
+%%CreationDate: Wed Apr 13 23:49:51 2005
+%%DocumentData: Clean7Bit
+%%LanguageLevel: 2
+%%Pages: 1
+%%BoundingBox: 14 14 43 43
+%%EndComments
+%%BeginProlog
+% Use own dictionary to avoid conflicts
+10 dict begin
+%%EndProlog
+%%Page: 1 1
+% Translate for offset
+14.173228346456694 14.173228346456694 translate
+% Translate to begin of first scanline
+0 28.800000000000001 translate
+28.800000000000001 -28.800000000000001 scale
+% Image geometry
+40 40 8
+% Transformation matrix
+[ 40 0 0 40 0 0 ]
+% Strings to hold RGB-samples per scanline
+/rstr 40 string def
+/gstr 40 string def
+/bstr 40 string def
+{currentfile /ASCII85Decode filter /RunLengthDecode filter rstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter gstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter bstr readstring pop}
+true 3
+%%BeginData:         2261 ASCII Bytes
+colorimage
+mf3:emf.e~>
+mf3:emf.e~>
+mf3:emf.e~>
+nc/Cbnc++~>
+nc/Cbnc++~>
+nc/Cbnc++~>
+oDe^gs8VusoDa=~>
+oDe^gs8VusoDa=~>
+oDe^gs8VusoDa=~>
+o`+jiqZ$Npo`'F~>
+o`+jiqZ$Npo`'F~>
+o`+jiqZ$Npo`'F~>
+p&G!kp](3mp&BO~>
+p&G!kp](3mp&BO~>
+p&G!kp](3mp&BO~>
+pAb*lp&G!kpA]X~>
+pAb*lp&G!kpA]X~>
+pAb*lp&G!kpA]X~>
+p](3moDedip]#a~>
+p](3moDedip]#a~>
+p](3moDedip]#a~>
+q#C<nnc/Rgq#>j~>
+q#C<nnc/Rgq#>j~>
+q#C<nnc/Rgq#>j~>
+q>^Eon,N@eq>Ys~>
+q>^Eon,N@eq>Ys~>
+q>^Eon,N@eq>Ys~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qu?Wqq>^<lq>^Eoqu;0~>
+r;Z`rq#C3kq#C<nr;V9~>
+r;Z`rq#C3kq#C<nr;V9~>
+r;Z`rq#C3kq#C<nr;V9~>
+rVuisp](*jp](3mrVqB~>
+rVuisp](*jp](3mrVqB~>
+rVuisp](*jp](3mrVqB~>
+rr;rtp&FpipAb*lrr7K~>
+rr;rtp&FpipAb*lrr7K~>
+rr;rtp&FpipAb*lrr7K~>
+rr;uuo`+ghp&G!ks8RT~>
+rr;uuo`+ghp&G!ks8RT~>
+rr;uuo`+ghp&G!ks8RT~>
+s8W*!oDe^go`+pks8RT~>
+s8W*!oDe^go`+pks8RT~>
+s8W*!oDe^go`+pks8RT~>
+!<<#uoDeaho)J^i!<7Q~>
+!<<#uoDeaho)J^i!<7Q~>
+!<<#uoDeaho)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!<<#uo)J^inc/Uh!<7Q~>
+!<<#uo)J^inc/Uh!<7Q~>
+!<<#uo)J^inc/Uh!<7Q~>
+s8W*!o)J^io)J[h!<7Q~>
+s8W*!o)J^io)J[h!<7Q~>
+s8W*!o)J^io)J[h!<7Q~>
+s8W&uj8])Ys8RT~>
+s8W&uj8])Ys8RT~>
+s8W&uj8])Ys8RT~>
+rr;rtjo>;[rr7K~>
+rr;rtjo>;[rr7K~>
+rr;rtjo>;[rr7K~>
+rVuispAb'kpAb*lrVqB~>
+rVuispAb'kpAb*lrVqB~>
+rVuispAb'kpAb*lrVqB~>
+r;Z`rp](-kq#C<nr;V9~>
+r;Z`rp](-kq#C<nr;V9~>
+r;Z`rp](-kq#C<nr;V9~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qZ$Npq>^?mqZ$NpqYu'~>
+q>^EoqZ$Hnqu?Wqq>Ys~>
+q>^EoqZ$Hnqu?Wqq>Ys~>
+q>^EoqZ$Hnqu?Wqq>Ys~>
+q#C<nnc/Rgq#>j~>
+q#C<nnc/Rgq#>j~>
+q#C<nnc/Rgq#>j~>
+p](3moDedip]#a~>
+p](3moDedip]#a~>
+p](3moDedip]#a~>
+pAb*lp&G!kpA]X~>
+pAb*lp&G!kpA]X~>
+pAb*lp&G!kpA]X~>
+p&G!kp](3mp&BO~>
+p&G!kp](3mp&BO~>
+p&G!kp](3mp&BO~>
+o`+mjq>^Eoo`'F~>
+o`+mjq>^Eoo`'F~>
+o`+mjq>^Eoo`'F~>
+oDeahr;Z`roDa=~>
+oDeahr;Z`roDa=~>
+oDeahr;Z`roDa=~>
+o)JFao)F4~>
+o)JFao)F4~>
+o)JFao)F4~>
+nGi@cnGe"~>
+nGi@cnGe"~>
+nGi@cnGe"~>
+g&HR~>
+g&HR~>
+g&HR~>
+%%EndData
+showpage
+%%Trailer
+end
+%%EOF
diff --git a/docs-xml/xslt/figures/important.eps b/docs-xml/xslt/figures/important.eps
new file mode 100644
index 00000000000..13b80498f68
--- /dev/null
+++ b/docs-xml/xslt/figures/important.eps
@@ -0,0 +1,158 @@
+%!PS-Adobe-3.0 EPSF-3.0
+%%Creator: GIMP PostScript file plugin V 1.16 by Peter Kirchgessner
+%%Title: /home/users/jht/SVN/samba-docs/xslt/figures/important.eps
+%%CreationDate: Wed Apr 13 23:49:17 2005
+%%DocumentData: Clean7Bit
+%%LanguageLevel: 2
+%%Pages: 1
+%%BoundingBox: 14 14 43 43
+%%EndComments
+%%BeginProlog
+% Use own dictionary to avoid conflicts
+10 dict begin
+%%EndProlog
+%%Page: 1 1
+% Translate for offset
+14.173228346456694 14.173228346456694 translate
+% Translate to begin of first scanline
+0 28.800000000000001 translate
+28.800000000000001 -28.800000000000001 scale
+% Image geometry
+40 40 8
+% Transformation matrix
+[ 40 0 0 40 0 0 ]
+% Strings to hold RGB-samples per scanline
+/rstr 40 string def
+/gstr 40 string def
+/bstr 40 string def
+{currentfile /ASCII85Decode filter /RunLengthDecode filter rstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter gstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter bstr readstring pop}
+true 3
+%%BeginData:         2261 ASCII Bytes
+colorimage
+mf3:emf.e~>
+mf3:emf.e~>
+mf3:emf.e~>
+nc/Cbnc++~>
+nc/Cbnc++~>
+nc/Cbnc++~>
+oDe^gs8VusoDa=~>
+oDe^gs8VusoDa=~>
+oDe^gs8VusoDa=~>
+o`+jiqZ$Npo`'F~>
+o`+jiqZ$Npo`'F~>
+o`+jiqZ$Npo`'F~>
+p&G!kp](3mp&BO~>
+p&G!kp](3mp&BO~>
+p&G!kp](3mp&BO~>
+pAb*lp&G!kpA]X~>
+pAb*lp&G!kpA]X~>
+pAb*lp&G!kpA]X~>
+p](3moDedip]#a~>
+p](3moDedip]#a~>
+p](3moDedip]#a~>
+q#C<nnc/Rgq#>j~>
+q#C<nnc/Rgq#>j~>
+q#C<nnc/Rgq#>j~>
+q>^Eon,N@eq>Ys~>
+q>^Eon,N@eq>Ys~>
+q>^Eon,N@eq>Ys~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qu?Wqq>^<lq>^Eoqu;0~>
+r;Z`rq#C3kq#C<nr;V9~>
+r;Z`rq#C3kq#C<nr;V9~>
+r;Z`rq#C3kq#C<nr;V9~>
+rVuisp](*jp](3mrVqB~>
+rVuisp](*jp](3mrVqB~>
+rVuisp](*jp](3mrVqB~>
+rr;rtp&FpipAb*lrr7K~>
+rr;rtp&FpipAb*lrr7K~>
+rr;rtp&FpipAb*lrr7K~>
+rr;uuo`+ghp&G!ks8RT~>
+rr;uuo`+ghp&G!ks8RT~>
+rr;uuo`+ghp&G!ks8RT~>
+s8W*!oDe^go`+pks8RT~>
+s8W*!oDe^go`+pks8RT~>
+s8W*!oDe^go`+pks8RT~>
+!<<#uoDeaho)J^i!<7Q~>
+!<<#uoDeaho)J^i!<7Q~>
+!<<#uoDeaho)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#o)JXgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!ri6#nc/Rgo)J^i!<7Q~>
+!<<#uo)J^inc/Uh!<7Q~>
+!<<#uo)J^inc/Uh!<7Q~>
+!<<#uo)J^inc/Uh!<7Q~>
+s8W*!o)J^io)J[h!<7Q~>
+s8W*!o)J^io)J[h!<7Q~>
+s8W*!o)J^io)J[h!<7Q~>
+s8W&uj8])Ys8RT~>
+s8W&uj8])Ys8RT~>
+s8W&uj8])Ys8RT~>
+rr;rtjo>;[rr7K~>
+rr;rtjo>;[rr7K~>
+rr;rtjo>;[rr7K~>
+rVuispAb'kpAb*lrVqB~>
+rVuispAb'kpAb*lrVqB~>
+rVuispAb'kpAb*lrVqB~>
+r;Z`rp](-kq#C<nr;V9~>
+r;Z`rp](-kq#C<nr;V9~>
+r;Z`rp](-kq#C<nr;V9~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qu?Wqq>^<lq>^Eoqu;0~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qZ$Npq>^?mqZ$NpqYu'~>
+qZ$Npq>^?mqZ$NpqYu'~>
+q>^EoqZ$Hnqu?Wqq>Ys~>
+q>^EoqZ$Hnqu?Wqq>Ys~>
+q>^EoqZ$Hnqu?Wqq>Ys~>
+q#C<nnc/Rgq#>j~>
+q#C<nnc/Rgq#>j~>
+q#C<nnc/Rgq#>j~>
+p](3moDedip]#a~>
+p](3moDedip]#a~>
+p](3moDedip]#a~>
+pAb*lp&G!kpA]X~>
+pAb*lp&G!kpA]X~>
+pAb*lp&G!kpA]X~>
+p&G!kp](3mp&BO~>
+p&G!kp](3mp&BO~>
+p&G!kp](3mp&BO~>
+o`+mjq>^Eoo`'F~>
+o`+mjq>^Eoo`'F~>
+o`+mjq>^Eoo`'F~>
+oDeahr;Z`roDa=~>
+oDeahr;Z`roDa=~>
+oDeahr;Z`roDa=~>
+o)JFao)F4~>
+o)JFao)F4~>
+o)JFao)F4~>
+nGi@cnGe"~>
+nGi@cnGe"~>
+nGi@cnGe"~>
+g&HR~>
+g&HR~>
+g&HR~>
+%%EndData
+showpage
+%%Trailer
+end
+%%EOF
diff --git a/docs-xml/xslt/figures/note.eps b/docs-xml/xslt/figures/note.eps
new file mode 100644
index 00000000000..8ce4a801dc9
--- /dev/null
+++ b/docs-xml/xslt/figures/note.eps
@@ -0,0 +1,152 @@
+%!PS-Adobe-3.0 EPSF-3.0
+%%Creator: GIMP PostScript file plugin V 1.16 by Peter Kirchgessner
+%%Title: /home/users/jht/SVN/samba-docs/xslt/figures/note.eps
+%%CreationDate: Wed Apr 13 23:48:34 2005
+%%DocumentData: Clean7Bit
+%%LanguageLevel: 2
+%%Pages: 1
+%%BoundingBox: 14 14 42 42
+%%EndComments
+%%BeginProlog
+% Use own dictionary to avoid conflicts
+10 dict begin
+%%EndProlog
+%%Page: 1 1
+% Translate for offset
+14.173228346456694 14.173228346456694 translate
+% Translate to begin of first scanline
+0 27.354330708661422 translate
+27.354330708661422 -27.354330708661422 scale
+% Image geometry
+38 38 8
+% Transformation matrix
+[ 38 0 0 38 0 0 ]
+% Strings to hold RGB-samples per scanline
+/rstr 38 string def
+/gstr 38 string def
+/bstr 38 string def
+{currentfile /ASCII85Decode filter /RunLengthDecode filter rstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter gstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter bstr readstring pop}
+true 3
+%%BeginData:         2705 ASCII Bytes
+colorimage
+g])d~>
+g])d~>
+g])d~>
+nc/LenGe"~>
+nc/LenGe"~>
+nc/LenGe"~>
+pAa^ao`'F~>
+pAa^ao`'F~>
+pAa^ao`'F~>
+p](-kqZ$HnpA]X~>
+p](-kqZ$HnpA]X~>
+p](-kqZ$HnpA]X~>
+q>^EooDeahq#>j~>
+q>^EooDeahq#>j~>
+q>^EooDeahq#>j~>
+qZ$NpnGiIfq>Ys~>
+qZ$NpnGiIfq>Ys~>
+qZ$NpnGiIfq>Ys~>
+r;Z`rmJm+bqu;0~>
+r;Z`rmJm+bqu;0~>
+r;Z`rmJm+bqu;0~>
+r;ZcslMpkaqu;0~>
+r;ZcslMpkaqu;0~>
+r;ZcslMpkaqu;0~>
+rVultkl:Y_r;V9~>
+rVultkl:Y_r;V9~>
+rVultkl:Y_r;V9~>
+rr;uus8VoqnGiIfrVqB~>
+rr;uus8VoqnGiIfrVqB~>
+rr;uus8VoqnGiIfrVqB~>
+rr;uu!ri6#rVuisnGiLgrVqB~>
+rr;uu!ri6#rVuisnGiLgrVqB~>
+rr;uu!ri6#rVuisnGiLgrVqB~>
+s8W*!s8N<(s8N*!rrE)u!:g*h!<3"K~>
+s8W*!s8N<(s8N*!rrE)u!:g*h!<3"K~>
+s8W*!s8N<(s8N*!rrE)u!:g*h!<3"K~>
+#QFc(s8N'!s8E!$rr<'!s8E#is8E#us*t~>
+#QFc(s8N'!s8E!$rr<'!s8E#is8E#us*t~>
+#QFc(s8N'!s8E!$rr<'!s8E#is8E#us*t~>
+#6+Z'rr<'!r;Zp!!!)utrrDZjrrE*!J,~>
+#6+Z'rr<'!r;Zp!!!)utrrDZjrrE*!J,~>
+#6+Z'rr<'!r;Zp!!!)utrrDZjrrE*!J,~>
+#6+Z'rr<'!rW)uur;cisrW)WkrrE*!J,~>
+#6+Z'rr<'!rW)uur;cisrW)WkrrE*!J,~>
+#6+Z'rr<'!rW)uur;cisrW)WkrrE*!J,~>
+!WN0!rs8]*!!*'!!!*'!rW)rtrW)]mrrE*!J,~>
+!WN0!rs8]*!!*'!!!*'!rW)rtrW)]mrrE*!J,~>
+!WN0!rs8]*!!*'!!!*'!rW)rtrW)]mrrE*!J,~>
+rrE&u!!)utrrE#tr;cisrrDfn!W`9#J,~>
+rrE&u!!)utrrE#tr;cisrrDfn!W`9#J,~>
+rrE&u!!)utrrE#tr;cisrrDfn!W`9#J,~>
+rrE&uq>gEmrW)rtrrDiorr<'!J,~>
+rrE&uq>gEmrW)rtrrDiorr<'!J,~>
+rrE&uq>gEmrW)rtrrDiorr<'!J,~>
+rrE#trW)uurW)iqrW)uurrDlprr<'!J,~>
+rrE#trW)uurW)iqrW)uurrDlprr<'!J,~>
+rrE#trW)uurW)iqrW)uurrDlprr<'!J,~>
+rrDusrW)rtrW)iqqZ-Kmrr<'!J,~>
+rrDusrW)rtrW)iqqZ-Kmrr<'!J,~>
+rrDusrW)rtrW)iqqZ-Kmrr<'!J,~>
+rrDrrrW)rtrW)iqrW!!!!;c`q!!*%L~>
+rrDrrrW)rtrW)iqrW!!!!;c`q!!*%L~>
+rrDrrrW)rtrW)iqrW!!!!;c`q!!*%L~>
+rrDlprW)rtrW)lrrr<-#!!)orrr<'!J,~>
+rrDlprW)rtrW)lrrr<-#!!)orrr<'!J,~>
+rrDlprW)rtrW)lrrr<-#!!)orrr<'!J,~>
+rrDfnrW)rtrW)rt!!*#u!!)or!W`9#J,~>
+rrDfnrW)rtrW)rt!!*#u!!)or!W`9#J,~>
+rrDfnrW)rtrW)rt!!*#u!!)or!W`9#J,~>
+!WN/ns8E#ts8E!"rr<&us8N)ts8N*!s*t~>
+!WN/ns8E#ts8E!"rr<&us8N)ts8N*!s*t~>
+!WN/ns8E#ts8E!"rr<&us8N)ts8N*!s*t~>
+!ri6#p&G!krr;rtr;Zcsrr;uus8RT~>
+!ri6#p&G!krr;rtr;Zcsrr;uus8RT~>
+!ri6#p&G!krr;rtr;Zcsrr;uus8RT~>
+!ri6#oDedi!ri6#r;Z`rrr;uus8RT~>
+!ri6#oDedi!ri6#r;Z`rrr;uus8RT~>
+!ri6#oDedi!ri6#r;Z`rrr;uus8RT~>
+!ri6#o)J=^rr;uus8RT~>
+!ri6#o)J=^rr;uus8RT~>
+!ri6#o)J=^rr;uus8RT~>
+s8W*!nGi7`rr;uurr7K~>
+s8W*!nGi7`rr;uurr7K~>
+s8W*!nGi7`rr;uurr7K~>
+s8W&uk5YD\rr7K~>
+s8W&uk5YD\rr7K~>
+s8W&uk5YD\rr7K~>
+rr;uuk5YG]rVqB~>
+rr;uuk5YG]rVqB~>
+rr;uuk5YG]rVqB~>
+rVultkl:Y_r;V9~>
+rVultkl:Y_r;V9~>
+rVultkl:Y_r;V9~>
+rVuislMpkaqu;0~>
+rVuislMpkaqu;0~>
+rVuislMpkaqu;0~>
+r;Z`rm/R%bqu;0~>
+r;Z`rm/R%bqu;0~>
+r;Z`rm/R%bqu;0~>
+qu?Wqn,N=dqYu'~>
+qu?Wqn,N=dqYu'~>
+qu?Wqn,N=dqYu'~>
+q>^Eoo)J[hq#>j~>
+q>^Eoo)J[hq#>j~>
+q>^Eoo)J[hq#>j~>
+q#C6lq#C6lp]#a~>
+q#C6lq#C6lp]#a~>
+q#C6lq#C6lp]#a~>
+pAa[`p&BO~>
+pAa[`p&BO~>
+pAa[`p&BO~>
+o)JOdnc++~>
+o)JOdnc++~>
+o)JOdnc++~>
+%%EndData
+showpage
+%%Trailer
+end
+%%EOF
diff --git a/docs-xml/xslt/figures/tip.eps b/docs-xml/xslt/figures/tip.eps
new file mode 100644
index 00000000000..5fb7c31ddb3
--- /dev/null
+++ b/docs-xml/xslt/figures/tip.eps
@@ -0,0 +1,152 @@
+%!PS-Adobe-3.0 EPSF-3.0
+%%Creator: GIMP PostScript file plugin V 1.16 by Peter Kirchgessner
+%%Title: /home/users/jht/SVN/samba-docs/xslt/figures/tip.eps
+%%CreationDate: Wed Apr 13 23:47:57 2005
+%%DocumentData: Clean7Bit
+%%LanguageLevel: 2
+%%Pages: 1
+%%BoundingBox: 14 14 42 42
+%%EndComments
+%%BeginProlog
+% Use own dictionary to avoid conflicts
+10 dict begin
+%%EndProlog
+%%Page: 1 1
+% Translate for offset
+14.173228346456694 14.173228346456694 translate
+% Translate to begin of first scanline
+0 27.354330708661422 translate
+27.354330708661422 -27.354330708661422 scale
+% Image geometry
+38 38 8
+% Transformation matrix
+[ 38 0 0 38 0 0 ]
+% Strings to hold RGB-samples per scanline
+/rstr 38 string def
+/gstr 38 string def
+/bstr 38 string def
+{currentfile /ASCII85Decode filter /RunLengthDecode filter rstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter gstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter bstr readstring pop}
+true 3
+%%BeginData:         2579 ASCII Bytes
+colorimage
+g])d~>
+g])d~>
+g])d~>
+nc/LenGe"~>
+nc/LenGe"~>
+nc/LenGe"~>
+pAa^ao`'F~>
+pAa^ao`'F~>
+pAa^ao`'F~>
+p](-kqZ$HnpA]X~>
+p](-kqZ$HnpA]X~>
+p](-kqZ$HnpA]X~>
+q>^EooDeahq#>j~>
+q>^EooDeahq#>j~>
+q>^EooDeahq#>j~>
+qZ$NpnGiIfq>Ys~>
+qZ$NpnGiIfq>Ys~>
+qZ$NpnGiIfq>Ys~>
+r;Z`rmJm+bqu;0~>
+r;Z`rmJm+bqu;0~>
+r;Z`rmJm+bqu;0~>
+r;ZcslMpkaqu;0~>
+r;ZcslMpkaqu;0~>
+r;ZcslMpkaqu;0~>
+rVultkl:Y_r;V9~>
+rVultkl:Y_r;V9~>
+rVultkl:Y_r;V9~>
+rr;uukPtM]rVqB~>
+rr;uukPtM]rVqB~>
+rr;uukPtM]rVqB~>
+rr;uuk5YG]rVqB~>
+rr;uuk5YG]rVqB~>
+rr;uuk5YG]rVqB~>
+s8W*!jT#5[rr7K~>
+s8W*!jT#5[rr7K~>
+s8W*!jT#5[rr7K~>
+!ri6#j8])Ys8RT~>
+!ri6#j8])Ys8RT~>
+!ri6#j8])Ys8RT~>
+!ri6#p&FU`r;Zcss8RT~>
+!ri6#p&FU`r;Zcss8RT~>
+!ri6#p&FU`r;Zcss8RT~>
+"TJH%s8Vrrs8W#ts8W&us8Vlps8W*!s8RT~>
+"TJH%s8Vrrs8W#ts8W&us8Vlps8W*!s8RT~>
+"TJH%s8Vrrs8W#ts8W&us8Vlps8W*!s8RT~>
+!WN0!s8E#us8;rps8N)os8N'%rr<'!s*t~>
+!WN0!s8E#us8;rps8N)os8N'%rr<'!s*t~>
+!WN0!s8E#us8;rps8N)os8N'%rr<'!s*t~>
+rrE&urW)uurrDus!!*#urrDlprrE*!!W`9#J,~>
+rrE&urW)uurrDus!!*#urrDlprrE*!!W`9#J,~>
+rrE&urW)uurrDus!!*#urrDlprrE*!!W`9#J,~>
+rrE&urW)uu!!)orrrE&upAk3mrr<'!J,~>
+rrE&urW)uu!!)orrrE&upAk3mrr<'!J,~>
+rrE&urW)uu!!)orrrE&upAk3mrr<'!J,~>
+rrE&urW)uu!!)lqrVururW)]mrr<'!J,~>
+rrE&urW)uu!!)lqrVururW)]mrr<'!J,~>
+rrE&urW)uu!!)lqrVururW)]mrr<'!J,~>
+rrE&urW)uu"T\T&!<<)q!!<0#!;QTo!!*%L~>
+rrE&urW)uu"T\T&!<<)q!!<0#!;QTo!!*%L~>
+rrE&urW)uu"T\T&!<<)q!!<0#!;QTo!!*%L~>
+rrE&urW)uu!W`9#quHZprW)`nrr<'!J,~>
+rrE&urW)uu!W`9#quHZprW)`nrr<'!J,~>
+rrE&urW)uu!W`9#quHZprW)`nrr<'!J,~>
+rrE&urW)uu!!)or!W`9#r;Zlu!;QTo!!*%L~>
+rrE&urW)uu!!)or!W`9#r;Zlu!;QTo!!*%L~>
+rrE&urW)uu!!)or!W`9#r;Zlu!;QTo!!*%L~>
+rrE&urW)uu!!)orr;cisrrDio!W`9#J,~>
+rrE&urW)uu!!)orr;cisrrDio!W`9#J,~>
+rrE&urW)uu!!)orr;cisrrDio!W`9#J,~>
+!WN0!s8E#us8;rqrrN3#s82lns8N*!s*t~>
+!WN0!s8E#us8;rqrrN3#s82lns8N*!s*t~>
+!WN0!s8E#us8;rqrrN3#s82lns8N*!s*t~>
+"TJH%s8Vrrs8W&urr;oss8W*!qZ$Qqs8RT~>
+"TJH%s8Vrrs8W&urr;oss8W*!qZ$Qqs8RT~>
+"TJH%s8Vrrs8W&urr;oss8W*!qZ$Qqs8RT~>
+"TJH%s8VrrrVu`prr;rtqZ$Qqs8RT~>
+"TJH%s8VrrrVu`prr;rtqZ$Qqs8RT~>
+"TJH%s8VrrrVu`prr;rtqZ$Qqs8RT~>
+!ri6#nGiCdq#C?os8RT~>
+!ri6#nGiCdq#C?os8RT~>
+!ri6#nGiCdq#C?os8RT~>
+s8W*!jT#5[rr7K~>
+s8W*!jT#5[rr7K~>
+s8W*!jT#5[rr7K~>
+s8W&uk5YD\rr7K~>
+s8W&uk5YD\rr7K~>
+s8W&uk5YD\rr7K~>
+rr;uuk5YG]rVqB~>
+rr;uuk5YG]rVqB~>
+rr;uuk5YG]rVqB~>
+rVultkl:Y_r;V9~>
+rVultkl:Y_r;V9~>
+rVultkl:Y_r;V9~>
+rVuislMpkaqu;0~>
+rVuislMpkaqu;0~>
+rVuislMpkaqu;0~>
+r;Z`rm/R%bqu;0~>
+r;Z`rm/R%bqu;0~>
+r;Z`rm/R%bqu;0~>
+qu?Wqn,N=dqYu'~>
+qu?Wqn,N=dqYu'~>
+qu?Wqn,N=dqYu'~>
+q>^Eoo)J[hq#>j~>
+q>^Eoo)J[hq#>j~>
+q>^Eoo)J[hq#>j~>
+q#C6lq#C6lp]#a~>
+q#C6lq#C6lp]#a~>
+q#C6lq#C6lp]#a~>
+pAa[`p&BO~>
+pAa[`p&BO~>
+pAa[`p&BO~>
+o)JOdnc++~>
+o)JOdnc++~>
+o)JOdnc++~>
+%%EndData
+showpage
+%%Trailer
+end
+%%EOF
diff --git a/docs-xml/xslt/figures/warning.eps b/docs-xml/xslt/figures/warning.eps
new file mode 100644
index 00000000000..184452b4c27
--- /dev/null
+++ b/docs-xml/xslt/figures/warning.eps
@@ -0,0 +1,134 @@
+%!PS-Adobe-3.0 EPSF-3.0
+%%Creator: GIMP PostScript file plugin V 1.16 by Peter Kirchgessner
+%%Title: /home/users/jht/w2.eps
+%%CreationDate: Thu Apr 14 00:46:36 2005
+%%DocumentData: Clean7Bit
+%%LanguageLevel: 2
+%%Pages: 1
+%%BoundingBox: 14 14 47 47
+%%EndComments
+%%BeginProlog
+% Use own dictionary to avoid conflicts
+10 dict begin
+%%EndProlog
+%%Page: 1 1
+% Translate for offset
+14.173228346456694 14.173228346456694 translate
+% Translate to begin of first scanline
+0 32 translate
+32 -32 scale
+% Image geometry
+32 32 8
+% Transformation matrix
+[ 32 0 0 32 0 0 ]
+% Strings to hold RGB-samples per scanline
+/rstr 32 string def
+/gstr 32 string def
+/bstr 32 string def
+{currentfile /ASCII85Decode filter /RunLengthDecode filter rstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter gstr readstring pop}
+{currentfile /ASCII85Decode filter /RunLengthDecode filter bstr readstring pop}
+true 3
+%%BeginData:         1493 ASCII Bytes
+colorimage
+i;eB~>
+i;eB~>
+i;eB~>
+i;eB~>
+i;eB~>
+i;eB~>
+rrD0\rr@Q~>
+rrD0Yrr@Q~>
+rrD0Yrr@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rr<'!k5tec!!%N~>
+rr<&sk5YS]!!%N~>
+rr<&sk5YS]!!%N~>
+rr<'!k5tec!!%N~>
+rr<&sk5YS]!!%N~>
+rr<&sk5YS]!!%N~>
+rr<'!k5tec!!%N~>
+rr<&sk5YS]!!%N~>
+rr<&sk5YS]!!%N~>
+rr<'!k5tec!!%N~>
+rr<&sk5YS]!!%N~>
+rr<&sk5YS]!!%N~>
+rr<'!k5tec!!%N~>
+rr<&sk5YS]!!%N~>
+rr<&sk5YS]!!%N~>
+rr<'!k5tec!!%N~>
+rr<&sk5YS]!!%N~>
+rr<&sk5YS]!!%N~>
+rr<'!k5tec!!%N~>
+rr<&sk5YS]!!%N~>
+rr<&sk5YS]!!%N~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrDfnq?-Hkrr@Q~>
+rrDfkq>g6err@Q~>
+rrDfkq>g6err@Q~>
+rrD0\rr@Q~>
+rrD0Yrr@Q~>
+rrD0Yrr@Q~>
+i;eB~>
+i;eB~>
+i;eB~>
+i;eB~>
+i;eB~>
+i;eB~>
+%%EndData
+showpage
+%%Trailer
+end
+%%EOF
diff --git a/docs-xml/xslt/fo.xsl b/docs-xml/xslt/fo.xsl
new file mode 100644
index 00000000000..f095f5df8f9
--- /dev/null
+++ b/docs-xml/xslt/fo.xsl
@@ -0,0 +1,8 @@
+<?xml version='1.0'?>
+<!-- vim:set sts=2 shiftwidth=2 syntax=xml: -->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                version='1.0'>
+
+<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl"/>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/generate-attributions.xsl b/docs-xml/xslt/generate-attributions.xsl
new file mode 100644
index 00000000000..90e3e17568b
--- /dev/null
+++ b/docs-xml/xslt/generate-attributions.xsl
@@ -0,0 +1,82 @@
+<?xml version='1.0'?>
+<!--
+	Generate Docbook/XML file with attributions based on chapter/author tags
+	(C) Jelmer Vernooij 2003
+-->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+				version="1.1">
+
+				<xsl:output method="xml" doctype-public="-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" doctype-system="http://www.samba.org/samba/DTD/samba-doc" indent="yes"/>
+
+<!-- Remove all character data -->
+<xsl:template match="@*|node()">
+   <xsl:apply-templates select="@*|node()"/>
+</xsl:template>
+
+<xsl:template match="/">
+	<xsl:element name="preface">
+		<xsl:element name="title"><xsl:text>Attribution</xsl:text></xsl:element>
+		<xsl:apply-templates/>
+	</xsl:element>
+</xsl:template>
+
+<xsl:template match="chapter|preface">
+	<xsl:choose>
+		<xsl:when test="chapterinfo/author != ''">
+			<xsl:element name="para">
+				<xsl:element name="link">
+					<xsl:attribute name="linkend"><xsl:value-of select="@id"/></xsl:attribute>
+					<xsl:value-of select="title"/>
+				</xsl:element>
+				<xsl:text>&#10;&#9;</xsl:text>
+				<xsl:element name="itemizedlist">
+					<xsl:apply-templates/>
+				<xsl:text>&#9;</xsl:text>
+				</xsl:element>
+				<xsl:text>&#10;</xsl:text>
+			</xsl:element>
+		</xsl:when>
+	</xsl:choose>
+</xsl:template>
+
+<xsl:template match="chapterinfo/author">
+	<xsl:choose>
+	<xsl:when test="firstname != ''">
+	<xsl:text>&#9;</xsl:text>
+	<xsl:element name="listitem">
+		<xsl:element name="para">
+			<xsl:value-of select="firstname"/>
+			<xsl:if test="othername != ''">
+				<xsl:text> </xsl:text>
+				<xsl:value-of select="othername"/>
+				<xsl:text> </xsl:text>
+			</xsl:if>
+			<xsl:text> </xsl:text><xsl:value-of select="surname"/>
+			<xsl:choose>
+				<xsl:when test="affiliation/address/email != ''">
+					<xsl:element name="ulink">
+						<xsl:attribute name="noescape">
+						<xsl:text>1</xsl:text>
+						</xsl:attribute>
+						<xsl:attribute name="url">
+							<xsl:text>mailto:</xsl:text>
+							<xsl:value-of select="affiliation/address/email"/>
+						</xsl:attribute>
+					</xsl:element>
+				</xsl:when>
+			</xsl:choose>
+			<xsl:choose>
+				<xsl:when test="contrib != ''">
+					<xsl:text> (</xsl:text>
+						<xsl:value-of select="contrib"/>
+					<xsl:text>) </xsl:text>
+					</xsl:when>
+			</xsl:choose>
+		</xsl:element>
+	</xsl:element>
+	<xsl:text>&#10;</xsl:text>
+	</xsl:when>
+	</xsl:choose>
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/generate-dependencies.xsl b/docs-xml/xslt/generate-dependencies.xsl
new file mode 100644
index 00000000000..e47ec6c698b
--- /dev/null
+++ b/docs-xml/xslt/generate-dependencies.xsl
@@ -0,0 +1,53 @@
+<?xml version='1.0'?>
+<!--
+	Find the image dependencies of a certain XML file
+	Generates (part of) a Makefile
+
+	- $(FNAME)-images-latex-{png,dvi} for role=latex
+	- $(FNAME)-images-role for all other roles
+	- $(TXTDIR)/$(FNAME)-text 
+
+	(C) Jelmer Vernooij	2004-2005
+-->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.1">
+	<xsl:output method="text"/>
+
+	<xsl:template match="/">
+		<xsl:for-each select="//mediaobject/imageobject[@role and not(@role=following::imageobject/@role)]">
+			<xsl:call-template name="generate-images">
+				<xsl:with-param name="role"><xsl:value-of select="@role"/></xsl:with-param>
+			</xsl:call-template>
+		</xsl:for-each>
+		<xsl:call-template name="generate-images">
+			<xsl:with-param name="role"/>
+		</xsl:call-template>
+		<xsl:call-template name="generate-txt-chunks"/>
+	</xsl:template>
+
+	<xsl:template name="generate-images">
+		<xsl:param name="role"/>
+		<xsl:value-of select="$target"/><xsl:text>-images-</xsl:text><xsl:value-of select="$role"/><xsl:text> = </xsl:text>
+		<xsl:for-each select="//mediaobject/imageobject[@role=$role]">
+			<xsl:value-of select="imagedata/@fileref"/>
+			<xsl:text> </xsl:text>
+		</xsl:for-each>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template name="generate-txt-chunks">
+		<xsl:value-of select="$target"/><xsl:text>-txt-chunks: </xsl:text>
+		<xsl:for-each select="(//chapter|//preface|//appendix)[@id]|book">
+			<xsl:value-of select="$txtbasedir"/>
+			<xsl:choose>
+				<xsl:when test="name() = 'book'">
+					<xsl:text>index</xsl:text>
+				</xsl:when>
+				<xsl:when test="@id != ''">
+					<xsl:value-of select="@id"/>
+				</xsl:when>
+			</xsl:choose>
+			<xsl:text>.txt </xsl:text>
+		</xsl:for-each>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/html-chunk.xsl b/docs-xml/xslt/html-chunk.xsl
new file mode 100644
index 00000000000..00b310610aa
--- /dev/null
+++ b/docs-xml/xslt/html-chunk.xsl
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- This file is generated from param.xweb; do not edit this file! -->
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+
+<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl"/>
+<xsl:import href="html-common.xsl"/>
+<xsl:param name="chunk.first.sections" select="1"/>
+<xsl:param name="chunk.quietly" select="0"/>
+<xsl:param name="chunk.section.depth" select="0"/>
+<xsl:param name="chunk.toc" select="''"/>
+<xsl:param name="chunk.tocs.and.lots" select="0"/>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/html-common.xsl b/docs-xml/xslt/html-common.xsl
new file mode 100644
index 00000000000..b584214cd71
--- /dev/null
+++ b/docs-xml/xslt/html-common.xsl
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- This file is generated from param.xweb; do not edit this file! -->
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
+                xmlns:xlink='http://www.w3.org/1999/xlink'
+                exclude-result-prefixes="xlink"
+		version="1.0">
+
+<xsl:param name="base.dir" select="'../htmldocs/'"/>
+<xsl:param name="bridgehead.in.toc" select="1"/>
+<xsl:param name="citerefentry.link" select="'1'"/>
+<xsl:param name="css.decoration" select="1"/>
+<xsl:param name="html.stylesheet" select="'samba.css'"/>
+<xsl:param name="html.stylesheet.type">text/css</xsl:param>
+<xsl:param name="use.extensions" select="'0'"/>
+<xsl:param name="use.id.as.filename" select="'1'"/>
+<xsl:param name="use.local.olink.style" select="1"/> 
+<xsl:param name="use.role.as.xrefstyle" select="1"/>
+<xsl:param name="use.role.for.mediaobject" select="1"/>
+
+<xsl:template name="generate.citerefentry.link">
+  <xsl:value-of select="refentrytitle"/><xsl:text>.</xsl:text><xsl:value-of select="manvolnum"/><xsl:text>.html</xsl:text>
+</xsl:template>
+
+<xsl:template match="author">
+</xsl:template>
+
+<xsl:template match="link" name="link">
+  <xsl:param name="linkend" select="@linkend"/>
+  <xsl:param name="a.target"/>
+  <xsl:param name="xhref" select="@xlink:href"/>
+
+  <xsl:variable name="content">
+    <xsl:call-template name="anchor"/>
+    <xsl:choose>
+      <xsl:when test="count(child::node()) &gt; 0">
+        <!-- If it has content, use it -->
+        <xsl:apply-templates/>
+      </xsl:when>
+      <!-- else look for an endterm -->
+      <xsl:when test="@endterm">
+        <xsl:variable name="etargets" select="key('id',@endterm)"/>
+        <xsl:variable name="etarget" select="$etargets[1]"/>
+        <xsl:choose>
+          <xsl:when test="count($etarget) = 0">
+            <xsl:message>
+              <xsl:value-of select="count($etargets)"/>
+              <xsl:text>Endterm points to nonexistent ID: </xsl:text>
+              <xsl:value-of select="@endterm"/>
+            </xsl:message>
+            <xsl:text>???</xsl:text>
+          </xsl:when>
+          <xsl:otherwise>
+              <xsl:apply-templates select="$etarget" mode="endterm"/>
+          </xsl:otherwise>
+        </xsl:choose>
+      </xsl:when>
+      <xsl:otherwise>
+         <xsl:choose>
+            <xsl:when test="key('id', @linkend)/title[1]">
+	      <xsl:call-template name="gentext.startquote"/>
+	      <xsl:value-of select="key('id', @linkend)/title[1]"/>
+	      <xsl:call-template name="gentext.endquote"/>
+            </xsl:when>
+         <xsl:otherwise>
+    	    <xsl:message>
+        	<xsl:text>Link element has no content and no Endterm. And linkend's pointer has no title. </xsl:text>
+        	<xsl:text>Nothing to show in the link to </xsl:text>
+        	<xsl:value-of select="(@linkend)[1]"/>
+    	    </xsl:message>
+    	 </xsl:otherwise>
+        </xsl:choose>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:variable>
+
+  <xsl:call-template name="simple.xlink">
+    <xsl:with-param name="node" select="."/>
+    <xsl:with-param name="linkend" select="$linkend"/>
+    <xsl:with-param name="content" select="$content"/>
+    <xsl:with-param name="a.target" select="$a.target"/>
+    <xsl:with-param name="xhref" select="$xhref"/>
+  </xsl:call-template>
+
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/html.xsl b/docs-xml/xslt/html.xsl
new file mode 100644
index 00000000000..8481a86d248
--- /dev/null
+++ b/docs-xml/xslt/html.xsl
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- This file is generated from param.xweb; do not edit this file! -->
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+
+<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl"/>
+<xsl:import href="html-common.xsl"/>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/html/samba.css b/docs-xml/xslt/html/samba.css
new file mode 100644
index 00000000000..3d926e8e741
--- /dev/null
+++ b/docs-xml/xslt/html/samba.css
@@ -0,0 +1,80 @@
+BODY {
+	font-family: helvetica, arial, lucida sans, sans-serif;
+	background-color: white;
+}
+
+H1, H2, H3 {
+	color: blue;
+	font-size: 120%;
+	padding: 2px;
+	margin-top: 0px;
+}
+
+H1 {
+	background-color: #EEEEFF;
+	color: blue;
+}
+
+H2 {
+	background-color: #DDDDFF;
+	color: blue;
+}
+
+H3 {
+	background-color: #CCCCFF;
+	color: blue;
+}
+
+H4 {
+	color: blue;
+}
+
+TR.qandadiv TD {
+	padding-top: 1em;
+}
+
+DIV.navhead {
+	font-size: 80%;
+}
+
+A:link {
+	color: #36F;
+}
+
+A:visited {
+	color: #96C;
+}
+
+A:active {
+	color: #F63;
+}
+
+TR.question {
+	color: #33C;
+	font-weight: bold;
+}
+
+TR.question TD {
+	padding-top: 1em;
+}
+
+DIV.variablelist {
+	padding-left: 2em;
+	color: #33C;
+}
+
+P {
+	color: black;
+}
+
+DIV.note, DIV.warning, DIV.caution, DIV.tip, DIV.important {
+	border: dashed 1px;
+	background-color: #EEEEFF;
+	width: 40em;
+}
+
+PRE.programlisting, PRE.screen {
+	border: #630 1px dashed;
+	color: #630;
+}
+
diff --git a/docs-xml/xslt/latex.overrides.xml b/docs-xml/xslt/latex.overrides.xml
new file mode 100644
index 00000000000..1923a63f083
--- /dev/null
+++ b/docs-xml/xslt/latex.overrides.xml
@@ -0,0 +1,10 @@
+<?xml version='1.0'?>
+<!DOCTYPE latexbindings SYSTEM "db2latex-xsl/xsl/latex.mapping.dtd">
+<latexbindings>
+	<latexmapping role="begin">
+	</latexmapping>
+	<latexmapping role="end">
+		<mapping key="glossary" text=""/>
+		<mapping key="index" text=""/>
+	</latexmapping>
+</latexbindings>
diff --git a/docs-xml/xslt/latex.xsl b/docs-xml/xslt/latex.xsl
new file mode 100644
index 00000000000..bb0907df558
--- /dev/null
+++ b/docs-xml/xslt/latex.xsl
@@ -0,0 +1,227 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'
+	xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<xsl:import href="db2latex-xsl/xsl/docbook.xsl"/>
+<xsl:import href="strip-references.xsl"/>
+
+<xsl:param name="latex.mapping.xml" select="document('latex.overrides.xml')"/>
+
+<xsl:param name="generate.toc">
+	/appendix toc,title
+	article/appendix  nop
+	/article  toc,title
+	book      toc,title,figure,table,example,equation
+	/chapter  toc,title,lop
+	part      toc,title
+	/preface  toc,title
+	qandadiv  toc
+	qandaset  toc
+	procedure lop
+	reference toc,title
+	/sect1    toc
+	/sect2    toc
+	/sect3    toc
+	/sect4    toc
+	/sect5    toc
+	/section  toc
+	set       toc,title
+</xsl:param>
+
+<!-- Show real name of the link rather then user specified description -->
+<xsl:template match="link">
+	<xsl:variable name="target" select="key('id',@linkend)[1]"/>
+	<xsl:variable name="refelem" select="local-name($target)"/>
+	<xsl:if test="$refelem=''">
+		<xsl:message><xsl:text>XRef to nonexistent id: </xsl:text><xsl:value-of select="@linkend"/></xsl:message>
+		<xsl:text>XrefId[?</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>?]</xsl:text>
+	</xsl:if>
+
+	<xsl:call-template name="generate.hyperlink">
+		<xsl:with-param name="target" select="$target"/>
+		<xsl:with-param name="text">
+			<xsl:call-template name="generate.xref.text">
+				<xsl:with-param name="target" select="$target"/>
+			</xsl:call-template>
+		</xsl:with-param>
+	</xsl:call-template>
+</xsl:template>
+
+<!-- LaTeX doesn't accept verbatim stuff in titles -->
+<xsl:template match="//title/filename|//title/command|//title/parameter|//title/constant">
+  <xsl:variable name="content">
+    <xsl:apply-templates/>
+  </xsl:variable>
+  <xsl:if test="$content != ''">
+    <xsl:value-of select="$content" />
+  </xsl:if>
+</xsl:template>
+
+<xsl:output method="text" encoding="UTF-8" indent="yes"/>
+<xsl:variable name="l10n.gentext.default.language" select="'en'"/>
+<xsl:variable name="latex.document.font">default</xsl:variable>
+<xsl:variable name="latex.example.caption.style"></xsl:variable>
+<xsl:variable name="latex.hyperref.param.pdftex">hyperfigures,hyperindex,citecolor=black,urlcolor=black,filecolor=black,linkcolor=black,menucolor=red,pagecolor=black</xsl:variable>
+<xsl:variable name="admon.graphics.path">xslt/figures</xsl:variable>
+<xsl:variable name="latex.use.tabularx">1</xsl:variable>
+<xsl:variable name="latex.fancyhdr.lh"></xsl:variable>
+<xsl:variable name="latex.use.fancyhdr"></xsl:variable>
+<xsl:variable name="latex.use.parskip">1</xsl:variable>
+<xsl:variable name="latex.use.ucs">1</xsl:variable>
+<xsl:variable name="latex.inputenc">utf8</xsl:variable>
+<xsl:variable name="latex.book.varsets" select="''"/>
+<xsl:variable name="latex.hyphenation.tttricks">1</xsl:variable>
+<xsl:variable name="latex.titlepage.file"></xsl:variable>
+<xsl:template name="latex.thead.row.entry">
+<xsl:text>{\bfseries </xsl:text><xsl:apply-templates/><xsl:text>}</xsl:text>
+</xsl:template>
+<xsl:variable name="latex.documentclass">sambadoc</xsl:variable>
+<xsl:variable name="latex.babel.language">english</xsl:variable>
+<xsl:variable name="ulink.footnotes" select="1"/>
+<xsl:variable name="ulink.show" select="0"/>
+
+<xsl:template match="smbconfblock/smbconfoption">
+	<xsl:text>	</xsl:text><xsl:value-of select="@name"/>
+	<xsl:if test="text() != ''">
+		<xsl:text> = </xsl:text>
+		<xsl:value-of select="text()"/>
+	</xsl:if>
+	<xsl:text>&#10;</xsl:text>
+</xsl:template>
+
+<xsl:template match="smbconfblock/smbconfcomment">
+	<xsl:text># </xsl:text>
+	<xsl:apply-templates/>
+	<xsl:text>&#10;</xsl:text>
+</xsl:template>
+
+<xsl:template match="smbconfblock/smbconfsection">
+	<xsl:value-of select="@name"/>
+	<xsl:text>&#10;</xsl:text>
+</xsl:template>
+
+<xsl:template match="smbconfoption">
+	<xsl:text>\smbconfoption{</xsl:text>
+	<xsl:call-template name="scape">
+		<xsl:with-param name="string" select="@name"/>
+	</xsl:call-template>
+	<xsl:text>}</xsl:text>
+
+	<xsl:choose>
+		<xsl:when test="text() != ''">
+			<xsl:text> = </xsl:text>
+			<xsl:call-template name="scape">
+				<xsl:with-param name="string" select="text()"/>
+			</xsl:call-template>
+		</xsl:when>
+	</xsl:choose>
+</xsl:template>
+
+<xsl:template match="smbconfblock">
+	<xsl:text>&#10;\begin{lstlisting}[language=smbconf,style=smbconfblock]&#10;</xsl:text>
+	<xsl:apply-templates/>
+	<xsl:text>\end{lstlisting}&#10;</xsl:text>
+</xsl:template>
+
+<xsl:template match="smbconfsection">
+	<xsl:text>\smbconfsection{</xsl:text>
+	<xsl:call-template name="scape">
+		<xsl:with-param name="string" select="@name"/>
+	</xsl:call-template>
+	<xsl:text>}</xsl:text>
+</xsl:template>
+
+<xsl:template match="imagefile">
+	<xsl:text>\includegraphics[scale=</xsl:text>
+	<xsl:choose>
+		<xsl:when test="@scale != ''"><xsl:value-of select="@scale div 100"/></xsl:when>
+
+		<xsl:otherwise><xsl:text>.50</xsl:text></xsl:otherwise>
+	</xsl:choose>
+	<xsl:text>]{</xsl:text>
+	<xsl:value-of select="$latex.imagebasedir"/><xsl:text>images/</xsl:text>
+	<xsl:value-of select="text()"/>
+	<xsl:text>}&#10;</xsl:text>
+</xsl:template>
+
+<!-- smb.conf documentation -->
+
+<xsl:template match="description"><xsl:apply-templates/></xsl:template>
+
+<xsl:template match="value"><xsl:apply-templates/></xsl:template>
+
+<xsl:template match="synonym"><xsl:apply-templates/></xsl:template>
+
+<xsl:template match="related"><xsl:apply-templates/></xsl:template>
+
+<xsl:template match="//samba:parameterlist">
+	<xsl:text>\begin{description}&#10;</xsl:text>
+	<xsl:apply-templates>
+		<xsl:sort select="samba:parameter/@name"/>
+	</xsl:apply-templates>
+	<xsl:text>\end{description}&#10;</xsl:text>
+</xsl:template>
+
+<xsl:template match="value/comment">
+	<xsl:text>&#10;# </xsl:text>
+	<xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="/">
+	<xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="refentry">
+	<xsl:text>\section{</xsl:text><xsl:value-of select="refmeta/refentrytitle"/><xsl:text>}&#10;</xsl:text>
+	<xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="//samba:parameter">
+	<xsl:for-each select="synonym">
+		<xsl:text>\item[{</xsl:text><xsl:value-of select="."/><xsl:text>}]\null{}&#10;</xsl:text>
+	<xsl:text>\index{</xsl:text><xsl:value-of select="."/><xsl:text>}&#10;</xsl:text>
+	<xsl:text>This parameter is a synonym for \smbconfoption{</xsl:text><xsl:value-of select="../@name"/><xsl:text>}.</xsl:text>
+	</xsl:for-each>
+
+	<xsl:text>\item[{</xsl:text><xsl:value-of select="@name"/>
+	<xsl:text> (</xsl:text>
+	<xsl:value-of select="@context"/>
+	<xsl:text>)</xsl:text>
+	<xsl:text>}]\null{}&#10;&#10;</xsl:text>
+	<xsl:text>\index{</xsl:text><xsl:value-of select="@name"/><xsl:text>}&#10;</xsl:text>
+
+	<!-- Print default value-->
+	<xsl:text>&#10;</xsl:text>
+	<xsl:text>Default: </xsl:text>
+	<xsl:text>\emph{</xsl:text>
+	<xsl:choose>
+		<xsl:when test="value[@type='default'] != ''">
+			<xsl:value-of select="@name"/>
+			<xsl:text> = </xsl:text>
+			<xsl:apply-templates select="value"/>
+		</xsl:when>
+		<xsl:otherwise>
+			<xsl:text>No default</xsl:text>
+		</xsl:otherwise>
+	</xsl:choose>
+	<xsl:text>}</xsl:text>
+	<xsl:text>&#10;</xsl:text>
+
+	<!-- Generate list of examples -->
+	<xsl:text>&#10;</xsl:text>
+	<xsl:for-each select="value[@type='example']">
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>Example: </xsl:text>
+		<xsl:text>\emph{</xsl:text><xsl:value-of select="../@name"/>
+		<xsl:text> = </xsl:text>
+		<xsl:apply-templates select="."/>
+		<xsl:text>}</xsl:text>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:for-each>
+
+	<!-- Description -->
+	<xsl:apply-templates select="description"/>
+</xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/latex/sambadoc.cls b/docs-xml/xslt/latex/sambadoc.cls
new file mode 100644
index 00000000000..8fe0043bc95
--- /dev/null
+++ b/docs-xml/xslt/latex/sambadoc.cls
@@ -0,0 +1,345 @@
+% $Id$
+% phstyle.cls -- Macros for formatting Prentice-Hall Books
+%               -- Compiled by J.K. Shultis, Dec. 1993
+% 		-- Modified and enhanced for LaTeX2e mdh/rlm 1997/02
+%       -- Style Modifications Lori Hughes June 2002 
+%       -- Modifications for Samba by Jelmer Vernooij 2003-2005
+
+\NeedsTeXFormat{LaTeX2e}%
+\ProvidesClass{sambadoc}[2005/06/13 Samba Documentation class]
+\newif\if@ph
+\@phfalse
+\DeclareOption{ph}{ \@phtrue }
+\DeclareOption*{\PassOptionsToClass{\CurrentOption}{report}}
+\ProcessOptions%
+
+%  Base everything on the default class 'report'.
+\LoadClass{report}%
+%================================================================================
+% 1. Page layout dimensions
+% 3. Define new fonts for headings
+% 4. Redefines the way "figure" amd "table" are formated in a \caption
+% 5. Defines a \capt macro which defines (1) \captwidth, (2) \captsize
+%    and \beforetableskip.
+% 6. Defines and modifies FANCYHDS.STY for headers and foots
+% 7. Change sectioning headings to bold sans serif fonts
+% 8. Turn off leader dots in Table of Contents
+%======================================================================
+
+%====================== Page Layout
+% \oddsidemargin 0.750in   \evensidemargin 0.750in  \textwidth 5.00in
+% \topmargin     0.625in    \headheight     0.3in    \headsep  0.2in
+% \textheight    7.3in     %\footheight .2in        
+% \footskip      0.3in
+% \parskip       0ex       \marginparwidth 1.00in  \marginparsep 0.5in
+%\setlength\arraycolsep{1pt}
+
+\if@ph
+	\RequirePackage{geometry}
+	\geometry{
+	twoside,
+	openleft,
+	papersize={7in,9.25in},
+	lmargin=.75in,
+	rmargin=.75in,
+	bmargin=.625in,
+	tmargin=.825in,
+	width=5.5in,
+	height=7.325in, 
+	marginparwidth=0.35in,
+	headheight=0.2in,
+	textwidth=5in,
+	headsep=.25in,
+	footskip=.025in}
+	%\usepackage[letter,cam,cross,center]{crop}
+\fi
+
+%====================== Define special fonts
+\newfont{\BIG}{cminch}                             %--- One-inch font
+\newfont{\sfbHuge}{cmssbx10 scaled\magstep5}       %-- 25pt sans serif bold
+\newfont{\sfblarge}{cmssbx10 scaled\magstep1}      %-- 12pt sans serif bold
+\newfont{\sfbeleven}{cmssbx10 scaled\magstephalf}  %-- 11pt sans serif bold
+\newfont{\sfb}{cmssbx10}                           %-- 10pt sans serif bold
+\newfont{\sfeight}{cmss8}                          %-- 8pt sans serif
+\newfont{\sfnine}{cmss8 at 9pt}                     %-- 9pt sans serif
+
+\newfont{\defnem}{cmbxti10}                    %-- 10pt sans serif bold
+\def\spacingset#1{\def\baselinestretch{#1}\small\normalsize}
+
+%-----------Change section heading font sizes here----
+\newfont{\sfbsection}{cmssbx10 at 13pt}
+\newfont{\sfbsubsec}{cmssbx10 at 12pt}
+\newfont{\sfbsubsub}{cmssbx10 at 11pt}
+\newfont{\sfbpara}{cmssbx10}
+%---------------------------------------------------
+
+
+%
+% Theorem hack
+%
+
+\def\@begintheorem#1#2{\trivlist
+   \item[\hskip \labelsep{\bfseries #1\ #2:}]\itshape}
+
+%===================== Redefine the \@makecaption command
+   \long\def\@makecaption#1#2{\vskip 10\p@
+%% \setbox\@tempboxa\hbox{#1: #2}%         %% original label definition
+   \setbox\@tempboxa\hbox{\textbf{ \small #1.} \small #2}%   %% bold and . instead of :
+   \ifdim \wd\@tempboxa >\hsize
+%%     #1: #2\par                   %% original definition
+       \textbf{ \small #1.} \small #2\par             %% bold and . instead of :
+   \else
+    \hbox to\hsize{\hfil\box\@tempboxa\hfil}%   %% original
+%%      \hbox to\hsize{\box\@tempboxa\hfil}%             %% no centering
+   \fi}
+
+%===================== New caption macro
+\newlength{\captsize}         \let\captsize=\footnotesize
+\newlength{\captwidth}        \setlength{\captwidth}{\textwidth}
+\newlength{\beforetableskip}  \setlength{\beforetableskip}{.5\baselineskip}
+\newcommand{\capt}[1]{\begin{minipage}{\captwidth}
+          \let\normalsize=\captsize
+          \caption[#1]{#1}
+          \end{minipage}\\ \vspace{\beforetableskip}}
+		  
+
+%---------- Change Figure Label
+\newcommand{\thefigurename}{Figure}   %-- set default: Figure
+\def\fnum@figure{\thefigurename\ \thefigure}
+
+%       This is to get the equation numbers in the form (section.equation),
+%       and to have the equation counter reset every time the section 
+%       counter is incremented.
+
+\def\theequation{\thechapter.\arabic{equation}}
+\@addtoreset{equation}{chapter}
+
+\RequirePackage{fancyhdr}
+
+%------------------- Modify Headers for Prentice-Hall Book Style
+%---------- Setup headers and footers
+\pagestyle{fancyplain}
+
+%--- Redefine Headers
+\renewcommand{\sectionmark}[1]{\markright{\thesection\ #1}}
+%
+\lhead[\fancyplain{}{\bf\thepage}]{\fancyplain{}{\sfnine\rightmark}}
+%
+%\rhead[\fancyplain{}{\footnotesize\sf\CHHEAD}]{\fancyplain{}{\bf\thepage}}
+ \rhead[\fancyplain{}{\sfnine \leftmark}]{\fancyplain{}{\bf\thepage}}
+%--- Empty footers on every page (except initial chapter page which has
+%--- page number) and optionally a small date stamp
+\cfoot[\fancyplain{}{}]{\fancyplain{}{}}
+\rfoot[\fancyplain{}{}]{\fancyplain{\hspace{\fill}\\ \bf\thepage}{}}
+\lfoot[\fancyplain{\hspace{\fill}\\ \bf\thepage}{}]{\fancyplain{}{}}
+%-- replace the two lines above with the two below for a date stamp footer
+%\rfoot[\fancyplain{\scriptsize \today}{\scriptsize \today}]{\fancyplain{\bf\thepage}{}}
+%\lfoot[\fancyplain{\bf\thepage}{}]{\fancyplain{\scriptsize \today}{\scriptsize \today}}
+%--- Change format of section header
+%
+% rlm added chaptermark 10/11/96
+\def\sectionmark#1{\markright{\ifnum \c@secnumdepth >\z@
+  {\sfeight Section}~\thesection.\quad \fi #1}}
+\def\sectionsmark#1{\markright{#1}{#1}}
+%
+\def\chaptermark#1{\markboth{#1 \quad \@chapapp{}~\thechapter}{}}
+\def\chaptersmark#1{\markboth{#1}{#1}}
+
+
+%===================== Change Section Heads to Bold Sans Serif
+% Create bolds sans serif sectioning headings.  Also the headings have
+% been reduced in size with less space before and after the heading.
+% Modified from macros given in BK10.STY
+%
+%----------------------------- part ---------------------------------
+\def\@part[#1]#2{%
+	\thispagestyle{empty}
+	\ifodd\c@page\hbox{}\else\clearpage\fi
+	\addtocounter{page}{-2}
+	\thispagestyle{empty}
+	\ifnum \c@secnumdepth >-2\relax
+		\refstepcounter{part}%
+		\addcontentsline{toc}{part}{Part \thepart\hspace{1em}#1}%
+	\else
+		\addcontentsline{toc}{part}{Part #1}%
+	\fi
+	{\centering
+		\interlinepenalty \@M
+			\normalfont
+			\ifnum \c@secnumdepth >-2\relax
+				\huge\bfseries \partname\nobreakspace\thepart
+				\par
+				\vskip 20\p@
+			\fi
+			\Huge \bfseries #2\par}%
+	\@endpart}
+
+%------------------------- appendix -----------------------------------
+
+\let\oldappendix\appendix
+\def\appendix{\oldappendix\def\addchaptertoloe{}}
+
+%------------------------- chapter -----------------------------------
+\def\addchaptertoloe{%
+	\addtocontents{loe}{\protect\addvspace{14pt}}%
+	\addtocontents{loe}{\noindent {\bfseries Chapter~\thechapter}\protect\par}%
+	\addtocontents{loe}{\protect\addvspace{10pt}}%
+}
+
+\def\chapter{\clearpage \thispagestyle{plain} \global\@topnum\z@
+\@afterindentfalse \secdef\@chapter\@schapter} 
+\def\@chapter[#1]#2{\ifnum \c@secnumdepth >\m@ne
+ \refstepcounter{chapter}
+ \typeout{\@chapapp\space\thechapter.}
+ \addcontentsline{toc}{chapter}{Chapter~\protect
+ \numberline{\thechapter}\uppercase{#1}}\else
+ \addcontentsline{toc}{chapter}{Chapter~\uppercase{#1}}\fi
+ \chaptermark{#1}
+ \addchaptertoloe
+ \addtocontents{lof}{\protect\addvspace{10pt}}
+\addtocontents{lot}{\protect\addvspace{10pt}} \if@twocolumn
+\@topnewpage[\@makechapterhead{#2}] 
+ \else \@makechapterhead{#2}
+ \@afterheading \fi} 
+%
+\def\@schapter#1{\if@twocolumn \@topnewpage[\@makeschapterhead{#1}]
+ \else \@makeschapterhead{#1}\chaptersmark{#1}
+ \@afterheading\fi\addcontentsline{toc}{chapter}{\uppercase{#1}}}
+
+
+
+\def\@makechapterhead#1{\vspace*{-20pt}{\parindent0pt\raggedright
+\ifnum\c@secnumdepth>\m@ne\LARGE\sf\@chapapp{}~\thechapter\par
+\vskip3pt\hrule\vskip3pt\hrule
+\vskip30pt\fi\raggedright\Huge\sfbHuge\uppercase{#1}\par
+\nobreak\vskip70pt}}%\chaptermark{#1}}
+
+\def\@makeschapterhead#1{\vspace*{4pt}{\parindent0pt
+\vskip3pt\hrule\vskip3pt\hrule
+\vskip36pt\raggedright\Huge\sfbHuge\uppercase{#1}\par
+\nobreak\vskip70pt}}%\chaptersmark{#1}}
+\widowpenalty=1000
+\clubpenalty=1000
+
+%------------------------ section -----------------------------------
+\def\section{\@startsection{section}{1}{\z@}{-3.5ex plus-1ex
+  minus -.2ex}{1.8ex}{\sfbsection}}
+
+%--------------------- subsection -----------------------------------
+\def\subsection{\@startsection{subsection}{2}{\z@}{-2.75ex plus -1ex
+    minus -.2ex}{1.2ex}{\sfbsubsec}}
+
+%-------------------- subsubsection --------------------------------
+\def\subsubsection{\@startsection{subsubsection}{3}{\z@}{-2.75ex
+  plus -1ex minus -.2ex}{1.2ex}{\sfbsubsub}}
+
+%----------------------- paragraph ----------------------------------
+\def\paragraph{\@startsection{paragraph}{4}{\z@}{1.25ex plus
+     1ex minus .2ex}{-1em}{\sfbpara}}
+
+%---------------------- subparagraph --------------------------------
+\def\subparagraph{\@startsection{subparagraph}{4}{\parindent}{1.25ex
+     plus 1ex minus .2ex}{-1em}{\normalsize\sfb}}
+
+
+
+%====================== Turn off leader dots in Table of Contents
+\renewcommand{\@dotsep}{500}
+
+\def\tableofcontents{\markboth{}{}\@restonecolfalse\if@twocolumn\@restonecoltrue\onecolumn
+ \fi\thispagestyle{plain} \@makeschapterhead{Contents} 
+ \@afterheading
+ \chaptersmark{Contents}
+ \sectionsmark{Contents}
+ \@starttoc{toc}\if@restonecol\twocolumn\fi}
+
+
+\def\thebibliography#1{\chapter*{Bibliography}\list
+% \addcontentsline{toc}{chapter}{Bibliography}
+ {[\arabic{enumi}]}{\settowidth\labelwidth{2em}\leftmargin\labelwidth
+% \advance\leftmargin\labelsep
+ \usecounter{enumi}}
+ \def\newblock{\hskip .11em plus .33em minus .07em}
+ \sloppy\clubpenalty4000\widowpenalty4000
+ \sfcode`\.=1000\relax}
+\let\endthebibliography=\endlist
+
+
+%% BIBLIOGRAPHY
+%
+%% separate citations with "], ["
+\def\@citex[#1]#2{\if@filesw\immediate\write\@auxout{\string\citation{#2}}\fi
+\def\@citea{}\@cite{\@for\@citeb:=#2\do {\@citea\def\@citea{],
+[}\@ifundefined {b@\@citeb}{{\bf ?}\@warning {Citation `\@citeb' on
+page \thepage \space undefined}}%
+{\csname b@\@citeb\endcsname}}}{#1}}
+ 
+\def\@cite#1#2{[{#1\if@tempswa, #2\fi}]}
+
+
+%% index
+
+\def\theindex{\cleardoublepage\@restonecoltrue\if@twocolumn\@restonecolfalse\fi
+\columnseprule \z@
+\columnsep 35pt\twocolumn[\@makeschapterhead{Subject Index}]
+  \chaptersmark{Subject Index}%
+ \addcontentsline{toc}{chapter}{SUBJECT INDEX}
+ \thispagestyle{plain}\parindent\z@
+ \parskip\z@ plus .3pt\relax\let\item\@idxitem}
+
+
+\renewcommand{\cleardoublepage}{\clearpage\if@twoside \ifodd\c@page\else
+\hbox{}\thispagestyle{empty}\newpage\if@twocolumn\hbox{}\newpage\fi\fi\fi}
+
+\renewcommand{\numberline}[1]{\sbox\@tempboxa{#1\hspace{2pt}}%
+	                \ifdim\wd\@tempboxa>\@tempdima \else \wd\@tempboxa\@tempdima\fi
+						                           \box\@tempboxa}
+
+% Custom list of examples
+\def\listofexamples{\@restonecolfalse\if@twocolumn\@restonecoltrue\onecolumn
+  \fi\chapter*{List of Examples}
+  \renewcommand\@pnumwidth{0em}
+  \@starttoc{loe}\if@restonecol
+  \twocolumn\fi}
+
+\def\l@example{\noindent\@dottedtocline{1}{0em}{3.5em}}
+
+\renewcommand\listfigurename{\uppercase{List Of Figures}}
+\renewcommand\listtablename{\uppercase{List Of Tables}}
+
+% smb.conf syntax highlighting
+\RequirePackage{listings}
+\RequirePackage{xcolor}
+
+\lstdefinelanguage{smbconf}{
+	morecomment=[l]{\#},
+}
+
+\newcommand{\linebreaksign}{\hbox{\ensuremath\hookleftarrow}}
+
+\lstdefinestyle{smbconfblock}
+{
+	breaklines=true,
+	backgroundcolor=\color[gray]{0.93},
+	frame=single,
+	frameround=tttt,
+	prebreak={\space\linebreaksign},
+	basicstyle=\small
+}
+
+\newcommand{\smbconfsection}[1]{\emph{#1}}
+\newcommand{\smbconfoption}[1]{\index{#1}\emph{#1}}
+
+\setlength{\emergencystretch}{0cm}
+
+
+\cleardoublepage
+\pagenumbering{roman}
+
+\setcounter{page}{2}
+\setcounter{totalnumber}{8}
+\setcounter{bottomnumber}{3}
+\setcounter{topnumber}{3}
+\renewcommand{\textfraction}{0.1}
+\renewcommand{\topfraction}{1.0}
+\renewcommand{\bottomfraction}{1.0}
diff --git a/docs-xml/xslt/man.xsl b/docs-xml/xslt/man.xsl
new file mode 100644
index 00000000000..99b2112cb3a
--- /dev/null
+++ b/docs-xml/xslt/man.xsl
@@ -0,0 +1,146 @@
+<?xml version='1.0'?>
+<!-- vim:set sts=2 shiftwidth=2 syntax=xml: -->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                version='1.0'>
+
+<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"/>
+
+<xsl:param name="chunk.section.depth" select="0"/>
+<xsl:param name="chunk.first.sections" select="1"/>
+<xsl:param name="use.id.as.filename" select="1"/>
+
+<!-- 
+    Our ulink stylesheet omits @url part if content was specified
+-->
+<xsl:template match="ulink">
+  <xsl:variable name="content">
+    <xsl:apply-templates/>
+  </xsl:variable>
+  <xsl:if test="$content = ''">
+    <xsl:text>: </xsl:text>
+  </xsl:if>
+  <xsl:if test="$content != ''">
+    <xsl:value-of select="$content" />
+  </xsl:if>
+  <xsl:if test="$content = ''">
+    <xsl:apply-templates mode="italic" select="@url" />
+  </xsl:if>
+</xsl:template>
+
+<xsl:template match="itemizedlist/listitem">
+  <!-- * We output a real bullet here (rather than, "\(bu", -->
+  <!-- * the roff bullet) because, when we do character-map -->
+  <!-- * processing before final output, the character-map will -->
+  <!-- * handle conversion of the &#x2022; to "\(bu" for us -->
+  <xsl:text>&#10;</xsl:text>
+  <xsl:text>.sp</xsl:text>
+  <xsl:text>&#10;</xsl:text>
+  <xsl:text>.RS</xsl:text>
+  <xsl:if test="not($list-indent = '')">
+    <xsl:text> </xsl:text>
+    <xsl:value-of select="$list-indent"/>
+  </xsl:if>
+  <xsl:text>&#10;</xsl:text>
+  <!-- * if "n" then we are using "nroff", which means the output is for -->
+  <!-- * TTY; so we do some fixed-width-font hackery with \h to make a -->
+  <!-- * hanging indent (instead of using .IP, which has some -->
+  <!-- * undesirable side effects under certain circumstances) -->
+  <xsl:call-template name="roff-if-else-start"/>
+  <xsl:text>\h'-</xsl:text>
+  <xsl:choose>
+    <xsl:when test="not($list-indent = '')">
+      <xsl:text>0</xsl:text>
+      <xsl:value-of select="$list-indent"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:text>\n(INu</xsl:text>
+    </xsl:otherwise>
+  </xsl:choose>
+  <xsl:text>'</xsl:text>
+  <xsl:text>&#x2022;</xsl:text>
+  <xsl:text>\h'+</xsl:text>
+  <xsl:choose>
+    <xsl:when test="not($list-indent = '')">
+      <xsl:text>0</xsl:text>
+      <xsl:value-of select="$list-indent - 1"/>
+    </xsl:when>
+    <xsl:otherwise>
+      <xsl:text>\n(INu-1</xsl:text>
+    </xsl:otherwise>
+  </xsl:choose>
+  <xsl:text>'\c&#10;</xsl:text>
+  <!-- * else, we are not using for "nroff", but instead "troff" - which -->
+  <!-- * means not for TTY, but for PS or whatever; so we’re not using a -->
+  <!-- * fixed-width font, so use a real .IP instead -->
+  <xsl:call-template name="roff-else"/>
+  <!-- * .IP generates a blank like of space, so let’s go backwards one -->
+  <!-- * line up to compensate for that -->
+  <xsl:text>.sp -1&#10;</xsl:text>
+  <xsl:text>.IP \(bu 2.3&#10;</xsl:text>
+  <!-- * The value 2.3 is the amount of indentation; we use 2.3 instead -->
+  <!-- * of 2 because when the font family is New Century Schoolbook it -->
+  <!-- * seems to require the extra space. -->
+  <xsl:call-template name="roff-if-end"/>
+  <xsl:apply-templates/>
+  <xsl:if test=" following-sibling::listitem">
+	 <xsl:text>&#10;.RE&#10;</xsl:text>
+  </xsl:if>
+</xsl:template>
+
+<xsl:template match="itemizedlist|orderedlist|procedure">
+  <xsl:if test="title">
+    <xsl:text>.PP&#10;</xsl:text>
+    <xsl:call-template name="bold">
+      <xsl:with-param name="node" select="title"/>
+      <xsl:with-param name="context" select="."/>
+    </xsl:call-template>
+    <xsl:text>&#10;</xsl:text>
+  </xsl:if>
+  <!-- * DocBook allows just about any block content to appear in -->
+  <!-- * lists before the actual list items, so we need to get that -->
+  <!-- * content (if any) before getting the list items -->
+  <xsl:apply-templates
+    select="*[not(self::listitem) and not(self::title)]"/>
+  <xsl:apply-templates select="listitem"/>
+  <xsl:if test="(parent::para or parent::listitem) or following-sibling::node()">
+    <xsl:text>.sp&#10;</xsl:text>
+    <xsl:text>.RE&#10;</xsl:text>
+  </xsl:if>
+</xsl:template>
+
+<xsl:template match="refsect3">
+  <xsl:text>&#10;.SS "</xsl:text>
+  <xsl:value-of select="title[1]"/>
+  <xsl:text>"&#10;</xsl:text>
+  <xsl:apply-templates/>
+</xsl:template>
+
+  <!-- ================================================================== -->
+  <!-- These macros are from Docbook manpages XSLT development tree       -->
+  <!-- help to maintain manpage generation clean when difference between  -->
+  <!-- roff processors is important to note.                              -->
+
+  <xsl:template name="roff-if-else-start">
+    <xsl:param name="condition">n</xsl:param>
+    <xsl:text>.ie </xsl:text>
+    <xsl:value-of select="$condition"/>
+    <xsl:text> \{\&#10;</xsl:text>
+  </xsl:template>
+
+  <xsl:template name="roff-if-start">
+    <xsl:param name="condition">n</xsl:param>
+    <xsl:text>.if </xsl:text>
+    <xsl:value-of select="$condition"/>
+    <xsl:text> \{\&#10;</xsl:text>
+  </xsl:template>
+
+  <xsl:template name="roff-else">
+    <xsl:text>.\}&#10;</xsl:text>
+    <xsl:text>.el \{\&#10;</xsl:text>
+  </xsl:template>
+
+  <xsl:template name="roff-if-end">
+    <xsl:text>.\}&#10;</xsl:text>
+  </xsl:template>
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/manpage-summary.xsl b/docs-xml/xslt/manpage-summary.xsl
new file mode 100644
index 00000000000..295cf857491
--- /dev/null
+++ b/docs-xml/xslt/manpage-summary.xsl
@@ -0,0 +1,36 @@
+<?xml version='1.0'?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:exsl="http://exslt.org/common"
+	version="1.1">
+
+	<xsl:output method="xml" encoding="UTF-8" omit-xml-declaration="yes"/>
+
+	<xsl:template match="refentry">
+		<xsl:element name="varlistentry">
+			<xsl:apply-templates/>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="refentry/refmeta">
+		<xsl:element name="term">
+			<xsl:element name="ulink">
+				<xsl:attribute name="url">
+					<xsl:value-of select="refentrytitle"/><xsl:text>.</xsl:text><xsl:value-of select="manvolnum"/><xsl:text>.html</xsl:text>
+				</xsl:attribute>
+				<xsl:value-of select="refentrytitle"/><xsl:text>(</xsl:text><xsl:value-of select="manvolnum"/><xsl:text>)</xsl:text>
+			</xsl:element>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="refentry/refnamediv">
+		<xsl:element name="listitem">
+			<xsl:element name="para">
+				<xsl:value-of select="refpurpose"/><xsl:text>&#10;</xsl:text>
+			</xsl:element>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="@*|node()">
+		<xsl:apply-templates/>
+	</xsl:template>
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/sambadoc2pearson.xsl b/docs-xml/xslt/sambadoc2pearson.xsl
new file mode 100644
index 00000000000..d7124193755
--- /dev/null
+++ b/docs-xml/xslt/sambadoc2pearson.xsl
@@ -0,0 +1,80 @@
+<?xml version='1.0'?>
+<!-- 
+	Convert DocBook to XML validating against the Pearson DTD
+
+	(C) Jelmer Vernooij <jelmer@samba.org>			2004
+-->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:doc="http://nwalsh.com/xsl/documentation/1.0"
+	exclude-result-prefixes="doc"
+	version="1.1" >
+
+	<xsl:import href="docbook2pearson.xsl"/>
+
+	<xsl:strip-space elements="smbconfoption smbconfsection"/>
+
+	<xsl:template match="smbconfblock/smbconfsection">
+		<xsl:text>&#10;</xsl:text>
+		<xsl:value-of select="."/><xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="smbconfblock/smbconfoption">
+		<xsl:text>	</xsl:text><xsl:value-of select="@name"/><xsl:text> = </xsl:text><xsl:value-of select="text()"/><xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="smbconfblock">
+		<xsl:call-template name="transform.id.attribute"/>
+		<listingcode>
+		<xsl:apply-templates/>
+		</listingcode>
+	</xsl:template>
+
+	<xsl:template match="image">
+		<figure>
+			<xsl:call-template name="transform.id.attribute"/>
+			<description><xsl:value-of select="imagedescription"/></description>
+			<figureref>
+				<xsl:attribute name="fileref">
+					<xsl:value-of select="imagefile"/>
+				</xsl:attribute>
+				<xsl:if test="@scale != ''">
+					<xsl:attribute name="scale">
+						<xsl:value-of select="@scale"/>
+					</xsl:attribute>
+				</xsl:if>
+			</figureref>
+		</figure>
+	</xsl:template>
+
+	<xsl:template match="smbconfblock/smbconfcomment">
+		<xsl:text># </xsl:text><xsl:value-of select="text()"/><xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="smbconfblock/member">
+		<xsl:value-of select="text()"/><xsl:text>&#10;</xsl:text>
+		<xsl:message><xsl:text>Encountered &lt;member&gt; element inside of smbconfblock!</xsl:text></xsl:message>
+	</xsl:template>
+
+	<xsl:template match="filterline">
+		<code><xsl:apply-templates/></code>
+	</xsl:template>
+
+	<xsl:template match="smbconfoption">
+		<code><xsl:value-of select="@name"/></code>
+		<xsl:if test="text() != ''">
+			<xsl:text> = </xsl:text>
+			<xsl:value-of select="text()"/>
+		</xsl:if>
+		<xsl:text>&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="smbconfsection">
+		<code><xsl:apply-templates/></code>
+	</xsl:template>
+
+	<xsl:template match="ntgroup|ntuser">
+		<em><xsl:apply-templates/></em>
+	</xsl:template>
+	<!-- translator -->
+
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/smb.conf-html.xsl b/docs-xml/xslt/smb.conf-html.xsl
new file mode 100644
index 00000000000..ebf07d9161d
--- /dev/null
+++ b/docs-xml/xslt/smb.conf-html.xsl
@@ -0,0 +1,103 @@
+<?xml version='1.0'?>
+<!-- 
+	Samba-documentation specific stylesheets
+	Published under the GNU GPL
+
+	(C) Jelmer Vernooij 					2005
+-->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:exsl="http://exslt.org/common"
+	xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"
+	version="1.1"
+	extension-element-prefixes="exsl">
+
+	<xsl:import href="html-common.xsl"/>
+
+	<xsl:output method="xml" encoding="UTF-8" doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN" indent="yes" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"/>
+
+	<xsl:template match="samba:parameter">
+		<xsl:element name="html">
+			<xsl:element name="head">
+				<xsl:element name="link">
+					<xsl:attribute name="href"><xsl:text>smb.conf.xsl</xsl:text></xsl:attribute>
+					<xsl:attribute name="rel"><xsl:text>stylesheet</xsl:text></xsl:attribute>
+					<xsl:attribute name="type"><xsl:text>text/css</xsl:text></xsl:attribute>
+				</xsl:element>
+
+				<xsl:element name="title">
+					<xsl:value-of select="@name"/>
+				</xsl:element>
+			</xsl:element>
+			<xsl:element name="body">
+				<xsl:element name="h1">
+					<xsl:value-of select="@name"/>
+				</xsl:element>
+
+				<xsl:element name="div">
+					<xsl:attribute name="class"><xsl:text>context</xsl:text></xsl:attribute>
+					<xsl:text>Context: </xsl:text>
+					<xsl:choose>
+						<xsl:when test="@context = 'S'">
+							<xsl:text>Share-specific</xsl:text>
+						</xsl:when>
+
+						<xsl:when test="@context = 'G'">
+							<xsl:text>Global</xsl:text>
+						</xsl:when>
+
+						<xsl:otherwise>
+							<xsl:message><xsl:text>Unknown value for context attribute : </xsl:text><xsl:value-of select="@context"/></xsl:message>
+						</xsl:otherwise>
+					</xsl:choose>
+						
+				</xsl:element>
+
+				<xsl:element name="div">
+					<xsl:attribute name="class"><xsl:text>type</xsl:text></xsl:attribute>
+					<xsl:text>Type: </xsl:text>
+					<xsl:value-of select="@type"/>
+				</xsl:element>
+
+				<xsl:element name="div">
+					<xsl:attribute name="class"><xsl:text>synonyms</xsl:text></xsl:attribute>
+					<xsl:text>Synonyms: </xsl:text>
+					<xsl:for-each select="synonym">
+						<xsl:text>, </xsl:text>
+						<xsl:value-of select="text()"/>
+					</xsl:for-each>
+				</xsl:element>
+
+				<xsl:for-each select="value">
+					<xsl:element name="div">
+						<xsl:attribute name="class"><xsl:text>value</xsl:text></xsl:attribute>
+						<xsl:choose>
+							<xsl:when test="@type = 'default'">
+								<xsl:text>Default value</xsl:text>
+							</xsl:when>
+							<xsl:when test="@type = 'example'">
+								<xsl:text>Example value</xsl:text>
+							</xsl:when>
+						</xsl:choose>
+
+						<xsl:text>: </xsl:text>
+					
+						<xsl:value-of select="text()"/>
+
+					</xsl:element>
+				</xsl:for-each>
+
+				<xsl:element name="div">
+					<xsl:attribute name="class"><xsl:text>description</xsl:text></xsl:attribute>
+
+					<xsl:for-each select="description">
+						<xsl:apply-templates/>
+					</xsl:for-each>
+				</xsl:element>
+			</xsl:element>
+		</xsl:element>
+	</xsl:template>
+
+	<xsl:template match="description">
+		<xsl:apply-templates/>
+	</xsl:template>
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/strip-references.xsl b/docs-xml/xslt/strip-references.xsl
new file mode 100644
index 00000000000..c3dbb71e112
--- /dev/null
+++ b/docs-xml/xslt/strip-references.xsl
@@ -0,0 +1,10 @@
+<?xml version='1.0'?>
+<!-- Removes particular (unuseful for the book) elements from references -->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	version="1.1">
+	<xsl:template match="reference/refentry/refsect1[title='VERSION' or title='AUTHOR']"/>
+
+	<xsl:template match="reference/refentry/refmeta"/>
+
+	<xsl:template match="reference/refentry/refnamediv"/>
+</xsl:stylesheet>
diff --git a/docs-xml/xslt/yodl.xsl b/docs-xml/xslt/yodl.xsl
new file mode 100644
index 00000000000..bac86c826c2
--- /dev/null
+++ b/docs-xml/xslt/yodl.xsl
@@ -0,0 +1,320 @@
+<?xml version='1.0'?>
+<!-- 
+	DocBook to yodl converter
+	
+	Lacks support for a few docbook tags, but pretty much all 
+	yodl macros are used
+
+	(C) Jelmer Vernooij 					2004
+-->
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+	xmlns:exsl="http://exslt.org/common"
+	version="1.1">
+
+	<xsl:output method="text" encoding="iso-8859-1" standalone="yes" indent="no"/>
+	<xsl:strip-space elements="*"/>
+
+	<xsl:template match="refentry">
+		<xsl:text>manpage(</xsl:text>
+		<xsl:value-of select="refmeta/refentrytitle"/>
+		<xsl:text>)()(</xsl:text>
+		<xsl:value-of select="refmeta/manvolnum"/>
+		<xsl:text>)(package)()&#10;</xsl:text>
+
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="article">
+		<xsl:text>article(</xsl:text>
+		<xsl:value-of select="title"/>
+		<xsl:text>)(</xsl:text>
+		<xsl:text>FIXME</xsl:text>
+		<xsl:text>)(</xsl:text>
+		<xsl:value-of select="articleinfo/pubdate"/>
+		<xsl:text>)</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="report">
+		<xsl:text>report(</xsl:text>
+		<xsl:value-of select="title"/>
+		<xsl:text>)(</xsl:text>
+		<xsl:text>FIXME</xsl:text>
+		<xsl:text>)(</xsl:text>
+		<xsl:value-of select="articleinfo/pubdate"/>
+		<xsl:text>)</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="book">
+		<xsl:text>book(</xsl:text>
+		<xsl:value-of select="title"/>
+		<xsl:text>)(</xsl:text>
+		<xsl:text>FIXME</xsl:text>
+		<xsl:text>)(</xsl:text>
+		<xsl:value-of select="articleinfo/pubdate"/>
+		<xsl:text>)</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="chapter">
+		<xsl:choose>
+			<xsl:when test="@id = ''">
+				<xsl:text>chapter(</xsl:text>
+				<xsl:value-of select="title"/>
+				<xsl:text>)&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>lchapter(</xsl:text>
+				<xsl:value-of select="@id"/>
+				<xsl:text>)(</xsl:text>
+				<xsl:value-of select="title"/>
+				<xsl:text>)&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="citerefentry">
+		<xsl:value-of select="refentrytitle"/>
+		<xsl:text>(</xsl:text>
+		<xsl:value-of select="manvolnum"/>
+		<xsl:text>)</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="para">
+		<xsl:apply-templates/>
+		<xsl:text>&#10;&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="formalpara">
+		<xsl:text>paragraph(</xsl:text>
+		<xsl:value-of select="title"/>
+		<xsl:text>)&#10;</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="part">
+		<xsl:text>part(</xsl:text>
+		<xsl:value-of select="title"/>
+		<xsl:text>)&#10;</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+	
+	<xsl:template match="preface">
+		<xsl:text>nchapter(</xsl:text>
+		<xsl:value-of select="title"/>
+		<xsl:text>)&#10;</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="quote">
+		<xsl:text>"</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>"</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="parameter|filename">
+		<xsl:text>code(</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>)</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="emphasis">
+		<xsl:text>em(</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>)</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="command">
+		<xsl:text>bf(</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>)</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="refnamediv">
+		<xsl:text>manpagename(</xsl:text>
+		<xsl:value-of select="refname"/>
+		<xsl:text>)(</xsl:text>
+		<xsl:value-of select="refpurpose"/>
+		<xsl:text>)&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="refsynopsisdiv">
+		<xsl:text>manpagesynopsis()</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="refsect1|refsect2">
+		<xsl:choose>
+			<xsl:when test="title='DESCRIPTION'">
+				<xsl:text>&#10;manpagedescription()&#10;&#10;</xsl:text>
+			</xsl:when>
+			<xsl:when test="title='OPTIONS'">
+				<xsl:text>&#10;manpageoptions()&#10;&#10;</xsl:text>
+			</xsl:when>
+			<xsl:when test="title='FILES'">
+				<xsl:text>&#10;manpagefiles()&#10;&#10;</xsl:text>
+			</xsl:when>
+			<xsl:when test="title='SEE ALSO'">
+				<xsl:text>&#10;manpageseealso()&#10;&#10;</xsl:text>
+			</xsl:when>
+			<xsl:when test="title='DIAGNOSTICS'">
+				<xsl:text>&#10;manpagediagnostics()&#10;&#10;</xsl:text>
+			</xsl:when>
+			<xsl:when test="title='BUGS'">
+				<xsl:text>&#10;manpagebugs()&#10;&#10;</xsl:text>
+			</xsl:when>
+			<xsl:when test="title='AUTHOR'">
+				<xsl:text>&#10;manpageauthor()&#10;&#10;</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>&#10;manpagesection(</xsl:text>
+				<xsl:value-of select="title"/>
+				<xsl:text>)&#10;&#10;</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="orderedlist">
+		<xsl:text>startdit()&#10;</xsl:text>
+		<xsl:for-each select="listitem">
+			<xsl:text>dit() </xsl:text>
+			<xsl:copy>
+				<xsl:apply-templates/>
+			</xsl:copy>
+			<xsl:text>&#10;</xsl:text>
+		</xsl:for-each>
+		<xsl:text>enddit()&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="itemizedlist">
+		<xsl:text>startit()&#10;</xsl:text>
+		<xsl:for-each select="listitem">
+			<xsl:text>it() </xsl:text>
+			<xsl:copy>
+				<xsl:apply-templates/>
+			</xsl:copy>
+			<xsl:text>&#10;</xsl:text>
+		</xsl:for-each>
+		<xsl:text>endit()&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="variablelist">
+		<xsl:text>startdit()&#10;</xsl:text>
+		<xsl:for-each select="varlistentry">
+			<xsl:text>dit(</xsl:text>
+			<xsl:copy-of select="term">
+				<xsl:apply-templates/>
+			</xsl:copy-of>
+			<xsl:text>) </xsl:text>
+			<xsl:apply-templates select="listitem/para"/>
+			<xsl:text>&#10;</xsl:text>
+		</xsl:for-each>
+		<xsl:text>enddit()&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="anchor">
+		<xsl:text>label(</xsl:text>
+		<xsl:value-of select="@id"/>
+		<xsl:text>)&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="footnote">
+		<xsl:text>footnote(</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>)</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="toc">
+		<xsl:text>gettocstring()&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="ulink">
+		<xsl:text>&#10;</xsl:text>
+		<xsl:text>url(</xsl:text>
+		<xsl:value-of select="url"/>
+		<xsl:text>)(</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>)</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="link">
+		<xsl:text>lref(</xsl:text>
+		<xsl:apply-templates/>
+		<xsl:text>)(</xsl:text>
+		<xsl:value-of select="@linkend"/>
+		<xsl:text>)</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="index">
+		<xsl:text>printindex()&#10;</xsl:text>
+	</xsl:template>
+
+	<xsl:template match="sect1">
+		<xsl:choose>
+			<xsl:when test="@id = ''">
+				<xsl:text>sect(</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>lsect(</xsl:text>
+				<xsl:value-of select="@id"/>
+				<xsl:text>)(</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:value-of select="title"/>
+		<xsl:text>)&#10;</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="sect2">
+		<xsl:choose>
+			<xsl:when test="@id = ''">
+				<xsl:text>subsect(</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>lsubsect(</xsl:text>
+				<xsl:value-of select="@id"/>
+				<xsl:text>)(</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:value-of select="title"/>
+		<xsl:text>)&#10;</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="sect3">
+		<xsl:choose>
+			<xsl:when test="@id = ''">
+				<xsl:text>subsubsect(</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>lsubsubsect(</xsl:text>
+				<xsl:value-of select="@id"/>
+				<xsl:text>)(</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:value-of select="title"/>
+		<xsl:text>)&#10;</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="sect4">
+		<xsl:choose>
+			<xsl:when test="@id = ''">
+				<xsl:text>subsubsubsect(</xsl:text>
+			</xsl:when>
+			<xsl:otherwise>
+				<xsl:text>lsubsubsubsect(</xsl:text>
+				<xsl:value-of select="@id"/>
+				<xsl:text>)(</xsl:text>
+			</xsl:otherwise>
+		</xsl:choose>
+		<xsl:value-of select="title"/>
+		<xsl:text>)&#10;</xsl:text>
+		<xsl:apply-templates/>
+	</xsl:template>
+
+	<xsl:template match="*"/>
+
+</xsl:stylesheet>